WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:15.180 align:start position:0% [Applause] 00:00:15.180 --> 00:00:15.190 align:start position:0% 00:00:15.190 --> 00:00:18.810 align:start position:0% and<00:00:15.279> the<00:00:15.820> funky<00:00:16.299> CEO<00:00:16.509> as<00:00:17.320> Isis<00:00:17.890> loves<00:00:18.130> and<00:00:18.430> also 00:00:18.810 --> 00:00:18.820 align:start position:0% and the funky CEO as Isis loves and also 00:00:18.820 --> 00:00:21.359 align:start position:0% and the funky CEO as Isis loves and also a<00:00:18.849> professor<00:00:19.060> at<00:00:19.570> UC<00:00:20.169> Berkeley<00:00:20.500> and<00:00:21.039> today<00:00:21.340> I 00:00:21.359 --> 00:00:21.369 align:start position:0% a professor at UC Berkeley and today I 00:00:21.369 --> 00:00:23.729 align:start position:0% a professor at UC Berkeley and today I will<00:00:21.669> talk<00:00:21.820> about<00:00:22.000> the<00:00:22.360> decentralized<00:00:22.930> petty 00:00:23.729 --> 00:00:23.739 align:start position:0% will talk about the decentralized petty 00:00:23.739 --> 00:00:27.720 align:start position:0% will talk about the decentralized petty tyranny<00:00:25.200> so<00:00:26.200> first<00:00:26.410> as<00:00:26.529> we<00:00:26.739> all<00:00:26.860> know<00:00:27.009> Peter<00:00:27.309> is 00:00:27.720 --> 00:00:27.730 align:start position:0% tyranny so first as we all know Peter is 00:00:27.730 --> 00:00:31.139 align:start position:0% tyranny so first as we all know Peter is the<00:00:28.000> new<00:00:28.390> oil<00:00:29.189> this<00:00:30.189> data<00:00:30.430> is<00:00:30.669> really<00:00:30.820> helpful 00:00:31.139 --> 00:00:31.149 align:start position:0% the new oil this data is really helpful 00:00:31.149 --> 00:00:35.160 align:start position:0% the new oil this data is really helpful for<00:00:31.540> us<00:00:32.290> to<00:00:32.950> make<00:00:33.100> better<00:00:33.129> decisions<00:00:33.899> and<00:00:34.899> give 00:00:35.160 --> 00:00:35.170 align:start position:0% for us to make better decisions and give 00:00:35.170 --> 00:00:39.540 align:start position:0% for us to make better decisions and give us<00:00:35.290> a<00:00:35.590> lot<00:00:35.710> in<00:00:36.640> fact<00:00:37.020> hi<00:00:38.050> a<00:00:38.559> lot<00:00:38.890> of<00:00:38.920> this<00:00:39.129> people 00:00:39.540 --> 00:00:39.550 align:start position:0% us a lot in fact hi a lot of this people 00:00:39.550 --> 00:00:42.389 align:start position:0% us a lot in fact hi a lot of this people is<00:00:39.850> really<00:00:40.210> is<00:00:40.629> also<00:00:40.989> very<00:00:41.200> sensitive<00:00:41.350> and<00:00:41.860> had 00:00:42.389 --> 00:00:42.399 align:start position:0% is really is also very sensitive and had 00:00:42.399 --> 00:00:45.599 align:start position:0% is really is also very sensitive and had not<00:00:42.550> any<00:00:42.730> sensitive<00:00:43.120> data<00:00:43.679> protists<00:00:44.679> a<00:00:44.859> lot<00:00:45.489> of 00:00:45.599 --> 00:00:45.609 align:start position:0% not any sensitive data protists a lot of 00:00:45.609 --> 00:00:47.849 align:start position:0% not any sensitive data protists a lot of challenges<00:00:45.789> so<00:00:46.300> for<00:00:46.809> example<00:00:47.170> we<00:00:47.260> continue<00:00:47.679> to 00:00:47.849 --> 00:00:47.859 align:start position:0% challenges so for example we continue to 00:00:47.859 --> 00:00:49.979 align:start position:0% challenges so for example we continue to see<00:00:48.069> really<00:00:48.699> large-scale<00:00:48.969> data<00:00:49.480> breaches 00:00:49.979 --> 00:00:49.989 align:start position:0% see really large-scale data breaches 00:00:49.989 --> 00:00:55.410 align:start position:0% see really large-scale data breaches where<00:00:50.940> attackers<00:00:51.940> compromised<00:00:54.420> sensitive 00:00:55.410 --> 00:00:55.420 align:start position:0% where attackers compromised sensitive 00:00:55.420 --> 00:00:57.209 align:start position:0% where attackers compromised sensitive and<00:00:55.839> still<00:00:56.079> sensitive<00:00:56.379> information<00:00:56.710> about 00:00:57.209 --> 00:00:57.219 align:start position:0% and still sensitive information about 00:00:57.219 --> 00:01:01.770 align:start position:0% and still sensitive information about hundreds<00:00:58.030> of<00:00:58.089> millions<00:00:58.149> of<00:00:58.679> users<00:01:00.239> being<00:01:01.239> in<00:01:01.629> a 00:01:01.770 --> 00:01:01.780 align:start position:0% hundreds of millions of users being in a 00:01:01.780 --> 00:01:06.060 align:start position:0% hundreds of millions of users being in a one<00:01:02.050> in<00:01:02.829> a<00:01:02.979> single<00:01:03.280> account<00:01:04.019> and<00:01:05.019> also<00:01:05.409> we 00:01:06.060 --> 00:01:06.070 align:start position:0% one in a single account and also we 00:01:06.070 --> 00:01:07.830 align:start position:0% one in a single account and also we continue<00:01:06.460> to<00:01:06.610> see<00:01:06.790> that<00:01:06.820> users<00:01:07.300> are<00:01:07.570> using 00:01:07.830 --> 00:01:07.840 align:start position:0% continue to see that users are using 00:01:07.840 --> 00:01:12.360 align:start position:0% continue to see that users are using trusts<00:01:08.549> incomplete<00:01:09.600> as<00:01:10.600> a<00:01:11.080> lot<00:01:11.500> bigger<00:01:12.070> and 00:01:12.360 --> 00:01:12.370 align:start position:0% trusts incomplete as a lot bigger and 00:01:12.370 --> 00:01:15.770 align:start position:0% trusts incomplete as a lot bigger and maybe<00:01:12.850> mishandles<00:01:13.540> abuse<00:01:14.350> and 00:01:15.770 --> 00:01:15.780 align:start position:0% maybe mishandles abuse and 00:01:15.780 --> 00:01:19.920 align:start position:0% maybe mishandles abuse and so<00:01:16.780> as<00:01:16.990> we<00:01:17.280> handle<00:01:18.280> sensitive<00:01:18.760> data<00:01:19.180> there<00:01:19.810> are 00:01:19.920 --> 00:01:19.930 align:start position:0% so as we handle sensitive data there are 00:01:19.930 --> 00:01:21.899 align:start position:0% so as we handle sensitive data there are a<00:01:19.960> number<00:01:20.080> of<00:01:20.409> challenges<00:01:20.740> that<00:01:21.310> we<00:01:21.490> need<00:01:21.670> to 00:01:21.899 --> 00:01:21.909 align:start position:0% a number of challenges that we need to 00:01:21.909 --> 00:01:27.330 align:start position:0% a number of challenges that we need to address<00:01:22.780> one<00:01:23.680> as<00:01:25.050> the<00:01:26.050> English<00:01:26.890> actor<00:01:27.160> maybe 00:01:27.330 --> 00:01:27.340 align:start position:0% address one as the English actor maybe 00:01:27.340 --> 00:01:29.609 align:start position:0% address one as the English actor maybe untrusted<00:01:27.970> attackers<00:01:28.750> may<00:01:28.960> have<00:01:29.110> compromised 00:01:29.609 --> 00:01:29.619 align:start position:0% untrusted attackers may have compromised 00:01:29.619 --> 00:01:32.700 align:start position:0% untrusted attackers may have compromised the<00:01:30.400> computer<00:01:30.850> infrastructure<00:01:31.410> are<00:01:32.410> the 00:01:32.700 --> 00:01:32.710 align:start position:0% the computer infrastructure are the 00:01:32.710 --> 00:01:35.430 align:start position:0% the computer infrastructure are the advocates<00:01:33.340> not<00:01:33.490> only<00:01:33.729> be<00:01:33.850> untrusted<00:01:34.440> because 00:01:35.430 --> 00:01:35.440 align:start position:0% advocates not only be untrusted because 00:01:35.440 --> 00:01:41.100 align:start position:0% advocates not only be untrusted because the<00:01:36.040> again<00:01:36.990> attackers<00:01:37.990> may<00:01:38.530> have<00:01:40.080> may<00:01:41.080> have 00:01:41.100 --> 00:01:41.110 align:start position:0% the again attackers may have may have 00:01:41.110 --> 00:01:42.840 align:start position:0% the again attackers may have may have launched<00:01:41.530> some<00:01:41.710> malicious<00:01:42.280> applications 00:01:42.840 --> 00:01:42.850 align:start position:0% launched some malicious applications 00:01:42.850 --> 00:01:44.730 align:start position:0% launched some malicious applications other<00:01:43.000> applications<00:01:43.600> may<00:01:43.869> have<00:01:44.140> poor 00:01:44.730 --> 00:01:44.740 align:start position:0% other applications may have poor 00:01:44.740 --> 00:01:49.410 align:start position:0% other applications may have poor abilities<00:01:45.220> and<00:01:46.119> also<00:01:47.610> some<00:01:48.610> applications<00:01:49.330> may 00:01:49.410 --> 00:01:49.420 align:start position:0% abilities and also some applications may 00:01:49.420 --> 00:01:54.090 align:start position:0% abilities and also some applications may have<00:01:49.750> undesirable<00:01:51.270> deferred<00:01:52.270> leakage<00:01:53.039> so<00:01:54.039> to 00:01:54.090 --> 00:01:54.100 align:start position:0% have undesirable deferred leakage so to 00:01:54.100 --> 00:01:58.650 align:start position:0% have undesirable deferred leakage so to address<00:01:54.460> these<00:01:54.700> problems<00:01:55.000> at<00:01:55.509> oasis<00:01:57.240> labs<00:01:58.240> we 00:01:58.650 --> 00:01:58.660 align:start position:0% address these problems at oasis labs we 00:01:58.660 --> 00:02:01.950 align:start position:0% address these problems at oasis labs we have<00:01:58.690> been<00:01:58.990> developing<00:01:59.530> new<00:02:00.250> solutions<00:02:01.180> where 00:02:01.950 --> 00:02:01.960 align:start position:0% have been developing new solutions where 00:02:01.960 --> 00:02:06.330 align:start position:0% have been developing new solutions where we<00:02:04.200> essentially<00:02:05.200> builds<00:02:05.649> the<00:02:06.039> next 00:02:06.330 --> 00:02:06.340 align:start position:0% we essentially builds the next 00:02:06.340 --> 00:02:08.009 align:start position:0% we essentially builds the next generation<00:02:06.820> Block<00:02:07.060> in<00:02:07.300> our<00:02:07.600> contract 00:02:08.009 --> 00:02:08.019 align:start position:0% generation Block in our contract 00:02:08.019 --> 00:02:11.009 align:start position:0% generation Block in our contract platform<00:02:08.670> with<00:02:09.670> British<00:02:10.090> scalability<00:02:10.750> and 00:02:11.009 --> 00:02:11.019 align:start position:0% platform with British scalability and 00:02:11.019 --> 00:02:14.370 align:start position:0% platform with British scalability and privacy<00:02:11.530> protection<00:02:12.750> where<00:02:13.750> we<00:02:13.930> unique<00:02:14.230> or 00:02:14.370 --> 00:02:14.380 align:start position:0% privacy protection where we unique or 00:02:14.380 --> 00:02:16.199 align:start position:0% privacy protection where we unique or skill<00:02:14.620> a<00:02:14.650> postmark<00:02:15.160> on<00:02:15.280> to<00:02:15.430> execution<00:02:16.060> and 00:02:16.199 --> 00:02:16.209 align:start position:0% skill a postmark on to execution and 00:02:16.209 --> 00:02:19.400 align:start position:0% skill a postmark on to execution and also<00:02:16.959> enable<00:02:17.560> for<00:02:18.310> the<00:02:18.430> first<00:02:18.610> time 00:02:19.400 --> 00:02:19.410 align:start position:0% also enable for the first time 00:02:19.410 --> 00:02:22.979 align:start position:0% also enable for the first time confidential<00:02:20.410> smart<00:02:20.830> contracts<00:02:21.400> and<00:02:22.330> also<00:02:22.780> on 00:02:22.979 --> 00:02:22.989 align:start position:0% confidential smart contracts and also on 00:02:22.989 --> 00:02:26.039 align:start position:0% confidential smart contracts and also on top<00:02:23.019> of<00:02:23.230> the<00:02:23.380> platform<00:02:23.820> we've<00:02:24.820> built<00:02:25.090> SDKs<00:02:25.810> to 00:02:26.039 --> 00:02:26.049 align:start position:0% top of the platform we've built SDKs to 00:02:26.049 --> 00:02:27.040 align:start position:0% top of the platform we've built SDKs to enable<00:02:26.470> privacy 00:02:27.040 --> 00:02:27.050 align:start position:0% enable privacy 00:02:27.050 --> 00:02:31.630 align:start position:0% enable privacy a<00:02:27.520> machine<00:02:29.500> so<00:02:30.500> today<00:02:30.830> I'll<00:02:30.980> talk<00:02:31.220> about<00:02:31.280> some 00:02:31.630 --> 00:02:31.640 align:start position:0% a machine so today I'll talk about some 00:02:31.640 --> 00:02:35.350 align:start position:0% a machine so today I'll talk about some new<00:02:31.820> research<00:02:32.420> that<00:02:32.480> we<00:02:32.930> have<00:02:32.960> done<00:02:33.280> at<00:02:34.360> every 00:02:35.350 --> 00:02:35.360 align:start position:0% new research that we have done at every 00:02:35.360 --> 00:02:39.730 align:start position:0% new research that we have done at every Clarion<00:02:35.840> our<00:02:36.080> voices<00:02:36.910> with<00:02:38.740> decentralized 00:02:39.730 --> 00:02:39.740 align:start position:0% Clarion our voices with decentralized 00:02:39.740 --> 00:02:43.900 align:start position:0% Clarion our voices with decentralized afetr<00:02:40.250> children<00:02:41.800> so<00:02:42.800> Christmas<00:02:43.250> book<00:02:43.460> has<00:02:43.670> a 00:02:43.900 --> 00:02:43.910 align:start position:0% afetr children so Christmas book has a 00:02:43.910 --> 00:02:46.990 align:start position:0% afetr children so Christmas book has a motivating<00:02:44.480> example<00:02:45.160> and<00:02:46.160> again<00:02:46.460> frantic 00:02:46.990 --> 00:02:47.000 align:start position:0% motivating example and again frantic 00:02:47.000 --> 00:02:47.850 align:start position:0% motivating example and again frantic action 00:02:47.850 --> 00:02:47.860 align:start position:0% action 00:02:47.860 --> 00:02:51.160 align:start position:0% action so<00:02:48.860> one<00:02:49.220> banks<00:02:49.640> provides<00:02:50.480> financial<00:02:50.960> services 00:02:51.160 --> 00:02:51.170 align:start position:0% so one banks provides financial services 00:02:51.170 --> 00:02:54.790 align:start position:0% so one banks provides financial services for<00:02:51.680> example<00:02:51.820> immigrants<00:02:52.820> the<00:02:53.780> lands<00:02:54.500> they 00:02:54.790 --> 00:02:54.800 align:start position:0% for example immigrants the lands they 00:02:54.800 --> 00:02:58.210 align:start position:0% for example immigrants the lands they need<00:02:54.950> to<00:02:55.420> detect<00:02:56.420> fraud<00:02:56.780> and<00:02:57.230> typically<00:02:58.010> how 00:02:58.210 --> 00:02:58.220 align:start position:0% need to detect fraud and typically how 00:02:58.220 --> 00:03:00.340 align:start position:0% need to detect fraud and typically how this<00:02:58.430> works<00:02:58.670> is<00:02:58.850> that<00:02:58.970> each<00:02:59.090> Bank<00:02:59.480> uses<00:03:00.110> its 00:03:00.340 --> 00:03:00.350 align:start position:0% this works is that each Bank uses its 00:03:00.350 --> 00:03:02.770 align:start position:0% this works is that each Bank uses its own<00:03:00.560> data<00:03:00.890> to<00:03:01.520> build<00:03:01.700> for<00:03:02.180> example<00:03:02.630> some 00:03:02.770 --> 00:03:02.780 align:start position:0% own data to build for example some 00:03:02.780 --> 00:03:06.780 align:start position:0% own data to build for example some agility<00:03:02.990> model<00:03:03.530> for<00:03:03.800> fraud<00:03:04.670> detection 00:03:06.780 --> 00:03:06.790 align:start position:0% agility model for fraud detection 00:03:06.790 --> 00:03:12.940 align:start position:0% agility model for fraud detection poverty<00:03:07.790> as<00:03:08.000> well<00:03:08.060> as<00:03:08.980> we<00:03:09.980> know<00:03:10.430> that<00:03:11.110> it<00:03:12.110> would 00:03:12.940 --> 00:03:12.950 align:start position:0% poverty as well as we know that it would 00:03:12.950 --> 00:03:15.940 align:start position:0% poverty as well as we know that it would be<00:03:12.980> much<00:03:13.910> better<00:03:13.940> if<00:03:14.510> these<00:03:15.350> banks<00:03:15.740> can 00:03:15.940 --> 00:03:15.950 align:start position:0% be much better if these banks can 00:03:15.950 --> 00:03:18.040 align:start position:0% be much better if these banks can actually<00:03:16.370> share<00:03:16.610> that<00:03:16.850> it<00:03:17.000> had<00:03:17.180> to<00:03:17.690> build<00:03:17.900> one 00:03:18.040 --> 00:03:18.050 align:start position:0% actually share that it had to build one 00:03:18.050 --> 00:03:19.780 align:start position:0% actually share that it had to build one traffic<00:03:18.650> picture<00:03:18.920> instead<00:03:19.310> of<00:03:19.430> the 00:03:19.780 --> 00:03:19.790 align:start position:0% traffic picture instead of the 00:03:19.790 --> 00:03:23.830 align:start position:0% traffic picture instead of the individual<00:03:20.420> ones<00:03:21.940> the<00:03:22.940> case<00:03:23.120> with<00:03:23.420> Mozilla 00:03:23.830 --> 00:03:23.840 align:start position:0% individual ones the case with Mozilla 00:03:23.840 --> 00:03:26.320 align:start position:0% individual ones the case with Mozilla the<00:03:24.440> machine<00:03:24.860> imago<00:03:25.130> can<00:03:25.580> essentially<00:03:26.090> be 00:03:26.320 --> 00:03:26.330 align:start position:0% the machine imago can essentially be 00:03:26.330 --> 00:03:29.020 align:start position:0% the machine imago can essentially be more<00:03:26.480> practice<00:03:26.930> I<00:03:27.230> witnessed<00:03:28.160> another<00:03:28.430> today 00:03:29.020 --> 00:03:29.030 align:start position:0% more practice I witnessed another today 00:03:29.030 --> 00:03:31.150 align:start position:0% more practice I witnessed another today because<00:03:29.480> there<00:03:29.900> is<00:03:29.990> a<00:03:30.260> lot<00:03:30.710> of<00:03:30.740> privacy 00:03:31.150 --> 00:03:31.160 align:start position:0% because there is a lot of privacy 00:03:31.160 --> 00:03:33.130 align:start position:0% because there is a lot of privacy concerns<00:03:31.640> because<00:03:31.910> it<00:03:32.120> is<00:03:32.239> excessive<00:03:32.840> and 00:03:33.130 --> 00:03:33.140 align:start position:0% concerns because it is excessive and 00:03:33.140 --> 00:03:36.610 align:start position:0% concerns because it is excessive and also<00:03:33.860> there<00:03:34.280> may<00:03:34.459> be<00:03:34.489> missed 00:03:36.610 --> 00:03:36.620 align:start position:0% also there may be missed 00:03:36.620 --> 00:03:40.480 align:start position:0% also there may be missed so<00:03:37.620> luckily<00:03:38.270> address<00:03:39.270> this<00:03:39.540> problem 00:03:40.480 --> 00:03:40.490 align:start position:0% so luckily address this problem 00:03:40.490 --> 00:03:44.330 align:start position:0% so luckily address this problem so<00:03:41.490> there<00:03:41.670> are<00:03:42.740> alternative<00:03:43.740> solutions<00:03:44.190> that 00:03:44.330 --> 00:03:44.340 align:start position:0% so there are alternative solutions that 00:03:44.340 --> 00:03:48.860 align:start position:0% so there are alternative solutions that we<00:03:44.430> can<00:03:44.580> consider<00:03:45.320> so<00:03:46.320> II<00:03:47.570> with<00:03:48.570> one 00:03:48.860 --> 00:03:48.870 align:start position:0% we can consider so II with one 00:03:48.870 --> 00:03:51.410 align:start position:0% we can consider so II with one admissible<00:03:49.320> solution<00:03:50.190> we<00:03:50.820> can<00:03:50.970> use<00:03:51.210> something 00:03:51.410 --> 00:03:51.420 align:start position:0% admissible solution we can use something 00:03:51.420 --> 00:03:54.290 align:start position:0% admissible solution we can use something called<00:03:51.630> a<00:03:51.900> feathery<00:03:52.260> learning<00:03:52.970> so<00:03:53.970> our 00:03:54.290 --> 00:03:54.300 align:start position:0% called a feathery learning so our 00:03:54.300 --> 00:03:57.320 align:start position:0% called a feathery learning so our facility<00:03:55.080> is<00:03:55.580> mechanism<00:03:56.580> we've<00:03:56.700> done<00:03:56.910> it's<00:03:57.240> an 00:03:57.320 --> 00:03:57.330 align:start position:0% facility is mechanism we've done it's an 00:03:57.330 --> 00:04:00.250 align:start position:0% facility is mechanism we've done it's an approach<00:03:57.860> that<00:03:58.860> actually<00:03:59.190> has<00:03:59.760> seen<00:04:00.000> some 00:04:00.250 --> 00:04:00.260 align:start position:0% approach that actually has seen some 00:04:00.260 --> 00:04:03.500 align:start position:0% approach that actually has seen some adoption<00:04:01.260> deployments<00:04:02.070> I<00:04:02.280> could<00:04:03.150> go<00:04:03.300> and 00:04:03.500 --> 00:04:03.510 align:start position:0% adoption deployments I could go and 00:04:03.510 --> 00:04:08.890 align:start position:0% adoption deployments I could go and Apple<00:04:03.990> for<00:04:04.140> example<00:04:04.250> we're<00:04:05.250> essentially 00:04:08.890 --> 00:04:08.900 align:start position:0% 00:04:08.900 --> 00:04:12.140 align:start position:0% using<00:04:09.900> fertility<00:04:10.470> and<00:04:11.100> usage<00:04:11.520> data<00:04:11.790> are 00:04:12.140 --> 00:04:12.150 align:start position:0% using fertility and usage data are 00:04:12.150 --> 00:04:15.440 align:start position:0% using fertility and usage data are stores<00:04:12.770> locally<00:04:13.770> on<00:04:14.010> their<00:04:14.310> mobile<00:04:15.210> phones 00:04:15.440 --> 00:04:15.450 align:start position:0% stores locally on their mobile phones 00:04:15.450 --> 00:04:18.289 align:start position:0% stores locally on their mobile phones and<00:04:15.750> then<00:04:16.440> the<00:04:17.070> central<00:04:17.580> server<00:04:17.940> at<00:04:18.150> Google 00:04:18.289 --> 00:04:18.299 align:start position:0% and then the central server at Google 00:04:18.299 --> 00:04:21.320 align:start position:0% and then the central server at Google are<00:04:18.780> a<00:04:19.020> broken<00:04:19.500> coordinates<00:04:20.130> these<00:04:20.700> different 00:04:21.320 --> 00:04:21.330 align:start position:0% are a broken coordinates these different 00:04:21.330 --> 00:04:25.820 align:start position:0% are a broken coordinates these different local<00:04:22.049> devices<00:04:22.650> to<00:04:23.450> collectively<00:04:24.620> train<00:04:25.620> a 00:04:25.820 --> 00:04:25.830 align:start position:0% local devices to collectively train a 00:04:25.830 --> 00:04:27.980 align:start position:0% local devices to collectively train a machine<00:04:25.950> any<00:04:26.280> model<00:04:26.730> in<00:04:27.090> this<00:04:27.300> distributed 00:04:27.980 --> 00:04:27.990 align:start position:0% machine any model in this distributed 00:04:27.990 --> 00:04:31.010 align:start position:0% machine any model in this distributed fashion<00:04:28.550> so<00:04:29.550> in<00:04:29.850> this<00:04:29.940> case<00:04:30.210> with<00:04:30.780> ready 00:04:31.010 --> 00:04:31.020 align:start position:0% fashion so in this case with ready 00:04:31.020 --> 00:04:34.330 align:start position:0% fashion so in this case with ready tyranny<00:04:31.530> it<00:04:31.740> takes<00:04:31.980> an<00:04:32.250> iterative<00:04:32.700> approach 00:04:34.330 --> 00:04:34.340 align:start position:0% tyranny it takes an iterative approach 00:04:34.340 --> 00:04:40.880 align:start position:0% tyranny it takes an iterative approach where<00:04:35.340> in<00:04:35.940> run<00:04:36.450> time<00:04:36.480> it<00:04:37.380> has<00:04:39.590> very<00:04:40.590> high 00:04:40.880 --> 00:04:40.890 align:start position:0% where in run time it has very high 00:04:40.890 --> 00:04:44.110 align:start position:0% where in run time it has very high bridge<00:04:41.670> in<00:04:41.820> a<00:04:41.970> fleece<00:04:42.210> global<00:04:42.690> global<00:04:43.230> model 00:04:44.110 --> 00:04:44.120 align:start position:0% bridge in a fleece global global model 00:04:44.120 --> 00:04:48.110 align:start position:0% bridge in a fleece global global model that's<00:04:45.740> that<00:04:46.740> is<00:04:46.860> being<00:04:47.070> trained<00:04:47.310> and<00:04:47.610> then 00:04:48.110 --> 00:04:48.120 align:start position:0% that's that is being trained and then 00:04:48.120 --> 00:04:51.170 align:start position:0% that's that is being trained and then this<00:04:48.300> model<00:04:48.750> is<00:04:48.870> distributed<00:04:49.530> to<00:04:49.770> the<00:04:50.760> local 00:04:51.170 --> 00:04:51.180 align:start position:0% this model is distributed to the local 00:04:51.180 --> 00:04:55.790 align:start position:0% this model is distributed to the local devices<00:04:51.930> and<00:04:53.030> and<00:04:54.030> then<00:04:54.600> each<00:04:54.870> local<00:04:55.410> device 00:04:55.790 --> 00:04:55.800 align:start position:0% devices and and then each local device 00:04:55.800 --> 00:05:00.560 align:start position:0% devices and and then each local device uses<00:04:56.340> its<00:04:56.520> own<00:04:56.790> local<00:04:57.750> data<00:04:57.930> to<00:04:58.320> try<00:04:58.800> to<00:04:59.570> update 00:05:00.560 --> 00:05:00.570 align:start position:0% uses its own local data to try to update 00:05:00.570 --> 00:05:03.680 align:start position:0% uses its own local data to try to update this<00:05:01.200> model<00:05:01.880> gives<00:05:02.880> more<00:05:03.120> we<00:05:03.270> can't<00:05:03.510> really 00:05:03.680 --> 00:05:03.690 align:start position:0% this model gives more we can't really 00:05:03.690 --> 00:05:06.110 align:start position:0% this model gives more we can't really update<00:05:04.170> and<00:05:04.470> then<00:05:04.980> the<00:05:05.160> sweetie<00:05:05.520> updates<00:05:05.880> is 00:05:06.110 --> 00:05:06.120 align:start position:0% update and then the sweetie updates is 00:05:06.120 --> 00:05:09.230 align:start position:0% update and then the sweetie updates is then<00:05:06.480> sent<00:05:07.080> back<00:05:07.140> to<00:05:07.320> the<00:05:07.860> central<00:05:08.190> server<00:05:08.490> to 00:05:09.230 --> 00:05:09.240 align:start position:0% then sent back to the central server to 00:05:09.240 --> 00:05:12.140 align:start position:0% then sent back to the central server to then<00:05:09.660> the<00:05:10.620> listener<00:05:10.980> terminal<00:05:11.400> advocate 00:05:12.140 --> 00:05:12.150 align:start position:0% then the listener terminal advocate 00:05:12.150 --> 00:05:15.830 align:start position:0% then the listener terminal advocate studies<00:05:12.660> with<00:05:13.410> the<00:05:13.500> updates<00:05:13.890> to<00:05:14.160> the<00:05:15.060> create 00:05:15.830 --> 00:05:15.840 align:start position:0% studies with the updates to the create 00:05:15.840 --> 00:05:17.450 align:start position:0% studies with the updates to the create to<00:05:16.050> the<00:05:16.200> next<00:05:16.440> version<00:05:16.740> of<00:05:16.770> the<00:05:16.950> mother<00:05:17.130> and 00:05:17.450 --> 00:05:17.460 align:start position:0% to the next version of the mother and 00:05:17.460 --> 00:05:23.150 align:start position:0% to the next version of the mother and then<00:05:17.790> this<00:05:18.110> continues<00:05:20.180> so<00:05:21.180> in<00:05:21.480> this<00:05:21.750> way<00:05:22.160> the 00:05:23.150 --> 00:05:23.160 align:start position:0% then this continues so in this way the 00:05:23.160 --> 00:05:27.320 align:start position:0% then this continues so in this way the advantage<00:05:24.030> is<00:05:24.270> that<00:05:24.300> the<00:05:25.790> each<00:05:26.790> user's<00:05:27.180> data 00:05:27.320 --> 00:05:27.330 align:start position:0% advantage is that the each user's data 00:05:27.330 --> 00:05:29.150 align:start position:0% advantage is that the each user's data is<00:05:27.630> stored<00:05:27.840> locally<00:05:28.110> is<00:05:28.440> not<00:05:28.710> actually 00:05:29.150 --> 00:05:29.160 align:start position:0% is stored locally is not actually 00:05:29.160 --> 00:05:31.760 align:start position:0% is stored locally is not actually uploaded<00:05:29.670> to<00:05:30.600> the<00:05:30.720> cloud<00:05:30.840> out<00:05:31.200> to<00:05:31.350> the<00:05:31.440> central 00:05:31.760 --> 00:05:31.770 align:start position:0% uploaded to the cloud out to the central 00:05:31.770 --> 00:05:35.480 align:start position:0% uploaded to the cloud out to the central server<00:05:32.070> but<00:05:32.670> still<00:05:33.680> in<00:05:34.680> this<00:05:34.890> case<00:05:35.100> it<00:05:35.310> still 00:05:35.480 --> 00:05:35.490 align:start position:0% server but still in this case it still 00:05:35.490 --> 00:05:38.150 align:start position:0% server but still in this case it still needs<00:05:35.730> as<00:05:35.910> inter<00:05:36.150> server<00:05:36.420> to<00:05:36.570> coordinate<00:05:37.200> this 00:05:38.150 --> 00:05:38.160 align:start position:0% needs as inter server to coordinate this 00:05:38.160 --> 00:05:41.810 align:start position:0% needs as inter server to coordinate this ferry<00:05:38.910> terminal<00:05:39.830> and<00:05:40.830> there<00:05:41.100> are<00:05:41.250> of<00:05:41.490> course<00:05:41.520> a 00:05:41.810 --> 00:05:41.820 align:start position:0% ferry terminal and there are of course a 00:05:41.820 --> 00:05:43.520 align:start position:0% ferry terminal and there are of course a number<00:05:41.850> of<00:05:42.120> challenges<00:05:42.660> about<00:05:43.229> which<00:05:43.350> might 00:05:43.520 --> 00:05:43.530 align:start position:0% number of challenges about which might 00:05:43.530 --> 00:05:46.460 align:start position:0% number of challenges about which might be<00:05:43.650> use<00:05:43.860> this<00:05:44.280> type<00:05:44.550> of<00:05:44.580> approach<00:05:44.970> to<00:05:45.470> address 00:05:46.460 --> 00:05:46.470 align:start position:0% be use this type of approach to address 00:05:46.470 --> 00:05:48.590 align:start position:0% be use this type of approach to address the<00:05:46.650> problem<00:05:46.950> that<00:05:47.160> I<00:05:47.250> just<00:05:47.460> mentioned<00:05:47.700> for 00:05:48.590 --> 00:05:48.600 align:start position:0% the problem that I just mentioned for 00:05:48.600 --> 00:05:50.360 align:start position:0% the problem that I just mentioned for example<00:05:48.630> in<00:05:49.200> this<00:05:49.290> case<00:05:49.530> when<00:05:49.800> the<00:05:49.830> banks 00:05:50.360 --> 00:05:50.370 align:start position:0% example in this case when the banks 00:05:50.370 --> 00:05:55.610 align:start position:0% example in this case when the banks wants<00:05:50.669> to<00:05:52.070> collaborate<00:05:53.990> the<00:05:54.990> questions<00:05:55.380> and 00:05:55.610 --> 00:05:55.620 align:start position:0% wants to collaborate the questions and 00:05:55.620 --> 00:05:56.960 align:start position:0% wants to collaborate the questions and one<00:05:55.919> question<00:05:56.190> is<00:05:56.220> the<00:05:56.400> who<00:05:56.550> should<00:05:56.790> actually 00:05:56.960 --> 00:05:56.970 align:start position:0% one question is the who should actually 00:05:56.970 --> 00:05:58.820 align:start position:0% one question is the who should actually hooks<00:05:57.330> the<00:05:57.479> center<00:05:57.750> server<00:05:57.960> ideally<00:05:58.470> you 00:05:58.820 --> 00:05:58.830 align:start position:0% hooks the center server ideally you 00:05:58.830 --> 00:06:00.680 align:start position:0% hooks the center server ideally you don't<00:05:58.979> want<00:05:59.190> to<00:05:59.280> rely<00:05:59.520> on<00:05:59.550> using<00:06:00.030> be<00:06:00.120> trusted 00:06:00.680 --> 00:06:00.690 align:start position:0% don't want to rely on using be trusted 00:06:00.690 --> 00:06:02.180 align:start position:0% don't want to rely on using be trusted so<00:06:00.840> you<00:06:01.020> don't<00:06:01.200> want<00:06:01.320> to<00:06:01.380> actually<00:06:01.530> have<00:06:01.710> and 00:06:02.180 --> 00:06:02.190 align:start position:0% so you don't want to actually have and 00:06:02.190 --> 00:06:03.950 align:start position:0% so you don't want to actually have and you<00:06:02.400> are<00:06:02.430> hosting<00:06:02.940> the<00:06:03.120> central<00:06:03.419> server<00:06:03.630> and 00:06:03.950 --> 00:06:03.960 align:start position:0% you are hosting the central server and 00:06:03.960 --> 00:06:06.469 align:start position:0% you are hosting the central server and also<00:06:04.590> this<00:06:04.710> is<00:06:04.830> a<00:06:04.860> new<00:06:04.979> survey<00:06:05.310> by<00:06:05.520> rely<00:06:06.450> on 00:06:06.469 --> 00:06:06.479 align:start position:0% also this is a new survey by rely on 00:06:06.479 --> 00:06:08.300 align:start position:0% also this is a new survey by rely on accessibility<00:06:07.110> and<00:06:07.530> creates<00:06:07.830> each<00:06:08.100> year 00:06:08.300 --> 00:06:08.310 align:start position:0% accessibility and creates each year 00:06:08.310 --> 00:06:10.580 align:start position:0% accessibility and creates each year spreads<00:06:08.640> at<00:06:08.820> home<00:06:09.030> if<00:06:09.240> they<00:06:09.660> became<00:06:10.020> malicious 00:06:10.580 --> 00:06:10.590 align:start position:0% spreads at home if they became malicious 00:06:10.590 --> 00:06:13.670 align:start position:0% spreads at home if they became malicious are<00:06:10.979> taken<00:06:11.700> may<00:06:12.240> also<00:06:12.390> give<00:06:12.870> the<00:06:13.410> single 00:06:13.670 --> 00:06:13.680 align:start position:0% are taken may also give the single 00:06:13.680 --> 00:06:20.750 align:start position:0% are taken may also give the single server<00:06:13.979> some<00:06:16.010> some<00:06:17.010> unfair<00:06:17.370> advantage 00:06:20.750 --> 00:06:20.760 align:start position:0% 00:06:20.760 --> 00:06:24.090 align:start position:0% so<00:06:21.760> in<00:06:22.120> contrast<00:06:22.480> to<00:06:22.960> this<00:06:23.230> family<00:06:23.710> tyranny 00:06:24.090 --> 00:06:24.100 align:start position:0% so in contrast to this family tyranny 00:06:24.100 --> 00:06:26.820 align:start position:0% so in contrast to this family tyranny motto<00:06:24.400> which<00:06:25.120> realises<00:06:26.080> that<00:06:26.230> your<00:06:26.440> server<00:06:26.620> to 00:06:26.820 --> 00:06:26.830 align:start position:0% motto which realises that your server to 00:06:26.830 --> 00:06:29.760 align:start position:0% motto which realises that your server to coordinate<00:06:27.310> distribute<00:06:28.090> the<00:06:28.180> devices<00:06:28.770> to 00:06:29.760 --> 00:06:29.770 align:start position:0% coordinate distribute the devices to 00:06:29.770 --> 00:06:32.600 align:start position:0% coordinate distribute the devices to together<00:06:30.580> train<00:06:30.910> machine<00:06:31.720> is<00:06:31.810> our<00:06:32.020> winner 00:06:32.600 --> 00:06:32.610 align:start position:0% together train machine is our winner 00:06:32.610 --> 00:06:35.220 align:start position:0% together train machine is our winner distributed<00:06:33.610> way<00:06:33.730> and<00:06:34.540> that<00:06:34.690> alternative 00:06:35.220 --> 00:06:35.230 align:start position:0% distributed way and that alternative 00:06:35.230 --> 00:06:36.930 align:start position:0% distributed way and that alternative solution<00:06:35.710> is<00:06:35.980> was<00:06:36.400> had<00:06:36.640> a<00:06:36.670> peer-to-peer 00:06:36.930 --> 00:06:36.940 align:start position:0% solution is was had a peer-to-peer 00:06:36.940 --> 00:06:40.110 align:start position:0% solution is was had a peer-to-peer solution<00:06:37.780> in<00:06:37.960> this<00:06:38.080> case<00:06:38.880> essentially<00:06:39.880> the 00:06:40.110 --> 00:06:40.120 align:start position:0% solution in this case essentially the 00:06:40.120 --> 00:06:42.060 align:start position:0% solution in this case essentially the different<00:06:40.480> devices<00:06:40.780> form<00:06:41.710> a<00:06:41.860> peer-to-peer 00:06:42.060 --> 00:06:42.070 align:start position:0% different devices form a peer-to-peer 00:06:42.070 --> 00:06:43.860 align:start position:0% different devices form a peer-to-peer network<00:06:42.190> if<00:06:42.820> there<00:06:42.940> is<00:06:43.000> no<00:06:43.300> central<00:06:43.720> server 00:06:43.860 --> 00:06:43.870 align:start position:0% network if there is no central server 00:06:43.870 --> 00:06:48.990 align:start position:0% network if there is no central server and<00:06:45.270> essentially<00:06:46.890> the<00:06:47.890> the<00:06:48.160> different 00:06:48.990 --> 00:06:49.000 align:start position:0% and essentially the the different 00:06:49.000 --> 00:06:51.270 align:start position:0% and essentially the the different devices<00:06:49.240> will<00:06:49.780> communicate<00:06:50.110> through<00:06:51.100> this 00:06:51.270 --> 00:06:51.280 align:start position:0% devices will communicate through this 00:06:51.280 --> 00:06:54.090 align:start position:0% devices will communicate through this peer-to-peer<00:06:51.610> network<00:06:52.290> with<00:06:53.290> its<00:06:53.620> neighbors 00:06:54.090 --> 00:06:54.100 align:start position:0% peer-to-peer network with its neighbors 00:06:54.100 --> 00:06:57.270 align:start position:0% peer-to-peer network with its neighbors and<00:06:54.460> then<00:06:55.060> through<00:06:56.020> again<00:06:56.530> an<00:06:56.860> interesting 00:06:57.270 --> 00:06:57.280 align:start position:0% and then through again an interesting 00:06:57.280 --> 00:07:03.260 align:start position:0% and then through again an interesting approach<00:06:57.550> to<00:06:57.970> try<00:06:58.660> to<00:06:59.730> together<00:07:01.260> updates<00:07:02.260> this 00:07:03.260 --> 00:07:03.270 align:start position:0% approach to try to together updates this 00:07:03.270 --> 00:07:07.050 align:start position:0% approach to try to together updates this much<00:07:04.270> mini<00:07:04.540> model<00:07:04.930> to<00:07:05.590> utilize<00:07:06.040> the<00:07:06.670> local 00:07:07.050 --> 00:07:07.060 align:start position:0% much mini model to utilize the local 00:07:07.060 --> 00:07:09.090 align:start position:0% much mini model to utilize the local data<00:07:07.210> on<00:07:07.390> the<00:07:07.480> different<00:07:07.810> devices<00:07:08.020> to<00:07:08.470> train 00:07:09.090 --> 00:07:09.100 align:start position:0% data on the different devices to train 00:07:09.100 --> 00:07:12.300 align:start position:0% data on the different devices to train the<00:07:09.810> to<00:07:10.810> train<00:07:11.050> the<00:07:11.170> sandwich<00:07:11.590> minimum<00:07:11.980> I 00:07:12.300 --> 00:07:12.310 align:start position:0% the to train the sandwich minimum I 00:07:12.310 --> 00:07:16.740 align:start position:0% the to train the sandwich minimum I would<00:07:14.760> advantage<00:07:15.760> of<00:07:15.880> this<00:07:16.030> approach<00:07:16.210> is<00:07:16.720> that 00:07:16.740 --> 00:07:16.750 align:start position:0% would advantage of this approach is that 00:07:16.750 --> 00:07:19.620 align:start position:0% would advantage of this approach is that in<00:07:17.680> the<00:07:17.860> city<00:07:18.160> we<00:07:18.430> don't<00:07:18.610> need<00:07:18.730> to<00:07:18.880> trust<00:07:19.150> any 00:07:19.620 --> 00:07:19.630 align:start position:0% in the city we don't need to trust any 00:07:19.630 --> 00:07:21.630 align:start position:0% in the city we don't need to trust any central<00:07:20.080> server<00:07:20.320> because<00:07:20.650> there's<00:07:20.890> simply<00:07:21.400> no 00:07:21.630 --> 00:07:21.640 align:start position:0% central server because there's simply no 00:07:21.640 --> 00:07:23.940 align:start position:0% central server because there's simply no central<00:07:22.000> server<00:07:22.030> however<00:07:22.960> the<00:07:23.710> challenge 00:07:23.940 --> 00:07:23.950 align:start position:0% central server however the challenge 00:07:23.950 --> 00:07:28.520 align:start position:0% central server however the challenge here<00:07:24.340> is<00:07:24.370> as<00:07:24.730> in<00:07:25.060> dispute<00:07:25.600> appear<00:07:27.240> the 00:07:28.520 --> 00:07:28.530 align:start position:0% here is as in dispute appear the 00:07:28.530 --> 00:07:31.230 align:start position:0% here is as in dispute appear the significant<00:07:29.530> results<00:07:30.220> and<00:07:30.850> for<00:07:31.120> our 00:07:31.230 --> 00:07:31.240 align:start position:0% significant results and for our 00:07:31.240 --> 00:07:34.170 align:start position:0% significant results and for our communication<00:07:32.020> as<00:07:32.230> on<00:07:32.530> and<00:07:32.830> especially<00:07:33.820> when 00:07:34.170 --> 00:07:34.180 align:start position:0% communication as on and especially when 00:07:34.180 --> 00:07:37.470 align:start position:0% communication as on and especially when Anna<00:07:34.390> Raph<00:07:34.800> the<00:07:35.800> client<00:07:36.220> becomes<00:07:37.000> flourished 00:07:37.470 --> 00:07:37.480 align:start position:0% Anna Raph the client becomes flourished 00:07:37.480 --> 00:07:40.330 align:start position:0% Anna Raph the client becomes flourished and<00:07:37.660> also<00:07:38.440> there<00:07:39.190> is<00:07:39.220> more<00:07:39.610> privacy 00:07:40.330 --> 00:07:40.340 align:start position:0% and also there is more privacy 00:07:40.340 --> 00:07:46.090 align:start position:0% and also there is more privacy challenges<00:07:41.240> Elizabeth<00:07:43.750> so<00:07:44.750> in<00:07:45.650> our<00:07:45.830> recent 00:07:46.090 --> 00:07:46.100 align:start position:0% challenges Elizabeth so in our recent 00:07:46.100 --> 00:07:47.830 align:start position:0% challenges Elizabeth so in our recent work<00:07:46.370> here<00:07:46.670> we<00:07:46.790> proposed<00:07:47.120> a<00:07:47.150> new<00:07:47.390> paradigm 00:07:47.830 --> 00:07:47.840 align:start position:0% work here we proposed a new paradigm 00:07:47.840 --> 00:07:51.910 align:start position:0% work here we proposed a new paradigm that<00:07:47.870> we<00:07:48.200> call<00:07:48.610> decentralize<00:07:49.610> the<00:07:49.640> 2020<00:07:50.920> with 00:07:51.910 --> 00:07:51.920 align:start position:0% that we call decentralize the 2020 with 00:07:51.920 --> 00:07:54.490 align:start position:0% that we call decentralize the 2020 with where<00:07:52.310> we<00:07:52.550> combine<00:07:52.760> is<00:07:53.480> into<00:07:53.810> the<00:07:53.900> best<00:07:54.140> of 00:07:54.490 --> 00:07:54.500 align:start position:0% where we combine is into the best of 00:07:54.500 --> 00:07:59.110 align:start position:0% where we combine is into the best of both<00:07:54.830> worlds<00:07:56.050> both<00:07:57.100> giving<00:07:58.100> and<00:07:58.130> this 00:07:59.110 --> 00:07:59.120 align:start position:0% both worlds both giving and this 00:07:59.120 --> 00:08:01.930 align:start position:0% both worlds both giving and this virtualized<00:07:59.800> setting<00:08:00.800> while<00:08:01.430> we<00:08:01.520> don't<00:08:01.700> rely 00:08:01.930 --> 00:08:01.940 align:start position:0% virtualized setting while we don't rely 00:08:01.940 --> 00:08:03.790 align:start position:0% virtualized setting while we don't rely on<00:08:01.970> a<00:08:02.300> nice<00:08:02.480> central<00:08:03.230> server 00:08:03.790 --> 00:08:03.800 align:start position:0% on a nice central server 00:08:03.800 --> 00:08:07.270 align:start position:0% on a nice central server but<00:08:04.160> also<00:08:04.400> at<00:08:04.880> the<00:08:05.000> same<00:08:05.180> time<00:08:05.950> we<00:08:06.950> can<00:08:07.130> achieve 00:08:07.270 --> 00:08:07.280 align:start position:0% but also at the same time we can achieve 00:08:07.280 --> 00:08:09.910 align:start position:0% but also at the same time we can achieve much<00:08:07.820> better<00:08:07.930> efficiency<00:08:08.930> and<00:08:09.440> dementia 00:08:09.910 --> 00:08:09.920 align:start position:0% much better efficiency and dementia 00:08:09.920 --> 00:08:12.390 align:start position:0% much better efficiency and dementia stronger<00:08:10.310> privacy<00:08:10.790> protection<00:08:11.270> than<00:08:11.900> the 00:08:12.390 --> 00:08:12.400 align:start position:0% stronger privacy protection than the 00:08:12.400 --> 00:08:15.670 align:start position:0% stronger privacy protection than the peer<00:08:13.400> to<00:08:13.550> peer<00:08:13.730> said<00:08:13.970> and<00:08:14.210> the<00:08:14.990> way<00:08:15.140> we<00:08:15.320> do<00:08:15.500> that 00:08:15.670 --> 00:08:15.680 align:start position:0% peer to peer said and the way we do that 00:08:15.680 --> 00:08:17.980 align:start position:0% peer to peer said and the way we do that is<00:08:15.950> the<00:08:16.520> instead<00:08:16.820> of<00:08:16.940> using<00:08:17.330> as<00:08:17.570> intrusive<00:08:17.780> a 00:08:17.980 --> 00:08:17.990 align:start position:0% is the instead of using as intrusive a 00:08:17.990 --> 00:08:21.100 align:start position:0% is the instead of using as intrusive a wastage<00:08:18.500> we<00:08:18.680> use<00:08:18.920> a<00:08:19.640> blockchain<00:08:20.270> smacking 00:08:21.100 --> 00:08:21.110 align:start position:0% wastage we use a blockchain smacking 00:08:21.110 --> 00:08:23.020 align:start position:0% wastage we use a blockchain smacking telephone<00:08:21.620> to<00:08:22.130> coordinate<00:08:22.760> this 00:08:23.020 --> 00:08:23.030 align:start position:0% telephone to coordinate this 00:08:23.030 --> 00:08:25.090 align:start position:0% telephone to coordinate this distribution<00:08:23.450> meaning<00:08:24.170> across<00:08:24.890> the 00:08:25.090 --> 00:08:25.100 align:start position:0% distribution meaning across the 00:08:25.100 --> 00:08:27.460 align:start position:0% distribution meaning across the different<00:08:25.660> local<00:08:26.660> devices<00:08:27.260> in<00:08:27.440> different 00:08:27.460 --> 00:08:27.470 align:start position:0% different local devices in different 00:08:27.470 --> 00:08:29.860 align:start position:0% different local devices in different coins<00:08:27.920> that<00:08:28.910> would<00:08:29.090> you<00:08:29.180> host<00:08:29.390> the<00:08:29.660> the 00:08:29.860 --> 00:08:29.870 align:start position:0% coins that would you host the the 00:08:29.870 --> 00:08:33.840 align:start position:0% coins that would you host the the pocketing 00:08:33.840 --> 00:08:33.850 align:start position:0% 00:08:33.850 --> 00:08:37.200 align:start position:0% using<00:08:34.690> this<00:08:35.140> new<00:08:35.500> paradise<00:08:36.010> we<00:08:36.700> achieve<00:08:37.120> a 00:08:37.200 --> 00:08:37.210 align:start position:0% using this new paradise we achieve a 00:08:37.210 --> 00:08:38.670 align:start position:0% using this new paradise we achieve a number<00:08:37.330> of<00:08:37.600> advantages 00:08:38.670 --> 00:08:38.680 align:start position:0% number of advantages 00:08:38.680 --> 00:08:41.430 align:start position:0% number of advantages once<00:08:39.130> again<00:08:39.419> we<00:08:40.419> ended<00:08:40.840> with<00:08:40.870> the<00:08:41.050> centralized 00:08:41.430 --> 00:08:41.440 align:start position:0% once again we ended with the centralized 00:08:41.440 --> 00:08:43.230 align:start position:0% once again we ended with the centralized and<00:08:41.680> the<00:08:41.979> secularization<00:08:42.340> so<00:08:42.789> we<00:08:42.880> do<00:08:43.000> need<00:08:43.090> to 00:08:43.230 --> 00:08:43.240 align:start position:0% and the secularization so we do need to 00:08:43.240 --> 00:08:46.230 align:start position:0% and the secularization so we do need to trust<00:08:43.479> and<00:08:44.110> listen<00:08:44.470> to<00:08:44.560> party<00:08:45.030> for<00:08:46.030> the 00:08:46.230 --> 00:08:46.240 align:start position:0% trust and listen to party for the 00:08:46.240 --> 00:08:49.680 align:start position:0% trust and listen to party for the operations<00:08:46.780> and<00:08:47.110> against<00:08:48.450> much<00:08:49.450> more 00:08:49.680 --> 00:08:49.690 align:start position:0% operations and against much more 00:08:49.690 --> 00:08:52.530 align:start position:0% operations and against much more efficient<00:08:50.230> and<00:08:50.760> community<00:08:51.760> scale<00:08:52.000> to<00:08:52.510> large 00:08:52.530 --> 00:08:52.540 align:start position:0% efficient and community scale to large 00:08:52.540 --> 00:08:55.290 align:start position:0% efficient and community scale to large number<00:08:53.170> of<00:08:53.200> participants<00:08:54.040> compared<00:08:54.850> to<00:08:55.060> the 00:08:55.290 --> 00:08:55.300 align:start position:0% number of participants compared to the 00:08:55.300 --> 00:08:57.390 align:start position:0% number of participants compared to the peer-to-peer<00:08:55.510> solution<00:08:56.260> and<00:08:56.860> we<00:08:57.160> can<00:08:57.280> achieve 00:08:57.390 --> 00:08:57.400 align:start position:0% peer-to-peer solution and we can achieve 00:08:57.400 --> 00:08:59.190 align:start position:0% peer-to-peer solution and we can achieve we're<00:08:57.790> high<00:08:57.970> utility<00:08:58.270> essentially<00:08:59.050> the 00:08:59.190 --> 00:08:59.200 align:start position:0% we're high utility essentially the 00:08:59.200 --> 00:09:01.020 align:start position:0% we're high utility essentially the accuracy<00:08:59.680> can<00:08:59.890> be<00:08:59.950> comparable<00:09:00.670> to<00:09:00.850> the 00:09:01.020 --> 00:09:01.030 align:start position:0% accuracy can be comparable to the 00:09:01.030 --> 00:09:03.750 align:start position:0% accuracy can be comparable to the centralized<00:09:01.600> model<00:09:01.800> and<00:09:02.800> we<00:09:03.070> achieve<00:09:03.370> strong 00:09:03.750 --> 00:09:03.760 align:start position:0% centralized model and we achieve strong 00:09:03.760 --> 00:09:06.710 align:start position:0% centralized model and we achieve strong privacy<00:09:04.210> where<00:09:04.840> we<00:09:04.990> can<00:09:05.200> protect<00:09:05.650> the<00:09:06.070> clients 00:09:06.710 --> 00:09:06.720 align:start position:0% privacy where we can protect the clients 00:09:06.720 --> 00:09:10.290 align:start position:0% privacy where we can protect the clients data<00:09:07.720> privacy<00:09:08.140> and<00:09:08.260> by<00:09:09.250> using<00:09:09.430> drugs<00:09:09.940> an 00:09:10.290 --> 00:09:10.300 align:start position:0% data privacy and by using drugs an 00:09:10.300 --> 00:09:12.690 align:start position:0% data privacy and by using drugs an entire<00:09:10.630> platform<00:09:11.110> that<00:09:11.440> wasn't<00:09:11.770> me<00:09:12.220> incentive 00:09:12.690 --> 00:09:12.700 align:start position:0% entire platform that wasn't me incentive 00:09:12.700 --> 00:09:16.860 align:start position:0% entire platform that wasn't me incentive method 00:09:16.860 --> 00:09:16.870 align:start position:0% 00:09:16.870 --> 00:09:19.650 align:start position:0% so<00:09:17.440> now<00:09:17.590> let's<00:09:17.830> take<00:09:18.100> a<00:09:18.130> look<00:09:19.090> at<00:09:19.240> how<00:09:19.450> this 00:09:19.650 --> 00:09:19.660 align:start position:0% so now let's take a look at how this 00:09:19.660 --> 00:09:21.960 align:start position:0% so now let's take a look at how this approach<00:09:20.140> works<00:09:20.440> so<00:09:21.130> first<00:09:21.370> let<00:09:21.610> me<00:09:21.640> give<00:09:21.850> you 00:09:21.960 --> 00:09:21.970 align:start position:0% approach works so first let me give you 00:09:21.970 --> 00:09:24.990 align:start position:0% approach works so first let me give you a<00:09:22.000> strongman<00:09:22.480> solution<00:09:23.490> whereas<00:09:24.490> emissions 00:09:24.990 --> 00:09:25.000 align:start position:0% a strongman solution whereas emissions 00:09:25.000 --> 00:09:27.210 align:start position:0% a strongman solution whereas emissions want<00:09:25.930> me<00:09:26.020> to<00:09:26.140> achieve<00:09:26.260> this<00:09:26.560> decentralize<00:09:27.190> the 00:09:27.210 --> 00:09:27.220 align:start position:0% want me to achieve this decentralize the 00:09:27.220 --> 00:09:29.370 align:start position:0% want me to achieve this decentralize the federal<00:09:28.060> sovereignty<00:09:28.240> as<00:09:28.870> we<00:09:29.050> use<00:09:29.200> of 00:09:29.370 --> 00:09:29.380 align:start position:0% federal sovereignty as we use of 00:09:29.380 --> 00:09:31.890 align:start position:0% federal sovereignty as we use of lotteries<00:09:29.740> my<00:09:29.920> contact<00:09:30.340> upon<00:09:30.700> to<00:09:31.150> coordinates 00:09:31.890 --> 00:09:31.900 align:start position:0% lotteries my contact upon to coordinates 00:09:31.900 --> 00:09:34.800 align:start position:0% lotteries my contact upon to coordinates these<00:09:32.410> different<00:09:32.890> clients<00:09:33.580> for<00:09:34.210> training<00:09:34.660> the 00:09:34.800 --> 00:09:34.810 align:start position:0% these different clients for training the 00:09:34.810 --> 00:09:36.840 align:start position:0% these different clients for training the marina<00:09:35.230> model<00:09:35.530> isn't<00:09:35.740> a<00:09:36.010> distributed 00:09:36.840 --> 00:09:36.850 align:start position:0% marina model isn't a distributed 00:09:36.850 --> 00:09:37.800 align:start position:0% marina model isn't a distributed decentralized<00:09:37.360> way 00:09:37.800 --> 00:09:37.810 align:start position:0% decentralized way 00:09:37.810 --> 00:09:40.350 align:start position:0% decentralized way so<00:09:38.410> one<00:09:38.710> a<00:09:38.950> stronger<00:09:39.520> approach<00:09:39.790> is<00:09:40.150> that<00:09:40.180> we 00:09:40.350 --> 00:09:40.360 align:start position:0% so one a stronger approach is that we 00:09:40.360 --> 00:09:42.750 align:start position:0% so one a stronger approach is that we can<00:09:40.570> simply<00:09:40.960> set<00:09:41.140> have<00:09:41.320> asthma<00:09:42.160> contracts 00:09:42.750 --> 00:09:42.760 align:start position:0% can simply set have asthma contracts 00:09:42.760 --> 00:09:45.030 align:start position:0% can simply set have asthma contracts under<00:09:43.150> party<00:09:43.480> platform<00:09:43.930> which<00:09:44.410> performs<00:09:44.920> a 00:09:45.030 --> 00:09:45.040 align:start position:0% under party platform which performs a 00:09:45.040 --> 00:09:46.440 align:start position:0% under party platform which performs a mother<00:09:45.220> aggregation<00:09:45.820> as<00:09:45.910> I<00:09:46.090> mentioned 00:09:46.440 --> 00:09:46.450 align:start position:0% mother aggregation as I mentioned 00:09:46.450 --> 00:09:49.080 align:start position:0% mother aggregation as I mentioned earlier<00:09:46.840> in<00:09:47.680> the<00:09:47.950> feathers<00:09:48.340> it's<00:09:48.610> been 00:09:49.080 --> 00:09:49.090 align:start position:0% earlier in the feathers it's been 00:09:49.090 --> 00:09:49.710 align:start position:0% earlier in the feathers it's been exciting 00:09:49.710 --> 00:09:49.720 align:start position:0% exciting 00:09:49.720 --> 00:09:51.690 align:start position:0% exciting where<00:09:50.080> essentially<00:09:50.470> this<00:09:50.890> a<00:09:51.130> modification 00:09:51.690 --> 00:09:51.700 align:start position:0% where essentially this a modification 00:09:51.700 --> 00:09:53.970 align:start position:0% where essentially this a modification smart<00:09:52.210> contract<00:09:52.570> will<00:09:52.750> perform<00:09:53.080> what<00:09:53.380> the 00:09:53.970 --> 00:09:53.980 align:start position:0% smart contract will perform what the 00:09:53.980 --> 00:09:56.610 align:start position:0% smart contract will perform what the central<00:09:54.220> server<00:09:54.490> would<00:09:54.610> do<00:09:54.790> down<00:09:55.150> life<00:09:55.620> but 00:09:56.610 --> 00:09:56.620 align:start position:0% central server would do down life but 00:09:56.620 --> 00:10:01.590 align:start position:0% central server would do down life but however<00:09:58.110> so<00:09:59.110> the<00:09:59.230> child<00:09:59.760> in<00:10:00.760> this<00:10:00.850> case<00:10:01.120> it<00:10:01.420> can 00:10:01.590 --> 00:10:01.600 align:start position:0% however so the child in this case it can 00:10:01.600 --> 00:10:05.400 align:start position:0% however so the child in this case it can be<00:10:02.010> very<00:10:03.010> efficient<00:10:03.720> and<00:10:04.720> also<00:10:05.020> provides 00:10:05.400 --> 00:10:05.410 align:start position:0% be very efficient and also provides 00:10:05.410 --> 00:10:07.410 align:start position:0% be very efficient and also provides strong<00:10:05.890> integrity<00:10:06.550> guarantees<00:10:06.970> even 00:10:07.410 --> 00:10:07.420 align:start position:0% strong integrity guarantees even 00:10:07.420 --> 00:10:09.870 align:start position:0% strong integrity guarantees even industry<00:10:08.170> centralized<00:10:08.590> the<00:10:08.890> city<00:10:09.100> where<00:10:09.730> we 00:10:09.870 --> 00:10:09.880 align:start position:0% industry centralized the city where we 00:10:09.880 --> 00:10:13.050 align:start position:0% industry centralized the city where we don't<00:10:10.090> need<00:10:10.210> to<00:10:10.360> actually<00:10:10.930> rely<00:10:11.850> trusts<00:10:12.850> are 00:10:13.050 --> 00:10:13.060 align:start position:0% don't need to actually rely trusts are 00:10:13.060 --> 00:10:15.390 align:start position:0% don't need to actually rely trusts are at<00:10:13.270> the<00:10:13.360> center<00:10:13.630> server<00:10:13.870> Harvard<00:10:14.770> the<00:10:15.160> China 00:10:15.390 --> 00:10:15.400 align:start position:0% at the center server Harvard the China 00:10:15.400 --> 00:10:17.580 align:start position:0% at the center server Harvard the China here<00:10:15.730> is<00:10:15.880> they<00:10:16.030> using<00:10:16.330> this<00:10:16.480> approach<00:10:16.900> there 00:10:17.580 --> 00:10:17.590 align:start position:0% here is they using this approach there 00:10:17.590 --> 00:10:20.430 align:start position:0% here is they using this approach there can<00:10:17.830> be<00:10:17.860> privacy<00:10:18.610> concerns<00:10:19.150> because<00:10:19.660> on<00:10:20.260> a 00:10:20.430 --> 00:10:20.440 align:start position:0% can be privacy concerns because on a 00:10:20.440 --> 00:10:22.650 align:start position:0% can be privacy concerns because on a typical<00:10:20.650> protein<00:10:21.040> smacking<00:10:21.670> her<00:10:21.820> perform<00:10:22.240> the 00:10:22.650 --> 00:10:22.660 align:start position:0% typical protein smacking her perform the 00:10:22.660 --> 00:10:25.860 align:start position:0% typical protein smacking her perform the protein<00:10:23.020> dinner<00:10:23.230> is<00:10:23.620> public<00:10:24.340> and<00:10:24.580> even<00:10:25.540> though 00:10:25.860 --> 00:10:25.870 align:start position:0% protein dinner is public and even though 00:10:25.870 --> 00:10:29.250 align:start position:0% protein dinner is public and even though in<00:10:26.110> this<00:10:26.200> case<00:10:26.260> the<00:10:27.180> the<00:10:28.180> clients<00:10:28.900> are<00:10:29.080> now 00:10:29.250 --> 00:10:29.260 align:start position:0% in this case the the clients are now 00:10:29.260 --> 00:10:31.560 align:start position:0% in this case the the clients are now sending<00:10:29.560> location<00:10:29.940> to<00:10:30.940> the 00:10:31.560 --> 00:10:31.570 align:start position:0% sending location to the 00:10:31.570 --> 00:10:35.190 align:start position:0% sending location to the got<00:10:31.870> a<00:10:31.980> platform<00:10:32.980> but<00:10:33.700> however<00:10:33.960> even<00:10:34.960> these 00:10:35.190 --> 00:10:35.200 align:start position:0% got a platform but however even these 00:10:35.200 --> 00:10:38.130 align:start position:0% got a platform but however even these screening<00:10:35.650> others<00:10:36.090> for<00:10:37.090> it<00:10:37.360> were<00:10:37.480> updates<00:10:37.930> in 00:10:38.130 --> 00:10:38.140 align:start position:0% screening others for it were updates in 00:10:38.140 --> 00:10:40.400 align:start position:0% screening others for it were updates in motion<00:10:38.410> any<00:10:38.530> models<00:10:38.920> they<00:10:39.400> can<00:10:39.670> see<00:10:39.850> okay 00:10:40.400 --> 00:10:40.410 align:start position:0% motion any models they can see okay 00:10:40.410 --> 00:10:43.460 align:start position:0% motion any models they can see okay information<00:10:41.310> so<00:10:42.089> the<00:10:42.240> question<00:10:42.569> is<00:10:42.779> how<00:10:43.019> can 00:10:43.460 --> 00:10:43.470 align:start position:0% information so the question is how can 00:10:43.470 --> 00:10:49.960 align:start position:0% information so the question is how can we<00:10:43.620> do<00:10:43.889> this<00:10:44.040> in<00:10:46.040> in<00:10:47.040> a<00:10:47.190> more<00:10:47.399> appropriate<00:10:47.819> way 00:10:49.960 --> 00:10:49.970 align:start position:0% we do this in in a more appropriate way 00:10:49.970 --> 00:10:53.780 align:start position:0% we do this in in a more appropriate way so<00:10:50.970> to<00:10:51.420> adjust<00:10:51.779> these<00:10:52.350> challenges<00:10:53.160> we 00:10:53.780 --> 00:10:53.790 align:start position:0% so to adjust these challenges we 00:10:53.790 --> 00:10:56.509 align:start position:0% so to adjust these challenges we proposed<00:10:54.269> pipelines<00:10:54.870> to<00:10:55.829> enable<00:10:56.339> this<00:10:56.459> new 00:10:56.509 --> 00:10:56.519 align:start position:0% proposed pipelines to enable this new 00:10:56.519 --> 00:10:59.019 align:start position:0% proposed pipelines to enable this new paradigm<00:10:56.970> up<00:10:57.389> he<00:10:57.750> centralized<00:10:58.199> effectively 00:10:59.019 --> 00:10:59.029 align:start position:0% paradigm up he centralized effectively 00:10:59.029 --> 00:11:02.030 align:start position:0% paradigm up he centralized effectively happened<00:11:00.029> essentially<00:11:00.449> you<00:11:00.829> utilizes<00:11:01.829> a 00:11:02.030 --> 00:11:02.040 align:start position:0% happened essentially you utilizes a 00:11:02.040 --> 00:11:04.869 align:start position:0% happened essentially you utilizes a number<00:11:02.430> of<00:11:02.670> private<00:11:03.509> secretively 00:11:04.869 --> 00:11:04.879 align:start position:0% number of private secretively 00:11:04.879 --> 00:11:07.759 align:start position:0% number of private secretively technologies<00:11:05.879> including<00:11:06.839> adventure<00:11:07.319> privacy 00:11:07.759 --> 00:11:07.769 align:start position:0% technologies including adventure privacy 00:11:07.769 --> 00:11:09.559 align:start position:0% technologies including adventure privacy where<00:11:08.250> we<00:11:08.430> actually<00:11:08.569> differentially 00:11:09.559 --> 00:11:09.569 align:start position:0% where we actually differentially 00:11:09.569 --> 00:11:14.240 align:start position:0% where we actually differentially comments<00:11:10.139> virtually<00:11:10.800> numata<00:11:11.389> and<00:11:13.250> using 00:11:14.240 --> 00:11:14.250 align:start position:0% comments virtually numata and using 00:11:14.250 --> 00:11:16.790 align:start position:0% comments virtually numata and using secure<00:11:14.639> aggregation<00:11:15.300> where<00:11:15.870> the<00:11:16.290> mother 00:11:16.790 --> 00:11:16.800 align:start position:0% secure aggregation where the mother 00:11:16.800 --> 00:11:18.679 align:start position:0% secure aggregation where the mother updates<00:11:17.310> has<00:11:17.519> been<00:11:17.759> sent<00:11:18.029> to<00:11:18.180> the<00:11:18.420> blockchain 00:11:18.679 --> 00:11:18.689 align:start position:0% updates has been sent to the blockchain 00:11:18.689 --> 00:11:21.199 align:start position:0% updates has been sent to the blockchain smart<00:11:19.199> contract<00:11:19.529> upon<00:11:19.860> actually<00:11:20.610> will<00:11:20.790> be<00:11:20.970> in 00:11:21.199 --> 00:11:21.209 align:start position:0% smart contract upon actually will be in 00:11:21.209 --> 00:11:23.600 align:start position:0% smart contract upon actually will be in an<00:11:21.329> encrypted<00:11:21.569> form<00:11:21.810> and<00:11:22.319> the<00:11:22.709> way<00:11:22.889> a<00:11:23.220> new 00:11:23.600 --> 00:11:23.610 align:start position:0% an encrypted form and the way a new 00:11:23.610 --> 00:11:26.090 align:start position:0% an encrypted form and the way a new secure<00:11:23.910> application<00:11:24.540> to<00:11:25.139> do<00:11:25.620> the<00:11:25.889> mother 00:11:26.090 --> 00:11:26.100 align:start position:0% secure application to do the mother 00:11:26.100 --> 00:11:28.939 align:start position:0% secure application to do the mother aggregation<00:11:26.730> and<00:11:27.170> of<00:11:28.170> course<00:11:28.470> in<00:11:28.620> this<00:11:28.740> case 00:11:28.939 --> 00:11:28.949 align:start position:0% aggregation and of course in this case 00:11:28.949 --> 00:11:32.030 align:start position:0% aggregation and of course in this case also<00:11:29.399> to<00:11:29.759> protect<00:11:30.089> privacy<00:11:30.420> we<00:11:30.990> we<00:11:31.769> ensure 00:11:32.030 --> 00:11:32.040 align:start position:0% also to protect privacy we we ensure 00:11:32.040 --> 00:11:37.639 align:start position:0% also to protect privacy we we ensure that<00:11:32.189> the<00:11:32.310> mother<00:11:32.490> is<00:11:32.639> equal<00:11:33.629> to<00:11:36.259> so<00:11:37.259> how<00:11:37.470> this 00:11:37.639 --> 00:11:37.649 align:start position:0% that the mother is equal to so how this 00:11:37.649 --> 00:11:40.999 align:start position:0% that the mother is equal to so how this works<00:11:37.709> is<00:11:38.310> that<00:11:38.990> again<00:11:39.990> we<00:11:40.379> take<00:11:40.560> an<00:11:40.740> iterative 00:11:40.999 --> 00:11:41.009 align:start position:0% works is that again we take an iterative 00:11:41.009 --> 00:11:43.639 align:start position:0% works is that again we take an iterative approach<00:11:41.569> and<00:11:42.569> in<00:11:42.990> this<00:11:43.079> case<00:11:43.319> in<00:11:43.529> particular 00:11:43.639 --> 00:11:43.649 align:start position:0% approach and in this case in particular 00:11:43.649 --> 00:11:47.569 align:start position:0% approach and in this case in particular we<00:11:44.189> actually<00:11:44.550> have<00:11:44.899> we<00:11:45.899> have<00:11:46.139> enabled<00:11:46.740> this<00:11:47.220> as 00:11:47.569 --> 00:11:47.579 align:start position:0% we actually have we have enabled this as 00:11:47.579 --> 00:11:49.069 align:start position:0% we actually have we have enabled this as essential<00:11:48.029> as<00:11:48.149> a<00:11:48.180> materially 00:11:49.069 --> 00:11:49.079 align:start position:0% essential as a materially 00:11:49.079 --> 00:11:51.620 align:start position:0% essential as a materially mother<00:11:49.649> always<00:11:49.800> is<00:11:50.069> fourteen<00:11:50.550> perform<00:11:51.149> so 00:11:51.620 --> 00:11:51.630 align:start position:0% mother always is fourteen perform so 00:11:51.630 --> 00:11:54.050 align:start position:0% mother always is fourteen perform so when<00:11:51.810> the<00:11:51.990> animation<00:11:52.560> are<00:11:52.680> here<00:11:52.920> oasis<00:11:53.699> party 00:11:54.050 --> 00:11:54.060 align:start position:0% when the animation are here oasis party 00:11:54.060 --> 00:11:56.090 align:start position:0% when the animation are here oasis party platform<00:11:54.449> actually<00:11:54.870> may<00:11:55.019> pose<00:11:55.259> computational 00:11:56.090 --> 00:11:56.100 align:start position:0% platform actually may pose computational 00:11:56.100 --> 00:11:58.780 align:start position:0% platform actually may pose computational contract<00:11:56.490> where<00:11:57.180> the<00:11:57.209> stock<00:11:57.899> contracts 00:11:58.780 --> 00:11:58.790 align:start position:0% contract where the stock contracts 00:11:58.790 --> 00:12:02.420 align:start position:0% contract where the stock contracts States<00:11:59.790> is<00:12:00.149> actually<00:12:00.750> even<00:12:01.199> perform<00:12:01.709> and<00:12:01.920> we 00:12:02.420 --> 00:12:02.430 align:start position:0% States is actually even perform and we 00:12:02.430 --> 00:12:05.509 align:start position:0% States is actually even perform and we utilize<00:12:02.819> secure<00:12:03.120> computing<00:12:03.569> to<00:12:04.519> enable 00:12:05.509 --> 00:12:05.519 align:start position:0% utilize secure computing to enable 00:12:05.519 --> 00:12:10.370 align:start position:0% utilize secure computing to enable secure<00:12:07.189> computation<00:12:08.189> our<00:12:08.990> execution<00:12:09.990> is<00:12:10.350> not 00:12:10.370 --> 00:12:10.380 align:start position:0% secure computation our execution is not 00:12:10.380 --> 00:12:12.100 align:start position:0% secure computation our execution is not contracts 00:12:12.100 --> 00:12:12.110 align:start position:0% contracts 00:12:12.110 --> 00:12:14.249 align:start position:0% contracts well<00:12:13.110> the 00:12:14.249 --> 00:12:14.259 align:start position:0% well the 00:12:14.259 --> 00:12:16.049 align:start position:0% well the my<00:12:14.350> contract<00:12:14.709> state<00:12:14.919> is<00:12:15.160> stored<00:12:15.759> in<00:12:15.879> an 00:12:16.049 --> 00:12:16.059 align:start position:0% my contract state is stored in an 00:12:16.059 --> 00:12:18.449 align:start position:0% my contract state is stored in an encrypted<00:12:16.209> form<00:12:16.569> so<00:12:17.439> essentially<00:12:18.009> we<00:12:18.160> kind<00:12:18.399> of 00:12:18.449 --> 00:12:18.459 align:start position:0% encrypted form so essentially we kind of 00:12:18.459 --> 00:12:20.729 align:start position:0% encrypted form so essentially we kind of mind<00:12:18.609> that<00:12:18.729> we<00:12:18.850> utilize<00:12:19.299> this<00:12:20.109> capital<00:12:20.649> to 00:12:20.729 --> 00:12:20.739 align:start position:0% mind that we utilize this capital to 00:12:20.739 --> 00:12:21.449 align:start position:0% mind that we utilize this capital to smart<00:12:20.979> contract 00:12:21.449 --> 00:12:21.459 align:start position:0% smart contract 00:12:21.459 --> 00:12:26.189 align:start position:0% smart contract primitives<00:12:22.679> where<00:12:23.679> again<00:12:24.389> this<00:12:25.389> iterative 00:12:26.189 --> 00:12:26.199 align:start position:0% primitives where again this iterative 00:12:26.199 --> 00:12:30.259 align:start position:0% primitives where again this iterative approach<00:12:27.119> at<00:12:28.119> each<00:12:28.419> interior<00:12:28.809> iteration<00:12:29.649> the 00:12:30.259 --> 00:12:30.269 align:start position:0% approach at each interior iteration the 00:12:30.269 --> 00:12:32.629 align:start position:0% approach at each interior iteration the Machinima<00:12:31.269> models<00:12:31.660> are<00:12:31.779> happening<00:12:32.139> between 00:12:32.629 --> 00:12:32.639 align:start position:0% Machinima models are happening between 00:12:32.639 --> 00:12:37.259 align:start position:0% Machinima models are happening between if<00:12:33.639> you<00:12:33.699> view<00:12:33.910> it<00:12:33.939> as<00:12:35.519> as<00:12:36.519> part<00:12:36.789> of<00:12:36.879> the<00:12:36.999> state's 00:12:37.259 --> 00:12:37.269 align:start position:0% if you view it as as part of the state's 00:12:37.269 --> 00:12:41.219 align:start position:0% if you view it as as part of the state's our<00:12:37.660> confidential<00:12:38.529> smart<00:12:38.829> contracts<00:12:40.109> well<00:12:41.109> we 00:12:41.219 --> 00:12:41.229 align:start position:0% our confidential smart contracts well we 00:12:41.229 --> 00:12:45.449 align:start position:0% our confidential smart contracts well we can't<00:12:41.470> hide<00:12:41.649> mites<00:12:41.949> and<00:12:42.789> as<00:12:43.329> each<00:12:44.009> it<00:12:45.009> erodes 00:12:45.449 --> 00:12:45.459 align:start position:0% can't hide mites and as each it erodes 00:12:45.459 --> 00:12:48.779 align:start position:0% can't hide mites and as each it erodes the<00:12:46.089> the<00:12:46.929> secret<00:12:47.259> input<00:12:47.889> the<00:12:48.009> mother<00:12:48.189> is<00:12:48.489> sent 00:12:48.779 --> 00:12:48.789 align:start position:0% the the secret input the mother is sent 00:12:48.789 --> 00:12:51.929 align:start position:0% the the secret input the mother is sent to<00:12:48.970> the<00:12:49.449> local<00:12:50.199> devices<00:12:50.499> we<00:12:51.279> do<00:12:51.459> handle<00:12:51.789> some 00:12:51.929 --> 00:12:51.939 align:start position:0% to the local devices we do handle some 00:12:51.939 --> 00:12:52.739 align:start position:0% to the local devices we do handle some key<00:12:52.179> management 00:12:52.739 --> 00:12:52.749 align:start position:0% key management 00:12:52.749 --> 00:12:57.359 align:start position:0% key management so<00:12:53.199> the<00:12:54.689> the<00:12:55.689> model<00:12:56.049> then<00:12:56.319> gives<00:12:56.769> decrypted 00:12:57.359 --> 00:12:57.369 align:start position:0% so the the model then gives decrypted 00:12:57.369 --> 00:12:59.729 align:start position:0% so the the model then gives decrypted and<00:12:57.639> the<00:12:58.029> local<00:12:58.449> device<00:12:58.689> on<00:12:59.350> the<00:12:59.470> local 00:12:59.729 --> 00:12:59.739 align:start position:0% and the local device on the local 00:12:59.739 --> 00:13:02.400 align:start position:0% and the local device on the local devices<00:12:59.979> and<00:13:00.399> then<00:13:00.910> the<00:13:01.029> clients<00:13:01.449> uses<00:13:02.109> its 00:13:02.400 --> 00:13:02.410 align:start position:0% devices and then the clients uses its 00:13:02.410 --> 00:13:08.849 align:start position:0% devices and then the clients uses its own<00:13:02.559> local<00:13:02.889> data<00:13:03.069> to<00:13:03.369> update<00:13:04.649> the<00:13:07.529> local<00:13:08.529> model 00:13:08.849 --> 00:13:08.859 align:start position:0% own local data to update the local model 00:13:08.859 --> 00:13:13.349 align:start position:0% own local data to update the local model and<00:13:09.309> then<00:13:09.639> it<00:13:11.729> computes<00:13:12.729> that<00:13:12.910> really 00:13:13.349 --> 00:13:13.359 align:start position:0% and then it computes that really 00:13:13.359 --> 00:13:15.529 align:start position:0% and then it computes that really athletes<00:13:13.779> and<00:13:14.049> then<00:13:14.589> it<00:13:14.709> also<00:13:14.979> has 00:13:15.529 --> 00:13:15.539 align:start position:0% athletes and then it also has 00:13:15.539 --> 00:13:18.989 align:start position:0% athletes and then it also has differential<00:13:16.539> privacy<00:13:17.379> in<00:13:17.829> perturbation<00:13:18.069> to 00:13:18.989 --> 00:13:18.999 align:start position:0% differential privacy in perturbation to 00:13:18.999 --> 00:13:22.499 align:start position:0% differential privacy in perturbation to ensure<00:13:19.449> that<00:13:19.480> they<00:13:20.699> the<00:13:21.699> nest<00:13:21.970> authority 00:13:22.499 --> 00:13:22.509 align:start position:0% ensure that they the nest authority 00:13:22.509 --> 00:13:25.650 align:start position:0% ensure that they the nest authority creates<00:13:23.350> evening<00:13:24.220> activity<00:13:24.819> trained<00:13:25.119> as 00:13:25.650 --> 00:13:25.660 align:start position:0% creates evening activity trained as 00:13:25.660 --> 00:13:30.389 align:start position:0% creates evening activity trained as eventually<00:13:26.169> private<00:13:26.529> owner<00:13:27.539> and<00:13:28.539> then<00:13:29.399> this 00:13:30.389 --> 00:13:30.399 align:start position:0% eventually private owner and then this 00:13:30.399 --> 00:13:32.699 align:start position:0% eventually private owner and then this Brittany<00:13:31.209> updates<00:13:31.629> with<00:13:32.079> the<00:13:32.109> differential 00:13:32.699 --> 00:13:32.709 align:start position:0% Brittany updates with the differential 00:13:32.709 --> 00:13:37.199 align:start position:0% Brittany updates with the differential privacy<00:13:32.999> annoys<00:13:33.999> Alice<00:13:34.509> is<00:13:35.019> then<00:13:35.529> again<00:13:36.489> at 00:13:37.199 --> 00:13:37.209 align:start position:0% privacy annoys Alice is then again at 00:13:37.209 --> 00:13:40.889 align:start position:0% privacy annoys Alice is then again at encrypted<00:13:37.869> and<00:13:38.079> the<00:13:38.529> send<00:13:38.799> to<00:13:39.039> the<00:13:39.899> also 00:13:40.889 --> 00:13:40.899 align:start position:0% encrypted and the send to the also 00:13:40.899 --> 00:13:42.659 align:start position:0% encrypted and the send to the also static<00:13:41.289> route<00:13:41.769> to<00:13:41.919> the<00:13:42.009> highlights<00:13:42.429> of<00:13:42.579> our 00:13:42.659 --> 00:13:42.669 align:start position:0% static route to the highlights of our 00:13:42.669 --> 00:13:46.700 align:start position:0% static route to the highlights of our contracts<00:13:43.119> whether<00:13:43.869> my<00:13:44.259> smart<00:13:44.559> contracts<00:13:45.089> in 00:13:46.700 --> 00:13:46.710 align:start position:0% contracts whether my smart contracts in 00:13:46.710 --> 00:13:49.190 align:start position:0% contracts whether my smart contracts in then<00:13:46.850> combines<00:13:47.850> the<00:13:48.120> screening<00:13:48.510> updated<00:13:49.050> that 00:13:49.190 --> 00:13:49.200 align:start position:0% then combines the screening updated that 00:13:49.200 --> 00:13:51.380 align:start position:0% then combines the screening updated that you<00:13:49.290> measure<00:13:49.910> different<00:13:50.910> differentially 00:13:51.380 --> 00:13:51.390 align:start position:0% you measure different differentially 00:13:51.390 --> 00:13:54.770 align:start position:0% you measure different differentially planets<00:13:52.340> perturbations<00:13:53.340> and<00:13:53.630> through<00:13:54.630> the 00:13:54.770 --> 00:13:54.780 align:start position:0% planets perturbations and through the 00:13:54.780 --> 00:13:57.830 align:start position:0% planets perturbations and through the secure<00:13:55.170> application<00:13:55.830> and<00:13:56.730> then<00:13:56.940> compute<00:13:57.450> the 00:13:57.830 --> 00:13:57.840 align:start position:0% secure application and then compute the 00:13:57.840 --> 00:14:02.090 align:start position:0% secure application and then compute the next<00:13:58.110> iteration<00:13:59.010> after<00:13:59.610> update<00:14:00.330> mode<00:14:01.100> so 00:14:02.090 --> 00:14:02.100 align:start position:0% next iteration after update mode so 00:14:02.100 --> 00:14:04.610 align:start position:0% next iteration after update mode so again<00:14:02.400> by<00:14:02.850> taking<00:14:03.060> this<00:14:03.420> iterative<00:14:04.020> approach 00:14:04.610 --> 00:14:04.620 align:start position:0% again by taking this iterative approach 00:14:04.620 --> 00:14:06.590 align:start position:0% again by taking this iterative approach within<00:14:05.310> the<00:14:05.640> news<00:14:05.880> this<00:14:06.120> combines 00:14:06.590 --> 00:14:06.600 align:start position:0% within the news this combines 00:14:06.600 --> 00:14:08.120 align:start position:0% within the news this combines combination<00:14:07.230> is<00:14:07.290> my<00:14:07.440> contract<00:14:07.890> to 00:14:08.120 --> 00:14:08.130 align:start position:0% combination is my contract to 00:14:08.130 --> 00:14:12.170 align:start position:0% combination is my contract to coordinates<00:14:09.000> the<00:14:10.790> distributed<00:14:11.790> dimension 00:14:12.170 --> 00:14:12.180 align:start position:0% coordinates the distributed dimension 00:14:12.180 --> 00:14:14.210 align:start position:0% coordinates the distributed dimension and<00:14:12.330> in<00:14:12.450> our<00:14:12.810> training<00:14:13.170> across<00:14:13.890> the<00:14:14.070> different 00:14:14.210 --> 00:14:14.220 align:start position:0% and in our training across the different 00:14:14.220 --> 00:14:16.940 align:start position:0% and in our training across the different devices<00:14:14.780> to<00:14:15.780> enable<00:14:16.050> decentralize<00:14:16.920> the 00:14:16.940 --> 00:14:16.950 align:start position:0% devices to enable decentralize the 00:14:16.950 --> 00:14:22.220 align:start position:0% devices to enable decentralize the practice<00:14:17.550> area<00:14:19.760> so<00:14:20.760> now<00:14:21.060> I'm<00:14:21.330> going<00:14:21.510> to<00:14:21.780> give 00:14:22.220 --> 00:14:22.230 align:start position:0% practice area so now I'm going to give 00:14:22.230 --> 00:14:27.200 align:start position:0% practice area so now I'm going to give you<00:14:22.440> an<00:14:22.740> example<00:14:23.550> of<00:14:25.370> actual<00:14:26.370> application 00:14:27.200 --> 00:14:27.210 align:start position:0% you an example of actual application 00:14:27.210 --> 00:14:31.100 align:start position:0% you an example of actual application that<00:14:27.690> we<00:14:27.810> have<00:14:28.070> in<00:14:29.070> the<00:14:29.540> domain<00:14:30.540> of<00:14:30.570> anomaly 00:14:31.100 --> 00:14:31.110 align:start position:0% that we have in the domain of anomaly 00:14:31.110 --> 00:14:34.610 align:start position:0% that we have in the domain of anomaly detection<00:14:32.390> so<00:14:33.390> in<00:14:33.540> this<00:14:33.690> case<00:14:33.930> essentially<00:14:34.350> we 00:14:34.610 --> 00:14:34.620 align:start position:0% detection so in this case essentially we 00:14:34.620 --> 00:14:37.280 align:start position:0% detection so in this case essentially we can<00:14:34.860> update<00:14:35.280> the<00:14:35.580> head<00:14:35.790> -<00:14:35.970> my<00:14:36.330> contract<00:14:36.600> to 00:14:37.280 --> 00:14:37.290 align:start position:0% can update the head - my contract to 00:14:37.290 --> 00:14:40.160 align:start position:0% can update the head - my contract to enable<00:14:38.540> especially<00:14:39.540> to<00:14:39.600> achieve<00:14:39.960> commercial 00:14:40.160 --> 00:14:40.170 align:start position:0% enable especially to achieve commercial 00:14:40.170 --> 00:14:43.130 align:start position:0% enable especially to achieve commercial model<00:14:40.770> for<00:14:40.920> anomaly<00:14:41.730> detection<00:14:42.060> and<00:14:42.960> in 00:14:43.130 --> 00:14:43.140 align:start position:0% model for anomaly detection and in 00:14:43.140 --> 00:14:45.740 align:start position:0% model for anomaly detection and in particular<00:14:43.620> in<00:14:43.740> this<00:14:43.860> case<00:14:43.920> for<00:14:44.850> anomaly 00:14:45.740 --> 00:14:45.750 align:start position:0% particular in this case for anomaly 00:14:45.750 --> 00:14:48.950 align:start position:0% particular in this case for anomaly detection<00:14:46.130> we<00:14:47.130> look<00:14:47.490> at<00:14:47.700> the<00:14:47.940> application<00:14:48.780> of 00:14:48.950 --> 00:14:48.960 align:start position:0% detection we look at the application of 00:14:48.960 --> 00:14:51.920 align:start position:0% detection we look at the application of a<00:14:49.050> system<00:14:49.380> block<00:14:49.590> another<00:14:50.070> detection<00:14:50.640> so<00:14:51.510> as 00:14:51.920 --> 00:14:51.930 align:start position:0% a system block another detection so as 00:14:51.930 --> 00:14:54.560 align:start position:0% a system block another detection so as computers<00:14:52.650> around<00:14:53.210> throughout<00:14:54.210> certain 00:14:54.560 --> 00:14:54.570 align:start position:0% computers around throughout certain 00:14:54.570 --> 00:14:57.470 align:start position:0% computers around throughout certain programs<00:14:54.900> other<00:14:55.440> times<00:14:55.820> it<00:14:56.820> produces<00:14:57.390> the 00:14:57.470 --> 00:14:57.480 align:start position:0% programs other times it produces the 00:14:57.480 --> 00:14:59.750 align:start position:0% programs other times it produces the system<00:14:57.780> loss<00:14:57.930> and<00:14:58.320> this<00:14:58.890> is<00:14:59.040> perhaps<00:14:59.190> contains 00:14:59.750 --> 00:14:59.760 align:start position:0% system loss and this is perhaps contains 00:14:59.760 --> 00:15:02.480 align:start position:0% system loss and this is perhaps contains very<00:15:00.000> useful<00:15:00.330> information<00:15:00.900> and<00:15:01.350> one<00:15:01.620> can<00:15:01.860> try 00:15:02.480 --> 00:15:02.490 align:start position:0% very useful information and one can try 00:15:02.490 --> 00:15:05.000 align:start position:0% very useful information and one can try to<00:15:02.550> train<00:15:03.210> which<00:15:03.360> million<00:15:03.690> others<00:15:03.990> to<00:15:04.620> go<00:15:04.800> over 00:15:05.000 --> 00:15:05.010 align:start position:0% to train which million others to go over 00:15:05.010 --> 00:15:06.800 align:start position:0% to train which million others to go over this<00:15:05.220> system<00:15:05.850> now<00:15:05.970> so<00:15:06.210> try<00:15:06.300> to<00:15:06.420> detect 00:15:06.800 --> 00:15:06.810 align:start position:0% this system now so try to detect 00:15:06.810 --> 00:15:10.970 align:start position:0% this system now so try to detect anomalies<00:15:08.840> essentially<00:15:09.840> one<00:15:10.050> way<00:15:10.080> to<00:15:10.260> do 00:15:10.970 --> 00:15:10.980 align:start position:0% anomalies essentially one way to do 00:15:10.980 --> 00:15:13.460 align:start position:0% anomalies essentially one way to do system<00:15:11.430> of<00:15:11.580> anomaly<00:15:12.360> detection<00:15:12.630> and<00:15:13.350> you 00:15:13.460 --> 00:15:13.470 align:start position:0% system of anomaly detection and you 00:15:13.470 --> 00:15:15.410 align:start position:0% system of anomaly detection and you think<00:15:13.680> bringing<00:15:14.130> is<00:15:14.250> over<00:15:14.520> here<00:15:14.700> to<00:15:14.910> between<00:15:15.240> a 00:15:15.410 --> 00:15:15.420 align:start position:0% think bringing is over here to between a 00:15:15.420 --> 00:15:17.540 align:start position:0% think bringing is over here to between a sequence<00:15:16.080> model<00:15:16.560> and<00:15:16.740> then<00:15:17.130> using<00:15:17.460> the 00:15:17.540 --> 00:15:17.550 align:start position:0% sequence model and then using the 00:15:17.550 --> 00:15:20.810 align:start position:0% sequence model and then using the sequence<00:15:17.880> model<00:15:18.240> we<00:15:18.750> can<00:15:19.080> then<00:15:19.520> go 00:15:20.810 --> 00:15:20.820 align:start position:0% sequence model we can then go 00:15:20.820 --> 00:15:25.630 align:start position:0% sequence model we can then go this<00:15:21.000> is<00:15:21.150> not<00:15:21.420> to<00:15:22.080> try<00:15:22.320> to<00:15:22.350> detect<00:15:23.600> anomalies 00:15:25.630 --> 00:15:25.640 align:start position:0% this is not to try to detect anomalies 00:15:25.640 --> 00:15:30.710 align:start position:0% this is not to try to detect anomalies so<00:15:27.800> so<00:15:28.800> in<00:15:28.980> our<00:15:29.070> case<00:15:29.370> essentially<00:15:29.910> were<00:15:30.510> to 00:15:30.710 --> 00:15:30.720 align:start position:0% so so in our case essentially were to 00:15:30.720 --> 00:15:33.290 align:start position:0% so so in our case essentially were to use<00:15:30.960> the<00:15:31.260> liberal<00:15:31.800> system<00:15:32.040> lot<00:15:32.340> and<00:15:32.700> then 00:15:33.290 --> 00:15:33.300 align:start position:0% use the liberal system lot and then 00:15:33.300 --> 00:15:35.710 align:start position:0% use the liberal system lot and then Trinity<00:15:34.050> through<00:15:34.350> you<00:15:35.130> see<00:15:35.340> this 00:15:35.710 --> 00:15:35.720 align:start position:0% Trinity through you see this 00:15:35.720 --> 00:15:39.170 align:start position:0% Trinity through you see this decentralized<00:15:36.800> fertility<00:15:37.800> to<00:15:38.670> actually 00:15:39.170 --> 00:15:39.180 align:start position:0% decentralized fertility to actually 00:15:39.180 --> 00:15:42.500 align:start position:0% decentralized fertility to actually train<00:15:39.450> and<00:15:39.690> update<00:15:39.990> drama<00:15:40.260> on<00:15:40.830> our<00:15:41.130> plasma<00:15:42.030> and 00:15:42.500 --> 00:15:42.510 align:start position:0% train and update drama on our plasma and 00:15:42.510 --> 00:15:46.610 align:start position:0% train and update drama on our plasma and we<00:15:43.170> achieve<00:15:44.330> we<00:15:45.330> enable<00:15:45.960> strong<00:15:46.230> privacy 00:15:46.610 --> 00:15:46.620 align:start position:0% we achieve we enable strong privacy 00:15:46.620 --> 00:15:49.340 align:start position:0% we achieve we enable strong privacy protection<00:15:47.160> well<00:15:47.760> as<00:15:47.910> system<00:15:48.420> achieve<00:15:49.110> high 00:15:49.340 --> 00:15:49.350 align:start position:0% protection well as system achieve high 00:15:49.350 --> 00:15:52.160 align:start position:0% protection well as system achieve high utility<00:15:49.680> and<00:15:50.220> in<00:15:50.790> many<00:15:51.450> settings<00:15:51.690> with 00:15:52.160 --> 00:15:52.170 align:start position:0% utility and in many settings with 00:15:52.170 --> 00:15:57.770 align:start position:0% utility and in many settings with utility<00:15:52.680> extension<00:15:52.860> which<00:15:54.050> is<00:15:55.400> close<00:15:56.400> to<00:15:56.780> the 00:15:57.770 --> 00:15:57.780 align:start position:0% utility extension which is close to the 00:15:57.780 --> 00:16:03.050 align:start position:0% utility extension which is close to the centralized<00:15:58.230> model<00:16:00.290> so<00:16:01.290> to<00:16:01.440> summarize<00:16:02.060> we 00:16:03.050 --> 00:16:03.060 align:start position:0% centralized model so to summarize we 00:16:03.060 --> 00:16:05.180 align:start position:0% centralized model so to summarize we have<00:16:03.090> proposed<00:16:03.750> a<00:16:03.900> new<00:16:04.050> paradigm<00:16:04.530> can't<00:16:05.070> be 00:16:05.180 --> 00:16:05.190 align:start position:0% have proposed a new paradigm can't be 00:16:05.190 --> 00:16:07.610 align:start position:0% have proposed a new paradigm can't be centralized<00:16:05.700> federal<00:16:06.000> revenue<00:16:06.510> where<00:16:07.350> we 00:16:07.610 --> 00:16:07.620 align:start position:0% centralized federal revenue where we 00:16:07.620 --> 00:16:10.010 align:start position:0% centralized federal revenue where we don't<00:16:07.740> need<00:16:07.920> to<00:16:08.100> Villa<00:16:08.400> and<00:16:08.670> the<00:16:08.850> trust<00:16:09.750> and 00:16:10.010 --> 00:16:10.020 align:start position:0% don't need to Villa and the trust and 00:16:10.020 --> 00:16:13.400 align:start position:0% don't need to Villa and the trust and incentive<00:16:10.530> ready<00:16:10.740> and<00:16:11.070> we<00:16:11.850> provide<00:16:12.480> much 00:16:13.400 --> 00:16:13.410 align:start position:0% incentive ready and we provide much 00:16:13.410 --> 00:16:16.670 align:start position:0% incentive ready and we provide much British<00:16:13.770> efficiency<00:16:14.640> for<00:16:15.600> training<00:16:16.200> teacher 00:16:16.670 --> 00:16:16.680 align:start position:0% British efficiency for training teacher 00:16:16.680 --> 00:16:18.050 align:start position:0% British efficiency for training teacher with<00:16:16.890> much<00:16:17.070> mini<00:16:17.310> model<00:16:17.700> then<00:16:17.910> the 00:16:18.050 --> 00:16:18.060 align:start position:0% with much mini model then the 00:16:18.060 --> 00:16:19.970 align:start position:0% with much mini model then the peer-to-peer<00:16:18.270> setting<00:16:18.930> now<00:16:19.440> with<00:16:19.620> the<00:16:19.710> strong 00:16:19.970 --> 00:16:19.980 align:start position:0% peer-to-peer setting now with the strong 00:16:19.980 --> 00:16:21.860 align:start position:0% peer-to-peer setting now with the strong privacy<00:16:20.310> protection<00:16:20.880> and<00:16:21.090> the<00:16:21.540> beauty 00:16:21.860 --> 00:16:21.870 align:start position:0% privacy protection and the beauty 00:16:21.870 --> 00:16:25.250 align:start position:0% privacy protection and the beauty incentive<00:16:22.500> mechanisms<00:16:23.070> and<00:16:23.250> this<00:16:24.260> the 00:16:25.250 --> 00:16:25.260 align:start position:0% incentive mechanisms and this the 00:16:25.260 --> 00:16:26.570 align:start position:0% incentive mechanisms and this the sentiments<00:16:25.680> friendly<00:16:25.950> bringing<00:16:26.250> has<00:16:26.400> been 00:16:26.570 --> 00:16:26.580 align:start position:0% sentiments friendly bringing has been 00:16:26.580 --> 00:16:29.510 align:start position:0% sentiments friendly bringing has been enabled<00:16:26.850> by<00:16:27.330> the<00:16:27.840> ISIS<00:16:28.170> party<00:16:28.530> platform<00:16:29.040> with 00:16:29.510 --> 00:16:29.520 align:start position:0% enabled by the ISIS party platform with 00:16:29.520 --> 00:16:32.930 align:start position:0% enabled by the ISIS party platform with its<00:16:29.820> unique<00:16:30.380> capabilities<00:16:31.380> to<00:16:32.250> operate<00:16:32.910> a 00:16:32.930 --> 00:16:32.940 align:start position:0% its unique capabilities to operate a 00:16:32.940 --> 00:16:34.940 align:start position:0% its unique capabilities to operate a skill<00:16:33.570> ability<00:16:33.960> and<00:16:34.200> also<00:16:34.560> privacy 00:16:34.940 --> 00:16:34.950 align:start position:0% skill ability and also privacy 00:16:34.950 --> 00:16:42.080 align:start position:0% skill ability and also privacy protection<00:16:39.200> so<00:16:40.250> right<00:16:41.250> so<00:16:41.430> with<00:16:41.640> the<00:16:41.730> Oasis 00:16:42.080 --> 00:16:42.090 align:start position:0% protection so right so with the Oasis 00:16:42.090 --> 00:16:43.820 align:start position:0% protection so right so with the Oasis Network<00:16:42.390> a<00:16:42.540> week<00:16:42.720> here<00:16:43.020> as<00:16:43.230> I<00:16:43.530> just 00:16:43.820 --> 00:16:43.830 align:start position:0% Network a week here as I just 00:16:43.830 --> 00:16:47.180 align:start position:0% Network a week here as I just demonstrated<00:16:44.030> it's<00:16:45.030> the<00:16:45.150> first<00:16:46.190> project 00:16:47.180 --> 00:16:47.190 align:start position:0% demonstrated it's the first project 00:16:47.190 --> 00:16:49.910 align:start position:0% demonstrated it's the first project smart<00:16:47.670> contractor<00:16:48.240> on<00:16:48.480> that<00:16:48.900> can<00:16:49.080> enable<00:16:49.440> this 00:16:49.910 --> 00:16:49.920 align:start position:0% smart contractor on that can enable this 00:16:49.920 --> 00:16:55.060 align:start position:0% smart contractor on that can enable this type<00:16:50.190> of<00:16:51.380> solutions<00:16:52.380> and<00:16:52.650> decentralized 00:16:55.060 --> 00:16:55.070 align:start position:0% type of solutions and decentralized 00:16:55.070 --> 00:17:00.280 align:start position:0% type of solutions and decentralized and<00:16:55.460> we<00:16:56.140> we<00:16:57.140> hope<00:16:57.350> encouraged<00:16:57.890> everyone<00:16:58.760> to<00:16:59.290> to 00:17:00.280 --> 00:17:00.290 align:start position:0% and we we hope encouraged everyone to to 00:17:00.290 --> 00:17:02.260 align:start position:0% and we we hope encouraged everyone to to build<00:17:00.500> the<00:17:00.590> new<00:17:00.680> applications<00:17:01.310> and<00:17:01.550> the<00:17:01.880> Oasis 00:17:02.260 --> 00:17:02.270 align:start position:0% build the new applications and the Oasis 00:17:02.270 --> 00:17:04.930 align:start position:0% build the new applications and the Oasis Network<00:17:02.630> and<00:17:03.100> we<00:17:04.100> recently<00:17:04.280> launched<00:17:04.730> the 00:17:04.930 --> 00:17:04.940 align:start position:0% Network and we recently launched the 00:17:04.940 --> 00:17:09.550 align:start position:0% Network and we recently launched the algorithm<00:17:05.270> that<00:17:05.450> 2.0<00:17:06.020> and<00:17:06.640> also<00:17:07.640> we<00:17:08.060> release<00:17:08.600> a 00:17:09.550 --> 00:17:09.560 align:start position:0% algorithm that 2.0 and also we release a 00:17:09.560 --> 00:17:13.830 align:start position:0% algorithm that 2.0 and also we release a number<00:17:09.980> of<00:17:10.130> new<00:17:10.430> developer<00:17:11.360> tools<00:17:11.600> within 00:17:13.830 --> 00:17:13.840 align:start position:0% number of new developer tools within 00:17:13.840 --> 00:17:16.840 align:start position:0% number of new developer tools within with<00:17:14.840> a<00:17:15.080> new<00:17:15.260> developer<00:17:15.830> experience<00:17:16.340> to<00:17:16.700> make 00:17:16.840 --> 00:17:16.850 align:start position:0% with a new developer experience to make 00:17:16.850 --> 00:17:18.730 align:start position:0% with a new developer experience to make it<00:17:16.970> really<00:17:17.180> easy<00:17:17.330> to<00:17:17.630> build<00:17:17.750> applications<00:17:18.440> on 00:17:18.730 --> 00:17:18.740 align:start position:0% it really easy to build applications on 00:17:18.740 --> 00:17:21.610 align:start position:0% it really easy to build applications on top<00:17:18.770> of<00:17:19.160> the<00:17:19.540> platform<00:17:20.540> and<00:17:20.840> in<00:17:21.110> particular 00:17:21.610 --> 00:17:21.620 align:start position:0% top of the platform and in particular 00:17:21.620 --> 00:17:26.080 align:start position:0% top of the platform and in particular also<00:17:21.950> equally<00:17:22.790> new<00:17:24.640> and<00:17:25.640> as<00:17:25.820> we<00:17:26.060> are 00:17:26.080 --> 00:17:26.090 align:start position:0% also equally new and as we are 00:17:26.090 --> 00:17:28.600 align:start position:0% also equally new and as we are developing<00:17:26.330> new<00:17:26.900> the<00:17:27.320> capacity<00:17:28.010> is<00:17:28.160> in 00:17:28.600 --> 00:17:28.610 align:start position:0% developing new the capacity is in 00:17:28.610 --> 00:17:30.970 align:start position:0% developing new the capacity is in particular<00:17:28.820> to<00:17:29.180> make<00:17:29.210> it<00:17:29.480> easier<00:17:29.930> for<00:17:30.260> a 00:17:30.970 --> 00:17:30.980 align:start position:0% particular to make it easier for a 00:17:30.980 --> 00:17:32.710 align:start position:0% particular to make it easier for a developer<00:17:31.550> to<00:17:31.580> build<00:17:31.730> our<00:17:32.240> secret 00:17:32.710 --> 00:17:32.720 align:start position:0% developer to build our secret 00:17:32.720 --> 00:17:39.970 align:start position:0% developer to build our secret applications<00:17:33.940> and<00:17:35.950> we<00:17:36.950> are<00:17:38.710> and<00:17:39.710> we<00:17:39.950> are 00:17:39.970 --> 00:17:39.980 align:start position:0% applications and we are and we are 00:17:39.980 --> 00:17:44.380 align:start position:0% applications and we are and we are inviting<00:17:40.700> know<00:17:41.300> the<00:17:41.480> operatives<00:17:42.050> and<00:17:43.120> to<00:17:44.120> join 00:17:44.380 --> 00:17:44.390 align:start position:0% inviting know the operatives and to join 00:17:44.390 --> 00:17:45.760 align:start position:0% inviting know the operatives and to join our<00:17:44.630> and<00:17:45.140> our 00:17:45.760 --> 00:17:45.770 align:start position:0% our and our 00:17:45.770 --> 00:17:48.070 align:start position:0% our and our and<00:17:46.070> we'll<00:17:46.340> be<00:17:46.520> starting<00:17:46.790> out<00:17:47.180> a<00:17:47.390> patent<00:17:47.810> team 00:17:48.070 --> 00:17:48.080 align:start position:0% and we'll be starting out a patent team 00:17:48.080 --> 00:17:51.310 align:start position:0% and we'll be starting out a patent team and<00:17:49.010> also<00:17:49.430> we'll<00:17:49.850> be<00:17:50.060> launching<00:17:50.720> a<00:17:51.110> public 00:17:51.310 --> 00:17:51.320 align:start position:0% and also we'll be launching a public 00:17:51.320 --> 00:17:53.200 align:start position:0% and also we'll be launching a public destination<00:17:51.650> and<00:17:52.340> with<00:17:52.820> the<00:17:52.940> state 00:17:53.200 --> 00:17:53.210 align:start position:0% destination and with the state 00:17:53.210 --> 00:17:56.590 align:start position:0% destination and with the state competition<00:17:55.000> so<00:17:56.000> the<00:17:56.120> speaking<00:17:56.360> competition 00:17:56.590 --> 00:17:56.600 align:start position:0% competition so the speaking competition 00:17:56.600 --> 00:18:00.360 align:start position:0% competition so the speaking competition will<00:17:57.110> be<00:17:57.260> coming<00:17:57.650> in<00:17:58.250> a<00:17:58.700> little<00:17:59.210> interval<00:18:00.050> and 00:18:00.360 --> 00:18:00.370 align:start position:0% will be coming in a little interval and 00:18:00.370 --> 00:18:05.530 align:start position:0% will be coming in a little interval and we<00:18:02.380> really<00:18:03.380> welcome<00:18:03.560> everyone<00:18:04.040> to<00:18:04.490> to<00:18:05.360> join 00:18:05.530 --> 00:18:05.540 align:start position:0% we really welcome everyone to to join 00:18:05.540 --> 00:18:11.500 align:start position:0% we really welcome everyone to to join the<00:18:06.500> sticky<00:18:06.920> competition<00:18:07.610> and<00:18:08.090> again<00:18:09.850> we<00:18:10.850> look 00:18:11.500 --> 00:18:11.510 align:start position:0% the sticky competition and again we look 00:18:11.510 --> 00:18:14.950 align:start position:0% the sticky competition and again we look forward<00:18:11.750> to<00:18:12.880> have<00:18:13.880> people<00:18:14.150> ask<00:18:14.450> the<00:18:14.660> network 00:18:14.950 --> 00:18:14.960 align:start position:0% forward to have people ask the network 00:18:14.960 --> 00:18:17.650 align:start position:0% forward to have people ask the network and<00:18:15.170> to<00:18:15.680> build<00:18:16.160> new<00:18:16.460> applications<00:18:16.660> that 00:18:17.650 --> 00:18:17.660 align:start position:0% and to build new applications that 00:18:17.660 --> 00:18:20.240 align:start position:0% and to build new applications that couldn't<00:18:18.050> be<00:18:18.110> built<00:18:18.260> before<00:18:18.620> thank<00:18:19.610> you 00:18:20.240 --> 00:18:20.250 align:start position:0% couldn't be built before thank you 00:18:20.250 --> 00:18:31.109 align:start position:0% couldn't be built before thank you [Applause]