WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:19.710 align:start position:0% [Applause] 00:00:19.710 --> 00:00:19.720 align:start position:0% 00:00:19.720 --> 00:00:37.900 align:start position:0% [Music] 00:00:37.900 --> 00:00:37.910 align:start position:0% 00:00:37.910 --> 00:00:51.840 align:start position:0% [Music] 00:00:51.840 --> 00:00:51.850 align:start position:0% 00:00:51.850 --> 00:01:17.730 align:start position:0% so<00:00:57.100> so<00:01:10.930> is<00:01:11.930> this<00:01:12.340> device<00:01:14.680> service<00:01:15.680> available 00:01:17.730 --> 00:01:17.740 align:start position:0% so so is this device service available 00:01:17.740 --> 00:01:21.820 align:start position:0% so so is this device service available times<00:01:18.740> and<00:01:19.750> I've<00:01:20.750> been<00:01:21.080> implementing<00:01:21.650> this 00:01:21.820 --> 00:01:21.830 align:start position:0% times and I've been implementing this 00:01:21.830 --> 00:01:25.600 align:start position:0% times and I've been implementing this model<00:01:22.250> in<00:01:22.970> the<00:01:23.450> GUI<00:01:23.659> theory<00:01:24.250> also<00:01:25.250> called 00:01:25.600 --> 00:01:25.610 align:start position:0% model in the GUI theory also called 00:01:25.610 --> 00:01:29.320 align:start position:0% model in the GUI theory also called alias<00:01:26.090> but<00:01:26.890> it's<00:01:27.890> also<00:01:28.070> applicable<00:01:28.490> in<00:01:29.030> any 00:01:29.320 --> 00:01:29.330 align:start position:0% alias but it's also applicable in any 00:01:29.330 --> 00:01:32.370 align:start position:0% alias but it's also applicable in any model<00:01:29.770> or<00:01:30.770> any<00:01:31.130> for<00:01:31.549> any<00:01:31.580> photos 00:01:32.370 --> 00:01:32.380 align:start position:0% model or any for any photos 00:01:32.380 --> 00:01:35.230 align:start position:0% model or any for any photos wetness<00:01:33.380> those<00:01:34.040> turns<00:01:34.460> out<00:01:34.640> to<00:01:34.820> be<00:01:34.850> workable 00:01:35.230 --> 00:01:35.240 align:start position:0% wetness those turns out to be workable 00:01:35.240 --> 00:01:37.030 align:start position:0% wetness those turns out to be workable than<00:01:35.810> it<00:01:35.930> could<00:01:36.080> also<00:01:36.230> serve<00:01:36.530> as<00:01:36.650> a<00:01:36.740> proof<00:01:36.950> of 00:01:37.030 --> 00:01:37.040 align:start position:0% than it could also serve as a proof of 00:01:37.040 --> 00:01:39.900 align:start position:0% than it could also serve as a proof of concept<00:01:37.250> for<00:01:37.670> our<00:01:37.760> future<00:01:38.420> Network<00:01:38.780> protocols 00:01:39.900 --> 00:01:39.910 align:start position:0% concept for our future Network protocols 00:01:39.910 --> 00:01:43.200 align:start position:0% concept for our future Network protocols so<00:01:40.910> what<00:01:41.120> I<00:01:41.330> was<00:01:41.510> trying<00:01:41.780> to<00:01:41.840> realize<00:01:42.230> is<00:01:42.560> a 00:01:43.200 --> 00:01:43.210 align:start position:0% so what I was trying to realize is a 00:01:43.210 --> 00:01:46.000 align:start position:0% so what I was trying to realize is a truly<00:01:44.210> needy<00:01:44.570> surprise<00:01:45.020> the<00:01:45.320> service<00:01:45.710> found 00:01:46.000 --> 00:01:46.010 align:start position:0% truly needy surprise the service found 00:01:46.010 --> 00:01:49.750 align:start position:0% truly needy surprise the service found the<00:01:46.640> very<00:01:47.030> presence<00:01:47.510> of<00:01:47.840> the<00:01:48.100> server's<00:01:49.100> can<00:01:49.430> do 00:01:49.750 --> 00:01:49.760 align:start position:0% the very presence of the server's can do 00:01:49.760 --> 00:01:52.960 align:start position:0% the very presence of the server's can do resource<00:01:50.360> allocation<00:01:51.020> and<00:01:51.550> vocalizing<00:01:52.550> based 00:01:52.960 --> 00:01:52.970 align:start position:0% resource allocation and vocalizing based 00:01:52.970 --> 00:01:56.950 align:start position:0% resource allocation and vocalizing based purely<00:01:53.450> on<00:01:53.690> market<00:01:54.380> signals<00:01:54.940> can<00:01:55.940> take<00:01:56.720> care 00:01:56.950 --> 00:01:56.960 align:start position:0% purely on market signals can take care 00:01:56.960 --> 00:01:58.450 align:start position:0% purely on market signals can take care of<00:01:57.020> their<00:01:57.350> own<00:01:57.590> interests<00:01:58.160> and<00:01:58.280> putting 00:01:58.450 --> 00:01:58.460 align:start position:0% of their own interests and putting 00:01:58.460 --> 00:02:00.130 align:start position:0% of their own interests and putting themselves<00:01:58.760> against<00:01:59.300> attackers<00:01:59.750> at<00:02:00.020> the 00:02:00.130 --> 00:02:00.140 align:start position:0% themselves against attackers at the 00:02:00.140 --> 00:02:10.060 align:start position:0% themselves against attackers at the course<00:02:00.380> and<00:02:00.530> force<00:02:00.770> because<00:02:03.250> and<00:02:07.540> so<00:02:08.890> the<00:02:09.890> most 00:02:10.060 --> 00:02:10.070 align:start position:0% course and force because and so the most 00:02:10.070 --> 00:02:12.160 align:start position:0% course and force because and so the most obvious<00:02:10.300> issues<00:02:11.300> such<00:02:11.510> a<00:02:11.540> system<00:02:11.900> has<00:02:12.050> to 00:02:12.160 --> 00:02:12.170 align:start position:0% obvious issues such a system has to 00:02:12.170 --> 00:02:17.490 align:start position:0% obvious issues such a system has to solve<00:02:12.410> is<00:02:13.130> that<00:02:13.540> in<00:02:14.540> a<00:02:14.690> peer-to-peer<00:02:15.260> network 00:02:17.490 --> 00:02:17.500 align:start position:0% 00:02:17.500 --> 00:02:20.199 align:start position:0% promises<00:02:18.500> are<00:02:18.650> nothing<00:02:19.010> forcible<00:02:19.730> so<00:02:19.910> anyone 00:02:20.199 --> 00:02:20.209 align:start position:0% promises are nothing forcible so anyone 00:02:20.209 --> 00:02:22.900 align:start position:0% promises are nothing forcible so anyone can<00:02:20.420> get<00:02:20.780> away<00:02:20.980> at<00:02:21.980> any<00:02:22.160> point<00:02:22.459> including 00:02:22.900 --> 00:02:22.910 align:start position:0% can get away at any point including 00:02:22.910 --> 00:02:25.900 align:start position:0% can get away at any point including server-side<00:02:23.720> after<00:02:24.080> receiving<00:02:24.709> payment<00:02:25.250> so 00:02:25.900 --> 00:02:25.910 align:start position:0% server-side after receiving payment so 00:02:25.910 --> 00:02:28.449 align:start position:0% server-side after receiving payment so we<00:02:26.150> can<00:02:26.810> have<00:02:27.080> some<00:02:27.620> kind<00:02:27.860> of<00:02:27.980> verification 00:02:28.449 --> 00:02:28.459 align:start position:0% we can have some kind of verification 00:02:28.459 --> 00:02:31.000 align:start position:0% we can have some kind of verification mechanism<00:02:29.209> and<00:02:29.420> then<00:02:29.780> in<00:02:30.260> this<00:02:30.470> case<00:02:30.530> in<00:02:30.920> this 00:02:31.000 --> 00:02:31.010 align:start position:0% mechanism and then in this case in this 00:02:31.010 --> 00:02:34.060 align:start position:0% mechanism and then in this case in this followed<00:02:31.370> this<00:02:32.150> will<00:02:32.390> look<00:02:32.540> like<00:02:32.780> so<00:02:33.680> servers 00:02:34.060 --> 00:02:34.070 align:start position:0% followed this will look like so servers 00:02:34.070 --> 00:02:36.340 align:start position:0% followed this will look like so servers have<00:02:34.310> to<00:02:34.489> first<00:02:34.970> provide<00:02:35.420> the<00:02:35.690> pre-service 00:02:36.340 --> 00:02:36.350 align:start position:0% have to first provide the pre-service 00:02:36.350 --> 00:02:39.850 align:start position:0% have to first provide the pre-service and<00:02:36.730> after<00:02:37.730> there's<00:02:38.660> a<00:02:38.780> high<00:02:39.019> demand<00:02:39.200> for<00:02:39.500> the 00:02:39.850 --> 00:02:39.860 align:start position:0% and after there's a high demand for the 00:02:39.860 --> 00:02:42.940 align:start position:0% and after there's a high demand for the pre-service<00:02:40.340> and<00:02:41.200> try<00:02:42.200> to<00:02:42.260> touch<00:02:42.560> the<00:02:42.590> server 00:02:42.940 --> 00:02:42.950 align:start position:0% pre-service and try to touch the server 00:02:42.950 --> 00:02:46.120 align:start position:0% pre-service and try to touch the server they<00:02:43.580> can<00:02:43.820> start<00:02:44.480> operating<00:02:45.200> the<00:02:45.470> money<00:02:45.680> in 00:02:46.120 --> 00:02:46.130 align:start position:0% they can start operating the money in 00:02:46.130 --> 00:03:22.819 align:start position:0% they can start operating the money in order<00:02:46.459> to 00:03:22.819 --> 00:03:22.829 align:start position:0% 00:03:22.829 --> 00:03:25.890 align:start position:0% also<00:03:23.829> the<00:03:24.040> market<00:03:24.579> mechanism<00:03:24.730> themselves<00:03:25.629> are 00:03:25.890 --> 00:03:25.900 align:start position:0% also the market mechanism themselves are 00:03:25.900 --> 00:03:29.330 align:start position:0% also the market mechanism themselves are time<00:03:26.409> dependent<00:03:26.440> and<00:03:27.329> what<00:03:28.329> works<00:03:28.810> on<00:03:28.959> a 00:03:29.330 --> 00:03:29.340 align:start position:0% time dependent and what works on a 00:03:29.340 --> 00:03:31.740 align:start position:0% time dependent and what works on a longer<00:03:30.340> time<00:03:30.549> scale<00:03:30.609> might<00:03:31.090> not<00:03:31.359> work<00:03:31.569> people 00:03:31.740 --> 00:03:31.750 align:start position:0% longer time scale might not work people 00:03:31.750 --> 00:03:33.899 align:start position:0% longer time scale might not work people evolve<00:03:32.170> the<00:03:32.349> short<00:03:32.590> of<00:03:32.769> time<00:03:32.980> still<00:03:33.310> simply 00:03:33.899 --> 00:03:33.909 align:start position:0% evolve the short of time still simply 00:03:33.909 --> 00:03:36.899 align:start position:0% evolve the short of time still simply because<00:03:34.180> the<00:03:34.389> information<00:03:35.079> that<00:03:35.859> actors<00:03:36.489> are 00:03:36.899 --> 00:03:36.909 align:start position:0% because the information that actors are 00:03:36.909 --> 00:03:39.119 align:start position:0% because the information that actors are trying<00:03:37.239> to<00:03:37.389> base<00:03:37.540> the<00:03:37.780> decision<00:03:37.870> stone<00:03:38.530> might 00:03:39.119 --> 00:03:39.129 align:start position:0% trying to base the decision stone might 00:03:39.129 --> 00:03:43.530 align:start position:0% trying to base the decision stone might need<00:03:40.090> some<00:03:40.329> time<00:03:40.720> to<00:03:41.049> become<00:03:41.379> a<00:03:41.560> reliable<00:03:42.540> like 00:03:43.530 --> 00:03:43.540 align:start position:0% need some time to become a reliable like 00:03:43.540 --> 00:03:46.679 align:start position:0% need some time to become a reliable like service<00:03:44.319> quality<00:03:44.739> age<00:03:44.980> and<00:03:45.689> responsibility 00:03:46.679 --> 00:03:46.689 align:start position:0% service quality age and responsibility 00:03:46.689 --> 00:03:50.280 align:start position:0% service quality age and responsibility stakes<00:03:47.040> and<00:03:48.689> service<00:03:49.689> difficulty 00:03:50.280 --> 00:03:50.290 align:start position:0% stakes and service difficulty 00:03:50.290 --> 00:03:52.319 align:start position:0% stakes and service difficulty measurements<00:03:50.829> are<00:03:51.160> very<00:03:51.190> nice<00:03:51.609> things<00:03:52.000> and 00:03:52.319 --> 00:03:52.329 align:start position:0% measurements are very nice things and 00:03:52.329 --> 00:03:54.629 align:start position:0% measurements are very nice things and you<00:03:52.870> just<00:03:52.989> have<00:03:53.680> to<00:03:53.709> collect<00:03:54.099> a<00:03:54.310> certain 00:03:54.629 --> 00:03:54.639 align:start position:0% you just have to collect a certain 00:03:54.639 --> 00:03:57.720 align:start position:0% you just have to collect a certain amount<00:03:54.819> of<00:03:55.060> data<00:03:55.599> in<00:03:55.930> order<00:03:56.049> to<00:03:56.260> able<00:03:57.010> to<00:03:57.250> make 00:03:57.720 --> 00:03:57.730 align:start position:0% amount of data in order to able to make 00:03:57.730 --> 00:04:01.830 align:start position:0% amount of data in order to able to make good<00:03:57.940> decisions<00:03:57.970> and<00:03:58.660> I<00:03:59.940> have<00:04:00.940> problems<00:04:01.660> in 00:04:01.830 --> 00:04:01.840 align:start position:0% good decisions and I have problems in 00:04:01.840 --> 00:04:04.259 align:start position:0% good decisions and I have problems in not<00:04:02.190> high-frequency<00:04:03.190> trading<00:04:03.790> which<00:04:04.090> I<00:04:04.209> do 00:04:04.259 --> 00:04:04.269 align:start position:0% not high-frequency trading which I do 00:04:04.269 --> 00:04:06.720 align:start position:0% not high-frequency trading which I do every<00:04:04.389> day<00:04:04.840> disconnect<00:04:05.560> from<00:04:05.680> any<00:04:06.010> market 00:04:06.720 --> 00:04:06.730 align:start position:0% every day disconnect from any market 00:04:06.730 --> 00:04:07.650 align:start position:0% every day disconnect from any market fundamentals 00:04:07.650 --> 00:04:07.660 align:start position:0% fundamentals 00:04:07.660 --> 00:04:10.680 align:start position:0% fundamentals stuff<00:04:08.350> that<00:04:08.380> he<00:04:08.680> provided<00:04:09.550> activity<00:04:10.150> bags<00:04:10.420> to 00:04:10.680 --> 00:04:10.690 align:start position:0% stuff that he provided activity bags to 00:04:10.690 --> 00:04:14.700 align:start position:0% stuff that he provided activity bags to price<00:04:10.990> fluctuations<00:04:11.800> so<00:04:12.480> this<00:04:13.480> would<00:04:13.710> also 00:04:14.700 --> 00:04:14.710 align:start position:0% price fluctuations so this would also 00:04:14.710 --> 00:04:17.160 align:start position:0% price fluctuations so this would also like<00:04:14.980> to<00:04:15.010> avoid<00:04:15.460> a<00:04:15.700> food<00:04:15.970> price<00:04:16.239> preparations 00:04:17.160 --> 00:04:17.170 align:start position:0% like to avoid a food price preparations 00:04:17.170 --> 00:04:19.170 align:start position:0% like to avoid a food price preparations because<00:04:17.580> surprises<00:04:18.580> I<00:04:18.700> believe<00:04:18.970> are 00:04:19.170 --> 00:04:19.180 align:start position:0% because surprises I believe are 00:04:19.180 --> 00:04:21.360 align:start position:0% because surprises I believe are practically<00:04:19.810> meaningless<00:04:20.500> on<00:04:20.800> a<00:04:20.980> net<00:04:21.100> short 00:04:21.360 --> 00:04:21.370 align:start position:0% practically meaningless on a net short 00:04:21.370 --> 00:04:25.560 align:start position:0% practically meaningless on a net short enough<00:04:21.670> time<00:04:21.910> scale<00:04:22.320> prestigious<00:04:23.320> and<00:04:23.740> so<00:04:24.570> in 00:04:25.560 --> 00:04:25.570 align:start position:0% enough time scale prestigious and so in 00:04:25.570 --> 00:04:27.840 align:start position:0% enough time scale prestigious and so in order<00:04:25.720> to<00:04:25.870> make<00:04:26.290> things<00:04:26.500> a<00:04:26.680> bit<00:04:26.860> more<00:04:27.070> stable 00:04:27.840 --> 00:04:27.850 align:start position:0% order to make things a bit more stable 00:04:27.850 --> 00:04:34.680 align:start position:0% order to make things a bit more stable and<00:04:29.520> predictable<00:04:32.250> in<00:04:33.250> this<00:04:33.370> talk<00:04:33.610> I<00:04:33.790> will<00:04:34.030> show 00:04:34.680 --> 00:04:34.690 align:start position:0% and predictable in this talk I will show 00:04:34.690 --> 00:04:37.590 align:start position:0% and predictable in this talk I will show you<00:04:34.750> how<00:04:34.960> the<00:04:35.140> server's<00:04:35.770> camera<00:04:36.280> but<00:04:37.240> I<00:04:37.270> happen 00:04:37.590 --> 00:04:37.600 align:start position:0% you how the server's camera but I happen 00:04:37.600 --> 00:04:40.470 align:start position:0% you how the server's camera but I happen to<00:04:37.720> be<00:04:37.870> to<00:04:38.460> allocating<00:04:39.460> their<00:04:40.090> serving 00:04:40.470 --> 00:04:40.480 align:start position:0% to be to allocating their serving 00:04:40.480 --> 00:04:43.830 align:start position:0% to be to allocating their serving capacity<00:04:41.050> and<00:04:41.320> how<00:04:41.920> science<00:04:42.370> can<00:04:42.700> do<00:04:43.600> load 00:04:43.830 --> 00:04:43.840 align:start position:0% capacity and how science can do load 00:04:43.840 --> 00:04:47.160 align:start position:0% capacity and how science can do load balancing<00:04:43.870> based<00:04:44.740> on<00:04:44.980> a<00:04:45.090> server<00:04:46.090> feedback<00:04:46.600> and 00:04:47.160 --> 00:04:47.170 align:start position:0% balancing based on a server feedback and 00:04:47.170 --> 00:04:52.650 align:start position:0% balancing based on a server feedback and also<00:04:47.470> the<00:04:47.770> longer<00:04:48.010> time<00:04:48.220> scale<00:04:49.440> can<00:04:51.660> evaluate 00:04:52.650 --> 00:04:52.660 align:start position:0% also the longer time scale can evaluate 00:04:52.660 --> 00:04:55.110 align:start position:0% also the longer time scale can evaluate server<00:04:53.170> performance<00:04:53.740> and<00:04:54.100> choose<00:04:54.550> the<00:04:54.790> best 00:04:55.110 --> 00:04:55.120 align:start position:0% server performance and choose the best 00:04:55.120 --> 00:04:56.900 align:start position:0% server performance and choose the best service<00:04:55.330> for<00:04:55.990> the<00:04:56.140> money 00:04:56.900 --> 00:04:56.910 align:start position:0% service for the money 00:04:56.910 --> 00:05:00.300 align:start position:0% service for the money so<00:04:57.910> for<00:04:58.150> toaster<00:04:58.690> let's<00:04:59.200> look<00:04:59.530> at<00:04:59.710> how<00:04:59.950> these 00:05:00.300 --> 00:05:00.310 align:start position:0% so for toaster let's look at how these 00:05:00.310 --> 00:05:04.260 align:start position:0% so for toaster let's look at how these servers<00:05:00.790> and<00:05:02.100> manage<00:05:03.100> their<00:05:03.340> own<00:05:03.370> serving 00:05:04.260 --> 00:05:04.270 align:start position:0% servers and manage their own serving 00:05:04.270 --> 00:05:13.490 align:start position:0% servers and manage their own serving capacity<00:05:04.840> and<00:05:05.050> the<00:05:05.310> response<00:05:06.310> times<00:05:07.740> servers 00:05:13.490 --> 00:05:13.500 align:start position:0% 00:05:13.500 --> 00:05:17.490 align:start position:0% so<00:05:14.500> the<00:05:15.090> server<00:05:16.090> still<00:05:16.330> have<00:05:16.870> their<00:05:17.020> own<00:05:17.140> token 00:05:17.490 --> 00:05:17.500 align:start position:0% so the server still have their own token 00:05:17.500 --> 00:05:20.910 align:start position:0% so the server still have their own token accounting<00:05:18.070> and<00:05:19.140> so<00:05:20.140> they<00:05:20.260> they<00:05:20.470> have<00:05:20.620> been<00:05:20.740> of 00:05:20.910 --> 00:05:20.920 align:start position:0% accounting and so they they have been of 00:05:20.920 --> 00:05:23.730 align:start position:0% accounting and so they they have been of service<00:05:21.100> tokens<00:05:21.610> which<00:05:22.180> are<00:05:22.750> meant<00:05:23.290> to<00:05:23.410> be 00:05:23.730 --> 00:05:23.740 align:start position:0% service tokens which are meant to be 00:05:23.740 --> 00:05:26.869 align:start position:0% service tokens which are meant to be based<00:05:23.980> on<00:05:24.420> the<00:05:25.420> actual<00:05:25.600> physical<00:05:26.140> serving 00:05:26.869 --> 00:05:26.879 align:start position:0% based on the actual physical serving 00:05:26.879 --> 00:05:30.379 align:start position:0% based on the actual physical serving request<00:05:27.509> and<00:05:28.580> they<00:05:29.580> should<00:05:29.729> be<00:05:29.849> unrelated<00:05:30.179> to 00:05:30.379 --> 00:05:30.389 align:start position:0% request and they should be unrelated to 00:05:30.389 --> 00:05:33.489 align:start position:0% request and they should be unrelated to any<00:05:30.659> market<00:05:31.229> the<00:05:31.409> prices<00:05:31.770> or<00:05:32.309> conditions<00:05:32.909> and 00:05:33.489 --> 00:05:33.499 align:start position:0% any market the prices or conditions and 00:05:33.499 --> 00:05:36.139 align:start position:0% any market the prices or conditions and the<00:05:34.499> universe<00:05:34.979> the<00:05:35.249> costs<00:05:35.789> are<00:05:35.879> always 00:05:36.139 --> 00:05:36.149 align:start position:0% the universe the costs are always 00:05:36.149 --> 00:05:37.939 align:start position:0% the universe the costs are always dominated<00:05:36.719> in<00:05:36.809> the<00:05:36.929> service<00:05:37.259> topaz<00:05:37.649> and 00:05:37.939 --> 00:05:37.949 align:start position:0% dominated in the service topaz and 00:05:37.949 --> 00:05:40.239 align:start position:0% dominated in the service topaz and basically<00:05:38.699> usually<00:05:38.939> the<00:05:39.300> server's<00:05:39.689> can 00:05:40.239 --> 00:05:40.249 align:start position:0% basically usually the server's can 00:05:40.249 --> 00:05:43.879 align:start position:0% basically usually the server's can freely<00:05:41.249> decide<00:05:41.520> is<00:05:41.939> the<00:05:42.179> cost<00:05:43.110> of<00:05:43.259> any 00:05:43.879 --> 00:05:43.889 align:start position:0% freely decide is the cost of any 00:05:43.889 --> 00:05:45.379 align:start position:0% freely decide is the cost of any individual<00:05:44.369> request<00:05:44.759> but<00:05:45.119> there<00:05:45.270> are 00:05:45.379 --> 00:05:45.389 align:start position:0% individual request but there are 00:05:45.389 --> 00:05:48.889 align:start position:0% individual request but there are previously<00:05:46.379> announced<00:05:46.649> the<00:05:47.039> maximum<00:05:47.729> cost<00:05:48.659> of 00:05:48.889 --> 00:05:48.899 align:start position:0% previously announced the maximum cost of 00:05:48.899 --> 00:05:49.609 align:start position:0% previously announced the maximum cost of is<00:05:48.990> electric 00:05:49.609 --> 00:05:49.619 align:start position:0% is electric 00:05:49.619 --> 00:05:52.850 align:start position:0% is electric Rufus<00:05:49.979> time<00:05:50.219> and<00:05:50.629> we<00:05:51.629> also<00:05:51.749> defined<00:05:52.229> capacity 00:05:52.850 --> 00:05:52.860 align:start position:0% Rufus time and we also defined capacity 00:05:52.860 --> 00:05:56.239 align:start position:0% Rufus time and we also defined capacity as<00:05:53.039> a<00:05:53.069> service<00:05:53.819> to<00:05:53.969> answer<00:05:54.449> spendable<00:05:55.409> a<00:05:55.559> time 00:05:56.239 --> 00:05:56.249 align:start position:0% as a service to answer spendable a time 00:05:56.249 --> 00:05:58.309 align:start position:0% as a service to answer spendable a time unit<00:05:56.490> and<00:05:56.789> we<00:05:57.059> assign<00:05:57.449> a<00:05:57.509> capacity<00:05:58.080> to<00:05:58.110> each 00:05:58.309 --> 00:05:58.319 align:start position:0% unit and we assign a capacity to each 00:05:58.319 --> 00:06:00.139 align:start position:0% unit and we assign a capacity to each client<00:05:58.559> which<00:05:58.979> basically<00:05:59.339> means<00:05:59.610> a<00:05:59.819> request 00:06:00.139 --> 00:06:00.149 align:start position:0% client which basically means a request 00:06:00.149 --> 00:06:02.059 align:start position:0% client which basically means a request rate<00:06:00.330> limiting<00:06:00.809> and<00:06:00.959> we<00:06:01.349> also<00:06:01.469> set<00:06:01.800> an<00:06:01.949> upper 00:06:02.059 --> 00:06:02.069 align:start position:0% rate limiting and we also set an upper 00:06:02.069 --> 00:06:05.329 align:start position:0% rate limiting and we also set an upper limit<00:06:02.369> on<00:06:02.639> the<00:06:02.959> total<00:06:03.959> capacity<00:06:04.709> of<00:06:04.740> all 00:06:05.329 --> 00:06:05.339 align:start position:0% limit on the total capacity of all 00:06:05.339 --> 00:06:08.839 align:start position:0% limit on the total capacity of all connected<00:06:05.819> clients<00:06:06.360> and<00:06:07.279> this<00:06:08.279> is<00:06:08.459> the 00:06:08.839 --> 00:06:08.849 align:start position:0% connected clients and this is the 00:06:08.849 --> 00:06:11.209 align:start position:0% connected clients and this is the drinkie<00:06:09.240> goal<00:06:09.389> of<00:06:09.509> this<00:06:09.689> is<00:06:09.869> to<00:06:09.979> avoid<00:06:10.979> the 00:06:11.209 --> 00:06:11.219 align:start position:0% drinkie goal of this is to avoid the 00:06:11.219 --> 00:06:14.239 align:start position:0% drinkie goal of this is to avoid the transient<00:06:11.699> overlords<00:06:12.300> by<00:06:13.169> which<00:06:13.349> I'm<00:06:13.559> in<00:06:13.740> a 00:06:14.239 --> 00:06:14.249 align:start position:0% transient overlords by which I'm in a 00:06:14.249 --> 00:06:15.589 align:start position:0% transient overlords by which I'm in a situation<00:06:14.639> where<00:06:15.119> we<00:06:15.209> have<00:06:15.330> a<00:06:15.360> lot<00:06:15.569> of 00:06:15.589 --> 00:06:15.599 align:start position:0% situation where we have a lot of 00:06:15.599 --> 00:06:17.719 align:start position:0% situation where we have a lot of requests<00:06:16.050> in<00:06:16.649> the<00:06:16.709> same<00:06:16.979> time<00:06:17.249> and<00:06:17.519> the 00:06:17.719 --> 00:06:17.729 align:start position:0% requests in the same time and the 00:06:17.729 --> 00:06:20.629 align:start position:0% requests in the same time and the response<00:06:18.389> time<00:06:18.569> start<00:06:18.959> to<00:06:19.249> rise<00:06:20.249> very<00:06:20.519> quickly 00:06:20.629 --> 00:06:20.639 align:start position:0% response time start to rise very quickly 00:06:20.639 --> 00:06:24.619 align:start position:0% response time start to rise very quickly and<00:06:21.289> so<00:06:22.289> maybe<00:06:22.699> set<00:06:23.699> up<00:06:23.729> some<00:06:23.999> criteria<00:06:24.569> for 00:06:24.619 --> 00:06:24.629 align:start position:0% and so maybe set up some criteria for 00:06:24.629 --> 00:06:28.939 align:start position:0% and so maybe set up some criteria for detecting<00:06:25.319> this<00:06:25.439> and<00:06:26.059> we<00:06:27.059> can<00:06:27.709> maybe<00:06:28.709> not 00:06:28.939 --> 00:06:28.949 align:start position:0% detecting this and we can maybe not 00:06:28.949 --> 00:06:30.759 align:start position:0% detecting this and we can maybe not always<00:06:29.159> avoid<00:06:29.490> this<00:06:29.729> part<00:06:29.939> they<00:06:30.119> reduce<00:06:30.419> its 00:06:30.759 --> 00:06:30.769 align:start position:0% always avoid this part they reduce its 00:06:30.769 --> 00:06:34.309 align:start position:0% always avoid this part they reduce its frequency<00:06:31.769> of<00:06:31.949> its<00:06:32.539> consistently<00:06:33.539> adjusting 00:06:34.309 --> 00:06:34.319 align:start position:0% frequency of its consistently adjusting 00:06:34.319 --> 00:06:39.769 align:start position:0% frequency of its consistently adjusting the<00:06:34.559> total<00:06:35.369> capacity<00:06:36.229> llamas<00:06:38.180> so<00:06:39.180> the<00:06:39.419> real 00:06:39.769 --> 00:06:39.779 align:start position:0% the total capacity llamas so the real 00:06:39.779 --> 00:06:42.829 align:start position:0% the total capacity llamas so the real frustration<00:06:40.139> within<00:06:40.699> method<00:06:41.699> of<00:06:41.819> attack<00:06:42.689> in 00:06:42.829 --> 00:06:42.839 align:start position:0% frustration within method of attack in 00:06:42.839 --> 00:06:45.859 align:start position:0% frustration within method of attack in ESS<00:06:43.319> for<00:06:43.529> the<00:06:43.800> price<00:06:44.009> side<00:06:44.339> of<00:06:44.490> control<00:06:45.089> and<00:06:45.329> as 00:06:45.859 --> 00:06:45.869 align:start position:0% ESS for the price side of control and as 00:06:45.869 --> 00:06:48.490 align:start position:0% ESS for the price side of control and as I<00:06:45.959> said<00:06:46.099> it's<00:06:47.099> based<00:06:47.430> on<00:06:47.550> the 00:06:48.490 --> 00:06:48.500 align:start position:0% I said it's based on the 00:06:48.500 --> 00:06:51.140 align:start position:0% I said it's based on the capacity<00:06:49.500> to<00:06:49.680> each<00:06:49.979> client<00:06:50.520> that<00:06:50.759> also 00:06:51.140 --> 00:06:51.150 align:start position:0% capacity to each client that also 00:06:51.150 --> 00:06:53.839 align:start position:0% capacity to each client that also requests<00:06:51.569> butter<00:06:51.990> and<00:06:52.440> the<00:06:52.620> server<00:06:52.860> to<00:06:53.580> assist 00:06:53.839 --> 00:06:53.849 align:start position:0% requests butter and the server to assist 00:06:53.849 --> 00:06:56.869 align:start position:0% requests butter and the server to assist request<00:06:54.300> it<00:06:54.479> can<00:06:55.139> remove<00:06:55.680> the<00:06:55.919> cost<00:06:56.639> of<00:06:56.789> the 00:06:56.869 --> 00:06:56.879 align:start position:0% request it can remove the cost of the 00:06:56.879 --> 00:06:58.850 align:start position:0% request it can remove the cost of the request<00:06:57.210> from<00:06:57.330> the<00:06:57.509> buffer<00:06:57.840> and<00:06:58.139> also<00:06:58.710> reach 00:06:58.850 --> 00:06:58.860 align:start position:0% request from the buffer and also reach 00:06:58.860 --> 00:06:59.960 align:start position:0% request from the buffer and also reach out<00:06:59.009> to<00:06:59.069> buffer<00:06:59.460> at<00:06:59.550> the<00:06:59.669> rate<00:06:59.789> that's 00:06:59.960 --> 00:06:59.970 align:start position:0% out to buffer at the rate that's 00:06:59.970 --> 00:07:02.589 align:start position:0% out to buffer at the rate that's proportional<00:07:00.330> to<00:07:00.720> the<00:07:00.840> capacity<00:07:01.409> and<00:07:01.650> in 00:07:02.589 --> 00:07:02.599 align:start position:0% proportional to the capacity and in 00:07:02.599 --> 00:07:05.860 align:start position:0% proportional to the capacity and in every<00:07:03.599> very<00:07:04.050> bind<00:07:04.349> and<00:07:04.650> it<00:07:04.830> also<00:07:05.069> includes<00:07:05.550> the 00:07:05.860 --> 00:07:05.870 align:start position:0% every very bind and it also includes the 00:07:05.870 --> 00:07:10.010 align:start position:0% every very bind and it also includes the interpreter<00:07:06.870> tables<00:07:07.800> and<00:07:08.479> this<00:07:09.479> is<00:07:09.659> what<00:07:09.870> the 00:07:10.010 --> 00:07:10.020 align:start position:0% interpreter tables and this is what the 00:07:10.020 --> 00:07:12.230 align:start position:0% interpreter tables and this is what the clients<00:07:10.650> can<00:07:10.770> use<00:07:11.009> as<00:07:11.310> a<00:07:11.400> feedback<00:07:11.819> for<00:07:12.120> know 00:07:12.230 --> 00:07:12.240 align:start position:0% clients can use as a feedback for know 00:07:12.240 --> 00:07:13.820 align:start position:0% clients can use as a feedback for know that<00:07:12.449> I'm<00:07:12.539> saying<00:07:12.870> because<00:07:13.319> if<00:07:13.530> they<00:07:13.650> have 00:07:13.820 --> 00:07:13.830 align:start position:0% that I'm saying because if they have 00:07:13.830 --> 00:07:16.369 align:start position:0% that I'm saying because if they have multiple<00:07:14.270> server<00:07:15.270> connections<00:07:15.780> I<00:07:15.930> can<00:07:16.110> always 00:07:16.369 --> 00:07:16.379 align:start position:0% multiple server connections I can always 00:07:16.379 --> 00:07:18.619 align:start position:0% multiple server connections I can always send<00:07:16.560> a<00:07:16.650> text<00:07:16.830> request<00:07:17.280> to<00:07:17.699> a<00:07:17.729> server<00:07:17.819> but<00:07:18.360> it 00:07:18.619 --> 00:07:18.629 align:start position:0% send a text request to a server but it 00:07:18.629 --> 00:07:24.740 align:start position:0% send a text request to a server but it may<00:07:18.930> have<00:07:19.110> the<00:07:19.319> best<00:07:20.009> value<00:07:21.500> and<00:07:23.539> yeah<00:07:24.539> now<00:07:24.719> a 00:07:24.740 --> 00:07:24.750 align:start position:0% may have the best value and yeah now a 00:07:24.750 --> 00:07:29.420 align:start position:0% may have the best value and yeah now a few<00:07:25.319> words<00:07:25.440> about<00:07:25.620> how<00:07:27.259> service<00:07:28.259> tokens<00:07:29.219> are 00:07:29.420 --> 00:07:29.430 align:start position:0% few words about how service tokens are 00:07:29.430 --> 00:07:33.529 align:start position:0% few words about how service tokens are being<00:07:29.610> so<00:07:29.879> so<00:07:30.650> so<00:07:31.669> basically<00:07:32.669> we<00:07:32.849> belong<00:07:33.300> to<00:07:33.509> a 00:07:33.529 --> 00:07:33.539 align:start position:0% being so so so basically we belong to a 00:07:33.539 --> 00:07:36.770 align:start position:0% being so so so basically we belong to a service<00:07:33.900> to<00:07:34.020> be<00:07:34.139> able<00:07:34.409> to<00:07:35.210> sell<00:07:36.210> some<00:07:36.539> of<00:07:36.569> them 00:07:36.770 --> 00:07:36.780 align:start position:0% service to be able to sell some of them 00:07:36.780 --> 00:07:39.050 align:start position:0% service to be able to sell some of them they<00:07:36.990> have<00:07:37.020> tokens<00:07:37.469> in<00:07:37.800> advance<00:07:38.129> but<00:07:38.550> not<00:07:38.879> too 00:07:39.050 --> 00:07:39.060 align:start position:0% they have tokens in advance but not too 00:07:39.060 --> 00:07:43.249 align:start position:0% they have tokens in advance but not too many<00:07:39.150> of<00:07:39.300> them<00:07:39.629> because<00:07:40.229> the<00:07:41.930> spending<00:07:42.930> the 00:07:43.249 --> 00:07:43.259 align:start position:0% many of them because the spending the 00:07:43.259 --> 00:07:45.140 align:start position:0% many of them because the spending the selling<00:07:43.710> rate<00:07:43.889> of<00:07:44.069> the<00:07:44.280> tokens<00:07:44.849> it's<00:07:45.000> also 00:07:45.140 --> 00:07:45.150 align:start position:0% selling rate of the tokens it's also 00:07:45.150 --> 00:07:47.809 align:start position:0% selling rate of the tokens it's also limited<00:07:45.659> and<00:07:45.930> it<00:07:46.919> is<00:07:47.099> always<00:07:47.250> the<00:07:47.460> service 00:07:47.809 --> 00:07:47.819 align:start position:0% limited and it is always the service 00:07:47.819 --> 00:07:51.649 align:start position:0% limited and it is always the service interested<00:07:48.530> in<00:07:49.530> the<00:07:49.949> answer<00:07:50.129> there<00:07:50.659> stability 00:07:51.649 --> 00:07:51.659 align:start position:0% interested in the answer there stability 00:07:51.659 --> 00:07:53.899 align:start position:0% interested in the answer there stability of<00:07:51.870> the<00:07:52.529> consciousness<00:07:52.889> power<00:07:53.219> of<00:07:53.610> its<00:07:53.819> own 00:07:53.899 --> 00:07:53.909 align:start position:0% of the consciousness power of its own 00:07:53.909 --> 00:07:56.200 align:start position:0% of the consciousness power of its own organs<00:07:54.389> because<00:07:54.990> as<00:07:55.349> we<00:07:55.500> will<00:07:55.620> see<00:07:55.800> later<00:07:55.830> that 00:07:56.200 --> 00:07:56.210 align:start position:0% organs because as we will see later that 00:07:56.210 --> 00:07:59.209 align:start position:0% organs because as we will see later that the<00:07:57.210> clients<00:07:57.599> will<00:07:57.810> pay<00:07:58.289> attention<00:07:58.650> to<00:07:58.979> this 00:07:59.209 --> 00:07:59.219 align:start position:0% the clients will pay attention to this 00:07:59.219 --> 00:08:02.510 align:start position:0% the clients will pay attention to this and<00:07:59.490> and<00:08:00.000> the<00:08:00.960> service<00:08:01.349> will<00:08:01.560> do<00:08:02.279> the 00:08:02.510 --> 00:08:02.520 align:start position:0% and and the service will do the 00:08:02.520 --> 00:08:06.709 align:start position:0% and and the service will do the reputation<00:08:02.789> it<00:08:03.710> so<00:08:04.710> what<00:08:05.699> is<00:08:05.880> a<00:08:06.240> service 00:08:06.709 --> 00:08:06.719 align:start position:0% reputation it so what is a service 00:08:06.719 --> 00:08:09.469 align:start position:0% reputation it so what is a service should<00:08:07.199> I<00:08:07.319> do<00:08:07.500> to<00:08:07.590> do<00:08:07.830> is<00:08:08.069> limit<00:08:08.699> the<00:08:09.060> total 00:08:09.469 --> 00:08:09.479 align:start position:0% should I do to do is limit the total 00:08:09.479 --> 00:08:12.700 align:start position:0% should I do to do is limit the total outstanding<00:08:09.719> about<00:08:10.349> its<00:08:11.099> service<00:08:11.520> to<00:08:11.550> ants<00:08:11.880> by 00:08:12.700 --> 00:08:12.710 align:start position:0% outstanding about its service to ants by 00:08:12.710 --> 00:08:15.769 align:start position:0% outstanding about its service to ants by controlling<00:08:13.710> the<00:08:13.979> selling<00:08:14.940> price<00:08:15.180> of<00:08:15.210> tokens 00:08:15.769 --> 00:08:15.779 align:start position:0% controlling the selling price of tokens 00:08:15.779 --> 00:08:18.100 align:start position:0% controlling the selling price of tokens so<00:08:16.440> there's<00:08:16.650> a<00:08:16.710> base<00:08:16.889> price<00:08:17.069> and 00:08:18.100 --> 00:08:18.110 align:start position:0% so there's a base price and 00:08:18.110 --> 00:08:21.220 align:start position:0% so there's a base price and as<00:08:18.170> issues<00:08:19.040> Morimoto<00:08:19.670> castle<00:08:20.030> can<00:08:20.240> arise<00:08:21.020> of 00:08:21.220 --> 00:08:21.230 align:start position:0% as issues Morimoto castle can arise of 00:08:21.230 --> 00:08:24.070 align:start position:0% as issues Morimoto castle can arise of the<00:08:21.410> total<00:08:21.800> price<00:08:22.120> if<00:08:23.120> we<00:08:23.360> are<00:08:23.480> limiting<00:08:24.050> the 00:08:24.070 --> 00:08:24.080 align:start position:0% the total price if we are limiting the 00:08:24.080 --> 00:08:26.760 align:start position:0% the total price if we are limiting the amount<00:08:24.740> of<00:08:25.010> tokens<00:08:25.370> we<00:08:25.520> should<00:08:25.670> also<00:08:25.820> enforce 00:08:26.760 --> 00:08:26.770 align:start position:0% amount of tokens we should also enforce 00:08:26.770 --> 00:08:29.680 align:start position:0% amount of tokens we should also enforce spending<00:08:27.770> of<00:08:27.950> little<00:08:28.400> pants<00:08:28.730> by<00:08:29.180> sending<00:08:29.540> an 00:08:29.680 --> 00:08:29.690 align:start position:0% spending of little pants by sending an 00:08:29.690 --> 00:08:31.810 align:start position:0% spending of little pants by sending an expiration<00:08:30.140> time<00:08:30.530> on<00:08:30.710> them<00:08:30.920> or<00:08:31.160> by<00:08:31.610> making 00:08:31.810 --> 00:08:31.820 align:start position:0% expiration time on them or by making 00:08:31.820 --> 00:08:34.150 align:start position:0% expiration time on them or by making them<00:08:32.180> inflationary<00:08:32.810> was<00:08:33.140> some<00:08:33.560> combination 00:08:34.150 --> 00:08:34.160 align:start position:0% them inflationary was some combination 00:08:34.160 --> 00:08:37.150 align:start position:0% them inflationary was some combination of<00:08:34.220> these<00:08:34.690> and<00:08:35.690> this<00:08:36.020> was<00:08:36.200> important<00:08:36.740> mention 00:08:37.150 --> 00:08:37.160 align:start position:0% of these and this was important mention 00:08:37.160 --> 00:08:39.790 align:start position:0% of these and this was important mention here<00:08:37.400> that<00:08:37.690> whenever<00:08:38.690> a<00:08:38.840> currency<00:08:39.470> transfer 00:08:39.790 --> 00:08:39.800 align:start position:0% here that whenever a currency transfer 00:08:39.800 --> 00:08:42.070 align:start position:0% here that whenever a currency transfer is<00:08:39.980> accepted<00:08:40.790> by<00:08:40.910> the<00:08:40.940> server<00:08:41.300> it's<00:08:41.810> not 00:08:42.070 --> 00:08:42.080 align:start position:0% is accepted by the server it's not 00:08:42.080 --> 00:08:44.170 align:start position:0% is accepted by the server it's not automatically<00:08:42.800> converted<00:08:43.700> to<00:08:43.790> service 00:08:44.170 --> 00:08:44.180 align:start position:0% automatically converted to service 00:08:44.180 --> 00:08:44.740 align:start position:0% automatically converted to service tokens 00:08:44.740 --> 00:08:44.750 align:start position:0% tokens 00:08:44.750 --> 00:08:46.630 align:start position:0% tokens that's<00:08:45.200> something<00:08:45.590> the<00:08:45.740> client<00:08:46.250> has<00:08:46.430> to 00:08:46.630 --> 00:08:46.640 align:start position:0% that's something the client has to 00:08:46.640 --> 00:08:50.350 align:start position:0% that's something the client has to explicitly<00:08:47.060> explicitly<00:08:48.050> initiate<00:08:48.590> and<00:08:49.360> and 00:08:50.350 --> 00:08:50.360 align:start position:0% explicitly explicitly initiate and and 00:08:50.360 --> 00:08:53.050 align:start position:0% explicitly explicitly initiate and and this<00:08:51.050> is<00:08:51.200> also<00:08:51.410> when<00:08:51.770> the<00:08:51.980> expiration<00:08:52.490> starts 00:08:53.050 --> 00:08:53.060 align:start position:0% this is also when the expiration starts 00:08:53.060 --> 00:08:56.580 align:start position:0% this is also when the expiration starts to<00:08:53.180> Kingdom<00:08:53.600> so<00:08:53.990> it's<00:08:54.740> always<00:08:55.340> optional<00:08:56.030> to 00:08:56.580 --> 00:08:56.590 align:start position:0% to Kingdom so it's always optional to 00:08:56.590 --> 00:08:59.800 align:start position:0% to Kingdom so it's always optional to buy<00:08:57.590> a<00:08:58.000> significant<00:08:59.000> amount<00:08:59.330> of<00:08:59.510> service 00:08:59.800 --> 00:08:59.810 align:start position:0% buy a significant amount of service 00:08:59.810 --> 00:09:01.840 align:start position:0% buy a significant amount of service tokens<00:09:00.140> in<00:09:00.320> advance<00:09:00.650> that's<00:09:01.310> an<00:09:01.430> option<00:09:01.730> for 00:09:01.840 --> 00:09:01.850 align:start position:0% tokens in advance that's an option for 00:09:01.850 --> 00:09:03.910 align:start position:0% tokens in advance that's an option for clients<00:09:02.210> that<00:09:02.240> has<00:09:02.510> a<00:09:02.540> national<00:09:03.470> course<00:09:03.710> but 00:09:03.910 --> 00:09:03.920 align:start position:0% clients that has a national course but 00:09:03.920 --> 00:09:06.130 align:start position:0% clients that has a national course but it<00:09:04.040> also<00:09:04.190> has<00:09:04.430> a<00:09:04.460> benefit<00:09:04.910> one<00:09:05.630> benefit<00:09:05.990> is 00:09:06.130 --> 00:09:06.140 align:start position:0% it also has a benefit one benefit is 00:09:06.140 --> 00:09:08.590 align:start position:0% it also has a benefit one benefit is that<00:09:06.200> they<00:09:06.500> eat<00:09:06.650> or<00:09:06.980> is<00:09:07.130> a<00:09:07.160> further<00:09:08.060> price<00:09:08.360> to 00:09:08.590 --> 00:09:08.600 align:start position:0% that they eat or is a further price to 00:09:08.600 --> 00:09:10.540 align:start position:0% that they eat or is a further price to fluctuations<00:09:09.170> of<00:09:09.500> even<00:09:09.860> more<00:09:09.950> importantly 00:09:10.540 --> 00:09:10.550 align:start position:0% fluctuations of even more importantly 00:09:10.550 --> 00:09:12.970 align:start position:0% fluctuations of even more importantly that<00:09:11.150> this<00:09:11.390> is<00:09:11.540> a<00:09:11.570> commitment<00:09:12.170> to<00:09:12.440> spending 00:09:12.970 --> 00:09:12.980 align:start position:0% that this is a commitment to spending 00:09:12.980 --> 00:09:15.220 align:start position:0% that this is a commitment to spending the<00:09:13.150> tokens<00:09:14.150> and<00:09:14.300> using<00:09:14.600> the<00:09:14.690> service<00:09:14.990> in<00:09:15.140> the 00:09:15.220 --> 00:09:15.230 align:start position:0% the tokens and using the service in the 00:09:15.230 --> 00:09:17.770 align:start position:0% the tokens and using the service in the near<00:09:15.380> future<00:09:15.590> and<00:09:16.070> the<00:09:16.700> server<00:09:17.120> this<00:09:17.600> is<00:09:17.750> a 00:09:17.770 --> 00:09:17.780 align:start position:0% near future and the server this is a 00:09:17.780 --> 00:09:19.540 align:start position:0% near future and the server this is a very<00:09:17.990> valuable<00:09:18.230> information<00:09:18.770> for<00:09:19.220> the<00:09:19.340> server 00:09:19.540 --> 00:09:19.550 align:start position:0% very valuable information for the server 00:09:19.550 --> 00:09:21.430 align:start position:0% very valuable information for the server and<00:09:19.790> the<00:09:19.910> server<00:09:19.940> will<00:09:20.450> deliver<00:09:20.870> this<00:09:21.080> by<00:09:21.380> it 00:09:21.430 --> 00:09:21.440 align:start position:0% and the server will deliver this by it 00:09:21.440 --> 00:09:22.840 align:start position:0% and the server will deliver this by it not<00:09:22.070> being<00:09:22.310> they're<00:09:22.550> more<00:09:22.760> stable 00:09:22.840 --> 00:09:22.850 align:start position:0% not being they're more stable 00:09:22.850 --> 00:09:31.630 align:start position:0% not being they're more stable connections<00:09:26.560> of<00:09:27.560> how<00:09:27.710> it's<00:09:27.920> done<00:09:28.160> so<00:09:29.710> so<00:09:30.710> we 00:09:31.630 --> 00:09:31.640 align:start position:0% connections of how it's done so so we 00:09:31.640 --> 00:09:34.570 align:start position:0% connections of how it's done so so we are<00:09:31.730> going<00:09:31.940> to<00:09:32.600> the<00:09:33.040> client<00:09:34.040> connection 00:09:34.570 --> 00:09:34.580 align:start position:0% are going to the client connection 00:09:34.580 --> 00:09:41.410 align:start position:0% are going to the client connection priority<00:09:35.180> model<00:09:38.170> the<00:09:39.170> service<00:09:39.830> obviously<00:09:40.460> the 00:09:41.410 --> 00:09:41.420 align:start position:0% priority model the service obviously the 00:09:41.420 --> 00:09:44.260 align:start position:0% priority model the service obviously the number<00:09:41.720> of<00:09:41.840> clients<00:09:42.650> to<00:09:42.920> be<00:09:43.010> connected<00:09:43.430> cycle 00:09:44.260 --> 00:09:44.270 align:start position:0% number of clients to be connected cycle 00:09:44.270 --> 00:09:46.630 align:start position:0% number of clients to be connected cycle there<00:09:44.450> is<00:09:44.480> limited<00:09:45.230> so<00:09:45.410> Victor<00:09:45.770> have<00:09:46.280> some<00:09:46.460> had 00:09:46.630 --> 00:09:46.640 align:start position:0% there is limited so Victor have some had 00:09:46.640 --> 00:09:48.820 align:start position:0% there is limited so Victor have some had priorities<00:09:47.330> and<00:09:47.510> the<00:09:47.690> private<00:09:48.110> dividing 00:09:48.820 --> 00:09:48.830 align:start position:0% priorities and the private dividing 00:09:48.830 --> 00:09:52.540 align:start position:0% priorities and the private dividing using<00:09:49.490> this<00:09:49.580> model<00:09:49.970> is<00:09:50.300> a<00:09:50.540> token<00:09:51.380> balance<00:09:51.890> / 00:09:52.540 --> 00:09:52.550 align:start position:0% using this model is a token balance / 00:09:52.550 --> 00:09:56.680 align:start position:0% using this model is a token balance / requested<00:09:53.120> capacity<00:09:53.690> and<00:09:55.120> I'm<00:09:56.120> not<00:09:56.360> going<00:09:56.570> to 00:09:56.680 --> 00:09:56.690 align:start position:0% requested capacity and I'm not going to 00:09:56.690 --> 00:09:58.389 align:start position:0% requested capacity and I'm not going to explain<00:09:56.899> missing 00:09:58.389 --> 00:09:58.399 align:start position:0% explain missing 00:09:58.399 --> 00:10:00.550 align:start position:0% explain missing the<00:09:58.730> nice<00:09:58.880> property<00:09:59.480> of<00:09:59.510> this<00:09:59.720> is<00:10:00.019> that<00:10:00.230> it 00:10:00.550 --> 00:10:00.560 align:start position:0% the nice property of this is that it 00:10:00.560 --> 00:10:03.610 align:start position:0% the nice property of this is that it rewards<00:10:01.089> commitment<00:10:02.089> commitment<00:10:02.420> so<00:10:03.350> the 00:10:03.610 --> 00:10:03.620 align:start position:0% rewards commitment commitment so the 00:10:03.620 --> 00:10:06.100 align:start position:0% rewards commitment commitment so the client<00:10:04.010> promised<00:10:04.279> to<00:10:04.540> use<00:10:05.540> the<00:10:05.690> service<00:10:05.990> in 00:10:06.100 --> 00:10:06.110 align:start position:0% client promised to use the service in 00:10:06.110 --> 00:10:07.870 align:start position:0% client promised to use the service in the<00:10:06.230> near<00:10:06.380> future<00:10:06.560> that<00:10:06.800> the<00:10:07.070> server<00:10:07.279> is<00:10:07.519> to 00:10:07.870 --> 00:10:07.880 align:start position:0% the near future that the server is to 00:10:07.880 --> 00:10:10.240 align:start position:0% the near future that the server is to let<00:10:08.029> the<00:10:08.149> client<00:10:08.329> use<00:10:08.990> this<00:10:09.170> service<00:10:10.010> in<00:10:10.130> the 00:10:10.240 --> 00:10:10.250 align:start position:0% let the client use this service in the 00:10:10.250 --> 00:10:13.690 align:start position:0% let the client use this service in the near<00:10:10.370> future<00:10:10.579> and<00:10:11.060> another<00:10:11.870> nice<00:10:12.410> property<00:10:12.700> is 00:10:13.690 --> 00:10:13.700 align:start position:0% near future and another nice property is 00:10:13.700 --> 00:10:16.840 align:start position:0% near future and another nice property is that<00:10:14.029> it<00:10:14.690> lets<00:10:14.930> us<00:10:15.680> integrate<00:10:16.279> the<00:10:16.550> free 00:10:16.840 --> 00:10:16.850 align:start position:0% that it lets us integrate the free 00:10:16.850 --> 00:10:19.509 align:start position:0% that it lets us integrate the free service<00:10:17.269> very<00:10:17.510> nicely<00:10:18.170> and<00:10:18.529> smoothly<00:10:19.160> into 00:10:19.509 --> 00:10:19.519 align:start position:0% service very nicely and smoothly into 00:10:19.519 --> 00:10:21.790 align:start position:0% service very nicely and smoothly into the<00:10:19.550> whole<00:10:19.790> model<00:10:20.170> and<00:10:21.170> this<00:10:21.529> is<00:10:21.680> all 00:10:21.790 --> 00:10:21.800 align:start position:0% the whole model and this is all 00:10:21.800 --> 00:10:24.340 align:start position:0% the whole model and this is all something<00:10:22.070> that<00:10:22.399> already<00:10:22.579> works<00:10:22.820> in<00:10:23.420> their 00:10:24.340 --> 00:10:24.350 align:start position:0% something that already works in their 00:10:24.350 --> 00:10:28.090 align:start position:0% something that already works in their big<00:10:24.529> night<00:10:24.680> servers<00:10:25.360> that<00:10:26.709> even<00:10:27.709> plants<00:10:28.010> we 00:10:28.090 --> 00:10:28.100 align:start position:0% big night servers that even plants we 00:10:28.100 --> 00:10:29.590 align:start position:0% big night servers that even plants we don't<00:10:28.279> have<00:10:28.459> a<00:10:28.490> token<00:10:28.970> palace 00:10:29.590 --> 00:10:29.600 align:start position:0% don't have a token palace 00:10:29.600 --> 00:10:32.230 align:start position:0% don't have a token palace they<00:10:29.720> have<00:10:29.899> a<00:10:30.160> virtual<00:10:31.160> negative<00:10:31.850> balance 00:10:32.230 --> 00:10:32.240 align:start position:0% they have a virtual negative balance 00:10:32.240 --> 00:10:36.990 align:start position:0% they have a virtual negative balance which<00:10:32.990> is<00:10:33.279> associated<00:10:34.279> to<00:10:34.519> IP<00:10:34.880> address<00:10:35.680> also 00:10:36.990 --> 00:10:37.000 align:start position:0% which is associated to IP address also 00:10:37.000 --> 00:10:39.850 align:start position:0% which is associated to IP address also it's<00:10:38.000> a<00:10:38.240> expire<00:10:38.720> this<00:10:39.050> one<00:10:39.230> actually<00:10:39.410> over 00:10:39.850 --> 00:10:39.860 align:start position:0% it's a expire this one actually over 00:10:39.860 --> 00:10:43.030 align:start position:0% it's a expire this one actually over along<00:10:40.279> another<00:10:40.730> kind<00:10:41.089> but<00:10:41.360> so<00:10:42.290> this<00:10:42.410> is<00:10:42.589> to 00:10:43.030 --> 00:10:43.040 align:start position:0% along another kind but so this is to 00:10:43.040 --> 00:10:47.829 align:start position:0% along another kind but so this is to ensure<00:10:43.160> that<00:10:44.079> three<00:10:45.079> clients<00:10:46.329> can<00:10:47.329> it's<00:10:47.660> also 00:10:47.829 --> 00:10:47.839 align:start position:0% ensure that three clients can it's also 00:10:47.839 --> 00:10:51.009 align:start position:0% ensure that three clients can it's also know<00:10:48.320> the<00:10:48.550> client<00:10:49.550> who<00:10:49.700> has<00:10:49.880> used<00:10:50.510> the<00:10:50.690> service 00:10:51.009 --> 00:10:51.019 align:start position:0% know the client who has used the service 00:10:51.019 --> 00:10:54.850 align:start position:0% know the client who has used the service lesson<00:10:51.880> recently<00:10:52.880> and<00:10:53.209> has<00:10:53.540> a<00:10:53.570> higher<00:10:54.260> chance 00:10:54.850 --> 00:10:54.860 align:start position:0% lesson recently and has a higher chance 00:10:54.860 --> 00:10:59.620 align:start position:0% lesson recently and has a higher chance to<00:10:55.250> connect<00:10:57.550> so<00:10:58.550> tree<00:10:58.790> service<00:10:59.120> is<00:10:59.390> also 00:10:59.620 --> 00:10:59.630 align:start position:0% to connect so tree service is also 00:10:59.630 --> 00:11:01.630 align:start position:0% to connect so tree service is also important<00:11:00.320> and<00:11:00.500> the<00:11:00.680> server<00:11:00.890> also<00:11:01.220> has<00:11:01.490> to 00:11:01.630 --> 00:11:01.640 align:start position:0% important and the server also has to 00:11:01.640 --> 00:11:03.699 align:start position:0% important and the server also has to ensure<00:11:01.760> that<00:11:02.029> the<00:11:02.480> free<00:11:03.020> service<00:11:03.410> is<00:11:03.649> a 00:11:03.699 --> 00:11:03.709 align:start position:0% ensure that the free service is a 00:11:03.709 --> 00:11:06.220 align:start position:0% ensure that the free service is a regular<00:11:04.670> did<00:11:04.910> not<00:11:05.060> always<00:11:05.450> but<00:11:05.690> regular 00:11:06.220 --> 00:11:06.230 align:start position:0% regular did not always but regular 00:11:06.230 --> 00:11:08.560 align:start position:0% regular did not always but regular regularly<00:11:06.829> available<00:11:07.430> for<00:11:07.880> two<00:11:08.060> reasons<00:11:08.510> one 00:11:08.560 --> 00:11:08.570 align:start position:0% regularly available for two reasons one 00:11:08.570 --> 00:11:10.090 align:start position:0% regularly available for two reasons one of<00:11:08.720> them<00:11:08.930> is<00:11:09.079> that<00:11:09.290> this<00:11:09.470> is<00:11:09.620> what<00:11:09.829> helps 00:11:10.090 --> 00:11:10.100 align:start position:0% of them is that this is what helps 00:11:10.100 --> 00:11:11.639 align:start position:0% of them is that this is what helps reputation<00:11:11.060> building 00:11:11.639 --> 00:11:11.649 align:start position:0% reputation building 00:11:11.649 --> 00:11:14.519 align:start position:0% reputation building new<00:11:12.279> customers<00:11:12.790> and<00:11:13.180> the<00:11:13.509> other<00:11:13.660> one<00:11:13.930> is<00:11:14.079> at 00:11:14.519 --> 00:11:14.529 align:start position:0% new customers and the other one is at 00:11:14.529 --> 00:11:17.100 align:start position:0% new customers and the other one is at the<00:11:14.649> same<00:11:14.860> condition<00:11:15.399> that<00:11:15.519> allows<00:11:16.110> free 00:11:17.100 --> 00:11:17.110 align:start position:0% the same condition that allows free 00:11:17.110 --> 00:11:18.900 align:start position:0% the same condition that allows free service<00:11:17.439> to<00:11:17.559> be<00:11:17.680> unavailable<00:11:18.369> it<00:11:18.699> also 00:11:18.900 --> 00:11:18.910 align:start position:0% service to be unavailable it also 00:11:18.910 --> 00:11:21.900 align:start position:0% service to be unavailable it also ensures<00:11:19.180> that<00:11:19.499> the<00:11:20.499> service<00:11:20.949> demands<00:11:21.399> are<00:11:21.579> all 00:11:21.900 --> 00:11:21.910 align:start position:0% ensures that the service demands are all 00:11:21.910 --> 00:11:24.410 align:start position:0% ensures that the service demands are all spendable<00:11:22.569> in<00:11:22.720> a<00:11:22.839> limited<00:11:23.230> time<00:11:23.649> frame<00:11:24.100> so 00:11:24.410 --> 00:11:24.420 align:start position:0% spendable in a limited time frame so 00:11:24.420 --> 00:11:27.600 align:start position:0% spendable in a limited time frame so there's<00:11:25.420> another<00:11:25.779> control<00:11:26.339> mechanism<00:11:27.339> healed 00:11:27.600 --> 00:11:27.610 align:start position:0% there's another control mechanism healed 00:11:27.610 --> 00:11:32.639 align:start position:0% there's another control mechanism healed that<00:11:28.920> controls<00:11:29.920> the<00:11:30.040> base<00:11:30.249> token<00:11:30.639> price<00:11:31.649> based 00:11:32.639 --> 00:11:32.649 align:start position:0% that controls the base token price based 00:11:32.649 --> 00:11:34.679 align:start position:0% that controls the base token price based on<00:11:32.889> whether<00:11:33.339> the<00:11:33.610> service<00:11:34.029> free<00:11:34.240> service<00:11:34.540> is 00:11:34.679 --> 00:11:34.689 align:start position:0% on whether the service free service is 00:11:34.689 --> 00:11:36.629 align:start position:0% on whether the service free service is possible<00:11:35.139> or<00:11:35.259> not<00:11:35.290> if<00:11:35.619> it<00:11:35.740> is<00:11:35.769> possible<00:11:36.399> then 00:11:36.629 --> 00:11:36.639 align:start position:0% possible or not if it is possible then 00:11:36.639 --> 00:11:42.660 align:start position:0% possible or not if it is possible then it<00:11:39.329> reduces<00:11:40.329> the<00:11:40.779> price<00:11:40.929> and<00:11:41.230> other<00:11:41.350> I<00:11:41.649> say<00:11:41.920> it 00:11:42.660 --> 00:11:42.670 align:start position:0% it reduces the price and other I say it 00:11:42.670 --> 00:11:45.179 align:start position:0% it reduces the price and other I say it is<00:11:43.179> slowly<00:11:43.480> exponentially<00:11:44.439> increases<00:11:45.040> the 00:11:45.179 --> 00:11:45.189 align:start position:0% is slowly exponentially increases the 00:11:45.189 --> 00:11:50.009 align:start position:0% is slowly exponentially increases the base<00:11:45.309> price<00:11:47.939> yeah<00:11:48.939> this<00:11:49.209> is<00:11:49.329> about<00:11:49.509> it<00:11:49.720> for<00:11:49.899> the 00:11:50.009 --> 00:11:50.019 align:start position:0% base price yeah this is about it for the 00:11:50.019 --> 00:11:52.650 align:start position:0% base price yeah this is about it for the server<00:11:50.230> mechanism<00:11:50.889> and<00:11:51.429> now<00:11:51.639> let's<00:11:52.360> take<00:11:52.600> a 00:11:52.650 --> 00:11:52.660 align:start position:0% server mechanism and now let's take a 00:11:52.660 --> 00:12:01.790 align:start position:0% server mechanism and now let's take a look<00:11:52.809> at<00:11:52.990> the<00:11:53.579> right<00:11:54.579> hand<00:11:54.730> side<00:11:56.129> so<00:11:57.129> this<00:11:58.709> is 00:12:01.790 --> 00:12:01.800 align:start position:0% 00:12:01.800 --> 00:12:04.379 align:start position:0% going<00:12:02.800> to<00:12:03.189> be<00:12:03.309> going<00:12:03.459> to<00:12:03.639> every<00:12:03.730> individual 00:12:04.379 --> 00:12:04.389 align:start position:0% going to be going to every individual 00:12:04.389 --> 00:12:06.989 align:start position:0% going to be going to every individual here<00:12:04.629> but<00:12:04.869> there's<00:12:05.709> a<00:12:05.920> subjective<00:12:06.490> value 00:12:06.989 --> 00:12:06.999 align:start position:0% here but there's a subjective value 00:12:06.999 --> 00:12:09.030 align:start position:0% here but there's a subjective value measurement<00:12:07.959> from<00:12:08.050> the<00:12:08.110> find<00:12:08.410> side<00:12:08.649> which<00:12:08.860> is 00:12:09.030 --> 00:12:09.040 align:start position:0% measurement from the find side which is 00:12:09.040 --> 00:12:12.199 align:start position:0% measurement from the find side which is ideally<00:12:09.699> it<00:12:09.999> should<00:12:10.029> be<00:12:10.360> a<00:12:10.389> mirror<00:12:10.929> of<00:12:11.259> the 00:12:12.199 --> 00:12:12.209 align:start position:0% ideally it should be a mirror of the 00:12:12.209 --> 00:12:15.359 align:start position:0% ideally it should be a mirror of the server<00:12:13.209> side<00:12:13.569> token<00:12:14.290> accounting<00:12:14.829> so 00:12:15.359 --> 00:12:15.369 align:start position:0% server side token accounting so 00:12:15.369 --> 00:12:17.480 align:start position:0% server side token accounting so basically<00:12:16.269> the<00:12:16.449> clients<00:12:16.779> will<00:12:17.110> try<00:12:17.350> to 00:12:17.480 --> 00:12:17.490 align:start position:0% basically the clients will try to 00:12:17.490 --> 00:12:20.489 align:start position:0% basically the clients will try to somehow<00:12:18.490> put<00:12:18.999> a<00:12:19.029> number<00:12:19.240> on<00:12:19.360> how<00:12:19.689> much<00:12:20.019> service 00:12:20.489 --> 00:12:20.499 align:start position:0% somehow put a number on how much service 00:12:20.499 --> 00:12:22.860 align:start position:0% somehow put a number on how much service they<00:12:21.279> receive<00:12:21.670> and<00:12:21.939> this<00:12:22.120> is<00:12:22.240> also<00:12:22.420> based<00:12:22.660> on 00:12:22.860 --> 00:12:22.870 align:start position:0% they receive and this is also based on 00:12:22.870 --> 00:12:25.590 align:start position:0% they receive and this is also based on serve<00:12:23.679> the<00:12:23.889> requests<00:12:24.429> and<00:12:24.600> currently 00:12:25.590 --> 00:12:25.600 align:start position:0% serve the requests and currently 00:12:25.600 --> 00:12:28.410 align:start position:0% serve the requests and currently capacities<00:12:26.259> and<00:12:26.679> it<00:12:26.889> also<00:12:27.120> modified<00:12:28.120> by<00:12:28.389> a 00:12:28.410 --> 00:12:28.420 align:start position:0% capacities and it also modified by a 00:12:28.420 --> 00:12:30.299 align:start position:0% capacities and it also modified by a service<00:12:28.929> quality<00:12:29.319> factor<00:12:29.649> which<00:12:29.769> is<00:12:29.920> based<00:12:30.129> on 00:12:30.299 --> 00:12:30.309 align:start position:0% service quality factor which is based on 00:12:30.309 --> 00:12:34.049 align:start position:0% service quality factor which is based on which<00:12:30.490> response<00:12:30.999> times<00:12:31.300> and<00:12:32.610> how<00:12:33.610> response 00:12:34.049 --> 00:12:34.059 align:start position:0% which response times and how response 00:12:34.059 --> 00:12:36.689 align:start position:0% which response times and how response times<00:12:34.269> are<00:12:34.480> probably<00:12:35.410> per<00:12:35.620> serving<00:12:35.980> but<00:12:36.220> it 00:12:36.689 --> 00:12:36.699 align:start position:0% times are probably per serving but it 00:12:36.699 --> 00:12:39.629 align:start position:0% times are probably per serving but it depends<00:12:37.420> on<00:12:37.509> the<00:12:38.069> expectations<00:12:39.069> of<00:12:39.249> response 00:12:39.629 --> 00:12:39.639 align:start position:0% depends on the expectations of response 00:12:39.639 --> 00:12:42.689 align:start position:0% depends on the expectations of response times<00:12:39.879> which<00:12:40.139> depends<00:12:41.139> on<00:12:41.379> price<00:12:41.980> factors<00:12:42.459> and 00:12:42.689 --> 00:12:42.699 align:start position:0% times which depends on price factors and 00:12:42.699 --> 00:12:44.819 align:start position:0% times which depends on price factors and everything<00:12:42.999> so<00:12:43.149> basically<00:12:43.480> it's<00:12:44.079> possible<00:12:44.559> to 00:12:44.819 --> 00:12:44.829 align:start position:0% everything so basically it's possible to 00:12:44.829 --> 00:12:48.150 align:start position:0% everything so basically it's possible to if<00:12:45.480> they<00:12:46.480> find<00:12:46.809> has<00:12:47.019> to<00:12:47.230> make<00:12:47.470> a<00:12:47.499> decision<00:12:47.800> on 00:12:48.150 --> 00:12:48.160 align:start position:0% if they find has to make a decision on 00:12:48.160 --> 00:12:50.639 align:start position:0% if they find has to make a decision on who<00:12:48.429> to<00:12:48.459> pay<00:12:48.850> for<00:12:49.149> it<00:12:49.420> can<00:12:49.809> map<00:12:50.019> out<00:12:50.170> the<00:12:50.410> whole 00:12:50.639 --> 00:12:50.649 align:start position:0% who to pay for it can map out the whole 00:12:50.649 --> 00:12:55.739 align:start position:0% who to pay for it can map out the whole available<00:12:51.279> market<00:12:51.699> as<00:12:51.910> a<00:12:52.949> price<00:12:53.970> versus<00:12:54.970> every 00:12:55.739 --> 00:12:55.749 align:start position:0% available market as a price versus every 00:12:55.749 --> 00:12:58.139 align:start position:0% available market as a price versus every expected<00:12:56.559> response<00:12:56.949> time<00:12:57.249> and<00:12:57.519> function 00:12:58.139 --> 00:12:58.149 align:start position:0% expected response time and function 00:12:58.149 --> 00:12:59.980 align:start position:0% expected response time and function which<00:12:58.600> is<00:12:58.809> nice<00:12:59.139> and<00:12:59.470> if<00:12:59.679> you 00:12:59.980 --> 00:12:59.990 align:start position:0% which is nice and if you 00:12:59.990 --> 00:13:03.310 align:start position:0% which is nice and if you easy<00:13:00.890> to<00:13:01.100> understand<00:13:01.580> for<00:13:01.790> human<00:13:02.240> users<00:13:02.660> so<00:13:03.170> if 00:13:03.310 --> 00:13:03.320 align:start position:0% easy to understand for human users so if 00:13:03.320 --> 00:13:05.350 align:start position:0% easy to understand for human users so if we<00:13:03.470> have<00:13:03.620> a<00:13:03.649> regular<00:13:04.160> groom<00:13:04.459> and<00:13:04.700> we<00:13:05.149> have<00:13:05.270> an 00:13:05.350 --> 00:13:05.360 align:start position:0% we have a regular groom and we have an 00:13:05.360 --> 00:13:07.090 align:start position:0% we have a regular groom and we have an expected<00:13:05.660> response<00:13:06.140> time<00:13:06.380> then<00:13:06.620> we<00:13:07.070> can 00:13:07.090 --> 00:13:07.100 align:start position:0% expected response time then we can 00:13:07.100 --> 00:13:10.470 align:start position:0% expected response time then we can convert<00:13:07.970> our<00:13:08.360> quality<00:13:09.050> statistics<00:13:09.230> into<00:13:10.130> a 00:13:10.470 --> 00:13:10.480 align:start position:0% convert our quality statistics into a 00:13:10.480 --> 00:13:13.840 align:start position:0% convert our quality statistics into a single<00:13:11.480> scalar<00:13:11.750> value<00:13:12.290> and<00:13:12.680> I'd<00:13:13.310> like<00:13:13.700> to 00:13:13.840 --> 00:13:13.850 align:start position:0% single scalar value and I'd like to 00:13:13.850 --> 00:13:16.329 align:start position:0% single scalar value and I'd like to mention<00:13:14.000> here<00:13:14.390> that<00:13:14.420> the<00:13:14.860> various<00:13:15.860> constants 00:13:16.329 --> 00:13:16.339 align:start position:0% mention here that the various constants 00:13:16.339 --> 00:13:20.500 align:start position:0% mention here that the various constants can<00:13:17.120> even<00:13:17.450> about<00:13:17.990> as<00:13:18.200> a<00:13:18.230> negative<00:13:18.560> by<00:13:19.510> for 00:13:20.500 --> 00:13:20.510 align:start position:0% can even about as a negative by for 00:13:20.510 --> 00:13:23.100 align:start position:0% can even about as a negative by for clients<00:13:21.050> because<00:13:21.890> we<00:13:22.040> have<00:13:22.130> to<00:13:22.310> incentivize 00:13:23.100 --> 00:13:23.110 align:start position:0% clients because we have to incentivize 00:13:23.110 --> 00:13:28.000 align:start position:0% clients because we have to incentivize reliably<00:13:24.550> with<00:13:25.550> response<00:13:25.940> times<00:13:26.800> and<00:13:27.800> this 00:13:28.000 --> 00:13:28.010 align:start position:0% reliably with response times and this 00:13:28.010 --> 00:13:30.220 align:start position:0% reliably with response times and this service<00:13:28.370> value<00:13:28.670> is<00:13:28.850> what<00:13:29.120> we<00:13:29.510> kind<00:13:29.690> started<00:13:30.140> up 00:13:30.220 --> 00:13:30.230 align:start position:0% service value is what we kind started up 00:13:30.230 --> 00:13:32.190 align:start position:0% service value is what we kind started up trying<00:13:30.470> to<00:13:30.529> get<00:13:30.740> all<00:13:30.980> their<00:13:31.130> money<00:13:31.160> basically 00:13:32.190 --> 00:13:32.200 align:start position:0% trying to get all their money basically 00:13:32.200 --> 00:13:35.740 align:start position:0% trying to get all their money basically and<00:13:33.200> finally<00:13:33.970> there's<00:13:34.970> the<00:13:35.089> tricky<00:13:35.360> part<00:13:35.570> of 00:13:35.740 --> 00:13:35.750 align:start position:0% and finally there's the tricky part of 00:13:35.750 --> 00:13:38.769 align:start position:0% and finally there's the tricky part of this<00:13:35.959> because<00:13:36.640> if<00:13:37.640> the<00:13:37.880> fight<00:13:38.120> wants<00:13:38.420> to<00:13:38.600> make 00:13:38.769 --> 00:13:38.779 align:start position:0% this because if the fight wants to make 00:13:38.779 --> 00:13:42.070 align:start position:0% this because if the fight wants to make a<00:13:38.810> statement<00:13:39.010> about<00:13:40.010> who<00:13:40.850> to<00:13:41.000> pay<00:13:41.180> for<00:13:41.480> than 00:13:42.070 --> 00:13:42.080 align:start position:0% a statement about who to pay for than 00:13:42.080 --> 00:13:44.680 align:start position:0% a statement about who to pay for than what<00:13:42.560> it<00:13:42.680> really<00:13:42.709> was<00:13:43.070> like<00:13:43.250> to<00:13:43.399> do<00:13:43.580> is<00:13:43.790> predict 00:13:44.680 --> 00:13:44.690 align:start position:0% what it really was like to do is predict 00:13:44.690 --> 00:13:48.310 align:start position:0% what it really was like to do is predict the<00:13:45.290> service<00:13:45.950> value<00:13:46.370> received<00:13:46.910> after<00:13:47.779> making 00:13:48.310 --> 00:13:48.320 align:start position:0% the service value received after making 00:13:48.320 --> 00:13:50.560 align:start position:0% the service value received after making the<00:13:48.560> payment<00:13:49.040> and<00:13:49.370> before<00:13:49.880> the<00:13:50.000> next<00:13:50.149> payment 00:13:50.560 --> 00:13:50.570 align:start position:0% the payment and before the next payment 00:13:50.570 --> 00:13:51.670 align:start position:0% the payment and before the next payment is<00:13:50.870> requested 00:13:51.670 --> 00:13:51.680 align:start position:0% is requested 00:13:51.680 --> 00:13:56.470 align:start position:0% is requested so<00:13:53.200> so<00:13:54.200> theoretically<00:13:54.709> if<00:13:55.550> they<00:13:55.790> can<00:13:56.270> trust 00:13:56.470 --> 00:13:56.480 align:start position:0% so so theoretically if they can trust 00:13:56.480 --> 00:13:58.889 align:start position:0% so so theoretically if they can trust the<00:13:56.630> server<00:13:56.870> this<00:13:57.200> is<00:13:57.380> not<00:13:57.560> so<00:13:57.740> hard<00:13:57.770> because 00:13:58.889 --> 00:13:58.899 align:start position:0% the server this is not so hard because 00:13:58.899 --> 00:14:02.860 align:start position:0% the server this is not so hard because we<00:13:59.899> expect<00:14:00.470> the<00:14:00.800> service<00:14:01.550> against<00:14:02.390> purchasing 00:14:02.860 --> 00:14:02.870 align:start position:0% we expect the service against purchasing 00:14:02.870 --> 00:14:04.990 align:start position:0% we expect the service against purchasing power<00:14:03.080> to<00:14:03.380> be<00:14:03.529> more<00:14:03.709> or<00:14:03.830> less<00:14:03.950> stable<00:14:04.190> and<00:14:04.610> the 00:14:04.990 --> 00:14:05.000 align:start position:0% power to be more or less stable and the 00:14:05.000 --> 00:14:07.120 align:start position:0% power to be more or less stable and the client<00:14:05.300> has<00:14:05.329> an<00:14:05.540> idea<00:14:05.839> of<00:14:05.899> how<00:14:06.380> well<00:14:06.680> your<00:14:06.890> the 00:14:07.120 --> 00:14:07.130 align:start position:0% client has an idea of how well your the 00:14:07.130 --> 00:14:09.010 align:start position:0% client has an idea of how well your the service<00:14:07.610> service<00:14:08.089> depends<00:14:08.420> were<00:14:08.570> in<00:14:08.690> the<00:14:08.810> past 00:14:09.010 --> 00:14:09.020 align:start position:0% service service depends were in the past 00:14:09.020 --> 00:14:11.050 align:start position:0% service service depends were in the past and<00:14:09.320> there's<00:14:09.800> a<00:14:09.890> token<00:14:10.370> price<00:14:10.610> at<00:14:10.850> the<00:14:10.940> moment 00:14:11.050 --> 00:14:11.060 align:start position:0% and there's a token price at the moment 00:14:11.060 --> 00:14:13.900 align:start position:0% and there's a token price at the moment so<00:14:11.709> it<00:14:12.709> should<00:14:12.950> be<00:14:13.070> predictable<00:14:13.610> but<00:14:13.730> of 00:14:13.900 --> 00:14:13.910 align:start position:0% so it should be predictable but of 00:14:13.910 --> 00:14:15.790 align:start position:0% so it should be predictable but of course<00:14:14.149> the<00:14:14.360> client<00:14:14.720> cannot<00:14:15.079> blindly<00:14:15.290> trust 00:14:15.790 --> 00:14:15.800 align:start position:0% course the client cannot blindly trust 00:14:15.800 --> 00:14:17.350 align:start position:0% course the client cannot blindly trust any<00:14:16.040> server<00:14:16.430> so<00:14:16.880> this<00:14:17.029> is<00:14:17.149> how<00:14:17.300> the 00:14:17.350 --> 00:14:17.360 align:start position:0% any server so this is how the 00:14:17.360 --> 00:14:19.990 align:start position:0% any server so this is how the recognition<00:14:18.230> building<00:14:18.529> magnesium<00:14:18.950> works<00:14:19.160> we 00:14:19.990 --> 00:14:20.000 align:start position:0% recognition building magnesium works we 00:14:20.000 --> 00:14:21.760 align:start position:0% recognition building magnesium works we have<00:14:20.180> three<00:14:20.480> predictors<00:14:20.899> we<00:14:21.290> have<00:14:21.440> a<00:14:21.470> base 00:14:21.760 --> 00:14:21.770 align:start position:0% have three predictors we have a base 00:14:21.770 --> 00:14:24.460 align:start position:0% have three predictors we have a base value<00:14:21.880> which<00:14:22.880> is<00:14:23.060> a<00:14:23.089> very<00:14:23.390> simple<00:14:23.720> as<00:14:23.959> paranoid 00:14:24.460 --> 00:14:24.470 align:start position:0% value which is a very simple as paranoid 00:14:24.470 --> 00:14:27.760 align:start position:0% value which is a very simple as paranoid and<00:14:24.740> all<00:14:25.579> uses<00:14:26.060> by<00:14:26.480> the<00:14:26.540> things<00:14:27.470> that<00:14:27.649> the 00:14:27.760 --> 00:14:27.770 align:start position:0% and all uses by the things that the 00:14:27.770 --> 00:14:31.000 align:start position:0% and all uses by the things that the Defiant<00:14:28.250> knows<00:14:28.459> for<00:14:28.700> sure<00:14:28.730> so<00:14:29.570> it's<00:14:30.320> basically 00:14:31.000 --> 00:14:31.010 align:start position:0% Defiant knows for sure so it's basically 00:14:31.010 --> 00:14:32.829 align:start position:0% Defiant knows for sure so it's basically takes<00:14:31.310> the<00:14:31.520> service<00:14:32.029> value<00:14:32.300> received<00:14:32.630> so<00:14:32.810> far 00:14:32.829 --> 00:14:32.839 align:start position:0% takes the service value received so far 00:14:32.839 --> 00:14:34.870 align:start position:0% takes the service value received so far and<00:14:33.380> the<00:14:33.529> payments<00:14:33.950> and<00:14:34.160> so<00:14:34.370> far<00:14:34.610> and<00:14:34.790> the 00:14:34.870 --> 00:14:34.880 align:start position:0% and the payments and so far and the 00:14:34.880 --> 00:14:37.660 align:start position:0% and the payments and so far and the payment<00:14:35.240> expected<00:14:35.810> currently<00:14:36.680> and<00:14:37.160> it<00:14:37.399> just 00:14:37.660 --> 00:14:37.670 align:start position:0% payment expected currently and it just 00:14:37.670 --> 00:14:40.150 align:start position:0% payment expected currently and it just does<00:14:37.880> a<00:14:37.910> linear<00:14:38.390> extrapolation<00:14:38.920> which<00:14:39.920> is 00:14:40.150 --> 00:14:40.160 align:start position:0% does a linear extrapolation which is 00:14:40.160 --> 00:14:42.970 align:start position:0% does a linear extrapolation which is which<00:14:40.820> converges<00:14:41.480> to<00:14:41.690> something 00:14:42.970 --> 00:14:42.980 align:start position:0% which converges to something 00:14:42.980 --> 00:14:44.770 align:start position:0% which converges to something over<00:14:43.280> the<00:14:43.430> long<00:14:43.580> term<00:14:43.760> is<00:14:44.000> not<00:14:44.180> very<00:14:44.210> good<00:14:44.540> but 00:14:44.770 --> 00:14:44.780 align:start position:0% over the long term is not very good but 00:14:44.780 --> 00:14:48.250 align:start position:0% over the long term is not very good but also<00:14:45.410> not<00:14:46.340> suitable<00:14:46.820> and<00:14:47.210> as<00:14:47.510> the<00:14:47.690> trusted<00:14:48.110> by 00:14:48.250 --> 00:14:48.260 align:start position:0% also not suitable and as the trusted by 00:14:48.260 --> 00:14:51.160 align:start position:0% also not suitable and as the trusted by a<00:14:48.290> predictor<00:14:48.920> it<00:14:49.390> does<00:14:50.390> what<00:14:50.630> I<00:14:50.660> already 00:14:51.160 --> 00:14:51.170 align:start position:0% a predictor it does what I already 00:14:51.170 --> 00:14:52.960 align:start position:0% a predictor it does what I already described<00:14:51.680> it<00:14:51.860> believes<00:14:52.190> the<00:14:52.340> server<00:14:52.610> and 00:14:52.960 --> 00:14:52.970 align:start position:0% described it believes the server and 00:14:52.970 --> 00:14:55.300 align:start position:0% described it believes the server and this<00:14:53.360> token<00:14:53.720> accounting<00:14:54.230> at<00:14:54.440> token<00:14:54.830> prices 00:14:55.300 --> 00:14:55.310 align:start position:0% this token accounting at token prices 00:14:55.310 --> 00:14:59.140 align:start position:0% this token accounting at token prices and<00:14:55.880> the<00:14:56.060> stability<00:14:56.570> of<00:14:56.600> these<00:14:56.810> tokens<00:14:57.050> and<00:14:58.150> to 00:14:59.140 --> 00:14:59.150 align:start position:0% and the stability of these tokens and to 00:14:59.150 --> 00:15:01.120 align:start position:0% and the stability of these tokens and to make<00:14:59.330> the<00:14:59.510> final<00:14:59.900> judgment<00:14:59.930> there's<00:15:00.650> a<00:15:00.740> third 00:15:01.120 --> 00:15:01.130 align:start position:0% make the final judgment there's a third 00:15:01.130 --> 00:15:04.720 align:start position:0% make the final judgment there's a third a<00:15:01.280> superb<00:15:01.760> predictor<00:15:02.270> which<00:15:03.490> initially<00:15:04.490> takes 00:15:04.720 --> 00:15:04.730 align:start position:0% a superb predictor which initially takes 00:15:04.730 --> 00:15:06.700 align:start position:0% a superb predictor which initially takes for<00:15:05.210> it<00:15:05.300> returns<00:15:05.690> the<00:15:05.930> predictions<00:15:06.500> of<00:15:06.650> the 00:15:06.700 --> 00:15:06.710 align:start position:0% for it returns the predictions of the 00:15:06.710 --> 00:15:09.550 align:start position:0% for it returns the predictions of the base<00:15:06.980> predictor<00:15:07.550> and<00:15:07.850> the<00:15:08.170> overtime<00:15:09.170> is<00:15:09.440> the 00:15:09.550 --> 00:15:09.560 align:start position:0% base predictor and the overtime is the 00:15:09.560 --> 00:15:11.530 align:start position:0% base predictor and the overtime is the trusted<00:15:09.920> predictor<00:15:10.400> process<00:15:10.940> and<00:15:11.150> they<00:15:11.300> gives 00:15:11.530 --> 00:15:11.540 align:start position:0% trusted predictor process and they gives 00:15:11.540 --> 00:15:13.600 align:start position:0% trusted predictor process and they gives the<00:15:11.690> better<00:15:11.840> estimates<00:15:12.380> of<00:15:12.740> service<00:15:13.310> value 00:15:13.600 --> 00:15:13.610 align:start position:0% the better estimates of service value 00:15:13.610 --> 00:15:16.930 align:start position:0% the better estimates of service value received<00:15:13.940> after<00:15:14.270> making<00:15:14.690> a<00:15:15.020> payment<00:15:15.610> then<00:15:16.610> it 00:15:16.930 --> 00:15:16.940 align:start position:0% received after making a payment then it 00:15:16.940 --> 00:15:19.060 align:start position:0% received after making a payment then it will<00:15:17.150> allow<00:15:17.510> more<00:15:17.840> and<00:15:17.990> more<00:15:18.200> deviation<00:15:18.860> from 00:15:19.060 --> 00:15:19.070 align:start position:0% will allow more and more deviation from 00:15:19.070 --> 00:15:21.970 align:start position:0% will allow more and more deviation from the<00:15:19.340> whispered<00:15:19.940> base<00:15:20.150> with<00:15:20.500> predictors<00:15:21.500> value 00:15:21.970 --> 00:15:21.980 align:start position:0% the whispered base with predictors value 00:15:21.980 --> 00:15:23.620 align:start position:0% the whispered base with predictors value in<00:15:22.400> the<00:15:22.520> direction<00:15:22.850> of<00:15:23.030> the<00:15:23.210> attractive 00:15:23.620 --> 00:15:23.630 align:start position:0% in the direction of the attractive 00:15:23.630 --> 00:15:26.950 align:start position:0% in the direction of the attractive predictors<00:15:24.410> prediction<00:15:25.310> and<00:15:25.790> so<00:15:26.660> this<00:15:26.810> is 00:15:26.950 --> 00:15:26.960 align:start position:0% predictors prediction and so this is 00:15:26.960 --> 00:15:27.940 align:start position:0% predictors prediction and so this is this 00:15:27.940 --> 00:15:27.950 align:start position:0% this 00:15:27.950 --> 00:15:31.930 align:start position:0% this this<00:15:28.810> allowed<00:15:29.810> deviation<00:15:30.830> this<00:15:31.130> represents 00:15:31.930 --> 00:15:31.940 align:start position:0% this allowed deviation this represents 00:15:31.940 --> 00:15:33.850 align:start position:0% this allowed deviation this represents the<00:15:32.030> reputation<00:15:32.780> of<00:15:32.840> the<00:15:32.960> server<00:15:33.200> and<00:15:33.560> this 00:15:33.850 --> 00:15:33.860 align:start position:0% the reputation of the server and this 00:15:33.860 --> 00:15:35.920 align:start position:0% the reputation of the server and this job<00:15:34.250> is<00:15:34.400> going<00:15:34.550> to<00:15:34.640> be<00:15:34.730> ruined<00:15:35.120> if<00:15:35.390> the<00:15:35.570> server 00:15:35.920 --> 00:15:35.930 align:start position:0% job is going to be ruined if the server 00:15:35.930 --> 00:15:38.440 align:start position:0% job is going to be ruined if the server doesn't<00:15:36.220> all<00:15:37.220> these<00:15:37.460> promises<00:15:37.640> and<00:15:38.060> doesn't 00:15:38.440 --> 00:15:38.450 align:start position:0% doesn't all these promises and doesn't 00:15:38.450 --> 00:15:42.870 align:start position:0% doesn't all these promises and doesn't keep<00:15:38.630> its<00:15:38.930> service<00:15:39.650> and<00:15:40.040> buy<00:15:40.370> a<00:15:40.580> device<00:15:40.730> table 00:15:42.870 --> 00:15:42.880 align:start position:0% keep its service and buy a device table 00:15:42.880 --> 00:15:51.340 align:start position:0% keep its service and buy a device table and<00:15:45.700> yeah<00:15:46.700> I<00:15:46.730> feel<00:15:47.060> thanks<00:15:47.840> so<00:15:49.360> now<00:15:50.360> just<00:15:50.660> just 00:15:51.340 --> 00:15:51.350 align:start position:0% and yeah I feel thanks so now just just 00:15:51.350 --> 00:15:53.440 align:start position:0% and yeah I feel thanks so now just just just<00:15:51.410> about<00:15:52.160> few<00:15:52.610> words<00:15:52.760> about<00:15:52.880> the<00:15:53.150> current 00:15:53.440 --> 00:15:53.450 align:start position:0% just about few words about the current 00:15:53.450 --> 00:15:56.440 align:start position:0% just about few words about the current state<00:15:53.660> of<00:15:53.690> implementation<00:15:54.620> and<00:15:55.240> the<00:15:56.240> roadmap 00:15:56.440 --> 00:15:56.450 align:start position:0% state of implementation and the roadmap 00:15:56.450 --> 00:16:00.190 align:start position:0% state of implementation and the roadmap so<00:15:57.440> as<00:15:58.220> I<00:15:58.550> already<00:15:59.270> said<00:15:59.570> the<00:15:59.630> most<00:15:59.900> of<00:16:00.080> the 00:16:00.190 --> 00:16:00.200 align:start position:0% so as I already said the most of the 00:16:00.200 --> 00:16:02.450 align:start position:0% so as I already said the most of the most<00:16:00.530> of<00:16:00.680> the<00:16:00.770> components 00:16:02.450 --> 00:16:02.460 align:start position:0% most of the components 00:16:02.460 --> 00:16:07.970 align:start position:0% most of the components living<00:16:03.650> material<00:16:04.650> and<00:16:04.860> I<00:16:06.200> so<00:16:07.200> far<00:16:07.440> mostly 00:16:07.970 --> 00:16:07.980 align:start position:0% living material and I so far mostly 00:16:07.980 --> 00:16:09.830 align:start position:0% living material and I so far mostly focused<00:16:08.460> on<00:16:08.640> implementing<00:16:09.240> the<00:16:09.420> server-side 00:16:09.830 --> 00:16:09.840 align:start position:0% focused on implementing the server-side 00:16:09.840 --> 00:16:14.570 align:start position:0% focused on implementing the server-side because<00:16:10.410> that's<00:16:10.860> what<00:16:11.790> the<00:16:11.970> first<00:16:13.580> that's 00:16:14.570 --> 00:16:14.580 align:start position:0% because that's what the first that's 00:16:14.580 --> 00:16:16.340 align:start position:0% because that's what the first that's what<00:16:14.760> we<00:16:14.970> first<00:16:15.180> need<00:16:15.390> in<00:16:15.630> order<00:16:15.780> to<00:16:15.930> even 00:16:16.340 --> 00:16:16.350 align:start position:0% what we first need in order to even 00:16:16.350 --> 00:16:21.220 align:start position:0% what we first need in order to even start<00:16:16.590> experimenting<00:16:17.580> and<00:16:19.280> recently<00:16:20.280> and 00:16:21.220 --> 00:16:21.230 align:start position:0% start experimenting and recently and 00:16:21.230 --> 00:16:24.740 align:start position:0% start experimenting and recently and server<00:16:22.230> India<00:16:22.650> has<00:16:22.890> been<00:16:23.130> implemented<00:16:23.750> it's 00:16:24.740 --> 00:16:24.750 align:start position:0% server India has been implemented it's 00:16:24.750 --> 00:16:26.300 align:start position:0% server India has been implemented it's going<00:16:25.050> to<00:16:25.200> come<00:16:25.530> out<00:16:25.650> in<00:16:25.860> one<00:16:26.070> of<00:16:26.100> the 00:16:26.300 --> 00:16:26.310 align:start position:0% going to come out in one of the 00:16:26.310 --> 00:16:29.540 align:start position:0% going to come out in one of the subsequent<00:16:27.150> get<00:16:27.720> releases<00:16:28.290> and<00:16:28.530> this<00:16:29.250> with 00:16:29.540 --> 00:16:29.550 align:start position:0% subsequent get releases and this with 00:16:29.550 --> 00:16:32.600 align:start position:0% subsequent get releases and this with this<00:16:29.730> you<00:16:29.910> can<00:16:30.000> already<00:16:30.270> play<00:16:31.170> with<00:16:31.620> the 00:16:32.600 --> 00:16:32.610 align:start position:0% this you can already play with the 00:16:32.610 --> 00:16:34.400 align:start position:0% this you can already play with the client<00:16:33.150> priorities<00:16:33.360> and<00:16:33.870> you<00:16:33.930> can<00:16:34.080> assign 00:16:34.400 --> 00:16:34.410 align:start position:0% client priorities and you can assign 00:16:34.410 --> 00:16:37.730 align:start position:0% client priorities and you can assign priorities<00:16:35.280> to<00:16:35.490> your<00:16:35.790> own<00:16:36.080> or<00:16:37.080> your<00:16:37.260> friends 00:16:37.730 --> 00:16:37.740 align:start position:0% priorities to your own or your friends 00:16:37.740 --> 00:16:41.690 align:start position:0% priorities to your own or your friends or<00:16:37.800> customers<00:16:38.370> nodes<00:16:38.670> and<00:16:40.160> there's<00:16:41.160> the<00:16:41.460> outer 00:16:41.690 --> 00:16:41.700 align:start position:0% or customers nodes and there's the outer 00:16:41.700 --> 00:16:44.600 align:start position:0% or customers nodes and there's the outer conceal<00:16:42.510> mechanism<00:16:43.110> is<00:16:44.010> working<00:16:44.430> progress 00:16:44.600 --> 00:16:44.610 align:start position:0% conceal mechanism is working progress 00:16:44.610 --> 00:16:48.020 align:start position:0% conceal mechanism is working progress but<00:16:45.030> I<00:16:45.570> really<00:16:46.110> hope<00:16:46.260> I<00:16:46.470> can<00:16:46.500> finish<00:16:47.460> it<00:16:47.580> and<00:16:47.880> we 00:16:48.020 --> 00:16:48.030 align:start position:0% but I really hope I can finish it and we 00:16:48.030 --> 00:16:50.630 align:start position:0% but I really hope I can finish it and we can<00:16:48.210> release<00:16:48.810> it<00:16:49.050> and<00:16:49.530> by<00:16:50.040> the<00:16:50.100> end<00:16:50.340> of<00:16:50.460> this 00:16:50.630 --> 00:16:50.640 align:start position:0% can release it and by the end of this 00:16:50.640 --> 00:16:52.340 align:start position:0% can release it and by the end of this year<00:16:50.910> and<00:16:51.030> this<00:16:51.300> will<00:16:51.480> mean<00:16:51.690> that<00:16:51.720> by<00:16:52.080> the<00:16:52.140> end 00:16:52.340 --> 00:16:52.350 align:start position:0% year and this will mean that by the end 00:16:52.350 --> 00:16:55.610 align:start position:0% year and this will mean that by the end of<00:16:52.470> this<00:16:52.950> year<00:16:53.220> we<00:16:53.640> are<00:16:53.730> going<00:16:53.850> to<00:16:54.090> have<00:16:54.270> a<00:16:54.620> thin 00:16:55.610 --> 00:16:55.620 align:start position:0% of this year we are going to have a thin 00:16:55.620 --> 00:16:57.590 align:start position:0% of this year we are going to have a thin and<00:16:55.860> fully<00:16:56.130> booking<00:16:56.490> payment<00:16:56.880> enabled<00:16:57.360> light 00:16:57.590 --> 00:16:57.600 align:start position:0% and fully booking payment enabled light 00:16:57.600 --> 00:17:01.580 align:start position:0% and fully booking payment enabled light servers<00:16:58.050> and<00:16:59.540> which<00:17:00.540> anyone<00:17:00.870> can<00:17:01.140> start<00:17:01.410> up 00:17:01.580 --> 00:17:01.590 align:start position:0% servers and which anyone can start up 00:17:01.590 --> 00:17:05.960 align:start position:0% servers and which anyone can start up and<00:17:01.770> start<00:17:01.980> earning<00:17:02.100> money<00:17:02.430> and<00:17:04.670> on<00:17:05.670> the<00:17:05.790> tight 00:17:05.960 --> 00:17:05.970 align:start position:0% and start earning money and on the tight 00:17:05.970 --> 00:17:09.380 align:start position:0% and start earning money and on the tight side<00:17:06.800> there's<00:17:07.800> going<00:17:07.980> to<00:17:08.070> be<00:17:08.160> some<00:17:08.670> manual 00:17:09.380 --> 00:17:09.390 align:start position:0% side there's going to be some manual 00:17:09.390 --> 00:17:11.690 align:start position:0% side there's going to be some manual have<00:17:09.630> maybe<00:17:09.930> like<00:17:10.530> a<00:17:10.589> revised<00:17:11.070> list<00:17:11.310> for 00:17:11.690 --> 00:17:11.700 align:start position:0% have maybe like a revised list for 00:17:11.700 --> 00:17:16.970 align:start position:0% have maybe like a revised list for servers<00:17:12.330> who<00:17:13.170> we<00:17:13.800> can<00:17:14.070> pay<00:17:14.760> for<00:17:14.820> but<00:17:15.600> the<00:17:15.980> the 00:17:16.970 --> 00:17:16.980 align:start position:0% servers who we can pay for but the the 00:17:16.980 --> 00:17:21.740 align:start position:0% servers who we can pay for but the the client<00:17:17.520> side<00:17:18.230> side<00:17:19.790> it's<00:17:20.790> also<00:17:20.970> already 00:17:21.740 --> 00:17:21.750 align:start position:0% client side side it's also already 00:17:21.750 --> 00:17:24.230 align:start position:0% client side side it's also already partially<00:17:22.170> implemented<00:17:22.650> and<00:17:23.400> I<00:17:23.790> really<00:17:24.089> hope 00:17:24.230 --> 00:17:24.240 align:start position:0% partially implemented and I really hope 00:17:24.240 --> 00:17:28.490 align:start position:0% partially implemented and I really hope that<00:17:25.910> by<00:17:26.910> the<00:17:26.970> middle<00:17:27.570> of<00:17:27.630> next<00:17:27.870> year<00:17:28.080> we<00:17:28.380> are 00:17:28.490 --> 00:17:28.500 align:start position:0% that by the middle of next year we are 00:17:28.500 --> 00:17:32.240 align:start position:0% that by the middle of next year we are going<00:17:28.650> I'm<00:17:29.310> going<00:17:29.970> to<00:17:30.120> be<00:17:30.240> able<00:17:30.330> to<00:17:30.540> show<00:17:31.250> some 00:17:32.240 --> 00:17:32.250 align:start position:0% going I'm going to be able to show some 00:17:32.250 --> 00:17:35.570 align:start position:0% going I'm going to be able to show some results<00:17:33.120> that<00:17:33.480> you<00:17:34.110> can<00:17:34.230> try<00:17:34.500> of<00:17:35.160> course<00:17:35.220> this 00:17:35.570 --> 00:17:35.580 align:start position:0% results that you can try of course this 00:17:35.580 --> 00:17:41.110 align:start position:0% results that you can try of course this is<00:17:35.730> going<00:17:35.880> to<00:17:36.060> be<00:17:36.210> an<00:17:36.480> ongoing<00:17:37.460> research<00:17:38.460> and 00:17:41.110 --> 00:17:41.120 align:start position:0% 00:17:41.120 --> 00:17:50.710 align:start position:0% yeah<00:17:42.120> so<00:17:47.300> if<00:17:48.300> you<00:17:48.480> if<00:17:48.660> you<00:17:48.780> have<00:17:48.900> any<00:17:49.050> feedback 00:17:50.710 --> 00:17:50.720 align:start position:0% yeah so if you if you have any feedback 00:17:50.720 --> 00:17:52.730 align:start position:0% yeah so if you if you have any feedback contact<00:17:51.720> me<00:17:51.870> I'm<00:17:52.050> going<00:17:52.350> to 00:17:52.730 --> 00:17:52.740 align:start position:0% contact me I'm going to 00:17:52.740 --> 00:17:55.700 align:start position:0% contact me I'm going to they're<00:17:53.070> pretty<00:17:53.820> the<00:17:54.289> community<00:17:55.289> man's<00:17:55.470> about 00:17:55.700 --> 00:17:55.710 align:start position:0% they're pretty the community man's about 00:17:55.710 --> 00:17:57.529 align:start position:0% they're pretty the community man's about the<00:17:56.070> details<00:17:56.429> of<00:17:56.549> this<00:17:56.760> model<00:17:57.120> because<00:17:57.390> I 00:17:57.529 --> 00:17:57.539 align:start position:0% the details of this model because I 00:17:57.539 --> 00:18:01.130 align:start position:0% the details of this model because I heard<00:17:58.380> that<00:17:58.860> I<00:17:59.669> didn't<00:18:00.539> answer<00:18:00.690> and<00:18:01.020> an 00:18:01.130 --> 00:18:01.140 align:start position:0% heard that I didn't answer and an 00:18:01.140 --> 00:18:03.350 align:start position:0% heard that I didn't answer and an advocate<00:18:01.559> questions<00:18:02.220> it<00:18:02.370> is<00:18:02.399> short<00:18:02.730> talk<00:18:02.940> but 00:18:03.350 --> 00:18:03.360 align:start position:0% advocate questions it is short talk but 00:18:03.360 --> 00:18:05.779 align:start position:0% advocate questions it is short talk but I'm<00:18:03.870> going<00:18:04.409> to<00:18:04.529> put<00:18:04.710> up<00:18:04.830> to<00:18:05.370> that<00:18:05.549> when<00:18:05.700> you 00:18:05.779 --> 00:18:05.789 align:start position:0% I'm going to put up to that when you 00:18:05.789 --> 00:18:09.440 align:start position:0% I'm going to put up to that when you documents<00:18:06.240> to<00:18:06.360> my<00:18:06.450> github<00:18:06.720> page<00:18:07.080> and<00:18:08.450> I'm 00:18:09.440 --> 00:18:09.450 align:start position:0% documents to my github page and I'm 00:18:09.450 --> 00:18:12.380 align:start position:0% documents to my github page and I'm going<00:18:09.779> to<00:18:10.279> announce<00:18:11.279> them<00:18:11.580> on<00:18:11.700> Twitter<00:18:12.090> and 00:18:12.380 --> 00:18:12.390 align:start position:0% going to announce them on Twitter and 00:18:12.390 --> 00:18:16.720 align:start position:0% going to announce them on Twitter and everywhere<00:18:13.200> and<00:18:13.529> I<00:18:14.399> would<00:18:14.850> really<00:18:15.090> like<00:18:15.330> to 00:18:16.720 --> 00:18:16.730 align:start position:0% everywhere and I would really like to 00:18:16.730 --> 00:18:20.299 align:start position:0% everywhere and I would really like to make<00:18:17.730> this<00:18:17.880> model<00:18:18.270> usable<00:18:18.720> vote<00:18:18.960> for<00:18:19.309> for 00:18:20.299 --> 00:18:20.309 align:start position:0% make this model usable vote for for 00:18:20.309 --> 00:18:22.760 align:start position:0% make this model usable vote for for going<00:18:20.580> to<00:18:20.850> even<00:18:21.179> the<00:18:21.330> Gateway<00:18:21.690> plant<00:18:22.169> and<00:18:22.380> also 00:18:22.760 --> 00:18:22.770 align:start position:0% going to even the Gateway plant and also 00:18:22.770 --> 00:18:26.029 align:start position:0% going to even the Gateway plant and also for<00:18:23.070> our<00:18:23.630> future<00:18:24.630> light<00:18:24.809> bands<00:18:25.110> of<00:18:25.380> material<00:18:25.799> - 00:18:26.029 --> 00:18:26.039 align:start position:0% for our future light bands of material - 00:18:26.039 --> 00:18:28.730 align:start position:0% for our future light bands of material - and<00:18:27.020> that<00:18:28.020> was<00:18:28.169> it<00:18:28.230> thank<00:18:28.440> you<00:18:28.470> for<00:18:28.529> your 00:18:28.730 --> 00:18:28.740 align:start position:0% and that was it thank you for your 00:18:28.740 --> 00:18:37.370 align:start position:0% and that was it thank you for your attention 00:18:37.370 --> 00:18:37.380 align:start position:0% 00:18:37.380 --> 00:18:51.060 align:start position:0% one<00:18:47.010> thread<00:18:48.010> I<00:18:48.280> do<00:18:48.490> a<00:18:48.760> mystery<00:18:50.010> how<00:18:51.010> the 00:18:51.060 --> 00:18:51.070 align:start position:0% one thread I do a mystery how the 00:18:51.070 --> 00:18:53.520 align:start position:0% one thread I do a mystery how the payments<00:18:51.550> work<00:18:51.700> well<00:18:52.210> so<00:18:53.110> this<00:18:53.320> business 00:18:53.520 --> 00:18:53.530 align:start position:0% payments work well so this business 00:18:53.530 --> 00:18:59.940 align:start position:0% payments work well so this business model<00:18:53.860> is<00:18:56.940> so<00:18:57.940> it<00:18:58.180> had<00:18:58.390> worked<00:18:58.630> with<00:18:58.740> any<00:18:59.740> kind 00:18:59.940 --> 00:18:59.950 align:start position:0% model is so it had worked with any kind 00:18:59.950 --> 00:19:03.540 align:start position:0% model is so it had worked with any kind of<00:18:59.980> payment<00:19:00.190> technologies<00:19:00.910> I<00:19:01.540> was<00:19:02.550> looking 00:19:03.540 --> 00:19:03.550 align:start position:0% of payment technologies I was looking 00:19:03.550 --> 00:19:08.430 align:start position:0% of payment technologies I was looking into<00:19:03.760> using<00:19:05.490> radar<00:19:06.490> and<00:19:07.210> now<00:19:07.570> this<00:19:07.870> whole<00:19:08.170> team 00:19:08.430 --> 00:19:08.440 align:start position:0% into using radar and now this whole team 00:19:08.440 --> 00:19:10.980 align:start position:0% into using radar and now this whole team also<00:19:08.650> has<00:19:08.980> a<00:19:09.010> base<00:19:09.640> web<00:19:09.910> protocol<00:19:10.390> that's<00:19:10.570> also 00:19:10.980 --> 00:19:10.990 align:start position:0% also has a base web protocol that's also 00:19:10.990 --> 00:19:15.330 align:start position:0% also has a base web protocol that's also a<00:19:12.570> an<00:19:13.570> interesting<00:19:14.140> dimension<00:19:14.350> of<00:19:14.770> technology 00:19:15.330 --> 00:19:15.340 align:start position:0% a an interesting dimension of technology 00:19:15.340 --> 00:19:17.970 align:start position:0% a an interesting dimension of technology but<00:19:15.940> I<00:19:16.330> think<00:19:16.630> we<00:19:16.780> can<00:19:16.930> even<00:19:17.050> start<00:19:17.350> is<00:19:17.530> because 00:19:17.970 --> 00:19:17.980 align:start position:0% but I think we can even start is because 00:19:17.980 --> 00:19:20.910 align:start position:0% but I think we can even start is because I<00:19:18.310> said<00:19:18.550> simple<00:19:19.410> payments<00:19:20.410> which<00:19:20.620> are<00:19:20.740> really 00:19:20.910 --> 00:19:20.920 align:start position:0% I said simple payments which are really 00:19:20.920 --> 00:19:24.330 align:start position:0% I said simple payments which are really easy<00:19:21.190> to<00:19:21.460> do<00:19:21.700> and<00:19:22.350> yes<00:19:23.350> also<00:19:23.800> the<00:19:23.980> model 00:19:24.330 --> 00:19:24.340 align:start position:0% easy to do and yes also the model 00:19:24.340 --> 00:19:32.150 align:start position:0% easy to do and yes also the model doesn't<00:19:24.520> depend<00:19:25.030> on<00:19:25.180> the<00:19:25.360> payment<00:19:26.100> technology 00:19:32.150 --> 00:19:32.160 align:start position:0% 00:19:32.160 --> 00:19:36.480 align:start position:0% just<00:19:33.160> service<00:19:33.760> to<00:19:33.850> testament<00:19:34.300> and<00:19:35.130> notes<00:19:36.130> also 00:19:36.480 --> 00:19:36.490 align:start position:0% just service to testament and notes also 00:19:36.490 --> 00:19:38.760 align:start position:0% just service to testament and notes also every<00:19:36.760> server<00:19:37.120> has<00:19:37.270> also<00:19:37.630> spoken<00:19:38.110> and<00:19:38.500> they 00:19:38.760 --> 00:19:38.770 align:start position:0% every server has also spoken and they 00:19:38.770 --> 00:19:40.620 align:start position:0% every server has also spoken and they are<00:19:38.890> only<00:19:39.070> a<00:19:39.190> country<00:19:39.550> locally<00:19:40.150> on<00:19:40.270> the<00:19:40.390> server 00:19:40.620 --> 00:19:40.630 align:start position:0% are only a country locally on the server 00:19:40.630 --> 00:19:42.810 align:start position:0% are only a country locally on the server and<00:19:41.170> I'm<00:19:41.740> not<00:19:41.950> sure<00:19:42.100> yet<00:19:42.220> whether<00:19:42.460> they<00:19:42.760> should 00:19:42.810 --> 00:19:42.820 align:start position:0% and I'm not sure yet whether they should 00:19:42.820 --> 00:19:45.570 align:start position:0% and I'm not sure yet whether they should be<00:19:43.440> tradable<00:19:44.440> transferable 00:19:45.570 --> 00:19:45.580 align:start position:0% be tradable transferable 00:19:45.580 --> 00:19:59.640 align:start position:0% be tradable transferable that's<00:19:46.320> what's<00:19:47.320> that<00:19:57.450> yes<00:19:58.450> so<00:19:58.720> the<00:19:59.440> server 00:19:59.640 --> 00:19:59.650 align:start position:0% that's what's that yes so the server 00:19:59.650 --> 00:20:01.950 align:start position:0% that's what's that yes so the server will<00:20:00.250> so<00:20:00.640> if<00:20:00.760> you<00:20:00.880> stand<00:20:01.150> either<00:20:01.390> to<00:20:01.690> a<00:20:01.720> server 00:20:01.950 --> 00:20:01.960 align:start position:0% will so if you stand either to a server 00:20:01.960 --> 00:20:03.930 align:start position:0% will so if you stand either to a server or<00:20:02.080> die<00:20:02.350> or<00:20:02.590> whatever<00:20:03.040> but<00:20:03.310> this<00:20:03.490> are<00:20:03.670> we<00:20:03.760> want 00:20:03.930 --> 00:20:03.940 align:start position:0% or die or whatever but this are we want 00:20:03.940 --> 00:20:06.030 align:start position:0% or die or whatever but this are we want to<00:20:04.060> accept<00:20:04.390> that<00:20:04.870> then<00:20:05.140> we<00:20:05.290> are<00:20:05.440> going<00:20:05.680> to<00:20:05.770> have 00:20:06.030 --> 00:20:06.040 align:start position:0% to accept that then we are going to have 00:20:06.040 --> 00:20:09.360 align:start position:0% to accept that then we are going to have an<00:20:06.250> ether<00:20:06.400> or<00:20:06.640> die<00:20:06.850> or<00:20:07.270> the<00:20:07.450> server<00:20:07.690> and<00:20:08.220> as<00:20:09.220> I 00:20:09.360 --> 00:20:09.370 align:start position:0% an ether or die or the server and as I 00:20:09.370 --> 00:20:12.510 align:start position:0% an ether or die or the server and as I said<00:20:09.640> you<00:20:10.060> have<00:20:10.090> to<00:20:10.450> explicitly<00:20:10.890> say<00:20:11.890> okay<00:20:12.250> now 00:20:12.510 --> 00:20:12.520 align:start position:0% said you have to explicitly say okay now 00:20:12.520 --> 00:20:15.660 align:start position:0% said you have to explicitly say okay now I<00:20:13.330> have<00:20:13.540> eaten<00:20:13.960> with<00:20:14.260> you<00:20:14.380> and<00:20:14.680> I<00:20:14.800> want<00:20:15.040> to<00:20:15.220> work 00:20:15.660 --> 00:20:15.670 align:start position:0% I have eaten with you and I want to work 00:20:15.670 --> 00:20:23.180 align:start position:0% I have eaten with you and I want to work some<00:20:16.060> of<00:20:16.150> it 00:20:23.180 --> 00:20:23.190 align:start position:0% 00:20:23.190 --> 00:20:32.180 align:start position:0% [Applause] 00:20:32.180 --> 00:20:32.190 align:start position:0% 00:20:32.190 --> 00:20:34.250 align:start position:0% you