WEBVTT Kind: captions Language: en 00:00:18.890 --> 00:00:22.940 align:start position:0% so<00:00:19.890> thanks<00:00:20.280> everyone<00:00:21.020> my<00:00:22.020> name<00:00:22.290> is<00:00:22.320> Jeff 00:00:22.940 --> 00:00:22.950 align:start position:0% so thanks everyone my name is Jeff 00:00:22.950 --> 00:00:23.600 align:start position:0% so thanks everyone my name is Jeff attack 00:00:23.600 --> 00:00:23.610 align:start position:0% attack 00:00:23.610 --> 00:00:26.570 align:start position:0% attack I'm<00:00:23.730> a<00:00:24.110> researcher<00:00:25.110> at<00:00:25.290> inria<00:00:25.950> which<00:00:26.279> is<00:00:26.430> the 00:00:26.570 --> 00:00:26.580 align:start position:0% I'm a researcher at inria which is the 00:00:26.580 --> 00:00:29.480 align:start position:0% I'm a researcher at inria which is the French<00:00:26.880> national<00:00:27.860> research<00:00:28.860> institute<00:00:29.460> for 00:00:29.480 --> 00:00:29.490 align:start position:0% French national research institute for 00:00:29.490 --> 00:00:32.960 align:start position:0% French national research institute for computer<00:00:30.480> science<00:00:30.930> and<00:00:31.860> my<00:00:32.669> research 00:00:32.960 --> 00:00:32.970 align:start position:0% computer science and my research 00:00:32.970 --> 00:00:34.880 align:start position:0% computer science and my research background<00:00:33.270> is<00:00:33.750> in<00:00:34.110> parallel<00:00:34.590> and 00:00:34.880 --> 00:00:34.890 align:start position:0% background is in parallel and 00:00:34.890 --> 00:00:37.549 align:start position:0% background is in parallel and distributed<00:00:34.920> computing<00:00:35.750> with<00:00:36.750> a<00:00:36.870> focus<00:00:37.320> on 00:00:37.549 --> 00:00:37.559 align:start position:0% distributed computing with a focus on 00:00:37.559 --> 00:00:39.979 align:start position:0% distributed computing with a focus on how<00:00:37.800> to<00:00:37.860> build<00:00:38.480> distributed<00:00:39.480> computing 00:00:39.979 --> 00:00:39.989 align:start position:0% how to build distributed computing 00:00:39.989 --> 00:00:42.979 align:start position:0% how to build distributed computing infrastructure<00:00:41.030> under<00:00:42.030> using<00:00:42.449> Internet 00:00:42.979 --> 00:00:42.989 align:start position:0% infrastructure under using Internet 00:00:42.989 --> 00:00:46.369 align:start position:0% infrastructure under using Internet resources<00:00:44.180> the<00:00:45.180> work<00:00:45.510> I'm<00:00:45.720> going<00:00:45.750> to<00:00:46.170> present 00:00:46.369 --> 00:00:46.379 align:start position:0% resources the work I'm going to present 00:00:46.379 --> 00:00:48.520 align:start position:0% resources the work I'm going to present today<00:00:46.710> is<00:00:46.920> actually<00:00:47.159> a<00:00:47.460> joint<00:00:47.729> work<00:00:47.970> with 00:00:48.520 --> 00:00:48.530 align:start position:0% today is actually a joint work with 00:00:48.530 --> 00:00:51.020 align:start position:0% today is actually a joint work with Hyrule<00:00:49.530> hair<00:00:49.769> from<00:00:50.070> the<00:00:50.220> Chinese<00:00:50.550> Academy<00:00:50.790> of 00:00:51.020 --> 00:00:51.030 align:start position:0% Hyrule hair from the Chinese Academy of 00:00:51.030 --> 00:00:51.590 align:start position:0% Hyrule hair from the Chinese Academy of Science 00:00:51.590 --> 00:00:51.600 align:start position:0% Science 00:00:51.600 --> 00:00:54.770 align:start position:0% Science I<00:00:51.690> don't<00:00:52.229> know<00:00:52.320> if<00:00:52.440> I<00:00:52.620> will<00:00:52.830> you<00:00:52.979> are<00:00:53.100> here<00:00:53.780> yes 00:00:54.770 --> 00:00:54.780 align:start position:0% I don't know if I will you are here yes 00:00:54.780 --> 00:01:01.189 align:start position:0% I don't know if I will you are here yes he<00:00:55.110> also<00:00:55.260> is<00:00:55.769> the<00:00:55.830> guy<00:00:56.129> here<00:00:57.350> and<00:00:59.870> this<00:01:00.870> talk 00:01:01.189 --> 00:01:01.199 align:start position:0% he also is the guy here and this talk 00:01:01.199 --> 00:01:03.799 align:start position:0% he also is the guy here and this talk today<00:01:01.440> is<00:01:01.860> about<00:01:02.339> how<00:01:02.879> we<00:01:02.940> can<00:01:03.059> build<00:01:03.479> a 00:01:03.799 --> 00:01:03.809 align:start position:0% today is about how we can build a 00:01:03.809 --> 00:01:05.870 align:start position:0% today is about how we can build a blockchain<00:01:04.260> but<00:01:04.589> fully<00:01:04.860> distributed<00:01:05.610> and 00:01:05.870 --> 00:01:05.880 align:start position:0% blockchain but fully distributed and 00:01:05.880 --> 00:01:10.070 align:start position:0% blockchain but fully distributed and cloud<00:01:06.870> and<00:01:07.860> what<00:01:08.220> would<00:01:08.700> like<00:01:08.880> to<00:01:09.150> my<00:01:09.870> goal 00:01:10.070 --> 00:01:10.080 align:start position:0% cloud and what would like to my goal 00:01:10.080 --> 00:01:12.710 align:start position:0% cloud and what would like to my goal today<00:01:10.650> is<00:01:11.010> to<00:01:11.100> give<00:01:11.640> you<00:01:11.820> a<00:01:11.850> perspective<00:01:12.180> from 00:01:12.710 --> 00:01:12.720 align:start position:0% today is to give you a perspective from 00:01:12.720 --> 00:01:14.810 align:start position:0% today is to give you a perspective from the<00:01:12.840> infrastructure<00:01:13.500> point<00:01:13.950> of<00:01:14.130> view<00:01:14.280> which<00:01:14.640> i 00:01:14.810 --> 00:01:14.820 align:start position:0% the infrastructure point of view which i 00:01:14.820 --> 00:01:19.190 align:start position:0% the infrastructure point of view which i think<00:01:15.030> is<00:01:15.360> very<00:01:15.830> important<00:01:17.299> so<00:01:18.299> as<00:01:18.720> you<00:01:19.020> know 00:01:19.190 --> 00:01:19.200 align:start position:0% think is very important so as you know 00:01:19.200 --> 00:01:21.560 align:start position:0% think is very important so as you know if<00:01:19.620> Iran<00:01:20.100> allows<00:01:20.790> you<00:01:20.940> to<00:01:21.120> develop<00:01:21.450> this 00:01:21.560 --> 00:01:21.570 align:start position:0% if Iran allows you to develop this 00:01:21.570 --> 00:01:23.000 align:start position:0% if Iran allows you to develop this trivial<00:01:21.900> application<00:01:22.010> distributed 00:01:23.000 --> 00:01:23.010 align:start position:0% trivial application distributed 00:01:23.010 --> 00:01:25.220 align:start position:0% trivial application distributed application<00:01:23.670> and<00:01:23.880> systems<00:01:24.450> that<00:01:24.690> run<00:01:24.840> on<00:01:25.050> the 00:01:25.220 --> 00:01:25.230 align:start position:0% application and systems that run on the 00:01:25.230 --> 00:01:28.190 align:start position:0% application and systems that run on the blockchain<00:01:25.470> and<00:01:26.120> the<00:01:27.120> blockchain<00:01:27.390> gives<00:01:28.050> this 00:01:28.190 --> 00:01:28.200 align:start position:0% blockchain and the blockchain gives this 00:01:28.200 --> 00:01:30.460 align:start position:0% blockchain and the blockchain gives this application<00:01:29.010> of<00:01:29.190> some<00:01:29.460> very<00:01:29.670> nice<00:01:29.880> properties 00:01:30.460 --> 00:01:30.470 align:start position:0% application of some very nice properties 00:01:30.470 --> 00:01:32.420 align:start position:0% application of some very nice properties applications<00:01:31.470> are<00:01:31.680> going<00:01:31.710> to<00:01:31.950> be<00:01:32.040> autonomous 00:01:32.420 --> 00:01:32.430 align:start position:0% applications are going to be autonomous 00:01:32.430 --> 00:01:35.420 align:start position:0% applications are going to be autonomous they<00:01:33.240> are<00:01:33.330> going<00:01:33.450> to<00:01:33.810> be<00:01:34.020> a<00:01:34.050> resilient<00:01:34.860> secure 00:01:35.420 --> 00:01:35.430 align:start position:0% they are going to be a resilient secure 00:01:35.430 --> 00:01:37.400 align:start position:0% they are going to be a resilient secure and<00:01:35.730> then<00:01:36.030> there's<00:01:36.240> also<00:01:36.480> these<00:01:36.750> distributed 00:01:37.400 --> 00:01:37.410 align:start position:0% and then there's also these distributed 00:01:37.410 --> 00:01:39.650 align:start position:0% and then there's also these distributed consensus<00:01:37.980> so<00:01:38.940> that's<00:01:39.120> a<00:01:39.210> great<00:01:39.390> thing 00:01:39.650 --> 00:01:39.660 align:start position:0% consensus so that's a great thing 00:01:39.660 --> 00:01:41.540 align:start position:0% consensus so that's a great thing that's<00:01:39.960> great<00:01:40.230> promises<00:01:40.650> and<00:01:41.040> particular 00:01:41.540 --> 00:01:41.550 align:start position:0% that's great promises and particular 00:01:41.550 --> 00:01:42.620 align:start position:0% that's great promises and particular sometimes<00:01:41.790> we<00:01:41.970> are<00:01:42.030> talking<00:01:42.360> about<00:01:42.480> a 00:01:42.620 --> 00:01:42.630 align:start position:0% sometimes we are talking about a 00:01:42.630 --> 00:01:45.950 align:start position:0% sometimes we are talking about a supercomputer<00:01:44.000> but<00:01:45.000> actually<00:01:45.660> what's 00:01:45.950 --> 00:01:45.960 align:start position:0% supercomputer but actually what's 00:01:45.960 --> 00:01:47.780 align:start position:0% supercomputer but actually what's happening<00:01:46.440> when<00:01:46.920> you<00:01:47.040> try<00:01:47.280> to<00:01:47.340> move<00:01:47.610> your 00:01:47.780 --> 00:01:47.790 align:start position:0% happening when you try to move your 00:01:47.790 --> 00:01:50.540 align:start position:0% happening when you try to move your existing<00:01:47.990> application<00:01:48.990> to<00:01:49.920> the<00:01:50.070> blockchain 00:01:50.540 --> 00:01:50.550 align:start position:0% existing application to the blockchain 00:01:50.550 --> 00:01:53.240 align:start position:0% existing application to the blockchain is<00:01:50.730> that<00:01:51.330> you<00:01:51.510> face<00:01:51.780> the<00:01:52.020> fact<00:01:52.050> that<00:01:52.380> in<00:01:52.890> fact 00:01:53.240 --> 00:01:53.250 align:start position:0% is that you face the fact that in fact 00:01:53.250 --> 00:01:55.820 align:start position:0% is that you face the fact that in fact you<00:01:53.400> are<00:01:53.430> offered<00:01:53.880> very<00:01:54.270> limited<00:01:54.830> computing 00:01:55.820 --> 00:01:55.830 align:start position:0% you are offered very limited computing 00:01:55.830 --> 00:01:59.060 align:start position:0% you are offered very limited computing capacities<00:01:57.170> offense<00:01:58.170> and<00:01:58.350> storage<00:01:58.680> is<00:01:58.800> quite 00:01:59.060 --> 00:01:59.070 align:start position:0% capacities offense and storage is quite 00:01:59.070 --> 00:02:01.460 align:start position:0% capacities offense and storage is quite expensive<00:01:59.430> it<00:01:59.880> spare<00:02:00.240> you<00:02:00.990> have<00:02:01.080> a<00:02:01.170> slower 00:02:01.460 --> 00:02:01.470 align:start position:0% expensive it spare you have a slower 00:02:01.470 --> 00:02:04.250 align:start position:0% expensive it spare you have a slower execution<00:02:02.370> very<00:02:02.670> high<00:02:02.909> latency<00:02:03.510> if<00:02:03.870> you<00:02:04.080> need 00:02:04.250 --> 00:02:04.260 align:start position:0% execution very high latency if you need 00:02:04.260 --> 00:02:06.590 align:start position:0% execution very high latency if you need communication<00:02:04.680> through<00:02:05.190> the<00:02:05.600> transaction 00:02:06.590 --> 00:02:06.600 align:start position:0% communication through the transaction 00:02:06.600 --> 00:02:12.490 align:start position:0% communication through the transaction and<00:02:07.050> so<00:02:07.409> that's<00:02:07.590> really<00:02:07.650> a<00:02:07.860> limitation 00:02:12.490 --> 00:02:12.500 align:start position:0% 00:02:12.500 --> 00:02:15.690 align:start position:0% and<00:02:12.920> so<00:02:13.280> and<00:02:14.060> so<00:02:14.240> the<00:02:14.360> question<00:02:14.720> he<00:02:15.080> is<00:02:15.110> a 00:02:15.690 --> 00:02:15.700 align:start position:0% and so and so the question he is a 00:02:15.700 --> 00:02:19.180 align:start position:0% and so and so the question he is a hooker<00:02:16.700> and<00:02:16.850> with<00:02:17.060> I<00:02:17.570> mean<00:02:18.140> I<00:02:18.590> live<00:02:18.890> yet<00:02:19.040> this 00:02:19.180 --> 00:02:19.190 align:start position:0% hooker and with I mean I live yet this 00:02:19.190 --> 00:02:22.660 align:start position:0% hooker and with I mean I live yet this and<00:02:19.430> that's<00:02:20.420> especially<00:02:21.080> an<00:02:21.620> issue<00:02:21.890> if<00:02:22.400> you 00:02:22.660 --> 00:02:22.670 align:start position:0% and that's especially an issue if you 00:02:22.670 --> 00:02:25.330 align:start position:0% and that's especially an issue if you consider<00:02:23.060> the<00:02:23.270> fact<00:02:23.540> that<00:02:23.830> there<00:02:24.830> is<00:02:24.980> a<00:02:25.010> huge 00:02:25.330 --> 00:02:25.340 align:start position:0% consider the fact that there is a huge 00:02:25.340 --> 00:02:28.510 align:start position:0% consider the fact that there is a huge computing<00:02:26.060> power<00:02:26.330> which<00:02:27.080> is<00:02:27.380> given<00:02:27.920> by<00:02:28.280> all 00:02:28.510 --> 00:02:28.520 align:start position:0% computing power which is given by all 00:02:28.520 --> 00:02:31.420 align:start position:0% computing power which is given by all these<00:02:28.790> are<00:02:29.030> the<00:02:29.450> miners<00:02:29.980> so<00:02:30.980> there's<00:02:31.190> really<00:02:31.340> a 00:02:31.420 --> 00:02:31.430 align:start position:0% these are the miners so there's really a 00:02:31.430 --> 00:02:33.940 align:start position:0% these are the miners so there's really a gap<00:02:31.730> and<00:02:32.000> the<00:02:32.450> objective<00:02:32.900> of<00:02:33.110> this<00:02:33.500> work<00:02:33.740> is<00:02:33.920> so 00:02:33.940 --> 00:02:33.950 align:start position:0% gap and the objective of this work is so 00:02:33.950 --> 00:02:36.970 align:start position:0% gap and the objective of this work is so to<00:02:34.850> try<00:02:35.120> to<00:02:35.150> give<00:02:35.600> all<00:02:35.870> this<00:02:36.170> computing<00:02:36.710> power 00:02:36.970 --> 00:02:36.980 align:start position:0% to try to give all this computing power 00:02:36.980 --> 00:02:40.140 align:start position:0% to try to give all this computing power back<00:02:37.550> to<00:02:37.730> the<00:02:37.760> application<00:02:38.390> that<00:02:38.600> needs<00:02:39.110> it<00:02:39.290> so 00:02:40.140 --> 00:02:40.150 align:start position:0% back to the application that needs it so 00:02:40.150 --> 00:02:43.960 align:start position:0% back to the application that needs it so the<00:02:41.150> objective<00:02:41.570> of<00:02:41.750> i<00:02:42.170> exac<00:02:42.650> is<00:02:42.890> to<00:02:43.520> provide 00:02:43.960 --> 00:02:43.970 align:start position:0% the objective of i exac is to provide 00:02:43.970 --> 00:02:45.670 align:start position:0% the objective of i exac is to provide blockchain<00:02:44.450> by<00:02:44.570> distributed<00:02:45.140> application 00:02:45.670 --> 00:02:45.680 align:start position:0% blockchain by distributed application 00:02:45.680 --> 00:02:49.030 align:start position:0% blockchain by distributed application access<00:02:46.160> to<00:02:46.400> ocean<00:02:47.150> computing<00:02:47.630> resources<00:02:48.110> when 00:02:49.030 --> 00:02:49.040 align:start position:0% access to ocean computing resources when 00:02:49.040 --> 00:02:50.920 align:start position:0% access to ocean computing resources when they<00:02:49.220> need<00:02:49.430> it<00:02:49.640> so<00:02:49.850> in<00:02:50.209> terms<00:02:50.420> of<00:02:50.540> computing 00:02:50.920 --> 00:02:50.930 align:start position:0% they need it so in terms of computing 00:02:50.930 --> 00:02:53.500 align:start position:0% they need it so in terms of computing resources<00:02:50.990> were<00:02:51.560> thinking<00:02:51.890> about<00:02:52.010> CPU<00:02:52.700> we<00:02:53.450> are 00:02:53.500 --> 00:02:53.510 align:start position:0% resources were thinking about CPU we are 00:02:53.510 --> 00:02:56.110 align:start position:0% resources were thinking about CPU we are thinking<00:02:53.810> about<00:02:54.050> data<00:02:54.290> access<00:02:55.120> application 00:02:56.110 --> 00:02:56.120 align:start position:0% thinking about data access application 00:02:56.120 --> 00:02:58.449 align:start position:0% thinking about data access application in<00:02:56.360> particular<00:02:56.900> focusing<00:02:57.410> on<00:02:57.459> compute 00:02:58.449 --> 00:02:58.459 align:start position:0% in particular focusing on compute 00:02:58.459 --> 00:03:00.970 align:start position:0% in particular focusing on compute intensive<00:02:58.640> application<00:02:59.510> services<00:03:00.500> and<00:03:00.770> so 00:03:00.970 --> 00:03:00.980 align:start position:0% intensive application services and so 00:03:00.980 --> 00:03:04.360 align:start position:0% intensive application services and so forth<00:03:01.010> and<00:03:01.810> to<00:03:02.810> do<00:03:02.959> this<00:03:03.110> of<00:03:03.380> course<00:03:03.410> we<00:03:04.190> can 00:03:04.360 --> 00:03:04.370 align:start position:0% forth and to do this of course we can 00:03:04.370 --> 00:03:06.460 align:start position:0% forth and to do this of course we can take<00:03:04.580> advantage<00:03:04.700> of<00:03:05.150> the<00:03:05.330> blockchain<00:03:05.570> and<00:03:05.930> try 00:03:06.460 --> 00:03:06.470 align:start position:0% take advantage of the blockchain and try 00:03:06.470 --> 00:03:08.380 align:start position:0% take advantage of the blockchain and try to<00:03:06.530> organize<00:03:06.709> a<00:03:07.100> global<00:03:07.670> market<00:03:08.360> for 00:03:08.380 --> 00:03:08.390 align:start position:0% to organize a global market for 00:03:08.390 --> 00:03:10.900 align:start position:0% to organize a global market for computing<00:03:09.020> resources<00:03:09.500> so<00:03:10.250> think<00:03:10.640> it<00:03:10.760> as<00:03:10.880> a 00:03:10.900 --> 00:03:10.910 align:start position:0% computing resources so think it as a 00:03:10.910 --> 00:03:13.360 align:start position:0% computing resources so think it as a kind<00:03:11.209> of<00:03:11.360> Airbnb<00:03:12.290> for<00:03:12.530> servers<00:03:13.070> where 00:03:13.360 --> 00:03:13.370 align:start position:0% kind of Airbnb for servers where 00:03:13.370 --> 00:03:15.340 align:start position:0% kind of Airbnb for servers where everyone<00:03:14.150> would<00:03:14.300> be<00:03:14.450> able<00:03:14.540> to<00:03:14.690> put<00:03:15.020> its<00:03:15.200> own 00:03:15.340 --> 00:03:15.350 align:start position:0% everyone would be able to put its own 00:03:15.350 --> 00:03:18.610 align:start position:0% everyone would be able to put its own servers<00:03:15.800> and<00:03:16.010> use<00:03:16.190> someone<00:03:17.090> else<00:03:17.269> evers<00:03:17.720> and 00:03:18.610 --> 00:03:18.620 align:start position:0% servers and use someone else evers and 00:03:18.620 --> 00:03:20.440 align:start position:0% servers and use someone else evers and so<00:03:18.769> that's<00:03:18.950> still<00:03:19.130> a<00:03:19.190> cloud<00:03:19.519> in<00:03:19.820> the<00:03:20.030> sense 00:03:20.440 --> 00:03:20.450 align:start position:0% so that's still a cloud in the sense 00:03:20.450 --> 00:03:22.750 align:start position:0% so that's still a cloud in the sense that<00:03:20.570> you<00:03:21.290> access<00:03:21.860> through<00:03:22.340> the<00:03:22.489> blockchain 00:03:22.750 --> 00:03:22.760 align:start position:0% that you access through the blockchain 00:03:22.760 --> 00:03:25.840 align:start position:0% that you access through the blockchain to<00:03:23.540> the<00:03:23.660> computing<00:03:24.080> resources<00:03:24.590> on<00:03:24.950> demand<00:03:25.640> and 00:03:25.840 --> 00:03:25.850 align:start position:0% to the computing resources on demand and 00:03:25.850 --> 00:03:29.199 align:start position:0% to the computing resources on demand and as<00:03:26.690> a<00:03:26.720> payoff<00:03:27.110> as<00:03:27.590> a<00:03:27.980> pay-as-you-go<00:03:28.250> basis<00:03:28.970> and 00:03:29.199 --> 00:03:29.209 align:start position:0% as a payoff as a pay-as-you-go basis and 00:03:29.209 --> 00:03:32.350 align:start position:0% as a payoff as a pay-as-you-go basis and so<00:03:29.989> this<00:03:30.140> idea<00:03:30.290> of<00:03:30.620> building<00:03:31.489> a<00:03:31.700> distributed 00:03:32.350 --> 00:03:32.360 align:start position:0% so this idea of building a distributed 00:03:32.360 --> 00:03:35.410 align:start position:0% so this idea of building a distributed cloud<00:03:32.510> is<00:03:32.870> actually<00:03:33.050> very<00:03:33.650> timely<00:03:34.130> at<00:03:35.060> the 00:03:35.410 --> 00:03:35.420 align:start position:0% cloud is actually very timely at the 00:03:35.420 --> 00:03:37.000 align:start position:0% cloud is actually very timely at the moment<00:03:35.750> what's<00:03:35.989> happening<00:03:36.290> with<00:03:36.470> the<00:03:36.650> cloud 00:03:37.000 --> 00:03:37.010 align:start position:0% moment what's happening with the cloud 00:03:37.010 --> 00:03:39.040 align:start position:0% moment what's happening with the cloud computing<00:03:37.160> is<00:03:37.700> that<00:03:37.880> very<00:03:38.180> centralized<00:03:38.840> on 00:03:39.040 --> 00:03:39.050 align:start position:0% computing is that very centralized on 00:03:39.050 --> 00:03:43.240 align:start position:0% computing is that very centralized on data<00:03:39.680> servers<00:03:40.340> and<00:03:40.690> big<00:03:41.690> data<00:03:41.900> centers<00:03:42.590> and<00:03:42.830> I 00:03:43.240 --> 00:03:43.250 align:start position:0% data servers and big data centers and I 00:03:43.250 --> 00:03:44.770 align:start position:0% data servers and big data centers and I don't<00:03:43.489> know<00:03:43.700> what<00:03:43.850> the<00:03:43.970> situation<00:03:44.120> your 00:03:44.770 --> 00:03:44.780 align:start position:0% don't know what the situation your 00:03:44.780 --> 00:03:46.960 align:start position:0% don't know what the situation your respective<00:03:45.290> countries<00:03:45.470> but<00:03:46.190> in<00:03:46.370> France<00:03:46.640> for 00:03:46.960 --> 00:03:46.970 align:start position:0% respective countries but in France for 00:03:46.970 --> 00:03:48.970 align:start position:0% respective countries but in France for instance<00:03:47.030> if<00:03:47.540> you<00:03:47.660> want<00:03:47.810> to<00:03:47.870> set<00:03:48.590> up<00:03:48.739> a<00:03:48.830> new 00:03:48.970 --> 00:03:48.980 align:start position:0% instance if you want to set up a new 00:03:48.980 --> 00:03:52.180 align:start position:0% instance if you want to set up a new data<00:03:49.160> center<00:03:49.640> in<00:03:49.730> Paris<00:03:50.060> area<00:03:50.680> the<00:03:51.680> answer<00:03:51.950> is 00:03:52.180 --> 00:03:52.190 align:start position:0% data center in Paris area the answer is 00:03:52.190 --> 00:03:54.520 align:start position:0% data center in Paris area the answer is simply<00:03:52.459> no<00:03:52.700> not<00:03:53.120> enough<00:03:53.420> room<00:03:53.630> not<00:03:54.260> enough 00:03:54.520 --> 00:03:54.530 align:start position:0% simply no not enough room not enough 00:03:54.530 --> 00:03:57.880 align:start position:0% simply no not enough room not enough power<00:03:54.709> forget<00:03:55.280> it<00:03:55.720> and<00:03:56.720> so<00:03:57.500> this<00:03:57.709> little 00:03:57.880 --> 00:03:57.890 align:start position:0% power forget it and so this little 00:03:57.890 --> 00:04:00.880 align:start position:0% power forget it and so this little situation<00:03:58.820> where<00:03:59.450> you<00:03:59.630> have<00:03:59.930> all<00:04:00.320> those<00:04:00.650> data 00:04:00.880 --> 00:04:00.890 align:start position:0% situation where you have all those data 00:04:00.890 --> 00:04:04.060 align:start position:0% situation where you have all those data centers<00:04:01.280> that<00:04:01.640> go<00:04:01.970> in<00:04:02.120> very<00:04:02.480> remote<00:04:02.750> area<00:04:03.410> you 00:04:04.060 --> 00:04:04.070 align:start position:0% centers that go in very remote area you 00:04:04.070 --> 00:04:06.160 align:start position:0% centers that go in very remote area you know<00:04:04.190> to<00:04:04.250> have<00:04:04.489> either<00:04:04.790> free<00:04:05.180> energy<00:04:05.630> or<00:04:05.780> free 00:04:06.160 --> 00:04:06.170 align:start position:0% know to have either free energy or free 00:04:06.170 --> 00:04:08.020 align:start position:0% know to have either free energy or free cooling<00:04:06.410> like<00:04:06.890> cheaper<00:04:07.340> energy<00:04:07.730> or<00:04:07.850> free 00:04:08.020 --> 00:04:08.030 align:start position:0% cooling like cheaper energy or free 00:04:08.030 --> 00:04:09.940 align:start position:0% cooling like cheaper energy or free cooling<00:04:08.239> like<00:04:08.720> Iceland<00:04:09.260> in<00:04:09.380> Europe<00:04:09.709> or 00:04:09.940 --> 00:04:09.950 align:start position:0% cooling like Iceland in Europe or 00:04:09.950 --> 00:04:10.810 align:start position:0% cooling like Iceland in Europe or tiburtina 00:04:10.810 --> 00:04:10.820 align:start position:0% tiburtina 00:04:10.820 --> 00:04:14.410 align:start position:0% tiburtina in<00:04:11.030> China<00:04:11.299> for<00:04:11.600> instance<00:04:11.750> and<00:04:12.560> so<00:04:13.420> distributed 00:04:14.410 --> 00:04:14.420 align:start position:0% in China for instance and so distributed 00:04:14.420 --> 00:04:17.349 align:start position:0% in China for instance and so distributed cloud<00:04:15.019> computing<00:04:15.590> is<00:04:15.709> also<00:04:16.220> about<00:04:16.459> relocating 00:04:17.349 --> 00:04:17.359 align:start position:0% cloud computing is also about relocating 00:04:17.359 --> 00:04:19.330 align:start position:0% cloud computing is also about relocating those<00:04:17.540> data<00:04:17.750> center<00:04:18.290> closer<00:04:18.830> to<00:04:19.100> the<00:04:19.220> data 00:04:19.330 --> 00:04:19.340 align:start position:0% those data center closer to the data 00:04:19.340 --> 00:04:21.430 align:start position:0% those data center closer to the data producer<00:04:20.000> and<00:04:20.090> consumer<00:04:20.239> and<00:04:20.959> just<00:04:21.169> to<00:04:21.260> give 00:04:21.430 --> 00:04:21.440 align:start position:0% producer and consumer and just to give 00:04:21.440 --> 00:04:23.920 align:start position:0% producer and consumer and just to give you<00:04:21.620> an<00:04:21.890> idea<00:04:22.220> of<00:04:22.610> you<00:04:22.820> know<00:04:22.940> how<00:04:23.450> we<00:04:23.750> could 00:04:23.920 --> 00:04:23.930 align:start position:0% you an idea of you know how we could 00:04:23.930 --> 00:04:26.230 align:start position:0% you an idea of you know how we could read<00:04:24.320> some<00:04:24.349> next-gen<00:04:25.250> data<00:04:25.550> center 00:04:26.230 --> 00:04:26.240 align:start position:0% read some next-gen data center 00:04:26.240 --> 00:04:28.390 align:start position:0% read some next-gen data center distributed<00:04:27.020> data<00:04:27.139> center<00:04:27.650> is<00:04:28.099> that<00:04:28.250> some 00:04:28.390 --> 00:04:28.400 align:start position:0% distributed data center is that some 00:04:28.400 --> 00:04:29.980 align:start position:0% distributed data center is that some picture<00:04:28.729> coming<00:04:29.090> from<00:04:29.300> people<00:04:29.690> who<00:04:29.870> are 00:04:29.980 --> 00:04:29.990 align:start position:0% picture coming from people who are 00:04:29.990 --> 00:04:32.080 align:start position:0% picture coming from people who are working<00:04:30.199> with<00:04:30.560> so<00:04:31.220> on<00:04:31.370> the<00:04:31.520> left<00:04:31.729> you<00:04:31.849> have<00:04:31.940> the 00:04:32.080 --> 00:04:32.090 align:start position:0% working with so on the left you have the 00:04:32.090 --> 00:04:34.240 align:start position:0% working with so on the left you have the Reuters<00:04:32.539> University<00:04:33.289> they<00:04:33.650> set<00:04:33.830> up<00:04:33.949> the<00:04:34.069> data 00:04:34.240 --> 00:04:34.250 align:start position:0% Reuters University they set up the data 00:04:34.250 --> 00:04:36.100 align:start position:0% Reuters University they set up the data center<00:04:34.759> on<00:04:34.880> the<00:04:34.970> roof<00:04:35.180> top<00:04:35.599> of<00:04:35.750> their<00:04:35.930> building 00:04:36.100 --> 00:04:36.110 align:start position:0% center on the roof top of their building 00:04:36.110 --> 00:04:38.680 align:start position:0% center on the roof top of their building with<00:04:36.830> solar<00:04:37.099> panel<00:04:37.520> and<00:04:37.729> this<00:04:37.819> is<00:04:38.000> fully<00:04:38.210> you 00:04:38.680 --> 00:04:38.690 align:start position:0% with solar panel and this is fully you 00:04:38.690 --> 00:04:40.480 align:start position:0% with solar panel and this is fully you know<00:04:38.780> low-power<00:04:39.110> processor<00:04:39.650> batteries<00:04:40.099> and 00:04:40.480 --> 00:04:40.490 align:start position:0% know low-power processor batteries and 00:04:40.490 --> 00:04:43.930 align:start position:0% know low-power processor batteries and this<00:04:40.699> is<00:04:40.819> fully<00:04:41.060> energy<00:04:41.930> autonomous<00:04:42.940> under 00:04:43.930 --> 00:04:43.940 align:start position:0% this is fully energy autonomous under 00:04:43.940 --> 00:04:45.460 align:start position:0% this is fully energy autonomous under right<00:04:44.360> oh<00:04:44.630> sorry 00:04:45.460 --> 00:04:45.470 align:start position:0% right oh sorry 00:04:45.470 --> 00:04:48.249 align:start position:0% right oh sorry on<00:04:45.590> my<00:04:45.800> left<00:04:46.009> and<00:04:46.819> so<00:04:46.970> on<00:04:47.120> your<00:04:47.270> right<00:04:47.690> this<00:04:48.110> is 00:04:48.249 --> 00:04:48.259 align:start position:0% on my left and so on your right this is 00:04:48.259 --> 00:04:49.719 align:start position:0% on my left and so on your right this is Colonel<00:04:48.440> computing<00:04:49.069> the<00:04:49.220> blackboard<00:04:49.669> that 00:04:49.719 --> 00:04:49.729 align:start position:0% Colonel computing the blackboard that 00:04:49.729 --> 00:04:51.909 align:start position:0% Colonel computing the blackboard that you<00:04:50.000> see<00:04:50.210> here<00:04:50.539> is<00:04:50.690> both<00:04:50.900> a<00:04:51.050> server<00:04:51.380> a<00:04:51.830> server 00:04:51.909 --> 00:04:51.919 align:start position:0% you see here is both a server a server 00:04:51.919 --> 00:04:55.600 align:start position:0% you see here is both a server a server and<00:04:52.759> a<00:04:52.819> heater<00:04:53.240> so<00:04:53.599> this<00:04:54.199> is<00:04:54.380> actually<00:04:54.949> the<00:04:55.069> CPU 00:04:55.600 --> 00:04:55.610 align:start position:0% and a heater so this is actually the CPU 00:04:55.610 --> 00:04:58.990 align:start position:0% and a heater so this is actually the CPU you<00:04:56.479> notice<00:04:56.780> the<00:04:57.020> CPU<00:04:57.440> energy<00:04:58.370> which<00:04:58.789> is 00:04:58.990 --> 00:04:59.000 align:start position:0% you notice the CPU energy which is 00:04:59.000 --> 00:05:01.270 align:start position:0% you notice the CPU energy which is warming<00:04:59.360> when<00:04:59.690> doing<00:04:59.990> 3d<00:05:00.409> rendering<00:05:00.919> which<00:05:01.159> is 00:05:01.270 --> 00:05:01.280 align:start position:0% warming when doing 3d rendering which is 00:05:01.280 --> 00:05:02.830 align:start position:0% warming when doing 3d rendering which is warming<00:05:01.580> your<00:05:01.759> apartment<00:05:02.210> during<00:05:02.449> winter 00:05:02.830 --> 00:05:02.840 align:start position:0% warming your apartment during winter 00:05:02.840 --> 00:05:04.809 align:start position:0% warming your apartment during winter winter<00:05:03.440> time<00:05:03.770> so<00:05:03.919> we<00:05:04.099> can<00:05:04.220> distribute<00:05:04.580> the 00:05:04.809 --> 00:05:04.819 align:start position:0% winter time so we can distribute the 00:05:04.819 --> 00:05:06.939 align:start position:0% winter time so we can distribute the data<00:05:04.940> sometimes<00:05:05.360> feasible<00:05:06.050> I'm<00:05:06.680> always 00:05:06.939 --> 00:05:06.949 align:start position:0% data sometimes feasible I'm always 00:05:06.949 --> 00:05:09.159 align:start position:0% data sometimes feasible I'm always coming<00:05:07.250> with<00:05:07.460> edge<00:05:07.669> for<00:05:07.940> computing<00:05:08.419> of<00:05:08.840> course 00:05:09.159 --> 00:05:09.169 align:start position:0% coming with edge for computing of course 00:05:09.169 --> 00:05:11.230 align:start position:0% coming with edge for computing of course the<00:05:09.380> goal<00:05:09.560> of<00:05:09.680> I<00:05:09.830> exactly<00:05:10.310> tooth<00:05:10.520> is<00:05:10.729> to<00:05:11.060> make 00:05:11.230 --> 00:05:11.240 align:start position:0% the goal of I exactly tooth is to make 00:05:11.240 --> 00:05:14.529 align:start position:0% the goal of I exactly tooth is to make those<00:05:12.280> not<00:05:13.280> be<00:05:13.490> able<00:05:13.669> to<00:05:13.729> to<00:05:14.150> to<00:05:14.180> add<00:05:14.360> those 00:05:14.529 --> 00:05:14.539 align:start position:0% those not be able to to to add those 00:05:14.539 --> 00:05:16.839 align:start position:0% those not be able to to to add those kind<00:05:14.810> of<00:05:14.870> it<00:05:15.020> right<00:05:15.169> so<00:05:15.319> to<00:05:15.620> be<00:05:15.740> run<00:05:15.919> on<00:05:16.159> the 00:05:16.839 --> 00:05:16.849 align:start position:0% kind of it right so to be run on the 00:05:16.849 --> 00:05:19.689 align:start position:0% kind of it right so to be run on the blockchain<00:05:17.440> so<00:05:18.440> how<00:05:18.710> to<00:05:18.770> do<00:05:19.039> that<00:05:19.190> actually 00:05:19.689 --> 00:05:19.699 align:start position:0% blockchain so how to do that actually 00:05:19.699 --> 00:05:21.760 align:start position:0% blockchain so how to do that actually the<00:05:20.090> technology<00:05:20.389> to<00:05:21.229> build<00:05:21.380> a<00:05:21.560> dead 00:05:21.760 --> 00:05:21.770 align:start position:0% the technology to build a dead 00:05:21.770 --> 00:05:24.040 align:start position:0% the technology to build a dead distributed<00:05:22.729> cloud<00:05:22.849> is<00:05:23.150> already<00:05:23.419> there<00:05:23.690> since 00:05:24.040 --> 00:05:24.050 align:start position:0% distributed cloud is already there since 00:05:24.050 --> 00:05:26.350 align:start position:0% distributed cloud is already there since many<00:05:24.259> times<00:05:24.590> we<00:05:25.220> just<00:05:25.250> call<00:05:25.789> that<00:05:25.819> desktop 00:05:26.350 --> 00:05:26.360 align:start position:0% many times we just call that desktop 00:05:26.360 --> 00:05:29.070 align:start position:0% many times we just call that desktop grid<00:05:26.630> computing<00:05:27.139> it's<00:05:28.039> the<00:05:28.250> idea<00:05:28.580> of<00:05:28.699> using 00:05:29.070 --> 00:05:29.080 align:start position:0% grid computing it's the idea of using 00:05:29.080 --> 00:05:31.749 align:start position:0% grid computing it's the idea of using PCs<00:05:30.080> and<00:05:30.380> the<00:05:30.500> internet<00:05:30.979> when<00:05:31.520> they<00:05:31.669> are 00:05:31.749 --> 00:05:31.759 align:start position:0% PCs and the internet when they are 00:05:31.759 --> 00:05:34.270 align:start position:0% PCs and the internet when they are either<00:05:32.000> and<00:05:32.900> it's<00:05:33.229> very<00:05:33.440> mature<00:05:33.740> technology 00:05:34.270 --> 00:05:34.280 align:start position:0% either and it's very mature technology 00:05:34.280 --> 00:05:36.820 align:start position:0% either and it's very mature technology so<00:05:34.460> for<00:05:34.669> instance<00:05:35.000> during<00:05:35.750> those<00:05:35.930> everything 00:05:36.820 --> 00:05:36.830 align:start position:0% so for instance during those everything 00:05:36.830 --> 00:05:39.219 align:start position:0% so for instance during those everything to<00:05:37.190> do<00:05:37.400> the<00:05:37.550> distributive<00:05:38.120> cloud<00:05:38.599> you<00:05:39.199> have 00:05:39.219 --> 00:05:39.229 align:start position:0% to do the distributive cloud you have 00:05:39.229 --> 00:05:41.830 align:start position:0% to do the distributive cloud you have security<00:05:39.710> virtualization<00:05:40.550> can<00:05:41.210> chip<00:05:41.479> VM 00:05:41.830 --> 00:05:41.840 align:start position:0% security virtualization can chip VM 00:05:41.840 --> 00:05:43.899 align:start position:0% security virtualization can chip VM images<00:05:42.169> you<00:05:42.860> can<00:05:43.070> even<00:05:43.250> do<00:05:43.430> quality<00:05:43.820> of 00:05:43.899 --> 00:05:43.909 align:start position:0% images you can even do quality of 00:05:43.909 --> 00:05:46.270 align:start position:0% images you can even do quality of services<00:05:44.479> you<00:05:44.840> know<00:05:44.930> high<00:05:45.080> level<00:05:45.320> things<00:05:45.590> so 00:05:46.270 --> 00:05:46.280 align:start position:0% services you know high level things so 00:05:46.280 --> 00:05:48.070 align:start position:0% services you know high level things so for<00:05:46.460> instance<00:05:46.699> in<00:05:46.849> Europe<00:05:46.969> we<00:05:47.509> had<00:05:47.930> the 00:05:48.070 --> 00:05:48.080 align:start position:0% for instance in Europe we had the 00:05:48.080 --> 00:05:50.800 align:start position:0% for instance in Europe we had the European<00:05:48.530> Union<00:05:48.830> funding<00:05:49.280> the<00:05:49.810> European 00:05:50.800 --> 00:05:50.810 align:start position:0% European Union funding the European 00:05:50.810 --> 00:05:52.450 align:start position:0% European Union funding the European disturb<00:05:51.169> green<00:05:51.349> infrastructure<00:05:51.889> we<00:05:52.250> had 00:05:52.450 --> 00:05:52.460 align:start position:0% disturb green infrastructure we had 00:05:52.460 --> 00:05:54.909 align:start position:0% disturb green infrastructure we had about<00:05:52.849> 11<00:05:53.449> different<00:05:53.599> sites<00:05:54.110> in<00:05:54.530> Hungary 00:05:54.909 --> 00:05:54.919 align:start position:0% about 11 different sites in Hungary 00:05:54.919 --> 00:05:58.180 align:start position:0% about 11 different sites in Hungary France<00:05:55.340> Denmark<00:05:55.610> etc<00:05:56.509> totally<00:05:57.409> not<00:05:57.830> two 00:05:58.180 --> 00:05:58.190 align:start position:0% France Denmark etc totally not two 00:05:58.190 --> 00:06:00.370 align:start position:0% France Denmark etc totally not two hundred<00:05:58.219> thousand<00:05:59.150> computing<00:05:59.750> nodes<00:05:59.900> and 00:06:00.370 --> 00:06:00.380 align:start position:0% hundred thousand computing nodes and 00:06:00.380 --> 00:06:02.439 align:start position:0% hundred thousand computing nodes and this<00:06:00.620> was<00:06:00.889> available<00:06:01.159> you<00:06:02.120> know<00:06:02.210> to<00:06:02.270> the 00:06:02.439 --> 00:06:02.449 align:start position:0% this was available you know to the 00:06:02.449 --> 00:06:05.770 align:start position:0% this was available you know to the traditional<00:06:03.020> science<00:06:04.389> infrastructure<00:06:05.389> such 00:06:05.770 --> 00:06:05.780 align:start position:0% traditional science infrastructure such 00:06:05.780 --> 00:06:07.559 align:start position:0% traditional science infrastructure such as<00:06:05.810> the<00:06:06.080> LHC<00:06:06.620> so<00:06:06.860> we<00:06:06.979> were<00:06:07.099> able<00:06:07.190> to 00:06:07.559 --> 00:06:07.569 align:start position:0% as the LHC so we were able to 00:06:07.569 --> 00:06:10.600 align:start position:0% as the LHC so we were able to transparently<00:06:08.569> execu<00:06:09.199> many<00:06:09.860> applications 00:06:10.600 --> 00:06:10.610 align:start position:0% transparently execu many applications 00:06:10.610 --> 00:06:12.580 align:start position:0% transparently execu many applications coming<00:06:10.969> from<00:06:11.120> finance<00:06:11.569> biomedical<00:06:12.229> research 00:06:12.580 --> 00:06:12.590 align:start position:0% coming from finance biomedical research 00:06:12.590 --> 00:06:16.480 align:start position:0% coming from finance biomedical research mathematics<00:06:13.430> high-energy<00:06:13.969> physics<00:06:14.479> etc<00:06:15.490> so 00:06:16.480 --> 00:06:16.490 align:start position:0% mathematics high-energy physics etc so 00:06:16.490 --> 00:06:19.270 align:start position:0% mathematics high-energy physics etc so in<00:06:16.580> my<00:06:16.699> research<00:06:17.060> team<00:06:17.930> we<00:06:18.500> used<00:06:18.740> to<00:06:18.860> push<00:06:19.099> this 00:06:19.270 --> 00:06:19.280 align:start position:0% in my research team we used to push this 00:06:19.280 --> 00:06:21.969 align:start position:0% in my research team we used to push this idea<00:06:19.490> in<00:06:19.880> every<00:06:20.659> possible<00:06:20.840> direction<00:06:21.169> with 00:06:21.969 --> 00:06:21.979 align:start position:0% idea in every possible direction with 00:06:21.979 --> 00:06:24.070 align:start position:0% idea in every possible direction with the<00:06:22.069> parallel<00:06:22.400> computing<00:06:22.909> and<00:06:23.120> internet<00:06:23.599> Map 00:06:24.070 --> 00:06:24.080 align:start position:0% the parallel computing and internet Map 00:06:24.080 --> 00:06:26.439 align:start position:0% the parallel computing and internet Map Reduce<00:06:24.229> computing<00:06:24.860> and<00:06:25.009> internet<00:06:25.610> quality<00:06:26.330> of 00:06:26.439 --> 00:06:26.449 align:start position:0% Reduce computing and internet quality of 00:06:26.449 --> 00:06:29.080 align:start position:0% Reduce computing and internet quality of services<00:06:26.840> for<00:06:27.280> execution<00:06:28.280> while<00:06:28.520> machine<00:06:29.000> da 00:06:29.080 --> 00:06:29.090 align:start position:0% services for execution while machine da 00:06:29.090 --> 00:06:31.659 align:start position:0% services for execution while machine da volatility<00:06:29.690> setter<00:06:29.900> etcetera<00:06:30.219> so<00:06:31.219> for<00:06:31.490> this 00:06:31.659 --> 00:06:31.669 align:start position:0% volatility setter etcetera so for this 00:06:31.669 --> 00:06:33.939 align:start position:0% volatility setter etcetera so for this work<00:06:31.909> what<00:06:32.120> is<00:06:32.330> interesting<00:06:32.960> for<00:06:33.199> us<00:06:33.409> these 00:06:33.939 --> 00:06:33.949 align:start position:0% work what is interesting for us these 00:06:33.949 --> 00:06:36.159 align:start position:0% work what is interesting for us these are<00:06:34.099> two<00:06:34.279> pieces<00:06:34.610> of<00:06:34.639> middleware<00:06:35.169> basically 00:06:36.159 --> 00:06:36.169 align:start position:0% are two pieces of middleware basically 00:06:36.169 --> 00:06:38.950 align:start position:0% are two pieces of middleware basically extreme<00:06:36.620> web<00:06:36.860> HTP<00:06:37.400> which<00:06:38.060> is<00:06:38.300> if<00:06:38.510> you<00:06:38.719> want<00:06:38.750> the 00:06:38.950 --> 00:06:38.960 align:start position:0% extreme web HTP which is if you want the 00:06:38.960 --> 00:06:39.970 align:start position:0% extreme web HTP which is if you want the production<00:06:39.500> version 00:06:39.970 --> 00:06:39.980 align:start position:0% production version 00:06:39.980 --> 00:06:42.130 align:start position:0% production version one<00:06:40.070> of<00:06:40.310> these<00:06:40.730> ideas<00:06:41.090> it's<00:06:41.600> done<00:06:41.780> by<00:06:41.960> your 00:06:42.130 --> 00:06:42.140 align:start position:0% one of these ideas it's done by your 00:06:42.140 --> 00:06:45.310 align:start position:0% one of these ideas it's done by your Oleg<00:06:42.410> ludajenski<00:06:42.710> at<00:06:43.280> the<00:06:44.270> in2<00:06:44.660> preframe<00:06:45.110> it 00:06:45.310 --> 00:06:45.320 align:start position:0% Oleg ludajenski at the in2 preframe it 00:06:45.320 --> 00:06:47.770 align:start position:0% Oleg ludajenski at the in2 preframe it does<00:06:45.740> task<00:06:46.100> management<00:06:46.520> and<00:06:47.240> the<00:06:47.360> other<00:06:47.480> one 00:06:47.770 --> 00:06:47.780 align:start position:0% does task management and the other one 00:06:47.780 --> 00:06:51.730 align:start position:0% does task management and the other one is<00:06:47.930> bid<00:06:48.140> you<00:06:48.290> that<00:06:48.470> those<00:06:48.650> data<00:06:49.010> management<00:06:50.740> so 00:06:51.730 --> 00:06:51.740 align:start position:0% is bid you that those data management so 00:06:51.740 --> 00:06:53.830 align:start position:0% is bid you that those data management so the<00:06:51.890> way<00:06:52.010> we<00:06:52.160> are<00:06:52.190> working<00:06:52.660> at<00:06:53.660> the<00:06:53.810> moment 00:06:53.830 --> 00:06:53.840 align:start position:0% the way we are working at the moment 00:06:53.840 --> 00:06:55.810 align:start position:0% the way we are working at the moment mostly<00:06:54.410> you<00:06:54.710> know<00:06:54.830> experiment<00:06:55.340> and 00:06:55.810 --> 00:06:55.820 align:start position:0% mostly you know experiment and 00:06:55.820 --> 00:06:57.820 align:start position:0% mostly you know experiment and proof-of-concept<00:06:56.180> see<00:06:56.750> what's<00:06:56.900> going<00:06:57.110> on<00:06:57.290> so 00:06:57.820 --> 00:06:57.830 align:start position:0% proof-of-concept see what's going on so 00:06:57.830 --> 00:06:59.950 align:start position:0% proof-of-concept see what's going on so we<00:06:57.920> have<00:06:58.040> the<00:06:58.190> regular<00:06:58.580> stack<00:06:59.510> if<00:06:59.720> you<00:06:59.840> want 00:06:59.950 --> 00:06:59.960 align:start position:0% we have the regular stack if you want 00:06:59.960 --> 00:07:01.480 align:start position:0% we have the regular stack if you want the<00:07:00.050> application<00:07:00.140> that<00:07:00.830> has<00:07:00.920> no<00:07:01.040> specialty 00:07:01.480 --> 00:07:01.490 align:start position:0% the application that has no specialty 00:07:01.490 --> 00:07:03.730 align:start position:0% the application that has no specialty blockchain<00:07:01.850> pass<00:07:02.030> the<00:07:02.600> resource<00:07:02.960> management 00:07:03.730 --> 00:07:03.740 align:start position:0% blockchain pass the resource management 00:07:03.740 --> 00:07:06.640 align:start position:0% blockchain pass the resource management middleware<00:07:04.550> and<00:07:04.930> and<00:07:05.930> of<00:07:06.230> course<00:07:06.530> the 00:07:06.640 --> 00:07:06.650 align:start position:0% middleware and and of course the 00:07:06.650 --> 00:07:10.090 align:start position:0% middleware and and of course the executing<00:07:07.360> the<00:07:08.360> actual<00:07:08.960> machines<00:07:09.410> and<00:07:09.680> what 00:07:10.090 --> 00:07:10.100 align:start position:0% executing the actual machines and what 00:07:10.100 --> 00:07:12.070 align:start position:0% executing the actual machines and what we<00:07:10.250> do<00:07:10.370> is<00:07:10.490> that<00:07:10.520> we<00:07:10.700> put<00:07:11.030> a<00:07:11.090> film<00:07:11.480> in<00:07:11.660> between<00:07:12.050> I 00:07:12.070 --> 00:07:12.080 align:start position:0% we do is that we put a film in between I 00:07:12.080 --> 00:07:13.810 align:start position:0% we do is that we put a film in between I would<00:07:12.320> try<00:07:12.530> to<00:07:12.560> see<00:07:12.890> what's<00:07:13.070> going<00:07:13.310> on<00:07:13.430> what<00:07:13.670> is 00:07:13.810 --> 00:07:13.820 align:start position:0% would try to see what's going on what is 00:07:13.820 --> 00:07:16.410 align:start position:0% would try to see what's going on what is difficult<00:07:14.240> or<00:07:14.690> challenging<00:07:14.750> or<00:07:15.440> what<00:07:15.560> is<00:07:15.680> easy 00:07:16.410 --> 00:07:16.420 align:start position:0% difficult or challenging or what is easy 00:07:16.420 --> 00:07:19.180 align:start position:0% difficult or challenging or what is easy that's<00:07:17.420> all<00:07:17.660> that's<00:07:18.170> basically<00:07:18.650> the<00:07:18.770> result 00:07:19.180 --> 00:07:19.190 align:start position:0% that's all that's basically the result 00:07:19.190 --> 00:07:20.980 align:start position:0% that's all that's basically the result so<00:07:19.370> on<00:07:19.610> the<00:07:19.730> left<00:07:19.910> part<00:07:20.120> you<00:07:20.330> have<00:07:20.540> what<00:07:20.780> is 00:07:20.980 --> 00:07:20.990 align:start position:0% so on the left part you have what is 00:07:20.990 --> 00:07:23.260 align:start position:0% so on the left part you have what is super<00:07:21.530> easy<00:07:21.830> the<00:07:22.040> goes<00:07:22.250> we'll<00:07:22.760> show<00:07:22.970> it<00:07:23.090> in 00:07:23.260 --> 00:07:23.270 align:start position:0% super easy the goes we'll show it in 00:07:23.270 --> 00:07:26.380 align:start position:0% super easy the goes we'll show it in green<00:07:23.570> and<00:07:23.870> on<00:07:24.320> the<00:07:24.500> right<00:07:25.370> part<00:07:25.670> light<00:07:26.180> right 00:07:26.380 --> 00:07:26.390 align:start position:0% green and on the right part light right 00:07:26.390 --> 00:07:28.870 align:start position:0% green and on the right part light right path<00:07:26.660> it's<00:07:27.230> what<00:07:27.440> is<00:07:27.590> red<00:07:27.860> and<00:07:28.160> what<00:07:28.430> is<00:07:28.610> really 00:07:28.870 --> 00:07:28.880 align:start position:0% path it's what is red and what is really 00:07:28.880 --> 00:07:29.530 align:start position:0% path it's what is red and what is really challenging 00:07:29.530 --> 00:07:29.540 align:start position:0% challenging 00:07:29.540 --> 00:07:31.960 align:start position:0% challenging so<00:07:30.170> results<00:07:30.740> publication<00:07:31.310> this<00:07:31.460> is<00:07:31.580> basically 00:07:31.960 --> 00:07:31.970 align:start position:0% so results publication this is basically 00:07:31.970 --> 00:07:33.550 align:start position:0% so results publication this is basically you<00:07:32.120> have<00:07:32.240> you<00:07:32.570> know<00:07:32.690> result<00:07:33.020> description 00:07:33.550 --> 00:07:33.560 align:start position:0% you have you know result description 00:07:33.560 --> 00:07:36.520 align:start position:0% you have you know result description language<00:07:33.920> or<00:07:34.130> very<00:07:34.490> well<00:07:34.960> standardized<00:07:35.960> and 00:07:36.520 --> 00:07:36.530 align:start position:0% language or very well standardized and 00:07:36.530 --> 00:07:38.320 align:start position:0% language or very well standardized and you<00:07:36.650> basically<00:07:37.040> translate<00:07:37.460> this<00:07:37.580> into<00:07:37.820> some 00:07:38.320 --> 00:07:38.330 align:start position:0% you basically translate this into some 00:07:38.330 --> 00:07:40.300 align:start position:0% you basically translate this into some sort<00:07:38.360> of<00:07:38.690> act<00:07:38.960> contract<00:07:39.560> and<00:07:39.800> put<00:07:39.980> it<00:07:40.100> on<00:07:40.220> the 00:07:40.300 --> 00:07:40.310 align:start position:0% sort of act contract and put it on the 00:07:40.310 --> 00:07:42.400 align:start position:0% sort of act contract and put it on the blockchain<00:07:40.520> so<00:07:40.850> fairly<00:07:41.180> easy<00:07:41.410> resource 00:07:42.400 --> 00:07:42.410 align:start position:0% blockchain so fairly easy resource 00:07:42.410 --> 00:07:44.170 align:start position:0% blockchain so fairly easy resource provisioning<00:07:42.710> just<00:07:43.370> add<00:07:43.520> the<00:07:43.670> flag<00:07:43.940> that 00:07:44.170 --> 00:07:44.180 align:start position:0% provisioning just add the flag that 00:07:44.180 --> 00:07:47.140 align:start position:0% provisioning just add the flag that gives<00:07:44.420> the<00:07:44.570> status<00:07:44.990> of<00:07:45.650> the<00:07:46.430> resources<00:07:46.940> and 00:07:47.140 --> 00:07:47.150 align:start position:0% gives the status of the resources and 00:07:47.150 --> 00:07:49.330 align:start position:0% gives the status of the resources and then<00:07:47.510> it<00:07:47.690> gets<00:07:48.020> more<00:07:48.140> tricky<00:07:48.710> so<00:07:48.920> for<00:07:49.070> instance 00:07:49.330 --> 00:07:49.340 align:start position:0% then it gets more tricky so for instance 00:07:49.340 --> 00:07:51.910 align:start position:0% then it gets more tricky so for instance match<00:07:49.580> matchmaking<00:07:50.180> is<00:07:50.570> you<00:07:51.470> want<00:07:51.650> to<00:07:51.740> be<00:07:51.830> able 00:07:51.910 --> 00:07:51.920 align:start position:0% match matchmaking is you want to be able 00:07:51.920 --> 00:07:54.460 align:start position:0% match matchmaking is you want to be able to<00:07:52.070> say<00:07:52.340> this<00:07:52.610> with<00:07:52.910> this<00:07:53.330> application<00:07:54.020> that 00:07:54.460 --> 00:07:54.470 align:start position:0% to say this with this application that 00:07:54.470 --> 00:07:58.570 align:start position:0% to say this with this application that requires<00:07:54.980> this<00:07:55.820> amount<00:07:56.360> of<00:07:56.590> memory<00:07:57.590> can<00:07:58.310> run 00:07:58.570 --> 00:07:58.580 align:start position:0% requires this amount of memory can run 00:07:58.580 --> 00:08:01.030 align:start position:0% requires this amount of memory can run on<00:07:58.820> those<00:07:59.180> resources<00:07:59.690> so<00:08:00.680> you<00:08:00.770> have<00:08:00.890> to 00:08:01.030 --> 00:08:01.040 align:start position:0% on those resources so you have to 00:08:01.040 --> 00:08:03.190 align:start position:0% on those resources so you have to brought<00:08:01.280> some<00:08:01.790> holder<00:08:02.150> blockchain<00:08:02.510> and<00:08:02.690> then 00:08:03.190 --> 00:08:03.200 align:start position:0% brought some holder blockchain and then 00:08:03.200 --> 00:08:05.050 align:start position:0% brought some holder blockchain and then things<00:08:03.620> get<00:08:03.770> real<00:08:04.040> tricky<00:08:04.400> with<00:08:04.580> scheduling 00:08:05.050 --> 00:08:05.060 align:start position:0% things get real tricky with scheduling 00:08:05.060 --> 00:08:07.090 align:start position:0% things get real tricky with scheduling so<00:08:05.390> simple<00:08:05.810> scheduling<00:08:06.230> so<00:08:06.470> scheduling<00:08:06.920> it 00:08:07.090 --> 00:08:07.100 align:start position:0% so simple scheduling so scheduling it 00:08:07.100 --> 00:08:09.640 align:start position:0% so simple scheduling so scheduling it you<00:08:07.700> have<00:08:07.880> a<00:08:07.910> list<00:08:08.180> of<00:08:08.330> tasks<00:08:08.660> you<00:08:08.960> have<00:08:09.380> a<00:08:09.410> list 00:08:09.640 --> 00:08:09.650 align:start position:0% you have a list of tasks you have a list 00:08:09.650 --> 00:08:11.710 align:start position:0% you have a list of tasks you have a list of<00:08:09.800> machines<00:08:10.280> and<00:08:10.520> you<00:08:11.000> want<00:08:11.180> to<00:08:11.330> build<00:08:11.510> the 00:08:11.710 --> 00:08:11.720 align:start position:0% of machines and you want to build the 00:08:11.720 --> 00:08:14.560 align:start position:0% of machines and you want to build the execution<00:08:12.350> plan<00:08:12.910> so<00:08:13.910> things<00:08:14.150> get<00:08:14.360> really 00:08:14.560 --> 00:08:14.570 align:start position:0% execution plan so things get really 00:08:14.570 --> 00:08:16.660 align:start position:0% execution plan so things get really tricky<00:08:14.990> when<00:08:15.170> you<00:08:15.320> need<00:08:15.530> you<00:08:16.100> know<00:08:16.220> advanced 00:08:16.660 --> 00:08:16.670 align:start position:0% tricky when you need you know advanced 00:08:16.670 --> 00:08:19.690 align:start position:0% tricky when you need you know advanced scheduling<00:08:18.040> advanced<00:08:19.040> scheduling<00:08:19.550> with 00:08:19.690 --> 00:08:19.700 align:start position:0% scheduling advanced scheduling with 00:08:19.700 --> 00:08:23.290 align:start position:0% scheduling advanced scheduling with multi<00:08:20.000> criteria<00:08:20.180> so<00:08:20.780> things<00:08:21.380> like<00:08:21.910> I'm<00:08:22.910> ready 00:08:23.290 --> 00:08:23.300 align:start position:0% multi criteria so things like I'm ready 00:08:23.300 --> 00:08:26.590 align:start position:0% multi criteria so things like I'm ready to<00:08:23.450> I<00:08:24.260> want<00:08:24.620> a<00:08:24.740> fastest<00:08:25.370> execution<00:08:26.030> possible 00:08:26.590 --> 00:08:26.600 align:start position:0% to I want a fastest execution possible 00:08:26.600 --> 00:08:30.190 align:start position:0% to I want a fastest execution possible and<00:08:26.810> I'm<00:08:27.110> ready<00:08:27.320> to<00:08:27.410> pay<00:08:27.680> for<00:08:27.890> that<00:08:29.200> it's 00:08:30.190 --> 00:08:30.200 align:start position:0% and I'm ready to pay for that it's 00:08:30.200 --> 00:08:32.080 align:start position:0% and I'm ready to pay for that it's getting<00:08:30.620> really<00:08:30.860> a<00:08:30.890> computer<00:08:31.460> tension<00:08:31.760> memory 00:08:32.080 --> 00:08:32.090 align:start position:0% getting really a computer tension memory 00:08:32.090 --> 00:08:34.150 align:start position:0% getting really a computer tension memory intensive<00:08:32.330> so<00:08:33.290> no<00:08:33.440> use<00:08:33.650> case<00:08:33.890> we're<00:08:34.040> also 00:08:34.150 --> 00:08:34.160 align:start position:0% intensive so no use case we're also 00:08:34.160 --> 00:08:36.730 align:start position:0% intensive so no use case we're also working<00:08:34.430> with<00:08:34.669> an<00:08:35.180> application<00:08:35.810> it's<00:08:36.440> called 00:08:36.730 --> 00:08:36.740 align:start position:0% working with an application it's called 00:08:36.740 --> 00:08:38.500 align:start position:0% working with an application it's called if<00:08:37.010> a<00:08:37.250> this<00:08:37.520> is<00:08:37.640> a<00:08:37.669> framework<00:08:38.030> for<00:08:38.210> doing 00:08:38.500 --> 00:08:38.510 align:start position:0% if a this is a framework for doing 00:08:38.510 --> 00:08:41.770 align:start position:0% if a this is a framework for doing Finance<00:08:39.580> analysis<00:08:40.580> and<00:08:40.880> the<00:08:41.240> interesting 00:08:41.770 --> 00:08:41.780 align:start position:0% Finance analysis and the interesting 00:08:41.780 --> 00:08:43.270 align:start position:0% Finance analysis and the interesting things<00:08:42.050> here<00:08:42.380> that<00:08:42.410> it<00:08:42.860> does<00:08:42.979> a<00:08:43.010> lot<00:08:43.220> of 00:08:43.270 --> 00:08:43.280 align:start position:0% things here that it does a lot of 00:08:43.280 --> 00:08:45.190 align:start position:0% things here that it does a lot of machine<00:08:43.760> learning<00:08:44.150> so<00:08:44.600> a<00:08:44.630> lot<00:08:44.750> of<00:08:44.780> machine 00:08:45.190 --> 00:08:45.200 align:start position:0% machine learning so a lot of machine 00:08:45.200 --> 00:08:47.770 align:start position:0% machine learning so a lot of machine learning<00:08:45.470> it's<00:08:45.860> both<00:08:46.430> data<00:08:46.880> intensive<00:08:47.330> and 00:08:47.770 --> 00:08:47.780 align:start position:0% learning it's both data intensive and 00:08:47.780 --> 00:08:49.750 align:start position:0% learning it's both data intensive and compute<00:08:48.230> intensive<00:08:48.410> so<00:08:49.160> here<00:08:49.370> of<00:08:49.430> course<00:08:49.490> I'm 00:08:49.750 --> 00:08:49.760 align:start position:0% compute intensive so here of course I'm 00:08:49.760 --> 00:08:51.160 align:start position:0% compute intensive so here of course I'm not<00:08:49.850> going<00:08:50.000> to<00:08:50.180> make<00:08:50.360> it<00:08:50.480> on<00:08:50.630> the<00:08:50.780> the 00:08:51.160 --> 00:08:51.170 align:start position:0% not going to make it on the the 00:08:51.170 --> 00:08:51.990 align:start position:0% not going to make it on the the blockchain<00:08:51.410> and 00:08:51.990 --> 00:08:52.000 align:start position:0% blockchain and 00:08:52.000 --> 00:08:55.140 align:start position:0% blockchain and you<00:08:52.030> need<00:08:52.180> to<00:08:52.300> go<00:08:52.420> offline<00:08:53.350> I've<00:08:54.340> seen<00:08:54.670> so<00:08:54.880> and 00:08:55.140 --> 00:08:55.150 align:start position:0% you need to go offline I've seen so and 00:08:55.150 --> 00:08:58.020 align:start position:0% you need to go offline I've seen so and the<00:08:55.720> good<00:08:55.870> thing<00:08:56.050> is<00:08:56.230> that<00:08:56.260> once<00:08:57.100> if<00:08:57.400> a<00:08:57.550> service 00:08:58.020 --> 00:08:58.030 align:start position:0% the good thing is that once if a service 00:08:58.030 --> 00:09:00.480 align:start position:0% the good thing is that once if a service is<00:08:58.060> ready<00:08:58.450> their<00:08:59.200> customers<00:08:59.740> will<00:08:59.920> be<00:09:00.040> able<00:09:00.070> to 00:09:00.480 --> 00:09:00.490 align:start position:0% is ready their customers will be able to 00:09:00.490 --> 00:09:02.370 align:start position:0% is ready their customers will be able to rent<00:09:01.360> it<00:09:01.540> directly<00:09:01.930> on<00:09:02.080> the<00:09:02.170> blockchain 00:09:02.370 --> 00:09:02.380 align:start position:0% rent it directly on the blockchain 00:09:02.380 --> 00:09:04.890 align:start position:0% rent it directly on the blockchain because<00:09:03.040> this<00:09:03.480> application<00:09:04.480> is<00:09:04.570> going<00:09:04.600> to<00:09:04.780> be 00:09:04.890 --> 00:09:04.900 align:start position:0% because this application is going to be 00:09:04.900 --> 00:09:07.470 align:start position:0% because this application is going to be autonomous<00:09:05.200> it<00:09:05.800> will<00:09:06.010> fetch<00:09:06.190> itself<00:09:07.060> the 00:09:07.470 --> 00:09:07.480 align:start position:0% autonomous it will fetch itself the 00:09:07.480 --> 00:09:09.840 align:start position:0% autonomous it will fetch itself the resources<00:09:08.020> in<00:09:08.170> need<00:09:08.350> on<00:09:08.560> the<00:09:09.010> blockchain<00:09:09.220> to 00:09:09.840 --> 00:09:09.850 align:start position:0% resources in need on the blockchain to 00:09:09.850 --> 00:09:13.860 align:start position:0% resources in need on the blockchain to execute<00:09:10.270> it<00:09:10.420> option<00:09:12.120> okay<00:09:13.120> so<00:09:13.180> our<00:09:13.420> test<00:09:13.630> bed 00:09:13.860 --> 00:09:13.870 align:start position:0% execute it option okay so our test bed 00:09:13.870 --> 00:09:17.100 align:start position:0% execute it option okay so our test bed for<00:09:14.200> doing<00:09:14.770> this<00:09:14.950> it's<00:09:15.250> the<00:09:15.460> grid<00:09:15.730> 5000<00:09:16.540> is<00:09:16.870> the 00:09:17.100 --> 00:09:17.110 align:start position:0% for doing this it's the grid 5000 is the 00:09:17.110 --> 00:09:20.070 align:start position:0% for doing this it's the grid 5000 is the French<00:09:17.940> interaction<00:09:18.940> show<00:09:19.090> dedicated<00:09:19.600> for 00:09:20.070 --> 00:09:20.080 align:start position:0% French interaction show dedicated for 00:09:20.080 --> 00:09:22.230 align:start position:0% French interaction show dedicated for researching<00:09:20.650> in<00:09:20.920> distributed<00:09:21.550> system<00:09:21.940> so<00:09:22.120> we 00:09:22.230 --> 00:09:22.240 align:start position:0% researching in distributed system so we 00:09:22.240 --> 00:09:24.510 align:start position:0% researching in distributed system so we are<00:09:22.270> very<00:09:22.930> lucky<00:09:23.200> to<00:09:23.680> have<00:09:23.980> this<00:09:24.190> at<00:09:24.370> all 00:09:24.510 --> 00:09:24.520 align:start position:0% are very lucky to have this at all 00:09:24.520 --> 00:09:26.640 align:start position:0% are very lucky to have this at all disposal<00:09:25.030> it's<00:09:25.510> actually<00:09:26.020> a<00:09:26.050> distributed 00:09:26.640 --> 00:09:26.650 align:start position:0% disposal it's actually a distributed 00:09:26.650 --> 00:09:29.400 align:start position:0% disposal it's actually a distributed cloud<00:09:26.800> it's<00:09:27.220> nine<00:09:27.490> sites<00:09:27.790> and<00:09:28.180> we<00:09:28.600> have<00:09:28.780> 100 00:09:29.400 --> 00:09:29.410 align:start position:0% cloud it's nine sites and we have 100 00:09:29.410 --> 00:09:33.030 align:start position:0% cloud it's nine sites and we have 100 about<00:09:30.040> of<00:09:30.310> course<00:09:30.550> 1,000<00:09:31.360> nodes<00:09:31.750> 8000<00:09:32.710> course 00:09:33.030 --> 00:09:33.040 align:start position:0% about of course 1,000 nodes 8000 course 00:09:33.040 --> 00:09:38.430 align:start position:0% about of course 1,000 nodes 8000 course and<00:09:35.220> yes<00:09:36.220> and<00:09:36.400> the<00:09:36.550> and<00:09:37.000> so<00:09:37.270> 3<00:09:37.600> grid<00:09:37.930> to<00:09:38.110> do<00:09:38.260> you 00:09:38.430 --> 00:09:38.440 align:start position:0% and yes and the and so 3 grid to do you 00:09:38.440 --> 00:09:40.170 align:start position:0% and yes and the and so 3 grid to do you know<00:09:38.530> scalability<00:09:38.980> tests<00:09:39.520> and<00:09:39.790> this<00:09:39.850> kind<00:09:40.120> of 00:09:40.170 --> 00:09:40.180 align:start position:0% know scalability tests and this kind of 00:09:40.180 --> 00:09:42.210 align:start position:0% know scalability tests and this kind of things<00:09:40.480> and<00:09:40.660> we<00:09:41.080> have<00:09:41.200> a<00:09:41.230> dedicated<00:09:41.410> 10<00:09:42.010> Giga 00:09:42.210 --> 00:09:42.220 align:start position:0% things and we have a dedicated 10 Giga 00:09:42.220 --> 00:09:46.980 align:start position:0% things and we have a dedicated 10 Giga Network<00:09:42.910> and<00:09:44.430> so<00:09:45.430> the<00:09:45.580> last<00:09:45.730> I<00:09:46.090> mean<00:09:46.690> the 00:09:46.980 --> 00:09:46.990 align:start position:0% Network and so the last I mean the 00:09:46.990 --> 00:09:50.850 align:start position:0% Network and so the last I mean the bottom<00:09:47.710> in<00:09:48.100> or<00:09:48.310> use<00:09:48.880> case<00:09:49.230> it's<00:09:50.230> we<00:09:50.530> want<00:09:50.710> to 00:09:50.850 --> 00:09:50.860 align:start position:0% bottom in or use case it's we want to 00:09:50.860 --> 00:09:55.490 align:start position:0% bottom in or use case it's we want to use<00:09:51.040> the<00:09:51.310> steam<00:09:51.790> LG<00:09:52.090> servers<00:09:53.130> to<00:09:54.130> run<00:09:54.310> this<00:09:54.520> so 00:09:55.490 --> 00:09:55.500 align:start position:0% use the steam LG servers to run this so 00:09:55.500 --> 00:09:58.230 align:start position:0% use the steam LG servers to run this so so<00:09:56.500> steam<00:09:56.740> adji<00:09:57.010> what<00:09:57.160> they<00:09:57.250> are<00:09:57.339> doing<00:09:57.520> it's<00:09:57.790> a 00:09:58.230 --> 00:09:58.240 align:start position:0% so steam adji what they are doing it's a 00:09:58.240 --> 00:10:00.300 align:start position:0% so steam adji what they are doing it's a this<00:09:58.750> is<00:09:58.930> actually<00:09:59.260> that<00:09:59.470> this<00:09:59.650> server<00:09:59.980> is<00:10:00.280> a 00:10:00.300 --> 00:10:00.310 align:start position:0% this is actually that this server is a 00:10:00.310 --> 00:10:04.350 align:start position:0% this is actually that this server is a furnace<00:10:00.850> so<00:10:01.570> it<00:10:01.870> pre-warmed<00:10:02.770> the<00:10:03.400> the<00:10:04.000> water 00:10:04.350 --> 00:10:04.360 align:start position:0% furnace so it pre-warmed the the water 00:10:04.360 --> 00:10:06.480 align:start position:0% furnace so it pre-warmed the the water before<00:10:04.810> distributed<00:10:05.589> this<00:10:05.770> in<00:10:05.950> the<00:10:06.070> building 00:10:06.480 --> 00:10:06.490 align:start position:0% before distributed this in the building 00:10:06.490 --> 00:10:09.150 align:start position:0% before distributed this in the building and<00:10:06.730> we<00:10:07.030> hope<00:10:07.180> to<00:10:07.390> to<00:10:08.020> do<00:10:08.170> demo<00:10:08.530> 18<00:10:08.860> know<00:10:09.010> in 00:10:09.150 --> 00:10:09.160 align:start position:0% and we hope to to do demo 18 know in 00:10:09.160 --> 00:10:10.770 align:start position:0% and we hope to to do demo 18 know in November<00:10:09.610> at<00:10:09.790> the<00:10:09.880> supercomputing<00:10:10.240> a 00:10:10.770 --> 00:10:10.780 align:start position:0% November at the supercomputing a 00:10:10.780 --> 00:10:12.900 align:start position:0% November at the supercomputing a conference<00:10:11.380> and<00:10:11.589> that<00:10:12.280> will<00:10:12.490> be<00:10:12.610> for<00:10:12.790> the 00:10:12.900 --> 00:10:12.910 align:start position:0% conference and that will be for the 00:10:12.910 --> 00:10:15.000 align:start position:0% conference and that will be for the first<00:10:13.180> time<00:10:13.390> in<00:10:13.660> the<00:10:13.839> history<00:10:14.020> of<00:10:14.380> blockchain 00:10:15.000 --> 00:10:15.010 align:start position:0% first time in the history of blockchain 00:10:15.010 --> 00:10:18.300 align:start position:0% first time in the history of blockchain a<00:10:15.190> smart<00:10:15.880> contract<00:10:16.120> with<00:10:17.020> wood<00:10:17.589> side<00:10:17.890> effect 00:10:18.300 --> 00:10:18.310 align:start position:0% a smart contract with wood side effect 00:10:18.310 --> 00:10:22.350 align:start position:0% a smart contract with wood side effect is<00:10:18.490> to<00:10:18.700> warm<00:10:19.000> a<00:10:19.210> swimming<00:10:20.020> pool<00:10:20.200> so<00:10:21.360> amazing 00:10:22.350 --> 00:10:22.360 align:start position:0% is to warm a swimming pool so amazing 00:10:22.360 --> 00:10:27.480 align:start position:0% is to warm a swimming pool so amazing this<00:10:23.230> is<00:10:23.440> true<00:10:23.620> this<00:10:23.830> is<00:10:23.890> true<00:10:26.010> this<00:10:27.010> is<00:10:27.070> lab<00:10:27.370> it 00:10:27.480 --> 00:10:27.490 align:start position:0% this is true this is true this is lab it 00:10:27.490 --> 00:10:30.680 align:start position:0% this is true this is true this is lab it ok<00:10:27.820> in<00:10:28.000> Paris<00:10:28.530> so<00:10:29.530> bad<00:10:29.770> on<00:10:29.980> those<00:10:30.160> earlier 00:10:30.680 --> 00:10:30.690 align:start position:0% ok in Paris so bad on those earlier 00:10:30.690 --> 00:10:34.260 align:start position:0% ok in Paris so bad on those earlier experiment<00:10:32.130> that's<00:10:33.130> a<00:10:33.280> sketch<00:10:33.580> of<00:10:33.610> what<00:10:34.180> the 00:10:34.260 --> 00:10:34.270 align:start position:0% experiment that's a sketch of what the 00:10:34.270 --> 00:10:35.520 align:start position:0% experiment that's a sketch of what the future<00:10:34.570> is<00:10:34.600> going<00:10:34.780> to<00:10:35.020> be<00:10:35.140> for<00:10:35.350> us 00:10:35.520 --> 00:10:35.530 align:start position:0% future is going to be for us 00:10:35.530 --> 00:10:39.480 align:start position:0% future is going to be for us most<00:10:36.100> certainly<00:10:36.790> so<00:10:37.480> from<00:10:38.110> what<00:10:38.260> I<00:10:38.290> am<00:10:38.500> what<00:10:39.460> I 00:10:39.480 --> 00:10:39.490 align:start position:0% most certainly so from what I am what I 00:10:39.490 --> 00:10:41.490 align:start position:0% most certainly so from what I am what I think<00:10:39.880> is<00:10:40.030> that<00:10:40.060> we<00:10:40.839> are<00:10:40.990> going<00:10:41.110> to<00:10:41.200> have 00:10:41.490 --> 00:10:41.500 align:start position:0% think is that we are going to have 00:10:41.500 --> 00:10:43.500 align:start position:0% think is that we are going to have something<00:10:41.920> like<00:10:42.070> a<00:10:42.160> side<00:10:42.760> chain<00:10:43.000> because<00:10:43.300> we 00:10:43.500 --> 00:10:43.510 align:start position:0% something like a side chain because we 00:10:43.510 --> 00:10:46.380 align:start position:0% something like a side chain because we need<00:10:43.690> know<00:10:44.290> some<00:10:44.500> sort<00:10:44.710> of<00:10:44.890> a<00:10:45.160> new<00:10:45.640> consensus 00:10:46.380 --> 00:10:46.390 align:start position:0% need know some sort of a new consensus 00:10:46.390 --> 00:10:49.170 align:start position:0% need know some sort of a new consensus for<00:10:46.570> what's<00:10:46.960> going<00:10:47.200> of<00:10:47.920> shame<00:10:48.580> that<00:10:48.790> we<00:10:48.970> call 00:10:49.170 --> 00:10:49.180 align:start position:0% for what's going of shame that we call 00:10:49.180 --> 00:10:51.840 align:start position:0% for what's going of shame that we call that<00:10:49.360> proof<00:10:50.050> of<00:10:50.170> contribution<00:10:50.890> important 00:10:51.840 --> 00:10:51.850 align:start position:0% that proof of contribution important 00:10:51.850 --> 00:10:53.370 align:start position:0% that proof of contribution important thing<00:10:52.060> is<00:10:52.210> that<00:10:52.360> there<00:10:52.540> are<00:10:52.630> many<00:10:52.810> information 00:10:53.370 --> 00:10:53.380 align:start position:0% thing is that there are many information 00:10:53.380 --> 00:10:55.650 align:start position:0% thing is that there are many information that<00:10:53.530> you<00:10:53.650> need<00:10:53.830> to<00:10:53.860> make<00:10:54.040> it<00:10:54.190> run<00:10:54.540> but<00:10:55.540> you 00:10:55.650 --> 00:10:55.660 align:start position:0% that you need to make it run but you 00:10:55.660 --> 00:10:58.730 align:start position:0% that you need to make it run but you know<00:10:55.750> that<00:10:55.900> are<00:10:56.080> not<00:10:56.650> necessarily<00:10:57.450> relevant 00:10:58.730 --> 00:10:58.740 align:start position:0% know that are not necessarily relevant 00:10:58.740 --> 00:11:01.350 align:start position:0% know that are not necessarily relevant with<00:10:59.740> respect<00:10:59.770> to<00:11:00.400> the<00:11:00.550> to<00:11:00.760> the<00:11:00.910> to<00:11:01.270> the 00:11:01.350 --> 00:11:01.360 align:start position:0% with respect to the to the to the 00:11:01.360 --> 00:11:03.630 align:start position:0% with respect to the to the to the provisioning<00:11:01.959> contract<00:11:02.650> if<00:11:02.770> you<00:11:02.920> so<00:11:03.459> for 00:11:03.630 --> 00:11:03.640 align:start position:0% provisioning contract if you so for 00:11:03.640 --> 00:11:05.650 align:start position:0% provisioning contract if you so for instance<00:11:03.910> everything<00:11:04.300> that<00:11:04.480> is<00:11:04.690> about<00:11:05.140> tasks 00:11:05.650 --> 00:11:05.660 align:start position:0% instance everything that is about tasks 00:11:05.660 --> 00:11:07.780 align:start position:0% instance everything that is about tasks you<00:11:05.720> sure<00:11:06.020> this<00:11:06.500> is<00:11:06.650> meaningful<00:11:07.010> when<00:11:07.670> you 00:11:07.780 --> 00:11:07.790 align:start position:0% you sure this is meaningful when you 00:11:07.790 --> 00:11:09.040 align:start position:0% you sure this is meaningful when you want<00:11:07.940> to<00:11:08.030> establish<00:11:08.150> the<00:11:08.570> fact<00:11:08.810> that<00:11:08.900> the 00:11:09.040 --> 00:11:09.050 align:start position:0% want to establish the fact that the 00:11:09.050 --> 00:11:10.900 align:start position:0% want to establish the fact that the computation<00:11:09.590> went<00:11:09.800> right<00:11:10.010> but<00:11:10.580> it's<00:11:10.760> not 00:11:10.900 --> 00:11:10.910 align:start position:0% computation went right but it's not 00:11:10.910 --> 00:11:12.760 align:start position:0% computation went right but it's not really<00:11:11.180> meaningful<00:11:11.660> with<00:11:12.110> respect<00:11:12.530> to<00:11:12.650> the 00:11:12.760 --> 00:11:12.770 align:start position:0% really meaningful with respect to the 00:11:12.770 --> 00:11:14.380 align:start position:0% really meaningful with respect to the contribute<00:11:13.610> to<00:11:13.790> the<00:11:13.880> contract<00:11:14.330> that 00:11:14.380 --> 00:11:14.390 align:start position:0% contribute to the contract that 00:11:14.390 --> 00:11:16.510 align:start position:0% contribute to the contract that provision<00:11:14.900> those<00:11:15.050> resources<00:11:15.620> and<00:11:15.770> as<00:11:16.160> for<00:11:16.400> the 00:11:16.510 --> 00:11:16.520 align:start position:0% provision those resources and as for the 00:11:16.520 --> 00:11:20.290 align:start position:0% provision those resources and as for the the<00:11:17.240> execution<00:11:18.050> so<00:11:18.590> I<00:11:18.920> want<00:11:19.700> to<00:11:19.760> I<00:11:19.910> think<00:11:19.970> we 00:11:20.290 --> 00:11:20.300 align:start position:0% the execution so I want to I think we 00:11:20.300 --> 00:11:23.710 align:start position:0% the execution so I want to I think we need<00:11:20.450> some<00:11:20.870> dedicated<00:11:21.470> section<00:11:22.400> for<00:11:22.730> this<00:11:22.820> we 00:11:23.710 --> 00:11:23.720 align:start position:0% need some dedicated section for this we 00:11:23.720 --> 00:11:26.050 align:start position:0% need some dedicated section for this we also<00:11:23.930> have<00:11:24.080> some<00:11:24.590> very<00:11:24.740> specific<00:11:25.070> workload<00:11:25.880> in 00:11:26.050 --> 00:11:26.060 align:start position:0% also have some very specific workload in 00:11:26.060 --> 00:11:29.140 align:start position:0% also have some very specific workload in in<00:11:26.480> perilous<00:11:26.930> and<00:11:27.710> parallel<00:11:28.070> computing<00:11:28.520> you 00:11:29.140 --> 00:11:29.150 align:start position:0% in perilous and parallel computing you 00:11:29.150 --> 00:11:31.810 align:start position:0% in perilous and parallel computing you often<00:11:29.780> have<00:11:30.080> things<00:11:30.680> that<00:11:30.830> arrives<00:11:31.250> really<00:11:31.640> in 00:11:31.810 --> 00:11:31.820 align:start position:0% often have things that arrives really in 00:11:31.820 --> 00:11:36.430 align:start position:0% often have things that arrives really in bursts<00:11:32.120> so<00:11:33.580> so<00:11:34.580> we<00:11:34.670> have<00:11:34.820> to<00:11:35.020> to<00:11:36.020> be<00:11:36.170> able<00:11:36.260> to 00:11:36.430 --> 00:11:36.440 align:start position:0% bursts so so we have to to be able to 00:11:36.440 --> 00:11:39.540 align:start position:0% bursts so so we have to to be able to optimize<00:11:36.740> for<00:11:37.130> this<00:11:37.900> specific<00:11:38.900> workload<00:11:39.350> and 00:11:39.540 --> 00:11:39.550 align:start position:0% optimize for this specific workload and 00:11:39.550 --> 00:11:42.370 align:start position:0% optimize for this specific workload and and<00:11:40.550> last<00:11:40.940> thing<00:11:41.120> is<00:11:41.270> that<00:11:41.420> the<00:11:41.870> console<00:11:42.230> fees 00:11:42.370 --> 00:11:42.380 align:start position:0% and last thing is that the console fees 00:11:42.380 --> 00:11:44.110 align:start position:0% and last thing is that the console fees can<00:11:42.560> be<00:11:42.590> very<00:11:42.890> different<00:11:43.130> for<00:11:43.580> parallel 00:11:44.110 --> 00:11:44.120 align:start position:0% can be very different for parallel 00:11:44.120 --> 00:11:46.150 align:start position:0% can be very different for parallel computing<00:11:44.300> you<00:11:44.720> know<00:11:44.840> in<00:11:45.140> some<00:11:45.830> case<00:11:46.010> in 00:11:46.150 --> 00:11:46.160 align:start position:0% computing you know in some case in 00:11:46.160 --> 00:11:47.830 align:start position:0% computing you know in some case in parallel<00:11:46.430> computing<00:11:46.820> that's<00:11:47.060> totally<00:11:47.510> okay 00:11:47.830 --> 00:11:47.840 align:start position:0% parallel computing that's totally okay 00:11:47.840 --> 00:11:50.560 align:start position:0% parallel computing that's totally okay to<00:11:47.900> have<00:11:48.230> a<00:11:48.440> fraction<00:11:49.430> of<00:11:49.580> your<00:11:49.760> application 00:11:50.560 --> 00:11:50.570 align:start position:0% to have a fraction of your application 00:11:50.570 --> 00:11:52.630 align:start position:0% to have a fraction of your application that<00:11:50.600> gives<00:11:50.900> you<00:11:51.050> wrong<00:11:51.230> result<00:11:51.620> it<00:11:52.610> just 00:11:52.630 --> 00:11:52.640 align:start position:0% that gives you wrong result it just 00:11:52.640 --> 00:11:55.450 align:start position:0% that gives you wrong result it just depends<00:11:53.270> on<00:11:53.300> the<00:11:53.450> application<00:11:53.710> so<00:11:54.710> we<00:11:55.070> must<00:11:55.280> be 00:11:55.450 --> 00:11:55.460 align:start position:0% depends on the application so we must be 00:11:55.460 --> 00:11:57.880 align:start position:0% depends on the application so we must be very<00:11:55.730> flexible<00:11:56.240> with<00:11:56.390> respect<00:11:56.780> to<00:11:56.870> this<00:11:57.020> okay 00:11:57.880 --> 00:11:57.890 align:start position:0% very flexible with respect to this okay 00:11:57.890 --> 00:12:00.040 align:start position:0% very flexible with respect to this okay so<00:11:57.950> just<00:11:58.280> to<00:11:58.370> conclude<00:11:58.900> distributing<00:11:59.900> the 00:12:00.040 --> 00:12:00.050 align:start position:0% so just to conclude distributing the 00:12:00.050 --> 00:12:03.160 align:start position:0% so just to conclude distributing the cloud<00:12:00.350> I<00:12:00.680> mean<00:12:01.670> it's<00:12:01.850> also<00:12:02.030> give<00:12:02.600> us<00:12:02.750> some<00:12:02.780> new 00:12:03.160 --> 00:12:03.170 align:start position:0% cloud I mean it's also give us some new 00:12:03.170 --> 00:12:05.740 align:start position:0% cloud I mean it's also give us some new opportunities<00:12:03.920> that's<00:12:04.490> very<00:12:04.700> important<00:12:05.240> so 00:12:05.740 --> 00:12:05.750 align:start position:0% opportunities that's very important so 00:12:05.750 --> 00:12:07.720 align:start position:0% opportunities that's very important so as<00:12:05.930> I<00:12:06.050> said<00:12:06.320> I'm<00:12:06.470> repeating<00:12:06.800> myself<00:12:07.100> it<00:12:07.550> hats 00:12:07.720 --> 00:12:07.730 align:start position:0% as I said I'm repeating myself it hats 00:12:07.730 --> 00:12:10.630 align:start position:0% as I said I'm repeating myself it hats which<00:12:07.880> are<00:12:08.060> matters<00:12:08.420> and<00:12:08.600> so<00:12:08.630> as<00:12:09.560> we<00:12:09.950> can<00:12:10.130> set 00:12:10.630 --> 00:12:10.640 align:start position:0% which are matters and so as we can set 00:12:10.640 --> 00:12:13.240 align:start position:0% which are matters and so as we can set up<00:12:10.820> the<00:12:10.970> rule<00:12:11.180> that's<00:12:11.420> our<00:12:11.570> own<00:12:11.750> game<00:12:12.020> so<00:12:12.250> we 00:12:13.240 --> 00:12:13.250 align:start position:0% up the rule that's our own game so we 00:12:13.250 --> 00:12:15.100 align:start position:0% up the rule that's our own game so we can<00:12:13.430> do<00:12:13.520> whatever<00:12:13.670> we<00:12:13.910> want<00:12:14.090> so<00:12:14.390> why<00:12:14.540> not<00:12:14.690> for 00:12:15.100 --> 00:12:15.110 align:start position:0% can do whatever we want so why not for 00:12:15.110 --> 00:12:17.920 align:start position:0% can do whatever we want so why not for instance<00:12:15.470> think<00:12:15.950> of<00:12:16.070> an<00:12:16.850> infrastructure<00:12:17.450> that 00:12:17.920 --> 00:12:17.930 align:start position:0% instance think of an infrastructure that 00:12:17.930 --> 00:12:20.050 align:start position:0% instance think of an infrastructure that would<00:12:18.140> be<00:12:18.260> energy<00:12:18.800> positive<00:12:19.280> no<00:12:19.700> that<00:12:19.880> would 00:12:20.050 --> 00:12:20.060 align:start position:0% would be energy positive no that would 00:12:20.060 --> 00:12:21.880 align:start position:0% would be energy positive no that would produce<00:12:20.240> more<00:12:20.390> energy<00:12:20.990> that<00:12:21.110> in<00:12:21.290> consumes<00:12:21.740> I 00:12:21.880 --> 00:12:21.890 align:start position:0% produce more energy that in consumes I 00:12:21.890 --> 00:12:24.690 align:start position:0% produce more energy that in consumes I mean<00:12:22.400> a<00:12:22.490> charger<00:12:22.820> up<00:12:22.970> to<00:12:23.240> us<00:12:23.360> to<00:12:23.570> decide<00:12:23.930> this 00:12:24.690 --> 00:12:24.700 align:start position:0% mean a charger up to us to decide this 00:12:24.700 --> 00:12:28.630 align:start position:0% mean a charger up to us to decide this okay<00:12:25.700> so<00:12:25.760> just<00:12:26.450> to<00:12:26.540> find<00:12:26.840> some<00:12:27.160> some<00:12:28.160> dude<00:12:28.400> and 00:12:28.630 --> 00:12:28.640 align:start position:0% okay so just to find some some dude and 00:12:28.640 --> 00:12:30.880 align:start position:0% okay so just to find some some dude and one<00:12:28.820> showing<00:12:29.090> the<00:12:29.210> blockchain<00:12:29.480> lab<00:12:29.840> Dacca<00:12:30.530> had 00:12:30.880 --> 00:12:30.890 align:start position:0% one showing the blockchain lab Dacca had 00:12:30.890 --> 00:12:32.770 align:start position:0% one showing the blockchain lab Dacca had the<00:12:31.070> French<00:12:31.310> team<00:12:31.520> who<00:12:31.610> has<00:12:31.730> been<00:12:31.760> a<00:12:32.120> very 00:12:32.770 --> 00:12:32.780 align:start position:0% the French team who has been a very 00:12:32.780 --> 00:12:40.000 align:start position:0% the French team who has been a very supportive<00:12:33.140> with<00:12:33.770> us<00:12:36.430> thank<00:12:37.430> you<00:12:37.520> very<00:12:37.610> much