WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:02.720 align:start position:0% they're<00:00:00.179> so<00:00:00.840> pantheon<00:00:01.620> is<00:00:01.949> a<00:00:01.979> new<00:00:02.310> aetherium 00:00:02.720 --> 00:00:02.730 align:start position:0% they're so pantheon is a new aetherium 00:00:02.730 --> 00:00:05.630 align:start position:0% they're so pantheon is a new aetherium client<00:00:03.090> built<00:00:03.389> with<00:00:03.540> the<00:00:03.629> JVM<00:00:04.520> because<00:00:05.520> we 00:00:05.630 --> 00:00:05.640 align:start position:0% client built with the JVM because we 00:00:05.640 --> 00:00:07.099 align:start position:0% client built with the JVM because we built<00:00:05.879> it<00:00:06.029> from<00:00:06.180> the<00:00:06.270> ground<00:00:06.359> up<00:00:06.779> it's<00:00:07.049> a 00:00:07.099 --> 00:00:07.109 align:start position:0% built it from the ground up it's a 00:00:07.109 --> 00:00:09.379 align:start position:0% built it from the ground up it's a patchy<00:00:07.319> -<00:00:07.560> license<00:00:07.980> and<00:00:08.280> we<00:00:08.400> quietly<00:00:09.150> over 00:00:09.379 --> 00:00:09.389 align:start position:0% patchy - license and we quietly over 00:00:09.389 --> 00:00:11.600 align:start position:0% patchy - license and we quietly over open-source<00:00:10.170> it<00:00:10.349> over<00:00:10.559> the<00:00:10.650> weekend<00:00:11.010> it's<00:00:11.460> now 00:00:11.600 --> 00:00:11.610 align:start position:0% open-source it over the weekend it's now 00:00:11.610 --> 00:00:13.220 align:start position:0% open-source it over the weekend it's now fully<00:00:11.880> open<00:00:12.179> source<00:00:12.210> you<00:00:12.660> can<00:00:12.750> check<00:00:12.960> it<00:00:13.080> out 00:00:13.220 --> 00:00:13.230 align:start position:0% fully open source you can check it out 00:00:13.230 --> 00:00:15.740 align:start position:0% fully open source you can check it out we'll<00:00:13.410> be<00:00:13.530> sharing<00:00:13.769> the<00:00:14.400> repo<00:00:14.670> later<00:00:14.910> we<00:00:15.630> had<00:00:15.719> a 00:00:15.740 --> 00:00:15.750 align:start position:0% we'll be sharing the repo later we had a 00:00:15.750 --> 00:00:18.410 align:start position:0% we'll be sharing the repo later we had a few<00:00:16.160> crawlers<00:00:17.160> find<00:00:17.550> us<00:00:17.730> over<00:00:17.970> the<00:00:18.060> weekend 00:00:18.410 --> 00:00:18.420 align:start position:0% few crawlers find us over the weekend 00:00:18.420 --> 00:00:20.630 align:start position:0% few crawlers find us over the weekend and<00:00:18.630> commit<00:00:18.869> PRS<00:00:19.470> submit<00:00:20.039> PRS<00:00:20.369> and<00:00:20.400> getting 00:00:20.630 --> 00:00:20.640 align:start position:0% and commit PRS submit PRS and getting 00:00:20.640 --> 00:00:22.099 align:start position:0% and commit PRS submit PRS and getting committed<00:00:20.880> so<00:00:21.180> we're<00:00:21.359> up<00:00:21.449> and<00:00:21.570> running<00:00:21.630> it<00:00:21.990> all 00:00:22.099 --> 00:00:22.109 align:start position:0% committed so we're up and running it all 00:00:22.109 --> 00:00:23.210 align:start position:0% committed so we're up and running it all works 00:00:23.210 --> 00:00:23.220 align:start position:0% works 00:00:23.220 --> 00:00:25.640 align:start position:0% works it<00:00:23.519> runs<00:00:23.880> live<00:00:24.119> on<00:00:24.330> main<00:00:24.539> net<00:00:24.779> on<00:00:24.990> rinkeby<00:00:25.439> on 00:00:25.640 --> 00:00:25.650 align:start position:0% it runs live on main net on rinkeby on 00:00:25.650 --> 00:00:27.290 align:start position:0% it runs live on main net on rinkeby on Rob<00:00:25.830> Stan<00:00:26.130> there's<00:00:26.430> proof<00:00:26.609> of<00:00:26.730> work<00:00:26.880> there's 00:00:27.290 --> 00:00:27.300 align:start position:0% Rob Stan there's proof of work there's 00:00:27.300 --> 00:00:29.810 align:start position:0% Rob Stan there's proof of work there's click<00:00:27.510> POA<00:00:27.810> it's<00:00:28.560> a<00:00:28.769> it's<00:00:28.980> a<00:00:29.070> real<00:00:29.279> functioning 00:00:29.810 --> 00:00:29.820 align:start position:0% click POA it's a it's a real functioning 00:00:29.820 --> 00:00:31.070 align:start position:0% click POA it's a it's a real functioning client<00:00:30.150> you<00:00:30.390> know<00:00:30.480> we<00:00:30.570> integrate<00:00:30.900> with<00:00:31.019> a 00:00:31.070 --> 00:00:31.080 align:start position:0% client you know we integrate with a 00:00:31.080 --> 00:00:32.900 align:start position:0% client you know we integrate with a bunch<00:00:31.260> of<00:00:31.349> other<00:00:31.439> consensus<00:00:32.070> projects<00:00:32.669> within 00:00:32.900 --> 00:00:32.910 align:start position:0% bunch of other consensus projects within 00:00:32.910 --> 00:00:35.750 align:start position:0% bunch of other consensus projects within furo<00:00:33.329> with<00:00:33.630> Alessio<00:00:34.079> with<00:00:34.440> truffle<00:00:34.920> meta<00:00:35.520> mask 00:00:35.750 --> 00:00:35.760 align:start position:0% furo with Alessio with truffle meta mask 00:00:35.760 --> 00:00:38.119 align:start position:0% furo with Alessio with truffle meta mask and<00:00:36.090> a<00:00:36.120> bunch<00:00:36.300> of<00:00:36.420> non<00:00:36.600> consensus<00:00:37.170> players<00:00:37.920> in 00:00:38.119 --> 00:00:38.129 align:start position:0% and a bunch of non consensus players in 00:00:38.129 --> 00:00:39.920 align:start position:0% and a bunch of non consensus players in the<00:00:38.219> ecosystem<00:00:38.250> as<00:00:38.969> well<00:00:39.000> and<00:00:39.390> we're<00:00:39.780> always 00:00:39.920 --> 00:00:39.930 align:start position:0% the ecosystem as well and we're always 00:00:39.930 --> 00:00:42.889 align:start position:0% the ecosystem as well and we're always looking<00:00:40.140> for<00:00:40.320> more<00:00:40.500> so<00:00:41.399> you<00:00:42.030> know<00:00:42.090> the<00:00:42.239> final 00:00:42.889 --> 00:00:42.899 align:start position:0% looking for more so you know the final 00:00:42.899 --> 00:00:44.690 align:start position:0% looking for more so you know the final point<00:00:43.110> that<00:00:43.200> I<00:00:43.290> just<00:00:43.410> want<00:00:43.590> to<00:00:43.649> say<00:00:43.860> on<00:00:44.010> what<00:00:44.550> we 00:00:44.690 --> 00:00:44.700 align:start position:0% point that I just want to say on what we 00:00:44.700 --> 00:00:46.369 align:start position:0% point that I just want to say on what we are<00:00:44.910> and<00:00:45.120> where<00:00:45.300> we<00:00:45.450> are<00:00:45.600> is<00:00:45.840> this<00:00:46.170> is<00:00:46.289> our 00:00:46.369 --> 00:00:46.379 align:start position:0% are and where we are is this is our 00:00:46.379 --> 00:00:48.500 align:start position:0% are and where we are is this is our first<00:00:46.890> release<00:00:47.160> we<00:00:47.489> wanted<00:00:47.730> to<00:00:47.820> release<00:00:48.059> early 00:00:48.500 --> 00:00:48.510 align:start position:0% first release we wanted to release early 00:00:48.510 --> 00:00:50.090 align:start position:0% first release we wanted to release early so<00:00:48.719> we<00:00:48.750> could<00:00:48.930> get<00:00:49.050> feedback<00:00:49.469> and<00:00:49.739> help<00:00:49.920> the 00:00:50.090 --> 00:00:50.100 align:start position:0% so we could get feedback and help the 00:00:50.100 --> 00:00:51.770 align:start position:0% so we could get feedback and help the community<00:00:50.219> shape<00:00:51.120> what<00:00:51.300> we're<00:00:51.449> doing<00:00:51.750> so 00:00:51.770 --> 00:00:51.780 align:start position:0% community shape what we're doing so 00:00:51.780 --> 00:00:53.840 align:start position:0% community shape what we're doing so please<00:00:52.559> play<00:00:52.739> around<00:00:52.949> with<00:00:53.100> it<00:00:53.280> please 00:00:53.840 --> 00:00:53.850 align:start position:0% please play around with it please 00:00:53.850 --> 00:00:55.250 align:start position:0% please play around with it please realize<00:00:54.270> it's<00:00:54.480> a<00:00:54.539> work<00:00:54.690> in<00:00:54.780> progress<00:00:55.020> but 00:00:55.250 --> 00:00:55.260 align:start position:0% realize it's a work in progress but 00:00:55.260 --> 00:00:56.869 align:start position:0% realize it's a work in progress but please<00:00:55.710> work<00:00:55.980> with<00:00:56.010> us<00:00:56.219> to<00:00:56.520> make<00:00:56.640> it<00:00:56.760> better 00:00:56.869 --> 00:00:56.879 align:start position:0% please work with us to make it better 00:00:56.879 --> 00:00:58.880 align:start position:0% please work with us to make it better and<00:00:57.270> so<00:00:57.480> just<00:00:57.750> to<00:00:57.930> prove<00:00:58.170> that<00:00:58.230> we're<00:00:58.649> real 00:00:58.880 --> 00:00:58.890 align:start position:0% and so just to prove that we're real 00:00:58.890 --> 00:01:00.830 align:start position:0% and so just to prove that we're real this<00:00:59.190> is<00:00:59.340> a<00:00:59.370> snapshot<00:00:59.699> we<00:01:00.059> took<00:01:00.239> this<00:01:00.420> morning 00:01:00.830 --> 00:01:00.840 align:start position:0% this is a snapshot we took this morning 00:01:00.840 --> 00:01:03.170 align:start position:0% this is a snapshot we took this morning from<00:01:00.989> each<00:01:01.230> stats<00:01:01.500> and<00:01:01.890> lo<00:01:02.399> and<00:01:02.520> behold<00:01:02.640> there 00:01:03.170 --> 00:01:03.180 align:start position:0% from each stats and lo and behold there 00:01:03.180 --> 00:01:05.390 align:start position:0% from each stats and lo and behold there we<00:01:03.329> are<00:01:03.359> running<00:01:04.229> both<00:01:04.439> our<00:01:04.619> own<00:01:04.769> nodes<00:01:05.070> and 00:01:05.390 --> 00:01:05.400 align:start position:0% we are running both our own nodes and 00:01:05.400 --> 00:01:07.190 align:start position:0% we are running both our own nodes and running<00:01:05.760> on<00:01:05.880> in<00:01:06.000> fear<00:01:06.240> uh<00:01:06.270> Pantheon<00:01:06.930> nodes 00:01:07.190 --> 00:01:07.200 align:start position:0% running on in fear uh Pantheon nodes 00:01:07.200 --> 00:01:09.080 align:start position:0% running on in fear uh Pantheon nodes which<00:01:07.470> for<00:01:07.950> us<00:01:07.979> is<00:01:08.040> pretty<00:01:08.400> exciting<00:01:08.790> it<00:01:08.880> works 00:01:09.080 --> 00:01:09.090 align:start position:0% which for us is pretty exciting it works 00:01:09.090 --> 00:01:15.990 align:start position:0% which for us is pretty exciting it works it's<00:01:09.390> real<00:01:09.619> we're<00:01:10.619> not<00:01:10.740> making<00:01:11.040> this<00:01:11.130> up<00:01:11.510> so 00:01:15.990 --> 00:01:16.000 align:start position:0% 00:01:16.000 --> 00:01:18.220 align:start position:0% [Applause] 00:01:18.220 --> 00:01:18.230 align:start position:0% [Applause] 00:01:18.230 --> 00:01:21.560 align:start position:0% [Applause] so<00:01:19.230> why<00:01:19.770> did<00:01:19.890> we<00:01:19.980> do<00:01:20.100> this<00:01:20.250> why<00:01:21.180> don't<00:01:21.360> we<00:01:21.420> spend 00:01:21.560 --> 00:01:21.570 align:start position:0% so why did we do this why don't we spend 00:01:21.570 --> 00:01:23.360 align:start position:0% so why did we do this why don't we spend the<00:01:21.720> last<00:01:21.840> year<00:01:22.110> building<00:01:22.380> another<00:01:22.740> aetherium 00:01:23.360 --> 00:01:23.370 align:start position:0% the last year building another aetherium 00:01:23.370 --> 00:01:25.790 align:start position:0% the last year building another aetherium client<00:01:23.730> a<00:01:23.820> couple<00:01:24.390> reasons<00:01:24.540> first<00:01:25.260> we<00:01:25.500> believe 00:01:25.790 --> 00:01:25.800 align:start position:0% client a couple reasons first we believe 00:01:25.800 --> 00:01:28.490 align:start position:0% client a couple reasons first we believe that<00:01:26.160> a<00:01:26.430> healthy<00:01:27.330> ecosystem<00:01:27.480> requires<00:01:28.290> a 00:01:28.490 --> 00:01:28.500 align:start position:0% that a healthy ecosystem requires a 00:01:28.500 --> 00:01:30.500 align:start position:0% that a healthy ecosystem requires a number<00:01:28.860> of<00:01:28.950> clients<00:01:29.130> we<00:01:29.490> want<00:01:29.790> a<00:01:29.940> diversity<00:01:30.390> of 00:01:30.500 --> 00:01:30.510 align:start position:0% number of clients we want a diversity of 00:01:30.510 --> 00:01:32.300 align:start position:0% number of clients we want a diversity of approaches<00:01:31.050> we<00:01:31.260> want<00:01:31.530> a<00:01:31.710> diversity<00:01:32.220> of 00:01:32.300 --> 00:01:32.310 align:start position:0% approaches we want a diversity of 00:01:32.310 --> 00:01:34.250 align:start position:0% approaches we want a diversity of techniques<00:01:32.760> and<00:01:32.970> teams<00:01:33.300> all<00:01:33.750> contributing 00:01:34.250 --> 00:01:34.260 align:start position:0% techniques and teams all contributing 00:01:34.260 --> 00:01:36.440 align:start position:0% techniques and teams all contributing ideas<00:01:34.410> and<00:01:34.920> so<00:01:35.340> we<00:01:35.520> thought<00:01:35.730> another<00:01:35.970> a<00:01:36.090> client 00:01:36.440 --> 00:01:36.450 align:start position:0% ideas and so we thought another a client 00:01:36.450 --> 00:01:38.300 align:start position:0% ideas and so we thought another a client could<00:01:36.570> really<00:01:36.720> contribute<00:01:37.020> the<00:01:37.830> second<00:01:38.190> bit 00:01:38.300 --> 00:01:38.310 align:start position:0% could really contribute the second bit 00:01:38.310 --> 00:01:39.920 align:start position:0% could really contribute the second bit though<00:01:38.460> is<00:01:38.520> we<00:01:38.730> really<00:01:39.060> wanted<00:01:39.270> to<00:01:39.420> build<00:01:39.600> our 00:01:39.920 --> 00:01:39.930 align:start position:0% though is we really wanted to build our 00:01:39.930 --> 00:01:41.660 align:start position:0% though is we really wanted to build our capabilities<00:01:40.620> from<00:01:40.740> the<00:01:40.890> ground<00:01:41.100> up<00:01:41.310> and<00:01:41.520> get 00:01:41.660 --> 00:01:41.670 align:start position:0% capabilities from the ground up and get 00:01:41.670 --> 00:01:43.250 align:start position:0% capabilities from the ground up and get into<00:01:41.880> the<00:01:41.970> weeds<00:01:42.210> of<00:01:42.480> the<00:01:42.540> challenges<00:01:43.140> of 00:01:43.250 --> 00:01:43.260 align:start position:0% into the weeds of the challenges of 00:01:43.260 --> 00:01:45.170 align:start position:0% into the weeds of the challenges of building<00:01:43.470> a<00:01:43.890> client<00:01:44.460> that's<00:01:44.880> really 00:01:45.170 --> 00:01:45.180 align:start position:0% building a client that's really 00:01:45.180 --> 00:01:46.610 align:start position:0% building a client that's really important<00:01:45.570> for<00:01:45.660> us<00:01:45.780> because<00:01:45.900> it<00:01:46.110> provides<00:01:46.470> a 00:01:46.610 --> 00:01:46.620 align:start position:0% important for us because it provides a 00:01:46.620 --> 00:01:47.960 align:start position:0% important for us because it provides a foundation<00:01:47.160> for<00:01:47.310> a<00:01:47.370> lot<00:01:47.520> of<00:01:47.610> the<00:01:47.700> research 00:01:47.960 --> 00:01:47.970 align:start position:0% foundation for a lot of the research 00:01:47.970 --> 00:01:49.870 align:start position:0% foundation for a lot of the research efforts<00:01:48.420> we're<00:01:48.630> contributing<00:01:48.930> to<00:01:49.290> as<00:01:49.410> well<00:01:49.590> on 00:01:49.870 --> 00:01:49.880 align:start position:0% efforts we're contributing to as well on 00:01:49.880 --> 00:01:52.730 align:start position:0% efforts we're contributing to as well on aetherium<00:01:50.880> 2.0<00:01:51.450> work<00:01:51.720> as<00:01:51.960> well<00:01:52.260> as<00:01:52.440> some<00:01:52.650> of 00:01:52.730 --> 00:01:52.740 align:start position:0% aetherium 2.0 work as well as some of 00:01:52.740 --> 00:01:55.280 align:start position:0% aetherium 2.0 work as well as some of our<00:01:52.800> enterprise<00:01:53.130> research<00:01:53.760> and<00:01:54.090> you<00:01:55.080> know<00:01:55.140> the 00:01:55.280 --> 00:01:55.290 align:start position:0% our enterprise research and you know the 00:01:55.290 --> 00:01:56.690 align:start position:0% our enterprise research and you know the other<00:01:55.410> bit<00:01:55.650> that's<00:01:56.010> really<00:01:56.250> important<00:01:56.520> to<00:01:56.580> us 00:01:56.690 --> 00:01:56.700 align:start position:0% other bit that's really important to us 00:01:56.700 --> 00:01:58.040 align:start position:0% other bit that's really important to us is<00:01:56.760> we<00:01:56.910> want<00:01:57.060> to<00:01:57.090> help<00:01:57.210> grow<00:01:57.479> the<00:01:57.630> community 00:01:58.040 --> 00:01:58.050 align:start position:0% is we want to help grow the community 00:01:58.050 --> 00:02:00.110 align:start position:0% is we want to help grow the community you<00:01:58.470> know<00:01:58.530> theorem<00:01:59.070> wins<00:01:59.340> and<00:01:59.760> aetherium 00:02:00.110 --> 00:02:00.120 align:start position:0% you know theorem wins and aetherium 00:02:00.120 --> 00:02:01.880 align:start position:0% you know theorem wins and aetherium works<00:02:00.360> and<00:02:00.630> aetherium<00:02:00.870> thrives<00:02:01.260> because<00:02:01.770> of 00:02:01.880 --> 00:02:01.890 align:start position:0% works and aetherium thrives because of 00:02:01.890 --> 00:02:04.780 align:start position:0% works and aetherium thrives because of the<00:02:01.979> community<00:02:02.340> we<00:02:02.490> have<00:02:02.520> and<00:02:03.030> so<00:02:03.660> by<00:02:03.990> enabling 00:02:04.780 --> 00:02:04.790 align:start position:0% the community we have and so by enabling 00:02:04.790 --> 00:02:07.490 align:start position:0% the community we have and so by enabling another<00:02:05.790> language<00:02:06.360> and<00:02:06.750> other<00:02:06.840> team<00:02:07.200> and 00:02:07.490 --> 00:02:07.500 align:start position:0% another language and other team and 00:02:07.500 --> 00:02:09.469 align:start position:0% another language and other team and other<00:02:07.620> set<00:02:07.979> of<00:02:08.010> developers<00:02:08.580> to<00:02:08.640> work<00:02:08.970> with<00:02:09.300> the 00:02:09.469 --> 00:02:09.479 align:start position:0% other set of developers to work with the 00:02:09.479 --> 00:02:12.140 align:start position:0% other set of developers to work with the community<00:02:09.869> we're<00:02:10.410> hoping<00:02:10.770> to<00:02:10.950> grow<00:02:11.280> and<00:02:11.730> and 00:02:12.140 --> 00:02:12.150 align:start position:0% community we're hoping to grow and and 00:02:12.150 --> 00:02:14.720 align:start position:0% community we're hoping to grow and and help<00:02:12.959> this<00:02:13.140> community<00:02:13.200> thrive<00:02:13.770> but<00:02:14.280> the<00:02:14.400> final 00:02:14.720 --> 00:02:14.730 align:start position:0% help this community thrive but the final 00:02:14.730 --> 00:02:15.800 align:start position:0% help this community thrive but the final bit<00:02:14.880> is<00:02:15.000> we<00:02:15.120> also<00:02:15.240> wanted<00:02:15.660> to<00:02:15.690> bring 00:02:15.800 --> 00:02:15.810 align:start position:0% bit is we also wanted to bring 00:02:15.810 --> 00:02:17.780 align:start position:0% bit is we also wanted to bring enterprises<00:02:16.560> to<00:02:16.800> Maine<00:02:16.980> that<00:02:17.010> help 00:02:17.780 --> 00:02:17.790 align:start position:0% enterprises to Maine that help 00:02:17.790 --> 00:02:20.090 align:start position:0% enterprises to Maine that help facilitate<00:02:18.620> enterprises<00:02:19.620> working<00:02:19.980> on 00:02:20.090 --> 00:02:20.100 align:start position:0% facilitate enterprises working on 00:02:20.100 --> 00:02:21.500 align:start position:0% facilitate enterprises working on maintenance<00:02:20.340> and<00:02:20.670> so<00:02:20.970> we<00:02:21.090> built<00:02:21.270> it<00:02:21.360> from<00:02:21.420> the 00:02:21.500 --> 00:02:21.510 align:start position:0% maintenance and so we built it from the 00:02:21.510 --> 00:02:23.449 align:start position:0% maintenance and so we built it from the ground<00:02:21.600> up<00:02:22.050> to<00:02:22.110> be<00:02:22.260> a<00:02:22.350> patchy<00:02:22.620> to<00:02:22.890> license<00:02:23.310> out 00:02:23.449 --> 00:02:23.459 align:start position:0% ground up to be a patchy to license out 00:02:23.459 --> 00:02:25.340 align:start position:0% ground up to be a patchy to license out of<00:02:23.610> the<00:02:23.700> box<00:02:23.880> any<00:02:24.180> Enterprise<00:02:24.660> can<00:02:24.930> take<00:02:25.170> this 00:02:25.340 --> 00:02:25.350 align:start position:0% of the box any Enterprise can take this 00:02:25.350 --> 00:02:27.680 align:start position:0% of the box any Enterprise can take this and<00:02:25.590> play<00:02:25.739> with<00:02:25.920> it<00:02:26.040> and<00:02:26.489> so<00:02:26.850> drilling<00:02:27.570> a 00:02:27.680 --> 00:02:27.690 align:start position:0% and play with it and so drilling a 00:02:27.690 --> 00:02:29.630 align:start position:0% and play with it and so drilling a little<00:02:27.900> deeper<00:02:28.170> into<00:02:28.320> this<00:02:28.590> we<00:02:29.040> chose<00:02:29.280> Java 00:02:29.630 --> 00:02:29.640 align:start position:0% little deeper into this we chose Java 00:02:29.640 --> 00:02:31.670 align:start position:0% little deeper into this we chose Java for<00:02:30.270> a<00:02:30.300> Pantheon<00:02:30.840> for<00:02:31.110> three<00:02:31.320> main<00:02:31.500> reasons 00:02:31.670 --> 00:02:31.680 align:start position:0% for a Pantheon for three main reasons 00:02:31.680 --> 00:02:34.430 align:start position:0% for a Pantheon for three main reasons the<00:02:32.160> first<00:02:32.370> is<00:02:32.730> that<00:02:33.300> Java<00:02:33.930> is<00:02:34.080> a<00:02:34.110> really 00:02:34.430 --> 00:02:34.440 align:start position:0% the first is that Java is a really 00:02:34.440 --> 00:02:36.440 align:start position:0% the first is that Java is a really mature<00:02:34.590> ecosystem<00:02:34.860> and<00:02:35.580> it<00:02:35.730> comes<00:02:35.970> with<00:02:36.060> a<00:02:36.150> lot 00:02:36.440 --> 00:02:36.450 align:start position:0% mature ecosystem and it comes with a lot 00:02:36.450 --> 00:02:39.440 align:start position:0% mature ecosystem and it comes with a lot of<00:02:36.630> free<00:02:37.170> tooling<00:02:37.910> database<00:02:38.910> integrations 00:02:39.440 --> 00:02:39.450 align:start position:0% of free tooling database integrations 00:02:39.450 --> 00:02:40.460 align:start position:0% of free tooling database integrations other<00:02:39.630> sorts<00:02:39.900> of<00:02:39.930> integrations 00:02:40.460 --> 00:02:40.470 align:start position:0% other sorts of integrations 00:02:40.470 --> 00:02:42.440 align:start position:0% other sorts of integrations instrumentation<00:02:41.190> monitoring<00:02:41.760> logging<00:02:42.180> stuff 00:02:42.440 --> 00:02:42.450 align:start position:0% instrumentation monitoring logging stuff 00:02:42.450 --> 00:02:44.300 align:start position:0% instrumentation monitoring logging stuff that<00:02:42.690> you<00:02:42.750> just<00:02:42.930> get<00:02:43.080> for<00:02:43.290> free<00:02:43.470> out<00:02:43.830> of<00:02:44.250> the 00:02:44.300 --> 00:02:44.310 align:start position:0% that you just get for free out of the 00:02:44.310 --> 00:02:45.890 align:start position:0% that you just get for free out of the box<00:02:44.519> with<00:02:44.760> Java<00:02:45.000> which<00:02:45.330> is<00:02:45.450> really<00:02:45.690> exciting 00:02:45.890 --> 00:02:45.900 align:start position:0% box with Java which is really exciting 00:02:45.900 --> 00:02:48.050 align:start position:0% box with Java which is really exciting but<00:02:46.680> it's<00:02:46.800> the<00:02:46.950> second<00:02:47.370> and<00:02:47.519> third<00:02:47.730> reason 00:02:48.050 --> 00:02:48.060 align:start position:0% but it's the second and third reason 00:02:48.060 --> 00:02:51.380 align:start position:0% but it's the second and third reason that<00:02:48.530> excite<00:02:49.530> us<00:02:49.709> the<00:02:49.860> most<00:02:50.040> Java<00:02:50.850> has<00:02:51.150> an 00:02:51.380 --> 00:02:51.390 align:start position:0% that excite us the most Java has an 00:02:51.390 --> 00:02:54.620 align:start position:0% that excite us the most Java has an enormous<00:02:51.860> community<00:02:52.860> of<00:02:53.430> developers<00:02:53.700> that 00:02:54.620 --> 00:02:54.630 align:start position:0% enormous community of developers that 00:02:54.630 --> 00:02:56.780 align:start position:0% enormous community of developers that aren't<00:02:55.019> engaging<00:02:55.380> sufficiently<00:02:56.340> in 00:02:56.780 --> 00:02:56.790 align:start position:0% aren't engaging sufficiently in 00:02:56.790 --> 00:02:58.910 align:start position:0% aren't engaging sufficiently in aetherium<00:02:57.510> right<00:02:57.690> now<00:02:57.840> and<00:02:58.170> they're<00:02:58.680> usually 00:02:58.910 --> 00:02:58.920 align:start position:0% aetherium right now and they're usually 00:02:58.920 --> 00:03:00.590 align:start position:0% aetherium right now and they're usually Enterprise<00:02:59.580> developers<00:03:00.090> and<00:03:00.330> so<00:03:00.450> we're 00:03:00.590 --> 00:03:00.600 align:start position:0% Enterprise developers and so we're 00:03:00.600 --> 00:03:02.479 align:start position:0% Enterprise developers and so we're hoping<00:03:00.989> by<00:03:01.170> delivering<00:03:01.890> Enterprise<00:03:02.280> great 00:03:02.479 --> 00:03:02.489 align:start position:0% hoping by delivering Enterprise great 00:03:02.489 --> 00:03:04.370 align:start position:0% hoping by delivering Enterprise great software<00:03:02.820> we<00:03:02.970> can<00:03:03.120> help<00:03:03.269> port<00:03:03.540> them<00:03:03.720> over<00:03:04.080> here 00:03:04.370 --> 00:03:04.380 align:start position:0% software we can help port them over here 00:03:04.380 --> 00:03:07.370 align:start position:0% software we can help port them over here the<00:03:05.250> final<00:03:05.580> bit<00:03:05.760> is<00:03:06.260> enterprises<00:03:07.260> have 00:03:07.370 --> 00:03:07.380 align:start position:0% the final bit is enterprises have 00:03:07.380 --> 00:03:09.380 align:start position:0% the final bit is enterprises have invested<00:03:07.830> in<00:03:07.920> Java<00:03:08.130> they<00:03:08.519> have<00:03:08.640> Java<00:03:08.880> systems 00:03:09.380 --> 00:03:09.390 align:start position:0% invested in Java they have Java systems 00:03:09.390 --> 00:03:11.180 align:start position:0% invested in Java they have Java systems they<00:03:09.660> have<00:03:09.690> Java<00:03:09.989> talent<00:03:10.470> and<00:03:10.830> it's<00:03:11.010> just 00:03:11.180 --> 00:03:11.190 align:start position:0% they have Java talent and it's just 00:03:11.190 --> 00:03:13.310 align:start position:0% they have Java talent and it's just easier<00:03:11.640> for<00:03:11.700> them<00:03:12.000> to<00:03:12.030> play<00:03:12.330> around<00:03:12.600> on<00:03:12.900> Java 00:03:13.310 --> 00:03:13.320 align:start position:0% easier for them to play around on Java 00:03:13.320 --> 00:03:15.229 align:start position:0% easier for them to play around on Java and<00:03:13.620> so<00:03:14.100> I'm<00:03:14.340> gonna<00:03:14.430> hand<00:03:14.640> over<00:03:14.880> to<00:03:14.970> Shahan 00:03:15.229 --> 00:03:15.239 align:start position:0% and so I'm gonna hand over to Shahan 00:03:15.239 --> 00:03:17.150 align:start position:0% and so I'm gonna hand over to Shahan who'll<00:03:15.450> talk<00:03:15.630> more<00:03:15.900> about<00:03:15.959> our<00:03:16.500> enterprise 00:03:17.150 --> 00:03:17.160 align:start position:0% who'll talk more about our enterprise 00:03:17.160 --> 00:03:20.900 align:start position:0% who'll talk more about our enterprise vision<00:03:17.640> as<00:03:17.760> well<00:03:18.050> hi<00:03:19.050> everybody<00:03:19.350> so<00:03:19.880> one<00:03:20.880> of 00:03:20.900 --> 00:03:20.910 align:start position:0% vision as well hi everybody so one of 00:03:20.910 --> 00:03:24.110 align:start position:0% vision as well hi everybody so one of the<00:03:21.060> reasons<00:03:21.209> why<00:03:21.720> we 00:03:24.110 --> 00:03:24.120 align:start position:0% the reasons why we 00:03:24.120 --> 00:03:27.990 align:start position:0% the reasons why we so<00:03:25.120> why<00:03:26.020> is<00:03:26.080> Pegasus<00:03:26.680> building<00:03:27.040> Pantheon<00:03:27.520> well 00:03:27.990 --> 00:03:28.000 align:start position:0% so why is Pegasus building Pantheon well 00:03:28.000 --> 00:03:30.930 align:start position:0% so why is Pegasus building Pantheon well when<00:03:28.780> we<00:03:29.200> started<00:03:30.100> getting<00:03:30.190> involved<00:03:30.580> in<00:03:30.790> this 00:03:30.930 --> 00:03:30.940 align:start position:0% when we started getting involved in this 00:03:30.940 --> 00:03:33.600 align:start position:0% when we started getting involved in this space<00:03:31.210> we<00:03:31.540> were<00:03:31.720> we<00:03:32.290> were<00:03:32.410> involved<00:03:32.980> in<00:03:33.160> the<00:03:33.220> EA 00:03:33.600 --> 00:03:33.610 align:start position:0% space we were we were involved in the EA 00:03:33.610 --> 00:03:35.820 align:start position:0% space we were we were involved in the EA founding<00:03:34.420> of<00:03:34.510> the<00:03:34.600> EEA<00:03:34.900> we<00:03:35.320> were<00:03:35.440> getting 00:03:35.820 --> 00:03:35.830 align:start position:0% founding of the EEA we were getting 00:03:35.830 --> 00:03:38.010 align:start position:0% founding of the EEA we were getting involved<00:03:36.280> with<00:03:36.370> enterprises<00:03:37.330> forming<00:03:37.900> the 00:03:38.010 --> 00:03:38.020 align:start position:0% involved with enterprises forming the 00:03:38.020 --> 00:03:40.380 align:start position:0% involved with enterprises forming the enterprise<00:03:38.920> aetherium<00:03:39.430> Alliance<00:03:39.820> vision<00:03:40.210> and 00:03:40.380 --> 00:03:40.390 align:start position:0% enterprise aetherium Alliance vision and 00:03:40.390 --> 00:03:42.390 align:start position:0% enterprise aetherium Alliance vision and we<00:03:40.990> were<00:03:41.140> hearing<00:03:41.320> from<00:03:41.500> enterprises<00:03:42.280> that 00:03:42.390 --> 00:03:42.400 align:start position:0% we were hearing from enterprises that 00:03:42.400 --> 00:03:45.030 align:start position:0% we were hearing from enterprises that they<00:03:42.550> wanted<00:03:42.880> to<00:03:42.970> use<00:03:43.150> aetherium<00:03:43.780> well<00:03:44.260> no<00:03:44.680> no 00:03:45.030 --> 00:03:45.040 align:start position:0% they wanted to use aetherium well no no 00:03:45.040 --> 00:03:46.710 align:start position:0% they wanted to use aetherium well no no kidding<00:03:45.370> it's<00:03:45.670> a<00:03:45.820> great<00:03:46.060> platform 00:03:46.710 --> 00:03:46.720 align:start position:0% kidding it's a great platform 00:03:46.720 --> 00:03:50.190 align:start position:0% kidding it's a great platform it's<00:03:46.990> robust<00:03:47.440> it's<00:03:48.010> a<00:03:48.070> resilient<00:03:48.370> and<00:03:48.820> we<00:03:49.720> we 00:03:50.190 --> 00:03:50.200 align:start position:0% it's robust it's a resilient and we we 00:03:50.200 --> 00:03:51.780 align:start position:0% it's robust it's a resilient and we we wanted<00:03:50.500> to<00:03:50.620> hear<00:03:50.800> their<00:03:50.950> requirements<00:03:51.580> so<00:03:51.670> we 00:03:51.780 --> 00:03:51.790 align:start position:0% wanted to hear their requirements so we 00:03:51.790 --> 00:03:54.060 align:start position:0% wanted to hear their requirements so we were<00:03:51.910> trying<00:03:52.630> to<00:03:52.690> ingest<00:03:53.320> their<00:03:53.500> requirements 00:03:54.060 --> 00:03:54.070 align:start position:0% were trying to ingest their requirements 00:03:54.070 --> 00:03:56.910 align:start position:0% were trying to ingest their requirements into<00:03:54.460> the<00:03:54.550> EA<00:03:54.820> vision<00:03:55.480> and<00:03:55.660> then<00:03:56.410> from<00:03:56.740> there 00:03:56.910 --> 00:03:56.920 align:start position:0% into the EA vision and then from there 00:03:56.920 --> 00:03:58.860 align:start position:0% into the EA vision and then from there we<00:03:57.160> started<00:03:57.550> working<00:03:57.730> with<00:03:57.850> customers<00:03:58.150> we 00:03:58.860 --> 00:03:58.870 align:start position:0% we started working with customers we 00:03:58.870 --> 00:04:01.110 align:start position:0% we started working with customers we engage<00:03:59.290> with<00:03:59.500> the<00:03:59.710> government<00:03:59.830> of<00:04:00.190> Dubai<00:04:00.310> we 00:04:01.110 --> 00:04:01.120 align:start position:0% engage with the government of Dubai we 00:04:01.120 --> 00:04:02.340 align:start position:0% engage with the government of Dubai we were<00:04:01.240> hearing<00:04:01.510> from<00:04:01.750> the<00:04:01.840> government<00:04:02.200> that 00:04:02.340 --> 00:04:02.350 align:start position:0% were hearing from the government that 00:04:02.350 --> 00:04:04.250 align:start position:0% were hearing from the government that they<00:04:02.590> wanted<00:04:02.920> to<00:04:02.980> use<00:04:03.100> enterprise-grade 00:04:04.250 --> 00:04:04.260 align:start position:0% they wanted to use enterprise-grade 00:04:04.260 --> 00:04:06.720 align:start position:0% they wanted to use enterprise-grade etherium<00:04:05.260> and<00:04:05.470> they<00:04:05.920> also<00:04:06.130> wanted<00:04:06.580> to<00:04:06.640> use 00:04:06.720 --> 00:04:06.730 align:start position:0% etherium and they also wanted to use 00:04:06.730 --> 00:04:11.520 align:start position:0% etherium and they also wanted to use maenette<00:04:07.720> well<00:04:08.050> no<00:04:08.530> no<00:04:08.950> kidding<00:04:09.310> and<00:04:09.610> so<00:04:10.530> we 00:04:11.520 --> 00:04:11.530 align:start position:0% maenette well no no kidding and so we 00:04:11.530 --> 00:04:14.070 align:start position:0% maenette well no no kidding and so we wanted<00:04:12.220> to<00:04:12.280> bridge<00:04:12.670> these<00:04:12.940> two<00:04:13.080> disparate 00:04:14.070 --> 00:04:14.080 align:start position:0% wanted to bridge these two disparate 00:04:14.080 --> 00:04:15.710 align:start position:0% wanted to bridge these two disparate worlds<00:04:14.290> we<00:04:14.680> wanted<00:04:15.040> to<00:04:15.130> build 00:04:15.710 --> 00:04:15.720 align:start position:0% worlds we wanted to build 00:04:15.720 --> 00:04:18.810 align:start position:0% worlds we wanted to build enterprise-grade<00:04:16.770> maenette<00:04:17.820> technologies 00:04:18.810 --> 00:04:18.820 align:start position:0% enterprise-grade maenette technologies 00:04:18.820 --> 00:04:20.760 align:start position:0% enterprise-grade maenette technologies with<00:04:19.120> that<00:04:19.900> would<00:04:20.080> integrate<00:04:20.380> and 00:04:20.760 --> 00:04:20.770 align:start position:0% with that would integrate and 00:04:20.770 --> 00:04:22.410 align:start position:0% with that would integrate and interoperate<00:04:21.459> with<00:04:21.489> enterprise<00:04:22.180> technology 00:04:22.410 --> 00:04:22.420 align:start position:0% interoperate with enterprise technology 00:04:22.420 --> 00:04:24.900 align:start position:0% interoperate with enterprise technology stacks<00:04:23.110> and<00:04:23.380> that's<00:04:23.980> why<00:04:24.220> Pegasus<00:04:24.760> was 00:04:24.900 --> 00:04:24.910 align:start position:0% stacks and that's why Pegasus was 00:04:24.910 --> 00:04:27.120 align:start position:0% stacks and that's why Pegasus was founded<00:04:25.330> in<00:04:25.480> order<00:04:25.690> to<00:04:25.930> build<00:04:26.050> Pantheon<00:04:26.860> from 00:04:27.120 --> 00:04:27.130 align:start position:0% founded in order to build Pantheon from 00:04:27.130 --> 00:04:29.730 align:start position:0% founded in order to build Pantheon from the<00:04:27.220> ground<00:04:27.400> up<00:04:27.640> in<00:04:28.120> a<00:04:28.540> way<00:04:28.660> that<00:04:28.740> enterprises 00:04:29.730 --> 00:04:29.740 align:start position:0% the ground up in a way that enterprises 00:04:29.740 --> 00:04:31.500 align:start position:0% the ground up in a way that enterprises would<00:04:30.010> be<00:04:30.130> able<00:04:30.220> to<00:04:30.370> incorporate<00:04:30.730> into<00:04:31.270> their 00:04:31.500 --> 00:04:31.510 align:start position:0% would be able to incorporate into their 00:04:31.510 --> 00:04:35.700 align:start position:0% would be able to incorporate into their technology<00:04:32.080> stacks<00:04:33.330> so<00:04:34.330> where<00:04:34.870> is<00:04:35.050> Pegasus 00:04:35.700 --> 00:04:35.710 align:start position:0% technology stacks so where is Pegasus 00:04:35.710 --> 00:04:38.250 align:start position:0% technology stacks so where is Pegasus well<00:04:35.890> Pegasus<00:04:36.460> is<00:04:36.610> a<00:04:36.640> global<00:04:37.120> group<00:04:37.750> where<00:04:38.230> a 00:04:38.250 --> 00:04:38.260 align:start position:0% well Pegasus is a global group where a 00:04:38.260 --> 00:04:41.490 align:start position:0% well Pegasus is a global group where a group<00:04:38.560> of<00:04:38.800> 50<00:04:39.250> people<00:04:39.510> in<00:04:40.510> Australia<00:04:41.080> Europe 00:04:41.490 --> 00:04:41.500 align:start position:0% group of 50 people in Australia Europe 00:04:41.500 --> 00:04:44.100 align:start position:0% group of 50 people in Australia Europe and<00:04:41.890> North<00:04:42.280> America<00:04:42.430> we<00:04:43.390> have<00:04:43.540> three<00:04:43.870> main 00:04:44.100 --> 00:04:44.110 align:start position:0% and North America we have three main 00:04:44.110 --> 00:04:47.160 align:start position:0% and North America we have three main three<00:04:45.010> main<00:04:45.190> prongs<00:04:45.490> we<00:04:46.180> have<00:04:46.360> product<00:04:46.990> which 00:04:47.160 --> 00:04:47.170 align:start position:0% three main prongs we have product which 00:04:47.170 --> 00:04:49.350 align:start position:0% three main prongs we have product which is<00:04:47.320> building<00:04:47.650> Pantheon<00:04:48.160> which<00:04:48.400> is<00:04:48.610> focused<00:04:49.210> on 00:04:49.350 --> 00:04:49.360 align:start position:0% is building Pantheon which is focused on 00:04:49.360 --> 00:04:51.630 align:start position:0% is building Pantheon which is focused on maenette<00:04:49.930> maenette<00:04:50.830> is<00:04:50.980> our<00:04:51.160> number<00:04:51.490> one 00:04:51.630 --> 00:04:51.640 align:start position:0% maenette maenette is our number one 00:04:51.640 --> 00:04:54.000 align:start position:0% maenette maenette is our number one priority<00:04:51.670> and<00:04:52.390> at<00:04:53.170> the<00:04:53.290> same<00:04:53.470> time<00:04:53.710> we<00:04:53.890> are 00:04:54.000 --> 00:04:54.010 align:start position:0% priority and at the same time we are 00:04:54.010 --> 00:04:55.860 align:start position:0% priority and at the same time we are building<00:04:54.190> Enterprise<00:04:54.940> modules<00:04:55.450> for 00:04:55.860 --> 00:04:55.870 align:start position:0% building Enterprise modules for 00:04:55.870 --> 00:04:58.020 align:start position:0% building Enterprise modules for aetherium<00:04:56.500> enterprise-grade<00:04:57.160> aetherium<00:04:57.850> and 00:04:58.020 --> 00:04:58.030 align:start position:0% aetherium enterprise-grade aetherium and 00:04:58.030 --> 00:05:00.360 align:start position:0% aetherium enterprise-grade aetherium and at<00:04:58.840> the<00:04:58.990> same<00:04:59.170> time<00:04:59.380> we're<00:04:59.590> doing<00:04:59.860> a<00:05:00.070> research 00:05:00.360 --> 00:05:00.370 align:start position:0% at the same time we're doing a research 00:05:00.370 --> 00:05:03.060 align:start position:0% at the same time we're doing a research and<00:05:00.610> development<00:05:00.930> with<00:05:01.930> the<00:05:02.530> if<00:05:02.740> they're<00:05:02.980> in 00:05:03.060 --> 00:05:03.070 align:start position:0% and development with the if they're in 00:05:03.070 --> 00:05:05.190 align:start position:0% and development with the if they're in foundation<00:05:03.700> we're<00:05:03.910> focus<00:05:04.570> on<00:05:04.750> if<00:05:04.930> their<00:05:05.080> iam 00:05:05.190 --> 00:05:05.200 align:start position:0% foundation we're focus on if their iam 00:05:05.200 --> 00:05:08.190 align:start position:0% foundation we're focus on if their iam 2.0<00:05:05.710> we're<00:05:06.250> focused<00:05:06.700> on<00:05:06.790> Enterprise<00:05:07.720> ethereum 00:05:08.190 --> 00:05:08.200 align:start position:0% 2.0 we're focused on Enterprise ethereum 00:05:08.200 --> 00:05:10.380 align:start position:0% 2.0 we're focused on Enterprise ethereum we're<00:05:08.650> we're<00:05:09.460> working<00:05:09.850> on<00:05:09.940> Enterprise 00:05:10.380 --> 00:05:10.390 align:start position:0% we're we're working on Enterprise 00:05:10.390 --> 00:05:12.470 align:start position:0% we're we're working on Enterprise modules<00:05:10.930> like<00:05:11.430> interoperability 00:05:12.470 --> 00:05:12.480 align:start position:0% modules like interoperability 00:05:12.480 --> 00:05:14.820 align:start position:0% modules like interoperability scalability<00:05:13.480> working<00:05:14.320> with<00:05:14.440> existing 00:05:14.820 --> 00:05:14.830 align:start position:0% scalability working with existing 00:05:14.830 --> 00:05:17.280 align:start position:0% scalability working with existing technology<00:05:15.520> stacks<00:05:15.820> and<00:05:16.210> at<00:05:16.750> the<00:05:16.870> same<00:05:17.050> time 00:05:17.280 --> 00:05:17.290 align:start position:0% technology stacks and at the same time 00:05:17.290 --> 00:05:18.900 align:start position:0% technology stacks and at the same time we<00:05:17.500> have<00:05:17.620> a<00:05:17.650> standards<00:05:18.130> group<00:05:18.370> that<00:05:18.730> is 00:05:18.900 --> 00:05:18.910 align:start position:0% we have a standards group that is 00:05:18.910 --> 00:05:22.260 align:start position:0% we have a standards group that is helping<00:05:19.330> to<00:05:19.540> bring<00:05:20.290> maenette<00:05:21.040> standards<00:05:21.550> into 00:05:22.260 --> 00:05:22.270 align:start position:0% helping to bring maenette standards into 00:05:22.270 --> 00:05:24.900 align:start position:0% helping to bring maenette standards into the<00:05:22.840> enterprise<00:05:23.380> group<00:05:23.620> an<00:05:24.040> enterprise<00:05:24.790> space 00:05:24.900 --> 00:05:24.910 align:start position:0% the enterprise group an enterprise space 00:05:24.910 --> 00:05:28.410 align:start position:0% the enterprise group an enterprise space so<00:05:25.450> that<00:05:25.480> enterprises<00:05:26.260> can<00:05:26.470> have<00:05:27.150> trust<00:05:28.150> that 00:05:28.410 --> 00:05:28.420 align:start position:0% so that enterprises can have trust that 00:05:28.420 --> 00:05:30.600 align:start position:0% so that enterprises can have trust that they<00:05:28.960> can<00:05:29.170> use<00:05:29.380> may<00:05:29.650> not<00:05:29.830> technologies<00:05:30.430> in 00:05:30.600 --> 00:05:30.610 align:start position:0% they can use may not technologies in 00:05:30.610 --> 00:05:32.940 align:start position:0% they can use may not technologies in their<00:05:30.910> technology<00:05:31.240> stack 00:05:32.940 --> 00:05:32.950 align:start position:0% their technology stack 00:05:32.950 --> 00:05:35.490 align:start position:0% their technology stack and<00:05:33.070> now<00:05:33.730> I<00:05:33.760> will<00:05:34.180> hand<00:05:34.390> it<00:05:34.480> over<00:05:34.600> to<00:05:34.810> Rob<00:05:35.290> who 00:05:35.490 --> 00:05:35.500 align:start position:0% and now I will hand it over to Rob who 00:05:35.500 --> 00:05:37.800 align:start position:0% and now I will hand it over to Rob who will<00:05:35.590> talk<00:05:35.770> demo<00:05:36.550> Pantheon<00:05:37.150> and<00:05:37.300> talk<00:05:37.570> about 00:05:37.800 --> 00:05:37.810 align:start position:0% will talk demo Pantheon and talk about 00:05:37.810 --> 00:05:45.030 align:start position:0% will talk demo Pantheon and talk about the<00:05:37.900> roadmap<00:05:40.920> so<00:05:43.350> while<00:05:44.350> it<00:05:44.530> was<00:05:44.620> kind<00:05:44.770> of<00:05:44.860> cool 00:05:45.030 --> 00:05:45.040 align:start position:0% the roadmap so while it was kind of cool 00:05:45.040 --> 00:05:47.790 align:start position:0% the roadmap so while it was kind of cool showing<00:05:45.400> like<00:05:45.580> a<00:05:45.610> screenshot<00:05:46.150> of<00:05:46.570> stats<00:05:47.410> it's 00:05:47.790 --> 00:05:47.800 align:start position:0% showing like a screenshot of stats it's 00:05:47.800 --> 00:05:49.350 align:start position:0% showing like a screenshot of stats it's actually<00:05:48.190> kind<00:05:48.400> of<00:05:48.460> nice<00:05:48.610> to<00:05:48.730> see<00:05:48.790> software<00:05:49.270> as 00:05:49.350 --> 00:05:49.360 align:start position:0% actually kind of nice to see software as 00:05:49.360 --> 00:05:52.380 align:start position:0% actually kind of nice to see software as well<00:05:49.590> so<00:05:50.590> I'll<00:05:51.160> start<00:05:51.520> off<00:05:51.640> by<00:05:51.670> showing<00:05:52.060> we've 00:05:52.380 --> 00:05:52.390 align:start position:0% well so I'll start off by showing we've 00:05:52.390 --> 00:05:54.870 align:start position:0% well so I'll start off by showing we've created<00:05:52.600> a<00:05:52.990> QuickStart<00:05:53.950> that<00:05:54.250> we<00:05:54.370> ship<00:05:54.640> as<00:05:54.850> a 00:05:54.870 --> 00:05:54.880 align:start position:0% created a QuickStart that we ship as a 00:05:54.880 --> 00:05:57.210 align:start position:0% created a QuickStart that we ship as a part<00:05:55.210> of<00:05:55.300> Pantheon<00:05:55.750> and<00:05:55.930> I'll<00:05:56.620> start<00:05:56.890> by<00:05:57.040> just 00:05:57.210 --> 00:05:57.220 align:start position:0% part of Pantheon and I'll start by just 00:05:57.220 --> 00:06:02.430 align:start position:0% part of Pantheon and I'll start by just running<00:05:57.400> that<00:05:57.580> up<00:05:58.470> and<00:06:00.600> I<00:06:01.600> won't<00:06:01.870> stop<00:06:02.410> it 00:06:02.430 --> 00:06:02.440 align:start position:0% running that up and I won't stop it 00:06:02.440 --> 00:06:04.380 align:start position:0% running that up and I won't stop it first<00:06:02.860> it's<00:06:03.100> already<00:06:03.310> stopped<00:06:03.550> so<00:06:03.880> we'll 00:06:04.380 --> 00:06:04.390 align:start position:0% first it's already stopped so we'll 00:06:04.390 --> 00:06:05.490 align:start position:0% first it's already stopped so we'll start<00:06:04.570> with<00:06:04.630> they're<00:06:04.810> running<00:06:05.050> the<00:06:05.140> private 00:06:05.490 --> 00:06:05.500 align:start position:0% start with they're running the private 00:06:05.500 --> 00:06:07.140 align:start position:0% start with they're running the private private<00:06:05.920> network<00:06:06.160> so<00:06:06.340> this<00:06:06.460> is<00:06:06.550> just<00:06:06.670> a<00:06:06.820> series 00:06:07.140 --> 00:06:07.150 align:start position:0% private network so this is just a series 00:06:07.150 --> 00:06:11.160 align:start position:0% private network so this is just a series of<00:06:07.180> docker<00:06:07.690> docker<00:06:08.380> images<00:06:09.120> running<00:06:10.120> a<00:06:10.600> few 00:06:11.160 --> 00:06:11.170 align:start position:0% of docker docker images running a few 00:06:11.170 --> 00:06:14.670 align:start position:0% of docker docker images running a few notes<00:06:11.380> and<00:06:11.740> a<00:06:12.780> nice<00:06:13.780> little<00:06:14.080> block<00:06:14.260> Explorer 00:06:14.670 --> 00:06:14.680 align:start position:0% notes and a nice little block Explorer 00:06:14.680 --> 00:06:17.550 align:start position:0% notes and a nice little block Explorer that's<00:06:14.890> been<00:06:15.010> built<00:06:15.220> by<00:06:15.340> alessio<00:06:16.200> so<00:06:17.200> as<00:06:17.410> this 00:06:17.550 --> 00:06:17.560 align:start position:0% that's been built by alessio so as this 00:06:17.560 --> 00:06:19.590 align:start position:0% that's been built by alessio so as this is<00:06:17.620> started<00:06:18.370> I'm<00:06:18.880> going<00:06:19.030> to<00:06:19.120> quickly<00:06:19.330> go 00:06:19.590 --> 00:06:19.600 align:start position:0% is started I'm going to quickly go 00:06:19.600 --> 00:06:22.290 align:start position:0% is started I'm going to quickly go across<00:06:19.870> and<00:06:20.290> go<00:06:21.040> to<00:06:21.100> our<00:06:21.460> acceptance<00:06:21.940> tests<00:06:22.150> so 00:06:22.290 --> 00:06:22.300 align:start position:0% across and go to our acceptance tests so 00:06:22.300 --> 00:06:24.210 align:start position:0% across and go to our acceptance tests so we<00:06:22.330> take<00:06:22.660> I<00:06:22.900> guess<00:06:23.260> our<00:06:23.650> software<00:06:24.070> really 00:06:24.210 --> 00:06:24.220 align:start position:0% we take I guess our software really 00:06:24.220 --> 00:06:25.590 align:start position:0% we take I guess our software really seriously<00:06:24.670> we've<00:06:24.880> got<00:06:25.000> a<00:06:25.030> great<00:06:25.300> set<00:06:25.570> of 00:06:25.590 --> 00:06:25.600 align:start position:0% seriously we've got a great set of 00:06:25.600 --> 00:06:27.300 align:start position:0% seriously we've got a great set of acceptance<00:06:26.410> tests<00:06:26.650> that<00:06:26.800> we<00:06:26.890> are<00:06:27.010> regularly 00:06:27.300 --> 00:06:27.310 align:start position:0% acceptance tests that we are regularly 00:06:27.310 --> 00:06:29.310 align:start position:0% acceptance tests that we are regularly running<00:06:27.610> on<00:06:27.730> commit<00:06:28.180> and<00:06:28.390> then<00:06:28.930> some<00:06:29.170> extra 00:06:29.310 --> 00:06:29.320 align:start position:0% running on commit and then some extra 00:06:29.320 --> 00:06:30.900 align:start position:0% running on commit and then some extra acceptance<00:06:29.950> tests<00:06:30.220> that<00:06:30.310> we<00:06:30.430> have<00:06:30.610> sort<00:06:30.820> of 00:06:30.900 --> 00:06:30.910 align:start position:0% acceptance tests that we have sort of 00:06:30.910 --> 00:06:33.270 align:start position:0% acceptance tests that we have sort of running<00:06:31.060> as<00:06:31.300> well<00:06:31.540> so<00:06:32.290> we've<00:06:32.380> got<00:06:32.500> truffle<00:06:33.040> is 00:06:33.270 --> 00:06:33.280 align:start position:0% running as well so we've got truffle is 00:06:33.280 --> 00:06:34.920 align:start position:0% running as well so we've got truffle is one<00:06:33.400> of<00:06:33.490> the<00:06:33.610> tools<00:06:33.820> that<00:06:33.940> we<00:06:34.090> think<00:06:34.120> is<00:06:34.480> pretty 00:06:34.920 --> 00:06:34.930 align:start position:0% one of the tools that we think is pretty 00:06:34.930 --> 00:06:36.950 align:start position:0% one of the tools that we think is pretty important<00:06:35.500> for<00:06:35.560> us<00:06:35.680> to<00:06:35.800> be<00:06:35.860> able<00:06:35.950> to<00:06:36.070> support 00:06:36.950 --> 00:06:36.960 align:start position:0% important for us to be able to support 00:06:36.960 --> 00:06:40.860 align:start position:0% important for us to be able to support and<00:06:38.310> so<00:06:39.310> it's<00:06:39.790> what<00:06:40.000> we're<00:06:40.120> running<00:06:40.210> and<00:06:40.690> so 00:06:40.860 --> 00:06:40.870 align:start position:0% and so it's what we're running and so 00:06:40.870 --> 00:06:42.090 align:start position:0% and so it's what we're running and so I'm<00:06:40.960> going<00:06:41.080> to<00:06:41.170> use<00:06:41.320> that<00:06:41.500> and<00:06:41.800> we're<00:06:42.010> gonna 00:06:42.090 --> 00:06:42.100 align:start position:0% I'm going to use that and we're gonna 00:06:42.100 --> 00:06:43.430 align:start position:0% I'm going to use that and we're gonna kick<00:06:42.310> off<00:06:42.400> we're<00:06:42.580> gonna<00:06:42.700> get<00:06:42.850> some 00:06:43.430 --> 00:06:43.440 align:start position:0% kick off we're gonna get some 00:06:43.440 --> 00:06:45.360 align:start position:0% kick off we're gonna get some transactions<00:06:44.440> happening<00:06:44.830> in<00:06:44.950> our<00:06:45.040> chain 00:06:45.360 --> 00:06:45.370 align:start position:0% transactions happening in our chain 00:06:45.370 --> 00:06:46.920 align:start position:0% transactions happening in our chain we're<00:06:45.670> going<00:06:45.790> to<00:06:45.850> get<00:06:45.940> some<00:06:46.180> things<00:06:46.360> happening 00:06:46.920 --> 00:06:46.930 align:start position:0% we're going to get some things happening 00:06:46.930 --> 00:06:49.050 align:start position:0% we're going to get some things happening some<00:06:47.140> real<00:06:47.350> blocks<00:06:47.650> actually<00:06:48.160> being<00:06:48.580> created 00:06:49.050 --> 00:06:49.060 align:start position:0% some real blocks actually being created 00:06:49.060 --> 00:06:51.630 align:start position:0% some real blocks actually being created and<00:06:49.560> transactions<00:06:50.560> inside<00:06:50.830> those<00:06:51.010> blocks<00:06:51.310> we 00:06:51.630 --> 00:06:51.640 align:start position:0% and transactions inside those blocks we 00:06:51.640 --> 00:06:53.190 align:start position:0% and transactions inside those blocks we can<00:06:51.760> see<00:06:51.910> that<00:06:52.090> things<00:06:52.330> are<00:06:52.450> compiling<00:06:52.810> and 00:06:53.190 --> 00:06:53.200 align:start position:0% can see that things are compiling and 00:06:53.200 --> 00:06:55.650 align:start position:0% can see that things are compiling and working<00:06:53.620> there<00:06:53.830> you'll<00:06:54.700> see<00:06:54.940> up<00:06:55.150> there<00:06:55.390> as 00:06:55.650 --> 00:06:55.660 align:start position:0% working there you'll see up there as 00:06:55.660 --> 00:06:57.630 align:start position:0% working there you'll see up there as well<00:06:55.810> in<00:06:56.050> the<00:06:56.200> blue<00:06:56.440> we've<00:06:56.710> got<00:06:56.890> a<00:06:56.920> series<00:06:57.430> of 00:06:57.630 --> 00:06:57.640 align:start position:0% well in the blue we've got a series of 00:06:57.640 --> 00:06:59.910 align:start position:0% well in the blue we've got a series of services<00:06:58.570> that<00:06:58.930> are<00:06:59.020> running<00:06:59.110> on<00:06:59.530> our 00:06:59.910 --> 00:06:59.920 align:start position:0% services that are running on our 00:06:59.920 --> 00:07:01.590 align:start position:0% services that are running on our QuickStart<00:07:00.250> so<00:07:00.640> we've<00:07:00.730> got<00:07:00.820> a<00:07:00.850> HTTP<00:07:01.390> endpoint 00:07:01.590 --> 00:07:01.600 align:start position:0% QuickStart so we've got a HTTP endpoint 00:07:01.600 --> 00:07:03.480 align:start position:0% QuickStart so we've got a HTTP endpoint that's<00:07:02.440> what<00:07:02.560> our<00:07:02.650> truffle<00:07:02.950> is<00:07:03.010> interacting 00:07:03.480 --> 00:07:03.490 align:start position:0% that's what our truffle is interacting 00:07:03.490 --> 00:07:05.930 align:start position:0% that's what our truffle is interacting with<00:07:03.640> right<00:07:03.910> now<00:07:04.180> there's<00:07:05.110> a<00:07:05.170> WebSocket 00:07:05.930 --> 00:07:05.940 align:start position:0% with right now there's a WebSocket 00:07:05.940 --> 00:07:08.340 align:start position:0% with right now there's a WebSocket endpoints<00:07:06.940> so<00:07:07.030> that's<00:07:07.210> supporting<00:07:08.170> the 00:07:08.340 --> 00:07:08.350 align:start position:0% endpoints so that's supporting the 00:07:08.350 --> 00:07:11.400 align:start position:0% endpoints so that's supporting the pub/sub<00:07:08.860> API<00:07:09.190> which<00:07:09.550> is<00:07:10.390> sort<00:07:10.990> of<00:07:11.050> well<00:07:11.200> known 00:07:11.400 --> 00:07:11.410 align:start position:0% pub/sub API which is sort of well known 00:07:11.410 --> 00:07:13.770 align:start position:0% pub/sub API which is sort of well known and<00:07:11.650> being<00:07:11.860> more<00:07:12.460> well<00:07:12.670> established<00:07:13.180> now<00:07:13.510> and 00:07:13.770 --> 00:07:13.780 align:start position:0% and being more well established now and 00:07:13.780 --> 00:07:15.960 align:start position:0% and being more well established now and there's<00:07:14.500> also<00:07:14.620> the<00:07:14.950> block<00:07:15.280> Explorer<00:07:15.670> sitting 00:07:15.960 --> 00:07:15.970 align:start position:0% there's also the block Explorer sitting 00:07:15.970 --> 00:07:17.550 align:start position:0% there's also the block Explorer sitting there<00:07:16.090> as<00:07:16.180> well<00:07:16.330> so<00:07:16.840> I'll<00:07:16.930> go<00:07:17.050> through<00:07:17.320> and 00:07:17.550 --> 00:07:17.560 align:start position:0% there as well so I'll go through and 00:07:17.560 --> 00:07:20.010 align:start position:0% there as well so I'll go through and show<00:07:17.620> you<00:07:17.950> our<00:07:18.390> connecting<00:07:19.390> into<00:07:19.540> the 00:07:20.010 --> 00:07:20.020 align:start position:0% show you our connecting into the 00:07:20.020 --> 00:07:22.140 align:start position:0% show you our connecting into the WebSocket<00:07:20.830> so<00:07:21.340> it's<00:07:21.460> just<00:07:21.610> using<00:07:21.790> a<00:07:22.000> normal 00:07:22.140 --> 00:07:22.150 align:start position:0% WebSocket so it's just using a normal 00:07:22.150 --> 00:07:25.470 align:start position:0% WebSocket so it's just using a normal simple<00:07:23.140> WebSocket<00:07:23.770> client<00:07:24.160> Chrome<00:07:24.970> extension 00:07:25.470 --> 00:07:25.480 align:start position:0% simple WebSocket client Chrome extension 00:07:25.480 --> 00:07:27.180 align:start position:0% simple WebSocket client Chrome extension sitting<00:07:25.840> here<00:07:26.020> so<00:07:26.380> I'm<00:07:26.470> just<00:07:26.620> going<00:07:26.770> to<00:07:26.800> open<00:07:27.100> a 00:07:27.180 --> 00:07:27.190 align:start position:0% sitting here so I'm just going to open a 00:07:27.190 --> 00:07:30.960 align:start position:0% sitting here so I'm just going to open a connection<00:07:27.610> to<00:07:27.970> that<00:07:28.120> WebSocket<00:07:28.750> and<00:07:29.820> send<00:07:30.820> in 00:07:30.960 --> 00:07:30.970 align:start position:0% connection to that WebSocket and send in 00:07:30.970 --> 00:07:33.540 align:start position:0% connection to that WebSocket and send in a<00:07:31.240> subscribe<00:07:32.230> telling<00:07:33.160> it<00:07:33.280> that<00:07:33.430> we're 00:07:33.540 --> 00:07:33.550 align:start position:0% a subscribe telling it that we're 00:07:33.550 --> 00:07:35.540 align:start position:0% a subscribe telling it that we're subscribing<00:07:34.030> to<00:07:34.150> the<00:07:34.270> new<00:07:34.420> heads<00:07:34.630> events<00:07:35.020> and 00:07:35.540 --> 00:07:35.550 align:start position:0% subscribing to the new heads events and 00:07:35.550 --> 00:07:39.240 align:start position:0% subscribing to the new heads events and if<00:07:36.550> the<00:07:36.910> demo<00:07:37.360> gods<00:07:37.630> are<00:07:37.840> kind<00:07:38.170> we'll<00:07:38.710> start<00:07:39.100> to 00:07:39.240 --> 00:07:39.250 align:start position:0% if the demo gods are kind we'll start to 00:07:39.250 --> 00:07:42.180 align:start position:0% if the demo gods are kind we'll start to see<00:07:39.280> some<00:07:40.650> transactions<00:07:41.650> coming<00:07:41.860> through<00:07:42.010> and 00:07:42.180 --> 00:07:42.190 align:start position:0% see some transactions coming through and 00:07:42.190 --> 00:07:43.790 align:start position:0% see some transactions coming through and there<00:07:42.760> we<00:07:42.880> go<00:07:43.060> so<00:07:43.420> ever 00:07:43.790 --> 00:07:43.800 align:start position:0% there we go so ever 00:07:43.800 --> 00:07:49.879 align:start position:0% there we go so ever we've<00:07:44.430> got<00:07:44.550> blocks<00:07:44.789> being<00:07:45.000> created<00:07:48.889> switch 00:07:49.879 --> 00:07:49.889 align:start position:0% we've got blocks being created switch 00:07:49.889 --> 00:07:51.980 align:start position:0% we've got blocks being created switch across<00:07:50.099> now<00:07:50.400> to<00:07:50.460> our<00:07:50.669> block<00:07:51.300> Explorer<00:07:51.750> which 00:07:51.980 --> 00:07:51.990 align:start position:0% across now to our block Explorer which 00:07:51.990 --> 00:07:55.339 align:start position:0% across now to our block Explorer which ships<00:07:52.229> is<00:07:52.380> a<00:07:52.410> part<00:07:52.740> of<00:07:52.979> the<00:07:53.810> test<00:07:54.810> network<00:07:55.199> that 00:07:55.339 --> 00:07:55.349 align:start position:0% ships is a part of the test network that 00:07:55.349 --> 00:07:57.439 align:start position:0% ships is a part of the test network that we've<00:07:55.440> got<00:07:55.590> sitting<00:07:55.889> there<00:07:56.099> and<00:07:56.400> we<00:07:57.270> should 00:07:57.439 --> 00:07:57.449 align:start position:0% we've got sitting there and we should 00:07:57.449 --> 00:07:58.760 align:start position:0% we've got sitting there and we should start<00:07:57.690> to<00:07:57.840> see<00:07:57.990> that<00:07:58.169> the<00:07:58.319> best<00:07:58.470> blocks 00:07:58.760 --> 00:07:58.770 align:start position:0% start to see that the best blocks 00:07:58.770 --> 00:08:00.860 align:start position:0% start to see that the best blocks numbers<00:07:59.490> will<00:07:59.729> be<00:07:59.849> increasing<00:08:00.479> there<00:08:00.660> so<00:08:00.780> you 00:08:00.860 --> 00:08:00.870 align:start position:0% numbers will be increasing there so you 00:08:00.870 --> 00:08:02.270 align:start position:0% numbers will be increasing there so you can<00:08:00.990> see<00:08:01.169> that<00:08:01.380> the<00:08:01.620> blocks<00:08:01.889> are<00:08:02.039> going 00:08:02.270 --> 00:08:02.280 align:start position:0% can see that the blocks are going 00:08:02.280 --> 00:08:04.400 align:start position:0% can see that the blocks are going through<00:08:02.400> this<00:08:02.580> is<00:08:02.639> a<00:08:02.970> new<00:08:03.630> block<00:08:03.930> Explorer 00:08:04.400 --> 00:08:04.410 align:start position:0% through this is a new block Explorer 00:08:04.410 --> 00:08:07.100 align:start position:0% through this is a new block Explorer that's<00:08:04.710> been<00:08:04.860> produced<00:08:05.280> by<00:08:05.460> the<00:08:05.569> team<00:08:06.599> Alessio 00:08:07.100 --> 00:08:07.110 align:start position:0% that's been produced by the team Alessio 00:08:07.110 --> 00:08:08.930 align:start position:0% that's been produced by the team Alessio they're<00:08:07.860> going<00:08:08.009> to<00:08:08.099> be<00:08:08.160> open<00:08:08.430> sourcing<00:08:08.849> this 00:08:08.930 --> 00:08:08.940 align:start position:0% they're going to be open sourcing this 00:08:08.940 --> 00:08:10.550 align:start position:0% they're going to be open sourcing this and<00:08:09.210> making<00:08:09.419> it<00:08:09.509> available<00:08:09.630> for<00:08:10.319> people<00:08:10.440> to 00:08:10.550 --> 00:08:10.560 align:start position:0% and making it available for people to 00:08:10.560 --> 00:08:11.930 align:start position:0% and making it available for people to have<00:08:10.710> on<00:08:10.860> their<00:08:10.979> own<00:08:11.009> private<00:08:11.280> networks<00:08:11.759> as 00:08:11.930 --> 00:08:11.940 align:start position:0% have on their own private networks as 00:08:11.940 --> 00:08:14.240 align:start position:0% have on their own private networks as well<00:08:12.110> so<00:08:13.110> you<00:08:13.169> can<00:08:13.410> see<00:08:13.590> it's<00:08:13.710> kind<00:08:13.919> of<00:08:13.979> a<00:08:14.069> nice 00:08:14.240 --> 00:08:14.250 align:start position:0% well so you can see it's kind of a nice 00:08:14.250 --> 00:08:15.950 align:start position:0% well so you can see it's kind of a nice clean<00:08:14.580> simple<00:08:15.180> interface<00:08:15.539> that<00:08:15.690> we've<00:08:15.810> got 00:08:15.950 --> 00:08:15.960 align:start position:0% clean simple interface that we've got 00:08:15.960 --> 00:08:17.570 align:start position:0% clean simple interface that we've got sitting<00:08:16.199> here<00:08:16.440> if<00:08:16.680> I<00:08:16.770> go<00:08:16.919> into<00:08:17.069> that<00:08:17.190> best 00:08:17.570 --> 00:08:17.580 align:start position:0% sitting here if I go into that best 00:08:17.580 --> 00:08:19.309 align:start position:0% sitting here if I go into that best block<00:08:17.849> you<00:08:18.000> can<00:08:18.090> also<00:08:18.210> see<00:08:18.509> I<00:08:18.750> guess<00:08:19.169> some 00:08:19.309 --> 00:08:19.319 align:start position:0% block you can also see I guess some 00:08:19.319 --> 00:08:20.559 align:start position:0% block you can also see I guess some things<00:08:19.349> you<00:08:19.620> can<00:08:19.770> see<00:08:19.949> there<00:08:20.130> so<00:08:20.159> we've<00:08:20.430> got 00:08:20.559 --> 00:08:20.569 align:start position:0% things you can see there so we've got 00:08:20.569 --> 00:08:24.020 align:start position:0% things you can see there so we've got six<00:08:21.569> peers<00:08:21.960> on<00:08:22.139> our<00:08:22.259> network<00:08:22.590> so<00:08:22.620> that<00:08:23.030> docker 00:08:24.020 --> 00:08:24.030 align:start position:0% six peers on our network so that docker 00:08:24.030 --> 00:08:25.520 align:start position:0% six peers on our network so that docker network<00:08:24.389> that<00:08:24.539> I<00:08:24.569> have<00:08:24.750> sitting<00:08:25.080> there<00:08:25.319> has 00:08:25.520 --> 00:08:25.530 align:start position:0% network that I have sitting there has 00:08:25.530 --> 00:08:27.290 align:start position:0% network that I have sitting there has six<00:08:25.800> peers<00:08:26.130> sort<00:08:26.370> of<00:08:26.430> sitting<00:08:26.610> in<00:08:26.819> connecting 00:08:27.290 --> 00:08:27.300 align:start position:0% six peers sort of sitting in connecting 00:08:27.300 --> 00:08:29.960 align:start position:0% six peers sort of sitting in connecting talking<00:08:27.630> to<00:08:27.720> each<00:08:27.840> other<00:08:28.069> our<00:08:29.069> best<00:08:29.310> block<00:08:29.580> is 00:08:29.960 --> 00:08:29.970 align:start position:0% talking to each other our best block is 00:08:29.970 --> 00:08:32.029 align:start position:0% talking to each other our best block is sitting<00:08:30.360> there<00:08:30.509> and<00:08:30.780> you<00:08:31.349> can<00:08:31.470> see<00:08:31.620> that<00:08:31.740> the 00:08:32.029 --> 00:08:32.039 align:start position:0% sitting there and you can see that the 00:08:32.039 --> 00:08:33.769 align:start position:0% sitting there and you can see that the current<00:08:32.399> head<00:08:32.669> block<00:08:33.000> there<00:08:33.300> doesn't<00:08:33.690> have 00:08:33.769 --> 00:08:33.779 align:start position:0% current head block there doesn't have 00:08:33.779 --> 00:08:35.750 align:start position:0% current head block there doesn't have any<00:08:33.959> transactions<00:08:34.560> in<00:08:34.680> it<00:08:34.800> we're<00:08:35.339> mining 00:08:35.750 --> 00:08:35.760 align:start position:0% any transactions in it we're mining 00:08:35.760 --> 00:08:37.790 align:start position:0% any transactions in it we're mining pretty<00:08:36.060> rapidly<00:08:36.479> in<00:08:36.750> this<00:08:36.899> network<00:08:37.140> so<00:08:37.349> that 00:08:37.790 --> 00:08:37.800 align:start position:0% pretty rapidly in this network so that 00:08:37.800 --> 00:08:40.339 align:start position:0% pretty rapidly in this network so that we<00:08:38.010> can<00:08:38.300> keep<00:08:39.300> seeing<00:08:39.570> our<00:08:39.690> transactions<00:08:40.169> come 00:08:40.339 --> 00:08:40.349 align:start position:0% we can keep seeing our transactions come 00:08:40.349 --> 00:08:42.260 align:start position:0% we can keep seeing our transactions come through<00:08:40.589> if<00:08:41.339> I<00:08:41.459> go<00:08:41.580> down<00:08:41.729> to<00:08:41.940> here<00:08:42.060> you<00:08:42.149> can 00:08:42.260 --> 00:08:42.270 align:start position:0% through if I go down to here you can 00:08:42.270 --> 00:08:44.240 align:start position:0% through if I go down to here you can sort<00:08:42.390> of<00:08:42.479> see<00:08:42.599> the<00:08:42.779> the<00:08:43.200> nice<00:08:43.500> interface<00:08:43.800> there 00:08:44.240 --> 00:08:44.250 align:start position:0% sort of see the the nice interface there 00:08:44.250 --> 00:08:45.769 align:start position:0% sort of see the the nice interface there you<00:08:44.490> go<00:08:44.610> kind<00:08:44.850> of<00:08:44.910> a<00:08:45.000> length<00:08:45.240> that<00:08:45.330> here's<00:08:45.690> how 00:08:45.769 --> 00:08:45.779 align:start position:0% you go kind of a length that here's how 00:08:45.779 --> 00:08:46.880 align:start position:0% you go kind of a length that here's how many<00:08:45.930> transactions<00:08:46.470> there<00:08:46.620> are<00:08:46.740> on<00:08:46.800> each 00:08:46.880 --> 00:08:46.890 align:start position:0% many transactions there are on each 00:08:46.890 --> 00:08:50.000 align:start position:0% many transactions there are on each block<00:08:47.160> so<00:08:48.000> if<00:08:48.060> I<00:08:48.180> click<00:08:48.839> on<00:08:48.930> one<00:08:48.990> you<00:08:49.740> can<00:08:49.800> see 00:08:50.000 --> 00:08:50.010 align:start position:0% block so if I click on one you can see 00:08:50.010 --> 00:08:52.370 align:start position:0% block so if I click on one you can see there's<00:08:50.250> our<00:08:50.370> transactions<00:08:51.000> and<00:08:51.240> then<00:08:52.110> we<00:08:52.230> can 00:08:52.370 --> 00:08:52.380 align:start position:0% there's our transactions and then we can 00:08:52.380 --> 00:08:54.500 align:start position:0% there's our transactions and then we can drill<00:08:52.589> down<00:08:52.829> and<00:08:53.100> actually<00:08:53.910> see<00:08:54.060> the<00:08:54.089> details 00:08:54.500 --> 00:08:54.510 align:start position:0% drill down and actually see the details 00:08:54.510 --> 00:08:56.840 align:start position:0% drill down and actually see the details of<00:08:54.690> one<00:08:54.930> of<00:08:55.050> our<00:08:55.110> transactions<00:08:55.800> and<00:08:56.160> get<00:08:56.730> some 00:08:56.840 --> 00:08:56.850 align:start position:0% of one of our transactions and get some 00:08:56.850 --> 00:08:58.250 align:start position:0% of one of our transactions and get some of<00:08:56.940> the<00:08:57.089> details<00:08:57.600> of<00:08:57.690> what's<00:08:57.870> happening<00:08:58.140> here 00:08:58.250 --> 00:08:58.260 align:start position:0% of the details of what's happening here 00:08:58.260 --> 00:09:01.790 align:start position:0% of the details of what's happening here so<00:08:58.829> that's<00:08:59.040> us<00:08:59.760> with<00:09:00.209> a<00:09:00.240> live<00:09:01.020> block<00:09:01.380> Explorer 00:09:01.790 --> 00:09:01.800 align:start position:0% so that's us with a live block Explorer 00:09:01.800 --> 00:09:04.579 align:start position:0% so that's us with a live block Explorer interacting<00:09:02.459> with<00:09:02.640> Pantheon<00:09:03.240> a<00:09:03.480> new<00:09:04.140> main<00:09:04.380> net 00:09:04.579 --> 00:09:04.589 align:start position:0% interacting with Pantheon a new main net 00:09:04.589 --> 00:09:07.400 align:start position:0% interacting with Pantheon a new main net client<00:09:05.240> one<00:09:06.240> last<00:09:06.480> thing<00:09:06.779> is<00:09:06.930> I<00:09:07.079> want<00:09:07.350> to 00:09:07.400 --> 00:09:07.410 align:start position:0% client one last thing is I want to 00:09:07.410 --> 00:09:09.230 align:start position:0% client one last thing is I want to highlight<00:09:07.649> here<00:09:07.980> is<00:09:08.190> just<00:09:08.820> we've<00:09:08.940> got<00:09:09.060> some 00:09:09.230 --> 00:09:09.240 align:start position:0% highlight here is just we've got some 00:09:09.240 --> 00:09:11.449 align:start position:0% highlight here is just we've got some simple<00:09:09.450> documentation<00:09:10.230> where<00:09:10.410> we're<00:09:11.070> working 00:09:11.449 --> 00:09:11.459 align:start position:0% simple documentation where we're working 00:09:11.459 --> 00:09:13.490 align:start position:0% simple documentation where we're working towards<00:09:11.940> making<00:09:12.120> this<00:09:12.450> an<00:09:12.630> accessible<00:09:12.930> client 00:09:13.490 --> 00:09:13.500 align:start position:0% towards making this an accessible client 00:09:13.500 --> 00:09:15.860 align:start position:0% towards making this an accessible client for<00:09:13.620> people<00:09:13.829> to<00:09:13.980> get<00:09:14.399> working<00:09:15.149> with<00:09:15.480> and<00:09:15.690> using 00:09:15.860 --> 00:09:15.870 align:start position:0% for people to get working with and using 00:09:15.870 --> 00:09:18.889 align:start position:0% for people to get working with and using it<00:09:16.140> easily<00:09:16.470> so<00:09:17.100> we<00:09:17.250> expect<00:09:17.579> that<00:09:17.940> I<00:09:18.149> guess<00:09:18.690> the 00:09:18.889 --> 00:09:18.899 align:start position:0% it easily so we expect that I guess the 00:09:18.899 --> 00:09:20.329 align:start position:0% it easily so we expect that I guess the if<00:09:19.170> we're<00:09:19.350> pulling<00:09:19.620> people<00:09:19.829> in<00:09:19.920> from<00:09:20.070> the<00:09:20.160> Java 00:09:20.329 --> 00:09:20.339 align:start position:0% if we're pulling people in from the Java 00:09:20.339 --> 00:09:21.470 align:start position:0% if we're pulling people in from the Java community<00:09:20.790> they're<00:09:20.970> going<00:09:21.089> to<00:09:21.149> know<00:09:21.270> nothing 00:09:21.470 --> 00:09:21.480 align:start position:0% community they're going to know nothing 00:09:21.480 --> 00:09:24.050 align:start position:0% community they're going to know nothing about<00:09:21.720> a<00:09:21.839> theorem<00:09:22.320> so<00:09:23.010> that<00:09:23.250> QuickStart<00:09:23.820> is<00:09:24.029> a 00:09:24.050 --> 00:09:24.060 align:start position:0% about a theorem so that QuickStart is a 00:09:24.060 --> 00:09:25.550 align:start position:0% about a theorem so that QuickStart is a great<00:09:24.329> way<00:09:24.450> for<00:09:24.480> them<00:09:24.690> to<00:09:24.750> get<00:09:24.899> started<00:09:25.380> our 00:09:25.550 --> 00:09:25.560 align:start position:0% great way for them to get started our 00:09:25.560 --> 00:09:27.260 align:start position:0% great way for them to get started our documentation<00:09:26.160> we're<00:09:26.520> making<00:09:26.850> it<00:09:26.940> easy<00:09:27.149> for 00:09:27.260 --> 00:09:27.270 align:start position:0% documentation we're making it easy for 00:09:27.270 --> 00:09:28.670 align:start position:0% documentation we're making it easy for people<00:09:27.420> to<00:09:27.570> get<00:09:27.720> started<00:09:27.779> and<00:09:28.260> working<00:09:28.560> with 00:09:28.670 --> 00:09:28.680 align:start position:0% people to get started and working with 00:09:28.680 --> 00:09:30.710 align:start position:0% people to get started and working with the<00:09:28.800> product<00:09:29.070> this<00:09:29.670> is<00:09:29.910> I<00:09:30.089> guess<00:09:30.240> an<00:09:30.480> area 00:09:30.710 --> 00:09:30.720 align:start position:0% the product this is I guess an area 00:09:30.720 --> 00:09:32.300 align:start position:0% the product this is I guess an area where<00:09:30.870> we'd<00:09:30.990> love<00:09:31.230> to<00:09:31.260> get<00:09:31.500> feedback<00:09:31.709> so<00:09:32.220> if 00:09:32.300 --> 00:09:32.310 align:start position:0% where we'd love to get feedback so if 00:09:32.310 --> 00:09:33.620 align:start position:0% where we'd love to get feedback so if people<00:09:32.430> are<00:09:32.670> downloading<00:09:32.850> and<00:09:33.420> getting 00:09:33.620 --> 00:09:33.630 align:start position:0% people are downloading and getting 00:09:33.630 --> 00:09:37.040 align:start position:0% people are downloading and getting started<00:09:33.990> with<00:09:34.170> Pantheon<00:09:34.890> you're<00:09:35.040> going<00:09:36.050> WTF 00:09:37.040 --> 00:09:37.050 align:start position:0% started with Pantheon you're going WTF 00:09:37.050 --> 00:09:39.530 align:start position:0% started with Pantheon you're going WTF what's<00:09:37.740> happening<00:09:38.100> here<00:09:38.310> then<00:09:38.970> we<00:09:39.240> want<00:09:39.450> to 00:09:39.530 --> 00:09:39.540 align:start position:0% what's happening here then we want to 00:09:39.540 --> 00:09:41.360 align:start position:0% what's happening here then we want to know<00:09:39.660> and<00:09:39.990> get<00:09:40.290> and<00:09:40.440> get<00:09:40.560> feedback<00:09:40.740> and<00:09:41.190> know 00:09:41.360 --> 00:09:41.370 align:start position:0% know and get and get feedback and know 00:09:41.370 --> 00:09:46.760 align:start position:0% know and get and get feedback and know how<00:09:41.579> we<00:09:41.640> can<00:09:41.880> make<00:09:42.029> this<00:09:42.149> thing<00:09:42.209> better<00:09:45.770> that's 00:09:46.760 --> 00:09:46.770 align:start position:0% how we can make this thing better that's 00:09:46.770 --> 00:09:48.800 align:start position:0% how we can make this thing better that's our<00:09:46.920> demo 00:09:48.800 --> 00:09:48.810 align:start position:0% our demo 00:09:48.810 --> 00:09:53.949 align:start position:0% our demo [Applause] 00:09:53.949 --> 00:09:53.959 align:start position:0% [Applause] 00:09:53.959 --> 00:09:55.670 align:start position:0% [Applause] let's<00:09:54.959> have<00:09:55.050> a<00:09:55.110> look<00:09:55.259> at<00:09:55.319> some<00:09:55.440> of<00:09:55.470> this<00:09:55.589> stuff 00:09:55.670 --> 00:09:55.680 align:start position:0% let's have a look at some of this stuff 00:09:55.680 --> 00:10:04.490 align:start position:0% let's have a look at some of this stuff yep<00:10:00.350> it's<00:10:01.350> just<00:10:01.470> a<00:10:01.589> test<00:10:01.800> net<00:10:02.009> so<00:10:02.370> yep<00:10:03.440> okay<00:10:04.440> so 00:10:04.490 --> 00:10:04.500 align:start position:0% yep it's just a test net so yep okay so 00:10:04.500 --> 00:10:06.829 align:start position:0% yep it's just a test net so yep okay so we've<00:10:04.769> got<00:10:04.800> our<00:10:05.240> roadmap<00:10:06.240> here<00:10:06.480> of<00:10:06.660> things 00:10:06.829 --> 00:10:06.839 align:start position:0% we've got our roadmap here of things 00:10:06.839 --> 00:10:08.300 align:start position:0% we've got our roadmap here of things that<00:10:06.959> are<00:10:07.050> happening<00:10:07.110> so<00:10:07.440> there's<00:10:07.620> three<00:10:07.980> main 00:10:08.300 --> 00:10:08.310 align:start position:0% that are happening so there's three main 00:10:08.310 --> 00:10:09.949 align:start position:0% that are happening so there's three main themes<00:10:08.639> that<00:10:08.880> we've<00:10:09.029> got<00:10:09.240> happening<00:10:09.660> as<00:10:09.899> a 00:10:09.949 --> 00:10:09.959 align:start position:0% themes that we've got happening as a 00:10:09.959 --> 00:10:12.800 align:start position:0% themes that we've got happening as a group<00:10:10.440> at<00:10:10.680> pegasus<00:10:11.339> so<00:10:12.240> we've<00:10:12.329> got<00:10:12.420> our<00:10:12.540> core 00:10:12.800 --> 00:10:12.810 align:start position:0% group at pegasus so we've got our core 00:10:12.810 --> 00:10:14.870 align:start position:0% group at pegasus so we've got our core client<00:10:13.290> we've<00:10:14.009> got<00:10:14.130> our<00:10:14.250> enterprise<00:10:14.670> features 00:10:14.870 --> 00:10:14.880 align:start position:0% client we've got our enterprise features 00:10:14.880 --> 00:10:20.150 align:start position:0% client we've got our enterprise features and<00:10:15.449> our<00:10:15.779> theory<00:10:16.110> and<00:10:16.139> 2.0<00:10:16.649> work<00:10:18.589> we<00:10:19.589> take<00:10:19.800> main 00:10:20.150 --> 00:10:20.160 align:start position:0% and our theory and 2.0 work we take main 00:10:20.160 --> 00:10:22.490 align:start position:0% and our theory and 2.0 work we take main net<00:10:20.370> as<00:10:20.550> the<00:10:21.300> message<00:10:21.600> has<00:10:21.750> been<00:10:21.779> we<00:10:22.319> take 00:10:22.490 --> 00:10:22.500 align:start position:0% net as the message has been we take 00:10:22.500 --> 00:10:24.680 align:start position:0% net as the message has been we take maintenance<00:10:22.889> seriously<00:10:23.399> and<00:10:23.610> so<00:10:24.240> we<00:10:24.420> want<00:10:24.630> to 00:10:24.680 --> 00:10:24.690 align:start position:0% maintenance seriously and so we want to 00:10:24.690 --> 00:10:27.740 align:start position:0% maintenance seriously and so we want to make<00:10:24.839> sure<00:10:25.019> that<00:10:25.259> we<00:10:25.470> are<00:10:26.149> having<00:10:27.149> main<00:10:27.509> that 00:10:27.740 --> 00:10:27.750 align:start position:0% make sure that we are having main that 00:10:27.750 --> 00:10:29.240 align:start position:0% make sure that we are having main that as<00:10:27.930> our<00:10:28.139> first<00:10:28.350> class<00:10:28.709> thing 00:10:29.240 --> 00:10:29.250 align:start position:0% as our first class thing 00:10:29.250 --> 00:10:31.550 align:start position:0% as our first class thing its<00:10:29.399> main<00:10:29.670> net<00:10:29.910> first<00:10:30.120> in<00:10:30.420> our<00:10:30.509> client<00:10:30.930> we've 00:10:31.550 --> 00:10:31.560 align:start position:0% its main net first in our client we've 00:10:31.560 --> 00:10:33.559 align:start position:0% its main net first in our client we've built<00:10:31.769> main<00:10:31.980> net<00:10:32.220> support<00:10:32.670> we<00:10:33.300> have<00:10:33.449> this 00:10:33.559 --> 00:10:33.569 align:start position:0% built main net support we have this 00:10:33.569 --> 00:10:36.559 align:start position:0% built main net support we have this vision<00:10:33.839> for<00:10:34.350> an<00:10:34.709> enterprise<00:10:35.449> client<00:10:36.449> that 00:10:36.559 --> 00:10:36.569 align:start position:0% vision for an enterprise client that 00:10:36.569 --> 00:10:38.600 align:start position:0% vision for an enterprise client that will<00:10:36.720> be<00:10:36.899> used<00:10:37.139> by<00:10:37.290> enterprises<00:10:38.220> and<00:10:38.339> it<00:10:38.430> is 00:10:38.600 --> 00:10:38.610 align:start position:0% will be used by enterprises and it is 00:10:38.610 --> 00:10:42.439 align:start position:0% will be used by enterprises and it is enterprise<00:10:39.509> grade<00:10:39.930> but<00:10:41.149> maintenance<00:10:42.149> first 00:10:42.439 --> 00:10:42.449 align:start position:0% enterprise grade but maintenance first 00:10:42.449 --> 00:10:44.329 align:start position:0% enterprise grade but maintenance first you<00:10:43.290> know<00:10:43.380> you've<00:10:43.560> got<00:10:43.649> to<00:10:43.740> build<00:10:43.920> on<00:10:44.130> top<00:10:44.160> of 00:10:44.329 --> 00:10:44.339 align:start position:0% you know you've got to build on top of 00:10:44.339 --> 00:10:47.050 align:start position:0% you know you've got to build on top of what's<00:10:44.670> there<00:10:44.880> and<00:10:45.209> a<00:10:45.709> world<00:10:46.709> where 00:10:47.050 --> 00:10:47.060 align:start position:0% what's there and a world where 00:10:47.060 --> 00:10:49.910 align:start position:0% what's there and a world where enterprises<00:10:48.060> are<00:10:48.360> pinning<00:10:49.230> their<00:10:49.259> their 00:10:49.910 --> 00:10:49.920 align:start position:0% enterprises are pinning their their 00:10:49.920 --> 00:10:51.559 align:start position:0% enterprises are pinning their their technologies<00:10:50.459> may<00:10:50.610> be<00:10:50.670> using<00:10:50.910> side<00:10:51.240> chains 00:10:51.559 --> 00:10:51.569 align:start position:0% technologies may be using side chains 00:10:51.569 --> 00:10:53.960 align:start position:0% technologies may be using side chains like<00:10:51.720> we've<00:10:52.079> got<00:10:52.170> on<00:10:52.319> our<00:10:52.410> enterprise<00:10:52.970> stack 00:10:53.960 --> 00:10:53.970 align:start position:0% like we've got on our enterprise stack 00:10:53.970 --> 00:10:57.559 align:start position:0% like we've got on our enterprise stack their<00:10:54.829> opinions<00:10:55.829> back<00:10:56.040> to<00:10:56.399> to<00:10:56.790> main<00:10:57.000> and<00:10:57.389> it 00:10:57.559 --> 00:10:57.569 align:start position:0% their opinions back to to main and it 00:10:57.569 --> 00:10:59.929 align:start position:0% their opinions back to to main and it all<00:10:57.720> sort<00:10:57.930> of<00:10:58.019> works<00:10:58.079> is<00:10:58.740> is<00:10:59.399> the<00:10:59.610> world<00:10:59.790> that 00:10:59.929 --> 00:10:59.939 align:start position:0% all sort of works is is the world that 00:10:59.939 --> 00:11:02.030 align:start position:0% all sort of works is is the world that we<00:11:00.029> want<00:11:00.149> to<00:11:00.269> enable<00:11:00.449> with<00:11:00.750> Pantheon<00:11:01.230> and<00:11:01.410> so 00:11:02.030 --> 00:11:02.040 align:start position:0% we want to enable with Pantheon and so 00:11:02.040 --> 00:11:03.019 align:start position:0% we want to enable with Pantheon and so that's<00:11:02.220> why<00:11:02.339> we're<00:11:02.519> doing<00:11:02.610> what<00:11:02.759> we're<00:11:02.970> doing 00:11:03.019 --> 00:11:03.029 align:start position:0% that's why we're doing what we're doing 00:11:03.029 --> 00:11:06.889 align:start position:0% that's why we're doing what we're doing so<00:11:03.649> core<00:11:04.730> our<00:11:05.730> two<00:11:06.029> sort<00:11:06.300> of<00:11:06.329> big<00:11:06.509> things<00:11:06.720> that 00:11:06.889 --> 00:11:06.899 align:start position:0% so core our two sort of big things that 00:11:06.899 --> 00:11:08.660 align:start position:0% so core our two sort of big things that we<00:11:06.990> see<00:11:07.139> in<00:11:07.259> the<00:11:07.350> short<00:11:07.589> term<00:11:07.800> there<00:11:08.069> we<00:11:08.550> don't 00:11:08.660 --> 00:11:08.670 align:start position:0% we see in the short term there we don't 00:11:08.670 --> 00:11:10.550 align:start position:0% we see in the short term there we don't have<00:11:08.850> a<00:11:08.880> far<00:11:09.120> sink<00:11:09.389> yet<00:11:09.569> so<00:11:09.990> we're<00:11:10.170> running<00:11:10.439> as 00:11:10.550 --> 00:11:10.560 align:start position:0% have a far sink yet so we're running as 00:11:10.560 --> 00:11:12.800 align:start position:0% have a far sink yet so we're running as a<00:11:11.160> full<00:11:11.430> archive<00:11:11.730> node<00:11:12.000> it's<00:11:12.360> our<00:11:12.480> alpha 00:11:12.800 --> 00:11:12.810 align:start position:0% a full archive node it's our alpha 00:11:12.810 --> 00:11:14.569 align:start position:0% a full archive node it's our alpha that's<00:11:13.170> where<00:11:13.380> we<00:11:13.470> started<00:11:13.889> we're<00:11:14.490> gonna 00:11:14.569 --> 00:11:14.579 align:start position:0% that's where we started we're gonna 00:11:14.579 --> 00:11:15.980 align:start position:0% that's where we started we're gonna build<00:11:14.850> on<00:11:14.970> top<00:11:15.120> of<00:11:15.180> that<00:11:15.269> and<00:11:15.540> be<00:11:15.630> running<00:11:15.870> as<00:11:15.959> a 00:11:15.980 --> 00:11:15.990 align:start position:0% build on top of that and be running as a 00:11:15.990 --> 00:11:17.960 align:start position:0% build on top of that and be running as a full<00:11:16.259> node<00:11:16.470> and<00:11:16.709> getting<00:11:16.889> the<00:11:17.069> the<00:11:17.459> sort<00:11:17.880> of 00:11:17.960 --> 00:11:17.970 align:start position:0% full node and getting the the sort of 00:11:17.970 --> 00:11:20.480 align:start position:0% full node and getting the the sort of fast<00:11:18.509> sink<00:11:18.870> East<00:11:19.110> 63<00:11:19.649> sort<00:11:19.949> of<00:11:20.040> messages 00:11:20.480 --> 00:11:20.490 align:start position:0% fast sink East 63 sort of messages 00:11:20.490 --> 00:11:22.699 align:start position:0% fast sink East 63 sort of messages working<00:11:20.880> well<00:11:21.060> and<00:11:21.540> working<00:11:22.319> on<00:11:22.439> performance 00:11:22.699 --> 00:11:22.709 align:start position:0% working well and working on performance 00:11:22.709 --> 00:11:24.590 align:start position:0% working well and working on performance so<00:11:23.100> working<00:11:23.310> with<00:11:23.459> the<00:11:23.670> inferior<00:11:23.939> guys<00:11:24.240> and 00:11:24.590 --> 00:11:24.600 align:start position:0% so working with the inferior guys and 00:11:24.600 --> 00:11:28.160 align:start position:0% so working with the inferior guys and making<00:11:24.839> sure<00:11:25.019> that<00:11:25.790> Pantheon<00:11:26.790> is<00:11:27.180> working 00:11:28.160 --> 00:11:28.170 align:start position:0% making sure that Pantheon is working 00:11:28.170 --> 00:11:30.740 align:start position:0% making sure that Pantheon is working well<00:11:28.350> enough<00:11:28.380> to<00:11:28.939> support<00:11:29.939> that<00:11:30.060> billions<00:11:30.569> of 00:11:30.740 --> 00:11:30.750 align:start position:0% well enough to support that billions of 00:11:30.750 --> 00:11:32.240 align:start position:0% well enough to support that billions of requests<00:11:31.230> that<00:11:31.290> are<00:11:31.380> coming<00:11:31.620> in<00:11:31.740> through<00:11:31.860> in 00:11:32.240 --> 00:11:32.250 align:start position:0% requests that are coming in through in 00:11:32.250 --> 00:11:34.460 align:start position:0% requests that are coming in through in furor<00:11:32.550> we'd<00:11:32.880> love<00:11:33.089> to<00:11:33.120> have<00:11:33.329> Pantheon<00:11:33.779> being<00:11:34.380> a 00:11:34.460 --> 00:11:34.470 align:start position:0% furor we'd love to have Pantheon being a 00:11:34.470 --> 00:11:35.629 align:start position:0% furor we'd love to have Pantheon being a part<00:11:34.680> of<00:11:34.769> that<00:11:34.920> and<00:11:35.100> we're<00:11:35.220> working<00:11:35.339> within 00:11:35.629 --> 00:11:35.639 align:start position:0% part of that and we're working within 00:11:35.639 --> 00:11:38.300 align:start position:0% part of that and we're working within fiatter<00:11:36.180> to<00:11:36.389> help<00:11:36.569> make<00:11:36.689> that<00:11:36.810> happen<00:11:37.279> on<00:11:38.279> the 00:11:38.300 --> 00:11:38.310 align:start position:0% fiatter to help make that happen on the 00:11:38.310 --> 00:11:40.189 align:start position:0% fiatter to help make that happen on the enterprise<00:11:38.819> side<00:11:38.850> so<00:11:39.509> there's<00:11:39.689> a<00:11:39.779> bunch<00:11:39.959> of 00:11:40.189 --> 00:11:40.199 align:start position:0% enterprise side so there's a bunch of 00:11:40.199 --> 00:11:43.100 align:start position:0% enterprise side so there's a bunch of things<00:11:40.439> happening<00:11:40.949> there<00:11:41.100> I<00:11:42.029> guess<00:11:42.660> the<00:11:42.870> the 00:11:43.100 --> 00:11:43.110 align:start position:0% things happening there I guess the the 00:11:43.110 --> 00:11:44.929 align:start position:0% things happening there I guess the the interesting<00:11:43.500> ones<00:11:43.680> so<00:11:43.889> we're<00:11:44.009> doing<00:11:44.100> a<00:11:44.310> pbft 00:11:44.929 --> 00:11:44.939 align:start position:0% interesting ones so we're doing a pbft 00:11:44.939 --> 00:11:48.050 align:start position:0% interesting ones so we're doing a pbft based<00:11:45.500> consensus<00:11:46.500> mechanism<00:11:47.040> we've<00:11:47.610> got<00:11:47.759> some 00:11:48.050 --> 00:11:48.060 align:start position:0% based consensus mechanism we've got some 00:11:48.060 --> 00:11:50.269 align:start position:0% based consensus mechanism we've got some really<00:11:48.600> smart<00:11:49.079> guys<00:11:49.290> way<00:11:49.560> smarter<00:11:49.800> than<00:11:50.009> me 00:11:50.269 --> 00:11:50.279 align:start position:0% really smart guys way smarter than me 00:11:50.279 --> 00:11:53.300 align:start position:0% really smart guys way smarter than me actually<00:11:50.550> doing<00:11:50.910> the<00:11:51.709> formal<00:11:52.709> definition<00:11:53.189> of 00:11:53.300 --> 00:11:53.310 align:start position:0% actually doing the formal definition of 00:11:53.310 --> 00:11:56.990 align:start position:0% actually doing the formal definition of that<00:11:53.490> and<00:11:53.880> doing<00:11:54.779> like<00:11:55.050> the<00:11:55.459> liveness<00:11:56.459> proofs 00:11:56.990 --> 00:11:57.000 align:start position:0% that and doing like the liveness proofs 00:11:57.000 --> 00:11:58.670 align:start position:0% that and doing like the liveness proofs and<00:11:57.209> making<00:11:57.480> sure<00:11:57.600> that<00:11:57.779> this<00:11:57.930> protocol<00:11:58.500> that 00:11:58.670 --> 00:11:58.680 align:start position:0% and making sure that this protocol that 00:11:58.680 --> 00:12:00.799 align:start position:0% and making sure that this protocol that we're<00:11:58.920> we're<00:11:59.490> specifying<00:11:59.730> up<00:12:00.240> there<00:12:00.540> that's 00:12:00.799 --> 00:12:00.809 align:start position:0% we're we're specifying up there that's 00:12:00.809 --> 00:12:02.240 align:start position:0% we're we're specifying up there that's pbft<00:12:01.260> based<00:12:01.680> is 00:12:02.240 --> 00:12:02.250 align:start position:0% pbft based is 00:12:02.250 --> 00:12:05.000 align:start position:0% pbft based is sort<00:12:02.580> of<00:12:02.670> robust<00:12:03.090> and<00:12:03.330> a<00:12:03.810> good<00:12:04.320> protocol<00:12:04.860> for 00:12:05.000 --> 00:12:05.010 align:start position:0% sort of robust and a good protocol for 00:12:05.010 --> 00:12:06.490 align:start position:0% sort of robust and a good protocol for us<00:12:05.100> to<00:12:05.250> be<00:12:05.310> using<00:12:05.640> and<00:12:05.790> building<00:12:06.090> on<00:12:06.180> top<00:12:06.300> of 00:12:06.490 --> 00:12:06.500 align:start position:0% us to be using and building on top of 00:12:06.500 --> 00:12:09.650 align:start position:0% us to be using and building on top of we're<00:12:07.500> looking<00:12:07.530> at<00:12:07.890> the<00:12:08.070> the<00:12:08.640> EEA<00:12:09.000> so<00:12:09.180> the 00:12:09.650 --> 00:12:09.660 align:start position:0% we're looking at the the EEA so the 00:12:09.660 --> 00:12:11.210 align:start position:0% we're looking at the the EEA so the enterprise<00:12:10.230> aetherium<00:12:10.650> alliance<00:12:11.010> they've 00:12:11.210 --> 00:12:11.220 align:start position:0% enterprise aetherium alliance they've 00:12:11.220 --> 00:12:14.090 align:start position:0% enterprise aetherium alliance they've specifying<00:12:11.790> a<00:12:11.970> bunch<00:12:12.150> of<00:12:12.270> stuff<00:12:12.480> around<00:12:13.100> the 00:12:14.090 --> 00:12:14.100 align:start position:0% specifying a bunch of stuff around the 00:12:14.100 --> 00:12:15.980 align:start position:0% specifying a bunch of stuff around the consensus<00:12:14.880> mechanisms<00:12:15.390> but<00:12:15.570> also<00:12:15.690> the 00:12:15.980 --> 00:12:15.990 align:start position:0% consensus mechanisms but also the 00:12:15.990 --> 00:12:18.170 align:start position:0% consensus mechanisms but also the permissioning<00:12:16.560> and<00:12:16.710> privacy<00:12:17.160> side<00:12:17.400> so<00:12:18.000> we're 00:12:18.170 --> 00:12:18.180 align:start position:0% permissioning and privacy side so we're 00:12:18.180 --> 00:12:20.170 align:start position:0% permissioning and privacy side so we're doing<00:12:18.420> our<00:12:18.810> own<00:12:18.840> implementations<00:12:19.710> of<00:12:19.860> those 00:12:20.170 --> 00:12:20.180 align:start position:0% doing our own implementations of those 00:12:20.180 --> 00:12:21.890 align:start position:0% doing our own implementations of those standards<00:12:21.180> and<00:12:21.330> making<00:12:21.450> sure<00:12:21.660> that<00:12:21.840> our 00:12:21.890 --> 00:12:21.900 align:start position:0% standards and making sure that our 00:12:21.900 --> 00:12:24.710 align:start position:0% standards and making sure that our client<00:12:22.470> is<00:12:22.590> ready<00:12:23.490> for<00:12:23.730> enterprises<00:12:24.180> to<00:12:24.510> start 00:12:24.710 --> 00:12:24.720 align:start position:0% client is ready for enterprises to start 00:12:24.720 --> 00:12:26.480 align:start position:0% client is ready for enterprises to start using<00:12:24.930> and<00:12:25.200> provides<00:12:25.530> the<00:12:25.710> features<00:12:26.100> which<00:12:26.280> we 00:12:26.480 --> 00:12:26.490 align:start position:0% using and provides the features which we 00:12:26.490 --> 00:12:27.860 align:start position:0% using and provides the features which we know<00:12:26.640> that<00:12:26.880> they<00:12:27.000> they<00:12:27.270> really<00:12:27.510> care<00:12:27.750> about 00:12:27.860 --> 00:12:27.870 align:start position:0% know that they they really care about 00:12:27.870 --> 00:12:31.220 align:start position:0% know that they they really care about and<00:12:28.140> meet<00:12:29.360> looking<00:12:30.360> as<00:12:30.510> well<00:12:30.660> at<00:12:30.810> the<00:12:30.930> site 00:12:31.220 --> 00:12:31.230 align:start position:0% and meet looking as well at the site 00:12:31.230 --> 00:12:33.590 align:start position:0% and meet looking as well at the site change<00:12:31.500> side<00:12:31.770> so<00:12:32.550> I<00:12:32.970> guess<00:12:33.210> being<00:12:33.420> able<00:12:33.510> to 00:12:33.590 --> 00:12:33.600 align:start position:0% change side so I guess being able to 00:12:33.600 --> 00:12:35.210 align:start position:0% change side so I guess being able to support<00:12:33.930> that<00:12:34.020> as<00:12:34.320> we<00:12:34.470> go<00:12:34.590> it<00:12:34.770> forward<00:12:35.130> with 00:12:35.210 --> 00:12:35.220 align:start position:0% support that as we go it forward with 00:12:35.220 --> 00:12:38.300 align:start position:0% support that as we go it forward with the<00:12:35.340> future<00:12:36.350> the<00:12:37.350> last<00:12:37.560> section<00:12:37.920> I<00:12:38.010> got<00:12:38.160> down 00:12:38.300 --> 00:12:38.310 align:start position:0% the future the last section I got down 00:12:38.310 --> 00:12:40.280 align:start position:0% the future the last section I got down the<00:12:38.400> bottom<00:12:38.640> there<00:12:38.880> and<00:12:39.000> last<00:12:39.720> but<00:12:39.930> clearly 00:12:40.280 --> 00:12:40.290 align:start position:0% the bottom there and last but clearly 00:12:40.290 --> 00:12:43.490 align:start position:0% the bottom there and last but clearly not<00:12:40.470> least<00:12:40.740> is<00:12:41.100> a<00:12:41.550> theory<00:12:42.060> of<00:12:42.090> 2.0<00:12:42.600> and<00:12:42.840> so 00:12:43.490 --> 00:12:43.500 align:start position:0% not least is a theory of 2.0 and so 00:12:43.500 --> 00:12:46.310 align:start position:0% not least is a theory of 2.0 and so Pegasus<00:12:44.340> has<00:12:44.580> a<00:12:44.910> bunch<00:12:45.210> of<00:12:45.390> work<00:12:45.630> that<00:12:45.870> we<00:12:45.990> are 00:12:46.310 --> 00:12:46.320 align:start position:0% Pegasus has a bunch of work that we are 00:12:46.320 --> 00:12:48.800 align:start position:0% Pegasus has a bunch of work that we are doing<00:12:46.500> in<00:12:46.770> the<00:12:46.920> etherium<00:12:47.310> 2.0<00:12:47.670> space<00:12:48.000> we've 00:12:48.800 --> 00:12:48.810 align:start position:0% doing in the etherium 2.0 space we've 00:12:48.810 --> 00:12:51.770 align:start position:0% doing in the etherium 2.0 space we've got<00:12:48.990> Ben<00:12:49.740> Edgington<00:12:50.340> is<00:12:50.880> probably<00:12:51.330> not<00:12:51.540> here 00:12:51.770 --> 00:12:51.780 align:start position:0% got Ben Edgington is probably not here 00:12:51.780 --> 00:12:54.860 align:start position:0% got Ben Edgington is probably not here but<00:12:51.990> he's<00:12:52.230> I<00:12:53.190> guess<00:12:53.490> got<00:12:54.180> a<00:12:54.210> team<00:12:54.480> around<00:12:54.630> him 00:12:54.860 --> 00:12:54.870 align:start position:0% but he's I guess got a team around him 00:12:54.870 --> 00:12:56.480 align:start position:0% but he's I guess got a team around him that's<00:12:55.200> doing<00:12:55.470> a<00:12:55.530> really<00:12:55.740> great<00:12:55.920> work<00:12:56.190> in<00:12:56.370> the 00:12:56.480 --> 00:12:56.490 align:start position:0% that's doing a really great work in the 00:12:56.490 --> 00:12:58.160 align:start position:0% that's doing a really great work in the the<00:12:56.700> research<00:12:57.030> side<00:12:57.330> and<00:12:57.510> bringing<00:12:58.050> that 00:12:58.160 --> 00:12:58.170 align:start position:0% the research side and bringing that 00:12:58.170 --> 00:12:59.870 align:start position:0% the research side and bringing that forward<00:12:58.380> into<00:12:58.830> the<00:12:58.920> development<00:12:59.490> side<00:12:59.700> as 00:12:59.870 --> 00:12:59.880 align:start position:0% forward into the development side as 00:12:59.880 --> 00:13:02.810 align:start position:0% forward into the development side as well<00:13:00.060> and<00:13:00.270> so<00:13:00.570> our<00:13:01.200> Pantheon<00:13:01.770> client<00:13:02.280> is<00:13:02.430> going 00:13:02.810 --> 00:13:02.820 align:start position:0% well and so our Pantheon client is going 00:13:02.820 --> 00:13:06.890 align:start position:0% well and so our Pantheon client is going to<00:13:02.970> be<00:13:03.150> an<00:13:03.420> ethereal<00:13:03.930> 2.0<00:13:04.320> client<00:13:04.910> and<00:13:05.910> so 00:13:06.890 --> 00:13:06.900 align:start position:0% to be an ethereal 2.0 client and so 00:13:06.900 --> 00:13:08.420 align:start position:0% to be an ethereal 2.0 client and so we're<00:13:07.080> doing<00:13:07.200> the<00:13:07.410> work<00:13:07.589> on<00:13:07.800> the<00:13:07.920> the<00:13:07.950> beacon 00:13:08.420 --> 00:13:08.430 align:start position:0% we're doing the work on the the beacon 00:13:08.430 --> 00:13:11.420 align:start position:0% we're doing the work on the the beacon chains<00:13:09.020> sharding<00:13:10.020> and<00:13:10.110> all<00:13:10.260> the<00:13:10.470> etherium<00:13:11.010> 2.0 00:13:11.420 --> 00:13:11.430 align:start position:0% chains sharding and all the etherium 2.0 00:13:11.430 --> 00:13:13.460 align:start position:0% chains sharding and all the etherium 2.0 research<00:13:11.850> and<00:13:12.120> bring<00:13:12.510> that<00:13:12.780> forward<00:13:13.050> into<00:13:13.350> our 00:13:13.460 --> 00:13:13.470 align:start position:0% research and bring that forward into our 00:13:13.470 --> 00:13:16.220 align:start position:0% research and bring that forward into our development<00:13:13.680> space<00:13:14.130> as<00:13:14.310> well<00:13:15.080> that's<00:13:16.080> our 00:13:16.220 --> 00:13:16.230 align:start position:0% development space as well that's our 00:13:16.230 --> 00:13:23.170 align:start position:0% development space as well that's our roadmap 00:13:23.170 --> 00:13:23.180 align:start position:0% 00:13:23.180 --> 00:13:25.880 align:start position:0% so<00:13:24.180> looking<00:13:24.510> at<00:13:24.660> that<00:13:24.900> there's<00:13:25.410> a<00:13:25.530> bunch<00:13:25.710> of 00:13:25.880 --> 00:13:25.890 align:start position:0% so looking at that there's a bunch of 00:13:25.890 --> 00:13:27.170 align:start position:0% so looking at that there's a bunch of ways<00:13:26.040> that<00:13:26.250> we'd<00:13:26.370> love<00:13:26.610> to<00:13:26.670> get<00:13:26.880> people 00:13:27.170 --> 00:13:27.180 align:start position:0% ways that we'd love to get people 00:13:27.180 --> 00:13:30.770 align:start position:0% ways that we'd love to get people involved<00:13:28.580> for<00:13:29.580> anyone<00:13:29.880> that's<00:13:30.060> enterprise-e 00:13:30.770 --> 00:13:30.780 align:start position:0% involved for anyone that's enterprise-e 00:13:30.780 --> 00:13:33.740 align:start position:0% involved for anyone that's enterprise-e and<00:13:31.130> working<00:13:32.130> it<00:13:32.280> working<00:13:32.940> at<00:13:33.060> places<00:13:33.390> in<00:13:33.540> in 00:13:33.740 --> 00:13:33.750 align:start position:0% and working it working at places in in 00:13:33.750 --> 00:13:35.840 align:start position:0% and working it working at places in in enterprise<00:13:34.260> we're<00:13:34.680> looking<00:13:34.920> for<00:13:35.190> our 00:13:35.840 --> 00:13:35.850 align:start position:0% enterprise we're looking for our 00:13:35.850 --> 00:13:38.120 align:start position:0% enterprise we're looking for our company's<00:13:36.300> partners<00:13:36.930> clients<00:13:37.440> that<00:13:37.590> we<00:13:37.950> can 00:13:38.120 --> 00:13:38.130 align:start position:0% company's partners clients that we can 00:13:38.130 --> 00:13:39.860 align:start position:0% company's partners clients that we can sort<00:13:38.430> of<00:13:38.490> partner<00:13:38.910> with<00:13:39.060> to<00:13:39.390> make<00:13:39.540> sure<00:13:39.600> that 00:13:39.860 --> 00:13:39.870 align:start position:0% sort of partner with to make sure that 00:13:39.870 --> 00:13:41.270 align:start position:0% sort of partner with to make sure that we're<00:13:40.020> building<00:13:40.230> the<00:13:40.530> software<00:13:40.710> that's<00:13:41.160> the 00:13:41.270 --> 00:13:41.280 align:start position:0% we're building the software that's the 00:13:41.280 --> 00:13:43.550 align:start position:0% we're building the software that's the right<00:13:41.520> software<00:13:41.790> for<00:13:42.150> you<00:13:42.270> we<00:13:43.230> want<00:13:43.380> to<00:13:43.440> make 00:13:43.550 --> 00:13:43.560 align:start position:0% right software for you we want to make 00:13:43.560 --> 00:13:46.820 align:start position:0% right software for you we want to make sure<00:13:43.590> that<00:13:43.890> our<00:13:44.090> code<00:13:45.090> is<00:13:45.330> not<00:13:45.540> being<00:13:46.350> built<00:13:46.650> in 00:13:46.820 --> 00:13:46.830 align:start position:0% sure that our code is not being built in 00:13:46.830 --> 00:13:48.860 align:start position:0% sure that our code is not being built in a<00:13:46.920> vacuum<00:13:47.130> off<00:13:47.520> to<00:13:47.700> the<00:13:47.820> side<00:13:48.030> by<00:13:48.330> a<00:13:48.360> bunch<00:13:48.660> of 00:13:48.860 --> 00:13:48.870 align:start position:0% a vacuum off to the side by a bunch of 00:13:48.870 --> 00:13:51.140 align:start position:0% a vacuum off to the side by a bunch of theoretical<00:13:49.470> engineering<00:13:49.950> guys<00:13:50.100> like<00:13:51.000> I'm 00:13:51.140 --> 00:13:51.150 align:start position:0% theoretical engineering guys like I'm 00:13:51.150 --> 00:13:53.210 align:start position:0% theoretical engineering guys like I'm the<00:13:51.570> product<00:13:51.870> guy<00:13:51.960> saying<00:13:52.320> let's<00:13:53.070> actually 00:13:53.210 --> 00:13:53.220 align:start position:0% the product guy saying let's actually 00:13:53.220 --> 00:13:55.520 align:start position:0% the product guy saying let's actually build<00:13:53.640> stuff<00:13:54.060> that<00:13:54.390> solves<00:13:54.750> problems<00:13:55.260> and 00:13:55.520 --> 00:13:55.530 align:start position:0% build stuff that solves problems and 00:13:55.530 --> 00:13:59.120 align:start position:0% build stuff that solves problems and meets<00:13:55.920> client<00:13:56.340> needs<00:13:57.680> so<00:13:58.680> we're<00:13:58.800> looking<00:13:58.980> for 00:13:59.120 --> 00:13:59.130 align:start position:0% meets client needs so we're looking for 00:13:59.130 --> 00:14:00.470 align:start position:0% meets client needs so we're looking for people<00:13:59.160> on<00:13:59.490> the<00:13:59.580> enterprise<00:13:59.940> side<00:13:59.970> there 00:14:00.470 --> 00:14:00.480 align:start position:0% people on the enterprise side there 00:14:00.480 --> 00:14:04.370 align:start position:0% people on the enterprise side there we're<00:14:01.380> looking<00:14:01.740> for<00:14:02.010> I<00:14:02.960> feel<00:14:03.960> almost<00:14:04.170> like 00:14:04.370 --> 00:14:04.380 align:start position:0% we're looking for I feel almost like 00:14:04.380 --> 00:14:05.090 align:start position:0% we're looking for I feel almost like Steve<00:14:04.710> Ballmer 00:14:05.090 --> 00:14:05.100 align:start position:0% Steve Ballmer 00:14:05.100 --> 00:14:08.720 align:start position:0% Steve Ballmer but<00:14:05.340> like<00:14:05.700> developers<00:14:06.300> so<00:14:06.960> I<00:14:07.490> won't<00:14:08.490> say<00:14:08.670> it 00:14:08.720 --> 00:14:08.730 align:start position:0% but like developers so I won't say it 00:14:08.730 --> 00:14:12.620 align:start position:0% but like developers so I won't say it three<00:14:08.910> times<00:14:08.940> but<00:14:09.390> and<00:14:10.280> I<00:14:11.280> guess<00:14:11.490> in<00:14:11.640> -<00:14:11.790> in<00:14:12.030> a 00:14:12.620 --> 00:14:12.630 align:start position:0% three times but and I guess in - in a 00:14:12.630 --> 00:14:15.230 align:start position:0% three times but and I guess in - in a bunch<00:14:12.840> of<00:14:12.930> ways<00:14:13.080> so<00:14:13.740> Pegasus<00:14:14.400> is<00:14:14.520> hiring<00:14:14.730> we'd 00:14:15.230 --> 00:14:15.240 align:start position:0% bunch of ways so Pegasus is hiring we'd 00:14:15.240 --> 00:14:16.670 align:start position:0% bunch of ways so Pegasus is hiring we'd love<00:14:15.420> to<00:14:15.450> have<00:14:15.660> people<00:14:15.930> join<00:14:16.230> our<00:14:16.410> team<00:14:16.620> and 00:14:16.670 --> 00:14:16.680 align:start position:0% love to have people join our team and 00:14:16.680 --> 00:14:19.490 align:start position:0% love to have people join our team and come<00:14:17.250> work<00:14:17.430> with<00:14:17.460> us<00:14:17.640> but<00:14:18.450> also<00:14:18.630> we<00:14:19.230> don't<00:14:19.380> want 00:14:19.490 --> 00:14:19.500 align:start position:0% come work with us but also we don't want 00:14:19.500 --> 00:14:21.890 align:start position:0% come work with us but also we don't want to<00:14:19.680> like<00:14:19.920> be<00:14:20.220> the<00:14:20.610> only<00:14:20.790> ones<00:14:21.090> doing<00:14:21.420> work<00:14:21.750> on 00:14:21.890 --> 00:14:21.900 align:start position:0% to like be the only ones doing work on 00:14:21.900 --> 00:14:23.810 align:start position:0% to like be the only ones doing work on this<00:14:22.080> product<00:14:22.310> we'd<00:14:23.310> love<00:14:23.460> to<00:14:23.490> have<00:14:23.700> an 00:14:23.810 --> 00:14:23.820 align:start position:0% this product we'd love to have an 00:14:23.820 --> 00:14:25.550 align:start position:0% this product we'd love to have an open-source<00:14:24.240> community<00:14:24.690> and<00:14:24.960> be<00:14:25.290> working 00:14:25.550 --> 00:14:25.560 align:start position:0% open-source community and be working 00:14:25.560 --> 00:14:27.050 align:start position:0% open-source community and be working with<00:14:25.890> a<00:14:25.920> community<00:14:26.130> of<00:14:26.400> people<00:14:26.610> so<00:14:26.850> if<00:14:26.940> you've 00:14:27.050 --> 00:14:27.060 align:start position:0% with a community of people so if you've 00:14:27.060 --> 00:14:30.230 align:start position:0% with a community of people so if you've got<00:14:27.260> ideas<00:14:28.400> things<00:14:29.400> that<00:14:29.490> you<00:14:29.670> want<00:14:29.850> to<00:14:29.910> see<00:14:30.090> in 00:14:30.230 --> 00:14:30.240 align:start position:0% got ideas things that you want to see in 00:14:30.240 --> 00:14:32.750 align:start position:0% got ideas things that you want to see in a<00:14:30.300> client<00:14:30.720> come<00:14:31.590> along<00:14:31.830> contribute<00:14:32.400> create 00:14:32.750 --> 00:14:32.760 align:start position:0% a client come along contribute create 00:14:32.760 --> 00:14:34.970 align:start position:0% a client come along contribute create pull<00:14:32.970> requests<00:14:33.510> we're<00:14:34.290> open<00:14:34.650> source<00:14:34.860> for 00:14:34.970 --> 00:14:34.980 align:start position:0% pull requests we're open source for 00:14:34.980 --> 00:14:37.700 align:start position:0% pull requests we're open source for Apache<00:14:35.250> -<00:14:35.610> you<00:14:36.240> know<00:14:36.360> we're<00:14:36.840> there<00:14:37.020> to<00:14:37.290> work 00:14:37.700 --> 00:14:37.710 align:start position:0% Apache - you know we're there to work 00:14:37.710 --> 00:14:41.600 align:start position:0% Apache - you know we're there to work with<00:14:37.740> you<00:14:39.320> if<00:14:40.320> you<00:14:40.800> I<00:14:41.100> guess<00:14:41.310> the<00:14:41.430> other<00:14:41.520> thing 00:14:41.600 --> 00:14:41.610 align:start position:0% with you if you I guess the other thing 00:14:41.610 --> 00:14:44.300 align:start position:0% with you if you I guess the other thing for<00:14:42.000> the<00:14:42.090> developers<00:14:42.630> is<00:14:42.870> download<00:14:43.680> us<00:14:43.830> use<00:14:44.130> us 00:14:44.300 --> 00:14:44.310 align:start position:0% for the developers is download us use us 00:14:44.310 --> 00:14:46.730 align:start position:0% for the developers is download us use us and<00:14:44.660> tell<00:14:45.660> us<00:14:45.690> what<00:14:45.870> doesn't<00:14:46.290> work 00:14:46.730 --> 00:14:46.740 align:start position:0% and tell us what doesn't work 00:14:46.740 --> 00:14:48.980 align:start position:0% and tell us what doesn't work tell<00:14:47.550> us<00:14:47.670> what's<00:14:47.850> hard<00:14:48.060> you<00:14:48.630> know<00:14:48.720> it's<00:14:48.870> an 00:14:48.980 --> 00:14:48.990 align:start position:0% tell us what's hard you know it's an 00:14:48.990 --> 00:14:51.950 align:start position:0% tell us what's hard you know it's an alpha<00:14:49.670> it's<00:14:50.670> it's<00:14:51.210> actually<00:14:51.330> a<00:14:51.540> really<00:14:51.690> good 00:14:51.950 --> 00:14:51.960 align:start position:0% alpha it's it's actually a really good 00:14:51.960 --> 00:14:54.020 align:start position:0% alpha it's it's actually a really good alpha<00:14:52.320> I<00:14:52.350> think<00:14:52.740> but<00:14:53.070> it's<00:14:53.370> it's<00:14:53.670> it's<00:14:53.850> still 00:14:54.020 --> 00:14:54.030 align:start position:0% alpha I think but it's it's it's still 00:14:54.030 --> 00:14:56.300 align:start position:0% alpha I think but it's it's it's still an<00:14:54.150> alpha<00:14:54.300> and<00:14:54.810> you<00:14:55.050> know<00:14:55.140> you<00:14:55.680> know<00:14:55.830> things 00:14:56.300 --> 00:14:56.310 align:start position:0% an alpha and you know you know things 00:14:56.310 --> 00:14:58.730 align:start position:0% an alpha and you know you know things aren't<00:14:56.550> going<00:14:56.790> to<00:14:56.880> be<00:14:56.940> perfect<00:14:57.390> and<00:14:57.660> we'd<00:14:58.560> love 00:14:58.730 --> 00:14:58.740 align:start position:0% aren't going to be perfect and we'd love 00:14:58.740 --> 00:15:00.230 align:start position:0% aren't going to be perfect and we'd love to<00:14:58.800> get<00:14:59.010> feedback<00:14:59.220> and<00:14:59.610> we<00:14:59.760> want<00:14:59.910> to<00:14:59.970> make<00:15:00.090> this 00:15:00.230 --> 00:15:00.240 align:start position:0% to get feedback and we want to make this 00:15:00.240 --> 00:15:04.430 align:start position:0% to get feedback and we want to make this like<00:15:00.600> the<00:15:01.020> best<00:15:01.200> client<00:15:01.620> I<00:15:02.720> am<00:15:03.720> going<00:15:04.170> to<00:15:04.260> hand 00:15:04.430 --> 00:15:04.440 align:start position:0% like the best client I am going to hand 00:15:04.440 --> 00:15:09.680 align:start position:0% like the best client I am going to hand over<00:15:04.530> to<00:15:04.650> Johan<00:15:05.750> thank<00:15:06.750> you<00:15:06.840> rob<00:15:07.050> so<00:15:08.390> we<00:15:09.390> are<00:15:09.540> on 00:15:09.680 --> 00:15:09.690 align:start position:0% over to Johan thank you rob so we are on 00:15:09.690 --> 00:15:12.650 align:start position:0% over to Johan thank you rob so we are on github<00:15:09.930> we<00:15:10.410> are<00:15:10.560> open<00:15:10.890> source<00:15:11.130> please<00:15:11.970> submit 00:15:12.650 --> 00:15:12.660 align:start position:0% github we are open source please submit 00:15:12.660 --> 00:15:15.890 align:start position:0% github we are open source please submit PRS<00:15:13.380> we<00:15:13.800> have<00:15:13.920> already<00:15:14.130> received<00:15:14.520> an<00:15:14.940> OPR<00:15:15.540> from 00:15:15.890 --> 00:15:15.900 align:start position:0% PRS we have already received an OPR from 00:15:15.900 --> 00:15:17.920 align:start position:0% PRS we have already received an OPR from somebody<00:15:16.620> out<00:15:16.770> there<00:15:16.980> in<00:15:17.070> the<00:15:17.160> world<00:15:17.340> and 00:15:17.920 --> 00:15:17.930 align:start position:0% somebody out there in the world and 00:15:17.930 --> 00:15:22.040 align:start position:0% somebody out there in the world and we've<00:15:18.930> accepted<00:15:19.800> the<00:15:20.040> PR<00:15:20.310> join<00:15:21.210> us<00:15:21.420> on<00:15:21.630> gator 00:15:22.040 --> 00:15:22.050 align:start position:0% we've accepted the PR join us on gator 00:15:22.050 --> 00:15:24.260 align:start position:0% we've accepted the PR join us on gator on<00:15:22.380> twit<00:15:22.830> on<00:15:23.100> Twitter 00:15:24.260 --> 00:15:24.270 align:start position:0% on twit on Twitter 00:15:24.270 --> 00:15:26.990 align:start position:0% on twit on Twitter visit<00:15:24.990> us<00:15:25.080> at<00:15:25.290> the<00:15:25.380> booth<00:15:25.800> we<00:15:26.220> are<00:15:26.370> close<00:15:26.730> by 00:15:26.990 --> 00:15:27.000 align:start position:0% visit us at the booth we are close by 00:15:27.000 --> 00:15:30.860 align:start position:0% visit us at the booth we are close by and<00:15:27.420> we<00:15:28.410> are<00:15:28.440> hiring<00:15:28.830> we<00:15:29.400> are<00:15:29.550> keen<00:15:30.000> on<00:15:30.390> talking 00:15:30.860 --> 00:15:30.870 align:start position:0% and we are hiring we are keen on talking 00:15:30.870 --> 00:15:33.250 align:start position:0% and we are hiring we are keen on talking to<00:15:31.350> you<00:15:31.700> developers 00:15:33.250 --> 00:15:33.260 align:start position:0% to you developers 00:15:33.260 --> 00:15:35.650 align:start position:0% to you developers enterprises<00:15:33.890> product<00:15:34.490> people<00:15:34.820> we<00:15:35.270> want<00:15:35.540> to 00:15:35.650 --> 00:15:35.660 align:start position:0% enterprises product people we want to 00:15:35.660 --> 00:15:37.780 align:start position:0% enterprises product people we want to ingest<00:15:36.290> your<00:15:36.530> ideas<00:15:36.890> we<00:15:37.100> want<00:15:37.280> to<00:15:37.370> chat<00:15:37.640> with 00:15:37.780 --> 00:15:37.790 align:start position:0% ingest your ideas we want to chat with 00:15:37.790 --> 00:15:40.210 align:start position:0% ingest your ideas we want to chat with you<00:15:37.940> so<00:15:38.450> please<00:15:38.720> talk<00:15:39.050> to<00:15:39.110> us<00:15:39.410> talk<00:15:39.830> to<00:15:39.890> rob 00:15:40.210 --> 00:15:40.220 align:start position:0% you so please talk to us talk to rob 00:15:40.220 --> 00:15:42.600 align:start position:0% you so please talk to us talk to rob about<00:15:40.250> product<00:15:41.030> talk<00:15:41.660> to<00:15:41.900> Dan<00:15:42.140> about 00:15:42.600 --> 00:15:42.610 align:start position:0% about product talk to Dan about 00:15:42.610 --> 00:15:46.450 align:start position:0% about product talk to Dan about engagement<00:15:43.610> about<00:15:44.560> strategy<00:15:45.560> talk<00:15:46.220> to<00:15:46.370> me 00:15:46.450 --> 00:15:46.460 align:start position:0% engagement about strategy talk to me 00:15:46.460 --> 00:15:47.770 align:start position:0% engagement about strategy talk to me about<00:15:46.550> research<00:15:47.090> talk<00:15:47.390> to<00:15:47.540> Ben<00:15:47.750> about 00:15:47.770 --> 00:15:47.780 align:start position:0% about research talk to Ben about 00:15:47.780 --> 00:15:51.160 align:start position:0% about research talk to Ben about research<00:15:48.410> please<00:15:49.100> just<00:15:49.850> talk<00:15:50.150> with<00:15:50.360> us<00:15:50.480> engage 00:15:51.160 --> 00:15:51.170 align:start position:0% research please just talk with us engage 00:15:51.170 --> 00:15:56.440 align:start position:0% research please just talk with us engage with<00:15:51.410> us<00:15:53.230> thank<00:15:54.230> you<00:15:55.000> thank<00:15:56.000> you<00:15:56.120> very<00:15:56.150> much 00:15:56.440 --> 00:15:56.450 align:start position:0% with us thank you thank you very much 00:15:56.450 --> 00:15:59.620 align:start position:0% with us thank you thank you very much guys<00:15:56.660> I<00:15:57.520> think<00:15:58.520> you're<00:15:58.820> doing<00:15:59.000> in<00:15:59.210> hacker<00:15:59.360> tone 00:15:59.620 --> 00:15:59.630 align:start position:0% guys I think you're doing in hacker tone 00:15:59.630 --> 00:16:04.810 align:start position:0% guys I think you're doing in hacker tone to<00:16:02.380> open<00:16:03.380> up<00:16:03.470> for<00:16:03.650> questions<00:16:03.740> we're<00:16:04.700> gonna 00:16:04.810 --> 00:16:04.820 align:start position:0% to open up for questions we're gonna 00:16:04.820 --> 00:16:07.150 align:start position:0% to open up for questions we're gonna take<00:16:05.030> questions<00:16:05.150> now<00:16:05.570> but<00:16:06.230> if<00:16:06.590> everyone<00:16:06.890> who 00:16:07.150 --> 00:16:07.160 align:start position:0% take questions now but if everyone who 00:16:07.160 --> 00:16:08.590 align:start position:0% take questions now but if everyone who is<00:16:07.220> a<00:16:07.280> member<00:16:07.550> of<00:16:07.670> Pegasus<00:16:08.120> could<00:16:08.240> raise<00:16:08.420> their 00:16:08.590 --> 00:16:08.600 align:start position:0% is a member of Pegasus could raise their 00:16:08.600 --> 00:16:10.060 align:start position:0% is a member of Pegasus could raise their hand<00:16:08.840> there's<00:16:09.320> a<00:16:09.380> few<00:16:09.650> of<00:16:09.710> you<00:16:09.830> in<00:16:09.890> the<00:16:10.040> room 00:16:10.060 --> 00:16:10.070 align:start position:0% hand there's a few of you in the room 00:16:10.070 --> 00:16:12.100 align:start position:0% hand there's a few of you in the room feel<00:16:10.970> free<00:16:11.210> after<00:16:11.450> this<00:16:11.540> talk<00:16:11.750> to<00:16:11.870> go<00:16:11.960> up<00:16:12.020> to 00:16:12.100 --> 00:16:12.110 align:start position:0% feel free after this talk to go up to 00:16:12.110 --> 00:16:13.840 align:start position:0% feel free after this talk to go up to any<00:16:12.230> one<00:16:12.440> of<00:16:12.470> them<00:16:12.770> for<00:16:13.070> questions<00:16:13.460> as<00:16:13.640> well 00:16:13.840 --> 00:16:13.850 align:start position:0% any one of them for questions as well 00:16:13.850 --> 00:16:15.670 align:start position:0% any one of them for questions as well and<00:16:14.180> we're<00:16:14.510> gonna<00:16:14.600> be<00:16:14.780> at<00:16:14.870> the<00:16:14.900> booth 00:16:15.670 --> 00:16:15.680 align:start position:0% and we're gonna be at the booth 00:16:15.680 --> 00:16:17.170 align:start position:0% and we're gonna be at the booth the<00:16:15.830> consensus<00:16:16.280> booth<00:16:16.460> which<00:16:16.700> is<00:16:16.820> just<00:16:17.030> in<00:16:17.120> the 00:16:17.170 --> 00:16:17.180 align:start position:0% the consensus booth which is just in the 00:16:17.180 --> 00:16:18.370 align:start position:0% the consensus booth which is just in the sponsor<00:16:17.540> zone<00:16:17.720> right<00:16:17.930> at<00:16:18.020> the<00:16:18.110> end<00:16:18.230> of<00:16:18.320> this 00:16:18.370 --> 00:16:18.380 align:start position:0% sponsor zone right at the end of this 00:16:18.380 --> 00:16:21.430 align:start position:0% sponsor zone right at the end of this hall<00:16:18.650> all<00:16:19.070> afternoon<00:16:19.610> and<00:16:20.510> as<00:16:20.810> drum<00:16:21.260> said 00:16:21.430 --> 00:16:21.440 align:start position:0% hall all afternoon and as drum said 00:16:21.440 --> 00:16:23.380 align:start position:0% hall all afternoon and as drum said there's<00:16:21.650> an<00:16:21.740> enterprise<00:16:22.190> hackathon<00:16:23.180> this 00:16:23.380 --> 00:16:23.390 align:start position:0% there's an enterprise hackathon this 00:16:23.390 --> 00:16:25.300 align:start position:0% there's an enterprise hackathon this weekend<00:16:23.780> that's<00:16:24.320> here<00:16:24.560> in<00:16:24.650> Prague<00:16:24.890> so<00:16:24.920> if 00:16:25.300 --> 00:16:25.310 align:start position:0% weekend that's here in Prague so if 00:16:25.310 --> 00:16:26.620 align:start position:0% weekend that's here in Prague so if you're<00:16:25.460> spending<00:16:25.970> a<00:16:26.120> few<00:16:26.270> days<00:16:26.390> in<00:16:26.570> this 00:16:26.620 --> 00:16:26.630 align:start position:0% you're spending a few days in this 00:16:26.630 --> 00:16:27.940 align:start position:0% you're spending a few days in this beautiful<00:16:26.870> city<00:16:27.140> and<00:16:27.380> don't<00:16:27.530> want<00:16:27.740> to<00:16:27.830> see 00:16:27.940 --> 00:16:27.950 align:start position:0% beautiful city and don't want to see 00:16:27.950 --> 00:16:29.650 align:start position:0% beautiful city and don't want to see pretty<00:16:28.220> sights<00:16:28.490> but<00:16:28.820> want<00:16:29.000> a<00:16:29.060> hack<00:16:29.210> instead 00:16:29.650 --> 00:16:29.660 align:start position:0% pretty sights but want a hack instead 00:16:29.660 --> 00:16:31.870 align:start position:0% pretty sights but want a hack instead come<00:16:30.470> join<00:16:30.710> us<00:16:30.920> we<00:16:31.160> we<00:16:31.400> can<00:16:31.520> give<00:16:31.640> you<00:16:31.700> all<00:16:31.790> the 00:16:31.870 --> 00:16:31.880 align:start position:0% come join us we we can give you all the 00:16:31.880 --> 00:16:33.640 align:start position:0% come join us we we can give you all the info<00:16:32.120> at<00:16:32.210> the<00:16:32.240> booth<00:16:32.450> what<00:16:32.900> a<00:16:32.930> sales<00:16:33.200> pitch<00:16:33.410> - 00:16:33.640 --> 00:16:33.650 align:start position:0% info at the booth what a sales pitch - 00:16:33.650 --> 00:16:36.070 align:start position:0% info at the booth what a sales pitch - yeah<00:16:33.830> I<00:16:34.070> know<00:16:34.420> it's<00:16:35.420> gonna<00:16:35.510> be<00:16:35.690> raining<00:16:35.810> this 00:16:36.070 --> 00:16:36.080 align:start position:0% yeah I know it's gonna be raining this 00:16:36.080 --> 00:16:38.280 align:start position:0% yeah I know it's gonna be raining this weekend<00:16:36.470> I<00:16:36.530> think<00:16:36.560> yeah<00:16:36.980> there<00:16:37.460> we<00:16:37.520> go 00:16:38.280 --> 00:16:38.290 align:start position:0% weekend I think yeah there we go 00:16:38.290 --> 00:16:49.630 align:start position:0% weekend I think yeah there we go so<00:16:39.290> where's<00:16:39.530> question<00:16:48.400> hi 00:16:49.630 --> 00:16:49.640 align:start position:0% so where's question hi 00:16:49.640 --> 00:16:54.520 align:start position:0% so where's question hi so<00:16:49.880> for<00:16:50.630> interaction<00:16:51.230> with<00:16:52.450> Pantheon<00:16:53.530> will 00:16:54.520 --> 00:16:54.530 align:start position:0% so for interaction with Pantheon will 00:16:54.530 --> 00:16:58.210 align:start position:0% so for interaction with Pantheon will people<00:16:54.680> use<00:16:54.800> a<00:16:55.390> web<00:16:56.390> 3j<00:16:56.900> library<00:16:57.470> or<00:16:57.740> is<00:16:58.040> it 00:16:58.210 --> 00:16:58.220 align:start position:0% people use a web 3j library or is it 00:16:58.220 --> 00:17:00.280 align:start position:0% people use a web 3j library or is it something<00:16:58.850> else<00:16:59.210> that<00:16:59.630> y'all<00:16:59.810> have<00:16:59.900> created 00:17:00.280 --> 00:17:00.290 align:start position:0% something else that y'all have created 00:17:00.290 --> 00:17:02.530 align:start position:0% something else that y'all have created yep<00:17:01.130> so<00:17:01.340> it's<00:17:01.370> the<00:17:01.670> standard<00:17:02.090> sort<00:17:02.300> of<00:17:02.390> API 00:17:02.530 --> 00:17:02.540 align:start position:0% yep so it's the standard sort of API 00:17:02.540 --> 00:17:04.660 align:start position:0% yep so it's the standard sort of API czar<00:17:03.140> the<00:17:03.260> main<00:17:03.410> way<00:17:03.560> to<00:17:03.590> work<00:17:04.280> with<00:17:04.400> it<00:17:04.520> at<00:17:04.610> the 00:17:04.660 --> 00:17:04.670 align:start position:0% czar the main way to work with it at the 00:17:04.670 --> 00:17:05.050 align:start position:0% czar the main way to work with it at the moment 00:17:05.050 --> 00:17:05.060 align:start position:0% moment 00:17:05.060 --> 00:17:07.660 align:start position:0% moment sorry<00:17:05.300> web<00:17:05.510> 3j<00:17:05.870> web<00:17:06.140> 3j<00:17:06.470> yes<00:17:06.620> so<00:17:06.800> the<00:17:06.980> ways<00:17:07.490> to 00:17:07.660 --> 00:17:07.670 align:start position:0% sorry web 3j web 3j yes so the ways to 00:17:07.670 --> 00:17:10.569 align:start position:0% sorry web 3j web 3j yes so the ways to go<00:17:07.760> right<00:17:08.000> now<00:17:08.170> I<00:17:09.170> expect<00:17:09.770> in<00:17:10.160> the<00:17:10.280> fullness<00:17:10.490> of 00:17:10.569 --> 00:17:10.579 align:start position:0% go right now I expect in the fullness of 00:17:10.579 --> 00:17:12.730 align:start position:0% go right now I expect in the fullness of time<00:17:10.760> there'll<00:17:11.390> be<00:17:11.420> a<00:17:11.720> more<00:17:12.020> direct<00:17:12.170> API<00:17:12.650> for 00:17:12.730 --> 00:17:12.740 align:start position:0% time there'll be a more direct API for 00:17:12.740 --> 00:17:14.829 align:start position:0% time there'll be a more direct API for Java<00:17:13.339> people<00:17:13.579> to<00:17:13.790> interact<00:17:14.270> with<00:17:14.360> but<00:17:14.690> right 00:17:14.829 --> 00:17:14.839 align:start position:0% Java people to interact with but right 00:17:14.839 --> 00:17:17.170 align:start position:0% Java people to interact with but right now<00:17:15.050> web<00:17:15.410> 3j<00:17:15.800> works<00:17:16.100> really<00:17:16.310> really<00:17:16.430> well<00:17:16.610> so 00:17:17.170 --> 00:17:17.180 align:start position:0% now web 3j works really really well so 00:17:17.180 --> 00:17:19.090 align:start position:0% now web 3j works really really well so we're<00:17:17.300> using<00:17:17.480> web<00:17:18.170> 3j<00:17:18.530> as<00:17:18.589> a<00:17:18.680> part<00:17:18.890> of<00:17:18.980> our 00:17:19.090 --> 00:17:19.100 align:start position:0% we're using web 3j as a part of our 00:17:19.100 --> 00:17:21.790 align:start position:0% we're using web 3j as a part of our acceptance<00:17:19.339> tests<00:17:19.820> sort<00:17:20.270> of<00:17:20.329> suite<00:17:20.770> so<00:17:21.770> you 00:17:21.790 --> 00:17:21.800 align:start position:0% acceptance tests sort of suite so you 00:17:21.800 --> 00:17:24.040 align:start position:0% acceptance tests sort of suite so you think<00:17:22.220> that<00:17:22.400> like<00:17:22.610> in<00:17:22.850> the<00:17:22.910> future<00:17:23.360> that 00:17:24.040 --> 00:17:24.050 align:start position:0% think that like in the future that 00:17:24.050 --> 00:17:26.470 align:start position:0% think that like in the future that Pantheon<00:17:24.530> will<00:17:24.800> be<00:17:24.980> maybe<00:17:25.370> a<00:17:25.520> library<00:17:26.120> that 00:17:26.470 --> 00:17:26.480 align:start position:0% Pantheon will be maybe a library that 00:17:26.480 --> 00:17:28.300 align:start position:0% Pantheon will be maybe a library that you<00:17:26.570> bring<00:17:26.780> in<00:17:26.900> to<00:17:26.930> whatever<00:17:27.320> Java<00:17:27.860> project 00:17:28.300 --> 00:17:28.310 align:start position:0% you bring in to whatever Java project 00:17:28.310 --> 00:17:36.779 align:start position:0% you bring in to whatever Java project you're<00:17:28.400> doing<00:17:28.430> cool<00:17:28.910> thank<00:17:29.390> you 00:17:36.779 --> 00:17:36.789 align:start position:0% 00:17:36.789 --> 00:17:38.649 align:start position:0% what<00:17:37.789> do<00:17:37.850> you<00:17:37.940> think<00:17:38.149> what<00:17:38.360> do<00:17:38.419> you<00:17:38.450> think 00:17:38.649 --> 00:17:38.659 align:start position:0% what do you think what do you think 00:17:38.659 --> 00:17:40.810 align:start position:0% what do you think what do you think about<00:17:38.720> using<00:17:39.019> cotton<00:17:39.649> to<00:17:39.950> get<00:17:40.129> most<00:17:40.399> of<00:17:40.610> the 00:17:40.810 --> 00:17:40.820 align:start position:0% about using cotton to get most of the 00:17:40.820 --> 00:17:44.499 align:start position:0% about using cotton to get most of the Java<00:17:41.799> benefits<00:17:42.799> but<00:17:43.220> you<00:17:44.120> don't<00:17:44.299> have<00:17:44.419> to 00:17:44.499 --> 00:17:44.509 align:start position:0% Java benefits but you don't have to 00:17:44.509 --> 00:17:49.389 align:start position:0% Java benefits but you don't have to write<00:17:44.690> this<00:17:44.779> language<00:17:48.159> yeah<00:17:49.159> I<00:17:49.190> think 00:17:49.389 --> 00:17:49.399 align:start position:0% write this language yeah I think 00:17:49.399 --> 00:17:51.669 align:start position:0% write this language yeah I think Cotton's<00:17:50.149> definitely<00:17:51.110> we've<00:17:51.409> got<00:17:51.529> people 00:17:51.669 --> 00:17:51.679 align:start position:0% Cotton's definitely we've got people 00:17:51.679 --> 00:17:53.259 align:start position:0% Cotton's definitely we've got people that<00:17:51.799> are<00:17:51.950> really<00:17:52.159> excited<00:17:52.519> about<00:17:52.580> Kotlin<00:17:53.029> and 00:17:53.259 --> 00:17:53.269 align:start position:0% that are really excited about Kotlin and 00:17:53.269 --> 00:17:54.940 align:start position:0% that are really excited about Kotlin and and<00:17:53.629> looking<00:17:53.870> at<00:17:54.019> it<00:17:54.169> for<00:17:54.379> for<00:17:54.679> definitely 00:17:54.940 --> 00:17:54.950 align:start position:0% and looking at it for for definitely 00:17:54.950 --> 00:17:56.799 align:start position:0% and looking at it for for definitely some<00:17:55.070> of<00:17:55.100> the<00:17:55.190> the<00:17:55.519> parts<00:17:55.820> of<00:17:55.970> the<00:17:56.149> code<00:17:56.659> base 00:17:56.799 --> 00:17:56.809 align:start position:0% some of the the parts of the code base 00:17:56.809 --> 00:17:58.960 align:start position:0% some of the the parts of the code base and<00:17:57.379> I<00:17:57.440> think<00:17:57.620> as<00:17:57.799> we<00:17:58.159> start<00:17:58.519> to<00:17:58.610> build<00:17:58.639> more 00:17:58.960 --> 00:17:58.970 align:start position:0% and I think as we start to build more 00:17:58.970 --> 00:17:59.799 align:start position:0% and I think as we start to build more and<00:17:58.999> more<00:17:59.120> modules 00:17:59.799 --> 00:17:59.809 align:start position:0% and more modules 00:17:59.809 --> 00:18:01.930 align:start position:0% and more modules I<00:17:59.840> think<00:18:00.080> cot<00:18:00.649> alone<00:18:00.799> is<00:18:00.950> probably<00:18:01.759> my 00:18:01.930 --> 00:18:01.940 align:start position:0% I think cot alone is probably my 00:18:01.940 --> 00:18:04.200 align:start position:0% I think cot alone is probably my preference<00:18:02.389> over<00:18:02.960> like<00:18:03.200> a<00:18:03.230> scholar<00:18:03.559> so 00:18:04.200 --> 00:18:04.210 align:start position:0% preference over like a scholar so 00:18:04.210 --> 00:18:06.399 align:start position:0% preference over like a scholar so there'll<00:18:05.210> be<00:18:05.240> some<00:18:05.509> people<00:18:05.779> I<00:18:05.870> think<00:18:05.899> maybe 00:18:06.399 --> 00:18:06.409 align:start position:0% there'll be some people I think maybe 00:18:06.409 --> 00:18:08.169 align:start position:0% there'll be some people I think maybe even<00:18:06.620> on<00:18:06.710> the<00:18:06.830> stage<00:18:07.070> who<00:18:07.549> might<00:18:07.759> say<00:18:08.029> that 00:18:08.169 --> 00:18:08.179 align:start position:0% even on the stage who might say that 00:18:08.179 --> 00:18:10.529 align:start position:0% even on the stage who might say that scholars<00:18:08.659> a<00:18:08.690> better<00:18:08.990> choice<00:18:09.139> than<00:18:09.259> colon<00:18:10.220> but 00:18:10.529 --> 00:18:10.539 align:start position:0% scholars a better choice than colon but 00:18:10.539 --> 00:18:15.970 align:start position:0% scholars a better choice than colon but we're<00:18:11.539> open<00:18:11.899> to<00:18:11.990> all<00:18:12.019> its<00:18:12.440> JVM<00:18:12.950> so<00:18:13.399> yeah<00:18:14.980> we're 00:18:15.970 --> 00:18:15.980 align:start position:0% we're open to all its JVM so yeah we're 00:18:15.980 --> 00:18:18.310 align:start position:0% we're open to all its JVM so yeah we're we're<00:18:16.340> actually<00:18:16.549> already<00:18:17.509> in<00:18:17.629> the<00:18:17.749> process<00:18:18.200> of 00:18:18.310 --> 00:18:18.320 align:start position:0% we're actually already in the process of 00:18:18.320 --> 00:18:20.169 align:start position:0% we're actually already in the process of transitioning<00:18:18.919> to<00:18:19.100> support<00:18:19.549> card<00:18:19.730> line<00:18:19.940> we're 00:18:20.169 --> 00:18:20.179 align:start position:0% transitioning to support card line we're 00:18:20.179 --> 00:18:22.239 align:start position:0% transitioning to support card line we're revamping<00:18:20.749> some<00:18:21.200> of<00:18:21.289> the<00:18:21.350> infrastructure<00:18:22.009> all 00:18:22.239 --> 00:18:22.249 align:start position:0% revamping some of the infrastructure all 00:18:22.249 --> 00:18:25.359 align:start position:0% revamping some of the infrastructure all right<00:18:22.399> the<00:18:22.490> architecture<00:18:23.029> to<00:18:23.179> do<00:18:23.299> that<00:18:24.249> are<00:18:25.249> we 00:18:25.359 --> 00:18:25.369 align:start position:0% right the architecture to do that are we 00:18:25.369 --> 00:18:28.570 align:start position:0% right the architecture to do that are we going<00:18:25.580> to<00:18:25.899> provide<00:18:27.159> corporative<00:18:28.159> support 00:18:28.570 --> 00:18:28.580 align:start position:0% going to provide corporative support 00:18:28.580 --> 00:18:31.359 align:start position:0% going to provide corporative support like<00:18:28.970> great<00:18:29.419> corporation<00:18:30.350> standards<00:18:31.039> and<00:18:31.279> a 00:18:31.359 --> 00:18:31.369 align:start position:0% like great corporation standards and a 00:18:31.369 --> 00:18:35.919 align:start position:0% like great corporation standards and a corporation<00:18:33.610> support<00:18:34.610> company<00:18:35.539> to<00:18:35.749> support 00:18:35.919 --> 00:18:35.929 align:start position:0% corporation support company to support 00:18:35.929 --> 00:18:38.919 align:start position:0% corporation support company to support companies<00:18:36.559> just<00:18:37.249> want<00:18:37.519> to<00:18:37.639> use<00:18:38.179> your<00:18:38.480> software 00:18:38.919 --> 00:18:38.929 align:start position:0% companies just want to use your software 00:18:38.929 --> 00:18:41.019 align:start position:0% companies just want to use your software the<00:18:39.619> short<00:18:40.039> answer<00:18:40.190> that<00:18:40.490> I'll<00:18:40.549> give<00:18:40.700> is<00:18:40.820> yes 00:18:41.019 --> 00:18:41.029 align:start position:0% the short answer that I'll give is yes 00:18:41.029 --> 00:18:45.730 align:start position:0% the short answer that I'll give is yes and<00:18:41.440> then<00:18:42.440> might<00:18:42.679> say<00:18:42.830> more<00:18:43.299> so<00:18:44.299> absolutely<00:18:44.840> we 00:18:45.730 --> 00:18:45.740 align:start position:0% and then might say more so absolutely we 00:18:45.740 --> 00:18:48.129 align:start position:0% and then might say more so absolutely we have<00:18:46.100> a<00:18:46.279> support<00:18:46.789> offering<00:18:47.419> that<00:18:47.990> we're 00:18:48.129 --> 00:18:48.139 align:start position:0% have a support offering that we're 00:18:48.139 --> 00:18:49.810 align:start position:0% have a support offering that we're already<00:18:48.350> working<00:18:48.559> on<00:18:48.889> if<00:18:49.220> you're<00:18:49.429> interested 00:18:49.810 --> 00:18:49.820 align:start position:0% already working on if you're interested 00:18:49.820 --> 00:18:51.340 align:start position:0% already working on if you're interested in<00:18:49.879> that<00:18:49.999> would<00:18:50.450> love<00:18:50.570> to<00:18:50.690> chat<00:18:50.899> a<00:18:51.110> little<00:18:51.200> bit 00:18:51.340 --> 00:18:51.350 align:start position:0% in that would love to chat a little bit 00:18:51.350 --> 00:18:53.919 align:start position:0% in that would love to chat a little bit more<00:18:51.619> we<00:18:51.889> can<00:18:51.919> talk<00:18:52.249> through<00:18:52.429> the<00:18:52.909> truth<00:18:53.149> is<00:18:53.360> we 00:18:53.919 --> 00:18:53.929 align:start position:0% more we can talk through the truth is we 00:18:53.929 --> 00:18:56.529 align:start position:0% more we can talk through the truth is we haven't<00:18:54.139> rolled<00:18:54.950> it<00:18:55.070> out<00:18:55.190> yet<00:18:55.399> so<00:18:55.730> the<00:18:56.210> details 00:18:56.529 --> 00:18:56.539 align:start position:0% haven't rolled it out yet so the details 00:18:56.539 --> 00:18:57.820 align:start position:0% haven't rolled it out yet so the details of<00:18:56.720> it<00:18:56.869> we<00:18:57.080> didn't<00:18:57.259> want<00:18:57.470> to<00:18:57.559> talk<00:18:57.679> to 00:18:57.820 --> 00:18:57.830 align:start position:0% of it we didn't want to talk to 00:18:57.830 --> 00:18:59.560 align:start position:0% of it we didn't want to talk to enterprises<00:18:58.159> and<00:18:58.460> understand<00:18:58.909> what<00:18:59.210> you'd<00:18:59.450> be 00:18:59.560 --> 00:18:59.570 align:start position:0% enterprises and understand what you'd be 00:18:59.570 --> 00:19:01.450 align:start position:0% enterprises and understand what you'd be looking<00:18:59.690> for<00:19:00.049> as<00:19:00.499> we<00:19:00.710> define<00:19:01.039> it<00:19:01.070> but 00:19:01.450 --> 00:19:01.460 align:start position:0% looking for as we define it but 00:19:01.460 --> 00:19:09.759 align:start position:0% looking for as we define it but absolutely<00:19:06.249> yep<00:19:07.629> yeah<00:19:08.629> hey<00:19:09.019> it's<00:19:09.559> super 00:19:09.759 --> 00:19:09.769 align:start position:0% absolutely yep yeah hey it's super 00:19:09.769 --> 00:19:13.450 align:start position:0% absolutely yep yeah hey it's super exciting<00:19:10.190> thank<00:19:10.369> you<00:19:10.929> did<00:19:11.929> you<00:19:11.960> start<00:19:12.460> working 00:19:13.450 --> 00:19:13.460 align:start position:0% exciting thank you did you start working 00:19:13.460 --> 00:19:16.659 align:start position:0% exciting thank you did you start working on<00:19:13.580> faster<00:19:14.090> yet<00:19:14.539> and<00:19:14.809> if<00:19:15.470> not<00:19:15.710> I<00:19:15.919> entrusted<00:19:16.460> to 00:19:16.659 --> 00:19:16.669 align:start position:0% on faster yet and if not I entrusted to 00:19:16.669 --> 00:19:18.700 align:start position:0% on faster yet and if not I entrusted to collaborate<00:19:17.419> with<00:19:17.450> was<00:19:18.049> the<00:19:18.139> guest<00:19:18.350> team<00:19:18.499> the 00:19:18.700 --> 00:19:18.710 align:start position:0% collaborate with was the guest team the 00:19:18.710 --> 00:19:22.119 align:start position:0% collaborate with was the guest team the parity<00:19:19.039> team<00:19:19.220> on<00:19:19.720> maybe<00:19:20.860> solutions<00:19:21.860> in<00:19:21.980> this 00:19:22.119 --> 00:19:22.129 align:start position:0% parity team on maybe solutions in this 00:19:22.129 --> 00:19:24.899 align:start position:0% parity team on maybe solutions in this regard 00:19:24.899 --> 00:19:24.909 align:start position:0% 00:19:24.909 --> 00:19:27.310 align:start position:0% yes<00:19:25.940> we<00:19:26.450> haven't<00:19:26.659> on<00:19:26.840> the<00:19:26.960> product<00:19:27.230> side 00:19:27.310 --> 00:19:27.320 align:start position:0% yes we haven't on the product side 00:19:27.320 --> 00:19:29.560 align:start position:0% yes we haven't on the product side started<00:19:27.799> doing<00:19:27.950> much<00:19:28.070> Casper<00:19:28.970> related<00:19:29.360> stuff 00:19:29.560 --> 00:19:29.570 align:start position:0% started doing much Casper related stuff 00:19:29.570 --> 00:19:31.299 align:start position:0% started doing much Casper related stuff but<00:19:29.899> Ben<00:19:30.379> Edgington<00:19:30.799> has<00:19:31.009> been<00:19:31.190> definitely 00:19:31.299 --> 00:19:31.309 align:start position:0% but Ben Edgington has been definitely 00:19:31.309 --> 00:19:33.460 align:start position:0% but Ben Edgington has been definitely looking<00:19:31.700> into<00:19:31.909> it<00:19:32.029> and<00:19:32.059> yeah<00:19:32.840> definitely<00:19:33.230> love 00:19:33.460 --> 00:19:33.470 align:start position:0% looking into it and yeah definitely love 00:19:33.470 --> 00:19:35.220 align:start position:0% looking into it and yeah definitely love the<00:19:33.710> idea<00:19:33.919> of<00:19:33.980> collaborating<00:19:34.460> with<00:19:34.549> people 00:19:35.220 --> 00:19:35.230 align:start position:0% the idea of collaborating with people 00:19:35.230 --> 00:19:38.619 align:start position:0% the idea of collaborating with people yeah<00:19:36.230> and<00:19:36.379> with<00:19:36.950> the<00:19:37.009> past<00:19:37.249> thing<00:19:37.460> yeah<00:19:37.669> we're 00:19:38.619 --> 00:19:38.629 align:start position:0% yeah and with the past thing yeah we're 00:19:38.629 --> 00:19:40.869 align:start position:0% yeah and with the past thing yeah we're working<00:19:38.990> on<00:19:39.110> having<00:19:39.980> that<00:19:40.100> interoperability 00:19:40.869 --> 00:19:40.879 align:start position:0% working on having that interoperability 00:19:40.879 --> 00:19:42.999 align:start position:0% working on having that interoperability that<00:19:41.090> extensibility<00:19:41.809> of<00:19:42.049> in<00:19:42.559> the<00:19:42.740> network 00:19:42.999 --> 00:19:43.009 align:start position:0% that extensibility of in the network 00:19:43.009 --> 00:19:44.630 align:start position:0% that extensibility of in the network protocol<00:19:43.460> for<00:19:43.669> example<00:19:44.090> on<00:19:44.210> this 00:19:44.630 --> 00:19:44.640 align:start position:0% protocol for example on this 00:19:44.640 --> 00:19:50.060 align:start position:0% protocol for example on this mechanism<00:19:45.299> yeah<00:19:48.740> did<00:19:49.740> I<00:19:49.830> hear 00:19:50.060 --> 00:19:50.070 align:start position:0% mechanism yeah did I hear 00:19:50.070 --> 00:19:52.669 align:start position:0% mechanism yeah did I hear interoperability<00:19:50.910> in<00:19:51.360> sync<00:19:52.020> mode<00:19:52.170> fasting 00:19:52.669 --> 00:19:52.679 align:start position:0% interoperability in sync mode fasting 00:19:52.679 --> 00:19:56.390 align:start position:0% interoperability in sync mode fasting mode<00:19:54.110> we're<00:19:55.110> looking<00:19:55.620> at<00:19:55.710> interoperability 00:19:56.390 --> 00:19:56.400 align:start position:0% mode we're looking at interoperability 00:19:56.400 --> 00:19:59.120 align:start position:0% mode we're looking at interoperability at<00:19:56.910> different<00:19:57.330> layers<00:19:57.480> so<00:19:57.840> at<00:19:58.710> the<00:19:58.830> network 00:19:59.120 --> 00:19:59.130 align:start position:0% at different layers so at the network 00:19:59.130 --> 00:20:02.000 align:start position:0% at different layers so at the network layer<00:19:59.340> at<00:19:59.760> the<00:20:00.049> EVM<00:20:01.049> layer<00:20:01.320> because<00:20:01.740> some 00:20:02.000 --> 00:20:02.010 align:start position:0% layer at the EVM layer because some 00:20:02.010 --> 00:20:04.130 align:start position:0% layer at the EVM layer because some enterprises<00:20:02.820> may<00:20:02.940> want<00:20:03.179> to<00:20:03.270> extend<00:20:03.630> the<00:20:03.750> EVM 00:20:04.130 --> 00:20:04.140 align:start position:0% enterprises may want to extend the EVM 00:20:04.140 --> 00:20:07.220 align:start position:0% enterprises may want to extend the EVM in<00:20:04.350> some<00:20:04.799> fashion<00:20:05.210> such<00:20:06.210> as<00:20:06.360> use<00:20:06.570> integrating 00:20:07.220 --> 00:20:07.230 align:start position:0% in some fashion such as use integrating 00:20:07.230 --> 00:20:08.900 align:start position:0% in some fashion such as use integrating their<00:20:07.440> databases<00:20:08.100> or<00:20:08.220> a<00:20:08.280> big<00:20:08.429> data<00:20:08.610> framework 00:20:08.900 --> 00:20:08.910 align:start position:0% their databases or a big data framework 00:20:08.910 --> 00:20:11.900 align:start position:0% their databases or a big data framework sorry<00:20:09.240> IA<00:20:09.450> iframe<00:20:10.110> works<00:20:10.340> the<00:20:11.340> use<00:20:11.490> cases<00:20:11.760> are 00:20:11.900 --> 00:20:11.910 align:start position:0% sorry IA iframe works the use cases are 00:20:11.910 --> 00:20:13.430 align:start position:0% sorry IA iframe works the use cases are still<00:20:12.120> open 00:20:13.430 --> 00:20:13.440 align:start position:0% still open 00:20:13.440 --> 00:20:15.380 align:start position:0% still open we'd<00:20:13.890> love<00:20:14.190> to<00:20:14.220> hear<00:20:14.610> the<00:20:14.820> use<00:20:14.970> cases<00:20:15.240> that 00:20:15.380 --> 00:20:15.390 align:start position:0% we'd love to hear the use cases that 00:20:15.390 --> 00:20:17.560 align:start position:0% we'd love to hear the use cases that enterprises<00:20:15.990> would<00:20:16.140> love<00:20:16.290> to<00:20:16.440> engage<00:20:16.559> on<00:20:17.010> and 00:20:17.560 --> 00:20:17.570 align:start position:0% enterprises would love to engage on and 00:20:17.570 --> 00:20:20.210 align:start position:0% enterprises would love to engage on and we're<00:20:18.570> and<00:20:19.260> the<00:20:19.530> more<00:20:19.710> we<00:20:19.860> talk<00:20:20.070> with 00:20:20.210 --> 00:20:20.220 align:start position:0% we're and the more we talk with 00:20:20.220 --> 00:20:21.500 align:start position:0% we're and the more we talk with customers<00:20:20.400> the<00:20:20.790> more<00:20:20.910> we'll<00:20:21.120> understand 00:20:21.500 --> 00:20:21.510 align:start position:0% customers the more we'll understand 00:20:21.510 --> 00:20:23.840 align:start position:0% customers the more we'll understand where<00:20:22.080> at<00:20:22.290> what<00:20:22.530> layers<00:20:22.830> we<00:20:23.100> can<00:20:23.280> develop<00:20:23.730> that 00:20:23.840 --> 00:20:23.850 align:start position:0% where at what layers we can develop that 00:20:23.850 --> 00:20:29.690 align:start position:0% where at what layers we can develop that at<00:20:24.090> API<00:20:24.450> those<00:20:24.780> api's<00:20:27.980> just<00:20:28.980> wanted<00:20:29.309> to<00:20:29.370> add<00:20:29.490> to 00:20:29.690 --> 00:20:29.700 align:start position:0% at API those api's just wanted to add to 00:20:29.700 --> 00:20:32.120 align:start position:0% at API those api's just wanted to add to some<00:20:29.910> something<00:20:30.450> that<00:20:30.630> every<00:20:31.320> said<00:20:31.530> about 00:20:32.120 --> 00:20:32.130 align:start position:0% some something that every said about 00:20:32.130 --> 00:20:34.280 align:start position:0% some something that every said about fasting<00:20:32.700> so<00:20:33.120> with<00:20:33.570> the<00:20:33.660> parity<00:20:33.960> team<00:20:34.140> and 00:20:34.280 --> 00:20:34.290 align:start position:0% fasting so with the parity team and 00:20:34.290 --> 00:20:36.289 align:start position:0% fasting so with the parity team and guess<00:20:34.440> team<00:20:34.679> wanted<00:20:35.520> to<00:20:35.610> collaborate<00:20:36.059> on<00:20:36.090> a 00:20:36.289 --> 00:20:36.299 align:start position:0% guess team wanted to collaborate on a 00:20:36.299 --> 00:20:38.900 align:start position:0% guess team wanted to collaborate on a new<00:20:36.600> sync<00:20:36.929> protocol<00:20:37.380> and<00:20:37.650> if<00:20:38.460> you<00:20:38.580> guys<00:20:38.760> are 00:20:38.900 --> 00:20:38.910 align:start position:0% new sync protocol and if you guys are 00:20:38.910 --> 00:20:40.460 align:start position:0% new sync protocol and if you guys are interested<00:20:39.150> you<00:20:39.510> were<00:20:39.630> more<00:20:39.900> than<00:20:40.049> welcome<00:20:40.440> to 00:20:40.460 --> 00:20:40.470 align:start position:0% interested you were more than welcome to 00:20:40.470 --> 00:20:44.720 align:start position:0% interested you were more than welcome to join<00:20:40.590> in<00:20:41.520> about<00:20:41.790> eight<00:20:42.059> minutes<00:20:43.730> the 00:20:44.720 --> 00:20:44.730 align:start position:0% join in about eight minutes the 00:20:44.730 --> 00:20:46.400 align:start position:0% join in about eight minutes the discussion<00:20:45.240> of<00:20:45.390> where<00:20:45.630> to<00:20:45.840> take<00:20:46.020> the<00:20:46.230> whole 00:20:46.400 --> 00:20:46.410 align:start position:0% discussion of where to take the whole 00:20:46.410 --> 00:20:48.200 align:start position:0% discussion of where to take the whole thing<00:20:46.770> protocols<00:20:47.460> because<00:20:47.640> it's<00:20:47.910> a<00:20:47.970> really 00:20:48.200 --> 00:20:48.210 align:start position:0% thing protocols because it's a really 00:20:48.210 --> 00:20:50.750 align:start position:0% thing protocols because it's a really paint<00:20:48.750> for<00:20:48.990> everybody<00:20:49.380> so<00:20:49.679> where's<00:20:50.429> that 00:20:50.750 --> 00:20:50.760 align:start position:0% paint for everybody so where's that 00:20:50.760 --> 00:20:53.740 align:start position:0% paint for everybody so where's that happening<00:20:51.150> here<00:20:52.010> we're<00:20:53.010> not<00:20:53.220> sure<00:20:53.460> yet 00:20:53.740 --> 00:20:53.750 align:start position:0% happening here we're not sure yet 00:20:53.750 --> 00:21:02.659 align:start position:0% happening here we're not sure yet somewhere<00:20:54.750> okay<00:20:55.140> great<00:20:55.370> I'll<00:20:56.370> grab<00:20:56.640> me<00:21:01.669> one 00:21:02.659 --> 00:21:02.669 align:start position:0% somewhere okay great I'll grab me one 00:21:02.669 --> 00:21:05.380 align:start position:0% somewhere okay great I'll grab me one more<00:21:02.880> question<00:21:03.710> gentleman<00:21:04.710> in<00:21:04.799> the<00:21:04.860> green 00:21:05.380 --> 00:21:05.390 align:start position:0% more question gentleman in the green 00:21:05.390 --> 00:21:08.630 align:start position:0% more question gentleman in the green have<00:21:06.390> you<00:21:06.540> reuse<00:21:07.020> any<00:21:07.260> of<00:21:07.500> the<00:21:07.679> themes<00:21:08.070> echoed 00:21:08.630 --> 00:21:08.640 align:start position:0% have you reuse any of the themes echoed 00:21:08.640 --> 00:21:12.320 align:start position:0% have you reuse any of the themes echoed or<00:21:08.850> you<00:21:09.360> have<00:21:09.570> started<00:21:10.230> from<00:21:10.410> scratch<00:21:11.330> sorry 00:21:12.320 --> 00:21:12.330 align:start position:0% or you have started from scratch sorry 00:21:12.330 --> 00:21:13.940 align:start position:0% or you have started from scratch sorry for<00:21:12.540> licensing<00:21:13.230> reasons<00:21:13.500> so<00:21:13.620> you<00:21:13.650> started 00:21:13.940 --> 00:21:13.950 align:start position:0% for licensing reasons so you started 00:21:13.950 --> 00:21:21.570 align:start position:0% for licensing reasons so you started from<00:21:14.070> scratch 00:21:21.570 --> 00:21:21.580 align:start position:0% 00:21:21.580 --> 00:21:23.370 align:start position:0% thanks<00:21:22.210> for<00:21:22.330> the<00:21:22.390> presentation<00:21:23.020> do<00:21:23.110> you<00:21:23.200> have 00:21:23.370 --> 00:21:23.380 align:start position:0% thanks for the presentation do you have 00:21:23.380 --> 00:21:26.400 align:start position:0% thanks for the presentation do you have any<00:21:24.030> point<00:21:25.030> in<00:21:25.210> your<00:21:25.360> roadmap<00:21:25.540> to<00:21:25.960> support 00:21:26.400 --> 00:21:26.410 align:start position:0% any point in your roadmap to support 00:21:26.410 --> 00:21:29.790 align:start position:0% any point in your roadmap to support OSGi<00:21:26.920> integration<00:21:27.610> for<00:21:27.880> example<00:21:28.800> not 00:21:29.790 --> 00:21:29.800 align:start position:0% OSGi integration for example not 00:21:29.800 --> 00:21:32.100 align:start position:0% OSGi integration for example not currently<00:21:30.220> but<00:21:30.490> we're<00:21:30.790> I<00:21:31.150> guess<00:21:31.720> we've<00:21:31.930> got<00:21:32.080> a 00:21:32.100 --> 00:21:32.110 align:start position:0% currently but we're I guess we've got a 00:21:32.110 --> 00:21:35.460 align:start position:0% currently but we're I guess we've got a short<00:21:32.950> short-term<00:21:33.850> roadmap<00:21:34.240> and<00:21:34.420> then<00:21:34.600> open 00:21:35.460 --> 00:21:35.470 align:start position:0% short short-term roadmap and then open 00:21:35.470 --> 00:21:37.710 align:start position:0% short short-term roadmap and then open sort<00:21:35.740> of<00:21:35.800> roadmap<00:21:35.950> beyond<00:21:36.370> yeah<00:21:37.120> so<00:21:37.540> even 00:21:37.710 --> 00:21:37.720 align:start position:0% sort of roadmap beyond yeah so even 00:21:37.720 --> 00:21:39.210 align:start position:0% sort of roadmap beyond yeah so even though<00:21:37.870> we're<00:21:38.080> not<00:21:38.110> supporting<00:21:38.590> usgi<00:21:39.100> it 00:21:39.210 --> 00:21:39.220 align:start position:0% though we're not supporting usgi it 00:21:39.220 --> 00:21:40.950 align:start position:0% though we're not supporting usgi it works<00:21:39.520> with<00:21:39.700> spring<00:21:40.000> so<00:21:40.330> dependency 00:21:40.950 --> 00:21:40.960 align:start position:0% works with spring so dependency 00:21:40.960 --> 00:21:42.540 align:start position:0% works with spring so dependency injection<00:21:41.350> works<00:21:41.530> very<00:21:41.710> well<00:21:41.800> with<00:21:42.070> the<00:21:42.220> the 00:21:42.540 --> 00:21:42.550 align:start position:0% injection works very well with the the 00:21:42.550 --> 00:21:44.730 align:start position:0% injection works very well with the the framework<00:21:42.910> that<00:21:43.030> as<00:21:43.180> is<00:21:43.390> and<00:21:44.320> it's<00:21:44.470> very<00:21:44.680> easy 00:21:44.730 --> 00:21:44.740 align:start position:0% framework that as is and it's very easy 00:21:44.740 --> 00:21:48.570 align:start position:0% framework that as is and it's very easy to<00:21:44.950> use<00:21:45.160> so<00:21:45.460> very<00:21:46.090> easy<00:21:46.240> to<00:21:46.360> extend<00:21:46.660> and<00:21:47.580> apply 00:21:48.570 --> 00:21:48.580 align:start position:0% to use so very easy to extend and apply 00:21:48.580 --> 00:21:50.280 align:start position:0% to use so very easy to extend and apply there's<00:21:48.910> probably<00:21:49.240> a<00:21:49.300> PR<00:21:49.600> sitting<00:21:49.990> somewhere 00:21:50.280 --> 00:21:50.290 align:start position:0% there's probably a PR sitting somewhere 00:21:50.290 --> 00:21:55.590 align:start position:0% there's probably a PR sitting somewhere that<00:21:50.830> does<00:21:51.010> the<00:21:51.400> spring<00:21:51.640> integration<00:21:52.150> I<00:21:54.210> saw<00:21:55.210> I 00:21:55.590 --> 00:21:55.600 align:start position:0% that does the spring integration I saw I 00:21:55.600 --> 00:21:58.740 align:start position:0% that does the spring integration I saw I BFT<00:21:56.320> is<00:21:56.680> on<00:21:56.890> the<00:21:57.190> roadmap<00:21:57.580> is<00:21:58.030> that<00:21:58.210> for<00:21:58.450> future 00:21:58.740 --> 00:21:58.750 align:start position:0% BFT is on the roadmap is that for future 00:21:58.750 --> 00:22:03.000 align:start position:0% BFT is on the roadmap is that for future quorum<00:21:59.050> support<00:21:59.880> so<00:22:00.880> we're<00:22:01.480> using<00:22:01.690> an<00:22:01.930> IBF<00:22:02.800> tea 00:22:03.000 --> 00:22:03.010 align:start position:0% quorum support so we're using an IBF tea 00:22:03.010 --> 00:22:08.190 align:start position:0% quorum support so we're using an IBF tea based<00:22:03.280> protocol<00:22:04.270> and<00:22:04.510> so<00:22:05.730> the<00:22:06.870> potential<00:22:07.870> for 00:22:08.190 --> 00:22:08.200 align:start position:0% based protocol and so the potential for 00:22:08.200 --> 00:22:10.770 align:start position:0% based protocol and so the potential for Interop<00:22:08.530> with<00:22:08.740> with<00:22:09.010> quorum<00:22:09.310> is<00:22:09.400> there<00:22:09.780> the 00:22:10.770 --> 00:22:10.780 align:start position:0% Interop with with quorum is there the 00:22:10.780 --> 00:22:12.300 align:start position:0% Interop with with quorum is there the actual<00:22:11.140> details<00:22:11.500> of<00:22:11.620> how<00:22:11.920> that's<00:22:12.070> going<00:22:12.220> to 00:22:12.300 --> 00:22:12.310 align:start position:0% actual details of how that's going to 00:22:12.310 --> 00:22:14.850 align:start position:0% actual details of how that's going to work<00:22:12.430> is<00:22:12.670> is<00:22:13.060> not<00:22:13.270> yet<00:22:13.510> I<00:22:14.140> guess 00:22:14.850 --> 00:22:14.860 align:start position:0% work is is not yet I guess 00:22:14.860 --> 00:22:17.820 align:start position:0% work is is not yet I guess developed<00:22:15.730> and<00:22:15.910> so<00:22:16.300> it's<00:22:17.230> hard<00:22:17.410> to<00:22:17.440> say<00:22:17.650> how 00:22:17.820 --> 00:22:17.830 align:start position:0% developed and so it's hard to say how 00:22:17.830 --> 00:22:21.330 align:start position:0% developed and so it's hard to say how it's<00:22:17.980> going<00:22:18.130> to<00:22:18.220> exactly<00:22:18.550> work<00:22:19.980> well<00:22:20.980> we<00:22:21.190> have 00:22:21.330 --> 00:22:21.340 align:start position:0% it's going to exactly work well we have 00:22:21.340 --> 00:22:23.160 align:start position:0% it's going to exactly work well we have IB<00:22:21.790> ft<00:22:22.060> implementation<00:22:22.780> and<00:22:22.930> it<00:22:23.050> is 00:22:23.160 --> 00:22:23.170 align:start position:0% IB ft implementation and it is 00:22:23.170 --> 00:22:24.810 align:start position:0% IB ft implementation and it is interoperable<00:22:23.920> with<00:22:23.980> quorum<00:22:24.460> right<00:22:24.670> now 00:22:24.810 --> 00:22:24.820 align:start position:0% interoperable with quorum right now 00:22:24.820 --> 00:22:29.000 align:start position:0% interoperable with quorum right now we're<00:22:25.660> working<00:22:25.840> on<00:22:26.110> an<00:22:26.620> IPF<00:22:27.130> TP<00:22:27.370> 2.0<00:22:27.910> which<00:22:28.390> is 00:22:29.000 --> 00:22:29.010 align:start position:0% we're working on an IPF TP 2.0 which is 00:22:29.010 --> 00:22:31.590 align:start position:0% we're working on an IPF TP 2.0 which is meets<00:22:30.010> better<00:22:30.310> constraints<00:22:31.030> for<00:22:31.210> liveness 00:22:31.590 --> 00:22:31.600 align:start position:0% meets better constraints for liveness 00:22:31.600 --> 00:22:37.260 align:start position:0% meets better constraints for liveness and<00:22:31.960> safety<00:22:35.220> yeah<00:22:36.250> do<00:22:36.640> you<00:22:36.730> all<00:22:36.790> have<00:22:36.850> on<00:22:37.090> your 00:22:37.260 --> 00:22:37.270 align:start position:0% and safety yeah do you all have on your 00:22:37.270 --> 00:22:40.470 align:start position:0% and safety yeah do you all have on your roadmap<00:22:37.450> a<00:22:37.930> plan<00:22:38.500> to<00:22:38.890> maybe<00:22:39.430> improve<00:22:39.580> the 00:22:40.470 --> 00:22:40.480 align:start position:0% roadmap a plan to maybe improve the 00:22:40.480 --> 00:22:42.660 align:start position:0% roadmap a plan to maybe improve the privacy<00:22:40.900> features<00:22:41.290> of<00:22:41.740> private<00:22:42.070> transactions 00:22:42.660 --> 00:22:42.670 align:start position:0% privacy features of private transactions 00:22:42.670 --> 00:22:45.750 align:start position:0% privacy features of private transactions and<00:22:42.880> in<00:22:43.210> Coram<00:22:43.620> you<00:22:44.620> talk<00:22:44.800> about<00:22:44.920> what<00:22:45.520> tiller 00:22:45.750 --> 00:22:45.760 align:start position:0% and in Coram you talk about what tiller 00:22:45.760 --> 00:22:48.600 align:start position:0% and in Coram you talk about what tiller doing<00:22:45.940> in<00:22:46.030> there<00:22:46.350> yep<00:22:47.350> so<00:22:47.590> we<00:22:47.800> definitely<00:22:48.400> have 00:22:48.600 --> 00:22:48.610 align:start position:0% doing in there yep so we definitely have 00:22:48.610 --> 00:22:52.050 align:start position:0% doing in there yep so we definitely have the<00:22:49.090> ideas<00:22:50.080> around<00:22:50.290> how<00:22:50.590> to<00:22:50.740> do<00:22:50.890> a<00:22:50.920> privacy<00:22:51.430> in 00:22:52.050 --> 00:22:52.060 align:start position:0% the ideas around how to do a privacy in 00:22:52.060 --> 00:22:54.000 align:start position:0% the ideas around how to do a privacy in a<00:22:52.150> way<00:22:52.300> that's<00:22:52.570> I<00:22:52.840> guess<00:22:53.260> different<00:22:53.650> decorum 00:22:54.000 --> 00:22:54.010 align:start position:0% a way that's I guess different decorum 00:22:54.010 --> 00:22:57.630 align:start position:0% a way that's I guess different decorum and<00:22:54.220> so<00:22:54.910> sort<00:22:55.210> of<00:22:55.300> inspired<00:22:55.720> by<00:22:56.710> learning<00:22:57.490> some 00:22:57.630 --> 00:22:57.640 align:start position:0% and so sort of inspired by learning some 00:22:57.640 --> 00:22:59.400 align:start position:0% and so sort of inspired by learning some of<00:22:57.700> the<00:22:57.760> lessons<00:22:57.940> from<00:22:58.150> quorum<00:22:58.600> but<00:22:58.960> done 00:22:59.400 --> 00:22:59.410 align:start position:0% of the lessons from quorum but done 00:22:59.410 --> 00:23:02.220 align:start position:0% of the lessons from quorum but done somewhat<00:22:59.800> differently<00:23:00.100> and<00:23:00.940> the<00:23:01.780> actual 00:23:02.220 --> 00:23:02.230 align:start position:0% somewhat differently and the actual 00:23:02.230 --> 00:23:05.160 align:start position:0% somewhat differently and the actual implementation<00:23:02.710> details<00:23:03.430> us<00:23:03.610> again<00:23:04.240> it's<00:23:05.080> not 00:23:05.160 --> 00:23:05.170 align:start position:0% implementation details us again it's not 00:23:05.170 --> 00:23:06.630 align:start position:0% implementation details us again it's not like<00:23:05.230> a<00:23:05.380> broken<00:23:05.620> record<00:23:05.710> haven't<00:23:06.490> got<00:23:06.610> a 00:23:06.630 --> 00:23:06.640 align:start position:0% like a broken record haven't got a 00:23:06.640 --> 00:23:08.910 align:start position:0% like a broken record haven't got a actually<00:23:07.090> done<00:23:07.270> yet<00:23:07.450> but<00:23:07.930> yeah<00:23:08.710> there's 00:23:08.910 --> 00:23:08.920 align:start position:0% actually done yet but yeah there's 00:23:08.920 --> 00:23:11.040 align:start position:0% actually done yet but yeah there's definitely<00:23:08.980> some<00:23:09.490> some<00:23:09.940> diagrams<00:23:10.600> and<00:23:10.930> things 00:23:11.040 --> 00:23:11.050 align:start position:0% definitely some some diagrams and things 00:23:11.050 --> 00:23:12.300 align:start position:0% definitely some some diagrams and things that<00:23:11.110> I<00:23:11.260> can<00:23:11.290> I<00:23:11.650> can<00:23:11.800> share<00:23:11.950> with<00:23:12.040> you<00:23:12.130> and<00:23:12.220> have 00:23:12.300 --> 00:23:12.310 align:start position:0% that I can I can share with you and have 00:23:12.310 --> 00:23:16.530 align:start position:0% that I can I can share with you and have a<00:23:12.340> chat<00:23:12.520> with<00:23:12.550> later<00:23:13.170> and<00:23:14.170> be<00:23:14.530> a<00:23:15.010> spec<00:23:15.580> v1<00:23:16.120> was 00:23:16.530 --> 00:23:16.540 align:start position:0% a chat with later and be a spec v1 was 00:23:16.540 --> 00:23:19.740 align:start position:0% a chat with later and be a spec v1 was released<00:23:17.110> in<00:23:17.710> May<00:23:18.180> v2<00:23:19.180> was<00:23:19.330> released 00:23:19.740 --> 00:23:19.750 align:start position:0% released in May v2 was released 00:23:19.750 --> 00:23:23.460 align:start position:0% released in May v2 was released yesterday<00:23:20.640> they<00:23:21.640> have<00:23:21.820> privacy<00:23:22.240> levels<00:23:22.780> we're 00:23:23.460 --> 00:23:23.470 align:start position:0% yesterday they have privacy levels we're 00:23:23.470 --> 00:23:26.010 align:start position:0% yesterday they have privacy levels we're looking<00:23:23.920> to<00:23:24.100> see<00:23:24.250> how<00:23:24.460> quorums<00:23:25.120> privacy<00:23:25.690> and 00:23:26.010 --> 00:23:26.020 align:start position:0% looking to see how quorums privacy and 00:23:26.020 --> 00:23:29.670 align:start position:0% looking to see how quorums privacy and our<00:23:26.260> privacy<00:23:26.880> features<00:23:27.880> may<00:23:28.600> interoperate<00:23:29.530> or 00:23:29.670 --> 00:23:29.680 align:start position:0% our privacy features may interoperate or 00:23:29.680 --> 00:23:32.820 align:start position:0% our privacy features may interoperate or just<00:23:30.220> compare<00:23:30.700> and<00:23:30.910> see<00:23:31.720> how<00:23:31.870> we<00:23:31.930> can<00:23:32.140> perhaps 00:23:32.820 --> 00:23:32.830 align:start position:0% just compare and see how we can perhaps 00:23:32.830 --> 00:23:34.890 align:start position:0% just compare and see how we can perhaps support<00:23:33.370> the<00:23:33.550> EI<00:23:33.760> standards<00:23:34.480> as<00:23:34.720> well<00:23:34.840> as 00:23:34.890 --> 00:23:34.900 align:start position:0% support the EI standards as well as 00:23:34.900 --> 00:23:35.520 align:start position:0% support the EI standards as well as customer 00:23:35.520 --> 00:23:35.530 align:start position:0% customer 00:23:35.530 --> 00:23:37.680 align:start position:0% customer quirements<00:23:35.890> they<00:23:36.370> may<00:23:36.490> not<00:23:36.610> overlap<00:23:36.790> so<00:23:37.330> we're 00:23:37.680 --> 00:23:37.690 align:start position:0% quirements they may not overlap so we're 00:23:37.690 --> 00:23:39.240 align:start position:0% quirements they may not overlap so we're very<00:23:37.720> curious<00:23:38.290> to<00:23:38.320> hear<00:23:38.800> what<00:23:38.860> kind<00:23:39.190> of 00:23:39.240 --> 00:23:39.250 align:start position:0% very curious to hear what kind of 00:23:39.250 --> 00:23:40.950 align:start position:0% very curious to hear what kind of privacy<00:23:39.580> requirements<00:23:39.820> that<00:23:40.300> you're<00:23:40.480> seeking 00:23:40.950 --> 00:23:40.960 align:start position:0% privacy requirements that you're seeking 00:23:40.960 --> 00:23:45.360 align:start position:0% privacy requirements that you're seeking so<00:23:41.560> please<00:23:41.860> come<00:23:42.130> talk<00:23:42.310> to<00:23:42.340> us<00:23:43.650> it<00:23:44.650> also<00:23:45.100> might 00:23:45.360 --> 00:23:45.370 align:start position:0% so please come talk to us it also might 00:23:45.370 --> 00:23:46.830 align:start position:0% so please come talk to us it also might be<00:23:45.400> worth<00:23:45.670> I<00:23:45.940> mean<00:23:46.240> you<00:23:46.450> might<00:23:46.630> have<00:23:46.720> thought 00:23:46.830 --> 00:23:46.840 align:start position:0% be worth I mean you might have thought 00:23:46.840 --> 00:23:48.330 align:start position:0% be worth I mean you might have thought about<00:23:46.960> this<00:23:47.230> but<00:23:47.500> you<00:23:47.770> know<00:23:47.890> creating<00:23:48.250> a 00:23:48.330 --> 00:23:48.340 align:start position:0% about this but you know creating a 00:23:48.340 --> 00:23:50.580 align:start position:0% about this but you know creating a bounty<00:23:48.670> to<00:23:48.850> see<00:23:49.030> if<00:23:49.210> you<00:23:50.050> know<00:23:50.170> there's<00:23:50.380> a<00:23:50.440> lot 00:23:50.580 --> 00:23:50.590 align:start position:0% bounty to see if you know there's a lot 00:23:50.590 --> 00:23:51.750 align:start position:0% bounty to see if you know there's a lot of<00:23:50.710> different<00:23:50.980> ways<00:23:51.100> to<00:23:51.370> kind<00:23:51.460> of<00:23:51.580> glean 00:23:51.750 --> 00:23:51.760 align:start position:0% of different ways to kind of glean 00:23:51.760 --> 00:23:53.040 align:start position:0% of different ways to kind of glean information<00:23:51.910> on<00:23:52.420> those<00:23:52.600> private 00:23:53.040 --> 00:23:53.050 align:start position:0% information on those private 00:23:53.050 --> 00:23:55.860 align:start position:0% information on those private transactions<00:23:53.710> so<00:23:54.010> yeah<00:23:54.970> it<00:23:55.420> might<00:23:55.600> be<00:23:55.690> a<00:23:55.720> good 00:23:55.860 --> 00:23:55.870 align:start position:0% transactions so yeah it might be a good 00:23:55.870 --> 00:23:57.810 align:start position:0% transactions so yeah it might be a good idea<00:23:56.200> to<00:23:56.470> like<00:23:56.650> try<00:23:56.920> and<00:23:56.950> open<00:23:57.130> that<00:23:57.370> up<00:23:57.430> just 00:23:57.810 --> 00:23:57.820 align:start position:0% idea to like try and open that up just 00:23:57.820 --> 00:23:59.490 align:start position:0% idea to like try and open that up just to<00:23:57.970> show<00:23:58.300> up<00:23:58.360> and<00:23:58.450> make<00:23:58.600> sure<00:23:58.750> that<00:23:58.930> banks<00:23:59.290> and 00:23:59.490 --> 00:23:59.500 align:start position:0% to show up and make sure that banks and 00:23:59.500 --> 00:24:01.290 align:start position:0% to show up and make sure that banks and insurance<00:23:59.800> companies<00:24:00.040> are<00:24:00.580> you<00:24:00.970> know<00:24:01.090> or 00:24:01.290 --> 00:24:01.300 align:start position:0% insurance companies are you know or 00:24:01.300 --> 00:24:03.600 align:start position:0% insurance companies are you know or comfortable<00:24:01.930> with<00:24:02.200> yeah<00:24:02.770> definitely<00:24:03.430> just 00:24:03.600 --> 00:24:03.610 align:start position:0% comfortable with yeah definitely just 00:24:03.610 --> 00:24:05.820 align:start position:0% comfortable with yeah definitely just just<00:24:04.030> a<00:24:04.120> thought<00:24:04.330> yeah<00:24:04.840> I<00:24:05.080> mean<00:24:05.230> our<00:24:05.380> R&D<00:24:05.680> team 00:24:05.820 --> 00:24:05.830 align:start position:0% just a thought yeah I mean our R&D team 00:24:05.830 --> 00:24:08.820 align:start position:0% just a thought yeah I mean our R&D team the<00:24:06.610> eath<00:24:06.790> 2.0<00:24:07.300> team<00:24:07.780> they're<00:24:08.050> working<00:24:08.380> on<00:24:08.440> ZK 00:24:08.820 --> 00:24:08.830 align:start position:0% the eath 2.0 team they're working on ZK 00:24:08.830 --> 00:24:11.910 align:start position:0% the eath 2.0 team they're working on ZK start<00:24:09.160> CK<00:24:09.940> starts<00:24:10.420> trying<00:24:11.320> to<00:24:11.440> figure<00:24:11.650> out<00:24:11.770> how 00:24:11.910 --> 00:24:11.920 align:start position:0% start CK starts trying to figure out how 00:24:11.920 --> 00:24:13.500 align:start position:0% start CK starts trying to figure out how those<00:24:12.130> get<00:24:12.340> integrated<00:24:12.880> at<00:24:12.970> multiple<00:24:13.390> layers 00:24:13.500 --> 00:24:13.510 align:start position:0% those get integrated at multiple layers 00:24:13.510 --> 00:24:16.710 align:start position:0% those get integrated at multiple layers of<00:24:13.840> the<00:24:13.930> protocol<00:24:14.490> how<00:24:15.490> they<00:24:16.420> can<00:24:16.600> be 00:24:16.710 --> 00:24:16.720 align:start position:0% of the protocol how they can be 00:24:16.720 --> 00:24:20.280 align:start position:0% of the protocol how they can be simplified<00:24:17.260> aggregated<00:24:18.510> composed<00:24:19.510> these<00:24:20.140> are 00:24:20.280 --> 00:24:20.290 align:start position:0% simplified aggregated composed these are 00:24:20.290 --> 00:24:22.920 align:start position:0% simplified aggregated composed these are all<00:24:20.610> pieces<00:24:21.610> that<00:24:21.820> we're<00:24:22.060> all<00:24:22.210> actively 00:24:22.920 --> 00:24:22.930 align:start position:0% all pieces that we're all actively 00:24:22.930 --> 00:24:26.640 align:start position:0% all pieces that we're all actively looking<00:24:23.230> into<00:24:24.390> what<00:24:25.390> kind<00:24:25.630> of<00:24:25.720> technology<00:24:26.230> are 00:24:26.640 --> 00:24:26.650 align:start position:0% looking into what kind of technology are 00:24:26.650 --> 00:24:30.660 align:start position:0% looking into what kind of technology are you<00:24:26.770> using<00:24:26.950> for<00:24:27.100> the<00:24:27.490> chain<00:24:27.940> data<00:24:28.180> storage<00:24:29.670> yep 00:24:30.660 --> 00:24:30.670 align:start position:0% you using for the chain data storage yep 00:24:30.670 --> 00:24:32.550 align:start position:0% you using for the chain data storage yep so<00:24:30.880> at<00:24:31.150> the<00:24:31.240> moment<00:24:31.390> we're<00:24:31.690> we're<00:24:32.320> still 00:24:32.550 --> 00:24:32.560 align:start position:0% so at the moment we're we're still 00:24:32.560 --> 00:24:35.250 align:start position:0% so at the moment we're we're still working<00:24:33.040> on<00:24:33.130> a<00:24:33.160> Rox<00:24:33.400> DB<00:24:33.730> sort<00:24:34.420> of<00:24:34.480> database<00:24:34.720> for 00:24:35.250 --> 00:24:35.260 align:start position:0% working on a Rox DB sort of database for 00:24:35.260 --> 00:24:38.610 align:start position:0% working on a Rox DB sort of database for the<00:24:35.590> the<00:24:35.980> storage<00:24:36.690> we're<00:24:37.690> looking<00:24:38.050> at<00:24:38.230> so 00:24:38.610 --> 00:24:38.620 align:start position:0% the the storage we're looking at so 00:24:38.620 --> 00:24:40.290 align:start position:0% the the storage we're looking at so we've<00:24:38.740> got<00:24:38.860> an<00:24:38.980> abstraction<00:24:39.340> layer<00:24:39.490> around 00:24:40.290 --> 00:24:40.300 align:start position:0% we've got an abstraction layer around 00:24:40.300 --> 00:24:42.570 align:start position:0% we've got an abstraction layer around that<00:24:40.480> and<00:24:40.690> so<00:24:40.870> moving<00:24:41.350> into<00:24:41.530> support<00:24:42.220> I<00:24:42.370> guess 00:24:42.570 --> 00:24:42.580 align:start position:0% that and so moving into support I guess 00:24:42.580 --> 00:24:46.110 align:start position:0% that and so moving into support I guess you<00:24:43.300> know<00:24:43.390> pluggable<00:24:44.340> storage<00:24:45.340> mechanisms<00:24:45.880> so 00:24:46.110 --> 00:24:46.120 align:start position:0% you know pluggable storage mechanisms so 00:24:46.120 --> 00:24:47.760 align:start position:0% you know pluggable storage mechanisms so I<00:24:46.330> guess<00:24:46.750> it's<00:24:46.900> Java<00:24:47.140> so<00:24:47.380> probably<00:24:47.620> something 00:24:47.760 --> 00:24:47.770 align:start position:0% I guess it's Java so probably something 00:24:47.770 --> 00:24:50.700 align:start position:0% I guess it's Java so probably something JDBC<00:24:48.310> based<00:24:48.720> with<00:24:49.720> the<00:24:49.840> casing<00:24:50.230> layer<00:24:50.380> to 00:24:50.700 --> 00:24:50.710 align:start position:0% JDBC based with the casing layer to 00:24:50.710 --> 00:24:51.900 align:start position:0% JDBC based with the casing layer to actually<00:24:50.920> make<00:24:51.250> sure<00:24:51.370> that<00:24:51.490> performance 00:24:51.900 --> 00:24:51.910 align:start position:0% actually make sure that performance 00:24:51.910 --> 00:24:55.140 align:start position:0% actually make sure that performance happens<00:24:52.210> as<00:24:52.690> well<00:24:52.870> yeah<00:24:53.680> and<00:24:54.220> the<00:24:54.340> R&D<00:24:54.640> team<00:24:54.970> is 00:24:55.140 --> 00:24:55.150 align:start position:0% happens as well yeah and the R&D team is 00:24:55.150 --> 00:24:57.120 align:start position:0% happens as well yeah and the R&D team is also<00:24:55.480> looking<00:24:55.600> at<00:24:55.840> database<00:24:56.200> technologies<00:24:56.950> to 00:24:57.120 --> 00:24:57.130 align:start position:0% also looking at database technologies to 00:24:57.130 --> 00:24:59.610 align:start position:0% also looking at database technologies to try<00:24:57.400> and<00:24:57.520> simplify<00:24:58.000> the<00:24:58.330> integration<00:24:58.900> and<00:24:59.260> the 00:24:59.610 --> 00:24:59.620 align:start position:0% try and simplify the integration and the 00:24:59.620 --> 00:25:01.500 align:start position:0% try and simplify the integration and the indexing<00:25:00.280> benefits<00:25:01.120> that<00:25:01.300> come<00:25:01.480> from 00:25:01.500 --> 00:25:01.510 align:start position:0% indexing benefits that come from 00:25:01.510 --> 00:25:03.570 align:start position:0% indexing benefits that come from databases<00:25:02.050> so<00:25:02.740> we're<00:25:02.890> trying<00:25:03.100> to<00:25:03.190> see<00:25:03.310> where 00:25:03.570 --> 00:25:03.580 align:start position:0% databases so we're trying to see where 00:25:03.580 --> 00:25:05.430 align:start position:0% databases so we're trying to see where where<00:25:04.060> the<00:25:04.210> technologies<00:25:04.840> can<00:25:05.020> be<00:25:05.110> leveraged 00:25:05.430 --> 00:25:05.440 align:start position:0% where the technologies can be leveraged 00:25:05.440 --> 00:25:07.740 align:start position:0% where the technologies can be leveraged in<00:25:05.680> in<00:25:05.920> the<00:25:06.160> blockchain<00:25:06.400> and<00:25:06.910> vice-versa 00:25:07.740 --> 00:25:07.750 align:start position:0% in in the blockchain and vice-versa 00:25:07.750 --> 00:25:09.300 align:start position:0% in in the blockchain and vice-versa because<00:25:08.470> that's<00:25:08.710> how<00:25:08.830> we're<00:25:08.980> trying<00:25:09.190> to 00:25:09.300 --> 00:25:09.310 align:start position:0% because that's how we're trying to 00:25:09.310 --> 00:25:10.350 align:start position:0% because that's how we're trying to bridge<00:25:09.490> we're<00:25:09.700> trying<00:25:09.910> to<00:25:09.970> bring<00:25:10.150> main 00:25:10.350 --> 00:25:10.360 align:start position:0% bridge we're trying to bring main 00:25:10.360 --> 00:25:11.820 align:start position:0% bridge we're trying to bring main technologies<00:25:11.050> to<00:25:11.170> enterprise<00:25:11.590> and 00:25:11.820 --> 00:25:11.830 align:start position:0% technologies to enterprise and 00:25:11.830 --> 00:25:12.780 align:start position:0% technologies to enterprise and vice-versa 00:25:12.780 --> 00:25:12.790 align:start position:0% vice-versa 00:25:12.790 --> 00:25:23.450 align:start position:0% vice-versa bring<00:25:13.090> Enterprise<00:25:13.510> technologies<00:25:14.020> to<00:25:14.230> may<00:25:14.620> not 00:25:23.450 --> 00:25:23.460 align:start position:0% 00:25:23.460 --> 00:25:25.520 align:start position:0% you