WEBVTT Kind: captions Language: en 00:00:04.450 --> 00:00:07.690 align:start position:0% good<00:00:05.450> morning<00:00:05.750> my<00:00:06.290> name<00:00:06.470> is<00:00:06.500> a<00:00:06.740> hiker<00:00:07.220> drop<00:00:07.519> I 00:00:07.690 --> 00:00:07.700 align:start position:0% good morning my name is a hiker drop I 00:00:07.700 --> 00:00:10.360 align:start position:0% good morning my name is a hiker drop I work<00:00:07.910> at<00:00:08.090> status<00:00:08.570> on<00:00:08.809> Nimbus<00:00:09.260> which<00:00:10.190> is<00:00:10.340> a 00:00:10.360 --> 00:00:10.370 align:start position:0% work at status on Nimbus which is a 00:00:10.370 --> 00:00:13.539 align:start position:0% work at status on Nimbus which is a client<00:00:11.120> for<00:00:11.360> eat<00:00:12.320> theorem<00:00:12.740> 1<00:00:12.920> and<00:00:13.190> helium<00:00:13.340> 2 00:00:13.539 --> 00:00:13.549 align:start position:0% client for eat theorem 1 and helium 2 00:00:13.549 --> 00:00:15.820 align:start position:0% client for eat theorem 1 and helium 2 client<00:00:13.940> forestry<00:00:14.480> resources<00:00:15.290> take<00:00:15.710> the 00:00:15.820 --> 00:00:15.830 align:start position:0% client forestry resources take the 00:00:15.830 --> 00:00:19.720 align:start position:0% client forestry resources take the devices<00:00:16.790> written<00:00:17.180> in<00:00:17.300> me<00:00:18.040> and<00:00:19.040> today<00:00:19.460> we<00:00:19.669> will 00:00:19.720 --> 00:00:19.730 align:start position:0% devices written in me and today we will 00:00:19.730 --> 00:00:21.819 align:start position:0% devices written in me and today we will be<00:00:19.880> talking<00:00:20.029> about<00:00:20.210> the<00:00:20.930> etherium<00:00:21.290> networking 00:00:21.819 --> 00:00:21.829 align:start position:0% be talking about the etherium networking 00:00:21.829 --> 00:00:25.780 align:start position:0% be talking about the etherium networking spec<00:00:22.160> how<00:00:22.820> it<00:00:23.239> evolved<00:00:23.779> and<00:00:24.130> what<00:00:25.130> was<00:00:25.369> the 00:00:25.780 --> 00:00:25.790 align:start position:0% spec how it evolved and what was the 00:00:25.790 --> 00:00:27.909 align:start position:0% spec how it evolved and what was the various<00:00:26.149> design<00:00:26.660> rationales<00:00:27.169> that<00:00:27.290> I<00:00:27.410> went<00:00:27.770> to 00:00:27.909 --> 00:00:27.919 align:start position:0% various design rationales that I went to 00:00:27.919 --> 00:00:32.770 align:start position:0% various design rationales that I went to into<00:00:28.189> it<00:00:29.619> so<00:00:30.619> the<00:00:31.130> person<00:00:31.939> the<00:00:32.570> major 00:00:32.770 --> 00:00:32.780 align:start position:0% into it so the person the major 00:00:32.780 --> 00:00:34.870 align:start position:0% into it so the person the major difference<00:00:33.380> between<00:00:33.410> a<00:00:33.950> theorem<00:00:34.250> 1<00:00:34.399> and<00:00:34.760> a 00:00:34.870 --> 00:00:34.880 align:start position:0% difference between a theorem 1 and a 00:00:34.880 --> 00:00:36.759 align:start position:0% difference between a theorem 1 and a theorem<00:00:35.180> 2<00:00:35.390> is<00:00:35.540> that<00:00:35.660> we<00:00:36.079> are<00:00:36.200> transitioning 00:00:36.759 --> 00:00:36.769 align:start position:0% theorem 2 is that we are transitioning 00:00:36.769 --> 00:00:40.060 align:start position:0% theorem 2 is that we are transitioning to<00:00:36.829> the<00:00:37.399> p2p<00:00:37.750> which<00:00:38.750> is<00:00:38.870> a<00:00:38.899> protocol<00:00:39.500> developed 00:00:40.060 --> 00:00:40.070 align:start position:0% to the p2p which is a protocol developed 00:00:40.070 --> 00:00:43.200 align:start position:0% to the p2p which is a protocol developed by<00:00:40.510> protocol<00:00:41.510> labs<00:00:41.780> for<00:00:42.109> the<00:00:42.170> purposes<00:00:42.679> of 00:00:43.200 --> 00:00:43.210 align:start position:0% by protocol labs for the purposes of 00:00:43.210 --> 00:00:46.000 align:start position:0% by protocol labs for the purposes of developing<00:00:44.210> ipfs<00:00:44.839> it<00:00:45.140> might<00:00:45.469> short<00:00:45.710> out<00:00:45.890> of 00:00:46.000 --> 00:00:46.010 align:start position:0% developing ipfs it might short out of 00:00:46.010 --> 00:00:50.529 align:start position:0% developing ipfs it might short out of this<00:00:46.219> project<00:00:46.899> and<00:00:47.899> I<00:00:49.359> figured<00:00:50.359> I<00:00:50.449> should 00:00:50.529 --> 00:00:50.539 align:start position:0% this project and I figured I should 00:00:50.539 --> 00:00:53.619 align:start position:0% this project and I figured I should start<00:00:50.960> with<00:00:51.109> few<00:00:51.320> words<00:00:51.350> why<00:00:52.120> this<00:00:53.120> transition 00:00:53.619 --> 00:00:53.629 align:start position:0% start with few words why this transition 00:00:53.629 --> 00:00:55.840 align:start position:0% start with few words why this transition was<00:00:53.780> made<00:00:53.809> and<00:00:54.260> why<00:00:54.800> we<00:00:55.010> decided<00:00:55.129> to<00:00:55.609> move<00:00:55.789> to 00:00:55.840 --> 00:00:55.850 align:start position:0% was made and why we decided to move to 00:00:55.850 --> 00:00:59.309 align:start position:0% was made and why we decided to move to the<00:00:55.999> p2p<00:00:56.800> and<00:00:57.800> there<00:00:58.069> are<00:00:58.249> I<00:00:58.519> would<00:00:58.819> say<00:00:58.999> two 00:00:59.309 --> 00:00:59.319 align:start position:0% the p2p and there are I would say two 00:00:59.319 --> 00:01:02.380 align:start position:0% the p2p and there are I would say two major<00:01:00.319> reasons<00:01:00.649> not<00:01:01.339> to<00:01:01.399> most<00:01:01.850> important 00:01:02.380 --> 00:01:02.390 align:start position:0% major reasons not to most important 00:01:02.390 --> 00:01:05.439 align:start position:0% major reasons not to most important promises<00:01:03.170> a<00:01:03.379> flea<00:01:03.559> p2p<00:01:03.979> and<00:01:04.220> the<00:01:04.879> first<00:01:05.120> one<00:01:05.300> is 00:01:05.439 --> 00:01:05.449 align:start position:0% promises a flea p2p and the first one is 00:01:05.449 --> 00:01:08.200 align:start position:0% promises a flea p2p and the first one is that<00:01:05.479> it<00:01:06.260> promises<00:01:06.860> to<00:01:07.130> take<00:01:07.370> a<00:01:07.670> theorem<00:01:08.000> to 00:01:08.200 --> 00:01:08.210 align:start position:0% that it promises to take a theorem to 00:01:08.210 --> 00:01:10.690 align:start position:0% that it promises to take a theorem to many<00:01:08.630> new<00:01:08.840> places<00:01:09.110> where<00:01:09.860> it<00:01:10.130> wasn't<00:01:10.370> quite 00:01:10.690 --> 00:01:10.700 align:start position:0% many new places where it wasn't quite 00:01:10.700 --> 00:01:14.320 align:start position:0% many new places where it wasn't quite possible<00:01:11.240> to<00:01:11.420> use<00:01:11.570> it<00:01:11.720> before<00:01:12.970> and<00:01:13.970> the<00:01:14.090> reason 00:01:14.320 --> 00:01:14.330 align:start position:0% possible to use it before and the reason 00:01:14.330 --> 00:01:15.490 align:start position:0% possible to use it before and the reason this<00:01:14.420> is<00:01:14.540> possible<00:01:14.600> because<00:01:15.110> all 00:01:15.490 --> 00:01:15.500 align:start position:0% this is possible because all 00:01:15.500 --> 00:01:18.550 align:start position:0% this is possible because all communication<00:01:16.160> in<00:01:16.340> the<00:01:16.580> p2p<00:01:16.850> is<00:01:17.350> carried<00:01:18.350> all 00:01:18.550 --> 00:01:18.560 align:start position:0% communication in the p2p is carried all 00:01:18.560 --> 00:01:21.790 align:start position:0% communication in the p2p is carried all over<00:01:18.800> this<00:01:19.600> so-called<00:01:20.600> the<00:01:20.990> p2p<00:01:21.290> streams 00:01:21.790 --> 00:01:21.800 align:start position:0% over this so-called the p2p streams 00:01:21.800 --> 00:01:25.840 align:start position:0% over this so-called the p2p streams which<00:01:22.640> in<00:01:22.850> turns<00:01:23.090> are<00:01:23.450> layered<00:01:24.020> over<00:01:24.850> let's 00:01:25.840 --> 00:01:25.850 align:start position:0% which in turns are layered over let's 00:01:25.850 --> 00:01:27.790 align:start position:0% which in turns are layered over let's call<00:01:26.060> them<00:01:26.180> physical<00:01:26.660> connections<00:01:27.170> which 00:01:27.790 --> 00:01:27.800 align:start position:0% call them physical connections which 00:01:27.800 --> 00:01:30.430 align:start position:0% call them physical connections which could<00:01:28.070> be<00:01:28.310> an<00:01:28.670> arbitrary<00:01:29.440> network 00:01:30.430 --> 00:01:30.440 align:start position:0% could be an arbitrary network 00:01:30.440 --> 00:01:31.960 align:start position:0% could be an arbitrary network connections<00:01:30.890> that<00:01:31.040> establish<00:01:31.550> between<00:01:31.700> two 00:01:31.960 --> 00:01:31.970 align:start position:0% connections that establish between two 00:01:31.970 --> 00:01:33.910 align:start position:0% connections that establish between two nodes<00:01:32.180> it<00:01:32.330> could<00:01:32.510> be<00:01:32.600> a<00:01:32.630> TCP<00:01:33.050> link<00:01:33.290> in<00:01:33.800> a 00:01:33.910 --> 00:01:33.920 align:start position:0% nodes it could be a TCP link in a 00:01:33.920 --> 00:01:36.940 align:start position:0% nodes it could be a TCP link in a classical<00:01:34.310> case<00:01:34.460> it<00:01:34.730> could<00:01:34.940> be<00:01:35.590> some<00:01:36.590> UDP 00:01:36.940 --> 00:01:36.950 align:start position:0% classical case it could be some UDP 00:01:36.950 --> 00:01:39.600 align:start position:0% classical case it could be some UDP scheme<00:01:37.220> like<00:01:37.460> quick<00:01:37.910> which<00:01:38.480> will<00:01:39.110> give<00:01:39.320> us 00:01:39.600 --> 00:01:39.610 align:start position:0% scheme like quick which will give us 00:01:39.610 --> 00:01:41.980 align:start position:0% scheme like quick which will give us very<00:01:40.610> good<00:01:40.730> censorship<00:01:41.360> resistant<00:01:41.810> in<00:01:41.900> the 00:01:41.980 --> 00:01:41.990 align:start position:0% very good censorship resistant in the 00:01:41.990 --> 00:01:45.100 align:start position:0% very good censorship resistant in the future<00:01:42.290> it<00:01:42.800> could<00:01:43.100> be<00:01:43.310> the<00:01:44.090> WebSockets<00:01:44.660> in<00:01:45.020> the 00:01:45.100 --> 00:01:45.110 align:start position:0% future it could be the WebSockets in the 00:01:45.110 --> 00:01:46.360 align:start position:0% future it could be the WebSockets in the browser 00:01:46.360 --> 00:01:46.370 align:start position:0% browser 00:01:46.370 --> 00:01:49.390 align:start position:0% browser it<00:01:47.240> could<00:01:47.510> even<00:01:47.690> be<00:01:47.840> snail<00:01:48.200> mail<00:01:48.470> let's<00:01:49.190> don't 00:01:49.390 --> 00:01:49.400 align:start position:0% it could even be snail mail let's don't 00:01:49.400 --> 00:01:51.280 align:start position:0% it could even be snail mail let's don't forget<00:01:49.460> the<00:01:49.790> that<00:01:50.210> protocol<00:01:50.660> loves<00:01:50.930> the 00:01:51.280 --> 00:01:51.290 align:start position:0% forget the that protocol loves the 00:01:51.290 --> 00:01:53.230 align:start position:0% forget the that protocol loves the people<00:01:51.410> who<00:01:51.620> created<00:01:51.890> the<00:01:52.010> p2p<00:01:52.310> they<00:01:52.850> want<00:01:53.060> the 00:01:53.230 --> 00:01:53.240 align:start position:0% people who created the p2p they want the 00:01:53.240 --> 00:01:59.440 align:start position:0% people who created the p2p they want the system<00:01:53.510> that<00:01:53.630> would<00:01:53.780> work<00:01:53.960> on<00:01:54.170> Mars<00:01:56.440> so<00:01:58.420> one<00:01:59.420> of 00:01:59.440 --> 00:01:59.450 align:start position:0% system that would work on Mars so one of 00:01:59.450 --> 00:02:01.420 align:start position:0% system that would work on Mars so one of the<00:01:59.750> key<00:02:00.290> features<00:02:00.470> of<00:02:00.650> Lippett<00:02:01.010> appears<00:02:01.280> that 00:02:01.420 --> 00:02:01.430 align:start position:0% the key features of Lippett appears that 00:02:01.430 --> 00:02:04.030 align:start position:0% the key features of Lippett appears that it's<00:02:02.090> not<00:02:02.300> only<00:02:02.480> option<00:02:02.930> allowing<00:02:03.890> these 00:02:04.030 --> 00:02:04.040 align:start position:0% it's not only option allowing these 00:02:04.040 --> 00:02:05.890 align:start position:0% it's not only option allowing these streams<00:02:04.460> to<00:02:04.640> be<00:02:04.700> multiplexed<00:02:05.240> over<00:02:05.630> a<00:02:05.660> single 00:02:05.890 --> 00:02:05.900 align:start position:0% streams to be multiplexed over a single 00:02:05.900 --> 00:02:08.199 align:start position:0% streams to be multiplexed over a single connection<00:02:06.050> but<00:02:06.590> a<00:02:06.980> node<00:02:07.580> in<00:02:07.790> the<00:02:07.880> network<00:02:07.910> can 00:02:08.199 --> 00:02:08.209 align:start position:0% connection but a node in the network can 00:02:08.209 --> 00:02:10.660 align:start position:0% connection but a node in the network can relay<00:02:08.750> the<00:02:09.229> connections<00:02:09.679> for<00:02:09.979> other<00:02:10.310> nodes 00:02:10.660 --> 00:02:10.670 align:start position:0% relay the connections for other nodes 00:02:10.670 --> 00:02:13.750 align:start position:0% relay the connections for other nodes and<00:02:11.080> a<00:02:12.080> single<00:02:12.650> physical<00:02:12.799> link<00:02:13.219> can<00:02:13.519> carry 00:02:13.750 --> 00:02:13.760 align:start position:0% and a single physical link can carry 00:02:13.760 --> 00:02:15.819 align:start position:0% and a single physical link can carry many<00:02:14.030> logical<00:02:14.480> link<00:02:14.870> between<00:02:15.140> arbitrary 00:02:15.819 --> 00:02:15.829 align:start position:0% many logical link between arbitrary 00:02:15.829 --> 00:02:17.290 align:start position:0% many logical link between arbitrary nodes<00:02:16.129> and<00:02:16.370> we<00:02:17.060> call 00:02:17.290 --> 00:02:17.300 align:start position:0% nodes and we call 00:02:17.300 --> 00:02:20.680 align:start position:0% nodes and we call this<00:02:17.920> multi<00:02:18.920> multiplexing<00:02:19.610> in<00:02:20.060> the<00:02:20.240> lipid 00:02:20.680 --> 00:02:20.690 align:start position:0% this multi multiplexing in the lipid 00:02:20.690 --> 00:02:23.950 align:start position:0% this multi multiplexing in the lipid Opie<00:02:21.160> sense<00:02:22.160> and<00:02:22.550> it's<00:02:22.850> easy<00:02:23.180> with<00:02:23.480> the<00:02:23.570> manger 00:02:23.950 --> 00:02:23.960 align:start position:0% Opie sense and it's easy with the manger 00:02:23.960 --> 00:02:29.230 align:start position:0% Opie sense and it's easy with the manger key<00:02:24.320> enabler<00:02:24.830> -<00:02:26.920> for<00:02:27.920> creating<00:02:28.280> things<00:02:28.730> like<00:02:29.000> a 00:02:29.230 --> 00:02:29.240 align:start position:0% key enabler - for creating things like a 00:02:29.240 --> 00:02:30.760 align:start position:0% key enabler - for creating things like a tea<00:02:29.360> room<00:02:29.630> light<00:02:29.810> clans<00:02:30.110> running<00:02:30.560> in<00:02:30.710> the 00:02:30.760 --> 00:02:30.770 align:start position:0% tea room light clans running in the 00:02:30.770 --> 00:02:36.010 align:start position:0% tea room light clans running in the browser<00:02:33.790> and<00:02:34.790> the<00:02:35.000> other<00:02:35.120> significant<00:02:35.720> reason 00:02:36.010 --> 00:02:36.020 align:start position:0% browser and the other significant reason 00:02:36.020 --> 00:02:40.180 align:start position:0% browser and the other significant reason is<00:02:36.340> gossip<00:02:37.340> sub<00:02:37.580> this<00:02:38.470> framework<00:02:39.470> in<00:02:39.830> the<00:02:39.950> p2p 00:02:40.180 --> 00:02:40.190 align:start position:0% is gossip sub this framework in the p2p 00:02:40.190 --> 00:02:43.480 align:start position:0% is gossip sub this framework in the p2p for<00:02:40.520> broadcasting<00:02:41.210> data<00:02:41.450> as<00:02:42.200> we<00:02:42.410> know<00:02:42.560> a<00:02:42.950> lot 00:02:43.480 --> 00:02:43.490 align:start position:0% for broadcasting data as we know a lot 00:02:43.490 --> 00:02:47.260 align:start position:0% for broadcasting data as we know a lot of<00:02:43.780> the<00:02:44.780> traffic<00:02:45.020> in<00:02:45.560> a<00:02:46.270> cryptocurrencies 00:02:47.260 --> 00:02:47.270 align:start position:0% of the traffic in a cryptocurrencies 00:02:47.270 --> 00:02:49.780 align:start position:0% of the traffic in a cryptocurrencies network<00:02:48.050> like<00:02:48.230> aetherium<00:02:48.680> it's<00:02:49.370> about 00:02:49.780 --> 00:02:49.790 align:start position:0% network like aetherium it's about 00:02:49.790 --> 00:02:53.380 align:start position:0% network like aetherium it's about broadcasting<00:02:51.010> blocks<00:02:52.010> and<00:02:52.430> now<00:02:53.120> with<00:02:53.300> the 00:02:53.380 --> 00:02:53.390 align:start position:0% broadcasting blocks and now with the 00:02:53.390 --> 00:02:55.630 align:start position:0% broadcasting blocks and now with the theorem<00:02:53.570> to<00:02:53.870> the<00:02:54.350> majority<00:02:54.620> of<00:02:54.800> traffic<00:02:55.370> is 00:02:55.630 --> 00:02:55.640 align:start position:0% theorem to the majority of traffic is 00:02:55.640 --> 00:02:57.460 align:start position:0% theorem to the majority of traffic is actually<00:02:55.850> broadcasting<00:02:56.570> the<00:02:56.690> ad<00:02:56.870> stations 00:02:57.460 --> 00:02:57.470 align:start position:0% actually broadcasting the ad stations 00:02:57.470 --> 00:02:59.770 align:start position:0% actually broadcasting the ad stations the<00:02:58.100> other<00:02:58.220> stations<00:02:58.700> are<00:02:58.940> the<00:02:59.210> votes<00:02:59.450> that 00:02:59.770 --> 00:02:59.780 align:start position:0% the other stations are the votes that 00:02:59.780 --> 00:03:03.390 align:start position:0% the other stations are the votes that the<00:03:00.710> participant<00:03:01.520> in<00:03:01.910> the<00:03:02.150> proof<00:03:02.450> of<00:03:02.600> stake 00:03:03.390 --> 00:03:03.400 align:start position:0% the participant in the proof of stake 00:03:03.400 --> 00:03:06.730 align:start position:0% the participant in the proof of stake consensus<00:03:04.750> exchange<00:03:05.750> with<00:03:05.930> which<00:03:06.230> is<00:03:06.440> each 00:03:06.730 --> 00:03:06.740 align:start position:0% consensus exchange with which is each 00:03:06.740 --> 00:03:09.040 align:start position:0% consensus exchange with which is each other<00:03:06.980> these<00:03:07.370> votes<00:03:07.730> allow<00:03:08.510> them<00:03:08.690> to<00:03:08.870> reach 00:03:09.040 --> 00:03:09.050 align:start position:0% other these votes allow them to reach 00:03:09.050 --> 00:03:11.710 align:start position:0% other these votes allow them to reach finality<00:03:09.440> and<00:03:09.890> to<00:03:10.130> cross<00:03:10.400> link<00:03:10.640> the<00:03:11.330> state<00:03:11.540> of 00:03:11.710 --> 00:03:11.720 align:start position:0% finality and to cross link the state of 00:03:11.720 --> 00:03:13.570 align:start position:0% finality and to cross link the state of all<00:03:11.960> the<00:03:12.020> various<00:03:12.350> charts<00:03:12.710> including<00:03:13.280> each 00:03:13.570 --> 00:03:13.580 align:start position:0% all the various charts including each 00:03:13.580 --> 00:03:18.310 align:start position:0% all the various charts including each one<00:03:14.650> so<00:03:15.650> we<00:03:16.400> know<00:03:16.550> that<00:03:17.060> from<00:03:17.420> experience<00:03:17.630> and 00:03:18.310 --> 00:03:18.320 align:start position:0% one so we know that from experience and 00:03:18.320 --> 00:03:22.080 align:start position:0% one so we know that from experience and from<00:03:18.470> just<00:03:19.010> theoretical<00:03:20.800> reasoning<00:03:21.800> that 00:03:22.080 --> 00:03:22.090 align:start position:0% from just theoretical reasoning that 00:03:22.090 --> 00:03:26.110 align:start position:0% from just theoretical reasoning that floods<00:03:23.090> up<00:03:23.330> the<00:03:23.480> system<00:03:23.750> where<00:03:24.280> every<00:03:25.280> message 00:03:26.110 --> 00:03:26.120 align:start position:0% floods up the system where every message 00:03:26.120 --> 00:03:27.880 align:start position:0% floods up the system where every message reaches<00:03:26.540> everybody<00:03:27.080> in<00:03:27.200> the<00:03:27.290> network<00:03:27.620> you<00:03:27.739> see 00:03:27.880 --> 00:03:27.890 align:start position:0% reaches everybody in the network you see 00:03:27.890 --> 00:03:30.790 align:start position:0% reaches everybody in the network you see and<00:03:28.130> it's<00:03:28.400> fully<00:03:28.700> broadcasted<00:03:29.420> on<00:03:30.200> every<00:03:30.560> step 00:03:30.790 --> 00:03:30.800 align:start position:0% and it's fully broadcasted on every step 00:03:30.800 --> 00:03:35.710 align:start position:0% and it's fully broadcasted on every step just<00:03:31.100> one<00:03:31.580> scale<00:03:32.120> to<00:03:32.390> the<00:03:34.090> scale<00:03:35.090> that<00:03:35.120> we<00:03:35.420> want 00:03:35.710 --> 00:03:35.720 align:start position:0% just one scale to the scale that we want 00:03:35.720 --> 00:03:42.880 align:start position:0% just one scale to the scale that we want to<00:03:35.810> reach<00:03:35.959> with<00:03:36.170> the<00:03:36.260> theorem<00:03:41.470> but<00:03:42.470> the<00:03:42.620> p2p 00:03:42.880 --> 00:03:42.890 align:start position:0% to reach with the theorem but the p2p 00:03:42.890 --> 00:03:47.320 align:start position:0% to reach with the theorem but the p2p comes<00:03:43.340> with<00:03:43.940> the<00:03:44.030> significant<00:03:44.570> cost<00:03:44.810> it<00:03:46.330> it 00:03:47.320 --> 00:03:47.330 align:start position:0% comes with the significant cost it it 00:03:47.330 --> 00:03:50.260 align:start position:0% comes with the significant cost it it took<00:03:47.570> quite<00:03:48.200> a<00:03:48.320> lot<00:03:48.530> of<00:03:48.970> convincing<00:03:49.970> for<00:03:50.180> the 00:03:50.260 --> 00:03:50.270 align:start position:0% took quite a lot of convincing for the 00:03:50.270 --> 00:03:55.210 align:start position:0% took quite a lot of convincing for the teams<00:03:50.510> to<00:03:51.400> jump<00:03:52.400> on<00:03:52.550> shame<00:03:52.760> because<00:03:54.100> when<00:03:55.100> you 00:03:55.210 --> 00:03:55.220 align:start position:0% teams to jump on shame because when you 00:03:55.220 --> 00:03:57.310 align:start position:0% teams to jump on shame because when you look<00:03:55.370> at<00:03:55.550> the<00:03:55.700> large<00:03:56.180> list<00:03:56.540> of<00:03:56.690> components 00:03:57.310 --> 00:03:57.320 align:start position:0% look at the large list of components 00:03:57.320 --> 00:03:58.960 align:start position:0% look at the large list of components that<00:03:57.350> you<00:03:57.680> have<00:03:57.860> to<00:03:57.980> implement<00:03:58.190> it<00:03:58.580> could<00:03:58.820> be<00:03:58.940> a 00:03:58.960 --> 00:03:58.970 align:start position:0% that you have to implement it could be a 00:03:58.970 --> 00:04:01.900 align:start position:0% that you have to implement it could be a little<00:03:59.090> bit<00:03:59.270> intimidating<00:04:00.520> the<00:04:01.520> reference 00:04:01.900 --> 00:04:01.910 align:start position:0% little bit intimidating the reference 00:04:01.910 --> 00:04:03.400 align:start position:0% little bit intimidating the reference code<00:04:02.150> written<00:04:02.450> in<00:04:02.690> go<00:04:02.900> is<00:04:03.140> spread<00:04:03.380> over 00:04:03.400 --> 00:04:03.410 align:start position:0% code written in go is spread over 00:04:03.410 --> 00:04:06.190 align:start position:0% code written in go is spread over multiple<00:04:04.010> repositories<00:04:04.580> and<00:04:05.180> it's<00:04:05.630> bit<00:04:05.840> hard 00:04:06.190 --> 00:04:06.200 align:start position:0% multiple repositories and it's bit hard 00:04:06.200 --> 00:04:12.130 align:start position:0% multiple repositories and it's bit hard to<00:04:06.610> make<00:04:07.610> sense<00:04:07.820> of<00:04:07.970> it<00:04:08.120> so<00:04:09.400> we<00:04:10.400> were<00:04:11.140> many 00:04:12.130 --> 00:04:12.140 align:start position:0% to make sense of it so we were many 00:04:12.140 --> 00:04:14.140 align:start position:0% to make sense of it so we were many teams<00:04:12.380> were<00:04:12.560> worried<00:04:13.010> whether<00:04:13.730> we'll<00:04:13.970> be<00:04:14.120> able 00:04:14.140 --> 00:04:14.150 align:start position:0% teams were worried whether we'll be able 00:04:14.150 --> 00:04:18.099 align:start position:0% teams were worried whether we'll be able to<00:04:14.330> make<00:04:14.510> it<00:04:14.660> on<00:04:14.810> time<00:04:14.840> but<00:04:15.680> luckily<00:04:17.109> the 00:04:18.099 --> 00:04:18.109 align:start position:0% to make it on time but luckily the 00:04:18.109 --> 00:04:19.870 align:start position:0% to make it on time but luckily the limitation<00:04:18.650> teams<00:04:18.890> have<00:04:19.100> rising<00:04:19.519> to<00:04:19.790> the 00:04:19.870 --> 00:04:19.880 align:start position:0% limitation teams have rising to the 00:04:19.880 --> 00:04:23.440 align:start position:0% limitation teams have rising to the challenge<00:04:20.209> and<00:04:20.450> we<00:04:21.160> now<00:04:22.160> have<00:04:22.460> the<00:04:23.210> p2p 00:04:23.440 --> 00:04:23.450 align:start position:0% challenge and we now have the p2p 00:04:23.450 --> 00:04:26.080 align:start position:0% challenge and we now have the p2p implementations<00:04:24.260> written<00:04:24.620> in<00:04:24.770> go<00:04:25.160> JavaScript 00:04:26.080 --> 00:04:26.090 align:start position:0% implementations written in go JavaScript 00:04:26.090 --> 00:04:30.010 align:start position:0% implementations written in go JavaScript Russ<00:04:26.539> Python<00:04:27.729> Java<00:04:28.729> in<00:04:29.150> him<00:04:29.390> and<00:04:29.600> I've<00:04:29.840> missed 00:04:30.010 --> 00:04:30.020 align:start position:0% Russ Python Java in him and I've missed 00:04:30.020 --> 00:04:30.980 align:start position:0% Russ Python Java in him and I've missed at<00:04:30.320> the 00:04:30.980 --> 00:04:30.990 align:start position:0% at the 00:04:30.990 --> 00:04:35.090 align:start position:0% at the C++<00:04:31.260> one<00:04:31.680> developed<00:04:33.140> so<00:04:34.140> far<00:04:34.320> not<00:04:34.500> for<00:04:34.710> helium 00:04:35.090 --> 00:04:35.100 align:start position:0% C++ one developed so far not for helium 00:04:35.100 --> 00:04:37.880 align:start position:0% C++ one developed so far not for helium two<00:04:35.250> purposes<00:04:35.580> but<00:04:35.880> it<00:04:36.540> exists<00:04:36.960> as<00:04:37.020> well<00:04:37.170> and<00:04:37.800> I 00:04:37.880 --> 00:04:37.890 align:start position:0% two purposes but it exists as well and I 00:04:37.890 --> 00:04:39.740 align:start position:0% two purposes but it exists as well and I should<00:04:38.070> mention<00:04:38.190> that<00:04:38.400> our<00:04:38.940> own<00:04:39.300> one<00:04:39.540> there's 00:04:39.740 --> 00:04:39.750 align:start position:0% should mention that our own one there's 00:04:39.750 --> 00:04:41.960 align:start position:0% should mention that our own one there's an<00:04:39.870> enum<00:04:40.200> it's<00:04:40.470> a<00:04:40.560> should<00:04:41.400> be<00:04:41.520> perfectly 00:04:41.960 --> 00:04:41.970 align:start position:0% an enum it's a should be perfectly 00:04:41.970 --> 00:04:44.000 align:start position:0% an enum it's a should be perfectly usable<00:04:42.240> and<00:04:42.630> seen<00:04:42.930> C++<00:04:43.380> projects<00:04:43.830> in<00:04:43.920> the 00:04:44.000 --> 00:04:44.010 align:start position:0% usable and seen C++ projects in the 00:04:44.010 --> 00:04:48.080 align:start position:0% usable and seen C++ projects in the future<00:04:45.830> and<00:04:46.830> what's<00:04:47.130> more<00:04:47.250> important<00:04:47.790> is<00:04:47.940> that 00:04:48.080 --> 00:04:48.090 align:start position:0% future and what's more important is that 00:04:48.090 --> 00:04:50.930 align:start position:0% future and what's more important is that during<00:04:48.570> all<00:04:49.020> this<00:04:49.950> implementation<00:04:50.430> are 00:04:50.930 --> 00:04:50.940 align:start position:0% during all this implementation are 00:04:50.940 --> 00:04:52.430 align:start position:0% during all this implementation are currently<00:04:51.360> at<00:04:51.480> the<00:04:51.510> stage<00:04:51.810> where<00:04:52.080> they<00:04:52.260> can 00:04:52.430 --> 00:04:52.440 align:start position:0% currently at the stage where they can 00:04:52.440 --> 00:04:54.650 align:start position:0% currently at the stage where they can talk<00:04:52.650> to<00:04:52.680> each<00:04:52.920> other<00:04:53.130> during<00:04:54.090> the<00:04:54.300> interrupt 00:04:54.650 --> 00:04:54.660 align:start position:0% talk to each other during the interrupt 00:04:54.660 --> 00:04:58.270 align:start position:0% talk to each other during the interrupt walking<00:04:55.140> we<00:04:55.680> demonstrated<00:04:56.490> networks<00:04:56.910> where 00:04:58.270 --> 00:04:58.280 align:start position:0% walking we demonstrated networks where 00:04:58.280 --> 00:05:01.160 align:start position:0% walking we demonstrated networks where all<00:04:59.280> these<00:04:59.580> clients<00:04:59.760> were<00:05:00.060> able<00:05:00.480> to<00:05:00.510> reach 00:05:01.160 --> 00:05:01.170 align:start position:0% all these clients were able to reach 00:05:01.170 --> 00:05:06.280 align:start position:0% all these clients were able to reach consensus<00:05:01.710> over<00:05:02.370> the<00:05:02.490> p2p<00:05:05.000> but<00:05:06.000> that's 00:05:06.280 --> 00:05:06.290 align:start position:0% consensus over the p2p but that's 00:05:06.290 --> 00:05:08.960 align:start position:0% consensus over the p2p but that's obviously<00:05:07.290> not<00:05:07.470> the<00:05:07.890> end<00:05:08.160> of<00:05:08.250> the<00:05:08.370> road<00:05:08.520> we 00:05:08.960 --> 00:05:08.970 align:start position:0% obviously not the end of the road we 00:05:08.970 --> 00:05:12.980 align:start position:0% obviously not the end of the road we have<00:05:09.180> a<00:05:09.630> lot<00:05:10.140> of<00:05:10.610> work<00:05:11.610> to<00:05:11.760> do<00:05:11.880> ahead<00:05:12.030> of<00:05:12.300> us<00:05:12.450> and 00:05:12.980 --> 00:05:12.990 align:start position:0% have a lot of work to do ahead of us and 00:05:12.990 --> 00:05:15.590 align:start position:0% have a lot of work to do ahead of us and the<00:05:13.500> leap<00:05:13.650> p2p<00:05:14.010> spec<00:05:14.280> that<00:05:14.670> we<00:05:14.820> created<00:05:15.270> for<00:05:15.540> a 00:05:15.590 --> 00:05:15.600 align:start position:0% the leap p2p spec that we created for a 00:05:15.600 --> 00:05:18.320 align:start position:0% the leap p2p spec that we created for a tearoom<00:05:15.900> -<00:05:16.110> is<00:05:16.320> actually<00:05:16.770> divided<00:05:17.070> in<00:05:17.550> you<00:05:18.150> can 00:05:18.320 --> 00:05:18.330 align:start position:0% tearoom - is actually divided in you can 00:05:18.330 --> 00:05:22.280 align:start position:0% tearoom - is actually divided in you can say<00:05:18.480> to<00:05:18.540> treat<00:05:19.410> two<00:05:19.830> or<00:05:20.040> more<00:05:20.250> phases<00:05:21.290> we 00:05:22.280 --> 00:05:22.290 align:start position:0% say to treat two or more phases we 00:05:22.290 --> 00:05:25.430 align:start position:0% say to treat two or more phases we identified<00:05:23.190> some<00:05:23.760> initial<00:05:24.120> targets<00:05:24.570> some 00:05:25.430 --> 00:05:25.440 align:start position:0% identified some initial targets some 00:05:25.440 --> 00:05:28.580 align:start position:0% identified some initial targets some initial<00:05:26.960> minimal<00:05:27.960> set<00:05:28.140> of<00:05:28.170> common 00:05:28.580 --> 00:05:28.590 align:start position:0% initial minimal set of common 00:05:28.590 --> 00:05:30.590 align:start position:0% initial minimal set of common requirements<00:05:29.220> that<00:05:29.340> all<00:05:29.760> the<00:05:30.060> clans<00:05:30.240> have<00:05:30.480> to 00:05:30.590 --> 00:05:30.600 align:start position:0% requirements that all the clans have to 00:05:30.600 --> 00:05:32.120 align:start position:0% requirements that all the clans have to implement<00:05:30.810> you<00:05:31.080> know<00:05:31.200> in<00:05:31.500> order<00:05:31.770> to<00:05:31.920> be<00:05:32.040> able 00:05:32.120 --> 00:05:32.130 align:start position:0% implement you know in order to be able 00:05:32.130 --> 00:05:36.020 align:start position:0% implement you know in order to be able to<00:05:32.280> talk<00:05:32.520> to<00:05:32.550> each<00:05:32.790> other<00:05:33.530> but<00:05:34.530> these<00:05:34.770> are<00:05:35.070> not 00:05:36.020 --> 00:05:36.030 align:start position:0% to talk to each other but these are not 00:05:36.030 --> 00:05:39.200 align:start position:0% to talk to each other but these are not the<00:05:36.210> underpinnings<00:05:36.900> of<00:05:36.960> a<00:05:37.080> secure<00:05:38.010> system<00:05:38.280> for 00:05:39.200 --> 00:05:39.210 align:start position:0% the underpinnings of a secure system for 00:05:39.210 --> 00:05:40.820 align:start position:0% the underpinnings of a secure system for launching<00:05:39.900> maintenance<00:05:40.380> we<00:05:40.530> would<00:05:40.650> be 00:05:40.820 --> 00:05:40.830 align:start position:0% launching maintenance we would be 00:05:40.830 --> 00:05:43.460 align:start position:0% launching maintenance we would be changing<00:05:41.280> a<00:05:41.400> lot<00:05:41.550> of<00:05:41.700> the<00:05:42.000> protocols<00:05:42.510> to<00:05:42.630> more 00:05:43.460 --> 00:05:43.470 align:start position:0% changing a lot of the protocols to more 00:05:43.470 --> 00:05:45.890 align:start position:0% changing a lot of the protocols to more modern<00:05:43.890> cryptography<00:05:44.580> more<00:05:45.120> modern<00:05:45.570> way<00:05:45.720> of 00:05:45.890 --> 00:05:45.900 align:start position:0% modern cryptography more modern way of 00:05:45.900 --> 00:05:47.330 align:start position:0% modern cryptography more modern way of doing<00:05:46.110> this<00:05:46.290> we'll<00:05:46.770> be<00:05:46.800> adding<00:05:47.040> new 00:05:47.330 --> 00:05:47.340 align:start position:0% doing this we'll be adding new 00:05:47.340 --> 00:05:50.540 align:start position:0% doing this we'll be adding new transports<00:05:48.090> and<00:05:48.860> even<00:05:49.860> this<00:05:49.980> is<00:05:50.100> not<00:05:50.250> where 00:05:50.540 --> 00:05:50.550 align:start position:0% transports and even this is not where 00:05:50.550 --> 00:05:54.110 align:start position:0% transports and even this is not where the<00:05:51.000> road<00:05:51.180> ends<00:05:51.480> over<00:05:52.350> time<00:05:52.770> there<00:05:53.640> will<00:05:53.760> be<00:05:53.790> a 00:05:54.110 --> 00:05:54.120 align:start position:0% the road ends over time there will be a 00:05:54.120 --> 00:05:56.330 align:start position:0% the road ends over time there will be a lot<00:05:54.660> of<00:05:54.690> new<00:05:54.990> high-level<00:05:55.260> protocols<00:05:55.950> defined 00:05:56.330 --> 00:05:56.340 align:start position:0% lot of new high-level protocols defined 00:05:56.340 --> 00:05:58.570 align:start position:0% lot of new high-level protocols defined for<00:05:56.640> things<00:05:56.970> like<00:05:57.030> light<00:05:57.390> clans<00:05:57.720> for<00:05:58.140> the 00:05:58.570 --> 00:05:58.580 align:start position:0% for things like light clans for the 00:05:58.580 --> 00:06:02.570 align:start position:0% for things like light clans for the communication<00:05:59.580> within<00:05:59.730> shards<00:06:00.240> and<00:06:00.420> so<00:06:00.570> on<00:06:01.580> so 00:06:02.570 --> 00:06:02.580 align:start position:0% communication within shards and so on so 00:06:02.580 --> 00:06:04.700 align:start position:0% communication within shards and so on so just<00:06:02.730> to<00:06:02.880> give<00:06:03.000> you<00:06:03.090> an<00:06:03.150> example<00:06:03.560> here<00:06:04.560> is<00:06:04.680> a 00:06:04.700 --> 00:06:04.710 align:start position:0% just to give you an example here is a 00:06:04.710 --> 00:06:07.850 align:start position:0% just to give you an example here is a comparison<00:06:05.400> between<00:06:06.110> this<00:06:07.110> minimum<00:06:07.620> winter 00:06:07.850 --> 00:06:07.860 align:start position:0% comparison between this minimum winter 00:06:07.860 --> 00:06:11.330 align:start position:0% comparison between this minimum winter of<00:06:08.010> spec<00:06:08.340> and<00:06:08.670> what<00:06:08.850> we<00:06:09.030> expect<00:06:09.540> to<00:06:09.720> do<00:06:10.470> in<00:06:10.830> form 00:06:11.330 --> 00:06:11.340 align:start position:0% of spec and what we expect to do in form 00:06:11.340 --> 00:06:13.280 align:start position:0% of spec and what we expect to do in form a<00:06:11.460> net<00:06:11.700> in<00:06:11.910> just<00:06:12.120> few<00:06:12.270> months<00:06:12.390> we'll<00:06:13.200> be 00:06:13.280 --> 00:06:13.290 align:start position:0% a net in just few months we'll be 00:06:13.290 --> 00:06:16.670 align:start position:0% a net in just few months we'll be changing<00:06:14.150> the<00:06:15.150> encryption<00:06:15.600> framework<00:06:16.110> and 00:06:16.670 --> 00:06:16.680 align:start position:0% changing the encryption framework and 00:06:16.680 --> 00:06:18.470 align:start position:0% changing the encryption framework and the<00:06:16.830> keys<00:06:17.070> that<00:06:17.100> are<00:06:17.460> used<00:06:17.880> to<00:06:18.000> indentify<00:06:18.330> the 00:06:18.470 --> 00:06:18.480 align:start position:0% the keys that are used to indentify the 00:06:18.480 --> 00:06:21.860 align:start position:0% the keys that are used to indentify the nodes<00:06:18.950> will<00:06:19.950> be<00:06:19.980> switching<00:06:20.310> to<00:06:20.760> the<00:06:20.880> supports 00:06:21.860 --> 00:06:21.870 align:start position:0% nodes will be switching to the supports 00:06:21.870 --> 00:06:23.620 align:start position:0% nodes will be switching to the supports changing<00:06:22.410> the<00:06:22.680> SU<00:06:22.830> protocol<00:06:23.250> negotiation 00:06:23.620 --> 00:06:23.630 align:start position:0% changing the SU protocol negotiation 00:06:23.630 --> 00:06:27.080 align:start position:0% changing the SU protocol negotiation scheme<00:06:24.630> in<00:06:24.810> the<00:06:25.140> p2p<00:06:25.410> and<00:06:25.830> so<00:06:26.160> on<00:06:26.310> you<00:06:27.060> are 00:06:27.080 --> 00:06:27.090 align:start position:0% scheme in the p2p and so on you are 00:06:27.090 --> 00:06:30.200 align:start position:0% scheme in the p2p and so on you are introducing<00:06:27.660> compression<00:06:28.430> quite<00:06:29.430> you<00:06:30.060> can 00:06:30.200 --> 00:06:30.210 align:start position:0% introducing compression quite you can 00:06:30.210 --> 00:06:32.030 align:start position:0% introducing compression quite you can say<00:06:30.330> that<00:06:30.480> the<00:06:30.600> entire<00:06:31.020> stack<00:06:31.410> on<00:06:31.770> every 00:06:32.030 --> 00:06:32.040 align:start position:0% say that the entire stack on every 00:06:32.040 --> 00:06:34.070 align:start position:0% say that the entire stack on every single<00:06:32.220> layer<00:06:32.550> there<00:06:33.420> will<00:06:33.570> be<00:06:33.600> new 00:06:34.070 --> 00:06:34.080 align:start position:0% single layer there will be new 00:06:34.080 --> 00:06:36.100 align:start position:0% single layer there will be new developments 00:06:36.100 --> 00:06:36.110 align:start position:0% developments 00:06:36.110 --> 00:06:39.860 align:start position:0% developments so<00:06:37.160> in<00:06:38.160> closing<00:06:38.340> remarks 00:06:39.860 --> 00:06:39.870 align:start position:0% so in closing remarks 00:06:39.870 --> 00:06:43.340 align:start position:0% so in closing remarks I<00:06:39.900> would<00:06:40.710> like<00:06:41.070> to<00:06:41.100> stress<00:06:41.460> out<00:06:41.669> that<00:06:42.169> what<00:06:43.169> we 00:06:43.340 --> 00:06:43.350 align:start position:0% I would like to stress out that what we 00:06:43.350 --> 00:06:45.350 align:start position:0% I would like to stress out that what we are<00:06:43.380> creating<00:06:43.770> here<00:06:43.919> would<00:06:44.190> be<00:06:44.340> very<00:06:44.910> valuable 00:06:45.350 --> 00:06:45.360 align:start position:0% are creating here would be very valuable 00:06:45.360 --> 00:06:47.240 align:start position:0% are creating here would be very valuable not<00:06:45.720> just<00:06:45.780> for<00:06:46.290> a<00:06:46.500> theorem<00:06:46.800> like<00:06:46.919> we're 00:06:47.240 --> 00:06:47.250 align:start position:0% not just for a theorem like we're 00:06:47.250 --> 00:06:49.189 align:start position:0% not just for a theorem like we're creating<00:06:47.639> this<00:06:47.760> system<00:06:47.970> of<00:06:48.419> Oh<00:06:48.690> between<00:06:48.900> so 00:06:49.189 --> 00:06:49.199 align:start position:0% creating this system of Oh between so 00:06:49.199 --> 00:06:51.110 align:start position:0% creating this system of Oh between so many<00:06:49.260> programming<00:06:49.860> languages<00:06:50.190> now<00:06:50.490> that 00:06:51.110 --> 00:06:51.120 align:start position:0% many programming languages now that 00:06:51.120 --> 00:06:53.540 align:start position:0% many programming languages now that could<00:06:51.780> serve<00:06:52.020> as<00:06:52.350> the<00:06:52.470> foundation<00:06:52.620> layer<00:06:53.190> for 00:06:53.540 --> 00:06:53.550 align:start position:0% could serve as the foundation layer for 00:06:53.550 --> 00:06:56.030 align:start position:0% could serve as the foundation layer for any<00:06:54.120> kind<00:06:54.419> of<00:06:54.570> distributed<00:06:55.020> applications<00:06:55.889> in 00:06:56.030 --> 00:06:56.040 align:start position:0% any kind of distributed applications in 00:06:56.040 --> 00:06:57.939 align:start position:0% any kind of distributed applications in the<00:06:56.130> future<00:06:56.250> and<00:06:56.639> that's<00:06:56.820> centralized 00:06:57.939 --> 00:06:57.949 align:start position:0% the future and that's centralized 00:06:57.949 --> 00:07:01.969 align:start position:0% the future and that's centralized when<00:06:58.949> we<00:06:59.610> are<00:06:59.639> ready<00:06:59.850> it<00:07:00.780> will<00:07:00.900> be<00:07:01.110> very<00:07:01.740> easy 00:07:01.969 --> 00:07:01.979 align:start position:0% when we are ready it will be very easy 00:07:01.979 --> 00:07:03.890 align:start position:0% when we are ready it will be very easy for<00:07:02.010> many<00:07:02.370> developers<00:07:02.790> to<00:07:02.970> just<00:07:03.180> take<00:07:03.720> over 00:07:03.890 --> 00:07:03.900 align:start position:0% for many developers to just take over 00:07:03.900 --> 00:07:05.540 align:start position:0% for many developers to just take over the<00:07:03.990> Shelf<00:07:04.290> implementation<00:07:04.949> of<00:07:05.040> lipid<00:07:05.340> to<00:07:05.400> be 00:07:05.540 --> 00:07:05.550 align:start position:0% the Shelf implementation of lipid to be 00:07:05.550 --> 00:07:07.670 align:start position:0% the Shelf implementation of lipid to be for<00:07:05.940> their<00:07:06.060> language<00:07:06.240> and<00:07:06.750> build<00:07:07.260> something 00:07:07.670 --> 00:07:07.680 align:start position:0% for their language and build something 00:07:07.680 --> 00:07:10.969 align:start position:0% for their language and build something amazing<00:07:08.100> with<00:07:08.550> it<00:07:08.669> so<00:07:09.630> the<00:07:10.320> p2<00:07:10.530> is<00:07:10.650> not<00:07:10.800> just 00:07:10.969 --> 00:07:10.979 align:start position:0% amazing with it so the p2 is not just 00:07:10.979 --> 00:07:13.190 align:start position:0% amazing with it so the p2 is not just for<00:07:11.130> a<00:07:11.160> tea<00:07:11.310> room<00:07:11.340> but<00:07:11.580> material<00:07:12.120> our<00:07:12.720> effort 00:07:13.190 --> 00:07:13.200 align:start position:0% for a tea room but material our effort 00:07:13.200 --> 00:07:18.050 align:start position:0% for a tea room but material our effort will<00:07:13.470> make<00:07:13.620> it<00:07:13.770> much<00:07:14.130> much<00:07:14.280> stronger<00:07:17.060> all 00:07:18.050 --> 00:07:18.060 align:start position:0% will make it much much stronger all 00:07:18.060 --> 00:07:20.719 align:start position:0% will make it much much stronger all right<00:07:18.270> so<00:07:18.540> I<00:07:19.080> figured<00:07:19.770> the<00:07:19.979> next<00:07:20.010> part<00:07:20.550> of<00:07:20.639> the 00:07:20.719 --> 00:07:20.729 align:start position:0% right so I figured the next part of the 00:07:20.729 --> 00:07:23.420 align:start position:0% right so I figured the next part of the talk<00:07:20.910> we<00:07:21.270> walk<00:07:22.080> us<00:07:22.320> through<00:07:22.350> how<00:07:22.889> do<00:07:23.130> you 00:07:23.420 --> 00:07:23.430 align:start position:0% talk we walk us through how do you 00:07:23.430 --> 00:07:25.550 align:start position:0% talk we walk us through how do you connect<00:07:23.729> to<00:07:23.970> the<00:07:24.060> network<00:07:24.240> like<00:07:24.930> what<00:07:25.169> are<00:07:25.380> the 00:07:25.550 --> 00:07:25.560 align:start position:0% connect to the network like what are the 00:07:25.560 --> 00:07:28.790 align:start position:0% connect to the network like what are the individual<00:07:25.950> steps<00:07:27.139> the<00:07:28.139> first<00:07:28.410> thing<00:07:28.620> you 00:07:28.790 --> 00:07:28.800 align:start position:0% individual steps the first thing you 00:07:28.800 --> 00:07:33.110 align:start position:0% individual steps the first thing you need<00:07:28.950> is<00:07:29.610> a<00:07:29.669> discovery<00:07:30.210> mechanism<00:07:31.400> now<00:07:32.400> I<00:07:32.729> did 00:07:33.110 --> 00:07:33.120 align:start position:0% need is a discovery mechanism now I did 00:07:33.120 --> 00:07:37.129 align:start position:0% need is a discovery mechanism now I did mention<00:07:33.330> that<00:07:33.479> the<00:07:33.990> p2p<00:07:34.260> is<00:07:35.539> going<00:07:36.539> to<00:07:36.840> go 00:07:37.129 --> 00:07:37.139 align:start position:0% mention that the p2p is going to go 00:07:37.139 --> 00:07:39.500 align:start position:0% mention that the p2p is going to go through<00:07:37.500> further<00:07:37.800> revolution<00:07:38.430> with<00:07:38.940> one<00:07:39.150> area 00:07:39.500 --> 00:07:39.510 align:start position:0% through further revolution with one area 00:07:39.510 --> 00:07:42.020 align:start position:0% through further revolution with one area where<00:07:39.960> it<00:07:40.320> didn't<00:07:40.979> quite<00:07:41.160> meet<00:07:41.430> the<00:07:41.460> needs<00:07:41.820> of 00:07:42.020 --> 00:07:42.030 align:start position:0% where it didn't quite meet the needs of 00:07:42.030 --> 00:07:44.950 align:start position:0% where it didn't quite meet the needs of a<00:07:42.270> tea<00:07:42.330> room<00:07:42.570> right<00:07:42.750> now<00:07:42.960> was<00:07:43.260> a<00:07:43.500> discovery 00:07:44.950 --> 00:07:44.960 align:start position:0% a tea room right now was a discovery 00:07:44.960 --> 00:07:47.840 align:start position:0% a tea room right now was a discovery since<00:07:45.960> a<00:07:46.680> tea<00:07:47.100> room<00:07:47.130> has<00:07:47.490> been<00:07:47.639> sober 00:07:47.840 --> 00:07:47.850 align:start position:0% since a tea room has been sober 00:07:47.850 --> 00:07:49.640 align:start position:0% since a tea room has been sober absolving<00:07:48.510> the<00:07:48.630> discovery<00:07:49.050> problem<00:07:49.440> for<00:07:49.620> a 00:07:49.640 --> 00:07:49.650 align:start position:0% absolving the discovery problem for a 00:07:49.650 --> 00:07:52.070 align:start position:0% absolving the discovery problem for a while<00:07:49.860> and<00:07:50.160> we<00:07:50.490> have<00:07:50.700> identified<00:07:51.270> some<00:07:51.600> unique 00:07:52.070 --> 00:07:52.080 align:start position:0% while and we have identified some unique 00:07:52.080 --> 00:07:54.920 align:start position:0% while and we have identified some unique requirements<00:07:53.090> that<00:07:54.090> we<00:07:54.300> won't<00:07:54.510> have<00:07:54.690> in<00:07:54.840> the 00:07:54.920 --> 00:07:54.930 align:start position:0% requirements that we won't have in the 00:07:54.930 --> 00:07:56.750 align:start position:0% requirements that we won't have in the network<00:07:55.110> the<00:07:55.919> existing<00:07:56.250> repeat<00:07:56.550> fit 00:07:56.750 --> 00:07:56.760 align:start position:0% network the existing repeat fit 00:07:56.760 --> 00:07:58.370 align:start position:0% network the existing repeat fit solutions<00:07:56.910> for<00:07:57.360> discovery<00:07:57.780> didn't<00:07:58.200> quite 00:07:58.370 --> 00:07:58.380 align:start position:0% solutions for discovery didn't quite 00:07:58.380 --> 00:08:02.839 align:start position:0% solutions for discovery didn't quite meet<00:07:58.620> them<00:07:58.830> so<00:07:59.039> instead<00:07:59.820> we<00:08:00.660> decided<00:08:00.780> to<00:08:01.849> unite 00:08:02.839 --> 00:08:02.849 align:start position:0% meet them so instead we decided to unite 00:08:02.849 --> 00:08:05.450 align:start position:0% meet them so instead we decided to unite the<00:08:03.000> efforts<00:08:03.080> for<00:08:04.080> a<00:08:04.530> tea<00:08:05.190> room<00:08:05.220> one 00:08:05.450 --> 00:08:05.460 align:start position:0% the efforts for a tea room one 00:08:05.460 --> 00:08:07.430 align:start position:0% the efforts for a tea room one development<00:08:05.970> and<00:08:06.150> here<00:08:06.300> on<00:08:06.419> to<00:08:06.660> I<00:08:06.870> need<00:08:07.320> to 00:08:07.430 --> 00:08:07.440 align:start position:0% development and here on to I need to 00:08:07.440 --> 00:08:09.290 align:start position:0% development and here on to I need to introduce<00:08:07.680> a<00:08:08.190> new<00:08:08.400> discovery<00:08:08.729> mechanism 00:08:09.290 --> 00:08:09.300 align:start position:0% introduce a new discovery mechanism 00:08:09.300 --> 00:08:11.779 align:start position:0% introduce a new discovery mechanism called<00:08:09.539> discovery<00:08:10.050> five<00:08:10.410> which<00:08:11.130> will<00:08:11.340> be<00:08:11.550> used 00:08:11.779 --> 00:08:11.789 align:start position:0% called discovery five which will be used 00:08:11.789 --> 00:08:14.570 align:start position:0% called discovery five which will be used in<00:08:11.940> both<00:08:12.090> networks<00:08:12.410> so<00:08:13.410> the<00:08:13.740> key<00:08:13.979> features 00:08:14.570 --> 00:08:14.580 align:start position:0% in both networks so the key features 00:08:14.580 --> 00:08:17.060 align:start position:0% in both networks so the key features that<00:08:15.360> are<00:08:15.960> missing<00:08:16.110> in<00:08:16.410> the<00:08:16.560> p2p<00:08:16.800> at<00:08:16.979> this 00:08:17.060 --> 00:08:17.070 align:start position:0% that are missing in the p2p at this 00:08:17.070 --> 00:08:20.360 align:start position:0% that are missing in the p2p at this point<00:08:17.370> is<00:08:17.880> one<00:08:18.660> first<00:08:18.960> of<00:08:19.050> all<00:08:19.169> the<00:08:19.470> capability 00:08:20.360 --> 00:08:20.370 align:start position:0% point is one first of all the capability 00:08:20.370 --> 00:08:23.000 align:start position:0% point is one first of all the capability advertising<00:08:20.970> this<00:08:21.150> is<00:08:21.300> where<00:08:21.510> a<00:08:21.780> known<00:08:22.080> a<00:08:22.620> node 00:08:23.000 --> 00:08:23.010 align:start position:0% advertising this is where a known a node 00:08:23.010 --> 00:08:30.250 align:start position:0% advertising this is where a known a node can<00:08:25.550> make<00:08:26.550> sure<00:08:27.030> that<00:08:27.240> can<00:08:27.960> be<00:08:28.110> found<00:08:28.349> on<00:08:29.150> the 00:08:30.250 --> 00:08:30.260 align:start position:0% can make sure that can be found on the 00:08:30.260 --> 00:08:32.930 align:start position:0% can make sure that can be found on the criteria<00:08:31.260> that<00:08:31.320> it<00:08:31.650> supports<00:08:32.190> a<00:08:32.400> particular 00:08:32.930 --> 00:08:32.940 align:start position:0% criteria that it supports a particular 00:08:32.940 --> 00:08:35.390 align:start position:0% criteria that it supports a particular protocol<00:08:33.450> for<00:08:34.409> example<00:08:34.860> this<00:08:35.070> could<00:08:35.250> be<00:08:35.370> a 00:08:35.390 --> 00:08:35.400 align:start position:0% protocol for example this could be a 00:08:35.400 --> 00:08:38.510 align:start position:0% protocol for example this could be a note<00:08:35.640> that<00:08:35.940> supports<00:08:36.830> the<00:08:37.830> right<00:08:37.950> client 00:08:38.510 --> 00:08:38.520 align:start position:0% note that supports the right client 00:08:38.520 --> 00:08:40.750 align:start position:0% note that supports the right client protocol<00:08:39.000> and<00:08:39.209> it<00:08:39.390> can<00:08:39.599> act<00:08:39.779> as<00:08:39.870> a<00:08:39.959> server<00:08:40.200> and 00:08:40.750 --> 00:08:40.760 align:start position:0% protocol and it can act as a server and 00:08:40.760 --> 00:08:44.840 align:start position:0% protocol and it can act as a server and the<00:08:41.760> other<00:08:42.469> feature<00:08:43.469> is<00:08:43.650> topic<00:08:44.190> advertising 00:08:44.840 --> 00:08:44.850 align:start position:0% the other feature is topic advertising 00:08:44.850 --> 00:08:46.940 align:start position:0% the other feature is topic advertising now<00:08:45.089> this<00:08:45.300> is<00:08:45.420> more<00:08:45.630> about<00:08:45.750> that<00:08:46.560> this<00:08:46.740> node 00:08:46.940 --> 00:08:46.950 align:start position:0% now this is more about that this node 00:08:46.950 --> 00:08:49.370 align:start position:0% now this is more about that this node has<00:08:47.220> access<00:08:47.730> to<00:08:47.760> some<00:08:48.030> resource<00:08:48.510> for<00:08:48.930> example 00:08:49.370 --> 00:08:49.380 align:start position:0% has access to some resource for example 00:08:49.380 --> 00:08:52.160 align:start position:0% has access to some resource for example it<00:08:49.920> could<00:08:50.190> be<00:08:50.250> the<00:08:50.940> fact<00:08:51.300> that<00:08:51.450> the<00:08:51.600> node<00:08:51.780> is 00:08:52.160 --> 00:08:52.170 align:start position:0% it could be the fact that the node is 00:08:52.170 --> 00:08:53.750 align:start position:0% it could be the fact that the node is currently<00:08:52.740> connected<00:08:53.010> to<00:08:53.310> a<00:08:53.339> party 00:08:53.750 --> 00:08:53.760 align:start position:0% currently connected to a party 00:08:53.760 --> 00:08:56.630 align:start position:0% currently connected to a party shirt<00:08:54.150> so<00:08:54.780> you<00:08:54.870> can<00:08:55.170> sync<00:08:55.470> the<00:08:55.890> information<00:08:56.460> on 00:08:56.630 --> 00:08:56.640 align:start position:0% shirt so you can sync the information on 00:08:56.640 --> 00:08:58.880 align:start position:0% shirt so you can sync the information on this<00:08:56.910> particular<00:08:57.450> chart<00:08:57.780> and<00:08:58.080> you<00:08:58.440> need<00:08:58.740> to 00:08:58.880 --> 00:08:58.890 align:start position:0% this particular chart and you need to 00:08:58.890 --> 00:09:01.310 align:start position:0% this particular chart and you need to find<00:08:59.100> nodes<00:08:59.610> which<00:08:59.970> are<00:09:00.180> already<00:09:00.450> connected 00:09:01.310 --> 00:09:01.320 align:start position:0% find nodes which are already connected 00:09:01.320 --> 00:09:06.770 align:start position:0% find nodes which are already connected to<00:09:01.410> it<00:09:01.530> and<00:09:04.130> we<00:09:05.130> didn't<00:09:05.310> discover<00:09:05.580> v5<00:09:06.060> there<00:09:06.690> is 00:09:06.770 --> 00:09:06.780 align:start position:0% to it and we didn't discover v5 there is 00:09:06.780 --> 00:09:08.600 align:start position:0% to it and we didn't discover v5 there is this<00:09:06.930> general<00:09:07.260> purpose<00:09:07.890> mechanism<00:09:08.490> of 00:09:08.600 --> 00:09:08.610 align:start position:0% this general purpose mechanism of 00:09:08.610 --> 00:09:11.840 align:start position:0% this general purpose mechanism of attaching<00:09:09.000> arbitrary<00:09:09.900> data<00:09:10.310> so<00:09:11.310> it's<00:09:11.640> both 00:09:11.840 --> 00:09:11.850 align:start position:0% attaching arbitrary data so it's both 00:09:11.850 --> 00:09:15.340 align:start position:0% attaching arbitrary data so it's both extensible<00:09:12.690> in<00:09:12.960> the<00:09:13.050> future<00:09:13.410> for<00:09:13.920> adding<00:09:14.760> more 00:09:15.340 --> 00:09:15.350 align:start position:0% extensible in the future for adding more 00:09:15.350 --> 00:09:18.830 align:start position:0% extensible in the future for adding more relevant<00:09:16.350> information<00:09:16.980> and<00:09:17.160> it's<00:09:17.910> quite<00:09:18.690> easy 00:09:18.830 --> 00:09:18.840 align:start position:0% relevant information and it's quite easy 00:09:18.840 --> 00:09:20.600 align:start position:0% relevant information and it's quite easy to<00:09:18.960> adapt<00:09:19.320> it<00:09:19.500> to<00:09:19.530> the<00:09:19.710> needs<00:09:19.740> of<00:09:20.040> Lippe<00:09:20.340> 2p 00:09:20.600 --> 00:09:20.610 align:start position:0% to adapt it to the needs of Lippe 2p 00:09:20.610 --> 00:09:26.420 align:start position:0% to adapt it to the needs of Lippe 2p already<00:09:23.480> so<00:09:24.480> after<00:09:24.900> we<00:09:25.050> have<00:09:25.200> found<00:09:25.500> other 00:09:26.420 --> 00:09:26.430 align:start position:0% already so after we have found other 00:09:26.430 --> 00:09:29.780 align:start position:0% already so after we have found other nodes<00:09:26.730> on<00:09:26.910> the<00:09:27.000> network<00:09:27.770> what<00:09:28.770> we<00:09:29.070> usually<00:09:29.430> do 00:09:29.780 --> 00:09:29.790 align:start position:0% nodes on the network what we usually do 00:09:29.790 --> 00:09:32.780 align:start position:0% nodes on the network what we usually do is<00:09:29.970> we<00:09:30.000> will<00:09:30.300> start<00:09:31.400> listening<00:09:32.400> to<00:09:32.640> the 00:09:32.780 --> 00:09:32.790 align:start position:0% is we will start listening to the 00:09:32.790 --> 00:09:34.970 align:start position:0% is we will start listening to the broadcast<00:09:33.210> the<00:09:33.870> gossip<00:09:34.200> sub<00:09:34.350> traffic<00:09:34.740> as<00:09:34.860> I 00:09:34.970 --> 00:09:34.980 align:start position:0% broadcast the gossip sub traffic as I 00:09:34.980 --> 00:09:39.740 align:start position:0% broadcast the gossip sub traffic as I mentioned<00:09:35.430> and<00:09:36.240> here<00:09:37.200> I've<00:09:37.530> listed<00:09:38.450> the<00:09:39.450> few 00:09:39.740 --> 00:09:39.750 align:start position:0% mentioned and here I've listed the few 00:09:39.750 --> 00:09:43.880 align:start position:0% mentioned and here I've listed the few particular<00:09:40.260> gossip<00:09:40.860> gossip<00:09:41.670> sub<00:09:42.080> topics<00:09:43.080> that 00:09:43.880 --> 00:09:43.890 align:start position:0% particular gossip gossip sub topics that 00:09:43.890 --> 00:09:47.540 align:start position:0% particular gossip gossip sub topics that are<00:09:44.100> relevant<00:09:44.670> for<00:09:45.170> kind<00:09:46.170> of<00:09:46.260> following<00:09:46.680> the 00:09:47.540 --> 00:09:47.550 align:start position:0% are relevant for kind of following the 00:09:47.550 --> 00:09:49.850 align:start position:0% are relevant for kind of following the progress<00:09:47.940> on<00:09:48.060> the<00:09:48.150> beacon<00:09:48.450> chain<00:09:48.720> and<00:09:49.500> we<00:09:49.680> have 00:09:49.850 --> 00:09:49.860 align:start position:0% progress on the beacon chain and we have 00:09:49.860 --> 00:09:53.300 align:start position:0% progress on the beacon chain and we have a<00:09:49.890> topic<00:09:50.250> where<00:09:50.460> new<00:09:51.060> blocks<00:09:51.330> are<00:09:51.540> produced<00:09:52.310> we 00:09:53.300 --> 00:09:53.310 align:start position:0% a topic where new blocks are produced we 00:09:53.310 --> 00:09:55.640 align:start position:0% a topic where new blocks are produced we have<00:09:53.520> a<00:09:53.790> other<00:09:54.180> topic<00:09:54.630> where<00:09:54.810> all<00:09:55.140> the<00:09:55.440> other 00:09:55.640 --> 00:09:55.650 align:start position:0% have a other topic where all the other 00:09:55.650 --> 00:09:57.590 align:start position:0% have a other topic where all the other stations<00:09:56.130> are<00:09:56.280> being<00:09:56.490> sent<00:09:56.790> and<00:09:57.060> current<00:09:57.450> in 00:09:57.590 --> 00:09:57.600 align:start position:0% stations are being sent and current in 00:09:57.600 --> 00:09:59.960 align:start position:0% stations are being sent and current in interrupt<00:09:58.140> we<00:09:58.350> use<00:09:58.980> a<00:09:59.010> single<00:09:59.430> topic<00:09:59.580> for<00:09:59.940> that 00:09:59.960 --> 00:09:59.970 align:start position:0% interrupt we use a single topic for that 00:09:59.970 --> 00:10:02.930 align:start position:0% interrupt we use a single topic for that so<00:10:00.570> that's<00:10:01.170> enough<00:10:01.380> to<00:10:01.620> to<00:10:02.010> monitor<00:10:02.340> the<00:10:02.790> whole 00:10:02.930 --> 00:10:02.940 align:start position:0% so that's enough to to monitor the whole 00:10:02.940 --> 00:10:04.970 align:start position:0% so that's enough to to monitor the whole network<00:10:03.270> but<00:10:03.870> what<00:10:04.260> we<00:10:04.380> plan<00:10:04.560> to<00:10:04.680> do<00:10:04.770> in<00:10:04.890> the 00:10:04.970 --> 00:10:04.980 align:start position:0% network but what we plan to do in the 00:10:04.980 --> 00:10:06.920 align:start position:0% network but what we plan to do in the future<00:10:05.190> is<00:10:05.430> to<00:10:05.760> introduce<00:10:05.910> separate<00:10:06.540> topics 00:10:06.920 --> 00:10:06.930 align:start position:0% future is to introduce separate topics 00:10:06.930 --> 00:10:10.010 align:start position:0% future is to introduce separate topics for<00:10:07.200> each<00:10:07.380> individual<00:10:07.950> chart<00:10:08.870> and<00:10:09.870> then 00:10:10.010 --> 00:10:10.020 align:start position:0% for each individual chart and then 00:10:10.020 --> 00:10:11.690 align:start position:0% for each individual chart and then you'll<00:10:10.170> be<00:10:10.320> able<00:10:10.380> to<00:10:10.620> choose<00:10:10.860> like<00:10:11.130> whether 00:10:11.690 --> 00:10:11.700 align:start position:0% you'll be able to choose like whether 00:10:11.700 --> 00:10:15.110 align:start position:0% you'll be able to choose like whether you<00:10:11.910> want<00:10:12.090> to<00:10:12.240> listen<00:10:12.930> to<00:10:13.170> the<00:10:13.820> traffic<00:10:14.820> for 00:10:15.110 --> 00:10:15.120 align:start position:0% you want to listen to the traffic for 00:10:15.120 --> 00:10:17.540 align:start position:0% you want to listen to the traffic for finalized<00:10:15.570> box<00:10:15.810> or<00:10:16.110> the<00:10:16.560> traffic's<00:10:17.010> for<00:10:17.280> at 00:10:17.540 --> 00:10:17.550 align:start position:0% finalized box or the traffic's for at 00:10:17.550 --> 00:10:20.120 align:start position:0% finalized box or the traffic's for at the<00:10:17.670> station<00:10:17.970> on<00:10:18.090> a<00:10:18.120> given<00:10:18.420> chart<00:10:18.950> and<00:10:19.950> then 00:10:20.120 --> 00:10:20.130 align:start position:0% the station on a given chart and then 00:10:20.130 --> 00:10:22.280 align:start position:0% the station on a given chart and then there<00:10:20.400> are<00:10:20.430> a<00:10:20.820> few<00:10:21.330> topics<00:10:21.660> which<00:10:21.960> are 00:10:22.280 --> 00:10:22.290 align:start position:0% there are a few topics which are 00:10:22.290 --> 00:10:25.520 align:start position:0% there are a few topics which are beginning<00:10:23.150> much<00:10:24.150> slower<00:10:24.630> amounts<00:10:25.230> of<00:10:25.320> traffic 00:10:25.520 --> 00:10:25.530 align:start position:0% beginning much slower amounts of traffic 00:10:25.530 --> 00:10:29.150 align:start position:0% beginning much slower amounts of traffic these<00:10:26.010> are<00:10:26.220> just<00:10:27.080> for<00:10:28.080> announcing<00:10:28.500> exits 00:10:29.150 --> 00:10:29.160 align:start position:0% these are just for announcing exits 00:10:29.160 --> 00:10:31.370 align:start position:0% these are just for announcing exits where<00:10:29.550> a<00:10:29.580> validator<00:10:30.090> once<00:10:30.930> talk<00:10:31.170> to<00:10:31.290> the 00:10:31.370 --> 00:10:31.380 align:start position:0% where a validator once talk to the 00:10:31.380 --> 00:10:33.740 align:start position:0% where a validator once talk to the network<00:10:31.500> or<00:10:31.890> for<00:10:32.250> slashings<00:10:33.000> when<00:10:33.360> something 00:10:33.740 --> 00:10:33.750 align:start position:0% network or for slashings when something 00:10:33.750 --> 00:10:36.920 align:start position:0% network or for slashings when something behaves<00:10:34.140> badly<00:10:35.780> okay 00:10:36.920 --> 00:10:36.930 align:start position:0% behaves badly okay 00:10:36.930 --> 00:10:39.200 align:start position:0% behaves badly okay and<00:10:37.170> now<00:10:37.470> again<00:10:38.280> here<00:10:38.490> I<00:10:38.520> would<00:10:38.940> like<00:10:39.090> to 00:10:39.200 --> 00:10:39.210 align:start position:0% and now again here I would like to 00:10:39.210 --> 00:10:41.240 align:start position:0% and now again here I would like to stress<00:10:39.300> out<00:10:39.570> it<00:10:39.750> if<00:10:40.350> you<00:10:40.530> have<00:10:40.710> a<00:10:40.740> lip<00:10:40.950> p2p 00:10:41.240 --> 00:10:41.250 align:start position:0% stress out it if you have a lip p2p 00:10:41.250 --> 00:10:44.210 align:start position:0% stress out it if you have a lip p2p implementation<00:10:41.880> you<00:10:42.870> don't<00:10:43.080> have<00:10:43.230> to<00:10:43.380> write<00:10:43.830> a 00:10:44.210 --> 00:10:44.220 align:start position:0% implementation you don't have to write a 00:10:44.220 --> 00:10:46.490 align:start position:0% implementation you don't have to write a full-blown<00:10:44.820> plant<00:10:45.300> you<00:10:45.570> can<00:10:45.720> just<00:10:45.990> implement 00:10:46.490 --> 00:10:46.500 align:start position:0% full-blown plant you can just implement 00:10:46.500 --> 00:10:49.340 align:start position:0% full-blown plant you can just implement an<00:10:46.980> SSD<00:10:47.760> decoder<00:10:48.270> and<00:10:48.480> you<00:10:48.690> can<00:10:48.870> tune<00:10:49.140> in<00:10:49.320> to 00:10:49.340 --> 00:10:49.350 align:start position:0% an SSD decoder and you can tune in to 00:10:49.350 --> 00:10:51.320 align:start position:0% an SSD decoder and you can tune in to the<00:10:49.710> gossips<00:10:50.160> of<00:10:50.280> traffic<00:10:50.700> and<00:10:51.000> start 00:10:51.320 --> 00:10:51.330 align:start position:0% the gossips of traffic and start 00:10:51.330 --> 00:10:56.270 align:start position:0% the gossips of traffic and start obtaining<00:10:51.810> useful<00:10:52.170> information<00:10:55.220> all<00:10:56.220> right 00:10:56.270 --> 00:10:56.280 align:start position:0% obtaining useful information all right 00:10:56.280 --> 00:11:00.950 align:start position:0% obtaining useful information all right but<00:10:56.610> now<00:10:57.300> that<00:10:57.480> after<00:10:57.780> we<00:10:58.080> have<00:10:58.260> connected<00:10:59.960> the 00:11:00.950 --> 00:11:00.960 align:start position:0% but now that after we have connected the 00:11:00.960 --> 00:11:02.770 align:start position:0% but now that after we have connected the p2p<00:11:01.200> goes<00:11:01.470> through<00:11:01.680> a<00:11:01.710> process<00:11:02.160> where<00:11:02.370> it 00:11:02.770 --> 00:11:02.780 align:start position:0% p2p goes through a process where it 00:11:02.780 --> 00:11:06.199 align:start position:0% p2p goes through a process where it negotiates<00:11:03.780> the<00:11:03.960> protocols<00:11:04.590> that 00:11:06.199 --> 00:11:06.209 align:start position:0% negotiates the protocols that 00:11:06.209 --> 00:11:08.929 align:start position:0% negotiates the protocols that can<00:11:06.420> use<00:11:07.319> and<00:11:07.740> to<00:11:08.009> exchange<00:11:08.189> messages<00:11:08.579> with 00:11:08.929 --> 00:11:08.939 align:start position:0% can use and to exchange messages with 00:11:08.939 --> 00:11:12.220 align:start position:0% can use and to exchange messages with the<00:11:08.970> other<00:11:09.149> clans<00:11:09.449> we<00:11:09.660> call<00:11:09.839> this<00:11:10.490> request 00:11:12.220 --> 00:11:12.230 align:start position:0% the other clans we call this request 00:11:12.230 --> 00:11:15.730 align:start position:0% the other clans we call this request response<00:11:13.230> kind<00:11:14.040> of<00:11:14.249> the<00:11:14.459> domain<00:11:14.819> of<00:11:14.850> the<00:11:15.029> spec 00:11:15.730 --> 00:11:15.740 align:start position:0% response kind of the domain of the spec 00:11:15.740 --> 00:11:18.710 align:start position:0% response kind of the domain of the spec and<00:11:16.740> it<00:11:17.040> so<00:11:17.610> far<00:11:17.790> it<00:11:17.939> involves<00:11:18.269> only<00:11:18.509> few 00:11:18.710 --> 00:11:18.720 align:start position:0% and it so far it involves only few 00:11:18.720 --> 00:11:20.989 align:start position:0% and it so far it involves only few requests<00:11:19.290> which<00:11:19.470> are<00:11:19.649> important<00:11:20.369> for<00:11:20.429> syncing 00:11:20.989 --> 00:11:20.999 align:start position:0% requests which are important for syncing 00:11:20.999 --> 00:11:23.720 align:start position:0% requests which are important for syncing the<00:11:21.179> beacon<00:11:21.540> chain<00:11:21.749> and<00:11:22.339> but<00:11:23.339> before<00:11:23.459> you 00:11:23.720 --> 00:11:23.730 align:start position:0% the beacon chain and but before you 00:11:23.730 --> 00:11:26.359 align:start position:0% the beacon chain and but before you start<00:11:23.790> with<00:11:24.149> this<00:11:25.040> when<00:11:26.040> you<00:11:26.129> connect<00:11:26.339> to 00:11:26.359 --> 00:11:26.369 align:start position:0% start with this when you connect to 00:11:26.369 --> 00:11:28.579 align:start position:0% start with this when you connect to another<00:11:26.519> node<00:11:26.879> you<00:11:27.329> start<00:11:27.839> by<00:11:28.259> exchanging 00:11:28.579 --> 00:11:28.589 align:start position:0% another node you start by exchanging 00:11:28.589 --> 00:11:31.220 align:start position:0% another node you start by exchanging your<00:11:29.160> status<00:11:29.579> information<00:11:29.759> with<00:11:30.629> this<00:11:31.019> node 00:11:31.220 --> 00:11:31.230 align:start position:0% your status information with this node 00:11:31.230 --> 00:11:34.790 align:start position:0% your status information with this node and<00:11:31.499> the<00:11:31.740> status<00:11:32.040> information<00:11:32.579> includes<00:11:33.800> four 00:11:34.790 --> 00:11:34.800 align:start position:0% and the status information includes four 00:11:34.800 --> 00:11:36.889 align:start position:0% and the status information includes four bytes<00:11:35.040> in<00:11:35.220> the<00:11:35.519> NT<00:11:35.699> fire<00:11:35.850> which<00:11:36.119> is<00:11:36.269> kind<00:11:36.779> of 00:11:36.889 --> 00:11:36.899 align:start position:0% bytes in the NT fire which is kind of 00:11:36.899 --> 00:11:38.989 align:start position:0% bytes in the NT fire which is kind of acts<00:11:37.050> as<00:11:37.259> a<00:11:37.290> marker<00:11:37.769> for<00:11:37.800> the<00:11:38.610> particular 00:11:38.989 --> 00:11:38.999 align:start position:0% acts as a marker for the particular 00:11:38.999 --> 00:11:40.790 align:start position:0% acts as a marker for the particular software<00:11:39.449> version<00:11:39.929> you<00:11:40.050> are<00:11:40.079> using<00:11:40.319> for 00:11:40.790 --> 00:11:40.800 align:start position:0% software version you are using for 00:11:40.800 --> 00:11:42.109 align:start position:0% software version you are using for example<00:11:41.160> you<00:11:41.220> can<00:11:41.369> imagine<00:11:41.550> if<00:11:41.759> there<00:11:41.879> was<00:11:41.939> a 00:11:42.109 --> 00:11:42.119 align:start position:0% example you can imagine if there was a 00:11:42.119 --> 00:11:45.590 align:start position:0% example you can imagine if there was a hard<00:11:42.629> fork<00:11:43.579> in<00:11:44.579> these<00:11:44.790> four<00:11:44.999> bytes<00:11:45.240> will<00:11:45.449> be 00:11:45.590 --> 00:11:45.600 align:start position:0% hard fork in these four bytes will be 00:11:45.600 --> 00:11:47.569 align:start position:0% hard fork in these four bytes will be modified<00:11:46.019> in<00:11:46.199> a<00:11:46.259> way<00:11:46.290> to<00:11:46.439> indicate<00:11:46.920> that<00:11:47.100> you 00:11:47.569 --> 00:11:47.579 align:start position:0% modified in a way to indicate that you 00:11:47.579 --> 00:11:49.220 align:start position:0% modified in a way to indicate that you are<00:11:47.670> now<00:11:47.819> following<00:11:48.209> different<00:11:48.689> rules<00:11:48.899> and 00:11:49.220 --> 00:11:49.230 align:start position:0% are now following different rules and 00:11:49.230 --> 00:11:51.739 align:start position:0% are now following different rules and you<00:11:50.129> can<00:11:50.339> also<00:11:50.490> be<00:11:50.759> on<00:11:50.879> a<00:11:50.910> different<00:11:51.089> network 00:11:51.739 --> 00:11:51.749 align:start position:0% you can also be on a different network 00:11:51.749 --> 00:11:54.290 align:start position:0% you can also be on a different network you<00:11:52.110> can<00:11:52.290> be<00:11:52.410> on<00:11:52.529> a<00:11:52.559> test<00:11:52.829> net<00:11:53.069> and<00:11:53.369> this<00:11:53.939> again 00:11:54.290 --> 00:11:54.300 align:start position:0% you can be on a test net and this again 00:11:54.300 --> 00:11:56.210 align:start position:0% you can be on a test net and this again will<00:11:54.480> be<00:11:54.629> written<00:11:54.809> in<00:11:55.079> this<00:11:55.199> form<00:11:55.589> right<00:11:56.069> in 00:11:56.210 --> 00:11:56.220 align:start position:0% will be written in this form right in 00:11:56.220 --> 00:11:59.090 align:start position:0% will be written in this form right in the<00:11:56.309> end<00:11:56.399> fire<00:11:56.699> and<00:11:57.769> the<00:11:58.769> other<00:11:58.889> piece 00:11:59.090 --> 00:11:59.100 align:start position:0% the end fire and the other piece 00:11:59.100 --> 00:12:01.340 align:start position:0% the end fire and the other piece information<00:11:59.309> that<00:11:59.790> this<00:11:59.910> exchange<00:12:00.179> is<00:12:00.509> what 00:12:01.340 --> 00:12:01.350 align:start position:0% information that this exchange is what 00:12:01.350 --> 00:12:03.230 align:start position:0% information that this exchange is what is<00:12:01.499> the<00:12:01.649> finalized<00:12:02.100> route<00:12:02.369> actually 00:12:03.230 --> 00:12:03.240 align:start position:0% is the finalized route actually 00:12:03.240 --> 00:12:05.090 align:start position:0% is the finalized route actually currently<00:12:03.929> working<00:12:04.110> on<00:12:04.319> and<00:12:04.589> what<00:12:04.709> is<00:12:04.889> your 00:12:05.090 --> 00:12:05.100 align:start position:0% currently working on and what is your 00:12:05.100 --> 00:12:07.429 align:start position:0% currently working on and what is your headlock<00:12:05.730> and<00:12:05.939> obviously<00:12:06.689> this<00:12:06.839> is<00:12:06.959> important 00:12:07.429 --> 00:12:07.439 align:start position:0% headlock and obviously this is important 00:12:07.439 --> 00:12:10.189 align:start position:0% headlock and obviously this is important because<00:12:07.589> it<00:12:08.490> allows<00:12:09.089> the<00:12:09.329> class<00:12:09.540> to<00:12:09.720> determine 00:12:10.189 --> 00:12:10.199 align:start position:0% because it allows the class to determine 00:12:10.199 --> 00:12:12.470 align:start position:0% because it allows the class to determine who<00:12:10.709> should<00:12:10.769> be<00:12:11.069> thinking<00:12:11.579> information<00:12:12.299> who 00:12:12.470 --> 00:12:12.480 align:start position:0% who should be thinking information who 00:12:12.480 --> 00:12:20.359 align:start position:0% who should be thinking information who is<00:12:12.769> right<00:12:13.769> I<00:12:13.799> have<00:12:14.160> much<00:12:14.730> quicker<00:12:19.249> all<00:12:20.249> right 00:12:20.359 --> 00:12:20.369 align:start position:0% is right I have much quicker all right 00:12:20.369 --> 00:12:23.419 align:start position:0% is right I have much quicker all right the<00:12:20.459> next<00:12:20.579> request<00:12:20.910> is<00:12:21.949> after<00:12:22.949> the<00:12:23.040> status 00:12:23.419 --> 00:12:23.429 align:start position:0% the next request is after the status 00:12:23.429 --> 00:12:24.679 align:start position:0% the next request is after the status message<00:12:23.519> tells<00:12:23.850> you<00:12:23.999> whether<00:12:24.209> you<00:12:24.389> have<00:12:24.569> to 00:12:24.679 --> 00:12:24.689 align:start position:0% message tells you whether you have to 00:12:24.689 --> 00:12:26.660 align:start position:0% message tells you whether you have to sync<00:12:24.929> so<00:12:25.139> the<00:12:25.259> next<00:12:25.439> request<00:12:25.769> is<00:12:25.949> your<00:12:26.399> request 00:12:26.660 --> 00:12:26.670 align:start position:0% sync so the next request is your request 00:12:26.670 --> 00:12:29.210 align:start position:0% sync so the next request is your request box<00:12:27.179> by<00:12:27.509> given<00:12:27.959> range<00:12:28.139> and<00:12:28.439> you<00:12:28.649> usually<00:12:28.889> do 00:12:29.210 --> 00:12:29.220 align:start position:0% box by given range and you usually do 00:12:29.220 --> 00:12:30.859 align:start position:0% box by given range and you usually do this<00:12:29.369> when<00:12:29.759> you<00:12:29.879> are<00:12:29.999> quite<00:12:30.540> a<00:12:30.569> bit<00:12:30.720> behind 00:12:30.859 --> 00:12:30.869 align:start position:0% this when you are quite a bit behind 00:12:30.869 --> 00:12:34.759 align:start position:0% this when you are quite a bit behind it's<00:12:31.410> intended<00:12:31.920> for<00:12:32.119> historic<00:12:33.119> blocks<00:12:33.769> and 00:12:34.759 --> 00:12:34.769 align:start position:0% it's intended for historic blocks and 00:12:34.769 --> 00:12:36.980 align:start position:0% it's intended for historic blocks and it's<00:12:35.339> optimized<00:12:35.850> in<00:12:35.970> a<00:12:36.029> way<00:12:36.179> that<00:12:36.389> the<00:12:36.660> clients 00:12:36.980 --> 00:12:36.990 align:start position:0% it's optimized in a way that the clients 00:12:36.990 --> 00:12:38.840 align:start position:0% it's optimized in a way that the clients will<00:12:37.079> be<00:12:37.199> able<00:12:37.350> to<00:12:37.529> implement<00:12:37.740> cold<00:12:38.429> storage 00:12:38.840 --> 00:12:38.850 align:start position:0% will be able to implement cold storage 00:12:38.850 --> 00:12:42.169 align:start position:0% will be able to implement cold storage of<00:12:39.119> the<00:12:39.299> beacon<00:12:39.629> chain<00:12:39.920> you<00:12:40.920> have<00:12:41.179> database 00:12:42.169 --> 00:12:42.179 align:start position:0% of the beacon chain you have database 00:12:42.179 --> 00:12:44.989 align:start position:0% of the beacon chain you have database with<00:12:42.389> random<00:12:42.720> access<00:12:43.110> and<00:12:43.379> the<00:12:44.040> range<00:12:44.279> queries 00:12:44.989 --> 00:12:44.999 align:start position:0% with random access and the range queries 00:12:44.999 --> 00:12:47.359 align:start position:0% with random access and the range queries are<00:12:45.269> supposed<00:12:46.079> to<00:12:46.259> hit<00:12:46.439> only<00:12:46.619> this<00:12:46.829> database 00:12:47.359 --> 00:12:47.369 align:start position:0% are supposed to hit only this database 00:12:47.369 --> 00:12:51.619 align:start position:0% are supposed to hit only this database of<00:12:47.639> cold<00:12:48.480> storage<00:12:48.869> for<00:12:49.139> historic<00:12:49.769> works<00:12:50.629> we 00:12:51.619 --> 00:12:51.629 align:start position:0% of cold storage for historic works we 00:12:51.629 --> 00:12:54.199 align:start position:0% of cold storage for historic works we also<00:12:51.809> have<00:12:52.170> a<00:12:52.529> way<00:12:52.860> to<00:12:52.920> request<00:12:53.339> recent<00:12:53.970> blocks 00:12:54.199 --> 00:12:54.209 align:start position:0% also have a way to request recent blocks 00:12:54.209 --> 00:12:56.389 align:start position:0% also have a way to request recent blocks which<00:12:54.600> is<00:12:54.809> you<00:12:55.230> request<00:12:55.589> them<00:12:55.740> by<00:12:55.889> their<00:12:56.129> hash 00:12:56.389 --> 00:12:56.399 align:start position:0% which is you request them by their hash 00:12:56.399 --> 00:12:58.850 align:start position:0% which is you request them by their hash what<00:12:57.089> you<00:12:57.329> would<00:12:57.720> usually<00:12:57.959> do<00:12:58.290> is<00:12:58.410> you<00:12:58.529> connect 00:12:58.850 --> 00:12:58.860 align:start position:0% what you would usually do is you connect 00:12:58.860 --> 00:13:00.230 align:start position:0% what you would usually do is you connect to<00:12:58.920> the<00:12:59.009> network<00:12:59.189> you<00:12:59.490> start<00:12:59.759> listening<00:12:59.970> to 00:13:00.230 --> 00:13:00.240 align:start position:0% to the network you start listening to 00:13:00.240 --> 00:13:01.910 align:start position:0% to the network you start listening to the<00:13:00.329> other<00:13:00.569> stations<00:13:01.110> you<00:13:01.410> notice<00:13:01.769> that 00:13:01.910 --> 00:13:01.920 align:start position:0% the other stations you notice that 00:13:01.920 --> 00:13:04.189 align:start position:0% the other stations you notice that certain<00:13:02.579> blocks<00:13:02.790> for<00:13:03.749> example<00:13:04.079> the 00:13:04.189 --> 00:13:04.199 align:start position:0% certain blocks for example the 00:13:04.199 --> 00:13:05.960 align:start position:0% certain blocks for example the attestation<00:13:04.559> is<00:13:04.920> referencing<00:13:05.459> a<00:13:05.610> block<00:13:05.819> that 00:13:05.960 --> 00:13:05.970 align:start position:0% attestation is referencing a block that 00:13:05.970 --> 00:13:08.239 align:start position:0% attestation is referencing a block that you<00:13:06.059> are<00:13:06.149> missing<00:13:06.299> so<00:13:07.170> you<00:13:07.230> will<00:13:07.589> request<00:13:07.889> in 00:13:08.239 --> 00:13:08.249 align:start position:0% you are missing so you will request in 00:13:08.249 --> 00:13:09.980 align:start position:0% you are missing so you will request in the<00:13:08.339> missing<00:13:08.579> ones<00:13:08.819> and<00:13:09.149> this<00:13:09.600> is<00:13:09.749> a<00:13:09.809> little 00:13:09.980 --> 00:13:09.990 align:start position:0% the missing ones and this is a little 00:13:09.990 --> 00:13:12.230 align:start position:0% the missing ones and this is a little bit<00:13:10.139> like<00:13:10.499> thinking<00:13:10.949> backwards<00:13:11.429> instead<00:13:12.029> of 00:13:12.230 --> 00:13:12.240 align:start position:0% bit like thinking backwards instead of 00:13:12.240 --> 00:13:18.379 align:start position:0% bit like thinking backwards instead of forward<00:13:14.329> all<00:13:15.329> right<00:13:16.579> I'll<00:13:17.579> just<00:13:17.639> then<00:13:18.029> finish 00:13:18.379 --> 00:13:18.389 align:start position:0% forward all right I'll just then finish 00:13:18.389 --> 00:13:18.870 align:start position:0% forward all right I'll just then finish with 00:13:18.870 --> 00:13:18.880 align:start position:0% with 00:13:18.880 --> 00:13:22.030 align:start position:0% with [Music] 00:13:22.030 --> 00:13:22.040 align:start position:0% [Music] 00:13:22.040 --> 00:13:24.500 align:start position:0% [Music] hearing<00:13:23.040> the<00:13:23.160> anti<00:13:23.400> I've<00:13:23.610> left<00:13:23.940> some<00:13:24.270> links 00:13:24.500 --> 00:13:24.510 align:start position:0% hearing the anti I've left some links 00:13:24.510 --> 00:13:27.260 align:start position:0% hearing the anti I've left some links for<00:13:25.320> anyone<00:13:25.740> who<00:13:26.040> wants<00:13:26.340> to<00:13:26.490> dig<00:13:26.700> deeper<00:13:27.090> in 00:13:27.260 --> 00:13:27.270 align:start position:0% for anyone who wants to dig deeper in 00:13:27.270 --> 00:13:30.830 align:start position:0% for anyone who wants to dig deeper in this<00:13:27.600> respect<00:13:28.080> that<00:13:28.230> I<00:13:28.380> have<00:13:28.410> discussed<00:13:29.840> and 00:13:30.830 --> 00:13:30.840 align:start position:0% this respect that I have discussed and 00:13:30.840 --> 00:13:33.290 align:start position:0% this respect that I have discussed and thank<00:13:31.380> you 00:13:33.290 --> 00:13:33.300 align:start position:0% thank you 00:13:33.300 --> 00:13:45.639 align:start position:0% thank you [Applause] 00:13:45.639 --> 00:13:45.649 align:start position:0% 00:13:45.649 --> 00:13:47.709 align:start position:0% you