WEBVTT Kind: captions Language: en 00:00:05.070 --> 00:00:14.910 align:start position:0% [Music] 00:00:14.910 --> 00:00:14.920 align:start position:0% 00:00:14.920 --> 00:00:19.670 align:start position:0% [Music] 00:00:19.670 --> 00:00:19.680 align:start position:0% 00:00:19.680 --> 00:00:23.109 align:start position:0% all<00:00:19.920> right<00:00:20.920> uh<00:00:21.800> thanks<00:00:22.000> a<00:00:22.119> lot<00:00:22.279> for 00:00:23.109 --> 00:00:23.119 align:start position:0% all right uh thanks a lot for 00:00:23.119 --> 00:00:26.310 align:start position:0% all right uh thanks a lot for coming<00:00:24.119> thanks<00:00:24.320> a<00:00:24.439> lot<00:00:24.680> to<00:00:24.880> Devcon<00:00:25.400> for<00:00:25.560> having 00:00:26.310 --> 00:00:26.320 align:start position:0% coming thanks a lot to Devcon for having 00:00:26.320 --> 00:00:30.070 align:start position:0% coming thanks a lot to Devcon for having me<00:00:27.320> um<00:00:28.119> first<00:00:28.439> things<00:00:28.840> first<00:00:29.199> this<00:00:29.320> is<00:00:29.519> my 00:00:30.070 --> 00:00:30.080 align:start position:0% me um first things first this is my 00:00:30.080 --> 00:00:32.630 align:start position:0% me um first things first this is my understanding<00:00:30.400> it's<00:00:30.519> not<00:00:30.679> the<00:00:30.840> official<00:00:31.320> IBM 00:00:32.630 --> 00:00:32.640 align:start position:0% understanding it's not the official IBM 00:00:32.640 --> 00:00:36.389 align:start position:0% understanding it's not the official IBM line<00:00:33.640> and<00:00:33.960> I'll<00:00:34.719> be<00:00:34.920> talking<00:00:35.280> about<00:00:36.120> the 00:00:36.389 --> 00:00:36.399 align:start position:0% line and I'll be talking about the 00:00:36.399 --> 00:00:40.110 align:start position:0% line and I'll be talking about the exploration<00:00:37.120> project<00:00:37.480> MTN<00:00:38.320> it's<00:00:38.559> not<00:00:38.840> a 00:00:40.110 --> 00:00:40.120 align:start position:0% exploration project MTN it's not a 00:00:40.120 --> 00:00:44.869 align:start position:0% exploration project MTN it's not a product<00:00:41.120> it's<00:00:41.280> a<00:00:41.520> research 00:00:44.869 --> 00:00:44.879 align:start position:0% 00:00:44.879 --> 00:00:48.229 align:start position:0% project<00:00:45.879> and<00:00:46.480> this<00:00:46.600> is<00:00:46.960> basically<00:00:47.960> how<00:00:48.079> it 00:00:48.229 --> 00:00:48.239 align:start position:0% project and this is basically how it 00:00:48.239 --> 00:00:50.950 align:start position:0% project and this is basically how it mostly 00:00:50.950 --> 00:00:50.960 align:start position:0% 00:00:50.960 --> 00:00:55.110 align:start position:0% looks<00:00:51.960> so<00:00:52.399> the<00:00:52.520> team<00:00:52.800> MTM<00:00:53.600> is<00:00:54.239> uh<00:00:54.559> sponsored<00:00:55.000> by 00:00:55.110 --> 00:00:55.120 align:start position:0% looks so the team MTM is uh sponsored by 00:00:55.120 --> 00:00:57.630 align:start position:0% looks so the team MTM is uh sponsored by MC<00:00:55.559> Divine<00:00:56.559> who's<00:00:56.800> the<00:00:56.920> vice<00:00:57.160> president<00:00:57.440> for 00:00:57.630 --> 00:00:57.640 align:start position:0% MC Divine who's the vice president for 00:00:57.640 --> 00:01:00.110 align:start position:0% MC Divine who's the vice president for cloud<00:00:57.879> Innovation<00:00:58.199> at<00:00:58.359> IBM<00:00:58.719> and<00:00:58.840> it's<00:00:59.039> run<00:01:00.000> by 00:01:00.110 --> 00:01:00.120 align:start position:0% cloud Innovation at IBM and it's run by 00:01:00.120 --> 00:01:02.430 align:start position:0% cloud Innovation at IBM and it's run by Egan<00:01:00.359> Ford<00:01:00.719> a<00:01:00.879> distinguished<00:01:01.320> engineer<00:01:01.840> who's 00:01:02.430 --> 00:01:02.440 align:start position:0% Egan Ford a distinguished engineer who's 00:01:02.440 --> 00:01:06.030 align:start position:0% Egan Ford a distinguished engineer who's uh<00:01:02.840> working<00:01:03.199> 24/7<00:01:03.879> in<00:01:04.000> the<00:01:04.519> moment<00:01:05.519> um<00:01:05.720> pushing 00:01:06.030 --> 00:01:06.040 align:start position:0% uh working 24/7 in the moment um pushing 00:01:06.040 --> 00:01:07.830 align:start position:0% uh working 24/7 in the moment um pushing this<00:01:06.200> and<00:01:06.320> also<00:01:06.560> pushing<00:01:06.840> this<00:01:07.000> within<00:01:07.280> IBM 00:01:07.830 --> 00:01:07.840 align:start position:0% this and also pushing this within IBM 00:01:07.840 --> 00:01:09.390 align:start position:0% this and also pushing this within IBM that's<00:01:08.080> that's<00:01:08.240> the<00:01:08.360> important<00:01:08.799> part<00:01:08.960> to 00:01:09.390 --> 00:01:09.400 align:start position:0% that's that's the important part to 00:01:09.400 --> 00:01:14.270 align:start position:0% that's that's the important part to understand<00:01:09.920> there<00:01:10.920> and<00:01:11.439> uh<00:01:11.640> with<00:01:11.840> r<00:01:12.360> lme<00:01:13.360> um 00:01:14.270 --> 00:01:14.280 align:start position:0% understand there and uh with r lme um 00:01:14.280 --> 00:01:16.590 align:start position:0% understand there and uh with r lme um driving<00:01:14.640> the<00:01:14.799> bus<00:01:15.000> and<00:01:15.439> 12<00:01:15.759> Engineers<00:01:16.479> that 00:01:16.590 --> 00:01:16.600 align:start position:0% driving the bus and 12 Engineers that 00:01:16.600 --> 00:01:18.710 align:start position:0% driving the bus and 12 Engineers that are<00:01:16.759> working<00:01:17.080> on<00:01:17.320> this 00:01:18.710 --> 00:01:18.720 align:start position:0% are working on this 00:01:18.720 --> 00:01:22.270 align:start position:0% are working on this project<00:01:19.720> I'm<00:01:20.000> Henning<00:01:20.320> d<00:01:21.320> uh<00:01:21.479> I'm<00:01:21.600> a<00:01:21.880> senior 00:01:22.270 --> 00:01:22.280 align:start position:0% project I'm Henning d uh I'm a senior 00:01:22.280 --> 00:01:24.270 align:start position:0% project I'm Henning d uh I'm a senior programmer<00:01:22.920> at<00:01:23.119> the<00:01:23.280> blockchain<00:01:23.680> group<00:01:23.960> at 00:01:24.270 --> 00:01:24.280 align:start position:0% programmer at the blockchain group at 00:01:24.280 --> 00:01:27.990 align:start position:0% programmer at the blockchain group at IBM<00:01:25.280> and<00:01:25.640> I<00:01:25.799> have<00:01:26.400> prior<00:01:27.119> experience<00:01:27.799> for 00:01:27.990 --> 00:01:28.000 align:start position:0% IBM and I have prior experience for 00:01:28.000 --> 00:01:30.789 align:start position:0% IBM and I have prior experience for example<00:01:28.320> in<00:01:28.479> distributed<00:01:29.000> databases<00:01:30.360> which 00:01:30.789 --> 00:01:30.799 align:start position:0% example in distributed databases which 00:01:30.799 --> 00:01:33.670 align:start position:0% example in distributed databases which come<00:01:31.040> in<00:01:31.640> quite<00:01:32.000> handy<00:01:32.600> sometimes<00:01:32.920> in<00:01:33.240> this 00:01:33.670 --> 00:01:33.680 align:start position:0% come in quite handy sometimes in this 00:01:33.680 --> 00:01:36.030 align:start position:0% come in quite handy sometimes in this particular<00:01:34.240> field<00:01:35.240> but<00:01:35.399> also<00:01:35.640> with<00:01:35.840> high 00:01:36.030 --> 00:01:36.040 align:start position:0% particular field but also with high 00:01:36.040 --> 00:01:38.630 align:start position:0% particular field but also with high velocity<00:01:36.600> and<00:01:37.200> scalability<00:01:38.200> as<00:01:38.399> these 00:01:38.630 --> 00:01:38.640 align:start position:0% velocity and scalability as these 00:01:38.640 --> 00:01:40.670 align:start position:0% velocity and scalability as these problems<00:01:38.960> are<00:01:39.200> of<00:01:39.399> course<00:01:40.040> nothing<00:01:40.320> new<00:01:40.560> in 00:01:40.670 --> 00:01:40.680 align:start position:0% problems are of course nothing new in 00:01:40.680 --> 00:01:43.789 align:start position:0% problems are of course nothing new in the<00:01:40.759> world<00:01:40.960> of<00:01:41.119> distributed 00:01:43.789 --> 00:01:43.799 align:start position:0% 00:01:43.799 --> 00:01:48.030 align:start position:0% databases<00:01:44.799> so<00:01:45.719> MTN<00:01:46.719> is<00:01:47.040> an<00:01:47.240> acronym<00:01:47.640> for 00:01:48.030 --> 00:01:48.040 align:start position:0% databases so MTN is an acronym for 00:01:48.040 --> 00:01:49.510 align:start position:0% databases so MTN is an acronym for multiplying<00:01:48.640> things 00:01:49.510 --> 00:01:49.520 align:start position:0% multiplying things 00:01:49.520 --> 00:01:52.789 align:start position:0% multiplying things needlessly<00:01:50.520> and<00:01:51.000> uh<00:01:51.320> this<00:01:51.439> was<00:01:51.600> a<00:01:51.799> pun<00:01:52.680> a 00:01:52.789 --> 00:01:52.799 align:start position:0% needlessly and uh this was a pun a 00:01:52.799 --> 00:01:55.190 align:start position:0% needlessly and uh this was a pun a little<00:01:52.960> bit<00:01:53.119> of<00:01:53.280> how<00:01:53.479> blockchain<00:01:54.040> works<00:01:55.040> and 00:01:55.190 --> 00:01:55.200 align:start position:0% little bit of how blockchain works and 00:01:55.200 --> 00:01:57.469 align:start position:0% little bit of how blockchain works and maybe<00:01:55.399> it's<00:01:55.520> not<00:01:55.680> quite<00:01:55.880> that<00:01:56.039> needless<00:01:56.520> right 00:01:57.469 --> 00:01:57.479 align:start position:0% maybe it's not quite that needless right 00:01:57.479 --> 00:02:01.149 align:start position:0% maybe it's not quite that needless right uh<00:01:58.479> and<00:01:58.600> it's<00:01:58.759> really<00:01:58.960> about<00:01:59.240> Aon<00:02:00.200> processing 00:02:01.149 --> 00:02:01.159 align:start position:0% uh and it's really about Aon processing 00:02:01.159 --> 00:02:03.670 align:start position:0% uh and it's really about Aon processing communication<00:02:01.759> and<00:02:02.000> coordination<00:02:03.000> between 00:02:03.670 --> 00:02:03.680 align:start position:0% communication and coordination between 00:02:03.680 --> 00:02:06.670 align:start position:0% communication and coordination between the<00:02:03.880> edge<00:02:04.840> and<00:02:05.000> the 00:02:06.670 --> 00:02:06.680 align:start position:0% the edge and the 00:02:06.680 --> 00:02:09.869 align:start position:0% the edge and the cloud<00:02:07.680> so<00:02:08.479> where<00:02:08.640> we're<00:02:08.879> at<00:02:09.399> we<00:02:09.520> saw<00:02:09.720> this 00:02:09.869 --> 00:02:09.879 align:start position:0% cloud so where we're at we saw this 00:02:09.879 --> 00:02:12.110 align:start position:0% cloud so where we're at we saw this diagram<00:02:10.319> before<00:02:10.720> today<00:02:11.039> even<00:02:11.319> I<00:02:11.480> think<00:02:12.000> uh 00:02:12.110 --> 00:02:12.120 align:start position:0% diagram before today even I think uh 00:02:12.120 --> 00:02:15.110 align:start position:0% diagram before today even I think uh we're<00:02:12.400> at<00:02:12.640> at<00:02:12.760> a<00:02:13.640> historic<00:02:14.120> explosion<00:02:14.720> of 00:02:15.110 --> 00:02:15.120 align:start position:0% we're at at a historic explosion of 00:02:15.120 --> 00:02:17.750 align:start position:0% we're at at a historic explosion of calculation<00:02:15.760> power<00:02:16.000> of<00:02:16.200> processing<00:02:16.760> power 00:02:17.750 --> 00:02:17.760 align:start position:0% calculation power of processing power 00:02:17.760 --> 00:02:19.150 align:start position:0% calculation power of processing power and<00:02:17.879> this<00:02:18.000> is<00:02:18.160> of<00:02:18.319> course<00:02:18.640> driving<00:02:19.040> the 00:02:19.150 --> 00:02:19.160 align:start position:0% and this is of course driving the 00:02:19.160 --> 00:02:21.309 align:start position:0% and this is of course driving the internet<00:02:19.519> of<00:02:19.680> things<00:02:20.080> because<00:02:20.360> more<00:02:20.519> and<00:02:20.680> more 00:02:21.309 --> 00:02:21.319 align:start position:0% internet of things because more and more 00:02:21.319 --> 00:02:25.030 align:start position:0% internet of things because more and more small<00:02:21.680> devices<00:02:22.120> are<00:02:22.280> becoming<00:02:22.599> more<00:02:22.760> and<00:02:22.879> more 00:02:25.030 --> 00:02:25.040 align:start position:0% small devices are becoming more and more 00:02:25.040 --> 00:02:29.110 align:start position:0% small devices are becoming more and more intelligent<00:02:26.480> iot<00:02:27.480> as<00:02:27.680> a<00:02:27.920> phomen<00:02:28.440> is<00:02:28.720> actually 00:02:29.110 --> 00:02:29.120 align:start position:0% intelligent iot as a phomen is actually 00:02:29.120 --> 00:02:30.430 align:start position:0% intelligent iot as a phomen is actually already<00:02:29.560> here 00:02:30.430 --> 00:02:30.440 align:start position:0% already here 00:02:30.440 --> 00:02:32.270 align:start position:0% already here um<00:02:30.599> there<00:02:30.680> are<00:02:31.040> huge<00:02:31.360> success<00:02:31.720> stories<00:02:32.040> in<00:02:32.160> the 00:02:32.270 --> 00:02:32.280 align:start position:0% um there are huge success stories in the 00:02:32.280 --> 00:02:34.910 align:start position:0% um there are huge success stories in the industry<00:02:33.120> for<00:02:33.280> example<00:02:33.680> jet<00:02:33.920> engines<00:02:34.519> the<00:02:34.640> way 00:02:34.910 --> 00:02:34.920 align:start position:0% industry for example jet engines the way 00:02:34.920 --> 00:02:38.110 align:start position:0% industry for example jet engines the way that<00:02:35.080> they<00:02:35.200> are<00:02:36.200> checked<00:02:37.000> every<00:02:37.239> second<00:02:37.640> and 00:02:38.110 --> 00:02:38.120 align:start position:0% that they are checked every second and 00:02:38.120 --> 00:02:40.589 align:start position:0% that they are checked every second and uh<00:02:38.360> traced<00:02:38.879> and<00:02:39.080> tracked<00:02:39.440> and<00:02:40.159> uh<00:02:40.280> the<00:02:40.400> way 00:02:40.589 --> 00:02:40.599 align:start position:0% uh traced and tracked and uh the way 00:02:40.599 --> 00:02:42.630 align:start position:0% uh traced and tracked and uh the way that<00:02:41.159> uh<00:02:41.319> a<00:02:41.440> new<00:02:41.640> business<00:02:41.920> model<00:02:42.239> basically 00:02:42.630 --> 00:02:42.640 align:start position:0% that uh a new business model basically 00:02:42.640 --> 00:02:44.830 align:start position:0% that uh a new business model basically has<00:02:42.800> evolved<00:02:43.200> from<00:02:43.400> the<00:02:43.560> way<00:02:43.760> that<00:02:44.400> they<00:02:44.560> are 00:02:44.830 --> 00:02:44.840 align:start position:0% has evolved from the way that they are 00:02:44.840 --> 00:02:47.229 align:start position:0% has evolved from the way that they are constantly<00:02:45.560> online<00:02:46.560> that<00:02:46.680> is<00:02:46.840> something<00:02:47.120> that 00:02:47.229 --> 00:02:47.239 align:start position:0% constantly online that is something that 00:02:47.239 --> 00:02:49.910 align:start position:0% constantly online that is something that is<00:02:47.319> a<00:02:47.480> reality<00:02:48.000> now<00:02:48.840> there<00:02:48.920> are<00:02:49.200> also 00:02:49.910 --> 00:02:49.920 align:start position:0% is a reality now there are also 00:02:49.920 --> 00:02:51.630 align:start position:0% is a reality now there are also disappointments<00:02:50.720> where<00:02:50.920> for<00:02:51.080> example<00:02:51.400> in<00:02:51.519> the 00:02:51.630 --> 00:02:51.640 align:start position:0% disappointments where for example in the 00:02:51.640 --> 00:02:53.910 align:start position:0% disappointments where for example in the consumer<00:02:52.080> sector<00:02:52.560> things<00:02:52.840> didn't<00:02:53.360> pick<00:02:53.599> up 00:02:53.910 --> 00:02:53.920 align:start position:0% consumer sector things didn't pick up 00:02:53.920 --> 00:02:55.229 align:start position:0% consumer sector things didn't pick up the<00:02:54.080> way<00:02:54.319> that<00:02:54.640> they<00:02:54.760> might<00:02:54.879> have<00:02:55.040> been 00:02:55.229 --> 00:02:55.239 align:start position:0% the way that they might have been 00:02:55.239 --> 00:02:58.110 align:start position:0% the way that they might have been expected<00:02:56.040> for<00:02:56.239> example<00:02:56.760> you<00:02:56.879> would<00:02:57.760> uh<00:02:57.879> still 00:02:58.110 --> 00:02:58.120 align:start position:0% expected for example you would uh still 00:02:58.120 --> 00:03:00.270 align:start position:0% expected for example you would uh still not<00:02:58.280> see<00:02:58.599> too<00:02:58.760> many<00:02:59.200> uh<00:02:59.319> TVs<00:02:59.879> that<00:03:00.080> actually 00:03:00.270 --> 00:03:00.280 align:start position:0% not see too many uh TVs that actually 00:03:00.280 --> 00:03:03.630 align:start position:0% not see too many uh TVs that actually are<00:03:00.480> used<00:03:00.800> to<00:03:01.519> uh<00:03:02.080> use<00:03:02.360> the<00:03:02.480> internet 00:03:03.630 --> 00:03:03.640 align:start position:0% are used to uh use the internet 00:03:03.640 --> 00:03:07.430 align:start position:0% are used to uh use the internet with<00:03:04.640> the<00:03:04.760> motivation<00:03:05.159> for<00:03:05.599> MDM<00:03:06.599> is<00:03:06.840> that<00:03:07.319> as 00:03:07.430 --> 00:03:07.440 align:start position:0% with the motivation for MDM is that as 00:03:07.440 --> 00:03:09.949 align:start position:0% with the motivation for MDM is that as more<00:03:07.599> and<00:03:07.799> more<00:03:08.120> devices<00:03:08.640> around<00:03:08.920> us<00:03:09.440> become 00:03:09.949 --> 00:03:09.959 align:start position:0% more and more devices around us become 00:03:09.959 --> 00:03:11.110 align:start position:0% more and more devices around us become more<00:03:10.120> and<00:03:10.239> more 00:03:11.110 --> 00:03:11.120 align:start position:0% more and more 00:03:11.120 --> 00:03:13.430 align:start position:0% more and more intelligent<00:03:12.120> um<00:03:12.280> the<00:03:12.440> digital<00:03:12.879> experience<00:03:13.280> is 00:03:13.430 --> 00:03:13.440 align:start position:0% intelligent um the digital experience is 00:03:13.440 --> 00:03:16.550 align:start position:0% intelligent um the digital experience is going<00:03:13.640> to<00:03:13.879> be<00:03:14.959> changing<00:03:15.959> and<00:03:16.080> more<00:03:16.239> and<00:03:16.400> more 00:03:16.550 --> 00:03:16.560 align:start position:0% going to be changing and more and more 00:03:16.560 --> 00:03:19.030 align:start position:0% going to be changing and more and more of<00:03:16.720> these<00:03:16.920> devices<00:03:17.319> will<00:03:17.519> be<00:03:18.239> connected 00:03:19.030 --> 00:03:19.040 align:start position:0% of these devices will be connected 00:03:19.040 --> 00:03:21.630 align:start position:0% of these devices will be connected directly<00:03:19.360> to<00:03:19.560> each<00:03:19.680> other<00:03:20.080> peer-to-peer<00:03:20.640> uh 00:03:21.630 --> 00:03:21.640 align:start position:0% directly to each other peer-to-peer uh 00:03:21.640 --> 00:03:23.470 align:start position:0% directly to each other peer-to-peer uh instead<00:03:21.959> of<00:03:22.080> to<00:03:22.360> centralized<00:03:22.879> Cloud<00:03:23.280> just 00:03:23.470 --> 00:03:23.480 align:start position:0% instead of to centralized Cloud just 00:03:23.480 --> 00:03:24.869 align:start position:0% instead of to centralized Cloud just because<00:03:23.920> they 00:03:24.869 --> 00:03:24.879 align:start position:0% because they 00:03:24.879 --> 00:03:29.589 align:start position:0% because they can<00:03:25.879> so<00:03:26.840> what's<00:03:27.080> emerging<00:03:27.920> there<00:03:28.920> is<00:03:29.319> uh<00:03:29.480> has 00:03:29.589 --> 00:03:29.599 align:start position:0% can so what's emerging there is uh has 00:03:29.599 --> 00:03:31.470 align:start position:0% can so what's emerging there is uh has been<00:03:29.959> called<00:03:30.319> a<00:03:30.480> devis 00:03:31.470 --> 00:03:31.480 align:start position:0% been called a devis 00:03:31.480 --> 00:03:34.710 align:start position:0% been called a devis democracy<00:03:32.480> in<00:03:32.599> the<00:03:32.720> best<00:03:33.080> case<00:03:34.080> where<00:03:34.519> the 00:03:34.710 --> 00:03:34.720 align:start position:0% democracy in the best case where the 00:03:34.720 --> 00:03:36.910 align:start position:0% democracy in the best case where the power<00:03:35.159> in<00:03:35.319> the<00:03:35.400> internet<00:03:35.799> of<00:03:36.239> of<00:03:36.400> things<00:03:36.680> will 00:03:36.910 --> 00:03:36.920 align:start position:0% power in the internet of of things will 00:03:36.920 --> 00:03:40.869 align:start position:0% power in the internet of of things will actually<00:03:37.239> shift<00:03:37.799> from<00:03:38.159> the<00:03:38.799> center<00:03:39.799> to<00:03:40.000> the 00:03:40.869 --> 00:03:40.879 align:start position:0% actually shift from the center to the 00:03:40.879 --> 00:03:43.550 align:start position:0% actually shift from the center to the edge<00:03:41.879> and<00:03:42.200> while<00:03:42.480> that 00:03:43.550 --> 00:03:43.560 align:start position:0% edge and while that 00:03:43.560 --> 00:03:45.910 align:start position:0% edge and while that happens<00:03:44.560> what<00:03:44.760> can<00:03:45.000> happen<00:03:45.319> there<00:03:45.519> is<00:03:45.640> that<00:03:45.799> a 00:03:45.910 --> 00:03:45.920 align:start position:0% happens what can happen there is that a 00:03:45.920 --> 00:03:48.110 align:start position:0% happens what can happen there is that a liquid<00:03:46.280> Market<00:03:46.840> can<00:03:47.040> emerge<00:03:47.480> where<00:03:47.720> devices 00:03:48.110 --> 00:03:48.120 align:start position:0% liquid Market can emerge where devices 00:03:48.120 --> 00:03:50.309 align:start position:0% liquid Market can emerge where devices are<00:03:48.239> dealing<00:03:48.599> directly<00:03:49.040> with<00:03:49.200> each 00:03:50.309 --> 00:03:50.319 align:start position:0% are dealing directly with each 00:03:50.319 --> 00:03:53.750 align:start position:0% are dealing directly with each other<00:03:51.319> and<00:03:51.680> this<00:03:51.799> will<00:03:51.959> hopefully<00:03:52.319> lead<00:03:52.760> to 00:03:53.750 --> 00:03:53.760 align:start position:0% other and this will hopefully lead to 00:03:53.760 --> 00:03:55.229 align:start position:0% other and this will hopefully lead to products<00:03:54.159> that<00:03:54.280> we<00:03:54.400> can't<00:03:54.599> even<00:03:54.799> imagine 00:03:55.229 --> 00:03:55.239 align:start position:0% products that we can't even imagine 00:03:55.239 --> 00:03:57.949 align:start position:0% products that we can't even imagine right 00:03:57.949 --> 00:03:57.959 align:start position:0% 00:03:57.959 --> 00:04:01.509 align:start position:0% now<00:03:58.959> obviously<00:03:59.840> to<00:04:00.000> make<00:04:00.280> that<00:04:00.560> happen<00:04:01.360> the 00:04:01.509 --> 00:04:01.519 align:start position:0% now obviously to make that happen the 00:04:01.519 --> 00:04:03.949 align:start position:0% now obviously to make that happen the blockchain<00:04:02.079> can<00:04:02.200> be<00:04:02.360> a<00:04:02.519> really<00:04:02.920> strong 00:04:03.949 --> 00:04:03.959 align:start position:0% blockchain can be a really strong 00:04:03.959 --> 00:04:06.869 align:start position:0% blockchain can be a really strong component<00:04:04.959> and<00:04:05.599> uh<00:04:05.799> the<00:04:05.959> needs<00:04:06.400> that<00:04:06.519> we 00:04:06.869 --> 00:04:06.879 align:start position:0% component and uh the needs that we 00:04:06.879 --> 00:04:10.190 align:start position:0% component and uh the needs that we identify<00:04:07.879> for<00:04:08.159> this<00:04:08.480> new<00:04:08.840> world<00:04:09.159> of<00:04:09.560> device 00:04:10.190 --> 00:04:10.200 align:start position:0% identify for this new world of device 00:04:10.200 --> 00:04:14.550 align:start position:0% identify for this new world of device democracy<00:04:11.200> are<00:04:12.159> um<00:04:12.400> to<00:04:13.239> large<00:04:13.599> degree<00:04:14.079> exactly 00:04:14.550 --> 00:04:14.560 align:start position:0% democracy are um to large degree exactly 00:04:14.560 --> 00:04:16.509 align:start position:0% democracy are um to large degree exactly what<00:04:14.799> what<00:04:14.879> a<00:04:15.040> blockchain<00:04:15.439> can 00:04:16.509 --> 00:04:16.519 align:start position:0% what what a blockchain can 00:04:16.519 --> 00:04:20.229 align:start position:0% what what a blockchain can offer<00:04:17.840> so<00:04:18.840> if<00:04:18.959> we<00:04:19.120> look<00:04:19.400> at<00:04:19.680> the<00:04:19.880> actual 00:04:20.229 --> 00:04:20.239 align:start position:0% offer so if we look at the actual 00:04:20.239 --> 00:04:22.749 align:start position:0% offer so if we look at the actual requirements<00:04:20.759> and<00:04:20.959> needs<00:04:21.639> of<00:04:21.959> the<00:04:22.360> Internet 00:04:22.749 --> 00:04:22.759 align:start position:0% requirements and needs of the Internet 00:04:22.759 --> 00:04:27.510 align:start position:0% requirements and needs of the Internet of<00:04:23.160> Things<00:04:24.160> realm<00:04:24.720> today<00:04:25.720> we<00:04:25.880> see<00:04:26.120> a<00:04:26.280> couple<00:04:26.560> of 00:04:27.510 --> 00:04:27.520 align:start position:0% of Things realm today we see a couple of 00:04:27.520 --> 00:04:30.510 align:start position:0% of Things realm today we see a couple of roadblocks<00:04:28.520> one<00:04:28.680> of<00:04:28.840> them<00:04:29.199> is<00:04:29.919> that<00:04:30.360> the 00:04:30.510 --> 00:04:30.520 align:start position:0% roadblocks one of them is that the 00:04:30.520 --> 00:04:31.950 align:start position:0% roadblocks one of them is that the architecture<00:04:31.039> that<00:04:31.160> we<00:04:31.280> have<00:04:31.440> today<00:04:31.759> that's 00:04:31.950 --> 00:04:31.960 align:start position:0% architecture that we have today that's 00:04:31.960 --> 00:04:34.230 align:start position:0% architecture that we have today that's highly<00:04:32.360> centralized<00:04:33.360> won't<00:04:33.720> necessarily 00:04:34.230 --> 00:04:34.240 align:start position:0% highly centralized won't necessarily 00:04:34.240 --> 00:04:36.230 align:start position:0% highly centralized won't necessarily scale<00:04:34.919> over<00:04:35.120> the<00:04:35.240> next<00:04:35.440> couple<00:04:35.720> years<00:04:36.000> we<00:04:36.120> now 00:04:36.230 --> 00:04:36.240 align:start position:0% scale over the next couple years we now 00:04:36.240 --> 00:04:39.150 align:start position:0% scale over the next couple years we now have<00:04:36.360> an<00:04:36.479> internet<00:04:36.840> of<00:04:37.000> things<00:04:38.000> that<00:04:38.199> is<00:04:38.919> uh 00:04:39.150 --> 00:04:39.160 align:start position:0% have an internet of things that is uh 00:04:39.160 --> 00:04:42.950 align:start position:0% have an internet of things that is uh having<00:04:39.400> a<00:04:39.560> certain<00:04:40.120> topology<00:04:41.120> and<00:04:41.520> we<00:04:41.800> will<00:04:42.800> at 00:04:42.950 --> 00:04:42.960 align:start position:0% having a certain topology and we will at 00:04:42.960 --> 00:04:46.150 align:start position:0% having a certain topology and we will at any<00:04:43.440> rate<00:04:44.440> uh<00:04:44.560> want<00:04:44.720> to<00:04:44.840> find<00:04:45.080> a<00:04:45.199> new<00:04:45.440> way<00:04:46.000> of 00:04:46.150 --> 00:04:46.160 align:start position:0% any rate uh want to find a new way of 00:04:46.160 --> 00:04:47.670 align:start position:0% any rate uh want to find a new way of connecting 00:04:47.670 --> 00:04:47.680 align:start position:0% connecting 00:04:47.680 --> 00:04:49.629 align:start position:0% connecting devices 00:04:49.629 --> 00:04:49.639 align:start position:0% devices 00:04:49.639 --> 00:04:52.350 align:start position:0% devices then<00:04:50.639> these<00:04:50.880> connections<00:04:51.479> have<00:04:51.600> to<00:04:51.800> be 00:04:52.350 --> 00:04:52.360 align:start position:0% then these connections have to be 00:04:52.360 --> 00:04:55.070 align:start position:0% then these connections have to be maintained<00:04:53.000> they<00:04:53.160> have<00:04:53.280> to<00:04:53.440> be<00:04:53.800> uphold<00:04:54.800> and 00:04:55.070 --> 00:04:55.080 align:start position:0% maintained they have to be uphold and 00:04:55.080 --> 00:04:58.110 align:start position:0% maintained they have to be uphold and this<00:04:55.240> is<00:04:55.400> going<00:04:55.639> to<00:04:55.840> be<00:04:56.759> creating<00:04:57.160> some 00:04:58.110 --> 00:04:58.120 align:start position:0% this is going to be creating some 00:04:58.120 --> 00:05:00.310 align:start position:0% this is going to be creating some expense<00:04:58.720> and<00:04:58.880> somehow<00:04:59.800> that<00:04:59.960> has<00:05:00.039> to<00:05:00.160> be 00:05:00.310 --> 00:05:00.320 align:start position:0% expense and somehow that has to be 00:05:00.320 --> 00:05:02.230 align:start position:0% expense and somehow that has to be justified<00:05:00.919> and<00:05:01.039> it's<00:05:01.240> not<00:05:01.520> quite<00:05:01.759> clear<00:05:02.039> that 00:05:02.230 --> 00:05:02.240 align:start position:0% justified and it's not quite clear that 00:05:02.240 --> 00:05:03.550 align:start position:0% justified and it's not quite clear that the<00:05:02.440> business<00:05:02.759> business<00:05:03.000> models<00:05:03.320> that<00:05:03.440> we 00:05:03.550 --> 00:05:03.560 align:start position:0% the business business models that we 00:05:03.560 --> 00:05:06.310 align:start position:0% the business business models that we have<00:05:03.680> today<00:05:03.960> are<00:05:04.199> actually<00:05:04.479> doing<00:05:05.160> that<00:05:06.160> what 00:05:06.310 --> 00:05:06.320 align:start position:0% have today are actually doing that what 00:05:06.320 --> 00:05:10.350 align:start position:0% have today are actually doing that what we<00:05:06.479> also<00:05:06.840> are<00:05:07.080> going<00:05:07.280> to<00:05:07.880> realize<00:05:08.360> is<00:05:08.560> that<00:05:09.360> um 00:05:10.350 --> 00:05:10.360 align:start position:0% we also are going to realize is that um 00:05:10.360 --> 00:05:13.230 align:start position:0% we also are going to realize is that um the<00:05:10.479> internet<00:05:10.840> of<00:05:11.199> trust<00:05:11.720> that<00:05:11.840> we<00:05:12.039> had<00:05:12.919> some 00:05:13.230 --> 00:05:13.240 align:start position:0% the internet of trust that we had some 00:05:13.240 --> 00:05:15.469 align:start position:0% the internet of trust that we had some decades<00:05:13.639> ago<00:05:14.320> without<00:05:14.639> spamming<00:05:15.160> everything 00:05:15.469 --> 00:05:15.479 align:start position:0% decades ago without spamming everything 00:05:15.479 --> 00:05:17.590 align:start position:0% decades ago without spamming everything is<00:05:15.680> not<00:05:15.800> a<00:05:15.919> reality<00:05:16.320> anymore<00:05:17.080> we<00:05:17.199> can<00:05:17.400> be 00:05:17.590 --> 00:05:17.600 align:start position:0% is not a reality anymore we can be 00:05:17.600 --> 00:05:20.309 align:start position:0% is not a reality anymore we can be certain<00:05:18.039> that<00:05:18.560> any<00:05:19.560> um<00:05:19.720> system<00:05:20.039> that<00:05:20.160> we're 00:05:20.309 --> 00:05:20.319 align:start position:0% certain that any um system that we're 00:05:20.319 --> 00:05:21.990 align:start position:0% certain that any um system that we're deploying<00:05:20.680> today<00:05:20.960> is<00:05:21.080> going<00:05:21.280> to<00:05:21.400> be<00:05:21.600> attacked 00:05:21.990 --> 00:05:22.000 align:start position:0% deploying today is going to be attacked 00:05:22.000 --> 00:05:23.950 align:start position:0% deploying today is going to be attacked and<00:05:22.160> his<00:05:22.680> vulnerabilities<00:05:23.360> are<00:05:23.479> going<00:05:23.680> to<00:05:23.800> be 00:05:23.950 --> 00:05:23.960 align:start position:0% and his vulnerabilities are going to be 00:05:23.960 --> 00:05:28.510 align:start position:0% and his vulnerabilities are going to be exploited<00:05:24.759> so<00:05:25.080> security<00:05:25.600> has<00:05:25.840> a<00:05:26.080> very<00:05:26.840> high<00:05:27.840> um 00:05:28.510 --> 00:05:28.520 align:start position:0% exploited so security has a very high um 00:05:28.520 --> 00:05:33.029 align:start position:0% exploited so security has a very high um priority<00:05:29.039> right<00:05:29.199> now<00:05:29.720> we<00:05:29.919> also<00:05:31.360> won't<00:05:32.360> have<00:05:32.880> be 00:05:33.029 --> 00:05:33.039 align:start position:0% priority right now we also won't have be 00:05:33.039 --> 00:05:35.830 align:start position:0% priority right now we also won't have be seeing<00:05:33.479> people<00:05:34.479> accepting<00:05:35.039> their<00:05:35.280> toast<00:05:35.639> or 00:05:35.830 --> 00:05:35.840 align:start position:0% seeing people accepting their toast or 00:05:35.840 --> 00:05:38.150 align:start position:0% seeing people accepting their toast or spying<00:05:36.240> at<00:05:36.440> them<00:05:37.120> so<00:05:37.319> that's<00:05:37.479> another 00:05:38.150 --> 00:05:38.160 align:start position:0% spying at them so that's another 00:05:38.160 --> 00:05:40.950 align:start position:0% spying at them so that's another dimension<00:05:38.520> of<00:05:38.720> security<00:05:39.479> where<00:05:40.479> people<00:05:40.720> will 00:05:40.950 --> 00:05:40.960 align:start position:0% dimension of security where people will 00:05:40.960 --> 00:05:42.670 align:start position:0% dimension of security where people will want<00:05:41.120> to<00:05:41.319> have<00:05:41.440> some<00:05:41.680> control<00:05:42.160> over<00:05:42.400> what<00:05:42.520> the 00:05:42.670 --> 00:05:42.680 align:start position:0% want to have some control over what the 00:05:42.680 --> 00:05:45.430 align:start position:0% want to have some control over what the devices<00:05:43.039> are<00:05:43.479> doing<00:05:44.479> and<00:05:44.759> the<00:05:44.919> way<00:05:45.160> that<00:05:45.319> for 00:05:45.430 --> 00:05:45.440 align:start position:0% devices are doing and the way that for 00:05:45.440 --> 00:05:47.150 align:start position:0% devices are doing and the way that for example<00:05:45.759> the<00:05:45.919> smartphone<00:05:46.479> is<00:05:46.759> completely 00:05:47.150 --> 00:05:47.160 align:start position:0% example the smartphone is completely 00:05:47.160 --> 00:05:49.550 align:start position:0% example the smartphone is completely owned<00:05:47.720> by<00:05:47.960> the<00:05:48.840> um<00:05:48.960> producer<00:05:49.360> of<00:05:49.440> the 00:05:49.550 --> 00:05:49.560 align:start position:0% owned by the um producer of the 00:05:49.560 --> 00:05:51.909 align:start position:0% owned by the um producer of the smartphone<00:05:50.039> today<00:05:50.960> is<00:05:51.280> probably<00:05:51.560> not<00:05:51.759> how 00:05:51.909 --> 00:05:51.919 align:start position:0% smartphone today is probably not how 00:05:51.919 --> 00:05:56.270 align:start position:0% smartphone today is probably not how it's<00:05:52.080> going<00:05:52.240> to<00:05:52.440> be 00:05:56.270 --> 00:05:56.280 align:start position:0% 00:05:56.280 --> 00:05:59.870 align:start position:0% continued<00:05:57.600> now<00:05:58.600> coming<00:05:58.919> back<00:05:59.039> to<00:05:59.120> the<00:05:59.240> toaster 00:05:59.870 --> 00:05:59.880 align:start position:0% continued now coming back to the toaster 00:05:59.880 --> 00:06:00.909 align:start position:0% continued now coming back to the toaster people 00:06:00.909 --> 00:06:00.919 align:start position:0% people 00:06:00.919 --> 00:06:04.990 align:start position:0% people expect<00:06:01.919> 20<00:06:02.319> years<00:06:02.720> or<00:06:02.960> more<00:06:03.800> as<00:06:03.919> a<00:06:04.120> LIF<00:06:04.680> span 00:06:04.990 --> 00:06:05.000 align:start position:0% expect 20 years or more as a LIF span 00:06:05.000 --> 00:06:05.909 align:start position:0% expect 20 years or more as a LIF span for<00:06:05.160> a 00:06:05.909 --> 00:06:05.919 align:start position:0% for a 00:06:05.919 --> 00:06:08.629 align:start position:0% for a toaster<00:06:06.919> if<00:06:07.039> you<00:06:07.160> have<00:06:07.240> a<00:06:07.360> centralist<00:06:07.880> model 00:06:08.629 --> 00:06:08.639 align:start position:0% toaster if you have a centralist model 00:06:08.639 --> 00:06:11.510 align:start position:0% toaster if you have a centralist model with<00:06:09.039> a<00:06:10.039> toaster<00:06:10.560> that's<00:06:10.759> somehow<00:06:11.080> useful 00:06:11.510 --> 00:06:11.520 align:start position:0% with a toaster that's somehow useful 00:06:11.520 --> 00:06:14.230 align:start position:0% with a toaster that's somehow useful because<00:06:11.759> it's<00:06:12.440> connected<00:06:13.440> um<00:06:13.680> then<00:06:14.000> you<00:06:14.160> have 00:06:14.230 --> 00:06:14.240 align:start position:0% because it's connected um then you have 00:06:14.240 --> 00:06:16.110 align:start position:0% because it's connected um then you have to<00:06:14.360> maintain<00:06:14.720> that<00:06:14.880> for<00:06:15.039> 20 00:06:16.110 --> 00:06:16.120 align:start position:0% to maintain that for 20 00:06:16.120 --> 00:06:19.230 align:start position:0% to maintain that for 20 years<00:06:17.120> is<00:06:17.319> that<00:06:17.639> even<00:06:17.919> viable<00:06:18.440> or<00:06:18.759> are<00:06:19.000> people 00:06:19.230 --> 00:06:19.240 align:start position:0% years is that even viable or are people 00:06:19.240 --> 00:06:21.950 align:start position:0% years is that even viable or are people going<00:06:19.440> to<00:06:19.560> be<00:06:19.840> very<00:06:20.080> very<00:06:20.280> frustrated<00:06:20.880> with<00:06:21.800> um 00:06:21.950 --> 00:06:21.960 align:start position:0% going to be very very frustrated with um 00:06:21.960 --> 00:06:23.990 align:start position:0% going to be very very frustrated with um producers<00:06:22.400> going<00:06:22.599> out<00:06:22.759> of<00:06:22.919> business<00:06:23.479> which<00:06:23.639> is 00:06:23.990 --> 00:06:24.000 align:start position:0% producers going out of business which is 00:06:24.000 --> 00:06:26.189 align:start position:0% producers going out of business which is kind<00:06:24.120> of<00:06:24.280> likely<00:06:24.680> within<00:06:25.080> 20<00:06:25.360> years<00:06:25.599> not<00:06:26.000> every 00:06:26.189 --> 00:06:26.199 align:start position:0% kind of likely within 20 years not every 00:06:26.199 --> 00:06:29.270 align:start position:0% kind of likely within 20 years not every company<00:06:26.800> gets<00:06:27.000> to<00:06:27.280> 100<00:06:27.560> like<00:06:28.039> IBM<00:06:29.039> and<00:06:29.160> then 00:06:29.270 --> 00:06:29.280 align:start position:0% company gets to 100 like IBM and then 00:06:29.280 --> 00:06:30.430 align:start position:0% company gets to 100 like IBM and then fin 00:06:30.430 --> 00:06:30.440 align:start position:0% fin 00:06:30.440 --> 00:06:32.390 align:start position:0% fin the<00:06:30.560> business<00:06:30.840> models<00:06:31.240> that<00:06:31.360> we're<00:06:31.720> seeing 00:06:32.390 --> 00:06:32.400 align:start position:0% the business models that we're seeing 00:06:32.400 --> 00:06:35.029 align:start position:0% the business models that we're seeing today<00:06:33.400> uh<00:06:33.520> sorry<00:06:34.160> uh<00:06:34.240> the<00:06:34.360> business<00:06:34.639> models 00:06:35.029 --> 00:06:35.039 align:start position:0% today uh sorry uh the business models 00:06:35.039 --> 00:06:37.990 align:start position:0% today uh sorry uh the business models that<00:06:35.120> we're<00:06:35.280> seeing<00:06:35.560> today 00:06:37.990 --> 00:06:38.000 align:start position:0% that we're seeing today 00:06:38.000 --> 00:06:40.830 align:start position:0% that we're seeing today are<00:06:39.000> very<00:06:39.240> much<00:06:39.479> focus<00:06:39.840> on<00:06:40.039> information<00:06:40.599> for 00:06:40.830 --> 00:06:40.840 align:start position:0% are very much focus on information for 00:06:40.840 --> 00:06:43.110 align:start position:0% are very much focus on information for advertisement<00:06:41.800> and<00:06:41.960> that<00:06:42.080> is<00:06:42.639> probably<00:06:42.960> not 00:06:43.110 --> 00:06:43.120 align:start position:0% advertisement and that is probably not 00:06:43.120 --> 00:06:44.909 align:start position:0% advertisement and that is probably not going<00:06:43.319> to<00:06:43.479> scale<00:06:44.039> because<00:06:44.280> there's<00:06:44.479> only<00:06:44.720> so 00:06:44.909 --> 00:06:44.919 align:start position:0% going to scale because there's only so 00:06:44.919 --> 00:06:47.469 align:start position:0% going to scale because there's only so much<00:06:45.120> data<00:06:45.360> that<00:06:45.479> you<00:06:45.599> can<00:06:45.880> actually<00:06:46.880> get<00:06:47.199> out 00:06:47.469 --> 00:06:47.479 align:start position:0% much data that you can actually get out 00:06:47.479 --> 00:06:50.029 align:start position:0% much data that you can actually get out of<00:06:47.960> a<00:06:48.240> household<00:06:49.240> and<00:06:49.400> as<00:06:49.599> more<00:06:49.720> and<00:06:49.880> more 00:06:50.029 --> 00:06:50.039 align:start position:0% of a household and as more and more 00:06:50.039 --> 00:06:51.990 align:start position:0% of a household and as more and more devices<00:06:50.440> compete<00:06:50.840> to<00:06:51.000> collect<00:06:51.280> the<00:06:51.400> same<00:06:51.639> data 00:06:51.990 --> 00:06:52.000 align:start position:0% devices compete to collect the same data 00:06:52.000 --> 00:06:54.070 align:start position:0% devices compete to collect the same data then<00:06:52.199> probably<00:06:52.599> the<00:06:53.199> value<00:06:53.479> of<00:06:53.639> the<00:06:53.759> data<00:06:53.960> is 00:06:54.070 --> 00:06:54.080 align:start position:0% then probably the value of the data is 00:06:54.080 --> 00:06:56.189 align:start position:0% then probably the value of the data is going<00:06:54.240> to<00:06:54.479> go 00:06:56.189 --> 00:06:56.199 align:start position:0% going to go 00:06:56.199 --> 00:06:59.749 align:start position:0% going to go down<00:06:57.199> so<00:06:57.440> the<00:06:57.520> motivation<00:06:58.039> here<00:06:58.280> is<00:06:59.080> that<00:06:59.639> when 00:06:59.749 --> 00:06:59.759 align:start position:0% down so the motivation here is that when 00:06:59.759 --> 00:07:02.869 align:start position:0% down so the motivation here is that when we<00:07:00.000> see<00:07:01.000> um<00:07:01.639> uh<00:07:01.800> the<00:07:02.000> possibilities<00:07:02.599> that<00:07:02.759> we 00:07:02.869 --> 00:07:02.879 align:start position:0% we see um uh the possibilities that we 00:07:02.879 --> 00:07:05.510 align:start position:0% we see um uh the possibilities that we have<00:07:03.080> here<00:07:03.240> today<00:07:03.960> can<00:07:04.160> we<00:07:04.440> have<00:07:04.960> a 00:07:05.510 --> 00:07:05.520 align:start position:0% have here today can we have a 00:07:05.520 --> 00:07:09.350 align:start position:0% have here today can we have a userdefined<00:07:06.720> algorithm<00:07:07.720> can<00:07:07.919> we<00:07:08.160> have<00:07:09.000> a 00:07:09.350 --> 00:07:09.360 align:start position:0% userdefined algorithm can we have a 00:07:09.360 --> 00:07:12.790 align:start position:0% userdefined algorithm can we have a customized<00:07:10.360> experience<00:07:11.360> that<00:07:11.479> is<00:07:11.720> not<00:07:12.120> based 00:07:12.790 --> 00:07:12.800 align:start position:0% customized experience that is not based 00:07:12.800 --> 00:07:15.110 align:start position:0% customized experience that is not based on<00:07:13.000> what<00:07:13.160> we<00:07:13.360> have<00:07:13.680> in<00:07:13.800> the<00:07:13.960> moment<00:07:14.879> and<00:07:15.000> the 00:07:15.110 --> 00:07:15.120 align:start position:0% on what we have in the moment and the 00:07:15.120 --> 00:07:18.230 align:start position:0% on what we have in the moment and the iot<00:07:15.560> today<00:07:16.319> where<00:07:16.479> we<00:07:16.720> have 00:07:18.230 --> 00:07:18.240 align:start position:0% iot today where we have 00:07:18.240 --> 00:07:21.430 align:start position:0% iot today where we have uh<00:07:19.240> new<00:07:19.599> possibilities<00:07:20.599> that<00:07:20.759> are<00:07:21.039> going<00:07:21.280> to 00:07:21.430 --> 00:07:21.440 align:start position:0% uh new possibilities that are going to 00:07:21.440 --> 00:07:25.309 align:start position:0% uh new possibilities that are going to be<00:07:21.599> used<00:07:22.039> either<00:07:22.919> for<00:07:23.919> mischievous<00:07:24.680> stuff<00:07:25.039> if 00:07:25.309 --> 00:07:25.319 align:start position:0% be used either for mischievous stuff if 00:07:25.319 --> 00:07:27.110 align:start position:0% be used either for mischievous stuff if security<00:07:25.680> is<00:07:25.800> not<00:07:26.000> high<00:07:26.199> enough<00:07:26.479> or<00:07:26.840> for 00:07:27.110 --> 00:07:27.120 align:start position:0% security is not high enough or for 00:07:27.120 --> 00:07:28.629 align:start position:0% security is not high enough or for exciting<00:07:27.520> new<00:07:27.800> stuff<00:07:28.080> that<00:07:28.240> we<00:07:28.319> might<00:07:28.479> not 00:07:28.629 --> 00:07:28.639 align:start position:0% exciting new stuff that we might not 00:07:28.639 --> 00:07:32.070 align:start position:0% exciting new stuff that we might not even<00:07:28.800> imagine<00:07:29.199> right<00:07:29.319> now 00:07:32.070 --> 00:07:32.080 align:start position:0% 00:07:32.080 --> 00:07:35.629 align:start position:0% when<00:07:32.759> we<00:07:33.759> see<00:07:34.000> at<00:07:34.120> the<00:07:34.240> bottom<00:07:34.520> line<00:07:34.840> though<00:07:35.520> uh 00:07:35.629 --> 00:07:35.639 align:start position:0% when we see at the bottom line though uh 00:07:35.639 --> 00:07:37.189 align:start position:0% when we see at the bottom line though uh it's<00:07:35.800> important<00:07:36.120> to<00:07:36.280> always<00:07:36.520> remember<00:07:36.919> that 00:07:37.189 --> 00:07:37.199 align:start position:0% it's important to always remember that 00:07:37.199 --> 00:07:38.990 align:start position:0% it's important to always remember that in<00:07:37.319> the<00:07:37.479> end<00:07:37.680> it's<00:07:37.840> about<00:07:38.120> making<00:07:38.440> the 00:07:38.990 --> 00:07:39.000 align:start position:0% in the end it's about making the 00:07:39.000 --> 00:07:40.309 align:start position:0% in the end it's about making the experience 00:07:40.309 --> 00:07:40.319 align:start position:0% experience 00:07:40.319 --> 00:07:44.309 align:start position:0% experience better<00:07:41.319> it's<00:07:41.560> not<00:07:42.520> maybe<00:07:43.280> worthwhile<00:07:43.919> to<00:07:44.120> have 00:07:44.309 --> 00:07:44.319 align:start position:0% better it's not maybe worthwhile to have 00:07:44.319 --> 00:07:46.790 align:start position:0% better it's not maybe worthwhile to have the<00:07:44.520> toaster<00:07:45.479> printing<00:07:46.000> advertisement<00:07:46.639> on 00:07:46.790 --> 00:07:46.800 align:start position:0% the toaster printing advertisement on 00:07:46.800 --> 00:07:49.070 align:start position:0% the toaster printing advertisement on your<00:07:47.080> toast<00:07:48.080> but<00:07:48.280> you<00:07:48.400> will<00:07:48.599> want<00:07:48.759> to<00:07:48.919> have 00:07:49.070 --> 00:07:49.080 align:start position:0% your toast but you will want to have 00:07:49.080 --> 00:07:52.110 align:start position:0% your toast but you will want to have something<00:07:49.400> that<00:07:49.560> really<00:07:49.759> makes 00:07:52.110 --> 00:07:52.120 align:start position:0% 00:07:52.120 --> 00:07:54.390 align:start position:0% sense<00:07:53.120> and<00:07:53.240> the<00:07:53.360> whole<00:07:53.560> on<00:07:53.680> the<00:07:53.800> whole<00:07:54.159> what<00:07:54.280> we 00:07:54.390 --> 00:07:54.400 align:start position:0% sense and the whole on the whole what we 00:07:54.400 --> 00:07:56.749 align:start position:0% sense and the whole on the whole what we are<00:07:54.759> having<00:07:55.039> today<00:07:55.400> is<00:07:55.560> the<00:07:55.759> cloud<00:07:56.360> as<00:07:56.479> a 00:07:56.749 --> 00:07:56.759 align:start position:0% are having today is the cloud as a 00:07:56.759 --> 00:07:59.790 align:start position:0% are having today is the cloud as a centralized<00:07:57.759> very<00:07:58.080> powerful<00:07:59.039> control 00:07:59.790 --> 00:07:59.800 align:start position:0% centralized very powerful control 00:07:59.800 --> 00:08:02.469 align:start position:0% centralized very powerful control mechanism<00:08:00.280> so<00:08:00.440> to<00:08:00.599> say<00:08:01.159> of<00:08:01.400> devices<00:08:02.240> that's 00:08:02.469 --> 00:08:02.479 align:start position:0% mechanism so to say of devices that's 00:08:02.479 --> 00:08:04.869 align:start position:0% mechanism so to say of devices that's less<00:08:02.639> centralized<00:08:03.159> than<00:08:03.280> we<00:08:03.400> had<00:08:03.759> before<00:08:04.759> but 00:08:04.869 --> 00:08:04.879 align:start position:0% less centralized than we had before but 00:08:04.879 --> 00:08:06.909 align:start position:0% less centralized than we had before but it's<00:08:05.159> also<00:08:05.680> not<00:08:06.000> probably<00:08:06.319> how<00:08:06.440> it's<00:08:06.599> going<00:08:06.720> to 00:08:06.909 --> 00:08:06.919 align:start position:0% it's also not probably how it's going to 00:08:06.919 --> 00:08:08.550 align:start position:0% it's also not probably how it's going to stay<00:08:07.199> when<00:08:07.319> we<00:08:07.520> going<00:08:07.680> to<00:08:07.840> more<00:08:08.000> and<00:08:08.120> more<00:08:08.360> peer 00:08:08.550 --> 00:08:08.560 align:start position:0% stay when we going to more and more peer 00:08:08.560 --> 00:08:10.990 align:start position:0% stay when we going to more and more peer and<00:08:08.759> peer 00:08:10.990 --> 00:08:11.000 align:start position:0% and peer 00:08:11.000 --> 00:08:13.309 align:start position:0% and peer architectures<00:08:12.000> that<00:08:12.360> this<00:08:12.520> kind<00:08:12.720> of 00:08:13.309 --> 00:08:13.319 align:start position:0% architectures that this kind of 00:08:13.319 --> 00:08:16.230 align:start position:0% architectures that this kind of development<00:08:14.039> is<00:08:15.039> uh<00:08:15.199> happening<00:08:15.840> no<00:08:15.960> matter 00:08:16.230 --> 00:08:16.240 align:start position:0% development is uh happening no matter 00:08:16.240 --> 00:08:18.430 align:start position:0% development is uh happening no matter whether<00:08:16.479> you<00:08:16.599> are<00:08:17.199> Imagining<00:08:17.759> the<00:08:17.919> blockchain 00:08:18.430 --> 00:08:18.440 align:start position:0% whether you are Imagining the blockchain 00:08:18.440 --> 00:08:20.550 align:start position:0% whether you are Imagining the blockchain here<00:08:18.720> or<00:08:19.039> some<00:08:19.240> other<00:08:19.440> peer-to-peer 00:08:20.550 --> 00:08:20.560 align:start position:0% here or some other peer-to-peer 00:08:20.560 --> 00:08:23.589 align:start position:0% here or some other peer-to-peer mechanism<00:08:21.560> that's<00:08:21.919> that<00:08:22.039> is<00:08:22.240> pretty 00:08:23.589 --> 00:08:23.599 align:start position:0% mechanism that's that is pretty 00:08:23.599 --> 00:08:25.869 align:start position:0% mechanism that's that is pretty clear<00:08:24.599> so<00:08:24.919> if<00:08:25.000> you<00:08:25.159> look<00:08:25.319> at<00:08:25.520> this 00:08:25.869 --> 00:08:25.879 align:start position:0% clear so if you look at this 00:08:25.879 --> 00:08:29.510 align:start position:0% clear so if you look at this requirements<00:08:26.639> what<00:08:26.840> emerges<00:08:27.800> as<00:08:28.440> um<00:08:28.919> basic 00:08:29.510 --> 00:08:29.520 align:start position:0% requirements what emerges as um basic 00:08:29.520 --> 00:08:32.310 align:start position:0% requirements what emerges as um basic foundation<00:08:29.879> so<00:08:30.039> to<00:08:30.240> say<00:08:31.080> has<00:08:31.199> a<00:08:31.680> very<00:08:31.960> large 00:08:32.310 --> 00:08:32.320 align:start position:0% foundation so to say has a very large 00:08:32.320 --> 00:08:35.829 align:start position:0% foundation so to say has a very large overlap<00:08:33.320> with<00:08:33.640> what<00:08:33.800> blockchain<00:08:34.240> can<00:08:34.839> offer 00:08:35.829 --> 00:08:35.839 align:start position:0% overlap with what blockchain can offer 00:08:35.839 --> 00:08:38.430 align:start position:0% overlap with what blockchain can offer and<00:08:36.279> uh<00:08:36.399> in<00:08:36.560> this<00:08:37.120> regard<00:08:38.000> except<00:08:38.240> for 00:08:38.430 --> 00:08:38.440 align:start position:0% and uh in this regard except for 00:08:38.440 --> 00:08:41.310 align:start position:0% and uh in this regard except for identity<00:08:39.159> all<00:08:39.440> three<00:08:39.680> of<00:08:39.919> the<00:08:40.680> first<00:08:41.120> all 00:08:41.310 --> 00:08:41.320 align:start position:0% identity all three of the first all 00:08:41.320 --> 00:08:43.870 align:start position:0% identity all three of the first all three<00:08:41.519> bullet<00:08:41.839> points<00:08:42.120> over<00:08:42.360> that<00:08:43.120> are 00:08:43.870 --> 00:08:43.880 align:start position:0% three bullet points over that are 00:08:43.880 --> 00:08:46.470 align:start position:0% three bullet points over that are exactly<00:08:44.360> what<00:08:44.480> a<00:08:44.640> blockchain<00:08:45.040> can<00:08:45.160> offer<00:08:45.480> you 00:08:46.470 --> 00:08:46.480 align:start position:0% exactly what a blockchain can offer you 00:08:46.480 --> 00:08:49.790 align:start position:0% exactly what a blockchain can offer you you<00:08:46.600> will<00:08:46.920> have<00:08:47.600> um<00:08:47.920> a<00:08:48.120> very<00:08:48.519> interested 00:08:49.790 --> 00:08:49.800 align:start position:0% you will have um a very interested 00:08:49.800 --> 00:08:51.949 align:start position:0% you will have um a very interested interesting<00:08:50.800> uh<00:08:50.959> convergence<00:08:51.600> here<00:08:51.839> where 00:08:51.949 --> 00:08:51.959 align:start position:0% interesting uh convergence here where 00:08:51.959 --> 00:08:54.350 align:start position:0% interesting uh convergence here where you<00:08:52.080> can<00:08:52.200> see<00:08:52.399> that<00:08:52.560> ethereum<00:08:53.000> for<00:08:53.160> example<00:08:53.760> is 00:08:54.350 --> 00:08:54.360 align:start position:0% you can see that ethereum for example is 00:08:54.360 --> 00:08:57.070 align:start position:0% you can see that ethereum for example is uh<00:08:54.519> implementing<00:08:55.040> whisper<00:08:55.519> now<00:08:56.519> um<00:08:56.720> there<00:08:56.880> are 00:08:57.070 --> 00:08:57.080 align:start position:0% uh implementing whisper now um there are 00:08:57.080 --> 00:09:00.430 align:start position:0% uh implementing whisper now um there are efforts<00:08:57.480> to<00:08:58.200> uh<00:08:58.440> create<00:08:58.720> swarm<00:08:59.880> that<00:09:00.000> is<00:09:00.240> going 00:09:00.430 --> 00:09:00.440 align:start position:0% efforts to uh create swarm that is going 00:09:00.440 --> 00:09:03.190 align:start position:0% efforts to uh create swarm that is going to<00:09:00.720> add<00:09:01.040> exactly<00:09:01.880> um<00:09:02.120> what<00:09:02.240> is<00:09:02.440> needed<00:09:02.760> to<00:09:03.000> have 00:09:03.190 --> 00:09:03.200 align:start position:0% to add exactly um what is needed to have 00:09:03.200 --> 00:09:06.829 align:start position:0% to add exactly um what is needed to have file<00:09:03.480> transfer<00:09:04.040> and<00:09:04.600> messaging<00:09:05.600> where<00:09:06.440> uh 00:09:06.829 --> 00:09:06.839 align:start position:0% file transfer and messaging where uh 00:09:06.839 --> 00:09:09.470 align:start position:0% file transfer and messaging where uh fascinatingly<00:09:07.839> in<00:09:08.040> earlier<00:09:08.880> Explorations 00:09:09.470 --> 00:09:09.480 align:start position:0% fascinatingly in earlier Explorations 00:09:09.480 --> 00:09:13.150 align:start position:0% fascinatingly in earlier Explorations that<00:09:09.720> were<00:09:10.160> done<00:09:10.399> at<00:09:10.680> IBM<00:09:11.680> um<00:09:11.839> Tash<00:09:12.600> and<00:09:12.800> bitter 00:09:13.150 --> 00:09:13.160 align:start position:0% that were done at IBM um Tash and bitter 00:09:13.160 --> 00:09:17.630 align:start position:0% that were done at IBM um Tash and bitter rent<00:09:13.440> were<00:09:13.880> used<00:09:14.720> um<00:09:14.920> that<00:09:15.040> are<00:09:15.320> now<00:09:16.320> um<00:09:17.320> or<00:09:17.519> at 00:09:17.630 --> 00:09:17.640 align:start position:0% rent were used um that are now um or at 00:09:17.640 --> 00:09:20.110 align:start position:0% rent were used um that are now um or at least<00:09:17.880> part<00:09:18.079> of<00:09:18.240> them<00:09:18.600> part<00:09:18.839> of<00:09:19.440> uh<00:09:19.720> whisper 00:09:20.110 --> 00:09:20.120 align:start position:0% least part of them part of uh whisper 00:09:20.120 --> 00:09:22.630 align:start position:0% least part of them part of uh whisper and 00:09:22.630 --> 00:09:22.640 align:start position:0% 00:09:22.640 --> 00:09:25.110 align:start position:0% swarm<00:09:23.640> so<00:09:24.040> the<00:09:24.160> internet<00:09:24.480> of<00:09:24.600> things<00:09:24.880> as<00:09:24.959> it 00:09:25.110 --> 00:09:25.120 align:start position:0% swarm so the internet of things as it 00:09:25.120 --> 00:09:27.990 align:start position:0% swarm so the internet of things as it stands<00:09:25.519> now<00:09:26.079> is<00:09:26.240> at<00:09:26.480> probably<00:09:26.800> 9<00:09:27.079> billion 00:09:27.990 --> 00:09:28.000 align:start position:0% stands now is at probably 9 billion 00:09:28.000 --> 00:09:30.150 align:start position:0% stands now is at probably 9 billion devices<00:09:29.000> and<00:09:29.160> what<00:09:29.440> we<00:09:29.600> thinking<00:09:29.839> about<00:09:30.000> and 00:09:30.150 --> 00:09:30.160 align:start position:0% devices and what we thinking about and 00:09:30.160 --> 00:09:31.949 align:start position:0% devices and what we thinking about and talking<00:09:30.440> about<00:09:30.720> is<00:09:30.959> when<00:09:31.120> it<00:09:31.279> goes<00:09:31.480> to<00:09:31.760> 100 00:09:31.949 --> 00:09:31.959 align:start position:0% talking about is when it goes to 100 00:09:31.959 --> 00:09:33.550 align:start position:0% talking about is when it goes to 100 billion<00:09:32.320> devices<00:09:32.800> which<00:09:32.880> is<00:09:33.000> the<00:09:33.120> future 00:09:33.550 --> 00:09:33.560 align:start position:0% billion devices which is the future 00:09:33.560 --> 00:09:35.949 align:start position:0% billion devices which is the future nobody<00:09:33.880> might<00:09:34.880> say<00:09:35.160> exactly<00:09:35.519> when<00:09:35.640> it<00:09:35.760> is 00:09:35.949 --> 00:09:35.959 align:start position:0% nobody might say exactly when it is 00:09:35.959 --> 00:09:39.670 align:start position:0% nobody might say exactly when it is maybe<00:09:36.200> it's<00:09:36.600> 2020<00:09:37.160> or<00:09:37.360> 20<00:09:38.160> 25<00:09:39.160> but<00:09:39.320> it's<00:09:39.480> going 00:09:39.670 --> 00:09:39.680 align:start position:0% maybe it's 2020 or 20 25 but it's going 00:09:39.680 --> 00:09:43.190 align:start position:0% maybe it's 2020 or 20 25 but it's going to<00:09:39.880> go<00:09:40.160> there<00:09:40.480> that's<00:09:41.000> pretty<00:09:41.640> clear<00:09:42.640> and<00:09:43.040> the 00:09:43.190 --> 00:09:43.200 align:start position:0% to go there that's pretty clear and the 00:09:43.200 --> 00:09:46.750 align:start position:0% to go there that's pretty clear and the mission<00:09:43.600> that<00:09:43.760> we<00:09:44.000> put<00:09:44.240> ourselves<00:09:45.040> for<00:09:45.399> MTN<00:09:46.120> is 00:09:46.750 --> 00:09:46.760 align:start position:0% mission that we put ourselves for MTN is 00:09:46.760 --> 00:09:49.069 align:start position:0% mission that we put ourselves for MTN is analytics<00:09:47.320> at<00:09:47.519> the 00:09:49.069 --> 00:09:49.079 align:start position:0% analytics at the 00:09:49.079 --> 00:09:52.110 align:start position:0% analytics at the edge<00:09:50.079> analytics<00:09:50.560> at<00:09:50.680> the<00:09:50.800> edge<00:09:51.079> means<00:09:51.880> if<00:09:52.000> you 00:09:52.110 --> 00:09:52.120 align:start position:0% edge analytics at the edge means if you 00:09:52.120 --> 00:09:55.190 align:start position:0% edge analytics at the edge means if you have<00:09:52.240> a<00:09:52.399> sensor<00:09:53.360> that<00:09:53.440> is<00:09:53.600> picking<00:09:53.839> up<00:09:54.200> data 00:09:55.190 --> 00:09:55.200 align:start position:0% have a sensor that is picking up data 00:09:55.200 --> 00:09:56.710 align:start position:0% have a sensor that is picking up data then<00:09:55.320> you<00:09:55.440> might<00:09:55.640> not<00:09:55.800> be<00:09:55.920> able<00:09:56.120> to<00:09:56.240> ship<00:09:56.480> it 00:09:56.710 --> 00:09:56.720 align:start position:0% then you might not be able to ship it 00:09:56.720 --> 00:09:58.150 align:start position:0% then you might not be able to ship it fast<00:09:56.959> enough<00:09:57.160> to<00:09:57.320> the<00:09:57.440> cloud<00:09:57.760> and<00:09:57.920> have<00:09:58.000> it 00:09:58.150 --> 00:09:58.160 align:start position:0% fast enough to the cloud and have it 00:09:58.160 --> 00:10:02.509 align:start position:0% fast enough to the cloud and have it analyzed<00:09:58.720> with<00:09:59.720> um<00:10:00.399> high<00:10:00.720> capacity<00:10:01.519> computers 00:10:02.509 --> 00:10:02.519 align:start position:0% analyzed with um high capacity computers 00:10:02.519 --> 00:10:04.630 align:start position:0% analyzed with um high capacity computers but<00:10:02.760> it's<00:10:03.000> possible<00:10:03.560> that<00:10:03.760> this<00:10:04.000> data<00:10:04.399> has<00:10:04.519> to 00:10:04.630 --> 00:10:04.640 align:start position:0% but it's possible that this data has to 00:10:04.640 --> 00:10:08.030 align:start position:0% but it's possible that this data has to be<00:10:04.760> selected<00:10:05.680> before<00:10:06.000> it<00:10:06.160> can<00:10:06.320> even<00:10:06.519> be 00:10:08.030 --> 00:10:08.040 align:start position:0% be selected before it can even be 00:10:08.040 --> 00:10:11.829 align:start position:0% be selected before it can even be shipped<00:10:09.440> and<00:10:10.440> it<00:10:10.560> seems<00:10:10.760> to<00:10:10.920> be<00:10:11.200> that<00:10:11.519> in<00:10:11.680> the 00:10:11.829 --> 00:10:11.839 align:start position:0% shipped and it seems to be that in the 00:10:11.839 --> 00:10:13.310 align:start position:0% shipped and it seems to be that in the moment 00:10:13.310 --> 00:10:13.320 align:start position:0% moment 00:10:13.320 --> 00:10:15.990 align:start position:0% moment 60%<00:10:14.320> of<00:10:14.480> all<00:10:14.640> the<00:10:14.760> data<00:10:15.040> that<00:10:15.160> is<00:10:15.399> collected<00:10:15.839> at 00:10:15.990 --> 00:10:16.000 align:start position:0% 60% of all the data that is collected at 00:10:16.000 --> 00:10:18.150 align:start position:0% 60% of all the data that is collected at the<00:10:16.160> edge<00:10:16.440> loses<00:10:16.839> its<00:10:17.040> value<00:10:17.320> within 00:10:18.150 --> 00:10:18.160 align:start position:0% the edge loses its value within 00:10:18.160 --> 00:10:20.710 align:start position:0% the edge loses its value within milliseconds<00:10:19.160> and<00:10:19.240> so<00:10:19.440> 90%<00:10:20.079> of<00:10:20.200> the<00:10:20.360> data<00:10:20.600> that 00:10:20.710 --> 00:10:20.720 align:start position:0% milliseconds and so 90% of the data that 00:10:20.720 --> 00:10:24.030 align:start position:0% milliseconds and so 90% of the data that is<00:10:20.920> collected<00:10:21.800> is<00:10:22.000> never<00:10:22.360> actually<00:10:22.920> used<00:10:23.920> and 00:10:24.030 --> 00:10:24.040 align:start position:0% is collected is never actually used and 00:10:24.040 --> 00:10:25.470 align:start position:0% is collected is never actually used and this<00:10:24.160> is<00:10:24.279> what<00:10:24.399> we<00:10:24.480> wanted<00:10:24.720> to<00:10:24.880> address<00:10:25.240> with 00:10:25.470 --> 00:10:25.480 align:start position:0% this is what we wanted to address with 00:10:25.480 --> 00:10:27.269 align:start position:0% this is what we wanted to address with the<00:10:25.760> exploration 00:10:27.269 --> 00:10:27.279 align:start position:0% the exploration 00:10:27.279 --> 00:10:30.230 align:start position:0% the exploration MTN<00:10:28.279> and<00:10:28.640> what<00:10:28.760> we<00:10:28.839> used<00:10:29.079> for<00:10:29.160> that 00:10:30.230 --> 00:10:30.240 align:start position:0% MTN and what we used for that 00:10:30.240 --> 00:10:33.150 align:start position:0% MTN and what we used for that um<00:10:30.440> and<00:10:30.760> what<00:10:30.880> we<00:10:31.000> looked<00:10:31.240> at<00:10:31.560> here<00:10:32.480> is<00:10:32.839> how<00:10:33.000> we 00:10:33.150 --> 00:10:33.160 align:start position:0% um and what we looked at here is how we 00:10:33.160 --> 00:10:37.150 align:start position:0% um and what we looked at here is how we can<00:10:33.399> use<00:10:34.160> um<00:10:35.000> technical 00:10:37.150 --> 00:10:37.160 align:start position:0% can use um technical 00:10:37.160 --> 00:10:40.350 align:start position:0% can use um technical um<00:10:38.160> behaviors<00:10:38.760> that<00:10:38.880> we<00:10:39.360> see<00:10:39.600> now<00:10:39.880> that<00:10:40.079> how<00:10:40.200> we 00:10:40.350 --> 00:10:40.360 align:start position:0% um behaviors that we see now that how we 00:10:40.360 --> 00:10:42.670 align:start position:0% um behaviors that we see now that how we have<00:10:40.760> real<00:10:41.040> time<00:10:41.240> processing<00:10:41.639> at<00:10:41.760> the<00:10:41.880> edge 00:10:42.670 --> 00:10:42.680 align:start position:0% have real time processing at the edge 00:10:42.680 --> 00:10:45.670 align:start position:0% have real time processing at the edge and<00:10:42.839> how<00:10:43.040> we<00:10:43.240> in<00:10:43.399> the<00:10:43.680> end<00:10:44.680> um<00:10:45.120> can<00:10:45.399> have 00:10:45.670 --> 00:10:45.680 align:start position:0% and how we in the end um can have 00:10:45.680 --> 00:10:47.389 align:start position:0% and how we in the end um can have security<00:10:46.240> containers<00:10:46.720> in<00:10:46.839> a<00:10:46.959> hostile 00:10:47.389 --> 00:10:47.399 align:start position:0% security containers in a hostile 00:10:47.399 --> 00:10:49.870 align:start position:0% security containers in a hostile environment<00:10:48.399> and<00:10:48.560> how<00:10:48.760> we<00:10:49.279> have<00:10:49.399> a<00:10:49.519> bottom 00:10:49.870 --> 00:10:49.880 align:start position:0% environment and how we have a bottom 00:10:49.880 --> 00:10:52.030 align:start position:0% environment and how we have a bottom line<00:10:50.320> that<00:10:50.800> gives<00:10:51.040> us<00:10:51.240> better<00:10:51.519> quality<00:10:51.839> of 00:10:52.030 --> 00:10:52.040 align:start position:0% line that gives us better quality of 00:10:52.040 --> 00:10:59.670 align:start position:0% line that gives us better quality of experience<00:10:52.480> hopefully 00:10:59.670 --> 00:10:59.680 align:start position:0% 00:10:59.680 --> 00:11:03.629 align:start position:0% so<00:11:00.680> this<00:11:00.800> is<00:11:00.959> how<00:11:01.079> it<00:11:01.200> looks<00:11:01.480> like<00:11:02.000> this<00:11:02.120> is<00:11:02.639> a 00:11:03.629 --> 00:11:03.639 align:start position:0% so this is how it looks like this is a 00:11:03.639 --> 00:11:08.269 align:start position:0% so this is how it looks like this is a um<00:11:04.440> software<00:11:05.480> defined<00:11:06.480> radio<00:11:07.440> and<00:11:07.560> it<00:11:07.720> has<00:11:08.000> 5 00:11:08.269 --> 00:11:08.279 align:start position:0% um software defined radio and it has 5 00:11:08.279 --> 00:11:10.389 align:start position:0% um software defined radio and it has 5 megabits<00:11:08.720> a<00:11:08.880> seconds<00:11:09.200> of<00:11:09.399> data<00:11:09.720> that<00:11:09.839> it 00:11:10.389 --> 00:11:10.399 align:start position:0% megabits a seconds of data that it 00:11:10.399 --> 00:11:13.190 align:start position:0% megabits a seconds of data that it collects<00:11:11.399> and<00:11:11.639> that<00:11:11.800> volume<00:11:12.240> is<00:11:12.560> enough<00:11:12.920> that 00:11:13.190 --> 00:11:13.200 align:start position:0% collects and that volume is enough that 00:11:13.200 --> 00:11:16.150 align:start position:0% collects and that volume is enough that you<00:11:13.360> cannot<00:11:13.720> actually<00:11:13.959> ship<00:11:14.279> it<00:11:14.839> from<00:11:15.440> our 00:11:16.150 --> 00:11:16.160 align:start position:0% you cannot actually ship it from our 00:11:16.160 --> 00:11:19.230 align:start position:0% you cannot actually ship it from our experimental<00:11:16.720> Raspberry<00:11:17.200> Pi<00:11:17.480> setup<00:11:18.320> to<00:11:18.920> uh<00:11:19.040> a 00:11:19.230 --> 00:11:19.240 align:start position:0% experimental Raspberry Pi setup to uh a 00:11:19.240 --> 00:11:22.310 align:start position:0% experimental Raspberry Pi setup to uh a central<00:11:19.560> Cloud<00:11:19.880> to<00:11:20.040> have<00:11:20.160> it<00:11:21.000> analyzed<00:11:22.000> so 00:11:22.310 --> 00:11:22.320 align:start position:0% central Cloud to have it analyzed so 00:11:22.320 --> 00:11:24.750 align:start position:0% central Cloud to have it analyzed so what<00:11:22.480> has<00:11:22.600> to<00:11:22.800> happen<00:11:23.160> is<00:11:24.160> um<00:11:24.320> create<00:11:24.600> an 00:11:24.750 --> 00:11:24.760 align:start position:0% what has to happen is um create an 00:11:24.760 --> 00:11:26.629 align:start position:0% what has to happen is um create an infrastructure<00:11:25.720> so<00:11:25.880> that<00:11:26.040> we<00:11:26.120> can<00:11:26.240> use<00:11:26.480> these 00:11:26.629 --> 00:11:26.639 align:start position:0% infrastructure so that we can use these 00:11:26.639 --> 00:11:28.590 align:start position:0% infrastructure so that we can use these little<00:11:26.880> devices<00:11:27.360> where<00:11:27.480> we<00:11:27.639> have<00:11:28.120> raspberry 00:11:28.590 --> 00:11:28.600 align:start position:0% little devices where we have raspberry 00:11:28.600 --> 00:11:30.310 align:start position:0% little devices where we have raspberry pies<00:11:28.880> that<00:11:29.000> end<00:11:29.360> points<00:11:29.639> that<00:11:29.760> are<00:11:30.079> our 00:11:30.310 --> 00:11:30.320 align:start position:0% pies that end points that are our 00:11:30.320 --> 00:11:34.750 align:start position:0% pies that end points that are our sensors<00:11:30.880> in<00:11:31.079> this<00:11:32.079> um<00:11:32.360> exploration<00:11:33.360> and<00:11:33.600> these 00:11:34.750 --> 00:11:34.760 align:start position:0% sensors in this um exploration and these 00:11:34.760 --> 00:11:38.829 align:start position:0% sensors in this um exploration and these software<00:11:35.760> um<00:11:36.519> radio<00:11:37.200> devices<00:11:38.200> uh<00:11:38.320> attached<00:11:38.680> to 00:11:38.829 --> 00:11:38.839 align:start position:0% software um radio devices uh attached to 00:11:38.839 --> 00:11:42.870 align:start position:0% software um radio devices uh attached to them<00:11:39.680> and<00:11:39.839> then<00:11:40.480> use<00:11:41.480> um<00:11:42.040> the<00:11:42.200> plethora<00:11:42.720> of 00:11:42.870 --> 00:11:42.880 align:start position:0% them and then use um the plethora of 00:11:42.880 --> 00:11:45.190 align:start position:0% them and then use um the plethora of data<00:11:43.200> that's<00:11:43.480> out<00:11:43.680> there<00:11:43.959> terabytes<00:11:44.600> actually 00:11:45.190 --> 00:11:45.200 align:start position:0% data that's out there terabytes actually 00:11:45.200 --> 00:11:46.550 align:start position:0% data that's out there terabytes actually that<00:11:45.360> you<00:11:45.480> have<00:11:45.680> access<00:11:45.920> to<00:11:46.200> this<00:11:46.320> is<00:11:46.440> the 00:11:46.550 --> 00:11:46.560 align:start position:0% that you have access to this is the 00:11:46.560 --> 00:11:49.949 align:start position:0% that you have access to this is the United<00:11:46.959> States<00:11:47.480> frequency<00:11:48.480> allocation<00:11:49.480> and 00:11:49.949 --> 00:11:49.959 align:start position:0% United States frequency allocation and 00:11:49.959 --> 00:11:51.990 align:start position:0% United States frequency allocation and zoom<00:11:50.240> in<00:11:50.519> into<00:11:50.760> some<00:11:50.959> frequency<00:11:51.519> where<00:11:51.680> we<00:11:51.800> can 00:11:51.990 --> 00:11:52.000 align:start position:0% zoom in into some frequency where we can 00:11:52.000 --> 00:11:55.190 align:start position:0% zoom in into some frequency where we can find<00:11:52.360> interesting<00:11:52.839> data<00:11:53.279> for<00:11:53.600> example<00:11:54.600> um<00:11:55.079> we 00:11:55.190 --> 00:11:55.200 align:start position:0% find interesting data for example um we 00:11:55.200 --> 00:11:57.550 align:start position:0% find interesting data for example um we have<00:11:55.360> Smart<00:11:55.639> Meters<00:11:56.560> at<00:11:56.680> some<00:11:56.880> point<00:11:57.160> we<00:11:57.279> also 00:11:57.550 --> 00:11:57.560 align:start position:0% have Smart Meters at some point we also 00:11:57.560 --> 00:11:59.310 align:start position:0% have Smart Meters at some point we also have<00:11:57.800> other<00:11:58.040> stuff<00:11:58.320> like<00:11:58.480> aircraft<00:11:58.880> radio 00:11:59.310 --> 00:11:59.320 align:start position:0% have other stuff like aircraft radio 00:11:59.320 --> 00:12:01.790 align:start position:0% have other stuff like aircraft radio navigation<00:11:59.800> where<00:11:59.920> you<00:12:00.000> can<00:12:00.240> track<00:12:00.800> aircraft 00:12:01.790 --> 00:12:01.800 align:start position:0% navigation where you can track aircraft 00:12:01.800 --> 00:12:03.949 align:start position:0% navigation where you can track aircraft of<00:12:01.920> course<00:12:02.120> mobile<00:12:02.440> and<00:12:02.639> FM<00:12:03.120> is<00:12:03.360> taking<00:12:03.639> up<00:12:03.800> big 00:12:03.949 --> 00:12:03.959 align:start position:0% of course mobile and FM is taking up big 00:12:03.959 --> 00:12:07.230 align:start position:0% of course mobile and FM is taking up big swaths<00:12:04.399> of<00:12:04.600> this<00:12:04.920> but<00:12:05.800> um<00:12:06.279> we<00:12:06.399> are<00:12:06.600> focusing<00:12:07.000> on 00:12:07.230 --> 00:12:07.240 align:start position:0% swaths of this but um we are focusing on 00:12:07.240 --> 00:12:08.750 align:start position:0% swaths of this but um we are focusing on something<00:12:07.519> simple<00:12:07.839> and<00:12:08.000> that<00:12:08.120> is<00:12:08.480> just<00:12:08.639> the 00:12:08.750 --> 00:12:08.760 align:start position:0% something simple and that is just the 00:12:08.760 --> 00:12:11.269 align:start position:0% something simple and that is just the water<00:12:09.000> and<00:12:09.200> power<00:12:09.399> meter<00:12:09.920> output<00:12:10.920> and<00:12:11.040> this<00:12:11.160> is 00:12:11.269 --> 00:12:11.279 align:start position:0% water and power meter output and this is 00:12:11.279 --> 00:12:12.990 align:start position:0% water and power meter output and this is how<00:12:11.399> it<00:12:11.600> actually<00:12:11.839> looks<00:12:12.320> if<00:12:12.440> you<00:12:12.560> read<00:12:12.800> that 00:12:12.990 --> 00:12:13.000 align:start position:0% how it actually looks if you read that 00:12:13.000 --> 00:12:15.990 align:start position:0% how it actually looks if you read that out<00:12:13.920> um<00:12:14.320> interestingly<00:12:15.320> in<00:12:15.480> America<00:12:15.880> there 00:12:15.990 --> 00:12:16.000 align:start position:0% out um interestingly in America there 00:12:16.000 --> 00:12:17.629 align:start position:0% out um interestingly in America there seems<00:12:16.199> to<00:12:16.279> be<00:12:16.399> no<00:12:16.600> protection<00:12:16.959> at<00:12:17.079> all<00:12:17.279> you<00:12:17.360> can 00:12:17.629 --> 00:12:17.639 align:start position:0% seems to be no protection at all you can 00:12:17.639 --> 00:12:18.829 align:start position:0% seems to be no protection at all you can read<00:12:17.920> all<00:12:18.040> the<00:12:18.120> meters<00:12:18.440> of<00:12:18.600> all<00:12:18.720> your 00:12:18.829 --> 00:12:18.839 align:start position:0% read all the meters of all your 00:12:18.839 --> 00:12:21.030 align:start position:0% read all the meters of all your neighbors<00:12:19.240> in<00:12:19.360> the<00:12:19.519> moment<00:12:20.519> um<00:12:20.680> maybe<00:12:20.880> that's 00:12:21.030 --> 00:12:21.040 align:start position:0% neighbors in the moment um maybe that's 00:12:21.040 --> 00:12:23.590 align:start position:0% neighbors in the moment um maybe that's not<00:12:21.120> going<00:12:21.240> to<00:12:21.320> stay<00:12:21.560> like<00:12:21.760> that<00:12:22.079> but<00:12:22.600> uh<00:12:23.399> for 00:12:23.590 --> 00:12:23.600 align:start position:0% not going to stay like that but uh for 00:12:23.600 --> 00:12:26.629 align:start position:0% not going to stay like that but uh for experimental<00:12:24.160> purposes<00:12:24.680> that<00:12:25.440> uh<00:12:26.279> may<00:12:26.440> be 00:12:26.629 --> 00:12:26.639 align:start position:0% experimental purposes that uh may be 00:12:26.639 --> 00:12:27.430 align:start position:0% experimental purposes that uh may be quite 00:12:27.430 --> 00:12:27.440 align:start position:0% quite 00:12:27.440 --> 00:12:29.750 align:start position:0% quite interesting<00:12:28.440> um<00:12:28.600> you<00:12:28.680> can<00:12:28.839> also<00:12:29.160> track<00:12:29.360> flight 00:12:29.750 --> 00:12:29.760 align:start position:0% interesting um you can also track flight 00:12:29.760 --> 00:12:33.310 align:start position:0% interesting um you can also track flight data<00:12:30.760> um<00:12:31.079> that<00:12:31.639> is<00:12:31.920> is<00:12:32.079> another<00:12:32.800> possibility 00:12:33.310 --> 00:12:33.320 align:start position:0% data um that is is another possibility 00:12:33.320 --> 00:12:34.670 align:start position:0% data um that is is another possibility this<00:12:33.440> is<00:12:33.600> how<00:12:33.800> this<00:12:33.920> looks<00:12:34.160> if<00:12:34.279> you<00:12:34.360> read<00:12:34.560> it 00:12:34.670 --> 00:12:34.680 align:start position:0% this is how this looks if you read it 00:12:34.680 --> 00:12:37.350 align:start position:0% this is how this looks if you read it out<00:12:34.880> of<00:12:35.199> the<00:12:35.760> uh<00:12:35.880> radio 00:12:37.350 --> 00:12:37.360 align:start position:0% out of the uh radio 00:12:37.360 --> 00:12:40.110 align:start position:0% out of the uh radio frequencies<00:12:38.360> so<00:12:38.680> for<00:12:38.880> our<00:12:39.399> um<00:12:39.600> experimental 00:12:40.110 --> 00:12:40.120 align:start position:0% frequencies so for our um experimental 00:12:40.120 --> 00:12:42.550 align:start position:0% frequencies so for our um experimental setup<00:12:40.480> we<00:12:40.600> have<00:12:40.760> a<00:12:40.839> couple<00:12:41.079> of<00:12:41.199> personas<00:12:41.720> here 00:12:42.550 --> 00:12:42.560 align:start position:0% setup we have a couple of personas here 00:12:42.560 --> 00:12:44.069 align:start position:0% setup we have a couple of personas here um<00:12:42.800> we<00:12:42.920> have<00:12:43.040> the<00:12:43.160> device<00:12:43.480> itself<00:12:43.839> that's<00:12:43.959> the 00:12:44.069 --> 00:12:44.079 align:start position:0% um we have the device itself that's the 00:12:44.079 --> 00:12:46.990 align:start position:0% um we have the device itself that's the Raspberry<00:12:44.560> Pi<00:12:45.279> we<00:12:45.440> have<00:12:45.560> the<00:12:45.680> device<00:12:46.040> contract 00:12:46.990 --> 00:12:47.000 align:start position:0% Raspberry Pi we have the device contract 00:12:47.000 --> 00:12:48.790 align:start position:0% Raspberry Pi we have the device contract that<00:12:47.160> is<00:12:47.720> um<00:12:47.880> the<00:12:48.000> contracts<00:12:48.480> that<00:12:48.600> are 00:12:48.790 --> 00:12:48.800 align:start position:0% that is um the contracts that are 00:12:48.800 --> 00:12:50.670 align:start position:0% that is um the contracts that are actually<00:12:49.160> that<00:12:49.639> ethereum<00:12:50.199> contracts<00:12:50.600> that 00:12:50.670 --> 00:12:50.680 align:start position:0% actually that ethereum contracts that 00:12:50.680 --> 00:12:52.470 align:start position:0% actually that ethereum contracts that are<00:12:50.839> actually<00:12:51.040> entered<00:12:51.399> in<00:12:51.959> between<00:12:52.279> the 00:12:52.470 --> 00:12:52.480 align:start position:0% are actually entered in between the 00:12:52.480 --> 00:12:56.030 align:start position:0% are actually entered in between the devices<00:12:53.320> and<00:12:53.680> a<00:12:54.320> central<00:12:55.120> token<00:12:55.600> Bank 00:12:56.030 --> 00:12:56.040 align:start position:0% devices and a central token Bank 00:12:56.040 --> 00:12:58.350 align:start position:0% devices and a central token Bank contract<00:12:57.000> we<00:12:57.160> have<00:12:57.279> the<00:12:57.519> device<00:12:57.839> registry 00:12:58.350 --> 00:12:58.360 align:start position:0% contract we have the device registry 00:12:58.360 --> 00:12:59.670 align:start position:0% contract we have the device registry that<00:12:58.519> basically<00:12:58.800> knows<00:12:59.240> everything<00:12:59.519> about 00:12:59.670 --> 00:12:59.680 align:start position:0% that basically knows everything about 00:12:59.680 --> 00:13:01.189 align:start position:0% that basically knows everything about all<00:12:59.800> the<00:12:59.920> devices<00:13:00.279> in<00:13:00.440> the<00:13:00.600> system<00:13:00.880> for<00:13:01.040> our 00:13:01.189 --> 00:13:01.199 align:start position:0% all the devices in the system for our 00:13:01.199 --> 00:13:03.790 align:start position:0% all the devices in the system for our setup<00:13:01.959> and<00:13:02.079> then<00:13:02.199> we<00:13:02.279> have<00:13:02.560> glansen<00:13:03.560> which<00:13:03.680> is 00:13:03.790 --> 00:13:03.800 align:start position:0% setup and then we have glansen which is 00:13:03.800 --> 00:13:06.550 align:start position:0% setup and then we have glansen which is a<00:13:03.959> producer<00:13:04.600> of<00:13:04.839> Docker<00:13:05.279> containers<00:13:06.279> that<00:13:06.399> are 00:13:06.550 --> 00:13:06.560 align:start position:0% a producer of Docker containers that are 00:13:06.560 --> 00:13:08.150 align:start position:0% a producer of Docker containers that are actually<00:13:06.720> shipped<00:13:07.040> out<00:13:07.240> to<00:13:07.360> the<00:13:07.519> devices<00:13:07.959> that 00:13:08.150 --> 00:13:08.160 align:start position:0% actually shipped out to the devices that 00:13:08.160 --> 00:13:12.550 align:start position:0% actually shipped out to the devices that those<00:13:08.519> devices<00:13:09.560> employ<00:13:10.800> deploy<00:13:11.800> and<00:13:12.199> that<00:13:12.320> are 00:13:12.550 --> 00:13:12.560 align:start position:0% those devices employ deploy and that are 00:13:12.560 --> 00:13:14.629 align:start position:0% those devices employ deploy and that are then<00:13:12.839> having<00:13:13.160> basically<00:13:13.480> the<00:13:13.600> entire<00:13:13.959> logic 00:13:14.629 --> 00:13:14.639 align:start position:0% then having basically the entire logic 00:13:14.639 --> 00:13:16.629 align:start position:0% then having basically the entire logic that<00:13:14.760> is<00:13:14.920> needed<00:13:15.240> to<00:13:15.480> ship<00:13:15.920> to<00:13:16.079> make<00:13:16.279> to<00:13:16.399> enter 00:13:16.629 --> 00:13:16.639 align:start position:0% that is needed to ship to make to enter 00:13:16.639 --> 00:13:19.310 align:start position:0% that is needed to ship to make to enter into<00:13:17.399> negotiations<00:13:18.399> and<00:13:18.519> to<00:13:18.639> ship<00:13:18.880> the<00:13:19.000> data 00:13:19.310 --> 00:13:19.320 align:start position:0% into negotiations and to ship the data 00:13:19.320 --> 00:13:22.269 align:start position:0% into negotiations and to ship the data home<00:13:20.079> to<00:13:20.240> a 00:13:22.269 --> 00:13:22.279 align:start position:0% home to a 00:13:22.279 --> 00:13:24.710 align:start position:0% home to a consumer<00:13:23.279> this<00:13:23.399> is<00:13:23.600> how<00:13:24.240> um<00:13:24.560> the 00:13:24.710 --> 00:13:24.720 align:start position:0% consumer this is how um the 00:13:24.720 --> 00:13:25.829 align:start position:0% consumer this is how um the infrastructure 00:13:25.829 --> 00:13:25.839 align:start position:0% infrastructure 00:13:25.839 --> 00:13:29.310 align:start position:0% infrastructure looks<00:13:26.839> um<00:13:27.320> up<00:13:27.519> on<00:13:27.639> the<00:13:27.839> top<00:13:28.040> you<00:13:28.240> have<00:13:28.639> the<00:13:29.199> uh 00:13:29.310 --> 00:13:29.320 align:start position:0% looks um up on the top you have the uh 00:13:29.320 --> 00:13:32.829 align:start position:0% looks um up on the top you have the uh raspberry<00:13:30.320> pies<00:13:31.320> um<00:13:32.320> down<00:13:32.519> here<00:13:32.639> in<00:13:32.760> the 00:13:32.829 --> 00:13:32.839 align:start position:0% raspberry pies um down here in the 00:13:32.839 --> 00:13:34.829 align:start position:0% raspberry pies um down here in the middle<00:13:33.160> you<00:13:33.320> have<00:13:33.560> the<00:13:34.120> um<00:13:34.360> Contracting 00:13:34.829 --> 00:13:34.839 align:start position:0% middle you have the um Contracting 00:13:34.839 --> 00:13:36.710 align:start position:0% middle you have the um Contracting server<00:13:35.320> that<00:13:35.440> is<00:13:35.600> the<00:13:35.800> consumer<00:13:36.199> of<00:13:36.320> the<00:13:36.440> data 00:13:36.710 --> 00:13:36.720 align:start position:0% server that is the consumer of the data 00:13:36.720 --> 00:13:38.230 align:start position:0% server that is the consumer of the data that<00:13:36.880> actually<00:13:37.240> is<00:13:37.360> willing<00:13:37.639> to<00:13:37.800> pay<00:13:37.959> for<00:13:38.120> the 00:13:38.230 --> 00:13:38.240 align:start position:0% that actually is willing to pay for the 00:13:38.240 --> 00:13:40.629 align:start position:0% that actually is willing to pay for the data<00:13:38.560> and<00:13:38.680> wants<00:13:38.920> the<00:13:39.079> data<00:13:39.320> to<00:13:39.480> be<00:13:39.800> to<00:13:40.240> um<00:13:40.480> to 00:13:40.629 --> 00:13:40.639 align:start position:0% data and wants the data to be to um to 00:13:40.639 --> 00:13:42.590 align:start position:0% data and wants the data to be to um to have<00:13:40.760> the<00:13:40.880> data<00:13:41.160> delivered<00:13:42.160> from<00:13:42.399> the 00:13:42.590 --> 00:13:42.600 align:start position:0% have the data delivered from the 00:13:42.600 --> 00:13:44.150 align:start position:0% have the data delivered from the raspberry 00:13:44.150 --> 00:13:44.160 align:start position:0% raspberry 00:13:44.160 --> 00:13:50.110 align:start position:0% raspberry pies<00:13:45.160> oops 00:13:50.110 --> 00:13:50.120 align:start position:0% 00:13:50.120 --> 00:13:52.430 align:start position:0% sorry<00:13:51.120> oh<00:13:51.399> sorry<00:13:51.639> it's<00:13:51.759> out<00:13:51.920> of<00:13:52.040> power<00:13:52.240> for 00:13:52.430 --> 00:13:52.440 align:start position:0% sorry oh sorry it's out of power for 00:13:52.440 --> 00:14:00.430 align:start position:0% sorry oh sorry it's out of power for good<00:13:53.120> somebody<00:13:53.360> can<00:13:53.560> help<00:13:53.720> me 00:14:00.430 --> 00:14:00.440 align:start position:0% 00:14:00.440 --> 00:14:01.829 align:start position:0% I<00:14:00.519> have<00:14:00.680> one<00:14:00.880> it's<00:14:01.040> fine<00:14:01.279> there's<00:14:01.440> one<00:14:01.639> on<00:14:01.720> the 00:14:01.829 --> 00:14:01.839 align:start position:0% I have one it's fine there's one on the 00:14:01.839 --> 00:14:42.030 align:start position:0% I have one it's fine there's one on the ground<00:14:02.040> ready<00:14:02.240> plug<00:14:02.480> in<00:14:02.880> oh 00:14:42.030 --> 00:14:42.040 align:start position:0% 00:14:42.040 --> 00:14:45.069 align:start position:0% not<00:14:43.040> okay 00:14:45.069 --> 00:14:45.079 align:start position:0% not okay 00:14:45.079 --> 00:14:48.829 align:start position:0% not okay so<00:14:46.079> the<00:14:46.199> main<00:14:46.519> aspect<00:14:47.320> um<00:14:48.040> what<00:14:48.240> ethereum<00:14:48.680> is 00:14:48.829 --> 00:14:48.839 align:start position:0% so the main aspect um what ethereum is 00:14:48.839 --> 00:14:50.230 align:start position:0% so the main aspect um what ethereum is actually<00:14:49.000> used<00:14:49.279> for<00:14:49.639> and<00:14:49.759> that's<00:14:50.000> that's<00:14:50.120> the 00:14:50.230 --> 00:14:50.240 align:start position:0% actually used for and that's that's the 00:14:50.240 --> 00:14:52.230 align:start position:0% actually used for and that's that's the important<00:14:50.600> thing<00:14:50.839> here<00:14:51.079> because<00:14:51.639> I<00:14:51.880> I've 00:14:52.230 --> 00:14:52.240 align:start position:0% important thing here because I I've 00:14:52.240 --> 00:14:54.069 align:start position:0% important thing here because I I've often<00:14:52.519> encountered<00:14:53.000> the<00:14:53.160> question<00:14:53.800> why<00:14:53.959> do 00:14:54.069 --> 00:14:54.079 align:start position:0% often encountered the question why do 00:14:54.079 --> 00:14:56.710 align:start position:0% often encountered the question why do you<00:14:54.199> need<00:14:54.440> blockchain<00:14:54.920> for<00:14:55.279> iot<00:14:56.279> and<00:14:56.360> the<00:14:56.480> main 00:14:56.710 --> 00:14:56.720 align:start position:0% you need blockchain for iot and the main 00:14:56.720 --> 00:14:59.189 align:start position:0% you need blockchain for iot and the main aspect<00:14:57.000> is<00:14:57.160> really<00:14:57.360> the<00:14:57.519> negotiation 00:14:59.189 --> 00:14:59.199 align:start position:0% aspect is really the negotiation 00:14:59.199 --> 00:15:01.350 align:start position:0% aspect is really the negotiation to<00:14:59.480> negotiate<00:14:59.959> between<00:15:00.279> devices<00:15:01.199> and 00:15:01.350 --> 00:15:01.360 align:start position:0% to negotiate between devices and 00:15:01.360 --> 00:15:04.389 align:start position:0% to negotiate between devices and endpoints<00:15:02.320> in<00:15:02.440> an<00:15:02.600> untrusted<00:15:03.399> environment 00:15:04.389 --> 00:15:04.399 align:start position:0% endpoints in an untrusted environment 00:15:04.399 --> 00:15:06.350 align:start position:0% endpoints in an untrusted environment that<00:15:04.480> is<00:15:04.639> what<00:15:04.800> we're<00:15:04.959> using<00:15:05.279> ethereum<00:15:05.759> for 00:15:06.350 --> 00:15:06.360 align:start position:0% that is what we're using ethereum for 00:15:06.360 --> 00:15:09.430 align:start position:0% that is what we're using ethereum for and<00:15:06.519> that<00:15:06.720> is<00:15:07.199> the<00:15:07.360> whole<00:15:07.839> mechanism<00:15:08.519> of<00:15:09.240> the 00:15:09.430 --> 00:15:09.440 align:start position:0% and that is the whole mechanism of the 00:15:09.440 --> 00:15:12.990 align:start position:0% and that is the whole mechanism of the devices<00:15:10.120> offering<00:15:11.120> their<00:15:11.360> data<00:15:12.000> the<00:15:12.160> central 00:15:12.990 --> 00:15:13.000 align:start position:0% devices offering their data the central 00:15:13.000 --> 00:15:14.790 align:start position:0% devices offering their data the central consumer<00:15:13.440> of<00:15:13.600> the<00:15:13.720> data<00:15:14.160> accepting<00:15:14.519> that 00:15:14.790 --> 00:15:14.800 align:start position:0% consumer of the data accepting that 00:15:14.800 --> 00:15:18.910 align:start position:0% consumer of the data accepting that offer<00:15:15.800> um<00:15:15.920> creating<00:15:16.240> an<00:15:16.399> escra<00:15:17.160> where<00:15:17.800> the<00:15:18.440> uh 00:15:18.910 --> 00:15:18.920 align:start position:0% offer um creating an escra where the uh 00:15:18.920 --> 00:15:21.509 align:start position:0% offer um creating an escra where the uh the<00:15:19.000> future<00:15:19.360> payment<00:15:19.759> is<00:15:20.079> put<00:15:21.000> uh<00:15:21.120> for<00:15:21.360> the 00:15:21.509 --> 00:15:21.519 align:start position:0% the future payment is put uh for the 00:15:21.519 --> 00:15:24.430 align:start position:0% the future payment is put uh for the devices<00:15:21.920> then<00:15:22.079> to<00:15:22.199> ship<00:15:22.480> the<00:15:23.040> data<00:15:24.040> um<00:15:24.320> which 00:15:24.430 --> 00:15:24.440 align:start position:0% devices then to ship the data um which 00:15:24.440 --> 00:15:27.590 align:start position:0% devices then to ship the data um which is<00:15:24.800> out<00:15:24.959> of<00:15:25.120> Bend<00:15:25.920> uh<00:15:26.680> and<00:15:26.839> then<00:15:27.120> and<00:15:27.399> in<00:15:27.519> the 00:15:27.590 --> 00:15:27.600 align:start position:0% is out of Bend uh and then and in the 00:15:27.600 --> 00:15:29.590 align:start position:0% is out of Bend uh and then and in the end<00:15:27.800> to<00:15:28.040> pay<00:15:28.319> out<00:15:28.440> of<00:15:28.560> the<00:15:28.680> ES 00:15:29.590 --> 00:15:29.600 align:start position:0% end to pay out of the ES 00:15:29.600 --> 00:15:32.749 align:start position:0% end to pay out of the ES when<00:15:30.160> the<00:15:30.360> data<00:15:30.639> has<00:15:30.800> been<00:15:30.959> shipped<00:15:31.920> so<00:15:32.600> and 00:15:32.749 --> 00:15:32.759 align:start position:0% when the data has been shipped so and 00:15:32.759 --> 00:15:35.030 align:start position:0% when the data has been shipped so and that<00:15:32.959> is<00:15:33.199> basically<00:15:33.639> the<00:15:33.800> main<00:15:34.440> um<00:15:34.680> point<00:15:34.920> of 00:15:35.030 --> 00:15:35.040 align:start position:0% that is basically the main um point of 00:15:35.040 --> 00:15:37.069 align:start position:0% that is basically the main um point of the<00:15:35.160> whole<00:15:35.360> experiment<00:15:35.839> to<00:15:36.000> see<00:15:36.600> whether<00:15:36.880> that 00:15:37.069 --> 00:15:37.079 align:start position:0% the whole experiment to see whether that 00:15:37.079 --> 00:15:39.790 align:start position:0% the whole experiment to see whether that in<00:15:37.199> a<00:15:37.480> fashion<00:15:37.759> that<00:15:37.920> scales<00:15:38.639> sufficiently<00:15:39.639> um 00:15:39.790 --> 00:15:39.800 align:start position:0% in a fashion that scales sufficiently um 00:15:39.800 --> 00:15:42.590 align:start position:0% in a fashion that scales sufficiently um can<00:15:40.000> actually<00:15:40.240> be<00:15:40.399> done<00:15:40.639> using<00:15:41.240> ethereum<00:15:42.240> and 00:15:42.590 --> 00:15:42.600 align:start position:0% can actually be done using ethereum and 00:15:42.600 --> 00:15:46.949 align:start position:0% can actually be done using ethereum and at<00:15:42.759> this<00:15:42.959> point<00:15:43.279> I<00:15:43.360> would<00:15:43.600> say<00:15:44.319> um<00:15:44.959> it<00:15:45.120> is<00:15:45.199> a 00:15:46.949 --> 00:15:46.959 align:start position:0% at this point I would say um it is a 00:15:46.959 --> 00:15:49.150 align:start position:0% at this point I would say um it is a success<00:15:47.959> so<00:15:48.160> this<00:15:48.279> is<00:15:48.440> how<00:15:48.600> a<00:15:48.720> proof<00:15:48.920> of 00:15:49.150 --> 00:15:49.160 align:start position:0% success so this is how a proof of 00:15:49.160 --> 00:15:53.150 align:start position:0% success so this is how a proof of concept<00:15:50.160> uh<00:15:50.319> looked<00:15:50.800> like<00:15:51.800> it's<00:15:52.120> actually 00:15:53.150 --> 00:15:53.160 align:start position:0% concept uh looked like it's actually 00:15:53.160 --> 00:15:56.269 align:start position:0% concept uh looked like it's actually emulated<00:15:54.160> uh<00:15:54.639> simulated<00:15:55.639> we<00:15:55.800> didn't<00:15:56.040> have 00:15:56.269 --> 00:15:56.279 align:start position:0% emulated uh simulated we didn't have 00:15:56.279 --> 00:15:58.670 align:start position:0% emulated uh simulated we didn't have quite<00:15:56.480> as<00:15:56.639> many<00:15:57.480> points<00:15:57.880> there<00:15:58.079> but<00:15:58.199> we<00:15:58.319> zeroed 00:15:58.670 --> 00:15:58.680 align:start position:0% quite as many points there but we zeroed 00:15:58.680 --> 00:15:59.590 align:start position:0% quite as many points there but we zeroed in 00:15:59.590 --> 00:15:59.600 align:start position:0% in 00:15:59.600 --> 00:16:01.949 align:start position:0% in on<00:15:59.920> some<00:16:00.279> that<00:16:00.560> that<00:16:00.639> were<00:16:00.839> actually<00:16:01.040> running 00:16:01.949 --> 00:16:01.959 align:start position:0% on some that that were actually running 00:16:01.959 --> 00:16:04.590 align:start position:0% on some that that were actually running then<00:16:02.120> you<00:16:02.240> could<00:16:02.440> see<00:16:03.040> what<00:16:03.279> data<00:16:04.160> um<00:16:04.360> was 00:16:04.590 --> 00:16:04.600 align:start position:0% then you could see what data um was 00:16:04.600 --> 00:16:06.590 align:start position:0% then you could see what data um was actually<00:16:05.000> there<00:16:05.600> to<00:16:05.920> and<00:16:06.079> what<00:16:06.240> connections 00:16:06.590 --> 00:16:06.600 align:start position:0% actually there to and what connections 00:16:06.600 --> 00:16:08.150 align:start position:0% actually there to and what connections were<00:16:06.759> endpoints<00:16:07.160> were<00:16:07.360> actually<00:16:07.600> there<00:16:07.800> to<00:16:07.959> be 00:16:08.150 --> 00:16:08.160 align:start position:0% were endpoints were actually there to be 00:16:08.160 --> 00:16:10.069 align:start position:0% were endpoints were actually there to be consumed<00:16:08.720> you<00:16:08.880> could<00:16:09.040> have<00:16:09.240> a<00:16:09.519> device 00:16:10.069 --> 00:16:10.079 align:start position:0% consumed you could have a device 00:16:10.079 --> 00:16:11.949 align:start position:0% consumed you could have a device registration<00:16:11.079> where<00:16:11.240> a<00:16:11.360> device<00:16:11.680> can<00:16:11.800> be 00:16:11.949 --> 00:16:11.959 align:start position:0% registration where a device can be 00:16:11.959 --> 00:16:14.389 align:start position:0% registration where a device can be registered<00:16:12.800> um<00:16:12.959> so<00:16:13.160> that<00:16:13.279> it<00:16:13.399> can<00:16:13.519> be<00:16:13.720> in<00:16:14.199> take 00:16:14.389 --> 00:16:14.399 align:start position:0% registered um so that it can be in take 00:16:14.399 --> 00:16:15.670 align:start position:0% registered um so that it can be in take part<00:16:14.600> in<00:16:14.720> the 00:16:15.670 --> 00:16:15.680 align:start position:0% part in the 00:16:15.680 --> 00:16:18.670 align:start position:0% part in the marketplace<00:16:16.680> we<00:16:16.880> then<00:16:17.160> have<00:16:17.839> uh<00:16:18.319> the<00:16:18.480> view 00:16:18.670 --> 00:16:18.680 align:start position:0% marketplace we then have uh the view 00:16:18.680 --> 00:16:20.150 align:start position:0% marketplace we then have uh the view here<00:16:18.800> of<00:16:18.920> the<00:16:19.000> blockchain<00:16:19.399> how<00:16:19.519> it<00:16:19.639> looks<00:16:19.880> when 00:16:20.150 --> 00:16:20.160 align:start position:0% here of the blockchain how it looks when 00:16:20.160 --> 00:16:21.870 align:start position:0% here of the blockchain how it looks when these<00:16:20.319> devices<00:16:20.759> actually<00:16:20.959> starting<00:16:21.319> to 00:16:21.870 --> 00:16:21.880 align:start position:0% these devices actually starting to 00:16:21.880 --> 00:16:23.509 align:start position:0% these devices actually starting to communicate<00:16:22.360> with<00:16:22.560> each<00:16:22.720> other<00:16:23.160> and<00:16:23.399> and 00:16:23.509 --> 00:16:23.519 align:start position:0% communicate with each other and and 00:16:23.519 --> 00:16:25.389 align:start position:0% communicate with each other and and starting<00:16:23.839> to<00:16:23.959> enter<00:16:24.279> contracts<00:16:24.720> with<00:16:24.880> each 00:16:25.389 --> 00:16:25.399 align:start position:0% starting to enter contracts with each 00:16:25.399 --> 00:16:31.069 align:start position:0% starting to enter contracts with each other<00:16:26.399> and<00:16:26.639> this<00:16:26.759> is<00:16:27.199> how<00:16:28.199> um<00:16:28.600> the<00:16:29.319> actual<00:16:30.319> flow 00:16:31.069 --> 00:16:31.079 align:start position:0% other and this is how um the actual flow 00:16:31.079 --> 00:16:32.870 align:start position:0% other and this is how um the actual flow within<00:16:31.480> the<00:16:31.759> different<00:16:32.079> players<00:16:32.519> in<00:16:32.680> the 00:16:32.870 --> 00:16:32.880 align:start position:0% within the different players in the 00:16:32.880 --> 00:16:35.389 align:start position:0% within the different players in the system<00:16:33.160> worked<00:16:33.519> I<00:16:33.639> I<00:16:33.720> won't<00:16:33.920> go<00:16:34.079> through<00:16:34.399> it 00:16:35.389 --> 00:16:35.399 align:start position:0% system worked I I won't go through it 00:16:35.399 --> 00:16:39.470 align:start position:0% system worked I I won't go through it step<00:16:35.639> by<00:16:35.839> step<00:16:36.000> in<00:16:36.120> the<00:16:36.199> moment<00:16:36.480> here<00:16:36.720> but 00:16:39.470 --> 00:16:39.480 align:start position:0% 00:16:39.480 --> 00:16:42.230 align:start position:0% um<00:16:40.480> it's<00:16:41.040> just<00:16:41.279> I<00:16:41.560> you<00:16:41.680> you're<00:16:41.839> getting<00:16:42.079> the 00:16:42.230 --> 00:16:42.240 align:start position:0% um it's just I you you're getting the 00:16:42.240 --> 00:16:44.269 align:start position:0% um it's just I you you're getting the idea<00:16:42.639> it's<00:16:42.920> it's<00:16:43.120> quite<00:16:43.279> straightforward 00:16:44.269 --> 00:16:44.279 align:start position:0% idea it's it's quite straightforward 00:16:44.279 --> 00:16:47.150 align:start position:0% idea it's it's quite straightforward actually<00:16:45.279> and<00:16:45.639> in<00:16:45.759> the<00:16:45.920> end<00:16:46.360> this<00:16:46.480> is<00:16:46.680> the<00:16:47.040> this 00:16:47.150 --> 00:16:47.160 align:start position:0% actually and in the end this is the this 00:16:47.160 --> 00:16:48.590 align:start position:0% actually and in the end this is the this was<00:16:47.279> the<00:16:47.360> bootstrapping<00:16:47.920> flow<00:16:48.240> actually<00:16:48.440> to 00:16:48.590 --> 00:16:48.600 align:start position:0% was the bootstrapping flow actually to 00:16:48.600 --> 00:16:51.470 align:start position:0% was the bootstrapping flow actually to enter<00:16:48.920> into<00:16:49.199> the<00:16:49.720> um<00:16:50.560> to<00:16:50.720> get<00:16:50.839> a<00:16:50.959> container<00:16:51.319> to 00:16:51.470 --> 00:16:51.480 align:start position:0% enter into the um to get a container to 00:16:51.480 --> 00:16:54.110 align:start position:0% enter into the um to get a container to a<00:16:51.680> device<00:16:52.000> so<00:16:52.399> the<00:16:52.519> whole<00:16:52.720> system<00:16:53.079> can<00:16:53.240> start 00:16:54.110 --> 00:16:54.120 align:start position:0% a device so the whole system can start 00:16:54.120 --> 00:16:55.990 align:start position:0% a device so the whole system can start and<00:16:54.240> this<00:16:54.360> is<00:16:54.480> the<00:16:54.639> flow<00:16:55.519> um<00:16:55.720> when<00:16:55.880> the 00:16:55.990 --> 00:16:56.000 align:start position:0% and this is the flow um when the 00:16:56.000 --> 00:16:59.389 align:start position:0% and this is the flow um when the container<00:16:56.440> actually<00:16:56.920> runs<00:16:57.920> where<00:16:58.079> you're<00:16:58.680> um 00:16:59.389 --> 00:16:59.399 align:start position:0% container actually runs where you're um 00:16:59.399 --> 00:17:02.949 align:start position:0% container actually runs where you're um making<00:16:59.680> a<00:16:59.880> proposal<00:17:00.680> and<00:17:01.240> uh<00:17:01.680> in<00:17:01.839> the<00:17:02.000> end<00:17:02.800> the 00:17:02.949 --> 00:17:02.959 align:start position:0% making a proposal and uh in the end the 00:17:02.959 --> 00:17:10.029 align:start position:0% making a proposal and uh in the end the execution<00:17:03.480> when<00:17:03.600> it's<00:17:03.800> done<00:17:04.480> is<00:17:04.640> wound 00:17:10.029 --> 00:17:10.039 align:start position:0% 00:17:10.039 --> 00:17:12.390 align:start position:0% down 00:17:12.390 --> 00:17:12.400 align:start position:0% down 00:17:12.400 --> 00:17:14.470 align:start position:0% down so<00:17:13.400> there<00:17:13.520> are<00:17:13.640> a<00:17:13.760> couple<00:17:13.919> of<00:17:14.039> risk<00:17:14.280> and 00:17:14.470 --> 00:17:14.480 align:start position:0% so there are a couple of risk and 00:17:14.480 --> 00:17:17.829 align:start position:0% so there are a couple of risk and opportunities<00:17:15.799> um<00:17:16.799> that<00:17:17.000> that<00:17:17.079> are<00:17:17.280> obvious<00:17:17.760> I 00:17:17.829 --> 00:17:17.839 align:start position:0% opportunities um that that are obvious I 00:17:17.839 --> 00:17:20.590 align:start position:0% opportunities um that that are obvious I mean<00:17:18.799> uh<00:17:18.959> that<00:17:19.079> we<00:17:19.199> haven't<00:17:19.480> looked<00:17:19.799> into<00:17:20.360> one 00:17:20.590 --> 00:17:20.600 align:start position:0% mean uh that we haven't looked into one 00:17:20.600 --> 00:17:22.590 align:start position:0% mean uh that we haven't looked into one is<00:17:20.720> the<00:17:20.919> question<00:17:21.480> about<00:17:21.679> a<00:17:21.839> spot<00:17:22.120> Market<00:17:22.480> how 00:17:22.590 --> 00:17:22.600 align:start position:0% is the question about a spot Market how 00:17:22.600 --> 00:17:26.429 align:start position:0% is the question about a spot Market how can<00:17:22.760> that<00:17:23.120> look<00:17:24.120> um<00:17:24.959> what<00:17:25.120> is<00:17:25.319> not<00:17:25.720> clear<00:17:26.039> to<00:17:26.280> us 00:17:26.429 --> 00:17:26.439 align:start position:0% can that look um what is not clear to us 00:17:26.439 --> 00:17:28.189 align:start position:0% can that look um what is not clear to us in<00:17:26.559> the<00:17:26.679> moment<00:17:26.959> is<00:17:27.199> how<00:17:27.400> do<00:17:27.520> you<00:17:27.799> actually 00:17:28.189 --> 00:17:28.199 align:start position:0% in the moment is how do you actually 00:17:28.199 --> 00:17:30.430 align:start position:0% in the moment is how do you actually control<00:17:29.000> access<00:17:29.320> to<00:17:29.480> the<00:17:29.640> whole<00:17:29.840> Market<00:17:30.320> how 00:17:30.430 --> 00:17:30.440 align:start position:0% control access to the whole Market how 00:17:30.440 --> 00:17:33.590 align:start position:0% control access to the whole Market how to<00:17:30.720> control<00:17:31.120> access<00:17:31.360> to<00:17:31.520> the<00:17:31.799> sensors<00:17:32.799> it's 00:17:33.590 --> 00:17:33.600 align:start position:0% to control access to the sensors it's 00:17:33.600 --> 00:17:34.750 align:start position:0% to control access to the sensors it's basically<00:17:33.919> out<00:17:34.039> of<00:17:34.160> the<00:17:34.280> scope<00:17:34.520> of<00:17:34.640> the 00:17:34.750 --> 00:17:34.760 align:start position:0% basically out of the scope of the 00:17:34.760 --> 00:17:37.029 align:start position:0% basically out of the scope of the experimentation<00:17:35.360> that<00:17:35.480> we<00:17:35.640> did<00:17:36.480> but<00:17:36.600> it's<00:17:36.720> not 00:17:37.029 --> 00:17:37.039 align:start position:0% experimentation that we did but it's not 00:17:37.039 --> 00:17:39.870 align:start position:0% experimentation that we did but it's not something<00:17:37.720> um<00:17:38.200> that<00:17:38.360> we<00:17:38.799> consider 00:17:39.870 --> 00:17:39.880 align:start position:0% something um that we consider 00:17:39.880 --> 00:17:43.710 align:start position:0% something um that we consider unsolvable<00:17:40.880> um<00:17:41.200> there's<00:17:42.120> also<00:17:43.120> the<00:17:43.320> question 00:17:43.710 --> 00:17:43.720 align:start position:0% unsolvable um there's also the question 00:17:43.720 --> 00:17:45.190 align:start position:0% unsolvable um there's also the question how<00:17:43.880> would<00:17:44.120> actual<00:17:44.440> vendors<00:17:44.880> how<00:17:45.000> would 00:17:45.190 --> 00:17:45.200 align:start position:0% how would actual vendors how would 00:17:45.200 --> 00:17:46.510 align:start position:0% how would actual vendors how would actually<00:17:45.520> participants<00:17:46.080> in<00:17:46.240> such<00:17:46.360> a 00:17:46.510 --> 00:17:46.520 align:start position:0% actually participants in such a 00:17:46.520 --> 00:17:49.270 align:start position:0% actually participants in such a Marketplace<00:17:47.039> like<00:17:47.320> to<00:17:48.320> uh<00:17:48.600> access<00:17:49.039> and 00:17:49.270 --> 00:17:49.280 align:start position:0% Marketplace like to uh access and 00:17:49.280 --> 00:17:51.070 align:start position:0% Marketplace like to uh access and process<00:17:49.760> and<00:17:49.919> analyze<00:17:50.320> and<00:17:50.440> filter<00:17:50.760> this<00:17:50.919> kind 00:17:51.070 --> 00:17:51.080 align:start position:0% process and analyze and filter this kind 00:17:51.080 --> 00:17:55.430 align:start position:0% process and analyze and filter this kind of<00:17:51.360> data<00:17:52.360> and<00:17:52.960> um<00:17:53.559> what<00:17:54.520> kind<00:17:54.679> of<00:17:54.880> arbitrary 00:17:55.430 --> 00:17:55.440 align:start position:0% of data and um what kind of arbitrary 00:17:55.440 --> 00:17:57.590 align:start position:0% of data and um what kind of arbitrary code<00:17:55.919> can<00:17:56.080> you<00:17:56.240> allow<00:17:56.600> in<00:17:56.840> this<00:17:57.120> this<00:17:57.280> kind<00:17:57.440> of 00:17:57.590 --> 00:17:57.600 align:start position:0% code can you allow in this this kind of 00:17:57.600 --> 00:17:59.710 align:start position:0% code can you allow in this this kind of environment 00:17:59.710 --> 00:17:59.720 align:start position:0% environment 00:17:59.720 --> 00:18:02.630 align:start position:0% environment um<00:18:00.720> the<00:18:00.840> next<00:18:01.039> steps<00:18:01.320> for<00:18:01.520> us<00:18:01.799> and<00:18:02.159> it's<00:18:02.480> it's 00:18:02.630 --> 00:18:02.640 align:start position:0% um the next steps for us and it's it's 00:18:02.640 --> 00:18:04.830 align:start position:0% um the next steps for us and it's it's still<00:18:02.880> ongoing<00:18:03.640> um<00:18:03.960> what<00:18:04.080> is<00:18:04.520> what<00:18:04.640> is 00:18:04.830 --> 00:18:04.840 align:start position:0% still ongoing um what is what is 00:18:04.840 --> 00:18:06.549 align:start position:0% still ongoing um what is what is happening<00:18:05.240> there<00:18:05.440> and<00:18:05.720> again<00:18:06.039> this<00:18:06.120> is<00:18:06.280> an 00:18:06.549 --> 00:18:06.559 align:start position:0% happening there and again this is an 00:18:06.559 --> 00:18:09.149 align:start position:0% happening there and again this is an internal<00:18:07.120> experimentation<00:18:07.679> so<00:18:07.880> to<00:18:08.080> say<00:18:08.799> where 00:18:09.149 --> 00:18:09.159 align:start position:0% internal experimentation so to say where 00:18:09.159 --> 00:18:11.830 align:start position:0% internal experimentation so to say where that<00:18:09.320> we<00:18:09.440> use<00:18:09.840> also<00:18:10.679> um<00:18:10.840> to<00:18:11.039> convince<00:18:11.520> people 00:18:11.830 --> 00:18:11.840 align:start position:0% that we use also um to convince people 00:18:11.840 --> 00:18:15.190 align:start position:0% that we use also um to convince people that<00:18:12.000> this<00:18:12.120> is<00:18:12.480> uh<00:18:12.600> the<00:18:12.679> way<00:18:12.840> to<00:18:13.360> forward 00:18:15.190 --> 00:18:15.200 align:start position:0% that this is uh the way to forward 00:18:15.200 --> 00:18:17.590 align:start position:0% that this is uh the way to forward and<00:18:16.200> we<00:18:16.320> are 00:18:17.590 --> 00:18:17.600 align:start position:0% and we are 00:18:17.600 --> 00:18:20.710 align:start position:0% and we are looking<00:18:18.600> uh<00:18:18.919> where<00:18:19.080> we're<00:18:19.360> just<00:18:20.039> hoping<00:18:20.520> that 00:18:20.710 --> 00:18:20.720 align:start position:0% looking uh where we're just hoping that 00:18:20.720 --> 00:18:22.710 align:start position:0% looking uh where we're just hoping that A<00:18:20.840> Thin<00:18:21.159> Client<00:18:21.520> is<00:18:22.039> going<00:18:22.240> to<00:18:22.360> be<00:18:22.480> in<00:18:22.559> the 00:18:22.710 --> 00:18:22.720 align:start position:0% A Thin Client is going to be in the 00:18:22.720 --> 00:18:26.870 align:start position:0% A Thin Client is going to be in the cards<00:18:23.120> very<00:18:23.320> soon<00:18:24.280> to<00:18:24.760> have<00:18:24.880> a<00:18:25.080> good<00:18:25.720> um<00:18:26.480> road 00:18:26.870 --> 00:18:26.880 align:start position:0% cards very soon to have a good um road 00:18:26.880 --> 00:18:29.430 align:start position:0% cards very soon to have a good um road towards<00:18:27.280> scalability<00:18:27.919> for<00:18:28.120> this<00:18:28.320> model 00:18:29.430 --> 00:18:29.440 align:start position:0% towards scalability for this model 00:18:29.440 --> 00:18:31.510 align:start position:0% towards scalability for this model where<00:18:30.120> as<00:18:30.280> far<00:18:30.400> as<00:18:30.559> I<00:18:30.679> can<00:18:30.840> see<00:18:31.120> we<00:18:31.200> are<00:18:31.320> going 00:18:31.510 --> 00:18:31.520 align:start position:0% where as far as I can see we are going 00:18:31.520 --> 00:18:33.390 align:start position:0% where as far as I can see we are going to<00:18:31.679> have<00:18:31.840> not<00:18:32.120> too<00:18:32.280> many<00:18:32.480> validators<00:18:33.200> but<00:18:33.320> a 00:18:33.390 --> 00:18:33.400 align:start position:0% to have not too many validators but a 00:18:33.400 --> 00:18:35.549 align:start position:0% to have not too many validators but a lot<00:18:33.520> of<00:18:33.640> thin<00:18:33.919> cines<00:18:34.679> and<00:18:34.799> that<00:18:34.960> would<00:18:35.120> be<00:18:35.400> a 00:18:35.549 --> 00:18:35.559 align:start position:0% lot of thin cines and that would be a 00:18:35.559 --> 00:18:37.549 align:start position:0% lot of thin cines and that would be a good<00:18:35.799> answer<00:18:36.120> to<00:18:36.320> how<00:18:36.480> this<00:18:36.760> can 00:18:37.549 --> 00:18:37.559 align:start position:0% good answer to how this can 00:18:37.559 --> 00:18:40.470 align:start position:0% good answer to how this can scale<00:18:38.559> um<00:18:39.240> there<00:18:39.360> should<00:18:39.559> be<00:18:39.799> some<00:18:40.039> kind<00:18:40.200> of<00:18:40.280> an 00:18:40.470 --> 00:18:40.480 align:start position:0% scale um there should be some kind of an 00:18:40.480 --> 00:18:42.510 align:start position:0% scale um there should be some kind of an exchange<00:18:40.799> and<00:18:41.000> directory<00:18:41.600> that<00:18:41.720> we<00:18:41.840> will<00:18:42.400> uh 00:18:42.510 --> 00:18:42.520 align:start position:0% exchange and directory that we will uh 00:18:42.520 --> 00:18:45.270 align:start position:0% exchange and directory that we will uh look<00:18:42.760> at<00:18:43.039> how<00:18:43.200> this<00:18:43.360> could<00:18:43.520> look<00:18:44.280> where<00:18:44.679> um<00:18:45.159> the 00:18:45.270 --> 00:18:45.280 align:start position:0% look at how this could look where um the 00:18:45.280 --> 00:18:47.110 align:start position:0% look at how this could look where um the entire<00:18:45.559> Marketplace<00:18:46.120> can<00:18:46.360> can<00:18:46.480> be<00:18:46.640> driven 00:18:47.110 --> 00:18:47.120 align:start position:0% entire Marketplace can can be driven 00:18:47.120 --> 00:18:50.230 align:start position:0% entire Marketplace can can be driven through<00:18:48.280> um<00:18:49.280> and<00:18:49.400> then<00:18:49.559> we're<00:18:49.760> going<00:18:49.919> to<00:18:50.120> have 00:18:50.230 --> 00:18:50.240 align:start position:0% through um and then we're going to have 00:18:50.240 --> 00:18:53.510 align:start position:0% through um and then we're going to have a<00:18:50.440> push<00:18:50.919> uh<00:18:51.039> internally<00:18:51.760> to<00:18:51.960> try<00:18:52.240> to<00:18:53.039> uh<00:18:53.200> find 00:18:53.510 --> 00:18:53.520 align:start position:0% a push uh internally to try to uh find 00:18:53.520 --> 00:18:56.950 align:start position:0% a push uh internally to try to uh find 20,000<00:18:54.640> people<00:18:55.640> um<00:18:56.000> that<00:18:56.159> are<00:18:56.320> interested<00:18:56.760> to 00:18:56.950 --> 00:18:56.960 align:start position:0% 20,000 people um that are interested to 00:18:56.960 --> 00:18:58.909 align:start position:0% 20,000 people um that are interested to sign<00:18:57.159> up<00:18:57.320> for<00:18:57.480> this<00:18:57.640> have<00:18:57.840> raspberry<00:18:58.320> ties 00:18:58.909 --> 00:18:58.919 align:start position:0% sign up for this have raspberry ties 00:18:58.919 --> 00:19:01.070 align:start position:0% sign up for this have raspberry ties connecting<00:18:59.280> into<00:18:59.559> the<00:18:59.760> system<00:19:00.559> and<00:19:00.720> making<00:19:00.960> a 00:19:01.070 --> 00:19:01.080 align:start position:0% connecting into the system and making a 00:19:01.080 --> 00:19:03.669 align:start position:0% connecting into the system and making a large<00:19:01.400> scale<00:19:02.039> real<00:19:02.480> test<00:19:03.000> testing<00:19:03.360> the<00:19:03.480> whole 00:19:03.669 --> 00:19:03.679 align:start position:0% large scale real test testing the whole 00:19:03.679 --> 00:19:07.350 align:start position:0% large scale real test testing the whole ethereum<00:19:04.679> installation<00:19:05.679> um<00:19:06.559> uh<00:19:06.880> how<00:19:07.039> fast<00:19:07.240> it 00:19:07.350 --> 00:19:07.360 align:start position:0% ethereum installation um uh how fast it 00:19:07.360 --> 00:19:10.270 align:start position:0% ethereum installation um uh how fast it can<00:19:07.559> really<00:19:07.919> how<00:19:08.159> how<00:19:08.320> big<00:19:08.480> it<00:19:08.600> can<00:19:08.760> really 00:19:10.270 --> 00:19:10.280 align:start position:0% can really how how big it can really 00:19:10.280 --> 00:19:12.669 align:start position:0% can really how how big it can really scale<00:19:11.280> uh<00:19:11.400> a<00:19:11.520> big<00:19:11.720> Thanks<00:19:12.000> goes<00:19:12.200> to<00:19:12.320> the<00:19:12.440> go 00:19:12.669 --> 00:19:12.679 align:start position:0% scale uh a big Thanks goes to the go 00:19:12.679 --> 00:19:14.430 align:start position:0% scale uh a big Thanks goes to the go team<00:19:13.159> at<00:19:13.320> this<00:19:13.480> point<00:19:13.720> and<00:19:13.880> I've<00:19:14.039> been<00:19:14.159> asked 00:19:14.430 --> 00:19:14.440 align:start position:0% team at this point and I've been asked 00:19:14.440 --> 00:19:16.149 align:start position:0% team at this point and I've been asked specifically<00:19:14.919> but<00:19:15.080> even<00:19:15.320> forward<00:19:15.600> to<00:19:15.840> extend 00:19:16.149 --> 00:19:16.159 align:start position:0% specifically but even forward to extend 00:19:16.159 --> 00:19:19.230 align:start position:0% specifically but even forward to extend that<00:19:16.760> um<00:19:16.960> Jeff<00:19:17.240> Felix<00:19:17.720> goph<00:19:18.320> Victor<00:19:19.000> uh<00:19:19.080> you 00:19:19.230 --> 00:19:19.240 align:start position:0% that um Jeff Felix goph Victor uh you 00:19:19.240 --> 00:19:21.110 align:start position:0% that um Jeff Felix goph Victor uh you really<00:19:19.440> helped<00:19:19.679> us<00:19:19.799> a<00:19:19.919> lot<00:19:20.280> I<00:19:20.400> hope<00:19:20.600> we<00:19:20.760> also 00:19:21.110 --> 00:19:21.120 align:start position:0% really helped us a lot I hope we also 00:19:21.120 --> 00:19:22.390 align:start position:0% really helped us a lot I hope we also were<00:19:21.280> able<00:19:21.440> to<00:19:21.559> contribute<00:19:22.000> because<00:19:22.200> we 00:19:22.390 --> 00:19:22.400 align:start position:0% were able to contribute because we 00:19:22.400 --> 00:19:24.909 align:start position:0% were able to contribute because we actually<00:19:23.240> did<00:19:23.520> ran<00:19:23.840> some<00:19:24.000> large<00:19:24.280> scale<00:19:24.559> tests 00:19:24.909 --> 00:19:24.919 align:start position:0% actually did ran some large scale tests 00:19:24.919 --> 00:19:27.270 align:start position:0% actually did ran some large scale tests with<00:19:25.080> hundreds<00:19:25.400> of<00:19:25.559> devices<00:19:26.520> or<00:19:26.640> at<00:19:26.720> least<00:19:27.039> 100 00:19:27.270 --> 00:19:27.280 align:start position:0% with hundreds of devices or at least 100 00:19:27.280 --> 00:19:29.950 align:start position:0% with hundreds of devices or at least 100 devices<00:19:27.960> uh<00:19:28.360> running<00:19:28.840> through<00:19:29.000> containers 00:19:29.950 --> 00:19:29.960 align:start position:0% devices uh running through containers 00:19:29.960 --> 00:19:32.669 align:start position:0% devices uh running through containers running<00:19:30.559> unusual<00:19:31.120> devices<00:19:31.640> like<00:19:31.799> arms<00:19:32.520> um 00:19:32.669 --> 00:19:32.679 align:start position:0% running unusual devices like arms um 00:19:32.679 --> 00:19:34.789 align:start position:0% running unusual devices like arms um raspberry<00:19:33.159> pies<00:19:33.440> who<00:19:33.559> are<00:19:33.720> slower<00:19:34.159> and<00:19:34.600> might 00:19:34.789 --> 00:19:34.799 align:start position:0% raspberry pies who are slower and might 00:19:34.799 --> 00:19:36.310 align:start position:0% raspberry pies who are slower and might have<00:19:34.960> different<00:19:35.240> kinds<00:19:35.440> of<00:19:35.559> race<00:19:35.960> conditions 00:19:36.310 --> 00:19:36.320 align:start position:0% have different kinds of race conditions 00:19:36.320 --> 00:19:39.909 align:start position:0% have different kinds of race conditions as<00:19:36.400> a<00:19:36.960> result<00:19:37.960> and<00:19:38.480> uh<00:19:39.000> we<00:19:39.159> ran<00:19:39.360> into<00:19:39.559> a<00:19:39.679> bug 00:19:39.909 --> 00:19:39.919 align:start position:0% as a result and uh we ran into a bug 00:19:39.919 --> 00:19:41.430 align:start position:0% as a result and uh we ran into a bug here<00:19:40.000> and<00:19:40.200> there<00:19:40.400> and<00:19:40.520> it<00:19:40.600> was<00:19:40.799> just<00:19:41.000> amazing 00:19:41.430 --> 00:19:41.440 align:start position:0% here and there and it was just amazing 00:19:41.440 --> 00:19:43.590 align:start position:0% here and there and it was just amazing how<00:19:41.720> this<00:19:41.880> week<00:19:42.400> uh<00:19:42.520> we've<00:19:42.720> been<00:19:42.919> able<00:19:43.159> to<00:19:43.280> work 00:19:43.590 --> 00:19:43.600 align:start position:0% how this week uh we've been able to work 00:19:43.600 --> 00:19:46.310 align:start position:0% how this week uh we've been able to work together<00:19:44.000> and<00:19:44.240> and<00:19:44.360> fix<00:19:44.720> the<00:19:44.880> stuff<00:19:45.760> the<00:19:45.919> IBM 00:19:46.310 --> 00:19:46.320 align:start position:0% together and and fix the stuff the IBM 00:19:46.320 --> 00:19:48.549 align:start position:0% together and and fix the stuff the IBM guys<00:19:46.520> were<00:19:46.799> very<00:19:47.039> tired<00:19:47.360> and<00:19:47.559> overworked<00:19:48.320> so 00:19:48.549 --> 00:19:48.559 align:start position:0% guys were very tired and overworked so 00:19:48.559 --> 00:19:51.430 align:start position:0% guys were very tired and overworked so they<00:19:48.640> were<00:19:48.799> grumpy<00:19:49.159> and<00:19:49.280> brief<00:19:50.080> sometimes<00:19:51.080> um 00:19:51.430 --> 00:19:51.440 align:start position:0% they were grumpy and brief sometimes um 00:19:51.440 --> 00:19:53.149 align:start position:0% they were grumpy and brief sometimes um but<00:19:51.760> it<00:19:51.880> was<00:19:52.039> great<00:19:52.240> support<00:19:52.559> that<00:19:52.760> came<00:19:52.960> from 00:19:53.149 --> 00:19:53.159 align:start position:0% but it was great support that came from 00:19:53.159 --> 00:19:56.669 align:start position:0% but it was great support that came from here<00:19:53.360> and<00:19:53.679> big<00:19:53.880> thanks<00:19:54.080> for<00:19:54.640> that<00:19:55.640> so<00:19:56.480> thank 00:19:56.669 --> 00:19:56.679 align:start position:0% here and big thanks for that so thank 00:19:56.679 --> 00:20:00.160 align:start position:0% here and big thanks for that so thank you 00:20:00.160 --> 00:20:00.170 align:start position:0% 00:20:00.170 --> 00:20:04.340 align:start position:0% [Applause] 00:20:04.340 --> 00:20:04.350 align:start position:0% [Applause] 00:20:04.350 --> 00:20:08.680 align:start position:0% [Applause] [Music]