WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:02.270 align:start position:0% let's<00:00:00.780> begin<00:00:00.989> my<00:00:01.260> name<00:00:01.380> is<00:00:01.469> yannick<00:00:01.740> I'm<00:00:01.979> from 00:00:02.270 --> 00:00:02.280 align:start position:0% let's begin my name is yannick I'm from 00:00:02.280 --> 00:00:04.519 align:start position:0% let's begin my name is yannick I'm from Rainbow<00:00:02.580> and<00:00:02.879> I'm<00:00:03.000> here<00:00:03.179> with<00:00:03.389> Kevin<00:00:04.140> from<00:00:04.500> the 00:00:04.519 --> 00:00:04.529 align:start position:0% Rainbow and I'm here with Kevin from the 00:00:04.529 --> 00:00:06.860 align:start position:0% Rainbow and I'm here with Kevin from the theorem<00:00:04.950> foundation<00:00:05.430> and<00:00:05.609> we're<00:00:06.480> going<00:00:06.779> to 00:00:06.860 --> 00:00:06.870 align:start position:0% theorem foundation and we're going to 00:00:06.870 --> 00:00:08.450 align:start position:0% theorem foundation and we're going to talk<00:00:07.049> a<00:00:07.080> little<00:00:07.319> bit<00:00:07.470> about<00:00:07.680> Italy<00:00:08.250> and 00:00:08.450 --> 00:00:08.460 align:start position:0% talk a little bit about Italy and 00:00:08.460 --> 00:00:10.820 align:start position:0% talk a little bit about Italy and networking<00:00:08.730> in<00:00:09.000> issue<00:00:09.240> in<00:00:09.420> Prato<00:00:09.809> or<00:00:10.440> how<00:00:10.769> we 00:00:10.820 --> 00:00:10.830 align:start position:0% networking in issue in Prato or how we 00:00:10.830 --> 00:00:14.749 align:start position:0% networking in issue in Prato or how we call<00:00:11.070> it<00:00:11.099> now<00:00:11.280> in<00:00:11.550> serenity<00:00:12.179> I<00:00:12.650> will<00:00:13.650> start<00:00:14.460> and 00:00:14.749 --> 00:00:14.759 align:start position:0% call it now in serenity I will start and 00:00:14.759 --> 00:00:18.380 align:start position:0% call it now in serenity I will start and give<00:00:15.630> a<00:00:15.660> little<00:00:15.809> bit<00:00:15.960> of<00:00:16.379> background<00:00:17.279> and<00:00:17.730> try 00:00:18.380 --> 00:00:18.390 align:start position:0% give a little bit of background and try 00:00:18.390 --> 00:00:19.939 align:start position:0% give a little bit of background and try to<00:00:18.449> introduce<00:00:18.900> you<00:00:19.170> to<00:00:19.320> the<00:00:19.439> problem<00:00:19.619> that<00:00:19.770> we 00:00:19.939 --> 00:00:19.949 align:start position:0% to introduce you to the problem that we 00:00:19.949 --> 00:00:22.220 align:start position:0% to introduce you to the problem that we are<00:00:19.980> trying<00:00:20.100> to<00:00:20.310> solve<00:00:20.490> and<00:00:20.789> then<00:00:20.900> and<00:00:21.900> also 00:00:22.220 --> 00:00:22.230 align:start position:0% are trying to solve and then and also 00:00:22.230 --> 00:00:24.529 align:start position:0% are trying to solve and then and also show<00:00:22.380> some<00:00:22.560> simulations<00:00:23.130> to<00:00:23.880> see<00:00:24.119> if<00:00:24.240> our 00:00:24.529 --> 00:00:24.539 align:start position:0% show some simulations to see if our 00:00:24.539 --> 00:00:26.839 align:start position:0% show some simulations to see if our approach<00:00:24.810> makes<00:00:25.500> somewhat<00:00:25.920> sense<00:00:26.130> and<00:00:26.490> then<00:00:26.820> I 00:00:26.839 --> 00:00:26.849 align:start position:0% approach makes somewhat sense and then I 00:00:26.849 --> 00:00:29.240 align:start position:0% approach makes somewhat sense and then I will<00:00:27.119> hand<00:00:27.300> it<00:00:27.390> over<00:00:27.480> to<00:00:27.630> Kevin<00:00:27.960> who<00:00:28.650> will<00:00:28.890> talk 00:00:29.240 --> 00:00:29.250 align:start position:0% will hand it over to Kevin who will talk 00:00:29.250 --> 00:00:31.880 align:start position:0% will hand it over to Kevin who will talk about<00:00:29.369> the<00:00:29.550> implementation<00:00:29.760> of<00:00:30.710> all<00:00:31.710> that 00:00:31.880 --> 00:00:31.890 align:start position:0% about the implementation of all that 00:00:31.890 --> 00:00:35.299 align:start position:0% about the implementation of all that stuff<00:00:32.099> but<00:00:33.090> let's<00:00:33.329> start<00:00:33.739> with<00:00:34.739> the<00:00:35.010> very 00:00:35.299 --> 00:00:35.309 align:start position:0% stuff but let's start with the very 00:00:35.309 --> 00:00:37.790 align:start position:0% stuff but let's start with the very basic<00:00:35.910> things<00:00:36.120> our<00:00:36.809> gods<00:00:37.110> of<00:00:37.260> networking<00:00:37.590> what 00:00:37.790 --> 00:00:37.800 align:start position:0% basic things our gods of networking what 00:00:37.800 --> 00:00:39.260 align:start position:0% basic things our gods of networking what we<00:00:37.890> actually<00:00:38.010> want<00:00:38.280> to<00:00:38.309> do<00:00:38.460> we<00:00:38.969> have<00:00:39.090> some 00:00:39.260 --> 00:00:39.270 align:start position:0% we actually want to do we have some 00:00:39.270 --> 00:00:41.090 align:start position:0% we actually want to do we have some notes<00:00:39.480> in<00:00:39.719> that<00:00:39.780> produced<00:00:40.260> data<00:00:40.410> and<00:00:40.770> others 00:00:41.090 --> 00:00:41.100 align:start position:0% notes in that produced data and others 00:00:41.100 --> 00:00:42.530 align:start position:0% notes in that produced data and others want<00:00:41.489> to<00:00:41.550> obtain<00:00:41.730> this<00:00:41.850> data<00:00:41.910> so<00:00:42.270> we<00:00:42.360> need<00:00:42.510> a 00:00:42.530 --> 00:00:42.540 align:start position:0% want to obtain this data so we need a 00:00:42.540 --> 00:00:44.959 align:start position:0% want to obtain this data so we need a way<00:00:42.690> to<00:00:42.719> distribute<00:00:43.230> this<00:00:43.379> and<00:00:43.559> that<00:00:44.370> way<00:00:44.579> the 00:00:44.959 --> 00:00:44.969 align:start position:0% way to distribute this and that way the 00:00:44.969 --> 00:00:46.520 align:start position:0% way to distribute this and that way the way<00:00:45.090> how<00:00:45.420> we<00:00:45.480> want<00:00:45.719> to<00:00:45.780> do<00:00:45.870> this<00:00:46.020> should<00:00:46.289> it 00:00:46.520 --> 00:00:46.530 align:start position:0% way how we want to do this should it 00:00:46.530 --> 00:00:48.229 align:start position:0% way how we want to do this should it should<00:00:46.590> be<00:00:46.739> efficient<00:00:47.219> it<00:00:47.399> should<00:00:47.550> be<00:00:47.670> fast 00:00:48.229 --> 00:00:48.239 align:start position:0% should be efficient it should be fast 00:00:48.239 --> 00:00:52.010 align:start position:0% should be efficient it should be fast and<00:00:48.480> it<00:00:48.600> should<00:00:48.719> also<00:00:48.899> be<00:00:49.020> safe<00:00:50.780> what<00:00:51.780> kind<00:00:51.960> of 00:00:52.010 --> 00:00:52.020 align:start position:0% and it should also be safe what kind of 00:00:52.020 --> 00:00:54.650 align:start position:0% and it should also be safe what kind of data<00:00:52.230> in<00:00:52.590> in<00:00:53.250> the<00:00:53.399> original<00:00:53.760> theorem<00:00:54.420> it's 00:00:54.650 --> 00:00:54.660 align:start position:0% data in in the original theorem it's 00:00:54.660 --> 00:00:56.630 align:start position:0% data in in the original theorem it's mostly<00:00:55.350> transactions<00:00:55.890> and<00:00:56.070> blocks<00:00:56.280> and<00:00:56.520> the 00:00:56.630 --> 00:00:56.640 align:start position:0% mostly transactions and blocks and the 00:00:56.640 --> 00:00:59.990 align:start position:0% mostly transactions and blocks and the important<00:00:57.030> thing<00:00:57.180> is<00:00:57.420> that<00:00:58.430> all<00:00:59.430> notes 00:00:59.990 --> 00:01:00.000 align:start position:0% important thing is that all notes 00:01:00.000 --> 00:01:02.180 align:start position:0% important thing is that all notes basically<00:01:00.510> download<00:01:01.140> the<00:01:01.320> same<00:01:01.649> data<00:01:01.890> so 00:01:02.180 --> 00:01:02.190 align:start position:0% basically download the same data so 00:01:02.190 --> 00:01:03.799 align:start position:0% basically download the same data so there's<00:01:02.460> no<00:01:02.789> distinction<00:01:03.149> at<00:01:03.329> all<00:01:03.420> basically 00:01:03.799 --> 00:01:03.809 align:start position:0% there's no distinction at all basically 00:01:03.809 --> 00:01:06.920 align:start position:0% there's no distinction at all basically all<00:01:04.080> notes<00:01:04.320> do<00:01:04.470> the<00:01:04.589> same<00:01:04.739> thing<00:01:05.299> in<00:01:06.299> serenity 00:01:06.920 --> 00:01:06.930 align:start position:0% all notes do the same thing in serenity 00:01:06.930 --> 00:01:08.960 align:start position:0% all notes do the same thing in serenity things<00:01:07.680> gets<00:01:07.920> different<00:01:08.100> mostly<00:01:08.610> because<00:01:08.760> of 00:01:08.960 --> 00:01:08.970 align:start position:0% things gets different mostly because of 00:01:08.970 --> 00:01:11.120 align:start position:0% things gets different mostly because of shouting<00:01:09.210> and<00:01:09.720> shouting<00:01:10.290> means<00:01:10.770> we<00:01:10.979> basically 00:01:11.120 --> 00:01:11.130 align:start position:0% shouting and shouting means we basically 00:01:11.130 --> 00:01:14.210 align:start position:0% shouting and shouting means we basically split<00:01:11.640> the<00:01:11.820> data<00:01:12.000> up<00:01:12.270> into<00:01:12.659> different<00:01:13.220> charts 00:01:14.210 --> 00:01:14.220 align:start position:0% split the data up into different charts 00:01:14.220 --> 00:01:17.480 align:start position:0% split the data up into different charts and<00:01:15.140> one<00:01:16.140> particular<00:01:16.560> node<00:01:16.770> only<00:01:16.979> downloads 00:01:17.480 --> 00:01:17.490 align:start position:0% and one particular node only downloads 00:01:17.490 --> 00:01:19.880 align:start position:0% and one particular node only downloads the<00:01:17.640> data<00:01:17.670> for<00:01:18.060> that<00:01:18.180> particular<00:01:18.689> shot<00:01:18.869> so<00:01:19.439> and 00:01:19.880 --> 00:01:19.890 align:start position:0% the data for that particular shot so and 00:01:19.890 --> 00:01:22.010 align:start position:0% the data for that particular shot so and that<00:01:20.159> way<00:01:20.310> we<00:01:20.670> can<00:01:20.820> save<00:01:21.060> a<00:01:21.090> lot<00:01:21.330> of<00:01:21.479> bandwidth 00:01:22.010 --> 00:01:22.020 align:start position:0% that way we can save a lot of bandwidth 00:01:22.020 --> 00:01:25.219 align:start position:0% that way we can save a lot of bandwidth I<00:01:22.259> plotted<00:01:22.979> in<00:01:23.850> this<00:01:24.240> picture<00:01:24.689> it's<00:01:24.810> 8:00<00:01:24.990> and 00:01:25.219 --> 00:01:25.229 align:start position:0% I plotted in this picture it's 8:00 and 00:01:25.229 --> 00:01:27.950 align:start position:0% I plotted in this picture it's 8:00 and reality<00:01:25.830> it's<00:01:25.950> a<00:01:26.040> thousand<00:01:26.400> but<00:01:27.060> it's<00:01:27.450> not<00:01:27.570> too 00:01:27.950 --> 00:01:27.960 align:start position:0% reality it's a thousand but it's not too 00:01:27.960 --> 00:01:30.410 align:start position:0% reality it's a thousand but it's not too many<00:01:28.140> to<00:01:28.320> to<00:01:29.070> draw<00:01:29.220> on<00:01:29.310> this<00:01:29.400> picture<00:01:29.700> but<00:01:29.880> just 00:01:30.410 --> 00:01:30.420 align:start position:0% many to to draw on this picture but just 00:01:30.420 --> 00:01:32.710 align:start position:0% many to to draw on this picture but just to<00:01:30.570> yeah 00:01:32.710 --> 00:01:32.720 align:start position:0% to yeah 00:01:32.720 --> 00:01:35.569 align:start position:0% to yeah in<00:01:33.720> addition<00:01:34.110> to<00:01:34.200> this<00:01:34.350> shot<00:01:34.680> data<00:01:34.920> we<00:01:35.400> also 00:01:35.569 --> 00:01:35.579 align:start position:0% in addition to this shot data we also 00:01:35.579 --> 00:01:37.340 align:start position:0% in addition to this shot data we also still<00:01:36.090> need<00:01:36.119> some<00:01:36.450> kind<00:01:36.600> of<00:01:36.630> global<00:01:36.869> data<00:01:37.079> that 00:01:37.340 --> 00:01:37.350 align:start position:0% still need some kind of global data that 00:01:37.350 --> 00:01:39.620 align:start position:0% still need some kind of global data that are<00:01:37.470> notes<00:01:37.680> download<00:01:38.070> this<00:01:38.670> is<00:01:38.820> the<00:01:39.390> beacon 00:01:39.620 --> 00:01:39.630 align:start position:0% are notes download this is the beacon 00:01:39.630 --> 00:01:43.100 align:start position:0% are notes download this is the beacon chain<00:01:39.810> data<00:01:41.299> and<00:01:42.299> from<00:01:42.540> that<00:01:42.630> we<00:01:42.930> can 00:01:43.100 --> 00:01:43.110 align:start position:0% chain data and from that we can 00:01:43.110 --> 00:01:46.069 align:start position:0% chain data and from that we can basically<00:01:43.439> infer<00:01:44.149> how<00:01:45.149> nodes<00:01:45.509> should<00:01:45.630> connect 00:01:46.069 --> 00:01:46.079 align:start position:0% basically infer how nodes should connect 00:01:46.079 --> 00:01:50.510 align:start position:0% basically infer how nodes should connect to<00:01:46.140> other<00:01:46.320> nodes<00:01:46.560> in<00:01:47.430> original<00:01:48.500> aetherium<00:01:49.530> all 00:01:50.510 --> 00:01:50.520 align:start position:0% to other nodes in original aetherium all 00:01:50.520 --> 00:01:52.700 align:start position:0% to other nodes in original aetherium all nodes<00:01:50.970> basically<00:01:51.360> are<00:01:51.479> the<00:01:51.570> same<00:01:51.750> so<00:01:52.079> one<00:01:52.470> node 00:01:52.700 --> 00:01:52.710 align:start position:0% nodes basically are the same so one node 00:01:52.710 --> 00:01:55.010 align:start position:0% nodes basically are the same so one node simply<00:01:53.159> basically<00:01:53.880> picks<00:01:54.090> random<00:01:54.180> Lee<00:01:54.570> from 00:01:55.010 --> 00:01:55.020 align:start position:0% simply basically picks random Lee from 00:01:55.020 --> 00:01:58.630 align:start position:0% simply basically picks random Lee from the<00:01:55.110> set<00:01:55.320> of<00:01:55.500> nodes<00:01:55.890> and<00:01:56.280> connects<00:01:56.820> to<00:01:56.880> them<00:01:57.119> in 00:01:58.630 --> 00:01:58.640 align:start position:0% the set of nodes and connects to them in 00:01:58.640 --> 00:02:02.149 align:start position:0% the set of nodes and connects to them in serenity<00:01:59.640> things<00:02:00.060> will<00:02:00.210> be<00:02:00.360> different<00:02:00.710> if<00:02:01.710> you 00:02:02.149 --> 00:02:02.159 align:start position:0% serenity things will be different if you 00:02:02.159 --> 00:02:04.910 align:start position:0% serenity things will be different if you pick<00:02:02.460> peers<00:02:02.790> you<00:02:03.240> first<00:02:03.780> look<00:02:03.990> at<00:02:04.110> what<00:02:04.619> shot 00:02:04.910 --> 00:02:04.920 align:start position:0% pick peers you first look at what shot 00:02:04.920 --> 00:02:06.469 align:start position:0% pick peers you first look at what shot you're<00:02:05.130> assigned<00:02:05.399> to<00:02:05.460> or<00:02:05.640> what<00:02:05.820> shot<00:02:06.149> you<00:02:06.299> want 00:02:06.469 --> 00:02:06.479 align:start position:0% you're assigned to or what shot you want 00:02:06.479 --> 00:02:08.660 align:start position:0% you're assigned to or what shot you want to<00:02:06.570> download<00:02:06.750> and<00:02:07.110> in<00:02:07.799> this<00:02:08.160> in<00:02:08.399> this<00:02:08.520> example 00:02:08.660 --> 00:02:08.670 align:start position:0% to download and in this in this example 00:02:08.670 --> 00:02:11.809 align:start position:0% to download and in this in this example shot<00:02:09.090> three<00:02:09.420> and<00:02:10.349> then<00:02:10.530> you<00:02:10.649> pick<00:02:10.860> peers<00:02:11.190> from 00:02:11.809 --> 00:02:11.819 align:start position:0% shot three and then you pick peers from 00:02:11.819 --> 00:02:13.140 align:start position:0% shot three and then you pick peers from that<00:02:12.270> shot 00:02:13.140 --> 00:02:13.150 align:start position:0% that shot 00:02:13.150 --> 00:02:15.300 align:start position:0% that shot and<00:02:13.239> so<00:02:13.930> that<00:02:14.110> you<00:02:14.230> they<00:02:14.530> can<00:02:14.709> give<00:02:15.040> you<00:02:15.129> useful 00:02:15.300 --> 00:02:15.310 align:start position:0% and so that you they can give you useful 00:02:15.310 --> 00:02:17.759 align:start position:0% and so that you they can give you useful information<00:02:15.610> so<00:02:16.450> here<00:02:16.810> we<00:02:16.959> have<00:02:17.080> three 00:02:17.759 --> 00:02:17.769 align:start position:0% information so here we have three 00:02:17.769 --> 00:02:19.530 align:start position:0% information so here we have three additional<00:02:18.190> notes<00:02:18.370> from<00:02:18.790> a<00:02:18.849> sharp<00:02:19.120> three<00:02:19.330> and 00:02:19.530 --> 00:02:19.540 align:start position:0% additional notes from a sharp three and 00:02:19.540 --> 00:02:22.830 align:start position:0% additional notes from a sharp three and then<00:02:19.930> in<00:02:20.170> addition<00:02:20.349> to<00:02:20.560> that<00:02:20.650> we<00:02:20.950> pick<00:02:21.840> notes 00:02:22.830 --> 00:02:22.840 align:start position:0% then in addition to that we pick notes 00:02:22.840 --> 00:02:26.550 align:start position:0% then in addition to that we pick notes from<00:02:23.080> the<00:02:23.260> global<00:02:23.560> set<00:02:24.930> that<00:02:25.930> can<00:02:26.140> provide<00:02:26.409> you 00:02:26.550 --> 00:02:26.560 align:start position:0% from the global set that can provide you 00:02:26.560 --> 00:02:29.160 align:start position:0% from the global set that can provide you with<00:02:26.739> beacon<00:02:27.549> data<00:02:27.700> in<00:02:28.030> this<00:02:28.269> example<00:02:28.659> one<00:02:28.989> and 00:02:29.160 --> 00:02:29.170 align:start position:0% with beacon data in this example one and 00:02:29.170 --> 00:02:32.280 align:start position:0% with beacon data in this example one and seven<00:02:29.440> and<00:02:30.190> then<00:02:30.610> we<00:02:31.569> can<00:02:31.690> basically<00:02:31.810> abstract 00:02:32.280 --> 00:02:32.290 align:start position:0% seven and then we can basically abstract 00:02:32.290 --> 00:02:34.770 align:start position:0% seven and then we can basically abstract from<00:02:32.500> that<00:02:32.680> essentially<00:02:33.340> what<00:02:33.519> you<00:02:33.610> do<00:02:33.790> is<00:02:33.819> we 00:02:34.770 --> 00:02:34.780 align:start position:0% from that essentially what you do is we 00:02:34.780 --> 00:02:36.960 align:start position:0% from that essentially what you do is we now<00:02:35.140> have<00:02:35.170> two<00:02:35.799> networks<00:02:36.190> and<00:02:36.459> then<00:02:36.549> one<00:02:36.730> is 00:02:36.960 --> 00:02:36.970 align:start position:0% now have two networks and then one is 00:02:36.970 --> 00:02:39.300 align:start position:0% now have two networks and then one is the<00:02:37.180> sharp<00:02:37.390> network<00:02:37.720> which<00:02:38.590> consists<00:02:39.069> of<00:02:39.099> all 00:02:39.300 --> 00:02:39.310 align:start position:0% the sharp network which consists of all 00:02:39.310 --> 00:02:40.949 align:start position:0% the sharp network which consists of all the<00:02:39.459> nodes<00:02:39.610> that<00:02:39.879> are<00:02:39.940> connected<00:02:40.420> to<00:02:40.569> a 00:02:40.949 --> 00:02:40.959 align:start position:0% the nodes that are connected to a 00:02:40.959 --> 00:02:42.839 align:start position:0% the nodes that are connected to a certain<00:02:41.920> shot<00:02:42.099> and<00:02:42.280> are<00:02:42.370> connected<00:02:42.730> to<00:02:42.819> each 00:02:42.839 --> 00:02:42.849 align:start position:0% certain shot and are connected to each 00:02:42.849 --> 00:02:43.520 align:start position:0% certain shot and are connected to each other 00:02:43.520 --> 00:02:43.530 align:start position:0% other 00:02:43.530 --> 00:02:47.910 align:start position:0% other and<00:02:44.530> then<00:02:44.980> with<00:02:45.129> the<00:02:45.370> beacon<00:02:45.640> network<00:02:46.920> that 00:02:47.910 --> 00:02:47.920 align:start position:0% and then with the beacon network that 00:02:47.920 --> 00:02:50.309 align:start position:0% and then with the beacon network that consists<00:02:48.459> of<00:02:48.519> all<00:02:48.760> the<00:02:48.970> different<00:02:49.420> nodes<00:02:49.569> and 00:02:50.309 --> 00:02:50.319 align:start position:0% consists of all the different nodes and 00:02:50.319 --> 00:02:52.729 align:start position:0% consists of all the different nodes and in<00:02:50.709> this<00:02:50.859> network<00:02:51.099> only<00:02:51.400> the<00:02:51.609> beacon<00:02:51.849> data<00:02:52.030> is 00:02:52.729 --> 00:02:52.739 align:start position:0% in this network only the beacon data is 00:02:52.739 --> 00:02:57.210 align:start position:0% in this network only the beacon data is transmitted<00:02:55.680> now<00:02:56.680> another<00:02:56.950> thing<00:02:57.040> that's 00:02:57.210 --> 00:02:57.220 align:start position:0% transmitted now another thing that's 00:02:57.220 --> 00:02:59.369 align:start position:0% transmitted now another thing that's different<00:02:57.579> to<00:02:58.239> the<00:02:58.659> existing<00:02:59.049> ischium 00:02:59.369 --> 00:02:59.379 align:start position:0% different to the existing ischium 00:02:59.379 --> 00:03:00.720 align:start position:0% different to the existing ischium network<00:02:59.620> is<00:02:59.739> that<00:02:59.980> we<00:03:00.069> have<00:03:00.159> a<00:03:00.220> new<00:03:00.370> class<00:03:00.579> of 00:03:00.720 --> 00:03:00.730 align:start position:0% network is that we have a new class of 00:03:00.730 --> 00:03:03.539 align:start position:0% network is that we have a new class of nodes<00:03:00.970> called<00:03:01.239> the<00:03:01.420> validators<00:03:01.930> and<00:03:02.859> they<00:03:03.370> are 00:03:03.539 --> 00:03:03.549 align:start position:0% nodes called the validators and they are 00:03:03.549 --> 00:03:06.479 align:start position:0% nodes called the validators and they are quite<00:03:03.819> similar<00:03:04.090> to<00:03:04.239> normal<00:03:05.140> nodes<00:03:05.409> in<00:03:05.680> that 00:03:06.479 --> 00:03:06.489 align:start position:0% quite similar to normal nodes in that 00:03:06.489 --> 00:03:08.880 align:start position:0% quite similar to normal nodes in that sense<00:03:06.730> that<00:03:06.819> they<00:03:07.180> are<00:03:08.170> interested<00:03:08.680> in<00:03:08.739> the 00:03:08.880 --> 00:03:08.890 align:start position:0% sense that they are interested in the 00:03:08.890 --> 00:03:11.430 align:start position:0% sense that they are interested in the data<00:03:09.010> that<00:03:09.400> concern<00:03:10.049> belongs<00:03:11.049> to<00:03:11.230> a<00:03:11.260> certain 00:03:11.430 --> 00:03:11.440 align:start position:0% data that concern belongs to a certain 00:03:11.440 --> 00:03:15.300 align:start position:0% data that concern belongs to a certain chart<00:03:11.799> but<00:03:12.430> in<00:03:12.609> addition<00:03:12.940> to<00:03:13.060> that<00:03:13.590> in<00:03:14.590> what's 00:03:15.300 --> 00:03:15.310 align:start position:0% chart but in addition to that in what's 00:03:15.310 --> 00:03:17.339 align:start position:0% chart but in addition to that in what's different<00:03:15.579> to<00:03:15.730> them<00:03:16.060> is<00:03:16.239> that<00:03:16.390> they<00:03:16.569> only<00:03:16.959> care 00:03:17.339 --> 00:03:17.349 align:start position:0% different to them is that they only care 00:03:17.349 --> 00:03:18.900 align:start position:0% different to them is that they only care about<00:03:17.380> the<00:03:17.650> recent<00:03:17.980> history<00:03:18.250> so<00:03:18.519> they<00:03:18.669> don't 00:03:18.900 --> 00:03:18.910 align:start position:0% about the recent history so they don't 00:03:18.910 --> 00:03:20.879 align:start position:0% about the recent history so they don't don't<00:03:19.269> don't<00:03:19.540> download<00:03:20.019> and<00:03:20.380> like<00:03:20.590> the<00:03:20.739> whole 00:03:20.879 --> 00:03:20.889 align:start position:0% don't don't download and like the whole 00:03:20.889 --> 00:03:23.370 align:start position:0% don't don't download and like the whole chain<00:03:21.430> up<00:03:22.000> until<00:03:22.299> Genesis<00:03:22.690> but<00:03:23.019> only<00:03:23.260> the 00:03:23.370 --> 00:03:23.380 align:start position:0% chain up until Genesis but only the 00:03:23.380 --> 00:03:26.759 align:start position:0% chain up until Genesis but only the recent<00:03:23.590> history<00:03:24.030> and<00:03:25.410> another<00:03:26.410> thing<00:03:26.590> that's 00:03:26.759 --> 00:03:26.769 align:start position:0% recent history and another thing that's 00:03:26.769 --> 00:03:28.530 align:start position:0% recent history and another thing that's different<00:03:26.950> is<00:03:27.190> that<00:03:27.250> they<00:03:27.549> switch<00:03:27.910> regularly 00:03:28.530 --> 00:03:28.540 align:start position:0% different is that they switch regularly 00:03:28.540 --> 00:03:31.920 align:start position:0% different is that they switch regularly between<00:03:28.959> charts<00:03:30.510> because<00:03:31.510> they<00:03:31.540> basically 00:03:31.920 --> 00:03:31.930 align:start position:0% between charts because they basically 00:03:31.930 --> 00:03:34.349 align:start position:0% between charts because they basically get<00:03:32.410> assigned<00:03:32.680> to<00:03:32.889> a<00:03:32.919> new<00:03:33.069> chart<00:03:33.280> which<00:03:34.120> they 00:03:34.349 --> 00:03:34.359 align:start position:0% get assigned to a new chart which they 00:03:34.359 --> 00:03:39.390 align:start position:0% get assigned to a new chart which they are<00:03:34.450> supposed<00:03:34.599> to<00:03:34.840> validate<00:03:37.019> randomly<00:03:38.019> and<00:03:38.400> a 00:03:39.390 --> 00:03:39.400 align:start position:0% are supposed to validate randomly and a 00:03:39.400 --> 00:03:40.890 align:start position:0% are supposed to validate randomly and a third<00:03:39.700> thing<00:03:39.940> and<00:03:40.239> that's<00:03:40.389> different<00:03:40.599> is<00:03:40.870> that 00:03:40.890 --> 00:03:40.900 align:start position:0% third thing and that's different is that 00:03:40.900 --> 00:03:44.789 align:start position:0% third thing and that's different is that they<00:03:41.379> want<00:03:41.799> not<00:03:42.609> they<00:03:43.030> want<00:03:43.209> not<00:03:43.449> and<00:03:43.840> that<00:03:44.440> the 00:03:44.789 --> 00:03:44.799 align:start position:0% they want not they want not and that the 00:03:44.799 --> 00:03:46.020 align:start position:0% they want not they want not and that the rest<00:03:44.949> of<00:03:45.099> the<00:03:45.190> network<00:03:45.340> knows<00:03:45.669> that<00:03:45.819> they<00:03:46.000> are 00:03:46.020 --> 00:03:46.030 align:start position:0% rest of the network knows that they are 00:03:46.030 --> 00:03:48.270 align:start position:0% rest of the network knows that they are billy<00:03:46.239> data<00:03:46.480> or<00:03:46.720> or<00:03:47.440> which<00:03:47.739> really<00:03:47.949> did<00:03:48.160> have 00:03:48.270 --> 00:03:48.280 align:start position:0% billy data or or which really did have 00:03:48.280 --> 00:03:51.479 align:start position:0% billy data or or which really did have they<00:03:48.370> are<00:03:48.519> because<00:03:49.120> they<00:03:49.389> stakes<00:03:49.930> and<00:03:50.489> some 00:03:51.479 --> 00:03:51.489 align:start position:0% they are because they stakes and some 00:03:51.489 --> 00:03:53.970 align:start position:0% they are because they stakes and some ether<00:03:51.639> and<00:03:52.000> so<00:03:52.930> they<00:03:53.109> want<00:03:53.319> to<00:03:53.440> have<00:03:53.590> extra 00:03:53.970 --> 00:03:53.980 align:start position:0% ether and so they want to have extra 00:03:53.980 --> 00:03:55.860 align:start position:0% ether and so they want to have extra protection<00:03:54.069> and<00:03:54.549> if<00:03:55.150> people<00:03:55.510> would<00:03:55.629> know<00:03:55.840> that 00:03:55.860 --> 00:03:55.870 align:start position:0% protection and if people would know that 00:03:55.870 --> 00:03:57.629 align:start position:0% protection and if people would know that they<00:03:56.199> are<00:03:56.319> validated<00:03:56.799> they<00:03:56.949> might<00:03:57.459> get 00:03:57.629 --> 00:03:57.639 align:start position:0% they are validated they might get 00:03:57.639 --> 00:04:04.470 align:start position:0% they are validated they might get attacked<00:04:00.690> now<00:04:01.690> that's<00:04:01.959> basically<00:04:02.709> all<00:04:02.949> in<00:04:03.480> all 00:04:04.470 --> 00:04:04.480 align:start position:0% attacked now that's basically all in all 00:04:04.480 --> 00:04:06.420 align:start position:0% attacked now that's basically all in all the<00:04:04.720> changes<00:04:05.049> we<00:04:05.079> have<00:04:05.319> and<00:04:05.650> now<00:04:06.069> we<00:04:06.099> need<00:04:06.340> to 00:04:06.420 --> 00:04:06.430 align:start position:0% the changes we have and now we need to 00:04:06.430 --> 00:04:07.970 align:start position:0% the changes we have and now we need to think<00:04:06.669> about<00:04:07.030> what<00:04:07.180> protocols<00:04:07.599> we<00:04:07.720> have 00:04:07.970 --> 00:04:07.980 align:start position:0% think about what protocols we have 00:04:07.980 --> 00:04:09.930 align:start position:0% think about what protocols we have basically<00:04:08.980> there<00:04:09.699> are<00:04:09.730> three 00:04:09.930 --> 00:04:09.940 align:start position:0% basically there are three 00:04:09.940 --> 00:04:12.030 align:start position:0% basically there are three functionalities<00:04:10.599> and<00:04:10.840> the<00:04:10.930> first<00:04:11.139> one<00:04:11.319> is<00:04:11.739> we 00:04:12.030 --> 00:04:12.040 align:start position:0% functionalities and the first one is we 00:04:12.040 --> 00:04:14.430 align:start position:0% functionalities and the first one is we need<00:04:12.280> a<00:04:12.519> way<00:04:12.699> to<00:04:12.760> find<00:04:13.120> suitable<00:04:13.389> peers<00:04:13.870> and 00:04:14.430 --> 00:04:14.440 align:start position:0% need a way to find suitable peers and 00:04:14.440 --> 00:04:17.640 align:start position:0% need a way to find suitable peers and that's<00:04:15.129> done<00:04:15.519> by<00:04:15.760> a<00:04:15.790> discovery<00:04:16.599> protocol<00:04:17.019> the 00:04:17.640 --> 00:04:17.650 align:start position:0% that's done by a discovery protocol the 00:04:17.650 --> 00:04:19.469 align:start position:0% that's done by a discovery protocol the second<00:04:17.949> a<00:04:18.190> second<00:04:18.489> thing<00:04:18.699> we<00:04:18.910> need<00:04:19.060> to<00:04:19.090> do<00:04:19.239> is 00:04:19.469 --> 00:04:19.479 align:start position:0% second a second thing we need to do is 00:04:19.479 --> 00:04:22.080 align:start position:0% second a second thing we need to do is to<00:04:19.690> distribute<00:04:20.079> data<00:04:20.349> and<00:04:20.769> we<00:04:21.459> do<00:04:21.609> this<00:04:21.789> using 00:04:22.080 --> 00:04:22.090 align:start position:0% to distribute data and we do this using 00:04:22.090 --> 00:04:25.380 align:start position:0% to distribute data and we do this using a<00:04:22.240> ghost<00:04:22.419> protocol<00:04:22.930> and<00:04:23.580> finally<00:04:24.580> four<00:04:25.150> new 00:04:25.380 --> 00:04:25.390 align:start position:0% a ghost protocol and finally four new 00:04:25.390 --> 00:04:26.860 align:start position:0% a ghost protocol and finally four new nodes<00:04:26.050> that 00:04:26.860 --> 00:04:26.870 align:start position:0% nodes that 00:04:26.870 --> 00:04:29.260 align:start position:0% nodes that join<00:04:26.990> the<00:04:27.110> network<00:04:27.260> or<00:04:27.740> validators<00:04:28.639> that<00:04:29.000> I 00:04:29.260 --> 00:04:29.270 align:start position:0% join the network or validators that I 00:04:29.270 --> 00:04:32.110 align:start position:0% join the network or validators that I signed<00:04:29.840> to<00:04:29.930> a<00:04:29.990> new<00:04:30.169> network<00:04:30.380> a<00:04:30.800> new<00:04:31.250> shot<00:04:31.460> then 00:04:32.110 --> 00:04:32.120 align:start position:0% signed to a new network a new shot then 00:04:32.120 --> 00:04:33.909 align:start position:0% signed to a new network a new shot then need<00:04:32.510> a<00:04:32.540> way<00:04:32.720> to<00:04:32.750> is<00:04:33.050> synchronized<00:04:33.530> in<00:04:33.740> the 00:04:33.909 --> 00:04:33.919 align:start position:0% need a way to is synchronized in the 00:04:33.919 --> 00:04:36.730 align:start position:0% need a way to is synchronized in the chain<00:04:34.160> on<00:04:34.910> the<00:04:35.090> history<00:04:35.930> of<00:04:35.990> the<00:04:36.169> chain<00:04:36.380> using 00:04:36.730 --> 00:04:36.740 align:start position:0% chain on the history of the chain using 00:04:36.740 --> 00:04:40.030 align:start position:0% chain on the history of the chain using RPC<00:04:37.460> calls<00:04:37.699> and<00:04:38.330> I<00:04:39.110> will<00:04:39.350> not<00:04:39.500> talk<00:04:39.620> about<00:04:39.770> the 00:04:40.030 --> 00:04:40.040 align:start position:0% RPC calls and I will not talk about the 00:04:40.040 --> 00:04:41.650 align:start position:0% RPC calls and I will not talk about the last<00:04:40.400> thing<00:04:40.669> because<00:04:40.820> that's<00:04:41.180> basically<00:04:41.360> the 00:04:41.650 --> 00:04:41.660 align:start position:0% last thing because that's basically the 00:04:41.660 --> 00:04:44.620 align:start position:0% last thing because that's basically the there's<00:04:42.560> basically<00:04:42.770> no<00:04:43.010> difference<00:04:43.370> to<00:04:43.630> how 00:04:44.620 --> 00:04:44.630 align:start position:0% there's basically no difference to how 00:04:44.630 --> 00:04:47.260 align:start position:0% there's basically no difference to how if<00:04:44.780> you<00:04:44.930> wondered<00:04:45.590> or<00:04:45.710> does<00:04:45.889> it<00:04:46.040> but<00:04:47.030> I<00:04:47.060> will 00:04:47.260 --> 00:04:47.270 align:start position:0% if you wondered or does it but I will 00:04:47.270 --> 00:04:49.180 align:start position:0% if you wondered or does it but I will focus<00:04:47.479> on<00:04:47.750> gossiping<00:04:48.229> and<00:04:48.470> the<00:04:48.680> discovery 00:04:49.180 --> 00:04:49.190 align:start position:0% focus on gossiping and the discovery 00:04:49.190 --> 00:04:49.750 align:start position:0% focus on gossiping and the discovery protocol 00:04:49.750 --> 00:04:49.760 align:start position:0% protocol 00:04:49.760 --> 00:04:52.390 align:start position:0% protocol I<00:04:49.790> said<00:04:50.690> what's<00:04:50.810> gossiping<00:04:51.260> gossiping<00:04:52.190> is<00:04:52.370> a 00:04:52.390 --> 00:04:52.400 align:start position:0% I said what's gossiping gossiping is a 00:04:52.400 --> 00:04:55.629 align:start position:0% I said what's gossiping gossiping is a very<00:04:52.850> simple<00:04:53.410> peer-to-peer<00:04:54.410> protocol<00:04:55.070> that's 00:04:55.629 --> 00:04:55.639 align:start position:0% very simple peer-to-peer protocol that's 00:04:55.639 --> 00:04:58.090 align:start position:0% very simple peer-to-peer protocol that's being<00:04:55.850> used<00:04:56.030> in<00:04:56.210> a<00:04:56.300> lot<00:04:56.449> of<00:04:57.100> projects 00:04:58.090 --> 00:04:58.100 align:start position:0% being used in a lot of projects 00:04:58.100 --> 00:05:00.279 align:start position:0% being used in a lot of projects including<00:04:58.729> Bitcoin<00:04:59.120> and<00:04:59.419> including<00:04:59.960> if<00:05:00.169> you 00:05:00.279 --> 00:05:00.289 align:start position:0% including Bitcoin and including if you 00:05:00.289 --> 00:05:04.330 align:start position:0% including Bitcoin and including if you own<00:05:00.380> one<00:05:00.410> at<00:05:00.650> all<00:05:02.050> the<00:05:03.050> idea<00:05:03.139> is<00:05:03.710> we<00:05:04.039> have<00:05:04.160> one 00:05:04.330 --> 00:05:04.340 align:start position:0% own one at all the idea is we have one 00:05:04.340 --> 00:05:06.040 align:start position:0% own one at all the idea is we have one node<00:05:04.550> in<00:05:04.789> the<00:05:05.090> network<00:05:05.120> that<00:05:05.539> lets<00:05:05.750> produced 00:05:06.040 --> 00:05:06.050 align:start position:0% node in the network that lets produced 00:05:06.050 --> 00:05:08.350 align:start position:0% node in the network that lets produced some<00:05:06.229> data<00:05:06.430> and<00:05:07.430> it<00:05:07.580> wants<00:05:07.820> to<00:05:07.850> inform<00:05:08.210> the 00:05:08.350 --> 00:05:08.360 align:start position:0% some data and it wants to inform the 00:05:08.360 --> 00:05:11.650 align:start position:0% some data and it wants to inform the rest<00:05:08.479> of<00:05:08.660> the<00:05:08.840> network<00:05:09.500> of<00:05:10.039> that<00:05:10.250> data<00:05:10.460> so<00:05:10.910> what 00:05:11.650 --> 00:05:11.660 align:start position:0% rest of the network of that data so what 00:05:11.660 --> 00:05:14.400 align:start position:0% rest of the network of that data so what they<00:05:12.410> they<00:05:13.010> do<00:05:13.070> is<00:05:13.310> they<00:05:13.520> pick<00:05:13.729> a<00:05:13.789> random<00:05:13.970> peer 00:05:14.400 --> 00:05:14.410 align:start position:0% they they do is they pick a random peer 00:05:14.410 --> 00:05:17.560 align:start position:0% they they do is they pick a random peer and<00:05:15.410> send<00:05:15.919> this<00:05:16.039> data<00:05:16.250> to<00:05:16.460> them<00:05:16.639> and<00:05:16.940> now<00:05:17.090> we 00:05:17.560 --> 00:05:17.570 align:start position:0% and send this data to them and now we 00:05:17.570 --> 00:05:19.360 align:start position:0% and send this data to them and now we have<00:05:17.690> two<00:05:17.840> kids<00:05:18.080> that<00:05:18.260> know<00:05:18.410> the<00:05:18.530> data<00:05:18.710> and<00:05:19.010> in 00:05:19.360 --> 00:05:19.370 align:start position:0% have two kids that know the data and in 00:05:19.370 --> 00:05:20.890 align:start position:0% have two kids that know the data and in the<00:05:19.490> second<00:05:19.760> round<00:05:19.910> they<00:05:20.090> basically<00:05:20.570> do<00:05:20.750> the 00:05:20.890 --> 00:05:20.900 align:start position:0% the second round they basically do the 00:05:20.900 --> 00:05:23.710 align:start position:0% the second round they basically do the same<00:05:20.930> thing<00:05:21.110> again<00:05:21.320> they<00:05:22.010> pick<00:05:22.880> randomly 00:05:23.710 --> 00:05:23.720 align:start position:0% same thing again they pick randomly 00:05:23.720 --> 00:05:26.050 align:start position:0% same thing again they pick randomly nucleus<00:05:24.350> and<00:05:24.590> sent<00:05:24.830> the<00:05:24.949> data<00:05:25.070> to<00:05:25.340> them<00:05:25.490> they 00:05:26.050 --> 00:05:26.060 align:start position:0% nucleus and sent the data to them they 00:05:26.060 --> 00:05:28.210 align:start position:0% nucleus and sent the data to them they and<00:05:26.419> do<00:05:26.900> this<00:05:27.050> a<00:05:27.110> couple<00:05:27.199> of<00:05:27.470> times<00:05:27.680> and<00:05:27.949> after 00:05:28.210 --> 00:05:28.220 align:start position:0% and do this a couple of times and after 00:05:28.220 --> 00:05:31.150 align:start position:0% and do this a couple of times and after a<00:05:28.250> few<00:05:28.460> rounds<00:05:28.990> the<00:05:29.990> whole<00:05:30.110> network<00:05:30.470> knows<00:05:30.950> the 00:05:31.150 --> 00:05:31.160 align:start position:0% a few rounds the whole network knows the 00:05:31.160 --> 00:05:35.409 align:start position:0% a few rounds the whole network knows the data<00:05:31.280> and<00:05:31.580> that's<00:05:31.880> a<00:05:32.000> very<00:05:32.120> simple<00:05:32.690> and<00:05:34.389> yeah<00:05:35.389> a 00:05:35.409 --> 00:05:35.419 align:start position:0% data and that's a very simple and yeah a 00:05:35.419 --> 00:05:37.960 align:start position:0% data and that's a very simple and yeah a static<00:05:35.810> protocol<00:05:36.200> that's<00:05:36.770> also<00:05:37.070> very 00:05:37.960 --> 00:05:37.970 align:start position:0% static protocol that's also very 00:05:37.970 --> 00:05:40.089 align:start position:0% static protocol that's also very efficient<00:05:38.360> and<00:05:38.510> this<00:05:39.110> process<00:05:39.349> is<00:05:39.530> also<00:05:39.830> very 00:05:40.089 --> 00:05:40.099 align:start position:0% efficient and this process is also very 00:05:40.099 --> 00:05:42.400 align:start position:0% efficient and this process is also very fast<00:05:40.370> and<00:05:40.669> safe<00:05:41.210> in<00:05:41.419> case<00:05:41.599> of<00:05:41.810> network 00:05:42.400 --> 00:05:42.410 align:start position:0% fast and safe in case of network 00:05:42.410 --> 00:05:49.480 align:start position:0% fast and safe in case of network failures<00:05:45.039> we<00:05:46.039> want<00:05:46.310> to<00:05:46.370> apply<00:05:46.610> this<00:05:46.669> in<00:05:48.099> in<00:05:49.099> two 00:05:49.480 --> 00:05:49.490 align:start position:0% failures we want to apply this in in two 00:05:49.490 --> 00:05:51.700 align:start position:0% failures we want to apply this in in two different<00:05:49.789> settings<00:05:49.970> gossiping<00:05:50.660> once<00:05:51.229> in<00:05:51.560> the 00:05:51.700 --> 00:05:51.710 align:start position:0% different settings gossiping once in the 00:05:51.710 --> 00:05:53.500 align:start position:0% different settings gossiping once in the shot<00:05:51.860> networks<00:05:52.220> and<00:05:52.520> once<00:05:52.820> in<00:05:53.150> the<00:05:53.300> beacon 00:05:53.500 --> 00:05:53.510 align:start position:0% shot networks and once in the beacon 00:05:53.510 --> 00:05:56.020 align:start position:0% shot networks and once in the beacon network<00:05:54.229> and<00:05:55.220> the<00:05:55.280> difference<00:05:55.610> between<00:05:55.880> these 00:05:56.020 --> 00:05:56.030 align:start position:0% network and the difference between these 00:05:56.030 --> 00:05:57.670 align:start position:0% network and the difference between these two<00:05:56.180> settings<00:05:56.510> is<00:05:56.660> that<00:05:56.900> in<00:05:57.020> the<00:05:57.169> shot 00:05:57.670 --> 00:05:57.680 align:start position:0% two settings is that in the shot 00:05:57.680 --> 00:05:59.950 align:start position:0% two settings is that in the shot networks<00:05:58.070> be<00:05:58.190> only<00:05:58.430> a<00:05:58.460> few<00:05:58.729> nodes<00:05:58.960> because 00:05:59.950 --> 00:05:59.960 align:start position:0% networks be only a few nodes because 00:05:59.960 --> 00:06:03.400 align:start position:0% networks be only a few nodes because they<00:06:00.699> distribute<00:06:01.699> themselves<00:06:01.880> over<00:06:02.539> the 00:06:03.400 --> 00:06:03.410 align:start position:0% they distribute themselves over the 00:06:03.410 --> 00:06:05.050 align:start position:0% they distribute themselves over the whole<00:06:03.530> set<00:06:03.949> of<00:06:04.099> nodes<00:06:04.280> distribute<00:06:04.789> themselves 00:06:05.050 --> 00:06:05.060 align:start position:0% whole set of nodes distribute themselves 00:06:05.060 --> 00:06:08.860 align:start position:0% whole set of nodes distribute themselves over<00:06:05.930> the<00:06:06.110> different<00:06:06.410> shots<00:06:06.910> but<00:06:07.910> we<00:06:08.449> have<00:06:08.570> a 00:06:08.860 --> 00:06:08.870 align:start position:0% over the different shots but we have a 00:06:08.870 --> 00:06:11.409 align:start position:0% over the different shots but we have a comparatively<00:06:09.590> high<00:06:09.710> throughput<00:06:10.210> so<00:06:11.210> a<00:06:11.240> lot 00:06:11.409 --> 00:06:11.419 align:start position:0% comparatively high throughput so a lot 00:06:11.419 --> 00:06:13.750 align:start position:0% comparatively high throughput so a lot of<00:06:11.539> data<00:06:11.720> is<00:06:11.930> transmitted<00:06:12.590> there<00:06:12.770> and<00:06:13.010> in<00:06:13.669> the 00:06:13.750 --> 00:06:13.760 align:start position:0% of data is transmitted there and in the 00:06:13.760 --> 00:06:15.129 align:start position:0% of data is transmitted there and in the beacon<00:06:14.030> network<00:06:14.330> we<00:06:14.570> have<00:06:14.660> a<00:06:14.690> lot<00:06:14.870> of<00:06:14.900> nodes 00:06:15.129 --> 00:06:15.139 align:start position:0% beacon network we have a lot of nodes 00:06:15.139 --> 00:06:16.839 align:start position:0% beacon network we have a lot of nodes because<00:06:15.680> all<00:06:15.889> of<00:06:16.070> the<00:06:16.190> nodes<00:06:16.550> in<00:06:16.729> the<00:06:16.760> network 00:06:16.839 --> 00:06:16.849 align:start position:0% because all of the nodes in the network 00:06:16.849 --> 00:06:21.939 align:start position:0% because all of the nodes in the network participate<00:06:17.570> here<00:06:18.669> but<00:06:19.669> it's<00:06:20.389> much<00:06:21.139> much<00:06:21.710> less 00:06:21.939 --> 00:06:21.949 align:start position:0% participate here but it's much much less 00:06:21.949 --> 00:06:26.560 align:start position:0% participate here but it's much much less data<00:06:23.590> so<00:06:24.590> we<00:06:25.250> did<00:06:25.400> some<00:06:25.550> simulations<00:06:25.699> to 00:06:26.560 --> 00:06:26.570 align:start position:0% data so we did some simulations to 00:06:26.570 --> 00:06:29.260 align:start position:0% data so we did some simulations to basically<00:06:26.870> answer<00:06:27.770> two<00:06:27.889> questions<00:06:28.240> the<00:06:29.240> first 00:06:29.260 --> 00:06:29.270 align:start position:0% basically answer two questions the first 00:06:29.270 --> 00:06:31.680 align:start position:0% basically answer two questions the first one<00:06:29.570> is<00:06:29.720> can<00:06:30.199> the<00:06:30.349> network<00:06:30.590> handle<00:06:30.860> is<00:06:30.949> handle 00:06:31.680 --> 00:06:31.690 align:start position:0% one is can the network handle is handle 00:06:31.690 --> 00:06:35.380 align:start position:0% one is can the network handle is handle our<00:06:32.690> and<00:06:33.260> the<00:06:33.590> numbers<00:06:33.860> we<00:06:34.010> have<00:06:34.039> or<00:06:34.520> the<00:06:34.789> the 00:06:35.380 --> 00:06:35.390 align:start position:0% our and the numbers we have or the the 00:06:35.390 --> 00:06:38.170 align:start position:0% our and the numbers we have or the the settings<00:06:35.599> we<00:06:35.870> have<00:06:35.900> and<00:06:36.229> how<00:06:36.950> fast<00:06:37.219> does<00:06:37.520> it<00:06:37.700> is 00:06:38.170 --> 00:06:38.180 align:start position:0% settings we have and how fast does it is 00:06:38.180 --> 00:06:39.760 align:start position:0% settings we have and how fast does it is the<00:06:38.539> propagation<00:06:38.960> how<00:06:39.140> much<00:06:39.320> time<00:06:39.560> does<00:06:39.710> it 00:06:39.760 --> 00:06:39.770 align:start position:0% the propagation how much time does it 00:06:39.770 --> 00:06:40.040 align:start position:0% the propagation how much time does it take 00:06:40.040 --> 00:06:40.050 align:start position:0% take 00:06:40.050 --> 00:06:42.860 align:start position:0% take to<00:06:40.169> propagate<00:06:40.680> data<00:06:41.180> and<00:06:42.180> to<00:06:42.419> do<00:06:42.539> this<00:06:42.659> we 00:06:42.860 --> 00:06:42.870 align:start position:0% to propagate data and to do this we 00:06:42.870 --> 00:06:45.800 align:start position:0% to propagate data and to do this we implemented<00:06:43.610> we<00:06:44.610> needed<00:06:44.940> in<00:06:45.120> implementation 00:06:45.800 --> 00:06:45.810 align:start position:0% implemented we needed in implementation 00:06:45.810 --> 00:06:47.809 align:start position:0% implemented we needed in implementation and<00:06:46.139> reuse<00:06:46.470> gossips<00:06:46.860> up<00:06:47.009> and<00:06:47.310> that's<00:06:47.580> been 00:06:47.809 --> 00:06:47.819 align:start position:0% and reuse gossips up and that's been 00:06:47.819 --> 00:06:50.809 align:start position:0% and reuse gossips up and that's been designed<00:06:48.180> by<00:06:48.360> a<00:06:48.389> lipid<00:06:48.750> B<00:06:49.009> and<00:06:50.009> we<00:06:50.159> which<00:06:50.610> will 00:06:50.809 --> 00:06:50.819 align:start position:0% designed by a lipid B and we which will 00:06:50.819 --> 00:06:52.670 align:start position:0% designed by a lipid B and we which will be<00:06:50.909> probably<00:06:51.120> or<00:06:51.479> most<00:06:51.780> likely<00:06:52.080> will<00:06:52.349> use<00:06:52.500> in 00:06:52.670 --> 00:06:52.680 align:start position:0% be probably or most likely will use in 00:06:52.680 --> 00:06:56.270 align:start position:0% be probably or most likely will use in the<00:06:52.770> end<00:06:53.090> and<00:06:54.090> we<00:06:54.479> implemented<00:06:54.750> that<00:06:54.930> and<00:06:55.289> then 00:06:56.270 --> 00:06:56.280 align:start position:0% the end and we implemented that and then 00:06:56.280 --> 00:06:57.800 align:start position:0% the end and we implemented that and then another<00:06:56.909> thing<00:06:57.120> we<00:06:57.210> need<00:06:57.330> if<00:06:57.509> we<00:06:57.659> do<00:06:57.780> a 00:06:57.800 --> 00:06:57.810 align:start position:0% another thing we need if we do a 00:06:57.810 --> 00:06:59.990 align:start position:0% another thing we need if we do a simulations<00:06:58.289> we<00:06:58.440> need<00:06:58.590> to<00:06:58.680> make<00:06:59.669> sure<00:06:59.819> that 00:06:59.990 --> 00:07:00.000 align:start position:0% simulations we need to make sure that 00:07:00.000 --> 00:07:03.649 align:start position:0% simulations we need to make sure that they<00:07:00.180> represent<00:07:01.080> reality<00:07:01.470> in<00:07:01.560> some<00:07:01.710> sense<00:07:02.659> and 00:07:03.649 --> 00:07:03.659 align:start position:0% they represent reality in some sense and 00:07:03.659 --> 00:07:06.950 align:start position:0% they represent reality in some sense and in<00:07:04.349> particular<00:07:04.800> we<00:07:04.919> need<00:07:05.069> to<00:07:05.159> know<00:07:05.310> what<00:07:05.960> the 00:07:06.950 --> 00:07:06.960 align:start position:0% in particular we need to know what the 00:07:06.960 --> 00:07:09.050 align:start position:0% in particular we need to know what the the<00:07:07.710> connections<00:07:08.159> of<00:07:08.370> the<00:07:08.430> net<00:07:08.759> the<00:07:08.789> nodes 00:07:09.050 --> 00:07:09.060 align:start position:0% the connections of the net the nodes 00:07:09.060 --> 00:07:10.939 align:start position:0% the connections of the net the nodes have<00:07:09.270> which<00:07:09.539> each<00:07:10.199> other<00:07:10.409> what<00:07:10.590> what 00:07:10.939 --> 00:07:10.949 align:start position:0% have which each other what what 00:07:10.949 --> 00:07:13.430 align:start position:0% have which each other what what bandwidth<00:07:11.310> they<00:07:11.520> have<00:07:11.669> and<00:07:12.440> unfortunately 00:07:13.430 --> 00:07:13.440 align:start position:0% bandwidth they have and unfortunately 00:07:13.440 --> 00:07:15.320 align:start position:0% bandwidth they have and unfortunately there's<00:07:13.710> a<00:07:13.889> scientific<00:07:14.490> paper<00:07:14.610> that<00:07:15.210> has 00:07:15.320 --> 00:07:15.330 align:start position:0% there's a scientific paper that has 00:07:15.330 --> 00:07:18.680 align:start position:0% there's a scientific paper that has measured<00:07:15.629> this<00:07:15.780> and<00:07:16.409> we<00:07:16.889> just<00:07:17.120> picked<00:07:18.120> those 00:07:18.680 --> 00:07:18.690 align:start position:0% measured this and we just picked those 00:07:18.690 --> 00:07:21.219 align:start position:0% measured this and we just picked those numbers<00:07:19.050> from<00:07:19.229> the<00:07:19.440> current<00:07:20.310> if<00:07:20.400> your<00:07:20.550> network 00:07:21.219 --> 00:07:21.229 align:start position:0% numbers from the current if your network 00:07:21.229 --> 00:07:24.559 align:start position:0% numbers from the current if your network and<00:07:22.229> here's<00:07:23.039> what<00:07:23.159> we<00:07:23.250> got<00:07:23.400> we<00:07:23.699> basically 00:07:24.559 --> 00:07:24.569 align:start position:0% and here's what we got we basically 00:07:24.569 --> 00:07:28.879 align:start position:0% and here's what we got we basically looked<00:07:25.259> at<00:07:25.379> and<00:07:26.990> how<00:07:27.990> much<00:07:28.139> time<00:07:28.349> it<00:07:28.500> takes<00:07:28.620> to 00:07:28.879 --> 00:07:28.889 align:start position:0% looked at and how much time it takes to 00:07:28.889 --> 00:07:32.719 align:start position:0% looked at and how much time it takes to the<00:07:29.840> propagation<00:07:30.840> of<00:07:31.080> a<00:07:31.680> message<00:07:32.129> through<00:07:32.610> the 00:07:32.719 --> 00:07:32.729 align:start position:0% the propagation of a message through the 00:07:32.729 --> 00:07:34.850 align:start position:0% the propagation of a message through the network<00:07:33.060> and<00:07:33.300> over<00:07:33.960> time<00:07:34.169> so<00:07:34.500> at<00:07:34.650> the 00:07:34.850 --> 00:07:34.860 align:start position:0% network and over time so at the 00:07:34.860 --> 00:07:36.860 align:start position:0% network and over time so at the beginning<00:07:35.310> time<00:07:35.789> zero<00:07:36.150> no<00:07:36.569> one<00:07:36.719> knows 00:07:36.860 --> 00:07:36.870 align:start position:0% beginning time zero no one knows 00:07:36.870 --> 00:07:38.930 align:start position:0% beginning time zero no one knows networks<00:07:37.319> no<00:07:37.949> one<00:07:38.069> knows<00:07:38.219> the<00:07:38.400> message<00:07:38.699> the 00:07:38.930 --> 00:07:38.940 align:start position:0% networks no one knows the message the 00:07:38.940 --> 00:07:40.459 align:start position:0% networks no one knows the message the network<00:07:39.210> the<00:07:39.509> message<00:07:39.780> is<00:07:39.900> created<00:07:40.229> at<00:07:40.349> time 00:07:40.459 --> 00:07:40.469 align:start position:0% network the message is created at time 00:07:40.469 --> 00:07:42.439 align:start position:0% network the message is created at time zero<00:07:40.740> and<00:07:41.009> then<00:07:41.340> it<00:07:41.370> starts<00:07:42.180> to<00:07:42.240> be 00:07:42.439 --> 00:07:42.449 align:start position:0% zero and then it starts to be 00:07:42.449 --> 00:07:44.120 align:start position:0% zero and then it starts to be transmitted<00:07:43.169> or<00:07:43.259> propagates<00:07:43.710> through<00:07:44.069> the 00:07:44.120 --> 00:07:44.130 align:start position:0% transmitted or propagates through the 00:07:44.130 --> 00:07:46.189 align:start position:0% transmitted or propagates through the network<00:07:44.550> and<00:07:44.699> at<00:07:44.969> some<00:07:45.150> point<00:07:45.389> it<00:07:45.630> reaches<00:07:45.930> one 00:07:46.189 --> 00:07:46.199 align:start position:0% network and at some point it reaches one 00:07:46.199 --> 00:07:48.920 align:start position:0% network and at some point it reaches one meaning<00:07:46.740> that<00:07:46.889> the<00:07:47.389> the<00:07:48.389> whole<00:07:48.509> network<00:07:48.810> has 00:07:48.920 --> 00:07:48.930 align:start position:0% meaning that the the whole network has 00:07:48.930 --> 00:07:51.469 align:start position:0% meaning that the the whole network has seen<00:07:49.080> the<00:07:49.229> message<00:07:49.500> and<00:07:50.219> we<00:07:50.699> did<00:07:51.060> this<00:07:51.240> for<00:07:51.449> a 00:07:51.469 --> 00:07:51.479 align:start position:0% seen the message and we did this for a 00:07:51.479 --> 00:07:53.689 align:start position:0% seen the message and we did this for a couple<00:07:51.539> of<00:07:51.779> block<00:07:51.960> sizes<00:07:52.190> one<00:07:53.190> thing<00:07:53.370> I<00:07:53.430> forgot 00:07:53.689 --> 00:07:53.699 align:start position:0% couple of block sizes one thing I forgot 00:07:53.699 --> 00:07:56.300 align:start position:0% couple of block sizes one thing I forgot this<00:07:53.849> is<00:07:54.000> for<00:07:54.180> four<00:07:54.449> shots<00:07:54.690> so<00:07:54.900> for<00:07:55.620> a<00:07:55.860> single 00:07:56.300 --> 00:07:56.310 align:start position:0% this is for four shots so for a single 00:07:56.310 --> 00:07:57.890 align:start position:0% this is for four shots so for a single shot<00:07:56.340> network<00:07:56.819> where<00:07:56.969> we<00:07:57.060> have<00:07:57.180> maybe<00:07:57.810> a 00:07:57.890 --> 00:07:57.900 align:start position:0% shot network where we have maybe a 00:07:57.900 --> 00:08:01.790 align:start position:0% shot network where we have maybe a thousand<00:07:58.349> nodes<00:07:59.000> and<00:08:00.289> the<00:08:01.289> numbers<00:08:01.560> we<00:08:01.680> get 00:08:01.790 --> 00:08:01.800 align:start position:0% thousand nodes and the numbers we get 00:08:01.800 --> 00:08:03.890 align:start position:0% thousand nodes and the numbers we get here<00:08:01.979> is<00:08:02.190> so<00:08:02.759> first<00:08:03.000> the<00:08:03.240> first<00:08:03.270> thing<00:08:03.539> we<00:08:03.750> see 00:08:03.890 --> 00:08:03.900 align:start position:0% here is so first the first thing we see 00:08:03.900 --> 00:08:06.890 align:start position:0% here is so first the first thing we see is<00:08:03.990> that<00:08:04.229> it<00:08:04.469> works<00:08:04.650> so<00:08:05.009> it's<00:08:05.969> not<00:08:06.150> like<00:08:06.389> it 00:08:06.890 --> 00:08:06.900 align:start position:0% is that it works so it's not like it 00:08:06.900 --> 00:08:09.140 align:start position:0% is that it works so it's not like it takes<00:08:07.139> forever<00:08:07.319> or<00:08:07.680> it<00:08:08.009> does<00:08:08.580> never<00:08:08.940> reach 00:08:09.140 --> 00:08:09.150 align:start position:0% takes forever or it does never reach 00:08:09.150 --> 00:08:11.629 align:start position:0% takes forever or it does never reach this<00:08:09.300> one<00:08:09.770> messages<00:08:10.770> are<00:08:10.889> always<00:08:11.129> transmitted 00:08:11.629 --> 00:08:11.639 align:start position:0% this one messages are always transmitted 00:08:11.639 --> 00:08:14.719 align:start position:0% this one messages are always transmitted and<00:08:12.349> the<00:08:13.349> larger<00:08:13.949> the<00:08:13.979> block<00:08:14.219> size<00:08:14.400> of<00:08:14.550> course 00:08:14.719 --> 00:08:14.729 align:start position:0% and the larger the block size of course 00:08:14.729 --> 00:08:16.490 align:start position:0% and the larger the block size of course the<00:08:14.819> longer<00:08:15.000> it<00:08:15.150> takes<00:08:15.180> but<00:08:15.900> for<00:08:16.139> a<00:08:16.169> small 00:08:16.490 --> 00:08:16.500 align:start position:0% the longer it takes but for a small 00:08:16.500 --> 00:08:18.290 align:start position:0% the longer it takes but for a small block<00:08:16.710> size<00:08:16.889> of<00:08:17.099> one<00:08:17.400> or<00:08:17.520> two<00:08:17.610> kilobytes<00:08:17.940> maybe 00:08:18.290 --> 00:08:18.300 align:start position:0% block size of one or two kilobytes maybe 00:08:18.300 --> 00:08:20.839 align:start position:0% block size of one or two kilobytes maybe it<00:08:18.479> takes<00:08:18.659> two<00:08:18.840> seconds<00:08:19.199> and<00:08:19.379> for<00:08:20.129> larger<00:08:20.669> ones 00:08:20.839 --> 00:08:20.849 align:start position:0% it takes two seconds and for larger ones 00:08:20.849 --> 00:08:23.570 align:start position:0% it takes two seconds and for larger ones it<00:08:21.060> gets<00:08:21.479> longer<00:08:21.690> and<00:08:21.870> longer<00:08:21.990> but<00:08:22.740> even<00:08:23.430> one 00:08:23.570 --> 00:08:23.580 align:start position:0% it gets longer and longer but even one 00:08:23.580 --> 00:08:27.499 align:start position:0% it gets longer and longer but even one megabyte<00:08:23.940> is<00:08:24.120> still<00:08:24.509> eight<00:08:24.719> seconds<00:08:26.509> now 00:08:27.499 --> 00:08:27.509 align:start position:0% megabyte is still eight seconds now 00:08:27.509 --> 00:08:30.140 align:start position:0% megabyte is still eight seconds now another<00:08:27.960> thing<00:08:28.110> we<00:08:28.319> should<00:08:28.349> look<00:08:28.590> at<00:08:28.740> is<00:08:29.150> what 00:08:30.140 --> 00:08:30.150 align:start position:0% another thing we should look at is what 00:08:30.150 --> 00:08:34.790 align:start position:0% another thing we should look at is what bandwidth<00:08:30.810> is<00:08:31.050> actually<00:08:31.529> used<00:08:32.719> and<00:08:33.719> we<00:08:34.589> see 00:08:34.790 --> 00:08:34.800 align:start position:0% bandwidth is actually used and we see 00:08:34.800 --> 00:08:36.709 align:start position:0% bandwidth is actually used and we see here<00:08:35.070> and<00:08:35.339> this<00:08:35.459> is<00:08:35.640> a<00:08:35.669> histogram<00:08:35.940> of<00:08:36.180> all<00:08:36.570> the 00:08:36.709 --> 00:08:36.719 align:start position:0% here and this is a histogram of all the 00:08:36.719 --> 00:08:40.490 align:start position:0% here and this is a histogram of all the nodes<00:08:36.899> and<00:08:37.589> how<00:08:37.769> much<00:08:37.949> data<00:08:38.310> how<00:08:39.209> much<00:08:39.570> of<00:08:39.810> what 00:08:40.490 --> 00:08:40.500 align:start position:0% nodes and how much data how much of what 00:08:40.500 --> 00:08:42.290 align:start position:0% nodes and how much data how much of what fraction<00:08:40.979> of<00:08:41.010> their<00:08:41.190> beta<00:08:41.370> bandwidth<00:08:42.120> they 00:08:42.290 --> 00:08:42.300 align:start position:0% fraction of their beta bandwidth they 00:08:42.300 --> 00:08:44.720 align:start position:0% fraction of their beta bandwidth they use<00:08:42.449> we<00:08:42.959> see<00:08:43.110> that<00:08:43.289> most<00:08:43.529> most<00:08:44.070> nodes<00:08:44.370> use 00:08:44.720 --> 00:08:44.730 align:start position:0% use we see that most most nodes use 00:08:44.730 --> 00:08:48.710 align:start position:0% use we see that most most nodes use about<00:08:45.000> 20%<00:08:45.360> of<00:08:46.140> the<00:08:46.440> bandwidth<00:08:46.800> and<00:08:47.690> some<00:08:48.690> a 00:08:48.710 --> 00:08:48.720 align:start position:0% about 20% of the bandwidth and some a 00:08:48.720 --> 00:08:50.660 align:start position:0% about 20% of the bandwidth and some a little<00:08:49.050> bit<00:08:49.140> more<00:08:49.320> but<00:08:49.500> no<00:08:49.740> nodes<00:08:50.160> use<00:08:50.399> more 00:08:50.660 --> 00:08:50.670 align:start position:0% little bit more but no nodes use more 00:08:50.670 --> 00:08:53.490 align:start position:0% little bit more but no nodes use more than<00:08:50.820> 60%<00:08:51.149> of<00:08:51.540> the<00:08:51.660> bandwidth<00:08:51.990> this<00:08:52.620> is 00:08:53.490 --> 00:08:53.500 align:start position:0% than 60% of the bandwidth this is 00:08:53.500 --> 00:08:56.040 align:start position:0% than 60% of the bandwidth this is important<00:08:54.150> because<00:08:55.150> it<00:08:55.450> tells<00:08:55.720> us<00:08:55.900> basically 00:08:56.040 --> 00:08:56.050 align:start position:0% important because it tells us basically 00:08:56.050 --> 00:08:57.810 align:start position:0% important because it tells us basically two<00:08:56.380> things<00:08:56.620> the<00:08:56.920> first<00:08:57.130> one<00:08:57.280> is<00:08:57.430> that<00:08:57.670> we're 00:08:57.810 --> 00:08:57.820 align:start position:0% two things the first one is that we're 00:08:57.820 --> 00:09:00.630 align:start position:0% two things the first one is that we're not<00:08:58.140> operating<00:08:59.140> at<00:08:59.260> capacity<00:08:59.290> even<00:08:59.950> at<00:09:00.220> large 00:09:00.630 --> 00:09:00.640 align:start position:0% not operating at capacity even at large 00:09:00.640 --> 00:09:05.310 align:start position:0% not operating at capacity even at large box<00:09:00.940> sizes<00:09:01.140> so<00:09:03.150> if<00:09:04.150> there<00:09:04.510> were<00:09:04.720> notes<00:09:05.050> that 00:09:05.310 --> 00:09:05.320 align:start position:0% box sizes so if there were notes that 00:09:05.320 --> 00:09:06.960 align:start position:0% box sizes so if there were notes that use<00:09:05.470> a<00:09:05.500> 100<00:09:05.980> percent<00:09:06.250> of<00:09:06.340> the<00:09:06.430> bandwidth<00:09:06.760> we 00:09:06.960 --> 00:09:06.970 align:start position:0% use a 100 percent of the bandwidth we 00:09:06.970 --> 00:09:08.670 align:start position:0% use a 100 percent of the bandwidth we would<00:09:07.180> be<00:09:07.330> we<00:09:07.990> could<00:09:08.020> be<00:09:08.260> pretty<00:09:08.470> sure<00:09:08.620> that 00:09:08.670 --> 00:09:08.680 align:start position:0% would be we could be pretty sure that 00:09:08.680 --> 00:09:11.040 align:start position:0% would be we could be pretty sure that they<00:09:09.280> will<00:09:09.490> not<00:09:09.670> keep<00:09:09.850> up<00:09:10.030> in<00:09:10.510> the<00:09:10.690> long<00:09:10.870> run 00:09:11.040 --> 00:09:11.050 align:start position:0% they will not keep up in the long run 00:09:11.050 --> 00:09:13.920 align:start position:0% they will not keep up in the long run and<00:09:11.790> this<00:09:12.790> is<00:09:12.910> not<00:09:13.030> what's<00:09:13.180> happening<00:09:13.240> the 00:09:13.920 --> 00:09:13.930 align:start position:0% and this is not what's happening the 00:09:13.930 --> 00:09:15.930 align:start position:0% and this is not what's happening the second<00:09:14.260> thing<00:09:14.470> is<00:09:14.650> we<00:09:15.310> see<00:09:15.490> that<00:09:15.520> there's<00:09:15.850> a 00:09:15.930 --> 00:09:15.940 align:start position:0% second thing is we see that there's a 00:09:15.940 --> 00:09:17.880 align:start position:0% second thing is we see that there's a lot<00:09:16.060> of<00:09:16.180> bandwidth<00:09:16.510> available<00:09:17.050> if<00:09:17.260> we<00:09:17.500> get<00:09:17.650> new 00:09:17.880 --> 00:09:17.890 align:start position:0% lot of bandwidth available if we get new 00:09:17.890 --> 00:09:19.710 align:start position:0% lot of bandwidth available if we get new nodes<00:09:18.130> that<00:09:18.340> join<00:09:18.550> the<00:09:18.670> network<00:09:18.850> and<00:09:19.270> download 00:09:19.710 --> 00:09:19.720 align:start position:0% nodes that join the network and download 00:09:19.720 --> 00:09:22.680 align:start position:0% nodes that join the network and download a<00:09:19.990> new<00:09:20.380> data<00:09:20.590> and<00:09:21.310> charts<00:09:22.030> the<00:09:22.300> download<00:09:22.600> the 00:09:22.680 --> 00:09:22.690 align:start position:0% a new data and charts the download the 00:09:22.690 --> 00:09:25.680 align:start position:0% a new data and charts the download the data<00:09:22.870> because<00:09:23.440> this<00:09:23.680> only<00:09:24.100> simulates<00:09:24.850> the 00:09:25.680 --> 00:09:25.690 align:start position:0% data because this only simulates the 00:09:25.690 --> 00:09:27.840 align:start position:0% data because this only simulates the propagation<00:09:26.470> of<00:09:26.680> data<00:09:26.950> that's<00:09:27.160> created<00:09:27.580> newly 00:09:27.840 --> 00:09:27.850 align:start position:0% propagation of data that's created newly 00:09:27.850 --> 00:09:30.540 align:start position:0% propagation of data that's created newly and<00:09:28.030> not<00:09:28.380> synchronization<00:09:29.380> of<00:09:29.440> chain<00:09:29.710> chains 00:09:30.540 --> 00:09:30.550 align:start position:0% and not synchronization of chain chains 00:09:30.550 --> 00:09:34.170 align:start position:0% and not synchronization of chain chains and<00:09:30.790> so<00:09:30.910> on<00:09:31.530> so<00:09:32.530> that's<00:09:32.650> good<00:09:32.860> and<00:09:33.120> now<00:09:34.120> we 00:09:34.170 --> 00:09:34.180 align:start position:0% and so on so that's good and now we 00:09:34.180 --> 00:09:36.990 align:start position:0% and so on so that's good and now we looked<00:09:34.780> at<00:09:34.930> the<00:09:35.440> beacon<00:09:35.980> Network<00:09:36.820> where<00:09:36.970> we 00:09:36.990 --> 00:09:37.000 align:start position:0% looked at the beacon Network where we 00:09:37.000 --> 00:09:39.480 align:start position:0% looked at the beacon Network where we have<00:09:37.150> a<00:09:37.180> lot<00:09:37.420> more<00:09:37.450> nodes<00:09:37.780> I<00:09:38.340> simulated<00:09:39.340> here 00:09:39.480 --> 00:09:39.490 align:start position:0% have a lot more nodes I simulated here 00:09:39.490 --> 00:09:43.980 align:start position:0% have a lot more nodes I simulated here 100,000<00:09:40.210> nodes<00:09:40.950> and<00:09:41.950> we<00:09:42.700> see<00:09:42.880> the<00:09:43.480> same<00:09:43.630> thing 00:09:43.980 --> 00:09:43.990 align:start position:0% 100,000 nodes and we see the same thing 00:09:43.990 --> 00:09:46.710 align:start position:0% 100,000 nodes and we see the same thing basically<00:09:44.410> at<00:09:44.890> time<00:09:45.040> 0<00:09:45.370> a<00:09:45.820> block<00:09:46.240> is<00:09:46.360> created 00:09:46.710 --> 00:09:46.720 align:start position:0% basically at time 0 a block is created 00:09:46.720 --> 00:09:47.940 align:start position:0% basically at time 0 a block is created and<00:09:46.900> it<00:09:47.050> propagates<00:09:47.230> through<00:09:47.560> the<00:09:47.620> network 00:09:47.940 --> 00:09:47.950 align:start position:0% and it propagates through the network 00:09:47.950 --> 00:09:49.920 align:start position:0% and it propagates through the network and<00:09:48.100> at<00:09:48.490> some<00:09:48.730> point<00:09:48.940> it<00:09:49.360> reaches<00:09:49.750> all<00:09:49.870> the 00:09:49.920 --> 00:09:49.930 align:start position:0% and at some point it reaches all the 00:09:49.930 --> 00:09:52.800 align:start position:0% and at some point it reaches all the nodes<00:09:50.370> block<00:09:51.370> sizes<00:09:51.610> are<00:09:51.850> smaller<00:09:52.090> here<00:09:52.300> 64 00:09:52.800 --> 00:09:52.810 align:start position:0% nodes block sizes are smaller here 64 00:09:52.810 --> 00:09:55.710 align:start position:0% nodes block sizes are smaller here 64 kilobytes<00:09:53.170> to<00:09:53.260> 512<00:09:53.920> kilobytes<00:09:54.450> we<00:09:55.450> will<00:09:55.600> see 00:09:55.710 --> 00:09:55.720 align:start position:0% kilobytes to 512 kilobytes we will see 00:09:55.720 --> 00:09:58.890 align:start position:0% kilobytes to 512 kilobytes we will see how<00:09:56.410> large<00:09:56.590> they<00:09:56.920> will<00:09:57.400> be<00:09:57.520> in<00:09:57.640> the<00:09:57.760> end<00:09:57.900> and 00:09:58.890 --> 00:09:58.900 align:start position:0% how large they will be in the end and 00:09:58.900 --> 00:10:00.960 align:start position:0% how large they will be in the end and here<00:09:59.589> even<00:09:59.980> though<00:10:00.220> the<00:10:00.430> network<00:10:00.580> is<00:10:00.790> much 00:10:00.960 --> 00:10:00.970 align:start position:0% here even though the network is much 00:10:00.970 --> 00:10:03.090 align:start position:0% here even though the network is much larger<00:10:01.330> we<00:10:01.810> still<00:10:02.050> get<00:10:02.200> propagation<00:10:02.710> times<00:10:02.890> of 00:10:03.090 --> 00:10:03.100 align:start position:0% larger we still get propagation times of 00:10:03.100 --> 00:10:07.050 align:start position:0% larger we still get propagation times of a<00:10:03.570> couple<00:10:04.570> of<00:10:04.630> seconds<00:10:05.040> so<00:10:06.040> this<00:10:06.640> seems<00:10:06.970> to 00:10:07.050 --> 00:10:07.060 align:start position:0% a couple of seconds so this seems to 00:10:07.060 --> 00:10:10.250 align:start position:0% a couple of seconds so this seems to work<00:10:07.150> very<00:10:07.330> well<00:10:07.570> and<00:10:07.930> we're<00:10:08.470> happy<00:10:08.800> with<00:10:08.950> that 00:10:10.250 --> 00:10:10.260 align:start position:0% work very well and we're happy with that 00:10:10.260 --> 00:10:14.360 align:start position:0% work very well and we're happy with that peer<00:10:11.260> discovery<00:10:12.480> that's<00:10:13.480> more<00:10:13.660> complicated 00:10:14.360 --> 00:10:14.370 align:start position:0% peer discovery that's more complicated 00:10:14.370 --> 00:10:17.340 align:start position:0% peer discovery that's more complicated and<00:10:15.370> the<00:10:15.880> job<00:10:16.150> of<00:10:16.270> peer<00:10:16.420> discovery<00:10:16.839> is<00:10:16.900> to<00:10:16.990> find 00:10:17.340 --> 00:10:17.350 align:start position:0% and the job of peer discovery is to find 00:10:17.350 --> 00:10:19.829 align:start position:0% and the job of peer discovery is to find peers<00:10:17.920> in<00:10:18.130> the<00:10:18.250> beacon<00:10:18.490> network<00:10:18.820> and<00:10:19.060> also<00:10:19.780> to 00:10:19.829 --> 00:10:19.839 align:start position:0% peers in the beacon network and also to 00:10:19.839 --> 00:10:22.200 align:start position:0% peers in the beacon network and also to find<00:10:20.080> peers<00:10:20.380> in<00:10:20.500> a<00:10:20.560> specific<00:10:20.770> shot<00:10:21.160> and<00:10:21.580> this 00:10:22.200 --> 00:10:22.210 align:start position:0% find peers in a specific shot and this 00:10:22.210 --> 00:10:24.329 align:start position:0% find peers in a specific shot and this is<00:10:22.450> the<00:10:23.260> challenging<00:10:23.800> or<00:10:24.010> one<00:10:24.130> of<00:10:24.220> the 00:10:24.329 --> 00:10:24.339 align:start position:0% is the challenging or one of the 00:10:24.339 --> 00:10:26.040 align:start position:0% is the challenging or one of the challenging<00:10:24.760> points<00:10:25.089> here<00:10:25.210> because<00:10:25.630> there 00:10:26.040 --> 00:10:26.050 align:start position:0% challenging points here because there 00:10:26.050 --> 00:10:27.600 align:start position:0% challenging points here because there are<00:10:26.080> a<00:10:26.140> lot<00:10:26.170> of<00:10:26.260> shots<00:10:26.530> and<00:10:26.830> if<00:10:26.980> you<00:10:27.100> just<00:10:27.400> pick 00:10:27.600 --> 00:10:27.610 align:start position:0% are a lot of shots and if you just pick 00:10:27.610 --> 00:10:29.460 align:start position:0% are a lot of shots and if you just pick a<00:10:27.760> random<00:10:27.940> node<00:10:28.240> in<00:10:28.390> the<00:10:28.450> network<00:10:28.480> you<00:10:29.200> need<00:10:29.380> to 00:10:29.460 --> 00:10:29.470 align:start position:0% a random node in the network you need to 00:10:29.470 --> 00:10:31.050 align:start position:0% a random node in the network you need to pick<00:10:29.560> a<00:10:29.620> lot<00:10:29.830> of<00:10:29.950> them<00:10:30.100> to<00:10:30.310> find<00:10:30.520> one<00:10:30.730> that's 00:10:31.050 --> 00:10:31.060 align:start position:0% pick a lot of them to find one that's 00:10:31.060 --> 00:10:33.690 align:start position:0% pick a lot of them to find one that's suitable<00:10:31.480> to<00:10:31.660> you<00:10:31.780> so<00:10:32.740> we<00:10:32.860> would<00:10:33.280> like<00:10:33.460> to<00:10:33.610> have 00:10:33.690 --> 00:10:33.700 align:start position:0% suitable to you so we would like to have 00:10:33.700 --> 00:10:36.870 align:start position:0% suitable to you so we would like to have a<00:10:33.730> way<00:10:33.970> that's<00:10:34.240> more<00:10:34.420> efficient<00:10:34.750> than<00:10:34.839> that<00:10:35.880> we 00:10:36.870 --> 00:10:36.880 align:start position:0% a way that's more efficient than that we 00:10:36.880 --> 00:10:39.090 align:start position:0% a way that's more efficient than that we also<00:10:37.030> need<00:10:37.390> this<00:10:37.960> also<00:10:38.200> should<00:10:38.470> be<00:10:38.620> very<00:10:38.800> fast 00:10:39.090 --> 00:10:39.100 align:start position:0% also need this also should be very fast 00:10:39.100 --> 00:10:41.970 align:start position:0% also need this also should be very fast so<00:10:39.370> in<00:10:39.580> that<00:10:39.730> validators<00:10:40.330> who<00:10:40.600> is<00:10:40.810> assigned<00:10:41.740> to 00:10:41.970 --> 00:10:41.980 align:start position:0% so in that validators who is assigned to 00:10:41.980 --> 00:10:44.430 align:start position:0% so in that validators who is assigned to a<00:10:42.010> new<00:10:42.160> shot<00:10:42.370> can<00:10:43.030> start<00:10:43.390> operating<00:10:43.930> as 00:10:44.430 --> 00:10:44.440 align:start position:0% a new shot can start operating as 00:10:44.440 --> 00:10:46.680 align:start position:0% a new shot can start operating as quickly<00:10:44.920> as<00:10:45.100> possible<00:10:45.460> so<00:10:45.670> that<00:10:45.850> at<00:10:46.300> that<00:10:46.480> time 00:10:46.680 --> 00:10:46.690 align:start position:0% quickly as possible so that at that time 00:10:46.690 --> 00:10:51.120 align:start position:0% quickly as possible so that at that time is<00:10:46.930> as<00:10:47.140> short<00:10:47.680> as<00:10:47.800> possible<00:10:48.089> and<00:10:50.130> fourth 00:10:51.120 --> 00:10:51.130 align:start position:0% is as short as possible and fourth 00:10:51.130 --> 00:10:54.270 align:start position:0% is as short as possible and fourth requirement<00:10:51.460> is<00:10:52.030> that<00:10:52.540> the<00:10:53.530> valid<00:10:53.770> data<00:10:53.800> as<00:10:54.190> I 00:10:54.270 --> 00:10:54.280 align:start position:0% requirement is that the valid data as I 00:10:54.280 --> 00:10:55.530 align:start position:0% requirement is that the valid data as I said<00:10:54.460> earlier<00:10:54.730> they<00:10:55.030> would<00:10:55.150> like<00:10:55.300> to<00:10:55.420> be 00:10:55.530 --> 00:10:55.540 align:start position:0% said earlier they would like to be 00:10:55.540 --> 00:10:57.210 align:start position:0% said earlier they would like to be private<00:10:55.900> and<00:10:56.020> if<00:10:56.230> it's<00:10:56.380> easy<00:10:56.680> to<00:10:56.890> discover 00:10:57.210 --> 00:10:57.220 align:start position:0% private and if it's easy to discover 00:10:57.220 --> 00:10:59.220 align:start position:0% private and if it's easy to discover them<00:10:57.430> using<00:10:57.820> this<00:10:57.940> discovery<00:10:58.390> protocol<00:10:58.750> then 00:10:59.220 --> 00:10:59.230 align:start position:0% them using this discovery protocol then 00:10:59.230 --> 00:11:02.510 align:start position:0% them using this discovery protocol then yeah<00:10:59.830> this<00:11:00.100> is<00:11:00.250> not<00:11:00.820> good 00:11:02.510 --> 00:11:02.520 align:start position:0% yeah this is not good 00:11:02.520 --> 00:11:05.820 align:start position:0% yeah this is not good we<00:11:03.520> are<00:11:03.910> considering<00:11:04.390> a<00:11:05.050> bunch<00:11:05.350> of<00:11:05.470> options 00:11:05.820 --> 00:11:05.830 align:start position:0% we are considering a bunch of options 00:11:05.830 --> 00:11:06.720 align:start position:0% we are considering a bunch of options here<00:11:05.950> and 00:11:06.720 --> 00:11:06.730 align:start position:0% here and 00:11:06.730 --> 00:11:11.269 align:start position:0% here and three<00:11:08.670> seem<00:11:09.670> to<00:11:09.790> be<00:11:09.910> viable 00:11:11.269 --> 00:11:11.279 align:start position:0% three seem to be viable 00:11:11.279 --> 00:11:13.949 align:start position:0% three seem to be viable the<00:11:12.279> first<00:11:12.490> one<00:11:12.610> is<00:11:12.760> discovery<00:11:13.269> version<00:11:13.570> 5<00:11:13.720> it 00:11:13.949 --> 00:11:13.959 align:start position:0% the first one is discovery version 5 it 00:11:13.959 --> 00:11:17.160 align:start position:0% the first one is discovery version 5 it has<00:11:13.990> been<00:11:14.430> designed<00:11:15.430> by<00:11:15.790> Felix<00:11:16.630> from<00:11:16.779> the<00:11:16.930> film 00:11:17.160 --> 00:11:17.170 align:start position:0% has been designed by Felix from the film 00:11:17.170 --> 00:11:19.530 align:start position:0% has been designed by Felix from the film foundation<00:11:17.589> to<00:11:18.279> be<00:11:18.370> used<00:11:18.579> in<00:11:18.820> the<00:11:19.029> existing<00:11:19.449> if 00:11:19.530 --> 00:11:19.540 align:start position:0% foundation to be used in the existing if 00:11:19.540 --> 00:11:21.060 align:start position:0% foundation to be used in the existing if you<00:11:19.660> network<00:11:19.990> but<00:11:20.170> it<00:11:20.290> actually<00:11:20.649> has<00:11:20.920> some 00:11:21.060 --> 00:11:21.070 align:start position:0% you network but it actually has some 00:11:21.070 --> 00:11:22.319 align:start position:0% you network but it actually has some nice<00:11:21.160> properties<00:11:21.220> meaning<00:11:21.940> that<00:11:22.060> we<00:11:22.180> can 00:11:22.319 --> 00:11:22.329 align:start position:0% nice properties meaning that we can 00:11:22.329 --> 00:11:24.840 align:start position:0% nice properties meaning that we can could<00:11:22.720> maybe<00:11:23.139> use<00:11:23.380> it<00:11:23.410> for<00:11:23.740> us<00:11:23.829> as<00:11:23.949> well<00:11:24.100> so<00:11:24.130> and 00:11:24.840 --> 00:11:24.850 align:start position:0% could maybe use it for us as well so and 00:11:24.850 --> 00:11:26.790 align:start position:0% could maybe use it for us as well so and it<00:11:25.000> looks<00:11:25.180> very<00:11:25.300> promising<00:11:25.540> I<00:11:25.899> think<00:11:26.110> second 00:11:26.790 --> 00:11:26.800 align:start position:0% it looks very promising I think second 00:11:26.800 --> 00:11:28.889 align:start position:0% it looks very promising I think second one<00:11:26.920> is<00:11:27.100> a<00:11:27.339> simple<00:11:28.149> variation<00:11:28.420> of<00:11:28.690> Kedah 00:11:28.889 --> 00:11:28.899 align:start position:0% one is a simple variation of Kedah 00:11:28.899 --> 00:11:30.660 align:start position:0% one is a simple variation of Kedah million<00:11:29.170> and<00:11:29.320> the<00:11:29.380> third<00:11:29.560> one<00:11:29.709> is<00:11:29.829> to<00:11:30.070> simply 00:11:30.660 --> 00:11:30.670 align:start position:0% million and the third one is to simply 00:11:30.670 --> 00:11:32.780 align:start position:0% million and the third one is to simply use<00:11:30.730> a<00:11:30.820> global<00:11:31.510> gossiping<00:11:32.079> channel<00:11:32.410> to 00:11:32.780 --> 00:11:32.790 align:start position:0% use a global gossiping channel to 00:11:32.790 --> 00:11:38.400 align:start position:0% use a global gossiping channel to propagate<00:11:34.380> the<00:11:35.380> shots<00:11:35.589> we<00:11:35.769> the<00:11:37.079> yet<00:11:38.079> the<00:11:38.170> sharp 00:11:38.400 --> 00:11:38.410 align:start position:0% propagate the shots we the yet the sharp 00:11:38.410 --> 00:11:40.590 align:start position:0% propagate the shots we the yet the sharp preferences<00:11:38.980> in<00:11:39.130> some<00:11:39.310> sense<00:11:39.519> which<00:11:40.089> seems 00:11:40.590 --> 00:11:40.600 align:start position:0% preferences in some sense which seems 00:11:40.600 --> 00:11:43.740 align:start position:0% preferences in some sense which seems kind<00:11:40.870> of<00:11:41.019> boot<00:11:41.589> forth<00:11:41.889> but<00:11:42.130> it<00:11:42.600> might<00:11:43.600> actually 00:11:43.740 --> 00:11:43.750 align:start position:0% kind of boot forth but it might actually 00:11:43.750 --> 00:11:46.920 align:start position:0% kind of boot forth but it might actually be<00:11:43.959> viable<00:11:44.760> but<00:11:45.760> we're<00:11:46.149> still<00:11:46.750> not<00:11:46.779> finished 00:11:46.920 --> 00:11:46.930 align:start position:0% be viable but we're still not finished 00:11:46.930 --> 00:11:51.449 align:start position:0% be viable but we're still not finished with<00:11:47.290> that<00:11:47.470> we're<00:11:47.949> still<00:11:48.160> evaluating<00:11:50.459> yeah 00:11:51.449 --> 00:11:51.459 align:start position:0% with that we're still evaluating yeah 00:11:51.459 --> 00:11:54.569 align:start position:0% with that we're still evaluating yeah but<00:11:52.329> that's<00:11:52.660> it<00:11:53.230> from<00:11:53.620> my<00:11:53.769> side<00:11:53.800> and<00:11:53.980> now<00:11:54.220> Kevin 00:11:54.569 --> 00:11:54.579 align:start position:0% but that's it from my side and now Kevin 00:11:54.579 --> 00:12:08.069 align:start position:0% but that's it from my side and now Kevin will<00:11:54.760> talk<00:11:55.060> about<00:11:56.130> implementation<00:12:06.360> and<00:12:07.360> I'm 00:12:08.069 --> 00:12:08.079 align:start position:0% will talk about implementation and I'm 00:12:08.079 --> 00:12:12.150 align:start position:0% will talk about implementation and I'm going<00:12:08.380> to<00:12:08.410> introduce<00:12:09.750> p2p<00:12:10.750> meditation<00:12:11.410> status 00:12:12.150 --> 00:12:12.160 align:start position:0% going to introduce p2p meditation status 00:12:12.160 --> 00:12:16.920 align:start position:0% going to introduce p2p meditation status on<00:12:12.370> our<00:12:12.670> site<00:12:13.980> so<00:12:14.980> this<00:12:15.459> project<00:12:16.120> them 00:12:16.920 --> 00:12:16.930 align:start position:0% on our site so this project them 00:12:16.930 --> 00:12:20.730 align:start position:0% on our site so this project them Charlene<00:12:17.769> pee-peed<00:12:18.310> of<00:12:18.399> a<00:12:18.490> POC<00:12:18.730> and<00:12:19.269> it<00:12:19.630> is<00:12:19.779> for 00:12:20.730 --> 00:12:20.740 align:start position:0% Charlene pee-peed of a POC and it is for 00:12:20.740 --> 00:12:22.769 align:start position:0% Charlene pee-peed of a POC and it is for for<00:12:20.860> a<00:12:20.889> concept<00:12:21.310> of<00:12:21.490> the<00:12:21.670> current<00:12:22.149> design<00:12:22.269> for 00:12:22.769 --> 00:12:22.779 align:start position:0% for a concept of the current design for 00:12:22.779 --> 00:12:25.129 align:start position:0% for a concept of the current design for if<00:12:22.990> you're<00:12:23.199> in<00:12:23.260> turmoil<00:12:23.560> it'll<00:12:24.519> be<00:12:24.610> there<00:12:24.819> and 00:12:25.129 --> 00:12:25.139 align:start position:0% if you're in turmoil it'll be there and 00:12:25.139 --> 00:12:30.509 align:start position:0% if you're in turmoil it'll be there and we<00:12:26.139> implement<00:12:26.740> it<00:12:26.860> using<00:12:27.160> the<00:12:27.790> p2p<00:12:28.980> so<00:12:29.980> what<00:12:30.399> is 00:12:30.509 --> 00:12:30.519 align:start position:0% we implement it using the p2p so what is 00:12:30.519 --> 00:12:34.769 align:start position:0% we implement it using the p2p so what is the<00:12:30.699> day<00:12:31.000> p2p<00:12:31.769> it<00:12:32.769> is<00:12:33.069> library<00:12:33.790> that<00:12:34.149> has<00:12:34.449> many 00:12:34.769 --> 00:12:34.779 align:start position:0% the day p2p it is library that has many 00:12:34.779 --> 00:12:37.139 align:start position:0% the day p2p it is library that has many useful<00:12:35.110> peer-to-peer<00:12:36.149> networking 00:12:37.139 --> 00:12:37.149 align:start position:0% useful peer-to-peer networking 00:12:37.149 --> 00:12:39.030 align:start position:0% useful peer-to-peer networking components<00:12:37.870> so<00:12:38.230> you<00:12:38.290> can<00:12:38.529> choose<00:12:38.860> the 00:12:39.030 --> 00:12:39.040 align:start position:0% components so you can choose the 00:12:39.040 --> 00:12:41.730 align:start position:0% components so you can choose the components<00:12:39.610> you<00:12:39.760> want<00:12:40.180> or<00:12:40.569> you<00:12:40.779> need<00:12:40.990> to<00:12:41.350> view 00:12:41.730 --> 00:12:41.740 align:start position:0% components you want or you need to view 00:12:41.740 --> 00:12:45.079 align:start position:0% components you want or you need to view your<00:12:41.920> own<00:12:41.980> peer-to-peer<00:12:42.880> applications<00:12:43.410> and 00:12:45.079 --> 00:12:45.089 align:start position:0% your own peer-to-peer applications and 00:12:45.089 --> 00:12:48.350 align:start position:0% your own peer-to-peer applications and currently<00:12:46.089> we're<00:12:46.300> using<00:12:46.329> the<00:12:46.930> TCP 00:12:48.350 --> 00:12:48.360 align:start position:0% currently we're using the TCP 00:12:48.360 --> 00:12:51.480 align:start position:0% currently we're using the TCP cumberlands<00:12:49.360> and<00:12:49.540> kadam<00:12:50.470> layout<00:12:50.769> DHT<00:12:51.220> and 00:12:51.480 --> 00:12:51.490 align:start position:0% cumberlands and kadam layout DHT and 00:12:51.490 --> 00:12:56.309 align:start position:0% cumberlands and kadam layout DHT and pops<00:12:51.760> up<00:12:52.110> and<00:12:53.430> the<00:12:54.430> goal<00:12:54.670> of<00:12:54.910> our<00:12:55.360> project<00:12:55.899> is 00:12:56.309 --> 00:12:56.319 align:start position:0% pops up and the goal of our project is 00:12:56.319 --> 00:12:59.550 align:start position:0% pops up and the goal of our project is we<00:12:57.310> want<00:12:57.490> to<00:12:57.579> see<00:12:57.730> if<00:12:57.940> our<00:12:58.569> current<00:12:59.440> design 00:12:59.550 --> 00:12:59.560 align:start position:0% we want to see if our current design 00:12:59.560 --> 00:13:03.809 align:start position:0% we want to see if our current design meets<00:13:00.519> the<00:13:00.670> needs<00:13:00.940> of<00:13:01.180> ether<00:13:02.019> and<00:13:02.139> 2.0<00:13:02.560> and<00:13:02.949> we 00:13:03.809 --> 00:13:03.819 align:start position:0% meets the needs of ether and 2.0 and we 00:13:03.819 --> 00:13:06.030 align:start position:0% meets the needs of ether and 2.0 and we also<00:13:04.000> want<00:13:04.300> to<00:13:04.389> see<00:13:04.630> if<00:13:04.959> the<00:13:05.410> able<00:13:05.589> to<00:13:05.680> be<00:13:05.769> faced 00:13:06.030 --> 00:13:06.040 align:start position:0% also want to see if the able to be faced 00:13:06.040 --> 00:13:10.139 align:start position:0% also want to see if the able to be faced our<00:13:06.279> needs<00:13:06.630> and<00:13:07.920> it<00:13:08.920> can<00:13:09.160> also<00:13:09.370> serve<00:13:09.910> as 00:13:10.139 --> 00:13:10.149 align:start position:0% our needs and it can also serve as 00:13:10.149 --> 00:13:12.870 align:start position:0% our needs and it can also serve as temporary<00:13:11.019> layer<00:13:11.470> for<00:13:11.949> if<00:13:12.160> you're<00:13:12.339> into<00:13:12.550> foil 00:13:12.870 --> 00:13:12.880 align:start position:0% temporary layer for if you're into foil 00:13:12.880 --> 00:13:16.740 align:start position:0% temporary layer for if you're into foil network<00:13:13.269> a<00:13:13.980> Python<00:13:14.980> implementation<00:13:15.750> until 00:13:16.740 --> 00:13:16.750 align:start position:0% network a Python implementation until 00:13:16.750 --> 00:13:19.170 align:start position:0% network a Python implementation until the<00:13:16.930> Python<00:13:17.319> let<00:13:17.829> beta<00:13:18.010> P<00:13:18.220> implementation<00:13:19.060> is 00:13:19.170 --> 00:13:19.180 align:start position:0% the Python let beta P implementation is 00:13:19.180 --> 00:13:21.050 align:start position:0% the Python let beta P implementation is rate 00:13:21.050 --> 00:13:21.060 align:start position:0% rate 00:13:21.060 --> 00:13:24.990 align:start position:0% rate so<00:13:22.060> the<00:13:22.240> requirement<00:13:22.810> for<00:13:22.870> our<00:13:24.000> networking 00:13:24.990 --> 00:13:25.000 align:start position:0% so the requirement for our networking 00:13:25.000 --> 00:13:29.790 align:start position:0% so the requirement for our networking layer<00:13:25.630> for<00:13:26.410> if<00:13:26.800> you're<00:13:27.040> in<00:13:27.160> tutorial<00:13:28.800> the 00:13:29.790 --> 00:13:29.800 align:start position:0% layer for if you're in tutorial the 00:13:29.800 --> 00:13:31.290 align:start position:0% layer for if you're in tutorial the clients<00:13:30.280> should<00:13:30.490> be<00:13:30.580> able<00:13:30.670> to<00:13:31.000> subscribe 00:13:31.290 --> 00:13:31.300 align:start position:0% clients should be able to subscribe 00:13:31.300 --> 00:13:34.740 align:start position:0% clients should be able to subscribe while<00:13:31.930> to<00:13:32.410> one<00:13:32.770> or<00:13:32.950> more<00:13:33.190> shards<00:13:33.730> so<00:13:33.940> in<00:13:34.570> this 00:13:34.740 --> 00:13:34.750 align:start position:0% while to one or more shards so in this 00:13:34.750 --> 00:13:36.870 align:start position:0% while to one or more shards so in this graph<00:13:35.020> that<00:13:35.350> clients<00:13:35.980> subscribe<00:13:36.340> to<00:13:36.520> to 00:13:36.870 --> 00:13:36.880 align:start position:0% graph that clients subscribe to to 00:13:36.880 --> 00:13:42.420 align:start position:0% graph that clients subscribe to to shards<00:13:37.150> wines<00:13:37.750> flagon<00:13:38.320> one<00:13:38.740> is<00:13:38.980> red<00:13:39.550> and<00:13:41.430> the 00:13:42.420 --> 00:13:42.430 align:start position:0% shards wines flagon one is red and the 00:13:42.430 --> 00:13:44.630 align:start position:0% shards wines flagon one is red and the client<00:13:42.850> should<00:13:42.970> only<00:13:43.270> receive<00:13:43.690> the<00:13:43.810> data<00:13:43.960> from 00:13:44.630 --> 00:13:44.640 align:start position:0% client should only receive the data from 00:13:44.640 --> 00:13:48.480 align:start position:0% client should only receive the data from the<00:13:45.640> shards<00:13:45.970> it<00:13:46.090> has<00:13:46.300> subscribed<00:13:47.080> so<00:13:47.770> in<00:13:48.310> this 00:13:48.480 --> 00:13:48.490 align:start position:0% the shards it has subscribed so in this 00:13:48.490 --> 00:13:50.550 align:start position:0% the shards it has subscribed so in this case<00:13:48.790> that<00:13:49.480> client<00:13:49.870> should<00:13:49.990> only<00:13:50.110> received 00:13:50.550 --> 00:13:50.560 align:start position:0% case that client should only received 00:13:50.560 --> 00:13:52.920 align:start position:0% case that client should only received the<00:13:50.620> plug-in<00:13:51.100> back<00:13:51.460> and<00:13:51.730> read<00:13:52.090> instead<00:13:52.660> of<00:13:52.810> the 00:13:52.920 --> 00:13:52.930 align:start position:0% the plug-in back and read instead of the 00:13:52.930 --> 00:13:57.390 align:start position:0% the plug-in back and read instead of the blue<00:13:53.170> one<00:13:53.460> and<00:13:55.110> the<00:13:56.110> time<00:13:56.410> to<00:13:56.710> subscribe<00:13:56.950> to<00:13:57.370> a 00:13:57.390 --> 00:13:57.400 align:start position:0% blue one and the time to subscribe to a 00:13:57.400 --> 00:14:00.990 align:start position:0% blue one and the time to subscribe to a char<00:13:57.760> should<00:13:58.270> be<00:13:58.360> sure<00:13:58.600> which<00:13:59.290> means<00:13:59.560> a<00:14:00.460> node 00:14:00.990 --> 00:14:01.000 align:start position:0% char should be sure which means a node 00:14:01.000 --> 00:14:03.660 align:start position:0% char should be sure which means a node should<00:14:01.300> be<00:14:01.420> able<00:14:01.660> to<00:14:01.780> find<00:14:02.080> the<00:14:02.470> sharp<00:14:02.890> ears<00:14:03.280> in 00:14:03.660 --> 00:14:03.670 align:start position:0% should be able to find the sharp ears in 00:14:03.670 --> 00:14:08.940 align:start position:0% should be able to find the sharp ears in a<00:14:03.760> short<00:14:04.000> time<00:14:05.490> so<00:14:06.490> the<00:14:06.640> design<00:14:07.770> currently<00:14:08.770> we 00:14:08.940 --> 00:14:08.950 align:start position:0% a short time so the design currently we 00:14:08.950 --> 00:14:12.750 align:start position:0% a short time so the design currently we mapped<00:14:09.280> shards<00:14:10.090> to<00:14:10.390> topics<00:14:10.960> in<00:14:11.230> pops<00:14:11.770> up<00:14:11.950> so 00:14:12.750 --> 00:14:12.760 align:start position:0% mapped shards to topics in pops up so 00:14:12.760 --> 00:14:15.020 align:start position:0% mapped shards to topics in pops up so the<00:14:12.970> concept<00:14:13.450> of<00:14:13.570> the<00:14:13.810> pops<00:14:14.140> out<00:14:14.320> is 00:14:15.020 --> 00:14:15.030 align:start position:0% the concept of the pops out is 00:14:15.030 --> 00:14:18.470 align:start position:0% the concept of the pops out is subscribers<00:14:16.030> subscribe<00:14:16.450> to<00:14:16.690> some<00:14:16.990> topics<00:14:17.920> and 00:14:18.470 --> 00:14:18.480 align:start position:0% subscribers subscribe to some topics and 00:14:18.480 --> 00:14:20.880 align:start position:0% subscribers subscribe to some topics and they<00:14:19.480> should<00:14:19.750> only<00:14:19.930> receive<00:14:20.410> that<00:14:20.620> data 00:14:20.880 --> 00:14:20.890 align:start position:0% they should only receive that data 00:14:20.890 --> 00:14:23.820 align:start position:0% they should only receive that data published<00:14:21.550> to<00:14:21.730> those<00:14:21.970> topics<00:14:22.540> in<00:14:22.810> this<00:14:23.590> way 00:14:23.820 --> 00:14:23.830 align:start position:0% published to those topics in this way 00:14:23.830 --> 00:14:27.660 align:start position:0% published to those topics in this way each<00:14:24.310> have<00:14:24.670> a<00:14:24.700> forms<00:14:25.270> a<00:14:25.480> separate<00:14:26.410> channel<00:14:26.860> so 00:14:27.660 --> 00:14:27.670 align:start position:0% each have a forms a separate channel so 00:14:27.670 --> 00:14:31.520 align:start position:0% each have a forms a separate channel so we<00:14:27.910> can<00:14:27.940> segregate<00:14:28.360> the<00:14:29.250> chars<00:14:30.250> with<00:14:30.640> topics 00:14:31.520 --> 00:14:31.530 align:start position:0% we can segregate the chars with topics 00:14:31.530 --> 00:14:36.480 align:start position:0% we can segregate the chars with topics and<00:14:32.790> about<00:14:33.790> discovery<00:14:34.330> we<00:14:35.050> use<00:14:35.350> puh<00:14:35.590> notes<00:14:35.830> for 00:14:36.480 --> 00:14:36.490 align:start position:0% and about discovery we use puh notes for 00:14:36.490 --> 00:14:39.150 align:start position:0% and about discovery we use puh notes for you<00:14:37.090> notes<00:14:37.330> to<00:14:37.540> join<00:14:37.780> the<00:14:37.990> network<00:14:38.140> and<00:14:38.560> to 00:14:39.150 --> 00:14:39.160 align:start position:0% you notes to join the network and to 00:14:39.160 --> 00:14:43.470 align:start position:0% you notes to join the network and to find<00:14:39.400> the<00:14:39.840> initial<00:14:40.840> peers<00:14:41.500> and<00:14:42.010> we<00:14:42.790> use<00:14:42.970> Kadhim 00:14:43.470 --> 00:14:43.480 align:start position:0% find the initial peers and we use Kadhim 00:14:43.480 --> 00:14:47.370 align:start position:0% find the initial peers and we use Kadhim the<00:14:43.600> Abbott<00:14:43.870> DHT<00:14:44.290> and<00:14:44.470> we<00:14:45.360> for<00:14:46.360> to<00:14:46.750> discover 00:14:47.370 --> 00:14:47.380 align:start position:0% the Abbott DHT and we for to discover 00:14:47.380 --> 00:14:51.720 align:start position:0% the Abbott DHT and we for to discover the<00:14:47.980> sharp<00:14:48.280> ears<00:14:49.080> our<00:14:50.080> approach<00:14:50.770> is<00:14:51.010> we<00:14:51.250> have<00:14:51.700> a 00:14:51.720 --> 00:14:51.730 align:start position:0% the sharp ears our approach is we have a 00:14:51.730 --> 00:14:55.050 align:start position:0% the sharp ears our approach is we have a global<00:14:52.090> topic<00:14:52.780> for<00:14:53.170> notes<00:14:53.650> to<00:14:53.920> broadcast<00:14:54.370> the 00:14:55.050 --> 00:14:55.060 align:start position:0% global topic for notes to broadcast the 00:14:55.060 --> 00:14:57.500 align:start position:0% global topic for notes to broadcast the chars<00:14:55.390> they're<00:14:55.660> currently<00:14:56.050> subscribing<00:14:56.860> so 00:14:57.500 --> 00:14:57.510 align:start position:0% chars they're currently subscribing so 00:14:57.510 --> 00:15:01.410 align:start position:0% chars they're currently subscribing so if<00:14:58.510> a<00:14:58.660> know<00:14:58.870> wants<00:14:59.200> to<00:14:59.550> to<00:15:00.550> find<00:15:00.760> appear<00:15:01.150> in<00:15:01.330> a 00:15:01.410 --> 00:15:01.420 align:start position:0% if a know wants to to find appear in a 00:15:01.420 --> 00:15:02.970 align:start position:0% if a know wants to to find appear in a specific<00:15:01.990> shark 00:15:02.970 --> 00:15:02.980 align:start position:0% specific shark 00:15:02.980 --> 00:15:07.170 align:start position:0% specific shark it<00:15:03.220> has<00:15:03.430> e<00:15:03.670> it<00:15:04.660> can<00:15:04.960> do<00:15:05.350> it<00:15:05.500> through<00:15:06.400> subscribe 00:15:07.170 --> 00:15:07.180 align:start position:0% it has e it can do it through subscribe 00:15:07.180 --> 00:15:10.590 align:start position:0% it has e it can do it through subscribe in<00:15:07.300> the<00:15:07.510> topic<00:15:08.200> and<00:15:09.130> we're<00:15:09.760> still<00:15:10.030> exploring 00:15:10.590 --> 00:15:10.600 align:start position:0% in the topic and we're still exploring 00:15:10.600 --> 00:15:14.580 align:start position:0% in the topic and we're still exploring other<00:15:11.260> options<00:15:11.620> and<00:15:12.780> each<00:15:13.780> node<00:15:13.960> provides<00:15:14.380> the 00:15:14.580 --> 00:15:14.590 align:start position:0% other options and each node provides the 00:15:14.590 --> 00:15:17.220 align:start position:0% other options and each node provides the obviously<00:15:15.010> for<00:15:15.280> other<00:15:15.520> nodes<00:15:15.820> to<00:15:16.060> request<00:15:16.480> for 00:15:17.220 --> 00:15:17.230 align:start position:0% obviously for other nodes to request for 00:15:17.230 --> 00:15:20.610 align:start position:0% obviously for other nodes to request for data<00:15:17.410> so<00:15:18.340> currently<00:15:19.240> we<00:15:19.390> support<00:15:19.570> the<00:15:20.170> request 00:15:20.610 --> 00:15:20.620 align:start position:0% data so currently we support the request 00:15:20.620 --> 00:15:23.850 align:start position:0% data so currently we support the request collation<00:15:21.250> collision<00:15:21.730> is<00:15:21.850> the<00:15:22.290> block<00:15:23.290> in<00:15:23.590> the 00:15:23.850 --> 00:15:23.860 align:start position:0% collation collision is the block in the 00:15:23.860 --> 00:15:28.020 align:start position:0% collation collision is the block in the shark<00:15:24.270> and<00:15:25.770> we're<00:15:26.770> going<00:15:27.040> to<00:15:27.070> change<00:15:27.400> to<00:15:27.790> use 00:15:28.020 --> 00:15:28.030 align:start position:0% shark and we're going to change to use 00:15:28.030 --> 00:15:31.740 align:start position:0% shark and we're going to change to use the<00:15:28.900> epitome<00:15:29.260> demon<00:15:29.590> so<00:15:30.160> what<00:15:30.400> is<00:15:30.580> the<00:15:31.360> pdb 00:15:31.740 --> 00:15:31.750 align:start position:0% the epitome demon so what is the pdb 00:15:31.750 --> 00:15:33.000 align:start position:0% the epitome demon so what is the pdb demon 00:15:33.000 --> 00:15:33.010 align:start position:0% demon 00:15:33.010 --> 00:15:36.140 align:start position:0% demon it<00:15:33.460> is<00:15:33.670> capable<00:15:34.120> of<00:15:34.510> supporting<00:15:35.140> liberty 00:15:36.140 --> 00:15:36.150 align:start position:0% it is capable of supporting liberty 00:15:36.150 --> 00:15:39.930 align:start position:0% it is capable of supporting liberty across<00:15:37.150> languages<00:15:37.900> and<00:15:38.170> you<00:15:39.100> if<00:15:39.460> you<00:15:39.700> want<00:15:39.730> to 00:15:39.930 --> 00:15:39.940 align:start position:0% across languages and you if you want to 00:15:39.940 --> 00:15:41.940 align:start position:0% across languages and you if you want to use<00:15:40.120> it<00:15:40.300> you<00:15:40.450> need<00:15:40.600> to<00:15:40.750> implement<00:15:41.560> the 00:15:41.940 --> 00:15:41.950 align:start position:0% use it you need to implement the 00:15:41.950 --> 00:15:44.940 align:start position:0% use it you need to implement the bindings<00:15:42.390> so<00:15:43.390> as<00:15:43.840> you<00:15:43.990> can<00:15:44.140> see<00:15:44.200> in<00:15:44.440> this<00:15:44.560> graph 00:15:44.940 --> 00:15:44.950 align:start position:0% bindings so as you can see in this graph 00:15:44.950 --> 00:15:48.840 align:start position:0% bindings so as you can see in this graph the<00:15:45.310> left<00:15:45.460> hand<00:15:45.700> side<00:15:45.880> is<00:15:46.030> the<00:15:46.770> B<00:15:47.770> demon<00:15:48.100> and<00:15:48.460> it 00:15:48.840 --> 00:15:48.850 align:start position:0% the left hand side is the B demon and it 00:15:48.850 --> 00:15:51.600 align:start position:0% the left hand side is the B demon and it is<00:15:49.030> a<00:15:49.060> standalone<00:15:49.630> process<00:15:50.290> and<00:15:50.560> in<00:15:51.070> handles 00:15:51.600 --> 00:15:51.610 align:start position:0% is a standalone process and in handles 00:15:51.610 --> 00:15:55.230 align:start position:0% is a standalone process and in handles they<00:15:52.600> to<00:15:52.960> be<00:15:53.110> components<00:15:53.800> and<00:15:54.370> you<00:15:55.060> can 00:15:55.230 --> 00:15:55.240 align:start position:0% they to be components and you can 00:15:55.240 --> 00:15:58.830 align:start position:0% they to be components and you can control<00:15:55.720> the<00:15:56.020> demon<00:15:56.920> through<00:15:57.250> the<00:15:57.840> UNIX 00:15:58.830 --> 00:15:58.840 align:start position:0% control the demon through the UNIX 00:15:58.840 --> 00:16:02.790 align:start position:0% control the demon through the UNIX domain<00:15:59.050> socket<00:16:00.030> and<00:16:01.030> in<00:16:01.720> currently<00:16:02.620> it 00:16:02.790 --> 00:16:02.800 align:start position:0% domain socket and in currently it 00:16:02.800 --> 00:16:06.210 align:start position:0% domain socket and in currently it supports<00:16:03.490> multiple<00:16:04.360> methods<00:16:04.870> so<00:16:05.410> I<00:16:05.740> didn't 00:16:06.210 --> 00:16:06.220 align:start position:0% supports multiple methods so I didn't 00:16:06.220 --> 00:16:09.450 align:start position:0% supports multiple methods so I didn't identify<00:16:06.580> you<00:16:07.270> can<00:16:07.530> get<00:16:08.530> the<00:16:08.650> peer<00:16:08.890> ID<00:16:09.070> from 00:16:09.450 --> 00:16:09.460 align:start position:0% identify you can get the peer ID from 00:16:09.460 --> 00:16:13.020 align:start position:0% identify you can get the peer ID from the<00:16:10.320> demon<00:16:11.320> and<00:16:11.470> you<00:16:12.280> can<00:16:12.430> connect<00:16:12.730> your<00:16:12.820> other 00:16:13.020 --> 00:16:13.030 align:start position:0% the demon and you can connect your other 00:16:13.030 --> 00:16:15.840 align:start position:0% the demon and you can connect your other peers<00:16:13.420> and<00:16:13.750> you<00:16:14.080> can<00:16:14.230> open<00:16:14.470> strings<00:16:15.040> to<00:16:15.700> other 00:16:15.840 --> 00:16:15.850 align:start position:0% peers and you can open strings to other 00:16:15.850 --> 00:16:18.450 align:start position:0% peers and you can open strings to other peers<00:16:16.210> and<00:16:16.420> you<00:16:16.990> can<00:16:17.140> set<00:16:17.470> up<00:16:17.500> you<00:16:18.340> can 00:16:18.450 --> 00:16:18.460 align:start position:0% peers and you can set up you can 00:16:18.460 --> 00:16:20.370 align:start position:0% peers and you can set up you can register<00:16:18.640> a<00:16:18.970> function<00:16:19.540> to<00:16:19.960> handle<00:16:20.260> the 00:16:20.370 --> 00:16:20.380 align:start position:0% register a function to handle the 00:16:20.380 --> 00:16:23.640 align:start position:0% register a function to handle the incoming<00:16:20.740> strings<00:16:21.160> and<00:16:21.510> the<00:16:22.510> DI<00:16:22.660> DHT 00:16:23.640 --> 00:16:23.650 align:start position:0% incoming strings and the DI DHT 00:16:23.650 --> 00:16:27.480 align:start position:0% incoming strings and the DI DHT operations<00:16:24.250> and<00:16:24.690> the<00:16:26.040> hops<00:16:27.040> are<00:16:27.190> still 00:16:27.480 --> 00:16:27.490 align:start position:0% operations and the hops are still 00:16:27.490 --> 00:16:33.210 align:start position:0% operations and the hops are still underway<00:16:28.590> and<00:16:30.360> this<00:16:31.360> graph<00:16:32.350> shows<00:16:32.830> how<00:16:32.860> we 00:16:33.210 --> 00:16:33.220 align:start position:0% underway and this graph shows how we 00:16:33.220 --> 00:16:36.990 align:start position:0% underway and this graph shows how we will<00:16:33.550> change<00:16:33.880> our<00:16:34.060> structure<00:16:34.840> so<00:16:35.790> in<00:16:36.790> this 00:16:36.990 --> 00:16:37.000 align:start position:0% will change our structure so in this 00:16:37.000 --> 00:16:40.020 align:start position:0% will change our structure so in this graph<00:16:37.270> the<00:16:37.780> blue<00:16:38.050> ones<00:16:38.350> means<00:16:38.680> the<00:16:39.580> part<00:16:39.850> we 00:16:40.020 --> 00:16:40.030 align:start position:0% graph the blue ones means the part we 00:16:40.030 --> 00:16:43.080 align:start position:0% graph the blue ones means the part we need<00:16:40.060> to<00:16:40.360> implement<00:16:41.190> and<00:16:42.190> the<00:16:42.460> lemons<00:16:42.820> is 00:16:43.080 --> 00:16:43.090 align:start position:0% need to implement and the lemons is 00:16:43.090 --> 00:16:46.980 align:start position:0% need to implement and the lemons is still<00:16:43.330> the<00:16:43.510> goal<00:16:43.840> and<00:16:44.190> right<00:16:45.190> hand<00:16:45.340> sighs<00:16:45.490> -<00:16:46.150> so 00:16:46.980 --> 00:16:46.990 align:start position:0% still the goal and right hand sighs - so 00:16:46.990 --> 00:16:49.380 align:start position:0% still the goal and right hand sighs - so currently<00:16:47.320> we<00:16:47.920> implement<00:16:48.460> our<00:16:48.520> large<00:16:48.880> Expo 00:16:49.380 --> 00:16:49.390 align:start position:0% currently we implement our large Expo 00:16:49.390 --> 00:16:53.010 align:start position:0% currently we implement our large Expo both<00:16:49.870> in<00:16:50.200> gold<00:16:50.740> and<00:16:50.950> Python<00:16:51.670> and<00:16:51.880> we<00:16:52.150> we<00:16:52.630> handle 00:16:53.010 --> 00:16:53.020 align:start position:0% both in gold and Python and we we handle 00:16:53.020 --> 00:16:56.660 align:start position:0% both in gold and Python and we we handle the<00:16:53.140> communication<00:16:53.410> through<00:16:54.310> G<00:16:54.610> RPC<00:16:54.970> and 00:16:56.660 --> 00:16:56.670 align:start position:0% the communication through G RPC and 00:16:56.670 --> 00:16:59.870 align:start position:0% the communication through G RPC and we're<00:16:57.670> changing<00:16:58.030> to<00:16:58.060> use<00:16:58.360> the<00:16:58.660> p2p<00:16:58.960> daemon<00:16:59.350> and 00:16:59.870 --> 00:16:59.880 align:start position:0% we're changing to use the p2p daemon and 00:16:59.880 --> 00:17:03.390 align:start position:0% we're changing to use the p2p daemon and in<00:17:00.880> this<00:17:01.060> way<00:17:01.300> we<00:17:01.510> can<00:17:01.630> move<00:17:01.870> off<00:17:02.080> our<00:17:02.590> logics 00:17:03.390 --> 00:17:03.400 align:start position:0% in this way we can move off our logics 00:17:03.400 --> 00:17:06.329 align:start position:0% in this way we can move off our logics to<00:17:03.730> Python<00:17:04.150> side<00:17:04.390> and<00:17:04.690> we<00:17:05.380> need<00:17:05.770> to<00:17:05.890> implement 00:17:06.329 --> 00:17:06.339 align:start position:0% to Python side and we need to implement 00:17:06.339 --> 00:17:10.380 align:start position:0% to Python side and we need to implement the<00:17:06.760> Python<00:17:07.390> bindings<00:17:07.680> and<00:17:08.680> after<00:17:09.579> party<00:17:10.060> PHP 00:17:10.380 --> 00:17:10.390 align:start position:0% the Python bindings and after party PHP 00:17:10.390 --> 00:17:14.460 align:start position:0% the Python bindings and after party PHP is<00:17:10.660> ready<00:17:10.930> we<00:17:11.410> can<00:17:11.440> use<00:17:11.740> it<00:17:11.949> directly<00:17:12.160> so<00:17:13.470> all 00:17:14.460 --> 00:17:14.470 align:start position:0% is ready we can use it directly so all 00:17:14.470 --> 00:17:17.310 align:start position:0% is ready we can use it directly so all the<00:17:14.860> logics<00:17:15.190> will<00:17:15.400> be<00:17:15.550> off<00:17:15.790> of<00:17:16.420> them<00:17:16.990> will<00:17:17.140> be 00:17:17.310 --> 00:17:17.320 align:start position:0% the logics will be off of them will be 00:17:17.320 --> 00:17:21.120 align:start position:0% the logics will be off of them will be in<00:17:17.380> a<00:17:17.800> zone<00:17:18.040> sign<00:17:19.079> and<00:17:20.079> about<00:17:20.949> the 00:17:21.120 --> 00:17:21.130 align:start position:0% in a zone sign and about the 00:17:21.130 --> 00:17:22.920 align:start position:0% in a zone sign and about the implementation<00:17:21.430> status<00:17:22.030> so<00:17:22.510> we<00:17:22.540> have 00:17:22.920 --> 00:17:22.930 align:start position:0% implementation status so we have 00:17:22.930 --> 00:17:25.079 align:start position:0% implementation status so we have finished<00:17:23.260> the<00:17:23.530> essential<00:17:24.130> functionalities 00:17:25.079 --> 00:17:25.089 align:start position:0% finished the essential functionalities 00:17:25.089 --> 00:17:29.280 align:start position:0% finished the essential functionalities so<00:17:26.050> including<00:17:27.040> the<00:17:27.339> joining<00:17:27.850> subscribing<00:17:28.660> to 00:17:29.280 --> 00:17:29.290 align:start position:0% so including the joining subscribing to 00:17:29.290 --> 00:17:32.460 align:start position:0% so including the joining subscribing to the<00:17:29.440> chars<00:17:29.680> and<00:17:30.480> broadcast<00:17:31.480> data<00:17:31.660> to<00:17:32.380> the 00:17:32.460 --> 00:17:32.470 align:start position:0% the chars and broadcast data to the 00:17:32.470 --> 00:17:35.460 align:start position:0% the chars and broadcast data to the chars<00:17:32.710> and<00:17:32.890> request<00:17:33.340> messages<00:17:33.910> and<00:17:34.320> we<00:17:35.320> have<00:17:35.440> a 00:17:35.460 --> 00:17:35.470 align:start position:0% chars and request messages and we have a 00:17:35.470 --> 00:17:37.920 align:start position:0% chars and request messages and we have a gobo<00:17:36.010> topic<00:17:36.400> for<00:17:36.580> discovery<00:17:37.120> and<00:17:37.300> condom 00:17:37.920 --> 00:17:37.930 align:start position:0% gobo topic for discovery and condom 00:17:37.930 --> 00:17:41.520 align:start position:0% gobo topic for discovery and condom validations<00:17:38.500> and<00:17:38.940> we<00:17:39.940> have<00:17:40.090> a<00:17:40.120> tracing<00:17:41.050> for 00:17:41.520 --> 00:17:41.530 align:start position:0% validations and we have a tracing for 00:17:41.530 --> 00:17:45.630 align:start position:0% validations and we have a tracing for the<00:17:41.710> testing<00:17:42.070> and<00:17:43.230> we<00:17:44.230> have<00:17:44.440> the<00:17:44.800> findings<00:17:45.460> of 00:17:45.630 --> 00:17:45.640 align:start position:0% the testing and we have the findings of 00:17:45.640 --> 00:17:46.210 align:start position:0% the testing and we have the findings of our<00:17:45.850> call 00:17:46.210 --> 00:17:46.220 align:start position:0% our call 00:17:46.220 --> 00:17:51.250 align:start position:0% our call for<00:17:46.520> python<00:17:47.320> and<00:17:48.320> was<00:17:48.860> in<00:17:49.040> progress<00:17:49.340> so<00:17:50.180> um<00:17:50.690> the 00:17:51.250 --> 00:17:51.260 align:start position:0% for python and was in progress so um the 00:17:51.260 --> 00:17:53.830 align:start position:0% for python and was in progress so um the white<00:17:51.590> bakhtin<00:17:52.100> they're<00:17:52.850> supporting<00:17:53.480> us<00:17:53.540> to 00:17:53.830 --> 00:17:53.840 align:start position:0% white bakhtin they're supporting us to 00:17:53.840 --> 00:17:58.780 align:start position:0% white bakhtin they're supporting us to do<00:17:53.990> the<00:17:54.880> testing<00:17:55.880> with<00:17:57.220> networking<00:17:58.220> they<00:17:58.580> were 00:17:58.780 --> 00:17:58.790 align:start position:0% do the testing with networking they were 00:17:58.790 --> 00:18:02.170 align:start position:0% do the testing with networking they were network<00:17:59.330> emulation<00:17:59.930> and<00:18:00.730> we're<00:18:01.730> still<00:18:01.970> doing 00:18:02.170 --> 00:18:02.180 align:start position:0% network emulation and we're still doing 00:18:02.180 --> 00:18:05.740 align:start position:0% network emulation and we're still doing our<00:18:02.510> own<00:18:03.100> deployment<00:18:04.100> and<00:18:04.190> testing<00:18:04.640> for<00:18:04.820> a 00:18:05.740 --> 00:18:05.750 align:start position:0% our own deployment and testing for a 00:18:05.750 --> 00:18:09.820 align:start position:0% our own deployment and testing for a testing<00:18:06.140> and<00:18:07.870> also<00:18:08.870> we<00:18:09.590> are<00:18:09.620> also 00:18:09.820 --> 00:18:09.830 align:start position:0% testing and also we are also 00:18:09.830 --> 00:18:12.820 align:start position:0% testing and also we are also implementing<00:18:10.640> the<00:18:10.970> python<00:18:11.390> the<00:18:11.540> p2p<00:18:12.350> diamond 00:18:12.820 --> 00:18:12.830 align:start position:0% implementing the python the p2p diamond 00:18:12.830 --> 00:18:16.900 align:start position:0% implementing the python the p2p diamond bindings<00:18:13.630> and<00:18:14.630> we<00:18:15.380> still<00:18:15.680> have<00:18:15.890> to<00:18:16.100> finish<00:18:16.760> the 00:18:16.900 --> 00:18:16.910 align:start position:0% bindings and we still have to finish the 00:18:16.910 --> 00:18:19.870 align:start position:0% bindings and we still have to finish the care<00:18:17.570> management<00:18:17.930> and<00:18:18.440> reputation<00:18:18.880> mackensen 00:18:19.870 --> 00:18:19.880 align:start position:0% care management and reputation mackensen 00:18:19.880 --> 00:18:23.380 align:start position:0% care management and reputation mackensen and<00:18:20.560> do<00:18:21.560> the<00:18:21.740> further<00:18:22.040> optimization<00:18:22.940> for<00:18:23.240> the 00:18:23.380 --> 00:18:23.390 align:start position:0% and do the further optimization for the 00:18:23.390 --> 00:18:27.700 align:start position:0% and do the further optimization for the operating<00:18:24.490> and<00:18:25.490> we<00:18:26.480> currently<00:18:27.290> will<00:18:27.590> have 00:18:27.700 --> 00:18:27.710 align:start position:0% operating and we currently will have 00:18:27.710 --> 00:18:30.640 align:start position:0% operating and we currently will have corporations<00:18:28.430> with<00:18:28.970> original<00:18:29.690> interim<00:18:30.230> p2p 00:18:30.640 --> 00:18:30.650 align:start position:0% corporations with original interim p2p 00:18:30.650 --> 00:18:34.120 align:start position:0% corporations with original interim p2p designers<00:18:31.220> and<00:18:31.810> got<00:18:32.810> a<00:18:32.840> lot<00:18:33.080> of<00:18:33.200> advice<00:18:33.830> from 00:18:34.120 --> 00:18:34.130 align:start position:0% designers and got a lot of advice from 00:18:34.130 --> 00:18:37.090 align:start position:0% designers and got a lot of advice from them<00:18:34.490> and<00:18:34.700> protocol<00:18:35.660> labs<00:18:35.900> they<00:18:36.470> support<00:18:36.890> us 00:18:37.090 --> 00:18:37.100 align:start position:0% them and protocol labs they support us 00:18:37.100 --> 00:18:41.020 align:start position:0% them and protocol labs they support us on<00:18:37.340> the<00:18:37.610> a<00:18:37.820> p2p<00:18:38.390> and<00:18:38.510> pops<00:18:38.810> up<00:18:39.400> white<00:18:40.400> block<00:18:40.610> how 00:18:41.020 --> 00:18:41.030 align:start position:0% on the a p2p and pops up white block how 00:18:41.030 --> 00:18:47.440 align:start position:0% on the a p2p and pops up white block how busted<00:18:41.480> -<00:18:42.610> to<00:18:43.610> do<00:18:43.730> the<00:18:43.760> testing<00:18:44.270> things<00:18:46.450> and 00:18:47.440 --> 00:18:47.450 align:start position:0% busted - to do the testing things and 00:18:47.450 --> 00:18:51.010 align:start position:0% busted - to do the testing things and that's<00:18:48.380> it<00:18:48.680> so<00:18:49.130> I<00:18:49.460> want<00:18:49.730> to<00:18:49.790> give<00:18:50.450> credits<00:18:50.930> to 00:18:51.010 --> 00:18:51.020 align:start position:0% that's it so I want to give credits to 00:18:51.020 --> 00:18:55.720 align:start position:0% that's it so I want to give credits to FedEx<00:18:51.650> in<00:18:52.180> from<00:18:53.350> Paris<00:18:54.350> and<00:18:54.560> Anton<00:18:55.040> from<00:18:55.340> EF 00:18:55.720 --> 00:18:55.730 align:start position:0% FedEx in from Paris and Anton from EF 00:18:55.730 --> 00:18:59.230 align:start position:0% FedEx in from Paris and Anton from EF they<00:18:56.060> give<00:18:56.330> us<00:18:56.480> a<00:18:56.990> lot<00:18:57.290> of<00:18:57.790> instructions<00:18:58.790> and 00:18:59.230 --> 00:18:59.240 align:start position:0% they give us a lot of instructions and 00:18:59.240 --> 00:19:02.290 align:start position:0% they give us a lot of instructions and my<00:18:59.600> a<00:19:00.020> great<00:19:00.530> word<00:19:00.740> from<00:19:01.010> my<00:19:01.160> colleagues<00:19:01.490> thank 00:19:02.290 --> 00:19:02.300 align:start position:0% my a great word from my colleagues thank 00:19:02.300 --> 00:19:08.220 align:start position:0% my a great word from my colleagues thank you 00:19:08.220 --> 00:19:08.230 align:start position:0% 00:19:08.230 --> 00:19:10.320 align:start position:0% um<00:19:08.769> if<00:19:09.220> anybody<00:19:09.609> in<00:19:09.730> the<00:19:09.789> audience<00:19:09.820> has<00:19:10.299> any 00:19:10.320 --> 00:19:10.330 align:start position:0% um if anybody in the audience has any 00:19:10.330 --> 00:19:13.220 align:start position:0% um if anybody in the audience has any questions<00:19:10.899> well<00:19:11.200> there<00:19:11.379> is<00:19:11.470> one<00:19:11.499> right<00:19:11.799> now 00:19:13.220 --> 00:19:13.230 align:start position:0% questions well there is one right now 00:19:13.230 --> 00:19:16.340 align:start position:0% questions well there is one right now was<00:19:14.230> the<00:19:14.440> propagation<00:19:15.039> data<00:19:15.429> you<00:19:15.639> showed<00:19:15.940> and 00:19:16.340 --> 00:19:16.350 align:start position:0% was the propagation data you showed and 00:19:16.350 --> 00:19:18.299 align:start position:0% was the propagation data you showed and ventilation<00:19:17.350> data<00:19:17.470> based<00:19:17.649> on<00:19:17.739> testing<00:19:18.159> on<00:19:18.249> a 00:19:18.299 --> 00:19:18.309 align:start position:0% ventilation data based on testing on a 00:19:18.309 --> 00:19:19.710 align:start position:0% ventilation data based on testing on a local<00:19:18.580> area<00:19:18.639> network<00:19:18.820> or<00:19:19.179> a<00:19:19.239> global<00:19:19.480> network 00:19:19.710 --> 00:19:19.720 align:start position:0% local area network or a global network 00:19:19.720 --> 00:19:23.430 align:start position:0% local area network or a global network and<00:19:20.190> either<00:19:21.190> so<00:19:21.759> it<00:19:21.879> was<00:19:22.119> it<00:19:23.049> was<00:19:23.200> a<00:19:23.230> simulation 00:19:23.430 --> 00:19:23.440 align:start position:0% and either so it was it was a simulation 00:19:23.440 --> 00:19:25.649 align:start position:0% and either so it was it was a simulation it<00:19:23.799> was<00:19:23.950> running<00:19:24.340> all<00:19:24.580> on<00:19:24.700> one<00:19:24.970> machine<00:19:25.119> but<00:19:25.480> we 00:19:25.649 --> 00:19:25.659 align:start position:0% it was running all on one machine but we 00:19:25.659 --> 00:19:27.810 align:start position:0% it was running all on one machine but we simulated<00:19:26.109> the<00:19:26.230> the<00:19:27.009> latency<00:19:27.549> and<00:19:27.580> the 00:19:27.810 --> 00:19:27.820 align:start position:0% simulated the the latency and the 00:19:27.820 --> 00:19:29.759 align:start position:0% simulated the the latency and the bandwidth<00:19:28.239> between<00:19:28.419> these<00:19:28.720> nodes<00:19:28.960> based<00:19:29.590> on 00:19:29.759 --> 00:19:29.769 align:start position:0% bandwidth between these nodes based on 00:19:29.769 --> 00:19:35.849 align:start position:0% bandwidth between these nodes based on global<00:19:30.629> yes<00:19:32.759> my<00:19:33.759> question<00:19:33.940> is<00:19:34.359> I<00:19:34.629> know<00:19:34.859> there's 00:19:35.849 --> 00:19:35.859 align:start position:0% global yes my question is I know there's 00:19:35.859 --> 00:19:38.430 align:start position:0% global yes my question is I know there's the<00:19:36.159> pr2<00:19:36.549> the<00:19:36.909> dev<00:19:37.090> p2p<00:19:37.509> implementation<00:19:38.230> and 00:19:38.430 --> 00:19:38.440 align:start position:0% the pr2 the dev p2p implementation and 00:19:38.440 --> 00:19:42.720 align:start position:0% the pr2 the dev p2p implementation and now<00:19:38.559> there's<00:19:38.830> the<00:19:38.980> 2.0<00:19:39.940> my<00:19:40.629> question<00:19:41.019> is<00:19:41.730> if 00:19:42.720 --> 00:19:42.730 align:start position:0% now there's the 2.0 my question is if 00:19:42.730 --> 00:19:45.570 align:start position:0% now there's the 2.0 my question is if the<00:19:43.179> previous<00:19:43.779> implementation<00:19:44.049> is<00:19:44.739> kind<00:19:45.489> of 00:19:45.570 --> 00:19:45.580 align:start position:0% the previous implementation is kind of 00:19:45.580 --> 00:19:47.399 align:start position:0% the previous implementation is kind of going<00:19:45.820> to<00:19:46.059> everything<00:19:46.779> is<00:19:46.899> going<00:19:46.960> to<00:19:47.289> be 00:19:47.399 --> 00:19:47.409 align:start position:0% going to everything is going to be 00:19:47.409 --> 00:19:49.440 align:start position:0% going to everything is going to be switching<00:19:47.649> to<00:19:48.039> nip<00:19:48.190> it<00:19:48.340> to<00:19:48.460> be<00:19:48.639> or<00:19:48.850> there's 00:19:49.440 --> 00:19:49.450 align:start position:0% switching to nip it to be or there's 00:19:49.450 --> 00:19:53.399 align:start position:0% switching to nip it to be or there's going<00:19:49.659> to<00:19:49.749> be<00:19:49.840> different<00:19:50.230> areas<00:19:50.559> there<00:19:51.299> so<00:19:52.409> in 00:19:53.399 --> 00:19:53.409 align:start position:0% going to be different areas there so in 00:19:53.409 --> 00:19:55.859 align:start position:0% going to be different areas there so in the<00:19:53.679> dev<00:19:53.859> p2p<00:19:54.249> right<00:19:54.429> now<00:19:54.549> there's<00:19:54.789> no<00:19:55.059> lip<00:19:55.359> b2p 00:19:55.859 --> 00:19:55.869 align:start position:0% the dev p2p right now there's no lip b2p 00:19:55.869 --> 00:19:58.139 align:start position:0% the dev p2p right now there's no lip b2p implementation<00:19:56.649> there's<00:19:56.889> CAD<00:19:57.399> Emilia<00:19:57.789> for 00:19:58.139 --> 00:19:58.149 align:start position:0% implementation there's CAD Emilia for 00:19:58.149 --> 00:20:01.049 align:start position:0% implementation there's CAD Emilia for discovery<00:19:58.869> etc<00:19:59.440> etc<00:19:59.619> but<00:20:00.399> in<00:20:00.609> this<00:20:00.759> version 00:20:01.049 --> 00:20:01.059 align:start position:0% discovery etc etc but in this version 00:20:01.059 --> 00:20:02.820 align:start position:0% discovery etc etc but in this version you're<00:20:01.359> showing<00:20:01.659> that<00:20:01.690> lipid<00:20:02.169> 2<00:20:02.350> piece<00:20:02.559> kind 00:20:02.820 --> 00:20:02.830 align:start position:0% you're showing that lipid 2 piece kind 00:20:02.830 --> 00:20:07.409 align:start position:0% you're showing that lipid 2 piece kind of<00:20:03.039> everywhere<00:20:03.639> yes<00:20:04.470> so<00:20:05.470> so<00:20:06.460> our<00:20:06.730> current<00:20:07.149> plan 00:20:07.409 --> 00:20:07.419 align:start position:0% of everywhere yes so so our current plan 00:20:07.419 --> 00:20:09.629 align:start position:0% of everywhere yes so so our current plan is<00:20:07.450> to<00:20:07.720> use<00:20:07.899> just<00:20:08.529> you<00:20:08.739> sleepy<00:20:09.009> dopey<00:20:09.070> and<00:20:09.460> not 00:20:09.629 --> 00:20:09.639 align:start position:0% is to use just you sleepy dopey and not 00:20:09.639 --> 00:20:14.190 align:start position:0% is to use just you sleepy dopey and not use<00:20:09.820> the<00:20:09.970> FPTP<00:20:10.299> for<00:20:10.720> the<00:20:11.759> Serenity<00:20:12.759> stuff<00:20:13.239> you 00:20:14.190 --> 00:20:14.200 align:start position:0% use the FPTP for the Serenity stuff you 00:20:14.200 --> 00:20:16.849 align:start position:0% use the FPTP for the Serenity stuff you going<00:20:14.470> for<00:20:14.649> the<00:20:14.739> go<00:20:14.859> implementation 00:20:16.849 --> 00:20:16.859 align:start position:0% going for the go implementation 00:20:16.859 --> 00:20:21.119 align:start position:0% going for the go implementation currently<00:20:18.330> we<00:20:19.330> have<00:20:19.929> a<00:20:19.960> grant<00:20:20.320> for<00:20:20.559> the<00:20:20.799> Python 00:20:21.119 --> 00:20:21.129 align:start position:0% currently we have a grant for the Python 00:20:21.129 --> 00:20:24.479 align:start position:0% currently we have a grant for the Python API<00:20:21.629> implementation<00:20:22.629> so<00:20:23.109> after<00:20:23.409> it<00:20:23.590> is<00:20:23.739> ready 00:20:24.479 --> 00:20:24.489 align:start position:0% API implementation so after it is ready 00:20:24.489 --> 00:20:28.590 align:start position:0% API implementation so after it is ready because<00:20:25.359> we<00:20:25.690> implement<00:20:26.470> in<00:20:26.710> Python<00:20:27.309> so<00:20:27.639> after 00:20:28.590 --> 00:20:28.600 align:start position:0% because we implement in Python so after 00:20:28.600 --> 00:20:30.210 align:start position:0% because we implement in Python so after it<00:20:28.749> is<00:20:28.869> ready<00:20:29.109> we<00:20:29.289> can<00:20:29.409> change<00:20:29.619> it<00:20:29.739> to<00:20:29.769> that 00:20:30.210 --> 00:20:30.220 align:start position:0% it is ready we can change it to that 00:20:30.220 --> 00:20:32.549 align:start position:0% it is ready we can change it to that so<00:20:30.519> other<00:20:30.730> and<00:20:31.509> this<00:20:31.809> is<00:20:31.929> why<00:20:32.049> you<00:20:32.109> also<00:20:32.320> have 00:20:32.549 --> 00:20:32.559 align:start position:0% so other and this is why you also have 00:20:32.559 --> 00:20:35.669 align:start position:0% so other and this is why you also have the<00:20:32.710> the<00:20:33.009> UNIX<00:20:33.639> the<00:20:34.119> daemon<00:20:34.480> right<00:20:34.690> yeah<00:20:35.109> that 00:20:35.669 --> 00:20:35.679 align:start position:0% the the UNIX the daemon right yeah that 00:20:35.679 --> 00:20:37.739 align:start position:0% the the UNIX the daemon right yeah that email<00:20:35.950> is<00:20:36.039> to<00:20:36.220> stop<00:20:36.580> this<00:20:36.759> problem<00:20:37.059> so<00:20:37.509> you<00:20:37.539> can 00:20:37.739 --> 00:20:37.749 align:start position:0% email is to stop this problem so you can 00:20:37.749 --> 00:20:41.070 align:start position:0% email is to stop this problem so you can commit<00:20:38.730> for<00:20:39.730> different<00:20:40.090> languages<00:20:40.659> they<00:20:40.869> can 00:20:41.070 --> 00:20:41.080 align:start position:0% commit for different languages they can 00:20:41.080 --> 00:20:44.489 align:start position:0% commit for different languages they can use<00:20:41.739> the<00:20:42.009> daemon<00:20:42.340> and<00:20:42.720> without<00:20:43.720> implement 00:20:44.489 --> 00:20:44.499 align:start position:0% use the daemon and without implement 00:20:44.499 --> 00:20:46.680 align:start position:0% use the daemon and without implement without<00:20:45.039> the<00:20:45.399> actual<00:20:45.909> they<00:20:46.179> paid<00:20:46.359> to<00:20:46.450> be<00:20:46.570> is 00:20:46.680 --> 00:20:46.690 align:start position:0% without the actual they paid to be is 00:20:46.690 --> 00:20:50.549 align:start position:0% without the actual they paid to be is implemented<00:20:47.289> thank<00:20:48.009> you<00:20:48.159> thank<00:20:48.789> you<00:20:49.559> are 00:20:50.549 --> 00:20:50.559 align:start position:0% implemented thank you thank you are 00:20:50.559 --> 00:20:51.869 align:start position:0% implemented thank you thank you are there<00:20:50.679> any<00:20:50.799> more<00:20:51.009> questions<00:20:51.519> from<00:20:51.789> the 00:20:51.869 --> 00:20:51.879 align:start position:0% there any more questions from the 00:20:51.879 --> 00:20:56.640 align:start position:0% there any more questions from the audience 00:20:56.640 --> 00:20:56.650 align:start position:0% 00:20:56.650 --> 00:21:01.140 align:start position:0% are<00:20:57.650> there<00:20:57.800> any<00:20:57.890> comments<00:20:58.160> from<00:20:58.430> the<00:20:58.520> audience 00:21:01.140 --> 00:21:01.150 align:start position:0% 00:21:01.150 --> 00:21:03.550 align:start position:0% who<00:21:02.150> they<00:21:02.360> like<00:21:02.540> thank<00:21:02.930> you<00:21:03.050> like<00:21:03.230> you<00:21:03.380> guys 00:21:03.550 --> 00:21:03.560 align:start position:0% who they like thank you like you guys 00:21:03.560 --> 00:21:04.690 align:start position:0% who they like thank you like you guys alright<00:21:04.040> great 00:21:04.690 --> 00:21:04.700 align:start position:0% alright great 00:21:04.700 --> 00:21:08.380 align:start position:0% alright great that's<00:21:05.540> it<00:21:05.750> round<00:21:06.200> of<00:21:06.260> applause<00:21:06.610> thank<00:21:07.610> you 00:21:08.380 --> 00:21:08.390 align:start position:0% that's it round of applause thank you 00:21:08.390 --> 00:21:16.850 align:start position:0% that's it round of applause thank you [Applause] 00:21:16.850 --> 00:21:16.860 align:start position:0% 00:21:16.860 --> 00:21:18.920 align:start position:0% you