WEBVTT Kind: captions Language: en 00:00:04.380 --> 00:00:07.670 align:start position:0% so<00:00:05.040> hi<00:00:05.250> my<00:00:06.029> name<00:00:06.210> is<00:00:06.240> Bob<00:00:06.479> some<00:00:06.720> oil<00:00:06.870> I'm<00:00:07.109> the 00:00:07.670 --> 00:00:07.680 align:start position:0% so hi my name is Bob some oil I'm the 00:00:07.680 --> 00:00:09.949 align:start position:0% so hi my name is Bob some oil I'm the executive<00:00:08.430> director<00:00:08.460> of<00:00:08.940> the<00:00:09.330> etherium 00:00:09.949 --> 00:00:09.959 align:start position:0% executive director of the etherium 00:00:09.959 --> 00:00:13.519 align:start position:0% executive director of the etherium classic<00:00:10.530> cooperative<00:00:11.280> I<00:00:12.320> been<00:00:13.320> in<00:00:13.440> that 00:00:13.519 --> 00:00:13.529 align:start position:0% classic cooperative I been in that 00:00:13.529 --> 00:00:16.820 align:start position:0% classic cooperative I been in that position<00:00:13.709> since<00:00:14.219> January<00:00:14.779> I<00:00:15.830> previously 00:00:16.820 --> 00:00:16.830 align:start position:0% position since January I previously 00:00:16.830 --> 00:00:21.770 align:start position:0% position since January I previously worked<00:00:17.730> at<00:00:18.510> the<00:00:18.690> foundation<00:00:19.410> at<00:00:19.740> consensus<00:00:20.780> on 00:00:21.770 --> 00:00:21.780 align:start position:0% worked at the foundation at consensus on 00:00:21.780 --> 00:00:23.990 align:start position:0% worked at the foundation at consensus on the<00:00:22.350> enterprise<00:00:22.800> aetherium<00:00:23.310> Alliance<00:00:23.730> where 00:00:23.990 --> 00:00:24.000 align:start position:0% the enterprise aetherium Alliance where 00:00:24.000 --> 00:00:26.270 align:start position:0% the enterprise aetherium Alliance where I<00:00:24.030> work<00:00:24.420> for<00:00:24.660> the<00:00:24.720> set<00:00:24.900> up<00:00:25.050> of<00:00:25.200> that<00:00:25.410> and<00:00:25.800> then<00:00:26.010> I 00:00:26.270 --> 00:00:26.280 align:start position:0% I work for the set up of that and then I 00:00:26.280 --> 00:00:29.900 align:start position:0% I work for the set up of that and then I was<00:00:26.880> the<00:00:27.090> the<00:00:27.890> co-lead<00:00:28.890> architect<00:00:29.460> during 00:00:29.900 --> 00:00:29.910 align:start position:0% was the the co-lead architect during 00:00:29.910 --> 00:00:32.689 align:start position:0% was the the co-lead architect during that<00:00:30.030> set<00:00:30.330> up<00:00:30.510> and<00:00:30.869> then<00:00:30.990> I<00:00:31.110> was<00:00:31.260> the<00:00:31.699> secretary 00:00:32.689 --> 00:00:32.699 align:start position:0% that set up and then I was the secretary 00:00:32.699 --> 00:00:34.819 align:start position:0% that set up and then I was the secretary of<00:00:33.149> their<00:00:33.270> technical<00:00:33.570> working<00:00:33.809> group<00:00:34.199> and<00:00:34.410> the 00:00:34.819 --> 00:00:34.829 align:start position:0% of their technical working group and the 00:00:34.829 --> 00:00:39.979 align:start position:0% of their technical working group and the vice<00:00:34.980> chair<00:00:35.309> of<00:00:35.340> the<00:00:35.539> the<00:00:36.539> TSC<00:00:38.059> and<00:00:39.059> I've<00:00:39.480> done 00:00:39.979 --> 00:00:39.989 align:start position:0% vice chair of the the TSC and I've done 00:00:39.989 --> 00:00:41.750 align:start position:0% vice chair of the the TSC and I've done stuff<00:00:40.230> in<00:00:40.379> in<00:00:40.710> hyper<00:00:40.920> lecture<00:00:41.219> as<00:00:41.339> well 00:00:41.750 --> 00:00:41.760 align:start position:0% stuff in in hyper lecture as well 00:00:41.760 --> 00:00:47.779 align:start position:0% stuff in in hyper lecture as well and<00:00:42.379> and<00:00:43.379> now<00:00:43.559> I<00:00:43.589> find<00:00:43.920> myself<00:00:43.949> in<00:00:44.280> classic<00:00:46.789> so 00:00:47.779 --> 00:00:47.789 align:start position:0% and and now I find myself in classic so 00:00:47.789 --> 00:00:49.250 align:start position:0% and and now I find myself in classic so I've<00:00:48.089> just<00:00:48.149> said<00:00:48.479> a<00:00:48.510> little<00:00:48.690> bit<00:00:48.809> about<00:00:48.989> what 00:00:49.250 --> 00:00:49.260 align:start position:0% I've just said a little bit about what 00:00:49.260 --> 00:00:52.369 align:start position:0% I've just said a little bit about what what<00:00:49.530> what's<00:00:49.889> been<00:00:50.069> happening<00:00:51.050> we<00:00:52.050> really 00:00:52.369 --> 00:00:52.379 align:start position:0% what what's been happening we really 00:00:52.379 --> 00:00:57.829 align:start position:0% what what's been happening we really have<00:00:52.670> a<00:00:53.670> a<00:00:54.659> resurgence<00:00:55.969> within<00:00:56.969> classic<00:00:57.659> right 00:00:57.829 --> 00:00:57.839 align:start position:0% have a a resurgence within classic right 00:00:57.839 --> 00:01:03.020 align:start position:0% have a a resurgence within classic right now<00:00:58.049> where<00:00:59.010> after<00:00:59.309> several<00:00:59.879> years<00:01:00.780> of<00:01:02.030> fairly 00:01:03.020 --> 00:01:03.030 align:start position:0% now where after several years of fairly 00:01:03.030 --> 00:01:05.990 align:start position:0% now where after several years of fairly inactive<00:01:03.769> kind<00:01:04.769> of<00:01:04.920> status 00:01:05.990 --> 00:01:06.000 align:start position:0% inactive kind of status 00:01:06.000 --> 00:01:08.749 align:start position:0% inactive kind of status we've<00:01:06.570> got<00:01:06.750> forward<00:01:07.049> movement<00:01:07.350> again<00:01:07.759> you 00:01:08.749 --> 00:01:08.759 align:start position:0% we've got forward movement again you 00:01:08.759 --> 00:01:10.700 align:start position:0% we've got forward movement again you know<00:01:08.880> you<00:01:08.939> had<00:01:09.210> the<00:01:09.390> you<00:01:09.990> had<00:01:10.140> the<00:01:10.289> split<00:01:10.560> at 00:01:10.700 --> 00:01:10.710 align:start position:0% know you had the you had the split at 00:01:10.710 --> 00:01:13.580 align:start position:0% know you had the you had the split at the<00:01:10.799> dow<00:01:10.950> fork<00:01:11.450> there<00:01:12.450> was<00:01:12.570> the<00:01:12.780> the<00:01:13.200> monetary 00:01:13.580 --> 00:01:13.590 align:start position:0% the dow fork there was the the monetary 00:01:13.590 --> 00:01:16.340 align:start position:0% the dow fork there was the the monetary policy<00:01:13.799> change<00:01:14.310> and<00:01:14.990> disabling<00:01:15.990> of<00:01:16.079> the<00:01:16.170> bomb 00:01:16.340 --> 00:01:16.350 align:start position:0% policy change and disabling of the bomb 00:01:16.350 --> 00:01:19.249 align:start position:0% policy change and disabling of the bomb and<00:01:16.680> then<00:01:17.159> that<00:01:17.880> was<00:01:18.030> about<00:01:18.240> what<00:01:18.479> what<00:01:19.170> had 00:01:19.249 --> 00:01:19.259 align:start position:0% and then that was about what what had 00:01:19.259 --> 00:01:24.770 align:start position:0% and then that was about what what had happened<00:01:21.259> but<00:01:22.259> what's<00:01:22.469> changed<00:01:23.070> is<00:01:23.280> is<00:01:24.270> really 00:01:24.770 --> 00:01:24.780 align:start position:0% happened but what's changed is is really 00:01:24.780 --> 00:01:29.090 align:start position:0% happened but what's changed is is really that<00:01:25.710> we<00:01:25.799> have<00:01:25.950> funding<00:01:26.369> now<00:01:27.020> that<00:01:28.020> with<00:01:28.170> etc' 00:01:29.090 --> 00:01:29.100 align:start position:0% that we have funding now that with etc' 00:01:29.100 --> 00:01:34.929 align:start position:0% that we have funding now that with etc' labs<00:01:30.229> we<00:01:31.229> we<00:01:31.859> have<00:01:33.049> effectively<00:01:34.049> unlike<00:01:34.469> a 00:01:34.929 --> 00:01:34.939 align:start position:0% labs we we have effectively unlike a 00:01:34.939 --> 00:01:40.310 align:start position:0% labs we we have effectively unlike a joseph<00:01:35.939> Lubin<00:01:36.390> for<00:01:36.840> classic<00:01:38.420> so<00:01:39.420> the<00:01:40.170> way<00:01:40.289> i 00:01:40.310 --> 00:01:40.320 align:start position:0% joseph Lubin for classic so the way i 00:01:40.320 --> 00:01:42.260 align:start position:0% joseph Lubin for classic so the way i describe<00:01:40.439> things<00:01:41.070> is<00:01:41.280> very<00:01:41.340> much<00:01:41.640> like<00:01:41.880> things 00:01:42.260 --> 00:01:42.270 align:start position:0% describe things is very much like things 00:01:42.270 --> 00:01:46.459 align:start position:0% describe things is very much like things were<00:01:42.479> in<00:01:43.049> in<00:01:43.950> aetherium<00:01:44.460> land<00:01:44.670> in<00:01:44.880> 2015<00:01:45.600> if 00:01:46.459 --> 00:01:46.469 align:start position:0% were in in aetherium land in 2015 if 00:01:46.469 --> 00:01:48.020 align:start position:0% were in in aetherium land in 2015 if you've<00:01:46.619> got<00:01:46.799> a<00:01:46.829> good<00:01:46.979> project<00:01:47.399> idea<00:01:47.700> you<00:01:47.880> have 00:01:48.020 --> 00:01:48.030 align:start position:0% you've got a good project idea you have 00:01:48.030 --> 00:01:49.340 align:start position:0% you've got a good project idea you have some<00:01:48.240> money<00:01:48.329> you<00:01:48.420> have<00:01:48.719> some<00:01:48.869> money<00:01:48.960> you<00:01:49.079> have 00:01:49.340 --> 00:01:49.350 align:start position:0% some money you have some money you have 00:01:49.350 --> 00:01:56.179 align:start position:0% some money you have some money you have some<00:01:49.530> money<00:01:52.039> so<00:01:53.039> we're<00:01:53.850> moving<00:01:53.969> and<00:01:54.649> the<00:01:55.649> the 00:01:56.179 --> 00:01:56.189 align:start position:0% some money so we're moving and the the 00:01:56.189 --> 00:01:58.639 align:start position:0% some money so we're moving and the the most<00:01:56.719> recent<00:01:57.719> and<00:01:57.899> big<00:01:58.020> thing<00:01:58.259> that<00:01:58.380> we<00:01:58.469> had 00:01:58.639 --> 00:01:58.649 align:start position:0% most recent and big thing that we had 00:01:58.649 --> 00:02:02.330 align:start position:0% most recent and big thing that we had was<00:01:58.890> Atlantis<00:01:59.820> so<00:02:00.630> Atlantis<00:02:01.380> was<00:02:01.829> our<00:02:02.100> first 00:02:02.330 --> 00:02:02.340 align:start position:0% was Atlantis so Atlantis was our first 00:02:02.340 --> 00:02:06.709 align:start position:0% was Atlantis so Atlantis was our first hard<00:02:02.819> fork<00:02:03.149> for<00:02:03.649> quite<00:02:04.649> a<00:02:04.679> long<00:02:04.890> time<00:02:05.159> and<00:02:05.719> and 00:02:06.709 --> 00:02:06.719 align:start position:0% hard fork for quite a long time and and 00:02:06.719 --> 00:02:09.620 align:start position:0% hard fork for quite a long time and and what<00:02:06.960> happened<00:02:07.350> there<00:02:07.530> was<00:02:08.100> that<00:02:08.490> we<00:02:08.819> we 00:02:09.620 --> 00:02:09.630 align:start position:0% what happened there was that we we 00:02:09.630 --> 00:02:14.240 align:start position:0% what happened there was that we we fought<00:02:09.899> in<00:02:10.640> Byzantium<00:02:11.640> opcodes<00:02:12.710> so<00:02:13.710> classic 00:02:14.240 --> 00:02:14.250 align:start position:0% fought in Byzantium opcodes so classic 00:02:14.250 --> 00:02:18.350 align:start position:0% fought in Byzantium opcodes so classic is<00:02:14.370> now<00:02:15.230> not<00:02:16.230> very<00:02:16.560> far<00:02:16.890> behind 00:02:18.350 --> 00:02:18.360 align:start position:0% is now not very far behind 00:02:18.360 --> 00:02:24.700 align:start position:0% is now not very far behind ETH<00:02:21.500> so<00:02:22.500> for<00:02:22.770> Atlantis<00:02:23.250> we<00:02:23.430> had<00:02:23.670> three<00:02:24.240> clients 00:02:24.700 --> 00:02:24.710 align:start position:0% ETH so for Atlantis we had three clients 00:02:24.710 --> 00:02:30.920 align:start position:0% ETH so for Atlantis we had three clients with<00:02:25.710> support<00:02:26.780> that's<00:02:28.700> multi<00:02:29.700> goth<00:02:29.880> which<00:02:30.780> is 00:02:30.920 --> 00:02:30.930 align:start position:0% with support that's multi goth which is 00:02:30.930 --> 00:02:36.230 align:start position:0% with support that's multi goth which is a<00:02:30.960> downstream<00:02:31.910> of<00:02:32.910> the<00:02:33.660> foundation<00:02:34.230> gap<00:02:35.240> we 00:02:36.230 --> 00:02:36.240 align:start position:0% a downstream of the foundation gap we 00:02:36.240 --> 00:02:40.640 align:start position:0% a downstream of the foundation gap we had<00:02:36.420> classic<00:02:37.050> death<00:02:37.260> which<00:02:38.190> is<00:02:38.220> a<00:02:39.650> very 00:02:40.640 --> 00:02:40.650 align:start position:0% had classic death which is a very 00:02:40.650 --> 00:02:43.100 align:start position:0% had classic death which is a very ancient<00:02:41.240> code<00:02:42.240> base<00:02:42.480> which<00:02:42.720> was<00:02:42.870> basically 00:02:43.100 --> 00:02:43.110 align:start position:0% ancient code base which was basically 00:02:43.110 --> 00:02:46.640 align:start position:0% ancient code base which was basically forged<00:02:43.590> at<00:02:43.860> the<00:02:44.010> time<00:02:44.220> of<00:02:44.400> the<00:02:44.490> Dow<00:02:45.200> and<00:02:46.200> then 00:02:46.640 --> 00:02:46.650 align:start position:0% forged at the time of the Dow and then 00:02:46.650 --> 00:02:48.260 align:start position:0% forged at the time of the Dow and then cobble<00:02:46.980> along<00:02:47.250> for<00:02:47.610> a<00:02:47.640> little<00:02:47.850> bit<00:02:47.970> further 00:02:48.260 --> 00:02:48.270 align:start position:0% cobble along for a little bit further 00:02:48.270 --> 00:02:53.660 align:start position:0% cobble along for a little bit further but<00:02:49.260> is<00:02:49.860> essentially<00:02:51.410> in<00:02:52.410> deprecation<00:02:53.370> state 00:02:53.660 --> 00:02:53.670 align:start position:0% but is essentially in deprecation state 00:02:53.670 --> 00:02:55.850 align:start position:0% but is essentially in deprecation state so<00:02:54.360> classic<00:02:54.810> death<00:02:54.990> is<00:02:55.170> not<00:02:55.350> going<00:02:55.500> to<00:02:55.560> make<00:02:55.710> it 00:02:55.850 --> 00:02:55.860 align:start position:0% so classic death is not going to make it 00:02:55.860 --> 00:02:58.790 align:start position:0% so classic death is not going to make it to<00:02:55.980> the<00:02:56.070> next<00:02:56.250> fork<00:02:56.550> it's<00:02:57.330> going<00:02:57.540> to<00:02:57.630> be<00:02:57.750> a<00:02:57.800> a 00:02:58.790 --> 00:02:58.800 align:start position:0% to the next fork it's going to be a a 00:02:58.800 --> 00:03:02.180 align:start position:0% to the next fork it's going to be a a happy<00:02:59.700> retirement<00:03:00.150> for<00:03:00.690> classic<00:03:01.020> death<00:03:01.260> as<00:03:01.980> we 00:03:02.180 --> 00:03:02.190 align:start position:0% happy retirement for classic death as we 00:03:02.190 --> 00:03:05.030 align:start position:0% happy retirement for classic death as we clap<00:03:02.970> it<00:03:03.180> clap<00:03:03.900> it<00:03:04.020> into<00:03:04.290> retirement<00:03:04.620> for<00:03:04.920> its 00:03:05.030 --> 00:03:05.040 align:start position:0% clap it clap it into retirement for its 00:03:05.040 --> 00:03:10.010 align:start position:0% clap it clap it into retirement for its service<00:03:05.459> but<00:03:05.780> it's<00:03:06.780> time<00:03:07.050> is<00:03:07.200> over<00:03:08.420> parity<00:03:09.420> has 00:03:10.010 --> 00:03:10.020 align:start position:0% service but it's time is over parity has 00:03:10.020 --> 00:03:13.760 align:start position:0% service but it's time is over parity has had<00:03:10.580> support<00:03:11.580> for<00:03:11.850> both<00:03:11.970> ET<00:03:12.660> c<00:03:13.050> and<00:03:13.290> e<00:03:13.440> th 00:03:13.760 --> 00:03:13.770 align:start position:0% had support for both ET c and e th 00:03:13.770 --> 00:03:18.670 align:start position:0% had support for both ET c and e th throughout<00:03:14.640> so<00:03:15.540> that's<00:03:15.750> not<00:03:16.350> a<00:03:16.380> problem<00:03:17.360> and 00:03:18.670 --> 00:03:18.680 align:start position:0% throughout so that's not a problem and 00:03:18.680 --> 00:03:21.260 align:start position:0% throughout so that's not a problem and and<00:03:19.680> those<00:03:19.830> are<00:03:19.890> the<00:03:20.190> the<00:03:20.400> three<00:03:20.610> code<00:03:20.820> bases 00:03:21.260 --> 00:03:21.270 align:start position:0% and those are the the three code bases 00:03:21.270 --> 00:03:26.140 align:start position:0% and those are the the three code bases that<00:03:21.450> we've<00:03:21.570> had<00:03:21.750> for<00:03:22.350> atlantis<00:03:22.830> the<00:03:24.320> other 00:03:26.140 --> 00:03:26.150 align:start position:0% that we've had for atlantis the other 00:03:26.150 --> 00:03:28.490 align:start position:0% that we've had for atlantis the other primary<00:03:27.150> code<00:03:27.510> base<00:03:27.750> that<00:03:27.989> there<00:03:28.110> is<00:03:28.230> on 00:03:28.490 --> 00:03:28.500 align:start position:0% primary code base that there is on 00:03:28.500 --> 00:03:32.870 align:start position:0% primary code base that there is on classic<00:03:29.250> is<00:03:30.150> mantis<00:03:30.690> which<00:03:31.650> is<00:03:31.890> from<00:03:32.130> io<00:03:32.430> HK 00:03:32.870 --> 00:03:32.880 align:start position:0% classic is mantis which is from io HK 00:03:32.880 --> 00:03:37.690 align:start position:0% classic is mantis which is from io HK now<00:03:33.840> at<00:03:34.230> the<00:03:34.380> time<00:03:34.620> that<00:03:36.080> classic<00:03:37.080> started 00:03:37.690 --> 00:03:37.700 align:start position:0% now at the time that classic started 00:03:37.700 --> 00:03:42.740 align:start position:0% now at the time that classic started charles<00:03:38.700> Hoskinson<00:03:39.950> returned<00:03:41.720> into<00:03:42.720> the 00:03:42.740 --> 00:03:42.750 align:start position:0% charles Hoskinson returned into the 00:03:42.750 --> 00:03:45.640 align:start position:0% charles Hoskinson returned into the classic<00:03:43.260> side<00:03:43.530> and<00:03:43.830> and<00:03:44.040> said<00:03:44.370> that<00:03:45.180> as<00:03:45.450> a 00:03:45.640 --> 00:03:45.650 align:start position:0% classic side and and said that as a 00:03:45.650 --> 00:03:48.080 align:start position:0% classic side and and said that as a aetherium<00:03:46.650> founder<00:03:47.190> he<00:03:47.459> helped<00:03:47.730> you<00:03:47.940> know 00:03:48.080 --> 00:03:48.090 align:start position:0% aetherium founder he helped you know 00:03:48.090 --> 00:03:52.610 align:start position:0% aetherium founder he helped you know felt<00:03:48.450> a<00:03:48.750> responsibility<00:03:49.640> to<00:03:50.810> support<00:03:51.810> the<00:03:52.350> the 00:03:52.610 --> 00:03:52.620 align:start position:0% felt a responsibility to support the the 00:03:52.620 --> 00:03:55.910 align:start position:0% felt a responsibility to support the the original<00:03:53.100> vision<00:03:53.280> that<00:03:53.519> he<00:03:53.640> felt<00:03:53.910> that<00:03:54.920> that 00:03:55.910 --> 00:03:55.920 align:start position:0% original vision that he felt that that 00:03:55.920 --> 00:03:57.740 align:start position:0% original vision that he felt that that really<00:03:56.160> he<00:03:56.310> should<00:03:56.340> he<00:03:57.000> should<00:03:57.030> get<00:03:57.269> involved 00:03:57.740 --> 00:03:57.750 align:start position:0% really he should he should get involved 00:03:57.750 --> 00:04:01.490 align:start position:0% really he should he should get involved and<00:03:57.930> help<00:03:58.350> out<00:03:58.560> so<00:03:59.519> he<00:03:59.730> hired<00:04:00.030> a<00:04:00.500> community 00:04:01.490 --> 00:04:01.500 align:start position:0% and help out so he hired a community 00:04:01.500 --> 00:04:04.610 align:start position:0% and help out so he hired a community manager<00:04:02.120> and<00:04:03.120> he<00:04:03.600> funded 00:04:04.610 --> 00:04:04.620 align:start position:0% manager and he funded 00:04:04.620 --> 00:04:08.630 align:start position:0% manager and he funded let's<00:04:05.130> talk<00:04:05.340> ECC<00:04:05.850> podcast<00:04:06.600> as<00:04:06.930> well<00:04:07.489> and<00:04:08.489> also 00:04:08.630 --> 00:04:08.640 align:start position:0% let's talk ECC podcast as well and also 00:04:08.640 --> 00:04:12.130 align:start position:0% let's talk ECC podcast as well and also Kevin<00:04:08.970> Lord<00:04:09.300> has<00:04:09.510> done<00:04:10.580> social<00:04:11.580> media<00:04:11.880> and 00:04:12.130 --> 00:04:12.140 align:start position:0% Kevin Lord has done social media and 00:04:12.140 --> 00:04:15.280 align:start position:0% Kevin Lord has done social media and sort<00:04:13.140> of<00:04:13.230> outreach<00:04:13.500> bits<00:04:13.950> and<00:04:14.100> pieces<00:04:14.250> as<00:04:14.549> well 00:04:15.280 --> 00:04:15.290 align:start position:0% sort of outreach bits and pieces as well 00:04:15.290 --> 00:04:20.060 align:start position:0% sort of outreach bits and pieces as well but<00:04:16.290> they<00:04:16.470> spent<00:04:17.000> two<00:04:18.000> years<00:04:18.030> building<00:04:19.019> a<00:04:19.830> new 00:04:20.060 --> 00:04:20.070 align:start position:0% but they spent two years building a new 00:04:20.070 --> 00:04:24.980 align:start position:0% but they spent two years building a new code<00:04:20.310> base<00:04:20.519> in<00:04:20.880> Scala<00:04:21.680> which<00:04:22.700> is<00:04:23.750> one<00:04:24.750> of<00:04:24.780> the 00:04:24.980 --> 00:04:24.990 align:start position:0% code base in Scala which is one of the 00:04:24.990 --> 00:04:27.650 align:start position:0% code base in Scala which is one of the the<00:04:25.350> turist<00:04:25.890> they're<00:04:26.850> implants<00:04:27.390> that<00:04:27.539> there 00:04:27.650 --> 00:04:27.660 align:start position:0% the turist they're implants that there 00:04:27.660 --> 00:04:30.409 align:start position:0% the turist they're implants that there is<00:04:27.780> and<00:04:28.050> apparently<00:04:28.979> is<00:04:29.160> also<00:04:29.520> the<00:04:29.820> lowest 00:04:30.409 --> 00:04:30.419 align:start position:0% is and apparently is also the lowest 00:04:30.419 --> 00:04:31.900 align:start position:0% is and apparently is also the lowest memory<00:04:30.960> footprint<00:04:31.350> and<00:04:31.620> highest 00:04:31.900 --> 00:04:31.910 align:start position:0% memory footprint and highest 00:04:31.910 --> 00:04:34.450 align:start position:0% memory footprint and highest performance<00:04:32.470> but<00:04:33.470> nobody<00:04:33.800> is<00:04:33.920> really<00:04:33.950> aware 00:04:34.450 --> 00:04:34.460 align:start position:0% performance but nobody is really aware 00:04:34.460 --> 00:04:34.990 align:start position:0% performance but nobody is really aware of<00:04:34.490> it 00:04:34.990 --> 00:04:35.000 align:start position:0% of it 00:04:35.000 --> 00:04:37.780 align:start position:0% of it within<00:04:35.810> the<00:04:36.200> broader<00:04:36.440> aetherium<00:04:37.100> ecosystem 00:04:37.780 --> 00:04:37.790 align:start position:0% within the broader aetherium ecosystem 00:04:37.790 --> 00:04:40.300 align:start position:0% within the broader aetherium ecosystem because<00:04:37.880> it's<00:04:38.180> been<00:04:38.330> a<00:04:38.360> classic<00:04:38.660> only<00:04:39.350> client 00:04:40.300 --> 00:04:40.310 align:start position:0% because it's been a classic only client 00:04:40.310 --> 00:04:43.750 align:start position:0% because it's been a classic only client so<00:04:41.240> nobody<00:04:41.570> nobody<00:04:42.080> knows<00:04:42.260> about<00:04:42.530> it 00:04:43.750 --> 00:04:43.760 align:start position:0% so nobody nobody knows about it 00:04:43.760 --> 00:04:47.890 align:start position:0% so nobody nobody knows about it work<00:04:44.180> started<00:04:44.960> on<00:04:45.080> that<00:04:45.230> codebase<00:04:45.710> to<00:04:45.920> add<00:04:46.900> ETH 00:04:47.890 --> 00:04:47.900 align:start position:0% work started on that codebase to add ETH 00:04:47.900 --> 00:04:50.800 align:start position:0% work started on that codebase to add ETH support<00:04:48.440> as<00:04:48.680> well<00:04:49.300> but<00:04:50.300> that<00:04:50.510> team 00:04:50.800 --> 00:04:50.810 align:start position:0% support as well but that team 00:04:50.810 --> 00:04:53.710 align:start position:0% support as well but that team essentially<00:04:51.470> got<00:04:51.790> source<00:04:52.790> of<00:04:52.940> defunded<00:04:53.570> and 00:04:53.710 --> 00:04:53.720 align:start position:0% essentially got source of defunded and 00:04:53.720 --> 00:04:57.040 align:start position:0% essentially got source of defunded and slowed<00:04:54.440> down<00:04:54.680> and<00:04:54.890> stopped<00:04:55.280> as<00:04:55.610> of<00:04:56.420> December 00:04:57.040 --> 00:04:57.050 align:start position:0% slowed down and stopped as of December 00:04:57.050 --> 00:05:00.070 align:start position:0% slowed down and stopped as of December of<00:04:57.170> last<00:04:57.200> year<00:04:57.670> really<00:04:58.670> with<00:04:59.080> Charles 00:05:00.070 --> 00:05:00.080 align:start position:0% of last year really with Charles 00:05:00.080 --> 00:05:02.790 align:start position:0% of last year really with Charles refocusing<00:05:00.920> his<00:05:01.040> efforts<00:05:01.370> on<00:05:01.700> kadhai<00:05:02.420> know 00:05:02.790 --> 00:05:02.800 align:start position:0% refocusing his efforts on kadhai know 00:05:02.800 --> 00:05:06.190 align:start position:0% refocusing his efforts on kadhai know and<00:05:03.800> really<00:05:04.130> sort<00:05:04.610> of<00:05:04.760> half<00:05:04.970> exiting<00:05:05.720> the<00:05:05.900> the 00:05:06.190 --> 00:05:06.200 align:start position:0% and really sort of half exiting the the 00:05:06.200 --> 00:05:10.980 align:start position:0% and really sort of half exiting the the classic<00:05:07.060> ecosystem<00:05:08.060> because<00:05:08.390> of<00:05:09.910> continual 00:05:10.980 --> 00:05:10.990 align:start position:0% classic ecosystem because of continual 00:05:10.990 --> 00:05:15.610 align:start position:0% classic ecosystem because of continual infighting<00:05:11.990> and<00:05:12.110> really<00:05:12.440> feeling<00:05:12.860> that<00:05:14.620> he 00:05:15.610 --> 00:05:15.620 align:start position:0% infighting and really feeling that he 00:05:15.620 --> 00:05:16.960 align:start position:0% infighting and really feeling that he couldn't<00:05:15.920> do<00:05:16.100> the<00:05:16.130> interesting<00:05:16.730> things 00:05:16.960 --> 00:05:16.970 align:start position:0% couldn't do the interesting things 00:05:16.970 --> 00:05:19.330 align:start position:0% couldn't do the interesting things within<00:05:17.210> classic<00:05:17.690> but<00:05:17.870> he<00:05:17.960> wanted<00:05:18.290> to<00:05:18.350> you<00:05:19.310> know 00:05:19.330 --> 00:05:19.340 align:start position:0% within classic but he wanted to you know 00:05:19.340 --> 00:05:21.880 align:start position:0% within classic but he wanted to you know he<00:05:19.610> can<00:05:19.730> he<00:05:19.820> sort<00:05:20.060> of<00:05:20.120> said<00:05:20.390> if<00:05:20.660> if<00:05:20.930> classic<00:05:21.740> is 00:05:21.880 --> 00:05:21.890 align:start position:0% he can he sort of said if if classic is 00:05:21.890 --> 00:05:26.020 align:start position:0% he can he sort of said if if classic is just<00:05:22.160> the<00:05:22.310> litecoin<00:05:22.850> of<00:05:23.030> etherium<00:05:24.760> who<00:05:25.760> wants 00:05:26.020 --> 00:05:26.030 align:start position:0% just the litecoin of etherium who wants 00:05:26.030 --> 00:05:31.120 align:start position:0% just the litecoin of etherium who wants to<00:05:26.150> do<00:05:26.270> that<00:05:27.490> anyway<00:05:29.080> we<00:05:30.080> recently<00:05:30.290> had<00:05:30.710> the 00:05:31.120 --> 00:05:31.130 align:start position:0% to do that anyway we recently had the 00:05:31.130 --> 00:05:34.900 align:start position:0% to do that anyway we recently had the etherium<00:05:32.090> classic<00:05:32.450> summit<00:05:32.930> in<00:05:33.680> vancouver<00:05:34.370> my 00:05:34.900 --> 00:05:34.910 align:start position:0% etherium classic summit in vancouver my 00:05:34.910 --> 00:05:40.690 align:start position:0% etherium classic summit in vancouver my hometown<00:05:35.270> of<00:05:35.300> Vancouver<00:05:35.830> and<00:05:37.300> Charles<00:05:39.700> close 00:05:40.690 --> 00:05:40.700 align:start position:0% hometown of Vancouver and Charles close 00:05:40.700 --> 00:05:42.340 align:start position:0% hometown of Vancouver and Charles close to<00:05:40.910> the<00:05:41.000> end<00:05:41.150> only<00:05:41.750> a<00:05:41.780> few<00:05:41.960> weeks<00:05:42.110> to<00:05:42.200> come 00:05:42.340 --> 00:05:42.350 align:start position:0% to the end only a few weeks to come 00:05:42.350 --> 00:05:44.140 align:start position:0% to the end only a few weeks to come finally<00:05:42.650> agreed<00:05:43.460> that<00:05:43.640> he<00:05:43.760> would<00:05:43.880> come<00:05:44.030> and 00:05:44.140 --> 00:05:44.150 align:start position:0% finally agreed that he would come and 00:05:44.150 --> 00:05:47.500 align:start position:0% finally agreed that he would come and speak<00:05:44.330> so<00:05:45.260> Charles<00:05:45.650> had<00:05:46.190> the<00:05:46.460> the<00:05:47.120> closing 00:05:47.500 --> 00:05:47.510 align:start position:0% speak so Charles had the the closing 00:05:47.510 --> 00:05:53.560 align:start position:0% speak so Charles had the the closing keynote<00:05:48.190> and<00:05:49.190> through<00:05:49.990> the<00:05:51.340> conference<00:05:52.340> we<00:05:52.570> we 00:05:53.560 --> 00:05:53.570 align:start position:0% keynote and through the conference we we 00:05:53.570 --> 00:05:55.750 align:start position:0% keynote and through the conference we we basically<00:05:53.720> like<00:05:54.200> romanced<00:05:54.800> him<00:05:54.950> back<00:05:55.160> in<00:05:55.370> a 00:05:55.750 --> 00:05:55.760 align:start position:0% basically like romanced him back in a 00:05:55.760 --> 00:05:59.710 align:start position:0% basically like romanced him back in a charmed<00:05:56.630> in<00:05:56.750> back<00:05:56.960> in<00:05:57.610> and<00:05:58.610> and<00:05:59.090> really<00:05:59.570> what's 00:05:59.710 --> 00:05:59.720 align:start position:0% charmed in back in and and really what's 00:05:59.720 --> 00:06:01.750 align:start position:0% charmed in back in and and really what's gonna<00:05:59.840> happen<00:06:00.260> there<00:06:00.470> is<00:06:00.650> that<00:06:00.830> you<00:06:01.490> know<00:06:01.520> that 00:06:01.750 --> 00:06:01.760 align:start position:0% gonna happen there is that you know that 00:06:01.760 --> 00:06:03.520 align:start position:0% gonna happen there is that you know that code<00:06:01.970> base<00:06:02.120> is<00:06:02.330> going<00:06:02.480> to<00:06:02.540> be<00:06:02.690> is<00:06:03.140> gonna<00:06:03.320> be 00:06:03.520 --> 00:06:03.530 align:start position:0% code base is going to be is gonna be 00:06:03.530 --> 00:06:06.490 align:start position:0% code base is going to be is gonna be revived<00:06:03.890> so<00:06:04.460> as<00:06:05.090> we<00:06:05.300> go<00:06:05.480> into<00:06:05.660> our<00:06:05.810> forthcoming 00:06:06.490 --> 00:06:06.500 align:start position:0% revived so as we go into our forthcoming 00:06:06.500 --> 00:06:10.510 align:start position:0% revived so as we go into our forthcoming hard<00:06:07.460> Forks<00:06:08.140> mantis<00:06:09.140> should<00:06:09.380> be<00:06:09.560> added<00:06:10.370> into 00:06:10.510 --> 00:06:10.520 align:start position:0% hard Forks mantis should be added into 00:06:10.520 --> 00:06:13.900 align:start position:0% hard Forks mantis should be added into the<00:06:10.700> set<00:06:11.000> of<00:06:11.180> of<00:06:11.419> clients<00:06:11.960> they're<00:06:12.169> so<00:06:12.910> classic 00:06:13.900 --> 00:06:13.910 align:start position:0% the set of of clients they're so classic 00:06:13.910 --> 00:06:16.650 align:start position:0% the set of of clients they're so classic death<00:06:14.060> will<00:06:14.300> be<00:06:14.419> retired<00:06:14.900> and<00:06:15.230> you<00:06:15.980> will<00:06:16.130> have 00:06:16.650 --> 00:06:16.660 align:start position:0% death will be retired and you will have 00:06:16.660 --> 00:06:22.180 align:start position:0% death will be retired and you will have death<00:06:18.130> and<00:06:19.130> you<00:06:19.340> will<00:06:19.490> have<00:06:19.700> parity<00:06:20.980> and<00:06:21.980> you 00:06:22.180 --> 00:06:22.190 align:start position:0% death and you will have parity and you 00:06:22.190 --> 00:06:23.710 align:start position:0% death and you will have parity and you will<00:06:22.310> you<00:06:22.640> will<00:06:22.700> have<00:06:22.760> mantas<00:06:23.270> coming<00:06:23.540> in<00:06:23.630> as 00:06:23.710 --> 00:06:23.720 align:start position:0% will you will have mantas coming in as 00:06:23.720 --> 00:06:27.250 align:start position:0% will you will have mantas coming in as well<00:06:23.900> but<00:06:24.800> not<00:06:24.980> just<00:06:25.280> that<00:06:25.990> you<00:06:26.990> will<00:06:27.110> also 00:06:27.250 --> 00:06:27.260 align:start position:0% well but not just that you will also 00:06:27.260 --> 00:06:32.050 align:start position:0% well but not just that you will also have<00:06:28.390> hyper<00:06:29.390> ledger<00:06:29.780> Bisou<00:06:30.700> now<00:06:31.700> you<00:06:31.760> may<00:06:31.970> have 00:06:32.050 --> 00:06:32.060 align:start position:0% have hyper ledger Bisou now you may have 00:06:32.060 --> 00:06:35.710 align:start position:0% have hyper ledger Bisou now you may have heard<00:06:32.120> of<00:06:32.570> Bisou<00:06:33.470> so<00:06:34.370> BZ<00:06:34.760> was<00:06:34.940> previously 00:06:35.710 --> 00:06:35.720 align:start position:0% heard of Bisou so BZ was previously 00:06:35.720 --> 00:06:40.060 align:start position:0% heard of Bisou so BZ was previously called<00:06:35.990> Pantheon<00:06:36.620> and<00:06:38.380> where<00:06:39.380> that<00:06:39.620> code<00:06:39.890> base 00:06:40.060 --> 00:06:40.070 align:start position:0% called Pantheon and where that code base 00:06:40.070 --> 00:06:42.909 align:start position:0% called Pantheon and where that code base has<00:06:40.280> come<00:06:40.520> from<00:06:40.729> is<00:06:41.380> when<00:06:42.380> I<00:06:42.410> was<00:06:42.650> involved 00:06:42.909 --> 00:06:42.919 align:start position:0% has come from is when I was involved 00:06:42.919 --> 00:06:45.400 align:start position:0% has come from is when I was involved with<00:06:43.419> setting<00:06:44.419> up<00:06:44.539> the<00:06:44.630> Enterprise<00:06:44.990> a<00:06:45.020> theory 00:06:45.400 --> 00:06:45.410 align:start position:0% with setting up the Enterprise a theory 00:06:45.410 --> 00:06:45.760 align:start position:0% with setting up the Enterprise a theory Malaya 00:06:45.760 --> 00:06:45.770 align:start position:0% Malaya 00:06:45.770 --> 00:06:49.390 align:start position:0% Malaya myself<00:06:46.190> and<00:06:46.960> Jehan<00:06:47.960> were<00:06:48.889> the<00:06:49.009> co-lead 00:06:49.390 --> 00:06:49.400 align:start position:0% myself and Jehan were the co-lead 00:06:49.400 --> 00:06:52.749 align:start position:0% myself and Jehan were the co-lead architects<00:06:50.060> and<00:06:50.210> we<00:06:50.300> did<00:06:50.509> the<00:06:51.280> the<00:06:52.280> tech<00:06:52.520> talk 00:06:52.749 --> 00:06:52.759 align:start position:0% architects and we did the the tech talk 00:06:52.759 --> 00:06:57.040 align:start position:0% architects and we did the the tech talk at<00:06:53.270> the<00:06:53.389> launch<00:06:53.539> event<00:06:53.740> at<00:06:54.740> which<00:06:55.069> I<00:06:55.400> I<00:06:55.550> said<00:06:56.150> so 00:06:57.040 --> 00:06:57.050 align:start position:0% at the launch event at which I I said so 00:06:57.050 --> 00:07:00.010 align:start position:0% at the launch event at which I I said so sure<00:06:57.289> hon<00:06:57.560> is<00:06:57.949> the<00:06:58.250> distributed<00:06:59.000> systems<00:06:59.389> PhD 00:07:00.010 --> 00:07:00.020 align:start position:0% sure hon is the distributed systems PhD 00:07:00.020 --> 00:07:04.869 align:start position:0% sure hon is the distributed systems PhD and<00:07:01.009> I'm<00:07:01.250> the<00:07:01.430> cheerleader<00:07:02.979> so<00:07:03.979> he<00:07:04.220> basically 00:07:04.869 --> 00:07:04.879 align:start position:0% and I'm the cheerleader so he basically 00:07:04.879 --> 00:07:07.240 align:start position:0% and I'm the cheerleader so he basically then<00:07:05.300> has<00:07:05.599> spent<00:07:05.840> the<00:07:05.990> last<00:07:06.020> two<00:07:06.409> years<00:07:06.440> back 00:07:07.240 --> 00:07:07.250 align:start position:0% then has spent the last two years back 00:07:07.250 --> 00:07:10.659 align:start position:0% then has spent the last two years back inside<00:07:07.900> consensus<00:07:08.979> building<00:07:09.979> a<00:07:10.190> new<00:07:10.430> code 00:07:10.659 --> 00:07:10.669 align:start position:0% inside consensus building a new code 00:07:10.669 --> 00:07:14.399 align:start position:0% inside consensus building a new code base<00:07:10.879> from<00:07:11.599> scratch<00:07:12.340> so<00:07:13.340> that<00:07:13.550> is 00:07:14.399 --> 00:07:14.409 align:start position:0% base from scratch so that is 00:07:14.409 --> 00:07:19.439 align:start position:0% base from scratch so that is permissively<00:07:15.409> licensed<00:07:15.919> patchy<00:07:16.909> to<00:07:17.830> it<00:07:18.830> is 00:07:19.439 --> 00:07:19.449 align:start position:0% permissively licensed patchy to it is 00:07:19.449 --> 00:07:24.820 align:start position:0% permissively licensed patchy to it is written<00:07:20.449> in<00:07:20.630> Java<00:07:21.789> and<00:07:22.789> it<00:07:23.419> is<00:07:23.659> a<00:07:24.050> theory<00:07:24.530> main 00:07:24.820 --> 00:07:24.830 align:start position:0% written in Java and it is a theory main 00:07:24.830 --> 00:07:28.330 align:start position:0% written in Java and it is a theory main that<00:07:24.979> compatible<00:07:25.630> also<00:07:26.630> supports<00:07:27.050> cleek<00:07:27.380> also 00:07:28.330 --> 00:07:28.340 align:start position:0% that compatible also supports cleek also 00:07:28.340 --> 00:07:32.230 align:start position:0% that compatible also supports cleek also supports<00:07:28.849> system<00:07:29.830> Istanbul<00:07:30.830> BFT<00:07:31.370> also 00:07:32.230 --> 00:07:32.240 align:start position:0% supports system Istanbul BFT also 00:07:32.240 --> 00:07:34.659 align:start position:0% supports system Istanbul BFT also supports<00:07:32.690> privacy<00:07:33.380> features<00:07:33.830> and<00:07:34.069> is<00:07:34.490> also 00:07:34.659 --> 00:07:34.669 align:start position:0% supports privacy features and is also 00:07:34.669 --> 00:07:38.260 align:start position:0% supports privacy features and is also compliant<00:07:35.389> with<00:07:35.539> the<00:07:35.690> EA<00:07:36.069> specification<00:07:37.270> so 00:07:38.260 --> 00:07:38.270 align:start position:0% compliant with the EA specification so 00:07:38.270 --> 00:07:41.320 align:start position:0% compliant with the EA specification so it's<00:07:38.419> really<00:07:38.810> like<00:07:39.370> it's<00:07:40.370> all<00:07:40.699> of<00:07:40.909> the<00:07:41.060> stuff 00:07:41.320 --> 00:07:41.330 align:start position:0% it's really like it's all of the stuff 00:07:41.330 --> 00:07:43.749 align:start position:0% it's really like it's all of the stuff it's<00:07:42.020> all<00:07:42.199> of<00:07:42.349> the<00:07:42.440> good<00:07:42.620> stuff<00:07:42.650> and<00:07:43.340> it's<00:07:43.550> and 00:07:43.749 --> 00:07:43.759 align:start position:0% it's all of the good stuff and it's and 00:07:43.759 --> 00:07:44.980 align:start position:0% it's all of the good stuff and it's and it's<00:07:43.849> really<00:07:44.180> something<00:07:44.389> that<00:07:44.569> we've<00:07:44.810> been 00:07:44.980 --> 00:07:44.990 align:start position:0% it's really something that we've been 00:07:44.990 --> 00:07:46.659 align:start position:0% it's really something that we've been striving<00:07:45.349> for<00:07:45.710> I<00:07:45.740> think<00:07:46.009> for<00:07:46.129> about<00:07:46.219> three 00:07:46.659 --> 00:07:46.669 align:start position:0% striving for I think for about three 00:07:46.669 --> 00:07:51.129 align:start position:0% striving for I think for about three years<00:07:46.699> is<00:07:47.360> to<00:07:47.960> get<00:07:48.199> to<00:07:48.680> you<00:07:49.340> know<00:07:49.460> a<00:07:49.900> very<00:07:50.900> high 00:07:51.129 --> 00:07:51.139 align:start position:0% years is to get to you know a very high 00:07:51.139 --> 00:07:54.159 align:start position:0% years is to get to you know a very high quality<00:07:51.409> code<00:07:51.919> base<00:07:52.190> in<00:07:52.699> a<00:07:53.270> language<00:07:53.690> which<00:07:53.930> is 00:07:54.159 --> 00:07:54.169 align:start position:0% quality code base in a language which is 00:07:54.169 --> 00:07:59.830 align:start position:0% quality code base in a language which is you<00:07:54.710> know<00:07:55.300> broadly<00:07:56.300> used<00:07:57.699> under<00:07:58.699> that<00:07:59.360> kind<00:07:59.750> of 00:07:59.830 --> 00:07:59.840 align:start position:0% you know broadly used under that kind of 00:07:59.840 --> 00:08:01.450 align:start position:0% you know broadly used under that kind of Licensing<00:08:00.500> and<00:08:00.650> governance<00:08:01.009> within<00:08:01.250> the 00:08:01.450 --> 00:08:01.460 align:start position:0% Licensing and governance within the 00:08:01.460 --> 00:08:04.059 align:start position:0% Licensing and governance within the Linux<00:08:01.759> Foundation<00:08:01.880> which<00:08:02.710> basically<00:08:03.710> lets 00:08:04.059 --> 00:08:04.069 align:start position:0% Linux Foundation which basically lets 00:08:04.069 --> 00:08:06.450 align:start position:0% Linux Foundation which basically lets large<00:08:04.940> enterprises<00:08:05.539> come<00:08:06.020> and<00:08:06.139> engage 00:08:06.450 --> 00:08:06.460 align:start position:0% large enterprises come and engage 00:08:06.460 --> 00:08:08.800 align:start position:0% large enterprises come and engage because<00:08:07.460> I<00:08:07.580> think<00:08:07.789> really<00:08:08.090> what<00:08:08.360> you<00:08:08.479> want<00:08:08.659> to 00:08:08.800 --> 00:08:08.810 align:start position:0% because I think really what you want to 00:08:08.810 --> 00:08:11.379 align:start position:0% because I think really what you want to have<00:08:09.050> with<00:08:10.009> aetherium<00:08:10.520> clients<00:08:11.060> is<00:08:11.210> is 00:08:11.379 --> 00:08:11.389 align:start position:0% have with aetherium clients is is 00:08:11.389 --> 00:08:13.450 align:start position:0% have with aetherium clients is is something<00:08:11.810> like<00:08:12.050> you<00:08:12.500> know<00:08:12.620> Linux<00:08:13.009> kernel 00:08:13.450 --> 00:08:13.460 align:start position:0% something like you know Linux kernel 00:08:13.460 --> 00:08:15.640 align:start position:0% something like you know Linux kernel kind<00:08:13.729> of<00:08:13.849> model<00:08:14.150> that<00:08:14.930> you<00:08:15.050> know<00:08:15.169> you<00:08:15.229> start 00:08:15.640 --> 00:08:15.650 align:start position:0% kind of model that you know you start 00:08:15.650 --> 00:08:17.409 align:start position:0% kind of model that you know you start out<00:08:15.889> well<00:08:16.130> hey<00:08:16.279> here's<00:08:16.610> a<00:08:16.669> project<00:08:17.120> just<00:08:17.330> for 00:08:17.409 --> 00:08:17.419 align:start position:0% out well hey here's a project just for 00:08:17.419 --> 00:08:21.010 align:start position:0% out well hey here's a project just for fun<00:08:18.039> but<00:08:19.039> then<00:08:19.250> things<00:08:19.759> get<00:08:19.969> serious<00:08:20.479> and<00:08:20.690> and 00:08:21.010 --> 00:08:21.020 align:start position:0% fun but then things get serious and and 00:08:21.020 --> 00:08:24.040 align:start position:0% fun but then things get serious and and and<00:08:21.349> and<00:08:22.190> and<00:08:22.580> basically<00:08:23.029> enterprises<00:08:23.750> start 00:08:24.040 --> 00:08:24.050 align:start position:0% and and and basically enterprises start 00:08:24.050 --> 00:08:25.749 align:start position:0% and and and basically enterprises start depending<00:08:24.590> on<00:08:24.680> that<00:08:24.830> stuff<00:08:25.159> and<00:08:25.310> they<00:08:25.430> start 00:08:25.749 --> 00:08:25.759 align:start position:0% depending on that stuff and they start 00:08:25.759 --> 00:08:28.149 align:start position:0% depending on that stuff and they start picking<00:08:26.090> up<00:08:26.330> the<00:08:26.389> load<00:08:26.630> you<00:08:27.469> know<00:08:27.590> so<00:08:27.800> you<00:08:27.860> see 00:08:28.149 --> 00:08:28.159 align:start position:0% picking up the load you know so you see 00:08:28.159 --> 00:08:30.550 align:start position:0% picking up the load you know so you see the<00:08:28.909> Linux<00:08:29.090> kernel<00:08:29.419> you<00:08:30.110> know<00:08:30.229> the<00:08:30.380> major 00:08:30.550 --> 00:08:30.560 align:start position:0% the Linux kernel you know the major 00:08:30.560 --> 00:08:34.120 align:start position:0% the Linux kernel you know the major contributors<00:08:31.370> are<00:08:32.829> you<00:08:33.829> know<00:08:33.950> they're 00:08:34.120 --> 00:08:34.130 align:start position:0% contributors are you know they're 00:08:34.130 --> 00:08:36.339 align:start position:0% contributors are you know they're they're<00:08:34.339> big<00:08:34.880> companies<00:08:35.329> that<00:08:35.599> that<00:08:36.140> have<00:08:36.320> a 00:08:36.339 --> 00:08:36.349 align:start position:0% they're big companies that that have a 00:08:36.349 --> 00:08:39.100 align:start position:0% they're big companies that that have a need<00:08:36.589> for<00:08:36.800> that<00:08:36.919> because<00:08:37.789> really<00:08:38.329> what<00:08:38.959> you 00:08:39.100 --> 00:08:39.110 align:start position:0% need for that because really what you 00:08:39.110 --> 00:08:41.050 align:start position:0% need for that because really what you want<00:08:39.349> is<00:08:39.560> is<00:08:39.890> you<00:08:40.190> want<00:08:40.370> these<00:08:40.520> big<00:08:40.700> companies 00:08:41.050 --> 00:08:41.060 align:start position:0% want is is you want these big companies 00:08:41.060 --> 00:08:42.519 align:start position:0% want is is you want these big companies to<00:08:41.180> be<00:08:41.419> doing<00:08:41.690> you<00:08:42.020> know<00:08:42.050> carrying<00:08:42.409> the 00:08:42.519 --> 00:08:42.529 align:start position:0% to be doing you know carrying the 00:08:42.529 --> 00:08:44.800 align:start position:0% to be doing you know carrying the engineering<00:08:43.039> load<00:08:43.219> you<00:08:44.089> know<00:08:44.209> you<00:08:44.270> can't<00:08:44.570> have 00:08:44.800 --> 00:08:44.810 align:start position:0% engineering load you know you can't have 00:08:44.810 --> 00:08:46.720 align:start position:0% engineering load you know you can't have the<00:08:45.079> get<00:08:45.440> a<00:08:45.470> team<00:08:45.770> with<00:08:45.950> four<00:08:46.160> or<00:08:46.279> five<00:08:46.430> people 00:08:46.720 --> 00:08:46.730 align:start position:0% the get a team with four or five people 00:08:46.730 --> 00:08:47.920 align:start position:0% the get a team with four or five people carrying<00:08:47.209> the<00:08:47.329> weight<00:08:47.420> of<00:08:47.570> the<00:08:47.630> world<00:08:47.810> on 00:08:47.920 --> 00:08:47.930 align:start position:0% carrying the weight of the world on 00:08:47.930 --> 00:08:49.630 align:start position:0% carrying the weight of the world on their<00:08:48.079> back<00:08:48.230> forever<00:08:48.560> like<00:08:49.070> that<00:08:49.250> just<00:08:49.490> isn't 00:08:49.630 --> 00:08:49.640 align:start position:0% their back forever like that just isn't 00:08:49.640 --> 00:08:50.290 align:start position:0% their back forever like that just isn't going<00:08:49.790> to<00:08:49.880> work 00:08:50.290 --> 00:08:50.300 align:start position:0% going to work 00:08:50.300 --> 00:08:52.269 align:start position:0% going to work you<00:08:50.660> need<00:08:50.810> large<00:08:51.079> professional<00:08:51.380> teams<00:08:51.980> and 00:08:52.269 --> 00:08:52.279 align:start position:0% you need large professional teams and 00:08:52.279 --> 00:08:55.210 align:start position:0% you need large professional teams and that's<00:08:52.370> really<00:08:52.730> what<00:08:53.029> started<00:08:53.860> with<00:08:54.860> with 00:08:55.210 --> 00:08:55.220 align:start position:0% that's really what started with with 00:08:55.220 --> 00:08:58.840 align:start position:0% that's really what started with with Pantheon<00:08:55.640> so<00:08:56.630> what<00:08:57.320> the<00:08:57.470> classic<00:08:57.860> cooperative 00:08:58.840 --> 00:08:58.850 align:start position:0% Pantheon so what the classic cooperative 00:08:58.850 --> 00:08:59.630 align:start position:0% Pantheon so what the classic cooperative is<00:08:58.970> doing<00:08:59.300> is 00:08:59.630 --> 00:08:59.640 align:start position:0% is doing is 00:08:59.640 --> 00:09:04.100 align:start position:0% is doing is is<00:08:59.730> we<00:09:00.000> are<00:09:00.120> funding<00:09:01.010> et<00:09:02.010> Cie<00:09:02.370> support<00:09:02.790> in<00:09:03.779> in 00:09:04.100 --> 00:09:04.110 align:start position:0% is we are funding et Cie support in in 00:09:04.110 --> 00:09:06.590 align:start position:0% is we are funding et Cie support in in baizhu<00:09:04.670> and<00:09:05.670> it's<00:09:05.820> the<00:09:05.910> very<00:09:06.089> first<00:09:06.300> thing 00:09:06.590 --> 00:09:06.600 align:start position:0% baizhu and it's the very first thing 00:09:06.600 --> 00:09:09.050 align:start position:0% baizhu and it's the very first thing that's<00:09:06.810> happening<00:09:07.200> within<00:09:08.010> that<00:09:08.519> code<00:09:08.820> being 00:09:09.050 --> 00:09:09.060 align:start position:0% that's happening within that code being 00:09:09.060 --> 00:09:12.139 align:start position:0% that's happening within that code being within<00:09:09.269> hi<00:09:09.959> pleasure<00:09:10.350> so<00:09:11.040> very<00:09:11.459> soon<00:09:11.760> what<00:09:12.060> you 00:09:12.139 --> 00:09:12.149 align:start position:0% within hi pleasure so very soon what you 00:09:12.149 --> 00:09:17.630 align:start position:0% within hi pleasure so very soon what you will<00:09:12.269> have<00:09:12.450> is<00:09:12.779> a<00:09:13.560> client<00:09:14.279> which<00:09:14.670> can<00:09:14.940> run<00:09:16.640> if 00:09:17.630 --> 00:09:17.640 align:start position:0% will have is a client which can run if 00:09:17.640 --> 00:09:20.079 align:start position:0% will have is a client which can run if they're<00:09:17.850> in<00:09:17.970> Maine<00:09:18.180> that<00:09:18.209> et<00:09:18.959> Cie<00:09:19.170> Maine<00:09:19.410> that 00:09:20.079 --> 00:09:20.089 align:start position:0% they're in Maine that et Cie Maine that 00:09:20.089 --> 00:09:23.540 align:start position:0% they're in Maine that et Cie Maine that kotti<00:09:21.089> Galli<00:09:21.750> or<00:09:22.410> any<00:09:22.890> of<00:09:23.010> these<00:09:23.130> private 00:09:23.540 --> 00:09:23.550 align:start position:0% kotti Galli or any of these private 00:09:23.550 --> 00:09:26.840 align:start position:0% kotti Galli or any of these private scenarios<00:09:24.980> so<00:09:25.980> chain<00:09:26.250> say<00:09:26.430> for<00:09:26.610> doing<00:09:26.760> the 00:09:26.840 --> 00:09:26.850 align:start position:0% scenarios so chain say for doing the 00:09:26.850 --> 00:09:30.500 align:start position:0% scenarios so chain say for doing the work<00:09:26.880> who<00:09:28.160> did<00:09:29.160> the<00:09:29.279> work<00:09:29.430> on<00:09:29.640> classic<00:09:30.060> to<00:09:30.390> get 00:09:30.500 --> 00:09:30.510 align:start position:0% work who did the work on classic to get 00:09:30.510 --> 00:09:33.319 align:start position:0% work who did the work on classic to get that<00:09:30.660> working<00:09:30.810> for<00:09:31.079> Atlantis<00:09:31.560> now<00:09:31.970> to<00:09:32.970> work<00:09:33.149> on 00:09:33.319 --> 00:09:33.329 align:start position:0% that working for Atlantis now to work on 00:09:33.329 --> 00:09:34.910 align:start position:0% that working for Atlantis now to work on hyper<00:09:33.600> ledger<00:09:33.810> code<00:09:34.050> bases<00:09:34.470> you<00:09:34.560> don't<00:09:34.740> have 00:09:34.910 --> 00:09:34.920 align:start position:0% hyper ledger code bases you don't have 00:09:34.920 --> 00:09:36.500 align:start position:0% hyper ledger code bases you don't have to<00:09:35.070> be<00:09:35.160> a<00:09:35.190> hyper<00:09:35.430> ledger<00:09:35.640> member<00:09:36.000> anyone<00:09:36.360> can 00:09:36.500 --> 00:09:36.510 align:start position:0% to be a hyper ledger member anyone can 00:09:36.510 --> 00:09:40.009 align:start position:0% to be a hyper ledger member anyone can work<00:09:36.660> on<00:09:36.870> those<00:09:37.019> but<00:09:38.329> we<00:09:39.329> love<00:09:39.510> fly<00:09:39.630> pledges 00:09:40.009 --> 00:09:40.019 align:start position:0% work on those but we love fly pledges 00:09:40.019 --> 00:09:41.210 align:start position:0% work on those but we love fly pledges that<00:09:40.050> we<00:09:40.230> joined<00:09:40.410> Hydra<00:09:40.680> Ledger<00:09:40.860> as<00:09:41.010> well 00:09:41.210 --> 00:09:41.220 align:start position:0% that we joined Hydra Ledger as well 00:09:41.220 --> 00:09:45.050 align:start position:0% that we joined Hydra Ledger as well we're<00:09:41.670> applying<00:09:41.880> to<00:09:43.250> so<00:09:44.250> hyper<00:09:44.490> ledger<00:09:44.760> for 00:09:45.050 --> 00:09:45.060 align:start position:0% we're applying to so hyper ledger for 00:09:45.060 --> 00:09:46.690 align:start position:0% we're applying to so hyper ledger for anyone<00:09:45.300> that<00:09:45.420> doesn't<00:09:45.480> know<00:09:45.720> is<00:09:46.230> a 00:09:46.690 --> 00:09:46.700 align:start position:0% anyone that doesn't know is a 00:09:46.700 --> 00:09:49.699 align:start position:0% anyone that doesn't know is a collaboration<00:09:47.700> project<00:09:48.089> within<00:09:48.959> the<00:09:49.410> Linux 00:09:49.699 --> 00:09:49.709 align:start position:0% collaboration project within the Linux 00:09:49.709 --> 00:09:53.300 align:start position:0% collaboration project within the Linux Foundation<00:09:50.420> which<00:09:51.420> is<00:09:51.450> an<00:09:51.779> umbrella<00:09:52.320> for<00:09:53.250> a 00:09:53.300 --> 00:09:53.310 align:start position:0% Foundation which is an umbrella for a 00:09:53.310 --> 00:09:55.130 align:start position:0% Foundation which is an umbrella for a set<00:09:53.610> of<00:09:53.790> open-source<00:09:54.570> blockchain 00:09:55.130 --> 00:09:55.140 align:start position:0% set of open-source blockchain 00:09:55.140 --> 00:09:58.430 align:start position:0% set of open-source blockchain technologies<00:09:55.790> so<00:09:56.790> hyper<00:09:57.600> ledger<00:09:57.810> fabric<00:09:58.320> is 00:09:58.430 --> 00:09:58.440 align:start position:0% technologies so hyper ledger fabric is 00:09:58.440 --> 00:09:59.690 align:start position:0% technologies so hyper ledger fabric is the<00:09:58.560> one<00:09:58.680> that<00:09:58.740> you<00:09:58.829> hear<00:09:59.010> about<00:09:59.040> all<00:09:59.250> the<00:09:59.519> time 00:09:59.690 --> 00:09:59.700 align:start position:0% the one that you hear about all the time 00:09:59.700 --> 00:10:01.819 align:start position:0% the one that you hear about all the time that<00:09:59.730> originally<00:10:00.300> came<00:10:00.329> from<00:10:00.510> IBM<00:10:01.170> the 00:10:01.819 --> 00:10:01.829 align:start position:0% that originally came from IBM the 00:10:01.829 --> 00:10:04.100 align:start position:0% that originally came from IBM the Sawtooth<00:10:02.370> that<00:10:02.640> originally<00:10:03.000> came<00:10:03.029> from<00:10:03.209> Intel 00:10:04.100 --> 00:10:04.110 align:start position:0% Sawtooth that originally came from Intel 00:10:04.110 --> 00:10:09.019 align:start position:0% Sawtooth that originally came from Intel you<00:10:04.709> have<00:10:04.890> borrow<00:10:05.550> which<00:10:06.540> is<00:10:06.779> an<00:10:06.959> EVM<00:10:07.790> but<00:10:08.790> not 00:10:09.019 --> 00:10:09.029 align:start position:0% you have borrow which is an EVM but not 00:10:09.029 --> 00:10:10.880 align:start position:0% you have borrow which is an EVM but not main<00:10:09.269> net<00:10:09.510> compatible<00:10:10.140> that<00:10:10.320> was<00:10:10.410> done<00:10:10.560> by<00:10:10.680> Mon 00:10:10.880 --> 00:10:10.890 align:start position:0% main net compatible that was done by Mon 00:10:10.890 --> 00:10:17.300 align:start position:0% main net compatible that was done by Mon acts<00:10:11.130> you<00:10:12.029> have<00:10:13.279> Iroha<00:10:15.019> and<00:10:16.019> you<00:10:16.860> also<00:10:17.010> have 00:10:17.300 --> 00:10:17.310 align:start position:0% acts you have Iroha and you also have 00:10:17.310 --> 00:10:19.639 align:start position:0% acts you have Iroha and you also have hyper<00:10:17.579> ledger<00:10:17.820> in<00:10:18.029> d<00:10:18.209> which<00:10:18.390> is<00:10:18.570> a<00:10:18.600> an<00:10:19.199> identity 00:10:19.639 --> 00:10:19.649 align:start position:0% hyper ledger in d which is a an identity 00:10:19.649 --> 00:10:24.319 align:start position:0% hyper ledger in d which is a an identity piece<00:10:21.410> the<00:10:22.410> other<00:10:22.560> thing<00:10:22.800> that<00:10:22.829> we've<00:10:23.070> done<00:10:23.329> is 00:10:24.319 --> 00:10:24.329 align:start position:0% piece the other thing that we've done is 00:10:24.329 --> 00:10:26.090 align:start position:0% piece the other thing that we've done is applied<00:10:24.839> to<00:10:25.050> join<00:10:25.199> the<00:10:25.260> enterprise<00:10:25.949> of 00:10:26.090 --> 00:10:26.100 align:start position:0% applied to join the enterprise of 00:10:26.100 --> 00:10:29.000 align:start position:0% applied to join the enterprise of theorem<00:10:26.370> Alliance<00:10:26.760> and<00:10:27.500> what<00:10:28.500> why<00:10:28.649> would<00:10:28.829> we 00:10:29.000 --> 00:10:29.010 align:start position:0% theorem Alliance and what why would we 00:10:29.010 --> 00:10:32.840 align:start position:0% theorem Alliance and what why would we do<00:10:29.130> that<00:10:29.209> well<00:10:30.209> the<00:10:30.839> fact<00:10:31.260> is<00:10:31.500> that<00:10:31.850> you've 00:10:32.840 --> 00:10:32.850 align:start position:0% do that well the fact is that you've 00:10:32.850 --> 00:10:35.750 align:start position:0% do that well the fact is that you've seen<00:10:33.149> announced<00:10:33.690> here<00:10:34.500> at<00:10:35.190> this<00:10:35.490> conference 00:10:35.750 --> 00:10:35.760 align:start position:0% seen announced here at this conference 00:10:35.760 --> 00:10:38.900 align:start position:0% seen announced here at this conference the<00:10:36.269> the<00:10:36.899> main<00:10:37.110> net<00:10:37.350> initiative<00:10:37.890> where<00:10:38.730> the 00:10:38.900 --> 00:10:38.910 align:start position:0% the the main net initiative where the 00:10:38.910 --> 00:10:41.210 align:start position:0% the the main net initiative where the etherium<00:10:39.360> foundation<00:10:39.990> and<00:10:40.199> the<00:10:40.290> EEA<00:10:40.620> are 00:10:41.210 --> 00:10:41.220 align:start position:0% etherium foundation and the EEA are 00:10:41.220 --> 00:10:44.120 align:start position:0% etherium foundation and the EEA are basically<00:10:41.850> working<00:10:42.300> together<00:10:42.449> on<00:10:43.130> spec'ing 00:10:44.120 --> 00:10:44.130 align:start position:0% basically working together on spec'ing 00:10:44.130 --> 00:10:50.170 align:start position:0% basically working together on spec'ing out<00:10:45.019> use<00:10:46.019> cases<00:10:46.380> and<00:10:48.230> you<00:10:49.230> know<00:10:49.350> protocol 00:10:50.170 --> 00:10:50.180 align:start position:0% out use cases and you know protocol 00:10:50.180 --> 00:10:54.170 align:start position:0% out use cases and you know protocol definitions<00:10:51.230> for<00:10:52.230> use<00:10:52.440> of<00:10:52.709> of<00:10:53.370> the<00:10:53.699> main<00:10:53.910> net 00:10:54.170 --> 00:10:54.180 align:start position:0% definitions for use of of the main net 00:10:54.180 --> 00:10:57.829 align:start position:0% definitions for use of of the main net for<00:10:55.019> enterprise<00:10:55.410> scenarios<00:10:55.980> so<00:10:56.880> really<00:10:57.240> the 00:10:57.829 --> 00:10:57.839 align:start position:0% for enterprise scenarios so really the 00:10:57.839 --> 00:11:00.019 align:start position:0% for enterprise scenarios so really the the<00:10:58.399> specification<00:10:59.399> work<00:10:59.550> that<00:10:59.760> you've<00:10:59.880> had 00:11:00.019 --> 00:11:00.029 align:start position:0% the specification work that you've had 00:11:00.029 --> 00:11:01.850 align:start position:0% the specification work that you've had happening<00:11:00.449> within<00:11:00.630> the<00:11:00.839> EA<00:11:00.990> has<00:11:01.290> primarily 00:11:01.850 --> 00:11:01.860 align:start position:0% happening within the EA has primarily 00:11:01.860 --> 00:11:04.720 align:start position:0% happening within the EA has primarily been<00:11:02.070> about<00:11:02.459> private<00:11:03.300> or<00:11:03.420> consortium<00:11:03.990> chains 00:11:04.720 --> 00:11:04.730 align:start position:0% been about private or consortium chains 00:11:04.730 --> 00:11:07.760 align:start position:0% been about private or consortium chains when<00:11:05.730> we<00:11:05.850> started<00:11:06.300> the<00:11:06.449> EA<00:11:06.600> the<00:11:07.170> vision<00:11:07.500> was 00:11:07.760 --> 00:11:07.770 align:start position:0% when we started the EA the vision was 00:11:07.770 --> 00:11:11.300 align:start position:0% when we started the EA the vision was that<00:11:08.300> the<00:11:09.300> main<00:11:09.510> net<00:11:09.810> and<00:11:10.140> and<00:11:10.470> you<00:11:11.190> know 00:11:11.300 --> 00:11:11.310 align:start position:0% that the main net and and you know 00:11:11.310 --> 00:11:13.250 align:start position:0% that the main net and and you know basically<00:11:11.520> private<00:11:12.060> and<00:11:12.180> public<00:11:12.300> these<00:11:13.020> the 00:11:13.250 --> 00:11:13.260 align:start position:0% basically private and public these the 00:11:13.260 --> 00:11:15.890 align:start position:0% basically private and public these the would<00:11:13.650> converge<00:11:14.130> and<00:11:14.580> that's<00:11:15.540> where<00:11:15.780> we're 00:11:15.890 --> 00:11:15.900 align:start position:0% would converge and that's where we're 00:11:15.900 --> 00:11:18.440 align:start position:0% would converge and that's where we're getting<00:11:16.020> to<00:11:16.230> right<00:11:16.590> now<00:11:16.770> and<00:11:17.210> what<00:11:18.210> you'll 00:11:18.440 --> 00:11:18.450 align:start position:0% getting to right now and what you'll 00:11:18.450 --> 00:11:21.050 align:start position:0% getting to right now and what you'll what<00:11:18.840> you'll<00:11:19.020> see<00:11:19.290> really<00:11:20.160> with<00:11:20.460> classic 00:11:21.050 --> 00:11:21.060 align:start position:0% what you'll see really with classic 00:11:21.060 --> 00:11:23.210 align:start position:0% what you'll see really with classic being<00:11:21.240> involved<00:11:21.600> as<00:11:21.810> well<00:11:22.020> is<00:11:22.320> that<00:11:23.070> the 00:11:23.210 --> 00:11:23.220 align:start position:0% being involved as well is that the 00:11:23.220 --> 00:11:24.860 align:start position:0% being involved as well is that the specifications<00:11:24.150> really<00:11:24.420> like<00:11:24.570> the<00:11:24.720> yellow 00:11:24.860 --> 00:11:24.870 align:start position:0% specifications really like the yellow 00:11:24.870 --> 00:11:26.330 align:start position:0% specifications really like the yellow paper<00:11:25.260> if<00:11:25.470> you<00:11:25.530> look<00:11:25.710> at<00:11:25.770> the<00:11:25.830> yellow<00:11:25.980> paper 00:11:26.330 --> 00:11:26.340 align:start position:0% paper if you look at the yellow paper 00:11:26.340 --> 00:11:28.250 align:start position:0% paper if you look at the yellow paper the<00:11:27.000> yellow<00:11:27.210> paper<00:11:27.450> assumes<00:11:27.960> that<00:11:28.080> you<00:11:28.230> have 00:11:28.250 --> 00:11:28.260 align:start position:0% the yellow paper assumes that you have 00:11:28.260 --> 00:11:29.660 align:start position:0% the yellow paper assumes that you have one<00:11:28.620> network<00:11:29.010> in<00:11:29.190> the<00:11:29.280> world 00:11:29.660 --> 00:11:29.670 align:start position:0% one network in the world 00:11:29.670 --> 00:11:31.880 align:start position:0% one network in the world you<00:11:29.790> know<00:11:29.910> everything<00:11:30.330> is<00:11:30.420> F<00:11:30.660> main<00:11:30.960> that<00:11:31.200> hard 00:11:31.880 --> 00:11:31.890 align:start position:0% you know everything is F main that hard 00:11:31.890 --> 00:11:33.680 align:start position:0% you know everything is F main that hard you<00:11:32.070> know<00:11:32.190> hard<00:11:32.400> coded<00:11:32.790> block<00:11:33.060> numbers<00:11:33.480> in<00:11:33.600> the 00:11:33.680 --> 00:11:33.690 align:start position:0% you know hard coded block numbers in the 00:11:33.690 --> 00:11:36.260 align:start position:0% you know hard coded block numbers in the specification<00:11:34.500> and<00:11:35.220> I<00:11:35.310> mean<00:11:35.430> that's<00:11:35.640> not<00:11:35.940> that 00:11:36.260 --> 00:11:36.270 align:start position:0% specification and I mean that's not that 00:11:36.270 --> 00:11:38.240 align:start position:0% specification and I mean that's not that is<00:11:36.390> not<00:11:36.600> the<00:11:36.720> way<00:11:36.840> to<00:11:36.870> do<00:11:37.200> a<00:11:37.230> specification<00:11:38.070> of 00:11:38.240 --> 00:11:38.250 align:start position:0% is not the way to do a specification of 00:11:38.250 --> 00:11:40.970 align:start position:0% is not the way to do a specification of a<00:11:38.790> technology<00:11:39.360> stack<00:11:39.600> of<00:11:39.750> a<00:11:39.810> protocol<00:11:40.320> you 00:11:40.970 --> 00:11:40.980 align:start position:0% a technology stack of a protocol you 00:11:40.980 --> 00:11:42.890 align:start position:0% a technology stack of a protocol you should<00:11:41.160> really<00:11:41.370> have<00:11:41.460> a<00:11:41.640> modular<00:11:42.510> setup 00:11:42.890 --> 00:11:42.900 align:start position:0% should really have a modular setup 00:11:42.900 --> 00:11:44.630 align:start position:0% should really have a modular setup that's<00:11:43.080> like<00:11:43.260> here<00:11:43.530> is<00:11:43.650> what<00:11:43.890> an<00:11:44.040> aetherium 00:11:44.630 --> 00:11:44.640 align:start position:0% that's like here is what an aetherium 00:11:44.640 --> 00:11:48.230 align:start position:0% that's like here is what an aetherium stack<00:11:44.970> looks<00:11:45.270> like<00:11:46.010> appendix<00:11:47.010> a<00:11:47.220> here<00:11:48.060> is<00:11:48.210> the 00:11:48.230 --> 00:11:48.240 align:start position:0% stack looks like appendix a here is the 00:11:48.240 --> 00:11:51.500 align:start position:0% stack looks like appendix a here is the definition<00:11:48.480> of<00:11:48.900> an<00:11:49.370> ethe<00:11:50.370> main<00:11:50.670> net<00:11:50.910> here's 00:11:51.500 --> 00:11:51.510 align:start position:0% definition of an ethe main net here's 00:11:51.510 --> 00:11:53.210 align:start position:0% definition of an ethe main net here's the<00:11:51.660> definition<00:11:51.810> of<00:11:52.200> an<00:11:52.290> e.t.c<00:11:52.740> main<00:11:53.010> net 00:11:53.210 --> 00:11:53.220 align:start position:0% the definition of an e.t.c main net 00:11:53.220 --> 00:11:55.580 align:start position:0% the definition of an e.t.c main net here's<00:11:53.760> the<00:11:53.940> definition<00:11:54.420> of<00:11:54.510> a<00:11:54.630> you<00:11:55.470> know<00:11:55.500> a 00:11:55.580 --> 00:11:55.590 align:start position:0% here's the definition of a you know a 00:11:55.590 --> 00:11:57.920 align:start position:0% here's the definition of a you know a private<00:11:55.890> chain<00:11:56.880> running<00:11:57.420> a<00:11:57.600> proof<00:11:57.840> of 00:11:57.920 --> 00:11:57.930 align:start position:0% private chain running a proof of 00:11:57.930 --> 00:12:02.770 align:start position:0% private chain running a proof of authority<00:11:58.440> so<00:11:59.430> we're<00:11:59.580> gonna<00:11:59.670> help<00:11:59.910> with<00:12:00.030> that 00:12:02.770 --> 00:12:02.780 align:start position:0% 00:12:02.780 --> 00:12:04.760 align:start position:0% another<00:12:03.780> thing<00:12:04.050> that<00:12:04.230> we've<00:12:04.350> done<00:12:04.380> recently 00:12:04.760 --> 00:12:04.770 align:start position:0% another thing that we've done recently 00:12:04.770 --> 00:12:11.590 align:start position:0% another thing that we've done recently is<00:12:06.020> revived<00:12:07.020> the<00:12:07.200> old<00:12:07.350> website<00:12:07.760> we<00:12:08.760> we<00:12:09.510> had<00:12:09.980> a 00:12:11.590 --> 00:12:11.600 align:start position:0% is revived the old website we we had a 00:12:11.600 --> 00:12:13.640 align:start position:0% is revived the old website we we had a maintenance<00:12:12.600> issue<00:12:12.720> one<00:12:13.260> of<00:12:13.350> the<00:12:13.440> first 00:12:13.640 --> 00:12:13.650 align:start position:0% maintenance issue one of the first 00:12:13.650 --> 00:12:15.820 align:start position:0% maintenance issue one of the first things<00:12:13.890> that<00:12:13.950> my<00:12:14.130> predecessor<00:12:14.400> at<00:12:15.090> the<00:12:15.510> coop 00:12:15.820 --> 00:12:15.830 align:start position:0% things that my predecessor at the coop 00:12:15.830 --> 00:12:19.580 align:start position:0% things that my predecessor at the coop Anthony<00:12:16.830> lucid<00:12:17.190> II<00:12:17.220> did<00:12:17.550> was<00:12:18.530> commissioned<00:12:19.530> a 00:12:19.580 --> 00:12:19.590 align:start position:0% Anthony lucid II did was commissioned a 00:12:19.590 --> 00:12:23.900 align:start position:0% Anthony lucid II did was commissioned a Spanky<00:12:20.310> new<00:12:20.490> WordPress<00:12:21.030> website<00:12:22.820> but<00:12:23.820> the 00:12:23.900 --> 00:12:23.910 align:start position:0% Spanky new WordPress website but the 00:12:23.910 --> 00:12:26.600 align:start position:0% Spanky new WordPress website but the problem<00:12:24.270> with<00:12:24.420> that<00:12:24.570> is<00:12:25.160> WordPress<00:12:26.160> websites 00:12:26.600 --> 00:12:26.610 align:start position:0% problem with that is WordPress websites 00:12:26.610 --> 00:12:29.420 align:start position:0% problem with that is WordPress websites you<00:12:26.850> only<00:12:27.180> your<00:12:27.330> admin<00:12:27.690> can<00:12:28.050> update<00:12:28.200> it<00:12:28.380> so<00:12:29.340> we 00:12:29.420 --> 00:12:29.430 align:start position:0% you only your admin can update it so we 00:12:29.430 --> 00:12:31.250 align:start position:0% you only your admin can update it so we didn't<00:12:29.670> really<00:12:29.940> have<00:12:30.090> a<00:12:30.120> good<00:12:30.300> means<00:12:30.660> for<00:12:31.200> the 00:12:31.250 --> 00:12:31.260 align:start position:0% didn't really have a good means for the 00:12:31.260 --> 00:12:33.220 align:start position:0% didn't really have a good means for the community<00:12:31.290> to<00:12:31.860> contribute<00:12:32.100> changes<00:12:32.670> back<00:12:32.820> in 00:12:33.220 --> 00:12:33.230 align:start position:0% community to contribute changes back in 00:12:33.230 --> 00:12:35.840 align:start position:0% community to contribute changes back in the<00:12:34.230> earlier<00:12:34.500> web<00:12:34.680> site<00:12:34.920> that<00:12:35.070> we<00:12:35.160> had<00:12:35.340> was<00:12:35.610> was 00:12:35.840 --> 00:12:35.850 align:start position:0% the earlier web site that we had was was 00:12:35.850 --> 00:12:37.130 align:start position:0% the earlier web site that we had was was based<00:12:36.060> on<00:12:36.240> github<00:12:36.570> and<00:12:36.690> you<00:12:36.750> could<00:12:36.870> just<00:12:36.990> do 00:12:37.130 --> 00:12:37.140 align:start position:0% based on github and you could just do 00:12:37.140 --> 00:12:38.990 align:start position:0% based on github and you could just do pull<00:12:37.320> requests<00:12:37.860> but<00:12:38.100> you<00:12:38.340> know<00:12:38.460> it<00:12:38.610> didn't 00:12:38.990 --> 00:12:39.000 align:start position:0% pull requests but you know it didn't 00:12:39.000 --> 00:12:41.180 align:start position:0% pull requests but you know it didn't look<00:12:39.090> great<00:12:39.390> so<00:12:40.320> what<00:12:40.500> we've<00:12:40.620> done<00:12:40.800> over<00:12:41.100> the 00:12:41.180 --> 00:12:41.190 align:start position:0% look great so what we've done over the 00:12:41.190 --> 00:12:42.740 align:start position:0% look great so what we've done over the last<00:12:41.280> little<00:12:41.610> while<00:12:41.700> is<00:12:41.970> basically<00:12:42.330> revived 00:12:42.740 --> 00:12:42.750 align:start position:0% last little while is basically revived 00:12:42.750 --> 00:12:45.890 align:start position:0% last little while is basically revived that<00:12:43.020> old<00:12:43.320> website<00:12:44.210> but<00:12:45.210> made<00:12:45.390> it<00:12:45.510> look<00:12:45.630> nicer 00:12:45.890 --> 00:12:45.900 align:start position:0% that old website but made it look nicer 00:12:45.900 --> 00:12:50.450 align:start position:0% that old website but made it look nicer and<00:12:46.730> updated<00:12:47.730> the<00:12:47.790> content<00:12:48.240> and<00:12:48.920> the<00:12:49.920> guy<00:12:50.100> who 00:12:50.450 --> 00:12:50.460 align:start position:0% and updated the content and the guy who 00:12:50.460 --> 00:12:52.550 align:start position:0% and updated the content and the guy who originally<00:12:51.150> did<00:12:51.480> the<00:12:51.690> web<00:12:51.990> design<00:12:52.350> on<00:12:52.530> that 00:12:52.550 --> 00:12:52.560 align:start position:0% originally did the web design on that 00:12:52.560 --> 00:12:56.330 align:start position:0% originally did the web design on that has<00:12:53.400> just<00:12:53.610> reappeared<00:12:54.350> he<00:12:55.350> actually<00:12:55.860> attended 00:12:56.330 --> 00:12:56.340 align:start position:0% has just reappeared he actually attended 00:12:56.340 --> 00:12:58.430 align:start position:0% has just reappeared he actually attended the<00:12:56.430> summit<00:12:56.720> because<00:12:57.720> he<00:12:57.930> sees<00:12:58.140> everything 00:12:58.430 --> 00:12:58.440 align:start position:0% the summit because he sees everything 00:12:58.440 --> 00:13:00.350 align:start position:0% the summit because he sees everything happening<00:12:58.860> in<00:12:58.980> classic<00:12:59.520> and<00:12:59.670> is<00:12:59.730> like<00:12:59.880> ooh<00:13:00.030> as 00:13:00.350 --> 00:13:00.360 align:start position:0% happening in classic and is like ooh as 00:13:00.360 --> 00:13:02.150 align:start position:0% happening in classic and is like ooh as this<00:13:00.480> is<00:13:00.630> quite<00:13:00.810> interesting<00:13:00.900> I'm<00:13:01.590> coming 00:13:02.150 --> 00:13:02.160 align:start position:0% this is quite interesting I'm coming 00:13:02.160 --> 00:13:04.250 align:start position:0% this is quite interesting I'm coming back<00:13:02.280> so<00:13:03.120> he<00:13:03.210> can<00:13:03.360> come<00:13:03.540> back<00:13:03.690> and<00:13:03.930> help<00:13:04.050> with<00:13:04.230> a 00:13:04.250 --> 00:13:04.260 align:start position:0% back so he can come back and help with a 00:13:04.260 --> 00:13:05.570 align:start position:0% back so he can come back and help with a web<00:13:04.440> site<00:13:04.620> because<00:13:04.860> he<00:13:04.950> did<00:13:05.130> it<00:13:05.220> originally 00:13:05.570 --> 00:13:05.580 align:start position:0% web site because he did it originally 00:13:05.580 --> 00:13:08.380 align:start position:0% web site because he did it originally the<00:13:06.450> other<00:13:06.600> problem<00:13:07.080> that<00:13:07.110> we<00:13:07.320> had<00:13:07.560> is 00:13:08.380 --> 00:13:08.390 align:start position:0% the other problem that we had is 00:13:08.390 --> 00:13:12.820 align:start position:0% the other problem that we had is problems<00:13:09.390> of<00:13:09.570> of<00:13:09.810> east-west<00:13:10.380> communication 00:13:12.820 --> 00:13:12.830 align:start position:0% problems of of east-west communication 00:13:12.830 --> 00:13:14.900 align:start position:0% problems of of east-west communication specifically<00:13:13.830> you<00:13:14.190> know<00:13:14.310> our<00:13:14.520> Chinese 00:13:14.900 --> 00:13:14.910 align:start position:0% specifically you know our Chinese 00:13:14.910 --> 00:13:16.940 align:start position:0% specifically you know our Chinese community<00:13:15.450> and<00:13:15.720> and<00:13:15.960> other<00:13:16.080> Asian 00:13:16.940 --> 00:13:16.950 align:start position:0% community and and other Asian 00:13:16.950 --> 00:13:18.380 align:start position:0% community and and other Asian communities<00:13:17.400> have<00:13:17.580> been<00:13:17.700> very<00:13:17.910> disconnected 00:13:18.380 --> 00:13:18.390 align:start position:0% communities have been very disconnected 00:13:18.390 --> 00:13:21.110 align:start position:0% communities have been very disconnected with<00:13:18.870> the<00:13:18.990> West<00:13:19.170> and<00:13:19.530> for<00:13:20.280> China<00:13:20.460> specifically 00:13:21.110 --> 00:13:21.120 align:start position:0% with the West and for China specifically 00:13:21.120 --> 00:13:24.740 align:start position:0% with the West and for China specifically a<00:13:21.390> primary<00:13:22.320> reason<00:13:22.500> for<00:13:22.860> that<00:13:22.950> is<00:13:23.880> is<00:13:24.240> is<00:13:24.510> the 00:13:24.740 --> 00:13:24.750 align:start position:0% a primary reason for that is is is the 00:13:24.750 --> 00:13:26.290 align:start position:0% a primary reason for that is is is the Great<00:13:25.050> Firewall 00:13:26.290 --> 00:13:26.300 align:start position:0% Great Firewall 00:13:26.300 --> 00:13:30.550 align:start position:0% Great Firewall so<00:13:26.720> if<00:13:26.990> you<00:13:27.230> are<00:13:27.790> in<00:13:28.790> mainland<00:13:29.420> China<00:13:29.690> you 00:13:30.550 --> 00:13:30.560 align:start position:0% so if you are in mainland China you 00:13:30.560 --> 00:13:33.130 align:start position:0% so if you are in mainland China you can't<00:13:30.800> access<00:13:31.250> Twitter<00:13:31.850> you<00:13:32.480> can't<00:13:32.720> access 00:13:33.130 --> 00:13:33.140 align:start position:0% can't access Twitter you can't access 00:13:33.140 --> 00:13:37.000 align:start position:0% can't access Twitter you can't access discord<00:13:33.860> you<00:13:34.100> can't<00:13:34.340> access<00:13:34.750> github<00:13:36.010> and 00:13:37.000 --> 00:13:37.010 align:start position:0% discord you can't access github and 00:13:37.010 --> 00:13:39.070 align:start position:0% discord you can't access github and specifically<00:13:37.880> the<00:13:38.030> communication<00:13:38.690> channels 00:13:39.070 --> 00:13:39.080 align:start position:0% specifically the communication channels 00:13:39.080 --> 00:13:41.470 align:start position:0% specifically the communication channels are<00:13:39.290> a<00:13:39.500> major<00:13:39.740> problem<00:13:39.980> because<00:13:40.940> the<00:13:41.060> discord 00:13:41.470 --> 00:13:41.480 align:start position:0% are a major problem because the discord 00:13:41.480 --> 00:13:42.970 align:start position:0% are a major problem because the discord and<00:13:41.630> the<00:13:41.720> Twitter<00:13:41.930> that's<00:13:42.230> where<00:13:42.470> all<00:13:42.740> of<00:13:42.890> the 00:13:42.970 --> 00:13:42.980 align:start position:0% and the Twitter that's where all of the 00:13:42.980 --> 00:13:45.580 align:start position:0% and the Twitter that's where all of the communication<00:13:43.580> happens<00:13:43.970> so<00:13:44.840> what<00:13:45.290> I've<00:13:45.410> done 00:13:45.580 --> 00:13:45.590 align:start position:0% communication happens so what I've done 00:13:45.590 --> 00:13:47.800 align:start position:0% communication happens so what I've done is<00:13:45.830> well<00:13:46.250> what's<00:13:46.460> the<00:13:46.640> answer<00:13:46.760> well<00:13:47.120> you<00:13:47.240> use 00:13:47.800 --> 00:13:47.810 align:start position:0% is well what's the answer well you use 00:13:47.810 --> 00:13:50.020 align:start position:0% is well what's the answer well you use WeChat<00:13:48.020> you<00:13:48.860> use<00:13:49.070> WeChat<00:13:49.280> anywhere<00:13:49.820> in<00:13:49.940> the 00:13:50.020 --> 00:13:50.030 align:start position:0% WeChat you use WeChat anywhere in the 00:13:50.030 --> 00:13:53.710 align:start position:0% WeChat you use WeChat anywhere in the world<00:13:50.210> so<00:13:50.960> we<00:13:51.080> now<00:13:51.290> have<00:13:51.730> etc'<00:13:52.730> global<00:13:53.330> comms 00:13:53.710 --> 00:13:53.720 align:start position:0% world so we now have etc' global comms 00:13:53.720 --> 00:13:56.860 align:start position:0% world so we now have etc' global comms channel<00:13:54.590> which<00:13:55.340> is<00:13:55.490> just<00:13:55.700> an<00:13:55.790> open<00:13:56.060> open 00:13:56.860 --> 00:13:56.870 align:start position:0% channel which is just an open open 00:13:56.870 --> 00:14:00.070 align:start position:0% channel which is just an open open WeChat<00:13:57.590> channel<00:13:58.010> where<00:13:58.670> we've<00:13:58.850> gathered<00:13:59.270> all 00:14:00.070 --> 00:14:00.080 align:start position:0% WeChat channel where we've gathered all 00:14:00.080 --> 00:14:02.920 align:start position:0% WeChat channel where we've gathered all of<00:14:00.140> the<00:14:00.530> all<00:14:01.100> of<00:14:01.250> the<00:14:01.340> community<00:14:01.760> people<00:14:02.690> from 00:14:02.920 --> 00:14:02.930 align:start position:0% of the all of the community people from 00:14:02.930 --> 00:14:06.720 align:start position:0% of the all of the community people from all<00:14:03.230> of<00:14:03.380> the<00:14:03.470> sides<00:14:03.680> and<00:14:04.070> myself<00:14:04.310> and<00:14:04.820> Yaz<00:14:05.140> and 00:14:06.720 --> 00:14:06.730 align:start position:0% all of the sides and myself and Yaz and 00:14:06.730 --> 00:14:09.960 align:start position:0% all of the sides and myself and Yaz and all<00:14:07.730> of<00:14:07.970> a<00:14:08.030> sudden<00:14:08.330> these<00:14:08.690> these 00:14:09.960 --> 00:14:09.970 align:start position:0% all of a sudden these these 00:14:09.970 --> 00:14:12.910 align:start position:0% all of a sudden these these communication<00:14:10.970> gaps<00:14:11.290> barring<00:14:12.290> time<00:14:12.590> zones 00:14:12.910 --> 00:14:12.920 align:start position:0% communication gaps barring time zones 00:14:12.920 --> 00:14:14.470 align:start position:0% communication gaps barring time zones they're<00:14:13.220> done<00:14:13.400> everyone<00:14:14.180> is<00:14:14.270> very 00:14:14.470 --> 00:14:14.480 align:start position:0% they're done everyone is very 00:14:14.480 --> 00:14:19.120 align:start position:0% they're done everyone is very communicative<00:14:15.020> if<00:14:15.650> you<00:14:16.490> can<00:14:16.730> communicate<00:14:18.130> so 00:14:19.120 --> 00:14:19.130 align:start position:0% communicative if you can communicate so 00:14:19.130 --> 00:14:20.950 align:start position:0% communicative if you can communicate so we're<00:14:19.280> doing<00:14:19.520> that<00:14:19.700> the<00:14:20.540> other<00:14:20.690> thing<00:14:20.930> that 00:14:20.950 --> 00:14:20.960 align:start position:0% we're doing that the other thing that 00:14:20.960 --> 00:14:22.690 align:start position:0% we're doing that the other thing that we're<00:14:21.200> going<00:14:21.350> to<00:14:21.440> do<00:14:21.680> is<00:14:22.010> on<00:14:22.280> that<00:14:22.430> main 00:14:22.690 --> 00:14:22.700 align:start position:0% we're going to do is on that main 00:14:22.700 --> 00:14:25.440 align:start position:0% we're going to do is on that main website<00:14:23.240> we<00:14:24.110> are<00:14:24.290> adding 00:14:25.440 --> 00:14:25.450 align:start position:0% website we are adding 00:14:25.450 --> 00:14:28.480 align:start position:0% website we are adding internationalization<00:14:27.070> because<00:14:28.070> we<00:14:28.190> also 00:14:28.480 --> 00:14:28.490 align:start position:0% internationalization because we also 00:14:28.490 --> 00:14:32.260 align:start position:0% internationalization because we also have<00:14:28.820> this<00:14:28.940> this<00:14:30.040> siloing<00:14:31.040> thing<00:14:31.460> of<00:14:31.730> the 00:14:32.260 --> 00:14:32.270 align:start position:0% have this this siloing thing of the 00:14:32.270 --> 00:14:34.360 align:start position:0% have this this siloing thing of the etherium<00:14:32.810> classic<00:14:33.200> dog<00:14:33.470> was<00:14:33.830> English<00:14:34.190> only 00:14:34.360 --> 00:14:34.370 align:start position:0% etherium classic dog was English only 00:14:34.370 --> 00:14:36.760 align:start position:0% etherium classic dog was English only and<00:14:34.790> then<00:14:35.510> other<00:14:35.810> communities<00:14:36.380> have<00:14:36.560> built 00:14:36.760 --> 00:14:36.770 align:start position:0% and then other communities have built 00:14:36.770 --> 00:14:38.770 align:start position:0% and then other communities have built their<00:14:36.980> own<00:14:37.010> websites<00:14:37.580> but<00:14:37.880> then<00:14:38.090> you<00:14:38.690> know 00:14:38.770 --> 00:14:38.780 align:start position:0% their own websites but then you know 00:14:38.780 --> 00:14:40.240 align:start position:0% their own websites but then you know they<00:14:38.930> don't<00:14:39.050> have<00:14:39.200> they're<00:14:39.950> having<00:14:40.160> to 00:14:40.240 --> 00:14:40.250 align:start position:0% they don't have they're having to 00:14:40.250 --> 00:14:42.160 align:start position:0% they don't have they're having to replicate<00:14:40.850> well<00:14:41.030> here's<00:14:41.210> a<00:14:41.270> tutorial<00:14:41.540> about 00:14:42.160 --> 00:14:42.170 align:start position:0% replicate well here's a tutorial about 00:14:42.170 --> 00:14:44.110 align:start position:0% replicate well here's a tutorial about how<00:14:42.320> we<00:14:42.530> write<00:14:42.800> a<00:14:42.830> small<00:14:43.040> contract<00:14:43.760> and<00:14:43.970> what 00:14:44.110 --> 00:14:44.120 align:start position:0% how we write a small contract and what 00:14:44.120 --> 00:14:48.060 align:start position:0% how we write a small contract and what is<00:14:44.240> is<00:14:44.480> classic<00:14:44.960> and<00:14:45.050> so<00:14:45.230> on<00:14:46.360> but<00:14:47.360> by<00:14:47.510> having 00:14:48.060 --> 00:14:48.070 align:start position:0% is is classic and so on but by having 00:14:48.070 --> 00:14:51.360 align:start position:0% is is classic and so on but by having that<00:14:49.070> language<00:14:49.520> support<00:14:49.910> within<00:14:50.180> that<00:14:50.300> base 00:14:51.360 --> 00:14:51.370 align:start position:0% that language support within that base 00:14:51.370 --> 00:14:54.640 align:start position:0% that language support within that base website<00:14:52.630> most<00:14:53.630> countries<00:14:54.110> maybe<00:14:54.380> that's 00:14:54.640 --> 00:14:54.650 align:start position:0% website most countries maybe that's 00:14:54.650 --> 00:14:56.950 align:start position:0% website most countries maybe that's enough<00:14:55.030> that<00:14:56.030> you<00:14:56.150> just<00:14:56.300> point<00:14:56.600> to<00:14:56.660> a<00:14:56.720> theory 00:14:56.950 --> 00:14:56.960 align:start position:0% enough that you just point to a theory 00:14:56.960 --> 00:14:59.080 align:start position:0% enough that you just point to a theory and<00:14:57.110> classic<00:14:57.410> dog<00:14:57.560> and<00:14:57.890> do<00:14:58.010> the<00:14:58.190> the<00:14:58.220> drop<00:14:58.850> down 00:14:59.080 --> 00:14:59.090 align:start position:0% and classic dog and do the the drop down 00:14:59.090 --> 00:15:01.420 align:start position:0% and classic dog and do the the drop down you<00:14:59.780> know<00:14:59.930> like<00:15:00.080> normal<00:15:00.530> websites<00:15:01.160> like 00:15:01.420 --> 00:15:01.430 align:start position:0% you know like normal websites like 00:15:01.430 --> 00:15:04.000 align:start position:0% you know like normal websites like professional<00:15:02.030> people<00:15:02.270> can<00:15:02.630> do<00:15:02.780> but<00:15:03.770> somehow 00:15:04.000 --> 00:15:04.010 align:start position:0% professional people can do but somehow 00:15:04.010 --> 00:15:07.420 align:start position:0% professional people can do but somehow we<00:15:04.160> had<00:15:04.340> not<00:15:04.550> done<00:15:05.860> so<00:15:06.860> we're<00:15:07.040> going<00:15:07.130> to<00:15:07.250> do 00:15:07.420 --> 00:15:07.430 align:start position:0% we had not done so we're going to do 00:15:07.430 --> 00:15:09.280 align:start position:0% we had not done so we're going to do that<00:15:07.610> and<00:15:08.060> I<00:15:08.240> mean<00:15:08.360> that's<00:15:08.570> not<00:15:08.750> to<00:15:08.930> say<00:15:09.080> well 00:15:09.280 --> 00:15:09.290 align:start position:0% that and I mean that's not to say well 00:15:09.290 --> 00:15:10.840 align:start position:0% that and I mean that's not to say well you<00:15:09.410> have<00:15:09.440> to<00:15:09.800> only<00:15:10.010> use<00:15:10.310> the<00:15:10.520> official 00:15:10.840 --> 00:15:10.850 align:start position:0% you have to only use the official 00:15:10.850 --> 00:15:14.020 align:start position:0% you have to only use the official website<00:15:12.280> obviously<00:15:13.280> anyone<00:15:13.490> can<00:15:13.730> do<00:15:13.850> whatever 00:15:14.020 --> 00:15:14.030 align:start position:0% website obviously anyone can do whatever 00:15:14.030 --> 00:15:15.730 align:start position:0% website obviously anyone can do whatever they<00:15:14.270> like<00:15:14.300> on<00:15:14.630> their<00:15:14.780> own<00:15:14.900> and<00:15:15.170> add<00:15:15.440> their<00:15:15.680> own 00:15:15.730 --> 00:15:15.740 align:start position:0% they like on their own and add their own 00:15:15.740 --> 00:15:19.390 align:start position:0% they like on their own and add their own pieces<00:15:16.210> but<00:15:17.210> we<00:15:17.480> should<00:15:17.720> have<00:15:17.750> that<00:15:18.400> basic 00:15:19.390 --> 00:15:19.400 align:start position:0% pieces but we should have that basic 00:15:19.400 --> 00:15:22.300 align:start position:0% pieces but we should have that basic information<00:15:20.470> available<00:15:21.470> to<00:15:21.770> everyone<00:15:22.010> and 00:15:22.300 --> 00:15:22.310 align:start position:0% information available to everyone and 00:15:22.310 --> 00:15:23.950 align:start position:0% information available to everyone and one<00:15:22.850> of<00:15:22.970> the<00:15:23.030> other<00:15:23.150> things<00:15:23.390> that<00:15:23.480> we<00:15:23.660> can<00:15:23.750> have 00:15:23.950 --> 00:15:23.960 align:start position:0% one of the other things that we can have 00:15:23.960 --> 00:15:27.700 align:start position:0% one of the other things that we can have in<00:15:24.080> there<00:15:24.290> is<00:15:24.530> blog<00:15:24.920> posts<00:15:25.810> so<00:15:26.810> this<00:15:27.260> site 00:15:27.700 --> 00:15:27.710 align:start position:0% in there is blog posts so this site 00:15:27.710 --> 00:15:30.340 align:start position:0% in there is blog posts so this site allows<00:15:28.070> you<00:15:28.340> to<00:15:28.580> use<00:15:29.000> simple<00:15:29.600> markdown<00:15:30.110> for 00:15:30.340 --> 00:15:30.350 align:start position:0% allows you to use simple markdown for 00:15:30.350 --> 00:15:33.210 align:start position:0% allows you to use simple markdown for blog<00:15:30.560> posts<00:15:31.040> we<00:15:31.790> have<00:15:32.030> been<00:15:32.240> using<00:15:32.450> medium 00:15:33.210 --> 00:15:33.220 align:start position:0% blog posts we have been using medium 00:15:33.220 --> 00:15:38.110 align:start position:0% blog posts we have been using medium medium<00:15:34.220> again<00:15:34.460> blocked<00:15:35.360> by<00:15:35.510> the<00:15:35.570> firewall<00:15:37.120> so 00:15:38.110 --> 00:15:38.120 align:start position:0% medium again blocked by the firewall so 00:15:38.120 --> 00:15:40.150 align:start position:0% medium again blocked by the firewall so the<00:15:38.510> flow<00:15:38.780> that<00:15:38.960> we<00:15:39.110> will<00:15:39.290> have<00:15:39.470> in<00:15:39.620> stairs 00:15:40.150 --> 00:15:40.160 align:start position:0% the flow that we will have in stairs 00:15:40.160 --> 00:15:43.030 align:start position:0% the flow that we will have in stairs is<00:15:40.310> blog<00:15:41.270> post<00:15:41.600> happening<00:15:42.260> on<00:15:42.410> that<00:15:42.590> website 00:15:43.030 --> 00:15:43.040 align:start position:0% is blog post happening on that website 00:15:43.040 --> 00:15:44.790 align:start position:0% is blog post happening on that website that's<00:15:43.310> accessible<00:15:43.790> anywhere<00:15:44.150> in<00:15:44.330> the<00:15:44.420> world 00:15:44.790 --> 00:15:44.800 align:start position:0% that's accessible anywhere in the world 00:15:44.800 --> 00:15:47.770 align:start position:0% that's accessible anywhere in the world probably<00:15:45.800> in<00:15:45.920> English<00:15:46.220> first<00:15:46.520> and<00:15:46.880> then<00:15:47.630> if 00:15:47.770 --> 00:15:47.780 align:start position:0% probably in English first and then if 00:15:47.780 --> 00:15:49.540 align:start position:0% probably in English first and then if you<00:15:47.930> are<00:15:47.960> flipping<00:15:48.890> to<00:15:49.100> one<00:15:49.250> of<00:15:49.340> the<00:15:49.430> other 00:15:49.540 --> 00:15:49.550 align:start position:0% you are flipping to one of the other 00:15:49.550 --> 00:15:51.640 align:start position:0% you are flipping to one of the other language<00:15:49.970> choices<00:15:50.300> well<00:15:51.230> you're<00:15:51.380> gonna<00:15:51.500> get 00:15:51.640 --> 00:15:51.650 align:start position:0% language choices well you're gonna get 00:15:51.650 --> 00:15:52.900 align:start position:0% language choices well you're gonna get it<00:15:51.710> in<00:15:51.920> English<00:15:52.250> if<00:15:52.430> there<00:15:52.670> isn't<00:15:52.760> a 00:15:52.900 --> 00:15:52.910 align:start position:0% it in English if there isn't a 00:15:52.910 --> 00:15:55.000 align:start position:0% it in English if there isn't a translation<00:15:53.570> if<00:15:53.840> there<00:15:54.080> is<00:15:54.200> you're<00:15:54.710> gonna<00:15:54.800> get 00:15:55.000 --> 00:15:55.010 align:start position:0% translation if there is you're gonna get 00:15:55.010 --> 00:15:56.830 align:start position:0% translation if there is you're gonna get it<00:15:55.100> in<00:15:55.190> your<00:15:55.280> own<00:15:55.430> language<00:15:55.610> so<00:15:56.540> that's<00:15:56.720> a 00:15:56.830 --> 00:15:56.840 align:start position:0% it in your own language so that's a 00:15:56.840 --> 00:15:59.560 align:start position:0% it in your own language so that's a pattern<00:15:57.020> which<00:15:57.410> is<00:15:57.710> not<00:15:58.340> only<00:15:58.580> breaching<00:15:59.240> you 00:15:59.560 --> 00:15:59.570 align:start position:0% pattern which is not only breaching you 00:15:59.570 --> 00:16:02.650 align:start position:0% pattern which is not only breaching you know<00:15:59.800> bridging<00:16:00.800> east<00:16:01.010> and<00:16:01.220> west<00:16:01.480> it's<00:16:02.480> also 00:16:02.650 --> 00:16:02.660 align:start position:0% know bridging east and west it's also 00:16:02.660 --> 00:16:05.260 align:start position:0% know bridging east and west it's also bridging<00:16:03.230> other<00:16:03.500> communities<00:16:04.270> Italian 00:16:05.260 --> 00:16:05.270 align:start position:0% bridging other communities Italian 00:16:05.270 --> 00:16:07.720 align:start position:0% bridging other communities Italian German<00:16:05.720> French<00:16:06.290> you<00:16:07.040> know<00:16:07.160> lots<00:16:07.400> of<00:16:07.550> these 00:16:07.720 --> 00:16:07.730 align:start position:0% German French you know lots of these 00:16:07.730 --> 00:16:10.330 align:start position:0% German French you know lots of these country<00:16:08.690> specific<00:16:09.140> ones<00:16:09.320> that<00:16:09.470> they're<00:16:10.220> not 00:16:10.330 --> 00:16:10.340 align:start position:0% country specific ones that they're not 00:16:10.340 --> 00:16:12.190 align:start position:0% country specific ones that they're not necessarily<00:16:10.570> developers<00:16:11.570> you<00:16:11.960> know<00:16:11.990> that 00:16:12.190 --> 00:16:12.200 align:start position:0% necessarily developers you know that 00:16:12.200 --> 00:16:15.250 align:start position:0% necessarily developers you know that they<00:16:12.380> are<00:16:13.030> enthusiasts<00:16:14.030> who<00:16:14.480> can<00:16:14.660> probably<00:16:14.930> do 00:16:15.250 --> 00:16:15.260 align:start position:0% they are enthusiasts who can probably do 00:16:15.260 --> 00:16:17.980 align:start position:0% they are enthusiasts who can probably do a<00:16:15.290> translation<00:16:16.180> but<00:16:17.180> you<00:16:17.450> know<00:16:17.570> they're<00:16:17.780> there 00:16:17.980 --> 00:16:17.990 align:start position:0% a translation but you know they're there 00:16:17.990 --> 00:16:19.270 align:start position:0% a translation but you know they're there they're<00:16:18.200> essentially<00:16:18.740> receiving 00:16:19.270 --> 00:16:19.280 align:start position:0% they're essentially receiving 00:16:19.280 --> 00:16:20.380 align:start position:0% they're essentially receiving information<00:16:19.400> you<00:16:20.000> know<00:16:20.120> they're<00:16:20.270> not 00:16:20.380 --> 00:16:20.390 align:start position:0% information you know they're not 00:16:20.390 --> 00:16:22.690 align:start position:0% information you know they're not necessarily<00:16:20.900> ever<00:16:21.170> gonna<00:16:21.350> be<00:16:21.470> doing<00:16:21.740> protocol 00:16:22.690 --> 00:16:22.700 align:start position:0% necessarily ever gonna be doing protocol 00:16:22.700 --> 00:16:26.200 align:start position:0% necessarily ever gonna be doing protocol changes<00:16:23.270> or<00:16:23.450> changes<00:16:23.720> to<00:16:24.020> clients<00:16:24.500> but<00:16:25.210> open 00:16:26.200 --> 00:16:26.210 align:start position:0% changes or changes to clients but open 00:16:26.210 --> 00:16:29.500 align:start position:0% changes or changes to clients but open open<00:16:26.630> that<00:16:26.720> stuff<00:16:26.930> up<00:16:28.120> the<00:16:29.120> other<00:16:29.270> piece<00:16:29.480> that 00:16:29.500 --> 00:16:29.510 align:start position:0% open that stuff up the other piece that 00:16:29.510 --> 00:16:32.370 align:start position:0% open that stuff up the other piece that we<00:16:29.840> have<00:16:30.080> is<00:16:30.350> that<00:16:30.710> the<00:16:30.890> is<00:16:31.340> that<00:16:31.400> the<00:16:31.610> classic 00:16:32.370 --> 00:16:32.380 align:start position:0% we have is that the is that the classic 00:16:32.380 --> 00:16:35.170 align:start position:0% we have is that the is that the classic has<00:16:33.380> signed<00:16:34.070> a<00:16:34.160> contract<00:16:34.190> with<00:16:34.580> Masari 00:16:35.170 --> 00:16:35.180 align:start position:0% has signed a contract with Masari 00:16:35.180 --> 00:16:39.240 align:start position:0% has signed a contract with Masari so<00:16:35.990> Masari<00:16:36.380> provide<00:16:37.070> basically<00:16:37.550> high-quality 00:16:39.240 --> 00:16:39.250 align:start position:0% so Masari provide basically high-quality 00:16:39.250 --> 00:16:45.430 align:start position:0% so Masari provide basically high-quality financial<00:16:40.270> information<00:16:41.270> on<00:16:43.720> on<00:16:44.720> particular 00:16:45.430 --> 00:16:45.440 align:start position:0% financial information on on particular 00:16:45.440 --> 00:16:48.060 align:start position:0% financial information on on particular coins<00:16:45.890> and<00:16:46.340> they're<00:16:47.060> they're<00:16:47.600> also<00:16:47.780> showing 00:16:48.060 --> 00:16:48.070 align:start position:0% coins and they're they're also showing 00:16:48.070 --> 00:16:50.860 align:start position:0% coins and they're they're also showing developer<00:16:49.070> activity<00:16:49.640> you<00:16:50.330> know<00:16:50.450> where<00:16:50.660> your 00:16:50.860 --> 00:16:50.870 align:start position:0% developer activity you know where your 00:16:50.870 --> 00:16:54.040 align:start position:0% developer activity you know where your repositories<00:16:51.620> are<00:16:52.240> you<00:16:53.240> know<00:16:53.330> how<00:16:53.600> many<00:16:53.780> how 00:16:54.040 --> 00:16:54.050 align:start position:0% repositories are you know how many how 00:16:54.050 --> 00:16:56.440 align:start position:0% repositories are you know how many how many<00:16:54.370> what<00:16:55.370> you<00:16:55.460> what<00:16:55.790> your<00:16:55.910> transaction 00:16:56.440 --> 00:16:56.450 align:start position:0% many what you what your transaction 00:16:56.450 --> 00:16:59.350 align:start position:0% many what you what your transaction rates<00:16:56.660> are<00:16:56.840> and<00:16:57.140> a<00:16:57.500> lot<00:16:57.740> of<00:16:57.770> information<00:16:58.360> about 00:16:59.350 --> 00:16:59.360 align:start position:0% rates are and a lot of information about 00:16:59.360 --> 00:17:01.540 align:start position:0% rates are and a lot of information about how<00:16:59.930> the<00:16:59.990> governance<00:17:00.530> works<00:17:00.860> what<00:17:01.280> legal 00:17:01.540 --> 00:17:01.550 align:start position:0% how the governance works what legal 00:17:01.550 --> 00:17:03.490 align:start position:0% how the governance works what legal entities<00:17:02.090> are<00:17:02.210> involved<00:17:02.510> how<00:17:02.840> decisions<00:17:03.200> are 00:17:03.490 --> 00:17:03.500 align:start position:0% entities are involved how decisions are 00:17:03.500 --> 00:17:07.000 align:start position:0% entities are involved how decisions are made<00:17:03.560> what<00:17:04.459> the<00:17:04.610> issuance<00:17:05.030> is<00:17:05.270> and<00:17:05.600> so<00:17:05.870> on 00:17:07.000 --> 00:17:07.010 align:start position:0% made what the issuance is and so on 00:17:07.010 --> 00:17:09.069 align:start position:0% made what the issuance is and so on there<00:17:07.760> hasn't<00:17:07.970> been<00:17:08.150> high-quality 00:17:09.069 --> 00:17:09.079 align:start position:0% there hasn't been high-quality 00:17:09.079 --> 00:17:13.660 align:start position:0% there hasn't been high-quality information<00:17:09.610> on<00:17:10.990> on<00:17:11.990> classic<00:17:12.620> and<00:17:12.860> and 00:17:13.660 --> 00:17:13.670 align:start position:0% information on on classic and and 00:17:13.670 --> 00:17:15.250 align:start position:0% information on on classic and and something<00:17:14.270> as<00:17:14.480> simple<00:17:14.689> as<00:17:14.870> the<00:17:15.020> fact<00:17:15.199> that 00:17:15.250 --> 00:17:15.260 align:start position:0% something as simple as the fact that 00:17:15.260 --> 00:17:16.960 align:start position:0% something as simple as the fact that we've<00:17:15.439> had<00:17:15.470> sort<00:17:15.800> of<00:17:15.860> messed<00:17:16.100> up<00:17:16.220> repositories 00:17:16.960 --> 00:17:16.970 align:start position:0% we've had sort of messed up repositories 00:17:16.970 --> 00:17:18.960 align:start position:0% we've had sort of messed up repositories and<00:17:17.209> things<00:17:17.930> have<00:17:18.079> been<00:17:18.199> pointing<00:17:18.709> at 00:17:18.960 --> 00:17:18.970 align:start position:0% and things have been pointing at 00:17:18.970 --> 00:17:21.490 align:start position:0% and things have been pointing at aetherium<00:17:19.970> project<00:17:20.630> where<00:17:20.990> actually<00:17:21.380> the 00:17:21.490 --> 00:17:21.500 align:start position:0% aetherium project where actually the 00:17:21.500 --> 00:17:23.110 align:start position:0% aetherium project where actually the work<00:17:21.620> is<00:17:21.800> happening<00:17:21.949> in<00:17:22.250> aetherium<00:17:22.520> classic 00:17:23.110 --> 00:17:23.120 align:start position:0% work is happening in aetherium classic 00:17:23.120 --> 00:17:26.980 align:start position:0% work is happening in aetherium classic or<00:17:23.329> in<00:17:23.680> another<00:17:24.680> area<00:17:25.160> you<00:17:25.569> get<00:17:26.569> this<00:17:26.720> false 00:17:26.980 --> 00:17:26.990 align:start position:0% or in another area you get this false 00:17:26.990 --> 00:17:28.630 align:start position:0% or in another area you get this false data<00:17:27.260> saying<00:17:27.680> hey<00:17:27.949> there's<00:17:28.160> no<00:17:28.280> developer 00:17:28.630 --> 00:17:28.640 align:start position:0% data saying hey there's no developer 00:17:28.640 --> 00:17:30.370 align:start position:0% data saying hey there's no developer activity<00:17:29.060> there's<00:17:29.270> no<00:17:29.390> being<00:17:29.570> there's<00:17:29.840> no<00:17:29.870> no 00:17:30.370 --> 00:17:30.380 align:start position:0% activity there's no being there's no no 00:17:30.380 --> 00:17:31.930 align:start position:0% activity there's no being there's no no commits<00:17:30.680> have<00:17:30.860> happened<00:17:31.190> and<00:17:31.550> that's<00:17:31.760> just 00:17:31.930 --> 00:17:31.940 align:start position:0% commits have happened and that's just 00:17:31.940 --> 00:17:36.100 align:start position:0% commits have happened and that's just wrong<00:17:32.440> and<00:17:33.970> and<00:17:34.970> and<00:17:35.300> but<00:17:35.600> really<00:17:35.840> having<00:17:36.080> that 00:17:36.100 --> 00:17:36.110 align:start position:0% wrong and and and but really having that 00:17:36.110 --> 00:17:37.480 align:start position:0% wrong and and and but really having that public<00:17:36.500> disclosure<00:17:36.890> is<00:17:37.070> something<00:17:37.310> that's 00:17:37.480 --> 00:17:37.490 align:start position:0% public disclosure is something that's 00:17:37.490 --> 00:17:39.160 align:start position:0% public disclosure is something that's very<00:17:37.640> important<00:17:38.300> to<00:17:38.420> me<00:17:38.450> I've<00:17:38.900> been 00:17:39.160 --> 00:17:39.170 align:start position:0% very important to me I've been 00:17:39.170 --> 00:17:40.980 align:start position:0% very important to me I've been maintaining<00:17:39.410> this<00:17:39.890> conflict<00:17:40.370> of<00:17:40.430> interests 00:17:40.980 --> 00:17:40.990 align:start position:0% maintaining this conflict of interests 00:17:40.990 --> 00:17:44.950 align:start position:0% maintaining this conflict of interests statement<00:17:41.990> myself<00:17:42.970> for<00:17:43.970> two<00:17:44.090> years<00:17:44.360> now<00:17:44.570> where 00:17:44.950 --> 00:17:44.960 align:start position:0% statement myself for two years now where 00:17:44.960 --> 00:17:47.560 align:start position:0% statement myself for two years now where I<00:17:44.990> list<00:17:45.470> essentially<00:17:46.460> all<00:17:46.700> of<00:17:46.880> my<00:17:47.000> financial 00:17:47.560 --> 00:17:47.570 align:start position:0% I list essentially all of my financial 00:17:47.570 --> 00:17:50.080 align:start position:0% I list essentially all of my financial arrangements<00:17:48.350> all<00:17:48.500> of<00:17:48.620> my<00:17:48.740> associations<00:17:49.490> all 00:17:50.080 --> 00:17:50.090 align:start position:0% arrangements all of my associations all 00:17:50.090 --> 00:17:53.050 align:start position:0% arrangements all of my associations all of<00:17:50.360> my<00:17:50.510> historical<00:17:50.900> salaries<00:17:51.890> my<00:17:52.640> crypto 00:17:53.050 --> 00:17:53.060 align:start position:0% of my historical salaries my crypto 00:17:53.060 --> 00:17:53.980 align:start position:0% of my historical salaries my crypto holdings<00:17:53.540> my 00:17:53.980 --> 00:17:53.990 align:start position:0% holdings my 00:17:53.990 --> 00:17:57.390 align:start position:0% holdings my tax<00:17:54.200> filings<00:17:54.710> everything<00:17:55.900> because<00:17:56.900> I<00:17:57.020> think 00:17:57.390 --> 00:17:57.400 align:start position:0% tax filings everything because I think 00:17:57.400 --> 00:18:00.910 align:start position:0% tax filings everything because I think that<00:17:58.400> in<00:17:58.580> a<00:17:58.700> in<00:17:58.970> a<00:17:59.090> sea<00:17:59.330> of<00:17:59.360> scammers<00:17:59.990> you 00:18:00.910 --> 00:18:00.920 align:start position:0% that in a in a sea of scammers you 00:18:00.920 --> 00:18:03.010 align:start position:0% that in a in a sea of scammers you distinguish<00:18:01.429> yourself<00:18:01.820> by<00:18:02.420> being 00:18:03.010 --> 00:18:03.020 align:start position:0% distinguish yourself by being 00:18:03.020 --> 00:18:07.060 align:start position:0% distinguish yourself by being transparent<00:18:05.320> so<00:18:06.320> that's<00:18:06.500> what<00:18:06.679> we've<00:18:06.830> been<00:18:06.950> up 00:18:07.060 --> 00:18:07.070 align:start position:0% transparent so that's what we've been up 00:18:07.070 --> 00:18:09.990 align:start position:0% transparent so that's what we've been up to 00:18:09.990 --> 00:18:10.000 align:start position:0% 00:18:10.000 --> 00:18:13.410 align:start position:0% we've<00:18:11.000> got<00:18:11.179> pending<00:18:11.600> changes<00:18:11.990> you<00:18:12.950> know<00:18:13.040> I 00:18:13.410 --> 00:18:13.420 align:start position:0% we've got pending changes you know I 00:18:13.420 --> 00:18:15.669 align:start position:0% we've got pending changes you know I were<00:18:14.420> basically<00:18:14.600> I<00:18:14.870> think<00:18:15.200> going<00:18:15.320> a<00:18:15.440> fast 00:18:15.669 --> 00:18:15.679 align:start position:0% were basically I think going a fast 00:18:15.679 --> 00:18:18.370 align:start position:0% were basically I think going a fast follow<00:18:15.920> Istanbul<00:18:16.460> so<00:18:17.420> within<00:18:17.780> a<00:18:17.960> few<00:18:18.170> months 00:18:18.370 --> 00:18:18.380 align:start position:0% follow Istanbul so within a few months 00:18:18.380 --> 00:18:22.210 align:start position:0% follow Istanbul so within a few months et<00:18:19.160> Cie<00:18:19.340> is<00:18:19.490> going<00:18:19.640> to<00:18:19.700> be<00:18:19.790> caught<00:18:20.179> up<00:18:20.710> and<00:18:21.710> you 00:18:22.210 --> 00:18:22.220 align:start position:0% et Cie is going to be caught up and you 00:18:22.220 --> 00:18:23.799 align:start position:0% et Cie is going to be caught up and you know<00:18:22.340> moving<00:18:22.850> between<00:18:22.970> chains<00:18:23.390> is<00:18:23.600> going<00:18:23.750> to 00:18:23.799 --> 00:18:23.809 align:start position:0% know moving between chains is going to 00:18:23.809 --> 00:18:26.049 align:start position:0% know moving between chains is going to be<00:18:23.900> very<00:18:24.380> trivial<00:18:24.740> and<00:18:25.160> beyond<00:18:25.400> catching<00:18:25.940> up 00:18:26.049 --> 00:18:26.059 align:start position:0% be very trivial and beyond catching up 00:18:26.059 --> 00:18:27.370 align:start position:0% be very trivial and beyond catching up we're<00:18:26.270> actually<00:18:26.390> going<00:18:26.750> to<00:18:26.809> have<00:18:26.870> you<00:18:27.230> know<00:18:27.260> a 00:18:27.370 --> 00:18:27.380 align:start position:0% we're actually going to have you know a 00:18:27.380 --> 00:18:31.290 align:start position:0% we're actually going to have you know a few<00:18:27.770> a<00:18:27.950> few<00:18:27.980> further<00:18:28.400> changes<00:18:28.940> so<00:18:29.570> amazingly 00:18:31.290 --> 00:18:31.300 align:start position:0% few a few further changes so amazingly 00:18:31.300 --> 00:18:33.790 align:start position:0% few a few further changes so amazingly perhaps<00:18:32.300> etc'<00:18:32.990> is<00:18:33.110> actually<00:18:33.440> going<00:18:33.559> to<00:18:33.679> be 00:18:33.790 --> 00:18:33.800 align:start position:0% perhaps etc' is actually going to be 00:18:33.800 --> 00:18:37.060 align:start position:0% perhaps etc' is actually going to be objectively<00:18:34.610> better<00:18:34.970> than<00:18:35.840> f1<00:18:36.110> within<00:18:36.830> a<00:18:36.920> few 00:18:37.060 --> 00:18:37.070 align:start position:0% objectively better than f1 within a few 00:18:37.070 --> 00:18:38.260 align:start position:0% objectively better than f1 within a few months<00:18:37.340> which<00:18:37.520> i<00:18:37.640> think<00:18:37.700> is<00:18:37.880> going<00:18:38.000> to<00:18:38.059> blow 00:18:38.260 --> 00:18:38.270 align:start position:0% months which i think is going to blow 00:18:38.270 --> 00:18:41.350 align:start position:0% months which i think is going to blow people's<00:18:38.630> minds<00:18:39.080> gas<00:18:39.890> prices<00:18:40.429> will<00:18:41.240> be<00:18:41.270> lower 00:18:41.350 --> 00:18:41.360 align:start position:0% people's minds gas prices will be lower 00:18:41.360 --> 00:18:43.750 align:start position:0% people's minds gas prices will be lower the<00:18:42.200> bloat<00:18:42.470> will<00:18:42.740> not<00:18:42.920> be<00:18:43.040> there<00:18:43.220> the 00:18:43.750 --> 00:18:43.760 align:start position:0% the bloat will not be there the 00:18:43.760 --> 00:18:46.120 align:start position:0% the bloat will not be there the irregular<00:18:44.240> state<00:18:44.770> transaction<00:18:45.770> will<00:18:45.890> not<00:18:46.040> be 00:18:46.120 --> 00:18:46.130 align:start position:0% irregular state transaction will not be 00:18:46.130 --> 00:18:50.830 align:start position:0% irregular state transaction will not be there<00:18:46.510> and<00:18:48.429> state<00:18:49.429> channels<00:18:49.820> work<00:18:50.090> there's<00:18:50.690> no 00:18:50.830 --> 00:18:50.840 align:start position:0% there and state channels work there's no 00:18:50.840 --> 00:18:52.690 align:start position:0% there and state channels work there's no need<00:18:51.050> to<00:18:51.080> blow<00:18:51.380> at<00:18:51.530> the<00:18:51.559> l1<00:18:51.980> because<00:18:52.429> we've<00:18:52.580> got 00:18:52.690 --> 00:18:52.700 align:start position:0% need to blow at the l1 because we've got 00:18:52.700 --> 00:18:56.950 align:start position:0% need to blow at the l1 because we've got working<00:18:52.880> state<00:18:53.240> channels<00:18:53.630> now<00:18:54.010> and<00:18:55.840> you<00:18:56.840> know 00:18:56.950 --> 00:18:56.960 align:start position:0% working state channels now and you know 00:18:56.960 --> 00:18:59.230 align:start position:0% working state channels now and you know so<00:18:57.170> I<00:18:57.200> think<00:18:57.470> in<00:18:57.559> a<00:18:57.620> few<00:18:57.740> months<00:18:57.920> time<00:18:58.240> we're 00:18:59.230 --> 00:18:59.240 align:start position:0% so I think in a few months time we're 00:18:59.240 --> 00:19:00.940 align:start position:0% so I think in a few months time we're going<00:18:59.390> to<00:18:59.450> be<00:18:59.570> in<00:18:59.840> a<00:18:59.929> in<00:19:00.200> a<00:19:00.260> really<00:19:00.440> great<00:19:00.710> place 00:19:00.940 --> 00:19:00.950 align:start position:0% going to be in a in a really great place 00:19:00.950 --> 00:19:02.140 align:start position:0% going to be in a in a really great place and<00:19:01.190> people<00:19:01.340> are<00:19:01.610> going<00:19:01.790> to<00:19:01.850> be<00:19:01.940> very 00:19:02.140 --> 00:19:02.150 align:start position:0% and people are going to be very 00:19:02.150 --> 00:19:04.960 align:start position:0% and people are going to be very surprised<00:19:02.630> to<00:19:02.929> say<00:19:03.140> even<00:19:03.950> if<00:19:04.040> you<00:19:04.190> don't<00:19:04.760> have 00:19:04.960 --> 00:19:04.970 align:start position:0% surprised to say even if you don't have 00:19:04.970 --> 00:19:08.049 align:start position:0% surprised to say even if you don't have any<00:19:05.300> ideological<00:19:05.980> alignment<00:19:06.980> it's<00:19:07.790> just 00:19:08.049 --> 00:19:08.059 align:start position:0% any ideological alignment it's just 00:19:08.059 --> 00:19:10.960 align:start position:0% any ideological alignment it's just maybe<00:19:08.480> a<00:19:08.600> better<00:19:08.809> deployment<00:19:09.710> choice<00:19:09.970> okay 00:19:10.960 --> 00:19:10.970 align:start position:0% maybe a better deployment choice okay 00:19:10.970 --> 00:19:13.570 align:start position:0% maybe a better deployment choice okay and<00:19:11.179> there's<00:19:11.300> my<00:19:11.420> time<00:19:11.630> up<00:19:12.160> has<00:19:13.160> anyone<00:19:13.429> got 00:19:13.570 --> 00:19:13.580 align:start position:0% and there's my time up has anyone got 00:19:13.580 --> 00:19:18.280 align:start position:0% and there's my time up has anyone got any<00:19:13.610> quick<00:19:13.970> questions<00:19:15.340> yep<00:19:16.340> so<00:19:17.020> Masari<00:19:18.020> will 00:19:18.280 --> 00:19:18.290 align:start position:0% any quick questions yep so Masari will 00:19:18.290 --> 00:19:20.740 align:start position:0% any quick questions yep so Masari will have<00:19:18.500> that<00:19:18.650> information<00:19:19.270> generally<00:19:20.270> speaking 00:19:20.740 --> 00:19:20.750 align:start position:0% have that information generally speaking 00:19:20.750 --> 00:19:22.960 align:start position:0% have that information generally speaking I<00:19:20.929> believe<00:19:21.290> we've<00:19:21.500> got<00:19:21.530> a<00:19:21.679> reasonable<00:19:22.670> amount 00:19:22.960 --> 00:19:22.970 align:start position:0% I believe we've got a reasonable amount 00:19:22.970 --> 00:19:24.669 align:start position:0% I believe we've got a reasonable amount of<00:19:23.090> transactions<00:19:23.750> but<00:19:23.900> they're<00:19:24.080> primarily 00:19:24.669 --> 00:19:24.679 align:start position:0% of transactions but they're primarily 00:19:24.679 --> 00:19:28.299 align:start position:0% of transactions but they're primarily value<00:19:25.250> transfers<00:19:25.790> there<00:19:26.720> is<00:19:26.870> a<00:19:27.140> dap<00:19:27.470> ecosystem 00:19:28.299 --> 00:19:28.309 align:start position:0% value transfers there is a dap ecosystem 00:19:28.309 --> 00:19:32.770 align:start position:0% value transfers there is a dap ecosystem but<00:19:28.460> it's<00:19:29.170> weak<00:19:30.700> and<00:19:31.700> that<00:19:31.880> really<00:19:32.210> is<00:19:32.390> because 00:19:32.770 --> 00:19:32.780 align:start position:0% but it's weak and that really is because 00:19:32.780 --> 00:19:34.630 align:start position:0% but it's weak and that really is because these<00:19:33.470> foundational<00:19:34.220> things<00:19:34.429> have<00:19:34.550> been 00:19:34.630 --> 00:19:34.640 align:start position:0% these foundational things have been 00:19:34.640 --> 00:19:36.700 align:start position:0% these foundational things have been missing<00:19:35.059> you<00:19:35.210> know<00:19:35.690> when<00:19:36.200> we're<00:19:36.410> at<00:19:36.530> that 00:19:36.700 --> 00:19:36.710 align:start position:0% missing you know when we're at that 00:19:36.710 --> 00:19:38.799 align:start position:0% missing you know when we're at that point<00:19:37.010> of<00:19:37.250> having<00:19:37.790> those<00:19:38.030> foundations<00:19:38.660> i 00:19:38.799 --> 00:19:38.809 align:start position:0% point of having those foundations i 00:19:38.809 --> 00:19:40.750 align:start position:0% point of having those foundations i think<00:19:39.020> we<00:19:39.140> are<00:19:39.620> going<00:19:39.679> to<00:19:40.100> get<00:19:40.190> an<00:19:40.400> awful<00:19:40.700> lot 00:19:40.750 --> 00:19:40.760 align:start position:0% think we are going to get an awful lot 00:19:40.760 --> 00:19:43.690 align:start position:0% think we are going to get an awful lot of<00:19:40.850> DAP<00:19:41.510> developers<00:19:42.050> supporting<00:19:43.040> both<00:19:43.250> moving 00:19:43.690 --> 00:19:43.700 align:start position:0% of DAP developers supporting both moving 00:19:43.700 --> 00:19:47.169 align:start position:0% of DAP developers supporting both moving over<00:19:44.950> really<00:19:45.950> because<00:19:46.220> it's<00:19:46.370> easy<00:19:46.550> to<00:19:46.790> do<00:19:46.940> so 00:19:47.169 --> 00:19:47.179 align:start position:0% over really because it's easy to do so 00:19:47.179 --> 00:19:48.970 align:start position:0% over really because it's easy to do so and<00:19:47.420> it's<00:19:47.570> gonna<00:19:47.690> be<00:19:47.870> sort<00:19:48.200> of<00:19:48.230> cheaper<00:19:48.890> and 00:19:48.970 --> 00:19:48.980 align:start position:0% and it's gonna be sort of cheaper and 00:19:48.980 --> 00:19:51.640 align:start position:0% and it's gonna be sort of cheaper and cheaper<00:19:49.220> and<00:19:49.820> better<00:19:50.290> there's<00:19:51.290> lots<00:19:51.500> of 00:19:51.640 --> 00:19:51.650 align:start position:0% cheaper and better there's lots of 00:19:51.650 --> 00:19:53.080 align:start position:0% cheaper and better there's lots of things<00:19:51.890> that<00:19:51.980> are<00:19:52.130> being<00:19:52.280> doing<00:19:52.580> to<00:19:52.730> help<00:19:52.880> that 00:19:53.080 --> 00:19:53.090 align:start position:0% things that are being doing to help that 00:19:53.090 --> 00:19:56.200 align:start position:0% things that are being doing to help that onboarding<00:19:53.600> some<00:19:54.260> of<00:19:54.380> which<00:19:54.700> terry<00:19:55.700> announced 00:19:56.200 --> 00:19:56.210 align:start position:0% onboarding some of which terry announced 00:19:56.210 --> 00:20:02.700 align:start position:0% onboarding some of which terry announced earlier<00:19:56.660> like<00:19:57.370> like<00:19:58.370> get<00:19:58.880> coin<00:19:59.410> swarm<00:20:00.410> support 00:20:02.700 --> 00:20:02.710 align:start position:0% earlier like like get coin swarm support 00:20:02.710 --> 00:20:05.680 align:start position:0% earlier like like get coin swarm support with<00:20:03.710> meta<00:20:04.070> masks<00:20:04.370> I<00:20:04.580> think<00:20:04.790> we<00:20:04.910> can<00:20:05.300> get<00:20:05.480> meta 00:20:05.680 --> 00:20:05.690 align:start position:0% with meta masks I think we can get meta 00:20:05.690 --> 00:20:07.720 align:start position:0% with meta masks I think we can get meta masks<00:20:05.929> really<00:20:06.530> very<00:20:06.710> soon<00:20:07.010> with 00:20:07.720 --> 00:20:07.730 align:start position:0% masks really very soon with 00:20:07.730 --> 00:20:11.160 align:start position:0% masks really very soon with some<00:20:07.820> of<00:20:07.910> the<00:20:08.000> changes<00:20:08.360> that<00:20:08.480> they<00:20:08.660> announce 00:20:11.160 --> 00:20:11.170 align:start position:0% some of the changes that they announce 00:20:11.170 --> 00:20:15.040 align:start position:0% some of the changes that they announce so<00:20:12.170> I<00:20:12.680> think<00:20:13.250> we<00:20:13.490> can<00:20:13.610> have<00:20:13.760> a<00:20:13.790> Moloch<00:20:14.120> Dow<00:20:14.330> for 00:20:15.040 --> 00:20:15.050 align:start position:0% so I think we can have a Moloch Dow for 00:20:15.050 --> 00:20:17.230 align:start position:0% so I think we can have a Moloch Dow for funding<00:20:15.410> a<00:20:15.650> whole<00:20:16.280> range<00:20:16.520> of<00:20:16.700> things<00:20:16.760> which 00:20:17.230 --> 00:20:17.240 align:start position:0% funding a whole range of things which 00:20:17.240 --> 00:20:20.440 align:start position:0% funding a whole range of things which you<00:20:18.170> know<00:20:18.290> really<00:20:19.160> should<00:20:19.400> be<00:20:19.520> the<00:20:19.700> story 00:20:20.440 --> 00:20:20.450 align:start position:0% you know really should be the story 00:20:20.450 --> 00:20:21.970 align:start position:0% you know really should be the story should<00:20:20.720> be<00:20:20.840> all<00:20:20.990> of<00:20:21.020> the<00:20:21.260> tools<00:20:21.470> that<00:20:21.590> you<00:20:21.710> love 00:20:21.970 --> 00:20:21.980 align:start position:0% should be all of the tools that you love 00:20:21.980 --> 00:20:28.180 align:start position:0% should be all of the tools that you love on<00:20:22.100> aetherium<00:20:23.830> same<00:20:24.830> deal<00:20:25.010> on<00:20:25.220> classic<00:20:26.380> so<00:20:27.380> 51% 00:20:28.180 --> 00:20:28.190 align:start position:0% on aetherium same deal on classic so 51% 00:20:28.190 --> 00:20:30.460 align:start position:0% on aetherium same deal on classic so 51% attacks<00:20:28.490> are<00:20:28.670> possible<00:20:28.790> on<00:20:29.120> any<00:20:29.270> chain<00:20:29.630> that's 00:20:30.460 --> 00:20:30.470 align:start position:0% attacks are possible on any chain that's 00:20:30.470 --> 00:20:34.090 align:start position:0% attacks are possible on any chain that's the<00:20:30.650> nature<00:20:30.830> of<00:20:31.120> proof<00:20:32.120> of<00:20:32.270> work<00:20:33.100> something 00:20:34.090 --> 00:20:34.100 align:start position:0% the nature of proof of work something 00:20:34.100 --> 00:20:35.830 align:start position:0% the nature of proof of work something though<00:20:34.370> that<00:20:34.760> I<00:20:34.790> think<00:20:35.030> maybe<00:20:35.240> people<00:20:35.570> don't 00:20:35.830 --> 00:20:35.840 align:start position:0% though that I think maybe people don't 00:20:35.840 --> 00:20:38.770 align:start position:0% though that I think maybe people don't kind<00:20:36.230> of<00:20:36.320> clock<00:20:36.620> is<00:20:36.830> that<00:20:36.970> 51%<00:20:37.970> attacks<00:20:38.630> are 00:20:38.770 --> 00:20:38.780 align:start position:0% kind of clock is that 51% attacks are 00:20:38.780 --> 00:20:40.480 align:start position:0% kind of clock is that 51% attacks are not<00:20:38.930> necessarily<00:20:39.410> disastrous<00:20:40.190> to<00:20:40.400> the 00:20:40.480 --> 00:20:40.490 align:start position:0% not necessarily disastrous to the 00:20:40.490 --> 00:20:43.030 align:start position:0% not necessarily disastrous to the network<00:20:40.820> they<00:20:41.450> attack<00:20:41.810> single<00:20:42.440> participants 00:20:43.030 --> 00:20:43.040 align:start position:0% network they attack single participants 00:20:43.040 --> 00:20:46.390 align:start position:0% network they attack single participants who<00:20:43.340> have<00:20:43.520> poor<00:20:43.850> trust<00:20:44.690> models<00:20:45.400> Pacific's 00:20:46.390 --> 00:20:46.400 align:start position:0% who have poor trust models Pacific's 00:20:46.400 --> 00:20:48.760 align:start position:0% who have poor trust models Pacific's specifically<00:20:46.940> usually<00:20:47.300> exchanges<00:20:48.110> you<00:20:48.680> know 00:20:48.760 --> 00:20:48.770 align:start position:0% specifically usually exchanges you know 00:20:48.770 --> 00:20:51.370 align:start position:0% specifically usually exchanges you know in<00:20:48.890> exchange<00:20:49.310> who<00:20:49.580> has<00:20:49.790> received<00:20:50.420> stuff<00:20:51.140> and 00:20:51.370 --> 00:20:51.380 align:start position:0% in exchange who has received stuff and 00:20:51.380 --> 00:20:52.660 align:start position:0% in exchange who has received stuff and and<00:20:51.650> you<00:20:51.800> know<00:20:51.920> release<00:20:52.190> things<00:20:52.430> without 00:20:52.660 --> 00:20:52.670 align:start position:0% and you know release things without 00:20:52.670 --> 00:20:54.370 align:start position:0% and you know release things without waiting<00:20:53.180> a<00:20:53.390> suitable<00:20:53.780> amount<00:20:53.840> of<00:20:54.110> of 00:20:54.370 --> 00:20:54.380 align:start position:0% waiting a suitable amount of of 00:20:54.380 --> 00:20:56.740 align:start position:0% waiting a suitable amount of of confirmations<00:20:55.100> if<00:20:55.460> you<00:20:55.970> have<00:20:56.090> less<00:20:56.330> hash 00:20:56.740 --> 00:20:56.750 align:start position:0% confirmations if you have less hash 00:20:56.750 --> 00:20:58.810 align:start position:0% confirmations if you have less hash power<00:20:56.990> well<00:20:57.290> you<00:20:57.530> you<00:20:58.160> really<00:20:58.340> need<00:20:58.580> to<00:20:58.670> wait 00:20:58.810 --> 00:20:58.820 align:start position:0% power well you you really need to wait 00:20:58.820 --> 00:21:01.210 align:start position:0% power well you you really need to wait for<00:20:58.970> a<00:20:59.030> lot<00:20:59.150> more<00:20:59.300> confirms<00:21:00.220> before 00:21:01.210 --> 00:21:01.220 align:start position:0% for a lot more confirms before 00:21:01.220 --> 00:21:04.180 align:start position:0% for a lot more confirms before proceeding<00:21:02.210> I<00:21:02.600> mean<00:21:03.440> that's<00:21:03.650> the<00:21:03.860> source<00:21:04.040> of 00:21:04.180 --> 00:21:04.190 align:start position:0% proceeding I mean that's the source of 00:21:04.190 --> 00:21:06.370 align:start position:0% proceeding I mean that's the source of stuff<00:21:04.370> that<00:21:04.550> only<00:21:04.790> really<00:21:05.150> generally<00:21:05.720> effects 00:21:06.370 --> 00:21:06.380 align:start position:0% stuff that only really generally effects 00:21:06.380 --> 00:21:09.640 align:start position:0% stuff that only really generally effects you<00:21:07.310> know<00:21:07.430> large<00:21:07.730> value<00:21:08.270> transfers<00:21:08.840> if<00:21:09.380> you're 00:21:09.640 --> 00:21:09.650 align:start position:0% you know large value transfers if you're 00:21:09.650 --> 00:21:12.160 align:start position:0% you know large value transfers if you're just<00:21:09.860> doing<00:21:10.100> little<00:21:10.520> state<00:21:10.880> changes<00:21:11.480> of<00:21:11.780> you 00:21:12.160 --> 00:21:12.170 align:start position:0% just doing little state changes of you 00:21:12.170 --> 00:21:15.610 align:start position:0% just doing little state changes of you know<00:21:12.290> Dappy<00:21:12.710> stuff<00:21:14.050> you<00:21:15.050> know<00:21:15.200> just<00:21:15.470> don't 00:21:15.610 --> 00:21:15.620 align:start position:0% know Dappy stuff you know just don't 00:21:15.620 --> 00:21:17.290 align:start position:0% know Dappy stuff you know just don't wait<00:21:15.860> a<00:21:15.890> lot<00:21:16.070> of<00:21:16.160> confirms<00:21:16.550> anyway<00:21:16.940> I<00:21:16.970> mean<00:21:17.210> I 00:21:17.290 --> 00:21:17.300 align:start position:0% wait a lot of confirms anyway I mean I 00:21:17.300 --> 00:21:20.080 align:start position:0% wait a lot of confirms anyway I mean I guess<00:21:17.480> it's<00:21:17.630> like<00:21:17.780> well<00:21:18.020> you<00:21:18.730> know<00:21:19.730> a<00:21:19.760> bus<00:21:20.060> pass 00:21:20.080 --> 00:21:20.090 align:start position:0% guess it's like well you know a bus pass 00:21:20.090 --> 00:21:23.470 align:start position:0% guess it's like well you know a bus pass or<00:21:20.630> whatever<00:21:20.930> it<00:21:21.140> is<00:21:21.170> money<00:21:22.000> it's<00:21:23.000> not<00:21:23.180> hard 00:21:23.470 --> 00:21:23.480 align:start position:0% or whatever it is money it's not hard 00:21:23.480 --> 00:21:25.450 align:start position:0% or whatever it is money it's not hard money<00:21:23.750> but<00:21:24.110> that's<00:21:24.320> fine<00:21:24.620> you<00:21:25.160> know<00:21:25.280> not 00:21:25.450 --> 00:21:25.460 align:start position:0% money but that's fine you know not 00:21:25.460 --> 00:21:28.030 align:start position:0% money but that's fine you know not everything<00:21:25.820> has<00:21:26.030> to<00:21:26.060> be<00:21:26.270> rock-hard<00:21:26.960> money<00:21:27.260> so 00:21:28.030 --> 00:21:28.040 align:start position:0% everything has to be rock-hard money so 00:21:28.040 --> 00:21:29.470 align:start position:0% everything has to be rock-hard money so I<00:21:28.070> think<00:21:28.340> you<00:21:28.490> know<00:21:28.610> the<00:21:28.730> answer<00:21:29.060> is<00:21:29.090> that<00:21:29.360> you 00:21:29.470 --> 00:21:29.480 align:start position:0% I think you know the answer is that you 00:21:29.480 --> 00:21:31.930 align:start position:0% I think you know the answer is that you you<00:21:29.720> you<00:21:29.750> are<00:21:29.990> gonna<00:21:30.200> have<00:21:30.350> that<00:21:30.820> security<00:21:31.820> at 00:21:31.930 --> 00:21:31.940 align:start position:0% you you are gonna have that security at 00:21:31.940 --> 00:21:33.640 align:start position:0% you you are gonna have that security at the<00:21:32.030> bottom<00:21:32.270> layer<00:21:32.510> and<00:21:32.870> you<00:21:33.020> know<00:21:33.380> you<00:21:33.440> get 00:21:33.640 --> 00:21:33.650 align:start position:0% the bottom layer and you know you get 00:21:33.650 --> 00:21:36.820 align:start position:0% the bottom layer and you know you get less<00:21:34.070> and<00:21:34.100> less<00:21:34.480> as<00:21:35.480> you<00:21:35.750> as<00:21:36.020> you<00:21:36.470> go<00:21:36.590> higher<00:21:36.800> up 00:21:36.820 --> 00:21:36.830 align:start position:0% less and less as you as you go higher up 00:21:36.830 --> 00:21:38.650 align:start position:0% less and less as you as you go higher up and<00:21:37.220> really<00:21:37.880> the<00:21:38.000> thing<00:21:38.210> that<00:21:38.360> is<00:21:38.450> going<00:21:38.600> to 00:21:38.650 --> 00:21:38.660 align:start position:0% and really the thing that is going to 00:21:38.660 --> 00:21:41.050 align:start position:0% and really the thing that is going to get<00:21:38.780> that<00:21:38.960> security<00:21:39.350> is<00:21:39.860> having<00:21:40.700> more<00:21:40.820> hash 00:21:41.050 --> 00:21:41.060 align:start position:0% get that security is having more hash 00:21:41.060 --> 00:21:43.780 align:start position:0% get that security is having more hash power<00:21:41.360> and<00:21:41.630> that<00:21:42.230> will<00:21:42.470> happen<00:21:42.680> as<00:21:43.100> the 00:21:43.780 --> 00:21:43.790 align:start position:0% power and that will happen as the 00:21:43.790 --> 00:21:45.910 align:start position:0% power and that will happen as the developers<00:21:44.210> come<00:21:44.390> over<00:21:44.690> as<00:21:45.290> more<00:21:45.620> and<00:21:45.800> more 00:21:45.910 --> 00:21:45.920 align:start position:0% developers come over as more and more 00:21:45.920 --> 00:21:47.800 align:start position:0% developers come over as more and more activities<00:21:46.220> happening<00:21:46.880> that<00:21:47.300> attracts<00:21:47.660> the 00:21:47.800 --> 00:21:47.810 align:start position:0% activities happening that attracts the 00:21:47.810 --> 00:21:49.600 align:start position:0% activities happening that attracts the hash<00:21:48.020> that<00:21:48.350> gets<00:21:48.590> you<00:21:48.710> the<00:21:48.860> security<00:21:49.160> and 00:21:49.600 --> 00:21:49.610 align:start position:0% hash that gets you the security and 00:21:49.610 --> 00:21:51.400 align:start position:0% hash that gets you the security and there<00:21:50.180> is<00:21:50.300> no<00:21:50.510> other<00:21:50.540> answer<00:21:51.080> than<00:21:51.110> that 00:21:51.400 --> 00:21:51.410 align:start position:0% there is no other answer than that 00:21:51.410 --> 00:21:53.890 align:start position:0% there is no other answer than that really<00:21:51.710> for<00:21:52.040> for<00:21:52.670> powa<00:21:53.210> that's<00:21:53.360> the<00:21:53.510> nature<00:21:53.720> of 00:21:53.890 --> 00:21:53.900 align:start position:0% really for for powa that's the nature of 00:21:53.900 --> 00:21:56.920 align:start position:0% really for for powa that's the nature of it<00:21:54.670> so<00:21:55.670> we<00:21:55.790> have<00:21:55.910> to<00:21:56.000> get<00:21:56.120> the<00:21:56.240> activity<00:21:56.690> when 00:21:56.920 --> 00:21:56.930 align:start position:0% it so we have to get the activity when 00:21:56.930 --> 00:21:58.780 align:start position:0% it so we have to get the activity when we<00:21:57.020> get<00:21:57.170> the<00:21:57.260> activity<00:21:57.770> we'll<00:21:57.920> get<00:21:58.100> the<00:21:58.250> we'll 00:21:58.780 --> 00:21:58.790 align:start position:0% we get the activity we'll get the we'll 00:21:58.790 --> 00:22:01.320 align:start position:0% we get the activity we'll get the we'll get<00:21:58.910> the<00:21:59.030> hash<00:21:59.180> and<00:21:59.720> we'll<00:21:59.900> get<00:22:00.020> the<00:22:00.140> security 00:22:01.320 --> 00:22:01.330 align:start position:0% get the hash and we'll get the security 00:22:01.330 --> 00:22:03.330 align:start position:0% get the hash and we'll get the security thank<00:22:02.330> you 00:22:03.330 --> 00:22:03.340 align:start position:0% thank you 00:22:03.340 --> 00:22:11.820 align:start position:0% thank you [Applause] 00:22:11.820 --> 00:22:11.830 align:start position:0% 00:22:11.830 --> 00:22:13.890 align:start position:0% you