WEBVTT Kind: captions Language: en 00:00:18.740 --> 00:00:22.010 align:start position:0% okay<00:00:19.740> hello<00:00:20.220> everyone<00:00:20.580> I<00:00:20.789> hope<00:00:21.660> you're<00:00:21.840> all 00:00:22.010 --> 00:00:22.020 align:start position:0% okay hello everyone I hope you're all 00:00:22.020 --> 00:00:23.540 align:start position:0% okay hello everyone I hope you're all really<00:00:22.230> excited<00:00:22.410> to<00:00:22.860> hear<00:00:23.009> the<00:00:23.130> latest<00:00:23.279> news 00:00:23.540 --> 00:00:23.550 align:start position:0% really excited to hear the latest news 00:00:23.550 --> 00:00:26.900 align:start position:0% really excited to hear the latest news about<00:00:23.700> the<00:00:23.970> light<00:00:24.119> client<00:00:25.520> well<00:00:26.520> the<00:00:26.730> good 00:00:26.900 --> 00:00:26.910 align:start position:0% about the light client well the good 00:00:26.910 --> 00:00:30.019 align:start position:0% about the light client well the good news<00:00:26.970> is<00:00:27.119> that<00:00:27.419> it's<00:00:27.680> already<00:00:28.680> in<00:00:29.160> public<00:00:29.550> beta 00:00:30.019 --> 00:00:30.029 align:start position:0% news is that it's already in public beta 00:00:30.029 --> 00:00:32.720 align:start position:0% news is that it's already in public beta testing<00:00:30.449> stage<00:00:30.720> we<00:00:31.560> are<00:00:31.589> behaving<00:00:32.160> it's<00:00:32.519> being 00:00:32.720 --> 00:00:32.730 align:start position:0% testing stage we are behaving it's being 00:00:32.730 --> 00:00:34.729 align:start position:0% testing stage we are behaving it's being prepared<00:00:33.120> for<00:00:33.300> the<00:00:33.390> official<00:00:33.780> release<00:00:34.050> if<00:00:34.290> you 00:00:34.729 --> 00:00:34.739 align:start position:0% prepared for the official release if you 00:00:34.739 --> 00:00:36.619 align:start position:0% prepared for the official release if you would<00:00:34.830> like<00:00:35.010> to<00:00:35.160> try<00:00:35.370> it<00:00:35.430> I<00:00:35.790> will<00:00:36.390> show<00:00:36.510> the 00:00:36.619 --> 00:00:36.629 align:start position:0% would like to try it I will show the 00:00:36.629 --> 00:00:37.910 align:start position:0% would like to try it I will show the necessary<00:00:37.050> links<00:00:37.290> at<00:00:37.410> the<00:00:37.440> end<00:00:37.559> of<00:00:37.769> my 00:00:37.910 --> 00:00:37.920 align:start position:0% necessary links at the end of my 00:00:37.920 --> 00:00:44.810 align:start position:0% necessary links at the end of my presentation<00:00:42.769> yeah<00:00:43.769> if<00:00:44.010> you<00:00:44.190> haven't<00:00:44.640> tried 00:00:44.810 --> 00:00:44.820 align:start position:0% presentation yeah if you haven't tried 00:00:44.820 --> 00:00:46.729 align:start position:0% presentation yeah if you haven't tried it<00:00:44.970> yet<00:00:45.150> the<00:00:45.690> first<00:00:46.110> thing<00:00:46.320> you<00:00:46.440> will<00:00:46.589> notice 00:00:46.729 --> 00:00:46.739 align:start position:0% it yet the first thing you will notice 00:00:46.739 --> 00:00:51.470 align:start position:0% it yet the first thing you will notice is<00:00:47.160> that<00:00:47.219> it<00:00:48.059> syncs<00:00:48.780> absolutely<00:00:49.260> fast<00:00:50.270> this<00:00:51.270> is 00:00:51.470 --> 00:00:51.480 align:start position:0% is that it syncs absolutely fast this is 00:00:51.480 --> 00:00:52.910 align:start position:0% is that it syncs absolutely fast this is of<00:00:51.690> course<00:00:51.719> mainly<00:00:52.110> because<00:00:52.320> it<00:00:52.620> doesn't<00:00:52.890> have 00:00:52.910 --> 00:00:52.920 align:start position:0% of course mainly because it doesn't have 00:00:52.920 --> 00:00:56.389 align:start position:0% of course mainly because it doesn't have to<00:00:53.250> process<00:00:53.850> state<00:00:54.719> transitions<00:00:55.590> just 00:00:56.389 --> 00:00:56.399 align:start position:0% to process state transitions just 00:00:56.399 --> 00:00:58.880 align:start position:0% to process state transitions just download<00:00:56.940> and<00:00:57.120> Jack<00:00:57.539> headers<00:00:57.989> processing 00:00:58.880 --> 00:00:58.890 align:start position:0% download and Jack headers processing 00:00:58.890 --> 00:01:01.130 align:start position:0% download and Jack headers processing headers<00:00:59.160> is<00:00:59.340> a<00:00:59.489> lot<00:01:00.149> faster<00:01:00.629> than<00:01:00.780> processing 00:01:01.130 --> 00:01:01.140 align:start position:0% headers is a lot faster than processing 00:01:01.140 --> 00:01:03.590 align:start position:0% headers is a lot faster than processing entire<00:01:01.590> blocks<00:01:01.949> our<00:01:02.219> current<00:01:02.910> implementation 00:01:03.590 --> 00:01:03.600 align:start position:0% entire blocks our current implementation 00:01:03.600 --> 00:01:06.260 align:start position:0% entire blocks our current implementation can<00:01:03.780> process<00:01:04.019> up<00:01:04.500> to<00:01:05.009> five<00:01:05.399> to<00:01:05.640> ten<00:01:05.850> thousand 00:01:06.260 --> 00:01:06.270 align:start position:0% can process up to five to ten thousand 00:01:06.270 --> 00:01:08.150 align:start position:0% can process up to five to ten thousand headers<00:01:06.660> per<00:01:06.990> second<00:01:07.380> on<00:01:07.500> a<00:01:07.590> good<00:01:07.920> desktop 00:01:08.150 --> 00:01:08.160 align:start position:0% headers per second on a good desktop 00:01:08.160 --> 00:01:12.370 align:start position:0% headers per second on a good desktop computer<00:01:08.729> to<00:01:09.890> improve<00:01:10.890> sinking<00:01:11.369> even<00:01:11.520> further 00:01:12.370 --> 00:01:12.380 align:start position:0% computer to improve sinking even further 00:01:12.380 --> 00:01:15.260 align:start position:0% computer to improve sinking even further it<00:01:13.380> is<00:01:13.560> possible<00:01:13.740> to<00:01:14.039> start<00:01:14.429> sinking<00:01:14.880> from<00:01:15.060> a 00:01:15.260 --> 00:01:15.270 align:start position:0% it is possible to start sinking from a 00:01:15.270 --> 00:01:18.499 align:start position:0% it is possible to start sinking from a trusted<00:01:15.780> checkpoint<00:01:16.320> which<00:01:17.100> is<00:01:17.509> represented 00:01:18.499 --> 00:01:18.509 align:start position:0% trusted checkpoint which is represented 00:01:18.509 --> 00:01:22.309 align:start position:0% trusted checkpoint which is represented by<00:01:18.539> the<00:01:18.720> root<00:01:19.349> of<00:01:19.530> a<00:01:19.830> mercury<00:01:20.869> containing<00:01:21.869> all 00:01:22.309 --> 00:01:22.319 align:start position:0% by the root of a mercury containing all 00:01:22.319 --> 00:01:24.499 align:start position:0% by the root of a mercury containing all previous<00:01:22.860> block<00:01:23.099> hashes<00:01:23.520> it's<00:01:23.819> called<00:01:24.420> a 00:01:24.499 --> 00:01:24.509 align:start position:0% previous block hashes it's called a 00:01:24.509 --> 00:01:27.770 align:start position:0% previous block hashes it's called a canonical<00:01:25.050> history<00:01:25.670> this<00:01:26.670> structure<00:01:27.270> also 00:01:27.770 --> 00:01:27.780 align:start position:0% canonical history this structure also 00:01:27.780 --> 00:01:33.949 align:start position:0% canonical history this structure also allows<00:01:28.619> to<00:01:31.819> access<00:01:32.819> all<00:01:33.209> the<00:01:33.270> headers<00:01:33.720> that 00:01:33.949 --> 00:01:33.959 align:start position:0% allows to access all the headers that 00:01:33.959 --> 00:01:35.690 align:start position:0% allows to access all the headers that hasn't<00:01:34.470> been<00:01:34.530> downloaded<00:01:35.039> during<00:01:35.310> initial 00:01:35.690 --> 00:01:35.700 align:start position:0% hasn't been downloaded during initial 00:01:35.700 --> 00:01:39.169 align:start position:0% hasn't been downloaded during initial sync<00:01:35.970> which<00:01:36.500> could<00:01:37.500> be<00:01:37.619> useful<00:01:37.830> for<00:01:38.179> searching 00:01:39.169 --> 00:01:39.179 align:start position:0% sync which could be useful for searching 00:01:39.179 --> 00:01:41.719 align:start position:0% sync which could be useful for searching for<00:01:39.569> old<00:01:39.869> logs<00:01:40.229> or<00:01:40.530> accessing<00:01:41.459> all 00:01:41.719 --> 00:01:41.729 align:start position:0% for old logs or accessing all 00:01:41.729 --> 00:01:44.479 align:start position:0% for old logs or accessing all transactions<00:01:42.709> currently<00:01:43.709> there<00:01:43.890> is<00:01:43.920> such<00:01:44.280> a 00:01:44.479 --> 00:01:44.489 align:start position:0% transactions currently there is such a 00:01:44.489 --> 00:01:46.580 align:start position:0% transactions currently there is such a checkpoint<00:01:45.030> hard-coded<00:01:45.660> into<00:01:45.810> into<00:01:46.470> the 00:01:46.580 --> 00:01:46.590 align:start position:0% checkpoint hard-coded into into the 00:01:46.590 --> 00:01:50.600 align:start position:0% checkpoint hard-coded into into the client<00:01:46.950> but<00:01:47.520> in<00:01:47.819> the<00:01:47.940> future<00:01:48.270> if<00:01:48.750> we<00:01:49.560> can<00:01:49.800> make 00:01:50.600 --> 00:01:50.610 align:start position:0% client but in the future if we can make 00:01:50.610 --> 00:01:53.089 align:start position:0% client but in the future if we can make this<00:01:51.479> these<00:01:52.140> checkpoints<00:01:52.410> or<00:01:52.800> some 00:01:53.089 --> 00:01:53.099 align:start position:0% this these checkpoints or some 00:01:53.099 --> 00:01:54.889 align:start position:0% this these checkpoints or some equivalent<00:01:53.280> information<00:01:53.819> a<00:01:54.330> part<00:01:54.599> of<00:01:54.720> the 00:01:54.889 --> 00:01:54.899 align:start position:0% equivalent information a part of the 00:01:54.899 --> 00:01:57.350 align:start position:0% equivalent information a part of the consensus<00:01:55.289> then<00:01:56.069> it<00:01:56.280> will<00:01:56.459> be<00:01:56.640> possible<00:01:56.819> to 00:01:57.350 --> 00:01:57.360 align:start position:0% consensus then it will be possible to 00:01:57.360 --> 00:02:00.229 align:start position:0% consensus then it will be possible to obtain<00:01:57.869> these<00:01:58.649> checkpoints<00:01:59.060> from<00:02:00.060> the 00:02:00.229 --> 00:02:00.239 align:start position:0% obtain these checkpoints from the 00:02:00.239 --> 00:02:02.859 align:start position:0% obtain these checkpoints from the servers<00:02:00.690> in<00:02:00.720> a<00:02:00.959> safe<00:02:01.259> and<00:02:01.500> trust<00:02:01.860> this<00:02:01.979> way<00:02:02.190> in 00:02:02.859 --> 00:02:02.869 align:start position:0% servers in a safe and trust this way in 00:02:02.869 --> 00:02:07.580 align:start position:0% servers in a safe and trust this way in addition<00:02:03.869> to<00:02:04.470> a<00:02:05.509> fast<00:02:06.509> thinking<00:02:06.959> another 00:02:07.580 --> 00:02:07.590 align:start position:0% addition to a fast thinking another 00:02:07.590 --> 00:02:09.380 align:start position:0% addition to a fast thinking another important<00:02:08.129> to<00:02:08.280> feature<00:02:08.520> of<00:02:08.700> the<00:02:08.819> light<00:02:08.970> client 00:02:09.380 --> 00:02:09.390 align:start position:0% important to feature of the light client 00:02:09.390 --> 00:02:12.140 align:start position:0% important to feature of the light client is<00:02:09.539> that<00:02:09.959> it<00:02:10.590> has<00:02:10.800> generally<00:02:11.370> low<00:02:11.640> resource 00:02:12.140 --> 00:02:12.150 align:start position:0% is that it has generally low resource 00:02:12.150 --> 00:02:14.900 align:start position:0% is that it has generally low resource requirements<00:02:12.930> since<00:02:13.860> everything<00:02:14.489> can<00:02:14.879> be 00:02:14.900 --> 00:02:14.910 align:start position:0% requirements since everything can be 00:02:14.910 --> 00:02:17.690 align:start position:0% requirements since everything can be flashed<00:02:15.209> on<00:02:15.420> demand<00:02:15.780> the<00:02:16.410> database<00:02:17.190> basically 00:02:17.690 --> 00:02:17.700 align:start position:0% flashed on demand the database basically 00:02:17.700 --> 00:02:20.390 align:start position:0% flashed on demand the database basically acts<00:02:18.090> like<00:02:18.450> a<00:02:18.480> cash<00:02:19.110> it<00:02:19.620> can<00:02:19.890> be<00:02:20.010> kept<00:02:20.190> really 00:02:20.390 --> 00:02:20.400 align:start position:0% acts like a cash it can be kept really 00:02:20.400 --> 00:02:22.869 align:start position:0% acts like a cash it can be kept really small<00:02:20.730> memory<00:02:21.510> requirements<00:02:22.410> are<00:02:22.530> also 00:02:22.869 --> 00:02:22.879 align:start position:0% small memory requirements are also 00:02:22.879 --> 00:02:25.699 align:start position:0% small memory requirements are also significantly<00:02:23.879> lower<00:02:24.090> than<00:02:24.120> with<00:02:24.900> a<00:02:24.930> good<00:02:25.319> foo 00:02:25.699 --> 00:02:25.709 align:start position:0% significantly lower than with a good foo 00:02:25.709 --> 00:02:27.440 align:start position:0% significantly lower than with a good foo node<00:02:25.920> mainly<00:02:26.579> because<00:02:26.730> we<00:02:27.000> don't<00:02:27.180> have<00:02:27.209> to 00:02:27.440 --> 00:02:27.450 align:start position:0% node mainly because we don't have to 00:02:27.450 --> 00:02:28.320 align:start position:0% node mainly because we don't have to process<00:02:27.659> entire 00:02:28.320 --> 00:02:28.330 align:start position:0% process entire 00:02:28.330 --> 00:02:30.990 align:start position:0% process entire it<00:02:28.480> this<00:02:29.140> aspect<00:02:29.560> of<00:02:30.070> the<00:02:30.220> get<00:02:30.370> implementation 00:02:30.990 --> 00:02:31.000 align:start position:0% it this aspect of the get implementation 00:02:31.000 --> 00:02:34.380 align:start position:0% it this aspect of the get implementation can<00:02:31.180> be<00:02:31.570> improved<00:02:32.350> even<00:02:32.650> further<00:02:32.860> and<00:02:33.730> still 00:02:34.380 --> 00:02:34.390 align:start position:0% can be improved even further and still 00:02:34.390 --> 00:02:36.390 align:start position:0% can be improved even further and still it<00:02:34.420> provides<00:02:35.110> an<00:02:35.230> aqueous<00:02:35.590> interface<00:02:36.100> that<00:02:36.250> is 00:02:36.390 --> 00:02:36.400 align:start position:0% it provides an aqueous interface that is 00:02:36.400 --> 00:02:38.580 align:start position:0% it provides an aqueous interface that is compatible<00:02:36.730> with<00:02:37.030> the<00:02:37.210> existing<00:02:37.960> phone<00:02:38.380> or 00:02:38.580 --> 00:02:38.590 align:start position:0% compatible with the existing phone or 00:02:38.590 --> 00:02:40.640 align:start position:0% compatible with the existing phone or the<00:02:38.680> interface<00:02:39.130> it's<00:02:39.580> not<00:02:39.790> perfect<00:02:40.180> yet<00:02:40.360> but 00:02:40.640 --> 00:02:40.650 align:start position:0% the interface it's not perfect yet but 00:02:40.650 --> 00:02:44.190 align:start position:0% the interface it's not perfect yet but it's<00:02:41.650> it<00:02:42.370> can<00:02:42.640> already<00:02:42.820> work<00:02:43.570> with<00:02:43.900> mist 00:02:44.190 --> 00:02:44.200 align:start position:0% it's it can already work with mist 00:02:44.200 --> 00:02:47.220 align:start position:0% it's it can already work with mist hopefully<00:02:45.130> tomorrow<00:02:45.430> you<00:02:45.790> will<00:02:46.000> also<00:02:46.390> see<00:02:46.630> a 00:02:47.220 --> 00:02:47.230 align:start position:0% hopefully tomorrow you will also see a 00:02:47.230 --> 00:02:50.250 align:start position:0% hopefully tomorrow you will also see a nice<00:02:48.010> missed<00:02:48.550> demo<00:02:48.940> using<00:02:49.180> the<00:02:49.480> lifeline<00:02:49.930> by 00:02:50.250 --> 00:02:50.260 align:start position:0% nice missed demo using the lifeline by 00:02:50.260 --> 00:02:55.770 align:start position:0% nice missed demo using the lifeline by Alex<00:02:53.670> several<00:02:54.670> people<00:02:55.180> have<00:02:55.450> already 00:02:55.770 --> 00:02:55.780 align:start position:0% Alex several people have already 00:02:55.780 --> 00:02:58.170 align:start position:0% Alex several people have already successfully<00:02:56.380> tested<00:02:56.980> in<00:02:57.100> on<00:02:57.250> smaller 00:02:58.170 --> 00:02:58.180 align:start position:0% successfully tested in on smaller 00:02:58.180 --> 00:03:00.870 align:start position:0% successfully tested in on smaller devices<00:02:58.600> to<00:02:58.990> this<00:02:59.440> picture<00:02:59.800> is<00:02:59.920> from<00:03:00.130> Martin 00:03:00.870 --> 00:03:00.880 align:start position:0% devices to this picture is from Martin 00:03:00.880 --> 00:03:05.360 align:start position:0% devices to this picture is from Martin Brooks<00:03:01.300> syncing<00:03:02.050> with<00:03:02.080> an<00:03:02.410> int'l<00:03:02.890> Addison<00:03:03.310> and 00:03:05.360 --> 00:03:05.370 align:start position:0% Brooks syncing with an int'l Addison and 00:03:05.370 --> 00:03:08.960 align:start position:0% Brooks syncing with an int'l Addison and this<00:03:06.370> screenshot<00:03:06.850> is<00:03:07.209> from<00:03:07.450> a<00:03:07.570> Raspberry<00:03:08.290> Pi 00:03:08.960 --> 00:03:08.970 align:start position:0% this screenshot is from a Raspberry Pi 00:03:08.970 --> 00:03:12.090 align:start position:0% this screenshot is from a Raspberry Pi using<00:03:09.970> running<00:03:10.540> mr.<00:03:10.870> using<00:03:11.350> the<00:03:11.470> light<00:03:11.620> client 00:03:12.090 --> 00:03:12.100 align:start position:0% using running mr. using the light client 00:03:12.100 --> 00:03:14.190 align:start position:0% using running mr. using the light client got<00:03:12.580> to<00:03:12.730> see<00:03:12.850> of<00:03:12.940> John<00:03:13.150> Gary's<00:03:13.480> who<00:03:13.750> by<00:03:14.050> the<00:03:14.110> way 00:03:14.190 --> 00:03:14.200 align:start position:0% got to see of John Gary's who by the way 00:03:14.200 --> 00:03:16.500 align:start position:0% got to see of John Gary's who by the way also<00:03:14.590> donated<00:03:14.950> a<00:03:15.040> lie<00:03:15.160> server<00:03:15.459> to<00:03:15.790> help<00:03:16.240> the 00:03:16.500 --> 00:03:16.510 align:start position:0% also donated a lie server to help the 00:03:16.510 --> 00:03:19.620 align:start position:0% also donated a lie server to help the public<00:03:16.810> testing<00:03:17.440> and<00:03:17.620> like<00:03:18.280> other<00:03:18.670> community 00:03:19.620 --> 00:03:19.630 align:start position:0% public testing and like other community 00:03:19.630 --> 00:03:21.030 align:start position:0% public testing and like other community members<00:03:19.660> provided<00:03:20.530> a<00:03:20.560> lot<00:03:20.680> of<00:03:20.830> useful 00:03:21.030 --> 00:03:21.040 align:start position:0% members provided a lot of useful 00:03:21.040 --> 00:03:27.060 align:start position:0% members provided a lot of useful feedback<00:03:21.870> during<00:03:22.870> testing<00:03:25.050> he<00:03:26.050> in<00:03:26.860> addition 00:03:27.060 --> 00:03:27.070 align:start position:0% feedback during testing he in addition 00:03:27.070 --> 00:03:30.330 align:start position:0% feedback during testing he in addition to<00:03:27.490> basic<00:03:27.820> protocol<00:03:28.360> functionality<00:03:29.340> another 00:03:30.330 --> 00:03:30.340 align:start position:0% to basic protocol functionality another 00:03:30.340 --> 00:03:32.550 align:start position:0% to basic protocol functionality another important<00:03:30.880> question<00:03:30.970> is<00:03:31.450> whether<00:03:31.930> all<00:03:32.350> of 00:03:32.550 --> 00:03:32.560 align:start position:0% important question is whether all of 00:03:32.560 --> 00:03:35.070 align:start position:0% important question is whether all of this<00:03:32.739> can<00:03:33.130> work<00:03:33.670> in<00:03:33.970> a<00:03:34.060> large<00:03:34.450> scale<00:03:34.720> with<00:03:34.930> good 00:03:35.070 --> 00:03:35.080 align:start position:0% this can work in a large scale with good 00:03:35.080 --> 00:03:38.729 align:start position:0% this can work in a large scale with good performance<00:03:35.850> the<00:03:36.850> basic<00:03:37.510> client<00:03:37.840> strategy<00:03:38.050> is 00:03:38.729 --> 00:03:38.739 align:start position:0% performance the basic client strategy is 00:03:38.739 --> 00:03:41.610 align:start position:0% performance the basic client strategy is simple<00:03:39.070> it<00:03:39.610> always<00:03:40.120> tries<00:03:40.360> to<00:03:40.390> have<00:03:40.900> a<00:03:40.930> few 00:03:41.610 --> 00:03:41.620 align:start position:0% simple it always tries to have a few 00:03:41.620 --> 00:03:43.979 align:start position:0% simple it always tries to have a few active<00:03:42.100> server<00:03:42.489> connections<00:03:43.180> selected 00:03:43.979 --> 00:03:43.989 align:start position:0% active server connections selected 00:03:43.989 --> 00:03:45.840 align:start position:0% active server connections selected randomly<00:03:44.170> from<00:03:44.650> a<00:03:44.800> suitable<00:03:45.310> pair<00:03:45.519> set 00:03:45.840 --> 00:03:45.850 align:start position:0% randomly from a suitable pair set 00:03:45.850 --> 00:03:49.440 align:start position:0% randomly from a suitable pair set whenever<00:03:46.450> one<00:03:47.200> of<00:03:47.230> them<00:03:47.530> seems<00:03:48.340> slow<00:03:49.239> or 00:03:49.440 --> 00:03:49.450 align:start position:0% whenever one of them seems slow or 00:03:49.450 --> 00:03:51.630 align:start position:0% whenever one of them seems slow or unresponsive<00:03:49.810> it<00:03:50.440> drops<00:03:50.680> it<00:03:50.860> and<00:03:51.070> looks<00:03:51.489> for 00:03:51.630 --> 00:03:51.640 align:start position:0% unresponsive it drops it and looks for 00:03:51.640 --> 00:03:55.110 align:start position:0% unresponsive it drops it and looks for another<00:03:51.850> one<00:03:52.260> servers<00:03:53.260> they<00:03:53.500> can<00:03:53.970> take<00:03:54.970> care 00:03:55.110 --> 00:03:55.120 align:start position:0% another one servers they can take care 00:03:55.120 --> 00:04:00.270 align:start position:0% another one servers they can take care of<00:03:55.180> themselves<00:03:55.800> by<00:03:58.140> limiting<00:03:59.140> the<00:03:59.280> bandwidth 00:04:00.270 --> 00:04:00.280 align:start position:0% of themselves by limiting the bandwidth 00:04:00.280 --> 00:04:05.910 align:start position:0% of themselves by limiting the bandwidth spent<00:04:00.900> benefit<00:04:01.900> of<00:04:02.080> clients<00:04:02.769> and<00:04:04.920> dropping 00:04:05.910 --> 00:04:05.920 align:start position:0% spent benefit of clients and dropping 00:04:05.920 --> 00:04:11.520 align:start position:0% spent benefit of clients and dropping also<00:04:06.130> dropping<00:04:06.489> them<00:04:06.700> if<00:04:06.820> necessary<00:04:09.750> mmm<00:04:10.750> they 00:04:11.520 --> 00:04:11.530 align:start position:0% also dropping them if necessary mmm they 00:04:11.530 --> 00:04:13.770 align:start position:0% also dropping them if necessary mmm they so<00:04:12.070> they<00:04:12.400> limit<00:04:12.910> the<00:04:13.000> time<00:04:13.180> and<00:04:13.360> resources 00:04:13.770 --> 00:04:13.780 align:start position:0% so they limit the time and resources 00:04:13.780 --> 00:04:17.090 align:start position:0% so they limit the time and resources spent<00:04:14.019> on<00:04:14.200> on<00:04:14.470> on<00:04:14.739> serving<00:04:15.340> serving<00:04:15.610> clients 00:04:17.090 --> 00:04:17.100 align:start position:0% spent on on on serving serving clients 00:04:17.100 --> 00:04:20.610 align:start position:0% spent on on on serving serving clients for<00:04:18.100> limiting<00:04:18.700> client<00:04:19.299> bandwidth<00:04:20.169> oh<00:04:20.320> we 00:04:20.610 --> 00:04:20.620 align:start position:0% for limiting client bandwidth oh we 00:04:20.620 --> 00:04:23.219 align:start position:0% for limiting client bandwidth oh we needed<00:04:20.979> some<00:04:21.570> smarter<00:04:22.570> mechanism<00:04:23.050> than 00:04:23.219 --> 00:04:23.229 align:start position:0% needed some smarter mechanism than 00:04:23.229 --> 00:04:26.430 align:start position:0% needed some smarter mechanism than simply<00:04:23.590> delaying<00:04:24.330> request<00:04:25.330> replies<00:04:25.660> because 00:04:26.430 --> 00:04:26.440 align:start position:0% simply delaying request replies because 00:04:26.440 --> 00:04:31.530 align:start position:0% simply delaying request replies because that<00:04:26.620> would<00:04:29.130> ruin<00:04:30.130> the<00:04:30.430> user<00:04:30.700> experience<00:04:31.390> of 00:04:31.530 --> 00:04:31.540 align:start position:0% that would ruin the user experience of 00:04:31.540 --> 00:04:34.020 align:start position:0% that would ruin the user experience of the<00:04:31.690> client<00:04:32.080> which<00:04:32.410> depends<00:04:33.310> heavily<00:04:33.400> on<00:04:33.669> so 00:04:34.020 --> 00:04:34.030 align:start position:0% the client which depends heavily on so 00:04:34.030 --> 00:04:36.840 align:start position:0% the client which depends heavily on so it<00:04:34.330> quick<00:04:34.600> survey<00:04:34.840> responses<00:04:35.500> this<00:04:36.040> is<00:04:36.220> why<00:04:36.400> we 00:04:36.840 --> 00:04:36.850 align:start position:0% it quick survey responses this is why we 00:04:36.850 --> 00:04:38.909 align:start position:0% it quick survey responses this is why we created<00:04:37.000> client<00:04:37.750> side<00:04:37.930> for<00:04:38.169> control<00:04:38.620> which<00:04:38.800> is 00:04:38.909 --> 00:04:38.919 align:start position:0% created client side for control which is 00:04:38.919 --> 00:04:40.300 align:start position:0% created client side for control which is a<00:04:38.950> simple<00:04:39.370> feedback<00:04:39.490> mechanism 00:04:40.300 --> 00:04:40.310 align:start position:0% a simple feedback mechanism 00:04:40.310 --> 00:04:43.120 align:start position:0% a simple feedback mechanism Thank<00:04:40.790> that<00:04:41.300> can<00:04:41.510> tell<00:04:41.930> clients<00:04:42.350> when<00:04:43.100> they 00:04:43.120 --> 00:04:43.130 align:start position:0% Thank that can tell clients when they 00:04:43.130 --> 00:04:47.170 align:start position:0% Thank that can tell clients when they can<00:04:43.820> send<00:04:44.330> the<00:04:44.590> next<00:04:45.590> request<00:04:46.220> so<00:04:46.820> that<00:04:47.030> the 00:04:47.170 --> 00:04:47.180 align:start position:0% can send the next request so that the 00:04:47.180 --> 00:04:49.210 align:start position:0% can send the next request so that the client<00:04:47.630> can<00:04:47.690> better<00:04:48.140> distribute<00:04:48.620> their 00:04:49.210 --> 00:04:49.220 align:start position:0% client can better distribute their 00:04:49.220 --> 00:04:50.980 align:start position:0% client can better distribute their requests<00:04:49.700> among<00:04:49.970> the<00:04:50.240> few<00:04:50.600> server 00:04:50.980 --> 00:04:50.990 align:start position:0% requests among the few server 00:04:50.990 --> 00:04:54.640 align:start position:0% requests among the few server connections<00:04:51.560> they<00:04:51.770> have<00:04:52.330> if<00:04:53.330> they<00:04:53.810> send<00:04:54.530> a 00:04:54.640 --> 00:04:54.650 align:start position:0% connections they have if they send a 00:04:54.650 --> 00:04:56.470 align:start position:0% connections they have if they send a crust<00:04:55.010> too<00:04:55.160> early<00:04:55.460> they<00:04:55.700> would<00:04:56.120> get<00:04:56.300> the 00:04:56.470 --> 00:04:56.480 align:start position:0% crust too early they would get the 00:04:56.480 --> 00:04:58.600 align:start position:0% crust too early they would get the immediately<00:04:57.080> disconnected<00:04:57.740> they<00:04:58.310> shouldn't 00:04:58.600 --> 00:04:58.610 align:start position:0% immediately disconnected they shouldn't 00:04:58.610 --> 00:05:01.150 align:start position:0% immediately disconnected they shouldn't do<00:04:58.760> that<00:04:58.940> but<00:04:59.480> these<00:05:00.170> strict<00:05:00.530> rules<00:05:00.740> have<00:05:01.040> the 00:05:01.150 --> 00:05:01.160 align:start position:0% do that but these strict rules have the 00:05:01.160 --> 00:05:04.300 align:start position:0% do that but these strict rules have the advantage<00:05:01.640> that<00:05:02.260> requests<00:05:03.260> never<00:05:03.590> get<00:05:03.890> queued 00:05:04.300 --> 00:05:04.310 align:start position:0% advantage that requests never get queued 00:05:04.310 --> 00:05:06.520 align:start position:0% advantage that requests never get queued up<00:05:04.400> on<00:05:04.550> the<00:05:04.640> server<00:05:04.880> side<00:05:05.030> and<00:05:05.630> therefore<00:05:06.410> they 00:05:06.520 --> 00:05:06.530 align:start position:0% up on the server side and therefore they 00:05:06.530 --> 00:05:11.920 align:start position:0% up on the server side and therefore they can<00:05:06.740> be<00:05:07.900> answered<00:05:08.900> immediately<00:05:10.930> this 00:05:11.920 --> 00:05:11.930 align:start position:0% can be answered immediately this 00:05:11.930 --> 00:05:14.500 align:start position:0% can be answered immediately this mechanism<00:05:12.380> can<00:05:12.800> ensure<00:05:13.340> a<00:05:13.580> good<00:05:13.730> distribution 00:05:14.500 --> 00:05:14.510 align:start position:0% mechanism can ensure a good distribution 00:05:14.510 --> 00:05:17.380 align:start position:0% mechanism can ensure a good distribution of<00:05:14.930> server<00:05:15.200> load<00:05:15.940> throughout<00:05:16.940> the<00:05:17.120> entire 00:05:17.380 --> 00:05:17.390 align:start position:0% of server load throughout the entire 00:05:17.390 --> 00:05:19.630 align:start position:0% of server load throughout the entire network<00:05:17.900> but<00:05:18.260> we<00:05:18.500> also<00:05:18.800> need<00:05:19.070> some<00:05:19.280> market 00:05:19.630 --> 00:05:19.640 align:start position:0% network but we also need some market 00:05:19.640 --> 00:05:23.470 align:start position:0% network but we also need some market forces<00:05:19.940> to<00:05:21.160> incentivize<00:05:22.160> the<00:05:22.430> running<00:05:23.360> of 00:05:23.470 --> 00:05:23.480 align:start position:0% forces to incentivize the running of 00:05:23.480 --> 00:05:27.400 align:start position:0% forces to incentivize the running of good<00:05:23.840> servers<00:05:24.550> in<00:05:25.550> theory<00:05:26.390> micropayment<00:05:26.990> is 00:05:27.400 --> 00:05:27.410 align:start position:0% good servers in theory micropayment is 00:05:27.410 --> 00:05:32.200 align:start position:0% good servers in theory micropayment is the<00:05:27.950> ideal<00:05:28.460> way<00:05:28.760> to<00:05:30.070> incentivize<00:05:31.210> high 00:05:32.200 --> 00:05:32.210 align:start position:0% the ideal way to incentivize high 00:05:32.210 --> 00:05:34.450 align:start position:0% the ideal way to incentivize high quality<00:05:32.810> service<00:05:33.350> and<00:05:33.380> responsible<00:05:34.250> use<00:05:34.310> of 00:05:34.450 --> 00:05:34.460 align:start position:0% quality service and responsible use of 00:05:34.460 --> 00:05:39.610 align:start position:0% quality service and responsible use of resources<00:05:35.380> but<00:05:36.970> on<00:05:37.970> the<00:05:38.090> other<00:05:38.120> hand<00:05:38.330> which<00:05:39.170> we 00:05:39.610 --> 00:05:39.620 align:start position:0% resources but on the other hand which we 00:05:39.620 --> 00:05:41.260 align:start position:0% resources but on the other hand which we should<00:05:39.770> also<00:05:39.920> take<00:05:40.130> into<00:05:40.280> consideration<00:05:41.120> that 00:05:41.260 --> 00:05:41.270 align:start position:0% should also take into consideration that 00:05:41.270 --> 00:05:44.500 align:start position:0% should also take into consideration that the<00:05:41.720> requiring<00:05:42.230> payment<00:05:43.130> for<00:05:43.550> all<00:05:43.580> Elias 00:05:44.500 --> 00:05:44.510 align:start position:0% the requiring payment for all Elias 00:05:44.510 --> 00:05:46.390 align:start position:0% the requiring payment for all Elias requests<00:05:45.020> would<00:05:45.170> seriously<00:05:45.560> hinder<00:05:46.190> the 00:05:46.390 --> 00:05:46.400 align:start position:0% requests would seriously hinder the 00:05:46.400 --> 00:05:48.490 align:start position:0% requests would seriously hinder the adoption<00:05:46.970> of<00:05:47.030> the<00:05:47.180> protocol<00:05:47.690> and<00:05:47.960> also<00:05:48.470> a 00:05:48.490 --> 00:05:48.500 align:start position:0% adoption of the protocol and also a 00:05:48.500 --> 00:05:50.170 align:start position:0% adoption of the protocol and also a limit<00:05:48.830> its<00:05:48.950> usefulness<00:05:49.400> you<00:05:49.730> couldn't<00:05:50.060> even 00:05:50.170 --> 00:05:50.180 align:start position:0% limit its usefulness you couldn't even 00:05:50.180 --> 00:05:52.150 align:start position:0% limit its usefulness you couldn't even sync<00:05:50.720> up<00:05:50.840> to<00:05:51.020> make<00:05:51.170> your<00:05:51.320> first<00:05:51.500> payment<00:05:51.650> using 00:05:52.150 --> 00:05:52.160 align:start position:0% sync up to make your first payment using 00:05:52.160 --> 00:05:54.820 align:start position:0% sync up to make your first payment using a<00:05:52.400> lifeline<00:05:52.790> and<00:05:52.940> then<00:05:53.150> so<00:05:53.870> another<00:05:54.260> important 00:05:54.820 --> 00:05:54.830 align:start position:0% a lifeline and then so another important 00:05:54.830 --> 00:05:57.870 align:start position:0% a lifeline and then so another important question<00:05:54.950> is<00:05:55.310> whether<00:05:55.520> it<00:05:55.940> is<00:05:56.150> possible<00:05:56.540> to 00:05:57.870 --> 00:05:57.880 align:start position:0% question is whether it is possible to 00:05:57.880 --> 00:06:01.900 align:start position:0% question is whether it is possible to create<00:05:58.880> a<00:05:59.300> an<00:05:59.950> ecosystem<00:06:00.950> we're<00:06:01.280> both<00:06:01.550> free 00:06:01.900 --> 00:06:01.910 align:start position:0% create a an ecosystem we're both free 00:06:01.910 --> 00:06:04.900 align:start position:0% create a an ecosystem we're both free and<00:06:01.940> paid<00:06:02.210> services<00:06:02.900> have<00:06:03.140> their<00:06:03.700> place<00:06:04.700> and 00:06:04.900 --> 00:06:04.910 align:start position:0% and paid services have their place and 00:06:04.910 --> 00:06:07.300 align:start position:0% and paid services have their place and purpose<00:06:05.500> fortunately<00:06:06.500> I<00:06:06.530> believe<00:06:06.890> the<00:06:07.010> answer 00:06:07.300 --> 00:06:07.310 align:start position:0% purpose fortunately I believe the answer 00:06:07.310 --> 00:06:11.380 align:start position:0% purpose fortunately I believe the answer is<00:06:07.340> yes<00:06:07.730> with<00:06:08.630> a<00:06:08.660> service<00:06:09.200> like<00:06:09.380> this<00:06:10.390> demand 00:06:11.380 --> 00:06:11.390 align:start position:0% is yes with a service like this demand 00:06:11.390 --> 00:06:14.860 align:start position:0% is yes with a service like this demand changes<00:06:11.810> very<00:06:11.990> rapidly<00:06:12.140> while<00:06:13.300> the<00:06:14.300> available 00:06:14.860 --> 00:06:14.870 align:start position:0% changes very rapidly while the available 00:06:14.870 --> 00:06:17.440 align:start position:0% changes very rapidly while the available server<00:06:15.080> capacity<00:06:15.550> is<00:06:16.550> a<00:06:16.970> change<00:06:17.300> is 00:06:17.440 --> 00:06:17.450 align:start position:0% server capacity is a change is 00:06:17.450 --> 00:06:19.390 align:start position:0% server capacity is a change is relatively<00:06:17.900> slowly<00:06:18.260> so<00:06:18.920> if<00:06:19.070> you<00:06:19.160> want<00:06:19.340> to 00:06:19.390 --> 00:06:19.400 align:start position:0% relatively slowly so if you want to 00:06:19.400 --> 00:06:21.400 align:start position:0% relatively slowly so if you want to provide<00:06:19.820> high<00:06:20.030> quality<00:06:20.060> service<00:06:20.810> you<00:06:21.170> have<00:06:21.200> to 00:06:21.400 --> 00:06:21.410 align:start position:0% provide high quality service you have to 00:06:21.410 --> 00:06:23.800 align:start position:0% provide high quality service you have to have<00:06:21.530> a<00:06:21.560> lot<00:06:22.130> of<00:06:22.160> reserve<00:06:22.580> capacity<00:06:22.790> and<00:06:23.360> you 00:06:23.800 --> 00:06:23.810 align:start position:0% have a lot of reserve capacity and you 00:06:23.810 --> 00:06:28.000 align:start position:0% have a lot of reserve capacity and you easily<00:06:24.320> get<00:06:24.470> a<00:06:24.500> low<00:06:24.920> utilization<00:06:25.190> ratio<00:06:27.010> which 00:06:28.000 --> 00:06:28.010 align:start position:0% easily get a low utilization ratio which 00:06:28.010 --> 00:06:30.130 align:start position:0% easily get a low utilization ratio which means<00:06:28.220> of<00:06:28.340> course<00:06:28.400> that<00:06:28.580> the<00:06:28.910> servers<00:06:29.600> can<00:06:29.780> is 00:06:30.130 --> 00:06:30.140 align:start position:0% means of course that the servers can is 00:06:30.140 --> 00:06:32.500 align:start position:0% means of course that the servers can is sad<00:06:30.770> the<00:06:30.980> remaining<00:06:31.490> capacity<00:06:31.670> at<00:06:32.180> a<00:06:32.300> lower 00:06:32.500 --> 00:06:32.510 align:start position:0% sad the remaining capacity at a lower 00:06:32.510 --> 00:06:35.830 align:start position:0% sad the remaining capacity at a lower priority<00:06:32.810> and<00:06:33.470> a<00:06:34.010> lower<00:06:34.280> price<00:06:34.670> so<00:06:35.240> basically 00:06:35.830 --> 00:06:35.840 align:start position:0% priority and a lower price so basically 00:06:35.840 --> 00:06:38.290 align:start position:0% priority and a lower price so basically our<00:06:35.960> model<00:06:36.350> is<00:06:36.500> that<00:06:36.820> clients<00:06:37.820> are<00:06:37.970> buying 00:06:38.290 --> 00:06:38.300 align:start position:0% our model is that clients are buying 00:06:38.300 --> 00:06:42.550 align:start position:0% our model is that clients are buying priority<00:06:39.080> from<00:06:39.440> the<00:06:39.650> servers<00:06:40.100> and<00:06:41.080> on<00:06:42.080> the 00:06:42.550 --> 00:06:42.560 align:start position:0% priority from the servers and on the 00:06:42.560 --> 00:06:44.830 align:start position:0% priority from the servers and on the lowest<00:06:43.400> possible<00:06:43.550> priority<00:06:43.970> level<00:06:44.570> if<00:06:44.690> the 00:06:44.830 --> 00:06:44.840 align:start position:0% lowest possible priority level if the 00:06:44.840 --> 00:06:47.170 align:start position:0% lowest possible priority level if the service<00:06:45.260> still<00:06:45.680> have<00:06:45.890> some<00:06:46.130> free<00:06:46.430> capacity 00:06:47.170 --> 00:06:47.180 align:start position:0% service still have some free capacity 00:06:47.180 --> 00:06:49.150 align:start position:0% service still have some free capacity they<00:06:47.540> can<00:06:47.780> basically<00:06:48.110> give<00:06:48.590> it<00:06:48.680> away<00:06:48.770> for<00:06:48.920> free 00:06:49.150 --> 00:06:49.160 align:start position:0% they can basically give it away for free 00:06:49.160 --> 00:06:50.980 align:start position:0% they can basically give it away for free which<00:06:49.940> of<00:06:50.090> course<00:06:50.120> still<00:06:50.540> wouldn't<00:06:50.840> insure 00:06:50.980 --> 00:06:50.990 align:start position:0% which of course still wouldn't insure 00:06:50.990 --> 00:06:53.679 align:start position:0% which of course still wouldn't insure that<00:06:51.200> they<00:06:51.500> actually<00:06:51.710> do<00:06:52.130> this<00:06:52.310> but<00:06:53.000> we 00:06:53.679 --> 00:06:53.689 align:start position:0% that they actually do this but we 00:06:53.689 --> 00:06:55.659 align:start position:0% that they actually do this but we angry<00:06:53.989> at<00:06:54.080> the<00:06:54.229> service<00:06:54.469> model<00:06:54.949> and<00:06:55.129> they<00:06:55.489> will 00:06:55.659 --> 00:06:55.669 align:start position:0% angry at the service model and they will 00:06:55.669 --> 00:06:57.719 align:start position:0% angry at the service model and they will have<00:06:55.849> a<00:06:55.879> natural<00:06:56.419> incentive<00:06:56.959> to<00:06:57.080> do<00:06:57.229> so 00:06:57.719 --> 00:06:57.729 align:start position:0% have a natural incentive to do so 00:06:57.729 --> 00:07:00.539 align:start position:0% have a natural incentive to do so pre-service<00:06:58.729> is<00:06:59.119> a<00:06:59.149> good<00:06:59.569> indicator<00:07:00.049> of 00:07:00.539 --> 00:07:00.549 align:start position:0% pre-service is a good indicator of 00:07:00.549 --> 00:07:03.999 align:start position:0% pre-service is a good indicator of reserve<00:07:01.549> capacities<00:07:02.149> which<00:07:02.809> are<00:07:03.529> necessary 00:07:03.999 --> 00:07:04.009 align:start position:0% reserve capacities which are necessary 00:07:04.009 --> 00:07:06.519 align:start position:0% reserve capacities which are necessary for<00:07:04.489> providing<00:07:05.329> a<00:07:05.629> high<00:07:05.779> quality<00:07:05.839> service 00:07:06.519 --> 00:07:06.529 align:start position:0% for providing a high quality service 00:07:06.529 --> 00:07:08.109 align:start position:0% for providing a high quality service that<00:07:06.709> is<00:07:06.829> actually<00:07:07.189> it<00:07:07.279> is<00:07:07.519> actually<00:07:07.729> worth 00:07:08.109 --> 00:07:08.119 align:start position:0% that is actually it is actually worth 00:07:08.119 --> 00:07:11.859 align:start position:0% that is actually it is actually worth paying<00:07:08.419> for<00:07:08.539> so<00:07:09.169> in<00:07:09.439> our<00:07:09.619> model<00:07:10.869> pre-service 00:07:11.859 --> 00:07:11.869 align:start position:0% paying for so in our model pre-service 00:07:11.869 --> 00:07:14.850 align:start position:0% paying for so in our model pre-service can<00:07:12.259> act<00:07:12.529> as<00:07:12.769> an<00:07:12.979> as<00:07:13.399> an<00:07:13.429> advertisement<00:07:14.419> and 00:07:14.850 --> 00:07:14.860 align:start position:0% can act as an as an advertisement and 00:07:14.860 --> 00:07:19.600 align:start position:0% can act as an as an advertisement and also<00:07:15.860> as<00:07:16.579> I<00:07:16.959> protection<00:07:17.959> against<00:07:18.769> the<00:07:18.919> scam 00:07:19.600 --> 00:07:19.610 align:start position:0% also as I protection against the scam 00:07:19.610 --> 00:07:23.499 align:start position:0% also as I protection against the scam for<00:07:19.939> clients<00:07:20.659> so<00:07:21.169> so<00:07:21.739> the<00:07:22.059> it<00:07:23.059> can<00:07:23.360> protect 00:07:23.499 --> 00:07:23.509 align:start position:0% for clients so so the it can protect 00:07:23.509 --> 00:07:27.159 align:start position:0% for clients so so the it can protect them<00:07:23.779> from<00:07:24.019> for<00:07:24.499> from<00:07:25.489> paying<00:07:25.819> for<00:07:26.449> and<00:07:26.749> then 00:07:27.159 --> 00:07:27.169 align:start position:0% them from for from paying for and then 00:07:27.169 --> 00:07:30.669 align:start position:0% them from for from paying for and then getting<00:07:27.409> those<00:07:27.879> service<00:07:28.879> in<00:07:29.029> return<00:07:29.409> so<00:07:30.409> the 00:07:30.669 --> 00:07:30.679 align:start position:0% getting those service in return so the 00:07:30.679 --> 00:07:32.679 align:start position:0% getting those service in return so the basic<00:07:31.189> client<00:07:31.459> strategy<00:07:31.639> should<00:07:31.969> be<00:07:32.119> that 00:07:32.679 --> 00:07:32.689 align:start position:0% basic client strategy should be that 00:07:32.689 --> 00:07:34.059 align:start position:0% basic client strategy should be that even<00:07:33.019> if<00:07:33.139> you<00:07:33.259> are<00:07:33.409> willing<00:07:33.559> to<00:07:33.769> pay<00:07:33.889> for 00:07:34.059 --> 00:07:34.069 align:start position:0% even if you are willing to pay for 00:07:34.069 --> 00:07:37.419 align:start position:0% even if you are willing to pay for services<00:07:34.759> if<00:07:35.419> if<00:07:35.959> you<00:07:36.139> find<00:07:36.589> a<00:07:36.800> new<00:07:36.979> server 00:07:37.419 --> 00:07:37.429 align:start position:0% services if if you find a new server 00:07:37.429 --> 00:07:39.189 align:start position:0% services if if you find a new server through<00:07:37.579> peer<00:07:37.819> discovery<00:07:38.300> first<00:07:38.629> you<00:07:38.839> always 00:07:39.189 --> 00:07:39.199 align:start position:0% through peer discovery first you always 00:07:39.199 --> 00:07:41.409 align:start position:0% through peer discovery first you always evaluate<00:07:39.769> it<00:07:39.919> for<00:07:40.099> free<00:07:40.399> collectors<00:07:41.149> and 00:07:41.409 --> 00:07:41.419 align:start position:0% evaluate it for free collectors and 00:07:41.419 --> 00:07:44.309 align:start position:0% evaluate it for free collectors and statistics<00:07:42.019> about<00:07:42.610> availability<00:07:43.610> and 00:07:44.309 --> 00:07:44.319 align:start position:0% statistics about availability and 00:07:44.319 --> 00:07:47.679 align:start position:0% statistics about availability and average<00:07:45.319> delays<00:07:46.129> and<00:07:46.429> then<00:07:47.389> if<00:07:47.569> the 00:07:47.679 --> 00:07:47.689 align:start position:0% average delays and then if the 00:07:47.689 --> 00:07:49.869 align:start position:0% average delays and then if the statistics<00:07:48.229> I'll<00:07:48.409> acceptable<00:07:49.189> then<00:07:49.579> you<00:07:49.699> can 00:07:49.869 --> 00:07:49.879 align:start position:0% statistics I'll acceptable then you can 00:07:49.879 --> 00:07:54.129 align:start position:0% statistics I'll acceptable then you can start<00:07:50.089> paying<00:07:50.389> for<00:07:50.479> it<00:07:51.549> and<00:07:52.549> I<00:07:52.669> wanted<00:07:53.089> to<00:07:53.149> talk 00:07:54.129 --> 00:07:54.139 align:start position:0% start paying for it and I wanted to talk 00:07:54.139 --> 00:07:56.709 align:start position:0% start paying for it and I wanted to talk about<00:07:54.169> the<00:07:54.829> new<00:07:55.129> discovery<00:07:56.089> protocol<00:07:56.509> we're 00:07:56.709 --> 00:07:56.719 align:start position:0% about the new discovery protocol we're 00:07:56.719 --> 00:07:58.809 align:start position:0% about the new discovery protocol we're working<00:07:57.139> on<00:07:57.319> unfortunately<00:07:58.189> there's<00:07:58.399> no<00:07:58.579> time 00:07:58.809 --> 00:07:58.819 align:start position:0% working on unfortunately there's no time 00:07:58.819 --> 00:08:02.559 align:start position:0% working on unfortunately there's no time for<00:07:58.849> many<00:07:59.449> details<00:07:59.899> it's<00:08:00.289> a<00:08:00.979> new<00:08:01.909> feature<00:08:02.209> is 00:08:02.559 --> 00:08:02.569 align:start position:0% for many details it's a new feature is 00:08:02.569 --> 00:08:05.799 align:start position:0% for many details it's a new feature is an<00:08:02.779> advertisement<00:08:03.729> in<00:08:04.729> a<00:08:04.909> feature<00:08:05.179> where 00:08:05.799 --> 00:08:05.809 align:start position:0% an advertisement in a feature where 00:08:05.809 --> 00:08:07.899 align:start position:0% an advertisement in a feature where nodes<00:08:06.050> can<00:08:06.319> advertise<00:08:06.829> their<00:08:07.189> capabilities 00:08:07.899 --> 00:08:07.909 align:start position:0% nodes can advertise their capabilities 00:08:07.909 --> 00:08:10.839 align:start position:0% nodes can advertise their capabilities they<00:08:08.539> can<00:08:08.839> a<00:08:09.259> big<00:08:09.739> multiple<00:08:10.249> category 00:08:10.839 --> 00:08:10.849 align:start position:0% they can a big multiple category 00:08:10.849 --> 00:08:13.559 align:start position:0% they can a big multiple category identifier<00:08:11.569> or<00:08:11.959> so-called<00:08:12.559> topics<00:08:13.159> and 00:08:13.559 --> 00:08:13.569 align:start position:0% identifier or so-called topics and 00:08:13.569 --> 00:08:16.209 align:start position:0% identifier or so-called topics and advertise<00:08:14.569> them<00:08:14.809> under<00:08:15.619> under<00:08:16.009> these 00:08:16.209 --> 00:08:16.219 align:start position:0% advertise them under under these 00:08:16.219 --> 00:08:17.679 align:start position:0% advertise them under under these categories<00:08:16.399> and<00:08:16.939> of<00:08:17.059> course<00:08:17.269> they<00:08:17.389> can<00:08:17.539> also 00:08:17.679 --> 00:08:17.689 align:start position:0% categories and of course they can also 00:08:17.689 --> 00:08:19.749 align:start position:0% categories and of course they can also look<00:08:17.959> for<00:08:18.199> notes<00:08:18.439> who<00:08:19.099> advertise<00:08:19.550> themselves 00:08:19.749 --> 00:08:19.759 align:start position:0% look for notes who advertise themselves 00:08:19.759 --> 00:08:22.540 align:start position:0% look for notes who advertise themselves under<00:08:20.269> certain<00:08:20.479> topics<00:08:21.050> of<00:08:21.259> course<00:08:21.919> one<00:08:22.429> of 00:08:22.540 --> 00:08:22.550 align:start position:0% under certain topics of course one of 00:08:22.550 --> 00:08:28.089 align:start position:0% under certain topics of course one of such<00:08:23.179> topics<00:08:23.419> will<00:08:23.839> be<00:08:23.869> light<00:08:24.349> server<00:08:27.099> and 00:08:28.089 --> 00:08:28.099 align:start position:0% such topics will be light server and 00:08:28.099 --> 00:08:30.879 align:start position:0% such topics will be light server and finally<00:08:29.059> I<00:08:29.269> would<00:08:29.449> quickly<00:08:30.289> like<00:08:30.529> to<00:08:30.679> talk 00:08:30.879 --> 00:08:30.889 align:start position:0% finally I would quickly like to talk 00:08:30.889 --> 00:08:33.699 align:start position:0% finally I would quickly like to talk about<00:08:31.069> one<00:08:32.029> of<00:08:32.059> my<00:08:32.209> future<00:08:32.719> development<00:08:33.409> plans 00:08:33.699 --> 00:08:33.709 align:start position:0% about one of my future development plans 00:08:33.709 --> 00:08:37.059 align:start position:0% about one of my future development plans which<00:08:34.550> could<00:08:35.149> greatly<00:08:36.110> enhance<00:08:36.769> the 00:08:37.059 --> 00:08:37.069 align:start position:0% which could greatly enhance the 00:08:37.069 --> 00:08:39.420 align:start position:0% which could greatly enhance the performance<00:08:37.459> and<00:08:38.059> reflective<00:08:38.870> respective 00:08:39.420 --> 00:08:39.430 align:start position:0% performance and reflective respective 00:08:39.430 --> 00:08:42.399 align:start position:0% performance and reflective respective flexibility<00:08:40.430> of<00:08:40.610> the<00:08:40.699> light<00:08:41.120> protocol<00:08:41.629> by 00:08:42.399 --> 00:08:42.409 align:start position:0% flexibility of the light protocol by 00:08:42.409 --> 00:08:45.369 align:start position:0% flexibility of the light protocol by allowing<00:08:42.889> clients<00:08:43.279> to<00:08:43.789> run<00:08:44.629> complex 00:08:45.369 --> 00:08:45.379 align:start position:0% allowing clients to run complex 00:08:45.379 --> 00:08:49.389 align:start position:0% allowing clients to run complex operations<00:08:46.009> on<00:08:46.279> the<00:08:46.339> server<00:08:46.850> side<00:08:48.100> in<00:08:49.100> theory 00:08:49.389 --> 00:08:49.399 align:start position:0% operations on the server side in theory 00:08:49.399 --> 00:08:51.790 align:start position:0% operations on the server side in theory basically<00:08:49.790> a<00:08:50.120> suckfest<00:08:50.389> can<00:08:50.779> provide<00:08:51.139> any 00:08:51.790 --> 00:08:51.800 align:start position:0% basically a suckfest can provide any 00:08:51.800 --> 00:08:54.519 align:start position:0% basically a suckfest can provide any information<00:08:52.040> a<00:08:52.459> client<00:08:52.819> needs<00:08:53.029> but<00:08:53.720> if<00:08:54.170> they 00:08:54.519 --> 00:08:54.529 align:start position:0% information a client needs but if they 00:08:54.529 --> 00:08:56.559 align:start position:0% information a client needs but if they want<00:08:54.740> to<00:08:54.920> evaluate<00:08:55.399> something<00:08:55.879> more<00:08:56.180> complex 00:08:56.559 --> 00:08:56.569 align:start position:0% want to evaluate something more complex 00:08:56.569 --> 00:08:59.799 align:start position:0% want to evaluate something more complex like<00:08:56.750> and<00:08:57.230> a<00:08:57.559> contract<00:08:58.370> the<00:08:58.809> accessor 00:08:59.799 --> 00:08:59.809 align:start position:0% like and a contract the accessor 00:08:59.809 --> 00:09:02.379 align:start position:0% like and a contract the accessor function<00:09:00.199> that<00:09:00.410> accesses<00:09:01.009> 8,000<00:09:01.939> state 00:09:02.379 --> 00:09:02.389 align:start position:0% function that accesses 8,000 state 00:09:02.389 --> 00:09:05.240 align:start position:0% function that accesses 8,000 state entries<00:09:02.839> that<00:09:03.019> would<00:09:03.500> also<00:09:03.649> mean 00:09:05.240 --> 00:09:05.250 align:start position:0% entries that would also mean 00:09:05.250 --> 00:09:08.750 align:start position:0% entries that would also mean a<00:09:05.780> thousand<00:09:06.780> consecutive<00:09:07.740> arias<00:09:08.160> requests 00:09:08.750 --> 00:09:08.760 align:start position:0% a thousand consecutive arias requests 00:09:08.760 --> 00:09:12.280 align:start position:0% a thousand consecutive arias requests which<00:09:09.240> would<00:09:09.660> take<00:09:09.960> a<00:09:09.990> very<00:09:10.170> long<00:09:10.500> time 00:09:12.280 --> 00:09:12.290 align:start position:0% which would take a very long time 00:09:12.290 --> 00:09:15.020 align:start position:0% which would take a very long time usually<00:09:13.460> evaluating<00:09:14.460> complex<00:09:14.880> data 00:09:15.020 --> 00:09:15.030 align:start position:0% usually evaluating complex data 00:09:15.030 --> 00:09:17.150 align:start position:0% usually evaluating complex data structures<00:09:15.150> on<00:09:15.810> server<00:09:16.110> side<00:09:16.500> could<00:09:17.010> be 00:09:17.150 --> 00:09:17.160 align:start position:0% structures on server side could be 00:09:17.160 --> 00:09:20.480 align:start position:0% structures on server side could be orders<00:09:17.610> of<00:09:17.790> magnitude<00:09:18.270> faster<00:09:18.300> and<00:09:19.070> I<00:09:20.070> don't 00:09:20.480 --> 00:09:20.490 align:start position:0% orders of magnitude faster and I don't 00:09:20.490 --> 00:09:23.330 align:start position:0% orders of magnitude faster and I don't only<00:09:20.880> want<00:09:21.270> to<00:09:21.510> evaluate<00:09:21.870> contact<00:09:22.680> mashup<00:09:23.100> of 00:09:23.330 --> 00:09:23.340 align:start position:0% only want to evaluate contact mashup of 00:09:23.340 --> 00:09:25.820 align:start position:0% only want to evaluate contact mashup of contract<00:09:24.120> functions<00:09:24.600> I<00:09:24.840> would<00:09:25.440> like<00:09:25.620> to 00:09:25.820 --> 00:09:25.830 align:start position:0% contract functions I would like to 00:09:25.830 --> 00:09:30.950 align:start position:0% contract functions I would like to create<00:09:26.220> a<00:09:27.170> universal<00:09:29.000> virtual<00:09:30.000> machine<00:09:30.360> that 00:09:30.950 --> 00:09:30.960 align:start position:0% create a universal virtual machine that 00:09:30.960 --> 00:09:36.290 align:start position:0% create a universal virtual machine that can<00:09:33.620> access<00:09:34.620> anything<00:09:35.100> anything<00:09:35.700> from<00:09:36.150> the 00:09:36.290 --> 00:09:36.300 align:start position:0% can access anything anything from the 00:09:36.300 --> 00:09:38.080 align:start position:0% can access anything anything from the block<00:09:36.480> chain<00:09:36.510> including<00:09:37.290> block<00:09:37.710> headers 00:09:38.080 --> 00:09:38.090 align:start position:0% block chain including block headers 00:09:38.090 --> 00:09:41.840 align:start position:0% block chain including block headers transactions<00:09:40.160> receipts<00:09:41.160> logs<00:09:41.460> everything 00:09:41.840 --> 00:09:41.850 align:start position:0% transactions receipts logs everything 00:09:41.850 --> 00:09:47.510 align:start position:0% transactions receipts logs everything and<00:09:44.060> allow<00:09:45.060> clients<00:09:45.360> to<00:09:45.690> run<00:09:46.440> any<00:09:46.710> code<00:09:47.010> in 00:09:47.510 --> 00:09:47.520 align:start position:0% and allow clients to run any code in 00:09:47.520 --> 00:09:50.810 align:start position:0% and allow clients to run any code in such<00:09:48.030> a<00:09:48.680> virtual<00:09:49.680> machine<00:09:49.920> on<00:09:49.980> server<00:09:50.400> side<00:09:50.640> so 00:09:50.810 --> 00:09:50.820 align:start position:0% such a virtual machine on server side so 00:09:50.820 --> 00:09:52.730 align:start position:0% such a virtual machine on server side so that<00:09:50.970> basically<00:09:51.120> they<00:09:51.480> can<00:09:51.690> ask<00:09:52.140> any<00:09:52.650> question 00:09:52.730 --> 00:09:52.740 align:start position:0% that basically they can ask any question 00:09:52.740 --> 00:09:55.010 align:start position:0% that basically they can ask any question about<00:09:53.190> the<00:09:53.460> blockchain<00:09:53.670> that<00:09:54.270> a<00:09:54.300> foo<00:09:54.630> not<00:09:54.810> can 00:09:55.010 --> 00:09:55.020 align:start position:0% about the blockchain that a foo not can 00:09:55.020 --> 00:09:57.500 align:start position:0% about the blockchain that a foo not can possibly<00:09:55.440> answer<00:09:55.740> of<00:09:56.730> course<00:09:57.060> if<00:09:57.270> we<00:09:57.420> are 00:09:57.500 --> 00:09:57.510 align:start position:0% possibly answer of course if we are 00:09:57.510 --> 00:10:00.620 align:start position:0% possibly answer of course if we are running<00:09:57.660> code<00:09:58.020> on<00:09:58.170> the<00:09:58.260> server<00:09:58.290> side<00:09:59.240> we<00:10:00.240> have 00:10:00.620 --> 00:10:00.630 align:start position:0% running code on the server side we have 00:10:00.630 --> 00:10:02.540 align:start position:0% running code on the server side we have to<00:10:00.750> make<00:10:00.930> sure<00:10:01.170> that<00:10:01.410> the<00:10:01.680> client<00:10:02.070> can<00:10:02.160> somehow 00:10:02.540 --> 00:10:02.550 align:start position:0% to make sure that the client can somehow 00:10:02.550 --> 00:10:04.880 align:start position:0% to make sure that the client can somehow know<00:10:02.970> that<00:10:03.270> they<00:10:04.230> are<00:10:04.380> getting<00:10:04.500> the<00:10:04.740> correct 00:10:04.880 --> 00:10:04.890 align:start position:0% know that they are getting the correct 00:10:04.890 --> 00:10:08.300 align:start position:0% know that they are getting the correct answer<00:10:05.430> and<00:10:06.240> there<00:10:06.900> are<00:10:07.200> two<00:10:07.800> possible 00:10:08.300 --> 00:10:08.310 align:start position:0% answer and there are two possible 00:10:08.310 --> 00:10:11.930 align:start position:0% answer and there are two possible approaches<00:10:08.820> to<00:10:09.150> achieve<00:10:09.510> this<00:10:09.750> and<00:10:10.400> I<00:10:11.400> would 00:10:11.930 --> 00:10:11.940 align:start position:0% approaches to achieve this and I would 00:10:11.940 --> 00:10:14.360 align:start position:0% approaches to achieve this and I would like<00:10:12.089> to<00:10:12.500> make<00:10:13.500> both<00:10:13.770> of<00:10:13.800> these<00:10:14.100> options 00:10:14.360 --> 00:10:14.370 align:start position:0% like to make both of these options 00:10:14.370 --> 00:10:17.079 align:start position:0% like to make both of these options available<00:10:15.060> for<00:10:15.300> clients<00:10:16.140> to<00:10:16.350> choose 00:10:17.079 --> 00:10:17.089 align:start position:0% available for clients to choose 00:10:17.089 --> 00:10:20.800 align:start position:0% available for clients to choose according<00:10:18.089> to<00:10:18.120> their<00:10:18.830> priorities<00:10:19.830> one<00:10:20.610> of 00:10:20.800 --> 00:10:20.810 align:start position:0% according to their priorities one of 00:10:20.810 --> 00:10:24.260 align:start position:0% according to their priorities one of such<00:10:21.810> one<00:10:22.140> of<00:10:22.230> these<00:10:22.380> approaches<00:10:22.650> is<00:10:23.040> a<00:10:23.270> that 00:10:24.260 --> 00:10:24.270 align:start position:0% such one of these approaches is a that 00:10:24.270 --> 00:10:27.220 align:start position:0% such one of these approaches is a that when<00:10:24.810> a<00:10:24.839> certain<00:10:25.320> in<00:10:25.500> the<00:10:25.589> server<00:10:25.920> runs<00:10:26.160> a 00:10:27.220 --> 00:10:27.230 align:start position:0% when a certain in the server runs a 00:10:27.230 --> 00:10:29.540 align:start position:0% when a certain in the server runs a virtual<00:10:28.230> machine<00:10:28.470> code<00:10:28.680> it<00:10:28.920> collects<00:10:29.339> all<00:10:29.520> the 00:10:29.540 --> 00:10:29.550 align:start position:0% virtual machine code it collects all the 00:10:29.550 --> 00:10:32.600 align:start position:0% virtual machine code it collects all the data<00:10:29.850> it<00:10:30.060> accesses<00:10:30.450> and<00:10:30.950> creates<00:10:31.950> more<00:10:32.100> proofs 00:10:32.600 --> 00:10:32.610 align:start position:0% data it accesses and creates more proofs 00:10:32.610 --> 00:10:34.490 align:start position:0% data it accesses and creates more proofs for<00:10:33.089> all<00:10:33.240> of<00:10:33.420> them<00:10:33.600> and<00:10:33.720> returns<00:10:34.050> this<00:10:34.260> proves 00:10:34.490 --> 00:10:34.500 align:start position:0% for all of them and returns this proves 00:10:34.500 --> 00:10:37.280 align:start position:0% for all of them and returns this proves to<00:10:34.620> the<00:10:34.650> client<00:10:35.100> so<00:10:35.520> that<00:10:35.550> client<00:10:36.060> can<00:10:36.300> with 00:10:37.280 --> 00:10:37.290 align:start position:0% to the client so that client can with 00:10:37.290 --> 00:10:40.450 align:start position:0% to the client so that client can with one<00:10:37.589> request<00:10:38.130> and<00:10:38.370> one<00:10:38.520> imply<00:10:38.850> the<00:10:38.910> client<00:10:39.630> can 00:10:40.450 --> 00:10:40.460 align:start position:0% one request and one imply the client can 00:10:40.460 --> 00:10:44.210 align:start position:0% one request and one imply the client can rerun<00:10:41.460> the<00:10:41.700> entire<00:10:42.589> function<00:10:43.589> and<00:10:43.800> have<00:10:44.040> other 00:10:44.210 --> 00:10:44.220 align:start position:0% rerun the entire function and have other 00:10:44.220 --> 00:10:47.810 align:start position:0% rerun the entire function and have other data<00:10:44.580> available<00:10:45.920> another<00:10:46.920> approach<00:10:47.400> might<00:10:47.670> be 00:10:47.810 --> 00:10:47.820 align:start position:0% data available another approach might be 00:10:47.820 --> 00:10:50.120 align:start position:0% data available another approach might be useful<00:10:47.970> than<00:10:48.420> processing<00:10:49.260> large<00:10:49.500> amounts<00:10:49.589> of 00:10:50.120 --> 00:10:50.130 align:start position:0% useful than processing large amounts of 00:10:50.130 --> 00:10:53.780 align:start position:0% useful than processing large amounts of data<00:10:50.370> and<00:10:50.790> it's<00:10:51.450> a<00:10:51.660> more<00:10:52.620> generalized<00:10:53.250> option 00:10:53.780 --> 00:10:53.790 align:start position:0% data and it's a more generalized option 00:10:53.790 --> 00:10:56.540 align:start position:0% data and it's a more generalized option computing<00:10:54.570> approach<00:10:55.320> very<00:10:55.680> much<00:10:55.890> like<00:10:56.160> what<00:10:56.520> a 00:10:56.540 --> 00:10:56.550 align:start position:0% computing approach very much like what a 00:10:56.550 --> 00:10:59.050 align:start position:0% computing approach very much like what a crystal<00:10:57.150> was<00:10:57.450> talking<00:10:58.170> about<00:10:58.410> yesterday 00:10:59.050 --> 00:10:59.060 align:start position:0% crystal was talking about yesterday 00:10:59.060 --> 00:11:02.770 align:start position:0% crystal was talking about yesterday basically<00:11:00.060> it's<00:11:00.480> about<00:11:00.770> server<00:11:01.770> signing 00:11:02.770 --> 00:11:02.780 align:start position:0% basically it's about server signing 00:11:02.780 --> 00:11:05.810 align:start position:0% basically it's about server signing statements<00:11:03.780> saying<00:11:04.380> that<00:11:04.800> I<00:11:04.950> guarantee<00:11:05.580> that 00:11:05.810 --> 00:11:05.820 align:start position:0% statements saying that I guarantee that 00:11:05.820 --> 00:11:08.630 align:start position:0% statements saying that I guarantee that running<00:11:06.150> this<00:11:06.300> function<00:11:06.980> with<00:11:07.980> this<00:11:08.250> block 00:11:08.630 --> 00:11:08.640 align:start position:0% running this function with this block 00:11:08.640 --> 00:11:11.690 align:start position:0% running this function with this block chain<00:11:08.820> as<00:11:08.970> an<00:11:09.060> input<00:11:09.830> returns<00:11:10.830> in<00:11:11.190> this<00:11:11.520> many 00:11:11.690 --> 00:11:11.700 align:start position:0% chain as an input returns in this many 00:11:11.700 --> 00:11:14.960 align:start position:0% chain as an input returns in this many clock<00:11:12.180> cycles<00:11:12.720> with<00:11:13.230> these<00:11:13.440> results<00:11:14.040> the 00:11:14.960 --> 00:11:14.970 align:start position:0% clock cycles with these results the 00:11:14.970 --> 00:11:16.780 align:start position:0% clock cycles with these results the client<00:11:15.360> can 00:11:16.780 --> 00:11:16.790 align:start position:0% client can 00:11:16.790 --> 00:11:19.300 align:start position:0% client can ask<00:11:16.940> multiple<00:11:17.750> randomly<00:11:18.440> selected<00:11:18.860> servers 00:11:19.300 --> 00:11:19.310 align:start position:0% ask multiple randomly selected servers 00:11:19.310 --> 00:11:21.850 align:start position:0% ask multiple randomly selected servers to<00:11:19.640> answer<00:11:20.330> the<00:11:20.510> same<00:11:20.780> question<00:11:20.840> evaluate<00:11:21.740> the 00:11:21.850 --> 00:11:21.860 align:start position:0% to answer the same question evaluate the 00:11:21.860 --> 00:11:24.190 align:start position:0% to answer the same question evaluate the same<00:11:22.040> function<00:11:22.630> hopefully<00:11:23.630> all<00:11:23.660> of<00:11:23.840> them<00:11:24.080> were 00:11:24.190 --> 00:11:24.200 align:start position:0% same function hopefully all of them were 00:11:24.200 --> 00:11:25.960 align:start position:0% same function hopefully all of them were returned<00:11:24.500> the<00:11:24.620> same<00:11:24.860> and<00:11:25.100> then<00:11:25.250> the<00:11:25.820> client 00:11:25.960 --> 00:11:25.970 align:start position:0% returned the same and then the client 00:11:25.970 --> 00:11:29.320 align:start position:0% returned the same and then the client can<00:11:26.270> believe<00:11:26.570> it<00:11:26.800> in<00:11:27.800> the<00:11:28.010> unlikely<00:11:28.400> case<00:11:28.820> when 00:11:29.320 --> 00:11:29.330 align:start position:0% can believe it in the unlikely case when 00:11:29.330 --> 00:11:31.630 align:start position:0% can believe it in the unlikely case when they<00:11:29.480> return<00:11:29.960> different<00:11:30.350> results<00:11:30.920> of<00:11:31.100> course 00:11:31.630 --> 00:11:31.640 align:start position:0% they return different results of course 00:11:31.640 --> 00:11:33.910 align:start position:0% they return different results of course at<00:11:32.480> least<00:11:32.690> one<00:11:32.810> of<00:11:32.840> them<00:11:33.080> will<00:11:33.230> be<00:11:33.410> false<00:11:33.680> and 00:11:33.910 --> 00:11:33.920 align:start position:0% at least one of them will be false and 00:11:33.920 --> 00:11:36.760 align:start position:0% at least one of them will be false and the<00:11:34.550> client<00:11:34.910> should<00:11:35.150> post<00:11:35.600> the<00:11:35.960> statements<00:11:36.560> to 00:11:36.760 --> 00:11:36.770 align:start position:0% the client should post the statements to 00:11:36.770 --> 00:11:39.100 align:start position:0% the client should post the statements to a<00:11:36.860> judge<00:11:37.250> contract<00:11:37.790> which<00:11:38.090> can<00:11:38.390> which<00:11:38.870> will 00:11:39.100 --> 00:11:39.110 align:start position:0% a judge contract which can which will 00:11:39.110 --> 00:11:43.750 align:start position:0% a judge contract which can which will then<00:11:39.320> request<00:11:40.100> the<00:11:40.750> intermediate<00:11:41.770> states<00:11:42.770> of 00:11:43.750 --> 00:11:43.760 align:start position:0% then request the intermediate states of 00:11:43.760 --> 00:11:47.050 align:start position:0% then request the intermediate states of off<00:11:44.240> of<00:11:44.570> this<00:11:44.720> vm<00:11:45.350> execution<00:11:46.040> from<00:11:46.190> the<00:11:46.520> from 00:11:47.050 --> 00:11:47.060 align:start position:0% off of this vm execution from the from 00:11:47.060 --> 00:11:49.570 align:start position:0% off of this vm execution from the from the<00:11:47.240> signing<00:11:47.750> parties<00:11:48.230> until<00:11:48.890> it<00:11:49.070> finds<00:11:49.310> the 00:11:49.570 --> 00:11:49.580 align:start position:0% the signing parties until it finds the 00:11:49.580 --> 00:11:51.340 align:start position:0% the signing parties until it finds the one<00:11:49.730> single<00:11:50.090> instruction<00:11:50.690> that<00:11:51.020> has<00:11:51.140> been 00:11:51.340 --> 00:11:51.350 align:start position:0% one single instruction that has been 00:11:51.350 --> 00:11:55.540 align:start position:0% one single instruction that has been executed<00:11:51.740> differently<00:11:52.580> and<00:11:53.470> punish<00:11:54.470> that<00:11:54.830> one 00:11:55.540 --> 00:11:55.550 align:start position:0% executed differently and punish that one 00:11:55.550 --> 00:11:57.640 align:start position:0% executed differently and punish that one which<00:11:55.940> has<00:11:56.150> been<00:11:56.330> lying<00:11:56.690> by<00:11:57.020> taking<00:11:57.440> away<00:11:57.560> a 00:11:57.640 --> 00:11:57.650 align:start position:0% which has been lying by taking away a 00:11:57.650 --> 00:12:02.860 align:start position:0% which has been lying by taking away a security<00:11:58.610> deposit<00:12:00.670> this<00:12:01.670> both<00:12:02.600> of<00:12:02.750> these 00:12:02.860 --> 00:12:02.870 align:start position:0% security deposit this both of these 00:12:02.870 --> 00:12:04.630 align:start position:0% security deposit this both of these approaches<00:12:03.110> have<00:12:03.560> their<00:12:03.770> advantages<00:12:04.040> and 00:12:04.630 --> 00:12:04.640 align:start position:0% approaches have their advantages and 00:12:04.640 --> 00:12:07.810 align:start position:0% approaches have their advantages and disadvantages<00:12:05.330> but<00:12:06.010> whichever<00:12:07.010> one<00:12:07.640> the 00:12:07.810 --> 00:12:07.820 align:start position:0% disadvantages but whichever one the 00:12:07.820 --> 00:12:11.260 align:start position:0% disadvantages but whichever one the clients<00:12:08.270> are<00:12:08.360> choosing<00:12:09.100> this<00:12:10.100> remote<00:12:10.850> virtual 00:12:11.260 --> 00:12:11.270 align:start position:0% clients are choosing this remote virtual 00:12:11.270 --> 00:12:14.380 align:start position:0% clients are choosing this remote virtual machine<00:12:11.540> execution<00:12:12.260> he<00:12:12.950> will<00:12:13.640> basically<00:12:14.210> be 00:12:14.380 --> 00:12:14.390 align:start position:0% machine execution he will basically be 00:12:14.390 --> 00:12:19.420 align:start position:0% machine execution he will basically be the<00:12:14.600> ultimate<00:12:15.340> flexible<00:12:17.950> Elias<00:12:18.950> request 00:12:19.420 --> 00:12:19.430 align:start position:0% the ultimate flexible Elias request 00:12:19.430 --> 00:12:23.140 align:start position:0% the ultimate flexible Elias request which<00:12:20.180> can<00:12:21.190> minimum<00:12:22.190> emission<00:12:22.700> minimalize 00:12:23.140 --> 00:12:23.150 align:start position:0% which can minimum emission minimalize 00:12:23.150 --> 00:12:27.820 align:start position:0% which can minimum emission minimalize any<00:12:23.570> gap<00:12:24.290> between<00:12:24.590> the<00:12:25.040> capabilities<00:12:25.910> of<00:12:26.830> full 00:12:27.820 --> 00:12:27.830 align:start position:0% any gap between the capabilities of full 00:12:27.830 --> 00:12:31.360 align:start position:0% any gap between the capabilities of full and<00:12:28.010> light<00:12:28.310> plants<00:12:29.440> which<00:12:30.440> I<00:12:30.740> believe<00:12:31.010> will 00:12:31.360 --> 00:12:31.370 align:start position:0% and light plants which I believe will 00:12:31.370 --> 00:12:34.620 align:start position:0% and light plants which I believe will bring<00:12:32.000> us<00:12:32.150> closer<00:12:32.480> to<00:12:32.810> realizing<00:12:33.800> our 00:12:34.620 --> 00:12:34.630 align:start position:0% bring us closer to realizing our 00:12:34.630 --> 00:12:44.940 align:start position:0% bring us closer to realizing our original<00:12:35.630> vision<00:12:35.930> we<00:12:36.590> had<00:12:36.770> with<00:12:37.070> athyrium<00:12:42.820> so 00:12:44.940 --> 00:12:44.950 align:start position:0% original vision we had with athyrium so 00:12:44.950 --> 00:12:47.590 align:start position:0% original vision we had with athyrium so we<00:12:45.950> already<00:12:46.070> and<00:12:46.520> thank<00:12:47.120> you<00:12:47.180> for<00:12:47.450> your 00:12:47.590 --> 00:12:47.600 align:start position:0% we already and thank you for your 00:12:47.600 --> 00:12:51.610 align:start position:0% we already and thank you for your attention<00:12:48.080> and<00:12:48.350> if<00:12:48.830> you<00:12:48.980> as<00:12:49.460> I<00:12:49.520> promised<00:12:50.620> here 00:12:51.610 --> 00:12:51.620 align:start position:0% attention and if you as I promised here 00:12:51.620 --> 00:12:53.860 align:start position:0% attention and if you as I promised here are<00:12:51.740> some<00:12:51.980> links<00:12:52.340> there's<00:12:52.940> a<00:12:53.030> gator<00:12:53.420> channel 00:12:53.860 --> 00:12:53.870 align:start position:0% are some links there's a gator channel 00:12:53.870 --> 00:12:56.950 align:start position:0% are some links there's a gator channel you<00:12:54.410> that<00:12:54.710> I<00:12:54.860> am<00:12:54.890> /<00:12:55.250> 18<00:12:55.520> /<00:12:55.820> light<00:12:56.210> client<00:12:56.720> and 00:12:56.950 --> 00:12:56.960 align:start position:0% you that I am / 18 / light client and 00:12:56.960 --> 00:12:59.530 align:start position:0% you that I am / 18 / light client and this<00:12:57.440> is<00:12:57.590> the<00:12:57.710> main<00:12:57.890> forum<00:12:58.190> of<00:12:58.490> the<00:12:58.550> where<00:12:59.420> you 00:12:59.530 --> 00:12:59.540 align:start position:0% this is the main forum of the where you 00:12:59.540 --> 00:13:02.080 align:start position:0% this is the main forum of the where you can<00:12:59.720> follow<00:12:59.990> the<00:13:00.890> developments<00:13:01.700> you<00:13:01.790> can<00:13:01.940> ask 00:13:02.080 --> 00:13:02.090 align:start position:0% can follow the developments you can ask 00:13:02.090 --> 00:13:06.730 align:start position:0% can follow the developments you can ask questions<00:13:02.980> and<00:13:04.600> whatever<00:13:05.600> news<00:13:06.140> I<00:13:06.320> have<00:13:06.500> I 00:13:06.730 --> 00:13:06.740 align:start position:0% questions and whatever news I have I 00:13:06.740 --> 00:13:11.320 align:start position:0% questions and whatever news I have I always<00:13:07.360> posted<00:13:08.360> there<00:13:08.630> and<00:13:09.700> there's<00:13:10.700> also<00:13:10.910> a 00:13:11.320 --> 00:13:11.330 align:start position:0% always posted there and there's also a 00:13:11.330 --> 00:13:13.900 align:start position:0% always posted there and there's also a wiki<00:13:11.930> page<00:13:12.140> with<00:13:12.550> with<00:13:13.550> with<00:13:13.760> the 00:13:13.900 --> 00:13:13.910 align:start position:0% wiki page with with with the 00:13:13.910 --> 00:13:16.810 align:start position:0% wiki page with with with the instructions<00:13:14.480> for<00:13:14.570> two<00:13:15.410> to<00:13:15.740> try<00:13:16.010> the<00:13:16.070> current 00:13:16.810 --> 00:13:16.820 align:start position:0% instructions for two to try the current 00:13:16.820 --> 00:13:25.780 align:start position:0% instructions for two to try the current beta<00:13:17.000> version<00:13:18.340> so<00:13:22.360> please<00:13:23.360> please<00:13:24.610> stay<00:13:25.610> tuned 00:13:25.780 --> 00:13:25.790 align:start position:0% beta version so please please stay tuned 00:13:25.790 --> 00:13:28.420 align:start position:0% beta version so please please stay tuned for<00:13:26.090> much<00:13:26.890> development<00:13:27.890> in<00:13:28.130> the<00:13:28.220> near<00:13:28.370> future 00:13:28.420 --> 00:13:28.430 align:start position:0% for much development in the near future 00:13:28.430 --> 00:13:30.430 align:start position:0% for much development in the near future I<00:13:29.060> was<00:13:29.420> so 00:13:30.430 --> 00:13:30.440 align:start position:0% I was so 00:13:30.440 --> 00:13:32.620 align:start position:0% I was so lot<00:13:30.560> of<00:13:30.670> documentation<00:13:31.670> is<00:13:31.970> coming<00:13:32.360> soon 00:13:32.620 --> 00:13:32.630 align:start position:0% lot of documentation is coming soon 00:13:32.630 --> 00:13:35.910 align:start position:0% lot of documentation is coming soon because<00:13:33.040> another<00:13:34.040> good<00:13:34.310> news<00:13:34.460> is<00:13:34.640> that<00:13:34.820> now 00:13:35.910 --> 00:13:35.920 align:start position:0% because another good news is that now 00:13:35.920 --> 00:13:41.350 align:start position:0% because another good news is that now both<00:13:37.360> parity<00:13:38.360> and<00:13:38.620> C++<00:13:39.620> wants<00:13:40.370> to<00:13:40.580> implement 00:13:41.350 --> 00:13:41.360 align:start position:0% both parity and C++ wants to implement 00:13:41.360 --> 00:13:43.870 align:start position:0% both parity and C++ wants to implement the<00:13:41.450> light<00:13:41.930> protocol<00:13:42.440> so<00:13:42.800> of<00:13:43.430> course<00:13:43.610> we<00:13:43.760> have 00:13:43.870 --> 00:13:43.880 align:start position:0% the light protocol so of course we have 00:13:43.880 --> 00:13:46.180 align:start position:0% the light protocol so of course we have to<00:13:44.060> improve<00:13:44.750> specifications<00:13:45.650> better<00:13:45.860> because 00:13:46.180 --> 00:13:46.190 align:start position:0% to improve specifications better because 00:13:46.190 --> 00:13:48.130 align:start position:0% to improve specifications better because so<00:13:46.340> far<00:13:46.490> I<00:13:46.550> have<00:13:46.790> concentrated<00:13:47.330> mostly<00:13:47.720> on<00:13:47.900> on 00:13:48.130 --> 00:13:48.140 align:start position:0% so far I have concentrated mostly on on 00:13:48.140 --> 00:13:52.300 align:start position:0% so far I have concentrated mostly on on code<00:13:49.180> thank<00:13:50.180> you