WEBVTT Kind: captions Language: en 00:00:01.100 --> 00:00:05.059 align:start position:0% if<00:00:02.100> you<00:00:03.290> essentially<00:00:04.290> the<00:00:04.560> a<00:00:04.770> theorem 00:00:05.059 --> 00:00:05.069 align:start position:0% if you essentially the a theorem 00:00:05.069 --> 00:00:06.440 align:start position:0% if you essentially the a theorem ecosystem<00:00:05.549> has<00:00:05.670> been<00:00:05.879> growing<00:00:06.210> at<00:00:06.330> a<00:00:06.359> very 00:00:06.440 --> 00:00:06.450 align:start position:0% ecosystem has been growing at a very 00:00:06.450 --> 00:00:08.780 align:start position:0% ecosystem has been growing at a very steady<00:00:06.870> pace<00:00:07.200> in<00:00:07.379> the<00:00:07.440> last<00:00:07.649> couple<00:00:08.280> of<00:00:08.460> years 00:00:08.780 --> 00:00:08.790 align:start position:0% steady pace in the last couple of years 00:00:08.790 --> 00:00:11.780 align:start position:0% steady pace in the last couple of years but<00:00:09.480> if<00:00:09.630> you<00:00:09.719> look<00:00:09.870> at<00:00:10.099> some<00:00:11.099> of<00:00:11.130> these<00:00:11.370> ether 00:00:11.780 --> 00:00:11.790 align:start position:0% but if you look at some of these ether 00:00:11.790 --> 00:00:13.249 align:start position:0% but if you look at some of these ether noes<00:00:11.969> websites<00:00:12.480> which<00:00:12.690> track<00:00:12.900> the<00:00:13.019> number<00:00:13.200> of 00:00:13.249 --> 00:00:13.259 align:start position:0% noes websites which track the number of 00:00:13.259 --> 00:00:14.930 align:start position:0% noes websites which track the number of full<00:00:13.469> nose<00:00:13.679> you'll<00:00:13.950> see<00:00:14.160> that<00:00:14.280> that<00:00:14.580> one<00:00:14.820> is 00:00:14.930 --> 00:00:14.940 align:start position:0% full nose you'll see that that one is 00:00:14.940 --> 00:00:16.369 align:start position:0% full nose you'll see that that one is kind<00:00:15.120> of<00:00:15.269> constant<00:00:15.780> or<00:00:15.960> maybe<00:00:16.260> even 00:00:16.369 --> 00:00:16.379 align:start position:0% kind of constant or maybe even 00:00:16.379 --> 00:00:20.480 align:start position:0% kind of constant or maybe even decreasing<00:00:17.010> and<00:00:17.400> why<00:00:18.359> is<00:00:18.420> that<00:00:18.600> well<00:00:19.310> first<00:00:20.310> up 00:00:20.480 --> 00:00:20.490 align:start position:0% decreasing and why is that well first up 00:00:20.490 --> 00:00:23.150 align:start position:0% decreasing and why is that well first up because<00:00:20.820> running<00:00:21.029> a<00:00:21.150> full-out<00:00:21.480> sucks<00:00:21.810> but<00:00:22.650> and 00:00:23.150 --> 00:00:23.160 align:start position:0% because running a full-out sucks but and 00:00:23.160 --> 00:00:25.330 align:start position:0% because running a full-out sucks but and even<00:00:23.789> though<00:00:23.880> we're<00:00:24.029> trying<00:00:24.180> to<00:00:24.539> solve<00:00:24.750> that 00:00:25.330 --> 00:00:25.340 align:start position:0% even though we're trying to solve that 00:00:25.340 --> 00:00:27.410 align:start position:0% even though we're trying to solve that the<00:00:26.340> issue<00:00:26.550> is<00:00:26.699> that<00:00:26.730> people<00:00:27.210> will<00:00:27.359> always 00:00:27.410 --> 00:00:27.420 align:start position:0% the issue is that people will always 00:00:27.420 --> 00:00:29.089 align:start position:0% the issue is that people will always prefer<00:00:27.750> having<00:00:28.080> a<00:00:28.260> light<00:00:28.410> client<00:00:28.800> opposed<00:00:29.039> to 00:00:29.089 --> 00:00:29.099 align:start position:0% prefer having a light client opposed to 00:00:29.099 --> 00:00:31.250 align:start position:0% prefer having a light client opposed to running<00:00:29.189> a<00:00:29.340> full<00:00:29.519> client<00:00:29.699> or<00:00:30.510> running<00:00:30.929> in 00:00:31.250 --> 00:00:31.260 align:start position:0% running a full client or running in 00:00:31.260 --> 00:00:34.069 align:start position:0% running a full client or running in fostering<00:00:31.949> a<00:00:32.250> light<00:00:32.399> client<00:00:32.850> or<00:00:32.969> even<00:00:33.079> just 00:00:34.069 --> 00:00:34.079 align:start position:0% fostering a light client or even just 00:00:34.079 --> 00:00:36.170 align:start position:0% fostering a light client or even just using<00:00:34.410> a<00:00:34.500> RESTful<00:00:34.829> API<00:00:34.860> versus<00:00:35.700> actually 00:00:36.170 --> 00:00:36.180 align:start position:0% using a RESTful API versus actually 00:00:36.180 --> 00:00:39.470 align:start position:0% using a RESTful API versus actually connecting<00:00:36.750> to<00:00:36.780> infra<00:00:37.680> and<00:00:38.309> this<00:00:39.059> is<00:00:39.210> kind<00:00:39.420> of 00:00:39.470 --> 00:00:39.480 align:start position:0% connecting to infra and this is kind of 00:00:39.480 --> 00:00:41.420 align:start position:0% connecting to infra and this is kind of fine<00:00:39.780> people<00:00:40.320> are<00:00:40.649> kind<00:00:40.980> of<00:00:41.100> more<00:00:41.309> or<00:00:41.399> less 00:00:41.420 --> 00:00:41.430 align:start position:0% fine people are kind of more or less 00:00:41.430 --> 00:00:43.580 align:start position:0% fine people are kind of more or less aware<00:00:41.879> of<00:00:42.149> the<00:00:42.329> implications<00:00:42.960> security-wise 00:00:43.580 --> 00:00:43.590 align:start position:0% aware of the implications security-wise 00:00:43.590 --> 00:00:46.040 align:start position:0% aware of the implications security-wise that<00:00:43.920> okay<00:00:44.219> if<00:00:44.309> use<00:00:44.520> a<00:00:44.550> light<00:00:44.820> client<00:00:45.300> and<00:00:45.480> the 00:00:46.040 --> 00:00:46.050 align:start position:0% that okay if use a light client and the 00:00:46.050 --> 00:00:47.840 align:start position:0% that okay if use a light client and the security<00:00:46.469> is<00:00:46.559> not<00:00:46.680> the<00:00:46.860> same<00:00:47.070> if<00:00:47.309> using<00:00:47.670> fluid 00:00:47.840 --> 00:00:47.850 align:start position:0% security is not the same if using fluid 00:00:47.850 --> 00:00:50.029 align:start position:0% security is not the same if using fluid and<00:00:48.090> you<00:00:48.149> kind<00:00:48.420> of<00:00:48.539> trust<00:00:48.809> them<00:00:49.170> you<00:00:49.649> can<00:00:49.920> maybe 00:00:50.029 --> 00:00:50.039 align:start position:0% and you kind of trust them you can maybe 00:00:50.039 --> 00:00:51.950 align:start position:0% and you kind of trust them you can maybe make<00:00:50.280> a<00:00:50.340> few<00:00:50.460> proofs<00:00:51.149> but<00:00:51.360> you<00:00:51.480> still<00:00:51.750> trust 00:00:51.950 --> 00:00:51.960 align:start position:0% make a few proofs but you still trust 00:00:51.960 --> 00:00:54.200 align:start position:0% make a few proofs but you still trust them<00:00:52.110> and<00:00:52.440> if<00:00:53.010> you<00:00:53.160> something<00:00:53.879> like<00:00:53.969> ether 00:00:54.200 --> 00:00:54.210 align:start position:0% them and if you something like ether 00:00:54.210 --> 00:00:56.630 align:start position:0% them and if you something like ether scan<00:00:54.600> then<00:00:54.899> you<00:00:54.989> know<00:00:55.170> that<00:00:55.530> you<00:00:56.160> cannot<00:00:56.399> trust 00:00:56.630 --> 00:00:56.640 align:start position:0% scan then you know that you cannot trust 00:00:56.640 --> 00:00:58.910 align:start position:0% scan then you know that you cannot trust them<00:00:56.940> but<00:00:57.210> yeah<00:00:57.480> you<00:00:57.539> kind<00:00:57.809> of<00:00:57.870> trust<00:00:58.170> them<00:00:58.440> so 00:00:58.910 --> 00:00:58.920 align:start position:0% them but yeah you kind of trust them so 00:00:58.920 --> 00:01:00.920 align:start position:0% them but yeah you kind of trust them so people<00:00:59.129> can<00:00:59.489> make<00:01:00.090> balanced<00:01:00.480> decisions 00:01:00.920 --> 00:01:00.930 align:start position:0% people can make balanced decisions 00:01:00.930 --> 00:01:03.319 align:start position:0% people can make balanced decisions however<00:01:01.680> one<00:01:02.460> thing<00:01:02.489> that<00:01:02.730> people<00:01:03.149> don't 00:01:03.319 --> 00:01:03.329 align:start position:0% however one thing that people don't 00:01:03.329 --> 00:01:06.770 align:start position:0% however one thing that people don't really<00:01:04.250> talk<00:01:05.250> much<00:01:05.309> about<00:01:05.670> is<00:01:06.150> what<00:01:06.390> happens 00:01:06.770 --> 00:01:06.780 align:start position:0% really talk much about is what happens 00:01:06.780 --> 00:01:08.630 align:start position:0% really talk much about is what happens for<00:01:06.960> example<00:01:07.020> to<00:01:07.439> metadata<00:01:07.830> what<00:01:08.250> happens 00:01:08.630 --> 00:01:08.640 align:start position:0% for example to metadata what happens 00:01:08.640 --> 00:01:10.460 align:start position:0% for example to metadata what happens when<00:01:08.880> you<00:01:09.030> actually<00:01:09.180> go<00:01:09.570> from<00:01:09.780> running<00:01:10.200> a<00:01:10.260> full 00:01:10.460 --> 00:01:10.470 align:start position:0% when you actually go from running a full 00:01:10.470 --> 00:01:12.320 align:start position:0% when you actually go from running a full node<00:01:10.680> down<00:01:10.979> to<00:01:11.159> running<00:01:11.430> a<00:01:11.490> restful<00:01:12.000> service 00:01:12.320 --> 00:01:12.330 align:start position:0% node down to running a restful service 00:01:12.330 --> 00:01:15.230 align:start position:0% node down to running a restful service and<00:01:12.570> how<00:01:13.500> that<00:01:13.710> actually<00:01:14.090> changes<00:01:15.090> the 00:01:15.230 --> 00:01:15.240 align:start position:0% and how that actually changes the 00:01:15.240 --> 00:01:17.359 align:start position:0% and how that actually changes the behaviors<00:01:15.689> or<00:01:15.990> the<00:01:16.140> the<00:01:16.500> traits<00:01:16.979> that<00:01:17.100> you 00:01:17.359 --> 00:01:17.369 align:start position:0% behaviors or the the traits that you 00:01:17.369 --> 00:01:20.060 align:start position:0% behaviors or the the traits that you leave<00:01:17.549> behind<00:01:17.700> you<00:01:18.080> and<00:01:19.080> that's<00:01:19.350> exactly<00:01:19.680> what 00:01:20.060 --> 00:01:20.070 align:start position:0% leave behind you and that's exactly what 00:01:20.070 --> 00:01:22.429 align:start position:0% leave behind you and that's exactly what I<00:01:20.580> would<00:01:20.729> like<00:01:20.970> to<00:01:21.030> talk<00:01:21.270> about<00:01:21.570> a<00:01:21.840> bit<00:01:22.170> in<00:01:22.320> this 00:01:22.429 --> 00:01:22.439 align:start position:0% I would like to talk about a bit in this 00:01:22.439 --> 00:01:25.310 align:start position:0% I would like to talk about a bit in this talk<00:01:22.710> specifically<00:01:23.670> let's<00:01:24.540> start<00:01:24.810> with<00:01:25.049> web 00:01:25.310 --> 00:01:25.320 align:start position:0% talk specifically let's start with web 00:01:25.320 --> 00:01:28.850 align:start position:0% talk specifically let's start with web 2.0<00:01:25.920> interfaces<00:01:26.580> now<00:01:27.299> my<00:01:28.049> talk<00:01:28.290> is<00:01:28.439> relevant 00:01:28.850 --> 00:01:28.860 align:start position:0% 2.0 interfaces now my talk is relevant 00:01:28.860 --> 00:01:31.730 align:start position:0% 2.0 interfaces now my talk is relevant for<00:01:29.040> almost<00:01:29.369> any<00:01:29.670> depth<00:01:29.970> that<00:01:30.270> uses<00:01:30.630> a<00:01:30.740> restful 00:01:31.730 --> 00:01:31.740 align:start position:0% for almost any depth that uses a restful 00:01:31.740 --> 00:01:33.140 align:start position:0% for almost any depth that uses a restful service<00:01:32.070> as<00:01:32.189> a<00:01:32.220> background<00:01:32.460> the<00:01:32.820> reason<00:01:33.060> I'm 00:01:33.140 --> 00:01:33.150 align:start position:0% service as a background the reason I'm 00:01:33.150 --> 00:01:34.940 align:start position:0% service as a background the reason I'm picking<00:01:33.329> ether<00:01:33.869> scan<00:01:34.140> is<00:01:34.350> not<00:01:34.500> to<00:01:34.619> pick<00:01:34.799> on 00:01:34.940 --> 00:01:34.950 align:start position:0% picking ether scan is not to pick on 00:01:34.950 --> 00:01:37.190 align:start position:0% picking ether scan is not to pick on them<00:01:35.100> rather<00:01:35.400> because<00:01:35.939> it's<00:01:36.090> everybody<00:01:36.840> knows 00:01:37.190 --> 00:01:37.200 align:start position:0% them rather because it's everybody knows 00:01:37.200 --> 00:01:39.020 align:start position:0% them rather because it's everybody knows what<00:01:37.470> if<00:01:37.590> the<00:01:37.710> scan<00:01:37.950> is<00:01:37.979> how<00:01:38.310> ether<00:01:38.610> scan<00:01:38.820> works 00:01:39.020 --> 00:01:39.030 align:start position:0% what if the scan is how ether scan works 00:01:39.030 --> 00:01:41.780 align:start position:0% what if the scan is how ether scan works so<00:01:39.990> what<00:01:40.259> is<00:01:40.380> either<00:01:40.530> scan<00:01:40.950> just<00:01:41.159> a<00:01:41.340> quit<00:01:41.520> in<00:01:41.700> a 00:01:41.780 --> 00:01:41.790 align:start position:0% so what is either scan just a quit in a 00:01:41.790 --> 00:01:43.580 align:start position:0% so what is either scan just a quit in a two-word<00:01:42.150> summary<00:01:42.899> basically<00:01:43.290> that<00:01:43.560> allows 00:01:43.580 --> 00:01:43.590 align:start position:0% two-word summary basically that allows 00:01:43.590 --> 00:01:45.800 align:start position:0% two-word summary basically that allows you<00:01:43.920> to<00:01:44.070> check<00:01:44.250> your<00:01:44.430> balances<00:01:45.119> your<00:01:45.270> tokens 00:01:45.800 --> 00:01:45.810 align:start position:0% you to check your balances your tokens 00:01:45.810 --> 00:01:50.840 align:start position:0% you to check your balances your tokens transactions<00:01:47.720> events<00:01:48.720> etc<00:01:49.409> and<00:01:49.700> apart<00:01:50.700> from 00:01:50.840 --> 00:01:50.850 align:start position:0% transactions events etc and apart from 00:01:50.850 --> 00:01:52.700 align:start position:0% transactions events etc and apart from that<00:01:50.970> it<00:01:51.119> also<00:01:51.270> allows<00:01:51.450> you<00:01:51.869> to<00:01:51.899> comment<00:01:52.590> on 00:01:52.700 --> 00:01:52.710 align:start position:0% that it also allows you to comment on 00:01:52.710 --> 00:01:55.730 align:start position:0% that it also allows you to comment on certain<00:01:53.070> accounts<00:01:53.460> if<00:01:53.610> you<00:01:53.640> like<00:01:54.020> now<00:01:55.020> this<00:01:55.560> is 00:01:55.730 --> 00:01:55.740 align:start position:0% certain accounts if you like now this is 00:01:55.740 --> 00:01:57.679 align:start position:0% certain accounts if you like now this is the<00:01:55.979> surface<00:01:56.369> what<00:01:56.579> happens<00:01:56.909> behind<00:01:57.479> the 00:01:57.679 --> 00:01:57.689 align:start position:0% the surface what happens behind the 00:01:57.689 --> 00:01:59.569 align:start position:0% the surface what happens behind the scenes<00:01:57.750> well<00:01:58.229> whatever<00:01:58.740> you<00:01:58.950> for<00:01:59.219> example<00:01:59.520> you 00:01:59.569 --> 00:01:59.579 align:start position:0% scenes well whatever you for example you 00:01:59.579 --> 00:02:01.069 align:start position:0% scenes well whatever you for example you want<00:01:59.729> to<00:01:59.790> check<00:01:59.969> your<00:02:00.030> balance<00:02:00.450> or<00:02:00.570> ether<00:02:00.810> scan 00:02:01.069 --> 00:02:01.079 align:start position:0% want to check your balance or ether scan 00:02:01.079 --> 00:02:04.850 align:start position:0% want to check your balance or ether scan you<00:02:02.689> try<00:02:03.689> to<00:02:03.750> load<00:02:03.930> this<00:02:04.079> Afghan<00:02:04.350> website 00:02:04.850 --> 00:02:04.860 align:start position:0% you try to load this Afghan website 00:02:04.860 --> 00:02:06.380 align:start position:0% you try to load this Afghan website which<00:02:05.100> goes<00:02:05.310> through<00:02:05.340> cloud<00:02:05.729> fair<00:02:06.030> because 00:02:06.380 --> 00:02:06.390 align:start position:0% which goes through cloud fair because 00:02:06.390 --> 00:02:08.059 align:start position:0% which goes through cloud fair because class<00:02:06.719> there<00:02:06.990> is<00:02:07.020> ether<00:02:07.350> scanned<00:02:07.590> accelerator 00:02:08.059 --> 00:02:08.069 align:start position:0% class there is ether scanned accelerator 00:02:08.069 --> 00:02:10.190 align:start position:0% class there is ether scanned accelerator ether<00:02:09.030> scan<00:02:09.300> returns<00:02:09.629> the<00:02:09.780> balance<00:02:10.080> and 00:02:10.190 --> 00:02:10.200 align:start position:0% ether scan returns the balance and 00:02:10.200 --> 00:02:11.750 align:start position:0% ether scan returns the balance and everything<00:02:10.289> plus<00:02:10.920> it<00:02:11.099> also<00:02:11.220> returns<00:02:11.580> a 00:02:11.750 --> 00:02:11.760 align:start position:0% everything plus it also returns a 00:02:11.760 --> 00:02:13.500 align:start position:0% everything plus it also returns a tracker<00:02:12.000> code<00:02:12.270> for<00:02:12.480> Google<00:02:12.720> Analytics 00:02:13.500 --> 00:02:13.510 align:start position:0% tracker code for Google Analytics 00:02:13.510 --> 00:02:17.160 align:start position:0% tracker code for Google Analytics I'm<00:02:13.930> better<00:02:14.200> discuss<00:02:14.680> forum<00:02:15.040> and<00:02:15.420> this<00:02:16.420> might 00:02:17.160 --> 00:02:17.170 align:start position:0% I'm better discuss forum and this might 00:02:17.170 --> 00:02:19.319 align:start position:0% I'm better discuss forum and this might sound<00:02:17.860> like<00:02:18.099> a<00:02:18.129> really<00:02:18.400> nice<00:02:18.610> design<00:02:18.909> really 00:02:19.319 --> 00:02:19.329 align:start position:0% sound like a really nice design really 00:02:19.329 --> 00:02:21.030 align:start position:0% sound like a really nice design really elegant<00:02:19.750> not<00:02:19.959> too<00:02:20.140> many<00:02:20.319> external<00:02:20.829> things 00:02:21.030 --> 00:02:21.040 align:start position:0% elegant not too many external things 00:02:21.040 --> 00:02:23.460 align:start position:0% elegant not too many external things included<00:02:21.579> but<00:02:22.209> if<00:02:22.360> we<00:02:22.480> start<00:02:22.720> digging<00:02:23.079> a<00:02:23.319> bit 00:02:23.460 --> 00:02:23.470 align:start position:0% included but if we start digging a bit 00:02:23.470 --> 00:02:25.770 align:start position:0% included but if we start digging a bit into<00:02:23.709> the<00:02:23.799> HTTP<00:02:24.220> protocol<00:02:24.640> we'll<00:02:25.450> see<00:02:25.599> a<00:02:25.629> few 00:02:25.770 --> 00:02:25.780 align:start position:0% into the HTTP protocol we'll see a few 00:02:25.780 --> 00:02:28.890 align:start position:0% into the HTTP protocol we'll see a few surprises<00:02:26.610> notably<00:02:27.610> HTTP<00:02:28.180> has<00:02:28.299> a<00:02:28.329> concept<00:02:28.750> of 00:02:28.890 --> 00:02:28.900 align:start position:0% surprises notably HTTP has a concept of 00:02:28.900 --> 00:02:29.640 align:start position:0% surprises notably HTTP has a concept of referrer 00:02:29.640 --> 00:02:29.650 align:start position:0% referrer 00:02:29.650 --> 00:02:31.920 align:start position:0% referrer every<00:02:30.310> time<00:02:30.519> you<00:02:30.670> visit<00:02:30.940> a<00:02:31.000> webpage<00:02:31.180> from 00:02:31.920 --> 00:02:31.930 align:start position:0% every time you visit a webpage from 00:02:31.930 --> 00:02:35.100 align:start position:0% every time you visit a webpage from another<00:02:32.230> web<00:02:32.440> page<00:02:32.470> you<00:02:33.310> get<00:02:33.489> a<00:02:33.730> Stinney<00:02:34.110> extra 00:02:35.100 --> 00:02:35.110 align:start position:0% another web page you get a Stinney extra 00:02:35.110 --> 00:02:36.809 align:start position:0% another web page you get a Stinney extra header<00:02:35.319> saying<00:02:35.860> that<00:02:36.069> you<00:02:36.220> came<00:02:36.430> from<00:02:36.610> this 00:02:36.809 --> 00:02:36.819 align:start position:0% header saying that you came from this 00:02:36.819 --> 00:02:38.819 align:start position:0% header saying that you came from this website<00:02:37.030> the<00:02:37.810> same<00:02:37.959> happens<00:02:38.319> if<00:02:38.409> you<00:02:38.500> embed 00:02:38.819 --> 00:02:38.829 align:start position:0% website the same happens if you embed 00:02:38.829 --> 00:02:40.890 align:start position:0% website the same happens if you embed something<00:02:39.099> every<00:02:39.940> time<00:02:39.970> you<00:02:40.150> embed<00:02:40.450> an<00:02:40.569> iframe 00:02:40.890 --> 00:02:40.900 align:start position:0% something every time you embed an iframe 00:02:40.900 --> 00:02:43.770 align:start position:0% something every time you embed an iframe into<00:02:41.349> your<00:02:41.530> own<00:02:41.650> little<00:02:42.090> website<00:02:43.090> that<00:02:43.450> iframe 00:02:43.770 --> 00:02:43.780 align:start position:0% into your own little website that iframe 00:02:43.780 --> 00:02:45.899 align:start position:0% into your own little website that iframe will<00:02:44.140> get<00:02:44.290> the<00:02:44.379> ping<00:02:44.620> that<00:02:44.859> you<00:02:45.250> were<00:02:45.700> actually 00:02:45.899 --> 00:02:45.909 align:start position:0% will get the ping that you were actually 00:02:45.909 --> 00:02:49.199 align:start position:0% will get the ping that you were actually coming<00:02:46.510> from<00:02:46.720> another<00:02:47.109> website<00:02:47.409> and<00:02:48.220> why<00:02:49.150> is 00:02:49.199 --> 00:02:49.209 align:start position:0% coming from another website and why is 00:02:49.209 --> 00:02:52.770 align:start position:0% coming from another website and why is this<00:02:49.420> bad<00:02:49.659> well<00:02:50.349> when<00:02:50.769> you<00:02:50.950> actually<00:02:51.400> load<00:02:52.060> for 00:02:52.770 --> 00:02:52.780 align:start position:0% this bad well when you actually load for 00:02:52.780 --> 00:02:55.410 align:start position:0% this bad well when you actually load for example<00:02:53.109> in<00:02:53.230> this<00:02:53.319> page<00:02:53.590> it's<00:02:53.859> a<00:02:54.180> ether<00:02:55.180> scan 00:02:55.410 --> 00:02:55.420 align:start position:0% example in this page it's a ether scan 00:02:55.420 --> 00:02:59.670 align:start position:0% example in this page it's a ether scan dot<00:02:55.569> io<00:02:55.780> /<00:02:55.959> address<00:02:56.620> /<00:02:57.000> 0<00:02:58.000> X<00:02:58.120> whatever<00:02:58.560> when<00:02:59.560> you 00:02:59.670 --> 00:02:59.680 align:start position:0% dot io / address / 0 X whatever when you 00:02:59.680 --> 00:03:02.009 align:start position:0% dot io / address / 0 X whatever when you load<00:02:59.829> that<00:03:00.030> Google<00:03:01.030> Analytics<00:03:01.239> will<00:03:01.659> actually 00:03:02.009 --> 00:03:02.019 align:start position:0% load that Google Analytics will actually 00:03:02.019 --> 00:03:05.520 align:start position:0% load that Google Analytics will actually have<00:03:02.260> a<00:03:02.590> ping<00:03:03.400> that<00:03:03.790> you<00:03:04.120> this<00:03:04.510> particular<00:03:05.109> IP 00:03:05.520 --> 00:03:05.530 align:start position:0% have a ping that you this particular IP 00:03:05.530 --> 00:03:07.860 align:start position:0% have a ping that you this particular IP address<00:03:05.739> loaded<00:03:06.430> that<00:03:06.819> particularly<00:03:07.299> theorum 00:03:07.860 --> 00:03:07.870 align:start position:0% address loaded that particularly theorum 00:03:07.870 --> 00:03:11.670 align:start position:0% address loaded that particularly theorum address<00:03:08.639> similarly<00:03:09.639> this<00:03:10.569> case<00:03:10.870> also<00:03:11.079> gets<00:03:11.560> a 00:03:11.670 --> 00:03:11.680 align:start position:0% address similarly this case also gets a 00:03:11.680 --> 00:03:13.890 align:start position:0% address similarly this case also gets a similar<00:03:11.859> ping<00:03:12.250> that<00:03:12.670> this<00:03:12.879> IP<00:03:13.060> address<00:03:13.239> loaded 00:03:13.890 --> 00:03:13.900 align:start position:0% similar ping that this IP address loaded 00:03:13.900 --> 00:03:15.930 align:start position:0% similar ping that this IP address loaded that<00:03:14.170> particularly<00:03:14.590> theorum<00:03:15.040> address<00:03:15.340> and<00:03:15.579> is 00:03:15.930 --> 00:03:15.940 align:start position:0% that particularly theorum address and is 00:03:15.940 --> 00:03:19.319 align:start position:0% that particularly theorum address and is that<00:03:16.150> bad<00:03:16.379> well<00:03:17.379> if<00:03:17.709> we<00:03:18.190> explore<00:03:19.180> what 00:03:19.319 --> 00:03:19.329 align:start position:0% that bad well if we explore what 00:03:19.329 --> 00:03:21.839 align:start position:0% that bad well if we explore what discussed<00:03:19.840> loads<00:03:20.079> the<00:03:20.949> things<00:03:21.220> start<00:03:21.609> to<00:03:21.669> get 00:03:21.839 --> 00:03:21.849 align:start position:0% discussed loads the things start to get 00:03:21.849 --> 00:03:24.509 align:start position:0% discussed loads the things start to get a<00:03:21.879> bit<00:03:22.090> weird<00:03:22.769> particularly<00:03:23.769> discussed<00:03:24.280> has 00:03:24.509 --> 00:03:24.519 align:start position:0% a bit weird particularly discussed has 00:03:24.519 --> 00:03:26.400 align:start position:0% a bit weird particularly discussed has three<00:03:24.879> types<00:03:25.060> of<00:03:25.239> integrations<00:03:25.840> has<00:03:26.049> social 00:03:26.400 --> 00:03:26.410 align:start position:0% three types of integrations has social 00:03:26.410 --> 00:03:28.039 align:start position:0% three types of integrations has social logins<00:03:26.590> to<00:03:26.889> Facebook<00:03:27.220> Google<00:03:27.489> and<00:03:27.549> Twitter 00:03:28.039 --> 00:03:28.049 align:start position:0% logins to Facebook Google and Twitter 00:03:28.049 --> 00:03:30.509 align:start position:0% logins to Facebook Google and Twitter which<00:03:29.049> means<00:03:29.319> that<00:03:29.620> this<00:03:29.769> cuss<00:03:30.040> actually 00:03:30.509 --> 00:03:30.519 align:start position:0% which means that this cuss actually 00:03:30.519 --> 00:03:33.330 align:start position:0% which means that this cuss actually reveals<00:03:30.940> the<00:03:31.239> IP<00:03:31.389> -<00:03:31.840> if<00:03:32.290> the<00:03:32.739> address<00:03:32.980> mapping 00:03:33.330 --> 00:03:33.340 align:start position:0% reveals the IP - if the address mapping 00:03:33.340 --> 00:03:37.080 align:start position:0% reveals the IP - if the address mapping to<00:03:33.940> Facebook<00:03:34.480> Twitter<00:03:34.959> and<00:03:35.349> Google+<00:03:35.739> and<00:03:36.129> it 00:03:37.080 --> 00:03:37.090 align:start position:0% to Facebook Twitter and Google+ and it 00:03:37.090 --> 00:03:40.020 align:start position:0% to Facebook Twitter and Google+ and it also<00:03:37.269> has<00:03:37.569> these<00:03:38.379> other<00:03:38.680> weird<00:03:38.980> trackers<00:03:39.790> kind 00:03:40.020 --> 00:03:40.030 align:start position:0% also has these other weird trackers kind 00:03:40.030 --> 00:03:43.439 align:start position:0% also has these other weird trackers kind of<00:03:40.120> like<00:03:40.269> people<00:03:40.540> market<00:03:41.169> a<00:03:41.319> I<00:03:41.410> might<00:03:42.449> mining 00:03:43.439 --> 00:03:43.449 align:start position:0% of like people market a I might mining 00:03:43.449 --> 00:03:45.089 align:start position:0% of like people market a I might mining market<00:03:43.629> and<00:03:43.959> all<00:03:44.049> kinds<00:03:44.319> of<00:03:44.379> weird<00:03:44.620> I<00:03:44.650> can't 00:03:45.089 --> 00:03:45.099 align:start position:0% market and all kinds of weird I can't 00:03:45.099 --> 00:03:47.250 align:start position:0% market and all kinds of weird I can't read<00:03:45.280> this<00:03:45.340> bit<00:03:45.730> time<00:03:45.940> here<00:03:46.209> but<00:03:46.870> you<00:03:47.019> get<00:03:47.109> the 00:03:47.250 --> 00:03:47.260 align:start position:0% read this bit time here but you get the 00:03:47.260 --> 00:03:49.349 align:start position:0% read this bit time here but you get the picture<00:03:47.590> so<00:03:47.620> it<00:03:47.829> it<00:03:48.190> loads<00:03:48.549> a<00:03:48.669> lot<00:03:48.790> of<00:03:48.910> trackers 00:03:49.349 --> 00:03:49.359 align:start position:0% picture so it it loads a lot of trackers 00:03:49.359 --> 00:03:51.539 align:start position:0% picture so it it loads a lot of trackers and<00:03:49.569> not<00:03:49.840> only<00:03:49.989> that<00:03:50.109> but<00:03:50.709> it<00:03:50.859> also<00:03:51.010> loads<00:03:51.340> a 00:03:51.539 --> 00:03:51.549 align:start position:0% and not only that but it also loads a 00:03:51.549 --> 00:03:53.490 align:start position:0% and not only that but it also loads a lot<00:03:51.819> of<00:03:51.970> I<00:03:52.120> think<00:03:52.150> disgust<00:03:53.019> has<00:03:53.199> 11 00:03:53.490 --> 00:03:53.500 align:start position:0% lot of I think disgust has 11 00:03:53.500 --> 00:03:55.949 align:start position:0% lot of I think disgust has 11 integrations<00:03:54.099> with<00:03:54.310> YouTube<00:03:54.669> Vimeo<00:03:55.000> and<00:03:55.449> all 00:03:55.949 --> 00:03:55.959 align:start position:0% integrations with YouTube Vimeo and all 00:03:55.959 --> 00:03:59.189 align:start position:0% integrations with YouTube Vimeo and all kinds<00:03:56.349> of<00:03:56.379> other<00:03:56.530> services<00:03:57.129> and<00:03:57.870> this<00:03:58.870> is<00:03:59.049> an 00:03:59.189 --> 00:03:59.199 align:start position:0% kinds of other services and this is an 00:03:59.199 --> 00:04:00.899 align:start position:0% kinds of other services and this is an issue<00:03:59.319> because<00:03:59.919> you<00:03:59.949> are<00:04:00.459> essentially 00:04:00.899 --> 00:04:00.909 align:start position:0% issue because you are essentially 00:04:00.909 --> 00:04:03.990 align:start position:0% issue because you are essentially associating<00:04:01.659> your<00:04:01.780> IP<00:04:01.959> to<00:04:02.590> a<00:04:02.859> theorem<00:04:03.639> address 00:04:03.990 --> 00:04:04.000 align:start position:0% associating your IP to a theorem address 00:04:04.000 --> 00:04:05.819 align:start position:0% associating your IP to a theorem address mapping<00:04:04.510> and<00:04:04.690> you're<00:04:04.810> revealing<00:04:05.109> that<00:04:05.500> to<00:04:05.799> a 00:04:05.819 --> 00:04:05.829 align:start position:0% mapping and you're revealing that to a 00:04:05.829 --> 00:04:08.729 align:start position:0% mapping and you're revealing that to a whole<00:04:06.010> lot<00:04:06.250> of<00:04:06.370> external<00:04:06.639> services<00:04:07.299> and<00:04:07.870> again 00:04:08.729 --> 00:04:08.739 align:start position:0% whole lot of external services and again 00:04:08.739 --> 00:04:10.469 align:start position:0% whole lot of external services and again this<00:04:08.889> is<00:04:09.040> not<00:04:09.069> to<00:04:09.220> pick<00:04:09.519> on<00:04:09.669> ether<00:04:09.940> scan<00:04:10.209> here 00:04:10.469 --> 00:04:10.479 align:start position:0% this is not to pick on ether scan here 00:04:10.479 --> 00:04:12.539 align:start position:0% this is not to pick on ether scan here and<00:04:10.690> adapt<00:04:11.019> is<00:04:11.620> vulnerable<00:04:12.129> to<00:04:12.190> the<00:04:12.340> same 00:04:12.539 --> 00:04:12.549 align:start position:0% and adapt is vulnerable to the same 00:04:12.549 --> 00:04:14.819 align:start position:0% and adapt is vulnerable to the same thing<00:04:12.849> it's<00:04:13.329> just<00:04:13.419> a<00:04:13.629> bit<00:04:13.780> clearer<00:04:14.409> to<00:04:14.680> use 00:04:14.819 --> 00:04:14.829 align:start position:0% thing it's just a bit clearer to use 00:04:14.829 --> 00:04:18.390 align:start position:0% thing it's just a bit clearer to use with<00:04:14.979> either<00:04:15.099> scan<00:04:15.599> and<00:04:16.599> ok<00:04:17.349> now<00:04:18.070> we<00:04:18.130> know<00:04:18.370> that 00:04:18.390 --> 00:04:18.400 align:start position:0% with either scan and ok now we know that 00:04:18.400 --> 00:04:20.250 align:start position:0% with either scan and ok now we know that there's<00:04:18.760> a<00:04:18.820> problem<00:04:19.030> but<00:04:19.599> what<00:04:19.750> can<00:04:19.930> we<00:04:20.049> do<00:04:20.139> to 00:04:20.250 --> 00:04:20.260 align:start position:0% there's a problem but what can we do to 00:04:20.260 --> 00:04:22.260 align:start position:0% there's a problem but what can we do to actually<00:04:20.349> fix<00:04:20.799> it<00:04:20.979> so<00:04:21.940> one<00:04:22.090> of<00:04:22.120> the 00:04:22.260 --> 00:04:22.270 align:start position:0% actually fix it so one of the 00:04:22.270 --> 00:04:24.839 align:start position:0% actually fix it so one of the possibilities<00:04:22.659> is<00:04:23.190> first<00:04:24.190> of<00:04:24.310> all<00:04:24.430> if<00:04:24.669> your 00:04:24.839 --> 00:04:24.849 align:start position:0% possibilities is first of all if your 00:04:24.849 --> 00:04:26.640 align:start position:0% possibilities is first of all if your provide<00:04:25.240> or<00:04:25.419> any<00:04:25.539> kind<00:04:25.780> of<00:04:25.840> that<00:04:26.080> poor<00:04:26.349> service 00:04:26.640 --> 00:04:26.650 align:start position:0% provide or any kind of that poor service 00:04:26.650 --> 00:04:27.930 align:start position:0% provide or any kind of that poor service provider 00:04:27.930 --> 00:04:27.940 align:start position:0% provider 00:04:27.940 --> 00:04:30.570 align:start position:0% provider first<00:04:28.389> stop<00:04:28.600> do<00:04:29.470> not<00:04:29.590> integrate<00:04:29.860> legacy<00:04:30.430> web 00:04:30.570 --> 00:04:30.580 align:start position:0% first stop do not integrate legacy web 00:04:30.580 --> 00:04:33.900 align:start position:0% first stop do not integrate legacy web 2.0<00:04:31.060> services<00:04:31.540> and<00:04:31.990> this<00:04:32.950> might<00:04:33.190> sound<00:04:33.580> like<00:04:33.850> a 00:04:33.900 --> 00:04:33.910 align:start position:0% 2.0 services and this might sound like a 00:04:33.910 --> 00:04:37.680 align:start position:0% 2.0 services and this might sound like a no-brainer<00:04:34.900> but<00:04:35.730> if<00:04:36.730> you<00:04:36.940> think<00:04:37.090> about<00:04:37.210> it<00:04:37.510> in 00:04:37.680 --> 00:04:37.690 align:start position:0% no-brainer but if you think about it in 00:04:37.690 --> 00:04:39.090 align:start position:0% no-brainer but if you think about it in either<00:04:37.840> scan<00:04:38.110> ether<00:04:38.440> scan<00:04:38.770> has<00:04:38.950> this 00:04:39.090 --> 00:04:39.100 align:start position:0% either scan ether scan has this 00:04:39.100 --> 00:04:41.520 align:start position:0% either scan ether scan has this possibility<00:04:39.700> to<00:04:39.820> comment<00:04:40.240> on<00:04:40.360> account<00:04:40.690> is 00:04:41.520 --> 00:04:41.530 align:start position:0% possibility to comment on account is 00:04:41.530 --> 00:04:44.340 align:start position:0% possibility to comment on account is that<00:04:41.760> genuinely<00:04:42.760> a<00:04:42.910> useful<00:04:43.360> feature<00:04:43.570> for<00:04:43.930> a 00:04:44.340 --> 00:04:44.350 align:start position:0% that genuinely a useful feature for a 00:04:44.350 --> 00:04:46.860 align:start position:0% that genuinely a useful feature for a block<00:04:44.560> Explorer<00:04:45.450> but<00:04:46.450> if<00:04:46.540> you<00:04:46.660> look<00:04:46.840> through 00:04:46.860 --> 00:04:46.870 align:start position:0% block Explorer but if you look through 00:04:46.870 --> 00:04:49.440 align:start position:0% block Explorer but if you look through the<00:04:47.139> comments<00:04:47.410> it's<00:04:47.850> pretty<00:04:48.850> noisy<00:04:49.090> it's 00:04:49.440 --> 00:04:49.450 align:start position:0% the comments it's pretty noisy it's 00:04:49.450 --> 00:04:51.210 align:start position:0% the comments it's pretty noisy it's pretty<00:04:49.660> spammy<00:04:49.990> there<00:04:50.560> are<00:04:50.650> a<00:04:50.710> few<00:04:50.860> scams 00:04:51.210 --> 00:04:51.220 align:start position:0% pretty spammy there are a few scams 00:04:51.220 --> 00:04:54.150 align:start position:0% pretty spammy there are a few scams going<00:04:51.580> around<00:04:51.820> on<00:04:52.000> and<00:04:52.360> off<00:04:52.480> so<00:04:52.780> it's<00:04:52.930> not<00:04:53.160> not 00:04:54.150 --> 00:04:54.160 align:start position:0% going around on and off so it's not not 00:04:54.160 --> 00:04:57.240 align:start position:0% going around on and off so it's not not the<00:04:54.340> best<00:04:54.880> feature<00:04:55.680> so<00:04:56.680> maybe<00:04:56.980> it<00:04:57.100> would<00:04:57.220> be 00:04:57.240 --> 00:04:57.250 align:start position:0% the best feature so maybe it would be 00:04:57.250 --> 00:04:59.970 align:start position:0% the best feature so maybe it would be worth<00:04:57.370> to<00:04:57.700> cut<00:04:57.880> it<00:04:58.030> out<00:04:58.180> the<00:04:58.620> second<00:04:59.620> thing<00:04:59.830> is 00:04:59.970 --> 00:04:59.980 align:start position:0% worth to cut it out the second thing is 00:04:59.980 --> 00:05:02.640 align:start position:0% worth to cut it out the second thing is that<00:05:00.010> if<00:05:00.490> you<00:05:00.780> even<00:05:01.780> if<00:05:01.990> you<00:05:02.080> don't<00:05:02.230> integrate 00:05:02.640 --> 00:05:02.650 align:start position:0% that if you even if you don't integrate 00:05:02.650 --> 00:05:04.500 align:start position:0% that if you even if you don't integrate external<00:05:03.340> services<00:05:03.760> or<00:05:03.880> try<00:05:04.030> to<00:05:04.060> keep<00:05:04.270> it<00:05:04.450> to 00:05:04.500 --> 00:05:04.510 align:start position:0% external services or try to keep it to 00:05:04.510 --> 00:05:06.090 align:start position:0% external services or try to keep it to the<00:05:04.600> minimum<00:05:04.990> you<00:05:05.380> should<00:05:05.410> always<00:05:05.650> wonder 00:05:06.090 --> 00:05:06.100 align:start position:0% the minimum you should always wonder 00:05:06.100 --> 00:05:07.620 align:start position:0% the minimum you should always wonder whether<00:05:06.310> it<00:05:06.550> is<00:05:06.700> worthwhile<00:05:06.940> to<00:05:07.300> reveal 00:05:07.620 --> 00:05:07.630 align:start position:0% whether it is worthwhile to reveal 00:05:07.630 --> 00:05:09.720 align:start position:0% whether it is worthwhile to reveal identifying<00:05:08.530> information<00:05:09.070> in<00:05:09.160> the<00:05:09.340> URL<00:05:09.700> you 00:05:09.720 --> 00:05:09.730 align:start position:0% identifying information in the URL you 00:05:09.730 --> 00:05:12.060 align:start position:0% identifying information in the URL you should<00:05:09.820> always<00:05:10.060> consider<00:05:10.570> that<00:05:10.740> anyone<00:05:11.740> can 00:05:12.060 --> 00:05:12.070 align:start position:0% should always consider that anyone can 00:05:12.070 --> 00:05:13.890 align:start position:0% should always consider that anyone can access<00:05:12.310> the<00:05:12.700> URL<00:05:12.850> let's<00:05:13.300> suppose<00:05:13.540> any<00:05:13.720> if 00:05:13.890 --> 00:05:13.900 align:start position:0% access the URL let's suppose any if 00:05:13.900 --> 00:05:15.840 align:start position:0% access the URL let's suppose any if anyone<00:05:14.440> can<00:05:14.590> access<00:05:14.710> the<00:05:14.950> IP<00:05:15.100> to<00:05:15.400> URL<00:05:15.669> mapping 00:05:15.840 --> 00:05:15.850 align:start position:0% anyone can access the IP to URL mapping 00:05:15.850 --> 00:05:18.090 align:start position:0% anyone can access the IP to URL mapping do<00:05:16.270> you<00:05:16.360> want<00:05:16.540> your<00:05:16.750> customers<00:05:17.260> data<00:05:17.680> to<00:05:17.980> be 00:05:18.090 --> 00:05:18.100 align:start position:0% do you want your customers data to be 00:05:18.100 --> 00:05:21.120 align:start position:0% do you want your customers data to be leaked<00:05:18.340> that<00:05:18.640> way<00:05:18.820> or<00:05:18.940> not<00:05:19.260> maybe<00:05:20.260> for<00:05:20.919> a<00:05:20.950> block 00:05:21.120 --> 00:05:21.130 align:start position:0% leaked that way or not maybe for a block 00:05:21.130 --> 00:05:22.860 align:start position:0% leaked that way or not maybe for a block Explorer<00:05:21.520> maybe<00:05:21.880> this<00:05:22.150> is<00:05:22.360> cannot<00:05:22.720> be 00:05:22.860 --> 00:05:22.870 align:start position:0% Explorer maybe this is cannot be 00:05:22.870 --> 00:05:25.290 align:start position:0% Explorer maybe this is cannot be circumvented<00:05:23.530> but<00:05:24.250> for<00:05:24.430> other<00:05:24.640> that<00:05:24.880> maybe<00:05:25.150> it 00:05:25.290 --> 00:05:25.300 align:start position:0% circumvented but for other that maybe it 00:05:25.300 --> 00:05:27.810 align:start position:0% circumvented but for other that maybe it should<00:05:25.510> be<00:05:25.660> and<00:05:26.290> last<00:05:26.590> of<00:05:26.740> last<00:05:27.310> but<00:05:27.490> not<00:05:27.580> least 00:05:27.810 --> 00:05:27.820 align:start position:0% should be and last of last but not least 00:05:27.820 --> 00:05:30.690 align:start position:0% should be and last of last but not least please<00:05:28.510> do<00:05:28.870> use<00:05:29.110> HTTP<00:05:29.800> referer<00:05:29.979> policy 00:05:30.690 --> 00:05:30.700 align:start position:0% please do use HTTP referer policy 00:05:30.700 --> 00:05:31.320 align:start position:0% please do use HTTP referer policy restrictions 00:05:31.320 --> 00:05:31.330 align:start position:0% restrictions 00:05:31.330 --> 00:05:34.260 align:start position:0% restrictions I<00:05:31.450> for<00:05:32.290> example<00:05:32.320> ethers<00:05:32.919> can<00:05:33.130> use<00:05:33.310> as<00:05:33.460> a<00:05:33.490> policy 00:05:34.260 --> 00:05:34.270 align:start position:0% I for example ethers can use as a policy 00:05:34.270 --> 00:05:37.950 align:start position:0% I for example ethers can use as a policy whereby<00:05:34.540> HTTP<00:05:35.410> to<00:05:35.710> HTTPS<00:05:36.720> forbid<00:05:37.720> the 00:05:37.950 --> 00:05:37.960 align:start position:0% whereby HTTP to HTTPS forbid the 00:05:37.960 --> 00:05:39.540 align:start position:0% whereby HTTP to HTTPS forbid the referral<00:05:38.350> header<00:05:38.590> from<00:05:38.800> being<00:05:39.040> forwarded 00:05:39.540 --> 00:05:39.550 align:start position:0% referral header from being forwarded 00:05:39.550 --> 00:05:41.850 align:start position:0% referral header from being forwarded there<00:05:40.180> are<00:05:40.570> much<00:05:40.690> more<00:05:40.720> stricter<00:05:41.290> policies 00:05:41.850 --> 00:05:41.860 align:start position:0% there are much more stricter policies 00:05:41.860 --> 00:05:43.590 align:start position:0% there are much more stricter policies which<00:05:42.040> actually<00:05:42.640> forbid<00:05:42.970> everything<00:05:43.240> being 00:05:43.590 --> 00:05:43.600 align:start position:0% which actually forbid everything being 00:05:43.600 --> 00:05:47.730 align:start position:0% which actually forbid everything being forwarded<00:05:44.940> ok<00:05:45.940> we<00:05:46.570> can<00:05:46.900> do<00:05:47.169> that<00:05:47.350> and<00:05:47.500> ether 00:05:47.730 --> 00:05:47.740 align:start position:0% forwarded ok we can do that and ether 00:05:47.740 --> 00:05:49.770 align:start position:0% forwarded ok we can do that and ether scan<00:05:47.979> is<00:05:48.070> actually<00:05:48.490> they<00:05:48.640> are<00:05:48.760> trying<00:05:49.150> to<00:05:49.539> fix 00:05:49.770 --> 00:05:49.780 align:start position:0% scan is actually they are trying to fix 00:05:49.780 --> 00:05:51.719 align:start position:0% scan is actually they are trying to fix these<00:05:49.990> issues<00:05:50.350> original<00:05:51.220> ether<00:05:51.460> scan 00:05:51.719 --> 00:05:51.729 align:start position:0% these issues original ether scan 00:05:51.729 --> 00:05:53.700 align:start position:0% these issues original ether scan integrated<00:05:52.479> an<00:05:52.570> external<00:05:52.990> ad<00:05:53.140> network<00:05:53.530> that 00:05:53.700 --> 00:05:53.710 align:start position:0% integrated an external ad network that 00:05:53.710 --> 00:05:55.200 align:start position:0% integrated an external ad network that they<00:05:53.800> replaced<00:05:54.190> an<00:05:54.310> eternal<00:05:54.760> with<00:05:55.090> an 00:05:55.200 --> 00:05:55.210 align:start position:0% they replaced an eternal with an 00:05:55.210 --> 00:05:57.210 align:start position:0% they replaced an eternal with an internal<00:05:55.539> one<00:05:55.780> originally<00:05:56.289> now<00:05:56.770> currently 00:05:57.210 --> 00:05:57.220 align:start position:0% internal one originally now currently 00:05:57.220 --> 00:05:59.250 align:start position:0% internal one originally now currently they<00:05:57.340> are<00:05:57.370> using<00:05:57.820> Google<00:05:58.510> Analytics<00:05:58.990> but<00:05:59.140> they 00:05:59.250 --> 00:05:59.260 align:start position:0% they are using Google Analytics but they 00:05:59.260 --> 00:06:01.110 align:start position:0% they are using Google Analytics but they want<00:05:59.440> to<00:05:59.530> replace<00:05:59.740> that<00:06:00.070> so<00:06:00.729> they<00:06:00.880> are<00:06:00.970> really 00:06:01.110 --> 00:06:01.120 align:start position:0% want to replace that so they are really 00:06:01.120 --> 00:06:04.140 align:start position:0% want to replace that so they are really open<00:06:01.600> to<00:06:01.630> fixing<00:06:02.320> issues<00:06:02.760> however<00:06:03.760> the<00:06:04.000> issue 00:06:04.140 --> 00:06:04.150 align:start position:0% open to fixing issues however the issue 00:06:04.150 --> 00:06:08.279 align:start position:0% open to fixing issues however the issue is<00:06:04.510> that<00:06:06.570> providers<00:06:07.570> fixing<00:06:07.960> it<00:06:08.050> is<00:06:08.169> not 00:06:08.279 --> 00:06:08.289 align:start position:0% is that providers fixing it is not 00:06:08.289 --> 00:06:09.719 align:start position:0% is that providers fixing it is not really<00:06:08.530> enough<00:06:08.770> because<00:06:09.070> we<00:06:09.160> can<00:06:09.310> get<00:06:09.460> ether 00:06:09.719 --> 00:06:09.729 align:start position:0% really enough because we can get ether 00:06:09.729 --> 00:06:12.540 align:start position:0% really enough because we can get ether scan<00:06:10.060> to<00:06:10.479> fix<00:06:10.690> it<00:06:10.840> but<00:06:11.440> can<00:06:11.740> we<00:06:11.890> get<00:06:12.070> random 00:06:12.540 --> 00:06:12.550 align:start position:0% scan to fix it but can we get random 00:06:12.550 --> 00:06:15.180 align:start position:0% scan to fix it but can we get random that<00:06:12.729> number<00:06:13.210> 2000<00:06:14.110> to<00:06:14.200> fix<00:06:14.380> it<00:06:14.560> probably<00:06:15.010> not 00:06:15.180 --> 00:06:15.190 align:start position:0% that number 2000 to fix it probably not 00:06:15.190 --> 00:06:17.460 align:start position:0% that number 2000 to fix it probably not so<00:06:15.820> users<00:06:16.150> need<00:06:16.330> to<00:06:16.450> protect<00:06:16.780> themselves<00:06:16.930> too 00:06:17.460 --> 00:06:17.470 align:start position:0% so users need to protect themselves too 00:06:17.470 --> 00:06:19.920 align:start position:0% so users need to protect themselves too and<00:06:17.740> the<00:06:18.700> obvious<00:06:18.970> choices<00:06:19.210> here<00:06:19.539> are<00:06:19.570> browser 00:06:19.920 --> 00:06:19.930 align:start position:0% and the obvious choices here are browser 00:06:19.930 --> 00:06:21.540 align:start position:0% and the obvious choices here are browser extensions<00:06:20.620> that<00:06:20.800> block<00:06:21.130> all<00:06:21.310> kinds<00:06:21.520> of 00:06:21.540 --> 00:06:21.550 align:start position:0% extensions that block all kinds of 00:06:21.550 --> 00:06:23.490 align:start position:0% extensions that block all kinds of checkers<00:06:22.030> or<00:06:22.210> if<00:06:22.630> you're<00:06:22.750> on<00:06:22.870> a<00:06:22.900> mobile<00:06:23.080> device 00:06:23.490 --> 00:06:23.500 align:start position:0% checkers or if you're on a mobile device 00:06:23.500 --> 00:06:25.320 align:start position:0% checkers or if you're on a mobile device you<00:06:23.560> could<00:06:23.950> for<00:06:24.550> example<00:06:24.580> use<00:06:24.910> a<00:06:25.000> brave 00:06:25.320 --> 00:06:25.330 align:start position:0% you could for example use a brave 00:06:25.330 --> 00:06:28.230 align:start position:0% you could for example use a brave browser<00:06:25.740> but<00:06:26.740> these<00:06:26.950> can<00:06:27.280> only<00:06:27.430> block<00:06:27.700> so<00:06:28.000> many 00:06:28.230 --> 00:06:28.240 align:start position:0% browser but these can only block so many 00:06:28.240 --> 00:06:30.750 align:start position:0% browser but these can only block so many things<00:06:28.710> for<00:06:29.710> example<00:06:30.039> if<00:06:30.100> I<00:06:30.190> have<00:06:30.340> you<00:06:30.490> to<00:06:30.669> be 00:06:30.750 --> 00:06:30.760 align:start position:0% things for example if I have you to be 00:06:30.760 --> 00:06:34.020 align:start position:0% things for example if I have you to be integrated<00:06:31.360> no<00:06:31.960> none<00:06:32.320> of<00:06:32.350> the<00:06:32.850> extensions<00:06:33.850> or 00:06:34.020 --> 00:06:34.030 align:start position:0% integrated no none of the extensions or 00:06:34.030 --> 00:06:36.420 align:start position:0% integrated no none of the extensions or browsers<00:06:34.450> will<00:06:34.660> block<00:06:34.930> YouTube<00:06:35.190> which<00:06:36.190> gets 00:06:36.420 --> 00:06:36.430 align:start position:0% browsers will block YouTube which gets 00:06:36.430 --> 00:06:38.399 align:start position:0% browsers will block YouTube which gets us<00:06:36.520> to<00:06:36.610> the<00:06:36.700> second<00:06:37.060> point<00:06:37.450> let's<00:06:38.260> let's 00:06:38.399 --> 00:06:38.409 align:start position:0% us to the second point let's let's 00:06:38.409 --> 00:06:40.080 align:start position:0% us to the second point let's let's suppose<00:06:38.680> we<00:06:38.919> managed<00:06:39.220> to<00:06:39.250> block<00:06:39.580> all<00:06:39.849> the 00:06:40.080 --> 00:06:40.090 align:start position:0% suppose we managed to block all the 00:06:40.090 --> 00:06:41.210 align:start position:0% suppose we managed to block all the external<00:06:40.270> service 00:06:41.210 --> 00:06:41.220 align:start position:0% external service 00:06:41.220 --> 00:06:44.780 align:start position:0% external service even<00:06:42.060> YouTube's<00:06:42.360> not<00:06:43.020> supposed<00:06:43.380> to<00:06:43.610> handle<00:06:44.610> it 00:06:44.780 --> 00:06:44.790 align:start position:0% even YouTube's not supposed to handle it 00:06:44.790 --> 00:06:47.390 align:start position:0% even YouTube's not supposed to handle it HTTP<00:06:45.300> refers<00:06:45.540> directly<00:06:45.750> and<00:06:46.200> everything<00:06:46.560> even 00:06:47.390 --> 00:06:47.400 align:start position:0% HTTP refers directly and everything even 00:06:47.400 --> 00:06:50.960 align:start position:0% HTTP refers directly and everything even then<00:06:47.610> we<00:06:47.790> have<00:06:47.970> this<00:06:48.180> fairly<00:06:48.900> complex<00:06:49.850> flow<00:06:50.850> of 00:06:50.960 --> 00:06:50.970 align:start position:0% then we have this fairly complex flow of 00:06:50.970 --> 00:06:52.790 align:start position:0% then we have this fairly complex flow of information<00:06:51.150> whereby<00:06:51.900> whenever<00:06:52.170> we<00:06:52.410> want<00:06:52.740> to 00:06:52.790 --> 00:06:52.800 align:start position:0% information whereby whenever we want to 00:06:52.800 --> 00:06:54.620 align:start position:0% information whereby whenever we want to access<00:06:53.010> anything<00:06:53.490> related<00:06:54.180> to<00:06:54.210> our<00:06:54.390> data 00:06:54.620 --> 00:06:54.630 align:start position:0% access anything related to our data 00:06:54.630 --> 00:06:57.650 align:start position:0% access anything related to our data either<00:06:55.500> by<00:06:55.740> meta<00:06:56.010> mask<00:06:56.280> adapt<00:06:56.940> or<00:06:57.270> via<00:06:57.510> my 00:06:57.650 --> 00:06:57.660 align:start position:0% either by meta mask adapt or via my 00:06:57.660 --> 00:07:00.770 align:start position:0% either by meta mask adapt or via my crypto<00:06:58.170> or<00:06:58.740> my<00:06:58.920> sir<00:06:59.160> wallet<00:06:59.460> we<00:06:59.610> still<00:06:59.880> reach 00:07:00.770 --> 00:07:00.780 align:start position:0% crypto or my sir wallet we still reach 00:07:00.780 --> 00:07:03.080 align:start position:0% crypto or my sir wallet we still reach out<00:07:01.020> to<00:07:01.170> either<00:07:01.290> scan<00:07:01.710> or<00:07:01.980> infra<00:07:02.430> or 00:07:03.080 --> 00:07:03.090 align:start position:0% out to either scan or infra or 00:07:03.090 --> 00:07:05.060 align:start position:0% out to either scan or infra or CloudFlare<00:07:03.750> in<00:07:03.870> between<00:07:04.140> and<00:07:04.380> what<00:07:04.950> this 00:07:05.060 --> 00:07:05.070 align:start position:0% CloudFlare in between and what this 00:07:05.070 --> 00:07:07.190 align:start position:0% CloudFlare in between and what this means<00:07:05.280> is<00:07:05.520> that<00:07:05.580> ether<00:07:06.150> scan<00:07:06.390> in<00:07:06.540> front<00:07:06.900> clouds 00:07:07.190 --> 00:07:07.200 align:start position:0% means is that ether scan in front clouds 00:07:07.200 --> 00:07:08.990 align:start position:0% means is that ether scan in front clouds there<00:07:07.470> still<00:07:07.770> have<00:07:08.010> access<00:07:08.220> to<00:07:08.460> the<00:07:08.550> exact 00:07:08.990 --> 00:07:09.000 align:start position:0% there still have access to the exact 00:07:09.000 --> 00:07:11.000 align:start position:0% there still have access to the exact same<00:07:09.240> information<00:07:09.450> the<00:07:10.350> exact<00:07:10.620> same<00:07:10.770> IP 00:07:11.000 --> 00:07:11.010 align:start position:0% same information the exact same IP 00:07:11.010 --> 00:07:14.090 align:start position:0% same information the exact same IP address<00:07:11.430> to<00:07:11.670> a<00:07:12.630> theorem<00:07:13.200> account<00:07:13.500> mappings 00:07:14.090 --> 00:07:14.100 align:start position:0% address to a theorem account mappings 00:07:14.100 --> 00:07:15.920 align:start position:0% address to a theorem account mappings now<00:07:14.280> you<00:07:14.340> may<00:07:14.700> trust<00:07:15.060> them<00:07:15.360> or<00:07:15.480> you<00:07:15.600> may<00:07:15.750> not 00:07:15.920 --> 00:07:15.930 align:start position:0% now you may trust them or you may not 00:07:15.930 --> 00:07:18.560 align:start position:0% now you may trust them or you may not trust<00:07:16.170> them<00:07:16.380> that<00:07:16.530> is<00:07:16.620> up<00:07:16.770> to<00:07:16.800> you<00:07:17.330> it's<00:07:18.330> an 00:07:18.560 --> 00:07:18.570 align:start position:0% trust them that is up to you it's an 00:07:18.570 --> 00:07:21.140 align:start position:0% trust them that is up to you it's an issue<00:07:18.690> and<00:07:19.340> unfortunately<00:07:20.340> the<00:07:20.550> only<00:07:20.580> current 00:07:21.140 --> 00:07:21.150 align:start position:0% issue and unfortunately the only current 00:07:21.150 --> 00:07:23.680 align:start position:0% issue and unfortunately the only current solution<00:07:21.540> that<00:07:21.660> you<00:07:21.780> can<00:07:21.810> do<00:07:22.260> is<00:07:22.530> if<00:07:22.800> use<00:07:23.040> an 00:07:23.680 --> 00:07:23.690 align:start position:0% solution that you can do is if use an 00:07:23.690 --> 00:07:26.090 align:start position:0% solution that you can do is if use an anonymizer<00:07:24.690> service<00:07:25.260> kind<00:07:25.500> of<00:07:25.650> like<00:07:25.800> tor 00:07:26.090 --> 00:07:26.100 align:start position:0% anonymizer service kind of like tor 00:07:26.100 --> 00:07:28.220 align:start position:0% anonymizer service kind of like tor which<00:07:26.880> is<00:07:27.030> willing<00:07:27.270> to<00:07:27.300> hide<00:07:27.600> your<00:07:27.780> IP<00:07:27.930> address 00:07:28.220 --> 00:07:28.230 align:start position:0% which is willing to hide your IP address 00:07:28.230 --> 00:07:30.920 align:start position:0% which is willing to hide your IP address behind<00:07:28.740> their<00:07:29.010> mixing<00:07:29.340> Network<00:07:29.730> but<00:07:30.600> kind<00:07:30.840> of 00:07:30.920 --> 00:07:30.930 align:start position:0% behind their mixing Network but kind of 00:07:30.930 --> 00:07:34.660 align:start position:0% behind their mixing Network but kind of that's<00:07:31.260> your<00:07:31.560> best<00:07:31.830> chance<00:07:31.980> currently<00:07:33.200> so 00:07:34.660 --> 00:07:34.670 align:start position:0% that's your best chance currently so 00:07:34.670 --> 00:07:37.700 align:start position:0% that's your best chance currently so bottom<00:07:35.670> line<00:07:35.820> is<00:07:36.030> using<00:07:36.510> restful<00:07:37.080> services<00:07:37.560> is 00:07:37.700 --> 00:07:37.710 align:start position:0% bottom line is using restful services is 00:07:37.710 --> 00:07:40.070 align:start position:0% bottom line is using restful services is not<00:07:37.890> the<00:07:38.040> best<00:07:38.340> thing<00:07:38.700> so<00:07:39.360> and<00:07:39.600> if<00:07:39.690> you<00:07:39.810> think 00:07:40.070 --> 00:07:40.080 align:start position:0% not the best thing so and if you think 00:07:40.080 --> 00:07:42.920 align:start position:0% not the best thing so and if you think now<00:07:40.290> my<00:07:40.730> my<00:07:41.730> conclusion<00:07:42.240> would<00:07:42.390> be<00:07:42.450> to<00:07:42.750> please 00:07:42.920 --> 00:07:42.930 align:start position:0% now my my conclusion would be to please 00:07:42.930 --> 00:07:46.730 align:start position:0% now my my conclusion would be to please use<00:07:43.260> light<00:07:43.650> clients<00:07:44.630> yeah<00:07:45.630> that's<00:07:45.960> going<00:07:46.530> to 00:07:46.730 --> 00:07:46.740 align:start position:0% use light clients yeah that's going to 00:07:46.740 --> 00:07:51.080 align:start position:0% use light clients yeah that's going to get<00:07:46.890> even<00:07:47.160> more<00:07:47.190> messy<00:07:48.200> so<00:07:49.640> let's<00:07:50.640> dig<00:07:50.880> into 00:07:51.080 --> 00:07:51.090 align:start position:0% get even more messy so let's dig into 00:07:51.090 --> 00:07:51.800 align:start position:0% get even more messy so let's dig into life<00:07:51.270> crisis 00:07:51.800 --> 00:07:51.810 align:start position:0% life crisis 00:07:51.810 --> 00:07:53.270 align:start position:0% life crisis forget<00:07:52.230> trustful<00:07:52.620> services<00:07:53.010> all<00:07:53.130> together 00:07:53.270 --> 00:07:53.280 align:start position:0% forget trustful services all together 00:07:53.280 --> 00:07:55.730 align:start position:0% forget trustful services all together all<00:07:53.550> kinds<00:07:53.760> of<00:07:53.820> depths<00:07:54.150> and<00:07:54.270> web<00:07:54.420> stuff<00:07:54.660> a<00:07:54.930> live 00:07:55.730 --> 00:07:55.740 align:start position:0% all kinds of depths and web stuff a live 00:07:55.740 --> 00:07:58.280 align:start position:0% all kinds of depths and web stuff a live clients<00:07:56.100> supposed<00:07:56.430> to<00:07:56.550> be<00:07:56.700> the<00:07:57.030> way<00:07:57.750> to<00:07:57.780> access 00:07:58.280 --> 00:07:58.290 align:start position:0% clients supposed to be the way to access 00:07:58.290 --> 00:07:59.900 align:start position:0% clients supposed to be the way to access aetherium<00:07:58.800> so<00:07:58.980> that<00:07:59.130> you<00:07:59.310> don't<00:07:59.490> have<00:07:59.670> to<00:07:59.790> run 00:07:59.900 --> 00:07:59.910 align:start position:0% aetherium so that you don't have to run 00:07:59.910 --> 00:08:01.790 align:start position:0% aetherium so that you don't have to run a<00:07:59.940> full<00:08:00.180> node<00:08:00.390> you<00:08:00.540> can<00:08:00.720> just<00:08:00.930> run<00:08:01.200> this<00:08:01.350> really 00:08:01.790 --> 00:08:01.800 align:start position:0% a full node you can just run this really 00:08:01.800 --> 00:08:04.100 align:start position:0% a full node you can just run this really nice<00:08:01.950> little<00:08:02.370> thing<00:08:02.670> which<00:08:03.270> is<00:08:03.510> essentially 00:08:04.100 --> 00:08:04.110 align:start position:0% nice little thing which is essentially 00:08:04.110 --> 00:08:06.170 align:start position:0% nice little thing which is essentially kind<00:08:04.680> of<00:08:04.770> feels<00:08:05.010> like<00:08:05.160> a<00:08:05.280> full<00:08:05.580> node<00:08:05.790> just<00:08:05.970> it's 00:08:06.170 --> 00:08:06.180 align:start position:0% kind of feels like a full node just it's 00:08:06.180 --> 00:08:10.340 align:start position:0% kind of feels like a full node just it's not<00:08:06.330> and<00:08:07.010> it<00:08:08.010> has<00:08:08.220> actually<00:08:08.790> two<00:08:09.350> significant 00:08:10.340 --> 00:08:10.350 align:start position:0% not and it has actually two significant 00:08:10.350 --> 00:08:12.530 align:start position:0% not and it has actually two significant problems<00:08:10.710> one<00:08:11.220> of<00:08:11.340> them<00:08:11.520> is<00:08:11.820> in<00:08:12.180> the<00:08:12.210> discovery 00:08:12.530 --> 00:08:12.540 align:start position:0% problems one of them is in the discovery 00:08:12.540 --> 00:08:15.890 align:start position:0% problems one of them is in the discovery protocol<00:08:14.030> I'm<00:08:15.030> not<00:08:15.240> sure<00:08:15.360> how<00:08:15.480> many<00:08:15.540> of<00:08:15.720> you 00:08:15.890 --> 00:08:15.900 align:start position:0% protocol I'm not sure how many of you 00:08:15.900 --> 00:08:17.600 align:start position:0% protocol I'm not sure how many of you are<00:08:16.050> aware<00:08:16.170> of<00:08:16.320> how<00:08:16.590> the<00:08:16.650> discovery<00:08:17.220> protocol 00:08:17.600 --> 00:08:17.610 align:start position:0% are aware of how the discovery protocol 00:08:17.610 --> 00:08:20.090 align:start position:0% are aware of how the discovery protocol discovery<00:08:18.000> layer<00:08:18.150> works<00:08:18.480> in<00:08:18.630> aetherium<00:08:19.110> or<00:08:19.890> in 00:08:20.090 --> 00:08:20.100 align:start position:0% discovery layer works in aetherium or in 00:08:20.100 --> 00:08:22.190 align:start position:0% discovery layer works in aetherium or in peer-to-peer<00:08:20.310> networks<00:08:20.820> in<00:08:20.970> general<00:08:21.000> but<00:08:21.960> in 00:08:22.190 --> 00:08:22.200 align:start position:0% peer-to-peer networks in general but in 00:08:22.200 --> 00:08:24.050 align:start position:0% peer-to-peer networks in general but in short<00:08:22.470> you<00:08:23.160> have<00:08:23.190> a<00:08:23.340> few<00:08:23.640> boot<00:08:23.820> notes 00:08:24.050 --> 00:08:24.060 align:start position:0% short you have a few boot notes 00:08:24.060 --> 00:08:27.200 align:start position:0% short you have a few boot notes hard-coded<00:08:24.990> into<00:08:25.140> the<00:08:25.350> client<00:08:26.190> when<00:08:26.880> you<00:08:27.000> boot 00:08:27.200 --> 00:08:27.210 align:start position:0% hard-coded into the client when you boot 00:08:27.210 --> 00:08:29.480 align:start position:0% hard-coded into the client when you boot up<00:08:27.330> your<00:08:27.390> node<00:08:27.780> it<00:08:28.140> reaches<00:08:28.770> out<00:08:28.920> to<00:08:28.950> a<00:08:29.190> few 00:08:29.480 --> 00:08:29.490 align:start position:0% up your node it reaches out to a few 00:08:29.490 --> 00:08:31.670 align:start position:0% up your node it reaches out to a few seed<00:08:29.790> nodes<00:08:30.030> gets<00:08:30.630> a<00:08:30.810> whole<00:08:31.050> bunch<00:08:31.320> of<00:08:31.440> peers 00:08:31.670 --> 00:08:31.680 align:start position:0% seed nodes gets a whole bunch of peers 00:08:31.680 --> 00:08:33.170 align:start position:0% seed nodes gets a whole bunch of peers in<00:08:31.860> the<00:08:31.920> network<00:08:31.950> and<00:08:32.520> then<00:08:32.700> boom<00:08:32.970> you're 00:08:33.170 --> 00:08:33.180 align:start position:0% in the network and then boom you're 00:08:33.180 --> 00:08:35.480 align:start position:0% in the network and then boom you're connected<00:08:33.660> now<00:08:34.620> in<00:08:34.860> reality<00:08:35.340> what<00:08:35.460> happens 00:08:35.480 --> 00:08:35.490 align:start position:0% connected now in reality what happens 00:08:35.490 --> 00:08:37.969 align:start position:0% connected now in reality what happens under<00:08:35.910> the<00:08:36.150> hood<00:08:36.360> is<00:08:36.570> that<00:08:37.290> these<00:08:37.530> boot<00:08:37.770> nodes 00:08:37.969 --> 00:08:37.979 align:start position:0% under the hood is that these boot nodes 00:08:37.979 --> 00:08:39.920 align:start position:0% under the hood is that these boot nodes aren't<00:08:38.220> some<00:08:38.520> magical<00:08:38.970> special<00:08:39.210> databases 00:08:39.920 --> 00:08:39.930 align:start position:0% aren't some magical special databases 00:08:39.930 --> 00:08:41.600 align:start position:0% aren't some magical special databases that<00:08:40.080> track<00:08:40.350> the<00:08:40.530> entire<00:08:40.800> network<00:08:41.010> rather 00:08:41.600 --> 00:08:41.610 align:start position:0% that track the entire network rather 00:08:41.610 --> 00:08:43.880 align:start position:0% that track the entire network rather they<00:08:42.000> the<00:08:42.630> network<00:08:42.990> itself<00:08:43.350> boot<00:08:43.680> nodes 00:08:43.880 --> 00:08:43.890 align:start position:0% they the network itself boot nodes 00:08:43.890 --> 00:08:45.170 align:start position:0% they the network itself boot nodes included<00:08:44.370> and<00:08:44.550> all<00:08:44.640> the<00:08:44.730> other<00:08:44.880> peers 00:08:45.170 --> 00:08:45.180 align:start position:0% included and all the other peers 00:08:45.180 --> 00:08:48.260 align:start position:0% included and all the other peers included<00:08:45.720> they<00:08:46.260> maintain<00:08:46.880> so-called<00:08:47.880> routing 00:08:48.260 --> 00:08:48.270 align:start position:0% included they maintain so-called routing 00:08:48.270 --> 00:08:50.990 align:start position:0% included they maintain so-called routing table<00:08:48.600> or<00:08:48.720> academia<00:08:49.050> DHT<00:08:49.740> which<00:08:49.920> is<00:08:50.640> kind<00:08:50.820> of<00:08:50.880> a 00:08:50.990 --> 00:08:51.000 align:start position:0% table or academia DHT which is kind of a 00:08:51.000 --> 00:08:53.630 align:start position:0% table or academia DHT which is kind of a fancy<00:08:51.180> way<00:08:51.450> of<00:08:51.570> putting<00:08:51.870> that<00:08:52.020> everyone<00:08:52.530> knows 00:08:53.630 --> 00:08:53.640 align:start position:0% fancy way of putting that everyone knows 00:08:53.640 --> 00:08:55.940 align:start position:0% fancy way of putting that everyone knows little<00:08:53.970> piece<00:08:54.300> about<00:08:54.960> the<00:08:55.140> network<00:08:55.500> so<00:08:55.680> nobody 00:08:55.940 --> 00:08:55.950 align:start position:0% little piece about the network so nobody 00:08:55.950 --> 00:08:57.830 align:start position:0% little piece about the network so nobody knows<00:08:56.580> the<00:08:56.760> entire<00:08:56.970> network<00:08:57.420> but<00:08:57.570> we<00:08:57.690> know 00:08:57.830 --> 00:08:57.840 align:start position:0% knows the entire network but we know 00:08:57.840 --> 00:09:00.020 align:start position:0% knows the entire network but we know little<00:08:58.080> pieces<00:08:58.380> of<00:08:58.590> it<00:08:58.740> and<00:08:58.860> if<00:08:59.400> you<00:08:59.520> reach<00:08:59.850> out 00:09:00.020 --> 00:09:00.030 align:start position:0% little pieces of it and if you reach out 00:09:00.030 --> 00:09:01.850 align:start position:0% little pieces of it and if you reach out to<00:09:00.090> enough<00:09:00.390> of<00:09:00.510> them<00:09:00.720> then<00:09:00.930> eventually<00:09:01.560> you 00:09:01.850 --> 00:09:01.860 align:start position:0% to enough of them then eventually you 00:09:01.860 --> 00:09:04.910 align:start position:0% to enough of them then eventually you can<00:09:02.070> discover<00:09:02.430> and<00:09:02.730> you<00:09:02.820> can<00:09:03.890> you<00:09:04.890> can 00:09:04.910 --> 00:09:04.920 align:start position:0% can discover and you can you can 00:09:04.920 --> 00:09:06.740 align:start position:0% can discover and you can you can discover<00:09:05.310> enough<00:09:05.580> nodes<00:09:05.850> to<00:09:06.090> have<00:09:06.540> good 00:09:06.740 --> 00:09:06.750 align:start position:0% discover enough nodes to have good 00:09:06.750 --> 00:09:10.760 align:start position:0% discover enough nodes to have good connections<00:09:07.320> and<00:09:08.630> and<00:09:09.630> have<00:09:09.780> a<00:09:09.840> stable<00:09:10.110> stable 00:09:10.760 --> 00:09:10.770 align:start position:0% connections and and have a stable stable 00:09:10.770 --> 00:09:12.980 align:start position:0% connections and and have a stable stable connectivity<00:09:11.370> test<00:09:11.520> essentially<00:09:12.060> the<00:09:12.810> issue 00:09:12.980 --> 00:09:12.990 align:start position:0% connectivity test essentially the issue 00:09:12.990 --> 00:09:19.450 align:start position:0% connectivity test essentially the issue here<00:09:13.820> is<00:09:15.140> that<00:09:16.140> in<00:09:16.890> order<00:09:17.040> to<00:09:17.220> do<00:09:17.490> that<00:09:17.670> so 00:09:19.450 --> 00:09:19.460 align:start position:0% here is that in order to do that so 00:09:19.460 --> 00:09:22.040 align:start position:0% here is that in order to do that so essentially<00:09:20.460> a<00:09:20.490> routing<00:09:20.760> table<00:09:20.910> requires<00:09:21.720> to 00:09:22.040 --> 00:09:22.050 align:start position:0% essentially a routing table requires to 00:09:22.050 --> 00:09:24.020 align:start position:0% essentially a routing table requires to be<00:09:22.110> able<00:09:22.230> to<00:09:22.440> tell<00:09:22.650> that<00:09:22.800> this<00:09:23.030> this 00:09:24.020 --> 00:09:24.030 align:start position:0% be able to tell that this this 00:09:24.030 --> 00:09:25.490 align:start position:0% be able to tell that this this particular<00:09:24.510> machine<00:09:24.660> is<00:09:24.990> at<00:09:25.170> this<00:09:25.290> particular 00:09:25.490 --> 00:09:25.500 align:start position:0% particular machine is at this particular 00:09:25.500 --> 00:09:28.190 align:start position:0% particular machine is at this particular IP<00:09:25.980> address<00:09:26.430> that's<00:09:27.330> what<00:09:27.570> the<00:09:27.660> routing<00:09:27.930> table 00:09:28.190 --> 00:09:28.200 align:start position:0% IP address that's what the routing table 00:09:28.200 --> 00:09:32.210 align:start position:0% IP address that's what the routing table does<00:09:28.410> the<00:09:29.400> problem<00:09:29.610> is<00:09:29.850> what<00:09:30.030> happens<00:09:30.510> if<00:09:31.220> my 00:09:32.210 --> 00:09:32.220 align:start position:0% does the problem is what happens if my 00:09:32.220 --> 00:09:34.790 align:start position:0% does the problem is what happens if my IP<00:09:32.850> address<00:09:33.060> is<00:09:33.330> changing<00:09:33.930> what<00:09:34.140> happens<00:09:34.530> if<00:09:34.680> I 00:09:34.790 --> 00:09:34.800 align:start position:0% IP address is changing what happens if I 00:09:34.800 --> 00:09:37.010 align:start position:0% IP address is changing what happens if I have<00:09:34.830> a<00:09:35.010> laptop<00:09:35.250> and<00:09:35.790> not<00:09:35.940> I'm<00:09:36.360> not<00:09:36.630> running<00:09:36.930> a 00:09:37.010 --> 00:09:37.020 align:start position:0% have a laptop and not I'm not running a 00:09:37.020 --> 00:09:38.630 align:start position:0% have a laptop and not I'm not running a theorem<00:09:37.260> on<00:09:37.350> my<00:09:37.440> home<00:09:37.620> server<00:09:37.890> rather<00:09:38.220> on<00:09:38.490> my 00:09:38.630 --> 00:09:38.640 align:start position:0% theorem on my home server rather on my 00:09:38.640 --> 00:09:41.090 align:start position:0% theorem on my home server rather on my laptop<00:09:38.820> and<00:09:39.210> I<00:09:39.630> keep<00:09:39.890> connecting<00:09:40.890> to<00:09:40.980> this 00:09:41.090 --> 00:09:41.100 align:start position:0% laptop and I keep connecting to this 00:09:41.100 --> 00:09:42.680 align:start position:0% laptop and I keep connecting to this theorem<00:09:41.340> network<00:09:41.730> from<00:09:41.940> all<00:09:42.060> over<00:09:42.090> the<00:09:42.480> world 00:09:42.680 --> 00:09:42.690 align:start position:0% theorem network from all over the world 00:09:42.690 --> 00:09:46.070 align:start position:0% theorem network from all over the world so<00:09:43.650> if<00:09:43.830> I<00:09:43.950> for<00:09:44.220> example<00:09:44.340> go<00:09:44.640> last<00:09:45.480> month<00:09:45.810> I<00:09:45.930> was 00:09:46.070 --> 00:09:46.080 align:start position:0% so if I for example go last month I was 00:09:46.080 --> 00:09:48.260 align:start position:0% so if I for example go last month I was in<00:09:46.200> San<00:09:46.380> Francisco<00:09:46.950> last<00:09:47.640> week<00:09:47.880> I<00:09:48.000> was<00:09:48.150> in 00:09:48.260 --> 00:09:48.270 align:start position:0% in San Francisco last week I was in 00:09:48.270 --> 00:09:50.630 align:start position:0% in San Francisco last week I was in Berlin<00:09:48.780> now<00:09:48.810> I'm<00:09:49.080> in<00:09:49.200> Prague<00:09:49.470> next<00:09:50.340> week<00:09:50.490> I'll 00:09:50.630 --> 00:09:50.640 align:start position:0% Berlin now I'm in Prague next week I'll 00:09:50.640 --> 00:09:53.030 align:start position:0% Berlin now I'm in Prague next week I'll be<00:09:50.670> in<00:09:50.850> I<00:09:51.420> don't<00:09:51.720> know<00:09:51.870> London<00:09:52.140> the<00:09:52.830> month 00:09:53.030 --> 00:09:53.040 align:start position:0% be in I don't know London the month 00:09:53.040 --> 00:09:55.250 align:start position:0% be in I don't know London the month afterwards<00:09:53.490> in<00:09:53.610> Shanghai<00:09:54.060> and<00:09:54.930> I<00:09:55.050> keep 00:09:55.250 --> 00:09:55.260 align:start position:0% afterwards in Shanghai and I keep 00:09:55.260 --> 00:09:56.750 align:start position:0% afterwards in Shanghai and I keep connecting<00:09:55.710> to<00:09:55.830> this<00:09:55.980> theorem<00:09:56.190> network<00:09:56.520> via 00:09:56.750 --> 00:09:56.760 align:start position:0% connecting to this theorem network via 00:09:56.760 --> 00:09:59.210 align:start position:0% connecting to this theorem network via light<00:09:57.000> client<00:09:57.450> be<00:09:58.080> that<00:09:58.260> mobile<00:09:58.500> device<00:09:58.920> be 00:09:59.210 --> 00:09:59.220 align:start position:0% light client be that mobile device be 00:09:59.220 --> 00:10:03.350 align:start position:0% light client be that mobile device be that<00:09:59.400> laptop<00:09:59.940> or<00:10:00.390> whatever<00:10:01.430> or<00:10:02.430> I<00:10:03.090> can<00:10:03.240> even 00:10:03.350 --> 00:10:03.360 align:start position:0% that laptop or whatever or I can even 00:10:03.360 --> 00:10:05.300 align:start position:0% that laptop or whatever or I can even run<00:10:03.750> a<00:10:03.810> full<00:10:04.110> note<00:10:04.320> on<00:10:04.470> my<00:10:04.590> laptop<00:10:04.830> and<00:10:05.070> do<00:10:05.190> the 00:10:05.300 --> 00:10:05.310 align:start position:0% run a full note on my laptop and do the 00:10:05.310 --> 00:10:06.830 align:start position:0% run a full note on my laptop and do the same<00:10:05.490> thing<00:10:05.730> that's<00:10:05.940> completely<00:10:06.600> equivalent 00:10:06.830 --> 00:10:06.840 align:start position:0% same thing that's completely equivalent 00:10:06.840 --> 00:10:09.140 align:start position:0% same thing that's completely equivalent what<00:10:07.740> the<00:10:07.860> result<00:10:08.190> will<00:10:08.370> be<00:10:08.400> is<00:10:08.700> that<00:10:08.880> every 00:10:09.140 --> 00:10:09.150 align:start position:0% what the result will be is that every 00:10:09.150 --> 00:10:10.580 align:start position:0% what the result will be is that every time<00:10:09.330> I<00:10:09.480> connect<00:10:09.750> to<00:10:09.780> the<00:10:09.930> network<00:10:10.110> I<00:10:10.440> am 00:10:10.580 --> 00:10:10.590 align:start position:0% time I connect to the network I am 00:10:10.590 --> 00:10:12.170 align:start position:0% time I connect to the network I am actually<00:10:10.740> revealing<00:10:11.280> to<00:10:11.520> the<00:10:11.610> network<00:10:12.000> that 00:10:12.170 --> 00:10:12.180 align:start position:0% actually revealing to the network that 00:10:12.180 --> 00:10:14.690 align:start position:0% actually revealing to the network that this<00:10:12.990> machine<00:10:13.440> which<00:10:13.830> last<00:10:14.100> week<00:10:14.370> was<00:10:14.550> in 00:10:14.690 --> 00:10:14.700 align:start position:0% this machine which last week was in 00:10:14.700 --> 00:10:17.540 align:start position:0% this machine which last week was in Berlin<00:10:15.150> this<00:10:15.540> week<00:10:15.750> is<00:10:15.870> in<00:10:15.900> Prague<00:10:16.320> and<00:10:16.650> next 00:10:17.540 --> 00:10:17.550 align:start position:0% Berlin this week is in Prague and next 00:10:17.550 --> 00:10:18.920 align:start position:0% Berlin this week is in Prague and next month<00:10:17.760> I<00:10:17.850> will<00:10:18.030> reveal<00:10:18.360> that<00:10:18.570> this<00:10:18.690> machine 00:10:18.920 --> 00:10:18.930 align:start position:0% month I will reveal that this machine 00:10:18.930 --> 00:10:20.810 align:start position:0% month I will reveal that this machine which<00:10:19.260> last<00:10:19.530> month<00:10:19.770> was<00:10:19.950> in<00:10:20.070> Prague<00:10:20.340> this 00:10:20.810 --> 00:10:20.820 align:start position:0% which last month was in Prague this 00:10:20.820 --> 00:10:24.290 align:start position:0% which last month was in Prague this month<00:10:21.120> is<00:10:21.330> in<00:10:21.510> Shanghai<00:10:22.410> and<00:10:23.060> this<00:10:24.060> is<00:10:24.180> an 00:10:24.290 --> 00:10:24.300 align:start position:0% month is in Shanghai and this is an 00:10:24.300 --> 00:10:28.280 align:start position:0% month is in Shanghai and this is an issue<00:10:24.920> because<00:10:25.920> this<00:10:26.730> public<00:10:27.090> information<00:10:27.290> so 00:10:28.280 --> 00:10:28.290 align:start position:0% issue because this public information so 00:10:28.290 --> 00:10:30.770 align:start position:0% issue because this public information so anyone<00:10:28.800> in<00:10:28.860> the<00:10:29.130> fear<00:10:29.340> network<00:10:29.790> can<00:10:30.270> at<00:10:30.570> any 00:10:30.770 --> 00:10:30.780 align:start position:0% anyone in the fear network can at any 00:10:30.780 --> 00:10:34.220 align:start position:0% anyone in the fear network can at any moment<00:10:31.170> in<00:10:31.290> time<00:10:31.320> see<00:10:31.910> where<00:10:32.910> certain<00:10:33.510> IDs<00:10:33.930> are 00:10:34.220 --> 00:10:34.230 align:start position:0% moment in time see where certain IDs are 00:10:34.230 --> 00:10:36.140 align:start position:0% moment in time see where certain IDs are and<00:10:34.530> not<00:10:35.010> only<00:10:35.160> that<00:10:35.280> but<00:10:35.640> if<00:10:35.790> you<00:10:35.880> are<00:10:35.910> willing 00:10:36.140 --> 00:10:36.150 align:start position:0% and not only that but if you are willing 00:10:36.150 --> 00:10:38.720 align:start position:0% and not only that but if you are willing to<00:10:36.450> do<00:10:36.600> this<00:10:36.780> for<00:10:37.230> example<00:10:37.320> every<00:10:37.770> day<00:10:37.950> just 00:10:38.720 --> 00:10:38.730 align:start position:0% to do this for example every day just 00:10:38.730 --> 00:10:42.050 align:start position:0% to do this for example every day just try<00:10:39.060> to<00:10:39.470> scan<00:10:40.470> the<00:10:40.620> network<00:10:40.710> every<00:10:41.190> day<00:10:41.340> then 00:10:42.050 --> 00:10:42.060 align:start position:0% try to scan the network every day then 00:10:42.060 --> 00:10:43.730 align:start position:0% try to scan the network every day then actually<00:10:42.420> you<00:10:42.510> can<00:10:42.660> create<00:10:42.960> an<00:10:43.170> extremely 00:10:43.730 --> 00:10:43.740 align:start position:0% actually you can create an extremely 00:10:43.740 --> 00:10:45.620 align:start position:0% actually you can create an extremely accurate<00:10:44.040> history<00:10:44.700> of<00:10:44.970> where<00:10:45.420> each 00:10:45.620 --> 00:10:45.630 align:start position:0% accurate history of where each 00:10:45.630 --> 00:10:49.040 align:start position:0% accurate history of where each individual<00:10:46.850> ëthere<00:10:47.850> node<00:10:48.120> was<00:10:48.390> moving<00:10:48.810> over 00:10:49.040 --> 00:10:49.050 align:start position:0% individual ëthere node was moving over 00:10:49.050 --> 00:10:51.710 align:start position:0% individual ëthere node was moving over time<00:10:49.440> and<00:10:49.740> just<00:10:50.610> nicely<00:10:51.030> plotted<00:10:51.510> on<00:10:51.630> the 00:10:51.710 --> 00:10:51.720 align:start position:0% time and just nicely plotted on the 00:10:51.720 --> 00:10:54.290 align:start position:0% time and just nicely plotted on the world<00:10:51.870> map<00:10:52.050> now<00:10:52.800> I'm<00:10:52.950> not<00:10:53.130> sure<00:10:53.180> most<00:10:54.180> people 00:10:54.290 --> 00:10:54.300 align:start position:0% world map now I'm not sure most people 00:10:54.300 --> 00:10:56.210 align:start position:0% world map now I'm not sure most people here<00:10:54.750> will<00:10:54.900> be<00:10:54.990> comfortable<00:10:55.560> having<00:10:55.800> their 00:10:56.210 --> 00:10:56.220 align:start position:0% here will be comfortable having their 00:10:56.220 --> 00:10:58.850 align:start position:0% here will be comfortable having their three<00:10:57.000> years<00:10:57.270> of<00:10:57.540> history<00:10:57.900> usage<00:10:58.350> mapped<00:10:58.590> out 00:10:58.850 --> 00:10:58.860 align:start position:0% three years of history usage mapped out 00:10:58.860 --> 00:11:02.950 align:start position:0% three years of history usage mapped out on<00:10:59.070> a<00:10:59.100> world<00:10:59.610> map<00:11:00.380> but<00:11:01.380> how<00:11:01.650> can<00:11:02.040> we<00:11:02.160> solve<00:11:02.340> this 00:11:02.950 --> 00:11:02.960 align:start position:0% on a world map but how can we solve this 00:11:02.960 --> 00:11:06.750 align:start position:0% on a world map but how can we solve this again<00:11:03.960> it's<00:11:04.290> not<00:11:04.860> an<00:11:05.160> obvious<00:11:05.490> solution 00:11:06.750 --> 00:11:06.760 align:start position:0% again it's not an obvious solution 00:11:06.760 --> 00:11:08.490 align:start position:0% again it's not an obvious solution one<00:11:06.940> of<00:11:07.029> the<00:11:07.149> simplest<00:11:07.510> thing<00:11:07.690> is<00:11:07.810> that<00:11:07.990> as<00:11:08.230> I 00:11:08.490 --> 00:11:08.500 align:start position:0% one of the simplest thing is that as I 00:11:08.500 --> 00:11:10.400 align:start position:0% one of the simplest thing is that as I said<00:11:08.529> the<00:11:08.769> domain<00:11:09.279> vulnerability<00:11:09.970> is<00:11:10.029> that 00:11:10.400 --> 00:11:10.410 align:start position:0% said the domain vulnerability is that 00:11:10.410 --> 00:11:12.569 align:start position:0% said the domain vulnerability is that machines<00:11:11.410> have<00:11:11.709> a<00:11:11.740> fixed<00:11:12.070> IP<00:11:12.220> address 00:11:12.569 --> 00:11:12.579 align:start position:0% machines have a fixed IP address 00:11:12.579 --> 00:11:14.340 align:start position:0% machines have a fixed IP address assigned<00:11:12.940> to<00:11:13.060> them<00:11:13.209> and<00:11:13.420> if<00:11:13.870> you<00:11:14.019> move<00:11:14.170> the 00:11:14.340 --> 00:11:14.350 align:start position:0% assigned to them and if you move the 00:11:14.350 --> 00:11:16.350 align:start position:0% assigned to them and if you move the machine<00:11:14.620> around<00:11:14.889> and<00:11:15.250> that<00:11:15.430> ID<00:11:15.639> ID<00:11:16.120> is 00:11:16.350 --> 00:11:16.360 align:start position:0% machine around and that ID ID is 00:11:16.360 --> 00:11:18.960 align:start position:0% machine around and that ID ID is essentially<00:11:16.870> the<00:11:17.019> global<00:11:17.350> tracker<00:11:17.790> so<00:11:18.790> we 00:11:18.960 --> 00:11:18.970 align:start position:0% essentially the global tracker so we 00:11:18.970 --> 00:11:21.000 align:start position:0% essentially the global tracker so we kind<00:11:19.180> of<00:11:19.240> made<00:11:19.420> a<00:11:19.449> cookie<00:11:19.750> tracking<00:11:20.320> on<00:11:20.709> top<00:11:20.889> of 00:11:21.000 --> 00:11:21.010 align:start position:0% kind of made a cookie tracking on top of 00:11:21.010 --> 00:11:23.069 align:start position:0% kind of made a cookie tracking on top of this<00:11:21.100> discovery<00:11:21.339> protocol<00:11:21.820> so<00:11:22.600> the<00:11:22.810> obvious 00:11:23.069 --> 00:11:23.079 align:start position:0% this discovery protocol so the obvious 00:11:23.079 --> 00:11:25.079 align:start position:0% this discovery protocol so the obvious solution<00:11:23.230> let's<00:11:23.649> get<00:11:23.800> rid<00:11:23.920> of<00:11:24.010> the<00:11:24.160> IDS<00:11:24.459> so 00:11:25.079 --> 00:11:25.089 align:start position:0% solution let's get rid of the IDS so 00:11:25.089 --> 00:11:27.360 align:start position:0% solution let's get rid of the IDS so just<00:11:25.480> minute<00:11:25.990> now<00:11:26.440> we<00:11:26.769> cannot<00:11:26.949> really<00:11:27.130> pin<00:11:27.339> it 00:11:27.360 --> 00:11:27.370 align:start position:0% just minute now we cannot really pin it 00:11:27.370 --> 00:11:28.500 align:start position:0% just minute now we cannot really pin it because<00:11:27.699> it's<00:11:27.850> part<00:11:28.029> of<00:11:28.089> the<00:11:28.240> etherium 00:11:28.500 --> 00:11:28.510 align:start position:0% because it's part of the etherium 00:11:28.510 --> 00:11:30.689 align:start position:0% because it's part of the etherium protocol<00:11:28.959> but<00:11:29.529> what<00:11:29.680> we<00:11:29.800> can<00:11:30.010> do<00:11:30.190> is<00:11:30.370> make<00:11:30.550> it 00:11:30.689 --> 00:11:30.699 align:start position:0% protocol but what we can do is make it 00:11:30.699 --> 00:11:32.759 align:start position:0% protocol but what we can do is make it as<00:11:30.790> ephemeral<00:11:31.120> so<00:11:31.959> that<00:11:32.170> every<00:11:32.410> time<00:11:32.589> we 00:11:32.759 --> 00:11:32.769 align:start position:0% as ephemeral so that every time we 00:11:32.769 --> 00:11:34.610 align:start position:0% as ephemeral so that every time we restart<00:11:33.130> the<00:11:33.220> machine<00:11:33.490> we<00:11:33.639> get<00:11:33.760> a<00:11:33.790> new<00:11:34.029> IP<00:11:34.240> and 00:11:34.610 --> 00:11:34.620 align:start position:0% restart the machine we get a new IP and 00:11:34.620 --> 00:11:38.699 align:start position:0% restart the machine we get a new IP and insert<00:11:35.620> a<00:11:35.649> new<00:11:35.709> ID<00:11:36.040> and<00:11:36.430> this<00:11:37.120> has<00:11:38.079> certain 00:11:38.699 --> 00:11:38.709 align:start position:0% insert a new ID and this has certain 00:11:38.709 --> 00:11:40.439 align:start position:0% insert a new ID and this has certain implications<00:11:38.949> one<00:11:39.730> of<00:11:39.820> the<00:11:39.940> implication<00:11:40.420> is 00:11:40.439 --> 00:11:40.449 align:start position:0% implications one of the implication is 00:11:40.449 --> 00:11:41.790 align:start position:0% implications one of the implication is that<00:11:40.540> obviously<00:11:41.079> if<00:11:41.199> I'm<00:11:41.320> running<00:11:41.560> a<00:11:41.620> boot 00:11:41.790 --> 00:11:41.800 align:start position:0% that obviously if I'm running a boot 00:11:41.800 --> 00:11:45.300 align:start position:0% that obviously if I'm running a boot node<00:11:42.040> the<00:11:42.699> ID<00:11:42.880> cannot<00:11:43.300> change<00:11:43.570> so<00:11:44.350> boot<00:11:45.070> nodes 00:11:45.300 --> 00:11:45.310 align:start position:0% node the ID cannot change so boot nodes 00:11:45.310 --> 00:11:47.129 align:start position:0% node the ID cannot change so boot nodes need<00:11:45.490> have<00:11:45.880> special<00:11:46.300> functionality<00:11:46.690> whereby 00:11:47.129 --> 00:11:47.139 align:start position:0% need have special functionality whereby 00:11:47.139 --> 00:11:50.160 align:start position:0% need have special functionality whereby the<00:11:47.199> IV<00:11:47.560> remains<00:11:48.279> the<00:11:48.430> same<00:11:48.750> what<00:11:49.750> happens 00:11:50.160 --> 00:11:50.170 align:start position:0% the IV remains the same what happens 00:11:50.170 --> 00:11:52.889 align:start position:0% the IV remains the same what happens however<00:11:50.500> if<00:11:50.800> I<00:11:51.070> run<00:11:51.579> a<00:11:51.610> full<00:11:51.910> node<00:11:52.149> and<00:11:52.420> I<00:11:52.690> just 00:11:52.889 --> 00:11:52.899 align:start position:0% however if I run a full node and I just 00:11:52.899 --> 00:11:54.780 align:start position:0% however if I run a full node and I just restarted<00:11:53.440> I<00:11:53.500> did<00:11:53.649> the<00:11:53.740> update<00:11:53.889> I<00:11:54.279> restarted 00:11:54.780 --> 00:11:54.790 align:start position:0% restarted I did the update I restarted 00:11:54.790 --> 00:11:57.180 align:start position:0% restarted I did the update I restarted it<00:11:54.940> normally<00:11:55.810> if<00:11:55.959> the<00:11:55.990> IV<00:11:56.290> changes<00:11:56.829> that's<00:11:57.010> not 00:11:57.180 --> 00:11:57.190 align:start position:0% it normally if the IV changes that's not 00:11:57.190 --> 00:12:00.720 align:start position:0% it normally if the IV changes that's not such<00:11:57.399> a<00:11:57.430> big<00:11:57.670> problem<00:11:57.940> in<00:11:58.420> practice<00:11:59.730> last 00:12:00.720 --> 00:12:00.730 align:start position:0% such a big problem in practice last 00:12:00.730 --> 00:12:04.439 align:start position:0% such a big problem in practice last minute<00:12:01.120> we<00:12:01.269> told<00:12:01.510> in<00:12:01.630> the<00:12:01.720> network<00:12:02.050> that<00:12:03.449> this 00:12:04.439 --> 00:12:04.449 align:start position:0% minute we told in the network that this 00:12:04.449 --> 00:12:06.509 align:start position:0% minute we told in the network that this IP<00:12:04.690> address<00:12:04.870> belongs<00:12:05.440> to<00:12:05.649> a<00:12:05.680> certain<00:12:05.829> ID<00:12:06.160> and 00:12:06.509 --> 00:12:06.519 align:start position:0% IP address belongs to a certain ID and 00:12:06.519 --> 00:12:08.610 align:start position:0% IP address belongs to a certain ID and now<00:12:07.329> we're<00:12:07.690> telling<00:12:08.019> conflicting 00:12:08.610 --> 00:12:08.620 align:start position:0% now we're telling conflicting 00:12:08.620 --> 00:12:10.650 align:start position:0% now we're telling conflicting information<00:12:08.769> and<00:12:09.430> currently<00:12:10.240> the<00:12:10.389> theorem 00:12:10.650 --> 00:12:10.660 align:start position:0% information and currently the theorem 00:12:10.660 --> 00:12:13.230 align:start position:0% information and currently the theorem discovery<00:12:11.230> protocol<00:12:11.470> cannot<00:12:11.920> handle<00:12:12.310> that<00:12:12.370> so 00:12:13.230 --> 00:12:13.240 align:start position:0% discovery protocol cannot handle that so 00:12:13.240 --> 00:12:15.300 align:start position:0% discovery protocol cannot handle that so if<00:12:13.300> you<00:12:13.389> keep<00:12:13.569> sending<00:12:13.779> in<00:12:14.019> that<00:12:14.199> you<00:12:14.829> restart 00:12:15.300 --> 00:12:15.310 align:start position:0% if you keep sending in that you restart 00:12:15.310 --> 00:12:16.829 align:start position:0% if you keep sending in that you restart your<00:12:15.399> machine<00:12:15.519> four<00:12:15.940> times<00:12:16.209> and<00:12:16.510> you're 00:12:16.829 --> 00:12:16.839 align:start position:0% your machine four times and you're 00:12:16.839 --> 00:12:18.480 align:start position:0% your machine four times and you're standing<00:12:17.230> in<00:12:17.319> for<00:12:17.560> completely<00:12:18.010> conflicting 00:12:18.480 --> 00:12:18.490 align:start position:0% standing in for completely conflicting 00:12:18.490 --> 00:12:20.129 align:start position:0% standing in for completely conflicting information<00:12:18.639> into<00:12:19.240> the<00:12:19.300> discovery<00:12:19.690> protocol 00:12:20.129 --> 00:12:20.139 align:start position:0% information into the discovery protocol 00:12:20.139 --> 00:12:21.990 align:start position:0% information into the discovery protocol then<00:12:20.440> discovery<00:12:20.949> protocol<00:12:21.279> will<00:12:21.490> just<00:12:21.699> go 00:12:21.990 --> 00:12:22.000 align:start position:0% then discovery protocol will just go 00:12:22.000 --> 00:12:24.689 align:start position:0% then discovery protocol will just go haywire<00:12:22.510> and<00:12:22.779> you<00:12:23.740> will<00:12:23.860> have<00:12:24.010> a<00:12:24.040> very<00:12:24.399> hard 00:12:24.689 --> 00:12:24.699 align:start position:0% haywire and you will have a very hard 00:12:24.699 --> 00:12:26.670 align:start position:0% haywire and you will have a very hard time<00:12:24.940> do<00:12:25.810> this<00:12:25.959> to<00:12:26.199> connect<00:12:26.470> to<00:12:26.560> the<00:12:26.649> network 00:12:26.670 --> 00:12:26.680 align:start position:0% time do this to connect to the network 00:12:26.680 --> 00:12:29.160 align:start position:0% time do this to connect to the network yes<00:12:27.190> eventually<00:12:27.459> maybe<00:12:28.389> five<00:12:28.720> minutes<00:12:28.990> ten 00:12:29.160 --> 00:12:29.170 align:start position:0% yes eventually maybe five minutes ten 00:12:29.170 --> 00:12:31.019 align:start position:0% yes eventually maybe five minutes ten minutes<00:12:29.290> everything<00:12:29.769> will<00:12:29.800> settle<00:12:30.040> down<00:12:30.220> but 00:12:31.019 --> 00:12:31.029 align:start position:0% minutes everything will settle down but 00:12:31.029 --> 00:12:33.269 align:start position:0% minutes everything will settle down but it<00:12:31.180> is<00:12:31.360> an<00:12:31.540> issue<00:12:31.660> and<00:12:32.170> last<00:12:32.410> mother<00:12:32.589> last<00:12:33.069> but 00:12:33.269 --> 00:12:33.279 align:start position:0% it is an issue and last mother last but 00:12:33.279 --> 00:12:35.759 align:start position:0% it is an issue and last mother last but not<00:12:33.370> least<00:12:33.639> if<00:12:33.940> we<00:12:34.630> actually<00:12:34.750> do<00:12:35.589> the<00:12:35.740> same 00:12:35.759 --> 00:12:35.769 align:start position:0% not least if we actually do the same 00:12:35.769 --> 00:12:39.000 align:start position:0% not least if we actually do the same thing<00:12:36.220> with<00:12:36.399> live<00:12:36.610> clients<00:12:37.120> then<00:12:38.010> we're 00:12:39.000 --> 00:12:39.010 align:start position:0% thing with live clients then we're 00:12:39.010 --> 00:12:41.009 align:start position:0% thing with live clients then we're breaking<00:12:39.430> projects<00:12:40.000> that<00:12:40.180> rely<00:12:40.600> on<00:12:40.630> this 00:12:41.009 --> 00:12:41.019 align:start position:0% breaking projects that rely on this 00:12:41.019 --> 00:12:43.259 align:start position:0% breaking projects that rely on this behavior<00:12:41.470> for<00:12:41.920> example<00:12:41.949> one<00:12:42.339> of<00:12:42.370> them<00:12:42.579> is<00:12:42.610> VIP 00:12:43.259 --> 00:12:43.269 align:start position:0% behavior for example one of them is VIP 00:12:43.269 --> 00:12:46.439 align:start position:0% behavior for example one of them is VIP node<00:12:43.660> and<00:12:44.370> they<00:12:45.370> are<00:12:45.490> essentially<00:12:45.970> trying<00:12:46.269> to 00:12:46.439 --> 00:12:46.449 align:start position:0% node and they are essentially trying to 00:12:46.449 --> 00:12:48.030 align:start position:0% node and they are essentially trying to incentivize<00:12:46.990> running<00:12:47.440> full<00:12:47.620> nodes<00:12:47.829> by 00:12:48.030 --> 00:12:48.040 align:start position:0% incentivize running full nodes by 00:12:48.040 --> 00:12:50.220 align:start position:0% incentivize running full nodes by providing<00:12:48.490> light<00:12:48.819> servers<00:12:49.329> for<00:12:49.630> payment<00:12:50.110> and 00:12:50.220 --> 00:12:50.230 align:start position:0% providing light servers for payment and 00:12:50.230 --> 00:12:53.309 align:start position:0% providing light servers for payment and then<00:12:50.560> live<00:12:50.740> clients<00:12:51.160> can<00:12:51.279> pay<00:12:51.459> a<00:12:51.490> bit<00:12:51.579> and<00:12:52.319> then 00:12:53.309 --> 00:12:53.319 align:start position:0% then live clients can pay a bit and then 00:12:53.319 --> 00:12:57.389 align:start position:0% then live clients can pay a bit and then they<00:12:53.440> get<00:12:53.620> the<00:12:54.630> light<00:12:55.630> server<00:12:55.930> services<00:12:56.529> the 00:12:57.389 --> 00:12:57.399 align:start position:0% they get the light server services the 00:12:57.399 --> 00:12:59.129 align:start position:0% they get the light server services the issue<00:12:57.610> here<00:12:57.819> is<00:12:58.000> that<00:12:58.029> the<00:12:58.240> authentication 00:12:59.129 --> 00:12:59.139 align:start position:0% issue here is that the authentication 00:12:59.139 --> 00:13:01.680 align:start position:0% issue here is that the authentication mechanism<00:12:59.589> they<00:12:59.740> use<00:12:59.980> is<00:13:00.220> that<00:13:00.880> their<00:13:01.269> payment 00:13:01.680 --> 00:13:01.690 align:start position:0% mechanism they use is that their payment 00:13:01.690 --> 00:13:04.710 align:start position:0% mechanism they use is that their payment is<00:13:01.810> associated<00:13:02.290> with<00:13:02.470> their<00:13:02.860> node<00:13:03.040> ID<00:13:03.420> so<00:13:04.420> take 00:13:04.710 --> 00:13:04.720 align:start position:0% is associated with their node ID so take 00:13:04.720 --> 00:13:07.379 align:start position:0% is associated with their node ID so take away<00:13:04.870> their<00:13:05.110> node<00:13:05.319> ID<00:13:05.529> and<00:13:05.860> we<00:13:06.639> just<00:13:06.880> blew<00:13:07.240> up 00:13:07.379 --> 00:13:07.389 align:start position:0% away their node ID and we just blew up 00:13:07.389 --> 00:13:10.920 align:start position:0% away their node ID and we just blew up the<00:13:07.750> VIP<00:13:08.019> node<00:13:08.230> business<00:13:08.560> model<00:13:08.889> and<00:13:09.779> this<00:13:10.779> is 00:13:10.920 --> 00:13:10.930 align:start position:0% the VIP node business model and this is 00:13:10.930 --> 00:13:12.900 align:start position:0% the VIP node business model and this is I'm<00:13:11.260> not<00:13:11.380> saying<00:13:11.709> that<00:13:11.800> this<00:13:12.310> is<00:13:12.430> cannot<00:13:12.760> be 00:13:12.900 --> 00:13:12.910 align:start position:0% I'm not saying that this is cannot be 00:13:12.910 --> 00:13:14.819 align:start position:0% I'm not saying that this is cannot be solved<00:13:13.300> what<00:13:13.690> I'm<00:13:13.810> trying<00:13:14.050> to<00:13:14.110> say<00:13:14.319> here<00:13:14.649> is 00:13:14.819 --> 00:13:14.829 align:start position:0% solved what I'm trying to say here is 00:13:14.829 --> 00:13:17.519 align:start position:0% solved what I'm trying to say here is that<00:13:15.100> these<00:13:15.610> really<00:13:16.420> trivial<00:13:16.720> issues<00:13:17.290> and 00:13:17.519 --> 00:13:17.529 align:start position:0% that these really trivial issues and 00:13:17.529 --> 00:13:20.160 align:start position:0% that these really trivial issues and trivial<00:13:17.860> fixes<00:13:18.339> can<00:13:18.790> have<00:13:19.000> very<00:13:19.209> very<00:13:19.390> heavy 00:13:20.160 --> 00:13:20.170 align:start position:0% trivial fixes can have very very heavy 00:13:20.170 --> 00:13:21.690 align:start position:0% trivial fixes can have very very heavy vacations<00:13:20.649> on<00:13:20.860> certain<00:13:21.250> players<00:13:21.430> in<00:13:21.610> the 00:13:21.690 --> 00:13:21.700 align:start position:0% vacations on certain players in the 00:13:21.700 --> 00:13:24.269 align:start position:0% vacations on certain players in the network<00:13:22.060> and<00:13:22.529> often<00:13:23.529> we<00:13:23.709> as<00:13:23.950> declined 00:13:24.269 --> 00:13:24.279 align:start position:0% network and often we as declined 00:13:24.279 --> 00:13:26.280 align:start position:0% network and often we as declined developers<00:13:24.700> don't<00:13:24.880> want<00:13:25.060> to<00:13:25.420> ruin<00:13:26.110> people's 00:13:26.280 --> 00:13:26.290 align:start position:0% developers don't want to ruin people's 00:13:26.290 --> 00:13:31.139 align:start position:0% developers don't want to ruin people's days<00:13:26.829> and<00:13:27.100> people's<00:13:27.430> projects<00:13:29.760> anyway<00:13:30.760> so 00:13:31.139 --> 00:13:31.149 align:start position:0% days and people's projects anyway so 00:13:31.149 --> 00:13:32.460 align:start position:0% days and people's projects anyway so that's<00:13:31.300> the<00:13:31.510> discovery<00:13:31.959> it<00:13:32.110> is<00:13:32.260> an 00:13:32.460 --> 00:13:32.470 align:start position:0% that's the discovery it is an 00:13:32.470 --> 00:13:35.120 align:start position:0% that's the discovery it is an interesting<00:13:33.040> interesting<00:13:33.790> problem<00:13:34.329> to<00:13:34.450> solve 00:13:35.120 --> 00:13:35.130 align:start position:0% interesting interesting problem to solve 00:13:35.130 --> 00:13:38.400 align:start position:0% interesting interesting problem to solve now<00:13:36.130> if<00:13:36.339> we<00:13:36.550> go<00:13:36.790> further<00:13:37.420> deep<00:13:37.839> into<00:13:38.170> the<00:13:38.290> light 00:13:38.400 --> 00:13:38.410 align:start position:0% now if we go further deep into the light 00:13:38.410 --> 00:13:42.210 align:start position:0% now if we go further deep into the light clients<00:13:38.910> then<00:13:40.500> how<00:13:41.500> do<00:13:41.560> light<00:13:41.769> clients<00:13:42.100> work 00:13:42.210 --> 00:13:42.220 align:start position:0% clients then how do light clients work 00:13:42.220 --> 00:13:43.860 align:start position:0% clients then how do light clients work last<00:13:42.430> I<00:13:42.550> suppose<00:13:42.850> we<00:13:43.000> forget<00:13:43.269> about<00:13:43.300> discovery 00:13:43.860 --> 00:13:43.870 align:start position:0% last I suppose we forget about discovery 00:13:43.870 --> 00:13:45.660 align:start position:0% last I suppose we forget about discovery let's<00:13:44.110> suppose<00:13:44.290> we<00:13:44.440> somehow<00:13:44.709> fix<00:13:44.980> discovery 00:13:45.660 --> 00:13:45.670 align:start position:0% let's suppose we somehow fix discovery 00:13:45.670 --> 00:13:48.120 align:start position:0% let's suppose we somehow fix discovery well<00:13:46.389> that<00:13:46.510> clients<00:13:46.899> essentially<00:13:47.440> they 00:13:48.120 --> 00:13:48.130 align:start position:0% well that clients essentially they 00:13:48.130 --> 00:13:50.060 align:start position:0% well that clients essentially they connect<00:13:48.430> with<00:13:48.490> full<00:13:48.760> nodes<00:13:48.970> full<00:13:49.360> servers 00:13:50.060 --> 00:13:50.070 align:start position:0% connect with full nodes full servers 00:13:50.070 --> 00:13:52.470 align:start position:0% connect with full nodes full servers which<00:13:51.070> actually<00:13:51.430> have<00:13:51.579> all<00:13:51.790> the<00:13:51.970> blocks<00:13:52.180> and 00:13:52.470 --> 00:13:52.480 align:start position:0% which actually have all the blocks and 00:13:52.480 --> 00:13:54.090 align:start position:0% which actually have all the blocks and instead<00:13:53.019> of<00:13:53.139> downloading<00:13:53.620> the<00:13:53.709> blocks<00:13:53.949> and 00:13:54.090 --> 00:13:54.100 align:start position:0% instead of downloading the blocks and 00:13:54.100 --> 00:13:55.949 align:start position:0% instead of downloading the blocks and processing<00:13:54.579> them<00:13:54.699> they<00:13:55.209> are<00:13:55.300> just<00:13:55.510> randomly 00:13:55.949 --> 00:13:55.959 align:start position:0% processing them they are just randomly 00:13:55.959 --> 00:13:58.829 align:start position:0% processing them they are just randomly picking<00:13:56.380> the<00:13:56.680> block<00:13:56.949> headers<00:13:57.389> which<00:13:58.389> are<00:13:58.600> kind 00:13:58.829 --> 00:13:58.839 align:start position:0% picking the block headers which are kind 00:13:58.839 --> 00:14:01.379 align:start position:0% picking the block headers which are kind of<00:13:58.899> is<00:13:59.170> a<00:13:59.320> nice<00:13:59.769> enough<00:13:59.949> proof<00:14:00.370> that<00:14:01.029> the<00:14:01.180> chain 00:14:01.379 --> 00:14:01.389 align:start position:0% of is a nice enough proof that the chain 00:14:01.389 --> 00:14:03.389 align:start position:0% of is a nice enough proof that the chain is<00:14:01.540> valid<00:14:01.899> but<00:14:02.470> they<00:14:02.680> do<00:14:02.740> not<00:14:02.949> download<00:14:03.100> the 00:14:03.389 --> 00:14:03.399 align:start position:0% is valid but they do not download the 00:14:03.399 --> 00:14:05.819 align:start position:0% is valid but they do not download the state<00:14:03.639> and<00:14:04.120> then<00:14:04.300> when<00:14:04.510> we<00:14:04.660> start<00:14:04.959> mist<00:14:05.230> or<00:14:05.560> any 00:14:05.819 --> 00:14:05.829 align:start position:0% state and then when we start mist or any 00:14:05.829 --> 00:14:07.970 align:start position:0% state and then when we start mist or any other<00:14:06.040> deck<00:14:06.820> that<00:14:07.060> we<00:14:07.209> really<00:14:07.420> care<00:14:07.600> about 00:14:07.970 --> 00:14:07.980 align:start position:0% other deck that we really care about 00:14:07.980 --> 00:14:11.579 align:start position:0% other deck that we really care about then<00:14:09.570> the<00:14:10.570> light<00:14:10.720> client<00:14:11.110> will<00:14:11.199> actually 00:14:11.579 --> 00:14:11.589 align:start position:0% then the light client will actually 00:14:11.589 --> 00:14:13.379 align:start position:0% then the light client will actually fetch<00:14:11.860> the<00:14:12.070> balance<00:14:12.459> for<00:14:12.760> example<00:14:12.820> if<00:14:13.149> I<00:14:13.240> have 00:14:13.379 --> 00:14:13.389 align:start position:0% fetch the balance for example if I have 00:14:13.389 --> 00:14:15.930 align:start position:0% fetch the balance for example if I have three<00:14:13.899> accounts<00:14:14.260> in<00:14:14.350> mist<00:14:14.529> then<00:14:15.250> every<00:14:15.519> time<00:14:15.699> a 00:14:15.930 --> 00:14:15.940 align:start position:0% three accounts in mist then every time a 00:14:15.940 --> 00:14:17.550 align:start position:0% three accounts in mist then every time a new<00:14:16.209> block<00:14:16.420> arrives<00:14:16.750> mist<00:14:17.050> will<00:14:17.230> actually 00:14:17.550 --> 00:14:17.560 align:start position:0% new block arrives mist will actually 00:14:17.560 --> 00:14:19.850 align:start position:0% new block arrives mist will actually fetch<00:14:17.800> those<00:14:18.070> balances<00:14:19.000> for<00:14:19.149> those<00:14:19.300> three 00:14:19.850 --> 00:14:19.860 align:start position:0% fetch those balances for those three 00:14:19.860 --> 00:14:22.829 align:start position:0% fetch those balances for those three accounts<00:14:20.860> I<00:14:20.920> care<00:14:21.160> about<00:14:21.370> and<00:14:21.690> again<00:14:22.690> this 00:14:22.829 --> 00:14:22.839 align:start position:0% accounts I care about and again this 00:14:22.839 --> 00:14:24.360 align:start position:0% accounts I care about and again this seems<00:14:23.079> like<00:14:23.199> completely<00:14:23.649> logical<00:14:23.800> this<00:14:24.250> is 00:14:24.360 --> 00:14:24.370 align:start position:0% seems like completely logical this is 00:14:24.370 --> 00:14:26.490 align:start position:0% seems like completely logical this is the<00:14:24.490> most<00:14:24.640> optimal<00:14:25.209> way<00:14:25.269> to<00:14:25.930> reduce<00:14:26.230> latency 00:14:26.490 --> 00:14:26.500 align:start position:0% the most optimal way to reduce latency 00:14:26.500 --> 00:14:28.860 align:start position:0% the most optimal way to reduce latency reduce<00:14:27.040> bandwidth<00:14:27.550> and<00:14:27.820> just<00:14:28.449> make<00:14:28.630> all<00:14:28.779> the 00:14:28.860 --> 00:14:28.870 align:start position:0% reduce bandwidth and just make all the 00:14:28.870 --> 00:14:33.750 align:start position:0% reduce bandwidth and just make all the traffic<00:14:29.170> useful<00:14:29.820> except<00:14:32.100> now<00:14:33.100> all<00:14:33.459> of<00:14:33.670> a 00:14:33.750 --> 00:14:33.760 align:start position:0% traffic useful except now all of a 00:14:33.760 --> 00:14:36.590 align:start position:0% traffic useful except now all of a sudden<00:14:33.790> the<00:14:34.300> light<00:14:34.449> server<00:14:34.810> knows<00:14:35.350> that<00:14:35.740> I<00:14:35.949> am 00:14:36.590 --> 00:14:36.600 align:start position:0% sudden the light server knows that I am 00:14:36.600 --> 00:14:39.090 align:start position:0% sudden the light server knows that I am this<00:14:37.600> IP<00:14:37.839> address<00:14:38.019> is<00:14:38.320> interested<00:14:38.829> in<00:14:38.890> that 00:14:39.090 --> 00:14:39.100 align:start position:0% this IP address is interested in that 00:14:39.100 --> 00:14:42.930 align:start position:0% this IP address is interested in that particular<00:14:39.339> account<00:14:39.970> oh<00:14:41.130> and<00:14:42.130> one<00:14:42.310> more<00:14:42.339> I 00:14:42.930 --> 00:14:42.940 align:start position:0% particular account oh and one more I 00:14:42.940 --> 00:14:44.850 align:start position:0% particular account oh and one more I think<00:14:43.630> I<00:14:43.720> want<00:14:43.870> to<00:14:43.930> be<00:14:44.019> the<00:14:44.110> head<00:14:44.230> so<00:14:44.560> two<00:14:44.709> more 00:14:44.850 --> 00:14:44.860 align:start position:0% think I want to be the head so two more 00:14:44.860 --> 00:14:46.319 align:start position:0% think I want to be the head so two more things<00:14:45.010> that<00:14:45.130> I<00:14:45.220> wanted<00:14:45.519> to<00:14:45.579> say<00:14:45.820> about<00:14:46.149> how 00:14:46.319 --> 00:14:46.329 align:start position:0% things that I wanted to say about how 00:14:46.329 --> 00:14:48.990 align:start position:0% things that I wanted to say about how the<00:14:46.390> light<00:14:46.839> clients<00:14:47.230> work<00:14:47.610> so<00:14:48.610> one<00:14:48.730> of<00:14:48.760> them 00:14:48.990 --> 00:14:49.000 align:start position:0% the light clients work so one of them 00:14:49.000 --> 00:14:50.519 align:start position:0% the light clients work so one of them was<00:14:49.180> that<00:14:49.660> they<00:14:50.050> are<00:14:50.140> obviously 00:14:50.519 --> 00:14:50.529 align:start position:0% was that they are obviously 00:14:50.529 --> 00:14:52.170 align:start position:0% was that they are obviously synchronizing<00:14:51.160> header<00:14:51.339> and<00:14:51.579> then<00:14:51.670> retrieving 00:14:52.170 --> 00:14:52.180 align:start position:0% synchronizing header and then retrieving 00:14:52.180 --> 00:14:54.170 align:start position:0% synchronizing header and then retrieving data<00:14:52.360> on<00:14:52.600> demand<00:14:52.750> only<00:14:53.410> interesting<00:14:53.920> data 00:14:54.170 --> 00:14:54.180 align:start position:0% data on demand only interesting data 00:14:54.180 --> 00:14:56.699 align:start position:0% data on demand only interesting data another<00:14:55.180> really<00:14:55.720> interesting<00:14:55.750> aspect<00:14:56.230> of<00:14:56.589> the 00:14:56.699 --> 00:14:56.709 align:start position:0% another really interesting aspect of the 00:14:56.709 --> 00:14:58.710 align:start position:0% another really interesting aspect of the light<00:14:56.860> kind<00:14:57.070> that<00:14:57.339> I<00:14:57.519> think<00:14:57.820> apart<00:14:58.600> from 00:14:58.710 --> 00:14:58.720 align:start position:0% light kind that I think apart from 00:14:58.720 --> 00:15:00.389 align:start position:0% light kind that I think apart from protocol<00:14:59.050> developers<00:14:59.649> most<00:14:59.890> people<00:15:00.250> are 00:15:00.389 --> 00:15:00.399 align:start position:0% protocol developers most people are 00:15:00.399 --> 00:15:02.970 align:start position:0% protocol developers most people are unaware<00:15:00.670> of<00:15:00.880> is<00:15:01.390> that<00:15:01.959> light<00:15:02.199> clients<00:15:02.649> cannot 00:15:02.970 --> 00:15:02.980 align:start position:0% unaware of is that light clients cannot 00:15:02.980 --> 00:15:05.130 align:start position:0% unaware of is that light clients cannot verify<00:15:03.670> the<00:15:03.730> state<00:15:04.149> so<00:15:04.569> they<00:15:04.690> are<00:15:04.779> verifying 00:15:05.130 --> 00:15:05.140 align:start position:0% verify the state so they are verifying 00:15:05.140 --> 00:15:07.740 align:start position:0% verify the state so they are verifying the<00:15:05.260> proof<00:15:05.440> of<00:15:05.589> work<00:15:05.769> but<00:15:06.430> they<00:15:06.610> blindly<00:15:07.360> trust 00:15:07.740 --> 00:15:07.750 align:start position:0% the proof of work but they blindly trust 00:15:07.750 --> 00:15:09.689 align:start position:0% the proof of work but they blindly trust that<00:15:07.959> so<00:15:08.589> every<00:15:08.800> time<00:15:08.949> you<00:15:09.100> get<00:15:09.220> a<00:15:09.250> new<00:15:09.430> block 00:15:09.689 --> 00:15:09.699 align:start position:0% that so every time you get a new block 00:15:09.699 --> 00:15:11.579 align:start position:0% that so every time you get a new block you<00:15:10.180> just<00:15:10.420> assume<00:15:10.720> if<00:15:10.870> the<00:15:11.050> proof<00:15:11.199> of<00:15:11.290> work<00:15:11.470> is 00:15:11.579 --> 00:15:11.589 align:start position:0% you just assume if the proof of work is 00:15:11.589 --> 00:15:14.160 align:start position:0% you just assume if the proof of work is valid<00:15:11.920> then<00:15:12.399> whatever<00:15:12.579> state<00:15:13.089> that<00:15:13.779> block<00:15:14.019> is 00:15:14.160 --> 00:15:14.170 align:start position:0% valid then whatever state that block is 00:15:14.170 --> 00:15:16.500 align:start position:0% valid then whatever state that block is associated<00:15:14.589> with<00:15:14.769> will<00:15:15.279> be<00:15:15.459> valid<00:15:15.850> and<00:15:16.060> this 00:15:16.500 --> 00:15:16.510 align:start position:0% associated with will be valid and this 00:15:16.510 --> 00:15:17.790 align:start position:0% associated with will be valid and this works<00:15:16.779> because<00:15:17.230> if<00:15:17.319> you<00:15:17.440> have<00:15:17.560> a<00:15:17.589> good 00:15:17.790 --> 00:15:17.800 align:start position:0% works because if you have a good 00:15:17.800 --> 00:15:20.280 align:start position:0% works because if you have a good connectivity<00:15:18.069> to<00:15:18.490> the<00:15:18.579> network<00:15:18.940> and<00:15:19.209> you<00:15:19.290> have 00:15:20.280 --> 00:15:20.290 align:start position:0% connectivity to the network and you have 00:15:20.290 --> 00:15:22.439 align:start position:0% connectivity to the network and you have many<00:15:20.500> people<00:15:20.829> sending<00:15:21.160> you<00:15:21.310> blocks<00:15:21.579> then<00:15:22.300> it's 00:15:22.439 --> 00:15:22.449 align:start position:0% many people sending you blocks then it's 00:15:22.449 --> 00:15:23.970 align:start position:0% many people sending you blocks then it's really<00:15:22.600> hard<00:15:22.899> for<00:15:22.959> somebody<00:15:23.260> to<00:15:23.440> forge<00:15:23.829> a 00:15:23.970 --> 00:15:23.980 align:start position:0% really hard for somebody to forge a 00:15:23.980 --> 00:15:25.530 align:start position:0% really hard for somebody to forge a block<00:15:24.190> because<00:15:24.519> yet<00:15:24.730> they<00:15:24.910> could<00:15:25.120> forge<00:15:25.420> a 00:15:25.530 --> 00:15:25.540 align:start position:0% block because yet they could forge a 00:15:25.540 --> 00:15:28.230 align:start position:0% block because yet they could forge a block<00:15:25.750> but<00:15:26.019> the<00:15:26.980> internet<00:15:27.699> where<00:15:27.910> the<00:15:27.940> rest<00:15:28.180> of 00:15:28.230 --> 00:15:28.240 align:start position:0% block but the internet where the rest of 00:15:28.240 --> 00:15:29.670 align:start position:0% block but the internet where the rest of the<00:15:28.329> network<00:15:28.630> won't<00:15:28.779> accept<00:15:29.199> it<00:15:29.380> so<00:15:29.529> after 00:15:29.670 --> 00:15:29.680 align:start position:0% the network won't accept it so after 00:15:29.680 --> 00:15:31.949 align:start position:0% the network won't accept it so after this<00:15:29.980> after<00:15:30.430> a<00:15:30.699> few<00:15:31.089> more<00:15:31.329> blocks<00:15:31.480> it<00:15:31.779> will 00:15:31.949 --> 00:15:31.959 align:start position:0% this after a few more blocks it will 00:15:31.959 --> 00:15:33.440 align:start position:0% this after a few more blocks it will just<00:15:32.140> get<00:15:32.260> reeled<00:15:32.649> out<00:15:32.800> of<00:15:33.010> your 00:15:33.440 --> 00:15:33.450 align:start position:0% just get reeled out of your 00:15:33.450 --> 00:15:36.330 align:start position:0% just get reeled out of your so<00:15:34.450> nobody<00:15:34.960> can<00:15:35.140> really<00:15:35.290> keep<00:15:35.560> attacking<00:15:35.980> you 00:15:36.330 --> 00:15:36.340 align:start position:0% so nobody can really keep attacking you 00:15:36.340 --> 00:15:41.540 align:start position:0% so nobody can really keep attacking you as<00:15:36.550> long<00:15:37.480> as<00:15:37.690> your<00:15:37.840> connectivity<00:15:38.530> is<00:15:38.710> valid<00:15:39.700> so 00:15:41.540 --> 00:15:41.550 align:start position:0% as long as your connectivity is valid so 00:15:41.550 --> 00:15:44.310 align:start position:0% as long as your connectivity is valid so what<00:15:42.550> happens<00:15:42.970> yeah<00:15:43.840> I<00:15:43.870> went<00:15:44.110> a<00:15:44.200> bit 00:15:44.310 --> 00:15:44.320 align:start position:0% what happens yeah I went a bit 00:15:44.320 --> 00:15:46.830 align:start position:0% what happens yeah I went a bit previously<00:15:45.310> with<00:15:45.430> the<00:15:45.460> head<00:15:45.670> but<00:15:46.330> essentially 00:15:46.830 --> 00:15:46.840 align:start position:0% previously with the head but essentially 00:15:46.840 --> 00:15:48.090 align:start position:0% previously with the head but essentially with<00:15:46.990> the<00:15:47.140> light<00:15:47.290> clients<00:15:47.800> and<00:15:47.950> on-demand 00:15:48.090 --> 00:15:48.100 align:start position:0% with the light clients and on-demand 00:15:48.100 --> 00:15:50.880 align:start position:0% with the light clients and on-demand retrieval<00:15:48.940> the<00:15:49.750> issue<00:15:49.960> is<00:15:50.200> that<00:15:50.230> whenever<00:15:50.560> if 00:15:50.880 --> 00:15:50.890 align:start position:0% retrieval the issue is that whenever if 00:15:50.890 --> 00:15:52.560 align:start position:0% retrieval the issue is that whenever if I<00:15:51.010> have<00:15:51.160> missed<00:15:51.400> connected<00:15:51.910> and<00:15:52.060> it<00:15:52.180> every 00:15:52.560 --> 00:15:52.570 align:start position:0% I have missed connected and it every 00:15:52.570 --> 00:15:55.380 align:start position:0% I have missed connected and it every whenever<00:15:53.350> I<00:15:53.440> have<00:15:53.680> an<00:15:53.830> updated<00:15:54.400> lock<00:15:54.790> it<00:15:55.120> keeps 00:15:55.380 --> 00:15:55.390 align:start position:0% whenever I have an updated lock it keeps 00:15:55.390 --> 00:15:57.660 align:start position:0% whenever I have an updated lock it keeps requesting<00:15:55.930> the<00:15:56.110> same<00:15:56.440> balance<00:15:57.190> for<00:15:57.370> the<00:15:57.460> same 00:15:57.660 --> 00:15:57.670 align:start position:0% requesting the same balance for the same 00:15:57.670 --> 00:15:59.160 align:start position:0% requesting the same balance for the same account<00:15:58.000> over<00:15:58.300> and<00:15:58.420> over<00:15:58.570> and<00:15:58.690> over<00:15:58.720> and<00:15:58.960> over 00:15:59.160 --> 00:15:59.170 align:start position:0% account over and over and over and over 00:15:59.170 --> 00:16:02.010 align:start position:0% account over and over and over and over again<00:15:59.290> the<00:16:00.250> light<00:16:00.490> servers<00:16:01.000> will<00:16:01.300> be<00:16:01.330> able<00:16:01.690> to 00:16:02.010 --> 00:16:02.020 align:start position:0% again the light servers will be able to 00:16:02.020 --> 00:16:04.110 align:start position:0% again the light servers will be able to create<00:16:02.200> a<00:16:02.290> statistically<00:16:03.100> map<00:16:03.280> out<00:16:03.550> that<00:16:03.910> this 00:16:04.110 --> 00:16:04.120 align:start position:0% create a statistically map out that this 00:16:04.120 --> 00:16:06.660 align:start position:0% create a statistically map out that this particular<00:16:04.690> IP<00:16:05.290> address<00:16:05.890> is<00:16:06.010> interested<00:16:06.550> in 00:16:06.660 --> 00:16:06.670 align:start position:0% particular IP address is interested in 00:16:06.670 --> 00:16:09.630 align:start position:0% particular IP address is interested in one<00:16:07.240> particular<00:16:07.480> address<00:16:08.260> and<00:16:08.530> that's<00:16:09.490> a 00:16:09.630 --> 00:16:09.640 align:start position:0% one particular address and that's a 00:16:09.640 --> 00:16:12.420 align:start position:0% one particular address and that's a problem<00:16:10.180> because<00:16:10.570> we<00:16:10.840> got<00:16:11.560> back<00:16:11.740> to<00:16:11.890> the<00:16:12.010> exact 00:16:12.420 --> 00:16:12.430 align:start position:0% problem because we got back to the exact 00:16:12.430 --> 00:16:14.730 align:start position:0% problem because we got back to the exact same<00:16:12.970> issue<00:16:13.330> an<00:16:13.600> exact<00:16:13.960> same<00:16:14.170> behavior<00:16:14.710> that 00:16:14.730 --> 00:16:14.740 align:start position:0% same issue an exact same behavior that 00:16:14.740 --> 00:16:17.040 align:start position:0% same issue an exact same behavior that we<00:16:15.040> had<00:16:15.250> with<00:16:15.460> the<00:16:15.520> discovery<00:16:15.970> protocol<00:16:16.450> only 00:16:17.040 --> 00:16:17.050 align:start position:0% we had with the discovery protocol only 00:16:17.050 --> 00:16:20.880 align:start position:0% we had with the discovery protocol only now<00:16:17.380> we<00:16:17.440> don't<00:16:17.710> have<00:16:17.860> a<00:16:19.050> map<00:16:20.050> world<00:16:20.410> map<00:16:20.680> of 00:16:20.880 --> 00:16:20.890 align:start position:0% now we don't have a map world map of 00:16:20.890 --> 00:16:23.190 align:start position:0% now we don't have a map world map of moving<00:16:21.340> IDs<00:16:22.000> now<00:16:22.210> we<00:16:22.270> have<00:16:22.510> a<00:16:22.540> world<00:16:22.810> map<00:16:22.960> of 00:16:23.190 --> 00:16:23.200 align:start position:0% moving IDs now we have a world map of 00:16:23.200 --> 00:16:25.920 align:start position:0% moving IDs now we have a world map of moving<00:16:23.650> etherium<00:16:24.160> addresses<00:16:24.640> and<00:16:24.930> again 00:16:25.920 --> 00:16:25.930 align:start position:0% moving etherium addresses and again 00:16:25.930 --> 00:16:28.050 align:start position:0% moving etherium addresses and again similarly<00:16:26.890> for<00:16:27.100> the<00:16:27.160> discovery<00:16:27.550> protocol 00:16:28.050 --> 00:16:28.060 align:start position:0% similarly for the discovery protocol 00:16:28.060 --> 00:16:29.880 align:start position:0% similarly for the discovery protocol this<00:16:28.300> can<00:16:28.600> be<00:16:28.750> done<00:16:28.990> exactly<00:16:29.200> the<00:16:29.590> same<00:16:29.650> way 00:16:29.880 --> 00:16:29.890 align:start position:0% this can be done exactly the same way 00:16:29.890 --> 00:16:32.190 align:start position:0% this can be done exactly the same way publicly<00:16:30.550> by<00:16:30.670> everyone<00:16:31.090> it's<00:16:31.720> a<00:16:31.840> bit<00:16:32.020> more 00:16:32.190 --> 00:16:32.200 align:start position:0% publicly by everyone it's a bit more 00:16:32.200 --> 00:16:33.420 align:start position:0% publicly by everyone it's a bit more expensive<00:16:32.320> because<00:16:32.770> you<00:16:33.010> need<00:16:33.160> to<00:16:33.250> run<00:16:33.370> a 00:16:33.420 --> 00:16:33.430 align:start position:0% expensive because you need to run a 00:16:33.430 --> 00:16:35.340 align:start position:0% expensive because you need to run a light<00:16:33.700> server<00:16:34.000> so<00:16:34.630> at<00:16:34.750> least<00:16:34.870> you're<00:16:35.050> having 00:16:35.340 --> 00:16:35.350 align:start position:0% light server so at least you're having 00:16:35.350 --> 00:16:37.110 align:start position:0% light server so at least you're having the<00:16:35.440> network<00:16:35.740> so<00:16:35.920> please<00:16:36.640> if<00:16:36.820> you<00:16:36.910> want<00:16:37.000> to 00:16:37.110 --> 00:16:37.120 align:start position:0% the network so please if you want to 00:16:37.120 --> 00:16:38.610 align:start position:0% the network so please if you want to attack<00:16:37.390> it<00:16:37.420> and<00:16:37.660> do<00:16:37.870> this<00:16:38.050> and<00:16:38.290> not<00:16:38.350> the<00:16:38.500> other 00:16:38.610 --> 00:16:38.620 align:start position:0% attack it and do this and not the other 00:16:38.620 --> 00:16:43.140 align:start position:0% attack it and do this and not the other fund<00:16:40.050> so<00:16:41.050> how<00:16:41.230> can<00:16:41.460> how<00:16:42.460> can<00:16:42.640> we<00:16:42.700> solve<00:16:42.910> this 00:16:43.140 --> 00:16:43.150 align:start position:0% fund so how can how can we solve this 00:16:43.150 --> 00:16:47.310 align:start position:0% fund so how can how can we solve this and<00:16:43.660> again<00:16:44.230> it's<00:16:44.440> a<00:16:44.560> it's<00:16:45.040> a<00:16:45.220> hard<00:16:45.900> question<00:16:46.900> to 00:16:47.310 --> 00:16:47.320 align:start position:0% and again it's a it's a hard question to 00:16:47.320 --> 00:16:49.200 align:start position:0% and again it's a it's a hard question to answer<00:16:47.440> because<00:16:47.890> it's<00:16:48.220> not<00:16:48.400> it's<00:16:48.790> kind<00:16:49.060> of 00:16:49.200 --> 00:16:49.210 align:start position:0% answer because it's not it's kind of 00:16:49.210 --> 00:16:51.030 align:start position:0% answer because it's not it's kind of this<00:16:49.390> is<00:16:49.600> how<00:16:49.840> the<00:16:49.900> protocol<00:16:50.380> was<00:16:50.560> meant<00:16:50.800> to<00:16:50.890> be 00:16:51.030 --> 00:16:51.040 align:start position:0% this is how the protocol was meant to be 00:16:51.040 --> 00:16:53.250 align:start position:0% this is how the protocol was meant to be this<00:16:51.190> is<00:16:51.340> the<00:16:51.370> optimization<00:16:51.910> so<00:16:52.870> we're<00:16:52.990> trying 00:16:53.250 --> 00:16:53.260 align:start position:0% this is the optimization so we're trying 00:16:53.260 --> 00:16:55.560 align:start position:0% this is the optimization so we're trying to<00:16:53.380> somehow<00:16:53.560> obfuscate<00:16:54.280> the<00:16:54.570> optimization 00:16:55.560 --> 00:16:55.570 align:start position:0% to somehow obfuscate the optimization 00:16:55.570 --> 00:16:59.520 align:start position:0% to somehow obfuscate the optimization and<00:16:56.910> one<00:16:57.910> of<00:16:58.030> them<00:16:58.240> is<00:16:58.510> again<00:16:58.870> similarly<00:16:59.320> to 00:16:59.520 --> 00:16:59.530 align:start position:0% and one of them is again similarly to 00:16:59.530 --> 00:17:02.190 align:start position:0% and one of them is again similarly to how<00:16:59.650> we<00:16:59.710> try<00:17:00.310> to<00:17:00.370> hide<00:17:00.640> our<00:17:00.820> IP<00:17:01.390> address<00:17:01.930> from 00:17:02.190 --> 00:17:02.200 align:start position:0% how we try to hide our IP address from 00:17:02.200 --> 00:17:04.380 align:start position:0% how we try to hide our IP address from ether<00:17:02.530> scan<00:17:02.800> or<00:17:03.010> from<00:17:03.400> centralized<00:17:04.120> the 00:17:04.380 --> 00:17:04.390 align:start position:0% ether scan or from centralized the 00:17:04.390 --> 00:17:06.720 align:start position:0% ether scan or from centralized the restful<00:17:04.780> services<00:17:05.170> we<00:17:05.830> can<00:17:06.010> try<00:17:06.280> to<00:17:06.339> do<00:17:06.610> the 00:17:06.720 --> 00:17:06.730 align:start position:0% restful services we can try to do the 00:17:06.730 --> 00:17:08.730 align:start position:0% restful services we can try to do the same<00:17:06.940> thing<00:17:07.180> and<00:17:07.360> maybe<00:17:07.510> run<00:17:07.839> live<00:17:08.230> clients<00:17:08.620> of 00:17:08.730 --> 00:17:08.740 align:start position:0% same thing and maybe run live clients of 00:17:08.740 --> 00:17:13.140 align:start position:0% same thing and maybe run live clients of over<00:17:09.070> tor<00:17:09.600> but<00:17:11.310> what<00:17:12.310> happens<00:17:12.670> if<00:17:12.790> I<00:17:12.910> have<00:17:13.030> an 00:17:13.140 --> 00:17:13.150 align:start position:0% over tor but what happens if I have an 00:17:13.150 --> 00:17:15.210 align:start position:0% over tor but what happens if I have an embedded<00:17:13.510> device<00:17:13.600> so<00:17:14.380> about<00:17:14.589> two<00:17:14.770> weeks<00:17:15.040> ago 00:17:15.210 --> 00:17:15.220 align:start position:0% embedded device so about two weeks ago 00:17:15.220 --> 00:17:17.550 align:start position:0% embedded device so about two weeks ago no<00:17:15.700> sorry<00:17:15.970> two<00:17:16.209> years<00:17:16.480> ago<00:17:16.750> you've<00:17:17.350> already 00:17:17.550 --> 00:17:17.560 align:start position:0% no sorry two years ago you've already 00:17:17.560 --> 00:17:20.280 align:start position:0% no sorry two years ago you've already had<00:17:17.980> raspberry<00:17:18.760> pi<00:17:18.940> zeros<00:17:19.360> as<00:17:19.660> live<00:17:19.839> clients 00:17:20.280 --> 00:17:20.290 align:start position:0% had raspberry pi zeros as live clients 00:17:20.290 --> 00:17:22.670 align:start position:0% had raspberry pi zeros as live clients on<00:17:20.380> may<00:17:20.500> not<00:17:20.740> somebody<00:17:21.640> even<00:17:21.730> had<00:17:22.060> this<00:17:22.270> little 00:17:22.670 --> 00:17:22.680 align:start position:0% on may not somebody even had this little 00:17:22.680 --> 00:17:25.530 align:start position:0% on may not somebody even had this little Intel<00:17:23.680> and<00:17:23.920> buy<00:17:24.040> the<00:17:24.100> chips<00:17:24.430> put<00:17:25.000> on<00:17:25.150> may<00:17:25.300> not 00:17:25.530 --> 00:17:25.540 align:start position:0% Intel and buy the chips put on may not 00:17:25.540 --> 00:17:26.760 align:start position:0% Intel and buy the chips put on may not and<00:17:25.780> they<00:17:25.900> were<00:17:25.990> really<00:17:26.140> happy<00:17:26.500> that<00:17:26.650> they 00:17:26.760 --> 00:17:26.770 align:start position:0% and they were really happy that they 00:17:26.770 --> 00:17:29.730 align:start position:0% and they were really happy that they could<00:17:26.980> they<00:17:27.550> can<00:17:27.700> use<00:17:27.850> the<00:17:27.970> light<00:17:28.120> client<00:17:28.740> but 00:17:29.730 --> 00:17:29.740 align:start position:0% could they can use the light client but 00:17:29.740 --> 00:17:31.290 align:start position:0% could they can use the light client but these<00:17:29.950> devices<00:17:30.370> aren't<00:17:30.580> really<00:17:30.730> compatible 00:17:31.290 --> 00:17:31.300 align:start position:0% these devices aren't really compatible 00:17:31.300 --> 00:17:33.300 align:start position:0% these devices aren't really compatible with<00:17:31.450> tours<00:17:31.750> so<00:17:31.960> tour<00:17:32.170> has<00:17:32.410> a<00:17:32.440> huge<00:17:32.770> overhead 00:17:33.300 --> 00:17:33.310 align:start position:0% with tours so tour has a huge overhead 00:17:33.310 --> 00:17:35.970 align:start position:0% with tours so tour has a huge overhead cryptographic<00:17:33.970> overhead<00:17:34.800> that's<00:17:35.800> one 00:17:35.970 --> 00:17:35.980 align:start position:0% cryptographic overhead that's one 00:17:35.980 --> 00:17:38.130 align:start position:0% cryptographic overhead that's one problem<00:17:36.190> the<00:17:36.490> other<00:17:36.520> problem<00:17:37.030> is<00:17:37.120> that<00:17:37.150> if<00:17:37.690> we 00:17:38.130 --> 00:17:38.140 align:start position:0% problem the other problem is that if we 00:17:38.140 --> 00:17:42.030 align:start position:0% problem the other problem is that if we start<00:17:38.200> adding<00:17:38.890> this<00:17:39.420> these<00:17:40.420> IP<00:17:41.080> mixers<00:17:41.740> into 00:17:42.030 --> 00:17:42.040 align:start position:0% start adding this these IP mixers into 00:17:42.040 --> 00:17:44.700 align:start position:0% start adding this these IP mixers into the<00:17:42.190> soup<00:17:43.030> and<00:17:43.330> trying<00:17:43.630> to<00:17:43.930> just<00:17:44.170> create 00:17:44.700 --> 00:17:44.710 align:start position:0% the soup and trying to just create 00:17:44.710 --> 00:17:46.890 align:start position:0% the soup and trying to just create trying<00:17:45.610> to<00:17:45.700> just<00:17:45.910> tunnel 00:17:46.890 --> 00:17:46.900 align:start position:0% trying to just tunnel 00:17:46.900 --> 00:17:48.540 align:start position:0% trying to just tunnel light<00:17:47.050> client<00:17:47.560> traffic<00:17:47.860> all<00:17:47.980> over<00:17:48.220> the<00:17:48.340> place 00:17:48.540 --> 00:17:48.550 align:start position:0% light client traffic all over the place 00:17:48.550 --> 00:17:50.040 align:start position:0% light client traffic all over the place the<00:17:49.300> issue<00:17:49.480> is<00:17:49.570> that<00:17:49.600> you<00:17:49.840> will<00:17:50.020> have 00:17:50.040 --> 00:17:50.050 align:start position:0% the issue is that you will have 00:17:50.050 --> 00:17:52.860 align:start position:0% the issue is that you will have connectivity<00:17:50.650> issues<00:17:51.190> so<00:17:51.550> again<00:17:51.760> maybe<00:17:52.630> you 00:17:52.860 --> 00:17:52.870 align:start position:0% connectivity issues so again maybe you 00:17:52.870 --> 00:17:55.500 align:start position:0% connectivity issues so again maybe you will<00:17:53.050> find<00:17:53.470> less<00:17:53.800> peers<00:17:54.190> maybe<00:17:54.820> the<00:17:55.030> latency 00:17:55.500 --> 00:17:55.510 align:start position:0% will find less peers maybe the latency 00:17:55.510 --> 00:17:57.150 align:start position:0% will find less peers maybe the latency will<00:17:55.660> go<00:17:55.840> up<00:17:56.050> the<00:17:56.230> bandwidth<00:17:56.590> will<00:17:56.740> go<00:17:56.920> down 00:17:57.150 --> 00:17:57.160 align:start position:0% will go up the bandwidth will go down 00:17:57.160 --> 00:17:59.880 align:start position:0% will go up the bandwidth will go down you<00:17:57.460> will<00:17:57.610> keep<00:17:57.910> dropping<00:17:58.150> peers<00:17:58.770> but<00:17:59.770> the 00:17:59.880 --> 00:17:59.890 align:start position:0% you will keep dropping peers but the 00:17:59.890 --> 00:18:01.230 align:start position:0% you will keep dropping peers but the issue<00:18:00.010> here<00:18:00.310> is<00:18:00.430> that<00:18:00.460> as<00:18:00.730> I<00:18:00.760> said<00:18:00.910> previously 00:18:01.230 --> 00:18:01.240 align:start position:0% issue here is that as I said previously 00:18:01.240 --> 00:18:03.570 align:start position:0% issue here is that as I said previously live<00:18:01.720> clients<00:18:02.110> depend<00:18:02.530> on<00:18:02.770> relatively<00:18:03.430> good 00:18:03.570 --> 00:18:03.580 align:start position:0% live clients depend on relatively good 00:18:03.580 --> 00:18:06.390 align:start position:0% live clients depend on relatively good connectivity<00:18:03.910> if<00:18:04.570> you<00:18:05.020> have<00:18:05.230> a<00:18:06.100> an 00:18:06.390 --> 00:18:06.400 align:start position:0% connectivity if you have a an 00:18:06.400 --> 00:18:08.460 align:start position:0% connectivity if you have a an application<00:18:07.120> layer<00:18:07.270> that<00:18:07.720> essentially<00:18:08.230> kills 00:18:08.460 --> 00:18:08.470 align:start position:0% application layer that essentially kills 00:18:08.470 --> 00:18:10.020 align:start position:0% application layer that essentially kills your<00:18:08.620> connectivity<00:18:09.040> then<00:18:09.700> all<00:18:09.820> of<00:18:09.850> a<00:18:10.000> sudden 00:18:10.020 --> 00:18:10.030 align:start position:0% your connectivity then all of a sudden 00:18:10.030 --> 00:18:13.740 align:start position:0% your connectivity then all of a sudden you<00:18:11.400> kind<00:18:12.400> of<00:18:12.520> raise<00:18:12.760> your<00:18:13.030> vulnerability 00:18:13.740 --> 00:18:13.750 align:start position:0% you kind of raise your vulnerability 00:18:13.750 --> 00:18:15.450 align:start position:0% you kind of raise your vulnerability against<00:18:14.170> these<00:18:14.470> kinds<00:18:14.740> of<00:18:14.800> eclipsed<00:18:15.130> attacks 00:18:15.450 --> 00:18:15.460 align:start position:0% against these kinds of eclipsed attacks 00:18:15.460 --> 00:18:19.200 align:start position:0% against these kinds of eclipsed attacks so<00:18:16.180> again<00:18:16.420> although<00:18:17.280> it<00:18:18.280> seems<00:18:18.760> that<00:18:19.000> there 00:18:19.200 --> 00:18:19.210 align:start position:0% so again although it seems that there 00:18:19.210 --> 00:18:21.600 align:start position:0% so again although it seems that there would<00:18:19.360> be<00:18:19.390> a<00:18:19.570> simple<00:18:19.990> enough<00:18:20.110> solution<00:18:20.740> in 00:18:21.600 --> 00:18:21.610 align:start position:0% would be a simple enough solution in 00:18:21.610 --> 00:18:26.310 align:start position:0% would be a simple enough solution in practice<00:18:22.150> it's<00:18:22.390> not<00:18:22.630> so<00:18:23.020> trivial<00:18:23.940> so<00:18:25.320> with 00:18:26.310 --> 00:18:26.320 align:start position:0% practice it's not so trivial so with 00:18:26.320 --> 00:18:30.630 align:start position:0% practice it's not so trivial so with that<00:18:26.500> said<00:18:27.360> I<00:18:28.950> think<00:18:29.950> this<00:18:30.040> was<00:18:30.250> the<00:18:30.340> first 00:18:30.630 --> 00:18:30.640 align:start position:0% that said I think this was the first 00:18:30.640 --> 00:18:33.030 align:start position:0% that said I think this was the first talk<00:18:30.880> that<00:18:31.030> I<00:18:31.180> did<00:18:31.420> where<00:18:31.630> I<00:18:32.230> kind<00:18:32.770> of<00:18:32.860> raised 00:18:33.030 --> 00:18:33.040 align:start position:0% talk that I did where I kind of raised 00:18:33.040 --> 00:18:35.130 align:start position:0% talk that I did where I kind of raised more<00:18:33.340> questions<00:18:33.520> than<00:18:34.060> talks<00:18:34.390> and<00:18:34.750> then 00:18:35.130 --> 00:18:35.140 align:start position:0% more questions than talks and then 00:18:35.140 --> 00:18:38.580 align:start position:0% more questions than talks and then solutions<00:18:36.000> but<00:18:37.000> I<00:18:37.390> still<00:18:37.810> I<00:18:37.870> figured<00:18:38.350> that<00:18:38.500> I 00:18:38.580 --> 00:18:38.590 align:start position:0% solutions but I still I figured that I 00:18:38.590 --> 00:18:42.240 align:start position:0% solutions but I still I figured that I would<00:18:38.650> like<00:18:38.890> I<00:18:39.430> would<00:18:40.120> like<00:18:40.360> to<00:18:41.190> formulate<00:18:42.190> a 00:18:42.240 --> 00:18:42.250 align:start position:0% would like I would like to formulate a 00:18:42.250 --> 00:18:45.150 align:start position:0% would like I would like to formulate a few<00:18:42.490> takeaways<00:18:42.700> for<00:18:43.270> for<00:18:43.720> you<00:18:43.890> yes<00:18:44.890> so<00:18:45.010> that 00:18:45.150 --> 00:18:45.160 align:start position:0% few takeaways for for you yes so that 00:18:45.160 --> 00:18:47.250 align:start position:0% few takeaways for for you yes so that you<00:18:45.250> don't<00:18:45.430> don't<00:18:45.940> leave<00:18:46.180> with<00:18:46.750> with<00:18:47.170> the 00:18:47.250 --> 00:18:47.260 align:start position:0% you don't don't leave with with the 00:18:47.260 --> 00:18:51.780 align:start position:0% you don't don't leave with with the concept<00:18:47.620> that<00:18:47.650> ok<00:18:47.950> theorem<00:18:48.220> sucks<00:18:50.790> and 00:18:51.780 --> 00:18:51.790 align:start position:0% concept that ok theorem sucks and 00:18:51.790 --> 00:18:54.060 align:start position:0% concept that ok theorem sucks and essentially<00:18:52.540> the<00:18:52.720> three<00:18:53.530> things<00:18:53.800> that<00:18:53.950> I 00:18:54.060 --> 00:18:54.070 align:start position:0% essentially the three things that I 00:18:54.070 --> 00:18:57.990 align:start position:0% essentially the three things that I would<00:18:54.130> really<00:18:54.400> like<00:18:54.640> to<00:18:55.000> highlight<00:18:55.780> as<00:18:57.000> the 00:18:57.990 --> 00:18:58.000 align:start position:0% would really like to highlight as the 00:18:58.000 --> 00:19:01.380 align:start position:0% would really like to highlight as the summary<00:18:58.300> of<00:18:58.420> this<00:18:58.570> talk<00:18:58.840> is<00:18:59.200> that<00:19:00.390> although 00:19:01.380 --> 00:19:01.390 align:start position:0% summary of this talk is that although 00:19:01.390 --> 00:19:03.420 align:start position:0% summary of this talk is that although people<00:19:01.780> don't<00:19:01.990> feel<00:19:02.230> like<00:19:02.380> full<00:19:02.650> notes<00:19:02.920> full 00:19:03.420 --> 00:19:03.430 align:start position:0% people don't feel like full notes full 00:19:03.430 --> 00:19:05.460 align:start position:0% people don't feel like full notes full notes<00:19:03.670> are<00:19:03.940> actually<00:19:04.180> the<00:19:04.630> best<00:19:04.840> anonymizer 00:19:05.460 --> 00:19:05.470 align:start position:0% notes are actually the best anonymizer 00:19:05.470 --> 00:19:07.560 align:start position:0% notes are actually the best anonymizer in<00:19:05.980> a<00:19:06.250> theorem<00:19:06.550> ecosystem<00:19:07.180> if<00:19:07.330> you<00:19:07.510> are 00:19:07.560 --> 00:19:07.570 align:start position:0% in a theorem ecosystem if you are 00:19:07.570 --> 00:19:09.630 align:start position:0% in a theorem ecosystem if you are running<00:19:07.750> a<00:19:07.900> full<00:19:08.140> note<00:19:08.350> then<00:19:09.220> nobody<00:19:09.550> knows 00:19:09.630 --> 00:19:09.640 align:start position:0% running a full note then nobody knows 00:19:09.640 --> 00:19:11.340 align:start position:0% running a full note then nobody knows what<00:19:10.000> data<00:19:10.210> you're<00:19:10.450> interested<00:19:11.050> in 00:19:11.340 --> 00:19:11.350 align:start position:0% what data you're interested in 00:19:11.350 --> 00:19:13.560 align:start position:0% what data you're interested in you<00:19:12.010> can't<00:19:12.220> poke<00:19:12.490> in<00:19:12.670> whatever<00:19:12.850> contract<00:19:13.480> you 00:19:13.560 --> 00:19:13.570 align:start position:0% you can't poke in whatever contract you 00:19:13.570 --> 00:19:15.150 align:start position:0% you can't poke in whatever contract you want<00:19:13.750> you<00:19:13.870> can<00:19:14.050> check<00:19:14.230> your<00:19:14.380> balance<00:19:14.440> as<00:19:14.950> many 00:19:15.150 --> 00:19:15.160 align:start position:0% want you can check your balance as many 00:19:15.160 --> 00:19:17.430 align:start position:0% want you can check your balance as many times<00:19:15.430> per<00:19:15.700> second<00:19:16.060> as<00:19:16.180> you<00:19:16.210> want<00:19:16.510> and<00:19:16.720> nobody 00:19:17.430 --> 00:19:17.440 align:start position:0% times per second as you want and nobody 00:19:17.440 --> 00:19:19.050 align:start position:0% times per second as you want and nobody from<00:19:17.560> the<00:19:17.740> outside<00:19:18.130> will<00:19:18.400> know<00:19:18.640> that<00:19:18.670> you're 00:19:19.050 --> 00:19:19.060 align:start position:0% from the outside will know that you're 00:19:19.060 --> 00:19:24.390 align:start position:0% from the outside will know that you're actually<00:19:19.210> doing<00:19:19.570> it<00:19:21.120> secondly<00:19:23.340> privacy<00:19:24.340> on 00:19:24.390 --> 00:19:24.400 align:start position:0% actually doing it secondly privacy on 00:19:24.400 --> 00:19:26.690 align:start position:0% actually doing it secondly privacy on this<00:19:24.520> theorem<00:19:24.730> is<00:19:25.000> bad<00:19:25.390> really<00:19:25.990> really<00:19:26.350> bad 00:19:26.690 --> 00:19:26.700 align:start position:0% this theorem is bad really really bad 00:19:26.700 --> 00:19:29.910 align:start position:0% this theorem is bad really really bad and<00:19:27.700> that<00:19:27.820> but<00:19:28.240> this<00:19:28.390> doesn't<00:19:28.570> mean<00:19:28.840> that<00:19:28.920> it's 00:19:29.910 --> 00:19:29.920 align:start position:0% and that but this doesn't mean that it's 00:19:29.920 --> 00:19:32.310 align:start position:0% and that but this doesn't mean that it's an<00:19:30.370> impossible<00:19:30.700> task<00:19:30.970> to<00:19:31.300> solve<00:19:31.510> so<00:19:32.140> there 00:19:32.310 --> 00:19:32.320 align:start position:0% an impossible task to solve so there 00:19:32.320 --> 00:19:34.290 align:start position:0% an impossible task to solve so there have<00:19:32.500> been<00:19:32.530> existing<00:19:33.370> projects<00:19:33.910> that<00:19:34.060> it's 00:19:34.290 --> 00:19:34.300 align:start position:0% have been existing projects that it's 00:19:34.300 --> 00:19:36.360 align:start position:0% have been existing projects that it's two<00:19:34.510> major<00:19:34.720> ones<00:19:35.020> the<00:19:35.170> Tor<00:19:35.380> network<00:19:35.530> The<00:19:36.100> Onion 00:19:36.360 --> 00:19:36.370 align:start position:0% two major ones the Tor network The Onion 00:19:36.370 --> 00:19:39.510 align:start position:0% two major ones the Tor network The Onion Routing<00:19:36.460> Network<00:19:36.910> I<00:19:37.060> mean<00:19:37.240> and<00:19:37.710> I<00:19:38.710> to<00:19:38.920> pee<00:19:39.310> and 00:19:39.510 --> 00:19:39.520 align:start position:0% Routing Network I mean and I to pee and 00:19:39.520 --> 00:19:41.910 align:start position:0% Routing Network I mean and I to pee and both<00:19:40.180> these<00:19:40.390> networks<00:19:40.840> try<00:19:41.200> to<00:19:41.260> solve<00:19:41.740> this 00:19:41.910 --> 00:19:41.920 align:start position:0% both these networks try to solve this 00:19:41.920 --> 00:19:44.130 align:start position:0% both these networks try to solve this exact<00:19:42.340> problem<00:19:42.460> of<00:19:43.090> how<00:19:43.240> to<00:19:43.300> anonymize<00:19:43.810> data 00:19:44.130 --> 00:19:44.140 align:start position:0% exact problem of how to anonymize data 00:19:44.140 --> 00:19:46.530 align:start position:0% exact problem of how to anonymize data so<00:19:44.830> that<00:19:45.010> you<00:19:45.160> don't<00:19:45.370> reveal<00:19:45.970> too<00:19:46.180> much<00:19:46.210> about 00:19:46.530 --> 00:19:46.540 align:start position:0% so that you don't reveal too much about 00:19:46.540 --> 00:19:49.830 align:start position:0% so that you don't reveal too much about yourself<00:19:46.770> now<00:19:47.770> I'm<00:19:48.430> not<00:19:48.670> saying<00:19:48.880> that<00:19:49.150> we 00:19:49.830 --> 00:19:49.840 align:start position:0% yourself now I'm not saying that we 00:19:49.840 --> 00:19:51.750 align:start position:0% yourself now I'm not saying that we should<00:19:50.110> all<00:19:50.320> of<00:19:50.470> a<00:19:50.560> sudden<00:19:50.800> put<00:19:51.010> a<00:19:51.220> theorem<00:19:51.670> on 00:19:51.750 --> 00:19:51.760 align:start position:0% should all of a sudden put a theorem on 00:19:51.760 --> 00:19:53.220 align:start position:0% should all of a sudden put a theorem on top<00:19:51.910> of<00:19:52.030> these<00:19:52.180> networks<00:19:52.450> these<00:19:52.840> networks 00:19:53.220 --> 00:19:53.230 align:start position:0% top of these networks these networks 00:19:53.230 --> 00:19:56.010 align:start position:0% top of these networks these networks have<00:19:53.440> a<00:19:53.470> very<00:19:53.890> very<00:19:54.130> broad<00:19:54.340> scope<00:19:55.090> and<00:19:55.450> it 00:19:56.010 --> 00:19:56.020 align:start position:0% have a very very broad scope and it 00:19:56.020 --> 00:19:58.260 align:start position:0% have a very very broad scope and it might<00:19:56.230> be<00:19:56.380> too<00:19:56.560> much<00:19:56.710> but<00:19:57.490> nonetheless<00:19:57.700> there 00:19:58.260 --> 00:19:58.270 align:start position:0% might be too much but nonetheless there 00:19:58.270 --> 00:20:00.090 align:start position:0% might be too much but nonetheless there have<00:19:58.420> been<00:19:58.570> 20<00:19:58.960> years<00:19:58.990> of<00:19:59.290> research<00:19:59.470> going 00:20:00.090 --> 00:20:00.100 align:start position:0% have been 20 years of research going 00:20:00.100 --> 00:20:00.720 align:start position:0% have been 20 years of research going going 00:20:00.720 --> 00:20:00.730 align:start position:0% going 00:20:00.730 --> 00:20:02.789 align:start position:0% going to<00:20:00.850> how<00:20:01.000> to<00:20:01.059> do<00:20:01.270> this<00:20:01.419> properly<00:20:01.690> so<00:20:02.380> let's<00:20:02.559> try 00:20:02.789 --> 00:20:02.799 align:start position:0% to how to do this properly so let's try 00:20:02.799 --> 00:20:05.669 align:start position:0% to how to do this properly so let's try to<00:20:02.860> at<00:20:03.040> least<00:20:03.070> learn<00:20:03.549> from<00:20:03.940> their<00:20:04.530> results<00:20:05.530> and 00:20:05.669 --> 00:20:05.679 align:start position:0% to at least learn from their results and 00:20:05.679 --> 00:20:10.560 align:start position:0% to at least learn from their results and try<00:20:05.830> to<00:20:05.890> fix<00:20:06.549> it<00:20:06.730> and<00:20:09.000> last<00:20:10.000> but<00:20:10.150> not<00:20:10.299> least 00:20:10.560 --> 00:20:10.570 align:start position:0% try to fix it and last but not least 00:20:10.570 --> 00:20:13.380 align:start position:0% try to fix it and last but not least I've<00:20:11.440> seen<00:20:11.980> it<00:20:12.130> many<00:20:12.429> times<00:20:12.549> in<00:20:12.910> the<00:20:13.000> community 00:20:13.380 --> 00:20:13.390 align:start position:0% I've seen it many times in the community 00:20:13.390 --> 00:20:14.909 align:start position:0% I've seen it many times in the community and<00:20:13.510> I<00:20:13.570> see<00:20:13.750> it<00:20:13.840> many<00:20:13.960> times<00:20:14.260> even<00:20:14.440> with<00:20:14.710> myself 00:20:14.909 --> 00:20:14.919 align:start position:0% and I see it many times even with myself 00:20:14.919 --> 00:20:17.280 align:start position:0% and I see it many times even with myself that<00:20:15.549> as<00:20:15.790> a<00:20:15.850> developer<00:20:16.059> it's<00:20:16.540> all<00:20:16.809> too<00:20:17.020> easy<00:20:17.049> to 00:20:17.280 --> 00:20:17.290 align:start position:0% that as a developer it's all too easy to 00:20:17.290 --> 00:20:19.140 align:start position:0% that as a developer it's all too easy to just<00:20:17.410> say<00:20:17.770> that<00:20:17.980> well<00:20:18.220> the<00:20:18.520> users<00:20:18.850> are<00:20:19.000> doing 00:20:19.140 --> 00:20:19.150 align:start position:0% just say that well the users are doing 00:20:19.150 --> 00:20:22.110 align:start position:0% just say that well the users are doing it<00:20:19.390> wrong<00:20:19.600> and<00:20:20.580> for<00:20:21.580> example<00:20:21.880> it<00:20:21.970> would<00:20:22.059> be 00:20:22.110 --> 00:20:22.120 align:start position:0% it wrong and for example it would be 00:20:22.120 --> 00:20:23.820 align:start position:0% it wrong and for example it would be nice<00:20:22.450> to<00:20:22.630> say<00:20:22.750> that<00:20:22.900> well<00:20:23.080> just<00:20:23.470> you<00:20:23.559> store 00:20:23.820 --> 00:20:23.830 align:start position:0% nice to say that well just you store 00:20:23.830 --> 00:20:26.039 align:start position:0% nice to say that well just you store figure<00:20:24.130> it<00:20:24.250> out<00:20:24.370> and<00:20:25.059> that's<00:20:25.570> a<00:20:25.720> problem 00:20:26.039 --> 00:20:26.049 align:start position:0% figure it out and that's a problem 00:20:26.049 --> 00:20:27.539 align:start position:0% figure it out and that's a problem because<00:20:26.140> most<00:20:26.559> users<00:20:26.740> don't<00:20:27.160> know<00:20:27.370> what 00:20:27.539 --> 00:20:27.549 align:start position:0% because most users don't know what 00:20:27.549 --> 00:20:29.100 align:start position:0% because most users don't know what tories<00:20:27.970> and<00:20:28.179> most<00:20:28.330> users<00:20:28.600> will<00:20:28.780> probably 00:20:29.100 --> 00:20:29.110 align:start position:0% tories and most users will probably 00:20:29.110 --> 00:20:30.659 align:start position:0% tories and most users will probably never<00:20:29.200> in<00:20:29.380> their<00:20:29.530> lives<00:20:29.740> you<00:20:30.040> store<00:20:30.520> even 00:20:30.659 --> 00:20:30.669 align:start position:0% never in their lives you store even 00:20:30.669 --> 00:20:32.250 align:start position:0% never in their lives you store even though<00:20:30.850> that<00:20:31.270> would<00:20:31.480> be<00:20:31.540> the<00:20:31.720> obvious 00:20:32.250 --> 00:20:32.260 align:start position:0% though that would be the obvious 00:20:32.260 --> 00:20:34.770 align:start position:0% though that would be the obvious solution<00:20:32.679> and<00:20:33.280> it's<00:20:33.580> kind<00:20:33.730> of<00:20:33.790> up<00:20:33.970> us<00:20:34.210> up<00:20:34.510> to<00:20:34.660> us 00:20:34.770 --> 00:20:34.780 align:start position:0% solution and it's kind of up us up to us 00:20:34.780 --> 00:20:37.289 align:start position:0% solution and it's kind of up us up to us to<00:20:34.929> as<00:20:35.080> the<00:20:35.830> app<00:20:35.890> and<00:20:36.160> platform<00:20:36.610> developers<00:20:37.090> to 00:20:37.289 --> 00:20:37.299 align:start position:0% to as the app and platform developers to 00:20:37.299 --> 00:20:41.310 align:start position:0% to as the app and platform developers to figure<00:20:37.600> it<00:20:37.750> out<00:20:37.870> and<00:20:38.080> to<00:20:38.200> fix<00:20:38.440> it<00:20:38.650> and<00:20:40.200> we<00:20:41.200> don't 00:20:41.310 --> 00:20:41.320 align:start position:0% figure it out and to fix it and we don't 00:20:41.320 --> 00:20:42.810 align:start position:0% figure it out and to fix it and we don't really<00:20:41.620> want<00:20:41.799> to<00:20:41.890> fix<00:20:42.160> it<00:20:42.309> to<00:20:42.429> protect<00:20:42.730> the 00:20:42.810 --> 00:20:42.820 align:start position:0% really want to fix it to protect the 00:20:42.820 --> 00:20:45.539 align:start position:0% really want to fix it to protect the users<00:20:43.120> from<00:20:43.710> not<00:20:44.710> only<00:20:44.740> from<00:20:45.070> external 00:20:45.539 --> 00:20:45.549 align:start position:0% users from not only from external 00:20:45.549 --> 00:20:46.830 align:start position:0% users from not only from external attacks<00:20:45.850> I<00:20:46.000> think<00:20:46.030> it's<00:20:46.270> really<00:20:46.390> important<00:20:46.780> to 00:20:46.830 --> 00:20:46.840 align:start position:0% attacks I think it's really important to 00:20:46.840 --> 00:20:48.030 align:start position:0% attacks I think it's really important to also<00:20:46.960> highlight<00:20:47.200> that<00:20:47.470> we<00:20:47.620> want<00:20:47.770> to<00:20:47.890> protect 00:20:48.030 --> 00:20:48.040 align:start position:0% also highlight that we want to protect 00:20:48.040 --> 00:20:51.960 align:start position:0% also highlight that we want to protect users<00:20:48.520> from<00:20:48.549> ourselves<00:20:48.880> too<00:20:49.679> because<00:20:50.679> I<00:20:50.970> just 00:20:51.960 --> 00:20:51.970 align:start position:0% users from ourselves too because I just 00:20:51.970 --> 00:20:53.310 align:start position:0% users from ourselves too because I just give<00:20:52.210> you<00:20:52.240> a<00:20:52.330> really<00:20:52.570> nice<00:20:52.750> example 00:20:53.310 --> 00:20:53.320 align:start position:0% give you a really nice example 00:20:53.320 --> 00:20:55.710 align:start position:0% give you a really nice example I<00:20:53.410> don't<00:20:53.620> think<00:20:53.710> Facebook<00:20:54.340> was<00:20:54.580> created<00:20:55.450> to 00:20:55.710 --> 00:20:55.720 align:start position:0% I don't think Facebook was created to 00:20:55.720 --> 00:20:58.560 align:start position:0% I don't think Facebook was created to gather<00:20:55.960> user<00:20:56.230> data<00:20:56.620> it<00:20:56.770> wasn't<00:20:57.070> created<00:20:57.520> to<00:20:57.570> to 00:20:58.560 --> 00:20:58.570 align:start position:0% gather user data it wasn't created to to 00:20:58.570 --> 00:21:01.340 align:start position:0% gather user data it wasn't created to to abuse<00:20:59.559> elections<00:21:00.100> that<00:21:00.520> one<00:21:00.730> just<00:21:00.940> kind<00:21:01.150> of 00:21:01.340 --> 00:21:01.350 align:start position:0% abuse elections that one just kind of 00:21:01.350 --> 00:21:08.070 align:start position:0% abuse elections that one just kind of happened<00:21:02.350> when<00:21:02.890> there<00:21:03.100> was<00:21:03.360> too<00:21:04.360> much<00:21:05.820> so<00:21:07.080> with 00:21:08.070 --> 00:21:08.080 align:start position:0% happened when there was too much so with 00:21:08.080 --> 00:21:11.610 align:start position:0% happened when there was too much so with that<00:21:08.260> I<00:21:09.299> conclude<00:21:10.299> my<00:21:10.600> talk<00:21:10.660> so<00:21:11.260> thank<00:21:11.530> you 00:21:11.610 --> 00:21:11.620 align:start position:0% that I conclude my talk so thank you 00:21:11.620 --> 00:21:17.770 align:start position:0% that I conclude my talk so thank you very<00:21:11.740> much 00:21:17.770 --> 00:21:17.780 align:start position:0% 00:21:17.780 --> 00:21:21.950 align:start position:0% and<00:21:18.780> I<00:21:18.990> guess<00:21:19.170> we<00:21:19.860> have<00:21:19.890> a<00:21:20.070> few<00:21:20.960> possible 00:21:21.950 --> 00:21:21.960 align:start position:0% and I guess we have a few possible 00:21:21.960 --> 00:21:23.750 align:start position:0% and I guess we have a few possible questions<00:21:22.320> a<00:21:22.590> few<00:21:22.920> minutes<00:21:23.160> for<00:21:23.280> questions<00:21:23.310> if 00:21:23.750 --> 00:21:23.760 align:start position:0% questions a few minutes for questions if 00:21:23.760 --> 00:21:30.230 align:start position:0% questions a few minutes for questions if I<00:21:23.820> may<00:21:23.940> hasn't<00:21:28.700> doesn't<00:21:29.700> look<00:21:29.790> like<00:21:29.970> we<00:21:30.090> have 00:21:30.230 --> 00:21:30.240 align:start position:0% I may hasn't doesn't look like we have 00:21:30.240 --> 00:21:35.090 align:start position:0% I may hasn't doesn't look like we have any<00:21:32.870> hey<00:21:33.870> could<00:21:34.680> you<00:21:34.740> talk<00:21:34.890> more<00:21:35.040> about 00:21:35.090 --> 00:21:35.100 align:start position:0% any hey could you talk more about 00:21:35.100 --> 00:21:36.860 align:start position:0% any hey could you talk more about helpful<00:21:35.580> notes<00:21:35.790> are<00:21:35.970> the<00:21:36.150> most<00:21:36.300> powerful<00:21:36.450> and 00:21:36.860 --> 00:21:36.870 align:start position:0% helpful notes are the most powerful and 00:21:36.870 --> 00:21:39.970 align:start position:0% helpful notes are the most powerful and atomizers<00:21:37.320> and<00:21:37.620> network<00:21:37.860> with<00:21:37.980> that<00:21:38.130> takeaway 00:21:39.970 --> 00:21:39.980 align:start position:0% atomizers and network with that takeaway 00:21:39.980 --> 00:21:44.090 align:start position:0% atomizers and network with that takeaway so<00:21:40.980> essentially<00:21:41.780> all<00:21:42.780> these<00:21:43.410> metadata<00:21:43.770> leaks 00:21:44.090 --> 00:21:44.100 align:start position:0% so essentially all these metadata leaks 00:21:44.100 --> 00:21:46.190 align:start position:0% so essentially all these metadata leaks as<00:21:44.280> are<00:21:44.490> possible<00:21:45.000> because<00:21:45.360> you<00:21:45.570> are<00:21:45.930> doing 00:21:46.190 --> 00:21:46.200 align:start position:0% as are possible because you are doing 00:21:46.200 --> 00:21:47.990 align:start position:0% as are possible because you are doing something<00:21:46.530> in<00:21:46.920> your<00:21:47.370> optimizing<00:21:47.970> your 00:21:47.990 --> 00:21:48.000 align:start position:0% something in your optimizing your 00:21:48.000 --> 00:21:49.520 align:start position:0% something in your optimizing your traffic<00:21:48.300> in<00:21:48.540> the<00:21:48.600> network<00:21:48.630> the<00:21:49.170> only<00:21:49.350> way<00:21:49.470> to 00:21:49.520 --> 00:21:49.530 align:start position:0% traffic in the network the only way to 00:21:49.530 --> 00:21:51.740 align:start position:0% traffic in the network the only way to optimize<00:21:49.860> your<00:21:50.040> traffic<00:21:50.400> is<00:21:50.700> to<00:21:51.210> request<00:21:51.450> only 00:21:51.740 --> 00:21:51.750 align:start position:0% optimize your traffic is to request only 00:21:51.750 --> 00:21:54.470 align:start position:0% optimize your traffic is to request only data<00:21:52.080> that<00:21:52.320> interests<00:21:52.830> you<00:21:52.980> so<00:21:53.270> every<00:21:54.270> time 00:21:54.470 --> 00:21:54.480 align:start position:0% data that interests you so every time 00:21:54.480 --> 00:21:56.000 align:start position:0% data that interests you so every time you<00:21:54.630> are<00:21:54.660> only<00:21:55.110> requesting<00:21:55.560> data<00:21:55.680> that 00:21:56.000 --> 00:21:56.010 align:start position:0% you are only requesting data that 00:21:56.010 --> 00:21:57.530 align:start position:0% you are only requesting data that interests<00:21:56.460> you<00:21:56.610> it<00:21:56.850> means<00:21:57.030> that<00:21:57.270> the<00:21:57.360> network 00:21:57.530 --> 00:21:57.540 align:start position:0% interests you it means that the network 00:21:57.540 --> 00:21:59.990 align:start position:0% interests you it means that the network itself<00:21:58.050> knows<00:21:58.410> that<00:21:58.770> that<00:21:59.280> particular<00:21:59.790> data 00:21:59.990 --> 00:22:00.000 align:start position:0% itself knows that that particular data 00:22:00.000 --> 00:22:01.910 align:start position:0% itself knows that that particular data for<00:22:00.330> some<00:22:00.480> reason<00:22:00.900> is<00:22:01.110> interesting<00:22:01.680> for<00:22:01.890> that 00:22:01.910 --> 00:22:01.920 align:start position:0% for some reason is interesting for that 00:22:01.920 --> 00:22:04.700 align:start position:0% for some reason is interesting for that particular<00:22:02.520> IP<00:22:02.640> address<00:22:03.060> and<00:22:03.240> this<00:22:04.140> thing<00:22:04.500> you 00:22:04.700 --> 00:22:04.710 align:start position:0% particular IP address and this thing you 00:22:04.710 --> 00:22:06.110 align:start position:0% particular IP address and this thing you can<00:22:04.950> completely<00:22:05.280> hide<00:22:05.520> the<00:22:05.760> phone<00:22:05.970> out 00:22:06.110 --> 00:22:06.120 align:start position:0% can completely hide the phone out 00:22:06.120 --> 00:22:07.850 align:start position:0% can completely hide the phone out because<00:22:06.750> the<00:22:06.870> FEU<00:22:06.990> node<00:22:07.200> essentially<00:22:07.710> gets 00:22:07.850 --> 00:22:07.860 align:start position:0% because the FEU node essentially gets 00:22:07.860 --> 00:22:17.660 align:start position:0% because the FEU node essentially gets everything<00:22:15.020> yes<00:22:16.020> so<00:22:16.350> that's<00:22:16.710> an<00:22:16.860> again 00:22:17.660 --> 00:22:17.670 align:start position:0% everything yes so that's an again 00:22:17.670 --> 00:22:19.460 align:start position:0% everything yes so that's an again another<00:22:17.970> interesting<00:22:18.450> question<00:22:18.540> that<00:22:18.810> while 00:22:19.460 --> 00:22:19.470 align:start position:0% another interesting question that while 00:22:19.470 --> 00:22:21.980 align:start position:0% another interesting question that while we<00:22:19.650> are<00:22:19.770> just<00:22:19.800> reading<00:22:20.550> the<00:22:20.910> chain<00:22:21.270> this 00:22:21.980 --> 00:22:21.990 align:start position:0% we are just reading the chain this 00:22:21.990 --> 00:22:23.690 align:start position:0% we are just reading the chain this completely<00:22:22.410> solves<00:22:22.740> it<00:22:22.830> a<00:22:22.890> fool<00:22:23.070> node<00:22:23.250> but 00:22:23.690 --> 00:22:23.700 align:start position:0% completely solves it a fool node but 00:22:23.700 --> 00:22:25.070 align:start position:0% completely solves it a fool node but when<00:22:23.850> we<00:22:23.970> are<00:22:24.060> trying<00:22:24.300> to<00:22:24.390> transact<00:22:24.840> with<00:22:24.900> the 00:22:25.070 --> 00:22:25.080 align:start position:0% when we are trying to transact with the 00:22:25.080 --> 00:22:28.820 align:start position:0% when we are trying to transact with the chain<00:22:25.460> then<00:22:26.810> then<00:22:27.810> if<00:22:27.960> for<00:22:28.230> example<00:22:28.260> somebody 00:22:28.820 --> 00:22:28.830 align:start position:0% chain then then if for example somebody 00:22:28.830 --> 00:22:32.330 align:start position:0% chain then then if for example somebody manages<00:22:29.460> if<00:22:29.700> I'm<00:22:30.140> let's<00:22:31.140> say<00:22:31.260> I<00:22:31.310> run<00:22:32.310> a 00:22:32.330 --> 00:22:32.340 align:start position:0% manages if I'm let's say I run a 00:22:32.340 --> 00:22:34.520 align:start position:0% manages if I'm let's say I run a thousand<00:22:32.910> full<00:22:33.150> nodes<00:22:33.390> and<00:22:33.630> I<00:22:34.230> start 00:22:34.520 --> 00:22:34.530 align:start position:0% thousand full nodes and I start 00:22:34.530 --> 00:22:36.530 align:start position:0% thousand full nodes and I start monitoring<00:22:34.950> where<00:22:35.340> certain<00:22:36.030> transactions 00:22:36.530 --> 00:22:36.540 align:start position:0% monitoring where certain transactions 00:22:36.540 --> 00:22:38.750 align:start position:0% monitoring where certain transactions are<00:22:36.660> coming<00:22:36.990> from<00:22:37.170> then<00:22:37.770> that<00:22:37.980> can<00:22:38.280> be<00:22:38.460> used<00:22:38.490> to 00:22:38.750 --> 00:22:38.760 align:start position:0% are coming from then that can be used to 00:22:38.760 --> 00:22:40.700 align:start position:0% are coming from then that can be used to eventually<00:22:39.480> statistically<00:22:40.230> hone<00:22:40.380> in<00:22:40.560> on<00:22:40.650> a 00:22:40.700 --> 00:22:40.710 align:start position:0% eventually statistically hone in on a 00:22:40.710 --> 00:22:42.800 align:start position:0% eventually statistically hone in on a certain<00:22:41.100> IP<00:22:41.460> address<00:22:41.910> that<00:22:42.030> this<00:22:42.210> IP<00:22:42.450> address 00:22:42.800 --> 00:22:42.810 align:start position:0% certain IP address that this IP address 00:22:42.810 --> 00:22:44.870 align:start position:0% certain IP address that this IP address is<00:22:42.960> usually<00:22:43.140> originating<00:22:43.860> some<00:22:44.040> ID<00:22:44.190> some 00:22:44.870 --> 00:22:44.880 align:start position:0% is usually originating some ID some 00:22:44.880 --> 00:22:48.890 align:start position:0% is usually originating some ID some transaction<00:22:45.480> and<00:22:46.640> here<00:22:47.640> here<00:22:48.300> my<00:22:48.420> solution<00:22:48.780> as 00:22:48.890 --> 00:22:48.900 align:start position:0% transaction and here here my solution as 00:22:48.900 --> 00:22:52.250 align:start position:0% transaction and here here my solution as I<00:22:49.110> think<00:22:49.940> for<00:22:50.940> example<00:22:51.030> ipfs<00:22:51.750> is<00:22:51.900> also<00:22:52.170> looking 00:22:52.250 --> 00:22:52.260 align:start position:0% I think for example ipfs is also looking 00:22:52.260 --> 00:22:56.270 align:start position:0% I think for example ipfs is also looking into<00:22:52.680> exactly<00:22:52.770> the<00:22:53.430> same<00:22:53.670> problem<00:22:54.090> and<00:22:55.280> their 00:22:56.270 --> 00:22:56.280 align:start position:0% into exactly the same problem and their 00:22:56.280 --> 00:22:58.730 align:start position:0% into exactly the same problem and their solution<00:22:56.880> or<00:22:57.090> let's<00:22:57.990> suppose<00:22:58.230> their<00:22:58.470> their 00:22:58.730 --> 00:22:58.740 align:start position:0% solution or let's suppose their their 00:22:58.740 --> 00:23:01.040 align:start position:0% solution or let's suppose their their ideas<00:22:59.220> are<00:22:59.520> all<00:22:59.670> all<00:23:00.120> revolve<00:23:00.450> around<00:23:00.570> the<00:23:01.020> I 00:23:01.040 --> 00:23:01.050 align:start position:0% ideas are all all revolve around the I 00:23:01.050 --> 00:23:03.380 align:start position:0% ideas are all all revolve around the I to<00:23:01.170> P<00:23:01.470> protocol<00:23:01.950> because<00:23:02.790> it's<00:23:02.940> essentially<00:23:03.360> a 00:23:03.380 --> 00:23:03.390 align:start position:0% to P protocol because it's essentially a 00:23:03.390 --> 00:23:07.100 align:start position:0% to P protocol because it's essentially a message<00:23:03.660> based<00:23:03.900> protocol<00:23:04.410> that<00:23:04.590> does<00:23:06.110> tries 00:23:07.100 --> 00:23:07.110 align:start position:0% message based protocol that does tries 00:23:07.110 --> 00:23:08.720 align:start position:0% message based protocol that does tries to<00:23:07.320> somehow<00:23:07.620> makes<00:23:07.860> the<00:23:08.010> transaction<00:23:08.490> a<00:23:08.580> bit 00:23:08.720 --> 00:23:08.730 align:start position:0% to somehow makes the transaction a bit 00:23:08.730 --> 00:23:10.460 align:start position:0% to somehow makes the transaction a bit in<00:23:08.940> the<00:23:09.150> network<00:23:09.480> before<00:23:09.690> popping<00:23:10.230> it<00:23:10.320> out 00:23:10.460 --> 00:23:10.470 align:start position:0% in the network before popping it out 00:23:10.470 --> 00:23:12.230 align:start position:0% in the network before popping it out somewhere<00:23:10.950> and<00:23:11.190> as<00:23:11.310> far<00:23:11.520> as<00:23:11.610> I<00:23:11.670> know<00:23:11.760> Manero 00:23:12.230 --> 00:23:12.240 align:start position:0% somewhere and as far as I know Manero 00:23:12.240 --> 00:23:13.990 align:start position:0% somewhere and as far as I know Manero does<00:23:12.480> the<00:23:12.630> same<00:23:12.840> thing<00:23:13.080> for<00:23:13.320> the<00:23:13.440> same<00:23:13.620> reasons 00:23:13.990 --> 00:23:14.000 align:start position:0% does the same thing for the same reasons 00:23:14.000 --> 00:23:17.150 align:start position:0% does the same thing for the same reasons so<00:23:15.000> that's<00:23:15.210> a<00:23:15.330> that's<00:23:16.080> possibly<00:23:16.620> that's<00:23:16.860> again 00:23:17.150 --> 00:23:17.160 align:start position:0% so that's a that's possibly that's again 00:23:17.160 --> 00:23:19.610 align:start position:0% so that's a that's possibly that's again something<00:23:17.190> that<00:23:17.790> many<00:23:18.270> people<00:23:18.660> before<00:23:18.840> us<00:23:19.230> did 00:23:19.610 --> 00:23:19.620 align:start position:0% something that many people before us did 00:23:19.620 --> 00:23:21.890 align:start position:0% something that many people before us did and<00:23:19.890> people<00:23:20.520> are<00:23:20.820> doing<00:23:21.090> concurrently<00:23:21.660> with 00:23:21.890 --> 00:23:21.900 align:start position:0% and people are doing concurrently with 00:23:21.900 --> 00:23:24.050 align:start position:0% and people are doing concurrently with us<00:23:22.080> so<00:23:22.620> it's<00:23:22.770> not<00:23:22.890> an<00:23:23.100> unsolvable<00:23:23.580> research 00:23:24.050 --> 00:23:24.060 align:start position:0% us so it's not an unsolvable research 00:23:24.060 --> 00:23:25.790 align:start position:0% us so it's not an unsolvable research problem<00:23:24.510> it's<00:23:24.630> just<00:23:24.690> an<00:23:25.140> engineering<00:23:25.560> problem 00:23:25.790 --> 00:23:25.800 align:start position:0% problem it's just an engineering problem 00:23:25.800 --> 00:23:29.820 align:start position:0% problem it's just an engineering problem that<00:23:26.400> we<00:23:26.760> have<00:23:26.880> to<00:23:27.000> pay<00:23:27.120> attention<00:23:27.330> to 00:23:29.820 --> 00:23:29.830 align:start position:0% 00:23:29.830 --> 00:23:31.480 align:start position:0% thanks<00:23:30.830> for<00:23:30.920> your<00:23:30.980> thought<00:23:31.130> it<00:23:31.250> was<00:23:31.340> really 00:23:31.480 --> 00:23:31.490 align:start position:0% thanks for your thought it was really 00:23:31.490 --> 00:23:34.360 align:start position:0% thanks for your thought it was really good<00:23:31.670> I<00:23:32.480> think<00:23:33.110> probably<00:23:33.440> most<00:23:33.740> people<00:23:33.980> in 00:23:34.360 --> 00:23:34.370 align:start position:0% good I think probably most people in 00:23:34.370 --> 00:23:36.190 align:start position:0% good I think probably most people in this<00:23:34.520> room<00:23:34.730> have<00:23:34.970> done<00:23:35.240> all<00:23:35.450> the<00:23:35.690> bad<00:23:35.870> things 00:23:36.190 --> 00:23:36.200 align:start position:0% this room have done all the bad things 00:23:36.200 --> 00:23:38.230 align:start position:0% this room have done all the bad things that<00:23:36.380> you<00:23:36.650> mentioned<00:23:36.790> throughout<00:23:37.790> the<00:23:38.000> talk 00:23:38.230 --> 00:23:38.240 align:start position:0% that you mentioned throughout the talk 00:23:38.240 --> 00:23:40.810 align:start position:0% that you mentioned throughout the talk so<00:23:38.660> is<00:23:38.870> there<00:23:39.020> anything<00:23:39.200> you<00:23:39.410> recommend<00:23:40.100> aside 00:23:40.810 --> 00:23:40.820 align:start position:0% so is there anything you recommend aside 00:23:40.820 --> 00:23:42.730 align:start position:0% so is there anything you recommend aside from<00:23:41.000> running<00:23:41.150> your<00:23:41.360> full<00:23:41.630> no<00:23:41.810> to<00:23:41.870> either<00:23:42.260> like 00:23:42.730 --> 00:23:42.740 align:start position:0% from running your full no to either like 00:23:42.740 --> 00:23:46.150 align:start position:0% from running your full no to either like go<00:23:42.920> forward<00:23:43.370> or<00:23:43.610> perhaps<00:23:44.410> anonymize<00:23:45.410> things 00:23:46.150 --> 00:23:46.160 align:start position:0% go forward or perhaps anonymize things 00:23:46.160 --> 00:23:50.260 align:start position:0% go forward or perhaps anonymize things with<00:23:46.430> these<00:23:46.580> services<00:23:47.090> more<00:23:47.530> yeah<00:23:49.240> well<00:23:50.240> I 00:23:50.260 --> 00:23:50.270 align:start position:0% with these services more yeah well I 00:23:50.270 --> 00:23:52.210 align:start position:0% with these services more yeah well I guess<00:23:50.630> my<00:23:50.870> recommendation<00:23:51.020> I<00:23:51.560> can<00:23:52.100> only 00:23:52.210 --> 00:23:52.220 align:start position:0% guess my recommendation I can only 00:23:52.220 --> 00:23:53.590 align:start position:0% guess my recommendation I can only recommend<00:23:52.370> what<00:23:52.700> I<00:23:52.790> already<00:23:53.090> recommended 00:23:53.590 --> 00:23:53.600 align:start position:0% recommend what I already recommended 00:23:53.600 --> 00:23:57.460 align:start position:0% recommend what I already recommended within<00:23:53.930> the<00:23:54.140> within<00:23:54.800> the<00:23:54.920> slides<00:23:55.250> that<00:23:56.170> if<00:23:57.170> you 00:23:57.460 --> 00:23:57.470 align:start position:0% within the within the slides that if you 00:23:57.470 --> 00:23:59.440 align:start position:0% within the within the slides that if you are<00:23:57.650> running<00:23:58.250> if<00:23:58.400> you<00:23:58.520> are<00:23:58.640> accessing<00:23:59.000> block 00:23:59.440 --> 00:23:59.450 align:start position:0% are running if you are accessing block 00:23:59.450 --> 00:24:02.020 align:start position:0% are running if you are accessing block Explorers<00:23:59.990> I<00:24:00.200> think<00:24:00.470> browser<00:24:01.160> extensions<00:24:01.850> are 00:24:02.020 --> 00:24:02.030 align:start position:0% Explorers I think browser extensions are 00:24:02.030 --> 00:24:04.030 align:start position:0% Explorers I think browser extensions are the<00:24:02.120> single<00:24:02.390> most<00:24:02.450> important<00:24:03.080> thing<00:24:03.290> if<00:24:03.680> you 00:24:04.030 --> 00:24:04.040 align:start position:0% the single most important thing if you 00:24:04.040 --> 00:24:06.100 align:start position:0% the single most important thing if you if<00:24:04.310> you<00:24:04.430> are<00:24:04.520> really<00:24:04.670> paranoid<00:24:05.300> then<00:24:05.780> tor 00:24:06.100 --> 00:24:06.110 align:start position:0% if you are really paranoid then tor 00:24:06.110 --> 00:24:08.110 align:start position:0% if you are really paranoid then tor network<00:24:06.290> is<00:24:06.650> also<00:24:06.800> an<00:24:07.280> essential<00:24:07.760> thing<00:24:07.790> so 00:24:08.110 --> 00:24:08.120 align:start position:0% network is also an essential thing so 00:24:08.120 --> 00:24:11.110 align:start position:0% network is also an essential thing so that<00:24:08.870> with<00:24:09.530> with<00:24:09.860> the<00:24:09.950> Tor<00:24:10.190> network<00:24:10.310> you<00:24:10.970> can 00:24:11.110 --> 00:24:11.120 align:start position:0% that with with the Tor network you can 00:24:11.120 --> 00:24:14.140 align:start position:0% that with with the Tor network you can completely<00:24:11.570> protect<00:24:11.900> yourself<00:24:12.320> against<00:24:13.120> Brau 00:24:14.140 --> 00:24:14.150 align:start position:0% completely protect yourself against Brau 00:24:14.150 --> 00:24:17.740 align:start position:0% completely protect yourself against Brau typical<00:24:14.960> browser-based<00:24:15.410> app<00:24:16.480> that's<00:24:17.480> from 00:24:17.740 --> 00:24:17.750 align:start position:0% typical browser-based app that's from 00:24:17.750 --> 00:24:19.750 align:start position:0% typical browser-based app that's from tracking<00:24:17.990> you<00:24:18.230> if<00:24:18.500> you<00:24:19.010> if<00:24:19.370> you<00:24:19.520> are<00:24:19.610> actually 00:24:19.750 --> 00:24:19.760 align:start position:0% tracking you if you if you are actually 00:24:19.760 --> 00:24:22.300 align:start position:0% tracking you if you if you are actually willing<00:24:20.090> to<00:24:20.270> run<00:24:20.360> a<00:24:20.420> light<00:24:20.630> client<00:24:21.190> that's<00:24:22.190> a 00:24:22.300 --> 00:24:22.310 align:start position:0% willing to run a light client that's a 00:24:22.310 --> 00:24:23.590 align:start position:0% willing to run a light client that's a hard<00:24:22.490> problem<00:24:22.610> that's<00:24:23.000> up<00:24:23.180> to<00:24:23.300> the<00:24:23.420> client 00:24:23.590 --> 00:24:23.600 align:start position:0% hard problem that's up to the client 00:24:23.600 --> 00:24:29.230 align:start position:0% hard problem that's up to the client developers<00:24:26.980> will<00:24:27.980> you<00:24:28.100> recommend<00:24:28.370> us<00:24:28.700> like 00:24:29.230 --> 00:24:29.240 align:start position:0% developers will you recommend us like 00:24:29.240 --> 00:24:34.750 align:start position:0% developers will you recommend us like general<00:24:30.050> rule<00:24:30.800> to<00:24:33.040> regularly<00:24:34.040> clean<00:24:34.250> out<00:24:34.460> the 00:24:34.750 --> 00:24:34.760 align:start position:0% general rule to regularly clean out the 00:24:34.760 --> 00:24:40.450 align:start position:0% general rule to regularly clean out the node<00:24:35.240> key<00:24:37.720> so<00:24:38.720> if<00:24:38.840> as<00:24:39.380> long<00:24:39.590> as<00:24:39.740> your<00:24:39.890> server<00:24:40.220> is 00:24:40.450 --> 00:24:40.460 align:start position:0% node key so if as long as your server is 00:24:40.460 --> 00:24:45.040 align:start position:0% node key so if as long as your server is stable<00:24:40.880> the<00:24:41.030> node<00:24:41.180> key<00:24:41.390> is<00:24:41.510> fine<00:24:41.780> I<00:24:42.020> mean<00:24:44.050> yes 00:24:45.040 --> 00:24:45.050 align:start position:0% stable the node key is fine I mean yes 00:24:45.050 --> 00:24:47.200 align:start position:0% stable the node key is fine I mean yes so<00:24:45.260> if<00:24:45.440> you<00:24:45.620> are<00:24:45.710> on<00:24:45.860> the<00:24:45.950> laptop<00:24:46.340> I<00:24:46.580> think<00:24:47.060> that 00:24:47.200 --> 00:24:47.210 align:start position:0% so if you are on the laptop I think that 00:24:47.210 --> 00:24:49.000 align:start position:0% so if you are on the laptop I think that that<00:24:47.750> would<00:24:47.930> be<00:24:47.990> the<00:24:48.110> first<00:24:48.410> no-brainer 00:24:49.000 --> 00:24:49.010 align:start position:0% that would be the first no-brainer 00:24:49.010 --> 00:24:50.590 align:start position:0% that would be the first no-brainer solution<00:24:49.370> that<00:24:49.460> we<00:24:49.580> have<00:24:49.730> to<00:24:49.910> do<00:24:50.030> is<00:24:50.240> we<00:24:50.450> have 00:24:50.590 --> 00:24:50.600 align:start position:0% solution that we have to do is we have 00:24:50.600 --> 00:24:52.870 align:start position:0% solution that we have to do is we have to<00:24:50.810> keep<00:24:51.080> every<00:24:51.860> so<00:24:52.100> for<00:24:52.280> example<00:24:52.550> if<00:24:52.640> you<00:24:52.730> run 00:24:52.870 --> 00:24:52.880 align:start position:0% to keep every so for example if you run 00:24:52.880 --> 00:24:54.940 align:start position:0% to keep every so for example if you run a<00:24:52.940> light<00:24:53.150> client<00:24:53.570> every<00:24:54.200> time<00:24:54.380> you<00:24:54.500> run<00:24:54.890> a 00:24:54.940 --> 00:24:54.950 align:start position:0% a light client every time you run a 00:24:54.950 --> 00:24:57.430 align:start position:0% a light client every time you run a light<00:24:55.160> client<00:24:55.580> you<00:24:55.820> we<00:24:56.150> should<00:24:56.450> reset<00:24:57.200> the 00:24:57.430 --> 00:24:57.440 align:start position:0% light client you we should reset the 00:24:57.440 --> 00:24:58.570 align:start position:0% light client you we should reset the node<00:24:57.560> because<00:24:57.770> we<00:24:57.890> should<00:24:58.070> use<00:24:58.190> a<00:24:58.220> firmer 00:24:58.570 --> 00:24:58.580 align:start position:0% node because we should use a firmer 00:24:58.580 --> 00:25:01.660 align:start position:0% node because we should use a firmer latkes<00:24:59.500> even<00:25:00.500> even<00:25:00.950> better<00:25:01.100> I<00:25:01.190> would<00:25:01.430> suggest 00:25:01.660 --> 00:25:01.670 align:start position:0% latkes even even better I would suggest 00:25:01.670 --> 00:25:03.640 align:start position:0% latkes even even better I would suggest that<00:25:01.940> maybe<00:25:02.180> even<00:25:02.600> four<00:25:02.780> full<00:25:02.960> nodes<00:25:03.230> we<00:25:03.410> can 00:25:03.640 --> 00:25:03.650 align:start position:0% that maybe even four full nodes we can 00:25:03.650 --> 00:25:05.910 align:start position:0% that maybe even four full nodes we can use<00:25:03.890> it<00:25:04.070> from<00:25:04.190> our<00:25:04.370> own<00:25:04.490> node<00:25:04.700> keys<00:25:04.970> and<00:25:05.210> just 00:25:05.910 --> 00:25:05.920 align:start position:0% use it from our own node keys and just 00:25:05.920 --> 00:25:08.650 align:start position:0% use it from our own node keys and just if<00:25:06.920> we<00:25:07.220> restart<00:25:07.640> them<00:25:07.790> yeah<00:25:07.970> maybe<00:25:08.360> it<00:25:08.540> will 00:25:08.650 --> 00:25:08.660 align:start position:0% if we restart them yeah maybe it will 00:25:08.660 --> 00:25:10.480 align:start position:0% if we restart them yeah maybe it will have<00:25:08.840> a<00:25:08.870> bit<00:25:09.080> harder<00:25:09.530> time<00:25:09.800> connecting<00:25:10.280> to<00:25:10.400> the 00:25:10.480 --> 00:25:10.490 align:start position:0% have a bit harder time connecting to the 00:25:10.490 --> 00:25:13.210 align:start position:0% have a bit harder time connecting to the network<00:25:10.520> for<00:25:10.940> the<00:25:11.030> first<00:25:11.060> couple<00:25:11.660> minutes<00:25:12.220> so 00:25:13.210 --> 00:25:13.220 align:start position:0% network for the first couple minutes so 00:25:13.220 --> 00:25:14.680 align:start position:0% network for the first couple minutes so I<00:25:13.280> think<00:25:13.370> apart<00:25:13.880> from<00:25:14.030> booth<00:25:14.240> knows<00:25:14.450> no 00:25:14.680 --> 00:25:14.690 align:start position:0% I think apart from booth knows no 00:25:14.690 --> 00:25:16.360 align:start position:0% I think apart from booth knows no nothing<00:25:15.080> in<00:25:15.170> the<00:25:15.230> network<00:25:15.590> really<00:25:15.830> requires 00:25:16.360 --> 00:25:16.370 align:start position:0% nothing in the network really requires 00:25:16.370 --> 00:25:20.110 align:start position:0% nothing in the network really requires stable<00:25:17.270> keys<00:25:18.190> okay<00:25:19.190> can<00:25:19.340> we<00:25:19.370> please<00:25:19.520> another 00:25:20.110 --> 00:25:20.120 align:start position:0% stable keys okay can we please another 00:25:20.120 --> 00:25:21.550 align:start position:0% stable keys okay can we please another round<00:25:20.360> of<00:25:20.420> applause<00:25:20.660> for<00:25:20.810> Peter<00:25:20.990> thank<00:25:21.470> you 00:25:21.550 --> 00:25:21.560 align:start position:0% round of applause for Peter thank you 00:25:21.560 --> 00:25:21.810 align:start position:0% round of applause for Peter thank you very<00:25:21.650> much 00:25:21.810 --> 00:25:21.820 align:start position:0% very much 00:25:21.820 --> 00:25:30.630 align:start position:0% very much [Applause] 00:25:30.630 --> 00:25:30.640 align:start position:0% 00:25:30.640 --> 00:25:32.700 align:start position:0% you