WEBVTT Kind: captions Language: en 00:00:16.880 --> 00:00:19.460 align:start position:0% and<00:00:17.880> if<00:00:18.210> Bob<00:00:18.480> is<00:00:18.720> going<00:00:18.960> to<00:00:19.080> talk<00:00:19.289> about 00:00:19.460 --> 00:00:19.470 align:start position:0% and if Bob is going to talk about 00:00:19.470 --> 00:00:21.080 align:start position:0% and if Bob is going to talk about something<00:00:19.830> a<00:00:20.039> little<00:00:20.160> bit<00:00:20.369> different<00:00:20.789> state 00:00:21.080 --> 00:00:21.090 align:start position:0% something a little bit different state 00:00:21.090 --> 00:00:22.999 align:start position:0% something a little bit different state of<00:00:21.119> the<00:00:21.300> union<00:00:21.720> and<00:00:21.930> roadmap<00:00:22.349> for<00:00:22.650> mobile 00:00:22.999 --> 00:00:23.009 align:start position:0% of the union and roadmap for mobile 00:00:23.009 --> 00:00:25.909 align:start position:0% of the union and roadmap for mobile wearables<00:00:23.640> SBC's<00:00:24.509> and<00:00:24.930> IOT<00:00:25.380> running 00:00:25.909 --> 00:00:25.919 align:start position:0% wearables SBC's and IOT running 00:00:25.919 --> 00:00:30.609 align:start position:0% wearables SBC's and IOT running aetherium 00:00:30.609 --> 00:00:30.619 align:start position:0% 00:00:30.619 --> 00:00:39.580 align:start position:0% hello<00:00:34.579> let's<00:00:35.579> see<00:00:35.760> if<00:00:35.850> this<00:00:36.000> works<00:00:36.239> this<00:00:36.480> time 00:00:39.580 --> 00:00:39.590 align:start position:0% 00:00:39.590 --> 00:00:49.120 align:start position:0% hey<00:00:40.590> hey<00:00:40.829> okay<00:00:41.630> fantastic<00:00:42.630> slides<00:00:46.160> so<00:00:47.180> hi<00:00:48.180> i 00:00:49.120 --> 00:00:49.130 align:start position:0% hey hey okay fantastic slides so hi i 00:00:49.130 --> 00:00:52.220 align:start position:0% hey hey okay fantastic slides so hi i i'm<00:00:50.130> bob<00:00:50.340> sim<00:00:50.550> well<00:00:50.700> i've<00:00:50.970> most<00:00:51.840> of<00:00:51.930> my<00:00:52.020> career 00:00:52.220 --> 00:00:52.230 align:start position:0% i'm bob sim well i've most of my career 00:00:52.230 --> 00:00:54.760 align:start position:0% i'm bob sim well i've most of my career has<00:00:52.320> actually<00:00:52.650> been<00:00:52.740> in<00:00:52.890> the<00:00:53.010> games<00:00:53.220> industry 00:00:54.760 --> 00:00:54.770 align:start position:0% has actually been in the games industry 00:00:54.770 --> 00:00:59.990 align:start position:0% has actually been in the games industry at<00:00:55.770> EA<00:00:56.250> sports<00:00:56.670> i<00:00:57.620> have<00:00:58.620> been<00:00:58.770> working<00:00:59.130> on<00:00:59.280> arm 00:00:59.990 --> 00:01:00.000 align:start position:0% at EA sports i have been working on arm 00:01:00.000 --> 00:01:03.770 align:start position:0% at EA sports i have been working on arm linux<00:01:00.420> cross<00:01:00.720> builds<00:01:01.140> of<00:01:02.010> the<00:01:02.640> c++<00:01:03.300> client<00:01:03.630> for 00:01:03.770 --> 00:01:03.780 align:start position:0% linux cross builds of the c++ client for 00:01:03.780 --> 00:01:06.109 align:start position:0% linux cross builds of the c++ client for the<00:01:03.840> last<00:01:03.989> year<00:01:04.199> or<00:01:04.320> so<00:01:04.530> and<00:01:04.799> then<00:01:05.129> since 00:01:06.109 --> 00:01:06.119 align:start position:0% the last year or so and then since 00:01:06.119 --> 00:01:08.389 align:start position:0% the last year or so and then since february<00:01:06.750> i've<00:01:07.229> been<00:01:07.770> working<00:01:08.159> for<00:01:08.189> the 00:01:08.389 --> 00:01:08.399 align:start position:0% february i've been working for the 00:01:08.399 --> 00:01:12.350 align:start position:0% february i've been working for the foundation<00:01:08.520> as<00:01:09.000> well<00:01:09.030> on<00:01:10.220> the<00:01:11.220> c++<00:01:11.729> client<00:01:12.119> and 00:01:12.350 --> 00:01:12.360 align:start position:0% foundation as well on the c++ client and 00:01:12.360 --> 00:01:16.910 align:start position:0% foundation as well on the c++ client and various<00:01:12.810> other<00:01:12.960> things<00:01:14.630> this<00:01:15.630> is<00:01:15.780> my<00:01:15.930> desk<00:01:16.170> in 00:01:16.910 --> 00:01:16.920 align:start position:0% various other things this is my desk in 00:01:16.920 --> 00:01:21.889 align:start position:0% various other things this is my desk in vancouver<00:01:18.859> got<00:01:19.859> a<00:01:19.889> Raspberry<00:01:20.850> Pi<00:01:20.880> here<00:01:21.359> its 00:01:21.889 --> 00:01:21.899 align:start position:0% vancouver got a Raspberry Pi here its 00:01:21.899 --> 00:01:28.489 align:start position:0% vancouver got a Raspberry Pi here its various<00:01:22.560> other<00:01:22.740> PI's<00:01:23.389> a<00:01:24.950> no<00:01:25.950> droid<00:01:26.280> a<00:01:27.499> project 00:01:28.489 --> 00:01:28.499 align:start position:0% various other PI's a no droid a project 00:01:28.499 --> 00:01:30.410 align:start position:0% various other PI's a no droid a project chip<00:01:28.770> and<00:01:29.009> in<00:01:29.579> the<00:01:29.759> background<00:01:30.119> there<00:01:30.299> I've 00:01:30.410 --> 00:01:30.420 align:start position:0% chip and in the background there I've 00:01:30.420 --> 00:01:33.620 align:start position:0% chip and in the background there I've got<00:01:30.539> a<00:01:30.569> Commodore<00:01:30.959> 64<00:01:31.469> and<00:01:31.649> an<00:01:31.889> Atari<00:01:32.310> I'm<00:01:32.789> not 00:01:33.620 --> 00:01:33.630 align:start position:0% got a Commodore 64 and an Atari I'm not 00:01:33.630 --> 00:01:34.940 align:start position:0% got a Commodore 64 and an Atari I'm not trying<00:01:33.929> to<00:01:33.959> get<00:01:34.109> a<00:01:34.139> theory<00:01:34.469> I'm<00:01:34.560> thorough<00:01:34.679> on 00:01:34.940 --> 00:01:34.950 align:start position:0% trying to get a theory I'm thorough on 00:01:34.950 --> 00:01:36.590 align:start position:0% trying to get a theory I'm thorough on it<00:01:35.429> would<00:01:35.609> be<00:01:35.729> great<00:01:35.939> if<00:01:36.060> we<00:01:36.179> could<00:01:36.359> but<00:01:36.569> I 00:01:36.590 --> 00:01:36.600 align:start position:0% it would be great if we could but I 00:01:36.600 --> 00:01:39.169 align:start position:0% it would be great if we could but I think<00:01:36.659> they're<00:01:36.929> a<00:01:36.959> little<00:01:37.200> bit<00:01:37.350> low<00:01:37.619> spec<00:01:38.179> but 00:01:39.169 --> 00:01:39.179 align:start position:0% think they're a little bit low spec but 00:01:39.179 --> 00:01:44.569 align:start position:0% think they're a little bit low spec but I<00:01:39.270> have<00:01:39.420> been<00:01:39.600> looking<00:01:39.929> at<00:01:43.039> mobile<00:01:44.039> devices 00:01:44.569 --> 00:01:44.579 align:start position:0% I have been looking at mobile devices 00:01:44.579 --> 00:01:50.719 align:start position:0% I have been looking at mobile devices and<00:01:44.819> wearables<00:01:47.569> so<00:01:48.920> what<00:01:49.920> are<00:01:50.189> resource 00:01:50.719 --> 00:01:50.729 align:start position:0% and wearables so what are resource 00:01:50.729 --> 00:01:53.749 align:start position:0% and wearables so what are resource constrained<00:01:51.569> devices<00:01:52.429> there's<00:01:53.429> lots<00:01:53.639> of 00:01:53.749 --> 00:01:53.759 align:start position:0% constrained devices there's lots of 00:01:53.759 --> 00:01:55.789 align:start position:0% constrained devices there's lots of different<00:01:54.119> kind<00:01:54.329> of<00:01:54.560> constraints<00:01:55.560> that<00:01:55.619> you 00:01:55.789 --> 00:01:55.799 align:start position:0% different kind of constraints that you 00:01:55.799 --> 00:01:58.819 align:start position:0% different kind of constraints that you might<00:01:55.979> have<00:01:56.389> I<00:01:57.389> mean<00:01:57.840> ultimately<00:01:58.079> all 00:01:58.819 --> 00:01:58.829 align:start position:0% might have I mean ultimately all 00:01:58.829 --> 00:02:01.580 align:start position:0% might have I mean ultimately all computing<00:01:59.490> devices<00:01:59.759> are<00:02:00.090> constrained<00:02:00.779> but 00:02:01.580 --> 00:02:01.590 align:start position:0% computing devices are constrained but 00:02:01.590 --> 00:02:03.379 align:start position:0% computing devices are constrained but really<00:02:01.950> it's<00:02:02.069> talking<00:02:02.310> about<00:02:02.459> things<00:02:03.179> which 00:02:03.379 --> 00:02:03.389 align:start position:0% really it's talking about things which 00:02:03.389 --> 00:02:06.319 align:start position:0% really it's talking about things which are<00:02:03.630> less<00:02:04.439> capable<00:02:04.709> than<00:02:05.340> desktop<00:02:05.969> machines 00:02:06.319 --> 00:02:06.329 align:start position:0% are less capable than desktop machines 00:02:06.329 --> 00:02:07.819 align:start position:0% are less capable than desktop machines and<00:02:06.630> there's<00:02:07.079> lots<00:02:07.289> of<00:02:07.409> different<00:02:07.709> dimensions 00:02:07.819 --> 00:02:07.829 align:start position:0% and there's lots of different dimensions 00:02:07.829 --> 00:02:11.180 align:start position:0% and there's lots of different dimensions that<00:02:08.340> might<00:02:09.030> be<00:02:09.149> happening<00:02:09.539> in<00:02:10.009> you<00:02:11.009> know<00:02:11.130> you 00:02:11.180 --> 00:02:11.190 align:start position:0% that might be happening in you know you 00:02:11.190 --> 00:02:14.660 align:start position:0% that might be happening in you know you might<00:02:11.459> be<00:02:11.660> limited<00:02:12.660> CPU<00:02:13.280> you<00:02:14.280> know<00:02:14.400> most 00:02:14.660 --> 00:02:14.670 align:start position:0% might be limited CPU you know most 00:02:14.670 --> 00:02:18.440 align:start position:0% might be limited CPU you know most desktops<00:02:15.150> now<00:02:15.360> 64-bit<00:02:16.610> but<00:02:17.610> 32<00:02:17.940> is<00:02:18.090> going<00:02:18.390> to 00:02:18.440 --> 00:02:18.450 align:start position:0% desktops now 64-bit but 32 is going to 00:02:18.450 --> 00:02:21.980 align:start position:0% desktops now 64-bit but 32 is going to be<00:02:18.540> around<00:02:18.810> for<00:02:19.170> a<00:02:19.200> long<00:02:19.500> long<00:02:19.680> time<00:02:20.840> lots<00:02:21.840> of 00:02:21.980 --> 00:02:21.990 align:start position:0% be around for a long long time lots of 00:02:21.990 --> 00:02:25.250 align:start position:0% be around for a long long time lots of them<00:02:22.140> in<00:02:22.410> these<00:02:23.099> kind<00:02:23.430> of<00:02:23.519> devices<00:02:24.360> are<00:02:24.870> just 00:02:25.250 --> 00:02:25.260 align:start position:0% them in these kind of devices are just 00:02:25.260 --> 00:02:27.770 align:start position:0% them in these kind of devices are just single<00:02:25.470> core<00:02:25.799> they<00:02:26.010> may<00:02:26.189> be<00:02:26.250> pretty<00:02:26.760> low 00:02:27.770 --> 00:02:27.780 align:start position:0% single core they may be pretty low 00:02:27.780 --> 00:02:30.440 align:start position:0% single core they may be pretty low frequency<00:02:28.650> as<00:02:28.770> well<00:02:28.950> limited<00:02:29.700> memory<00:02:29.910> limits 00:02:30.440 --> 00:02:30.450 align:start position:0% frequency as well limited memory limits 00:02:30.450 --> 00:02:33.380 align:start position:0% frequency as well limited memory limits its<00:02:30.569> storage<00:02:30.990> limited<00:02:31.380> bandwidth<00:02:32.390> limited 00:02:33.380 --> 00:02:33.390 align:start position:0% its storage limited bandwidth limited 00:02:33.390 --> 00:02:37.790 align:start position:0% its storage limited bandwidth limited power<00:02:33.660> as<00:02:34.050> well<00:02:34.910> and<00:02:35.910> also<00:02:36.450> the<00:02:36.900> OS<00:02:37.170> itself<00:02:37.590> may 00:02:37.790 --> 00:02:37.800 align:start position:0% power as well and also the OS itself may 00:02:37.800 --> 00:02:40.760 align:start position:0% power as well and also the OS itself may be<00:02:37.830> limited<00:02:38.280> lots<00:02:38.760> of<00:02:38.990> such<00:02:39.990> devices<00:02:40.319> are 00:02:40.760 --> 00:02:40.770 align:start position:0% be limited lots of such devices are 00:02:40.770 --> 00:02:44.229 align:start position:0% be limited lots of such devices are basically<00:02:41.370> you<00:02:41.700> know<00:02:41.819> single<00:02:42.120> app<00:02:42.330> at<00:02:42.480> a<00:02:42.540> time 00:02:44.229 --> 00:02:44.239 align:start position:0% basically you know single app at a time 00:02:44.239 --> 00:02:47.050 align:start position:0% basically you know single app at a time so<00:02:45.239> some<00:02:45.540> kind<00:02:45.690> of<00:02:45.840> examples<00:02:46.800> of<00:02:46.920> these 00:02:47.050 --> 00:02:47.060 align:start position:0% so some kind of examples of these 00:02:47.060 --> 00:02:52.040 align:start position:0% so some kind of examples of these wearables<00:02:48.650> you<00:02:49.650> know<00:02:49.770> be<00:02:50.160> those<00:02:50.810> smart<00:02:51.810> rings 00:02:52.040 --> 00:02:52.050 align:start position:0% wearables you know be those smart rings 00:02:52.050 --> 00:02:56.110 align:start position:0% wearables you know be those smart rings or<00:02:52.290> watches<00:02:52.709> or<00:02:53.300> health<00:02:54.300> tracking<00:02:54.660> devices 00:02:56.110 --> 00:02:56.120 align:start position:0% or watches or health tracking devices 00:02:56.120 --> 00:02:59.570 align:start position:0% or watches or health tracking devices mobile<00:02:57.120> devices<00:02:57.780> though<00:02:58.230> they<00:02:58.440> are<00:02:58.620> very 00:02:59.570 --> 00:02:59.580 align:start position:0% mobile devices though they are very 00:02:59.580 --> 00:03:01.729 align:start position:0% mobile devices though they are very prevalent<00:02:59.940> now<00:03:00.330> they<00:03:00.540> are<00:03:00.690> very<00:03:00.959> constrained 00:03:01.729 --> 00:03:01.739 align:start position:0% prevalent now they are very constrained 00:03:01.739 --> 00:03:03.920 align:start position:0% prevalent now they are very constrained compared<00:03:02.340> to<00:03:02.430> desktops<00:03:02.880> even<00:03:03.269> tablets<00:03:03.660> same 00:03:03.920 --> 00:03:03.930 align:start position:0% compared to desktops even tablets same 00:03:03.930 --> 00:03:06.860 align:start position:0% compared to desktops even tablets same thing<00:03:04.140> games<00:03:05.100> consoles<00:03:05.610> people<00:03:06.450> often<00:03:06.750> don't 00:03:06.860 --> 00:03:06.870 align:start position:0% thing games consoles people often don't 00:03:06.870 --> 00:03:08.600 align:start position:0% thing games consoles people often don't think<00:03:07.140> of<00:03:07.230> those<00:03:07.350> as<00:03:07.560> being<00:03:07.590> constrained<00:03:08.340> but 00:03:08.600 --> 00:03:08.610 align:start position:0% think of those as being constrained but 00:03:08.610 --> 00:03:12.380 align:start position:0% think of those as being constrained but they<00:03:08.760> they<00:03:09.180> are<00:03:09.920> and<00:03:10.920> more<00:03:11.700> generally<00:03:12.090> just<00:03:12.209> in 00:03:12.380 --> 00:03:12.390 align:start position:0% they they are and more generally just in 00:03:12.390 --> 00:03:15.250 align:start position:0% they they are and more generally just in embedded<00:03:12.690> devices<00:03:13.280> lots<00:03:14.280> of<00:03:14.400> single<00:03:14.670> board 00:03:15.250 --> 00:03:15.260 align:start position:0% embedded devices lots of single board 00:03:15.260 --> 00:03:19.820 align:start position:0% embedded devices lots of single board computers<00:03:16.260> like<00:03:16.920> Raspberry<00:03:17.430> Pi<00:03:18.050> and<00:03:19.050> really 00:03:19.820 --> 00:03:19.830 align:start position:0% computers like Raspberry Pi and really 00:03:19.830 --> 00:03:22.220 align:start position:0% computers like Raspberry Pi and really IOT<00:03:20.640> devices<00:03:20.970> of<00:03:21.239> all<00:03:21.300> stripes<00:03:21.630> is<00:03:21.959> really 00:03:22.220 --> 00:03:22.230 align:start position:0% IOT devices of all stripes is really 00:03:22.230 --> 00:03:29.300 align:start position:0% IOT devices of all stripes is really where<00:03:22.410> this<00:03:22.860> stuff<00:03:23.130> gets<00:03:23.730> interesting<00:03:28.100> so<00:03:29.100> I 00:03:29.300 --> 00:03:29.310 align:start position:0% where this stuff gets interesting so I 00:03:29.310 --> 00:03:31.670 align:start position:0% where this stuff gets interesting so I mean<00:03:29.519> why<00:03:29.730> why<00:03:30.480> would<00:03:30.810> you<00:03:30.930> care<00:03:31.110> about<00:03:31.410> having 00:03:31.670 --> 00:03:31.680 align:start position:0% mean why why would you care about having 00:03:31.680 --> 00:03:36.650 align:start position:0% mean why why would you care about having aetherium<00:03:32.570> you<00:03:33.570> know<00:03:33.720> on<00:03:33.959> your<00:03:34.019> SmartWatch<00:03:35.660> or 00:03:36.650 --> 00:03:36.660 align:start position:0% aetherium you know on your SmartWatch or 00:03:36.660 --> 00:03:39.350 align:start position:0% aetherium you know on your SmartWatch or any<00:03:37.320> such<00:03:37.739> device<00:03:38.070> well<00:03:38.610> really<00:03:38.850> when<00:03:39.239> you 00:03:39.350 --> 00:03:39.360 align:start position:0% any such device well really when you 00:03:39.360 --> 00:03:41.180 align:start position:0% any such device well really when you look<00:03:39.390> at<00:03:39.600> mobile<00:03:39.930> computing<00:03:40.380> I<00:03:40.500> mean<00:03:40.680> mobile 00:03:41.180 --> 00:03:41.190 align:start position:0% look at mobile computing I mean mobile 00:03:41.190 --> 00:03:44.319 align:start position:0% look at mobile computing I mean mobile computing<00:03:41.640> now<00:03:41.850> is<00:03:42.120> mainstream<00:03:42.600> computing 00:03:44.319 --> 00:03:44.329 align:start position:0% computing now is mainstream computing 00:03:44.329 --> 00:03:47.240 align:start position:0% computing now is mainstream computing for<00:03:45.329> lots<00:03:45.510> of<00:03:45.600> people<00:03:45.870> in<00:03:45.959> the<00:03:46.049> world<00:03:46.250> their 00:03:47.240 --> 00:03:47.250 align:start position:0% for lots of people in the world their 00:03:47.250 --> 00:03:50.240 align:start position:0% for lots of people in the world their smart<00:03:48.200> phone<00:03:49.200> that<00:03:49.410> they<00:03:49.530> get<00:03:49.709> is<00:03:49.890> likely 00:03:50.240 --> 00:03:50.250 align:start position:0% smart phone that they get is likely 00:03:50.250 --> 00:03:54.110 align:start position:0% smart phone that they get is likely their<00:03:50.549> first<00:03:50.730> computer<00:03:51.799> and<00:03:52.820> really<00:03:53.820> if<00:03:54.000> you 00:03:54.110 --> 00:03:54.120 align:start position:0% their first computer and really if you 00:03:54.120 --> 00:03:55.880 align:start position:0% their first computer and really if you look<00:03:54.239> at<00:03:54.360> the<00:03:54.450> specs<00:03:54.720> on<00:03:54.900> mobile<00:03:55.230> devices<00:03:55.500> they 00:03:55.880 --> 00:03:55.890 align:start position:0% look at the specs on mobile devices they 00:03:55.890 --> 00:04:00.170 align:start position:0% look at the specs on mobile devices they are<00:03:56.070> of<00:03:56.480> comparable<00:03:58.549> specifications<00:03:59.549> to<00:03:59.790> what 00:04:00.170 --> 00:04:00.180 align:start position:0% are of comparable specifications to what 00:04:00.180 --> 00:04:03.289 align:start position:0% are of comparable specifications to what desktops<00:04:00.660> were<00:04:00.870> not<00:04:01.140> so<00:04:01.290> very<00:04:01.410> long<00:04:01.500> ago 00:04:03.289 --> 00:04:03.299 align:start position:0% desktops were not so very long ago 00:04:03.299 --> 00:04:06.620 align:start position:0% desktops were not so very long ago you've<00:04:04.019> got<00:04:04.230> mobile<00:04:05.120> and<00:04:06.120> then<00:04:06.239> after<00:04:06.510> that 00:04:06.620 --> 00:04:06.630 align:start position:0% you've got mobile and then after that 00:04:06.630 --> 00:04:08.750 align:start position:0% you've got mobile and then after that wearable<00:04:07.260> taking<00:04:07.829> it<00:04:07.920> down<00:04:08.100> a<00:04:08.130> bit 00:04:08.750 --> 00:04:08.760 align:start position:0% wearable taking it down a bit 00:04:08.760 --> 00:04:10.970 align:start position:0% wearable taking it down a bit edge<00:04:09.390> computing<00:04:10.230> is<00:04:10.350> a<00:04:10.380> term<00:04:10.650> that<00:04:10.680> you'll 00:04:10.970 --> 00:04:10.980 align:start position:0% edge computing is a term that you'll 00:04:10.980 --> 00:04:13.060 align:start position:0% edge computing is a term that you'll hear<00:04:11.220> more<00:04:11.489> and<00:04:11.640> more<00:04:11.820> in<00:04:11.940> the<00:04:12.030> coming<00:04:12.060> years 00:04:13.060 --> 00:04:13.070 align:start position:0% hear more and more in the coming years 00:04:13.070 --> 00:04:17.539 align:start position:0% hear more and more in the coming years really<00:04:14.070> long<00:04:15.650> along<00:04:16.650> the<00:04:16.799> theme<00:04:16.979> that<00:04:17.220> if<00:04:17.370> you 00:04:17.539 --> 00:04:17.549 align:start position:0% really long along the theme that if you 00:04:17.549 --> 00:04:19.509 align:start position:0% really long along the theme that if you have<00:04:17.789> billions<00:04:18.269> and<00:04:18.450> billions<00:04:18.600> of<00:04:18.840> devices 00:04:19.509 --> 00:04:19.519 align:start position:0% have billions and billions of devices 00:04:19.519 --> 00:04:21.620 align:start position:0% have billions and billions of devices they're<00:04:20.519> not<00:04:20.669> going<00:04:20.820> to<00:04:20.850> run<00:04:21.000> client-server 00:04:21.620 --> 00:04:21.630 align:start position:0% they're not going to run client-server 00:04:21.630 --> 00:04:23.090 align:start position:0% they're not going to run client-server there's<00:04:21.900> no<00:04:22.049> way<00:04:22.260> that<00:04:22.440> you<00:04:22.530> can<00:04:22.680> have<00:04:22.800> some 00:04:23.090 --> 00:04:23.100 align:start position:0% there's no way that you can have some 00:04:23.100 --> 00:04:25.100 align:start position:0% there's no way that you can have some you<00:04:23.910> know<00:04:23.940> mega<00:04:24.300> farm<00:04:24.630> that<00:04:24.870> they're<00:04:24.990> all 00:04:25.100 --> 00:04:25.110 align:start position:0% you know mega farm that they're all 00:04:25.110 --> 00:04:26.420 align:start position:0% you know mega farm that they're all talking<00:04:25.380> to<00:04:25.710> and<00:04:25.890> waiting<00:04:26.280> their 00:04:26.420 --> 00:04:26.430 align:start position:0% talking to and waiting their 00:04:26.430 --> 00:04:28.969 align:start position:0% talking to and waiting their instructions<00:04:27.200> devices<00:04:28.200> need<00:04:28.440> to<00:04:28.500> become 00:04:28.969 --> 00:04:28.979 align:start position:0% instructions devices need to become 00:04:28.979 --> 00:04:33.909 align:start position:0% instructions devices need to become autonomous<00:04:29.460> to<00:04:29.880> scale<00:04:31.820> and<00:04:32.820> also<00:04:33.330> really 00:04:33.909 --> 00:04:33.919 align:start position:0% autonomous to scale and also really 00:04:33.919 --> 00:04:39.589 align:start position:0% autonomous to scale and also really along<00:04:35.360> Andreas's<00:04:36.470> analogy<00:04:38.599> boundaries 00:04:39.589 --> 00:04:39.599 align:start position:0% along Andreas's analogy boundaries 00:04:39.599 --> 00:04:41.330 align:start position:0% along Andreas's analogy boundaries security<00:04:40.229> is<00:04:40.560> a<00:04:40.950> dying 00:04:41.330 --> 00:04:41.340 align:start position:0% security is a dying 00:04:41.340 --> 00:04:44.270 align:start position:0% security is a dying paradigm<00:04:41.820> really<00:04:42.750> you<00:04:43.260> need<00:04:43.440> individual 00:04:44.270 --> 00:04:44.280 align:start position:0% paradigm really you need individual 00:04:44.280 --> 00:04:46.610 align:start position:0% paradigm really you need individual notes<00:04:44.550> to<00:04:44.850> be<00:04:44.930> working<00:04:45.930> on<00:04:46.050> the<00:04:46.139> assumption 00:04:46.610 --> 00:04:46.620 align:start position:0% notes to be working on the assumption 00:04:46.620 --> 00:04:49.670 align:start position:0% notes to be working on the assumption that<00:04:46.650> they<00:04:46.889> are<00:04:46.919> in<00:04:47.790> a<00:04:48.300> hostile<00:04:48.690> place<00:04:49.350> and 00:04:49.670 --> 00:04:49.680 align:start position:0% that they are in a hostile place and 00:04:49.680 --> 00:04:51.830 align:start position:0% that they are in a hostile place and they<00:04:49.770> need<00:04:49.949> to<00:04:50.130> be<00:04:50.600> responsible<00:04:51.600> for<00:04:51.630> their 00:04:51.830 --> 00:04:51.840 align:start position:0% they need to be responsible for their 00:04:51.840 --> 00:04:59.689 align:start position:0% they need to be responsible for their own<00:04:51.930> security<00:04:55.580> this<00:04:56.580> is<00:04:56.880> not<00:04:57.180> new<00:04:57.960> on<00:04:58.460> my<00:04:59.460> right 00:04:59.689 --> 00:04:59.699 align:start position:0% own security this is not new on my right 00:04:59.699 --> 00:05:02.030 align:start position:0% own security this is not new on my right hand<00:04:59.970> here<00:05:00.240> I<00:05:00.270> have<00:05:00.570> a<00:05:00.600> Java<00:05:00.930> ring<00:05:01.229> don't<00:05:01.979> know 00:05:02.030 --> 00:05:02.040 align:start position:0% hand here I have a Java ring don't know 00:05:02.040 --> 00:05:06.219 align:start position:0% hand here I have a Java ring don't know if<00:05:02.160> anyone<00:05:02.430> is<00:05:02.460> aware<00:05:02.729> of<00:05:02.880> the<00:05:03.000> Java<00:05:03.270> ring<00:05:04.760> 1998 00:05:06.219 --> 00:05:06.229 align:start position:0% if anyone is aware of the Java ring 1998 00:05:06.229 --> 00:05:11.030 align:start position:0% if anyone is aware of the Java ring 1998 at<00:05:07.229> the<00:05:08.210> Java<00:05:09.210> developer<00:05:09.720> conference<00:05:10.169> in<00:05:10.320> 1998 00:05:11.030 --> 00:05:11.040 align:start position:0% at the Java developer conference in 1998 00:05:11.040 --> 00:05:16.360 align:start position:0% at the Java developer conference in 1998 this<00:05:11.190> was<00:05:11.400> a<00:05:11.430> giveaway<00:05:12.169> and<00:05:13.550> what<00:05:14.550> it<00:05:14.729> is<00:05:14.910> is<00:05:15.150> a 00:05:16.360 --> 00:05:16.370 align:start position:0% this was a giveaway and what it is is a 00:05:16.370 --> 00:05:18.560 align:start position:0% this was a giveaway and what it is is a there<00:05:17.370> is<00:05:17.400> basically<00:05:17.850> a<00:05:17.940> chip<00:05:18.210> in<00:05:18.360> there 00:05:18.560 --> 00:05:18.570 align:start position:0% there is basically a chip in there 00:05:18.570 --> 00:05:22.909 align:start position:0% there is basically a chip in there running<00:05:19.530> Java<00:05:20.479> with<00:05:21.479> a<00:05:21.780> battery<00:05:22.260> in<00:05:22.410> there<00:05:22.620> and 00:05:22.909 --> 00:05:22.919 align:start position:0% running Java with a battery in there and 00:05:22.919 --> 00:05:25.129 align:start position:0% running Java with a battery in there and the<00:05:23.550> external<00:05:23.910> part<00:05:24.389> is<00:05:24.570> actually<00:05:24.720> a<00:05:24.930> physical 00:05:25.129 --> 00:05:25.139 align:start position:0% the external part is actually a physical 00:05:25.139 --> 00:05:32.180 align:start position:0% the external part is actually a physical contact<00:05:27.200> and<00:05:29.900> it<00:05:30.900> was<00:05:31.110> doing<00:05:31.440> public<00:05:31.979> key 00:05:32.180 --> 00:05:32.190 align:start position:0% contact and it was doing public key 00:05:32.190 --> 00:05:39.320 align:start position:0% contact and it was doing public key encryption<00:05:33.380> in<00:05:34.520> 1998<00:05:36.320> and<00:05:37.850> this<00:05:38.850> is<00:05:39.000> how<00:05:39.150> it 00:05:39.320 --> 00:05:39.330 align:start position:0% encryption in 1998 and this is how it 00:05:39.330 --> 00:05:42.920 align:start position:0% encryption in 1998 and this is how it was<00:05:39.449> envisaged<00:05:40.080> it<00:05:40.919> would<00:05:41.070> be<00:05:41.190> used<00:05:41.780> lots<00:05:42.780> of 00:05:42.920 --> 00:05:42.930 align:start position:0% was envisaged it would be used lots of 00:05:42.930 --> 00:05:43.990 align:start position:0% was envisaged it would be used lots of things<00:05:43.139> that<00:05:43.289> we're<00:05:43.410> talking<00:05:43.560> about<00:05:43.740> now 00:05:43.990 --> 00:05:44.000 align:start position:0% things that we're talking about now 00:05:44.000 --> 00:05:50.540 align:start position:0% things that we're talking about now smart<00:05:45.000> locks<00:05:47.539> the<00:05:48.539> the<00:05:49.080> the<00:05:49.470> blue<00:05:49.860> dot<00:05:50.190> the<00:05:50.430> way 00:05:50.540 --> 00:05:50.550 align:start position:0% smart locks the the the blue dot the way 00:05:50.550 --> 00:05:53.420 align:start position:0% smart locks the the the blue dot the way that<00:05:50.789> that<00:05:50.910> works<00:05:51.150> is<00:05:51.630> you<00:05:52.530> would<00:05:53.190> you<00:05:53.340> would 00:05:53.420 --> 00:05:53.430 align:start position:0% that that works is you would you would 00:05:53.430 --> 00:05:57.620 align:start position:0% that that works is you would you would physically<00:05:53.910> touch<00:05:54.330> your<00:05:54.960> ring<00:05:55.260> onto<00:05:56.240> on<00:05:57.240> to 00:05:57.620 --> 00:05:57.630 align:start position:0% physically touch your ring onto on to 00:05:57.630 --> 00:06:01.610 align:start position:0% physically touch your ring onto on to the<00:05:57.750> blue<00:05:57.900> button<00:05:58.289> that<00:05:58.610> would<00:05:59.610> do<00:06:00.620> signing 00:06:01.610 --> 00:06:01.620 align:start position:0% the blue button that would do signing 00:06:01.620 --> 00:06:04.400 align:start position:0% the blue button that would do signing using<00:06:02.610> the<00:06:02.729> private<00:06:02.970> key<00:06:03.180> that<00:06:03.360> was<00:06:03.630> in<00:06:03.810> this 00:06:04.400 --> 00:06:04.410 align:start position:0% using the private key that was in this 00:06:04.410 --> 00:06:08.450 align:start position:0% using the private key that was in this device<00:06:05.900> and<00:06:06.900> really<00:06:07.590> I<00:06:07.740> mean<00:06:07.919> barring<00:06:08.370> the 00:06:08.450 --> 00:06:08.460 align:start position:0% device and really I mean barring the 00:06:08.460 --> 00:06:11.060 align:start position:0% device and really I mean barring the fact<00:06:08.669> that<00:06:08.729> you<00:06:08.849> haven't<00:06:09.030> got<00:06:09.770> NFC<00:06:10.770> at<00:06:10.919> that 00:06:11.060 --> 00:06:11.070 align:start position:0% fact that you haven't got NFC at that 00:06:11.070 --> 00:06:14.029 align:start position:0% fact that you haven't got NFC at that point<00:06:11.370> it's<00:06:11.910> a<00:06:12.300> lot<00:06:13.020> of<00:06:13.050> the<00:06:13.349> sort<00:06:13.830> of<00:06:13.860> things 00:06:14.029 --> 00:06:14.039 align:start position:0% point it's a lot of the sort of things 00:06:14.039 --> 00:06:18.500 align:start position:0% point it's a lot of the sort of things that<00:06:14.220> we're<00:06:14.310> looking<00:06:14.430> at<00:06:14.669> now<00:06:17.120> coming<00:06:18.120> right 00:06:18.500 --> 00:06:18.510 align:start position:0% that we're looking at now coming right 00:06:18.510 --> 00:06:22.610 align:start position:0% that we're looking at now coming right up<00:06:18.570> to<00:06:18.840> the<00:06:18.930> future<00:06:20.930> this<00:06:21.930> is<00:06:21.990> the<00:06:22.229> Samsung 00:06:22.610 --> 00:06:22.620 align:start position:0% up to the future this is the Samsung 00:06:22.620 --> 00:06:26.420 align:start position:0% up to the future this is the Samsung gear<00:06:22.860> s<00:06:23.099> 3<00:06:24.260> SmartWatch<00:06:25.260> just<00:06:26.039> being<00:06:26.220> announced 00:06:26.420 --> 00:06:26.430 align:start position:0% gear s 3 SmartWatch just being announced 00:06:26.430 --> 00:06:29.089 align:start position:0% gear s 3 SmartWatch just being announced but<00:06:26.700> not<00:06:26.880> released<00:06:27.180> yet<00:06:27.300> on<00:06:27.810> my<00:06:27.870> other<00:06:28.620> wrist<00:06:28.860> I 00:06:29.089 --> 00:06:29.099 align:start position:0% but not released yet on my other wrist I 00:06:29.099 --> 00:06:31.969 align:start position:0% but not released yet on my other wrist I have<00:06:29.280> a<00:06:29.310> an<00:06:29.720> s2<00:06:30.720> which<00:06:31.080> is<00:06:31.260> pretty<00:06:31.740> similar 00:06:31.969 --> 00:06:31.979 align:start position:0% have a an s2 which is pretty similar 00:06:31.979 --> 00:06:35.930 align:start position:0% have a an s2 which is pretty similar spec<00:06:32.370> to<00:06:32.520> it<00:06:32.669> but<00:06:33.630> if<00:06:33.720> you<00:06:33.840> look<00:06:34.050> at<00:06:34.139> this<00:06:34.940> you 00:06:35.930 --> 00:06:35.940 align:start position:0% spec to it but if you look at this you 00:06:35.940 --> 00:06:37.339 align:start position:0% spec to it but if you look at this you know<00:06:35.970> you've<00:06:36.180> got<00:06:36.330> a<00:06:36.360> you've<00:06:36.660> got<00:06:36.690> a<00:06:36.780> dual<00:06:37.139> core 00:06:37.339 --> 00:06:37.349 align:start position:0% know you've got a you've got a dual core 00:06:37.349 --> 00:06:42.140 align:start position:0% know you've got a you've got a dual core ARM<00:06:37.650> chip<00:06:39.229> 3/4<00:06:40.229> of<00:06:40.260> a<00:06:40.410> gig<00:06:40.560> of<00:06:40.590> memory<00:06:41.370> 4<00:06:41.849> gig<00:06:42.000> of 00:06:42.140 --> 00:06:42.150 align:start position:0% ARM chip 3/4 of a gig of memory 4 gig of 00:06:42.150 --> 00:06:46.520 align:start position:0% ARM chip 3/4 of a gig of memory 4 gig of flash<00:06:42.360> storage<00:06:43.550> not<00:06:44.550> only<00:06:45.320> Bluetooth<00:06:46.320> and 00:06:46.520 --> 00:06:46.530 align:start position:0% flash storage not only Bluetooth and 00:06:46.530 --> 00:06:53.089 align:start position:0% flash storage not only Bluetooth and Wi-Fi<00:06:46.740> but<00:06:47.729> also<00:06:47.910> LTE<00:06:48.479> and<00:06:48.870> GPS<00:06:51.979> accelerates<00:06:52.979> a 00:06:53.089 --> 00:06:53.099 align:start position:0% Wi-Fi but also LTE and GPS accelerates a 00:06:53.099 --> 00:06:55.730 align:start position:0% Wi-Fi but also LTE and GPS accelerates a gyro<00:06:53.340> heart<00:06:53.909> rate<00:06:54.090> monitor<00:06:54.419> and<00:06:54.450> so<00:06:54.690> on 00:06:55.730 --> 00:06:55.740 align:start position:0% gyro heart rate monitor and so on 00:06:55.740 --> 00:06:57.680 align:start position:0% gyro heart rate monitor and so on and<00:06:55.980> and<00:06:56.580> I<00:06:56.910> mean<00:06:57.030> the<00:06:57.120> other<00:06:57.270> thing<00:06:57.330> that<00:06:57.510> you 00:06:57.680 --> 00:06:57.690 align:start position:0% and and I mean the other thing that you 00:06:57.690 --> 00:07:00.860 align:start position:0% and and I mean the other thing that you have<00:06:57.720> on<00:06:57.990> this<00:06:58.680> device<00:06:59.040> is<00:06:59.580> actually<00:06:59.970> you've 00:07:00.860 --> 00:07:00.870 align:start position:0% have on this device is actually you've 00:07:00.870 --> 00:07:02.930 align:start position:0% have on this device is actually you've got<00:07:01.020> a<00:07:01.050> GPU<00:07:01.470> with<00:07:01.800> hardware<00:07:02.250> accelerated<00:07:02.760> to 00:07:02.930 --> 00:07:02.940 align:start position:0% got a GPU with hardware accelerated to 00:07:02.940 --> 00:07:08.600 align:start position:0% got a GPU with hardware accelerated to 3d<00:07:03.270> graphics<00:07:03.690> on<00:07:03.900> your<00:07:03.960> watch<00:07:07.220> so<00:07:08.220> this<00:07:08.370> kind 00:07:08.600 --> 00:07:08.610 align:start position:0% 3d graphics on your watch so this kind 00:07:08.610 --> 00:07:11.300 align:start position:0% 3d graphics on your watch so this kind of<00:07:08.670> caliber<00:07:09.090> of<00:07:09.120> devices<00:07:09.810> obviously<00:07:10.190> you<00:07:11.190> know 00:07:11.300 --> 00:07:11.310 align:start position:0% of caliber of devices obviously you know 00:07:11.310 --> 00:07:15.650 align:start position:0% of caliber of devices obviously you know it's<00:07:11.550> it's<00:07:11.790> kind<00:07:12.030> of<00:07:12.060> top-end<00:07:12.300> for<00:07:12.720> that<00:07:14.660> but 00:07:15.650 --> 00:07:15.660 align:start position:0% it's it's kind of top-end for that but 00:07:15.660 --> 00:07:17.990 align:start position:0% it's it's kind of top-end for that but it's<00:07:15.810> indicative<00:07:16.110> of<00:07:16.440> how<00:07:16.910> even<00:07:17.910> these 00:07:17.990 --> 00:07:18.000 align:start position:0% it's indicative of how even these 00:07:18.000 --> 00:07:20.420 align:start position:0% it's indicative of how even these constrained<00:07:18.540> devices<00:07:19.020> are<00:07:19.200> really<00:07:19.650> moving<00:07:20.250> up 00:07:20.420 --> 00:07:20.430 align:start position:0% constrained devices are really moving up 00:07:20.430 --> 00:07:26.530 align:start position:0% constrained devices are really moving up in<00:07:20.610> spec<00:07:21.080> but<00:07:22.080> it's<00:07:22.230> expensive<00:07:25.250> project<00:07:26.250> chip 00:07:26.530 --> 00:07:26.540 align:start position:0% in spec but it's expensive project chip 00:07:26.540 --> 00:07:31.190 align:start position:0% in spec but it's expensive project chip nine<00:07:27.540> dollars<00:07:29.390> and<00:07:30.390> what<00:07:30.690> you<00:07:30.780> have<00:07:30.930> there 00:07:31.190 --> 00:07:31.200 align:start position:0% nine dollars and what you have there 00:07:31.200 --> 00:07:33.740 align:start position:0% nine dollars and what you have there again<00:07:31.560> you<00:07:32.400> know<00:07:32.520> you've<00:07:32.670> got<00:07:32.880> a<00:07:32.910> system<00:07:33.600> on<00:07:33.720> a 00:07:33.740 --> 00:07:33.750 align:start position:0% again you know you've got a system on a 00:07:33.750 --> 00:07:37.120 align:start position:0% again you know you've got a system on a chip<00:07:33.840> an<00:07:34.200> arm<00:07:34.350> device<00:07:34.620> you've<00:07:35.010> got<00:07:35.370> a<00:07:35.400> Mali<00:07:35.670> GPU 00:07:37.120 --> 00:07:37.130 align:start position:0% chip an arm device you've got a Mali GPU 00:07:37.130 --> 00:07:41.930 align:start position:0% chip an arm device you've got a Mali GPU you<00:07:38.130> know<00:07:38.480> nearly<00:07:39.480> as<00:07:39.600> good<00:07:39.750> as<00:07:39.900> speck<00:07:40.940> but 00:07:41.930 --> 00:07:41.940 align:start position:0% you know nearly as good as speck but 00:07:41.940 --> 00:07:48.310 align:start position:0% you know nearly as good as speck but it's<00:07:42.120> nine<00:07:42.300> dollars<00:07:44.330> if<00:07:45.330> you<00:07:45.930> go<00:07:46.050> down<00:07:46.260> lower 00:07:48.310 --> 00:07:48.320 align:start position:0% it's nine dollars if you go down lower 00:07:48.320 --> 00:07:51.730 align:start position:0% it's nine dollars if you go down lower you're<00:07:49.320> not<00:07:49.440> gonna<00:07:49.530> run<00:07:49.740> a<00:07:49.800> theory<00:07:50.160> on<00:07:50.190> this 00:07:51.730 --> 00:07:51.740 align:start position:0% you're not gonna run a theory on this 00:07:51.740 --> 00:07:55.570 align:start position:0% you're not gonna run a theory on this but<00:07:53.360> espresso<00:07:54.360> systems<00:07:54.960> who<00:07:55.290> are 00:07:55.570 --> 00:07:55.580 align:start position:0% but espresso systems who are 00:07:55.580 --> 00:08:00.710 align:start position:0% but espresso systems who are shanghai-based<00:07:58.190> this<00:07:59.190> chip<00:07:59.580> you<00:08:00.360> can<00:08:00.390> get<00:08:00.630> it 00:08:00.710 --> 00:08:00.720 align:start position:0% shanghai-based this chip you can get it 00:08:00.720 --> 00:08:03.710 align:start position:0% shanghai-based this chip you can get it for<00:08:00.810> about<00:08:01.050> for<00:08:01.560> about<00:08:01.710> $2<00:08:02.310> and<00:08:02.610> it's<00:08:02.820> it's 00:08:03.710 --> 00:08:03.720 align:start position:0% for about for about $2 and it's it's 00:08:03.720 --> 00:08:07.000 align:start position:0% for about for about $2 and it's it's about<00:08:03.930> the<00:08:04.110> cheapest<00:08:04.560> kind<00:08:04.770> of<00:08:04.890> Wi-Fi<00:08:05.340> capable 00:08:07.000 --> 00:08:07.010 align:start position:0% about the cheapest kind of Wi-Fi capable 00:08:07.010 --> 00:08:11.090 align:start position:0% about the cheapest kind of Wi-Fi capable device<00:08:08.010> you<00:08:08.190> can<00:08:08.310> get<00:08:08.630> you<00:08:09.630> know<00:08:09.660> again<00:08:10.100> 32-bit 00:08:11.090 --> 00:08:11.100 align:start position:0% device you can get you know again 32-bit 00:08:11.100 --> 00:08:16.100 align:start position:0% device you can get you know again 32-bit risc<00:08:11.310> chip<00:08:11.550> I<00:08:11.790> mean<00:08:12.570> very<00:08:12.750> very<00:08:13.170> low<00:08:13.730> specs<00:08:15.110> but 00:08:16.100 --> 00:08:16.110 align:start position:0% risc chip I mean very very low specs but 00:08:16.110 --> 00:08:18.020 align:start position:0% risc chip I mean very very low specs but this<00:08:16.260> kind<00:08:16.620> of<00:08:16.770> price<00:08:17.130> point<00:08:17.160> and<00:08:17.670> this<00:08:17.760> kind 00:08:18.020 --> 00:08:18.030 align:start position:0% this kind of price point and this kind 00:08:18.030 --> 00:08:21.080 align:start position:0% this kind of price point and this kind of<00:08:18.090> caliber<00:08:18.540> of<00:08:18.570> device<00:08:19.220> is<00:08:20.220> likely<00:08:20.760> to<00:08:20.910> sort 00:08:21.080 --> 00:08:21.090 align:start position:0% of caliber of device is likely to sort 00:08:21.090 --> 00:08:22.760 align:start position:0% of caliber of device is likely to sort of<00:08:21.210> creep<00:08:21.480> up<00:08:21.690> in<00:08:21.840> specs<00:08:22.230> to<00:08:22.440> some<00:08:22.620> of<00:08:22.710> those 00:08:22.760 --> 00:08:22.770 align:start position:0% of creep up in specs to some of those 00:08:22.770 --> 00:08:25.100 align:start position:0% of creep up in specs to some of those higher<00:08:23.040> ones<00:08:23.280> over<00:08:23.520> the<00:08:23.610> coming<00:08:23.820> years<00:08:24.150> so<00:08:24.420> you 00:08:25.100 --> 00:08:25.110 align:start position:0% higher ones over the coming years so you 00:08:25.110 --> 00:08:26.660 align:start position:0% higher ones over the coming years so you know<00:08:25.230> that<00:08:25.440> that<00:08:25.620> kind<00:08:25.830> of<00:08:25.980> price<00:08:26.220> point<00:08:26.250> is 00:08:26.660 --> 00:08:26.670 align:start position:0% know that that kind of price point is 00:08:26.670 --> 00:08:30.310 align:start position:0% know that that kind of price point is not<00:08:26.940> inconceivable<00:08:27.480> for<00:08:28.290> running<00:08:29.030> an 00:08:30.310 --> 00:08:30.320 align:start position:0% not inconceivable for running an 00:08:30.320 --> 00:08:32.780 align:start position:0% not inconceivable for running an aetherium<00:08:31.320> capable<00:08:31.800> device<00:08:32.040> in<00:08:32.520> the<00:08:32.640> near 00:08:32.780 --> 00:08:32.790 align:start position:0% aetherium capable device in the near 00:08:32.790 --> 00:08:37.130 align:start position:0% aetherium capable device in the near future<00:08:34.880> this<00:08:35.880> is<00:08:35.940> a<00:08:36.090> quote<00:08:36.420> that<00:08:36.600> you<00:08:36.660> you<00:08:37.020> know 00:08:37.130 --> 00:08:37.140 align:start position:0% future this is a quote that you you know 00:08:37.140 --> 00:08:38.510 align:start position:0% future this is a quote that you you know this<00:08:37.290> is<00:08:37.350> a<00:08:37.440> figure<00:08:37.740> that<00:08:37.830> you<00:08:38.010> see<00:08:38.190> all<00:08:38.340> the 00:08:38.510 --> 00:08:38.520 align:start position:0% this is a figure that you see all the 00:08:38.520 --> 00:08:40.700 align:start position:0% this is a figure that you see all the time<00:08:38.760> is<00:08:39.060> so<00:08:39.270> you<00:08:39.330> know<00:08:39.480> gonna<00:08:39.960> be<00:08:40.050> 50<00:08:40.530> billion 00:08:40.700 --> 00:08:40.710 align:start position:0% time is so you know gonna be 50 billion 00:08:40.710 --> 00:08:42.560 align:start position:0% time is so you know gonna be 50 billion IOT<00:08:41.250> devices<00:08:41.550> by<00:08:41.850> 2020 00:08:42.560 --> 00:08:42.570 align:start position:0% IOT devices by 2020 00:08:42.570 --> 00:08:44.510 align:start position:0% IOT devices by 2020 looks<00:08:43.170> like<00:08:43.350> the<00:08:43.530> consensus<00:08:44.100> on<00:08:44.220> that<00:08:44.400> has 00:08:44.510 --> 00:08:44.520 align:start position:0% looks like the consensus on that has 00:08:44.520 --> 00:08:47.360 align:start position:0% looks like the consensus on that has come<00:08:44.670> down<00:08:44.700> to<00:08:44.880> 30<00:08:45.360> billion<00:08:45.660> which<00:08:46.590> is<00:08:46.800> you 00:08:47.360 --> 00:08:47.370 align:start position:0% come down to 30 billion which is you 00:08:47.370 --> 00:08:49.910 align:start position:0% come down to 30 billion which is you know<00:08:47.460> it's<00:08:47.760> less<00:08:48.000> but<00:08:48.210> it's<00:08:48.360> still<00:08:48.920> gigantic 00:08:49.910 --> 00:08:49.920 align:start position:0% know it's less but it's still gigantic 00:08:49.920 --> 00:08:55.160 align:start position:0% know it's less but it's still gigantic number<00:08:50.130> of<00:08:50.220> machines<00:08:53.810> so<00:08:54.810> you<00:08:54.840> might<00:08:55.050> be 00:08:55.160 --> 00:08:55.170 align:start position:0% number of machines so you might be 00:08:55.170 --> 00:08:56.720 align:start position:0% number of machines so you might be thinking<00:08:55.530> you<00:08:55.800> know<00:08:56.100> some<00:08:56.340> of<00:08:56.430> this<00:08:56.490> stuff 00:08:56.720 --> 00:08:56.730 align:start position:0% thinking you know some of this stuff 00:08:56.730 --> 00:08:58.040 align:start position:0% thinking you know some of this stuff that<00:08:56.760> you're<00:08:57.000> saying<00:08:57.150> here<00:08:57.360> Bob<00:08:57.540> off<00:08:57.690> I<00:08:57.870> think 00:08:58.040 --> 00:08:58.050 align:start position:0% that you're saying here Bob off I think 00:08:58.050 --> 00:09:01.070 align:start position:0% that you're saying here Bob off I think I've<00:08:58.170> heard<00:08:58.290> this<00:08:58.350> before<00:08:59.660> so<00:09:00.660> this<00:09:00.780> is<00:09:00.810> Paul 00:09:01.070 --> 00:09:01.080 align:start position:0% I've heard this before so this is Paul 00:09:01.080 --> 00:09:06.560 align:start position:0% I've heard this before so this is Paul Brody<00:09:01.500> who<00:09:02.900> was<00:09:03.900> previously<00:09:04.350> at<00:09:04.530> IBM<00:09:05.570> leading 00:09:06.560 --> 00:09:06.570 align:start position:0% Brody who was previously at IBM leading 00:09:06.570 --> 00:09:09.330 align:start position:0% Brody who was previously at IBM leading project<00:09:06.990> adept<00:09:07.320> and 00:09:09.330 --> 00:09:09.340 align:start position:0% project adept and 00:09:09.340 --> 00:09:16.540 align:start position:0% project adept and and<00:09:10.540> here<00:09:13.150> is<00:09:14.150> Henning<00:09:15.160> who<00:09:16.160> I<00:09:16.220> believe<00:09:16.520> is 00:09:16.540 --> 00:09:16.550 align:start position:0% and here is Henning who I believe is 00:09:16.550 --> 00:09:20.280 align:start position:0% and here is Henning who I believe is here<00:09:16.880> later<00:09:17.690> in<00:09:17.810> the<00:09:17.960> week<00:09:18.080> and<00:09:18.730> project<00:09:19.730> depth 00:09:20.280 --> 00:09:20.290 align:start position:0% here later in the week and project depth 00:09:20.290 --> 00:09:25.810 align:start position:0% here later in the week and project depth was<00:09:21.290> unveiled<00:09:21.500> in<00:09:22.040> January<00:09:22.730> 20<00:09:23.030> 2015<00:09:24.820> using 00:09:25.810 --> 00:09:25.820 align:start position:0% was unveiled in January 20 2015 using 00:09:25.820 --> 00:09:26.920 align:start position:0% was unveiled in January 20 2015 using Tallahassee 00:09:26.920 --> 00:09:26.930 align:start position:0% Tallahassee 00:09:26.930 --> 00:09:30.220 align:start position:0% Tallahassee BitTorrent<00:09:27.830> and<00:09:27.920> etherium<00:09:28.870> and<00:09:29.870> there<00:09:30.110> are 00:09:30.220 --> 00:09:30.230 align:start position:0% BitTorrent and etherium and there are 00:09:30.230 --> 00:09:32.200 align:start position:0% BitTorrent and etherium and there are follow-on<00:09:30.680> projects<00:09:31.460> which<00:09:31.580> are<00:09:31.700> still<00:09:31.880> going 00:09:32.200 --> 00:09:32.210 align:start position:0% follow-on projects which are still going 00:09:32.210 --> 00:09:38.220 align:start position:0% follow-on projects which are still going here<00:09:32.510> which<00:09:33.380> is<00:09:33.560> really<00:09:33.920> looking<00:09:34.370> to<00:09:35.860> to<00:09:36.860> blend 00:09:38.220 --> 00:09:38.230 align:start position:0% here which is really looking to to blend 00:09:38.230 --> 00:09:42.970 align:start position:0% here which is really looking to to blend blockchain<00:09:39.230> and<00:09:39.260> IOT<00:09:40.510> and<00:09:41.510> these<00:09:42.440> efforts<00:09:42.650> are 00:09:42.970 --> 00:09:42.980 align:start position:0% blockchain and IOT and these efforts are 00:09:42.980 --> 00:09:44.890 align:start position:0% blockchain and IOT and these efforts are still<00:09:43.070> really<00:09:43.550> ongoing<00:09:44.210> though<00:09:44.360> the<00:09:44.510> projects 00:09:44.890 --> 00:09:44.900 align:start position:0% still really ongoing though the projects 00:09:44.900 --> 00:09:47.020 align:start position:0% still really ongoing though the projects are<00:09:45.020> changing<00:09:45.410> this<00:09:46.340> is<00:09:46.400> still<00:09:46.730> what<00:09:46.880> we're 00:09:47.020 --> 00:09:47.030 align:start position:0% are changing this is still what we're 00:09:47.030 --> 00:09:51.100 align:start position:0% are changing this is still what we're all<00:09:47.150> aiming<00:09:47.360> for<00:09:49.240> and<00:09:50.240> this<00:09:50.450> is<00:09:50.510> a<00:09:50.630> slide<00:09:50.930> from 00:09:51.100 --> 00:09:51.110 align:start position:0% all aiming for and this is a slide from 00:09:51.110 --> 00:09:53.470 align:start position:0% all aiming for and this is a slide from one<00:09:51.590> of<00:09:51.710> the<00:09:51.830> the<00:09:52.310> project<00:09:52.580> to<00:09:52.850> DEP<00:09:53.030> ones<00:09:53.270> which 00:09:53.470 --> 00:09:53.480 align:start position:0% one of the the project to DEP ones which 00:09:53.480 --> 00:09:55.930 align:start position:0% one of the the project to DEP ones which is<00:09:53.630> basically<00:09:53.930> showing<00:09:54.260> this<00:09:54.580> this<00:09:55.580> really 00:09:55.930 --> 00:09:55.940 align:start position:0% is basically showing this this really 00:09:55.940 --> 00:09:57.430 align:start position:0% is basically showing this this really long-term<00:09:56.150> progression<00:09:56.900> through<00:09:57.140> from<00:09:57.290> the 00:09:57.430 --> 00:09:57.440 align:start position:0% long-term progression through from the 00:09:57.440 --> 00:09:59.730 align:start position:0% long-term progression through from the 50s<00:09:57.860> you<00:09:58.520> know<00:09:58.670> really<00:09:58.940> small<00:09:59.210> number<00:09:59.480> of 00:09:59.730 --> 00:09:59.740 align:start position:0% 50s you know really small number of 00:09:59.740 --> 00:10:02.740 align:start position:0% 50s you know really small number of mainframes<00:10:00.740> through<00:10:01.240> personal<00:10:02.240> computers 00:10:02.740 --> 00:10:02.750 align:start position:0% mainframes through personal computers 00:10:02.750 --> 00:10:05.500 align:start position:0% mainframes through personal computers through<00:10:03.020> mobile<00:10:03.260> and<00:10:04.130> on<00:10:04.700> and<00:10:04.910> on<00:10:04.970> and<00:10:05.120> on<00:10:05.270> and 00:10:05.500 --> 00:10:05.510 align:start position:0% through mobile and on and on and on and 00:10:05.510 --> 00:10:08.170 align:start position:0% through mobile and on and on and on and we<00:10:06.050> are<00:10:06.080> going<00:10:06.440> to<00:10:06.590> have<00:10:06.740> a<00:10:06.770> gigantic<00:10:07.400> number 00:10:08.170 --> 00:10:08.180 align:start position:0% we are going to have a gigantic number 00:10:08.180 --> 00:10:13.450 align:start position:0% we are going to have a gigantic number of<00:10:08.420> devices<00:10:10.030> in<00:10:11.030> the<00:10:11.300> near<00:10:11.420> future<00:10:11.980> though<00:10:12.980> who 00:10:13.450 --> 00:10:13.460 align:start position:0% of devices in the near future though who 00:10:13.460 --> 00:10:14.590 align:start position:0% of devices in the near future though who knows<00:10:13.640> what<00:10:13.820> the<00:10:13.910> actual<00:10:14.089> figures<00:10:14.390> are<00:10:14.480> going 00:10:14.590 --> 00:10:14.600 align:start position:0% knows what the actual figures are going 00:10:14.600 --> 00:10:18.070 align:start position:0% knows what the actual figures are going to<00:10:14.660> be<00:10:15.790> so<00:10:16.790> I<00:10:16.820> mean<00:10:16.970> across<00:10:17.240> that<00:10:17.420> you've<00:10:17.839> got<00:10:18.050> a 00:10:18.070 --> 00:10:18.080 align:start position:0% to be so I mean across that you've got a 00:10:18.080 --> 00:10:21.760 align:start position:0% to be so I mean across that you've got a sliding<00:10:18.470> scale<00:10:18.890> of<00:10:18.920> options<00:10:19.400> really<00:10:20.770> for 00:10:21.760 --> 00:10:21.770 align:start position:0% sliding scale of options really for 00:10:21.770 --> 00:10:24.040 align:start position:0% sliding scale of options really for aetherium<00:10:22.070> you<00:10:23.000> know<00:10:23.120> the<00:10:23.270> very<00:10:23.450> easy<00:10:23.690> thing 00:10:24.040 --> 00:10:24.050 align:start position:0% aetherium you know the very easy thing 00:10:24.050 --> 00:10:25.570 align:start position:0% aetherium you know the very easy thing to<00:10:24.080> do<00:10:24.290> on<00:10:24.410> a<00:10:24.440> very<00:10:24.650> constrained<00:10:25.100> device<00:10:25.370> right 00:10:25.570 --> 00:10:25.580 align:start position:0% to do on a very constrained device right 00:10:25.580 --> 00:10:27.790 align:start position:0% to do on a very constrained device right now<00:10:25.820> is<00:10:26.000> basically<00:10:26.390> not<00:10:26.660> really<00:10:26.690> to<00:10:27.260> run 00:10:27.790 --> 00:10:27.800 align:start position:0% now is basically not really to run 00:10:27.800 --> 00:10:29.770 align:start position:0% now is basically not really to run anything<00:10:28.220> on<00:10:28.460> it<00:10:28.610> but<00:10:29.089> have<00:10:29.240> it<00:10:29.360> talked<00:10:29.600> to<00:10:29.750> a 00:10:29.770 --> 00:10:29.780 align:start position:0% anything on it but have it talked to a 00:10:29.780 --> 00:10:31.420 align:start position:0% anything on it but have it talked to a trusted<00:10:30.200> server 00:10:31.420 --> 00:10:31.430 align:start position:0% trusted server 00:10:31.430 --> 00:10:33.220 align:start position:0% trusted server you<00:10:31.760> know<00:10:31.880> just<00:10:32.089> sign<00:10:32.270> transactions<00:10:32.900> and<00:10:33.080> talk 00:10:33.220 --> 00:10:33.230 align:start position:0% you know just sign transactions and talk 00:10:33.230 --> 00:10:34.930 align:start position:0% you know just sign transactions and talk to<00:10:33.350> a<00:10:33.380> trusted<00:10:33.589> server<00:10:34.100> I<00:10:34.190> think<00:10:34.370> that's<00:10:34.520> kind 00:10:34.930 --> 00:10:34.940 align:start position:0% to a trusted server I think that's kind 00:10:34.940 --> 00:10:36.160 align:start position:0% to a trusted server I think that's kind of<00:10:35.000> the<00:10:35.120> integration<00:10:35.660> route<00:10:35.839> that<00:10:35.990> you<00:10:36.050> can 00:10:36.160 --> 00:10:36.170 align:start position:0% of the integration route that you can 00:10:36.170 --> 00:10:40.930 align:start position:0% of the integration route that you can see<00:10:36.380> on<00:10:36.500> a<00:10:36.530> lot<00:10:36.740> of<00:10:37.180> of<00:10:38.180> mobile<00:10:38.660> devices<00:10:39.940> but 00:10:40.930 --> 00:10:40.940 align:start position:0% see on a lot of of mobile devices but 00:10:40.940 --> 00:10:45.220 align:start position:0% see on a lot of of mobile devices but like<00:10:41.150> client<00:10:42.550> is<00:10:43.550> a<00:10:44.030> big<00:10:44.300> big<00:10:44.480> step<00:10:44.750> up<00:10:44.930> to<00:10:45.110> it 00:10:45.220 --> 00:10:45.230 align:start position:0% like client is a big big step up to it 00:10:45.230 --> 00:10:49.090 align:start position:0% like client is a big big step up to it you<00:10:45.950> know<00:10:45.980> from<00:10:46.310> that<00:10:46.490> which<00:10:46.700> is<00:10:46.880> really<00:10:48.100> you 00:10:49.090 --> 00:10:49.100 align:start position:0% you know from that which is really you 00:10:49.100 --> 00:10:51.160 align:start position:0% you know from that which is really you know<00:10:49.130> it's<00:10:49.250> it's<00:10:49.760> it's<00:10:50.120> really<00:10:50.270> then<00:10:50.720> running 00:10:51.160 --> 00:10:51.170 align:start position:0% know it's it's it's really then running 00:10:51.170 --> 00:10:54.520 align:start position:0% know it's it's it's really then running as<00:10:51.350> a<00:10:51.800> standalone<00:10:52.310> node<00:10:52.700> that<00:10:52.910> is<00:10:53.410> you<00:10:54.410> know 00:10:54.520 --> 00:10:54.530 align:start position:0% as a standalone node that is you know 00:10:54.530 --> 00:10:58.270 align:start position:0% as a standalone node that is you know not<00:10:54.770> assuming<00:10:55.430> trust<00:10:56.710> and<00:10:57.710> then<00:10:58.130> up<00:10:58.250> through 00:10:58.270 --> 00:10:58.280 align:start position:0% not assuming trust and then up through 00:10:58.280 --> 00:11:01.420 align:start position:0% not assuming trust and then up through full<00:10:58.760> node<00:10:58.940> and<00:10:59.089> archival<00:10:59.890> but<00:11:00.890> as<00:11:01.040> we<00:11:01.190> as 00:11:01.420 --> 00:11:01.430 align:start position:0% full node and archival but as we as 00:11:01.430 --> 00:11:05.170 align:start position:0% full node and archival but as we as we've<00:11:01.670> heard<00:11:01.880> if<00:11:02.810> they're<00:11:02.990> my<00:11:03.260> client<00:11:04.180> really 00:11:05.170 --> 00:11:05.180 align:start position:0% we've heard if they're my client really 00:11:05.180 --> 00:11:12.520 align:start position:0% we've heard if they're my client really really<00:11:05.390> close<00:11:05.570> now<00:11:09.640> for<00:11:10.640> myself<00:11:11.230> you<00:11:12.230> know<00:11:12.260> the 00:11:12.520 --> 00:11:12.530 align:start position:0% really close now for myself you know the 00:11:12.530 --> 00:11:15.070 align:start position:0% really close now for myself you know the question<00:11:12.860> of<00:11:12.950> why<00:11:13.580> C++<00:11:14.270> for<00:11:14.480> resource 00:11:15.070 --> 00:11:15.080 align:start position:0% question of why C++ for resource 00:11:15.080 --> 00:11:17.230 align:start position:0% question of why C++ for resource constrained<00:11:15.500> devices<00:11:15.770> you<00:11:16.040> know<00:11:16.160> why<00:11:16.370> why<00:11:17.150> am 00:11:17.230 --> 00:11:17.240 align:start position:0% constrained devices you know why why am 00:11:17.240 --> 00:11:19.780 align:start position:0% constrained devices you know why why am I<00:11:17.360> even<00:11:17.390> bothering<00:11:17.630> doing<00:11:18.530> this<00:11:18.680> why<00:11:19.610> am<00:11:19.700> I 00:11:19.780 --> 00:11:19.790 align:start position:0% I even bothering doing this why am I 00:11:19.790 --> 00:11:21.490 align:start position:0% I even bothering doing this why am I even<00:11:19.820> looking<00:11:20.180> at<00:11:20.390> this<00:11:20.540> rather<00:11:20.839> than<00:11:21.050> just 00:11:21.490 --> 00:11:21.500 align:start position:0% even looking at this rather than just 00:11:21.500 --> 00:11:24.280 align:start position:0% even looking at this rather than just you<00:11:22.220> know<00:11:22.370> the<00:11:22.550> Geth<00:11:23.120> implementation<00:11:23.900> and<00:11:24.050> and 00:11:24.280 --> 00:11:24.290 align:start position:0% you know the Geth implementation and and 00:11:24.290 --> 00:11:26.170 align:start position:0% you know the Geth implementation and and really<00:11:24.920> the<00:11:25.040> reason<00:11:25.340> is<00:11:25.460> that<00:11:25.490> if<00:11:25.700> you<00:11:25.820> if<00:11:26.060> you 00:11:26.170 --> 00:11:26.180 align:start position:0% really the reason is that if you if you 00:11:26.180 --> 00:11:27.670 align:start position:0% really the reason is that if you if you look<00:11:26.300> at<00:11:26.450> the<00:11:26.600> the<00:11:26.930> gains<00:11:27.140> that<00:11:27.290> were<00:11:27.470> getting 00:11:27.670 --> 00:11:27.680 align:start position:0% look at the the gains that were getting 00:11:27.680 --> 00:11:29.230 align:start position:0% look at the the gains that were getting from<00:11:27.830> Moore's<00:11:28.040> Law<00:11:28.220> they<00:11:28.430> are<00:11:28.610> slowing<00:11:28.970> down 00:11:29.230 --> 00:11:29.240 align:start position:0% from Moore's Law they are slowing down 00:11:29.240 --> 00:11:31.300 align:start position:0% from Moore's Law they are slowing down you<00:11:30.050> know<00:11:30.170> there's<00:11:30.380> only<00:11:30.440> so<00:11:30.710> small<00:11:31.010> you<00:11:31.160> can 00:11:31.300 --> 00:11:31.310 align:start position:0% you know there's only so small you can 00:11:31.310 --> 00:11:33.970 align:start position:0% you know there's only so small you can get<00:11:31.490> and<00:11:31.820> we're<00:11:32.510> kind<00:11:32.900> of<00:11:32.960> getting<00:11:33.590> towards 00:11:33.970 --> 00:11:33.980 align:start position:0% get and we're kind of getting towards 00:11:33.980 --> 00:11:36.700 align:start position:0% get and we're kind of getting towards the<00:11:34.040> end<00:11:34.190> of<00:11:34.280> the<00:11:34.370> line<00:11:34.490> on<00:11:34.670> that<00:11:35.530> Amdahl's<00:11:36.530> law 00:11:36.700 --> 00:11:36.710 align:start position:0% the end of the line on that Amdahl's law 00:11:36.710 --> 00:11:38.740 align:start position:0% the end of the line on that Amdahl's law is<00:11:37.100> something<00:11:37.310> which<00:11:38.000> a<00:11:38.150> lot<00:11:38.300> of<00:11:38.420> people<00:11:38.660> are 00:11:38.740 --> 00:11:38.750 align:start position:0% is something which a lot of people are 00:11:38.750 --> 00:11:41.620 align:start position:0% is something which a lot of people are not<00:11:38.840> aware<00:11:38.960> of<00:11:39.820> but<00:11:40.820> it's<00:11:40.970> gonna<00:11:41.270> become<00:11:41.600> very 00:11:41.620 --> 00:11:41.630 align:start position:0% not aware of but it's gonna become very 00:11:41.630 --> 00:11:43.390 align:start position:0% not aware of but it's gonna become very very<00:11:42.020> important<00:11:42.530> in<00:11:42.650> the<00:11:42.740> coming<00:11:42.980> years<00:11:43.220> and 00:11:43.390 --> 00:11:43.400 align:start position:0% very important in the coming years and 00:11:43.400 --> 00:11:46.120 align:start position:0% very important in the coming years and what<00:11:43.580> what<00:11:44.330> Amdahl's<00:11:44.750> law<00:11:44.900> is<00:11:45.260> is<00:11:45.500> is<00:11:45.830> saying 00:11:46.120 --> 00:11:46.130 align:start position:0% what what Amdahl's law is is is saying 00:11:46.130 --> 00:11:49.590 align:start position:0% what what Amdahl's law is is is saying is<00:11:46.430> that<00:11:47.020> you<00:11:48.020> know<00:11:48.140> not<00:11:48.530> everything<00:11:49.010> that 00:11:49.590 --> 00:11:49.600 align:start position:0% is that you know not everything that 00:11:49.600 --> 00:11:54.100 align:start position:0% is that you know not everything that there<00:11:50.600> is<00:11:50.720> can<00:11:51.470> be<00:11:52.090> parallelized<00:11:53.090> you<00:11:53.900> know<00:11:54.020> to 00:11:54.100 --> 00:11:54.110 align:start position:0% there is can be parallelized you know to 00:11:54.110 --> 00:11:57.820 align:start position:0% there is can be parallelized you know to an<00:11:54.260> infinite<00:11:54.650> degree<00:11:55.030> programs<00:11:56.030> do<00:11:56.300> have<00:11:56.830> you 00:11:57.820 --> 00:11:57.830 align:start position:0% an infinite degree programs do have you 00:11:57.830 --> 00:11:59.970 align:start position:0% an infinite degree programs do have you know<00:11:57.860> critical<00:11:58.280> path<00:11:58.580> pieces<00:11:59.090> which<00:11:59.300> are 00:11:59.970 --> 00:11:59.980 align:start position:0% know critical path pieces which are 00:11:59.980 --> 00:12:05.560 align:start position:0% know critical path pieces which are serial<00:12:00.980> by<00:12:01.100> nature<00:12:01.550> and<00:12:03.220> depending<00:12:04.220> on<00:12:04.570> the 00:12:05.560 --> 00:12:05.570 align:start position:0% serial by nature and depending on the 00:12:05.570 --> 00:12:07.450 align:start position:0% serial by nature and depending on the parallel<00:12:06.020> proportion<00:12:06.650> that<00:12:07.220> you<00:12:07.310> have 00:12:07.450 --> 00:12:07.460 align:start position:0% parallel proportion that you have 00:12:07.460 --> 00:12:07.990 align:start position:0% parallel proportion that you have available 00:12:07.990 --> 00:12:08.000 align:start position:0% available 00:12:08.000 --> 00:12:10.090 align:start position:0% available you<00:12:08.540> are<00:12:08.690> basically<00:12:08.900> capped<00:12:09.500> on<00:12:09.710> how<00:12:09.920> much 00:12:10.090 --> 00:12:10.100 align:start position:0% you are basically capped on how much 00:12:10.100 --> 00:12:13.930 align:start position:0% you are basically capped on how much speed<00:12:10.460> you<00:12:10.610> can<00:12:10.730> get<00:12:10.910> by<00:12:12.520> by<00:12:13.520> adding<00:12:13.790> more 00:12:13.930 --> 00:12:13.940 align:start position:0% speed you can get by by adding more 00:12:13.940 --> 00:12:17.740 align:start position:0% speed you can get by by adding more cores<00:12:14.180> and<00:12:15.340> and<00:12:16.340> it's<00:12:16.940> and<00:12:17.270> it's<00:12:17.420> a<00:12:17.540> fact 00:12:17.740 --> 00:12:17.750 align:start position:0% cores and and it's and it's a fact 00:12:17.750 --> 00:12:19.870 align:start position:0% cores and and it's and it's a fact really<00:12:18.050> that<00:12:18.380> for<00:12:19.040> the<00:12:19.340> majority<00:12:19.430> of 00:12:19.870 --> 00:12:19.880 align:start position:0% really that for the majority of 00:12:19.880 --> 00:12:22.450 align:start position:0% really that for the majority of general-purpose<00:12:20.480> programs<00:12:21.170> that<00:12:21.560> constant 00:12:22.450 --> 00:12:22.460 align:start position:0% general-purpose programs that constant 00:12:22.460 --> 00:12:25.000 align:start position:0% general-purpose programs that constant it's<00:12:22.580> probably<00:12:22.880> really<00:12:23.060> quite<00:12:23.360> quite<00:12:23.810> low<00:12:24.080> you 00:12:25.000 --> 00:12:25.010 align:start position:0% it's probably really quite quite low you 00:12:25.010 --> 00:12:27.940 align:start position:0% it's probably really quite quite low you know<00:12:25.130> you<00:12:25.190> see<00:12:25.460> on<00:12:25.610> on<00:12:25.880> PCs<00:12:26.680> there's<00:12:27.680> very<00:12:27.890> few 00:12:27.940 --> 00:12:27.950 align:start position:0% know you see on on PCs there's very few 00:12:27.950 --> 00:12:30.130 align:start position:0% know you see on on PCs there's very few apps<00:12:28.339> that<00:12:28.490> can<00:12:28.850> take<00:12:29.180> advantage<00:12:29.300> of<00:12:29.839> you<00:12:30.020> know 00:12:30.130 --> 00:12:30.140 align:start position:0% apps that can take advantage of you know 00:12:30.140 --> 00:12:33.280 align:start position:0% apps that can take advantage of you know four<00:12:30.410> eight<00:12:30.620> sixteen<00:12:31.070> cause<00:12:31.780> you<00:12:32.780> just<00:12:32.960> end<00:12:33.200> up 00:12:33.280 --> 00:12:33.290 align:start position:0% four eight sixteen cause you just end up 00:12:33.290 --> 00:12:35.640 align:start position:0% four eight sixteen cause you just end up with<00:12:33.470> multiple<00:12:33.890> apps<00:12:34.070> running<00:12:34.280> in<00:12:34.400> parallel 00:12:35.640 --> 00:12:35.650 align:start position:0% with multiple apps running in parallel 00:12:35.650 --> 00:12:38.440 align:start position:0% with multiple apps running in parallel so<00:12:36.650> I<00:12:36.680> mean<00:12:36.860> what<00:12:37.010> that<00:12:37.130> means<00:12:37.430> is<00:12:37.790> is<00:12:38.120> raw 00:12:38.440 --> 00:12:38.450 align:start position:0% so I mean what that means is is raw 00:12:38.450 --> 00:12:42.070 align:start position:0% so I mean what that means is is raw performance<00:12:38.960> does<00:12:39.380> ultimately<00:12:39.890> matter<00:12:41.080> you 00:12:42.070 --> 00:12:42.080 align:start position:0% performance does ultimately matter you 00:12:42.080 --> 00:12:46.390 align:start position:0% performance does ultimately matter you know<00:12:42.460> you<00:12:43.460> see<00:12:43.700> now<00:12:44.030> also<00:12:45.010> compiler<00:12:46.010> settings 00:12:46.390 --> 00:12:46.400 align:start position:0% know you see now also compiler settings 00:12:46.400 --> 00:12:49.240 align:start position:0% know you see now also compiler settings optimizing<00:12:47.210> for<00:12:47.390> power<00:12:47.690> usage<00:12:48.200> that<00:12:49.010> where 00:12:49.240 --> 00:12:49.250 align:start position:0% optimizing for power usage that where 00:12:49.250 --> 00:12:50.530 align:start position:0% optimizing for power usage that where you're<00:12:49.400> running<00:12:49.520> from<00:12:49.820> batteries<00:12:50.270> actually 00:12:50.530 --> 00:12:50.540 align:start position:0% you're running from batteries actually 00:12:50.540 --> 00:12:53.290 align:start position:0% you're running from batteries actually the<00:12:50.900> you<00:12:51.410> know<00:12:51.530> the<00:12:51.680> power<00:12:51.860> drain<00:12:52.190> it<00:12:53.089> does 00:12:53.290 --> 00:12:53.300 align:start position:0% the you know the power drain it does 00:12:53.300 --> 00:12:57.040 align:start position:0% the you know the power drain it does matter<00:12:54.070> also<00:12:55.070> modern<00:12:55.550> C++<00:12:56.089> doesn't<00:12:56.570> suck<00:12:56.839> any 00:12:57.040 --> 00:12:57.050 align:start position:0% matter also modern C++ doesn't suck any 00:12:57.050 --> 00:13:03.700 align:start position:0% matter also modern C++ doesn't suck any more<00:12:57.220> most<00:12:58.220> C++<00:12:59.120> is<00:12:59.330> not<00:12:59.600> modern<00:12:59.870> C++<00:13:02.589> but<00:13:03.589> you 00:13:03.700 --> 00:13:03.710 align:start position:0% more most C++ is not modern C++ but you 00:13:03.710 --> 00:13:06.310 align:start position:0% more most C++ is not modern C++ but you can<00:13:04.040> write<00:13:04.430> C++<00:13:04.820> apps<00:13:05.330> that<00:13:05.570> look<00:13:05.720> fairly 00:13:06.310 --> 00:13:06.320 align:start position:0% can write C++ apps that look fairly 00:13:06.320 --> 00:13:08.950 align:start position:0% can write C++ apps that look fairly similar<00:13:06.440> to<00:13:06.770> other<00:13:07.010> ones<00:13:07.750> but<00:13:08.750> most 00:13:08.950 --> 00:13:08.960 align:start position:0% similar to other ones but most 00:13:08.960 --> 00:13:11.560 align:start position:0% similar to other ones but most importantly<00:13:09.500> is<00:13:09.650> maximum<00:13:10.070> portability<00:13:10.220> is<00:13:10.880> C 00:13:11.560 --> 00:13:11.570 align:start position:0% importantly is maximum portability is C 00:13:11.570 --> 00:13:14.470 align:start position:0% importantly is maximum portability is C and<00:13:11.690> C++<00:13:11.839> you<00:13:12.589> know<00:13:12.710> they<00:13:12.890> are<00:13:13.150> the<00:13:14.150> language 00:13:14.470 --> 00:13:14.480 align:start position:0% and C++ you know they are the language 00:13:14.480 --> 00:13:17.620 align:start position:0% and C++ you know they are the language which<00:13:14.720> pretty<00:13:15.650> much<00:13:15.830> all<00:13:16.010> OSS<00:13:16.670> and<00:13:16.700> systems 00:13:17.620 --> 00:13:17.630 align:start position:0% which pretty much all OSS and systems 00:13:17.630 --> 00:13:21.340 align:start position:0% which pretty much all OSS and systems programming<00:13:18.110> is<00:13:18.230> done<00:13:18.260> in<00:13:19.600> so<00:13:20.600> really<00:13:21.050> when 00:13:21.340 --> 00:13:21.350 align:start position:0% programming is done in so really when 00:13:21.350 --> 00:13:22.660 align:start position:0% programming is done in so really when you<00:13:21.470> when<00:13:21.800> you're<00:13:21.920> looking<00:13:22.160> at<00:13:22.310> these<00:13:22.400> very 00:13:22.660 --> 00:13:22.670 align:start position:0% you when you're looking at these very 00:13:22.670 --> 00:13:25.360 align:start position:0% you when you're looking at these very constrained<00:13:23.150> devices<00:13:23.589> having<00:13:24.589> the<00:13:24.800> raw<00:13:25.040> power 00:13:25.360 --> 00:13:25.370 align:start position:0% constrained devices having the raw power 00:13:25.370 --> 00:13:31.870 align:start position:0% constrained devices having the raw power of<00:13:25.550> of<00:13:26.420> C++<00:13:27.200> does<00:13:27.650> actually<00:13:27.920> matter 00:13:31.870 --> 00:13:31.880 align:start position:0% 00:13:31.880 --> 00:13:36.280 align:start position:0% so<00:13:32.569> cross<00:13:32.959> cpp<00:13:33.410> aetherium<00:13:33.889> is<00:13:34.240> is<00:13:35.240> what<00:13:36.199> i've 00:13:36.280 --> 00:13:36.290 align:start position:0% so cross cpp aetherium is is what i've 00:13:36.290 --> 00:13:38.079 align:start position:0% so cross cpp aetherium is is what i've been<00:13:36.380> working<00:13:36.800> on<00:13:36.889> for<00:13:36.949> the<00:13:37.130> last<00:13:37.160> year<00:13:37.730> in<00:13:38.029> a 00:13:38.079 --> 00:13:38.089 align:start position:0% been working on for the last year in a 00:13:38.089 --> 00:13:39.910 align:start position:0% been working on for the last year in a bit<00:13:38.209> and<00:13:38.569> it's<00:13:38.930> dhaka<00:13:39.259> files<00:13:39.529> and<00:13:39.800> bash 00:13:39.910 --> 00:13:39.920 align:start position:0% bit and it's dhaka files and bash 00:13:39.920 --> 00:13:43.420 align:start position:0% bit and it's dhaka files and bash scripts<00:13:40.370> to<00:13:40.670> cross<00:13:41.060> build<00:13:41.680> cpp<00:13:42.680> aetherium<00:13:43.190> to 00:13:43.420 --> 00:13:43.430 align:start position:0% scripts to cross build cpp aetherium to 00:13:43.430 --> 00:13:46.629 align:start position:0% scripts to cross build cpp aetherium to to<00:13:43.850> arm<00:13:44.029> linux<00:13:44.360> and<00:13:45.190> you<00:13:46.190> know<00:13:46.310> we<00:13:46.399> have<00:13:46.550> the 00:13:46.629 --> 00:13:46.639 align:start position:0% to arm linux and you know we have the 00:13:46.639 --> 00:13:48.670 align:start position:0% to arm linux and you know we have the first<00:13:46.670> successful<00:13:47.209> cross<00:13:48.050> built<00:13:48.259> binary<00:13:48.620> is 00:13:48.670 --> 00:13:48.680 align:start position:0% first successful cross built binary is 00:13:48.680 --> 00:13:50.079 align:start position:0% first successful cross built binary is in<00:13:48.769> november<00:13:49.279> of<00:13:49.310> last<00:13:49.399> year<00:13:49.850> it's<00:13:49.970> been 00:13:50.079 --> 00:13:50.089 align:start position:0% in november of last year it's been 00:13:50.089 --> 00:13:52.449 align:start position:0% in november of last year it's been largely<00:13:50.540> stalled<00:13:50.990> since<00:13:51.290> then<00:13:51.560> and 00:13:52.449 --> 00:13:52.459 align:start position:0% largely stalled since then and 00:13:52.459 --> 00:13:54.550 align:start position:0% largely stalled since then and especially<00:13:52.880> since<00:13:53.089> february<00:13:53.509> when<00:13:54.230> i<00:13:54.259> joined 00:13:54.550 --> 00:13:54.560 align:start position:0% especially since february when i joined 00:13:54.560 --> 00:13:55.960 align:start position:0% especially since february when i joined the<00:13:54.649> foundation<00:13:54.769> and<00:13:55.310> then<00:13:55.430> i've<00:13:55.610> been<00:13:55.790> just 00:13:55.960 --> 00:13:55.970 align:start position:0% the foundation and then i've been just 00:13:55.970 --> 00:13:57.850 align:start position:0% the foundation and then i've been just working<00:13:56.149> for<00:13:56.660> the<00:13:56.750> foundation<00:13:57.199> on<00:13:57.290> foundation 00:13:57.850 --> 00:13:57.860 align:start position:0% working for the foundation on foundation 00:13:57.860 --> 00:14:05.470 align:start position:0% working for the foundation on foundation things<00:13:58.040> not<00:13:58.910> on<00:13:59.029> my<00:13:59.180> own<00:13:59.300> project<00:13:59.810> here<00:14:04.480> but 00:14:05.470 --> 00:14:05.480 align:start position:0% things not on my own project here but 00:14:05.480 --> 00:14:08.079 align:start position:0% things not on my own project here but very<00:14:05.810> soon<00:14:06.050> I<00:14:06.230> will<00:14:06.500> be<00:14:06.620> starting<00:14:07.339> on<00:14:07.579> my 00:14:08.079 --> 00:14:08.089 align:start position:0% very soon I will be starting on my 00:14:08.089 --> 00:14:10.809 align:start position:0% very soon I will be starting on my client<00:14:08.509> implementation<00:14:09.199> for<00:14:09.290> C++<00:14:09.860> I<00:14:10.339> did 00:14:10.809 --> 00:14:10.819 align:start position:0% client implementation for C++ I did 00:14:10.819 --> 00:14:13.120 align:start position:0% client implementation for C++ I did receive<00:14:11.209> a<00:14:11.480> grant<00:14:12.139> for<00:14:12.290> that<00:14:12.350> which<00:14:12.889> I'm<00:14:13.069> very 00:14:13.120 --> 00:14:13.130 align:start position:0% receive a grant for that which I'm very 00:14:13.130 --> 00:14:14.800 align:start position:0% receive a grant for that which I'm very grateful<00:14:13.459> and<00:14:13.759> I<00:14:13.819> hope<00:14:14.000> to<00:14:14.120> actually<00:14:14.389> do<00:14:14.630> some 00:14:14.800 --> 00:14:14.810 align:start position:0% grateful and I hope to actually do some 00:14:14.810 --> 00:14:20.650 align:start position:0% grateful and I hope to actually do some work<00:14:14.839> on<00:14:15.110> that<00:14:15.259> soon<00:14:17.889> so<00:14:19.269> number<00:14:20.269> of<00:14:20.300> devices 00:14:20.650 --> 00:14:20.660 align:start position:0% work on that soon so number of devices 00:14:20.660 --> 00:14:24.280 align:start position:0% work on that soon so number of devices have<00:14:21.019> had<00:14:21.199> success<00:14:22.160> for<00:14:22.399> this<00:14:22.519> already 00:14:24.280 --> 00:14:24.290 align:start position:0% have had success for this already 00:14:24.290 --> 00:14:27.280 align:start position:0% have had success for this already Yolo<00:14:24.800> phone<00:14:25.069> running<00:14:25.310> sailfish<00:14:25.790> OS<00:14:26.259> also<00:14:27.259> a 00:14:27.280 --> 00:14:27.290 align:start position:0% Yolo phone running sailfish OS also a 00:14:27.290 --> 00:14:31.990 align:start position:0% Yolo phone running sailfish OS also a bun<00:14:27.560> two<00:14:27.709> phone<00:14:28.420> a<00:14:29.649> goodly<00:14:30.649> variety<00:14:31.250> of<00:14:31.279> single 00:14:31.990 --> 00:14:32.000 align:start position:0% bun two phone a goodly variety of single 00:14:32.000 --> 00:14:36.819 align:start position:0% bun two phone a goodly variety of single board<00:14:32.209> computers<00:14:32.779> and<00:14:35.019> I'm<00:14:36.019> targeting 00:14:36.819 --> 00:14:36.829 align:start position:0% board computers and I'm targeting 00:14:36.829 --> 00:14:40.240 align:start position:0% board computers and I'm targeting further<00:14:37.720> SBC's<00:14:38.720> and<00:14:39.079> Tizen<00:14:39.500> and<00:14:39.649> Android<00:14:39.980> and 00:14:40.240 --> 00:14:40.250 align:start position:0% further SBC's and Tizen and Android and 00:14:40.250 --> 00:14:44.170 align:start position:0% further SBC's and Tizen and Android and iOS<00:14:41.439> very<00:14:42.439> low<00:14:42.649> demand<00:14:43.009> really<00:14:43.220> for<00:14:43.550> for<00:14:43.850> x86 00:14:44.170 --> 00:14:44.180 align:start position:0% iOS very low demand really for for x86 00:14:44.180 --> 00:14:49.829 align:start position:0% iOS very low demand really for for x86 for<00:14:44.600> Intel<00:14:44.899> arm<00:14:45.889> is<00:14:46.220> where<00:14:46.459> it's<00:14:46.639> at 00:14:49.829 --> 00:14:49.839 align:start position:0% 00:14:49.839 --> 00:14:55.809 align:start position:0% looking<00:14:50.839> beyond<00:14:51.110> my<00:14:51.319> work<00:14:53.019> peter<00:14:54.019> has<00:14:54.380> had<00:14:54.819> go 00:14:55.809 --> 00:14:55.819 align:start position:0% looking beyond my work peter has had go 00:14:55.819 --> 00:14:57.999 align:start position:0% looking beyond my work peter has had go aetherium<00:14:56.329> cross<00:14:56.540> builds<00:14:56.839> working<00:14:57.259> for<00:14:57.980> a 00:14:57.999 --> 00:14:58.009 align:start position:0% aetherium cross builds working for a 00:14:58.009 --> 00:15:02.280 align:start position:0% aetherium cross builds working for a goodly<00:14:58.189> amount<00:14:58.310> of<00:14:58.670> time<00:14:59.439> there<00:15:00.439> on<00:15:00.769> on<00:15:01.189> arm 00:15:02.280 --> 00:15:02.290 align:start position:0% goodly amount of time there on on arm 00:15:02.290 --> 00:15:05.860 align:start position:0% goodly amount of time there on on arm arm<00:15:03.290> 64<00:15:03.860> and<00:15:04.100> more<00:15:04.279> recently<00:15:04.639> on<00:15:04.699> mips<00:15:05.029> as<00:15:05.389> well 00:15:05.860 --> 00:15:05.870 align:start position:0% arm 64 and more recently on mips as well 00:15:05.870 --> 00:15:11.780 align:start position:0% arm 64 and more recently on mips as well interestingly 00:15:11.780 --> 00:15:11.790 align:start position:0% 00:15:11.790 --> 00:15:14.490 align:start position:0% the<00:15:12.790> light<00:15:12.940> client<00:15:13.330> work<00:15:13.480> so<00:15:14.020> Zolt 00:15:14.490 --> 00:15:14.500 align:start position:0% the light client work so Zolt 00:15:14.500 --> 00:15:17.370 align:start position:0% the light client work so Zolt we'll<00:15:15.250> be<00:15:15.370> presenting<00:15:15.760> on<00:15:16.450> his<00:15:16.810> progress<00:15:17.170> on 00:15:17.370 --> 00:15:17.380 align:start position:0% we'll be presenting on his progress on 00:15:17.380 --> 00:15:21.750 align:start position:0% we'll be presenting on his progress on light<00:15:17.590> client<00:15:17.920> as<00:15:18.040> well<00:15:18.540> and<00:15:20.310> the<00:15:21.310> stats<00:15:21.610> here 00:15:21.750 --> 00:15:21.760 align:start position:0% light client as well and the stats here 00:15:21.760 --> 00:15:27.180 align:start position:0% light client as well and the stats here are<00:15:22.300> from<00:15:23.080> John<00:15:24.040> Garrett's<00:15:25.350> on<00:15:26.350> what<00:15:26.890> he<00:15:27.160> is 00:15:27.180 --> 00:15:27.190 align:start position:0% are from John Garrett's on what he is 00:15:27.190 --> 00:15:29.760 align:start position:0% are from John Garrett's on what he is seeing<00:15:27.580> of<00:15:27.940> that<00:15:28.029> le<00:15:28.750> s<00:15:28.960> branch<00:15:29.260> running<00:15:29.620> on<00:15:29.710> a 00:15:29.760 --> 00:15:29.770 align:start position:0% seeing of that le s branch running on a 00:15:29.770 --> 00:15:33.150 align:start position:0% seeing of that le s branch running on a Raspberry<00:15:30.130> Pi<00:15:30.160> 3<00:15:30.550> so<00:15:31.420> so<00:15:31.900> the<00:15:31.990> binary<00:15:32.380> 25<00:15:32.830> mag 00:15:33.150 --> 00:15:33.160 align:start position:0% Raspberry Pi 3 so so the binary 25 mag 00:15:33.160 --> 00:15:36.750 align:start position:0% Raspberry Pi 3 so so the binary 25 mag the<00:15:34.120> chain<00:15:34.390> data<00:15:34.600> only<00:15:35.080> coming<00:15:35.290> in<00:15:35.440> at<00:15:35.760> 50/50 00:15:36.750 --> 00:15:36.760 align:start position:0% the chain data only coming in at 50/50 00:15:36.760 --> 00:15:40.740 align:start position:0% the chain data only coming in at 50/50 mag<00:15:36.960> only<00:15:37.960> using<00:15:38.290> 12<00:15:38.860> percent<00:15:39.160> of<00:15:39.279> CPU<00:15:39.790> and<00:15:40.120> the 00:15:40.740 --> 00:15:40.750 align:start position:0% mag only using 12 percent of CPU and the 00:15:40.750 --> 00:15:44.400 align:start position:0% mag only using 12 percent of CPU and the high<00:15:40.900> high<00:15:41.560> watermark<00:15:42.070> on<00:15:42.190> the<00:15:42.279> RAM<00:15:42.430> of<00:15:42.810> 162<00:15:43.810> so 00:15:44.400 --> 00:15:44.410 align:start position:0% high high watermark on the RAM of 162 so 00:15:44.410 --> 00:15:46.920 align:start position:0% high high watermark on the RAM of 162 so I<00:15:44.440> mean<00:15:44.560> these<00:15:44.740> figures<00:15:45.100> are<00:15:45.130> very<00:15:45.490> much<00:15:45.930> very 00:15:46.920 --> 00:15:46.930 align:start position:0% I mean these figures are very much very 00:15:46.930 --> 00:15:52.880 align:start position:0% I mean these figures are very much very very<00:15:47.020> doable<00:15:47.410> on<00:15:48.240> a<00:15:49.240> lot<00:15:50.050> of<00:15:50.080> these<00:15:50.260> devices 00:15:52.880 --> 00:15:52.890 align:start position:0% 00:15:52.890 --> 00:15:55.470 align:start position:0% nine<00:15:53.890> nine<00:15:54.460> minutes<00:15:54.820> therefore<00:15:55.180> ahead<00:15:55.360> of 00:15:55.470 --> 00:15:55.480 align:start position:0% nine nine minutes therefore ahead of 00:15:55.480 --> 00:15:59.550 align:start position:0% nine nine minutes therefore ahead of sync<00:15:57.120> the<00:15:58.120> the<00:15:58.480> smallest<00:15:58.839> device<00:15:59.200> that<00:15:59.470> I'm 00:15:59.550 --> 00:15:59.560 align:start position:0% sync the the smallest device that I'm 00:15:59.560 --> 00:16:02.370 align:start position:0% sync the the smallest device that I'm aware<00:15:59.830> of<00:15:59.890> that<00:16:00.100> we've<00:16:00.460> got<00:16:01.080> etherium<00:16:02.080> running 00:16:02.370 --> 00:16:02.380 align:start position:0% aware of that we've got etherium running 00:16:02.380 --> 00:16:05.040 align:start position:0% aware of that we've got etherium running on<00:16:02.500> so<00:16:02.710> far<00:16:02.980> as<00:16:03.160> a<00:16:03.190> Raspberry<00:16:03.670> Pi<00:16:03.700> a<00:16:03.880> which<00:16:04.870> is<00:16:05.020> a 00:16:05.040 --> 00:16:05.050 align:start position:0% on so far as a Raspberry Pi a which is a 00:16:05.050 --> 00:16:08.040 align:start position:0% on so far as a Raspberry Pi a which is a very<00:16:05.380> very<00:16:05.860> weedy<00:16:06.160> device<00:16:06.550> and<00:16:07.029> that<00:16:07.630> was<00:16:07.779> full 00:16:08.040 --> 00:16:08.050 align:start position:0% very very weedy device and that was full 00:16:08.050 --> 00:16:10.200 align:start position:0% very very weedy device and that was full clients<00:16:08.500> as<00:16:08.620> well<00:16:08.770> that<00:16:09.190> was<00:16:09.339> prior<00:16:09.640> to<00:16:09.670> any<00:16:10.060> of 00:16:10.200 --> 00:16:10.210 align:start position:0% clients as well that was prior to any of 00:16:10.210 --> 00:16:13.260 align:start position:0% clients as well that was prior to any of this<00:16:10.450> le<00:16:11.140> s<00:16:11.260> work<00:16:11.500> so<00:16:12.400> it's<00:16:12.790> quite<00:16:13.029> conceivable 00:16:13.260 --> 00:16:13.270 align:start position:0% this le s work so it's quite conceivable 00:16:13.270 --> 00:16:16.590 align:start position:0% this le s work so it's quite conceivable that<00:16:13.870> we<00:16:14.020> can<00:16:14.200> that<00:16:15.130> we<00:16:15.160> can<00:16:15.339> have<00:16:15.600> etherium 00:16:16.590 --> 00:16:16.600 align:start position:0% that we can that we can have etherium 00:16:16.600 --> 00:16:18.450 align:start position:0% that we can that we can have etherium running<00:16:16.900> on<00:16:16.990> something<00:16:17.410> even<00:16:17.800> we<00:16:17.980> do<00:16:18.040> than<00:16:18.339> or 00:16:18.450 --> 00:16:18.460 align:start position:0% running on something even we do than or 00:16:18.460 --> 00:16:22.560 align:start position:0% running on something even we do than or asbury<00:16:18.760> pi<00:16:18.970> a<00:16:19.740> and<00:16:20.760> getting<00:16:21.760> down<00:16:21.910> to<00:16:22.210> some 00:16:22.560 --> 00:16:22.570 align:start position:0% asbury pi a and getting down to some 00:16:22.570 --> 00:16:25.500 align:start position:0% asbury pi a and getting down to some really<00:16:23.440> really<00:16:23.710> very<00:16:23.860> minimal<00:16:24.339> devices<00:16:25.330> and 00:16:25.500 --> 00:16:25.510 align:start position:0% really really very minimal devices and 00:16:25.510 --> 00:16:28.230 align:start position:0% really really very minimal devices and whisper<00:16:26.320> you<00:16:27.040> know<00:16:27.160> so<00:16:27.370> whisper<00:16:27.760> development 00:16:28.230 --> 00:16:28.240 align:start position:0% whisper you know so whisper development 00:16:28.240 --> 00:16:31.950 align:start position:0% whisper you know so whisper development has<00:16:28.360> restarted<00:16:29.110> quite<00:16:29.589> recently<00:16:30.480> that's<00:16:31.480> also 00:16:31.950 --> 00:16:31.960 align:start position:0% has restarted quite recently that's also 00:16:31.960 --> 00:16:33.150 align:start position:0% has restarted quite recently that's also something<00:16:32.200> which<00:16:32.500> is<00:16:32.680> going<00:16:32.800> to<00:16:32.890> be<00:16:32.980> very 00:16:33.150 --> 00:16:33.160 align:start position:0% something which is going to be very 00:16:33.160 --> 00:16:36.470 align:start position:0% something which is going to be very applicable<00:16:33.700> for<00:16:34.210> these<00:16:34.300> kind<00:16:34.540> of<00:16:34.600> devices<00:16:35.370> and 00:16:36.470 --> 00:16:36.480 align:start position:0% applicable for these kind of devices and 00:16:36.480 --> 00:16:39.510 align:start position:0% applicable for these kind of devices and also<00:16:37.480> Raiden<00:16:38.290> I<00:16:38.440> haven't<00:16:38.710> got<00:16:38.860> on<00:16:38.980> slides<00:16:39.280> here 00:16:39.510 --> 00:16:39.520 align:start position:0% also Raiden I haven't got on slides here 00:16:39.520 --> 00:16:41.700 align:start position:0% also Raiden I haven't got on slides here I'd<00:16:39.910> kind<00:16:40.180> of<00:16:40.240> forgotten<00:16:40.300> but<00:16:41.020> Raiden<00:16:41.500> is 00:16:41.700 --> 00:16:41.710 align:start position:0% I'd kind of forgotten but Raiden is 00:16:41.710 --> 00:16:43.710 align:start position:0% I'd kind of forgotten but Raiden is gonna<00:16:41.980> be<00:16:42.130> very<00:16:42.700> very<00:16:42.910> applicable<00:16:43.240> to<00:16:43.270> these 00:16:43.710 --> 00:16:43.720 align:start position:0% gonna be very very applicable to these 00:16:43.720 --> 00:16:48.240 align:start position:0% gonna be very very applicable to these kind<00:16:43.960> of<00:16:43.990> devices<00:16:45.780> so<00:16:46.780> you<00:16:47.500> know<00:16:47.620> what<00:16:47.860> are<00:16:48.040> the 00:16:48.240 --> 00:16:48.250 align:start position:0% kind of devices so you know what are the 00:16:48.250 --> 00:16:50.130 align:start position:0% kind of devices so you know what are the ultimate<00:16:48.460> constraints<00:16:49.180> on<00:16:49.330> on<00:16:49.720> running 00:16:50.130 --> 00:16:50.140 align:start position:0% ultimate constraints on on running 00:16:50.140 --> 00:16:54.990 align:start position:0% ultimate constraints on on running aetherium<00:16:50.620> on<00:16:50.740> on<00:16:51.430> limited<00:16:51.910> hardware<00:16:53.820> so<00:16:54.820> yeah 00:16:54.990 --> 00:16:55.000 align:start position:0% aetherium on on limited hardware so yeah 00:16:55.000 --> 00:16:56.400 align:start position:0% aetherium on on limited hardware so yeah I<00:16:55.030> mean<00:16:55.180> the<00:16:55.300> specs<00:16:55.600> there<00:16:55.839> on<00:16:55.959> the<00:16:56.080> Raspberry 00:16:56.400 --> 00:16:56.410 align:start position:0% I mean the specs there on the Raspberry 00:16:56.410 --> 00:16:59.070 align:start position:0% I mean the specs there on the Raspberry Pi<00:16:56.470> model<00:16:56.800> a<00:16:57.040> you<00:16:57.310> know<00:16:57.940> it's<00:16:58.420> a<00:16:58.540> single<00:16:58.870> core 00:16:59.070 --> 00:16:59.080 align:start position:0% Pi model a you know it's a single core 00:16:59.080 --> 00:17:04.610 align:start position:0% Pi model a you know it's a single core only<00:16:59.589> 256<00:17:00.250> mega<00:17:00.550> memory<00:17:02.130> 700<00:17:03.130> megahertz<00:17:03.400> that 00:17:04.610 --> 00:17:04.620 align:start position:0% only 256 mega memory 700 megahertz that 00:17:04.620 --> 00:17:11.130 align:start position:0% only 256 mega memory 700 megahertz that device<00:17:06.900> can<00:17:07.900> run<00:17:08.620> full<00:17:08.890> client<00:17:09.810> the<00:17:10.810> problem 00:17:11.130 --> 00:17:11.140 align:start position:0% device can run full client the problem 00:17:11.140 --> 00:17:13.050 align:start position:0% device can run full client the problem is<00:17:11.290> that<00:17:11.560> the<00:17:11.709> you<00:17:12.160> know<00:17:12.250> the<00:17:12.400> full<00:17:12.610> sync<00:17:12.910> on 00:17:13.050 --> 00:17:13.060 align:start position:0% is that the you know the full sync on 00:17:13.060 --> 00:17:15.600 align:start position:0% is that the you know the full sync on that<00:17:13.270> it<00:17:13.390> can<00:17:13.540> barely<00:17:13.900> keep<00:17:14.050> pace<00:17:14.350> that<00:17:15.339> no 00:17:15.600 --> 00:17:15.610 align:start position:0% that it can barely keep pace that no 00:17:15.610 --> 00:17:17.189 align:start position:0% that it can barely keep pace that no longer<00:17:15.910> a<00:17:15.939> problem<00:17:16.179> though<00:17:16.540> if<00:17:16.839> you're 00:17:17.189 --> 00:17:17.199 align:start position:0% longer a problem though if you're 00:17:17.199 --> 00:17:20.730 align:start position:0% longer a problem though if you're running<00:17:17.620> like<00:17:17.860> client<00:17:19.380> so<00:17:20.380> I<00:17:20.410> mean<00:17:20.560> you<00:17:20.709> know 00:17:20.730 --> 00:17:20.740 align:start position:0% running like client so I mean you know 00:17:20.740 --> 00:17:22.470 align:start position:0% running like client so I mean you know what<00:17:21.010> are<00:17:21.160> the<00:17:21.310> ultimate<00:17:21.490> constraints<00:17:22.209> well 00:17:22.470 --> 00:17:22.480 align:start position:0% what are the ultimate constraints well 00:17:22.480 --> 00:17:24.270 align:start position:0% what are the ultimate constraints well the<00:17:22.870> CPU<00:17:23.319> is<00:17:23.380> got<00:17:23.530> to<00:17:23.560> be<00:17:23.650> able<00:17:23.770> to 00:17:24.270 --> 00:17:24.280 align:start position:0% the CPU is got to be able to 00:17:24.280 --> 00:17:27.660 align:start position:0% the CPU is got to be able to execute<00:17:24.970> the<00:17:25.150> the<00:17:25.570> VM<00:17:25.900> fast<00:17:26.170> enough<00:17:26.550> you<00:17:27.550> know 00:17:27.660 --> 00:17:27.670 align:start position:0% execute the the VM fast enough you know 00:17:27.670 --> 00:17:29.550 align:start position:0% execute the the VM fast enough you know this<00:17:27.850> kind<00:17:28.150> of<00:17:28.180> collaborative<00:17:28.480> device<00:17:28.870> can<00:17:29.410> do 00:17:29.550 --> 00:17:29.560 align:start position:0% this kind of collaborative device can do 00:17:29.560 --> 00:17:34.160 align:start position:0% this kind of collaborative device can do that<00:17:31.410> you've<00:17:32.410> got<00:17:32.560> to<00:17:32.620> have<00:17:32.650> enough<00:17:32.920> memory 00:17:34.160 --> 00:17:34.170 align:start position:0% that you've got to have enough memory 00:17:34.170 --> 00:17:36.960 align:start position:0% that you've got to have enough memory I'd<00:17:35.170> imagine<00:17:35.590> that's<00:17:35.710> gonna<00:17:35.950> stay<00:17:36.190> around<00:17:36.550> the 00:17:36.960 --> 00:17:36.970 align:start position:0% I'd imagine that's gonna stay around the 00:17:36.970 --> 00:17:38.700 align:start position:0% I'd imagine that's gonna stay around the same<00:17:37.180> even<00:17:37.600> with<00:17:37.720> like<00:17:37.930> client<00:17:38.320> even<00:17:38.470> through 00:17:38.700 --> 00:17:38.710 align:start position:0% same even with like client even through 00:17:38.710 --> 00:17:41.550 align:start position:0% same even with like client even through Casper<00:17:39.100> as<00:17:39.220> well<00:17:39.400> and<00:17:40.200> you<00:17:41.200> need<00:17:41.410> to<00:17:41.500> have 00:17:41.550 --> 00:17:41.560 align:start position:0% Casper as well and you need to have 00:17:41.560 --> 00:17:43.680 align:start position:0% Casper as well and you need to have enough<00:17:41.800> storage<00:17:42.130> for<00:17:42.340> blocks<00:17:42.730> though<00:17:43.510> the 00:17:43.680 --> 00:17:43.690 align:start position:0% enough storage for blocks though the 00:17:43.690 --> 00:17:47.370 align:start position:0% enough storage for blocks though the storage<00:17:45.480> bottleneck<00:17:46.480> there<00:17:46.660> really<00:17:46.930> goes 00:17:47.370 --> 00:17:47.380 align:start position:0% storage bottleneck there really goes 00:17:47.380 --> 00:17:49.820 align:start position:0% storage bottleneck there really goes away<00:17:47.530> quite<00:17:47.920> a<00:17:47.950> lot<00:17:48.160> with<00:17:48.400> with<00:17:48.880> like<00:17:49.090> client 00:17:49.820 --> 00:17:49.830 align:start position:0% away quite a lot with with like client 00:17:49.830 --> 00:17:52.140 align:start position:0% away quite a lot with with like client when<00:17:50.830> you're<00:17:50.980> running<00:17:51.220> a<00:17:51.280> full<00:17:51.520> node<00:17:51.820> and 00:17:52.140 --> 00:17:52.150 align:start position:0% when you're running a full node and 00:17:52.150 --> 00:17:53.940 align:start position:0% when you're running a full node and you're<00:17:52.240> having<00:17:52.360> to<00:17:52.540> sync<00:17:52.780> from<00:17:53.050> from<00:17:53.830> the 00:17:53.940 --> 00:17:53.950 align:start position:0% you're having to sync from from the 00:17:53.950 --> 00:17:55.830 align:start position:0% you're having to sync from from the start<00:17:54.310> the<00:17:54.640> you<00:17:54.910> know<00:17:55.030> the<00:17:55.150> performance<00:17:55.690> can 00:17:55.830 --> 00:17:55.840 align:start position:0% start the you know the performance can 00:17:55.840 --> 00:17:58.050 align:start position:0% start the you know the performance can really<00:17:56.080> matter<00:17:56.310> you<00:17:57.310> know<00:17:57.430> having<00:17:57.670> an<00:17:57.760> SSD 00:17:58.050 --> 00:17:58.060 align:start position:0% really matter you know having an SSD 00:17:58.060 --> 00:17:59.870 align:start position:0% really matter you know having an SSD makes<00:17:58.450> a<00:17:58.600> huge<00:17:58.840> difference 00:17:59.870 --> 00:17:59.880 align:start position:0% makes a huge difference 00:17:59.880 --> 00:18:02.340 align:start position:0% makes a huge difference but<00:18:00.880> that's<00:18:01.060> only<00:18:01.240> really<00:18:01.840> relevant<00:18:02.050> if 00:18:02.340 --> 00:18:02.350 align:start position:0% but that's only really relevant if 00:18:02.350 --> 00:18:03.990 align:start position:0% but that's only really relevant if you're<00:18:02.500> doing<00:18:02.650> a<00:18:02.740> load<00:18:02.920> of<00:18:03.040> work<00:18:03.160> and<00:18:03.520> the<00:18:03.880> aim 00:18:03.990 --> 00:18:04.000 align:start position:0% you're doing a load of work and the aim 00:18:04.000 --> 00:18:07.710 align:start position:0% you're doing a load of work and the aim is<00:18:04.180> not<00:18:04.420> to<00:18:04.840> do<00:18:05.050> a<00:18:05.080> load<00:18:05.290> of<00:18:05.320> work<00:18:05.470> anymore<00:18:06.720> and 00:18:07.710 --> 00:18:07.720 align:start position:0% is not to do a load of work anymore and 00:18:07.720 --> 00:18:09.540 align:start position:0% is not to do a load of work anymore and the<00:18:08.410> network<00:18:08.680> connections<00:18:09.160> got<00:18:09.280> to<00:18:09.400> be<00:18:09.460> good 00:18:09.540 --> 00:18:09.550 align:start position:0% the network connections got to be good 00:18:09.550 --> 00:18:14.310 align:start position:0% the network connections got to be good enough<00:18:11.340> so<00:18:12.340> yeah<00:18:12.600> we're<00:18:13.600> gonna<00:18:13.690> see<00:18:13.990> aetherium 00:18:14.310 --> 00:18:14.320 align:start position:0% enough so yeah we're gonna see aetherium 00:18:14.320 --> 00:18:16.680 align:start position:0% enough so yeah we're gonna see aetherium on<00:18:14.590> a<00:18:14.620> lot<00:18:14.800> of<00:18:14.860> devices<00:18:15.100> and<00:18:15.550> they<00:18:16.240> are<00:18:16.450> going 00:18:16.680 --> 00:18:16.690 align:start position:0% on a lot of devices and they are going 00:18:16.690 --> 00:18:21.090 align:start position:0% on a lot of devices and they are going to<00:18:16.780> be<00:18:17.010> very<00:18:18.010> very<00:18:18.220> weak<00:18:19.320> devices<00:18:20.320> and<00:18:20.710> they'll 00:18:21.090 --> 00:18:21.100 align:start position:0% to be very very weak devices and they'll 00:18:21.100 --> 00:18:23.870 align:start position:0% to be very very weak devices and they'll be<00:18:21.250> able<00:18:21.400> to<00:18:21.490> cope<00:18:21.700> just<00:18:21.730> fine<00:18:22.650> there<00:18:23.650> are 00:18:23.870 --> 00:18:23.880 align:start position:0% be able to cope just fine there are 00:18:23.880 --> 00:18:27.600 align:start position:0% be able to cope just fine there are multiple<00:18:24.880> threats<00:18:25.240> of<00:18:25.780> work<00:18:26.770> going<00:18:27.040> on<00:18:27.280> to 00:18:27.600 --> 00:18:27.610 align:start position:0% multiple threats of work going on to 00:18:27.610 --> 00:18:33.330 align:start position:0% multiple threats of work going on to reduce<00:18:28.060> the<00:18:28.720> resource<00:18:29.470> needs<00:18:31.830> so<00:18:32.830> you<00:18:32.890> know<00:18:33.160> we 00:18:33.330 --> 00:18:33.340 align:start position:0% reduce the resource needs so you know we 00:18:33.340 --> 00:18:36.720 align:start position:0% reduce the resource needs so you know we we<00:18:33.880> can<00:18:34.030> cope<00:18:34.300> now<00:18:34.600> and<00:18:35.340> the<00:18:36.340> demands<00:18:36.670> are 00:18:36.720 --> 00:18:36.730 align:start position:0% we can cope now and the demands are 00:18:36.730 --> 00:18:38.430 align:start position:0% we can cope now and the demands are gonna<00:18:36.820> get<00:18:37.030> a<00:18:37.060> lot<00:18:37.330> lower<00:18:37.510> so<00:18:37.990> it's<00:18:38.140> only<00:18:38.260> gonna 00:18:38.430 --> 00:18:38.440 align:start position:0% gonna get a lot lower so it's only gonna 00:18:38.440 --> 00:18:40.980 align:start position:0% gonna get a lot lower so it's only gonna get<00:18:38.620> better<00:18:38.800> thank<00:18:39.700> you<00:18:39.820> so<00:18:40.090> much<00:18:40.300> Bob<00:18:40.600> and 00:18:40.980 --> 00:18:40.990 align:start position:0% get better thank you so much Bob and 00:18:40.990 --> 00:18:47.820 align:start position:0% get better thank you so much Bob and there<00:18:41.140> we<00:18:41.230> go<00:18:41.410> yeah<00:18:44.640> we'll<00:18:45.640> be<00:18:45.850> a<00:18:46.120> delight<00:18:47.080> with 00:18:47.820 --> 00:18:47.830 align:start position:0% there we go yeah we'll be a delight with 00:18:47.830 --> 00:18:50.310 align:start position:0% there we go yeah we'll be a delight with blockchain