WEBVTT Kind: captions Language: en 00:00:13.629 --> 00:00:16.180 align:start position:0% okay<00:00:14.629> so<00:00:14.809> thank<00:00:15.110> you<00:00:15.289> today<00:00:15.829> I'm<00:00:15.919> going<00:00:16.100> to 00:00:16.180 --> 00:00:16.190 align:start position:0% okay so thank you today I'm going to 00:00:16.190 --> 00:00:19.570 align:start position:0% okay so thank you today I'm going to present<00:00:16.460> you<00:00:16.730> or<00:00:17.060> solutions<00:00:18.050> for<00:00:18.410> a<00:00:18.580> efficient 00:00:19.570 --> 00:00:19.580 align:start position:0% present you or solutions for a efficient 00:00:19.580 --> 00:00:22.240 align:start position:0% present you or solutions for a efficient and<00:00:19.700> scalable<00:00:19.790> on<00:00:20.450> option<00:00:21.290> execution<00:00:22.040> for 00:00:22.240 --> 00:00:22.250 align:start position:0% and scalable on option execution for 00:00:22.250 --> 00:00:26.830 align:start position:0% and scalable on option execution for arbitrary<00:00:22.850> application<00:00:23.330> for<00:00:25.510> aetherium<00:00:26.510> so 00:00:26.830 --> 00:00:26.840 align:start position:0% arbitrary application for aetherium so 00:00:26.840 --> 00:00:29.490 align:start position:0% arbitrary application for aetherium so we<00:00:26.990> are<00:00:27.110> I<00:00:27.140> exactly<00:00:27.650> I'm<00:00:28.730> fed<00:00:28.910> up 00:00:29.490 --> 00:00:29.500 align:start position:0% we are I exactly I'm fed up 00:00:29.500 --> 00:00:32.799 align:start position:0% we are I exactly I'm fed up so<00:00:30.500> first<00:00:30.830> let's<00:00:31.190> thanks<00:00:31.970> and<00:00:32.149> give<00:00:32.329> the<00:00:32.450> be 00:00:32.799 --> 00:00:32.809 align:start position:0% so first let's thanks and give the be 00:00:32.809 --> 00:00:34.900 align:start position:0% so first let's thanks and give the be close<00:00:33.140> to<00:00:33.289> the<00:00:33.410> team<00:00:33.680> because<00:00:33.950> they<00:00:34.640> worked 00:00:34.900 --> 00:00:34.910 align:start position:0% close to the team because they worked 00:00:34.910 --> 00:00:37.240 align:start position:0% close to the team because they worked really<00:00:35.060> hard<00:00:35.390> to<00:00:36.380> be<00:00:36.530> ready<00:00:36.770> for<00:00:36.890> their 00:00:37.240 --> 00:00:37.250 align:start position:0% really hard to be ready for their 00:00:37.250 --> 00:00:39.640 align:start position:0% really hard to be ready for their country<00:00:37.730> and<00:00:37.940> having<00:00:38.540> this<00:00:38.810> release<00:00:39.140> ready 00:00:39.640 --> 00:00:39.650 align:start position:0% country and having this release ready 00:00:39.650 --> 00:00:42.280 align:start position:0% country and having this release ready some<00:00:40.070> of<00:00:40.250> us<00:00:40.760> are<00:00:41.120> here<00:00:41.510> we<00:00:41.720> are<00:00:41.750> at<00:00:41.930> the<00:00:42.079> booth 00:00:42.280 --> 00:00:42.290 align:start position:0% some of us are here we are at the booth 00:00:42.290 --> 00:00:46.870 align:start position:0% some of us are here we are at the booth just<00:00:43.070> over<00:00:43.550> there<00:00:43.790> at<00:00:44.120> the<00:00:45.460> the<00:00:46.460> outside<00:00:46.760> of 00:00:46.870 --> 00:00:46.880 align:start position:0% just over there at the the outside of 00:00:46.880 --> 00:00:50.350 align:start position:0% just over there at the the outside of this<00:00:47.000> of<00:00:47.690> this<00:00:47.899> conference<00:00:48.500> room<00:00:49.090> so<00:00:50.090> we<00:00:50.270> all 00:00:50.350 --> 00:00:50.360 align:start position:0% this of this conference room so we all 00:00:50.360 --> 00:00:53.530 align:start position:0% this of this conference room so we all know<00:00:50.570> about<00:00:51.230> 15<00:00:51.620> people<00:00:51.920> in<00:00:52.100> yo<00:00:52.280> in<00:00:52.610> front<00:00:53.329> and 00:00:53.530 --> 00:00:53.540 align:start position:0% know about 15 people in yo in front and 00:00:53.540 --> 00:00:55.240 align:start position:0% know about 15 people in yo in front and we<00:00:53.989> are<00:00:54.079> going<00:00:54.260> to<00:00:54.410> be<00:00:54.530> a<00:00:54.559> little<00:00:54.860> more<00:00:54.980> formal 00:00:55.240 --> 00:00:55.250 align:start position:0% we are going to be a little more formal 00:00:55.250 --> 00:00:58.240 align:start position:0% we are going to be a little more formal joining<00:00:55.880> us<00:00:56.090> by<00:00:56.870> the<00:00:56.930> end<00:00:57.140> of<00:00:57.230> this<00:00:57.350> year<00:00:57.620> so 00:00:58.240 --> 00:00:58.250 align:start position:0% joining us by the end of this year so 00:00:58.250 --> 00:01:00.069 align:start position:0% joining us by the end of this year so that's<00:00:58.399> a<00:00:58.579> wonderful<00:00:58.760> team<00:00:59.270> and<00:00:59.480> I'm<00:00:59.540> really 00:01:00.069 --> 00:01:00.079 align:start position:0% that's a wonderful team and I'm really 00:01:00.079 --> 00:01:02.799 align:start position:0% that's a wonderful team and I'm really proud<00:01:00.260> of<00:01:00.380> them<00:01:00.590> so<00:01:01.399> what<00:01:01.610> we<00:01:01.730> are<00:01:01.820> doing<00:01:01.850> at<00:01:02.360> I 00:01:02.799 --> 00:01:02.809 align:start position:0% proud of them so what we are doing at I 00:01:02.809 --> 00:01:05.170 align:start position:0% proud of them so what we are doing at I exam<00:01:03.290> are<00:01:03.530> doing<00:01:03.770> the<00:01:03.980> etherium<00:01:04.850> based 00:01:05.170 --> 00:01:05.180 align:start position:0% exam are doing the etherium based 00:01:05.180 --> 00:01:07.600 align:start position:0% exam are doing the etherium based decentralized<00:01:05.870> cloud<00:01:06.440> computing<00:01:07.010> which 00:01:07.600 --> 00:01:07.610 align:start position:0% decentralized cloud computing which 00:01:07.610 --> 00:01:09.789 align:start position:0% decentralized cloud computing which means<00:01:07.970> that<00:01:08.299> we<00:01:08.780> are<00:01:08.840> using<00:01:09.020> the<00:01:09.350> aphelion 00:01:09.789 --> 00:01:09.799 align:start position:0% means that we are using the aphelion 00:01:09.799 --> 00:01:12.190 align:start position:0% means that we are using the aphelion blockchain<00:01:10.310> to<00:01:10.729> create<00:01:11.090> a<00:01:11.330> decentralized 00:01:12.190 --> 00:01:12.200 align:start position:0% blockchain to create a decentralized 00:01:12.200 --> 00:01:13.840 align:start position:0% blockchain to create a decentralized marketplace<00:01:12.830> for<00:01:13.490> cloud<00:01:13.820> computing 00:01:13.840 --> 00:01:13.850 align:start position:0% marketplace for cloud computing 00:01:13.850 --> 00:01:14.950 align:start position:0% marketplace for cloud computing resources 00:01:14.950 --> 00:01:14.960 align:start position:0% resources 00:01:14.960 --> 00:01:17.320 align:start position:0% resources so<00:01:15.560> those<00:01:15.740> computing<00:01:16.250> resources<00:01:16.670> that<00:01:17.090> can<00:01:17.270> be 00:01:17.320 --> 00:01:17.330 align:start position:0% so those computing resources that can be 00:01:17.330 --> 00:01:19.830 align:start position:0% so those computing resources that can be what<00:01:17.960> you<00:01:17.990> typically<00:01:18.470> found<00:01:18.740> in<00:01:18.950> a<00:01:19.130> cloud<00:01:19.400> so 00:01:19.830 --> 00:01:19.840 align:start position:0% what you typically found in a cloud so 00:01:19.840 --> 00:01:23.190 align:start position:0% what you typically found in a cloud so servers<00:01:20.840> applications<00:01:21.740> and<00:01:22.070> data<00:01:22.280> datasets 00:01:23.190 --> 00:01:23.200 align:start position:0% servers applications and data datasets 00:01:23.200 --> 00:01:25.300 align:start position:0% servers applications and data datasets and<00:01:24.200> so<00:01:24.350> we<00:01:24.470> are<00:01:24.530> using<00:01:24.650> the<00:01:24.860> theory<00:01:25.130> on 00:01:25.300 --> 00:01:25.310 align:start position:0% and so we are using the theory on 00:01:25.310 --> 00:01:27.310 align:start position:0% and so we are using the theory on blockchain<00:01:25.880> to<00:01:26.240> advertise<00:01:26.720> and<00:01:26.900> project 00:01:27.310 --> 00:01:27.320 align:start position:0% blockchain to advertise and project 00:01:27.320 --> 00:01:29.649 align:start position:0% blockchain to advertise and project those<00:01:27.560> are<00:01:27.740> computing<00:01:28.130> resources<00:01:28.580> so<00:01:29.390> you<00:01:29.450> can 00:01:29.649 --> 00:01:29.659 align:start position:0% those are computing resources so you can 00:01:29.659 --> 00:01:32.500 align:start position:0% those are computing resources so you can figure<00:01:29.869> that<00:01:30.020> a<00:01:30.260> sort<00:01:30.530> of<00:01:30.680> Airbnb<00:01:31.159> for<00:01:31.909> servers 00:01:32.500 --> 00:01:32.510 align:start position:0% figure that a sort of Airbnb for servers 00:01:32.510 --> 00:01:35.410 align:start position:0% figure that a sort of Airbnb for servers but<00:01:33.080> without<00:01:33.470> Airbnb<00:01:34.310> and<00:01:34.520> of<00:01:34.909> course<00:01:35.180> in<00:01:35.330> this 00:01:35.410 --> 00:01:35.420 align:start position:0% but without Airbnb and of course in this 00:01:35.420 --> 00:01:37.929 align:start position:0% but without Airbnb and of course in this case<00:01:35.720> this<00:01:35.900> is<00:01:36.110> the<00:01:36.229> blockchain<00:01:36.549> that<00:01:37.549> creates 00:01:37.929 --> 00:01:37.939 align:start position:0% case this is the blockchain that creates 00:01:37.939 --> 00:01:40.359 align:start position:0% case this is the blockchain that creates those<00:01:38.600> are<00:01:38.869> peer<00:01:39.049> to<00:01:39.170> peer<00:01:39.369> interactions 00:01:40.359 --> 00:01:40.369 align:start position:0% those are peer to peer interactions 00:01:40.369 --> 00:01:43.330 align:start position:0% those are peer to peer interactions between<00:01:40.880> the<00:01:41.180> users<00:01:41.600> and<00:01:41.869> the<00:01:41.930> providers<00:01:42.530> so 00:01:43.330 --> 00:01:43.340 align:start position:0% between the users and the providers so 00:01:43.340 --> 00:01:46.060 align:start position:0% between the users and the providers so having<00:01:43.700> a<00:01:43.970> decentralized<00:01:44.659> cloud<00:01:45.409> why<00:01:45.740> does<00:01:45.920> it 00:01:46.060 --> 00:01:46.070 align:start position:0% having a decentralized cloud why does it 00:01:46.070 --> 00:01:48.609 align:start position:0% having a decentralized cloud why does it matter<00:01:46.250> for<00:01:46.700> two<00:01:47.299> main<00:01:47.630> reasons<00:01:47.659> I<00:01:48.259> would<00:01:48.320> say 00:01:48.609 --> 00:01:48.619 align:start position:0% matter for two main reasons I would say 00:01:48.619 --> 00:01:51.219 align:start position:0% matter for two main reasons I would say the<00:01:49.400> first<00:01:49.610> one<00:01:49.909> is<00:01:50.180> that<00:01:50.210> we<00:01:50.689> can<00:01:50.900> see<00:01:51.110> that 00:01:51.219 --> 00:01:51.229 align:start position:0% the first one is that we can see that 00:01:51.229 --> 00:01:53.620 align:start position:0% the first one is that we can see that this<00:01:51.590> conference<00:01:52.040> there<00:01:52.790> are<00:01:52.970> more<00:01:53.240> and<00:01:53.420> more 00:01:53.620 --> 00:01:53.630 align:start position:0% this conference there are more and more 00:01:53.630 --> 00:01:56.350 align:start position:0% this conference there are more and more new<00:01:54.200> decentralized<00:01:54.950> application<00:01:55.700> it<00:01:56.180> is 00:01:56.350 --> 00:01:56.360 align:start position:0% new decentralized application it is 00:01:56.360 --> 00:01:58.690 align:start position:0% new decentralized application it is coming<00:01:56.810> a<00:01:56.960> new<00:01:56.990> a<00:01:57.229> decentralized<00:01:57.920> economy<00:01:58.490> and 00:01:58.690 --> 00:01:58.700 align:start position:0% coming a new a decentralized economy and 00:01:58.700 --> 00:02:01.539 align:start position:0% coming a new a decentralized economy and so<00:01:59.180> we<00:01:59.360> now<00:01:59.570> need<00:01:59.840> a<00:02:00.110> natural<00:02:00.829> infrastructure 00:02:01.539 --> 00:02:01.549 align:start position:0% so we now need a natural infrastructure 00:02:01.549 --> 00:02:03.700 align:start position:0% so we now need a natural infrastructure to<00:02:01.909> support<00:02:02.060> those<00:02:02.390> new<00:02:02.600> application<00:02:03.290> that's 00:02:03.700 --> 00:02:03.710 align:start position:0% to support those new application that's 00:02:03.710 --> 00:02:05.710 align:start position:0% to support those new application that's the<00:02:03.829> first<00:02:04.070> reason<00:02:04.400> and<00:02:04.610> the<00:02:05.119> second<00:02:05.479> reason 00:02:05.710 --> 00:02:05.720 align:start position:0% the first reason and the second reason 00:02:05.720 --> 00:02:09.839 align:start position:0% the first reason and the second reason is<00:02:06.110> that<00:02:06.470> is<00:02:06.950> this<00:02:07.189> is<00:02:08.170> decentralized<00:02:09.170> cloud 00:02:09.839 --> 00:02:09.849 align:start position:0% is that is this is decentralized cloud 00:02:09.849 --> 00:02:12.760 align:start position:0% is that is this is decentralized cloud the<00:02:10.849> infrastructure<00:02:11.360> is<00:02:11.420> going<00:02:11.500> to<00:02:12.500> be<00:02:12.620> very 00:02:12.760 --> 00:02:12.770 align:start position:0% the infrastructure is going to be very 00:02:12.770 --> 00:02:14.860 align:start position:0% the infrastructure is going to be very different<00:02:13.099> it's<00:02:13.400> going<00:02:13.580> to<00:02:13.700> be<00:02:13.819> distributed 00:02:14.860 --> 00:02:14.870 align:start position:0% different it's going to be distributed 00:02:14.870 --> 00:02:17.020 align:start position:0% different it's going to be distributed and<00:02:14.980> probably<00:02:15.980> compared<00:02:16.700> to<00:02:16.879> the 00:02:17.020 --> 00:02:17.030 align:start position:0% and probably compared to the 00:02:17.030 --> 00:02:18.640 align:start position:0% and probably compared to the essentialist<00:02:17.540> cloud<00:02:17.780> we're<00:02:18.019> going<00:02:18.230> to<00:02:18.409> have 00:02:18.640 --> 00:02:18.650 align:start position:0% essentialist cloud we're going to have 00:02:18.650 --> 00:02:21.399 align:start position:0% essentialist cloud we're going to have many<00:02:19.250> advantages<00:02:19.629> because<00:02:20.629> a<00:02:20.810> marketplace 00:02:21.399 --> 00:02:21.409 align:start position:0% many advantages because a marketplace 00:02:21.409 --> 00:02:23.589 align:start position:0% many advantages because a marketplace not<00:02:21.620> only<00:02:21.799> going<00:02:21.980> to<00:02:22.099> be<00:02:22.220> much<00:02:22.700> cheaper<00:02:22.730> it's 00:02:23.589 --> 00:02:23.599 align:start position:0% not only going to be much cheaper it's 00:02:23.599 --> 00:02:25.809 align:start position:0% not only going to be much cheaper it's going<00:02:23.900> to<00:02:24.019> be<00:02:24.140> distributed<00:02:24.319> that<00:02:24.890> going<00:02:25.400> to<00:02:25.700> be 00:02:25.809 --> 00:02:25.819 align:start position:0% going to be distributed that going to be 00:02:25.819 --> 00:02:28.420 align:start position:0% going to be distributed that going to be greener<00:02:26.690> and<00:02:27.019> certainly<00:02:27.379> more<00:02:27.830> efficient 00:02:28.420 --> 00:02:28.430 align:start position:0% greener and certainly more efficient 00:02:28.430 --> 00:02:30.280 align:start position:0% greener and certainly more efficient because<00:02:28.790> the<00:02:29.090> data<00:02:29.299> are<00:02:29.510> going<00:02:29.810> to<00:02:29.900> be<00:02:30.019> closer 00:02:30.280 --> 00:02:30.290 align:start position:0% because the data are going to be closer 00:02:30.290 --> 00:02:35.020 align:start position:0% because the data are going to be closer to<00:02:31.010> the<00:02:31.190> to<00:02:31.670> the<00:02:31.790> consumer<00:02:32.269> or<00:02:32.299> producer<00:02:34.030> so 00:02:35.020 --> 00:02:35.030 align:start position:0% to the to the consumer or producer so 00:02:35.030 --> 00:02:37.030 align:start position:0% to the to the consumer or producer so what<00:02:35.450> are<00:02:35.599> the<00:02:35.780> the<00:02:36.260> applications<00:02:36.890> we<00:02:37.010> are 00:02:37.030 --> 00:02:37.040 align:start position:0% what are the the applications we are 00:02:37.040 --> 00:02:39.369 align:start position:0% what are the the applications we are targeting<00:02:37.420> first<00:02:38.420> we<00:02:38.599> are<00:02:38.659> looking<00:02:39.019> at<00:02:39.200> the 00:02:39.369 --> 00:02:39.379 align:start position:0% targeting first we are looking at the 00:02:39.379 --> 00:02:42.009 align:start position:0% targeting first we are looking at the blockchain<00:02:39.769> base<00:02:40.480> distributed<00:02:41.480> application 00:02:42.009 --> 00:02:42.019 align:start position:0% blockchain base distributed application 00:02:42.019 --> 00:02:43.690 align:start position:0% blockchain base distributed application the<00:02:42.200> Dubs<00:02:42.409> so<00:02:42.739> the<00:02:42.890> application<00:02:43.519> that 00:02:43.690 --> 00:02:43.700 align:start position:0% the Dubs so the application that 00:02:43.700 --> 00:02:45.670 align:start position:0% the Dubs so the application that executes<00:02:44.150> on<00:02:44.239> the<00:02:44.360> blockchain<00:02:44.569> and<00:02:44.989> you<00:02:45.560> know 00:02:45.670 --> 00:02:45.680 align:start position:0% executes on the blockchain and you know 00:02:45.680 --> 00:02:49.630 align:start position:0% executes on the blockchain and you know that<00:02:46.540> the<00:02:47.540> etherium<00:02:48.200> virtual<00:02:48.560> machine<00:02:49.069> offer 00:02:49.630 --> 00:02:49.640 align:start position:0% that the etherium virtual machine offer 00:02:49.640 --> 00:02:52.330 align:start position:0% that the etherium virtual machine offer very<00:02:50.569> few<00:02:50.959> computing<00:02:51.410> capacities<00:02:52.010> to<00:02:52.040> those 00:02:52.330 --> 00:02:52.340 align:start position:0% very few computing capacities to those 00:02:52.340 --> 00:02:54.759 align:start position:0% very few computing capacities to those application<00:02:53.000> the<00:02:53.480> processing<00:02:54.079> is<00:02:54.349> very<00:02:54.379> low 00:02:54.759 --> 00:02:54.769 align:start position:0% application the processing is very low 00:02:54.769 --> 00:02:57.099 align:start position:0% application the processing is very low it's<00:02:55.220> extremely<00:02:55.790> expensive<00:02:56.150> for<00:02:56.420> storage<00:02:56.959> and 00:02:57.099 --> 00:02:57.109 align:start position:0% it's extremely expensive for storage and 00:02:57.109 --> 00:02:59.470 align:start position:0% it's extremely expensive for storage and computation<00:02:57.440> and<00:02:57.980> so<00:02:58.489> they<00:02:58.670> need<00:02:58.879> option 00:02:59.470 --> 00:02:59.480 align:start position:0% computation and so they need option 00:02:59.480 --> 00:03:02.830 align:start position:0% computation and so they need option computation<00:02:59.959> to<00:03:00.739> have<00:03:01.250> an<00:03:01.370> actual<00:03:01.670> I<00:03:02.239> mean<00:03:02.720> to 00:03:02.830 --> 00:03:02.840 align:start position:0% computation to have an actual I mean to 00:03:02.840 --> 00:03:05.050 align:start position:0% computation to have an actual I mean to be<00:03:02.959> a<00:03:02.989> really<00:03:03.230> important<00:03:03.650> application<00:03:04.250> the 00:03:05.050 --> 00:03:05.060 align:start position:0% be a really important application the 00:03:05.060 --> 00:03:06.640 align:start position:0% be a really important application the second<00:03:05.390> category<00:03:05.569> is<00:03:05.930> what<00:03:06.170> we<00:03:06.319> call<00:03:06.530> the 00:03:06.640 --> 00:03:06.650 align:start position:0% second category is what we call the 00:03:06.650 --> 00:03:09.250 align:start position:0% second category is what we call the legacy<00:03:07.099> application<00:03:07.790> those<00:03:08.450> are<00:03:08.840> these<00:03:09.079> up 00:03:09.250 --> 00:03:09.260 align:start position:0% legacy application those are these up 00:03:09.260 --> 00:03:11.890 align:start position:0% legacy application those are these up the<00:03:09.620> application<00:03:10.250> running<00:03:10.700> now<00:03:11.209> on<00:03:11.450> the<00:03:11.569> cloud 00:03:11.890 --> 00:03:11.900 align:start position:0% the application running now on the cloud 00:03:11.900 --> 00:03:14.259 align:start position:0% the application running now on the cloud that<00:03:12.680> would<00:03:12.920> eventually<00:03:13.280> come<00:03:13.790> to 00:03:14.259 --> 00:03:14.269 align:start position:0% that would eventually come to 00:03:14.269 --> 00:03:16.780 align:start position:0% that would eventually come to infrastructure<00:03:15.260> because<00:03:15.920> we<00:03:16.040> can<00:03:16.220> offer<00:03:16.370> a 00:03:16.780 --> 00:03:16.790 align:start position:0% infrastructure because we can offer a 00:03:16.790 --> 00:03:19.979 align:start position:0% infrastructure because we can offer a better<00:03:17.299> price<00:03:18.260> per<00:03:18.290> price<00:03:19.250> performance<00:03:19.519> ratio 00:03:19.979 --> 00:03:19.989 align:start position:0% better price per price performance ratio 00:03:19.989 --> 00:03:23.110 align:start position:0% better price per price performance ratio so<00:03:20.989> here<00:03:21.380> we<00:03:21.530> are<00:03:21.560> thinking<00:03:21.769> of<00:03:22.220> applications 00:03:23.110 --> 00:03:23.120 align:start position:0% so here we are thinking of applications 00:03:23.120 --> 00:03:26.370 align:start position:0% so here we are thinking of applications such<00:03:23.419> as<00:03:23.739> simulations<00:03:24.739> machine<00:03:25.549> learning 00:03:26.370 --> 00:03:26.380 align:start position:0% such as simulations machine learning 00:03:26.380 --> 00:03:29.949 align:start position:0% such as simulations machine learning finance<00:03:27.380> 3d<00:03:27.950> rendering<00:03:28.489> and<00:03:28.669> so<00:03:28.819> forth<00:03:29.060> and 00:03:29.949 --> 00:03:29.959 align:start position:0% finance 3d rendering and so forth and 00:03:29.959 --> 00:03:33.909 align:start position:0% finance 3d rendering and so forth and the<00:03:30.739> next<00:03:31.040> category<00:03:31.910> are<00:03:32.120> those<00:03:33.019> applications 00:03:33.909 --> 00:03:33.919 align:start position:0% the next category are those applications 00:03:33.919 --> 00:03:37.210 align:start position:0% the next category are those applications the<00:03:34.549> data<00:03:34.790> as<00:03:35.569> close<00:03:35.959> as<00:03:36.079> possible<00:03:36.169> to<00:03:36.560> the 00:03:37.210 --> 00:03:37.220 align:start position:0% the data as close as possible to the 00:03:37.220 --> 00:03:39.490 align:start position:0% the data as close as possible to the origin<00:03:37.669> so<00:03:38.239> people<00:03:38.629> talk<00:03:38.840> about<00:03:39.079> the<00:03:39.349> de 00:03:39.490 --> 00:03:39.500 align:start position:0% origin so people talk about the de 00:03:39.500 --> 00:03:41.140 align:start position:0% origin so people talk about the de Kooning<00:03:39.650> that<00:03:39.980> fog<00:03:40.370> or<00:03:40.609> edge<00:03:40.849> server 00:03:41.140 --> 00:03:41.150 align:start position:0% Kooning that fog or edge server 00:03:41.150 --> 00:03:47.650 align:start position:0% Kooning that fog or edge server computing<00:03:43.419> so<00:03:44.419> with<00:03:45.109> the<00:03:45.530> one<00:03:46.010> of<00:03:46.129> the<00:03:46.250> key<00:03:46.660> the 00:03:47.650 --> 00:03:47.660 align:start position:0% computing so with the one of the key the 00:03:47.660 --> 00:03:50.879 align:start position:0% computing so with the one of the key the fundamental<00:03:48.549> point<00:03:49.549> in<00:03:49.760> the<00:03:49.879> protocol<00:03:50.359> is<00:03:50.599> the 00:03:50.879 --> 00:03:50.889 align:start position:0% fundamental point in the protocol is the 00:03:50.889 --> 00:03:54.009 align:start position:0% fundamental point in the protocol is the exact<00:03:51.889> tokens<00:03:52.280> called<00:03:52.519> RLC<00:03:52.970> so<00:03:53.780> this<00:03:53.900> is<00:03:53.989> a 00:03:54.009 --> 00:03:54.019 align:start position:0% exact tokens called RLC so this is a 00:03:54.019 --> 00:03:56.920 align:start position:0% exact tokens called RLC so this is a pure<00:03:54.290> utility<00:03:54.769> token<00:03:55.449> this<00:03:56.449> is<00:03:56.629> the<00:03:56.780> way 00:03:56.920 --> 00:03:56.930 align:start position:0% pure utility token this is the way 00:03:56.930 --> 00:04:00.129 align:start position:0% pure utility token this is the way people<00:03:56.959> can<00:03:57.590> enter<00:03:57.859> the<00:03:58.250> network<00:03:58.430> and<00:03:58.940> use<00:03:59.269> the 00:04:00.129 --> 00:04:00.139 align:start position:0% people can enter the network and use the 00:04:00.139 --> 00:04:01.869 align:start position:0% people can enter the network and use the computing<00:04:00.650> resources<00:04:00.680> that<00:04:01.549> I<00:04:01.699> need<00:04:01.790> is 00:04:01.869 --> 00:04:01.879 align:start position:0% computing resources that I need is 00:04:01.879 --> 00:04:04.330 align:start position:0% computing resources that I need is decentralized<00:04:02.299> cloud<00:04:02.900> and<00:04:03.379> this<00:04:03.650> is<00:04:03.829> also<00:04:04.010> the 00:04:04.330 --> 00:04:04.340 align:start position:0% decentralized cloud and this is also the 00:04:04.340 --> 00:04:06.759 align:start position:0% decentralized cloud and this is also the way<00:04:04.690> provider<00:04:05.690> for<00:04:06.109> resources<00:04:06.560> or 00:04:06.759 --> 00:04:06.769 align:start position:0% way provider for resources or 00:04:06.769 --> 00:04:09.460 align:start position:0% way provider for resources or application<00:04:07.489> are<00:04:07.790> being<00:04:08.209> paid<00:04:08.510> and<00:04:08.720> this<00:04:09.290> is 00:04:09.460 --> 00:04:09.470 align:start position:0% application are being paid and this is 00:04:09.470 --> 00:04:11.589 align:start position:0% application are being paid and this is very<00:04:09.650> important<00:04:10.069> also<00:04:10.220> because<00:04:10.400> it<00:04:11.209> allows<00:04:11.569> to 00:04:11.589 --> 00:04:11.599 align:start position:0% very important also because it allows to 00:04:11.599 --> 00:04:13.960 align:start position:0% very important also because it allows to create<00:04:11.930> incentives<00:04:12.859> in<00:04:13.040> the<00:04:13.250> protocol<00:04:13.579> and 00:04:13.960 --> 00:04:13.970 align:start position:0% create incentives in the protocol and 00:04:13.970 --> 00:04:15.369 align:start position:0% create incentives in the protocol and that's<00:04:14.180> something<00:04:14.569> that<00:04:14.720> is<00:04:14.840> really<00:04:15.199> new 00:04:15.369 --> 00:04:15.379 align:start position:0% that's something that is really new 00:04:15.379 --> 00:04:17.529 align:start position:0% that's something that is really new compared<00:04:16.190> that<00:04:16.669> can<00:04:16.820> be<00:04:16.940> eventually<00:04:17.449> an 00:04:17.529 --> 00:04:17.539 align:start position:0% compared that can be eventually an 00:04:17.539 --> 00:04:20.020 align:start position:0% compared that can be eventually an advantage<00:04:18.380> compared<00:04:19.039> with<00:04:19.190> the<00:04:19.340> existing 00:04:20.020 --> 00:04:20.030 align:start position:0% advantage compared with the existing 00:04:20.030 --> 00:04:22.390 align:start position:0% advantage compared with the existing cloud<00:04:20.510> and<00:04:21.049> the<00:04:21.139> way<00:04:21.260> we're<00:04:21.440> doing<00:04:21.560> this<00:04:21.680> so<00:04:22.370> we 00:04:22.390 --> 00:04:22.400 align:start position:0% cloud and the way we're doing this so we 00:04:22.400 --> 00:04:25.240 align:start position:0% cloud and the way we're doing this so we should<00:04:22.550> this<00:04:23.210> token<00:04:23.599> on<00:04:23.750> my<00:04:23.870> net<00:04:24.110> and<00:04:24.349> elastic 00:04:25.240 --> 00:04:25.250 align:start position:0% should this token on my net and elastic 00:04:25.250 --> 00:04:26.520 align:start position:0% should this token on my net and elastic freedom<00:04:25.669> 2000 00:04:26.520 --> 00:04:26.530 align:start position:0% freedom 2000 00:04:26.530 --> 00:04:30.540 align:start position:0% freedom 2000 17<00:04:27.690> so<00:04:28.690> the<00:04:28.990> roadmap<00:04:29.380> where<00:04:29.590> we<00:04:29.860> are<00:04:30.010> now<00:04:30.220> so<00:04:30.430> we 00:04:30.540 --> 00:04:30.550 align:start position:0% 17 so the roadmap where we are now so we 00:04:30.550 --> 00:04:32.490 align:start position:0% 17 so the roadmap where we are now so we started<00:04:31.030> about<00:04:31.540> six<00:04:31.930> months<00:04:32.230> ago 00:04:32.490 --> 00:04:32.500 align:start position:0% started about six months ago 00:04:32.500 --> 00:04:38.070 align:start position:0% started about six months ago we<00:04:33.490> are<00:04:33.610> now<00:04:34.800> the<00:04:35.800> first<00:04:36.430> version<00:04:36.820> of<00:04:37.080> Apple 00:04:38.070 --> 00:04:38.080 align:start position:0% we are now the first version of Apple 00:04:38.080 --> 00:04:40.830 align:start position:0% we are now the first version of Apple you<00:04:38.139> have<00:04:38.230> i<00:04:38.740> exac<00:04:39.280> so<00:04:39.520> the<00:04:40.030> way<00:04:40.210> when<00:04:40.690> you 00:04:40.830 --> 00:04:40.840 align:start position:0% you have i exac so the way when you 00:04:40.840 --> 00:04:43.470 align:start position:0% you have i exac so the way when you create<00:04:41.380> a<00:04:41.740> distribute<00:04:42.490> in<00:04:42.610> is<00:04:42.730> hot<00:04:42.940> switcher 00:04:43.470 --> 00:04:43.480 align:start position:0% create a distribute in is hot switcher 00:04:43.480 --> 00:04:45.120 align:start position:0% create a distribute in is hot switcher it's<00:04:43.690> a<00:04:43.780> kind<00:04:44.020> of<00:04:44.169> a<00:04:44.290> chicken<00:04:44.620> and<00:04:44.680> egg<00:04:44.860> problem 00:04:45.120 --> 00:04:45.130 align:start position:0% it's a kind of a chicken and egg problem 00:04:45.130 --> 00:04:48.120 align:start position:0% it's a kind of a chicken and egg problem do<00:04:45.910> you<00:04:46.030> first<00:04:46.330> start<00:04:46.630> to<00:04:46.930> have<00:04:47.500> the<00:04:47.680> machines 00:04:48.120 --> 00:04:48.130 align:start position:0% do you first start to have the machines 00:04:48.130 --> 00:04:50.640 align:start position:0% do you first start to have the machines and<00:04:48.400> then<00:04:49.000> in<00:04:49.360> the<00:04:49.510> network<00:04:49.930> and<00:04:50.169> then<00:04:50.260> you<00:04:50.290> try 00:04:50.640 --> 00:04:50.650 align:start position:0% and then in the network and then you try 00:04:50.650 --> 00:04:52.350 align:start position:0% and then in the network and then you try to<00:04:50.710> find<00:04:50.980> some<00:04:51.190> application<00:04:51.820> to<00:04:51.970> run<00:04:52.090> on<00:04:52.240> this 00:04:52.350 --> 00:04:52.360 align:start position:0% to find some application to run on this 00:04:52.360 --> 00:04:55.140 align:start position:0% to find some application to run on this machine<00:04:52.660> or<00:04:53.290> do<00:04:53.650> you<00:04:53.740> first<00:04:54.040> start<00:04:54.340> to<00:04:54.580> with 00:04:55.140 --> 00:04:55.150 align:start position:0% machine or do you first start to with 00:04:55.150 --> 00:04:57.450 align:start position:0% machine or do you first start to with the<00:04:55.360> applications<00:04:56.169> and<00:04:56.440> then<00:04:56.620> once<00:04:57.250> you<00:04:57.430> know 00:04:57.450 --> 00:04:57.460 align:start position:0% the applications and then once you know 00:04:57.460 --> 00:05:00.990 align:start position:0% the applications and then once you know the<00:04:57.940> application<00:04:58.560> you<00:04:59.560> then<00:04:59.890> you<00:05:00.010> can<00:05:00.190> create 00:05:00.990 --> 00:05:01.000 align:start position:0% the application you then you can create 00:05:01.000 --> 00:05:03.570 align:start position:0% the application you then you can create a<00:05:01.330> relevant<00:05:01.840> architecture<00:05:02.710> so<00:05:03.250> when<00:05:03.430> we 00:05:03.570 --> 00:05:03.580 align:start position:0% a relevant architecture so when we 00:05:03.580 --> 00:05:07.980 align:start position:0% a relevant architecture so when we design<00:05:03.910> this<00:05:04.060> roadmap<00:05:04.360> for<00:05:05.260> i<00:05:05.770> exac<00:05:06.660> we<00:05:07.660> design 00:05:07.980 --> 00:05:07.990 align:start position:0% design this roadmap for i exac we design 00:05:07.990 --> 00:05:11.640 align:start position:0% design this roadmap for i exac we design it<00:05:08.169> by<00:05:09.330> starting<00:05:10.330> with<00:05:10.540> the<00:05:10.750> application<00:05:11.440> and 00:05:11.640 --> 00:05:11.650 align:start position:0% it by starting with the application and 00:05:11.650 --> 00:05:13.409 align:start position:0% it by starting with the application and particularly<00:05:12.220> with<00:05:12.370> the<00:05:12.490> Dubs<00:05:12.730> and<00:05:13.000> then 00:05:13.409 --> 00:05:13.419 align:start position:0% particularly with the Dubs and then 00:05:13.419 --> 00:05:17.430 align:start position:0% particularly with the Dubs and then later<00:05:13.690> that<00:05:14.110> we<00:05:14.530> come<00:05:14.800> in<00:05:15.790> next<00:05:16.480> May<00:05:16.960> or<00:05:17.169> next 00:05:17.430 --> 00:05:17.440 align:start position:0% later that we come in next May or next 00:05:17.440 --> 00:05:19.350 align:start position:0% later that we come in next May or next June<00:05:17.620> will<00:05:18.130> open<00:05:18.580> the<00:05:18.700> network<00:05:18.910> to<00:05:19.240> the 00:05:19.350 --> 00:05:19.360 align:start position:0% June will open the network to the 00:05:19.360 --> 00:05:21.330 align:start position:0% June will open the network to the servers<00:05:19.810> so<00:05:20.380> it<00:05:20.470> means<00:05:20.710> that<00:05:20.890> at<00:05:21.070> the<00:05:21.190> moment 00:05:21.330 --> 00:05:21.340 align:start position:0% servers so it means that at the moment 00:05:21.340 --> 00:05:23.280 align:start position:0% servers so it means that at the moment you<00:05:21.520> can<00:05:21.610> push<00:05:21.820> any<00:05:21.970> applications<00:05:22.690> but<00:05:23.200> they 00:05:23.280 --> 00:05:23.290 align:start position:0% you can push any applications but they 00:05:23.290 --> 00:05:24.960 align:start position:0% you can push any applications but they are<00:05:23.350> going<00:05:23.470> to<00:05:23.590> be<00:05:23.740> executed<00:05:24.190> on<00:05:24.340> all<00:05:24.580> machine 00:05:24.960 --> 00:05:24.970 align:start position:0% are going to be executed on all machine 00:05:24.970 --> 00:05:27.360 align:start position:0% are going to be executed on all machine so<00:05:25.240> you<00:05:25.270> somehow<00:05:25.780> you<00:05:25.930> have<00:05:26.229> to<00:05:26.260> trust<00:05:26.560> us<00:05:26.740> but 00:05:27.360 --> 00:05:27.370 align:start position:0% so you somehow you have to trust us but 00:05:27.370 --> 00:05:30.180 align:start position:0% so you somehow you have to trust us but later<00:05:27.669> on<00:05:27.820> in<00:05:28.389> next<00:05:29.169> June<00:05:29.380> it<00:05:29.650> would<00:05:29.889> be<00:05:29.979> any 00:05:30.180 --> 00:05:30.190 align:start position:0% later on in next June it would be any 00:05:30.190 --> 00:05:31.469 align:start position:0% later on in next June it would be any machine<00:05:30.610> that<00:05:30.760> can<00:05:30.850> compute<00:05:31.270> any 00:05:31.469 --> 00:05:31.479 align:start position:0% machine that can compute any 00:05:31.479 --> 00:05:35.460 align:start position:0% machine that can compute any applications<00:05:33.390> so<00:05:34.390> we<00:05:34.419> are<00:05:34.720> very<00:05:35.110> pleased 00:05:35.460 --> 00:05:35.470 align:start position:0% applications so we are very pleased 00:05:35.470 --> 00:05:36.840 align:start position:0% applications so we are very pleased today<00:05:35.650> because<00:05:36.130> we<00:05:36.280> are<00:05:36.400> not<00:05:36.550> seeing<00:05:36.729> the 00:05:36.840 --> 00:05:36.850 align:start position:0% today because we are not seeing the 00:05:36.850 --> 00:05:39.600 align:start position:0% today because we are not seeing the first<00:05:37.150> version<00:05:37.600> of<00:05:37.780> AI<00:05:38.200> exact<00:05:38.620> and<00:05:38.860> it's 00:05:39.600 --> 00:05:39.610 align:start position:0% first version of AI exact and it's 00:05:39.610 --> 00:05:42.719 align:start position:0% first version of AI exact and it's called<00:05:39.910> a<00:05:40.030> wonderer<00:05:40.710> so<00:05:41.710> the<00:05:42.100> way<00:05:42.280> we<00:05:42.490> are 00:05:42.719 --> 00:05:42.729 align:start position:0% called a wonderer so the way we are 00:05:42.729 --> 00:05:45.360 align:start position:0% called a wonderer so the way we are naming<00:05:43.000> the<00:05:43.419> exact<00:05:43.900> version<00:05:44.160> we<00:05:45.160> take 00:05:45.360 --> 00:05:45.370 align:start position:0% naming the exact version we take 00:05:45.370 --> 00:05:47.820 align:start position:0% naming the exact version we take characters<00:05:46.000> from<00:05:46.330> the<00:05:46.570> Chinese<00:05:46.930> novel<00:05:47.140> what 00:05:47.820 --> 00:05:47.830 align:start position:0% characters from the Chinese novel what 00:05:47.830 --> 00:05:49.710 align:start position:0% characters from the Chinese novel what imagine<00:05:48.340> so<00:05:49.000> I<00:05:49.030> don't<00:05:49.240> know<00:05:49.300> if<00:05:49.360> you<00:05:49.450> know<00:05:49.570> this 00:05:49.710 --> 00:05:49.720 align:start position:0% imagine so I don't know if you know this 00:05:49.720 --> 00:05:52.320 align:start position:0% imagine so I don't know if you know this novel<00:05:50.110> I<00:05:50.200> love<00:05:50.380> it<00:05:50.530> it's<00:05:50.979> a<00:05:51.160> story<00:05:51.460> of<00:05:51.580> people 00:05:52.320 --> 00:05:52.330 align:start position:0% novel I love it it's a story of people 00:05:52.330 --> 00:05:56.190 align:start position:0% novel I love it it's a story of people who<00:05:52.570> robbers<00:05:53.430> rebelled<00:05:54.430> against<00:05:54.880> the<00:05:55.300> central 00:05:56.190 --> 00:05:56.200 align:start position:0% who robbers rebelled against the central 00:05:56.200 --> 00:06:00.300 align:start position:0% who robbers rebelled against the central authority<00:05:56.740> in<00:05:57.190> middle<00:05:57.940> a<00:05:58.000> China<00:05:58.419> and<00:05:58.979> here<00:05:59.979> the 00:06:00.300 --> 00:06:00.310 align:start position:0% authority in middle a China and here the 00:06:00.310 --> 00:06:03.659 align:start position:0% authority in middle a China and here the one<00:06:00.460> who<00:06:00.490> writes<00:06:00.700> the<00:06:00.940> number<00:06:01.240> 36<00:06:01.870> and<00:06:02.669> among 00:06:03.659 --> 00:06:03.669 align:start position:0% one who writes the number 36 and among 00:06:03.669 --> 00:06:06.630 align:start position:0% one who writes the number 36 and among the<00:06:03.820> durable<00:06:04.510> so<00:06:05.380> this<00:06:05.560> Russian<00:06:05.979> one<00:06:06.220> it's 00:06:06.630 --> 00:06:06.640 align:start position:0% the durable so this Russian one it's 00:06:06.640 --> 00:06:10.020 align:start position:0% the durable so this Russian one it's basically<00:06:07.470> a<00:06:08.470> software<00:06:09.310> development<00:06:09.610> kit 00:06:10.020 --> 00:06:10.030 align:start position:0% basically a software development kit 00:06:10.030 --> 00:06:12.270 align:start position:0% basically a software development kit that<00:06:10.270> allows<00:06:10.630> you<00:06:11.020> to<00:06:11.350> deploy<00:06:12.010> your 00:06:12.270 --> 00:06:12.280 align:start position:0% that allows you to deploy your 00:06:12.280 --> 00:06:15.029 align:start position:0% that allows you to deploy your application<00:06:13.180> on<00:06:13.360> aetherium<00:06:14.200> and<00:06:14.440> i<00:06:14.650> exac 00:06:15.029 --> 00:06:15.039 align:start position:0% application on aetherium and i exac 00:06:15.039 --> 00:06:29.300 align:start position:0% application on aetherium and i exac so<00:06:15.520> I'm<00:06:15.610> going<00:06:15.850> to<00:06:16.060> present<00:06:16.479> you<00:06:16.720> how<00:06:17.200> it<00:06:17.320> works 00:06:29.300 --> 00:06:29.310 align:start position:0% 00:06:29.310 --> 00:06:31.400 align:start position:0% so<00:06:30.030> this<00:06:30.330> is<00:06:30.480> a<00:06:30.510> video<00:06:30.780> but<00:06:31.050> really<00:06:31.380> I 00:06:31.400 --> 00:06:31.410 align:start position:0% so this is a video but really I 00:06:31.410 --> 00:06:34.760 align:start position:0% so this is a video but really I encourage<00:06:32.250> you<00:06:32.490> to<00:06:32.630> to<00:06:33.630> try<00:06:34.050> the<00:06:34.110> tutorial<00:06:34.620> by 00:06:34.760 --> 00:06:34.770 align:start position:0% encourage you to to try the tutorial by 00:06:34.770 --> 00:06:37.400 align:start position:0% encourage you to to try the tutorial by yourself<00:06:35.190> by<00:06:35.790> yourself<00:06:35.820> it's<00:06:36.570> much<00:06:37.080> more<00:06:37.230> fun 00:06:37.400 --> 00:06:37.410 align:start position:0% yourself by yourself it's much more fun 00:06:37.410 --> 00:06:40.100 align:start position:0% yourself by yourself it's much more fun than<00:06:37.470> watching<00:06:38.010> a<00:06:38.250> video<00:06:38.850> so<00:06:39.600> what<00:06:39.750> you<00:06:39.870> see 00:06:40.100 --> 00:06:40.110 align:start position:0% than watching a video so what you see 00:06:40.110 --> 00:06:43.940 align:start position:0% than watching a video so what you see here<00:06:40.139> is<00:06:40.770> actually<00:06:40.950> a<00:06:41.280> screencast<00:06:41.880> of<00:06:42.950> it's 00:06:43.940 --> 00:06:43.950 align:start position:0% here is actually a screencast of it's 00:06:43.950 --> 00:06:47.180 align:start position:0% here is actually a screencast of it's actually<00:06:44.070> a<00:06:44.340> screencap<00:06:44.880> of<00:06:44.910> a<00:06:45.870> webpage<00:06:46.410> and<00:06:46.800> so 00:06:47.180 --> 00:06:47.190 align:start position:0% actually a screencap of a webpage and so 00:06:47.190 --> 00:06:49.580 align:start position:0% actually a screencap of a webpage and so you<00:06:47.250> don't<00:06:47.400> have<00:06:47.520> to<00:06:47.940> install<00:06:48.180> anything<00:06:48.660> to<00:06:49.200> do 00:06:49.580 --> 00:06:49.590 align:start position:0% you don't have to install anything to do 00:06:49.590 --> 00:06:52.040 align:start position:0% you don't have to install anything to do the<00:06:49.710> tutorial<00:06:50.210> you<00:06:51.210> just<00:06:51.450> visit<00:06:51.720> the<00:06:51.870> webpage 00:06:52.040 --> 00:06:52.050 align:start position:0% the tutorial you just visit the webpage 00:06:52.050 --> 00:06:56.000 align:start position:0% the tutorial you just visit the webpage and<00:06:52.620> the<00:06:53.460> tutorial<00:06:53.880> is<00:06:53.940> about<00:06:54.060> six<00:06:54.900> I<00:06:55.260> mean 00:06:56.000 --> 00:06:56.010 align:start position:0% and the tutorial is about six I mean 00:06:56.010 --> 00:06:58.220 align:start position:0% and the tutorial is about six I mean from<00:06:56.220> ten<00:06:56.700> to<00:06:56.970> a<00:06:57.000> half<00:06:57.240> an<00:06:57.419> hour<00:06:57.570> depending<00:06:57.870> on 00:06:58.220 --> 00:06:58.230 align:start position:0% from ten to a half an hour depending on 00:06:58.230 --> 00:07:01.550 align:start position:0% from ten to a half an hour depending on what<00:06:58.470> kind<00:06:58.680> of<00:06:58.889> test<00:06:59.550> net<00:06:59.730> you're<00:06:59.910> using<00:07:00.560> so 00:07:01.550 --> 00:07:01.560 align:start position:0% what kind of test net you're using so 00:07:01.560 --> 00:07:14.690 align:start position:0% what kind of test net you're using so when<00:07:01.740> you<00:07:01.830> use<00:07:02.040> gear<00:07:02.910> so<00:07:10.970> so<00:07:12.560> DSD<00:07:13.560> so<00:07:14.130> first<00:07:14.430> you 00:07:14.690 --> 00:07:14.700 align:start position:0% when you use gear so so DSD so first you 00:07:14.700 --> 00:07:17.080 align:start position:0% when you use gear so so DSD so first you install<00:07:15.060> the<00:07:15.210> SDK<00:07:15.360> that's<00:07:16.320> very<00:07:16.530> similar<00:07:16.860> to 00:07:17.080 --> 00:07:17.090 align:start position:0% install the SDK that's very similar to 00:07:17.090 --> 00:07:19.250 align:start position:0% install the SDK that's very similar to traffic<00:07:18.090> so<00:07:18.270> if<00:07:18.360> you<00:07:18.480> are<00:07:18.540> used<00:07:18.720> to<00:07:18.810> troffer 00:07:19.250 --> 00:07:19.260 align:start position:0% traffic so if you are used to troffer 00:07:19.260 --> 00:07:21.170 align:start position:0% traffic so if you are used to troffer you<00:07:19.680> will<00:07:19.800> find<00:07:20.040> that<00:07:20.190> it's<00:07:20.400> exactly<00:07:20.669> almost 00:07:21.170 --> 00:07:21.180 align:start position:0% you will find that it's exactly almost 00:07:21.180 --> 00:07:22.700 align:start position:0% you will find that it's exactly almost the<00:07:21.479> same 00:07:22.700 --> 00:07:22.710 align:start position:0% the same 00:07:22.710 --> 00:07:25.310 align:start position:0% the same then<00:07:23.340> we<00:07:23.790> are<00:07:23.910> here<00:07:24.240> with<00:07:24.419> this<00:07:24.600> tutorial<00:07:25.169> we 00:07:25.310 --> 00:07:25.320 align:start position:0% then we are here with this tutorial we 00:07:25.320 --> 00:07:27.260 align:start position:0% then we are here with this tutorial we are<00:07:25.350> playing<00:07:25.650> with<00:07:26.010> a<00:07:26.040> toy<00:07:26.490> application<00:07:27.120> of 00:07:27.260 --> 00:07:27.270 align:start position:0% are playing with a toy application of 00:07:27.270 --> 00:07:29.600 align:start position:0% are playing with a toy application of course<00:07:27.479> it's<00:07:27.750> factorial<00:07:28.350> but<00:07:28.950> if<00:07:29.160> you<00:07:29.430> are 00:07:29.600 --> 00:07:29.610 align:start position:0% course it's factorial but if you are 00:07:29.610 --> 00:07:32.240 align:start position:0% course it's factorial but if you are using<00:07:29.850> when<00:07:30.389> storing<00:07:30.840> the<00:07:30.990> SDK<00:07:31.500> on<00:07:31.710> your<00:07:32.130> own 00:07:32.240 --> 00:07:32.250 align:start position:0% using when storing the SDK on your own 00:07:32.250 --> 00:07:34.820 align:start position:0% using when storing the SDK on your own machine<00:07:32.400> you<00:07:33.120> will<00:07:33.270> be<00:07:33.450> able<00:07:33.660> to<00:07:34.080> use<00:07:34.260> any<00:07:34.590> kind 00:07:34.820 --> 00:07:34.830 align:start position:0% machine you will be able to use any kind 00:07:34.830 --> 00:07:38.300 align:start position:0% machine you will be able to use any kind of<00:07:34.919> application<00:07:35.820> so<00:07:36.780> when<00:07:36.990> we<00:07:37.140> start<00:07:37.500> we<00:07:38.010> first 00:07:38.300 --> 00:07:38.310 align:start position:0% of application so when we start we first 00:07:38.310 --> 00:07:40.430 align:start position:0% of application so when we start we first get<00:07:38.490> some<00:07:38.669> ETA<00:07:38.970> -<00:07:39.090> just<00:07:39.600> to<00:07:39.720> be<00:07:39.840> able<00:07:39.930> to<00:07:40.050> deploy 00:07:40.430 --> 00:07:40.440 align:start position:0% get some ETA - just to be able to deploy 00:07:40.440 --> 00:07:43.460 align:start position:0% get some ETA - just to be able to deploy a<00:07:40.530> contract<00:07:41.370> we're<00:07:42.000> using<00:07:42.150> a<00:07:42.600> function<00:07:43.200> which 00:07:43.460 --> 00:07:43.470 align:start position:0% a contract we're using a function which 00:07:43.470 --> 00:07:45.590 align:start position:0% a contract we're using a function which is<00:07:43.620> called<00:07:43.860> I<00:07:43.979> exact<00:07:44.400> deploy<00:07:44.760> so<00:07:45.030> I<00:07:45.240> exact 00:07:45.590 --> 00:07:45.600 align:start position:0% is called I exact deploy so I exact 00:07:45.600 --> 00:07:47.840 align:start position:0% is called I exact deploy so I exact deploy<00:07:45.900> those<00:07:46.140> two<00:07:46.380> things<00:07:46.650> at<00:07:47.010> the<00:07:47.340> one<00:07:47.520> hand 00:07:47.840 --> 00:07:47.850 align:start position:0% deploy those two things at the one hand 00:07:47.850 --> 00:07:50.420 align:start position:0% deploy those two things at the one hand it<00:07:48.030> combines<00:07:48.450> all<00:07:48.660> the<00:07:48.810> solidity<00:07:49.430> smart 00:07:50.420 --> 00:07:50.430 align:start position:0% it combines all the solidity smart 00:07:50.430 --> 00:07:52.219 align:start position:0% it combines all the solidity smart contract<00:07:50.880> we<00:07:51.030> will<00:07:51.150> deploy<00:07:51.419> it<00:07:51.660> on<00:07:51.810> inferior 00:07:52.219 --> 00:07:52.229 align:start position:0% contract we will deploy it on inferior 00:07:52.229 --> 00:07:54.529 align:start position:0% contract we will deploy it on inferior and<00:07:52.500> the<00:07:52.530> second<00:07:53.520> thing<00:07:53.729> that<00:07:53.789> it<00:07:54.090> does<00:07:54.270> is 00:07:54.529 --> 00:07:54.539 align:start position:0% and the second thing that it does is 00:07:54.539 --> 00:07:59.150 align:start position:0% and the second thing that it does is that<00:07:54.960> it<00:07:55.820> it<00:07:56.820> compiles<00:07:57.479> it<00:07:57.630> it<00:07:58.260> pushes<00:07:58.620> your 00:07:59.150 --> 00:07:59.160 align:start position:0% that it it compiles it it pushes your 00:07:59.160 --> 00:08:02.240 align:start position:0% that it it compiles it it pushes your existing<00:07:59.669> application<00:08:00.390> -<00:08:01.110> I<00:08:01.140> exact<00:08:01.800> and<00:08:02.039> what 00:08:02.240 --> 00:08:02.250 align:start position:0% existing application - I exact and what 00:08:02.250 --> 00:08:03.590 align:start position:0% existing application - I exact and what you've<00:08:02.490> just<00:08:02.520> seen<00:08:02.880> here<00:08:03.240> it's<00:08:03.390> the 00:08:03.590 --> 00:08:03.600 align:start position:0% you've just seen here it's the 00:08:03.600 --> 00:08:05.180 align:start position:0% you've just seen here it's the application<00:08:04.169> what<00:08:04.380> it<00:08:04.500> has<00:08:04.620> been<00:08:04.770> deployed 00:08:05.180 --> 00:08:05.190 align:start position:0% application what it has been deployed 00:08:05.190 --> 00:08:06.500 align:start position:0% application what it has been deployed and<00:08:05.550> i<00:08:06.150> exac 00:08:06.500 --> 00:08:06.510 align:start position:0% and i exac 00:08:06.510 --> 00:08:09.260 align:start position:0% and i exac so<00:08:07.020> now<00:08:07.320> what<00:08:07.500> you<00:08:07.620> will<00:08:07.710> see<00:08:07.979> here<00:08:08.010> is<00:08:08.760> that<00:08:08.910> we 00:08:09.260 --> 00:08:09.270 align:start position:0% so now what you will see here is that we 00:08:09.270 --> 00:08:11.690 align:start position:0% so now what you will see here is that we are<00:08:09.360> going<00:08:09.479> to<00:08:09.600> to<00:08:10.500> use<00:08:10.530> the<00:08:10.770> application<00:08:11.070> I 00:08:11.690 --> 00:08:11.700 align:start position:0% are going to to use the application I 00:08:11.700 --> 00:08:14.029 align:start position:0% are going to to use the application I use<00:08:11.880> you<00:08:12.060> user<00:08:12.360> so<00:08:12.900> for<00:08:13.169> doing<00:08:13.260> this<00:08:13.530> we<00:08:13.800> first 00:08:14.029 --> 00:08:14.039 align:start position:0% use you user so for doing this we first 00:08:14.039 --> 00:08:18.260 align:start position:0% use you user so for doing this we first retrieve<00:08:14.850> some<00:08:15.210> RFC<00:08:15.840> tokens<00:08:16.850> we<00:08:17.850> allow<00:08:18.210> the 00:08:18.260 --> 00:08:18.270 align:start position:0% retrieve some RFC tokens we allow the 00:08:18.270 --> 00:08:20.510 align:start position:0% retrieve some RFC tokens we allow the soap<00:08:18.600> the<00:08:19.229> contract<00:08:19.710> will<00:08:19.979> span<00:08:20.370> those 00:08:20.510 --> 00:08:20.520 align:start position:0% soap the contract will span those 00:08:20.520 --> 00:08:23.060 align:start position:0% soap the contract will span those documents<00:08:21.030> and<00:08:21.360> what<00:08:21.810> we're<00:08:22.020> doing<00:08:22.050> now<00:08:22.470> that 00:08:23.060 --> 00:08:23.070 align:start position:0% documents and what we're doing now that 00:08:23.070 --> 00:08:26.420 align:start position:0% documents and what we're doing now that we<00:08:23.220> submit<00:08:23.550> a<00:08:23.669> Java<00:08:24.590> so<00:08:25.590> once<00:08:25.800> you<00:08:25.950> submit<00:08:26.220> a 00:08:26.420 --> 00:08:26.430 align:start position:0% we submit a Java so once you submit a 00:08:26.430 --> 00:08:29.000 align:start position:0% we submit a Java so once you submit a job<00:08:26.669> you<00:08:27.180> can<00:08:27.390> see<00:08:27.630> that<00:08:27.810> I'm<00:08:28.440> going<00:08:28.650> to<00:08:28.710> stop 00:08:29.000 --> 00:08:29.010 align:start position:0% job you can see that I'm going to stop 00:08:29.010 --> 00:08:31.520 align:start position:0% job you can see that I'm going to stop here<00:08:29.250> you<00:08:29.640> can<00:08:29.850> see<00:08:30.120> that<00:08:30.330> so<00:08:30.900> when<00:08:31.169> you<00:08:31.289> submit 00:08:31.520 --> 00:08:31.530 align:start position:0% here you can see that so when you submit 00:08:31.530 --> 00:08:33.500 align:start position:0% here you can see that so when you submit a<00:08:31.710> job<00:08:31.950> the<00:08:32.159> job<00:08:32.370> here<00:08:32.700> is<00:08:32.789> being<00:08:32.969> computed 00:08:33.500 --> 00:08:33.510 align:start position:0% a job the job here is being computed 00:08:33.510 --> 00:08:35.810 align:start position:0% a job the job here is being computed this<00:08:34.050> is<00:08:34.229> why<00:08:34.320> you<00:08:34.380> see<00:08:34.650> pending<00:08:35.099> and<00:08:35.339> pending 00:08:35.810 --> 00:08:35.820 align:start position:0% this is why you see pending and pending 00:08:35.820 --> 00:08:38.149 align:start position:0% this is why you see pending and pending so<00:08:36.360> it<00:08:36.810> has<00:08:36.960> been<00:08:37.110> accelerated<00:08:37.680> but<00:08:37.830> of<00:08:37.950> course 00:08:38.149 --> 00:08:38.159 align:start position:0% so it has been accelerated but of course 00:08:38.159 --> 00:08:39.150 align:start position:0% so it has been accelerated but of course it<00:08:38.310> takes<00:08:38.430> a<00:08:38.640> much<00:08:38.820> more 00:08:39.150 --> 00:08:39.160 align:start position:0% it takes a much more 00:08:39.160 --> 00:08:41.969 align:start position:0% it takes a much more he<00:08:39.490> can<00:08:39.760> take<00:08:39.970> more<00:08:40.120> time<00:08:40.390> and<00:08:40.720> when<00:08:41.500> it's<00:08:41.710> done 00:08:41.969 --> 00:08:41.979 align:start position:0% he can take more time and when it's done 00:08:41.979 --> 00:08:44.250 align:start position:0% he can take more time and when it's done so<00:08:42.550> this<00:08:42.700> is<00:08:42.760> the<00:08:43.090> house<00:08:43.330> of<00:08:43.510> the<00:08:43.630> transaction 00:08:44.250 --> 00:08:44.260 align:start position:0% so this is the house of the transaction 00:08:44.260 --> 00:08:46.890 align:start position:0% so this is the house of the transaction that<00:08:44.500> you<00:08:44.980> got<00:08:45.160> from<00:08:45.370> the<00:08:45.610> smart<00:08:46.060> contract<00:08:46.210> and 00:08:46.890 --> 00:08:46.900 align:start position:0% that you got from the smart contract and 00:08:46.900 --> 00:08:49.290 align:start position:0% that you got from the smart contract and once<00:08:47.350> it's<00:08:47.530> done<00:08:47.770> you<00:08:48.340> can<00:08:48.370> see<00:08:48.580> that<00:08:48.880> you<00:08:49.060> you 00:08:49.290 --> 00:08:49.300 align:start position:0% once it's done you can see that you you 00:08:49.300 --> 00:08:51.450 align:start position:0% once it's done you can see that you you finish<00:08:49.990> the<00:08:50.110> job<00:08:50.140> and<00:08:50.500> this<00:08:50.650> this<00:08:51.160> is<00:08:51.310> the 00:08:51.450 --> 00:08:51.460 align:start position:0% finish the job and this this is the 00:08:51.460 --> 00:08:55.470 align:start position:0% finish the job and this this is the result<00:08:51.640> of<00:08:52.000> the<00:08:52.210> of<00:08:52.600> the<00:08:52.990> computation<00:08:54.420> and<00:08:55.420> you 00:08:55.470 --> 00:08:55.480 align:start position:0% result of the of the computation and you 00:08:55.480 --> 00:08:57.690 align:start position:0% result of the of the computation and you can<00:08:55.840> see<00:08:56.080> on<00:08:56.260> the<00:08:56.590> Explorer<00:08:57.070> so<00:08:57.340> this<00:08:57.490> is<00:08:57.610> an 00:08:57.690 --> 00:08:57.700 align:start position:0% can see on the Explorer so this is an 00:08:57.700 --> 00:09:00.180 align:start position:0% can see on the Explorer so this is an explorer<00:08:58.090> we<00:08:58.300> provide<00:08:58.750> to<00:08:59.290> see<00:08:59.470> what's<00:08:59.950> going 00:09:00.180 --> 00:09:00.190 align:start position:0% explorer we provide to see what's going 00:09:00.190 --> 00:09:02.070 align:start position:0% explorer we provide to see what's going on<00:09:00.310> between<00:09:00.520> our<00:09:00.820> chain<00:09:01.120> and<00:09:01.330> off<00:09:01.510> chain<00:09:01.810> and 00:09:02.070 --> 00:09:02.080 align:start position:0% on between our chain and off chain and 00:09:02.080 --> 00:09:03.270 align:start position:0% on between our chain and off chain and you<00:09:02.320> can<00:09:02.500> see<00:09:02.650> the<00:09:02.740> result<00:09:03.040> of<00:09:03.190> the 00:09:03.270 --> 00:09:03.280 align:start position:0% you can see the result of the 00:09:03.280 --> 00:09:05.340 align:start position:0% you can see the result of the computation<00:09:03.580> in<00:09:04.270> the<00:09:04.480> smart<00:09:04.750> code<00:09:04.870> track<00:09:05.140> or 00:09:05.340 --> 00:09:05.350 align:start position:0% computation in the smart code track or 00:09:05.350 --> 00:09:07.110 align:start position:0% computation in the smart code track or you<00:09:05.440> can<00:09:05.470> retrieve<00:09:06.010> it<00:09:06.100> using<00:09:06.460> our<00:09:06.610> or<00:09:07.060> a 00:09:07.110 --> 00:09:07.120 align:start position:0% you can retrieve it using our or a 00:09:07.120 --> 00:09:17.850 align:start position:0% you can retrieve it using our or a command<00:09:07.780> line<00:09:07.960> tool<00:09:15.660> so<00:09:16.660> what<00:09:17.470> is<00:09:17.650> the 00:09:17.850 --> 00:09:17.860 align:start position:0% command line tool so what is the 00:09:17.860 --> 00:09:20.310 align:start position:0% command line tool so what is the deployment<00:09:18.700> strategy<00:09:19.390> for<00:09:19.630> on<00:09:19.810> the<00:09:19.930> route<00:09:20.110> so 00:09:20.310 --> 00:09:20.320 align:start position:0% deployment strategy for on the route so 00:09:20.320 --> 00:09:23.880 align:start position:0% deployment strategy for on the route so what<00:09:20.500> you<00:09:20.650> have<00:09:20.950> seen<00:09:22.080> now<00:09:23.080> is<00:09:23.380> that<00:09:23.650> it's 00:09:23.880 --> 00:09:23.890 align:start position:0% what you have seen now is that it's 00:09:23.890 --> 00:09:26.970 align:start position:0% what you have seen now is that it's running<00:09:24.160> now<00:09:24.340> on<00:09:24.760> Rob<00:09:25.300> stone<00:09:25.540> and<00:09:26.290> an<00:09:26.500> order 00:09:26.970 --> 00:09:26.980 align:start position:0% running now on Rob stone and an order 00:09:26.980 --> 00:09:31.290 align:start position:0% running now on Rob stone and an order test<00:09:27.430> net<00:09:27.640> so<00:09:28.450> we<00:09:28.780> are<00:09:29.560> going<00:09:29.740> to<00:09:29.890> deploy<00:09:30.160> it<00:09:30.300> in 00:09:31.290 --> 00:09:31.300 align:start position:0% test net so we are going to deploy it in 00:09:31.300 --> 00:09:33.720 align:start position:0% test net so we are going to deploy it in the<00:09:31.450> coming<00:09:31.780> weeks<00:09:32.470> so<00:09:32.740> first<00:09:33.220> we<00:09:33.310> deployed 00:09:33.720 --> 00:09:33.730 align:start position:0% the coming weeks so first we deployed 00:09:33.730 --> 00:09:36.900 align:start position:0% the coming weeks so first we deployed the<00:09:33.910> SDK<00:09:34.450> with<00:09:34.690> on<00:09:35.010> application<00:09:36.010> the<00:09:36.520> next<00:09:36.760> two 00:09:36.900 --> 00:09:36.910 align:start position:0% the SDK with on application the next two 00:09:36.910 --> 00:09:38.970 align:start position:0% the SDK with on application the next two weeks<00:09:37.090> we<00:09:37.660> are<00:09:37.690> going<00:09:37.780> to<00:09:38.140> create<00:09:38.410> an<00:09:38.740> app 00:09:38.970 --> 00:09:38.980 align:start position:0% weeks we are going to create an app 00:09:38.980 --> 00:09:40.790 align:start position:0% weeks we are going to create an app store<00:09:39.100> so<00:09:39.850> that<00:09:40.000> it<00:09:40.150> makes<00:09:40.390> the<00:09:40.540> application 00:09:40.790 --> 00:09:40.800 align:start position:0% store so that it makes the application 00:09:40.800 --> 00:09:43.170 align:start position:0% store so that it makes the application for<00:09:41.800> the<00:09:41.920> end<00:09:42.040> user<00:09:42.370> much<00:09:42.640> more<00:09:42.850> user-friendly 00:09:43.170 --> 00:09:43.180 align:start position:0% for the end user much more user-friendly 00:09:43.180 --> 00:09:44.850 align:start position:0% for the end user much more user-friendly because<00:09:43.900> at<00:09:44.020> the<00:09:44.140> moment<00:09:44.170> they<00:09:44.590> have<00:09:44.620> to 00:09:44.850 --> 00:09:44.860 align:start position:0% because at the moment they have to 00:09:44.860 --> 00:09:47.880 align:start position:0% because at the moment they have to interact<00:09:45.100> with<00:09:45.310> the<00:09:45.520> spa<00:09:45.940> contract<00:09:46.420> and<00:09:46.890> later 00:09:47.880 --> 00:09:47.890 align:start position:0% interact with the spa contract and later 00:09:47.890 --> 00:09:49.710 align:start position:0% interact with the spa contract and later on<00:09:48.190> by<00:09:48.460> the<00:09:48.520> end<00:09:48.730> of<00:09:48.880> the<00:09:49.030> year<00:09:49.210> we<00:09:49.420> are<00:09:49.480> going 00:09:49.710 --> 00:09:49.720 align:start position:0% on by the end of the year we are going 00:09:49.720 --> 00:09:51.990 align:start position:0% on by the end of the year we are going to<00:09:49.900> deploy<00:09:50.230> this<00:09:50.770> app<00:09:50.980> store<00:09:51.250> on<00:09:51.430> main<00:09:51.730> net 00:09:51.990 --> 00:09:52.000 align:start position:0% to deploy this app store on main net 00:09:52.000 --> 00:09:54.150 align:start position:0% to deploy this app store on main net which<00:09:52.450> means<00:09:52.750> that<00:09:52.960> developers<00:09:53.500> using<00:09:54.010> the<00:09:54.130> I 00:09:54.150 --> 00:09:54.160 align:start position:0% which means that developers using the I 00:09:54.160 --> 00:09:59.280 align:start position:0% which means that developers using the I exact<00:09:54.700> will<00:09:55.150> actually<00:09:55.660> be<00:09:56.460> able<00:09:57.460> to<00:09:58.030> earn<00:09:58.290> IC 00:09:59.280 --> 00:09:59.290 align:start position:0% exact will actually be able to earn IC 00:09:59.290 --> 00:10:04.580 align:start position:0% exact will actually be able to earn IC tokens<00:10:00.630> so<00:10:01.630> what<00:10:02.440> happens<00:10:02.980> under<00:10:03.670> the<00:10:03.970> hood 00:10:04.580 --> 00:10:04.590 align:start position:0% tokens so what happens under the hood 00:10:04.590 --> 00:10:07.410 align:start position:0% tokens so what happens under the hood what<00:10:05.590> we<00:10:05.770> do<00:10:05.950> is<00:10:06.130> that<00:10:06.310> those<00:10:07.000> computations 00:10:07.410 --> 00:10:07.420 align:start position:0% what we do is that those computations 00:10:07.420 --> 00:10:10.410 align:start position:0% what we do is that those computations are<00:10:08.110> actually<00:10:08.680> executed<00:10:09.670> on<00:10:09.790> distributed 00:10:10.410 --> 00:10:10.420 align:start position:0% are actually executed on distributed 00:10:10.420 --> 00:10:13.320 align:start position:0% are actually executed on distributed infrastructure<00:10:10.990> so<00:10:11.740> we<00:10:11.770> called<00:10:12.340> worker<00:10:12.940> the 00:10:13.320 --> 00:10:13.330 align:start position:0% infrastructure so we called worker the 00:10:13.330 --> 00:10:15.840 align:start position:0% infrastructure so we called worker the machines<00:10:13.780> that<00:10:14.040> joined<00:10:15.040> us<00:10:15.190> in<00:10:15.310> hospital 00:10:15.840 --> 00:10:15.850 align:start position:0% machines that joined us in hospital 00:10:15.850 --> 00:10:18.000 align:start position:0% machines that joined us in hospital jointly<00:10:16.180> this<00:10:16.390> network<00:10:16.870> and<00:10:17.080> that<00:10:17.590> provider 00:10:18.000 --> 00:10:18.010 align:start position:0% jointly this network and that provider 00:10:18.010 --> 00:10:20.400 align:start position:0% jointly this network and that provider our<00:10:18.430> CPU<00:10:18.760> time<00:10:19.060> to<00:10:19.270> execute<00:10:19.570> the<00:10:20.320> application 00:10:20.400 --> 00:10:20.410 align:start position:0% our CPU time to execute the application 00:10:20.410 --> 00:10:23.400 align:start position:0% our CPU time to execute the application and<00:10:21.190> so<00:10:21.730> we<00:10:21.880> organize<00:10:22.390> those<00:10:22.690> workers<00:10:22.990> in 00:10:23.400 --> 00:10:23.410 align:start position:0% and so we organize those workers in 00:10:23.410 --> 00:10:25.320 align:start position:0% and so we organize those workers in worker<00:10:23.740> pool<00:10:24.130> a<00:10:24.340> little<00:10:24.640> bit<00:10:24.940> like<00:10:25.090> you<00:10:25.210> have 00:10:25.320 --> 00:10:25.330 align:start position:0% worker pool a little bit like you have 00:10:25.330 --> 00:10:27.150 align:start position:0% worker pool a little bit like you have my<00:10:25.540> nerves<00:10:25.780> and<00:10:26.050> my<00:10:26.230> nurple<00:10:26.560> it's<00:10:26.710> exactly<00:10:27.010> the 00:10:27.150 --> 00:10:27.160 align:start position:0% my nerves and my nurple it's exactly the 00:10:27.160 --> 00:10:29.220 align:start position:0% my nerves and my nurple it's exactly the same<00:10:27.340> way<00:10:27.490> the<00:10:27.670> same<00:10:27.820> idea<00:10:28.180> but<00:10:28.390> here<00:10:28.930> any 00:10:29.220 --> 00:10:29.230 align:start position:0% same way the same idea but here any 00:10:29.230 --> 00:10:31.380 align:start position:0% same way the same idea but here any worker<00:10:29.950> can<00:10:30.310> execute<00:10:30.580> any<00:10:30.820> arbitrary 00:10:31.380 --> 00:10:31.390 align:start position:0% worker can execute any arbitrary 00:10:31.390 --> 00:10:33.900 align:start position:0% worker can execute any arbitrary application<00:10:31.720> are<00:10:32.410> not<00:10:32.500> just<00:10:32.710> mining<00:10:33.100> and<00:10:33.490> what 00:10:33.900 --> 00:10:33.910 align:start position:0% application are not just mining and what 00:10:33.910 --> 00:10:36.180 align:start position:0% application are not just mining and what we<00:10:34.090> do<00:10:34.210> is<00:10:34.330> now<00:10:34.540> that<00:10:35.050> we<00:10:35.260> have<00:10:35.440> an<00:10:35.530> Oracle<00:10:35.770> that 00:10:36.180 --> 00:10:36.190 align:start position:0% we do is now that we have an Oracle that 00:10:36.190 --> 00:10:37.950 align:start position:0% we do is now that we have an Oracle that looks<00:10:36.880> at<00:10:37.120> what's<00:10:37.390> happening<00:10:37.720> at<00:10:37.870> the 00:10:37.950 --> 00:10:37.960 align:start position:0% looks at what's happening at the 00:10:37.960 --> 00:10:39.480 align:start position:0% looks at what's happening at the blockchain<00:10:38.170> on<00:10:38.620> the<00:10:38.800> smart<00:10:39.040> your<00:10:39.250> smart 00:10:39.480 --> 00:10:39.490 align:start position:0% blockchain on the smart your smart 00:10:39.490 --> 00:10:41.790 align:start position:0% blockchain on the smart your smart contract<00:10:39.970> and<00:10:40.150> each<00:10:40.570> time<00:10:40.870> there<00:10:41.080> were<00:10:41.200> the 00:10:41.790 --> 00:10:41.800 align:start position:0% contract and each time there were the 00:10:41.800 --> 00:10:43.950 align:start position:0% contract and each time there were the Oracle<00:10:42.310> detected<00:10:43.090> as<00:10:43.240> at<00:10:43.360> reduction<00:10:43.840> is 00:10:43.950 --> 00:10:43.960 align:start position:0% Oracle detected as at reduction is 00:10:43.960 --> 00:10:45.180 align:start position:0% Oracle detected as at reduction is market<00:10:44.320> right<00:10:44.500> it's<00:10:44.710> exactly<00:10:44.800> the 00:10:45.180 --> 00:10:45.190 align:start position:0% market right it's exactly the 00:10:45.190 --> 00:10:49.790 align:start position:0% market right it's exactly the corresponding<00:10:45.670> application<00:10:45.790> on<00:10:46.420> the<00:10:46.900> workers 00:10:49.790 --> 00:10:49.800 align:start position:0% 00:10:49.800 --> 00:10:54.110 align:start position:0% so<00:10:49.860> for<00:10:50.760> version<00:10:51.029> 2<00:10:52.250> it<00:10:53.250> means<00:10:53.580> that<00:10:53.850> any 00:10:54.110 --> 00:10:54.120 align:start position:0% so for version 2 it means that any 00:10:54.120 --> 00:10:56.300 align:start position:0% so for version 2 it means that any computing<00:10:54.870> resources<00:10:55.440> can<00:10:55.769> join<00:10:55.980> the<00:10:56.130> network 00:10:56.300 --> 00:10:56.310 align:start position:0% computing resources can join the network 00:10:56.310 --> 00:10:58.850 align:start position:0% computing resources can join the network and<00:10:56.730> also<00:10:57.060> of<00:10:57.209> course<00:10:57.480> it<00:10:57.630> causes<00:10:57.990> a<00:10:58.019> lot<00:10:58.200> of<00:10:58.230> of 00:10:58.850 --> 00:10:58.860 align:start position:0% and also of course it causes a lot of of 00:10:58.860 --> 00:11:01.730 align:start position:0% and also of course it causes a lot of of issues<00:10:59.490> in<00:10:59.730> particular<00:10:59.970> with<00:11:00.529> respect<00:11:01.529> to<00:11:01.680> a 00:11:01.730 --> 00:11:01.740 align:start position:0% issues in particular with respect to a 00:11:01.740 --> 00:11:05.180 align:start position:0% issues in particular with respect to a security<00:11:02.399> and<00:11:02.910> so<00:11:03.120> since<00:11:03.390> this<00:11:04.110> September<00:11:05.010> we 00:11:05.180 --> 00:11:05.190 align:start position:0% security and so since this September we 00:11:05.190 --> 00:11:06.590 align:start position:0% security and so since this September we have<00:11:05.339> launched<00:11:05.610> an<00:11:05.880> official<00:11:06.089> reserves 00:11:06.590 --> 00:11:06.600 align:start position:0% have launched an official reserves 00:11:06.600 --> 00:11:09.319 align:start position:0% have launched an official reserves program<00:11:07.339> that<00:11:08.339> has<00:11:08.490> started<00:11:08.940> very<00:11:09.149> well 00:11:09.319 --> 00:11:09.329 align:start position:0% program that has started very well 00:11:09.329 --> 00:11:11.930 align:start position:0% program that has started very well actually<00:11:09.980> so<00:11:10.980> we're<00:11:11.130> working<00:11:11.220> on<00:11:11.579> two<00:11:11.760> things 00:11:11.930 --> 00:11:11.940 align:start position:0% actually so we're working on two things 00:11:11.940 --> 00:11:14.840 align:start position:0% actually so we're working on two things one<00:11:12.750> is<00:11:13.019> proof<00:11:13.410> of<00:11:13.529> contribution<00:11:14.250> which<00:11:14.820> is 00:11:14.840 --> 00:11:14.850 align:start position:0% one is proof of contribution which is 00:11:14.850 --> 00:11:17.240 align:start position:0% one is proof of contribution which is basically<00:11:15.390> a<00:11:15.510> conscious<00:11:16.019> protocol<00:11:16.560> to<00:11:16.769> verify 00:11:17.240 --> 00:11:17.250 align:start position:0% basically a conscious protocol to verify 00:11:17.250 --> 00:11:19.400 align:start position:0% basically a conscious protocol to verify that<00:11:17.459> the<00:11:17.579> execution<00:11:17.850> that<00:11:18.660> went<00:11:18.899> off<00:11:19.079> Shane 00:11:19.400 --> 00:11:19.410 align:start position:0% that the execution that went off Shane 00:11:19.410 --> 00:11:21.740 align:start position:0% that the execution that went off Shane everybody<00:11:20.220> agrees<00:11:20.670> that<00:11:20.700> the<00:11:20.940> computation<00:11:21.510> is 00:11:21.740 --> 00:11:21.750 align:start position:0% everybody agrees that the computation is 00:11:21.750 --> 00:11:23.900 align:start position:0% everybody agrees that the computation is OK<00:11:22.110> before<00:11:22.829> proceeding<00:11:23.100> to<00:11:23.279> the<00:11:23.459> payments 00:11:23.900 --> 00:11:23.910 align:start position:0% OK before proceeding to the payments 00:11:23.910 --> 00:11:26.410 align:start position:0% OK before proceeding to the payments that's<00:11:24.630> one<00:11:24.870> and<00:11:25.140> the<00:11:25.290> second<00:11:25.709> is<00:11:25.920> some 00:11:26.410 --> 00:11:26.420 align:start position:0% that's one and the second is some 00:11:26.420 --> 00:11:29.210 align:start position:0% that's one and the second is some security<00:11:27.470> reserves<00:11:28.470> that<00:11:28.589> we<00:11:28.740> are<00:11:28.829> doing<00:11:28.920> to 00:11:29.210 --> 00:11:29.220 align:start position:0% security reserves that we are doing to 00:11:29.220 --> 00:11:30.680 align:start position:0% security reserves that we are doing to protect<00:11:29.579> both<00:11:29.730> the<00:11:29.910> application<00:11:30.240> at<00:11:30.570> the 00:11:30.680 --> 00:11:30.690 align:start position:0% protect both the application at the 00:11:30.690 --> 00:11:32.810 align:start position:0% protect both the application at the remote<00:11:30.959> machine<00:11:31.130> so<00:11:32.130> actually<00:11:32.459> proof<00:11:32.670> of 00:11:32.810 --> 00:11:32.820 align:start position:0% remote machine so actually proof of 00:11:32.820 --> 00:11:35.650 align:start position:0% remote machine so actually proof of contribution<00:11:33.450> is<00:11:33.630> done<00:11:33.839> by<00:11:34.079> a<00:11:34.110> PhD<00:11:34.740> student 00:11:35.650 --> 00:11:35.660 align:start position:0% contribution is done by a PhD student 00:11:35.660 --> 00:11:38.810 align:start position:0% contribution is done by a PhD student Adria<00:11:36.660> who<00:11:37.560> were<00:11:37.769> with<00:11:38.070> the<00:11:38.279> student<00:11:38.640> at 00:11:38.810 --> 00:11:38.820 align:start position:0% Adria who were with the student at 00:11:38.820 --> 00:11:43.810 align:start position:0% Adria who were with the student at economic<00:11:39.510> volume<00:11:40.880> for<00:11:41.880> more<00:11:42.209> long-term 00:11:43.810 --> 00:11:43.820 align:start position:0% economic volume for more long-term 00:11:43.820 --> 00:11:47.120 align:start position:0% economic volume for more long-term perspective<00:11:44.820> we<00:11:45.810> think<00:11:46.110> that<00:11:46.260> we<00:11:46.470> are<00:11:46.500> really 00:11:47.120 --> 00:11:47.130 align:start position:0% perspective we think that we are really 00:11:47.130 --> 00:11:50.240 align:start position:0% perspective we think that we are really lacking<00:11:47.519> some<00:11:48.209> good<00:11:48.450> experimental<00:11:49.230> tools<00:11:49.560> to 00:11:50.240 --> 00:11:50.250 align:start position:0% lacking some good experimental tools to 00:11:50.250 --> 00:11:51.740 align:start position:0% lacking some good experimental tools to understand<00:11:50.820> the<00:11:50.940> performance<00:11:51.120> of<00:11:51.630> those 00:11:51.740 --> 00:11:51.750 align:start position:0% understand the performance of those 00:11:51.750 --> 00:11:54.230 align:start position:0% understand the performance of those blockchain<00:11:52.380> based<00:11:52.589> a<00:11:52.709> distributed<00:11:53.220> system<00:11:53.399> so 00:11:54.230 --> 00:11:54.240 align:start position:0% blockchain based a distributed system so 00:11:54.240 --> 00:11:56.540 align:start position:0% blockchain based a distributed system so we<00:11:54.390> are<00:11:54.480> starting<00:11:54.990> PhD<00:11:55.950> thesis<00:11:56.339> in 00:11:56.540 --> 00:11:56.550 align:start position:0% we are starting PhD thesis in 00:11:56.550 --> 00:11:59.300 align:start position:0% we are starting PhD thesis in collaboration<00:11:57.270> with<00:11:57.300> a<00:11:57.959> lab<00:11:58.440> in<00:11:58.649> France<00:11:58.829> which 00:11:59.300 --> 00:11:59.310 align:start position:0% collaboration with a lab in France which 00:11:59.310 --> 00:12:02.030 align:start position:0% collaboration with a lab in France which is<00:11:59.490> called<00:11:59.760> a<00:11:59.910> lawyer<00:12:00.180> and<00:12:00.600> those<00:12:01.440> people<00:12:01.649> are 00:12:02.030 --> 00:12:02.040 align:start position:0% is called a lawyer and those people are 00:12:02.040 --> 00:12:05.480 align:start position:0% is called a lawyer and those people are really<00:12:02.220> expert<00:12:02.760> in<00:12:03.060> emulation<00:12:03.570> of<00:12:04.279> very<00:12:05.279> large 00:12:05.480 --> 00:12:05.490 align:start position:0% really expert in emulation of very large 00:12:05.490 --> 00:12:08.240 align:start position:0% really expert in emulation of very large parallel<00:12:05.970> dispute<00:12:06.570> very<00:12:07.290> large<00:12:07.470> distributed 00:12:08.240 --> 00:12:08.250 align:start position:0% parallel dispute very large distributed 00:12:08.250 --> 00:12:10.579 align:start position:0% parallel dispute very large distributed system<00:12:08.579> sorry<00:12:08.820> so<00:12:09.480> why<00:12:09.899> do<00:12:09.959> you<00:12:10.110> want<00:12:10.320> to<00:12:10.470> do 00:12:10.579 --> 00:12:10.589 align:start position:0% system sorry so why do you want to do 00:12:10.589 --> 00:12:12.560 align:start position:0% system sorry so why do you want to do emulation<00:12:11.250> because<00:12:11.610> it<00:12:11.760> allows<00:12:12.029> you<00:12:12.209> to<00:12:12.420> do 00:12:12.560 --> 00:12:12.570 align:start position:0% emulation because it allows you to do 00:12:12.570 --> 00:12:14.810 align:start position:0% emulation because it allows you to do experiments<00:12:13.260> but<00:12:14.190> with<00:12:14.430> an<00:12:14.520> existing 00:12:14.810 --> 00:12:14.820 align:start position:0% experiments but with an existing 00:12:14.820 --> 00:12:17.480 align:start position:0% experiments but with an existing software<00:12:15.329> stack<00:12:15.750> so<00:12:16.410> it's<00:12:16.589> much<00:12:16.860> closer<00:12:17.190> to 00:12:17.480 --> 00:12:17.490 align:start position:0% software stack so it's much closer to 00:12:17.490 --> 00:12:19.579 align:start position:0% software stack so it's much closer to the<00:12:17.610> reality<00:12:17.760> than<00:12:18.360> just<00:12:18.570> doing<00:12:18.959> simulation 00:12:19.579 --> 00:12:19.589 align:start position:0% the reality than just doing simulation 00:12:19.589 --> 00:12:22.040 align:start position:0% the reality than just doing simulation so<00:12:20.040> it's<00:12:20.160> not<00:12:20.339> only<00:12:20.490> for<00:12:20.700> us<00:12:20.760> I<00:12:21.029> think<00:12:21.060> it<00:12:21.870> will 00:12:22.040 --> 00:12:22.050 align:start position:0% so it's not only for us I think it will 00:12:22.050 --> 00:12:24.310 align:start position:0% so it's not only for us I think it will be<00:12:22.230> very<00:12:22.500> interesting<00:12:22.980> also<00:12:23.160> for<00:12:23.310> the<00:12:23.610> film 00:12:24.310 --> 00:12:24.320 align:start position:0% be very interesting also for the film 00:12:24.320 --> 00:12:26.750 align:start position:0% be very interesting also for the film community<00:12:25.320> to<00:12:25.470> have<00:12:25.589> such<00:12:25.890> such<00:12:26.459> tools 00:12:26.750 --> 00:12:26.760 align:start position:0% community to have such such tools 00:12:26.760 --> 00:12:28.519 align:start position:0% community to have such such tools basically<00:12:27.360> you<00:12:27.750> can<00:12:27.930> test<00:12:28.170> your<00:12:28.320> software 00:12:28.519 --> 00:12:28.529 align:start position:0% basically you can test your software 00:12:28.529 --> 00:12:31.370 align:start position:0% basically you can test your software very<00:12:29.070> rapidly<00:12:29.459> on<00:12:29.970> tens<00:12:30.300> of<00:12:30.450> thousand<00:12:30.870> virtual 00:12:31.370 --> 00:12:31.380 align:start position:0% very rapidly on tens of thousand virtual 00:12:31.380 --> 00:12:35.780 align:start position:0% very rapidly on tens of thousand virtual nodes<00:12:32.839> so<00:12:33.839> some<00:12:34.410> words<00:12:34.589> about<00:12:34.740> proof<00:12:35.640> of 00:12:35.780 --> 00:12:35.790 align:start position:0% nodes so some words about proof of 00:12:35.790 --> 00:12:38.780 align:start position:0% nodes so some words about proof of contribution<00:12:36.480> so<00:12:36.690> we<00:12:36.779> started<00:12:37.170> this<00:12:37.790> in 00:12:38.780 --> 00:12:38.790 align:start position:0% contribution so we started this in 00:12:38.790 --> 00:12:41.600 align:start position:0% contribution so we started this in September<00:12:39.329> about<00:12:39.620> we<00:12:40.620> now<00:12:40.770> have<00:12:41.040> no<00:12:41.430> real 00:12:41.600 --> 00:12:41.610 align:start position:0% September about we now have no real 00:12:41.610 --> 00:12:43.939 align:start position:0% September about we now have no real solutions<00:12:42.209> it's<00:12:42.839> based<00:12:43.199> basically<00:12:43.470> on<00:12:43.770> a 00:12:43.939 --> 00:12:43.949 align:start position:0% solutions it's based basically on a 00:12:43.949 --> 00:12:46.850 align:start position:0% solutions it's based basically on a stacking<00:12:44.520> and<00:12:44.670> reputation<00:12:45.390> so<00:12:46.079> how<00:12:46.350> do<00:12:46.410> I<00:12:46.529> come 00:12:46.850 --> 00:12:46.860 align:start position:0% stacking and reputation so how do I come 00:12:46.860 --> 00:12:48.650 align:start position:0% stacking and reputation so how do I come up<00:12:46.949> with<00:12:47.130> a<00:12:47.220> very<00:12:47.399> interesting<00:12:47.579> protocol<00:12:48.390> it's 00:12:48.650 --> 00:12:48.660 align:start position:0% up with a very interesting protocol it's 00:12:48.660 --> 00:12:50.689 align:start position:0% up with a very interesting protocol it's very<00:12:48.839> simple<00:12:49.140> basically<00:12:50.010> the<00:12:50.220> idea<00:12:50.550> is<00:12:50.670> that 00:12:50.689 --> 00:12:50.699 align:start position:0% very simple basically the idea is that 00:12:50.699 --> 00:12:53.870 align:start position:0% very simple basically the idea is that for<00:12:50.910> each<00:12:51.449> execution<00:12:52.230> you<00:12:52.769> submit<00:12:53.220> you 00:12:53.870 --> 00:12:53.880 align:start position:0% for each execution you submit you 00:12:53.880 --> 00:12:55.759 align:start position:0% for each execution you submit you associate<00:12:54.510> this<00:12:54.630> execution<00:12:55.380> with<00:12:55.620> a 00:12:55.759 --> 00:12:55.769 align:start position:0% associate this execution with a 00:12:55.769 --> 00:12:58.130 align:start position:0% associate this execution with a confidence<00:12:56.279> or<00:12:56.519> threshold<00:12:57.029> and<00:12:57.149> so<00:12:57.720> workers 00:12:58.130 --> 00:12:58.140 align:start position:0% confidence or threshold and so workers 00:12:58.140 --> 00:12:59.900 align:start position:0% confidence or threshold and so workers they<00:12:58.410> have<00:12:58.620> both<00:12:58.860> a<00:12:59.010> reputation<00:12:59.310> and 00:12:59.900 --> 00:12:59.910 align:start position:0% they have both a reputation and 00:12:59.910 --> 00:13:01.970 align:start position:0% they have both a reputation and reputation<00:13:00.209> is<00:13:00.720> gained<00:13:00.959> according<00:13:01.709> to<00:13:01.829> their 00:13:01.970 --> 00:13:01.980 align:start position:0% reputation is gained according to their 00:13:01.980 --> 00:13:03.109 align:start position:0% reputation is gained according to their past 00:13:03.109 --> 00:13:03.119 align:start position:0% past 00:13:03.119 --> 00:13:07.099 align:start position:0% past work<00:13:03.539> so<00:13:03.869> the<00:13:04.109> task<00:13:04.769> succeeded<00:13:05.279> or<00:13:05.399> not<00:13:06.109> and 00:13:07.099 --> 00:13:07.109 align:start position:0% work so the task succeeded or not and 00:13:07.109 --> 00:13:09.259 align:start position:0% work so the task succeeded or not and they<00:13:07.289> also<00:13:07.469> have<00:13:07.799> to<00:13:07.949> stick<00:13:08.159> some<00:13:08.369> money<00:13:08.579> to 00:13:09.259 --> 00:13:09.269 align:start position:0% they also have to stick some money to 00:13:09.269 --> 00:13:11.779 align:start position:0% they also have to stick some money to stack<00:13:09.509> some<00:13:09.689> token<00:13:10.109> and<00:13:10.949> so<00:13:11.249> what<00:13:11.399> we<00:13:11.549> do<00:13:11.699> is 00:13:11.779 --> 00:13:11.789 align:start position:0% stack some token and so what we do is 00:13:11.789 --> 00:13:13.849 align:start position:0% stack some token and so what we do is that<00:13:11.819> each<00:13:12.179> time<00:13:12.209> we<00:13:12.419> receive<00:13:12.899> the<00:13:13.289> sum 00:13:13.849 --> 00:13:13.859 align:start position:0% that each time we receive the sum 00:13:13.859 --> 00:13:15.919 align:start position:0% that each time we receive the sum results<00:13:14.369> we<00:13:14.819> compare<00:13:15.179> the<00:13:15.299> results<00:13:15.749> and<00:13:15.839> we 00:13:15.919 --> 00:13:15.929 align:start position:0% results we compare the results and we 00:13:15.929 --> 00:13:18.709 align:start position:0% results we compare the results and we compute<00:13:16.619> a<00:13:17.159> new<00:13:17.579> confidence<00:13:17.909> threshold<00:13:18.539> and 00:13:18.709 --> 00:13:18.719 align:start position:0% compute a new confidence threshold and 00:13:18.719 --> 00:13:20.239 align:start position:0% compute a new confidence threshold and we<00:13:18.809> can<00:13:19.019> pass<00:13:19.229> this<00:13:19.379> to<00:13:19.559> a<00:13:19.619> short<00:13:19.889> then<00:13:20.039> the 00:13:20.239 --> 00:13:20.249 align:start position:0% we can pass this to a short then the 00:13:20.249 --> 00:13:22.489 align:start position:0% we can pass this to a short then the result<00:13:20.759> is<00:13:20.819> accepted<00:13:21.329> by<00:13:21.449> the<00:13:21.509> submitter<00:13:21.899> and 00:13:22.489 --> 00:13:22.499 align:start position:0% result is accepted by the submitter and 00:13:22.499 --> 00:13:25.459 align:start position:0% result is accepted by the submitter and so<00:13:23.009> task<00:13:23.279> it<00:13:23.489> duplicated<00:13:24.269> or<00:13:24.449> replicating<00:13:25.139> as 00:13:25.459 --> 00:13:25.469 align:start position:0% so task it duplicated or replicating as 00:13:25.469 --> 00:13:27.469 align:start position:0% so task it duplicated or replicating as long<00:13:25.739> as<00:13:25.889> the<00:13:26.009> confidence<00:13:26.549> threshold<00:13:27.179> is<00:13:27.299> not 00:13:27.469 --> 00:13:27.479 align:start position:0% long as the confidence threshold is not 00:13:27.479 --> 00:13:30.229 align:start position:0% long as the confidence threshold is not met<00:13:27.689> and<00:13:28.079> so<00:13:28.679> at<00:13:29.069> the<00:13:29.309> end<00:13:29.339> what<00:13:29.669> you<00:13:29.699> have<00:13:29.999> is 00:13:30.229 --> 00:13:30.239 align:start position:0% met and so at the end what you have is 00:13:30.239 --> 00:13:33.229 align:start position:0% met and so at the end what you have is workers<00:13:30.989> who<00:13:31.379> behave<00:13:32.159> correctly<00:13:32.399> in<00:13:33.029> this 00:13:33.229 --> 00:13:33.239 align:start position:0% workers who behave correctly in this 00:13:33.239 --> 00:13:35.239 align:start position:0% workers who behave correctly in this case<00:13:33.449> they<00:13:33.569> receive<00:13:33.899> the<00:13:34.049> payment<00:13:34.469> and<00:13:34.589> some 00:13:35.239 --> 00:13:35.249 align:start position:0% case they receive the payment and some 00:13:35.249 --> 00:13:37.309 align:start position:0% case they receive the payment and some we<00:13:35.369> did<00:13:35.579> wrong<00:13:35.849> because<00:13:36.209> maybe<00:13:36.599> they<00:13:36.839> try<00:13:37.259> to 00:13:37.309 --> 00:13:37.319 align:start position:0% we did wrong because maybe they try to 00:13:37.319 --> 00:13:39.259 align:start position:0% we did wrong because maybe they try to steal<00:13:37.919> some<00:13:37.949> money<00:13:38.279> in<00:13:38.759> this<00:13:38.939> case<00:13:39.119> we 00:13:39.259 --> 00:13:39.269 align:start position:0% steal some money in this case we 00:13:39.269 --> 00:13:41.599 align:start position:0% steal some money in this case we punished<00:13:39.599> we<00:13:40.139> punish<00:13:40.739> them<00:13:40.949> we<00:13:41.189> take<00:13:41.399> that 00:13:41.599 --> 00:13:41.609 align:start position:0% punished we punish them we take that 00:13:41.609 --> 00:13:42.949 align:start position:0% punished we punish them we take that stack<00:13:41.879> and<00:13:41.909> we<00:13:42.179> distribute<00:13:42.599> the<00:13:42.719> stake 00:13:42.949 --> 00:13:42.959 align:start position:0% stack and we distribute the stake 00:13:42.959 --> 00:13:46.309 align:start position:0% stack and we distribute the stake amongst<00:13:43.679> the<00:13:43.799> workers<00:13:44.249> we<00:13:44.639> did<00:13:44.849> correctly<00:13:45.479> so 00:13:46.309 --> 00:13:46.319 align:start position:0% amongst the workers we did correctly so 00:13:46.319 --> 00:13:48.559 align:start position:0% amongst the workers we did correctly so the<00:13:47.309> good<00:13:47.489> thing<00:13:47.669> with<00:13:47.819> this<00:13:47.939> protocol<00:13:48.299> is 00:13:48.559 --> 00:13:48.569 align:start position:0% the good thing with this protocol is 00:13:48.569 --> 00:13:50.749 align:start position:0% the good thing with this protocol is that<00:13:48.719> it's<00:13:48.869> actually<00:13:48.989> very<00:13:49.289> simple<00:13:49.709> so<00:13:50.519> it's 00:13:50.749 --> 00:13:50.759 align:start position:0% that it's actually very simple so it's 00:13:50.759 --> 00:13:53.029 align:start position:0% that it's actually very simple so it's simple<00:13:51.059> to<00:13:51.209> implement<00:13:51.479> and<00:13:51.959> then<00:13:52.379> to<00:13:52.529> verify 00:13:53.029 --> 00:13:53.039 align:start position:0% simple to implement and then to verify 00:13:53.039 --> 00:13:55.369 align:start position:0% simple to implement and then to verify also<00:13:53.249> and<00:13:53.669> it<00:13:54.239> would<00:13:54.419> be<00:13:54.539> also<00:13:54.779> simple<00:13:55.169> to 00:13:55.369 --> 00:13:55.379 align:start position:0% also and it would be also simple to 00:13:55.379 --> 00:13:58.789 align:start position:0% also and it would be also simple to optimize<00:13:56.479> so<00:13:57.479> at<00:13:57.599> the<00:13:57.689> moment<00:13:57.839> Audrina<00:13:58.739> is 00:13:58.789 --> 00:13:58.799 align:start position:0% optimize so at the moment Audrina is 00:13:58.799 --> 00:14:01.339 align:start position:0% optimize so at the moment Audrina is doing<00:13:59.009> the<00:13:59.099> performance<00:13:59.549> evaluation<00:13:59.639> and<00:14:00.359> we 00:14:01.339 --> 00:14:01.349 align:start position:0% doing the performance evaluation and we 00:14:01.349 --> 00:14:03.619 align:start position:0% doing the performance evaluation and we are<00:14:01.439> quite<00:14:01.679> happy<00:14:02.249> with<00:14:02.549> these<00:14:02.669> these<00:14:03.209> early 00:14:03.619 --> 00:14:03.629 align:start position:0% are quite happy with these these early 00:14:03.629 --> 00:14:08.169 align:start position:0% are quite happy with these these early results<00:14:05.089> the<00:14:06.089> other<00:14:06.149> thing<00:14:06.509> when<00:14:06.689> you<00:14:07.129> compute 00:14:08.169 --> 00:14:08.179 align:start position:0% results the other thing when you compute 00:14:08.179 --> 00:14:11.119 align:start position:0% results the other thing when you compute when<00:14:09.179> you<00:14:09.269> do<00:14:09.419> an<00:14:09.539> execution<00:14:10.229> on<00:14:10.439> a<00:14:10.499> machine 00:14:11.119 --> 00:14:11.129 align:start position:0% when you do an execution on a machine 00:14:11.129 --> 00:14:14.659 align:start position:0% when you do an execution on a machine you<00:14:11.219> don't<00:14:11.369> trust<00:14:11.699> is<00:14:11.969> the<00:14:12.449> security<00:14:13.369> and<00:14:14.369> so 00:14:14.659 --> 00:14:14.669 align:start position:0% you don't trust is the security and so 00:14:14.669 --> 00:14:18.319 align:start position:0% you don't trust is the security and so there<00:14:15.089> are<00:14:15.119> two<00:14:15.769> aspects<00:14:16.769> here<00:14:17.129> so<00:14:17.789> once<00:14:18.029> the 00:14:18.319 --> 00:14:18.329 align:start position:0% there are two aspects here so once the 00:14:18.329 --> 00:14:21.229 align:start position:0% there are two aspects here so once the sandbox<00:14:18.809> sandbox<00:14:19.199> thing<00:14:19.859> it's<00:14:20.519> the<00:14:20.879> technique 00:14:21.229 --> 00:14:21.239 align:start position:0% sandbox sandbox thing it's the technique 00:14:21.239 --> 00:14:23.299 align:start position:0% sandbox sandbox thing it's the technique that<00:14:21.299> protect<00:14:22.019> the<00:14:22.139> workers<00:14:22.529> from<00:14:22.979> the 00:14:23.299 --> 00:14:23.309 align:start position:0% that protect the workers from the 00:14:23.309 --> 00:14:25.399 align:start position:0% that protect the workers from the application<00:14:24.239> so<00:14:24.449> imagine<00:14:24.779> the<00:14:24.869> applications 00:14:25.399 --> 00:14:25.409 align:start position:0% application so imagine the applications 00:14:25.409 --> 00:14:27.799 align:start position:0% application so imagine the applications of<00:14:25.529> virus<00:14:25.889> what<00:14:26.519> you<00:14:26.639> want<00:14:26.819> to<00:14:26.939> do<00:14:27.089> is<00:14:27.299> to 00:14:27.799 --> 00:14:27.809 align:start position:0% of virus what you want to do is to 00:14:27.809 --> 00:14:29.929 align:start position:0% of virus what you want to do is to execute<00:14:28.199> this<00:14:28.409> application<00:14:29.099> in<00:14:29.279> sort<00:14:29.579> of<00:14:29.729> a 00:14:29.929 --> 00:14:29.939 align:start position:0% execute this application in sort of a 00:14:29.939 --> 00:14:31.669 align:start position:0% execute this application in sort of a restrain<00:14:30.329> an<00:14:30.449> environment<00:14:31.199> where<00:14:31.559> you 00:14:31.669 --> 00:14:31.679 align:start position:0% restrain an environment where you 00:14:31.679 --> 00:14:33.679 align:start position:0% restrain an environment where you control<00:14:31.919> what<00:14:32.279> the<00:14:32.369> application<00:14:32.879> is<00:14:32.909> actually 00:14:33.679 --> 00:14:33.689 align:start position:0% control what the application is actually 00:14:33.689 --> 00:14:35.869 align:start position:0% control what the application is actually going<00:14:33.839> to<00:14:34.019> do<00:14:34.139> so<00:14:34.829> this<00:14:35.009> is<00:14:35.129> something<00:14:35.549> that<00:14:35.579> is 00:14:35.869 --> 00:14:35.879 align:start position:0% going to do so this is something that is 00:14:35.879 --> 00:14:38.029 align:start position:0% going to do so this is something that is not<00:14:36.029> you<00:14:36.209> take<00:14:36.419> this<00:14:36.569> for<00:14:36.779> us<00:14:37.019> actually<00:14:37.199> there 00:14:38.029 --> 00:14:38.039 align:start position:0% not you take this for us actually there 00:14:38.039 --> 00:14:39.769 align:start position:0% not you take this for us actually there are<00:14:38.099> many<00:14:38.249> ways<00:14:38.519> to<00:14:38.549> do<00:14:38.789> that<00:14:38.909> can<00:14:39.209> be<00:14:39.329> a<00:14:39.359> kernel 00:14:39.769 --> 00:14:39.779 align:start position:0% are many ways to do that can be a kernel 00:14:39.779 --> 00:14:42.949 align:start position:0% are many ways to do that can be a kernel level<00:14:39.899> or<00:14:40.259> virtualization<00:14:41.629> basically<00:14:42.629> here 00:14:42.949 --> 00:14:42.959 align:start position:0% level or virtualization basically here 00:14:42.959 --> 00:14:45.769 align:start position:0% level or virtualization basically here the<00:14:42.989> main<00:14:43.349> issues<00:14:43.769> are<00:14:44.069> more<00:14:44.759> with<00:14:44.969> respect<00:14:45.179> to 00:14:45.769 --> 00:14:45.779 align:start position:0% the main issues are more with respect to 00:14:45.779 --> 00:14:48.319 align:start position:0% the main issues are more with respect to deployment<00:14:46.679> how<00:14:47.009> is<00:14:47.099> it<00:14:47.219> going<00:14:47.489> to<00:14:47.609> be<00:14:47.729> deep<00:14:47.909> to 00:14:48.319 --> 00:14:48.329 align:start position:0% deployment how is it going to be deep to 00:14:48.329 --> 00:14:50.239 align:start position:0% deployment how is it going to be deep to be<00:14:48.569> installed<00:14:49.139> by<00:14:49.379> the<00:14:49.409> machine<00:14:49.889> join<00:14:50.039> in<00:14:50.159> the 00:14:50.239 --> 00:14:50.249 align:start position:0% be installed by the machine join in the 00:14:50.249 --> 00:14:53.889 align:start position:0% be installed by the machine join in the network<00:14:50.989> the<00:14:51.989> second<00:14:52.289> thing<00:14:52.469> that<00:14:52.499> is<00:14:52.769> renew 00:14:53.889 --> 00:14:53.899 align:start position:0% network the second thing that is renew 00:14:53.899 --> 00:14:56.389 align:start position:0% network the second thing that is renew the<00:14:54.899> second<00:14:55.169> thing<00:14:55.379> is<00:14:55.679> how<00:14:55.889> you're<00:14:56.099> going<00:14:56.279> to 00:14:56.389 --> 00:14:56.399 align:start position:0% the second thing is how you're going to 00:14:56.399 --> 00:14:58.939 align:start position:0% the second thing is how you're going to protect<00:14:56.939> the<00:14:57.629> application<00:14:58.349> from<00:14:58.589> the<00:14:58.769> worker 00:14:58.939 --> 00:14:58.949 align:start position:0% protect the application from the worker 00:14:58.949 --> 00:15:00.559 align:start position:0% protect the application from the worker who<00:14:59.249> don't<00:14:59.429> trust<00:14:59.639> the<00:14:59.759> machine<00:15:00.149> how<00:15:00.509> the 00:15:00.559 --> 00:15:00.569 align:start position:0% who don't trust the machine how the 00:15:00.569 --> 00:15:02.389 align:start position:0% who don't trust the machine how the machine<00:15:00.929> is<00:15:01.049> going<00:15:01.079> you<00:15:01.499> know<00:15:01.529> that<00:15:02.009> there<00:15:02.279> can 00:15:02.389 --> 00:15:02.399 align:start position:0% machine is going you know that there can 00:15:02.399 --> 00:15:04.639 align:start position:0% machine is going you know that there can be<00:15:02.429> some<00:15:02.669> privacy<00:15:03.149> issue<00:15:03.389> so<00:15:03.959> up<00:15:04.199> to<00:15:04.379> know<00:15:04.529> we 00:15:04.639 --> 00:15:04.649 align:start position:0% be some privacy issue so up to know we 00:15:04.649 --> 00:15:07.519 align:start position:0% be some privacy issue so up to know we had<00:15:04.799> no<00:15:04.979> solution<00:15:05.309> for<00:15:05.339> that<00:15:05.609> but<00:15:06.359> since<00:15:06.659> since 00:15:07.519 --> 00:15:07.529 align:start position:0% had no solution for that but since since 00:15:07.529 --> 00:15:08.929 align:start position:0% had no solution for that but since since some<00:15:07.709> time<00:15:07.739> there<00:15:08.129> is<00:15:08.249> a<00:15:08.279> new<00:15:08.429> solution<00:15:08.639> that 00:15:08.929 --> 00:15:08.939 align:start position:0% some time there is a new solution that 00:15:08.939 --> 00:15:11.899 align:start position:0% some time there is a new solution that appears<00:15:09.899> it's<00:15:10.409> called<00:15:10.709> an<00:15:10.859> clave<00:15:11.249> and 00:15:11.899 --> 00:15:11.909 align:start position:0% appears it's called an clave and 00:15:11.909 --> 00:15:13.759 align:start position:0% appears it's called an clave and particular<00:15:12.449> thanks<00:15:12.809> to<00:15:13.019> Intel 00:15:13.759 --> 00:15:13.769 align:start position:0% particular thanks to Intel 00:15:13.769 --> 00:15:18.590 align:start position:0% particular thanks to Intel as<00:15:14.119> our<00:15:15.119> new<00:15:15.329> instruction<00:15:16.050> set<00:15:16.679> that<00:15:17.389> that<00:15:18.389> are 00:15:18.590 --> 00:15:18.600 align:start position:0% as our new instruction set that that are 00:15:18.600 --> 00:15:22.939 align:start position:0% as our new instruction set that that are no<00:15:18.839> deployed<00:15:19.589> and<00:15:20.089> entire<00:15:21.089> process<00:15:21.600> holes<00:15:21.949> we 00:15:22.939 --> 00:15:22.949 align:start position:0% no deployed and entire process holes we 00:15:22.949 --> 00:15:24.739 align:start position:0% no deployed and entire process holes we don't<00:15:23.129> have<00:15:23.220> a<00:15:23.249> solution<00:15:23.429> for<00:15:23.819> that<00:15:23.879> so<00:15:24.480> an<00:15:24.600> in 00:15:24.739 --> 00:15:24.749 align:start position:0% don't have a solution for that so an in 00:15:24.749 --> 00:15:28.759 align:start position:0% don't have a solution for that so an in clave<00:15:25.050> this<00:15:25.350> is<00:15:25.559> basically<00:15:26.689> a<00:15:27.689> memory<00:15:28.379> space 00:15:28.759 --> 00:15:28.769 align:start position:0% clave this is basically a memory space 00:15:28.769 --> 00:15:31.400 align:start position:0% clave this is basically a memory space that<00:15:29.309> is<00:15:29.489> for<00:15:29.670> you<00:15:29.790> you<00:15:30.149> executor<00:15:30.660> application 00:15:31.400 --> 00:15:31.410 align:start position:0% that is for you you executor application 00:15:31.410 --> 00:15:34.429 align:start position:0% that is for you you executor application and<00:15:31.649> even<00:15:32.279> I<00:15:32.790> mean<00:15:33.239> even<00:15:33.600> root<00:15:33.809> on<00:15:34.019> the<00:15:34.049> machine 00:15:34.429 --> 00:15:34.439 align:start position:0% and even I mean even root on the machine 00:15:34.439 --> 00:15:35.809 align:start position:0% and even I mean even root on the machine even<00:15:34.589> if<00:15:34.739> you<00:15:34.799> have<00:15:34.889> privileged<00:15:35.309> access<00:15:35.339> on 00:15:35.809 --> 00:15:35.819 align:start position:0% even if you have privileged access on 00:15:35.819 --> 00:15:37.549 align:start position:0% even if you have privileged access on the<00:15:35.939> machine<00:15:36.209> you<00:15:36.299> cannot<00:15:36.509> access<00:15:36.899> to<00:15:37.439> this 00:15:37.549 --> 00:15:37.559 align:start position:0% the machine you cannot access to this 00:15:37.559 --> 00:15:39.979 align:start position:0% the machine you cannot access to this memory<00:15:37.860> because<00:15:38.309> fully<00:15:38.610> encrypted<00:15:38.910> and<00:15:39.239> the 00:15:39.979 --> 00:15:39.989 align:start position:0% memory because fully encrypted and the 00:15:39.989 --> 00:15:41.539 align:start position:0% memory because fully encrypted and the way<00:15:40.139> to<00:15:40.199> decrypt<00:15:40.589> the<00:15:40.769> memories<00:15:41.309> in<00:15:41.459> a 00:15:41.539 --> 00:15:41.549 align:start position:0% way to decrypt the memories in a 00:15:41.549 --> 00:15:43.970 align:start position:0% way to decrypt the memories in a situation<00:15:41.999> mat<00:15:42.119> in<00:15:42.239> the<00:15:42.329> processor<00:15:42.809> so<00:15:43.709> what 00:15:43.970 --> 00:15:43.980 align:start position:0% situation mat in the processor so what 00:15:43.980 --> 00:15:45.289 align:start position:0% situation mat in the processor so what we<00:15:44.100> are<00:15:44.160> doing<00:15:44.189> now<00:15:44.579> that<00:15:44.610> we're<00:15:45.029> evaluating 00:15:45.289 --> 00:15:45.299 align:start position:0% we are doing now that we're evaluating 00:15:45.299 --> 00:15:48.559 align:start position:0% we are doing now that we're evaluating two<00:15:46.079> solutions<00:15:46.860> to<00:15:47.459> execute<00:15:47.879> our<00:15:47.970> application 00:15:48.559 --> 00:15:48.569 align:start position:0% two solutions to execute our application 00:15:48.569 --> 00:15:50.989 align:start position:0% two solutions to execute our application within<00:15:48.749> an<00:15:48.899> app<00:15:49.049> claim<00:15:49.350> one<00:15:50.220> is<00:15:50.519> called<00:15:50.850> as 00:15:50.989 --> 00:15:50.999 align:start position:0% within an app claim one is called as 00:15:50.999 --> 00:15:52.850 align:start position:0% within an app claim one is called as Korn<00:15:51.329> something<00:15:52.110> that<00:15:52.259> has<00:15:52.379> been<00:15:52.499> published 00:15:52.850 --> 00:15:52.860 align:start position:0% Korn something that has been published 00:15:52.860 --> 00:15:55.549 align:start position:0% Korn something that has been published at<00:15:53.160> the<00:15:53.339> West<00:15:53.579> di<00:15:53.790> dis<00:15:54.509> Europe<00:15:54.809> and<00:15:55.079> this 00:15:55.549 --> 00:15:55.559 align:start position:0% at the West di dis Europe and this 00:15:55.559 --> 00:15:57.619 align:start position:0% at the West di dis Europe and this allows<00:15:55.889> you<00:15:56.040> to<00:15:56.100> run<00:15:56.489> and<00:15:56.759> Linux<00:15:57.179> container 00:15:57.619 --> 00:15:57.629 align:start position:0% allows you to run and Linux container 00:15:57.629 --> 00:15:59.900 align:start position:0% allows you to run and Linux container Indian<00:15:58.230> clay<00:15:58.499> there<00:15:59.339> is<00:15:59.459> another<00:15:59.670> solution 00:15:59.900 --> 00:15:59.910 align:start position:0% Indian clay there is another solution 00:15:59.910 --> 00:16:01.910 align:start position:0% Indian clay there is another solution that<00:16:00.239> we<00:16:00.449> are<00:16:00.540> looking<00:16:00.600> at<00:16:00.929> called<00:16:01.439> a<00:16:01.529> graphene 00:16:01.910 --> 00:16:01.920 align:start position:0% that we are looking at called a graphene 00:16:01.920 --> 00:16:04.460 align:start position:0% that we are looking at called a graphene as<00:16:02.249> IG's<00:16:02.579> the<00:16:03.299> same<00:16:03.509> idea<00:16:03.809> but<00:16:03.839> instead<00:16:04.230> of 00:16:04.460 --> 00:16:04.470 align:start position:0% as IG's the same idea but instead of 00:16:04.470 --> 00:16:06.949 align:start position:0% as IG's the same idea but instead of container<00:16:04.889> it<00:16:05.069> relies<00:16:05.399> on<00:16:05.429> library<00:16:06.299> OS<00:16:06.660> or<00:16:06.899> a 00:16:06.949 --> 00:16:06.959 align:start position:0% container it relies on library OS or a 00:16:06.959 --> 00:16:09.139 align:start position:0% container it relies on library OS or a microkernel<00:16:07.889> it's<00:16:08.220> almost<00:16:08.459> the<00:16:08.939> same<00:16:09.089> thing 00:16:09.139 --> 00:16:09.149 align:start position:0% microkernel it's almost the same thing 00:16:09.149 --> 00:16:14.059 align:start position:0% microkernel it's almost the same thing fuel<00:16:10.699> so<00:16:11.699> a<00:16:12.059> couple<00:16:12.389> of<00:16:12.689> things<00:16:13.679> that<00:16:13.799> are 00:16:14.059 --> 00:16:14.069 align:start position:0% fuel so a couple of things that are 00:16:14.069 --> 00:16:17.299 align:start position:0% fuel so a couple of things that are coming<00:16:14.309> in<00:16:14.790> the<00:16:15.149> very<00:16:15.899> next<00:16:16.079> future<00:16:16.559> just 00:16:17.299 --> 00:16:17.309 align:start position:0% coming in the very next future just 00:16:17.309 --> 00:16:20.059 align:start position:0% coming in the very next future just after<00:16:17.459> Def<00:16:17.819> Con<00:16:18.179> we're<00:16:18.420> going<00:16:18.660> to<00:16:18.839> run<00:16:19.019> and<00:16:19.290> ask 00:16:20.059 --> 00:16:20.069 align:start position:0% after Def Con we're going to run and ask 00:16:20.069 --> 00:16:23.900 align:start position:0% after Def Con we're going to run and ask me<00:16:20.339> at<00:16:20.699> freaking<00:16:21.149> ready<00:16:22.519> then<00:16:23.519> we<00:16:23.639> are<00:16:23.730> going 00:16:23.900 --> 00:16:23.910 align:start position:0% me at freaking ready then we are going 00:16:23.910 --> 00:16:25.429 align:start position:0% me at freaking ready then we are going to<00:16:24.029> participate<00:16:24.269> to<00:16:24.720> the<00:16:24.809> supercomputing 00:16:25.429 --> 00:16:25.439 align:start position:0% to participate to the supercomputing 00:16:25.439 --> 00:16:27.199 align:start position:0% to participate to the supercomputing conference<00:16:25.549> even<00:16:26.549> though<00:16:26.730> we<00:16:26.879> all<00:16:26.970> know<00:16:26.999> it 00:16:27.199 --> 00:16:27.209 align:start position:0% conference even though we all know it 00:16:27.209 --> 00:16:28.340 align:start position:0% conference even though we all know it could<00:16:27.389> talk<00:16:27.540> you<00:16:27.660> and<00:16:27.779> see<00:16:27.959> we<00:16:28.110> still<00:16:28.290> have 00:16:28.340 --> 00:16:28.350 align:start position:0% could talk you and see we still have 00:16:28.350 --> 00:16:31.129 align:start position:0% could talk you and see we still have those<00:16:28.679> big<00:16:29.339> machines<00:16:29.549> that<00:16:30.059> that<00:16:30.480> you<00:16:30.929> have<00:16:31.110> a 00:16:31.129 --> 00:16:31.139 align:start position:0% those big machines that that you have a 00:16:31.139 --> 00:16:33.549 align:start position:0% those big machines that that you have a super<00:16:31.559> computing<00:16:32.009> to<00:16:32.429> be<00:16:32.579> in<00:16:32.670> Denver<00:16:32.879> Colorado 00:16:33.549 --> 00:16:33.559 align:start position:0% super computing to be in Denver Colorado 00:16:33.559 --> 00:16:36.049 align:start position:0% super computing to be in Denver Colorado we<00:16:34.559> are<00:16:34.649> going<00:16:34.860> to<00:16:34.980> organise<00:16:35.309> a<00:16:35.339> Serie<00:16:35.699> of<00:16:35.790> meet 00:16:36.049 --> 00:16:36.059 align:start position:0% we are going to organise a Serie of meet 00:16:36.059 --> 00:16:38.749 align:start position:0% we are going to organise a Serie of meet up<00:16:36.089> starting<00:16:36.959> with<00:16:36.990> volume<00:16:37.649> so<00:16:38.189> that<00:16:38.369> people 00:16:38.749 --> 00:16:38.759 align:start position:0% up starting with volume so that people 00:16:38.759 --> 00:16:41.030 align:start position:0% up starting with volume so that people can<00:16:39.029> get<00:16:39.240> in<00:16:39.449> the<00:16:39.600> technology<00:16:40.290> and<00:16:40.619> use<00:16:40.799> that 00:16:41.030 --> 00:16:41.040 align:start position:0% can get in the technology and use that 00:16:41.040 --> 00:16:42.530 align:start position:0% can get in the technology and use that and<00:16:41.399> start<00:16:41.939> to<00:16:42.059> develop<00:16:42.209> their<00:16:42.509> own 00:16:42.530 --> 00:16:42.540 align:start position:0% and start to develop their own 00:16:42.540 --> 00:16:45.970 align:start position:0% and start to develop their own application<00:16:43.529> by<00:16:44.459> being<00:16:44.759> December<00:16:45.329> hopefully 00:16:45.970 --> 00:16:45.980 align:start position:0% application by being December hopefully 00:16:45.980 --> 00:16:48.499 align:start position:0% application by being December hopefully the<00:16:46.980> App<00:16:47.100> Store<00:16:47.429> for<00:16:47.670> distributed 00:16:48.499 --> 00:16:48.509 align:start position:0% the App Store for distributed 00:16:48.509 --> 00:16:50.539 align:start position:0% the App Store for distributed application<00:16:49.110> will<00:16:49.379> go<00:16:49.499> live<00:16:49.799> will<00:16:50.189> go<00:16:50.339> live 00:16:50.539 --> 00:16:50.549 align:start position:0% application will go live will go live 00:16:50.549 --> 00:16:52.879 align:start position:0% application will go live will go live and<00:16:50.790> so<00:16:51.420> you<00:16:51.480> will<00:16:51.959> be<00:16:52.110> able<00:16:52.199> to<00:16:52.470> publish<00:16:52.649> the 00:16:52.879 --> 00:16:52.889 align:start position:0% and so you will be able to publish the 00:16:52.889 --> 00:16:55.759 align:start position:0% and so you will be able to publish the application<00:16:52.980> this<00:16:53.579> our<00:16:53.790> App<00:16:53.999> Store<00:16:54.769> by 00:16:55.759 --> 00:16:55.769 align:start position:0% application this our App Store by 00:16:55.769 --> 00:17:00.350 align:start position:0% application this our App Store by December<00:16:56.249> we<00:16:56.369> also<00:16:56.610> going<00:16:56.790> to<00:16:57.110> launch<00:16:59.089> ad<00:17:00.089> app 00:17:00.350 --> 00:17:00.360 align:start position:0% December we also going to launch ad app 00:17:00.360 --> 00:17:02.419 align:start position:0% December we also going to launch ad app development<00:17:00.809> challenge<00:17:01.470> the<00:17:01.799> idea<00:17:02.100> is<00:17:02.189> really 00:17:02.419 --> 00:17:02.429 align:start position:0% development challenge the idea is really 00:17:02.429 --> 00:17:06.079 align:start position:0% development challenge the idea is really to<00:17:02.720> to<00:17:03.720> give<00:17:04.559> bounties<00:17:04.980> to<00:17:05.010> developers<00:17:05.909> so 00:17:06.079 --> 00:17:06.089 align:start position:0% to to give bounties to developers so 00:17:06.089 --> 00:17:07.879 align:start position:0% to to give bounties to developers so that<00:17:06.120> they<00:17:06.449> can<00:17:06.720> proposer<00:17:07.319> some<00:17:07.679> cool 00:17:07.879 --> 00:17:07.889 align:start position:0% that they can proposer some cool 00:17:07.889 --> 00:17:10.159 align:start position:0% that they can proposer some cool applications<00:17:08.579> and<00:17:09.029> we<00:17:09.179> will<00:17:09.299> be<00:17:09.449> really<00:17:09.839> happy 00:17:10.159 --> 00:17:10.169 align:start position:0% applications and we will be really happy 00:17:10.169 --> 00:17:13.279 align:start position:0% applications and we will be really happy to<00:17:10.319> support<00:17:10.649> them<00:17:10.889> and<00:17:11.220> by<00:17:12.179> the<00:17:12.240> next<00:17:13.110> year<00:17:13.260> so 00:17:13.279 --> 00:17:13.289 align:start position:0% to support them and by the next year so 00:17:13.289 --> 00:17:15.139 align:start position:0% to support them and by the next year so we<00:17:13.529> are<00:17:13.649> going<00:17:13.799> to<00:17:13.919> not<00:17:14.100> show<00:17:14.279> another<00:17:14.639> program 00:17:15.139 --> 00:17:15.149 align:start position:0% we are going to not show another program 00:17:15.149 --> 00:17:17.449 align:start position:0% we are going to not show another program which<00:17:15.569> is<00:17:15.779> di<00:17:15.959> exact<00:17:16.439> Summer<00:17:16.649> of<00:17:16.740> Code<00:17:16.860> I<00:17:17.279> don't 00:17:17.449 --> 00:17:17.459 align:start position:0% which is di exact Summer of Code I don't 00:17:17.459 --> 00:17:17.780 align:start position:0% which is di exact Summer of Code I don't know<00:17:17.549> if<00:17:17.610> you 00:17:17.780 --> 00:17:17.790 align:start position:0% know if you 00:17:17.790 --> 00:17:19.760 align:start position:0% know if you I<00:17:17.820> mean<00:17:18.060> our<00:17:18.150> google<00:17:18.570> Summer<00:17:18.930> of<00:17:18.960> Code<00:17:19.050> that 00:17:19.760 --> 00:17:19.770 align:start position:0% I mean our google Summer of Code that 00:17:19.770 --> 00:17:25.040 align:start position:0% I mean our google Summer of Code that same<00:17:20.040> ID<00:17:20.660> so<00:17:21.660> it<00:17:21.690> allows<00:17:22.490> students<00:17:23.960> you<00:17:24.960> know 00:17:25.040 --> 00:17:25.050 align:start position:0% same ID so it allows students you know 00:17:25.050 --> 00:17:27.800 align:start position:0% same ID so it allows students you know everywhere<00:17:25.500> on<00:17:25.650> earth<00:17:25.830> to<00:17:26.100> work<00:17:26.310> on<00:17:26.810> any 00:17:27.800 --> 00:17:27.810 align:start position:0% everywhere on earth to work on any 00:17:27.810 --> 00:17:30.620 align:start position:0% everywhere on earth to work on any subject<00:17:28.200> related<00:17:28.620> to<00:17:29.160> a<00:17:29.190> decentralization<00:17:30.180> so 00:17:30.620 --> 00:17:30.630 align:start position:0% subject related to a decentralization so 00:17:30.630 --> 00:17:32.270 align:start position:0% subject related to a decentralization so it's<00:17:30.780> not<00:17:30.960> only<00:17:31.140> for<00:17:31.350> exact<00:17:31.680> it's<00:17:32.070> for 00:17:32.270 --> 00:17:32.280 align:start position:0% it's not only for exact it's for 00:17:32.280 --> 00:17:35.540 align:start position:0% it's not only for exact it's for everyone<00:17:33.410> okay<00:17:34.410> so<00:17:34.620> as<00:17:34.800> a<00:17:34.830> conclusion<00:17:35.220> we've 00:17:35.540 --> 00:17:35.550 align:start position:0% everyone okay so as a conclusion we've 00:17:35.550 --> 00:17:37.520 align:start position:0% everyone okay so as a conclusion we've been<00:17:35.700> really<00:17:35.970> happy<00:17:36.150> to<00:17:36.570> present<00:17:36.990> you<00:17:37.320> this 00:17:37.520 --> 00:17:37.530 align:start position:0% been really happy to present you this 00:17:37.530 --> 00:17:40.700 align:start position:0% been really happy to present you this first<00:17:37.830> step<00:17:38.040> for<00:17:38.550> I<00:17:38.610> exact<00:17:39.120> hope<00:17:39.780> you<00:17:40.020> will<00:17:40.200> try 00:17:40.700 --> 00:17:40.710 align:start position:0% first step for I exact hope you will try 00:17:40.710 --> 00:17:43.810 align:start position:0% first step for I exact hope you will try it<00:17:40.740> meters<00:17:41.550> where<00:17:41.790> we<00:17:42.030> have<00:17:42.180> a<00:17:42.210> booth<00:17:42.480> and 00:17:43.810 --> 00:17:43.820 align:start position:0% it meters where we have a booth and 00:17:43.820 --> 00:17:47.590 align:start position:0% it meters where we have a booth and happy<00:17:44.820> Def<00:17:44.970> Con<00:17:45.240> happy<00:17:45.870> I<00:17:45.900> king 00:17:47.590 --> 00:17:47.600 align:start position:0% happy Def Con happy I king 00:17:47.600 --> 00:17:53.300 align:start position:0% happy Def Con happy I king [Applause] 00:17:53.300 --> 00:17:53.310 align:start position:0% [Applause] 00:17:53.310 --> 00:18:00.609 align:start position:0% [Applause] [Music]