WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:16.740 align:start position:0% [Music] 00:00:16.740 --> 00:00:16.750 align:start position:0% 00:00:16.750 --> 00:00:22.480 align:start position:0% hello<00:00:17.750> hello<00:00:19.240> yeah<00:00:20.710> very<00:00:21.710> good<00:00:21.920> afternoon<00:00:22.160> one 00:00:22.480 --> 00:00:22.490 align:start position:0% hello hello yeah very good afternoon one 00:00:22.490 --> 00:00:27.850 align:start position:0% hello hello yeah very good afternoon one my<00:00:23.360> name<00:00:23.540> is<00:00:24.430> matthew<00:00:25.430> tan<00:00:25.610> and<00:00:25.880> I'm<00:00:26.270> the<00:00:26.860> CEO 00:00:27.850 --> 00:00:27.860 align:start position:0% my name is matthew tan and I'm the CEO 00:00:27.860 --> 00:00:32.229 align:start position:0% my name is matthew tan and I'm the CEO and<00:00:28.340> lead<00:00:28.880> developer<00:00:29.210> at<00:00:29.720> ETS<00:00:30.680> Ken<00:00:30.830> so<00:00:31.670> welcome 00:00:32.229 --> 00:00:32.239 align:start position:0% and lead developer at ETS Ken so welcome 00:00:32.239 --> 00:00:34.630 align:start position:0% and lead developer at ETS Ken so welcome to<00:00:32.390> one<00:00:32.539> of<00:00:32.570> the<00:00:32.980> less<00:00:33.980> technical 00:00:34.630 --> 00:00:34.640 align:start position:0% to one of the less technical 00:00:34.640 --> 00:00:39.610 align:start position:0% to one of the less technical presentations<00:00:35.240> of<00:00:35.510> the<00:00:35.630> day<00:00:37.510> so<00:00:38.510> the<00:00:39.079> topic<00:00:39.530> of 00:00:39.610 --> 00:00:39.620 align:start position:0% presentations of the day so the topic of 00:00:39.620 --> 00:00:41.920 align:start position:0% presentations of the day so the topic of our<00:00:39.829> presentation<00:00:40.370> today<00:00:40.520> is<00:00:40.670> exploring<00:00:41.480> the 00:00:41.920 --> 00:00:41.930 align:start position:0% our presentation today is exploring the 00:00:41.930 --> 00:00:44.140 align:start position:0% our presentation today is exploring the theorem<00:00:42.380> blockchain<00:00:42.800> so<00:00:43.460> I<00:00:43.489> will<00:00:43.730> do<00:00:43.910> is<00:00:44.000> will 00:00:44.140 --> 00:00:44.150 align:start position:0% theorem blockchain so I will do is will 00:00:44.150 --> 00:00:47.260 align:start position:0% theorem blockchain so I will do is will first<00:00:44.450> begin<00:00:44.600> with<00:00:44.989> a<00:00:45.230> quick<00:00:46.100> overview<00:00:46.399> of<00:00:46.700> the 00:00:47.260 --> 00:00:47.270 align:start position:0% first begin with a quick overview of the 00:00:47.270 --> 00:00:49.360 align:start position:0% first begin with a quick overview of the blockchain<00:00:47.630> stats<00:00:48.020> and<00:00:48.470> then<00:00:48.770> share<00:00:49.130> your 00:00:49.360 --> 00:00:49.370 align:start position:0% blockchain stats and then share your 00:00:49.370 --> 00:00:51.819 align:start position:0% blockchain stats and then share your some<00:00:49.760> of<00:00:49.790> the<00:00:50.110> challenges<00:00:51.110> issues<00:00:51.320> that<00:00:51.710> we 00:00:51.819 --> 00:00:51.829 align:start position:0% some of the challenges issues that we 00:00:51.829 --> 00:00:54.340 align:start position:0% some of the challenges issues that we face<00:00:52.070> wobbling<00:00:52.880> and<00:00:53.050> infrastructure<00:00:54.050> level 00:00:54.340 --> 00:00:54.350 align:start position:0% face wobbling and infrastructure level 00:00:54.350 --> 00:00:56.950 align:start position:0% face wobbling and infrastructure level service<00:00:54.649> for<00:00:55.190> the<00:00:55.370> term<00:00:55.610> blockchain<00:00:56.030> and<00:00:56.239> they 00:00:56.950 --> 00:00:56.960 align:start position:0% service for the term blockchain and they 00:00:56.960 --> 00:00:59.290 align:start position:0% service for the term blockchain and they will<00:00:57.140> attempt<00:00:57.530> to<00:00:57.620> derive<00:00:57.950> the<00:00:58.280> theorem<00:00:59.059> used 00:00:59.290 --> 00:00:59.300 align:start position:0% will attempt to derive the theorem used 00:00:59.300 --> 00:01:04.299 align:start position:0% will attempt to derive the theorem used Upasana<00:00:59.870> using<00:01:00.680> Google<00:01:01.160> Analytics<00:01:01.610> data<00:01:03.309> so 00:01:04.299 --> 00:01:04.309 align:start position:0% Upasana using Google Analytics data so 00:01:04.309 --> 00:01:06.160 align:start position:0% Upasana using Google Analytics data so OB<00:01:04.729> before<00:01:05.089> for<00:01:05.239> the<00:01:05.329> accounting<00:01:05.720> I'd<00:01:05.840> like<00:01:05.990> to 00:01:06.160 --> 00:01:06.170 align:start position:0% OB before for the accounting I'd like to 00:01:06.170 --> 00:01:08.530 align:start position:0% OB before for the accounting I'd like to do<00:01:06.320> just<00:01:06.650> a<00:01:06.799> very<00:01:06.830> brief<00:01:07.400> introduction<00:01:08.030> of<00:01:08.360> who 00:01:08.530 --> 00:01:08.540 align:start position:0% do just a very brief introduction of who 00:01:08.540 --> 00:01:11.890 align:start position:0% do just a very brief introduction of who we<00:01:08.720> are<00:01:08.870> so<00:01:09.830> either<00:01:10.549> scan<00:01:10.880> is<00:01:11.030> a<00:01:11.240> block<00:01:11.570> power 00:01:11.890 --> 00:01:11.900 align:start position:0% we are so either scan is a block power 00:01:11.900 --> 00:01:14.289 align:start position:0% we are so either scan is a block power and<00:01:12.229> search<00:01:12.979> engine<00:01:13.220> for<00:01:13.400> the<00:01:13.490> ETM<00:01:13.909> blockchain 00:01:14.289 --> 00:01:14.299 align:start position:0% and search engine for the ETM blockchain 00:01:14.299 --> 00:01:18.609 align:start position:0% and search engine for the ETM blockchain and<00:01:15.010> it<00:01:16.010> just<00:01:16.370> came<00:01:16.490> we<00:01:16.640> have<00:01:16.790> up<00:01:17.570> to<00:01:17.960> 1<00:01:18.440> billion 00:01:18.609 --> 00:01:18.619 align:start position:0% and it just came we have up to 1 billion 00:01:18.619 --> 00:01:22.870 align:start position:0% and it just came we have up to 1 billion monthly<00:01:18.920> active<00:01:19.100> users<00:01:19.310> we<00:01:21.190> receive<00:01:22.190> 18 00:01:22.870 --> 00:01:22.880 align:start position:0% monthly active users we receive 18 00:01:22.880 --> 00:01:24.609 align:start position:0% monthly active users we receive 18 million<00:01:23.090> pages<00:01:23.270> per<00:01:23.479> month<00:01:23.659> and<00:01:23.960> we<00:01:24.170> serve 00:01:24.609 --> 00:01:24.619 align:start position:0% million pages per month and we serve 00:01:24.619 --> 00:01:27.039 align:start position:0% million pages per month and we serve over<00:01:24.860> nine<00:01:25.310> billion<00:01:25.610> API<00:01:26.000> calls<00:01:26.360> every<00:01:26.600> month 00:01:27.039 --> 00:01:27.049 align:start position:0% over nine billion API calls every month 00:01:27.049 --> 00:01:29.560 align:start position:0% over nine billion API calls every month so<00:01:27.619> either<00:01:28.460> scan<00:01:28.729> was<00:01:28.880> first<00:01:29.090> launched<00:01:29.360> in 00:01:29.560 --> 00:01:29.570 align:start position:0% so either scan was first launched in 00:01:29.570 --> 00:01:31.000 align:start position:0% so either scan was first launched in August<00:01:29.930> 2nd<00:01:30.320> 2015 00:01:31.000 --> 00:01:31.010 align:start position:0% August 2nd 2015 00:01:31.010 --> 00:01:33.609 align:start position:0% August 2nd 2015 and<00:01:31.340> today<00:01:31.820> were<00:01:31.970> one<00:01:32.150> of<00:01:32.330> the<00:01:32.540> oldest<00:01:33.290> and 00:01:33.609 --> 00:01:33.619 align:start position:0% and today were one of the oldest and 00:01:33.619 --> 00:01:36.520 align:start position:0% and today were one of the oldest and longest<00:01:34.600> externally<00:01:35.600> run<00:01:35.810> project<00:01:36.260> built 00:01:36.520 --> 00:01:36.530 align:start position:0% longest externally run project built 00:01:36.530 --> 00:01:38.880 align:start position:0% longest externally run project built around<00:01:36.950> and<00:01:37.369> for<00:01:38.000> the<00:01:38.150> Chilean<00:01:38.420> blockchain 00:01:38.880 --> 00:01:38.890 align:start position:0% around and for the Chilean blockchain 00:01:38.890 --> 00:01:42.070 align:start position:0% around and for the Chilean blockchain for<00:01:39.890> the<00:01:39.950> most<00:01:40.159> part<00:01:40.369> ETS<00:01:40.610> can<00:01:41.080> weave 00:01:42.070 --> 00:01:42.080 align:start position:0% for the most part ETS can weave 00:01:42.080 --> 00:01:44.170 align:start position:0% for the most part ETS can weave bootstrap<00:01:42.890> the<00:01:43.070> entire<00:01:43.460> project<00:01:43.670> is<00:01:43.909> my<00:01:44.030> own 00:01:44.170 --> 00:01:44.180 align:start position:0% bootstrap the entire project is my own 00:01:44.180 --> 00:01:48.219 align:start position:0% bootstrap the entire project is my own personal<00:01:44.689> funds<00:01:44.930> but<00:01:45.650> in<00:01:46.720> 2016<00:01:47.720> we<00:01:47.869> did<00:01:48.049> raise 00:01:48.219 --> 00:01:48.229 align:start position:0% personal funds but in 2016 we did raise 00:01:48.229 --> 00:01:51.100 align:start position:0% personal funds but in 2016 we did raise a<00:01:48.470> seed<00:01:49.400> round<00:01:49.580> from<00:01:50.000> leading<00:01:50.509> players<00:01:50.780> and 00:01:51.100 --> 00:01:51.110 align:start position:0% a seed round from leading players and 00:01:51.110 --> 00:01:55.570 align:start position:0% a seed round from leading players and blocked<00:01:51.290> investors<00:01:51.770> in<00:01:51.890> space<00:01:54.280> so<00:01:55.280> as<00:01:55.400> for<00:01:55.520> the 00:01:55.570 --> 00:01:55.580 align:start position:0% blocked investors in space so as for the 00:01:55.580 --> 00:01:57.819 align:start position:0% blocked investors in space so as for the team<00:01:55.820> at<00:01:56.060> one<00:01:56.210> money<00:01:56.390> we<00:01:57.020> are<00:01:57.229> a<00:01:57.259> team<00:01:57.619> of<00:01:57.650> five 00:01:57.819 --> 00:01:57.829 align:start position:0% team at one money we are a team of five 00:01:57.829 --> 00:02:02.370 align:start position:0% team at one money we are a team of five a<00:01:58.570> paste<00:01:59.570> out<00:01:59.720> of<00:01:59.930> Malaysia<00:02:00.200> and<00:02:00.850> all<00:02:01.850> the<00:02:02.030> next 00:02:02.370 --> 00:02:02.380 align:start position:0% a paste out of Malaysia and all the next 00:02:02.380 --> 00:02:04.390 align:start position:0% a paste out of Malaysia and all the next two<00:02:03.380> weeks<00:02:03.560> we<00:02:03.710> will<00:02:03.799> be<00:02:03.890> adding<00:02:04.009> in<00:02:04.130> a<00:02:04.220> more 00:02:04.390 --> 00:02:04.400 align:start position:0% two weeks we will be adding in a more 00:02:04.400 --> 00:02:06.819 align:start position:0% two weeks we will be adding in a more two<00:02:04.820> more<00:02:04.970> two<00:02:05.030> new<00:02:05.900> team<00:02:06.140> members<00:02:06.470> the<00:02:06.619> SIS 00:02:06.819 --> 00:02:06.829 align:start position:0% two more two new team members the SIS 00:02:06.829 --> 00:02:09.690 align:start position:0% two more two new team members the SIS with<00:02:07.159> support<00:02:07.939> and<00:02:08.119> software<00:02:08.780> engineering 00:02:09.690 --> 00:02:09.700 align:start position:0% with support and software engineering 00:02:09.700 --> 00:02:14.290 align:start position:0% with support and software engineering for<00:02:11.200> manpower<00:02:12.200> resource<00:02:12.920> allocation<00:02:13.489> as<00:02:14.000> far 00:02:14.290 --> 00:02:14.300 align:start position:0% for manpower resource allocation as far 00:02:14.300 --> 00:02:15.580 align:start position:0% for manpower resource allocation as far exploit<00:02:14.930> am<00:02:15.200> half 00:02:15.580 --> 00:02:15.590 align:start position:0% exploit am half 00:02:15.590 --> 00:02:17.259 align:start position:0% exploit am half our<00:02:15.680> resources<00:02:16.190> is<00:02:16.340> actually<00:02:16.640> dedicated 00:02:17.259 --> 00:02:17.269 align:start position:0% our resources is actually dedicated 00:02:17.269 --> 00:02:20.740 align:start position:0% our resources is actually dedicated towards<00:02:17.930> providing<00:02:18.550> community<00:02:19.550> support<00:02:19.910> and 00:02:20.740 --> 00:02:20.750 align:start position:0% towards providing community support and 00:02:20.750 --> 00:02:29.110 align:start position:0% towards providing community support and yet<00:02:21.379> half<00:02:21.620> on<00:02:21.879> software<00:02:22.879> engineering<00:02:28.120> alright 00:02:29.110 --> 00:02:29.120 align:start position:0% yet half on software engineering alright 00:02:29.120 --> 00:02:32.770 align:start position:0% yet half on software engineering alright so<00:02:29.300> for<00:02:29.540> a<00:02:29.720> quick<00:02:30.319> blockchain<00:02:31.099> or<00:02:31.250> used<00:02:31.459> s<00:02:31.780> so 00:02:32.770 --> 00:02:32.780 align:start position:0% so for a quick blockchain or used s so 00:02:32.780 --> 00:02:34.750 align:start position:0% so for a quick blockchain or used s so the<00:02:32.900> etherion<00:02:33.260> blockchain<00:02:33.680> as<00:02:33.950> all<00:02:34.250> as<00:02:34.519> some 00:02:34.750 --> 00:02:34.760 align:start position:0% the etherion blockchain as all as some 00:02:34.760 --> 00:02:36.910 align:start position:0% the etherion blockchain as all as some of<00:02:34.849> you<00:02:34.910> might<00:02:35.030> know<00:02:35.209> was<00:02:35.510> first<00:02:35.810> born<00:02:36.650> or 00:02:36.910 --> 00:02:36.920 align:start position:0% of you might know was first born or 00:02:36.920 --> 00:02:39.339 align:start position:0% of you might know was first born or kick-started<00:02:37.519> on<00:02:37.700> with<00:02:38.330> the<00:02:38.450> Genesis<00:02:38.840> block<00:02:38.989> 0 00:02:39.339 --> 00:02:39.349 align:start position:0% kick-started on with the Genesis block 0 00:02:39.349 --> 00:02:42.809 align:start position:0% kick-started on with the Genesis block 0 on<00:02:40.280> July<00:02:40.849> 30th<00:02:41.480> 2015 00:02:42.809 --> 00:02:42.819 align:start position:0% on July 30th 2015 00:02:42.819 --> 00:02:46.150 align:start position:0% on July 30th 2015 fast<00:02:43.819> forward<00:02:44.150> today<00:02:44.620> the<00:02:45.620> interim<00:02:46.010> block 00:02:46.150 --> 00:02:46.160 align:start position:0% fast forward today the interim block 00:02:46.160 --> 00:02:48.610 align:start position:0% fast forward today the interim block team<00:02:46.310> has<00:02:46.430> processed<00:02:46.790> more<00:02:47.120> than<00:02:47.360> 4.4<00:02:48.319> million 00:02:48.610 --> 00:02:48.620 align:start position:0% team has processed more than 4.4 million 00:02:48.620 --> 00:02:51.819 align:start position:0% team has processed more than 4.4 million blocks<00:02:49.180> which<00:02:50.180> consists<00:02:50.660> of<00:02:50.720> more<00:02:50.959> than<00:02:51.140> 71 00:02:51.819 --> 00:02:51.829 align:start position:0% blocks which consists of more than 71 00:02:51.829 --> 00:02:54.370 align:start position:0% blocks which consists of more than 71 million<00:02:52.069> transactions<00:02:52.790> and<00:02:53.780> I<00:02:53.870> wish<00:02:54.110> there 00:02:54.370 --> 00:02:54.380 align:start position:0% million transactions and I wish there 00:02:54.380 --> 00:02:56.229 align:start position:0% million transactions and I wish there are<00:02:54.440> more<00:02:54.620> than<00:02:54.739> thirty<00:02:55.400> seven<00:02:55.819> point<00:02:55.970> five 00:02:56.229 --> 00:02:56.239 align:start position:0% are more than thirty seven point five 00:02:56.239 --> 00:02:59.350 align:start position:0% are more than thirty seven point five million<00:02:56.750> internal<00:02:57.680> transactions<00:02:58.190> now<00:02:59.120> just 00:02:59.350 --> 00:02:59.360 align:start position:0% million internal transactions now just 00:02:59.360 --> 00:03:01.750 align:start position:0% million internal transactions now just to<00:02:59.510> further<00:02:59.840> clarify<00:03:00.049> an<00:03:00.760> internal 00:03:01.750 --> 00:03:01.760 align:start position:0% to further clarify an internal 00:03:01.760 --> 00:03:04.330 align:start position:0% to further clarify an internal transaction<00:03:02.329> really<00:03:02.720> isn't<00:03:02.870> an<00:03:03.340> official 00:03:04.330 --> 00:03:04.340 align:start position:0% transaction really isn't an official 00:03:04.340 --> 00:03:06.819 align:start position:0% transaction really isn't an official term<00:03:04.579> is<00:03:05.030> merely<00:03:05.269> a<00:03:05.360> term<00:03:05.690> that<00:03:05.829> blog 00:03:06.819 --> 00:03:06.829 align:start position:0% term is merely a term that blog 00:03:06.829 --> 00:03:09.640 align:start position:0% term is merely a term that blog explorers<00:03:07.310> came<00:03:07.549> to<00:03:07.760> dot<00:03:07.970> to<00:03:08.720> represent<00:03:09.500> a 00:03:09.640 --> 00:03:09.650 align:start position:0% explorers came to dot to represent a 00:03:09.650 --> 00:03:12.690 align:start position:0% explorers came to dot to represent a message<00:03:10.280> call<00:03:10.549> or<00:03:11.239> action<00:03:11.690> that<00:03:11.870> resulted<00:03:12.349> in 00:03:12.690 --> 00:03:12.700 align:start position:0% message call or action that resulted in 00:03:12.700 --> 00:03:19.780 align:start position:0% message call or action that resulted in a<00:03:13.720> value<00:03:14.720> transfer<00:03:17.709> and<00:03:18.709> just<00:03:19.310> to<00:03:19.400> give<00:03:19.639> you<00:03:19.730> an 00:03:19.780 --> 00:03:19.790 align:start position:0% a value transfer and just to give you an 00:03:19.790 --> 00:03:22.000 align:start position:0% a value transfer and just to give you an overview<00:03:20.060> of<00:03:20.269> how<00:03:20.690> far<00:03:21.200> the<00:03:21.260> interim 00:03:22.000 --> 00:03:22.010 align:start position:0% overview of how far the interim 00:03:22.010 --> 00:03:23.580 align:start position:0% overview of how far the interim blockchain<00:03:22.340> has<00:03:22.459> come<00:03:22.670> since<00:03:22.850> the<00:03:23.090> early<00:03:23.480> days 00:03:23.580 --> 00:03:23.590 align:start position:0% blockchain has come since the early days 00:03:23.590 --> 00:03:26.740 align:start position:0% blockchain has come since the early days so<00:03:24.590> we're<00:03:24.709> going<00:03:24.799> to<00:03:24.920> use<00:03:25.040> the<00:03:25.389> previous<00:03:26.389> DEF 00:03:26.740 --> 00:03:26.750 align:start position:0% so we're going to use the previous DEF 00:03:26.750 --> 00:03:29.620 align:start position:0% so we're going to use the previous DEF CON<00:03:27.019> conferences<00:03:27.620> as<00:03:27.829> data<00:03:28.579> points<00:03:28.970> or<00:03:29.030> DTM 00:03:29.620 --> 00:03:29.630 align:start position:0% CON conferences as data points or DTM 00:03:29.630 --> 00:03:32.680 align:start position:0% CON conferences as data points or DTM transaction<00:03:30.109> chart<00:03:30.910> so<00:03:31.910> at<00:03:32.000> Def<00:03:32.180> Con<00:03:32.209> one 00:03:32.680 --> 00:03:32.690 align:start position:0% transaction chart so at Def Con one 00:03:32.690 --> 00:03:36.550 align:start position:0% transaction chart so at Def Con one which<00:03:33.170> took<00:03:33.349> place<00:03:33.500> around<00:03:34.569> two<00:03:35.569> years<00:03:35.750> ago<00:03:36.109> in 00:03:36.550 --> 00:03:36.560 align:start position:0% which took place around two years ago in 00:03:36.560 --> 00:03:39.580 align:start position:0% which took place around two years ago in London<00:03:37.090> November<00:03:38.090> 2015<00:03:38.690> at<00:03:39.139> the<00:03:39.200> point<00:03:39.470> at 00:03:39.580 --> 00:03:39.590 align:start position:0% London November 2015 at the point at 00:03:39.590 --> 00:03:41.890 align:start position:0% London November 2015 at the point at time<00:03:39.799> the<00:03:40.160> term<00:03:40.790> blockchain<00:03:41.239> was<00:03:41.660> only 00:03:41.890 --> 00:03:41.900 align:start position:0% time the term blockchain was only 00:03:41.900 --> 00:03:44.470 align:start position:0% time the term blockchain was only processing<00:03:42.230> around<00:03:42.849> 8,500<00:03:43.849> transactions<00:03:44.329> per 00:03:44.470 --> 00:03:44.480 align:start position:0% processing around 8,500 transactions per 00:03:44.480 --> 00:03:49.080 align:start position:0% processing around 8,500 transactions per day<00:03:45.549> at<00:03:46.549> the<00:03:46.700> f-con<00:03:47.030> to<00:03:47.239> last<00:03:47.840> change<00:03:48.019> Shanghai 00:03:49.080 --> 00:03:49.090 align:start position:0% day at the f-con to last change Shanghai 00:03:49.090 --> 00:03:51.490 align:start position:0% day at the f-con to last change Shanghai the<00:03:50.090> term<00:03:50.299> blocks<00:03:50.510> was<00:03:50.840> processing<00:03:51.319> around 00:03:51.490 --> 00:03:51.500 align:start position:0% the term blocks was processing around 00:03:51.500 --> 00:03:54.550 align:start position:0% the term blocks was processing around forty<00:03:52.370> six<00:03:52.579> thousand<00:03:53.319> transactions<00:03:54.319> per<00:03:54.410> day 00:03:54.550 --> 00:03:54.560 align:start position:0% forty six thousand transactions per day 00:03:54.560 --> 00:03:57.729 align:start position:0% forty six thousand transactions per day representing<00:03:55.250> a<00:03:55.400> 5x<00:03:56.239> or<00:03:56.450> a<00:03:56.709> 500%<00:03:57.709> increase 00:03:57.729 --> 00:03:57.739 align:start position:0% representing a 5x or a 500% increase 00:03:57.739 --> 00:04:01.479 align:start position:0% representing a 5x or a 500% increase from<00:03:58.280> the<00:03:58.400> previous<00:03:58.430> year<00:03:59.650> today<00:04:00.650> a<00:04:00.680> DEFCON<00:04:00.950> 3 00:04:01.479 --> 00:04:01.489 align:start position:0% from the previous year today a DEFCON 3 00:04:01.489 --> 00:04:04.089 align:start position:0% from the previous year today a DEFCON 3 the<00:04:01.790> term<00:04:02.030> networks<00:04:02.359> processing<00:04:02.840> outputs<00:04:03.319> up 00:04:04.089 --> 00:04:04.099 align:start position:0% the term networks processing outputs up 00:04:04.099 --> 00:04:07.000 align:start position:0% the term networks processing outputs up to<00:04:04.340> half<00:04:04.880> a<00:04:05.030> million<00:04:05.299> or<00:04:05.799> 500,000<00:04:06.799> passengers 00:04:07.000 --> 00:04:07.010 align:start position:0% to half a million or 500,000 passengers 00:04:07.010 --> 00:04:10.509 align:start position:0% to half a million or 500,000 passengers per<00:04:07.370> day<00:04:07.400> representing<00:04:08.180> a<00:04:08.299> 10x<00:04:09.169> or<00:04:09.349> a<00:04:09.519> 1000% 00:04:10.509 --> 00:04:10.519 align:start position:0% per day representing a 10x or a 1000% 00:04:10.519 --> 00:04:14.729 align:start position:0% per day representing a 10x or a 1000% increase<00:04:10.639> in<00:04:10.970> number<00:04:11.419> of<00:04:11.450> their<00:04:11.660> transactions 00:04:14.729 --> 00:04:14.739 align:start position:0% 00:04:14.739 --> 00:04:19.360 align:start position:0% as<00:04:15.739> for<00:04:15.980> the<00:04:16.280> interim<00:04:16.609> block<00:04:16.820> times<00:04:18.370> pre 00:04:19.360 --> 00:04:19.370 align:start position:0% as for the interim block times pre 00:04:19.370 --> 00:04:23.529 align:start position:0% as for the interim block times pre byzantium<00:04:19.970> folk<00:04:20.889> the<00:04:21.889> block<00:04:22.460> x<00:04:22.729> used<00:04:23.030> around 00:04:23.529 --> 00:04:23.539 align:start position:0% byzantium folk the block x used around 00:04:23.539 --> 00:04:26.920 align:start position:0% byzantium folk the block x used around 30<00:04:24.200> seconds<00:04:24.680> a<00:04:24.919> post<00:04:25.610> by<00:04:25.789> the<00:04:25.849> NMR<00:04:26.300> fork<00:04:26.599> after 00:04:26.920 --> 00:04:26.930 align:start position:0% 30 seconds a post by the NMR fork after 00:04:26.930 --> 00:04:30.080 align:start position:0% 30 seconds a post by the NMR fork after october<00:04:27.500> 16<00:04:27.950> 20<00:04:28.880> 71<00:04:29.300> now<00:04:29.479> looking 00:04:30.080 --> 00:04:30.090 align:start position:0% october 16 20 71 now looking 00:04:30.090 --> 00:04:32.720 align:start position:0% october 16 20 71 now looking the<00:04:30.360> block<00:04:30.960> times<00:04:31.170> have<00:04:31.460> significant<00:04:32.460> reduce 00:04:32.720 --> 00:04:32.730 align:start position:0% the block times have significant reduce 00:04:32.730 --> 00:04:34.790 align:start position:0% the block times have significant reduce they<00:04:33.330> were<00:04:33.480> now<00:04:33.720> everything<00:04:34.200> around<00:04:34.380> 14 00:04:34.790 --> 00:04:34.800 align:start position:0% they were now everything around 14 00:04:34.800 --> 00:04:37.760 align:start position:0% they were now everything around 14 seconds<00:04:35.240> today<00:04:36.240> today<00:04:36.660> the<00:04:36.690> term<00:04:37.410> blocks<00:04:37.650> is 00:04:37.760 --> 00:04:37.770 align:start position:0% seconds today today the term blocks is 00:04:37.770 --> 00:04:41.000 align:start position:0% seconds today today the term blocks is processing<00:04:38.390> more<00:04:39.390> transactions<00:04:40.050> at<00:04:40.650> shorter 00:04:41.000 --> 00:04:41.010 align:start position:0% processing more transactions at shorter 00:04:41.010 --> 00:04:42.170 align:start position:0% processing more transactions at shorter block<00:04:41.220> in<00:04:41.370> first<00:04:41.610> I<00:04:41.790> with<00:04:41.910> a<00:04:41.940> lower 00:04:42.170 --> 00:04:42.180 align:start position:0% block in first I with a lower 00:04:42.180 --> 00:04:48.250 align:start position:0% block in first I with a lower transaction<00:04:42.540> pending<00:04:43.050> queue<00:04:45.830> all<00:04:46.830> right<00:04:47.010> so 00:04:48.250 --> 00:04:48.260 align:start position:0% transaction pending queue all right so 00:04:48.260 --> 00:04:50.270 align:start position:0% transaction pending queue all right so yeah<00:04:49.260> for<00:04:49.380> the<00:04:49.470> next<00:04:49.590> section<00:04:49.770> I'd<00:04:49.980> like<00:04:50.130> to 00:04:50.270 --> 00:04:50.280 align:start position:0% yeah for the next section I'd like to 00:04:50.280 --> 00:05:04.690 align:start position:0% yeah for the next section I'd like to pass<00:04:50.610> a<00:04:50.640> mic<00:04:50.880> -<00:05:00.890> Thank<00:05:01.890> You<00:05:01.950> Matthew 00:05:04.690 --> 00:05:04.700 align:start position:0% 00:05:04.700 --> 00:05:08.240 align:start position:0% hi<00:05:05.700> I'm<00:05:05.910> we<00:05:06.120> product<00:05:07.020> manager<00:05:07.410> at<00:05:07.590> the<00:05:07.740> scan<00:05:08.070> I 00:05:08.240 --> 00:05:08.250 align:start position:0% hi I'm we product manager at the scan I 00:05:08.250 --> 00:05:09.650 align:start position:0% hi I'm we product manager at the scan I would<00:05:08.760> like<00:05:08.850> to<00:05:08.970> share<00:05:09.180> some<00:05:09.450> of<00:05:09.480> the 00:05:09.650 --> 00:05:09.660 align:start position:0% would like to share some of the 00:05:09.660 --> 00:05:11.560 align:start position:0% would like to share some of the challenges<00:05:09.690> we<00:05:10.350> face<00:05:10.590> in<00:05:10.830> building<00:05:11.220> and 00:05:11.560 --> 00:05:11.570 align:start position:0% challenges we face in building and 00:05:11.570 --> 00:05:14.060 align:start position:0% challenges we face in building and infrastructure<00:05:12.570> level<00:05:13.260> service<00:05:13.530> around<00:05:13.890> the 00:05:14.060 --> 00:05:14.070 align:start position:0% infrastructure level service around the 00:05:14.070 --> 00:05:16.790 align:start position:0% infrastructure level service around the atrium<00:05:14.310> blockchain<00:05:14.900> first<00:05:15.900> off<00:05:16.110> is<00:05:16.410> the<00:05:16.650> issue 00:05:16.790 --> 00:05:16.800 align:start position:0% atrium blockchain first off is the issue 00:05:16.800 --> 00:05:19.580 align:start position:0% atrium blockchain first off is the issue of<00:05:16.950> scale<00:05:17.250> already<00:05:17.610> we've<00:05:18.300> revolves<00:05:18.840> resolve 00:05:19.580 --> 00:05:19.590 align:start position:0% of scale already we've revolves resolve 00:05:19.590 --> 00:05:21.380 align:start position:0% of scale already we've revolves resolve revolves<00:05:20.160> around<00:05:20.430> managing<00:05:21.060> and<00:05:21.240> supporting 00:05:21.380 --> 00:05:21.390 align:start position:0% revolves around managing and supporting 00:05:21.390 --> 00:05:24.350 align:start position:0% revolves around managing and supporting and<00:05:21.870> ever-growing<00:05:22.350> user<00:05:22.680> base<00:05:23.060> just<00:05:24.060> looking 00:05:24.350 --> 00:05:24.360 align:start position:0% and ever-growing user base just looking 00:05:24.360 --> 00:05:26.360 align:start position:0% and ever-growing user base just looking at<00:05:24.480> a<00:05:24.540> transactions<00:05:25.080> volume<00:05:25.440> alone<00:05:25.710> we<00:05:26.280> have 00:05:26.360 --> 00:05:26.370 align:start position:0% at a transactions volume alone we have 00:05:26.370 --> 00:05:28.490 align:start position:0% at a transactions volume alone we have seen<00:05:26.610> an<00:05:26.910> average<00:05:27.120> of<00:05:27.390> up<00:05:27.540> to<00:05:27.570> 10<00:05:27.930> times<00:05:28.140> growth 00:05:28.490 --> 00:05:28.500 align:start position:0% seen an average of up to 10 times growth 00:05:28.500 --> 00:05:31.430 align:start position:0% seen an average of up to 10 times growth year-on-year<00:05:29.040> and<00:05:30.000> from<00:05:30.840> an<00:05:30.960> operational 00:05:31.430 --> 00:05:31.440 align:start position:0% year-on-year and from an operational 00:05:31.440 --> 00:05:33.860 align:start position:0% year-on-year and from an operational viewpoint<00:05:31.940> hiring<00:05:32.940> and<00:05:33.090> expanding<00:05:33.150> and<00:05:33.600> team 00:05:33.860 --> 00:05:33.870 align:start position:0% viewpoint hiring and expanding and team 00:05:33.870 --> 00:05:35.690 align:start position:0% viewpoint hiring and expanding and team is<00:05:34.080> also<00:05:34.260> tricky<00:05:34.590> as<00:05:34.890> there's<00:05:35.250> a<00:05:35.340> shortage<00:05:35.640> of 00:05:35.690 --> 00:05:35.700 align:start position:0% is also tricky as there's a shortage of 00:05:35.700 --> 00:05:38.740 align:start position:0% is also tricky as there's a shortage of blockchain<00:05:36.600> their<00:05:36.810> place<00:05:37.020> in<00:05:37.230> the<00:05:37.380> space 00:05:38.740 --> 00:05:38.750 align:start position:0% blockchain their place in the space 00:05:38.750 --> 00:05:43.760 align:start position:0% blockchain their place in the space security<00:05:39.750> is<00:05:40.280> sorry<00:05:42.350> security<00:05:43.350> is<00:05:43.410> always<00:05:43.620> a 00:05:43.760 --> 00:05:43.770 align:start position:0% security is sorry security is always a 00:05:43.770 --> 00:05:46.520 align:start position:0% security is sorry security is always a top<00:05:44.070> concept<00:05:44.580> top<00:05:44.880> concern<00:05:45.270> for<00:05:45.420> us<00:05:45.630> being<00:05:46.410> on 00:05:46.520 --> 00:05:46.530 align:start position:0% top concept top concern for us being on 00:05:46.530 --> 00:05:48.640 align:start position:0% top concept top concern for us being on a<00:05:46.560> protocol<00:05:47.070> of<00:05:47.280> application<00:05:48.000> level<00:05:48.390> or 00:05:48.640 --> 00:05:48.650 align:start position:0% a protocol of application level or 00:05:48.650 --> 00:05:51.430 align:start position:0% a protocol of application level or external<00:05:49.650> event<00:05:49.950> such<00:05:50.100> as<00:05:50.130> DDoS<00:05:50.580> attacks 00:05:51.430 --> 00:05:51.440 align:start position:0% external event such as DDoS attacks 00:05:51.440 --> 00:05:54.890 align:start position:0% external event such as DDoS attacks being<00:05:52.440> the<00:05:52.590> space<00:05:52.860> as<00:05:53.100> we<00:05:53.310> all<00:05:53.430> know<00:05:53.700> and<00:05:54.270> is<00:05:54.420> if 00:05:54.890 --> 00:05:54.900 align:start position:0% being the space as we all know and is if 00:05:54.900 --> 00:05:56.750 align:start position:0% being the space as we all know and is if there<00:05:55.200> exists<00:05:55.590> and<00:05:55.770> any<00:05:56.250> security 00:05:56.750 --> 00:05:56.760 align:start position:0% there exists and any security 00:05:56.760 --> 00:05:59.600 align:start position:0% there exists and any security vulnerabilities<00:05:57.680> you'll<00:05:58.680> be<00:05:58.800> fairly<00:05:59.160> quickly 00:05:59.600 --> 00:05:59.610 align:start position:0% vulnerabilities you'll be fairly quickly 00:05:59.610 --> 00:06:03.200 align:start position:0% vulnerabilities you'll be fairly quickly exploited<00:06:00.540> or<00:06:00.720> taken<00:06:01.050> advantage<00:06:01.140> of<00:06:01.620> on<00:06:02.580> the 00:06:03.200 --> 00:06:03.210 align:start position:0% exploited or taken advantage of on the 00:06:03.210 --> 00:06:05.810 align:start position:0% exploited or taken advantage of on the support<00:06:03.630> front<00:06:03.870> we<00:06:04.650> have<00:06:04.770> seen<00:06:05.040> changing<00:06:05.550> user 00:06:05.810 --> 00:06:05.820 align:start position:0% support front we have seen changing user 00:06:05.820 --> 00:06:08.780 align:start position:0% support front we have seen changing user dynamics<00:06:06.330> over<00:06:06.660> the<00:06:06.750> last<00:06:06.960> two<00:06:07.260> years<00:06:07.790> back 00:06:08.780 --> 00:06:08.790 align:start position:0% dynamics over the last two years back 00:06:08.790 --> 00:06:11.120 align:start position:0% dynamics over the last two years back then<00:06:09.000> when<00:06:09.240> we<00:06:09.270> first<00:06:09.630> started<00:06:09.990> most<00:06:10.860> of<00:06:11.010> the 00:06:11.120 --> 00:06:11.130 align:start position:0% then when we first started most of the 00:06:11.130 --> 00:06:13.190 align:start position:0% then when we first started most of the questions<00:06:11.310> or<00:06:11.730> issues<00:06:11.940> that<00:06:12.210> we<00:06:12.630> receive<00:06:12.990> are 00:06:13.190 --> 00:06:13.200 align:start position:0% questions or issues that we receive are 00:06:13.200 --> 00:06:15.650 align:start position:0% questions or issues that we receive are more<00:06:13.500> technical<00:06:13.920> in<00:06:14.100> nature<00:06:14.130> or<00:06:14.820> coming<00:06:15.480> from 00:06:15.650 --> 00:06:15.660 align:start position:0% more technical in nature or coming from 00:06:15.660 --> 00:06:18.040 align:start position:0% more technical in nature or coming from CalPERS<00:06:16.260> already<00:06:16.590> work<00:06:16.740> in<00:06:16.860> the<00:06:16.950> space 00:06:18.040 --> 00:06:18.050 align:start position:0% CalPERS already work in the space 00:06:18.050 --> 00:06:20.090 align:start position:0% CalPERS already work in the space however<00:06:19.050> going<00:06:19.290> forward<00:06:19.740> since<00:06:19.950> the 00:06:20.090 --> 00:06:20.100 align:start position:0% however going forward since the 00:06:20.100 --> 00:06:21.950 align:start position:0% however going forward since the beginning<00:06:20.340> of<00:06:20.400> year<00:06:20.610> we<00:06:21.270> have<00:06:21.360> seen<00:06:21.600> more<00:06:21.900> and 00:06:21.950 --> 00:06:21.960 align:start position:0% beginning of year we have seen more and 00:06:21.960 --> 00:06:23.990 align:start position:0% beginning of year we have seen more and more<00:06:22.170> normal<00:06:22.710> regular<00:06:23.160> users<00:06:23.580> coming<00:06:23.820> on 00:06:23.990 --> 00:06:24.000 align:start position:0% more normal regular users coming on 00:06:24.000 --> 00:06:27.020 align:start position:0% more normal regular users coming on board<00:06:24.150> on<00:06:24.750> a<00:06:25.500> daily<00:06:25.800> basis<00:06:26.220> we<00:06:26.580> are<00:06:26.610> receiving 00:06:27.020 --> 00:06:27.030 align:start position:0% board on a daily basis we are receiving 00:06:27.030 --> 00:06:29.540 align:start position:0% board on a daily basis we are receiving an<00:06:27.330> average<00:06:27.930> of<00:06:28.080> 80<00:06:28.290> 200<00:06:28.800> tickets<00:06:28.890> per<00:06:29.190> day<00:06:29.340> and 00:06:29.540 --> 00:06:29.550 align:start position:0% an average of 80 200 tickets per day and 00:06:29.550 --> 00:06:31.460 align:start position:0% an average of 80 200 tickets per day and most<00:06:30.180> of<00:06:30.300> the<00:06:30.420> users<00:06:30.750> are<00:06:30.990> first-time 00:06:31.460 --> 00:06:31.470 align:start position:0% most of the users are first-time 00:06:31.470 --> 00:06:33.770 align:start position:0% most of the users are first-time blockchain<00:06:31.980> users<00:06:32.370> with<00:06:32.970> basic<00:06:33.360> questions 00:06:33.770 --> 00:06:33.780 align:start position:0% blockchain users with basic questions 00:06:33.780 --> 00:06:36.170 align:start position:0% blockchain users with basic questions such<00:06:33.960> as<00:06:33.990> how<00:06:34.830> do<00:06:34.890> they<00:06:35.130> transfer<00:06:35.520> tokens 00:06:36.170 --> 00:06:36.180 align:start position:0% such as how do they transfer tokens 00:06:36.180 --> 00:06:39.050 align:start position:0% such as how do they transfer tokens missing<00:06:36.870> or<00:06:36.990> invalid<00:06:37.110> transactions<00:06:37.950> or<00:06:38.640> even 00:06:39.050 --> 00:06:39.060 align:start position:0% missing or invalid transactions or even 00:06:39.060 --> 00:06:41.120 align:start position:0% missing or invalid transactions or even request<00:06:39.210> for<00:06:39.540> refunds<00:06:39.900> which<00:06:40.680> we<00:06:40.830> all<00:06:40.950> know 00:06:41.120 --> 00:06:41.130 align:start position:0% request for refunds which we all know 00:06:41.130 --> 00:06:42.790 align:start position:0% request for refunds which we all know it's<00:06:41.280> not<00:06:41.340> possible 00:06:42.790 --> 00:06:42.800 align:start position:0% it's not possible 00:06:42.800 --> 00:06:44.230 align:start position:0% it's not possible you<00:06:42.860> cannot<00:06:43.099> reverse<00:06:43.370> transactions<00:06:43.940> on<00:06:44.120> it 00:06:44.230 --> 00:06:44.240 align:start position:0% you cannot reverse transactions on it 00:06:44.240 --> 00:06:47.320 align:start position:0% you cannot reverse transactions on it really<00:06:45.310> given<00:06:46.310> the<00:06:46.460> ecosystem<00:06:47.030> is<00:06:47.150> still 00:06:47.320 --> 00:06:47.330 align:start position:0% really given the ecosystem is still 00:06:47.330 --> 00:06:50.140 align:start position:0% really given the ecosystem is still fairly<00:06:47.539> young<00:06:47.780> and<00:06:47.960> evolving<00:06:48.500> so<00:06:48.680> fast<00:06:49.150> at 00:06:50.140 --> 00:06:50.150 align:start position:0% fairly young and evolving so fast at 00:06:50.150 --> 00:06:52.360 align:start position:0% fairly young and evolving so fast at times<00:06:50.569> is<00:06:50.930> also<00:06:51.319> a<00:06:51.349> challenge<00:06:51.590> for<00:06:51.919> us<00:06:51.949> just<00:06:52.250> to 00:06:52.360 --> 00:06:52.370 align:start position:0% times is also a challenge for us just to 00:06:52.370 --> 00:06:55.360 align:start position:0% times is also a challenge for us just to keep<00:06:52.610> it<00:06:52.699> up<00:06:53.470> there's<00:06:54.470> never<00:06:54.650> a<00:06:54.770> boring<00:06:55.069> week 00:06:55.360 --> 00:06:55.370 align:start position:0% keep it up there's never a boring week 00:06:55.370 --> 00:06:59.040 align:start position:0% keep it up there's never a boring week with<00:06:55.759> aetherium<00:06:56.319> new<00:06:57.319> features<00:06:57.710> i<00:06:58.129> SEOs 00:06:59.040 --> 00:06:59.050 align:start position:0% with aetherium new features i SEOs 00:06:59.050 --> 00:07:01.899 align:start position:0% with aetherium new features i SEOs secretary<00:07:00.050> issues<00:07:00.669> multiple<00:07:01.669> software 00:07:01.899 --> 00:07:01.909 align:start position:0% secretary issues multiple software 00:07:01.909 --> 00:07:03.909 align:start position:0% secretary issues multiple software revision<00:07:02.479> patches<00:07:02.870> within<00:07:03.289> a<00:07:03.470> short<00:07:03.680> space<00:07:03.860> of 00:07:03.909 --> 00:07:03.919 align:start position:0% revision patches within a short space of 00:07:03.919 --> 00:07:07.480 align:start position:0% revision patches within a short space of time<00:07:05.289> while<00:07:06.289> it's<00:07:06.470> extremely<00:07:07.009> exciting 00:07:07.480 --> 00:07:07.490 align:start position:0% time while it's extremely exciting 00:07:07.490 --> 00:07:09.339 align:start position:0% time while it's extremely exciting interesting<00:07:07.819> it<00:07:08.569> can<00:07:08.629> be<00:07:08.870> difficult<00:07:09.080> to 00:07:09.339 --> 00:07:09.349 align:start position:0% interesting it can be difficult to 00:07:09.349 --> 00:07:11.050 align:start position:0% interesting it can be difficult to manage<00:07:09.560> over<00:07:09.889> a<00:07:10.039> longer<00:07:10.340> period<00:07:10.610> of<00:07:10.789> time 00:07:11.050 --> 00:07:11.060 align:start position:0% manage over a longer period of time 00:07:11.060 --> 00:07:15.369 align:start position:0% manage over a longer period of time and<00:07:12.039> lastly<00:07:13.039> the<00:07:13.729> final<00:07:14.180> issue<00:07:14.690> revolves 00:07:15.369 --> 00:07:15.379 align:start position:0% and lastly the final issue revolves 00:07:15.379 --> 00:07:17.709 align:start position:0% and lastly the final issue revolves around<00:07:15.500> interim<00:07:16.069> notes<00:07:16.250> management<00:07:16.819> which<00:07:17.569> is 00:07:17.709 --> 00:07:17.719 align:start position:0% around interim notes management which is 00:07:17.719 --> 00:07:19.600 align:start position:0% around interim notes management which is something<00:07:17.990> at<00:07:18.440> least<00:07:18.710> one<00:07:18.979> that<00:07:19.219> we<00:07:19.370> often 00:07:19.600 --> 00:07:19.610 align:start position:0% something at least one that we often 00:07:19.610 --> 00:07:22.540 align:start position:0% something at least one that we often been<00:07:19.849> asked<00:07:20.120> about<00:07:20.330> and<00:07:20.690> we<00:07:21.169> exploded<00:07:21.680> in<00:07:22.190> the 00:07:22.540 --> 00:07:22.550 align:start position:0% been asked about and we exploded in the 00:07:22.550 --> 00:07:29.080 align:start position:0% been asked about and we exploded in the infrared<00:07:23.300> details<00:07:26.740> that<00:07:27.740> either<00:07:27.919> scan<00:07:28.280> in<00:07:28.909> the 00:07:29.080 --> 00:07:29.090 align:start position:0% infrared details that either scan in the 00:07:29.090 --> 00:07:31.180 align:start position:0% infrared details that either scan in the earlier<00:07:29.330> days<00:07:29.509> we<00:07:30.169> ran<00:07:30.409> three<00:07:30.740> different 00:07:31.180 --> 00:07:31.190 align:start position:0% earlier days we ran three different 00:07:31.190 --> 00:07:35.589 align:start position:0% earlier days we ran three different client<00:07:31.490> implementations<00:07:32.210> namely<00:07:33.550> get<00:07:34.599> parity 00:07:35.589 --> 00:07:35.599 align:start position:0% client implementations namely get parity 00:07:35.599 --> 00:07:39.520 align:start position:0% client implementations namely get parity and<00:07:35.840> TMJ<00:07:36.849> over<00:07:37.849> time<00:07:38.120> we<00:07:38.810> managed<00:07:39.169> to<00:07:39.199> reduce 00:07:39.520 --> 00:07:39.530 align:start position:0% and TMJ over time we managed to reduce 00:07:39.530 --> 00:07:42.670 align:start position:0% and TMJ over time we managed to reduce this<00:07:39.919> to<00:07:39.979> just<00:07:40.430> two<00:07:40.639> clients<00:07:41.259> which<00:07:42.259> is<00:07:42.440> get 00:07:42.670 --> 00:07:42.680 align:start position:0% this to just two clients which is get 00:07:42.680 --> 00:07:46.540 align:start position:0% this to just two clients which is get and<00:07:42.919> parity<00:07:43.539> so<00:07:44.539> some<00:07:44.780> of<00:07:44.810> you<00:07:45.080> may<00:07:45.289> ask<00:07:45.530> why<00:07:46.490> do 00:07:46.540 --> 00:07:46.550 align:start position:0% and parity so some of you may ask why do 00:07:46.550 --> 00:07:48.939 align:start position:0% and parity so some of you may ask why do we<00:07:46.789> need<00:07:46.940> to<00:07:47.060> run<00:07:47.240> two<00:07:47.509> clients<00:07:47.779> why<00:07:48.529> not<00:07:48.710> just 00:07:48.939 --> 00:07:48.949 align:start position:0% we need to run two clients why not just 00:07:48.949 --> 00:07:51.730 align:start position:0% we need to run two clients why not just one<00:07:49.810> we<00:07:50.810> are<00:07:50.900> not<00:07:51.020> saying<00:07:51.289> this<00:07:51.529> is<00:07:51.710> the 00:07:51.730 --> 00:07:51.740 align:start position:0% one we are not saying this is the 00:07:51.740 --> 00:07:54.399 align:start position:0% one we are not saying this is the correct<00:07:52.219> way<00:07:52.400> but<00:07:52.759> this<00:07:53.690> is<00:07:53.840> what<00:07:54.080> we<00:07:54.229> found 00:07:54.399 --> 00:07:54.409 align:start position:0% correct way but this is what we found 00:07:54.409 --> 00:07:58.269 align:start position:0% correct way but this is what we found works<00:07:54.680> best<00:07:54.830> for<00:07:55.069> us<00:07:56.050> so<00:07:57.050> while<00:07:57.289> both<00:07:57.590> clients 00:07:58.269 --> 00:07:58.279 align:start position:0% works best for us so while both clients 00:07:58.279 --> 00:08:01.330 align:start position:0% works best for us so while both clients supports<00:07:58.880> all<00:07:59.029> the<00:07:59.539> official<00:07:59.990> api's<00:08:00.349> there 00:08:01.330 --> 00:08:01.340 align:start position:0% supports all the official api's there 00:08:01.340 --> 00:08:03.279 align:start position:0% supports all the official api's there are<00:08:01.400> certain<00:08:01.789> areas<00:08:02.060> that<00:08:02.300> each<00:08:02.870> of<00:08:02.900> these 00:08:03.279 --> 00:08:03.289 align:start position:0% are certain areas that each of these 00:08:03.289 --> 00:08:07.360 align:start position:0% are certain areas that each of these clients<00:08:03.620> excels<00:08:04.340> in<00:08:05.080> for<00:08:06.080> instance<00:08:06.469> if<00:08:07.130> you 00:08:07.360 --> 00:08:07.370 align:start position:0% clients excels in for instance if you 00:08:07.370 --> 00:08:10.120 align:start position:0% clients excels in for instance if you plan<00:08:07.639> to<00:08:07.669> use<00:08:07.819> remix<00:08:08.479> debugger<00:08:08.810> for<00:08:09.770> now<00:08:09.919> this 00:08:10.120 --> 00:08:10.130 align:start position:0% plan to use remix debugger for now this 00:08:10.130 --> 00:08:13.089 align:start position:0% plan to use remix debugger for now this works<00:08:10.610> only<00:08:10.789> we<00:08:11.029> get<00:08:11.319> on<00:08:12.319> the<00:08:12.500> other<00:08:12.620> hand<00:08:12.919> if 00:08:13.089 --> 00:08:13.099 align:start position:0% works only we get on the other hand if 00:08:13.099 --> 00:08:15.570 align:start position:0% works only we get on the other hand if you<00:08:13.789> need<00:08:14.060> to<00:08:14.180> trace<00:08:14.419> internal<00:08:14.900> transactions 00:08:15.570 --> 00:08:15.580 align:start position:0% you need to trace internal transactions 00:08:15.580 --> 00:08:18.490 align:start position:0% you need to trace internal transactions parity<00:08:16.580> provides<00:08:16.969> an<00:08:17.240> easy-to-use<00:08:17.599> RPC 00:08:18.490 --> 00:08:18.500 align:start position:0% parity provides an easy-to-use RPC 00:08:18.500 --> 00:08:21.760 align:start position:0% parity provides an easy-to-use RPC endpoint<00:08:18.889> the<00:08:19.009> dusties<00:08:20.409> but<00:08:21.409> more<00:08:21.590> than<00:08:21.710> just 00:08:21.760 --> 00:08:21.770 align:start position:0% endpoint the dusties but more than just 00:08:21.770 --> 00:08:24.519 align:start position:0% endpoint the dusties but more than just feature<00:08:22.159> set<00:08:22.490> running<00:08:23.360> multiple<00:08:23.779> clients 00:08:24.519 --> 00:08:24.529 align:start position:0% feature set running multiple clients 00:08:24.529 --> 00:08:26.709 align:start position:0% feature set running multiple clients also<00:08:25.219> provide<00:08:25.639> what<00:08:25.909> we<00:08:25.940> call<00:08:26.029> network 00:08:26.709 --> 00:08:26.719 align:start position:0% also provide what we call network 00:08:26.719 --> 00:08:30.580 align:start position:0% also provide what we call network robustness<00:08:27.229> a<00:08:28.270> case<00:08:29.270> in<00:08:29.419> hand<00:08:29.599> some<00:08:30.319> of<00:08:30.469> you 00:08:30.580 --> 00:08:30.590 align:start position:0% robustness a case in hand some of you 00:08:30.590 --> 00:08:32.380 align:start position:0% robustness a case in hand some of you may<00:08:30.740> recall<00:08:31.009> that<00:08:31.069> during<00:08:31.340> DEFCON<00:08:31.969> 2<00:08:32.240> in 00:08:32.380 --> 00:08:32.390 align:start position:0% may recall that during DEFCON 2 in 00:08:32.390 --> 00:08:35.110 align:start position:0% may recall that during DEFCON 2 in Shanghai<00:08:32.690> last<00:08:32.870> year<00:08:33.279> the<00:08:34.279> network<00:08:34.610> was<00:08:34.789> under 00:08:35.110 --> 00:08:35.120 align:start position:0% Shanghai last year the network was under 00:08:35.120 --> 00:08:37.089 align:start position:0% Shanghai last year the network was under a<00:08:35.149> massive<00:08:35.449> DDoS<00:08:35.930> attack<00:08:36.260> just<00:08:36.649> before<00:08:37.010> the 00:08:37.089 --> 00:08:37.099 align:start position:0% a massive DDoS attack just before the 00:08:37.099 --> 00:08:40.360 align:start position:0% a massive DDoS attack just before the event<00:08:37.159> started<00:08:38.529> one<00:08:39.529> of<00:08:39.560> the<00:08:39.740> reasons<00:08:40.130> that 00:08:40.360 --> 00:08:40.370 align:start position:0% event started one of the reasons that 00:08:40.370 --> 00:08:41.800 align:start position:0% event started one of the reasons that the<00:08:40.519> network<00:08:40.880> was<00:08:41.000> able<00:08:41.390> to<00:08:41.419> continue 00:08:41.800 --> 00:08:41.810 align:start position:0% the network was able to continue 00:08:41.810 --> 00:08:44.019 align:start position:0% the network was able to continue chugging<00:08:42.289> along<00:08:42.380> was<00:08:43.159> when<00:08:43.430> a<00:08:43.459> specified 00:08:44.019 --> 00:08:44.029 align:start position:0% chugging along was when a specified 00:08:44.029 --> 00:08:46.840 align:start position:0% chugging along was when a specified attack<00:08:44.630> was<00:08:45.050> successfully<00:08:45.980> executed<00:08:46.010> against 00:08:46.840 --> 00:08:46.850 align:start position:0% attack was successfully executed against 00:08:46.850 --> 00:08:48.699 align:start position:0% attack was successfully executed against one<00:08:47.000> client<00:08:47.240> the<00:08:47.990> other<00:08:48.110> client<00:08:48.560> was<00:08:48.680> not 00:08:48.699 --> 00:08:48.709 align:start position:0% one client the other client was not 00:08:48.709 --> 00:08:53.440 align:start position:0% one client the other client was not affected<00:08:49.339> I'm<00:08:50.029> vice<00:08:50.300> versa 00:08:53.440 --> 00:08:53.450 align:start position:0% 00:08:53.450 --> 00:08:56.240 align:start position:0% so<00:08:54.450> while<00:08:54.690> both<00:08:54.930> get<00:08:55.320> and<00:08:55.560> parity<00:08:55.980> works 00:08:56.240 --> 00:08:56.250 align:start position:0% so while both get and parity works 00:08:56.250 --> 00:08:58.250 align:start position:0% so while both get and parity works extremely<00:08:56.640> well<00:08:56.910> for<00:08:57.060> private<00:08:57.930> notes<00:08:58.110> in 00:08:58.250 --> 00:08:58.260 align:start position:0% extremely well for private notes in 00:08:58.260 --> 00:09:00.260 align:start position:0% extremely well for private notes in default<00:08:58.590> settings<00:08:58.980> there<00:08:59.970> are<00:09:00.030> some 00:09:00.260 --> 00:09:00.270 align:start position:0% default settings there are some 00:09:00.270 --> 00:09:02.480 align:start position:0% default settings there are some challenges<00:09:00.540> when<00:09:01.080> running<00:09:01.290> these<00:09:01.590> as<00:09:01.920> public 00:09:02.480 --> 00:09:02.490 align:start position:0% challenges when running these as public 00:09:02.490 --> 00:09:06.200 align:start position:0% challenges when running these as public fun<00:09:02.850> facing<00:09:03.300> notes<00:09:04.010> for<00:09:05.010> instance<00:09:05.370> to<00:09:05.850> handle 00:09:06.200 --> 00:09:06.210 align:start position:0% fun facing notes for instance to handle 00:09:06.210 --> 00:09:08.150 align:start position:0% fun facing notes for instance to handle burst<00:09:06.480> of<00:09:06.630> traffic's<00:09:07.140> of<00:09:07.410> upwards<00:09:08.040> to 00:09:08.150 --> 00:09:08.160 align:start position:0% burst of traffic's of upwards to 00:09:08.160 --> 00:09:09.980 align:start position:0% burst of traffic's of upwards to thousands<00:09:08.670> of<00:09:08.730> concurring<00:09:09.240> API<00:09:09.480> calls<00:09:09.780> per 00:09:09.980 --> 00:09:09.990 align:start position:0% thousands of concurring API calls per 00:09:09.990 --> 00:09:12.400 align:start position:0% thousands of concurring API calls per seconds<00:09:10.410> here<00:09:11.220> are<00:09:11.370> some<00:09:11.550> recommendations 00:09:12.400 --> 00:09:12.410 align:start position:0% seconds here are some recommendations 00:09:12.410 --> 00:09:16.640 align:start position:0% seconds here are some recommendations tip<00:09:13.410> number<00:09:13.620> one<00:09:13.890> use<00:09:14.730> SSD<00:09:15.270> drives<00:09:15.570> do<00:09:16.320> not<00:09:16.470> use 00:09:16.640 --> 00:09:16.650 align:start position:0% tip number one use SSD drives do not use 00:09:16.650 --> 00:09:19.070 align:start position:0% tip number one use SSD drives do not use normal<00:09:17.040> hardest<00:09:17.400> rice<00:09:17.610> as<00:09:17.880> these<00:09:18.480> AI<00:09:18.690> ops<00:09:18.870> will 00:09:19.070 --> 00:09:19.080 align:start position:0% normal hardest rice as these AI ops will 00:09:19.080 --> 00:09:22.940 align:start position:0% normal hardest rice as these AI ops will be<00:09:19.200> about<00:09:19.350> a<00:09:19.410> net<00:09:19.850> tip<00:09:20.850> number<00:09:21.030> two<00:09:21.740> if<00:09:22.740> you<00:09:22.920> are 00:09:22.940 --> 00:09:22.950 align:start position:0% be about a net tip number two if you are 00:09:22.950 --> 00:09:25.310 align:start position:0% be about a net tip number two if you are Sparrow<00:09:23.310> X<00:09:23.520> program<00:09:23.760> you<00:09:24.540> can<00:09:24.720> allocate<00:09:24.900> like 00:09:25.310 --> 00:09:25.320 align:start position:0% Sparrow X program you can allocate like 00:09:25.320 --> 00:09:27.590 align:start position:0% Sparrow X program you can allocate like larger<00:09:25.890> cache<00:09:26.130> settings<00:09:26.340> than<00:09:27.180> the<00:09:27.300> default 00:09:27.590 --> 00:09:27.600 align:start position:0% larger cache settings than the default 00:09:27.600 --> 00:09:30.920 align:start position:0% larger cache settings than the default ones<00:09:28.910> when<00:09:29.910> running<00:09:30.120> over<00:09:30.420> a<00:09:30.450> longer<00:09:30.780> period 00:09:30.920 --> 00:09:30.930 align:start position:0% ones when running over a longer period 00:09:30.930 --> 00:09:33.100 align:start position:0% ones when running over a longer period of<00:09:31.260> time<00:09:31.320> with<00:09:31.680> a<00:09:31.710> high<00:09:31.980> concurrent<00:09:32.580> request 00:09:33.100 --> 00:09:33.110 align:start position:0% of time with a high concurrent request 00:09:33.110 --> 00:09:35.210 align:start position:0% of time with a high concurrent request you'll<00:09:34.110> want<00:09:34.350> to<00:09:34.380> run<00:09:34.590> some<00:09:34.890> sort<00:09:35.100> of 00:09:35.210 --> 00:09:35.220 align:start position:0% you'll want to run some sort of 00:09:35.220 --> 00:09:36.770 align:start position:0% you'll want to run some sort of monitoring<00:09:35.580> service<00:09:36.000> that<00:09:36.270> checks<00:09:36.600> if<00:09:36.720> the 00:09:36.770 --> 00:09:36.780 align:start position:0% monitoring service that checks if the 00:09:36.780 --> 00:09:38.780 align:start position:0% monitoring service that checks if the note<00:09:37.020> is<00:09:37.050> seen<00:09:37.350> Corelli<00:09:37.800> or<00:09:38.130> the<00:09:38.610> latest 00:09:38.780 --> 00:09:38.790 align:start position:0% note is seen Corelli or the latest 00:09:38.790 --> 00:09:41.000 align:start position:0% note is seen Corelli or the latest blocked<00:09:39.180> time<00:09:39.390> is<00:09:39.600> leaders<00:09:40.320> block<00:09:40.590> times<00:09:40.830> them 00:09:41.000 --> 00:09:41.010 align:start position:0% blocked time is leaders block times them 00:09:41.010 --> 00:09:44.120 align:start position:0% blocked time is leaders block times them it's<00:09:41.160> not<00:09:41.280> too<00:09:41.430> old<00:09:41.630> if<00:09:42.630> they<00:09:42.870> are<00:09:43.020> the<00:09:43.830> service 00:09:44.120 --> 00:09:44.130 align:start position:0% it's not too old if they are the service 00:09:44.130 --> 00:09:47.330 align:start position:0% it's not too old if they are the service you<00:09:44.250> restart<00:09:44.580> the<00:09:44.670> nodes<00:09:44.880> to<00:09:45.800> scale<00:09:46.800> upwards 00:09:47.330 --> 00:09:47.340 align:start position:0% you restart the nodes to scale upwards 00:09:47.340 --> 00:09:49.700 align:start position:0% you restart the nodes to scale upwards of<00:09:47.430> multiple<00:09:47.940> concurrent<00:09:48.330> connections<00:09:48.720> you 00:09:49.700 --> 00:09:49.710 align:start position:0% of multiple concurrent connections you 00:09:49.710 --> 00:09:52.730 align:start position:0% of multiple concurrent connections you may<00:09:49.860> want<00:09:50.190> to<00:09:50.600> deploy<00:09:51.600> multiple<00:09:52.440> smaller 00:09:52.730 --> 00:09:52.740 align:start position:0% may want to deploy multiple smaller 00:09:52.740 --> 00:09:55.610 align:start position:0% may want to deploy multiple smaller nodes<00:09:52.980> behind<00:09:53.490> a<00:09:53.640> load<00:09:54.090> balancer<00:09:54.620> application 00:09:55.610 --> 00:09:55.620 align:start position:0% nodes behind a load balancer application 00:09:55.620 --> 00:09:57.530 align:start position:0% nodes behind a load balancer application gateways<00:09:56.010> while<00:09:56.520> taking<00:09:56.760> care<00:09:57.060> of<00:09:57.090> the 00:09:57.530 --> 00:09:57.540 align:start position:0% gateways while taking care of the 00:09:57.540 --> 00:10:00.320 align:start position:0% gateways while taking care of the session<00:09:57.870> position<00:09:58.290> settings<00:09:58.790> are<00:09:59.790> now<00:10:00.030> passed 00:10:00.320 --> 00:10:00.330 align:start position:0% session position settings are now passed 00:10:00.330 --> 00:10:09.640 align:start position:0% session position settings are now passed to<00:10:00.510> metric<00:10:01.110> on<00:10:01.260> your<00:10:01.410> representation 00:10:09.640 --> 00:10:09.650 align:start position:0% 00:10:09.650 --> 00:10:19.460 align:start position:0% thanks<00:10:10.650> P<00:10:13.670> so<00:10:14.690> for<00:10:15.690> the<00:10:16.320> next<00:10:17.010> section<00:10:17.310> I<00:10:18.470> would 00:10:19.460 --> 00:10:19.470 align:start position:0% thanks P so for the next section I would 00:10:19.470 --> 00:10:23.140 align:start position:0% thanks P so for the next section I would like<00:10:19.680> to<00:10:19.830> talk<00:10:20.010> about<00:10:20.750> deriving<00:10:21.750> the<00:10:22.290> theorem 00:10:23.140 --> 00:10:23.150 align:start position:0% like to talk about deriving the theorem 00:10:23.150 --> 00:10:26.980 align:start position:0% like to talk about deriving the theorem user<00:10:24.150> persona<00:10:24.660> with<00:10:25.050> Google<00:10:25.440> Analytics 00:10:26.980 --> 00:10:26.990 align:start position:0% user persona with Google Analytics 00:10:26.990 --> 00:10:31.130 align:start position:0% user persona with Google Analytics so<00:10:27.990> as<00:10:28.470> a<00:10:29.070> blockchain<00:10:29.610> developer<00:10:30.210> or<00:10:30.630> as<00:10:31.020> the 00:10:31.130 --> 00:10:31.140 align:start position:0% so as a blockchain developer or as the 00:10:31.140 --> 00:10:32.900 align:start position:0% so as a blockchain developer or as the developer<00:10:31.500> in<00:10:31.560> general<00:10:31.920> one<00:10:32.520> of<00:10:32.610> the<00:10:32.700> things 00:10:32.900 --> 00:10:32.910 align:start position:0% developer in general one of the things 00:10:32.910 --> 00:10:36.080 align:start position:0% developer in general one of the things that<00:10:33.090> I<00:10:33.120> found<00:10:33.720> extremely<00:10:34.160> useful<00:10:35.160> is<00:10:35.520> when 00:10:36.080 --> 00:10:36.090 align:start position:0% that I found extremely useful is when 00:10:36.090 --> 00:10:37.640 align:start position:0% that I found extremely useful is when building<00:10:36.300> applications<00:10:36.960> is<00:10:37.260> to<00:10:37.440> first 00:10:37.640 --> 00:10:37.650 align:start position:0% building applications is to first 00:10:37.650 --> 00:10:40.130 align:start position:0% building applications is to first understand<00:10:38.070> who<00:10:38.730> your<00:10:39.150> target<00:10:39.540> audience<00:10:39.960> is 00:10:40.130 --> 00:10:40.140 align:start position:0% understand who your target audience is 00:10:40.140 --> 00:10:42.500 align:start position:0% understand who your target audience is who<00:10:40.560> your<00:10:40.890> users<00:10:41.130> are<00:10:41.430> who<00:10:41.820> your<00:10:42.120> customers 00:10:42.500 --> 00:10:42.510 align:start position:0% who your users are who your customers 00:10:42.510 --> 00:10:48.280 align:start position:0% who your users are who your customers are<00:10:43.400> so<00:10:44.480> ETS<00:10:45.480> can<00:10:45.720> add<00:10:45.990> as<00:10:46.830> a<00:10:46.890> base<00:10:47.700> layer 00:10:48.280 --> 00:10:48.290 align:start position:0% are so ETS can add as a base layer 00:10:48.290 --> 00:10:50.990 align:start position:0% are so ETS can add as a base layer infrastructure<00:10:49.290> service<00:10:49.650> for<00:10:50.610> the<00:10:50.700> interim 00:10:50.990 --> 00:10:51.000 align:start position:0% infrastructure service for the interim 00:10:51.000 --> 00:10:54.080 align:start position:0% infrastructure service for the interim blockchain<00:10:51.450> we<00:10:52.170> serve<00:10:52.590> a<00:10:52.950> diverse<00:10:53.430> range<00:10:53.610> of 00:10:54.080 --> 00:10:54.090 align:start position:0% blockchain we serve a diverse range of 00:10:54.090 --> 00:10:57.350 align:start position:0% blockchain we serve a diverse range of etrem<00:10:54.450> users<00:10:54.780> from<00:10:54.930> all<00:10:55.140> across<00:10:55.380> the<00:10:55.500> globe<00:10:56.360> so 00:10:57.350 --> 00:10:57.360 align:start position:0% etrem users from all across the globe so 00:10:57.360 --> 00:10:59.810 align:start position:0% etrem users from all across the globe so what<00:10:57.930> I<00:10:58.230> would<00:10:58.680> like<00:10:58.890> to<00:10:58.950> do<00:10:59.190> right<00:10:59.370> now<00:10:59.550> is<00:10:59.700> to 00:10:59.810 --> 00:10:59.820 align:start position:0% what I would like to do right now is to 00:10:59.820 --> 00:11:02.930 align:start position:0% what I would like to do right now is to share<00:11:00.060> via<00:11:00.240> our<00:11:01.110> own<00:11:01.410> a<00:11:01.770> very<00:11:02.190> own<00:11:02.400> Google 00:11:02.930 --> 00:11:02.940 align:start position:0% share via our own a very own Google 00:11:02.940 --> 00:11:05.360 align:start position:0% share via our own a very own Google Analytics<00:11:03.510> data<00:11:03.540> that<00:11:04.440> we<00:11:04.530> derived<00:11:04.890> over<00:11:05.190> the 00:11:05.360 --> 00:11:05.370 align:start position:0% Analytics data that we derived over the 00:11:05.370 --> 00:11:05.910 align:start position:0% Analytics data that we derived over the last 00:11:05.910 --> 00:11:05.920 align:start position:0% last 00:11:05.920 --> 00:11:08.879 align:start position:0% last and<00:11:06.100> half<00:11:06.249> years<00:11:06.549> which<00:11:07.420> we<00:11:08.290> feel<00:11:08.679> will 00:11:08.879 --> 00:11:08.889 align:start position:0% and half years which we feel will 00:11:08.889 --> 00:11:12.269 align:start position:0% and half years which we feel will provide<00:11:09.189> you<00:11:09.459> with<00:11:09.759> a<00:11:10.649> rough<00:11:11.649> indication<00:11:12.160> of 00:11:12.269 --> 00:11:12.279 align:start position:0% provide you with a rough indication of 00:11:12.279 --> 00:11:15.090 align:start position:0% provide you with a rough indication of what<00:11:12.429> the<00:11:12.699> typical<00:11:13.600> user<00:11:13.899> of<00:11:14.230> the<00:11:14.799> interim 00:11:15.090 --> 00:11:15.100 align:start position:0% what the typical user of the interim 00:11:15.100 --> 00:11:21.259 align:start position:0% what the typical user of the interim blockchain<00:11:15.399> looks<00:11:15.579> like<00:11:18.329> so<00:11:19.329> looking<00:11:19.929> at<00:11:20.049> our 00:11:21.259 --> 00:11:21.269 align:start position:0% blockchain looks like so looking at our 00:11:21.269 --> 00:11:24.299 align:start position:0% blockchain looks like so looking at our analytics<00:11:22.269> data<00:11:22.629> one<00:11:23.499> of<00:11:23.619> the<00:11:23.709> interesting 00:11:24.299 --> 00:11:24.309 align:start position:0% analytics data one of the interesting 00:11:24.309 --> 00:11:28.079 align:start position:0% analytics data one of the interesting things<00:11:24.549> that<00:11:24.669> we<00:11:24.999> found<00:11:25.299> was<00:11:26.019> a<00:11:26.290> shift<00:11:26.799> in<00:11:27.100> user 00:11:28.079 --> 00:11:28.089 align:start position:0% things that we found was a shift in user 00:11:28.089 --> 00:11:29.280 align:start position:0% things that we found was a shift in user geography<00:11:28.629> locations 00:11:29.280 --> 00:11:29.290 align:start position:0% geography locations 00:11:29.290 --> 00:11:34.109 align:start position:0% geography locations what<00:11:30.069> last<00:11:30.249> two<00:11:30.399> years<00:11:31.859> so<00:11:32.859> in<00:11:33.040> borders<00:11:33.459> the 00:11:34.109 --> 00:11:34.119 align:start position:0% what last two years so in borders the 00:11:34.119 --> 00:11:37.349 align:start position:0% what last two years so in borders the united<00:11:34.720> states<00:11:35.939> represented<00:11:36.939> our<00:11:37.029> largest 00:11:37.349 --> 00:11:37.359 align:start position:0% united states represented our largest 00:11:37.359 --> 00:11:41.729 align:start position:0% united states represented our largest user<00:11:37.569> base<00:11:38.279> in<00:11:39.600> 2016<00:11:40.600> the<00:11:41.169> united<00:11:41.529> states 00:11:41.729 --> 00:11:41.739 align:start position:0% user base in 2016 the united states 00:11:41.739 --> 00:11:44.789 align:start position:0% user base in 2016 the united states represented<00:11:42.699> half<00:11:42.939> of<00:11:43.119> our<00:11:43.239> user<00:11:43.389> base<00:11:43.799> around 00:11:44.789 --> 00:11:44.799 align:start position:0% represented half of our user base around 00:11:44.799 --> 00:11:49.139 align:start position:0% represented half of our user base around 44%<00:11:45.249> followed<00:11:45.879> by<00:11:46.089> Russia<00:11:46.859> Germany<00:11:48.149> United 00:11:49.139 --> 00:11:49.149 align:start position:0% 44% followed by Russia Germany United 00:11:49.149 --> 00:11:54.629 align:start position:0% 44% followed by Russia Germany United Kingdom<00:11:49.540> and<00:11:49.720> Ukraine<00:11:50.879> but<00:11:51.879> in<00:11:52.439> 2017<00:11:53.439> we<00:11:54.100> saw<00:11:54.369> a 00:11:54.629 --> 00:11:54.639 align:start position:0% Kingdom and Ukraine but in 2017 we saw a 00:11:54.639 --> 00:11:56.249 align:start position:0% Kingdom and Ukraine but in 2017 we saw a large<00:11:54.999> increase<00:11:55.299> in<00:11:55.419> number<00:11:55.779> of<00:11:55.809> users 00:11:56.249 --> 00:11:56.259 align:start position:0% large increase in number of users 00:11:56.259 --> 00:11:58.949 align:start position:0% large increase in number of users originating<00:11:57.129> from<00:11:57.160> coming<00:11:58.149> from<00:11:58.239> China<00:11:58.540> and 00:11:58.949 --> 00:11:58.959 align:start position:0% originating from coming from China and 00:11:58.959 --> 00:12:01.859 align:start position:0% originating from coming from China and the<00:11:59.889> emergence<00:12:00.369> of<00:12:00.519> new<00:12:00.579> interests<00:12:01.299> from 00:12:01.859 --> 00:12:01.869 align:start position:0% the emergence of new interests from 00:12:01.869 --> 00:12:06.539 align:start position:0% the emergence of new interests from South<00:12:02.379> Korea<00:12:03.089> in<00:12:04.089> the<00:12:04.359> crypto<00:12:04.629> scene<00:12:05.429> so<00:12:06.429> the 00:12:06.539 --> 00:12:06.549 align:start position:0% South Korea in the crypto scene so the 00:12:06.549 --> 00:12:08.999 align:start position:0% South Korea in the crypto scene so the take-home<00:12:06.730> points<00:12:07.529> while<00:12:08.529> the<00:12:08.619> United<00:12:08.980> States 00:12:08.999 --> 00:12:09.009 align:start position:0% take-home points while the United States 00:12:09.009 --> 00:12:12.840 align:start position:0% take-home points while the United States still<00:12:09.429> is<00:12:10.089> the<00:12:11.129> represents<00:12:12.129> the<00:12:12.220> largest<00:12:12.429> user 00:12:12.840 --> 00:12:12.850 align:start position:0% still is the represents the largest user 00:12:12.850 --> 00:12:15.720 align:start position:0% still is the represents the largest user base<00:12:13.829> China<00:12:14.829> is<00:12:14.980> definitely<00:12:15.129> a<00:12:15.399> growing 00:12:15.720 --> 00:12:15.730 align:start position:0% base China is definitely a growing 00:12:15.730 --> 00:12:18.689 align:start position:0% base China is definitely a growing market<00:12:16.379> in<00:12:17.379> at<00:12:17.649> least<00:12:17.799> South<00:12:18.160> Korea's<00:12:18.489> a<00:12:18.549> new 00:12:18.689 --> 00:12:18.699 align:start position:0% market in at least South Korea's a new 00:12:18.699 --> 00:12:22.739 align:start position:0% market in at least South Korea's a new player<00:12:18.910> on<00:12:18.939> the<00:12:19.029> scene<00:12:19.889> so<00:12:20.889> by<00:12:21.689> sort<00:12:22.689> of 00:12:22.739 --> 00:12:22.749 align:start position:0% player on the scene so by sort of 00:12:22.749 --> 00:12:24.960 align:start position:0% player on the scene so by sort of understanding<00:12:23.579> where<00:12:24.579> your<00:12:24.699> users<00:12:24.939> are 00:12:24.960 --> 00:12:24.970 align:start position:0% understanding where your users are 00:12:24.970 --> 00:12:27.269 align:start position:0% understanding where your users are located<00:12:25.509> know<00:12:25.809> perhaps<00:12:26.199> as<00:12:26.769> the<00:12:26.919> developer 00:12:27.269 --> 00:12:27.279 align:start position:0% located know perhaps as the developer 00:12:27.279 --> 00:12:30.689 align:start position:0% located know perhaps as the developer this<00:12:27.399> can<00:12:27.549> help<00:12:27.730> you<00:12:28.799> by<00:12:29.799> deciding<00:12:30.369> about 00:12:30.689 --> 00:12:30.699 align:start position:0% this can help you by deciding about 00:12:30.699 --> 00:12:32.759 align:start position:0% this can help you by deciding about optimizing<00:12:31.209> location<00:12:31.809> of<00:12:32.019> your<00:12:32.049> physical 00:12:32.759 --> 00:12:32.769 align:start position:0% optimizing location of your physical 00:12:32.769 --> 00:12:35.280 align:start position:0% optimizing location of your physical servers<00:12:33.129> or<00:12:33.519> like<00:12:33.999> or<00:12:34.209> even<00:12:34.239> like<00:12:34.809> when 00:12:35.280 --> 00:12:35.290 align:start position:0% servers or like or even like when 00:12:35.290 --> 00:12:37.919 align:start position:0% servers or like or even like when assigning<00:12:35.529> which<00:12:36.389> languages<00:12:37.389> you<00:12:37.569> should 00:12:37.919 --> 00:12:37.929 align:start position:0% assigning which languages you should 00:12:37.929 --> 00:12:43.829 align:start position:0% assigning which languages you should support<00:12:38.079> for<00:12:38.410> your<00:12:38.529> application<00:12:42.089> so<00:12:43.089> as<00:12:43.360> for 00:12:43.829 --> 00:12:43.839 align:start position:0% support for your application so as for 00:12:43.839 --> 00:12:46.379 align:start position:0% support for your application so as for the<00:12:43.899> age<00:12:44.169> engendered<00:12:44.980> user<00:12:45.189> demographics<00:12:45.850> our 00:12:46.379 --> 00:12:46.389 align:start position:0% the age engendered user demographics our 00:12:46.389 --> 00:12:49.289 align:start position:0% the age engendered user demographics our data<00:12:46.660> was<00:12:46.959> actually<00:12:47.199> fairly<00:12:48.179> consistent<00:12:49.179> of 00:12:49.289 --> 00:12:49.299 align:start position:0% data was actually fairly consistent of 00:12:49.299 --> 00:12:53.279 align:start position:0% data was actually fairly consistent of what<00:12:49.480> one<00:12:50.319> might<00:12:50.529> expect<00:12:50.559> in<00:12:51.100> crypto<00:12:51.970> scene<00:12:52.289> so 00:12:53.279 --> 00:12:53.289 align:start position:0% what one might expect in crypto scene so 00:12:53.289 --> 00:12:55.289 align:start position:0% what one might expect in crypto scene so it's<00:12:53.499> still<00:12:53.799> largely<00:12:54.100> dominated<00:12:54.459> by<00:12:55.029> males 00:12:55.289 --> 00:12:55.299 align:start position:0% it's still largely dominated by males 00:12:55.299 --> 00:12:59.509 align:start position:0% it's still largely dominated by males which<00:12:56.110> make<00:12:56.289> up<00:12:56.610> 92%<00:12:57.610> of<00:12:57.759> the<00:12:57.879> user<00:12:58.059> base<00:12:58.299> and 00:12:59.509 --> 00:12:59.519 align:start position:0% which make up 92% of the user base and 00:12:59.519 --> 00:13:04.139 align:start position:0% which make up 92% of the user base and on<00:13:00.519> which<00:13:00.689> 50%<00:13:01.689> of<00:13:02.589> the<00:13:02.829> users<00:13:03.160> belong<00:13:03.879> to<00:13:04.029> the 00:13:04.139 --> 00:13:04.149 align:start position:0% on which 50% of the users belong to the 00:13:04.149 --> 00:13:09.169 align:start position:0% on which 50% of the users belong to the age<00:13:04.269> groups<00:13:04.600> of<00:13:04.839> 25<00:13:05.829> to<00:13:06.039> 34<00:13:06.459> years<00:13:06.669> of<00:13:06.759> age<00:13:07.980> and 00:13:09.169 --> 00:13:09.179 align:start position:0% age groups of 25 to 34 years of age and 00:13:09.179 --> 00:13:14.230 align:start position:0% age groups of 25 to 34 years of age and females<00:13:10.179> only<00:13:10.329> making<00:13:10.539> up<00:13:10.689> 8% 00:13:14.230 --> 00:13:14.240 align:start position:0% 00:13:14.240 --> 00:13:17.759 align:start position:0% and<00:13:14.449> looking<00:13:14.689> at<00:13:14.779> the<00:13:15.490> affinity<00:13:16.490> in<00:13:16.730> marker<00:13:17.119> um 00:13:17.759 --> 00:13:17.769 align:start position:0% and looking at the affinity in marker um 00:13:17.769 --> 00:13:20.499 align:start position:0% and looking at the affinity in marker um demographics<00:13:18.769> we<00:13:19.179> generally<00:13:20.179> see<00:13:20.360> this 00:13:20.499 --> 00:13:20.509 align:start position:0% demographics we generally see this 00:13:20.509 --> 00:13:23.499 align:start position:0% demographics we generally see this coming<00:13:20.929> from<00:13:21.110> users<00:13:21.699> with<00:13:22.699> interests<00:13:23.420> in 00:13:23.499 --> 00:13:23.509 align:start position:0% coming from users with interests in 00:13:23.509 --> 00:13:27.100 align:start position:0% coming from users with interests in areas<00:13:23.869> of<00:13:24.309> Technology<00:13:25.309> and<00:13:26.209> also<00:13:26.809> those 00:13:27.100 --> 00:13:27.110 align:start position:0% areas of Technology and also those 00:13:27.110 --> 00:13:30.009 align:start position:0% areas of Technology and also those interested<00:13:27.980> in<00:13:28.329> financial<00:13:29.329> and<00:13:29.720> investment 00:13:30.009 --> 00:13:30.019 align:start position:0% interested in financial and investment 00:13:30.019 --> 00:13:38.799 align:start position:0% interested in financial and investment services<00:13:34.929> so<00:13:35.929> for<00:13:35.959> the<00:13:36.860> user<00:13:37.480> interface<00:13:38.480> and 00:13:38.799 --> 00:13:38.809 align:start position:0% services so for the user interface and 00:13:38.809 --> 00:13:41.019 align:start position:0% services so for the user interface and ethics<00:13:39.290> we<00:13:39.740> look<00:13:40.009> at<00:13:40.129> two<00:13:40.249> data<00:13:40.429> points<00:13:40.519> which 00:13:41.019 --> 00:13:41.029 align:start position:0% ethics we look at two data points which 00:13:41.029 --> 00:13:43.629 align:start position:0% ethics we look at two data points which is<00:13:41.300> the<00:13:41.800> user<00:13:42.800> browser<00:13:43.129> and<00:13:43.429> screen 00:13:43.629 --> 00:13:43.639 align:start position:0% is the user browser and screen 00:13:43.639 --> 00:13:47.530 align:start position:0% is the user browser and screen resolutions<00:13:44.379> so<00:13:45.379> as<00:13:46.129> for<00:13:46.490> the<00:13:46.790> web<00:13:47.119> browser 00:13:47.530 --> 00:13:47.540 align:start position:0% resolutions so as for the web browser 00:13:47.540 --> 00:13:50.079 align:start position:0% resolutions so as for the web browser type<00:13:47.740> the<00:13:48.740> Chrome<00:13:49.040> browser<00:13:49.100> represents<00:13:49.970> the 00:13:50.079 --> 00:13:50.089 align:start position:0% type the Chrome browser represents the 00:13:50.089 --> 00:13:53.470 align:start position:0% type the Chrome browser represents the largest<00:13:50.869> share<00:13:51.050> at<00:13:51.199> 60%<00:13:51.639> followed<00:13:52.639> by<00:13:52.819> the 00:13:53.470 --> 00:13:53.480 align:start position:0% largest share at 60% followed by the 00:13:53.480 --> 00:13:57.730 align:start position:0% largest share at 60% followed by the Safari<00:13:53.959> and<00:13:54.439> Firefox<00:13:54.949> browser<00:13:56.439> and<00:13:57.439> as<00:13:57.529> for 00:13:57.730 --> 00:13:57.740 align:start position:0% Safari and Firefox browser and as for 00:13:57.740 --> 00:14:00.489 align:start position:0% Safari and Firefox browser and as for screen<00:13:58.399> resolutions<00:13:58.939> we<00:13:59.540> normally<00:13:59.809> see<00:13:59.959> users 00:14:00.489 --> 00:14:00.499 align:start position:0% screen resolutions we normally see users 00:14:00.499 --> 00:14:02.769 align:start position:0% screen resolutions we normally see users interacting<00:14:01.129> with<00:14:01.279> a<00:14:01.600> larger<00:14:02.600> screen 00:14:02.769 --> 00:14:02.779 align:start position:0% interacting with a larger screen 00:14:02.779 --> 00:14:04.600 align:start position:0% interacting with a larger screen resolutions<00:14:03.470> normally<00:14:03.829> indicating<00:14:04.519> a 00:14:04.600 --> 00:14:04.610 align:start position:0% resolutions normally indicating a 00:14:04.610 --> 00:14:09.540 align:start position:0% resolutions normally indicating a desktop<00:14:05.119> or<00:14:05.300> a<00:14:05.509> laptop<00:14:05.720> interface<00:14:08.019> so<00:14:09.019> for<00:14:09.259> the 00:14:09.540 --> 00:14:09.550 align:start position:0% desktop or a laptop interface so for the 00:14:09.550 --> 00:14:11.530 align:start position:0% desktop or a laptop interface so for the collaborating<00:14:10.550> the<00:14:10.639> screen<00:14:10.910> wrestle<00:14:11.300> and 00:14:11.530 --> 00:14:11.540 align:start position:0% collaborating the screen wrestle and 00:14:11.540 --> 00:14:14.079 align:start position:0% collaborating the screen wrestle and ethics<00:14:11.869> we<00:14:11.990> do<00:14:12.199> indeed<00:14:12.470> see<00:14:12.679> that<00:14:12.709> around<00:14:13.339> 2/3 00:14:14.079 --> 00:14:14.089 align:start position:0% ethics we do indeed see that around 2/3 00:14:14.089 --> 00:14:16.660 align:start position:0% ethics we do indeed see that around 2/3 of<00:14:14.119> the<00:14:14.300> users<00:14:14.600> are<00:14:14.839> indeed<00:14:15.259> using<00:14:15.559> a<00:14:16.069> desktop 00:14:16.660 --> 00:14:16.670 align:start position:0% of the users are indeed using a desktop 00:14:16.670 --> 00:14:19.239 align:start position:0% of the users are indeed using a desktop interface<00:14:17.269> and<00:14:17.839> around<00:14:18.259> 20%<00:14:18.559> of<00:14:18.889> remaining 00:14:19.239 --> 00:14:19.249 align:start position:0% interface and around 20% of remaining 00:14:19.249 --> 00:14:23.400 align:start position:0% interface and around 20% of remaining users<00:14:19.519> using<00:14:19.730> a<00:14:19.879> mobile<00:14:20.089> interface<00:14:22.209> for<00:14:23.209> the 00:14:23.400 --> 00:14:23.410 align:start position:0% users using a mobile interface for the 00:14:23.410 --> 00:14:26.470 align:start position:0% users using a mobile interface for the opening<00:14:24.410> systems<00:14:24.740> break<00:14:25.399> down<00:14:25.459> we<00:14:26.089> see<00:14:26.269> that 00:14:26.470 --> 00:14:26.480 align:start position:0% opening systems break down we see that 00:14:26.480 --> 00:14:31.090 align:start position:0% opening systems break down we see that around<00:14:26.869> half<00:14:27.350> the<00:14:27.589> users<00:14:27.980> or<00:14:28.249> 50%<00:14:29.889> using<00:14:30.889> the 00:14:31.090 --> 00:14:31.100 align:start position:0% around half the users or 50% using the 00:14:31.100 --> 00:14:33.759 align:start position:0% around half the users or 50% using the Windows<00:14:31.519> operating<00:14:31.759> system<00:14:32.619> followed<00:14:33.619> by 00:14:33.759 --> 00:14:33.769 align:start position:0% Windows operating system followed by 00:14:33.769 --> 00:14:38.679 align:start position:0% Windows operating system followed by Android<00:14:34.809> iOS<00:14:35.809> and<00:14:36.490> Macintosh<00:14:37.519> in<00:14:37.819> similar 00:14:38.679 --> 00:14:38.689 align:start position:0% Android iOS and Macintosh in similar 00:14:38.689 --> 00:14:42.280 align:start position:0% Android iOS and Macintosh in similar proportions<00:14:39.610> Linux<00:14:40.610> users<00:14:41.059> only<00:14:41.839> represent 00:14:42.280 --> 00:14:42.290 align:start position:0% proportions Linux users only represent 00:14:42.290 --> 00:14:47.139 align:start position:0% proportions Linux users only represent 3%<00:14:42.799> of<00:14:43.069> the<00:14:43.189> user<00:14:43.339> base<00:14:45.429> so<00:14:46.429> further<00:14:46.639> diving<00:14:47.029> to 00:14:47.139 --> 00:14:47.149 align:start position:0% 3% of the user base so further diving to 00:14:47.149 --> 00:14:49.030 align:start position:0% 3% of the user base so further diving to a<00:14:47.179> mobile<00:14:47.569> device<00:14:47.600> background<00:14:48.319> we<00:14:48.559> see<00:14:48.769> that 00:14:49.030 --> 00:14:49.040 align:start position:0% a mobile device background we see that 00:14:49.040 --> 00:14:52.869 align:start position:0% a mobile device background we see that as<00:14:49.279> a<00:14:49.699> single<00:14:50.660> device<00:14:50.959> type<00:14:51.319> the<00:14:52.069> Apple<00:14:52.670> iPhone 00:14:52.869 --> 00:14:52.879 align:start position:0% as a single device type the Apple iPhone 00:14:52.879 --> 00:14:54.660 align:start position:0% as a single device type the Apple iPhone commands<00:14:53.569> the<00:14:53.720> largest<00:14:54.230> market<00:14:54.559> share 00:14:54.660 --> 00:14:54.670 align:start position:0% commands the largest market share 00:14:54.670 --> 00:14:57.879 align:start position:0% commands the largest market share followed<00:14:55.670> at<00:14:56.059> 40<00:14:56.420> percent<00:14:56.569> followed<00:14:57.290> by<00:14:57.319> the 00:14:57.879 --> 00:14:57.889 align:start position:0% followed at 40 percent followed by the 00:14:57.889 --> 00:15:03.100 align:start position:0% followed at 40 percent followed by the Apple<00:14:58.129> iPad<00:14:58.429> and<00:14:58.670> Samsung<00:14:59.660> Galaxy<00:15:00.019> phones<00:15:02.110> all 00:15:03.100 --> 00:15:03.110 align:start position:0% Apple iPad and Samsung Galaxy phones all 00:15:03.110 --> 00:15:05.100 align:start position:0% Apple iPad and Samsung Galaxy phones all right<00:15:03.290> so<00:15:03.499> looking<00:15:03.949> at<00:15:04.100> the<00:15:04.369> previous 00:15:05.100 --> 00:15:05.110 align:start position:0% right so looking at the previous 00:15:05.110 --> 00:15:11.619 align:start position:0% right so looking at the previous analytics<00:15:06.110> data<00:15:08.290> our<00:15:09.369> derive<00:15:10.369> a<00:15:10.759> theorem<00:15:11.329> user 00:15:11.619 --> 00:15:11.629 align:start position:0% analytics data our derive a theorem user 00:15:11.629 --> 00:15:15.999 align:start position:0% analytics data our derive a theorem user would<00:15:12.079> most<00:15:12.290> likely<00:15:13.990> be<00:15:14.990> a<00:15:15.019> meal<00:15:15.350> from<00:15:15.889> the 00:15:15.999 --> 00:15:16.009 align:start position:0% would most likely be a meal from the 00:15:16.009 --> 00:15:18.269 align:start position:0% would most likely be a meal from the ages<00:15:16.309> of<00:15:16.339> 25<00:15:17.059> to<00:15:17.389> 34 00:15:18.269 --> 00:15:18.279 align:start position:0% ages of 25 to 34 00:15:18.279 --> 00:15:22.139 align:start position:0% ages of 25 to 34 located<00:15:19.279> in<00:15:19.429> the<00:15:19.999> US<00:15:20.360> China<00:15:20.869> or<00:15:21.230> Russia 00:15:22.139 --> 00:15:22.149 align:start position:0% located in the US China or Russia 00:15:22.149 --> 00:15:26.259 align:start position:0% located in the US China or Russia generally<00:15:23.149> tech<00:15:23.480> oriented<00:15:23.720> interests<00:15:25.269> and 00:15:26.259 --> 00:15:26.269 align:start position:0% generally tech oriented interests and 00:15:26.269 --> 00:15:28.060 align:start position:0% generally tech oriented interests and with<00:15:26.689> financial<00:15:27.410> services 00:15:28.060 --> 00:15:28.070 align:start position:0% with financial services 00:15:28.070 --> 00:15:31.390 align:start position:0% with financial services and<00:15:28.670> uses<00:15:29.030> a<00:15:29.270> windows-based<00:15:29.930> PC<00:15:30.710> and<00:15:30.950> Chrome 00:15:31.390 --> 00:15:31.400 align:start position:0% and uses a windows-based PC and Chrome 00:15:31.400 --> 00:15:34.090 align:start position:0% and uses a windows-based PC and Chrome as<00:15:31.640> the<00:15:31.850> primary<00:15:32.300> browser<00:15:32.510> and<00:15:33.140> you<00:15:33.950> all 00:15:34.090 --> 00:15:34.100 align:start position:0% as the primary browser and you all 00:15:34.100 --> 00:15:37.150 align:start position:0% as the primary browser and you all likelihood<00:15:34.520> either<00:15:34.880> owns<00:15:35.240> an<00:15:36.170> Apple<00:15:37.010> iPhone 00:15:37.150 --> 00:15:37.160 align:start position:0% likelihood either owns an Apple iPhone 00:15:37.160 --> 00:15:46.860 align:start position:0% likelihood either owns an Apple iPhone or<00:15:37.580> a<00:15:37.640> Samsung<00:15:38.330> mobile<00:15:38.570> device<00:15:44.920> okay<00:15:45.920> so<00:15:45.980> uh 00:15:46.860 --> 00:15:46.870 align:start position:0% or a Samsung mobile device okay so uh 00:15:46.870 --> 00:15:52.290 align:start position:0% or a Samsung mobile device okay so uh summing<00:15:47.870> up<00:15:47.990> so<00:15:48.290> where<00:15:48.440> are<00:15:48.530> we<00:15:48.560> today<00:15:50.470> we 00:15:52.290 --> 00:15:52.300 align:start position:0% summing up so where are we today we 00:15:52.300 --> 00:15:54.700 align:start position:0% summing up so where are we today we generally<00:15:53.300> feel<00:15:53.480> that<00:15:53.660> we<00:15:53.810> are<00:15:53.840> definitely 00:15:54.700 --> 00:15:54.710 align:start position:0% generally feel that we are definitely 00:15:54.710 --> 00:15:57.010 align:start position:0% generally feel that we are definitely very<00:15:54.890> early<00:15:55.400> stages<00:15:55.730> of<00:15:56.090> the<00:15:56.330> technology<00:15:56.840> and 00:15:57.010 --> 00:15:57.020 align:start position:0% very early stages of the technology and 00:15:57.020 --> 00:15:58.380 align:start position:0% very early stages of the technology and its<00:15:57.680> potential 00:15:58.380 --> 00:15:58.390 align:start position:0% its potential 00:15:58.390 --> 00:16:01.000 align:start position:0% its potential however<00:15:59.390> with<00:15:59.600> like<00:15:59.900> like<00:16:00.260> past<00:16:00.530> that<00:16:00.710> first 00:16:01.000 --> 00:16:01.010 align:start position:0% however with like like past that first 00:16:01.010 --> 00:16:04.630 align:start position:0% however with like like past that first wave<00:16:01.340> of<00:16:01.370> like<00:16:01.880> any<00:16:02.530> pure<00:16:03.590> early<00:16:03.890> adopters<00:16:04.340> or 00:16:04.630 --> 00:16:04.640 align:start position:0% wave of like any pure early adopters or 00:16:04.640 --> 00:16:06.520 align:start position:0% wave of like any pure early adopters or software<00:16:05.240> developers<00:16:05.690> or<00:16:05.900> like<00:16:06.110> hardcore 00:16:06.520 --> 00:16:06.530 align:start position:0% software developers or like hardcore 00:16:06.530 --> 00:16:09.090 align:start position:0% software developers or like hardcore techie<00:16:07.130> users<00:16:07.460> and<00:16:08.210> what<00:16:08.390> we're<00:16:08.540> seeing<00:16:08.720> now 00:16:09.090 --> 00:16:09.100 align:start position:0% techie users and what we're seeing now 00:16:09.100 --> 00:16:12.670 align:start position:0% techie users and what we're seeing now more<00:16:10.100> regular<00:16:10.550> users<00:16:10.940> so<00:16:11.930> in<00:16:12.080> large<00:16:12.320> part<00:16:12.590> we 00:16:12.670 --> 00:16:12.680 align:start position:0% more regular users so in large part we 00:16:12.680 --> 00:16:15.040 align:start position:0% more regular users so in large part we believe<00:16:12.890> this<00:16:13.070> is<00:16:13.250> perhaps<00:16:13.940> due<00:16:14.720> to<00:16:14.780> the 00:16:15.040 --> 00:16:15.050 align:start position:0% believe this is perhaps due to the 00:16:15.050 --> 00:16:17.140 align:start position:0% believe this is perhaps due to the recent<00:16:15.860> popularity<00:16:16.010> of<00:16:16.430> icos 00:16:17.140 --> 00:16:17.150 align:start position:0% recent popularity of icos 00:16:17.150 --> 00:16:20.050 align:start position:0% recent popularity of icos well<00:16:17.960> really<00:16:18.320> getting<00:16:18.590> a<00:16:18.650> lot<00:16:18.800> of<00:16:18.830> users<00:16:19.280> who 00:16:20.050 --> 00:16:20.060 align:start position:0% well really getting a lot of users who 00:16:20.060 --> 00:16:21.880 align:start position:0% well really getting a lot of users who don't<00:16:20.510> really<00:16:20.900> understand<00:16:21.260> what<00:16:21.440> blocked<00:16:21.740> in 00:16:21.880 --> 00:16:21.890 align:start position:0% don't really understand what blocked in 00:16:21.890 --> 00:16:24.610 align:start position:0% don't really understand what blocked in technologies<00:16:22.370> but<00:16:22.970> I<00:16:23.210> need<00:16:23.510> for<00:16:23.750> speculative 00:16:24.610 --> 00:16:24.620 align:start position:0% technologies but I need for speculative 00:16:24.620 --> 00:16:29.260 align:start position:0% technologies but I need for speculative investment<00:16:25.100> reasons<00:16:27.010> which<00:16:28.010> is<00:16:28.220> why<00:16:28.400> during 00:16:29.260 --> 00:16:29.270 align:start position:0% investment reasons which is why during 00:16:29.270 --> 00:16:31.720 align:start position:0% investment reasons which is why during this<00:16:29.360> stage<00:16:29.600> onboarding<00:16:30.440> and<00:16:30.650> user<00:16:31.580> education 00:16:31.720 --> 00:16:31.730 align:start position:0% this stage onboarding and user education 00:16:31.730 --> 00:16:33.610 align:start position:0% this stage onboarding and user education is<00:16:32.240> extremely<00:16:32.420> important<00:16:33.260> if<00:16:33.350> you<00:16:33.410> want<00:16:33.440> to 00:16:33.610 --> 00:16:33.620 align:start position:0% is extremely important if you want to 00:16:33.620 --> 00:16:36.480 align:start position:0% is extremely important if you want to continue<00:16:34.400> growing<00:16:34.490> the<00:16:34.730> ecosystem<00:16:35.300> so 00:16:36.480 --> 00:16:36.490 align:start position:0% continue growing the ecosystem so 00:16:36.490 --> 00:16:39.550 align:start position:0% continue growing the ecosystem so onboarding<00:16:37.490> regular<00:16:38.000> users<00:16:38.440> onto<00:16:39.440> the 00:16:39.550 --> 00:16:39.560 align:start position:0% onboarding regular users onto the 00:16:39.560 --> 00:16:42.600 align:start position:0% onboarding regular users onto the platform<00:16:40.070> through<00:16:40.400> better<00:16:40.790> user<00:16:41.090> interfaces 00:16:42.600 --> 00:16:42.610 align:start position:0% platform through better user interfaces 00:16:42.610 --> 00:16:45.310 align:start position:0% platform through better user interfaces education<00:16:43.610> and<00:16:44.150> while<00:16:44.300> providing<00:16:44.630> a<00:16:44.990> secure 00:16:45.310 --> 00:16:45.320 align:start position:0% education and while providing a secure 00:16:45.320 --> 00:16:50.710 align:start position:0% education and while providing a secure user<00:16:45.830> experience<00:16:46.280> is<00:16:46.460> critical<00:16:49.330> at<00:16:50.330> the<00:16:50.540> same 00:16:50.710 --> 00:16:50.720 align:start position:0% user experience is critical at the same 00:16:50.720 --> 00:16:54.220 align:start position:0% user experience is critical at the same time<00:16:51.040> we<00:16:52.040> are<00:16:52.670> actually<00:16:52.970> extremely<00:16:53.690> excited 00:16:54.220 --> 00:16:54.230 align:start position:0% time we are actually extremely excited 00:16:54.230 --> 00:16:57.130 align:start position:0% time we are actually extremely excited because<00:16:54.260> we<00:16:54.650> sort<00:16:55.040> of<00:16:55.160> can<00:16:55.700> see<00:16:55.970> the<00:16:56.020> pieces<00:16:57.020> of 00:16:57.130 --> 00:16:57.140 align:start position:0% because we sort of can see the pieces of 00:16:57.140 --> 00:17:00.130 align:start position:0% because we sort of can see the pieces of the<00:16:57.200> puzzle<00:16:57.320> coming<00:16:57.680> together<00:16:58.720> the<00:16:59.720> etherion 00:17:00.130 --> 00:17:00.140 align:start position:0% the puzzle coming together the etherion 00:17:00.140 --> 00:17:02.410 align:start position:0% the puzzle coming together the etherion protocol<00:17:00.590> continues<00:17:01.310> to<00:17:01.640> be<00:17:01.790> further 00:17:02.410 --> 00:17:02.420 align:start position:0% protocol continues to be further 00:17:02.420 --> 00:17:04.800 align:start position:0% protocol continues to be further developed<00:17:02.990> at<00:17:03.110> a<00:17:03.140> rapid<00:17:03.620> pace 00:17:04.800 --> 00:17:04.810 align:start position:0% developed at a rapid pace 00:17:04.810 --> 00:17:09.550 align:start position:0% developed at a rapid pace things<00:17:05.810> like<00:17:06.939> ens<00:17:07.939> ETA<00:17:08.329> Observatory<00:17:09.170> in<00:17:09.320> place 00:17:09.550 --> 00:17:09.560 align:start position:0% things like ens ETA Observatory in place 00:17:09.560 --> 00:17:14.110 align:start position:0% things like ens ETA Observatory in place today<00:17:09.740> and<00:17:09.949> in<00:17:10.280> use<00:17:10.550> and<00:17:11.329> then<00:17:12.100> both<00:17:13.120> response 00:17:14.110 --> 00:17:14.120 align:start position:0% today and in use and then both response 00:17:14.120 --> 00:17:16.390 align:start position:0% today and in use and then both response wom<00:17:14.449> will<00:17:14.750> fill<00:17:15.020> the<00:17:15.230> remaining<00:17:15.980> pieces<00:17:16.189> of 00:17:16.390 --> 00:17:16.400 align:start position:0% wom will fill the remaining pieces of 00:17:16.400 --> 00:17:18.130 align:start position:0% wom will fill the remaining pieces of storage<00:17:16.730> and<00:17:16.970> communication<00:17:17.209> to<00:17:17.810> form<00:17:18.020> the 00:17:18.130 --> 00:17:18.140 align:start position:0% storage and communication to form the 00:17:18.140 --> 00:17:22.240 align:start position:0% storage and communication to form the next<00:17:18.439> distributed<00:17:18.890> web<00:17:18.980> built<00:17:19.250> on<00:17:19.430> interim<00:17:21.250> so 00:17:22.240 --> 00:17:22.250 align:start position:0% next distributed web built on interim so 00:17:22.250 --> 00:17:24.370 align:start position:0% next distributed web built on interim so an<00:17:22.579> ether<00:17:22.820> scan<00:17:23.120> will<00:17:23.300> do<00:17:23.510> what<00:17:24.079> we've<00:17:24.290> always 00:17:24.370 --> 00:17:24.380 align:start position:0% an ether scan will do what we've always 00:17:24.380 --> 00:17:26.500 align:start position:0% an ether scan will do what we've always done<00:17:24.560> which<00:17:25.010> is<00:17:25.160> actually<00:17:25.520> which<00:17:25.820> is<00:17:25.850> to 00:17:26.500 --> 00:17:26.510 align:start position:0% done which is actually which is to 00:17:26.510 --> 00:17:28.960 align:start position:0% done which is actually which is to continue<00:17:27.110> to<00:17:27.140> push<00:17:27.410> forward<00:17:27.790> at<00:17:28.790> the 00:17:28.960 --> 00:17:28.970 align:start position:0% continue to push forward at the 00:17:28.970 --> 00:17:33.160 align:start position:0% continue to push forward at the background<00:17:30.250> while<00:17:31.250> continuing<00:17:32.090> to<00:17:32.330> expand 00:17:33.160 --> 00:17:33.170 align:start position:0% background while continuing to expand 00:17:33.170 --> 00:17:35.530 align:start position:0% background while continuing to expand our<00:17:33.350> search<00:17:33.620> for<00:17:33.830> content<00:17:34.280> for<00:17:34.540> distributed 00:17:35.530 --> 00:17:35.540 align:start position:0% our search for content for distributed 00:17:35.540 --> 00:17:40.030 align:start position:0% our search for content for distributed protocols<00:17:36.940> ladies<00:17:37.940> and<00:17:38.060> gentlemen<00:17:38.980> thank<00:17:39.980> you 00:17:40.030 --> 00:17:40.040 align:start position:0% protocols ladies and gentlemen thank you 00:17:40.040 --> 00:17:52.620 align:start position:0% protocols ladies and gentlemen thank you for<00:17:40.100> exploring<00:17:40.490> the<00:17:40.700> interlocutors 00:17:52.620 --> 00:17:52.630 align:start position:0% 00:17:52.630 --> 00:18:00.209 align:start position:0% [Music]