WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:37.340 align:start position:0% [Applause] 00:00:37.340 --> 00:00:37.350 align:start position:0% 00:00:37.350 --> 00:00:45.350 align:start position:0% [Music] 00:00:45.350 --> 00:00:45.360 align:start position:0% 00:00:45.360 --> 00:00:52.250 align:start position:0% [Music] 00:00:52.250 --> 00:00:52.260 align:start position:0% 00:00:52.260 --> 00:00:57.020 align:start position:0% so<00:00:52.980> again<00:00:53.340> again<00:00:53.640> is<00:00:53.940> like<00:00:55.550> Sunday<00:00:56.550> from<00:00:56.700> inter 00:00:57.020 --> 00:00:57.030 align:start position:0% so again again is like Sunday from inter 00:00:57.030 --> 00:01:01.570 align:start position:0% so again again is like Sunday from inter so<00:00:57.870> as<00:00:58.170> you<00:00:58.320> can<00:00:58.440> see<00:00:58.500> it's<00:00:59.370> quite<00:00:59.640> a<00:00:59.900> cross 00:01:01.570 --> 00:01:01.580 align:start position:0% so as you can see it's quite a cross 00:01:01.580 --> 00:01:04.789 align:start position:0% so as you can see it's quite a cross company<00:01:02.580> effort<00:01:02.940> so<00:01:03.570> so<00:01:04.019> today<00:01:04.290> you<00:01:04.619> know 00:01:04.789 --> 00:01:04.799 align:start position:0% company effort so so today you know 00:01:04.799 --> 00:01:07.940 align:start position:0% company effort so so today you know we're<00:01:05.220> going<00:01:05.369> to<00:01:05.430> talk<00:01:05.580> about<00:01:06.650> object<00:01:07.650> Pacific 00:01:07.940 --> 00:01:07.950 align:start position:0% we're going to talk about object Pacific 00:01:07.950 --> 00:01:12.109 align:start position:0% we're going to talk about object Pacific compute<00:01:08.340> this<00:01:08.579> work<00:01:08.939> started<00:01:09.450> off 00:01:12.109 --> 00:01:12.119 align:start position:0% 00:01:12.119 --> 00:01:21.710 align:start position:0% and<00:01:13.640> enterprise<00:01:18.170> expediency<00:01:19.430> so<00:01:20.570> what<00:01:21.570> I<00:01:21.600> will 00:01:21.710 --> 00:01:21.720 align:start position:0% and enterprise expediency so what I will 00:01:21.720 --> 00:01:23.450 align:start position:0% and enterprise expediency so what I will do<00:01:21.960> quickly<00:01:22.229> is<00:01:22.439> likely<00:01:22.829> to<00:01:23.009> give<00:01:23.189> you<00:01:23.220> some 00:01:23.450 --> 00:01:23.460 align:start position:0% do quickly is likely to give you some 00:01:23.460 --> 00:01:27.469 align:start position:0% do quickly is likely to give you some little<00:01:23.820> bit<00:01:23.970> of<00:01:24.060> history<00:01:24.479> and<00:01:25.009> then<00:01:26.119> drop<00:01:27.119> into 00:01:27.469 --> 00:01:27.479 align:start position:0% little bit of history and then drop into 00:01:27.479 --> 00:01:29.960 align:start position:0% little bit of history and then drop into you<00:01:27.930> know<00:01:28.049> the<00:01:28.259> immediate<00:01:28.920> details<00:01:29.189> of<00:01:29.549> it<00:01:29.759> so 00:01:29.960 --> 00:01:29.970 align:start position:0% you know the immediate details of it so 00:01:29.970 --> 00:01:35.270 align:start position:0% you know the immediate details of it so we<00:01:30.810> were<00:01:32.090> and<00:01:33.090> we<00:01:33.720> were<00:01:33.840> gonna<00:01:34.409> show<00:01:34.740> actually 00:01:35.270 --> 00:01:35.280 align:start position:0% we were and we were gonna show actually 00:01:35.280 --> 00:01:39.830 align:start position:0% we were and we were gonna show actually walking<00:01:35.579> to<00:01:35.939> some<00:01:37.610> hands-on<00:01:38.840> demonstrations 00:01:39.830 --> 00:01:39.840 align:start position:0% walking to some hands-on demonstrations 00:01:39.840 --> 00:01:42.770 align:start position:0% walking to some hands-on demonstrations but<00:01:40.850> internet<00:01:41.850> access<00:01:42.210> here<00:01:42.390> is<00:01:42.600> very 00:01:42.770 --> 00:01:42.780 align:start position:0% but internet access here is very 00:01:42.780 --> 00:01:45.199 align:start position:0% but internet access here is very interesting<00:01:42.899> so<00:01:43.679> we're<00:01:44.250> gonna<00:01:44.459> spot<00:01:45.030> you 00:01:45.199 --> 00:01:45.209 align:start position:0% interesting so we're gonna spot you 00:01:45.209 --> 00:01:50.300 align:start position:0% interesting so we're gonna spot you fluenta<00:01:45.600> if<00:01:46.470> you<00:01:47.270> have<00:01:48.270> my<00:01:48.450> readers<00:01:48.810> can<00:01:49.310> go 00:01:50.300 --> 00:01:50.310 align:start position:0% fluenta if you have my readers can go 00:01:50.310 --> 00:01:53.350 align:start position:0% fluenta if you have my readers can go and<00:01:50.429> you<00:01:51.179> know<00:01:51.240> try<00:01:51.600> it<00:01:51.630> out<00:01:51.869> at<00:01:52.319> your 00:01:53.350 --> 00:01:53.360 align:start position:0% and you know try it out at your 00:01:53.360 --> 00:01:58.219 align:start position:0% and you know try it out at your convenience<00:01:55.159> so<00:01:56.360> so<00:01:57.360> there<00:01:57.840> are<00:01:57.959> going<00:01:58.080> to<00:01:58.170> be 00:01:58.219 --> 00:01:58.229 align:start position:0% convenience so so there are going to be 00:01:58.229 --> 00:02:00.919 align:start position:0% convenience so so there are going to be two<00:01:58.439> of<00:01:58.590> these<00:01:58.740> boxes<00:01:59.179> that<00:02:00.179> canteen<00:02:00.750> filled 00:02:00.919 --> 00:02:00.929 align:start position:0% two of these boxes that canteen filled 00:02:00.929 --> 00:02:03.199 align:start position:0% two of these boxes that canteen filled introduced<00:02:01.349> and<00:02:01.590> then<00:02:01.740> hopefully<00:02:02.640> we'll<00:02:03.030> have 00:02:03.199 --> 00:02:03.209 align:start position:0% introduced and then hopefully we'll have 00:02:03.209 --> 00:02:09.979 align:start position:0% introduced and then hopefully we'll have time<00:02:03.420> to<00:02:03.630> have<00:02:04.020> some<00:02:06.679> study<00:02:08.690> how<00:02:09.690> they<00:02:09.869> are 00:02:09.979 --> 00:02:09.989 align:start position:0% time to have some study how they are 00:02:09.989 --> 00:02:14.000 align:start position:0% time to have some study how they are using<00:02:10.530> trusted<00:02:10.860> computer<00:02:11.280> so<00:02:12.739> quick<00:02:13.739> on 00:02:14.000 --> 00:02:14.010 align:start position:0% using trusted computer so quick on 00:02:14.010 --> 00:02:18.740 align:start position:0% using trusted computer so quick on enterprise<00:02:14.430> aetherium<00:02:15.620> it's<00:02:17.269> the<00:02:18.269> focus<00:02:18.600> is 00:02:18.740 --> 00:02:18.750 align:start position:0% enterprise aetherium it's the focus is 00:02:18.750 --> 00:02:20.870 align:start position:0% enterprise aetherium it's the focus is how<00:02:19.500> to<00:02:19.560> apply<00:02:19.859> it<00:02:20.250> here<00:02:20.310> iam<00:02:20.609> in<00:02:20.760> the 00:02:20.870 --> 00:02:20.880 align:start position:0% how to apply it here iam in the 00:02:20.880 --> 00:02:25.550 align:start position:0% how to apply it here iam in the enterprise<00:02:21.209> world<00:02:21.769> and<00:02:23.359> the<00:02:24.359> main<00:02:24.560> challenges 00:02:25.550 --> 00:02:25.560 align:start position:0% enterprise world and the main challenges 00:02:25.560 --> 00:02:28.640 align:start position:0% enterprise world and the main challenges when<00:02:25.739> it<00:02:25.769> comes<00:02:25.890> to<00:02:26.600> enterprise<00:02:27.630> we<00:02:28.350> call<00:02:28.530> them 00:02:28.640 --> 00:02:28.650 align:start position:0% when it comes to enterprise we call them 00:02:28.650 --> 00:02:31.960 align:start position:0% when it comes to enterprise we call them 3ds<00:02:29.130> publishing<00:02:30.090> privacy<00:02:30.660> and<00:02:30.840> performance 00:02:31.960 --> 00:02:31.970 align:start position:0% 3ds publishing privacy and performance 00:02:31.970 --> 00:02:36.229 align:start position:0% 3ds publishing privacy and performance so<00:02:33.350> we<00:02:34.350> looked<00:02:34.560> at<00:02:34.709> you<00:02:35.310> know<00:02:35.370> prior 00:02:36.229 --> 00:02:36.239 align:start position:0% so we looked at you know prior 00:02:36.239 --> 00:02:40.039 align:start position:0% so we looked at you know prior performance<00:02:36.510> and<00:02:36.959> privacy<00:02:37.410> are<00:02:39.049> important 00:02:40.039 --> 00:02:40.049 align:start position:0% performance and privacy are important 00:02:40.049 --> 00:02:44.270 align:start position:0% performance and privacy are important months<00:02:40.290> and 00:02:44.270 --> 00:02:44.280 align:start position:0% 00:02:44.280 --> 00:02:47.309 align:start position:0% compute<00:02:45.280> as<00:02:45.430> an<00:02:45.580> option<00:02:46.000> for<00:02:46.750> solving<00:02:47.170> those 00:02:47.309 --> 00:02:47.319 align:start position:0% compute as an option for solving those 00:02:47.319 --> 00:02:50.190 align:start position:0% compute as an option for solving those kinds<00:02:47.650> of<00:02:47.709> things<00:02:47.920> so<00:02:48.519> we<00:02:49.209> have<00:02:49.390> made<00:02:49.540> more 00:02:50.190 --> 00:02:50.200 align:start position:0% kinds of things so we have made more 00:02:50.200 --> 00:02:53.640 align:start position:0% kinds of things so we have made more progress<00:02:50.260> on<00:02:50.860> that<00:02:50.920> one<00:02:52.019> we<00:02:53.019> introduced<00:02:53.379> it 00:02:53.640 --> 00:02:53.650 align:start position:0% progress on that one we introduced it 00:02:53.650 --> 00:02:57.000 align:start position:0% progress on that one we introduced it last<00:02:53.860> year<00:02:54.569> point<00:02:55.569> by<00:02:55.780> spectator<00:02:56.290> Pentagon 00:02:57.000 --> 00:02:57.010 align:start position:0% last year point by spectator Pentagon 00:02:57.010 --> 00:02:57.420 align:start position:0% last year point by spectator Pentagon fault 00:02:57.420 --> 00:02:57.430 align:start position:0% fault 00:02:57.430 --> 00:03:00.630 align:start position:0% fault and<00:02:57.580> now<00:02:58.510> we<00:02:58.750> have<00:02:59.170> a<00:02:59.200> 1<00:02:59.560> dot<00:02:59.739> respect<00:03:00.160> out 00:03:00.630 --> 00:03:00.640 align:start position:0% and now we have a 1 dot respect out 00:03:00.640 --> 00:03:06.300 align:start position:0% and now we have a 1 dot respect out there<00:03:01.000> and<00:03:04.530> level<00:03:05.530> for<00:03:05.680> people<00:03:05.950> to<00:03:06.069> play<00:03:06.250> this 00:03:06.300 --> 00:03:06.310 align:start position:0% there and level for people to play this 00:03:06.310 --> 00:03:15.080 align:start position:0% there and level for people to play this and<00:03:06.730> we'll<00:03:06.970> walk<00:03:07.120> you<00:03:07.180> through<00:03:07.480> some<00:03:07.599> of<00:03:07.720> that 00:03:15.080 --> 00:03:15.090 align:start position:0% 00:03:15.090 --> 00:03:46.759 align:start position:0% yeah<00:03:16.120> and<00:03:16.530> as<00:03:17.530> I<00:03:17.680> said<00:03:19.260> some<00:03:20.260> of<00:03:20.290> the 00:03:46.759 --> 00:03:46.769 align:start position:0% 00:03:46.769 --> 00:03:51.120 align:start position:0% businesses<00:03:48.959> and<00:03:49.959> the<00:03:50.019> things<00:03:50.500> the<00:03:50.650> crying<00:03:50.950> of 00:03:51.120 --> 00:03:51.130 align:start position:0% businesses and the things the crying of 00:03:51.130 --> 00:03:54.360 align:start position:0% businesses and the things the crying of the<00:03:51.280> spec<00:03:51.870> has<00:03:52.870> been<00:03:53.349> we<00:03:53.500> talk<00:03:53.650> about<00:03:53.799> mystical 00:03:54.360 --> 00:03:54.370 align:start position:0% the spec has been we talk about mystical 00:03:54.370 --> 00:03:57.930 align:start position:0% the spec has been we talk about mystical flute<00:03:54.489> a<00:03:54.700> lot<00:03:55.090> of<00:03:55.239> in<00:03:56.230> it<00:03:56.349> but<00:03:57.010> what<00:03:57.430> we<00:03:57.549> have<00:03:57.760> in 00:03:57.930 --> 00:03:57.940 align:start position:0% flute a lot of in it but what we have in 00:03:57.940 --> 00:04:02.599 align:start position:0% flute a lot of in it but what we have in there<00:03:58.120> is<00:03:58.720> a<00:03:59.680> supporting<00:04:00.340> of<00:04:00.579> other<00:04:01.510> forms<00:04:02.440> of 00:04:02.599 --> 00:04:02.609 align:start position:0% there is a supporting of other forms of 00:04:02.609 --> 00:04:06.240 align:start position:0% there is a supporting of other forms of computation<00:04:03.609> like<00:04:04.260> Ezekiel's<00:04:05.260> multi-party 00:04:06.240 --> 00:04:06.250 align:start position:0% computation like Ezekiel's multi-party 00:04:06.250 --> 00:04:09.000 align:start position:0% computation like Ezekiel's multi-party computation<00:04:06.370> and<00:04:06.819> things<00:04:07.030> like<00:04:07.180> that<00:04:07.500> a<00:04:08.500> lot 00:04:09.000 --> 00:04:09.010 align:start position:0% computation and things like that a lot 00:04:09.010 --> 00:04:15.659 align:start position:0% computation and things like that a lot of<00:04:09.040> that<00:04:09.250> is<00:04:09.430> in<00:04:09.549> there<00:04:09.730> so<00:04:13.319> with<00:04:14.319> that<00:04:14.669> you 00:04:15.659 --> 00:04:15.669 align:start position:0% of that is in there so with that you 00:04:15.669 --> 00:04:17.740 align:start position:0% of that is in there so with that you know<00:04:15.790> I'll<00:04:15.970> hand<00:04:16.359> off<00:04:16.539> to 00:04:17.740 --> 00:04:17.750 align:start position:0% know I'll hand off to 00:04:17.750 --> 00:04:20.319 align:start position:0% know I'll hand off to [Music] 00:04:20.319 --> 00:04:20.329 align:start position:0% [Music] 00:04:20.329 --> 00:04:24.399 align:start position:0% [Music] to<00:04:20.690> me<00:04:20.870> the<00:04:21.859> best<00:04:22.550> part<00:04:23.110> yeah 00:04:24.399 --> 00:04:24.409 align:start position:0% to me the best part yeah 00:04:24.409 --> 00:04:29.640 align:start position:0% to me the best part yeah hello<00:04:24.979> everyone<00:04:25.340> I<00:04:26.440> would<00:04:27.440> like<00:04:27.500> to<00:04:28.240> say<00:04:29.240> first 00:04:29.640 --> 00:04:29.650 align:start position:0% hello everyone I would like to say first 00:04:29.650 --> 00:04:33.610 align:start position:0% hello everyone I would like to say first thank<00:04:30.650> you<00:04:30.830> to<00:04:30.949> all<00:04:31.280> the<00:04:31.729> collaborators<00:04:32.620> it 00:04:33.610 --> 00:04:33.620 align:start position:0% thank you to all the collaborators it 00:04:33.620 --> 00:04:37.570 align:start position:0% thank you to all the collaborators it was<00:04:33.919> truly<00:04:34.639> an<00:04:35.389> amazing<00:04:35.840> journey<00:04:36.310> it<00:04:37.310> is<00:04:37.370> the 00:04:37.570 --> 00:04:37.580 align:start position:0% was truly an amazing journey it is the 00:04:37.580 --> 00:04:39.969 align:start position:0% was truly an amazing journey it is the first<00:04:37.849> time<00:04:38.090> that<00:04:38.449> the<00:04:38.840> EA<00:04:39.020> has<00:04:39.500> produced 00:04:39.969 --> 00:04:39.979 align:start position:0% first time that the EA has produced 00:04:39.979 --> 00:04:44.100 align:start position:0% first time that the EA has produced shippable<00:04:40.430> code<00:04:40.639> and<00:04:41.440> it<00:04:42.440> is<00:04:42.740> the<00:04:43.370> largest 00:04:44.100 --> 00:04:44.110 align:start position:0% shippable code and it is the largest 00:04:44.110 --> 00:04:47.170 align:start position:0% shippable code and it is the largest enterprise<00:04:45.110> collaboration<00:04:45.940> in<00:04:46.940> the 00:04:47.170 --> 00:04:47.180 align:start position:0% enterprise collaboration in the 00:04:47.180 --> 00:04:50.439 align:start position:0% enterprise collaboration in the blockchain<00:04:47.389> space<00:04:47.990> period<00:04:49.240> and<00:04:50.240> there<00:04:50.389> are 00:04:50.439 --> 00:04:50.449 align:start position:0% blockchain space period and there are 00:04:50.449 --> 00:04:52.059 align:start position:0% blockchain space period and there are five<00:04:50.720> companies<00:04:51.409> that<00:04:51.590> have<00:04:51.710> worked<00:04:51.949> together 00:04:52.059 --> 00:04:52.069 align:start position:0% five companies that have worked together 00:04:52.069 --> 00:04:58.839 align:start position:0% five companies that have worked together to<00:04:52.580> produce<00:04:53.680> this<00:04:54.680> a<00:04:55.009> just<00:04:55.729> reward<00:04:56.509> token<00:04:57.849> this 00:04:58.839 --> 00:04:58.849 align:start position:0% to produce this a just reward token this 00:04:58.849 --> 00:05:06.420 align:start position:0% to produce this a just reward token this is<00:04:59.030> the<00:04:59.509> goal<00:04:59.719> of<00:05:00.110> this<00:05:01.449> of<00:05:02.560> this<00:05:04.750> token 00:05:06.420 --> 00:05:06.430 align:start position:0% is the goal of this of this token 00:05:06.430 --> 00:05:09.010 align:start position:0% is the goal of this of this token students<00:05:07.430> and<00:05:07.550> device<00:05:07.759> participation<00:05:08.509> of<00:05:08.629> GME 00:05:09.010 --> 00:05:09.020 align:start position:0% students and device participation of GME 00:05:09.020 --> 00:05:11.999 align:start position:0% students and device participation of GME member<00:05:09.319> organizations<00:05:10.190> and<00:05:10.699> their<00:05:10.940> employees 00:05:11.999 --> 00:05:12.009 align:start position:0% member organizations and their employees 00:05:12.009 --> 00:05:16.719 align:start position:0% member organizations and their employees why<00:05:13.009> is<00:05:13.069> that<00:05:13.990> important<00:05:14.990> because<00:05:15.919> is<00:05:16.310> very 00:05:16.719 --> 00:05:16.729 align:start position:0% why is that important because is very 00:05:16.729 --> 00:05:20.559 align:start position:0% why is that important because is very hard<00:05:17.319> to<00:05:18.319> get<00:05:18.469> people<00:05:18.530> to<00:05:19.219> contribute<00:05:20.150> it's 00:05:20.559 --> 00:05:20.569 align:start position:0% hard to get people to contribute it's 00:05:20.569 --> 00:05:24.730 align:start position:0% hard to get people to contribute it's always<00:05:20.900> the<00:05:21.050> same<00:05:21.259> usual<00:05:22.069> suspects<00:05:22.580> and<00:05:23.740> the 00:05:24.730 --> 00:05:24.740 align:start position:0% always the same usual suspects and the 00:05:24.740 --> 00:05:26.680 align:start position:0% always the same usual suspects and the goal<00:05:24.949> is<00:05:24.979> to<00:05:25.520> apply<00:05:25.729> some<00:05:26.090> of<00:05:26.150> the<00:05:26.270> learnings 00:05:26.680 --> 00:05:26.690 align:start position:0% goal is to apply some of the learnings 00:05:26.690 --> 00:05:28.320 align:start position:0% goal is to apply some of the learnings from 00:05:28.320 --> 00:05:28.330 align:start position:0% from 00:05:28.330 --> 00:05:31.529 align:start position:0% from you<00:05:28.389> know<00:05:28.479> the<00:05:28.720> open<00:05:29.110> ecosystem<00:05:29.800> space<00:05:30.539> around 00:05:31.529 --> 00:05:31.539 align:start position:0% you know the open ecosystem space around 00:05:31.539 --> 00:05:34.409 align:start position:0% you know the open ecosystem space around the<00:05:31.900> set<00:05:32.110> of<00:05:32.259> models<00:05:32.650> to<00:05:33.129> see<00:05:33.610> whether<00:05:33.849> they 00:05:34.409 --> 00:05:34.419 align:start position:0% the set of models to see whether they 00:05:34.419 --> 00:05:36.240 align:start position:0% the set of models to see whether they can<00:05:34.479> be<00:05:34.720> leveraged<00:05:35.080> in<00:05:35.319> the<00:05:35.500> enterprise<00:05:35.860> so 00:05:36.240 --> 00:05:36.250 align:start position:0% can be leveraged in the enterprise so 00:05:36.250 --> 00:05:40.469 align:start position:0% can be leveraged in the enterprise so there<00:05:36.430> is<00:05:36.520> experimentation<00:05:38.129> with<00:05:39.479> total 00:05:40.469 --> 00:05:40.479 align:start position:0% there is experimentation with total 00:05:40.479 --> 00:05:43.320 align:start position:0% there is experimentation with total principles<00:05:40.960> and<00:05:41.139> design<00:05:41.669> templates<00:05:42.669> we're 00:05:43.320 --> 00:05:43.330 align:start position:0% principles and design templates we're 00:05:43.330 --> 00:05:46.950 align:start position:0% principles and design templates we're eating<00:05:43.719> our<00:05:44.620> own<00:05:44.860> dog<00:05:44.919> food<00:05:45.159> here<00:05:45.639> we<00:05:46.599> want<00:05:46.840> to 00:05:46.950 --> 00:05:46.960 align:start position:0% eating our own dog food here we want to 00:05:46.960 --> 00:05:49.290 align:start position:0% eating our own dog food here we want to create<00:05:47.169> synergies<00:05:47.710> with<00:05:47.740> other<00:05:48.129> groups<00:05:48.849> so 00:05:49.290 --> 00:05:49.300 align:start position:0% create synergies with other groups so 00:05:49.300 --> 00:05:51.629 align:start position:0% create synergies with other groups so the<00:05:49.389> Testament<00:05:49.870> group<00:05:50.080> the<00:05:50.530> toking<00:05:50.889> taxonomy 00:05:51.629 --> 00:05:51.639 align:start position:0% the Testament group the toking taxonomy 00:05:51.639 --> 00:05:54.300 align:start position:0% the Testament group the toking taxonomy initiative<00:05:52.419> that<00:05:52.659> Marley<00:05:52.960> is<00:05:53.020> heading<00:05:53.349> and 00:05:54.300 --> 00:05:54.310 align:start position:0% initiative that Marley is heading and 00:05:54.310 --> 00:05:56.490 align:start position:0% initiative that Marley is heading and the<00:05:54.430> new<00:05:54.520> technical<00:05:54.969> token<00:05:55.330> working<00:05:55.659> group<00:05:55.810> as 00:05:56.490 --> 00:05:56.500 align:start position:0% the new technical token working group as 00:05:56.500 --> 00:06:00.300 align:start position:0% the new technical token working group as well<00:05:56.800> as<00:05:57.659> aetherium<00:05:58.659> specs<00:05:58.960> so<00:05:59.620> the<00:05:59.770> ERC's 00:06:00.300 --> 00:06:00.310 align:start position:0% well as aetherium specs so the ERC's 00:06:00.310 --> 00:06:03.990 align:start position:0% well as aetherium specs so the ERC's mike<00:06:01.180> will<00:06:01.360> talk<00:06:01.539> about<00:06:01.690> that<00:06:01.960> and<00:06:02.229> then<00:06:03.000> web 00:06:03.990 --> 00:06:04.000 align:start position:0% mike will talk about that and then web 00:06:04.000 --> 00:06:07.050 align:start position:0% mike will talk about that and then web standards<00:06:04.740> w3c<00:06:05.740> we're<00:06:05.979> actually<00:06:06.159> using<00:06:06.610> the 00:06:07.050 --> 00:06:07.060 align:start position:0% standards w3c we're actually using the 00:06:07.060 --> 00:06:10.409 align:start position:0% standards w3c we're actually using the three<00:06:07.509> 3c<00:06:08.409> standards<00:06:08.800> for<00:06:09.009> the<00:06:09.159> IES<00:06:09.520> and<00:06:09.879> fair 00:06:10.409 --> 00:06:10.419 align:start position:0% three 3c standards for the IES and fair 00:06:10.419 --> 00:06:13.740 align:start position:0% three 3c standards for the IES and fair table<00:06:11.460> credentials<00:06:12.460> Mike<00:06:13.120> walls<00:06:13.419> will<00:06:13.599> talk 00:06:13.740 --> 00:06:13.750 align:start position:0% table credentials Mike walls will talk 00:06:13.750 --> 00:06:16.619 align:start position:0% table credentials Mike walls will talk about<00:06:13.870> that<00:06:14.430> and<00:06:15.430> this<00:06:15.849> is<00:06:16.090> really<00:06:16.270> the<00:06:16.449> use 00:06:16.619 --> 00:06:16.629 align:start position:0% about that and this is really the use 00:06:16.629 --> 00:06:19.529 align:start position:0% about that and this is really the use case<00:06:16.870> for<00:06:16.900> the<00:06:17.560> trusted<00:06:17.919> computing<00:06:17.949> work<00:06:18.940> spec 00:06:19.529 --> 00:06:19.539 align:start position:0% case for the trusted computing work spec 00:06:19.539 --> 00:06:23.519 align:start position:0% case for the trusted computing work spec and<00:06:19.779> the<00:06:20.259> EA<00:06:20.940> compute<00:06:21.940> test<00:06:22.120> methods<00:06:22.690> so<00:06:23.500> that 00:06:23.519 --> 00:06:23.529 align:start position:0% and the EA compute test methods so that 00:06:23.529 --> 00:06:26.399 align:start position:0% and the EA compute test methods so that that's<00:06:23.979> that's<00:06:24.370> really<00:06:24.729> really<00:06:25.419> important 00:06:26.399 --> 00:06:26.409 align:start position:0% that's that's really really important 00:06:26.409 --> 00:06:29.519 align:start position:0% that's that's really really important and<00:06:26.500> we're<00:06:26.830> creating<00:06:27.069> a<00:06:27.430> first<00:06:27.729> simple<00:06:28.659> use 00:06:29.519 --> 00:06:29.529 align:start position:0% and we're creating a first simple use 00:06:29.529 --> 00:06:32.760 align:start position:0% and we're creating a first simple use case<00:06:29.650> that<00:06:30.009> is<00:06:30.099> actually<00:06:30.669> usable<00:06:31.319> and<00:06:32.319> that<00:06:32.620> is 00:06:32.760 --> 00:06:32.770 align:start position:0% case that is actually usable and that is 00:06:32.770 --> 00:06:34.170 align:start position:0% case that is actually usable and that is also<00:06:33.490> a<00:06:33.639> first 00:06:34.170 --> 00:06:34.180 align:start position:0% also a first 00:06:34.180 --> 00:06:37.080 align:start position:0% also a first so<00:06:34.529> enterprises<00:06:35.529> can<00:06:35.889> actually<00:06:36.250> start<00:06:36.550> using 00:06:37.080 --> 00:06:37.090 align:start position:0% so enterprises can actually start using 00:06:37.090 --> 00:06:40.290 align:start position:0% so enterprises can actually start using tokens<00:06:37.509> from<00:06:38.169> in<00:06:39.159> their<00:06:39.460> in<00:06:39.819> their<00:06:39.969> day<00:06:40.120> to<00:06:40.180> day 00:06:40.290 --> 00:06:40.300 align:start position:0% tokens from in their in their day to day 00:06:40.300 --> 00:06:42.469 align:start position:0% tokens from in their in their day to day operation<00:06:40.810> because<00:06:41.050> this<00:06:41.259> model<00:06:41.529> is<00:06:41.740> easily 00:06:42.469 --> 00:06:42.479 align:start position:0% operation because this model is easily 00:06:42.479 --> 00:06:45.829 align:start position:0% operation because this model is easily transferrable<00:06:43.479> into<00:06:43.900> one<00:06:44.770> enterprise<00:06:45.250> or 00:06:45.829 --> 00:06:45.839 align:start position:0% transferrable into one enterprise or 00:06:45.839 --> 00:06:48.920 align:start position:0% transferrable into one enterprise or between<00:06:46.839> multiple<00:06:47.669> enterprises<00:06:48.669> and 00:06:48.920 --> 00:06:48.930 align:start position:0% between multiple enterprises and 00:06:48.930 --> 00:06:52.100 align:start position:0% between multiple enterprises and other<00:06:49.220> consortium<00:06:50.220> and<00:06:50.460> without<00:06:51.389> when<00:06:52.080> I 00:06:52.100 --> 00:06:52.110 align:start position:0% other consortium and without when I 00:06:52.110 --> 00:06:53.480 align:start position:0% other consortium and without when I handed<00:06:52.410> over<00:06:52.500> its<00:06:52.740> from<00:06:52.860> Arlington<00:06:53.310> talk<00:06:53.460> a 00:06:53.480 --> 00:06:53.490 align:start position:0% handed over its from Arlington talk a 00:06:53.490 --> 00:06:54.920 align:start position:0% handed over its from Arlington talk a little<00:06:53.789> bit<00:06:53.940> more<00:06:54.090> about<00:06:54.240> the<00:06:54.360> details<00:06:54.720> of<00:06:54.840> the 00:06:54.920 --> 00:06:54.930 align:start position:0% little bit more about the details of the 00:06:54.930 --> 00:06:59.300 align:start position:0% little bit more about the details of the total<00:06:55.229> model<00:06:56.570> alright<00:06:57.570> so<00:06:57.979> what<00:06:58.979> we<00:06:59.070> wanted<00:06:59.250> to 00:06:59.300 --> 00:06:59.310 align:start position:0% total model alright so what we wanted to 00:06:59.310 --> 00:07:01.100 align:start position:0% total model alright so what we wanted to do<00:06:59.460> is<00:06:59.639> to<00:06:59.850> figure<00:07:00.150> out<00:07:00.270> the<00:07:00.389> business<00:07:00.570> process 00:07:01.100 --> 00:07:01.110 align:start position:0% do is to figure out the business process 00:07:01.110 --> 00:07:03.020 align:start position:0% do is to figure out the business process of<00:07:01.320> solving<00:07:01.860> the<00:07:01.949> difficult<00:07:02.340> problem<00:07:02.639> how<00:07:02.970> do 00:07:03.020 --> 00:07:03.030 align:start position:0% of solving the difficult problem how do 00:07:03.030 --> 00:07:06.760 align:start position:0% of solving the difficult problem how do you<00:07:03.240> get<00:07:04.160> consortiums<00:07:05.160> comprised<00:07:05.940> of<00:07:06.150> mobile 00:07:06.760 --> 00:07:06.770 align:start position:0% you get consortiums comprised of mobile 00:07:06.770 --> 00:07:08.719 align:start position:0% you get consortiums comprised of mobile corporations<00:07:07.770> some<00:07:08.039> of<00:07:08.160> which<00:07:08.280> might<00:07:08.460> compete 00:07:08.719 --> 00:07:08.729 align:start position:0% corporations some of which might compete 00:07:08.729 --> 00:07:10.969 align:start position:0% corporations some of which might compete with<00:07:08.880> each<00:07:08.970> other<00:07:09.090> to<00:07:09.600> actually<00:07:10.259> lean<00:07:10.470> in<00:07:10.680> and 00:07:10.969 --> 00:07:10.979 align:start position:0% with each other to actually lean in and 00:07:10.979 --> 00:07:13.340 align:start position:0% with each other to actually lean in and do<00:07:11.250> the<00:07:11.400> work<00:07:11.430> to<00:07:11.789> contribute<00:07:12.150> to<00:07:12.660> the<00:07:12.930> benefit 00:07:13.340 --> 00:07:13.350 align:start position:0% do the work to contribute to the benefit 00:07:13.350 --> 00:07:15.680 align:start position:0% do the work to contribute to the benefit of<00:07:13.410> all<00:07:13.620> which<00:07:14.460> is<00:07:14.639> pretty<00:07:15.509> difficult 00:07:15.680 --> 00:07:15.690 align:start position:0% of all which is pretty difficult 00:07:15.690 --> 00:07:16.969 align:start position:0% of all which is pretty difficult actually<00:07:16.259> Paula 00:07:16.969 --> 00:07:16.979 align:start position:0% actually Paula 00:07:16.979 --> 00:07:19.420 align:start position:0% actually Paula so<00:07:17.580> with<00:07:17.729> one<00:07:17.850> of<00:07:17.940> the<00:07:18.030> create<00:07:18.509> an<00:07:18.660> incentive 00:07:19.420 --> 00:07:19.430 align:start position:0% so with one of the create an incentive 00:07:19.430 --> 00:07:21.920 align:start position:0% so with one of the create an incentive like<00:07:20.430> development<00:07:20.880> behavioral<00:07:21.300> modification 00:07:21.920 --> 00:07:21.930 align:start position:0% like development behavioral modification 00:07:21.930 --> 00:07:24.260 align:start position:0% like development behavioral modification protocols<00:07:22.380> to<00:07:23.190> incent<00:07:23.580> good<00:07:23.820> behavior<00:07:24.240> and 00:07:24.260 --> 00:07:24.270 align:start position:0% protocols to incent good behavior and 00:07:24.270 --> 00:07:28.520 align:start position:0% protocols to incent good behavior and punish<00:07:25.080> bad<00:07:25.289> behavior<00:07:26.479> but<00:07:27.479> you<00:07:27.720> also<00:07:28.199> have<00:07:28.500> to 00:07:28.520 --> 00:07:28.530 align:start position:0% punish bad behavior but you also have to 00:07:28.530 --> 00:07:30.740 align:start position:0% punish bad behavior but you also have to because<00:07:29.340> we're<00:07:29.490> trying<00:07:29.729> to<00:07:30.030> scope<00:07:30.360> out<00:07:30.509> work 00:07:30.740 --> 00:07:30.750 align:start position:0% because we're trying to scope out work 00:07:30.750 --> 00:07:33.680 align:start position:0% because we're trying to scope out work that<00:07:30.780> needs<00:07:31.169> to<00:07:31.320> occur<00:07:31.550> do<00:07:32.550> you<00:07:32.639> need<00:07:32.789> to<00:07:33.000> do 00:07:33.680 --> 00:07:33.690 align:start position:0% that needs to occur do you need to do 00:07:33.690 --> 00:07:35.870 align:start position:0% that needs to occur do you need to do this<00:07:33.810> in<00:07:34.020> a<00:07:34.080> way<00:07:34.229> that<00:07:34.259> you<00:07:35.009> say<00:07:35.580> it's<00:07:35.759> the 00:07:35.870 --> 00:07:35.880 align:start position:0% this in a way that you say it's the 00:07:35.880 --> 00:07:38.270 align:start position:0% this in a way that you say it's the potential<00:07:36.539> to<00:07:36.810> earn<00:07:36.930> these<00:07:37.320> rewards<00:07:38.039> so<00:07:38.160> we'll 00:07:38.270 --> 00:07:38.280 align:start position:0% potential to earn these rewards so we'll 00:07:38.280 --> 00:07:40.610 align:start position:0% potential to earn these rewards so we'll talk<00:07:38.430> about<00:07:38.520> though<00:07:38.699> the<00:07:39.270> tokens<00:07:39.780> and<00:07:40.050> then 00:07:40.610 --> 00:07:40.620 align:start position:0% talk about though the tokens and then 00:07:40.620 --> 00:07:42.730 align:start position:0% talk about though the tokens and then we'll<00:07:40.800> talk<00:07:40.979> about<00:07:41.039> how<00:07:41.759> we<00:07:41.820> ought<00:07:42.030> to 00:07:42.730 --> 00:07:42.740 align:start position:0% we'll talk about how we ought to 00:07:42.740 --> 00:07:45.610 align:start position:0% we'll talk about how we ought to quickly<00:07:43.069> first<00:07:43.699> thought<00:07:43.880> we<00:07:44.060> we<00:07:45.050> we<00:07:45.319> do<00:07:45.470> these 00:07:45.610 --> 00:07:45.620 align:start position:0% quickly first thought we we we do these 00:07:45.620 --> 00:07:49.390 align:start position:0% quickly first thought we we we do these we<00:07:45.860> simply<00:07:46.220> create<00:07:46.400> a<00:07:46.729> grant<00:07:47.630> in<00:07:48.380> this<00:07:48.620> if<00:07:49.130> the 00:07:49.390 --> 00:07:49.400 align:start position:0% we simply create a grant in this if the 00:07:49.400 --> 00:07:51.820 align:start position:0% we simply create a grant in this if the potential<00:07:49.940> for<00:07:50.270> an<00:07:50.680> organization<00:07:51.680> that's 00:07:51.820 --> 00:07:51.830 align:start position:0% potential for an organization that's 00:07:51.830 --> 00:07:54.010 align:start position:0% potential for an organization that's given<00:07:52.099> to<00:07:52.160> the<00:07:52.310> organization<00:07:52.880> to<00:07:53.419> receive<00:07:53.660> X 00:07:54.010 --> 00:07:54.020 align:start position:0% given to the organization to receive X 00:07:54.020 --> 00:07:56.980 align:start position:0% given to the organization to receive X number<00:07:54.380> of<00:07:54.470> war<00:07:54.860> tokens<00:07:55.340> if<00:07:56.030> they<00:07:56.300> achieve<00:07:56.660> the 00:07:56.980 --> 00:07:56.990 align:start position:0% number of war tokens if they achieve the 00:07:56.990 --> 00:08:01.390 align:start position:0% number of war tokens if they achieve the goal<00:07:57.259> laid<00:07:57.620> out<00:07:57.800> in<00:07:57.919> the<00:07:58.009> grant<00:07:58.389> and<00:08:00.400> and 00:08:01.390 --> 00:08:01.400 align:start position:0% goal laid out in the grant and and 00:08:01.400 --> 00:08:03.219 align:start position:0% goal laid out in the grant and and that's<00:08:02.090> the<00:08:02.210> potential<00:08:02.599> and<00:08:02.720> they<00:08:02.780> can<00:08:02.960> have 00:08:03.219 --> 00:08:03.229 align:start position:0% that's the potential and they can have 00:08:03.229 --> 00:08:05.529 align:start position:0% that's the potential and they can have individual<00:08:03.830> contributors<00:08:04.400> so<00:08:05.120> the<00:08:05.210> actual 00:08:05.529 --> 00:08:05.539 align:start position:0% individual contributors so the actual 00:08:05.539 --> 00:08:06.939 align:start position:0% individual contributors so the actual people<00:08:05.720> that<00:08:05.810> are<00:08:05.990> doing<00:08:06.110> the<00:08:06.380> work<00:08:06.410> we<00:08:06.770> want 00:08:06.939 --> 00:08:06.949 align:start position:0% people that are doing the work we want 00:08:06.949 --> 00:08:09.279 align:start position:0% people that are doing the work we want taxi<00:08:07.340> I<00:08:07.580> get<00:08:08.270> the<00:08:08.389> credit<00:08:08.599> for<00:08:08.780> doing<00:08:09.139> that 00:08:09.279 --> 00:08:09.289 align:start position:0% taxi I get the credit for doing that 00:08:09.289 --> 00:08:11.680 align:start position:0% taxi I get the credit for doing that work<00:08:09.550> be<00:08:10.550> able<00:08:10.699> to<00:08:10.759> use<00:08:10.940> it<00:08:11.090> so<00:08:11.210> we<00:08:11.240> can<00:08:11.479> enlist 00:08:11.680 --> 00:08:11.690 align:start position:0% work be able to use it so we can enlist 00:08:11.690 --> 00:08:13.839 align:start position:0% work be able to use it so we can enlist who<00:08:11.990> those<00:08:12.169> people<00:08:12.199> are<00:08:12.620> and<00:08:12.889> they<00:08:13.310> could<00:08:13.490> you 00:08:13.839 --> 00:08:13.849 align:start position:0% who those people are and they could you 00:08:13.849 --> 00:08:15.939 align:start position:0% who those people are and they could you know<00:08:13.910> get<00:08:14.630> a<00:08:14.690> percentage<00:08:15.199> of<00:08:15.440> that<00:08:15.620> total 00:08:15.939 --> 00:08:15.949 align:start position:0% know get a percentage of that total 00:08:15.949 --> 00:08:19.270 align:start position:0% know get a percentage of that total award<00:08:16.250> if<00:08:16.400> it's<00:08:16.580> cheap<00:08:17.889> there's<00:08:18.889> also<00:08:19.130> a 00:08:19.270 --> 00:08:19.280 align:start position:0% award if it's cheap there's also a 00:08:19.280 --> 00:08:20.200 align:start position:0% award if it's cheap there's also a punishment 00:08:20.200 --> 00:08:20.210 align:start position:0% punishment 00:08:20.210 --> 00:08:23.620 align:start position:0% punishment well<00:08:20.599> the<00:08:21.110> punishment<00:08:21.590> may<00:08:22.039> equal<00:08:22.580> the<00:08:22.789> sum<00:08:23.419> or 00:08:23.620 --> 00:08:23.630 align:start position:0% well the punishment may equal the sum or 00:08:23.630 --> 00:08:27.450 align:start position:0% well the punishment may equal the sum or negative<00:08:24.020> value<00:08:24.380> of<00:08:24.409> their<00:08:24.830> total<00:08:25.099> award<00:08:25.930> and 00:08:27.450 --> 00:08:27.460 align:start position:0% negative value of their total award and 00:08:27.460 --> 00:08:30.010 align:start position:0% negative value of their total award and and<00:08:28.460> you<00:08:28.729> can<00:08:28.909> set<00:08:29.120> that<00:08:29.270> in<00:08:29.449> the<00:08:29.599> grant<00:08:29.840> as 00:08:30.010 --> 00:08:30.020 align:start position:0% and you can set that in the grant as 00:08:30.020 --> 00:08:32.500 align:start position:0% and you can set that in the grant as well<00:08:30.050> and<00:08:30.650> then<00:08:31.340> there's<00:08:32.149> also<00:08:32.270> something 00:08:32.500 --> 00:08:32.510 align:start position:0% well and then there's also something 00:08:32.510 --> 00:08:34.389 align:start position:0% well and then there's also something called<00:08:32.630> reputation<00:08:33.469> token<00:08:34.099> so<00:08:34.190> we'll<00:08:34.310> talk 00:08:34.389 --> 00:08:34.399 align:start position:0% called reputation token so we'll talk 00:08:34.399 --> 00:08:35.949 align:start position:0% called reputation token so we'll talk about<00:08:34.490> that<00:08:34.669> as<00:08:34.760> well<00:08:34.969> those<00:08:35.390> are<00:08:35.539> granted 00:08:35.949 --> 00:08:35.959 align:start position:0% about that as well those are granted 00:08:35.959 --> 00:08:39.130 align:start position:0% about that as well those are granted this<00:08:36.140> or<00:08:36.380> one<00:08:37.190> for<00:08:37.430> one<00:08:37.610> with<00:08:37.880> the<00:08:38.120> home<00:08:38.750> or<00:08:38.930> to 00:08:39.130 --> 00:08:39.140 align:start position:0% this or one for one with the home or to 00:08:39.140 --> 00:08:39.490 align:start position:0% this or one for one with the home or to me 00:08:39.490 --> 00:08:39.500 align:start position:0% me 00:08:39.500 --> 00:08:40.899 align:start position:0% me essentially<00:08:39.950> what<00:08:40.099> the<00:08:40.250> World<00:08:40.430> War<00:08:40.550> took<00:08:40.760> it 00:08:40.899 --> 00:08:40.909 align:start position:0% essentially what the World War took it 00:08:40.909 --> 00:08:45.360 align:start position:0% essentially what the World War took it does<00:08:41.120> it's<00:08:41.450> a<00:08:42.669> it's<00:08:43.669> a<00:08:43.909> token<00:08:44.390> that 00:08:45.360 --> 00:08:45.370 align:start position:0% does it's a it's a token that 00:08:45.370 --> 00:08:47.680 align:start position:0% does it's a it's a token that organizations<00:08:46.370> can<00:08:46.520> when<00:08:47.029> you<00:08:47.180> are<00:08:47.390> granted 00:08:47.680 --> 00:08:47.690 align:start position:0% organizations can when you are granted 00:08:47.690 --> 00:08:51.639 align:start position:0% organizations can when you are granted them<00:08:48.079> let's<00:08:48.320> say<00:08:48.470> you're<00:08:48.740> the<00:08:49.690> the<00:08:50.690> reward 00:08:51.639 --> 00:08:51.649 align:start position:0% them let's say you're the the reward 00:08:51.649 --> 00:08:54.699 align:start position:0% them let's say you're the the reward grant<00:08:52.279> vests<00:08:52.910> and<00:08:53.149> you're<00:08:54.050> awarded<00:08:54.470> the 00:08:54.699 --> 00:08:54.709 align:start position:0% grant vests and you're awarded the 00:08:54.709 --> 00:08:56.519 align:start position:0% grant vests and you're awarded the organization<00:08:55.190> for<00:08:55.399> one<00:08:55.490> of<00:08:55.610> those<00:08:55.730> tokens 00:08:56.519 --> 00:08:56.529 align:start position:0% organization for one of those tokens 00:08:56.529 --> 00:08:59.740 align:start position:0% organization for one of those tokens they<00:08:57.529> can<00:08:57.770> take<00:08:58.370> those<00:08:58.550> tokens<00:08:59.060> and<00:08:59.420> repeat 00:08:59.740 --> 00:08:59.750 align:start position:0% they can take those tokens and repeat 00:08:59.750 --> 00:09:03.430 align:start position:0% they can take those tokens and repeat them<00:09:00.020> for<00:09:00.399> value<00:09:01.870> we'll<00:09:02.870> talk<00:09:03.020> about<00:09:03.140> what 00:09:03.430 --> 00:09:03.440 align:start position:0% them for value we'll talk about what 00:09:03.440 --> 00:09:04.840 align:start position:0% them for value we'll talk about what we're<00:09:03.560> actually<00:09:03.709> providing<00:09:04.640> here<00:09:04.760> in<00:09:04.820> a 00:09:04.840 --> 00:09:04.850 align:start position:0% we're actually providing here in a 00:09:04.850 --> 00:09:07.000 align:start position:0% we're actually providing here in a minute<00:09:05.000> I<00:09:05.360> go<00:09:06.079> to<00:09:06.140> the<00:09:06.260> next<00:09:06.380> slide<00:09:06.529> it's<00:09:06.800> fine 00:09:07.000 --> 00:09:07.010 align:start position:0% minute I go to the next slide it's fine 00:09:07.010 --> 00:09:10.019 align:start position:0% minute I go to the next slide it's fine so<00:09:07.640> you<00:09:07.670> can<00:09:08.000> go<00:09:08.510> out<00:09:08.660> and<00:09:08.690> shop<00:09:09.500> at<00:09:09.709> the<00:09:09.890> e 00:09:10.019 --> 00:09:10.029 align:start position:0% so you can go out and shop at the e 00:09:10.029 --> 00:09:12.340 align:start position:0% so you can go out and shop at the e scratch<00:09:11.029> store<00:09:11.360> and<00:09:11.810> get<00:09:11.959> some<00:09:12.170> really 00:09:12.340 --> 00:09:12.350 align:start position:0% scratch store and get some really 00:09:12.350 --> 00:09:16.440 align:start position:0% scratch store and get some really interesting<00:09:13.029> materials<00:09:14.029> some<00:09:14.750> t-shirts 00:09:16.440 --> 00:09:16.450 align:start position:0% interesting materials some t-shirts 00:09:16.450 --> 00:09:18.420 align:start position:0% interesting materials some t-shirts dinner<00:09:17.450> with<00:09:17.630> Ron 00:09:18.420 --> 00:09:18.430 align:start position:0% dinner with Ron 00:09:18.430 --> 00:09:20.620 align:start position:0% dinner with Ron that<00:09:19.430> doesn't<00:09:19.640> mean<00:09:19.700> Ron<00:09:20.060> is<00:09:20.180> going<00:09:20.329> to<00:09:20.390> pay<00:09:20.600> to 00:09:20.620 --> 00:09:20.630 align:start position:0% that doesn't mean Ron is going to pay to 00:09:20.630 --> 00:09:22.240 align:start position:0% that doesn't mean Ron is going to pay to dinner 00:09:22.240 --> 00:09:22.250 align:start position:0% dinner 00:09:22.250 --> 00:09:25.560 align:start position:0% dinner everyone<00:09:22.910> come<00:09:23.270> with<00:09:23.450> you 00:09:25.560 --> 00:09:25.570 align:start position:0% everyone come with you 00:09:25.570 --> 00:09:29.320 align:start position:0% everyone come with you and<00:09:26.570> then<00:09:27.350> but<00:09:28.250> and<00:09:28.430> then<00:09:28.610> sunglasses<00:09:29.240> but 00:09:29.320 --> 00:09:29.330 align:start position:0% and then but and then sunglasses but 00:09:29.330 --> 00:09:31.360 align:start position:0% and then but and then sunglasses but this<00:09:29.450> is<00:09:29.600> this<00:09:29.720> was<00:09:29.930> more<00:09:30.170> for<00:09:30.410> just<00:09:30.560> the<00:09:31.190> show 00:09:31.360 --> 00:09:31.370 align:start position:0% this is this was more for just the show 00:09:31.370 --> 00:09:33.430 align:start position:0% this is this was more for just the show what<00:09:31.580> you<00:09:31.640> could<00:09:31.790> do<00:09:31.910> really<00:09:32.420> one<00:09:33.290> of<00:09:33.320> they 00:09:33.430 --> 00:09:33.440 align:start position:0% what you could do really one of they 00:09:33.440 --> 00:09:34.630 align:start position:0% what you could do really one of they threw<00:09:33.620> one<00:09:33.650> of<00:09:33.770> the<00:09:33.860> put<00:09:34.070> it<00:09:34.130> in<00:09:34.190> the<00:09:34.250> grant<00:09:34.490> as 00:09:34.630 --> 00:09:34.640 align:start position:0% threw one of the put it in the grant as 00:09:34.640 --> 00:09:37.390 align:start position:0% threw one of the put it in the grant as follows<00:09:35.000> to<00:09:35.150> have<00:09:35.330> because<00:09:36.020> it's<00:09:36.400> consortiums 00:09:37.390 --> 00:09:37.400 align:start position:0% follows to have because it's consortiums 00:09:37.400 --> 00:09:39.400 align:start position:0% follows to have because it's consortiums we<00:09:37.640> made<00:09:37.850> up<00:09:37.970> organizations<00:09:38.870> we<00:09:39.020> might<00:09:39.200> have 00:09:39.400 --> 00:09:39.410 align:start position:0% we made up organizations we might have 00:09:39.410 --> 00:09:42.430 align:start position:0% we made up organizations we might have systems<00:09:40.220> like<00:09:40.250> Microsoft<00:09:40.490> contribute<00:09:41.440> to 00:09:42.430 --> 00:09:42.440 align:start position:0% systems like Microsoft contribute to 00:09:42.440 --> 00:09:44.730 align:start position:0% systems like Microsoft contribute to have<00:09:42.560> a<00:09:42.590> bounty<00:09:42.860> in<00:09:43.280> there<00:09:44.000> and<00:09:44.150> say<00:09:44.270> hey 00:09:44.730 --> 00:09:44.740 align:start position:0% have a bounty in there and say hey 00:09:44.740 --> 00:09:47.770 align:start position:0% have a bounty in there and say hey offices<00:09:45.740> or<00:09:46.070> some<00:09:46.340> X<00:09:46.670> boxes<00:09:47.090> so<00:09:47.750> that 00:09:47.770 --> 00:09:47.780 align:start position:0% offices or some X boxes so that 00:09:47.780 --> 00:09:49.780 align:start position:0% offices or some X boxes so that contributors<00:09:48.590> actually<00:09:49.340> meet<00:09:49.490> the<00:09:49.610> goal 00:09:49.780 --> 00:09:49.790 align:start position:0% contributors actually meet the goal 00:09:49.790 --> 00:09:51.780 align:start position:0% contributors actually meet the goal they'll<00:09:50.030> actually<00:09:50.210> get<00:09:50.480> some<00:09:50.630> of<00:09:50.660> they<00:09:50.870> want 00:09:51.780 --> 00:09:51.790 align:start position:0% they'll actually get some of they want 00:09:51.790 --> 00:09:55.000 align:start position:0% they'll actually get some of they want at<00:09:52.790> the<00:09:52.910> end<00:09:52.940> of<00:09:53.240> that<00:09:53.360> call<00:09:53.630> so<00:09:53.990> really<00:09:54.860> we 00:09:55.000 --> 00:09:55.010 align:start position:0% at the end of that call so really we 00:09:55.010 --> 00:09:56.590 align:start position:0% at the end of that call so really we want<00:09:55.190> to<00:09:55.250> leave<00:09:55.430> the<00:09:55.580> model<00:09:55.880> open<00:09:56.180> to<00:09:56.300> say<00:09:56.450> that 00:09:56.590 --> 00:09:56.600 align:start position:0% want to leave the model open to say that 00:09:56.600 --> 00:09:57.820 align:start position:0% want to leave the model open to say that you've<00:09:56.690> ever<00:09:56.840> worn<00:09:56.990> so<00:09:57.320> interesting<00:09:57.650> things 00:09:57.820 --> 00:09:57.830 align:start position:0% you've ever worn so interesting things 00:09:57.830 --> 00:10:00.610 align:start position:0% you've ever worn so interesting things about<00:09:57.920> this<00:09:58.160> is<00:09:58.720> you<00:09:59.720> get<00:09:59.870> a<00:09:59.930> reward<00:10:00.290> to<00:10:00.380> open 00:10:00.610 --> 00:10:00.620 align:start position:0% about this is you get a reward to open 00:10:00.620 --> 00:10:02.470 align:start position:0% about this is you get a reward to open the<00:10:00.740> reputation<00:10:01.340> flows<00:10:01.670> to<00:10:01.880> the<00:10:01.910> individual 00:10:02.470 --> 00:10:02.480 align:start position:0% the reputation flows to the individual 00:10:02.480 --> 00:10:05.230 align:start position:0% the reputation flows to the individual so<00:10:02.960> the<00:10:03.080> individuals<00:10:03.620> will<00:10:04.280> get<00:10:04.460> a<00:10:04.700> percentage 00:10:05.230 --> 00:10:05.240 align:start position:0% so the individuals will get a percentage 00:10:05.240 --> 00:10:06.450 align:start position:0% so the individuals will get a percentage there's<00:10:05.600> 100<00:10:05.960> tokens 00:10:06.450 --> 00:10:06.460 align:start position:0% there's 100 tokens 00:10:06.460 --> 00:10:09.760 align:start position:0% there's 100 tokens three<00:10:07.460> or<00:10:07.640> two<00:10:07.850> participants<00:10:08.690> you<00:10:09.260> can<00:10:09.290> divide 00:10:09.760 --> 00:10:09.770 align:start position:0% three or two participants you can divide 00:10:09.770 --> 00:10:12.370 align:start position:0% three or two participants you can divide up<00:10:09.980> those<00:10:10.160> reputation<00:10:11.030> points<00:10:11.570> that<00:10:11.900> it<00:10:12.290> was 00:10:12.370 --> 00:10:12.380 align:start position:0% up those reputation points that it was 00:10:12.380 --> 00:10:14.980 align:start position:0% up those reputation points that it was equal<00:10:12.710> effort<00:10:13.580> by<00:10:13.730> both<00:10:13.760> participants<00:10:14.660> and 00:10:14.980 --> 00:10:14.990 align:start position:0% equal effort by both participants and 00:10:14.990 --> 00:10:17.530 align:start position:0% equal effort by both participants and they<00:10:15.050> will<00:10:15.170> get<00:10:15.260> 15<00:10:15.680> reputation<00:10:16.280> points<00:10:16.540> the 00:10:17.530 --> 00:10:17.540 align:start position:0% they will get 15 reputation points the 00:10:17.540 --> 00:10:19.210 align:start position:0% they will get 15 reputation points the cute<00:10:17.750> little<00:10:17.900> all<00:10:18.350> up<00:10:18.500> to<00:10:18.620> the<00:10:18.740> individual 00:10:19.210 --> 00:10:19.220 align:start position:0% cute little all up to the individual 00:10:19.220 --> 00:10:23.050 align:start position:0% cute little all up to the individual penalty<00:10:20.150> tokens<00:10:21.040> essentially<00:10:22.040> our<00:10:22.700> negative 00:10:23.050 --> 00:10:23.060 align:start position:0% penalty tokens essentially our negative 00:10:23.060 --> 00:10:25.720 align:start position:0% penalty tokens essentially our negative value<00:10:23.420> they<00:10:24.380> all<00:10:24.710> have<00:10:25.040> to<00:10:25.190> be<00:10:25.250> redeemed 00:10:25.720 --> 00:10:25.730 align:start position:0% value they all have to be redeemed 00:10:25.730 --> 00:10:27.910 align:start position:0% value they all have to be redeemed before<00:10:26.540> you<00:10:26.870> can<00:10:27.020> redeem<00:10:27.290> your<00:10:27.500> reward<00:10:27.860> - 00:10:27.910 --> 00:10:27.920 align:start position:0% before you can redeem your reward - 00:10:27.920 --> 00:10:30.070 align:start position:0% before you can redeem your reward - means<00:10:28.250> they'll<00:10:28.839> decrease<00:10:29.839> your<00:10:30.020> overall 00:10:30.070 --> 00:10:30.080 align:start position:0% means they'll decrease your overall 00:10:30.080 --> 00:10:32.920 align:start position:0% means they'll decrease your overall balance<00:10:30.620> for<00:10:31.610> dictating<00:10:32.510> whether<00:10:32.660> or<00:10:32.720> not<00:10:32.780> you 00:10:32.920 --> 00:10:32.930 align:start position:0% balance for dictating whether or not you 00:10:32.930 --> 00:10:34.690 align:start position:0% balance for dictating whether or not you have<00:10:33.110> to<00:10:33.230> settle<00:10:33.440> for<00:10:33.530> the<00:10:33.830> autograph 00:10:34.690 --> 00:10:34.700 align:start position:0% have to settle for the autograph 00:10:34.700 --> 00:10:38.530 align:start position:0% have to settle for the autograph sunglasses<00:10:35.510> that<00:10:35.660> I<00:10:35.780> provided<00:10:36.640> or<00:10:37.640> you<00:10:38.270> know 00:10:38.530 --> 00:10:38.540 align:start position:0% sunglasses that I provided or you know 00:10:38.540 --> 00:10:41.260 align:start position:0% sunglasses that I provided or you know even<00:10:39.040> slowing<00:10:40.040> down<00:10:40.310> with<00:10:40.490> the<00:10:40.550> teacher<00:10:40.940> so 00:10:41.260 --> 00:10:41.270 align:start position:0% even slowing down with the teacher so 00:10:41.270 --> 00:10:43.860 align:start position:0% even slowing down with the teacher so this<00:10:42.110> is<00:10:42.230> how<00:10:42.320> these<00:10:42.440> dentists<00:10:42.830> will 00:10:43.860 --> 00:10:43.870 align:start position:0% this is how these dentists will 00:10:43.870 --> 00:10:45.990 align:start position:0% this is how these dentists will and<00:10:44.110> create<00:10:44.440> this<00:10:44.530> business<00:10:44.770> model<00:10:45.070> for<00:10:45.820> doing 00:10:45.990 --> 00:10:46.000 align:start position:0% and create this business model for doing 00:10:46.000 --> 00:10:50.130 align:start position:0% and create this business model for doing that<00:10:46.150> so<00:10:46.470> move<00:10:47.470> on<00:10:47.650> yeah<00:10:48.070> so<00:10:48.610> I<00:10:48.640> think<00:10:49.140> what 00:10:50.130 --> 00:10:50.140 align:start position:0% that so move on yeah so I think what 00:10:50.140 --> 00:10:52.920 align:start position:0% that so move on yeah so I think what we'd<00:10:50.350> like<00:10:51.160> the<00:10:51.640> real<00:10:51.820> meat<00:10:52.090> and<00:10:52.390> does<00:10:52.750> not 00:10:52.920 --> 00:10:52.930 align:start position:0% we'd like the real meat and does not 00:10:52.930 --> 00:10:56.580 align:start position:0% we'd like the real meat and does not like<00:10:53.110> you<00:10:53.230> know<00:10:53.670> how<00:10:54.670> this<00:10:54.940> pasta<00:10:55.510> token<00:10:55.900> was 00:10:56.580 --> 00:10:56.590 align:start position:0% like you know how this pasta token was 00:10:56.590 --> 00:10:58.830 align:start position:0% like you know how this pasta token was implemented<00:10:57.280> and<00:10:57.490> by<00:10:57.640> the<00:10:57.700> does<00:10:58.480> it<00:10:58.630> come<00:10:58.810> to 00:10:58.830 --> 00:10:58.840 align:start position:0% implemented and by the does it come to 00:10:58.840 --> 00:11:04.190 align:start position:0% implemented and by the does it come to the<00:10:58.990> X<00:10:59.140> we<00:10:59.320> effects<00:10:59.800> and<00:11:00.010> everything<00:11:00.280> else 00:11:04.190 --> 00:11:04.200 align:start position:0% 00:11:04.200 --> 00:11:06.770 align:start position:0% [Music] 00:11:06.770 --> 00:11:06.780 align:start position:0% [Music] 00:11:06.780 --> 00:11:12.720 align:start position:0% [Music] after<00:11:07.780> everyone<00:11:09.750> sees<00:11:10.750> early<00:11:11.260> last<00:11:11.560> year<00:11:11.730> so 00:11:12.720 --> 00:11:12.730 align:start position:0% after everyone sees early last year so 00:11:12.730 --> 00:11:14.970 align:start position:0% after everyone sees early last year so Isaac<00:11:13.000> has<00:11:13.450> been<00:11:13.690> significantly<00:11:14.620> working 00:11:14.970 --> 00:11:14.980 align:start position:0% Isaac has been significantly working 00:11:14.980 --> 00:11:18.870 align:start position:0% Isaac has been significantly working with<00:11:15.130> Intel<00:11:15.780> consensus<00:11:16.780> and<00:11:17.200> the<00:11:17.920> idea<00:11:18.430> member 00:11:18.870 --> 00:11:18.880 align:start position:0% with Intel consensus and the idea member 00:11:18.880 --> 00:11:21.870 align:start position:0% with Intel consensus and the idea member is<00:11:19.090> to<00:11:19.450> acknowledge<00:11:20.370> computing<00:11:21.370> framework 00:11:21.870 --> 00:11:21.880 align:start position:0% is to acknowledge computing framework 00:11:21.880 --> 00:11:25.290 align:start position:0% is to acknowledge computing framework and<00:11:22.570> move<00:11:23.020> for<00:11:23.350> the<00:11:23.980> related<00:11:24.430> specifications 00:11:25.290 --> 00:11:25.300 align:start position:0% and move for the related specifications 00:11:25.300 --> 00:11:28.610 align:start position:0% and move for the related specifications and<00:11:25.900> trustee<00:11:26.500> use<00:11:26.680> case<00:11:26.950> just<00:11:27.340> like<00:11:27.460> ETA<00:11:27.970> token 00:11:28.610 --> 00:11:28.620 align:start position:0% and trustee use case just like ETA token 00:11:28.620 --> 00:11:32.130 align:start position:0% and trustee use case just like ETA token so<00:11:29.620> firstly<00:11:30.070> before<00:11:30.730> talk<00:11:31.090> about<00:11:31.420> technical 00:11:32.130 --> 00:11:32.140 align:start position:0% so firstly before talk about technical 00:11:32.140 --> 00:11:34.800 align:start position:0% so firstly before talk about technical details<00:11:32.530> I<00:11:32.800> would<00:11:33.580> like<00:11:33.850> to<00:11:34.000> tell<00:11:34.180> ten<00:11:34.480> minutes 00:11:34.800 --> 00:11:34.810 align:start position:0% details I would like to tell ten minutes 00:11:34.810 --> 00:11:37.230 align:start position:0% details I would like to tell ten minutes to<00:11:35.200> talk<00:11:35.440> about<00:11:35.500> a<00:11:35.740> phenomenal<00:11:36.640> question<00:11:36.760> for 00:11:37.230 --> 00:11:37.240 align:start position:0% to talk about a phenomenal question for 00:11:37.240 --> 00:11:41.010 align:start position:0% to talk about a phenomenal question for me<00:11:37.330> why<00:11:38.290> we<00:11:38.560> need<00:11:38.830> accurate<00:11:39.160> of<00:11:39.760> the<00:11:40.030> county 00:11:41.010 --> 00:11:41.020 align:start position:0% me why we need accurate of the county 00:11:41.020 --> 00:11:44.370 align:start position:0% me why we need accurate of the county exclusion<00:11:41.770> to<00:11:42.610> the<00:11:42.700> object<00:11:43.150> trust<00:11:43.750> excusing 00:11:44.370 --> 00:11:44.380 align:start position:0% exclusion to the object trust excusing 00:11:44.380 --> 00:11:48.540 align:start position:0% exclusion to the object trust excusing the<00:11:44.500> environment<00:11:45.930> so<00:11:46.930> now<00:11:47.110> there<00:11:47.320> is<00:11:47.350> a<00:11:47.710> lot<00:11:48.070> on 00:11:48.540 --> 00:11:48.550 align:start position:0% the environment so now there is a lot on 00:11:48.550 --> 00:11:50.940 align:start position:0% the environment so now there is a lot on chair<00:11:49.270> applications<00:11:50.230> that<00:11:50.440> are<00:11:50.650> smoothly 00:11:50.940 --> 00:11:50.950 align:start position:0% chair applications that are smoothly 00:11:50.950 --> 00:11:54.450 align:start position:0% chair applications that are smoothly running<00:11:51.280> on<00:11:52.030> can<00:11:52.480> afford<00:11:52.750> to<00:11:53.410> support<00:11:53.830> another 00:11:54.450 --> 00:11:54.460 align:start position:0% running on can afford to support another 00:11:54.460 --> 00:11:58.110 align:start position:0% running on can afford to support another a<00:11:54.940> great<00:11:55.300> in<00:11:55.450> our<00:11:55.540> interesting<00:11:56.320> use<00:11:56.530> case<00:11:57.120> but 00:11:58.110 --> 00:11:58.120 align:start position:0% a great in our interesting use case but 00:11:58.120 --> 00:12:02.180 align:start position:0% a great in our interesting use case but for<00:11:58.510> some<00:11:58.780> of<00:11:58.990> these<00:11:59.170> use<00:11:59.500> cases<00:12:00.090> we<00:12:01.090> are<00:12:01.450> just 00:12:02.180 --> 00:12:02.190 align:start position:0% for some of these use cases we are just 00:12:02.190 --> 00:12:06.870 align:start position:0% for some of these use cases we are just starting<00:12:03.190> realizing<00:12:04.090> that<00:12:05.100> there<00:12:06.100> cannot<00:12:06.730> be 00:12:06.870 --> 00:12:06.880 align:start position:0% starting realizing that there cannot be 00:12:06.880 --> 00:12:12.210 align:start position:0% starting realizing that there cannot be limits<00:12:08.490> take<00:12:09.490> that<00:12:09.670> book<00:12:10.110> what<00:12:11.110> about<00:12:11.380> if<00:12:11.860> the 00:12:12.210 --> 00:12:12.220 align:start position:0% limits take that book what about if the 00:12:12.220 --> 00:12:16.500 align:start position:0% limits take that book what about if the execution<00:12:13.060> is<00:12:13.480> becoming<00:12:14.790> these<00:12:15.790> giving<00:12:16.270> up<00:12:16.480> a 00:12:16.500 --> 00:12:16.510 align:start position:0% execution is becoming these giving up a 00:12:16.510 --> 00:12:18.270 align:start position:0% execution is becoming these giving up a great<00:12:17.010> frequented 00:12:18.270 --> 00:12:18.280 align:start position:0% great frequented 00:12:18.280 --> 00:12:21.210 align:start position:0% great frequented so<00:12:19.150> if<00:12:19.510> every<00:12:19.900> since<00:12:20.140> are<00:12:20.680> deployed<00:12:21.070> on 00:12:21.210 --> 00:12:21.220 align:start position:0% so if every since are deployed on 00:12:21.220 --> 00:12:26.190 align:start position:0% so if every since are deployed on content<00:12:21.730> walks<00:12:22.000> into<00:12:22.690> the<00:12:22.990> constant<00:12:24.390> and<00:12:25.390> for 00:12:26.190 --> 00:12:26.200 align:start position:0% content walks into the constant and for 00:12:26.200 --> 00:12:28.650 align:start position:0% content walks into the constant and for some<00:12:26.410> values<00:12:26.800> cases<00:12:27.340> some<00:12:28.060> execution 00:12:28.650 --> 00:12:28.660 align:start position:0% some values cases some execution 00:12:28.660 --> 00:12:30.860 align:start position:0% some values cases some execution execution<00:12:28.990> logic<00:12:29.710> could<00:12:29.950> be<00:12:30.070> very<00:12:30.400> very 00:12:30.860 --> 00:12:30.870 align:start position:0% execution logic could be very very 00:12:30.870 --> 00:12:35.280 align:start position:0% execution logic could be very very complex<00:12:31.870> and<00:12:32.320> sophisticated<00:12:33.690> it<00:12:34.690> is<00:12:34.750> just<00:12:35.080> it 00:12:35.280 --> 00:12:35.290 align:start position:0% complex and sophisticated it is just it 00:12:35.290 --> 00:12:39.890 align:start position:0% complex and sophisticated it is just it is<00:12:35.650> constant<00:12:36.520> costly<00:12:36.940> and<00:12:37.650> it's<00:12:38.650> money<00:12:39.070> on<00:12:39.370> the 00:12:39.890 --> 00:12:39.900 align:start position:0% is constant costly and it's money on the 00:12:39.900 --> 00:12:41.880 align:start position:0% is constant costly and it's money on the eastern<00:12:40.900> virtual<00:12:41.410> machine 00:12:41.880 --> 00:12:41.890 align:start position:0% eastern virtual machine 00:12:41.890 --> 00:12:44.940 align:start position:0% eastern virtual machine parents<00:12:42.550> not<00:12:42.790> so<00:12:43.090> efficient<00:12:43.930> if<00:12:44.620> the 00:12:44.940 --> 00:12:44.950 align:start position:0% parents not so efficient if the 00:12:44.950 --> 00:12:46.960 align:start position:0% parents not so efficient if the application<00:12:45.250> becomes<00:12:45.580> so<00:12:45.970> softly 00:12:46.960 --> 00:12:46.970 align:start position:0% application becomes so softly 00:12:46.970 --> 00:12:52.579 align:start position:0% application becomes so softly so<00:12:47.970> we<00:12:48.899> have<00:12:49.110> Nadia<00:12:49.879> why<00:12:50.879> don't<00:12:51.629> we<00:12:51.749> just<00:12:52.050> leave 00:12:52.579 --> 00:12:52.589 align:start position:0% so we have Nadia why don't we just leave 00:12:52.589 --> 00:12:55.819 align:start position:0% so we have Nadia why don't we just leave it<00:12:52.829> migrate<00:12:53.399> this<00:12:54.029> execution<00:12:54.839> Brown<00:12:55.470> I'm 00:12:55.819 --> 00:12:55.829 align:start position:0% it migrate this execution Brown I'm 00:12:55.829 --> 00:12:58.400 align:start position:0% it migrate this execution Brown I'm chained<00:12:56.220> to<00:12:56.249> the<00:12:56.850> option<00:12:57.389> trusted<00:12:58.110> execution 00:12:58.400 --> 00:12:58.410 align:start position:0% chained to the option trusted execution 00:12:58.410 --> 00:13:03.559 align:start position:0% chained to the option trusted execution of<00:12:58.800> the<00:12:58.949> environment<00:13:00.739> so<00:13:01.910> the<00:13:02.910> application 00:13:03.559 --> 00:13:03.569 align:start position:0% of the environment so the application 00:13:03.569 --> 00:13:06.499 align:start position:0% of the environment so the application wrong<00:13:03.809> in<00:13:04.079> our<00:13:04.230> training<00:13:05.299> opportunity<00:13:06.299> works 00:13:06.499 --> 00:13:06.509 align:start position:0% wrong in our training opportunity works 00:13:06.509 --> 00:13:09.619 align:start position:0% wrong in our training opportunity works so<00:13:07.199> whenever<00:13:08.040> you<00:13:08.339> want<00:13:08.629> upgraded 00:13:09.619 --> 00:13:09.629 align:start position:0% so whenever you want upgraded 00:13:09.629 --> 00:13:11.749 align:start position:0% so whenever you want upgraded applications<00:13:10.259> it<00:13:10.709> just<00:13:11.129> represent<00:13:11.639> nearly 00:13:11.749 --> 00:13:11.759 align:start position:0% applications it just represent nearly 00:13:11.759 --> 00:13:16.249 align:start position:0% applications it just represent nearly zero<00:13:12.629> cost<00:13:12.959> and<00:13:13.790> of<00:13:14.790> champ<00:13:15.149> our<00:13:15.720> execution 00:13:16.249 --> 00:13:16.259 align:start position:0% zero cost and of champ our execution 00:13:16.259 --> 00:13:19.489 align:start position:0% zero cost and of champ our execution holy<00:13:16.889> soft<00:13:17.249> attacked<00:13:17.670> occasions<00:13:18.499> with 00:13:19.489 --> 00:13:19.499 align:start position:0% holy soft attacked occasions with 00:13:19.499 --> 00:13:23.449 align:start position:0% holy soft attacked occasions with incremental<00:13:20.119> efficiency<00:13:21.410> what's<00:13:22.410> more<00:13:22.649> in 00:13:23.449 --> 00:13:23.459 align:start position:0% incremental efficiency what's more in 00:13:23.459 --> 00:13:24.650 align:start position:0% incremental efficiency what's more in the<00:13:23.610> option<00:13:24.119> it<00:13:24.239> works 00:13:24.650 --> 00:13:24.660 align:start position:0% the option it works 00:13:24.660 --> 00:13:28.239 align:start position:0% the option it works the<00:13:25.259> only<00:13:25.470> excuse<00:13:26.429> me<00:13:26.519> logic<00:13:26.970> and<00:13:27.269> coded<00:13:27.839> in 00:13:28.239 --> 00:13:28.249 align:start position:0% the only excuse me logic and coded in 00:13:28.249 --> 00:13:32.329 align:start position:0% the only excuse me logic and coded in almost<00:13:29.249> any<00:13:29.639> of<00:13:29.910> the<00:13:30.679> mainstream<00:13:31.679> languages 00:13:32.329 --> 00:13:32.339 align:start position:0% almost any of the mainstream languages 00:13:32.339 --> 00:13:35.600 align:start position:0% almost any of the mainstream languages like<00:13:32.759> Java<00:13:33.299> Python<00:13:33.600> JavaScript<00:13:34.230> or<00:13:35.100> girl 00:13:35.600 --> 00:13:35.610 align:start position:0% like Java Python JavaScript or girl 00:13:35.610 --> 00:13:41.619 align:start position:0% like Java Python JavaScript or girl evencio<00:13:36.029> spells<00:13:37.759> so<00:13:38.759> and<00:13:39.569> what's<00:13:40.410> more<00:13:40.589> the 00:13:41.619 --> 00:13:41.629 align:start position:0% evencio spells so and what's more the 00:13:41.629 --> 00:13:44.470 align:start position:0% evencio spells so and what's more the exclusion<00:13:42.629> oi<00:13:42.779> in<00:13:43.110> off<00:13:43.319> channel<00:13:43.709> box<00:13:43.920> it<00:13:44.369> has 00:13:44.470 --> 00:13:44.480 align:start position:0% exclusion oi in off channel box it has 00:13:44.480 --> 00:13:46.970 align:start position:0% exclusion oi in off channel box it has offers<00:13:45.480> better<00:13:45.720> performance<00:13:45.899> because<00:13:46.709> just 00:13:46.970 --> 00:13:46.980 align:start position:0% offers better performance because just 00:13:46.980 --> 00:13:50.090 align:start position:0% offers better performance because just executed<00:13:47.579> worms<00:13:47.879> based<00:13:48.480> on<00:13:48.660> totally<00:13:49.100> confined 00:13:50.090 --> 00:13:50.100 align:start position:0% executed worms based on totally confined 00:13:50.100 --> 00:13:54.699 align:start position:0% executed worms based on totally confined code<00:13:50.839> it<00:13:51.839> allows<00:13:52.170> to<00:13:52.670> very<00:13:53.670> seamlessly 00:13:54.699 --> 00:13:54.709 align:start position:0% code it allows to very seamlessly 00:13:54.709 --> 00:13:58.819 align:start position:0% code it allows to very seamlessly talking<00:13:55.709> with<00:13:56.220> external<00:13:56.850> data<00:13:57.360> source<00:13:57.829> based 00:13:58.819 --> 00:13:58.829 align:start position:0% talking with external data source based 00:13:58.829 --> 00:14:03.710 align:start position:0% talking with external data source based on<00:13:59.100> the<00:13:59.279> course<00:13:59.549> political<00:14:00.179> post<00:14:01.399> and<00:14:02.720> 120 00:14:03.710 --> 00:14:03.720 align:start position:0% on the course political post and 120 00:14:03.720 --> 00:14:06.019 align:start position:0% on the course political post and 120 teachers<00:14:03.839> brought<00:14:04.529> by<00:14:04.829> the<00:14:04.889> key<00:14:05.519> is<00:14:05.970> that 00:14:06.019 --> 00:14:06.029 align:start position:0% teachers brought by the key is that 00:14:06.029 --> 00:14:10.970 align:start position:0% teachers brought by the key is that offers<00:14:06.809> and<00:14:07.290> and<00:14:08.059> privacy<00:14:09.059> preserving<00:14:09.980> at 00:14:10.970 --> 00:14:10.980 align:start position:0% offers and and privacy preserving at 00:14:10.980 --> 00:14:14.269 align:start position:0% offers and and privacy preserving at record<00:14:11.509> aesthetically<00:14:12.509> strictly<00:14:13.230> in<00:14:13.589> gravity 00:14:14.269 --> 00:14:14.279 align:start position:0% record aesthetically strictly in gravity 00:14:14.279 --> 00:14:18.139 align:start position:0% record aesthetically strictly in gravity the<00:14:15.269> decryption<00:14:15.720> can<00:14:16.230> only<00:14:16.470> happens<00:14:17.149> inside 00:14:18.139 --> 00:14:18.149 align:start position:0% the decryption can only happens inside 00:14:18.149 --> 00:14:23.869 align:start position:0% the decryption can only happens inside this<00:14:19.220> DVD<00:14:20.220> Enclave<00:14:20.670> so<00:14:21.540> the<00:14:22.610> promise<00:14:23.610> is 00:14:23.869 --> 00:14:23.879 align:start position:0% this DVD Enclave so the promise is 00:14:23.879 --> 00:14:26.619 align:start position:0% this DVD Enclave so the promise is guaranteed<00:14:24.540> by<00:14:24.839> the<00:14:24.869> hardware<00:14:25.499> level<00:14:25.679> story 00:14:26.619 --> 00:14:26.629 align:start position:0% guaranteed by the hardware level story 00:14:26.629 --> 00:14:30.049 align:start position:0% guaranteed by the hardware level story so<00:14:27.629> his<00:14:27.899> dye<00:14:28.139> work<00:14:28.410> that<00:14:28.740> you<00:14:28.949> can<00:14:29.309> see<00:14:29.669> that 00:14:30.049 --> 00:14:30.059 align:start position:0% so his dye work that you can see that 00:14:30.059 --> 00:14:33.679 align:start position:0% so his dye work that you can see that originally<00:14:30.959> we<00:14:31.169> can<00:14:31.499> deploy<00:14:32.399> our<00:14:32.459> contract<00:14:33.389> on 00:14:33.679 --> 00:14:33.689 align:start position:0% originally we can deploy our contract on 00:14:33.689 --> 00:14:35.960 align:start position:0% originally we can deploy our contract on previous<00:14:34.169> marking<00:14:34.589> tracked<00:14:34.949> your<00:14:35.669> own 00:14:35.960 --> 00:14:35.970 align:start position:0% previous marking tracked your own 00:14:35.970 --> 00:14:39.650 align:start position:0% previous marking tracked your own channel<00:14:36.269> work<00:14:36.600> based<00:14:36.959> on<00:14:37.259> a<00:14:38.329> particle<00:14:39.329> here 00:14:39.650 --> 00:14:39.660 align:start position:0% channel work based on a particle here 00:14:39.660 --> 00:14:42.559 align:start position:0% channel work based on a particle here which<00:14:40.350> is<00:14:40.499> used<00:14:40.799> to<00:14:41.089> sign<00:14:42.089> the<00:14:42.329> browser 00:14:42.559 --> 00:14:42.569 align:start position:0% which is used to sign the browser 00:14:42.569 --> 00:14:45.769 align:start position:0% which is used to sign the browser introduction<00:14:43.290> and<00:14:43.649> now<00:14:44.579> we<00:14:44.639> could<00:14:45.209> migrate 00:14:45.769 --> 00:14:45.779 align:start position:0% introduction and now we could migrate 00:14:45.779 --> 00:14:49.009 align:start position:0% introduction and now we could migrate this<00:14:46.439> mark<00:14:46.769> contract<00:14:47.279> execution<00:14:47.819> are<00:14:48.179> due<00:14:48.419> to 00:14:49.009 --> 00:14:49.019 align:start position:0% this mark contract execution are due to 00:14:49.019 --> 00:14:52.580 align:start position:0% this mark contract execution are due to an<00:14:49.079> often<00:14:49.319> trusted<00:14:50.129> execution<00:14:51.049> event 00:14:52.580 --> 00:14:52.590 align:start position:0% an often trusted execution event 00:14:52.590 --> 00:14:56.170 align:start position:0% an often trusted execution event and<00:14:53.040> unrivaled<00:14:53.640> and<00:14:54.510> we<00:14:55.440> all<00:14:55.650> need<00:14:56.010> to 00:14:56.170 --> 00:14:56.180 align:start position:0% and unrivaled and we all need to 00:14:56.180 --> 00:15:00.260 align:start position:0% and unrivaled and we all need to transfer<00:14:57.320> this<00:14:58.320> tribe<00:14:58.830> came<00:14:59.190> to<00:14:59.610> this<00:14:59.760> pompous 00:15:00.260 --> 00:15:00.270 align:start position:0% transfer this tribe came to this pompous 00:15:00.270 --> 00:15:03.340 align:start position:0% transfer this tribe came to this pompous te<00:15:00.540> enclave<00:15:01.290> we<00:15:01.890> are<00:15:01.980> a<00:15:02.010> high<00:15:02.340> skill<00:15:02.790> channel 00:15:03.340 --> 00:15:03.350 align:start position:0% te enclave we are a high skill channel 00:15:03.350 --> 00:15:06.800 align:start position:0% te enclave we are a high skill channel and<00:15:04.350> after<00:15:04.860> applying<00:15:05.279> the<00:15:05.850> expression<00:15:06.420> logic 00:15:06.800 --> 00:15:06.810 align:start position:0% and after applying the expression logic 00:15:06.810 --> 00:15:09.980 align:start position:0% and after applying the expression logic a<00:15:07.170> block<00:15:07.950> contraction<00:15:08.820> can<00:15:09.089> be<00:15:09.240> transferred 00:15:09.980 --> 00:15:09.990 align:start position:0% a block contraction can be transferred 00:15:09.990 --> 00:15:13.579 align:start position:0% a block contraction can be transferred directly<00:15:10.589> from<00:15:11.040> the<00:15:11.430> TV<00:15:11.640> Conclave<00:15:12.589> internet 00:15:13.579 --> 00:15:13.589 align:start position:0% directly from the TV Conclave internet 00:15:13.589 --> 00:15:15.470 align:start position:0% directly from the TV Conclave internet though<00:15:13.980> this<00:15:14.250> red<00:15:14.550> block<00:15:14.730> introduction 00:15:15.470 --> 00:15:15.480 align:start position:0% though this red block introduction 00:15:15.480 --> 00:15:17.660 align:start position:0% though this red block introduction triggered<00:15:15.930> in<00:15:16.110> the<00:15:16.170> name<00:15:16.440> of<00:15:16.860> people<00:15:17.250> being 00:15:17.660 --> 00:15:17.670 align:start position:0% triggered in the name of people being 00:15:17.670 --> 00:15:21.079 align:start position:0% triggered in the name of people being the<00:15:17.880> owner<00:15:18.270> because<00:15:18.930> only<00:15:19.350> the<00:15:20.339> the<00:15:20.610> private 00:15:21.079 --> 00:15:21.089 align:start position:0% the owner because only the the private 00:15:21.089 --> 00:15:24.290 align:start position:0% the owner because only the the private key<00:15:21.240> is<00:15:21.650> transferred<00:15:22.650> to<00:15:22.680> ete<00:15:23.339> unplayed<00:15:23.820> and 00:15:24.290 --> 00:15:24.300 align:start position:0% key is transferred to ete unplayed and 00:15:24.300 --> 00:15:26.840 align:start position:0% key is transferred to ete unplayed and no<00:15:24.540> one<00:15:24.720> else<00:15:24.930> is<00:15:25.230> neighbor<00:15:25.500> to<00:15:25.860> his<00:15:26.279> patent 00:15:26.840 --> 00:15:26.850 align:start position:0% no one else is neighbor to his patent 00:15:26.850 --> 00:15:32.090 align:start position:0% no one else is neighbor to his patent emperor's<00:15:27.710> particle<00:15:29.390> so<00:15:30.390> in<00:15:30.720> this<00:15:30.900> way<00:15:31.140> we<00:15:31.830> can 00:15:32.090 --> 00:15:32.100 align:start position:0% emperor's particle so in this way we can 00:15:32.100 --> 00:15:35.120 align:start position:0% emperor's particle so in this way we can offload<00:15:32.540> the<00:15:33.540> execution<00:15:34.200> from<00:15:34.470> function<00:15:35.100> to 00:15:35.120 --> 00:15:35.130 align:start position:0% offload the execution from function to 00:15:35.130 --> 00:15:38.930 align:start position:0% offload the execution from function to of<00:15:35.550> chemicals<00:15:36.240> without<00:15:37.110> sacrifice<00:15:38.010> the<00:15:38.610> user 00:15:38.930 --> 00:15:38.940 align:start position:0% of chemicals without sacrifice the user 00:15:38.940 --> 00:15:41.900 align:start position:0% of chemicals without sacrifice the user experience<00:15:39.330> without<00:15:40.290> sacrifice<00:15:41.100> Trustin 00:15:41.900 --> 00:15:41.910 align:start position:0% experience without sacrifice Trustin 00:15:41.910 --> 00:15:48.170 align:start position:0% experience without sacrifice Trustin ease<00:15:42.029> and<00:15:42.540> security<00:15:45.680> so<00:15:46.680> as<00:15:47.250> I<00:15:47.400> just<00:15:47.430> imagining 00:15:48.170 --> 00:15:48.180 align:start position:0% ease and security so as I just imagining 00:15:48.180 --> 00:15:53.900 align:start position:0% ease and security so as I just imagining that<00:15:48.510> great<00:15:49.260> idea<00:15:50.000> to<00:15:51.000> migrate<00:15:51.690> the<00:15:52.910> execution 00:15:53.900 --> 00:15:53.910 align:start position:0% that great idea to migrate the execution 00:15:53.910 --> 00:15:57.590 align:start position:0% that great idea to migrate the execution from<00:15:54.060> the<00:15:54.240> content<00:15:54.720> of<00:15:54.930> gem<00:15:55.290> if<00:15:56.570> for<00:15:57.570> example 00:15:57.590 --> 00:15:57.600 align:start position:0% from the content of gem if for example 00:15:57.600 --> 00:16:01.100 align:start position:0% from the content of gem if for example if<00:15:58.370> execution<00:15:59.370> is<00:15:59.520> to<00:15:59.670> be<00:15:59.760> a<00:15:59.790> great<00:16:00.089> a<00:16:00.600> very 00:16:01.100 --> 00:16:01.110 align:start position:0% if execution is to be a great a very 00:16:01.110 --> 00:16:03.700 align:start position:0% if execution is to be a great a very frequently<00:16:01.589> so<00:16:01.890> that<00:16:02.160> is<00:16:02.310> Ken's<00:16:02.580> party's 00:16:03.700 --> 00:16:03.710 align:start position:0% frequently so that is Ken's party's 00:16:03.710 --> 00:16:08.960 align:start position:0% frequently so that is Ken's party's total<00:16:04.710> excretion<00:16:05.130> logic<00:16:06.260> so<00:16:07.260> yes<00:16:07.620> diagram<00:16:08.220> the 00:16:08.960 --> 00:16:08.970 align:start position:0% total excretion logic so yes diagram the 00:16:08.970 --> 00:16:12.410 align:start position:0% total excretion logic so yes diagram the architecture<00:16:09.900> diagram<00:16:10.310> token<00:16:11.310> which<00:16:12.240> is 00:16:12.410 --> 00:16:12.420 align:start position:0% architecture diagram token which is 00:16:12.420 --> 00:16:16.610 align:start position:0% architecture diagram token which is composed<00:16:12.839> by<00:16:13.339> four<00:16:14.339> principal<00:16:15.060> parts<00:16:15.390> so<00:16:16.140> here 00:16:16.610 --> 00:16:16.620 align:start position:0% composed by four principal parts so here 00:16:16.620 --> 00:16:20.840 align:start position:0% composed by four principal parts so here the<00:16:16.830> UI<00:16:17.010> parts<00:16:17.670> which<00:16:18.540> allows<00:16:19.380> user<00:16:20.310> to<00:16:20.460> find 00:16:20.840 --> 00:16:20.850 align:start position:0% the UI parts which allows user to find 00:16:20.850 --> 00:16:25.850 align:start position:0% the UI parts which allows user to find the<00:16:22.040> iaea<00:16:23.040> token<00:16:23.580> request<00:16:24.060> and<00:16:24.300> the<00:16:25.200> ETA<00:16:25.530> token 00:16:25.850 --> 00:16:25.860 align:start position:0% the iaea token request and the ETA token 00:16:25.860 --> 00:16:29.600 align:start position:0% the iaea token request and the ETA token request<00:16:26.390> could<00:16:27.390> be<00:16:27.570> then<00:16:27.839> captured<00:16:28.800> by<00:16:29.100> te 00:16:29.600 --> 00:16:29.610 align:start position:0% request could be then captured by te 00:16:29.610 --> 00:16:33.140 align:start position:0% request could be then captured by te listen<00:16:30.450> immoral<00:16:31.050> and<00:16:31.520> te<00:16:32.520> listen<00:16:32.910> tomorrow 00:16:33.140 --> 00:16:33.150 align:start position:0% listen immoral and te listen tomorrow 00:16:33.150 --> 00:16:36.770 align:start position:0% listen immoral and te listen tomorrow could<00:16:33.600> then<00:16:34.070> trigger<00:16:35.070> the<00:16:35.490> te<00:16:36.000> s3x 00:16:36.770 --> 00:16:36.780 align:start position:0% could then trigger the te s3x 00:16:36.780 --> 00:16:40.100 align:start position:0% could then trigger the te s3x applications<00:16:37.500> so<00:16:37.950> it's<00:16:38.130> representative<00:16:38.959> ee<00:16:39.959> a 00:16:40.100 --> 00:16:40.110 align:start position:0% applications so it's representative ee a 00:16:40.110 --> 00:16:44.449 align:start position:0% applications so it's representative ee a token<00:16:40.800> a<00:16:41.040> squishy<00:16:41.670> logic<00:16:42.180> rose<00:16:42.900> beside<00:16:43.440> the<00:16:43.770> SG 00:16:44.449 --> 00:16:44.459 align:start position:0% token a squishy logic rose beside the SG 00:16:44.459 --> 00:16:48.030 align:start position:0% token a squishy logic rose beside the SG x<00:16:45.380> te<00:16:46.380> complex<00:16:47.310> of<00:16:47.430> earth 00:16:48.030 --> 00:16:48.040 align:start position:0% x te complex of earth 00:16:48.040 --> 00:16:51.650 align:start position:0% x te complex of earth which<00:16:48.790> is<00:16:49.000> deployed<00:16:49.470> in<00:16:50.470> the<00:16:50.620> Microsoft<00:16:51.280> Asia 00:16:51.650 --> 00:16:51.660 align:start position:0% which is deployed in the Microsoft Asia 00:16:51.660 --> 00:16:55.890 align:start position:0% which is deployed in the Microsoft Asia as<00:16:52.660> Linux<00:16:53.170> virtual<00:16:53.410> machine<00:16:54.600> and<00:16:55.600> after 00:16:55.890 --> 00:16:55.900 align:start position:0% as Linux virtual machine and after 00:16:55.900 --> 00:16:58.580 align:start position:0% as Linux virtual machine and after politics<00:16:56.650> fishing<00:16:57.040> logic<00:16:57.460> the<00:16:58.120> blockchain 00:16:58.580 --> 00:16:58.590 align:start position:0% politics fishing logic the blockchain 00:16:58.590 --> 00:17:01.320 align:start position:0% politics fishing logic the blockchain traction<00:16:59.590> can<00:16:59.800> be<00:16:59.980> triggered<00:17:00.430> from<00:17:00.550> the<00:17:00.880> rocky 00:17:01.320 --> 00:17:01.330 align:start position:0% traction can be triggered from the rocky 00:17:01.330 --> 00:17:04.980 align:start position:0% traction can be triggered from the rocky uncle<00:17:01.960> directly<00:17:02.860> his<00:17:03.400> name<00:17:03.760> of<00:17:04.030> the<00:17:04.300> TE<00:17:04.540> a 00:17:04.980 --> 00:17:04.990 align:start position:0% uncle directly his name of the TE a 00:17:04.990 --> 00:17:07.100 align:start position:0% uncle directly his name of the TE a Arminius<00:17:05.440> traitor 00:17:07.100 --> 00:17:07.110 align:start position:0% Arminius traitor 00:17:07.110 --> 00:17:11.760 align:start position:0% Arminius traitor so<00:17:08.220> this<00:17:09.360> has<00:17:10.360> Angela<00:17:10.839> smashing<00:17:11.350> this<00:17:11.589> is<00:17:11.740> a 00:17:11.760 --> 00:17:11.770 align:start position:0% so this has Angela smashing this is a 00:17:11.770 --> 00:17:14.819 align:start position:0% so this has Angela smashing this is a great<00:17:12.180> cooperation<00:17:13.180> work<00:17:14.170> from<00:17:14.709> the 00:17:14.819 --> 00:17:14.829 align:start position:0% great cooperation work from the 00:17:14.829 --> 00:17:17.550 align:start position:0% great cooperation work from the different<00:17:15.190> ear<00:17:15.459> members<00:17:15.970> so<00:17:16.810> the<00:17:17.199> original 00:17:17.550 --> 00:17:17.560 align:start position:0% different ear members so the original 00:17:17.560 --> 00:17:20.490 align:start position:0% different ear members so the original champ<00:17:18.250> takes<00:17:18.550> charge<00:17:18.940> of<00:17:19.270> the<00:17:19.500> implementation 00:17:20.490 --> 00:17:20.500 align:start position:0% champ takes charge of the implementation 00:17:20.500 --> 00:17:23.550 align:start position:0% champ takes charge of the implementation of<00:17:20.589> the<00:17:20.740> UI<00:17:20.920> part<00:17:21.370> and<00:17:21.640> I<00:17:22.270> sentence<00:17:22.930> charge<00:17:23.230> of 00:17:23.550 --> 00:17:23.560 align:start position:0% of the UI part and I sentence charge of 00:17:23.560 --> 00:17:27.240 align:start position:0% of the UI part and I sentence charge of the<00:17:23.709> implementation<00:17:24.010> of<00:17:24.699> the<00:17:25.030> TE<00:17:25.570> listener<00:17:26.320> as 00:17:27.240 --> 00:17:27.250 align:start position:0% the implementation of the TE listener as 00:17:27.250 --> 00:17:30.750 align:start position:0% the implementation of the TE listener as well<00:17:27.520> as<00:17:27.870> a<00:17:28.870> tedious<00:17:29.680> px<00:17:30.130> application 00:17:30.750 --> 00:17:30.760 align:start position:0% well as a tedious px application 00:17:30.760 --> 00:17:33.570 align:start position:0% well as a tedious px application implement<00:17:31.290> implementation<00:17:32.290> and<00:17:32.590> deploy<00:17:33.280> the 00:17:33.570 --> 00:17:33.580 align:start position:0% implement implementation and deploy the 00:17:33.580 --> 00:17:36.000 align:start position:0% implement implementation and deploy the trust<00:17:33.850> computers<00:17:34.360> computer<00:17:35.170> framework<00:17:35.830> to 00:17:36.000 --> 00:17:36.010 align:start position:0% trust computers computer framework to 00:17:36.010 --> 00:17:40.010 align:start position:0% trust computers computer framework to Microsoft<00:17:36.700> Azure<00:17:37.830> STX<00:17:38.830> virtual<00:17:39.310> machine<00:17:39.610> I 00:17:40.010 --> 00:17:40.020 align:start position:0% Microsoft Azure STX virtual machine I 00:17:40.020 --> 00:17:42.720 align:start position:0% Microsoft Azure STX virtual machine I think<00:17:41.020> also<00:17:41.500> takes<00:17:41.860> charge<00:17:42.130> of<00:17:42.430> the 00:17:42.720 --> 00:17:42.730 align:start position:0% think also takes charge of the 00:17:42.730 --> 00:17:46.490 align:start position:0% think also takes charge of the implementation<00:17:43.450> of<00:17:44.170> the<00:17:44.320> TCF<00:17:44.740> te<00:17:45.310> contract 00:17:46.490 --> 00:17:46.500 align:start position:0% implementation of the TCF te contract 00:17:46.500 --> 00:17:49.500 align:start position:0% implementation of the TCF te contract and<00:17:47.610> consensus<00:17:48.610> takes<00:17:48.910> charge<00:17:49.150> of<00:17:49.390> the 00:17:49.500 --> 00:17:49.510 align:start position:0% and consensus takes charge of the 00:17:49.510 --> 00:17:52.590 align:start position:0% and consensus takes charge of the implementation<00:17:49.810> of<00:17:50.350> the<00:17:50.670> mediator<00:17:51.670> token<00:17:52.150> as 00:17:52.590 --> 00:17:52.600 align:start position:0% implementation of the mediator token as 00:17:52.600 --> 00:17:55.860 align:start position:0% implementation of the mediator token as Malcolm<00:17:53.110> X<00:17:53.320> al<00:17:54.190> Qaeda<00:17:54.520> has<00:17:55.270> charge<00:17:55.570> of<00:17:55.660> the 00:17:55.860 --> 00:17:55.870 align:start position:0% Malcolm X al Qaeda has charge of the 00:17:55.870 --> 00:17:58.890 align:start position:0% Malcolm X al Qaeda has charge of the deploying<00:17:56.350> the<00:17:56.790> virtual<00:17:57.790> networks<00:17:58.180> actually 00:17:58.890 --> 00:17:58.900 align:start position:0% deploying the virtual networks actually 00:17:58.900 --> 00:18:01.770 align:start position:0% deploying the virtual networks actually the<00:17:59.410> proctor<00:18:00.190> networks<00:18:00.640> is<00:18:01.000> based<00:18:01.300> on<00:18:01.480> Cairo 00:18:01.770 --> 00:18:01.780 align:start position:0% the proctor networks is based on Cairo 00:18:01.780 --> 00:18:02.460 align:start position:0% the proctor networks is based on Cairo Airport 00:18:02.460 --> 00:18:02.470 align:start position:0% Airport 00:18:02.470 --> 00:18:07.770 align:start position:0% Airport based<00:18:03.250> on<00:18:03.430> the<00:18:03.640> highway<00:18:04.570> here<00:18:06.360> -<00:18:07.360> use<00:18:07.570> of 00:18:07.770 --> 00:18:07.780 align:start position:0% based on the highway here - use of 00:18:07.780 --> 00:18:13.440 align:start position:0% based on the highway here - use of previous<00:18:08.230> name<00:18:08.440> and<00:18:08.620> password<00:18:09.010> so<00:18:09.730> I<00:18:10.110> might<00:18:12.450> to 00:18:13.440 --> 00:18:13.450 align:start position:0% previous name and password so I might to 00:18:13.450 --> 00:18:16.890 align:start position:0% previous name and password so I might to talk<00:18:13.690> about<00:18:13.780> the<00:18:14.460> small<00:18:15.460> contract<00:18:15.940> improved 00:18:16.890 --> 00:18:16.900 align:start position:0% talk about the small contract improved 00:18:16.900 --> 00:18:18.630 align:start position:0% talk about the small contract improved by<00:18:17.080> processes 00:18:18.630 --> 00:18:18.640 align:start position:0% by processes 00:18:18.640 --> 00:18:20.860 align:start position:0% by processes [Music] 00:18:20.860 --> 00:18:20.870 align:start position:0% [Music] 00:18:20.870 --> 00:18:23.630 align:start position:0% [Music] so<00:18:21.870> in<00:18:22.170> the<00:18:22.380> smart<00:18:22.740> contract<00:18:22.920> layer<00:18:23.370> we<00:18:23.610> have 00:18:23.630 --> 00:18:23.640 align:start position:0% so in the smart contract layer we have 00:18:23.640 --> 00:18:27.170 align:start position:0% so in the smart contract layer we have three<00:18:24.210> components<00:18:24.440> one<00:18:25.440> tokens<00:18:26.030> second<00:18:27.030> are 00:18:27.170 --> 00:18:27.180 align:start position:0% three components one tokens second are 00:18:27.180 --> 00:18:29.300 align:start position:0% three components one tokens second are essentially<00:18:28.020> identifiers<00:18:28.620> with<00:18:28.860> kids<00:18:29.100> and 00:18:29.300 --> 00:18:29.310 align:start position:0% essentially identifiers with kids and 00:18:29.310 --> 00:18:30.830 align:start position:0% essentially identifiers with kids and the<00:18:29.520> third<00:18:29.700> one<00:18:29.880> is<00:18:29.910> going<00:18:30.150> to<00:18:30.210> be<00:18:30.300> verifiable 00:18:30.830 --> 00:18:30.840 align:start position:0% the third one is going to be verifiable 00:18:30.840 --> 00:18:33.440 align:start position:0% the third one is going to be verifiable claims<00:18:31.490> so<00:18:32.490> how<00:18:32.700> we<00:18:32.760> make<00:18:33.030> this<00:18:33.150> ecosystem 00:18:33.440 --> 00:18:33.450 align:start position:0% claims so how we make this ecosystem 00:18:33.450 --> 00:18:36.260 align:start position:0% claims so how we make this ecosystem work<00:18:33.960> is<00:18:34.200> we've<00:18:34.650> deployed<00:18:35.010> these<00:18:35.910> three 00:18:36.260 --> 00:18:36.270 align:start position:0% work is we've deployed these three 00:18:36.270 --> 00:18:39.260 align:start position:0% work is we've deployed these three contracts<00:18:36.780> as<00:18:37.020> an<00:18:37.260> operator<00:18:38.220> contract<00:18:39.000> on 00:18:39.260 --> 00:18:39.270 align:start position:0% contracts as an operator contract on 00:18:39.270 --> 00:18:41.450 align:start position:0% contracts as an operator contract on tops<00:18:39.690> management<00:18:40.590> contracts<00:18:41.100> admin 00:18:41.450 --> 00:18:41.460 align:start position:0% tops management contracts admin 00:18:41.460 --> 00:18:45.800 align:start position:0% tops management contracts admin functions<00:18:41.670> such<00:18:42.090> as<00:18:42.620> ferment<00:18:43.620> transfer<00:18:44.810> such 00:18:45.800 --> 00:18:45.810 align:start position:0% functions such as ferment transfer such 00:18:45.810 --> 00:18:47.840 align:start position:0% functions such as ferment transfer such a<00:18:45.840> right<00:18:46.140> so<00:18:46.590> to<00:18:47.010> be<00:18:47.100> able<00:18:47.160> to<00:18:47.250> do<00:18:47.400> that<00:18:47.520> we<00:18:47.730> need 00:18:47.840 --> 00:18:47.850 align:start position:0% a right so to be able to do that we need 00:18:47.850 --> 00:18:50.630 align:start position:0% a right so to be able to do that we need to<00:18:48.000> make<00:18:48.120> sure<00:18:48.150> that<00:18:49.160> they're<00:18:50.160> participants 00:18:50.630 --> 00:18:50.640 align:start position:0% to make sure that they're participants 00:18:50.640 --> 00:18:52.550 align:start position:0% to make sure that they're participants that<00:18:50.850> are<00:18:50.940> receiving<00:18:51.330> the<00:18:51.480> tokens<00:18:51.870> are<00:18:52.080> one 00:18:52.550 --> 00:18:52.560 align:start position:0% that are receiving the tokens are one 00:18:52.560 --> 00:18:55.040 align:start position:0% that are receiving the tokens are one employees<00:18:52.950> of<00:18:53.130> organization<00:18:53.730> and<00:18:54.720> to<00:18:55.020> the 00:18:55.040 --> 00:18:55.050 align:start position:0% employees of organization and to the 00:18:55.050 --> 00:18:57.710 align:start position:0% employees of organization and to the organization<00:18:55.560> is<00:18:56.100> a<00:18:56.220> member<00:18:56.550> of<00:18:56.820> the<00:18:57.090> ETA<00:18:57.420> and 00:18:57.710 --> 00:18:57.720 align:start position:0% organization is a member of the ETA and 00:18:57.720 --> 00:19:01.520 align:start position:0% organization is a member of the ETA and that<00:18:58.620> is<00:18:58.800> where<00:18:58.980> the<00:18:59.190> GRC<00:18:59.700> 780<00:19:00.480> and<00:19:00.780> the<00:19:00.870> 1056 00:19:01.520 --> 00:19:01.530 align:start position:0% that is where the GRC 780 and the 1056 00:19:01.530 --> 00:19:05.080 align:start position:0% that is where the GRC 780 and the 1056 come<00:19:01.770> come<00:19:02.130> into<00:19:02.430> play<00:19:02.580> the<00:19:03.450> GRC<00:19:03.870> 780<00:19:04.470> is 00:19:05.080 --> 00:19:05.090 align:start position:0% come come into play the GRC 780 is 00:19:05.090 --> 00:19:08.030 align:start position:0% come come into play the GRC 780 is contract<00:19:06.090> claim<00:19:07.050> dry<00:19:07.320> stream<00:19:07.590> contract 00:19:08.030 --> 00:19:08.040 align:start position:0% contract claim dry stream contract 00:19:08.040 --> 00:19:09.860 align:start position:0% contract claim dry stream contract originally<00:19:08.850> developed<00:19:09.060> by<00:19:09.210> airport<00:19:09.630> and 00:19:09.860 --> 00:19:09.870 align:start position:0% originally developed by airport and 00:19:09.870 --> 00:19:12.560 align:start position:0% originally developed by airport and we've<00:19:10.590> adapted<00:19:10.890> it<00:19:11.220> for<00:19:11.490> this<00:19:11.790> use<00:19:12.060> case<00:19:12.150> and 00:19:12.560 --> 00:19:12.570 align:start position:0% we've adapted it for this use case and 00:19:12.570 --> 00:19:15.470 align:start position:0% we've adapted it for this use case and essentially<00:19:13.380> it's<00:19:14.070> a<00:19:14.280> contract<00:19:14.880> where<00:19:15.240> we 00:19:15.470 --> 00:19:15.480 align:start position:0% essentially it's a contract where we 00:19:15.480 --> 00:19:18.430 align:start position:0% essentially it's a contract where we allow<00:19:15.870> an<00:19:16.740> admin<00:19:17.310> to<00:19:17.490> specify<00:19:18.060> which 00:19:18.430 --> 00:19:18.440 align:start position:0% allow an admin to specify which 00:19:18.440 --> 00:19:22.850 align:start position:0% allow an admin to specify which organizations<00:19:19.440> are<00:19:19.560> members<00:19:20.490> of<00:19:20.630> and<00:19:21.860> then 00:19:22.850 --> 00:19:22.860 align:start position:0% organizations are members of and then 00:19:22.860 --> 00:19:25.490 align:start position:0% organizations are members of and then the<00:19:22.950> second<00:19:23.450> contract<00:19:24.450> is<00:19:24.720> going<00:19:25.260> to<00:19:25.410> be 00:19:25.490 --> 00:19:25.500 align:start position:0% the second contract is going to be 00:19:25.500 --> 00:19:27.770 align:start position:0% the second contract is going to be variable<00:19:26.400> different<00:19:26.730> shoe<00:19:26.910> or<00:19:27.150> it'll<00:19:27.510> tend<00:19:27.690> to 00:19:27.770 --> 00:19:27.780 align:start position:0% variable different shoe or it'll tend to 00:19:27.780 --> 00:19:28.400 align:start position:0% variable different shoe or it'll tend to be<00:19:27.900> six 00:19:28.400 --> 00:19:28.410 align:start position:0% be six 00:19:28.410 --> 00:19:30.770 align:start position:0% be six let's<00:19:28.860> also<00:19:29.130> contract<00:19:29.640> standard<00:19:30.420> that's<00:19:30.600> but 00:19:30.770 --> 00:19:30.780 align:start position:0% let's also contract standard that's but 00:19:30.780 --> 00:19:33.620 align:start position:0% let's also contract standard that's but that<00:19:30.990> was<00:19:31.110> developed<00:19:31.410> by<00:19:31.440> q4<00:19:31.700> and<00:19:32.700> it's<00:19:33.030> going 00:19:33.620 --> 00:19:33.630 align:start position:0% that was developed by q4 and it's going 00:19:33.630 --> 00:19:38.090 align:start position:0% that was developed by q4 and it's going to<00:19:33.780> allow<00:19:34.140> an<00:19:34.620> organization<00:19:35.430> to<00:19:35.910> specify<00:19:37.100> who 00:19:38.090 --> 00:19:38.100 align:start position:0% to allow an organization to specify who 00:19:38.100 --> 00:19:39.950 align:start position:0% to allow an organization to specify who is<00:19:38.400> an<00:19:38.670> employee<00:19:38.910> of<00:19:39.120> the<00:19:39.180> organization<00:19:39.300> so 00:19:39.950 --> 00:19:39.960 align:start position:0% is an employee of the organization so 00:19:39.960 --> 00:19:42.050 align:start position:0% is an employee of the organization so this<00:19:40.110> is<00:19:40.200> not<00:19:40.320> even<00:19:41.160> function<00:19:41.610> but<00:19:41.850> we<00:19:41.910> don't 00:19:42.050 --> 00:19:42.060 align:start position:0% this is not even function but we don't 00:19:42.060 --> 00:19:43.520 align:start position:0% this is not even function but we don't want<00:19:42.180> that<00:19:42.300> function<00:19:42.510> we<00:19:43.260> want<00:19:43.380> the 00:19:43.520 --> 00:19:43.530 align:start position:0% want that function we want the 00:19:43.530 --> 00:19:45.110 align:start position:0% want that function we want the organisation's<00:19:44.160> myself<00:19:44.490> specified<00:19:44.910> who's 00:19:45.110 --> 00:19:45.120 align:start position:0% organisation's myself specified who's 00:19:45.120 --> 00:19:46.580 align:start position:0% organisation's myself specified who's working<00:19:45.750> on<00:19:45.810> their<00:19:45.960> behalf<00:19:46.050> or<00:19:46.470> their 00:19:46.580 --> 00:19:46.590 align:start position:0% working on their behalf or their 00:19:46.590 --> 00:19:48.920 align:start position:0% working on their behalf or their delegates<00:19:47.010> so<00:19:47.910> the<00:19:48.030> function<00:19:48.540> we're<00:19:48.660> actually 00:19:48.920 --> 00:19:48.930 align:start position:0% delegates so the function we're actually 00:19:48.930 --> 00:19:50.480 align:start position:0% delegates so the function we're actually really<00:19:49.170> interested<00:19:49.620> is<00:19:49.770> the<00:19:49.800> set<00:19:50.130> delegate 00:19:50.480 --> 00:19:50.490 align:start position:0% really interested is the set delegate 00:19:50.490 --> 00:19:53.270 align:start position:0% really interested is the set delegate function<00:19:50.880> in<00:19:50.970> topic<00:19:51.360> 6<00:19:51.630> so<00:19:52.200> I<00:19:52.230> never<00:19:52.440> gonna<00:19:53.010> say 00:19:53.270 --> 00:19:53.280 align:start position:0% function in topic 6 so I never gonna say 00:19:53.280 --> 00:19:55.340 align:start position:0% function in topic 6 so I never gonna say Scott<00:19:53.700> instead<00:19:54.120> you<00:19:54.570> deploy<00:19:54.960> these<00:19:55.140> I 00:19:55.340 --> 00:19:55.350 align:start position:0% Scott instead you deploy these I 00:19:55.350 --> 00:19:57.230 align:start position:0% Scott instead you deploy these I spell<00:19:55.560> again<00:19:55.770> support<00:19:56.100> me<00:19:56.190> on<00:19:56.250> the<00:19:56.370> path<00:19:56.580> so 00:19:57.230 --> 00:19:57.240 align:start position:0% spell again support me on the path so 00:19:57.240 --> 00:19:59.480 align:start position:0% spell again support me on the path so that<00:19:57.270> what<00:19:57.510> we<00:19:57.660> meant<00:19:57.870> tokens<00:19:58.350> the<00:19:58.680> EI<00:19:58.890> and 00:19:59.480 --> 00:19:59.490 align:start position:0% that what we meant tokens the EI and 00:19:59.490 --> 00:20:02.390 align:start position:0% that what we meant tokens the EI and when<00:19:59.580> they<00:19:59.700> selected<00:20:00.180> tokens<00:20:01.110> it's<00:20:01.890> going<00:20:02.250> to 00:20:02.390 --> 00:20:02.400 align:start position:0% when they selected tokens it's going to 00:20:02.400 --> 00:20:05.440 align:start position:0% when they selected tokens it's going to check<00:20:02.670> one<00:20:03.540> is<00:20:03.780> the<00:20:03.990> organization 00:20:05.440 --> 00:20:05.450 align:start position:0% check one is the organization 00:20:05.450 --> 00:20:08.289 align:start position:0% check one is the organization through<00:20:05.960> the<00:20:06.049> 780<00:20:06.559> and<00:20:06.950> then<00:20:07.519> to<00:20:07.850> its<00:20:08.090> going<00:20:08.240> to 00:20:08.289 --> 00:20:08.299 align:start position:0% through the 780 and then to its going to 00:20:08.299 --> 00:20:11.680 align:start position:0% through the 780 and then to its going to check<00:20:08.600> if<00:20:08.870> the<00:20:09.110> employee<00:20:09.440> is<00:20:10.279> a<00:20:10.690> participant 00:20:11.680 --> 00:20:11.690 align:start position:0% check if the employee is a participant 00:20:11.690 --> 00:20:13.210 align:start position:0% check if the employee is a participant as<00:20:11.779> an<00:20:11.899> employee<00:20:12.169> or<00:20:12.289> organization<00:20:12.919> under<00:20:13.100> the 00:20:13.210 --> 00:20:13.220 align:start position:0% as an employee or organization under the 00:20:13.220 --> 00:20:13.870 align:start position:0% as an employee or organization under the m56 00:20:13.870 --> 00:20:13.880 align:start position:0% m56 00:20:13.880 --> 00:20:16.470 align:start position:0% m56 and<00:20:14.029> then<00:20:14.720> from<00:20:14.899> there<00:20:15.080> we<00:20:15.200> met<00:20:15.350> their<00:20:15.559> tokens 00:20:16.470 --> 00:20:16.480 align:start position:0% and then from there we met their tokens 00:20:16.480 --> 00:20:19.390 align:start position:0% and then from there we met their tokens based<00:20:17.480> on<00:20:17.659> what<00:20:17.929> the<00:20:18.049> amount 00:20:19.390 --> 00:20:19.400 align:start position:0% based on what the amount 00:20:19.400 --> 00:20:26.279 align:start position:0% based on what the amount [Music] 00:20:26.279 --> 00:20:26.289 align:start position:0% 00:20:26.289 --> 00:20:29.680 align:start position:0% hey<00:20:27.289> so<00:20:27.740> this<00:20:27.950> is<00:20:28.009> gonna<00:20:28.429> get<00:20:28.700> increasingly 00:20:29.680 --> 00:20:29.690 align:start position:0% hey so this is gonna get increasingly 00:20:29.690 --> 00:20:32.460 align:start position:0% hey so this is gonna get increasingly more<00:20:30.019> complex<00:20:30.320> so<00:20:30.830> let's<00:20:31.159> just<00:20:31.580> bear<00:20:31.759> with<00:20:31.789> us 00:20:32.460 --> 00:20:32.470 align:start position:0% more complex so let's just bear with us 00:20:32.470 --> 00:20:35.409 align:start position:0% more complex so let's just bear with us before<00:20:33.470> we<00:20:33.769> step<00:20:34.070> through<00:20:34.100> this<00:20:34.429> chart<00:20:34.700> that's 00:20:35.409 --> 00:20:35.419 align:start position:0% before we step through this chart that's 00:20:35.419 --> 00:20:37.899 align:start position:0% before we step through this chart that's uh<00:20:35.690> let's<00:20:36.289> use<00:20:36.470> an<00:20:36.620> example<00:20:36.740> why<00:20:37.429> are<00:20:37.759> we 00:20:37.899 --> 00:20:37.909 align:start position:0% uh let's use an example why are we 00:20:37.909 --> 00:20:40.600 align:start position:0% uh let's use an example why are we bothering<00:20:38.120> doing<00:20:38.779> all<00:20:39.440> this<00:20:39.740> stuff<00:20:39.919> that's 00:20:40.600 --> 00:20:40.610 align:start position:0% bothering doing all this stuff that's 00:20:40.610 --> 00:20:42.879 align:start position:0% bothering doing all this stuff that's that's<00:20:40.999> the<00:20:41.149> heart<00:20:41.360> of<00:20:41.499> cute 00:20:42.879 --> 00:20:42.889 align:start position:0% that's the heart of cute 00:20:42.889 --> 00:20:49.060 align:start position:0% that's the heart of cute so<00:20:43.899> notice<00:20:44.899> about<00:20:45.080> yours<00:20:45.409> 220<00:20:46.360> right<00:20:47.360> so<00:20:48.200> I'm 00:20:49.060 --> 00:20:49.070 align:start position:0% so notice about yours 220 right so I'm 00:20:49.070 --> 00:20:50.799 align:start position:0% so notice about yours 220 right so I'm talking<00:20:49.490> about<00:20:49.519> tokens<00:20:50.120> none<00:20:50.360> fungible 00:20:50.799 --> 00:20:50.809 align:start position:0% talking about tokens none fungible 00:20:50.809 --> 00:20:57.310 align:start position:0% talking about tokens none fungible talking<00:20:51.340> so<00:20:52.720> LC<00:20:53.720> 721<00:20:54.820> okay<00:20:55.850> so<00:20:56.450> 20<00:20:57.200> with 00:20:57.310 --> 00:20:57.320 align:start position:0% talking so LC 721 okay so 20 with 00:20:57.320 --> 00:20:58.930 align:start position:0% talking so LC 721 okay so 20 with Hawkins<00:20:57.619> and<00:20:57.740> not<00:20:57.889> wonderful<00:20:58.309> talking's<00:20:58.669> I 00:20:58.930 --> 00:20:58.940 align:start position:0% Hawkins and not wonderful talking's I 00:20:58.940 --> 00:21:02.409 align:start position:0% Hawkins and not wonderful talking's I run<00:20:59.539> those<00:20:59.749> in<00:21:00.049> unity<00:21:00.830> everybody<00:21:01.700> knows<00:21:01.970> who's 00:21:02.409 --> 00:21:02.419 align:start position:0% run those in unity everybody knows who's 00:21:02.419 --> 00:21:05.499 align:start position:0% run those in unity everybody knows who's they're<00:21:02.690> going<00:21:03.019> to<00:21:03.200> and<00:21:03.559> I<00:21:04.279> have<00:21:04.490> issuer<00:21:04.970> that 00:21:05.499 --> 00:21:05.509 align:start position:0% they're going to and I have issuer that 00:21:05.509 --> 00:21:07.899 align:start position:0% they're going to and I have issuer that has<00:21:05.840> the<00:21:06.110> secret<00:21:06.409> key<00:21:06.710> and<00:21:07.070> sign<00:21:07.460> them<00:21:07.700> and 00:21:07.899 --> 00:21:07.909 align:start position:0% has the secret key and sign them and 00:21:07.909 --> 00:21:10.509 align:start position:0% has the secret key and sign them and push<00:21:08.629> the<00:21:08.929> request<00:21:09.470> and<00:21:09.679> you<00:21:10.100> get<00:21:10.249> the<00:21:10.340> token 00:21:10.509 --> 00:21:10.519 align:start position:0% push the request and you get the token 00:21:10.519 --> 00:21:13.149 align:start position:0% push the request and you get the token what's<00:21:11.419> a<00:21:11.539> problem<00:21:11.720> why<00:21:12.230> do<00:21:12.289> we<00:21:12.529> need<00:21:12.679> all<00:21:12.950> this 00:21:13.149 --> 00:21:13.159 align:start position:0% what's a problem why do we need all this 00:21:13.159 --> 00:21:17.680 align:start position:0% what's a problem why do we need all this unitl<00:21:14.320> lets<00:21:15.320> you<00:21:15.499> use<00:21:15.860> this<00:21:16.039> in<00:21:16.249> example<00:21:16.940> let's 00:21:17.680 --> 00:21:17.690 align:start position:0% unitl lets you use this in example let's 00:21:17.690 --> 00:21:21.430 align:start position:0% unitl lets you use this in example let's say<00:21:18.039> wrong<00:21:19.039> is<00:21:19.399> the<00:21:19.730> owner<00:21:20.509> of<00:21:20.749> this<00:21:20.929> cookie 00:21:21.430 --> 00:21:21.440 align:start position:0% say wrong is the owner of this cookie 00:21:21.440 --> 00:21:23.739 align:start position:0% say wrong is the owner of this cookie that<00:21:21.710> condition<00:21:22.190> affects<00:21:22.580> meet<00:21:22.940> the<00:21:23.119> token<00:21:23.509> to 00:21:23.739 --> 00:21:23.749 align:start position:0% that condition affects meet the token to 00:21:23.749 --> 00:21:26.320 align:start position:0% that condition affects meet the token to or<00:21:24.350> nation<00:21:24.830> one<00:21:25.129> so<00:21:25.759> they<00:21:25.940> get<00:21:26.119> some 00:21:26.320 --> 00:21:26.330 align:start position:0% or nation one so they get some 00:21:26.330 --> 00:21:29.109 align:start position:0% or nation one so they get some reputation<00:21:26.600> tokens<00:21:27.230> right<00:21:27.519> and<00:21:28.519> let's<00:21:28.879> see 00:21:29.109 --> 00:21:29.119 align:start position:0% reputation tokens right and let's see 00:21:29.119 --> 00:21:33.129 align:start position:0% reputation tokens right and let's see let's<00:21:29.509> say<00:21:30.070> well<00:21:31.070> actually<00:21:31.509> ramos<00:21:32.509> uncorrupt 00:21:33.129 --> 00:21:33.139 align:start position:0% let's say well actually ramos uncorrupt 00:21:33.139 --> 00:21:39.760 align:start position:0% let's say well actually ramos uncorrupt oh<00:21:33.289> so<00:21:33.529> that's<00:21:33.950> not 00:21:39.760 --> 00:21:39.770 align:start position:0% 00:21:39.770 --> 00:21:42.010 align:start position:0% there's<00:21:40.400> a<00:21:40.550> whole<00:21:40.790> year<00:21:41.060> out<00:21:41.240> with<00:21:41.450> my<00:21:41.600> babies 00:21:42.010 --> 00:21:42.020 align:start position:0% there's a whole year out with my babies 00:21:42.020 --> 00:21:44.590 align:start position:0% there's a whole year out with my babies and<00:21:42.260> I<00:21:43.010> know<00:21:43.070> Charles<00:21:43.670> for<00:21:43.940> a<00:21:43.970> long<00:21:44.120> time<00:21:44.360> so<00:21:44.570> I 00:21:44.590 --> 00:21:44.600 align:start position:0% and I know Charles for a long time so I 00:21:44.600 --> 00:21:47.920 align:start position:0% and I know Charles for a long time so I know<00:21:44.720> he<00:21:45.080> loves<00:21:45.380> exotic<00:21:46.280> this<00:21:46.580> right<00:21:47.060> so<00:21:47.600> we're 00:21:47.920 --> 00:21:47.930 align:start position:0% know he loves exotic this right so we're 00:21:47.930 --> 00:21:50.050 align:start position:0% know he loves exotic this right so we're gonna<00:21:48.050> make<00:21:48.230> it<00:21:48.290> thank<00:21:48.530> Charles<00:21:49.220> for<00:21:49.460> every 00:21:50.050 --> 00:21:50.060 align:start position:0% gonna make it thank Charles for every 00:21:50.060 --> 00:21:52.840 align:start position:0% gonna make it thank Charles for every token<00:21:50.750> you<00:21:50.900> issue<00:21:51.110> to<00:21:51.530> collide<00:21:51.920> oh<00:21:51.950> I'm<00:21:52.580> gonna 00:21:52.840 --> 00:21:52.850 align:start position:0% token you issue to collide oh I'm gonna 00:21:52.850 --> 00:21:57.430 align:start position:0% token you issue to collide oh I'm gonna give<00:21:53.090> you<00:21:53.330> a<00:21:53.360> case<00:21:53.750> of<00:21:54.460> whispers<00:21:55.600> so<00:21:56.600> what<00:21:57.020> what 00:21:57.430 --> 00:21:57.440 align:start position:0% give you a case of whispers so what what 00:21:57.440 --> 00:21:59.980 align:start position:0% give you a case of whispers so what what this<00:21:57.590> means<00:21:57.860> is<00:21:58.130> as<00:21:58.730> long<00:21:59.000> as<00:21:59.210> I<00:21:59.450> can<00:21:59.510> corrupt 00:21:59.980 --> 00:21:59.990 align:start position:0% this means is as long as I can corrupt 00:21:59.990 --> 00:22:03.220 align:start position:0% this means is as long as I can corrupt the<00:22:00.530> secret<00:22:01.340> key<00:22:01.490> holder<00:22:01.880> I<00:22:02.150> can<00:22:02.780> get<00:22:02.960> all<00:22:03.110> the 00:22:03.220 --> 00:22:03.230 align:start position:0% the secret key holder I can get all the 00:22:03.230 --> 00:22:06.940 align:start position:0% the secret key holder I can get all the tokens<00:22:03.380> I<00:22:03.680> want<00:22:03.920> right<00:22:04.310> and<00:22:05.030> there's<00:22:05.360> no<00:22:05.950> safe 00:22:06.940 --> 00:22:06.950 align:start position:0% tokens I want right and there's no safe 00:22:06.950 --> 00:22:10.210 align:start position:0% tokens I want right and there's no safe bar<00:22:07.220> to<00:22:07.460> make<00:22:07.640> sure<00:22:07.880> that<00:22:08.450> reduction<00:22:08.930> is<00:22:09.440> is 00:22:10.210 --> 00:22:10.220 align:start position:0% bar to make sure that reduction is is 00:22:10.220 --> 00:22:13.450 align:start position:0% bar to make sure that reduction is is legit<00:22:10.820> you<00:22:11.630> can<00:22:11.810> only<00:22:11.990> trust<00:22:12.350> as<00:22:12.800> much<00:22:12.860> as<00:22:13.310> you 00:22:13.450 --> 00:22:13.460 align:start position:0% legit you can only trust as much as you 00:22:13.460 --> 00:22:16.600 align:start position:0% legit you can only trust as much as you trust<00:22:13.700> the<00:22:13.910> person<00:22:14.090> that<00:22:14.660> was<00:22:15.280> so<00:22:16.280> what<00:22:16.460> we 00:22:16.600 --> 00:22:16.610 align:start position:0% trust the person that was so what we 00:22:16.610 --> 00:22:19.690 align:start position:0% trust the person that was so what we want<00:22:16.880> is<00:22:17.270> some<00:22:18.200> sort<00:22:18.530> of<00:22:18.650> safeguard<00:22:19.430> to<00:22:19.550> make 00:22:19.690 --> 00:22:19.700 align:start position:0% want is some sort of safeguard to make 00:22:19.700 --> 00:22:24.760 align:start position:0% want is some sort of safeguard to make sure<00:22:19.940> one<00:22:20.410> tweenty<00:22:21.410> request<00:22:22.250> is<00:22:22.430> in<00:22:22.930> issue<00:22:23.930> as 00:22:24.760 --> 00:22:24.770 align:start position:0% sure one tweenty request is in issue as 00:22:24.770 --> 00:22:27.700 align:start position:0% sure one tweenty request is in issue as issued<00:22:25.310> with<00:22:25.960> by<00:22:26.960> meeting<00:22:27.230> a<00:22:27.380> bunch<00:22:27.560> of 00:22:27.700 --> 00:22:27.710 align:start position:0% issued with by meeting a bunch of 00:22:27.710 --> 00:22:29.830 align:start position:0% issued with by meeting a bunch of criterias<00:22:28.370> that's<00:22:28.700> set<00:22:29.120> in<00:22:29.360> place 00:22:29.830 --> 00:22:29.840 align:start position:0% criterias that's set in place 00:22:29.840 --> 00:22:32.230 align:start position:0% criterias that's set in place okay<00:22:30.320> now<00:22:30.470> you<00:22:30.530> think<00:22:31.100> about<00:22:31.250> this<00:22:31.550> we<00:22:32.090> do 00:22:32.230 --> 00:22:32.240 align:start position:0% okay now you think about this we do 00:22:32.240 --> 00:22:34.000 align:start position:0% okay now you think about this we do criteria<00:22:32.750> so<00:22:32.810> why<00:22:33.020> don't<00:22:33.230> we<00:22:33.350> just<00:22:33.560> put<00:22:33.800> them 00:22:34.000 --> 00:22:34.010 align:start position:0% criteria so why don't we just put them 00:22:34.010 --> 00:22:36.910 align:start position:0% criteria so why don't we just put them in<00:22:34.220> a<00:22:34.340> small<00:22:34.430> contract<00:22:35.030> the<00:22:35.840> stands<00:22:36.410> in<00:22:36.530> common 00:22:36.910 --> 00:22:36.920 align:start position:0% in a small contract the stands in common 00:22:36.920 --> 00:22:39.760 align:start position:0% in a small contract the stands in common er<00:22:37.160> C<00:22:37.310> 20<00:22:37.640> and<00:22:37.910> dust<00:22:38.720> about<00:22:38.990> evasion<00:22:39.440> and<00:22:39.620> then 00:22:39.760 --> 00:22:39.770 align:start position:0% er C 20 and dust about evasion and then 00:22:39.770 --> 00:22:44.020 align:start position:0% er C 20 and dust about evasion and then cost<00:22:40.010> us<00:22:40.280> 20<00:22:40.730> right<00:22:41.270> it's<00:22:41.930> easy<00:22:42.260> to<00:22:42.470> solve<00:22:43.030> it 00:22:44.020 --> 00:22:44.030 align:start position:0% cost us 20 right it's easy to solve it 00:22:44.030 --> 00:22:45.940 align:start position:0% cost us 20 right it's easy to solve it can<00:22:44.210> be<00:22:44.300> solved<00:22:44.600> this<00:22:44.690> way<00:22:44.960> it's<00:22:45.350> all<00:22:45.740> your 00:22:45.940 --> 00:22:45.950 align:start position:0% can be solved this way it's all your 00:22:45.950 --> 00:22:48.610 align:start position:0% can be solved this way it's all your checking<00:22:46.430> can<00:22:46.730> be<00:22:46.820> done<00:22:47.030> on<00:22:47.270> the<00:22:47.390> chain<00:22:47.630> and 00:22:48.610 --> 00:22:48.620 align:start position:0% checking can be done on the chain and 00:22:48.620 --> 00:22:50.170 align:start position:0% checking can be done on the chain and all<00:22:48.890> the<00:22:48.920> data<00:22:49.160> is<00:22:49.340> have<00:22:49.550> been<00:22:49.670> launched<00:22:49.940> in 00:22:50.170 --> 00:22:50.180 align:start position:0% all the data is have been launched in 00:22:50.180 --> 00:22:52.810 align:start position:0% all the data is have been launched in you<00:22:50.390> can<00:22:50.570> do<00:22:50.720> this<00:22:50.900> pretty<00:22:51.140> easily<00:22:51.820> there's 00:22:52.810 --> 00:22:52.820 align:start position:0% you can do this pretty easily there's 00:22:52.820 --> 00:22:55.360 align:start position:0% you can do this pretty easily there's there<00:22:53.300> are<00:22:53.330> a<00:22:53.420> lot<00:22:53.570> of<00:22:53.600> situations<00:22:53.900> where<00:22:54.440> the 00:22:55.360 --> 00:22:55.370 align:start position:0% there are a lot of situations where the 00:22:55.370 --> 00:22:57.400 align:start position:0% there are a lot of situations where the check<00:22:55.640> he<00:22:55.820> needs<00:22:56.060> to<00:22:56.240> consult<00:22:56.600> exponent<00:22:57.320> in 00:22:57.400 --> 00:22:57.410 align:start position:0% check he needs to consult exponent in 00:22:57.410 --> 00:23:00.130 align:start position:0% check he needs to consult exponent in bases<00:22:57.920> look<00:22:58.370> at<00:22:58.550> the<00:22:58.700> logs<00:22:58.940> look<00:22:59.750> at<00:22:59.930> the 00:23:00.130 --> 00:23:00.140 align:start position:0% bases look at the logs look at the 00:23:00.140 --> 00:23:02.830 align:start position:0% bases look at the logs look at the meeting<00:23:00.500> minutes<00:23:00.830> from<00:23:01.100> illustrators<00:23:02.030> and<00:23:02.270> do 00:23:02.830 --> 00:23:02.840 align:start position:0% meeting minutes from illustrators and do 00:23:02.840 --> 00:23:05.530 align:start position:0% meeting minutes from illustrators and do the<00:23:03.230> validation<00:23:03.470> from<00:23:04.010> also<00:23:04.910> resources 00:23:05.530 --> 00:23:05.540 align:start position:0% the validation from also resources 00:23:05.540 --> 00:23:07.930 align:start position:0% the validation from also resources that's<00:23:05.780> not<00:23:06.140> reachable<00:23:06.500> from<00:23:06.940> smart 00:23:07.930 --> 00:23:07.940 align:start position:0% that's not reachable from smart 00:23:07.940 --> 00:23:10.810 align:start position:0% that's not reachable from smart contracts<00:23:08.450> and<00:23:09.260> that's<00:23:09.560> where<00:23:09.890> this<00:23:10.160> kind<00:23:10.670> of 00:23:10.810 --> 00:23:10.820 align:start position:0% contracts and that's where this kind of 00:23:10.820 --> 00:23:12.830 align:start position:0% contracts and that's where this kind of solution<00:23:11.330> being<00:23:11.990> said 00:23:12.830 --> 00:23:12.840 align:start position:0% solution being said 00:23:12.840 --> 00:23:15.440 align:start position:0% solution being said and<00:23:13.110> so<00:23:13.770> let's<00:23:14.070> uh<00:23:14.279> let's<00:23:14.549> step<00:23:15.059> through<00:23:15.270> this 00:23:15.440 --> 00:23:15.450 align:start position:0% and so let's uh let's step through this 00:23:15.450 --> 00:23:17.560 align:start position:0% and so let's uh let's step through this and<00:23:15.720> see<00:23:15.929> how<00:23:15.960> this<00:23:16.409> works<00:23:16.710> in<00:23:16.830> this<00:23:17.070> program 00:23:17.560 --> 00:23:17.570 align:start position:0% and see how this works in this program 00:23:17.570 --> 00:23:22.519 align:start position:0% and see how this works in this program right<00:23:18.570> so<00:23:18.900> Amy<00:23:19.789> before<00:23:20.789> this<00:23:21.299> can<00:23:21.539> flow<00:23:21.840> and<00:23:22.140> to 00:23:22.519 --> 00:23:22.529 align:start position:0% right so Amy before this can flow and to 00:23:22.529 --> 00:23:24.740 align:start position:0% right so Amy before this can flow and to end<00:23:22.679> we<00:23:23.220> need<00:23:23.429> to<00:23:23.520> do<00:23:23.669> two<00:23:23.940> things<00:23:23.970> we<00:23:24.510> need<00:23:24.630> to 00:23:24.740 --> 00:23:24.750 align:start position:0% end we need to do two things we need to 00:23:24.750 --> 00:23:28.700 align:start position:0% end we need to do two things we need to make<00:23:24.929> sure<00:23:25.200> the<00:23:25.830> ending<00:23:27.140> secret<00:23:28.140> keys<00:23:28.350> are<00:23:28.590> in 00:23:28.700 --> 00:23:28.710 align:start position:0% make sure the ending secret keys are in 00:23:28.710 --> 00:23:32.240 align:start position:0% make sure the ending secret keys are in place<00:23:28.950> so<00:23:29.250> first<00:23:29.909> of<00:23:30.029> all<00:23:30.150> you<00:23:30.990> have<00:23:31.230> the<00:23:31.260> front 00:23:32.240 --> 00:23:32.250 align:start position:0% place so first of all you have the front 00:23:32.250 --> 00:23:35.930 align:start position:0% place so first of all you have the front end<00:23:32.600> and<00:23:33.600> it<00:23:33.720> has<00:23:33.750> a<00:23:33.840> block<00:23:34.110> chain<00:23:34.380> and<00:23:34.940> then 00:23:35.930 --> 00:23:35.940 align:start position:0% end and it has a block chain and then 00:23:35.940 --> 00:23:38.350 align:start position:0% end and it has a block chain and then somebody<00:23:36.419> needs<00:23:36.480> to<00:23:36.750> hold 00:23:38.350 --> 00:23:38.360 align:start position:0% somebody needs to hold 00:23:38.360 --> 00:23:41.710 align:start position:0% somebody needs to hold has<00:23:39.360> the<00:23:39.750> special<00:23:40.470> power<00:23:40.800> of<00:23:41.130> being<00:23:41.400> too<00:23:41.550> close 00:23:41.710 --> 00:23:41.720 align:start position:0% has the special power of being too close 00:23:41.720 --> 00:23:45.380 align:start position:0% has the special power of being too close so<00:23:42.720> that's<00:23:42.960> going<00:23:43.320> to<00:23:43.430> exist<00:23:44.430> at<00:23:44.640> this<00:23:45.060> later 00:23:45.380 --> 00:23:45.390 align:start position:0% so that's going to exist at this later 00:23:45.390 --> 00:23:48.710 align:start position:0% so that's going to exist at this later we<00:23:45.630> call<00:23:45.900> a<00:23:46.680> trusted<00:23:47.460> compute<00:23:47.820> listener<00:23:48.240> this 00:23:48.710 --> 00:23:48.720 align:start position:0% we call a trusted compute listener this 00:23:48.720 --> 00:23:52.940 align:start position:0% we call a trusted compute listener this is<00:23:48.870> basically<00:23:49.320> the<00:23:49.470> API<00:23:50.090> service<00:23:51.110> makes<00:23:52.110> the 00:23:52.940 --> 00:23:52.950 align:start position:0% is basically the API service makes the 00:23:52.950 --> 00:23:56.030 align:start position:0% is basically the API service makes the system<00:23:53.160> work<00:23:53.340> together<00:23:53.790> with<00:23:54.270> from<00:23:54.660> them<00:23:55.040> and 00:23:56.030 --> 00:23:56.040 align:start position:0% system work together with from them and 00:23:56.040 --> 00:24:00.470 align:start position:0% system work together with from them and then<00:23:56.520> this<00:23:57.180> is<00:23:57.390> going<00:23:57.630> to<00:23:57.720> call<00:23:58.530> some<00:23:59.480> trusted 00:24:00.470 --> 00:24:00.480 align:start position:0% then this is going to call some trusted 00:24:00.480 --> 00:24:03.530 align:start position:0% then this is going to call some trusted system<00:24:00.960> that<00:24:01.260> you<00:24:01.500> can<00:24:01.650> say<00:24:01.950> when<00:24:02.850> this<00:24:03.300> system 00:24:03.530 --> 00:24:03.540 align:start position:0% system that you can say when this system 00:24:03.540 --> 00:24:06.470 align:start position:0% system that you can say when this system is<00:24:03.930> executing<00:24:04.590> some<00:24:04.830> logic<00:24:05.280> I<00:24:05.490> can<00:24:06.090> be<00:24:06.210> somehow 00:24:06.470 --> 00:24:06.480 align:start position:0% is executing some logic I can be somehow 00:24:06.480 --> 00:24:08.960 align:start position:0% is executing some logic I can be somehow guarantees<00:24:07.230> and<00:24:07.500> convinced<00:24:08.010> that<00:24:08.580> is<00:24:08.730> running 00:24:08.960 --> 00:24:08.970 align:start position:0% guarantees and convinced that is running 00:24:08.970 --> 00:24:12.650 align:start position:0% guarantees and convinced that is running the<00:24:09.090> right<00:24:09.330> logic<00:24:09.740> and<00:24:10.740> the<00:24:11.520> magic<00:24:11.940> is<00:24:12.120> in<00:24:12.150> the 00:24:12.650 --> 00:24:12.660 align:start position:0% the right logic and the magic is in the 00:24:12.660 --> 00:24:17.740 align:start position:0% the right logic and the magic is in the Intel<00:24:13.290> guy's<00:24:13.730> technology<00:24:14.730> called<00:24:15.000> SPS<00:24:16.370> same 00:24:17.740 --> 00:24:17.750 align:start position:0% Intel guy's technology called SPS same 00:24:17.750 --> 00:24:20.900 align:start position:0% Intel guy's technology called SPS same software<00:24:18.770> connect<00:24:19.770> the<00:24:19.950> cars<00:24:20.190> extension 00:24:20.900 --> 00:24:20.910 align:start position:0% software connect the cars extension 00:24:20.910 --> 00:24:24.350 align:start position:0% software connect the cars extension thank<00:24:21.300> you<00:24:21.530> so<00:24:22.530> that<00:24:22.770> you<00:24:23.280> can<00:24:23.520> be<00:24:23.700> convinced 00:24:24.350 --> 00:24:24.360 align:start position:0% thank you so that you can be convinced 00:24:24.360 --> 00:24:28.550 align:start position:0% thank you so that you can be convinced that<00:24:24.420> one<00:24:25.050> it<00:24:25.320> executes<00:24:25.950> as<00:24:26.400> a<00:24:26.580> logic<00:24:27.350> you<00:24:28.350> know 00:24:28.550 --> 00:24:28.560 align:start position:0% that one it executes as a logic you know 00:24:28.560 --> 00:24:30.470 align:start position:0% that one it executes as a logic you know exactly<00:24:29.040> what<00:24:29.340> the<00:24:29.460> project<00:24:29.940> was<00:24:30.210> being 00:24:30.470 --> 00:24:30.480 align:start position:0% exactly what the project was being 00:24:30.480 --> 00:24:33.890 align:start position:0% exactly what the project was being executed<00:24:31.200> in<00:24:31.710> terms<00:24:31.950> of<00:24:32.220> getting<00:24:33.060> a<00:24:33.330> proof<00:24:33.660> or 00:24:33.890 --> 00:24:33.900 align:start position:0% executed in terms of getting a proof or 00:24:33.900 --> 00:24:37.430 align:start position:0% executed in terms of getting a proof or attestation<00:24:34.530> from<00:24:35.010> a<00:24:35.130> component<00:24:36.260> because<00:24:37.260> of 00:24:37.430 --> 00:24:37.440 align:start position:0% attestation from a component because of 00:24:37.440 --> 00:24:41.510 align:start position:0% attestation from a component because of that<00:24:37.590> we<00:24:38.160> know<00:24:38.370> that<00:24:38.400> any<00:24:39.530> to<00:24:40.530> make<00:24:40.950> the<00:24:41.130> token 00:24:41.510 --> 00:24:41.520 align:start position:0% that we know that any to make the token 00:24:41.520 --> 00:24:45.730 align:start position:0% that we know that any to make the token we<00:24:41.730> have<00:24:42.000> to<00:24:42.380> have<00:24:43.380> participation<00:24:44.340> records 00:24:45.730 --> 00:24:45.740 align:start position:0% we have to have participation records 00:24:45.740 --> 00:24:49.200 align:start position:0% we have to have participation records issuing 00:24:49.200 --> 00:24:49.210 align:start position:0% 00:24:49.210 --> 00:24:52.370 align:start position:0% that<00:24:49.690> say<00:24:49.929> the<00:24:50.679> organization<00:24:51.220> participating 00:24:52.370 --> 00:24:52.380 align:start position:0% that say the organization participating 00:24:52.380 --> 00:24:54.930 align:start position:0% that say the organization participating gift<00:24:53.380> up<00:24:53.620> that<00:24:54.010> they<00:24:54.130> have<00:24:54.309> commits<00:24:54.669> that 00:24:54.930 --> 00:24:54.940 align:start position:0% gift up that they have commits that 00:24:54.940 --> 00:24:57.480 align:start position:0% gift up that they have commits that contribute<00:24:55.659> to<00:24:55.900> the<00:24:56.100> publication<00:24:57.100> of<00:24:57.250> the 00:24:57.480 --> 00:24:57.490 align:start position:0% contribute to the publication of the 00:24:57.490 --> 00:24:59.519 align:start position:0% contribute to the publication of the next<00:24:57.760> back<00:24:57.970> that<00:24:58.720> sort<00:24:58.960> of<00:24:58.990> thing<00:24:59.230> to<00:24:59.409> be 00:24:59.519 --> 00:24:59.529 align:start position:0% next back that sort of thing to be 00:24:59.529 --> 00:25:02.460 align:start position:0% next back that sort of thing to be checked<00:24:59.860> here<00:25:00.220> and<00:25:00.400> all<00:25:01.210> the<00:25:01.330> logic<00:25:01.809> run<00:25:02.230> that 00:25:02.460 --> 00:25:02.470 align:start position:0% checked here and all the logic run that 00:25:02.470 --> 00:25:04.680 align:start position:0% checked here and all the logic run that they<00:25:02.679> can<00:25:02.890> call<00:25:03.130> any<00:25:03.370> api's<00:25:04.029> they<00:25:04.270> wanted 00:25:04.680 --> 00:25:04.690 align:start position:0% they can call any api's they wanted 00:25:04.690 --> 00:25:07.380 align:start position:0% they can call any api's they wanted whether<00:25:05.320> they<00:25:05.529> are<00:25:05.679> on<00:25:06.010> general<00:25:06.429> FG<00:25:06.789> object 00:25:07.380 --> 00:25:07.390 align:start position:0% whether they are on general FG object 00:25:07.390 --> 00:25:10.279 align:start position:0% whether they are on general FG object because<00:25:07.720> this<00:25:08.080> is<00:25:08.320> just<00:25:09.159> record<00:25:09.490> regular 00:25:10.279 --> 00:25:10.289 align:start position:0% because this is just record regular 00:25:10.289 --> 00:25:13.590 align:start position:0% because this is just record regular component<00:25:11.289> not<00:25:11.440> a<00:25:11.650> does<00:25:11.919> computer<00:25:12.450> so<00:25:13.450> that's 00:25:13.590 --> 00:25:13.600 align:start position:0% component not a does computer so that's 00:25:13.600 --> 00:25:16.230 align:start position:0% component not a does computer so that's beauty<00:25:14.020> of<00:25:14.140> the<00:25:14.289> solution<00:25:14.740> once<00:25:15.730> we've<00:25:15.970> got 00:25:16.230 --> 00:25:16.240 align:start position:0% beauty of the solution once we've got 00:25:16.240 --> 00:25:19.620 align:start position:0% beauty of the solution once we've got the<00:25:16.600> keys<00:25:16.870> in<00:25:17.049> the<00:25:17.080> right<00:25:17.260> place<00:25:18.210> the<00:25:19.210> Edmond 00:25:19.620 --> 00:25:19.630 align:start position:0% the keys in the right place the Edmond 00:25:19.630 --> 00:25:22.019 align:start position:0% the keys in the right place the Edmond Charles<00:25:20.440> in<00:25:20.529> this<00:25:20.679> case<00:25:20.919> walks<00:25:21.429> into<00:25:21.700> the<00:25:21.880> UI 00:25:22.019 --> 00:25:22.029 align:start position:0% Charles in this case walks into the UI 00:25:22.029 --> 00:25:25.019 align:start position:0% Charles in this case walks into the UI and<00:25:22.659> then<00:25:23.110> says<00:25:23.470> okay<00:25:23.860> Clyde<00:25:24.370> oh<00:25:24.399> did<00:25:24.820> some 00:25:25.019 --> 00:25:25.029 align:start position:0% and then says okay Clyde oh did some 00:25:25.029 --> 00:25:27.110 align:start position:0% and then says okay Clyde oh did some good<00:25:25.179> work<00:25:25.240> that's<00:25:25.690> given<00:25:26.020> to<00:25:26.049> some<00:25:26.529> tokens 00:25:27.110 --> 00:25:27.120 align:start position:0% good work that's given to some tokens 00:25:27.120 --> 00:25:31.250 align:start position:0% good work that's given to some tokens send<00:25:28.120> the<00:25:28.179> request<00:25:28.480> that's<00:25:29.470> going<00:25:29.799> to<00:25:29.860> be 00:25:31.250 --> 00:25:31.260 align:start position:0% send the request that's going to be 00:25:31.260 --> 00:25:35.840 align:start position:0% send the request that's going to be accepted<00:25:32.260> by<00:25:32.940> the<00:25:33.940> customer<00:25:34.390> listener<00:25:35.020> and 00:25:35.840 --> 00:25:35.850 align:start position:0% accepted by the customer listener and 00:25:35.850 --> 00:25:41.430 align:start position:0% accepted by the customer listener and the<00:25:36.850> list<00:25:37.029> of<00:25:37.149> now<00:25:37.390> me<00:25:37.690> still<00:25:37.990> talking<00:25:40.440> secure 00:25:41.430 --> 00:25:41.440 align:start position:0% the list of now me still talking secure 00:25:41.440 --> 00:25:45.840 align:start position:0% the list of now me still talking secure mode<00:25:41.740> so<00:25:42.370> that<00:25:42.840> this<00:25:43.840> request<00:25:44.710> going<00:25:45.309> to<00:25:45.580> the 00:25:45.840 --> 00:25:45.850 align:start position:0% mode so that this request going to the 00:25:45.850 --> 00:25:48.090 align:start position:0% mode so that this request going to the trust 00:25:48.090 --> 00:25:48.100 align:start position:0% trust 00:25:48.100 --> 00:25:52.919 align:start position:0% trust it's<00:25:48.549> going<00:25:48.970> to<00:25:49.059> be<00:25:50.009> secured<00:25:51.009> by<00:25:51.929> public 00:25:52.919 --> 00:25:52.929 align:start position:0% it's going to be secured by public 00:25:52.929 --> 00:25:55.680 align:start position:0% it's going to be secured by public encryption<00:25:53.259> so<00:25:53.769> only<00:25:54.269> economic<00:25:55.269> here<00:25:55.509> at<00:25:55.600> the 00:25:55.680 --> 00:25:55.690 align:start position:0% encryption so only economic here at the 00:25:55.690 --> 00:25:59.159 align:start position:0% encryption so only economic here at the Depot<00:25:56.100> so<00:25:57.100> now<00:25:57.399> the<00:25:57.460> work<00:25:58.090> flow<00:25:58.269> goes<00:25:58.509> to<00:25:58.809> trust 00:25:59.159 --> 00:25:59.169 align:start position:0% Depot so now the work flow goes to trust 00:25:59.169 --> 00:26:03.330 align:start position:0% Depot so now the work flow goes to trust compute<00:25:59.649> it's<00:25:59.889> going<00:26:00.639> to<00:26:00.820> do<00:26:01.269> the<00:26:02.340> logical 00:26:03.330 --> 00:26:03.340 align:start position:0% compute it's going to do the logical 00:26:03.340 --> 00:26:06.360 align:start position:0% compute it's going to do the logical checking<00:26:03.820> and<00:26:04.110> eventually<00:26:05.110> once<00:26:05.559> it<00:26:06.070> passes 00:26:06.360 --> 00:26:06.370 align:start position:0% checking and eventually once it passes 00:26:06.370 --> 00:26:09.899 align:start position:0% checking and eventually once it passes the<00:26:06.669> criteria<00:26:07.240> finally<00:26:08.230> the<00:26:08.499> total<00:26:09.340> issuance 00:26:09.899 --> 00:26:09.909 align:start position:0% the criteria finally the total issuance 00:26:09.909 --> 00:26:12.930 align:start position:0% the criteria finally the total issuance of<00:26:10.179> Isis<00:26:10.809> made<00:26:11.049> until<00:26:12.039> it's<00:26:12.220> officially<00:26:12.669> and 00:26:12.930 --> 00:26:12.940 align:start position:0% of Isis made until it's officially and 00:26:12.940 --> 00:26:18.180 align:start position:0% of Isis made until it's officially and anybody's<00:26:13.480> head<00:26:13.860> so<00:26:14.860> that's<00:26:15.279> the<00:26:15.610> low<00:26:17.009> this<00:26:18.009> is 00:26:18.180 --> 00:26:18.190 align:start position:0% anybody's head so that's the low this is 00:26:18.190 --> 00:26:20.609 align:start position:0% anybody's head so that's the low this is only<00:26:18.340> one<00:26:18.639> pattern<00:26:18.879> of<00:26:19.120> what<00:26:19.990> you<00:26:20.139> can<00:26:20.289> do<00:26:20.409> with 00:26:20.609 --> 00:26:20.619 align:start position:0% only one pattern of what you can do with 00:26:20.619 --> 00:26:23.129 align:start position:0% only one pattern of what you can do with trust<00:26:20.860> a<00:26:20.950> compute<00:26:21.309> there's<00:26:22.269> other<00:26:22.570> like 00:26:23.129 --> 00:26:23.139 align:start position:0% trust a compute there's other like 00:26:23.139 --> 00:26:25.379 align:start position:0% trust a compute there's other like Oracle<00:26:23.499> pendant<00:26:24.070> patterns<00:26:24.429> where<00:26:25.090> you<00:26:25.240> can 00:26:25.379 --> 00:26:25.389 align:start position:0% Oracle pendant patterns where you can 00:26:25.389 --> 00:26:29.159 align:start position:0% Oracle pendant patterns where you can use<00:26:25.629> it<00:26:25.840> to<00:26:26.289> get<00:26:26.769> external<00:26:27.460> data<00:26:27.610> and<00:26:28.210> you<00:26:28.990> can 00:26:29.159 --> 00:26:29.169 align:start position:0% use it to get external data and you can 00:26:29.169 --> 00:26:31.409 align:start position:0% use it to get external data and you can be<00:26:29.259> assured<00:26:29.379> that<00:26:29.619> what<00:26:30.519> one's<00:26:30.909> it's<00:26:31.149> grabbing 00:26:31.409 --> 00:26:31.419 align:start position:0% be assured that what one's it's grabbing 00:26:31.419 --> 00:26:34.430 align:start position:0% be assured that what one's it's grabbing data<00:26:32.139> from<00:26:32.470> external<00:26:32.710> resources<00:26:33.429> they're<00:26:34.119> not 00:26:34.430 --> 00:26:34.440 align:start position:0% data from external resources they're not 00:26:34.440 --> 00:26:38.609 align:start position:0% data from external resources they're not manipulating<00:26:35.440> them<00:26:35.619> right<00:26:36.159> so<00:26:37.529> there<00:26:38.529> are 00:26:38.609 --> 00:26:38.619 align:start position:0% manipulating them right so there are 00:26:38.619 --> 00:26:41.190 align:start position:0% manipulating them right so there are various<00:26:39.029> sensitive<00:26:40.029> data<00:26:40.210> in<00:26:40.570> the<00:26:40.659> world<00:26:40.960> that 00:26:41.190 --> 00:26:41.200 align:start position:0% various sensitive data in the world that 00:26:41.200 --> 00:26:44.009 align:start position:0% various sensitive data in the world that can<00:26:41.499> be<00:26:42.210> millions<00:26:43.210> and<00:26:43.480> millions<00:26:43.840> of<00:26:43.960> dollars 00:26:44.009 --> 00:26:44.019 align:start position:0% can be millions and millions of dollars 00:26:44.019 --> 00:26:46.700 align:start position:0% can be millions and millions of dollars even<00:26:44.980> if<00:26:45.100> you<00:26:45.220> leave<00:26:45.490> it<00:26:45.669> just<00:26:45.940> a<00:26:46.119> tiny<00:26:46.299> bit 00:26:46.700 --> 00:26:46.710 align:start position:0% even if you leave it just a tiny bit 00:26:46.710 --> 00:26:49.350 align:start position:0% even if you leave it just a tiny bit when<00:26:47.710> you<00:26:47.950> are<00:26:47.980> getting<00:26:48.220> that<00:26:48.490> data<00:26:48.730> from<00:26:48.999> this 00:26:49.350 --> 00:26:49.360 align:start position:0% when you are getting that data from this 00:26:49.360 --> 00:26:51.119 align:start position:0% when you are getting that data from this kind<00:26:49.629> of<00:26:49.690> components<00:26:50.259> you<00:26:50.409> know<00:26:50.590> they're<00:26:50.919> not 00:26:51.119 --> 00:26:51.129 align:start position:0% kind of components you know they're not 00:26:51.129 --> 00:26:55.350 align:start position:0% kind of components you know they're not what<00:26:51.279> you<00:26:51.399> paid<00:26:52.379> so 00:26:55.350 --> 00:26:55.360 align:start position:0% what you paid so 00:26:55.360 --> 00:26:57.630 align:start position:0% what you paid so [Music] 00:26:57.630 --> 00:26:57.640 align:start position:0% [Music] 00:26:57.640 --> 00:27:01.640 align:start position:0% [Music] what<00:26:58.240> we<00:26:58.420> have<00:26:58.630> done<00:26:58.870> with<00:26:59.620> the<00:26:59.860> be<00:27:00.820> a<00:27:00.940> token 00:27:01.640 --> 00:27:01.650 align:start position:0% what we have done with the be a token 00:27:01.650 --> 00:27:05.220 align:start position:0% what we have done with the be a token project<00:27:02.650> is<00:27:02.830> if<00:27:03.640> you<00:27:03.850> go<00:27:04.000> to<00:27:04.059> this<00:27:04.330> link<00:27:04.600> you 00:27:05.220 --> 00:27:05.230 align:start position:0% project is if you go to this link you 00:27:05.230 --> 00:27:06.539 align:start position:0% project is if you go to this link you will<00:27:05.260> see<00:27:05.410> all<00:27:05.740> the<00:27:05.860> components<00:27:06.040> that's 00:27:06.539 --> 00:27:06.549 align:start position:0% will see all the components that's 00:27:06.549 --> 00:27:09.600 align:start position:0% will see all the components that's involved<00:27:07.090> to<00:27:07.600> make<00:27:07.630> this<00:27:07.929> work<00:27:08.200> from<00:27:08.610> Mike 00:27:09.600 --> 00:27:09.610 align:start position:0% involved to make this work from Mike 00:27:09.610 --> 00:27:12.410 align:start position:0% involved to make this work from Mike already<00:27:10.030> took<00:27:10.330> you<00:27:10.480> through<00:27:10.809> smart<00:27:11.650> contracts 00:27:12.410 --> 00:27:12.420 align:start position:0% already took you through smart contracts 00:27:12.420 --> 00:27:15.510 align:start position:0% already took you through smart contracts it<00:27:13.420> took<00:27:13.660> about<00:27:14.230> ten<00:27:14.710> different<00:27:15.309> small 00:27:15.510 --> 00:27:15.520 align:start position:0% it took about ten different small 00:27:15.520 --> 00:27:18.870 align:start position:0% it took about ten different small contracting<00:27:16.059> work<00:27:16.179> together<00:27:17.040> so<00:27:18.040> take<00:27:18.760> your 00:27:18.870 --> 00:27:18.880 align:start position:0% contracting work together so take your 00:27:18.880 --> 00:27:21.650 align:start position:0% contracting work together so take your time<00:27:19.120> to<00:27:19.299> understand<00:27:19.660> what<00:27:19.690> each<00:27:20.049> of<00:27:20.260> them<00:27:20.410> do 00:27:21.650 --> 00:27:21.660 align:start position:0% time to understand what each of them do 00:27:21.660 --> 00:27:26.250 align:start position:0% time to understand what each of them do and<00:27:22.660> then<00:27:23.140> the<00:27:23.380> T<00:27:23.590> layer<00:27:24.210> that<00:27:25.210> exact<00:27:25.990> folks 00:27:26.250 --> 00:27:26.260 align:start position:0% and then the T layer that exact folks 00:27:26.260 --> 00:27:30.360 align:start position:0% and then the T layer that exact folks did<00:27:26.590> has<00:27:27.549> two<00:27:27.730> components<00:27:28.299> one<00:27:28.480> is<00:27:28.540> that<00:27:29.370> API 00:27:30.360 --> 00:27:30.370 align:start position:0% did has two components one is that API 00:27:30.370 --> 00:27:32.880 align:start position:0% did has two components one is that API layer<00:27:30.549> that<00:27:30.820> takes<00:27:31.059> request<00:27:31.870> from<00:27:32.049> the<00:27:32.200> UI<00:27:32.380> and 00:27:32.880 --> 00:27:32.890 align:start position:0% layer that takes request from the UI and 00:27:32.890 --> 00:27:35.520 align:start position:0% layer that takes request from the UI and then<00:27:33.429> that<00:27:33.820> launches<00:27:34.419> the<00:27:34.690> worker<00:27:35.350> node 00:27:35.520 --> 00:27:35.530 align:start position:0% then that launches the worker node 00:27:35.530 --> 00:27:38.159 align:start position:0% then that launches the worker node actually<00:27:36.190> does<00:27:36.669> the<00:27:36.850> processing<00:27:37.330> through<00:27:38.049> a 00:27:38.159 --> 00:27:38.169 align:start position:0% actually does the processing through a 00:27:38.169 --> 00:27:41.700 align:start position:0% actually does the processing through a secure<00:27:38.740> Channel<00:27:39.220> and<00:27:40.110> finally<00:27:41.110> that 00:27:41.700 --> 00:27:41.710 align:start position:0% secure Channel and finally that 00:27:41.710 --> 00:27:45.000 align:start position:0% secure Channel and finally that envisioned<00:27:42.250> folks<00:27:42.540> envision<00:27:43.540> blocking<00:27:44.010> the 00:27:45.000 --> 00:27:45.010 align:start position:0% envisioned folks envision blocking the 00:27:45.010 --> 00:27:48.330 align:start position:0% envisioned folks envision blocking the UI<00:27:45.040> work<00:27:45.960> to<00:27:46.960> make<00:27:47.140> it<00:27:47.169> you<00:27:47.620> know<00:27:47.740> grating<00:27:48.130> to 00:27:48.330 --> 00:27:48.340 align:start position:0% UI work to make it you know grating to 00:27:48.340 --> 00:27:52.440 align:start position:0% UI work to make it you know grating to the<00:27:48.580> a<00:27:48.610> member<00:27:49.510> website<00:27:50.410> and<00:27:51.370> finally<00:27:51.820> Marlene 00:27:52.440 --> 00:27:52.450 align:start position:0% the a member website and finally Marlene 00:27:52.450 --> 00:27:56.430 align:start position:0% the a member website and finally Marlene this<00:27:53.290> team<00:27:53.590> did<00:27:54.059> male<00:27:55.059> to<00:27:55.120> make<00:27:55.510> sure<00:27:55.750> the 00:27:56.430 --> 00:27:56.440 align:start position:0% this team did male to make sure the 00:27:56.440 --> 00:28:00.380 align:start position:0% this team did male to make sure the stuff<00:27:56.679> that<00:27:56.890> we<00:27:57.010> do<00:27:57.190> is<00:27:57.429> compliant<00:27:58.120> to<00:27:58.919> TTF 00:28:00.380 --> 00:28:00.390 align:start position:0% stuff that we do is compliant to TTF 00:28:00.390 --> 00:28:04.230 align:start position:0% stuff that we do is compliant to TTF spec<00:28:01.620> so<00:28:02.620> you<00:28:02.679> can<00:28:02.950> check<00:28:03.280> out<00:28:03.490> this<00:28:03.970> stuff 00:28:04.230 --> 00:28:04.240 align:start position:0% spec so you can check out this stuff 00:28:04.240 --> 00:28:07.470 align:start position:0% spec so you can check out this stuff from<00:28:05.140> the<00:28:05.250> pus<00:28:06.250> tree<00:28:06.520> and<00:28:06.730> you<00:28:06.940> if<00:28:07.210> you<00:28:07.299> have 00:28:07.470 --> 00:28:07.480 align:start position:0% from the pus tree and you if you have 00:28:07.480 --> 00:28:09.570 align:start position:0% from the pus tree and you if you have any<00:28:07.600> questions<00:28:08.020> people<00:28:08.440> free<00:28:08.590> the<00:28:08.770> open<00:28:09.490> an 00:28:09.570 --> 00:28:09.580 align:start position:0% any questions people free the open an 00:28:09.580 --> 00:28:15.570 align:start position:0% any questions people free the open an issue<00:28:09.730> and<00:28:10.090> we<00:28:10.540> can<00:28:10.720> gauge<00:28:12.540> to<00:28:13.540> help<00:28:14.580> folks 00:28:15.570 --> 00:28:15.580 align:start position:0% issue and we can gauge to help folks 00:28:15.580 --> 00:28:17.460 align:start position:0% issue and we can gauge to help folks understand<00:28:16.179> that<00:28:16.419> this<00:28:16.570> is<00:28:16.840> real<00:28:17.169> and<00:28:17.260> this 00:28:17.460 --> 00:28:17.470 align:start position:0% understand that this is real and this 00:28:17.470 --> 00:28:21.500 align:start position:0% understand that this is real and this works<00:28:17.940> we<00:28:18.940> did<00:28:19.330> a<00:28:19.570> live<00:28:19.929> employment 00:28:21.500 --> 00:28:21.510 align:start position:0% works we did a live employment 00:28:21.510 --> 00:28:26.630 align:start position:0% works we did a live employment they<00:28:22.250> even<00:28:23.250> measure<00:28:23.660> non-vital<00:28:24.660> so<00:28:25.169> that<00:28:25.640> all 00:28:26.630 --> 00:28:26.640 align:start position:0% they even measure non-vital so that all 00:28:26.640 --> 00:28:28.880 align:start position:0% they even measure non-vital so that all the<00:28:26.760> components<00:28:26.880> outside<00:28:27.720> will<00:28:28.110> option<00:28:28.620> is 00:28:28.880 --> 00:28:28.890 align:start position:0% the components outside will option is 00:28:28.890 --> 00:28:33.880 align:start position:0% the components outside will option is void<00:28:29.309> of<00:28:29.610> treasure<00:28:30.059> including<00:28:31.010> the<00:28:32.010> the<00:28:32.490> SPX 00:28:33.880 --> 00:28:33.890 align:start position:0% void of treasure including the the SPX 00:28:33.890 --> 00:28:37.070 align:start position:0% void of treasure including the the SPX question<00:28:34.890> and<00:28:35.100> then<00:28:35.790> the<00:28:36.090> watching<00:28:36.510> itself<00:28:36.900> is 00:28:37.070 --> 00:28:37.080 align:start position:0% question and then the watching itself is 00:28:37.080 --> 00:28:40.100 align:start position:0% question and then the watching itself is this<00:28:37.830> managed<00:28:38.280> by<00:28:38.490> divider<00:28:38.820> which<00:28:39.600> is<00:28:39.750> also<00:28:39.960> a 00:28:40.100 --> 00:28:40.110 align:start position:0% this managed by divider which is also a 00:28:40.110 --> 00:28:44.120 align:start position:0% this managed by divider which is also a measure<00:28:40.470> and<00:28:41.330> then<00:28:42.500> if<00:28:43.500> you<00:28:43.650> want<00:28:43.799> to<00:28:43.890> try<00:28:44.070> this 00:28:44.120 --> 00:28:44.130 align:start position:0% measure and then if you want to try this 00:28:44.130 --> 00:28:46.690 align:start position:0% measure and then if you want to try this yourself<00:28:44.250> right<00:28:44.880> how<00:28:45.660> these<00:28:46.169> different 00:28:46.690 --> 00:28:46.700 align:start position:0% yourself right how these different 00:28:46.700 --> 00:28:51.080 align:start position:0% yourself right how these different together<00:28:48.500> we<00:28:49.500> also<00:28:49.679> created<00:28:50.220> you<00:28:50.549> created<00:28:50.700> a 00:28:51.080 --> 00:28:51.090 align:start position:0% together we also created you created a 00:28:51.090 --> 00:28:52.850 align:start position:0% together we also created you created a local<00:28:51.419> environment<00:28:51.809> that's<00:28:52.350> based<00:28:52.679> on 00:28:52.850 --> 00:28:52.860 align:start position:0% local environment that's based on 00:28:52.860 --> 00:28:56.810 align:start position:0% local environment that's based on Windows<00:28:53.960> so<00:28:54.960> just<00:28:55.320> following<00:28:55.740> that<00:28:56.400> we<00:28:56.549> move 00:28:56.810 --> 00:28:56.820 align:start position:0% Windows so just following that we move 00:28:56.820 --> 00:28:59.480 align:start position:0% Windows so just following that we move and<00:28:57.270> you<00:28:57.510> can<00:28:57.690> try<00:28:58.440> this<00:28:58.500> yourself<00:28:58.679> and<00:28:59.250> run 00:28:59.480 --> 00:28:59.490 align:start position:0% and you can try this yourself and run 00:28:59.490 --> 00:29:02.630 align:start position:0% and you can try this yourself and run everything<00:28:59.910> and<00:29:00.210> went<00:29:00.480> without<00:29:01.140> relying<00:29:01.740> on 00:29:02.630 --> 00:29:02.640 align:start position:0% everything and went without relying on 00:29:02.640 --> 00:29:06.700 align:start position:0% everything and went without relying on the<00:29:03.360> opponent<00:29:04.220> so<00:29:05.220> that's<00:29:05.549> why<00:29:05.850> I'm<00:29:05.940> trying<00:29:06.179> to 00:29:06.700 --> 00:29:06.710 align:start position:0% the opponent so that's why I'm trying to 00:29:06.710 --> 00:29:09.440 align:start position:0% the opponent so that's why I'm trying to take<00:29:07.710> you<00:29:07.890> through<00:29:08.250> in<00:29:08.580> the<00:29:08.700> next<00:29:09.090> I<00:29:09.360> don't 00:29:09.440 --> 00:29:09.450 align:start position:0% take you through in the next I don't 00:29:09.450 --> 00:29:14.150 align:start position:0% take you through in the next I don't know<00:29:09.690> of<00:29:10.590> way<00:29:11.179> 15<00:29:12.179> to<00:29:12.330> 20<00:29:12.630> minutes<00:29:12.900> of<00:29:13.169> stepping 00:29:14.150 --> 00:29:14.160 align:start position:0% know of way 15 to 20 minutes of stepping 00:29:14.160 --> 00:29:15.470 align:start position:0% know of way 15 to 20 minutes of stepping through<00:29:14.250> all<00:29:14.549> the<00:29:14.640> different<00:29:14.820> components<00:29:15.419> so 00:29:15.470 --> 00:29:15.480 align:start position:0% through all the different components so 00:29:15.480 --> 00:29:17.750 align:start position:0% through all the different components so you<00:29:15.510> can<00:29:15.750> see<00:29:15.960> this<00:29:16.290> thing<00:29:16.530> running<00:29:16.830> at<00:29:17.610> the 00:29:17.750 --> 00:29:17.760 align:start position:0% you can see this thing running at the 00:29:17.760 --> 00:29:24.080 align:start position:0% you can see this thing running at the end<00:29:18.799> and<00:29:19.799> let's<00:29:20.160> get<00:29:20.490> to<00:29:20.640> that<00:29:20.790> now<00:29:23.090> any 00:29:24.080 --> 00:29:24.090 align:start position:0% end and let's get to that now any 00:29:24.090 --> 00:29:28.540 align:start position:0% end and let's get to that now any questions<00:29:24.660> so<00:29:25.080> far<00:29:25.110> about<00:29:25.740> a<00:29:26.160> user<00:29:26.640> stuff 00:29:28.540 --> 00:29:28.550 align:start position:0% questions so far about a user stuff 00:29:28.550 --> 00:29:35.510 align:start position:0% questions so far about a user stuff [Music] 00:29:35.510 --> 00:29:35.520 align:start position:0% 00:29:35.520 --> 00:29:39.120 align:start position:0% what<00:29:36.520> up<00:29:36.730> testes<00:29:37.150> get<00:29:37.330> coins<00:29:37.860> deploy 00:29:39.120 --> 00:29:39.130 align:start position:0% what up testes get coins deploy 00:29:39.130 --> 00:29:41.810 align:start position:0% what up testes get coins deploy what<00:29:39.460> does<00:29:39.760> get<00:29:40.120> coin<00:29:40.510> oh<00:29:40.539> yeah<00:29:40.870> if<00:29:41.110> somebody 00:29:41.810 --> 00:29:41.820 align:start position:0% what does get coin oh yeah if somebody 00:29:41.820 --> 00:29:44.700 align:start position:0% what does get coin oh yeah if somebody anybody<00:29:42.820> aces<00:29:43.360> is<00:29:43.600> welcome<00:29:44.200> to<00:29:44.380> create<00:29:44.650> a 00:29:44.700 --> 00:29:44.710 align:start position:0% anybody aces is welcome to create a 00:29:44.710 --> 00:29:48.180 align:start position:0% anybody aces is welcome to create a bunker<00:29:45.100> project<00:29:45.580> and<00:29:45.850> see<00:29:46.090> how<00:29:46.660> we<00:29:47.559> improve<00:29:47.919> on 00:29:48.180 --> 00:29:48.190 align:start position:0% bunker project and see how we improve on 00:29:48.190 --> 00:29:50.130 align:start position:0% bunker project and see how we improve on how<00:29:48.340> about<00:29:48.490> this<00:29:48.669> right<00:29:48.940> what<00:29:49.240> we've<00:29:49.450> done<00:29:49.840> is 00:29:50.130 --> 00:29:50.140 align:start position:0% how about this right what we've done is 00:29:50.140 --> 00:29:53.010 align:start position:0% how about this right what we've done is one<00:29:50.530> pattern<00:29:50.799> against<00:29:51.400> one<00:29:51.880> thing<00:29:52.120> you<00:29:52.720> can<00:29:52.870> do 00:29:53.010 --> 00:29:53.020 align:start position:0% one pattern against one thing you can do 00:29:53.020 --> 00:29:54.990 align:start position:0% one pattern against one thing you can do with<00:29:53.169> TCS<00:29:53.530> and<00:29:53.679> there's<00:29:54.039> you<00:29:54.669> know<00:29:54.730> other 00:29:54.990 --> 00:29:55.000 align:start position:0% with TCS and there's you know other 00:29:55.000 --> 00:29:56.520 align:start position:0% with TCS and there's you know other other<00:29:55.330> patterns<00:29:55.990> you<00:29:56.140> can<00:29:56.230> use<00:29:56.350> on<00:29:56.500> that 00:29:56.520 --> 00:29:56.530 align:start position:0% other patterns you can use on that 00:29:56.530 --> 00:29:59.060 align:start position:0% other patterns you can use on that that's<00:29:57.250> a<00:29:57.340> great<00:29:57.429> idea 00:29:59.060 --> 00:29:59.070 align:start position:0% that's a great idea 00:29:59.070 --> 00:30:04.590 align:start position:0% that's a great idea alright<00:30:00.070> so<00:30:02.070> before<00:30:03.070> I<00:30:03.250> go<00:30:03.460> to<00:30:03.520> the<00:30:03.789> code<00:30:04.000> this 00:30:04.590 --> 00:30:04.600 align:start position:0% alright so before I go to the code this 00:30:04.600 --> 00:30:08.430 align:start position:0% alright so before I go to the code this is<00:30:04.870> one<00:30:05.080> of<00:30:05.610> the<00:30:06.610> simpler<00:30:06.970> simplified<00:30:07.870> version 00:30:08.430 --> 00:30:08.440 align:start position:0% is one of the simpler simplified version 00:30:08.440 --> 00:30:10.260 align:start position:0% is one of the simpler simplified version of<00:30:08.710> the<00:30:08.950> mobile<00:30:09.190> environment<00:30:09.280> compared<00:30:10.120> to 00:30:10.260 --> 00:30:10.270 align:start position:0% of the mobile environment compared to 00:30:10.270 --> 00:30:11.789 align:start position:0% of the mobile environment compared to the<00:30:10.360> real<00:30:10.570> version<00:30:11.020> that's<00:30:11.169> the<00:30:11.350> points<00:30:11.679> of 00:30:11.789 --> 00:30:11.799 align:start position:0% the real version that's the points of 00:30:11.799 --> 00:30:14.870 align:start position:0% the real version that's the points of the<00:30:11.860> cloud<00:30:12.039> we<00:30:13.030> have<00:30:13.059> these<00:30:13.330> components<00:30:13.929> that 00:30:14.870 --> 00:30:14.880 align:start position:0% the cloud we have these components that 00:30:14.880 --> 00:30:21.620 align:start position:0% the cloud we have these components that well<00:30:15.880> so<00:30:16.809> how<00:30:17.970> the<00:30:19.080> the<00:30:20.080> heart<00:30:21.070> of<00:30:21.250> the 00:30:21.620 --> 00:30:21.630 align:start position:0% well so how the the heart of the 00:30:21.630 --> 00:30:24.930 align:start position:0% well so how the the heart of the security<00:30:22.630> component<00:30:22.990> is<00:30:23.679> a<00:30:24.100> secure<00:30:24.520> channel 00:30:24.930 --> 00:30:24.940 align:start position:0% security component is a secure channel 00:30:24.940 --> 00:30:31.220 align:start position:0% security component is a secure channel between<00:30:27.690> component<00:30:28.690> that's<00:30:28.870> owned<00:30:29.289> by<00:30:29.470> EA<00:30:30.250> and 00:30:31.220 --> 00:30:31.230 align:start position:0% between component that's owned by EA and 00:30:31.230 --> 00:30:34.100 align:start position:0% between component that's owned by EA and at<00:30:32.230> some<00:30:32.470> point<00:30:32.740> that<00:30:32.860> needs<00:30:33.220> to<00:30:33.370> call<00:30:33.700> a 00:30:34.100 --> 00:30:34.110 align:start position:0% at some point that needs to call a 00:30:34.110 --> 00:30:37.380 align:start position:0% at some point that needs to call a spitless<00:30:35.110> worker<00:30:35.770> node<00:30:36.130> that's<00:30:36.700> you<00:30:37.330> know 00:30:37.380 --> 00:30:37.390 align:start position:0% spitless worker node that's you know 00:30:37.390 --> 00:30:40.520 align:start position:0% spitless worker node that's you know conserve<00:30:37.870> anybody<00:30:38.409> so<00:30:39.070> how<00:30:39.309> does<00:30:39.370> that 00:30:40.520 --> 00:30:40.530 align:start position:0% conserve anybody so how does that 00:30:40.530 --> 00:30:42.990 align:start position:0% conserve anybody so how does that communication<00:30:41.530> have<00:30:41.740> been<00:30:41.770> securely<00:30:42.429> is 00:30:42.990 --> 00:30:43.000 align:start position:0% communication have been securely is 00:30:43.000 --> 00:30:43.940 align:start position:0% communication have been securely is through<00:30:43.330> a 00:30:43.940 --> 00:30:43.950 align:start position:0% through a 00:30:43.950 --> 00:30:46.190 align:start position:0% through a your<00:30:44.100> channel<00:30:44.400> if<00:30:45.360> you<00:30:45.570> want<00:30:45.780> to<00:30:45.870> know<00:30:45.990> any 00:30:46.190 --> 00:30:46.200 align:start position:0% your channel if you want to know any 00:30:46.200 --> 00:30:50.780 align:start position:0% your channel if you want to know any details<00:30:46.380> ask<00:30:46.980> these<00:30:47.400> guys<00:30:48.350> but<00:30:49.460> we<00:30:50.460> obviously 00:30:50.780 --> 00:30:50.790 align:start position:0% details ask these guys but we obviously 00:30:50.790 --> 00:30:53.000 align:start position:0% details ask these guys but we obviously we<00:30:51.270> don't<00:30:51.420> need<00:30:51.900> that<00:30:52.170> our<00:30:52.560> local<00:30:52.920> environment 00:30:53.000 --> 00:30:53.010 align:start position:0% we don't need that our local environment 00:30:53.010 --> 00:30:57.560 align:start position:0% we don't need that our local environment so<00:30:53.670> what<00:30:53.910> we<00:30:54.030> do<00:30:54.240> is<00:30:54.480> using<00:30:55.440> a<00:30:55.530> shared<00:30:56.570> file 00:30:57.560 --> 00:30:57.570 align:start position:0% so what we do is using a shared file 00:30:57.570 --> 00:31:00.380 align:start position:0% so what we do is using a shared file system<00:30:57.890> we<00:30:58.890> have<00:30:59.160> something<00:30:59.670> generated<00:31:00.240> by 00:31:00.380 --> 00:31:00.390 align:start position:0% system we have something generated by 00:31:00.390 --> 00:31:02.540 align:start position:0% system we have something generated by the<00:31:01.320> keyless<00:31:01.800> minitest 00:31:02.540 --> 00:31:02.550 align:start position:0% the keyless minitest 00:31:02.550 --> 00:31:05.120 align:start position:0% the keyless minitest it's<00:31:03.000> a<00:31:03.150> file<00:31:03.390> system<00:31:03.870> and<00:31:04.290> this<00:31:04.560> file<00:31:04.740> system 00:31:05.120 --> 00:31:05.130 align:start position:0% it's a file system and this file system 00:31:05.130 --> 00:31:07.730 align:start position:0% it's a file system and this file system this<00:31:05.250> is<00:31:05.610> shared<00:31:05.940> by<00:31:06.180> the<00:31:06.450> worker<00:31:06.840> node<00:31:07.020> so 00:31:07.730 --> 00:31:07.740 align:start position:0% this is shared by the worker node so 00:31:07.740 --> 00:31:10.430 align:start position:0% this is shared by the worker node so that's<00:31:07.950> how<00:31:08.220> that's<00:31:08.430> secure<00:31:09.320> provisioning<00:31:10.320> is 00:31:10.430 --> 00:31:10.440 align:start position:0% that's how that's secure provisioning is 00:31:10.440 --> 00:31:15.110 align:start position:0% that's how that's secure provisioning is not<00:31:10.620> the<00:31:10.770> community<00:31:11.280> and<00:31:11.840> then<00:31:12.840> the<00:31:14.120> watching 00:31:15.110 --> 00:31:15.120 align:start position:0% not the community and then the watching 00:31:15.120 --> 00:31:19.730 align:start position:0% not the community and then the watching itself<00:31:15.690> is<00:31:15.990> I<00:31:16.650> believe<00:31:17.340> the<00:31:17.430> best<00:31:18.140> running<00:31:19.140> all 00:31:19.730 --> 00:31:19.740 align:start position:0% itself is I believe the best running all 00:31:19.740 --> 00:31:24.930 align:start position:0% itself is I believe the best running all the<00:31:19.830> way<00:31:19.920> through<00:31:20.640> the<00:31:20.730> docker<00:31:20.910> compose<00:31:22.760> right 00:31:24.930 --> 00:31:24.940 align:start position:0% the way through the docker compose right 00:31:24.940 --> 00:31:33.440 align:start position:0% the way through the docker compose right [Music] 00:31:33.440 --> 00:31:33.450 align:start position:0% 00:31:33.450 --> 00:31:36.949 align:start position:0% if<00:31:33.959> Ray<00:31:34.229> does<00:31:34.469> not<00:31:34.859> be<00:31:35.099> any<00:31:35.609> time<00:31:35.909> if<00:31:36.179> you<00:31:36.389> see 00:31:36.949 --> 00:31:36.959 align:start position:0% if Ray does not be any time if you see 00:31:36.959 --> 00:31:38.779 align:start position:0% if Ray does not be any time if you see something<00:31:37.379> that<00:31:37.559> you<00:31:37.709> like<00:31:37.889> to<00:31:38.129> understand 00:31:38.779 --> 00:31:38.789 align:start position:0% something that you like to understand 00:31:38.789 --> 00:31:46.530 align:start position:0% something that you like to understand more<00:31:38.820> about<00:31:40.459> the<00:31:41.459> size<00:31:41.700> of<00:31:41.820> Oh 00:31:46.530 --> 00:31:46.540 align:start position:0% 00:31:46.540 --> 00:32:00.190 align:start position:0% [Music] 00:32:00.190 --> 00:32:00.200 align:start position:0% 00:32:00.200 --> 00:32:04.550 align:start position:0% okay<00:32:01.200> okay<00:32:02.100> no<00:32:02.430> is<00:32:03.390> that<00:32:03.600> good<00:32:03.810> enough<00:32:04.230> for<00:32:04.290> the 00:32:04.550 --> 00:32:04.560 align:start position:0% okay okay no is that good enough for the 00:32:04.560 --> 00:32:13.600 align:start position:0% okay okay no is that good enough for the folks<00:32:04.830> on<00:32:05.070> the<00:32:05.310> human<00:32:05.760> back<00:32:05.880> bro<00:32:07.550> ignore<00:32:08.550> this 00:32:13.600 --> 00:32:13.610 align:start position:0% 00:32:13.610 --> 00:32:21.980 align:start position:0% step<00:32:14.610> enough<00:32:15.000> what<00:32:15.870> do<00:32:15.930> you<00:32:15.990> think<00:32:20.990> alright 00:32:21.980 --> 00:32:21.990 align:start position:0% step enough what do you think alright 00:32:21.990 --> 00:32:25.060 align:start position:0% step enough what do you think alright let's<00:32:22.950> make<00:32:23.190> it<00:32:23.220> you 00:32:25.060 --> 00:32:25.070 align:start position:0% let's make it you 00:32:25.070 --> 00:32:27.680 align:start position:0% let's make it you [Music] 00:32:27.680 --> 00:32:27.690 align:start position:0% [Music] 00:32:27.690 --> 00:32:38.390 align:start position:0% [Music] there<00:32:28.140> we<00:32:28.290> go<00:32:30.320> bigger<00:32:32.240> bigger<00:32:33.800> okay<00:32:35.810> so<00:32:37.160> on<00:32:38.160> the 00:32:38.390 --> 00:32:38.400 align:start position:0% there we go bigger bigger okay so on the 00:32:38.400 --> 00:32:47.450 align:start position:0% there we go bigger bigger okay so on the beam<00:32:38.730> up<00:32:38.880> first 00:32:47.450 --> 00:32:47.460 align:start position:0% 00:32:47.460 --> 00:32:53.539 align:start position:0% all<00:32:48.460> right<00:32:49.230> by<00:32:50.230> the<00:32:50.289> way<00:32:50.500> I<00:32:50.799> mentioned<00:32:51.789> the 00:32:53.539 --> 00:32:53.549 align:start position:0% all right by the way I mentioned the 00:32:53.549 --> 00:32:59.460 align:start position:0% all right by the way I mentioned the github<00:32:55.769> so<00:32:56.769> if<00:32:57.009> you<00:32:57.159> go<00:32:57.370> to<00:32:57.899> that<00:32:58.899> github<00:32:59.320> at 00:32:59.460 --> 00:32:59.470 align:start position:0% github so if you go to that github at 00:32:59.470 --> 00:33:03.779 align:start position:0% github so if you go to that github at the<00:32:59.620> link<00:33:00.389> switch<00:33:01.389> to<00:33:01.659> dead<00:33:01.870> calm<00:33:02.490> brunch<00:33:03.490> and 00:33:03.779 --> 00:33:03.789 align:start position:0% the link switch to dead calm brunch and 00:33:03.789 --> 00:33:07.420 align:start position:0% the link switch to dead calm brunch and then<00:33:03.850> you<00:33:04.480> can<00:33:04.690> see 00:33:07.420 --> 00:33:07.430 align:start position:0% 00:33:07.430 --> 00:33:10.010 align:start position:0% [Music] 00:33:10.010 --> 00:33:10.020 align:start position:0% [Music] 00:33:10.020 --> 00:33:14.450 align:start position:0% [Music] all<00:33:10.679> right<00:33:10.770> no<00:33:11.010> no<00:33:11.070> we<00:33:11.520> don't<00:33:11.640> need<00:33:11.850> that<00:33:13.400> go<00:33:14.400> to 00:33:14.450 --> 00:33:14.460 align:start position:0% all right no no we don't need that go to 00:33:14.460 --> 00:33:16.549 align:start position:0% all right no no we don't need that go to the<00:33:14.700> death<00:33:15.240> of<00:33:15.450> brunch<00:33:15.750> and<00:33:16.020> then<00:33:16.080> go<00:33:16.320> to<00:33:16.500> the 00:33:16.549 --> 00:33:16.559 align:start position:0% the death of brunch and then go to the 00:33:16.559 --> 00:33:19.060 align:start position:0% the death of brunch and then go to the logo<00:33:16.800> folder<00:33:17.610> and<00:33:17.790> then<00:33:18.000> there's<00:33:18.240> a<00:33:18.300> weakness 00:33:19.060 --> 00:33:19.070 align:start position:0% logo folder and then there's a weakness 00:33:19.070 --> 00:33:21.770 align:start position:0% logo folder and then there's a weakness that<00:33:20.070> you<00:33:20.130> want<00:33:20.520> so<00:33:20.790> if<00:33:20.940> you<00:33:20.970> want<00:33:21.059> try<00:33:21.450> this<00:33:21.510> at 00:33:21.770 --> 00:33:21.780 align:start position:0% that you want so if you want try this at 00:33:21.780 --> 00:33:24.560 align:start position:0% that you want so if you want try this at home<00:33:21.809> you<00:33:22.020> can<00:33:22.440> you<00:33:22.620> can<00:33:22.770> do<00:33:22.860> that<00:33:23.010> oh<00:33:23.309> you<00:33:24.240> eat 00:33:24.560 --> 00:33:24.570 align:start position:0% home you can you can do that oh you eat 00:33:24.570 --> 00:33:32.120 align:start position:0% home you can you can do that oh you eat is<00:33:27.890> okay<00:33:28.890> so<00:33:29.570> what<00:33:30.570> I<00:33:30.600> thought<00:33:30.900> is<00:33:31.140> I've<00:33:31.770> got 00:33:32.120 --> 00:33:32.130 align:start position:0% is okay so what I thought is I've got 00:33:32.130 --> 00:33:35.570 align:start position:0% is okay so what I thought is I've got three<00:33:32.850> different<00:33:33.030> talking<00:33:33.720> compose<00:33:34.580> puts 00:33:35.570 --> 00:33:35.580 align:start position:0% three different talking compose puts 00:33:35.580 --> 00:33:40.190 align:start position:0% three different talking compose puts this<00:33:35.790> together<00:33:36.350> the<00:33:37.350> first<00:33:37.590> one<00:33:37.920> is<00:33:38.660> the<00:33:39.660> deep 00:33:40.190 --> 00:33:40.200 align:start position:0% this together the first one is the deep 00:33:40.200 --> 00:33:42.820 align:start position:0% this together the first one is the deep back<00:33:40.559> end<00:33:40.800> which<00:33:41.070> is<00:33:41.250> watching<00:33:41.850> itself 00:33:42.820 --> 00:33:42.830 align:start position:0% back end which is watching itself 00:33:42.830 --> 00:33:53.210 align:start position:0% back end which is watching itself it<00:33:43.830> runs<00:33:46.220> the<00:33:47.220> latest<00:33:47.370> version<00:33:51.710> for<00:33:52.710> every<00:33:53.010> bit 00:33:53.210 --> 00:33:53.220 align:start position:0% it runs the latest version for every bit 00:33:53.220 --> 00:33:56.090 align:start position:0% it runs the latest version for every bit soon<00:33:53.520> known<00:33:54.150> we<00:33:54.750> need<00:33:54.929> to<00:33:55.080> run<00:33:55.290> the<00:33:55.470> continue 00:33:56.090 --> 00:33:56.100 align:start position:0% soon known we need to run the continue 00:33:56.100 --> 00:33:59.150 align:start position:0% soon known we need to run the continue Mona's<00:33:56.940> which<00:33:57.150> is<00:33:57.650> essentially<00:33:58.650> the<00:33:58.800> wallet 00:33:59.150 --> 00:33:59.160 align:start position:0% Mona's which is essentially the wallet 00:33:59.160 --> 00:34:01.790 align:start position:0% Mona's which is essentially the wallet because<00:34:00.150> work<00:34:00.630> will<00:34:00.900> easy<00:34:01.110> we<00:34:01.410> don't<00:34:01.530> want<00:34:01.710> to 00:34:01.790 --> 00:34:01.800 align:start position:0% because work will easy we don't want to 00:34:01.800 --> 00:34:04.850 align:start position:0% because work will easy we don't want to do<00:34:01.950> external<00:34:02.520> sign<00:34:02.880> so<00:34:03.720> we<00:34:03.840> just<00:34:04.020> asked<00:34:04.380> no<00:34:04.620> to 00:34:04.850 --> 00:34:04.860 align:start position:0% do external sign so we just asked no to 00:34:04.860 --> 00:34:07.669 align:start position:0% do external sign so we just asked no to do<00:34:04.980> the<00:34:05.130> signing<00:34:05.490> for<00:34:05.700> us<00:34:05.900> and<00:34:06.900> this<00:34:07.080> is<00:34:07.260> giving 00:34:07.669 --> 00:34:07.679 align:start position:0% do the signing for us and this is giving 00:34:07.679 --> 00:34:11.210 align:start position:0% do the signing for us and this is giving the<00:34:07.920> best<00:34:08.100> you<00:34:08.540> motivate<00:34:09.540> wallet<00:34:09.990> so<00:34:10.919> that's 00:34:11.210 --> 00:34:11.220 align:start position:0% the best you motivate wallet so that's 00:34:11.220 --> 00:34:14.210 align:start position:0% the best you motivate wallet so that's what<00:34:11.429> the<00:34:11.520> assignor<00:34:12.060> does<00:34:12.210> here<00:34:12.869> and<00:34:13.320> then<00:34:13.860> we 00:34:14.210 --> 00:34:14.220 align:start position:0% what the assignor does here and then we 00:34:14.220 --> 00:34:19.970 align:start position:0% what the assignor does here and then we have<00:34:14.399> another<00:34:15.200> festive<00:34:16.200> node<00:34:16.379> and<00:34:17.310> another<00:34:18.980> so 00:34:19.970 --> 00:34:19.980 align:start position:0% have another festive node and another so 00:34:19.980 --> 00:34:22.240 align:start position:0% have another festive node and another so that's<00:34:20.129> pretty<00:34:20.399> simple<00:34:20.850> it's<00:34:21.090> Martha 00:34:22.240 --> 00:34:22.250 align:start position:0% that's pretty simple it's Martha 00:34:22.250 --> 00:34:29.510 align:start position:0% that's pretty simple it's Martha [Music] 00:34:29.510 --> 00:34:29.520 align:start position:0% 00:34:29.520 --> 00:34:34.790 align:start position:0% it's<00:34:30.149> creating<00:34:30.750> in<00:34:31.350> the<00:34:31.560> to<00:34:31.740> note<00:34:31.950> and<00:34:32.250> to<00:34:33.800> well 00:34:34.790 --> 00:34:34.800 align:start position:0% it's creating in the to note and to well 00:34:34.800 --> 00:34:38.720 align:start position:0% it's creating in the to note and to well it's<00:34:35.010> right<00:34:35.550> so<00:34:35.970> it's<00:34:36.210> all<00:34:37.429> working<00:34:38.429> fine<00:34:38.700> so 00:34:38.720 --> 00:34:38.730 align:start position:0% it's right so it's all working fine so 00:34:38.730 --> 00:34:43.820 align:start position:0% it's right so it's all working fine so far<00:34:39.270> and<00:34:40.850> you<00:34:41.850> can<00:34:42.409> connect<00:34:43.409> to<00:34:43.560> them 00:34:43.820 --> 00:34:43.830 align:start position:0% far and you can connect to them 00:34:43.830 --> 00:34:55.860 align:start position:0% far and you can connect to them [Music] 00:34:55.860 --> 00:34:55.870 align:start position:0% 00:34:55.870 --> 00:35:00.900 align:start position:0% you<00:34:56.870> can<00:34:57.080> attach<00:34:57.500> to<00:34:57.950> that 00:35:00.900 --> 00:35:00.910 align:start position:0% 00:35:00.910 --> 00:35:06.690 align:start position:0% see<00:35:01.910> that<00:35:02.150> it's<00:35:02.360> running<00:35:03.080> for<00:35:03.470> you<00:35:05.590> okay<00:35:06.590> so 00:35:06.690 --> 00:35:06.700 align:start position:0% see that it's running for you okay so 00:35:06.700 --> 00:35:08.620 align:start position:0% see that it's running for you okay so there<00:35:07.700> you<00:35:08.090> have<00:35:08.270> it 00:35:08.620 --> 00:35:08.630 align:start position:0% there you have it 00:35:08.630 --> 00:35:11.050 align:start position:0% there you have it we<00:35:09.290> were<00:35:09.530> even<00:35:09.830> come<00:35:10.010> so<00:35:10.220> we<00:35:10.370> can<00:35:10.550> see<00:35:10.790> that 00:35:11.050 --> 00:35:11.060 align:start position:0% we were even come so we can see that 00:35:11.060 --> 00:35:13.720 align:start position:0% we were even come so we can see that it's<00:35:11.420> it's<00:35:11.690> already<00:35:12.050> that<00:35:12.200> block<00:35:12.560> 14<00:35:13.250> thousand 00:35:13.720 --> 00:35:13.730 align:start position:0% it's it's already that block 14 thousand 00:35:13.730 --> 00:35:15.670 align:start position:0% it's it's already that block 14 thousand something<00:35:14.150> because<00:35:14.540> I've<00:35:14.990> been<00:35:15.170> running<00:35:15.560> this 00:35:15.670 --> 00:35:15.680 align:start position:0% something because I've been running this 00:35:15.680 --> 00:35:17.620 align:start position:0% something because I've been running this apartment<00:35:16.160> for<00:35:16.280> a<00:35:16.340> while<00:35:16.520> that's<00:35:17.300> why<00:35:17.480> it's 00:35:17.620 --> 00:35:17.630 align:start position:0% apartment for a while that's why it's 00:35:17.630 --> 00:35:21.730 align:start position:0% apartment for a while that's why it's got<00:35:17.810> a<00:35:18.050> bunch<00:35:18.200> of<00:35:18.320> blocks<00:35:18.530> ready<00:35:20.170> so<00:35:21.170> now<00:35:21.200> we 00:35:21.730 --> 00:35:21.740 align:start position:0% got a bunch of blocks ready so now we 00:35:21.740 --> 00:35:25.170 align:start position:0% got a bunch of blocks ready so now we have<00:35:21.920> the<00:35:22.040> back<00:35:22.190> end<00:35:22.430> let's<00:35:23.030> burn<00:35:23.720> up<00:35:23.840> the 00:35:25.170 --> 00:35:25.180 align:start position:0% have the back end let's burn up the 00:35:25.180 --> 00:35:27.400 align:start position:0% have the back end let's burn up the contract<00:35:26.180> so<00:35:26.450> I<00:35:26.630> wear<00:35:26.930> it<00:35:27.020> before<00:35:27.110> the 00:35:27.400 --> 00:35:27.410 align:start position:0% contract so I wear it before the 00:35:27.410 --> 00:35:31.060 align:start position:0% contract so I wear it before the contract<00:35:27.890> so<00:35:28.040> I'm<00:35:28.600> nothing<00:35:29.600> but<00:35:29.630> again<00:35:30.110> but<00:35:30.950> in 00:35:31.060 --> 00:35:31.070 align:start position:0% contract so I'm nothing but again but in 00:35:31.070 --> 00:35:42.140 align:start position:0% contract so I'm nothing but again but in what<00:35:31.520> it<00:35:31.610> does<00:35:31.910> is 00:35:42.140 --> 00:35:42.150 align:start position:0% 00:35:42.150 --> 00:35:45.510 align:start position:0% yeah<00:35:43.150> that's<00:35:43.630> available<00:35:44.010> and<00:35:45.010> it<00:35:45.190> won't<00:35:45.370> get 00:35:45.510 --> 00:35:45.520 align:start position:0% yeah that's available and it won't get 00:35:45.520 --> 00:35:51.210 align:start position:0% yeah that's available and it won't get really<00:35:47.430> so<00:35:48.430> there<00:35:48.700> are<00:35:48.820> these<00:35:49.890> one<00:35:50.890> two<00:35:51.040> three 00:35:51.210 --> 00:35:51.220 align:start position:0% really so there are these one two three 00:35:51.220 --> 00:35:54.510 align:start position:0% really so there are these one two three ten<00:35:51.670> different<00:35:52.180> smart<00:35:52.990> contracts<00:35:53.530> that<00:35:53.800> gives 00:35:54.510 --> 00:35:54.520 align:start position:0% ten different smart contracts that gives 00:35:54.520 --> 00:35:57.090 align:start position:0% ten different smart contracts that gives you<00:35:54.640> a<00:35:54.670> registry<00:35:55.300> that<00:35:56.110> gives<00:35:56.350> you<00:35:56.530> a<00:35:56.560> registry 00:35:57.090 --> 00:35:57.100 align:start position:0% you a registry that gives you a registry 00:35:57.100 --> 00:36:01.020 align:start position:0% you a registry that gives you a registry of<00:35:57.160> the<00:35:57.610> works<00:35:57.940> so<00:35:58.780> when<00:35:59.020> when<00:35:59.500> a<00:35:59.830> request<00:36:00.340> goes 00:36:01.020 --> 00:36:01.030 align:start position:0% of the works so when when a request goes 00:36:01.030 --> 00:36:04.620 align:start position:0% of the works so when when a request goes to<00:36:01.740> the<00:36:02.740> smart<00:36:03.040> contracts<00:36:03.430> to<00:36:03.610> issue<00:36:03.820> a<00:36:04.240> token 00:36:04.620 --> 00:36:04.630 align:start position:0% to the smart contracts to issue a token 00:36:04.630 --> 00:36:06.990 align:start position:0% to the smart contracts to issue a token to<00:36:04.660> the<00:36:04.780> Lord<00:36:05.050> it's<00:36:05.710> using<00:36:06.100> registry<00:36:06.580> to 00:36:06.990 --> 00:36:07.000 align:start position:0% to the Lord it's using registry to 00:36:07.000 --> 00:36:09.030 align:start position:0% to the Lord it's using registry to verify<00:36:07.420> that<00:36:07.450> this<00:36:07.810> works<00:36:08.140> has<00:36:08.800> been 00:36:09.030 --> 00:36:09.040 align:start position:0% verify that this works has been 00:36:09.040 --> 00:36:11.820 align:start position:0% verify that this works has been registered<00:36:09.580> and<00:36:09.930> then<00:36:10.930> when<00:36:11.410> you<00:36:11.530> want<00:36:11.770> to 00:36:11.820 --> 00:36:11.830 align:start position:0% registered and then when you want to 00:36:11.830 --> 00:36:15.330 align:start position:0% registered and then when you want to issue<00:36:12.010> to<00:36:12.610> our<00:36:12.760> employee<00:36:13.210> then<00:36:14.170> the<00:36:14.650> claims 00:36:15.330 --> 00:36:15.340 align:start position:0% issue to our employee then the claims 00:36:15.340 --> 00:36:19.800 align:start position:0% issue to our employee then the claims reader<00:36:15.880> registry<00:36:16.630> is<00:36:16.960> as<00:36:17.830> well<00:36:18.760> as<00:36:19.120> used<00:36:19.450> to 00:36:19.800 --> 00:36:19.810 align:start position:0% reader registry is as well as used to 00:36:19.810 --> 00:36:22.380 align:start position:0% reader registry is as well as used to verify<00:36:20.590> that<00:36:20.620> there's<00:36:21.040> a<00:36:21.100> claim<00:36:21.460> about<00:36:22.030> the 00:36:22.380 --> 00:36:22.390 align:start position:0% verify that there's a claim about the 00:36:22.390 --> 00:36:24.540 align:start position:0% verify that there's a claim about the association's<00:36:23.140> of<00:36:23.410> employees<00:36:24.220> without 00:36:24.540 --> 00:36:24.550 align:start position:0% association's of employees without 00:36:24.550 --> 00:36:26.730 align:start position:0% association's of employees without information<00:36:25.050> so<00:36:26.050> that's<00:36:26.290> how<00:36:26.530> these<00:36:26.680> things 00:36:26.730 --> 00:36:26.740 align:start position:0% information so that's how these things 00:36:26.740 --> 00:36:29.790 align:start position:0% information so that's how these things work<00:36:27.220> and<00:36:27.430> then<00:36:27.550> the<00:36:28.090> main<00:36:28.360> logic<00:36:29.290> of 00:36:29.790 --> 00:36:29.800 align:start position:0% work and then the main logic of 00:36:29.800 --> 00:36:33.540 align:start position:0% work and then the main logic of processing<00:36:30.760> the<00:36:31.420> issue<00:36:31.630> the<00:36:32.110> burn<00:36:32.830> of<00:36:33.100> the 00:36:33.540 --> 00:36:33.550 align:start position:0% processing the issue the burn of the 00:36:33.550 --> 00:36:35.880 align:start position:0% processing the issue the burn of the tokens<00:36:34.120> is<00:36:34.420> operator<00:36:34.960> so<00:36:35.410> that's<00:36:35.590> the<00:36:35.710> main 00:36:35.880 --> 00:36:35.890 align:start position:0% tokens is operator so that's the main 00:36:35.890 --> 00:36:39.650 align:start position:0% tokens is operator so that's the main thing<00:36:35.920> or<00:36:36.280> the<00:36:36.460> logics<00:36:36.850> exist 00:36:39.650 --> 00:36:39.660 align:start position:0% thing or the logics exist 00:36:39.660 --> 00:36:42.930 align:start position:0% thing or the logics exist and<00:36:40.660> you<00:36:40.840> have<00:36:41.020> the<00:36:41.230> different<00:36:42.010> token 00:36:42.930 --> 00:36:42.940 align:start position:0% and you have the different token 00:36:42.940 --> 00:36:45.570 align:start position:0% and you have the different token contracts<00:36:43.870> undercover<00:36:44.830> they<00:36:45.040> are<00:36:45.100> all<00:36:45.310> based 00:36:45.570 --> 00:36:45.580 align:start position:0% contracts undercover they are all based 00:36:45.580 --> 00:36:51.750 align:start position:0% contracts undercover they are all based on<00:36:45.850> GRC<00:36:46.830> 777<00:36:47.830> advice<00:36:48.550> of<00:36:48.940> GRC<00:36:50.100> 20<00:36:51.100> that<00:36:51.370> setting 00:36:51.750 --> 00:36:51.760 align:start position:0% on GRC 777 advice of GRC 20 that setting 00:36:51.760 --> 00:36:55.070 align:start position:0% on GRC 777 advice of GRC 20 that setting proof<00:36:52.060> version<00:36:52.420> of<00:36:52.870> GRC<00:36:53.140> 24:9<00:36:54.040> performance 00:36:55.070 --> 00:36:55.080 align:start position:0% proof version of GRC 24:9 performance 00:36:55.080 --> 00:36:59.400 align:start position:0% proof version of GRC 24:9 performance for<00:36:56.080> fungible<00:36:56.560> opens<00:36:57.840> so<00:36:58.840> that's<00:36:59.200> been 00:36:59.400 --> 00:36:59.410 align:start position:0% for fungible opens so that's been 00:36:59.410 --> 00:37:03.570 align:start position:0% for fungible opens so that's been deployed<00:36:59.760> let's<00:37:01.470> start<00:37:02.470> the<00:37:02.860> middle<00:37:03.400> tier 00:37:03.570 --> 00:37:03.580 align:start position:0% deployed let's start the middle tier 00:37:03.580 --> 00:37:15.090 align:start position:0% deployed let's start the middle tier which<00:37:03.910> is<00:37:03.940> the<00:37:04.240> tea<00:37:04.870> stuff<00:37:06.090> so<00:37:07.090> we<00:37:07.240> have 00:37:15.090 --> 00:37:15.100 align:start position:0% 00:37:15.100 --> 00:37:21.760 align:start position:0% [Music] 00:37:21.760 --> 00:37:21.770 align:start position:0% 00:37:21.770 --> 00:37:26.020 align:start position:0% and<00:37:22.040> so<00:37:22.369> what<00:37:23.119> this<00:37:23.240> does<00:37:23.300> is<00:37:23.780> it<00:37:24.140> gives<00:37:24.410> a<00:37:25.310> P<00:37:25.820> is 00:37:26.020 --> 00:37:26.030 align:start position:0% and so what this does is it gives a P is 00:37:26.030 --> 00:37:29.980 align:start position:0% and so what this does is it gives a P is for<00:37:26.869> the<00:37:26.990> UI<00:37:27.350> to<00:37:27.530> call<00:37:28.000> and<00:37:29.000> then<00:37:29.180> process<00:37:29.690> with 00:37:29.980 --> 00:37:29.990 align:start position:0% for the UI to call and then process with 00:37:29.990 --> 00:37:33.460 align:start position:0% for the UI to call and then process with license<00:37:31.030> so<00:37:32.030> this<00:37:32.330> only<00:37:32.510> needs<00:37:33.230> minimum 00:37:33.460 --> 00:37:33.470 align:start position:0% license so this only needs minimum 00:37:33.470 --> 00:37:36.760 align:start position:0% license so this only needs minimum component<00:37:34.340> one<00:37:35.000> doctor<00:37:35.540> Easton's<00:37:36.380> because 00:37:36.760 --> 00:37:36.770 align:start position:0% component one doctor Easton's because 00:37:36.770 --> 00:37:39.550 align:start position:0% component one doctor Easton's because that<00:37:37.220> the<00:37:37.340> actual<00:37:37.730> work<00:37:37.940> Mandela's<00:37:38.510> are<00:37:38.750> spun 00:37:39.550 --> 00:37:39.560 align:start position:0% that the actual work Mandela's are spun 00:37:39.560 --> 00:37:42.340 align:start position:0% that the actual work Mandela's are spun up<00:37:39.740> by<00:37:40.190> this<00:37:40.540> on-demand<00:37:41.540> when<00:37:42.110> there's<00:37:42.290> a 00:37:42.340 --> 00:37:42.350 align:start position:0% up by this on-demand when there's a 00:37:42.350 --> 00:37:44.710 align:start position:0% up by this on-demand when there's a worked<00:37:42.560> up<00:37:42.710> when<00:37:43.040> there's<00:37:43.250> a<00:37:43.340> work<00:37:43.790> request<00:37:44.180> it 00:37:44.710 --> 00:37:44.720 align:start position:0% worked up when there's a work request it 00:37:44.720 --> 00:37:47.050 align:start position:0% worked up when there's a work request it spins<00:37:45.020> up<00:37:45.170> a<00:37:45.290> new<00:37:45.440> instance<00:37:45.619> of<00:37:46.130> working 00:37:47.050 --> 00:37:47.060 align:start position:0% spins up a new instance of working 00:37:47.060 --> 00:37:49.300 align:start position:0% spins up a new instance of working though<00:37:47.210> than<00:37:47.450> that<00:37:47.660> heaven<00:37:48.440> as<00:37:48.770> I<00:37:48.800> said<00:37:49.100> and 00:37:49.300 --> 00:37:49.310 align:start position:0% though than that heaven as I said and 00:37:49.310 --> 00:37:53.400 align:start position:0% though than that heaven as I said and then<00:37:49.460> clean<00:37:50.000> it<00:37:50.030> up<00:37:50.360> upwards<00:37:51.550> thought<00:37:52.550> that 00:37:53.400 --> 00:37:53.410 align:start position:0% then clean it up upwards thought that 00:37:53.410 --> 00:38:11.230 align:start position:0% then clean it up upwards thought that finally<00:37:54.410> let's<00:37:54.800> put<00:37:55.490> the<00:37:55.610> new<00:37:55.760> why 00:38:11.230 --> 00:38:11.240 align:start position:0% 00:38:11.240 --> 00:38:13.990 align:start position:0% the<00:38:11.570> UI<00:38:11.780> has<00:38:12.140> four<00:38:12.470> different<00:38:12.650> coupons<00:38:13.190> it's 00:38:13.990 --> 00:38:14.000 align:start position:0% the UI has four different coupons it's 00:38:14.000 --> 00:38:17.590 align:start position:0% the UI has four different coupons it's about<00:38:14.180> the<00:38:14.480> the<00:38:14.840> HTML<00:38:15.380> layer<00:38:15.650> the<00:38:16.180> Becca<00:38:17.180> layer 00:38:17.590 --> 00:38:17.600 align:start position:0% about the the HTML layer the Becca layer 00:38:17.600 --> 00:38:21.910 align:start position:0% about the the HTML layer the Becca layer in<00:38:18.380> node.js<00:38:18.710> and<00:38:20.710> nginx 00:38:21.910 --> 00:38:21.920 align:start position:0% in node.js and nginx 00:38:21.920 --> 00:38:25.600 align:start position:0% in node.js and nginx for<00:38:22.700> load<00:38:22.910> balancing<00:38:23.090> and<00:38:24.070> database<00:38:25.070> to<00:38:25.340> save 00:38:25.600 --> 00:38:25.610 align:start position:0% for load balancing and database to save 00:38:25.610 --> 00:38:29.140 align:start position:0% for load balancing and database to save both<00:38:26.330> information<00:38:27.370> so<00:38:28.370> we've<00:38:28.580> got<00:38:28.790> everything 00:38:29.140 --> 00:38:29.150 align:start position:0% both information so we've got everything 00:38:29.150 --> 00:38:37.040 align:start position:0% both information so we've got everything running<00:38:29.690> now<00:38:29.810> let's<00:38:30.200> look<00:38:30.470> at<00:38:30.620> the<00:38:30.800> UI 00:38:37.040 --> 00:38:37.050 align:start position:0% 00:38:37.050 --> 00:38:43.180 align:start position:0% and<00:38:37.620> so<00:38:39.170> you<00:38:40.170> need<00:38:41.130> to<00:38:41.280> do<00:38:41.460> a<00:38:41.700> login<00:38:42.150> so<00:38:42.750> that's 00:38:43.180 --> 00:38:43.190 align:start position:0% and so you need to do a login so that's 00:38:43.190 --> 00:38:48.980 align:start position:0% and so you need to do a login so that's the<00:38:44.190> default<00:38:44.670> is<00:38:44.910> admin<00:38:46.610> PWD<00:38:47.610> so<00:38:48.450> that's<00:38:48.720> the 00:38:48.980 --> 00:38:48.990 align:start position:0% the default is admin PWD so that's the 00:38:48.990 --> 00:38:53.240 align:start position:0% the default is admin PWD so that's the when<00:38:49.860> you<00:38:49.980> try<00:38:50.220> this<00:38:50.280> yourself<00:38:50.550> a<00:38:51.290> at<00:38:52.290> the<00:38:52.560> PWD 00:38:53.240 --> 00:38:53.250 align:start position:0% when you try this yourself a at the PWD 00:38:53.250 --> 00:39:11.770 align:start position:0% when you try this yourself a at the PWD with<00:38:53.490> the<00:38:53.640> capitalized<00:38:54.270> P<00:38:54.720> is<00:38:54.990> the<00:38:55.260> password 00:39:11.770 --> 00:39:11.780 align:start position:0% 00:39:11.780 --> 00:39:28.820 align:start position:0% so<00:39:12.780> the 00:39:28.820 --> 00:39:28.830 align:start position:0% 00:39:28.830 --> 00:39:36.700 align:start position:0% [Music] 00:39:36.700 --> 00:39:36.710 align:start position:0% 00:39:36.710 --> 00:39:39.790 align:start position:0% all<00:39:37.190> right<00:39:37.280> this<00:39:37.880> password<00:39:38.420> so<00:39:39.200> this<00:39:39.440> is<00:39:39.589> going 00:39:39.790 --> 00:39:39.800 align:start position:0% all right this password so this is going 00:39:39.800 --> 00:39:46.059 align:start position:0% all right this password so this is going to<00:39:40.069> call<00:39:40.400> the<00:39:43.030> D<00:39:44.030> ID<00:39:44.240> registering<00:39:44.990> to<00:39:45.290> register 00:39:46.059 --> 00:39:46.069 align:start position:0% to call the D ID registering to register 00:39:46.069 --> 00:39:54.290 align:start position:0% to call the D ID registering to register this<00:39:46.720> new<00:39:47.720> member<00:39:48.230> with<00:39:49.069> a 00:39:54.290 --> 00:39:54.300 align:start position:0% 00:39:54.300 --> 00:39:58.830 align:start position:0% in 00:39:58.830 --> 00:39:58.840 align:start position:0% 00:39:58.840 --> 00:40:01.799 align:start position:0% this<00:39:59.580> sucks 00:40:01.799 --> 00:40:01.809 align:start position:0% this sucks 00:40:01.809 --> 00:40:12.800 align:start position:0% this sucks take<00:40:02.109> a<00:40:02.140> look 00:40:12.800 --> 00:40:12.810 align:start position:0% 00:40:12.810 --> 00:40:15.089 align:start position:0% [Music] 00:40:15.089 --> 00:40:15.099 align:start position:0% [Music] 00:40:15.099 --> 00:40:18.130 align:start position:0% [Music] so<00:40:15.729> it<00:40:15.849> goes<00:40:16.269> to<00:40:16.449> call 00:40:18.130 --> 00:40:18.140 align:start position:0% so it goes to call 00:40:18.140 --> 00:40:23.740 align:start position:0% so it goes to call oh<00:40:18.170> I<00:40:18.980> know<00:40:19.069> what 00:40:23.740 --> 00:40:23.750 align:start position:0% 00:40:23.750 --> 00:40:28.740 align:start position:0% I'm<00:40:24.410> using<00:40:24.740> the<00:40:25.069> wrong<00:40:25.310> branch 00:40:28.740 --> 00:40:28.750 align:start position:0% 00:40:28.750 --> 00:40:30.130 align:start position:0% [Music] 00:40:30.130 --> 00:40:30.140 align:start position:0% [Music] 00:40:30.140 --> 00:40:34.370 align:start position:0% [Music] yeah<00:40:30.589> I<00:40:30.619> need<00:40:31.039> a<00:40:31.069> switch<00:40:31.489> to 00:40:34.370 --> 00:40:34.380 align:start position:0% 00:40:34.380 --> 00:40:37.200 align:start position:0% remember<00:40:34.950> to<00:40:35.100> use<00:40:35.130> that<00:40:35.490> on<00:40:35.730> branch 00:40:37.200 --> 00:40:37.210 align:start position:0% remember to use that on branch 00:40:37.210 --> 00:40:39.790 align:start position:0% remember to use that on branch this 00:40:39.790 --> 00:40:39.800 align:start position:0% 00:40:39.800 --> 00:40:46.450 align:start position:0% [Music] 00:40:46.450 --> 00:40:46.460 align:start position:0% 00:40:46.460 --> 00:40:51.109 align:start position:0% so<00:40:46.880> we<00:40:47.089> need<00:40:47.300> to 00:40:51.109 --> 00:40:51.119 align:start position:0% 00:40:51.119 --> 00:40:54.339 align:start position:0% we 00:40:54.339 --> 00:40:54.349 align:start position:0% 00:40:54.349 --> 00:41:01.070 align:start position:0% we<00:40:54.890> build<00:40:55.189> the<00:40:55.519> middle<00:40:56.150> tier<00:40:56.479> and<00:40:56.509> UI<00:40:57.499> tier 00:41:01.070 --> 00:41:01.080 align:start position:0% 00:41:01.080 --> 00:41:05.900 align:start position:0% there<00:41:01.650> was<00:41:01.830> the 00:41:05.900 --> 00:41:05.910 align:start position:0% 00:41:05.910 --> 00:41:08.630 align:start position:0% [Music] 00:41:08.630 --> 00:41:08.640 align:start position:0% [Music] 00:41:08.640 --> 00:41:12.860 align:start position:0% [Music] all<00:41:09.150> right<00:41:09.660> so<00:41:09.990> that's<00:41:10.250> three<00:41:11.250> bills<00:41:11.870> you 00:41:12.860 --> 00:41:12.870 align:start position:0% all right so that's three bills you 00:41:12.870 --> 00:41:16.800 align:start position:0% all right so that's three bills you restart<00:41:13.410> the<00:41:13.440> UI<00:41:13.830> as<00:41:14.010> well 00:41:16.800 --> 00:41:16.810 align:start position:0% 00:41:16.810 --> 00:41:27.890 align:start position:0% [Music] 00:41:27.890 --> 00:41:27.900 align:start position:0% 00:41:27.900 --> 00:41:31.010 align:start position:0% I<00:41:28.430> needed<00:41:29.430> to<00:41:29.550> do<00:41:29.700> this<00:41:29.730> because<00:41:30.119> early<00:41:30.630> I<00:41:30.660> was 00:41:31.010 --> 00:41:31.020 align:start position:0% I needed to do this because early I was 00:41:31.020 --> 00:41:33.109 align:start position:0% I needed to do this because early I was trying<00:41:31.650> to<00:41:31.680> connect<00:41:32.040> the<00:41:32.160> system<00:41:32.369> to<00:41:32.730> a<00:41:32.760> cloud 00:41:33.109 --> 00:41:33.119 align:start position:0% trying to connect the system to a cloud 00:41:33.119 --> 00:41:35.750 align:start position:0% trying to connect the system to a cloud deployment<00:41:33.839> that's<00:41:34.560> obviously<00:41:35.130> not<00:41:35.490> the 00:41:35.750 --> 00:41:35.760 align:start position:0% deployment that's obviously not the 00:41:35.760 --> 00:41:41.049 align:start position:0% deployment that's obviously not the right<00:41:35.900> operation<00:41:38.330> right 00:41:41.049 --> 00:41:41.059 align:start position:0% right operation right 00:41:41.059 --> 00:41:48.890 align:start position:0% right operation right remind<00:41:41.900> us<00:41:42.019> again<00:41:43.089> register 00:41:48.890 --> 00:41:48.900 align:start position:0% 00:41:48.900 --> 00:41:56.430 align:start position:0% [Music] 00:41:56.430 --> 00:41:56.440 align:start position:0% [Music] 00:41:56.440 --> 00:42:00.990 align:start position:0% [Music] okay<00:41:57.160> looks<00:41:58.060> better<00:41:58.270> so<00:41:58.770> now<00:41:59.770> we've<00:42:00.160> got<00:42:00.430> we've 00:42:00.990 --> 00:42:01.000 align:start position:0% okay looks better so now we've got we've 00:42:01.000 --> 00:42:04.350 align:start position:0% okay looks better so now we've got we've got<00:42:01.240> the<00:42:01.480> member<00:42:01.960> as<00:42:02.950> that's<00:42:03.460> part<00:42:04.000> of<00:42:04.120> this 00:42:04.350 --> 00:42:04.360 align:start position:0% got the member as that's part of this 00:42:04.360 --> 00:42:06.690 align:start position:0% got the member as that's part of this consortium<00:42:04.960> let's<00:42:05.410> say<00:42:05.590> EE<00:42:05.920> itself<00:42:06.520> is<00:42:06.670> a 00:42:06.690 --> 00:42:06.700 align:start position:0% consortium let's say EE itself is a 00:42:06.700 --> 00:42:09.060 align:start position:0% consortium let's say EE itself is a consortium<00:42:07.090> we<00:42:07.420> just<00:42:07.630> added<00:42:07.840> DEFCON<00:42:08.470> 5<00:42:08.740> as<00:42:09.040> the 00:42:09.060 --> 00:42:09.070 align:start position:0% consortium we just added DEFCON 5 as the 00:42:09.070 --> 00:42:10.470 align:start position:0% consortium we just added DEFCON 5 as the brand<00:42:09.760> new<00:42:09.910> member 00:42:10.470 --> 00:42:10.480 align:start position:0% brand new member 00:42:10.480 --> 00:42:13.350 align:start position:0% brand new member so<00:42:11.170> now<00:42:11.440> we're<00:42:11.680> gonna<00:42:11.830> ask<00:42:12.100> the<00:42:12.520> admin<00:42:12.940> of<00:42:12.970> that 00:42:13.350 --> 00:42:13.360 align:start position:0% so now we're gonna ask the admin of that 00:42:13.360 --> 00:42:22.280 align:start position:0% so now we're gonna ask the admin of that DEFCON<00:42:13.900> 5<00:42:14.610> please<00:42:18.330> login 00:42:22.280 --> 00:42:22.290 align:start position:0% 00:42:22.290 --> 00:42:30.380 align:start position:0% by<00:42:22.860> at<00:42:23.280> noon<00:42:25.850> as<00:42:26.850> invalid<00:42:27.750> zero<00:42:28.380> tokens<00:42:29.330> so<00:42:30.330> I 00:42:30.380 --> 00:42:30.390 align:start position:0% by at noon as invalid zero tokens so I 00:42:30.390 --> 00:42:32.510 align:start position:0% by at noon as invalid zero tokens so I need<00:42:30.660> to<00:42:30.810> register<00:42:30.990> some<00:42:31.500> employees<00:42:32.010> that's 00:42:32.510 --> 00:42:32.520 align:start position:0% need to register some employees that's 00:42:32.520 --> 00:42:34.250 align:start position:0% need to register some employees that's going<00:42:32.880> to<00:42:32.970> be<00:42:33.090> a<00:42:33.120> sign<00:42:33.450> that<00:42:33.810> you<00:42:33.930> can<00:42:33.960> work 00:42:34.250 --> 00:42:34.260 align:start position:0% going to be a sign that you can work 00:42:34.260 --> 00:42:36.610 align:start position:0% going to be a sign that you can work with<00:42:34.320> EEA<00:42:34.830> all<00:42:35.220> great<00:42:35.520> stuff<00:42:35.760> right<00:42:36.060> so 00:42:36.610 --> 00:42:36.620 align:start position:0% with EEA all great stuff right so 00:42:36.620 --> 00:42:41.599 align:start position:0% with EEA all great stuff right so employee 00:42:41.599 --> 00:42:41.609 align:start position:0% 00:42:41.609 --> 00:42:46.940 align:start position:0% the 00:42:46.940 --> 00:42:46.950 align:start position:0% 00:42:46.950 --> 00:42:49.670 align:start position:0% as<00:42:47.400> you<00:42:47.670> can<00:42:47.819> see<00:42:48.089> the<00:42:48.359> email<00:42:48.569> we<00:42:49.290> don't<00:42:49.500> really 00:42:49.670 --> 00:42:49.680 align:start position:0% as you can see the email we don't really 00:42:49.680 --> 00:42:54.190 align:start position:0% as you can see the email we don't really use<00:42:49.799> it<00:42:50.010> to<00:42:50.369> verify<00:42:51.829> identities<00:42:52.829> it's<00:42:53.250> just 00:42:54.190 --> 00:42:54.200 align:start position:0% use it to verify identities it's just 00:42:54.200 --> 00:42:57.849 align:start position:0% use it to verify identities it's just you<00:42:55.200> can<00:42:55.410> give<00:42:55.710> any<00:42:55.980> you<00:42:56.130> know<00:42:56.309> address 00:42:57.849 --> 00:42:57.859 align:start position:0% you can give any you know address 00:42:57.859 --> 00:42:59.979 align:start position:0% you can give any you know address all<00:42:58.430> right<00:42:58.549> so<00:42:58.819> now<00:42:59.089> we<00:42:59.150> have<00:42:59.509> a<00:42:59.539> Bingley 00:42:59.979 --> 00:42:59.989 align:start position:0% all right so now we have a Bingley 00:42:59.989 --> 00:43:03.910 align:start position:0% all right so now we have a Bingley that's<00:43:00.609> part<00:43:01.609> of<00:43:01.670> that<00:43:01.940> multiplied<00:43:02.739> let's<00:43:03.739> go 00:43:03.910 --> 00:43:03.920 align:start position:0% that's part of that multiplied let's go 00:43:03.920 --> 00:43:06.359 align:start position:0% that's part of that multiplied let's go back<00:43:04.160> and<00:43:04.459> say<00:43:04.700> you<00:43:04.999> know<00:43:05.420> in<00:43:05.869> half<00:43:06.200> a<00:43:06.289> year 00:43:06.359 --> 00:43:06.369 align:start position:0% back and say you know in half a year 00:43:06.369 --> 00:43:09.400 align:start position:0% back and say you know in half a year that<00:43:07.369> come<00:43:07.430> five<00:43:07.880> equal<00:43:08.420> you<00:43:08.599> want<00:43:08.869> has<00:43:09.170> been 00:43:09.400 --> 00:43:09.410 align:start position:0% that come five equal you want has been 00:43:09.410 --> 00:43:12.160 align:start position:0% that come five equal you want has been from<00:43:09.650> spending<00:43:10.130> all<00:43:10.489> calls<00:43:11.180> and<00:43:11.509> even<00:43:11.719> chair 00:43:12.160 --> 00:43:12.170 align:start position:0% from spending all calls and even chair 00:43:12.170 --> 00:43:12.969 align:start position:0% from spending all calls and even chair some<00:43:12.469> calls 00:43:12.969 --> 00:43:12.979 align:start position:0% some calls 00:43:12.979 --> 00:43:15.729 align:start position:0% some calls neither<00:43:13.420> contributor<00:43:14.420> to<00:43:14.630> the<00:43:14.809> next<00:43:15.140> version 00:43:15.729 --> 00:43:15.739 align:start position:0% neither contributor to the next version 00:43:15.739 --> 00:43:17.680 align:start position:0% neither contributor to the next version of<00:43:15.920> the<00:43:16.069> spec<00:43:16.339> right<00:43:16.759> so<00:43:16.969> it's<00:43:17.119> time<00:43:17.150> to<00:43:17.390> give 00:43:17.680 --> 00:43:17.690 align:start position:0% of the spec right so it's time to give 00:43:17.690 --> 00:43:23.920 align:start position:0% of the spec right so it's time to give them<00:43:17.809> some<00:43:18.200> tokens<00:43:22.150> so<00:43:23.150> they<00:43:23.299> can<00:43:23.539> have<00:43:23.779> their 00:43:23.920 --> 00:43:23.930 align:start position:0% them some tokens so they can have their 00:43:23.930 --> 00:43:29.579 align:start position:0% them some tokens so they can have their dinner<00:43:24.200> they've<00:43:24.589> been<00:43:24.769> waiting<00:43:25.099> for<00:43:25.279> waiting 00:43:29.579 --> 00:43:29.589 align:start position:0% 00:43:29.589 --> 00:43:33.180 align:start position:0% okay<00:43:30.589> so<00:43:30.650> it's<00:43:31.099> gonna<00:43:31.219> be<00:43:31.489> for<00:43:31.849> DEFCON<00:43:32.239> five 00:43:33.180 --> 00:43:33.190 align:start position:0% okay so it's gonna be for DEFCON five 00:43:33.190 --> 00:43:42.099 align:start position:0% okay so it's gonna be for DEFCON five one<00:43:34.190> because<00:43:39.579> tribution<00:43:40.869> so<00:43:41.869> what's 00:43:42.099 --> 00:43:42.109 align:start position:0% one because tribution so what's 00:43:42.109 --> 00:43:46.060 align:start position:0% one because tribution so what's happening<00:43:42.499> undercover<00:43:43.009> is 00:43:46.060 --> 00:43:46.070 align:start position:0% 00:43:46.070 --> 00:43:56.930 align:start position:0% [Music] 00:43:56.930 --> 00:43:56.940 align:start position:0% 00:43:56.940 --> 00:44:01.600 align:start position:0% one<00:43:57.540> so<00:43:58.470> mm-hmm<00:43:59.310> this<00:44:00.270> is<00:44:00.420> all<00:44:00.660> do 00:44:01.600 --> 00:44:01.610 align:start position:0% one so mm-hmm this is all do 00:44:01.610 --> 00:44:05.990 align:start position:0% one so mm-hmm this is all do TLS<00:44:02.610> no<00:44:02.850> one<00:44:03.090> which<00:44:03.330> is<00:44:03.510> API<00:44:03.930> server<00:44:04.790> just<00:44:05.790> saw 00:44:05.990 --> 00:44:06.000 align:start position:0% TLS no one which is API server just saw 00:44:06.000 --> 00:44:09.380 align:start position:0% TLS no one which is API server just saw the<00:44:06.200> request<00:44:07.200> from<00:44:07.410> the<00:44:07.560> UI<00:44:07.710> and<00:44:08.190> then<00:44:08.970> it 00:44:09.380 --> 00:44:09.390 align:start position:0% the request from the UI and then it 00:44:09.390 --> 00:44:11.300 align:start position:0% the request from the UI and then it understands<00:44:10.140> that<00:44:10.320> this<00:44:10.500> is<00:44:10.560> a<00:44:10.710> request<00:44:11.100> to 00:44:11.300 --> 00:44:11.310 align:start position:0% understands that this is a request to 00:44:11.310 --> 00:44:14.120 align:start position:0% understands that this is a request to issues<00:44:11.730> on<00:44:11.940> tokens<00:44:12.360> so<00:44:13.050> it<00:44:13.170> generated<00:44:13.680> some 00:44:14.120 --> 00:44:14.130 align:start position:0% issues on tokens so it generated some 00:44:14.130 --> 00:44:20.090 align:start position:0% issues on tokens so it generated some command<00:44:15.230> and<00:44:16.230> then<00:44:17.120> asked<00:44:18.380> the<00:44:19.380> worker<00:44:19.770> level 00:44:20.090 --> 00:44:20.100 align:start position:0% command and then asked the worker level 00:44:20.100 --> 00:44:23.690 align:start position:0% command and then asked the worker level to<00:44:21.110> process<00:44:22.110> this<00:44:22.290> command<00:44:22.710> so<00:44:23.400> the 00:44:23.690 --> 00:44:23.700 align:start position:0% to process this command so the 00:44:23.700 --> 00:44:25.760 align:start position:0% to process this command so the processing<00:44:24.240> of<00:44:24.300> the<00:44:24.450> command<00:44:24.780> is<00:44:25.080> thawing<00:44:25.440> the 00:44:25.760 --> 00:44:25.770 align:start position:0% processing of the command is thawing the 00:44:25.770 --> 00:44:28.310 align:start position:0% processing of the command is thawing the trust<00:44:26.040> involved<00:44:26.430> right<00:44:27.060> by<00:44:27.570> the<00:44:27.630> by<00:44:28.260> the 00:44:28.310 --> 00:44:28.320 align:start position:0% trust involved right by the by the 00:44:28.320 --> 00:44:32.080 align:start position:0% trust involved right by the by the trusted<00:44:28.920> component<00:44:29.460> and<00:44:29.720> as<00:44:30.720> a<00:44:30.750> result<00:44:31.230> some 00:44:32.080 --> 00:44:32.090 align:start position:0% trusted component and as a result some 00:44:32.090 --> 00:44:35.210 align:start position:0% trusted component and as a result some reward<00:44:33.090> tokens<00:44:33.690> were<00:44:33.840> meditating<00:44:34.140> so<00:44:34.500> that<00:44:34.950> C 00:44:35.210 --> 00:44:35.220 align:start position:0% reward tokens were meditating so that C 00:44:35.220 --> 00:44:46.030 align:start position:0% reward tokens were meditating so that C is<00:44:37.730> death<00:44:38.730> I've<00:44:39.390> actually<00:44:39.780> got<00:44:40.350> da 00:44:46.030 --> 00:44:46.040 align:start position:0% 00:44:46.040 --> 00:44:48.040 align:start position:0% Venus<00:44:46.640> was<00:44:46.790> you<00:44:46.970> know 00:44:48.040 --> 00:44:48.050 align:start position:0% Venus was you know 00:44:48.050 --> 00:44:50.319 align:start position:0% Venus was you know did<00:44:48.560> I<00:44:48.650> use<00:44:48.830> Gmail 00:44:50.319 --> 00:44:50.329 align:start position:0% did I use Gmail 00:44:50.329 --> 00:44:53.679 align:start position:0% did I use Gmail right<00:44:51.099> you<00:44:52.099> got<00:44:52.249> 100<00:44:52.609> tokens<00:44:52.789> because<00:44:53.359> you<00:44:53.509> get 00:44:53.679 --> 00:44:53.689 align:start position:0% right you got 100 tokens because you get 00:44:53.689 --> 00:45:01.449 align:start position:0% right you got 100 tokens because you get that<00:44:53.869> so<00:44:58.089> if<00:44:59.089> you<00:44:59.390> didn't<00:44:59.719> understand<00:45:00.529> what's 00:45:01.449 --> 00:45:01.459 align:start position:0% that so if you didn't understand what's 00:45:01.459 --> 00:45:03.339 align:start position:0% that so if you didn't understand what's happening<00:45:01.880> undercover<00:45:02.390> this<00:45:02.660> made<00:45:03.109> me 00:45:03.339 --> 00:45:03.349 align:start position:0% happening undercover this made me 00:45:03.349 --> 00:45:05.469 align:start position:0% happening undercover this made me underwhelming<00:45:04.069> but<00:45:04.219> if<00:45:04.670> you<00:45:04.910> actually<00:45:05.299> know 00:45:05.469 --> 00:45:05.479 align:start position:0% underwhelming but if you actually know 00:45:05.479 --> 00:45:07.809 align:start position:0% underwhelming but if you actually know that<00:45:05.509> in<00:45:06.380> this<00:45:06.619> system<00:45:06.829> there's<00:45:07.339> no<00:45:07.429> way 00:45:07.809 --> 00:45:07.819 align:start position:0% that in this system there's no way 00:45:07.819 --> 00:45:12.370 align:start position:0% that in this system there's no way anybody<00:45:08.390> can<00:45:08.689> and<00:45:10.029> drive<00:45:11.029> Charles<00:45:11.929> to<00:45:12.199> get 00:45:12.370 --> 00:45:12.380 align:start position:0% anybody can and drive Charles to get 00:45:12.380 --> 00:45:14.650 align:start position:0% anybody can and drive Charles to get three<00:45:12.679> tokens<00:45:12.949> then<00:45:13.519> that's<00:45:14.150> a<00:45:14.299> really<00:45:14.539> good 00:45:14.650 --> 00:45:14.660 align:start position:0% three tokens then that's a really good 00:45:14.660 --> 00:45:28.600 align:start position:0% three tokens then that's a really good thing<00:45:14.929> so<00:45:15.829> thank<00:45:16.099> you 00:45:28.600 --> 00:45:28.610 align:start position:0% 00:45:28.610 --> 00:45:37.690 align:start position:0% [Music] 00:45:37.690 --> 00:45:37.700 align:start position:0% 00:45:37.700 --> 00:45:41.500 align:start position:0% so<00:45:38.210> so<00:45:38.510> that<00:45:38.690> does<00:45:39.880> all<00:45:40.880> of<00:45:40.940> this<00:45:41.180> is<00:45:41.359> actually 00:45:41.500 --> 00:45:41.510 align:start position:0% so so that does all of this is actually 00:45:41.510 --> 00:45:49.900 align:start position:0% so so that does all of this is actually really 00:45:49.900 --> 00:45:49.910 align:start position:0% 00:45:49.910 --> 00:45:54.490 align:start position:0% just<00:45:50.870> sex<00:45:51.290> game<00:45:51.590> for<00:45:51.980> the<00:45:52.160> demo<00:45:53.150> so<00:45:53.930> that 00:45:54.490 --> 00:45:54.500 align:start position:0% just sex game for the demo so that 00:45:54.500 --> 00:45:56.560 align:start position:0% just sex game for the demo so that avoids<00:45:55.250> the<00:45:55.370> immigrants<00:45:55.850> in<00:45:56.180> that<00:45:56.330> simulation 00:45:56.560 --> 00:45:56.570 align:start position:0% avoids the immigrants in that simulation 00:45:56.570 --> 00:45:59.170 align:start position:0% avoids the immigrants in that simulation mower<00:45:57.020> which<00:45:57.950> promised<00:45:58.370> every<00:45:58.760> component 00:45:59.170 --> 00:45:59.180 align:start position:0% mower which promised every component 00:45:59.180 --> 00:46:02.490 align:start position:0% mower which promised every component from<00:45:59.570> home<00:45:59.930> the<00:46:00.080> same<00:46:00.320> are<00:46:00.770> no<00:46:00.950> commercial<00:46:01.460> so 00:46:02.490 --> 00:46:02.500 align:start position:0% from home the same are no commercial so 00:46:02.500 --> 00:46:05.170 align:start position:0% from home the same are no commercial so here<00:46:03.500> actually<00:46:03.740> has<00:46:04.100> something<00:46:04.310> wrong<00:46:04.700> in<00:46:05.090> the 00:46:05.170 --> 00:46:05.180 align:start position:0% here actually has something wrong in the 00:46:05.180 --> 00:46:07.450 align:start position:0% here actually has something wrong in the highway<00:46:05.600> road<00:46:05.870> which<00:46:06.560> of<00:46:06.710> course<00:46:06.740> we'll<00:46:07.190> use 00:46:07.450 --> 00:46:07.460 align:start position:0% highway road which of course we'll use 00:46:07.460 --> 00:46:11.200 align:start position:0% highway road which of course we'll use case<00:46:08.060> so<00:46:08.720> basically<00:46:09.110> the<00:46:09.680> PE<00:46:10.100> the<00:46:10.760> component 00:46:11.200 --> 00:46:11.210 align:start position:0% case so basically the PE the component 00:46:11.210 --> 00:46:15.370 align:start position:0% case so basically the PE the component and<00:46:12.220> deploy<00:46:13.220> on<00:46:13.460> Microsoft<00:46:14.120> Azure<00:46:14.360> as<00:46:14.930> Jack's 00:46:15.370 --> 00:46:15.380 align:start position:0% and deploy on Microsoft Azure as Jack's 00:46:15.380 --> 00:46:19.180 align:start position:0% and deploy on Microsoft Azure as Jack's prohibition<00:46:16.010> and<00:46:16.910> the<00:46:17.560> project<00:46:18.560> based<00:46:18.860> on<00:46:19.040> the 00:46:19.180 --> 00:46:19.190 align:start position:0% prohibition and the project based on the 00:46:19.190 --> 00:46:22.150 align:start position:0% prohibition and the project based on the final<00:46:19.760> networks<00:46:20.300> so<00:46:20.870> the<00:46:21.350> heart<00:46:21.800> of<00:46:21.860> the<00:46:21.950> mound 00:46:22.150 --> 00:46:22.160 align:start position:0% final networks so the heart of the mound 00:46:22.160 --> 00:46:25.060 align:start position:0% final networks so the heart of the mound he<00:46:22.730> that<00:46:22.970> title<00:46:23.390> custom<00:46:23.840> for<00:46:24.080> the<00:46:24.200> EA<00:46:24.530> token 00:46:25.060 --> 00:46:25.070 align:start position:0% he that title custom for the EA token 00:46:25.070 --> 00:46:28.470 align:start position:0% he that title custom for the EA token hardware<00:46:25.550> board<00:46:25.730> it's<00:46:26.450> kind<00:46:26.630> of<00:46:26.950> complicated 00:46:28.470 --> 00:46:28.480 align:start position:0% hardware board it's kind of complicated 00:46:28.480 --> 00:46:32.620 align:start position:0% hardware board it's kind of complicated the<00:46:29.890> principal<00:46:30.890> difference<00:46:31.450> compared<00:46:32.450> to<00:46:32.510> the 00:46:32.620 --> 00:46:32.630 align:start position:0% the principal difference compared to the 00:46:32.630 --> 00:46:35.350 align:start position:0% the principal difference compared to the assimilation<00:46:33.140> motive<00:46:33.710> point<00:46:33.980> is<00:46:34.250> focused<00:46:35.150> on 00:46:35.350 --> 00:46:35.360 align:start position:0% assimilation motive point is focused on 00:46:35.360 --> 00:46:39.340 align:start position:0% assimilation motive point is focused on these<00:46:35.570> thirty<00:46:36.020> announcements<00:46:36.740> so<00:46:38.350> basically 00:46:39.340 --> 00:46:39.350 align:start position:0% these thirty announcements so basically 00:46:39.350 --> 00:46:42.370 align:start position:0% these thirty announcements so basically for<00:46:39.770> the<00:46:39.830> dua<00:46:39.950> poverty<00:46:40.640> it's<00:46:41.060> a<00:46:41.180> same<00:46:41.420> so<00:46:41.750> you 00:46:42.370 --> 00:46:42.380 align:start position:0% for the dua poverty it's a same so you 00:46:42.380 --> 00:46:47.110 align:start position:0% for the dua poverty it's a same so you are<00:46:42.560> here<00:46:42.950> the<00:46:43.940> users<00:46:44.330> have<00:46:44.870> five<00:46:45.460> he<00:46:46.460> a<00:46:46.670> token 00:46:47.110 --> 00:46:47.120 align:start position:0% are here the users have five he a token 00:46:47.120 --> 00:46:50.530 align:start position:0% are here the users have five he a token request<00:46:47.660> and<00:46:48.050> the<00:46:48.740> Year<00:46:49.100> token<00:46:49.430> request<00:46:50.120> could 00:46:50.530 --> 00:46:50.540 align:start position:0% request and the Year token request could 00:46:50.540 --> 00:46:54.730 align:start position:0% request and the Year token request could be<00:46:50.830> captured<00:46:51.830> by<00:46:52.280> the<00:46:52.340> TE<00:46:52.700> listener<00:46:53.330> ERG<00:46:54.260> TT 00:46:54.730 --> 00:46:54.740 align:start position:0% be captured by the TE listener ERG TT 00:46:54.740 --> 00:46:59.380 align:start position:0% be captured by the TE listener ERG TT cos<00:46:55.100> P<00:46:55.310> channel<00:46:56.380> and<00:46:57.380> the<00:46:58.190> key<00:46:58.430> listener<00:46:58.880> is<00:46:59.150> in 00:46:59.380 --> 00:46:59.390 align:start position:0% cos P channel and the key listener is in 00:46:59.390 --> 00:47:02.830 align:start position:0% cos P channel and the key listener is in the<00:46:59.510> scope<00:46:59.720> of<00:46:59.990> the<00:47:00.170> EA<00:47:00.500> illustrator<00:47:01.510> so<00:47:02.510> the 00:47:02.830 --> 00:47:02.840 align:start position:0% the scope of the EA illustrator so the 00:47:02.840 --> 00:47:05.410 align:start position:0% the scope of the EA illustrator so the administrator<00:47:03.740> can<00:47:04.100> just<00:47:04.730> inject 00:47:05.410 --> 00:47:05.420 align:start position:0% administrator can just inject 00:47:05.420 --> 00:47:08.020 align:start position:0% administrator can just inject signing<00:47:06.380> key<00:47:06.530> and<00:47:06.620> five<00:47:06.920> decay<00:47:07.250> between<00:47:07.730> te 00:47:08.020 --> 00:47:08.030 align:start position:0% signing key and five decay between te 00:47:08.030 --> 00:47:11.020 align:start position:0% signing key and five decay between te listener<00:47:08.690> and<00:47:08.870> he<00:47:09.680> listener<00:47:10.130> will<00:47:10.310> transfer 00:47:11.020 --> 00:47:11.030 align:start position:0% listener and he listener will transfer 00:47:11.030 --> 00:47:13.780 align:start position:0% listener and he listener will transfer the<00:47:11.300> scheme<00:47:11.720> to<00:47:12.350> a<00:47:12.380> secret<00:47:13.130> management 00:47:13.780 --> 00:47:13.790 align:start position:0% the scheme to a secret management 00:47:13.790 --> 00:47:16.150 align:start position:0% the scheme to a secret management management<00:47:14.210> service<00:47:14.750> which<00:47:15.350> is<00:47:15.530> also<00:47:15.950> running 00:47:16.150 --> 00:47:16.160 align:start position:0% management service which is also running 00:47:16.160 --> 00:47:21.430 align:start position:0% management service which is also running inside<00:47:16.790> the<00:47:17.290> USGS<00:47:18.290> Enclave<00:47:18.920> and<00:47:20.440> meanwhile 00:47:21.430 --> 00:47:21.440 align:start position:0% inside the USGS Enclave and meanwhile 00:47:21.440 --> 00:47:25.710 align:start position:0% inside the USGS Enclave and meanwhile the<00:47:22.220> key<00:47:22.460> listener<00:47:22.910> may<00:47:23.180> also<00:47:23.450> encrypt<00:47:24.380> the 00:47:25.710 --> 00:47:25.720 align:start position:0% the key listener may also encrypt the 00:47:25.720 --> 00:47:29.530 align:start position:0% the key listener may also encrypt the token<00:47:26.720> requests<00:47:27.230> and<00:47:27.640> pushed<00:47:28.640> the<00:47:28.940> encryption 00:47:29.530 --> 00:47:29.540 align:start position:0% token requests and pushed the encryption 00:47:29.540 --> 00:47:33.090 align:start position:0% token requests and pushed the encryption which<00:47:29.840> requests<00:47:30.410> to<00:47:30.620> a<00:47:30.650> data<00:47:31.370> storage<00:47:31.790> server 00:47:33.090 --> 00:47:33.100 align:start position:0% which requests to a data storage server 00:47:33.100 --> 00:47:36.750 align:start position:0% which requests to a data storage server so<00:47:34.100> all<00:47:34.580> these<00:47:35.060> competence<00:47:35.630> are<00:47:36.200> power 00:47:36.750 --> 00:47:36.760 align:start position:0% so all these competence are power 00:47:36.760 --> 00:47:39.550 align:start position:0% so all these competence are power studies<00:47:37.760> in<00:47:38.030> the<00:47:38.150> EEA<00:47:38.560> administrator 00:47:39.550 --> 00:47:39.560 align:start position:0% studies in the EEA administrator 00:47:39.560 --> 00:47:42.730 align:start position:0% studies in the EEA administrator confidence<00:47:40.190> not<00:47:40.400> yet<00:47:40.790> the<00:47:41.060> router<00:47:41.270> Desco<00:47:41.990> so 00:47:42.730 --> 00:47:42.740 align:start position:0% confidence not yet the router Desco so 00:47:42.740 --> 00:47:45.110 align:start position:0% confidence not yet the router Desco so the<00:47:43.700> next<00:47:43.910> step<00:47:44.210> that 00:47:45.110 --> 00:47:45.120 align:start position:0% the next step that 00:47:45.120 --> 00:47:48.380 align:start position:0% the next step that neither<00:47:45.750> the<00:47:46.410> off<00:47:46.620> chair<00:47:46.950> apart<00:47:47.550> object 00:47:48.380 --> 00:47:48.390 align:start position:0% neither the off chair apart object 00:47:48.390 --> 00:47:51.200 align:start position:0% neither the off chair apart object trusted<00:47:48.840> execution<00:47:49.140> so<00:47:50.130> these<00:47:50.340> are<00:47:50.640> two<00:47:50.910> ways 00:47:51.200 --> 00:47:51.210 align:start position:0% trusted execution so these are two ways 00:47:51.210 --> 00:47:56.030 align:start position:0% trusted execution so these are two ways of<00:47:52.130> triggering<00:47:53.130> the<00:47:53.760> key<00:47:54.360> applications<00:47:55.110> the 00:47:56.030 --> 00:47:56.040 align:start position:0% of triggering the key applications the 00:47:56.040 --> 00:47:59.360 align:start position:0% of triggering the key applications the direct<00:47:56.640> model<00:47:57.060> and<00:47:57.390> approximately<00:47:57.990> so<00:47:58.860> for 00:47:59.360 --> 00:47:59.370 align:start position:0% direct model and approximately so for 00:47:59.370 --> 00:48:02.000 align:start position:0% direct model and approximately so for the<00:47:59.460> director<00:47:59.910> model<00:48:00.240> actually<00:48:00.780> te<00:48:01.380> where 00:48:02.000 --> 00:48:02.010 align:start position:0% the director model actually te where 00:48:02.010 --> 00:48:06.530 align:start position:0% the director model actually te where lori<00:48:02.460> the<00:48:03.060> blockchain<00:48:03.570> and<00:48:04.280> the<00:48:05.280> hey<00:48:05.760> i<00:48:06.150> want 00:48:06.530 --> 00:48:06.540 align:start position:0% lori the blockchain and the hey i want 00:48:06.540 --> 00:48:09.170 align:start position:0% lori the blockchain and the hey i want to<00:48:06.630> treat<00:48:06.810> for<00:48:07.140> them<00:48:07.290> for<00:48:07.560> Rajesh<00:48:08.490> loved<00:48:08.850> one 00:48:09.170 --> 00:48:09.180 align:start position:0% to treat for them for Rajesh loved one 00:48:09.180 --> 00:48:11.570 align:start position:0% to treat for them for Rajesh loved one money<00:48:09.600> when<00:48:10.080> he<00:48:10.110> died<00:48:10.410> he<00:48:10.470> dressed<00:48:10.920> and<00:48:11.310> his 00:48:11.570 --> 00:48:11.580 align:start position:0% money when he died he dressed and his 00:48:11.580 --> 00:48:14.120 align:start position:0% money when he died he dressed and his configuration<00:48:12.270> equations<00:48:12.780> then<00:48:13.560> he<00:48:13.920> could 00:48:14.120 --> 00:48:14.130 align:start position:0% configuration equations then he could 00:48:14.130 --> 00:48:17.090 align:start position:0% configuration equations then he could die<00:48:14.850> along<00:48:15.060> with<00:48:15.090> the<00:48:15.510> resist<00:48:16.470> information<00:48:17.010> to 00:48:17.090 --> 00:48:17.100 align:start position:0% die along with the resist information to 00:48:17.100 --> 00:48:19.940 align:start position:0% die along with the resist information to try<00:48:17.280> from<00:48:17.550> the<00:48:17.790> north<00:48:18.000> changing<00:48:18.450> the<00:48:18.990> dialogue 00:48:19.940 --> 00:48:19.950 align:start position:0% try from the north changing the dialogue 00:48:19.950 --> 00:48:21.890 align:start position:0% try from the north changing the dialogue with<00:48:20.370> the<00:48:20.550> bridges<00:48:20.850> were<00:48:21.090> configured<00:48:21.750> a<00:48:21.810> lot 00:48:21.890 --> 00:48:21.900 align:start position:0% with the bridges were configured a lot 00:48:21.900 --> 00:48:23.930 align:start position:0% with the bridges were configured a lot of<00:48:21.960> change<00:48:22.170> has<00:48:22.380> to<00:48:22.500> come<00:48:22.530> here<00:48:22.860> so<00:48:23.580> this<00:48:23.790> is 00:48:23.930 --> 00:48:23.940 align:start position:0% of change has to come here so this is 00:48:23.940 --> 00:48:26.030 align:start position:0% of change has to come here so this is right<00:48:24.120> it's<00:48:24.780> quite<00:48:24.960> a<00:48:24.990> physical<00:48:25.440> force<00:48:25.650> report 00:48:26.030 --> 00:48:26.040 align:start position:0% right it's quite a physical force report 00:48:26.040 --> 00:48:28.880 align:start position:0% right it's quite a physical force report and<00:48:26.730> for<00:48:27.060> the<00:48:27.150> proxy<00:48:27.390> model<00:48:27.810> actually<00:48:28.290> diva 00:48:28.880 --> 00:48:28.890 align:start position:0% and for the proxy model actually diva 00:48:28.890 --> 00:48:31.850 align:start position:0% and for the proxy model actually diva scenario<00:48:29.460> host<00:48:29.960> find<00:48:30.960> a<00:48:31.200> new<00:48:31.410> government 00:48:31.850 --> 00:48:31.860 align:start position:0% scenario host find a new government 00:48:31.860 --> 00:48:36.250 align:start position:0% scenario host find a new government commercial<00:48:32.340> said<00:48:33.150> that<00:48:33.630> I<00:48:33.930> will<00:48:34.460> run<00:48:35.460> this 00:48:36.250 --> 00:48:36.260 align:start position:0% commercial said that I will run this 00:48:36.260 --> 00:48:39.980 align:start position:0% commercial said that I will run this execution<00:48:37.260> logic<00:48:38.190> for<00:48:39.030> the<00:48:39.150> richest<00:48:39.750> Walker 00:48:39.980 --> 00:48:39.990 align:start position:0% execution logic for the richest Walker 00:48:39.990 --> 00:48:43.660 align:start position:0% execution logic for the richest Walker he<00:48:40.230> and<00:48:41.040> the<00:48:41.400> world<00:48:41.610> register<00:48:42.030> water<00:48:42.570> it<00:48:43.140> will 00:48:43.660 --> 00:48:43.670 align:start position:0% he and the world register water it will 00:48:43.670 --> 00:48:46.760 align:start position:0% he and the world register water it will we<00:48:44.670> always<00:48:44.970> listening<00:48:45.630> the<00:48:45.780> doctrine<00:48:46.200> events 00:48:46.760 --> 00:48:46.770 align:start position:0% we always listening the doctrine events 00:48:46.770 --> 00:48:49.850 align:start position:0% we always listening the doctrine events and<00:48:47.220> as<00:48:47.880> soon<00:48:48.570> as<00:48:48.690> we<00:48:48.900> capture<00:48:49.140> is<00:48:49.530> for 00:48:49.850 --> 00:48:49.860 align:start position:0% and as soon as we capture is for 00:48:49.860 --> 00:48:51.920 align:start position:0% and as soon as we capture is for caravans<00:48:50.160> we<00:48:50.520> will<00:48:50.670> retrieve<00:48:50.970> me<00:48:51.240> key 00:48:51.920 --> 00:48:51.930 align:start position:0% caravans we will retrieve me key 00:48:51.930 --> 00:48:54.290 align:start position:0% caravans we will retrieve me key applications<00:48:52.620> so<00:48:53.220> as<00:48:53.400> soon<00:48:53.610> as<00:48:53.730> a<00:48:53.880> TV 00:48:54.290 --> 00:48:54.300 align:start position:0% applications so as soon as a TV 00:48:54.300 --> 00:48:58.040 align:start position:0% applications so as soon as a TV applications<00:48:54.990> it's<00:48:55.230> pretty<00:48:55.530> good<00:48:55.740> as<00:48:57.050> skill 00:48:58.040 --> 00:48:58.050 align:start position:0% applications it's pretty good as skill 00:48:58.050 --> 00:49:01.160 align:start position:0% applications it's pretty good as skill channel<00:48:58.560> is<00:48:58.770> established<00:48:59.840> between<00:49:00.840> the 00:49:01.160 --> 00:49:01.170 align:start position:0% channel is established between the 00:49:01.170 --> 00:49:03.050 align:start position:0% channel is established between the security<00:49:01.650> manager<00:49:01.860> Security<00:49:02.640> Management 00:49:03.050 --> 00:49:03.060 align:start position:0% security manager Security Management 00:49:03.060 --> 00:49:07.820 align:start position:0% security manager Security Management Service<00:49:03.600> and<00:49:04.230> the<00:49:04.890> remote<00:49:05.190> de<00:49:05.730> Enclave<00:49:06.830> so 00:49:07.820 --> 00:49:07.830 align:start position:0% Service and the remote de Enclave so 00:49:07.830 --> 00:49:10.370 align:start position:0% Service and the remote de Enclave so this<00:49:08.130> remote<00:49:08.550> remote<00:49:08.900> screen<00:49:09.900> channel<00:49:10.320> is 00:49:10.370 --> 00:49:10.380 align:start position:0% this remote remote screen channel is 00:49:10.380 --> 00:49:12.500 align:start position:0% this remote remote screen channel is also<00:49:10.590> called<00:49:10.980> called<00:49:11.550> SGX 00:49:12.500 --> 00:49:12.510 align:start position:0% also called called SGX 00:49:12.510 --> 00:49:15.950 align:start position:0% also called called SGX secret<00:49:13.500> peripheral<00:49:14.160> channel<00:49:14.550> so<00:49:15.180> the<00:49:15.690> Sony 00:49:15.950 --> 00:49:15.960 align:start position:0% secret peripheral channel so the Sony 00:49:15.960 --> 00:49:19.310 align:start position:0% secret peripheral channel so the Sony came<00:49:16.580> the<00:49:17.580> private<00:49:18.270> key<00:49:18.420> needs<00:49:18.660> to<00:49:18.780> sign<00:49:19.020> the 00:49:19.310 --> 00:49:19.320 align:start position:0% came the private key needs to sign the 00:49:19.320 --> 00:49:22.790 align:start position:0% came the private key needs to sign the flood<00:49:20.300> contracted<00:49:21.300> by<00:49:21.570> the<00:49:21.630> ER<00:49:21.870> administrator 00:49:22.790 --> 00:49:22.800 align:start position:0% flood contracted by the ER administrator 00:49:22.800 --> 00:49:25.850 align:start position:0% flood contracted by the ER administrator that<00:49:23.430> can<00:49:23.640> be<00:49:23.820> transferred<00:49:24.720> to<00:49:25.020> the<00:49:25.500> TV<00:49:25.830> II 00:49:25.850 --> 00:49:25.860 align:start position:0% that can be transferred to the TV II 00:49:25.860 --> 00:49:30.050 align:start position:0% that can be transferred to the TV II complex<00:49:26.310> so<00:49:27.240> I<00:49:27.810> would<00:49:28.230> laugh<00:49:28.440> and<00:49:29.280> lie<00:49:29.550> once 00:49:30.050 --> 00:49:30.060 align:start position:0% complex so I would laugh and lie once 00:49:30.060 --> 00:49:34.010 align:start position:0% complex so I would laugh and lie once again<00:49:30.360> that<00:49:30.770> the<00:49:31.770> team<00:49:32.340> that<00:49:33.180> morning<00:49:33.600> inside 00:49:34.010 --> 00:49:34.020 align:start position:0% again that the team that morning inside 00:49:34.020 --> 00:49:36.860 align:start position:0% again that the team that morning inside the<00:49:34.410> uncles<00:49:34.980> is<00:49:35.520> directed<00:49:36.090> by<00:49:36.120> the<00:49:36.300> hardware 00:49:36.860 --> 00:49:36.870 align:start position:0% the uncles is directed by the hardware 00:49:36.870 --> 00:49:40.160 align:start position:0% the uncles is directed by the hardware interest<00:49:37.800> rates<00:49:38.100> higher<00:49:38.970> level<00:49:39.480> of<00:49:39.660> security 00:49:40.160 --> 00:49:40.170 align:start position:0% interest rates higher level of security 00:49:40.170 --> 00:49:44.840 align:start position:0% interest rates higher level of security so<00:49:40.980> even<00:49:41.970> the<00:49:42.090> owner<00:49:42.390> of<00:49:42.840> the<00:49:43.170> TE<00:49:43.460> the<00:49:44.460> machine 00:49:44.840 --> 00:49:44.850 align:start position:0% so even the owner of the TE the machine 00:49:44.850 --> 00:49:48.930 align:start position:0% so even the owner of the TE the machine is<00:49:45.270> not<00:49:45.570> able<00:49:46.170> to<00:49:46.350> penetrate<00:49:46.710> this<00:49:47.340> Enclave 00:49:48.930 --> 00:49:48.940 align:start position:0% is not able to penetrate this Enclave 00:49:48.940 --> 00:49:54.290 align:start position:0% is not able to penetrate this Enclave and<00:49:49.030> still<00:49:49.660> or<00:49:50.170> temper<00:49:51.069> that<00:49:51.849> is<00:49:52.030> privately<00:49:52.480> so 00:49:54.290 --> 00:49:54.300 align:start position:0% and still or temper that is privately so 00:49:54.300 --> 00:49:59.579 align:start position:0% and still or temper that is privately so the<00:49:55.680> equal<00:49:56.680> data<00:49:57.160> equivalent<00:49:58.150> they<00:49:58.270> also<00:49:58.599> both 00:49:59.579 --> 00:49:59.589 align:start position:0% the equal data equivalent they also both 00:49:59.589 --> 00:50:03.359 align:start position:0% the equal data equivalent they also both port<00:50:00.190> to<00:50:00.490> the<00:50:00.599> TV<00:50:01.599> applications<00:50:02.290> so<00:50:03.069> the 00:50:03.359 --> 00:50:03.369 align:start position:0% port to the TV applications so the 00:50:03.369 --> 00:50:05.760 align:start position:0% port to the TV applications so the applications<00:50:04.150> is<00:50:04.390> not<00:50:04.630> this<00:50:04.810> able<00:50:05.230> to<00:50:05.380> decrypt 00:50:05.760 --> 00:50:05.770 align:start position:0% applications is not this able to decrypt 00:50:05.770 --> 00:50:08.190 align:start position:0% applications is not this able to decrypt the<00:50:05.890> data<00:50:05.980> and<00:50:06.520> apply<00:50:06.880> the<00:50:07.200> exclusive 00:50:08.190 --> 00:50:08.200 align:start position:0% the data and apply the exclusive 00:50:08.200 --> 00:50:11.430 align:start position:0% the data and apply the exclusive execution<00:50:08.770> logic<00:50:09.190> and<00:50:09.780> finally<00:50:10.780> and<00:50:11.050> file 00:50:11.430 --> 00:50:11.440 align:start position:0% execution logic and finally and file 00:50:11.440 --> 00:50:14.069 align:start position:0% execution logic and finally and file object<00:50:12.040> reduction<00:50:12.609> directly<00:50:13.480> to<00:50:13.960> the 00:50:14.069 --> 00:50:14.079 align:start position:0% object reduction directly to the 00:50:14.079 --> 00:50:17.760 align:start position:0% object reduction directly to the blockchain<00:50:14.380> networks<00:50:15.040> based<00:50:15.730> on<00:50:16.240> the<00:50:16.770> there's 00:50:17.760 --> 00:50:17.770 align:start position:0% blockchain networks based on the there's 00:50:17.770 --> 00:50:20.910 align:start position:0% blockchain networks based on the there's a<00:50:17.829> question<00:50:18.390> question<00:50:19.390> he<00:50:19.690> said<00:50:19.900> this<00:50:20.530> India 00:50:20.910 --> 00:50:20.920 align:start position:0% a question question he said this India 00:50:20.920 --> 00:50:23.190 align:start position:0% a question question he said this India first<00:50:21.400> environment<00:50:22.000> right<00:50:22.180> the<00:50:22.540> key<00:50:22.780> to<00:50:23.020> the 00:50:23.190 --> 00:50:23.200 align:start position:0% first environment right the key to the 00:50:23.200 --> 00:50:25.390 align:start position:0% first environment right the key to the secret<00:50:23.500> our<00:50:23.859> country 00:50:25.390 --> 00:50:25.400 align:start position:0% secret our country 00:50:25.400 --> 00:50:28.090 align:start position:0% secret our country the<00:50:25.610> mystery<00:50:25.970> of<00:50:26.000> where<00:50:26.240> the<00:50:26.540> access<00:50:27.010> for<00:50:28.010> this 00:50:28.090 --> 00:50:28.100 align:start position:0% the mystery of where the access for this 00:50:28.100 --> 00:50:31.780 align:start position:0% the mystery of where the access for this one<00:50:28.340> yeah<00:50:28.790> yeah<00:50:29.420> actually<00:50:29.630> this<00:50:29.990> one<00:50:30.230> as<00:50:30.980> since 00:50:31.780 --> 00:50:31.790 align:start position:0% one yeah yeah actually this one as since 00:50:31.790 --> 00:50:34.780 align:start position:0% one yeah yeah actually this one as since he<00:50:32.060> he<00:50:32.780> also<00:50:32.930> have<00:50:33.290> is<00:50:33.650> wrong<00:50:33.890> inside<00:50:34.130> interest 00:50:34.780 --> 00:50:34.790 align:start position:0% he he also have is wrong inside interest 00:50:34.790 --> 00:50:37.090 align:start position:0% he he also have is wrong inside interest GX<00:50:35.120> on<00:50:35.270> conflict<00:50:35.690> so<00:50:36.110> even<00:50:36.500> you<00:50:36.620> don't<00:50:36.860> trust 00:50:37.090 --> 00:50:37.100 align:start position:0% GX on conflict so even you don't trust 00:50:37.100 --> 00:50:39.640 align:start position:0% GX on conflict so even you don't trust this<00:50:37.310> machine<00:50:37.730> because<00:50:38.420> all<00:50:38.990> the<00:50:39.170> kings<00:50:39.380> are 00:50:39.640 --> 00:50:39.650 align:start position:0% this machine because all the kings are 00:50:39.650 --> 00:50:42.070 align:start position:0% this machine because all the kings are wrong<00:50:39.860> inside<00:50:40.250> Enclave<00:50:40.700> so<00:50:41.330> actually<00:50:41.870> when 00:50:42.070 --> 00:50:42.080 align:start position:0% wrong inside Enclave so actually when 00:50:42.080 --> 00:50:44.170 align:start position:0% wrong inside Enclave so actually when this<00:50:42.380> machine<00:50:42.590> wrong<00:50:42.890> when<00:50:43.310> is<00:50:43.490> unclear<00:50:43.910> start 00:50:44.170 --> 00:50:44.180 align:start position:0% this machine wrong when is unclear start 00:50:44.180 --> 00:50:45.850 align:start position:0% this machine wrong when is unclear start Ronnie<00:50:44.420> do<00:50:44.660> we<00:50:44.750> also<00:50:44.930> do<00:50:45.200> with<00:50:45.290> a<00:50:45.410> broadcast 00:50:45.850 --> 00:50:45.860 align:start position:0% Ronnie do we also do with a broadcast 00:50:45.860 --> 00:50:48.010 align:start position:0% Ronnie do we also do with a broadcast station<00:50:46.040> so<00:50:46.610> totally<00:50:47.090> essentially<00:50:47.660> you<00:50:47.780> have 00:50:48.010 --> 00:50:48.020 align:start position:0% station so totally essentially you have 00:50:48.020 --> 00:50:49.870 align:start position:0% station so totally essentially you have an<00:50:48.110> enemy<00:50:48.260> cluster<00:50:48.830> which<00:50:49.160> were<00:50:49.370> obviously 00:50:49.870 --> 00:50:49.880 align:start position:0% an enemy cluster which were obviously 00:50:49.880 --> 00:50:52.480 align:start position:0% an enemy cluster which were obviously hundred<00:50:50.780> yeah<00:50:51.110> but<00:50:51.350> this<00:50:51.770> was<00:50:51.980> also<00:50:52.220> in<00:50:52.430> that 00:50:52.480 --> 00:50:52.490 align:start position:0% hundred yeah but this was also in that 00:50:52.490 --> 00:50:54.760 align:start position:0% hundred yeah but this was also in that administers<00:50:53.120> co-pastor<00:50:53.750> I<00:50:53.960> hope<00:50:54.410> but 00:50:54.760 --> 00:50:54.770 align:start position:0% administers co-pastor I hope but 00:50:54.770 --> 00:50:56.470 align:start position:0% administers co-pastor I hope but essentially<00:50:55.220> you<00:50:55.430> have<00:50:55.580> to<00:50:55.700> be<00:50:55.790> Harry<00:50:56.060> trust 00:50:56.470 --> 00:50:56.480 align:start position:0% essentially you have to be Harry trust 00:50:56.480 --> 00:50:58.600 align:start position:0% essentially you have to be Harry trust and<00:50:56.840> so<00:50:57.350> he<00:50:57.470> said<00:50:57.680> okay<00:50:57.950> said<00:50:58.250> with<00:50:58.580> a 00:50:58.600 --> 00:50:58.610 align:start position:0% and so he said okay said with a 00:50:58.610 --> 00:51:00.190 align:start position:0% and so he said okay said with a consortia<00:50:59.180> that<00:50:59.480> each<00:50:59.720> member 00:51:00.190 --> 00:51:00.200 align:start position:0% consortia that each member 00:51:00.200 --> 00:51:03.100 align:start position:0% consortia that each member yeah<00:51:01.190> good<00:51:01.850> question<00:51:01.970> actually<00:51:02.570> for<00:51:02.840> the 00:51:03.100 --> 00:51:03.110 align:start position:0% yeah good question actually for the 00:51:03.110 --> 00:51:07.000 align:start position:0% yeah good question actually for the token<00:51:03.730> insurance<00:51:04.730> for<00:51:05.540> the<00:51:05.630> all<00:51:06.140> the<00:51:06.410> talking 00:51:07.000 --> 00:51:07.010 align:start position:0% token insurance for the all the talking 00:51:07.010 --> 00:51:09.760 align:start position:0% token insurance for the all the talking turrents<00:51:07.430> request<00:51:08.330> is<00:51:08.600> horrified<00:51:09.440> by<00:51:09.710> the 00:51:09.760 --> 00:51:09.770 align:start position:0% turrents request is horrified by the 00:51:09.770 --> 00:51:13.240 align:start position:0% turrents request is horrified by the Australian<00:51:10.730> actually<00:51:11.540> but<00:51:12.110> this<00:51:12.560> for 00:51:13.240 --> 00:51:13.250 align:start position:0% Australian actually but this for 00:51:13.250 --> 00:51:15.270 align:start position:0% Australian actually but this for different<00:51:13.610> use<00:51:13.760> case<00:51:13.970> for<00:51:14.240> the<00:51:14.330> obvious<00:51:14.600> a 00:51:15.270 --> 00:51:15.280 align:start position:0% different use case for the obvious a 00:51:15.280 --> 00:51:18.940 align:start position:0% different use case for the obvious a organisation<00:51:16.280> he<00:51:16.520> want<00:51:16.730> to<00:51:17.530> make<00:51:18.530> the 00:51:18.940 --> 00:51:18.950 align:start position:0% organisation he want to make the 00:51:18.950 --> 00:51:21.250 align:start position:0% organisation he want to make the reputation<00:51:19.250> for<00:51:19.970> different<00:51:20.300> employees<00:51:20.630> so 00:51:21.250 --> 00:51:21.260 align:start position:0% reputation for different employees so 00:51:21.260 --> 00:51:23.700 align:start position:0% reputation for different employees so this<00:51:21.530> could<00:51:21.800> be<00:51:21.920> in<00:51:22.640> the<00:51:22.670> organised 00:51:23.700 --> 00:51:23.710 align:start position:0% this could be in the organised 00:51:23.710 --> 00:51:26.050 align:start position:0% this could be in the organised economical<00:51:24.710> so<00:51:25.220> that<00:51:25.400> afforded<00:51:25.820> for<00:51:25.910> this 00:51:26.050 --> 00:51:26.060 align:start position:0% economical so that afforded for this 00:51:26.060 --> 00:51:28.180 align:start position:0% economical so that afforded for this case<00:51:26.300> so<00:51:26.540> for<00:51:26.750> this<00:51:26.840> token<00:51:27.530> insurance<00:51:27.890> is<00:51:28.070> only 00:51:28.180 --> 00:51:28.190 align:start position:0% case so for this token insurance is only 00:51:28.190 --> 00:51:32.790 align:start position:0% case so for this token insurance is only for<00:51:28.520> the<00:51:28.670> year<00:51:29.320> and<00:51:30.320> his<00:51:30.500> greatest<00:51:30.740> country<00:51:31.220> so 00:51:32.790 --> 00:51:32.800 align:start position:0% for the year and his greatest country so 00:51:32.800 --> 00:51:37.060 align:start position:0% for the year and his greatest country so so<00:51:33.800> the<00:51:34.430> the<00:51:35.270> the<00:51:35.660> travertine<00:51:36.320> approaching 00:51:37.060 --> 00:51:37.070 align:start position:0% so the the the travertine approaching 00:51:37.070 --> 00:51:39.820 align:start position:0% so the the the travertine approaching from<00:51:37.610> a<00:51:37.640> plane<00:51:37.940> can<00:51:38.150> be<00:51:38.290> triggered<00:51:39.290> to<00:51:39.770> the 00:51:39.820 --> 00:51:39.830 align:start position:0% from a plane can be triggered to the 00:51:39.830 --> 00:51:41.560 align:start position:0% from a plane can be triggered to the brow<00:51:40.010> gel<00:51:40.280> directly<00:51:40.580> based<00:51:40.970> on<00:51:41.210> the<00:51:41.330> sunny 00:51:41.560 --> 00:51:41.570 align:start position:0% brow gel directly based on the sunny 00:51:41.570 --> 00:51:44.320 align:start position:0% brow gel directly based on the sunny with<00:51:42.290> based<00:51:42.590> on<00:51:42.740> this<00:51:42.920> side<00:51:43.160> Hakeem<00:51:43.490> so<00:51:44.090> he<00:51:44.270> the 00:51:44.320 --> 00:51:44.330 align:start position:0% with based on this side Hakeem so he the 00:51:44.330 --> 00:51:48.700 align:start position:0% with based on this side Hakeem so he the name<00:51:44.600> of<00:51:44.930> the<00:51:45.280> arbitrator<00:51:46.750> so<00:51:47.750> in<00:51:48.320> this<00:51:48.470> way 00:51:48.700 --> 00:51:48.710 align:start position:0% name of the arbitrator so in this way 00:51:48.710 --> 00:51:51.190 align:start position:0% name of the arbitrator so in this way that<00:51:49.010> we<00:51:49.190> can<00:51:49.400> see<00:51:49.580> that<00:51:49.790> we<00:51:49.970> can<00:51:50.180> all<00:51:50.420> option 00:51:51.190 --> 00:51:51.200 align:start position:0% that we can see that we can all option 00:51:51.200 --> 00:51:54.580 align:start position:0% that we can see that we can all option or<00:51:51.530> the<00:51:51.590> execution<00:51:52.040> from<00:51:52.520> function<00:51:53.090> to<00:51:53.590> from 00:51:54.580 --> 00:51:54.590 align:start position:0% or the execution from function to from 00:51:54.590 --> 00:51:57.250 align:start position:0% or the execution from function to from check<00:51:54.800> option<00:51:55.010> without<00:51:55.880> mine<00:51:56.570> are 00:51:57.250 --> 00:51:57.260 align:start position:0% check option without mine are 00:51:57.260 --> 00:51:59.560 align:start position:0% check option without mine are compromised<00:51:57.830> into<00:51:58.190> the<00:51:58.280> screen<00:51:58.670> trust<00:51:59.090> me 00:51:59.560 --> 00:51:59.570 align:start position:0% compromised into the screen trust me 00:51:59.570 --> 00:52:00.620 align:start position:0% compromised into the screen trust me and<00:51:59.660> you<00:51:59.960> expands 00:52:00.620 --> 00:52:00.630 align:start position:0% and you expands 00:52:00.630 --> 00:52:05.200 align:start position:0% and you expands [Music] 00:52:05.200 --> 00:52:05.210 align:start position:0% 00:52:05.210 --> 00:52:09.770 align:start position:0% silly<00:52:06.210> girl<00:52:07.310> so<00:52:08.310> this<00:52:08.700> dislike<00:52:09.180> area<00:52:09.510> worked 00:52:09.770 --> 00:52:09.780 align:start position:0% silly girl so this dislike area worked 00:52:09.780 --> 00:52:14.870 align:start position:0% silly girl so this dislike area worked application<00:52:10.410> that<00:52:10.560> we<00:52:10.740> have<00:52:10.920> you<00:52:11.700> know<00:52:13.880> it's 00:52:14.870 --> 00:52:14.880 align:start position:0% application that we have you know it's 00:52:14.880 --> 00:52:17.599 align:start position:0% application that we have you know it's an<00:52:15.060> aspect<00:52:16.050> compliant<00:52:16.650> implementation<00:52:17.310> cost 00:52:17.599 --> 00:52:17.609 align:start position:0% an aspect compliant implementation cost 00:52:17.609 --> 00:52:26.599 align:start position:0% an aspect compliant implementation cost of<00:52:17.760> its<00:52:17.940> kind<00:52:22.550> and<00:52:23.550> now<00:52:24.650> not<00:52:25.650> another<00:52:25.980> other 00:52:26.599 --> 00:52:26.609 align:start position:0% of its kind and now not another other 00:52:26.609 --> 00:52:28.430 align:start position:0% of its kind and now not another other part<00:52:27.000> is<00:52:27.150> liquid<00:52:27.450> also<00:52:27.750> we<00:52:27.869> talked<00:52:28.079> about<00:52:28.230> his 00:52:28.430 --> 00:52:28.440 align:start position:0% part is liquid also we talked about his 00:52:28.440 --> 00:52:31.790 align:start position:0% part is liquid also we talked about his application<00:52:29.270> the<00:52:30.270> second<00:52:31.260> part<00:52:31.440> is<00:52:31.619> like 00:52:31.790 --> 00:52:31.800 align:start position:0% application the second part is like 00:52:31.800 --> 00:52:33.410 align:start position:0% application the second part is like Eugene<00:52:32.190> will<00:52:32.369> walk<00:52:32.550> us<00:52:32.730> through<00:52:32.819> some<00:52:33.119> of<00:52:33.210> the 00:52:33.410 --> 00:52:33.420 align:start position:0% Eugene will walk us through some of the 00:52:33.420 --> 00:52:37.190 align:start position:0% Eugene will walk us through some of the you<00:52:33.990> know<00:52:34.020> what<00:52:34.650> does<00:52:34.770> it<00:52:34.800> take<00:52:35.040> to<00:52:35.069> write<00:52:36.200> you 00:52:37.190 --> 00:52:37.200 align:start position:0% you know what does it take to write you 00:52:37.200 --> 00:52:39.319 align:start position:0% you know what does it take to write you know<00:52:37.230> we<00:52:37.470> talked<00:52:37.680> about<00:52:37.800> hey<00:52:38.609> though<00:52:38.940> you<00:52:39.089> can 00:52:39.319 --> 00:52:39.329 align:start position:0% know we talked about hey though you can 00:52:39.329 --> 00:52:42.290 align:start position:0% know we talked about hey though you can implement<00:52:39.720> this<00:52:40.020> thing<00:52:40.079> him<00:52:40.349> in<00:52:40.680> STF<00:52:41.220> ste<00:52:41.609> so 00:52:42.290 --> 00:52:42.300 align:start position:0% implement this thing him in STF ste so 00:52:42.300 --> 00:52:44.990 align:start position:0% implement this thing him in STF ste so however<00:52:42.480> how<00:52:42.810> hard<00:52:43.109> is<00:52:43.920> it<00:52:43.950> so<00:52:44.670> he's<00:52:44.819> gonna 00:52:44.990 --> 00:52:45.000 align:start position:0% however how hard is it so he's gonna 00:52:45.000 --> 00:52:47.450 align:start position:0% however how hard is it so he's gonna walk<00:52:45.240> through<00:52:45.569> this<00:52:45.690> framework<00:52:46.380> where<00:52:47.040> put 00:52:47.450 --> 00:52:47.460 align:start position:0% walk through this framework where put 00:52:47.460 --> 00:52:49.520 align:start position:0% walk through this framework where put together<00:52:47.609> and<00:52:48.000> that<00:52:48.180> will<00:52:48.329> be<00:52:48.480> open<00:52:48.750> source<00:52:48.990> to 00:52:49.520 --> 00:52:49.530 align:start position:0% together and that will be open source to 00:52:49.530 --> 00:52:51.800 align:start position:0% together and that will be open source to walk<00:52:50.400> you<00:52:50.550> through<00:52:50.730> you<00:52:51.000> know<00:52:51.150> how<00:52:51.300> we're 00:52:51.800 --> 00:52:51.810 align:start position:0% walk you through you know how we're 00:52:51.810 --> 00:53:02.680 align:start position:0% walk you through you know how we're making<00:52:51.960> it<00:52:52.200> easy<00:52:52.440> to<00:52:52.680> write<00:52:52.829> a<00:52:52.859> hello<00:52:53.160> world 00:53:02.680 --> 00:53:02.690 align:start position:0% 00:53:02.690 --> 00:53:05.080 align:start position:0% yeah<00:53:03.290> just<00:53:03.590> a<00:53:03.740> question<00:53:04.220> that<00:53:04.370> I<00:53:04.520> get<00:53:04.730> this<00:53:04.910> one 00:53:05.080 --> 00:53:05.090 align:start position:0% yeah just a question that I get this one 00:53:05.090 --> 00:53:06.700 align:start position:0% yeah just a question that I get this one there's<00:53:05.330> like<00:53:05.390> a<00:53:05.510> single<00:53:05.870> governor<00:53:06.320> how<00:53:06.560> would 00:53:06.700 --> 00:53:06.710 align:start position:0% there's like a single governor how would 00:53:06.710 --> 00:53:09.730 align:start position:0% there's like a single governor how would this<00:53:06.830> model<00:53:07.340> work<00:53:07.580> if<00:53:07.880> you<00:53:08.240> had<00:53:08.540> to<00:53:09.260> share<00:53:09.560> the 00:53:09.730 --> 00:53:09.740 align:start position:0% this model work if you had to share the 00:53:09.740 --> 00:53:11.590 align:start position:0% this model work if you had to share the trusted<00:53:10.190> locket<00:53:10.520> to<00:53:10.670> ensure<00:53:10.970> that<00:53:11.000> multiple 00:53:11.590 --> 00:53:11.600 align:start position:0% trusted locket to ensure that multiple 00:53:11.600 --> 00:53:13.330 align:start position:0% trusted locket to ensure that multiple parties<00:53:11.960> are<00:53:12.110> running<00:53:12.410> the<00:53:12.470> same<00:53:12.710> exact<00:53:13.040> trust 00:53:13.330 --> 00:53:13.340 align:start position:0% parties are running the same exact trust 00:53:13.340 --> 00:53:15.730 align:start position:0% parties are running the same exact trust and<00:53:13.520> logic<00:53:13.850> and<00:53:14.120> agreeing<00:53:14.690> this<00:53:15.410> is<00:53:15.530> free 00:53:15.730 --> 00:53:15.740 align:start position:0% and logic and agreeing this is free 00:53:15.740 --> 00:53:19.780 align:start position:0% and logic and agreeing this is free event<00:53:15.950> relationship<00:53:18.040> that<00:53:19.040> is<00:53:19.220> possible<00:53:19.670> then 00:53:19.780 --> 00:53:19.790 align:start position:0% event relationship that is possible then 00:53:19.790 --> 00:53:21.310 align:start position:0% event relationship that is possible then how<00:53:19.940> would<00:53:20.000> you<00:53:20.120> distribute<00:53:20.720> them<00:53:20.870> trust<00:53:21.140> and 00:53:21.310 --> 00:53:21.320 align:start position:0% how would you distribute them trust and 00:53:21.320 --> 00:53:24.070 align:start position:0% how would you distribute them trust and logic<00:53:21.650> in<00:53:21.770> ways<00:53:22.480> we<00:53:23.480> can't<00:53:23.720> repeat<00:53:23.930> the 00:53:24.070 --> 00:53:24.080 align:start position:0% logic in ways we can't repeat the 00:53:24.080 --> 00:53:25.750 align:start position:0% logic in ways we can't repeat the question<00:53:24.440> well<00:53:24.860> it<00:53:24.920> seems<00:53:25.070> like<00:53:25.160> this<00:53:25.430> model 00:53:25.750 --> 00:53:25.760 align:start position:0% question well it seems like this model 00:53:25.760 --> 00:53:27.820 align:start position:0% question well it seems like this model works<00:53:26.120> you<00:53:26.360> have<00:53:26.450> a<00:53:26.510> single<00:53:26.810> admin<00:53:27.350> of<00:53:27.680> the 00:53:27.820 --> 00:53:27.830 align:start position:0% works you have a single admin of the 00:53:27.830 --> 00:53:29.680 align:start position:0% works you have a single admin of the system<00:53:28.310> and<00:53:28.580> you<00:53:28.640> have<00:53:28.880> trusted<00:53:29.210> logic<00:53:29.540> that's 00:53:29.680 --> 00:53:29.690 align:start position:0% system and you have trusted logic that's 00:53:29.690 --> 00:53:31.090 align:start position:0% system and you have trusted logic that's put<00:53:29.990> but<00:53:30.320> I'm<00:53:30.380> curious<00:53:30.710> when<00:53:30.890> you<00:53:30.980> have 00:53:31.090 --> 00:53:31.100 align:start position:0% put but I'm curious when you have 00:53:31.100 --> 00:53:33.130 align:start position:0% put but I'm curious when you have multiple<00:53:31.370> parties<00:53:32.090> that<00:53:32.360> have<00:53:32.660> to<00:53:32.810> run<00:53:33.020> the 00:53:33.130 --> 00:53:33.140 align:start position:0% multiple parties that have to run the 00:53:33.140 --> 00:53:35.650 align:start position:0% multiple parties that have to run the same<00:53:33.410> exact<00:53:33.800> trust<00:53:34.130> in<00:53:34.340> logic<00:53:34.580> yes<00:53:35.240> how<00:53:35.480> do<00:53:35.540> you 00:53:35.650 --> 00:53:35.660 align:start position:0% same exact trust in logic yes how do you 00:53:35.660 --> 00:53:38.950 align:start position:0% same exact trust in logic yes how do you guarantee<00:53:35.900> in<00:53:36.200> the<00:53:36.350> state<00:53:36.620> your<00:53:36.770> shitty<00:53:37.960> types 00:53:38.950 --> 00:53:38.960 align:start position:0% guarantee in the state your shitty types 00:53:38.960 --> 00:53:42.160 align:start position:0% guarantee in the state your shitty types may<00:53:39.170> have<00:53:39.440> forcibly<00:53:40.010> to<00:53:40.220> answer<00:53:40.820> my<00:53:41.570> view<00:53:41.900> is 00:53:42.160 --> 00:53:42.170 align:start position:0% may have forcibly to answer my view is 00:53:42.170 --> 00:53:44.500 align:start position:0% may have forcibly to answer my view is that<00:53:42.500> the<00:53:43.400> point<00:53:43.640> that<00:53:43.700> you're<00:53:44.000> using<00:53:44.240> this 00:53:44.500 --> 00:53:44.510 align:start position:0% that the point that you're using this 00:53:44.510 --> 00:53:47.800 align:start position:0% that the point that you're using this centralized<00:53:45.110> component<00:53:46.100> there<00:53:46.460> is<00:53:46.760> that<00:53:47.570> you 00:53:47.800 --> 00:53:47.810 align:start position:0% centralized component there is that you 00:53:47.810 --> 00:53:49.720 align:start position:0% centralized component there is that you can<00:53:47.960> trust<00:53:48.230> it<00:53:48.470> typically<00:53:49.160> you<00:53:49.310> don't<00:53:49.460> trust 00:53:49.720 --> 00:53:49.730 align:start position:0% can trust it typically you don't trust 00:53:49.730 --> 00:53:51.220 align:start position:0% can trust it typically you don't trust their<00:53:49.940> sin<00:53:50.120> Phi<00:53:50.270> component<00:53:50.450> because<00:53:50.960> there's 00:53:51.220 --> 00:53:51.230 align:start position:0% their sin Phi component because there's 00:53:51.230 --> 00:53:53.290 align:start position:0% their sin Phi component because there's operator<00:53:51.860> there's<00:53:52.130> there's<00:53:52.910> some<00:53:53.060> code<00:53:53.270> that 00:53:53.290 --> 00:53:53.300 align:start position:0% operator there's there's some code that 00:53:53.300 --> 00:53:56.170 align:start position:0% operator there's there's some code that you<00:53:53.870> don't<00:53:53.900> know<00:53:54.340> give<00:53:55.340> you<00:53:55.460> away<00:53:55.700> in<00:53:55.940> some 00:53:56.170 --> 00:53:56.180 align:start position:0% you don't know give you away in some 00:53:56.180 --> 00:53:58.150 align:start position:0% you don't know give you away in some machines<00:53:56.330> you<00:53:56.870> can<00:53:56.900> trust<00:53:57.350> a<00:53:57.500> centralized<00:53:57.950> to 00:53:58.150 --> 00:53:58.160 align:start position:0% machines you can trust a centralized to 00:53:58.160 --> 00:54:00.610 align:start position:0% machines you can trust a centralized to thumb<00:53:58.370> right<00:53:58.610> but<00:53:59.390> this<00:53:59.570> is<00:53:59.630> a<00:53:59.810> special<00:54:00.230> kind 00:54:00.610 --> 00:54:00.620 align:start position:0% thumb right but this is a special kind 00:54:00.620 --> 00:54:02.500 align:start position:0% thumb right but this is a special kind of<00:54:00.680> central<00:54:01.040> component<00:54:01.910> that<00:54:02.000> you<00:54:02.150> can<00:54:02.300> trust 00:54:02.500 --> 00:54:02.510 align:start position:0% of central component that you can trust 00:54:02.510 --> 00:54:05.580 align:start position:0% of central component that you can trust because<00:54:03.140> you<00:54:03.410> can<00:54:03.740> ask<00:54:03.920> Intel<00:54:04.400> to<00:54:05.060> give<00:54:05.270> you<00:54:05.540> a 00:54:05.580 --> 00:54:05.590 align:start position:0% because you can ask Intel to give you a 00:54:05.590 --> 00:54:08.860 align:start position:0% because you can ask Intel to give you a gestation<00:54:06.590> that's<00:54:06.910> somebody<00:54:07.910> tell<00:54:08.270> if<00:54:08.720> you 00:54:08.860 --> 00:54:08.870 align:start position:0% gestation that's somebody tell if you 00:54:08.870 --> 00:54:10.510 align:start position:0% gestation that's somebody tell if you found<00:54:09.050> it<00:54:09.170> wrong<00:54:09.380> you<00:54:09.590> consuming<00:54:10.040> tell<00:54:10.250> and 00:54:10.510 --> 00:54:10.520 align:start position:0% found it wrong you consuming tell and 00:54:10.520 --> 00:54:11.670 align:start position:0% found it wrong you consuming tell and that's 00:54:11.670 --> 00:54:11.680 align:start position:0% that's 00:54:11.680 --> 00:54:14.130 align:start position:0% that's -<00:54:11.770> right<00:54:12.490> which<00:54:13.089> means<00:54:13.359> you<00:54:13.569> can<00:54:13.720> trust<00:54:13.960> they 00:54:14.130 --> 00:54:14.140 align:start position:0% - right which means you can trust they 00:54:14.140 --> 00:54:16.200 align:start position:0% - right which means you can trust they said<00:54:14.410> there's<00:54:14.859> no<00:54:15.099> reason<00:54:15.460> that<00:54:15.790> you<00:54:15.849> have<00:54:16.089> to 00:54:16.200 --> 00:54:16.210 align:start position:0% said there's no reason that you have to 00:54:16.210 --> 00:54:19.079 align:start position:0% said there's no reason that you have to want<00:54:16.420> a<00:54:16.660> decent<00:54:16.869> classism<00:54:17.700> so<00:54:18.700> you<00:54:18.849> wouldn't 00:54:19.079 --> 00:54:19.089 align:start position:0% want a decent classism so you wouldn't 00:54:19.089 --> 00:54:20.660 align:start position:0% want a decent classism so you wouldn't use<00:54:19.240> this<00:54:19.420> for<00:54:19.630> a<00:54:19.660> model<00:54:19.990> if<00:54:20.109> you<00:54:20.170> had<00:54:20.410> like 00:54:20.660 --> 00:54:20.670 align:start position:0% use this for a model if you had like 00:54:20.670 --> 00:54:22.770 align:start position:0% use this for a model if you had like calculations<00:54:21.670> that<00:54:21.790> you<00:54:21.910> want<00:54:22.150> a<00:54:22.210> mobile<00:54:22.390> or 00:54:22.770 --> 00:54:22.780 align:start position:0% calculations that you want a mobile or 00:54:22.780 --> 00:54:26.309 align:start position:0% calculations that you want a mobile or Easter<00:54:23.079> fun<00:54:23.849> so<00:54:24.849> maybe<00:54:25.630> we'll<00:54:25.990> have<00:54:26.170> an 00:54:26.309 --> 00:54:26.319 align:start position:0% Easter fun so maybe we'll have an 00:54:26.319 --> 00:54:28.559 align:start position:0% Easter fun so maybe we'll have an opportunity<00:54:27.040> to<00:54:27.130> present<00:54:27.280> our<00:54:27.550> use<00:54:27.819> days<00:54:28.030> but 00:54:28.559 --> 00:54:28.569 align:start position:0% opportunity to present our use days but 00:54:28.569 --> 00:54:30.960 align:start position:0% opportunity to present our use days but basically<00:54:29.050> is<00:54:29.500> a<00:54:29.559> very<00:54:29.859> good<00:54:30.040> question<00:54:30.490> but 00:54:30.960 --> 00:54:30.970 align:start position:0% basically is a very good question but 00:54:30.970 --> 00:54:34.740 align:start position:0% basically is a very good question but SGX<00:54:31.780> allows<00:54:32.140> you<00:54:32.550> to<00:54:33.550> attest<00:54:33.940> the<00:54:34.359> code<00:54:34.569> the 00:54:34.740 --> 00:54:34.750 align:start position:0% SGX allows you to attest the code the 00:54:34.750 --> 00:54:37.069 align:start position:0% SGX allows you to attest the code the transient<00:54:35.230> idea<00:54:35.589> so<00:54:36.040> we<00:54:36.160> publish<00:54:36.550> it<00:54:36.730> and 00:54:37.069 --> 00:54:37.079 align:start position:0% transient idea so we publish it and 00:54:37.079 --> 00:54:39.299 align:start position:0% transient idea so we publish it and everybody<00:54:38.079> ever<00:54:38.319> participant<00:54:38.920> can<00:54:39.069> verify 00:54:39.299 --> 00:54:39.309 align:start position:0% everybody ever participant can verify 00:54:39.309 --> 00:54:41.309 align:start position:0% everybody ever participant can verify that<00:54:39.609> it<00:54:40.000> runs<00:54:40.180> inside<00:54:40.480> the<00:54:40.750> I<00:54:40.780> believe<00:54:41.050> it 00:54:41.309 --> 00:54:41.319 align:start position:0% that it runs inside the I believe it 00:54:41.319 --> 00:54:49.230 align:start position:0% that it runs inside the I believe it what<00:54:41.650> has<00:54:41.829> been<00:54:42.040> agreed<00:54:42.250> upon<00:54:42.460> okay<00:54:48.119> this<00:54:49.119> is 00:54:49.230 --> 00:54:49.240 align:start position:0% what has been agreed upon okay this is 00:54:49.240 --> 00:54:54.870 align:start position:0% what has been agreed upon okay this is like<00:54:49.359> about<00:54:49.809> it<00:54:49.960> so<00:54:51.839> this<00:54:53.130> notation<00:54:54.130> of<00:54:54.369> okay 00:54:54.870 --> 00:54:54.880 align:start position:0% like about it so this notation of okay 00:54:54.880 --> 00:54:58.920 align:start position:0% like about it so this notation of okay so<00:54:55.599> we<00:54:55.990> note<00:54:56.890> on<00:54:57.280> the<00:54:57.819> years 00:54:58.920 --> 00:54:58.930 align:start position:0% so we note on the years 00:54:58.930 --> 00:55:11.750 align:start position:0% so we note on the years since<00:54:59.380> we<00:55:00.010> have<00:55:00.130> a<00:55:00.160> small<00:55:00.309> contracting 00:55:11.750 --> 00:55:11.760 align:start position:0% 00:55:11.760 --> 00:55:16.460 align:start position:0% [Music] 00:55:16.460 --> 00:55:16.470 align:start position:0% 00:55:16.470 --> 00:55:23.070 align:start position:0% he<00:55:17.470> repeat<00:55:17.710> the<00:55:17.830> answer<00:55:20.850> I<00:55:21.850> think<00:55:22.510> you<00:55:22.720> know 00:55:23.070 --> 00:55:23.080 align:start position:0% he repeat the answer I think you know 00:55:23.080 --> 00:55:36.500 align:start position:0% he repeat the answer I think you know sometimes<00:55:23.260> I<00:55:23.560> think<00:55:23.880> because<00:55:35.040> everybody<00:55:36.040> is 00:55:36.500 --> 00:55:36.510 align:start position:0% sometimes I think because everybody is 00:55:36.510 --> 00:55:40.140 align:start position:0% sometimes I think because everybody is that<00:55:37.510> single<00:55:37.870> person<00:55:38.350> of<00:55:38.530> control<00:55:39.060> could<00:55:40.060> it 00:55:40.140 --> 00:55:40.150 align:start position:0% that single person of control could it 00:55:40.150 --> 00:55:42.510 align:start position:0% that single person of control could it be<00:55:40.470> replaced<00:55:41.470> by<00:55:41.770> some<00:55:41.980> sort<00:55:42.160> of<00:55:42.190> a<00:55:42.280> smart 00:55:42.510 --> 00:55:42.520 align:start position:0% be replaced by some sort of a smart 00:55:42.520 --> 00:55:44.490 align:start position:0% be replaced by some sort of a smart contract<00:55:42.970> that<00:55:43.090> actually<00:55:43.660> completes<00:55:43.990> Oracle 00:55:44.490 --> 00:55:44.500 align:start position:0% contract that actually completes Oracle 00:55:44.500 --> 00:55:46.320 align:start position:0% contract that actually completes Oracle so<00:55:44.710> the<00:55:44.830> events<00:55:45.160> that<00:55:45.280> would<00:55:45.370> keep<00:55:45.580> token 00:55:46.320 --> 00:55:46.330 align:start position:0% so the events that would keep token 00:55:46.330 --> 00:55:48.750 align:start position:0% so the events that would keep token issuance<00:55:46.690> if<00:55:46.960> that<00:55:47.260> is<00:55:47.410> possible<00:55:47.920> which<00:55:48.100> feels 00:55:48.750 --> 00:55:48.760 align:start position:0% issuance if that is possible which feels 00:55:48.760 --> 00:55:51.600 align:start position:0% issuance if that is possible which feels like<00:55:48.880> it<00:55:49.180> is<00:55:49.330> in<00:55:50.320> which<00:55:50.560> side<00:55:50.860> does<00:55:51.100> that's<00:55:51.310> my 00:55:51.600 --> 00:55:51.610 align:start position:0% like it is in which side does that's my 00:55:51.610 --> 00:55:55.070 align:start position:0% like it is in which side does that's my contract<00:55:52.060> ago<00:55:52.530> and<00:55:53.530> I<00:55:53.890> mean<00:55:54.070> on<00:55:54.190> the<00:55:54.310> sense<00:55:54.520> of 00:55:55.070 --> 00:55:55.080 align:start position:0% contract ago and I mean on the sense of 00:55:55.080 --> 00:55:57.270 align:start position:0% contract ago and I mean on the sense of you<00:55:56.080> know<00:55:56.110> when<00:55:56.380> we<00:55:56.530> are<00:55:56.560> being<00:55:56.890> on<00:55:57.040> that<00:55:57.190> on 00:55:57.270 --> 00:55:57.280 align:start position:0% you know when we are being on that on 00:55:57.280 --> 00:55:59.940 align:start position:0% you know when we are being on that on the<00:55:57.370> on<00:55:57.400> chain<00:55:57.880> or<00:55:58.030> really<00:55:58.390> often<00:55:58.620> it<00:55:59.620> would<00:55:59.740> be 00:55:59.940 --> 00:55:59.950 align:start position:0% the on chain or really often it would be 00:55:59.950 --> 00:56:01.920 align:start position:0% the on chain or really often it would be combination<00:56:00.250> you<00:56:00.880> will<00:56:01.060> have<00:56:01.300> that<00:56:01.510> kind<00:56:01.750> of 00:56:01.920 --> 00:56:01.930 align:start position:0% combination you will have that kind of 00:56:01.930 --> 00:56:02.610 align:start position:0% combination you will have that kind of like 00:56:02.610 --> 00:56:02.620 align:start position:0% like 00:56:02.620 --> 00:56:05.100 align:start position:0% like on<00:56:02.920> both<00:56:03.100> sides<00:56:03.430> and<00:56:04.300> the<00:56:04.600> you<00:56:04.690> would<00:56:04.840> execute 00:56:05.100 --> 00:56:05.110 align:start position:0% on both sides and the you would execute 00:56:05.110 --> 00:56:07.140 align:start position:0% on both sides and the you would execute the<00:56:05.410> part<00:56:05.650> of<00:56:05.800> the<00:56:05.920> court<00:56:06.190> Indian<00:56:06.670> clay<00:56:06.910> for 00:56:07.140 --> 00:56:07.150 align:start position:0% the part of the court Indian clay for 00:56:07.150 --> 00:56:09.210 align:start position:0% the part of the court Indian clay for example<00:56:07.630> so<00:56:07.870> they'll<00:56:08.170> keep<00:56:08.410> information<00:56:09.070> that 00:56:09.210 --> 00:56:09.220 align:start position:0% example so they'll keep information that 00:56:09.220 --> 00:56:11.490 align:start position:0% example so they'll keep information that don't<00:56:09.580> only<00:56:10.030> been<00:56:10.240> quite<00:56:10.540> political<00:56:11.320> on<00:56:11.470> the 00:56:11.490 --> 00:56:11.500 align:start position:0% don't only been quite political on the 00:56:11.500 --> 00:56:13.110 align:start position:0% don't only been quite political on the complaints<00:56:12.070> but<00:56:12.280> at<00:56:12.430> the<00:56:12.490> same<00:56:12.670> time<00:56:12.910> you're 00:56:13.110 --> 00:56:13.120 align:start position:0% complaints but at the same time you're 00:56:13.120 --> 00:56:14.910 align:start position:0% complaints but at the same time you're going<00:56:13.270> to<00:56:13.450> their<00:56:13.660> function<00:56:13.900> information<00:56:14.770> that 00:56:14.910 --> 00:56:14.920 align:start position:0% going to their function information that 00:56:14.920 --> 00:56:17.220 align:start position:0% going to their function information that they're<00:56:15.130> waiting<00:56:15.630> Democratic<00:56:16.630> know<00:56:16.930> for<00:56:17.140> what 00:56:17.220 --> 00:56:17.230 align:start position:0% they're waiting Democratic know for what 00:56:17.230 --> 00:56:19.470 align:start position:0% they're waiting Democratic know for what excited<00:56:17.800> is<00:56:17.920> out<00:56:18.100> there<00:56:18.310> shorted<00:56:18.700> it<00:56:18.970> was<00:56:19.390> a 00:56:19.470 --> 00:56:19.480 align:start position:0% excited is out there shorted it was a 00:56:19.480 --> 00:56:21.660 align:start position:0% excited is out there shorted it was a typical<00:56:19.690> the<00:56:20.110> better<00:56:20.830> at<00:56:21.040> actually<00:56:21.400> like 00:56:21.660 --> 00:56:21.670 align:start position:0% typical the better at actually like 00:56:21.670 --> 00:56:26.090 align:start position:0% typical the better at actually like using<00:56:22.060> the<00:56:23.520> villager<00:56:24.520> Evelyn 00:56:26.090 --> 00:56:26.100 align:start position:0% using the villager Evelyn 00:56:26.100 --> 00:56:32.760 align:start position:0% using the villager Evelyn so<00:56:28.200> we<00:56:29.250> heard<00:56:30.250> about<00:56:30.430> the<00:56:30.850> EE<00:56:31.560> excited<00:56:32.560> use 00:56:32.760 --> 00:56:32.770 align:start position:0% so we heard about the EE excited use 00:56:32.770 --> 00:56:34.530 align:start position:0% so we heard about the EE excited use case<00:56:33.070> but<00:56:33.520> we're<00:56:33.700> going<00:56:33.940> to<00:56:34.090> hear<00:56:34.270> about<00:56:34.300> a 00:56:34.530 --> 00:56:34.540 align:start position:0% case but we're going to hear about a 00:56:34.540 --> 00:56:37.320 align:start position:0% case but we're going to hear about a couple<00:56:35.050> more<00:56:35.200> eccentric<00:56:35.650> use<00:56:35.980> cases<00:56:36.250> but<00:56:37.150> now 00:56:37.320 --> 00:56:37.330 align:start position:0% couple more eccentric use cases but now 00:56:37.330 --> 00:56:39.450 align:start position:0% couple more eccentric use cases but now I<00:56:37.360> have<00:56:37.930> a<00:56:37.960> privilege<00:56:38.290> to<00:56:38.530> talk<00:56:38.860> about<00:56:39.190> the 00:56:39.450 --> 00:56:39.460 align:start position:0% I have a privilege to talk about the 00:56:39.460 --> 00:56:41.280 align:start position:0% I have a privilege to talk about the most<00:56:39.700> famous<00:56:40.150> of<00:56:40.450> the<00:56:40.540> most<00:56:40.750> boring<00:56:40.990> Hughes 00:56:41.280 --> 00:56:41.290 align:start position:0% most famous of the most boring Hughes 00:56:41.290 --> 00:56:45.000 align:start position:0% most famous of the most boring Hughes case<00:56:41.530> hello<00:56:42.010> world<00:56:42.270> so<00:56:43.470> episode<00:56:44.470> that<00:56:44.740> though 00:56:45.000 --> 00:56:45.010 align:start position:0% case hello world so episode that though 00:56:45.010 --> 00:56:46.260 align:start position:0% case hello world so episode that though we<00:56:45.250> cannot<00:56:45.490> know<00:56:45.700> forever 00:56:46.260 --> 00:56:46.270 align:start position:0% we cannot know forever 00:56:46.270 --> 00:56:48.570 align:start position:0% we cannot know forever so<00:56:46.420> what<00:56:46.750> actually<00:56:46.930> brings<00:56:47.470> together<00:56:47.890> the<00:56:48.400> all 00:56:48.570 --> 00:56:48.580 align:start position:0% so what actually brings together the all 00:56:48.580 --> 00:56:49.800 align:start position:0% so what actually brings together the all use<00:56:48.790> cases<00:56:49.030> you're<00:56:49.300> going<00:56:49.480> to<00:56:49.570> hear<00:56:49.780> today 00:56:49.800 --> 00:56:49.810 align:start position:0% use cases you're going to hear today 00:56:49.810 --> 00:56:54.110 align:start position:0% use cases you're going to hear today about<00:56:50.460> exactly<00:56:51.460> that<00:56:51.640> under<00:56:52.120> easily<00:56:52.570> have<00:56:52.840> the 00:56:54.110 --> 00:56:54.120 align:start position:0% about exactly that under easily have the 00:56:54.120 --> 00:56:59.100 align:start position:0% about exactly that under easily have the liberal<00:56:55.120> end<00:56:55.270> of<00:56:55.600> a<00:56:55.720> long<00:56:58.110> residence 00:56:59.100 --> 00:56:59.110 align:start position:0% liberal end of a long residence 00:56:59.110 --> 00:57:00.740 align:start position:0% liberal end of a long residence implementation<00:56:59.830> of<00:56:59.950> the<00:57:00.070> trusted 00:57:00.740 --> 00:57:00.750 align:start position:0% implementation of the trusted 00:57:00.750 --> 00:57:03.510 align:start position:0% implementation of the trusted communication<00:57:01.750> so<00:57:01.930> that<00:57:01.960> is<00:57:02.230> how<00:57:02.650> operator<00:57:03.250> of 00:57:03.510 --> 00:57:03.520 align:start position:0% communication so that is how operator of 00:57:03.520 --> 00:57:07.800 align:start position:0% communication so that is how operator of power<00:57:03.760> the<00:57:04.030> he<00:57:04.630> may<00:57:04.750> work<00:57:04.960> together<00:57:05.970> so<00:57:06.970> before 00:57:07.800 --> 00:57:07.810 align:start position:0% power the he may work together so before 00:57:07.810 --> 00:57:09.900 align:start position:0% power the he may work together so before we're<00:57:07.930> going<00:57:08.110> to<00:57:08.290> Julie<00:57:08.770> and<00:57:09.130> initially<00:57:09.850> it 00:57:09.900 --> 00:57:09.910 align:start position:0% we're going to Julie and initially it 00:57:09.910 --> 00:57:12.510 align:start position:0% we're going to Julie and initially it was<00:57:10.060> intended<00:57:10.480> as<00:57:10.720> a<00:57:10.750> tutorial<00:57:11.140> so<00:57:11.710> we<00:57:12.250> don't 00:57:12.510 --> 00:57:12.520 align:start position:0% was intended as a tutorial so we don't 00:57:12.520 --> 00:57:14.970 align:start position:0% was intended as a tutorial so we don't have<00:57:12.760> the<00:57:13.090> ability<00:57:13.270> to<00:57:13.630> go<00:57:13.930> to<00:57:14.290> do<00:57:14.530> this<00:57:14.650> hands 00:57:14.970 --> 00:57:14.980 align:start position:0% have the ability to go to do this hands 00:57:14.980 --> 00:57:17.430 align:start position:0% have the ability to go to do this hands upon<00:57:15.220> so<00:57:15.910> that<00:57:15.940> is<00:57:16.240> why<00:57:16.390> I'm<00:57:16.510> going<00:57:16.720> to<00:57:16.900> kinda 00:57:17.430 --> 00:57:17.440 align:start position:0% upon so that is why I'm going to kinda 00:57:17.440 --> 00:57:19.200 align:start position:0% upon so that is why I'm going to kinda let<00:57:17.560> go<00:57:17.770> through<00:57:18.160> these<00:57:18.340> steps<00:57:18.610> what<00:57:18.850> it<00:57:18.970> takes 00:57:19.200 --> 00:57:19.210 align:start position:0% let go through these steps what it takes 00:57:19.210 --> 00:57:21.690 align:start position:0% let go through these steps what it takes to<00:57:19.420> go<00:57:19.570> into<00:57:19.900> sort<00:57:20.020> of<00:57:20.110> a<00:57:20.230> to<00:57:20.950> build<00:57:21.130> HelloWorld 00:57:21.690 --> 00:57:21.700 align:start position:0% to go into sort of a to build HelloWorld 00:57:21.700 --> 00:57:25.050 align:start position:0% to go into sort of a to build HelloWorld application<00:57:22.140> but<00:57:23.140> then<00:57:23.550> first<00:57:24.550> we<00:57:24.790> need<00:57:24.940> to 00:57:25.050 --> 00:57:25.060 align:start position:0% application but then first we need to 00:57:25.060 --> 00:57:27.510 align:start position:0% application but then first we need to stop<00:57:25.300> is<00:57:25.480> a<00:57:25.510> little<00:57:25.840> bit<00:57:25.990> deeper<00:57:26.260> ground<00:57:26.770> and 00:57:27.510 --> 00:57:27.520 align:start position:0% stop is a little bit deeper ground and 00:57:27.520 --> 00:57:29.850 align:start position:0% stop is a little bit deeper ground and the<00:57:28.090> neutral<00:57:28.630> background<00:57:28.870> they<00:57:29.230> really<00:57:29.680> don't 00:57:29.850 --> 00:57:29.860 align:start position:0% the neutral background they really don't 00:57:29.860 --> 00:57:31.550 align:start position:0% the neutral background they really don't just<00:57:30.190> understand<00:57:30.790> what<00:57:31.000> is<00:57:31.150> needed 00:57:31.550 --> 00:57:31.560 align:start position:0% just understand what is needed 00:57:31.560 --> 00:57:33.550 align:start position:0% just understand what is needed absolutely<00:57:32.560> beautiful 00:57:33.550 --> 00:57:33.560 align:start position:0% absolutely beautiful 00:57:33.560 --> 00:57:36.970 align:start position:0% absolutely beautiful application<00:57:34.280> so<00:57:34.520> he<00:57:35.030> definitely<00:57:35.980> religion 00:57:36.970 --> 00:57:36.980 align:start position:0% application so he definitely religion 00:57:36.980 --> 00:57:38.410 align:start position:0% application so he definitely religion alone<00:57:37.220> in<00:57:37.610> three<00:57:37.850> parts 00:57:38.410 --> 00:57:38.420 align:start position:0% alone in three parts 00:57:38.420 --> 00:57:40.540 align:start position:0% alone in three parts it's<00:57:38.570> a<00:57:38.660> trusted<00:57:39.050> computing<00:57:39.320> service<00:57:39.800> that 00:57:40.540 --> 00:57:40.550 align:start position:0% it's a trusted computing service that 00:57:40.550 --> 00:57:44.500 align:start position:0% it's a trusted computing service that runs<00:57:40.790> the<00:57:42.010> workloads<00:57:43.010> and<00:57:43.610> managers<00:57:44.330> map 00:57:44.500 --> 00:57:44.510 align:start position:0% runs the workloads and managers map 00:57:44.510 --> 00:57:47.380 align:start position:0% runs the workloads and managers map there<00:57:45.380> is<00:57:45.530> there<00:57:46.340> are<00:57:46.370> smart<00:57:46.850> contracts<00:57:47.210> that 00:57:47.380 --> 00:57:47.390 align:start position:0% there is there are smart contracts that 00:57:47.390 --> 00:57:49.420 align:start position:0% there is there are smart contracts that run<00:57:47.630> in<00:57:47.840> a<00:57:47.930> stadium<00:57:48.140> that<00:57:48.680> allows<00:57:48.980> you<00:57:49.250> to 00:57:49.420 --> 00:57:49.430 align:start position:0% run in a stadium that allows you to 00:57:49.430 --> 00:57:52.090 align:start position:0% run in a stadium that allows you to involve<00:57:49.790> these<00:57:50.390> workloads<00:57:51.080> in<00:57:51.500> the<00:57:51.710> trusted 00:57:52.090 --> 00:57:52.100 align:start position:0% involve these workloads in the trusted 00:57:52.100 --> 00:57:54.100 align:start position:0% involve these workloads in the trusted public<00:57:52.190> service<00:57:52.760> and<00:57:53.180> there<00:57:53.840> are<00:57:53.960> always 00:57:54.100 --> 00:57:54.110 align:start position:0% public service and there are always 00:57:54.110 --> 00:57:56.020 align:start position:0% public service and there are always requested<00:57:54.920> for<00:57:55.100> wants<00:57:55.340> to<00:57:55.550> make<00:57:55.790> this 00:57:56.020 --> 00:57:56.030 align:start position:0% requested for wants to make this 00:57:56.030 --> 00:58:01.510 align:start position:0% requested for wants to make this execution<00:57:56.810> and<00:57:59.560> colors<00:58:00.560> very<00:58:00.980> different<00:58:01.370> them 00:58:01.510 --> 00:58:01.520 align:start position:0% execution and colors very different them 00:58:01.520 --> 00:58:07.320 align:start position:0% execution and colors very different them so<00:58:02.150> now<00:58:02.270> a<00:58:02.300> little<00:58:02.510> bit<00:58:02.780> about<00:58:02.930> the<00:58:03.230> colors<00:58:03.590> the 00:58:07.320 --> 00:58:07.330 align:start position:0% 00:58:07.330 --> 00:58:10.090 align:start position:0% take<00:58:08.330> the<00:58:08.540> dark<00:58:08.780> bull<00:58:09.020> in<00:58:09.290> these<00:58:09.800> cases 00:58:10.090 --> 00:58:10.100 align:start position:0% take the dark bull in these cases 00:58:10.100 --> 00:58:12.310 align:start position:0% take the dark bull in these cases actually<00:58:10.520> that<00:58:11.210> is<00:58:11.360> the<00:58:11.510> application<00:58:11.690> code 00:58:12.310 --> 00:58:12.320 align:start position:0% actually that is the application code 00:58:12.320 --> 00:58:15.730 align:start position:0% actually that is the application code and<00:58:12.470> they<00:58:12.710> everything<00:58:13.310> else<00:58:14.020> that<00:58:15.020> is<00:58:15.350> the 00:58:15.730 --> 00:58:15.740 align:start position:0% and they everything else that is the 00:58:15.740 --> 00:58:19.120 align:start position:0% and they everything else that is the quote<00:58:16.160> that<00:58:16.430> is<00:58:16.880> the<00:58:17.150> people<00:58:17.510> in<00:58:18.440> the<00:58:18.650> common 00:58:19.120 --> 00:58:19.130 align:start position:0% quote that is the people in the common 00:58:19.130 --> 00:58:21.760 align:start position:0% quote that is the people in the common for<00:58:19.370> the<00:58:19.460> all<00:58:19.730> applications<00:58:20.560> so<00:58:21.560> the 00:58:21.760 --> 00:58:21.770 align:start position:0% for the all applications so the 00:58:21.770 --> 00:58:24.280 align:start position:0% for the all applications so the applications<00:58:22.520> in<00:58:23.300> order<00:58:23.420> to<00:58:23.660> do<00:58:23.750> application 00:58:24.280 --> 00:58:24.290 align:start position:0% applications in order to do application 00:58:24.290 --> 00:58:26.680 align:start position:0% applications in order to do application you<00:58:24.380> need<00:58:24.500> to<00:58:24.680> do<00:58:24.800> three<00:58:25.250> parts<00:58:25.700> different<00:58:26.120> UI 00:58:26.680 --> 00:58:26.690 align:start position:0% you need to do three parts different UI 00:58:26.690 --> 00:58:30.280 align:start position:0% you need to do three parts different UI you<00:58:27.290> need<00:58:27.470> to<00:58:27.680> build<00:58:27.920> the<00:58:28.810> smart<00:58:29.810> contracts 00:58:30.280 --> 00:58:30.290 align:start position:0% you need to build the smart contracts 00:58:30.290 --> 00:58:32.530 align:start position:0% you need to build the smart contracts you<00:58:30.410> may<00:58:30.620> use<00:58:30.890> these<00:58:31.220> marketers<00:58:31.760> provided<00:58:32.360> by 00:58:32.530 --> 00:58:32.540 align:start position:0% you may use these marketers provided by 00:58:32.540 --> 00:58:34.750 align:start position:0% you may use these marketers provided by the<00:58:32.600> accelerator<00:58:33.170> alone<00:58:33.620> or<00:58:34.160> you<00:58:34.340> might<00:58:34.550> need 00:58:34.750 --> 00:58:34.760 align:start position:0% the accelerator alone or you might need 00:58:34.760 --> 00:58:37.440 align:start position:0% the accelerator alone or you might need to<00:58:35.060> modify<00:58:35.180> them<00:58:35.630> and<00:58:35.780> build<00:58:35.990> your<00:58:36.320> additional 00:58:37.440 --> 00:58:37.450 align:start position:0% to modify them and build your additional 00:58:37.450 --> 00:58:41.200 align:start position:0% to modify them and build your additional smart<00:58:38.450> contracts<00:58:39.490> in<00:58:40.490> the<00:58:40.550> allocate<00:58:41.090> these 00:58:41.200 --> 00:58:41.210 align:start position:0% smart contracts in the allocate these 00:58:41.210 --> 00:58:43.600 align:start position:0% smart contracts in the allocate these parts<00:58:41.660> is<00:58:41.810> actually<00:58:42.410> well<00:58:43.070> known<00:58:43.100> how<00:58:43.550> to 00:58:43.600 --> 00:58:43.610 align:start position:0% parts is actually well known how to 00:58:43.610 --> 00:58:46.570 align:start position:0% parts is actually well known how to build<00:58:44.000> but<00:58:44.270> the<00:58:44.770> workloads<00:58:45.770> is<00:58:46.040> actually<00:58:46.370> very 00:58:46.570 --> 00:58:46.580 align:start position:0% build but the workloads is actually very 00:58:46.580 --> 00:58:48.040 align:start position:0% build but the workloads is actually very new<00:58:46.850> that<00:58:47.150> is<00:58:47.300> why<00:58:47.420> we're<00:58:47.630> going<00:58:47.810> to<00:58:47.900> focus 00:58:48.040 --> 00:58:48.050 align:start position:0% new that is why we're going to focus 00:58:48.050 --> 00:58:50.050 align:start position:0% new that is why we're going to focus with<00:58:48.320> a<00:58:48.470> only<00:58:48.980> on<00:58:49.190> how<00:58:49.400> to<00:58:49.460> build<00:58:49.790> these 00:58:50.050 --> 00:58:50.060 align:start position:0% with a only on how to build these 00:58:50.060 --> 00:58:54.880 align:start position:0% with a only on how to build these workers<00:58:52.390> so<00:58:53.390> we're<00:58:54.050> going<00:58:54.230> to<00:58:54.530> pretty<00:58:54.740> much 00:58:54.880 --> 00:58:54.890 align:start position:0% workers so we're going to pretty much 00:58:54.890 --> 00:58:56.830 align:start position:0% workers so we're going to pretty much the<00:58:55.190> field<00:58:55.370> the<00:58:55.550> hello<00:58:55.790> mobile<00:58:56.030> application 00:58:56.830 --> 00:58:56.840 align:start position:0% the field the hello mobile application 00:58:56.840 --> 00:58:59.530 align:start position:0% the field the hello mobile application and<00:58:57.080> the<00:58:57.230> learn<00:58:57.800> how<00:58:58.100> to<00:58:58.270> build<00:58:59.270> your<00:58:59.360> own 00:58:59.530 --> 00:58:59.540 align:start position:0% and the learn how to build your own 00:58:59.540 --> 00:59:06.490 align:start position:0% and the learn how to build your own example<00:59:03.460> so<00:59:04.460> our<00:59:05.000> core<00:59:05.630> application<00:59:06.170> going<00:59:06.380> to 00:59:06.490 --> 00:59:06.500 align:start position:0% example so our core application going to 00:59:06.500 --> 00:59:08.200 align:start position:0% example so our core application going to be<00:59:06.590> pretty<00:59:06.830> simple<00:59:07.100> is<00:59:07.280> going<00:59:07.520> to<00:59:07.640> take<00:59:07.880> as<00:59:08.060> an 00:59:08.200 --> 00:59:08.210 align:start position:0% be pretty simple is going to take as an 00:59:08.210 --> 00:59:10.120 align:start position:0% be pretty simple is going to take as an input<00:59:08.570> list<00:59:08.870> of<00:59:09.080> names<00:59:09.320> and<00:59:09.650> is<00:59:09.800> going<00:59:10.010> to 00:59:10.120 --> 00:59:10.130 align:start position:0% input list of names and is going to 00:59:10.130 --> 00:59:13.540 align:start position:0% input list of names and is going to depend<00:59:10.490> the<00:59:11.020> hello<00:59:12.020> to<00:59:12.350> each<00:59:12.620> name<00:59:12.980> and<00:59:13.310> if 00:59:13.540 --> 00:59:13.550 align:start position:0% depend the hello to each name and if 00:59:13.550 --> 00:59:16.180 align:start position:0% depend the hello to each name and if notice<00:59:13.940> as<00:59:14.150> a<00:59:14.180> result<00:59:14.600> and<00:59:14.900> we<00:59:15.380> encourage<00:59:16.010> the 00:59:16.180 --> 00:59:16.190 align:start position:0% notice as a result and we encourage the 00:59:16.190 --> 00:59:18.150 align:start position:0% notice as a result and we encourage the building<00:59:16.370> the<00:59:17.020> application 00:59:18.150 --> 00:59:18.160 align:start position:0% building the application 00:59:18.160 --> 00:59:21.210 align:start position:0% building the application and<00:59:18.430> anywhere<00:59:19.000> in<00:59:19.630> the<00:59:19.779> two<00:59:19.990> stages<00:59:20.289> first<00:59:20.500> get 00:59:21.210 --> 00:59:21.220 align:start position:0% and anywhere in the two stages first get 00:59:21.220 --> 00:59:23.609 align:start position:0% and anywhere in the two stages first get it<00:59:21.339> plugged<00:59:22.000> in<00:59:22.119> into<00:59:22.750> the<00:59:22.869> framework<00:59:23.230> and 00:59:23.609 --> 00:59:23.619 align:start position:0% it plugged in into the framework and 00:59:23.619 --> 00:59:25.640 align:start position:0% it plugged in into the framework and then<00:59:23.980> actually<00:59:24.369> build<00:59:24.670> your<00:59:24.700> business<00:59:25.059> coach 00:59:25.640 --> 00:59:25.650 align:start position:0% then actually build your business coach 00:59:25.650 --> 00:59:28.319 align:start position:0% then actually build your business coach so<00:59:26.650> in<00:59:26.950> the<00:59:27.099> great<00:59:27.279> follow<00:59:27.609> the<00:59:27.819> same<00:59:28.000> pattern 00:59:28.319 --> 00:59:28.329 align:start position:0% so in the great follow the same pattern 00:59:28.329 --> 00:59:32.880 align:start position:0% so in the great follow the same pattern today<00:59:30.509> so<00:59:31.509> there<00:59:31.839> are<00:59:31.930> a<00:59:31.960> couple<00:59:31.990> dependences 00:59:32.880 --> 00:59:32.890 align:start position:0% today so there are a couple dependences 00:59:32.890 --> 00:59:34.200 align:start position:0% today so there are a couple dependences that<00:59:33.099> we<00:59:33.220> should<00:59:33.460> be<00:59:33.609> aware 00:59:34.200 --> 00:59:34.210 align:start position:0% that we should be aware 00:59:34.210 --> 00:59:37.140 align:start position:0% that we should be aware so<00:59:34.420> the<00:59:34.630> each<00:59:35.559> workout<00:59:36.069> has<00:59:36.430> to<00:59:36.670> contain<00:59:37.000> it 00:59:37.140 --> 00:59:37.150 align:start position:0% so the each workout has to contain it 00:59:37.150 --> 00:59:41.309 align:start position:0% so the each workout has to contain it from<00:59:37.390> the<00:59:37.539> class<00:59:38.130> process<00:59:39.390> workload<00:59:40.390> and<00:59:41.259> the 00:59:41.309 --> 00:59:41.319 align:start position:0% from the class process workload and the 00:59:41.319 --> 00:59:44.039 align:start position:0% from the class process workload and the test<00:59:41.859> implemented<00:59:42.250> one<00:59:42.940> virtual<00:59:43.630> function 00:59:44.039 --> 00:59:44.049 align:start position:0% test implemented one virtual function 00:59:44.049 --> 00:59:46.109 align:start position:0% test implemented one virtual function and<00:59:44.259> it's<00:59:44.769> been<00:59:45.039> closed<00:59:45.309> a<00:59:45.400> couple<00:59:45.579> markers 00:59:46.109 --> 00:59:46.119 align:start position:0% and it's been closed a couple markers 00:59:46.119 --> 00:59:47.789 align:start position:0% and it's been closed a couple markers and<00:59:46.329> we'll<00:59:46.539> talk<00:59:46.779> about<00:59:46.930> the<00:59:47.230> details<00:59:47.529> of<00:59:47.740> that 00:59:47.789 --> 00:59:47.799 align:start position:0% and we'll talk about the details of that 00:59:47.799 --> 00:59:50.460 align:start position:0% and we'll talk about the details of that I<00:59:48.339> will<00:59:48.880> provide<00:59:49.180> a<00:59:49.359> number<00:59:49.539> of<00:59:49.960> templates 00:59:50.460 --> 00:59:50.470 align:start position:0% I will provide a number of templates 00:59:50.470 --> 00:59:55.019 align:start position:0% I will provide a number of templates that<00:59:51.160> actually<00:59:51.700> make<00:59:52.059> the<00:59:52.089> arm<00:59:53.880> pretty<00:59:54.880> much 00:59:55.019 --> 00:59:55.029 align:start position:0% that actually make the arm pretty much 00:59:55.029 --> 00:59:57.559 align:start position:0% that actually make the arm pretty much include<00:59:55.359> the<00:59:55.480> old<00:59:55.660> boiler<00:59:56.009> call<00:59:57.009> so<00:59:57.279> the 00:59:57.559 --> 00:59:57.569 align:start position:0% include the old boiler call so the 00:59:57.569 --> 01:00:00.089 align:start position:0% include the old boiler call so the boiler<00:59:58.569> plate<00:59:58.809> also<00:59:59.230> you<00:59:59.410> don't<00:59:59.619> need<00:59:59.859> really 01:00:00.089 --> 01:00:00.099 align:start position:0% boiler plate also you don't need really 01:00:00.099 --> 01:00:02.579 align:start position:0% boiler plate also you don't need really need<01:00:00.369> to<01:00:00.670> write<01:00:00.819> that<01:00:01.000> yourself<01:00:01.150> and<01:00:01.750> finally 01:00:02.579 --> 01:00:02.589 align:start position:0% need to write that yourself and finally 01:00:02.589 --> 01:00:04.559 align:start position:0% need to write that yourself and finally for<01:00:02.950> this<01:00:03.069> in<01:00:03.759> order<01:00:03.880> to<01:00:04.089> start<01:00:04.480> your 01:00:04.559 --> 01:00:04.569 align:start position:0% for this in order to start your 01:00:04.569 --> 01:00:05.940 align:start position:0% for this in order to start your development<01:00:05.019> you<01:00:05.170> don't<01:00:05.349> get<01:00:05.559> ready<01:00:05.769> to 01:00:05.940 --> 01:00:05.950 align:start position:0% development you don't get ready to 01:00:05.950 --> 01:00:08.279 align:start position:0% development you don't get ready to develop<01:00:06.190> immediately<01:00:06.819> applied<01:00:07.150> you<01:00:07.390> can<01:00:08.049> use 01:00:08.279 --> 01:00:08.289 align:start position:0% develop immediately applied you can use 01:00:08.289 --> 01:00:10.470 align:start position:0% develop immediately applied you can use the<01:00:08.470> generic<01:00:08.740> client<01:00:09.009> provided<01:00:09.730> with<01:00:10.299> the 01:00:10.470 --> 01:00:10.480 align:start position:0% the generic client provided with the 01:00:10.480 --> 01:00:16.620 align:start position:0% the generic client provided with the framework<01:00:10.750> to<01:00:11.559> test<01:00:11.589> your<01:00:12.039> application<01:00:14.819> so<01:00:15.819> at 01:00:16.620 --> 01:00:16.630 align:start position:0% framework to test your application so at 01:00:16.630 --> 01:00:19.019 align:start position:0% framework to test your application so at the<01:00:16.750> end<01:00:16.930> I'm<01:00:17.500> going<01:00:17.829> to<01:00:18.009> distribute<01:00:18.369> the<01:00:18.700> use 01:00:19.019 --> 01:00:19.029 align:start position:0% the end I'm going to distribute the use 01:00:19.029 --> 01:00:20.970 align:start position:0% the end I'm going to distribute the use this<01:00:19.269> as<01:00:19.480> I<01:00:19.599> said<01:00:19.660> that<01:00:20.079> we<01:00:20.259> plan<01:00:20.500> to<01:00:20.680> do<01:00:20.799> this 01:00:20.970 --> 01:00:20.980 align:start position:0% this as I said that we plan to do this 01:00:20.980 --> 01:00:23.009 align:start position:0% this as I said that we plan to do this happens<01:00:21.549> on<01:00:21.670> experience<01:00:22.210> so<01:00:22.299> they<01:00:22.569> include 01:00:23.009 --> 01:00:23.019 align:start position:0% happens on experience so they include 01:00:23.019 --> 01:00:24.029 align:start position:0% happens on experience so they include kind<01:00:23.259> of<01:00:23.410> like<01:00:23.559> a<01:00:23.589> and 01:00:24.029 --> 01:00:24.039 align:start position:0% kind of like a and 01:00:24.039 --> 01:00:26.880 align:start position:0% kind of like a and GT<01:00:24.789> version<01:00:25.059> so<01:00:25.660> it<01:00:25.779> has<01:00:26.019> the<01:00:26.230> all<01:00:26.470> components 01:00:26.880 --> 01:00:26.890 align:start position:0% GT version so it has the all components 01:00:26.890 --> 01:00:29.759 align:start position:0% GT version so it has the all components put<01:00:27.190> installed<01:00:27.700> and<01:00:28.059> it<01:00:28.269> has<01:00:28.539> the<01:00:28.809> even<01:00:29.589> the 01:00:29.759 --> 01:00:29.769 align:start position:0% put installed and it has the even the 01:00:29.769 --> 01:00:33.240 align:start position:0% put installed and it has the even the stage<01:00:30.279> one<01:00:30.579> preview<01:00:31.089> so<01:00:31.779> it's<01:00:31.900> even<01:00:32.740> kind<01:00:33.130> of 01:00:33.240 --> 01:00:33.250 align:start position:0% stage one preview so it's even kind of 01:00:33.250 --> 01:00:36.720 align:start position:0% stage one preview so it's even kind of example<01:00:33.849> the<01:00:34.740> without<01:00:35.740> really<01:00:36.130> going<01:00:36.430> to<01:00:36.700> a 01:00:36.720 --> 01:00:36.730 align:start position:0% example the without really going to a 01:00:36.730 --> 01:00:41.740 align:start position:0% example the without really going to a full<01:00:37.119> installation<01:00:37.359> and<01:00:37.990> see<01:00:38.410> how<01:00:38.740> it<01:00:38.890> works 01:00:41.740 --> 01:00:41.750 align:start position:0% 01:00:41.750 --> 01:00:45.770 align:start position:0% [Music] 01:00:45.770 --> 01:00:45.780 align:start position:0% 01:00:45.780 --> 01:00:47.750 align:start position:0% so<01:00:46.350> this<01:00:46.530> is<01:00:46.680> actually<01:00:46.830> let's<01:00:47.190> start<01:00:47.280> kind<01:00:47.670> of 01:00:47.750 --> 01:00:47.760 align:start position:0% so this is actually let's start kind of 01:00:47.760 --> 01:00:50.510 align:start position:0% so this is actually let's start kind of from<01:00:48.180> the<01:00:48.330> end<01:00:48.510> stage<01:00:49.260> one<01:00:49.560> the<01:00:49.890> what<01:00:50.220> we<01:00:50.310> want 01:00:50.510 --> 01:00:50.520 align:start position:0% from the end stage one the what we want 01:00:50.520 --> 01:00:52.370 align:start position:0% from the end stage one the what we want to<01:00:50.670> see<01:00:50.880> the<01:00:51.120> if<01:00:51.270> we<01:00:51.450> will<01:00:51.570> have<01:00:51.600> the<01:00:51.930> stage<01:00:52.170> one 01:00:52.370 --> 01:00:52.380 align:start position:0% to see the if we will have the stage one 01:00:52.380 --> 01:00:54.260 align:start position:0% to see the if we will have the stage one what<01:00:52.620> would<01:00:52.800> be<01:00:52.980> the<01:00:53.220> result<01:00:53.550> so<01:00:53.790> first<01:00:54.060> of<01:00:54.210> all 01:00:54.260 --> 01:00:54.270 align:start position:0% what would be the result so first of all 01:00:54.270 --> 01:00:58.340 align:start position:0% what would be the result so first of all we'll<01:00:54.450> start<01:00:54.900> the<01:00:55.140> IVA<01:00:56.090> Lisa<01:00:57.090> this<01:00:57.720> is<01:00:57.780> legal 01:00:58.340 --> 01:00:58.350 align:start position:0% we'll start the IVA Lisa this is legal 01:00:58.350 --> 01:01:01.400 align:start position:0% we'll start the IVA Lisa this is legal or<01:00:58.440> spin<01:00:58.890> and<01:00:59.520> it<01:01:00.000> will<01:01:00.030> start<01:01:00.420> at<01:01:00.540> the<01:01:00.660> client 01:01:01.400 --> 01:01:01.410 align:start position:0% or spin and it will start at the client 01:01:01.410 --> 01:01:03.470 align:start position:0% or spin and it will start at the client application<01:01:01.530> in<01:01:02.490> most<01:01:02.700> cases<01:01:02.910> just<01:01:03.090> when 01:01:03.470 --> 01:01:03.480 align:start position:0% application in most cases just when 01:01:03.480 --> 01:01:05.060 align:start position:0% application in most cases just when they're<01:01:03.630> going<01:01:03.750> to<01:01:03.810> try<01:01:04.050> and<01:01:04.080> don't<01:01:04.380> forget<01:01:04.740> to 01:01:05.060 --> 01:01:05.070 align:start position:0% they're going to try and don't forget to 01:01:05.070 --> 01:01:08.390 align:start position:0% they're going to try and don't forget to shortly<01:01:06.470> fancy<01:01:07.470> virtual<01:01:07.920> environment 01:01:08.390 --> 01:01:08.400 align:start position:0% shortly fancy virtual environment 01:01:08.400 --> 01:01:11.180 align:start position:0% shortly fancy virtual environment otherwise<01:01:08.730> nothing<01:01:09.210> going<01:01:09.420> to<01:01:09.480> work<01:01:10.010> so<01:01:11.010> when 01:01:11.180 --> 01:01:11.190 align:start position:0% otherwise nothing going to work so when 01:01:11.190 --> 01:01:12.560 align:start position:0% otherwise nothing going to work so when we<01:01:11.310> going<01:01:11.460> to<01:01:11.610> submit<01:01:11.880> the<01:01:12.000> command<01:01:12.360> the 01:01:12.560 --> 01:01:12.570 align:start position:0% we going to submit the command the 01:01:12.570 --> 01:01:14.480 align:start position:0% we going to submit the command the important<01:01:13.320> parts<01:01:13.620> we<01:01:13.740> said<01:01:13.920> meet<01:01:14.130> the<01:01:14.280> hello 01:01:14.480 --> 01:01:14.490 align:start position:0% important parts we said meet the hello 01:01:14.490 --> 01:01:16.670 align:start position:0% important parts we said meet the hello world<01:01:14.850> which<01:01:15.240> is<01:01:15.450> the<01:01:15.630> idea<01:01:16.110> of<01:01:16.230> the<01:01:16.320> workload 01:01:16.670 --> 01:01:16.680 align:start position:0% world which is the idea of the workload 01:01:16.680 --> 01:01:19.760 align:start position:0% world which is the idea of the workload that<01:01:17.160> we<01:01:18.060> built<01:01:18.330> and<01:01:18.540> the<01:01:18.870> data<01:01:19.200> and<01:01:19.590> it's 01:01:19.760 --> 01:01:19.770 align:start position:0% that we built and the data and it's 01:01:19.770 --> 01:01:22.190 align:start position:0% that we built and the data and it's involved<01:01:20.460> so<01:01:21.210> we're<01:01:21.570> going<01:01:21.720> to<01:01:21.810> get<01:01:22.020> the 01:01:22.190 --> 01:01:22.200 align:start position:0% involved so we're going to get the 01:01:22.200 --> 01:01:24.530 align:start position:0% involved so we're going to get the result<01:01:22.500> error<01:01:22.800> under<01:01:23.310> construction<01:01:23.940> and<01:01:24.120> at 01:01:24.530 --> 01:01:24.540 align:start position:0% result error under construction and at 01:01:24.540 --> 01:01:26.150 align:start position:0% result error under construction and at the<01:01:24.780> end<01:01:24.870> of<01:01:25.080> stage<01:01:25.350> one<01:01:25.620> that<01:01:25.860> has<01:01:26.010> the 01:01:26.150 --> 01:01:26.160 align:start position:0% the end of stage one that has the 01:01:26.160 --> 01:01:28.610 align:start position:0% the end of stage one that has the expected<01:01:26.820> output<01:01:27.150> because<01:01:27.810> at<01:01:27.930> this<01:01:28.050> time<01:01:28.110> all 01:01:28.610 --> 01:01:28.620 align:start position:0% expected output because at this time all 01:01:28.620 --> 01:01:30.350 align:start position:0% expected output because at this time all they<01:01:28.770> care<01:01:29.070> they<01:01:29.400> want<01:01:29.580> to<01:01:29.730> make<01:01:29.910> sure<01:01:29.940> that 01:01:30.350 --> 01:01:30.360 align:start position:0% they care they want to make sure that 01:01:30.360 --> 01:01:34.040 align:start position:0% they care they want to make sure that hello<01:01:30.750> world<01:01:31.080> what<01:01:31.890> was<01:01:32.310> the<01:01:32.790> message<01:01:33.630> has 01:01:34.040 --> 01:01:34.050 align:start position:0% hello world what was the message has 01:01:34.050 --> 01:01:37.250 align:start position:0% hello world what was the message has come<01:01:34.080> to<01:01:34.830> the<01:01:34.980> hour<01:01:35.270> that<01:01:36.270> we<01:01:36.600> just<01:01:36.780> integrated 01:01:37.250 --> 01:01:37.260 align:start position:0% come to the hour that we just integrated 01:01:37.260 --> 01:01:40.670 align:start position:0% come to the hour that we just integrated in<01:01:37.650> the<01:01:37.830> framework<01:01:38.760> but<01:01:39.420> we<01:01:39.900> don't<01:01:40.410> really 01:01:40.670 --> 01:01:40.680 align:start position:0% in the framework but we don't really 01:01:40.680 --> 01:01:43.450 align:start position:0% in the framework but we don't really have<01:01:40.950> our<01:01:41.220> own<01:01:41.520> business<01:01:41.970> logic<01:01:42.180> that<01:01:42.540> yet 01:01:43.450 --> 01:01:43.460 align:start position:0% have our own business logic that yet 01:01:43.460 --> 01:01:48.740 align:start position:0% have our own business logic that yet next<01:01:44.460> time<01:01:46.370> so<01:01:47.370> what<01:01:48.030> this<01:01:48.180> actually<01:01:48.360> it 01:01:48.740 --> 01:01:48.750 align:start position:0% next time so what this actually it 01:01:48.750 --> 01:01:51.230 align:start position:0% next time so what this actually it really<01:01:49.140> takes<01:01:49.440> to<01:01:49.590> get<01:01:50.340> to<01:01:50.400> the<01:01:50.730> stage<01:01:51.000> one 01:01:51.230 --> 01:01:51.240 align:start position:0% really takes to get to the stage one 01:01:51.240 --> 01:01:53.630 align:start position:0% really takes to get to the stage one first<01:01:51.960> of<01:01:52.260> all<01:01:52.410> we<01:01:52.830> need<01:01:53.010> to<01:01:53.040> create<01:01:53.310> a<01:01:53.430> folder 01:01:53.630 --> 01:01:53.640 align:start position:0% first of all we need to create a folder 01:01:53.640 --> 01:01:55.850 align:start position:0% first of all we need to create a folder like<01:01:54.150> an<01:01:54.300> any<01:01:54.510> application<01:01:55.080> and<01:01:55.200> that<01:01:55.290> fellow 01:01:55.850 --> 01:01:55.860 align:start position:0% like an any application and that fellow 01:01:55.860 --> 01:01:58.100 align:start position:0% like an any application and that fellow work<01:01:56.130> application<01:01:56.760> name<01:01:57.390> we<01:01:57.600> have<01:01:57.810> to<01:01:57.930> keep 01:01:58.100 --> 01:01:58.110 align:start position:0% work application name we have to keep 01:01:58.110 --> 01:01:59.510 align:start position:0% work application name we have to keep because<01:01:58.260> we<01:01:58.560> don't<01:01:58.740> need<01:01:58.860> to<01:01:59.010> use<01:01:59.160> this<01:01:59.310> name 01:01:59.510 --> 01:01:59.520 align:start position:0% because we don't need to use this name 01:01:59.520 --> 01:02:01.640 align:start position:0% because we don't need to use this name couple<01:01:59.970> times<01:02:00.180> more<01:02:00.480> in<01:02:00.720> the<01:02:00.930> updates<01:02:01.410> with 01:02:01.640 --> 01:02:01.650 align:start position:0% couple times more in the updates with 01:02:01.650 --> 01:02:04.670 align:start position:0% couple times more in the updates with fans<01:02:01.950> we<01:02:02.850> will<01:02:03.030> need<01:02:03.300> to<01:02:03.540> cut<01:02:03.930> it<01:02:04.140> to<01:02:04.470> play 01:02:04.670 --> 01:02:04.680 align:start position:0% fans we will need to cut it to play 01:02:04.680 --> 01:02:07.100 align:start position:0% fans we will need to cut it to play files<01:02:05.010> from<01:02:05.490> the<01:02:05.700> folder<01:02:05.970> where<01:02:06.600> we<01:02:06.660> give<01:02:06.930> them 01:02:07.100 --> 01:02:07.110 align:start position:0% files from the folder where we give them 01:02:07.110 --> 01:02:10.340 align:start position:0% files from the folder where we give them and<01:02:07.610> they<01:02:08.610> need<01:02:09.060> to<01:02:09.240> play<01:02:09.420> update<01:02:09.900> couple 01:02:10.340 --> 01:02:10.350 align:start position:0% and they need to play update couple 01:02:10.350 --> 01:02:11.900 align:start position:0% and they need to play update couple files<01:02:10.590> in<01:02:11.070> the<01:02:11.280> email 01:02:11.900 --> 01:02:11.910 align:start position:0% files in the email 01:02:11.910 --> 01:02:13.700 align:start position:0% files in the email among<01:02:12.390> those<01:02:12.540> templates<01:02:12.990> and<01:02:13.230> couple<01:02:13.560> more 01:02:13.700 --> 01:02:13.710 align:start position:0% among those templates and couple more 01:02:13.710 --> 01:02:19.550 align:start position:0% among those templates and couple more build<01:02:14.040> files<01:02:14.310> in<01:02:15.300> the<01:02:15.540> framework<01:02:16.260> itself<01:02:18.560> so 01:02:19.550 --> 01:02:19.560 align:start position:0% build files in the framework itself so 01:02:19.560 --> 01:02:22.040 align:start position:0% build files in the framework itself so the<01:02:19.920> first<01:02:20.790> of<01:02:21.000> all<01:02:21.090> there<01:02:21.540> are<01:02:21.630> three<01:02:21.690> files 01:02:22.040 --> 01:02:22.050 align:start position:0% the first of all there are three files 01:02:22.050 --> 01:02:26.960 align:start position:0% the first of all there are three files that<01:02:22.470> actually<01:02:23.130> allows<01:02:23.460> to<01:02:23.940> build<01:02:24.240> the<01:02:25.970> hello 01:02:26.960 --> 01:02:26.970 align:start position:0% that actually allows to build the hello 01:02:26.970 --> 01:02:28.160 align:start position:0% that actually allows to build the hello world 01:02:28.160 --> 01:02:28.170 align:start position:0% world 01:02:28.170 --> 01:02:30.710 align:start position:0% world so<01:02:28.530> first<01:02:28.800> one<01:02:29.070> that<01:02:30.000> was<01:02:30.180> actually<01:02:30.360> one<01:02:30.690> of 01:02:30.710 --> 01:02:30.720 align:start position:0% so first one that was actually one of 01:02:30.720 --> 01:02:33.290 align:start position:0% so first one that was actually one of the<01:02:30.900> two<01:02:31.020> played<01:02:31.230> files<01:02:31.550> that<01:02:32.550> is<01:02:32.760> the<01:02:32.880> top<01:02:33.090> one 01:02:33.290 --> 01:02:33.300 align:start position:0% the two played files that is the top one 01:02:33.300 --> 01:02:35.450 align:start position:0% the two played files that is the top one the<01:02:33.510> controls<01:02:34.350> how<01:02:34.560> to<01:02:34.800> do<01:02:34.950> the<01:02:35.100> static 01:02:35.450 --> 01:02:35.460 align:start position:0% the controls how to do the static 01:02:35.460 --> 01:02:38.420 align:start position:0% the controls how to do the static library<01:02:35.940> the<01:02:36.600> second<01:02:36.990> one<01:02:37.170> is<01:02:37.470> actually<01:02:37.980> the 01:02:38.420 --> 01:02:38.430 align:start position:0% library the second one is actually the 01:02:38.430 --> 01:02:40.970 align:start position:0% library the second one is actually the includes<01:02:39.120> the<01:02:39.630> building<01:02:40.080> or<01:02:40.380> this<01:02:40.560> particular 01:02:40.970 --> 01:02:40.980 align:start position:0% includes the building or this particular 01:02:40.980 --> 01:02:43.460 align:start position:0% includes the building or this particular static<01:02:41.670> library<01:02:42.060> into<01:02:42.780> the<01:02:42.900> overall<01:02:43.230> due 01:02:43.460 --> 01:02:43.470 align:start position:0% static library into the overall due 01:02:43.470 --> 01:02:46.370 align:start position:0% static library into the overall due process<01:02:43.980> and<01:02:44.220> the<01:02:44.430> third<01:02:44.670> one<01:02:44.940> is<01:02:45.300> links<01:02:46.200> that 01:02:46.370 --> 01:02:46.380 align:start position:0% process and the third one is links that 01:02:46.380 --> 01:02:48.650 align:start position:0% process and the third one is links that into<01:02:46.980> overall<01:02:47.400> set<01:02:47.670> of<01:02:47.790> workloads<01:02:48.240> to<01:02:48.510> be 01:02:48.650 --> 01:02:48.660 align:start position:0% into overall set of workloads to be 01:02:48.660 --> 01:02:50.660 align:start position:0% into overall set of workloads to be loaded<01:02:49.020> in<01:02:49.170> the<01:02:49.320> employer<01:02:49.800> so<01:02:50.490> the 01:02:50.660 --> 01:02:50.670 align:start position:0% loaded in the employer so the 01:02:50.670 --> 01:02:52.850 align:start position:0% loaded in the employer so the highlighted<01:02:51.420> items<01:02:52.170> is<01:02:52.350> actually<01:02:52.680> what 01:02:52.850 --> 01:02:52.860 align:start position:0% highlighted items is actually what 01:02:52.860 --> 01:02:54.080 align:start position:0% highlighted items is actually what really<01:02:53.100> has<01:02:53.400> to<01:02:53.430> be<01:02:53.550> changed<01:02:53.970> because 01:02:54.080 --> 01:02:54.090 align:start position:0% really has to be changed because 01:02:54.090 --> 01:02:59.050 align:start position:0% really has to be changed because everything<01:02:54.810> else<01:02:54.960> provided<01:02:55.650> as<01:02:55.830> templates 01:02:59.050 --> 01:02:59.060 align:start position:0% 01:02:59.060 --> 01:03:02.290 align:start position:0% then<01:03:00.060> we<01:03:00.420> need<01:03:00.570> to<01:03:00.750> update<01:03:00.870> at<01:03:01.380> this<01:03:01.560> stage<01:03:01.860> one 01:03:02.290 --> 01:03:02.300 align:start position:0% then we need to update at this stage one 01:03:02.300 --> 01:03:06.830 align:start position:0% then we need to update at this stage one source<01:03:03.300> file<01:03:03.510> scatter<01:03:04.110> file<01:03:04.410> so<01:03:05.340> we<01:03:06.300> begin<01:03:06.720> we 01:03:06.830 --> 01:03:06.840 align:start position:0% source file scatter file so we begin we 01:03:06.840 --> 01:03:09.230 align:start position:0% source file scatter file so we begin we have<01:03:06.900> to<01:03:07.050> make<01:03:07.350> the<01:03:07.530> industry<01:03:08.010> changes<01:03:08.430> to 01:03:09.230 --> 01:03:09.240 align:start position:0% have to make the industry changes to 01:03:09.240 --> 01:03:12.410 align:start position:0% have to make the industry changes to them<01:03:09.540> first<01:03:10.110> and<01:03:10.290> last<01:03:10.680> really<01:03:11.400> the<01:03:11.550> same<01:03:11.760> we 01:03:12.410 --> 01:03:12.420 align:start position:0% them first and last really the same we 01:03:12.420 --> 01:03:14.030 align:start position:0% them first and last really the same we just<01:03:12.690> need<01:03:12.900> to<01:03:13.050> change<01:03:13.260> the<01:03:13.380> name<01:03:13.680> space 01:03:14.030 --> 01:03:14.040 align:start position:0% just need to change the name space 01:03:14.040 --> 01:03:16.150 align:start position:0% just need to change the name space because<01:03:14.490> if<01:03:14.700> we<01:03:14.850> continue<01:03:15.060> the<01:03:15.420> same<01:03:15.630> template 01:03:16.150 --> 01:03:16.160 align:start position:0% because if we continue the same template 01:03:16.160 --> 01:03:20.540 align:start position:0% because if we continue the same template -<01:03:17.160> for<01:03:18.120> multiple<01:03:18.600> workloads<01:03:18.960> they<01:03:19.920> should<01:03:20.370> not 01:03:20.540 --> 01:03:20.550 align:start position:0% - for multiple workloads they should not 01:03:20.550 --> 01:03:24.470 align:start position:0% - for multiple workloads they should not come<01:03:21.210> up<01:03:21.450> compete<01:03:22.050> and<01:03:22.760> we<01:03:23.760> should<01:03:24.000> keep<01:03:24.210> the 01:03:24.470 --> 01:03:24.480 align:start position:0% come up compete and we should keep the 01:03:24.480 --> 01:03:27.440 align:start position:0% come up compete and we should keep the compiler<01:03:24.930> head<01:03:25.140> and<01:03:26.100> finally<01:03:26.700> we<01:03:26.850> need<01:03:26.970> to<01:03:27.180> set 01:03:27.440 --> 01:03:27.450 align:start position:0% compiler head and finally we need to set 01:03:27.450 --> 01:03:30.170 align:start position:0% compiler head and finally we need to set the<01:03:27.800> workload<01:03:28.800> ID<01:03:29.220> and<01:03:29.520> by<01:03:29.670> the<01:03:29.730> way<01:03:29.910> I<01:03:29.940> made<01:03:30.150> a 01:03:30.170 --> 01:03:30.180 align:start position:0% the workload ID and by the way I made a 01:03:30.180 --> 01:03:30.650 align:start position:0% the workload ID and by the way I made a mistake 01:03:30.650 --> 01:03:30.660 align:start position:0% mistake 01:03:30.660 --> 01:03:34.880 align:start position:0% mistake check<01:03:30.930> the<01:03:31.050> hello<01:03:31.350> there<01:03:33.020> or<01:03:34.020> not<01:03:34.410> they<01:03:34.620> have 01:03:34.880 --> 01:03:34.890 align:start position:0% check the hello there or not they have 01:03:34.890 --> 01:03:36.170 align:start position:0% check the hello there or not they have all<01:03:35.040> under<01:03:35.280> control 01:03:36.170 --> 01:03:36.180 align:start position:0% all under control 01:03:36.180 --> 01:03:41.940 align:start position:0% all under control next<01:03:36.600> time<01:03:39.650> at<01:03:40.650> the<01:03:40.830> same<01:03:41.190> time 01:03:41.940 --> 01:03:41.950 align:start position:0% next time at the same time 01:03:41.950 --> 01:03:43.210 align:start position:0% next time at the same time [Music] 01:03:43.210 --> 01:03:43.220 align:start position:0% [Music] 01:03:43.220 --> 01:03:50.539 align:start position:0% [Music] it's<01:03:44.220> like<01:03:44.690> house 01:03:50.539 --> 01:03:50.549 align:start position:0% 01:03:50.549 --> 01:03:53.460 align:start position:0% okay<01:03:51.549> so<01:03:51.880> this<01:03:52.059> is<01:03:52.269> okay<01:03:52.660> so<01:03:52.960> these<01:03:53.109> is 01:03:53.460 --> 01:03:53.470 align:start position:0% okay so this is okay so these is 01:03:53.470 --> 01:03:57.420 align:start position:0% okay so this is okay so these is actually<01:03:53.940> help<01:03:55.109> so<01:03:56.109> this<01:03:56.829> line<01:03:57.069> is<01:03:57.099> actually 01:03:57.420 --> 01:03:57.430 align:start position:0% actually help so this line is actually 01:03:57.430 --> 01:04:01.680 align:start position:0% actually help so this line is actually just<01:03:58.000> usually<01:03:58.900> the<01:03:59.049> different<01:03:59.500> recover<01:04:00.690> the 01:04:01.680 --> 01:04:01.690 align:start position:0% just usually the different recover the 01:04:01.690 --> 01:04:03.990 align:start position:0% just usually the different recover the what<01:04:02.559> is<01:04:02.680> it<01:04:02.829> to<01:04:02.980> show<01:04:03.010> us<01:04:03.220> here<01:04:03.579> not<01:04:03.880> the 01:04:03.990 --> 01:04:04.000 align:start position:0% what is it to show us here not the 01:04:04.000 --> 01:04:06.380 align:start position:0% what is it to show us here not the changes<01:04:04.450> but<01:04:04.690> they<01:04:04.930> just<01:04:05.140> didn't<01:04:05.589> ins<01:04:05.740> that 01:04:06.380 --> 01:04:06.390 align:start position:0% changes but they just didn't ins that 01:04:06.390 --> 01:04:08.789 align:start position:0% changes but they just didn't ins that important<01:04:07.390> to<01:04:07.930> understand<01:04:08.440> why<01:04:08.589> are<01:04:08.650> they 01:04:08.789 --> 01:04:08.799 align:start position:0% important to understand why are they 01:04:08.799 --> 01:04:12.329 align:start position:0% important to understand why are they here<01:04:09.130> so<01:04:09.519> we<01:04:09.849> have<01:04:10.089> to<01:04:10.269> inherit<01:04:10.690> from<01:04:11.019> the<01:04:11.339> word 01:04:12.329 --> 01:04:12.339 align:start position:0% here so we have to inherit from the word 01:04:12.339 --> 01:04:14.670 align:start position:0% here so we have to inherit from the word processor<01:04:13.059> class<01:04:13.420> we<01:04:13.930> have<01:04:14.170> to<01:04:14.319> have<01:04:14.529> this 01:04:14.670 --> 01:04:14.680 align:start position:0% processor class we have to have this 01:04:14.680 --> 01:04:17.339 align:start position:0% processor class we have to have this macro<01:04:15.160> that<01:04:15.460> actually<01:04:15.910> allows<01:04:16.240> us<01:04:16.269> to<01:04:16.990> clone 01:04:17.339 --> 01:04:17.349 align:start position:0% macro that actually allows us to clone 01:04:17.349 --> 01:04:20.940 align:start position:0% macro that actually allows us to clone the<01:04:17.980> class<01:04:18.250> whatever<01:04:18.700> execution<01:04:19.450> we<01:04:19.630> need<01:04:20.019> we 01:04:20.940 --> 01:04:20.950 align:start position:0% the class whatever execution we need we 01:04:20.950 --> 01:04:24.120 align:start position:0% the class whatever execution we need we need<01:04:20.980> to<01:04:21.250> implement<01:04:21.490> these<01:04:22.680> virtual<01:04:23.680> function 01:04:24.120 --> 01:04:24.130 align:start position:0% need to implement these virtual function 01:04:24.130 --> 01:04:26.599 align:start position:0% need to implement these virtual function and<01:04:24.940> we're<01:04:25.359> going<01:04:25.539> to<01:04:25.720> look<01:04:25.809> at<01:04:25.960> the 01:04:26.599 --> 01:04:26.609 align:start position:0% and we're going to look at the 01:04:26.609 --> 01:04:28.890 align:start position:0% and we're going to look at the implementation<01:04:27.609> a<01:04:28.059> little<01:04:28.299> bit<01:04:28.420> later<01:04:28.660> and 01:04:28.890 --> 01:04:28.900 align:start position:0% implementation a little bit later and 01:04:28.900 --> 01:04:30.569 align:start position:0% implementation a little bit later and finally<01:04:29.349> there<01:04:29.500> is<01:04:29.529> a<01:04:29.650> helper<01:04:30.130> function<01:04:30.549> that 01:04:30.569 --> 01:04:30.579 align:start position:0% finally there is a helper function that 01:04:30.579 --> 01:04:33.269 align:start position:0% finally there is a helper function that just<01:04:31.089> makes<01:04:31.359> agent<01:04:31.839> Lee<01:04:31.960> output<01:04:32.799> elements 01:04:33.269 --> 01:04:33.279 align:start position:0% just makes agent Lee output elements 01:04:33.279 --> 01:04:38.579 align:start position:0% just makes agent Lee output elements easier<01:04:33.640> that's<01:04:34.359> right<01:04:35.490> so<01:04:36.490> now<01:04:36.670> if<01:04:37.630> we<01:04:37.690> we<01:04:38.500> were 01:04:38.579 --> 01:04:38.589 align:start position:0% easier that's right so now if we we were 01:04:38.589 --> 01:04:41.640 align:start position:0% easier that's right so now if we we were done<01:04:38.859> with<01:04:39.039> this<01:04:39.480> stage<01:04:40.480> one<01:04:40.750> so<01:04:41.109> what<01:04:41.500> would 01:04:41.640 --> 01:04:41.650 align:start position:0% done with this stage one so what would 01:04:41.650 --> 01:04:43.559 align:start position:0% done with this stage one so what would happen<01:04:41.890> that<01:04:42.220> when<01:04:42.400> we're<01:04:42.549> going<01:04:42.730> to<01:04:42.849> be<01:04:43.119> at 01:04:43.559 --> 01:04:43.569 align:start position:0% happen that when we're going to be at 01:04:43.569 --> 01:04:45.240 align:start position:0% happen that when we're going to be at this<01:04:43.779> stage<01:04:43.839> two<01:04:44.349> we're<01:04:44.589> pretty<01:04:44.769> much<01:04:44.980> going 01:04:45.240 --> 01:04:45.250 align:start position:0% this stage two we're pretty much going 01:04:45.250 --> 01:04:47.940 align:start position:0% this stage two we're pretty much going to<01:04:45.490> modify<01:04:45.789> two<01:04:46.630> more<01:04:46.869> vials<01:04:47.319> consuming<01:04:47.859> more 01:04:47.940 --> 01:04:47.950 align:start position:0% to modify two more vials consuming more 01:04:47.950 --> 01:04:52.769 align:start position:0% to modify two more vials consuming more vials<01:04:48.279> this<01:04:48.549> is<01:04:50.250> going<01:04:51.250> to<01:04:51.430> get<01:04:51.849> the<01:04:52.059> logic<01:04:52.240> the 01:04:52.769 --> 01:04:52.779 align:start position:0% vials this is going to get the logic the 01:04:52.779 --> 01:04:57.749 align:start position:0% vials this is going to get the logic the digital<01:04:54.450> file<01:04:55.450> for<01:04:55.839> plugging<01:04:56.319> that<01:04:56.950> CBD<01:04:57.309> that 01:04:57.749 --> 01:04:57.759 align:start position:0% digital file for plugging that CBD that 01:04:57.759 --> 01:05:00.240 align:start position:0% digital file for plugging that CBD that is<01:04:57.910> actually<01:04:58.299> the<01:04:58.450> file<01:04:59.109> that<01:04:59.410> kind<01:04:59.799> of<01:04:59.890> links 01:05:00.240 --> 01:05:00.250 align:start position:0% is actually the file that kind of links 01:05:00.250 --> 01:05:02.970 align:start position:0% is actually the file that kind of links your<01:05:00.430> logic<01:05:00.759> is<01:05:00.940> the<01:05:01.180> framework<01:05:01.809> and<01:05:02.349> when<01:05:02.890> we 01:05:02.970 --> 01:05:02.980 align:start position:0% your logic is the framework and when we 01:05:02.980 --> 01:05:03.599 align:start position:0% your logic is the framework and when we do<01:05:03.130> this<01:05:03.309> stuff 01:05:03.599 --> 01:05:03.609 align:start position:0% do this stuff 01:05:03.609 --> 01:05:05.370 align:start position:0% do this stuff and<01:05:03.880> when<01:05:04.059> we<01:05:04.240> run<01:05:04.390> the<01:05:04.539> same<01:05:04.720> command<01:05:04.930> we're 01:05:05.370 --> 01:05:05.380 align:start position:0% and when we run the same command we're 01:05:05.380 --> 01:05:07.319 align:start position:0% and when we run the same command we're going<01:05:05.589> to<01:05:05.740> have<01:05:05.920> the<01:05:06.069> proper<01:05:06.430> response<01:05:06.819> for 01:05:07.319 --> 01:05:07.329 align:start position:0% going to have the proper response for 01:05:07.329 --> 01:05:11.620 align:start position:0% going to have the proper response for Edison<01:05:07.839> to<01:05:08.019> go<01:05:08.170> walk<01:05:09.180> next<01:05:10.180> time 01:05:11.620 --> 01:05:11.630 align:start position:0% Edison to go walk next time 01:05:11.630 --> 01:05:14.420 align:start position:0% Edison to go walk next time so<01:05:12.630> logic<01:05:13.529> is<01:05:13.650> actually<01:05:13.979> where<01:05:14.190> the 01:05:14.420 --> 01:05:14.430 align:start position:0% so logic is actually where the 01:05:14.430 --> 01:05:16.969 align:start position:0% so logic is actually where the developers<01:05:14.969> will<01:05:15.209> spend<01:05:15.509> probably<01:05:15.959> 99%<01:05:16.619> of 01:05:16.969 --> 01:05:16.979 align:start position:0% developers will spend probably 99% of 01:05:16.979 --> 01:05:21.410 align:start position:0% developers will spend probably 99% of that<01:05:17.160> time<01:05:17.430> and<01:05:19.430> no<01:05:20.430> case<01:05:20.729> it's<01:05:20.969> very<01:05:21.029> creative 01:05:21.410 --> 01:05:21.420 align:start position:0% that time and no case it's very creative 01:05:21.420 --> 01:05:23.479 align:start position:0% that time and no case it's very creative it<01:05:21.959> just<01:05:22.199> the<01:05:22.440> function<01:05:22.859> that<01:05:23.039> takes<01:05:23.309> the 01:05:23.479 --> 01:05:23.489 align:start position:0% it just the function that takes the 01:05:23.489 --> 01:05:25.630 align:start position:0% it just the function that takes the stream<01:05:23.880> inputs<01:05:24.449> think<01:05:24.719> as<01:05:24.869> a<01:05:24.900> parameter 01:05:25.630 --> 01:05:25.640 align:start position:0% stream inputs think as a parameter 01:05:25.640 --> 01:05:28.549 align:start position:0% stream inputs think as a parameter density<01:05:26.640> hello<01:05:26.940> depends<01:05:27.690> if<01:05:27.839> is<01:05:27.989> below<01:05:28.259> and 01:05:28.549 --> 01:05:28.559 align:start position:0% density hello depends if is below and 01:05:28.559 --> 01:05:35.959 align:start position:0% density hello depends if is below and returns<01:05:29.279> the<01:05:29.430> result<01:05:32.839> and<01:05:34.039> the<01:05:35.039> now<01:05:35.489> before 01:05:35.959 --> 01:05:35.969 align:start position:0% returns the result and the now before 01:05:35.969 --> 01:05:37.579 align:start position:0% returns the result and the now before we're<01:05:36.119> going<01:05:36.269> to<01:05:36.449> look<01:05:36.599> in<01:05:36.869> what<01:05:37.109> we<01:05:37.229> actually 01:05:37.579 --> 01:05:37.589 align:start position:0% we're going to look in what we actually 01:05:37.589 --> 01:05:41.269 align:start position:0% we're going to look in what we actually have<01:05:37.799> to<01:05:37.979> change<01:05:38.009> in<01:05:38.729> the<01:05:39.019> file<01:05:40.019> that<01:05:40.319> contains 01:05:41.269 --> 01:05:41.279 align:start position:0% have to change in the file that contains 01:05:41.279 --> 01:05:46.719 align:start position:0% have to change in the file that contains the<01:05:41.400> our<01:05:41.729> business<01:05:42.420> logic<01:05:42.630> please<01:05:43.109> the 01:05:46.719 --> 01:05:46.729 align:start position:0% 01:05:46.729 --> 01:05:49.670 align:start position:0% framework<01:05:47.729> we<01:05:48.180> need<01:05:48.509> to<01:05:48.719> look<01:05:49.380> in<01:05:49.650> the 01:05:49.670 --> 01:05:49.680 align:start position:0% framework we need to look in the 01:05:49.680 --> 01:05:51.709 align:start position:0% framework we need to look in the previous<01:05:50.309> implementation<01:05:50.579> this<01:05:51.180> is<01:05:51.329> a<01:05:51.359> start 01:05:51.709 --> 01:05:51.719 align:start position:0% previous implementation this is a start 01:05:51.719 --> 01:05:54.769 align:start position:0% previous implementation this is a start and<01:05:51.839> limitation<01:05:52.469> in<01:05:52.619> digit<01:05:52.949> way<01:05:53.180> so<01:05:54.180> because 01:05:54.769 --> 01:05:54.779 align:start position:0% and limitation in digit way so because 01:05:54.779 --> 01:05:57.709 align:start position:0% and limitation in digit way so because this<01:05:54.989> my<01:05:55.589> product<01:05:55.920> register<01:05:56.459> or<01:05:56.969> processor 01:05:57.709 --> 01:05:57.719 align:start position:0% this my product register or processor 01:05:57.719 --> 01:05:59.809 align:start position:0% this my product register or processor that<01:05:58.019> just<01:05:58.289> simply<01:05:58.589> has<01:05:58.769> to<01:05:58.799> be<01:05:58.949> present<01:05:59.279> there 01:05:59.809 --> 01:05:59.819 align:start position:0% that just simply has to be present there 01:05:59.819 --> 01:06:02.989 align:start position:0% that just simply has to be present there is<01:05:59.940> the<01:06:00.119> function<01:06:00.660> process<01:06:01.589> work<01:06:01.859> order<01:06:02.489> that 01:06:02.989 --> 01:06:02.999 align:start position:0% is the function process work order that 01:06:02.999 --> 01:06:06.589 align:start position:0% is the function process work order that has<01:06:03.359> number<01:06:03.719> of<01:06:03.839> parameters<01:06:04.319> that<01:06:05.599> describe 01:06:06.589 --> 01:06:06.599 align:start position:0% has number of parameters that describe 01:06:06.599 --> 01:06:09.559 align:start position:0% has number of parameters that describe the<01:06:07.079> or<01:06:07.289> call<01:06:07.499> submitted<01:06:08.099> to<01:06:08.699> execution<01:06:09.329> and 01:06:09.559 --> 01:06:09.569 align:start position:0% the or call submitted to execution and 01:06:09.569 --> 01:06:12.319 align:start position:0% the or call submitted to execution and the<01:06:09.930> most<01:06:10.109> important<01:06:10.619> in<01:06:10.829> work<01:06:11.579> order<01:06:11.969> date<01:06:12.150> in 01:06:12.319 --> 01:06:12.329 align:start position:0% the most important in work order date in 01:06:12.329 --> 01:06:15.559 align:start position:0% the most important in work order date in Outworld<01:06:12.959> beta<01:06:13.440> and<01:06:13.999> it<01:06:14.999> has<01:06:15.269> a<01:06:15.299> couple 01:06:15.559 --> 01:06:15.569 align:start position:0% Outworld beta and it has a couple 01:06:15.569 --> 01:06:18.049 align:start position:0% Outworld beta and it has a couple extreme<01:06:16.199> error<01:06:16.739> under<01:06:17.130> construction<01:06:17.759> that<01:06:17.789> is 01:06:18.049 --> 01:06:18.059 align:start position:0% extreme error under construction that is 01:06:18.059 --> 01:06:20.150 align:start position:0% extreme error under construction that is conducted<01:06:18.539> on<01:06:18.630> battery<01:06:19.109> and<01:06:19.469> the<01:06:19.619> phone<01:06:19.920> as<01:06:20.130> a 01:06:20.150 --> 01:06:20.160 align:start position:0% conducted on battery and the phone as a 01:06:20.160 --> 01:06:21.769 align:start position:0% conducted on battery and the phone as a result<01:06:20.549> and<01:06:20.849> as<01:06:20.999> you<01:06:21.150> can<01:06:21.299> see<01:06:21.359> it<01:06:21.569> a 01:06:21.769 --> 01:06:21.779 align:start position:0% result and as you can see it a 01:06:21.779 --> 01:06:26.539 align:start position:0% result and as you can see it a particular<01:06:22.199> speed<01:06:22.789> next<01:06:24.469> and<01:06:25.469> that<01:06:26.130> is<01:06:26.430> the 01:06:26.539 --> 01:06:26.549 align:start position:0% particular speed next and that is the 01:06:26.549 --> 01:06:29.359 align:start position:0% particular speed next and that is the function<01:06:27.029> that<01:06:27.059> we<01:06:27.839> are<01:06:28.229> going<01:06:28.680> to<01:06:28.859> implement 01:06:29.359 --> 01:06:29.369 align:start position:0% function that we are going to implement 01:06:29.369 --> 01:06:32.479 align:start position:0% function that we are going to implement in<01:06:29.549> order<01:06:29.699> to<01:06:30.119> leave<01:06:30.390> the<01:06:30.719> allergic<01:06:31.349> or<01:06:31.589> the 01:06:32.479 --> 01:06:32.489 align:start position:0% in order to leave the allergic or the 01:06:32.489 --> 01:06:35.630 align:start position:0% in order to leave the allergic or the this<01:06:33.299> hello<01:06:33.719> world<01:06:33.930> who<01:06:34.529> is<01:06:34.589> the<01:06:34.739> framework 01:06:35.630 --> 01:06:35.640 align:start position:0% this hello world who is the framework 01:06:35.640 --> 01:06:38.299 align:start position:0% this hello world who is the framework so<01:06:36.299> in<01:06:36.390> this<01:06:36.539> is<01:06:36.959> the<01:06:37.440> for<01:06:37.769> loop<01:06:37.949> is<01:06:38.130> actually 01:06:38.299 --> 01:06:38.309 align:start position:0% so in this is the for loop is actually 01:06:38.309 --> 01:06:40.219 align:start position:0% so in this is the for loop is actually it<01:06:38.670> allows<01:06:38.940> you<01:06:39.150> to<01:06:39.329> enumerate<01:06:39.630> from<01:06:39.989> each 01:06:40.219 --> 01:06:40.229 align:start position:0% it allows you to enumerate from each 01:06:40.229 --> 01:06:42.109 align:start position:0% it allows you to enumerate from each input<01:06:40.559> date<01:06:40.890> on<01:06:41.099> the<01:06:41.249> first 01:06:42.109 --> 01:06:42.119 align:start position:0% input date on the first 01:06:42.119 --> 01:06:45.779 align:start position:0% input date on the first on<01:06:43.119> the<01:06:43.239> second<01:06:43.569> that<01:06:43.689> will<01:06:43.839> be<01:06:43.900> it<01:06:44.199> but<01:06:44.799> then 01:06:45.779 --> 01:06:45.789 align:start position:0% on the second that will be it but then 01:06:45.789 --> 01:06:47.789 align:start position:0% on the second that will be it but then what<01:06:46.209> we're<01:06:46.359> going<01:06:46.509> to<01:06:46.599> do<01:06:46.809> the<01:06:46.929> data<01:06:47.289> comes<01:06:47.619> in 01:06:47.789 --> 01:06:47.799 align:start position:0% what we're going to do the data comes in 01:06:47.799 --> 01:06:50.009 align:start position:0% what we're going to do the data comes in the<01:06:47.890> battery<01:06:48.279> so<01:06:48.640> they<01:06:48.789> have<01:06:48.999> to<01:06:49.150> be<01:06:49.479> converted 01:06:50.009 --> 01:06:50.019 align:start position:0% the battery so they have to be converted 01:06:50.019 --> 01:06:55.109 align:start position:0% the battery so they have to be converted to<01:06:50.049> steam<01:06:50.439> and<01:06:50.920> sent<01:06:51.789> to<01:06:52.179> the<01:06:52.739> front<01:06:53.910> part<01:06:54.910> s 01:06:55.109 --> 01:06:55.119 align:start position:0% to steam and sent to the front part s 01:06:55.119 --> 01:06:57.509 align:start position:0% to steam and sent to the front part s hello<01:06:55.420> world<01:06:55.749> and<01:06:56.079> once<01:06:56.739> they<01:06:56.859> process<01:06:57.279> the 01:06:57.509 --> 01:06:57.519 align:start position:0% hello world and once they process the 01:06:57.519 --> 01:06:59.519 align:start position:0% hello world and once they process the result<01:06:57.819> comes<01:06:58.089> as<01:06:58.239> thing<01:06:58.569> that<01:06:58.779> has<01:06:59.349> to<01:06:59.499> be 01:06:59.519 --> 01:06:59.529 align:start position:0% result comes as thing that has to be 01:06:59.529 --> 01:07:05.370 align:start position:0% result comes as thing that has to be converted<01:06:59.890> to<01:07:00.099> by<01:07:00.369> tray<01:07:00.699> and<01:07:01.029> edit<01:07:01.959> to<01:07:02.380> the<01:07:04.380> to 01:07:05.370 --> 01:07:05.380 align:start position:0% converted to by tray and edit to the to 01:07:05.380 --> 01:07:07.829 align:start position:0% converted to by tray and edit to the to the<01:07:05.559> work<01:07:06.369> order<01:07:06.609> itself<01:07:07.119> and<01:07:07.390> those<01:07:07.479> those 01:07:07.829 --> 01:07:07.839 align:start position:0% the work order itself and those those 01:07:07.839 --> 01:07:12.150 align:start position:0% the work order itself and those those links<01:07:08.289> to<01:07:08.469> stinks<01:07:09.400> the<01:07:10.079> hello<01:07:11.079> hello<01:07:11.920> all 01:07:12.150 --> 01:07:12.160 align:start position:0% links to stinks the hello hello all 01:07:12.160 --> 01:07:15.900 align:start position:0% links to stinks the hello hello all going<01:07:12.429> to<01:07:12.670> be<01:07:12.789> returned<01:07:13.329> to<01:07:14.259> the<01:07:14.910> powerful 01:07:15.900 --> 01:07:15.910 align:start position:0% going to be returned to the powerful 01:07:15.910 --> 01:07:19.199 align:start position:0% going to be returned to the powerful dimension<01:07:16.689> so<01:07:17.410> the<01:07:18.099> theta<01:07:18.459> in<01:07:18.759> the<01:07:18.880> process 01:07:19.199 --> 01:07:19.209 align:start position:0% dimension so the theta in the process 01:07:19.209 --> 01:07:22.410 align:start position:0% dimension so the theta in the process going<01:07:19.449> to<01:07:19.569> do<01:07:20.289> a<01:07:20.319> lot<01:07:20.589> of<01:07:20.739> different<01:07:21.579> processes 01:07:22.410 --> 01:07:22.420 align:start position:0% going to do a lot of different processes 01:07:22.420 --> 01:07:24.269 align:start position:0% going to do a lot of different processes they're<01:07:22.959> going<01:07:23.170> to<01:07:23.349> be<01:07:23.469> encrypted<01:07:23.859> they're 01:07:24.269 --> 01:07:24.279 align:start position:0% they're going to be encrypted they're 01:07:24.279 --> 01:07:27.749 align:start position:0% they're going to be encrypted they're going<01:07:24.489> to<01:07:24.729> be<01:07:24.880> unsigned<01:07:25.599> but<01:07:26.559> all<01:07:27.489> this<01:07:27.699> is 01:07:27.749 --> 01:07:27.759 align:start position:0% going to be unsigned but all this is 01:07:27.759 --> 01:07:29.370 align:start position:0% going to be unsigned but all this is actually<01:07:28.209> kind<01:07:28.420> of<01:07:28.509> transparent<01:07:29.140> for<01:07:29.289> the 01:07:29.370 --> 01:07:29.380 align:start position:0% actually kind of transparent for the 01:07:29.380 --> 01:07:31.199 align:start position:0% actually kind of transparent for the developer<01:07:29.890> or<01:07:30.130> the<01:07:30.160> workflow<01:07:30.699> but<01:07:30.819> as<01:07:30.969> long<01:07:31.179> as 01:07:31.199 --> 01:07:31.209 align:start position:0% developer or the workflow but as long as 01:07:31.209 --> 01:07:33.179 align:start position:0% developer or the workflow but as long as the<01:07:31.599> you<01:07:31.749> provide<01:07:32.170> this<01:07:32.349> function<01:07:32.829> that<01:07:33.039> is 01:07:33.179 --> 01:07:33.189 align:start position:0% the you provide this function that is 01:07:33.189 --> 01:07:36.289 align:start position:0% the you provide this function that is going<01:07:33.369> to<01:07:33.579> be<01:07:33.670> whole<01:07:33.939> they<01:07:34.869> do<01:07:35.439> provide<01:07:35.709> the 01:07:36.289 --> 01:07:36.299 align:start position:0% going to be whole they do provide the 01:07:36.299 --> 01:07:39.809 align:start position:0% going to be whole they do provide the workload<01:07:37.299> ideal<01:07:37.809> the<01:07:38.279> framework<01:07:39.279> will<01:07:39.489> find 01:07:39.809 --> 01:07:39.819 align:start position:0% workload ideal the framework will find 01:07:39.819 --> 01:07:42.390 align:start position:0% workload ideal the framework will find your<01:07:40.089> workload<01:07:40.569> and<01:07:40.809> will<01:07:41.380> send<01:07:41.829> the<01:07:42.039> data<01:07:42.219> to 01:07:42.390 --> 01:07:42.400 align:start position:0% your workload and will send the data to 01:07:42.400 --> 01:07:47.860 align:start position:0% your workload and will send the data to the<01:07:42.609> worker<01:07:43.089> for<01:07:43.359> the<01:07:43.479> institution<01:07:43.959> that's<01:07:44.829> it 01:07:47.860 --> 01:07:47.870 align:start position:0% 01:07:47.870 --> 01:07:50.470 align:start position:0% [Music] 01:07:50.470 --> 01:07:50.480 align:start position:0% [Music] 01:07:50.480 --> 01:08:01.640 align:start position:0% [Music] silica<01:07:57.200> plumbing<01:07:59.869> though<01:08:00.869> the<01:08:01.079> restart<01:08:01.559> you 01:08:01.640 --> 01:08:01.650 align:start position:0% silica plumbing though the restart you 01:08:01.650 --> 01:08:07.910 align:start position:0% silica plumbing though the restart you think<01:08:04.640> so<01:08:05.640> now<01:08:05.819> love<01:08:06.150> like<01:08:07.140> we<01:08:07.500> have<01:08:07.650> three 01:08:07.910 --> 01:08:07.920 align:start position:0% think so now love like we have three 01:08:07.920 --> 01:08:34.820 align:start position:0% think so now love like we have three histories<01:08:08.579> that<01:08:14.599> the<01:08:15.599> first<01:08:15.839> one<01:08:16.080> is<01:08:33.830> I'm 01:08:34.820 --> 01:08:34.830 align:start position:0% histories that the first one is I'm 01:08:34.830 --> 01:08:36.979 align:start position:0% histories that the first one is I'm Jimmy<01:08:35.460> and<01:08:35.489> I'm<01:08:35.699> from<01:08:35.969> Banco<01:08:36.239> Santander<01:08:36.420> and 01:08:36.979 --> 01:08:36.989 align:start position:0% Jimmy and I'm from Banco Santander and 01:08:36.989 --> 01:08:42.050 align:start position:0% Jimmy and I'm from Banco Santander and we<01:08:37.890> are<01:08:38.069> kind<01:08:38.310> of<01:08:38.520> special<01:08:39.480> car<01:08:40.400> child:yeah 01:08:42.050 --> 01:08:42.060 align:start position:0% we are kind of special car child:yeah 01:08:42.060 --> 01:08:44.360 align:start position:0% we are kind of special car child:yeah because<01:08:42.540> we<01:08:42.750> are<01:08:42.900> not<01:08:43.080> software<01:08:43.830> vendor<01:08:44.159> we 01:08:44.360 --> 01:08:44.370 align:start position:0% because we are not software vendor we 01:08:44.370 --> 01:08:46.789 align:start position:0% because we are not software vendor we were<01:08:44.520> back<01:08:45.199> so<01:08:46.199> we<01:08:46.319> are<01:08:46.440> not<01:08:46.589> the<01:08:46.710> smartest 01:08:46.789 --> 01:08:46.799 align:start position:0% were back so we are not the smartest 01:08:46.799 --> 01:08:49.760 align:start position:0% were back so we are not the smartest ones<01:08:47.339> but<01:08:47.969> we<01:08:48.299> are<01:08:48.630> ones<01:08:48.960> with<01:08:49.259> interesting 01:08:49.760 --> 01:08:49.770 align:start position:0% ones but we are ones with interesting 01:08:49.770 --> 01:08:52.370 align:start position:0% ones but we are ones with interesting your<01:08:49.890> spaces<01:08:50.310> and<01:08:50.520> we<01:08:51.449> actually<01:08:51.870> do<01:08:52.080> have<01:08:52.350> a 01:08:52.370 --> 01:08:52.380 align:start position:0% your spaces and we actually do have a 01:08:52.380 --> 01:08:54.800 align:start position:0% your spaces and we actually do have a lot<01:08:52.650> of<01:08:52.679> exciting<01:08:53.489> new<01:08:53.759> spaces<01:08:54.150> that<01:08:54.420> we<01:08:54.569> found 01:08:54.800 --> 01:08:54.810 align:start position:0% lot of exciting new spaces that we found 01:08:54.810 --> 01:08:57.800 align:start position:0% lot of exciting new spaces that we found to<01:08:55.109> talk<01:08:55.380> about<01:08:55.969> but<01:08:56.969> there<01:08:57.330> are<01:08:57.480> maybe<01:08:57.659> some 01:08:57.800 --> 01:08:57.810 align:start position:0% to talk about but there are maybe some 01:08:57.810 --> 01:09:01.210 align:start position:0% to talk about but there are maybe some that<01:08:58.290> we<01:08:58.409> catch<01:08:58.650> her<01:08:58.949> and 01:09:01.210 --> 01:09:01.220 align:start position:0% that we catch her and 01:09:01.220 --> 01:09:03.590 align:start position:0% that we catch her and SGX<01:09:02.220> as<01:09:02.490> a<01:09:02.520> technology<01:09:03.180> that<01:09:03.360> has<01:09:03.420> been 01:09:03.590 --> 01:09:03.600 align:start position:0% SGX as a technology that has been 01:09:03.600 --> 01:09:07.840 align:start position:0% SGX as a technology that has been operator<01:09:04.820> we<01:09:05.820> thought<01:09:06.330> we<01:09:06.510> could<01:09:06.750> solve<01:09:06.990> us 01:09:07.840 --> 01:09:07.850 align:start position:0% operator we thought we could solve us 01:09:07.850 --> 01:09:12.550 align:start position:0% operator we thought we could solve us sound<01:09:08.850> problems<01:09:09.750> instead<01:09:10.730> now<01:09:11.730> comes<01:09:12.030> along 01:09:12.550 --> 01:09:12.560 align:start position:0% sound problems instead now comes along 01:09:12.560 --> 01:09:17.270 align:start position:0% sound problems instead now comes along comes<01:09:13.560> SDK<01:09:14.190> so<01:09:15.050> hopefully<01:09:16.050> we<01:09:16.470> are<01:09:16.590> lazy<01:09:16.860> and 01:09:17.270 --> 01:09:17.280 align:start position:0% comes SDK so hopefully we are lazy and 01:09:17.280 --> 01:09:19.270 align:start position:0% comes SDK so hopefully we are lazy and we<01:09:17.430> are<01:09:17.520> always<01:09:17.700> looking<01:09:17.880> how<01:09:18.690> to<01:09:18.720> piggyback 01:09:19.270 --> 01:09:19.280 align:start position:0% we are always looking how to piggyback 01:09:19.280 --> 01:09:24.350 align:start position:0% we are always looking how to piggyback smart<01:09:20.280> people's<01:09:20.700> work<01:09:20.880> and<01:09:22.340> let<01:09:23.340> us<01:09:23.490> let<01:09:24.330> me 01:09:24.350 --> 01:09:24.360 align:start position:0% smart people's work and let us let me 01:09:24.360 --> 01:09:27.380 align:start position:0% smart people's work and let us let me walk<01:09:25.230> you<01:09:25.260> through<01:09:25.590> the<01:09:25.710> problem<01:09:26.160> it's<01:09:26.790> on 01:09:27.380 --> 01:09:27.390 align:start position:0% walk you through the problem it's on 01:09:27.390 --> 01:09:29.360 align:start position:0% walk you through the problem it's on either<01:09:27.600> side<01:09:27.900> is<01:09:28.050> very<01:09:28.200> boring<01:09:28.530> because<01:09:29.160> there 01:09:29.360 --> 01:09:29.370 align:start position:0% either side is very boring because there 01:09:29.370 --> 01:09:32.030 align:start position:0% either side is very boring because there is<01:09:29.460> not<01:09:30.120> much<01:09:30.180> money<01:09:30.540> involved<01:09:30.930> on<01:09:31.740> the<01:09:31.920> other 01:09:32.030 --> 01:09:32.040 align:start position:0% is not much money involved on the other 01:09:32.040 --> 01:09:33.920 align:start position:0% is not much money involved on the other hand<01:09:32.280> side<01:09:32.490> it's<01:09:32.700> interesting<01:09:33.180> because<01:09:33.570> it 01:09:33.920 --> 01:09:33.930 align:start position:0% hand side it's interesting because it 01:09:33.930 --> 01:09:36.920 align:start position:0% hand side it's interesting because it has<01:09:34.140> many<01:09:34.730> aspects<01:09:35.730> that<01:09:36.060> we<01:09:36.300> want<01:09:36.570> to<01:09:36.720> cover 01:09:36.920 --> 01:09:36.930 align:start position:0% has many aspects that we want to cover 01:09:36.930 --> 01:09:39.140 align:start position:0% has many aspects that we want to cover and<01:09:37.320> that<01:09:37.350> are<01:09:37.710> relevant<01:09:38.040> in<01:09:38.670> deciding 01:09:39.140 --> 01:09:39.150 align:start position:0% and that are relevant in deciding 01:09:39.150 --> 01:09:43.000 align:start position:0% and that are relevant in deciding businesses<01:09:40.160> so<01:09:41.160> we<01:09:41.340> have<01:09:41.640> three<01:09:42.150> friends 01:09:43.000 --> 01:09:43.010 align:start position:0% businesses so we have three friends 01:09:43.010 --> 01:09:48.260 align:start position:0% businesses so we have three friends Alice<01:09:44.120> and<01:09:45.120> Eva<01:09:45.450> and<01:09:46.350> I'm<01:09:46.610> friends<01:09:47.610> but<01:09:48.150> they 01:09:48.260 --> 01:09:48.270 align:start position:0% Alice and Eva and I'm friends but they 01:09:48.270 --> 01:09:50.980 align:start position:0% Alice and Eva and I'm friends but they were<01:09:48.360> working<01:09:48.480> for<01:09:48.630> competing<01:09:49.440> backs<01:09:49.800> and 01:09:50.980 --> 01:09:50.990 align:start position:0% were working for competing backs and 01:09:50.990 --> 01:09:54.560 align:start position:0% were working for competing backs and next<01:09:51.990> like<01:09:52.170> this<01:09:52.410> and<01:09:52.890> each<01:09:53.670> of<01:09:53.850> them<01:09:54.060> has<01:09:54.540> a 01:09:54.560 --> 01:09:54.570 align:start position:0% next like this and each of them has a 01:09:54.570 --> 01:09:58.340 align:start position:0% next like this and each of them has a portfolio<01:09:54.990> of<01:09:55.470> VIP<01:09:55.890> customers<01:09:56.790> that<01:09:57.720> he<01:09:58.290> or 01:09:58.340 --> 01:09:58.350 align:start position:0% portfolio of VIP customers that he or 01:09:58.350 --> 01:10:02.300 align:start position:0% portfolio of VIP customers that he or she<01:09:58.470> takes<01:09:58.950> care<01:09:59.840> and<01:10:00.840> of<01:10:01.440> course<01:10:01.770> it's<01:10:02.100> like 01:10:02.300 --> 01:10:02.310 align:start position:0% she takes care and of course it's like 01:10:02.310 --> 01:10:04.730 align:start position:0% she takes care and of course it's like you<01:10:02.550> know<01:10:02.700> we<01:10:03.120> are<01:10:03.210> friends<01:10:03.780> but<01:10:04.020> stealing<01:10:04.650> a 01:10:04.730 --> 01:10:04.740 align:start position:0% you know we are friends but stealing a 01:10:04.740 --> 01:10:08.420 align:start position:0% you know we are friends but stealing a customer<01:10:05.340> is<01:10:06.120> a<01:10:06.180> problematic<01:10:06.720> thing<01:10:07.160> so<01:10:08.160> next 01:10:08.420 --> 01:10:08.430 align:start position:0% customer is a problematic thing so next 01:10:08.430 --> 01:10:12.850 align:start position:0% customer is a problematic thing so next slide<01:10:09.530> with<01:10:10.530> each<01:10:10.710> customer<01:10:11.010> set<01:10:11.670> there<01:10:12.000> is 01:10:12.850 --> 01:10:12.860 align:start position:0% slide with each customer set there is 01:10:12.860 --> 01:10:16.870 align:start position:0% slide with each customer set there is customer<01:10:13.860> name<01:10:14.310> now<01:10:15.240> this<01:10:15.480> customer<01:10:15.990> data<01:10:16.350> is 01:10:16.870 --> 01:10:16.880 align:start position:0% customer name now this customer data is 01:10:16.880 --> 01:10:20.120 align:start position:0% customer name now this customer data is precious<01:10:17.880> this<01:10:18.750> customer<01:10:19.230> data<01:10:19.380> is<01:10:19.740> something 01:10:20.120 --> 01:10:20.130 align:start position:0% precious this customer data is something 01:10:20.130 --> 01:10:21.320 align:start position:0% precious this customer data is something to<01:10:20.250> be<01:10:20.370> contacted 01:10:21.320 --> 01:10:21.330 align:start position:0% to be contacted 01:10:21.330 --> 01:10:23.120 align:start position:0% to be contacted this<01:10:21.720> customer<01:10:22.200> that<01:10:22.380> is<01:10:22.560> something<01:10:22.950> we 01:10:23.120 --> 01:10:23.130 align:start position:0% this customer that is something we 01:10:23.130 --> 01:10:27.140 align:start position:0% this customer that is something we mustn't<01:10:23.400> share<01:10:24.170> however<01:10:25.700> there<01:10:26.700> are<01:10:26.880> use 01:10:27.140 --> 01:10:27.150 align:start position:0% mustn't share however there are use 01:10:27.150 --> 01:10:30.220 align:start position:0% mustn't share however there are use cases<01:10:27.180> there<01:10:28.020> are<01:10:28.310> situations<01:10:29.310> that<01:10:29.430> our 01:10:30.220 --> 01:10:30.230 align:start position:0% cases there are situations that our 01:10:30.230 --> 01:10:32.900 align:start position:0% cases there are situations that our regulatory<01:10:31.230> requirements<01:10:32.190> when<01:10:32.430> we<01:10:32.580> actually 01:10:32.900 --> 01:10:32.910 align:start position:0% regulatory requirements when we actually 01:10:32.910 --> 01:10:35.450 align:start position:0% regulatory requirements when we actually need<01:10:33.510> to<01:10:33.540> process<01:10:34.070> identity 01:10:35.450 --> 01:10:35.460 align:start position:0% need to process identity 01:10:35.460 --> 01:10:41.300 align:start position:0% need to process identity so<01:10:36.090> one<01:10:36.300> very<01:10:36.330> simple<01:10:37.700> cuz<01:10:38.700> I<01:10:38.850> am<01:10:39.180> L<01:10:40.310> example 01:10:41.300 --> 01:10:41.310 align:start position:0% so one very simple cuz I am L example 01:10:41.310 --> 01:10:42.830 align:start position:0% so one very simple cuz I am L example this<01:10:41.430> one<01:10:41.640> we<01:10:41.790> want<01:10:42.000> to<01:10:42.060> look<01:10:42.180> for<01:10:42.600> people 01:10:42.830 --> 01:10:42.840 align:start position:0% this one we want to look for people 01:10:42.840 --> 01:10:47.420 align:start position:0% this one we want to look for people sending<01:10:43.320> money<01:10:43.670> in<01:10:44.670> a<01:10:44.700> site<01:10:45.470> it's<01:10:46.470> not<01:10:46.740> Troy<01:10:47.040> ml 01:10:47.420 --> 01:10:47.430 align:start position:0% sending money in a site it's not Troy ml 01:10:47.430 --> 01:10:49.700 align:start position:0% sending money in a site it's not Troy ml but<01:10:48.000> it's<01:10:48.180> like<01:10:48.390> you<01:10:48.540> know<01:10:48.690> you're<01:10:48.930> making<01:10:49.410> an 01:10:49.700 --> 01:10:49.710 align:start position:0% but it's like you know you're making an 01:10:49.710 --> 01:10:51.590 align:start position:0% but it's like you know you're making an impression<01:10:49.980> of<01:10:50.280> having<01:10:50.430> money<01:10:50.760> where<01:10:51.060> why<01:10:51.540> you 01:10:51.590 --> 01:10:51.600 align:start position:0% impression of having money where why you 01:10:51.600 --> 01:10:54.620 align:start position:0% impression of having money where why you not<01:10:52.470> really<01:10:52.770> so<01:10:53.670> this<01:10:53.820> is<01:10:53.940> the<01:10:54.090> very<01:10:54.390> simple 01:10:54.620 --> 01:10:54.630 align:start position:0% not really so this is the very simple 01:10:54.630 --> 01:10:59.390 align:start position:0% not really so this is the very simple logic<01:10:55.170> that<01:10:55.350> we<01:10:56.030> use<01:10:57.030> the<01:10:57.980> templates<01:10:58.980> provided 01:10:59.390 --> 01:10:59.400 align:start position:0% logic that we use the templates provided 01:10:59.400 --> 01:11:04.250 align:start position:0% logic that we use the templates provided by<01:10:59.730> Zhang<01:11:00.270> Jian<01:11:00.690> and<01:11:01.250> Eugene<01:11:02.250> as<01:11:03.140> we<01:11:04.140> are 01:11:04.250 --> 01:11:04.260 align:start position:0% by Zhang Jian and Eugene as we are 01:11:04.260 --> 01:11:06.620 align:start position:0% by Zhang Jian and Eugene as we are contributing<01:11:04.620> as<01:11:05.130> an<01:11:05.280> example<01:11:05.640> we<01:11:06.300> have<01:11:06.510> a 01:11:06.620 --> 01:11:06.630 align:start position:0% contributing as an example we have a 01:11:06.630 --> 01:11:09.700 align:start position:0% contributing as an example we have a long<01:11:06.900> hydrologic<01:11:07.740> project<01:11:08.160> so<01:11:08.370> they<01:11:08.600> not<01:11:09.600> only 01:11:09.700 --> 01:11:09.710 align:start position:0% long hydrologic project so they not only 01:11:09.710 --> 01:11:14.330 align:start position:0% long hydrologic project so they not only we<01:11:10.710> have<01:11:11.000> been<01:11:12.000> able<01:11:12.180> to<01:11:12.360> do<01:11:12.570> it<01:11:12.720> but<01:11:13.160> but<01:11:14.160> the 01:11:14.330 --> 01:11:14.340 align:start position:0% we have been able to do it but but the 01:11:14.340 --> 01:11:18.640 align:start position:0% we have been able to do it but but the more<01:11:14.490> so<01:11:15.500> smart<01:11:16.500> developers 01:11:18.640 --> 01:11:18.650 align:start position:0% more so smart developers 01:11:18.650 --> 01:11:21.040 align:start position:0% more so smart developers so<01:11:19.220> this<01:11:19.370> is<01:11:19.490> a<01:11:19.520> question<01:11:20.270> of<01:11:20.390> how<01:11:20.600> the<01:11:20.660> process 01:11:21.040 --> 01:11:21.050 align:start position:0% so this is a question of how the process 01:11:21.050 --> 01:11:24.420 align:start position:0% so this is a question of how the process of<01:11:21.770> suddenly<01:11:22.220> the<01:11:22.400> data<01:11:22.660> without<01:11:23.660> disclosing 01:11:24.420 --> 01:11:24.430 align:start position:0% of suddenly the data without disclosing 01:11:24.430 --> 01:11:27.160 align:start position:0% of suddenly the data without disclosing because<01:11:25.430> we<01:11:25.550> now<01:11:25.760> we<01:11:25.820> can<01:11:26.120> have<01:11:26.540> a<01:11:26.570> gentleman's 01:11:27.160 --> 01:11:27.170 align:start position:0% because we now we can have a gentleman's 01:11:27.170 --> 01:11:29.920 align:start position:0% because we now we can have a gentleman's agreement<01:11:27.290> and<01:11:28.040> we<01:11:28.340> know<01:11:28.550> that<01:11:28.790> maybe<01:11:29.150> it 01:11:29.920 --> 01:11:29.930 align:start position:0% agreement and we know that maybe it 01:11:29.930 --> 01:11:33.040 align:start position:0% agreement and we know that maybe it would<01:11:30.080> work<01:11:30.290> with<01:11:30.500> Alice<01:11:31.250> and<01:11:31.280> Bob<01:11:31.750> but<01:11:32.750> we<01:11:32.870> all 01:11:33.040 --> 01:11:33.050 align:start position:0% would work with Alice and Bob but we all 01:11:33.050 --> 01:11:35.430 align:start position:0% would work with Alice and Bob but we all know<01:11:33.290> something<01:11:33.590> about<01:11:33.830> Eva<01:11:34.280> right 01:11:35.430 --> 01:11:35.440 align:start position:0% know something about Eva right 01:11:35.440 --> 01:11:40.780 align:start position:0% know something about Eva right so<01:11:36.440> we<01:11:37.190> mustn't<01:11:37.460> trust<01:11:37.820> Eva<01:11:38.530> but<01:11:39.530> now<01:11:40.130> comes 01:11:40.780 --> 01:11:40.790 align:start position:0% so we mustn't trust Eva but now comes 01:11:40.790 --> 01:11:44.560 align:start position:0% so we mustn't trust Eva but now comes the<01:11:40.940> solution<01:11:41.260> and<01:11:42.260> the<01:11:42.410> solution<01:11:42.530> is<01:11:43.360> we<01:11:44.360> do 01:11:44.560 --> 01:11:44.570 align:start position:0% the solution and the solution is we do 01:11:44.570 --> 01:11:47.350 align:start position:0% the solution and the solution is we do everything<01:11:45.200> in<01:11:45.500> a<01:11:45.740> vault<01:11:46.010> we<01:11:46.700> do<01:11:46.910> everything 01:11:47.350 --> 01:11:47.360 align:start position:0% everything in a vault we do everything 01:11:47.360 --> 01:11:50.860 align:start position:0% everything in a vault we do everything in<01:11:47.660> a<01:11:47.750> special<01:11:48.260> banker<01:11:48.910> it's<01:11:49.910> a<01:11:50.210> software<01:11:50.600> Bank 01:11:50.860 --> 01:11:50.870 align:start position:0% in a special banker it's a software Bank 01:11:50.870 --> 01:11:53.710 align:start position:0% in a special banker it's a software Bank ERISA<01:11:51.440> is<01:11:52.100> about<01:11:52.580> your<01:11:52.760> made<01:11:52.910> of<01:11:53.030> dreams<01:11:53.270> of 01:11:53.710 --> 01:11:53.720 align:start position:0% ERISA is about your made of dreams of 01:11:53.720 --> 01:11:55.690 align:start position:0% ERISA is about your made of dreams of Sanjay<01:11:54.170> and<01:11:54.350> Eugene<01:11:54.830> and<01:11:55.070> other<01:11:55.220> people<01:11:55.580> in 01:11:55.690 --> 01:11:55.700 align:start position:0% Sanjay and Eugene and other people in 01:11:55.700 --> 01:11:56.290 align:start position:0% Sanjay and Eugene and other people in Enderlin 01:11:56.290 --> 01:11:56.300 align:start position:0% Enderlin 01:11:56.300 --> 01:12:00.190 align:start position:0% Enderlin other<01:11:56.960> people<01:11:57.380> from<01:11:57.530> Avalon<01:11:58.190> project<01:11:58.960> so<01:11:59.960> we 01:12:00.190 --> 01:12:00.200 align:start position:0% other people from Avalon project so we 01:12:00.200 --> 01:12:02.470 align:start position:0% other people from Avalon project so we have<01:12:00.560> this<01:12:00.830> cryptographically<01:12:01.520> secure<01:12:01.910> and 01:12:02.470 --> 01:12:02.480 align:start position:0% have this cryptographically secure and 01:12:02.480 --> 01:12:06.730 align:start position:0% have this cryptographically secure and plate<01:12:02.780> and<01:12:03.610> we<01:12:04.610> see<01:12:04.910> it<01:12:04.970> with<01:12:05.960> a<01:12:05.990> code<01:12:06.350> that 01:12:06.730 --> 01:12:06.740 align:start position:0% plate and we see it with a code that 01:12:06.740 --> 01:12:11.040 align:start position:0% plate and we see it with a code that everybody<01:12:07.580> has<01:12:07.820> seen<01:12:08.090> and<01:12:09.160> everybody<01:12:10.160> is 01:12:11.040 --> 01:12:11.050 align:start position:0% everybody has seen and everybody is 01:12:11.050 --> 01:12:14.710 align:start position:0% everybody has seen and everybody is Peapod<01:12:12.080> whoever<01:12:12.590> I<01:12:12.620> don't<01:12:12.950> know<01:12:13.100> why<01:12:13.540> this<01:12:14.540> is 01:12:14.710 --> 01:12:14.720 align:start position:0% Peapod whoever I don't know why this is 01:12:14.720 --> 01:12:16.720 align:start position:0% Peapod whoever I don't know why this is missing<01:12:15.080> what<01:12:15.260> I<01:12:15.440> find<01:12:15.740> things<01:12:15.980> happening<01:12:16.520> as 01:12:16.720 --> 01:12:16.730 align:start position:0% missing what I find things happening as 01:12:16.730 --> 01:12:23.110 align:start position:0% missing what I find things happening as you<01:12:16.880> move<01:12:17.150> from<01:12:20.980> windows<01:12:21.980> especially<01:12:22.940> this 01:12:23.110 --> 01:12:23.120 align:start position:0% you move from windows especially this 01:12:23.120 --> 01:12:29.890 align:start position:0% you move from windows especially this person<01:12:26.530> so<01:12:27.530> that<01:12:28.090> was<01:12:29.090> this<01:12:29.210> question<01:12:29.450> about 01:12:29.890 --> 01:12:29.900 align:start position:0% person so that was this question about 01:12:29.900 --> 01:12:35.890 align:start position:0% person so that was this question about how<01:12:30.290> to<01:12:30.350> trust<01:12:30.800> and<01:12:31.610> so<01:12:31.880> Vegas<01:12:32.660> if<01:12:33.110> you<01:12:33.730> see<01:12:34.900> the 01:12:35.890 --> 01:12:35.900 align:start position:0% how to trust and so Vegas if you see the 01:12:35.900 --> 01:12:38.590 align:start position:0% how to trust and so Vegas if you see the end<01:12:36.110> link<01:12:36.410> with<01:12:36.590> your<01:12:36.680> card<01:12:37.150> you<01:12:38.150> can<01:12:38.360> verify 01:12:38.590 --> 01:12:38.600 align:start position:0% end link with your card you can verify 01:12:38.600 --> 01:12:41.080 align:start position:0% end link with your card you can verify that<01:12:38.900> this<01:12:39.320> is<01:12:39.380> account<01:12:39.890> provided<01:12:40.850> that<01:12:40.940> you 01:12:41.080 --> 01:12:41.090 align:start position:0% that this is account provided that you 01:12:41.090 --> 01:12:44.470 align:start position:0% that this is account provided that you trust<01:12:41.360> Angie<01:12:42.670> but<01:12:43.670> this<01:12:43.850> is<01:12:43.940> a<01:12:44.000> minor<01:12:44.210> point 01:12:44.470 --> 01:12:44.480 align:start position:0% trust Angie but this is a minor point 01:12:44.480 --> 01:12:46.450 align:start position:0% trust Angie but this is a minor point conversion<01:12:44.870> of<01:12:45.320> we<01:12:45.440> are<01:12:45.620> bank<01:12:45.950> and<01:12:46.250> people 01:12:46.450 --> 01:12:46.460 align:start position:0% conversion of we are bank and people 01:12:46.460 --> 01:12:49.420 align:start position:0% conversion of we are bank and people trust<01:12:46.880> us<01:12:47.120> with<01:12:47.390> way<01:12:48.320> more<01:12:48.350> complex<01:12:49.130> things 01:12:49.420 --> 01:12:49.430 align:start position:0% trust us with way more complex things 01:12:49.430 --> 01:12:57.330 align:start position:0% trust us with way more complex things and<01:12:49.730> with<01:12:50.830> way<01:12:51.830> more<01:12:52.450> rational<01:12:53.450> knowledge<01:12:54.910> so 01:12:57.330 --> 01:12:57.340 align:start position:0% and with way more rational knowledge so 01:12:57.340 --> 01:13:01.860 align:start position:0% and with way more rational knowledge so agreed-upon<01:12:57.880> algorithm<01:12:59.130> and<01:13:00.130> now<01:13:00.870> everybody 01:13:01.860 --> 01:13:01.870 align:start position:0% agreed-upon algorithm and now everybody 01:13:01.870 --> 01:13:06.590 align:start position:0% agreed-upon algorithm and now everybody takes<01:13:02.350> an<01:13:02.560> envelope<01:13:03.480> from<01:13:04.480> the<01:13:05.050> vault<01:13:05.950> and 01:13:06.590 --> 01:13:06.600 align:start position:0% takes an envelope from the vault and 01:13:06.600 --> 01:13:09.540 align:start position:0% takes an envelope from the vault and everybody<01:13:07.600> was<01:13:07.900> there<01:13:08.530> data<01:13:08.800> into<01:13:09.460> the 01:13:09.540 --> 01:13:09.550 align:start position:0% everybody was there data into the 01:13:09.550 --> 01:13:14.580 align:start position:0% everybody was there data into the envelop<01:13:10.140> her<01:13:11.140> blouses<01:13:11.790> seals<01:13:12.790> and<01:13:13.440> puts<01:13:14.440> it 01:13:14.580 --> 01:13:14.590 align:start position:0% envelop her blouses seals and puts it 01:13:14.590 --> 01:13:18.360 align:start position:0% envelop her blouses seals and puts it into<01:13:15.010> the<01:13:15.280> Alembic<01:13:15.580> is<01:13:16.480> a<01:13:16.600> default<01:13:17.370> now 01:13:18.360 --> 01:13:18.370 align:start position:0% into the Alembic is a default now 01:13:18.370 --> 01:13:20.910 align:start position:0% into the Alembic is a default now without<01:13:18.760> words<01:13:19.030> kicks<01:13:19.810> it<01:13:20.020> it's<01:13:20.680> being 01:13:20.910 --> 01:13:20.920 align:start position:0% without words kicks it it's being 01:13:20.920 --> 01:13:25.650 align:start position:0% without words kicks it it's being processed<01:13:21.190> but<01:13:22.090> nobody<01:13:22.720> sees<01:13:23.580> the<01:13:24.660> assembled 01:13:25.650 --> 01:13:25.660 align:start position:0% processed but nobody sees the assembled 01:13:25.660 --> 01:13:29.220 align:start position:0% processed but nobody sees the assembled Angus<01:13:26.260> assemble<01:13:26.950> data<01:13:27.100> is<01:13:27.430> only<01:13:28.230> consolidated 01:13:29.220 --> 01:13:29.230 align:start position:0% Angus assemble data is only consolidated 01:13:29.230 --> 01:13:34.080 align:start position:0% Angus assemble data is only consolidated in<01:13:29.440> the<01:13:29.710> protected<01:13:30.250> memory<01:13:32.280> so<01:13:33.280> outcomes<01:13:33.880> on 01:13:34.080 --> 01:13:34.090 align:start position:0% in the protected memory so outcomes on 01:13:34.090 --> 01:13:37.620 align:start position:0% in the protected memory so outcomes on the<01:13:34.270> list<01:13:35.080> of<01:13:35.230> suspects<01:13:36.030> so<01:13:37.030> we<01:13:37.150> have<01:13:37.270> solved 01:13:37.620 --> 01:13:37.630 align:start position:0% the list of suspects so we have solved 01:13:37.630 --> 01:13:42.900 align:start position:0% the list of suspects so we have solved our<01:13:37.810> problem<01:13:38.320> and<01:13:39.210> a<01:13:40.860> little<01:13:41.860> vocabulary<01:13:42.580> here 01:13:42.900 --> 01:13:42.910 align:start position:0% our problem and a little vocabulary here 01:13:42.910 --> 01:13:48.660 align:start position:0% our problem and a little vocabulary here so<01:13:43.890> the<01:13:44.890> the<01:13:45.220> bunker<01:13:45.640> is<01:13:45.970> the<01:13:47.100> SG<01:13:48.100> exactly 01:13:48.660 --> 01:13:48.670 align:start position:0% so the the bunker is the SG exactly 01:13:48.670 --> 01:13:55.760 align:start position:0% so the the bunker is the SG exactly wrapped<01:13:49.480> in<01:13:50.410> the<01:13:50.680> abalone<01:13:52.830> framework<01:13:53.830> for<01:13:54.100> our 01:13:55.760 --> 01:13:55.770 align:start position:0% wrapped in the abalone framework for our 01:13:55.770 --> 01:14:01.710 align:start position:0% wrapped in the abalone framework for our utility<01:13:56.880> the<01:13:57.880> envelope<01:13:58.450> is<01:13:59.260> a<01:14:00.010> public<01:14:00.880> RSA<01:14:01.330> key 01:14:01.710 --> 01:14:01.720 align:start position:0% utility the envelope is a public RSA key 01:14:01.720 --> 01:14:05.790 align:start position:0% utility the envelope is a public RSA key so<01:14:02.650> as<01:14:03.190> we<01:14:03.520> start<01:14:03.910> the<01:14:04.300> end<01:14:04.450> plate<01:14:04.690> the<01:14:05.380> keeper 01:14:05.790 --> 01:14:05.800 align:start position:0% so as we start the end plate the keeper 01:14:05.800 --> 01:14:08.430 align:start position:0% so as we start the end plate the keeper is<01:14:05.950> generated<01:14:06.550> but<01:14:07.300> only<01:14:07.570> the<01:14:07.840> public<01:14:07.990> key<01:14:08.410> is 01:14:08.430 --> 01:14:08.440 align:start position:0% is generated but only the public key is 01:14:08.440 --> 01:14:13.050 align:start position:0% is generated but only the public key is revealed<01:14:09.570> so<01:14:11.070> everybody<01:14:12.070> in<01:14:12.490> the<01:14:12.520> world<01:14:12.850> can 01:14:13.050 --> 01:14:13.060 align:start position:0% revealed so everybody in the world can 01:14:13.060 --> 01:14:15.300 align:start position:0% revealed so everybody in the world can encrypt<01:14:13.570> of<01:14:14.020> the<01:14:14.200> stuff<01:14:14.560> and<01:14:14.740> only<01:14:15.160> the 01:14:15.300 --> 01:14:15.310 align:start position:0% encrypt of the stuff and only the 01:14:15.310 --> 01:14:18.660 align:start position:0% encrypt of the stuff and only the decrypted<01:14:15.820> inside<01:14:16.150> yesterday<01:14:17.070> or<01:14:18.070> maybe<01:14:18.130> by 01:14:18.660 --> 01:14:18.670 align:start position:0% decrypted inside yesterday or maybe by 01:14:18.670 --> 01:14:21.680 align:start position:0% decrypted inside yesterday or maybe by sake 01:14:21.680 --> 01:14:21.690 align:start position:0% 01:14:21.690 --> 01:14:24.440 align:start position:0% now<01:14:22.440> the<01:14:22.500> seal<01:14:22.980> of<01:14:23.400> course<01:14:24.000> we<01:14:24.210> want 01:14:24.440 --> 01:14:24.450 align:start position:0% now the seal of course we want 01:14:24.450 --> 01:14:28.010 align:start position:0% now the seal of course we want commitment<01:14:24.990> we<01:14:25.620> want<01:14:25.860> people<01:14:26.070> to<01:14:27.020> certify 01:14:28.010 --> 01:14:28.020 align:start position:0% commitment we want people to certify 01:14:28.020 --> 01:14:30.290 align:start position:0% commitment we want people to certify this<01:14:28.290> that<01:14:28.650> they<01:14:28.770> not<01:14:28.950> able<01:14:29.070> to<01:14:29.220> commit<01:14:29.580> so 01:14:30.290 --> 01:14:30.300 align:start position:0% this that they not able to commit so 01:14:30.300 --> 01:14:33.500 align:start position:0% this that they not able to commit so there<01:14:30.540> is<01:14:30.720> an<01:14:31.440> elliptic<01:14:31.920> curve<01:14:32.190> in<01:14:33.090> this<01:14:33.240> curve 01:14:33.500 --> 01:14:33.510 align:start position:0% there is an elliptic curve in this curve 01:14:33.510 --> 01:14:37.120 align:start position:0% there is an elliptic curve in this curve actually<01:14:34.400> sign<01:14:35.400> signature<01:14:36.120> on<01:14:36.270> it 01:14:37.120 --> 01:14:37.130 align:start position:0% actually sign signature on it 01:14:37.130 --> 01:14:42.260 align:start position:0% actually sign signature on it and<01:14:38.130> now<01:14:39.410> couple<01:14:40.410> of<01:14:40.470> questions<01:14:41.040> here<01:14:41.340> so<01:14:41.610> one 01:14:42.260 --> 01:14:42.270 align:start position:0% and now couple of questions here so one 01:14:42.270 --> 01:14:45.980 align:start position:0% and now couple of questions here so one was<01:14:42.750> already<01:14:43.110> asked<01:14:43.940> how<01:14:44.940> can<01:14:45.660> you<01:14:45.780> be<01:14:45.960> sure 01:14:45.980 --> 01:14:45.990 align:start position:0% was already asked how can you be sure 01:14:45.990 --> 01:14:49.550 align:start position:0% was already asked how can you be sure that<01:14:47.030> there<01:14:48.030> is<01:14:48.150> no<01:14:48.330> trapdoor<01:14:48.900> there<01:14:49.080> is<01:14:49.200> no 01:14:49.550 --> 01:14:49.560 align:start position:0% that there is no trapdoor there is no 01:14:49.560 --> 01:14:51.380 align:start position:0% that there is no trapdoor there is no and<01:14:50.160> the<01:14:50.280> malicious<01:14:50.700> code<01:14:50.790> inside<01:14:51.330> the 01:14:51.380 --> 01:14:51.390 align:start position:0% and the malicious code inside the 01:14:51.390 --> 01:14:56.240 align:start position:0% and the malicious code inside the enclaves<01:14:52.190> so<01:14:53.190> this<01:14:53.660> we<01:14:54.660> can<01:14:54.840> do<01:14:55.250> by 01:14:56.240 --> 01:14:56.250 align:start position:0% enclaves so this we can do by 01:14:56.250 --> 01:14:59.300 align:start position:0% enclaves so this we can do by efficiently<01:14:56.970> codes<01:14:57.210> and<01:14:57.660> by<01:14:58.500> publishing<01:14:58.890> on 01:14:59.300 --> 01:14:59.310 align:start position:0% efficiently codes and by publishing on 01:14:59.310 --> 01:15:01.580 align:start position:0% efficiently codes and by publishing on chain<01:14:59.670> and<01:15:00.000> this<01:15:00.420> section<01:15:00.660> where<01:15:01.020> blockchain 01:15:01.580 --> 01:15:01.590 align:start position:0% chain and this section where blockchain 01:15:01.590 --> 01:15:05.150 align:start position:0% chain and this section where blockchain how<01:15:01.740> sensitive<01:15:02.250> us<01:15:03.350> so<01:15:04.350> far<01:15:04.650> you<01:15:04.830> would<01:15:04.980> ask 01:15:05.150 --> 01:15:05.160 align:start position:0% how sensitive us so far you would ask 01:15:05.160 --> 01:15:10.400 align:start position:0% how sensitive us so far you would ask okay<01:15:05.720> this<01:15:06.720> story<01:15:07.010> but<01:15:08.010> white<01:15:08.340> object<01:15:09.410> what 01:15:10.400 --> 01:15:10.410 align:start position:0% okay this story but white object what 01:15:10.410 --> 01:15:14.180 align:start position:0% okay this story but white object what for<01:15:10.710> so<01:15:11.700> one<01:15:11.910> thing<01:15:12.120> is<01:15:12.330> where<01:15:13.230> you<01:15:13.530> when<01:15:14.160> I 01:15:14.180 --> 01:15:14.190 align:start position:0% for so one thing is where you when I 01:15:14.190 --> 01:15:17.590 align:start position:0% for so one thing is where you when I advertise<01:15:14.970> my<01:15:15.810> android<01:15:16.470> to<01:15:17.010> other 01:15:17.590 --> 01:15:17.600 align:start position:0% advertise my android to other 01:15:17.600 --> 01:15:23.260 align:start position:0% advertise my android to other participants<01:15:18.600> I<01:15:19.640> should<01:15:20.690> offer<01:15:21.690> a<01:15:21.960> number<01:15:22.230> of 01:15:23.260 --> 01:15:23.270 align:start position:0% participants I should offer a number of 01:15:23.270 --> 01:15:27.500 align:start position:0% participants I should offer a number of certificates<01:15:24.890> say<01:15:25.890> do<01:15:26.280> you<01:15:26.760> guarantee<01:15:26.940> that 01:15:27.500 --> 01:15:27.510 align:start position:0% certificates say do you guarantee that 01:15:27.510 --> 01:15:29.600 align:start position:0% certificates say do you guarantee that one<01:15:28.020> thing<01:15:28.260> is<01:15:28.410> that<01:15:28.620> the<01:15:28.710> code<01:15:28.950> there<01:15:29.370> is 01:15:29.600 --> 01:15:29.610 align:start position:0% one thing is that the code there is 01:15:29.610 --> 01:15:32.180 align:start position:0% one thing is that the code there is actually<01:15:30.120> this<01:15:30.240> and<01:15:30.540> then<01:15:30.840> if<01:15:31.440> they<01:15:31.740> use 01:15:32.180 --> 01:15:32.190 align:start position:0% actually this and then if they use 01:15:32.190 --> 01:15:35.090 align:start position:0% actually this and then if they use attestation<01:15:32.520> service<01:15:33.470> if<01:15:34.470> they<01:15:34.530> have<01:15:34.890> those 01:15:35.090 --> 01:15:35.100 align:start position:0% attestation service if they have those 01:15:35.100 --> 01:15:37.250 align:start position:0% attestation service if they have those cryptographic<01:15:35.940> primitives<01:15:36.690> think<01:15:36.990> and 01:15:37.250 --> 01:15:37.260 align:start position:0% cryptographic primitives think and 01:15:37.260 --> 01:15:40.550 align:start position:0% cryptographic primitives think and verify<01:15:37.940> themselves<01:15:38.940> that<01:15:39.720> this<01:15:39.990> is<01:15:40.170> actually 01:15:40.550 --> 01:15:40.560 align:start position:0% verify themselves that this is actually 01:15:40.560 --> 01:15:42.470 align:start position:0% verify themselves that this is actually the<01:15:40.590> code<01:15:40.890> there<01:15:41.400> is<01:15:41.430> no<01:15:41.700> traveler<01:15:42.000> or<01:15:42.270> there 01:15:42.470 --> 01:15:42.480 align:start position:0% the code there is no traveler or there 01:15:42.480 --> 01:15:46.160 align:start position:0% the code there is no traveler or there is<01:15:42.600> no<01:15:43.730> funny<01:15:44.730> thing<01:15:45.030> and<01:15:45.180> the<01:15:45.630> other<01:15:45.780> question 01:15:46.160 --> 01:15:46.170 align:start position:0% is no funny thing and the other question 01:15:46.170 --> 01:15:49.400 align:start position:0% is no funny thing and the other question that<01:15:46.410> you<01:15:46.650> can<01:15:46.800> ask<01:15:47.010> is<01:15:47.720> how<01:15:48.720> can<01:15:49.050> we<01:15:49.080> guarantee 01:15:49.400 --> 01:15:49.410 align:start position:0% that you can ask is how can we guarantee 01:15:49.410 --> 01:15:52.370 align:start position:0% that you can ask is how can we guarantee the<01:15:49.950> people<01:15:50.280> that<01:15:50.430> achieve<01:15:50.780> by<01:15:51.780> submitting 01:15:52.370 --> 01:15:52.380 align:start position:0% the people that achieve by submitting 01:15:52.380 --> 01:15:57.740 align:start position:0% the people that achieve by submitting false<01:15:53.100> data<01:15:53.460> you<01:15:54.330> know<01:15:54.450> we<01:15:54.570> find<01:15:54.810> in<01:15:55.530> La<01:15:55.740> Paz<01:15:56.750> if 01:15:57.740 --> 01:15:57.750 align:start position:0% false data you know we find in La Paz if 01:15:57.750 --> 01:16:02.570 align:start position:0% false data you know we find in La Paz if we've<01:15:58.230> chances<01:15:58.740> my<01:15:58.890> customer<01:15:59.400> and<01:16:01.160> I<01:16:02.160> want<01:16:02.490> to 01:16:02.570 --> 01:16:02.580 align:start position:0% we've chances my customer and I want to 01:16:02.580 --> 01:16:06.090 align:start position:0% we've chances my customer and I want to protect<01:16:03.000> you<01:16:03.380> from<01:16:04.380> a<01:16:04.740> well<01:16:05.070> algorithm 01:16:06.090 --> 01:16:06.100 align:start position:0% protect you from a well algorithm 01:16:06.100 --> 01:16:10.070 align:start position:0% protect you from a well algorithm I<01:16:06.130> may<01:16:06.940> be<01:16:07.000> sending<01:16:07.570> you<01:16:08.440> know<01:16:08.650> come<01:16:08.980> predicta 01:16:10.070 --> 01:16:10.080 align:start position:0% I may be sending you know come predicta 01:16:10.080 --> 01:16:13.920 align:start position:0% I may be sending you know come predicta but<01:16:11.080> this<01:16:11.380> actually<01:16:11.770> is<01:16:12.400> a<01:16:12.970> moment<01:16:13.420> when<01:16:13.600> again 01:16:13.920 --> 01:16:13.930 align:start position:0% but this actually is a moment when again 01:16:13.930 --> 01:16:16.320 align:start position:0% but this actually is a moment when again blockchain<01:16:14.680> comes<01:16:14.920> handy<01:16:15.340> because<01:16:15.820> I<01:16:16.090> can 01:16:16.320 --> 01:16:16.330 align:start position:0% blockchain comes handy because I can 01:16:16.330 --> 01:16:19.170 align:start position:0% blockchain comes handy because I can gather<01:16:16.540> commitments<01:16:17.260> I<01:16:17.440> can<01:16:17.920> gather<01:16:18.100> and<01:16:18.670> for 01:16:19.170 --> 01:16:19.180 align:start position:0% gather commitments I can gather and for 01:16:19.180 --> 01:16:21.780 align:start position:0% gather commitments I can gather and for essentially<01:16:19.810> a<01:16:19.840> hash<01:16:20.140> of<01:16:20.590> the<01:16:21.130> submitted<01:16:21.520> data 01:16:21.780 --> 01:16:21.790 align:start position:0% essentially a hash of the submitted data 01:16:21.790 --> 01:16:25.200 align:start position:0% essentially a hash of the submitted data and<01:16:22.300> then<01:16:22.960> at<01:16:23.260> any<01:16:23.530> time<01:16:23.860> in<01:16:24.130> the<01:16:24.310> future<01:16:24.580> and 01:16:25.200 --> 01:16:25.210 align:start position:0% and then at any time in the future and 01:16:25.210 --> 01:16:28.230 align:start position:0% and then at any time in the future and all<01:16:25.360> that<01:16:25.540> have<01:16:25.720> come<01:16:25.980> to<01:16:26.980> this<01:16:27.100> body<01:16:27.340> say<01:16:27.700> okay 01:16:28.230 --> 01:16:28.240 align:start position:0% all that have come to this body say okay 01:16:28.240 --> 01:16:30.660 align:start position:0% all that have come to this body say okay present<01:16:28.750> the<01:16:28.810> data<01:16:28.960> and<01:16:29.830> prepare<01:16:30.100> against<01:16:30.520> the 01:16:30.660 --> 01:16:30.670 align:start position:0% present the data and prepare against the 01:16:30.670 --> 01:16:33.210 align:start position:0% present the data and prepare against the action<01:16:31.030> so<01:16:31.840> this<01:16:32.170> is<01:16:32.320> not<01:16:32.500> perfect<01:16:32.710> but<01:16:33.040> this 01:16:33.210 --> 01:16:33.220 align:start position:0% action so this is not perfect but this 01:16:33.220 --> 01:16:35.760 align:start position:0% action so this is not perfect but this is<01:16:33.340> as<01:16:33.580> good<01:16:33.610> as<01:16:34.090> can<01:16:34.330> be<01:16:34.510> because<01:16:34.840> if<01:16:35.530> we 01:16:35.760 --> 01:16:35.770 align:start position:0% is as good as can be because if we 01:16:35.770 --> 01:16:37.590 align:start position:0% is as good as can be because if we protect<01:16:36.190> the<01:16:36.280> data<01:16:36.460> is<01:16:36.670> protected<01:16:36.910> so<01:16:37.390> there 01:16:37.590 --> 01:16:37.600 align:start position:0% protect the data is protected so there 01:16:37.600 --> 01:16:40.080 align:start position:0% protect the data is protected so there is<01:16:37.720> no<01:16:37.930> verification<01:16:38.590> of<01:16:38.680> data<01:16:38.740> quality<01:16:39.100> of 01:16:40.080 --> 01:16:40.090 align:start position:0% is no verification of data quality of 01:16:40.090 --> 01:16:42.750 align:start position:0% is no verification of data quality of truthfulness<01:16:40.870> but<01:16:41.230> what<01:16:41.410> we<01:16:41.560> can<01:16:41.740> do<01:16:42.250> is<01:16:42.580> we 01:16:42.750 --> 01:16:42.760 align:start position:0% truthfulness but what we can do is we 01:16:42.760 --> 01:16:47.910 align:start position:0% truthfulness but what we can do is we can<01:16:42.940> gather<01:16:43.540> and<01:16:45.390> memorize<01:16:46.390> and<01:16:46.990> store<01:16:47.410> the 01:16:47.910 --> 01:16:47.920 align:start position:0% can gather and memorize and store the 01:16:47.920 --> 01:16:52.560 align:start position:0% can gather and memorize and store the commitment<01:16:48.690> for<01:16:49.690> future<01:16:50.020> verification<01:16:51.570> so 01:16:52.560 --> 01:16:52.570 align:start position:0% commitment for future verification so 01:16:52.570 --> 01:16:54.390 align:start position:0% commitment for future verification so we've<01:16:52.780> done<01:16:52.990> this<01:16:53.170> and<01:16:53.440> we<01:16:53.560> are<01:16:53.590> contributing 01:16:54.390 --> 01:16:54.400 align:start position:0% we've done this and we are contributing 01:16:54.400 --> 01:16:56.820 align:start position:0% we've done this and we are contributing this<01:16:55.000> is<01:16:55.180> a<01:16:55.210> use<01:16:55.450> case<01:16:55.720> and<01:16:56.260> we've<01:16:56.410> done<01:16:56.620> this 01:16:56.820 --> 01:16:56.830 align:start position:0% this is a use case and we've done this 01:16:56.830 --> 01:16:59.220 align:start position:0% this is a use case and we've done this in<01:16:56.890> a<01:16:57.160> way<01:16:57.310> that<01:16:57.540> like<01:16:58.540> we<01:16:58.720> are<01:16:58.810> properly 01:16:59.220 --> 01:16:59.230 align:start position:0% in a way that like we are properly 01:16:59.230 --> 01:17:02.370 align:start position:0% in a way that like we are properly paranoid<01:16:59.860> about<01:17:00.490> photography<01:17:01.110> so<01:17:02.110> there<01:17:02.320> are 01:17:02.370 --> 01:17:02.380 align:start position:0% paranoid about photography so there are 01:17:02.380 --> 01:17:06.090 align:start position:0% paranoid about photography so there are two<01:17:02.650> components<01:17:03.370> one<01:17:03.550> is<01:17:04.440> the<01:17:05.440> application 01:17:06.090 --> 01:17:06.100 align:start position:0% two components one is the application 01:17:06.100 --> 01:17:08.370 align:start position:0% two components one is the application and<01:17:06.220> we<01:17:06.370> are<01:17:06.670> we<01:17:07.060> were<01:17:07.210> ready<01:17:07.450> to<01:17:07.540> present<01:17:07.840> but 01:17:08.370 --> 01:17:08.380 align:start position:0% and we are we were ready to present but 01:17:08.380 --> 01:17:11.430 align:start position:0% and we are we were ready to present but you<01:17:08.680> know<01:17:08.830> time<01:17:09.160> constraints<01:17:10.030> Network 01:17:11.430 --> 01:17:11.440 align:start position:0% you know time constraints Network 01:17:11.440 --> 01:17:14.870 align:start position:0% you know time constraints Network what<01:17:12.429> component<01:17:13.060> is<01:17:13.330> the<01:17:13.690> client<01:17:14.199> that<01:17:14.349> you 01:17:14.870 --> 01:17:14.880 align:start position:0% what component is the client that you 01:17:14.880 --> 01:17:18.359 align:start position:0% what component is the client that you talk<01:17:15.880> to<01:17:16.150> the<01:17:16.330> end<01:17:16.510> plate<01:17:17.070> so<01:17:18.070> that<01:17:18.250> you 01:17:18.359 --> 01:17:18.369 align:start position:0% talk to the end plate so that you 01:17:18.369 --> 01:17:21.500 align:start position:0% talk to the end plate so that you discover<01:17:18.849> the<01:17:19.090> worker<01:17:19.540> that<01:17:19.750> you<01:17:19.810> get<01:17:20.170> all<01:17:20.980> the 01:17:21.500 --> 01:17:21.510 align:start position:0% discover the worker that you get all the 01:17:21.510 --> 01:17:23.640 align:start position:0% discover the worker that you get all the cryptographic<01:17:22.510> primitives<01:17:23.199> that<01:17:23.349> you<01:17:23.500> need 01:17:23.640 --> 01:17:23.650 align:start position:0% cryptographic primitives that you need 01:17:23.650 --> 01:17:27.120 align:start position:0% cryptographic primitives that you need base<01:17:23.860> the<01:17:24.070> runs<01:17:24.310> and<01:17:25.150> the<01:17:25.270> addresses<01:17:25.599> and<01:17:26.130> the 01:17:27.120 --> 01:17:27.130 align:start position:0% base the runs and the addresses and the 01:17:27.130 --> 01:17:28.669 align:start position:0% base the runs and the addresses and the other<01:17:27.280> component<01:17:27.880> is<01:17:28.030> a<01:17:28.060> standalone 01:17:28.669 --> 01:17:28.679 align:start position:0% other component is a standalone 01:17:28.679 --> 01:17:32.430 align:start position:0% other component is a standalone encryption<01:17:29.679> application<01:17:30.250> so<01:17:30.760> we<01:17:31.270> say<01:17:31.449> okay<01:17:31.750> if 01:17:32.430 --> 01:17:32.440 align:start position:0% encryption application so we say okay if 01:17:32.440 --> 01:17:34.020 align:start position:0% encryption application so we say okay if you're<01:17:32.650> really<01:17:32.889> paranoid<01:17:33.159> about<01:17:33.610> your<01:17:33.880> data 01:17:34.020 --> 01:17:34.030 align:start position:0% you're really paranoid about your data 01:17:34.030 --> 01:17:37.410 align:start position:0% you're really paranoid about your data you<01:17:34.780> don't<01:17:34.989> want<01:17:35.230> to<01:17:35.290> encrypt<01:17:35.730> in<01:17:36.730> an<01:17:36.940> app<01:17:37.090> at 01:17:37.410 --> 01:17:37.420 align:start position:0% you don't want to encrypt in an app at 01:17:37.420 --> 01:17:40.410 align:start position:0% you don't want to encrypt in an app at this<01:17:37.599> online<01:17:37.900> connected<01:17:38.650> to<01:17:38.770> something<01:17:39.420> you 01:17:40.410 --> 01:17:40.420 align:start position:0% this online connected to something you 01:17:40.420 --> 01:17:44.399 align:start position:0% this online connected to something you just<01:17:40.920> take<01:17:41.920> the<01:17:42.219> public<01:17:42.580> key<01:17:42.929> will<01:17:43.929> transfer 01:17:44.399 --> 01:17:44.409 align:start position:0% just take the public key will transfer 01:17:44.409 --> 01:17:46.350 align:start position:0% just take the public key will transfer it<01:17:44.560> somehow<01:17:44.860> hopefully<01:17:45.610> not<01:17:45.790> on<01:17:45.820> the<01:17:46.030> Russian 01:17:46.350 --> 01:17:46.360 align:start position:0% it somehow hopefully not on the Russian 01:17:46.360 --> 01:17:49.379 align:start position:0% it somehow hopefully not on the Russian USB<01:17:46.750> stick<01:17:47.130> to<01:17:48.130> an<01:17:48.790> air-gapped<01:17:49.300> computer 01:17:49.379 --> 01:17:49.389 align:start position:0% USB stick to an air-gapped computer 01:17:49.389 --> 01:17:51.990 align:start position:0% USB stick to an air-gapped computer related<01:17:50.199> to<01:17:50.469> the<01:17:50.590> basement<01:17:50.800> there<01:17:51.639> you<01:17:51.820> do 01:17:51.990 --> 01:17:52.000 align:start position:0% related to the basement there you do 01:17:52.000 --> 01:17:54.000 align:start position:0% related to the basement there you do your<01:17:52.030> decryption<01:17:52.719> there<01:17:53.440> you<01:17:53.650> build<01:17:53.830> your 01:17:54.000 --> 01:17:54.010 align:start position:0% your decryption there you build your 01:17:54.010 --> 01:17:57.450 align:start position:0% your decryption there you build your JSON<01:17:54.639> message<01:17:55.560> you<01:17:56.560> bring<01:17:56.710> it<01:17:56.949> back<01:17:57.130> to<01:17:57.190> the 01:17:57.450 --> 01:17:57.460 align:start position:0% JSON message you bring it back to the 01:17:57.460 --> 01:18:01.800 align:start position:0% JSON message you bring it back to the application<01:17:57.580> you<01:17:58.030> send<01:17:58.360> it<01:17:59.010> and<01:18:00.540> then<01:18:01.540> we 01:18:01.800 --> 01:18:01.810 align:start position:0% application you send it and then we 01:18:01.810 --> 01:18:03.899 align:start position:0% application you send it and then we stretch<01:18:02.739> a<01:18:02.949> little<01:18:03.130> bit<01:18:03.280> the<01:18:03.489> framework 01:18:03.899 --> 01:18:03.909 align:start position:0% stretch a little bit the framework 01:18:03.909 --> 01:18:07.140 align:start position:0% stretch a little bit the framework because<01:18:04.920> you<01:18:05.920> can<01:18:06.099> recognize<01:18:06.429> that<01:18:06.639> the<01:18:07.119> word 01:18:07.140 --> 01:18:07.150 align:start position:0% because you can recognize that the word 01:18:07.150 --> 01:18:09.959 align:start position:0% because you can recognize that the word becomes<01:18:07.810> stateful<01:18:08.500> because<01:18:09.099> it<01:18:09.219> way<01:18:09.400> waits 01:18:09.959 --> 01:18:09.969 align:start position:0% becomes stateful because it way waits 01:18:09.969 --> 01:18:12.209 align:start position:0% becomes stateful because it way waits for<01:18:10.270> all<01:18:10.300> the<01:18:10.599> data<01:18:10.810> space<01:18:11.170> but<01:18:11.980> this<01:18:12.070> is 01:18:12.209 --> 01:18:12.219 align:start position:0% for all the data space but this is 01:18:12.219 --> 01:18:15.390 align:start position:0% for all the data space but this is anyhow<01:18:12.610> on<01:18:12.880> the<01:18:13.119> roadmap<01:18:13.869> of<01:18:14.409> the<01:18:15.250> other 01:18:15.390 --> 01:18:15.400 align:start position:0% anyhow on the roadmap of the other 01:18:15.400 --> 01:18:22.050 align:start position:0% anyhow on the roadmap of the other project<01:18:16.469> other<01:18:17.469> is<01:18:18.719> to<01:18:19.719> do<01:18:19.900> but<01:18:21.030> you<01:18:22.030> know 01:18:22.050 --> 01:18:22.060 align:start position:0% project other is to do but you know 01:18:22.060 --> 01:18:26.520 align:start position:0% project other is to do but you know we've<01:18:22.750> managed<01:18:23.290> to<01:18:23.320> pull<01:18:23.619> it<01:18:23.710> up<01:18:24.540> so<01:18:25.540> thank<01:18:26.409> you 01:18:26.520 --> 01:18:26.530 align:start position:0% we've managed to pull it up so thank you 01:18:26.530 --> 01:18:30.000 align:start position:0% we've managed to pull it up so thank you very<01:18:26.560> much<01:18:27.090> it's<01:18:28.090> like<01:18:28.500> really<01:18:29.500> exciting 01:18:30.000 --> 01:18:30.010 align:start position:0% very much it's like really exciting 01:18:30.010 --> 01:18:32.200 align:start position:0% very much it's like really exciting these<01:18:30.550> are<01:18:30.730> screenshots 01:18:32.200 --> 01:18:32.210 align:start position:0% these are screenshots 01:18:32.210 --> 01:18:40.910 align:start position:0% these are screenshots you<01:18:33.210> can<01:18:33.530> connect<01:18:38.030> at<01:18:39.030> the<01:18:39.059> moment<01:18:39.770> lots<01:18:40.770> of 01:18:40.910 --> 01:18:40.920 align:start position:0% you can connect at the moment lots of 01:18:40.920 --> 01:18:42.740 align:start position:0% you can connect at the moment lots of funny<01:18:41.190> stories<01:18:41.639> like<01:18:41.820> at<01:18:41.969> the<01:18:42.090> moment<01:18:42.239> the 01:18:42.740 --> 01:18:42.750 align:start position:0% funny stories like at the moment the 01:18:42.750 --> 01:18:46.069 align:start position:0% funny stories like at the moment the abalone<01:18:43.550> uses<01:18:44.550> those<01:18:44.820> pretty<01:18:45.329> names<01:18:45.719> to 01:18:46.069 --> 01:18:46.079 align:start position:0% abalone uses those pretty names to 01:18:46.079 --> 01:18:49.280 align:start position:0% abalone uses those pretty names to identify<01:18:46.170> workers<01:18:47.099> so<01:18:47.670> normally<01:18:48.449> you<01:18:48.809> go<01:18:49.139> to 01:18:49.280 --> 01:18:49.290 align:start position:0% identify workers so normally you go to 01:18:49.290 --> 01:18:51.729 align:start position:0% identify workers so normally you go to block<01:18:49.500> that<01:18:49.710> you<01:18:49.770> would<01:18:49.980> have<01:18:50.159> a<01:18:50.190> list<01:18:50.540> of 01:18:51.729 --> 01:18:51.739 align:start position:0% block that you would have a list of 01:18:51.739 --> 01:18:56.439 align:start position:0% block that you would have a list of workers<01:18:52.739> available<01:18:52.940> these<01:18:53.940> are<01:18:54.119> their<01:18:54.599> names 01:18:56.439 --> 01:18:56.449 align:start position:0% workers available these are their names 01:18:56.449 --> 01:18:59.089 align:start position:0% workers available these are their names something<01:18:57.449> to<01:18:57.570> work<01:18:57.780> about<01:18:58.050> you<01:18:58.800> press 01:18:59.089 --> 01:18:59.099 align:start position:0% something to work about you press 01:18:59.099 --> 01:19:01.970 align:start position:0% something to work about you press details<01:18:59.699> and<01:19:00.030> you<01:19:00.150> get<01:19:00.619> stuff<01:19:01.619> that<01:19:01.829> you 01:19:01.970 --> 01:19:01.980 align:start position:0% details and you get stuff that you 01:19:01.980 --> 01:19:04.310 align:start position:0% details and you get stuff that you actually<01:19:02.159> need<01:19:02.610> like<01:19:03.210> the<01:19:03.630> encryption<01:19:04.139> other 01:19:04.310 --> 01:19:04.320 align:start position:0% actually need like the encryption other 01:19:04.320 --> 01:19:06.109 align:start position:0% actually need like the encryption other key<01:19:04.619> so<01:19:05.219> this<01:19:05.369> is<01:19:05.550> the<01:19:05.670> stuff<01:19:05.909> that<01:19:05.940> you 01:19:06.109 --> 01:19:06.119 align:start position:0% key so this is the stuff that you 01:19:06.119 --> 01:19:09.350 align:start position:0% key so this is the stuff that you publicize<01:19:06.599> that<01:19:06.840> you<01:19:07.010> take<01:19:08.010> to<01:19:09.000> your<01:19:09.150> basement 01:19:09.350 --> 01:19:09.360 align:start position:0% publicize that you take to your basement 01:19:09.360 --> 01:19:14.240 align:start position:0% publicize that you take to your basement community<01:19:11.000> and<01:19:12.000> the<01:19:12.840> gather<01:19:13.079> is<01:19:13.650> a<01:19:13.800> screenshot 01:19:14.240 --> 01:19:14.250 align:start position:0% community and the gather is a screenshot 01:19:14.250 --> 01:19:19.310 align:start position:0% community and the gather is a screenshot of<01:19:14.489> the<01:19:16.520> standard<01:19:17.520> encryption<01:19:17.849> app<01:19:18.210> so<01:19:18.480> first 01:19:19.310 --> 01:19:19.320 align:start position:0% of the standard encryption app so first 01:19:19.320 --> 01:19:22.339 align:start position:0% of the standard encryption app so first you<01:19:19.710> need<01:19:20.159> to<01:19:20.190> define<01:19:20.690> how<01:19:21.690> many<01:19:21.750> data's 01:19:22.339 --> 01:19:22.349 align:start position:0% you need to define how many data's 01:19:22.349 --> 01:19:25.399 align:start position:0% you need to define how many data's things<01:19:22.650> are<01:19:23.099> there<01:19:23.429> then<01:19:24.119> you<01:19:24.329> need<01:19:24.540> to<01:19:24.840> submit 01:19:25.399 --> 01:19:25.409 align:start position:0% things are there then you need to submit 01:19:25.409 --> 01:19:28.100 align:start position:0% things are there then you need to submit your<01:19:25.559> data<01:19:25.829> as<01:19:26.460> a<01:19:26.730> separated<01:19:27.360> value<01:19:27.599> files<01:19:27.840> in 01:19:28.100 --> 01:19:28.110 align:start position:0% your data as a separated value files in 01:19:28.110 --> 01:19:30.740 align:start position:0% your data as a separated value files in our<01:19:28.489> if<01:19:29.489> you<01:19:29.699> will<01:19:29.909> be<01:19:30.030> able<01:19:30.300> to<01:19:30.420> work<01:19:30.570> with 01:19:30.740 --> 01:19:30.750 align:start position:0% our if you will be able to work with 01:19:30.750 --> 01:19:32.270 align:start position:0% our if you will be able to work with this<01:19:30.869> example<01:19:31.230> because<01:19:31.559> we're<01:19:31.800> committing 01:19:32.270 --> 01:19:32.280 align:start position:0% this example because we're committing 01:19:32.280 --> 01:19:36.049 align:start position:0% this example because we're committing this<01:19:32.429> to<01:19:32.699> do<01:19:32.880> the<01:19:33.750> project<01:19:34.710> it<01:19:35.280> is<01:19:35.520> already<01:19:35.820> on 01:19:36.049 --> 01:19:36.059 align:start position:0% this to do the project it is already on 01:19:36.059 --> 01:19:39.040 align:start position:0% this to do the project it is already on the<01:19:36.179> branch<01:19:36.889> then<01:19:37.889> you<01:19:38.040> have<01:19:38.159> pursue<01:19:38.579> you 01:19:39.040 --> 01:19:39.050 align:start position:0% the branch then you have pursue you 01:19:39.050 --> 01:19:41.870 align:start position:0% the branch then you have pursue you create<01:19:40.050> the<01:19:40.260> JSON<01:19:40.650> file<01:19:40.889> in<01:19:41.190> we<01:19:41.309> review<01:19:41.730> the 01:19:41.870 --> 01:19:41.880 align:start position:0% create the JSON file in we review the 01:19:41.880 --> 01:19:44.930 align:start position:0% create the JSON file in we review the justified<01:19:42.420> before<01:19:42.630> it<01:19:43.050> is<01:19:43.199> encrypted<01:19:43.940> then 01:19:44.930 --> 01:19:44.940 align:start position:0% justified before it is encrypted then 01:19:44.940 --> 01:19:48.649 align:start position:0% justified before it is encrypted then you<01:19:45.059> encrypt<01:19:45.360> the<01:19:45.599> JSON<01:19:45.960> file<01:19:46.230> with<01:19:47.659> public 01:19:48.649 --> 01:19:48.659 align:start position:0% you encrypt the JSON file with public 01:19:48.659 --> 01:19:51.439 align:start position:0% you encrypt the JSON file with public key<01:19:48.840> that<01:19:48.869> you<01:19:49.250> submit<01:19:50.250> so<01:19:50.940> it's<01:19:51.059> a<01:19:51.179> very 01:19:51.439 --> 01:19:51.449 align:start position:0% key that you submit so it's a very 01:19:51.449 --> 01:19:53.250 align:start position:0% key that you submit so it's a very simple<01:19:51.780> Python<01:19:52.380> public 01:19:53.250 --> 01:19:53.260 align:start position:0% simple Python public 01:19:53.260 --> 01:19:56.500 align:start position:0% simple Python public actually<01:19:54.260> guys<01:19:55.130> use<01:19:55.430> for<01:19:55.460> the<01:19:55.880> steps<01:19:56.180> that<01:19:56.390> you 01:19:56.500 --> 01:19:56.510 align:start position:0% actually guys use for the steps that you 01:19:56.510 --> 01:20:01.870 align:start position:0% actually guys use for the steps that you need<01:19:56.540> to<01:19:56.750> create<01:19:57.850> read<01:19:58.850> encrypted<01:19:59.810> signed<01:20:00.880> hot 01:20:01.870 --> 01:20:01.880 align:start position:0% need to create read encrypted signed hot 01:20:01.880 --> 01:20:08.439 align:start position:0% need to create read encrypted signed hot message<01:20:02.780> that<01:20:06.340> service<01:20:07.340> will<01:20:07.610> accept<01:20:08.090> and 01:20:08.439 --> 01:20:08.449 align:start position:0% message that service will accept and 01:20:08.449 --> 01:20:12.670 align:start position:0% message that service will accept and process<01:20:09.550> and<01:20:10.550> yes<01:20:10.989> amazing<01:20:11.989> thing<01:20:12.170> is<01:20:12.380> it 01:20:12.670 --> 01:20:12.680 align:start position:0% process and yes amazing thing is it 01:20:12.680 --> 01:20:15.880 align:start position:0% process and yes amazing thing is it works<01:20:12.890> and<01:20:13.160> I<01:20:13.910> invite<01:20:14.239> you<01:20:14.480> to<01:20:14.890> experiment 01:20:15.880 --> 01:20:15.890 align:start position:0% works and I invite you to experiment 01:20:15.890 --> 01:20:16.600 align:start position:0% works and I invite you to experiment like<01:20:16.340> this 01:20:16.600 --> 01:20:16.610 align:start position:0% like this 01:20:16.610 --> 01:20:23.530 align:start position:0% like this thank<01:20:17.150> you 01:20:23.530 --> 01:20:23.540 align:start position:0% 01:20:23.540 --> 01:20:25.689 align:start position:0% second<01:20:24.170> use<01:20:24.290> case<01:20:24.320> we'll<01:20:24.710> talk<01:20:24.830> about<01:20:24.890> this<01:20:25.310> at 01:20:25.689 --> 01:20:25.699 align:start position:0% second use case we'll talk about this at 01:20:25.699 --> 01:20:28.090 align:start position:0% second use case we'll talk about this at the<01:20:25.820> story<01:20:26.180> comes<01:20:26.510> from<01:20:26.570> I<01:20:27.110> do<01:20:27.590> it<01:20:27.739> from 01:20:28.090 --> 01:20:28.100 align:start position:0% the story comes from I do it from 01:20:28.100 --> 01:20:32.110 align:start position:0% the story comes from I do it from changing<01:20:29.920> alright<01:20:30.920> hello<01:20:31.460> everyone<01:20:31.699> thank 01:20:32.110 --> 01:20:32.120 align:start position:0% changing alright hello everyone thank 01:20:32.120 --> 01:20:34.360 align:start position:0% changing alright hello everyone thank you<01:20:32.210> very<01:20:32.360> much<01:20:32.600> so<01:20:33.440> you<01:20:33.500> have<01:20:33.650> you<01:20:33.800> an<01:20:33.920> even 01:20:34.360 --> 01:20:34.370 align:start position:0% you very much so you have you an even 01:20:34.370 --> 01:20:36.520 align:start position:0% you very much so you have you an even from<01:20:34.670> France<01:20:35.120> probably<01:20:36.050> notice<01:20:36.350> from<01:20:36.469> my 01:20:36.520 --> 01:20:36.530 align:start position:0% from France probably notice from my 01:20:36.530 --> 01:20:39.400 align:start position:0% from France probably notice from my accent<01:20:37.420> so<01:20:38.420> today<01:20:38.780> I<01:20:38.810> would<01:20:38.960> like<01:20:39.080> to<01:20:39.230> talk 01:20:39.400 --> 01:20:39.410 align:start position:0% accent so today I would like to talk 01:20:39.410 --> 01:20:42.459 align:start position:0% accent so today I would like to talk about<01:20:39.710> how<01:20:40.250> Jenny<01:20:40.640> can<01:20:41.000> connect<01:20:41.390> the<01:20:41.660> TCF<01:20:42.140> to 01:20:42.459 --> 01:20:42.469 align:start position:0% about how Jenny can connect the TCF to 01:20:42.469 --> 01:20:46.900 align:start position:0% about how Jenny can connect the TCF to revert<01:20:43.010> beta<01:20:43.780> so<01:20:44.980> when<01:20:45.980> when<01:20:46.520> you<01:20:46.580> started 01:20:46.900 --> 01:20:46.910 align:start position:0% revert beta so when when you started 01:20:46.910 --> 01:20:48.280 align:start position:0% revert beta so when when you started working<01:20:47.120> on<01:20:47.210> training<01:20:47.480> basically<01:20:47.900> we're<01:20:48.080> not 01:20:48.280 --> 01:20:48.290 align:start position:0% working on training basically we're not 01:20:48.290 --> 01:20:51.160 align:start position:0% working on training basically we're not super<01:20:48.530> so<01:20:48.739> it<01:20:48.800> was<01:20:49.219> how<01:20:49.580> we<01:20:49.610> breach<01:20:50.170> fabric 01:20:51.160 --> 01:20:51.170 align:start position:0% super so it was how we breach fabric 01:20:51.170 --> 01:20:53.290 align:start position:0% super so it was how we breach fabric block<01:20:51.380> chains<01:20:51.620> to<01:20:52.070> real-world<01:20:52.340> data<01:20:52.670> because 01:20:53.290 --> 01:20:53.300 align:start position:0% block chains to real-world data because 01:20:53.300 --> 01:20:55.990 align:start position:0% block chains to real-world data because after<01:20:53.719> all<01:20:53.750> a<01:20:54.050> big<01:20:54.410> block<01:20:54.650> chain<01:20:55.000> result 01:20:55.990 --> 01:20:56.000 align:start position:0% after all a big block chain result 01:20:56.000 --> 01:20:58.750 align:start position:0% after all a big block chain result market<01:20:56.750> data<01:20:56.960> Insurance<01:20:57.770> data<01:20:57.980> I<01:20:58.430> would've 01:20:58.750 --> 01:20:58.760 align:start position:0% market data Insurance data I would've 01:20:58.760 --> 01:21:00.910 align:start position:0% market data Insurance data I would've ended<01:20:58.880> up<01:20:59.150> as<01:20:59.900> in<01:21:00.080> favor<01:21:00.260> of<01:21:00.410> the<01:21:00.469> first<01:21:00.739> cases 01:21:00.910 --> 01:21:00.920 align:start position:0% ended up as in favor of the first cases 01:21:00.920 --> 01:21:02.920 align:start position:0% ended up as in favor of the first cases right<01:21:01.370> and<01:21:01.699> we<01:21:01.820> feel<01:21:02.030> it's<01:21:02.150> the<01:21:02.239> same<01:21:02.480> for<01:21:02.780> it 01:21:02.920 --> 01:21:02.930 align:start position:0% right and we feel it's the same for it 01:21:02.930 --> 01:21:04.000 align:start position:0% right and we feel it's the same for it is<01:21:03.110> yet<01:21:03.320> so 01:21:04.000 --> 01:21:04.010 align:start position:0% is yet so 01:21:04.010 --> 01:21:06.760 align:start position:0% is yet so laticia<01:21:04.880> provides<01:21:05.239> a<01:21:05.330> great<01:21:05.510> framework<01:21:05.810> to 01:21:06.760 --> 01:21:06.770 align:start position:0% laticia provides a great framework to 01:21:06.770 --> 01:21:09.880 align:start position:0% laticia provides a great framework to scale<01:21:07.160> and<01:21:07.510> compute<01:21:08.510> smart<01:21:09.020> and<01:21:09.170> watts<01:21:09.410> in<01:21:09.770> a 01:21:09.880 --> 01:21:09.890 align:start position:0% scale and compute smart and watts in a 01:21:09.890 --> 01:21:10.660 align:start position:0% scale and compute smart and watts in a private<01:21:10.280> matter 01:21:10.660 --> 01:21:10.670 align:start position:0% private matter 01:21:10.670 --> 01:21:14.800 align:start position:0% private matter however<01:21:11.600> how<01:21:12.170> do<01:21:12.230> we<01:21:12.500> provide<01:21:13.130> this<01:21:13.969> hybrid<01:21:14.660> or 01:21:14.800 --> 01:21:14.810 align:start position:0% however how do we provide this hybrid or 01:21:14.810 --> 01:21:17.800 align:start position:0% however how do we provide this hybrid or even<01:21:15.170> with<01:21:15.920> data<01:21:16.489> right<01:21:17.060> and<01:21:17.090> how<01:21:17.390> can<01:21:17.449> we<01:21:17.630> make 01:21:17.800 --> 01:21:17.810 align:start position:0% even with data right and how can we make 01:21:17.810 --> 01:21:20.680 align:start position:0% even with data right and how can we make sure<01:21:18.050> that<01:21:18.260> this<01:21:18.380> data<01:21:18.620> is<01:21:19.040> as<01:21:19.730> accurate<01:21:20.449> and 01:21:20.680 --> 01:21:20.690 align:start position:0% sure that this data is as accurate and 01:21:20.690 --> 01:21:22.420 align:start position:0% sure that this data is as accurate and secure<01:21:21.020> as<01:21:21.680> possible 01:21:22.420 --> 01:21:22.430 align:start position:0% secure as possible 01:21:22.430 --> 01:21:27.589 align:start position:0% secure as possible because 01:21:27.589 --> 01:21:27.599 align:start position:0% 01:21:27.599 --> 01:21:30.229 align:start position:0% all<01:21:28.139> right<01:21:28.260> yeah<01:21:28.889> so<01:21:29.190> current<01:21:29.639> visa<01:21:29.790> program 01:21:30.229 --> 01:21:30.239 align:start position:0% all right yeah so current visa program 01:21:30.239 --> 01:21:33.260 align:start position:0% all right yeah so current visa program is<01:21:30.449> a<01:21:30.840> furniture<01:21:31.619> Avedon<01:21:32.369> doesn't<01:21:33.119> have 01:21:33.260 --> 01:21:33.270 align:start position:0% is a furniture Avedon doesn't have 01:21:33.270 --> 01:21:36.439 align:start position:0% is a furniture Avedon doesn't have access<01:21:33.480> or<01:21:34.139> safe<01:21:34.710> access<01:21:34.920> to<01:21:35.280> data<01:21:35.579> inputs<01:21:36.090> so 01:21:36.439 --> 01:21:36.449 align:start position:0% access or safe access to data inputs so 01:21:36.449 --> 01:21:38.060 align:start position:0% access or safe access to data inputs so we<01:21:36.540> have<01:21:36.659> this<01:21:36.780> great<01:21:36.960> framework<01:21:37.260> which 01:21:38.060 --> 01:21:38.070 align:start position:0% we have this great framework which 01:21:38.070 --> 01:21:40.780 align:start position:0% we have this great framework which cannot<01:21:38.369> access<01:21:38.760> real<01:21:39.090> world<01:21:39.329> data<01:21:39.690> right<01:21:40.380> and 01:21:40.780 --> 01:21:40.790 align:start position:0% cannot access real world data right and 01:21:40.790 --> 01:21:42.919 align:start position:0% cannot access real world data right and all<01:21:41.790> of<01:21:41.849> the<01:21:42.119> great<01:21:42.210> use<01:21:42.480> cases 01:21:42.919 --> 01:21:42.929 align:start position:0% all of the great use cases 01:21:42.929 --> 01:21:47.890 align:start position:0% all of the great use cases necesita<01:21:43.710> require<01:21:44.810> real<01:21:45.810> world<01:21:46.020> of<01:21:46.380> animals 01:21:47.890 --> 01:21:47.900 align:start position:0% necesita require real world of animals 01:21:47.900 --> 01:21:51.050 align:start position:0% necesita require real world of animals basically<01:21:48.900> what<01:21:49.380> you<01:21:49.469> want<01:21:49.590> to<01:21:49.679> do<01:21:49.860> is<01:21:50.159> get 01:21:51.050 --> 01:21:51.060 align:start position:0% basically what you want to do is get 01:21:51.060 --> 01:21:54.169 align:start position:0% basically what you want to do is get access<01:21:51.770> him<01:21:52.770> access<01:21:53.070> to<01:21:53.130> sniper<01:21:53.520> injure<01:21:53.909> other 01:21:54.169 --> 01:21:54.179 align:start position:0% access him access to sniper injure other 01:21:54.179 --> 01:21:56.930 align:start position:0% access him access to sniper injure other on<01:21:54.389> to<01:21:54.750> payment<01:21:55.500> methods<01:21:55.829> such<01:21:56.250> as<01:21:56.280> paper 01:21:56.930 --> 01:21:56.940 align:start position:0% on to payment methods such as paper 01:21:56.940 --> 01:21:59.359 align:start position:0% on to payment methods such as paper Swift<01:21:57.869> where<01:21:58.260> basically<01:21:59.010> if<01:21:59.159> you<01:21:59.280> were<01:21:59.340> to 01:21:59.359 --> 01:21:59.369 align:start position:0% Swift where basically if you were to 01:21:59.369 --> 01:22:01.550 align:start position:0% Swift where basically if you were to compute<01:21:59.760> a<01:22:00.060> smart<01:22:00.360> contract<01:22:00.750> into<01:22:01.230> TCL 01:22:01.550 --> 01:22:01.560 align:start position:0% compute a smart contract into TCL 01:22:01.560 --> 01:22:04.729 align:start position:0% compute a smart contract into TCL framework<01:22:02.070> you<01:22:02.340> put<01:22:02.760> trigger<01:22:03.060> X<01:22:03.869> on<01:22:04.110> actions 01:22:04.729 --> 01:22:04.739 align:start position:0% framework you put trigger X on actions 01:22:04.739 --> 01:22:09.129 align:start position:0% framework you put trigger X on actions right<01:22:05.130> we<01:22:05.880> also<01:22:06.030> want<01:22:06.329> to<01:22:06.360> be<01:22:06.540> able<01:22:06.630> to<01:22:06.869> allow 01:22:09.129 --> 01:22:09.139 align:start position:0% right we also want to be able to allow 01:22:09.139 --> 01:22:11.680 align:start position:0% right we also want to be able to allow 12:03 01:22:11.680 --> 01:22:11.690 align:start position:0% 12:03 01:22:11.690 --> 01:22:15.500 align:start position:0% 12:03 my<01:22:12.690> size<01:22:12.900> are<01:22:13.079> a<01:22:13.110> bit<01:22:13.320> done<01:22:13.820> yet<01:22:14.820> basically<01:22:15.179> to 01:22:15.500 --> 01:22:15.510 align:start position:0% my size are a bit done yet basically to 01:22:15.510 --> 01:22:17.810 align:start position:0% my size are a bit done yet basically to expiry<01:22:16.110> season<01:22:16.500> so<01:22:16.619> we<01:22:16.679> know<01:22:16.800> to<01:22:16.860> allow<01:22:17.190> the 01:22:17.810 --> 01:22:17.820 align:start position:0% expiry season so we know to allow the 01:22:17.820 --> 01:22:20.620 align:start position:0% expiry season so we know to allow the TCM<01:22:18.210> to<01:22:18.329> get<01:22:18.570> access<01:22:18.780> to<01:22:19.139> real<01:22:19.530> birth<01:22:19.710> data<01:22:19.920> so 01:22:20.620 --> 01:22:20.630 align:start position:0% TCM to get access to real birth data so 01:22:20.630 --> 01:22:23.689 align:start position:0% TCM to get access to real birth data so market<01:22:21.630> data<01:22:21.840> from<01:22:22.290> Bloomberg<01:22:22.739> from<01:22:23.159> Reuters 01:22:23.689 --> 01:22:23.699 align:start position:0% market data from Bloomberg from Reuters 01:22:23.699 --> 01:22:25.879 align:start position:0% market data from Bloomberg from Reuters your<01:22:24.389> so<01:22:24.599> on<01:22:24.750> to<01:22:24.900> be<01:22:25.020> able<01:22:25.139> to<01:22:25.619> trigger 01:22:25.879 --> 01:22:25.889 align:start position:0% your so on to be able to trigger 01:22:25.889 --> 01:22:28.609 align:start position:0% your so on to be able to trigger external<01:22:26.670> payments<01:22:27.119> with<01:22:27.810> the<01:22:27.840> DCF<01:22:28.349> and 01:22:28.609 --> 01:22:28.619 align:start position:0% external payments with the DCF and 01:22:28.619 --> 01:22:31.370 align:start position:0% external payments with the DCF and finally<01:22:29.520> the<01:22:29.760> third<01:22:30.030> use<01:22:30.239> case<01:22:30.320> is<01:22:31.320> to 01:22:31.370 --> 01:22:31.380 align:start position:0% finally the third use case is to 01:22:31.380 --> 01:22:35.169 align:start position:0% finally the third use case is to basically<01:22:31.829> allow<01:22:32.219> ctcf<01:22:32.909> to<01:22:33.329> gain<01:22:33.480> access<01:22:33.840> to 01:22:35.169 --> 01:22:35.179 align:start position:0% basically allow ctcf to gain access to 01:22:35.179 --> 01:22:37.850 align:start position:0% basically allow ctcf to gain access to other<01:22:36.179> reductions<01:22:36.599> so<01:22:36.960> basically<01:22:37.409> let's<01:22:37.739> say 01:22:37.850 --> 01:22:37.860 align:start position:0% other reductions so basically let's say 01:22:37.860 --> 01:22:40.069 align:start position:0% other reductions so basically let's say you<01:22:37.980> were<01:22:38.130> to<01:22:38.340> compute<01:22:39.060> a<01:22:39.360> smart<01:22:39.690> contract 01:22:40.069 --> 01:22:40.079 align:start position:0% you were to compute a smart contract 01:22:40.079 --> 01:22:41.959 align:start position:0% you were to compute a smart contract inside<01:22:40.530> this<01:22:40.800> yet<01:22:41.070> you<01:22:41.460> could<01:22:41.610> trigger<01:22:41.820> a 01:22:41.959 --> 01:22:41.969 align:start position:0% inside this yet you could trigger a 01:22:41.969 --> 01:22:44.810 align:start position:0% inside this yet you could trigger a Bitcoin<01:22:42.570> payment<01:22:42.989> or<01:22:43.170> lithium<01:22:44.010> transaction 01:22:44.810 --> 01:22:44.820 align:start position:0% Bitcoin payment or lithium transaction 01:22:44.820 --> 01:22:47.660 align:start position:0% Bitcoin payment or lithium transaction or<01:22:44.969> even<01:22:45.449> integers<01:22:45.780> might<01:22:46.079> not<01:22:46.230> run<01:22:46.440> so<01:22:46.889> those 01:22:47.660 --> 01:22:47.670 align:start position:0% or even integers might not run so those 01:22:47.670 --> 01:22:49.640 align:start position:0% or even integers might not run so those are<01:22:47.820> all<01:22:48.119> great<01:22:48.329> use<01:22:48.599> cases<01:22:48.840> is<01:22:49.199> that<01:22:49.469> you've 01:22:49.640 --> 01:22:49.650 align:start position:0% are all great use cases is that you've 01:22:49.650 --> 01:22:53.919 align:start position:0% are all great use cases is that you've been<01:22:49.829> working<01:22:49.949> on<01:22:50.520> implementing<01:22:51.360> a<01:22:51.570> city 01:22:53.919 --> 01:22:53.929 align:start position:0% been working on implementing a city 01:22:53.929 --> 01:22:57.319 align:start position:0% been working on implementing a city alright<01:22:54.929> so<01:22:55.639> currently<01:22:56.639> were<01:22:57.000> some<01:22:57.210> of 01:22:57.319 --> 01:22:57.329 align:start position:0% alright so currently were some of 01:22:57.329 --> 01:23:01.129 align:start position:0% alright so currently were some of guarantee<01:22:58.139> and<01:22:58.349> -<01:22:58.710> and<01:22:58.889> reliability<01:22:59.610> so<01:23:00.510> the 01:23:01.129 --> 01:23:01.139 align:start position:0% guarantee and - and reliability so the 01:23:01.139 --> 01:23:04.189 align:start position:0% guarantee and - and reliability so the only<01:23:01.380> heidi<01:23:01.590> is<01:23:02.010> as<01:23:02.369> we<01:23:03.060> use<01:23:03.210> public<01:23:03.750> auctions 01:23:04.189 --> 01:23:04.199 align:start position:0% only heidi is as we use public auctions 01:23:04.199 --> 01:23:07.280 align:start position:0% only heidi is as we use public auctions in<01:23:04.619> order<01:23:05.010> to<01:23:05.429> be<01:23:05.550> tamper<01:23:06.030> proof<01:23:06.239> transparent 01:23:07.280 --> 01:23:07.290 align:start position:0% in order to be tamper proof transparent 01:23:07.290 --> 01:23:10.069 align:start position:0% in order to be tamper proof transparent rights<01:23:07.710> use<01:23:08.219> the<01:23:08.400> GCS<01:23:08.849> in<01:23:08.969> order<01:23:09.210> to<01:23:09.389> scale<01:23:09.690> and 01:23:10.069 --> 01:23:10.079 align:start position:0% rights use the GCS in order to scale and 01:23:10.079 --> 01:23:13.609 align:start position:0% rights use the GCS in order to scale and to<01:23:10.980> learn<01:23:11.730> privacy<01:23:12.540> whenever<01:23:13.079> we<01:23:13.260> compute 01:23:13.609 --> 01:23:13.619 align:start position:0% to learn privacy whenever we compute 01:23:13.619 --> 01:23:15.830 align:start position:0% to learn privacy whenever we compute smart<01:23:13.860> contracts<01:23:14.250> and<01:23:14.489> we<01:23:15.270> also<01:23:15.389> want<01:23:15.630> to<01:23:15.659> make 01:23:15.830 --> 01:23:15.840 align:start position:0% smart contracts and we also want to make 01:23:15.840 --> 01:23:17.629 align:start position:0% smart contracts and we also want to make sure<01:23:15.869> that<01:23:16.170> the<01:23:16.290> data<01:23:16.469> is<01:23:16.829> as<01:23:17.040> being 01:23:17.629 --> 01:23:17.639 align:start position:0% sure that the data is as being 01:23:17.639 --> 01:23:20.080 align:start position:0% sure that the data is as being -<01:23:17.760> the<01:23:17.880> system<01:23:18.300> is<01:23:18.540> as<01:23:19.260> secure<01:23:19.619> as<01:23:19.800> possible 01:23:20.080 --> 01:23:20.090 align:start position:0% - the system is as secure as possible 01:23:20.090 --> 01:23:22.669 align:start position:0% - the system is as secure as possible after<01:23:21.090> all<01:23:21.210> if<01:23:21.510> we're<01:23:21.780> to<01:23:21.929> have<01:23:21.989> a<01:23:22.050> system 01:23:22.669 --> 01:23:22.679 align:start position:0% after all if we're to have a system 01:23:22.679 --> 01:23:24.890 align:start position:0% after all if we're to have a system which<01:23:23.219> is<01:23:23.250> processing<01:23:24.000> real<01:23:24.420> world<01:23:24.659> data 01:23:24.890 --> 01:23:24.900 align:start position:0% which is processing real world data 01:23:24.900 --> 01:23:27.439 align:start position:0% which is processing real world data inside<01:23:25.619> an<01:23:25.739> unclaimed<01:23:26.100> but<01:23:26.850> you're<01:23:27.090> not<01:23:27.239> sure 01:23:27.439 --> 01:23:27.449 align:start position:0% inside an unclaimed but you're not sure 01:23:27.449 --> 01:23:29.810 align:start position:0% inside an unclaimed but you're not sure about<01:23:27.570> is<01:23:27.869> data<01:23:28.080> is<01:23:28.889> annual<01:23:29.219> run<01:23:29.400> into<01:23:29.670> each 01:23:29.810 --> 01:23:29.820 align:start position:0% about is data is annual run into each 01:23:29.820 --> 01:23:32.629 align:start position:0% about is data is annual run into each issue<01:23:30.060> right<01:23:30.570> why<01:23:30.929> do<01:23:30.989> you<01:23:31.139> insist<01:23:31.639> super 01:23:32.629 --> 01:23:32.639 align:start position:0% issue right why do you insist super 01:23:32.639 --> 01:23:34.939 align:start position:0% issue right why do you insist super secure<01:23:32.850> system<01:23:33.480> which<01:23:34.230> is<01:23:34.380> being<01:23:34.560> triggered 01:23:34.939 --> 01:23:34.949 align:start position:0% secure system which is being triggered 01:23:34.949 --> 01:23:37.970 align:start position:0% secure system which is being triggered by<01:23:35.130> super<01:23:35.880> secure<01:23:36.389> data<01:23:36.810> just<01:23:37.530> a<01:23:37.619> program 01:23:37.970 --> 01:23:37.980 align:start position:0% by super secure data just a program 01:23:37.980 --> 01:23:40.520 align:start position:0% by super secure data just a program right<01:23:38.250> so<01:23:38.790> what<01:23:39.480> you<01:23:39.600> be<01:23:39.960> working<01:23:40.199> on<01:23:40.469> a 01:23:40.520 --> 01:23:40.530 align:start position:0% right so what you be working on a 01:23:40.530 --> 01:23:43.399 align:start position:0% right so what you be working on a chaining<01:23:41.010> is<01:23:41.510> basically<01:23:42.510> being<01:23:42.780> able<01:23:42.989> to<01:23:43.199> add 01:23:43.399 --> 01:23:43.409 align:start position:0% chaining is basically being able to add 01:23:43.409 --> 01:23:45.770 align:start position:0% chaining is basically being able to add multiple<01:23:43.949> sources<01:23:44.610> which<01:23:45.090> are<01:23:45.239> fetching<01:23:45.449> data 01:23:45.770 --> 01:23:45.780 align:start position:0% multiple sources which are fetching data 01:23:45.780 --> 01:23:49.220 align:start position:0% multiple sources which are fetching data from<01:23:46.350> multiple<01:23:46.440> data<01:23:47.369> providers<01:23:48.030> in<01:23:48.750> order<01:23:48.900> to 01:23:49.220 --> 01:23:49.230 align:start position:0% from multiple data providers in order to 01:23:49.230 --> 01:23:51.379 align:start position:0% from multiple data providers in order to make<01:23:49.380> sure<01:23:49.409> through<01:23:50.100> redundancy<01:23:50.909> that<01:23:51.119> the 01:23:51.379 --> 01:23:51.389 align:start position:0% make sure through redundancy that the 01:23:51.389 --> 01:23:53.540 align:start position:0% make sure through redundancy that the data<01:23:51.570> you<01:23:51.690> get<01:23:51.989> into<01:23:52.679> your<01:23:52.889> smart<01:23:53.159> inference 01:23:53.540 --> 01:23:53.550 align:start position:0% data you get into your smart inference 01:23:53.550 --> 01:23:56.720 align:start position:0% data you get into your smart inference is<01:23:53.790> as<01:23:54.239> secure<01:23:54.570> as<01:23:54.869> possible<01:23:55.170> and<01:23:55.920> we<01:23:56.489> believe 01:23:56.720 --> 01:23:56.730 align:start position:0% is as secure as possible and we believe 01:23:56.730 --> 01:23:59.600 align:start position:0% is as secure as possible and we believe it's<01:23:56.880> a<01:23:57.000> huge<01:23:57.210> importance<01:23:58.080> for<01:23:58.440> the<01:23:58.590> TCF<01:23:59.010> to<01:23:59.489> in 01:23:59.600 --> 01:23:59.610 align:start position:0% it's a huge importance for the TCF to in 01:23:59.610 --> 01:24:03.200 align:start position:0% it's a huge importance for the TCF to in access<01:23:59.969> to<01:24:00.210> it<01:24:00.929> data<01:24:01.340> which<01:24:02.340> offers 01:24:03.200 --> 01:24:03.210 align:start position:0% access to it data which offers 01:24:03.210 --> 01:24:05.629 align:start position:0% access to it data which offers redundancy<01:24:04.020> and<01:24:04.230> which<01:24:04.739> offers<01:24:05.130> basically 01:24:05.629 --> 01:24:05.639 align:start position:0% redundancy and which offers basically 01:24:05.639 --> 01:24:08.419 align:start position:0% redundancy and which offers basically incentives<01:24:06.150> where<01:24:06.600> people<01:24:07.310> will<01:24:08.310> be 01:24:08.419 --> 01:24:08.429 align:start position:0% incentives where people will be 01:24:08.429 --> 01:24:11.090 align:start position:0% incentives where people will be incentivized<01:24:09.000> to<01:24:09.119> provide<01:24:09.800> to<01:24:10.800> the<01:24:10.920> right 01:24:11.090 --> 01:24:11.100 align:start position:0% incentivized to provide to the right 01:24:11.100 --> 01:24:14.180 align:start position:0% incentivized to provide to the right data<01:24:11.730> points<01:24:12.210> without<01:24:12.949> without<01:24:13.949> being 01:24:14.180 --> 01:24:14.190 align:start position:0% data points without without being 01:24:14.190 --> 01:24:15.590 align:start position:0% data points without without being malicious<01:24:14.460> whenever<01:24:14.969> Center<01:24:15.179> giving<01:24:15.480> up 01:24:15.590 --> 01:24:15.600 align:start position:0% malicious whenever Center giving up 01:24:15.600 --> 01:24:19.479 align:start position:0% malicious whenever Center giving up system<01:24:15.989> top<01:24:16.199> right<01:24:16.670> so<01:24:17.670> next<01:24:17.820> time<01:24:18.090> so 01:24:19.479 --> 01:24:19.489 align:start position:0% system top right so next time so 01:24:19.489 --> 01:24:21.410 align:start position:0% system top right so next time so basically<01:24:20.489> was<01:24:20.670> not<01:24:20.699> to<01:24:20.969> apply<01:24:21.090> to<01:24:21.179> this 01:24:21.410 --> 01:24:21.420 align:start position:0% basically was not to apply to this 01:24:21.420 --> 01:24:23.899 align:start position:0% basically was not to apply to this architecture<01:24:22.050> you<01:24:22.679> have<01:24:22.710> a<01:24:23.100> great<01:24:23.580> for<01:24:23.820> the 01:24:23.899 --> 01:24:23.909 align:start position:0% architecture you have a great for the 01:24:23.909 --> 01:24:27.850 align:start position:0% architecture you have a great for the system<01:24:24.300> so<01:24:24.570> currently<01:24:25.699> if<01:24:26.699> you<01:24:26.850> carry<01:24:27.090> on<01:24:27.179> and 01:24:27.850 --> 01:24:27.860 align:start position:0% system so currently if you carry on and 01:24:27.860 --> 01:24:30.649 align:start position:0% system so currently if you carry on and hybrid<01:24:28.860> of<01:24:29.190> another<01:24:29.489> right<01:24:29.699> and<01:24:30.030> we<01:24:30.540> don't 01:24:30.649 --> 01:24:30.659 align:start position:0% hybrid of another right and we don't 01:24:30.659 --> 01:24:33.169 align:start position:0% hybrid of another right and we don't want<01:24:30.869> this<01:24:31.050> for<01:24:31.710> existin<01:24:32.250> to<01:24:32.550> be<01:24:32.670> triggered<01:24:32.940> by 01:24:33.169 --> 01:24:33.179 align:start position:0% want this for existin to be triggered by 01:24:33.179 --> 01:24:36.169 align:start position:0% want this for existin to be triggered by one<01:24:33.480> surprise<01:24:33.989> or<01:24:34.320> occur<01:24:34.469> because<01:24:35.159> if<01:24:35.909> you 01:24:36.169 --> 01:24:36.179 align:start position:0% one surprise or occur because if you 01:24:36.179 --> 01:24:38.180 align:start position:0% one surprise or occur because if you have<01:24:36.270> a<01:24:36.330> super<01:24:36.480> reliable<01:24:36.869> system<01:24:37.530> he<01:24:37.920> doesn't 01:24:38.180 --> 01:24:38.190 align:start position:0% have a super reliable system he doesn't 01:24:38.190 --> 01:24:40.250 align:start position:0% have a super reliable system he doesn't make<01:24:38.340> sense<01:24:38.639> to<01:24:38.909> have<01:24:39.000> been<01:24:39.179> triggered<01:24:39.719> by<01:24:39.960> one 01:24:40.250 --> 01:24:40.260 align:start position:0% make sense to have been triggered by one 01:24:40.260 --> 01:24:43.040 align:start position:0% make sense to have been triggered by one single<01:24:40.980> centralized<01:24:41.940> or<01:24:42.210> occurred<01:24:42.480> that's 01:24:43.040 --> 01:24:43.050 align:start position:0% single centralized or occurred that's 01:24:43.050 --> 01:24:44.419 align:start position:0% single centralized or occurred that's what<01:24:43.199> you<01:24:43.350> to<01:24:43.530> avoid<01:24:43.770> we<01:24:44.100> want<01:24:44.280> to<01:24:44.369> add 01:24:44.419 --> 01:24:44.429 align:start position:0% what you to avoid we want to add 01:24:44.429 --> 01:24:47.149 align:start position:0% what you to avoid we want to add redundancy<01:24:45.030> also<01:24:45.960> forever<01:24:46.199> there<01:24:46.619> but<01:24:47.010> you 01:24:47.149 --> 01:24:47.159 align:start position:0% redundancy also forever there but you 01:24:47.159 --> 01:24:49.760 align:start position:0% redundancy also forever there but you variant<01:24:47.639> multiple<01:24:48.179> partners<01:24:48.690> providing<01:24:49.619> data 01:24:49.760 --> 01:24:49.770 align:start position:0% variant multiple partners providing data 01:24:49.770 --> 01:24:53.510 align:start position:0% variant multiple partners providing data from<01:24:50.369> multiple<01:24:50.460> data<01:24:51.210> providers<01:24:51.960> right<01:24:52.520> so 01:24:53.510 --> 01:24:53.520 align:start position:0% from multiple data providers right so 01:24:53.520 --> 01:24:56.240 align:start position:0% from multiple data providers right so next<01:24:53.969> one<01:24:54.239> and<01:24:54.800> yes<01:24:55.800> that's<01:24:55.949> what<01:24:56.130> we 01:24:56.240 --> 01:24:56.250 align:start position:0% next one and yes that's what we 01:24:56.250 --> 01:24:58.760 align:start position:0% next one and yes that's what we implemented<01:24:56.730> basically<01:24:57.210> it's<01:24:57.619> working<01:24:58.619> and 01:24:58.760 --> 01:24:58.770 align:start position:0% implemented basically it's working and 01:24:58.770 --> 01:25:01.100 align:start position:0% implemented basically it's working and we<01:24:59.340> are<01:24:59.400> going<01:24:59.550> to<01:24:59.790> commit<01:25:00.179> it<01:25:00.330> to<01:25:00.630> the<01:25:00.810> high 01:25:01.100 --> 01:25:01.110 align:start position:0% we are going to commit it to the high 01:25:01.110 --> 01:25:04.459 align:start position:0% we are going to commit it to the high pressure<01:25:01.380> column<01:25:01.670> it's<01:25:02.670> a<01:25:02.909> waiting<01:25:03.179> for<01:25:03.540> to 01:25:04.459 --> 01:25:04.469 align:start position:0% pressure column it's a waiting for to 01:25:04.469 --> 01:25:07.580 align:start position:0% pressure column it's a waiting for to provide<01:25:04.830> data<01:25:05.070> to<01:25:05.460> the<01:25:05.699> GCF<01:25:06.230> using<01:25:07.230> change 01:25:07.580 --> 01:25:07.590 align:start position:0% provide data to the GCF using change 01:25:07.590 --> 01:25:09.080 align:start position:0% provide data to the GCF using change nodes<01:25:07.949> and<01:25:08.130> I'm<01:25:08.460> going<01:25:08.639> to<01:25:08.760> run<01:25:08.909> you<01:25:08.940> through 01:25:09.080 --> 01:25:09.090 align:start position:0% nodes and I'm going to run you through 01:25:09.090 --> 01:25:11.060 align:start position:0% nodes and I'm going to run you through the<01:25:09.420> process<01:25:09.630> how<01:25:10.139> it<01:25:10.170> works<01:25:10.530> exactly 01:25:11.060 --> 01:25:11.070 align:start position:0% the process how it works exactly 01:25:11.070 --> 01:25:13.729 align:start position:0% the process how it works exactly so<01:25:11.940> when<01:25:12.360> the<01:25:12.510> requester<01:25:12.929> contracts<01:25:13.320> which<01:25:13.560> is 01:25:13.729 --> 01:25:13.739 align:start position:0% so when the requester contracts which is 01:25:13.739 --> 01:25:16.760 align:start position:0% so when the requester contracts which is unchanged<01:25:14.280> so<01:25:14.670> it<01:25:14.760> can<01:25:14.940> you<01:25:15.060> hear<01:25:15.389> me<01:25:15.780> on<01:25:15.869> hyper 01:25:16.760 --> 01:25:16.770 align:start position:0% unchanged so it can you hear me on hyper 01:25:16.770 --> 01:25:19.310 align:start position:0% unchanged so it can you hear me on hyper nature<01:25:17.130> and<01:25:17.400> young<01:25:17.520> any<01:25:17.909> production<01:25:18.570> with 01:25:19.310 --> 01:25:19.320 align:start position:0% nature and young any production with 01:25:19.320 --> 01:25:21.890 align:start position:0% nature and young any production with and<01:25:19.620> into<01:25:20.550> into<01:25:20.610> sense<01:25:20.970> the<01:25:21.240> notion<01:25:21.570> request 01:25:21.890 --> 01:25:21.900 align:start position:0% and into into sense the notion request 01:25:21.900 --> 01:25:23.540 align:start position:0% and into into sense the notion request for<01:25:22.110> changing<01:25:22.440> contracts<01:25:22.830> okay 01:25:23.540 --> 01:25:23.550 align:start position:0% for changing contracts okay 01:25:23.550 --> 01:25:26.110 align:start position:0% for changing contracts okay this<01:25:24.150> training<01:25:24.390> contract<01:25:25.170> is<01:25:25.290> going<01:25:25.500> to<01:25:25.620> send 01:25:26.110 --> 01:25:26.120 align:start position:0% this training contract is going to send 01:25:26.120 --> 01:25:28.130 align:start position:0% this training contract is going to send triggered<01:25:27.120> personal<01:25:27.690> notes 01:25:28.130 --> 01:25:28.140 align:start position:0% triggered personal notes 01:25:28.140 --> 01:25:29.980 align:start position:0% triggered personal notes mrs.<01:25:28.470> Channing<01:25:28.710> note<01:25:28.980> is<01:25:29.130> basically<01:25:29.490> run<01:25:29.790> by 01:25:29.980 --> 01:25:29.990 align:start position:0% mrs. Channing note is basically run by 01:25:29.990 --> 01:25:32.090 align:start position:0% mrs. Channing note is basically run by blockchain<01:25:30.990> infrastructure<01:25:31.530> companies 01:25:32.090 --> 01:25:32.100 align:start position:0% blockchain infrastructure companies 01:25:32.100 --> 01:25:35.450 align:start position:0% blockchain infrastructure companies Guarani<01:25:32.850> and<01:25:33.150> etherium<01:25:33.660> or<01:25:34.220> any<01:25:35.220> kind<01:25:35.400> of 01:25:35.450 --> 01:25:35.460 align:start position:0% Guarani and etherium or any kind of 01:25:35.460 --> 01:25:38.090 align:start position:0% Guarani and etherium or any kind of blocks<01:25:35.700> and<01:25:35.850> food<01:25:36.180> production<01:25:36.810> plans<01:25:37.380> and 01:25:38.090 --> 01:25:38.100 align:start position:0% blocks and food production plans and 01:25:38.100 --> 01:25:40.430 align:start position:0% blocks and food production plans and which<01:25:38.730> anecdotes<01:25:39.300> and<01:25:39.480> it's<01:25:40.140> going<01:25:40.320> to 01:25:40.430 --> 01:25:40.440 align:start position:0% which anecdotes and it's going to 01:25:40.440 --> 01:25:42.590 align:start position:0% which anecdotes and it's going to retrieve<01:25:40.830> the<01:25:41.160> external<01:25:41.550> data<01:25:41.700> from<01:25:42.360> an<01:25:42.480> API 01:25:42.590 --> 01:25:42.600 align:start position:0% retrieve the external data from an API 01:25:42.600 --> 01:25:45.350 align:start position:0% retrieve the external data from an API endpoint<01:25:43.100> now<01:25:44.100> is<01:25:44.340> a<01:25:44.550> Cal<01:25:44.760> points<01:25:45.090> would<01:25:45.330> be 01:25:45.350 --> 01:25:45.360 align:start position:0% endpoint now is a Cal points would be 01:25:45.360 --> 01:25:48.410 align:start position:0% endpoint now is a Cal points would be bloomberg<01:25:45.960> rewriters<01:25:46.950> it<01:25:47.580> could<01:25:47.820> be<01:25:47.940> our<01:25:48.180> G 01:25:48.410 --> 01:25:48.420 align:start position:0% bloomberg rewriters it could be our G 01:25:48.420 --> 01:25:50.540 align:start position:0% bloomberg rewriters it could be our G data<01:25:48.570> it<01:25:49.110> could<01:25:49.260> be<01:25:49.350> any<01:25:49.620> kind<01:25:49.830> of<01:25:49.950> data<01:25:50.220> you 01:25:50.540 --> 01:25:50.550 align:start position:0% data it could be any kind of data you 01:25:50.550 --> 01:25:53.840 align:start position:0% data it could be any kind of data you could<01:25:50.790> think<01:25:51.180> of<01:25:51.360> right<01:25:51.770> so<01:25:52.770> watch<01:25:53.490> my<01:25:53.670> weight 01:25:53.840 --> 01:25:53.850 align:start position:0% could think of right so watch my weight 01:25:53.850 --> 01:25:55.820 align:start position:0% could think of right so watch my weight with<01:25:54.060> the<01:25:54.150> data<01:25:54.360> we<01:25:54.690> fit<01:25:54.870> into<01:25:55.170> an<01:25:55.410> adapter 01:25:55.820 --> 01:25:55.830 align:start position:0% with the data we fit into an adapter 01:25:55.830 --> 01:25:57.620 align:start position:0% with the data we fit into an adapter basically<01:25:56.760> this<01:25:56.880> adapter<01:25:57.240> is<01:25:57.270> going<01:25:57.510> to 01:25:57.620 --> 01:25:57.630 align:start position:0% basically this adapter is going to 01:25:57.630 --> 01:26:00.950 align:start position:0% basically this adapter is going to include<01:25:57.930> the<01:25:58.080> data<01:25:58.260> and<01:25:58.710> sends<01:25:59.640> your<01:25:59.760> order<01:26:00.450> to 01:26:00.950 --> 01:26:00.960 align:start position:0% include the data and sends your order to 01:26:00.960 --> 01:26:03.020 align:start position:0% include the data and sends your order to the<01:26:01.080> GCF<01:26:01.500> is<01:26:01.770> your<01:26:02.010> order<01:26:02.280> is<01:26:02.520> basically<01:26:02.850> the 01:26:03.020 --> 01:26:03.030 align:start position:0% the GCF is your order is basically the 01:26:03.030 --> 01:26:05.060 align:start position:0% the GCF is your order is basically the sequence<01:26:03.450> of<01:26:03.750> operation<01:26:04.320> that<01:26:04.470> needs<01:26:04.920> to<01:26:05.040> be 01:26:05.060 --> 01:26:05.070 align:start position:0% sequence of operation that needs to be 01:26:05.070 --> 01:26:08.030 align:start position:0% sequence of operation that needs to be processed<01:26:05.340> inside<01:26:06.090> of<01:26:06.240> the<01:26:06.330> tissue<01:26:06.540> and<01:26:07.040> now 01:26:08.030 --> 01:26:08.040 align:start position:0% processed inside of the tissue and now 01:26:08.040 --> 01:26:09.650 align:start position:0% processed inside of the tissue and now for<01:26:08.280> the<01:26:08.370> most<01:26:08.550> security-conscious<01:26:09.150> people 01:26:09.650 --> 01:26:09.660 align:start position:0% for the most security-conscious people 01:26:09.660 --> 01:26:11.540 align:start position:0% for the most security-conscious people in<01:26:09.900> this<01:26:10.110> room<01:26:10.650> you're<01:26:10.890> probably<01:26:11.070> noticed 01:26:11.540 --> 01:26:11.550 align:start position:0% in this room you're probably noticed 01:26:11.550 --> 01:26:12.860 align:start position:0% in this room you're probably noticed that<01:26:11.730> whenever<01:26:12.150> we<01:26:12.450> were<01:26:12.570> to<01:26:12.630> raise<01:26:12.840> the 01:26:12.860 --> 01:26:12.870 align:start position:0% that whenever we were to raise the 01:26:12.870 --> 01:26:15.770 align:start position:0% that whenever we were to raise the challenge<01:26:13.440> the<01:26:14.190> data<01:26:14.400> and<01:26:14.760> it<01:26:15.420> goes<01:26:15.570> through 01:26:15.770 --> 01:26:15.780 align:start position:0% challenge the data and it goes through 01:26:15.780 --> 01:26:17.570 align:start position:0% challenge the data and it goes through the<01:26:15.900> chaining<01:26:16.170> tops<01:26:16.410> there<01:26:16.770> is<01:26:16.830> a<01:26:16.860> possibility 01:26:17.570 --> 01:26:17.580 align:start position:0% the chaining tops there is a possibility 01:26:17.580 --> 01:26:20.000 align:start position:0% the chaining tops there is a possibility for<01:26:17.730> the<01:26:18.000> oracle<01:26:18.480> to<01:26:19.050> pair<01:26:19.230> up<01:26:19.290> the<01:26:19.410> data<01:26:19.620> right 01:26:20.000 --> 01:26:20.010 align:start position:0% for the oracle to pair up the data right 01:26:20.010 --> 01:26:22.730 align:start position:0% for the oracle to pair up the data right at<01:26:20.250> this<01:26:20.400> point<01:26:20.640> and<01:26:21.170> set<01:26:22.170> where<01:26:22.320> the<01:26:22.440> beauty 01:26:22.730 --> 01:26:22.740 align:start position:0% at this point and set where the beauty 01:26:22.740 --> 01:26:25.880 align:start position:0% at this point and set where the beauty of<01:26:22.770> GCF<01:26:23.250> very<01:26:23.430> comes<01:26:23.700> in<01:26:23.930> let's<01:26:24.930> say<01:26:25.140> I<01:26:25.380> want<01:26:25.860> to 01:26:25.880 --> 01:26:25.890 align:start position:0% of GCF very comes in let's say I want to 01:26:25.890 --> 01:26:28.370 align:start position:0% of GCF very comes in let's say I want to make<01:26:26.040> sure<01:26:26.280> that<01:26:26.550> I<01:26:26.910> want<01:26:27.750> to<01:26:27.810> prove<01:26:28.050> that<01:26:28.110> the 01:26:28.370 --> 01:26:28.380 align:start position:0% make sure that I want to prove that the 01:26:28.380 --> 01:26:30.230 align:start position:0% make sure that I want to prove that the data<01:26:28.560> hasn't<01:26:28.950> been<01:26:29.190> tampered<01:26:29.460> with<01:26:29.730> by<01:26:30.030> search 01:26:30.230 --> 01:26:30.240 align:start position:0% data hasn't been tampered with by search 01:26:30.240 --> 01:26:33.320 align:start position:0% data hasn't been tampered with by search any<01:26:30.510> price<01:26:31.170> you<01:26:31.500> ask<01:26:32.280> so<01:26:32.910> you<01:26:32.970> take<01:26:33.240> that 01:26:33.320 --> 01:26:33.330 align:start position:0% any price you ask so you take that 01:26:33.330 --> 01:26:36.680 align:start position:0% any price you ask so you take that provider<01:26:33.690> to<01:26:34.140> sign<01:26:34.440> this<01:26:34.800> data<01:26:35.430> and<01:26:35.670> then<01:26:36.540> I 01:26:36.680 --> 01:26:36.690 align:start position:0% provider to sign this data and then I 01:26:36.690 --> 01:26:37.400 align:start position:0% provider to sign this data and then I can<01:26:36.840> verify 01:26:37.400 --> 01:26:37.410 align:start position:0% can verify 01:26:37.410 --> 01:26:39.770 align:start position:0% can verify since<01:26:38.160> is<01:26:38.280> that<01:26:38.460> our<01:26:38.610> sons<01:26:38.970> and<01:26:39.240> I<01:26:39.450> can<01:26:39.600> verify 01:26:39.770 --> 01:26:39.780 align:start position:0% since is that our sons and I can verify 01:26:39.780 --> 01:26:42.410 align:start position:0% since is that our sons and I can verify the<01:26:39.990> signature<01:26:40.500> inside<01:26:41.010> of<01:26:41.160> the<01:26:41.280> diskette<01:26:41.700> now 01:26:42.410 --> 01:26:42.420 align:start position:0% the signature inside of the diskette now 01:26:42.420 --> 01:26:46.210 align:start position:0% the signature inside of the diskette now very<01:26:42.930> famous<01:26:43.110> signatures<01:26:43.770> is<01:26:44.370> a<01:26:44.430> very<01:26:44.880> very 01:26:46.210 --> 01:26:46.220 align:start position:0% very famous signatures is a very very 01:26:46.220 --> 01:26:48.230 align:start position:0% very famous signatures is a very very consuming<01:26:47.220> process<01:26:47.670> right<01:26:47.910> it's<01:26:48.090> not 01:26:48.230 --> 01:26:48.240 align:start position:0% consuming process right it's not 01:26:48.240 --> 01:26:49.670 align:start position:0% consuming process right it's not something<01:26:48.540> that<01:26:48.570> you<01:26:48.750> have<01:26:48.810> to<01:26:48.870> do<01:26:49.140> one<01:26:49.380> shell 01:26:49.670 --> 01:26:49.680 align:start position:0% something that you have to do one shell 01:26:49.680 --> 01:26:51.680 align:start position:0% something that you have to do one shell it's<01:26:50.310> extremely<01:26:50.760> computing<01:26:51.270> so<01:26:51.420> if<01:26:51.480> you<01:26:51.630> were 01:26:51.680 --> 01:26:51.690 align:start position:0% it's extremely computing so if you were 01:26:51.690 --> 01:26:55.820 align:start position:0% it's extremely computing so if you were to<01:26:51.900> do<01:26:52.050> it<01:26:52.140> inside<01:26:53.510> contracts<01:26:54.510> on<01:26:54.780> Shane<01:26:55.080> it 01:26:55.820 --> 01:26:55.830 align:start position:0% to do it inside contracts on Shane it 01:26:55.830 --> 01:26:57.650 align:start position:0% to do it inside contracts on Shane it wouldn't<01:26:56.160> be<01:26:56.250> a<01:26:56.280> viable<01:26:56.580> option<01:26:56.790> to<01:26:57.270> verify 01:26:57.650 --> 01:26:57.660 align:start position:0% wouldn't be a viable option to verify 01:26:57.660 --> 01:27:00.440 align:start position:0% wouldn't be a viable option to verify system<01:26:57.870> price<01:26:58.620> however<01:26:59.250> appear<01:26:59.850> with<01:27:00.270> high 01:27:00.440 --> 01:27:00.450 align:start position:0% system price however appear with high 01:27:00.450 --> 01:27:03.170 align:start position:0% system price however appear with high pressure<01:27:00.660> at<01:27:00.990> all<01:27:01.140> you<01:27:01.500> can<01:27:01.680> just<01:27:01.710> verify<01:27:02.310> the 01:27:03.170 --> 01:27:03.180 align:start position:0% pressure at all you can just verify the 01:27:03.180 --> 01:27:06.830 align:start position:0% pressure at all you can just verify the signature<01:27:03.690> on<01:27:04.350> to<01:27:04.980> TCF<01:27:05.370> river<01:27:05.670> and<01:27:05.940> this<01:27:06.480> huge 01:27:06.830 --> 01:27:06.840 align:start position:0% signature on to TCF river and this huge 01:27:06.840 --> 01:27:07.490 align:start position:0% signature on to TCF river and this huge higher<01:27:07.140> odds 01:27:07.490 --> 01:27:07.500 align:start position:0% higher odds 01:27:07.500 --> 01:27:09.350 align:start position:0% higher odds basically<01:27:07.830> you<01:27:07.980> can<01:27:08.100> verify<01:27:08.310> the<01:27:09.090> data 01:27:09.350 --> 01:27:09.360 align:start position:0% basically you can verify the data 01:27:09.360 --> 01:27:11.630 align:start position:0% basically you can verify the data assigned<01:27:09.960> place<01:27:10.350> to<01:27:10.470> take<01:27:10.590> the<01:27:10.710> provider<01:27:11.040> send 01:27:11.630 --> 01:27:11.640 align:start position:0% assigned place to take the provider send 01:27:11.640 --> 01:27:13.250 align:start position:0% assigned place to take the provider send you<01:27:11.700> changing<01:27:12.030> floaties<01:27:12.240> interpret<01:27:12.840> it<01:27:13.050> and 01:27:13.250 --> 01:27:13.260 align:start position:0% you changing floaties interpret it and 01:27:13.260 --> 01:27:16.100 align:start position:0% you changing floaties interpret it and what<01:27:13.950> your<01:27:14.130> first<01:27:14.340> so<01:27:14.550> is<01:27:14.670> running<01:27:15.030> as<01:27:15.990> the 01:27:16.100 --> 01:27:16.110 align:start position:0% what your first so is running as the 01:27:16.110 --> 01:27:18.440 align:start position:0% what your first so is running as the same<01:27:16.290> data<01:27:16.530> through<01:27:16.920> multiple<01:27:17.400> channels<01:27:17.760> so 01:27:18.440 --> 01:27:18.450 align:start position:0% same data through multiple channels so 01:27:18.450 --> 01:27:20.600 align:start position:0% same data through multiple channels so really<01:27:19.110> an<01:27:19.230> attestation<01:27:19.590> of<01:27:19.950> the<01:27:20.100> data<01:27:20.250> and 01:27:20.600 --> 01:27:20.610 align:start position:0% really an attestation of the data and 01:27:20.610 --> 01:27:21.860 align:start position:0% really an attestation of the data and you<01:27:21.180> get 01:27:21.860 --> 01:27:21.870 align:start position:0% you get 01:27:21.870 --> 01:27:24.689 align:start position:0% you get redundancy<01:27:22.870> threatening<01:27:23.830> magic<01:27:24.100> Pacino's 01:27:24.689 --> 01:27:24.699 align:start position:0% redundancy threatening magic Pacino's 01:27:24.699 --> 01:27:26.400 align:start position:0% redundancy threatening magic Pacino's preventing<01:27:25.150> the<01:27:25.270> same<01:27:25.449> thing<01:27:25.660> that<01:27:25.780> pops<01:27:26.050> from 01:27:26.400 --> 01:27:26.410 align:start position:0% preventing the same thing that pops from 01:27:26.410 --> 01:27:30.209 align:start position:0% preventing the same thing that pops from expert<01:27:26.800> data<01:27:27.010> providers<01:27:27.580> right<01:27:27.910> so<01:27:29.040> we<01:27:30.040> can 01:27:30.209 --> 01:27:30.219 align:start position:0% expert data providers right so we can 01:27:30.219 --> 01:27:31.770 align:start position:0% expert data providers right so we can always<01:27:30.640> get<01:27:30.790> more<01:27:30.940> secure<01:27:31.300> but<01:27:31.510> that<01:27:31.630> fit 01:27:31.770 --> 01:27:31.780 align:start position:0% always get more secure but that fit 01:27:31.780 --> 01:27:33.900 align:start position:0% always get more secure but that fit existing<01:27:32.260> Authority<01:27:32.830> quite<01:27:33.370> secure<01:27:33.699> rights 01:27:33.900 --> 01:27:33.910 align:start position:0% existing Authority quite secure rights 01:27:33.910 --> 01:27:35.729 align:start position:0% existing Authority quite secure rights but<01:27:34.090> we<01:27:34.150> are<01:27:34.330> feeding<01:27:34.540> right<01:27:34.840> into<01:27:34.900> the<01:27:35.320> GCF 01:27:35.729 --> 01:27:35.739 align:start position:0% but we are feeding right into the GCF 01:27:35.739 --> 01:27:38.160 align:start position:0% but we are feeding right into the GCF has<01:27:36.610> written<01:27:36.850> many<01:27:37.090> security<01:27:37.719> assumptions 01:27:38.160 --> 01:27:38.170 align:start position:0% has written many security assumptions 01:27:38.170 --> 01:27:40.979 align:start position:0% has written many security assumptions visitor<01:27:38.830> able<01:27:39.190> to<01:27:39.310> provide<01:27:39.670> by<01:27:40.120> combining<01:27:40.510> the 01:27:40.979 --> 01:27:40.989 align:start position:0% visitor able to provide by combining the 01:27:40.989 --> 01:27:44.250 align:start position:0% visitor able to provide by combining the TCF<01:27:41.410> and<01:27:41.699> combining<01:27:42.699> chaining<01:27:43.150> looks<01:27:43.360> person 01:27:44.250 --> 01:27:44.260 align:start position:0% TCF and combining chaining looks person 01:27:44.260 --> 01:27:47.880 align:start position:0% TCF and combining chaining looks person explained<01:27:44.670> so<01:27:45.670> westfield<01:27:46.410> cousins<01:27:47.410> is<01:27:47.530> a<01:27:47.650> that 01:27:47.880 --> 01:27:47.890 align:start position:0% explained so westfield cousins is a that 01:27:47.890 --> 01:27:49.620 align:start position:0% explained so westfield cousins is a that basically<01:27:48.250> is<01:27:48.400> a<01:27:48.550> process<01:27:48.880> to<01:27:49.000> consume<01:27:49.390> it<01:27:49.510> is 01:27:49.620 --> 01:27:49.630 align:start position:0% basically is a process to consume it is 01:27:49.630 --> 01:27:52.169 align:start position:0% basically is a process to consume it is very<01:27:49.840> simple<01:27:50.290> with<01:27:51.040> computer<01:27:51.489> today<01:27:51.640> does<01:27:52.000> so 01:27:52.169 --> 01:27:52.179 align:start position:0% very simple with computer today does so 01:27:52.179 --> 01:27:55.410 align:start position:0% very simple with computer today does so let's<01:27:52.330> say<01:27:52.540> we<01:27:52.870> want<01:27:53.080> to<01:27:54.030> let's<01:27:55.030> say<01:27:55.120> we<01:27:55.210> have<01:27:55.360> a 01:27:55.410 --> 01:27:55.420 align:start position:0% let's say we want to let's say we have a 01:27:55.420 --> 01:27:57.330 align:start position:0% let's say we want to let's say we have a data<01:27:55.570> provider<01:27:55.929> or<01:27:56.320> a<01:27:56.350> Spartan<01:27:56.739> track<01:27:56.949> Creator 01:27:57.330 --> 01:27:57.340 align:start position:0% data provider or a Spartan track Creator 01:27:57.340 --> 01:28:00.030 align:start position:0% data provider or a Spartan track Creator who<01:27:58.150> has<01:27:58.210> a<01:27:58.540> use<01:27:58.750> case<01:27:58.960> he<01:27:59.440> wants<01:27:59.650> to<01:27:59.739> get<01:27:59.890> the 01:28:00.030 --> 01:28:00.040 align:start position:0% who has a use case he wants to get the 01:28:00.040 --> 01:28:02.010 align:start position:0% who has a use case he wants to get the price<01:28:00.310> but<01:28:00.850> he<01:28:00.969> will<01:28:01.150> put<01:28:01.420> transmit<01:28:01.900> this 01:28:02.010 --> 01:28:02.020 align:start position:0% price but he will put transmit this 01:28:02.020 --> 01:28:04.500 align:start position:0% price but he will put transmit this price<01:28:02.260> uncheck<01:28:02.800> right<01:28:03.040> so<01:28:03.850> maybe<01:28:04.030> you<01:28:04.239> do<01:28:04.330> some 01:28:04.500 --> 01:28:04.510 align:start position:0% price uncheck right so maybe you do some 01:28:04.510 --> 01:28:07.590 align:start position:0% price uncheck right so maybe you do some computation<01:28:04.870> of<01:28:05.290> chain<01:28:05.650> using<01:28:05.949> so<01:28:06.190> TCF<01:28:06.670> and<01:28:06.910> he 01:28:07.590 --> 01:28:07.600 align:start position:0% computation of chain using so TCF and he 01:28:07.600 --> 01:28:10.400 align:start position:0% computation of chain using so TCF and he returns<01:28:08.050> the<01:28:08.140> request<01:28:08.890> or<01:28:09.219> the<01:28:09.340> results<01:28:10.030> right 01:28:10.400 --> 01:28:10.410 align:start position:0% returns the request or the results right 01:28:10.410 --> 01:28:12.689 align:start position:0% returns the request or the results right using<01:28:11.410> the<01:28:11.560> same<01:28:11.710> process<01:28:12.130> we<01:28:12.340> go<01:28:12.460> through<01:28:12.489> the 01:28:12.689 --> 01:28:12.699 align:start position:0% using the same process we go through the 01:28:12.699 --> 01:28:14.430 align:start position:0% using the same process we go through the adapter<01:28:13.179> because<01:28:13.840> through<01:28:14.020> the<01:28:14.080> chain<01:28:14.320> you 01:28:14.430 --> 01:28:14.440 align:start position:0% adapter because through the chain you 01:28:14.440 --> 01:28:17.220 align:start position:0% adapter because through the chain you know<01:28:14.530> interchange<01:28:15.100> fees<01:28:15.850> to<01:28:16.510> answer<01:28:16.929> to<01:28:17.140> the 01:28:17.220 --> 01:28:17.230 align:start position:0% know interchange fees to answer to the 01:28:17.230 --> 01:28:19.439 align:start position:0% know interchange fees to answer to the training<01:28:17.530> contracts<01:28:17.949> which<01:28:18.640> fits<01:28:18.910> into<01:28:19.300> the 01:28:19.439 --> 01:28:19.449 align:start position:0% training contracts which fits into the 01:28:19.449 --> 01:28:22.050 align:start position:0% training contracts which fits into the consumer<01:28:19.960> contracts<01:28:20.440> so<01:28:21.160> a<01:28:21.429> very<01:28:21.699> easy 01:28:22.050 --> 01:28:22.060 align:start position:0% consumer contracts so a very easy 01:28:22.060 --> 01:28:23.060 align:start position:0% consumer contracts so a very easy process 01:28:23.060 --> 01:28:23.070 align:start position:0% process 01:28:23.070 --> 01:28:27.750 align:start position:0% process now<01:28:24.070> I<01:28:24.929> didn't<01:28:25.929> give<01:28:26.080> any<01:28:26.260> clear<01:28:26.770> time<01:28:27.400> to<01:28:27.550> use 01:28:27.750 --> 01:28:27.760 align:start position:0% now I didn't give any clear time to use 01:28:27.760 --> 01:28:30.030 align:start position:0% now I didn't give any clear time to use images<01:28:28.179> because<01:28:28.540> the<01:28:29.290> use<01:28:29.469> cases<01:28:29.710> for<01:28:29.980> this 01:28:30.030 --> 01:28:30.040 align:start position:0% images because the use cases for this 01:28:30.040 --> 01:28:32.850 align:start position:0% images because the use cases for this are<01:28:30.489> limitless<01:28:31.000> you<01:28:31.780> can<01:28:31.960> get<01:28:32.110> any<01:28:32.410> kind<01:28:32.679> of 01:28:32.850 --> 01:28:32.860 align:start position:0% are limitless you can get any kind of 01:28:32.860 --> 01:28:35.640 align:start position:0% are limitless you can get any kind of API<01:28:33.340> and<01:28:33.730> point<01:28:34.060> to<01:28:34.510> fit<01:28:34.690> data<01:28:34.929> doors<01:28:35.469> my 01:28:35.640 --> 01:28:35.650 align:start position:0% API and point to fit data doors my 01:28:35.650 --> 01:28:38.430 align:start position:0% API and point to fit data doors my podcast<01:28:36.070> using<01:28:36.340> ctcf<01:28:37.030> and<01:28:37.300> using<01:28:38.080> chinese 01:28:38.430 --> 01:28:38.440 align:start position:0% podcast using ctcf and using chinese 01:28:38.440 --> 01:28:40.919 align:start position:0% podcast using ctcf and using chinese notes<01:28:38.679> and<01:28:38.920> here<01:28:39.580> it<01:28:39.850> goes<01:28:40.030> from<01:28:40.210> insurance 01:28:40.919 --> 01:28:40.929 align:start position:0% notes and here it goes from insurance 01:28:40.929 --> 01:28:43.290 align:start position:0% notes and here it goes from insurance contracts<01:28:41.500> to<01:28:41.739> global<01:28:42.130> trade<01:28:42.160> and<01:28:43.060> trade 01:28:43.290 --> 01:28:43.300 align:start position:0% contracts to global trade and trade 01:28:43.300 --> 01:28:45.360 align:start position:0% contracts to global trade and trade finance<01:28:43.810> basically<01:28:44.320> any<01:28:44.530> kind<01:28:44.860> of<01:28:44.949> use<01:28:45.130> cases 01:28:45.360 --> 01:28:45.370 align:start position:0% finance basically any kind of use cases 01:28:45.370 --> 01:28:48.090 align:start position:0% finance basically any kind of use cases that<01:28:45.760> needs<01:28:46.420> data<01:28:46.660> doesn't<01:28:47.500> want<01:28:47.800> this<01:28:47.890> data 01:28:48.090 --> 01:28:48.100 align:start position:0% that needs data doesn't want this data 01:28:48.100 --> 01:28:49.939 align:start position:0% that needs data doesn't want this data to<01:28:48.370> be<01:28:48.489> published<01:28:48.850> unchecked<01:28:49.390> because 01:28:49.939 --> 01:28:49.949 align:start position:0% to be published unchecked because 01:28:49.949 --> 01:28:54.090 align:start position:0% to be published unchecked because financial<01:28:50.949> boom<01:28:51.160> financial<01:28:52.440> enterprises<01:28:53.440> are 01:28:54.090 --> 01:28:54.100 align:start position:0% financial boom financial enterprises are 01:28:54.100 --> 01:28:55.770 align:start position:0% financial boom financial enterprises are company<01:28:54.460> many<01:28:54.820> don't<01:28:55.239> really<01:28:55.540> want<01:28:55.690> to 01:28:55.770 --> 01:28:55.780 align:start position:0% company many don't really want to 01:28:55.780 --> 01:28:58.620 align:start position:0% company many don't really want to publish<01:28:56.050> order<01:28:56.469> Troy<01:28:56.739> sunshine<01:28:57.190> right<01:28:57.460> but<01:28:58.330> in 01:28:58.620 --> 01:28:58.630 align:start position:0% publish order Troy sunshine right but in 01:28:58.630 --> 01:29:00.090 align:start position:0% publish order Troy sunshine right but in order<01:28:58.840> to<01:28:58.870> use<01:28:59.080> the<01:28:59.230> security<01:28:59.530> guarantees 01:29:00.090 --> 01:29:00.100 align:start position:0% order to use the security guarantees 01:29:00.100 --> 01:29:03.689 align:start position:0% order to use the security guarantees that<01:29:00.429> TCF<01:29:01.420> and<01:29:01.949> ethereal<01:29:02.949> and<01:29:03.040> public<01:29:03.340> options 01:29:03.689 --> 01:29:03.699 align:start position:0% that TCF and ethereal and public options 01:29:03.699 --> 01:29:06.150 align:start position:0% that TCF and ethereal and public options offer<01:29:04.120> so<01:29:04.510> this<01:29:05.230> is<01:29:05.290> a<01:29:05.350> beautiful<01:29:05.739> way<01:29:05.860> to<01:29:05.890> do 01:29:06.150 --> 01:29:06.160 align:start position:0% offer so this is a beautiful way to do 01:29:06.160 --> 01:29:08.910 align:start position:0% offer so this is a beautiful way to do it<01:29:06.280> basically<01:29:06.670> answer<01:29:07.739> possibilities<01:29:08.739> are 01:29:08.910 --> 01:29:08.920 align:start position:0% it basically answer possibilities are 01:29:08.920 --> 01:29:09.540 align:start position:0% it basically answer possibilities are limitless 01:29:09.540 --> 01:29:09.550 align:start position:0% limitless 01:29:09.550 --> 01:29:11.910 align:start position:0% limitless so<01:29:10.150> I<01:29:10.330> think<01:29:10.449> I<01:29:10.630> probably<01:29:10.660> ran<01:29:11.230> out<01:29:11.380> of<01:29:11.469> time<01:29:11.860> so 01:29:11.910 --> 01:29:11.920 align:start position:0% so I think I probably ran out of time so 01:29:11.920 --> 01:29:13.359 align:start position:0% so I think I probably ran out of time so I'm<01:29:12.370> gonna<01:29:12.550> and 01:29:13.359 --> 01:29:13.369 align:start position:0% I'm gonna and 01:29:13.369 --> 01:29:15.310 align:start position:0% I'm gonna and I<01:29:13.400> had<01:29:13.670> if<01:29:13.880> you<01:29:13.940> guys<01:29:14.030> are<01:29:14.210> like<01:29:14.960> but<01:29:15.199> I<01:29:15.289> think 01:29:15.310 --> 01:29:15.320 align:start position:0% I had if you guys are like but I think 01:29:15.320 --> 01:29:18.430 align:start position:0% I had if you guys are like but I think it's<01:29:15.590> fine<01:29:16.449> yeah<01:29:17.449> this<01:29:17.630> I<01:29:17.989> would<01:29:18.260> have<01:29:18.349> to 01:29:18.430 --> 01:29:18.440 align:start position:0% it's fine yeah this I would have to 01:29:18.440 --> 01:29:19.990 align:start position:0% it's fine yeah this I would have to finish<01:29:18.650> by<01:29:18.889> saying<01:29:18.920> I<01:29:19.429> think<01:29:19.489> that<01:29:19.760> was<01:29:19.969> a 01:29:19.990 --> 01:29:20.000 align:start position:0% finish by saying I think that was a 01:29:20.000 --> 01:29:22.689 align:start position:0% finish by saying I think that was a beautiful<01:29:20.360> efforts<01:29:20.929> that<01:29:21.460> many<01:29:22.460> companies 01:29:22.689 --> 01:29:22.699 align:start position:0% beautiful efforts that many companies 01:29:22.699 --> 01:29:26.890 align:start position:0% beautiful efforts that many companies led<01:29:23.239> through<01:29:24.050> a<01:29:24.260> thriver<01:29:24.980> lecture<01:29:25.400> and<01:29:25.900> yeah 01:29:26.890 --> 01:29:26.900 align:start position:0% led through a thriver lecture and yeah 01:29:26.900 --> 01:29:28.240 align:start position:0% led through a thriver lecture and yeah I'm<01:29:27.110> really<01:29:27.349> excited<01:29:27.530> to<01:29:27.770> see<01:29:27.949> where<01:29:28.130> it's 01:29:28.240 --> 01:29:28.250 align:start position:0% I'm really excited to see where it's 01:29:28.250 --> 01:29:28.839 align:start position:0% I'm really excited to see where it's gonna<01:29:28.400> go 01:29:28.839 --> 01:29:28.849 align:start position:0% gonna go 01:29:28.849 --> 01:29:32.379 align:start position:0% gonna go these<01:29:29.690> use<01:29:29.900> cases<01:29:29.929> are<01:29:31.090> really<01:29:32.090> limitless 01:29:32.379 --> 01:29:32.389 align:start position:0% these use cases are really limitless 01:29:32.389 --> 01:29:34.720 align:start position:0% these use cases are really limitless into<01:29:32.840> the<01:29:32.989> future<01:29:33.409> but<01:29:34.130> you're<01:29:34.280> creating<01:29:34.520> here 01:29:34.720 --> 01:29:34.730 align:start position:0% into the future but you're creating here 01:29:34.730 --> 01:29:36.609 align:start position:0% into the future but you're creating here we<01:29:35.059> have<01:29:35.210> a<01:29:35.239> huge<01:29:35.449> impact<01:29:35.599> in<01:29:35.960> serve<01:29:36.199> on<01:29:36.440> the 01:29:36.609 --> 01:29:36.619 align:start position:0% we have a huge impact in serve on the 01:29:36.619 --> 01:29:38.830 align:start position:0% we have a huge impact in serve on the industry<01:29:37.010> I<01:29:37.130> think<01:29:37.190> and<01:29:37.550> drive<01:29:37.969> companies<01:29:38.510> to 01:29:38.830 --> 01:29:38.840 align:start position:0% industry I think and drive companies to 01:29:38.840 --> 01:29:40.660 align:start position:0% industry I think and drive companies to start<01:29:39.079> using<01:29:39.230> a<01:29:39.500> big<01:29:39.650> brush<01:29:39.860> and<01:29:40.010> smart<01:29:40.429> more 01:29:40.660 --> 01:29:40.670 align:start position:0% start using a big brush and smart more 01:29:40.670 --> 01:30:01.120 align:start position:0% start using a big brush and smart more so<01:29:41.270> thank<01:29:41.630> you<01:29:41.719> very<01:29:52.270> much 01:30:01.120 --> 01:30:01.130 align:start position:0% 01:30:01.130 --> 01:30:04.970 align:start position:0% [Music] 01:30:04.970 --> 01:30:04.980 align:start position:0% 01:30:04.980 --> 01:30:07.850 align:start position:0% hi<01:30:05.640> everyone<01:30:05.940> my<01:30:06.810> name<01:30:06.989> is<01:30:07.110> John<01:30:07.320> King<01:30:07.469> second 01:30:07.850 --> 01:30:07.860 align:start position:0% hi everyone my name is John King second 01:30:07.860 --> 01:30:11.610 align:start position:0% hi everyone my name is John King second one<01:30:08.640> of<01:30:08.730> the<01:30:08.820> co-founders<01:30:09.449> I<01:30:09.780> believe<01:30:10.260> my 01:30:11.610 --> 01:30:11.620 align:start position:0% one of the co-founders I believe my 01:30:11.620 --> 01:30:16.620 align:start position:0% one of the co-founders I believe my Paisley<01:30:12.220> was<01:30:13.000> back<01:30:13.210> then<01:30:14.610> today<01:30:15.610> it's<01:30:15.910> great 01:30:16.620 --> 01:30:16.630 align:start position:0% Paisley was back then today it's great 01:30:16.630 --> 01:30:19.110 align:start position:0% Paisley was back then today it's great that<01:30:16.930> I<01:30:17.080> can<01:30:17.140> plus<01:30:17.500> because<01:30:18.250> you<01:30:18.550> mention<01:30:19.000> an 01:30:19.110 --> 01:30:19.120 align:start position:0% that I can plus because you mention an 01:30:19.120 --> 01:30:21.330 align:start position:0% that I can plus because you mention an application<01:30:19.720> which<01:30:19.960> packet<01:30:20.350> that<01:30:20.530> we<01:30:20.710> work 01:30:21.330 --> 01:30:21.340 align:start position:0% application which packet that we work 01:30:21.340 --> 01:30:24.150 align:start position:0% application which packet that we work together<01:30:21.490> to<01:30:22.000> do<01:30:22.150> away<01:30:22.390> from<01:30:22.570> us<01:30:22.660> today<01:30:23.160> the 01:30:24.150 --> 01:30:24.160 align:start position:0% together to do away from us today the 01:30:24.160 --> 01:30:29.340 align:start position:0% together to do away from us today the men<01:30:24.370> you<01:30:26.250> securely<01:30:27.250> in<01:30:27.520> the<01:30:28.330> block<01:30:28.510> jeans<01:30:28.720> I'm 01:30:29.340 --> 01:30:29.350 align:start position:0% men you securely in the block jeans I'm 01:30:29.350 --> 01:30:32.400 align:start position:0% men you securely in the block jeans I'm going<01:30:29.590> to<01:30:29.680> talk<01:30:29.770> about<01:30:29.800> how<01:30:30.160> we've<01:30:31.380> tried<01:30:32.380> to 01:30:32.400 --> 01:30:32.410 align:start position:0% going to talk about how we've tried to 01:30:32.410 --> 01:30:34.350 align:start position:0% going to talk about how we've tried to build<01:30:32.680> the<01:30:32.950> block<01:30:33.130> chaining<01:30:33.430> that<01:30:33.700> isn't 01:30:34.350 --> 01:30:34.360 align:start position:0% build the block chaining that isn't 01:30:34.360 --> 01:30:41.220 align:start position:0% build the block chaining that isn't managed<01:30:35.370> TCF<01:30:36.930> so<01:30:38.940> an<01:30:39.940> enigma<01:30:40.420> our<01:30:40.600> goal<01:30:40.900> is<01:30:41.200> to 01:30:41.220 --> 01:30:41.230 align:start position:0% managed TCF so an enigma our goal is to 01:30:41.230 --> 01:30:44.040 align:start position:0% managed TCF so an enigma our goal is to ensure<01:30:42.130> a<01:30:42.400> document<01:30:42.940> level<01:30:43.060> to<01:30:43.420> your<01:30:43.600> dissent 01:30:44.040 --> 01:30:44.050 align:start position:0% ensure a document level to your dissent 01:30:44.050 --> 01:30:46.110 align:start position:0% ensure a document level to your dissent as<01:30:44.200> technologies<01:30:44.710> we<01:30:45.250> focus<01:30:45.550> primarily<01:30:45.730> on 01:30:46.110 --> 01:30:46.120 align:start position:0% as technologies we focus primarily on 01:30:46.120 --> 01:30:48.750 align:start position:0% as technologies we focus primarily on public<01:30:46.480> love<01:30:46.660> chains<01:30:46.930> the<01:30:47.830> way<01:30:47.980> we<01:30:48.220> try<01:30:48.430> to<01:30:48.490> do 01:30:48.750 --> 01:30:48.760 align:start position:0% public love chains the way we try to do 01:30:48.760 --> 01:30:51.990 align:start position:0% public love chains the way we try to do this<01:30:48.940> is<01:30:49.210> by<01:30:49.600> enabling<01:30:49.840> block<01:30:50.740> chains<01:30:51.040> public 01:30:51.990 --> 01:30:52.000 align:start position:0% this is by enabling block chains public 01:30:52.000 --> 01:30:54.770 align:start position:0% this is by enabling block chains public or<01:30:52.120> private<01:30:52.270> to<01:30:53.110> handle<01:30:53.620> sensitive<01:30:53.770> data<01:30:54.190> and 01:30:54.770 --> 01:30:54.780 align:start position:0% or private to handle sensitive data and 01:30:54.780 --> 01:31:00.090 align:start position:0% or private to handle sensitive data and we've<01:30:55.780> built<01:30:56.140> a<01:30:57.030> computation<01:30:58.030> platform<01:30:59.100> that 01:31:00.090 --> 01:31:00.100 align:start position:0% we've built a computation platform that 01:31:00.100 --> 01:31:02.220 align:start position:0% we've built a computation platform that enables<01:31:00.430> block<01:31:00.880> chain<01:31:01.090> functions<01:31:01.630> or<01:31:01.870> smart 01:31:02.220 --> 01:31:02.230 align:start position:0% enables block chain functions or smart 01:31:02.230 --> 01:31:04.740 align:start position:0% enables block chain functions or smart contracts<01:31:02.740> to<01:31:03.280> run<01:31:03.550> with<01:31:03.760> the<01:31:04.120> inputs<01:31:04.540> and 01:31:04.740 --> 01:31:04.750 align:start position:0% contracts to run with the inputs and 01:31:04.750 --> 01:31:11.960 align:start position:0% contracts to run with the inputs and this<01:31:05.230> is<01:31:05.350> done<01:31:05.560> using<01:31:05.920> the<01:31:06.100> TC<01:31:06.570> framework<01:31:08.040> so<01:31:09.040> I 01:31:11.960 --> 01:31:11.970 align:start position:0% 01:31:11.970 --> 01:31:14.370 align:start position:0% guess<01:31:12.970> the<01:31:13.120> problem<01:31:13.420> of<01:31:13.630> privacy<01:31:14.080> is<01:31:14.140> very 01:31:14.370 --> 01:31:14.380 align:start position:0% guess the problem of privacy is very 01:31:14.380 --> 01:31:15.810 align:start position:0% guess the problem of privacy is very obvious<01:31:14.770> I'm<01:31:14.890> going<01:31:15.100> to<01:31:15.160> spend<01:31:15.340> time<01:31:15.490> on<01:31:15.550> this 01:31:15.810 --> 01:31:15.820 align:start position:0% obvious I'm going to spend time on this 01:31:15.820 --> 01:31:17.280 align:start position:0% obvious I'm going to spend time on this this<01:31:16.030> is<01:31:16.150> something<01:31:16.360> that's<01:31:16.630> been<01:31:16.810> they<01:31:16.990> did 01:31:17.280 --> 01:31:17.290 align:start position:0% this is something that's been they did 01:31:17.290 --> 01:31:17.790 align:start position:0% this is something that's been they did to<01:31:17.470> us 01:31:17.790 --> 01:31:17.800 align:start position:0% to us 01:31:17.800 --> 01:31:20.379 align:start position:0% to us we<01:31:18.280> started<01:31:18.610> our<01:31:18.820> research<01:31:19.000> into 01:31:20.379 --> 01:31:20.389 align:start position:0% we started our research into 01:31:20.389 --> 01:31:23.620 align:start position:0% we started our research into t1<01:31:20.719> vs<01:31:21.050> MIT<01:31:21.770> and<01:31:22.159> at<01:31:23.090> the<01:31:23.210> time<01:31:23.420> we<01:31:23.540> were 01:31:23.620 --> 01:31:23.630 align:start position:0% t1 vs MIT and at the time we were 01:31:23.630 --> 01:31:27.010 align:start position:0% t1 vs MIT and at the time we were focusing<01:31:24.020> on<01:31:24.139> multi-party<01:31:24.679> computation<01:31:26.020> we 01:31:27.010 --> 01:31:27.020 align:start position:0% focusing on multi-party computation we 01:31:27.020 --> 01:31:28.780 align:start position:0% focusing on multi-party computation we wrote<01:31:27.199> two<01:31:27.350> papers<01:31:27.710> that<01:31:27.889> were<01:31:28.010> most<01:31:28.429> cited<01:31:28.699> in 01:31:28.780 --> 01:31:28.790 align:start position:0% wrote two papers that were most cited in 01:31:28.790 --> 01:31:31.649 align:start position:0% wrote two papers that were most cited in the<01:31:28.880> industry<01:31:29.360> fast<01:31:30.139> forward<01:31:30.619> four<01:31:30.920> years 01:31:31.649 --> 01:31:31.659 align:start position:0% the industry fast forward four years 01:31:31.659 --> 01:31:35.500 align:start position:0% the industry fast forward four years we're<01:31:32.659> at<01:31:32.810> the<01:31:32.989> place<01:31:33.619> where<01:31:34.070> were<01:31:35.000> about<01:31:35.300> to 01:31:35.500 --> 01:31:35.510 align:start position:0% we're at the place where were about to 01:31:35.510 --> 01:31:38.290 align:start position:0% we're at the place where were about to launch<01:31:35.630> our<01:31:35.840> network<01:31:36.320> which<01:31:37.300> again 01:31:38.290 --> 01:31:38.300 align:start position:0% launch our network which again 01:31:38.300 --> 01:31:40.300 align:start position:0% launch our network which again introduced<01:31:38.719> responsible<01:31:39.409> pacific<01:31:39.830> contract 01:31:40.300 --> 01:31:40.310 align:start position:0% introduced responsible pacific contract 01:31:40.310 --> 01:31:42.250 align:start position:0% introduced responsible pacific contract a<01:31:40.520> civil<01:31:41.090> contract<01:31:41.540> is<01:31:41.659> a<01:31:41.690> smart<01:31:42.020> contract 01:31:42.250 --> 01:31:42.260 align:start position:0% a civil contract is a smart contract 01:31:42.260 --> 01:31:47.080 align:start position:0% a civil contract is a smart contract that<01:31:43.119> can<01:31:44.119> run<01:31:44.330> with<01:31:44.480> individuals<01:31:45.139> and<01:31:46.090> we're 01:31:47.080 --> 01:31:47.090 align:start position:0% that can run with individuals and we're 01:31:47.090 --> 01:31:48.580 align:start position:0% that can run with individuals and we're seeing<01:31:47.540> that<01:31:47.630> this<01:31:47.929> has<01:31:48.080> a<01:31:48.170> lot<01:31:48.290> of<01:31:48.380> use<01:31:48.560> cases 01:31:48.580 --> 01:31:48.590 align:start position:0% seeing that this has a lot of use cases 01:31:48.590 --> 01:31:50.800 align:start position:0% seeing that this has a lot of use cases and<01:31:49.130> the<01:31:49.219> public<01:31:49.550> option<01:31:49.940> public<01:31:50.360> poaching 01:31:50.800 --> 01:31:50.810 align:start position:0% and the public option public poaching 01:31:50.810 --> 01:31:53.530 align:start position:0% and the public option public poaching ecosystem<01:31:51.739> both<01:31:52.340> in<01:31:52.610> terms<01:31:52.820> of<01:31:52.940> enabling<01:31:53.239> new 01:31:53.530 --> 01:31:53.540 align:start position:0% ecosystem both in terms of enabling new 01:31:53.540 --> 01:31:55.359 align:start position:0% ecosystem both in terms of enabling new application<01:31:54.110> that<01:31:54.139> haven't<01:31:54.530> existed<01:31:54.650> before 01:31:55.359 --> 01:31:55.369 align:start position:0% application that haven't existed before 01:31:55.369 --> 01:31:58.050 align:start position:0% application that haven't existed before but<01:31:55.610> also<01:31:56.090> creating<01:31:56.810> a<01:31:56.840> much<01:31:57.020> better<01:31:57.170> to 01:31:58.050 --> 01:31:58.060 align:start position:0% but also creating a much better to 01:31:58.060 --> 01:32:03.340 align:start position:0% but also creating a much better to expose<01:31:59.060> cases<01:32:01.210> today<01:32:02.210> I'm<01:32:02.719> going<01:32:03.110> to<01:32:03.170> talk 01:32:03.340 --> 01:32:03.350 align:start position:0% expose cases today I'm going to talk 01:32:03.350 --> 01:32:04.660 align:start position:0% expose cases today I'm going to talk about<01:32:03.380> discovery<01:32:04.040> which<01:32:04.219> is<01:32:04.250> the<01:32:04.369> first 01:32:04.660 --> 01:32:04.670 align:start position:0% about discovery which is the first 01:32:04.670 --> 01:32:07.689 align:start position:0% about discovery which is the first release<01:32:05.679> the<01:32:06.679> first<01:32:06.860> thing<01:32:07.070> so<01:32:07.190> far<01:32:07.340> network 01:32:07.689 --> 01:32:07.699 align:start position:0% release the first thing so far network 01:32:07.699 --> 01:32:09.850 align:start position:0% release the first thing so far network connects<01:32:08.030> about<01:32:08.210> four<01:32:08.360> months<01:32:08.659> this<01:32:09.500> company 01:32:09.850 --> 01:32:09.860 align:start position:0% connects about four months this company 01:32:09.860 --> 01:32:11.410 align:start position:0% connects about four months this company is<01:32:09.889> interesting<01:32:10.400> because<01:32:10.520> it's<01:32:11.239> an 01:32:11.410 --> 01:32:11.420 align:start position:0% is interesting because it's an 01:32:11.420 --> 01:32:14.649 align:start position:0% is interesting because it's an implementation<01:32:11.690> of<01:32:12.050> TCF<01:32:12.820> we<01:32:13.820> actually<01:32:14.239> went 01:32:14.649 --> 01:32:14.659 align:start position:0% implementation of TCF we actually went 01:32:14.659 --> 01:32:16.450 align:start position:0% implementation of TCF we actually went our<01:32:14.960> separate<01:32:15.320> ways<01:32:15.350> but<01:32:15.530> we<01:32:15.889> converge<01:32:16.280> on 01:32:16.450 --> 01:32:16.460 align:start position:0% our separate ways but we converge on 01:32:16.460 --> 01:32:19.330 align:start position:0% our separate ways but we converge on they<01:32:16.550> say<01:32:16.730> expect<01:32:17.119> more<01:32:17.300> or<01:32:17.330> less<01:32:18.340> improve 01:32:19.330 --> 01:32:19.340 align:start position:0% they say expect more or less improve 01:32:19.340 --> 01:32:21.640 align:start position:0% they say expect more or less improve means<01:32:19.639> he<01:32:19.760> said<01:32:19.969> in<01:32:20.119> two<01:32:20.300> ways<01:32:20.510> one<01:32:20.810> is<01:32:20.869> it<01:32:21.469> is<01:32:21.619> a 01:32:21.640 --> 01:32:21.650 align:start position:0% means he said in two ways one is it is a 01:32:21.650 --> 01:32:23.379 align:start position:0% means he said in two ways one is it is a stateful<01:32:22.040> net<01:32:22.429> what<01:32:22.610> would<01:32:22.790> it<01:32:22.880> stays<01:32:23.090> private 01:32:23.379 --> 01:32:23.389 align:start position:0% stateful net what would it stays private 01:32:23.389 --> 01:32:25.300 align:start position:0% stateful net what would it stays private and<01:32:23.810> the<01:32:24.409> second<01:32:24.770> thing<01:32:24.860> is<01:32:25.040> in<01:32:25.190> this 01:32:25.300 --> 01:32:25.310 align:start position:0% and the second thing is in this 01:32:25.310 --> 01:32:28.240 align:start position:0% and the second thing is in this compatibility<01:32:26.210> team<01:32:26.630> which<01:32:26.869> means<01:32:27.250> something 01:32:28.240 --> 01:32:28.250 align:start position:0% compatibility team which means something 01:32:28.250 --> 01:32:30.320 align:start position:0% compatibility team which means something that<01:32:28.280> our<01:32:28.929> contract 01:32:30.320 --> 01:32:30.330 align:start position:0% that our contract 01:32:30.330 --> 01:32:33.230 align:start position:0% that our contract it's<01:32:30.450> an<01:32:30.600> enigma<01:32:31.110> can<01:32:31.710> I<01:32:31.820> call<01:32:32.820> a<01:32:32.850> contractor 01:32:33.230 --> 01:32:33.240 align:start position:0% it's an enigma can I call a contractor 01:32:33.240 --> 01:32:35.930 align:start position:0% it's an enigma can I call a contractor material<01:32:33.840> to<01:32:34.050> move<01:32:34.230> funds<01:32:34.560> to<01:32:34.830> mint<01:32:35.040> tokens<01:32:35.460> or 01:32:35.930 --> 01:32:35.940 align:start position:0% material to move funds to mint tokens or 01:32:35.940 --> 01:32:40.910 align:start position:0% material to move funds to mint tokens or store<01:32:36.660> records<01:32:36.840> of<01:32:37.740> that<01:32:37.980> sort<01:32:38.250> so<01:32:39.770> I'm<01:32:40.770> going 01:32:40.910 --> 01:32:40.920 align:start position:0% store records of that sort so I'm going 01:32:40.920 --> 01:32:42.410 align:start position:0% store records of that sort so I'm going to<01:32:40.950> talk<01:32:41.130> a<01:32:41.430> bit<01:32:41.490> about<01:32:41.700> the<01:32:41.970> network<01:32:42.240> very 01:32:42.410 --> 01:32:42.420 align:start position:0% to talk a bit about the network very 01:32:42.420 --> 01:32:45.380 align:start position:0% to talk a bit about the network very quickly<01:32:43.520> with<01:32:44.520> their<01:32:44.640> developers<01:32:45.150> have<01:32:45.300> built 01:32:45.380 --> 01:32:45.390 align:start position:0% quickly with their developers have built 01:32:45.390 --> 01:32:47.990 align:start position:0% quickly with their developers have built apps<01:32:45.690> in<01:32:46.080> the<01:32:46.170> deuterium<01:32:46.590> users<01:32:47.550> who<01:32:47.700> interact 01:32:47.990 --> 01:32:48.000 align:start position:0% apps in the deuterium users who interact 01:32:48.000 --> 01:32:51.110 align:start position:0% apps in the deuterium users who interact with<01:32:48.210> these<01:32:48.330> maps<01:32:48.680> and<01:32:49.680> then<01:32:49.920> finally<01:32:50.700> workers 01:32:51.110 --> 01:32:51.120 align:start position:0% with these maps and then finally workers 01:32:51.120 --> 01:32:53.420 align:start position:0% with these maps and then finally workers who<01:32:51.270> execute<01:32:51.690> these<01:32:51.870> tasks<01:32:52.320> these<01:32:52.920> workers 01:32:53.420 --> 01:32:53.430 align:start position:0% who execute these tasks these workers 01:32:53.430 --> 01:32:56.270 align:start position:0% who execute these tasks these workers run<01:32:53.670> into<01:32:54.360> this<01:32:54.450> Jack's<01:32:54.750> devices<01:32:55.230> and<01:32:55.440> that's 01:32:56.270 --> 01:32:56.280 align:start position:0% run into this Jack's devices and that's 01:32:56.280 --> 01:32:57.680 align:start position:0% run into this Jack's devices and that's how<01:32:56.400> the<01:32:56.460> network<01:32:56.730> issues<01:32:57.180> his<01:32:57.300> privacy 01:32:57.680 --> 01:32:57.690 align:start position:0% how the network issues his privacy 01:32:57.690 --> 01:33:00.620 align:start position:0% how the network issues his privacy feature<01:32:58.640> on<01:32:59.640> a<01:32:59.700> high<01:32:59.940> level<01:33:00.000> the<01:33:00.450> white 01:33:00.620 --> 01:33:00.630 align:start position:0% feature on a high level the white 01:33:00.630 --> 01:33:02.450 align:start position:0% feature on a high level the white network<01:33:01.080> works<01:33:01.320> is<01:33:01.560> the<01:33:01.740> the<01:33:01.950> middle<01:33:02.130> thing<01:33:02.340> I 01:33:02.450 --> 01:33:02.460 align:start position:0% network works is the the middle thing I 01:33:02.460 --> 01:33:04.040 align:start position:0% network works is the the middle thing I have<01:33:02.640> there<01:33:02.850> is<01:33:02.970> the<01:33:03.360> secret<01:33:03.600> contract 01:33:04.040 --> 01:33:04.050 align:start position:0% have there is the secret contract 01:33:04.050 --> 01:33:07.730 align:start position:0% have there is the secret contract concept<01:33:04.820> in<01:33:05.820> this<01:33:06.120> network<01:33:06.690> and<01:33:07.590> the 01:33:07.730 --> 01:33:07.740 align:start position:0% concept in this network and the 01:33:07.740 --> 01:33:09.410 align:start position:0% concept in this network and the interesting<01:33:08.070> thing<01:33:08.100> is<01:33:08.370> the<01:33:08.880> inputs<01:33:09.300> are 01:33:09.410 --> 01:33:09.420 align:start position:0% interesting thing is the inputs are 01:33:09.420 --> 01:33:11.270 align:start position:0% interesting thing is the inputs are encrypted<01:33:09.870> and<01:33:09.960> the<01:33:10.170> state<01:33:10.410> is<01:33:10.530> included<01:33:10.890> at 01:33:11.270 --> 01:33:11.280 align:start position:0% encrypted and the state is included at 01:33:11.280 --> 01:33:14.360 align:start position:0% encrypted and the state is included at all<01:33:11.400> times<01:33:11.670> so<01:33:12.390> what<01:33:13.350> happens<01:33:13.740> is<01:33:13.860> the<01:33:14.010> users 01:33:14.360 --> 01:33:14.370 align:start position:0% all times so what happens is the users 01:33:14.370 --> 01:33:16.910 align:start position:0% all times so what happens is the users sends<01:33:14.970> the<01:33:15.060> inputs<01:33:15.450> while<01:33:16.080> you<01:33:16.380> sending<01:33:16.770> the 01:33:16.910 --> 01:33:16.920 align:start position:0% sends the inputs while you sending the 01:33:16.920 --> 01:33:18.790 align:start position:0% sends the inputs while you sending the input<01:33:17.250> they're<01:33:17.460> using<01:33:17.790> our<01:33:17.910> library<01:33:18.180> which 01:33:18.790 --> 01:33:18.800 align:start position:0% input they're using our library which 01:33:18.800 --> 01:33:21.920 align:start position:0% input they're using our library which which<01:33:19.800> ensures<01:33:20.430> the<01:33:20.460> encryption<01:33:21.120> are<01:33:21.480> locally 01:33:21.920 --> 01:33:21.930 align:start position:0% which ensures the encryption are locally 01:33:21.930 --> 01:33:24.500 align:start position:0% which ensures the encryption are locally and<01:33:22.110> that<01:33:22.350> sensitivity<01:33:22.830> to<01:33:23.340> the<01:33:23.400> network<01:33:23.790> then 01:33:24.500 --> 01:33:24.510 align:start position:0% and that sensitivity to the network then 01:33:24.510 --> 01:33:27.530 align:start position:0% and that sensitivity to the network then we<01:33:25.200> have<01:33:25.440> built<01:33:25.680> a<01:33:25.800> p2p<01:33:26.340> network<01:33:26.850> where<01:33:27.150> all 01:33:27.530 --> 01:33:27.540 align:start position:0% we have built a p2p network where all 01:33:27.540 --> 01:33:30.800 align:start position:0% we have built a p2p network where all the<01:33:28.790> basically<01:33:29.790> state<01:33:30.120> is<01:33:30.330> kept<01:33:30.600> that<01:33:30.720> the 01:33:30.800 --> 01:33:30.810 align:start position:0% the basically state is kept that the 01:33:30.810 --> 01:33:34.040 align:start position:0% the basically state is kept that the communication<01:33:31.410> takes<01:33:31.530> place<01:33:32.450> that<01:33:33.450> also<01:33:33.810> is 01:33:34.040 --> 01:33:34.050 align:start position:0% communication takes place that also is 01:33:34.050 --> 01:33:35.690 align:start position:0% communication takes place that also is in<01:33:34.170> people<01:33:34.410> at<01:33:34.470> all<01:33:34.620> times<01:33:34.650> the<01:33:35.130> worker<01:33:35.550> who's 01:33:35.690 --> 01:33:35.700 align:start position:0% in people at all times the worker who's 01:33:35.700 --> 01:33:37.520 align:start position:0% in people at all times the worker who's chosen<01:33:35.970> to<01:33:36.240> work<01:33:36.330> on<01:33:36.540> this<01:33:36.660> has<01:33:36.840> developed 01:33:37.520 --> 01:33:37.530 align:start position:0% chosen to work on this has developed 01:33:37.530 --> 01:33:39.590 align:start position:0% chosen to work on this has developed based<01:33:37.980> on<01:33:38.130> proof<01:33:38.310> of<01:33:38.430> state<01:33:38.640> algorithm<01:33:38.940> has 01:33:39.590 --> 01:33:39.600 align:start position:0% based on proof of state algorithm has 01:33:39.600 --> 01:33:41.810 align:start position:0% based on proof of state algorithm has the<01:33:39.900> ability<01:33:40.290> to<01:33:40.350> decrypt<01:33:40.800> both<01:33:41.160> the<01:33:41.430> inputs 01:33:41.810 --> 01:33:41.820 align:start position:0% the ability to decrypt both the inputs 01:33:41.820 --> 01:33:44.720 align:start position:0% the ability to decrypt both the inputs and<01:33:42.000> the<01:33:42.420> state<01:33:43.200> of<01:33:43.320> the<01:33:43.350> contract<01:33:43.830> do 01:33:44.720 --> 01:33:44.730 align:start position:0% and the state of the contract do 01:33:44.730 --> 01:33:47.900 align:start position:0% and the state of the contract do computation<01:33:45.420> on<01:33:45.510> it<01:33:45.660> and<01:33:46.350> then<01:33:46.740> update<01:33:47.670> the<01:33:47.880> a 01:33:47.900 --> 01:33:47.910 align:start position:0% computation on it and then update the a 01:33:47.910 --> 01:33:50.510 align:start position:0% computation on it and then update the a mistake<01:33:48.390> one<01:33:48.720> cinema<01:33:49.200> state<01:33:49.410> is<01:33:49.500> updated<01:33:50.070> it's 01:33:50.510 --> 01:33:50.520 align:start position:0% mistake one cinema state is updated it's 01:33:50.520 --> 01:33:53.570 align:start position:0% mistake one cinema state is updated it's amazing<01:33:51.060> cryptic<01:33:51.450> it<01:33:51.600> is<01:33:51.840> visible<01:33:52.830> to<01:33:52.890> the 01:33:53.570 --> 01:33:53.580 align:start position:0% amazing cryptic it is visible to the 01:33:53.580 --> 01:33:56.270 align:start position:0% amazing cryptic it is visible to the user<01:33:54.060> who<01:33:54.330> created<01:33:54.810> transaction<01:33:55.530> and<01:33:56.040> as<01:33:56.160> I 01:33:56.270 --> 01:33:56.280 align:start position:0% user who created transaction and as I 01:33:56.280 --> 01:34:00.159 align:start position:0% user who created transaction and as I mentioned<01:33:56.760> we<01:33:57.540> can<01:33:57.780> do<01:33:58.100> computation 01:34:00.159 --> 01:34:00.169 align:start position:0% mentioned we can do computation 01:34:00.169 --> 01:34:02.889 align:start position:0% mentioned we can do computation with<01:34:00.349> precision<01:34:01.669> I<01:34:01.699> was<01:34:02.059> going<01:34:02.209> to<01:34:02.300> focus<01:34:02.510> a 01:34:02.889 --> 01:34:02.899 align:start position:0% with precision I was going to focus a 01:34:02.899 --> 01:34:05.529 align:start position:0% with precision I was going to focus a bit<01:34:03.050> more<01:34:03.110> on<01:34:03.369> like<01:34:04.369> on<01:34:04.550> supplies<01:34:04.969> Enterprise 01:34:05.529 --> 01:34:05.539 align:start position:0% bit more on like on supplies Enterprise 01:34:05.539 --> 01:34:07.270 align:start position:0% bit more on like on supplies Enterprise but<01:34:06.110> I<01:34:06.199> think<01:34:06.409> it's<01:34:06.499> it's<01:34:06.619> it's<01:34:07.070> interesting 01:34:07.270 --> 01:34:07.280 align:start position:0% but I think it's it's it's interesting 01:34:07.280 --> 01:34:10.959 align:start position:0% but I think it's it's it's interesting to<01:34:07.729> show<01:34:07.969> how<01:34:08.659> this<01:34:08.989> can<01:34:09.229> be<01:34:09.439> a<01:34:09.949> use<01:34:10.550> case<01:34:10.760> that 01:34:10.959 --> 01:34:10.969 align:start position:0% to show how this can be a use case that 01:34:10.969 --> 01:34:12.850 align:start position:0% to show how this can be a use case that can<01:34:11.090> be<01:34:11.149> used<01:34:11.360> on<01:34:11.449> public<01:34:11.719> YouTube<01:34:12.139> so<01:34:12.679> what<01:34:12.829> I 01:34:12.850 --> 01:34:12.860 align:start position:0% can be used on public YouTube so what I 01:34:12.860 --> 01:34:14.139 align:start position:0% can be used on public YouTube so what I want<01:34:13.130> to<01:34:13.159> do<01:34:13.309> is<01:34:13.399> I<01:34:13.489> want<01:34:13.639> to<01:34:13.699> talk<01:34:13.820> a<01:34:13.849> bit<01:34:14.119> more 01:34:14.139 --> 01:34:14.149 align:start position:0% want to do is I want to talk a bit more 01:34:14.149 --> 01:34:17.109 align:start position:0% want to do is I want to talk a bit more about<01:34:14.570> like<01:34:14.749> what<01:34:15.079> we're<01:34:15.979> building<01:34:16.189> or<01:34:16.880> what 01:34:17.109 --> 01:34:17.119 align:start position:0% about like what we're building or what 01:34:17.119 --> 01:34:21.339 align:start position:0% about like what we're building or what people<01:34:17.449> are<01:34:17.510> building<01:34:17.899> is<01:34:18.110> the<01:34:19.099> system<01:34:20.349> we 01:34:21.339 --> 01:34:21.349 align:start position:0% people are building is the system we 01:34:21.349 --> 01:34:23.859 align:start position:0% people are building is the system we recently<01:34:21.649> built<01:34:22.159> a<01:34:22.399> coin<01:34:22.880> mixer<01:34:23.300> to<01:34:23.539> achieve 01:34:23.859 --> 01:34:23.869 align:start position:0% recently built a coin mixer to achieve 01:34:23.869 --> 01:34:28.020 align:start position:0% recently built a coin mixer to achieve transaction<01:34:24.829> to<01:34:24.919> privacy<01:34:25.309> material<01:34:26.019> we<01:34:27.019> see 01:34:28.020 --> 01:34:28.030 align:start position:0% transaction to privacy material we see 01:34:28.030 --> 01:34:32.319 align:start position:0% transaction to privacy material we see potentially<01:34:29.030> that<01:34:29.419> tried<01:34:29.659> to<01:34:29.749> do<01:34:29.899> that<01:34:30.639> we<01:34:31.639> we 01:34:32.319 --> 01:34:32.329 align:start position:0% potentially that tried to do that we we 01:34:32.329 --> 01:34:34.239 align:start position:0% potentially that tried to do that we we use<01:34:32.510> our<01:34:32.749> network<01:34:32.929> and<01:34:33.320> see<01:34:33.559> contracts<01:34:34.099> and 01:34:34.239 --> 01:34:34.249 align:start position:0% use our network and see contracts and 01:34:34.249 --> 01:34:36.520 align:start position:0% use our network and see contracts and I'm<01:34:34.309> going<01:34:34.489> to<01:34:34.579> collect<01:34:35.269> encrypted<01:34:36.019> recipient 01:34:36.520 --> 01:34:36.530 align:start position:0% I'm going to collect encrypted recipient 01:34:36.530 --> 01:34:38.589 align:start position:0% I'm going to collect encrypted recipient addresses<01:34:37.039> and<01:34:37.219> then<01:34:37.309> shuffle<01:34:37.699> them<01:34:37.909> in<01:34:38.419> order 01:34:38.589 --> 01:34:38.599 align:start position:0% addresses and then shuffle them in order 01:34:38.599 --> 01:34:41.199 align:start position:0% addresses and then shuffle them in order to<01:34:38.719> achieve<01:34:38.959> transactional<01:34:39.709> privacy<01:34:40.209> there 01:34:41.199 --> 01:34:41.209 align:start position:0% to achieve transactional privacy there 01:34:41.209 --> 01:34:42.879 align:start position:0% to achieve transactional privacy there are<01:34:41.300> a<01:34:41.329> lot<01:34:41.449> of<01:34:41.510> define<01:34:42.019> use<01:34:42.229> cases<01:34:42.499> that<01:34:42.709> are 01:34:42.879 --> 01:34:42.889 align:start position:0% are a lot of define use cases that are 01:34:42.889 --> 01:34:47.469 align:start position:0% are a lot of define use cases that are interested<01:34:43.340> in<01:34:43.369> this<01:34:45.130> there<01:34:46.130> is<01:34:46.159> a<01:34:46.249> lot<01:34:46.519> of<01:34:47.090> use 01:34:47.469 --> 01:34:47.479 align:start position:0% interested in this there is a lot of use 01:34:47.479 --> 01:34:50.439 align:start position:0% interested in this there is a lot of use cases<01:34:47.510> that<01:34:48.229> require<01:34:48.489> options<01:34:49.489> in<01:34:50.090> order<01:34:50.239> to 01:34:50.439 --> 01:34:50.449 align:start position:0% cases that require options in order to 01:34:50.449 --> 01:34:52.449 align:start position:0% cases that require options in order to create<01:34:50.630> efficient<01:34:51.110> marketplaces<01:34:51.769> this<01:34:52.249> could 01:34:52.449 --> 01:34:52.459 align:start position:0% create efficient marketplaces this could 01:34:52.459 --> 01:34:54.189 align:start position:0% create efficient marketplaces this could be<01:34:52.550> things<01:34:52.699> like<01:34:52.849> creating<01:34:53.239> order<01:34:53.419> books<01:34:53.749> or 01:34:54.189 --> 01:34:54.199 align:start position:0% be things like creating order books or 01:34:54.199 --> 01:34:58.989 align:start position:0% be things like creating order books or this<01:34:54.380> could<01:34:54.530> be<01:34:54.649> things<01:34:54.889> like<01:34:57.789> having<01:34:58.789> an 01:34:58.989 --> 01:34:58.999 align:start position:0% this could be things like having an 01:34:58.999 --> 01:35:01.560 align:start position:0% this could be things like having an auction<01:34:59.389> to<01:34:59.539> say<01:34:59.809> like<01:34:59.989> creating<01:35:00.469> a<01:35:00.590> fixed 01:35:01.560 --> 01:35:01.570 align:start position:0% auction to say like creating a fixed 01:35:01.570 --> 01:35:03.750 align:start position:0% auction to say like creating a fixed using<01:35:01.870> the<01:35:02.260> interest<01:35:02.560> swaps<01:35:02.770> are<01:35:03.040> on<01:35:03.370> the 01:35:03.750 --> 01:35:03.760 align:start position:0% using the interest swaps are on the 01:35:03.760 --> 01:35:05.520 align:start position:0% using the interest swaps are on the define<01:35:04.090> ecosystem<01:35:04.630> but<01:35:05.140> there<01:35:05.320> are<01:35:05.380> things 01:35:05.520 --> 01:35:05.530 align:start position:0% define ecosystem but there are things 01:35:05.530 --> 01:35:08.040 align:start position:0% define ecosystem but there are things that<01:35:05.860> are<01:35:06.160> around<01:35:06.310> this<01:35:06.810> discipline<01:35:07.810> of 01:35:08.040 --> 01:35:08.050 align:start position:0% that are around this discipline of 01:35:08.050 --> 01:35:10.950 align:start position:0% that are around this discipline of gaming<01:35:08.760> situations<01:35:09.760> that<01:35:09.940> we<01:35:10.120> see<01:35:10.360> where 01:35:10.950 --> 01:35:10.960 align:start position:0% gaming situations that we see where 01:35:10.960 --> 01:35:13.740 align:start position:0% gaming situations that we see where there's<01:35:11.290> a<01:35:11.350> multiplayer<01:35:12.030> situation<01:35:13.030> a<01:35:13.270> very 01:35:13.740 --> 01:35:13.750 align:start position:0% there's a multiplayer situation a very 01:35:13.750 --> 01:35:15.240 align:start position:0% there's a multiplayer situation a very simple<01:35:14.110> example<01:35:14.200> is<01:35:14.590> about<01:35:14.680> Paper<01:35:15.070> Scissors 01:35:15.240 --> 01:35:15.250 align:start position:0% simple example is about Paper Scissors 01:35:15.250 --> 01:35:17.220 align:start position:0% simple example is about Paper Scissors but<01:35:15.910> I<01:35:15.940> can<01:35:16.120> take<01:35:16.300> it<01:35:16.420> to<01:35:16.480> the<01:35:16.570> next<01:35:16.780> level<01:35:16.870> and 01:35:17.220 --> 01:35:17.230 align:start position:0% but I can take it to the next level and 01:35:17.230 --> 01:35:19.110 align:start position:0% but I can take it to the next level and build<01:35:17.470> a<01:35:17.680> poker<01:35:18.010> game<01:35:18.130> graphically<01:35:18.790> it's 01:35:19.110 --> 01:35:19.120 align:start position:0% build a poker game graphically it's 01:35:19.120 --> 01:35:21.240 align:start position:0% build a poker game graphically it's decentralized<01:35:19.570> and<01:35:20.140> cannot<01:35:20.620> be<01:35:20.770> shut<01:35:20.920> down<01:35:20.980> by 01:35:21.240 --> 01:35:21.250 align:start position:0% decentralized and cannot be shut down by 01:35:21.250 --> 01:35:22.350 align:start position:0% decentralized and cannot be shut down by governments<01:35:21.760> which<01:35:21.940> i<01:35:22.060> think<01:35:22.120> is<01:35:22.330> very 01:35:22.350 --> 01:35:22.360 align:start position:0% governments which i think is very 01:35:22.360 --> 01:35:25.380 align:start position:0% governments which i think is very interesting<01:35:23.760> governance<01:35:24.760> kind<01:35:25.150> of<01:35:25.210> flows 01:35:25.380 --> 01:35:25.390 align:start position:0% interesting governance kind of flows 01:35:25.390 --> 01:35:27.720 align:start position:0% interesting governance kind of flows into<01:35:25.570> it<01:35:25.780> because<01:35:25.990> voting<01:35:26.440> things<01:35:27.370> like<01:35:27.550> that 01:35:27.720 --> 01:35:27.730 align:start position:0% into it because voting things like that 01:35:27.730 --> 01:35:30.750 align:start position:0% into it because voting things like that were<01:35:28.060> commenced<01:35:28.810> reveals<01:35:29.170> can<01:35:30.130> use<01:35:30.640> the 01:35:30.750 --> 01:35:30.760 align:start position:0% were commenced reveals can use the 01:35:30.760 --> 01:35:36.270 align:start position:0% were commenced reveals can use the benefit<01:35:31.090> from<01:35:31.270> it<01:35:31.860> and<01:35:32.860> and<01:35:33.400> that's<01:35:34.020> the<01:35:35.280> the 01:35:36.270 --> 01:35:36.280 align:start position:0% benefit from it and and that's the the 01:35:36.280 --> 01:35:37.590 align:start position:0% benefit from it and and that's the the interest<01:35:36.700> and<01:35:36.820> interaction<01:35:37.270> we<01:35:37.420> were 01:35:37.590 --> 01:35:37.600 align:start position:0% interest and interaction we were 01:35:37.600 --> 01:35:39.870 align:start position:0% interest and interaction we were primarily<01:35:37.840> seen<01:35:38.380> in<01:35:38.680> the<01:35:39.280> in<01:35:39.550> the<01:35:39.730> public 01:35:39.870 --> 01:35:39.880 align:start position:0% primarily seen in the in the public 01:35:39.880 --> 01:35:42.690 align:start position:0% primarily seen in the in the public YouTube<01:35:40.330> and<01:35:41.230> level<01:35:41.620> I<01:35:41.800> think<01:35:42.190> one<01:35:42.580> thing 01:35:42.690 --> 01:35:42.700 align:start position:0% YouTube and level I think one thing 01:35:42.700 --> 01:35:45.330 align:start position:0% YouTube and level I think one thing that's<01:35:42.850> interesting<01:35:43.380> for<01:35:44.380> the<01:35:44.980> enterprise 01:35:45.330 --> 01:35:45.340 align:start position:0% that's interesting for the enterprise 01:35:45.340 --> 01:35:48.330 align:start position:0% that's interesting for the enterprise water<01:35:45.640> and<01:35:45.910> ecosystem<01:35:46.480> s<01:35:46.740> and<01:35:47.740> this<01:35:48.010> may<01:35:48.310> be 01:35:48.330 --> 01:35:48.340 align:start position:0% water and ecosystem s and this may be 01:35:48.340 --> 01:35:51.390 align:start position:0% water and ecosystem s and this may be sounded<01:35:48.910> at<01:35:49.060> both<01:35:49.240> but<01:35:49.570> I<01:35:50.080> think<01:35:50.920> it's<01:35:51.010> a<01:35:51.130> point 01:35:51.390 --> 01:35:51.400 align:start position:0% sounded at both but I think it's a point 01:35:51.400 --> 01:35:51.960 align:start position:0% sounded at both but I think it's a point worth<01:35:51.580> making 01:35:51.960 --> 01:35:51.970 align:start position:0% worth making 01:35:51.970 --> 01:35:53.610 align:start position:0% worth making I<01:35:52.090> don't<01:35:52.270> think<01:35:52.570> personally<01:35:53.320> the<01:35:53.440> cure 01:35:53.610 --> 01:35:53.620 align:start position:0% I don't think personally the cure 01:35:53.620 --> 01:35:55.650 align:start position:0% I don't think personally the cure identified<01:35:54.160> merchants<01:35:54.660> significantly 01:35:55.650 --> 01:35:55.660 align:start position:0% identified merchants significantly 01:35:55.660 --> 01:36:01.140 align:start position:0% identified merchants significantly improve<01:35:57.090> the<01:35:59.160> databases<01:36:00.160> and<01:36:00.280> the<01:36:00.820> reason<01:36:01.120> for 01:36:01.140 --> 01:36:01.150 align:start position:0% improve the databases and the reason for 01:36:01.150 --> 01:36:03.960 align:start position:0% improve the databases and the reason for that<01:36:01.330> is<01:36:01.690> primarily<01:36:02.320> about<01:36:02.560> privacy<01:36:02.980> we<01:36:03.760> have 01:36:03.960 --> 01:36:03.970 align:start position:0% that is primarily about privacy we have 01:36:03.970 --> 01:36:06.030 align:start position:0% that is primarily about privacy we have a<01:36:04.000> lot<01:36:04.270> of<01:36:04.380> consortium<01:36:05.380> of<01:36:05.530> chains<01:36:05.800> which 01:36:06.030 --> 01:36:06.040 align:start position:0% a lot of consortium of chains which 01:36:06.040 --> 01:36:09.800 align:start position:0% a lot of consortium of chains which creates<01:36:06.400> further<01:36:06.640> data<01:36:06.820> silos<01:36:07.330> and<01:36:07.710> have<01:36:08.710> the 01:36:09.800 --> 01:36:09.810 align:start position:0% creates further data silos and have the 01:36:09.810 --> 01:36:12.570 align:start position:0% creates further data silos and have the ability<01:36:10.810> to<01:36:11.110> tap<01:36:11.530> into<01:36:11.830> network<01:36:12.220> effects 01:36:12.570 --> 01:36:12.580 align:start position:0% ability to tap into network effects 01:36:12.580 --> 01:36:17.010 align:start position:0% ability to tap into network effects that's<01:36:13.270> a<01:36:13.950> great<01:36:14.950> value<01:36:15.480> when<01:36:16.480> something<01:36:16.930> like 01:36:17.010 --> 01:36:17.020 align:start position:0% that's a great value when something like 01:36:17.020 --> 01:36:20.220 align:start position:0% that's a great value when something like anymore<01:36:17.530> this<01:36:18.280> can<01:36:19.090> be<01:36:19.270> addressed<01:36:19.600> trying<01:36:19.870> to 01:36:20.220 --> 01:36:20.230 align:start position:0% anymore this can be addressed trying to 01:36:20.230 --> 01:36:23.280 align:start position:0% anymore this can be addressed trying to address<01:36:20.530> because<01:36:20.980> now<01:36:21.610> you<01:36:21.670> can<01:36:22.000> have<01:36:22.290> an 01:36:23.280 --> 01:36:23.290 align:start position:0% address because now you can have an 01:36:23.290 --> 01:36:26.340 align:start position:0% address because now you can have an actual<01:36:23.890> blockchain<01:36:24.520> where<01:36:25.240> you<01:36:25.780> know<01:36:25.930> you<01:36:26.230> can 01:36:26.340 --> 01:36:26.350 align:start position:0% actual blockchain where you know you can 01:36:26.350 --> 01:36:27.980 align:start position:0% actual blockchain where you know you can connect<01:36:26.680> to<01:36:26.770> different<01:36:26.890> ball<01:36:27.250> chains<01:36:27.550> and 01:36:27.980 --> 01:36:27.990 align:start position:0% connect to different ball chains and 01:36:27.990 --> 01:36:29.690 align:start position:0% connect to different ball chains and parties<01:36:28.990> who<01:36:29.200> have 01:36:29.690 --> 01:36:29.700 align:start position:0% parties who have 01:36:29.700 --> 01:36:31.490 align:start position:0% parties who have business<01:36:30.240> interests<01:36:30.630> can<01:36:30.900> attract<01:36:31.260> each 01:36:31.490 --> 01:36:31.500 align:start position:0% business interests can attract each 01:36:31.500 --> 01:36:33.830 align:start position:0% business interests can attract each other<01:36:31.650> without<01:36:32.370> revealing<01:36:32.970> anything<01:36:33.420> both 01:36:33.830 --> 01:36:33.840 align:start position:0% other without revealing anything both 01:36:33.840 --> 01:36:37.880 align:start position:0% other without revealing anything both from<01:36:34.050> their<01:36:34.200> business<01:36:34.530> logic<01:36:35.040> and<01:36:36.170> and<01:36:37.170> you 01:36:37.880 --> 01:36:37.890 align:start position:0% from their business logic and and you 01:36:37.890 --> 01:36:38.510 align:start position:0% from their business logic and and you know 01:36:38.510 --> 01:36:38.520 align:start position:0% know 01:36:38.520 --> 01:36:40.670 align:start position:0% know two<01:36:38.640> contracts<01:36:39.360> so<01:36:39.930> we<01:36:40.260> think<01:36:40.410> this<01:36:40.560> is 01:36:40.670 --> 01:36:40.680 align:start position:0% two contracts so we think this is 01:36:40.680 --> 01:36:43.330 align:start position:0% two contracts so we think this is interesting<01:36:41.120> going<01:36:42.120> forward<01:36:42.720> excite<01:36:43.140> to 01:36:43.330 --> 01:36:43.340 align:start position:0% interesting going forward excite to 01:36:43.340 --> 01:36:47.180 align:start position:0% interesting going forward excite to contribute<01:36:44.340> to<01:36:44.490> expects<01:36:44.910> the<01:36:45.420> e<01:36:45.500> -<01:36:46.500> relational 01:36:47.180 --> 01:36:47.190 align:start position:0% contribute to expects the e - relational 01:36:47.190 --> 01:36:50.360 align:start position:0% contribute to expects the e - relational aspects<01:36:47.600> new<01:36:48.600> theory<01:36:48.900> on<01:36:49.050> how<01:36:49.260> to<01:36:49.370> share 01:36:50.360 --> 01:36:50.370 align:start position:0% aspects new theory on how to share 01:36:50.370 --> 01:37:09.200 align:start position:0% aspects new theory on how to share knowledge<01:36:50.640> and<01:36:50.850> afters<01:36:51.210> stay<01:36:52.340> foolish<01:37:08.150> so<01:37:09.150> I 01:37:09.200 --> 01:37:09.210 align:start position:0% knowledge and afters stay foolish so I 01:37:09.210 --> 01:37:12.170 align:start position:0% knowledge and afters stay foolish so I think<01:37:09.270> a<01:37:09.570> little<01:37:10.040> we<01:37:11.040> started<01:37:11.430> I<01:37:11.520> was<01:37:11.670> quite 01:37:12.170 --> 01:37:12.180 align:start position:0% think a little we started I was quite 01:37:12.180 --> 01:37:14.330 align:start position:0% think a little we started I was quite worried<01:37:12.510> that<01:37:12.690> we<01:37:12.840> have<01:37:13.020> so<01:37:13.800> many<01:37:13.920> people 01:37:14.330 --> 01:37:14.340 align:start position:0% worried that we have so many people 01:37:14.340 --> 01:37:23.870 align:start position:0% worried that we have so many people present<01:37:19.940> that<01:37:20.940> was<01:37:21.920> basically<01:37:22.920> the<01:37:23.040> session 01:37:23.870 --> 01:37:23.880 align:start position:0% present that was basically the session 01:37:23.880 --> 01:37:32.870 align:start position:0% present that was basically the session and<01:37:24.620> thanks<01:37:25.620> to<01:37:25.710> everyone<01:37:25.950> you<01:37:26.940> know<01:37:29.450> and<01:37:31.880> the 01:37:32.870 --> 01:37:32.880 align:start position:0% and thanks to everyone you know and the 01:37:32.880 --> 01:37:35.450 align:start position:0% and thanks to everyone you know and the main<01:37:33.090> point<01:37:33.360> is<01:37:33.480> that<01:37:33.510> you<01:37:33.990> know<01:37:34.170> the<01:37:34.860> facts 01:37:35.450 --> 01:37:35.460 align:start position:0% main point is that you know the facts 01:37:35.460 --> 01:37:39.650 align:start position:0% main point is that you know the facts are<01:37:35.820> mature<01:37:36.360> and<01:37:37.340> there<01:37:38.340> is<01:37:38.520> he<01:37:39.090> heard<01:37:39.450> about 01:37:39.650 --> 01:37:39.660 align:start position:0% are mature and there is he heard about 01:37:39.660 --> 01:37:43.940 align:start position:0% are mature and there is he heard about this<01:37:39.810> hyper<01:37:40.020> later<01:37:40.320> along<01:37:40.860> its<01:37:41.640> basically 01:37:43.940 --> 01:37:43.950 align:start position:0% this hyper later along its basically 01:37:43.950 --> 01:37:47.720 align:start position:0% this hyper later along its basically eeeh<01:37:44.460> cannot<01:37:44.970> hold<01:37:45.240> saw<01:37:46.110> sports<01:37:46.470> so<01:37:46.860> so<01:37:47.550> this 01:37:47.720 --> 01:37:47.730 align:start position:0% eeeh cannot hold saw sports so so this 01:37:47.730 --> 01:37:52.930 align:start position:0% eeeh cannot hold saw sports so so this work<01:37:48.000> group<01:37:48.150> was<01:37:48.560> set<01:37:49.560> up<01:37:49.590> as<01:37:50.100> a<01:37:51.030> little 01:37:52.930 --> 01:37:52.940 align:start position:0% work group was set up as a little 01:37:52.940 --> 01:37:56.180 align:start position:0% work group was set up as a little Foundation<01:37:53.940> and<01:37:54.180> that's<01:37:54.750> why<01:37:54.960> you<01:37:55.020> know<01:37:55.320> all 01:37:56.180 --> 01:37:56.190 align:start position:0% Foundation and that's why you know all 01:37:56.190 --> 01:37:57.950 align:start position:0% Foundation and that's why you know all of<01:37:56.430> this<01:37:56.700> code<01:37:57.000> that<01:37:57.030> we're<01:37:57.450> talking<01:37:57.690> about 01:37:57.950 --> 01:37:57.960 align:start position:0% of this code that we're talking about 01:37:57.960 --> 01:38:01.520 align:start position:0% of this code that we're talking about will<01:37:58.230> be<01:37:58.410> a<01:37:58.680> place<01:37:59.220> and<01:38:00.020> there's<01:38:01.020> a<01:38:01.140> community 01:38:01.520 --> 01:38:01.530 align:start position:0% will be a place and there's a community 01:38:01.530 --> 01:38:03.200 align:start position:0% will be a place and there's a community building<01:38:01.740> they're<01:38:02.010> already<01:38:02.250> there<01:38:02.520> like<01:38:02.730> 15 01:38:03.200 --> 01:38:03.210 align:start position:0% building they're already there like 15 01:38:03.210 --> 01:38:06.980 align:start position:0% building they're already there like 15 to<01:38:03.360> 16<01:38:03.720> companies<01:38:03.990> they're<01:38:05.990> actually 01:38:06.980 --> 01:38:06.990 align:start position:0% to 16 companies they're actually 01:38:06.990 --> 01:38:09.110 align:start position:0% to 16 companies they're actually contributing<01:38:07.170> forth<01:38:07.860> in<01:38:08.070> those<01:38:08.190> cases<01:38:08.490> and<01:38:08.820> to 01:38:09.110 --> 01:38:09.120 align:start position:0% contributing forth in those cases and to 01:38:09.120 --> 01:38:22.670 align:start position:0% contributing forth in those cases and to the<01:38:09.240> spec<01:38:18.020> and<01:38:19.020> then<01:38:19.740> the<01:38:20.310> things<01:38:21.500> and<01:38:22.500> the 01:38:22.670 --> 01:38:22.680 align:start position:0% the spec and then the things and the 01:38:22.680 --> 01:38:24.770 align:start position:0% the spec and then the things and the thing<01:38:22.860> is<01:38:22.950> like<01:38:23.100> you<01:38:23.130> know<01:38:23.310> the<01:38:23.970> framework 01:38:24.770 --> 01:38:24.780 align:start position:0% thing is like you know the framework 01:38:24.780 --> 01:38:27.920 align:start position:0% thing is like you know the framework that<01:38:25.710> we<01:38:26.400> talked<01:38:26.940> about<01:38:27.060> we<01:38:27.450> wanted<01:38:27.780> to 01:38:27.920 --> 01:38:27.930 align:start position:0% that we talked about we wanted to 01:38:27.930 --> 01:38:30.650 align:start position:0% that we talked about we wanted to basically<01:38:28.050> do<01:38:28.980> it<01:38:29.130> here<01:38:29.580> but<01:38:29.850> given<01:38:30.510> the 01:38:30.650 --> 01:38:30.660 align:start position:0% basically do it here but given the 01:38:30.660 --> 01:38:33.100 align:start position:0% basically do it here but given the situation<01:38:31.140> we<01:38:31.500> couldn't<01:38:31.770> do<01:38:31.830> it<01:38:31.980> so<01:38:32.220> he<01:38:32.730> has 01:38:33.100 --> 01:38:33.110 align:start position:0% situation we couldn't do it so he has 01:38:33.110 --> 01:38:35.930 align:start position:0% situation we couldn't do it so he has the<01:38:34.110> whole<01:38:34.290> framework<01:38:34.590> on<01:38:35.010> the<01:38:35.040> USB<01:38:35.430> sticks 01:38:35.930 --> 01:38:35.940 align:start position:0% the whole framework on the USB sticks 01:38:35.940 --> 01:38:38.530 align:start position:0% the whole framework on the USB sticks [Music] 01:38:38.530 --> 01:38:38.540 align:start position:0% [Music] 01:38:38.540 --> 01:38:41.660 align:start position:0% [Music] and<01:38:39.620> you<01:38:40.620> know<01:38:40.770> they<01:38:40.950> can<01:38:41.100> just<01:38:41.250> pass<01:38:41.460> it 01:38:41.660 --> 01:38:41.670 align:start position:0% and you know they can just pass it 01:38:41.670 --> 01:38:47.300 align:start position:0% and you know they can just pass it around<01:38:41.790> that<01:38:42.230> people<01:38:43.230> can<01:38:43.530> just 01:38:47.300 --> 01:38:47.310 align:start position:0% 01:38:47.310 --> 01:38:48.700 align:start position:0% [Music] 01:38:48.700 --> 01:38:48.710 align:start position:0% [Music] 01:38:48.710 --> 01:38:55.060 align:start position:0% [Music] thank<01:38:49.400> you 01:38:55.060 --> 01:38:55.070 align:start position:0% 01:38:55.070 --> 01:38:59.520 align:start position:0% [Applause]