WEBVTT Kind: captions Language: en 00:00:00.599 --> 00:00:03.649 align:start position:0% I'm<00:00:01.050> Sanjay<00:00:01.530> I<00:00:02.010> work<00:00:02.460> for<00:00:02.669> Intel<00:00:02.939> and<00:00:03.179> this 00:00:03.649 --> 00:00:03.659 align:start position:0% I'm Sanjay I work for Intel and this 00:00:03.659 --> 00:00:07.190 align:start position:0% I'm Sanjay I work for Intel and this Andreas<00:00:04.170> works<00:00:05.160> for<00:00:05.339> consensus<00:00:05.850> so<00:00:06.509> today 00:00:07.190 --> 00:00:07.200 align:start position:0% Andreas works for consensus so today 00:00:07.200 --> 00:00:09.440 align:start position:0% Andreas works for consensus so today we're<00:00:07.350> gonna<00:00:07.470> we<00:00:07.740> are<00:00:07.830> going<00:00:08.010> to<00:00:08.130> share<00:00:08.450> some 00:00:09.440 --> 00:00:09.450 align:start position:0% we're gonna we are going to share some 00:00:09.450 --> 00:00:12.020 align:start position:0% we're gonna we are going to share some of<00:00:09.480> the<00:00:09.660> work<00:00:09.870> that<00:00:09.900> we<00:00:10.349> have<00:00:10.500> been<00:00:10.620> doing<00:00:11.030> in 00:00:12.020 --> 00:00:12.030 align:start position:0% of the work that we have been doing in 00:00:12.030 --> 00:00:14.120 align:start position:0% of the work that we have been doing in the<00:00:12.300> space<00:00:12.540> of<00:00:12.570> like<00:00:13.019> you<00:00:13.139> know<00:00:13.259> how<00:00:13.799> we<00:00:13.860> can 00:00:14.120 --> 00:00:14.130 align:start position:0% the space of like you know how we can 00:00:14.130 --> 00:00:16.550 align:start position:0% the space of like you know how we can apply<00:00:14.429> trusted<00:00:14.910> compute<00:00:15.299> for<00:00:16.289> the<00:00:16.410> good<00:00:16.529> of 00:00:16.550 --> 00:00:16.560 align:start position:0% apply trusted compute for the good of 00:00:16.560 --> 00:00:21.080 align:start position:0% apply trusted compute for the good of aetherium<00:00:17.840> as<00:00:18.840> an<00:00:19.080> option<00:00:19.470> so<00:00:20.279> the<00:00:20.609> talk<00:00:20.850> today 00:00:21.080 --> 00:00:21.090 align:start position:0% aetherium as an option so the talk today 00:00:21.090 --> 00:00:23.230 align:start position:0% aetherium as an option so the talk today is<00:00:21.210> like<00:00:21.480> you<00:00:21.570> know<00:00:21.660> two<00:00:21.810> parts<00:00:22.230> one<00:00:22.560> is 00:00:23.230 --> 00:00:23.240 align:start position:0% is like you know two parts one is 00:00:23.240 --> 00:00:25.370 align:start position:0% is like you know two parts one is generally<00:00:24.240> talking<00:00:24.449> about<00:00:24.750> how<00:00:24.960> we<00:00:25.019> are 00:00:25.370 --> 00:00:25.380 align:start position:0% generally talking about how we are 00:00:25.380 --> 00:00:28.970 align:start position:0% generally talking about how we are viewing<00:00:25.740> this<00:00:26.150> trusted<00:00:27.150> compute<00:00:27.779> play<00:00:28.740> in<00:00:28.859> the 00:00:28.970 --> 00:00:28.980 align:start position:0% viewing this trusted compute play in the 00:00:28.980 --> 00:00:30.890 align:start position:0% viewing this trusted compute play in the space<00:00:29.220> and<00:00:29.460> then<00:00:29.939> the<00:00:30.060> RDS<00:00:30.510> will<00:00:30.660> drive 00:00:30.890 --> 00:00:30.900 align:start position:0% space and then the RDS will drive 00:00:30.900 --> 00:00:33.139 align:start position:0% space and then the RDS will drive complete<00:00:31.560> it<00:00:31.710> with<00:00:31.890> a<00:00:31.920> concrete<00:00:32.369> example<00:00:32.579> of 00:00:33.139 --> 00:00:33.149 align:start position:0% complete it with a concrete example of 00:00:33.149 --> 00:00:35.209 align:start position:0% complete it with a concrete example of something<00:00:33.780> that<00:00:33.930> we<00:00:34.170> are<00:00:34.230> doing<00:00:34.320> and<00:00:34.620> then 00:00:35.209 --> 00:00:35.219 align:start position:0% something that we are doing and then 00:00:35.219 --> 00:00:37.850 align:start position:0% something that we are doing and then tomorrow<00:00:35.840> there's<00:00:36.840> a<00:00:36.899> breakout<00:00:37.230> session<00:00:37.440> that 00:00:37.850 --> 00:00:37.860 align:start position:0% tomorrow there's a breakout session that 00:00:37.860 --> 00:00:40.959 align:start position:0% tomorrow there's a breakout session that will<00:00:38.010> go<00:00:38.190> into<00:00:38.370> a<00:00:38.700> whole<00:00:38.969> bunch<00:00:39.210> of<00:00:39.329> more 00:00:40.959 --> 00:00:40.969 align:start position:0% will go into a whole bunch of more 00:00:40.969 --> 00:00:44.000 align:start position:0% will go into a whole bunch of more applications<00:00:41.969> in<00:00:42.120> this<00:00:42.300> space<00:00:42.540> so<00:00:43.079> with<00:00:43.860> that 00:00:44.000 --> 00:00:44.010 align:start position:0% applications in this space so with that 00:00:44.010 --> 00:00:49.670 align:start position:0% applications in this space so with that I'll<00:00:44.489> get<00:00:44.730> started<00:00:47.120> so<00:00:48.170> together 00:00:49.670 --> 00:00:49.680 align:start position:0% I'll get started so together 00:00:49.680 --> 00:00:51.740 align:start position:0% I'll get started so together there<00:00:50.460> are<00:00:50.550> like<00:00:50.670> lots<00:00:50.940> of<00:00:51.059> definitions<00:00:51.270> of 00:00:51.740 --> 00:00:51.750 align:start position:0% there are like lots of definitions of 00:00:51.750 --> 00:00:54.740 align:start position:0% there are like lots of definitions of when<00:00:51.870> it<00:00:51.989> comes<00:00:52.199> to<00:00:52.320> trusted<00:00:52.620> compute<00:00:53.010> so<00:00:53.719> so<00:00:54.719> I 00:00:54.740 --> 00:00:54.750 align:start position:0% when it comes to trusted compute so so I 00:00:54.750 --> 00:00:56.869 align:start position:0% when it comes to trusted compute so so I thought<00:00:55.110> that<00:00:55.289> would<00:00:55.410> start<00:00:55.710> off<00:00:55.860> with<00:00:56.070> you 00:00:56.869 --> 00:00:56.879 align:start position:0% thought that would start off with you 00:00:56.879 --> 00:00:59.540 align:start position:0% thought that would start off with you know<00:00:56.940> having<00:00:57.690> a<00:00:57.780> level<00:00:57.930> set<00:00:58.230> of<00:00:58.379> what<00:00:58.800> it<00:00:58.980> means 00:00:59.540 --> 00:00:59.550 align:start position:0% know having a level set of what it means 00:00:59.550 --> 00:01:03.229 align:start position:0% know having a level set of what it means right<00:01:00.559> typically<00:01:01.559> when<00:01:01.739> I<00:01:02.090> talk<00:01:03.090> about 00:01:03.229 --> 00:01:03.239 align:start position:0% right typically when I talk about 00:01:03.239 --> 00:01:05.630 align:start position:0% right typically when I talk about trusted<00:01:03.629> compute<00:01:03.960> I<00:01:04.080> say<00:01:04.290> that<00:01:04.500> hey<00:01:04.860> it's<00:01:05.430> a 00:01:05.630 --> 00:01:05.640 align:start position:0% trusted compute I say that hey it's a 00:01:05.640 --> 00:01:10.850 align:start position:0% trusted compute I say that hey it's a place<00:01:06.210> on<00:01:06.630> your<00:01:06.960> PC<00:01:07.409> or<00:01:07.619> on<00:01:07.920> your<00:01:09.020> server<00:01:10.020> where 00:01:10.850 --> 00:01:10.860 align:start position:0% place on your PC or on your server where 00:01:10.860 --> 00:01:13.429 align:start position:0% place on your PC or on your server where software<00:01:11.640> can<00:01:11.760> execute<00:01:12.439> without 00:01:13.429 --> 00:01:13.439 align:start position:0% software can execute without 00:01:13.439 --> 00:01:15.289 align:start position:0% software can execute without interference<00:01:14.010> and<00:01:14.189> without<00:01:14.549> enter<00:01:14.790> any 00:01:15.289 --> 00:01:15.299 align:start position:0% interference and without enter any 00:01:15.299 --> 00:01:17.600 align:start position:0% interference and without enter any external<00:01:15.750> interference<00:01:16.320> so<00:01:16.979> to<00:01:17.040> drive<00:01:17.460> the 00:01:17.600 --> 00:01:17.610 align:start position:0% external interference so to drive the 00:01:17.610 --> 00:01:21.109 align:start position:0% external interference so to drive the point<00:01:17.790> home<00:01:18.920> so<00:01:19.920> think<00:01:20.340> of<00:01:20.460> the<00:01:20.670> Box<00:01:20.909> in<00:01:21.090> the 00:01:21.109 --> 00:01:21.119 align:start position:0% point home so think of the Box in the 00:01:21.119 --> 00:01:23.060 align:start position:0% point home so think of the Box in the big<00:01:21.330> box<00:01:21.509> in<00:01:21.689> the<00:01:21.780> middle<00:01:22.020> is<00:01:22.200> your<00:01:22.229> PC<00:01:22.830> or<00:01:22.920> your 00:01:23.060 --> 00:01:23.070 align:start position:0% big box in the middle is your PC or your 00:01:23.070 --> 00:01:25.130 align:start position:0% big box in the middle is your PC or your server<00:01:23.340> it<00:01:23.850> has<00:01:24.060> two<00:01:24.509> parts<00:01:24.720> to<00:01:24.990> it 00:01:25.130 --> 00:01:25.140 align:start position:0% server it has two parts to it 00:01:25.140 --> 00:01:28.190 align:start position:0% server it has two parts to it trusted<00:01:26.040> and<00:01:26.189> untrusted<00:01:26.759> the<00:01:26.939> part<00:01:27.570> and<00:01:27.780> the 00:01:28.190 --> 00:01:28.200 align:start position:0% trusted and untrusted the part and the 00:01:28.200 --> 00:01:30.020 align:start position:0% trusted and untrusted the part and the blue<00:01:28.409> is<00:01:28.560> the<00:01:28.590> trusted<00:01:28.979> part<00:01:29.250> or<00:01:29.490> the<00:01:29.700> trusted 00:01:30.020 --> 00:01:30.030 align:start position:0% blue is the trusted part or the trusted 00:01:30.030 --> 00:01:32.960 align:start position:0% blue is the trusted part or the trusted compute<00:01:30.420> and<00:01:30.630> inside<00:01:31.500> there<00:01:31.860> you<00:01:32.460> can<00:01:32.700> run 00:01:32.960 --> 00:01:32.970 align:start position:0% compute and inside there you can run 00:01:32.970 --> 00:01:36.260 align:start position:0% compute and inside there you can run your<00:01:33.509> code<00:01:34.259> and<00:01:34.590> or<00:01:35.369> you<00:01:35.610> can<00:01:35.790> have<00:01:36.060> your 00:01:36.260 --> 00:01:36.270 align:start position:0% your code and or you can have your 00:01:36.270 --> 00:01:39.069 align:start position:0% your code and or you can have your secrets<00:01:36.780> like<00:01:37.049> keys<00:01:37.320> and<00:01:37.680> any<00:01:38.460> sensitive<00:01:38.970> data 00:01:39.069 --> 00:01:39.079 align:start position:0% secrets like keys and any sensitive data 00:01:39.079 --> 00:01:41.390 align:start position:0% secrets like keys and any sensitive data all<00:01:40.079> of<00:01:40.140> that<00:01:40.439> can<00:01:40.619> be<00:01:40.740> processed<00:01:40.920> in<00:01:41.280> this 00:01:41.390 --> 00:01:41.400 align:start position:0% all of that can be processed in this 00:01:41.400 --> 00:01:44.030 align:start position:0% all of that can be processed in this blue<00:01:41.670> part<00:01:41.990> and<00:01:42.990> it<00:01:43.200> will<00:01:43.320> be<00:01:43.439> secure<00:01:43.770> even 00:01:44.030 --> 00:01:44.040 align:start position:0% blue part and it will be secure even 00:01:44.040 --> 00:01:46.819 align:start position:0% blue part and it will be secure even though<00:01:44.280> in<00:01:44.460> the<00:01:44.610> white<00:01:44.790> past<00:01:45.119> around<00:01:45.570> it<00:01:45.829> you 00:01:46.819 --> 00:01:46.829 align:start position:0% though in the white past around it you 00:01:46.829 --> 00:01:49.370 align:start position:0% though in the white past around it you may<00:01:47.009> have<00:01:47.040> a<00:01:47.250> malware<00:01:47.909> or<00:01:48.299> something<00:01:48.960> else<00:01:49.140> is 00:01:49.370 --> 00:01:49.380 align:start position:0% may have a malware or something else is 00:01:49.380 --> 00:01:52.510 align:start position:0% may have a malware or something else is owning<00:01:49.829> that<00:01:50.009> system<00:01:50.430> so<00:01:50.909> it<00:01:51.869> gives<00:01:52.110> you<00:01:52.229> that 00:01:52.510 --> 00:01:52.520 align:start position:0% owning that system so it gives you that 00:01:52.520 --> 00:01:56.060 align:start position:0% owning that system so it gives you that isolation<00:01:53.630> on<00:01:54.630> a<00:01:54.689> on<00:01:55.170> and<00:01:55.500> off<00:01:55.680> the<00:01:55.860> shelf 00:01:56.060 --> 00:01:56.070 align:start position:0% isolation on a on and off the shelf 00:01:56.070 --> 00:01:59.330 align:start position:0% isolation on a on and off the shelf platforms<00:01:56.729> and<00:01:57.320> the<00:01:58.320> other<00:01:58.740> side<00:01:58.979> of<00:01:59.159> it<00:01:59.280> is 00:01:59.330 --> 00:01:59.340 align:start position:0% platforms and the other side of it is 00:01:59.340 --> 00:02:01.550 align:start position:0% platforms and the other side of it is like<00:01:59.640> you<00:01:59.759> know<00:01:59.880> the<00:02:00.600> final<00:02:01.049> point<00:02:01.229> there<00:02:01.409> is 00:02:01.550 --> 00:02:01.560 align:start position:0% like you know the final point there is 00:02:01.560 --> 00:02:03.679 align:start position:0% like you know the final point there is that<00:02:01.710> whatever<00:02:02.579> it<00:02:02.880> does<00:02:03.030> it<00:02:03.270> gives<00:02:03.479> you<00:02:03.570> an 00:02:03.679 --> 00:02:03.689 align:start position:0% that whatever it does it gives you an 00:02:03.689 --> 00:02:07.249 align:start position:0% that whatever it does it gives you an attestation<00:02:03.960> to<00:02:04.640> what<00:02:05.640> happened<00:02:06.110> so<00:02:07.110> that 00:02:07.249 --> 00:02:07.259 align:start position:0% attestation to what happened so that 00:02:07.259 --> 00:02:09.260 align:start position:0% attestation to what happened so that like<00:02:07.439> anybody<00:02:07.829> can<00:02:07.950> verify<00:02:08.190> the<00:02:08.459> that<00:02:09.119> the 00:02:09.260 --> 00:02:09.270 align:start position:0% like anybody can verify the that the 00:02:09.270 --> 00:02:10.790 align:start position:0% like anybody can verify the that the result<00:02:09.539> really<00:02:09.720> did<00:02:10.050> happen<00:02:10.229> inside<00:02:10.649> the 00:02:10.790 --> 00:02:10.800 align:start position:0% result really did happen inside the 00:02:10.800 --> 00:02:12.440 align:start position:0% result really did happen inside the trusted<00:02:11.129> compute<00:02:11.520> and 00:02:12.440 --> 00:02:12.450 align:start position:0% trusted compute and 00:02:12.450 --> 00:02:14.570 align:start position:0% trusted compute and and<00:02:12.780> these<00:02:12.930> instructions<00:02:13.560> did<00:02:13.740> actually<00:02:14.160> get 00:02:14.570 --> 00:02:14.580 align:start position:0% and these instructions did actually get 00:02:14.580 --> 00:02:15.890 align:start position:0% and these instructions did actually get executed 00:02:15.890 --> 00:02:15.900 align:start position:0% executed 00:02:15.900 --> 00:02:19.940 align:start position:0% executed so<00:02:16.550> I<00:02:17.550> worked<00:02:18.210> for<00:02:18.360> Intel<00:02:18.630> and<00:02:18.780> Intel's<00:02:19.230> one<00:02:19.830> of 00:02:19.940 --> 00:02:19.950 align:start position:0% so I worked for Intel and Intel's one of 00:02:19.950 --> 00:02:23.060 align:start position:0% so I worked for Intel and Intel's one of the<00:02:20.300> popular<00:02:21.350> trusted<00:02:22.350> computes<00:02:22.710> out<00:02:22.860> there 00:02:23.060 --> 00:02:23.070 align:start position:0% the popular trusted computes out there 00:02:23.070 --> 00:02:26.720 align:start position:0% the popular trusted computes out there as<00:02:23.280> Intel<00:02:23.910> SGX<00:02:24.060> and<00:02:25.100> more<00:02:26.100> than<00:02:26.250> happy<00:02:26.460> to<00:02:26.490> talk 00:02:26.720 --> 00:02:26.730 align:start position:0% as Intel SGX and more than happy to talk 00:02:26.730 --> 00:02:30.290 align:start position:0% as Intel SGX and more than happy to talk about<00:02:26.910> it<00:02:27.890> in<00:02:28.890> general<00:02:29.070> but<00:02:29.790> today<00:02:30.030> we<00:02:30.240> will 00:02:30.290 --> 00:02:30.300 align:start position:0% about it in general but today we will 00:02:30.300 --> 00:02:32.090 align:start position:0% about it in general but today we will talk<00:02:30.540> in<00:02:30.780> generally<00:02:31.290> in<00:02:31.470> terms<00:02:31.500> of<00:02:31.890> Tharsis 00:02:32.090 --> 00:02:32.100 align:start position:0% talk in generally in terms of Tharsis 00:02:32.100 --> 00:02:34.540 align:start position:0% talk in generally in terms of Tharsis computer<00:02:32.580> and<00:02:32.730> then<00:02:33.120> there<00:02:33.270> are<00:02:33.360> these<00:02:33.510> other 00:02:34.540 --> 00:02:34.550 align:start position:0% computer and then there are these other 00:02:34.550 --> 00:02:36.940 align:start position:0% computer and then there are these other variants<00:02:35.550> of<00:02:35.640> trusted<00:02:35.970> compute<00:02:36.330> based<00:02:36.510> on 00:02:36.940 --> 00:02:36.950 align:start position:0% variants of trusted compute based on 00:02:36.950 --> 00:02:40.460 align:start position:0% variants of trusted compute based on Zeki<00:02:37.950> approves<00:02:38.220> and<00:02:38.490> MPC<00:02:39.170> those<00:02:40.170> are<00:02:40.320> also 00:02:40.460 --> 00:02:40.470 align:start position:0% Zeki approves and MPC those are also 00:02:40.470 --> 00:02:44.240 align:start position:0% Zeki approves and MPC those are also there<00:02:40.770> that<00:02:41.340> can<00:02:42.120> be<00:02:42.390> used<00:02:42.630> to<00:02:43.530> apply<00:02:43.860> to<00:02:43.890> the 00:02:44.240 --> 00:02:44.250 align:start position:0% there that can be used to apply to the 00:02:44.250 --> 00:02:46.070 align:start position:0% there that can be used to apply to the concepts<00:02:44.760> that<00:02:44.850> we<00:02:45.030> are<00:02:45.090> going<00:02:45.210> to<00:02:45.330> be<00:02:45.450> talking 00:02:46.070 --> 00:02:46.080 align:start position:0% concepts that we are going to be talking 00:02:46.080 --> 00:02:50.570 align:start position:0% concepts that we are going to be talking here<00:02:46.610> so<00:02:47.990> so<00:02:48.990> this<00:02:49.170> so<00:02:50.010> the<00:02:50.130> first<00:02:50.340> thing<00:02:50.460> we 00:02:50.570 --> 00:02:50.580 align:start position:0% here so so this so the first thing we 00:02:50.580 --> 00:02:52.730 align:start position:0% here so so this so the first thing we were<00:02:50.700> saying<00:02:50.970> is<00:02:51.090> like<00:02:51.210> you<00:02:51.300> know<00:02:51.390> hey<00:02:51.540> how<00:02:52.170> do 00:02:52.730 --> 00:02:52.740 align:start position:0% were saying is like you know hey how do 00:02:52.740 --> 00:02:55.100 align:start position:0% were saying is like you know hey how do we<00:02:52.890> how<00:02:53.100> can<00:02:53.310> does<00:02:54.090> it<00:02:54.240> compute<00:02:54.600> play<00:02:54.840> in<00:02:54.990> this 00:02:55.100 --> 00:02:55.110 align:start position:0% we how can does it compute play in this 00:02:55.110 --> 00:02:56.690 align:start position:0% we how can does it compute play in this space<00:02:55.410> and<00:02:55.710> there<00:02:55.860> are<00:02:55.920> lots<00:02:56.100> of<00:02:56.220> questions 00:02:56.690 --> 00:02:56.700 align:start position:0% space and there are lots of questions 00:02:56.700 --> 00:03:02.240 align:start position:0% space and there are lots of questions and<00:02:58.220> you<00:02:59.220> guys<00:02:59.400> probably<00:02:59.970> seen<00:03:00.420> this<00:03:01.250> this 00:03:02.240 --> 00:03:02.250 align:start position:0% and you guys probably seen this this 00:03:02.250 --> 00:03:05.090 align:start position:0% and you guys probably seen this this picture<00:03:02.700> and<00:03:03.660> what<00:03:04.230> we<00:03:04.350> are<00:03:04.440> asking<00:03:04.770> is<00:03:04.920> like 00:03:05.090 --> 00:03:05.100 align:start position:0% picture and what we are asking is like 00:03:05.100 --> 00:03:07.970 align:start position:0% picture and what we are asking is like you<00:03:05.190> know<00:03:05.310> hey<00:03:05.460> how<00:03:05.670> can<00:03:06.260> you<00:03:07.260> know<00:03:07.410> if<00:03:07.740> we 00:03:07.970 --> 00:03:07.980 align:start position:0% you know hey how can you know if we 00:03:07.980 --> 00:03:10.340 align:start position:0% you know hey how can you know if we address<00:03:08.880> it<00:03:09.030> computer<00:03:09.480> this<00:03:09.660> world<00:03:09.900> right<00:03:10.290> now 00:03:10.340 --> 00:03:10.350 align:start position:0% address it computer this world right now 00:03:10.350 --> 00:03:13.190 align:start position:0% address it computer this world right now the<00:03:10.560> problem<00:03:11.040> is<00:03:11.160> like<00:03:11.760> you<00:03:11.910> can<00:03:12.090> get<00:03:12.300> two<00:03:13.050> of 00:03:13.190 --> 00:03:13.200 align:start position:0% the problem is like you can get two of 00:03:13.200 --> 00:03:15.200 align:start position:0% the problem is like you can get two of the<00:03:13.410> three<00:03:13.590> not<00:03:13.860> all<00:03:14.040> three<00:03:14.340> so<00:03:14.760> can<00:03:15.000> we 00:03:15.200 --> 00:03:15.210 align:start position:0% the three not all three so can we 00:03:15.210 --> 00:03:17.210 align:start position:0% the three not all three so can we basically<00:03:15.570> do<00:03:16.440> something<00:03:16.800> with<00:03:16.920> trusted 00:03:17.210 --> 00:03:17.220 align:start position:0% basically do something with trusted 00:03:17.220 --> 00:03:20.060 align:start position:0% basically do something with trusted compute<00:03:17.550> so<00:03:17.730> that<00:03:17.910> we<00:03:18.120> can<00:03:18.330> you<00:03:19.290> know<00:03:19.410> make<00:03:20.040> it 00:03:20.060 --> 00:03:20.070 align:start position:0% compute so that we can you know make it 00:03:20.070 --> 00:03:22.580 align:start position:0% compute so that we can you know make it possible<00:03:20.489> to<00:03:20.790> achieve<00:03:21.000> all<00:03:21.330> three<00:03:21.600> so<00:03:22.320> that<00:03:22.440> we 00:03:22.580 --> 00:03:22.590 align:start position:0% possible to achieve all three so that we 00:03:22.590 --> 00:03:23.660 align:start position:0% possible to achieve all three so that we have<00:03:22.739> scalability<00:03:23.370> we<00:03:23.520> have 00:03:23.660 --> 00:03:23.670 align:start position:0% have scalability we have 00:03:23.670 --> 00:03:25.460 align:start position:0% have scalability we have decentralization<00:03:24.360> and<00:03:24.630> we<00:03:24.900> have<00:03:25.080> the 00:03:25.460 --> 00:03:25.470 align:start position:0% decentralization and we have the 00:03:25.470 --> 00:03:27.410 align:start position:0% decentralization and we have the security<00:03:25.980> so<00:03:26.430> let's<00:03:26.610> talk<00:03:26.790> about<00:03:26.850> each<00:03:27.270> of 00:03:27.410 --> 00:03:27.420 align:start position:0% security so let's talk about each of 00:03:27.420 --> 00:03:31.070 align:start position:0% security so let's talk about each of these<00:03:27.540> things<00:03:28.070> briefly<00:03:29.070> and<00:03:29.690> and<00:03:30.690> then<00:03:30.900> see 00:03:31.070 --> 00:03:31.080 align:start position:0% these things briefly and and then see 00:03:31.080 --> 00:03:32.060 align:start position:0% these things briefly and and then see how<00:03:31.170> that<00:03:31.350> goes 00:03:32.060 --> 00:03:32.070 align:start position:0% how that goes 00:03:32.070 --> 00:03:34.300 align:start position:0% how that goes so<00:03:32.459> first<00:03:32.670> of<00:03:32.790> all<00:03:32.910> like<00:03:33.060> the<00:03:33.239> security's 00:03:34.300 --> 00:03:34.310 align:start position:0% so first of all like the security's 00:03:34.310 --> 00:03:36.620 align:start position:0% so first of all like the security's plainly<00:03:35.310> is<00:03:35.370> like<00:03:35.580> transactions<00:03:36.090> per<00:03:36.239> second 00:03:36.620 --> 00:03:36.630 align:start position:0% plainly is like transactions per second 00:03:36.630 --> 00:03:39.470 align:start position:0% plainly is like transactions per second or<00:03:36.750> seconds<00:03:37.110> per<00:03:37.260> transaction<00:03:38.209> we<00:03:39.209> believe 00:03:39.470 --> 00:03:39.480 align:start position:0% or seconds per transaction we believe 00:03:39.480 --> 00:03:42.770 align:start position:0% or seconds per transaction we believe that<00:03:39.690> you<00:03:39.810> know<00:03:39.930> given<00:03:40.170> the<00:03:40.970> you<00:03:41.970> know<00:03:42.120> the<00:03:42.630> way 00:03:42.770 --> 00:03:42.780 align:start position:0% that you know given the you know the way 00:03:42.780 --> 00:03:44.570 align:start position:0% that you know given the you know the way these<00:03:43.080> trusted<00:03:43.410> computers<00:03:43.830> work<00:03:44.010> in<00:03:44.160> terms<00:03:44.370> of 00:03:44.570 --> 00:03:44.580 align:start position:0% these trusted computers work in terms of 00:03:44.580 --> 00:03:46.220 align:start position:0% these trusted computers work in terms of you<00:03:44.760> have<00:03:44.820> the<00:03:45.030> integrity<00:03:45.300> of<00:03:45.570> the<00:03:45.780> execution 00:03:46.220 --> 00:03:46.230 align:start position:0% you have the integrity of the execution 00:03:46.230 --> 00:03:48.500 align:start position:0% you have the integrity of the execution and<00:03:46.350> things<00:03:46.500> like<00:03:46.650> that<00:03:46.709> you<00:03:47.489> can<00:03:47.760> combine<00:03:48.330> it 00:03:48.500 --> 00:03:48.510 align:start position:0% and things like that you can combine it 00:03:48.510 --> 00:03:51.080 align:start position:0% and things like that you can combine it with<00:03:48.690> constructs<00:03:49.470> like<00:03:49.590> you<00:03:49.890> know<00:03:50.090> plasma 00:03:51.080 --> 00:03:51.090 align:start position:0% with constructs like you know plasma 00:03:51.090 --> 00:03:53.449 align:start position:0% with constructs like you know plasma chains<00:03:51.360> and<00:03:51.690> side<00:03:52.290> chains<00:03:52.590> and<00:03:52.739> you<00:03:53.250> can 00:03:53.449 --> 00:03:53.459 align:start position:0% chains and side chains and you can 00:03:53.459 --> 00:03:56.090 align:start position:0% chains and side chains and you can achieve<00:03:53.790> a<00:03:54.330> lot<00:03:54.420> of<00:03:55.260> scalability<00:03:55.680> in<00:03:55.920> that 00:03:56.090 --> 00:03:56.100 align:start position:0% achieve a lot of scalability in that 00:03:56.100 --> 00:03:58.400 align:start position:0% achieve a lot of scalability in that space<00:03:56.340> and<00:03:56.630> there<00:03:57.630> has<00:03:57.780> been<00:03:57.810> work<00:03:58.050> in<00:03:58.260> the 00:03:58.400 --> 00:03:58.410 align:start position:0% space and there has been work in the 00:03:58.410 --> 00:04:01.729 align:start position:0% space and there has been work in the space<00:03:58.650> have<00:03:58.860> done<00:03:59.580> and<00:03:59.989> some<00:04:00.989> of<00:04:01.080> that<00:04:01.260> will<00:04:01.680> be 00:04:01.729 --> 00:04:01.739 align:start position:0% space have done and some of that will be 00:04:01.739 --> 00:04:03.560 align:start position:0% space have done and some of that will be talked<00:04:02.100> about<00:04:02.220> in<00:04:02.580> the<00:04:02.730> breakout<00:04:03.060> tomorrow 00:04:03.560 --> 00:04:03.570 align:start position:0% talked about in the breakout tomorrow 00:04:03.570 --> 00:04:06.410 align:start position:0% talked about in the breakout tomorrow the<00:04:04.500> other<00:04:04.650> side<00:04:04.890> of<00:04:05.040> the<00:04:05.160> thing<00:04:05.340> is<00:04:05.520> that<00:04:05.700> the 00:04:06.410 --> 00:04:06.420 align:start position:0% the other side of the thing is that the 00:04:06.420 --> 00:04:09.050 align:start position:0% the other side of the thing is that the security<00:04:06.959> is<00:04:07.950> there<00:04:08.489> are<00:04:08.550> two<00:04:08.670> ways<00:04:08.850> to<00:04:08.880> look 00:04:09.050 --> 00:04:09.060 align:start position:0% security is there are two ways to look 00:04:09.060 --> 00:04:11.860 align:start position:0% security is there are two ways to look at<00:04:09.300> the<00:04:09.420> security<00:04:09.630> one<00:04:10.080> is<00:04:10.260> security<00:04:11.040> of<00:04:11.220> your 00:04:11.860 --> 00:04:11.870 align:start position:0% at the security one is security of your 00:04:11.870 --> 00:04:14.030 align:start position:0% at the security one is security of your consensus<00:04:12.870> and<00:04:13.140> things<00:04:13.320> like<00:04:13.470> that<00:04:13.680> and<00:04:13.890> one 00:04:14.030 --> 00:04:14.040 align:start position:0% consensus and things like that and one 00:04:14.040 --> 00:04:16.750 align:start position:0% consensus and things like that and one is<00:04:14.190> the<00:04:14.280> security<00:04:14.550> of<00:04:15.019> around<00:04:16.019> it<00:04:16.260> you<00:04:16.380> know 00:04:16.750 --> 00:04:16.760 align:start position:0% is the security of around it you know 00:04:16.760 --> 00:04:19.099 align:start position:0% is the security of around it you know transaction<00:04:17.760> ordering<00:04:18.600> and<00:04:18.780> things<00:04:18.930> like 00:04:19.099 --> 00:04:19.109 align:start position:0% transaction ordering and things like 00:04:19.109 --> 00:04:21.620 align:start position:0% transaction ordering and things like that<00:04:19.169> so<00:04:19.560> again<00:04:20.280> going<00:04:20.729> to<00:04:20.910> the<00:04:21.030> property<00:04:21.450> that 00:04:21.620 --> 00:04:21.630 align:start position:0% that so again going to the property that 00:04:21.630 --> 00:04:23.930 align:start position:0% that so again going to the property that you<00:04:21.870> have<00:04:22.140> you<00:04:22.710> can<00:04:22.890> trust<00:04:23.130> like<00:04:23.370> hey<00:04:23.580> if<00:04:23.789> I 00:04:23.930 --> 00:04:23.940 align:start position:0% you have you can trust like hey if I 00:04:23.940 --> 00:04:24.800 align:start position:0% you have you can trust like hey if I asked 00:04:24.800 --> 00:04:24.810 align:start position:0% asked 00:04:24.810 --> 00:04:27.590 align:start position:0% asked trusted<00:04:25.590> computer<00:04:25.950> to<00:04:26.040> do<00:04:26.190> 1+1<00:04:26.820> it<00:04:27.060> did<00:04:27.240> do<00:04:27.419> one 00:04:27.590 --> 00:04:27.600 align:start position:0% trusted computer to do 1+1 it did do one 00:04:27.600 --> 00:04:31.970 align:start position:0% trusted computer to do 1+1 it did do one plus<00:04:27.840> one<00:04:28.400> so<00:04:29.450> so<00:04:30.450> based<00:04:30.690> on<00:04:30.870> that<00:04:30.930> we<00:04:31.740> are 00:04:31.970 --> 00:04:31.980 align:start position:0% plus one so so based on that we are 00:04:31.980 --> 00:04:34.360 align:start position:0% plus one so so based on that we are doing<00:04:32.400> some<00:04:32.580> work<00:04:32.610> and<00:04:33.000> that's<00:04:33.510> work<00:04:34.290> that 00:04:34.360 --> 00:04:34.370 align:start position:0% doing some work and that's work that 00:04:34.370 --> 00:04:39.290 align:start position:0% doing some work and that's work that andreas<00:04:35.370> will<00:04:36.889> talk<00:04:37.889> about<00:04:38.040> in<00:04:38.760> a<00:04:38.880> little<00:04:39.000> bit 00:04:39.290 --> 00:04:39.300 align:start position:0% andreas will talk about in a little bit 00:04:39.300 --> 00:04:42.040 align:start position:0% andreas will talk about in a little bit and<00:04:39.450> finally<00:04:40.200> the<00:04:40.440> decentralization<00:04:41.160> right 00:04:42.040 --> 00:04:42.050 align:start position:0% and finally the decentralization right 00:04:42.050 --> 00:04:45.320 align:start position:0% and finally the decentralization right there's<00:04:43.050> lot<00:04:43.470> of<00:04:43.620> this<00:04:43.740> conversation<00:04:44.639> is<00:04:45.270> like 00:04:45.320 --> 00:04:45.330 align:start position:0% there's lot of this conversation is like 00:04:45.330 --> 00:04:48.379 align:start position:0% there's lot of this conversation is like if<00:04:45.780> you<00:04:45.930> rely<00:04:46.590> on<00:04:46.650> trusted<00:04:47.040> compute<00:04:47.400> you<00:04:47.580> let 00:04:48.379 --> 00:04:48.389 align:start position:0% if you rely on trusted compute you let 00:04:48.389 --> 00:04:50.030 align:start position:0% if you rely on trusted compute you let go<00:04:48.600> of<00:04:48.720> decentralization<00:04:49.440> and<00:04:49.740> this<00:04:49.919> is 00:04:50.030 --> 00:04:50.040 align:start position:0% go of decentralization and this is 00:04:50.040 --> 00:04:51.200 align:start position:0% go of decentralization and this is something<00:04:50.340> that<00:04:50.370> we<00:04:50.639> would<00:04:50.700> like<00:04:50.880> to<00:04:51.030> have<00:04:51.180> a 00:04:51.200 --> 00:04:51.210 align:start position:0% something that we would like to have a 00:04:51.210 --> 00:04:54.890 align:start position:0% something that we would like to have a conversation<00:04:51.450> around<00:04:51.960> because<00:04:53.180> if<00:04:54.180> you<00:04:54.510> take 00:04:54.890 --> 00:04:54.900 align:start position:0% conversation around because if you take 00:04:54.900 --> 00:04:57.230 align:start position:0% conversation around because if you take trusted<00:04:55.440> compute<00:04:55.800> the<00:04:56.430> way<00:04:56.550> I<00:04:56.580> view<00:04:56.790> a 00:04:57.230 --> 00:04:57.240 align:start position:0% trusted compute the way I view a 00:04:57.240 --> 00:04:59.060 align:start position:0% trusted compute the way I view a decentralization<00:04:57.960> the<00:04:58.260> way<00:04:58.350> I<00:04:58.380> have<00:04:58.620> you<00:04:58.950> know 00:04:59.060 --> 00:04:59.070 align:start position:0% decentralization the way I have you know 00:04:59.070 --> 00:05:01.820 align:start position:0% decentralization the way I have you know read<00:04:59.610> it<00:04:59.760> in<00:04:59.940> various<00:05:00.270> articles<00:05:00.870> like<00:05:01.470> on 00:05:01.820 --> 00:05:01.830 align:start position:0% read it in various articles like on 00:05:01.830 --> 00:05:03.200 align:start position:0% read it in various articles like on showering<00:05:02.280> and<00:05:02.550> things<00:05:02.610> like<00:05:02.820> that<00:05:02.880> it's 00:05:03.200 --> 00:05:03.210 align:start position:0% showering and things like that it's 00:05:03.210 --> 00:05:04.760 align:start position:0% showering and things like that it's about<00:05:03.450> you<00:05:03.510> know<00:05:03.900> two<00:05:03.960> properties<00:05:04.470> like 00:05:04.760 --> 00:05:04.770 align:start position:0% about you know two properties like 00:05:04.770 --> 00:05:07.090 align:start position:0% about you know two properties like censorship<00:05:05.490> resistance<00:05:06.090> and<00:05:06.330> permitting<00:05:06.870> and 00:05:07.090 --> 00:05:07.100 align:start position:0% censorship resistance and permitting and 00:05:07.100 --> 00:05:10.640 align:start position:0% censorship resistance and permitting and we<00:05:08.100> look<00:05:08.250> at<00:05:08.370> tacit<00:05:09.000> compute<00:05:09.389> it<00:05:10.229> doesn't<00:05:10.530> have 00:05:10.640 --> 00:05:10.650 align:start position:0% we look at tacit compute it doesn't have 00:05:10.650 --> 00:05:12.409 align:start position:0% we look at tacit compute it doesn't have either<00:05:10.919> of<00:05:11.130> these<00:05:11.310> properties 00:05:12.409 --> 00:05:12.419 align:start position:0% either of these properties 00:05:12.419 --> 00:05:16.690 align:start position:0% either of these properties anybody<00:05:13.229> can<00:05:13.940> you<00:05:14.940> can<00:05:15.120> it<00:05:15.510> my<00:05:15.720> PC<00:05:16.080> has 00:05:16.690 --> 00:05:16.700 align:start position:0% anybody can you can it my PC has 00:05:16.700 --> 00:05:19.159 align:start position:0% anybody can you can it my PC has distrusted<00:05:17.700> computing<00:05:18.240> all<00:05:18.570> of<00:05:18.690> your<00:05:18.840> pcs 00:05:19.159 --> 00:05:19.169 align:start position:0% distrusted computing all of your pcs 00:05:19.169 --> 00:05:21.050 align:start position:0% distrusted computing all of your pcs have<00:05:19.350> have<00:05:19.770> it<00:05:19.889> and<00:05:20.100> you<00:05:20.220> are<00:05:20.370> free<00:05:20.550> to<00:05:20.700> run<00:05:20.880> it 00:05:21.050 --> 00:05:21.060 align:start position:0% have have it and you are free to run it 00:05:21.060 --> 00:05:23.330 align:start position:0% have have it and you are free to run it so<00:05:21.570> there<00:05:21.750> is<00:05:21.870> no<00:05:22.050> that<00:05:22.590> you<00:05:22.770> need<00:05:22.950> to<00:05:23.130> have<00:05:23.310> a 00:05:23.330 --> 00:05:23.340 align:start position:0% so there is no that you need to have a 00:05:23.340 --> 00:05:25.460 align:start position:0% so there is no that you need to have a special<00:05:23.910> hardware<00:05:24.540> from<00:05:24.690> somewhere<00:05:25.169> to<00:05:25.350> do 00:05:25.460 --> 00:05:25.470 align:start position:0% special hardware from somewhere to do 00:05:25.470 --> 00:05:29.590 align:start position:0% special hardware from somewhere to do these<00:05:25.710> kinds<00:05:26.040> of<00:05:26.100> things<00:05:26.310> and<00:05:27.180> then<00:05:28.070> UK<00:05:29.070> and 00:05:29.590 --> 00:05:29.600 align:start position:0% these kinds of things and then UK and 00:05:29.600 --> 00:05:32.090 align:start position:0% these kinds of things and then UK and initially<00:05:30.600> yes<00:05:30.840> there<00:05:31.140> were<00:05:31.350> some<00:05:31.620> controls 00:05:32.090 --> 00:05:32.100 align:start position:0% initially yes there were some controls 00:05:32.100 --> 00:05:34.010 align:start position:0% initially yes there were some controls in<00:05:32.280> terms<00:05:32.490> of<00:05:32.640> like<00:05:32.820> you<00:05:32.940> know<00:05:32.970> who<00:05:33.539> all<00:05:33.750> gets 00:05:34.010 --> 00:05:34.020 align:start position:0% in terms of like you know who all gets 00:05:34.020 --> 00:05:35.810 align:start position:0% in terms of like you know who all gets to<00:05:34.229> run<00:05:34.410> software<00:05:34.680> in<00:05:35.070> this<00:05:35.190> space<00:05:35.460> and<00:05:35.640> things 00:05:35.810 --> 00:05:35.820 align:start position:0% to run software in this space and things 00:05:35.820 --> 00:05:38.870 align:start position:0% to run software in this space and things like<00:05:35.970> that<00:05:36.030> and<00:05:36.770> what<00:05:37.770> at<00:05:37.950> least<00:05:38.220> for<00:05:38.400> Intel<00:05:38.729> we 00:05:38.870 --> 00:05:38.880 align:start position:0% like that and what at least for Intel we 00:05:38.880 --> 00:05:41.360 align:start position:0% like that and what at least for Intel we have<00:05:38.910> worked<00:05:39.240> to<00:05:39.680> you<00:05:40.680> know<00:05:40.770> actually<00:05:41.100> remove 00:05:41.360 --> 00:05:41.370 align:start position:0% have worked to you know actually remove 00:05:41.370 --> 00:05:43.279 align:start position:0% have worked to you know actually remove all<00:05:41.490> of<00:05:41.640> those<00:05:41.789> controls<00:05:42.510> in<00:05:42.720> terms<00:05:42.960> of<00:05:43.110> like 00:05:43.279 --> 00:05:43.289 align:start position:0% all of those controls in terms of like 00:05:43.289 --> 00:05:44.960 align:start position:0% all of those controls in terms of like we<00:05:43.470> know<00:05:43.590> we<00:05:43.740> are<00:05:43.890> no<00:05:44.100> longer<00:05:44.310> going<00:05:44.550> to<00:05:44.760> be<00:05:44.880> in 00:05:44.960 --> 00:05:44.970 align:start position:0% we know we are no longer going to be in 00:05:44.970 --> 00:05:47.630 align:start position:0% we know we are no longer going to be in the<00:05:45.120> middle<00:05:45.390> of<00:05:45.539> like<00:05:46.350> who<00:05:46.710> gets<00:05:46.890> to<00:05:47.160> execute 00:05:47.630 --> 00:05:47.640 align:start position:0% the middle of like who gets to execute 00:05:47.640 --> 00:05:49.400 align:start position:0% the middle of like who gets to execute and<00:05:47.940> who<00:05:48.150> gets<00:05:48.360> to<00:05:48.539> a<00:05:48.570> test<00:05:48.870> and<00:05:49.080> things<00:05:49.200> like 00:05:49.400 --> 00:05:49.410 align:start position:0% and who gets to a test and things like 00:05:49.410 --> 00:05:53.390 align:start position:0% and who gets to a test and things like that<00:05:49.590> so<00:05:49.770> we<00:05:50.280> have<00:05:51.110> you<00:05:52.110> know<00:05:52.229> worked<00:05:52.770> to<00:05:53.070> be<00:05:53.220> in 00:05:53.390 --> 00:05:53.400 align:start position:0% that so we have you know worked to be in 00:05:53.400 --> 00:05:56.110 align:start position:0% that so we have you know worked to be in last<00:05:53.610> one<00:05:53.880> year<00:05:54.060> since<00:05:54.660> last<00:05:54.750> DEFCON<00:05:55.440> three<00:05:55.680> to 00:05:56.110 --> 00:05:56.120 align:start position:0% last one year since last DEFCON three to 00:05:56.120 --> 00:05:59.629 align:start position:0% last one year since last DEFCON three to you<00:05:57.120> know<00:05:57.210> ease<00:05:57.450> out<00:05:57.630> all<00:05:57.870> of<00:05:57.990> that<00:05:58.139> stuff<00:05:58.639> but 00:05:59.629 --> 00:05:59.639 align:start position:0% you know ease out all of that stuff but 00:05:59.639 --> 00:06:02.240 align:start position:0% you know ease out all of that stuff but but<00:06:00.600> there<00:06:00.780> is<00:06:00.960> this<00:06:01.500> thing<00:06:01.710> like<00:06:01.919> like 00:06:02.240 --> 00:06:02.250 align:start position:0% but there is this thing like like 00:06:02.250 --> 00:06:05.690 align:start position:0% but there is this thing like like anything<00:06:02.760> in<00:06:03.090> this<00:06:03.389> space<00:06:03.710> as<00:06:04.710> we<00:06:05.160> go<00:06:05.400> further 00:06:05.690 --> 00:06:05.700 align:start position:0% anything in this space as we go further 00:06:05.700 --> 00:06:09.200 align:start position:0% anything in this space as we go further as<00:06:06.630> we<00:06:06.840> go<00:06:07.020> and<00:06:07.110> you<00:06:07.229> use<00:06:08.160> it<00:06:08.190> in<00:06:08.460> your<00:06:08.520> spaces 00:06:09.200 --> 00:06:09.210 align:start position:0% as we go and you use it in your spaces 00:06:09.210 --> 00:06:11.629 align:start position:0% as we go and you use it in your spaces there's<00:06:09.720> always<00:06:09.930> that<00:06:10.350> you<00:06:10.500> know<00:06:10.530> hey<00:06:11.160> things 00:06:11.629 --> 00:06:11.639 align:start position:0% there's always that you know hey things 00:06:11.639 --> 00:06:13.879 align:start position:0% there's always that you know hey things can<00:06:11.880> get<00:06:12.090> hacked<00:06:12.389> which<00:06:12.690> is<00:06:12.870> which<00:06:13.320> we<00:06:13.560> view<00:06:13.710> is 00:06:13.879 --> 00:06:13.889 align:start position:0% can get hacked which is which we view is 00:06:13.889 --> 00:06:16.310 align:start position:0% can get hacked which is which we view is no<00:06:14.130> different<00:06:14.490> than<00:06:14.639> a<00:06:15.270> particular<00:06:15.960> hashing 00:06:16.310 --> 00:06:16.320 align:start position:0% no different than a particular hashing 00:06:16.320 --> 00:06:18.860 align:start position:0% no different than a particular hashing algorithm<00:06:16.770> getting<00:06:17.039> hacked<00:06:17.270> as<00:06:18.270> long<00:06:18.539> as<00:06:18.720> we 00:06:18.860 --> 00:06:18.870 align:start position:0% algorithm getting hacked as long as we 00:06:18.870 --> 00:06:21.200 align:start position:0% algorithm getting hacked as long as we there's<00:06:19.289> a<00:06:19.350> commitment<00:06:19.710> to<00:06:19.950> basically<00:06:20.700> fix<00:06:21.000> it 00:06:21.200 --> 00:06:21.210 align:start position:0% there's a commitment to basically fix it 00:06:21.210 --> 00:06:23.180 align:start position:0% there's a commitment to basically fix it and<00:06:21.360> then<00:06:21.960> there<00:06:22.440> is<00:06:22.590> this<00:06:22.710> notion<00:06:22.950> that 00:06:23.180 --> 00:06:23.190 align:start position:0% and then there is this notion that 00:06:23.190 --> 00:06:25.640 align:start position:0% and then there is this notion that Hoover<00:06:24.150> is<00:06:24.479> the<00:06:24.600> provider<00:06:24.960> of<00:06:25.139> this<00:06:25.289> trusted 00:06:25.640 --> 00:06:25.650 align:start position:0% Hoover is the provider of this trusted 00:06:25.650 --> 00:06:28.129 align:start position:0% Hoover is the provider of this trusted compute<00:06:26.070> has<00:06:26.639> done<00:06:26.940> the<00:06:27.120> due<00:06:27.389> diligence<00:06:27.570> or 00:06:28.129 --> 00:06:28.139 align:start position:0% compute has done the due diligence or 00:06:28.139 --> 00:06:30.320 align:start position:0% compute has done the due diligence or and<00:06:28.680> is<00:06:28.950> willing<00:06:29.250> to<00:06:29.280> do<00:06:29.639> continue<00:06:30.150> due 00:06:30.320 --> 00:06:30.330 align:start position:0% and is willing to do continue due 00:06:30.330 --> 00:06:32.870 align:start position:0% and is willing to do continue due diligence<00:06:30.780> to<00:06:30.870> make<00:06:30.990> sure<00:06:31.320> that<00:06:31.530> it<00:06:31.830> is<00:06:32.130> you 00:06:32.870 --> 00:06:32.880 align:start position:0% diligence to make sure that it is you 00:06:32.880 --> 00:06:36.260 align:start position:0% diligence to make sure that it is you know<00:06:33.030> delivering<00:06:33.960> on<00:06:34.080> its<00:06:34.110> promises<00:06:35.060> so<00:06:36.060> in 00:06:36.260 --> 00:06:36.270 align:start position:0% know delivering on its promises so in 00:06:36.270 --> 00:06:38.390 align:start position:0% know delivering on its promises so in general<00:06:36.450> we<00:06:36.810> believe<00:06:36.870> that<00:06:37.320> you<00:06:37.470> know<00:06:37.500> it 00:06:38.390 --> 00:06:38.400 align:start position:0% general we believe that you know it 00:06:38.400 --> 00:06:40.400 align:start position:0% general we believe that you know it should<00:06:38.550> compute<00:06:38.850> if<00:06:39.090> it<00:06:39.300> used<00:06:40.139> in<00:06:40.320> a 00:06:40.400 --> 00:06:40.410 align:start position:0% should compute if it used in a 00:06:40.410 --> 00:06:44.409 align:start position:0% should compute if it used in a particular<00:06:40.860> you<00:06:41.850> know<00:06:42.000> ways<00:06:42.470> can<00:06:43.470> be<00:06:43.680> a<00:06:43.710> very 00:06:44.409 --> 00:06:44.419 align:start position:0% particular you know ways can be a very 00:06:44.419 --> 00:06:48.170 align:start position:0% particular you know ways can be a very helpful<00:06:45.419> tool<00:06:45.930> in<00:06:46.259> addressing<00:06:47.070> and<00:06:47.759> easing 00:06:48.170 --> 00:06:48.180 align:start position:0% helpful tool in addressing and easing 00:06:48.180 --> 00:06:51.529 align:start position:0% helpful tool in addressing and easing this<00:06:48.360> try<00:06:48.900> Lima<00:06:49.460> problem<00:06:50.460> that<00:06:51.030> that<00:06:51.389> we 00:06:51.529 --> 00:06:51.539 align:start position:0% this try Lima problem that that we 00:06:51.539 --> 00:06:53.330 align:start position:0% this try Lima problem that that we haven't<00:06:51.780> blocked<00:06:51.960> chains<00:06:52.199> can<00:06:52.650> just<00:06:53.009> help<00:06:53.190> it 00:06:53.330 --> 00:06:53.340 align:start position:0% haven't blocked chains can just help it 00:06:53.340 --> 00:06:56.719 align:start position:0% haven't blocked chains can just help it to<00:06:53.460> you<00:06:54.030> know<00:06:54.150> get<00:06:54.960> deployed<00:06:55.289> very<00:06:55.530> easily<00:06:56.400> in 00:06:56.719 --> 00:06:56.729 align:start position:0% to you know get deployed very easily in 00:06:56.729 --> 00:07:00.170 align:start position:0% to you know get deployed very easily in some<00:06:56.940> cases<00:06:57.180> so<00:06:58.550> so<00:06:59.550> what<00:06:59.669> I<00:06:59.699> will<00:06:59.850> do<00:06:59.940> is<00:07:00.060> like 00:07:00.170 --> 00:07:00.180 align:start position:0% some cases so so what I will do is like 00:07:00.180 --> 00:07:02.120 align:start position:0% some cases so so what I will do is like quickly<00:07:00.570> you<00:07:00.750> know<00:07:00.870> before<00:07:01.380> I<00:07:01.410> jump<00:07:01.740> into<00:07:01.889> like 00:07:02.120 --> 00:07:02.130 align:start position:0% quickly you know before I jump into like 00:07:02.130 --> 00:07:04.700 align:start position:0% quickly you know before I jump into like you<00:07:02.250> know<00:07:02.340> some<00:07:03.000> of<00:07:03.030> the<00:07:03.210> ideas<00:07:04.050> we<00:07:04.259> have<00:07:04.470> and 00:07:04.700 --> 00:07:04.710 align:start position:0% you know some of the ideas we have and 00:07:04.710 --> 00:07:07.279 align:start position:0% you know some of the ideas we have and then<00:07:04.800> a<00:07:04.830> concrete<00:07:05.190> idea<00:07:05.310> just<00:07:05.789> to<00:07:06.630> level<00:07:06.780> set<00:07:07.080> a 00:07:07.279 --> 00:07:07.289 align:start position:0% then a concrete idea just to level set a 00:07:07.289 --> 00:07:09.710 align:start position:0% then a concrete idea just to level set a common<00:07:08.160> design<00:07:08.430> pattern<00:07:08.910> around<00:07:09.150> us<00:07:09.509> so<00:07:09.660> you 00:07:09.710 --> 00:07:09.720 align:start position:0% common design pattern around us so you 00:07:09.720 --> 00:07:12.170 align:start position:0% common design pattern around us so you have<00:07:09.960> a<00:07:09.990> transit<00:07:10.380> compute<00:07:10.770> it<00:07:10.979> can<00:07:11.190> be<00:07:11.340> in<00:07:11.400> a<00:07:11.520> PC 00:07:12.170 --> 00:07:12.180 align:start position:0% have a transit compute it can be in a PC 00:07:12.180 --> 00:07:15.050 align:start position:0% have a transit compute it can be in a PC or<00:07:12.419> in<00:07:12.600> a<00:07:12.690> server<00:07:13.470> you<00:07:14.190> have<00:07:14.340> some<00:07:14.550> function 00:07:15.050 --> 00:07:15.060 align:start position:0% or in a server you have some function 00:07:15.060 --> 00:07:17.960 align:start position:0% or in a server you have some function that<00:07:15.210> you<00:07:15.750> can<00:07:15.930> basically<00:07:16.169> you<00:07:17.130> know<00:07:17.310> deploy 00:07:17.960 --> 00:07:17.970 align:start position:0% that you can basically you know deploy 00:07:17.970 --> 00:07:20.510 align:start position:0% that you can basically you know deploy to<00:07:18.240> it<00:07:18.360> and<00:07:18.630> that<00:07:19.229> that<00:07:19.650> typically<00:07:20.070> we<00:07:20.220> call<00:07:20.370> an 00:07:20.510 --> 00:07:20.520 align:start position:0% to it and that that typically we call an 00:07:20.520 --> 00:07:22.850 align:start position:0% to it and that that typically we call an unclear<00:07:20.940> and<00:07:21.780> that<00:07:22.050> function<00:07:22.560> can<00:07:22.710> be 00:07:22.850 --> 00:07:22.860 align:start position:0% unclear and that function can be 00:07:22.860 --> 00:07:25.700 align:start position:0% unclear and that function can be anything<00:07:23.100> it<00:07:23.340> could<00:07:23.490> be<00:07:24.410> matching<00:07:25.410> the 00:07:25.700 --> 00:07:25.710 align:start position:0% anything it could be matching the 00:07:25.710 --> 00:07:27.860 align:start position:0% anything it could be matching the fingerprint<00:07:26.250> data<00:07:26.430> against<00:07:26.880> template<00:07:27.570> or 00:07:27.860 --> 00:07:27.870 align:start position:0% fingerprint data against template or 00:07:27.870 --> 00:07:30.080 align:start position:0% fingerprint data against template or finding<00:07:28.380> a<00:07:28.530> particular<00:07:29.460> pattern<00:07:29.669> in 00:07:30.080 --> 00:07:30.090 align:start position:0% finding a particular pattern in 00:07:30.090 --> 00:07:32.600 align:start position:0% finding a particular pattern in something<00:07:30.479> it<00:07:30.690> can<00:07:30.870> be<00:07:30.900> anything<00:07:31.169> the<00:07:31.590> idea<00:07:32.490> is 00:07:32.600 --> 00:07:32.610 align:start position:0% something it can be anything the idea is 00:07:32.610 --> 00:07:35.420 align:start position:0% something it can be anything the idea is that<00:07:32.639> you<00:07:32.970> can<00:07:33.590> you<00:07:34.590> know<00:07:34.710> you<00:07:34.949> can<00:07:35.130> be<00:07:35.250> sure 00:07:35.420 --> 00:07:35.430 align:start position:0% that you can you know you can be sure 00:07:35.430 --> 00:07:37.430 align:start position:0% that you can you know you can be sure that<00:07:35.699> particular<00:07:36.210> sets<00:07:36.780> of<00:07:36.900> instructions 00:07:37.430 --> 00:07:37.440 align:start position:0% that particular sets of instructions 00:07:37.440 --> 00:07:39.499 align:start position:0% that particular sets of instructions were<00:07:37.590> executed<00:07:38.190> and<00:07:38.310> that<00:07:38.370> your<00:07:39.000> data<00:07:39.210> that 00:07:39.499 --> 00:07:39.509 align:start position:0% were executed and that your data that 00:07:39.509 --> 00:07:41.689 align:start position:0% were executed and that your data that whatever<00:07:39.870> you<00:07:39.990> gave<00:07:40.169> it<00:07:40.320> was<00:07:40.699> handled 00:07:41.689 --> 00:07:41.699 align:start position:0% whatever you gave it was handled 00:07:41.699 --> 00:07:44.480 align:start position:0% whatever you gave it was handled confidentiality<00:07:42.389> and<00:07:42.930> then<00:07:43.590> there<00:07:44.280> can<00:07:44.460> be 00:07:44.480 --> 00:07:44.490 align:start position:0% confidentiality and then there can be 00:07:44.490 --> 00:07:46.550 align:start position:0% confidentiality and then there can be any<00:07:44.760> requester<00:07:45.330> who<00:07:45.479> can<00:07:45.690> provide<00:07:46.050> two<00:07:46.320> things 00:07:46.550 --> 00:07:46.560 align:start position:0% any requester who can provide two things 00:07:46.560 --> 00:07:48.140 align:start position:0% any requester who can provide two things one<00:07:46.800> is<00:07:46.949> the<00:07:47.130> data<00:07:47.340> on<00:07:47.460> which<00:07:47.760> they<00:07:48.000> would<00:07:48.120> like 00:07:48.140 --> 00:07:48.150 align:start position:0% one is the data on which they would like 00:07:48.150 --> 00:07:50.180 align:start position:0% one is the data on which they would like to<00:07:48.419> operate<00:07:48.690> that<00:07:49.260> algorithm<00:07:49.530> operate<00:07:50.070> upon 00:07:50.180 --> 00:07:50.190 align:start position:0% to operate that algorithm operate upon 00:07:50.190 --> 00:07:53.000 align:start position:0% to operate that algorithm operate upon and<00:07:50.520> plus<00:07:51.180> you<00:07:51.690> can<00:07:51.870> also<00:07:52.020> provide<00:07:52.590> your<00:07:52.800> own 00:07:53.000 --> 00:07:53.010 align:start position:0% and plus you can also provide your own 00:07:53.010 --> 00:07:55.520 align:start position:0% and plus you can also provide your own identity<00:07:53.250> that<00:07:53.849> the<00:07:54.150> Enclave<00:07:54.990> or<00:07:55.349> the 00:07:55.520 --> 00:07:55.530 align:start position:0% identity that the Enclave or the 00:07:55.530 --> 00:07:57.230 align:start position:0% identity that the Enclave or the function<00:07:56.159> will<00:07:56.310> check<00:07:56.610> before<00:07:57.060> even 00:07:57.230 --> 00:07:57.240 align:start position:0% function will check before even 00:07:57.240 --> 00:08:03.230 align:start position:0% function will check before even executing<00:07:57.930> your<00:07:59.180> your<00:08:00.180> request<00:08:00.539> and<00:08:01.070> then<00:08:02.240> and 00:08:03.230 --> 00:08:03.240 align:start position:0% executing your your request and then and 00:08:03.240 --> 00:08:04.939 align:start position:0% executing your your request and then and result<00:08:03.599> of<00:08:03.720> this<00:08:03.870> all<00:08:04.110> of<00:08:04.260> this<00:08:04.349> processes 00:08:04.939 --> 00:08:04.949 align:start position:0% result of this all of this processes 00:08:04.949 --> 00:08:06.409 align:start position:0% result of this all of this processes like<00:08:05.070> you<00:08:05.220> have<00:08:05.370> data<00:08:05.520> you<00:08:05.789> have<00:08:05.940> algorithm 00:08:06.409 --> 00:08:06.419 align:start position:0% like you have data you have algorithm 00:08:06.419 --> 00:08:08.330 align:start position:0% like you have data you have algorithm all<00:08:06.630> executing<00:08:07.199> inside<00:08:07.500> this<00:08:07.650> container<00:08:08.130> and 00:08:08.330 --> 00:08:08.340 align:start position:0% all executing inside this container and 00:08:08.340 --> 00:08:11.480 align:start position:0% all executing inside this container and secure<00:08:09.300> container<00:08:09.690> and<00:08:09.840> you<00:08:10.349> come<00:08:10.590> output<00:08:11.340> is 00:08:11.480 --> 00:08:11.490 align:start position:0% secure container and you come output is 00:08:11.490 --> 00:08:15.439 align:start position:0% secure container and you come output is this<00:08:11.699> attested<00:08:12.300> result<00:08:13.080> that<00:08:13.710> anybody<00:08:14.449> can 00:08:15.439 --> 00:08:15.449 align:start position:0% this attested result that anybody can 00:08:15.449 --> 00:08:18.770 align:start position:0% this attested result that anybody can basically<00:08:15.780> validate<00:08:17.300> it<00:08:18.300> can<00:08:18.539> be<00:08:18.690> the 00:08:18.770 --> 00:08:18.780 align:start position:0% basically validate it can be the 00:08:18.780 --> 00:08:20.450 align:start position:0% basically validate it can be the requester<00:08:19.260> or<00:08:19.470> it<00:08:19.590> can<00:08:19.740> be<00:08:19.860> somebody<00:08:20.070> else<00:08:20.370> who 00:08:20.450 --> 00:08:20.460 align:start position:0% requester or it can be somebody else who 00:08:20.460 --> 00:08:22.670 align:start position:0% requester or it can be somebody else who you<00:08:20.699> are<00:08:20.789> targeting<00:08:20.970> with<00:08:21.360> that<00:08:21.510> and<00:08:21.720> finally 00:08:22.670 --> 00:08:22.680 align:start position:0% you are targeting with that and finally 00:08:22.680 --> 00:08:24.230 align:start position:0% you are targeting with that and finally if<00:08:22.889> you<00:08:23.010> are<00:08:23.039> running<00:08:23.400> this<00:08:23.520> trusted<00:08:23.880> compute 00:08:24.230 --> 00:08:24.240 align:start position:0% if you are running this trusted compute 00:08:24.240 --> 00:08:26.890 align:start position:0% if you are running this trusted compute in<00:08:24.330> the<00:08:24.419> context<00:08:24.810> of<00:08:24.960> a<00:08:25.050> PC<00:08:25.440> you<00:08:26.070> do<00:08:26.250> have<00:08:26.490> this 00:08:26.890 --> 00:08:26.900 align:start position:0% in the context of a PC you do have this 00:08:26.900 --> 00:08:30.409 align:start position:0% in the context of a PC you do have this human<00:08:28.190> secure<00:08:29.190> what<00:08:29.669> we<00:08:29.789> call<00:08:29.940> protected 00:08:30.409 --> 00:08:30.419 align:start position:0% human secure what we call protected 00:08:30.419 --> 00:08:32.750 align:start position:0% human secure what we call protected transaction<00:08:30.900> display<00:08:31.229> and<00:08:31.409> that's<00:08:32.070> basically 00:08:32.750 --> 00:08:32.760 align:start position:0% transaction display and that's basically 00:08:32.760 --> 00:08:35.510 align:start position:0% transaction display and that's basically is<00:08:32.909> that<00:08:33.169> before<00:08:34.169> the<00:08:34.500> transaction<00:08:34.830> is 00:08:35.510 --> 00:08:35.520 align:start position:0% is that before the transaction is 00:08:35.520 --> 00:08:38.240 align:start position:0% is that before the transaction is completed<00:08:36.089> you<00:08:36.599> can<00:08:36.659> prompt<00:08:37.260> a<00:08:37.349> user<00:08:37.380> for<00:08:38.039> some 00:08:38.240 --> 00:08:38.250 align:start position:0% completed you can prompt a user for some 00:08:38.250 --> 00:08:40.310 align:start position:0% completed you can prompt a user for some kind<00:08:38.729> of<00:08:38.820> a<00:08:38.909> pin<00:08:39.150> or<00:08:39.300> something<00:08:39.750> like<00:08:39.870> that<00:08:39.930> so 00:08:40.310 --> 00:08:40.320 align:start position:0% kind of a pin or something like that so 00:08:40.320 --> 00:08:44.329 align:start position:0% kind of a pin or something like that so that<00:08:40.469> you<00:08:41.039> have<00:08:41.640> user<00:08:42.270> has<00:08:42.539> all<00:08:42.750> the<00:08:43.339> control 00:08:44.329 --> 00:08:44.339 align:start position:0% that you have user has all the control 00:08:44.339 --> 00:08:46.130 align:start position:0% that you have user has all the control at<00:08:44.730> the<00:08:44.910> end<00:08:44.940> of<00:08:45.120> the<00:08:45.209> day<00:08:45.330> what<00:08:45.510> happened<00:08:45.870> so 00:08:46.130 --> 00:08:46.140 align:start position:0% at the end of the day what happened so 00:08:46.140 --> 00:08:49.980 align:start position:0% at the end of the day what happened so you<00:08:46.170> can<00:08:47.750> build<00:08:48.750> that<00:08:48.959> in 00:08:49.980 --> 00:08:49.990 align:start position:0% you can build that in 00:08:49.990 --> 00:08:53.730 align:start position:0% you can build that in the<00:08:50.110> tomorrow<00:08:50.800> a<00:08:51.399> June<00:08:51.820> breakout<00:08:52.320> Ledger<00:08:53.320> who 00:08:53.730 --> 00:08:53.740 align:start position:0% the tomorrow a June breakout Ledger who 00:08:53.740 --> 00:08:56.940 align:start position:0% the tomorrow a June breakout Ledger who have<00:08:53.890> built<00:08:54.070> a<00:08:54.190> wallet<00:08:54.580> on<00:08:54.610> top<00:08:54.940> of<00:08:55.560> STX<00:08:56.560> we'll 00:08:56.940 --> 00:08:56.950 align:start position:0% have built a wallet on top of STX we'll 00:08:56.950 --> 00:08:59.550 align:start position:0% have built a wallet on top of STX we'll talk<00:08:57.160> about<00:08:57.310> some<00:08:57.610> of<00:08:57.640> this<00:08:58.170> so<00:08:59.170> in<00:08:59.350> general 00:08:59.550 --> 00:08:59.560 align:start position:0% talk about some of this so in general 00:08:59.560 --> 00:09:01.560 align:start position:0% talk about some of this so in general what<00:08:59.770> what<00:09:00.130> we<00:09:00.220> believe<00:09:00.459> is<00:09:00.580> like<00:09:00.700> if<00:09:00.820> you<00:09:00.850> step 00:09:01.560 --> 00:09:01.570 align:start position:0% what what we believe is like if you step 00:09:01.570 --> 00:09:05.250 align:start position:0% what what we believe is like if you step up<00:09:01.779> from<00:09:02.440> all<00:09:02.920> of<00:09:03.100> this<00:09:03.540> this<00:09:04.540> thing<00:09:04.750> enables 00:09:05.250 --> 00:09:05.260 align:start position:0% up from all of this this thing enables 00:09:05.260 --> 00:09:07.650 align:start position:0% up from all of this this thing enables this<00:09:05.470> notion<00:09:05.740> that<00:09:05.980> I<00:09:06.370> can<00:09:06.970> prove<00:09:07.360> that 00:09:07.650 --> 00:09:07.660 align:start position:0% this notion that I can prove that 00:09:07.660 --> 00:09:10.980 align:start position:0% this notion that I can prove that something<00:09:08.470> I<00:09:08.680> did<00:09:09.160> or<00:09:09.339> I<00:09:09.399> did<00:09:09.730> not<00:09:09.940> and<00:09:10.209> I<00:09:10.750> can 00:09:10.980 --> 00:09:10.990 align:start position:0% something I did or I did not and I can 00:09:10.990 --> 00:09:13.199 align:start position:0% something I did or I did not and I can be<00:09:11.110> kind<00:09:11.529> of<00:09:11.620> sure<00:09:11.830> that<00:09:12.070> the<00:09:12.459> data<00:09:12.670> that<00:09:13.180> I 00:09:13.199 --> 00:09:13.209 align:start position:0% be kind of sure that the data that I 00:09:13.209 --> 00:09:15.630 align:start position:0% be kind of sure that the data that I gave<00:09:13.510> it<00:09:13.630> to<00:09:13.660> you<00:09:13.899> didn't<00:09:14.529> leak<00:09:14.740> that's<00:09:15.310> what 00:09:15.630 --> 00:09:15.640 align:start position:0% gave it to you didn't leak that's what 00:09:15.640 --> 00:09:17.940 align:start position:0% gave it to you didn't leak that's what this<00:09:15.790> trusted<00:09:16.149> compute<00:09:16.510> is<00:09:16.630> giving<00:09:17.589> at<00:09:17.800> the 00:09:17.940 --> 00:09:17.950 align:start position:0% this trusted compute is giving at the 00:09:17.950 --> 00:09:18.600 align:start position:0% this trusted compute is giving at the end<00:09:18.100> of<00:09:18.190> the<00:09:18.279> day 00:09:18.600 --> 00:09:18.610 align:start position:0% end of the day 00:09:18.610 --> 00:09:22.740 align:start position:0% end of the day so<00:09:18.850> now<00:09:19.029> let's<00:09:20.190> jump<00:09:21.190> into<00:09:21.370> one<00:09:22.029> one<00:09:22.570> last 00:09:22.740 --> 00:09:22.750 align:start position:0% so now let's jump into one one last 00:09:22.750 --> 00:09:25.290 align:start position:0% so now let's jump into one one last light<00:09:22.990> from<00:09:23.200> me<00:09:23.410> is<00:09:23.620> how<00:09:24.190> could<00:09:24.730> it<00:09:24.850> now 00:09:25.290 --> 00:09:25.300 align:start position:0% light from me is how could it now 00:09:25.300 --> 00:09:27.449 align:start position:0% light from me is how could it now connect<00:09:25.690> with<00:09:25.950> aetherium<00:09:26.950> specifically 00:09:27.449 --> 00:09:27.459 align:start position:0% connect with aetherium specifically 00:09:27.459 --> 00:09:30.480 align:start position:0% connect with aetherium specifically cerium<00:09:27.820> to<00:09:27.970> dato<00:09:28.200> this<00:09:29.200> picture<00:09:29.529> probably<00:09:29.770> you 00:09:30.480 --> 00:09:30.490 align:start position:0% cerium to dato this picture probably you 00:09:30.490 --> 00:09:32.519 align:start position:0% cerium to dato this picture probably you know<00:09:30.640> most<00:09:31.360> of<00:09:31.480> the<00:09:31.570> people<00:09:31.720> have<00:09:31.959> seen<00:09:32.200> it 00:09:32.519 --> 00:09:32.529 align:start position:0% know most of the people have seen it 00:09:32.529 --> 00:09:36.210 align:start position:0% know most of the people have seen it it's<00:09:33.029> of<00:09:34.029> the<00:09:34.209> medium<00:09:34.510> articles<00:09:34.959> and<00:09:35.140> the<00:09:35.770> main 00:09:36.210 --> 00:09:36.220 align:start position:0% it's of the medium articles and the main 00:09:36.220 --> 00:09:38.310 align:start position:0% it's of the medium articles and the main thing<00:09:36.370> really<00:09:36.580> here<00:09:36.910> is<00:09:37.089> that<00:09:37.240> this<00:09:37.690> whole<00:09:37.899> you 00:09:38.310 --> 00:09:38.320 align:start position:0% thing really here is that this whole you 00:09:38.320 --> 00:09:39.870 align:start position:0% thing really here is that this whole you know<00:09:38.440> today<00:09:38.680> morning<00:09:38.920> like<00:09:39.279> in<00:09:39.459> the<00:09:39.550> morning 00:09:39.870 --> 00:09:39.880 align:start position:0% know today morning like in the morning 00:09:39.880 --> 00:09:41.639 align:start position:0% know today morning like in the morning Vitalik<00:09:40.510> talked<00:09:40.720> about<00:09:40.959> this<00:09:41.110> beacon<00:09:41.410> chain 00:09:41.639 --> 00:09:41.649 align:start position:0% Vitalik talked about this beacon chain 00:09:41.649 --> 00:09:43.139 align:start position:0% Vitalik talked about this beacon chain and<00:09:41.860> things<00:09:42.010> like<00:09:42.160> that<00:09:42.339> so<00:09:42.550> there's<00:09:42.760> four 00:09:43.139 --> 00:09:43.149 align:start position:0% and things like that so there's four 00:09:43.149 --> 00:09:45.630 align:start position:0% and things like that so there's four tiers<00:09:43.450> of<00:09:43.660> you<00:09:44.470> know<00:09:44.589> abstraction<00:09:45.339> or<00:09:45.430> the 00:09:45.630 --> 00:09:45.640 align:start position:0% tiers of you know abstraction or the 00:09:45.640 --> 00:09:49.079 align:start position:0% tiers of you know abstraction or the layering<00:09:46.300> of<00:09:46.570> this<00:09:46.750> whole<00:09:47.790> etherium<00:09:48.790> to<00:09:48.910> dot<00:09:49.060> o 00:09:49.079 --> 00:09:49.089 align:start position:0% layering of this whole etherium to dot o 00:09:49.089 --> 00:09:52.170 align:start position:0% layering of this whole etherium to dot o in<00:09:49.779> this<00:09:50.110> there<00:09:50.800> two<00:09:51.010> two<00:09:51.370> things<00:09:51.580> here<00:09:51.850> one<00:09:52.000> is 00:09:52.170 --> 00:09:52.180 align:start position:0% in this there two two things here one is 00:09:52.180 --> 00:09:54.449 align:start position:0% in this there two two things here one is this<00:09:52.330> beacon<00:09:52.660> chain<00:09:52.899> which<00:09:53.140> I<00:09:53.350> in<00:09:53.860> my<00:09:54.070> view<00:09:54.310> is 00:09:54.449 --> 00:09:54.459 align:start position:0% this beacon chain which I in my view is 00:09:54.459 --> 00:09:56.280 align:start position:0% this beacon chain which I in my view is like<00:09:54.610> it's<00:09:54.790> the<00:09:54.970> control<00:09:55.329> plane<00:09:55.600> that's 00:09:56.280 --> 00:09:56.290 align:start position:0% like it's the control plane that's 00:09:56.290 --> 00:09:57.780 align:start position:0% like it's the control plane that's making<00:09:56.980> sure<00:09:57.160> that<00:09:57.339> things<00:09:57.579> are<00:09:57.760> happening 00:09:57.780 --> 00:09:57.790 align:start position:0% making sure that things are happening 00:09:57.790 --> 00:10:00.300 align:start position:0% making sure that things are happening the<00:09:58.270> right<00:09:58.480> way<00:09:58.690> and<00:09:58.839> then<00:09:59.350> at<00:09:59.589> the<00:09:59.800> bottom<00:09:59.950> is 00:10:00.300 --> 00:10:00.310 align:start position:0% the right way and then at the bottom is 00:10:00.310 --> 00:10:03.180 align:start position:0% the right way and then at the bottom is your<00:10:00.420> execution<00:10:01.420> plane<00:10:01.630> so<00:10:02.260> in<00:10:02.709> the<00:10:02.920> control 00:10:03.180 --> 00:10:03.190 align:start position:0% your execution plane so in the control 00:10:03.190 --> 00:10:06.300 align:start position:0% your execution plane so in the control plane<00:10:03.490> this<00:10:04.089> is<00:10:04.240> where<00:10:04.480> you<00:10:05.110> have<00:10:05.350> the 00:10:06.300 --> 00:10:06.310 align:start position:0% plane this is where you have the 00:10:06.310 --> 00:10:09.300 align:start position:0% plane this is where you have the validators<00:10:06.940> and<00:10:07.209> verification<00:10:07.899> and<00:10:08.170> you<00:10:09.160> know 00:10:09.300 --> 00:10:09.310 align:start position:0% validators and verification and you know 00:10:09.310 --> 00:10:12.210 align:start position:0% validators and verification and you know all<00:10:10.060> the<00:10:10.270> crypto<00:10:10.570> economics<00:10:11.020> going<00:10:11.320> on<00:10:11.500> in 00:10:12.210 --> 00:10:12.220 align:start position:0% all the crypto economics going on in 00:10:12.220 --> 00:10:14.100 align:start position:0% all the crypto economics going on in terms<00:10:12.430> of<00:10:12.610> like<00:10:12.820> you<00:10:12.850> know<00:10:13.060> making<00:10:13.540> sure<00:10:13.839> that 00:10:14.100 --> 00:10:14.110 align:start position:0% terms of like you know making sure that 00:10:14.110 --> 00:10:15.690 align:start position:0% terms of like you know making sure that you<00:10:14.320> know<00:10:14.350> everybody<00:10:15.100> is<00:10:15.220> doing<00:10:15.339> the<00:10:15.520> right 00:10:15.690 --> 00:10:15.700 align:start position:0% you know everybody is doing the right 00:10:15.700 --> 00:10:17.340 align:start position:0% you know everybody is doing the right thing<00:10:15.970> and<00:10:16.209> if<00:10:16.360> somebody<00:10:16.720> is<00:10:16.839> not<00:10:17.020> doing<00:10:17.260> the 00:10:17.340 --> 00:10:17.350 align:start position:0% thing and if somebody is not doing the 00:10:17.350 --> 00:10:17.819 align:start position:0% thing and if somebody is not doing the right<00:10:17.380> thing 00:10:17.819 --> 00:10:17.829 align:start position:0% right thing 00:10:17.829 --> 00:10:19.889 align:start position:0% right thing penalizing<00:10:18.399> them<00:10:18.730> and<00:10:18.910> all<00:10:19.360> of<00:10:19.480> that<00:10:19.510> you<00:10:19.810> know 00:10:19.889 --> 00:10:19.899 align:start position:0% penalizing them and all of that you know 00:10:19.899 --> 00:10:21.680 align:start position:0% penalizing them and all of that you know keeping<00:10:20.200> the<00:10:20.350> equilibrium<00:10:20.950> and<00:10:21.040> keeping<00:10:21.430> the 00:10:21.680 --> 00:10:21.690 align:start position:0% keeping the equilibrium and keeping the 00:10:21.690 --> 00:10:25.620 align:start position:0% keeping the equilibrium and keeping the system<00:10:22.690> working<00:10:23.200> so<00:10:24.060> right<00:10:25.060> now<00:10:25.300> the<00:10:25.360> focus 00:10:25.620 --> 00:10:25.630 align:start position:0% system working so right now the focus 00:10:25.630 --> 00:10:30.720 align:start position:0% system working so right now the focus really<00:10:25.959> is<00:10:26.140> on<00:10:26.320> hey<00:10:28.320> you<00:10:29.320> know<00:10:29.440> you<00:10:30.160> know<00:10:30.279> you 00:10:30.720 --> 00:10:30.730 align:start position:0% really is on hey you know you know you 00:10:30.730 --> 00:10:32.310 align:start position:0% really is on hey you know you know you did<00:10:30.940> something<00:10:30.970> wrong<00:10:31.450> okay<00:10:31.870> I<00:10:31.899> will<00:10:32.050> penalize 00:10:32.310 --> 00:10:32.320 align:start position:0% did something wrong okay I will penalize 00:10:32.320 --> 00:10:35.490 align:start position:0% did something wrong okay I will penalize you<00:10:32.880> but<00:10:33.880> what<00:10:34.029> we<00:10:34.180> are<00:10:34.270> saying<00:10:34.480> is<00:10:34.750> with<00:10:35.260> if 00:10:35.490 --> 00:10:35.500 align:start position:0% you but what we are saying is with if 00:10:35.500 --> 00:10:37.800 align:start position:0% you but what we are saying is with if you<00:10:35.770> run<00:10:35.980> say<00:10:36.220> validator<00:10:36.730> or<00:10:37.000> even<00:10:37.270> a<00:10:37.300> verifier 00:10:37.800 --> 00:10:37.810 align:start position:0% you run say validator or even a verifier 00:10:37.810 --> 00:10:39.780 align:start position:0% you run say validator or even a verifier inside<00:10:38.290> a<00:10:38.320> tacit<00:10:38.770> compute<00:10:39.160> and<00:10:39.339> you<00:10:39.430> have<00:10:39.579> all 00:10:39.780 --> 00:10:39.790 align:start position:0% inside a tacit compute and you have all 00:10:39.790 --> 00:10:42.990 align:start position:0% inside a tacit compute and you have all of<00:10:39.820> those<00:10:40.089> a<00:10:40.930> log<00:10:41.589> of<00:10:41.800> your<00:10:41.950> activity<00:10:42.459> you<00:10:42.820> can 00:10:42.990 --> 00:10:43.000 align:start position:0% of those a log of your activity you can 00:10:43.000 --> 00:10:45.510 align:start position:0% of those a log of your activity you can really<00:10:43.390> prove<00:10:43.600> that<00:10:43.810> you<00:10:43.959> know<00:10:44.050> hey<00:10:44.200> hey<00:10:44.620> I<00:10:44.860> did 00:10:45.510 --> 00:10:45.520 align:start position:0% really prove that you know hey hey I did 00:10:45.520 --> 00:10:47.699 align:start position:0% really prove that you know hey hey I did do<00:10:45.730> this<00:10:45.940> that<00:10:46.510> means<00:10:46.750> I<00:10:46.899> did<00:10:47.110> vote<00:10:47.350> on<00:10:47.529> it 00:10:47.699 --> 00:10:47.709 align:start position:0% do this that means I did vote on it 00:10:47.709 --> 00:10:50.550 align:start position:0% do this that means I did vote on it something<00:10:48.040> else<00:10:48.399> in<00:10:48.579> the<00:10:49.260> ecosystem<00:10:50.260> down<00:10:50.410> the 00:10:50.550 --> 00:10:50.560 align:start position:0% something else in the ecosystem down the 00:10:50.560 --> 00:10:54.079 align:start position:0% something else in the ecosystem down the line<00:10:50.709> is<00:10:50.950> basically<00:10:51.990> censoring<00:10:52.990> my<00:10:53.140> output<00:10:53.529> or 00:10:54.079 --> 00:10:54.089 align:start position:0% line is basically censoring my output or 00:10:54.089 --> 00:10:57.810 align:start position:0% line is basically censoring my output or or<00:10:55.089> I<00:10:55.149> did<00:10:55.450> not<00:10:55.630> do<00:10:55.750> that<00:10:55.779> because<00:10:56.380> the<00:10:56.829> this 00:10:57.810 --> 00:10:57.820 align:start position:0% or I did not do that because the this 00:10:57.820 --> 00:10:59.640 align:start position:0% or I did not do that because the this key<00:10:58.060> that's<00:10:58.449> used<00:10:58.720> to<00:10:58.839> sign<00:10:59.020> the<00:10:59.050> result<00:10:59.470> is 00:10:59.640 --> 00:10:59.650 align:start position:0% key that's used to sign the result is 00:10:59.650 --> 00:11:01.920 align:start position:0% key that's used to sign the result is safely<00:11:00.400> inside<00:11:00.730> the<00:11:00.790> thing<00:11:01.150> and<00:11:01.390> cannot<00:11:01.720> be 00:11:01.920 --> 00:11:01.930 align:start position:0% safely inside the thing and cannot be 00:11:01.930 --> 00:11:03.600 align:start position:0% safely inside the thing and cannot be leaked<00:11:02.380> so 00:11:03.600 --> 00:11:03.610 align:start position:0% leaked so 00:11:03.610 --> 00:11:05.670 align:start position:0% leaked so this<00:11:03.730> is<00:11:03.850> whatever<00:11:04.029> we<00:11:04.209> see<00:11:04.360> is<00:11:04.420> like<00:11:04.630> we<00:11:05.500> can 00:11:05.670 --> 00:11:05.680 align:start position:0% this is whatever we see is like we can 00:11:05.680 --> 00:11:07.139 align:start position:0% this is whatever we see is like we can simplify<00:11:05.980> some<00:11:06.339> of<00:11:06.370> these<00:11:06.579> things<00:11:06.820> and<00:11:07.000> this 00:11:07.139 --> 00:11:07.149 align:start position:0% simplify some of these things and this 00:11:07.149 --> 00:11:08.310 align:start position:0% simplify some of these things and this is<00:11:07.209> where<00:11:07.420> you<00:11:07.570> will<00:11:07.660> talk<00:11:07.870> a<00:11:07.930> little<00:11:08.079> bit 00:11:08.310 --> 00:11:08.320 align:start position:0% is where you will talk a little bit 00:11:08.320 --> 00:11:11.970 align:start position:0% is where you will talk a little bit about<00:11:08.350> it<00:11:08.709> and<00:11:08.860> then<00:11:09.670> lastly<00:11:10.329> at<00:11:10.570> the<00:11:10.750> at<00:11:11.740> the 00:11:11.970 --> 00:11:11.980 align:start position:0% about it and then lastly at the at the 00:11:11.980 --> 00:11:13.680 align:start position:0% about it and then lastly at the at the execution<00:11:12.399> layer<00:11:12.790> you<00:11:13.300> know 00:11:13.680 --> 00:11:13.690 align:start position:0% execution layer you know 00:11:13.690 --> 00:11:17.100 align:start position:0% execution layer you know signature<00:11:14.230> validations<00:11:14.829> as<00:11:15.040> an<00:11:15.190> example<00:11:16.110> you 00:11:17.100 --> 00:11:17.110 align:start position:0% signature validations as an example you 00:11:17.110 --> 00:11:20.370 align:start position:0% signature validations as an example you know<00:11:17.260> yeah<00:11:17.940> it's<00:11:18.940> a<00:11:19.029> common<00:11:19.420> thing<00:11:19.600> and<00:11:19.899> they 00:11:20.370 --> 00:11:20.380 align:start position:0% know yeah it's a common thing and they 00:11:20.380 --> 00:11:22.610 align:start position:0% know yeah it's a common thing and they take<00:11:20.560> a<00:11:20.589> lot<00:11:20.709> of<00:11:20.860> time<00:11:21.040> you<00:11:21.279> can<00:11:21.790> offload<00:11:22.209> that 00:11:22.610 --> 00:11:22.620 align:start position:0% take a lot of time you can offload that 00:11:22.620 --> 00:11:27.690 align:start position:0% take a lot of time you can offload that complex<00:11:24.450> tasks<00:11:25.450> that<00:11:25.750> require<00:11:25.959> lot<00:11:26.920> of<00:11:27.040> arrow 00:11:27.690 --> 00:11:27.700 align:start position:0% complex tasks that require lot of arrow 00:11:27.700 --> 00:11:30.090 align:start position:0% complex tasks that require lot of arrow gasps<00:11:28.120> you<00:11:28.690> can<00:11:28.870> offload<00:11:29.170> that<00:11:29.290> were<00:11:29.709> you<00:11:30.070> know 00:11:30.090 --> 00:11:30.100 align:start position:0% gasps you can offload that were you know 00:11:30.100 --> 00:11:32.759 align:start position:0% gasps you can offload that were you know plasma<00:11:30.640> chain<00:11:30.910> built<00:11:31.839> around<00:11:32.079> this<00:11:32.320> or<00:11:32.709> a 00:11:32.759 --> 00:11:32.769 align:start position:0% plasma chain built around this or a 00:11:32.769 --> 00:11:35.550 align:start position:0% plasma chain built around this or a sidechain<00:11:33.339> so<00:11:34.000> in<00:11:34.510> general<00:11:34.990> like<00:11:35.140> like<00:11:35.350> what 00:11:35.550 --> 00:11:35.560 align:start position:0% sidechain so in general like like what 00:11:35.560 --> 00:11:37.139 align:start position:0% sidechain so in general like like what the<00:11:36.070> thing<00:11:36.190> is<00:11:36.310> like<00:11:36.459> what<00:11:36.610> we<00:11:36.730> see<00:11:36.880> is<00:11:36.940> like 00:11:37.139 --> 00:11:37.149 align:start position:0% the thing is like what we see is like 00:11:37.149 --> 00:11:40.769 align:start position:0% the thing is like what we see is like you<00:11:37.269> know<00:11:37.390> it<00:11:38.339> at<00:11:39.339> the<00:11:39.610> beacon<00:11:39.940> layer<00:11:40.120> it 00:11:40.769 --> 00:11:40.779 align:start position:0% you know it at the beacon layer it 00:11:40.779 --> 00:11:43.410 align:start position:0% you know it at the beacon layer it reduces<00:11:41.649> the<00:11:41.829> friction<00:11:42.100> or<00:11:42.610> reduces<00:11:43.029> the<00:11:43.149> fear 00:11:43.410 --> 00:11:43.420 align:start position:0% reduces the friction or reduces the fear 00:11:43.420 --> 00:11:46.620 align:start position:0% reduces the friction or reduces the fear that<00:11:43.450> I<00:11:43.779> might<00:11:44.079> get<00:11:44.290> slashed<00:11:45.209> and<00:11:46.209> I<00:11:46.450> don't 00:11:46.620 --> 00:11:46.630 align:start position:0% that I might get slashed and I don't 00:11:46.630 --> 00:11:49.139 align:start position:0% that I might get slashed and I don't have<00:11:46.810> anything<00:11:47.019> to<00:11:47.170> fall<00:11:47.410> back<00:11:47.680> to<00:11:47.709> so<00:11:48.519> it<00:11:48.700> in<00:11:49.029> a 00:11:49.139 --> 00:11:49.149 align:start position:0% have anything to fall back to so it in a 00:11:49.149 --> 00:11:51.600 align:start position:0% have anything to fall back to so it in a way<00:11:49.300> helps<00:11:50.170> more<00:11:50.440> people<00:11:50.500> to<00:11:50.920> participate<00:11:51.190> and 00:11:51.600 --> 00:11:51.610 align:start position:0% way helps more people to participate and 00:11:51.610 --> 00:11:53.670 align:start position:0% way helps more people to participate and increase<00:11:51.940> hopefully<00:11:52.750> the<00:11:52.870> democratization 00:11:53.670 --> 00:11:53.680 align:start position:0% increase hopefully the democratization 00:11:53.680 --> 00:11:55.920 align:start position:0% increase hopefully the democratization of<00:11:53.800> this<00:11:53.980> whole<00:11:54.130> decentralization<00:11:54.790> and<00:11:55.089> also 00:11:55.920 --> 00:11:55.930 align:start position:0% of this whole decentralization and also 00:11:55.930 --> 00:11:58.319 align:start position:0% of this whole decentralization and also helps<00:11:56.170> with<00:11:56.290> the<00:11:56.350> scalability<00:11:56.980> and<00:11:57.329> security 00:11:58.319 --> 00:11:58.329 align:start position:0% helps with the scalability and security 00:11:58.329 --> 00:12:13.730 align:start position:0% helps with the scalability and security at<00:11:59.019> this<00:11:59.230> point<00:11:59.470> I<00:11:59.709> will<00:12:00.070> turn<00:12:00.310> over<00:12:00.550> to<00:12:11.430> better 00:12:13.730 --> 00:12:13.740 align:start position:0% at this point I will turn over to better 00:12:13.740 --> 00:12:17.870 align:start position:0% at this point I will turn over to better so<00:12:14.740> we<00:12:15.310> talked<00:12:15.550> about<00:12:15.779> secure<00:12:16.779> private<00:12:17.320> and 00:12:17.870 --> 00:12:17.880 align:start position:0% so we talked about secure private and 00:12:17.880 --> 00:12:22.170 align:start position:0% so we talked about secure private and self<00:12:18.880> control<00:12:19.269> and<00:12:19.540> it<00:12:20.170> can<00:12:20.380> be<00:12:20.760> ubiquitous<00:12:21.760> so 00:12:22.170 --> 00:12:22.180 align:start position:0% self control and it can be ubiquitous so 00:12:22.180 --> 00:12:25.290 align:start position:0% self control and it can be ubiquitous so what<00:12:23.110> are<00:12:23.230> the<00:12:23.500> type<00:12:23.680> of<00:12:23.709> services<00:12:24.430> that<00:12:25.089> could 00:12:25.290 --> 00:12:25.300 align:start position:0% what are the type of services that could 00:12:25.300 --> 00:12:29.189 align:start position:0% what are the type of services that could be<00:12:25.480> build<00:12:25.750> with<00:12:26.470> this<00:12:26.680> on<00:12:26.949> top<00:12:27.190> of<00:12:27.399> etherium<00:12:28.199> so 00:12:29.189 --> 00:12:29.199 align:start position:0% be build with this on top of etherium so 00:12:29.199 --> 00:12:32.420 align:start position:0% be build with this on top of etherium so you<00:12:29.260> have<00:12:30.060> for<00:12:31.060> example<00:12:31.180> a<00:12:31.570> decentralized 00:12:32.420 --> 00:12:32.430 align:start position:0% you have for example a decentralized 00:12:32.430 --> 00:12:36.030 align:start position:0% you have for example a decentralized device<00:12:33.430> registry<00:12:33.970> which<00:12:34.750> is<00:12:34.899> valuable<00:12:35.620> when 00:12:36.030 --> 00:12:36.040 align:start position:0% device registry which is valuable when 00:12:36.040 --> 00:12:39.840 align:start position:0% device registry which is valuable when you're<00:12:36.160> talking<00:12:36.670> about<00:12:36.850> IOT<00:12:38.850> self-driving 00:12:39.840 --> 00:12:39.850 align:start position:0% you're talking about IOT self-driving 00:12:39.850 --> 00:12:43.009 align:start position:0% you're talking about IOT self-driving vehicles<00:12:40.740> you<00:12:41.740> have<00:12:41.769> secure<00:12:42.310> multi-party 00:12:43.009 --> 00:12:43.019 align:start position:0% vehicles you have secure multi-party 00:12:43.019 --> 00:12:45.650 align:start position:0% vehicles you have secure multi-party transaction<00:12:44.019> signing<00:12:44.410> which<00:12:44.980> is<00:12:45.160> applicable 00:12:45.650 --> 00:12:45.660 align:start position:0% transaction signing which is applicable 00:12:45.660 --> 00:12:49.889 align:start position:0% transaction signing which is applicable not<00:12:46.660> only<00:12:46.690> for<00:12:48.240> aetherium<00:12:49.240> transaction<00:12:49.779> but 00:12:49.889 --> 00:12:49.899 align:start position:0% not only for aetherium transaction but 00:12:49.899 --> 00:12:53.100 align:start position:0% not only for aetherium transaction but for<00:12:50.019> any<00:12:50.940> transaction<00:12:51.940> you<00:12:52.060> don't<00:12:52.209> no<00:12:53.079> longer 00:12:53.100 --> 00:12:53.110 align:start position:0% for any transaction you don't no longer 00:12:53.110 --> 00:12:56.340 align:start position:0% for any transaction you don't no longer need<00:12:53.800> your<00:12:54.310> private<00:12:54.760> key<00:12:55.000> on<00:12:55.269> your<00:12:55.959> device 00:12:56.340 --> 00:12:56.350 align:start position:0% need your private key on your device 00:12:56.350 --> 00:12:59.639 align:start position:0% need your private key on your device because<00:12:57.279> you<00:12:57.459> can<00:12:57.610> have<00:12:57.790> the<00:12:58.149> signing<00:12:58.570> done<00:12:58.779> in 00:12:59.639 --> 00:12:59.649 align:start position:0% because you can have the signing done in 00:12:59.649 --> 00:13:02.069 align:start position:0% because you can have the signing done in a<00:12:59.769> trusted<00:13:00.160> way<00:13:00.339> by<00:13:00.519> multiple<00:13:00.970> parties<00:13:01.630> you 00:13:02.069 --> 00:13:02.079 align:start position:0% a trusted way by multiple parties you 00:13:02.079 --> 00:13:04.259 align:start position:0% a trusted way by multiple parties you have<00:13:02.170> secured<00:13:02.680> decentralized<00:13:03.399> cloud<00:13:03.760> so 00:13:04.259 --> 00:13:04.269 align:start position:0% have secured decentralized cloud so 00:13:04.269 --> 00:13:06.780 align:start position:0% have secured decentralized cloud so we're<00:13:04.480> talking<00:13:04.720> with<00:13:05.339> we're<00:13:06.339> talking<00:13:06.640> with 00:13:06.780 --> 00:13:06.790 align:start position:0% we're talking with we're talking with 00:13:06.790 --> 00:13:12.120 align:start position:0% we're talking with we're talking with OEMs<00:13:07.660> to<00:13:08.019> be<00:13:08.260> able<00:13:08.350> to<00:13:08.620> provide<00:13:10.500> to<00:13:11.500> collect<00:13:11.949> a 00:13:12.120 --> 00:13:12.130 align:start position:0% OEMs to be able to provide to collect a 00:13:12.130 --> 00:13:16.900 align:start position:0% OEMs to be able to provide to collect a cloud<00:13:12.579> a<00:13:13.029> fog<00:13:13.680> of<00:13:14.730> devices<00:13:15.730> that<00:13:15.910> run 00:13:16.900 --> 00:13:16.910 align:start position:0% cloud a fog of devices that run 00:13:16.910 --> 00:13:19.630 align:start position:0% cloud a fog of devices that run trusted<00:13:17.300> compute<00:13:17.960> services<00:13:18.530> and<00:13:18.890> I'll<00:13:19.340> talk 00:13:19.630 --> 00:13:19.640 align:start position:0% trusted compute services and I'll talk 00:13:19.640 --> 00:13:22.320 align:start position:0% trusted compute services and I'll talk at<00:13:20.360> the<00:13:20.600> end<00:13:20.750> for<00:13:21.260> a<00:13:21.320> few<00:13:21.500> minutes<00:13:21.740> about<00:13:21.860> that 00:13:22.320 --> 00:13:22.330 align:start position:0% at the end for a few minutes about that 00:13:22.330 --> 00:13:26.620 align:start position:0% at the end for a few minutes about that you<00:13:23.330> also<00:13:23.570> can<00:13:24.140> do<00:13:24.530> NPC<00:13:25.220> analytics<00:13:25.820> you<00:13:26.600> can 00:13:26.620 --> 00:13:26.630 align:start position:0% you also can do NPC analytics you can 00:13:26.630 --> 00:13:29.380 align:start position:0% you also can do NPC analytics you can also<00:13:27.080> now<00:13:27.500> do<00:13:27.560> secure<00:13:28.370> wallets<00:13:28.910> and<00:13:29.180> real-time 00:13:29.380 --> 00:13:29.390 align:start position:0% also now do secure wallets and real-time 00:13:29.390 --> 00:13:32.620 align:start position:0% also now do secure wallets and real-time Oracle's<00:13:30.140> with<00:13:30.410> this<00:13:30.620> and<00:13:31.070> you<00:13:31.700> can<00:13:31.910> do<00:13:32.090> secure 00:13:32.620 --> 00:13:32.630 align:start position:0% Oracle's with this and you can do secure 00:13:32.630 --> 00:13:36.190 align:start position:0% Oracle's with this and you can do secure public<00:13:32.900> or<00:13:33.260> private<00:13:33.500> data<00:13:33.950> stores<00:13:35.200> at 00:13:36.190 --> 00:13:36.200 align:start position:0% public or private data stores at 00:13:36.200 --> 00:13:38.950 align:start position:0% public or private data stores at consensus<00:13:36.830> there<00:13:37.100> there<00:13:37.490> a<00:13:37.690> project<00:13:38.690> called 00:13:38.950 --> 00:13:38.960 align:start position:0% consensus there there a project called 00:13:38.960 --> 00:13:40.840 align:start position:0% consensus there there a project called Linea<00:13:39.350> at<00:13:39.710> the<00:13:39.830> decentralized<00:13:40.190> identity 00:13:40.840 --> 00:13:40.850 align:start position:0% Linea at the decentralized identity 00:13:40.850 --> 00:13:43.840 align:start position:0% Linea at the decentralized identity foundation<00:13:41.810> we're<00:13:42.020> working<00:13:42.550> together<00:13:43.550> with 00:13:43.840 --> 00:13:43.850 align:start position:0% foundation we're working together with 00:13:43.850 --> 00:13:46.120 align:start position:0% foundation we're working together with others<00:13:44.120> on<00:13:44.380> identity<00:13:45.380> hubs<00:13:45.710> where<00:13:45.920> we<00:13:46.040> will 00:13:46.120 --> 00:13:46.130 align:start position:0% others on identity hubs where we will 00:13:46.130 --> 00:13:49.750 align:start position:0% others on identity hubs where we will actually<00:13:46.310> employ<00:13:46.820> these<00:13:47.120> these<00:13:48.760> technologies 00:13:49.750 --> 00:13:49.760 align:start position:0% actually employ these these technologies 00:13:49.760 --> 00:13:51.550 align:start position:0% actually employ these these technologies then<00:13:50.480> you<00:13:50.630> have<00:13:50.840> which<00:13:51.080> you<00:13:51.170> probably<00:13:51.440> have 00:13:51.550 --> 00:13:51.560 align:start position:0% then you have which you probably have 00:13:51.560 --> 00:13:54.640 align:start position:0% then you have which you probably have heard<00:13:51.650> before<00:13:52.040> off<00:13:52.370> chain<00:13:52.850> compute<00:13:53.510> offload<00:13:54.260> a 00:13:54.640 --> 00:13:54.650 align:start position:0% heard before off chain compute offload a 00:13:54.650 --> 00:13:59.590 align:start position:0% heard before off chain compute offload a lot<00:13:54.860> of<00:13:55.280> smart<00:13:55.670> contract<00:13:56.500> heavy<00:13:57.500> logic<00:13:58.600> onto 00:13:59.590 --> 00:13:59.600 align:start position:0% lot of smart contract heavy logic onto 00:13:59.600 --> 00:14:02.560 align:start position:0% lot of smart contract heavy logic onto trusted<00:14:00.230> compute<00:14:01.130> entities<00:14:01.550> as<00:14:01.820> well<00:14:02.300> as 00:14:02.560 --> 00:14:02.570 align:start position:0% trusted compute entities as well as 00:14:02.570 --> 00:14:05.410 align:start position:0% trusted compute entities as well as secure<00:14:03.440> data<00:14:03.620> station<00:14:03.920> validation<00:14:04.760> so<00:14:05.240> for 00:14:05.410 --> 00:14:05.420 align:start position:0% secure data station validation so for 00:14:05.420 --> 00:14:08.200 align:start position:0% secure data station validation so for example<00:14:05.780> if<00:14:05.870> your<00:14:06.020> bank<00:14:06.260> gives<00:14:06.770> you<00:14:07.070> your<00:14:07.430> kyc 00:14:08.200 --> 00:14:08.210 align:start position:0% example if your bank gives you your kyc 00:14:08.210 --> 00:14:11.920 align:start position:0% example if your bank gives you your kyc and<00:14:08.510> it<00:14:08.600> says<00:14:08.810> you<00:14:08.990> have<00:14:09.200> a<00:14:10.000> you<00:14:11.000> have<00:14:11.270> a<00:14:11.540> user 00:14:11.920 --> 00:14:11.930 align:start position:0% and it says you have a you have a user 00:14:11.930 --> 00:14:15.040 align:start position:0% and it says you have a you have a user security<00:14:12.500> number<00:14:12.860> you<00:14:13.100> have<00:14:13.430> a<00:14:13.460> valid<00:14:13.850> US<00:14:14.150> u.s. 00:14:15.040 --> 00:14:15.050 align:start position:0% security number you have a valid US u.s. 00:14:15.050 --> 00:14:17.110 align:start position:0% security number you have a valid US u.s. address<00:14:15.500> you<00:14:16.220> don't<00:14:16.400> want<00:14:16.550> to<00:14:16.610> reveal<00:14:16.760> that 00:14:17.110 --> 00:14:17.120 align:start position:0% address you don't want to reveal that 00:14:17.120 --> 00:14:19.330 align:start position:0% address you don't want to reveal that right<00:14:17.900> but<00:14:18.170> you<00:14:18.290> can<00:14:18.440> prove<00:14:18.710> that<00:14:18.920> your<00:14:19.100> over 00:14:19.330 --> 00:14:19.340 align:start position:0% right but you can prove that your over 00:14:19.340 --> 00:14:22.870 align:start position:0% right but you can prove that your over over<00:14:19.730> 21<00:14:20.330> that<00:14:20.690> your<00:14:20.980> that<00:14:21.980> you<00:14:22.100> have<00:14:22.220> a<00:14:22.250> valid 00:14:22.870 --> 00:14:22.880 align:start position:0% over 21 that your that you have a valid 00:14:22.880 --> 00:14:24.850 align:start position:0% over 21 that your that you have a valid social<00:14:23.210> security<00:14:23.390> number<00:14:24.050> and<00:14:24.080> you<00:14:24.440> can<00:14:24.620> pass 00:14:24.850 --> 00:14:24.860 align:start position:0% social security number and you can pass 00:14:24.860 --> 00:14:27.400 align:start position:0% social security number and you can pass this<00:14:25.100> attestation<00:14:25.550> into<00:14:26.240> trusted<00:14:26.750> compute 00:14:27.400 --> 00:14:27.410 align:start position:0% this attestation into trusted compute 00:14:27.410 --> 00:14:29.260 align:start position:0% this attestation into trusted compute that<00:14:27.770> applies<00:14:28.160> the<00:14:28.190> logic<00:14:28.790> to<00:14:28.820> it<00:14:29.060> and 00:14:29.260 --> 00:14:29.270 align:start position:0% that applies the logic to it and 00:14:29.270 --> 00:14:33.700 align:start position:0% that applies the logic to it and generates<00:14:30.230> another<00:14:30.640> anonymized<00:14:32.440> at<00:14:33.440> the 00:14:33.700 --> 00:14:33.710 align:start position:0% generates another anonymized at the 00:14:33.710 --> 00:14:37.980 align:start position:0% generates another anonymized at the station<00:14:34.130> that<00:14:34.280> still<00:14:34.310> proves<00:14:34.880> the<00:14:35.470> same<00:14:36.470> thing 00:14:37.980 --> 00:14:37.990 align:start position:0% station that still proves the same thing 00:14:37.990 --> 00:14:41.860 align:start position:0% station that still proves the same thing so<00:14:38.990> after<00:14:39.890> talking<00:14:40.310> about<00:14:40.550> the<00:14:41.090> applications 00:14:41.860 --> 00:14:41.870 align:start position:0% so after talking about the applications 00:14:41.870 --> 00:14:44.710 align:start position:0% so after talking about the applications on<00:14:42.200> top<00:14:42.230> let's<00:14:42.830> come<00:14:43.310> back<00:14:43.520> one<00:14:44.210> step<00:14:44.390> and 00:14:44.710 --> 00:14:44.720 align:start position:0% on top let's come back one step and 00:14:44.720 --> 00:14:47.950 align:start position:0% on top let's come back one step and let's<00:14:45.020> talk<00:14:45.350> about<00:14:46.240> what<00:14:47.240> we<00:14:47.390> can<00:14:47.540> do<00:14:47.690> on<00:14:47.720> any 00:14:47.950 --> 00:14:47.960 align:start position:0% let's talk about what we can do on any 00:14:47.960 --> 00:14:49.390 align:start position:0% let's talk about what we can do on any theory<00:14:48.260> of<00:14:48.380> no<00:14:48.530> time<00:14:48.590> apparently<00:14:49.070> I<00:14:49.100> shouldn't 00:14:49.390 --> 00:14:49.400 align:start position:0% theory of no time apparently I shouldn't 00:14:49.400 --> 00:14:51.600 align:start position:0% theory of no time apparently I shouldn't shouldn't<00:14:49.970> touch<00:14:50.090> this 00:14:51.600 --> 00:14:51.610 align:start position:0% shouldn't touch this 00:14:51.610 --> 00:14:54.580 align:start position:0% shouldn't touch this so<00:14:52.610> what<00:14:53.180> Sanjay<00:14:53.570> showed<00:14:54.110> you<00:14:54.260> about<00:14:54.410> in 00:14:54.580 --> 00:14:54.590 align:start position:0% so what Sanjay showed you about in 00:14:54.590 --> 00:14:57.760 align:start position:0% so what Sanjay showed you about in theory<00:14:54.800> M<00:14:54.980> 2.0<00:14:55.520> let's<00:14:55.760> take<00:14:55.970> that<00:14:56.120> a<00:14:56.770> level 00:14:57.760 --> 00:14:57.770 align:start position:0% theory M 2.0 let's take that a level 00:14:57.770 --> 00:15:00.070 align:start position:0% theory M 2.0 let's take that a level deeper<00:14:58.250> and<00:14:58.430> that's<00:14:58.550> do<00:14:59.180> it<00:14:59.300> to<00:14:59.660> a<00:14:59.690> little 00:15:00.070 --> 00:15:00.080 align:start position:0% deeper and that's do it to a little 00:15:00.080 --> 00:15:02.890 align:start position:0% deeper and that's do it to a little journey<00:15:00.440> of<00:15:00.890> a<00:15:01.370> theorem<00:15:02.060> transaction<00:15:02.690> so<00:15:02.810> it 00:15:02.890 --> 00:15:02.900 align:start position:0% journey of a theorem transaction so it 00:15:02.900 --> 00:15:04.750 align:start position:0% journey of a theorem transaction so it first<00:15:03.140> comes<00:15:03.440> into<00:15:03.590> the<00:15:03.830> transaction<00:15:04.340> pool 00:15:04.750 --> 00:15:04.760 align:start position:0% first comes into the transaction pool 00:15:04.760 --> 00:15:07.300 align:start position:0% first comes into the transaction pool well<00:15:05.300> nowadays<00:15:05.540> any<00:15:06.320> node<00:15:06.590> can<00:15:06.860> do<00:15:06.950> anything 00:15:07.300 --> 00:15:07.310 align:start position:0% well nowadays any node can do anything 00:15:07.310 --> 00:15:10.120 align:start position:0% well nowadays any node can do anything with<00:15:07.460> your<00:15:08.140> transaction<00:15:09.140> it<00:15:09.320> can<00:15:09.530> it<00:15:09.800> can<00:15:09.830> do 00:15:10.120 --> 00:15:10.130 align:start position:0% with your transaction it can it can do 00:15:10.130 --> 00:15:12.880 align:start position:0% with your transaction it can it can do front<00:15:10.400> running<00:15:10.730> it<00:15:11.060> can<00:15:11.480> do<00:15:11.660> will<00:15:11.990> put<00:15:12.560> it<00:15:12.650> into 00:15:12.880 --> 00:15:12.890 align:start position:0% front running it can do will put it into 00:15:12.890 --> 00:15:14.590 align:start position:0% front running it can do will put it into any<00:15:13.010> order<00:15:13.250> that<00:15:13.550> it<00:15:13.640> wants<00:15:14.030> or<00:15:14.150> it<00:15:14.270> might<00:15:14.420> just 00:15:14.590 --> 00:15:14.600 align:start position:0% any order that it wants or it might just 00:15:14.600 --> 00:15:16.950 align:start position:0% any order that it wants or it might just simply<00:15:14.720> a<00:15:14.870> censor<00:15:15.230> it<00:15:15.350> so<00:15:15.920> if<00:15:16.130> you<00:15:16.250> ask<00:15:16.430> at 00:15:16.950 --> 00:15:16.960 align:start position:0% simply a censor it so if you ask at 00:15:16.960 --> 00:15:19.570 align:start position:0% simply a censor it so if you ask at trusted<00:15:17.960> ordering<00:15:18.380> an<00:15:18.620> encryption<00:15:19.010> service 00:15:19.570 --> 00:15:19.580 align:start position:0% trusted ordering an encryption service 00:15:19.580 --> 00:15:21.910 align:start position:0% trusted ordering an encryption service to<00:15:19.760> that<00:15:19.790> all<00:15:20.240> of<00:15:20.480> us<00:15:20.630> goes<00:15:21.200> away<00:15:21.470> so<00:15:21.530> you're 00:15:21.910 --> 00:15:21.920 align:start position:0% to that all of us goes away so you're 00:15:21.920 --> 00:15:25.420 align:start position:0% to that all of us goes away so you're taking<00:15:22.100> a<00:15:22.520> significant<00:15:23.210> attack<00:15:23.600> vector<00:15:24.430> out 00:15:25.420 --> 00:15:25.430 align:start position:0% taking a significant attack vector out 00:15:25.430 --> 00:15:27.790 align:start position:0% taking a significant attack vector out if<00:15:25.970> you're<00:15:26.300> following<00:15:26.750> along<00:15:26.840> you<00:15:27.080> go<00:15:27.500> to<00:15:27.560> the 00:15:27.790 --> 00:15:27.800 align:start position:0% if you're following along you go to the 00:15:27.800 --> 00:15:28.960 align:start position:0% if you're following along you go to the EVM 00:15:28.960 --> 00:15:28.970 align:start position:0% EVM 00:15:28.970 --> 00:15:31.689 align:start position:0% EVM that<00:15:29.240> goes<00:15:29.420> into<00:15:29.629> the<00:15:29.750> level<00:15:30.050> DB<00:15:30.800> you<00:15:31.399> can<00:15:31.579> now 00:15:31.689 --> 00:15:31.699 align:start position:0% that goes into the level DB you can now 00:15:31.699 --> 00:15:34.090 align:start position:0% that goes into the level DB you can now do<00:15:31.759> a<00:15:32.000> trusted<00:15:32.600> EVM<00:15:32.959> execution<00:15:33.709> service 00:15:34.090 --> 00:15:34.100 align:start position:0% do a trusted EVM execution service 00:15:34.100 --> 00:15:37.210 align:start position:0% do a trusted EVM execution service before<00:15:34.790> it<00:15:35.300> goes<00:15:35.509> to<00:15:36.199> proof<00:15:36.500> of<00:15:36.649> work<00:15:36.829> that's 00:15:37.210 --> 00:15:37.220 align:start position:0% before it goes to proof of work that's 00:15:37.220 --> 00:15:39.579 align:start position:0% before it goes to proof of work that's for<00:15:37.459> the<00:15:37.550> main<00:15:37.730> net<00:15:38.019> if<00:15:39.019> you're<00:15:39.199> now<00:15:39.350> going 00:15:39.579 --> 00:15:39.589 align:start position:0% for the main net if you're now going 00:15:39.589 --> 00:15:42.340 align:start position:0% for the main net if you're now going plasma<00:15:40.250> plasma<00:15:40.730> chain<00:15:41.180> sidechain<00:15:41.870> beacon 00:15:42.340 --> 00:15:42.350 align:start position:0% plasma plasma chain sidechain beacon 00:15:42.350 --> 00:15:46.300 align:start position:0% plasma plasma chain sidechain beacon chain<00:15:42.620> you<00:15:43.399> talking<00:15:43.819> about<00:15:44.000> Casper<00:15:44.389> FFG<00:15:45.310> and 00:15:46.300 --> 00:15:46.310 align:start position:0% chain you talking about Casper FFG and 00:15:46.310 --> 00:15:49.840 align:start position:0% chain you talking about Casper FFG and here<00:15:46.790> again<00:15:47.149> you<00:15:47.480> can<00:15:47.509> employ<00:15:48.079> a<00:15:48.850> trusted 00:15:49.840 --> 00:15:49.850 align:start position:0% here again you can employ a trusted 00:15:49.850 --> 00:15:51.850 align:start position:0% here again you can employ a trusted compute<00:15:50.240> service<00:15:50.689> that<00:15:50.930> actually<00:15:51.170> says<00:15:51.589> hey<00:15:51.829> I 00:15:51.850 --> 00:15:51.860 align:start position:0% compute service that actually says hey I 00:15:51.860 --> 00:15:54.939 align:start position:0% compute service that actually says hey I voted<00:15:52.490> this<00:15:52.610> way<00:15:52.819> right<00:15:53.600> and<00:15:53.959> you<00:15:54.500> know<00:15:54.620> no 00:15:54.939 --> 00:15:54.949 align:start position:0% voted this way right and you know no 00:15:54.949 --> 00:15:58.179 align:start position:0% voted this way right and you know no human<00:15:55.399> being<00:15:55.610> can<00:15:56.480> can<00:15:57.019> can<00:15:57.500> influence<00:15:57.889> that 00:15:58.179 --> 00:15:58.189 align:start position:0% human being can can can influence that 00:15:58.189 --> 00:16:01.540 align:start position:0% human being can can can influence that which<00:15:59.000> means<00:15:59.209> the<00:15:59.810> your<00:16:00.410> assurances<00:16:01.100> that<00:16:01.160> the 00:16:01.540 --> 00:16:01.550 align:start position:0% which means the your assurances that the 00:16:01.550 --> 00:16:04.410 align:start position:0% which means the your assurances that the vote<00:16:01.759> was<00:16:02.240> done<00:16:02.509> honestly<00:16:02.990> go<00:16:03.980> up 00:16:04.410 --> 00:16:04.420 align:start position:0% vote was done honestly go up 00:16:04.420 --> 00:16:09.550 align:start position:0% vote was done honestly go up exponentially<00:16:06.009> so<00:16:07.480> this<00:16:08.480> is<00:16:08.629> for<00:16:08.899> for<00:16:09.379> now 00:16:09.550 --> 00:16:09.560 align:start position:0% exponentially so this is for for now 00:16:09.560 --> 00:16:12.970 align:start position:0% exponentially so this is for for now let's<00:16:09.889> let's<00:16:10.189> go<00:16:10.339> one<00:16:10.610> level<00:16:10.819> deeper<00:16:11.199> okay<00:16:12.199> so 00:16:12.970 --> 00:16:12.980 align:start position:0% let's let's go one level deeper okay so 00:16:12.980 --> 00:16:16.360 align:start position:0% let's let's go one level deeper okay so I<00:16:13.009> give<00:16:13.639> you<00:16:13.730> three<00:16:14.060> concrete<00:16:14.509> and<00:16:15.370> example 00:16:16.360 --> 00:16:16.370 align:start position:0% I give you three concrete and example 00:16:16.370 --> 00:16:18.509 align:start position:0% I give you three concrete and example already<00:16:16.610> at<00:16:16.759> layer<00:16:17.300> 1<00:16:17.389> now<00:16:17.779> let's<00:16:18.019> dive<00:16:18.139> one 00:16:18.509 --> 00:16:18.519 align:start position:0% already at layer 1 now let's dive one 00:16:18.519 --> 00:16:21.100 align:start position:0% already at layer 1 now let's dive one level<00:16:19.519> deeper<00:16:19.970> this<00:16:20.329> looks<00:16:20.600> really<00:16:20.990> really 00:16:21.100 --> 00:16:21.110 align:start position:0% level deeper this looks really really 00:16:21.110 --> 00:16:24.939 align:start position:0% level deeper this looks really really ugly<00:16:21.500> and<00:16:22.009> it<00:16:22.129> is<00:16:22.660> what<00:16:23.660> I<00:16:23.689> want<00:16:23.930> to<00:16:24.019> focus<00:16:24.589> on 00:16:24.939 --> 00:16:24.949 align:start position:0% ugly and it is what I want to focus on 00:16:24.949 --> 00:16:27.689 align:start position:0% ugly and it is what I want to focus on on<00:16:25.220> the<00:16:25.250> right<00:16:25.490> hand<00:16:25.790> side<00:16:26.029> the<00:16:26.540> actual 00:16:27.689 --> 00:16:27.699 align:start position:0% on the right hand side the actual 00:16:27.699 --> 00:16:30.999 align:start position:0% on the right hand side the actual trusted<00:16:28.699> compute<00:16:29.209> logic<00:16:29.720> for<00:16:30.110> a<00:16:30.410> transaction 00:16:30.999 --> 00:16:31.009 align:start position:0% trusted compute logic for a transaction 00:16:31.009 --> 00:16:34.199 align:start position:0% trusted compute logic for a transaction ordering<00:16:31.639> service<00:16:32.089> is<00:16:32.269> very<00:16:32.329> very<00:16:32.750> simple<00:16:33.170> and 00:16:34.199 --> 00:16:34.209 align:start position:0% ordering service is very very simple and 00:16:34.209 --> 00:16:37.119 align:start position:0% ordering service is very very simple and on<00:16:35.209> the<00:16:35.449> left<00:16:35.600> hand<00:16:35.839> side<00:16:36.110> and<00:16:36.470> again<00:16:36.589> don't 00:16:37.119 --> 00:16:37.129 align:start position:0% on the left hand side and again don't 00:16:37.129 --> 00:16:39.340 align:start position:0% on the left hand side and again don't focus<00:16:37.430> on<00:16:37.670> the<00:16:37.819> on<00:16:38.029> all<00:16:38.389> the<00:16:38.569> text<00:16:38.959> the<00:16:39.110> key 00:16:39.340 --> 00:16:39.350 align:start position:0% focus on the on all the text the key 00:16:39.350 --> 00:16:41.559 align:start position:0% focus on the on all the text the key thing<00:16:39.589> or<00:16:39.800> the<00:16:39.920> two<00:16:40.160> blue<00:16:40.459> boxes<00:16:40.970> about 00:16:41.559 --> 00:16:41.569 align:start position:0% thing or the two blue boxes about 00:16:41.569 --> 00:16:44.610 align:start position:0% thing or the two blue boxes about trusted<00:16:42.050> transaction<00:16:42.680> pool<00:16:42.889> app<00:16:43.189> and<00:16:43.579> the 00:16:44.610 --> 00:16:44.620 align:start position:0% trusted transaction pool app and the 00:16:44.620 --> 00:16:47.470 align:start position:0% trusted transaction pool app and the trusted<00:16:45.620> or<00:16:45.800> during<00:16:46.129> registration<00:16:46.480> update 00:16:47.470 --> 00:16:47.480 align:start position:0% trusted or during registration update 00:16:47.480 --> 00:16:51.160 align:start position:0% trusted or during registration update service<00:16:48.139> or<00:16:48.500> two<00:16:49.220> updates<00:16:49.610> that<00:16:50.449> are<00:16:50.480> that<00:16:50.959> can 00:16:51.160 --> 00:16:51.170 align:start position:0% service or two updates that are that can 00:16:51.170 --> 00:16:53.740 align:start position:0% service or two updates that are that can that<00:16:51.379> can<00:16:51.439> be<00:16:51.680> done<00:16:51.829> to<00:16:52.040> the<00:16:52.629> to<00:16:53.629> the 00:16:53.740 --> 00:16:53.750 align:start position:0% that can be done to the to the 00:16:53.750 --> 00:16:56.889 align:start position:0% that can be done to the to the transaction<00:16:54.379> pool<00:16:55.389> module<00:16:56.389> in<00:16:56.779> a 00:16:56.889 --> 00:16:56.899 align:start position:0% transaction pool module in a 00:16:56.899 --> 00:16:59.590 align:start position:0% transaction pool module in a complimentary<00:16:57.740> fashion<00:16:58.000> which<00:16:59.000> means<00:16:59.300> the 00:16:59.590 --> 00:16:59.600 align:start position:0% complimentary fashion which means the 00:16:59.600 --> 00:17:03.460 align:start position:0% complimentary fashion which means the actual<00:17:00.079> change<00:17:00.670> to<00:17:01.670> to<00:17:02.389> to<00:17:02.870> the<00:17:03.050> to<00:17:03.350> the 00:17:03.460 --> 00:17:03.470 align:start position:0% actual change to to to the to the 00:17:03.470 --> 00:17:06.100 align:start position:0% actual change to to to the to the protocol<00:17:03.949> is<00:17:04.220> actually<00:17:04.490> minimal<00:17:05.089> so<00:17:05.630> you<00:17:05.720> can 00:17:06.100 --> 00:17:06.110 align:start position:0% protocol is actually minimal so you can 00:17:06.110 --> 00:17:08.199 align:start position:0% protocol is actually minimal so you can with<00:17:06.289> minimal<00:17:06.740> protocol<00:17:07.159> changes<00:17:07.669> that<00:17:07.909> have 00:17:08.199 --> 00:17:08.209 align:start position:0% with minimal protocol changes that have 00:17:08.209 --> 00:17:10.419 align:start position:0% with minimal protocol changes that have do<00:17:08.630> not<00:17:08.659> require<00:17:09.140> an<00:17:09.439> art<00:17:09.709> for<00:17:09.949> Kerry<00:17:10.159> I<00:17:10.250> think 00:17:10.419 --> 00:17:10.429 align:start position:0% do not require an art for Kerry I think 00:17:10.429 --> 00:17:14.010 align:start position:0% do not require an art for Kerry I think like<00:17:10.579> like<00:17:11.510> that<00:17:11.689> you<00:17:11.990> can<00:17:12.230> increase<00:17:12.850> the 00:17:14.010 --> 00:17:14.020 align:start position:0% like like that you can increase the 00:17:14.020 --> 00:17:21.370 align:start position:0% like like that you can increase the security<00:17:15.020> of<00:17:17.770> of<00:17:18.770> the<00:17:19.339> etherium<00:17:20.380> network 00:17:21.370 --> 00:17:21.380 align:start position:0% security of of the etherium network 00:17:21.380 --> 00:17:28.000 align:start position:0% security of of the etherium network significantly<00:17:23.860> okay<00:17:24.860> so<00:17:25.689> after<00:17:26.689> going<00:17:27.530> down 00:17:28.000 --> 00:17:28.010 align:start position:0% significantly okay so after going down 00:17:28.010 --> 00:17:31.330 align:start position:0% significantly okay so after going down to<00:17:28.159> the<00:17:28.280> protocol<00:17:28.700> layer<00:17:28.909> let's<00:17:29.240> go<00:17:29.390> one<00:17:30.340> back 00:17:31.330 --> 00:17:31.340 align:start position:0% to the protocol layer let's go one back 00:17:31.340 --> 00:17:35.380 align:start position:0% to the protocol layer let's go one back up<00:17:31.850> and<00:17:32.360> talk<00:17:32.809> about<00:17:33.220> services<00:17:34.220> how<00:17:34.640> can<00:17:34.669> you 00:17:35.380 --> 00:17:35.390 align:start position:0% up and talk about services how can you 00:17:35.390 --> 00:17:38.430 align:start position:0% up and talk about services how can you discover<00:17:35.929> these<00:17:36.200> services<00:17:36.830> right<00:17:37.730> there<00:17:38.059> are 00:17:38.430 --> 00:17:38.440 align:start position:0% discover these services right there are 00:17:38.440 --> 00:17:41.500 align:start position:0% discover these services right there are you<00:17:39.440> know<00:17:39.470> you<00:17:39.620> can<00:17:39.890> you<00:17:40.100> can<00:17:40.250> run<00:17:40.520> Intel<00:17:41.299> SGX 00:17:41.500 --> 00:17:41.510 align:start position:0% you know you can you can run Intel SGX 00:17:41.510 --> 00:17:42.440 align:start position:0% you know you can you can run Intel SGX or 00:17:42.440 --> 00:17:42.450 align:start position:0% or 00:17:42.450 --> 00:17:46.279 align:start position:0% or or<00:17:42.809> MD<00:17:43.529> or<00:17:43.559> trustzone<00:17:44.700> or<00:17:45.149> you<00:17:45.840> know<00:17:45.929> is<00:17:46.109> their 00:17:46.279 --> 00:17:46.289 align:start position:0% or MD or trustzone or you know is their 00:17:46.289 --> 00:17:48.379 align:start position:0% or MD or trustzone or you know is their knowledge<00:17:46.499> proof<00:17:46.859> service<00:17:47.369> on<00:17:47.549> your<00:17:47.850> on<00:17:48.029> your 00:17:48.379 --> 00:17:48.389 align:start position:0% knowledge proof service on your on your 00:17:48.389 --> 00:17:51.379 align:start position:0% knowledge proof service on your on your laptop<00:17:48.869> and<00:17:49.169> that's<00:17:50.039> great<00:17:50.369> but<00:17:50.730> no<00:17:51.059> one<00:17:51.239> can 00:17:51.379 --> 00:17:51.389 align:start position:0% laptop and that's great but no one can 00:17:51.389 --> 00:17:54.529 align:start position:0% laptop and that's great but no one can find<00:17:51.690> it<00:17:51.929> so<00:17:52.759> you<00:17:53.759> know<00:17:53.879> that's<00:17:54.119> you<00:17:54.330> the 00:17:54.529 --> 00:17:54.539 align:start position:0% find it so you know that's you the 00:17:54.539 --> 00:17:56.899 align:start position:0% find it so you know that's you the provider<00:17:54.899> you<00:17:55.049> have<00:17:55.379> your<00:17:55.529> trusted<00:17:55.909> compute 00:17:56.899 --> 00:17:56.909 align:start position:0% provider you have your trusted compute 00:17:56.909 --> 00:17:58.759 align:start position:0% provider you have your trusted compute what<00:17:57.480> do<00:17:57.539> you<00:17:57.629> need<00:17:57.809> you<00:17:58.049> need<00:17:58.200> a<00:17:58.230> utility 00:17:58.759 --> 00:17:58.769 align:start position:0% what do you need you need a utility 00:17:58.769 --> 00:18:01.070 align:start position:0% what do you need you need a utility service<00:17:59.100> market<00:17:59.460> platform<00:17:59.909> so<00:18:00.539> really<00:18:00.899> for 00:18:01.070 --> 00:18:01.080 align:start position:0% service market platform so really for 00:18:01.080 --> 00:18:04.489 align:start position:0% service market platform so really for trusted<00:18:01.499> compute<00:18:02.009> is<00:18:02.909> best<00:18:03.659> if<00:18:03.960> it<00:18:04.230> has<00:18:04.470> a 00:18:04.489 --> 00:18:04.499 align:start position:0% trusted compute is best if it has a 00:18:04.499 --> 00:18:08.810 align:start position:0% trusted compute is best if it has a marketplace<00:18:07.039> with<00:18:08.039> a<00:18:08.070> broker<00:18:08.460> service 00:18:08.810 --> 00:18:08.820 align:start position:0% marketplace with a broker service 00:18:08.820 --> 00:18:11.330 align:start position:0% marketplace with a broker service running<00:18:09.059> on<00:18:09.179> him<00:18:09.600> on<00:18:09.840> a<00:18:09.899> blockchain<00:18:10.259> such<00:18:11.129> that 00:18:11.330 --> 00:18:11.340 align:start position:0% running on him on a blockchain such that 00:18:11.340 --> 00:18:14.570 align:start position:0% running on him on a blockchain such that a<00:18:11.369> buyer<00:18:11.730> who<00:18:12.509> uses<00:18:12.899> and<00:18:13.379> needs<00:18:13.799> this<00:18:14.129> trusted 00:18:14.570 --> 00:18:14.580 align:start position:0% a buyer who uses and needs this trusted 00:18:14.580 --> 00:18:18.349 align:start position:0% a buyer who uses and needs this trusted compute<00:18:15.389> service<00:18:15.779> can<00:18:16.350> now<00:18:16.499> find<00:18:16.919> it<00:18:17.159> and<00:18:17.369> pay 00:18:18.349 --> 00:18:18.359 align:start position:0% compute service can now find it and pay 00:18:18.359 --> 00:18:20.409 align:start position:0% compute service can now find it and pay for<00:18:18.629> it<00:18:18.720> on<00:18:18.929> a<00:18:18.960> per<00:18:19.259> transaction<00:18:19.710> or<00:18:20.100> on<00:18:20.309> a 00:18:20.409 --> 00:18:20.419 align:start position:0% for it on a per transaction or on a 00:18:20.419 --> 00:18:23.330 align:start position:0% for it on a per transaction or on a subscription<00:18:21.419> basis<00:18:22.139> and<00:18:22.289> now<00:18:22.379> anybody<00:18:23.070> in 00:18:23.330 --> 00:18:23.340 align:start position:0% subscription basis and now anybody in 00:18:23.340 --> 00:18:26.749 align:start position:0% subscription basis and now anybody in the<00:18:23.759> world<00:18:23.909> who<00:18:24.210> runs<00:18:25.220> such<00:18:26.220> a<00:18:26.249> trusted 00:18:26.749 --> 00:18:26.759 align:start position:0% the world who runs such a trusted 00:18:26.759 --> 00:18:29.359 align:start position:0% the world who runs such a trusted compute<00:18:27.570> service<00:18:27.929> can<00:18:28.109> register<00:18:28.289> it<00:18:28.710> can 00:18:29.359 --> 00:18:29.369 align:start position:0% compute service can register it can 00:18:29.369 --> 00:18:33.830 align:start position:0% compute service can register it can expose<00:18:30.269> it<00:18:30.570> and<00:18:30.720> can<00:18:31.379> offer<00:18:31.649> it<00:18:32.059> to<00:18:33.059> to<00:18:33.389> anyone 00:18:33.830 --> 00:18:33.840 align:start position:0% expose it and can offer it to to anyone 00:18:33.840 --> 00:18:36.889 align:start position:0% expose it and can offer it to to anyone on<00:18:34.799> this<00:18:35.669> planet<00:18:36.059> and<00:18:36.179> they<00:18:36.330> can<00:18:36.539> actually 00:18:36.889 --> 00:18:36.899 align:start position:0% on this planet and they can actually 00:18:36.899 --> 00:18:39.200 align:start position:0% on this planet and they can actually resell<00:18:37.259> it<00:18:37.440> if<00:18:37.619> they<00:18:38.100> want<00:18:38.340> to<00:18:38.429> however 00:18:39.200 --> 00:18:39.210 align:start position:0% resell it if they want to however 00:18:39.210 --> 00:18:43.669 align:start position:0% resell it if they want to however because<00:18:40.200> of<00:18:40.999> the<00:18:41.999> way<00:18:42.149> this<00:18:42.389> this<00:18:42.929> this<00:18:43.409> works 00:18:43.669 --> 00:18:43.679 align:start position:0% because of the way this this this works 00:18:43.679 --> 00:18:49.479 align:start position:0% because of the way this this this works you<00:18:44.279> can<00:18:44.489> now<00:18:44.609> exact<00:18:45.119> another<00:18:46.109> rent<00:18:48.139> it's<00:18:49.139> fine 00:18:49.479 --> 00:18:49.489 align:start position:0% you can now exact another rent it's fine 00:18:49.489 --> 00:18:52.149 align:start position:0% you can now exact another rent it's fine if<00:18:50.489> you<00:18:50.549> guys<00:18:50.789> can<00:18:51.029> hear<00:18:51.149> me<00:18:51.210> all<00:18:51.389> right<00:18:51.570> then 00:18:52.149 --> 00:18:52.159 align:start position:0% if you guys can hear me all right then 00:18:52.159 --> 00:18:56.599 align:start position:0% if you guys can hear me all right then and<00:18:53.159> that's<00:18:53.659> then<00:18:54.659> then<00:18:55.169> that's<00:18:55.350> good<00:18:55.559> so<00:18:56.070> this 00:18:56.599 --> 00:18:56.609 align:start position:0% and that's then then that's good so this 00:18:56.609 --> 00:18:58.789 align:start position:0% and that's then then that's good so this way<00:18:56.820> the<00:18:57.059> provider<00:18:57.480> can<00:18:58.019> can<00:18:58.590> also 00:18:58.789 --> 00:18:58.799 align:start position:0% way the provider can can also 00:18:58.799 --> 00:19:01.039 align:start position:0% way the provider can can also participate<00:18:59.669> on<00:19:00.359> the<00:19:00.690> subsequent 00:19:01.039 --> 00:19:01.049 align:start position:0% participate on the subsequent 00:19:01.049 --> 00:19:05.109 align:start position:0% participate on the subsequent monetization<00:19:01.739> of<00:19:02.039> that<00:19:02.429> secure<00:19:03.389> service<00:19:03.749> so 00:19:05.109 --> 00:19:05.119 align:start position:0% monetization of that secure service so 00:19:05.119 --> 00:19:07.190 align:start position:0% monetization of that secure service so through<00:19:06.119> the<00:19:06.269> through<00:19:06.720> the<00:19:06.779> through<00:19:06.899> the 00:19:07.190 --> 00:19:07.200 align:start position:0% through the through the through the 00:19:07.200 --> 00:19:10.129 align:start position:0% through the through the through the marketplace<00:19:07.739> so<00:19:08.070> again<00:19:08.970> we're<00:19:09.239> we're<00:19:09.629> we're 00:19:10.129 --> 00:19:10.139 align:start position:0% marketplace so again we're we're we're 00:19:10.139 --> 00:19:12.619 align:start position:0% marketplace so again we're we're we're discussing<00:19:10.499> with<00:19:10.830> with<00:19:11.129> with<00:19:11.369> various<00:19:11.730> om 00:19:12.619 --> 00:19:12.629 align:start position:0% discussing with with with various om 00:19:12.629 --> 00:19:14.720 align:start position:0% discussing with with with various om providers<00:19:13.139> to<00:19:13.619> actually<00:19:13.950> to<00:19:14.340> actually<00:19:14.580> build 00:19:14.720 --> 00:19:14.730 align:start position:0% providers to actually to actually build 00:19:14.730 --> 00:19:18.080 align:start position:0% providers to actually to actually build such<00:19:14.909> a<00:19:14.940> such<00:19:15.720> a<00:19:15.749> marketplace<00:19:16.309> so<00:19:17.309> that's 00:19:18.080 --> 00:19:18.090 align:start position:0% such a such a marketplace so that's 00:19:18.090 --> 00:19:20.389 align:start position:0% such a such a marketplace so that's that's<00:19:18.480> very<00:19:18.600> exciting<00:19:19.320> work<00:19:19.529> that's<00:19:19.830> that's 00:19:20.389 --> 00:19:20.399 align:start position:0% that's very exciting work that's that's 00:19:20.399 --> 00:19:23.330 align:start position:0% that's very exciting work that's that's going<00:19:20.580> on<00:19:20.879> that<00:19:21.539> we're<00:19:21.749> we<00:19:22.259> we<00:19:22.799> want<00:19:23.009> to<00:19:23.129> push 00:19:23.330 --> 00:19:23.340 align:start position:0% going on that we're we we want to push 00:19:23.340 --> 00:19:26.989 align:start position:0% going on that we're we we want to push we<00:19:23.999> want<00:19:24.210> to<00:19:24.299> push<00:19:24.480> forward<00:19:24.840> and<00:19:25.730> so<00:19:26.730> when<00:19:26.909> you 00:19:26.989 --> 00:19:26.999 align:start position:0% we want to push forward and so when you 00:19:26.999 --> 00:19:30.019 align:start position:0% we want to push forward and so when you look<00:19:27.029> at<00:19:27.419> the<00:19:28.200> services<00:19:28.769> the<00:19:29.279> applications 00:19:30.019 --> 00:19:30.029 align:start position:0% look at the services the applications 00:19:30.029 --> 00:19:33.139 align:start position:0% look at the services the applications and<00:19:30.419> the<00:19:30.960> and<00:19:31.169> the<00:19:31.679> layer<00:19:31.889> and<00:19:32.129> the<00:19:32.669> layer<00:19:32.700> one 00:19:33.139 --> 00:19:33.149 align:start position:0% and the and the layer and the layer one 00:19:33.149 --> 00:19:37.789 align:start position:0% and the and the layer and the layer one you<00:19:33.600> see<00:19:33.960> how<00:19:34.289> the<00:19:35.269> trusted<00:19:36.269> computing<00:19:36.799> really 00:19:37.789 --> 00:19:37.799 align:start position:0% you see how the trusted computing really 00:19:37.799 --> 00:19:41.629 align:start position:0% you see how the trusted computing really add<00:19:38.029> to<00:19:39.029> as<00:19:39.869> Sanjay<00:19:40.320> said<00:19:40.649> to<00:19:41.460> the 00:19:41.629 --> 00:19:41.639 align:start position:0% add to as Sanjay said to the 00:19:41.639 --> 00:19:45.080 align:start position:0% add to as Sanjay said to the democratization<00:19:42.299> and<00:19:43.669> decentralization<00:19:44.669> of 00:19:45.080 --> 00:19:45.090 align:start position:0% democratization and decentralization of 00:19:45.090 --> 00:19:47.779 align:start position:0% democratization and decentralization of block<00:19:45.809> chains<00:19:46.139> not<00:19:46.350> only<00:19:46.739> if<00:19:47.039> they're<00:19:47.369> iam<00:19:47.519> but 00:19:47.779 --> 00:19:47.789 align:start position:0% block chains not only if they're iam but 00:19:47.789 --> 00:19:50.899 align:start position:0% block chains not only if they're iam but any<00:19:48.029> blockchain<00:19:48.570> that's<00:19:49.169> out<00:19:49.350> there<00:19:49.909> so 00:19:50.899 --> 00:19:50.909 align:start position:0% any blockchain that's out there so 00:19:50.909 --> 00:19:54.259 align:start position:0% any blockchain that's out there so that's<00:19:51.210> that's<00:19:51.599> why<00:19:51.779> we're<00:19:51.989> really<00:19:53.269> excited 00:19:54.259 --> 00:19:54.269 align:start position:0% that's that's why we're really excited 00:19:54.269 --> 00:19:55.299 align:start position:0% that's that's why we're really excited about<00:19:54.359> this 00:19:55.299 --> 00:19:55.309 align:start position:0% about this 00:19:55.309 --> 00:19:57.970 align:start position:0% about this aspect<00:19:55.669> and<00:19:55.820> therefore<00:19:56.149> it's<00:19:56.299> a<00:19:56.389> really<00:19:56.980> want 00:19:57.970 --> 00:19:57.980 align:start position:0% aspect and therefore it's a really want 00:19:57.980 --> 00:19:59.799 align:start position:0% aspect and therefore it's a really want to<00:19:58.070> finish<00:19:58.249> here<00:19:58.519> with<00:19:58.639> a<00:19:58.669> call<00:19:58.970> to<00:19:59.149> action<00:19:59.330> to 00:19:59.799 --> 00:19:59.809 align:start position:0% to finish here with a call to action to 00:19:59.809 --> 00:20:04.330 align:start position:0% to finish here with a call to action to the<00:20:00.710> community<00:20:01.580> right<00:20:02.269> we<00:20:02.720> invite<00:20:03.169> you<00:20:04.039> to 00:20:04.330 --> 00:20:04.340 align:start position:0% the community right we invite you to 00:20:04.340 --> 00:20:06.700 align:start position:0% the community right we invite you to review<00:20:04.909> improve<00:20:05.629> and<00:20:05.899> to<00:20:05.990> help<00:20:06.139> implement 00:20:06.700 --> 00:20:06.710 align:start position:0% review improve and to help implement 00:20:06.710 --> 00:20:11.499 align:start position:0% review improve and to help implement this<00:20:07.309> vision<00:20:07.580> not<00:20:08.539> only<00:20:09.789> for<00:20:10.789> aetherium<00:20:11.120> but 00:20:11.499 --> 00:20:11.509 align:start position:0% this vision not only for aetherium but 00:20:11.509 --> 00:20:13.720 align:start position:0% this vision not only for aetherium but for<00:20:11.720> all<00:20:11.870> blockchains<00:20:12.470> such<00:20:13.159> that<00:20:13.340> they<00:20:13.519> can 00:20:13.720 --> 00:20:13.730 align:start position:0% for all blockchains such that they can 00:20:13.730 --> 00:20:17.350 align:start position:0% for all blockchains such that they can be<00:20:14.149> successful<00:20:14.509> and<00:20:15.080> deliver<00:20:15.940> on<00:20:16.940> their 00:20:17.350 --> 00:20:17.360 align:start position:0% be successful and deliver on their 00:20:17.360 --> 00:20:20.139 align:start position:0% be successful and deliver on their promise<00:20:18.129> and<00:20:19.129> as<00:20:19.279> a<00:20:19.309> first<00:20:19.580> step 00:20:20.139 --> 00:20:20.149 align:start position:0% promise and as a first step 00:20:20.149 --> 00:20:23.200 align:start position:0% promise and as a first step please<00:20:20.480> join<00:20:20.840> us<00:20:20.899> tomorrow<00:20:21.940> at<00:20:22.940> the<00:20:23.090> other 00:20:23.200 --> 00:20:23.210 align:start position:0% please join us tomorrow at the other 00:20:23.210 --> 00:20:25.570 align:start position:0% please join us tomorrow at the other trusted<00:20:23.600> compute<00:20:24.110> and<00:20:24.679> other<00:20:24.830> to<00:20:25.100> compute 00:20:25.570 --> 00:20:25.580 align:start position:0% trusted compute and other to compute 00:20:25.580 --> 00:20:28.389 align:start position:0% trusted compute and other to compute enthusiasts<00:20:26.409> actually<00:20:27.409> in<00:20:27.919> the<00:20:28.009> ultraviolet 00:20:28.389 --> 00:20:28.399 align:start position:0% enthusiasts actually in the ultraviolet 00:20:28.399 --> 00:20:31.869 align:start position:0% enthusiasts actually in the ultraviolet Room<00:20:28.759> at<00:20:29.240> 10<00:20:29.570> a.m.<00:20:30.070> what<00:20:31.070> we<00:20:31.190> talk<00:20:31.429> about<00:20:31.700> the 00:20:31.869 --> 00:20:31.879 align:start position:0% Room at 10 a.m. what we talk about the 00:20:31.879 --> 00:20:35.430 align:start position:0% Room at 10 a.m. what we talk about the future<00:20:32.240> of<00:20:32.419> aetherium<00:20:33.350> with<00:20:33.740> trusted<00:20:34.220> compute 00:20:35.430 --> 00:20:35.440 align:start position:0% future of aetherium with trusted compute 00:20:35.440 --> 00:20:41.220 align:start position:0% future of aetherium with trusted compute thank<00:20:36.440> you<00:20:37.539> thank<00:20:38.539> you<00:20:38.600> very<00:20:38.749> much<00:20:38.899> guys<00:20:39.110> we 00:20:41.220 --> 00:20:41.230 align:start position:0% thank you thank you very much guys we 00:20:41.230 --> 00:20:44.590 align:start position:0% thank you thank you very much guys we got<00:20:42.230> eight<00:20:42.499> minutes<00:20:42.950> for<00:20:43.070> questions<00:20:43.490> so<00:20:43.970> this 00:20:44.590 --> 00:20:44.600 align:start position:0% got eight minutes for questions so this 00:20:44.600 --> 00:20:49.899 align:start position:0% got eight minutes for questions so this get<00:20:45.499> started<00:20:47.889> on<00:20:48.889> that<00:20:48.950> previous<00:20:49.429> slide<00:20:49.460> you 00:20:49.899 --> 00:20:49.909 align:start position:0% get started on that previous slide you 00:20:49.909 --> 00:20:52.840 align:start position:0% get started on that previous slide you had<00:20:50.059> a<00:20:50.090> the<00:20:50.659> buyer<00:20:50.889> reselling<00:20:51.889> data<00:20:52.100> from<00:20:52.789> the 00:20:52.840 --> 00:20:52.850 align:start position:0% had a the buyer reselling data from the 00:20:52.850 --> 00:20:54.249 align:start position:0% had a the buyer reselling data from the provider<00:20:53.179> and<00:20:53.269> the<00:20:53.389> provider<00:20:53.509> collecting 00:20:54.249 --> 00:20:54.259 align:start position:0% provider and the provider collecting 00:20:54.259 --> 00:20:56.109 align:start position:0% provider and the provider collecting rent<00:20:54.470> from<00:20:54.710> the<00:20:54.830> buyer<00:20:55.119> third-party 00:20:56.109 --> 00:20:56.119 align:start position:0% rent from the buyer third-party 00:20:56.119 --> 00:20:59.049 align:start position:0% rent from the buyer third-party customers<00:20:56.919> how<00:20:57.919> in<00:20:58.009> the<00:20:58.100> world<00:20:58.129> can<00:20:58.460> you<00:20:58.639> do 00:20:59.049 --> 00:20:59.059 align:start position:0% customers how in the world can you do 00:20:59.059 --> 00:21:03.039 align:start position:0% customers how in the world can you do that<00:21:00.730> your<00:21:01.730> your<00:21:02.090> you're<00:21:02.450> actually<00:21:02.869> not 00:21:03.039 --> 00:21:03.049 align:start position:0% that your your you're actually not 00:21:03.049 --> 00:21:04.840 align:start position:0% that your your you're actually not reselling<00:21:03.799> the<00:21:03.950> data<00:21:04.159> you<00:21:04.340> were<00:21:04.429> reselling 00:21:04.840 --> 00:21:04.850 align:start position:0% reselling the data you were reselling 00:21:04.850 --> 00:21:07.600 align:start position:0% reselling the data you were reselling the<00:21:04.970> service<00:21:05.499> which<00:21:06.499> means<00:21:06.740> you<00:21:07.039> are<00:21:07.070> you're 00:21:07.600 --> 00:21:07.610 align:start position:0% the service which means you are you're 00:21:07.610 --> 00:21:10.889 align:start position:0% the service which means you are you're you<00:21:07.999> still<00:21:08.299> control<00:21:08.720> who<00:21:09.259> who<00:21:09.799> gets<00:21:10.009> the<00:21:10.220> the 00:21:10.889 --> 00:21:10.899 align:start position:0% you still control who who gets the the 00:21:10.899 --> 00:21:13.529 align:start position:0% you still control who who gets the the service<00:21:11.899> there<00:21:12.200> is<00:21:12.230> still<00:21:12.649> hold<00:21:13.309> there 00:21:13.529 --> 00:21:13.539 align:start position:0% service there is still hold there 00:21:13.539 --> 00:21:16.269 align:start position:0% service there is still hold there permissioning<00:21:14.539> so<00:21:14.899> if<00:21:15.139> he<00:21:15.559> wants<00:21:15.799> to<00:21:15.830> resell 00:21:16.269 --> 00:21:16.279 align:start position:0% permissioning so if he wants to resell 00:21:16.279 --> 00:21:16.690 align:start position:0% permissioning so if he wants to resell it 00:21:16.690 --> 00:21:16.700 align:start position:0% it 00:21:16.700 --> 00:21:19.210 align:start position:0% it the<00:21:17.509> other<00:21:17.690> party<00:21:18.379> needs<00:21:18.590> to<00:21:18.740> be<00:21:18.830> added<00:21:19.190> to 00:21:19.210 --> 00:21:19.220 align:start position:0% the other party needs to be added to 00:21:19.220 --> 00:21:21.369 align:start position:0% the other party needs to be added to that<00:21:19.369> that<00:21:20.059> to<00:21:20.480> that<00:21:20.659> to<00:21:20.899> that<00:21:21.049> service 00:21:21.369 --> 00:21:21.379 align:start position:0% that that to that to that service 00:21:21.379 --> 00:21:24.960 align:start position:0% that that to that to that service contract<00:21:21.850> so<00:21:22.850> that's<00:21:23.119> how<00:21:23.269> you<00:21:23.330> how<00:21:23.809> you<00:21:23.840> an<00:21:24.169> in 00:21:24.960 --> 00:21:24.970 align:start position:0% contract so that's how you how you an in 00:21:24.970 --> 00:21:27.669 align:start position:0% contract so that's how you how you an in ensure<00:21:25.970> that<00:21:26.240> you<00:21:26.360> can<00:21:26.539> that<00:21:27.200> you<00:21:27.320> get<00:21:27.470> paid 00:21:27.669 --> 00:21:27.679 align:start position:0% ensure that you can that you get paid 00:21:27.679 --> 00:21:31.109 align:start position:0% ensure that you can that you get paid for<00:21:27.919> that<00:21:27.980> for<00:21:28.580> that<00:21:28.700> service<00:21:28.999> if<00:21:29.149> it's<00:21:29.299> resold 00:21:31.109 --> 00:21:31.119 align:start position:0% for that for that service if it's resold 00:21:31.119 --> 00:21:33.999 align:start position:0% for that for that service if it's resold so<00:21:32.119> what<00:21:32.600> do<00:21:32.659> you<00:21:32.749> say<00:21:32.929> to<00:21:32.990> ease<00:21:33.259> the<00:21:33.470> fears<00:21:33.710> of 00:21:33.999 --> 00:21:34.009 align:start position:0% so what do you say to ease the fears of 00:21:34.009 --> 00:21:37.299 align:start position:0% so what do you say to ease the fears of people<00:21:34.039> that<00:21:35.559> generally<00:21:36.559> notice<00:21:37.129> that 00:21:37.299 --> 00:21:37.309 align:start position:0% people that generally notice that 00:21:37.309 --> 00:21:39.100 align:start position:0% people that generally notice that trusted<00:21:37.700> compute<00:21:38.090> relies<00:21:38.389> on<00:21:38.419> trusted 00:21:39.100 --> 00:21:39.110 align:start position:0% trusted compute relies on trusted 00:21:39.110 --> 00:21:41.529 align:start position:0% trusted compute relies on trusted hardware<00:21:39.440> that's<00:21:39.710> oftentimes<00:21:40.580> closed<00:21:41.240> source 00:21:41.529 --> 00:21:41.539 align:start position:0% hardware that's oftentimes closed source 00:21:41.539 --> 00:21:44.489 align:start position:0% hardware that's oftentimes closed source and<00:21:41.899> not<00:21:42.049> allow<00:21:42.559> for<00:21:42.950> security<00:21:43.429> reviews 00:21:44.489 --> 00:21:44.499 align:start position:0% and not allow for security reviews 00:21:44.499 --> 00:21:46.330 align:start position:0% and not allow for security reviews resulting<00:21:45.499> in<00:21:45.559> things<00:21:45.740> like<00:21:45.830> the<00:21:46.009> level<00:21:46.249> 1 00:21:46.330 --> 00:21:46.340 align:start position:0% resulting in things like the level 1 00:21:46.340 --> 00:21:48.549 align:start position:0% resulting in things like the level 1 terminal<00:21:46.580> fault<00:21:46.940> and<00:21:47.179> then<00:21:47.299> a<00:21:47.659> recent<00:21:48.320> breach 00:21:48.549 --> 00:21:48.559 align:start position:0% terminal fault and then a recent breach 00:21:48.559 --> 00:21:50.080 align:start position:0% terminal fault and then a recent breach that<00:21:48.830> exposed<00:21:49.159> system<00:21:49.460> management<00:21:49.700> mode<00:21:49.879> on 00:21:50.080 --> 00:21:50.090 align:start position:0% that exposed system management mode on 00:21:50.090 --> 00:21:52.269 align:start position:0% that exposed system management mode on Intel<00:21:50.360> chipset<00:21:50.809> invalidated<00:21:51.259> SGX<00:21:51.740> completely 00:21:52.269 --> 00:21:52.279 align:start position:0% Intel chipset invalidated SGX completely 00:21:52.279 --> 00:21:54.220 align:start position:0% Intel chipset invalidated SGX completely just<00:21:52.639> how<00:21:52.789> do<00:21:52.850> you<00:21:52.999> how<00:21:53.600> do<00:21:53.659> you<00:21:53.779> reconcile 00:21:54.220 --> 00:21:54.230 align:start position:0% just how do you how do you reconcile 00:21:54.230 --> 00:21:58.659 align:start position:0% just how do you how do you reconcile that<00:21:55.539> so<00:21:56.539> the<00:21:57.169> the<00:21:57.559> general<00:21:58.190> thing<00:21:58.340> is<00:21:58.490> like 00:21:58.659 --> 00:21:58.669 align:start position:0% that so the the general thing is like 00:21:58.669 --> 00:22:03.369 align:start position:0% that so the the general thing is like you<00:21:58.789> know<00:21:59.529> being<00:22:00.730> as<00:22:01.730> much<00:22:01.970> as<00:22:02.119> open<00:22:02.779> as<00:22:02.899> we<00:22:03.110> can 00:22:03.369 --> 00:22:03.379 align:start position:0% you know being as much as open as we can 00:22:03.379 --> 00:22:05.919 align:start position:0% you know being as much as open as we can in<00:22:03.980> terms<00:22:04.279> of<00:22:04.429> like 00:22:05.919 --> 00:22:05.929 align:start position:0% in terms of like 00:22:05.929 --> 00:22:10.120 align:start position:0% in terms of like the<00:22:06.549> the<00:22:07.549> breaches<00:22:07.970> happen<00:22:08.299> not<00:22:08.750> because<00:22:09.130> they 00:22:10.120 --> 00:22:10.130 align:start position:0% the the breaches happen not because they 00:22:10.130 --> 00:22:11.500 align:start position:0% the the breaches happen not because they are<00:22:10.190> intentional<00:22:10.790> which<00:22:11.059> has<00:22:11.210> happened 00:22:11.500 --> 00:22:11.510 align:start position:0% are intentional which has happened 00:22:11.510 --> 00:22:13.930 align:start position:0% are intentional which has happened because<00:22:11.600> you<00:22:11.960> know<00:22:12.080> we<00:22:12.410> have<00:22:12.669> starting<00:22:13.669> to<00:22:13.790> use 00:22:13.930 --> 00:22:13.940 align:start position:0% because you know we have starting to use 00:22:13.940 --> 00:22:15.909 align:start position:0% because you know we have starting to use this<00:22:14.090> technology<00:22:14.690> at<00:22:14.809> scale<00:22:15.140> and<00:22:15.410> many<00:22:15.590> people 00:22:15.909 --> 00:22:15.919 align:start position:0% this technology at scale and many people 00:22:15.919 --> 00:22:20.230 align:start position:0% this technology at scale and many people are<00:22:16.010> looking<00:22:16.130> at<00:22:16.429> it<00:22:16.630> and<00:22:17.630> as<00:22:18.460> at<00:22:19.460> Intel<00:22:19.970> right 00:22:20.230 --> 00:22:20.240 align:start position:0% are looking at it and as at Intel right 00:22:20.240 --> 00:22:23.230 align:start position:0% are looking at it and as at Intel right we<00:22:20.540> are<00:22:20.720> committed<00:22:21.260> to<00:22:21.730> you<00:22:22.730> know<00:22:22.850> working 00:22:23.230 --> 00:22:23.240 align:start position:0% we are committed to you know working 00:22:23.240 --> 00:22:27.460 align:start position:0% we are committed to you know working continuously<00:22:24.020> and<00:22:25.090> quickly<00:22:26.090> to<00:22:26.320> you<00:22:27.320> know 00:22:27.460 --> 00:22:27.470 align:start position:0% continuously and quickly to you know 00:22:27.470 --> 00:22:29.560 align:start position:0% continuously and quickly to you know provide<00:22:27.799> patches<00:22:28.280> provide<00:22:28.669> whatever<00:22:29.270> is 00:22:29.560 --> 00:22:29.570 align:start position:0% provide patches provide whatever is 00:22:29.570 --> 00:22:33.580 align:start position:0% provide patches provide whatever is needed<00:22:29.780> and<00:22:30.820> as<00:22:31.820> you<00:22:32.480> know<00:22:32.600> the<00:22:32.840> the<00:22:33.260> breaches 00:22:33.580 --> 00:22:33.590 align:start position:0% needed and as you know the the breaches 00:22:33.590 --> 00:22:35.860 align:start position:0% needed and as you know the the breaches that<00:22:33.620> happened<00:22:34.240> there's<00:22:35.240> a<00:22:35.330> lot<00:22:35.780> of 00:22:35.860 --> 00:22:35.870 align:start position:0% that happened there's a lot of 00:22:35.870 --> 00:22:37.390 align:start position:0% that happened there's a lot of information<00:22:36.140> on<00:22:36.530> the<00:22:36.590> interweb<00:22:36.950> site<00:22:37.190> in 00:22:37.390 --> 00:22:37.400 align:start position:0% information on the interweb site in 00:22:37.400 --> 00:22:39.310 align:start position:0% information on the interweb site in terms<00:22:37.640> of<00:22:37.790> where<00:22:38.330> you<00:22:38.480> can<00:22:38.630> get<00:22:38.750> the<00:22:38.900> patches 00:22:39.310 --> 00:22:39.320 align:start position:0% terms of where you can get the patches 00:22:39.320 --> 00:22:42.490 align:start position:0% terms of where you can get the patches and<00:22:39.530> how<00:22:39.620> we<00:22:39.679> can<00:22:39.919> basically<00:22:40.450> you<00:22:41.450> know<00:22:41.600> put<00:22:42.380> it 00:22:42.490 --> 00:22:42.500 align:start position:0% and how we can basically you know put it 00:22:42.500 --> 00:22:45.130 align:start position:0% and how we can basically you know put it on<00:22:42.620> the<00:22:42.740> systems<00:22:43.160> and<00:22:43.340> how<00:22:43.460> we<00:22:43.520> can<00:22:44.020> you<00:22:45.020> know 00:22:45.130 --> 00:22:45.140 align:start position:0% on the systems and how we can you know 00:22:45.140 --> 00:22:47.320 align:start position:0% on the systems and how we can you know figure<00:22:45.919> out<00:22:46.070> whether<00:22:46.640> the<00:22:46.880> system<00:22:47.210> has 00:22:47.320 --> 00:22:47.330 align:start position:0% figure out whether the system has 00:22:47.330 --> 00:22:48.460 align:start position:0% figure out whether the system has embarrassed<00:22:47.660> so<00:22:48.049> there's<00:22:48.230> a<00:22:48.260> lot<00:22:48.350> of 00:22:48.460 --> 00:22:48.470 align:start position:0% embarrassed so there's a lot of 00:22:48.470 --> 00:22:52.060 align:start position:0% embarrassed so there's a lot of information<00:22:48.980> here<00:22:50.350> you<00:22:51.350> know<00:22:51.440> if<00:22:51.650> you're<00:22:51.799> if 00:22:52.060 --> 00:22:52.070 align:start position:0% information here you know if you're if 00:22:52.070 --> 00:22:53.530 align:start position:0% information here you know if you're if you<00:22:52.250> if<00:22:52.520> you<00:22:52.640> think<00:22:52.820> about<00:22:52.970> side-channel 00:22:53.530 --> 00:22:53.540 align:start position:0% you if you think about side-channel 00:22:53.540 --> 00:22:59.020 align:start position:0% you if you think about side-channel attacks<00:22:55.690> actually<00:22:56.690> I<00:22:57.520> talked<00:22:58.520> with<00:22:58.640> with 00:22:59.020 --> 00:22:59.030 align:start position:0% attacks actually I talked with with 00:22:59.030 --> 00:23:00.789 align:start position:0% attacks actually I talked with with Marla<00:22:59.330> gray<00:22:59.480> from<00:22:59.750> from<00:23:00.110> from<00:23:00.350> Microsoft 00:23:00.789 --> 00:23:00.799 align:start position:0% Marla gray from from from Microsoft 00:23:00.799 --> 00:23:02.980 align:start position:0% Marla gray from from from Microsoft yesterday<00:23:01.190> and<00:23:01.340> we'll<00:23:01.429> probably<00:23:01.940> do<00:23:02.210> do<00:23:02.600> a 00:23:02.980 --> 00:23:02.990 align:start position:0% yesterday and we'll probably do do a 00:23:02.990 --> 00:23:05.470 align:start position:0% yesterday and we'll probably do do a little<00:23:03.460> experiment<00:23:04.460> with<00:23:04.580> with<00:23:04.970> Microsoft 00:23:05.470 --> 00:23:05.480 align:start position:0% little experiment with with Microsoft 00:23:05.480 --> 00:23:08.380 align:start position:0% little experiment with with Microsoft research<00:23:05.840> to<00:23:06.530> see<00:23:07.460> whether<00:23:07.700> you<00:23:07.880> can<00:23:08.030> actually 00:23:08.380 --> 00:23:08.390 align:start position:0% research to see whether you can actually 00:23:08.390 --> 00:23:11.049 align:start position:0% research to see whether you can actually do<00:23:08.480> a<00:23:08.510> side<00:23:08.780> channel<00:23:09.110> attack<00:23:09.620> on<00:23:09.890> a<00:23:10.220> laptop<00:23:10.490> in 00:23:11.049 --> 00:23:11.059 align:start position:0% do a side channel attack on a laptop in 00:23:11.059 --> 00:23:16.120 align:start position:0% do a side channel attack on a laptop in a<00:23:11.270> in<00:23:11.870> a<00:23:12.020> Starbucks<00:23:13.660> if<00:23:14.660> that's<00:23:14.900> if<00:23:15.260> that's<00:23:15.350> if 00:23:16.120 --> 00:23:16.130 align:start position:0% a in a Starbucks if that's if that's if 00:23:16.130 --> 00:23:17.620 align:start position:0% a in a Starbucks if that's if that's if you<00:23:16.280> can<00:23:16.429> do<00:23:16.580> that<00:23:16.760> then<00:23:16.970> you<00:23:17.000> really<00:23:17.480> have<00:23:17.600> a 00:23:17.620 --> 00:23:17.630 align:start position:0% you can do that then you really have a 00:23:17.630 --> 00:23:20.830 align:start position:0% you can do that then you really have a problem<00:23:17.809> alright<00:23:19.090> because<00:23:20.090> typically<00:23:20.600> you 00:23:20.830 --> 00:23:20.840 align:start position:0% problem alright because typically you 00:23:20.840 --> 00:23:22.780 align:start position:0% problem alright because typically you will<00:23:20.960> not<00:23:21.110> be<00:23:21.290> able<00:23:21.380> to<00:23:21.559> to<00:23:21.980> get<00:23:22.160> the<00:23:22.460> apparatus 00:23:22.780 --> 00:23:22.790 align:start position:0% will not be able to to get the apparatus 00:23:22.790 --> 00:23:25.180 align:start position:0% will not be able to to get the apparatus you<00:23:23.750> need<00:23:23.960> into<00:23:24.290> a<00:23:24.320> secure<00:23:24.650> data<00:23:24.860> center 00:23:25.180 --> 00:23:25.190 align:start position:0% you need into a secure data center 00:23:25.190 --> 00:23:28.000 align:start position:0% you need into a secure data center that's<00:23:25.309> really<00:23:25.669> hard<00:23:25.850> so<00:23:26.480> it's<00:23:27.380> more<00:23:27.559> like<00:23:27.770> on 00:23:28.000 --> 00:23:28.010 align:start position:0% that's really hard so it's more like on 00:23:28.010 --> 00:23:30.100 align:start position:0% that's really hard so it's more like on your<00:23:28.250> on<00:23:28.490> your<00:23:28.669> custom<00:23:29.090> custom<00:23:29.510> laptop<00:23:29.900> and 00:23:30.100 --> 00:23:30.110 align:start position:0% your on your custom custom laptop and 00:23:30.110 --> 00:23:33.669 align:start position:0% your on your custom custom laptop and we'll<00:23:31.030> we'll<00:23:32.030> we'll<00:23:32.660> do<00:23:32.840> that<00:23:32.990> more<00:23:33.290> hopefully 00:23:33.669 --> 00:23:33.679 align:start position:0% we'll we'll we'll do that more hopefully 00:23:33.679 --> 00:23:36.400 align:start position:0% we'll we'll we'll do that more hopefully you<00:23:34.580> know<00:23:34.669> in<00:23:35.240> some<00:23:35.510> time<00:23:35.690> could<00:23:35.960> you<00:23:35.990> be<00:23:36.260> able 00:23:36.400 --> 00:23:36.410 align:start position:0% you know in some time could you be able 00:23:36.410 --> 00:23:38.919 align:start position:0% you know in some time could you be able to<00:23:36.530> produce<00:23:36.830> a<00:23:37.100> little<00:23:37.250> low<00:23:38.120> video<00:23:38.360> about<00:23:38.690> that 00:23:38.919 --> 00:23:38.929 align:start position:0% to produce a little low video about that 00:23:38.929 --> 00:23:41.680 align:start position:0% to produce a little low video about that and<00:23:38.990> see<00:23:39.320> how<00:23:39.620> well<00:23:40.340> that<00:23:40.549> works<00:23:40.850> or<00:23:41.090> or 00:23:41.680 --> 00:23:41.690 align:start position:0% and see how well that works or or 00:23:41.690 --> 00:23:45.850 align:start position:0% and see how well that works or or doesn't<00:23:42.470> doesn't<00:23:42.950> work<00:23:43.190> so<00:23:44.350> looking<00:23:45.350> looking 00:23:45.850 --> 00:23:45.860 align:start position:0% doesn't doesn't work so looking looking 00:23:45.860 --> 00:23:48.549 align:start position:0% doesn't doesn't work so looking looking forward<00:23:46.330> looking<00:23:47.330> forward<00:23:47.660> to<00:23:48.200> that 00:23:48.549 --> 00:23:48.559 align:start position:0% forward looking forward to that 00:23:48.559 --> 00:23:52.510 align:start position:0% forward looking forward to that so<00:23:48.830> and<00:23:49.280> in<00:23:49.880> the<00:23:50.059> end<00:23:50.179> the<00:23:51.110> more<00:23:51.440> you<00:23:51.740> get<00:23:51.980> these 00:23:52.510 --> 00:23:52.520 align:start position:0% so and in the end the more you get these 00:23:52.520 --> 00:23:55.000 align:start position:0% so and in the end the more you get these trusted<00:23:53.210> compute<00:23:53.690> services<00:23:54.200> out<00:23:54.350> into<00:23:54.919> the 00:23:55.000 --> 00:23:55.010 align:start position:0% trusted compute services out into the 00:23:55.010 --> 00:23:57.570 align:start position:0% trusted compute services out into the marketplace<00:23:55.370> and<00:23:55.840> into<00:23:56.840> the<00:23:56.929> hands<00:23:57.260> of<00:23:57.350> people 00:23:57.570 --> 00:23:57.580 align:start position:0% marketplace and into the hands of people 00:23:57.580 --> 00:24:00.430 align:start position:0% marketplace and into the hands of people the<00:23:58.580> more<00:23:58.820> secure<00:23:59.419> is<00:23:59.570> going<00:23:59.780> to<00:23:59.840> be<00:23:59.990> and<00:24:00.230> the 00:24:00.430 --> 00:24:00.440 align:start position:0% the more secure is going to be and the 00:24:00.440 --> 00:24:03.220 align:start position:0% the more secure is going to be and the more<00:24:01.299> decentralized<00:24:02.299> so<00:24:02.750> if<00:24:02.840> people<00:24:03.049> are 00:24:03.220 --> 00:24:03.230 align:start position:0% more decentralized so if people are 00:24:03.230 --> 00:24:05.020 align:start position:0% more decentralized so if people are offering<00:24:03.530> those<00:24:03.770> those<00:24:04.220> services<00:24:04.610> and<00:24:04.850> other 00:24:05.020 --> 00:24:05.030 align:start position:0% offering those those services and other 00:24:05.030 --> 00:24:09.669 align:start position:0% offering those those services and other people<00:24:05.470> people<00:24:06.470> use<00:24:06.799> it<00:24:07.010> the<00:24:07.400> risk<00:24:07.700> of<00:24:08.679> you 00:24:09.669 --> 00:24:09.679 align:start position:0% people people use it the risk of you 00:24:09.679 --> 00:24:12.250 align:start position:0% people people use it the risk of you know<00:24:09.710> a<00:24:09.830> few<00:24:10.340> controlling<00:24:11.330> the<00:24:11.780> many<00:24:11.990> is 00:24:12.250 --> 00:24:12.260 align:start position:0% know a few controlling the many is 00:24:12.260 --> 00:24:16.900 align:start position:0% know a few controlling the many is really<00:24:12.620> is<00:24:13.580> really<00:24:13.970> low 00:24:16.900 --> 00:24:16.910 align:start position:0% 00:24:16.910 --> 00:24:19.630 align:start position:0% had<00:24:17.570> a<00:24:17.600> question<00:24:17.810> if<00:24:18.200> you<00:24:18.350> could<00:24:18.620> try<00:24:19.580> to 00:24:19.630 --> 00:24:19.640 align:start position:0% had a question if you could try to 00:24:19.640 --> 00:24:23.260 align:start position:0% had a question if you could try to correlate<00:24:20.030> for<00:24:20.720> the<00:24:21.340> you<00:24:22.340> know<00:24:22.460> naive 00:24:23.260 --> 00:24:23.270 align:start position:0% correlate for the you know naive 00:24:23.270 --> 00:24:26.230 align:start position:0% correlate for the you know naive observer<00:24:23.840> who<00:24:24.260> you<00:24:24.740> know<00:24:24.860> sees<00:24:25.490> a<00:24:25.520> vision<00:24:25.760> here 00:24:26.230 --> 00:24:26.240 align:start position:0% observer who you know sees a vision here 00:24:26.240 --> 00:24:28.330 align:start position:0% observer who you know sees a vision here for<00:24:26.510> something<00:24:26.960> that<00:24:27.200> allows<00:24:27.860> additional 00:24:28.330 --> 00:24:28.340 align:start position:0% for something that allows additional 00:24:28.340 --> 00:24:30.760 align:start position:0% for something that allows additional scaling<00:24:29.090> better<00:24:29.540> efficiency<00:24:30.110> of<00:24:30.230> compute<00:24:30.620> and 00:24:30.760 --> 00:24:30.770 align:start position:0% scaling better efficiency of compute and 00:24:30.770 --> 00:24:33.310 align:start position:0% scaling better efficiency of compute and so<00:24:30.920> forth<00:24:31.190> but<00:24:32.060> then<00:24:32.240> it's<00:24:32.420> not<00:24:32.570> really<00:24:32.930> on<00:24:33.170> the 00:24:33.310 --> 00:24:33.320 align:start position:0% so forth but then it's not really on the 00:24:33.320 --> 00:24:35.970 align:start position:0% so forth but then it's not really on the roadmap<00:24:33.500> when<00:24:34.160> you<00:24:34.700> know<00:24:34.790> the<00:24:35.030> etherium 00:24:35.970 --> 00:24:35.980 align:start position:0% roadmap when you know the etherium 00:24:35.980 --> 00:24:37.990 align:start position:0% roadmap when you know the etherium foundation<00:24:36.980> and<00:24:37.160> the<00:24:37.220> group<00:24:37.430> is<00:24:37.610> talking 00:24:37.990 --> 00:24:38.000 align:start position:0% foundation and the group is talking 00:24:38.000 --> 00:24:40.600 align:start position:0% foundation and the group is talking about<00:24:38.090> what's<00:24:38.570> in<00:24:38.780> aetherium<00:24:39.290> 2.0<00:24:39.980> you<00:24:40.460> know 00:24:40.600 --> 00:24:40.610 align:start position:0% about what's in aetherium 2.0 you know 00:24:40.610 --> 00:24:44.410 align:start position:0% about what's in aetherium 2.0 you know zero<00:24:41.150> knowledge<00:24:41.300> proof<00:24:41.480> SAR<00:24:42.640> as<00:24:43.640> both<00:24:43.910> scaling 00:24:44.410 --> 00:24:44.420 align:start position:0% zero knowledge proof SAR as both scaling 00:24:44.420 --> 00:24:48.070 align:start position:0% zero knowledge proof SAR as both scaling and<00:24:44.570> privacy<00:24:45.020> but<00:24:45.730> so<00:24:46.730> just<00:24:47.180> you<00:24:47.630> know<00:24:47.660> can<00:24:47.990> you 00:24:48.070 --> 00:24:48.080 align:start position:0% and privacy but so just you know can you 00:24:48.080 --> 00:24:50.110 align:start position:0% and privacy but so just you know can you say<00:24:48.200> some<00:24:48.380> words<00:24:48.500> about<00:24:48.650> that<00:24:48.800> yeah<00:24:49.580> I<00:24:49.610> could 00:24:50.110 --> 00:24:50.120 align:start position:0% say some words about that yeah I could 00:24:50.120 --> 00:24:53.530 align:start position:0% say some words about that yeah I could start<00:24:50.390> that<00:24:50.570> right<00:24:50.780> so<00:24:51.320> you<00:24:51.740> are<00:24:51.830> right<00:24:52.010> and<00:24:52.540> a 00:24:53.530 --> 00:24:53.540 align:start position:0% start that right so you are right and a 00:24:53.540 --> 00:24:58.450 align:start position:0% start that right so you are right and a lot<00:24:54.260> of<00:24:54.290> it<00:24:54.500> is<00:24:54.650> like<00:24:55.720> generally<00:24:56.720> a<00:24:56.750> lot<00:24:57.080> of<00:24:57.460> you 00:24:58.450 --> 00:24:58.460 align:start position:0% lot of it is like generally a lot of you 00:24:58.460 --> 00:24:59.950 align:start position:0% lot of it is like generally a lot of you know<00:24:58.520> not<00:24:58.730> information<00:24:59.120> about<00:24:59.510> how<00:24:59.600> to<00:24:59.630> suit 00:24:59.950 --> 00:24:59.960 align:start position:0% know not information about how to suit 00:24:59.960 --> 00:25:02.950 align:start position:0% know not information about how to suit computers<00:25:00.290> work<00:25:00.470> and<00:25:00.590> all<00:25:00.680> that<00:25:00.830> stuff<00:25:01.010> so<00:25:01.960> we 00:25:02.950 --> 00:25:02.960 align:start position:0% computers work and all that stuff so we 00:25:02.960 --> 00:25:06.010 align:start position:0% computers work and all that stuff so we have<00:25:03.520> done<00:25:04.520> a<00:25:04.880> lot<00:25:05.150> of<00:25:05.180> work<00:25:05.420> in<00:25:05.600> the<00:25:05.720> context 00:25:06.010 --> 00:25:06.020 align:start position:0% have done a lot of work in the context 00:25:06.020 --> 00:25:09.010 align:start position:0% have done a lot of work in the context of<00:25:06.110> enterprise<00:25:06.500> etherium<00:25:06.980> a<00:25:07.160> wire<00:25:07.970> in<00:25:08.180> for 00:25:09.010 --> 00:25:09.020 align:start position:0% of enterprise etherium a wire in for 00:25:09.020 --> 00:25:11.890 align:start position:0% of enterprise etherium a wire in for example<00:25:09.290> we<00:25:09.560> have<00:25:09.740> we<00:25:10.310> have<00:25:10.760> released<00:25:11.420> a<00:25:11.660> point 00:25:11.890 --> 00:25:11.900 align:start position:0% example we have we have released a point 00:25:11.900 --> 00:25:14.370 align:start position:0% example we have we have released a point five<00:25:12.140> version<00:25:12.500> of<00:25:12.620> an<00:25:12.800> API<00:25:13.190> we<00:25:14.000> are<00:25:14.120> which 00:25:14.370 --> 00:25:14.380 align:start position:0% five version of an API we are which 00:25:14.380 --> 00:25:17.140 align:start position:0% five version of an API we are which anybody<00:25:15.380> on<00:25:15.740> the<00:25:15.890> chain<00:25:16.130> a<00:25:16.160> smart<00:25:16.640> contract<00:25:17.030> on 00:25:17.140 --> 00:25:17.150 align:start position:0% anybody on the chain a smart contract on 00:25:17.150 --> 00:25:20.200 align:start position:0% anybody on the chain a smart contract on the<00:25:17.240> chain<00:25:17.680> can<00:25:18.680> talk<00:25:19.070> to<00:25:19.280> a<00:25:19.340> trusted<00:25:19.550> computer 00:25:20.200 --> 00:25:20.210 align:start position:0% the chain can talk to a trusted computer 00:25:20.210 --> 00:25:21.580 align:start position:0% the chain can talk to a trusted computer and<00:25:20.300> bring<00:25:20.480> the<00:25:20.630> results<00:25:20.720> back<00:25:21.110> and<00:25:21.170> things 00:25:21.580 --> 00:25:21.590 align:start position:0% and bring the results back and things 00:25:21.590 --> 00:25:23.830 align:start position:0% and bring the results back and things like<00:25:21.710> that<00:25:21.770> it's<00:25:22.250> point<00:25:22.550> five<00:25:22.790> ocean<00:25:23.150> and<00:25:23.330> the 00:25:23.830 --> 00:25:23.840 align:start position:0% like that it's point five ocean and the 00:25:23.840 --> 00:25:25.780 align:start position:0% like that it's point five ocean and the idea<00:25:24.230> is<00:25:24.470> to<00:25:24.800> get<00:25:25.190> that<00:25:25.370> kind<00:25:25.550> of<00:25:25.670> a 00:25:25.780 --> 00:25:25.790 align:start position:0% idea is to get that kind of a 00:25:25.790 --> 00:25:27.940 align:start position:0% idea is to get that kind of a conversation<00:25:25.970> going<00:25:26.390> and<00:25:26.810> that's<00:25:27.380> where<00:25:27.800> we 00:25:27.940 --> 00:25:27.950 align:start position:0% conversation going and that's where we 00:25:27.950 --> 00:25:29.290 align:start position:0% conversation going and that's where we are<00:25:28.070> here<00:25:28.310> in<00:25:28.340> terms<00:25:28.670> of<00:25:28.790> like<00:25:28.940> you<00:25:29.060> know<00:25:29.090> hey 00:25:29.290 --> 00:25:29.300 align:start position:0% are here in terms of like you know hey 00:25:29.300 --> 00:25:31.090 align:start position:0% are here in terms of like you know hey there<00:25:29.930> are<00:25:29.960> these<00:25:30.230> things<00:25:30.500> and<00:25:30.770> that<00:25:30.890> was 00:25:31.090 --> 00:25:31.100 align:start position:0% there are these things and that was 00:25:31.100 --> 00:25:33.010 align:start position:0% there are these things and that was completely<00:25:31.640> API<00:25:31.940> that<00:25:32.150> we<00:25:32.330> have<00:25:32.480> put<00:25:32.900> out 00:25:33.010 --> 00:25:33.020 align:start position:0% completely API that we have put out 00:25:33.020 --> 00:25:35.950 align:start position:0% completely API that we have put out there<00:25:33.050> it's<00:25:34.120> not<00:25:35.120> specific<00:25:35.600> to<00:25:35.630> a<00:25:35.780> particular 00:25:35.950 --> 00:25:35.960 align:start position:0% there it's not specific to a particular 00:25:35.960 --> 00:25:39.430 align:start position:0% there it's not specific to a particular thing<00:25:36.470> you<00:25:37.190> know<00:25:37.660> we<00:25:38.660> want<00:25:38.870> to<00:25:38.960> comprehend 00:25:39.430 --> 00:25:39.440 align:start position:0% thing you know we want to comprehend 00:25:39.440 --> 00:25:41.320 align:start position:0% thing you know we want to comprehend hardware<00:25:40.070> based<00:25:40.220> and<00:25:40.580> software<00:25:40.970> based<00:25:41.150> trust 00:25:41.320 --> 00:25:41.330 align:start position:0% hardware based and software based trust 00:25:41.330 --> 00:25:45.190 align:start position:0% hardware based and software based trust it<00:25:41.510> computes<00:25:41.930> because<00:25:43.090> it's<00:25:44.090> not<00:25:44.270> a<00:25:44.660> one<00:25:44.930> it's 00:25:45.190 --> 00:25:45.200 align:start position:0% it computes because it's not a one it's 00:25:45.200 --> 00:25:48.160 align:start position:0% it computes because it's not a one it's not<00:25:45.380> a<00:25:45.410> silver<00:25:46.070> bullet<00:25:46.190> kind<00:25:47.150> of<00:25:47.240> a<00:25:47.360> thing<00:25:47.540> so 00:25:48.160 --> 00:25:48.170 align:start position:0% not a silver bullet kind of a thing so 00:25:48.170 --> 00:25:51.040 align:start position:0% not a silver bullet kind of a thing so we<00:25:48.620> see<00:25:48.800> a<00:25:48.830> so<00:25:49.490> so<00:25:49.940> that's<00:25:50.090> what<00:25:50.510> we<00:25:50.900> are<00:25:50.930> doing 00:25:51.040 --> 00:25:51.050 align:start position:0% we see a so so that's what we are doing 00:25:51.050 --> 00:25:54.850 align:start position:0% we see a so so that's what we are doing and<00:25:52.210> that<00:25:53.210> would<00:25:53.390> be<00:25:53.510> a<00:25:53.540> great<00:25:53.750> place<00:25:54.050> to<00:25:54.080> start 00:25:54.850 --> 00:25:54.860 align:start position:0% and that would be a great place to start 00:25:54.860 --> 00:25:56.920 align:start position:0% and that would be a great place to start because<00:25:55.520> they<00:25:55.700> got<00:25:55.820> a<00:25:55.880> lot<00:25:56.060> of<00:25:56.120> their<00:25:56.390> stuff 00:25:56.920 --> 00:25:56.930 align:start position:0% because they got a lot of their stuff 00:25:56.930 --> 00:25:59.670 align:start position:0% because they got a lot of their stuff work<00:25:57.230> in<00:25:57.410> there<00:25:57.560> is<00:25:57.710> like<00:25:57.860> right<00:25:58.520> now<00:25:58.790> more 00:25:59.670 --> 00:25:59.680 align:start position:0% work in there is like right now more 00:25:59.680 --> 00:26:03.430 align:start position:0% work in there is like right now more Enterprise<00:26:00.680> II<00:26:00.710> in<00:26:01.220> terms<00:26:01.430> of<00:26:01.720> the<00:26:02.720> flows<00:26:02.930> but 00:26:03.430 --> 00:26:03.440 align:start position:0% Enterprise II in terms of the flows but 00:26:03.440 --> 00:26:05.890 align:start position:0% Enterprise II in terms of the flows but immediately<00:26:04.250> you<00:26:04.700> know<00:26:04.820> we<00:26:05.000> will<00:26:05.360> work<00:26:05.390> on<00:26:05.870> a 00:26:05.890 --> 00:26:05.900 align:start position:0% immediately you know we will work on a 00:26:05.900 --> 00:26:09.790 align:start position:0% immediately you know we will work on a star<00:26:06.200> we<00:26:06.500> start<00:26:07.070> work<00:26:07.280> on<00:26:07.490> how<00:26:08.450> to<00:26:08.590> make<00:26:09.590> that 00:26:09.790 --> 00:26:09.800 align:start position:0% star we start work on how to make that 00:26:09.800 --> 00:26:13.480 align:start position:0% star we start work on how to make that apply<00:26:10.130> API<00:26:10.880> apply<00:26:11.510> for<00:26:11.890> enterprise<00:26:12.890> I<00:26:13.340> get 00:26:13.480 --> 00:26:13.490 align:start position:0% apply API apply for enterprise I get 00:26:13.490 --> 00:26:14.470 align:start position:0% apply API apply for enterprise I get here<00:26:13.640> iam<00:26:13.790> where<00:26:14.000> you<00:26:14.120> have<00:26:14.240> the<00:26:14.360> gas 00:26:14.470 --> 00:26:14.480 align:start position:0% here iam where you have the gas 00:26:14.480 --> 00:26:15.880 align:start position:0% here iam where you have the gas constraints<00:26:15.230> and<00:26:15.350> things<00:26:15.530> like<00:26:15.650> that 00:26:15.880 --> 00:26:15.890 align:start position:0% constraints and things like that 00:26:15.890 --> 00:26:26.020 align:start position:0% constraints and things like that oh<00:26:17.740> yeah<00:26:18.740> so<00:26:19.450> sort<00:26:20.450> of<00:26:20.510> a<00:26:23.380> yeah<00:26:24.550> yeah<00:26:25.550> so<00:26:25.730> sort 00:26:26.020 --> 00:26:26.030 align:start position:0% oh yeah so sort of a yeah yeah so sort 00:26:26.030 --> 00:26:27.700 align:start position:0% oh yeah so sort of a yeah yeah so sort of<00:26:26.090> a<00:26:26.180> follow<00:26:26.420> up<00:26:26.510> to<00:26:26.810> the<00:26:27.140> question<00:26:27.170> that<00:26:27.470> was 00:26:27.700 --> 00:26:27.710 align:start position:0% of a follow up to the question that was 00:26:27.710 --> 00:26:29.240 align:start position:0% of a follow up to the question that was just<00:26:27.740> asked 00:26:29.240 --> 00:26:29.250 align:start position:0% just asked 00:26:29.250 --> 00:26:30.950 align:start position:0% just asked you<00:26:29.340> know<00:26:29.430> about<00:26:29.580> how<00:26:29.760> it's<00:26:30.060> you<00:26:30.750> know<00:26:30.840> we 00:26:30.950 --> 00:26:30.960 align:start position:0% you know about how it's you know we 00:26:30.960 --> 00:26:32.660 align:start position:0% you know about how it's you know we don't<00:26:31.050> really<00:26:31.170> see<00:26:31.500> this<00:26:31.680> on<00:26:31.890> the<00:26:31.920> roadmap<00:26:32.160> you 00:26:32.660 --> 00:26:32.670 align:start position:0% don't really see this on the roadmap you 00:26:32.670 --> 00:26:34.820 align:start position:0% don't really see this on the roadmap you know<00:26:32.880> with<00:26:33.030> aetherium<00:26:33.660> 2.0<00:26:34.170> I<00:26:34.200> think<00:26:34.440> like<00:26:34.620> one 00:26:34.820 --> 00:26:34.830 align:start position:0% know with aetherium 2.0 I think like one 00:26:34.830 --> 00:26:37.100 align:start position:0% know with aetherium 2.0 I think like one thing<00:26:35.010> that<00:26:35.160> would<00:26:35.250> help<00:26:35.310> is<00:26:35.670> if<00:26:36.030> you<00:26:36.990> know 00:26:37.100 --> 00:26:37.110 align:start position:0% thing that would help is if you know 00:26:37.110 --> 00:26:39.290 align:start position:0% thing that would help is if you know these<00:26:37.320> designs<00:26:37.680> were<00:26:38.010> like<00:26:38.220> open<00:26:38.580> that<00:26:39.150> would 00:26:39.290 --> 00:26:39.300 align:start position:0% these designs were like open that would 00:26:39.300 --> 00:26:41.750 align:start position:0% these designs were like open that would help<00:26:39.420> you<00:26:39.930> know<00:26:39.960> people<00:26:40.560> actually<00:26:40.770> like<00:26:41.370> trust 00:26:41.750 --> 00:26:41.760 align:start position:0% help you know people actually like trust 00:26:41.760 --> 00:26:43.520 align:start position:0% help you know people actually like trust what's<00:26:42.030> going<00:26:42.300> on<00:26:42.420> and<00:26:42.630> another<00:26:42.780> thing<00:26:43.080> is<00:26:43.260> is 00:26:43.520 --> 00:26:43.530 align:start position:0% what's going on and another thing is is 00:26:43.530 --> 00:26:45.710 align:start position:0% what's going on and another thing is is I<00:26:43.740> mean<00:26:44.340> have<00:26:44.490> you<00:26:44.520> all<00:26:44.670> approached<00:26:45.030> them<00:26:45.330> even 00:26:45.710 --> 00:26:45.720 align:start position:0% I mean have you all approached them even 00:26:45.720 --> 00:26:49.820 align:start position:0% I mean have you all approached them even you<00:26:46.220> know<00:26:47.220> even<00:26:47.250> the<00:26:48.150> whole<00:26:48.300> idea<00:26:48.630> of<00:26:48.750> you<00:26:49.710> know 00:26:49.820 --> 00:26:49.830 align:start position:0% you know even the whole idea of you know 00:26:49.830 --> 00:26:52.310 align:start position:0% you know even the whole idea of you know feeding<00:26:50.250> you<00:26:50.820> know<00:26:50.940> randomness<00:26:51.630> from<00:26:51.990> you 00:26:52.310 --> 00:26:52.320 align:start position:0% feeding you know randomness from you 00:26:52.320 --> 00:26:54.050 align:start position:0% feeding you know randomness from you know<00:26:52.410> Randa<00:26:52.860> on<00:26:53.010> the<00:26:53.100> beacon<00:26:53.400> chain<00:26:53.670> into<00:26:54.030> a 00:26:54.050 --> 00:26:54.060 align:start position:0% know Randa on the beacon chain into a 00:26:54.060 --> 00:26:55.820 align:start position:0% know Randa on the beacon chain into a PDF<00:26:54.600> you<00:26:54.930> know<00:26:55.020> there's<00:26:55.230> all<00:26:55.410> this<00:26:55.530> research 00:26:55.820 --> 00:26:55.830 align:start position:0% PDF you know there's all this research 00:26:55.830 --> 00:26:58.040 align:start position:0% PDF you know there's all this research and<00:26:56.130> work<00:26:56.340> and<00:26:56.790> we<00:26:56.880> want<00:26:57.030> to<00:26:57.120> create<00:26:57.240> a<00:26:57.420> you 00:26:58.040 --> 00:26:58.050 align:start position:0% and work and we want to create a you 00:26:58.050 --> 00:27:00.940 align:start position:0% and work and we want to create a you know<00:26:58.170> a<00:26:58.200> verifiable<00:26:58.950> delay<00:26:59.490> function<00:26:59.970> ASIC 00:27:00.940 --> 00:27:00.950 align:start position:0% know a verifiable delay function ASIC 00:27:00.950 --> 00:27:05.300 align:start position:0% know a verifiable delay function ASIC could<00:27:01.950> this<00:27:02.100> help<00:27:02.370> yeah<00:27:03.860> why<00:27:04.860> don't<00:27:04.920> we<00:27:05.100> talk 00:27:05.300 --> 00:27:05.310 align:start position:0% could this help yeah why don't we talk 00:27:05.310 --> 00:27:09.830 align:start position:0% could this help yeah why don't we talk about<00:27:05.460> that<00:27:05.730> so<00:27:07.490> you're<00:27:08.490> right<00:27:08.670> on<00:27:08.850> the<00:27:09.030> mark 00:27:09.830 --> 00:27:09.840 align:start position:0% about that so you're right on the mark 00:27:09.840 --> 00:27:12.200 align:start position:0% about that so you're right on the mark right<00:27:10.050> because<00:27:10.410> like<00:27:10.590> you<00:27:10.710> know<00:27:10.830> we<00:27:11.610> have<00:27:11.880> some 00:27:12.200 --> 00:27:12.210 align:start position:0% right because like you know we have some 00:27:12.210 --> 00:27:15.230 align:start position:0% right because like you know we have some really<00:27:12.600> hard<00:27:13.200> earned<00:27:13.730> you<00:27:14.730> know<00:27:14.850> random 00:27:15.230 --> 00:27:15.240 align:start position:0% really hard earned you know random 00:27:15.240 --> 00:27:18.790 align:start position:0% really hard earned you know random generators<00:27:16.080> within<00:27:16.560> within<00:27:17.370> the<00:27:17.550> hardware 00:27:18.790 --> 00:27:18.800 align:start position:0% generators within within the hardware 00:27:18.800 --> 00:27:21.470 align:start position:0% generators within within the hardware that<00:27:19.800> feed<00:27:20.370> of<00:27:20.520> the<00:27:20.640> entropy<00:27:20.970> within<00:27:21.360> the 00:27:21.470 --> 00:27:21.480 align:start position:0% that feed of the entropy within the 00:27:21.480 --> 00:27:25.100 align:start position:0% that feed of the entropy within the system<00:27:21.950> and<00:27:23.060> when<00:27:24.060> I<00:27:24.090> look<00:27:24.300> at<00:27:24.420> Rando<00:27:24.810> and 00:27:25.100 --> 00:27:25.110 align:start position:0% system and when I look at Rando and 00:27:25.110 --> 00:27:26.780 align:start position:0% system and when I look at Rando and think<00:27:25.320> all<00:27:25.710> that<00:27:25.920> in<00:27:26.070> context<00:27:26.400> of<00:27:26.520> beacon 00:27:26.780 --> 00:27:26.790 align:start position:0% think all that in context of beacon 00:27:26.790 --> 00:27:28.610 align:start position:0% think all that in context of beacon chain<00:27:26.970> it<00:27:27.330> becomes<00:27:27.660> very<00:27:27.810> very<00:27:28.110> interesting 00:27:28.610 --> 00:27:28.620 align:start position:0% chain it becomes very very interesting 00:27:28.620 --> 00:27:31.190 align:start position:0% chain it becomes very very interesting so<00:27:29.100> that's<00:27:29.430> where<00:27:29.730> we<00:27:30.270> talked<00:27:30.510> about<00:27:30.660> it<00:27:30.960> like 00:27:31.190 --> 00:27:31.200 align:start position:0% so that's where we talked about it like 00:27:31.200 --> 00:27:33.740 align:start position:0% so that's where we talked about it like you<00:27:31.320> know<00:27:31.700> there's<00:27:32.700> a<00:27:32.850> role<00:27:33.000> to<00:27:33.180> be<00:27:33.270> played<00:27:33.300> and 00:27:33.740 --> 00:27:33.750 align:start position:0% you know there's a role to be played and 00:27:33.750 --> 00:27:36.140 align:start position:0% you know there's a role to be played and that's<00:27:34.650> why<00:27:34.860> we<00:27:35.160> are<00:27:35.190> here<00:27:35.460> is<00:27:35.640> like<00:27:35.940> you<00:27:35.970> know 00:27:36.140 --> 00:27:36.150 align:start position:0% that's why we are here is like you know 00:27:36.150 --> 00:27:37.610 align:start position:0% that's why we are here is like you know let's<00:27:36.360> have<00:27:36.540> that<00:27:36.690> conversation<00:27:36.870> going 00:27:37.610 --> 00:27:37.620 align:start position:0% let's have that conversation going 00:27:37.620 --> 00:27:40.100 align:start position:0% let's have that conversation going what's<00:27:38.160> the<00:27:38.250> right<00:27:38.400> way<00:27:38.580> to<00:27:38.640> you<00:27:39.480> know<00:27:39.570> you're 00:27:40.100 --> 00:27:40.110 align:start position:0% what's the right way to you know you're 00:27:40.110 --> 00:27:43.850 align:start position:0% what's the right way to you know you're approaching<00:27:40.890> just<00:27:41.370> and<00:27:41.550> Drake<00:27:41.730> to<00:27:42.090> ask<00:27:42.860> we 00:27:43.850 --> 00:27:43.860 align:start position:0% approaching just and Drake to ask we 00:27:43.860 --> 00:27:46.640 align:start position:0% approaching just and Drake to ask we have<00:27:44.040> not<00:27:44.280> yet<00:27:44.490> but<00:27:44.760> the<00:27:44.880> idea<00:27:45.210> is<00:27:45.380> first<00:27:46.380> was 00:27:46.640 --> 00:27:46.650 align:start position:0% have not yet but the idea is first was 00:27:46.650 --> 00:27:49.730 align:start position:0% have not yet but the idea is first was to<00:27:46.680> get<00:27:46.980> the<00:27:47.130> API<00:27:47.430> out<00:27:47.960> have<00:27:48.960> something<00:27:49.560> to 00:27:49.730 --> 00:27:49.740 align:start position:0% to get the API out have something to 00:27:49.740 --> 00:27:51.680 align:start position:0% to get the API out have something to shoot<00:27:49.890> against<00:27:50.400> and<00:27:50.580> yeah<00:27:50.730> but<00:27:51.030> but<00:27:51.510> that's 00:27:51.680 --> 00:27:51.690 align:start position:0% shoot against and yeah but but that's 00:27:51.690 --> 00:27:53.480 align:start position:0% shoot against and yeah but but that's idea<00:27:52.110> yeah<00:27:52.410> that<00:27:52.800> means<00:27:53.010> that<00:27:53.130> just<00:27:53.280> be<00:27:53.460> a 00:27:53.480 --> 00:27:53.490 align:start position:0% idea yeah that means that just be a 00:27:53.490 --> 00:27:55.310 align:start position:0% idea yeah that means that just be a really<00:27:53.730> good<00:27:53.970> way<00:27:54.150> to<00:27:54.210> like<00:27:54.660> get<00:27:54.840> an<00:27:54.990> answer 00:27:55.310 --> 00:27:55.320 align:start position:0% really good way to like get an answer 00:27:55.320 --> 00:27:57.380 align:start position:0% really good way to like get an answer really<00:27:55.590> quick<00:27:55.890> about<00:27:56.070> what<00:27:56.430> they<00:27:56.880> you<00:27:57.360> know 00:27:57.380 --> 00:27:57.390 align:start position:0% really quick about what they you know 00:27:57.390 --> 00:27:59.270 align:start position:0% really quick about what they you know what<00:27:57.480> reservations<00:27:58.230> they<00:27:58.590> have<00:27:58.770> so<00:27:59.130> that 00:27:59.270 --> 00:27:59.280 align:start position:0% what reservations they have so that 00:27:59.280 --> 00:28:02.630 align:start position:0% what reservations they have so that could<00:28:00.090> be<00:28:00.120> move<00:28:00.390> forward<00:28:00.750> you<00:28:01.020> know<00:28:01.520> thank<00:28:02.520> you 00:28:02.630 --> 00:28:02.640 align:start position:0% could be move forward you know thank you 00:28:02.640 --> 00:28:04.970 align:start position:0% could be move forward you know thank you yeah<00:28:02.850> and<00:28:03.420> it's<00:28:03.690> it's<00:28:03.990> this<00:28:04.290> is<00:28:04.440> the<00:28:04.470> beginning 00:28:04.970 --> 00:28:04.980 align:start position:0% yeah and it's it's this is the beginning 00:28:04.980 --> 00:28:08.630 align:start position:0% yeah and it's it's this is the beginning of<00:28:05.100> a<00:28:05.310> dialogue<00:28:05.490> right<00:28:05.970> so<00:28:06.590> and<00:28:07.590> and<00:28:08.100> one<00:28:08.610> thing 00:28:08.630 --> 00:28:08.640 align:start position:0% of a dialogue right so and and one thing 00:28:08.640 --> 00:28:11.060 align:start position:0% of a dialogue right so and and one thing that<00:28:08.940> want<00:28:09.840> to<00:28:09.930> point<00:28:10.140> out<00:28:10.350> was<00:28:10.620> just<00:28:10.830> really 00:28:11.060 --> 00:28:11.070 align:start position:0% that want to point out was just really 00:28:11.070 --> 00:28:13.250 align:start position:0% that want to point out was just really important<00:28:11.700> what<00:28:12.270> we're<00:28:12.480> saying<00:28:12.780> here<00:28:12.930> is 00:28:13.250 --> 00:28:13.260 align:start position:0% important what we're saying here is 00:28:13.260 --> 00:28:16.760 align:start position:0% important what we're saying here is we're<00:28:13.740> not<00:28:14.330> replacing<00:28:15.330> any<00:28:15.690> of<00:28:15.900> the<00:28:16.320> current 00:28:16.760 --> 00:28:16.770 align:start position:0% we're not replacing any of the current 00:28:16.770 --> 00:28:19.490 align:start position:0% we're not replacing any of the current security<00:28:17.010> features<00:28:17.870> right<00:28:18.870> we're<00:28:19.080> not<00:28:19.230> saying 00:28:19.490 --> 00:28:19.500 align:start position:0% security features right we're not saying 00:28:19.500 --> 00:28:22.700 align:start position:0% security features right we're not saying replace<00:28:20.190> you<00:28:21.180> know<00:28:21.270> of<00:28:21.630> proof<00:28:22.020> of<00:28:22.140> work<00:28:22.350> with 00:28:22.700 --> 00:28:22.710 align:start position:0% replace you know of proof of work with 00:28:22.710 --> 00:28:27.440 align:start position:0% replace you know of proof of work with proof<00:28:23.400> of<00:28:23.520> elapsed<00:28:24.390> time<00:28:25.040> using<00:28:26.040> until<00:28:26.580> SGX<00:28:27.300> or 00:28:27.440 --> 00:28:27.450 align:start position:0% proof of elapsed time using until SGX or 00:28:27.450 --> 00:28:29.390 align:start position:0% proof of elapsed time using until SGX or any<00:28:27.600> other<00:28:27.780> trusted<00:28:28.470> trusted<00:28:28.740> Enclave<00:28:29.250> but 00:28:29.390 --> 00:28:29.400 align:start position:0% any other trusted trusted Enclave but 00:28:29.400 --> 00:28:30.980 align:start position:0% any other trusted trusted Enclave but we're<00:28:29.610> saying<00:28:29.880> we're<00:28:30.150> adding<00:28:30.600> additional 00:28:30.980 --> 00:28:30.990 align:start position:0% we're saying we're adding additional 00:28:30.990 --> 00:28:35.180 align:start position:0% we're saying we're adding additional security<00:28:31.620> features<00:28:31.980> to<00:28:33.200> the<00:28:34.200> ecosystem<00:28:34.860> stack 00:28:35.180 --> 00:28:35.190 align:start position:0% security features to the ecosystem stack 00:28:35.190 --> 00:28:39.520 align:start position:0% security features to the ecosystem stack that<00:28:36.000> makes<00:28:36.390> the<00:28:37.170> whole<00:28:37.350> thing 00:28:39.520 --> 00:28:39.530 align:start position:0% that makes the whole thing 00:28:39.530 --> 00:28:42.600 align:start position:0% that makes the whole thing more<00:28:39.950> secure<00:28:40.690> allows<00:28:41.690> better 00:28:42.600 --> 00:28:42.610 align:start position:0% more secure allows better 00:28:42.610 --> 00:28:45.010 align:start position:0% more secure allows better decentralization<00:28:43.610> and<00:28:43.910> lowers<00:28:44.450> the<00:28:44.690> barrier 00:28:45.010 --> 00:28:45.020 align:start position:0% decentralization and lowers the barrier 00:28:45.020 --> 00:28:49.180 align:start position:0% decentralization and lowers the barrier to<00:28:45.350> to<00:28:46.160> entry<00:28:46.880> because<00:28:47.510> it<00:28:47.809> is<00:28:48.110> literally<00:28:48.650> the 00:28:49.180 --> 00:28:49.190 align:start position:0% to to entry because it is literally the 00:28:49.190 --> 00:28:51.610 align:start position:0% to to entry because it is literally the big<00:28:49.340> witness<00:28:49.929> right<00:28:50.929> already 00:28:51.610 --> 00:28:51.620 align:start position:0% big witness right already 00:28:51.620 --> 00:28:54.039 align:start position:0% big witness right already right<00:28:51.860> you<00:28:52.100> can<00:28:52.250> you<00:28:52.520> if<00:28:52.760> if<00:28:53.660> you're<00:28:53.900> running 00:28:54.039 --> 00:28:54.049 align:start position:0% right you can you if if you're running 00:28:54.049 --> 00:28:58.030 align:start position:0% right you can you if if you're running an<00:28:54.260> i7<00:28:54.740> +<00:28:55.090> i9<00:28:56.090> you<00:28:56.540> can<00:28:56.720> turn<00:28:56.929> on<00:28:57.169> turn<00:28:57.500> on<00:28:57.559> Intel 00:28:58.030 --> 00:28:58.040 align:start position:0% an i7 + i9 you can turn on turn on Intel 00:28:58.040 --> 00:29:03.640 align:start position:0% an i7 + i9 you can turn on turn on Intel SGX<00:28:58.429> and<00:28:59.210> and<00:28:59.540> and<00:28:59.780> deploy<00:29:00.650> a<00:29:02.110> trusted<00:29:03.110> trusted 00:29:03.640 --> 00:29:03.650 align:start position:0% SGX and and and deploy a trusted trusted 00:29:03.650 --> 00:29:07.419 align:start position:0% SGX and and and deploy a trusted trusted service<00:29:04.010> in<00:29:04.220> in<00:29:04.520> a<00:29:04.610> few<00:29:04.760> minutes<00:29:05.169> so<00:29:06.429> it's 00:29:07.419 --> 00:29:07.429 align:start position:0% service in in a few minutes so it's 00:29:07.429 --> 00:29:12.460 align:start position:0% service in in a few minutes so it's about<00:29:07.700> educating<00:29:09.040> the<00:29:10.040> ecosystem<00:29:10.790> about<00:29:11.470> this 00:29:12.460 --> 00:29:12.470 align:start position:0% about educating the ecosystem about this 00:29:12.470 --> 00:29:15.820 align:start position:0% about educating the ecosystem about this novel<00:29:13.270> idea<00:29:14.270> and<00:29:14.419> it<00:29:14.480> really<00:29:14.750> has<00:29:14.990> only<00:29:15.320> come 00:29:15.820 --> 00:29:15.830 align:start position:0% novel idea and it really has only come 00:29:15.830 --> 00:29:17.380 align:start position:0% novel idea and it really has only come out<00:29:15.890> in<00:29:16.250> the<00:29:16.340> last<00:29:16.490> you<00:29:16.850> know<00:29:16.970> six<00:29:17.299> months 00:29:17.380 --> 00:29:17.390 align:start position:0% out in the last you know six months 00:29:17.390 --> 00:29:21.039 align:start position:0% out in the last you know six months really<00:29:18.580> six<00:29:19.580> to<00:29:19.760> nine<00:29:20.210> months<00:29:20.540> really<00:29:20.750> that 00:29:21.039 --> 00:29:21.049 align:start position:0% really six to nine months really that 00:29:21.049 --> 00:29:23.680 align:start position:0% really six to nine months really that we've<00:29:21.200> been<00:29:21.320> working<00:29:21.679> on<00:29:22.240> on<00:29:23.240> this<00:29:23.570> to 00:29:23.680 --> 00:29:23.690 align:start position:0% we've been working on on this to 00:29:23.690 --> 00:29:25.600 align:start position:0% we've been working on on this to formulate<00:29:24.110> the<00:29:24.500> ideas<00:29:24.860> to<00:29:25.010> tomorrow<00:29:25.340> with 00:29:25.600 --> 00:29:25.610 align:start position:0% formulate the ideas to tomorrow with 00:29:25.610 --> 00:29:28.120 align:start position:0% formulate the ideas to tomorrow with people<00:29:25.910> like<00:29:26.000> Virgil<00:29:26.720> to<00:29:26.900> get<00:29:27.080> feedback<00:29:27.290> so 00:29:28.120 --> 00:29:28.130 align:start position:0% people like Virgil to get feedback so 00:29:28.130 --> 00:29:29.560 align:start position:0% people like Virgil to get feedback so and<00:29:28.370> it's<00:29:28.490> a<00:29:28.610> it's<00:29:28.820> a<00:29:28.910> slow<00:29:29.120> process 00:29:29.560 --> 00:29:29.570 align:start position:0% and it's a it's a slow process 00:29:29.570 --> 00:29:32.230 align:start position:0% and it's a it's a slow process right<00:29:30.380> because<00:29:30.650> Intel<00:29:31.190> came<00:29:31.429> out<00:29:31.580> first<00:29:31.910> and 00:29:32.230 --> 00:29:32.240 align:start position:0% right because Intel came out first and 00:29:32.240 --> 00:29:35.140 align:start position:0% right because Intel came out first and it<00:29:32.390> was<00:29:32.540> Intel<00:29:33.350> he'll<00:29:33.559> help<00:29:34.370> the<00:29:34.429> keys<00:29:34.730> and 00:29:35.140 --> 00:29:35.150 align:start position:0% it was Intel he'll help the keys and 00:29:35.150 --> 00:29:37.090 align:start position:0% it was Intel he'll help the keys and that's<00:29:35.299> what's<00:29:35.660> stuck<00:29:36.110> in<00:29:36.290> people<00:29:36.559> people's 00:29:37.090 --> 00:29:37.100 align:start position:0% that's what's stuck in people people's 00:29:37.100 --> 00:29:38.799 align:start position:0% that's what's stuck in people people's heads<00:29:37.370> and<00:29:37.760> you<00:29:38.150> know<00:29:38.240> you're<00:29:38.450> saying<00:29:38.600> now 00:29:38.799 --> 00:29:38.809 align:start position:0% heads and you know you're saying now 00:29:38.809 --> 00:29:40.360 align:start position:0% heads and you know you're saying now until<00:29:39.110> there's<00:29:39.320> no<00:29:39.410> all<00:29:39.500> the<00:29:39.650> keys<00:29:39.830> anymore<00:29:40.250> or 00:29:40.360 --> 00:29:40.370 align:start position:0% until there's no all the keys anymore or 00:29:40.370 --> 00:29:42.010 align:start position:0% until there's no all the keys anymore or AMD<00:29:40.669> or<00:29:41.179> arm 00:29:42.010 --> 00:29:42.020 align:start position:0% AMD or arm 00:29:42.020 --> 00:29:51.690 align:start position:0% AMD or arm it<00:29:42.470> really<00:29:42.830> doesn't<00:29:43.040> doesn't<00:29:44.000> matter 00:29:51.690 --> 00:29:51.700 align:start position:0% 00:29:51.700 --> 00:29:53.760 align:start position:0% you