WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:10.270 align:start position:0% [Music] 00:00:10.270 --> 00:00:10.280 align:start position:0% [Music] 00:00:10.280 --> 00:00:12.629 align:start position:0% [Music] all<00:00:10.400> right<00:00:10.679> yes<00:00:10.880> so<00:00:11.160> I<00:00:11.320> am<00:00:11.639> Derek 00:00:12.629 --> 00:00:12.639 align:start position:0% all right yes so I am Derek 00:00:12.639 --> 00:00:14.709 align:start position:0% all right yes so I am Derek unfortunately<00:00:13.639> my<00:00:13.759> partner<00:00:14.040> Melton<00:00:14.480> wasn't 00:00:14.709 --> 00:00:14.719 align:start position:0% unfortunately my partner Melton wasn't 00:00:14.719 --> 00:00:18.230 align:start position:0% unfortunately my partner Melton wasn't able<00:00:14.920> to<00:00:15.080> make<00:00:15.280> it<00:00:16.279> um<00:00:17.279> but<00:00:17.520> yeah<00:00:17.760> our<00:00:18.000> our 00:00:18.230 --> 00:00:18.240 align:start position:0% able to make it um but yeah our our 00:00:18.240 --> 00:00:20.710 align:start position:0% able to make it um but yeah our our project<00:00:18.640> our<00:00:18.800> joint<00:00:19.160> project<00:00:19.600> is<00:00:19.920> uh<00:00:20.160> bzu 00:00:20.710 --> 00:00:20.720 align:start position:0% project our joint project is uh bzu 00:00:20.720 --> 00:00:43.790 align:start position:0% project our joint project is uh bzu portal<00:00:21.080> client<00:00:21.680> Samba<00:00:22.480> so 00:00:43.790 --> 00:00:43.800 align:start position:0% 00:00:43.800 --> 00:00:45.470 align:start position:0% yes<00:00:43.960> so<00:00:44.320> I<00:00:44.399> guess<00:00:44.520> I'll<00:00:44.680> give<00:00:44.840> a<00:00:44.960> a<00:00:45.160> brief 00:00:45.470 --> 00:00:45.480 align:start position:0% yes so I guess I'll give a a brief 00:00:45.480 --> 00:00:48.630 align:start position:0% yes so I guess I'll give a a brief introduction<00:00:46.039> to<00:00:46.320> portal<00:00:47.320> um<00:00:47.559> because<00:00:48.559> I 00:00:48.630 --> 00:00:48.640 align:start position:0% introduction to portal um because I 00:00:48.640 --> 00:00:50.229 align:start position:0% introduction to portal um because I think<00:00:48.960> a<00:00:49.039> lot<00:00:49.199> of<00:00:49.280> the<00:00:49.399> reasons<00:00:49.719> that<00:00:49.879> I<00:00:50.000> wanted 00:00:50.229 --> 00:00:50.239 align:start position:0% think a lot of the reasons that I wanted 00:00:50.239 --> 00:00:51.549 align:start position:0% think a lot of the reasons that I wanted to<00:00:50.360> work<00:00:50.520> on<00:00:50.719> this<00:00:50.920> project<00:00:51.199> were<00:00:51.399> just 00:00:51.549 --> 00:00:51.559 align:start position:0% to work on this project were just 00:00:51.559 --> 00:00:53.630 align:start position:0% to work on this project were just because<00:00:51.879> I<00:00:52.000> found<00:00:52.760> uh<00:00:52.879> portal<00:00:53.199> to<00:00:53.280> be<00:00:53.359> such<00:00:53.520> an 00:00:53.630 --> 00:00:53.640 align:start position:0% because I found uh portal to be such an 00:00:53.640 --> 00:00:58.150 align:start position:0% because I found uh portal to be such an interesting<00:00:54.239> topic<00:00:55.239> and<00:00:55.960> so<00:00:56.960> there<00:00:57.079> we<00:00:57.239> go<00:00:57.440> so 00:00:58.150 --> 00:00:58.160 align:start position:0% interesting topic and so there we go so 00:00:58.160 --> 00:01:00.069 align:start position:0% interesting topic and so there we go so for<00:00:58.320> the<00:00:58.399> purposes<00:00:58.719> of<00:00:58.920> Som<00:00:59.320> up<00:00:59.440> to<00:00:59.519> the<00:00:59.600> scope 00:01:00.069 --> 00:01:00.079 align:start position:0% for the purposes of Som up to the scope 00:01:00.079 --> 00:01:04.509 align:start position:0% for the purposes of Som up to the scope of<00:01:00.239> EPF<00:01:01.120> um<00:01:02.039> which<00:01:02.199> is<00:01:02.640> uh<00:01:02.840> just<00:01:03.280> for<00:01:03.519> a<00:01:03.640> few<00:01:04.400> uh 00:01:04.509 --> 00:01:04.519 align:start position:0% of EPF um which is uh just for a few uh 00:01:04.519 --> 00:01:05.710 align:start position:0% of EPF um which is uh just for a few uh main<00:01:04.680> roles<00:01:04.920> through<00:01:05.080> the<00:01:05.199> history<00:01:05.519> sub 00:01:05.710 --> 00:01:05.720 align:start position:0% main roles through the history sub 00:01:05.720 --> 00:01:07.590 align:start position:0% main roles through the history sub network<00:01:06.479> uh<00:01:06.600> portal<00:01:06.880> Network<00:01:07.200> provides<00:01:07.479> a 00:01:07.590 --> 00:01:07.600 align:start position:0% network uh portal Network provides a 00:01:07.600 --> 00:01:09.830 align:start position:0% network uh portal Network provides a solution<00:01:08.520> uh<00:01:08.680> to<00:01:08.840> the<00:01:08.960> proposed<00:01:09.320> changes<00:01:09.640> in 00:01:09.830 --> 00:01:09.840 align:start position:0% solution uh to the proposed changes in 00:01:09.840 --> 00:01:12.670 align:start position:0% solution uh to the proposed changes in EIP<00:01:10.560> 44s<00:01:11.560> that<00:01:11.680> allows<00:01:12.000> for<00:01:12.159> the<00:01:12.320> DraStic 00:01:12.670 --> 00:01:12.680 align:start position:0% EIP 44s that allows for the DraStic 00:01:12.680 --> 00:01:14.590 align:start position:0% EIP 44s that allows for the DraStic limiting<00:01:13.040> of<00:01:13.200> Storage<00:01:13.880> storage<00:01:14.200> requirements 00:01:14.590 --> 00:01:14.600 align:start position:0% limiting of Storage storage requirements 00:01:14.600 --> 00:01:17.190 align:start position:0% limiting of Storage storage requirements to<00:01:14.759> run<00:01:14.920> a<00:01:15.000> node<00:01:15.799> um<00:01:16.600> as<00:01:16.720> well<00:01:16.880> it<00:01:17.000> also 00:01:17.190 --> 00:01:17.200 align:start position:0% to run a node um as well it also 00:01:17.200 --> 00:01:18.630 align:start position:0% to run a node um as well it also provides<00:01:17.479> a<00:01:17.600> way<00:01:17.720> to<00:01:17.880> handle<00:01:18.119> the<00:01:18.200> sharing<00:01:18.520> of 00:01:18.630 --> 00:01:18.640 align:start position:0% provides a way to handle the sharing of 00:01:18.640 --> 00:01:20.710 align:start position:0% provides a way to handle the sharing of data<00:01:18.880> in<00:01:18.960> a<00:01:19.119> way<00:01:19.280> that<00:01:20.040> uh<00:01:20.159> not<00:01:20.320> only<00:01:20.560> can 00:01:20.710 --> 00:01:20.720 align:start position:0% data in a way that uh not only can 00:01:20.720 --> 00:01:22.350 align:start position:0% data in a way that uh not only can handle<00:01:21.000> scaling<00:01:21.479> but<00:01:21.640> actually<00:01:21.880> benefits 00:01:22.350 --> 00:01:22.360 align:start position:0% handle scaling but actually benefits 00:01:22.360 --> 00:01:24.429 align:start position:0% handle scaling but actually benefits from<00:01:22.560> scaling<00:01:23.240> and<00:01:23.439> these<00:01:23.600> benefits<00:01:24.159> also 00:01:24.429 --> 00:01:24.439 align:start position:0% from scaling and these benefits also 00:01:24.439 --> 00:01:26.590 align:start position:0% from scaling and these benefits also directly<00:01:24.759> link<00:01:25.040> to<00:01:25.240> ethereum<00:01:25.680> usability<00:01:26.400> and 00:01:26.590 --> 00:01:26.600 align:start position:0% directly link to ethereum usability and 00:01:26.600 --> 00:01:28.990 align:start position:0% directly link to ethereum usability and the<00:01:27.439> uh<00:01:27.560> lowering<00:01:27.960> the<00:01:28.119> barrier<00:01:28.400> of<00:01:28.520> Entry<00:01:28.799> to 00:01:28.990 --> 00:01:29.000 align:start position:0% the uh lowering the barrier of Entry to 00:01:29.000 --> 00:01:30.990 align:start position:0% the uh lowering the barrier of Entry to participation<00:01:29.759> uh<00:01:29.960> in<00:01:30.040> the<00:01:30.159> ethereum 00:01:30.990 --> 00:01:31.000 align:start position:0% participation uh in the ethereum 00:01:31.000 --> 00:01:33.270 align:start position:0% participation uh in the ethereum ecosystem<00:01:32.000> and<00:01:32.079> then<00:01:32.240> as<00:01:32.399> well<00:01:32.759> outside<00:01:33.079> of 00:01:33.270 --> 00:01:33.280 align:start position:0% ecosystem and then as well outside of 00:01:33.280 --> 00:01:35.830 align:start position:0% ecosystem and then as well outside of the<00:01:33.399> scope<00:01:33.640> of<00:01:33.759> EPF<00:01:34.360> as<00:01:34.439> we<00:01:34.600> continue<00:01:35.479> portal 00:01:35.830 --> 00:01:35.840 align:start position:0% the scope of EPF as we continue portal 00:01:35.840 --> 00:01:37.350 align:start position:0% the scope of EPF as we continue portal also<00:01:36.079> contains<00:01:36.520> proposed<00:01:36.880> solutions<00:01:37.240> to 00:01:37.350 --> 00:01:37.360 align:start position:0% also contains proposed solutions to 00:01:37.360 --> 00:01:39.270 align:start position:0% also contains proposed solutions to managing<00:01:37.720> State<00:01:38.000> and<00:01:38.159> Beacon<00:01:38.560> chain<00:01:38.880> related 00:01:39.270 --> 00:01:39.280 align:start position:0% managing State and Beacon chain related 00:01:39.280 --> 00:01:40.789 align:start position:0% managing State and Beacon chain related information<00:01:39.920> although<00:01:40.280> this<00:01:40.360> is<00:01:40.520> somewhat 00:01:40.789 --> 00:01:40.799 align:start position:0% information although this is somewhat 00:01:40.799 --> 00:01:43.190 align:start position:0% information although this is somewhat more 00:01:43.190 --> 00:01:43.200 align:start position:0% 00:01:43.200 --> 00:01:46.270 align:start position:0% preliminary<00:01:44.200> oh<00:01:45.040> there<00:01:45.159> we<00:01:45.280> go<00:01:45.479> and<00:01:45.600> so<00:01:46.119> now 00:01:46.270 --> 00:01:46.280 align:start position:0% preliminary oh there we go and so now 00:01:46.280 --> 00:01:48.469 align:start position:0% preliminary oh there we go and so now moving<00:01:46.520> into<00:01:46.840> the<00:01:47.000> the<00:01:47.119> role<00:01:47.520> of<00:01:47.719> Samba<00:01:48.280> in 00:01:48.469 --> 00:01:48.479 align:start position:0% moving into the the role of Samba in 00:01:48.479 --> 00:01:51.149 align:start position:0% moving into the the role of Samba in Portal 00:01:51.149 --> 00:01:51.159 align:start position:0% Portal 00:01:51.159 --> 00:01:54.109 align:start position:0% Portal um<00:01:52.159> there<00:01:52.280> we<00:01:52.479> go<00:01:53.079> uh<00:01:53.200> so<00:01:53.439> there's<00:01:53.640> kind<00:01:53.759> of<00:01:53.880> two 00:01:54.109 --> 00:01:54.119 align:start position:0% um there we go uh so there's kind of two 00:01:54.119 --> 00:01:57.270 align:start position:0% um there we go uh so there's kind of two main<00:01:54.399> roles<00:01:55.040> s<00:01:55.479> can<00:01:55.680> play<00:01:56.000> in<00:01:56.159> the<00:01:56.320> in<00:01:56.479> this<00:01:57.119> in 00:01:57.270 --> 00:01:57.280 align:start position:0% main roles s can play in the in this in 00:01:57.280 --> 00:02:00.029 align:start position:0% main roles s can play in the in this in this<00:01:57.680> big<00:01:58.000> kind<00:01:58.119> of<00:01:58.280> puzzle<00:01:58.680> and<00:01:58.799> so<00:01:59.640> one<00:01:59.960> of 00:02:00.029 --> 00:02:00.039 align:start position:0% this big kind of puzzle and so one of 00:02:00.039 --> 00:02:01.550 align:start position:0% this big kind of puzzle and so one of the<00:02:00.159> big<00:02:00.320> roles<00:02:00.600> is<00:02:00.719> of<00:02:00.840> course<00:02:01.000> to<00:02:01.119> fill<00:02:01.360> the 00:02:01.550 --> 00:02:01.560 align:start position:0% the big roles is of course to fill the 00:02:01.560 --> 00:02:02.830 align:start position:0% the big roles is of course to fill the Gap<00:02:01.759> in<00:02:01.840> the<00:02:01.960> consensus<00:02:02.320> hyperledger 00:02:02.830 --> 00:02:02.840 align:start position:0% Gap in the consensus hyperledger 00:02:02.840 --> 00:02:05.270 align:start position:0% Gap in the consensus hyperledger ecosystem<00:02:03.320> in<00:02:03.439> terms<00:02:03.640> of<00:02:03.759> a<00:02:03.840> long-term<00:02:04.280> EIP<00:02:04.640> 44 00:02:05.270 --> 00:02:05.280 align:start position:0% ecosystem in terms of a long-term EIP 44 00:02:05.280 --> 00:02:07.950 align:start position:0% ecosystem in terms of a long-term EIP 44 solution<00:02:06.159> in<00:02:06.360> regard<00:02:06.640> to<00:02:07.039> the<00:02:07.200> existence<00:02:07.520> of<00:02:07.640> s 00:02:07.950 --> 00:02:07.960 align:start position:0% solution in regard to the existence of s 00:02:07.960 --> 00:02:09.550 align:start position:0% solution in regard to the existence of s but<00:02:08.119> this<00:02:08.239> also<00:02:08.440> works<00:02:08.679> to<00:02:08.920> increase<00:02:09.360> the 00:02:09.550 --> 00:02:09.560 align:start position:0% but this also works to increase the 00:02:09.560 --> 00:02:11.710 align:start position:0% but this also works to increase the portal<00:02:09.920> client<00:02:10.360> diversity<00:02:11.280> um<00:02:11.400> in<00:02:11.480> addition 00:02:11.710 --> 00:02:11.720 align:start position:0% portal client diversity um in addition 00:02:11.720 --> 00:02:13.830 align:start position:0% portal client diversity um in addition to<00:02:11.840> ease<00:02:12.000> of<00:02:12.160> use<00:02:12.920> in<00:02:13.000> terms<00:02:13.200> of<00:02:13.319> the<00:02:13.440> basic 00:02:13.830 --> 00:02:13.840 align:start position:0% to ease of use in terms of the basic 00:02:13.840 --> 00:02:16.070 align:start position:0% to ease of use in terms of the basic execution<00:02:14.360> clients<00:02:15.280> but<00:02:15.440> I<00:02:15.519> think<00:02:15.640> the<00:02:15.760> other 00:02:16.070 --> 00:02:16.080 align:start position:0% execution clients but I think the other 00:02:16.080 --> 00:02:18.309 align:start position:0% execution clients but I think the other one<00:02:16.560> and<00:02:16.879> potentially<00:02:17.239> more<00:02:17.440> exciting<00:02:17.879> in<00:02:18.080> my 00:02:18.309 --> 00:02:18.319 align:start position:0% one and potentially more exciting in my 00:02:18.319 --> 00:02:20.750 align:start position:0% one and potentially more exciting in my eyes<00:02:18.760> is<00:02:19.040> its<00:02:19.599> unique<00:02:19.959> position<00:02:20.319> compared<00:02:20.599> to 00:02:20.750 --> 00:02:20.760 align:start position:0% eyes is its unique position compared to 00:02:20.760 --> 00:02:24.070 align:start position:0% eyes is its unique position compared to other<00:02:21.080> portal<00:02:21.440> clients<00:02:21.800> in<00:02:22.000> that<00:02:22.879> um<00:02:23.640> it<00:02:23.800> has<00:02:23.959> a 00:02:24.070 --> 00:02:24.080 align:start position:0% other portal clients in that um it has a 00:02:24.080 --> 00:02:26.030 align:start position:0% other portal clients in that um it has a way<00:02:24.200> to<00:02:24.400> easily<00:02:24.720> bring<00:02:25.000> portal<00:02:25.360> functionality 00:02:26.030 --> 00:02:26.040 align:start position:0% way to easily bring portal functionality 00:02:26.040 --> 00:02:28.229 align:start position:0% way to easily bring portal functionality to<00:02:26.280> different<00:02:26.800> uh<00:02:26.920> Android<00:02:27.599> to<00:02:27.800> the<00:02:27.920> Android 00:02:28.229 --> 00:02:28.239 align:start position:0% to different uh Android to the Android 00:02:28.239 --> 00:02:29.990 align:start position:0% to different uh Android to the Android ecosystem<00:02:29.200> with<00:02:29.319> the<00:02:29.400> benefit<00:02:29.680> of<00:02:29.920> the 00:02:29.990 --> 00:02:30.000 align:start position:0% ecosystem with the benefit of the 00:02:30.000 --> 00:02:31.710 align:start position:0% ecosystem with the benefit of the inherent<00:02:30.360> modularity<00:02:30.840> of<00:02:31.000> java<00:02:31.280> but<00:02:31.400> also<00:02:31.560> its 00:02:31.710 --> 00:02:31.720 align:start position:0% inherent modularity of java but also its 00:02:31.720 --> 00:02:33.470 align:start position:0% inherent modularity of java but also its native<00:02:32.040> support<00:02:32.840> and<00:02:32.959> so<00:02:33.080> it's<00:02:33.160> a<00:02:33.280> very 00:02:33.470 --> 00:02:33.480 align:start position:0% native support and so it's a very 00:02:33.480 --> 00:02:35.750 align:start position:0% native support and so it's a very realistic<00:02:33.920> goal<00:02:34.080> to<00:02:34.280> expect<00:02:34.519> that<00:02:34.680> sble<00:02:35.080> could 00:02:35.750 --> 00:02:35.760 align:start position:0% realistic goal to expect that sble could 00:02:35.760 --> 00:02:37.990 align:start position:0% realistic goal to expect that sble could simply<00:02:36.000> be<00:02:36.160> built<00:02:36.519> on<00:02:36.720> top<00:02:36.879> of<00:02:37.280> as<00:02:37.360> a<00:02:37.519> library 00:02:37.990 --> 00:02:38.000 align:start position:0% simply be built on top of as a library 00:02:38.000 --> 00:02:39.550 align:start position:0% simply be built on top of as a library for<00:02:38.239> other<00:02:38.519> mobile<00:02:39.000> or<00:02:39.159> resource 00:02:39.550 --> 00:02:39.560 align:start position:0% for other mobile or resource 00:02:39.560 --> 00:02:41.990 align:start position:0% for other mobile or resource constrainted 00:02:41.990 --> 00:02:42.000 align:start position:0% constrainted 00:02:42.000 --> 00:02:45.149 align:start position:0% constrainted applications<00:02:43.000> and<00:02:43.200> so<00:02:43.879> moving<00:02:44.159> into<00:02:44.879> where 00:02:45.149 --> 00:02:45.159 align:start position:0% applications and so moving into where 00:02:45.159 --> 00:02:49.190 align:start position:0% applications and so moving into where Samba<00:02:45.680> is<00:02:45.920> at<00:02:46.280> right<00:02:46.440> now<00:02:47.200> um<00:02:48.200> my<00:02:48.599> my<00:02:48.760> initial 00:02:49.190 --> 00:02:49.200 align:start position:0% Samba is at right now um my my initial 00:02:49.200 --> 00:02:52.229 align:start position:0% Samba is at right now um my my initial proposal<00:02:50.000> at<00:02:50.120> the<00:02:50.640> beginning<00:02:51.640> was<00:02:51.800> extremely 00:02:52.229 --> 00:02:52.239 align:start position:0% proposal at the beginning was extremely 00:02:52.239 --> 00:02:54.509 align:start position:0% proposal at the beginning was extremely ambitious<00:02:52.640> and<00:02:52.760> I<00:02:52.879> admit<00:02:53.159> that<00:02:53.480> obviously<00:02:53.879> not 00:02:54.509 --> 00:02:54.519 align:start position:0% ambitious and I admit that obviously not 00:02:54.519 --> 00:02:56.869 align:start position:0% ambitious and I admit that obviously not quite<00:02:54.800> where<00:02:55.000> we<00:02:55.280> got<00:02:55.480> to<00:02:55.800> but<00:02:56.280> essentially 00:02:56.869 --> 00:02:56.879 align:start position:0% quite where we got to but essentially 00:02:56.879 --> 00:02:57.790 align:start position:0% quite where we got to but essentially this 00:02:57.790 --> 00:02:57.800 align:start position:0% this 00:02:57.800 --> 00:03:00.670 align:start position:0% this proposal<00:02:58.800> is<00:02:59.200> a<00:02:59.319> model<00:02:59.599> of<00:02:59.879> where<00:03:00.519> will 00:03:00.670 --> 00:03:00.680 align:start position:0% proposal is a model of where will 00:03:00.680 --> 00:03:02.869 align:start position:0% proposal is a model of where will be<00:03:00.879> at<00:03:01.040> one<00:03:01.280> point<00:03:01.720> and<00:03:01.840> so<00:03:02.640> all 00:03:02.869 --> 00:03:02.879 align:start position:0% be at one point and so all 00:03:02.879 --> 00:03:05.149 align:start position:0% be at one point and so all Communications<00:03:03.519> in<00:03:03.920> related<00:03:04.239> infrastructure 00:03:05.149 --> 00:03:05.159 align:start position:0% Communications in related infrastructure 00:03:05.159 --> 00:03:08.030 align:start position:0% Communications in related infrastructure uh<00:03:05.319> including<00:03:06.040> um<00:03:06.319> dis5<00:03:06.920> portal<00:03:07.200> wire<00:03:07.360> and<00:03:07.440> UTP 00:03:08.030 --> 00:03:08.040 align:start position:0% uh including um dis5 portal wire and UTP 00:03:08.040 --> 00:03:09.710 align:start position:0% uh including um dis5 portal wire and UTP are<00:03:08.280> eventually<00:03:08.599> going<00:03:08.760> to<00:03:08.840> be<00:03:08.959> implemented 00:03:09.710 --> 00:03:09.720 align:start position:0% are eventually going to be implemented 00:03:09.720 --> 00:03:11.350 align:start position:0% are eventually going to be implemented uh<00:03:09.920> mainly<00:03:10.200> UTP<00:03:10.640> at<00:03:10.720> this<00:03:10.840> point<00:03:11.040> is<00:03:11.159> the<00:03:11.239> one 00:03:11.350 --> 00:03:11.360 align:start position:0% uh mainly UTP at this point is the one 00:03:11.360 --> 00:03:13.869 align:start position:0% uh mainly UTP at this point is the one that<00:03:11.440> we're<00:03:11.599> working<00:03:11.840> on<00:03:12.599> um<00:03:13.360> and<00:03:13.480> then<00:03:13.680> to 00:03:13.869 --> 00:03:13.879 align:start position:0% that we're working on um and then to 00:03:13.879 --> 00:03:16.030 align:start position:0% that we're working on um and then to have<00:03:14.000> a<00:03:14.120> fully<00:03:14.440> functioning<00:03:14.840> history<00:03:15.200> Network 00:03:16.030 --> 00:03:16.040 align:start position:0% have a fully functioning history Network 00:03:16.040 --> 00:03:17.910 align:start position:0% have a fully functioning history Network as<00:03:16.159> well<00:03:16.280> as<00:03:16.400> full<00:03:16.599> function<00:03:16.879> of<00:03:17.000> State<00:03:17.239> Beacon 00:03:17.910 --> 00:03:17.920 align:start position:0% as well as full function of State Beacon 00:03:17.920 --> 00:03:19.309 align:start position:0% as well as full function of State Beacon uh<00:03:18.040> State<00:03:18.239> and<00:03:18.319> Beacon<00:03:18.680> to<00:03:18.840> the<00:03:18.959> point<00:03:19.159> of 00:03:19.309 --> 00:03:19.319 align:start position:0% uh State and Beacon to the point of 00:03:19.319 --> 00:03:21.309 align:start position:0% uh State and Beacon to the point of present<00:03:19.599> portal<00:03:19.920> development<00:03:20.920> as<00:03:21.040> well<00:03:21.159> as 00:03:21.309 --> 00:03:21.319 align:start position:0% present portal development as well as 00:03:21.319 --> 00:03:22.830 align:start position:0% present portal development as well as full<00:03:21.560> interoperability<00:03:22.280> with<00:03:22.400> other<00:03:22.599> Port 00:03:22.830 --> 00:03:22.840 align:start position:0% full interoperability with other Port 00:03:22.840 --> 00:03:25.910 align:start position:0% full interoperability with other Port portal<00:03:23.120> clients<00:03:24.080> and 00:03:25.910 --> 00:03:25.920 align:start position:0% portal clients and 00:03:25.920 --> 00:03:28.470 align:start position:0% portal clients and so<00:03:26.920> uh<00:03:27.040> our<00:03:27.239> updated<00:03:27.599> goal<00:03:27.840> range<00:03:28.159> of<00:03:28.280> course 00:03:28.470 --> 00:03:28.480 align:start position:0% so uh our updated goal range of course 00:03:28.480 --> 00:03:30.309 align:start position:0% so uh our updated goal range of course for<00:03:28.720> the<00:03:28.879> the<00:03:28.959> scope<00:03:29.200> of<00:03:29.319> EPF 00:03:30.309 --> 00:03:30.319 align:start position:0% for the the scope of EPF 00:03:30.319 --> 00:03:32.229 align:start position:0% for the the scope of EPF at<00:03:30.599> up<00:03:30.680> to<00:03:30.840> this<00:03:31.000> point<00:03:31.400> just<00:03:31.519> pertains<00:03:31.879> to 00:03:32.229 --> 00:03:32.239 align:start position:0% at up to this point just pertains to 00:03:32.239 --> 00:03:33.910 align:start position:0% at up to this point just pertains to what<00:03:32.360> we<00:03:32.480> figured<00:03:32.879> would<00:03:33.000> be<00:03:33.200> reasonable<00:03:33.760> in 00:03:33.910 --> 00:03:33.920 align:start position:0% what we figured would be reasonable in 00:03:33.920 --> 00:03:35.910 align:start position:0% what we figured would be reasonable in this<00:03:34.120> time<00:03:34.360> scope<00:03:34.760> but<00:03:35.280> essentially<00:03:35.720> that's 00:03:35.910 --> 00:03:35.920 align:start position:0% this time scope but essentially that's 00:03:35.920 --> 00:03:38.429 align:start position:0% this time scope but essentially that's to<00:03:36.280> get<00:03:37.280> to<00:03:37.480> have<00:03:37.680> had<00:03:37.920> a<00:03:38.120> primary 00:03:38.429 --> 00:03:38.439 align:start position:0% to get to have had a primary 00:03:38.439 --> 00:03:39.990 align:start position:0% to get to have had a primary communication<00:03:38.879> infrastructure<00:03:39.400> including<00:03:39.720> a 00:03:39.990 --> 00:03:40.000 align:start position:0% communication infrastructure including a 00:03:40.000 --> 00:03:42.390 align:start position:0% communication infrastructure including a Discovery<00:03:40.200> V5<00:03:40.640> and<00:03:40.760> then<00:03:40.879> the<00:03:41.000> portal<00:03:41.360> wire<00:03:42.239> um 00:03:42.390 --> 00:03:42.400 align:start position:0% Discovery V5 and then the portal wire um 00:03:42.400 --> 00:03:44.949 align:start position:0% Discovery V5 and then the portal wire um unfortunately<00:03:43.080> UTP<00:03:43.720> was<00:03:44.040> some<00:03:44.239> a<00:03:44.360> big<00:03:44.519> setback 00:03:44.949 --> 00:03:44.959 align:start position:0% unfortunately UTP was some a big setback 00:03:44.959 --> 00:03:47.949 align:start position:0% unfortunately UTP was some a big setback in<00:03:45.080> the<00:03:45.280> sense<00:03:45.959> that<00:03:46.959> um<00:03:47.480> there<00:03:47.599> is<00:03:47.760> no 00:03:47.949 --> 00:03:47.959 align:start position:0% in the sense that um there is no 00:03:47.959 --> 00:03:49.470 align:start position:0% in the sense that um there is no generalized<00:03:48.439> UTP<00:03:48.879> library<00:03:49.239> and<00:03:49.319> so 00:03:49.470 --> 00:03:49.480 align:start position:0% generalized UTP library and so 00:03:49.480 --> 00:03:50.910 align:start position:0% generalized UTP library and so unfortunately<00:03:49.840> we're<00:03:50.159> to<00:03:50.239> piggy<00:03:50.519> back<00:03:50.640> off<00:03:50.760> of 00:03:50.910 --> 00:03:50.920 align:start position:0% unfortunately we're to piggy back off of 00:03:50.920 --> 00:03:52.470 align:start position:0% unfortunately we're to piggy back off of anything<00:03:51.159> like<00:03:51.319> that<00:03:51.439> and<00:03:51.799> will<00:03:52.120> have<00:03:52.200> to<00:03:52.319> be 00:03:52.470 --> 00:03:52.480 align:start position:0% anything like that and will have to be 00:03:52.480 --> 00:03:54.149 align:start position:0% anything like that and will have to be something<00:03:52.720> that<00:03:52.920> we<00:03:53.040> sit<00:03:53.280> down<00:03:53.480> and<00:03:53.920> do 00:03:54.149 --> 00:03:54.159 align:start position:0% something that we sit down and do 00:03:54.159 --> 00:03:57.110 align:start position:0% something that we sit down and do ourselves<00:03:55.239> um<00:03:56.239> and<00:03:56.360> then<00:03:56.680> uh<00:03:56.760> to<00:03:56.959> have 00:03:57.110 --> 00:03:57.120 align:start position:0% ourselves um and then uh to have 00:03:57.120 --> 00:03:58.350 align:start position:0% ourselves um and then uh to have infrastructure<00:03:57.640> in<00:03:57.760> place<00:03:57.920> where<00:03:58.159> his 00:03:58.350 --> 00:03:58.360 align:start position:0% infrastructure in place where his 00:03:58.360 --> 00:04:01.270 align:start position:0% infrastructure in place where his history<00:03:58.640> Network<00:03:58.959> function<00:03:59.959> and<00:04:00.120> so<00:04:01.120> then 00:04:01.270 --> 00:04:01.280 align:start position:0% history Network function and so then 00:04:01.280 --> 00:04:02.509 align:start position:0% history Network function and so then moving<00:04:01.560> on<00:04:01.879> once<00:04:02.079> we<00:04:02.239> have<00:04:02.360> that 00:04:02.509 --> 00:04:02.519 align:start position:0% moving on once we have that 00:04:02.519 --> 00:04:04.270 align:start position:0% moving on once we have that infrastructure<00:04:03.040> and<00:04:03.159> that<00:04:03.319> we<00:04:03.480> have<00:04:03.840> is<00:04:04.000> to 00:04:04.270 --> 00:04:04.280 align:start position:0% infrastructure and that we have is to 00:04:04.280 --> 00:04:06.350 align:start position:0% infrastructure and that we have is to have<00:04:04.560> generalized<00:04:05.200> internal<00:04:05.599> testing<00:04:06.159> uh<00:04:06.280> we 00:04:06.350 --> 00:04:06.360 align:start position:0% have generalized internal testing uh we 00:04:06.360 --> 00:04:08.069 align:start position:0% have generalized internal testing uh we wanted<00:04:06.599> to<00:04:06.799> have<00:04:07.120> SSD<00:04:07.519> sterilization 00:04:08.069 --> 00:04:08.079 align:start position:0% wanted to have SSD sterilization 00:04:08.079 --> 00:04:10.830 align:start position:0% wanted to have SSD sterilization distalization<00:04:09.079> exposed<00:04:09.480> API<00:04:09.840> infrastructure 00:04:10.830 --> 00:04:10.840 align:start position:0% distalization exposed API infrastructure 00:04:10.840 --> 00:04:13.229 align:start position:0% distalization exposed API infrastructure metrics<00:04:11.799> and<00:04:11.920> the<00:04:12.040> only<00:04:12.239> thing<00:04:12.360> on<00:04:12.480> the<00:04:12.640> list 00:04:13.229 --> 00:04:13.239 align:start position:0% metrics and the only thing on the list 00:04:13.239 --> 00:04:15.630 align:start position:0% metrics and the only thing on the list that<00:04:13.400> we<00:04:13.720> weren't<00:04:14.200> quite<00:04:14.400> able<00:04:14.640> to<00:04:15.000> achieve<00:04:15.480> in 00:04:15.630 --> 00:04:15.640 align:start position:0% that we weren't quite able to achieve in 00:04:15.640 --> 00:04:18.870 align:start position:0% that we weren't quite able to achieve in this<00:04:15.959> goal<00:04:16.199> range<00:04:16.519> is<00:04:16.720> Portal<00:04:17.040> Hive<00:04:17.320> testing 00:04:18.870 --> 00:04:18.880 align:start position:0% this goal range is Portal Hive testing 00:04:18.880 --> 00:04:21.870 align:start position:0% this goal range is Portal Hive testing unfortunately<00:04:19.880> just<00:04:20.280> given<00:04:20.519> the<00:04:20.680> scope<00:04:21.600> is 00:04:21.870 --> 00:04:21.880 align:start position:0% unfortunately just given the scope is 00:04:21.880 --> 00:04:23.629 align:start position:0% unfortunately just given the scope is we're<00:04:22.160> very<00:04:22.400> close<00:04:22.639> to<00:04:22.800> having<00:04:23.040> had<00:04:23.199> it<00:04:23.400> a<00:04:23.520> lot 00:04:23.629 --> 00:04:23.639 align:start position:0% we're very close to having had it a lot 00:04:23.639 --> 00:04:24.790 align:start position:0% we're very close to having had it a lot of<00:04:23.759> it<00:04:23.880> was<00:04:24.040> just<00:04:24.199> have<00:04:24.360> putting<00:04:24.600> little 00:04:24.790 --> 00:04:24.800 align:start position:0% of it was just have putting little 00:04:24.800 --> 00:04:26.390 align:start position:0% of it was just have putting little pieces<00:04:25.199> together<00:04:25.440> to<00:04:25.639> to<00:04:25.840> test<00:04:26.040> it<00:04:26.199> but<00:04:26.280> we 00:04:26.390 --> 00:04:26.400 align:start position:0% pieces together to to test it but we 00:04:26.400 --> 00:04:28.710 align:start position:0% pieces together to to test it but we figured<00:04:27.160> it'd<00:04:27.320> be<00:04:27.520> better<00:04:28.000> uh<00:04:28.080> to<00:04:28.280> just<00:04:28.520> add 00:04:28.710 --> 00:04:28.720 align:start position:0% figured it'd be better uh to just add 00:04:28.720 --> 00:04:30.950 align:start position:0% figured it'd be better uh to just add more<00:04:28.960> functionality<00:04:29.479> before<00:04:29.880> we<00:04:30.199> go<00:04:30.560> and<00:04:30.800> add 00:04:30.950 --> 00:04:30.960 align:start position:0% more functionality before we go and add 00:04:30.960 --> 00:04:32.310 align:start position:0% more functionality before we go and add some<00:04:31.160> just<00:04:31.320> small<00:04:31.520> pieces<00:04:31.759> of<00:04:31.880> testing<00:04:32.199> as 00:04:32.310 --> 00:04:32.320 align:start position:0% some just small pieces of testing as 00:04:32.320 --> 00:04:34.350 align:start position:0% some just small pieces of testing as opposed<00:04:32.560> to<00:04:32.759> now<00:04:32.919> we<00:04:33.039> can<00:04:33.600> as<00:04:33.720> we<00:04:33.840> go<00:04:33.960> forward 00:04:34.350 --> 00:04:34.360 align:start position:0% opposed to now we can as we go forward 00:04:34.360 --> 00:04:37.749 align:start position:0% opposed to now we can as we go forward add<00:04:34.520> a<00:04:34.639> lot<00:04:34.880> more<00:04:35.280> uh<00:04:35.440> tests<00:04:36.000> and<00:04:36.400> then<00:04:37.320> um 00:04:37.749 --> 00:04:37.759 align:start position:0% add a lot more uh tests and then um 00:04:37.759 --> 00:04:39.670 align:start position:0% add a lot more uh tests and then um prove<00:04:38.199> that<00:04:38.400> we<00:04:38.560> can<00:04:38.800> then<00:04:39.000> interact<00:04:39.520> with 00:04:39.670 --> 00:04:39.680 align:start position:0% prove that we can then interact with 00:04:39.680 --> 00:04:41.870 align:start position:0% prove that we can then interact with other 00:04:41.870 --> 00:04:41.880 align:start position:0% other 00:04:41.880 --> 00:04:44.870 align:start position:0% other clients<00:04:42.880> and<00:04:43.039> so<00:04:43.600> this<00:04:43.800> is<00:04:43.960> a<00:04:44.120> general<00:04:44.440> diagram 00:04:44.870 --> 00:04:44.880 align:start position:0% clients and so this is a general diagram 00:04:44.880 --> 00:04:48.110 align:start position:0% clients and so this is a general diagram of<00:04:45.360> kind<00:04:45.479> of<00:04:45.680> how<00:04:45.840> Samba<00:04:46.360> functions<00:04:47.039> and<00:04:47.960> the 00:04:48.110 --> 00:04:48.120 align:start position:0% of kind of how Samba functions and the 00:04:48.120 --> 00:04:50.110 align:start position:0% of kind of how Samba functions and the the<00:04:48.199> layout<00:04:48.520> of<00:04:48.639> Samba<00:04:49.160> and<00:04:49.360> the<00:04:49.520> big<00:04:49.759> two 00:04:50.110 --> 00:04:50.120 align:start position:0% the layout of Samba and the big two 00:04:50.120 --> 00:04:52.670 align:start position:0% the layout of Samba and the big two pieces<00:04:50.520> on<00:04:50.639> the<00:04:50.800> bottom<00:04:51.199> here<00:04:51.479> are<00:04:51.720> the<00:04:51.880> ones 00:04:52.670 --> 00:04:52.680 align:start position:0% pieces on the bottom here are the ones 00:04:52.680 --> 00:04:55.070 align:start position:0% pieces on the bottom here are the ones that<00:04:53.680> really<00:04:53.919> took<00:04:54.199> the<00:04:54.400> the<00:04:54.560> the<00:04:54.680> brunt<00:04:54.919> of 00:04:55.070 --> 00:04:55.080 align:start position:0% that really took the the the brunt of 00:04:55.080 --> 00:04:58.270 align:start position:0% that really took the the the brunt of the<00:04:55.240> time<00:04:55.720> is<00:04:55.960> getting<00:04:56.400> all<00:04:56.639> the<00:04:56.919> the<00:04:57.199> uh<00:04:57.759> base 00:04:58.270 --> 00:04:58.280 align:start position:0% the time is getting all the the uh base 00:04:58.280 --> 00:05:00.909 align:start position:0% the time is getting all the the uh base protocol<00:04:59.120> um<00:04:59.720> communication<00:05:00.320> systems<00:05:00.680> in 00:05:00.909 --> 00:05:00.919 align:start position:0% protocol um communication systems in 00:05:00.919 --> 00:05:03.430 align:start position:0% protocol um communication systems in place<00:05:01.720> and<00:05:01.840> so<00:05:02.120> that<00:05:02.360> includes<00:05:02.800> like<00:05:02.919> inbound 00:05:03.430 --> 00:05:03.440 align:start position:0% place and so that includes like inbound 00:05:03.440 --> 00:05:05.870 align:start position:0% place and so that includes like inbound outbound<00:05:04.039> communication<00:05:05.039> um<00:05:05.520> whether<00:05:05.720> that 00:05:05.870 --> 00:05:05.880 align:start position:0% outbound communication um whether that 00:05:05.880 --> 00:05:07.390 align:start position:0% outbound communication um whether that be<00:05:06.080> coming<00:05:06.360> from<00:05:06.560> a<00:05:06.759> client<00:05:07.080> there's<00:05:07.240> a 00:05:07.390 --> 00:05:07.400 align:start position:0% be coming from a client there's a 00:05:07.400 --> 00:05:09.550 align:start position:0% be coming from a client there's a different<00:05:07.840> way<00:05:08.000> to<00:05:08.199> handle<00:05:08.880> requests<00:05:09.320> coming 00:05:09.550 --> 00:05:09.560 align:start position:0% different way to handle requests coming 00:05:09.560 --> 00:05:11.590 align:start position:0% different way to handle requests coming in<00:05:09.800> as<00:05:09.919> opposed<00:05:10.240> to<00:05:10.360> sending<00:05:10.639> out<00:05:10.880> requests<00:05:11.240> or 00:05:11.590 --> 00:05:11.600 align:start position:0% in as opposed to sending out requests or 00:05:11.600 --> 00:05:13.550 align:start position:0% in as opposed to sending out requests or then<00:05:12.039> receiving<00:05:12.240> inbound<00:05:12.680> requests<00:05:13.199> or<00:05:13.360> or 00:05:13.550 --> 00:05:13.560 align:start position:0% then receiving inbound requests or or 00:05:13.560 --> 00:05:17.510 align:start position:0% then receiving inbound requests or or responses<00:05:14.039> and<00:05:14.280> vice<00:05:14.560> versa<00:05:16.039> um<00:05:17.039> but<00:05:17.240> then<00:05:17.400> of 00:05:17.510 --> 00:05:17.520 align:start position:0% responses and vice versa um but then of 00:05:17.520 --> 00:05:19.629 align:start position:0% responses and vice versa um but then of course<00:05:17.759> there's<00:05:18.039> other<00:05:18.639> uh<00:05:18.840> pieces<00:05:19.120> of<00:05:19.280> puzzle 00:05:19.629 --> 00:05:19.639 align:start position:0% course there's other uh pieces of puzzle 00:05:19.639 --> 00:05:21.710 align:start position:0% course there's other uh pieces of puzzle such<00:05:19.800> as<00:05:20.000> the<00:05:20.160> API<00:05:20.720> which<00:05:21.000> Melton<00:05:21.440> had<00:05:21.560> done 00:05:21.710 --> 00:05:21.720 align:start position:0% such as the API which Melton had done 00:05:21.720 --> 00:05:24.110 align:start position:0% such as the API which Melton had done and<00:05:21.880> exposed<00:05:22.199> an<00:05:22.360> API<00:05:22.800> so<00:05:22.960> we're<00:05:23.800> very<00:05:23.960> well 00:05:24.110 --> 00:05:24.120 align:start position:0% and exposed an API so we're very well 00:05:24.120 --> 00:05:26.110 align:start position:0% and exposed an API so we're very well set<00:05:24.360> up<00:05:24.520> to<00:05:24.720> then<00:05:24.960> start<00:05:25.360> actually<00:05:25.560> serving 00:05:26.110 --> 00:05:26.120 align:start position:0% set up to then start actually serving 00:05:26.120 --> 00:05:28.270 align:start position:0% set up to then start actually serving different<00:05:26.400> pieces<00:05:26.960> such<00:05:27.120> as<00:05:27.280> the<00:05:27.440> uh<00:05:27.560> disb<00:05:28.039> 5 00:05:28.270 --> 00:05:28.280 align:start position:0% different pieces such as the uh disb 5 00:05:28.280 --> 00:05:32.909 align:start position:0% different pieces such as the uh disb 5 and<00:05:28.520> history<00:05:29.319> portal<00:05:29.759> history<00:05:30.280> uh<00:05:30.720> apis<00:05:31.919> um 00:05:32.909 --> 00:05:32.919 align:start position:0% and history portal history uh apis um 00:05:32.919 --> 00:05:33.870 align:start position:0% and history portal history uh apis um and 00:05:33.870 --> 00:05:33.880 align:start position:0% and 00:05:33.880 --> 00:05:36.749 align:start position:0% and so<00:05:34.880> moving<00:05:35.319> forward<00:05:35.800> in<00:05:35.960> the<00:05:36.199> uh<00:05:36.360> in<00:05:36.440> the 00:05:36.749 --> 00:05:36.759 align:start position:0% so moving forward in the uh in the 00:05:36.759 --> 00:05:39.870 align:start position:0% so moving forward in the uh in the project<00:05:37.560> uh<00:05:38.080> the<00:05:38.160> future<00:05:38.440> of<00:05:38.560> Soma<00:05:39.400> obviously 00:05:39.870 --> 00:05:39.880 align:start position:0% project uh the future of Soma obviously 00:05:39.880 --> 00:05:41.749 align:start position:0% project uh the future of Soma obviously the<00:05:40.039> development<00:05:40.440> of<00:05:40.560> Soma<00:05:41.039> does<00:05:41.199> not<00:05:41.440> stop 00:05:41.749 --> 00:05:41.759 align:start position:0% the development of Soma does not stop 00:05:41.759 --> 00:05:44.230 align:start position:0% the development of Soma does not stop with<00:05:41.919> EPF<00:05:42.840> uh<00:05:42.960> the<00:05:43.120> project<00:05:43.560> is<00:05:43.759> in<00:05:43.880> a<00:05:44.039> very 00:05:44.230 --> 00:05:44.240 align:start position:0% with EPF uh the project is in a very 00:05:44.240 --> 00:05:46.070 align:start position:0% with EPF uh the project is in a very good<00:05:44.440> place<00:05:44.680> infrastructure<00:05:45.280> wise<00:05:45.560> and<00:05:45.919> has 00:05:46.070 --> 00:05:46.080 align:start position:0% good place infrastructure wise and has 00:05:46.080 --> 00:05:49.070 align:start position:0% good place infrastructure wise and has achieved<00:05:46.400> a<00:05:46.520> lot<00:05:46.600> of<00:05:47.039> Milestones<00:05:48.039> um<00:05:48.720> in<00:05:48.840> terms 00:05:49.070 --> 00:05:49.080 align:start position:0% achieved a lot of Milestones um in terms 00:05:49.080 --> 00:05:51.270 align:start position:0% achieved a lot of Milestones um in terms of<00:05:49.240> functionality<00:05:49.960> like<00:05:50.639> at<00:05:50.840> this<00:05:51.000> point 00:05:51.270 --> 00:05:51.280 align:start position:0% of functionality like at this point 00:05:51.280 --> 00:05:53.350 align:start position:0% of functionality like at this point currently<00:05:51.919> we<00:05:52.160> are<00:05:52.400> able<00:05:52.639> to<00:05:52.919> send<00:05:53.240> and 00:05:53.350 --> 00:05:53.360 align:start position:0% currently we are able to send and 00:05:53.360 --> 00:05:54.870 align:start position:0% currently we are able to send and receive<00:05:53.800> all<00:05:54.000> different<00:05:54.240> types<00:05:54.600> all<00:05:54.759> the 00:05:54.870 --> 00:05:54.880 align:start position:0% receive all different types all the 00:05:54.880 --> 00:05:57.110 align:start position:0% receive all different types all the available<00:05:55.360> uh<00:05:55.479> portal<00:05:55.759> wire<00:05:56.039> packets<00:05:56.759> uh<00:05:56.880> to 00:05:57.110 --> 00:05:57.120 align:start position:0% available uh portal wire packets uh to 00:05:57.120 --> 00:06:00.110 align:start position:0% available uh portal wire packets uh to all<00:05:57.280> the<00:05:57.360> other<00:05:57.560> portal<00:05:58.000> clients<00:05:59.000> um<00:05:59.759> and<00:05:59.960> in 00:06:00.110 --> 00:06:00.120 align:start position:0% all the other portal clients um and in 00:06:00.120 --> 00:06:02.270 align:start position:0% all the other portal clients um and in terms<00:06:00.440> of<00:06:01.080> certain<00:06:01.440> packet<00:06:01.759> types<00:06:02.000> such<00:06:02.160> as 00:06:02.270 --> 00:06:02.280 align:start position:0% terms of certain packet types such as 00:06:02.280 --> 00:06:04.390 align:start position:0% terms of certain packet types such as ping<00:06:02.600> pong<00:06:02.880> obviously<00:06:03.440> work<00:06:03.720> well<00:06:04.000> and<00:06:04.120> then 00:06:04.390 --> 00:06:04.400 align:start position:0% ping pong obviously work well and then 00:06:04.400 --> 00:06:06.830 align:start position:0% ping pong obviously work well and then uh<00:06:04.520> we<00:06:04.639> are<00:06:04.759> able<00:06:04.919> to<00:06:05.120> now<00:06:05.759> up<00:06:05.919> to<00:06:06.120> this<00:06:06.280> point 00:06:06.830 --> 00:06:06.840 align:start position:0% uh we are able to now up to this point 00:06:06.840 --> 00:06:08.909 align:start position:0% uh we are able to now up to this point uh<00:06:07.199> almost<00:06:07.440> full<00:06:07.680> functionality<00:06:08.199> on<00:06:08.479> just<00:06:08.800> uh 00:06:08.909 --> 00:06:08.919 align:start position:0% uh almost full functionality on just uh 00:06:08.919 --> 00:06:10.550 align:start position:0% uh almost full functionality on just uh sending<00:06:09.240> and<00:06:09.560> receiving<00:06:09.759> nodes<00:06:10.080> in<00:06:10.199> terms<00:06:10.400> of 00:06:10.550 --> 00:06:10.560 align:start position:0% sending and receiving nodes in terms of 00:06:10.560 --> 00:06:12.469 align:start position:0% sending and receiving nodes in terms of building<00:06:10.880> our 00:06:12.469 --> 00:06:12.479 align:start position:0% building our 00:06:12.479 --> 00:06:16.230 align:start position:0% building our um<00:06:13.479> uh<00:06:13.680> our<00:06:14.039> our<00:06:14.360> uh<00:06:14.560> peers<00:06:15.160> and 00:06:16.230 --> 00:06:16.240 align:start position:0% um uh our our uh peers and 00:06:16.240 --> 00:06:18.790 align:start position:0% um uh our our uh peers and so<00:06:17.240> um<00:06:17.479> moving<00:06:17.800> forward<00:06:18.120> then<00:06:18.280> the<00:06:18.400> continued 00:06:18.790 --> 00:06:18.800 align:start position:0% so um moving forward then the continued 00:06:18.800 --> 00:06:20.510 align:start position:0% so um moving forward then the continued development<00:06:19.240> will<00:06:19.520> eventually<00:06:19.919> bring<00:06:20.120> us<00:06:20.319> up 00:06:20.510 --> 00:06:20.520 align:start position:0% development will eventually bring us up 00:06:20.520 --> 00:06:23.189 align:start position:0% development will eventually bring us up to<00:06:20.680> dat<00:06:21.240> with<00:06:21.560> the<00:06:21.639> other<00:06:21.840> portal<00:06:22.199> clients<00:06:22.759> and 00:06:23.189 --> 00:06:23.199 align:start position:0% to dat with the other portal clients and 00:06:23.199 --> 00:06:26.430 align:start position:0% to dat with the other portal clients and so<00:06:24.199> that<00:06:24.400> that<00:06:24.520> is<00:06:24.919> to<00:06:25.080> me<00:06:25.280> also<00:06:25.520> an<00:06:25.680> exciting 00:06:26.430 --> 00:06:26.440 align:start position:0% so that that is to me also an exciting 00:06:26.440 --> 00:06:28.909 align:start position:0% so that that is to me also an exciting uh<00:06:27.199> part<00:06:27.520> of<00:06:27.720> being<00:06:27.960> a<00:06:28.080> part<00:06:28.240> of<00:06:28.360> portal<00:06:28.720> is 00:06:28.909 --> 00:06:28.919 align:start position:0% uh part of being a part of portal is 00:06:28.919 --> 00:06:30.510 align:start position:0% uh part of being a part of portal is that 00:06:30.510 --> 00:06:30.520 align:start position:0% that 00:06:30.520 --> 00:06:34.629 align:start position:0% that um<00:06:31.520> for<00:06:31.880> for<00:06:32.120> the<00:06:32.319> development<00:06:32.880> of<00:06:33.400> Samba<00:06:34.400> we 00:06:34.629 --> 00:06:34.639 align:start position:0% um for for the development of Samba we 00:06:34.639 --> 00:06:37.830 align:start position:0% um for for the development of Samba we have<00:06:35.280> uh<00:06:35.440> EPF<00:06:36.319> but<00:06:36.479> then<00:06:36.720> also<00:06:37.560> there<00:06:37.680> after 00:06:37.830 --> 00:06:37.840 align:start position:0% have uh EPF but then also there after 00:06:37.840 --> 00:06:39.749 align:start position:0% have uh EPF but then also there after moving<00:06:38.080> after<00:06:38.360> EPF<00:06:38.840> there's<00:06:39.000> a<00:06:39.240> portion<00:06:39.560> of 00:06:39.749 --> 00:06:39.759 align:start position:0% moving after EPF there's a portion of 00:06:39.759 --> 00:06:41.749 align:start position:0% moving after EPF there's a portion of getting<00:06:40.039> fully<00:06:40.400> caught<00:06:40.680> up<00:06:40.800> to<00:06:40.919> other<00:06:41.120> portal 00:06:41.749 --> 00:06:41.759 align:start position:0% getting fully caught up to other portal 00:06:41.759 --> 00:06:45.710 align:start position:0% getting fully caught up to other portal clients<00:06:42.759> um<00:06:42.960> but<00:06:43.160> then<00:06:43.680> in<00:06:43.960> in<00:06:44.039> terms<00:06:44.560> of<00:06:45.560> I 00:06:45.710 --> 00:06:45.720 align:start position:0% clients um but then in in terms of I 00:06:45.720 --> 00:06:47.749 align:start position:0% clients um but then in in terms of I guess<00:06:45.919> my<00:06:46.160> experience<00:06:47.120> it's<00:06:47.280> also<00:06:47.520> very 00:06:47.749 --> 00:06:47.759 align:start position:0% guess my experience it's also very 00:06:47.759 --> 00:06:49.790 align:start position:0% guess my experience it's also very exciting<00:06:48.120> in<00:06:48.280> that<00:06:49.000> once<00:06:49.199> we<00:06:49.360> get<00:06:49.479> to<00:06:49.639> that 00:06:49.790 --> 00:06:49.800 align:start position:0% exciting in that once we get to that 00:06:49.800 --> 00:06:51.830 align:start position:0% exciting in that once we get to that point<00:06:50.120> it's<00:06:50.240> a<00:06:50.599> entirely<00:06:51.000> different 00:06:51.830 --> 00:06:51.840 align:start position:0% point it's a entirely different 00:06:51.840 --> 00:06:53.230 align:start position:0% point it's a entirely different development<00:06:52.319> Paradigm<00:06:52.720> where<00:06:52.880> instead<00:06:53.080> of 00:06:53.230 --> 00:06:53.240 align:start position:0% development Paradigm where instead of 00:06:53.240 --> 00:06:54.390 align:start position:0% development Paradigm where instead of catching<00:06:53.560> up<00:06:53.680> and<00:06:53.800> following<00:06:54.160> different 00:06:54.390 --> 00:06:54.400 align:start position:0% catching up and following different 00:06:54.400 --> 00:06:56.710 align:start position:0% catching up and following different specs<00:06:54.759> that's<00:06:55.000> now<00:06:55.639> actively<00:06:56.120> participating 00:06:56.710 --> 00:06:56.720 align:start position:0% specs that's now actively participating 00:06:56.720 --> 00:07:00.110 align:start position:0% specs that's now actively participating in<00:06:57.160> development<00:06:58.160> um<00:06:58.960> and<00:06:59.120> so 00:07:00.110 --> 00:07:00.120 align:start position:0% in development um and so 00:07:00.120 --> 00:07:02.230 align:start position:0% in development um and so th<00:07:00.319> this<00:07:00.520> development<00:07:01.160> is<00:07:01.479> much<00:07:01.680> more 00:07:02.230 --> 00:07:02.240 align:start position:0% th this development is much more 00:07:02.240 --> 00:07:03.390 align:start position:0% th this development is much more something<00:07:02.479> that<00:07:02.560> I<00:07:02.680> will<00:07:02.800> have<00:07:02.919> to<00:07:03.000> learn<00:07:03.280> as 00:07:03.390 --> 00:07:03.400 align:start position:0% something that I will have to learn as 00:07:03.400 --> 00:07:05.950 align:start position:0% something that I will have to learn as well<00:07:03.599> and<00:07:03.759> that<00:07:04.360> kind<00:07:04.479> of<00:07:04.800> brings<00:07:05.080> me<00:07:05.199> to<00:07:05.840> I 00:07:05.950 --> 00:07:05.960 align:start position:0% well and that kind of brings me to I 00:07:05.960 --> 00:07:08.710 align:start position:0% well and that kind of brings me to I would<00:07:06.080> like<00:07:06.199> to<00:07:06.400> talk<00:07:06.599> a<00:07:06.720> bit<00:07:07.039> about<00:07:08.039> my<00:07:08.199> EPF 00:07:08.710 --> 00:07:08.720 align:start position:0% would like to talk a bit about my EPF 00:07:08.720 --> 00:07:10.270 align:start position:0% would like to talk a bit about my EPF experience<00:07:09.240> because<00:07:09.520> I<00:07:09.599> think<00:07:09.759> that<00:07:09.879> was<00:07:10.160> a 00:07:10.270 --> 00:07:10.280 align:start position:0% experience because I think that was a 00:07:10.280 --> 00:07:13.029 align:start position:0% experience because I think that was a really<00:07:10.520> big<00:07:11.000> part<00:07:11.280> of<00:07:12.280> uh<00:07:12.400> this<00:07:12.599> program<00:07:12.879> for 00:07:13.029 --> 00:07:13.039 align:start position:0% really big part of uh this program for 00:07:13.039 --> 00:07:14.390 align:start position:0% really big part of uh this program for me<00:07:13.160> is<00:07:13.319> just<00:07:13.560> a<00:07:13.639> lot<00:07:13.759> of<00:07:13.879> the<00:07:13.960> learning<00:07:14.280> that 00:07:14.390 --> 00:07:14.400 align:start position:0% me is just a lot of the learning that 00:07:14.400 --> 00:07:17.430 align:start position:0% me is just a lot of the learning that I've<00:07:14.560> done<00:07:14.879> and<00:07:15.000> so<00:07:15.440> I<00:07:15.560> think<00:07:16.039> for<00:07:16.280> me<00:07:17.199> there 00:07:17.430 --> 00:07:17.440 align:start position:0% I've done and so I think for me there 00:07:17.440 --> 00:07:18.990 align:start position:0% I've done and so I think for me there there's<00:07:17.680> definitely<00:07:18.080> too<00:07:18.240> many<00:07:18.479> skills<00:07:18.840> to 00:07:18.990 --> 00:07:19.000 align:start position:0% there's definitely too many skills to 00:07:19.000 --> 00:07:22.469 align:start position:0% there's definitely too many skills to list<00:07:19.319> here<00:07:19.840> um<00:07:20.840> but<00:07:21.000> if<00:07:21.080> I<00:07:21.160> were<00:07:21.280> to<00:07:21.360> sum<00:07:21.560> it<00:07:21.680> up 00:07:22.469 --> 00:07:22.479 align:start position:0% list here um but if I were to sum it up 00:07:22.479 --> 00:07:24.869 align:start position:0% list here um but if I were to sum it up EPF<00:07:23.240> was<00:07:23.560> my<00:07:23.720> introduction<00:07:24.160> to<00:07:24.319> ethereum 00:07:24.869 --> 00:07:24.879 align:start position:0% EPF was my introduction to ethereum 00:07:24.879 --> 00:07:26.589 align:start position:0% EPF was my introduction to ethereum before<00:07:25.120> EPF<00:07:25.639> I<00:07:25.720> didn't<00:07:25.879> know<00:07:26.039> what<00:07:26.160> ethereum 00:07:26.589 --> 00:07:26.599 align:start position:0% before EPF I didn't know what ethereum 00:07:26.599 --> 00:07:27.990 align:start position:0% before EPF I didn't know what ethereum was<00:07:26.800> I<00:07:26.840> didn't<00:07:27.039> even<00:07:27.199> know<00:07:27.360> what<00:07:27.520> blockchain 00:07:27.990 --> 00:07:28.000 align:start position:0% was I didn't even know what blockchain 00:07:28.000 --> 00:07:30.749 align:start position:0% was I didn't even know what blockchain technology<00:07:28.560> was<00:07:29.080> so<00:07:29.560> for<00:07:29.680> me<00:07:29.960> that<00:07:30.080> was<00:07:30.199> a<00:07:30.400> huge 00:07:30.749 --> 00:07:30.759 align:start position:0% technology was so for me that was a huge 00:07:30.759 --> 00:07:32.790 align:start position:0% technology was so for me that was a huge just<00:07:30.879> to<00:07:31.400> get<00:07:31.560> into<00:07:31.800> the<00:07:32.000> space<00:07:32.240> and<00:07:32.360> learn 00:07:32.790 --> 00:07:32.800 align:start position:0% just to get into the space and learn 00:07:32.800 --> 00:07:35.270 align:start position:0% just to get into the space and learn everything<00:07:33.800> um<00:07:34.039> and<00:07:34.319> of<00:07:34.479> course<00:07:34.759> that<00:07:35.039> brought 00:07:35.270 --> 00:07:35.280 align:start position:0% everything um and of course that brought 00:07:35.280 --> 00:07:36.790 align:start position:0% everything um and of course that brought a<00:07:35.440> huge<00:07:35.720> confidence<00:07:36.120> boost<00:07:36.400> in<00:07:36.479> terms<00:07:36.639> of 00:07:36.790 --> 00:07:36.800 align:start position:0% a huge confidence boost in terms of 00:07:36.800 --> 00:07:39.869 align:start position:0% a huge confidence boost in terms of development<00:07:37.479> I<00:07:38.319> previously<00:07:39.319> you<00:07:39.440> know<00:07:39.680> I've 00:07:39.869 --> 00:07:39.879 align:start position:0% development I previously you know I've 00:07:39.879 --> 00:07:41.550 align:start position:0% development I previously you know I've never<00:07:40.120> worked<00:07:40.440> on<00:07:40.639> such<00:07:40.759> a<00:07:40.919> large<00:07:41.199> scale 00:07:41.550 --> 00:07:41.560 align:start position:0% never worked on such a large scale 00:07:41.560 --> 00:07:42.990 align:start position:0% never worked on such a large scale project<00:07:41.919> before<00:07:42.319> and<00:07:42.440> so<00:07:42.759> those 00:07:42.990 --> 00:07:43.000 align:start position:0% project before and so those 00:07:43.000 --> 00:07:44.909 align:start position:0% project before and so those organizational<00:07:43.680> skills<00:07:44.120> are<00:07:44.360> required<00:07:44.720> to 00:07:44.909 --> 00:07:44.919 align:start position:0% organizational skills are required to 00:07:44.919 --> 00:07:47.909 align:start position:0% organizational skills are required to create<00:07:45.240> that<00:07:45.479> project<00:07:46.000> was<00:07:47.000> like<00:07:47.199> huge<00:07:47.479> to<00:07:47.639> me 00:07:47.909 --> 00:07:47.919 align:start position:0% create that project was like huge to me 00:07:47.919 --> 00:07:49.589 align:start position:0% create that project was like huge to me and<00:07:48.639> definitely<00:07:48.960> gives<00:07:49.120> me<00:07:49.240> a<00:07:49.319> lot<00:07:49.440> more 00:07:49.589 --> 00:07:49.599 align:start position:0% and definitely gives me a lot more 00:07:49.599 --> 00:07:51.309 align:start position:0% and definitely gives me a lot more confidence<00:07:50.000> moving<00:07:50.240> forward<00:07:50.680> and<00:07:50.919> in<00:07:51.039> terms 00:07:51.309 --> 00:07:51.319 align:start position:0% confidence moving forward and in terms 00:07:51.319 --> 00:07:52.830 align:start position:0% confidence moving forward and in terms of<00:07:51.520> developing<00:07:51.960> projects<00:07:52.240> and<00:07:52.400> continuing<00:07:52.720> to 00:07:52.830 --> 00:07:52.840 align:start position:0% of developing projects and continuing to 00:07:52.840 --> 00:07:55.830 align:start position:0% of developing projects and continuing to work<00:07:52.960> on<00:07:53.120> this<00:07:53.319> project<00:07:54.159> um<00:07:54.319> as<00:07:54.560> well<00:07:55.560> I<00:07:55.639> think 00:07:55.830 --> 00:07:55.840 align:start position:0% work on this project um as well I think 00:07:55.840 --> 00:07:58.469 align:start position:0% work on this project um as well I think I<00:07:56.000> acquired<00:07:56.440> a<00:07:56.560> lot<00:07:56.720> of<00:07:56.919> new<00:07:57.159> learning<00:07:57.560> skills 00:07:58.469 --> 00:07:58.479 align:start position:0% I acquired a lot of new learning skills 00:07:58.479 --> 00:08:00.350 align:start position:0% I acquired a lot of new learning skills I<00:07:58.639> for<00:07:58.800> me<00:07:59.039> it's<00:07:59.680> I<00:07:59.800> think<00:07:59.960> I<00:08:00.039> could<00:08:00.199> best 00:08:00.350 --> 00:08:00.360 align:start position:0% I for me it's I think I could best 00:08:00.360 --> 00:08:02.869 align:start position:0% I for me it's I think I could best describe<00:08:00.680> it<00:08:00.759> as<00:08:00.919> I<00:08:01.000> learned<00:08:01.360> how<00:08:01.560> to<00:08:01.720> learn<00:08:02.599> um 00:08:02.869 --> 00:08:02.879 align:start position:0% describe it as I learned how to learn um 00:08:02.879 --> 00:08:05.350 align:start position:0% describe it as I learned how to learn um so<00:08:03.479> I<00:08:03.599> guess<00:08:03.720> the<00:08:03.840> biggest<00:08:04.159> example<00:08:04.479> for<00:08:05.000> in<00:08:05.159> my 00:08:05.350 --> 00:08:05.360 align:start position:0% so I guess the biggest example for in my 00:08:05.360 --> 00:08:07.869 align:start position:0% so I guess the biggest example for in my case<00:08:05.599> is<00:08:06.440> going<00:08:06.720> through<00:08:07.000> and<00:08:07.159> learning<00:08:07.560> the 00:08:07.869 --> 00:08:07.879 align:start position:0% case is going through and learning the 00:08:07.879 --> 00:08:11.189 align:start position:0% case is going through and learning the consensus<00:08:08.599> Discovery<00:08:08.879> V5<00:08:09.400> Library<00:08:10.159> I<00:08:11.039> had 00:08:11.189 --> 00:08:11.199 align:start position:0% consensus Discovery V5 Library I had 00:08:11.199 --> 00:08:13.749 align:start position:0% consensus Discovery V5 Library I had never<00:08:11.479> had<00:08:11.720> such<00:08:11.919> a<00:08:12.560> a<00:08:12.720> large<00:08:13.039> scale<00:08:13.360> library 00:08:13.749 --> 00:08:13.759 align:start position:0% never had such a a large scale library 00:08:13.759 --> 00:08:15.309 align:start position:0% never had such a a large scale library that<00:08:13.879> I<00:08:14.000> had<00:08:14.159> had<00:08:14.240> to<00:08:14.360> learn<00:08:14.560> in<00:08:14.720> the<00:08:14.919> past<00:08:15.199> and 00:08:15.309 --> 00:08:15.319 align:start position:0% that I had had to learn in the past and 00:08:15.319 --> 00:08:17.909 align:start position:0% that I had had to learn in the past and so<00:08:16.319> uh<00:08:16.440> learning<00:08:16.800> this<00:08:17.000> library<00:08:17.440> and<00:08:17.560> then 00:08:17.909 --> 00:08:17.919 align:start position:0% so uh learning this library and then 00:08:17.919 --> 00:08:19.589 align:start position:0% so uh learning this library and then automatically<00:08:18.599> going<00:08:18.879> and<00:08:19.039> going<00:08:19.280> over<00:08:19.440> to 00:08:19.589 --> 00:08:19.599 align:start position:0% automatically going and going over to 00:08:19.599 --> 00:08:21.990 align:start position:0% automatically going and going over to the<00:08:19.720> teu<00:08:20.319> library<00:08:21.120> and<00:08:21.240> then<00:08:21.360> learning<00:08:21.800> uh<00:08:21.919> the 00:08:21.990 --> 00:08:22.000 align:start position:0% the teu library and then learning uh the 00:08:22.000 --> 00:08:24.189 align:start position:0% the teu library and then learning uh the SS<00:08:22.400> internal<00:08:22.759> infrastructure<00:08:23.680> was<00:08:23.800> a<00:08:23.919> way<00:08:24.039> to 00:08:24.189 --> 00:08:24.199 align:start position:0% SS internal infrastructure was a way to 00:08:24.199 --> 00:08:26.309 align:start position:0% SS internal infrastructure was a way to then<00:08:24.360> quickly<00:08:25.319> uh<00:08:25.440> apply<00:08:25.720> the<00:08:25.840> skills<00:08:26.080> that<00:08:26.199> I 00:08:26.309 --> 00:08:26.319 align:start position:0% then quickly uh apply the skills that I 00:08:26.319 --> 00:08:28.710 align:start position:0% then quickly uh apply the skills that I just<00:08:26.440> learned<00:08:26.759> to<00:08:26.960> then<00:08:27.240> learn<00:08:27.759> a<00:08:27.919> new<00:08:28.199> library 00:08:28.710 --> 00:08:28.720 align:start position:0% just learned to then learn a new library 00:08:28.720 --> 00:08:31.710 align:start position:0% just learned to then learn a new library which<00:08:28.879> was<00:08:29.039> a<00:08:29.159> really<00:08:29.560> great<00:08:29.800> experience<00:08:30.720> um 00:08:31.710 --> 00:08:31.720 align:start position:0% which was a really great experience um 00:08:31.720 --> 00:08:33.750 align:start position:0% which was a really great experience um and<00:08:31.840> then<00:08:32.000> as<00:08:32.159> well<00:08:32.760> it<00:08:32.919> gave<00:08:33.080> me<00:08:33.200> a<00:08:33.320> project<00:08:33.640> I 00:08:33.750 --> 00:08:33.760 align:start position:0% and then as well it gave me a project I 00:08:33.760 --> 00:08:35.709 align:start position:0% and then as well it gave me a project I really<00:08:33.919> enjoy<00:08:34.200> working<00:08:34.440> on<00:08:34.800> and<00:08:35.360> of<00:08:35.519> course 00:08:35.709 --> 00:08:35.719 align:start position:0% really enjoy working on and of course 00:08:35.719 --> 00:08:39.469 align:start position:0% really enjoy working on and of course will<00:08:35.959> continue<00:08:36.360> working<00:08:36.719> on<00:08:37.719> um<00:08:38.719> and<00:08:38.839> so<00:08:39.159> yeah 00:08:39.469 --> 00:08:39.479 align:start position:0% will continue working on um and so yeah 00:08:39.479 --> 00:08:42.269 align:start position:0% will continue working on um and so yeah uh<00:08:39.599> the<00:08:39.719> SoMo<00:08:40.279> repository<00:08:40.800> can<00:08:40.919> be<00:08:41.159> found<00:08:42.159> uh 00:08:42.269 --> 00:08:42.279 align:start position:0% uh the SoMo repository can be found uh 00:08:42.279 --> 00:08:45.389 align:start position:0% uh the SoMo repository can be found uh on<00:08:42.440> melson's<00:08:43.240> G<00:08:43.479> GitHub<00:08:44.200> um<00:08:44.560> I<00:08:44.680> hope<00:08:45.040> that<00:08:45.200> one 00:08:45.389 --> 00:08:45.399 align:start position:0% on melson's G GitHub um I hope that one 00:08:45.399 --> 00:08:47.110 align:start position:0% on melson's G GitHub um I hope that one day<00:08:45.600> we<00:08:45.720> can<00:08:45.839> have<00:08:46.000> a<00:08:46.360> hyperledger<00:08:46.920> or 00:08:47.110 --> 00:08:47.120 align:start position:0% day we can have a hyperledger or 00:08:47.120 --> 00:08:50.470 align:start position:0% day we can have a hyperledger or consensus<00:08:47.880> of<00:08:48.240> repository<00:08:49.240> uh<00:08:49.440> for<00:08:49.640> that<00:08:49.839> name 00:08:50.470 --> 00:08:50.480 align:start position:0% consensus of repository uh for that name 00:08:50.480 --> 00:08:52.790 align:start position:0% consensus of repository uh for that name um<00:08:51.279> and<00:08:51.399> then<00:08:51.560> of<00:08:51.720> course<00:08:52.160> I'd<00:08:52.360> like<00:08:52.480> to<00:08:52.560> give<00:08:52.680> a 00:08:52.790 --> 00:08:52.800 align:start position:0% um and then of course I'd like to give a 00:08:52.800 --> 00:08:54.269 align:start position:0% um and then of course I'd like to give a big<00:08:53.000> thank<00:08:53.120> you<00:08:53.240> to<00:08:53.480> Melton<00:08:53.920> unfortunately 00:08:54.269 --> 00:08:54.279 align:start position:0% big thank you to Melton unfortunately 00:08:54.279 --> 00:08:55.870 align:start position:0% big thank you to Melton unfortunately wasn't<00:08:54.480> able<00:08:54.600> to<00:08:54.680> be<00:08:54.800> here<00:08:54.920> but<00:08:55.040> it's<00:08:55.600> been<00:08:55.720> a 00:08:55.870 --> 00:08:55.880 align:start position:0% wasn't able to be here but it's been a 00:08:55.880 --> 00:08:57.630 align:start position:0% wasn't able to be here but it's been a great<00:08:56.160> a<00:08:56.279> great<00:08:56.519> partner<00:08:57.080> great<00:08:57.279> working<00:08:57.519> with 00:08:57.630 --> 00:08:57.640 align:start position:0% great a great partner great working with 00:08:57.640 --> 00:08:59.990 align:start position:0% great a great partner great working with you<00:08:57.720> Melton<00:08:58.079> if<00:08:58.160> you're<00:08:58.360> watching<00:08:59.240> um 00:08:59.990 --> 00:09:00.000 align:start position:0% you Melton if you're watching um 00:09:00.000 --> 00:09:02.630 align:start position:0% you Melton if you're watching um and<00:09:00.120> then<00:09:00.519> my<00:09:00.640> friend<00:09:00.839> and<00:09:01.000> Mentor<00:09:01.440> Colby<00:09:02.240> uh 00:09:02.630 --> 00:09:02.640 align:start position:0% and then my friend and Mentor Colby uh 00:09:02.640 --> 00:09:04.829 align:start position:0% and then my friend and Mentor Colby uh so<00:09:03.360> unfortunately<00:09:03.800> I<00:09:03.880> can't<00:09:04.000> say<00:09:04.160> that<00:09:04.240> to<00:09:04.360> kby 00:09:04.829 --> 00:09:04.839 align:start position:0% so unfortunately I can't say that to kby 00:09:04.839 --> 00:09:07.110 align:start position:0% so unfortunately I can't say that to kby if<00:09:05.600> if<00:09:05.680> you're<00:09:05.839> interested<00:09:06.200> more<00:09:06.320> in<00:09:06.480> Portal 00:09:07.110 --> 00:09:07.120 align:start position:0% if if you're interested more in Portal 00:09:07.120 --> 00:09:08.990 align:start position:0% if if you're interested more in Portal um<00:09:07.480> his<00:09:07.680> talk<00:09:07.880> is<00:09:08.000> going<00:09:08.200> on<00:09:08.560> I<00:09:08.640> believe<00:09:08.880> on 00:09:08.990 --> 00:09:09.000 align:start position:0% um his talk is going on I believe on 00:09:09.000 --> 00:09:11.230 align:start position:0% um his talk is going on I believe on stage<00:09:09.240> two<00:09:09.560> right<00:09:09.720> now<00:09:10.480> um<00:09:10.760> and<00:09:10.880> then<00:09:11.079> of 00:09:11.230 --> 00:09:11.240 align:start position:0% stage two right now um and then of 00:09:11.240 --> 00:09:13.190 align:start position:0% stage two right now um and then of course<00:09:11.680> EPF<00:09:12.040> organizers<00:09:12.519> Josh<00:09:12.720> and<00:09:12.839> Mario 00:09:13.190 --> 00:09:13.200 align:start position:0% course EPF organizers Josh and Mario 00:09:13.200 --> 00:09:14.990 align:start position:0% course EPF organizers Josh and Mario it's<00:09:13.360> been<00:09:13.480> a<00:09:13.600> really<00:09:13.760> great<00:09:14.040> experience<00:09:14.880> I 00:09:14.990 --> 00:09:15.000 align:start position:0% it's been a really great experience I 00:09:15.000 --> 00:09:16.829 align:start position:0% it's been a really great experience I really<00:09:15.160> thank<00:09:15.320> you<00:09:15.480> for<00:09:15.680> this<00:09:16.240> but<00:09:16.440> yeah<00:09:16.640> thank 00:09:16.829 --> 00:09:16.839 align:start position:0% really thank you for this but yeah thank 00:09:16.839 --> 00:09:20.069 align:start position:0% really thank you for this but yeah thank you<00:09:17.720> thank<00:09:17.839> you<00:09:17.959> so<00:09:18.079> much<00:09:18.240> Derek<00:09:18.880> I<00:09:19.880> yeah<00:09:19.959> I 00:09:20.069 --> 00:09:20.079 align:start position:0% you thank you so much Derek I yeah I 00:09:20.079 --> 00:09:21.190 align:start position:0% you thank you so much Derek I yeah I really<00:09:20.240> appreciate<00:09:20.560> it<00:09:20.720> really<00:09:20.839> appreciate 00:09:21.190 --> 00:09:21.200 align:start position:0% really appreciate it really appreciate 00:09:21.200 --> 00:09:23.030 align:start position:0% really appreciate it really appreciate your<00:09:21.360> words<00:09:21.760> and<00:09:21.959> also<00:09:22.200> your<00:09:22.399> experience<00:09:22.839> with 00:09:23.030 --> 00:09:23.040 align:start position:0% your words and also your experience with 00:09:23.040 --> 00:09:25.829 align:start position:0% your words and also your experience with EPF<00:09:23.560> it's<00:09:23.720> amazing<00:09:24.040> to<00:09:24.160> see<00:09:24.480> and<00:09:24.760> uh<00:09:25.320> yeah<00:09:25.680> yeah 00:09:25.829 --> 00:09:25.839 align:start position:0% EPF it's amazing to see and uh yeah yeah 00:09:25.839 --> 00:09:27.550 align:start position:0% EPF it's amazing to see and uh yeah yeah m<00:09:26.160> going<00:09:26.399> make<00:09:26.560> it<00:09:26.640> I<00:09:26.760> met<00:09:26.959> him<00:09:27.360> uh<00:09:27.440> in 00:09:27.550 --> 00:09:27.560 align:start position:0% m going make it I met him uh in 00:09:27.560 --> 00:09:29.750 align:start position:0% m going make it I met him uh in Argentina<00:09:28.079> like<00:09:28.200> a<00:09:28.320> week<00:09:28.519> ago<00:09:28.959> and<00:09:29.200> like<00:09:29.560> he's 00:09:29.750 --> 00:09:29.760 align:start position:0% Argentina like a week ago and like he's 00:09:29.760 --> 00:09:31.509 align:start position:0% Argentina like a week ago and like he's he's<00:09:29.920> also<00:09:30.079> a<00:09:30.200> great<00:09:30.440> person<00:09:31.160> couldn't 00:09:31.509 --> 00:09:31.519 align:start position:0% he's also a great person couldn't 00:09:31.519 --> 00:09:32.990 align:start position:0% he's also a great person couldn't couldn't<00:09:31.760> come<00:09:32.000> but<00:09:32.279> uh<00:09:32.360> he<00:09:32.480> will<00:09:32.600> be<00:09:32.760> still 00:09:32.990 --> 00:09:33.000 align:start position:0% couldn't come but uh he will be still 00:09:33.000 --> 00:09:35.750 align:start position:0% couldn't come but uh he will be still also<00:09:33.360> contributing<00:09:33.880> to<00:09:34.079> sambba<00:09:35.079> um<00:09:35.360> anyone 00:09:35.750 --> 00:09:35.760 align:start position:0% also contributing to sambba um anyone 00:09:35.760 --> 00:09:39.310 align:start position:0% also contributing to sambba um anyone anyone<00:09:36.560> has<00:09:36.680> a<00:09:36.839> question<00:09:37.680> about<00:09:38.000> portal<00:09:38.680> about 00:09:39.310 --> 00:09:39.320 align:start position:0% anyone has a question about portal about 00:09:39.320 --> 00:09:45.190 align:start position:0% anyone has a question about portal about uh<00:09:40.120> um<00:09:40.440> the<00:09:40.720> best<00:09:41.160> java<00:09:41.399> implementation 00:09:45.190 --> 00:09:45.200 align:start position:0% 00:09:45.200 --> 00:09:47.230 align:start position:0% yeah<00:09:46.200> yeah<00:09:46.360> just<00:09:46.519> kind<00:09:46.600> of<00:09:46.720> a<00:09:46.839> general 00:09:47.230 --> 00:09:47.240 align:start position:0% yeah yeah just kind of a general 00:09:47.240 --> 00:09:49.389 align:start position:0% yeah yeah just kind of a general question<00:09:47.720> like<00:09:48.000> if<00:09:48.519> uh<00:09:48.720> you're<00:09:48.920> still<00:09:49.120> working 00:09:49.389 --> 00:09:49.399 align:start position:0% question like if uh you're still working 00:09:49.399 --> 00:09:52.069 align:start position:0% question like if uh you're still working on<00:09:49.680> UTP<00:09:50.480> how<00:09:50.600> are<00:09:50.760> you<00:09:50.920> doing<00:09:51.360> the<00:09:51.600> interupt 00:09:52.069 --> 00:09:52.079 align:start position:0% on UTP how are you doing the interupt 00:09:52.079 --> 00:09:54.150 align:start position:0% on UTP how are you doing the interupt testing<00:09:52.760> to<00:09:53.000> to<00:09:53.120> verify<00:09:53.560> correctness<00:09:54.040> with 00:09:54.150 --> 00:09:54.160 align:start position:0% testing to to verify correctness with 00:09:54.160 --> 00:09:56.670 align:start position:0% testing to to verify correctness with the<00:09:54.240> other<00:09:54.399> portal<00:09:54.680> clients<00:09:55.360> so<00:09:55.839> for<00:09:56.160> interrup 00:09:56.670 --> 00:09:56.680 align:start position:0% the other portal clients so for interrup 00:09:56.680 --> 00:09:58.430 align:start position:0% the other portal clients so for interrup testing<00:09:57.040> there's<00:09:57.200> a<00:09:57.360> lot<00:09:57.720> more<00:09:58.000> than<00:09:58.200> just 00:09:58.430 --> 00:09:58.440 align:start position:0% testing there's a lot more than just 00:09:58.440 --> 00:10:00.150 align:start position:0% testing there's a lot more than just actual<00:09:58.760> like<00:09:58.880> content<00:09:59.360> sharing<00:09:59.680> testing<00:10:00.040> like 00:10:00.150 --> 00:10:00.160 align:start position:0% actual like content sharing testing like 00:10:00.160 --> 00:10:01.790 align:start position:0% actual like content sharing testing like for<00:10:00.320> example<00:10:00.720> just<00:10:00.920> the<00:10:01.079> propagation<00:10:01.600> of 00:10:01.790 --> 00:10:01.800 align:start position:0% for example just the propagation of 00:10:01.800 --> 00:10:03.949 align:start position:0% for example just the propagation of peers<00:10:02.200> is<00:10:02.320> one<00:10:02.480> thing<00:10:02.600> that<00:10:02.720> we<00:10:02.839> can<00:10:03.000> test<00:10:03.839> and 00:10:03.949 --> 00:10:03.959 align:start position:0% peers is one thing that we can test and 00:10:03.959 --> 00:10:05.350 align:start position:0% peers is one thing that we can test and there's<00:10:04.160> like<00:10:04.279> General<00:10:04.600> testing<00:10:04.880> in<00:10:04.959> terms<00:10:05.200> of 00:10:05.350 --> 00:10:05.360 align:start position:0% there's like General testing in terms of 00:10:05.360 --> 00:10:07.350 align:start position:0% there's like General testing in terms of like<00:10:05.480> just<00:10:05.640> making<00:10:05.880> sure<00:10:06.200> that<00:10:06.399> ping<00:10:06.760> pong 00:10:07.350 --> 00:10:07.360 align:start position:0% like just making sure that ping pong 00:10:07.360 --> 00:10:09.069 align:start position:0% like just making sure that ping pong find<00:10:07.600> nodes<00:10:07.920> nodes<00:10:08.360> responses<00:10:08.760> are 00:10:09.069 --> 00:10:09.079 align:start position:0% find nodes nodes responses are 00:10:09.079 --> 00:10:11.389 align:start position:0% find nodes nodes responses are functioning<00:10:10.079> um<00:10:10.200> and<00:10:10.320> then<00:10:10.440> as<00:10:10.600> well<00:10:10.920> exposing 00:10:11.389 --> 00:10:11.399 align:start position:0% functioning um and then as well exposing 00:10:11.399 --> 00:10:13.509 align:start position:0% functioning um and then as well exposing apis<00:10:12.120> a<00:10:12.200> lot<00:10:12.320> of<00:10:12.440> the<00:10:12.600> stuff<00:10:13.160> also<00:10:13.360> just 00:10:13.509 --> 00:10:13.519 align:start position:0% apis a lot of the stuff also just 00:10:13.519 --> 00:10:15.430 align:start position:0% apis a lot of the stuff also just includes<00:10:13.880> serving<00:10:14.399> like<00:10:14.920> uh<00:10:15.040> information 00:10:15.430 --> 00:10:15.440 align:start position:0% includes serving like uh information 00:10:15.440 --> 00:10:17.030 align:start position:0% includes serving like uh information that<00:10:15.560> comes<00:10:15.760> just<00:10:15.920> from<00:10:16.079> the<00:10:16.360> Discovery<00:10:16.600> V5 00:10:17.030 --> 00:10:17.040 align:start position:0% that comes just from the Discovery V5 00:10:17.040 --> 00:10:18.949 align:start position:0% that comes just from the Discovery V5 library<00:10:17.560> and<00:10:17.720> so<00:10:18.279> that's<00:10:18.440> kind<00:10:18.560> of<00:10:18.640> the<00:10:18.760> part 00:10:18.949 --> 00:10:18.959 align:start position:0% library and so that's kind of the part 00:10:18.959 --> 00:10:20.670 align:start position:0% library and so that's kind of the part that<00:10:19.160> we<00:10:19.279> are<00:10:19.600> now<00:10:19.760> stepping<00:10:20.079> into<00:10:20.360> is<00:10:20.519> getting 00:10:20.670 --> 00:10:20.680 align:start position:0% that we are now stepping into is getting 00:10:20.680 --> 00:10:21.910 align:start position:0% that we are now stepping into is getting all<00:10:20.839> that<00:10:21.000> set 00:10:21.910 --> 00:10:21.920 align:start position:0% all that set 00:10:21.920 --> 00:10:24.069 align:start position:0% all that set up 00:10:24.069 --> 00:10:24.079 align:start position:0% up 00:10:24.079 --> 00:10:26.269 align:start position:0% up cool<00:10:25.079> thank<00:10:25.240> you<00:10:25.320> so<00:10:25.480> much<00:10:25.839> uh<00:10:25.959> we<00:10:26.040> have<00:10:26.160> a 00:10:26.269 --> 00:10:26.279 align:start position:0% cool thank you so much uh we have a 00:10:26.279 --> 00:10:28.190 align:start position:0% cool thank you so much uh we have a space<00:10:26.480> for<00:10:26.680> another<00:10:27.000> question<00:10:27.320> if<00:10:27.480> there<00:10:27.600> is 00:10:28.190 --> 00:10:28.200 align:start position:0% space for another question if there is 00:10:28.200 --> 00:10:31.470 align:start position:0% space for another question if there is uh<00:10:28.519> anyone<00:10:29.000> any<00:10:29.360> comments<00:10:29.720> any<00:10:30.399> questions 00:10:31.470 --> 00:10:31.480 align:start position:0% uh anyone any comments any questions 00:10:31.480 --> 00:10:34.030 align:start position:0% uh anyone any comments any questions yeah<00:10:32.480> I<00:10:32.560> mean<00:10:32.839> it's<00:10:33.000> it's<00:10:33.200> very<00:10:33.399> important 00:10:34.030 --> 00:10:34.040 align:start position:0% yeah I mean it's it's very important 00:10:34.040 --> 00:10:36.670 align:start position:0% yeah I mean it's it's very important topic<00:10:34.440> right<00:10:34.600> now<00:10:34.880> because<00:10:35.639> uh<00:10:36.120> in<00:10:36.320> probably 00:10:36.670 --> 00:10:36.680 align:start position:0% topic right now because uh in probably 00:10:36.680 --> 00:10:38.829 align:start position:0% topic right now because uh in probably in<00:10:36.920> like<00:10:37.279> next<00:10:37.600> year<00:10:37.880> the<00:10:38.000> four<00:10:38.240> fors<00:10:38.680> will 00:10:38.829 --> 00:10:38.839 align:start position:0% in like next year the four fors will 00:10:38.839 --> 00:10:42.230 align:start position:0% in like next year the four fors will ship<00:10:39.440> the<00:10:40.120> uh<00:10:40.480> ethereum<00:10:40.959> will<00:10:41.160> drop<00:10:41.440> it<00:10:41.639> it<00:10:42.000> it 00:10:42.230 --> 00:10:42.240 align:start position:0% ship the uh ethereum will drop it it it 00:10:42.240 --> 00:10:44.470 align:start position:0% ship the uh ethereum will drop it it it its<00:10:42.440> history<00:10:43.200> and<00:10:43.360> verle<00:10:43.760> is<00:10:43.839> not<00:10:43.959> coming 00:10:44.470 --> 00:10:44.480 align:start position:0% its history and verle is not coming 00:10:44.480 --> 00:10:46.790 align:start position:0% its history and verle is not coming anytime<00:10:44.800> soon<00:10:45.480> so<00:10:45.800> meanwhile<00:10:46.240> having<00:10:46.519> light 00:10:46.790 --> 00:10:46.800 align:start position:0% anytime soon so meanwhile having light 00:10:46.800 --> 00:10:49.350 align:start position:0% anytime soon so meanwhile having light clients<00:10:47.680> uh<00:10:47.760> serving<00:10:48.120> the<00:10:48.279> state<00:10:48.600> and<00:10:49.040> serving 00:10:49.350 --> 00:10:49.360 align:start position:0% clients uh serving the state and serving 00:10:49.360 --> 00:10:51.430 align:start position:0% clients uh serving the state and serving the<00:10:49.519> history<00:10:49.800> is<00:10:49.920> extremely<00:10:50.360> important<00:10:51.200> and 00:10:51.430 --> 00:10:51.440 align:start position:0% the history is extremely important and 00:10:51.440 --> 00:10:53.389 align:start position:0% the history is extremely important and as<00:10:51.560> we<00:10:51.680> have<00:10:51.880> diversity<00:10:52.360> in<00:10:52.480> the<00:10:52.639> L1<00:10:53.040> clients 00:10:53.389 --> 00:10:53.399 align:start position:0% as we have diversity in the L1 clients 00:10:53.399 --> 00:10:55.430 align:start position:0% as we have diversity in the L1 clients we<00:10:53.519> need<00:10:53.720> diversity<00:10:54.200> in<00:10:54.320> the<00:10:54.639> portal<00:10:55.000> clients 00:10:55.430 --> 00:10:55.440 align:start position:0% we need diversity in the portal clients 00:10:55.440 --> 00:10:57.430 align:start position:0% we need diversity in the portal clients so<00:10:55.680> yeah<00:10:55.800> I<00:10:55.920> really<00:10:56.160> respect<00:10:56.440> the<00:10:56.600> work<00:10:56.800> man 00:10:57.430 --> 00:10:57.440 align:start position:0% so yeah I really respect the work man 00:10:57.440 --> 00:10:59.030 align:start position:0% so yeah I really respect the work man and<00:10:57.680> if<00:10:57.839> there<00:10:57.920> are<00:10:58.079> no<00:10:58.240> more<00:10:58.600> yeah<00:10:58.760> yeah<00:10:58.880> there 00:10:59.030 --> 00:10:59.040 align:start position:0% and if there are no more yeah yeah there 00:10:59.040 --> 00:11:02.829 align:start position:0% and if there are no more yeah yeah there sorry 00:11:02.829 --> 00:11:02.839 align:start position:0% 00:11:02.839 --> 00:11:05.670 align:start position:0% um<00:11:03.200> for<00:11:03.440> serving<00:11:03.920> the<00:11:04.160> data<00:11:05.120> are<00:11:05.200> you<00:11:05.399> get<00:11:05.600> are 00:11:05.670 --> 00:11:05.680 align:start position:0% um for serving the data are you get are 00:11:05.680 --> 00:11:07.550 align:start position:0% um for serving the data are you get are you<00:11:05.839> getting<00:11:06.079> that<00:11:06.240> from<00:11:06.480> Basu<00:11:07.160> like<00:11:07.480> if 00:11:07.550 --> 00:11:07.560 align:start position:0% you getting that from Basu like if 00:11:07.560 --> 00:11:09.670 align:start position:0% you getting that from Basu like if you're<00:11:08.240> res 00:11:09.670 --> 00:11:09.680 align:start position:0% you're res 00:11:09.680 --> 00:11:11.829 align:start position:0% you're res sharing<00:11:10.680> this<00:11:10.880> chain<00:11:11.240> State<00:11:11.560> over<00:11:11.720> the 00:11:11.829 --> 00:11:11.839 align:start position:0% sharing this chain State over the 00:11:11.839 --> 00:11:13.430 align:start position:0% sharing this chain State over the network<00:11:12.200> does<00:11:12.320> that<00:11:12.480> come<00:11:12.600> from<00:11:12.760> the<00:11:12.880> basso 00:11:13.430 --> 00:11:13.440 align:start position:0% network does that come from the basso 00:11:13.440 --> 00:11:15.629 align:start position:0% network does that come from the basso database<00:11:13.959> or<00:11:14.320> so<00:11:14.680> that<00:11:14.839> will<00:11:15.079> eventally<00:11:15.519> but 00:11:15.629 --> 00:11:15.639 align:start position:0% database or so that will eventally but 00:11:15.639 --> 00:11:18.670 align:start position:0% database or so that will eventally but in<00:11:15.760> terms<00:11:16.000> of<00:11:16.360> History<00:11:16.959> right<00:11:17.160> now<00:11:17.839> uh<00:11:18.480> uh<00:11:18.600> the 00:11:18.670 --> 00:11:18.680 align:start position:0% in terms of History right now uh uh the 00:11:18.680 --> 00:11:21.030 align:start position:0% in terms of History right now uh uh the portal<00:11:19.040> Network<00:11:19.480> itself<00:11:20.040> there<00:11:20.480> is<00:11:20.600> slowly 00:11:21.030 --> 00:11:21.040 align:start position:0% portal Network itself there is slowly 00:11:21.040 --> 00:11:22.509 align:start position:0% portal Network itself there is slowly being<00:11:21.480> uh<00:11:21.680> history<00:11:21.959> is<00:11:22.040> being<00:11:22.200> slowly 00:11:22.509 --> 00:11:22.519 align:start position:0% being uh history is being slowly 00:11:22.519 --> 00:11:23.870 align:start position:0% being uh history is being slowly propagated<00:11:22.959> into<00:11:23.120> the<00:11:23.240> network<00:11:23.560> so<00:11:23.680> that<00:11:23.800> it 00:11:23.870 --> 00:11:23.880 align:start position:0% propagated into the network so that it 00:11:23.880 --> 00:11:26.310 align:start position:0% propagated into the network so that it can<00:11:24.000> then<00:11:24.120> be<00:11:24.200> shared<00:11:24.519> around<00:11:25.440> the<00:11:25.720> chain<00:11:26.200> like 00:11:26.310 --> 00:11:26.320 align:start position:0% can then be shared around the chain like 00:11:26.320 --> 00:11:28.310 align:start position:0% can then be shared around the chain like State<00:11:26.600> and<00:11:26.760> Beacon<00:11:27.200> will<00:11:27.440> eventually<00:11:27.920> come 00:11:28.310 --> 00:11:28.320 align:start position:0% State and Beacon will eventually come 00:11:28.320 --> 00:11:29.790 align:start position:0% State and Beacon will eventually come but<00:11:28.600> as<00:11:28.800> as<00:11:28.920> it<00:11:29.040> stands<00:11:29.360> we're<00:11:29.440> just<00:11:29.519> trying<00:11:29.680> to 00:11:29.790 --> 00:11:29.800 align:start position:0% but as as it stands we're just trying to 00:11:29.800 --> 00:11:31.629 align:start position:0% but as as it stands we're just trying to get<00:11:29.920> history<00:11:30.200> up<00:11:30.320> and<00:11:30.440> running<00:11:30.720> and<00:11:30.880> then 00:11:31.629 --> 00:11:31.639 align:start position:0% get history up and running and then 00:11:31.639 --> 00:11:33.509 align:start position:0% get history up and running and then that's<00:11:31.839> kind<00:11:31.959> of<00:11:32.079> the<00:11:32.320> point<00:11:32.839> where<00:11:33.279> we'll 00:11:33.509 --> 00:11:33.519 align:start position:0% that's kind of the point where we'll 00:11:33.519 --> 00:11:35.110 align:start position:0% that's kind of the point where we'll then<00:11:33.680> focus<00:11:33.959> on<00:11:34.120> other<00:11:34.320> things<00:11:34.519> and<00:11:34.680> then<00:11:34.959> as 00:11:35.110 --> 00:11:35.120 align:start position:0% then focus on other things and then as 00:11:35.120 --> 00:11:37.590 align:start position:0% then focus on other things and then as well<00:11:35.600> where<00:11:35.760> we<00:11:35.920> kind<00:11:36.000> of<00:11:36.120> shift<00:11:36.360> into<00:11:36.720> actual 00:11:37.590 --> 00:11:37.600 align:start position:0% well where we kind of shift into actual 00:11:37.600 --> 00:11:38.710 align:start position:0% well where we kind of shift into actual participating<00:11:38.040> in<00:11:38.120> the<00:11:38.200> development<00:11:38.560> of 00:11:38.710 --> 00:11:38.720 align:start position:0% participating in the development of 00:11:38.720 --> 00:11:41.790 align:start position:0% participating in the development of portal<00:11:39.720> okay<00:11:40.200> thank 00:11:41.790 --> 00:11:41.800 align:start position:0% portal okay thank 00:11:41.800 --> 00:11:44.350 align:start position:0% portal okay thank you<00:11:42.800> awesome<00:11:43.120> thank<00:11:43.240> you<00:11:43.320> so<00:11:43.440> much<00:11:43.600> Derek<00:11:44.120> yeah 00:11:44.350 --> 00:11:44.360 align:start position:0% you awesome thank you so much Derek yeah 00:11:44.360 --> 00:11:47.720 align:start position:0% you awesome thank you so much Derek yeah uh<00:11:44.480> very<00:11:44.760> well<00:11:45.200> um<00:11:45.480> yeah