WEBVTT Kind: captions Language: en 00:00:04.430 --> 00:00:07.789 align:start position:0% so<00:00:05.430> but<00:00:05.670> before<00:00:05.970> we<00:00:06.299> start<00:00:06.359> I'll<00:00:07.229> talk<00:00:07.769> a 00:00:07.789 --> 00:00:07.799 align:start position:0% so but before we start I'll talk a 00:00:07.799 --> 00:00:09.110 align:start position:0% so but before we start I'll talk a little<00:00:08.069> bit<00:00:08.219> about<00:00:08.250> what<00:00:08.580> we'll<00:00:08.730> go<00:00:08.969> over 00:00:09.110 --> 00:00:09.120 align:start position:0% little bit about what we'll go over 00:00:09.120 --> 00:00:11.360 align:start position:0% little bit about what we'll go over today<00:00:09.450> so<00:00:09.480> talk<00:00:10.469> about<00:00:10.680> a<00:00:10.709> little<00:00:10.830> bit<00:00:10.980> about 00:00:11.360 --> 00:00:11.370 align:start position:0% today so talk about a little bit about 00:00:11.370 --> 00:00:13.340 align:start position:0% today so talk about a little bit about who<00:00:11.580> we<00:00:11.610> are<00:00:11.850> at<00:00:12.510> white<00:00:12.750> black<00:00:12.959> and<00:00:12.990> what<00:00:13.230> our 00:00:13.340 --> 00:00:13.350 align:start position:0% who we are at white black and what our 00:00:13.350 --> 00:00:15.830 align:start position:0% who we are at white black and what our role<00:00:13.469> is<00:00:13.500> in<00:00:13.680> eath<00:00:13.949> two<00:00:14.570> challenges<00:00:15.570> to 00:00:15.830 --> 00:00:15.840 align:start position:0% role is in eath two challenges to 00:00:15.840 --> 00:00:19.310 align:start position:0% role is in eath two challenges to networking<00:00:16.470> and<00:00:16.740> eath<00:00:16.830> 2<00:00:17.359> we'll<00:00:18.359> go<00:00:18.539> over<00:00:18.690> a 00:00:19.310 --> 00:00:19.320 align:start position:0% networking and eath 2 we'll go over a 00:00:19.320 --> 00:00:21.680 align:start position:0% networking and eath 2 we'll go over a recap<00:00:20.039> of<00:00:20.070> the<00:00:20.370> Interop<00:00:20.790> lock-in<00:00:21.240> that<00:00:21.450> we<00:00:21.540> had 00:00:21.680 --> 00:00:21.690 align:start position:0% recap of the Interop lock-in that we had 00:00:21.690 --> 00:00:24.880 align:start position:0% recap of the Interop lock-in that we had in<00:00:21.900> September<00:00:22.440> and<00:00:23.430> what<00:00:23.640> our<00:00:23.730> role<00:00:23.910> was<00:00:24.060> there 00:00:24.880 --> 00:00:24.890 align:start position:0% in September and what our role was there 00:00:24.890 --> 00:00:28.490 align:start position:0% in September and what our role was there and<00:00:25.890> a<00:00:26.070> roadmap<00:00:26.280> as<00:00:26.760> well<00:00:27.450> as<00:00:27.630> a<00:00:27.660> Q&A<00:00:28.200> at<00:00:28.440> the 00:00:28.490 --> 00:00:28.500 align:start position:0% and a roadmap as well as a Q&A at the 00:00:28.500 --> 00:00:31.939 align:start position:0% and a roadmap as well as a Q&A at the end<00:00:28.619> so<00:00:29.930> white<00:00:30.930> block<00:00:31.170> is<00:00:31.410> a<00:00:31.440> team<00:00:31.920> of 00:00:31.939 --> 00:00:31.949 align:start position:0% end so white block is a team of 00:00:31.949 --> 00:00:34.660 align:start position:0% end so white block is a team of engineers<00:00:32.579> building<00:00:33.420> tools<00:00:34.079> to<00:00:34.410> test 00:00:34.660 --> 00:00:34.670 align:start position:0% engineers building tools to test 00:00:34.670 --> 00:00:35.810 align:start position:0% engineers building tools to test blockchains 00:00:35.810 --> 00:00:35.820 align:start position:0% blockchains 00:00:35.820 --> 00:00:37.849 align:start position:0% blockchains servitude<00:00:36.749> systems<00:00:37.109> protocols<00:00:37.530> what<00:00:37.710> have 00:00:37.849 --> 00:00:37.859 align:start position:0% servitude systems protocols what have 00:00:37.859 --> 00:00:39.950 align:start position:0% servitude systems protocols what have you<00:00:38.149> we<00:00:39.149> have<00:00:39.300> a<00:00:39.329> core<00:00:39.539> product<00:00:39.719> called 00:00:39.950 --> 00:00:39.960 align:start position:0% you we have a core product called 00:00:39.960 --> 00:00:42.079 align:start position:0% you we have a core product called Genesis<00:00:40.379> what<00:00:41.249> Genesis<00:00:41.640> you<00:00:41.760> can<00:00:41.879> fully 00:00:42.079 --> 00:00:42.089 align:start position:0% Genesis what Genesis you can fully 00:00:42.089 --> 00:00:44.090 align:start position:0% Genesis what Genesis you can fully automate<00:00:42.600> the<00:00:42.749> creation<00:00:42.899> and<00:00:43.469> deployment<00:00:43.649> of 00:00:44.090 --> 00:00:44.100 align:start position:0% automate the creation and deployment of 00:00:44.100 --> 00:00:47.029 align:start position:0% automate the creation and deployment of a<00:00:44.760> blockchain<00:00:45.120> you<00:00:45.659> can<00:00:45.839> configure<00:00:46.109> network 00:00:47.029 --> 00:00:47.039 align:start position:0% a blockchain you can configure network 00:00:47.039 --> 00:00:49.579 align:start position:0% a blockchain you can configure network topologies<00:00:48.079> deterministically<00:00:49.079> tests<00:00:49.499> how 00:00:49.579 --> 00:00:49.589 align:start position:0% topologies deterministically tests how 00:00:49.589 --> 00:00:52.340 align:start position:0% topologies deterministically tests how they'll<00:00:49.800> react<00:00:50.309> in<00:00:50.579> real<00:00:51.269> world<00:00:51.479> and<00:00:51.839> worst 00:00:52.340 --> 00:00:52.350 align:start position:0% they'll react in real world and worst 00:00:52.350 --> 00:00:54.590 align:start position:0% they'll react in real world and worst case<00:00:52.589> conditions<00:00:53.089> we<00:00:54.089> can<00:00:54.239> do<00:00:54.359> things<00:00:54.479> like 00:00:54.590 --> 00:00:54.600 align:start position:0% case conditions we can do things like 00:00:54.600 --> 00:00:57.439 align:start position:0% case conditions we can do things like implement<00:00:55.199> a<00:00:55.379> network<00:00:55.769> partition<00:00:56.339> to<00:00:57.210> force 00:00:57.439 --> 00:00:57.449 align:start position:0% implement a network partition to force 00:00:57.449 --> 00:00:58.729 align:start position:0% implement a network partition to force forking<00:00:57.839> events<00:00:58.170> and<00:00:58.350> see<00:00:58.469> how<00:00:58.620> your 00:00:58.729 --> 00:00:58.739 align:start position:0% forking events and see how your 00:00:58.739 --> 00:01:00.680 align:start position:0% forking events and see how your blockchain<00:00:59.100> will<00:00:59.280> react<00:00:59.549> and<00:00:59.789> reconciliate 00:01:00.680 --> 00:01:00.690 align:start position:0% blockchain will react and reconciliate 00:01:00.690 --> 00:01:02.959 align:start position:0% blockchain will react and reconciliate that<00:01:00.839> information<00:01:01.350> and<00:01:02.249> the<00:01:02.670> reason<00:01:02.789> why 00:01:02.959 --> 00:01:02.969 align:start position:0% that information and the reason why 00:01:02.969 --> 00:01:04.520 align:start position:0% that information and the reason why we're<00:01:03.120> talking<00:01:03.269> about<00:01:03.539> it<00:01:03.690> is<00:01:03.959> because<00:01:04.350> we 00:01:04.520 --> 00:01:04.530 align:start position:0% we're talking about it is because we 00:01:04.530 --> 00:01:06.190 align:start position:0% we're talking about it is because we will<00:01:04.650> use<00:01:04.680> its<00:01:05.010> functionality<00:01:05.549> to<00:01:05.790> test 00:01:06.190 --> 00:01:06.200 align:start position:0% will use its functionality to test 00:01:06.200 --> 00:01:10.340 align:start position:0% will use its functionality to test interoperability<00:01:07.200> and<00:01:07.500> eath<00:01:07.799> -<00:01:08.899> so<00:01:09.899> here<00:01:10.200> we 00:01:10.340 --> 00:01:10.350 align:start position:0% interoperability and eath - so here we 00:01:10.350 --> 00:01:12.850 align:start position:0% interoperability and eath - so here we have<00:01:10.530> everybody's<00:01:11.250> favorite<00:01:11.729> diagram<00:01:12.270> the 00:01:12.850 --> 00:01:12.860 align:start position:0% have everybody's favorite diagram the 00:01:12.860 --> 00:01:15.770 align:start position:0% have everybody's favorite diagram the networking<00:01:13.860> old<00:01:14.130> paradigm<00:01:14.520> right<00:01:14.759> so<00:01:15.390> sorry 00:01:15.770 --> 00:01:15.780 align:start position:0% networking old paradigm right so sorry 00:01:15.780 --> 00:01:17.899 align:start position:0% networking old paradigm right so sorry it's<00:01:16.079> a<00:01:16.170> little<00:01:16.200> messed<00:01:16.530> up<00:01:16.680> we<00:01:17.640> just 00:01:17.899 --> 00:01:17.909 align:start position:0% it's a little messed up we just 00:01:17.909 --> 00:01:20.209 align:start position:0% it's a little messed up we just downloaded<00:01:18.270> to<00:01:18.450> PowerPoint<00:01:18.930> and<00:01:19.619> didn't<00:01:20.130> have 00:01:20.209 --> 00:01:20.219 align:start position:0% downloaded to PowerPoint and didn't have 00:01:20.219 --> 00:01:22.969 align:start position:0% downloaded to PowerPoint and didn't have time<00:01:20.369> to<00:01:20.430> fix<00:01:20.700> this<00:01:20.880> but<00:01:21.450> we<00:01:22.229> so<00:01:22.710> you<00:01:22.770> have<00:01:22.950> a 00:01:22.969 --> 00:01:22.979 align:start position:0% time to fix this but we so you have a 00:01:22.979 --> 00:01:24.740 align:start position:0% time to fix this but we so you have a client<00:01:23.219> currying<00:01:23.820> server<00:01:24.060> for<00:01:24.329> information 00:01:24.740 --> 00:01:24.750 align:start position:0% client currying server for information 00:01:24.750 --> 00:01:26.779 align:start position:0% client currying server for information that<00:01:24.869> it<00:01:24.990> desires<00:01:25.320> server<00:01:26.100> acts<00:01:26.369> as<00:01:26.579> the 00:01:26.779 --> 00:01:26.789 align:start position:0% that it desires server acts as the 00:01:26.789 --> 00:01:28.910 align:start position:0% that it desires server acts as the centralized<00:01:27.270> point<00:01:27.479> of<00:01:27.630> truth<00:01:27.869> for<00:01:28.740> that 00:01:28.910 --> 00:01:28.920 align:start position:0% centralized point of truth for that 00:01:28.920 --> 00:01:31.190 align:start position:0% centralized point of truth for that information<00:01:29.299> right<00:01:30.299> everybody<00:01:30.719> knows<00:01:31.079> this 00:01:31.190 --> 00:01:31.200 align:start position:0% information right everybody knows this 00:01:31.200 --> 00:01:35.389 align:start position:0% information right everybody knows this model<00:01:31.500> that's<00:01:31.619> my<00:01:31.770> world<00:01:31.950> here<00:01:32.929> cool<00:01:33.929> so<00:01:34.399> then 00:01:35.389 --> 00:01:35.399 align:start position:0% model that's my world here cool so then 00:01:35.399 --> 00:01:37.010 align:start position:0% model that's my world here cool so then you<00:01:35.579> have<00:01:35.789> blockchain<00:01:36.270> networking<00:01:36.659> which<00:01:36.840> is 00:01:37.010 --> 00:01:37.020 align:start position:0% you have blockchain networking which is 00:01:37.020 --> 00:01:40.819 align:start position:0% you have blockchain networking which is very<00:01:37.799> very<00:01:38.789> difficult<00:01:39.509> you<00:01:40.289> have<00:01:40.320> a<00:01:40.530> bunch<00:01:40.770> of 00:01:40.819 --> 00:01:40.829 align:start position:0% very very difficult you have a bunch of 00:01:40.829 --> 00:01:42.349 align:start position:0% very very difficult you have a bunch of nodes<00:01:41.009> in<00:01:41.100> the<00:01:41.159> network<00:01:41.429> that<00:01:41.670> are<00:01:41.939> tasked 00:01:42.349 --> 00:01:42.359 align:start position:0% nodes in the network that are tasked 00:01:42.359 --> 00:01:44.959 align:start position:0% nodes in the network that are tasked with<00:01:42.530> challenge<00:01:43.530> to<00:01:43.740> communicate<00:01:44.280> over<00:01:44.820> a 00:01:44.959 --> 00:01:44.969 align:start position:0% with challenge to communicate over a 00:01:44.969 --> 00:01:47.389 align:start position:0% with challenge to communicate over a large<00:01:45.270> network<00:01:45.630> and<00:01:46.340> communicate<00:01:47.340> with 00:01:47.389 --> 00:01:47.399 align:start position:0% large network and communicate with 00:01:47.399 --> 00:01:50.719 align:start position:0% large network and communicate with unknown<00:01:47.789> peers<00:01:48.060> at<00:01:48.240> that<00:01:48.420> so<00:01:49.490> it<00:01:50.490> gets<00:01:50.670> pretty 00:01:50.719 --> 00:01:50.729 align:start position:0% unknown peers at that so it gets pretty 00:01:50.729 --> 00:01:53.569 align:start position:0% unknown peers at that so it gets pretty difficult<00:01:51.240> in<00:01:52.170> eath<00:01:52.439> to<00:01:52.649> specifically<00:01:53.159> this 00:01:53.569 --> 00:01:53.579 align:start position:0% difficult in eath to specifically this 00:01:53.579 --> 00:01:55.700 align:start position:0% difficult in eath to specifically this means<00:01:53.850> that<00:01:54.060> you<00:01:54.359> have<00:01:54.600> nodes<00:01:55.200> receiving 00:01:55.700 --> 00:01:55.710 align:start position:0% means that you have nodes receiving 00:01:55.710 --> 00:01:57.410 align:start position:0% means that you have nodes receiving messages<00:01:55.859> of<00:01:56.280> blocks<00:01:56.579> and<00:01:56.789> add<00:01:56.939> to<00:01:57.060> stations 00:01:57.410 --> 00:01:57.420 align:start position:0% messages of blocks and add to stations 00:01:57.420 --> 00:02:00.499 align:start position:0% messages of blocks and add to stations and<00:01:58.009> propagating<00:01:59.009> them<00:01:59.130> to<00:01:59.280> other<00:01:59.369> nodes<00:01:59.640> and 00:02:00.499 --> 00:02:00.509 align:start position:0% and propagating them to other nodes and 00:02:00.509 --> 00:02:01.730 align:start position:0% and propagating them to other nodes and they<00:02:00.659> do<00:02:00.719> this<00:02:00.990> over<00:02:01.259> an<00:02:01.319> asynchronous 00:02:01.730 --> 00:02:01.740 align:start position:0% they do this over an asynchronous 00:02:01.740 --> 00:02:03.739 align:start position:0% they do this over an asynchronous communication<00:02:02.069> pattern<00:02:02.789> called<00:02:03.060> gossip<00:02:03.329> sub 00:02:03.739 --> 00:02:03.749 align:start position:0% communication pattern called gossip sub 00:02:03.749 --> 00:02:04.969 align:start position:0% communication pattern called gossip sub and<00:02:03.899> we'll<00:02:04.049> talk<00:02:04.229> a<00:02:04.259> little<00:02:04.439> bit<00:02:04.649> more<00:02:04.679> about 00:02:04.969 --> 00:02:04.979 align:start position:0% and we'll talk a little bit more about 00:02:04.979 --> 00:02:06.499 align:start position:0% and we'll talk a little bit more about that<00:02:05.039> later 00:02:06.499 --> 00:02:06.509 align:start position:0% that later 00:02:06.509 --> 00:02:08.419 align:start position:0% that later so<00:02:06.840> nodes<00:02:07.079> will<00:02:07.170> receive<00:02:07.439> a<00:02:07.469> message<00:02:07.829> and<00:02:08.220> pass 00:02:08.419 --> 00:02:08.429 align:start position:0% so nodes will receive a message and pass 00:02:08.429 --> 00:02:10.669 align:start position:0% so nodes will receive a message and pass it<00:02:08.580> on<00:02:08.670> to<00:02:08.789> their<00:02:08.970> interested<00:02:09.450> peers<00:02:09.720> and<00:02:10.590> the 00:02:10.669 --> 00:02:10.679 align:start position:0% it on to their interested peers and the 00:02:10.679 --> 00:02:11.780 align:start position:0% it on to their interested peers and the idea<00:02:10.950> what<00:02:11.100> gossips 00:02:11.780 --> 00:02:11.790 align:start position:0% idea what gossips 00:02:11.790 --> 00:02:13.220 align:start position:0% idea what gossips is<00:02:11.849> that<00:02:12.180> a<00:02:12.390> message<00:02:12.780> will<00:02:12.930> efficiently 00:02:13.220 --> 00:02:13.230 align:start position:0% is that a message will efficiently 00:02:13.230 --> 00:02:14.839 align:start position:0% is that a message will efficiently propagate<00:02:13.769> throughout<00:02:14.010> the<00:02:14.280> network<00:02:14.430> once 00:02:14.839 --> 00:02:14.849 align:start position:0% propagate throughout the network once 00:02:14.849 --> 00:02:17.149 align:start position:0% propagate throughout the network once the<00:02:15.299> originating<00:02:15.870> node<00:02:16.019> broadcasts<00:02:16.709> it<00:02:16.799> out 00:02:17.149 --> 00:02:17.159 align:start position:0% the originating node broadcasts it out 00:02:17.159 --> 00:02:19.250 align:start position:0% the originating node broadcasts it out so<00:02:17.909> nodes<00:02:18.269> will<00:02:18.390> request<00:02:18.629> information<00:02:19.170> they 00:02:19.250 --> 00:02:19.260 align:start position:0% so nodes will request information they 00:02:19.260 --> 00:02:21.770 align:start position:0% so nodes will request information they don't<00:02:19.439> have<00:02:19.620> from<00:02:20.010> other<00:02:20.159> nodes<00:02:20.430> so<00:02:21.060> if<00:02:21.420> a<00:02:21.599> node 00:02:21.770 --> 00:02:21.780 align:start position:0% don't have from other nodes so if a node 00:02:21.780 --> 00:02:23.330 align:start position:0% don't have from other nodes so if a node has<00:02:21.810> adequate<00:02:22.319> resources<00:02:22.620> it<00:02:22.980> learns<00:02:23.129> of<00:02:23.250> a 00:02:23.330 --> 00:02:23.340 align:start position:0% has adequate resources it learns of a 00:02:23.340 --> 00:02:26.449 align:start position:0% has adequate resources it learns of a new<00:02:23.459> block<00:02:23.719> it<00:02:24.719> will<00:02:24.900> RPC<00:02:25.379> request<00:02:25.500> that<00:02:26.069> the 00:02:26.449 --> 00:02:26.459 align:start position:0% new block it will RPC request that the 00:02:26.459 --> 00:02:27.890 align:start position:0% new block it will RPC request that the block<00:02:26.670> or<00:02:26.909> the<00:02:27.090> node<00:02:27.239> that<00:02:27.420> has<00:02:27.480> that 00:02:27.890 --> 00:02:27.900 align:start position:0% block or the node that has that 00:02:27.900 --> 00:02:33.170 align:start position:0% block or the node that has that information<00:02:28.640> to<00:02:29.640> receive<00:02:30.000> it<00:02:31.250> cool<00:02:32.250> so<00:02:32.519> there 00:02:33.170 --> 00:02:33.180 align:start position:0% information to receive it cool so there 00:02:33.180 --> 00:02:35.420 align:start position:0% information to receive it cool so there are<00:02:33.239> a<00:02:33.269> lot<00:02:33.390> of<00:02:33.420> challenges<00:02:33.930> in<00:02:34.590> distributed 00:02:35.420 --> 00:02:35.430 align:start position:0% are a lot of challenges in distributed 00:02:35.430 --> 00:02:36.500 align:start position:0% are a lot of challenges in distributed networking 00:02:36.500 --> 00:02:36.510 align:start position:0% networking 00:02:36.510 --> 00:02:39.050 align:start position:0% networking I<00:02:36.569> don't<00:02:37.319> know<00:02:37.409> how<00:02:37.620> where<00:02:38.129> you<00:02:38.519> are<00:02:38.670> of<00:02:38.879> them 00:02:39.050 --> 00:02:39.060 align:start position:0% I don't know how where you are of them 00:02:39.060 --> 00:02:42.319 align:start position:0% I don't know how where you are of them but<00:02:39.239> when<00:02:39.359> we<00:02:39.569> listed<00:02:39.959> very<00:02:40.170> few<00:02:40.530> of<00:02:40.650> them<00:02:41.329> but 00:02:42.319 --> 00:02:42.329 align:start position:0% but when we listed very few of them but 00:02:42.329 --> 00:02:43.970 align:start position:0% but when we listed very few of them but we're<00:02:42.599> actively<00:02:42.780> at<00:02:43.260> web<00:02:43.409> block<00:02:43.560> looking<00:02:43.859> at 00:02:43.970 --> 00:02:43.980 align:start position:0% we're actively at web block looking at 00:02:43.980 --> 00:02:45.649 align:start position:0% we're actively at web block looking at these<00:02:44.129> challenges<00:02:44.700> along<00:02:45.000> with<00:02:45.060> eath<00:02:45.480> to 00:02:45.649 --> 00:02:45.659 align:start position:0% these challenges along with eath to 00:02:45.659 --> 00:02:47.599 align:start position:0% these challenges along with eath to client<00:02:46.019> teams<00:02:46.230> if<00:02:46.530> two<00:02:46.709> research<00:02:47.069> teams<00:02:47.370> and 00:02:47.599 --> 00:02:47.609 align:start position:0% client teams if two research teams and 00:02:47.609 --> 00:02:49.970 align:start position:0% client teams if two research teams and other<00:02:48.180> teams<00:02:48.480> in<00:02:48.629> the<00:02:48.720> space<00:02:48.930> looking<00:02:49.709> at<00:02:49.829> them 00:02:49.970 --> 00:02:49.980 align:start position:0% other teams in the space looking at them 00:02:49.980 --> 00:02:52.250 align:start position:0% other teams in the space looking at them so<00:02:50.579> there's<00:02:51.090> the<00:02:51.209> issue<00:02:51.329> of<00:02:51.480> peer<00:02:51.780> discovery 00:02:52.250 --> 00:02:52.260 align:start position:0% so there's the issue of peer discovery 00:02:52.260 --> 00:02:55.039 align:start position:0% so there's the issue of peer discovery how<00:02:53.010> do<00:02:53.069> you<00:02:53.939> as<00:02:54.060> a<00:02:54.090> node<00:02:54.359> find<00:02:54.780> two<00:02:54.930> other 00:02:55.039 --> 00:02:55.049 align:start position:0% how do you as a node find two other 00:02:55.049 --> 00:02:56.750 align:start position:0% how do you as a node find two other nodes<00:02:55.379> that<00:02:55.560> you<00:02:55.650> want<00:02:55.799> to<00:02:55.889> talk<00:02:56.069> to<00:02:56.220> in<00:02:56.459> a 00:02:56.750 --> 00:02:56.760 align:start position:0% nodes that you want to talk to in a 00:02:56.760 --> 00:02:59.449 align:start position:0% nodes that you want to talk to in a large<00:02:57.120> network<00:02:57.650> the<00:02:58.650> issue<00:02:58.829> of<00:02:59.010> distributed 00:02:59.449 --> 00:02:59.459 align:start position:0% large network the issue of distributed 00:02:59.459 --> 00:03:00.979 align:start position:0% large network the issue of distributed hash<00:02:59.609> tables<00:03:00.090> so<00:03:00.269> dhts 00:03:00.979 --> 00:03:00.989 align:start position:0% hash tables so dhts 00:03:00.989 --> 00:03:04.039 align:start position:0% hash tables so dhts how<00:03:01.739> do<00:03:01.799> you<00:03:02.120> store<00:03:03.120> information<00:03:03.299> about<00:03:03.750> those 00:03:04.039 --> 00:03:04.049 align:start position:0% how do you store information about those 00:03:04.049 --> 00:03:06.920 align:start position:0% how do you store information about those peers<00:03:04.319> in<00:03:04.530> the<00:03:04.859> network<00:03:05.540> there's<00:03:06.540> a<00:03:06.689> issue<00:03:06.810> of 00:03:06.920 --> 00:03:06.930 align:start position:0% peers in the network there's a issue of 00:03:06.930 --> 00:03:08.750 align:start position:0% peers in the network there's a issue of security<00:03:07.290> how<00:03:07.560> do<00:03:07.620> you<00:03:07.769> increase<00:03:08.220> tolerance 00:03:08.750 --> 00:03:08.760 align:start position:0% security how do you increase tolerance 00:03:08.760 --> 00:03:10.670 align:start position:0% security how do you increase tolerance to<00:03:08.909> certain<00:03:09.180> kinds<00:03:09.510> of<00:03:09.540> attacks<00:03:09.900> that<00:03:10.200> are 00:03:10.670 --> 00:03:10.680 align:start position:0% to certain kinds of attacks that are 00:03:10.680 --> 00:03:12.949 align:start position:0% to certain kinds of attacks that are prevalent<00:03:10.829> in<00:03:11.299> distributed<00:03:12.299> networks<00:03:12.599> like 00:03:12.949 --> 00:03:12.959 align:start position:0% prevalent in distributed networks like 00:03:12.959 --> 00:03:15.199 align:start position:0% prevalent in distributed networks like eucalyptus<00:03:13.349> attacks<00:03:13.620> what<00:03:13.799> have<00:03:13.950> you<00:03:14.209> the 00:03:15.199 --> 00:03:15.209 align:start position:0% eucalyptus attacks what have you the 00:03:15.209 --> 00:03:16.849 align:start position:0% eucalyptus attacks what have you the issue<00:03:15.419> of<00:03:15.840> block<00:03:16.409> and<00:03:16.560> attestation 00:03:16.849 --> 00:03:16.859 align:start position:0% issue of block and attestation 00:03:16.859 --> 00:03:19.580 align:start position:0% issue of block and attestation propagation<00:03:17.729> for<00:03:18.479> which<00:03:18.599> we<00:03:18.810> will<00:03:18.930> use<00:03:19.019> gossip 00:03:19.580 --> 00:03:19.590 align:start position:0% propagation for which we will use gossip 00:03:19.590 --> 00:03:21.050 align:start position:0% propagation for which we will use gossip so<00:03:19.739> again<00:03:20.129> we'll<00:03:20.430> talk<00:03:20.579> a<00:03:20.639> little<00:03:20.819> bit<00:03:20.940> more 00:03:21.050 --> 00:03:21.060 align:start position:0% so again we'll talk a little bit more 00:03:21.060 --> 00:03:23.750 align:start position:0% so again we'll talk a little bit more about<00:03:21.329> that<00:03:21.389> in<00:03:21.569> a<00:03:21.750> second<00:03:22.280> the<00:03:23.280> issue<00:03:23.400> of<00:03:23.609> loot 00:03:23.750 --> 00:03:23.760 align:start position:0% about that in a second the issue of loot 00:03:23.760 --> 00:03:25.250 align:start position:0% about that in a second the issue of loot nodes<00:03:23.970> in<00:03:24.090> the<00:03:24.180> network<00:03:24.479> which<00:03:24.780> are<00:03:24.930> points<00:03:25.169> of 00:03:25.250 --> 00:03:25.260 align:start position:0% nodes in the network which are points of 00:03:25.260 --> 00:03:27.080 align:start position:0% nodes in the network which are points of centralization<00:03:25.650> perceived<00:03:26.489> to<00:03:26.609> be<00:03:26.639> points<00:03:27.000> of 00:03:27.080 --> 00:03:27.090 align:start position:0% centralization perceived to be points of 00:03:27.090 --> 00:03:29.180 align:start position:0% centralization perceived to be points of weakness<00:03:27.650> issue<00:03:28.650> of<00:03:28.889> cryptographic 00:03:29.180 --> 00:03:29.190 align:start position:0% weakness issue of cryptographic 00:03:29.190 --> 00:03:31.339 align:start position:0% weakness issue of cryptographic verification<00:03:30.120> checking<00:03:30.810> to<00:03:30.930> make<00:03:30.959> sure<00:03:31.079> that 00:03:31.339 --> 00:03:31.349 align:start position:0% verification checking to make sure that 00:03:31.349 --> 00:03:34.909 align:start position:0% verification checking to make sure that signatures<00:03:31.859> are<00:03:32.010> valid<00:03:32.150> hashes<00:03:33.150> match<00:03:33.919> block 00:03:34.909 --> 00:03:34.919 align:start position:0% signatures are valid hashes match block 00:03:34.919 --> 00:03:37.099 align:start position:0% signatures are valid hashes match block information<00:03:35.519> and<00:03:35.879> then<00:03:36.659> the<00:03:36.810> issue<00:03:36.930> of 00:03:37.099 --> 00:03:37.109 align:start position:0% information and then the issue of 00:03:37.109 --> 00:03:40.189 align:start position:0% information and then the issue of syncing<00:03:37.560> so<00:03:38.220> how<00:03:38.639> do<00:03:38.699> you<00:03:39.049> how<00:03:40.049> do<00:03:40.109> you 00:03:40.189 --> 00:03:40.199 align:start position:0% syncing so how do you how do you 00:03:40.199 --> 00:03:41.960 align:start position:0% syncing so how do you how do you efficiently<00:03:40.620> sync<00:03:40.889> and<00:03:41.310> securely<00:03:41.669> sync 00:03:41.960 --> 00:03:41.970 align:start position:0% efficiently sync and securely sync 00:03:41.970 --> 00:03:44.000 align:start position:0% efficiently sync and securely sync information<00:03:42.569> against<00:03:42.930> other<00:03:43.500> nodes<00:03:43.769> in<00:03:43.919> the 00:03:44.000 --> 00:03:44.010 align:start position:0% information against other nodes in the 00:03:44.010 --> 00:03:47.300 align:start position:0% information against other nodes in the network<00:03:44.720> so<00:03:45.720> I'm<00:03:46.109> sure<00:03:46.349> that<00:03:46.680> you<00:03:46.859> guys<00:03:47.040> have 00:03:47.300 --> 00:03:47.310 align:start position:0% network so I'm sure that you guys have 00:03:47.310 --> 00:03:49.009 align:start position:0% network so I'm sure that you guys have already<00:03:47.519> had<00:03:47.849> like<00:03:48.030> your<00:03:48.239> ears<00:03:48.569> talked<00:03:48.870> off 00:03:49.009 --> 00:03:49.019 align:start position:0% already had like your ears talked off 00:03:49.019 --> 00:03:51.080 align:start position:0% already had like your ears talked off about<00:03:49.229> it<00:03:49.379> would<00:03:49.500> be<00:03:49.590> 2p<00:03:49.829> at<00:03:50.069> this<00:03:50.310> conference 00:03:51.080 --> 00:03:51.090 align:start position:0% about it would be 2p at this conference 00:03:51.090 --> 00:03:53.000 align:start position:0% about it would be 2p at this conference it's<00:03:51.479> been<00:03:51.629> like<00:03:51.780> a<00:03:51.810> super<00:03:52.079> hot<00:03:52.229> topic<00:03:52.560> at<00:03:52.769> Def 00:03:53.000 --> 00:03:53.010 align:start position:0% it's been like a super hot topic at Def 00:03:53.010 --> 00:03:55.250 align:start position:0% it's been like a super hot topic at Def Con<00:03:53.040> and<00:03:53.459> if<00:03:54.060> you<00:03:54.180> want<00:03:54.419> to<00:03:54.510> go<00:03:54.599> we're<00:03:55.079> only 00:03:55.250 --> 00:03:55.260 align:start position:0% Con and if you want to go we're only 00:03:55.260 --> 00:03:56.809 align:start position:0% Con and if you want to go we're only gonna<00:03:55.470> cover<00:03:55.680> it<00:03:55.829> briefly<00:03:56.099> but<00:03:56.340> if<00:03:56.430> you<00:03:56.489> want 00:03:56.809 --> 00:03:56.819 align:start position:0% gonna cover it briefly but if you want 00:03:56.819 --> 00:03:58.399 align:start position:0% gonna cover it briefly but if you want to<00:03:56.909> go<00:03:56.970> like<00:03:57.150> more<00:03:57.329> in<00:03:57.419> depth<00:03:57.659> about<00:03:57.780> it<00:03:58.109> roll 00:03:58.399 --> 00:03:58.409 align:start position:0% to go like more in depth about it roll 00:03:58.409 --> 00:04:01.250 align:start position:0% to go like more in depth about it roll Kripalani<00:03:58.889> from<00:03:59.189> the<00:03:59.340> p2p<00:03:59.659> did<00:04:00.659> it<00:04:00.780> talk<00:04:00.989> about 00:04:01.250 --> 00:04:01.260 align:start position:0% Kripalani from the p2p did it talk about 00:04:01.260 --> 00:04:02.839 align:start position:0% Kripalani from the p2p did it talk about gossip<00:04:01.620> sub<00:04:01.799> like<00:04:02.040> two<00:04:02.220> days<00:04:02.400> ago 00:04:02.839 --> 00:04:02.849 align:start position:0% gossip sub like two days ago 00:04:02.849 --> 00:04:04.670 align:start position:0% gossip sub like two days ago I'm<00:04:03.150> sure<00:04:03.419> the<00:04:03.750> slides<00:04:04.049> are<00:04:04.199> already<00:04:04.290> up<00:04:04.530> on 00:04:04.670 --> 00:04:04.680 align:start position:0% I'm sure the slides are already up on 00:04:04.680 --> 00:04:06.740 align:start position:0% I'm sure the slides are already up on Twitter<00:04:04.919> somewhere<00:04:05.310> and<00:04:05.609> the<00:04:06.269> video<00:04:06.510> will<00:04:06.629> be 00:04:06.740 --> 00:04:06.750 align:start position:0% Twitter somewhere and the video will be 00:04:06.750 --> 00:04:08.089 align:start position:0% Twitter somewhere and the video will be uploaded<00:04:06.959> but<00:04:07.229> he<00:04:07.349> did<00:04:07.500> a<00:04:07.530> really<00:04:07.709> good<00:04:07.919> deep 00:04:08.089 --> 00:04:08.099 align:start position:0% uploaded but he did a really good deep 00:04:08.099 --> 00:04:11.210 align:start position:0% uploaded but he did a really good deep dive<00:04:08.280> into<00:04:08.489> gossip<00:04:09.209> 7<00:04:09.689> but<00:04:10.139> we<00:04:10.259> will<00:04:10.470> we<00:04:11.099> will 00:04:11.210 --> 00:04:11.220 align:start position:0% dive into gossip 7 but we will we will 00:04:11.220 --> 00:04:13.069 align:start position:0% dive into gossip 7 but we will we will cover<00:04:11.400> just<00:04:11.519> like<00:04:11.819> very<00:04:12.239> basically<00:04:12.750> what 00:04:13.069 --> 00:04:13.079 align:start position:0% cover just like very basically what 00:04:13.079 --> 00:04:15.010 align:start position:0% cover just like very basically what gossip<00:04:13.799> sub<00:04:13.979> does<00:04:14.159> so<00:04:14.340> that<00:04:14.489> we<00:04:14.639> have<00:04:14.759> a 00:04:15.010 --> 00:04:15.020 align:start position:0% gossip sub does so that we have a 00:04:15.020 --> 00:04:17.410 align:start position:0% gossip sub does so that we have a to<00:04:15.230> start<00:04:15.440> off<00:04:15.590> at<00:04:15.770> so<00:04:16.489> gossip<00:04:16.940> sub<00:04:17.120> is<00:04:17.270> an 00:04:17.410 --> 00:04:17.420 align:start position:0% to start off at so gossip sub is an 00:04:17.420 --> 00:04:19.960 align:start position:0% to start off at so gossip sub is an epidemic<00:04:17.690> broadcast<00:04:18.320> protocol<00:04:18.850> it's<00:04:19.850> an 00:04:19.960 --> 00:04:19.970 align:start position:0% epidemic broadcast protocol it's an 00:04:19.970 --> 00:04:21.160 align:start position:0% epidemic broadcast protocol it's an implementation<00:04:20.540> of<00:04:20.600> a<00:04:20.690> pub/sub 00:04:21.160 --> 00:04:21.170 align:start position:0% implementation of a pub/sub 00:04:21.170 --> 00:04:23.560 align:start position:0% implementation of a pub/sub communication<00:04:22.040> pattern<00:04:22.340> and<00:04:22.550> it's<00:04:23.150> designed 00:04:23.560 --> 00:04:23.570 align:start position:0% communication pattern and it's designed 00:04:23.570 --> 00:04:25.330 align:start position:0% communication pattern and it's designed in<00:04:23.630> such<00:04:23.780> a<00:04:23.840> way<00:04:24.020> that<00:04:24.160> information<00:04:25.160> will 00:04:25.330 --> 00:04:25.340 align:start position:0% in such a way that information will 00:04:25.340 --> 00:04:27.910 align:start position:0% in such a way that information will efficiently<00:04:26.150> propagate<00:04:26.690> across<00:04:27.320> the<00:04:27.620> network 00:04:27.910 --> 00:04:27.920 align:start position:0% efficiently propagate across the network 00:04:27.920 --> 00:04:29.590 align:start position:0% efficiently propagate across the network so<00:04:28.430> nodes<00:04:28.610> will<00:04:28.790> listen<00:04:28.940> for<00:04:29.060> information 00:04:29.590 --> 00:04:29.600 align:start position:0% so nodes will listen for information 00:04:29.600 --> 00:04:31.870 align:start position:0% so nodes will listen for information that<00:04:29.630> they<00:04:29.870> want<00:04:30.110> and<00:04:30.800> pass<00:04:31.250> it<00:04:31.460> on<00:04:31.550> to<00:04:31.670> their 00:04:31.870 --> 00:04:31.880 align:start position:0% that they want and pass it on to their 00:04:31.880 --> 00:04:34.060 align:start position:0% that they want and pass it on to their peers<00:04:32.180> that<00:04:32.240> want<00:04:32.630> that<00:04:32.720> information<00:04:33.070> pattern 00:04:34.060 --> 00:04:34.070 align:start position:0% peers that want that information pattern 00:04:34.070 --> 00:04:35.560 align:start position:0% peers that want that information pattern will<00:04:34.190> continue<00:04:34.670> until<00:04:34.820> all<00:04:34.940> nodes<00:04:35.390> that<00:04:35.510> are 00:04:35.560 --> 00:04:35.570 align:start position:0% will continue until all nodes that are 00:04:35.570 --> 00:04:37.270 align:start position:0% will continue until all nodes that are interested<00:04:36.020> in<00:04:36.080> that<00:04:36.140> information<00:04:36.500> have 00:04:37.270 --> 00:04:37.280 align:start position:0% interested in that information have 00:04:37.280 --> 00:04:39.940 align:start position:0% interested in that information have received<00:04:37.610> it<00:04:37.790> and<00:04:38.000> in<00:04:38.330> the<00:04:38.450> network<00:04:38.720> so<00:04:39.020> gossip 00:04:39.940 --> 00:04:39.950 align:start position:0% received it and in the network so gossip 00:04:39.950 --> 00:04:42.010 align:start position:0% received it and in the network so gossip sub<00:04:40.130> is<00:04:40.280> an<00:04:40.580> efficient<00:04:41.060> protocol<00:04:41.840> for 00:04:42.010 --> 00:04:42.020 align:start position:0% sub is an efficient protocol for 00:04:42.020 --> 00:04:43.660 align:start position:0% sub is an efficient protocol for propagating<00:04:42.410> blocks<00:04:42.740> and<00:04:43.100> at<00:04:43.190> the<00:04:43.310> stations 00:04:43.660 --> 00:04:43.670 align:start position:0% propagating blocks and at the stations 00:04:43.670 --> 00:04:45.460 align:start position:0% propagating blocks and at the stations in<00:04:43.760> eath<00:04:43.910> too<00:04:44.120> which<00:04:44.630> is<00:04:44.750> why<00:04:44.780> it's<00:04:45.050> used<00:04:45.260> as 00:04:45.460 --> 00:04:45.470 align:start position:0% in eath too which is why it's used as 00:04:45.470 --> 00:04:48.340 align:start position:0% in eath too which is why it's used as the<00:04:45.650> eath<00:04:45.890> to<00:04:46.130> networking<00:04:46.520> stack<00:04:47.020> so<00:04:48.020> back<00:04:48.200> in 00:04:48.340 --> 00:04:48.350 align:start position:0% the eath to networking stack so back in 00:04:48.350 --> 00:04:50.260 align:start position:0% the eath to networking stack so back in april<00:04:48.620> we<00:04:48.740> actually<00:04:49.040> did<00:04:49.220> a<00:04:49.520> few<00:04:50.060> preliminary 00:04:50.260 --> 00:04:50.270 align:start position:0% april we actually did a few preliminary 00:04:50.270 --> 00:04:54.640 align:start position:0% april we actually did a few preliminary tests<00:04:51.050> on<00:04:51.200> the<00:04:51.530> PDP<00:04:52.120> and<00:04:53.120> they<00:04:53.570> were<00:04:53.630> not<00:04:54.170> so 00:04:54.640 --> 00:04:54.650 align:start position:0% tests on the PDP and they were not so 00:04:54.650 --> 00:04:57.220 align:start position:0% tests on the PDP and they were not so great<00:04:54.890> but<00:04:55.550> again<00:04:56.120> like<00:04:56.300> role<00:04:56.600> mentioned<00:04:57.080> that 00:04:57.220 --> 00:04:57.230 align:start position:0% great but again like role mentioned that 00:04:57.230 --> 00:04:59.470 align:start position:0% great but again like role mentioned that flip<00:04:57.710> p2p<00:04:58.130> is<00:04:58.220> in<00:04:58.370> alpha<00:04:58.700> mode<00:04:58.730> right<00:04:59.030> now<00:04:59.090> so 00:04:59.470 --> 00:04:59.480 align:start position:0% flip p2p is in alpha mode right now so 00:04:59.480 --> 00:05:00.580 align:start position:0% flip p2p is in alpha mode right now so there<00:04:59.750> are<00:04:59.840> a<00:04:59.900> lot<00:05:00.050> of<00:05:00.080> parts<00:05:00.380> of<00:05:00.440> it<00:05:00.530> that 00:05:00.580 --> 00:05:00.590 align:start position:0% there are a lot of parts of it that 00:05:00.590 --> 00:05:02.890 align:start position:0% there are a lot of parts of it that still<00:05:00.890> need<00:05:01.040> to<00:05:01.100> be<00:05:01.220> like<00:05:01.370> massaged<00:05:02.240> and<00:05:02.600> and 00:05:02.890 --> 00:05:02.900 align:start position:0% still need to be like massaged and and 00:05:02.900 --> 00:05:05.410 align:start position:0% still need to be like massaged and and improved<00:05:03.320> to<00:05:03.500> make<00:05:03.530> sure<00:05:03.830> that<00:05:04.070> it's<00:05:04.940> going<00:05:05.330> to 00:05:05.410 --> 00:05:05.420 align:start position:0% improved to make sure that it's going to 00:05:05.420 --> 00:05:07.330 align:start position:0% improved to make sure that it's going to be<00:05:05.540> ready<00:05:05.690> for<00:05:05.930> Phase<00:05:06.680> II<00:05:06.710> our<00:05:06.950> launch 00:05:07.330 --> 00:05:07.340 align:start position:0% be ready for Phase II our launch 00:05:07.340 --> 00:05:10.060 align:start position:0% be ready for Phase II our launch so<00:05:08.230> we<00:05:09.230> at<00:05:09.350> white<00:05:09.500> block<00:05:09.650> will<00:05:09.800> actually 00:05:10.060 --> 00:05:10.070 align:start position:0% so we at white block will actually 00:05:10.070 --> 00:05:12.820 align:start position:0% so we at white block will actually continue<00:05:10.340> testing<00:05:10.880> and<00:05:11.000> auditing<00:05:11.360> the<00:05:12.230> p2p<00:05:12.500> to 00:05:12.820 --> 00:05:12.830 align:start position:0% continue testing and auditing the p2p to 00:05:12.830 --> 00:05:16.740 align:start position:0% continue testing and auditing the p2p to ensure<00:05:13.220> that<00:05:13.250> it<00:05:13.730> will<00:05:13.960> be<00:05:14.960> ready<00:05:15.110> for<00:05:15.410> a 00:05:16.740 --> 00:05:16.750 align:start position:0% ensure that it will be ready for a 00:05:16.750 --> 00:05:21.550 align:start position:0% ensure that it will be ready for a successful<00:05:17.750> phaser<00:05:19.870> and<00:05:20.870> I'm<00:05:20.960> gonna<00:05:21.440> talk 00:05:21.550 --> 00:05:21.560 align:start position:0% successful phaser and I'm gonna talk 00:05:21.560 --> 00:05:25.110 align:start position:0% successful phaser and I'm gonna talk about<00:05:21.620> that 00:05:25.110 --> 00:05:25.120 align:start position:0% 00:05:25.120 --> 00:05:30.520 align:start position:0% thanks<00:05:26.120> for<00:05:26.210> me<00:05:26.800> so<00:05:28.930> why<00:05:29.930> are<00:05:29.990> we<00:05:30.050> testing<00:05:30.260> us 00:05:30.520 --> 00:05:30.530 align:start position:0% thanks for me so why are we testing us 00:05:30.530 --> 00:05:32.470 align:start position:0% thanks for me so why are we testing us observe<00:05:30.860> right<00:05:31.040> so<00:05:31.280> the<00:05:31.610> point<00:05:31.880> of<00:05:32.060> this<00:05:32.210> is<00:05:32.450> to 00:05:32.470 --> 00:05:32.480 align:start position:0% observe right so the point of this is to 00:05:32.480 --> 00:05:34.150 align:start position:0% observe right so the point of this is to really<00:05:32.900> assess<00:05:33.470> the<00:05:33.710> real-world<00:05:33.890> performance 00:05:34.150 --> 00:05:34.160 align:start position:0% really assess the real-world performance 00:05:34.160 --> 00:05:38.080 align:start position:0% really assess the real-world performance of<00:05:35.290> gossip<00:05:36.290> sub<00:05:36.500> under<00:05:37.280> very<00:05:38.030> adverse 00:05:38.080 --> 00:05:38.090 align:start position:0% of gossip sub under very adverse 00:05:38.090 --> 00:05:42.450 align:start position:0% of gossip sub under very adverse conditions<00:05:38.870> dropping<00:05:39.740> gears<00:05:40.450> bad<00:05:41.450> bandwidth 00:05:42.450 --> 00:05:42.460 align:start position:0% conditions dropping gears bad bandwidth 00:05:42.460 --> 00:05:45.820 align:start position:0% conditions dropping gears bad bandwidth packet<00:05:43.460> loss<00:05:43.990> huge<00:05:44.990> latency<00:05:45.470> between<00:05:45.560> the 00:05:45.820 --> 00:05:45.830 align:start position:0% packet loss huge latency between the 00:05:45.830 --> 00:05:49.240 align:start position:0% packet loss huge latency between the nodes<00:05:46.210> knowing<00:05:47.210> that<00:05:47.420> in<00:05:48.410> the<00:05:48.530> case<00:05:48.710> of<00:05:48.740> if<00:05:49.010> - 00:05:49.240 --> 00:05:49.250 align:start position:0% nodes knowing that in the case of if - 00:05:49.250 --> 00:05:52.840 align:start position:0% nodes knowing that in the case of if - we<00:05:49.790> have<00:05:50.050> 6<00:05:51.050> seconds<00:05:51.380> per<00:05:51.590> block<00:05:51.830> so<00:05:52.580> if<00:05:52.760> you 00:05:52.840 --> 00:05:52.850 align:start position:0% we have 6 seconds per block so if you 00:05:52.850 --> 00:05:54.460 align:start position:0% we have 6 seconds per block so if you want<00:05:53.030> to<00:05:53.090> really<00:05:53.330> gossip<00:05:53.720> everything<00:05:54.170> you 00:05:54.460 --> 00:05:54.470 align:start position:0% want to really gossip everything you 00:05:54.470 --> 00:05:56.260 align:start position:0% want to really gossip everything you would<00:05:54.590> want<00:05:54.650> to<00:05:54.980> have<00:05:55.130> 3<00:05:55.460> seconds<00:05:55.790> to<00:05:55.940> go<00:05:56.060> sip 00:05:56.260 --> 00:05:56.270 align:start position:0% would want to have 3 seconds to go sip 00:05:56.270 --> 00:05:58.480 align:start position:0% would want to have 3 seconds to go sip the<00:05:56.420> whole<00:05:56.660> information<00:05:57.470> between<00:05:58.130> all<00:05:58.370> the 00:05:58.480 --> 00:05:58.490 align:start position:0% the whole information between all the 00:05:58.490 --> 00:06:00.520 align:start position:0% the whole information between all the peers<00:05:58.850> so<00:05:59.240> they<00:05:59.390> can<00:05:59.540> decide<00:05:59.960> and<00:06:00.200> start 00:06:00.520 --> 00:06:00.530 align:start position:0% peers so they can decide and start 00:06:00.530 --> 00:06:04.420 align:start position:0% peers so they can decide and start voting<00:06:00.740> correctly<00:06:01.520> on<00:06:01.850> the<00:06:02.180> new<00:06:02.390> block<00:06:03.430> one 00:06:04.420 --> 00:06:04.430 align:start position:0% voting correctly on the new block one 00:06:04.430 --> 00:06:06.940 align:start position:0% voting correctly on the new block one thing<00:06:04.640> that<00:06:04.820> we<00:06:05.600> can<00:06:05.720> reach<00:06:05.900> week<00:06:06.200> during<00:06:06.680> that 00:06:06.940 --> 00:06:06.950 align:start position:0% thing that we can reach week during that 00:06:06.950 --> 00:06:08.110 align:start position:0% thing that we can reach week during that testing<00:06:07.340> is<00:06:07.550> a<00:06:07.610> different<00:06:08.000> network 00:06:08.110 --> 00:06:08.120 align:start position:0% testing is a different network 00:06:08.120 --> 00:06:10.900 align:start position:0% testing is a different network topologies<00:06:08.750> so<00:06:09.169> if<00:06:09.680> you<00:06:09.800> went<00:06:09.980> to<00:06:10.160> Randall's 00:06:10.900 --> 00:06:10.910 align:start position:0% topologies so if you went to Randall's 00:06:10.910 --> 00:06:13.000 align:start position:0% topologies so if you went to Randall's talk<00:06:11.120> he<00:06:11.720> said<00:06:11.960> that<00:06:12.140> you<00:06:12.410> have<00:06:12.560> a<00:06:12.590> minimum<00:06:12.830> of 00:06:13.000 --> 00:06:13.010 align:start position:0% talk he said that you have a minimum of 00:06:13.010 --> 00:06:15.730 align:start position:0% talk he said that you have a minimum of 4<00:06:13.250> peers<00:06:13.580> a<00:06:13.669> maximum<00:06:14.120> of<00:06:14.180> 12<00:06:14.480> is<00:06:15.140> that<00:06:15.440> really 00:06:15.730 --> 00:06:15.740 align:start position:0% 4 peers a maximum of 12 is that really 00:06:15.740 --> 00:06:17.380 align:start position:0% 4 peers a maximum of 12 is that really what<00:06:15.919> we<00:06:16.040> want<00:06:16.220> to<00:06:16.340> go<00:06:16.430> for<00:06:16.700> should<00:06:16.940> we<00:06:17.030> have 00:06:17.380 --> 00:06:17.390 align:start position:0% what we want to go for should we have 00:06:17.390 --> 00:06:19.870 align:start position:0% what we want to go for should we have more<00:06:17.690> peers<00:06:17.990> we<00:06:18.230> have<00:06:18.440> a<00:06:18.680> few<00:06:19.340> better<00:06:19.550> peers 00:06:19.870 --> 00:06:19.880 align:start position:0% more peers we have a few better peers 00:06:19.880 --> 00:06:21.970 align:start position:0% more peers we have a few better peers should<00:06:20.240> we<00:06:20.330> start<00:06:20.630> working<00:06:21.290> a<00:06:21.470> little<00:06:21.620> bit<00:06:21.800> on 00:06:21.970 --> 00:06:21.980 align:start position:0% should we start working a little bit on 00:06:21.980 --> 00:06:23.710 align:start position:0% should we start working a little bit on some<00:06:22.010> of<00:06:22.250> the<00:06:22.550> working<00:06:23.270> wants<00:06:23.450> to<00:06:23.510> do<00:06:23.600> for 00:06:23.710 --> 00:06:23.720 align:start position:0% some of the working wants to do for 00:06:23.720 --> 00:06:25.120 align:start position:0% some of the working wants to do for episode<00:06:24.140> where<00:06:24.410> we're<00:06:24.800> going<00:06:24.979> to<00:06:25.100> have 00:06:25.120 --> 00:06:25.130 align:start position:0% episode where we're going to have 00:06:25.130 --> 00:06:27.070 align:start position:0% episode where we're going to have optimizations<00:06:25.940> where<00:06:26.210> we're<00:06:26.750> going<00:06:26.930> to 00:06:27.070 --> 00:06:27.080 align:start position:0% optimizations where we're going to 00:06:27.080 --> 00:06:28.960 align:start position:0% optimizations where we're going to prefer<00:06:27.260> nodes<00:06:27.680> which<00:06:27.830> are<00:06:27.950> closer<00:06:28.190> to<00:06:28.430> us 00:06:28.960 --> 00:06:28.970 align:start position:0% prefer nodes which are closer to us 00:06:28.970 --> 00:06:31.450 align:start position:0% prefer nodes which are closer to us which<00:06:29.540> have<00:06:29.720> lower<00:06:29.990> latency<00:06:30.530> which<00:06:31.160> are<00:06:31.310> more 00:06:31.450 --> 00:06:31.460 align:start position:0% which have lower latency which are more 00:06:31.460 --> 00:06:33.840 align:start position:0% which have lower latency which are more responsive<00:06:32.000> we're<00:06:32.570> going<00:06:32.750> to<00:06:32.840> look<00:06:32.990> into<00:06:33.140> that 00:06:33.840 --> 00:06:33.850 align:start position:0% responsive we're going to look into that 00:06:33.850 --> 00:06:37.150 align:start position:0% responsive we're going to look into that so<00:06:34.850> to<00:06:34.910> get<00:06:35.720> to<00:06:35.780> work<00:06:36.020> first<00:06:36.770> thing<00:06:36.920> we<00:06:37.010> need<00:06:37.130> is 00:06:37.150 --> 00:06:37.160 align:start position:0% so to get to work first thing we need is 00:06:37.160 --> 00:06:39.280 align:start position:0% so to get to work first thing we need is when<00:06:37.550> we<00:06:37.670> did<00:06:37.790> our<00:06:37.850> past<00:06:38.090> name<00:06:38.300> Pro<00:06:38.540> we<00:06:38.750> used<00:06:39.110> to 00:06:39.280 --> 00:06:39.290 align:start position:0% when we did our past name Pro we used to 00:06:39.290 --> 00:06:42.430 align:start position:0% when we did our past name Pro we used to go<00:06:39.770> to<00:06:39.800> p2p<00:06:40.280> demon<00:06:40.750> this<00:06:41.750> time<00:06:41.810> we're<00:06:42.140> starting 00:06:42.430 --> 00:06:42.440 align:start position:0% go to p2p demon this time we're starting 00:06:42.440 --> 00:06:44.560 align:start position:0% go to p2p demon this time we're starting from<00:06:42.560> scratch<00:06:42.770> with<00:06:43.130> a<00:06:43.670> company<00:06:44.090> called<00:06:44.120> the 00:06:44.560 --> 00:06:44.570 align:start position:0% from scratch with a company called the 00:06:44.570 --> 00:06:48.070 align:start position:0% from scratch with a company called the agency<00:06:45.080> Enterprise<00:06:45.980> and<00:06:46.760> they're<00:06:47.660> really 00:06:48.070 --> 00:06:48.080 align:start position:0% agency Enterprise and they're really 00:06:48.080 --> 00:06:49.090 align:start position:0% agency Enterprise and they're really great<00:06:48.230> they<00:06:48.380> work<00:06:48.530> very<00:06:48.740> closely<00:06:48.980> with 00:06:49.090 --> 00:06:49.100 align:start position:0% great they work very closely with 00:06:49.100 --> 00:06:51.160 align:start position:0% great they work very closely with protocol<00:06:49.550> labs<00:06:49.790> so<00:06:50.180> Adam<00:06:50.540> Hannah<00:06:50.750> has<00:06:51.020> been 00:06:51.160 --> 00:06:51.170 align:start position:0% protocol labs so Adam Hannah has been 00:06:51.170 --> 00:06:53.230 align:start position:0% protocol labs so Adam Hannah has been building<00:06:51.530> a<00:06:51.590> leap<00:06:51.980> PGP<00:06:52.310> client<00:06:52.670> which<00:06:53.210> is 00:06:53.230 --> 00:06:53.240 align:start position:0% building a leap PGP client which is 00:06:53.240 --> 00:06:56.920 align:start position:0% building a leap PGP client which is based<00:06:53.660> on<00:06:53.870> the<00:06:54.080> Goldie<00:06:54.380> p2p<00:06:54.800> core<00:06:55.160> library<00:06:55.930> and 00:06:56.920 --> 00:06:56.930 align:start position:0% based on the Goldie p2p core library and 00:06:56.930 --> 00:06:59.080 align:start position:0% based on the Goldie p2p core library and it's<00:06:57.380> a<00:06:57.470> very<00:06:57.650> simple<00:06:57.830> client<00:06:58.070> that<00:06:58.280> just<00:06:58.490> is 00:06:59.080 --> 00:06:59.090 align:start position:0% it's a very simple client that just is 00:06:59.090 --> 00:07:00.640 align:start position:0% it's a very simple client that just is going<00:06:59.300> to<00:06:59.420> output<00:06:59.780> a<00:06:59.840> bunch<00:07:00.170> of<00:07:00.290> metadata 00:07:00.640 --> 00:07:00.650 align:start position:0% going to output a bunch of metadata 00:07:00.650 --> 00:07:02.620 align:start position:0% going to output a bunch of metadata information<00:07:01.010> about<00:07:01.520> the<00:07:01.820> message<00:07:02.210> right<00:07:02.390> when 00:07:02.620 --> 00:07:02.630 align:start position:0% information about the message right when 00:07:02.630 --> 00:07:05.100 align:start position:0% information about the message right when was<00:07:02.810> it<00:07:02.960> sent<00:07:03.200> who<00:07:03.830> sent<00:07:04.100> it<00:07:04.280> who<00:07:04.580> is<00:07:04.700> it<00:07:04.730> for 00:07:05.100 --> 00:07:05.110 align:start position:0% was it sent who sent it who is it for 00:07:05.110 --> 00:07:08.680 align:start position:0% was it sent who sent it who is it for how<00:07:06.110> many<00:07:06.170> hops<00:07:06.950> DC<00:07:07.520> for<00:07:07.790> that<00:07:07.880> message 00:07:08.680 --> 00:07:08.690 align:start position:0% how many hops DC for that message 00:07:08.690 --> 00:07:10.710 align:start position:0% how many hops DC for that message you<00:07:09.530> know<00:07:09.620> how<00:07:09.770> long<00:07:09.860> has<00:07:09.980> it<00:07:10.010> been<00:07:10.130> around 00:07:10.710 --> 00:07:10.720 align:start position:0% you know how long has it been around 00:07:10.720 --> 00:07:13.300 align:start position:0% you know how long has it been around what<00:07:11.720> type<00:07:11.900> of<00:07:11.930> like<00:07:12.410> how<00:07:12.620> long<00:07:12.680> was<00:07:12.980> the<00:07:13.130> hop 00:07:13.300 --> 00:07:13.310 align:start position:0% what type of like how long was the hop 00:07:13.310 --> 00:07:16.000 align:start position:0% what type of like how long was the hop between<00:07:13.550> those<00:07:13.850> different<00:07:13.970> peers<00:07:14.860> we<00:07:15.860> also 00:07:16.000 --> 00:07:16.010 align:start position:0% between those different peers we also 00:07:16.010 --> 00:07:19.120 align:start position:0% between those different peers we also hired<00:07:16.910> an<00:07:17.120> academic<00:07:17.870> on<00:07:18.200> our<00:07:18.320> team<00:07:18.560> who<00:07:18.890> is<00:07:19.010> now 00:07:19.120 --> 00:07:19.130 align:start position:0% hired an academic on our team who is now 00:07:19.130 --> 00:07:21.610 align:start position:0% hired an academic on our team who is now doing<00:07:19.430> a<00:07:19.670> literature<00:07:20.180> review<00:07:20.270> to<00:07:21.140> look<00:07:21.350> at<00:07:21.530> the 00:07:21.610 --> 00:07:21.620 align:start position:0% doing a literature review to look at the 00:07:21.620 --> 00:07:23.530 align:start position:0% doing a literature review to look at the different<00:07:21.950> topologies<00:07:22.430> everything<00:07:23.360> should 00:07:23.530 --> 00:07:23.540 align:start position:0% different topologies everything should 00:07:23.540 --> 00:07:26.500 align:start position:0% different topologies everything should be<00:07:23.570> done<00:07:23.810> there<00:07:24.370> namely<00:07:25.370> right<00:07:25.670> now<00:07:25.850> I'd<00:07:26.450> like 00:07:26.500 --> 00:07:26.510 align:start position:0% be done there namely right now I'd like 00:07:26.510 --> 00:07:29.020 align:start position:0% be done there namely right now I'd like to<00:07:26.630> try<00:07:26.930> also<00:07:27.140> to<00:07:27.350> do<00:07:27.650> some<00:07:27.860> discovery 00:07:29.020 --> 00:07:29.030 align:start position:0% to try also to do some discovery 00:07:29.030 --> 00:07:31.630 align:start position:0% to try also to do some discovery you<00:07:29.990> know<00:07:30.050> associations<00:07:30.620> so<00:07:31.250> we<00:07:31.370> can<00:07:31.520> do 00:07:31.630 --> 00:07:31.640 align:start position:0% you know associations so we can do 00:07:31.640 --> 00:07:33.760 align:start position:0% you know associations so we can do academia<00:07:32.090> approach<00:07:32.390> to<00:07:32.750> just<00:07:33.020> let<00:07:33.650> the 00:07:33.760 --> 00:07:33.770 align:start position:0% academia approach to just let the 00:07:33.770 --> 00:07:36.340 align:start position:0% academia approach to just let the network<00:07:34.100> self<00:07:34.310> organize<00:07:34.640> but<00:07:35.510> it<00:07:35.870> might 00:07:36.340 --> 00:07:36.350 align:start position:0% network self organize but it might 00:07:36.350 --> 00:07:38.230 align:start position:0% network self organize but it might actually<00:07:36.530> not<00:07:36.890> be<00:07:36.950> the<00:07:37.280> best<00:07:37.400> way<00:07:37.670> to<00:07:37.910> organize 00:07:38.230 --> 00:07:38.240 align:start position:0% actually not be the best way to organize 00:07:38.240 --> 00:07:40.690 align:start position:0% actually not be the best way to organize appears<00:07:38.780> so<00:07:39.080> we're<00:07:39.950> testing<00:07:40.280> nozzles<00:07:40.580> at 00:07:40.690 --> 00:07:40.700 align:start position:0% appears so we're testing nozzles at 00:07:40.700 --> 00:07:43.630 align:start position:0% appears so we're testing nozzles at different<00:07:40.910> aspects<00:07:41.710> so<00:07:42.710> talking<00:07:43.610> about 00:07:43.630 --> 00:07:43.640 align:start position:0% different aspects so talking about 00:07:43.640 --> 00:07:45.190 align:start position:0% different aspects so talking about network<00:07:43.910> topologies<00:07:44.480> we're<00:07:44.690> going<00:07:44.810> to<00:07:44.930> strain 00:07:45.190 --> 00:07:45.200 align:start position:0% network topologies we're going to strain 00:07:45.200 --> 00:07:46.720 align:start position:0% network topologies we're going to strain it<00:07:45.230> or<00:07:45.500> gain<00:07:45.620> credit<00:07:45.920> sequence<00:07:46.250> of<00:07:46.400> peers 00:07:46.720 --> 00:07:46.730 align:start position:0% it or gain credit sequence of peers 00:07:46.730 --> 00:07:48.520 align:start position:0% it or gain credit sequence of peers we're<00:07:47.060> going<00:07:47.210> to<00:07:47.390> create<00:07:47.630> a<00:07:47.870> mesh<00:07:48.110> of<00:07:48.260> tears 00:07:48.520 --> 00:07:48.530 align:start position:0% we're going to create a mesh of tears 00:07:48.530 --> 00:07:50.890 align:start position:0% we're going to create a mesh of tears just<00:07:48.860> like<00:07:49.120> redundant<00:07:50.120> hubs<00:07:50.330> between<00:07:50.780> each 00:07:50.890 --> 00:07:50.900 align:start position:0% just like redundant hubs between each 00:07:50.900 --> 00:07:52.780 align:start position:0% just like redundant hubs between each other<00:07:51.110> so<00:07:51.800> we're<00:07:52.070> going<00:07:52.190> to<00:07:52.280> really<00:07:52.490> see<00:07:52.760> that 00:07:52.780 --> 00:07:52.790 align:start position:0% other so we're going to really see that 00:07:52.790 --> 00:07:55.750 align:start position:0% other so we're going to really see that you<00:07:53.330> know<00:07:53.420> from<00:07:53.690> node<00:07:54.140> 1<00:07:54.170> to<00:07:54.380> 100<00:07:54.980> we're<00:07:55.580> going 00:07:55.750 --> 00:07:55.760 align:start position:0% you know from node 1 to 100 we're going 00:07:55.760 --> 00:07:58.210 align:start position:0% you know from node 1 to 100 we're going to<00:07:55.910> you<00:07:56.180> have<00:07:56.510> to<00:07:56.720> traverse<00:07:57.320> all<00:07:57.860> the<00:07:58.100> other 00:07:58.210 --> 00:07:58.220 align:start position:0% to you have to traverse all the other 00:07:58.220 --> 00:08:03.430 align:start position:0% to you have to traverse all the other nodes<00:07:58.400> to<00:07:58.640> get<00:07:58.760> to<00:07:58.910> that<00:07:59.030> one<00:08:01.120> so<00:08:02.200> this<00:08:03.200> is<00:08:03.260> in 00:08:03.430 --> 00:08:03.440 align:start position:0% nodes to get to that one so this is in 00:08:03.440 --> 00:08:05.080 align:start position:0% nodes to get to that one so this is in progress<00:08:03.620> you<00:08:04.010> can<00:08:04.130> check<00:08:04.430> out<00:08:04.580> those<00:08:04.790> two 00:08:05.080 --> 00:08:05.090 align:start position:0% progress you can check out those two 00:08:05.090 --> 00:08:08.230 align:start position:0% progress you can check out those two repos<00:08:05.480> the<00:08:05.750> first<00:08:05.960> one<00:08:06.170> here<00:08:06.440> is<00:08:06.470> our<00:08:07.240> project 00:08:08.230 --> 00:08:08.240 align:start position:0% repos the first one here is our project 00:08:08.240 --> 00:08:10.900 align:start position:0% repos the first one here is our project management<00:08:08.480> repo<00:08:09.010> this<00:08:10.010> is<00:08:10.160> all<00:08:10.310> the<00:08:10.460> issues 00:08:10.900 --> 00:08:10.910 align:start position:0% management repo this is all the issues 00:08:10.910 --> 00:08:12.370 align:start position:0% management repo this is all the issues kind<00:08:11.240> of<00:08:11.300> reflect<00:08:11.660> the<00:08:11.750> work<00:08:11.900> from<00:08:12.080> the<00:08:12.200> team 00:08:12.370 --> 00:08:12.380 align:start position:0% kind of reflect the work from the team 00:08:12.380 --> 00:08:13.540 align:start position:0% kind of reflect the work from the team you<00:08:12.650> can<00:08:12.800> take<00:08:13.070> a<00:08:13.100> look 00:08:13.540 --> 00:08:13.550 align:start position:0% you can take a look 00:08:13.550 --> 00:08:15.970 align:start position:0% you can take a look contributions<00:08:14.390> are<00:08:14.510> very<00:08:14.690> welcome<00:08:15.020> your 00:08:15.970 --> 00:08:15.980 align:start position:0% contributions are very welcome your 00:08:15.980 --> 00:08:18.580 align:start position:0% contributions are very welcome your feedback<00:08:16.160> in<00:08:16.700> issues<00:08:17.060> you<00:08:17.150> see<00:08:17.410> the<00:08:18.410> work 00:08:18.580 --> 00:08:18.590 align:start position:0% feedback in issues you see the work 00:08:18.590 --> 00:08:20.350 align:start position:0% feedback in issues you see the work itself<00:08:18.950> the<00:08:19.520> benchmark<00:08:19.940> tool<00:08:20.090> is<00:08:20.240> actually 00:08:20.350 --> 00:08:20.360 align:start position:0% itself the benchmark tool is actually 00:08:20.360 --> 00:08:22.900 align:start position:0% itself the benchmark tool is actually under<00:08:20.840> agency<00:08:21.170> enterprise<00:08:21.800> it<00:08:22.550> can<00:08:22.730> take<00:08:22.880> a 00:08:22.900 --> 00:08:22.910 align:start position:0% under agency enterprise it can take a 00:08:22.910 --> 00:08:25.180 align:start position:0% under agency enterprise it can take a look<00:08:23.060> at<00:08:23.210> it<00:08:23.300> you<00:08:23.750> can<00:08:23.900> run<00:08:24.080> it<00:08:24.200> right<00:08:24.350> now<00:08:24.530> the 00:08:25.180 --> 00:08:25.190 align:start position:0% look at it you can run it right now the 00:08:25.190 --> 00:08:26.380 align:start position:0% look at it you can run it right now the idea<00:08:25.430> is<00:08:25.550> that<00:08:25.580> we're<00:08:25.820> going<00:08:25.940> to<00:08:26.000> talk<00:08:26.210> right 00:08:26.380 --> 00:08:26.390 align:start position:0% idea is that we're going to talk right 00:08:26.390 --> 00:08:28.030 align:start position:0% idea is that we're going to talk right at<00:08:26.600> work<00:08:26.810> and<00:08:27.050> then<00:08:27.140> deploy<00:08:27.380> it<00:08:27.440> on<00:08:27.650> Genesis 00:08:28.030 --> 00:08:28.040 align:start position:0% at work and then deploy it on Genesis 00:08:28.040 --> 00:08:29.950 align:start position:0% at work and then deploy it on Genesis we're<00:08:28.280> getting<00:08:28.460> around<00:08:28.730> you<00:08:28.880> know<00:08:28.970> 3100<00:08:29.840> of 00:08:29.950 --> 00:08:29.960 align:start position:0% we're getting around you know 3100 of 00:08:29.960 --> 00:08:33.909 align:start position:0% we're getting around you know 3100 of those<00:08:30.140> in<00:08:30.500> parallel<00:08:31.300> and<00:08:32.300> we<00:08:33.229> had<00:08:33.740> some 00:08:33.909 --> 00:08:33.919 align:start position:0% those in parallel and we had some 00:08:33.919 --> 00:08:37.360 align:start position:0% those in parallel and we had some unexpected<00:08:34.400> good<00:08:34.700> news<00:08:34.960> and<00:08:35.960> of<00:08:36.229> familiar<00:08:37.190> but 00:08:37.360 --> 00:08:37.370 align:start position:0% unexpected good news and of familiar but 00:08:37.370 --> 00:08:41.380 align:start position:0% unexpected good news and of familiar but we<00:08:37.580> got<00:08:38.180> access<00:08:38.930> to<00:08:39.469> an<00:08:39.770> academic 00:08:41.380 --> 00:08:41.390 align:start position:0% we got access to an academic 00:08:41.390 --> 00:08:43.500 align:start position:0% we got access to an academic facility<00:08:42.380> to<00:08:42.620> run<00:08:42.800> all<00:08:43.010> those<00:08:43.099> tests 00:08:43.500 --> 00:08:43.510 align:start position:0% facility to run all those tests 00:08:43.510 --> 00:08:46.960 align:start position:0% facility to run all those tests something<00:08:44.510> called<00:08:44.690> amil<00:08:44.959> abhinaya<00:08:45.339> so<00:08:46.339> we're 00:08:46.960 --> 00:08:46.970 align:start position:0% something called amil abhinaya so we're 00:08:46.970 --> 00:08:48.430 align:start position:0% something called amil abhinaya so we're starting<00:08:47.089> testing<00:08:47.750> actually<00:08:47.839> this<00:08:48.110> week<00:08:48.320> you 00:08:48.430 --> 00:08:48.440 align:start position:0% starting testing actually this week you 00:08:48.440 --> 00:08:50.620 align:start position:0% starting testing actually this week you got<00:08:48.560> a<00:08:48.589> guy<00:08:48.769> on<00:08:48.800> this<00:08:49.100> we're<00:08:49.760> going<00:08:49.880> to<00:08:50.120> publish 00:08:50.620 --> 00:08:50.630 align:start position:0% got a guy on this we're going to publish 00:08:50.630 --> 00:08:52.540 align:start position:0% got a guy on this we're going to publish all<00:08:50.870> the<00:08:51.019> raw<00:08:51.140> data<00:08:51.170> sets<00:08:51.620> for<00:08:51.769> every<00:08:52.160> test 00:08:52.540 --> 00:08:52.550 align:start position:0% all the raw data sets for every test 00:08:52.550 --> 00:08:54.940 align:start position:0% all the raw data sets for every test suite<00:08:52.790> on<00:08:53.149> Google<00:08:53.870> Cloud<00:08:54.019> Storage<00:08:54.380> you<00:08:54.800> can 00:08:54.940 --> 00:08:54.950 align:start position:0% suite on Google Cloud Storage you can 00:08:54.950 --> 00:08:57.490 align:start position:0% suite on Google Cloud Storage you can download<00:08:55.160> those<00:08:55.870> there<00:08:56.870> you<00:08:57.079> know<00:08:57.170> one<00:08:57.350> point 00:08:57.490 --> 00:08:57.500 align:start position:0% download those there you know one point 00:08:57.500 --> 00:08:59.740 align:start position:0% download those there you know one point five<00:08:57.709> gigabytes<00:08:58.040> each<00:08:58.279> so<00:08:58.790> just<00:08:59.420> quite<00:08:59.570> a<00:08:59.600> bit 00:08:59.740 --> 00:08:59.750 align:start position:0% five gigabytes each so just quite a bit 00:08:59.750 --> 00:09:02.829 align:start position:0% five gigabytes each so just quite a bit of<00:08:59.870> data<00:09:00.190> and<00:09:01.190> then<00:09:01.730> we'll<00:09:01.910> also<00:09:02.240> share<00:09:02.540> the 00:09:02.829 --> 00:09:02.839 align:start position:0% of data and then we'll also share the 00:09:02.839 --> 00:09:04.600 align:start position:0% of data and then we'll also share the Python<00:09:03.410> parsing<00:09:03.709> script<00:09:03.950> that<00:09:04.070> we<00:09:04.190> use<00:09:04.370> to 00:09:04.600 --> 00:09:04.610 align:start position:0% Python parsing script that we use to 00:09:04.610 --> 00:09:06.069 align:start position:0% Python parsing script that we use to read<00:09:04.760> all<00:09:04.910> the<00:09:05.029> logs<00:09:05.209> to<00:09:05.450> make<00:09:05.570> sense<00:09:05.779> of<00:09:05.870> them 00:09:06.069 --> 00:09:06.079 align:start position:0% read all the logs to make sense of them 00:09:06.079 --> 00:09:07.930 align:start position:0% read all the logs to make sense of them to<00:09:06.320> compare<00:09:06.589> all<00:09:06.800> the<00:09:06.980> statistics<00:09:07.490> the<00:09:07.790> median 00:09:07.930 --> 00:09:07.940 align:start position:0% to compare all the statistics the median 00:09:07.940 --> 00:09:10.900 align:start position:0% to compare all the statistics the median the<00:09:08.420> all<00:09:08.990> these<00:09:09.470> data<00:09:09.680> in<00:09:09.950> will<00:09:10.640> make<00:09:10.790> that 00:09:10.900 --> 00:09:10.910 align:start position:0% the all these data in will make that 00:09:10.910 --> 00:09:12.910 align:start position:0% the all these data in will make that open<00:09:11.240> source<00:09:11.420> as<00:09:11.540> well<00:09:11.690> probably<00:09:12.410> and<00:09:12.769> there's 00:09:12.910 --> 00:09:12.920 align:start position:0% open source as well probably and there's 00:09:12.920 --> 00:09:16.120 align:start position:0% open source as well probably and there's a<00:09:13.070> the<00:09:13.370> PM<00:09:13.610> repo<00:09:13.850> so<00:09:14.630> the<00:09:15.589> idea<00:09:15.800> is<00:09:15.890> that<00:09:15.920> we 00:09:16.120 --> 00:09:16.130 align:start position:0% a the PM repo so the idea is that we 00:09:16.130 --> 00:09:17.800 align:start position:0% a the PM repo so the idea is that we want<00:09:16.250> to<00:09:16.399> be<00:09:16.519> completely<00:09:16.880> transparent<00:09:17.149> make 00:09:17.800 --> 00:09:17.810 align:start position:0% want to be completely transparent make 00:09:17.810 --> 00:09:19.660 align:start position:0% want to be completely transparent make sure<00:09:17.990> that<00:09:18.200> our<00:09:18.410> work<00:09:18.680> is<00:09:19.010> being<00:09:19.250> reviewed<00:09:19.519> by 00:09:19.660 --> 00:09:19.670 align:start position:0% sure that our work is being reviewed by 00:09:19.670 --> 00:09:22.329 align:start position:0% sure that our work is being reviewed by the<00:09:19.820> community<00:09:20.329> and<00:09:21.019> if<00:09:21.230> you<00:09:21.410> have<00:09:21.589> an<00:09:21.829> idea<00:09:22.220> or 00:09:22.329 --> 00:09:22.339 align:start position:0% the community and if you have an idea or 00:09:22.339 --> 00:09:23.650 align:start position:0% the community and if you have an idea or a<00:09:22.490> suggestion<00:09:22.880> for<00:09:23.209> a<00:09:23.269> different<00:09:23.510> type<00:09:23.630> of 00:09:23.650 --> 00:09:23.660 align:start position:0% a suggestion for a different type of 00:09:23.660 --> 00:09:25.180 align:start position:0% a suggestion for a different type of testing<00:09:24.140> you<00:09:24.260> can<00:09:24.290> come<00:09:24.589> to<00:09:24.740> us<00:09:24.860> you<00:09:25.040> can<00:09:25.070> ask 00:09:25.180 --> 00:09:25.190 align:start position:0% testing you can come to us you can ask 00:09:25.190 --> 00:09:27.040 align:start position:0% testing you can come to us you can ask us<00:09:25.459> questions<00:09:25.880> we<00:09:26.510> can<00:09:26.660> have<00:09:26.779> a<00:09:26.810> conversation 00:09:27.040 --> 00:09:27.050 align:start position:0% us questions we can have a conversation 00:09:27.050 --> 00:09:29.259 align:start position:0% us questions we can have a conversation about<00:09:27.380> this<00:09:27.649> and<00:09:27.950> we<00:09:28.040> can<00:09:28.220> come<00:09:28.850> together<00:09:29.029> and 00:09:29.259 --> 00:09:29.269 align:start position:0% about this and we can come together and 00:09:29.269 --> 00:09:32.740 align:start position:0% about this and we can come together and collaborate<00:09:29.420> on<00:09:29.750> all<00:09:29.899> those<00:09:30.019> things<00:09:30.970> so<00:09:31.970> to 00:09:32.740 --> 00:09:32.750 align:start position:0% collaborate on all those things so to 00:09:32.750 --> 00:09:34.389 align:start position:0% collaborate on all those things so to switch<00:09:32.870> gears<00:09:33.260> this<00:09:33.410> is<00:09:33.560> coming<00:09:33.890> a<00:09:34.070> little<00:09:34.220> bit 00:09:34.389 --> 00:09:34.399 align:start position:0% switch gears this is coming a little bit 00:09:34.399 --> 00:09:37.329 align:start position:0% switch gears this is coming a little bit also<00:09:34.579> from<00:09:34.970> a<00:09:35.269> workforce<00:09:35.720> if<00:09:36.050> you're<00:09:36.170> m2<00:09:36.470> so 00:09:37.329 --> 00:09:37.339 align:start position:0% also from a workforce if you're m2 so 00:09:37.339 --> 00:09:39.819 align:start position:0% also from a workforce if you're m2 so just<00:09:37.579> going<00:09:38.180> to<00:09:38.300> do<00:09:38.390> a<00:09:38.420> little<00:09:38.510> recap<00:09:38.870> on<00:09:39.170> the 00:09:39.819 --> 00:09:39.829 align:start position:0% just going to do a little recap on the 00:09:39.829 --> 00:09:41.170 align:start position:0% just going to do a little recap on the interrupt<00:09:40.250> workshop<00:09:40.610> that<00:09:40.730> we<00:09:40.880> did<00:09:41.029> in 00:09:41.170 --> 00:09:41.180 align:start position:0% interrupt workshop that we did in 00:09:41.180 --> 00:09:43.900 align:start position:0% interrupt workshop that we did in September<00:09:41.829> here<00:09:42.829> you<00:09:42.920> can<00:09:43.040> see<00:09:43.220> these<00:09:43.730> are 00:09:43.900 --> 00:09:43.910 align:start position:0% September here you can see these are 00:09:43.910 --> 00:09:45.639 align:start position:0% September here you can see these are stand<00:09:44.180> up<00:09:44.329> in<00:09:44.420> the<00:09:44.480> morning<00:09:44.810> have<00:09:45.110> Danny<00:09:45.410> Ryan 00:09:45.639 --> 00:09:45.649 align:start position:0% stand up in the morning have Danny Ryan 00:09:45.649 --> 00:09:49.360 align:start position:0% stand up in the morning have Danny Ryan F<00:09:46.010> telling<00:09:46.790> us<00:09:46.910> how<00:09:47.510> things<00:09:47.660> are<00:09:47.839> going<00:09:48.370> we 00:09:49.360 --> 00:09:49.370 align:start position:0% F telling us how things are going we 00:09:49.370 --> 00:09:51.970 align:start position:0% F telling us how things are going we were<00:09:49.519> going<00:09:49.850> by<00:09:50.000> team<00:09:50.529> here<00:09:51.529> you<00:09:51.649> have<00:09:51.769> like 00:09:51.970 --> 00:09:51.980 align:start position:0% were going by team here you have like 00:09:51.980 --> 00:09:54.060 align:start position:0% were going by team here you have like different<00:09:52.220> teams<00:09:52.550> working<00:09:52.699> together<00:09:53.060> on 00:09:54.060 --> 00:09:54.070 align:start position:0% different teams working together on 00:09:54.070 --> 00:09:58.000 align:start position:0% different teams working together on working<00:09:55.070> on<00:09:55.430> the<00:09:55.490> same<00:09:55.640> laptops<00:09:56.350> so<00:09:57.350> the 00:09:58.000 --> 00:09:58.010 align:start position:0% working on the same laptops so the 00:09:58.010 --> 00:10:00.189 align:start position:0% working on the same laptops so the purpose<00:09:58.339> of<00:09:58.579> interrupt<00:09:59.240> for<00:09:59.390> us<00:09:59.570> was<00:10:00.050> to 00:10:00.189 --> 00:10:00.199 align:start position:0% purpose of interrupt for us was to 00:10:00.199 --> 00:10:02.259 align:start position:0% purpose of interrupt for us was to establish<00:10:00.920> communications<00:10:01.519> between<00:10:02.120> the 00:10:02.259 --> 00:10:02.269 align:start position:0% establish communications between the 00:10:02.269 --> 00:10:04.930 align:start position:0% establish communications between the teams<00:10:02.570> to<00:10:03.260> make<00:10:03.380> sure<00:10:03.560> that<00:10:03.829> they<00:10:04.100> had<00:10:04.310> a<00:10:04.550> good 00:10:04.930 --> 00:10:04.940 align:start position:0% teams to make sure that they had a good 00:10:04.940 --> 00:10:07.269 align:start position:0% teams to make sure that they had a good process<00:10:05.209> to<00:10:05.600> work<00:10:05.750> together<00:10:05.980> coming<00:10:06.980> in<00:10:07.100> to 00:10:07.269 --> 00:10:07.279 align:start position:0% process to work together coming in to 00:10:07.279 --> 00:10:09.610 align:start position:0% process to work together coming in to interrupt<00:10:08.000> we<00:10:08.209> just<00:10:08.390> wanted<00:10:08.690> people<00:10:08.990> to<00:10:09.170> just 00:10:09.610 --> 00:10:09.620 align:start position:0% interrupt we just wanted people to just 00:10:09.620 --> 00:10:12.069 align:start position:0% interrupt we just wanted people to just take<00:10:09.800> one<00:10:10.040> laptop<00:10:10.220> to<00:10:10.730> clients<00:10:11.209> make<00:10:11.870> them 00:10:12.069 --> 00:10:12.079 align:start position:0% take one laptop to clients make them 00:10:12.079 --> 00:10:14.170 align:start position:0% take one laptop to clients make them work<00:10:12.260> and<00:10:12.620> see<00:10:12.890> he<00:10:13.100> was<00:10:13.190> able<00:10:13.459> to<00:10:13.490> even<00:10:14.029> just 00:10:14.170 --> 00:10:14.180 align:start position:0% work and see he was able to even just 00:10:14.180 --> 00:10:16.389 align:start position:0% work and see he was able to even just gossip<00:10:14.660> a<00:10:14.720> blog<00:10:14.930> say<00:10:15.800> hello 00:10:16.389 --> 00:10:16.399 align:start position:0% gossip a blog say hello 00:10:16.399 --> 00:10:21.939 align:start position:0% gossip a blog say hello have<00:10:16.699> some<00:10:16.910> information<00:10:19.899> we<00:10:20.899> had<00:10:21.050> some<00:10:21.260> great 00:10:21.939 --> 00:10:21.949 align:start position:0% have some information we had some great 00:10:21.949 --> 00:10:24.430 align:start position:0% have some information we had some great tooling<00:10:22.310> from<00:10:22.699> pato<00:10:23.269> lambda<00:10:23.660> from<00:10:23.870> the<00:10:23.930> Fenian 00:10:24.430 --> 00:10:24.440 align:start position:0% tooling from pato lambda from the Fenian 00:10:24.440 --> 00:10:25.960 align:start position:0% tooling from pato lambda from the Fenian foundation<00:10:24.860> so<00:10:25.040> he<00:10:25.220> gave<00:10:25.430> us<00:10:25.610> a<00:10:25.640> way<00:10:25.910> to 00:10:25.960 --> 00:10:25.970 align:start position:0% foundation so he gave us a way to 00:10:25.970 --> 00:10:29.050 align:start position:0% foundation so he gave us a way to regenerate<00:10:26.890> genesis<00:10:27.890> states<00:10:28.130> like<00:10:28.730> 30 00:10:29.050 --> 00:10:29.060 align:start position:0% regenerate genesis states like 30 00:10:29.060 --> 00:10:31.269 align:start position:0% regenerate genesis states like 30 seconds<00:10:29.510> or<00:10:29.600> 1<00:10:29.779> minute<00:10:29.810> in<00:10:30.140> the<00:10:30.199> future<00:10:30.500> that 00:10:31.269 --> 00:10:31.279 align:start position:0% seconds or 1 minute in the future that 00:10:31.279 --> 00:10:33.310 align:start position:0% seconds or 1 minute in the future that everybody<00:10:32.089> could<00:10:32.240> ingest 00:10:33.310 --> 00:10:33.320 align:start position:0% everybody could ingest 00:10:33.320 --> 00:10:35.500 align:start position:0% everybody could ingest as<00:10:33.980> well<00:10:34.190> as<00:10:34.279> the<00:10:34.399> list<00:10:34.519> of<00:10:34.670> validators<00:10:35.149> that 00:10:35.500 --> 00:10:35.510 align:start position:0% as well as the list of validators that 00:10:35.510 --> 00:10:37.630 align:start position:0% as well as the list of validators that would<00:10:35.630> be<00:10:35.779> associated<00:10:36.560> with<00:10:36.709> each<00:10:36.980> client<00:10:37.279> and 00:10:37.630 --> 00:10:37.640 align:start position:0% would be associated with each client and 00:10:37.640 --> 00:10:40.600 align:start position:0% would be associated with each client and then<00:10:38.390> would<00:10:38.570> give<00:10:38.690> us<00:10:38.930> the<00:10:39.079> ability<00:10:39.470> to<00:10:39.860> very 00:10:40.600 --> 00:10:40.610 align:start position:0% then would give us the ability to very 00:10:40.610 --> 00:10:42.639 align:start position:0% then would give us the ability to very quickly<00:10:40.850> set<00:10:41.209> up<00:10:41.329> this<00:10:41.930> type<00:10:42.140> of<00:10:42.170> scenarios 00:10:42.639 --> 00:10:42.649 align:start position:0% quickly set up this type of scenarios 00:10:42.649 --> 00:10:44.980 align:start position:0% quickly set up this type of scenarios you<00:10:43.610> know<00:10:43.699> initially<00:10:43.910> what<00:10:44.329> the<00:10:44.510> clients<00:10:44.810> did 00:10:44.980 --> 00:10:44.990 align:start position:0% you know initially what the clients did 00:10:44.990 --> 00:10:47.319 align:start position:0% you know initially what the clients did was<00:10:45.230> only<00:10:45.920> one<00:10:46.100> client<00:10:46.310> in<00:10:46.760> the<00:10:46.850> test<00:10:47.060> net<00:10:47.209> with 00:10:47.319 --> 00:10:47.329 align:start position:0% was only one client in the test net with 00:10:47.329 --> 00:10:49.210 align:start position:0% was only one client in the test net with a<00:10:47.360> validators<00:10:47.930> everybody<00:10:48.860> else<00:10:48.980> would<00:10:49.100> be 00:10:49.210 --> 00:10:49.220 align:start position:0% a validators everybody else would be 00:10:49.220 --> 00:10:51.550 align:start position:0% a validators everybody else would be passive<00:10:49.640> and<00:10:49.850> just<00:10:50.180> ingesting<00:10:50.959> old<00:10:51.079> data<00:10:51.319> and 00:10:51.550 --> 00:10:51.560 align:start position:0% passive and just ingesting old data and 00:10:51.560 --> 00:10:54.010 align:start position:0% passive and just ingesting old data and as<00:10:52.490> we<00:10:52.790> got<00:10:52.910> closer<00:10:53.240> to<00:10:53.390> the<00:10:53.600> end<00:10:53.720> of<00:10:53.779> the<00:10:53.870> week 00:10:54.010 --> 00:10:54.020 align:start position:0% as we got closer to the end of the week 00:10:54.020 --> 00:10:55.690 align:start position:0% as we got closer to the end of the week everybody<00:10:54.560> was<00:10:54.949> able<00:10:55.069> to 00:10:55.690 --> 00:10:55.700 align:start position:0% everybody was able to 00:10:55.700 --> 00:10:57.310 align:start position:0% everybody was able to very<00:10:56.180> same<00:10:56.390> time<00:10:56.600> so<00:10:56.840> everybody<00:10:57.110> was 00:10:57.310 --> 00:10:57.320 align:start position:0% very same time so everybody was 00:10:57.320 --> 00:10:59.050 align:start position:0% very same time so everybody was processing<00:10:57.650> blocks<00:10:57.950> we<00:10:58.580> had<00:10:58.760> to<00:10:58.880> get 00:10:59.050 --> 00:10:59.060 align:start position:0% processing blocks we had to get 00:10:59.060 --> 00:11:01.900 align:start position:0% processing blocks we had to get everybody<00:10:59.420> going<00:10:59.620> a<00:11:00.620> good<00:11:01.010> caveat<00:11:01.430> of<00:11:01.550> this<00:11:01.730> is 00:11:01.900 --> 00:11:01.910 align:start position:0% everybody going a good caveat of this is 00:11:01.910 --> 00:11:05.320 align:start position:0% everybody going a good caveat of this is that<00:11:02.060> solo<00:11:02.840> jury<00:11:03.170> because<00:11:03.740> we<00:11:04.190> had<00:11:04.340> to<00:11:04.520> kind<00:11:05.270> of 00:11:05.320 --> 00:11:05.330 align:start position:0% that solo jury because we had to kind of 00:11:05.330 --> 00:11:07.240 align:start position:0% that solo jury because we had to kind of go<00:11:06.020> with<00:11:06.200> the<00:11:06.290> flow<00:11:06.530> of<00:11:06.560> those<00:11:06.890> different 00:11:07.240 --> 00:11:07.250 align:start position:0% go with the flow of those different 00:11:07.250 --> 00:11:09.430 align:start position:0% go with the flow of those different clients<00:11:07.700> some<00:11:08.240> cons<00:11:08.450> did<00:11:08.630> not<00:11:08.810> support<00:11:09.110> sync 00:11:09.430 --> 00:11:09.440 align:start position:0% clients some cons did not support sync 00:11:09.440 --> 00:11:12.190 align:start position:0% clients some cons did not support sync for<00:11:09.650> example<00:11:10.070> so<00:11:10.550> if<00:11:10.850> they<00:11:11.060> studied<00:11:11.510> after<00:11:11.690> to 00:11:12.190 --> 00:11:12.200 align:start position:0% for example so if they studied after to 00:11:12.200 --> 00:11:13.960 align:start position:0% for example so if they studied after to Genesis<00:11:12.590> time<00:11:12.800> they<00:11:13.250> would<00:11:13.430> not<00:11:13.580> have<00:11:13.760> a<00:11:13.790> good 00:11:13.960 --> 00:11:13.970 align:start position:0% Genesis time they would not have a good 00:11:13.970 --> 00:11:16.350 align:start position:0% Genesis time they would not have a good time<00:11:14.120> working<00:11:14.450> with<00:11:14.630> the<00:11:14.810> others<00:11:15.050> right<00:11:15.530> so 00:11:16.350 --> 00:11:16.360 align:start position:0% time working with the others right so 00:11:16.360 --> 00:11:20.110 align:start position:0% time working with the others right so you<00:11:17.360> also<00:11:17.590> to<00:11:18.590> give<00:11:18.740> you<00:11:18.770> an<00:11:18.920> idea<00:11:19.550> it<00:11:19.790> was<00:11:19.880> very 00:11:20.110 --> 00:11:20.120 align:start position:0% you also to give you an idea it was very 00:11:20.120 --> 00:11:23.890 align:start position:0% you also to give you an idea it was very manual<00:11:20.680> they<00:11:21.680> would<00:11:21.890> have<00:11:22.220> a<00:11:23.030> Tmax 00:11:23.890 --> 00:11:23.900 align:start position:0% manual they would have a Tmax 00:11:23.900 --> 00:11:26.560 align:start position:0% manual they would have a Tmax kind<00:11:24.560> of<00:11:24.620> window<00:11:25.010> at<00:11:25.100> first<00:11:25.360> start<00:11:26.360> first 00:11:26.560 --> 00:11:26.570 align:start position:0% kind of window at first start first 00:11:26.570 --> 00:11:29.700 align:start position:0% kind of window at first start first client<00:11:27.080> look<00:11:27.620> at<00:11:27.860> the<00:11:28.160> inno<00:11:28.490> dove<00:11:28.790> that<00:11:28.940> client 00:11:29.700 --> 00:11:29.710 align:start position:0% client look at the inno dove that client 00:11:29.710 --> 00:11:32.140 align:start position:0% client look at the inno dove that client paste<00:11:30.710> that<00:11:30.890> into<00:11:31.130> the<00:11:31.520> start<00:11:31.730> script<00:11:31.940> of<00:11:32.090> the 00:11:32.140 --> 00:11:32.150 align:start position:0% paste that into the start script of the 00:11:32.150 --> 00:11:33.850 align:start position:0% paste that into the start script of the second<00:11:32.480> client<00:11:32.660> start<00:11:33.170> the<00:11:33.290> second<00:11:33.650> client 00:11:33.850 --> 00:11:33.860 align:start position:0% second client start the second client 00:11:33.860 --> 00:11:36.760 align:start position:0% second client start the second client start<00:11:34.670> a<00:11:34.730> circle<00:11:35.420> i<00:11:35.480> n't<00:11:35.660> cetera<00:11:36.320> et<00:11:36.350> cetera 00:11:36.760 --> 00:11:36.770 align:start position:0% start a circle i n't cetera et cetera 00:11:36.770 --> 00:11:39.670 align:start position:0% start a circle i n't cetera et cetera very<00:11:37.460> manual<00:11:37.760> but<00:11:38.120> you<00:11:38.450> know<00:11:38.570> for<00:11:39.080> first<00:11:39.380> try 00:11:39.670 --> 00:11:39.680 align:start position:0% very manual but you know for first try 00:11:39.680 --> 00:11:42.430 align:start position:0% very manual but you know for first try that<00:11:40.010> was<00:11:40.160> that<00:11:40.610> was<00:11:40.730> a<00:11:40.760> good<00:11:40.940> try<00:11:41.420> right<00:11:41.720> so<00:11:42.020> we 00:11:42.430 --> 00:11:42.440 align:start position:0% that was that was a good try right so we 00:11:42.440 --> 00:11:43.600 align:start position:0% that was that was a good try right so we had<00:11:42.560> a<00:11:42.620> few<00:11:42.740> panics<00:11:43.130> we<00:11:43.250> had<00:11:43.370> a<00:11:43.430> few 00:11:43.600 --> 00:11:43.610 align:start position:0% had a few panics we had a few 00:11:43.610 --> 00:11:46.840 align:start position:0% had a few panics we had a few interesting<00:11:44.030> crashes<00:11:44.830> we<00:11:45.830> saw<00:11:46.040> all<00:11:46.520> the 00:11:46.840 --> 00:11:46.850 align:start position:0% interesting crashes we saw all the 00:11:46.850 --> 00:11:50.530 align:start position:0% interesting crashes we saw all the things<00:11:47.090> that<00:11:47.390> could<00:11:47.480> go<00:11:47.540> wrong<00:11:47.690> and<00:11:49.540> well 00:11:50.530 --> 00:11:50.540 align:start position:0% things that could go wrong and well 00:11:50.540 --> 00:11:52.180 align:start position:0% things that could go wrong and well eventually<00:11:51.080> they<00:11:51.410> managed<00:11:51.650> to<00:11:51.710> get<00:11:51.950> some 00:11:52.180 --> 00:11:52.190 align:start position:0% eventually they managed to get some 00:11:52.190 --> 00:11:54.790 align:start position:0% eventually they managed to get some clients<00:11:52.400> on<00:11:52.640> laptop<00:11:52.940> which<00:11:53.150> is<00:11:53.330> a<00:11:53.750> pretty<00:11:54.590> good 00:11:54.790 --> 00:11:54.800 align:start position:0% clients on laptop which is a pretty good 00:11:54.800 --> 00:11:57.190 align:start position:0% clients on laptop which is a pretty good result<00:11:55.430> much<00:11:56.180> better<00:11:56.420> than<00:11:56.660> we<00:11:56.750> anticipated 00:11:57.190 --> 00:11:57.200 align:start position:0% result much better than we anticipated 00:11:57.200 --> 00:12:01.450 align:start position:0% result much better than we anticipated going<00:11:57.590> in<00:11:58.030> so<00:11:59.230> yeah<00:12:00.230> eventually<00:12:00.650> what<00:12:01.070> we<00:12:01.280> want 00:12:01.450 --> 00:12:01.460 align:start position:0% going in so yeah eventually what we want 00:12:01.460 --> 00:12:02.980 align:start position:0% going in so yeah eventually what we want to<00:12:01.550> do<00:12:01.640> now<00:12:01.790> is<00:12:01.970> to<00:12:02.090> actually<00:12:02.150> productize<00:12:02.720> this 00:12:02.980 --> 00:12:02.990 align:start position:0% to do now is to actually productize this 00:12:02.990 --> 00:12:06.310 align:start position:0% to do now is to actually productize this so<00:12:03.700> recap<00:12:04.700> of<00:12:04.850> the<00:12:04.910> success<00:12:05.270> we<00:12:05.660> had<00:12:05.840> some 00:12:06.310 --> 00:12:06.320 align:start position:0% so recap of the success we had some 00:12:06.320 --> 00:12:08.470 align:start position:0% so recap of the success we had some clients<00:12:06.530> talking<00:12:07.130> to<00:12:07.340> each<00:12:07.430> other<00:12:07.580> on<00:12:08.030> a<00:12:08.090> local 00:12:08.470 --> 00:12:08.480 align:start position:0% clients talking to each other on a local 00:12:08.480 --> 00:12:11.800 align:start position:0% clients talking to each other on a local machine<00:12:08.800> a<00:12:09.800> little<00:12:10.280> harder<00:12:10.610> for<00:12:10.760> us<00:12:10.910> we're 00:12:11.800 --> 00:12:11.810 align:start position:0% machine a little harder for us we're 00:12:11.810 --> 00:12:14.080 align:start position:0% machine a little harder for us we're using<00:12:12.020> docker<00:12:12.350> and<00:12:12.710> now<00:12:13.550> we<00:12:13.610> want<00:12:13.970> to 00:12:14.080 --> 00:12:14.090 align:start position:0% using docker and now we want to 00:12:14.090 --> 00:12:15.940 align:start position:0% using docker and now we want to publicize<00:12:14.510> what<00:12:14.780> they've<00:12:14.900> done<00:12:15.110> into<00:12:15.740> weather 00:12:15.940 --> 00:12:15.950 align:start position:0% publicize what they've done into weather 00:12:15.950 --> 00:12:17.980 align:start position:0% publicize what they've done into weather is<00:12:16.130> completely<00:12:16.520> automated<00:12:16.940> so<00:12:17.450> for<00:12:17.690> us<00:12:17.780> it<00:12:17.870> was 00:12:17.980 --> 00:12:17.990 align:start position:0% is completely automated so for us it was 00:12:17.990 --> 00:12:19.840 align:start position:0% is completely automated so for us it was a<00:12:18.020> little<00:12:18.230> harder<00:12:18.470> because<00:12:18.620> each<00:12:19.430> client<00:12:19.790> is 00:12:19.840 --> 00:12:19.850 align:start position:0% a little harder because each client is 00:12:19.850 --> 00:12:21.370 align:start position:0% a little harder because each client is ever<00:12:20.090> so<00:12:20.240> slightly<00:12:20.480> different<00:12:20.660> I'm<00:12:21.020> gonna<00:12:21.260> go 00:12:21.370 --> 00:12:21.380 align:start position:0% ever so slightly different I'm gonna go 00:12:21.380 --> 00:12:24.610 align:start position:0% ever so slightly different I'm gonna go into<00:12:21.620> that<00:12:22.630> the<00:12:23.630> way<00:12:23.750> we<00:12:23.930> run<00:12:24.140> things<00:12:24.350> with 00:12:24.610 --> 00:12:24.620 align:start position:0% into that the way we run things with 00:12:24.620 --> 00:12:26.320 align:start position:0% into that the way we run things with Genesis<00:12:25.070> is<00:12:25.280> that<00:12:25.430> we<00:12:25.700> pretty<00:12:25.940> much<00:12:26.030> take 00:12:26.320 --> 00:12:26.330 align:start position:0% Genesis is that we pretty much take 00:12:26.330 --> 00:12:28.270 align:start position:0% Genesis is that we pretty much take whatever<00:12:26.780> docker<00:12:27.050> image<00:12:27.440> are<00:12:27.950> blocked<00:12:28.190> in 00:12:28.270 --> 00:12:28.280 align:start position:0% whatever docker image are blocked in 00:12:28.280 --> 00:12:30.790 align:start position:0% whatever docker image are blocked in client<00:12:28.610> has<00:12:28.790> and<00:12:29.060> we<00:12:29.810> just<00:12:30.050> automate<00:12:30.440> its 00:12:30.790 --> 00:12:30.800 align:start position:0% client has and we just automate its 00:12:30.800 --> 00:12:32.860 align:start position:0% client has and we just automate its creation<00:12:31.400> in<00:12:31.520> its<00:12:31.640> lifecycle<00:12:31.910> as<00:12:32.420> part<00:12:32.690> of<00:12:32.750> a 00:12:32.860 --> 00:12:32.870 align:start position:0% creation in its lifecycle as part of a 00:12:32.870 --> 00:12:35.470 align:start position:0% creation in its lifecycle as part of a platform<00:12:33.050> so<00:12:33.920> it's<00:12:34.070> very<00:12:34.310> easy<00:12:34.460> for<00:12:34.850> us<00:12:34.910> once 00:12:35.470 --> 00:12:35.480 align:start position:0% platform so it's very easy for us once 00:12:35.480 --> 00:12:37.000 align:start position:0% platform so it's very easy for us once everything<00:12:35.870> is<00:12:35.930> in<00:12:36.080> place<00:12:36.110> to<00:12:36.680> go<00:12:36.770> very 00:12:37.000 --> 00:12:37.010 align:start position:0% everything is in place to go very 00:12:37.010 --> 00:12:38.890 align:start position:0% everything is in place to go very quickly<00:12:37.250> to<00:12:37.640> a<00:12:37.880> destination<00:12:38.360> to<00:12:38.570> just 00:12:38.890 --> 00:12:38.900 align:start position:0% quickly to a destination to just 00:12:38.900 --> 00:12:43.920 align:start position:0% quickly to a destination to just generate<00:12:39.200> many<00:12:39.440> of<00:12:39.590> them<00:12:41.560> so<00:12:42.560> things<00:12:43.310> that 00:12:43.920 --> 00:12:43.930 align:start position:0% generate many of them so things that 00:12:43.930 --> 00:12:47.220 align:start position:0% generate many of them so things that kind<00:12:44.930> of<00:12:45.040> took<00:12:46.040> a<00:12:46.190> bit<00:12:46.310> of<00:12:46.400> time<00:12:46.460> to<00:12:46.760> figure<00:12:46.910> out 00:12:47.220 --> 00:12:47.230 align:start position:0% kind of took a bit of time to figure out 00:12:47.230 --> 00:12:50.440 align:start position:0% kind of took a bit of time to figure out we<00:12:48.230> saw<00:12:48.500> that<00:12:48.580> you<00:12:49.580> know<00:12:49.700> if<00:12:50.000> even<00:12:50.420> so 00:12:50.440 --> 00:12:50.450 align:start position:0% we saw that you know if even so 00:12:50.450 --> 00:12:52.900 align:start position:0% we saw that you know if even so everybody<00:12:50.810> is<00:12:50.900> using<00:12:51.020> the<00:12:51.230> p2p<00:12:51.550> when<00:12:52.550> you<00:12:52.730> have 00:12:52.900 --> 00:12:52.910 align:start position:0% everybody is using the p2p when you have 00:12:52.910 --> 00:12:55.600 align:start position:0% everybody is using the p2p when you have an<00:12:53.240> address<00:12:53.480> for<00:12:53.960> a<00:12:54.620> client<00:12:54.890> for<00:12:55.190> a<00:12:55.220> node<00:12:55.400> in 00:12:55.600 --> 00:12:55.610 align:start position:0% an address for a client for a node in 00:12:55.610 --> 00:12:57.250 align:start position:0% an address for a client for a node in Limpy<00:12:55.850> GP<00:12:56.150> can<00:12:56.390> do<00:12:56.570> a<00:12:56.840> couple<00:12:57.110> different 00:12:57.250 --> 00:12:57.260 align:start position:0% Limpy GP can do a couple different 00:12:57.260 --> 00:12:59.110 align:start position:0% Limpy GP can do a couple different things<00:12:57.530> you<00:12:57.860> can<00:12:57.980> have<00:12:58.220> the<00:12:58.430> public<00:12:58.730> key<00:12:58.970> of 00:12:59.110 --> 00:12:59.120 align:start position:0% things you can have the public key of 00:12:59.120 --> 00:13:01.360 align:start position:0% things you can have the public key of your<00:12:59.210> client<00:13:00.170> being<00:13:00.350> published<00:13:00.920> to<00:13:01.070> all<00:13:01.250> your 00:13:01.360 --> 00:13:01.370 align:start position:0% your client being published to all your 00:13:01.370 --> 00:13:03.070 align:start position:0% your client being published to all your peers<00:13:01.670> or<00:13:01.940> you<00:13:02.000> can<00:13:02.180> choose<00:13:02.390> not<00:13:02.600> to<00:13:02.780> do<00:13:02.900> that 00:13:03.070 --> 00:13:03.080 align:start position:0% peers or you can choose not to do that 00:13:03.080 --> 00:13:04.810 align:start position:0% peers or you can choose not to do that and<00:13:03.350> when<00:13:04.100> they<00:13:04.220> connect<00:13:04.490> to<00:13:04.550> each<00:13:04.640> other 00:13:04.810 --> 00:13:04.820 align:start position:0% and when they connect to each other 00:13:04.820 --> 00:13:06.430 align:start position:0% and when they connect to each other that's<00:13:05.090> when<00:13:05.330> the<00:13:05.480> public<00:13:05.750> key<00:13:05.870> get<00:13:06.020> exchanged 00:13:06.430 --> 00:13:06.440 align:start position:0% that's when the public key get exchanged 00:13:06.440 --> 00:13:08.680 align:start position:0% that's when the public key get exchanged right<00:13:06.980> so<00:13:07.280> in<00:13:08.030> that<00:13:08.180> case<00:13:08.450> for<00:13:08.600> example 00:13:08.680 --> 00:13:08.690 align:start position:0% right so in that case for example 00:13:08.690 --> 00:13:09.550 align:start position:0% right so in that case for example sometimes 00:13:09.550 --> 00:13:09.560 align:start position:0% sometimes 00:13:09.560 --> 00:13:11.680 align:start position:0% sometimes just<00:13:09.770> barf<00:13:10.010> because<00:13:10.490> didn't<00:13:11.210> want<00:13:11.420> to<00:13:11.510> have 00:13:11.680 --> 00:13:11.690 align:start position:0% just barf because didn't want to have 00:13:11.690 --> 00:13:13.390 align:start position:0% just barf because didn't want to have the<00:13:11.840> public<00:13:11.960> key<00:13:12.350> of<00:13:12.560> the<00:13:12.830> other<00:13:13.010> node<00:13:13.250> in 00:13:13.390 --> 00:13:13.400 align:start position:0% the public key of the other node in 00:13:13.400 --> 00:13:15.040 align:start position:0% the public key of the other node in there<00:13:13.550> so<00:13:14.060> we<00:13:14.180> had<00:13:14.360> to<00:13:14.480> start<00:13:14.660> tweaking<00:13:14.900> for 00:13:15.040 --> 00:13:15.050 align:start position:0% there so we had to start tweaking for 00:13:15.050 --> 00:13:17.050 align:start position:0% there so we had to start tweaking for that<00:13:15.320> like<00:13:15.620> night-hunting<00:13:16.100> like<00:13:16.520> that<00:13:16.730> or 00:13:17.050 --> 00:13:17.060 align:start position:0% that like night-hunting like that or 00:13:17.060 --> 00:13:18.370 align:start position:0% that like night-hunting like that or should<00:13:17.090> we<00:13:17.600> have<00:13:17.690> to<00:13:17.840> change<00:13:18.050> the<00:13:18.170> start 00:13:18.370 --> 00:13:18.380 align:start position:0% should we have to change the start 00:13:18.380 --> 00:13:21.490 align:start position:0% should we have to change the start scrape<00:13:18.620> just<00:13:18.860> for<00:13:19.010> them<00:13:19.220> etc<00:13:19.960> we<00:13:20.960> saw<00:13:21.140> also 00:13:21.490 --> 00:13:21.500 align:start position:0% scrape just for them etc we saw also 00:13:21.500 --> 00:13:24.550 align:start position:0% scrape just for them etc we saw also that<00:13:21.710> they<00:13:22.190> have<00:13:22.779> different<00:13:23.779> ways<00:13:23.930> of<00:13:24.260> storing 00:13:24.550 --> 00:13:24.560 align:start position:0% that they have different ways of storing 00:13:24.560 --> 00:13:26.800 align:start position:0% that they have different ways of storing the<00:13:24.860> identity<00:13:25.460> key<00:13:25.640> the<00:13:26.000> key<00:13:26.210> that<00:13:26.420> actually 00:13:26.800 --> 00:13:26.810 align:start position:0% the identity key the key that actually 00:13:26.810 --> 00:13:29.500 align:start position:0% the identity key the key that actually represents<00:13:27.260> the<00:13:27.320> identity<00:13:27.470> of<00:13:27.800> the<00:13:28.310> note<00:13:28.510> lead 00:13:29.500 --> 00:13:29.510 align:start position:0% represents the identity of the note lead 00:13:29.510 --> 00:13:31.300 align:start position:0% represents the identity of the note lead PGP<00:13:29.900> by<00:13:30.050> default<00:13:30.470> is<00:13:30.830> going<00:13:31.040> to<00:13:31.160> use<00:13:31.279> a 00:13:31.300 --> 00:13:31.310 align:start position:0% PGP by default is going to use a 00:13:31.310 --> 00:13:33.640 align:start position:0% PGP by default is going to use a portable<00:13:31.580> format<00:13:32.120> which<00:13:32.540> adds<00:13:32.839> two<00:13:33.140> bytes<00:13:33.380> to 00:13:33.640 --> 00:13:33.650 align:start position:0% portable format which adds two bytes to 00:13:33.650 --> 00:13:35.769 align:start position:0% portable format which adds two bytes to the<00:13:33.680> beginning<00:13:34.190> of<00:13:34.400> the<00:13:34.850> the<00:13:35.300> string<00:13:35.570> that 00:13:35.769 --> 00:13:35.779 align:start position:0% the beginning of the the string that 00:13:35.779 --> 00:13:38.670 align:start position:0% the beginning of the the string that would<00:13:35.870> store<00:13:36.460> some<00:13:37.460> clients<00:13:37.910> like<00:13:38.089> that<00:13:38.270> as<00:13:38.510> a 00:13:38.670 --> 00:13:38.680 align:start position:0% would store some clients like that as a 00:13:38.680 --> 00:13:41.380 align:start position:0% would store some clients like that as a exactly<00:13:39.680> similar<00:13:40.010> string<00:13:40.250> being<00:13:40.700> passed<00:13:40.970> some 00:13:41.380 --> 00:13:41.390 align:start position:0% exactly similar string being passed some 00:13:41.390 --> 00:13:43.930 align:start position:0% exactly similar string being passed some like<00:13:41.570> that<00:13:41.930> as<00:13:42.170> a<00:13:42.230> basic<00:13:42.800> ste<00:13:42.950> for<00:13:43.190> string<00:13:43.520> to 00:13:43.930 --> 00:13:43.940 align:start position:0% like that as a basic ste for string to 00:13:43.940 --> 00:13:45.610 align:start position:0% like that as a basic ste for string to be<00:13:43.970> passed<00:13:44.270> and<00:13:44.570> something<00:13:45.050> like<00:13:45.140> that<00:13:45.260> into<00:13:45.470> a 00:13:45.610 --> 00:13:45.620 align:start position:0% be passed and something like that into a 00:13:45.620 --> 00:13:48.340 align:start position:0% be passed and something like that into a file<00:13:45.830> so<00:13:46.820> we<00:13:46.970> had<00:13:47.150> to<00:13:47.390> account<00:13:47.779> for<00:13:47.930> all<00:13:48.050> those 00:13:48.340 --> 00:13:48.350 align:start position:0% file so we had to account for all those 00:13:48.350 --> 00:13:50.470 align:start position:0% file so we had to account for all those different<00:13:48.410> variances<00:13:49.100> of<00:13:49.160> the<00:13:49.310> way<00:13:50.300> they 00:13:50.470 --> 00:13:50.480 align:start position:0% different variances of the way they 00:13:50.480 --> 00:13:53.290 align:start position:0% different variances of the way they would<00:13:50.600> consume<00:13:50.960> the<00:13:51.170> information<00:13:52.150> all<00:13:53.150> this 00:13:53.290 --> 00:13:53.300 align:start position:0% would consume the information all this 00:13:53.300 --> 00:13:55.540 align:start position:0% would consume the information all this of<00:13:53.450> course<00:13:53.770> works<00:13:54.770> very<00:13:54.980> well<00:13:55.070> when<00:13:55.370> you're 00:13:55.540 --> 00:13:55.550 align:start position:0% of course works very well when you're 00:13:55.550 --> 00:13:58.240 align:start position:0% of course works very well when you're doing<00:13:55.760> static<00:13:56.029> peering<00:13:56.560> at<00:13:57.560> this<00:13:57.890> point<00:13:58.130> I 00:13:58.240 --> 00:13:58.250 align:start position:0% doing static peering at this point I 00:13:58.250 --> 00:13:59.769 align:start position:0% doing static peering at this point I think<00:13:58.310> we<00:13:58.520> have<00:13:58.610> two<00:13:58.790> clients<00:13:59.000> that<00:13:59.270> do<00:13:59.510> this 00:13:59.769 --> 00:13:59.779 align:start position:0% think we have two clients that do this 00:13:59.779 --> 00:14:03.370 align:start position:0% think we have two clients that do this v5<00:14:00.140> it<00:14:00.260> might<00:14:00.380> be<00:14:00.500> wrong<00:14:01.600> so<00:14:02.600> that's<00:14:03.170> something 00:14:03.370 --> 00:14:03.380 align:start position:0% v5 it might be wrong so that's something 00:14:03.380 --> 00:14:06.670 align:start position:0% v5 it might be wrong so that's something that<00:14:03.500> we<00:14:03.920> need<00:14:04.160> to<00:14:04.220> look<00:14:04.460> at<00:14:04.670> next<00:14:05.170> so<00:14:06.170> that 00:14:06.670 --> 00:14:06.680 align:start position:0% that we need to look at next so that 00:14:06.680 --> 00:14:07.690 align:start position:0% that we need to look at next so that we're<00:14:06.950> going<00:14:07.070> to<00:14:07.160> talk<00:14:07.339> a<00:14:07.400> little<00:14:07.490> bit<00:14:07.610> about 00:14:07.690 --> 00:14:07.700 align:start position:0% we're going to talk a little bit about 00:14:07.700 --> 00:14:11.590 align:start position:0% we're going to talk a little bit about that<00:14:08.060> quickly<00:14:08.650> for<00:14:09.650> us<00:14:09.800> it<00:14:10.070> was<00:14:10.480> kind<00:14:11.480> of<00:14:11.510> a 00:14:11.590 --> 00:14:11.600 align:start position:0% that quickly for us it was kind of a 00:14:11.600 --> 00:14:13.000 align:start position:0% that quickly for us it was kind of a great<00:14:11.870> learning<00:14:12.170> experiment<00:14:12.440> working<00:14:12.740> to 00:14:13.000 --> 00:14:13.010 align:start position:0% great learning experiment working to 00:14:13.010 --> 00:14:14.829 align:start position:0% great learning experiment working to generalize<00:14:13.400> or<00:14:13.670> framework<00:14:14.030> to<00:14:14.390> make<00:14:14.480> it<00:14:14.630> much 00:14:14.829 --> 00:14:14.839 align:start position:0% generalize or framework to make it much 00:14:14.839 --> 00:14:16.960 align:start position:0% generalize or framework to make it much easier<00:14:15.080> to<00:14:15.320> recognize<00:14:15.680> those<00:14:16.100> those<00:14:16.580> clients 00:14:16.960 --> 00:14:16.970 align:start position:0% easier to recognize those those clients 00:14:16.970 --> 00:14:19.890 align:start position:0% easier to recognize those those clients without<00:14:17.210> changes<00:14:17.600> as<00:14:18.170> much<00:14:18.200> as<00:14:18.500> possible 00:14:19.890 --> 00:14:19.900 align:start position:0% without changes as much as possible 00:14:19.900 --> 00:14:22.090 align:start position:0% without changes as much as possible so<00:14:20.900> discovery 00:14:22.090 --> 00:14:22.100 align:start position:0% so discovery 00:14:22.100 --> 00:14:25.120 align:start position:0% so discovery I<00:14:22.270> love<00:14:23.270> discovery<00:14:23.720> v5<00:14:24.050> I<00:14:24.320> need<00:14:24.920> to<00:14:25.010> make 00:14:25.120 --> 00:14:25.130 align:start position:0% I love discovery v5 I need to make 00:14:25.130 --> 00:14:29.110 align:start position:0% I love discovery v5 I need to make stickers<00:14:25.430> for<00:14:25.640> this<00:14:26.710> it's<00:14:27.710> a<00:14:27.890> big<00:14:28.100> change<00:14:28.430> from 00:14:29.110 --> 00:14:29.120 align:start position:0% stickers for this it's a big change from 00:14:29.120 --> 00:14:31.780 align:start position:0% stickers for this it's a big change from each<00:14:29.300> one<00:14:29.890> you<00:14:30.890> know<00:14:30.980> an<00:14:31.070> if<00:14:31.190> one<00:14:31.370> you<00:14:31.490> used<00:14:31.670> to 00:14:31.780 --> 00:14:31.790 align:start position:0% each one you know an if one you used to 00:14:31.790 --> 00:14:33.850 align:start position:0% each one you know an if one you used to have<00:14:31.940> just<00:14:32.240> the<00:14:32.420> URL<00:14:32.870> being<00:14:33.290> broadcasted<00:14:33.800> to 00:14:33.850 --> 00:14:33.860 align:start position:0% have just the URL being broadcasted to 00:14:33.860 --> 00:14:35.500 align:start position:0% have just the URL being broadcasted to all<00:14:33.950> your<00:14:34.190> peers<00:14:34.430> and<00:14:34.640> you<00:14:35.030> would<00:14:35.150> have<00:14:35.330> those 00:14:35.500 --> 00:14:35.510 align:start position:0% all your peers and you would have those 00:14:35.510 --> 00:14:37.510 align:start position:0% all your peers and you would have those kimia<00:14:36.170> buckets<00:14:36.500> where<00:14:36.770> it<00:14:37.220> would<00:14:37.370> be 00:14:37.510 --> 00:14:37.520 align:start position:0% kimia buckets where it would be 00:14:37.520 --> 00:14:39.880 align:start position:0% kimia buckets where it would be organized<00:14:37.940> in<00:14:38.660> Discovery<00:14:39.050> v5<00:14:39.410> you<00:14:39.589> now<00:14:39.710> have 00:14:39.880 --> 00:14:39.890 align:start position:0% organized in Discovery v5 you now have 00:14:39.890 --> 00:14:42.010 align:start position:0% organized in Discovery v5 you now have the<00:14:40.130> notion<00:14:40.280> of<00:14:40.490> if<00:14:40.730> am<00:14:41.000> not<00:14:41.210> records<00:14:41.600> which 00:14:42.010 --> 00:14:42.020 align:start position:0% the notion of if am not records which 00:14:42.020 --> 00:14:43.990 align:start position:0% the notion of if am not records which are<00:14:42.170> still<00:14:42.530> signs<00:14:42.770> or<00:14:43.010> still<00:14:43.339> making<00:14:43.790> sense 00:14:43.990 --> 00:14:44.000 align:start position:0% are still signs or still making sense 00:14:44.000 --> 00:14:46.270 align:start position:0% are still signs or still making sense it's<00:14:44.690> a<00:14:44.720> little<00:14:44.930> bit<00:14:45.020> of<00:14:45.140> security<00:14:45.320> can<00:14:45.770> do<00:14:45.890> and 00:14:46.270 --> 00:14:46.280 align:start position:0% it's a little bit of security can do and 00:14:46.280 --> 00:14:48.430 align:start position:0% it's a little bit of security can do and handshake<00:14:46.730> so<00:14:46.940> you<00:14:47.270> can<00:14:47.450> kind<00:14:47.780> of<00:14:47.810> make<00:14:48.290> sure 00:14:48.430 --> 00:14:48.440 align:start position:0% handshake so you can kind of make sure 00:14:48.440 --> 00:14:52.030 align:start position:0% handshake so you can kind of make sure not<00:14:48.650> being<00:14:48.860> spammed<00:14:49.190> as<00:14:49.700> much<00:14:50.530> but<00:14:51.530> what<00:14:51.830> comes 00:14:52.030 --> 00:14:52.040 align:start position:0% not being spammed as much but what comes 00:14:52.040 --> 00:14:54.970 align:start position:0% not being spammed as much but what comes with<00:14:52.339> in<00:14:52.850> ours<00:14:53.180> is<00:14:53.630> now<00:14:53.810> the<00:14:53.870> ability<00:14:54.350> for<00:14:54.860> you 00:14:54.970 --> 00:14:54.980 align:start position:0% with in ours is now the ability for you 00:14:54.980 --> 00:14:57.490 align:start position:0% with in ours is now the ability for you to<00:14:55.010> have<00:14:55.310> in<00:14:56.000> those<00:14:56.150> key<00:14:56.720> value<00:14:56.839> pairs<00:14:57.230> you<00:14:57.440> can 00:14:57.490 --> 00:14:57.500 align:start position:0% to have in those key value pairs you can 00:14:57.500 --> 00:14:59.860 align:start position:0% to have in those key value pairs you can arbitrary<00:14:58.220> stowing<00:14:58.670> them<00:14:58.880> a<00:14:59.089> notion<00:14:59.810> of 00:14:59.860 --> 00:14:59.870 align:start position:0% arbitrary stowing them a notion of 00:14:59.870 --> 00:15:02.320 align:start position:0% arbitrary stowing them a notion of topics<00:15:00.260> so<00:15:00.589> you<00:15:00.680> can<00:15:00.830> actually<00:15:00.970> when<00:15:01.970> you<00:15:02.089> come 00:15:02.320 --> 00:15:02.330 align:start position:0% topics so you can actually when you come 00:15:02.330 --> 00:15:04.180 align:start position:0% topics so you can actually when you come in<00:15:02.480> you<00:15:02.959> know<00:15:02.990> podcast<00:15:03.260> you<00:15:03.589> stuff<00:15:03.800> to<00:15:03.920> others 00:15:04.180 --> 00:15:04.190 align:start position:0% in you know podcast you stuff to others 00:15:04.190 --> 00:15:06.280 align:start position:0% in you know podcast you stuff to others tell<00:15:04.610> that<00:15:04.820> you're<00:15:05.089> in<00:15:05.180> if<00:15:05.300> -<00:15:05.480> node<00:15:05.900> or<00:15:06.110> you're 00:15:06.280 --> 00:15:06.290 align:start position:0% tell that you're in if - node or you're 00:15:06.290 --> 00:15:08.590 align:start position:0% tell that you're in if - node or you're an<00:15:06.380> East<00:15:06.560> 1<00:15:06.770> node<00:15:06.950> or<00:15:07.190> you'll<00:15:08.120> poke<00:15:08.360> it<00:15:08.480> out 00:15:08.590 --> 00:15:08.600 align:start position:0% an East 1 node or you'll poke it out 00:15:08.600 --> 00:15:10.990 align:start position:0% an East 1 node or you'll poke it out node<00:15:08.779> right<00:15:09.260> so<00:15:09.529> this<00:15:09.740> allows<00:15:10.220> all<00:15:10.550> the<00:15:10.730> block 00:15:10.990 --> 00:15:11.000 align:start position:0% node right so this allows all the block 00:15:11.000 --> 00:15:13.620 align:start position:0% node right so this allows all the block chains<00:15:11.209> to<00:15:11.360> also<00:15:11.570> participate<00:15:11.800> in<00:15:12.800> a<00:15:12.860> global 00:15:13.620 --> 00:15:13.630 align:start position:0% chains to also participate in a global 00:15:13.630 --> 00:15:16.600 align:start position:0% chains to also participate in a global DHT<00:15:14.630> is<00:15:15.290> nucleate<00:15:15.709> immunity<00:15:16.010> HT<00:15:16.279> which<00:15:16.430> is 00:15:16.600 --> 00:15:16.610 align:start position:0% DHT is nucleate immunity HT which is 00:15:16.610 --> 00:15:20.170 align:start position:0% DHT is nucleate immunity HT which is also<00:15:17.209> simpler<00:15:17.630> than<00:15:17.990> it<00:15:18.110> used<00:15:18.260> to<00:15:18.290> be<00:15:18.820> so<00:15:19.820> it's 00:15:20.170 --> 00:15:20.180 align:start position:0% also simpler than it used to be so it's 00:15:20.180 --> 00:15:22.690 align:start position:0% also simpler than it used to be so it's going<00:15:20.510> to<00:15:20.690> allow<00:15:21.080> better<00:15:21.380> security<00:15:21.800> right<00:15:22.310> so 00:15:22.690 --> 00:15:22.700 align:start position:0% going to allow better security right so 00:15:22.700 --> 00:15:25.840 align:start position:0% going to allow better security right so like<00:15:22.970> six<00:15:23.900> months<00:15:24.050> ago<00:15:24.370> French<00:15:25.370> came<00:15:25.610> to<00:15:25.760> New 00:15:25.840 --> 00:15:25.850 align:start position:0% like six months ago French came to New 00:15:25.850 --> 00:15:28.420 align:start position:0% like six months ago French came to New York<00:15:25.970> and<00:15:26.590> one<00:15:27.590> thing<00:15:27.800> that<00:15:27.920> I<00:15:27.950> mentioned<00:15:28.340> is 00:15:28.420 --> 00:15:28.430 align:start position:0% York and one thing that I mentioned is 00:15:28.430 --> 00:15:30.250 align:start position:0% York and one thing that I mentioned is that<00:15:28.460> dc5<00:15:29.090> will<00:15:29.270> only<00:15:29.420> work<00:15:29.660> if<00:15:29.840> you<00:15:29.930> have<00:15:30.020> over 00:15:30.250 --> 00:15:30.260 align:start position:0% that dc5 will only work if you have over 00:15:30.260 --> 00:15:32.410 align:start position:0% that dc5 will only work if you have over thousand<00:15:30.830> nodes<00:15:30.980> running<00:15:31.550> it<00:15:31.670> otherwise<00:15:32.270> the 00:15:32.410 --> 00:15:32.420 align:start position:0% thousand nodes running it otherwise the 00:15:32.420 --> 00:15:34.660 align:start position:0% thousand nodes running it otherwise the security<00:15:32.900> is<00:15:33.440> going<00:15:33.800> to<00:15:33.890> be<00:15:33.950> compromised<00:15:34.490> by 00:15:34.660 --> 00:15:34.670 align:start position:0% security is going to be compromised by 00:15:34.670 --> 00:15:38.200 align:start position:0% security is going to be compromised by eclipse<00:15:35.000> attacks<00:15:35.330> very<00:15:35.960> quickly<00:15:36.280> so<00:15:37.280> this<00:15:38.030> is 00:15:38.200 --> 00:15:38.210 align:start position:0% eclipse attacks very quickly so this is 00:15:38.210 --> 00:15:40.750 align:start position:0% eclipse attacks very quickly so this is a<00:15:38.240> huge<00:15:38.540> effort<00:15:38.720> going<00:15:39.200> to<00:15:39.380> allow<00:15:39.770> if<00:15:40.400> one<00:15:40.640> in 00:15:40.750 --> 00:15:40.760 align:start position:0% a huge effort going to allow if one in 00:15:40.760 --> 00:15:42.610 align:start position:0% a huge effort going to allow if one in if<00:15:40.940> to<00:15:41.150> to<00:15:41.300> also<00:15:41.540> share<00:15:41.750> some<00:15:42.020> of<00:15:42.140> the<00:15:42.200> work<00:15:42.380> and 00:15:42.610 --> 00:15:42.620 align:start position:0% if to to also share some of the work and 00:15:42.620 --> 00:15:45.460 align:start position:0% if to to also share some of the work and to<00:15:43.190> share<00:15:43.400> some<00:15:43.430> of<00:15:43.670> the<00:15:43.880> infrastructure<00:15:44.470> so 00:15:45.460 --> 00:15:45.470 align:start position:0% to share some of the infrastructure so 00:15:45.470 --> 00:15:47.500 align:start position:0% to share some of the infrastructure so really<00:15:46.010> excited<00:15:46.310> about<00:15:46.370> this<00:15:46.580> is<00:15:46.790> a<00:15:46.820> network 00:15:47.500 --> 00:15:47.510 align:start position:0% really excited about this is a network 00:15:47.510 --> 00:15:51.820 align:start position:0% really excited about this is a network geek<00:15:48.040> so<00:15:49.360> next<00:15:50.360> steps<00:15:50.570> for<00:15:50.660> us<00:15:50.780> so<00:15:51.620> we're 00:15:51.820 --> 00:15:51.830 align:start position:0% geek so next steps for us so we're 00:15:51.830 --> 00:15:55.150 align:start position:0% geek so next steps for us so we're recipient<00:15:52.310> on<00:15:52.430> EF<00:15:52.640> grant<00:15:53.140> we<00:15:54.140> think<00:15:54.410> we<00:15:54.740> think 00:15:55.150 --> 00:15:55.160 align:start position:0% recipient on EF grant we think we think 00:15:55.160 --> 00:15:57.670 align:start position:0% recipient on EF grant we think we think if<00:15:55.940> M<00:15:56.120> foundation<00:15:56.570> for<00:15:56.780> helping<00:15:57.260> us<00:15:57.410> in 00:15:57.670 --> 00:15:57.680 align:start position:0% if M foundation for helping us in 00:15:57.680 --> 00:15:59.860 align:start position:0% if M foundation for helping us in sponsoring<00:15:58.190> this<00:15:58.340> effort<00:15:58.670> we're<00:15:59.630> going<00:15:59.780> to 00:15:59.860 --> 00:15:59.870 align:start position:0% sponsoring this effort we're going to 00:15:59.870 --> 00:16:02.020 align:start position:0% sponsoring this effort we're going to continue<00:16:00.110> working<00:16:00.410> on<00:16:00.800> some<00:16:01.340> of<00:16:01.460> the<00:16:01.580> tests 00:16:02.020 --> 00:16:02.030 align:start position:0% continue working on some of the tests 00:16:02.030 --> 00:16:04.090 align:start position:0% continue working on some of the tests for<00:16:02.420> SPECT<00:16:03.290> conformance<00:16:03.710> in<00:16:03.830> terms<00:16:03.980> of 00:16:04.090 --> 00:16:04.100 align:start position:0% for SPECT conformance in terms of 00:16:04.100 --> 00:16:05.980 align:start position:0% for SPECT conformance in terms of networking<00:16:04.460> so<00:16:04.850> we're<00:16:05.420> going<00:16:05.570> to<00:16:05.660> be<00:16:05.780> able<00:16:05.840> to 00:16:05.980 --> 00:16:05.990 align:start position:0% networking so we're going to be able to 00:16:05.990 --> 00:16:09.970 align:start position:0% networking so we're going to be able to replay<00:16:06.740> traffic<00:16:07.630> send<00:16:08.630> can<00:16:09.290> request<00:16:09.650> make 00:16:09.970 --> 00:16:09.980 align:start position:0% replay traffic send can request make 00:16:09.980 --> 00:16:11.230 align:start position:0% replay traffic send can request make sure<00:16:10.130> that<00:16:10.310> we're<00:16:10.490> getting<00:16:10.580> the<00:16:10.700> response<00:16:11.090> we 00:16:11.230 --> 00:16:11.240 align:start position:0% sure that we're getting the response we 00:16:11.240 --> 00:16:13.630 align:start position:0% sure that we're getting the response we expect<00:16:11.570> across<00:16:12.020> all<00:16:12.170> the<00:16:12.260> clients<00:16:12.620> it's<00:16:13.460> kind 00:16:13.630 --> 00:16:13.640 align:start position:0% expect across all the clients it's kind 00:16:13.640 --> 00:16:16.260 align:start position:0% expect across all the clients it's kind of<00:16:13.670> at<00:16:13.970> the<00:16:14.090> unit<00:16:14.390> testing<00:16:14.690> level<00:16:15.320> if<00:16:15.620> you<00:16:15.770> want 00:16:16.260 --> 00:16:16.270 align:start position:0% of at the unit testing level if you want 00:16:16.270 --> 00:16:19.600 align:start position:0% of at the unit testing level if you want and<00:16:17.270> we've<00:16:17.900> been<00:16:18.050> talking<00:16:18.230> along<00:16:18.590> long<00:16:19.430> last 00:16:19.600 --> 00:16:19.610 align:start position:0% and we've been talking along long last 00:16:19.610 --> 00:16:22.030 align:start position:0% and we've been talking along long last about<00:16:19.910> the<00:16:19.970> lipids<00:16:20.510> because<00:16:20.810> if<00:16:20.960> sub<00:16:21.200> testing 00:16:22.030 --> 00:16:22.040 align:start position:0% about the lipids because if sub testing 00:16:22.040 --> 00:16:24.070 align:start position:0% about the lipids because if sub testing so<00:16:22.190> we'll<00:16:22.340> continue<00:16:22.520> eating<00:16:22.940> that<00:16:23.210> we<00:16:23.810> want<00:16:23.990> to 00:16:24.070 --> 00:16:24.080 align:start position:0% so we'll continue eating that we want to 00:16:24.080 --> 00:16:26.860 align:start position:0% so we'll continue eating that we want to kind<00:16:24.200> of<00:16:24.290> have<00:16:24.470> a<00:16:24.500> hand<00:16:25.430> in<00:16:25.520> this<00:16:25.700> make<00:16:26.690> sure 00:16:26.860 --> 00:16:26.870 align:start position:0% kind of have a hand in this make sure 00:16:26.870 --> 00:16:28.060 align:start position:0% kind of have a hand in this make sure that<00:16:26.990> all<00:16:27.170> the<00:16:27.290> configuration<00:16:27.920> parameters 00:16:28.060 --> 00:16:28.070 align:start position:0% that all the configuration parameters 00:16:28.070 --> 00:16:30.160 align:start position:0% that all the configuration parameters are<00:16:28.580> kind<00:16:28.730> of<00:16:28.760> optimized<00:16:29.300> for<00:16:29.570> the<00:16:29.780> workload 00:16:30.160 --> 00:16:30.170 align:start position:0% are kind of optimized for the workload 00:16:30.170 --> 00:16:34.450 align:start position:0% are kind of optimized for the workload of<00:16:30.200> if<00:16:30.470> to<00:16:30.970> and<00:16:32.260> we're<00:16:33.260> pretty<00:16:33.470> close<00:16:33.680> to<00:16:33.860> being 00:16:34.450 --> 00:16:34.460 align:start position:0% of if to and we're pretty close to being 00:16:34.460 --> 00:16:36.010 align:start position:0% of if to and we're pretty close to being able<00:16:34.520> to<00:16:34.670> do<00:16:34.850> a<00:16:34.880> lot<00:16:35.030> a<00:16:35.090> client<00:16:35.450> test<00:16:35.660> met<00:16:35.810> with 00:16:36.010 --> 00:16:36.020 align:start position:0% able to do a lot a client test met with 00:16:36.020 --> 00:16:37.720 align:start position:0% able to do a lot a client test met with all<00:16:36.260> the<00:16:36.410> production<00:16:36.770> ready<00:16:36.920> clients<00:16:37.340> does 00:16:37.720 --> 00:16:37.730 align:start position:0% all the production ready clients does 00:16:37.730 --> 00:16:39.400 align:start position:0% all the production ready clients does the<00:16:37.850> idea<00:16:38.090> there<00:16:38.300> is<00:16:38.330> that<00:16:38.420> every<00:16:39.230> time 00:16:39.400 --> 00:16:39.410 align:start position:0% the idea there is that every time 00:16:39.410 --> 00:16:41.830 align:start position:0% the idea there is that every time there's<00:16:39.620> a<00:16:39.680> new<00:16:39.860> docker<00:16:40.580> image<00:16:40.910> for<00:16:41.330> Trinity 00:16:41.830 --> 00:16:41.840 align:start position:0% there's a new docker image for Trinity 00:16:41.840 --> 00:16:44.050 align:start position:0% there's a new docker image for Trinity or<00:16:41.870> lighthouse<00:16:42.440> or<00:16:42.710> Artemis<00:16:43.070> or<00:16:43.250> anything<00:16:43.430> we 00:16:44.050 --> 00:16:44.060 align:start position:0% or lighthouse or Artemis or anything we 00:16:44.060 --> 00:16:46.660 align:start position:0% or lighthouse or Artemis or anything we can<00:16:44.240> pick<00:16:44.420> that<00:16:44.570> up<00:16:44.860> insert<00:16:45.860> it<00:16:46.010> into<00:16:46.220> the<00:16:46.460> test 00:16:46.660 --> 00:16:46.670 align:start position:0% can pick that up insert it into the test 00:16:46.670 --> 00:16:49.420 align:start position:0% can pick that up insert it into the test net<00:16:47.140> try<00:16:48.140> it<00:16:48.200> out<00:16:48.350> see<00:16:48.710> if<00:16:48.740> it's<00:16:48.950> behaving 00:16:49.420 --> 00:16:49.430 align:start position:0% net try it out see if it's behaving 00:16:49.430 --> 00:16:51.580 align:start position:0% net try it out see if it's behaving correctly<00:16:49.750> it's<00:16:50.750> still<00:16:50.960> able<00:16:51.050> to<00:16:51.200> find<00:16:51.440> out 00:16:51.580 --> 00:16:51.590 align:start position:0% correctly it's still able to find out 00:16:51.590 --> 00:16:53.950 align:start position:0% correctly it's still able to find out the<00:16:51.740> blog<00:16:51.920> sources<00:16:52.340> good<00:16:52.490> stuff 00:16:53.950 --> 00:16:53.960 align:start position:0% the blog sources good stuff 00:16:53.960 --> 00:16:56.410 align:start position:0% the blog sources good stuff so<00:16:54.710> not<00:16:54.920> to<00:16:55.040> put<00:16:55.190> words<00:16:55.220> into<00:16:55.610> the<00:16:55.850> if<00:16:56.210> to 00:16:56.410 --> 00:16:56.420 align:start position:0% so not to put words into the if to 00:16:56.420 --> 00:16:59.980 align:start position:0% so not to put words into the if to clients<00:16:57.370> implementers<00:16:58.370> mouth<00:16:58.550> but<00:16:59.330> their 00:16:59.980 --> 00:16:59.990 align:start position:0% clients implementers mouth but their 00:16:59.990 --> 00:17:02.500 align:start position:0% clients implementers mouth but their heads<00:17:00.440> down<00:17:00.730> finishing<00:17:01.730> up<00:17:01.820> all<00:17:01.910> the<00:17:01.970> work<00:17:02.180> all 00:17:02.500 --> 00:17:02.510 align:start position:0% heads down finishing up all the work all 00:17:02.510 --> 00:17:05.140 align:start position:0% heads down finishing up all the work all the<00:17:02.780> details<00:17:03.140> of<00:17:03.380> each<00:17:03.560> cases<00:17:04.070> all<00:17:04.610> the<00:17:04.790> things 00:17:05.140 --> 00:17:05.150 align:start position:0% the details of each cases all the things 00:17:05.150 --> 00:17:07.210 align:start position:0% the details of each cases all the things that<00:17:05.300> are<00:17:05.480> kind<00:17:05.930> of<00:17:06.020> sticking<00:17:06.290> out<00:17:06.530> really 00:17:07.210 --> 00:17:07.220 align:start position:0% that are kind of sticking out really 00:17:07.220 --> 00:17:10.390 align:start position:0% that are kind of sticking out really stabilizing<00:17:07.850> the<00:17:08.000> implementations<00:17:08.810> and<00:17:09.400> we 00:17:10.390 --> 00:17:10.400 align:start position:0% stabilizing the implementations and we 00:17:10.400 --> 00:17:12.460 align:start position:0% stabilizing the implementations and we want<00:17:10.579> to<00:17:10.640> help<00:17:10.850> them<00:17:11.030> get<00:17:11.660> the<00:17:11.870> safety<00:17:12.230> that 00:17:12.460 --> 00:17:12.470 align:start position:0% want to help them get the safety that 00:17:12.470 --> 00:17:16.800 align:start position:0% want to help them get the safety that they<00:17:12.560> need<00:17:12.709> to<00:17:12.740> declare<00:17:13.579> facial<00:17:14.030> release<00:17:14.300> and 00:17:16.800 --> 00:17:16.810 align:start position:0% they need to declare facial release and 00:17:16.810 --> 00:17:21.910 align:start position:0% they need to declare facial release and that<00:17:17.810> they<00:17:18.770> call<00:17:18.920> your<00:17:19.040> questions 00:17:21.910 --> 00:17:21.920 align:start position:0% 00:17:21.920 --> 00:17:24.500 align:start position:0% you're<00:17:22.920> asking<00:17:23.339> how<00:17:23.490> how<00:17:23.850> things<00:17:24.089> went<00:17:24.270> and 00:17:24.500 --> 00:17:24.510 align:start position:0% you're asking how how things went and 00:17:24.510 --> 00:17:26.569 align:start position:0% you're asking how how things went and how<00:17:24.660> who<00:17:24.990> started<00:17:25.380> first<00:17:25.620> is<00:17:25.890> it<00:17:26.010> a<00:17:26.100> spec 00:17:26.569 --> 00:17:26.579 align:start position:0% how who started first is it a spec 00:17:26.579 --> 00:17:34.010 align:start position:0% how who started first is it a spec effort<00:17:26.910> or<00:17:27.060> is<00:17:27.150> it<00:17:27.270> uh<00:17:31.790> yeah<00:17:32.790> so<00:17:33.090> it's<00:17:33.750> it's 00:17:34.010 --> 00:17:34.020 align:start position:0% effort or is it uh yeah so it's it's 00:17:34.020 --> 00:17:36.380 align:start position:0% effort or is it uh yeah so it's it's interesting<00:17:34.410> so<00:17:34.710> there's<00:17:34.950> been<00:17:35.190> first<00:17:36.090> like 00:17:36.380 --> 00:17:36.390 align:start position:0% interesting so there's been first like 00:17:36.390 --> 00:17:38.600 align:start position:0% interesting so there's been first like some<00:17:37.050> min<00:17:37.560> Devine<00:17:37.830> talking<00:17:38.190> about<00:17:38.370> if<00:17:38.490> two 00:17:38.600 --> 00:17:38.610 align:start position:0% some min Devine talking about if two 00:17:38.610 --> 00:17:40.070 align:start position:0% some min Devine talking about if two four<00:17:38.790> years<00:17:39.000> right<00:17:39.240> so<00:17:39.510> there's<00:17:39.780> a<00:17:39.840> lot<00:17:40.050> of 00:17:40.070 --> 00:17:40.080 align:start position:0% four years right so there's a lot of 00:17:40.080 --> 00:17:41.510 align:start position:0% four years right so there's a lot of like<00:17:40.500> different<00:17:40.830> initiatives<00:17:41.340> and<00:17:41.490> efforts 00:17:41.510 --> 00:17:41.520 align:start position:0% like different initiatives and efforts 00:17:41.520 --> 00:17:44.870 align:start position:0% like different initiatives and efforts by<00:17:41.820> vitalik<00:17:42.560> eventually<00:17:43.560> the<00:17:44.310> research<00:17:44.610> team 00:17:44.870 --> 00:17:44.880 align:start position:0% by vitalik eventually the research team 00:17:44.880 --> 00:17:47.240 align:start position:0% by vitalik eventually the research team around<00:17:45.120> if<00:17:45.360> to<00:17:45.570> kind<00:17:45.900> of<00:17:45.960> solidified<00:17:46.590> with 00:17:47.240 --> 00:17:47.250 align:start position:0% around if to kind of solidified with 00:17:47.250 --> 00:17:50.300 align:start position:0% around if to kind of solidified with Danny<00:17:47.520> ryan<00:17:47.790> kind<00:17:48.030> of<00:17:48.120> helping<00:17:48.780> also<00:17:49.380> get<00:17:50.130> to<00:17:50.280> a 00:17:50.300 --> 00:17:50.310 align:start position:0% Danny ryan kind of helping also get to a 00:17:50.310 --> 00:17:53.030 align:start position:0% Danny ryan kind of helping also get to a point<00:17:50.490> where<00:17:50.730> he<00:17:50.760> could<00:17:51.200> name<00:17:52.200> releases<00:17:52.650> of 00:17:53.030 --> 00:17:53.040 align:start position:0% point where he could name releases of 00:17:53.040 --> 00:17:57.170 align:start position:0% point where he could name releases of the<00:17:53.970> spec<00:17:54.180> right<00:17:54.840> the<00:17:55.380> spec<00:17:55.620> was<00:17:56.310> written<00:17:56.640> by 00:17:57.170 --> 00:17:57.180 align:start position:0% the spec right the spec was written by 00:17:57.180 --> 00:17:59.630 align:start position:0% the spec right the spec was written by Justin<00:17:57.750> Drake<00:17:57.960> to<00:17:58.170> be<00:17:58.290> more<00:17:58.800> in<00:17:58.890> a<00:17:58.980> table 00:17:59.630 --> 00:17:59.640 align:start position:0% Justin Drake to be more in a table 00:17:59.640 --> 00:18:01.010 align:start position:0% Justin Drake to be more in a table format<00:17:59.940> so<00:18:00.090> it<00:18:00.210> could<00:18:00.360> actually<00:18:00.420> become<00:18:00.840> part 00:18:01.010 --> 00:18:01.020 align:start position:0% format so it could actually become part 00:18:01.020 --> 00:18:05.060 align:start position:0% format so it could actually become part of<00:18:01.440> the<00:18:01.590> testing<00:18:02.180> I<00:18:03.380> think<00:18:04.380> Pato<00:18:04.590> Liam<00:18:04.860> that 00:18:05.060 --> 00:18:05.070 align:start position:0% of the testing I think Pato Liam that 00:18:05.070 --> 00:18:08.180 align:start position:0% of the testing I think Pato Liam that really<00:18:05.310> helped<00:18:05.580> as<00:18:05.670> well<00:18:05.910> to<00:18:06.710> really<00:18:07.710> create 00:18:08.180 --> 00:18:08.190 align:start position:0% really helped as well to really create 00:18:08.190 --> 00:18:10.670 align:start position:0% really helped as well to really create testing<00:18:08.670> and<00:18:08.820> tooling<00:18:09.210> around<00:18:09.450> it<00:18:09.720> and<00:18:10.200> in 00:18:10.670 --> 00:18:10.680 align:start position:0% testing and tooling around it and in 00:18:10.680 --> 00:18:13.400 align:start position:0% testing and tooling around it and in parallel<00:18:10.980> all<00:18:11.340> the<00:18:11.670> I<00:18:12.240> mean<00:18:12.540> the 00:18:13.400 --> 00:18:13.410 align:start position:0% parallel all the I mean the 00:18:13.410 --> 00:18:14.660 align:start position:0% parallel all the I mean the implementation<00:18:13.950> I'm<00:18:14.070> most<00:18:14.220> familiar<00:18:14.310> with<00:18:14.520> is 00:18:14.660 --> 00:18:14.670 align:start position:0% implementation I'm most familiar with is 00:18:14.670 --> 00:18:17.630 align:start position:0% implementation I'm most familiar with is Artemis<00:18:15.330> for<00:18:15.510> example<00:18:15.930> right<00:18:16.200> and<00:18:16.640> what 00:18:17.630 --> 00:18:17.640 align:start position:0% Artemis for example right and what 00:18:17.640 --> 00:18:20.410 align:start position:0% Artemis for example right and what happened<00:18:18.030> is<00:18:18.120> I<00:18:18.150> had<00:18:18.240> a<00:18:18.390> lot<00:18:18.600> of<00:18:18.720> churn<00:18:19.020> because 00:18:20.410 --> 00:18:20.420 align:start position:0% happened is I had a lot of churn because 00:18:20.420 --> 00:18:23.360 align:start position:0% happened is I had a lot of churn because lots<00:18:21.420> of<00:18:21.540> moving<00:18:22.320> pieces<00:18:22.530> came<00:18:22.920> back<00:18:23.190> and 00:18:23.360 --> 00:18:23.370 align:start position:0% lots of moving pieces came back and 00:18:23.370 --> 00:18:25.610 align:start position:0% lots of moving pieces came back and forth<00:18:23.580> right<00:18:23.910> so<00:18:24.090> SSD<00:18:24.660> for<00:18:24.780> example<00:18:25.170> at<00:18:25.230> three 00:18:25.610 --> 00:18:25.620 align:start position:0% forth right so SSD for example at three 00:18:25.620 --> 00:18:27.950 align:start position:0% forth right so SSD for example at three or<00:18:25.830> four<00:18:26.240> incompatible<00:18:27.240> designs<00:18:27.630> to<00:18:27.870> each 00:18:27.950 --> 00:18:27.960 align:start position:0% or four incompatible designs to each 00:18:27.960 --> 00:18:30.470 align:start position:0% or four incompatible designs to each other<00:18:28.140> until<00:18:29.010> the<00:18:29.160> point<00:18:29.370> that<00:18:29.490> they<00:18:29.850> agreed 00:18:30.470 --> 00:18:30.480 align:start position:0% other until the point that they agreed 00:18:30.480 --> 00:18:32.540 align:start position:0% other until the point that they agreed on<00:18:30.510> all<00:18:30.720> of<00:18:30.840> this<00:18:30.930> so<00:18:31.260> every<00:18:31.980> little<00:18:32.190> piece<00:18:32.490> of 00:18:32.540 --> 00:18:32.550 align:start position:0% on all of this so every little piece of 00:18:32.550 --> 00:18:34.730 align:start position:0% on all of this so every little piece of the<00:18:32.820> spec<00:18:33.060> kept<00:18:33.360> changing<00:18:33.630> as<00:18:34.260> part<00:18:34.620> of 00:18:34.730 --> 00:18:34.740 align:start position:0% the spec kept changing as part of 00:18:34.740 --> 00:18:41.480 align:start position:0% the spec kept changing as part of decisions<00:18:35.280> down<00:18:35.460> the<00:18:35.670> road<00:18:38.150> yeah<00:18:40.490> networking 00:18:41.480 --> 00:18:41.490 align:start position:0% decisions down the road yeah networking 00:18:41.490 --> 00:18:43.610 align:start position:0% decisions down the road yeah networking is<00:18:41.700> not<00:18:41.910> done<00:18:42.150> anything<00:18:42.480> so<00:18:43.050> they're<00:18:43.200> a<00:18:43.230> couple 00:18:43.610 --> 00:18:43.620 align:start position:0% is not done anything so they're a couple 00:18:43.620 --> 00:18:45.710 align:start position:0% is not done anything so they're a couple fees<00:18:43.860> networking<00:18:44.370> one<00:18:44.490> is<00:18:44.670> the<00:18:45.150> wire<00:18:45.270> protocol 00:18:45.710 --> 00:18:45.720 align:start position:0% fees networking one is the wire protocol 00:18:45.720 --> 00:18:47.510 align:start position:0% fees networking one is the wire protocol we're<00:18:46.080> getting<00:18:46.350> to<00:18:46.530> a<00:18:46.560> point<00:18:46.590> where<00:18:46.980> we<00:18:47.340> have<00:18:47.490> a 00:18:47.510 --> 00:18:47.520 align:start position:0% we're getting to a point where we have a 00:18:47.520 --> 00:18:49.910 align:start position:0% we're getting to a point where we have a good<00:18:47.730> idea<00:18:48.060> gossiping<00:18:48.990> is<00:18:49.410> actually<00:18:49.710> pretty 00:18:49.910 --> 00:18:49.920 align:start position:0% good idea gossiping is actually pretty 00:18:49.920 --> 00:18:51.350 align:start position:0% good idea gossiping is actually pretty easy<00:18:49.950> because<00:18:50.100> you<00:18:50.490> just<00:18:50.670> use<00:18:50.820> gossip<00:18:51.150> sub 00:18:51.350 --> 00:18:51.360 align:start position:0% easy because you just use gossip sub 00:18:51.360 --> 00:18:52.490 align:start position:0% easy because you just use gossip sub just<00:18:51.570> send<00:18:51.840> all<00:18:51.960> the<00:18:52.110> blocks<00:18:52.320> all<00:18:52.470> the 00:18:52.490 --> 00:18:52.500 align:start position:0% just send all the blocks all the 00:18:52.500 --> 00:18:55.040 align:start position:0% just send all the blocks all the stations<00:18:53.100> that<00:18:53.160> you<00:18:53.280> have<00:18:53.520> Susana<00:18:54.480> is<00:18:54.600> not<00:18:54.870> too 00:18:55.040 --> 00:18:55.050 align:start position:0% stations that you have Susana is not too 00:18:55.050 --> 00:18:57.260 align:start position:0% stations that you have Susana is not too much<00:18:55.170> of<00:18:55.320> a<00:18:55.380> problem<00:18:55.620> in<00:18:56.190> terms<00:18:56.490> of<00:18:56.700> sinking 00:18:57.260 --> 00:18:57.270 align:start position:0% much of a problem in terms of sinking 00:18:57.270 --> 00:18:59.810 align:start position:0% much of a problem in terms of sinking the<00:18:57.770> the<00:18:58.770> team<00:18:58.950> right<00:18:59.160> now<00:18:59.190> are<00:18:59.340> talking<00:18:59.730> about 00:18:59.810 --> 00:18:59.820 align:start position:0% the the team right now are talking about 00:18:59.820 --> 00:19:01.730 align:start position:0% the the team right now are talking about different<00:18:59.970> sinking<00:19:00.480> strategies<00:19:00.990> if<00:19:01.590> you 00:19:01.730 --> 00:19:01.740 align:start position:0% different sinking strategies if you 00:19:01.740 --> 00:19:03.200 align:start position:0% different sinking strategies if you familiar<00:19:02.040> with<00:19:02.070> if<00:19:02.250> one<00:19:02.460> and<00:19:02.730> all<00:19:02.970> the<00:19:03.000> ways 00:19:03.200 --> 00:19:03.210 align:start position:0% familiar with if one and all the ways 00:19:03.210 --> 00:19:04.910 align:start position:0% familiar with if one and all the ways you<00:19:03.330> can<00:19:03.450> sink<00:19:03.750> there<00:19:04.080> are<00:19:04.170> so<00:19:04.470> many<00:19:04.590> ways<00:19:04.830> you 00:19:04.910 --> 00:19:04.920 align:start position:0% you can sink there are so many ways you 00:19:04.920 --> 00:19:06.920 align:start position:0% you can sink there are so many ways you can<00:19:04.980> do<00:19:05.220> this<00:19:05.370> right<00:19:06.210> it's<00:19:06.420> still<00:19:06.630> something 00:19:06.920 --> 00:19:06.930 align:start position:0% can do this right it's still something 00:19:06.930 --> 00:19:10.580 align:start position:0% can do this right it's still something that<00:19:07.080> is<00:19:07.380> an<00:19:07.530> active<00:19:07.830> research<00:19:08.160> and<00:19:09.380> our<00:19:10.380> time 00:19:10.580 --> 00:19:10.590 align:start position:0% that is an active research and our time 00:19:10.590 --> 00:19:12.910 align:start position:0% that is an active research and our time is<00:19:10.620> up 00:19:12.910 --> 00:19:12.920 align:start position:0% 00:19:12.920 --> 00:19:15.100 align:start position:0% so<00:19:13.490> yeah<00:19:13.850> there's<00:19:14.090> more<00:19:14.270> and<00:19:14.450> there's<00:19:14.570> no<00:19:14.720> RPC 00:19:15.100 --> 00:19:15.110 align:start position:0% so yeah there's more and there's no RPC 00:19:15.110 --> 00:19:17.590 align:start position:0% so yeah there's more and there's no RPC interface<00:19:15.170> for<00:19:15.620> if<00:19:15.710> two<00:19:15.830> yet<00:19:16.010> as<00:19:16.600> Greg 00:19:17.590 --> 00:19:17.600 align:start position:0% interface for if two yet as Greg 00:19:17.600 --> 00:19:28.050 align:start position:0% interface for if two yet as Greg mentioned<00:19:17.630> yesterday<00:19:18.200> on<00:19:18.590> this<00:19:18.830> very<00:19:19.070> stage 00:19:28.050 --> 00:19:28.060 align:start position:0% 00:19:28.060 --> 00:19:30.070 align:start position:0% when<00:19:29.060> we<00:19:29.090> did<00:19:29.330> the<00:19:29.420> first<00:19:29.660> round<00:19:29.840> of<00:19:29.900> research 00:19:30.070 --> 00:19:30.080 align:start position:0% when we did the first round of research 00:19:30.080 --> 00:19:31.750 align:start position:0% when we did the first round of research we<00:19:30.440> found<00:19:30.650> that<00:19:30.740> the<00:19:30.860> median<00:19:31.130> time<00:19:31.310> was<00:19:31.520> pretty 00:19:31.750 --> 00:19:31.760 align:start position:0% we found that the median time was pretty 00:19:31.760 --> 00:19:34.930 align:start position:0% we found that the median time was pretty low<00:19:31.910> and<00:19:32.090> pretty<00:19:32.870> pretty<00:19:33.350> good<00:19:33.500> but<00:19:34.310> we<00:19:34.550> had<00:19:34.730> uh 00:19:34.930 --> 00:19:34.940 align:start position:0% low and pretty pretty good but we had uh 00:19:34.940 --> 00:19:37.870 align:start position:0% low and pretty pretty good but we had uh pliers<00:19:35.150> which<00:19:35.840> were<00:19:36.050> really<00:19:36.440> really<00:19:36.620> bad<00:19:36.880> so 00:19:37.870 --> 00:19:37.880 align:start position:0% pliers which were really really bad so 00:19:37.880 --> 00:19:39.370 align:start position:0% pliers which were really really bad so it<00:19:37.970> looks<00:19:38.120> like<00:19:38.210> the<00:19:38.540> routing<00:19:38.840> strategy<00:19:39.320> is 00:19:39.370 --> 00:19:39.380 align:start position:0% it looks like the routing strategy is 00:19:39.380 --> 00:19:42.790 align:start position:0% it looks like the routing strategy is not<00:19:39.500> always<00:19:39.650> optimal<00:19:40.570> I<00:19:41.570> think<00:19:42.470> that's<00:19:42.620> the 00:19:42.790 --> 00:19:42.800 align:start position:0% not always optimal I think that's the 00:19:42.800 --> 00:19:46.290 align:start position:0% not always optimal I think that's the only<00:19:42.830> hunch<00:19:43.190> I<00:19:43.340> really<00:19:43.550> have<00:19:43.700> at<00:19:43.820> this<00:19:43.940> point 00:19:46.290 --> 00:19:46.300 align:start position:0% 00:19:46.300 --> 00:19:50.710 align:start position:0% okay<00:19:47.300> so<00:19:48.760> how<00:19:49.760> we<00:19:49.820> scale<00:19:50.120> to<00:19:50.270> thousands<00:19:50.690> of 00:19:50.710 --> 00:19:50.720 align:start position:0% okay so how we scale to thousands of 00:19:50.720 --> 00:19:53.020 align:start position:0% okay so how we scale to thousands of nodes<00:19:50.990> in<00:19:51.620> our<00:19:51.860> testing<00:19:52.340> scenarios 00:19:53.020 --> 00:19:53.030 align:start position:0% nodes in our testing scenarios 00:19:53.030 --> 00:19:56.980 align:start position:0% nodes in our testing scenarios yes<00:19:53.930> so<00:19:54.610> right<00:19:55.610> now<00:19:55.790> what<00:19:55.910> we<00:19:56.180> do<00:19:56.390> is<00:19:56.630> we<00:19:56.870> do 00:19:56.980 --> 00:19:56.990 align:start position:0% yes so right now what we do is we do 00:19:56.990 --> 00:19:59.020 align:start position:0% yes so right now what we do is we do small-scale<00:19:57.470> testing<00:19:57.860> about<00:19:58.100> 30<00:19:58.400> to<00:19:58.550> 50<00:19:58.670> nodes 00:19:59.020 --> 00:19:59.030 align:start position:0% small-scale testing about 30 to 50 nodes 00:19:59.030 --> 00:20:01.930 align:start position:0% small-scale testing about 30 to 50 nodes our<00:19:59.510> firstly<00:19:59.960> p2p<00:20:00.350> testing<00:20:00.680> was<00:20:00.830> 100<00:20:01.340> in 00:20:01.930 --> 00:20:01.940 align:start position:0% our firstly p2p testing was 100 in 00:20:01.940 --> 00:20:04.780 align:start position:0% our firstly p2p testing was 100 in required<00:20:02.600> quite<00:20:02.780> a<00:20:02.840> bit<00:20:02.990> of<00:20:03.140> compute<00:20:03.790> right 00:20:04.780 --> 00:20:04.790 align:start position:0% required quite a bit of compute right 00:20:04.790 --> 00:20:06.430 align:start position:0% required quite a bit of compute right now<00:20:05.000> we<00:20:05.060> are<00:20:05.480> in<00:20:05.630> touch<00:20:05.810> with<00:20:06.020> that<00:20:06.080> research 00:20:06.430 --> 00:20:06.440 align:start position:0% now we are in touch with that research 00:20:06.440 --> 00:20:07.720 align:start position:0% now we are in touch with that research labs<00:20:06.650> came<00:20:06.920> to<00:20:07.070> give<00:20:07.250> us<00:20:07.280> pretty<00:20:07.580> much 00:20:07.720 --> 00:20:07.730 align:start position:0% labs came to give us pretty much 00:20:07.730 --> 00:20:09.970 align:start position:0% labs came to give us pretty much infinite<00:20:07.970> resources<00:20:08.660> across<00:20:08.870> the<00:20:09.350> u.s. 00:20:09.970 --> 00:20:09.980 align:start position:0% infinite resources across the u.s. 00:20:09.980 --> 00:20:12.340 align:start position:0% infinite resources across the u.s. continent<00:20:10.490> so<00:20:11.030> we'll<00:20:11.210> see<00:20:11.390> how<00:20:11.990> to<00:20:12.050> go<00:20:12.260> about 00:20:12.340 --> 00:20:12.350 align:start position:0% continent so we'll see how to go about 00:20:12.350 --> 00:20:15.400 align:start position:0% continent so we'll see how to go about that<00:20:12.620> we<00:20:13.400> run<00:20:13.580> docker<00:20:13.790> containers<00:20:14.300> so<00:20:14.960> we're 00:20:15.400 --> 00:20:15.410 align:start position:0% that we run docker containers so we're 00:20:15.410 --> 00:20:17.350 align:start position:0% that we run docker containers so we're pretty<00:20:15.680> agnostic<00:20:15.950> about<00:20:16.460> the<00:20:16.760> underlying 00:20:17.350 --> 00:20:17.360 align:start position:0% pretty agnostic about the underlying 00:20:17.360 --> 00:20:19.450 align:start position:0% pretty agnostic about the underlying hardware<00:20:17.870> we<00:20:18.560> you<00:20:19.010> know<00:20:19.100> we<00:20:19.190> run<00:20:19.310> on 00:20:19.450 --> 00:20:19.460 align:start position:0% hardware we you know we run on 00:20:19.460 --> 00:20:22.060 align:start position:0% hardware we you know we run on virtualized<00:20:19.910> cloud<00:20:20.150> software<00:20:20.660> like<00:20:21.350> GCP 00:20:22.060 --> 00:20:22.070 align:start position:0% virtualized cloud software like GCP 00:20:22.070 --> 00:20:24.550 align:start position:0% virtualized cloud software like GCP Amazon<00:20:22.820> Azure 00:20:24.550 --> 00:20:24.560 align:start position:0% Amazon Azure 00:20:24.560 --> 00:20:26.830 align:start position:0% Amazon Azure so<00:20:24.920> the<00:20:25.070> idea<00:20:25.250> is<00:20:25.310> we<00:20:25.790> just<00:20:25.970> add<00:20:26.330> more<00:20:26.600> and<00:20:26.720> more 00:20:26.830 --> 00:20:26.840 align:start position:0% so the idea is we just add more and more 00:20:26.840 --> 00:20:29.560 align:start position:0% so the idea is we just add more and more machines<00:20:26.990> about<00:20:27.650> 100<00:20:28.100> nodes<00:20:28.250> per<00:20:28.460> machines<00:20:28.790> to 00:20:29.560 --> 00:20:29.570 align:start position:0% machines about 100 nodes per machines to 00:20:29.570 --> 00:20:33.130 align:start position:0% machines about 100 nodes per machines to scale<00:20:29.990> to<00:20:30.050> that<00:20:31.030> we<00:20:32.030> try<00:20:32.240> not<00:20:32.510> to<00:20:32.750> do<00:20:32.900> the<00:20:33.080> other 00:20:33.130 --> 00:20:33.140 align:start position:0% scale to that we try not to do the other 00:20:33.140 --> 00:20:35.470 align:start position:0% scale to that we try not to do the other islands<00:20:33.440> of<00:20:33.500> nodes<00:20:33.790> from<00:20:34.790> experience<00:20:35.270> from 00:20:35.470 --> 00:20:35.480 align:start position:0% islands of nodes from experience from 00:20:35.480 --> 00:20:37.420 align:start position:0% islands of nodes from experience from practical<00:20:36.230> experience<00:20:36.290> we<00:20:36.800> study<00:20:37.040> notes<00:20:37.250> you 00:20:37.420 --> 00:20:37.430 align:start position:0% practical experience we study notes you 00:20:37.430 --> 00:20:40.000 align:start position:0% practical experience we study notes you get<00:20:37.700> already<00:20:38.000> a<00:20:38.150> lot<00:20:38.420> of<00:20:38.450> insights<00:20:39.080> because<00:20:39.860> we 00:20:40.000 --> 00:20:40.010 align:start position:0% get already a lot of insights because we 00:20:40.010 --> 00:20:42.220 align:start position:0% get already a lot of insights because we can<00:20:40.160> we<00:20:40.580> can<00:20:40.730> really<00:20:40.970> tear<00:20:41.240> apart<00:20:41.510> all<00:20:42.020> the 00:20:42.220 --> 00:20:42.230 align:start position:0% can we can really tear apart all the 00:20:42.230 --> 00:20:45.760 align:start position:0% can we can really tear apart all the network<00:20:42.560> connections<00:20:44.140> like<00:20:45.140> we<00:20:45.410> can<00:20:45.530> simulate 00:20:45.760 --> 00:20:45.770 align:start position:0% network connections like we can simulate 00:20:45.770 --> 00:20:47.260 align:start position:0% network connections like we can simulate a<00:20:45.950> lot<00:20:46.130> of<00:20:46.250> latency<00:20:46.550> we<00:20:46.760> can<00:20:46.910> actually<00:20:47.030> have 00:20:47.260 --> 00:20:47.270 align:start position:0% a lot of latency we can actually have 00:20:47.270 --> 00:20:49.000 align:start position:0% a lot of latency we can actually have nodes<00:20:47.570> being<00:20:48.020> submitted<00:20:48.380> between<00:20:48.800> New<00:20:48.980> York 00:20:49.000 --> 00:20:49.010 align:start position:0% nodes being submitted between New York 00:20:49.010 --> 00:20:51.430 align:start position:0% nodes being submitted between New York and<00:20:49.250> Tokyo<00:20:49.490> for<00:20:49.790> example<00:20:50.240> to<00:20:50.870> really<00:20:51.110> show 00:20:51.430 --> 00:20:51.440 align:start position:0% and Tokyo for example to really show 00:20:51.440 --> 00:20:53.680 align:start position:0% and Tokyo for example to really show what<00:20:51.470> happens<00:20:52.130> if<00:20:52.460> the<00:20:52.940> transaction<00:20:53.240> takes<00:20:53.540> a 00:20:53.680 --> 00:20:53.690 align:start position:0% what happens if the transaction takes a 00:20:53.690 --> 00:20:56.490 align:start position:0% what happens if the transaction takes a long<00:20:53.810> time<00:20:53.840> to<00:20:54.020> even<00:20:54.320> come<00:20:54.560> back<00:20:54.680> to<00:20:54.860> you<00:20:54.980> so 00:20:56.490 --> 00:20:56.500 align:start position:0% long time to even come back to you so 00:20:56.500 --> 00:20:58.390 align:start position:0% long time to even come back to you so second<00:20:57.500> part<00:20:57.680> of<00:20:57.770> your<00:20:57.890> question<00:20:57.980> I'm<00:20:58.280> gonna 00:20:58.390 --> 00:20:58.400 align:start position:0% second part of your question I'm gonna 00:20:58.400 --> 00:21:07.940 align:start position:0% second part of your question I'm gonna get<00:20:58.610> killed<00:20:59.000> by<00:20:59.090> this<00:20:59.150> guy<00:21:01.930> yes 00:21:07.940 --> 00:21:07.950 align:start position:0% 00:21:07.950 --> 00:21:20.290 align:start position:0% you 00:21:20.290 --> 00:21:20.300 align:start position:0% 00:21:20.300 --> 00:21:22.360 align:start position:0% you