WEBVTT Kind: captions Language: en 00:00:09.010 --> 00:00:20.140 align:start position:0% [Music] 00:00:20.140 --> 00:00:20.150 align:start position:0% 00:00:20.150 --> 00:00:25.850 align:start position:0% hey<00:00:21.150> guys<00:00:22.849> so<00:00:23.849> many<00:00:24.029> people<00:00:24.390> here<00:00:24.660> yeah<00:00:25.560> I'm 00:00:25.850 --> 00:00:25.860 align:start position:0% hey guys so many people here yeah I'm 00:00:25.860 --> 00:00:33.530 align:start position:0% hey guys so many people here yeah I'm Felix<00:00:29.000> what<00:00:30.000> is<00:00:30.119> it<00:00:31.489> should<00:00:32.489> I<00:00:32.520> use<00:00:32.730> this<00:00:32.970> okay 00:00:33.530 --> 00:00:33.540 align:start position:0% Felix what is it should I use this okay 00:00:33.540 --> 00:00:37.970 align:start position:0% Felix what is it should I use this okay hi<00:00:34.470> guys<00:00:34.550> so<00:00:35.550> I'm<00:00:35.910> Felix<00:00:36.420> I<00:00:36.720> work<00:00:37.680> for<00:00:37.950> a 00:00:37.970 --> 00:00:37.980 align:start position:0% hi guys so I'm Felix I work for a 00:00:37.980 --> 00:00:40.790 align:start position:0% hi guys so I'm Felix I work for a theorem<00:00:38.399> foundation<00:00:39.030> on<00:00:39.260> the<00:00:40.260> Goya<00:00:40.440> theorem 00:00:40.790 --> 00:00:40.800 align:start position:0% theorem foundation on the Goya theorem 00:00:40.800 --> 00:00:44.330 align:start position:0% theorem foundation on the Goya theorem client<00:00:41.309> and<00:00:42.410> my<00:00:43.410> role<00:00:43.590> there<00:00:43.800> is<00:00:43.920> mainly 00:00:44.330 --> 00:00:44.340 align:start position:0% client and my role there is mainly 00:00:44.340 --> 00:00:46.579 align:start position:0% client and my role there is mainly bug-fixing<00:00:45.090> in<00:00:45.239> feature<00:00:45.449> development<00:00:45.690> but<00:00:46.320> I 00:00:46.579 --> 00:00:46.589 align:start position:0% bug-fixing in feature development but I 00:00:46.589 --> 00:00:48.590 align:start position:0% bug-fixing in feature development but I guess<00:00:47.070> there's<00:00:47.339> a<00:00:47.429> lot<00:00:47.670> less<00:00:47.879> time<00:00:48.059> for<00:00:48.390> new 00:00:48.590 --> 00:00:48.600 align:start position:0% guess there's a lot less time for new 00:00:48.600 --> 00:00:52.369 align:start position:0% guess there's a lot less time for new features<00:00:48.989> lately<00:00:49.379> and<00:00:50.750> my<00:00:51.750> passion<00:00:52.140> and<00:00:52.260> this 00:00:52.369 --> 00:00:52.379 align:start position:0% features lately and my passion and this 00:00:52.379 --> 00:00:54.020 align:start position:0% features lately and my passion and this project<00:00:52.589> has<00:00:52.800> always<00:00:53.070> been<00:00:53.370> you<00:00:53.699> know<00:00:53.730> like 00:00:54.020 --> 00:00:54.030 align:start position:0% project has always been you know like 00:00:54.030 --> 00:00:56.720 align:start position:0% project has always been you know like taking<00:00:54.870> care<00:00:55.050> of<00:00:55.079> the<00:00:55.320> way<00:00:55.469> that<00:00:55.769> nodes<00:00:56.519> talk 00:00:56.720 --> 00:00:56.730 align:start position:0% taking care of the way that nodes talk 00:00:56.730 --> 00:00:58.939 align:start position:0% taking care of the way that nodes talk to<00:00:56.879> each<00:00:56.969> other<00:00:57.179> and<00:00:57.420> this<00:00:58.289> is<00:00:58.440> also<00:00:58.620> what<00:00:58.829> I'm 00:00:58.939 --> 00:00:58.949 align:start position:0% to each other and this is also what I'm 00:00:58.949 --> 00:01:02.770 align:start position:0% to each other and this is also what I'm talking<00:00:59.309> about<00:00:59.370> today<00:01:00.859> hmm 00:01:02.770 --> 00:01:02.780 align:start position:0% talking about today hmm 00:01:02.780 --> 00:01:07.760 align:start position:0% talking about today hmm so<00:01:03.780> death<00:01:04.500> p2p<00:01:05.390> wasn't<00:01:06.409> came<00:01:07.409> into<00:01:07.590> existence 00:01:07.760 --> 00:01:07.770 align:start position:0% so death p2p wasn't came into existence 00:01:07.770 --> 00:01:10.820 align:start position:0% so death p2p wasn't came into existence I<00:01:08.460> guess<00:01:08.670> three<00:01:09.540> about<00:01:09.870> three<00:01:09.930> years<00:01:10.290> ago<00:01:10.590> and 00:01:10.820 --> 00:01:10.830 align:start position:0% I guess three about three years ago and 00:01:10.830 --> 00:01:16.010 align:start position:0% I guess three about three years ago and at<00:01:11.759> the<00:01:11.939> time<00:01:12.090> the<00:01:12.960> vision<00:01:13.290> was<00:01:13.439> to<00:01:14.000> as<00:01:15.000> you<00:01:15.869> can 00:01:16.010 --> 00:01:16.020 align:start position:0% at the time the vision was to as you can 00:01:16.020 --> 00:01:18.170 align:start position:0% at the time the vision was to as you can read<00:01:16.200> there<00:01:16.439> provide<00:01:17.159> the<00:01:17.640> lightweight 00:01:18.170 --> 00:01:18.180 align:start position:0% read there provide the lightweight 00:01:18.180 --> 00:01:20.060 align:start position:0% read there provide the lightweight abstraction<00:01:18.899> layer<00:01:19.079> that<00:01:19.380> provides<00:01:19.799> low 00:01:20.060 --> 00:01:20.070 align:start position:0% abstraction layer that provides low 00:01:20.070 --> 00:01:22.039 align:start position:0% abstraction layer that provides low level<00:01:20.430> algorithms<00:01:21.000> protocols<00:01:21.630> and<00:01:21.810> services 00:01:22.039 --> 00:01:22.049 align:start position:0% level algorithms protocols and services 00:01:22.049 --> 00:01:26.240 align:start position:0% level algorithms protocols and services in<00:01:22.530> a<00:01:22.619> transparent<00:01:23.070> framework<00:01:24.439> so<00:01:25.439> you<00:01:26.130> know 00:01:26.240 --> 00:01:26.250 align:start position:0% in a transparent framework so you know 00:01:26.250 --> 00:01:34.209 align:start position:0% in a transparent framework so you know like<00:01:26.490> it<00:01:26.670> was<00:01:26.820> a<00:01:26.850> pretty<00:01:27.119> grand<00:01:27.450> vision<00:01:32.990> in 00:01:34.209 --> 00:01:34.219 align:start position:0% like it was a pretty grand vision in 00:01:34.219 --> 00:01:37.999 align:start position:0% like it was a pretty grand vision in 2017<00:01:35.219> though<00:01:35.460> deaf<00:01:36.210> p2p<00:01:36.750> is<00:01:36.990> just<00:01:37.590> this<00:01:37.740> thing 00:01:37.999 --> 00:01:38.009 align:start position:0% 2017 though deaf p2p is just this thing 00:01:38.009 --> 00:01:39.679 align:start position:0% 2017 though deaf p2p is just this thing that<00:01:38.070> you<00:01:38.340> need<00:01:38.490> to<00:01:38.610> implement<00:01:38.850> to<00:01:39.240> talk<00:01:39.509> to 00:01:39.679 --> 00:01:39.689 align:start position:0% that you need to implement to talk to 00:01:39.689 --> 00:01:42.590 align:start position:0% that you need to implement to talk to the<00:01:39.810> ethereum<00:01:40.200> blockchain<00:01:40.229> and<00:01:41.000> it's<00:01:42.000> part<00:01:42.509> of 00:01:42.590 --> 00:01:42.600 align:start position:0% the ethereum blockchain and it's part of 00:01:42.600 --> 00:01:46.670 align:start position:0% the ethereum blockchain and it's part of all<00:01:42.780> noni<00:01:43.140> theorem<00:01:43.469> implementations<00:01:45.020> so<00:01:46.020> all 00:01:46.670 --> 00:01:46.680 align:start position:0% all noni theorem implementations so all 00:01:46.680 --> 00:01:49.249 align:start position:0% all noni theorem implementations so all of<00:01:46.979> the<00:01:47.130> 6-7<00:01:47.969> implementations<00:01:48.840> that<00:01:49.079> are 00:01:49.249 --> 00:01:49.259 align:start position:0% of the 6-7 implementations that are 00:01:49.259 --> 00:01:50.599 align:start position:0% of the 6-7 implementations that are alive<00:01:49.500> on<00:01:49.710> the<00:01:49.829> network<00:01:50.159> have<00:01:50.430> an 00:01:50.599 --> 00:01:50.609 align:start position:0% alive on the network have an 00:01:50.609 --> 00:01:52.609 align:start position:0% alive on the network have an implementation<00:01:51.299> of<00:01:51.420> def<00:01:51.630> PDP<00:01:52.049> and<00:01:52.079> all<00:01:52.380> of<00:01:52.500> the 00:01:52.609 --> 00:01:52.619 align:start position:0% implementation of def PDP and all of the 00:01:52.619 --> 00:01:56.120 align:start position:0% implementation of def PDP and all of the stuff<00:01:52.859> that's<00:01:53.039> in<00:01:53.219> it<00:01:53.340> and<00:01:54.950> there<00:01:55.950> have<00:01:56.100> been 00:01:56.120 --> 00:01:56.130 align:start position:0% stuff that's in it and there have been 00:01:56.130 --> 00:01:58.639 align:start position:0% stuff that's in it and there have been very<00:01:56.490> few<00:01:56.689> actual<00:01:57.689> protocol<00:01:58.079> changes<00:01:58.469> since 00:01:58.639 --> 00:01:58.649 align:start position:0% very few actual protocol changes since 00:01:58.649 --> 00:02:02.599 align:start position:0% very few actual protocol changes since 2014<00:01:59.549> so<00:02:00.590> if<00:02:01.590> you<00:02:01.770> wanted<00:02:02.009> to<00:02:02.130> you<00:02:02.280> could<00:02:02.430> count 00:02:02.599 --> 00:02:02.609 align:start position:0% 2014 so if you wanted to you could count 00:02:02.609 --> 00:02:03.469 align:start position:0% 2014 so if you wanted to you could count them<00:02:02.820> on<00:02:02.909> one<00:02:02.969> hand 00:02:03.469 --> 00:02:03.479 align:start position:0% them on one hand 00:02:03.479 --> 00:02:08.350 align:start position:0% them on one hand basically<00:02:05.270> deaf<00:02:06.270> p2p<00:02:06.659> has<00:02:06.929> a<00:02:07.229> bunch<00:02:07.799> of 00:02:08.350 --> 00:02:08.360 align:start position:0% basically deaf p2p has a bunch of 00:02:08.360 --> 00:02:11.300 align:start position:0% basically deaf p2p has a bunch of elements<00:02:09.360> to<00:02:09.509> it<00:02:09.660> so<00:02:10.020> the<00:02:10.200> first<00:02:10.440> one<00:02:10.649> is<00:02:10.979> the 00:02:11.300 --> 00:02:11.310 align:start position:0% elements to it so the first one is the 00:02:11.310 --> 00:02:13.670 align:start position:0% elements to it so the first one is the no<00:02:11.640> discovery<00:02:12.210> protocol<00:02:12.720> which<00:02:13.020> is<00:02:13.200> a<00:02:13.380> way<00:02:13.650> of 00:02:13.670 --> 00:02:13.680 align:start position:0% no discovery protocol which is a way of 00:02:13.680 --> 00:02:16.520 align:start position:0% no discovery protocol which is a way of finding<00:02:14.130> other<00:02:14.550> nodes<00:02:14.880> to<00:02:15.120> talk<00:02:15.330> to 00:02:16.520 --> 00:02:16.530 align:start position:0% finding other nodes to talk to 00:02:16.530 --> 00:02:19.040 align:start position:0% finding other nodes to talk to then<00:02:16.860> there<00:02:17.070> is<00:02:17.100> the<00:02:17.400> RL<00:02:18.180> PX<00:02:18.510> transport 00:02:19.040 --> 00:02:19.050 align:start position:0% then there is the RL PX transport 00:02:19.050 --> 00:02:20.870 align:start position:0% then there is the RL PX transport protocol<00:02:19.470> which<00:02:19.680> is<00:02:19.710> what<00:02:20.040> it's<00:02:20.190> spoken<00:02:20.490> on 00:02:20.870 --> 00:02:20.880 align:start position:0% protocol which is what it's spoken on 00:02:20.880 --> 00:02:24.580 align:start position:0% protocol which is what it's spoken on the<00:02:21.690> on<00:02:21.960> the<00:02:22.350> TCP<00:02:22.860> connections<00:02:23.400> between<00:02:23.670> nodes 00:02:24.580 --> 00:02:24.590 align:start position:0% the on the TCP connections between nodes 00:02:24.590 --> 00:02:28.910 align:start position:0% the on the TCP connections between nodes and<00:02:26.330> finally<00:02:27.330> there's<00:02:27.840> an<00:02:28.020> application<00:02:28.200> layer 00:02:28.910 --> 00:02:28.920 align:start position:0% and finally there's an application layer 00:02:28.920 --> 00:02:31.820 align:start position:0% and finally there's an application layer protocol<00:02:29.490> that<00:02:29.610> sits<00:02:29.850> on<00:02:30.000> top<00:02:30.060> of<00:02:30.300> the<00:02:31.230> ROP<00:02:31.590> X 00:02:31.820 --> 00:02:31.830 align:start position:0% protocol that sits on top of the ROP X 00:02:31.830 --> 00:02:34.970 align:start position:0% protocol that sits on top of the ROP X transport<00:02:32.340> protocol<00:02:32.760> and<00:02:33.620> this<00:02:34.620> one<00:02:34.830> is 00:02:34.970 --> 00:02:34.980 align:start position:0% transport protocol and this one is 00:02:34.980 --> 00:02:38.930 align:start position:0% transport protocol and this one is somewhat<00:02:35.970> confusingly<00:02:36.540> also<00:02:36.930> called<00:02:37.170> FPTP<00:02:37.940> so 00:02:38.930 --> 00:02:38.940 align:start position:0% somewhat confusingly also called FPTP so 00:02:38.940 --> 00:02:41.150 align:start position:0% somewhat confusingly also called FPTP so both<00:02:39.120> the<00:02:39.270> overall<00:02:39.420> system<00:02:40.080> and<00:02:40.320> this 00:02:41.150 --> 00:02:41.160 align:start position:0% both the overall system and this 00:02:41.160 --> 00:02:45.740 align:start position:0% both the overall system and this particular<00:02:41.520> protocol<00:02:42.420> are<00:02:42.600> called<00:02:42.870> FPTP<00:02:44.750> let 00:02:45.740 --> 00:02:45.750 align:start position:0% particular protocol are called FPTP let 00:02:45.750 --> 00:02:47.930 align:start position:0% particular protocol are called FPTP let me<00:02:45.840> just<00:02:46.050> walk<00:02:46.260> you<00:02:46.440> through<00:02:46.980> the<00:02:47.460> protocol 00:02:47.930 --> 00:02:47.940 align:start position:0% me just walk you through the protocol 00:02:47.940 --> 00:02:50.630 align:start position:0% me just walk you through the protocol that's<00:02:48.840> in<00:02:49.110> use<00:02:49.290> on<00:02:49.500> the<00:02:49.530> network<00:02:49.920> today<00:02:50.250> and 00:02:50.630 --> 00:02:50.640 align:start position:0% that's in use on the network today and 00:02:50.640 --> 00:02:53.690 align:start position:0% that's in use on the network today and then<00:02:51.090> maybe<00:02:51.330> like<00:02:51.900> we'll<00:02:52.800> come<00:02:53.040> to<00:02:53.310> the<00:02:53.460> part 00:02:53.690 --> 00:02:53.700 align:start position:0% then maybe like we'll come to the part 00:02:53.700 --> 00:02:56.600 align:start position:0% then maybe like we'll come to the part that<00:02:54.170> can<00:02:55.170> actually<00:02:55.320> be<00:02:55.500> improved<00:02:55.920> about<00:02:56.190> this 00:02:56.600 --> 00:02:56.610 align:start position:0% that can actually be improved about this 00:02:56.610 --> 00:03:01.820 align:start position:0% that can actually be improved about this so<00:02:57.590> this<00:02:59.330> dark<00:03:00.330> circle<00:03:00.720> there<00:03:00.900> that's<00:03:01.290> that's 00:03:01.820 --> 00:03:01.830 align:start position:0% so this dark circle there that's that's 00:03:01.830 --> 00:03:04.310 align:start position:0% so this dark circle there that's that's us<00:03:02.130> so<00:03:02.610> that<00:03:02.820> we're<00:03:03.300> node<00:03:03.540> that<00:03:04.020> wants<00:03:04.260> to 00:03:04.310 --> 00:03:04.320 align:start position:0% us so that we're node that wants to 00:03:04.320 --> 00:03:07.370 align:start position:0% us so that we're node that wants to connect<00:03:04.620> to<00:03:04.770> the<00:03:04.890> etherium<00:03:05.280> Network<00:03:06.020> so<00:03:07.020> how 00:03:07.370 --> 00:03:07.380 align:start position:0% connect to the etherium Network so how 00:03:07.380 --> 00:03:08.180 align:start position:0% connect to the etherium Network so how do<00:03:07.440> we<00:03:07.560> do<00:03:07.770> that 00:03:08.180 --> 00:03:08.190 align:start position:0% do we do that 00:03:08.190 --> 00:03:11.720 align:start position:0% do we do that so<00:03:08.750> we'll<00:03:09.750> join<00:03:09.960> the<00:03:10.020> DHT<00:03:10.380> first<00:03:10.860> and<00:03:11.220> the<00:03:11.430> DHT 00:03:11.720 --> 00:03:11.730 align:start position:0% so we'll join the DHT first and the DHT 00:03:11.730 --> 00:03:15.980 align:start position:0% so we'll join the DHT first and the DHT is<00:03:12.260> basically<00:03:13.260> the<00:03:13.830> part<00:03:14.100> that<00:03:14.420> is<00:03:15.420> this<00:03:15.780> thing 00:03:15.980 --> 00:03:15.990 align:start position:0% is basically the part that is this thing 00:03:15.990 --> 00:03:17.420 align:start position:0% is basically the part that is this thing where<00:03:16.170> you<00:03:16.260> can<00:03:16.440> find<00:03:16.710> the<00:03:16.830> other<00:03:17.010> nodes<00:03:17.280> that 00:03:17.420 --> 00:03:17.430 align:start position:0% where you can find the other nodes that 00:03:17.430 --> 00:03:21.920 align:start position:0% where you can find the other nodes that are<00:03:17.490> on<00:03:17.670> the<00:03:17.790> network<00:03:20.390> yeah<00:03:21.390> so<00:03:21.660> there<00:03:21.870> are 00:03:21.920 --> 00:03:21.930 align:start position:0% are on the network yeah so there are 00:03:21.930 --> 00:03:22.970 align:start position:0% are on the network yeah so there are some<00:03:22.050> other<00:03:22.230> nodes<00:03:22.500> they<00:03:22.739> are<00:03:22.800> also 00:03:22.970 --> 00:03:22.980 align:start position:0% some other nodes they are also 00:03:22.980 --> 00:03:27.380 align:start position:0% some other nodes they are also registered<00:03:23.220> there<00:03:23.790> and<00:03:24.950> then<00:03:25.950> basically<00:03:26.730> we 00:03:27.380 --> 00:03:27.390 align:start position:0% registered there and then basically we 00:03:27.390 --> 00:03:29.510 align:start position:0% registered there and then basically we walk<00:03:27.630> to<00:03:27.810> the<00:03:27.930> HT<00:03:28.260> at<00:03:28.380> random<00:03:28.770> to<00:03:28.950> find<00:03:29.190> someone 00:03:29.510 --> 00:03:29.520 align:start position:0% walk to the HT at random to find someone 00:03:29.520 --> 00:03:33.080 align:start position:0% walk to the HT at random to find someone to<00:03:29.730> connect<00:03:30.300> to<00:03:30.480> and<00:03:31.370> then<00:03:32.370> we<00:03:32.790> try<00:03:33.030> to 00:03:33.080 --> 00:03:33.090 align:start position:0% to connect to and then we try to 00:03:33.090 --> 00:03:36.370 align:start position:0% to connect to and then we try to establish<00:03:33.300> a<00:03:33.690> TCP<00:03:34.170> connection<00:03:34.650> to<00:03:34.800> them<00:03:35.010> and 00:03:36.370 --> 00:03:36.380 align:start position:0% establish a TCP connection to them and 00:03:36.380 --> 00:03:39.830 align:start position:0% establish a TCP connection to them and the<00:03:37.380> TCP<00:03:37.890> connection<00:03:38.400> might<00:03:39.300> actually<00:03:39.630> fail 00:03:39.830 --> 00:03:39.840 align:start position:0% the TCP connection might actually fail 00:03:39.840 --> 00:03:41.600 align:start position:0% the TCP connection might actually fail so<00:03:40.110> this<00:03:40.260> happens<00:03:40.590> quite<00:03:40.650> a<00:03:40.830> lot<00:03:41.070> because<00:03:41.340> the 00:03:41.600 --> 00:03:41.610 align:start position:0% so this happens quite a lot because the 00:03:41.610 --> 00:03:43.820 align:start position:0% so this happens quite a lot because the node<00:03:41.790> you<00:03:42.150> know<00:03:42.360> might<00:03:42.630> no<00:03:42.780> longer<00:03:42.810> be<00:03:43.080> live<00:03:43.380> or 00:03:43.820 --> 00:03:43.830 align:start position:0% node you know might no longer be live or 00:03:43.830 --> 00:03:46.010 align:start position:0% node you know might no longer be live or you<00:03:44.400> know<00:03:44.550> it<00:03:44.700> might<00:03:44.880> be<00:03:45.030> too<00:03:45.360> busy<00:03:45.540> handling 00:03:46.010 --> 00:03:46.020 align:start position:0% you know it might be too busy handling 00:03:46.020 --> 00:03:48.170 align:start position:0% you know it might be too busy handling all<00:03:46.170> the<00:03:46.260> connections<00:03:46.739> but<00:03:47.459> let's<00:03:47.880> just 00:03:48.170 --> 00:03:48.180 align:start position:0% all the connections but let's just 00:03:48.180 --> 00:03:49.870 align:start position:0% all the connections but let's just assume<00:03:48.450> that<00:03:48.540> it<00:03:48.810> works<00:03:49.020> this<00:03:49.260> time 00:03:49.870 --> 00:03:49.880 align:start position:0% assume that it works this time 00:03:49.880 --> 00:03:54.050 align:start position:0% assume that it works this time so<00:03:50.880> once<00:03:51.540> the<00:03:51.660> connection<00:03:52.080> is<00:03:52.140> established<00:03:53.060> we 00:03:54.050 --> 00:03:54.060 align:start position:0% so once the connection is established we 00:03:54.060 --> 00:03:56.240 align:start position:0% so once the connection is established we actually<00:03:54.510> exchange<00:03:55.050> capabilities<00:03:55.830> with<00:03:56.130> the 00:03:56.240 --> 00:03:56.250 align:start position:0% actually exchange capabilities with the 00:03:56.250 --> 00:03:58.850 align:start position:0% actually exchange capabilities with the other<00:03:56.370> side<00:03:56.670> so<00:03:57.090> basically<00:03:57.570> this<00:03:58.500> is<00:03:58.650> now<00:03:58.800> the 00:03:58.850 --> 00:03:58.860 align:start position:0% other side so basically this is now the 00:03:58.860 --> 00:04:00.890 align:start position:0% other side so basically this is now the part<00:03:59.190> where<00:03:59.370> like<00:03:59.400> the<00:03:59.730> DEF<00:03:59.910> PDP<00:04:00.360> application 00:04:00.890 --> 00:04:00.900 align:start position:0% part where like the DEF PDP application 00:04:00.900 --> 00:04:02.960 align:start position:0% part where like the DEF PDP application layer<00:04:01.080> kicks<00:04:01.380> in<00:04:01.590> and<00:04:01.770> in<00:04:02.459> this<00:04:02.610> particular 00:04:02.960 --> 00:04:02.970 align:start position:0% layer kicks in and in this particular 00:04:02.970 --> 00:04:05.449 align:start position:0% layer kicks in and in this particular case<00:04:03.360> we<00:04:03.870> see<00:04:04.110> that<00:04:04.140> the<00:04:04.470> shared<00:04:04.709> capabilities 00:04:05.449 --> 00:04:05.459 align:start position:0% case we see that the shared capabilities 00:04:05.459 --> 00:04:08.150 align:start position:0% case we see that the shared capabilities or<00:04:05.790> is<00:04:06.000> it<00:04:06.630> is<00:04:06.810> just<00:04:07.050> one<00:04:07.230> shared<00:04:07.500> capability 00:04:08.150 --> 00:04:08.160 align:start position:0% or is it is just one shared capability 00:04:08.160 --> 00:04:12.440 align:start position:0% or is it is just one shared capability and<00:04:08.340> it's<00:04:09.200> it's<00:04:10.200> the<00:04:10.470> eath<00:04:11.180> capability<00:04:12.180> in 00:04:12.440 --> 00:04:12.450 align:start position:0% and it's it's the eath capability in 00:04:12.450 --> 00:04:16.670 align:start position:0% and it's it's the eath capability in version<00:04:12.810> 63<00:04:14.060> so<00:04:15.060> now<00:04:15.239> once<00:04:15.510> each<00:04:15.810> version<00:04:16.169> 63 00:04:16.670 --> 00:04:16.680 align:start position:0% version 63 so now once each version 63 00:04:16.680 --> 00:04:18.710 align:start position:0% version 63 so now once each version 63 is<00:04:17.100> running<00:04:17.489> we<00:04:17.970> can<00:04:18.180> exchange<00:04:18.390> information 00:04:18.710 --> 00:04:18.720 align:start position:0% is running we can exchange information 00:04:18.720 --> 00:04:21.740 align:start position:0% is running we can exchange information about<00:04:19.260> a<00:04:19.440> blockchain<00:04:19.739> that<00:04:20.730> we're<00:04:21.330> both<00:04:21.450> on 00:04:21.740 --> 00:04:21.750 align:start position:0% about a blockchain that we're both on 00:04:21.750 --> 00:04:26.060 align:start position:0% about a blockchain that we're both on and<00:04:21.989> once<00:04:22.680> that<00:04:22.890> matches<00:04:23.460> we<00:04:24.090> have<00:04:24.240> a<00:04:24.270> new<00:04:24.479> Pia 00:04:26.060 --> 00:04:26.070 align:start position:0% and once that matches we have a new Pia 00:04:26.070 --> 00:04:28.320 align:start position:0% and once that matches we have a new Pia yeah<00:04:27.070> so<00:04:27.220> that's<00:04:27.400> the<00:04:27.520> current<00:04:27.699> system<00:04:28.150> and 00:04:28.320 --> 00:04:28.330 align:start position:0% yeah so that's the current system and 00:04:28.330 --> 00:04:32.460 align:start position:0% yeah so that's the current system and it's<00:04:29.290> not<00:04:29.500> super<00:04:29.830> efficient<00:04:30.370> and<00:04:31.470> well 00:04:32.460 --> 00:04:32.470 align:start position:0% it's not super efficient and well 00:04:32.470 --> 00:04:34.050 align:start position:0% it's not super efficient and well there's<00:04:32.650> a<00:04:32.710> whole<00:04:33.190> bunch<00:04:33.370> of<00:04:33.460> details<00:04:33.639> that<00:04:33.940> I 00:04:34.050 --> 00:04:34.060 align:start position:0% there's a whole bunch of details that I 00:04:34.060 --> 00:04:35.730 align:start position:0% there's a whole bunch of details that I haven't<00:04:34.270> really<00:04:34.479> talked<00:04:34.810> about<00:04:34.930> but<00:04:35.350> you<00:04:35.710> know 00:04:35.730 --> 00:04:35.740 align:start position:0% haven't really talked about but you know 00:04:35.740 --> 00:04:40.439 align:start position:0% haven't really talked about but you know I<00:04:36.100> I<00:04:36.310> guess<00:04:36.729> you<00:04:36.880> kind<00:04:37.150> of<00:04:37.270> get<00:04:37.419> the<00:04:37.540> idea<00:04:39.449> so 00:04:40.439 --> 00:04:40.449 align:start position:0% I I guess you kind of get the idea so 00:04:40.449 --> 00:04:43.800 align:start position:0% I I guess you kind of get the idea so what<00:04:41.110> can<00:04:41.440> we<00:04:41.500> improve<00:04:41.680> about<00:04:42.130> this<00:04:42.310> though<00:04:42.810> so 00:04:43.800 --> 00:04:43.810 align:start position:0% what can we improve about this though so 00:04:43.810 --> 00:04:45.990 align:start position:0% what can we improve about this though so first<00:04:44.020> of<00:04:44.169> all<00:04:44.260> you<00:04:44.410> know<00:04:44.669> it's<00:04:45.669> kind<00:04:45.940> of 00:04:45.990 --> 00:04:46.000 align:start position:0% first of all you know it's kind of 00:04:46.000 --> 00:04:47.400 align:start position:0% first of all you know it's kind of annoying<00:04:46.270> that<00:04:46.570> there<00:04:46.690> are<00:04:46.780> so<00:04:46.960> many<00:04:47.110> round 00:04:47.400 --> 00:04:47.410 align:start position:0% annoying that there are so many round 00:04:47.410 --> 00:04:49.020 align:start position:0% annoying that there are so many round trips<00:04:47.680> just<00:04:47.889> to<00:04:48.010> figure<00:04:48.190> out<00:04:48.340> whether<00:04:48.610> someone 00:04:49.020 --> 00:04:49.030 align:start position:0% trips just to figure out whether someone 00:04:49.030 --> 00:04:51.620 align:start position:0% trips just to figure out whether someone is<00:04:49.060> on<00:04:49.330> you<00:04:49.540> know<00:04:49.660> the<00:04:49.810> right<00:04:49.930> blockchain<00:04:50.410> I 00:04:51.620 --> 00:04:51.630 align:start position:0% is on you know the right blockchain I 00:04:51.630 --> 00:04:55.490 align:start position:0% is on you know the right blockchain I mean<00:04:52.630> I<00:04:53.110> guess<00:04:53.530> that's<00:04:53.650> kind<00:04:53.889> of<00:04:53.949> obvious 00:04:55.490 --> 00:04:55.500 align:start position:0% mean I guess that's kind of obvious 00:04:55.500 --> 00:04:58.650 align:start position:0% mean I guess that's kind of obvious and<00:04:56.500> then<00:04:56.740> it<00:04:57.580> would<00:04:57.760> be<00:04:57.910> really<00:04:58.210> nice<00:04:58.419> to<00:04:58.479> just 00:04:58.650 --> 00:04:58.660 align:start position:0% and then it would be really nice to just 00:04:58.660 --> 00:05:00.330 align:start position:0% and then it would be really nice to just sort<00:04:59.050> of<00:04:59.110> know<00:04:59.350> that<00:04:59.530> like<00:04:59.770> before<00:04:59.919> even 00:05:00.330 --> 00:05:00.340 align:start position:0% sort of know that like before even 00:05:00.340 --> 00:05:03.900 align:start position:0% sort of know that like before even connecting<00:05:00.820> maybe<00:05:01.090> and<00:05:01.600> then<00:05:02.639> another<00:05:03.639> issue 00:05:03.900 --> 00:05:03.910 align:start position:0% connecting maybe and then another issue 00:05:03.910 --> 00:05:06.540 align:start position:0% connecting maybe and then another issue is<00:05:04.270> that<00:05:04.570> the<00:05:05.080> whole<00:05:05.320> system<00:05:05.530> is<00:05:06.039> basically 00:05:06.540 --> 00:05:06.550 align:start position:0% is that the whole system is basically 00:05:06.550 --> 00:05:11.550 align:start position:0% is that the whole system is basically frozen<00:05:07.389> so<00:05:09.539> making<00:05:10.539> any<00:05:10.660> change<00:05:11.020> to<00:05:11.229> any<00:05:11.410> of 00:05:11.550 --> 00:05:11.560 align:start position:0% frozen so making any change to any of 00:05:11.560 --> 00:05:13.590 align:start position:0% frozen so making any change to any of the<00:05:11.680> protocols<00:05:12.190> requires<00:05:12.639> like<00:05:13.000> really<00:05:13.389> tight 00:05:13.590 --> 00:05:13.600 align:start position:0% the protocols requires like really tight 00:05:13.600 --> 00:05:15.719 align:start position:0% the protocols requires like really tight coordinations<00:05:14.410> requires<00:05:14.979> implementation 00:05:15.719 --> 00:05:15.729 align:start position:0% coordinations requires implementation 00:05:15.729 --> 00:05:18.750 align:start position:0% coordinations requires implementation consensus<00:05:16.300> and<00:05:16.740> any<00:05:17.740> change<00:05:18.070> we<00:05:18.310> make<00:05:18.490> needs 00:05:18.750 --> 00:05:18.760 align:start position:0% consensus and any change we make needs 00:05:18.760 --> 00:05:21.840 align:start position:0% consensus and any change we make needs to<00:05:18.880> be<00:05:19.000> backwards<00:05:19.419> compatible<00:05:19.479> and<00:05:20.850> to 00:05:21.840 --> 00:05:21.850 align:start position:0% to be backwards compatible and to 00:05:21.850 --> 00:05:23.760 align:start position:0% to be backwards compatible and to achieve<00:05:22.150> upgrades<00:05:22.870> at<00:05:23.020> all<00:05:23.229> what<00:05:23.500> we've<00:05:23.620> done 00:05:23.760 --> 00:05:23.770 align:start position:0% achieve upgrades at all what we've done 00:05:23.770 --> 00:05:25.710 align:start position:0% achieve upgrades at all what we've done in<00:05:23.919> the<00:05:23.979> past<00:05:24.190> is<00:05:24.490> we<00:05:24.669> we've<00:05:25.090> made<00:05:25.389> all<00:05:25.600> the 00:05:25.710 --> 00:05:25.720 align:start position:0% in the past is we we've made all the 00:05:25.720 --> 00:05:27.390 align:start position:0% in the past is we we've made all the upgrades<00:05:26.080> backwards<00:05:26.500> compatible<00:05:27.039> and<00:05:27.190> we've 00:05:27.390 --> 00:05:27.400 align:start position:0% upgrades backwards compatible and we've 00:05:27.400 --> 00:05:29.700 align:start position:0% upgrades backwards compatible and we've tied<00:05:27.639> them<00:05:27.850> to<00:05:28.060> a<00:05:28.090> theorem<00:05:28.570> main<00:05:28.780> that<00:05:28.990> hard 00:05:29.700 --> 00:05:29.710 align:start position:0% tied them to a theorem main that hard 00:05:29.710 --> 00:05:33.779 align:start position:0% tied them to a theorem main that hard Forks<00:05:30.039> because<00:05:32.039> well<00:05:33.039> everyone<00:05:33.639> has<00:05:33.729> to 00:05:33.779 --> 00:05:33.789 align:start position:0% Forks because well everyone has to 00:05:33.789 --> 00:05:35.879 align:start position:0% Forks because well everyone has to upgrade<00:05:34.180> their<00:05:34.330> node<00:05:34.479> anyways<00:05:34.900> and<00:05:35.169> then<00:05:35.440> once 00:05:35.879 --> 00:05:35.889 align:start position:0% upgrade their node anyways and then once 00:05:35.889 --> 00:05:38.010 align:start position:0% upgrade their node anyways and then once the<00:05:36.280> Heart<00:05:36.460> Walk<00:05:36.610> is<00:05:36.880> successfully<00:05:37.630> launched 00:05:38.010 --> 00:05:38.020 align:start position:0% the Heart Walk is successfully launched 00:05:38.020 --> 00:05:40.379 align:start position:0% the Heart Walk is successfully launched we<00:05:38.860> can<00:05:39.039> start<00:05:39.280> phasing<00:05:39.520> out<00:05:39.760> the<00:05:39.940> old<00:05:40.090> stuff 00:05:40.379 --> 00:05:40.389 align:start position:0% we can start phasing out the old stuff 00:05:40.389 --> 00:05:42.600 align:start position:0% we can start phasing out the old stuff and<00:05:40.570> just<00:05:40.660> you<00:05:41.020> know<00:05:41.099> only<00:05:42.099> speak<00:05:42.340> the<00:05:42.370> new 00:05:42.600 --> 00:05:42.610 align:start position:0% and just you know only speak the new 00:05:42.610 --> 00:05:45.600 align:start position:0% and just you know only speak the new protocol<00:05:43.289> but<00:05:44.289> you<00:05:44.770> know<00:05:44.889> hard<00:05:45.130> folks<00:05:45.370> don't 00:05:45.600 --> 00:05:45.610 align:start position:0% protocol but you know hard folks don't 00:05:45.610 --> 00:05:47.070 align:start position:0% protocol but you know hard folks don't happen<00:05:45.910> all<00:05:46.060> that<00:05:46.180> often<00:05:46.389> and<00:05:46.750> we'd<00:05:46.900> rather 00:05:47.070 --> 00:05:47.080 align:start position:0% happen all that often and we'd rather 00:05:47.080 --> 00:05:48.990 align:start position:0% happen all that often and we'd rather you<00:05:47.320> know<00:05:47.470> make<00:05:47.680> changes<00:05:48.099> on<00:05:48.250> an<00:05:48.370> accelerated 00:05:48.990 --> 00:05:49.000 align:start position:0% you know make changes on an accelerated 00:05:49.000 --> 00:05:51.150 align:start position:0% you know make changes on an accelerated schedule<00:05:49.180> but<00:05:49.660> it's<00:05:49.840> like<00:05:50.440> really<00:05:50.889> not<00:05:51.039> that 00:05:51.150 --> 00:05:51.160 align:start position:0% schedule but it's like really not that 00:05:51.160 --> 00:05:53.430 align:start position:0% schedule but it's like really not that possible<00:05:51.639> and<00:05:51.880> then<00:05:52.450> finally<00:05:52.900> because<00:05:53.080> no 00:05:53.430 --> 00:05:53.440 align:start position:0% possible and then finally because no 00:05:53.440 --> 00:05:55.620 align:start position:0% possible and then finally because no discovery<00:05:53.800> only<00:05:54.130> relays<00:05:54.550> information<00:05:54.789> about 00:05:55.620 --> 00:05:55.630 align:start position:0% discovery only relays information about 00:05:55.630 --> 00:05:59.279 align:start position:0% discovery only relays information about the<00:05:55.780> oral<00:05:56.020> TX<00:05:56.320> protocol<00:05:57.780> there's<00:05:58.780> really<00:05:59.020> not 00:05:59.279 --> 00:05:59.289 align:start position:0% the oral TX protocol there's really not 00:05:59.289 --> 00:06:01.800 align:start position:0% the oral TX protocol there's really not there<00:06:00.130> isn't<00:06:00.340> like<00:06:00.729> any<00:06:00.970> sort<00:06:01.300> of<00:06:01.419> room<00:06:01.599> for 00:06:01.800 --> 00:06:01.810 align:start position:0% there isn't like any sort of room for 00:06:01.810 --> 00:06:04.950 align:start position:0% there isn't like any sort of room for experimentation<00:06:02.080> because<00:06:03.330> well<00:06:04.330> we 00:06:04.950 --> 00:06:04.960 align:start position:0% experimentation because well we 00:06:04.960 --> 00:06:06.839 align:start position:0% experimentation because well we essentially<00:06:05.470> stuck<00:06:05.830> with<00:06:06.039> our<00:06:06.190> lpx<00:06:06.550> and<00:06:06.789> the 00:06:06.839 --> 00:06:06.849 align:start position:0% essentially stuck with our lpx and the 00:06:06.849 --> 00:06:11.129 align:start position:0% essentially stuck with our lpx and the crypto<00:06:07.180> system<00:06:07.539> that<00:06:07.690> it<00:06:07.810> uses<00:06:09.180> so<00:06:10.180> improving 00:06:11.129 --> 00:06:11.139 align:start position:0% crypto system that it uses so improving 00:06:11.139 --> 00:06:13.379 align:start position:0% crypto system that it uses so improving these<00:06:11.380> things<00:06:11.740> is<00:06:12.010> the<00:06:12.520> no<00:06:12.669> discovery<00:06:13.180> version 00:06:13.379 --> 00:06:13.389 align:start position:0% these things is the no discovery version 00:06:13.389 --> 00:06:16.350 align:start position:0% these things is the no discovery version five<00:06:13.690> effort<00:06:14.229> and<00:06:14.789> with<00:06:15.789> no<00:06:16.000> discovery 00:06:16.350 --> 00:06:16.360 align:start position:0% five effort and with no discovery 00:06:16.360 --> 00:06:19.350 align:start position:0% five effort and with no discovery version<00:06:16.690> five<00:06:17.050> we<00:06:17.740> want<00:06:17.949> to<00:06:18.070> make<00:06:18.280> two<00:06:19.000> changes 00:06:19.350 --> 00:06:19.360 align:start position:0% version five we want to make two changes 00:06:19.360 --> 00:06:21.719 align:start position:0% version five we want to make two changes in<00:06:19.630> particular<00:06:20.070> or<00:06:21.070> rather<00:06:21.280> we<00:06:21.460> want<00:06:21.580> to 00:06:21.719 --> 00:06:21.729 align:start position:0% in particular or rather we want to 00:06:21.729 --> 00:06:23.969 align:start position:0% in particular or rather we want to achieve<00:06:22.030> two<00:06:22.300> things<00:06:22.330> in<00:06:22.690> particular<00:06:22.860> so<00:06:23.860> the 00:06:23.969 --> 00:06:23.979 align:start position:0% achieve two things in particular so the 00:06:23.979 --> 00:06:25.950 align:start position:0% achieve two things in particular so the first<00:06:24.160> one<00:06:24.400> is<00:06:24.430> we'd<00:06:25.090> rather<00:06:25.330> you<00:06:25.599> know<00:06:25.750> be 00:06:25.950 --> 00:06:25.960 align:start position:0% first one is we'd rather you know be 00:06:25.960 --> 00:06:27.900 align:start position:0% first one is we'd rather you know be able<00:06:26.110> to<00:06:26.260> find<00:06:26.620> notes<00:06:26.830> more<00:06:27.130> efficiently<00:06:27.610> and 00:06:27.900 --> 00:06:27.910 align:start position:0% able to find notes more efficiently and 00:06:27.910 --> 00:06:31.379 align:start position:0% able to find notes more efficiently and then<00:06:28.840> the<00:06:28.960> second<00:06:29.320> one<00:06:29.470> is<00:06:29.940> we'd<00:06:30.940> rather<00:06:31.120> know 00:06:31.379 --> 00:06:31.389 align:start position:0% then the second one is we'd rather know 00:06:31.389 --> 00:06:33.060 align:start position:0% then the second one is we'd rather know more<00:06:31.630> about<00:06:31.780> those<00:06:32.080> nodes<00:06:32.320> before<00:06:32.770> we<00:06:32.860> even 00:06:33.060 --> 00:06:33.070 align:start position:0% more about those nodes before we even 00:06:33.070 --> 00:06:36.119 align:start position:0% more about those nodes before we even connect 00:06:36.119 --> 00:06:36.129 align:start position:0% 00:06:36.129 --> 00:06:38.919 align:start position:0% so<00:06:37.129> the<00:06:37.729> first<00:06:37.969> part<00:06:38.179> of<00:06:38.300> our<00:06:38.449> solution<00:06:38.599> to 00:06:38.919 --> 00:06:38.929 align:start position:0% so the first part of our solution to 00:06:38.929 --> 00:06:42.639 align:start position:0% so the first part of our solution to these<00:06:39.169> issues<00:06:39.229> is<00:06:40.569> called<00:06:41.569> E&R<00:06:42.110> which<00:06:42.409> stands 00:06:42.639 --> 00:06:42.649 align:start position:0% these issues is called E&R which stands 00:06:42.649 --> 00:06:45.999 align:start position:0% these issues is called E&R which stands for<00:06:42.770> aetherium<00:06:43.429> node<00:06:43.669> records<00:06:44.319> so<00:06:45.319> earlier<00:06:45.679> in 00:06:45.999 --> 00:06:46.009 align:start position:0% for aetherium node records so earlier in 00:06:46.009 --> 00:06:48.309 align:start position:0% for aetherium node records so earlier in the<00:06:46.339> v4<00:06:46.699> overview<00:06:47.149> you<00:06:47.419> saw<00:06:47.659> that<00:06:47.869> the<00:06:48.050> DHT 00:06:48.309 --> 00:06:48.319 align:start position:0% the v4 overview you saw that the DHT 00:06:48.319 --> 00:06:50.739 align:start position:0% the v4 overview you saw that the DHT holds<00:06:49.009> all<00:06:49.189> those<00:06:49.369> a<00:06:49.610> node<00:06:49.849> addresses<00:06:50.509> and 00:06:50.739 --> 00:06:50.749 align:start position:0% holds all those a node addresses and 00:06:50.749 --> 00:06:53.019 align:start position:0% holds all those a node addresses and then<00:06:51.199> a<00:06:51.379> node<00:06:51.559> address<00:06:52.039> is<00:06:52.219> really<00:06:52.520> just<00:06:52.789> a 00:06:53.019 --> 00:06:53.029 align:start position:0% then a node address is really just a 00:06:53.029 --> 00:06:56.820 align:start position:0% then a node address is really just a public<00:06:53.629> key<00:06:53.809> and<00:06:54.080> IP<00:06:54.379> address<00:06:54.800> in<00:06:55.009> two<00:06:55.189> ports 00:06:56.820 --> 00:06:56.830 align:start position:0% public key and IP address in two ports 00:06:56.830 --> 00:07:00.730 align:start position:0% public key and IP address in two ports if<00:06:57.830> there<00:06:58.069> are<00:06:58.129> m<00:06:58.189> node<00:06:58.369> records<00:06:59.469> can<00:07:00.469> hold 00:07:00.730 --> 00:07:00.740 align:start position:0% if there are m node records can hold 00:07:00.740 --> 00:07:03.489 align:start position:0% if there are m node records can hold arbitrary<00:07:01.580> information<00:07:01.909> about<00:07:02.509> a<00:07:02.539> node<00:07:02.839> so 00:07:03.489 --> 00:07:03.499 align:start position:0% arbitrary information about a node so 00:07:03.499 --> 00:07:07.869 align:start position:0% arbitrary information about a node so that's<00:07:03.709> the<00:07:03.800> main<00:07:03.979> difference 00:07:07.869 --> 00:07:07.879 align:start position:0% 00:07:07.879 --> 00:07:10.089 align:start position:0% so<00:07:08.270> this<00:07:08.569> arbitrary<00:07:08.959> information<00:07:09.589> that<00:07:09.860> can 00:07:10.089 --> 00:07:10.099 align:start position:0% so this arbitrary information that can 00:07:10.099 --> 00:07:13.029 align:start position:0% so this arbitrary information that can be<00:07:10.129> information<00:07:11.089> about<00:07:11.259> the<00:07:12.259> capabilities<00:07:12.889> of 00:07:13.029 --> 00:07:13.039 align:start position:0% be information about the capabilities of 00:07:13.039 --> 00:07:14.739 align:start position:0% be information about the capabilities of the<00:07:13.159> node<00:07:13.339> it<00:07:13.610> can<00:07:13.819> be<00:07:13.969> information<00:07:14.599> about 00:07:14.739 --> 00:07:14.749 align:start position:0% the node it can be information about 00:07:14.749 --> 00:07:17.199 align:start position:0% the node it can be information about other<00:07:15.529> transport<00:07:16.159> protocols<00:07:16.580> spoken<00:07:17.029> by<00:07:17.149> the 00:07:17.199 --> 00:07:17.209 align:start position:0% other transport protocols spoken by the 00:07:17.209 --> 00:07:19.570 align:start position:0% other transport protocols spoken by the node<00:07:17.509> it<00:07:17.990> can<00:07:18.259> be<00:07:18.379> initial<00:07:18.860> key<00:07:19.039> material 00:07:19.570 --> 00:07:19.580 align:start position:0% node it can be initial key material 00:07:19.580 --> 00:07:21.969 align:start position:0% node it can be initial key material follows<00:07:19.939> for<00:07:20.449> those<00:07:20.599> transports<00:07:21.229> anything 00:07:21.969 --> 00:07:21.979 align:start position:0% follows for those transports anything 00:07:21.979 --> 00:07:24.519 align:start position:0% follows for those transports anything really<00:07:22.189> like<00:07:22.789> as<00:07:23.180> long<00:07:23.360> as<00:07:23.539> it<00:07:23.659> fits<00:07:23.809> into<00:07:24.050> 300 00:07:24.519 --> 00:07:24.529 align:start position:0% really like as long as it fits into 300 00:07:24.529 --> 00:07:27.790 align:start position:0% really like as long as it fits into 300 bytes<00:07:25.509> we're<00:07:26.509> basically<00:07:26.809> like<00:07:27.259> almost 00:07:27.790 --> 00:07:27.800 align:start position:0% bytes we're basically like almost 00:07:27.800 --> 00:07:30.549 align:start position:0% bytes we're basically like almost anything<00:07:28.249> can<00:07:28.369> be<00:07:28.519> relayed<00:07:28.819> there<00:07:29.089> and<00:07:29.629> the 00:07:30.549 --> 00:07:30.559 align:start position:0% anything can be relayed there and the 00:07:30.559 --> 00:07:33.339 align:start position:0% anything can be relayed there and the limitation<00:07:31.159> of<00:07:31.309> 300<00:07:31.909> bytes<00:07:32.119> is<00:07:32.419> important 00:07:33.339 --> 00:07:33.349 align:start position:0% limitation of 300 bytes is important 00:07:33.349 --> 00:07:37.509 align:start position:0% limitation of 300 bytes is important because<00:07:33.819> E&R<00:07:34.819> is<00:07:35.119> a<00:07:35.689> separate<00:07:36.169> format<00:07:36.619> a 00:07:37.509 --> 00:07:37.519 align:start position:0% because E&R is a separate format a 00:07:37.519 --> 00:07:39.969 align:start position:0% because E&R is a separate format a seperate<00:07:38.269> spec<00:07:38.479> even<00:07:38.839> and<00:07:38.990> it's<00:07:39.110> not<00:07:39.259> at<00:07:39.740> all 00:07:39.969 --> 00:07:39.979 align:start position:0% seperate spec even and it's not at all 00:07:39.979 --> 00:07:43.239 align:start position:0% seperate spec even and it's not at all connected<00:07:40.339> to<00:07:40.580> the<00:07:40.789> DHT<00:07:41.110> so<00:07:42.110> you<00:07:42.740> can<00:07:42.949> relay 00:07:43.239 --> 00:07:43.249 align:start position:0% connected to the DHT so you can relay 00:07:43.249 --> 00:07:45.339 align:start position:0% connected to the DHT so you can relay those<00:07:43.430> records<00:07:43.939> through<00:07:44.269> any<00:07:44.449> other<00:07:44.569> means<00:07:44.809> if 00:07:45.339 --> 00:07:45.349 align:start position:0% those records through any other means if 00:07:45.349 --> 00:07:48.579 align:start position:0% those records through any other means if you<00:07:45.469> want<00:07:45.619> to<00:07:45.740> including<00:07:46.459> say<00:07:46.729> a<00:07:47.029> DNS<00:07:48.019> record 00:07:48.579 --> 00:07:48.589 align:start position:0% you want to including say a DNS record 00:07:48.589 --> 00:07:51.129 align:start position:0% you want to including say a DNS record or<00:07:48.769> something<00:07:49.069> like<00:07:49.189> that<00:07:49.539> and<00:07:50.539> then<00:07:50.689> finally 00:07:51.129 --> 00:07:51.139 align:start position:0% or something like that and then finally 00:07:51.139 --> 00:07:54.249 align:start position:0% or something like that and then finally node<00:07:51.949> records<00:07:52.399> are<00:07:52.729> signed<00:07:53.389> and<00:07:53.599> also 00:07:54.249 --> 00:07:54.259 align:start position:0% node records are signed and also 00:07:54.259 --> 00:07:56.980 align:start position:0% node records are signed and also versioned<00:07:54.829> so<00:07:55.399> if<00:07:55.699> you<00:07:55.849> have<00:07:56.029> two<00:07:56.300> versions<00:07:56.809> of 00:07:56.980 --> 00:07:56.990 align:start position:0% versioned so if you have two versions of 00:07:56.990 --> 00:07:59.290 align:start position:0% versioned so if you have two versions of the<00:07:57.619> record<00:07:57.949> that<00:07:58.129> described<00:07:58.519> the<00:07:58.789> same<00:07:58.999> that 00:07:59.290 --> 00:07:59.300 align:start position:0% the record that described the same that 00:07:59.300 --> 00:08:01.059 align:start position:0% the record that described the same that describes<00:07:59.719> the<00:07:59.869> same<00:08:00.050> node<00:08:00.349> you<00:08:00.889> can 00:08:01.059 --> 00:08:01.069 align:start position:0% describes the same node you can 00:08:01.069 --> 00:08:03.249 align:start position:0% describes the same node you can determine<00:08:01.369> which<00:08:01.699> one<00:08:01.879> is<00:08:01.909> newer<00:08:02.269> for<00:08:02.809> example 00:08:03.249 --> 00:08:03.259 align:start position:0% determine which one is newer for example 00:08:03.259 --> 00:08:08.980 align:start position:0% determine which one is newer for example and<00:08:05.379> we<00:08:06.379> think<00:08:06.649> that<00:08:06.709> you<00:08:07.159> know<00:08:07.399> is<00:08:08.209> a<00:08:08.749> good 00:08:08.980 --> 00:08:08.990 align:start position:0% and we think that you know is a good 00:08:08.990 --> 00:08:10.420 align:start position:0% and we think that you know is a good solution<00:08:09.259> for<00:08:09.469> the<00:08:09.769> transportability 00:08:10.420 --> 00:08:10.430 align:start position:0% solution for the transportability 00:08:10.430 --> 00:08:13.239 align:start position:0% solution for the transportability problem<00:08:11.119> because<00:08:11.899> again<00:08:12.169> information<00:08:12.949> about 00:08:13.239 --> 00:08:13.249 align:start position:0% problem because again information about 00:08:13.249 --> 00:08:15.219 align:start position:0% problem because again information about arbitrary<00:08:13.699> transports<00:08:14.419> can<00:08:14.659> be<00:08:14.809> related<00:08:15.110> to 00:08:15.219 --> 00:08:15.229 align:start position:0% arbitrary transports can be related to 00:08:15.229 --> 00:08:18.790 align:start position:0% arbitrary transports can be related to this<00:08:15.529> protocol<00:08:16.009> and<00:08:17.229> well<00:08:18.229> yeah<00:08:18.589> because 00:08:18.790 --> 00:08:18.800 align:start position:0% this protocol and well yeah because 00:08:18.800 --> 00:08:20.889 align:start position:0% this protocol and well yeah because there's<00:08:19.189> just<00:08:19.249> a<00:08:19.550> lot<00:08:19.729> more<00:08:19.759> room<00:08:20.119> to<00:08:20.149> put<00:08:20.599> you 00:08:20.889 --> 00:08:20.899 align:start position:0% there's just a lot more room to put you 00:08:20.899 --> 00:08:26.469 align:start position:0% there's just a lot more room to put you know<00:08:21.219> information<00:08:22.219> about<00:08:23.559> anything<00:08:24.559> so<00:08:25.479> we 00:08:26.469 --> 00:08:26.479 align:start position:0% know information about anything so we 00:08:26.479 --> 00:08:28.359 align:start position:0% know information about anything so we still<00:08:26.779> need<00:08:26.809> implementation<00:08:27.800> consensus 00:08:28.359 --> 00:08:28.369 align:start position:0% still need implementation consensus 00:08:28.369 --> 00:08:30.100 align:start position:0% still need implementation consensus though<00:08:28.519> because<00:08:28.909> you<00:08:29.089> know<00:08:29.209> in<00:08:29.419> order<00:08:29.569> to<00:08:29.809> be 00:08:30.100 --> 00:08:30.110 align:start position:0% though because you know in order to be 00:08:30.110 --> 00:08:31.809 align:start position:0% though because you know in order to be able<00:08:30.229> to<00:08:30.379> talk<00:08:30.649> to<00:08:30.800> everyone<00:08:31.069> everyone<00:08:31.550> kind 00:08:31.809 --> 00:08:31.819 align:start position:0% able to talk to everyone everyone kind 00:08:31.819 --> 00:08:34.120 align:start position:0% able to talk to everyone everyone kind of<00:08:31.849> has<00:08:31.969> to<00:08:31.999> agree<00:08:32.360> on<00:08:32.449> you<00:08:32.959> know<00:08:33.079> what<00:08:34.009> the 00:08:34.120 --> 00:08:34.130 align:start position:0% of has to agree on you know what the 00:08:34.130 --> 00:08:36.209 align:start position:0% of has to agree on you know what the language<00:08:34.339> is<00:08:34.610> that<00:08:34.639> they're<00:08:34.939> speaking<00:08:35.149> to 00:08:36.209 --> 00:08:36.219 align:start position:0% language is that they're speaking to 00:08:36.219 --> 00:08:38.259 align:start position:0% language is that they're speaking to they're<00:08:37.219> using<00:08:37.550> when<00:08:37.669> speaking<00:08:37.939> to<00:08:38.089> each 00:08:38.259 --> 00:08:38.269 align:start position:0% they're using when speaking to each 00:08:38.269 --> 00:08:43.029 align:start position:0% they're using when speaking to each other<00:08:38.449> and<00:08:38.949> it<00:08:39.949> is<00:08:40.069> very<00:08:40.279> likely<00:08:40.550> that<00:08:42.009> for<00:08:43.009> a 00:08:43.029 --> 00:08:43.039 align:start position:0% other and it is very likely that for a 00:08:43.039 --> 00:08:45.579 align:start position:0% other and it is very likely that for a considerable<00:08:43.729> amount<00:08:43.969> of<00:08:44.089> time<00:08:44.149> the<00:08:45.019> lowest 00:08:45.579 --> 00:08:45.589 align:start position:0% considerable amount of time the lowest 00:08:45.589 --> 00:08:48.429 align:start position:0% considerable amount of time the lowest common<00:08:45.769> denominator<00:08:46.370> will<00:08:46.610> be<00:08:46.939> our<00:08:47.149> lpx<00:08:47.540> but 00:08:48.429 --> 00:08:48.439 align:start position:0% common denominator will be our lpx but 00:08:48.439 --> 00:08:52.929 align:start position:0% common denominator will be our lpx but eventually<00:08:50.050> one<00:08:51.050> CNR<00:08:51.470> is<00:08:51.589> launched<00:08:52.010> we<00:08:52.699> can 00:08:52.929 --> 00:08:52.939 align:start position:0% eventually one CNR is launched we can 00:08:52.939 --> 00:08:55.780 align:start position:0% eventually one CNR is launched we can actually<00:08:53.740> try<00:08:54.740> out<00:08:54.769> different<00:08:54.920> transports 00:08:55.780 --> 00:08:55.790 align:start position:0% actually try out different transports 00:08:55.790 --> 00:08:59.019 align:start position:0% actually try out different transports find<00:08:56.420> a<00:08:56.540> viable<00:08:56.750> alternative<00:08:57.079> and<00:08:57.769> then<00:08:58.029> you 00:08:59.019 --> 00:08:59.029 align:start position:0% find a viable alternative and then you 00:08:59.029 --> 00:09:02.439 align:start position:0% find a viable alternative and then you know<00:08:59.180> maybe<00:08:59.990> like<00:09:00.439> at<00:09:00.649> the<00:09:00.769> end<00:09:00.920> of<00:09:01.149> 2020<00:09:02.149> like 00:09:02.439 --> 00:09:02.449 align:start position:0% know maybe like at the end of 2020 like 00:09:02.449 --> 00:09:08.799 align:start position:0% know maybe like at the end of 2020 like delete<00:09:02.779> or<00:09:02.959> LP<00:09:03.199> access<00:09:05.769> so<00:09:07.209> in<00:09:08.209> order<00:09:08.389> to<00:09:08.540> get 00:09:08.799 --> 00:09:08.809 align:start position:0% delete or LP access so in order to get 00:09:08.809 --> 00:09:11.259 align:start position:0% delete or LP access so in order to get in<00:09:09.319> our<00:09:09.559> launch<00:09:09.860> though<00:09:10.189> we<00:09:10.790> need<00:09:10.970> to<00:09:11.089> upgrade 00:09:11.259 --> 00:09:11.269 align:start position:0% in our launch though we need to upgrade 00:09:11.269 --> 00:09:14.110 align:start position:0% in our launch though we need to upgrade the<00:09:11.600> discovery<00:09:12.079> protocol<00:09:12.620> this<00:09:13.610> is<00:09:13.760> something 00:09:14.110 --> 00:09:14.120 align:start position:0% the discovery protocol this is something 00:09:14.120 --> 00:09:17.199 align:start position:0% the discovery protocol this is something that<00:09:14.149> needs<00:09:14.420> to<00:09:14.510> happen<00:09:14.720> once<00:09:15.230> and<00:09:15.670> it<00:09:16.670> will<00:09:16.939> be 00:09:17.199 --> 00:09:17.209 align:start position:0% that needs to happen once and it will be 00:09:17.209 --> 00:09:19.900 align:start position:0% that needs to happen once and it will be a<00:09:17.420> backwards<00:09:17.870> incompatible<00:09:18.050> upgrade<00:09:18.980> so 00:09:19.900 --> 00:09:19.910 align:start position:0% a backwards incompatible upgrade so 00:09:19.910 --> 00:09:23.079 align:start position:0% a backwards incompatible upgrade so likely<00:09:20.870> what<00:09:21.290> the<00:09:22.069> way<00:09:22.220> this<00:09:22.399> will<00:09:22.610> work<00:09:22.639> is 00:09:23.079 --> 00:09:23.089 align:start position:0% likely what the way this will work is 00:09:23.089 --> 00:09:26.439 align:start position:0% likely what the way this will work is that<00:09:23.660> the<00:09:24.170> discovery<00:09:24.680> version<00:09:24.889> 5<00:09:25.250> DHT<00:09:25.790> will<00:09:26.300> be 00:09:26.439 --> 00:09:26.449 align:start position:0% that the discovery version 5 DHT will be 00:09:26.449 --> 00:09:28.809 align:start position:0% that the discovery version 5 DHT will be a<00:09:26.480> totally<00:09:26.899> separate<00:09:27.319> DHT<00:09:27.860> that<00:09:28.370> will<00:09:28.550> run<00:09:28.699> in 00:09:28.809 --> 00:09:28.819 align:start position:0% a totally separate DHT that will run in 00:09:28.819 --> 00:09:31.949 align:start position:0% a totally separate DHT that will run in parallel<00:09:28.850> to<00:09:29.480> the<00:09:29.630> current<00:09:29.779> system<00:09:30.290> and 00:09:31.949 --> 00:09:31.959 align:start position:0% parallel to the current system and 00:09:31.959 --> 00:09:33.939 align:start position:0% parallel to the current system and because<00:09:32.959> this<00:09:33.110> is<00:09:33.230> kind<00:09:33.470> of<00:09:33.529> a<00:09:33.649> unique 00:09:33.939 --> 00:09:33.949 align:start position:0% because this is kind of a unique 00:09:33.949 --> 00:09:36.579 align:start position:0% because this is kind of a unique opportunity<00:09:34.220> for<00:09:34.579> us<00:09:34.809> in<00:09:35.809> addition<00:09:36.260> to<00:09:36.439> you 00:09:36.579 --> 00:09:36.589 align:start position:0% opportunity for us in addition to you 00:09:36.589 --> 00:09:38.319 align:start position:0% opportunity for us in addition to you know<00:09:36.649> just<00:09:36.949> including<00:09:37.399> support<00:09:37.760> for<00:09:37.880> en<00:09:38.149> our 00:09:38.319 --> 00:09:38.329 align:start position:0% know just including support for en our 00:09:38.329 --> 00:09:40.269 align:start position:0% know just including support for en our we<00:09:38.809> want<00:09:39.019> to<00:09:39.110> make<00:09:39.290> a<00:09:39.319> bunch<00:09:39.589> of<00:09:39.709> other<00:09:39.860> changes 00:09:40.269 --> 00:09:40.279 align:start position:0% we want to make a bunch of other changes 00:09:40.279 --> 00:09:44.079 align:start position:0% we want to make a bunch of other changes to<00:09:40.430> the<00:09:40.519> protocol<00:09:41.170> in<00:09:42.170> particular<00:09:43.089> one 00:09:44.079 --> 00:09:44.089 align:start position:0% to the protocol in particular one 00:09:44.089 --> 00:09:47.170 align:start position:0% to the protocol in particular one problem<00:09:44.630> that<00:09:44.660> the<00:09:44.959> v4<00:09:45.380> discovery<00:09:46.370> one 00:09:47.170 --> 00:09:47.180 align:start position:0% problem that the v4 discovery one 00:09:47.180 --> 00:09:49.150 align:start position:0% problem that the v4 discovery one problem<00:09:47.449> that<00:09:47.510> that<00:09:47.779> v4<00:09:48.230> discovery<00:09:48.740> protocol 00:09:49.150 --> 00:09:49.160 align:start position:0% problem that that v4 discovery protocol 00:09:49.160 --> 00:09:53.400 align:start position:0% problem that that v4 discovery protocol has<00:09:49.399> is<00:09:49.699> its<00:09:50.300> reliance<00:09:50.750> on<00:09:50.899> absolute<00:09:51.439> time<00:09:52.059> so 00:09:53.400 --> 00:09:53.410 align:start position:0% has is its reliance on absolute time so 00:09:53.410 --> 00:09:55.809 align:start position:0% has is its reliance on absolute time so maybe<00:09:54.410> you<00:09:54.860> know<00:09:54.980> some<00:09:55.189> of<00:09:55.309> you<00:09:55.430> have<00:09:55.610> actually 00:09:55.809 --> 00:09:55.819 align:start position:0% maybe you know some of you have actually 00:09:55.819 --> 00:09:58.389 align:start position:0% maybe you know some of you have actually experienced<00:09:56.420> this<00:09:56.569> so<00:09:57.019> if<00:09:57.319> your<00:09:57.709> clock<00:09:57.949> is<00:09:58.130> off 00:09:58.389 --> 00:09:58.399 align:start position:0% experienced this so if your clock is off 00:09:58.399 --> 00:10:01.540 align:start position:0% experienced this so if your clock is off let's<00:09:59.180> say<00:09:59.420> bye-bye<00:09:59.660> to<00:10:00.110> minutes<00:10:00.680> you<00:10:01.339> won't 00:10:01.540 --> 00:10:01.550 align:start position:0% let's say bye-bye to minutes you won't 00:10:01.550 --> 00:10:02.920 align:start position:0% let's say bye-bye to minutes you won't really<00:10:01.760> be<00:10:01.970> able<00:10:02.089> to<00:10:02.269> connect<00:10:02.689> to<00:10:02.750> the<00:10:02.839> network 00:10:02.920 --> 00:10:02.930 align:start position:0% really be able to connect to the network 00:10:02.930 --> 00:10:07.389 align:start position:0% really be able to connect to the network and<00:10:04.300> we've<00:10:05.300> worked<00:10:06.079> around<00:10:06.500> this<00:10:06.680> by<00:10:06.920> like 00:10:07.389 --> 00:10:07.399 align:start position:0% and we've worked around this by like 00:10:07.399 --> 00:10:09.490 align:start position:0% and we've worked around this by like alerting<00:10:07.939> users<00:10:08.180> when<00:10:08.569> the<00:10:08.720> clock<00:10:08.959> seems<00:10:09.230> off 00:10:09.490 --> 00:10:09.500 align:start position:0% alerting users when the clock seems off 00:10:09.500 --> 00:10:11.679 align:start position:0% alerting users when the clock seems off but<00:10:10.100> that's<00:10:10.279> a<00:10:10.399> really<00:10:10.639> ugly<00:10:10.760> workaround<00:10:11.480> and 00:10:11.679 --> 00:10:11.689 align:start position:0% but that's a really ugly workaround and 00:10:11.689 --> 00:10:13.780 align:start position:0% but that's a really ugly workaround and you<00:10:11.750> know<00:10:11.899> like<00:10:12.319> we<00:10:12.470> might<00:10:12.680> just<00:10:12.920> fix<00:10:13.490> it<00:10:13.639> in 00:10:13.780 --> 00:10:13.790 align:start position:0% you know like we might just fix it in 00:10:13.790 --> 00:10:18.819 align:start position:0% you know like we might just fix it in the<00:10:13.819> protocol<00:10:14.269> this<00:10:14.449> time<00:10:14.750> and<00:10:15.740> then<00:10:17.829> with 00:10:18.819 --> 00:10:18.829 align:start position:0% the protocol this time and then with 00:10:18.829 --> 00:10:21.579 align:start position:0% the protocol this time and then with many<00:10:19.100> of<00:10:19.279> the<00:10:19.430> notes<00:10:19.639> in<00:10:20.300> the<00:10:20.480> DHT<00:10:20.750> you'll<00:10:21.290> find 00:10:21.579 --> 00:10:21.589 align:start position:0% many of the notes in the DHT you'll find 00:10:21.589 --> 00:10:23.170 align:start position:0% many of the notes in the DHT you'll find that<00:10:21.769> the<00:10:21.920> information<00:10:22.040> that's<00:10:22.670> listed<00:10:22.970> there 00:10:23.170 --> 00:10:23.180 align:start position:0% that the information that's listed there 00:10:23.180 --> 00:10:26.590 align:start position:0% that the information that's listed there isn't<00:10:23.689> very<00:10:24.139> accurate<00:10:24.680> so<00:10:24.980> you<00:10:25.250> might<00:10:26.209> you 00:10:26.590 --> 00:10:26.600 align:start position:0% isn't very accurate so you might you 00:10:26.600 --> 00:10:28.150 align:start position:0% isn't very accurate so you might you know<00:10:26.720> not<00:10:26.930> be<00:10:27.050> able<00:10:27.230> to<00:10:27.380> connect<00:10:27.680> to<00:10:27.740> this<00:10:27.920> node 00:10:28.150 --> 00:10:28.160 align:start position:0% know not be able to connect to this node 00:10:28.160 --> 00:10:30.009 align:start position:0% know not be able to connect to this node at<00:10:28.309> all<00:10:28.490> even<00:10:28.850> though<00:10:28.970> it's<00:10:29.000> listed<00:10:29.509> there<00:10:29.689> and 00:10:30.009 --> 00:10:30.019 align:start position:0% at all even though it's listed there and 00:10:30.019 --> 00:10:32.679 align:start position:0% at all even though it's listed there and in<00:10:30.740> v5<00:10:31.160> we<00:10:31.519> want<00:10:31.759> to<00:10:31.880> introduce<00:10:32.180> this<00:10:32.480> concept 00:10:32.679 --> 00:10:32.689 align:start position:0% in v5 we want to introduce this concept 00:10:32.689 --> 00:10:35.920 align:start position:0% in v5 we want to introduce this concept of<00:10:33.050> endpoint<00:10:33.559> proofs<00:10:33.860> where<00:10:34.519> the<00:10:35.059> DHT<00:10:35.360> ensures 00:10:35.920 --> 00:10:35.930 align:start position:0% of endpoint proofs where the DHT ensures 00:10:35.930 --> 00:10:39.040 align:start position:0% of endpoint proofs where the DHT ensures that<00:10:36.079> if<00:10:36.649> if<00:10:37.370> nodes<00:10:37.819> record<00:10:38.300> is<00:10:38.480> listed<00:10:38.839> in<00:10:38.930> the 00:10:39.040 --> 00:10:39.050 align:start position:0% that if if nodes record is listed in the 00:10:39.050 --> 00:10:41.799 align:start position:0% that if if nodes record is listed in the DHT<00:10:39.319> you<00:10:39.800> there's<00:10:40.339> a<00:10:40.430> pretty<00:10:41.059> fair<00:10:41.540> chance 00:10:41.799 --> 00:10:41.809 align:start position:0% DHT you there's a pretty fair chance 00:10:41.809 --> 00:10:43.269 align:start position:0% DHT you there's a pretty fair chance that<00:10:41.959> you'll<00:10:42.230> actually<00:10:42.380> be<00:10:42.620> able<00:10:42.889> to<00:10:43.009> talk<00:10:43.220> to 00:10:43.269 --> 00:10:43.279 align:start position:0% that you'll actually be able to talk to 00:10:43.279 --> 00:10:48.009 align:start position:0% that you'll actually be able to talk to it<00:10:43.459> and<00:10:45.309> then<00:10:46.309> finally<00:10:46.790> we<00:10:46.939> have<00:10:47.120> another<00:10:47.360> we 00:10:48.009 --> 00:10:48.019 align:start position:0% it and then finally we have another we 00:10:48.019 --> 00:10:49.769 align:start position:0% it and then finally we have another we have<00:10:48.139> another<00:10:48.410> improvement<00:10:48.800> which<00:10:49.370> is<00:10:49.399> also 00:10:49.769 --> 00:10:49.779 align:start position:0% have another improvement which is also 00:10:49.779 --> 00:10:53.500 align:start position:0% have another improvement which is also which<00:10:50.779> can<00:10:50.990> be<00:10:51.139> considered<00:10:51.760> an<00:10:52.760> extension<00:10:53.120> of 00:10:53.500 --> 00:10:53.510 align:start position:0% which can be considered an extension of 00:10:53.510 --> 00:10:56.019 align:start position:0% which can be considered an extension of the<00:10:54.380> of<00:10:54.589> the<00:10:54.709> DHT<00:10:54.980> protocol 00:10:56.019 --> 00:10:56.029 align:start position:0% the of the DHT protocol 00:10:56.029 --> 00:10:58.689 align:start position:0% the of the DHT protocol and<00:10:56.149> this<00:10:56.930> is<00:10:57.110> the<00:10:57.350> this<00:10:58.069> one<00:10:58.129> is<00:10:58.550> about 00:10:58.689 --> 00:10:58.699 align:start position:0% and this is the this one is about 00:10:58.699 --> 00:11:06.600 align:start position:0% and this is the this one is about finding<00:10:59.449> notes<00:10:59.779> more<00:11:00.019> efficiently<00:11:00.470> so<00:11:04.779> in<00:11:05.779> a 00:11:06.600 --> 00:11:06.610 align:start position:0% finding notes more efficiently so in a 00:11:06.610 --> 00:11:10.780 align:start position:0% finding notes more efficiently so in a classical<00:11:07.610> THC<00:11:08.089> so<00:11:08.480> to<00:11:08.540> say<00:11:09.100> the<00:11:10.100> THC<00:11:10.370> is<00:11:10.670> an 00:11:10.780 --> 00:11:10.790 align:start position:0% classical THC so to say the THC is an 00:11:10.790 --> 00:11:14.079 align:start position:0% classical THC so to say the THC is an index<00:11:11.180> of<00:11:11.329> nodes<00:11:11.720> by<00:11:12.370> by<00:11:13.370> their<00:11:13.579> public<00:11:13.910> key 00:11:14.079 --> 00:11:14.089 align:start position:0% index of nodes by by their public key 00:11:14.089 --> 00:11:17.710 align:start position:0% index of nodes by by their public key and<00:11:14.500> it<00:11:15.500> maps<00:11:15.949> public<00:11:16.910> keys<00:11:17.120> to<00:11:17.360> know<00:11:17.660> the 00:11:17.710 --> 00:11:17.720 align:start position:0% and it maps public keys to know the 00:11:17.720 --> 00:11:31.660 align:start position:0% and it maps public keys to know the endpoints<00:11:18.319> but<00:11:28.029> well<00:11:29.029> so<00:11:29.709> the<00:11:30.709> nodes<00:11:30.889> in<00:11:31.519> the 00:11:31.660 --> 00:11:31.670 align:start position:0% endpoints but well so the nodes in the 00:11:31.670 --> 00:11:33.280 align:start position:0% endpoints but well so the nodes in the DHT<00:11:31.910> though<00:11:32.269> they're<00:11:32.449> not<00:11:32.600> in<00:11:32.660> any<00:11:32.930> kind<00:11:33.230> of 00:11:33.280 --> 00:11:33.290 align:start position:0% DHT though they're not in any kind of 00:11:33.290 --> 00:11:35.949 align:start position:0% DHT though they're not in any kind of useful<00:11:33.500> order<00:11:34.040> so<00:11:34.490> you'll<00:11:34.670> find<00:11:35.000> an<00:11:35.600> if<00:11:35.779> there 00:11:35.949 --> 00:11:35.959 align:start position:0% useful order so you'll find an if there 00:11:35.959 --> 00:11:37.600 align:start position:0% useful order so you'll find an if there are<00:11:36.050> may<00:11:36.230> not<00:11:36.259> note<00:11:36.620> next<00:11:36.949> to<00:11:37.160> an<00:11:37.220> a<00:11:37.310> theorem 00:11:37.600 --> 00:11:37.610 align:start position:0% are may not note next to an a theorem 00:11:37.610 --> 00:11:39.579 align:start position:0% are may not note next to an a theorem classic<00:11:38.060> node<00:11:38.269> next<00:11:38.569> to<00:11:38.779> a<00:11:38.810> node<00:11:39.019> that<00:11:39.050> doesn't 00:11:39.579 --> 00:11:39.589 align:start position:0% classic node next to a node that doesn't 00:11:39.589 --> 00:11:40.990 align:start position:0% classic node next to a node that doesn't really<00:11:39.740> participate<00:11:40.370> in<00:11:40.399> the<00:11:40.610> ethereum 00:11:40.990 --> 00:11:41.000 align:start position:0% really participate in the ethereum 00:11:41.000 --> 00:11:43.869 align:start position:0% really participate in the ethereum blockchain<00:11:41.029> at<00:11:41.540> all<00:11:41.750> and<00:11:42.550> there<00:11:43.550> isn't<00:11:43.759> really 00:11:43.869 --> 00:11:43.879 align:start position:0% blockchain at all and there isn't really 00:11:43.879 --> 00:11:46.269 align:start position:0% blockchain at all and there isn't really like<00:11:44.029> an<00:11:44.660> efficient<00:11:45.110> way<00:11:45.199> of<00:11:45.230> like<00:11:45.649> knowing 00:11:46.269 --> 00:11:46.279 align:start position:0% like an efficient way of like knowing 00:11:46.279 --> 00:11:47.860 align:start position:0% like an efficient way of like knowing about<00:11:46.459> you<00:11:46.819> know<00:11:46.910> just<00:11:47.240> in<00:11:47.389> those<00:11:47.509> that<00:11:47.720> you 00:11:47.860 --> 00:11:47.870 align:start position:0% about you know just in those that you 00:11:47.870 --> 00:11:53.650 align:start position:0% about you know just in those that you care<00:11:48.110> about<00:11:48.230> and<00:11:49.959> contrasting<00:11:50.959> that<00:11:50.990> the<00:11:52.660> the 00:11:53.650 --> 00:11:53.660 align:start position:0% care about and contrasting that the the 00:11:53.660 --> 00:11:56.019 align:start position:0% care about and contrasting that the the topic<00:11:53.899> index<00:11:54.350> that<00:11:54.470> we<00:11:54.620> have<00:11:54.769> in<00:11:54.920> mind<00:11:55.129> is<00:11:55.339> sort 00:11:56.019 --> 00:11:56.029 align:start position:0% topic index that we have in mind is sort 00:11:56.029 --> 00:11:58.960 align:start position:0% topic index that we have in mind is sort of<00:11:56.089> like<00:11:56.300> in<00:11:56.839> index<00:11:57.230> of<00:11:57.410> all<00:11:57.589> the<00:11:57.709> nodes<00:11:57.920> by<00:11:58.220> by 00:11:58.960 --> 00:11:58.970 align:start position:0% of like in index of all the nodes by by 00:11:58.970 --> 00:12:00.910 align:start position:0% of like in index of all the nodes by by that<00:11:59.149> by<00:11:59.389> the<00:11:59.449> topic<00:11:59.990> or<00:12:00.199> the<00:12:00.319> service<00:12:00.740> that 00:12:00.910 --> 00:12:00.920 align:start position:0% that by the topic or the service that 00:12:00.920 --> 00:12:04.569 align:start position:0% that by the topic or the service that they<00:12:01.069> are<00:12:01.100> providing<00:12:02.470> I<00:12:03.470> don't<00:12:04.129> have<00:12:04.279> a<00:12:04.309> lot<00:12:04.550> of 00:12:04.569 --> 00:12:04.579 align:start position:0% they are providing I don't have a lot of 00:12:04.579 --> 00:12:06.819 align:start position:0% they are providing I don't have a lot of time<00:12:04.850> today<00:12:05.059> to<00:12:05.720> really<00:12:05.990> go<00:12:06.110> into<00:12:06.259> the<00:12:06.439> detail 00:12:06.819 --> 00:12:06.829 align:start position:0% time today to really go into the detail 00:12:06.829 --> 00:12:08.949 align:start position:0% time today to really go into the detail or<00:12:06.980> how<00:12:07.100> this<00:12:07.309> works<00:12:07.579> but<00:12:08.029> I<00:12:08.360> can<00:12:08.600> give<00:12:08.779> you<00:12:08.870> an 00:12:08.949 --> 00:12:08.959 align:start position:0% or how this works but I can give you an 00:12:08.959 --> 00:12:10.689 align:start position:0% or how this works but I can give you an overview<00:12:09.290> of<00:12:09.470> the<00:12:09.740> design<00:12:10.069> constraints<00:12:10.519> that 00:12:10.689 --> 00:12:10.699 align:start position:0% overview of the design constraints that 00:12:10.699 --> 00:12:14.319 align:start position:0% overview of the design constraints that we<00:12:10.939> set<00:12:11.180> when<00:12:12.490> when<00:12:13.490> when<00:12:13.819> making<00:12:14.059> this 00:12:14.319 --> 00:12:14.329 align:start position:0% we set when when when making this 00:12:14.329 --> 00:12:17.679 align:start position:0% we set when when when making this protocol<00:12:14.740> so<00:12:15.740> the<00:12:16.189> first<00:12:16.490> big<00:12:17.000> constraint 00:12:17.679 --> 00:12:17.689 align:start position:0% protocol so the first big constraint 00:12:17.689 --> 00:12:19.600 align:start position:0% protocol so the first big constraint that<00:12:17.899> we<00:12:17.990> had<00:12:18.199> is<00:12:18.470> that<00:12:18.529> we<00:12:18.980> don't<00:12:19.279> want<00:12:19.490> to 00:12:19.600 --> 00:12:19.610 align:start position:0% that we had is that we don't want to 00:12:19.610 --> 00:12:23.319 align:start position:0% that we had is that we don't want to split<00:12:19.850> up<00:12:19.910> the<00:12:20.180> DHT<00:12:20.500> because<00:12:21.500> the<00:12:22.309> DHT<00:12:23.029> is 00:12:23.319 --> 00:12:23.329 align:start position:0% split up the DHT because the DHT is 00:12:23.329 --> 00:12:27.030 align:start position:0% split up the DHT because the DHT is bigger<00:12:24.139> is<00:12:24.559> better<00:12:25.370> right<00:12:25.759> I<00:12:26.149> mean 00:12:27.030 --> 00:12:27.040 align:start position:0% bigger is better right I mean 00:12:27.040 --> 00:12:29.559 align:start position:0% bigger is better right I mean fundamentally<00:12:28.040> the<00:12:28.579> security<00:12:29.089> of<00:12:29.120> a<00:12:29.329> DHT 00:12:29.559 --> 00:12:29.569 align:start position:0% fundamentally the security of a DHT 00:12:29.569 --> 00:12:31.809 align:start position:0% fundamentally the security of a DHT depends<00:12:30.350> on<00:12:30.500> the<00:12:30.680> number<00:12:30.920> of<00:12:31.009> participants<00:12:31.550> in 00:12:31.809 --> 00:12:31.819 align:start position:0% depends on the number of participants in 00:12:31.819 --> 00:12:34.269 align:start position:0% depends on the number of participants in it<00:12:31.970> so<00:12:32.509> you'd<00:12:32.750> want<00:12:32.990> to<00:12:33.110> like<00:12:33.620> have<00:12:33.949> always 00:12:34.269 --> 00:12:34.279 align:start position:0% it so you'd want to like have always 00:12:34.279 --> 00:12:36.730 align:start position:0% it so you'd want to like have always have<00:12:34.610> a<00:12:34.639> very<00:12:34.970> large<00:12:35.240> number<00:12:35.930> of<00:12:36.170> participants 00:12:36.730 --> 00:12:36.740 align:start position:0% have a very large number of participants 00:12:36.740 --> 00:12:41.139 align:start position:0% have a very large number of participants and<00:12:38.500> another<00:12:39.500> design<00:12:40.129> constraint<00:12:40.550> we<00:12:40.699> had<00:12:40.910> is 00:12:41.139 --> 00:12:41.149 align:start position:0% and another design constraint we had is 00:12:41.149 --> 00:12:45.639 align:start position:0% and another design constraint we had is that<00:12:41.680> these<00:12:42.680> topics<00:12:43.959> kind<00:12:44.959> of<00:12:45.050> have<00:12:45.170> to<00:12:45.319> scale 00:12:45.639 --> 00:12:45.649 align:start position:0% that these topics kind of have to scale 00:12:45.649 --> 00:12:47.740 align:start position:0% that these topics kind of have to scale to<00:12:45.680> an<00:12:46.399> arbitrary<00:12:46.879> number<00:12:47.000> of<00:12:47.240> participants 00:12:47.740 --> 00:12:47.750 align:start position:0% to an arbitrary number of participants 00:12:47.750 --> 00:12:49.960 align:start position:0% to an arbitrary number of participants so<00:12:47.990> there<00:12:48.170> might<00:12:48.350> be<00:12:48.379> topics<00:12:48.949> that<00:12:49.370> everyone 00:12:49.960 --> 00:12:49.970 align:start position:0% so there might be topics that everyone 00:12:49.970 --> 00:12:52.780 align:start position:0% so there might be topics that everyone is<00:12:50.120> advertising<00:12:50.839> like<00:12:51.230> everyone<00:12:51.680> who's<00:12:52.009> in 00:12:52.780 --> 00:12:52.790 align:start position:0% is advertising like everyone who's in 00:12:52.790 --> 00:12:54.400 align:start position:0% is advertising like everyone who's in the<00:12:52.850> whole<00:12:52.970> network<00:12:53.149> but<00:12:53.990> then<00:12:54.139> on<00:12:54.259> the<00:12:54.350> other 00:12:54.400 --> 00:12:54.410 align:start position:0% the whole network but then on the other 00:12:54.410 --> 00:12:56.110 align:start position:0% the whole network but then on the other hand<00:12:54.740> there<00:12:54.889> might<00:12:54.980> also<00:12:55.189> be<00:12:55.309> topics<00:12:55.790> that<00:12:56.000> are 00:12:56.110 --> 00:12:56.120 align:start position:0% hand there might also be topics that are 00:12:56.120 --> 00:12:58.059 align:start position:0% hand there might also be topics that are very<00:12:56.329> small<00:12:56.629> and<00:12:56.899> only<00:12:57.050> advertised<00:12:57.649> by<00:12:57.889> let's 00:12:58.059 --> 00:12:58.069 align:start position:0% very small and only advertised by let's 00:12:58.069 --> 00:13:01.060 align:start position:0% very small and only advertised by let's say<00:12:58.220> five<00:12:58.519> or<00:12:58.550> six<00:12:58.910> different<00:12:59.449> nodes<00:12:59.870> and 00:13:01.060 --> 00:13:01.070 align:start position:0% say five or six different nodes and 00:13:01.070 --> 00:13:03.460 align:start position:0% say five or six different nodes and these<00:13:01.700> topics<00:13:02.690> shouldn't<00:13:02.960> really<00:13:03.110> compete 00:13:03.460 --> 00:13:03.470 align:start position:0% these topics shouldn't really compete 00:13:03.470 --> 00:13:05.080 align:start position:0% these topics shouldn't really compete with<00:13:03.620> each<00:13:03.770> other<00:13:03.890> so<00:13:04.220> you<00:13:04.400> should<00:13:04.670> be<00:13:04.820> able<00:13:04.940> to 00:13:05.080 --> 00:13:05.090 align:start position:0% with each other so you should be able to 00:13:05.090 --> 00:13:08.470 align:start position:0% with each other so you should be able to resolve<00:13:05.540> both<00:13:05.750> equally<00:13:06.650> quickly<00:13:07.100> and<00:13:07.910> then 00:13:08.470 --> 00:13:08.480 align:start position:0% resolve both equally quickly and then 00:13:08.480 --> 00:13:12.190 align:start position:0% resolve both equally quickly and then finally<00:13:10.180> with<00:13:11.180> all<00:13:11.210> of<00:13:11.450> these<00:13:11.540> systems<00:13:11.990> there 00:13:12.190 --> 00:13:12.200 align:start position:0% finally with all of these systems there 00:13:12.200 --> 00:13:13.830 align:start position:0% finally with all of these systems there is<00:13:12.290> always<00:13:12.590> like<00:13:12.800> the<00:13:12.980> danger<00:13:13.310> of<00:13:13.400> you<00:13:13.610> know 00:13:13.830 --> 00:13:13.840 align:start position:0% is always like the danger of you know 00:13:13.840 --> 00:13:17.080 align:start position:0% is always like the danger of you know people<00:13:14.840> spamming<00:13:15.140> it<00:13:15.440> with<00:13:15.680> like<00:13:16.090> arbitrary 00:13:17.080 --> 00:13:17.090 align:start position:0% people spamming it with like arbitrary 00:13:17.090 --> 00:13:18.880 align:start position:0% people spamming it with like arbitrary registrations<00:13:17.780> that<00:13:17.840> nobody<00:13:18.320> ever<00:13:18.590> cares 00:13:18.880 --> 00:13:18.890 align:start position:0% registrations that nobody ever cares 00:13:18.890 --> 00:13:22.270 align:start position:0% registrations that nobody ever cares about<00:13:19.190> and<00:13:19.960> those<00:13:20.960> particular<00:13:21.650> registrations 00:13:22.270 --> 00:13:22.280 align:start position:0% about and those particular registrations 00:13:22.280 --> 00:13:24.010 align:start position:0% about and those particular registrations should<00:13:22.490> not<00:13:22.670> drown<00:13:22.970> out<00:13:23.180> you<00:13:23.390> know<00:13:23.510> the<00:13:23.690> actual 00:13:24.010 --> 00:13:24.020 align:start position:0% should not drown out you know the actual 00:13:24.020 --> 00:13:26.520 align:start position:0% should not drown out you know the actual useful<00:13:24.470> ones<00:13:24.680> that<00:13:24.890> you<00:13:25.010> really<00:13:25.040> want<00:13:25.430> to<00:13:25.580> see 00:13:26.520 --> 00:13:26.530 align:start position:0% useful ones that you really want to see 00:13:26.530 --> 00:13:31.060 align:start position:0% useful ones that you really want to see and<00:13:27.700> to<00:13:28.700> combat<00:13:29.090> many<00:13:29.480> of<00:13:29.630> these<00:13:29.750> attacks<00:13:30.070> the 00:13:31.060 --> 00:13:31.070 align:start position:0% and to combat many of these attacks the 00:13:31.070 --> 00:13:33.850 align:start position:0% and to combat many of these attacks the topic<00:13:32.060> advertisement<00:13:32.720> protocol<00:13:33.200> includes 00:13:33.850 --> 00:13:33.860 align:start position:0% topic advertisement protocol includes 00:13:33.860 --> 00:13:35.860 align:start position:0% topic advertisement protocol includes this<00:13:34.460> thing<00:13:34.700> called<00:13:34.910> advertisement<00:13:35.630> inertia 00:13:35.860 --> 00:13:35.870 align:start position:0% this thing called advertisement inertia 00:13:35.870 --> 00:13:38.620 align:start position:0% this thing called advertisement inertia so<00:13:36.830> this<00:13:37.310> is<00:13:37.460> really<00:13:37.760> just<00:13:37.790> you<00:13:38.210> know<00:13:38.390> an 00:13:38.620 --> 00:13:38.630 align:start position:0% so this is really just you know an 00:13:38.630 --> 00:13:40.690 align:start position:0% so this is really just you know an artificial<00:13:39.470> delay<00:13:39.830> enforced<00:13:40.550> by<00:13:40.670> the 00:13:40.690 --> 00:13:40.700 align:start position:0% artificial delay enforced by the 00:13:40.700 --> 00:13:43.180 align:start position:0% artificial delay enforced by the protocol<00:13:41.270> before<00:13:41.450> a<00:13:41.900> certain<00:13:42.440> registration 00:13:43.180 --> 00:13:43.190 align:start position:0% protocol before a certain registration 00:13:43.190 --> 00:13:47.230 align:start position:0% protocol before a certain registration for<00:13:43.400> topic<00:13:43.790> and<00:13:43.970> go<00:13:44.090> live<00:13:44.300> and<00:13:45.760> we<00:13:46.760> feel<00:13:47.030> that 00:13:47.230 --> 00:13:47.240 align:start position:0% for topic and go live and we feel that 00:13:47.240 --> 00:13:49.810 align:start position:0% for topic and go live and we feel that you<00:13:47.390> know<00:13:47.540> in<00:13:47.990> addition<00:13:48.380> to<00:13:48.590> maybe<00:13:49.160> reducing 00:13:49.810 --> 00:13:49.820 align:start position:0% you know in addition to maybe reducing 00:13:49.820 --> 00:13:52.270 align:start position:0% you know in addition to maybe reducing misuse<00:13:50.210> of<00:13:50.450> this<00:13:50.630> in<00:13:51.440> addition<00:13:51.680> to<00:13:51.980> you<00:13:52.160> know 00:13:52.270 --> 00:13:52.280 align:start position:0% misuse of this in addition to you know 00:13:52.280 --> 00:13:54.100 align:start position:0% misuse of this in addition to you know combating<00:13:52.790> these<00:13:52.910> attacks<00:13:53.330> this<00:13:53.840> also 00:13:54.100 --> 00:13:54.110 align:start position:0% combating these attacks this also 00:13:54.110 --> 00:13:57.820 align:start position:0% combating these attacks this also reduces<00:13:54.350> the<00:13:55.210> misuse<00:13:56.210> of<00:13:56.450> the<00:13:57.050> topic<00:13:57.410> index 00:13:57.820 --> 00:13:57.830 align:start position:0% reduces the misuse of the topic index 00:13:57.830 --> 00:14:00.850 align:start position:0% reduces the misuse of the topic index because<00:13:58.640> fundamentally<00:13:59.500> topics<00:14:00.500> are<00:14:00.680> meant 00:14:00.850 --> 00:14:00.860 align:start position:0% because fundamentally topics are meant 00:14:00.860 --> 00:14:02.800 align:start position:0% because fundamentally topics are meant to<00:14:00.920> be<00:14:01.100> used<00:14:01.340> for<00:14:01.550> announcing<00:14:02.060> big<00:14:02.300> decisions 00:14:02.800 --> 00:14:02.810 align:start position:0% to be used for announcing big decisions 00:14:02.810 --> 00:14:04.810 align:start position:0% to be used for announcing big decisions like<00:14:03.080> way<00:14:03.260> ahead<00:14:03.410> of<00:14:03.560> time<00:14:03.680> and<00:14:04.100> those<00:14:04.610> big 00:14:04.810 --> 00:14:04.820 align:start position:0% like way ahead of time and those big 00:14:04.820 --> 00:14:07.570 align:start position:0% like way ahead of time and those big decisions<00:14:04.940> can<00:14:05.510> be<00:14:05.540> something<00:14:06.020> like<00:14:06.580> which 00:14:07.570 --> 00:14:07.580 align:start position:0% decisions can be something like which 00:14:07.580 --> 00:14:09.880 align:start position:0% decisions can be something like which blockchain<00:14:08.060> you're<00:14:08.240> on<00:14:08.390> were<00:14:08.840> which<00:14:09.380> short<00:14:09.740> of 00:14:09.880 --> 00:14:09.890 align:start position:0% blockchain you're on were which short of 00:14:09.890 --> 00:14:12.520 align:start position:0% blockchain you're on were which short of the<00:14:10.010> blockchain<00:14:10.220> you're<00:14:10.610> on<00:14:10.760> or<00:14:11.260> well<00:14:12.260> you 00:14:12.520 --> 00:14:12.530 align:start position:0% the blockchain you're on or well you 00:14:12.530 --> 00:14:14.500 align:start position:0% the blockchain you're on or well you know<00:14:12.830> things<00:14:13.100> like<00:14:13.250> that<00:14:13.310> and<00:14:13.880> not<00:14:14.090> so<00:14:14.270> much 00:14:14.500 --> 00:14:14.510 align:start position:0% know things like that and not so much 00:14:14.510 --> 00:14:17.500 align:start position:0% know things like that and not so much like<00:14:15.080> let's<00:14:15.440> say<00:14:15.650> the<00:14:16.160> URL<00:14:16.580> of<00:14:16.790> the<00:14:16.970> video<00:14:17.090> chat 00:14:17.500 --> 00:14:17.510 align:start position:0% like let's say the URL of the video chat 00:14:17.510 --> 00:14:19.660 align:start position:0% like let's say the URL of the video chat that<00:14:17.720> you<00:14:17.870> know<00:14:18.050> you're<00:14:18.770> just<00:14:18.800> starting<00:14:19.160> so 00:14:19.660 --> 00:14:19.670 align:start position:0% that you know you're just starting so 00:14:19.670 --> 00:14:22.810 align:start position:0% that you know you're just starting so there's<00:14:19.940> a<00:14:20.800> we<00:14:21.800> really<00:14:21.950> want<00:14:22.280> those<00:14:22.400> things<00:14:22.610> to 00:14:22.810 --> 00:14:22.820 align:start position:0% there's a we really want those things to 00:14:22.820 --> 00:14:25.180 align:start position:0% there's a we really want those things to be<00:14:22.940> used<00:14:23.120> you<00:14:23.240> know<00:14:23.420> like<00:14:23.630> four<00:14:23.900> four<00:14:24.770> four 00:14:25.180 --> 00:14:25.190 align:start position:0% be used you know like four four four 00:14:25.190 --> 00:14:34.420 align:start position:0% be used you know like four four four four<00:14:25.630> facts<00:14:26.630> that<00:14:30.790> so<00:14:31.790> to<00:14:32.780> recap<00:14:33.140> the<00:14:34.040> no 00:14:34.420 --> 00:14:34.430 align:start position:0% four facts that so to recap the no 00:14:34.430 --> 00:14:36.880 align:start position:0% four facts that so to recap the no discovery<00:14:34.790> version<00:14:35.120> five<00:14:35.480> is<00:14:35.750> about<00:14:36.170> finding 00:14:36.880 --> 00:14:36.890 align:start position:0% discovery version five is about finding 00:14:36.890 --> 00:14:38.800 align:start position:0% discovery version five is about finding notes<00:14:37.040> more<00:14:37.370> efficiently<00:14:37.850> and<00:14:38.030> knowing<00:14:38.330> more 00:14:38.800 --> 00:14:38.810 align:start position:0% notes more efficiently and knowing more 00:14:38.810 --> 00:14:40.860 align:start position:0% notes more efficiently and knowing more about<00:14:38.870> those<00:14:39.200> notes<00:14:39.440> before<00:14:39.800> we<00:14:39.920> connect<00:14:40.280> a 00:14:40.860 --> 00:14:40.870 align:start position:0% about those notes before we connect a 00:14:40.870 --> 00:14:43.360 align:start position:0% about those notes before we connect a prototype<00:14:41.870> of<00:14:41.900> the<00:14:42.170> system<00:14:42.620> although<00:14:43.010> without 00:14:43.360 --> 00:14:43.370 align:start position:0% prototype of the system although without 00:14:43.370 --> 00:14:45.820 align:start position:0% prototype of the system although without the<00:14:43.790> ENR<00:14:44.210> has<00:14:44.780> been<00:14:45.050> in<00:14:45.200> use<00:14:45.350> by<00:14:45.530> The<00:14:45.590> Gaslight 00:14:45.820 --> 00:14:45.830 align:start position:0% the ENR has been in use by The Gaslight 00:14:45.830 --> 00:14:50.620 align:start position:0% the ENR has been in use by The Gaslight client<00:14:46.490> since<00:14:46.700> early<00:14:47.090> 2017<00:14:49.390> we're<00:14:50.390> still 00:14:50.620 --> 00:14:50.630 align:start position:0% client since early 2017 we're still 00:14:50.630 --> 00:14:52.660 align:start position:0% client since early 2017 we're still working<00:14:51.020> on<00:14:51.170> the<00:14:51.260> e<00:14:51.290> IPS<00:14:51.740> so<00:14:52.160> nothing<00:14:52.520> is 00:14:52.660 --> 00:14:52.670 align:start position:0% working on the e IPS so nothing is 00:14:52.670 --> 00:14:55.660 align:start position:0% working on the e IPS so nothing is published<00:14:53.060> yet<00:14:53.300> but<00:14:53.800> once<00:14:54.800> it<00:14:54.950> is<00:14:54.980> we<00:14:55.520> will 00:14:55.660 --> 00:14:55.670 align:start position:0% published yet but once it is we will 00:14:55.670 --> 00:14:58.870 align:start position:0% published yet but once it is we will have<00:14:55.820> like<00:14:56.150> a<00:14:56.510> separate<00:14:57.080> spec<00:14:57.350> for<00:14:57.620> ian's<00:14:57.860> or<00:14:58.010> a 00:14:58.870 --> 00:14:58.880 align:start position:0% have like a separate spec for ian's or a 00:14:58.880 --> 00:15:01.060 align:start position:0% have like a separate spec for ian's or a document<00:14:59.480> that<00:14:59.600> goes<00:14:59.930> into<00:15:00.110> detail<00:15:00.560> about<00:15:00.590> you 00:15:01.060 --> 00:15:01.070 align:start position:0% document that goes into detail about you 00:15:01.070 --> 00:15:03.040 align:start position:0% document that goes into detail about you know<00:15:01.190> like<00:15:01.490> the<00:15:01.610> semantics<00:15:02.120> of<00:15:02.270> the<00:15:02.480> topic 00:15:03.040 --> 00:15:03.050 align:start position:0% know like the semantics of the topic 00:15:03.050 --> 00:15:05.800 align:start position:0% know like the semantics of the topic advertisement<00:15:03.620> protocol<00:15:04.070> and<00:15:04.280> finally<00:15:04.940> a 00:15:05.800 --> 00:15:05.810 align:start position:0% advertisement protocol and finally a 00:15:05.810 --> 00:15:07.960 align:start position:0% advertisement protocol and finally a description<00:15:06.410> of<00:15:06.680> the<00:15:06.860> actual<00:15:07.250> wire<00:15:07.460> protocol 00:15:07.960 --> 00:15:07.970 align:start position:0% description of the actual wire protocol 00:15:07.970 --> 00:15:09.210 align:start position:0% description of the actual wire protocol that<00:15:08.150> spoken 00:15:09.210 --> 00:15:09.220 align:start position:0% that spoken 00:15:09.220 --> 00:15:12.330 align:start position:0% that spoken via<00:15:09.430> UDP<00:15:10.050> but<00:15:11.050> there<00:15:11.230> is<00:15:11.350> really<00:15:11.560> nothing<00:15:11.950> set 00:15:12.330 --> 00:15:12.340 align:start position:0% via UDP but there is really nothing set 00:15:12.340 --> 00:15:14.490 align:start position:0% via UDP but there is really nothing set in<00:15:12.370> stone<00:15:12.610> yet<00:15:12.790> so<00:15:13.090> if<00:15:13.750> you<00:15:13.960> feel<00:15:14.170> like<00:15:14.380> you 00:15:14.490 --> 00:15:14.500 align:start position:0% in stone yet so if you feel like you 00:15:14.500 --> 00:15:15.840 align:start position:0% in stone yet so if you feel like you know<00:15:14.650> there<00:15:14.860> is<00:15:14.950> a<00:15:14.980> certain<00:15:15.340> change<00:15:15.580> that 00:15:15.840 --> 00:15:15.850 align:start position:0% know there is a certain change that 00:15:15.850 --> 00:15:18.210 align:start position:0% know there is a certain change that absolutely<00:15:16.600> has<00:15:16.810> to<00:15:16.840> be<00:15:17.020> made<00:15:17.320> or<00:15:17.740> a<00:15:17.800> certain 00:15:18.210 --> 00:15:18.220 align:start position:0% absolutely has to be made or a certain 00:15:18.220 --> 00:15:20.220 align:start position:0% absolutely has to be made or a certain feature<00:15:18.370> there<00:15:18.670> to<00:15:18.790> really<00:15:19.060> be<00:15:19.180> included<00:15:19.690> were 00:15:20.220 --> 00:15:20.230 align:start position:0% feature there to really be included were 00:15:20.230 --> 00:15:27.540 align:start position:0% feature there to really be included were not<00:15:20.470> included<00:15:20.980> just<00:15:21.220> come<00:15:21.430> talk<00:15:21.670> to<00:15:21.700> us 00:15:27.540 --> 00:15:27.550 align:start position:0% 00:15:27.550 --> 00:15:36.070 align:start position:0% [Applause] 00:15:36.070 --> 00:15:36.080 align:start position:0% 00:15:36.080 --> 00:15:43.570 align:start position:0% [Music]