WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:01.699 align:start position:0% like<00:00:00.329> to<00:00:00.480> share<00:00:00.690> with<00:00:00.840> you<00:00:01.050> a<00:00:01.290> little<00:00:01.439> bit<00:00:01.680> of 00:00:01.699 --> 00:00:01.709 align:start position:0% like to share with you a little bit of 00:00:01.709 --> 00:00:05.869 align:start position:0% like to share with you a little bit of the<00:00:02.040> vision<00:00:02.700> of<00:00:02.820> the<00:00:02.879> EI<00:00:03.210> and<00:00:04.100> how<00:00:05.100> we<00:00:05.160> are 00:00:05.869 --> 00:00:05.879 align:start position:0% the vision of the EI and how we are 00:00:05.879 --> 00:00:08.000 align:start position:0% the vision of the EI and how we are working<00:00:06.180> toward<00:00:06.569> intersection<00:00:07.379> and<00:00:07.620> working 00:00:08.000 --> 00:00:08.010 align:start position:0% working toward intersection and working 00:00:08.010 --> 00:00:11.030 align:start position:0% working toward intersection and working collaboratively<00:00:08.550> with<00:00:10.040> aetherium 00:00:11.030 --> 00:00:11.040 align:start position:0% collaboratively with aetherium 00:00:11.040 --> 00:00:13.580 align:start position:0% collaboratively with aetherium Foundation<00:00:11.730> and<00:00:11.969> other<00:00:12.230> organizations<00:00:13.230> as 00:00:13.580 --> 00:00:13.590 align:start position:0% Foundation and other organizations as 00:00:13.590 --> 00:00:16.189 align:start position:0% Foundation and other organizations as well<00:00:14.009> moving<00:00:14.519> forward<00:00:15.080> just<00:00:16.080> a<00:00:16.170> little 00:00:16.189 --> 00:00:16.199 align:start position:0% well moving forward just a little 00:00:16.199 --> 00:00:19.130 align:start position:0% well moving forward just a little background<00:00:16.529> from<00:00:16.920> where<00:00:17.580> I<00:00:17.779> spent<00:00:18.779> 12<00:00:19.080> years 00:00:19.130 --> 00:00:19.140 align:start position:0% background from where I spent 12 years 00:00:19.140 --> 00:00:21.500 align:start position:0% background from where I spent 12 years in<00:00:19.350> in<00:00:19.560> town<00:00:19.770> and<00:00:20.189> the<00:00:20.340> telecom<00:00:20.939> side<00:00:21.330> of 00:00:21.500 --> 00:00:21.510 align:start position:0% in in town and the telecom side of 00:00:21.510 --> 00:00:23.750 align:start position:0% in in town and the telecom side of things<00:00:21.750> so<00:00:22.109> it's<00:00:22.710> very<00:00:22.859> interesting<00:00:23.189> in<00:00:23.609> my 00:00:23.750 --> 00:00:23.760 align:start position:0% things so it's very interesting in my 00:00:23.760 --> 00:00:26.450 align:start position:0% things so it's very interesting in my world<00:00:24.060> and<00:00:24.330> how<00:00:24.449> it<00:00:24.720> can<00:00:25.289> how<00:00:25.920> it<00:00:26.130> addresses 00:00:26.450 --> 00:00:26.460 align:start position:0% world and how it can how it addresses 00:00:26.460 --> 00:00:29.419 align:start position:0% world and how it can how it addresses the<00:00:27.150> world<00:00:27.630> of<00:00:27.840> more<00:00:28.170> of<00:00:28.230> open-source<00:00:28.859> so<00:00:29.250> it's 00:00:29.419 --> 00:00:29.429 align:start position:0% the world of more of open-source so it's 00:00:29.429 --> 00:00:31.609 align:start position:0% the world of more of open-source so it's been<00:00:29.640> a<00:00:29.670> learning<00:00:29.939> experience<00:00:30.269> to<00:00:30.840> to<00:00:31.470> figure 00:00:31.609 --> 00:00:31.619 align:start position:0% been a learning experience to to figure 00:00:31.619 --> 00:00:34.010 align:start position:0% been a learning experience to to figure out<00:00:31.830> how<00:00:31.949> we<00:00:32.009> how<00:00:32.730> are<00:00:32.759> you<00:00:32.940> married<00:00:33.660> the<00:00:33.780> best 00:00:34.010 --> 00:00:34.020 align:start position:0% out how we how are you married the best 00:00:34.020 --> 00:00:35.990 align:start position:0% out how we how are you married the best of<00:00:34.230> both<00:00:34.380> worlds<00:00:34.410> and<00:00:35.100> I<00:00:35.160> think<00:00:35.430> that's<00:00:35.610> one<00:00:35.969> of 00:00:35.990 --> 00:00:36.000 align:start position:0% of both worlds and I think that's one of 00:00:36.000 --> 00:00:37.819 align:start position:0% of both worlds and I think that's one of the<00:00:36.120> reasons<00:00:36.360> why<00:00:36.480> I<00:00:36.510> think<00:00:36.960> I<00:00:37.320> was<00:00:37.680> even 00:00:37.819 --> 00:00:37.829 align:start position:0% the reasons why I think I was even 00:00:37.829 --> 00:00:40.760 align:start position:0% the reasons why I think I was even invited<00:00:38.250> to<00:00:38.579> take<00:00:38.969> the<00:00:39.149> the<00:00:39.540> role<00:00:39.780> of<00:00:40.050> heading 00:00:40.760 --> 00:00:40.770 align:start position:0% invited to take the the role of heading 00:00:40.770 --> 00:00:45.020 align:start position:0% invited to take the the role of heading up<00:00:40.920> the<00:00:41.520> EA<00:00:41.730> is<00:00:42.239> that<00:00:42.980> we<00:00:43.980> we<00:00:44.340> we<00:00:44.610> need<00:00:44.789> to<00:00:44.910> do 00:00:45.020 --> 00:00:45.030 align:start position:0% up the EA is that we we we need to do 00:00:45.030 --> 00:00:46.639 align:start position:0% up the EA is that we we we need to do that<00:00:45.180> we<00:00:45.360> shouldn't<00:00:45.719> try<00:00:45.899> to<00:00:45.930> reinvent<00:00:46.469> the 00:00:46.639 --> 00:00:46.649 align:start position:0% that we shouldn't try to reinvent the 00:00:46.649 --> 00:00:48.799 align:start position:0% that we shouldn't try to reinvent the wheel<00:00:46.829> and<00:00:47.129> so<00:00:47.969> there's<00:00:48.239> lots<00:00:48.450> of<00:00:48.660> benefits 00:00:48.799 --> 00:00:48.809 align:start position:0% wheel and so there's lots of benefits 00:00:48.809 --> 00:00:52.700 align:start position:0% wheel and so there's lots of benefits from<00:00:49.320> both<00:00:50.000> aspects<00:00:51.000> of<00:00:51.120> looking<00:00:51.480> at<00:00:51.660> what's<00:00:52.559> a 00:00:52.700 --> 00:00:52.710 align:start position:0% from both aspects of looking at what's a 00:00:52.710 --> 00:00:55.580 align:start position:0% from both aspects of looking at what's a pure<00:00:52.980> a<00:00:53.010> purist<00:00:53.520> version<00:00:53.969> of<00:00:54.210> open-source<00:00:54.899> and 00:00:55.580 --> 00:00:55.590 align:start position:0% pure a purist version of open-source and 00:00:55.590 --> 00:00:57.470 align:start position:0% pure a purist version of open-source and how<00:00:55.739> does<00:00:55.800> that<00:00:56.070> work<00:00:56.250> and<00:00:56.460> how<00:00:56.969> do<00:00:57.030> you<00:00:57.180> also 00:00:57.470 --> 00:00:57.480 align:start position:0% how does that work and how do you also 00:00:57.480 --> 00:01:01.279 align:start position:0% how does that work and how do you also protect<00:00:57.930> the<00:00:58.350> the<00:00:58.949> enterprise's<00:00:59.699> of<00:00:59.730> which<00:01:00.289> we 00:01:01.279 --> 00:01:01.289 align:start position:0% protect the the enterprise's of which we 00:01:01.289 --> 00:01:05.210 align:start position:0% protect the the enterprise's of which we we<00:01:01.710> address<00:01:02.460> and<00:01:02.789> that's<00:01:03.600> how<00:01:03.809> we<00:01:03.870> we<00:01:04.589> started 00:01:05.210 --> 00:01:05.220 align:start position:0% we address and that's how we we started 00:01:05.220 --> 00:01:09.230 align:start position:0% we address and that's how we we started I<00:01:05.610> joined<00:01:06.420> last<00:01:06.900> January<00:01:07.830> but<00:01:08.159> as<00:01:08.310> many<00:01:09.090> of<00:01:09.180> you 00:01:09.230 --> 00:01:09.240 align:start position:0% I joined last January but as many of you 00:01:09.240 --> 00:01:13.700 align:start position:0% I joined last January but as many of you know<00:01:09.360> the<00:01:09.600> EA<00:01:10.670> the<00:01:11.670> initial<00:01:12.030> date<00:01:12.240> has<00:01:12.390> gone<00:01:12.710> jo 00:01:13.700 --> 00:01:13.710 align:start position:0% know the EA the initial date has gone jo 00:01:13.710 --> 00:01:16.940 align:start position:0% know the EA the initial date has gone jo zuban<00:01:13.920> told<00:01:14.250> me<00:01:14.340> was<00:01:14.430> February<00:01:15.210> 29th<00:01:15.950> the 00:01:16.940 --> 00:01:16.950 align:start position:0% zuban told me was February 29th the 00:01:16.950 --> 00:01:22.760 align:start position:0% zuban told me was February 29th the prior<00:01:17.430> year<00:01:17.850> and<00:01:17.970> so<00:01:19.250> so<00:01:20.250> in<00:01:20.369> any<00:01:20.490> event<00:01:21.500> it's<00:01:22.500> a 00:01:22.760 --> 00:01:22.770 align:start position:0% prior year and so so in any event it's a 00:01:22.770 --> 00:01:24.920 align:start position:0% prior year and so so in any event it's a very<00:01:23.159> new<00:01:23.310> organization<00:01:24.030> but<00:01:24.180> the<00:01:24.330> intent<00:01:24.689> was 00:01:24.920 --> 00:01:24.930 align:start position:0% very new organization but the intent was 00:01:24.930 --> 00:01:27.890 align:start position:0% very new organization but the intent was okay<00:01:25.619> we<00:01:25.920> have<00:01:26.070> the<00:01:26.220> the<00:01:26.549> open<00:01:26.880> May<00:01:27.390> net<00:01:27.659> and 00:01:27.890 --> 00:01:27.900 align:start position:0% okay we have the the open May net and 00:01:27.900 --> 00:01:29.960 align:start position:0% okay we have the the open May net and there<00:01:28.110> there's<00:01:28.470> a<00:01:28.530> vision<00:01:29.130> a<00:01:29.280> purpose<00:01:29.670> for<00:01:29.909> it 00:01:29.960 --> 00:01:29.970 align:start position:0% there there's a vision a purpose for it 00:01:29.970 --> 00:01:33.440 align:start position:0% there there's a vision a purpose for it but<00:01:30.659> again<00:01:31.250> what<00:01:32.250> about<00:01:32.460> the<00:01:32.640> enterprise<00:01:32.909> and 00:01:33.440 --> 00:01:33.450 align:start position:0% but again what about the enterprise and 00:01:33.450 --> 00:01:35.480 align:start position:0% but again what about the enterprise and and<00:01:33.720> we<00:01:33.930> are<00:01:34.079> leaving<00:01:34.290> out<00:01:34.619> the<00:01:34.650> opportunity 00:01:35.480 --> 00:01:35.490 align:start position:0% and we are leaving out the opportunity 00:01:35.490 --> 00:01:37.039 align:start position:0% and we are leaving out the opportunity for<00:01:35.640> enterprises<00:01:36.090> to<00:01:36.329> do<00:01:36.600> good<00:01:36.810> in<00:01:36.930> the<00:01:36.960> world 00:01:37.039 --> 00:01:37.049 align:start position:0% for enterprises to do good in the world 00:01:37.049 --> 00:01:38.749 align:start position:0% for enterprises to do good in the world as<00:01:37.439> well<00:01:37.710> as<00:01:37.829> be<00:01:38.009> profitable 00:01:38.749 --> 00:01:38.759 align:start position:0% as well as be profitable 00:01:38.759 --> 00:01:41.210 align:start position:0% as well as be profitable so<00:01:39.270> that's<00:01:39.630> partially<00:01:39.930> if<00:01:40.409> the<00:01:40.590> role<00:01:40.770> of<00:01:40.799> what 00:01:41.210 --> 00:01:41.220 align:start position:0% so that's partially if the role of what 00:01:41.220 --> 00:01:42.740 align:start position:0% so that's partially if the role of what I<00:01:41.460> believe<00:01:41.759> that<00:01:41.790> we<00:01:41.939> should<00:01:41.970> do<00:01:42.329> and<00:01:42.540> how<00:01:42.689> we 00:01:42.740 --> 00:01:42.750 align:start position:0% I believe that we should do and how we 00:01:42.750 --> 00:01:48.590 align:start position:0% I believe that we should do and how we work<00:01:43.079> so<00:01:43.799> so<00:01:44.759> we<00:01:45.180> formed<00:01:45.630> and<00:01:46.409> what<00:01:47.390> we<00:01:48.390> ended 00:01:48.590 --> 00:01:48.600 align:start position:0% work so so we formed and what we ended 00:01:48.600 --> 00:01:50.480 align:start position:0% work so so we formed and what we ended up<00:01:48.720> doing<00:01:48.899> we<00:01:49.140> took<00:01:49.290> a<00:01:49.350> look<00:01:49.530> at<00:01:49.680> initially<00:01:50.070> the 00:01:50.480 --> 00:01:50.490 align:start position:0% up doing we took a look at initially the 00:01:50.490 --> 00:01:52.760 align:start position:0% up doing we took a look at initially the EA<00:01:50.729> was<00:01:50.970> even<00:01:51.270> thinking<00:01:51.570> of<00:01:51.659> writing<00:01:51.899> code<00:01:52.259> but 00:01:52.760 --> 00:01:52.770 align:start position:0% EA was even thinking of writing code but 00:01:52.770 --> 00:01:55.639 align:start position:0% EA was even thinking of writing code but when<00:01:53.310> you<00:01:53.460> look<00:01:53.610> at<00:01:53.930> the<00:01:54.930> organizations<00:01:55.590> that 00:01:55.639 --> 00:01:55.649 align:start position:0% when you look at the organizations that 00:01:55.649 --> 00:01:59.600 align:start position:0% when you look at the organizations that I<00:01:56.240> am<00:01:57.240> very<00:01:57.600> familiar<00:01:57.810> with<00:01:58.079> our<00:01:58.380> or<00:01:59.040> standards 00:01:59.600 --> 00:01:59.610 align:start position:0% I am very familiar with our or standards 00:01:59.610 --> 00:02:01.120 align:start position:0% I am very familiar with our or standards orgs<00:01:59.850> that<00:02:00.030> I'm<00:02:00.149> familiar<00:02:00.329> with<00:02:00.600> and<00:02:00.930> have 00:02:01.120 --> 00:02:01.130 align:start position:0% orgs that I'm familiar with and have 00:02:01.130 --> 00:02:04.399 align:start position:0% orgs that I'm familiar with and have been<00:02:02.130> actively<00:02:02.729> engaged<00:02:03.180> in<00:02:03.420> the<00:02:03.600> last<00:02:03.780> 15<00:02:04.200> 20 00:02:04.399 --> 00:02:04.409 align:start position:0% been actively engaged in the last 15 20 00:02:04.409 --> 00:02:06.740 align:start position:0% been actively engaged in the last 15 20 years<00:02:04.770> such<00:02:05.040> as<00:02:05.189> the<00:02:05.310> I<00:02:05.340> Triple<00:02:05.850> E<00:02:05.969> and<00:02:06.479> I<00:02:06.689> don't 00:02:06.740 --> 00:02:06.750 align:start position:0% years such as the I Triple E and I don't 00:02:06.750 --> 00:02:08.150 align:start position:0% years such as the I Triple E and I don't know<00:02:06.930> if<00:02:06.990> you're<00:02:07.110> familiar<00:02:07.229> with<00:02:07.469> some<00:02:08.039> of 00:02:08.150 --> 00:02:08.160 align:start position:0% know if you're familiar with some of 00:02:08.160 --> 00:02:11.809 align:start position:0% know if you're familiar with some of these<00:02:08.220> at<00:02:08.580> sea<00:02:08.940> and<00:02:09.750> then<00:02:10.080> 3gpp<00:02:11.009> and<00:02:11.310> the<00:02:11.370> 3gpp 00:02:11.809 --> 00:02:11.819 align:start position:0% these at sea and then 3gpp and the 3gpp 00:02:11.819 --> 00:02:13.290 align:start position:0% these at sea and then 3gpp and the 3gpp is<00:02:12.330> a<00:02:12.599> partner 00:02:13.290 --> 00:02:13.300 align:start position:0% is a partner 00:02:13.300 --> 00:02:15.780 align:start position:0% is a partner project<00:02:13.840> it's<00:02:14.530> a<00:02:14.740> it's<00:02:14.950> a<00:02:15.130> group<00:02:15.430> it's<00:02:15.610> not 00:02:15.780 --> 00:02:15.790 align:start position:0% project it's a it's a group it's not 00:02:15.790 --> 00:02:19.260 align:start position:0% project it's a it's a group it's not even<00:02:16.030> formal<00:02:16.480> they<00:02:16.990> write<00:02:17.290> a<00:02:17.320> spec<00:02:17.970> there's<00:02:18.970> no 00:02:19.260 --> 00:02:19.270 align:start position:0% even formal they write a spec there's no 00:02:19.270 --> 00:02:22.920 align:start position:0% even formal they write a spec there's no code<00:02:19.630> and<00:02:19.960> then<00:02:20.560> it<00:02:20.590> goes<00:02:20.890> to<00:02:20.920> ed<00:02:21.250> C<00:02:21.550> which<00:02:22.150> is 00:02:22.920 --> 00:02:22.930 align:start position:0% code and then it goes to ed C which is 00:02:22.930 --> 00:02:26.820 align:start position:0% code and then it goes to ed C which is the<00:02:23.140> European<00:02:24.660> the<00:02:25.660> version<00:02:26.170> of<00:02:26.260> a<00:02:26.350> standards 00:02:26.820 --> 00:02:26.830 align:start position:0% the European the version of a standards 00:02:26.830 --> 00:02:29.070 align:start position:0% the European the version of a standards or<00:02:26.980> got<00:02:27.190> it<00:02:27.310> covers<00:02:27.610> international<00:02:28.330> and<00:02:28.510> then 00:02:29.070 --> 00:02:29.080 align:start position:0% or got it covers international and then 00:02:29.080 --> 00:02:31.260 align:start position:0% or got it covers international and then it<00:02:29.620> gets<00:02:29.710> rubber<00:02:30.010> stamped<00:02:30.460> and<00:02:30.640> then<00:02:31.120> it 00:02:31.260 --> 00:02:31.270 align:start position:0% it gets rubber stamped and then it 00:02:31.270 --> 00:02:35.070 align:start position:0% it gets rubber stamped and then it becomes<00:02:31.660> a<00:02:31.780> global<00:02:31.960> spec<00:02:32.610> and<00:02:33.610> the<00:02:34.240> the<00:02:34.810> the 00:02:35.070 --> 00:02:35.080 align:start position:0% becomes a global spec and the the the 00:02:35.080 --> 00:02:36.600 align:start position:0% becomes a global spec and the the the end<00:02:35.230> result<00:02:35.650> and<00:02:35.920> this<00:02:35.980> is<00:02:36.130> the<00:02:36.370> the 00:02:36.600 --> 00:02:36.610 align:start position:0% end result and this is the the 00:02:36.610 --> 00:02:38.460 align:start position:0% end result and this is the the philosophy<00:02:37.150> that<00:02:37.330> I'd<00:02:37.480> really<00:02:37.810> like<00:02:38.050> to<00:02:38.230> see 00:02:38.460 --> 00:02:38.470 align:start position:0% philosophy that I'd really like to see 00:02:38.470 --> 00:02:41.550 align:start position:0% philosophy that I'd really like to see is<00:02:38.770> that<00:02:39.460> when<00:02:39.850> you<00:02:39.970> buy<00:02:40.150> a<00:02:40.290> if<00:02:41.290> you<00:02:41.410> buy 00:02:41.550 --> 00:02:41.560 align:start position:0% is that when you buy a if you buy 00:02:41.560 --> 00:02:44.790 align:start position:0% is that when you buy a if you buy cellphone<00:02:42.190> here<00:02:42.880> in<00:02:42.970> Prague<00:02:43.240> and<00:02:43.690> it's<00:02:44.530> made 00:02:44.790 --> 00:02:44.800 align:start position:0% cellphone here in Prague and it's made 00:02:44.800 --> 00:02:50.400 align:start position:0% cellphone here in Prague and it's made made<00:02:45.730> in<00:02:46.090> in<00:02:46.990> Korea<00:02:47.890> and<00:02:48.630> and<00:02:49.630> then<00:02:49.840> you<00:02:50.110> you 00:02:50.400 --> 00:02:50.410 align:start position:0% made in in Korea and and then you you 00:02:50.410 --> 00:02:52.800 align:start position:0% made in in Korea and and then you you show<00:02:50.620> up<00:02:50.740> in<00:02:50.890> Venezuela<00:02:51.490> and<00:02:51.640> you<00:02:51.790> buy<00:02:51.940> a<00:02:51.970> SIM 00:02:52.800 --> 00:02:52.810 align:start position:0% show up in Venezuela and you buy a SIM 00:02:52.810 --> 00:02:56.070 align:start position:0% show up in Venezuela and you buy a SIM card<00:02:53.170> you<00:02:53.910> expect<00:02:54.910> that<00:02:55.090> phone<00:02:55.360> to<00:02:55.570> work<00:02:55.750> and 00:02:56.070 --> 00:02:56.080 align:start position:0% card you expect that phone to work and 00:02:56.080 --> 00:02:57.780 align:start position:0% card you expect that phone to work and that<00:02:56.440> deals<00:02:56.740> it<00:02:56.950> that<00:02:57.130> that's<00:02:57.310> all<00:02:57.550> about 00:02:57.780 --> 00:02:57.790 align:start position:0% that deals it that that's all about 00:02:57.790 --> 00:03:00.390 align:start position:0% that deals it that that's all about interoperability<00:02:58.170> and<00:02:59.170> global<00:03:00.010> in<00:03:00.130> are<00:03:00.250> by 00:03:00.390 --> 00:03:00.400 align:start position:0% interoperability and global in are by 00:03:00.400 --> 00:03:02.310 align:start position:0% interoperability and global in are by interoperability<00:03:01.240> and<00:03:01.600> that's<00:03:01.750> the<00:03:02.170> vision 00:03:02.310 --> 00:03:02.320 align:start position:0% interoperability and that's the vision 00:03:02.320 --> 00:03:05.790 align:start position:0% interoperability and that's the vision that<00:03:02.590> I'd<00:03:02.710> like<00:03:02.950> to<00:03:02.980> see<00:03:03.310> our<00:03:03.880> world<00:03:04.300> be<00:03:04.800> and 00:03:05.790 --> 00:03:05.800 align:start position:0% that I'd like to see our world be and 00:03:05.800 --> 00:03:08.340 align:start position:0% that I'd like to see our world be and and<00:03:06.220> and<00:03:06.490> the<00:03:06.670> way<00:03:06.850> to<00:03:06.910> do<00:03:07.240> it<00:03:07.450> is<00:03:07.720> to<00:03:07.990> have<00:03:08.320> a 00:03:08.340 --> 00:03:08.350 align:start position:0% and and the way to do it is to have a 00:03:08.350 --> 00:03:11.340 align:start position:0% and and the way to do it is to have a standards<00:03:08.920> org<00:03:09.070> and<00:03:09.400> so<00:03:10.330> a<00:03:10.660> standards<00:03:11.200> or 00:03:11.340 --> 00:03:11.350 align:start position:0% standards org and so a standards or 00:03:11.350 --> 00:03:12.840 align:start position:0% standards org and so a standards or doesn't<00:03:11.710> write<00:03:11.830> code<00:03:12.100> we<00:03:12.460> should<00:03:12.700> never 00:03:12.840 --> 00:03:12.850 align:start position:0% doesn't write code we should never 00:03:12.850 --> 00:03:16.320 align:start position:0% doesn't write code we should never compete<00:03:13.330> with<00:03:13.480> our<00:03:13.630> members<00:03:14.370> who<00:03:15.370> do<00:03:15.700> work<00:03:15.970> and 00:03:16.320 --> 00:03:16.330 align:start position:0% compete with our members who do work and 00:03:16.330 --> 00:03:19.380 align:start position:0% compete with our members who do work and then<00:03:17.110> and<00:03:18.100> then<00:03:18.310> in<00:03:18.459> order<00:03:18.610> to<00:03:18.850> enforce<00:03:19.180> the 00:03:19.380 --> 00:03:19.390 align:start position:0% then and then in order to enforce the 00:03:19.390 --> 00:03:21.890 align:start position:0% then and then in order to enforce the standards<00:03:19.630> code<00:03:20.170> you<00:03:21.040> need<00:03:21.220> some<00:03:21.459> form<00:03:21.700> of 00:03:21.890 --> 00:03:21.900 align:start position:0% standards code you need some form of 00:03:21.900 --> 00:03:23.760 align:start position:0% standards code you need some form of certification<00:03:22.900> and<00:03:23.020> that's<00:03:23.260> the<00:03:23.410> reason<00:03:23.650> why 00:03:23.760 --> 00:03:23.770 align:start position:0% certification and that's the reason why 00:03:23.770 --> 00:03:25.860 align:start position:0% certification and that's the reason why all<00:03:23.950> these<00:03:24.160> phones<00:03:24.430> work<00:03:24.730> and<00:03:25.000> where<00:03:25.540> I<00:03:25.570> come 00:03:25.860 --> 00:03:25.870 align:start position:0% all these phones work and where I come 00:03:25.870 --> 00:03:27.720 align:start position:0% all these phones work and where I come from<00:03:25.900> it's<00:03:26.260> called<00:03:26.320> NW<00:03:26.770> IOT<00:03:27.370> network 00:03:27.720 --> 00:03:27.730 align:start position:0% from it's called NW IOT network 00:03:27.730 --> 00:03:29.880 align:start position:0% from it's called NW IOT network interoperability<00:03:28.450> testing<00:03:28.870> every<00:03:29.709> one<00:03:29.860> of 00:03:29.880 --> 00:03:29.890 align:start position:0% interoperability testing every one of 00:03:29.890 --> 00:03:31.530 align:start position:0% interoperability testing every one of those<00:03:30.040> operators<00:03:30.459> by<00:03:30.670> that<00:03:30.910> phone<00:03:31.150> they<00:03:31.300> plug 00:03:31.530 --> 00:03:31.540 align:start position:0% those operators by that phone they plug 00:03:31.540 --> 00:03:33.479 align:start position:0% those operators by that phone they plug it<00:03:31.690> into<00:03:31.870> their<00:03:32.140> own<00:03:32.260> network<00:03:32.650> or<00:03:33.190> they<00:03:33.280> don't 00:03:33.479 --> 00:03:33.489 align:start position:0% it into their own network or they don't 00:03:33.489 --> 00:03:36.030 align:start position:0% it into their own network or they don't sign<00:03:33.730> off<00:03:33.970> on<00:03:34.000> it<00:03:34.270> so<00:03:34.989> we<00:03:35.170> can't<00:03:35.440> do<00:03:35.650> all<00:03:35.680> those 00:03:36.030 --> 00:03:36.040 align:start position:0% sign off on it so we can't do all those 00:03:36.040 --> 00:03:37.530 align:start position:0% sign off on it so we can't do all those things<00:03:36.280> because<00:03:36.550> that's<00:03:36.670> hardware<00:03:37.180> but 00:03:37.530 --> 00:03:37.540 align:start position:0% things because that's hardware but 00:03:37.540 --> 00:03:38.699 align:start position:0% things because that's hardware but there's<00:03:37.690> things<00:03:37.959> that<00:03:38.080> we<00:03:38.170> could<00:03:38.380> do<00:03:38.530> for 00:03:38.699 --> 00:03:38.709 align:start position:0% there's things that we could do for 00:03:38.709 --> 00:03:41.820 align:start position:0% there's things that we could do for software<00:03:39.130> and<00:03:39.489> there's<00:03:40.150> lots<00:03:40.660> of<00:03:40.840> ways<00:03:41.020> you 00:03:41.820 --> 00:03:41.830 align:start position:0% software and there's lots of ways you 00:03:41.830 --> 00:03:44.310 align:start position:0% software and there's lots of ways you guys<00:03:41.950> Justin<00:03:42.700> Lee<00:03:42.790> he<00:03:42.910> was<00:03:43.060> came<00:03:44.050> out<00:03:44.200> an 00:03:44.310 --> 00:03:44.320 align:start position:0% guys Justin Lee he was came out an 00:03:44.320 --> 00:03:45.780 align:start position:0% guys Justin Lee he was came out an entertainment<00:03:44.890> gaming<00:03:45.220> industry<00:03:45.670> as<00:03:45.760> a 00:03:45.780 --> 00:03:45.790 align:start position:0% entertainment gaming industry as a 00:03:45.790 --> 00:03:47.760 align:start position:0% entertainment gaming industry as a product<00:03:46.180> marketing<00:03:46.600> manager<00:03:46.630> there's<00:03:47.440> a<00:03:47.500> lot 00:03:47.760 --> 00:03:47.770 align:start position:0% product marketing manager there's a lot 00:03:47.770 --> 00:03:50.160 align:start position:0% product marketing manager there's a lot that<00:03:47.950> you<00:03:48.010> can<00:03:48.310> do<00:03:48.550> to<00:03:49.390> assure 00:03:50.160 --> 00:03:50.170 align:start position:0% that you can do to assure 00:03:50.170 --> 00:03:52.380 align:start position:0% that you can do to assure interoperability<00:03:50.860> so<00:03:51.250> that's<00:03:51.430> where<00:03:51.700> that's 00:03:52.380 --> 00:03:52.390 align:start position:0% interoperability so that's where that's 00:03:52.390 --> 00:03:54.780 align:start position:0% interoperability so that's where that's where<00:03:52.630> I'm<00:03:53.380> coming<00:03:53.830> from<00:03:53.860> that's<00:03:54.280> where<00:03:54.520> I've 00:03:54.780 --> 00:03:54.790 align:start position:0% where I'm coming from that's where I've 00:03:54.790 --> 00:03:57.330 align:start position:0% where I'm coming from that's where I've got<00:03:54.970> support<00:03:55.270> from<00:03:55.450> our<00:03:55.570> board<00:03:55.950> and<00:03:56.950> the<00:03:57.100> folks 00:03:57.330 --> 00:03:57.340 align:start position:0% got support from our board and the folks 00:03:57.340 --> 00:04:00.390 align:start position:0% got support from our board and the folks in<00:03:57.640> our<00:03:57.820> world<00:03:58.090> how<00:03:58.660> do<00:03:58.720> we<00:03:58.900> do<00:03:59.080> do<00:03:59.440> that<00:03:59.620> using 00:04:00.390 --> 00:04:00.400 align:start position:0% in our world how do we do do that using 00:04:00.400 --> 00:04:03.420 align:start position:0% in our world how do we do do that using the<00:04:00.670> EA<00:04:01.410> so<00:04:02.410> I've<00:04:02.530> walked<00:04:02.800> you<00:04:02.980> through<00:04:03.010> I'm 00:04:03.420 --> 00:04:03.430 align:start position:0% the EA so I've walked you through I'm 00:04:03.430 --> 00:04:04.470 align:start position:0% the EA so I've walked you through I'm not<00:04:03.580> going<00:04:03.730> to<00:04:03.790> go<00:04:03.880> through<00:04:04.060> all<00:04:04.120> the<00:04:04.239> slides 00:04:04.470 --> 00:04:04.480 align:start position:0% not going to go through all the slides 00:04:04.480 --> 00:04:06.210 align:start position:0% not going to go through all the slides but<00:04:04.690> you'll<00:04:04.840> be<00:04:04.870> able<00:04:05.140> to<00:04:05.260> get<00:04:05.709> them<00:04:05.890> so<00:04:06.190> I 00:04:06.210 --> 00:04:06.220 align:start position:0% but you'll be able to get them so I 00:04:06.220 --> 00:04:08.940 align:start position:0% but you'll be able to get them so I already<00:04:06.820> share<00:04:07.180> with<00:04:07.330> you<00:04:07.540> why<00:04:08.200> standards<00:04:08.800> are 00:04:08.940 --> 00:04:08.950 align:start position:0% already share with you why standards are 00:04:08.950 --> 00:04:10.740 align:start position:0% already share with you why standards are really<00:04:09.250> important<00:04:09.760> because<00:04:09.850> without<00:04:10.239> that<00:04:10.600> we 00:04:10.740 --> 00:04:10.750 align:start position:0% really important because without that we 00:04:10.750 --> 00:04:15.270 align:start position:0% really important because without that we can't<00:04:11.110> accomplish<00:04:11.739> that<00:04:12.070> goal<00:04:13.380> in<00:04:14.380> our<00:04:14.560> org<00:04:14.860> we 00:04:15.270 --> 00:04:15.280 align:start position:0% can't accomplish that goal in our org we 00:04:15.280 --> 00:04:17.070 align:start position:0% can't accomplish that goal in our org we have<00:04:15.430> a<00:04:15.459> very<00:04:15.700> good<00:04:15.880> Board<00:04:16.180> of<00:04:16.330> Directors<00:04:16.810> and 00:04:17.070 --> 00:04:17.080 align:start position:0% have a very good Board of Directors and 00:04:17.080 --> 00:04:18.780 align:start position:0% have a very good Board of Directors and initially<00:04:17.919> I<00:04:17.980> was<00:04:18.100> telling<00:04:18.400> some<00:04:18.519> of<00:04:18.580> the<00:04:18.640> guys 00:04:18.780 --> 00:04:18.790 align:start position:0% initially I was telling some of the guys 00:04:18.790 --> 00:04:20.220 align:start position:0% initially I was telling some of the guys I<00:04:18.970> don't<00:04:19.060> want<00:04:19.239> you<00:04:19.359> to<00:04:19.419> think<00:04:19.600> great<00:04:19.660> I<00:04:20.019> know 00:04:20.220 --> 00:04:20.230 align:start position:0% I don't want you to think great I know 00:04:20.230 --> 00:04:21.810 align:start position:0% I don't want you to think great I know it<00:04:20.500> is<00:04:20.590> all<00:04:20.739> the<00:04:20.919> biggest<00:04:21.220> companies<00:04:21.640> in<00:04:21.669> the 00:04:21.810 --> 00:04:21.820 align:start position:0% it is all the biggest companies in the 00:04:21.820 --> 00:04:23.790 align:start position:0% it is all the biggest companies in the world<00:04:21.880> where<00:04:22.720> are<00:04:22.870> they<00:04:22.990> and<00:04:23.229> compared<00:04:23.560> to<00:04:23.620> the 00:04:23.790 --> 00:04:23.800 align:start position:0% world where are they and compared to the 00:04:23.800 --> 00:04:26.750 align:start position:0% world where are they and compared to the smallest<00:04:24.100> ones<00:04:24.550> so<00:04:25.180> but 00:04:26.750 --> 00:04:26.760 align:start position:0% smallest ones so but 00:04:26.760 --> 00:04:29.900 align:start position:0% smallest ones so but and<00:04:27.240> as<00:04:27.480> you<00:04:27.660> know<00:04:27.810> in<00:04:28.620> the<00:04:29.460> world<00:04:29.640> of 00:04:29.900 --> 00:04:29.910 align:start position:0% and as you know in the world of 00:04:29.910 --> 00:04:32.030 align:start position:0% and as you know in the world of blockchain<00:04:30.780> and<00:04:31.080> the<00:04:31.170> enterprise 00:04:32.030 --> 00:04:32.040 align:start position:0% blockchain and the enterprise 00:04:32.040 --> 00:04:34.160 align:start position:0% blockchain and the enterprise I<00:04:32.070> want<00:04:32.670> the<00:04:32.790> lowest<00:04:33.060> hanging<00:04:33.240> fruit<00:04:33.480> our 00:04:34.160 --> 00:04:34.170 align:start position:0% I want the lowest hanging fruit our 00:04:34.170 --> 00:04:36.170 align:start position:0% I want the lowest hanging fruit our financial<00:04:34.770> services<00:04:34.950> of<00:04:35.610> course<00:04:35.910> and<00:04:36.060> there's 00:04:36.170 --> 00:04:36.180 align:start position:0% financial services of course and there's 00:04:36.180 --> 00:04:37.340 align:start position:0% financial services of course and there's amber<00:04:36.570> hi<00:04:36.870> amber 00:04:37.340 --> 00:04:37.350 align:start position:0% amber hi amber 00:04:37.350 --> 00:04:39.830 align:start position:0% amber hi amber so<00:04:37.740> she<00:04:37.800> helps<00:04:38.490> start<00:04:38.760> the<00:04:39.000> quorum<00:04:39.390> side<00:04:39.660> of 00:04:39.830 --> 00:04:39.840 align:start position:0% so she helps start the quorum side of 00:04:39.840 --> 00:04:43.730 align:start position:0% so she helps start the quorum side of things<00:04:40.080> so<00:04:40.680> at<00:04:41.520> Quora<00:04:41.850> so<00:04:42.210> in<00:04:42.360> any<00:04:42.510> event<00:04:42.740> that 00:04:43.730 --> 00:04:43.740 align:start position:0% things so at Quora so in any event that 00:04:43.740 --> 00:04:46.520 align:start position:0% things so at Quora so in any event that was<00:04:44.370> low-hanging<00:04:44.850> fruit<00:04:45.300> but<00:04:45.930> it<00:04:46.050> but<00:04:46.320> if<00:04:46.470> you 00:04:46.520 --> 00:04:46.530 align:start position:0% was low-hanging fruit but it but if you 00:04:46.530 --> 00:04:48.230 align:start position:0% was low-hanging fruit but it but if you take<00:04:46.740> a<00:04:46.770> look<00:04:46.920> at<00:04:47.100> some<00:04:47.340> of<00:04:47.430> the<00:04:47.520> folks<00:04:47.730> on<00:04:47.970> our 00:04:48.230 --> 00:04:48.240 align:start position:0% take a look at some of the folks on our 00:04:48.240 --> 00:04:50.090 align:start position:0% take a look at some of the folks on our board<00:04:48.660> Andrew<00:04:49.020> Miller<00:04:49.200> from<00:04:49.530> the<00:04:49.620> University 00:04:50.090 --> 00:04:50.100 align:start position:0% board Andrew Miller from the University 00:04:50.100 --> 00:04:52.580 align:start position:0% board Andrew Miller from the University of<00:04:50.130> Illinois<00:04:50.250> and<00:04:51.090> then<00:04:51.330> so<00:04:51.540> we<00:04:51.720> try<00:04:51.930> to<00:04:51.990> have<00:04:52.560> a 00:04:52.580 --> 00:04:52.590 align:start position:0% of Illinois and then so we try to have a 00:04:52.590 --> 00:04:54.350 align:start position:0% of Illinois and then so we try to have a balanced<00:04:53.100> approach<00:04:53.400> and<00:04:53.610> everybody<00:04:53.970> gets<00:04:54.180> one 00:04:54.350 --> 00:04:54.360 align:start position:0% balanced approach and everybody gets one 00:04:54.360 --> 00:04:57.190 align:start position:0% balanced approach and everybody gets one vote<00:04:54.390> no<00:04:55.260> matter<00:04:55.440> how<00:04:55.650> big<00:04:55.890> or<00:04:56.010> small<00:04:56.070> you<00:04:56.490> are 00:04:57.190 --> 00:04:57.200 align:start position:0% vote no matter how big or small you are 00:04:57.200 --> 00:05:00.410 align:start position:0% vote no matter how big or small you are and<00:04:58.200> the<00:04:58.650> organization<00:04:59.370> since<00:04:59.850> I<00:05:00.090> started 00:05:00.410 --> 00:05:00.420 align:start position:0% and the organization since I started 00:05:00.420 --> 00:05:03.620 align:start position:0% and the organization since I started we've<00:05:00.750> doubled<00:05:01.140> in<00:05:01.290> size<00:05:01.320> and<00:05:02.070> I<00:05:03.030> can<00:05:03.420> share 00:05:03.620 --> 00:05:03.630 align:start position:0% we've doubled in size and I can share 00:05:03.630 --> 00:05:06.380 align:start position:0% we've doubled in size and I can share with<00:05:03.660> you<00:05:03.900> the<00:05:04.050> the<00:05:04.890> argument<00:05:05.370> that<00:05:05.490> we<00:05:05.880> make 00:05:06.380 --> 00:05:06.390 align:start position:0% with you the the argument that we make 00:05:06.390 --> 00:05:07.880 align:start position:0% with you the the argument that we make is<00:05:06.630> okay<00:05:07.050> if<00:05:07.260> you're<00:05:07.470> looking<00:05:07.770> for 00:05:07.880 --> 00:05:07.890 align:start position:0% is okay if you're looking for 00:05:07.890 --> 00:05:09.920 align:start position:0% is okay if you're looking for interoperability<00:05:08.550> if<00:05:08.940> you're<00:05:09.330> looking<00:05:09.660> for 00:05:09.920 --> 00:05:09.930 align:start position:0% interoperability if you're looking for 00:05:09.930 --> 00:05:12.020 align:start position:0% interoperability if you're looking for sure<00:05:10.590> insan'<00:05:11.100> die<00:05:11.250> can<00:05:11.460> tell<00:05:11.640> you<00:05:11.760> it's<00:05:11.880> not 00:05:12.020 --> 00:05:12.030 align:start position:0% sure insan' die can tell you it's not 00:05:12.030 --> 00:05:14.240 align:start position:0% sure insan' die can tell you it's not easy<00:05:12.090> to<00:05:12.540> convince<00:05:12.720> the<00:05:13.080> enterprise's<00:05:13.740> to<00:05:13.920> bet 00:05:14.240 --> 00:05:14.250 align:start position:0% easy to convince the enterprise's to bet 00:05:14.250 --> 00:05:16.370 align:start position:0% easy to convince the enterprise's to bet down<00:05:14.520> let<00:05:15.360> alone<00:05:15.570> understand<00:05:16.170> what 00:05:16.370 --> 00:05:16.380 align:start position:0% down let alone understand what 00:05:16.380 --> 00:05:18.650 align:start position:0% down let alone understand what blockchain<00:05:16.860> is<00:05:16.890> but<00:05:17.790> to<00:05:17.940> bet<00:05:18.150> down<00:05:18.300> and<00:05:18.540> make<00:05:18.630> a 00:05:18.650 --> 00:05:18.660 align:start position:0% blockchain is but to bet down and make a 00:05:18.660 --> 00:05:22.880 align:start position:0% blockchain is but to bet down and make a commitment<00:05:19.410> not<00:05:20.040> easy<00:05:20.370> and<00:05:20.790> so<00:05:21.680> that's<00:05:22.680> our 00:05:22.880 --> 00:05:22.890 align:start position:0% commitment not easy and so that's our 00:05:22.890 --> 00:05:25.520 align:start position:0% commitment not easy and so that's our story<00:05:23.250> we<00:05:23.520> use<00:05:23.730> that<00:05:24.000> we<00:05:24.090> use<00:05:24.120> what<00:05:24.990> the<00:05:25.080> EA<00:05:25.260> is 00:05:25.520 --> 00:05:25.530 align:start position:0% story we use that we use what the EA is 00:05:25.530 --> 00:05:27.410 align:start position:0% story we use that we use what the EA is about<00:05:25.980> and<00:05:26.250> it<00:05:26.340> can<00:05:26.460> help<00:05:26.610> all<00:05:26.820> of<00:05:26.910> you<00:05:27.000> even<00:05:27.150> if 00:05:27.410 --> 00:05:27.420 align:start position:0% about and it can help all of you even if 00:05:27.420 --> 00:05:28.550 align:start position:0% about and it can help all of you even if you're<00:05:27.540> looking<00:05:27.780> at<00:05:27.900> where<00:05:28.050> we're<00:05:28.230> headed 00:05:28.550 --> 00:05:28.560 align:start position:0% you're looking at where we're headed 00:05:28.560 --> 00:05:30.470 align:start position:0% you're looking at where we're headed which<00:05:28.680> I<00:05:28.860> would<00:05:29.100> like<00:05:29.220> to<00:05:29.400> see<00:05:29.640> us<00:05:29.970> and<00:05:30.270> when<00:05:30.420> we 00:05:30.470 --> 00:05:30.480 align:start position:0% which I would like to see us and when we 00:05:30.480 --> 00:05:34.340 align:start position:0% which I would like to see us and when we talk<00:05:30.690> about<00:05:30.810> the<00:05:30.960> roadmap<00:05:32.270> Inc<00:05:33.270> enhance<00:05:34.170> our 00:05:34.340 --> 00:05:34.350 align:start position:0% talk about the roadmap Inc enhance our 00:05:34.350 --> 00:05:36.290 align:start position:0% talk about the roadmap Inc enhance our specification<00:05:35.220> so<00:05:35.370> we<00:05:35.490> can<00:05:35.760> do<00:05:35.910> things<00:05:36.090> to 00:05:36.290 --> 00:05:36.300 align:start position:0% specification so we can do things to 00:05:36.300 --> 00:05:38.360 align:start position:0% specification so we can do things to help<00:05:36.480> accelerate<00:05:36.900> the<00:05:37.290> adoption<00:05:37.740> on<00:05:38.190> the 00:05:38.360 --> 00:05:38.370 align:start position:0% help accelerate the adoption on the 00:05:38.370 --> 00:05:40.070 align:start position:0% help accelerate the adoption on the public<00:05:38.730> maenette<00:05:39.180> because<00:05:39.510> right<00:05:39.720> now<00:05:39.870> we're 00:05:40.070 --> 00:05:40.080 align:start position:0% public maenette because right now we're 00:05:40.080 --> 00:05:42.800 align:start position:0% public maenette because right now we're not<00:05:40.110> doing<00:05:40.290> that<00:05:40.680> but<00:05:40.830> we<00:05:40.890> want<00:05:41.220> to<00:05:41.460> so<00:05:42.390> we<00:05:42.630> have 00:05:42.800 --> 00:05:42.810 align:start position:0% not doing that but we want to so we have 00:05:42.810 --> 00:05:44.470 align:start position:0% not doing that but we want to so we have 500<00:05:43.290> members<00:05:43.470> and<00:05:43.800> we're<00:05:43.890> growing 00:05:44.470 --> 00:05:44.480 align:start position:0% 500 members and we're growing 00:05:44.480 --> 00:05:47.240 align:start position:0% 500 members and we're growing continually<00:05:45.480> growing<00:05:45.960> more<00:05:46.650> and<00:05:46.680> more<00:05:46.980> and 00:05:47.240 --> 00:05:47.250 align:start position:0% continually growing more and more and 00:05:47.250 --> 00:05:50.090 align:start position:0% continually growing more and more and the<00:05:47.640> reason<00:05:47.940> why<00:05:48.060> is<00:05:48.120> they<00:05:48.750> do<00:05:48.810> want<00:05:49.230> the<00:05:49.470> these 00:05:50.090 --> 00:05:50.100 align:start position:0% the reason why is they do want the these 00:05:50.100 --> 00:05:52.100 align:start position:0% the reason why is they do want the these big<00:05:50.310> these<00:05:50.700> enterprises<00:05:51.180> whether<00:05:51.480> small<00:05:51.840> or 00:05:52.100 --> 00:05:52.110 align:start position:0% big these enterprises whether small or 00:05:52.110 --> 00:05:54.350 align:start position:0% big these enterprises whether small or large<00:05:52.710> and<00:05:53.190> particularly<00:05:53.640> if<00:05:53.820> they<00:05:53.970> buy<00:05:54.180> from 00:05:54.350 --> 00:05:54.360 align:start position:0% large and particularly if they buy from 00:05:54.360 --> 00:05:56.480 align:start position:0% large and particularly if they buy from smaller<00:05:54.840> companies<00:05:54.960> and<00:05:55.770> I'm<00:05:55.860> an<00:05:55.980> ex<00:05:56.130> Intel 00:05:56.480 --> 00:05:56.490 align:start position:0% smaller companies and I'm an ex Intel 00:05:56.490 --> 00:05:58.850 align:start position:0% smaller companies and I'm an ex Intel guy<00:05:56.670> but<00:05:56.850> I<00:05:56.880> can<00:05:57.180> tell<00:05:57.360> you<00:05:57.540> if<00:05:58.230> we're 00:05:58.850 --> 00:05:58.860 align:start position:0% guy but I can tell you if we're 00:05:58.860 --> 00:06:01.100 align:start position:0% guy but I can tell you if we're competing<00:05:59.190> if<00:05:59.460> Intel<00:06:00.270> is<00:06:00.390> competing<00:06:00.810> and<00:06:00.990> that 00:06:01.100 --> 00:06:01.110 align:start position:0% competing if Intel is competing and that 00:06:01.110 --> 00:06:02.960 align:start position:0% competing if Intel is competing and that a<00:06:01.140> very<00:06:01.320> small<00:06:01.470> company<00:06:01.860> it's<00:06:02.520> really<00:06:02.580> hard 00:06:02.960 --> 00:06:02.970 align:start position:0% a very small company it's really hard 00:06:02.970 --> 00:06:04.130 align:start position:0% a very small company it's really hard for<00:06:03.060> the<00:06:03.150> small<00:06:03.360> company<00:06:03.720> to<00:06:03.810> get<00:06:03.960> some 00:06:04.130 --> 00:06:04.140 align:start position:0% for the small company to get some 00:06:04.140 --> 00:06:06.530 align:start position:0% for the small company to get some traction<00:06:04.440> so<00:06:05.100> being<00:06:05.370> part<00:06:05.670> of<00:06:05.760> an 00:06:06.530 --> 00:06:06.540 align:start position:0% traction so being part of an 00:06:06.540 --> 00:06:08.420 align:start position:0% traction so being part of an organization<00:06:06.660> like<00:06:07.440> in<00:06:07.590> EA<00:06:07.740> when<00:06:08.100> you<00:06:08.250> say 00:06:08.420 --> 00:06:08.430 align:start position:0% organization like in EA when you say 00:06:08.430 --> 00:06:11.060 align:start position:0% organization like in EA when you say you're<00:06:08.850> you're<00:06:09.330> writing<00:06:09.690> code<00:06:09.720> that<00:06:10.650> can<00:06:10.800> form 00:06:11.060 --> 00:06:11.070 align:start position:0% you're you're writing code that can form 00:06:11.070 --> 00:06:13.070 align:start position:0% you're you're writing code that can form CVA<00:06:11.400> here<00:06:11.790> it's<00:06:11.970> certified<00:06:12.300> they<00:06:12.690> feel<00:06:12.870> better 00:06:13.070 --> 00:06:13.080 align:start position:0% CVA here it's certified they feel better 00:06:13.080 --> 00:06:16.190 align:start position:0% CVA here it's certified they feel better about<00:06:13.290> taking<00:06:13.830> the<00:06:13.920> risk 00:06:16.190 --> 00:06:16.200 align:start position:0% 00:06:16.200 --> 00:06:19.310 align:start position:0% we're<00:06:16.710> diversified<00:06:17.400> we're<00:06:18.210> we<00:06:18.630> have<00:06:18.660> members 00:06:19.310 --> 00:06:19.320 align:start position:0% we're diversified we're we have members 00:06:19.320 --> 00:06:20.750 align:start position:0% we're diversified we're we have members from<00:06:19.350> all<00:06:19.680> over<00:06:19.710> the<00:06:20.040> world<00:06:20.190> with<00:06:20.610> different 00:06:20.750 --> 00:06:20.760 align:start position:0% from all over the world with different 00:06:20.760 --> 00:06:25.100 align:start position:0% from all over the world with different categories<00:06:21.540> of<00:06:21.690> business<00:06:22.340> so<00:06:23.340> we<00:06:24.150> try<00:06:24.390> the 00:06:25.100 --> 00:06:25.110 align:start position:0% categories of business so we try the 00:06:25.110 --> 00:06:26.810 align:start position:0% categories of business so we try the bottom<00:06:25.380> line<00:06:25.560> is<00:06:25.770> folks<00:06:26.010> are<00:06:26.190> joining<00:06:26.370> us<00:06:26.670> in 00:06:26.810 --> 00:06:26.820 align:start position:0% bottom line is folks are joining us in 00:06:26.820 --> 00:06:30.230 align:start position:0% bottom line is folks are joining us in all<00:06:26.940> all<00:06:27.300> the<00:06:27.540> different<00:06:27.930> areas<00:06:29.090> the<00:06:30.090> way 00:06:30.230 --> 00:06:30.240 align:start position:0% all all the different areas the way 00:06:30.240 --> 00:06:32.720 align:start position:0% all all the different areas the way we're<00:06:30.450> organized<00:06:30.930> we<00:06:31.500> have<00:06:31.740> a<00:06:31.770> legal<00:06:32.190> advisory 00:06:32.720 --> 00:06:32.730 align:start position:0% we're organized we have a legal advisory 00:06:32.730 --> 00:06:35.390 align:start position:0% we're organized we have a legal advisory group<00:06:32.910> we're<00:06:33.720> not<00:06:33.930> doing<00:06:34.620> a<00:06:34.710> tremendous 00:06:35.390 --> 00:06:35.400 align:start position:0% group we're not doing a tremendous 00:06:35.400 --> 00:06:37.100 align:start position:0% group we're not doing a tremendous amount<00:06:35.790> of<00:06:35.850> legal<00:06:36.060> work<00:06:36.210> but<00:06:36.600> we<00:06:36.690> do<00:06:36.870> try<00:06:37.080> to 00:06:37.100 --> 00:06:37.110 align:start position:0% amount of legal work but we do try to 00:06:37.110 --> 00:06:37.879 align:start position:0% amount of legal work but we do try to intersect 00:06:37.879 --> 00:06:37.889 align:start position:0% intersect 00:06:37.889 --> 00:06:40.850 align:start position:0% intersect the<00:06:38.460> technical<00:06:38.969> spec<00:06:39.270> work<00:06:39.539> is<00:06:39.810> bit<00:06:40.500> headed<00:06:40.770> by 00:06:40.850 --> 00:06:40.860 align:start position:0% the technical spec work is bit headed by 00:06:40.860 --> 00:06:42.559 align:start position:0% the technical spec work is bit headed by Connor<00:06:41.189> Svendsen<00:06:41.789> he'll<00:06:41.969> come<00:06:42.150> up<00:06:42.180> and<00:06:42.419> talk 00:06:42.559 --> 00:06:42.569 align:start position:0% Connor Svendsen he'll come up and talk 00:06:42.569 --> 00:06:44.600 align:start position:0% Connor Svendsen he'll come up and talk to<00:06:42.599> you<00:06:42.750> about<00:06:42.870> a<00:06:43.169> road<00:06:43.439> map<00:06:43.680> and<00:06:44.009> our<00:06:44.250> stack 00:06:44.600 --> 00:06:44.610 align:start position:0% to you about a road map and our stack 00:06:44.610 --> 00:06:47.480 align:start position:0% to you about a road map and our stack and<00:06:44.969> then<00:06:45.419> we'll<00:06:46.259> forming<00:06:47.039> a<00:06:47.129> certification 00:06:47.480 --> 00:06:47.490 align:start position:0% and then we'll forming a certification 00:06:47.490 --> 00:06:49.100 align:start position:0% and then we'll forming a certification working<00:06:48.150> group<00:06:48.300> and<00:06:48.479> actually<00:06:48.629> now<00:06:48.930> we're 00:06:49.100 --> 00:06:49.110 align:start position:0% working group and actually now we're 00:06:49.110 --> 00:06:52.939 align:start position:0% working group and actually now we're going<00:06:49.199> to<00:06:49.259> form<00:06:49.500> a<00:06:50.120> global<00:06:51.120> test<00:06:51.360> net<00:06:51.659> and<00:06:52.199> that 00:06:52.939 --> 00:06:52.949 align:start position:0% going to form a global test net and that 00:06:52.949 --> 00:06:54.860 align:start position:0% going to form a global test net and that global<00:06:53.310> test<00:06:53.520> and<00:06:53.819> that<00:06:53.909> means<00:06:54.120> if<00:06:54.539> you<00:06:54.689> guys 00:06:54.860 --> 00:06:54.870 align:start position:0% global test and that means if you guys 00:06:54.870 --> 00:06:56.990 align:start position:0% global test and that means if you guys are<00:06:55.110> writing<00:06:55.319> solutions<00:06:55.979> based<00:06:56.729> on 00:06:56.990 --> 00:06:57.000 align:start position:0% are writing solutions based on 00:06:57.000 --> 00:07:00.740 align:start position:0% are writing solutions based on enterprise<00:06:57.810> aetherium<00:06:58.620> and<00:06:59.120> you<00:07:00.120> can<00:07:00.330> use<00:07:00.569> our 00:07:00.740 --> 00:07:00.750 align:start position:0% enterprise aetherium and you can use our 00:07:00.750 --> 00:07:02.480 align:start position:0% enterprise aetherium and you can use our test<00:07:00.990> net<00:07:01.289> and<00:07:01.500> that<00:07:01.800> we<00:07:01.919> have<00:07:02.069> a<00:07:02.099> goal<00:07:02.370> of 00:07:02.480 --> 00:07:02.490 align:start position:0% test net and that we have a goal of 00:07:02.490 --> 00:07:04.040 align:start position:0% test net and that we have a goal of getting<00:07:02.639> that<00:07:02.879> up<00:07:03.030> and<00:07:03.180> running<00:07:03.360> we<00:07:03.689> now<00:07:03.870> have 00:07:04.040 --> 00:07:04.050 align:start position:0% getting that up and running we now have 00:07:04.050 --> 00:07:05.629 align:start position:0% getting that up and running we now have a<00:07:04.080> commitment<00:07:04.500> from<00:07:04.740> different<00:07:05.460> companies 00:07:05.629 --> 00:07:05.639 align:start position:0% a commitment from different companies 00:07:05.639 --> 00:07:07.760 align:start position:0% a commitment from different companies including<00:07:06.360> Microsoft<00:07:06.840> to<00:07:07.050> help<00:07:07.199> us<00:07:07.379> do<00:07:07.590> this 00:07:07.760 --> 00:07:07.770 align:start position:0% including Microsoft to help us do this 00:07:07.770 --> 00:07:11.059 align:start position:0% including Microsoft to help us do this so<00:07:08.580> we<00:07:09.210> plan<00:07:09.509> to<00:07:09.810> implement<00:07:10.680> that<00:07:10.800> and<00:07:10.949> then 00:07:11.059 --> 00:07:11.069 align:start position:0% so we plan to implement that and then 00:07:11.069 --> 00:07:13.189 align:start position:0% so we plan to implement that and then you<00:07:11.159> can<00:07:11.340> actually<00:07:11.490> have<00:07:11.969> your<00:07:12.659> customers 00:07:13.189 --> 00:07:13.199 align:start position:0% you can actually have your customers 00:07:13.199 --> 00:07:14.209 align:start position:0% you can actually have your customers that<00:07:13.349> they<00:07:13.439> don't<00:07:13.590> have<00:07:13.680> to<00:07:13.770> be<00:07:13.860> a<00:07:13.889> member<00:07:14.129> of 00:07:14.209 --> 00:07:14.219 align:start position:0% that they don't have to be a member of 00:07:14.219 --> 00:07:16.129 align:start position:0% that they don't have to be a member of the<00:07:14.340> org<00:07:14.550> and<00:07:14.729> they<00:07:15.090> can<00:07:15.270> they<00:07:15.449> can<00:07:15.689> they<00:07:15.900> can 00:07:16.129 --> 00:07:16.139 align:start position:0% the org and they can they can they can 00:07:16.139 --> 00:07:19.100 align:start position:0% the org and they can they can they can use<00:07:16.319> it<00:07:16.500> and<00:07:16.969> I'm<00:07:17.969> just<00:07:18.029> checking<00:07:18.479> the<00:07:18.569> time<00:07:18.810> is 00:07:19.100 --> 00:07:19.110 align:start position:0% use it and I'm just checking the time is 00:07:19.110 --> 00:07:21.230 align:start position:0% use it and I'm just checking the time is it<00:07:19.229> tracking<00:07:19.650> there<00:07:19.830> or<00:07:20.009> where<00:07:20.219> is<00:07:20.400> it<00:07:20.580> the 00:07:21.230 --> 00:07:21.240 align:start position:0% it tracking there or where is it the 00:07:21.240 --> 00:07:24.920 align:start position:0% it tracking there or where is it the track<00:07:21.539> the<00:07:21.689> time<00:07:23.120> you're<00:07:24.120> there<00:07:24.360> keep<00:07:24.810> me 00:07:24.920 --> 00:07:24.930 align:start position:0% track the time you're there keep me 00:07:24.930 --> 00:07:29.689 align:start position:0% track the time you're there keep me posted<00:07:25.110> okay<00:07:26.330> so<00:07:27.330> another<00:07:27.779> another<00:07:28.699> thing 00:07:29.689 --> 00:07:29.699 align:start position:0% posted okay so another another thing 00:07:29.699 --> 00:07:31.730 align:start position:0% posted okay so another another thing that<00:07:29.879> we<00:07:29.969> do<00:07:30.240> is<00:07:30.509> we<00:07:30.960> now<00:07:31.110> have<00:07:31.139> associate 00:07:31.730 --> 00:07:31.740 align:start position:0% that we do is we now have associate 00:07:31.740 --> 00:07:33.950 align:start position:0% that we do is we now have associate member<00:07:32.069> program<00:07:32.729> so<00:07:33.150> I<00:07:33.389> don't<00:07:33.569> know<00:07:33.629> some<00:07:33.870> of 00:07:33.950 --> 00:07:33.960 align:start position:0% member program so I don't know some of 00:07:33.960 --> 00:07:35.719 align:start position:0% member program so I don't know some of you<00:07:34.080> saw<00:07:34.259> but<00:07:34.469> we<00:07:34.620> entered<00:07:35.340> an<00:07:35.460> agreement 00:07:35.719 --> 00:07:35.729 align:start position:0% you saw but we entered an agreement 00:07:35.729 --> 00:07:38.510 align:start position:0% you saw but we entered an agreement hyper<00:07:36.060> ledger<00:07:36.360> and<00:07:36.689> I<00:07:37.349> was<00:07:37.919> invited<00:07:38.189> to 00:07:38.510 --> 00:07:38.520 align:start position:0% hyper ledger and I was invited to 00:07:38.520 --> 00:07:40.129 align:start position:0% hyper ledger and I was invited to present<00:07:38.669> and<00:07:39.060> we<00:07:39.120> did<00:07:39.300> get<00:07:39.449> an<00:07:39.569> applause<00:07:39.840> when 00:07:40.129 --> 00:07:40.139 align:start position:0% present and we did get an applause when 00:07:40.139 --> 00:07:41.719 align:start position:0% present and we did get an applause when brian<00:07:40.590> behlendorf<00:07:40.830> and<00:07:41.250> i<00:07:41.279> know<00:07:41.340> if<00:07:41.460> he's<00:07:41.550> here 00:07:41.719 --> 00:07:41.729 align:start position:0% brian behlendorf and i know if he's here 00:07:41.729 --> 00:07:45.350 align:start position:0% brian behlendorf and i know if he's here it<00:07:42.000> invited<00:07:42.900> me<00:07:43.020> but<00:07:43.729> at<00:07:44.729> the<00:07:44.819> end<00:07:44.849> of<00:07:45.089> the<00:07:45.180> day 00:07:45.350 --> 00:07:45.360 align:start position:0% it invited me but at the end of the day 00:07:45.360 --> 00:07:47.809 align:start position:0% it invited me but at the end of the day I<00:07:45.719> encourage<00:07:46.560> the<00:07:46.860> the<00:07:47.129> folks<00:07:47.370> who<00:07:47.490> work<00:07:47.610> on 00:07:47.809 --> 00:07:47.819 align:start position:0% I encourage the the folks who work on 00:07:47.819 --> 00:07:49.640 align:start position:0% I encourage the the folks who work on fabric<00:07:48.300> to<00:07:48.539> develop<00:07:48.900> a<00:07:48.960> version<00:07:49.169> that<00:07:49.529> could 00:07:49.640 --> 00:07:49.650 align:start position:0% fabric to develop a version that could 00:07:49.650 --> 00:07:52.959 align:start position:0% fabric to develop a version that could conform<00:07:50.250> to<00:07:50.400> the<00:07:50.490> a<00:07:50.520> spec<00:07:51.029> and<00:07:51.300> and<00:07:52.169> since<00:07:52.589> they 00:07:52.959 --> 00:07:52.969 align:start position:0% conform to the a spec and and since they 00:07:52.969 --> 00:07:55.339 align:start position:0% conform to the a spec and and since they they're<00:07:53.969> not<00:07:54.000> a<00:07:54.180> standards<00:07:54.659> org<00:07:54.900> there's<00:07:55.259> a 00:07:55.339 --> 00:07:55.349 align:start position:0% they're not a standards org there's a 00:07:55.349 --> 00:07:57.529 align:start position:0% they're not a standards org there's a very<00:07:55.560> good<00:07:55.830> synergy<00:07:56.069> and<00:07:56.490> we<00:07:56.940> invite<00:07:57.270> all 00:07:57.529 --> 00:07:57.539 align:start position:0% very good synergy and we invite all 00:07:57.539 --> 00:07:59.659 align:start position:0% very good synergy and we invite all these<00:07:57.960> other<00:07:58.199> orgs<00:07:58.620> and<00:07:58.710> around<00:07:59.159> me<00:07:59.310> that 00:07:59.659 --> 00:07:59.669 align:start position:0% these other orgs and around me that 00:07:59.669 --> 00:08:01.820 align:start position:0% these other orgs and around me that could<00:08:00.060> be<00:08:00.180> synergistic<00:08:00.659> because<00:08:01.199> there<00:08:01.680> isn't 00:08:01.820 --> 00:08:01.830 align:start position:0% could be synergistic because there isn't 00:08:01.830 --> 00:08:03.890 align:start position:0% could be synergistic because there isn't any<00:08:02.069> one<00:08:02.279> org<00:08:02.610> that<00:08:02.849> really<00:08:03.210> solves<00:08:03.449> all<00:08:03.779> the 00:08:03.890 --> 00:08:03.900 align:start position:0% any one org that really solves all the 00:08:03.900 --> 00:08:06.379 align:start position:0% any one org that really solves all the problems<00:08:03.930> that<00:08:04.409> you<00:08:04.650> need<00:08:04.770> for<00:08:05.389> delivered 00:08:06.379 --> 00:08:06.389 align:start position:0% problems that you need for delivered 00:08:06.389 --> 00:08:09.860 align:start position:0% problems that you need for delivered developing<00:08:07.110> solutions<00:08:07.620> for<00:08:08.120> blockchain<00:08:09.120> we 00:08:09.860 --> 00:08:09.870 align:start position:0% developing solutions for blockchain we 00:08:09.870 --> 00:08:12.140 align:start position:0% developing solutions for blockchain we also<00:08:10.050> are<00:08:10.379> very<00:08:10.439> involved<00:08:10.979> with<00:08:11.219> the<00:08:11.550> the<00:08:12.120> the 00:08:12.140 --> 00:08:12.150 align:start position:0% also are very involved with the the the 00:08:12.150 --> 00:08:14.029 align:start position:0% also are very involved with the the the deaf<00:08:12.659> organization<00:08:13.379> some<00:08:13.560> of<00:08:13.650> the<00:08:13.710> folks<00:08:13.889> are 00:08:14.029 --> 00:08:14.039 align:start position:0% deaf organization some of the folks are 00:08:14.039 --> 00:08:15.469 align:start position:0% deaf organization some of the folks are familiar<00:08:14.370> with<00:08:14.430> the<00:08:14.550> organizations<00:08:15.180> that<00:08:15.210> do 00:08:15.469 --> 00:08:15.479 align:start position:0% familiar with the organizations that do 00:08:15.479 --> 00:08:18.679 align:start position:0% familiar with the organizations that do social<00:08:16.199> impact<00:08:16.560> we<00:08:17.189> we<00:08:17.729> don't<00:08:17.939> plan<00:08:18.210> to<00:08:18.360> deal 00:08:18.679 --> 00:08:18.689 align:start position:0% social impact we we don't plan to deal 00:08:18.689 --> 00:08:20.719 align:start position:0% social impact we we don't plan to deal with<00:08:18.839> and<00:08:19.080> write<00:08:19.349> solutions<00:08:20.039> for<00:08:20.219> identity 00:08:20.719 --> 00:08:20.729 align:start position:0% with and write solutions for identity 00:08:20.729 --> 00:08:23.540 align:start position:0% with and write solutions for identity we'll<00:08:21.120> partner<00:08:21.479> with<00:08:21.539> the<00:08:21.719> w3c<00:08:22.080> with<00:08:22.889> deaf<00:08:23.159> ID 00:08:23.540 --> 00:08:23.550 align:start position:0% we'll partner with the w3c with deaf ID 00:08:23.550 --> 00:08:25.790 align:start position:0% we'll partner with the w3c with deaf ID 2020<00:08:24.419> and<00:08:24.599> come<00:08:25.080> up<00:08:25.199> with<00:08:25.259> the<00:08:25.349> solutions 00:08:25.790 --> 00:08:25.800 align:start position:0% 2020 and come up with the solutions 00:08:25.800 --> 00:08:27.409 align:start position:0% 2020 and come up with the solutions Perce<00:08:26.069> again<00:08:26.370> we<00:08:26.580> don't<00:08:26.759> want<00:08:26.909> to<00:08:27.120> reinvent 00:08:27.409 --> 00:08:27.419 align:start position:0% Perce again we don't want to reinvent 00:08:27.419 --> 00:08:31.129 align:start position:0% Perce again we don't want to reinvent the<00:08:27.509> wheel<00:08:28.129> and<00:08:29.129> so<00:08:29.729> how<00:08:30.089> we<00:08:30.150> operate<00:08:30.719> we<00:08:30.930> have 00:08:31.129 --> 00:08:31.139 align:start position:0% the wheel and so how we operate we have 00:08:31.139 --> 00:08:32.899 align:start position:0% the wheel and so how we operate we have technical<00:08:31.770> work<00:08:31.979> technical<00:08:32.579> working<00:08:32.760> groups 00:08:32.899 --> 00:08:32.909 align:start position:0% technical work technical working groups 00:08:32.909 --> 00:08:35.329 align:start position:0% technical work technical working groups we<00:08:33.240> also<00:08:33.390> have<00:08:33.539> special<00:08:33.899> interest<00:08:34.229> groups<00:08:34.469> and 00:08:35.329 --> 00:08:35.339 align:start position:0% we also have special interest groups and 00:08:35.339 --> 00:08:37.069 align:start position:0% we also have special interest groups and so<00:08:35.729> we<00:08:35.849> have<00:08:36.029> one<00:08:36.240> for<00:08:36.419> financial<00:08:36.930> services 00:08:37.069 --> 00:08:37.079 align:start position:0% so we have one for financial services 00:08:37.079 --> 00:08:40.279 align:start position:0% so we have one for financial services one<00:08:37.709> for<00:08:37.979> help<00:08:38.130> and<00:08:38.399> it's<00:08:38.930> we're<00:08:39.930> member 00:08:40.279 --> 00:08:40.289 align:start position:0% one for help and it's we're member 00:08:40.289 --> 00:08:43.040 align:start position:0% one for help and it's we're member driven<00:08:40.500> org<00:08:40.890> we<00:08:41.820> don't<00:08:42.300> run<00:08:42.510> the<00:08:42.630> org<00:08:42.839> the 00:08:43.040 --> 00:08:43.050 align:start position:0% driven org we don't run the org the 00:08:43.050 --> 00:08:45.170 align:start position:0% driven org we don't run the org the members<00:08:43.380> do<00:08:43.560> so<00:08:43.800> if<00:08:43.890> anybody<00:08:44.250> wanted<00:08:44.760> to<00:08:44.940> have 00:08:45.170 --> 00:08:45.180 align:start position:0% members do so if anybody wanted to have 00:08:45.180 --> 00:08:46.730 align:start position:0% members do so if anybody wanted to have more<00:08:45.329> visibility<00:08:45.720> whatever<00:08:46.350> you<00:08:46.470> whatever 00:08:46.730 --> 00:08:46.740 align:start position:0% more visibility whatever you whatever 00:08:46.740 --> 00:08:49.700 align:start position:0% more visibility whatever you whatever members<00:08:47.310> want<00:08:47.520> to<00:08:47.640> see<00:08:47.819> they<00:08:48.449> join<00:08:48.810> and<00:08:49.050> they 00:08:49.700 --> 00:08:49.710 align:start position:0% members want to see they join and they 00:08:49.710 --> 00:08:52.730 align:start position:0% members want to see they join and they raise<00:08:49.980> their<00:08:50.220> hands<00:08:50.400> and<00:08:50.580> they<00:08:50.730> they<00:08:51.210> can<00:08:51.780> make 00:08:52.730 --> 00:08:52.740 align:start position:0% raise their hands and they they can make 00:08:52.740 --> 00:08:54.560 align:start position:0% raise their hands and they they can make it<00:08:52.890> happen<00:08:53.280> so<00:08:53.580> that<00:08:53.730> that's<00:08:54.000> how<00:08:54.150> the<00:08:54.210> org 00:08:54.560 --> 00:08:54.570 align:start position:0% it happen so that that's how the org 00:08:54.570 --> 00:08:56.270 align:start position:0% it happen so that that's how the org works<00:08:54.930> and<00:08:55.350> that's<00:08:55.410> how<00:08:55.620> while<00:08:55.800> standard 00:08:56.270 --> 00:08:56.280 align:start position:0% works and that's how while standard 00:08:56.280 --> 00:09:01.520 align:start position:0% works and that's how while standard sword<00:08:56.490> works<00:08:57.800> so<00:08:58.910> with<00:08:59.910> that<00:09:00.090> I<00:09:00.390> wanted<00:09:01.350> to 00:09:01.520 --> 00:09:01.530 align:start position:0% sword works so with that I wanted to 00:09:01.530 --> 00:09:05.900 align:start position:0% sword works so with that I wanted to bring<00:09:02.070> up<00:09:02.220> Connor<00:09:02.870> so<00:09:03.870> I<00:09:04.740> come<00:09:05.550> out<00:09:05.670> of<00:09:05.820> the 00:09:05.900 --> 00:09:05.910 align:start position:0% bring up Connor so I come out of the 00:09:05.910 --> 00:09:08.090 align:start position:0% bring up Connor so I come out of the world<00:09:06.060> the<00:09:06.180> telecom<00:09:06.660> and<00:09:07.080> telecom<00:09:07.710> they<00:09:07.860> have 00:09:08.090 --> 00:09:08.100 align:start position:0% world the telecom and telecom they have 00:09:08.100 --> 00:09:12.200 align:start position:0% world the telecom and telecom they have it's<00:09:08.280> called<00:09:08.430> an<00:09:08.640> OSI<00:09:09.090> 7<00:09:09.150> layer<00:09:09.540> stack<00:09:10.940> we<00:09:11.940> want 00:09:12.200 --> 00:09:12.210 align:start position:0% it's called an OSI 7 layer stack we want 00:09:12.210 --> 00:09:14.890 align:start position:0% it's called an OSI 7 layer stack we want to<00:09:12.330> formalize<00:09:12.840> how<00:09:13.530> work<00:09:14.280> is<00:09:14.490> done 00:09:14.890 --> 00:09:14.900 align:start position:0% to formalize how work is done 00:09:14.900 --> 00:09:17.000 align:start position:0% to formalize how work is done technically<00:09:15.900> so<00:09:16.470> you<00:09:16.530> can<00:09:16.770> have<00:09:16.860> multiple 00:09:17.000 --> 00:09:17.010 align:start position:0% technically so you can have multiple 00:09:17.010 --> 00:09:19.130 align:start position:0% technically so you can have multiple vendors<00:09:17.550> of<00:09:17.850> choice<00:09:18.120> and<00:09:18.570> by<00:09:18.750> the<00:09:18.810> way<00:09:18.930> this 00:09:19.130 --> 00:09:19.140 align:start position:0% vendors of choice and by the way this 00:09:19.140 --> 00:09:20.720 align:start position:0% vendors of choice and by the way this stack<00:09:19.530> you<00:09:20.190> don't<00:09:20.340> even<00:09:20.430> need<00:09:20.520> to<00:09:20.580> take<00:09:20.700> a 00:09:20.720 --> 00:09:20.730 align:start position:0% stack you don't even need to take a 00:09:20.730 --> 00:09:23.480 align:start position:0% stack you don't even need to take a photo<00:09:21.080> if<00:09:22.080> you<00:09:22.290> go<00:09:22.440> to<00:09:22.500> our<00:09:22.650> website<00:09:22.830> you<00:09:23.400> don't 00:09:23.480 --> 00:09:23.490 align:start position:0% photo if you go to our website you don't 00:09:23.490 --> 00:09:25.760 align:start position:0% photo if you go to our website you don't even<00:09:23.790> I<00:09:24.060> now<00:09:24.420> you<00:09:24.480> don't<00:09:24.900> even<00:09:25.050> have<00:09:25.290> to<00:09:25.500> say 00:09:25.760 --> 00:09:25.770 align:start position:0% even I now you don't even have to say 00:09:25.770 --> 00:09:28.880 align:start position:0% even I now you don't even have to say who<00:09:25.950> you<00:09:26.130> are<00:09:26.310> because<00:09:26.820> you<00:09:27.750> can<00:09:28.380> just<00:09:28.590> go<00:09:28.830> to 00:09:28.880 --> 00:09:28.890 align:start position:0% who you are because you can just go to 00:09:28.890 --> 00:09:30.830 align:start position:0% who you are because you can just go to our<00:09:29.040> website<00:09:29.520> and<00:09:29.850> you<00:09:30.270> can<00:09:30.390> download<00:09:30.630> our 00:09:30.830 --> 00:09:30.840 align:start position:0% our website and you can download our 00:09:30.840 --> 00:09:33.470 align:start position:0% our website and you can download our stack<00:09:31.200> and<00:09:31.440> our<00:09:31.530> spec<00:09:31.890> everything<00:09:32.610> and<00:09:33.120> just 00:09:33.470 --> 00:09:33.480 align:start position:0% stack and our spec everything and just 00:09:33.480 --> 00:09:35.570 align:start position:0% stack and our spec everything and just do<00:09:34.320> whatever<00:09:34.500> you<00:09:34.680> want<00:09:34.920> in<00:09:35.070> developing 00:09:35.570 --> 00:09:35.580 align:start position:0% do whatever you want in developing 00:09:35.580 --> 00:09:38.060 align:start position:0% do whatever you want in developing whatever<00:09:36.060> you<00:09:36.270> want<00:09:36.480> and<00:09:36.720> then<00:09:37.410> if<00:09:37.620> you<00:09:37.860> want 00:09:38.060 --> 00:09:38.070 align:start position:0% whatever you want and then if you want 00:09:38.070 --> 00:09:40.880 align:start position:0% whatever you want and then if you want to<00:09:38.160> use<00:09:38.280> our<00:09:38.430> logo<00:09:39.060> or<00:09:39.900> go<00:09:40.620> through<00:09:40.770> our 00:09:40.880 --> 00:09:40.890 align:start position:0% to use our logo or go through our 00:09:40.890 --> 00:09:43.970 align:start position:0% to use our logo or go through our certification<00:09:41.640> process<00:09:42.150> process<00:09:42.990> then<00:09:43.560> you 00:09:43.970 --> 00:09:43.980 align:start position:0% certification process process then you 00:09:43.980 --> 00:09:45.920 align:start position:0% certification process process then you would<00:09:44.220> we<00:09:44.880> you<00:09:45.150> would<00:09:45.270> be<00:09:45.390> asked<00:09:45.690> to<00:09:45.810> join 00:09:45.920 --> 00:09:45.930 align:start position:0% would we you would be asked to join 00:09:45.930 --> 00:09:47.140 align:start position:0% would we you would be asked to join because<00:09:46.290> of<00:09:46.560> intellectual<00:09:47.100> property 00:09:47.140 --> 00:09:47.150 align:start position:0% because of intellectual property 00:09:47.150 --> 00:09:49.910 align:start position:0% because of intellectual property requirements<00:09:48.150> etc<00:09:48.270> but<00:09:49.110> anybody<00:09:49.410> here<00:09:49.740> can 00:09:49.910 --> 00:09:49.920 align:start position:0% requirements etc but anybody here can 00:09:49.920 --> 00:09:52.220 align:start position:0% requirements etc but anybody here can can<00:09:50.370> download<00:09:50.610> our<00:09:50.820> spec<00:09:51.210> and<00:09:51.450> work<00:09:51.600> on<00:09:51.810> an 00:09:52.220 --> 00:09:52.230 align:start position:0% can download our spec and work on an 00:09:52.230 --> 00:09:54.620 align:start position:0% can download our spec and work on an enterprise<00:09:52.890> etherium<00:09:53.640> so<00:09:54.180> I'll<00:09:54.240> turn<00:09:54.390> it<00:09:54.510> over 00:09:54.620 --> 00:09:54.630 align:start position:0% enterprise etherium so I'll turn it over 00:09:54.630 --> 00:09:55.760 align:start position:0% enterprise etherium so I'll turn it over to<00:09:54.750> Connor<00:09:54.990> he's<00:09:55.230> going<00:09:55.380> to<00:09:55.440> walk<00:09:55.620> you<00:09:55.740> through 00:09:55.760 --> 00:09:55.770 align:start position:0% to Connor he's going to walk you through 00:09:55.770 --> 00:09:56.990 align:start position:0% to Connor he's going to walk you through and<00:09:56.130> talk<00:09:56.280> to<00:09:56.370> you<00:09:56.430> a<00:09:56.520> bit<00:09:56.640> about<00:09:56.670> our 00:09:56.990 --> 00:09:57.000 align:start position:0% and talk to you a bit about our 00:09:57.000 --> 00:10:00.470 align:start position:0% and talk to you a bit about our architecture<00:09:57.540> stack<00:09:58.910> thanks<00:09:59.910> Ron<00:10:00.180> hey 00:10:00.470 --> 00:10:00.480 align:start position:0% architecture stack thanks Ron hey 00:10:00.480 --> 00:10:05.990 align:start position:0% architecture stack thanks Ron hey everyone<00:10:00.840> so<00:10:02.840> I'm<00:10:04.040> the<00:10:05.040> chair<00:10:05.460> of<00:10:05.550> the<00:10:05.730> tech 00:10:05.990 --> 00:10:06.000 align:start position:0% everyone so I'm the chair of the tech 00:10:06.000 --> 00:10:09.140 align:start position:0% everyone so I'm the chair of the tech spec<00:10:06.240> working<00:10:06.630> group<00:10:06.870> but<00:10:07.080> I'm<00:10:07.230> also<00:10:07.560> a<00:10:08.400> guest 00:10:09.140 --> 00:10:09.150 align:start position:0% spec working group but I'm also a guest 00:10:09.150 --> 00:10:11.180 align:start position:0% spec working group but I'm also a guest developer<00:10:09.600> by<00:10:09.750> background<00:10:10.290> I<00:10:10.410> wrote<00:10:10.560> web<00:10:10.740> 3j 00:10:11.180 --> 00:10:11.190 align:start position:0% developer by background I wrote web 3j 00:10:11.190 --> 00:10:12.770 align:start position:0% developer by background I wrote web 3j the<00:10:11.430> Java<00:10:11.730> library<00:10:12.120> for<00:10:12.300> working<00:10:12.570> with<00:10:12.690> the 00:10:12.770 --> 00:10:12.780 align:start position:0% the Java library for working with the 00:10:12.780 --> 00:10:15.590 align:start position:0% the Java library for working with the theorem<00:10:13.140> and<00:10:13.260> have<00:10:13.410> my<00:10:13.560> own<00:10:14.600> blockchain 00:10:15.590 --> 00:10:15.600 align:start position:0% theorem and have my own blockchain 00:10:15.600 --> 00:10:17.870 align:start position:0% theorem and have my own blockchain technology<00:10:16.260> startup<00:10:16.680> as<00:10:16.830> well<00:10:17.010> so<00:10:17.220> I<00:10:17.250> come<00:10:17.760> at 00:10:17.870 --> 00:10:17.880 align:start position:0% technology startup as well so I come at 00:10:17.880 --> 00:10:20.300 align:start position:0% technology startup as well so I come at this<00:10:18.000> from<00:10:18.060> a<00:10:18.570> I<00:10:18.990> guess<00:10:19.230> they've<00:10:19.590> perspective 00:10:20.300 --> 00:10:20.310 align:start position:0% this from a I guess they've perspective 00:10:20.310 --> 00:10:23.270 align:start position:0% this from a I guess they've perspective ultimately<00:10:21.260> the<00:10:22.260> idea<00:10:22.590> they<00:10:22.830> with<00:10:23.040> the 00:10:23.270 --> 00:10:23.280 align:start position:0% ultimately the idea they with the 00:10:23.280 --> 00:10:25.850 align:start position:0% ultimately the idea they with the architecture<00:10:24.120> stack<00:10:24.360> as<00:10:24.570> Ron<00:10:24.720> said<00:10:24.770> you<00:10:25.770> know 00:10:25.850 --> 00:10:25.860 align:start position:0% architecture stack as Ron said you know 00:10:25.860 --> 00:10:28.670 align:start position:0% architecture stack as Ron said you know I<00:10:26.250> guess<00:10:26.730> inspiration<00:10:27.510> was<00:10:27.720> the<00:10:27.750> the<00:10:28.320> eye<00:10:28.350> size 00:10:28.670 --> 00:10:28.680 align:start position:0% I guess inspiration was the the eye size 00:10:28.680 --> 00:10:31.070 align:start position:0% I guess inspiration was the the eye size seven<00:10:29.010> layer<00:10:29.160> model<00:10:29.220> but<00:10:30.090> really<00:10:30.420> it<00:10:30.840> was<00:10:31.050> that 00:10:31.070 --> 00:10:31.080 align:start position:0% seven layer model but really it was that 00:10:31.080 --> 00:10:34.340 align:start position:0% seven layer model but really it was that the<00:10:31.500> first<00:10:31.820> artifact<00:10:32.820> that<00:10:33.240> they<00:10:33.350> produced 00:10:34.340 --> 00:10:34.350 align:start position:0% the first artifact that they produced 00:10:34.350 --> 00:10:36.560 align:start position:0% the first artifact that they produced and<00:10:34.800> put<00:10:34.920> out<00:10:35.100> there<00:10:35.370> is<00:10:35.580> a<00:10:35.610> reference<00:10:36.060> points 00:10:36.560 --> 00:10:36.570 align:start position:0% and put out there is a reference points 00:10:36.570 --> 00:10:38.450 align:start position:0% and put out there is a reference points to<00:10:36.990> try<00:10:37.260> and<00:10:37.380> capture<00:10:37.590> everything<00:10:37.950> that<00:10:38.370> we're 00:10:38.450 --> 00:10:38.460 align:start position:0% to try and capture everything that we're 00:10:38.460 --> 00:10:41.380 align:start position:0% to try and capture everything that we're thinking<00:10:38.670> about<00:10:39.150> with<00:10:40.080> respect<00:10:40.290> to<00:10:40.800> the<00:10:40.980> EA 00:10:41.380 --> 00:10:41.390 align:start position:0% thinking about with respect to the EA 00:10:41.390 --> 00:10:44.570 align:start position:0% thinking about with respect to the EA the<00:10:42.390> actual<00:10:42.660> inspiration<00:10:42.990> for<00:10:43.800> the<00:10:43.980> stack<00:10:44.250> was 00:10:44.570 --> 00:10:44.580 align:start position:0% the actual inspiration for the stack was 00:10:44.580 --> 00:10:46.700 align:start position:0% the actual inspiration for the stack was a<00:10:45.000> talk<00:10:45.330> that<00:10:45.540> was<00:10:45.630> done<00:10:45.810> at<00:10:45.930> Def<00:10:46.080> Con<00:10:46.110> last 00:10:46.700 --> 00:10:46.710 align:start position:0% a talk that was done at Def Con last 00:10:46.710 --> 00:10:51.230 align:start position:0% a talk that was done at Def Con last year<00:10:47.040> where<00:10:47.430> one<00:10:48.330> of<00:10:48.450> the<00:10:50.000> developers<00:10:51.000> working 00:10:51.230 --> 00:10:51.240 align:start position:0% year where one of the developers working 00:10:51.240 --> 00:10:54.050 align:start position:0% year where one of the developers working for<00:10:51.540> the<00:10:51.600> foundation<00:10:52.340> did<00:10:53.340> a<00:10:53.370> talk<00:10:53.610> on<00:10:53.640> the 00:10:54.050 --> 00:10:54.060 align:start position:0% for the foundation did a talk on the 00:10:54.060 --> 00:10:55.880 align:start position:0% for the foundation did a talk on the anatomy<00:10:54.510> of<00:10:54.540> an<00:10:54.720> aetherium<00:10:55.260> clients<00:10:55.710> and<00:10:55.800> one 00:10:55.880 --> 00:10:55.890 align:start position:0% anatomy of an aetherium clients and one 00:10:55.890 --> 00:10:57.380 align:start position:0% anatomy of an aetherium clients and one of<00:10:56.010> the<00:10:56.070> really<00:10:56.190> neat<00:10:56.610> things<00:10:56.850> that<00:10:57.090> they<00:10:57.180> did 00:10:57.380 --> 00:10:57.390 align:start position:0% of the really neat things that they did 00:10:57.390 --> 00:10:58.580 align:start position:0% of the really neat things that they did there<00:10:57.570> was<00:10:57.720> they<00:10:57.900> highlighted<00:10:58.320> the 00:10:58.580 --> 00:10:58.590 align:start position:0% there was they highlighted the 00:10:58.590 --> 00:11:00.320 align:start position:0% there was they highlighted the components<00:10:59.160> in<00:10:59.250> yellow<00:10:59.550> that<00:10:59.790> were<00:10:59.910> aligned 00:11:00.320 --> 00:11:00.330 align:start position:0% components in yellow that were aligned 00:11:00.330 --> 00:11:02.670 align:start position:0% components in yellow that were aligned with<00:11:00.510> the<00:11:00.600> yellow<00:11:00.810> paper<00:11:01.020> and 00:11:02.670 --> 00:11:02.680 align:start position:0% with the yellow paper and 00:11:02.680 --> 00:11:05.160 align:start position:0% with the yellow paper and basically<00:11:03.639> adopted<00:11:04.029> that<00:11:04.149> idea<00:11:04.540> as<00:11:04.720> well<00:11:04.959> so<00:11:05.110> I 00:11:05.160 --> 00:11:05.170 align:start position:0% basically adopted that idea as well so I 00:11:05.170 --> 00:11:06.960 align:start position:0% basically adopted that idea as well so I thought<00:11:05.319> it's<00:11:05.439> a<00:11:05.499> really<00:11:05.709> neat<00:11:06.040> way<00:11:06.220> of<00:11:06.249> you 00:11:06.960 --> 00:11:06.970 align:start position:0% thought it's a really neat way of you 00:11:06.970 --> 00:11:08.519 align:start position:0% thought it's a really neat way of you know<00:11:07.029> talking<00:11:07.329> in<00:11:07.600> terms<00:11:07.779> of<00:11:08.079> where<00:11:08.350> these 00:11:08.519 --> 00:11:08.529 align:start position:0% know talking in terms of where these 00:11:08.529 --> 00:11:10.019 align:start position:0% know talking in terms of where these things<00:11:08.709> are<00:11:08.889> formally<00:11:09.249> specified<00:11:09.759> in<00:11:09.939> the 00:11:10.019 --> 00:11:10.029 align:start position:0% things are formally specified in the 00:11:10.029 --> 00:11:12.569 align:start position:0% things are formally specified in the yellow<00:11:10.240> paper<00:11:10.470> then<00:11:11.470> also<00:11:11.649> those<00:11:11.980> components 00:11:12.569 --> 00:11:12.579 align:start position:0% yellow paper then also those components 00:11:12.579 --> 00:11:14.970 align:start position:0% yellow paper then also those components that<00:11:12.759> are<00:11:12.970> core<00:11:13.329> to<00:11:13.360> just<00:11:14.170> general<00:11:14.470> aetherium 00:11:14.970 --> 00:11:14.980 align:start position:0% that are core to just general aetherium 00:11:14.980 --> 00:11:16.859 align:start position:0% that are core to just general aetherium and<00:11:15.220> then<00:11:15.369> we<00:11:15.490> added<00:11:15.730> on<00:11:15.879> a<00:11:16.089> piece<00:11:16.300> which<00:11:16.629> was 00:11:16.859 --> 00:11:16.869 align:start position:0% and then we added on a piece which was 00:11:16.869 --> 00:11:19.049 align:start position:0% and then we added on a piece which was what<00:11:17.230> we<00:11:17.499> see<00:11:17.740> as<00:11:17.860> being<00:11:18.069> answered<00:11:18.369> more<00:11:18.939> in 00:11:19.049 --> 00:11:19.059 align:start position:0% what we see as being answered more in 00:11:19.059 --> 00:11:22.619 align:start position:0% what we see as being answered more in surprise<00:11:19.480> focus<00:11:20.110> pieces<00:11:20.910> the<00:11:21.910> key<00:11:22.089> you<00:11:22.240> always 00:11:22.619 --> 00:11:22.629 align:start position:0% surprise focus pieces the key you always 00:11:22.629 --> 00:11:24.509 align:start position:0% surprise focus pieces the key you always would<00:11:22.809> be<00:11:22.869> EA<00:11:23.079> has<00:11:23.470> been<00:11:23.709> about<00:11:23.949> aetherium 00:11:24.509 --> 00:11:24.519 align:start position:0% would be EA has been about aetherium 00:11:24.519 --> 00:11:27.210 align:start position:0% would be EA has been about aetherium technology<00:11:25.179> and<00:11:25.389> so<00:11:25.629> we<00:11:26.439> will<00:11:26.649> always<00:11:26.769> see<00:11:27.189> the 00:11:27.210 --> 00:11:27.220 align:start position:0% technology and so we will always see the 00:11:27.220 --> 00:11:29.340 align:start position:0% technology and so we will always see the initiatives<00:11:27.819> that<00:11:27.970> we're<00:11:28.119> doing<00:11:28.269> as<00:11:28.689> being<00:11:28.990> a 00:11:29.340 --> 00:11:29.350 align:start position:0% initiatives that we're doing as being a 00:11:29.350 --> 00:11:31.319 align:start position:0% initiatives that we're doing as being a superset<00:11:30.040> of<00:11:30.069> what's<00:11:30.670> happening<00:11:31.119> in<00:11:31.240> the 00:11:31.319 --> 00:11:31.329 align:start position:0% superset of what's happening in the 00:11:31.329 --> 00:11:33.509 align:start position:0% superset of what's happening in the world<00:11:31.420> of<00:11:31.600> public<00:11:31.990> aetherium<00:11:32.499> and<00:11:32.860> we<00:11:33.160> never 00:11:33.509 --> 00:11:33.519 align:start position:0% world of public aetherium and we never 00:11:33.519 --> 00:11:35.429 align:start position:0% world of public aetherium and we never want<00:11:33.759> to<00:11:33.850> sort<00:11:34.089> of<00:11:34.179> be<00:11:34.660> separating<00:11:35.319> ourselves 00:11:35.429 --> 00:11:35.439 align:start position:0% want to sort of be separating ourselves 00:11:35.439 --> 00:11:38.369 align:start position:0% want to sort of be separating ourselves from<00:11:35.860> it<00:11:36.189> because<00:11:36.339> you<00:11:36.819> know<00:11:36.959> many<00:11:37.959> members<00:11:38.350> of 00:11:38.369 --> 00:11:38.379 align:start position:0% from it because you know many members of 00:11:38.379 --> 00:11:40.559 align:start position:0% from it because you know many members of the<00:11:38.619> you<00:11:39.309> know<00:11:39.339> passionate<00:11:39.699> about<00:11:40.149> a<00:11:40.179> theorem 00:11:40.559 --> 00:11:40.569 align:start position:0% the you know passionate about a theorem 00:11:40.569 --> 00:11:42.299 align:start position:0% the you know passionate about a theorem technology<00:11:41.139> that's<00:11:41.350> why<00:11:41.559> they<00:11:41.860> joined<00:11:42.040> up 00:11:42.299 --> 00:11:42.309 align:start position:0% technology that's why they joined up 00:11:42.309 --> 00:11:43.769 align:start position:0% technology that's why they joined up that's<00:11:42.490> what<00:11:42.639> got<00:11:42.819> me<00:11:42.850> into<00:11:43.300> it<00:11:43.420> as<00:11:43.569> well 00:11:43.769 --> 00:11:43.779 align:start position:0% that's what got me into it as well 00:11:43.779 --> 00:11:45.299 align:start position:0% that's what got me into it as well because<00:11:44.050> I<00:11:44.259> came<00:11:44.769> from<00:11:44.889> an<00:11:45.040> enterprise 00:11:45.299 --> 00:11:45.309 align:start position:0% because I came from an enterprise 00:11:45.309 --> 00:11:47.609 align:start position:0% because I came from an enterprise background<00:11:46.059> but<00:11:46.240> then<00:11:46.389> you<00:11:47.379> know<00:11:47.470> really 00:11:47.609 --> 00:11:47.619 align:start position:0% background but then you know really 00:11:47.619 --> 00:11:49.739 align:start position:0% background but then you know really likely<00:11:48.040> theory<00:11:48.279> and<00:11:48.490> technology<00:11:49.089> and<00:11:49.629> it 00:11:49.739 --> 00:11:49.749 align:start position:0% likely theory and technology and it 00:11:49.749 --> 00:11:52.319 align:start position:0% likely theory and technology and it reminds<00:11:50.319> me<00:11:50.379> of<00:11:50.499> the<00:11:51.309> community<00:11:51.759> reminds<00:11:52.209> me 00:11:52.319 --> 00:11:52.329 align:start position:0% reminds me of the community reminds me 00:11:52.329 --> 00:11:54.389 align:start position:0% reminds me of the community reminds me somewhat<00:11:52.959> of<00:11:52.990> the<00:11:53.110> Linux<00:11:53.529> community<00:11:53.769> back<00:11:54.249> in 00:11:54.389 --> 00:11:54.399 align:start position:0% somewhat of the Linux community back in 00:11:54.399 --> 00:11:55.499 align:start position:0% somewhat of the Linux community back in the<00:11:54.490> day<00:11:54.639> and<00:11:54.699> we<00:11:54.819> all<00:11:54.939> know<00:11:55.089> how<00:11:55.300> well<00:11:55.449> that 00:11:55.499 --> 00:11:55.509 align:start position:0% the day and we all know how well that 00:11:55.509 --> 00:11:59.400 align:start position:0% the day and we all know how well that panned<00:11:55.929> out<00:11:56.079> there<00:11:56.319> as<00:11:56.470> well<00:11:57.809> but<00:11:58.809> the<00:11:58.990> the 00:11:59.400 --> 00:11:59.410 align:start position:0% panned out there as well but the the 00:11:59.410 --> 00:12:00.689 align:start position:0% panned out there as well but the the stack<00:11:59.619> I'm<00:11:59.769> not<00:11:59.889> going<00:12:00.040> to<00:12:00.100> go<00:12:00.189> through<00:12:00.459> all 00:12:00.689 --> 00:12:00.699 align:start position:0% stack I'm not going to go through all 00:12:00.699 --> 00:12:02.309 align:start position:0% stack I'm not going to go through all the<00:12:00.819> different<00:12:00.999> layers<00:12:01.329> about<00:12:01.689> it<00:12:01.899> now<00:12:02.079> but<00:12:02.290> I 00:12:02.309 --> 00:12:02.319 align:start position:0% the different layers about it now but I 00:12:02.319 --> 00:12:03.989 align:start position:0% the different layers about it now but I think<00:12:02.410> that<00:12:02.860> the<00:12:03.189> key<00:12:03.339> point<00:12:03.579> is<00:12:03.790> is<00:12:03.970> that 00:12:03.989 --> 00:12:03.999 align:start position:0% think that the key point is is that 00:12:03.999 --> 00:12:06.179 align:start position:0% think that the key point is is that we're<00:12:04.179> trying<00:12:04.329> to<00:12:04.509> just<00:12:04.660> encompass<00:12:05.100> you<00:12:06.100> know 00:12:06.179 --> 00:12:06.189 align:start position:0% we're trying to just encompass you know 00:12:06.189 --> 00:12:08.160 align:start position:0% we're trying to just encompass you know everything<00:12:06.879> that<00:12:06.910> we<00:12:07.149> believe<00:12:07.449> is<00:12:07.689> in<00:12:07.720> scope 00:12:08.160 --> 00:12:08.170 align:start position:0% everything that we believe is in scope 00:12:08.170 --> 00:12:10.079 align:start position:0% everything that we believe is in scope there<00:12:08.470> and<00:12:08.679> she<00:12:08.829> can<00:12:09.040> do<00:12:09.309> certainly<00:12:09.670> review<00:12:09.819> it 00:12:10.079 --> 00:12:10.089 align:start position:0% there and she can do certainly review it 00:12:10.089 --> 00:12:12.389 align:start position:0% there and she can do certainly review it in<00:12:10.179> your<00:12:10.329> own<00:12:10.449> time<00:12:10.720> and<00:12:11.019> go<00:12:11.769> over<00:12:12.069> to<00:12:12.220> the 00:12:12.389 --> 00:12:12.399 align:start position:0% in your own time and go over to the 00:12:12.399 --> 00:12:16.590 align:start position:0% in your own time and go over to the website<00:12:13.269> to<00:12:13.720> review<00:12:14.019> it<00:12:15.149> what<00:12:16.149> I<00:12:16.209> did<00:12:16.360> want<00:12:16.509> to 00:12:16.590 --> 00:12:16.600 align:start position:0% website to review it what I did want to 00:12:16.600 --> 00:12:20.160 align:start position:0% website to review it what I did want to talk<00:12:16.720> about<00:12:17.110> though<00:12:17.319> was<00:12:17.559> the<00:12:19.170> the 00:12:20.160 --> 00:12:20.170 align:start position:0% talk about though was the the 00:12:20.170 --> 00:12:22.139 align:start position:0% talk about though was the the specifications<00:12:21.160> that<00:12:21.339> we've<00:12:21.429> released<00:12:21.610> this 00:12:22.139 --> 00:12:22.149 align:start position:0% specifications that we've released this 00:12:22.149 --> 00:12:24.090 align:start position:0% specifications that we've released this week<00:12:22.389> we<00:12:22.660> released<00:12:22.899> two<00:12:23.079> new<00:12:23.110> specifications 00:12:24.090 --> 00:12:24.100 align:start position:0% week we released two new specifications 00:12:24.100 --> 00:12:27.869 align:start position:0% week we released two new specifications on<00:12:24.999> this<00:12:25.240> slide<00:12:25.480> here<00:12:25.779> we<00:12:26.050> have<00:12:26.879> organizations 00:12:27.869 --> 00:12:27.879 align:start position:0% on this slide here we have organizations 00:12:27.879 --> 00:12:30.449 align:start position:0% on this slide here we have organizations that<00:12:28.600> directly<00:12:29.230> contributed<00:12:29.949> to<00:12:30.069> this<00:12:30.189> these 00:12:30.449 --> 00:12:30.459 align:start position:0% that directly contributed to this these 00:12:30.459 --> 00:12:32.850 align:start position:0% that directly contributed to this these specifications<00:12:31.360> I<00:12:31.600> think<00:12:32.470> historically 00:12:32.850 --> 00:12:32.860 align:start position:0% specifications I think historically 00:12:32.860 --> 00:12:34.919 align:start position:0% specifications I think historically there's<00:12:33.459> been<00:12:33.730> sort<00:12:34.089> of<00:12:34.179> a<00:12:34.269> perception<00:12:34.749> with 00:12:34.919 --> 00:12:34.929 align:start position:0% there's been sort of a perception with 00:12:34.929 --> 00:12:36.780 align:start position:0% there's been sort of a perception with the<00:12:35.050> EA<00:12:35.199> that<00:12:35.679> there<00:12:35.829> was<00:12:35.949> you<00:12:36.160> know<00:12:36.249> only<00:12:36.670> a 00:12:36.780 --> 00:12:36.790 align:start position:0% the EA that there was you know only a 00:12:36.790 --> 00:12:38.610 align:start position:0% the EA that there was you know only a few<00:12:36.819> firms<00:12:37.269> contributing<00:12:38.019> to<00:12:38.170> it<00:12:38.319> but<00:12:38.410> I<00:12:38.470> think 00:12:38.610 --> 00:12:38.620 align:start position:0% few firms contributing to it but I think 00:12:38.620 --> 00:12:40.110 align:start position:0% few firms contributing to it but I think what's<00:12:38.769> really<00:12:38.800> nice<00:12:39.189> about<00:12:39.249> this<00:12:39.759> is<00:12:39.970> it 00:12:40.110 --> 00:12:40.120 align:start position:0% what's really nice about this is it 00:12:40.120 --> 00:12:41.879 align:start position:0% what's really nice about this is it shows<00:12:40.300> that<00:12:40.360> you<00:12:41.230> know<00:12:41.319> you've<00:12:41.439> got<00:12:41.589> a<00:12:41.620> fairly 00:12:41.879 --> 00:12:41.889 align:start position:0% shows that you know you've got a fairly 00:12:41.889 --> 00:12:43.379 align:start position:0% shows that you know you've got a fairly good<00:12:42.040> cross-section<00:12:42.490> of<00:12:42.999> different 00:12:43.379 --> 00:12:43.389 align:start position:0% good cross-section of different 00:12:43.389 --> 00:12:45.660 align:start position:0% good cross-section of different companies<00:12:43.809> getting<00:12:44.110> involved<00:12:44.679> in<00:12:45.189> the<00:12:45.370> actual 00:12:45.660 --> 00:12:45.670 align:start position:0% companies getting involved in the actual 00:12:45.670 --> 00:12:47.309 align:start position:0% companies getting involved in the actual specification<00:12:46.059> work<00:12:46.689> which<00:12:46.929> i<00:12:47.049> think<00:12:47.110> is 00:12:47.309 --> 00:12:47.319 align:start position:0% specification work which i think is 00:12:47.319 --> 00:12:53.160 align:start position:0% specification work which i think is really<00:12:47.529> cool<00:12:47.829> to<00:12:48.040> see 00:12:53.160 --> 00:12:53.170 align:start position:0% 00:12:53.170 --> 00:12:56.729 align:start position:0% and<00:12:53.859> so<00:12:54.639> this<00:12:55.209> week<00:12:55.480> the<00:12:55.959> two<00:12:56.139> specs<00:12:56.470> that<00:12:56.589> we 00:12:56.729 --> 00:12:56.739 align:start position:0% and so this week the two specs that we 00:12:56.739 --> 00:12:58.410 align:start position:0% and so this week the two specs that we released<00:12:57.100> one<00:12:57.339> of<00:12:57.459> them<00:12:57.609> was<00:12:57.819> the<00:12:58.059> client 00:12:58.410 --> 00:12:58.420 align:start position:0% released one of them was the client 00:12:58.420 --> 00:13:01.859 align:start position:0% released one of them was the client specification<00:12:59.230> v2<00:12:59.920> and<00:13:00.220> so<00:13:00.790> we<00:13:01.029> released<00:13:01.329> v1 00:13:01.859 --> 00:13:01.869 align:start position:0% specification v2 and so we released v1 00:13:01.869 --> 00:13:07.379 align:start position:0% specification v2 and so we released v1 to<00:13:02.470> coincide<00:13:02.889> with<00:13:03.629> the<00:13:04.739> consensus<00:13:06.209> coined<00:13:07.209> s 00:13:07.379 --> 00:13:07.389 align:start position:0% to coincide with the consensus coined s 00:13:07.389 --> 00:13:11.159 align:start position:0% to coincide with the consensus coined s conference<00:13:07.869> in<00:13:08.170> May<00:13:08.379> of<00:13:08.499> this<00:13:08.649> year<00:13:09.540> we're<00:13:10.540> now 00:13:11.159 --> 00:13:11.169 align:start position:0% conference in May of this year we're now 00:13:11.169 --> 00:13:14.239 align:start position:0% conference in May of this year we're now on<00:13:11.439> a<00:13:11.470> six<00:13:12.339> month<00:13:12.609> release<00:13:12.910> cycle<00:13:13.389> with<00:13:13.660> the 00:13:14.239 --> 00:13:14.249 align:start position:0% on a six month release cycle with the 00:13:14.249 --> 00:13:17.759 align:start position:0% on a six month release cycle with the specifications<00:13:15.249> whereby<00:13:16.199> every<00:13:17.199> six<00:13:17.410> months 00:13:17.759 --> 00:13:17.769 align:start position:0% specifications whereby every six months 00:13:17.769 --> 00:13:19.439 align:start position:0% specifications whereby every six months that<00:13:17.980> the<00:13:18.129> next<00:13:18.369> version<00:13:18.519> will<00:13:18.850> come<00:13:18.879> out<00:13:19.179> so 00:13:19.439 --> 00:13:19.449 align:start position:0% that the next version will come out so 00:13:19.449 --> 00:13:21.169 align:start position:0% that the next version will come out so we'd<00:13:19.569> envisage<00:13:19.959> the<00:13:20.139> next<00:13:20.379> one<00:13:20.559> will<00:13:20.739> be 00:13:21.169 --> 00:13:21.179 align:start position:0% we'd envisage the next one will be 00:13:21.179 --> 00:13:24.840 align:start position:0% we'd envisage the next one will be likely<00:13:22.179> April<00:13:22.899> next<00:13:23.290> year<00:13:23.549> all<00:13:24.549> of<00:13:24.609> the 00:13:24.840 --> 00:13:24.850 align:start position:0% likely April next year all of the 00:13:24.850 --> 00:13:26.729 align:start position:0% likely April next year all of the development<00:13:25.540> of<00:13:25.600> these<00:13:25.689> specifications<00:13:26.499> now 00:13:26.729 --> 00:13:26.739 align:start position:0% development of these specifications now 00:13:26.739 --> 00:13:28.530 align:start position:0% development of these specifications now is<00:13:26.949> taking<00:13:27.309> place<00:13:27.699> on<00:13:27.910> github<00:13:28.329> we're 00:13:28.530 --> 00:13:28.540 align:start position:0% is taking place on github we're 00:13:28.540 --> 00:13:30.150 align:start position:0% is taking place on github we're following<00:13:28.749> similar<00:13:29.290> sort<00:13:29.499> of<00:13:29.529> processes<00:13:30.129> to 00:13:30.150 --> 00:13:30.160 align:start position:0% following similar sort of processes to 00:13:30.160 --> 00:13:32.809 align:start position:0% following similar sort of processes to how<00:13:30.429> the<00:13:30.489> w3c<00:13:31.299> specs<00:13:31.660> are<00:13:31.839> being<00:13:31.989> developed<00:13:32.259> so 00:13:32.809 --> 00:13:32.819 align:start position:0% how the w3c specs are being developed so 00:13:32.819 --> 00:13:35.729 align:start position:0% how the w3c specs are being developed so people<00:13:33.819> members<00:13:34.419> of<00:13:34.569> submitting<00:13:35.079> issues<00:13:35.470> and 00:13:35.729 --> 00:13:35.739 align:start position:0% people members of submitting issues and 00:13:35.739 --> 00:13:37.349 align:start position:0% people members of submitting issues and pull<00:13:35.949> requests<00:13:36.429> with<00:13:36.579> changes<00:13:37.059> they<00:13:37.209> get 00:13:37.349 --> 00:13:37.359 align:start position:0% pull requests with changes they get 00:13:37.359 --> 00:13:40.849 align:start position:0% pull requests with changes they get approved<00:13:37.749> by<00:13:38.679> just<00:13:39.549> different<00:13:40.179> members 00:13:40.849 --> 00:13:40.859 align:start position:0% approved by just different members 00:13:40.859 --> 00:13:42.809 align:start position:0% approved by just different members there's<00:13:41.859> actually<00:13:42.220> going<00:13:42.339> to<00:13:42.399> be<00:13:42.489> a<00:13:42.549> lot<00:13:42.699> more 00:13:42.809 --> 00:13:42.819 align:start position:0% there's actually going to be a lot more 00:13:42.819 --> 00:13:44.819 align:start position:0% there's actually going to be a lot more transparency<00:13:43.480> as<00:13:43.720> well<00:13:43.749> very<00:13:44.139> soon<00:13:44.470> in<00:13:44.709> that 00:13:44.819 --> 00:13:44.829 align:start position:0% transparency as well very soon in that 00:13:44.829 --> 00:13:47.909 align:start position:0% transparency as well very soon in that we're<00:13:44.980> going<00:13:45.129> to<00:13:45.249> be<00:13:45.489> the<00:13:46.419> actual<00:13:47.019> repo<00:13:47.559> is<00:13:47.619> no 00:13:47.909 --> 00:13:47.919 align:start position:0% we're going to be the actual repo is no 00:13:47.919 --> 00:13:49.439 align:start position:0% we're going to be the actual repo is no longer<00:13:48.100> going<00:13:48.309> to<00:13:48.399> be<00:13:48.489> private<00:13:48.730> so<00:13:49.029> people<00:13:49.329> can 00:13:49.439 --> 00:13:49.449 align:start position:0% longer going to be private so people can 00:13:49.449 --> 00:13:51.659 align:start position:0% longer going to be private so people can see<00:13:49.869> exactly<00:13:50.230> what's<00:13:50.559> happening<00:13:50.949> as<00:13:51.369> the 00:13:51.659 --> 00:13:51.669 align:start position:0% see exactly what's happening as the 00:13:51.669 --> 00:13:55.229 align:start position:0% see exactly what's happening as the specifications<00:13:52.569> evolve<00:13:53.730> but<00:13:54.730> in<00:13:54.850> terms<00:13:55.059> of 00:13:55.229 --> 00:13:55.239 align:start position:0% specifications evolve but in terms of 00:13:55.239 --> 00:13:57.269 align:start position:0% specifications evolve but in terms of the<00:13:55.329> highlights<00:13:55.749> just<00:13:56.019> wanted<00:13:56.259> to<00:13:56.470> bring<00:13:57.100> your 00:13:57.269 --> 00:13:57.279 align:start position:0% the highlights just wanted to bring your 00:13:57.279 --> 00:13:59.879 align:start position:0% the highlights just wanted to bring your attention<00:13:57.339> to<00:13:57.850> a<00:13:57.879> couple<00:13:58.269> of<00:13:58.329> them<00:13:58.829> one<00:13:59.829> of 00:13:59.879 --> 00:13:59.889 align:start position:0% attention to a couple of them one of 00:13:59.889 --> 00:14:02.759 align:start position:0% attention to a couple of them one of them<00:14:00.129> is<00:14:00.249> that<00:14:00.339> we've<00:14:00.489> now<00:14:00.660> in<00:14:01.660> in<00:14:01.989> the<00:14:02.139> EA<00:14:02.259> spec 00:14:02.759 --> 00:14:02.769 align:start position:0% them is that we've now in in the EA spec 00:14:02.769 --> 00:14:06.600 align:start position:0% them is that we've now in in the EA spec we<00:14:02.949> have<00:14:03.160> a<00:14:03.189> core<00:14:03.519> set<00:14:03.549> of<00:14:03.759> JSON<00:14:04.059> RPC<00:14:04.299> a<00:14:05.610> API 00:14:06.600 --> 00:14:06.610 align:start position:0% we have a core set of JSON RPC a API 00:14:06.610 --> 00:14:08.999 align:start position:0% we have a core set of JSON RPC a API implementations<00:14:07.569> from<00:14:07.869> aetherium<00:14:08.679> that<00:14:08.919> you 00:14:08.999 --> 00:14:09.009 align:start position:0% implementations from aetherium that you 00:14:09.009 --> 00:14:11.220 align:start position:0% implementations from aetherium that you need<00:14:09.189> to<00:14:09.369> implement<00:14:09.669> to<00:14:10.119> have<00:14:10.269> an<00:14:10.749> enterprise 00:14:11.220 --> 00:14:11.230 align:start position:0% need to implement to have an enterprise 00:14:11.230 --> 00:14:13.199 align:start position:0% need to implement to have an enterprise aetherium<00:14:11.739> clients<00:14:12.160> we've<00:14:12.309> also<00:14:12.489> added<00:14:13.029> some 00:14:13.199 --> 00:14:13.209 align:start position:0% aetherium clients we've also added some 00:14:13.209 --> 00:14:14.100 align:start position:0% aetherium clients we've also added some additional<00:14:13.660> ones 00:14:14.100 --> 00:14:14.110 align:start position:0% additional ones 00:14:14.110 --> 00:14:16.979 align:start position:0% additional ones this.e<00:14:14.980> which<00:14:15.489> we<00:14:15.639> use<00:14:15.790> in<00:14:15.939> EE<00:14:16.089> a<00:14:16.209> namespace 00:14:16.979 --> 00:14:16.989 align:start position:0% this.e which we use in EE a namespace 00:14:16.989 --> 00:14:18.960 align:start position:0% this.e which we use in EE a namespace and<00:14:17.470> this<00:14:17.559> is<00:14:17.709> mainly<00:14:17.919> right<00:14:18.339> now<00:14:18.489> functions 00:14:18.960 --> 00:14:18.970 align:start position:0% and this is mainly right now functions 00:14:18.970 --> 00:14:21.539 align:start position:0% and this is mainly right now functions around<00:14:19.689> supporting<00:14:20.379> the<00:14:20.529> privacy<00:14:21.160> models 00:14:21.539 --> 00:14:21.549 align:start position:0% around supporting the privacy models 00:14:21.549 --> 00:14:24.960 align:start position:0% around supporting the privacy models that<00:14:21.790> are<00:14:21.910> specified<00:14:22.149> by<00:14:23.139> the<00:14:23.619> EA<00:14:24.009> so<00:14:24.549> these 00:14:24.960 --> 00:14:24.970 align:start position:0% that are specified by the EA so these 00:14:24.970 --> 00:14:27.359 align:start position:0% that are specified by the EA so these are<00:14:25.209> your<00:14:25.689> your<00:14:26.079> quorum<00:14:26.499> type<00:14:26.739> approach<00:14:27.160> to 00:14:27.359 --> 00:14:27.369 align:start position:0% are your your quorum type approach to 00:14:27.369 --> 00:14:29.489 align:start position:0% are your your quorum type approach to privacy<00:14:27.669> where<00:14:28.059> you<00:14:28.179> have<00:14:28.389> a<00:14:28.720> you<00:14:29.470> know 00:14:29.489 --> 00:14:29.499 align:start position:0% privacy where you have a you know 00:14:29.499 --> 00:14:32.309 align:start position:0% privacy where you have a you know transactions<00:14:30.189> being<00:14:30.459> stored<00:14:30.819> off<00:14:31.509> off<00:14:31.959> chain 00:14:32.309 --> 00:14:32.319 align:start position:0% transactions being stored off off chain 00:14:32.319 --> 00:14:33.989 align:start position:0% transactions being stored off off chain and<00:14:32.619> but<00:14:33.040> also<00:14:33.160> there's<00:14:33.489> some<00:14:33.610> on<00:14:33.730> chain 00:14:33.989 --> 00:14:33.999 align:start position:0% and but also there's some on chain 00:14:33.999 --> 00:14:35.850 align:start position:0% and but also there's some on chain techniques<00:14:34.480> as<00:14:34.689> well<00:14:34.839> that<00:14:35.439> the<00:14:35.529> likes<00:14:35.709> of 00:14:35.850 --> 00:14:35.860 align:start position:0% techniques as well that the likes of 00:14:35.860 --> 00:14:37.889 align:start position:0% techniques as well that the likes of Claire<00:14:36.069> Maddox<00:14:36.249> have<00:14:36.579> been<00:14:36.759> promoting<00:14:37.660> with 00:14:37.889 --> 00:14:37.899 align:start position:0% Claire Maddox have been promoting with 00:14:37.899 --> 00:14:41.220 align:start position:0% Claire Maddox have been promoting with their<00:14:38.319> actual<00:14:38.709> client<00:14:39.100> implementation<00:14:40.230> we 00:14:41.220 --> 00:14:41.230 align:start position:0% their actual client implementation we 00:14:41.230 --> 00:14:44.579 align:start position:0% their actual client implementation we also<00:14:41.789> reference<00:14:42.789> the<00:14:43.079> precompile<00:14:44.079> contracts 00:14:44.579 --> 00:14:44.589 align:start position:0% also reference the precompile contracts 00:14:44.589 --> 00:14:47.029 align:start position:0% also reference the precompile contracts as<00:14:44.769> well<00:14:44.949> so<00:14:45.249> we<00:14:45.369> list<00:14:45.549> the<00:14:46.209> eighth's 00:14:47.029 --> 00:14:47.039 align:start position:0% as well so we list the eighth's 00:14:47.039 --> 00:14:49.650 align:start position:0% as well so we list the eighth's precompile<00:14:48.039> contracts<00:14:48.669> that<00:14:48.819> are<00:14:48.999> specified 00:14:49.650 --> 00:14:49.660 align:start position:0% precompile contracts that are specified 00:14:49.660 --> 00:14:51.210 align:start position:0% precompile contracts that are specified in<00:14:49.899> the<00:14:50.019> yellow<00:14:50.230> paper<00:14:50.499> they're<00:14:50.919> all<00:14:51.039> now 00:14:51.210 --> 00:14:51.220 align:start position:0% in the yellow paper they're all now 00:14:51.220 --> 00:14:53.279 align:start position:0% in the yellow paper they're all now referenced<00:14:52.149> in<00:14:52.269> the<00:14:52.389> EA<00:14:52.509> spec<00:14:52.899> as<00:14:53.079> being 00:14:53.279 --> 00:14:53.289 align:start position:0% referenced in the EA spec as being 00:14:53.289 --> 00:14:55.499 align:start position:0% referenced in the EA spec as being mandatory<00:14:53.799> requirements<00:14:54.429> and<00:14:54.879> the<00:14:55.359> other 00:14:55.499 --> 00:14:55.509 align:start position:0% mandatory requirements and the other 00:14:55.509 --> 00:14:57.710 align:start position:0% mandatory requirements and the other thing<00:14:55.779> as<00:14:55.929> well<00:14:56.109> is<00:14:56.169> that<00:14:56.470> we've<00:14:56.589> actually 00:14:57.710 --> 00:14:57.720 align:start position:0% thing as well is that we've actually 00:14:57.720 --> 00:15:01.559 align:start position:0% thing as well is that we've actually provided<00:14:58.720> a<00:14:58.929> an<00:14:59.799> API<00:15:00.160> and<00:15:00.669> for<00:15:01.179> network 00:15:01.559 --> 00:15:01.569 align:start position:0% provided a an API and for network 00:15:01.569 --> 00:15:03.150 align:start position:0% provided a an API and for network permissioning<00:15:02.230> the<00:15:02.619> you<00:15:02.949> know<00:15:03.039> the 00:15:03.150 --> 00:15:03.160 align:start position:0% permissioning the you know the 00:15:03.160 --> 00:15:04.889 align:start position:0% permissioning the you know the government<00:15:03.579> governance<00:15:04.119> of<00:15:04.360> private 00:15:04.889 --> 00:15:04.899 align:start position:0% government governance of private 00:15:04.899 --> 00:15:06.660 align:start position:0% government governance of private permission<00:15:05.289> networks<00:15:05.679> is<00:15:05.949> obviously<00:15:06.339> a 00:15:06.660 --> 00:15:06.670 align:start position:0% permission networks is obviously a 00:15:06.670 --> 00:15:08.850 align:start position:0% permission networks is obviously a you<00:15:06.910> know<00:15:07.000> it's<00:15:07.660> a<00:15:07.750> challenge<00:15:07.960> and<00:15:08.380> so<00:15:08.650> we've 00:15:08.850 --> 00:15:08.860 align:start position:0% you know it's a challenge and so we've 00:15:08.860 --> 00:15:11.370 align:start position:0% you know it's a challenge and so we've we've<00:15:09.370> now<00:15:09.610> included<00:15:09.970> in<00:15:10.360> our<00:15:10.420> specification 00:15:11.370 --> 00:15:11.380 align:start position:0% we've now included in our specification 00:15:11.380 --> 00:15:13.980 align:start position:0% we've now included in our specification an<00:15:11.650> API<00:15:11.980> for<00:15:12.070> this<00:15:12.550> based<00:15:12.790> on<00:15:13.000> work<00:15:13.210> that<00:15:13.540> some 00:15:13.980 --> 00:15:13.990 align:start position:0% an API for this based on work that some 00:15:13.990 --> 00:15:16.500 align:start position:0% an API for this based on work that some members<00:15:14.320> have<00:15:14.440> contributed<00:15:15.090> so<00:15:16.090> it's<00:15:16.240> you 00:15:16.500 --> 00:15:16.510 align:start position:0% members have contributed so it's you 00:15:16.510 --> 00:15:18.330 align:start position:0% members have contributed so it's you know<00:15:16.570> for<00:15:16.780> us<00:15:16.870> it's<00:15:17.110> I<00:15:17.320> think<00:15:17.380> it's<00:15:17.860> you<00:15:18.220> know<00:15:18.280> a 00:15:18.330 --> 00:15:18.340 align:start position:0% know for us it's I think it's you know a 00:15:18.340 --> 00:15:21.120 align:start position:0% know for us it's I think it's you know a good<00:15:18.970> move<00:15:19.180> forward<00:15:19.600> in<00:15:19.750> that<00:15:19.950> right<00:15:20.950> now 00:15:21.120 --> 00:15:21.130 align:start position:0% good move forward in that right now 00:15:21.130 --> 00:15:22.250 align:start position:0% good move forward in that right now there's<00:15:21.400> not<00:15:21.490> really<00:15:21.640> any<00:15:21.940> any 00:15:22.250 --> 00:15:22.260 align:start position:0% there's not really any any 00:15:22.260 --> 00:15:24.740 align:start position:0% there's not really any any standardization<00:15:23.260> around<00:15:23.350> this<00:15:23.680> just<00:15:24.070> yet<00:15:24.310> and 00:15:24.740 --> 00:15:24.750 align:start position:0% standardization around this just yet and 00:15:24.750 --> 00:15:27.000 align:start position:0% standardization around this just yet and we've<00:15:25.750> also<00:15:25.930> added<00:15:26.080> in<00:15:26.380> a<00:15:26.500> security 00:15:27.000 --> 00:15:27.010 align:start position:0% we've also added in a security 00:15:27.010 --> 00:15:28.740 align:start position:0% we've also added in a security considerations<00:15:27.760> section<00:15:28.240> but<00:15:28.360> that's<00:15:28.510> more 00:15:28.740 --> 00:15:28.750 align:start position:0% considerations section but that's more 00:15:28.750 --> 00:15:31.530 align:start position:0% considerations section but that's more based<00:15:29.110> on<00:15:29.350> just<00:15:30.100> best<00:15:30.340> practices<00:15:30.940> around<00:15:31.090> you 00:15:31.530 --> 00:15:31.540 align:start position:0% based on just best practices around you 00:15:31.540 --> 00:15:35.270 align:start position:0% based on just best practices around you know<00:15:31.630> security<00:15:32.200> for<00:15:32.530> these<00:15:32.680> mission<00:15:33.280> Jane's 00:15:35.270 --> 00:15:35.280 align:start position:0% know security for these mission Jane's 00:15:35.280 --> 00:15:39.360 align:start position:0% know security for these mission Jane's the<00:15:36.280> other<00:15:36.550> big<00:15:37.830> specification<00:15:38.830> release<00:15:39.100> was 00:15:39.360 --> 00:15:39.370 align:start position:0% the other big specification release was 00:15:39.370 --> 00:15:42.030 align:start position:0% the other big specification release was the<00:15:39.400> off<00:15:39.760> chain<00:15:40.060> trusted<00:15:40.600> compute<00:15:41.500> spec<00:15:41.800> and 00:15:42.030 --> 00:15:42.040 align:start position:0% the off chain trusted compute spec and 00:15:42.040 --> 00:15:44.700 align:start position:0% the off chain trusted compute spec and so<00:15:42.460> this<00:15:42.610> was<00:15:42.820> mainly<00:15:43.240> driven<00:15:43.450> by<00:15:43.720> Intel<00:15:44.410> and<00:15:44.650> I 00:15:44.700 --> 00:15:44.710 align:start position:0% so this was mainly driven by Intel and I 00:15:44.710 --> 00:15:46.920 align:start position:0% so this was mainly driven by Intel and I exact<00:15:45.100> but<00:15:45.280> a<00:15:45.310> number<00:15:45.520> of<00:15:45.670> different<00:15:46.180> you<00:15:46.840> know 00:15:46.920 --> 00:15:46.930 align:start position:0% exact but a number of different you know 00:15:46.930 --> 00:15:49.440 align:start position:0% exact but a number of different you know contributors<00:15:47.560> did<00:15:47.740> get<00:15:47.920> involved<00:15:48.490> include 00:15:49.440 --> 00:15:49.450 align:start position:0% contributors did get involved include 00:15:49.450 --> 00:15:50.970 align:start position:0% contributors did get involved include including<00:15:49.780> Oracle<00:15:50.260> ice<00:15:50.350> and<00:15:50.620> I<00:15:50.800> think 00:15:50.970 --> 00:15:50.980 align:start position:0% including Oracle ice and I think 00:15:50.980 --> 00:15:53.850 align:start position:0% including Oracle ice and I think consensus<00:15:51.460> did<00:15:51.640> some<00:15:51.850> stuff<00:15:52.150> but<00:15:52.840> the<00:15:53.620> point 00:15:53.850 --> 00:15:53.860 align:start position:0% consensus did some stuff but the point 00:15:53.860 --> 00:15:57.570 align:start position:0% consensus did some stuff but the point is<00:15:54.100> is<00:15:54.310> it<00:15:54.490> provides<00:15:55.450> a<00:15:55.810> JSON<00:15:56.560> RPC<00:15:56.710> based<00:15:57.310> API 00:15:57.570 --> 00:15:57.580 align:start position:0% is is it provides a JSON RPC based API 00:15:57.580 --> 00:16:01.010 align:start position:0% is is it provides a JSON RPC based API for<00:15:57.910> vendors<00:15:58.720> whereby<00:15:59.500> they<00:15:59.890> can<00:15:59.950> achieve 00:16:01.010 --> 00:16:01.020 align:start position:0% for vendors whereby they can achieve 00:16:01.020 --> 00:16:04.380 align:start position:0% for vendors whereby they can achieve well<00:16:02.020> really<00:16:02.380> really<00:16:03.120> achieve<00:16:04.120> a<00:16:04.210> few 00:16:04.380 --> 00:16:04.390 align:start position:0% well really really achieve a few 00:16:04.390 --> 00:16:06.090 align:start position:0% well really really achieve a few different<00:16:04.720> things<00:16:04.900> there<00:16:05.170> one<00:16:05.350> is<00:16:05.500> use<00:16:05.740> it<00:16:05.920> for 00:16:06.090 --> 00:16:06.100 align:start position:0% different things there one is use it for 00:16:06.100 --> 00:16:08.640 align:start position:0% different things there one is use it for Oracle<00:16:06.520> type<00:16:06.730> services<00:16:07.330> another<00:16:08.110> where<00:16:08.350> they 00:16:08.640 --> 00:16:08.650 align:start position:0% Oracle type services another where they 00:16:08.650 --> 00:16:11.010 align:start position:0% Oracle type services another where they just<00:16:08.830> want<00:16:09.070> to<00:16:09.220> use<00:16:09.520> a<00:16:09.550> secure<00:16:10.180> Enclave<00:16:10.420> to<00:16:10.690> do 00:16:11.010 --> 00:16:11.020 align:start position:0% just want to use a secure Enclave to do 00:16:11.020 --> 00:16:12.900 align:start position:0% just want to use a secure Enclave to do some<00:16:11.320> sort<00:16:11.560> of<00:16:11.590> computation<00:16:12.400> or<00:16:12.610> it<00:16:12.730> could 00:16:12.900 --> 00:16:12.910 align:start position:0% some sort of computation or it could 00:16:12.910 --> 00:16:15.090 align:start position:0% some sort of computation or it could just<00:16:13.030> be<00:16:13.270> doing<00:16:13.810> some<00:16:14.140> sort<00:16:14.260> of<00:16:14.380> computations 00:16:15.090 --> 00:16:15.100 align:start position:0% just be doing some sort of computations 00:16:15.100 --> 00:16:18.990 align:start position:0% just be doing some sort of computations off<00:16:15.670> chain<00:16:16.090> in<00:16:16.360> a<00:16:17.280> again<00:16:18.280> you<00:16:18.610> know<00:16:18.820> as<00:16:18.970> a 00:16:18.990 --> 00:16:19.000 align:start position:0% off chain in a again you know as a 00:16:19.000 --> 00:16:20.640 align:start position:0% off chain in a again you know as a secure<00:16:19.570> environment<00:16:19.900> but<00:16:20.380> stuff<00:16:20.620> that 00:16:20.640 --> 00:16:20.650 align:start position:0% secure environment but stuff that 00:16:20.650 --> 00:16:23.460 align:start position:0% secure environment but stuff that wouldn't<00:16:21.040> actually<00:16:21.310> be<00:16:21.990> easy<00:16:22.990> to<00:16:23.320> do 00:16:23.460 --> 00:16:23.470 align:start position:0% wouldn't actually be easy to do 00:16:23.470 --> 00:16:25.020 align:start position:0% wouldn't actually be easy to do unchanged<00:16:24.070> you<00:16:24.220> to<00:16:24.460> the<00:16:24.550> performance 00:16:25.020 --> 00:16:25.030 align:start position:0% unchanged you to the performance 00:16:25.030 --> 00:16:27.660 align:start position:0% unchanged you to the performance requirements<00:16:25.720> so<00:16:26.410> it's<00:16:26.560> it's<00:16:26.920> it's<00:16:27.160> you<00:16:27.640> know 00:16:27.660 --> 00:16:27.670 align:start position:0% requirements so it's it's it's you know 00:16:27.670 --> 00:16:29.430 align:start position:0% requirements so it's it's it's you know for<00:16:27.910> us<00:16:28.210> we're<00:16:28.420> really<00:16:28.600> happy<00:16:28.810> that<00:16:28.960> it's<00:16:29.230> made 00:16:29.430 --> 00:16:29.440 align:start position:0% for us we're really happy that it's made 00:16:29.440 --> 00:16:31.530 align:start position:0% for us we're really happy that it's made it<00:16:29.590> out<00:16:29.740> there<00:16:29.980> because<00:16:30.160> you<00:16:30.670> know<00:16:30.760> this<00:16:31.270> it's 00:16:31.530 --> 00:16:31.540 align:start position:0% it out there because you know this it's 00:16:31.540 --> 00:16:33.150 align:start position:0% it out there because you know this it's a<00:16:31.630> second<00:16:31.990> spec<00:16:32.290> we<00:16:32.500> envisage<00:16:32.770> that<00:16:32.920> there 00:16:33.150 --> 00:16:33.160 align:start position:0% a second spec we envisage that there 00:16:33.160 --> 00:16:35.100 align:start position:0% a second spec we envisage that there will<00:16:33.280> be<00:16:33.310> multiple<00:16:33.580> specs<00:16:34.120> appearing<00:16:34.990> over 00:16:35.100 --> 00:16:35.110 align:start position:0% will be multiple specs appearing over 00:16:35.110 --> 00:16:39.020 align:start position:0% will be multiple specs appearing over time<00:16:35.640> but<00:16:36.640> you<00:16:37.270> know<00:16:37.330> especially<00:16:37.990> given<00:16:38.500> that 00:16:39.020 --> 00:16:39.030 align:start position:0% time but you know especially given that 00:16:39.030 --> 00:16:42.540 align:start position:0% time but you know especially given that you<00:16:40.030> know<00:16:40.090> it's<00:16:40.690> ready<00:16:40.960> in<00:16:41.110> time<00:16:41.260> for<00:16:41.550> this 00:16:42.540 --> 00:16:42.550 align:start position:0% you know it's ready in time for this 00:16:42.550 --> 00:16:44.400 align:start position:0% you know it's ready in time for this conference<00:16:43.000> as<00:16:43.210> well<00:16:43.360> was<00:16:43.540> you<00:16:43.960> know<00:16:44.020> happy<00:16:44.290> to 00:16:44.400 --> 00:16:44.410 align:start position:0% conference as well was you know happy to 00:16:44.410 --> 00:16:45.810 align:start position:0% conference as well was you know happy to have<00:16:44.530> it<00:16:44.560> out<00:16:44.800> there<00:16:45.010> and<00:16:45.190> I'm<00:16:45.400> really<00:16:45.640> keen 00:16:45.810 --> 00:16:45.820 align:start position:0% have it out there and I'm really keen 00:16:45.820 --> 00:16:47.370 align:start position:0% have it out there and I'm really keen for<00:16:45.850> people<00:16:46.270> to<00:16:46.390> take<00:16:46.660> a<00:16:46.690> look<00:16:46.990> and<00:16:47.110> start 00:16:47.370 --> 00:16:47.380 align:start position:0% for people to take a look and start 00:16:47.380 --> 00:16:49.950 align:start position:0% for people to take a look and start feeding<00:16:47.620> back<00:16:47.890> into<00:16:48.220> it<00:16:48.370> and<00:16:49.030> so<00:16:49.240> that<00:16:49.270> was<00:16:49.750> all 00:16:49.950 --> 00:16:49.960 align:start position:0% feeding back into it and so that was all 00:16:49.960 --> 00:16:51.360 align:start position:0% feeding back into it and so that was all I<00:16:49.990> was<00:16:50.170> going<00:16:50.350> to<00:16:50.410> say<00:16:50.560> here<00:16:50.800> and<00:16:50.980> I'll<00:16:51.100> pass 00:16:51.360 --> 00:16:51.370 align:start position:0% I was going to say here and I'll pass 00:16:51.370 --> 00:16:52.740 align:start position:0% I was going to say here and I'll pass back<00:16:51.640> to<00:16:51.670> Ron's<00:16:51.970> talk<00:16:52.240> about<00:16:52.480> the<00:16:52.570> road<00:16:52.720> map 00:16:52.740 --> 00:16:52.750 align:start position:0% back to Ron's talk about the road map 00:16:52.750 --> 00:16:58.110 align:start position:0% back to Ron's talk about the road map thank<00:16:53.170> you<00:16:54.870> so<00:16:55.870> we<00:16:56.200> we<00:16:57.070> have<00:16:57.310> a<00:16:57.340> timetable<00:16:57.730> for 00:16:58.110 --> 00:16:58.120 align:start position:0% thank you so we we have a timetable for 00:16:58.120 --> 00:17:01.410 align:start position:0% thank you so we we have a timetable for road<00:16:58.450> maps<00:16:58.690> and<00:16:59.050> we<00:16:59.110> try<00:16:59.350> to<00:16:59.410> tie<00:16:59.650> it<00:17:00.130> to<00:17:00.420> events 00:17:01.410 --> 00:17:01.420 align:start position:0% road maps and we try to tie it to events 00:17:01.420 --> 00:17:03.660 align:start position:0% road maps and we try to tie it to events so<00:17:01.690> it<00:17:02.080> puts<00:17:02.290> pressure<00:17:02.560> on<00:17:02.770> the<00:17:02.950> folks<00:17:03.280> doing 00:17:03.660 --> 00:17:03.670 align:start position:0% so it puts pressure on the folks doing 00:17:03.670 --> 00:17:09.120 align:start position:0% so it puts pressure on the folks doing work<00:17:03.910> and<00:17:04.600> so<00:17:05.470> that<00:17:06.570> helps<00:17:07.570> but<00:17:07.770> so<00:17:08.770> what<00:17:08.950> we 00:17:09.120 --> 00:17:09.130 align:start position:0% work and so that helps but so what we 00:17:09.130 --> 00:17:11.460 align:start position:0% work and so that helps but so what we our<00:17:09.490> plan<00:17:09.850> is<00:17:10.060> to<00:17:10.090> have<00:17:10.390> a<00:17:10.450> six-month<00:17:11.110> as 00:17:11.460 --> 00:17:11.470 align:start position:0% our plan is to have a six-month as 00:17:11.470 --> 00:17:15.540 align:start position:0% our plan is to have a six-month as Connor<00:17:12.160> said<00:17:12.490> a<00:17:12.640> six-month<00:17:13.120> cadence<00:17:13.660> so<00:17:14.550> we're 00:17:15.540 --> 00:17:15.550 align:start position:0% Connor said a six-month cadence so we're 00:17:15.550 --> 00:17:18.120 align:start position:0% Connor said a six-month cadence so we're an<00:17:15.700> open<00:17:15.820> door<00:17:16.210> anyone<00:17:16.750> who<00:17:17.140> wants<00:17:17.740> to<00:17:17.770> be 00:17:18.120 --> 00:17:18.130 align:start position:0% an open door anyone who wants to be 00:17:18.130 --> 00:17:19.350 align:start position:0% an open door anyone who wants to be involved<00:17:18.430> in<00:17:18.730> yeah 00:17:19.350 --> 00:17:19.360 align:start position:0% involved in yeah 00:17:19.360 --> 00:17:21.929 align:start position:0% involved in yeah can<00:17:19.929> be<00:17:20.049> a<00:17:20.079> member<00:17:20.380> and<00:17:20.709> just<00:17:21.610> to<00:17:21.699> share<00:17:21.880> with 00:17:21.929 --> 00:17:21.939 align:start position:0% can be a member and just to share with 00:17:21.939 --> 00:17:25.319 align:start position:0% can be a member and just to share with you<00:17:22.240> so<00:17:22.449> you<00:17:22.539> know<00:17:22.720> it's<00:17:23.459> $3,000<00:17:24.459> for<00:17:24.760> a<00:17:24.789> member 00:17:25.319 --> 00:17:25.329 align:start position:0% you so you know it's $3,000 for a member 00:17:25.329 --> 00:17:27.539 align:start position:0% you so you know it's $3,000 for a member with<00:17:25.720> a<00:17:25.990> company<00:17:26.620> that<00:17:26.649> has<00:17:26.980> 50<00:17:27.399> or<00:17:27.519> less 00:17:27.539 --> 00:17:27.549 align:start position:0% with a company that has 50 or less 00:17:27.549 --> 00:17:30.360 align:start position:0% with a company that has 50 or less employees<00:17:28.679> so<00:17:29.679> we<00:17:29.710> try<00:17:29.980> to<00:17:30.039> make<00:17:30.220> it 00:17:30.360 --> 00:17:30.370 align:start position:0% employees so we try to make it 00:17:30.370 --> 00:17:33.210 align:start position:0% employees so we try to make it affordable<00:17:30.940> we're<00:17:31.510> a<00:17:31.539> non-profit<00:17:31.809> so<00:17:32.559> the 00:17:33.210 --> 00:17:33.220 align:start position:0% affordable we're a non-profit so the 00:17:33.220 --> 00:17:35.190 align:start position:0% affordable we're a non-profit so the money<00:17:33.700> that<00:17:33.909> comes<00:17:34.120> in<00:17:34.419> just<00:17:34.570> pays<00:17:34.840> for<00:17:35.110> the 00:17:35.190 --> 00:17:35.200 align:start position:0% money that comes in just pays for the 00:17:35.200 --> 00:17:37.350 align:start position:0% money that comes in just pays for the work<00:17:35.380> that<00:17:35.620> we<00:17:35.740> do<00:17:35.980> trying<00:17:36.730> to<00:17:36.789> support<00:17:37.179> the 00:17:37.350 --> 00:17:37.360 align:start position:0% work that we do trying to support the 00:17:37.360 --> 00:17:39.570 align:start position:0% work that we do trying to support the activities<00:17:37.929> to<00:17:38.169> get<00:17:38.380> get<00:17:38.919> the<00:17:39.039> spec<00:17:39.309> done 00:17:39.570 --> 00:17:39.580 align:start position:0% activities to get get the spec done 00:17:39.580 --> 00:17:41.070 align:start position:0% activities to get get the spec done we're<00:17:39.850> not<00:17:39.880> not<00:17:40.360> it's<00:17:40.750> we're<00:17:40.929> not<00:17:41.049> a 00:17:41.070 --> 00:17:41.080 align:start position:0% we're not not it's we're not a 00:17:41.080 --> 00:17:42.990 align:start position:0% we're not not it's we're not a profit-making<00:17:41.679> venture<00:17:41.890> and<00:17:42.460> we<00:17:42.549> don't<00:17:42.760> make 00:17:42.990 --> 00:17:43.000 align:start position:0% profit-making venture and we don't make 00:17:43.000 --> 00:17:45.600 align:start position:0% profit-making venture and we don't make a<00:17:43.059> lot<00:17:43.179> of<00:17:43.330> money<00:17:43.620> and<00:17:44.620> what<00:17:44.890> we<00:17:45.010> get<00:17:45.220> we<00:17:45.460> get 00:17:45.600 --> 00:17:45.610 align:start position:0% a lot of money and what we get we get 00:17:45.610 --> 00:17:47.730 align:start position:0% a lot of money and what we get we get approved<00:17:45.880> by<00:17:46.029> our<00:17:46.059> board<00:17:46.419> and<00:17:46.720> then<00:17:46.929> we<00:17:47.409> spend 00:17:47.730 --> 00:17:47.740 align:start position:0% approved by our board and then we spend 00:17:47.740 --> 00:17:50.639 align:start position:0% approved by our board and then we spend it<00:17:47.919> on<00:17:48.179> making<00:17:49.179> sure<00:17:49.450> our<00:17:49.480> tests<00:17:50.080> net<00:17:50.260> will<00:17:50.440> get 00:17:50.639 --> 00:17:50.649 align:start position:0% it on making sure our tests net will get 00:17:50.649 --> 00:17:52.649 align:start position:0% it on making sure our tests net will get in<00:17:50.769> place<00:17:51.039> we<00:17:51.399> have<00:17:51.580> a<00:17:51.610> test<00:17:51.909> net<00:17:52.149> we'll<00:17:52.419> try<00:17:52.600> to 00:17:52.649 --> 00:17:52.659 align:start position:0% in place we have a test net we'll try to 00:17:52.659 --> 00:17:56.610 align:start position:0% in place we have a test net we'll try to promote<00:17:53.070> to<00:17:54.070> the<00:17:54.220> whole<00:17:54.429> world<00:17:54.960> the<00:17:55.960> benefits 00:17:56.610 --> 00:17:56.620 align:start position:0% promote to the whole world the benefits 00:17:56.620 --> 00:17:59.399 align:start position:0% promote to the whole world the benefits of<00:17:56.799> blockchain<00:17:57.250> technology<00:17:57.970> so<00:17:58.299> so<00:17:59.019> those<00:17:59.200> are 00:17:59.399 --> 00:17:59.409 align:start position:0% of blockchain technology so so those are 00:17:59.409 --> 00:18:00.840 align:start position:0% of blockchain technology so so those are the<00:17:59.470> things<00:17:59.679> some<00:17:59.919> of<00:18:00.039> the<00:18:00.100> things<00:18:00.279> we<00:18:00.429> do<00:18:00.610> and 00:18:00.840 --> 00:18:00.850 align:start position:0% the things some of the things we do and 00:18:00.850 --> 00:18:04.169 align:start position:0% the things some of the things we do and and<00:18:01.600> again<00:18:01.779> we<00:18:02.110> hire<00:18:02.409> a<00:18:02.440> folks<00:18:02.919> to<00:18:03.220> work<00:18:03.760> on<00:18:04.000> our 00:18:04.169 --> 00:18:04.179 align:start position:0% and again we hire a folks to work on our 00:18:04.179 --> 00:18:07.049 align:start position:0% and again we hire a folks to work on our spec<00:18:04.510> and<00:18:04.840> as<00:18:05.830> far<00:18:06.130> as<00:18:06.190> making<00:18:06.490> sure<00:18:06.639> it 00:18:07.049 --> 00:18:07.059 align:start position:0% spec and as far as making sure it 00:18:07.059 --> 00:18:09.600 align:start position:0% spec and as far as making sure it conforms<00:18:07.419> to<00:18:07.899> the<00:18:08.169> quality<00:18:08.799> and<00:18:08.830> caliber<00:18:09.130> that 00:18:09.600 --> 00:18:09.610 align:start position:0% conforms to the quality and caliber that 00:18:09.610 --> 00:18:12.180 align:start position:0% conforms to the quality and caliber that if<00:18:09.909> we<00:18:10.360> show<00:18:10.389> our<00:18:10.690> respect<00:18:11.080> to<00:18:11.200> a<00:18:11.320> standards 00:18:12.180 --> 00:18:12.190 align:start position:0% if we show our respect to a standards 00:18:12.190 --> 00:18:14.580 align:start position:0% if we show our respect to a standards org<00:18:12.460> and<00:18:12.639> there's<00:18:12.789> they're<00:18:13.690> called<00:18:13.899> sto 00:18:14.580 --> 00:18:14.590 align:start position:0% org and there's they're called sto 00:18:14.590 --> 00:18:21.840 align:start position:0% org and there's they're called sto standards<00:18:15.490> development<00:18:20.100> organs<00:18:21.100> so<00:18:21.549> we<00:18:21.669> can 00:18:21.840 --> 00:18:21.850 align:start position:0% standards development organs so we can 00:18:21.850 --> 00:18:24.299 align:start position:0% standards development organs so we can do<00:18:21.940> marketing<00:18:22.419> so<00:18:23.049> the<00:18:23.529> quality<00:18:23.799> and<00:18:24.130> caliber 00:18:24.299 --> 00:18:24.309 align:start position:0% do marketing so the quality and caliber 00:18:24.309 --> 00:18:27.299 align:start position:0% do marketing so the quality and caliber of<00:18:24.549> our<00:18:24.730> spec<00:18:25.149> has<00:18:25.960> to<00:18:26.169> be<00:18:26.320> top-notch<00:18:26.679> and 00:18:27.299 --> 00:18:27.309 align:start position:0% of our spec has to be top-notch and 00:18:27.309 --> 00:18:30.720 align:start position:0% of our spec has to be top-notch and that's<00:18:27.429> why<00:18:27.610> our<00:18:27.639> spec<00:18:28.330> version<00:18:28.899> is<00:18:29.549> 4.5<00:18:30.549> is 00:18:30.720 --> 00:18:30.730 align:start position:0% that's why our spec version is 4.5 is 00:18:30.730 --> 00:18:33.810 align:start position:0% that's why our spec version is 4.5 is 0.5<00:18:31.360> for<00:18:32.260> the<00:18:32.500> trusted<00:18:32.919> execution<00:18:33.370> because 00:18:33.810 --> 00:18:33.820 align:start position:0% 0.5 for the trusted execution because 00:18:33.820 --> 00:18:35.820 align:start position:0% 0.5 for the trusted execution because it's<00:18:34.000> really<00:18:34.179> our<00:18:34.389> first<00:18:34.630> one<00:18:34.870> out<00:18:35.049> so<00:18:35.679> we're 00:18:35.820 --> 00:18:35.830 align:start position:0% it's really our first one out so we're 00:18:35.830 --> 00:18:38.430 align:start position:0% it's really our first one out so we're not<00:18:35.919> making<00:18:36.309> it<00:18:36.460> a<00:18:36.490> formal<00:18:37.330> spec<00:18:37.659> yet<00:18:37.929> compared 00:18:38.430 --> 00:18:38.440 align:start position:0% not making it a formal spec yet compared 00:18:38.440 --> 00:18:40.049 align:start position:0% not making it a formal spec yet compared to<00:18:38.590> the<00:18:38.769> other<00:18:38.950> work<00:18:39.130> that<00:18:39.159> we're<00:18:39.429> doing<00:18:39.460> so 00:18:40.049 --> 00:18:40.059 align:start position:0% to the other work that we're doing so 00:18:40.059 --> 00:18:43.409 align:start position:0% to the other work that we're doing so every<00:18:40.330> six<00:18:40.539> six<00:18:41.320> months<00:18:41.880> we'll<00:18:42.880> be<00:18:43.029> coming<00:18:43.240> out 00:18:43.409 --> 00:18:43.419 align:start position:0% every six six months we'll be coming out 00:18:43.419 --> 00:18:46.019 align:start position:0% every six six months we'll be coming out with<00:18:43.450> a<00:18:43.600> new<00:18:43.870> one<00:18:44.190> we're<00:18:45.190> done<00:18:45.549> we're<00:18:45.760> trying 00:18:46.019 --> 00:18:46.029 align:start position:0% with a new one we're done we're trying 00:18:46.029 --> 00:18:48.990 align:start position:0% with a new one we're done we're trying to<00:18:46.269> get<00:18:46.720> to<00:18:47.200> the<00:18:47.440> point<00:18:47.679> of<00:18:47.799> you<00:18:48.519> don't<00:18:48.639> see<00:18:48.850> the 00:18:48.990 --> 00:18:49.000 align:start position:0% to get to the point of you don't see the 00:18:49.000 --> 00:18:50.820 align:start position:0% to get to the point of you don't see the test<00:18:49.269> not<00:18:49.450> there<00:18:49.690> because<00:18:50.080> I<00:18:50.110> wasn't<00:18:50.679> sure 00:18:50.820 --> 00:18:50.830 align:start position:0% test not there because I wasn't sure 00:18:50.830 --> 00:18:52.860 align:start position:0% test not there because I wasn't sure that<00:18:50.860> we'll<00:18:51.190> have<00:18:51.429> one<00:18:51.730> until<00:18:52.630> I<00:18:52.690> get 00:18:52.860 --> 00:18:52.870 align:start position:0% that we'll have one until I get 00:18:52.870 --> 00:18:54.870 align:start position:0% that we'll have one until I get commitments<00:18:53.440> from<00:18:53.559> members<00:18:54.010> to<00:18:54.490> say<00:18:54.669> they're 00:18:54.870 --> 00:18:54.880 align:start position:0% commitments from members to say they're 00:18:54.880 --> 00:18:56.610 align:start position:0% commitments from members to say they're gonna<00:18:55.029> do<00:18:55.299> it<00:18:55.510> and<00:18:55.750> now<00:18:55.840> I<00:18:55.870> just<00:18:56.080> got<00:18:56.440> those 00:18:56.610 --> 00:18:56.620 align:start position:0% gonna do it and now I just got those 00:18:56.620 --> 00:18:59.159 align:start position:0% gonna do it and now I just got those commitments<00:18:57.159> here<00:18:57.399> at<00:18:57.580> Def<00:18:57.820> Con<00:18:57.850> so<00:18:58.809> we 00:18:59.159 --> 00:18:59.169 align:start position:0% commitments here at Def Con so we 00:18:59.169 --> 00:19:01.649 align:start position:0% commitments here at Def Con so we absolutely<00:18:59.799> this<00:18:59.889> is<00:18:59.950> this<00:19:00.279> and<00:19:00.549> and<00:19:01.120> in<00:19:01.419> order 00:19:01.649 --> 00:19:01.659 align:start position:0% absolutely this is this and and in order 00:19:01.659 --> 00:19:03.750 align:start position:0% absolutely this is this and and in order to<00:19:01.690> make<00:19:01.840> that<00:19:01.990> happen<00:19:02.139> you<00:19:02.740> need<00:19:03.130> a<00:19:03.190> common 00:19:03.750 --> 00:19:03.760 align:start position:0% to make that happen you need a common 00:19:03.760 --> 00:19:06.720 align:start position:0% to make that happen you need a common consensus<00:19:04.360> mechanism<00:19:05.019> correct<00:19:05.529> so<00:19:06.130> that's 00:19:06.720 --> 00:19:06.730 align:start position:0% consensus mechanism correct so that's 00:19:06.730 --> 00:19:10.080 align:start position:0% consensus mechanism correct so that's what<00:19:06.970> we're<00:19:07.090> working<00:19:07.120> on<00:19:07.570> so<00:19:08.820> anyone<00:19:09.820> who's 00:19:10.080 --> 00:19:10.090 align:start position:0% what we're working on so anyone who's 00:19:10.090 --> 00:19:12.060 align:start position:0% what we're working on so anyone who's interested<00:19:10.630> and<00:19:10.840> and<00:19:11.230> you<00:19:11.590> could<00:19:11.830> have<00:19:12.039> a 00:19:12.060 --> 00:19:12.070 align:start position:0% interested and and you could have a 00:19:12.070 --> 00:19:14.549 align:start position:0% interested and and you could have a reason<00:19:12.639> not<00:19:13.149> everybody's<00:19:13.779> looking<00:19:14.440> at 00:19:14.549 --> 00:19:14.559 align:start position:0% reason not everybody's looking at 00:19:14.559 --> 00:19:16.830 align:start position:0% reason not everybody's looking at enterprise<00:19:14.980> side<00:19:15.279> things<00:19:15.610> but<00:19:15.880> we<00:19:16.419> do<00:19:16.570> want<00:19:16.750> to 00:19:16.830 --> 00:19:16.840 align:start position:0% enterprise side things but we do want to 00:19:16.840 --> 00:19:19.980 align:start position:0% enterprise side things but we do want to scale<00:19:17.139> so<00:19:17.470> our<00:19:18.100> solutions<00:19:18.580> can<00:19:18.909> can<00:19:19.600> support 00:19:19.980 --> 00:19:19.990 align:start position:0% scale so our solutions can can support 00:19:19.990 --> 00:19:22.080 align:start position:0% scale so our solutions can can support all<00:19:20.559> kinds<00:19:20.950> of<00:19:21.010> future<00:19:21.220> aspects<00:19:21.789> of<00:19:21.940> what 00:19:22.080 --> 00:19:22.090 align:start position:0% all kinds of future aspects of what 00:19:22.090 --> 00:19:23.159 align:start position:0% all kinds of future aspects of what maybe<00:19:22.360> some<00:19:22.480> of<00:19:22.720> the<00:19:22.779> things<00:19:22.929> that<00:19:22.990> you're 00:19:23.159 --> 00:19:23.169 align:start position:0% maybe some of the things that you're 00:19:23.169 --> 00:19:26.850 align:start position:0% maybe some of the things that you're working<00:19:23.289> on<00:19:23.590> and<00:19:24.389> and<00:19:25.389> then<00:19:25.600> we'll<00:19:25.779> have<00:19:26.470> so 00:19:26.850 --> 00:19:26.860 align:start position:0% working on and and then we'll have so 00:19:26.860 --> 00:19:29.399 align:start position:0% working on and and then we'll have so we'll<00:19:27.010> be<00:19:27.130> you<00:19:27.250> tire<00:19:27.520> a<00:19:27.549> next<00:19:27.940> one<00:19:28.149> time<00:19:29.110> to 00:19:29.399 --> 00:19:29.409 align:start position:0% we'll be you tire a next one time to 00:19:29.409 --> 00:19:31.740 align:start position:0% we'll be you tire a next one time to like<00:19:29.830> the<00:19:29.950> consensus<00:19:30.520> 2000 00:19:31.740 --> 00:19:31.750 align:start position:0% like the consensus 2000 00:19:31.750 --> 00:19:35.250 align:start position:0% like the consensus 2000 eighteen<00:19:32.350> event<00:19:33.390> timeframe<00:19:34.390> and<00:19:34.600> then<00:19:34.720> by 00:19:35.250 --> 00:19:35.260 align:start position:0% eighteen event timeframe and then by 00:19:35.260 --> 00:19:37.140 align:start position:0% eighteen event timeframe and then by next<00:19:35.320> Def<00:19:35.860> Con<00:19:36.100> we'll<00:19:36.310> have<00:19:36.430> released<00:19:36.880> four 00:19:37.140 --> 00:19:37.150 align:start position:0% next Def Con we'll have released four 00:19:37.150 --> 00:19:38.790 align:start position:0% next Def Con we'll have released four and<00:19:37.420> then<00:19:37.930> our<00:19:38.110> plans<00:19:38.410> to<00:19:38.650> launch 00:19:38.790 --> 00:19:38.800 align:start position:0% and then our plans to launch 00:19:38.800 --> 00:19:40.950 align:start position:0% and then our plans to launch certification<00:19:39.640> you<00:19:40.030> do<00:19:40.180> certification 00:19:40.950 --> 00:19:40.960 align:start position:0% certification you do certification 00:19:40.960 --> 00:19:43.470 align:start position:0% certification you do certification through<00:19:41.170> independent<00:19:42.070> labs<00:19:42.550> so<00:19:43.150> I<00:19:43.180> want<00:19:43.390> to 00:19:43.470 --> 00:19:43.480 align:start position:0% through independent labs so I want to 00:19:43.480 --> 00:19:45.360 align:start position:0% through independent labs so I want to leave<00:19:43.720> it<00:19:43.930> just<00:19:44.080> a<00:19:44.140> couple<00:19:44.290> minutes<00:19:44.560> so<00:19:45.220> we're 00:19:45.360 --> 00:19:45.370 align:start position:0% leave it just a couple minutes so we're 00:19:45.370 --> 00:19:46.950 align:start position:0% leave it just a couple minutes so we're just<00:19:45.400> about<00:19:45.580> done<00:19:45.700> I<00:19:46.150> just<00:19:46.510> shared<00:19:46.690> with<00:19:46.750> you 00:19:46.950 --> 00:19:46.960 align:start position:0% just about done I just shared with you 00:19:46.960 --> 00:19:48.320 align:start position:0% just about done I just shared with you were<00:19:47.050> really<00:19:47.230> committed<00:19:47.680> to<00:19:47.710> social<00:19:48.010> impact 00:19:48.320 --> 00:19:48.330 align:start position:0% were really committed to social impact 00:19:48.330 --> 00:19:50.940 align:start position:0% were really committed to social impact part<00:19:49.330> of<00:19:49.450> the<00:19:49.510> reason<00:19:49.840> why<00:19:49.990> I<00:19:50.020> have<00:19:50.560> this<00:19:50.680> here 00:19:50.940 --> 00:19:50.950 align:start position:0% part of the reason why I have this here 00:19:50.950 --> 00:19:53.010 align:start position:0% part of the reason why I have this here is<00:19:51.070> that<00:19:51.250> we're<00:19:51.970> going<00:19:52.240> to<00:19:52.330> work<00:19:52.480> hard<00:19:52.510> to<00:19:52.870> get 00:19:53.010 --> 00:19:53.020 align:start position:0% is that we're going to work hard to get 00:19:53.020 --> 00:19:54.720 align:start position:0% is that we're going to work hard to get the<00:19:53.170> enterprises<00:19:53.830> to<00:19:54.010> support<00:19:54.490> and<00:19:54.670> they 00:19:54.720 --> 00:19:54.730 align:start position:0% the enterprises to support and they 00:19:54.730 --> 00:19:56.970 align:start position:0% the enterprises to support and they already<00:19:54.850> do<00:19:55.210> I've<00:19:55.840> learned<00:19:56.500> about<00:19:56.650> it<00:19:56.800> through 00:19:56.970 --> 00:19:56.980 align:start position:0% already do I've learned about it through 00:19:56.980 --> 00:20:00.450 align:start position:0% already do I've learned about it through some<00:19:57.760> board<00:19:58.300> members<00:19:58.360> but<00:19:58.900> we<00:19:59.170> we<00:19:59.980> really<00:20:00.280> want 00:20:00.450 --> 00:20:00.460 align:start position:0% some board members but we we really want 00:20:00.460 --> 00:20:03.450 align:start position:0% some board members but we we really want to<00:20:00.520> do<00:20:00.640> a<00:20:00.670> good<00:20:00.850> job<00:20:00.910> to<00:20:01.270> help<00:20:01.770> the<00:20:02.770> south<00:20:03.220> side 00:20:03.450 --> 00:20:03.460 align:start position:0% to do a good job to help the south side 00:20:03.460 --> 00:20:06.120 align:start position:0% to do a good job to help the south side of<00:20:03.610> social<00:20:03.790> impact<00:20:04.180> so<00:20:04.600> with<00:20:04.870> that<00:20:04.990> said<00:20:05.350> we 00:20:06.120 --> 00:20:06.130 align:start position:0% of social impact so with that said we 00:20:06.130 --> 00:20:08.760 align:start position:0% of social impact so with that said we have<00:20:06.340> just<00:20:06.370> about<00:20:07.120> five<00:20:07.390> minutes<00:20:07.630> for<00:20:08.620> any 00:20:08.760 --> 00:20:08.770 align:start position:0% have just about five minutes for any 00:20:08.770 --> 00:20:12.720 align:start position:0% have just about five minutes for any questions<00:20:09.690> so<00:20:10.800> there<00:20:11.800> you<00:20:11.920> go<00:20:12.070> Connor<00:20:12.490> you<00:20:12.640> can 00:20:12.720 --> 00:20:12.730 align:start position:0% questions so there you go Connor you can 00:20:12.730 --> 00:20:27.180 align:start position:0% questions so there you go Connor you can come<00:20:12.850> up<00:20:12.880> in<00:20:13.120> case<00:20:13.240> it's<00:20:13.450> technical<00:20:16.770> Thanks<00:20:26.190> on 00:20:27.180 --> 00:20:27.190 align:start position:0% come up in case it's technical Thanks on 00:20:27.190 --> 00:20:30.030 align:start position:0% come up in case it's technical Thanks on the<00:20:27.340> roadmap<00:20:27.520> is<00:20:27.910> there<00:20:28.150> going<00:20:28.420> to<00:20:28.480> be<00:20:29.040> another 00:20:30.030 --> 00:20:30.040 align:start position:0% the roadmap is there going to be another 00:20:30.040 --> 00:20:33.120 align:start position:0% the roadmap is there going to be another client<00:20:30.670> implementation<00:20:31.300> of<00:20:31.420> quorum<00:20:32.130> okay 00:20:33.120 --> 00:20:33.130 align:start position:0% client implementation of quorum okay 00:20:33.130 --> 00:20:34.890 align:start position:0% client implementation of quorum okay that's<00:20:33.430> that's<00:20:33.760> a<00:20:33.940> good<00:20:34.120> question<00:20:34.630> so 00:20:34.890 --> 00:20:34.900 align:start position:0% that's that's a good question so 00:20:34.900 --> 00:20:38.160 align:start position:0% that's that's a good question so initially<00:20:35.680> a<00:20:35.710> quorum<00:20:36.660> jump-started<00:20:37.660> the<00:20:37.900> work 00:20:38.160 --> 00:20:38.170 align:start position:0% initially a quorum jump-started the work 00:20:38.170 --> 00:20:42.870 align:start position:0% initially a quorum jump-started the work that<00:20:38.350> we<00:20:38.470> did<00:20:38.680> and<00:20:39.960> but<00:20:40.960> right<00:20:41.800> now<00:20:42.040> what<00:20:42.850> we 00:20:42.870 --> 00:20:42.880 align:start position:0% that we did and but right now what we 00:20:42.880 --> 00:20:45.960 align:start position:0% that we did and but right now what we I'd<00:20:43.810> say<00:20:44.050> there's<00:20:44.230> about<00:20:44.290> six<00:20:44.710> months<00:20:45.010> ago<00:20:45.130> we 00:20:45.960 --> 00:20:45.970 align:start position:0% I'd say there's about six months ago we 00:20:45.970 --> 00:20:47.520 align:start position:0% I'd say there's about six months ago we transition<00:20:46.780> that<00:20:46.930> there<00:20:47.050> was<00:20:47.140> a<00:20:47.170> quorum 00:20:47.520 --> 00:20:47.530 align:start position:0% transition that there was a quorum 00:20:47.530 --> 00:20:49.950 align:start position:0% transition that there was a quorum working<00:20:47.860> group<00:20:48.040> and<00:20:48.460> Amber<00:20:49.150> was<00:20:49.180> completely 00:20:49.950 --> 00:20:49.960 align:start position:0% working group and Amber was completely 00:20:49.960 --> 00:20:51.060 align:start position:0% working group and Amber was completely involved<00:20:50.200> in<00:20:50.320> she<00:20:50.530> can<00:20:50.680> tell<00:20:50.830> you<00:20:50.950> we 00:20:51.060 --> 00:20:51.070 align:start position:0% involved in she can tell you we 00:20:51.070 --> 00:20:54.060 align:start position:0% involved in she can tell you we transitioned<00:20:51.910> that<00:20:52.060> and<00:20:52.750> we<00:20:53.320> did<00:20:53.560> change<00:20:53.800> the 00:20:54.060 --> 00:20:54.070 align:start position:0% transitioned that and we did change the 00:20:54.070 --> 00:20:56.700 align:start position:0% transitioned that and we did change the name<00:20:54.250> because<00:20:55.180> we<00:20:55.480> want<00:20:55.720> the<00:20:55.930> work<00:20:56.140> it<00:20:56.320> we<00:20:56.440> want 00:20:56.700 --> 00:20:56.710 align:start position:0% name because we want the work it we want 00:20:56.710 --> 00:20:59.100 align:start position:0% name because we want the work it we want this<00:20:56.860> to<00:20:57.040> be<00:20:57.070> a<00:20:57.400> collective<00:20:58.030> so<00:20:58.690> there<00:20:58.930> isn't 00:20:59.100 --> 00:20:59.110 align:start position:0% this to be a collective so there isn't 00:20:59.110 --> 00:21:01.320 align:start position:0% this to be a collective so there isn't anything<00:20:59.530> at<00:20:59.890> quorum<00:21:00.370> quorums<00:21:01.090> work 00:21:01.320 --> 00:21:01.330 align:start position:0% anything at quorum quorums work 00:21:01.330 --> 00:21:04.260 align:start position:0% anything at quorum quorums work contribute<00:21:02.230> to<00:21:02.380> the<00:21:02.530> technical<00:21:03.070> spec<00:21:03.430> that's 00:21:04.260 --> 00:21:04.270 align:start position:0% contribute to the technical spec that's 00:21:04.270 --> 00:21:05.970 align:start position:0% contribute to the technical spec that's built<00:21:04.630> into<00:21:04.810> the<00:21:05.020> spec<00:21:05.320> that<00:21:05.530> you'll<00:21:05.710> download 00:21:05.970 --> 00:21:05.980 align:start position:0% built into the spec that you'll download 00:21:05.980 --> 00:21:09.210 align:start position:0% built into the spec that you'll download and<00:21:06.460> so<00:21:07.000> there<00:21:07.360> are<00:21:07.480> multiple<00:21:07.920> clients<00:21:08.920> that 00:21:09.210 --> 00:21:09.220 align:start position:0% and so there are multiple clients that 00:21:09.220 --> 00:21:10.980 align:start position:0% and so there are multiple clients that are<00:21:09.400> all<00:21:09.550> incorporated<00:21:10.270> rolled<00:21:10.720> into<00:21:10.870> one 00:21:10.980 --> 00:21:10.990 align:start position:0% are all incorporated rolled into one 00:21:10.990 --> 00:21:13.050 align:start position:0% are all incorporated rolled into one that<00:21:11.440> should<00:21:11.710> be<00:21:11.740> have<00:21:12.520> the<00:21:12.730> level 00:21:13.050 --> 00:21:13.060 align:start position:0% that should be have the level 00:21:13.060 --> 00:21:16.290 align:start position:0% that should be have the level interoperability<00:21:13.780> is<00:21:14.110> defined<00:21:15.070> by<00:21:15.310> what<00:21:16.120> they 00:21:16.290 --> 00:21:16.300 align:start position:0% interoperability is defined by what they 00:21:16.300 --> 00:21:19.140 align:start position:0% interoperability is defined by what they all<00:21:16.480> agree<00:21:16.900> upon<00:21:17.020> that's<00:21:17.920> required<00:21:18.490> must<00:21:18.850> have 00:21:19.140 --> 00:21:19.150 align:start position:0% all agree upon that's required must have 00:21:19.150 --> 00:21:21.540 align:start position:0% all agree upon that's required must have so<00:21:19.720> you<00:21:19.780> have<00:21:19.990> Claire<00:21:20.290> Maddox<00:21:20.470> you<00:21:21.040> have<00:21:21.280> block 00:21:21.540 --> 00:21:21.550 align:start position:0% so you have Claire Maddox you have block 00:21:21.550 --> 00:21:24.290 align:start position:0% so you have Claire Maddox you have block apps<00:21:21.820> you<00:21:22.180> have<00:21:22.330> the<00:21:22.660> new<00:21:22.840> Pantheon<00:21:23.440> solution 00:21:24.290 --> 00:21:24.300 align:start position:0% apps you have the new Pantheon solution 00:21:24.300 --> 00:21:28.590 align:start position:0% apps you have the new Pantheon solution all<00:21:25.300> of<00:21:25.540> those<00:21:25.750> folks<00:21:26.680> worked<00:21:27.370> very<00:21:27.790> closely 00:21:28.590 --> 00:21:28.600 align:start position:0% all of those folks worked very closely 00:21:28.600 --> 00:21:32.970 align:start position:0% all of those folks worked very closely together<00:21:28.990> so<00:21:29.970> quorum<00:21:30.970> quorum<00:21:31.750> is<00:21:32.050> a<00:21:32.350> platform 00:21:32.970 --> 00:21:32.980 align:start position:0% together so quorum quorum is a platform 00:21:32.980 --> 00:21:35.070 align:start position:0% together so quorum quorum is a platform or<00:21:33.220> you<00:21:34.150> can<00:21:34.330> download<00:21:34.540> the<00:21:34.780> source<00:21:34.930> code 00:21:35.070 --> 00:21:35.080 align:start position:0% or you can download the source code 00:21:35.080 --> 00:21:38.880 align:start position:0% or you can download the source code write<00:21:35.500> the<00:21:35.740> quorum<00:21:36.100> and<00:21:36.600> but<00:21:37.600> it'll<00:21:38.170> the<00:21:38.680> goal 00:21:38.880 --> 00:21:38.890 align:start position:0% write the quorum and but it'll the goal 00:21:38.890 --> 00:21:40.590 align:start position:0% write the quorum and but it'll the goal is<00:21:39.100> that<00:21:39.280> and<00:21:39.550> it<00:21:39.760> is<00:21:39.910> because<00:21:40.240> the<00:21:40.360> quorum 00:21:40.590 --> 00:21:40.600 align:start position:0% is that and it is because the quorum 00:21:40.600 --> 00:21:42.660 align:start position:0% is that and it is because the quorum guys<00:21:40.750> are<00:21:40.929> very<00:21:41.080> involved<00:21:41.470> in<00:21:41.530> our<00:21:41.650> org 00:21:42.660 --> 00:21:42.670 align:start position:0% guys are very involved in our org 00:21:42.670 --> 00:21:45.510 align:start position:0% guys are very involved in our org it'll<00:21:43.179> conform<00:21:43.900> to<00:21:44.020> the<00:21:44.110> a<00:21:44.140> spec<00:21:44.620> any<00:21:45.309> other 00:21:45.510 --> 00:21:45.520 align:start position:0% it'll conform to the a spec any other 00:21:45.520 --> 00:21:49.250 align:start position:0% it'll conform to the a spec any other questions 00:21:49.250 --> 00:21:49.260 align:start position:0% 00:21:49.260 --> 00:21:52.470 align:start position:0% Alex<00:21:50.610> sorry<00:21:51.610> could<00:21:51.760> you<00:21:51.790> share<00:21:52.030> Allah<00:21:52.210> I<00:21:52.360> know 00:21:52.470 --> 00:21:52.480 align:start position:0% Alex sorry could you share Allah I know 00:21:52.480 --> 00:21:53.940 align:start position:0% Alex sorry could you share Allah I know that<00:21:52.600> there<00:21:52.720> was<00:21:52.809> a<00:21:52.840> couple<00:21:53.290> sessions<00:21:53.710> that<00:21:53.830> we 00:21:53.940 --> 00:21:53.950 align:start position:0% that there was a couple sessions that we 00:21:53.950 --> 00:21:56.190 align:start position:0% that there was a couple sessions that we had<00:21:54.070> on<00:21:54.630> interaction<00:21:55.630> with<00:21:55.780> like<00:21:55.929> public 00:21:56.190 --> 00:21:56.200 align:start position:0% had on interaction with like public 00:21:56.200 --> 00:21:57.120 align:start position:0% had on interaction with like public etherium<00:21:56.530> could<00:21:56.679> you<00:21:56.770> just<00:21:56.920> give<00:21:57.100> a 00:21:57.120 --> 00:21:57.130 align:start position:0% etherium could you just give a 00:21:57.130 --> 00:21:58.830 align:start position:0% etherium could you just give a high-level<00:21:57.640> overview<00:21:57.970> of<00:21:58.360> what<00:21:58.480> the<00:21:58.570> outcomes 00:21:58.830 --> 00:21:58.840 align:start position:0% high-level overview of what the outcomes 00:21:58.840 --> 00:22:01.620 align:start position:0% high-level overview of what the outcomes of<00:21:58.929> those<00:21:59.049> were<00:21:59.790> yeah<00:22:00.790> I'll<00:22:01.000> I'll<00:22:01.330> talk<00:22:01.600> a 00:22:01.620 --> 00:22:01.630 align:start position:0% of those were yeah I'll I'll talk a 00:22:01.630 --> 00:22:04.020 align:start position:0% of those were yeah I'll I'll talk a little<00:22:01.720> bit<00:22:01.960> about<00:22:01.990> and<00:22:02.380> where<00:22:02.740> so<00:22:03.549> we've<00:22:03.760> had 00:22:04.020 --> 00:22:04.030 align:start position:0% little bit about and where so we've had 00:22:04.030 --> 00:22:05.640 align:start position:0% little bit about and where so we've had multiple<00:22:04.270> meetings<00:22:04.660> with<00:22:05.080> the<00:22:05.230> folks<00:22:05.470> from 00:22:05.640 --> 00:22:05.650 align:start position:0% multiple meetings with the folks from 00:22:05.650 --> 00:22:09.810 align:start position:0% multiple meetings with the folks from public<00:22:06.490> etherium<00:22:07.120> and<00:22:07.470> our<00:22:08.470> goal<00:22:08.740> is<00:22:08.950> we<00:22:09.190> we 00:22:09.810 --> 00:22:09.820 align:start position:0% public etherium and our goal is we we 00:22:09.820 --> 00:22:12.510 align:start position:0% public etherium and our goal is we we should<00:22:10.059> be<00:22:10.240> very<00:22:10.870> collegiate<00:22:11.830> ly<00:22:12.070> working 00:22:12.510 --> 00:22:12.520 align:start position:0% should be very collegiate ly working 00:22:12.520 --> 00:22:16.669 align:start position:0% should be very collegiate ly working collaboratively<00:22:13.059> together<00:22:13.540> and<00:22:14.200> we<00:22:14.530> are<00:22:15.120> and 00:22:16.669 --> 00:22:16.679 align:start position:0% collaboratively together and we are and 00:22:16.679 --> 00:22:22.860 align:start position:0% collaboratively together and we are and and<00:22:17.679> so<00:22:18.419> we<00:22:19.620> we<00:22:20.620> we<00:22:21.070> track<00:22:21.460> the<00:22:21.700> roadmap<00:22:22.150> that 00:22:22.860 --> 00:22:22.870 align:start position:0% and so we we we track the roadmap that 00:22:22.870 --> 00:22:25.080 align:start position:0% and so we we we track the roadmap that goes<00:22:23.140> on<00:22:23.410> and<00:22:23.710> they<00:22:24.130> therein<00:22:24.490> foundation<00:22:24.970> we 00:22:25.080 --> 00:22:25.090 align:start position:0% goes on and they therein foundation we 00:22:25.090 --> 00:22:26.730 align:start position:0% goes on and they therein foundation we had<00:22:25.299> some<00:22:25.510> meetings<00:22:25.960> where<00:22:26.200> we<00:22:26.320> talked<00:22:26.559> about 00:22:26.730 --> 00:22:26.740 align:start position:0% had some meetings where we talked about 00:22:26.740 --> 00:22:29.900 align:start position:0% had some meetings where we talked about like<00:22:27.190> the<00:22:27.340> EIP<00:22:27.700> process<00:22:28.510> and<00:22:28.809> how<00:22:29.380> the<00:22:29.440> EAP 00:22:29.900 --> 00:22:29.910 align:start position:0% like the EIP process and how the EAP 00:22:29.910 --> 00:22:31.980 align:start position:0% like the EIP process and how the EAP process<00:22:30.910> should<00:22:31.120> benefit<00:22:31.540> we<00:22:31.720> should<00:22:31.870> be 00:22:31.980 --> 00:22:31.990 align:start position:0% process should benefit we should be 00:22:31.990 --> 00:22:34.470 align:start position:0% process should benefit we should be mutually<00:22:32.440> benefiting<00:22:33.160> each<00:22:33.370> other<00:22:33.640> so<00:22:34.270> we<00:22:34.390> had 00:22:34.470 --> 00:22:34.480 align:start position:0% mutually benefiting each other so we had 00:22:34.480 --> 00:22:36.480 align:start position:0% mutually benefiting each other so we had a<00:22:34.540> two<00:22:34.750> hour<00:22:34.780> meeting<00:22:35.140> that<00:22:35.500> Connor<00:22:35.919> actually 00:22:36.480 --> 00:22:36.490 align:start position:0% a two hour meeting that Connor actually 00:22:36.490 --> 00:22:39.210 align:start position:0% a two hour meeting that Connor actually presented<00:22:37.030> on<00:22:37.150> in<00:22:37.360> others<00:22:37.690> and<00:22:38.020> so<00:22:38.650> we<00:22:39.010> will 00:22:39.210 --> 00:22:39.220 align:start position:0% presented on in others and so we will 00:22:39.220 --> 00:22:41.280 align:start position:0% presented on in others and so we will actually<00:22:39.460> look<00:22:39.880> at<00:22:40.090> what<00:22:40.240> we<00:22:40.480> develop<00:22:41.020> and<00:22:41.200> if 00:22:41.280 --> 00:22:41.290 align:start position:0% actually look at what we develop and if 00:22:41.290 --> 00:22:43.350 align:start position:0% actually look at what we develop and if we<00:22:41.470> see<00:22:41.799> things<00:22:41.980> that<00:22:42.220> can<00:22:42.400> work<00:22:42.730> on<00:22:42.940> that<00:22:43.120> yet 00:22:43.350 --> 00:22:43.360 align:start position:0% we see things that can work on that yet 00:22:43.360 --> 00:22:50.010 align:start position:0% we see things that can work on that yet your<00:22:44.490> and<00:22:45.490> these<00:22:46.030> yours<00:22:46.360> or<00:22:47.160> any<00:22:48.160> of<00:22:48.370> the<00:22:49.020> VIPs 00:22:50.010 --> 00:22:50.020 align:start position:0% your and these yours or any of the VIPs 00:22:50.020 --> 00:22:53.190 align:start position:0% your and these yours or any of the VIPs that<00:22:50.530> make<00:22:50.950> sense<00:22:51.340> will<00:22:51.910> do<00:22:52.090> it<00:22:52.240> and<00:22:52.450> we<00:22:53.080> were 00:22:53.190 --> 00:22:53.200 align:start position:0% that make sense will do it and we were 00:22:53.200 --> 00:22:55.260 align:start position:0% that make sense will do it and we were also<00:22:53.350> giving<00:22:53.799> visibility<00:22:54.400> to<00:22:54.669> the<00:22:54.760> folks<00:22:55.030> in 00:22:55.260 --> 00:22:55.270 align:start position:0% also giving visibility to the folks in 00:22:55.270 --> 00:22:57.720 align:start position:0% also giving visibility to the folks in the<00:22:55.330> Theorem<00:22:55.780> foundation<00:22:56.410> to<00:22:56.710> they<00:22:57.340> can<00:22:57.549> go 00:22:57.720 --> 00:22:57.730 align:start position:0% the Theorem foundation to they can go 00:22:57.730 --> 00:23:00.620 align:start position:0% the Theorem foundation to they can go participate<00:22:58.660> and<00:22:58.960> see<00:22:59.140> what<00:22:59.320> we're<00:22:59.470> doing 00:23:00.620 --> 00:23:00.630 align:start position:0% participate and see what we're doing 00:23:00.630 --> 00:23:03.390 align:start position:0% participate and see what we're doing what's<00:23:01.630> not<00:23:01.840> on<00:23:02.110> here<00:23:02.410> and<00:23:02.530> I'll<00:23:02.650> just<00:23:02.740> don't<00:23:03.040> I 00:23:03.390 --> 00:23:03.400 align:start position:0% what's not on here and I'll just don't I 00:23:03.400 --> 00:23:05.630 align:start position:0% what's not on here and I'll just don't I right<00:23:04.240> now<00:23:04.390> the<00:23:04.450> work<00:23:04.720> we're<00:23:04.900> doing<00:23:04.929> is 00:23:05.630 --> 00:23:05.640 align:start position:0% right now the work we're doing is 00:23:05.640 --> 00:23:08.549 align:start position:0% right now the work we're doing is private<00:23:06.640> permission<00:23:07.030> networks<00:23:07.419> I've<00:23:08.200> talked 00:23:08.549 --> 00:23:08.559 align:start position:0% private permission networks I've talked 00:23:08.559 --> 00:23:10.530 align:start position:0% private permission networks I've talked to<00:23:08.710> our<00:23:08.830> two<00:23:09.370> folks<00:23:09.610> in<00:23:09.760> our<00:23:09.850> org<00:23:10.120> and 00:23:10.530 --> 00:23:10.540 align:start position:0% to our two folks in our org and 00:23:10.540 --> 00:23:15.630 align:start position:0% to our two folks in our org and teammates<00:23:11.290> we<00:23:11.950> we<00:23:12.820> want<00:23:13.120> a<00:23:13.799> roadmap<00:23:14.799> to<00:23:15.100> to 00:23:15.630 --> 00:23:15.640 align:start position:0% teammates we we want a roadmap to to 00:23:15.640 --> 00:23:18.930 align:start position:0% teammates we we want a roadmap to to address<00:23:16.150> public<00:23:17.110> commercial<00:23:17.950> networks<00:23:18.460> that 00:23:18.930 --> 00:23:18.940 align:start position:0% address public commercial networks that 00:23:18.940 --> 00:23:22.620 align:start position:0% address public commercial networks that use<00:23:19.179> the<00:23:19.360> etherium<00:23:19.870> a<00:23:20.020> net<00:23:20.290> and<00:23:21.150> so<00:23:22.150> part<00:23:22.540> of 00:23:22.620 --> 00:23:22.630 align:start position:0% use the etherium a net and so part of 00:23:22.630 --> 00:23:23.909 align:start position:0% use the etherium a net and so part of what<00:23:22.780> we're<00:23:22.929> looking<00:23:23.200> to<00:23:23.230> do<00:23:23.440> and<00:23:23.620> I've<00:23:23.710> talked 00:23:23.909 --> 00:23:23.919 align:start position:0% what we're looking to do and I've talked 00:23:23.919 --> 00:23:26.310 align:start position:0% what we're looking to do and I've talked to<00:23:24.040> a<00:23:24.070> number<00:23:24.220> of<00:23:24.429> companies<00:23:24.760> they<00:23:25.510> too<00:23:26.080> can 00:23:26.310 --> 00:23:26.320 align:start position:0% to a number of companies they too can 00:23:26.320 --> 00:23:29.100 align:start position:0% to a number of companies they too can join<00:23:26.530> us<00:23:27.070> and<00:23:27.370> contribute<00:23:28.059> how<00:23:28.270> do<00:23:28.330> we<00:23:28.570> how<00:23:29.049> do 00:23:29.100 --> 00:23:29.110 align:start position:0% join us and contribute how do we how do 00:23:29.110 --> 00:23:31.250 align:start position:0% join us and contribute how do we how do we<00:23:29.290> bring<00:23:29.679> that<00:23:29.830> in<00:23:30.040> and<00:23:30.280> and<00:23:30.730> so<00:23:31.030> we're 00:23:31.250 --> 00:23:31.260 align:start position:0% we bring that in and and so we're 00:23:31.260 --> 00:23:33.510 align:start position:0% we bring that in and and so we're leveraging<00:23:32.260> there's<00:23:32.830> so<00:23:32.980> many<00:23:33.130> opportunities 00:23:33.510 --> 00:23:33.520 align:start position:0% leveraging there's so many opportunities 00:23:33.520 --> 00:23:35.789 align:start position:0% leveraging there's so many opportunities for<00:23:33.970> the<00:23:34.179> public<00:23:34.419> may<00:23:34.809> net<00:23:35.049> that<00:23:35.590> are 00:23:35.789 --> 00:23:35.799 align:start position:0% for the public may net that are 00:23:35.799 --> 00:23:37.200 align:start position:0% for the public may net that are commercial<00:23:36.280> and<00:23:36.460> I<00:23:36.520> could<00:23:36.700> think<00:23:36.880> of<00:23:37.000> some 00:23:37.200 --> 00:23:37.210 align:start position:0% commercial and I could think of some 00:23:37.210 --> 00:23:39.630 align:start position:0% commercial and I could think of some that<00:23:37.390> I'd<00:23:37.600> love<00:23:38.140> to<00:23:38.320> see<00:23:38.530> like<00:23:38.830> get<00:23:39.160> rid<00:23:39.340> of<00:23:39.370> the 00:23:39.630 --> 00:23:39.640 align:start position:0% that I'd love to see like get rid of the 00:23:39.640 --> 00:23:41.430 align:start position:0% that I'd love to see like get rid of the ticket<00:23:40.000> scalpers<00:23:40.480> a<00:23:40.510> secondhand<00:23:41.080> ticket 00:23:41.430 --> 00:23:41.440 align:start position:0% ticket scalpers a secondhand ticket 00:23:41.440 --> 00:23:44.010 align:start position:0% ticket scalpers a secondhand ticket market<00:23:41.830> I<00:23:42.010> would<00:23:42.700> pay<00:23:43.000> money<00:23:43.240> to<00:23:43.419> have<00:23:43.660> that 00:23:44.010 --> 00:23:44.020 align:start position:0% market I would pay money to have that 00:23:44.020 --> 00:23:46.530 align:start position:0% market I would pay money to have that done<00:23:44.290> so<00:23:44.799> there<00:23:45.040> your<00:23:45.610> imagination<00:23:46.360> could 00:23:46.530 --> 00:23:46.540 align:start position:0% done so there your imagination could 00:23:46.540 --> 00:23:48.090 align:start position:0% done so there your imagination could just<00:23:46.750> take<00:23:46.900> you<00:23:47.020> everywhere<00:23:47.320> for<00:23:47.679> what<00:23:47.890> we 00:23:48.090 --> 00:23:48.100 align:start position:0% just take you everywhere for what we 00:23:48.100 --> 00:23:49.890 align:start position:0% just take you everywhere for what we want<00:23:48.309> to<00:23:48.460> do<00:23:48.640> because<00:23:49.120> there's<00:23:49.450> a<00:23:49.510> lot<00:23:49.660> of<00:23:49.690> work 00:23:49.890 --> 00:23:49.900 align:start position:0% want to do because there's a lot of work 00:23:49.900 --> 00:23:52.770 align:start position:0% want to do because there's a lot of work but<00:23:50.049> you<00:23:50.110> definitely<00:23:50.410> need<00:23:50.740> to<00:23:51.419> create<00:23:52.419> a<00:23:52.480> spec 00:23:52.770 --> 00:23:52.780 align:start position:0% but you definitely need to create a spec 00:23:52.780 --> 00:23:55.169 align:start position:0% but you definitely need to create a spec you<00:23:53.200> need<00:23:53.410> to<00:23:53.559> get<00:23:54.100> get<00:23:54.460> it<00:23:54.580> certified<00:23:54.760> if 00:23:55.169 --> 00:23:55.179 align:start position:0% you need to get get it certified if 00:23:55.179 --> 00:23:56.190 align:start position:0% you need to get get it certified if you're<00:23:55.300> going<00:23:55.390> to<00:23:55.480> get<00:23:55.660> like 00:23:56.190 --> 00:23:56.200 align:start position:0% you're going to get like 00:23:56.200 --> 00:23:58.590 align:start position:0% you're going to get like Faiza<00:23:57.039> or<00:23:57.309> anybody<00:23:57.730> else<00:23:57.940> to<00:23:58.149> say<00:23:58.330> I'm<00:23:58.450> going 00:23:58.590 --> 00:23:58.600 align:start position:0% Faiza or anybody else to say I'm going 00:23:58.600 --> 00:23:59.460 align:start position:0% Faiza or anybody else to say I'm going to<00:23:58.659> buy<00:23:58.809> into<00:23:59.019> it 00:23:59.460 --> 00:23:59.470 align:start position:0% to buy into it 00:23:59.470 --> 00:24:01.590 align:start position:0% to buy into it they're<00:23:59.830> gonna<00:23:59.980> want<00:24:00.399> to<00:24:00.669> know<00:24:00.880> that<00:24:01.240> there's 00:24:01.590 --> 00:24:01.600 align:start position:0% they're gonna want to know that there's 00:24:01.600 --> 00:24:04.230 align:start position:0% they're gonna want to know that there's 500<00:24:02.529> companies<00:24:02.919> behind<00:24:03.370> it<00:24:03.519> there's<00:24:03.760> multiple 00:24:04.230 --> 00:24:04.240 align:start position:0% 500 companies behind it there's multiple 00:24:04.240 --> 00:24:05.750 align:start position:0% 500 companies behind it there's multiple vendors<00:24:04.510> that<00:24:04.809> they<00:24:04.870> can<00:24:05.139> pick<00:24:05.289> from<00:24:05.500> any 00:24:05.750 --> 00:24:05.760 align:start position:0% vendors that they can pick from any 00:24:05.760 --> 00:24:13.160 align:start position:0% vendors that they can pick from any other<00:24:06.760> questions<00:24:09.600> great<00:24:10.600> thanks<00:24:11.350> very<00:24:11.529> much 00:24:13.160 --> 00:24:13.170 align:start position:0% other questions great thanks very much 00:24:13.170 --> 00:24:21.980 align:start position:0% other questions great thanks very much [Applause] 00:24:21.980 --> 00:24:21.990 align:start position:0% 00:24:21.990 --> 00:24:24.050 align:start position:0% you