WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:15.000 align:start position:0% [Music] 00:00:15.000 --> 00:00:15.010 align:start position:0% [Music] 00:00:15.010 --> 00:00:19.120 align:start position:0% [Music] thank<00:00:16.010> you<00:00:16.190> yeah<00:00:16.460> I'm<00:00:16.610> Tyron<00:00:16.910> Logan<00:00:17.210> I<00:00:17.980> work<00:00:18.980> at 00:00:19.120 --> 00:00:19.130 align:start position:0% thank you yeah I'm Tyron Logan I work at 00:00:19.130 --> 00:00:21.010 align:start position:0% thank you yeah I'm Tyron Logan I work at JPMorgan<00:00:19.400> and<00:00:19.700> I'm<00:00:20.120> the<00:00:20.300> technical<00:00:20.600> product 00:00:21.010 --> 00:00:21.020 align:start position:0% JPMorgan and I'm the technical product 00:00:21.020 --> 00:00:22.750 align:start position:0% JPMorgan and I'm the technical product lead<00:00:21.170> for<00:00:21.440> an<00:00:21.770> a<00:00:22.070> theorem<00:00:22.370> based<00:00:22.550> client 00:00:22.750 --> 00:00:22.760 align:start position:0% lead for an a theorem based client 00:00:22.760 --> 00:00:25.510 align:start position:0% lead for an a theorem based client called<00:00:23.150> quorum<00:00:23.710> I'm<00:00:24.710> gonna<00:00:24.980> be<00:00:25.070> presenting 00:00:25.510 --> 00:00:25.520 align:start position:0% called quorum I'm gonna be presenting 00:00:25.520 --> 00:00:29.410 align:start position:0% called quorum I'm gonna be presenting with<00:00:25.670> you<00:00:26.270> today<00:00:26.780> on<00:00:27.880> basically<00:00:28.880> consensus 00:00:29.410 --> 00:00:29.420 align:start position:0% with you today on basically consensus 00:00:29.420 --> 00:00:31.660 align:start position:0% with you today on basically consensus mechanisms<00:00:29.990> and<00:00:30.320> permission<00:00:30.980> networks<00:00:31.370> and 00:00:31.660 --> 00:00:31.670 align:start position:0% mechanisms and permission networks and 00:00:31.670 --> 00:00:35.140 align:start position:0% mechanisms and permission networks and how<00:00:31.880> companies<00:00:32.360> like<00:00:33.220> JPMorgan<00:00:34.220> and<00:00:34.790> startups 00:00:35.140 --> 00:00:35.150 align:start position:0% how companies like JPMorgan and startups 00:00:35.150 --> 00:00:37.270 align:start position:0% how companies like JPMorgan and startups like<00:00:35.210> me<00:00:35.630> are<00:00:35.930> coming<00:00:36.110> together<00:00:36.380> to<00:00:36.680> really 00:00:37.270 --> 00:00:37.280 align:start position:0% like me are coming together to really 00:00:37.280 --> 00:00:39.100 align:start position:0% like me are coming together to really help<00:00:37.520> advance<00:00:37.910> the<00:00:38.120> theorem<00:00:38.390> both<00:00:38.870> in<00:00:39.020> the 00:00:39.100 --> 00:00:39.110 align:start position:0% help advance the theorem both in the 00:00:39.110 --> 00:00:41.229 align:start position:0% help advance the theorem both in the permission<00:00:39.470> space<00:00:39.739> and<00:00:39.980> also<00:00:40.280> in<00:00:40.579> the<00:00:40.820> in<00:00:41.120> the 00:00:41.229 --> 00:00:41.239 align:start position:0% permission space and also in the in the 00:00:41.239 --> 00:00:43.990 align:start position:0% permission space and also in the in the public<00:00:41.360> enterprise<00:00:41.930> space<00:00:42.170> so<00:00:43.100> the<00:00:43.460> nexus<00:00:43.820> of 00:00:43.990 --> 00:00:44.000 align:start position:0% public enterprise space so the nexus of 00:00:44.000 --> 00:00:45.640 align:start position:0% public enterprise space so the nexus of the<00:00:44.329> of<00:00:44.660> you<00:00:44.780> know<00:00:44.900> all<00:00:45.020> these<00:00:45.200> themes<00:00:45.440> is 00:00:45.640 --> 00:00:45.650 align:start position:0% the of you know all these themes is 00:00:45.650 --> 00:00:48.069 align:start position:0% the of you know all these themes is really<00:00:45.920> quorum<00:00:46.280> itself<00:00:46.640> and<00:00:46.960> for<00:00:47.960> those<00:00:48.020> of 00:00:48.069 --> 00:00:48.079 align:start position:0% really quorum itself and for those of 00:00:48.079 --> 00:00:49.479 align:start position:0% really quorum itself and for those of you<00:00:48.260> who<00:00:48.470> are<00:00:48.649> not<00:00:48.800> really<00:00:49.100> familiar<00:00:49.220> with 00:00:49.479 --> 00:00:49.489 align:start position:0% you who are not really familiar with 00:00:49.489 --> 00:00:52.030 align:start position:0% you who are not really familiar with quorum<00:00:49.970> quite<00:00:50.810> simply<00:00:51.170> it's<00:00:51.530> a<00:00:51.800> lightweight 00:00:52.030 --> 00:00:52.040 align:start position:0% quorum quite simply it's a lightweight 00:00:52.040 --> 00:00:55.479 align:start position:0% quorum quite simply it's a lightweight fork<00:00:52.489> of<00:00:52.730> guess<00:00:53.079> and<00:00:54.079> so<00:00:54.230> by<00:00:54.410> that<00:00:54.590> I<00:00:54.980> mean<00:00:55.220> you 00:00:55.479 --> 00:00:55.489 align:start position:0% fork of guess and so by that I mean you 00:00:55.489 --> 00:00:57.130 align:start position:0% fork of guess and so by that I mean you can<00:00:55.640> take<00:00:55.850> a<00:00:55.880> smart<00:00:56.420> contract<00:00:56.809> that<00:00:56.960> you<00:00:57.110> have 00:00:57.130 --> 00:00:57.140 align:start position:0% can take a smart contract that you have 00:00:57.140 --> 00:01:00.010 align:start position:0% can take a smart contract that you have written<00:00:57.829> and<00:00:58.130> deployed<00:00:58.460> to<00:00:58.640> the<00:00:58.730> main<00:00:58.880> net<00:00:59.120> and 00:01:00.010 --> 00:01:00.020 align:start position:0% written and deployed to the main net and 00:01:00.020 --> 00:01:01.959 align:start position:0% written and deployed to the main net and you<00:01:00.230> can<00:01:00.380> deploy<00:01:00.590> it<00:01:00.649> to<00:01:00.800> a<00:01:01.040> coral<00:01:01.399> network<00:01:01.760> in 00:01:01.959 --> 00:01:01.969 align:start position:0% you can deploy it to a coral network in 00:01:01.969 --> 00:01:03.940 align:start position:0% you can deploy it to a coral network in exactly<00:01:02.300> the<00:01:02.450> same<00:01:02.480> way<00:01:02.780> without<00:01:02.989> any<00:01:03.350> changes 00:01:03.940 --> 00:01:03.950 align:start position:0% exactly the same way without any changes 00:01:03.950 --> 00:01:05.980 align:start position:0% exactly the same way without any changes which<00:01:04.549> is<00:01:04.729> amazing<00:01:05.239> but<00:01:05.420> also<00:01:05.540> not<00:01:05.780> very 00:01:05.980 --> 00:01:05.990 align:start position:0% which is amazing but also not very 00:01:05.990 --> 00:01:07.420 align:start position:0% which is amazing but also not very exciting<00:01:06.380> if<00:01:06.530> that's<00:01:06.680> all<00:01:06.830> that<00:01:06.860> quorum<00:01:07.220> did 00:01:07.420 --> 00:01:07.430 align:start position:0% exciting if that's all that quorum did 00:01:07.430 --> 00:01:09.370 align:start position:0% exciting if that's all that quorum did so<00:01:08.090> that<00:01:08.630> we'll<00:01:08.780> go<00:01:08.900> through<00:01:08.930> some<00:01:09.229> of<00:01:09.320> the 00:01:09.370 --> 00:01:09.380 align:start position:0% so that we'll go through some of the 00:01:09.380 --> 00:01:11.140 align:start position:0% so that we'll go through some of the additional<00:01:09.710> features<00:01:09.890> that<00:01:10.130> Corum<00:01:10.880> provides 00:01:11.140 --> 00:01:11.150 align:start position:0% additional features that Corum provides 00:01:11.150 --> 00:01:13.360 align:start position:0% additional features that Corum provides as<00:01:11.330> well<00:01:11.680> quorum<00:01:12.680> is<00:01:12.770> designed<00:01:13.100> to<00:01:13.250> our 00:01:13.360 --> 00:01:13.370 align:start position:0% as well quorum is designed to our 00:01:13.370 --> 00:01:14.800 align:start position:0% as well quorum is designed to our present<00:01:13.700> operate<00:01:14.000> within<00:01:14.180> permission 00:01:14.800 --> 00:01:14.810 align:start position:0% present operate within permission 00:01:14.810 --> 00:01:18.430 align:start position:0% present operate within permission networks<00:01:15.350> so<00:01:15.979> we<00:01:16.340> know<00:01:16.520> who<00:01:16.880> the<00:01:17.270> protocol<00:01:17.840> is 00:01:18.430 --> 00:01:18.440 align:start position:0% networks so we know who the protocol is 00:01:18.440 --> 00:01:19.600 align:start position:0% networks so we know who the protocol is geared<00:01:18.710> towards<00:01:19.100> we<00:01:19.220> know<00:01:19.310> who<00:01:19.490> the 00:01:19.600 --> 00:01:19.610 align:start position:0% geared towards we know who the 00:01:19.610 --> 00:01:22.060 align:start position:0% geared towards we know who the participants<00:01:19.880> on<00:01:20.270> the<00:01:20.390> network<00:01:20.780> are<00:01:21.020> and<00:01:21.290> this 00:01:22.060 --> 00:01:22.070 align:start position:0% participants on the network are and this 00:01:22.070 --> 00:01:24.130 align:start position:0% participants on the network are and this gives<00:01:22.400> us<00:01:22.520> you<00:01:23.240> know<00:01:23.299> sembly<00:01:23.690> away<00:01:23.869> from<00:01:24.110> a 00:01:24.130 --> 00:01:24.140 align:start position:0% gives us you know sembly away from a 00:01:24.140 --> 00:01:25.960 align:start position:0% gives us you know sembly away from a consensus<00:01:24.650> perspective<00:01:25.100> as<00:01:25.220> well<00:01:25.369> it<00:01:25.790> makes 00:01:25.960 --> 00:01:25.970 align:start position:0% consensus perspective as well it makes 00:01:25.970 --> 00:01:27.940 align:start position:0% consensus perspective as well it makes us<00:01:26.180> it<00:01:26.630> gives<00:01:27.110> us<00:01:27.200> the<00:01:27.320> ability<00:01:27.380> to<00:01:27.680> have 00:01:27.940 --> 00:01:27.950 align:start position:0% us it gives us the ability to have 00:01:27.950 --> 00:01:30.399 align:start position:0% us it gives us the ability to have faster<00:01:28.369> consensus<00:01:28.850> effectively<00:01:29.409> ultimately 00:01:30.399 --> 00:01:30.409 align:start position:0% faster consensus effectively ultimately 00:01:30.409 --> 00:01:32.710 align:start position:0% faster consensus effectively ultimately though<00:01:30.710> the<00:01:30.860> reason<00:01:31.280> why<00:01:31.400> quorum<00:01:31.850> exists<00:01:32.420> is 00:01:32.710 --> 00:01:32.720 align:start position:0% though the reason why quorum exists is 00:01:32.720 --> 00:01:35.679 align:start position:0% though the reason why quorum exists is to<00:01:33.020> provide<00:01:33.909> enterprises<00:01:34.909> who<00:01:35.119> want<00:01:35.330> to<00:01:35.450> use<00:01:35.659> a 00:01:35.679 --> 00:01:35.689 align:start position:0% to provide enterprises who want to use a 00:01:35.689 --> 00:01:37.810 align:start position:0% to provide enterprises who want to use a theorem<00:01:36.200> with<00:01:36.799> the<00:01:36.979> features<00:01:37.280> that<00:01:37.430> they<00:01:37.549> need 00:01:37.810 --> 00:01:37.820 align:start position:0% theorem with the features that they need 00:01:37.820 --> 00:01:39.250 align:start position:0% theorem with the features that they need to<00:01:38.240> operate<00:01:38.360> within<00:01:38.750> a<00:01:38.869> production 00:01:39.250 --> 00:01:39.260 align:start position:0% to operate within a production 00:01:39.260 --> 00:01:41.500 align:start position:0% to operate within a production environment<00:01:39.350> and<00:01:40.010> because<00:01:40.790> they<00:01:40.939> want<00:01:41.119> to<00:01:41.240> use 00:01:41.500 --> 00:01:41.510 align:start position:0% environment and because they want to use 00:01:41.510 --> 00:01:43.390 align:start position:0% environment and because they want to use aetherium<00:01:42.470> you<00:01:42.619> know<00:01:42.710> one<00:01:42.890> of<00:01:42.920> the<00:01:43.070> goals<00:01:43.280> that 00:01:43.390 --> 00:01:43.400 align:start position:0% aetherium you know one of the goals that 00:01:43.400 --> 00:01:45.550 align:start position:0% aetherium you know one of the goals that we<00:01:43.490> have<00:01:43.580> as<00:01:44.090> a<00:01:44.390> result<00:01:44.630> is<00:01:45.049> to<00:01:45.229> make<00:01:45.380> sure<00:01:45.409> that 00:01:45.550 --> 00:01:45.560 align:start position:0% we have as a result is to make sure that 00:01:45.560 --> 00:01:47.620 align:start position:0% we have as a result is to make sure that quorum<00:01:46.100> stays<00:01:46.700> as<00:01:46.939> close<00:01:47.119> to<00:01:47.479> public 00:01:47.620 --> 00:01:47.630 align:start position:0% quorum stays as close to public 00:01:47.630 --> 00:01:50.109 align:start position:0% quorum stays as close to public aetherium<00:01:48.200> as<00:01:48.350> possible<00:01:48.830> and<00:01:49.759> this<00:01:49.970> week 00:01:50.109 --> 00:01:50.119 align:start position:0% aetherium as possible and this week 00:01:50.119 --> 00:01:53.080 align:start position:0% aetherium as possible and this week actually<00:01:50.540> we<00:01:50.630> just<00:01:50.810> upgraded<00:01:50.990> to<00:01:51.560> gif<00:01:52.090> 1.7.2 00:01:53.080 --> 00:01:53.090 align:start position:0% actually we just upgraded to gif 1.7.2 00:01:53.090 --> 00:01:55.090 align:start position:0% actually we just upgraded to gif 1.7.2 which<00:01:53.750> is<00:01:53.930> actually<00:01:54.380> really<00:01:54.500> great<00:01:54.619> news<00:01:54.920> and 00:01:55.090 --> 00:01:55.100 align:start position:0% which is actually really great news and 00:01:55.100 --> 00:01:57.219 align:start position:0% which is actually really great news and if<00:01:55.189> you<00:01:55.310> use<00:01:55.759> in<00:01:55.970> quorum<00:01:56.360> I<00:01:56.570> think<00:01:57.020> this<00:01:57.110> is 00:01:57.219 --> 00:01:57.229 align:start position:0% if you use in quorum I think this is 00:01:57.229 --> 00:01:58.210 align:start position:0% if you use in quorum I think this is something<00:01:57.380> that<00:01:57.650> you<00:01:57.890> know<00:01:57.979> the<00:01:58.070> user 00:01:58.210 --> 00:01:58.220 align:start position:0% something that you know the user 00:01:58.220 --> 00:02:00.069 align:start position:0% something that you know the user community<00:01:58.549> have<00:01:58.939> been<00:01:59.119> looking<00:01:59.390> at<00:01:59.570> for<00:02:00.049> a 00:02:00.069 --> 00:02:00.079 align:start position:0% community have been looking at for a 00:02:00.079 --> 00:02:00.310 align:start position:0% community have been looking at for a while 00:02:00.310 --> 00:02:00.320 align:start position:0% while 00:02:00.320 --> 00:02:02.710 align:start position:0% while so<00:02:01.220> we're<00:02:01.340> really<00:02:01.490> excited<00:02:01.579> about<00:02:01.939> that<00:02:02.090> but 00:02:02.710 --> 00:02:02.720 align:start position:0% so we're really excited about that but 00:02:02.720 --> 00:02:04.270 align:start position:0% so we're really excited about that but it's<00:02:02.840> more<00:02:03.020> than<00:02:03.110> just<00:02:03.170> that<00:02:03.350> we're<00:02:04.130> also 00:02:04.270 --> 00:02:04.280 align:start position:0% it's more than just that we're also 00:02:04.280 --> 00:02:06.880 align:start position:0% it's more than just that we're also helping<00:02:05.030> provide<00:02:05.750> standards<00:02:06.409> under<00:02:06.799> the 00:02:06.880 --> 00:02:06.890 align:start position:0% helping provide standards under the 00:02:06.890 --> 00:02:08.289 align:start position:0% helping provide standards under the umbrella<00:02:07.189> of<00:02:07.369> the<00:02:07.400> Enterprise<00:02:07.880> aetherium 00:02:08.289 --> 00:02:08.299 align:start position:0% umbrella of the Enterprise aetherium 00:02:08.299 --> 00:02:09.969 align:start position:0% umbrella of the Enterprise aetherium Alliance<00:02:08.659> and<00:02:08.869> really<00:02:09.379> making<00:02:09.649> sure<00:02:09.679> that<00:02:09.830> we 00:02:09.969 --> 00:02:09.979 align:start position:0% Alliance and really making sure that we 00:02:09.979 --> 00:02:11.430 align:start position:0% Alliance and really making sure that we are<00:02:10.160> contributing<00:02:10.520> back<00:02:10.849> to<00:02:10.910> the<00:02:11.090> community 00:02:11.430 --> 00:02:11.440 align:start position:0% are contributing back to the community 00:02:11.440 --> 00:02:14.290 align:start position:0% are contributing back to the community but<00:02:12.440> again<00:02:12.860> really<00:02:13.220> the<00:02:13.280> ultimate<00:02:13.489> goal<00:02:13.760> is<00:02:14.120> to 00:02:14.290 --> 00:02:14.300 align:start position:0% but again really the ultimate goal is to 00:02:14.300 --> 00:02:14.840 align:start position:0% but again really the ultimate goal is to have 00:02:14.840 --> 00:02:14.850 align:start position:0% have 00:02:14.850 --> 00:02:17.150 align:start position:0% have nerium<00:02:15.240> available<00:02:15.810> to<00:02:16.050> enterprises<00:02:16.530> within<00:02:17.130> a 00:02:17.150 --> 00:02:17.160 align:start position:0% nerium available to enterprises within a 00:02:17.160 --> 00:02:19.490 align:start position:0% nerium available to enterprises within a production<00:02:17.700> environment<00:02:17.900> but<00:02:18.900> to<00:02:18.960> do<00:02:19.170> that<00:02:19.320> we 00:02:19.490 --> 00:02:19.500 align:start position:0% production environment but to do that we 00:02:19.500 --> 00:02:21.110 align:start position:0% production environment but to do that we have<00:02:19.650> to<00:02:19.800> solve<00:02:20.010> four<00:02:20.370> requirements<00:02:21.000> that 00:02:21.110 --> 00:02:21.120 align:start position:0% have to solve four requirements that 00:02:21.120 --> 00:02:23.420 align:start position:0% have to solve four requirements that enterprises<00:02:21.690> need<00:02:21.810> and<00:02:22.170> the<00:02:23.010> first<00:02:23.160> one<00:02:23.340> of 00:02:23.420 --> 00:02:23.430 align:start position:0% enterprises need and the first one of 00:02:23.430 --> 00:02:25.480 align:start position:0% enterprises need and the first one of course<00:02:23.490> that<00:02:23.790> always<00:02:24.000> comes<00:02:24.210> up<00:02:24.330> is<00:02:24.540> privacy 00:02:25.480 --> 00:02:25.490 align:start position:0% course that always comes up is privacy 00:02:25.490 --> 00:02:27.980 align:start position:0% course that always comes up is privacy and<00:02:26.490> from<00:02:27.000> a<00:02:27.060> current<00:02:27.240> perspective<00:02:27.750> what<00:02:27.870> we 00:02:27.980 --> 00:02:27.990 align:start position:0% and from a current perspective what we 00:02:27.990 --> 00:02:29.930 align:start position:0% and from a current perspective what we have<00:02:28.200> is<00:02:28.470> the<00:02:28.650> ability<00:02:28.680> to<00:02:29.040> have<00:02:29.340> private 00:02:29.930 --> 00:02:29.940 align:start position:0% have is the ability to have private 00:02:29.940 --> 00:02:32.270 align:start position:0% have is the ability to have private transactions<00:02:30.570> private<00:02:31.410> smart<00:02:31.650> contracts<00:02:32.130> and 00:02:32.270 --> 00:02:32.280 align:start position:0% transactions private smart contracts and 00:02:32.280 --> 00:02:34.940 align:start position:0% transactions private smart contracts and also<00:02:32.790> the<00:02:33.060> ability<00:02:33.120> to<00:02:33.420> exchange<00:02:34.110> assets<00:02:34.410> in<00:02:34.860> a 00:02:34.940 --> 00:02:34.950 align:start position:0% also the ability to exchange assets in a 00:02:34.950 --> 00:02:36.980 align:start position:0% also the ability to exchange assets in a private<00:02:35.280> way<00:02:35.310> and<00:02:35.730> the<00:02:36.480> way<00:02:36.600> that<00:02:36.780> this<00:02:36.840> is 00:02:36.980 --> 00:02:36.990 align:start position:0% private way and the way that this is 00:02:36.990 --> 00:02:39.350 align:start position:0% private way and the way that this is achieved<00:02:37.320> is<00:02:37.500> effectively<00:02:38.090> utilizing<00:02:39.090> two 00:02:39.350 --> 00:02:39.360 align:start position:0% achieved is effectively utilizing two 00:02:39.360 --> 00:02:41.690 align:start position:0% achieved is effectively utilizing two services<00:02:39.990> within<00:02:40.560> the<00:02:40.680> Corum<00:02:40.980> architecture 00:02:41.690 --> 00:02:41.700 align:start position:0% services within the Corum architecture 00:02:41.700 --> 00:02:44.000 align:start position:0% services within the Corum architecture the<00:02:42.120> first<00:02:42.360> is<00:02:42.660> constellation<00:02:43.530> which<00:02:43.890> is 00:02:44.000 --> 00:02:44.010 align:start position:0% the first is constellation which is 00:02:44.010 --> 00:02:45.650 align:start position:0% the first is constellation which is effectively<00:02:44.400> the<00:02:44.490> core<00:02:44.850> privacy<00:02:45.300> service 00:02:45.650 --> 00:02:45.660 align:start position:0% effectively the core privacy service 00:02:45.660 --> 00:02:48.500 align:start position:0% effectively the core privacy service that<00:02:46.380> Corum<00:02:46.710> implements<00:02:47.160> and<00:02:47.340> the<00:02:48.060> second<00:02:48.360> is 00:02:48.500 --> 00:02:48.510 align:start position:0% that Corum implements and the second is 00:02:48.510 --> 00:02:50.630 align:start position:0% that Corum implements and the second is a<00:02:48.540> new<00:02:48.780> one<00:02:49.200> called<00:02:49.530> zsl<00:02:50.070> which<00:02:50.280> stands<00:02:50.520> for 00:02:50.630 --> 00:02:50.640 align:start position:0% a new one called zsl which stands for 00:02:50.640 --> 00:02:53.030 align:start position:0% a new one called zsl which stands for zero<00:02:51.090> knowledge<00:02:51.270> settlement<00:02:52.020> layer<00:02:52.170> which<00:02:52.830> is 00:02:53.030 --> 00:02:53.040 align:start position:0% zero knowledge settlement layer which is 00:02:53.040 --> 00:02:55.340 align:start position:0% zero knowledge settlement layer which is a<00:02:53.280> full<00:02:54.030> implementation<00:02:54.300> of<00:02:54.840> zero<00:02:55.200> knowledge 00:02:55.340 --> 00:02:55.350 align:start position:0% a full implementation of zero knowledge 00:02:55.350 --> 00:02:56.840 align:start position:0% a full implementation of zero knowledge proof<00:02:55.500> within<00:02:55.890> etherium<00:02:56.400> it's<00:02:56.580> something 00:02:56.840 --> 00:02:56.850 align:start position:0% proof within etherium it's something 00:02:56.850 --> 00:02:58.460 align:start position:0% proof within etherium it's something that<00:02:56.940> we've<00:02:57.060> done<00:02:57.270> in<00:02:57.440> collaboration<00:02:58.440> with 00:02:58.460 --> 00:02:58.470 align:start position:0% that we've done in collaboration with 00:02:58.470 --> 00:03:00.710 align:start position:0% that we've done in collaboration with the<00:02:58.650> Z<00:02:58.800> cache<00:02:59.010> team<00:02:59.280> very<00:02:59.490> recently<00:02:59.910> and<00:03:00.210> we'll 00:03:00.710 --> 00:03:00.720 align:start position:0% the Z cache team very recently and we'll 00:03:00.720 --> 00:03:03.020 align:start position:0% the Z cache team very recently and we'll go<00:03:00.870> over<00:03:00.960> what<00:03:01.260> CSL<00:03:01.890> gives<00:03:02.430> us<00:03:02.550> in<00:03:02.670> a<00:03:02.730> moment 00:03:03.020 --> 00:03:03.030 align:start position:0% go over what CSL gives us in a moment 00:03:03.030 --> 00:03:05.930 align:start position:0% go over what CSL gives us in a moment but<00:03:03.900> from<00:03:04.050> a<00:03:04.110> constellation<00:03:04.440> perspective<00:03:05.220> if 00:03:05.930 --> 00:03:05.940 align:start position:0% but from a constellation perspective if 00:03:05.940 --> 00:03:07.760 align:start position:0% but from a constellation perspective if you<00:03:06.060> think<00:03:06.240> about<00:03:06.480> you<00:03:07.200> know<00:03:07.320> I<00:03:07.350> have<00:03:07.650> an 00:03:07.760 --> 00:03:07.770 align:start position:0% you think about you know I have an 00:03:07.770 --> 00:03:09.290 align:start position:0% you think about you know I have an insurance<00:03:08.160> contract<00:03:08.610> for<00:03:08.760> example<00:03:09.150> that<00:03:09.270> I 00:03:09.290 --> 00:03:09.300 align:start position:0% insurance contract for example that I 00:03:09.300 --> 00:03:12.350 align:start position:0% insurance contract for example that I want<00:03:09.570> to<00:03:09.840> deploy<00:03:10.110> with<00:03:11.070> yourself<00:03:11.520> and<00:03:11.790> I<00:03:12.300> don't 00:03:12.350 --> 00:03:12.360 align:start position:0% want to deploy with yourself and I don't 00:03:12.360 --> 00:03:13.940 align:start position:0% want to deploy with yourself and I don't want<00:03:12.570> anyone<00:03:12.810> else<00:03:12.840> on<00:03:13.110> the<00:03:13.200> network<00:03:13.350> to<00:03:13.740> know 00:03:13.940 --> 00:03:13.950 align:start position:0% want anyone else on the network to know 00:03:13.950 --> 00:03:15.680 align:start position:0% want anyone else on the network to know what<00:03:14.220> the<00:03:14.340> details<00:03:14.460> of<00:03:14.850> that<00:03:14.970> contract<00:03:15.360> are 00:03:15.680 --> 00:03:15.690 align:start position:0% what the details of that contract are 00:03:15.690 --> 00:03:17.630 align:start position:0% what the details of that contract are this<00:03:16.590> is<00:03:16.740> where<00:03:16.830> we<00:03:16.950> can<00:03:17.070> use<00:03:17.130> the 00:03:17.630 --> 00:03:17.640 align:start position:0% this is where we can use the 00:03:17.640 --> 00:03:19.030 align:start position:0% this is where we can use the constellation<00:03:18.180> features<00:03:18.540> to<00:03:18.660> actually 00:03:19.030 --> 00:03:19.040 align:start position:0% constellation features to actually 00:03:19.040 --> 00:03:21.380 align:start position:0% constellation features to actually obfuscate<00:03:20.040> that<00:03:20.190> information<00:03:20.700> and<00:03:20.940> so 00:03:21.380 --> 00:03:21.390 align:start position:0% obfuscate that information and so 00:03:21.390 --> 00:03:23.660 align:start position:0% obfuscate that information and so effectively<00:03:21.810> what<00:03:21.960> happens<00:03:22.350> is<00:03:22.620> when<00:03:23.310> I<00:03:23.340> send 00:03:23.660 --> 00:03:23.670 align:start position:0% effectively what happens is when I send 00:03:23.670 --> 00:03:26.570 align:start position:0% effectively what happens is when I send that<00:03:23.730> transaction<00:03:24.330> into<00:03:24.480> the<00:03:24.660> network<00:03:25.020> I<00:03:25.580> make 00:03:26.570 --> 00:03:26.580 align:start position:0% that transaction into the network I make 00:03:26.580 --> 00:03:27.950 align:start position:0% that transaction into the network I make a<00:03:26.610> call<00:03:26.850> to<00:03:27.000> constellation<00:03:27.630> constellation 00:03:27.950 --> 00:03:27.960 align:start position:0% a call to constellation constellation 00:03:27.960 --> 00:03:30.650 align:start position:0% a call to constellation constellation we'll<00:03:28.590> replace<00:03:29.190> the<00:03:29.550> the<00:03:30.030> payload<00:03:30.390> of<00:03:30.540> that 00:03:30.650 --> 00:03:30.660 align:start position:0% we'll replace the the payload of that 00:03:30.660 --> 00:03:32.840 align:start position:0% we'll replace the the payload of that transaction<00:03:31.020> with<00:03:31.800> a<00:03:32.010> hash<00:03:32.280> of<00:03:32.610> the<00:03:32.820> encrypted 00:03:32.840 --> 00:03:32.850 align:start position:0% transaction with a hash of the encrypted 00:03:32.850 --> 00:03:35.390 align:start position:0% transaction with a hash of the encrypted payload<00:03:33.600> and<00:03:33.870> that<00:03:34.350> hash<00:03:34.620> is<00:03:34.830> then<00:03:34.980> globally 00:03:35.390 --> 00:03:35.400 align:start position:0% payload and that hash is then globally 00:03:35.400 --> 00:03:37.130 align:start position:0% payload and that hash is then globally distributed<00:03:35.580> across<00:03:36.060> the<00:03:36.150> network<00:03:36.600> there's 00:03:37.130 --> 00:03:37.140 align:start position:0% distributed across the network there's 00:03:37.140 --> 00:03:38.390 align:start position:0% distributed across the network there's nothing<00:03:37.440> that's<00:03:37.590> revealed<00:03:37.950> about<00:03:38.160> this 00:03:38.390 --> 00:03:38.400 align:start position:0% nothing that's revealed about this 00:03:38.400 --> 00:03:40.700 align:start position:0% nothing that's revealed about this information<00:03:38.970> but<00:03:39.480> what<00:03:39.660> this<00:03:39.780> does<00:03:39.840> is<00:03:40.350> it 00:03:40.700 --> 00:03:40.710 align:start position:0% information but what this does is it 00:03:40.710 --> 00:03:42.110 align:start position:0% information but what this does is it gives<00:03:40.830> us<00:03:41.010> some<00:03:41.190> really<00:03:41.400> nice<00:03:41.520> resiliency 00:03:42.110 --> 00:03:42.120 align:start position:0% gives us some really nice resiliency 00:03:42.120 --> 00:03:43.460 align:start position:0% gives us some really nice resiliency properties<00:03:42.510> which<00:03:42.750> we're<00:03:43.050> not<00:03:43.110> going<00:03:43.170> to<00:03:43.350> get 00:03:43.460 --> 00:03:43.470 align:start position:0% properties which we're not going to get 00:03:43.470 --> 00:03:46.250 align:start position:0% properties which we're not going to get into<00:03:43.680> today<00:03:43.860> but<00:03:44.580> the<00:03:44.700> key<00:03:44.850> here<00:03:45.150> is<00:03:45.180> that<00:03:45.450> we 00:03:46.250 --> 00:03:46.260 align:start position:0% into today but the key here is that we 00:03:46.260 --> 00:03:47.540 align:start position:0% into today but the key here is that we actually<00:03:46.560> also<00:03:46.710> have<00:03:46.980> a<00:03:47.220> shadow 00:03:47.540 --> 00:03:47.550 align:start position:0% actually also have a shadow 00:03:47.550 --> 00:03:49.730 align:start position:0% actually also have a shadow constellation<00:03:48.450> network<00:03:48.780> that<00:03:49.260> runs<00:03:49.500> in<00:03:49.650> the 00:03:49.730 --> 00:03:49.740 align:start position:0% constellation network that runs in the 00:03:49.740 --> 00:03:51.500 align:start position:0% constellation network that runs in the background<00:03:49.830> and<00:03:50.370> so<00:03:50.790> what<00:03:50.940> happens<00:03:51.240> here<00:03:51.300> is 00:03:51.500 --> 00:03:51.510 align:start position:0% background and so what happens here is 00:03:51.510 --> 00:03:53.960 align:start position:0% background and so what happens here is you<00:03:51.660> have<00:03:51.840> a<00:03:52.620> point-to-point<00:03:53.160> communication 00:03:53.960 --> 00:03:53.970 align:start position:0% you have a point-to-point communication 00:03:53.970 --> 00:03:55.520 align:start position:0% you have a point-to-point communication between<00:03:54.120> these<00:03:54.420> constellation<00:03:55.110> nodes<00:03:55.320> of 00:03:55.520 --> 00:03:55.530 align:start position:0% between these constellation nodes of 00:03:55.530 --> 00:03:57.800 align:start position:0% between these constellation nodes of their<00:03:56.040> private<00:03:56.430> information<00:03:56.970> and<00:03:57.120> so<00:03:57.750> you 00:03:57.800 --> 00:03:57.810 align:start position:0% their private information and so you 00:03:57.810 --> 00:04:00.610 align:start position:0% their private information and so you never<00:03:57.990> are<00:03:58.370> globally<00:03:59.370> distributing<00:04:00.000> private 00:04:00.610 --> 00:04:00.620 align:start position:0% never are globally distributing private 00:04:00.620 --> 00:04:02.630 align:start position:0% never are globally distributing private information<00:04:01.620> to<00:04:01.800> parties<00:04:02.160> that<00:04:02.190> shouldn't 00:04:02.630 --> 00:04:02.640 align:start position:0% information to parties that shouldn't 00:04:02.640 --> 00:04:04.820 align:start position:0% information to parties that shouldn't see<00:04:02.850> it<00:04:02.940> but<00:04:03.660> you<00:04:03.780> do<00:04:03.930> end<00:04:04.260> up<00:04:04.410> with<00:04:04.590> this<00:04:04.680> very 00:04:04.820 --> 00:04:04.830 align:start position:0% see it but you do end up with this very 00:04:04.830 --> 00:04:07.550 align:start position:0% see it but you do end up with this very strong<00:04:05.130> pragmatic<00:04:05.820> privacy<00:04:06.300> solution<00:04:06.720> the 00:04:07.550 --> 00:04:07.560 align:start position:0% strong pragmatic privacy solution the 00:04:07.560 --> 00:04:09.590 align:start position:0% strong pragmatic privacy solution the side<00:04:07.800> effect<00:04:08.160> though<00:04:08.310> is<00:04:08.580> that<00:04:08.610> if<00:04:09.060> you<00:04:09.480> are 00:04:09.590 --> 00:04:09.600 align:start position:0% side effect though is that if you are 00:04:09.600 --> 00:04:11.300 align:start position:0% side effect though is that if you are not<00:04:09.780> actually<00:04:09.930> part<00:04:10.380> of<00:04:10.650> you<00:04:10.980> know<00:04:11.070> for 00:04:11.300 --> 00:04:11.310 align:start position:0% not actually part of you know for 00:04:11.310 --> 00:04:14.000 align:start position:0% not actually part of you know for example<00:04:11.670> a<00:04:11.730> chain<00:04:12.000> of<00:04:12.300> asset<00:04:12.810> transfers<00:04:13.320> then 00:04:14.000 --> 00:04:14.010 align:start position:0% example a chain of asset transfers then 00:04:14.010 --> 00:04:15.800 align:start position:0% example a chain of asset transfers then if<00:04:14.310> you're<00:04:14.610> trying<00:04:14.820> to<00:04:14.910> sell<00:04:15.060> me<00:04:15.090> an<00:04:15.360> asset<00:04:15.690> I 00:04:15.800 --> 00:04:15.810 align:start position:0% if you're trying to sell me an asset I 00:04:15.810 --> 00:04:17.240 align:start position:0% if you're trying to sell me an asset I don't<00:04:15.960> necessarily<00:04:16.170> have<00:04:16.739> guarantees<00:04:17.220> that 00:04:17.240 --> 00:04:17.250 align:start position:0% don't necessarily have guarantees that 00:04:17.250 --> 00:04:19.430 align:start position:0% don't necessarily have guarantees that you<00:04:18.000> are<00:04:18.180> the<00:04:18.330> rightful<00:04:18.660> owner<00:04:18.870> of<00:04:18.960> the<00:04:19.049> asset 00:04:19.430 --> 00:04:19.440 align:start position:0% you are the rightful owner of the asset 00:04:19.440 --> 00:04:21.320 align:start position:0% you are the rightful owner of the asset or<00:04:19.620> that<00:04:20.070> you<00:04:20.160> haven't<00:04:20.400> sold<00:04:20.609> sold<00:04:21.000> it<00:04:21.120> on<00:04:21.210> to 00:04:21.320 --> 00:04:21.330 align:start position:0% or that you haven't sold sold it on to 00:04:21.330 --> 00:04:23.060 align:start position:0% or that you haven't sold sold it on to someone<00:04:21.510> else<00:04:21.780> and<00:04:22.049> so<00:04:22.560> this<00:04:22.680> is<00:04:22.800> where<00:04:22.950> we 00:04:23.060 --> 00:04:23.070 align:start position:0% someone else and so this is where we 00:04:23.070 --> 00:04:25.940 align:start position:0% someone else and so this is where we leverage<00:04:24.000> the<00:04:24.150> CSL<00:04:24.540> implementation<00:04:25.229> so<00:04:25.890> if 00:04:25.940 --> 00:04:25.950 align:start position:0% leverage the CSL implementation so if 00:04:25.950 --> 00:04:28.220 align:start position:0% leverage the CSL implementation so if you<00:04:26.040> think<00:04:26.160> about<00:04:26.510> public<00:04:27.510> if<00:04:28.020> you 00:04:28.220 --> 00:04:28.230 align:start position:0% you think about public if you 00:04:28.230 --> 00:04:30.920 align:start position:0% you think about public if you we're<00:04:28.770> balances<00:04:29.370> and<00:04:29.700> amounts<00:04:30.270> are<00:04:30.510> you<00:04:30.810> know 00:04:30.920 --> 00:04:30.930 align:start position:0% we're balances and amounts are you know 00:04:30.930 --> 00:04:32.690 align:start position:0% we're balances and amounts are you know globally<00:04:31.320> visible<00:04:31.470> clearly<00:04:32.430> from<00:04:32.580> an 00:04:32.690 --> 00:04:32.700 align:start position:0% globally visible clearly from an 00:04:32.700 --> 00:04:34.100 align:start position:0% globally visible clearly from an enterprise<00:04:33.000> perspective<00:04:33.150> this<00:04:33.810> is<00:04:33.960> not 00:04:34.100 --> 00:04:34.110 align:start position:0% enterprise perspective this is not 00:04:34.110 --> 00:04:35.570 align:start position:0% enterprise perspective this is not really<00:04:34.380> something<00:04:34.650> that's<00:04:34.740> going<00:04:35.010> to<00:04:35.070> fly<00:04:35.250> and 00:04:35.570 --> 00:04:35.580 align:start position:0% really something that's going to fly and 00:04:35.580 --> 00:04:37.670 align:start position:0% really something that's going to fly and so<00:04:36.150> with<00:04:36.300> the<00:04:36.390> CSL<00:04:36.750> implementation<00:04:37.440> what<00:04:37.560> we 00:04:37.670 --> 00:04:37.680 align:start position:0% so with the CSL implementation what we 00:04:37.680 --> 00:04:40.460 align:start position:0% so with the CSL implementation what we have<00:04:37.860> is<00:04:38.130> a<00:04:38.460> full<00:04:38.730> obfuscation<00:04:39.720> and<00:04:39.960> shielding 00:04:40.460 --> 00:04:40.470 align:start position:0% have is a full obfuscation and shielding 00:04:40.470 --> 00:04:43.280 align:start position:0% have is a full obfuscation and shielding of<00:04:40.710> balances<00:04:41.340> of<00:04:41.610> positions<00:04:42.210> of<00:04:42.660> transaction 00:04:43.280 --> 00:04:43.290 align:start position:0% of balances of positions of transaction 00:04:43.290 --> 00:04:45.290 align:start position:0% of balances of positions of transaction amounts<00:04:43.650> and<00:04:43.860> also<00:04:44.310> of<00:04:44.640> who<00:04:45.000> is<00:04:45.120> actually 00:04:45.290 --> 00:04:45.300 align:start position:0% amounts and also of who is actually 00:04:45.300 --> 00:04:46.730 align:start position:0% amounts and also of who is actually taking<00:04:45.750> part<00:04:45.870> in<00:04:46.050> the<00:04:46.110> transaction<00:04:46.590> in<00:04:46.680> the 00:04:46.730 --> 00:04:46.740 align:start position:0% taking part in the transaction in the 00:04:46.740 --> 00:04:49.100 align:start position:0% taking part in the transaction in the first<00:04:46.950> place<00:04:47.130> and<00:04:47.400> so<00:04:48.120> this<00:04:48.300> combination<00:04:48.930> of 00:04:49.100 --> 00:04:49.110 align:start position:0% first place and so this combination of 00:04:49.110 --> 00:04:51.620 align:start position:0% first place and so this combination of constellation<00:04:49.950> and<00:04:50.160> zsl<00:04:50.700> gives<00:04:51.360> us<00:04:51.480> this 00:04:51.620 --> 00:04:51.630 align:start position:0% constellation and zsl gives us this 00:04:51.630 --> 00:04:54.110 align:start position:0% constellation and zsl gives us this really<00:04:51.780> nice<00:04:52.020> hybrid<00:04:52.500> hybrid<00:04:53.120> privacy 00:04:54.110 --> 00:04:54.120 align:start position:0% really nice hybrid hybrid privacy 00:04:54.120 --> 00:04:55.810 align:start position:0% really nice hybrid hybrid privacy environment<00:04:54.660> within<00:04:54.960> the<00:04:55.140> quorum<00:04:55.410> network 00:04:55.810 --> 00:04:55.820 align:start position:0% environment within the quorum network 00:04:55.820 --> 00:04:58.430 align:start position:0% environment within the quorum network but<00:04:56.820> of<00:04:56.910> course<00:04:57.090> privacy<00:04:57.810> is<00:04:57.900> not<00:04:58.080> the<00:04:58.260> only 00:04:58.430 --> 00:04:58.440 align:start position:0% but of course privacy is not the only 00:04:58.440 --> 00:05:00.140 align:start position:0% but of course privacy is not the only thing<00:04:58.590> that<00:04:58.620> enterprises<00:04:59.250> need<00:04:59.430> they<00:05:00.120> have 00:05:00.140 --> 00:05:00.150 align:start position:0% thing that enterprises need they have 00:05:00.150 --> 00:05:03.170 align:start position:0% thing that enterprises need they have high<00:05:00.720> performance<00:05:01.380> requirements<00:05:02.190> very<00:05:02.820> often 00:05:03.170 --> 00:05:03.180 align:start position:0% high performance requirements very often 00:05:03.180 --> 00:05:05.840 align:start position:0% high performance requirements very often given<00:05:03.870> the<00:05:03.900> high<00:05:04.530> volumes<00:05:05.010> that<00:05:05.190> need<00:05:05.700> to<00:05:05.820> be 00:05:05.840 --> 00:05:05.850 align:start position:0% given the high volumes that need to be 00:05:05.850 --> 00:05:07.220 align:start position:0% given the high volumes that need to be processed<00:05:06.060> and<00:05:06.510> as<00:05:06.600> a<00:05:06.660> result<00:05:07.020> the<00:05:07.110> high 00:05:07.220 --> 00:05:07.230 align:start position:0% processed and as a result the high 00:05:07.230 --> 00:05:08.960 align:start position:0% processed and as a result the high throughput<00:05:07.470> and<00:05:07.890> they<00:05:08.340> also<00:05:08.520> need<00:05:08.730> to<00:05:08.850> make 00:05:08.960 --> 00:05:08.970 align:start position:0% throughput and they also need to make 00:05:08.970 --> 00:05:11.510 align:start position:0% throughput and they also need to make sure<00:05:09.000> that<00:05:09.360> those<00:05:09.930> transactions<00:05:10.620> are<00:05:10.950> not 00:05:11.510 --> 00:05:11.520 align:start position:0% sure that those transactions are not 00:05:11.520 --> 00:05:12.790 align:start position:0% sure that those transactions are not only<00:05:11.700> processed<00:05:12.090> quickly<00:05:12.420> but<00:05:12.630> also 00:05:12.790 --> 00:05:12.800 align:start position:0% only processed quickly but also 00:05:12.800 --> 00:05:15.380 align:start position:0% only processed quickly but also definitively<00:05:13.800> so<00:05:14.460> once<00:05:14.670> a<00:05:14.760> transaction<00:05:15.270> is 00:05:15.380 --> 00:05:15.390 align:start position:0% definitively so once a transaction is 00:05:15.390 --> 00:05:17.360 align:start position:0% definitively so once a transaction is actually<00:05:15.710> written<00:05:16.710> you<00:05:16.980> know<00:05:17.040> they<00:05:17.190> don't 00:05:17.360 --> 00:05:17.370 align:start position:0% actually written you know they don't 00:05:17.370 --> 00:05:19.520 align:start position:0% actually written you know they don't want<00:05:17.490> to<00:05:17.580> have<00:05:17.760> it<00:05:17.940> reversed<00:05:18.360> such<00:05:19.230> that<00:05:19.440> the 00:05:19.520 --> 00:05:19.530 align:start position:0% want to have it reversed such that the 00:05:19.530 --> 00:05:20.870 align:start position:0% want to have it reversed such that the transaction<00:05:19.980> all<00:05:20.130> of<00:05:20.220> a<00:05:20.280> sudden<00:05:20.520> didn't<00:05:20.760> take 00:05:20.870 --> 00:05:20.880 align:start position:0% transaction all of a sudden didn't take 00:05:20.880 --> 00:05:22.010 align:start position:0% transaction all of a sudden didn't take place<00:05:21.000> and<00:05:21.300> it<00:05:21.420> was<00:05:21.510> only<00:05:21.630> going<00:05:21.840> to<00:05:21.900> be 00:05:22.010 --> 00:05:22.020 align:start position:0% place and it was only going to be 00:05:22.020 --> 00:05:24.050 align:start position:0% place and it was only going to be included<00:05:22.830> in<00:05:22.920> the<00:05:23.010> chain<00:05:23.190> in<00:05:23.520> a<00:05:23.640> later<00:05:23.790> point 00:05:24.050 --> 00:05:24.060 align:start position:0% included in the chain in a later point 00:05:24.060 --> 00:05:26.240 align:start position:0% included in the chain in a later point and<00:05:24.390> finally<00:05:25.260> they<00:05:25.380> need<00:05:25.560> to<00:05:25.680> know<00:05:25.800> who 00:05:26.240 --> 00:05:26.250 align:start position:0% and finally they need to know who 00:05:26.250 --> 00:05:27.890 align:start position:0% and finally they need to know who they're<00:05:26.460> actually<00:05:26.760> transacting<00:05:27.270> with<00:05:27.300> you 00:05:27.890 --> 00:05:27.900 align:start position:0% they're actually transacting with you 00:05:27.900 --> 00:05:29.720 align:start position:0% they're actually transacting with you know<00:05:27.990> we<00:05:28.080> can't<00:05:28.290> have<00:05:28.530> this<00:05:28.740> in<00:05:29.160> an<00:05:29.310> enterprise 00:05:29.720 --> 00:05:29.730 align:start position:0% know we can't have this in an enterprise 00:05:29.730 --> 00:05:31.190 align:start position:0% know we can't have this in an enterprise environment<00:05:29.910> the<00:05:30.450> pseudonymous<00:05:30.960> or 00:05:31.190 --> 00:05:31.200 align:start position:0% environment the pseudonymous or 00:05:31.200 --> 00:05:34.370 align:start position:0% environment the pseudonymous or anonymous<00:05:32.270> participation<00:05:33.270> network<00:05:33.570> and<00:05:33.840> so 00:05:34.370 --> 00:05:34.380 align:start position:0% anonymous participation network and so 00:05:34.380 --> 00:05:35.960 align:start position:0% anonymous participation network and so the<00:05:34.500> way<00:05:34.590> that<00:05:34.620> quorum<00:05:35.130> solves<00:05:35.730> for<00:05:35.760> these 00:05:35.960 --> 00:05:35.970 align:start position:0% the way that quorum solves for these 00:05:35.970 --> 00:05:38.720 align:start position:0% the way that quorum solves for these things<00:05:36.240> is<00:05:36.540> on<00:05:37.380> the<00:05:37.530> performance<00:05:37.980> side<00:05:38.130> you 00:05:38.720 --> 00:05:38.730 align:start position:0% things is on the performance side you 00:05:38.730 --> 00:05:40.010 align:start position:0% things is on the performance side you know<00:05:38.850> quorum<00:05:39.240> is<00:05:39.330> pretty<00:05:39.510> quick<00:05:39.690> we<00:05:39.900> have 00:05:40.010 --> 00:05:40.020 align:start position:0% know quorum is pretty quick we have 00:05:40.020 --> 00:05:41.360 align:start position:0% know quorum is pretty quick we have blocks<00:05:40.290> that<00:05:40.440> it<00:05:40.530> creates<00:05:40.770> at<00:05:40.890> every<00:05:41.100> 50 00:05:41.360 --> 00:05:41.370 align:start position:0% blocks that it creates at every 50 00:05:41.370 --> 00:05:43.400 align:start position:0% blocks that it creates at every 50 milliseconds<00:05:42.050> transaction<00:05:43.050> throughput 00:05:43.400 --> 00:05:43.410 align:start position:0% milliseconds transaction throughput 00:05:43.410 --> 00:05:44.870 align:start position:0% milliseconds transaction throughput around<00:05:43.710> a<00:05:43.890> thousand<00:05:44.220> transactions<00:05:44.700> per 00:05:44.870 --> 00:05:44.880 align:start position:0% around a thousand transactions per 00:05:44.880 --> 00:05:48.230 align:start position:0% around a thousand transactions per second<00:05:45.240> for<00:05:45.840> simple<00:05:46.320> value<00:05:46.590> transfers<00:05:47.010> and<00:05:47.250> we 00:05:48.230 --> 00:05:48.240 align:start position:0% second for simple value transfers and we 00:05:48.240 --> 00:05:50.750 align:start position:0% second for simple value transfers and we ensure<00:05:48.600> that<00:05:48.630> transaction<00:05:49.640> transactions<00:05:50.640> are 00:05:50.750 --> 00:05:50.760 align:start position:0% ensure that transaction transactions are 00:05:50.760 --> 00:05:53.210 align:start position:0% ensure that transaction transactions are finalized<00:05:51.210> immediately<00:05:51.840> so<00:05:52.410> the<00:05:52.710> consensus 00:05:53.210 --> 00:05:53.220 align:start position:0% finalized immediately so the consensus 00:05:53.220 --> 00:05:55.160 align:start position:0% finalized immediately so the consensus mechanisms<00:05:53.760> that<00:05:53.910> we<00:05:54.030> use<00:05:54.060> I<00:05:54.540> don't<00:05:54.990> actually 00:05:55.160 --> 00:05:55.170 align:start position:0% mechanisms that we use I don't actually 00:05:55.170 --> 00:05:56.870 align:start position:0% mechanisms that we use I don't actually allow<00:05:55.470> for<00:05:55.500> Forks<00:05:56.010> so<00:05:56.160> you<00:05:56.250> have<00:05:56.370> a<00:05:56.400> guarantee 00:05:56.870 --> 00:05:56.880 align:start position:0% allow for Forks so you have a guarantee 00:05:56.880 --> 00:05:58.160 align:start position:0% allow for Forks so you have a guarantee that<00:05:57.120> once<00:05:57.300> your<00:05:57.510> transaction<00:05:57.930> has<00:05:58.020> been 00:05:58.160 --> 00:05:58.170 align:start position:0% that once your transaction has been 00:05:58.170 --> 00:05:59.480 align:start position:0% that once your transaction has been committed<00:05:58.590> to<00:05:58.620> the<00:05:58.710> chain<00:05:58.950> it's<00:05:59.160> not<00:05:59.280> going<00:05:59.430> to 00:05:59.480 --> 00:05:59.490 align:start position:0% committed to the chain it's not going to 00:05:59.490 --> 00:06:01.190 align:start position:0% committed to the chain it's not going to be<00:05:59.580> reversed<00:05:59.940> and<00:06:00.210> then<00:06:00.990> from<00:06:01.140> a 00:06:01.190 --> 00:06:01.200 align:start position:0% be reversed and then from a 00:06:01.200 --> 00:06:03.440 align:start position:0% be reversed and then from a permissioning<00:06:01.620> perspective<00:06:02.210> we<00:06:03.210> have<00:06:03.420> a 00:06:03.440 --> 00:06:03.450 align:start position:0% permissioning perspective we have a 00:06:03.450 --> 00:06:05.390 align:start position:0% permissioning perspective we have a strong<00:06:03.810> protocol<00:06:04.230> that<00:06:04.350> ensures<00:06:04.680> that<00:06:04.710> you 00:06:05.390 --> 00:06:05.400 align:start position:0% strong protocol that ensures that you 00:06:05.400 --> 00:06:06.860 align:start position:0% strong protocol that ensures that you have<00:06:05.520> to<00:06:05.610> be<00:06:05.700> authenticated<00:06:06.360> and<00:06:06.450> authorized 00:06:06.860 --> 00:06:06.870 align:start position:0% have to be authenticated and authorized 00:06:06.870 --> 00:06:09.770 align:start position:0% have to be authenticated and authorized onto<00:06:07.230> the<00:06:07.320> network<00:06:07.500> and<00:06:07.950> if<00:06:08.610> you<00:06:08.700> are<00:06:08.820> not<00:06:09.060> then 00:06:09.770 --> 00:06:09.780 align:start position:0% onto the network and if you are not then 00:06:09.780 --> 00:06:10.910 align:start position:0% onto the network and if you are not then basically<00:06:10.350> you<00:06:10.500> cannot<00:06:10.740> actually 00:06:10.910 --> 00:06:10.920 align:start position:0% basically you cannot actually 00:06:10.920 --> 00:06:13.730 align:start position:0% basically you cannot actually communicate<00:06:11.460> with<00:06:11.610> any<00:06:11.760> other<00:06:11.970> node<00:06:12.410> and<00:06:13.410> it's 00:06:13.730 --> 00:06:13.740 align:start position:0% communicate with any other node and it's 00:06:13.740 --> 00:06:15.470 align:start position:0% communicate with any other node and it's probably<00:06:13.980> a<00:06:14.010> good<00:06:14.160> time<00:06:14.340> to<00:06:14.490> actually<00:06:14.640> talk 00:06:15.470 --> 00:06:15.480 align:start position:0% probably a good time to actually talk 00:06:15.480 --> 00:06:17.780 align:start position:0% probably a good time to actually talk about<00:06:15.650> permission<00:06:16.650> block<00:06:16.920> chains<00:06:17.190> in<00:06:17.430> general 00:06:17.780 --> 00:06:17.790 align:start position:0% about permission block chains in general 00:06:17.790 --> 00:06:19.070 align:start position:0% about permission block chains in general you<00:06:17.970> know<00:06:18.030> the<00:06:18.150> question<00:06:18.420> always<00:06:18.600> comes<00:06:18.690> up 00:06:19.070 --> 00:06:19.080 align:start position:0% you know the question always comes up 00:06:19.080 --> 00:06:21.590 align:start position:0% you know the question always comes up why<00:06:19.890> do<00:06:19.950> you<00:06:20.370> need<00:06:20.550> a<00:06:20.580> permission<00:06:20.850> blossom<00:06:21.300> why 00:06:21.590 --> 00:06:21.600 align:start position:0% why do you need a permission blossom why 00:06:21.600 --> 00:06:23.990 align:start position:0% why do you need a permission blossom why not<00:06:21.810> just<00:06:21.960> use<00:06:22.320> a<00:06:22.590> regular<00:06:23.000> centralized 00:06:23.990 --> 00:06:24.000 align:start position:0% not just use a regular centralized 00:06:24.000 --> 00:06:26.360 align:start position:0% not just use a regular centralized database<00:06:24.450> or<00:06:24.720> distributed<00:06:25.380> database<00:06:25.770> and 00:06:26.360 --> 00:06:26.370 align:start position:0% database or distributed database and 00:06:26.370 --> 00:06:28.340 align:start position:0% database or distributed database and when<00:06:26.460> you<00:06:26.550> start<00:06:26.760> to<00:06:26.850> look<00:06:26.970> at<00:06:27.150> the<00:06:27.660> properties 00:06:28.340 --> 00:06:28.350 align:start position:0% when you start to look at the properties 00:06:28.350 --> 00:06:30.320 align:start position:0% when you start to look at the properties of<00:06:28.520> traditional<00:06:29.520> distributed<00:06:30.000> database 00:06:30.320 --> 00:06:30.330 align:start position:0% of traditional distributed database 00:06:30.330 --> 00:06:32.210 align:start position:0% of traditional distributed database technology<00:06:30.840> and<00:06:31.020> you<00:06:31.080> have<00:06:31.290> you<00:06:31.830> know<00:06:31.950> this 00:06:32.210 --> 00:06:32.220 align:start position:0% technology and you have you know this 00:06:32.220 --> 00:06:34.730 align:start position:0% technology and you have you know this trust<00:06:32.520> among<00:06:32.790> nodes<00:06:33.030> this<00:06:33.390> closed<00:06:34.140> network 00:06:34.730 --> 00:06:34.740 align:start position:0% trust among nodes this closed network 00:06:34.740 --> 00:06:38.750 align:start position:0% trust among nodes this closed network you<00:06:35.370> have<00:06:36.080> strong<00:06:37.080> consistency<00:06:37.830> this<00:06:38.460> starts 00:06:38.750 --> 00:06:38.760 align:start position:0% you have strong consistency this starts 00:06:38.760 --> 00:06:40.100 align:start position:0% you have strong consistency this starts to<00:06:38.790> sound<00:06:38.970> very<00:06:39.270> much<00:06:39.330> like<00:06:39.480> the<00:06:39.750> things<00:06:39.960> that 00:06:40.100 --> 00:06:40.110 align:start position:0% to sound very much like the things that 00:06:40.110 --> 00:06:41.060 align:start position:0% to sound very much like the things that we<00:06:40.230> need<00:06:40.440> from<00:06:40.590> an 00:06:41.060 --> 00:06:41.070 align:start position:0% we need from an 00:06:41.070 --> 00:06:42.860 align:start position:0% we need from an suspected<00:06:41.610> you<00:06:41.730> know<00:06:41.820> all<00:06:41.910> the<00:06:42.090> requirements 00:06:42.860 --> 00:06:42.870 align:start position:0% suspected you know all the requirements 00:06:42.870 --> 00:06:44.540 align:start position:0% suspected you know all the requirements that<00:06:43.110> we've<00:06:43.260> just<00:06:43.350> kind<00:06:43.500> of<00:06:43.590> gone<00:06:43.650> through<00:06:44.040> so 00:06:44.540 --> 00:06:44.550 align:start position:0% that we've just kind of gone through so 00:06:44.550 --> 00:06:46.640 align:start position:0% that we've just kind of gone through so why<00:06:44.790> would<00:06:45.030> we<00:06:45.120> consider<00:06:45.350> you<00:06:46.350> know<00:06:46.470> there's 00:06:46.640 --> 00:06:46.650 align:start position:0% why would we consider you know there's 00:06:46.650 --> 00:06:48.110 align:start position:0% why would we consider you know there's public<00:06:47.040> blockchain<00:06:47.460> or<00:06:47.640> this<00:06:47.730> blockchain 00:06:48.110 --> 00:06:48.120 align:start position:0% public blockchain or this blockchain 00:06:48.120 --> 00:06:49.790 align:start position:0% public blockchain or this blockchain implementation<00:06:48.810> where<00:06:48.990> you<00:06:49.080> have<00:06:49.260> only 00:06:49.790 --> 00:06:49.800 align:start position:0% implementation where you have only 00:06:49.800 --> 00:06:51.530 align:start position:0% implementation where you have only eventual<00:06:50.370> consistency<00:06:50.550> you<00:06:51.180> don't<00:06:51.360> know 00:06:51.530 --> 00:06:51.540 align:start position:0% eventual consistency you don't know 00:06:51.540 --> 00:06:52.610 align:start position:0% eventual consistency you don't know who's<00:06:51.780> on<00:06:51.870> the<00:06:51.930> network 00:06:52.610 --> 00:06:52.620 align:start position:0% who's on the network 00:06:52.620 --> 00:06:54.040 align:start position:0% who's on the network you<00:06:53.100> don't<00:06:53.250> have<00:06:53.460> the<00:06:53.580> high<00:06:53.730> throughput 00:06:54.040 --> 00:06:54.050 align:start position:0% you don't have the high throughput 00:06:54.050 --> 00:06:57.230 align:start position:0% you don't have the high throughput environment<00:06:55.050> and<00:06:55.260> really<00:06:56.010> the<00:06:56.130> answer<00:06:56.240> comes 00:06:57.230 --> 00:06:57.240 align:start position:0% environment and really the answer comes 00:06:57.240 --> 00:06:58.580 align:start position:0% environment and really the answer comes down<00:06:57.420> to<00:06:57.570> the<00:06:57.690> fact<00:06:57.900> that<00:06:57.990> even<00:06:58.350> in<00:06:58.470> this 00:06:58.580 --> 00:06:58.590 align:start position:0% down to the fact that even in this 00:06:58.590 --> 00:07:00.260 align:start position:0% down to the fact that even in this permissioned<00:06:59.100> environment<00:06:59.760> in<00:06:59.910> this<00:07:00.000> closed 00:07:00.260 --> 00:07:00.270 align:start position:0% permissioned environment in this closed 00:07:00.270 --> 00:07:02.030 align:start position:0% permissioned environment in this closed network<00:07:00.630> we<00:07:01.200> still<00:07:01.410> only<00:07:01.530> have<00:07:01.620> partial 00:07:02.030 --> 00:07:02.040 align:start position:0% network we still only have partial 00:07:02.040 --> 00:07:04.040 align:start position:0% network we still only have partial trusts<00:07:02.640> we<00:07:02.760> don't<00:07:02.940> have<00:07:03.090> this<00:07:03.210> unconditional 00:07:04.040 --> 00:07:04.050 align:start position:0% trusts we don't have this unconditional 00:07:04.050 --> 00:07:06.410 align:start position:0% trusts we don't have this unconditional trust<00:07:04.590> amongst<00:07:04.890> network<00:07:05.250> participants<00:07:06.240> and 00:07:06.410 --> 00:07:06.420 align:start position:0% trust amongst network participants and 00:07:06.420 --> 00:07:08.330 align:start position:0% trust amongst network participants and so<00:07:06.900> actually<00:07:07.260> from<00:07:07.530> a<00:07:07.620> permission<00:07:07.860> network 00:07:08.330 --> 00:07:08.340 align:start position:0% so actually from a permission network 00:07:08.340 --> 00:07:09.440 align:start position:0% so actually from a permission network perspective<00:07:08.790> and<00:07:08.940> from<00:07:09.030> a<00:07:09.150> quorum 00:07:09.440 --> 00:07:09.450 align:start position:0% perspective and from a quorum 00:07:09.450 --> 00:07:11.240 align:start position:0% perspective and from a quorum perspective<00:07:09.900> we<00:07:10.320> kind<00:07:10.470> of<00:07:10.560> land<00:07:10.740> somewhere<00:07:11.010> in 00:07:11.240 --> 00:07:11.250 align:start position:0% perspective we kind of land somewhere in 00:07:11.250 --> 00:07:13.100 align:start position:0% perspective we kind of land somewhere in the<00:07:11.340> middle<00:07:11.610> and<00:07:11.820> we<00:07:12.210> end<00:07:12.330> up<00:07:12.420> taking<00:07:12.780> you<00:07:13.050> know 00:07:13.100 --> 00:07:13.110 align:start position:0% the middle and we end up taking you know 00:07:13.110 --> 00:07:15.620 align:start position:0% the middle and we end up taking you know the<00:07:13.230> best<00:07:13.380> of<00:07:13.500> both<00:07:13.680> worlds<00:07:14.040> from<00:07:14.190> from<00:07:14.850> both 00:07:15.620 --> 00:07:15.630 align:start position:0% the best of both worlds from from both 00:07:15.630 --> 00:07:17.570 align:start position:0% the best of both worlds from from both the<00:07:15.810> distributed<00:07:16.770> database<00:07:17.100> technology 00:07:17.570 --> 00:07:17.580 align:start position:0% the distributed database technology 00:07:17.580 --> 00:07:19.310 align:start position:0% the distributed database technology environment<00:07:18.090> as<00:07:18.180> well<00:07:18.300> as<00:07:18.450> the<00:07:18.660> the<00:07:18.930> public 00:07:19.310 --> 00:07:19.320 align:start position:0% environment as well as the the public 00:07:19.320 --> 00:07:21.410 align:start position:0% environment as well as the the public blockchain<00:07:19.650> space<00:07:19.890> so<00:07:20.550> we<00:07:20.700> have<00:07:20.850> guarantees 00:07:21.410 --> 00:07:21.420 align:start position:0% blockchain space so we have guarantees 00:07:21.420 --> 00:07:23.390 align:start position:0% blockchain space so we have guarantees around<00:07:21.630> the<00:07:21.930> mutability<00:07:22.260> we<00:07:22.740> have<00:07:22.920> guarantees 00:07:23.390 --> 00:07:23.400 align:start position:0% around the mutability we have guarantees 00:07:23.400 --> 00:07:25.160 align:start position:0% around the mutability we have guarantees around<00:07:23.930> auditability 00:07:25.160 --> 00:07:25.170 align:start position:0% around auditability 00:07:25.170 --> 00:07:27.010 align:start position:0% around auditability and<00:07:25.500> we<00:07:25.770> have<00:07:25.920> the<00:07:26.040> ability<00:07:26.370> to<00:07:26.400> have<00:07:26.640> multiple 00:07:27.010 --> 00:07:27.020 align:start position:0% and we have the ability to have multiple 00:07:27.020 --> 00:07:29.450 align:start position:0% and we have the ability to have multiple writers<00:07:28.020> write<00:07:28.320> to<00:07:28.470> the<00:07:28.590> to<00:07:29.160> the<00:07:29.250> chain 00:07:29.450 --> 00:07:29.460 align:start position:0% writers write to the to the chain 00:07:29.460 --> 00:07:32.030 align:start position:0% writers write to the to the chain without<00:07:30.150> having<00:07:30.570> to<00:07:30.720> cede<00:07:30.960> control<00:07:30.990> to<00:07:31.650> some 00:07:32.030 --> 00:07:32.040 align:start position:0% without having to cede control to some 00:07:32.040 --> 00:07:34.070 align:start position:0% without having to cede control to some central<00:07:32.460> party<00:07:32.820> to<00:07:33.030> manage<00:07:33.360> conflict 00:07:34.070 --> 00:07:34.080 align:start position:0% central party to manage conflict 00:07:34.080 --> 00:07:36.380 align:start position:0% central party to manage conflict resolution<00:07:34.560> for<00:07:34.710> example<00:07:35.130> but<00:07:35.820> the<00:07:36.000> question 00:07:36.380 --> 00:07:36.390 align:start position:0% resolution for example but the question 00:07:36.390 --> 00:07:38.390 align:start position:0% resolution for example but the question of<00:07:36.480> course<00:07:36.630> is<00:07:36.840> well<00:07:37.530> what<00:07:37.800> do<00:07:37.890> you<00:07:37.980> do<00:07:38.130> from<00:07:38.340> a 00:07:38.390 --> 00:07:38.400 align:start position:0% of course is well what do you do from a 00:07:38.400 --> 00:07:40.910 align:start position:0% of course is well what do you do from a consensus<00:07:38.910> perspective<00:07:39.390> in<00:07:40.380> a<00:07:40.530> permissioned 00:07:40.910 --> 00:07:40.920 align:start position:0% consensus perspective in a permissioned 00:07:40.920 --> 00:07:43.250 align:start position:0% consensus perspective in a permissioned environment<00:07:41.460> we<00:07:41.820> don't<00:07:42.000> need<00:07:42.240> proof<00:07:42.990> of<00:07:43.110> work 00:07:43.250 --> 00:07:43.260 align:start position:0% environment we don't need proof of work 00:07:43.260 --> 00:07:44.840 align:start position:0% environment we don't need proof of work we<00:07:43.500> don't<00:07:43.650> need<00:07:43.740> proof<00:07:43.980> of<00:07:44.100> stake<00:07:44.340> you<00:07:44.640> know<00:07:44.670> we 00:07:44.840 --> 00:07:44.850 align:start position:0% we don't need proof of stake you know we 00:07:44.850 --> 00:07:46.240 align:start position:0% we don't need proof of stake you know we don't<00:07:44.940> have<00:07:45.060> the<00:07:45.180> same<00:07:45.480> in<00:07:45.630> sense<00:07:45.810> of 00:07:46.240 --> 00:07:46.250 align:start position:0% don't have the same in sense of 00:07:46.250 --> 00:07:48.200 align:start position:0% don't have the same in sense of incentivization<00:07:47.250> model<00:07:47.490> that<00:07:47.610> you<00:07:47.700> have<00:07:47.910> in 00:07:48.200 --> 00:07:48.210 align:start position:0% incentivization model that you have in 00:07:48.210 --> 00:07:50.540 align:start position:0% incentivization model that you have in public<00:07:48.900> aetherium<00:07:49.320> so<00:07:49.860> what<00:07:50.040> we<00:07:50.130> can<00:07:50.250> do<00:07:50.430> is 00:07:50.540 --> 00:07:50.550 align:start position:0% public aetherium so what we can do is 00:07:50.550 --> 00:07:52.220 align:start position:0% public aetherium so what we can do is start<00:07:50.760> to<00:07:50.880> implement<00:07:51.090> some<00:07:51.420> some<00:07:51.900> different 00:07:52.220 --> 00:07:52.230 align:start position:0% start to implement some some different 00:07:52.230 --> 00:07:54.710 align:start position:0% start to implement some some different and<00:07:52.440> quicker<00:07:52.650> consensus<00:07:53.220> mechanisms<00:07:53.760> to<00:07:54.570> date 00:07:54.710 --> 00:07:54.720 align:start position:0% and quicker consensus mechanisms to date 00:07:54.720 --> 00:07:57.590 align:start position:0% and quicker consensus mechanisms to date we've<00:07:54.900> had<00:07:55.080> two<00:07:55.380> in<00:07:56.300> quorum<00:07:57.300> we<00:07:57.450> have<00:07:57.570> a 00:07:57.590 --> 00:07:57.600 align:start position:0% we've had two in quorum we have a 00:07:57.600 --> 00:08:00.590 align:start position:0% we've had two in quorum we have a configurable<00:07:58.590> consensus<00:07:59.280> environment<00:07:59.790> on 00:08:00.590 --> 00:08:00.600 align:start position:0% configurable consensus environment on 00:08:00.600 --> 00:08:02.570 align:start position:0% configurable consensus environment on the<00:08:00.750> one<00:08:00.870> hand<00:08:01.050> we<00:08:01.200> have<00:08:01.230> quorum<00:08:02.130> chain<00:08:02.340> which 00:08:02.570 --> 00:08:02.580 align:start position:0% the one hand we have quorum chain which 00:08:02.580 --> 00:08:05.300 align:start position:0% the one hand we have quorum chain which is<00:08:02.610> a<00:08:02.730> smart<00:08:03.060> contract<00:08:03.240> based<00:08:03.770> protocol<00:08:04.770> that 00:08:05.300 --> 00:08:05.310 align:start position:0% is a smart contract based protocol that 00:08:05.310 --> 00:08:07.910 align:start position:0% is a smart contract based protocol that has<00:08:05.370> virtues<00:08:06.060> and<00:08:06.420> block<00:08:06.720> makers<00:08:07.110> kind<00:08:07.830> of 00:08:07.910 --> 00:08:07.920 align:start position:0% has virtues and block makers kind of 00:08:07.920 --> 00:08:09.440 align:start position:0% has virtues and block makers kind of akin<00:08:08.160> to<00:08:08.400> proof<00:08:08.640> of<00:08:08.760> authority<00:08:09.180> which<00:08:09.330> is 00:08:09.440 --> 00:08:09.450 align:start position:0% akin to proof of authority which is 00:08:09.450 --> 00:08:10.370 align:start position:0% akin to proof of authority which is something<00:08:09.600> we're<00:08:09.840> going<00:08:09.930> to<00:08:09.990> be<00:08:10.050> looking<00:08:10.350> to 00:08:10.370 --> 00:08:10.380 align:start position:0% something we're going to be looking to 00:08:10.380 --> 00:08:12.500 align:start position:0% something we're going to be looking to implement<00:08:10.650> and<00:08:11.040> then<00:08:11.550> we<00:08:11.670> have<00:08:11.820> raft<00:08:12.210> on<00:08:12.420> the 00:08:12.500 --> 00:08:12.510 align:start position:0% implement and then we have raft on the 00:08:12.510 --> 00:08:13.790 align:start position:0% implement and then we have raft on the other<00:08:12.630> on<00:08:12.960> the<00:08:13.080> other<00:08:13.110> hand<00:08:13.440> which<00:08:13.590> is 00:08:13.790 --> 00:08:13.800 align:start position:0% other on the other hand which is 00:08:13.800 --> 00:08:16.400 align:start position:0% other on the other hand which is obviously<00:08:14.490> a<00:08:14.550> formally<00:08:14.910> proven<00:08:15.270> protocol<00:08:16.080> it 00:08:16.400 --> 00:08:16.410 align:start position:0% obviously a formally proven protocol it 00:08:16.410 --> 00:08:19.250 align:start position:0% obviously a formally proven protocol it is<00:08:16.770> actually<00:08:17.130> based<00:08:17.340> on<00:08:17.610> the<00:08:17.940> core<00:08:18.390> OS<00:08:18.510> HCD 00:08:19.250 --> 00:08:19.260 align:start position:0% is actually based on the core OS HCD 00:08:19.260 --> 00:08:21.080 align:start position:0% is actually based on the core OS HCD implementation<00:08:19.860> which<00:08:19.980> is<00:08:20.100> used<00:08:20.310> in<00:08:20.460> things 00:08:21.080 --> 00:08:21.090 align:start position:0% implementation which is used in things 00:08:21.090 --> 00:08:22.790 align:start position:0% implementation which is used in things like<00:08:21.180> kubernetes<00:08:21.660> and<00:08:21.780> Cloud<00:08:22.170> Foundry<00:08:22.380> and 00:08:22.790 --> 00:08:22.800 align:start position:0% like kubernetes and Cloud Foundry and 00:08:22.800 --> 00:08:25.070 align:start position:0% like kubernetes and Cloud Foundry and this<00:08:23.340> is<00:08:23.490> the<00:08:24.030> consensus<00:08:24.510> mechanism<00:08:24.960> that 00:08:25.070 --> 00:08:25.080 align:start position:0% this is the consensus mechanism that 00:08:25.080 --> 00:08:26.510 align:start position:0% this is the consensus mechanism that gives<00:08:25.260> us<00:08:25.380> a<00:08:25.470> lot<00:08:25.590> of<00:08:25.680> the<00:08:25.800> properties<00:08:26.490> that 00:08:26.510 --> 00:08:26.520 align:start position:0% gives us a lot of the properties that 00:08:26.520 --> 00:08:28.640 align:start position:0% gives us a lot of the properties that we've<00:08:26.730> already<00:08:26.880> spoken<00:08:27.150> about<00:08:27.420> but<00:08:28.290> neither 00:08:28.640 --> 00:08:28.650 align:start position:0% we've already spoken about but neither 00:08:28.650 --> 00:08:31.610 align:start position:0% we've already spoken about but neither of<00:08:28.950> them<00:08:29.190> are<00:08:29.630> Byzantine<00:08:30.630> fault<00:08:30.990> tolerant<00:08:31.380> and 00:08:31.610 --> 00:08:31.620 align:start position:0% of them are Byzantine fault tolerant and 00:08:31.620 --> 00:08:34.580 align:start position:0% of them are Byzantine fault tolerant and so<00:08:31.800> when<00:08:32.130> we<00:08:32.250> heard<00:08:32.490> that<00:08:32.700> a<00:08:32.760> me<00:08:33.120> had<00:08:33.810> written<00:08:34.229> a 00:08:34.580 --> 00:08:34.590 align:start position:0% so when we heard that a me had written a 00:08:34.590 --> 00:08:36.230 align:start position:0% so when we heard that a me had written a Byzantine<00:08:35.250> fault<00:08:35.460> tolerant<00:08:35.790> consensus 00:08:36.230 --> 00:08:36.240 align:start position:0% Byzantine fault tolerant consensus 00:08:36.240 --> 00:08:38.810 align:start position:0% Byzantine fault tolerant consensus mechanism<00:08:36.750> targeted<00:08:37.500> at<00:08:37.590> Geth<00:08:37.830> we<00:08:38.490> got<00:08:38.669> very 00:08:38.810 --> 00:08:38.820 align:start position:0% mechanism targeted at Geth we got very 00:08:38.820 --> 00:08:40.190 align:start position:0% mechanism targeted at Geth we got very excited<00:08:39.390> and<00:08:39.510> quickly<00:08:39.900> started 00:08:40.190 --> 00:08:40.200 align:start position:0% excited and quickly started 00:08:40.200 --> 00:08:42.380 align:start position:0% excited and quickly started collaborating<00:08:40.410> with<00:08:41.070> them<00:08:41.219> to<00:08:41.400> have<00:08:41.580> have 00:08:42.380 --> 00:08:42.390 align:start position:0% collaborating with them to have have 00:08:42.390 --> 00:08:44.060 align:start position:0% collaborating with them to have have their<00:08:42.570> consensus<00:08:43.110> mechanism<00:08:43.560> implemented 00:08:44.060 --> 00:08:44.070 align:start position:0% their consensus mechanism implemented 00:08:44.070 --> 00:08:46.070 align:start position:0% their consensus mechanism implemented within<00:08:44.550> quorum<00:08:44.940> and<00:08:45.120> so<00:08:45.630> with<00:08:45.780> that<00:08:45.870> let<00:08:46.050> me 00:08:46.070 --> 00:08:46.080 align:start position:0% within quorum and so with that let me 00:08:46.080 --> 00:08:48.110 align:start position:0% within quorum and so with that let me hand<00:08:46.170> over<00:08:46.470> to<00:08:46.590> you<00:08:46.800> say<00:08:46.980> who<00:08:47.160> can<00:08:47.310> tell<00:08:47.970> you<00:08:48.060> a 00:08:48.110 --> 00:08:48.120 align:start position:0% hand over to you say who can tell you a 00:08:48.120 --> 00:08:49.250 align:start position:0% hand over to you say who can tell you a little<00:08:48.180> bit<00:08:48.360> more<00:08:48.480> about<00:08:48.690> a<00:08:48.750> me<00:08:48.960> and<00:08:49.110> also 00:08:49.250 --> 00:08:49.260 align:start position:0% little bit more about a me and also 00:08:49.260 --> 00:08:51.860 align:start position:0% little bit more about a me and also Istanbul 00:08:51.860 --> 00:08:51.870 align:start position:0% 00:08:51.870 --> 00:08:57.150 align:start position:0% [Applause] 00:08:57.150 --> 00:08:57.160 align:start position:0% [Applause] 00:08:57.160 --> 00:08:59.280 align:start position:0% [Applause] good<00:08:57.580> morning<00:08:57.820> everyone<00:08:58.060> my<00:08:58.660> name<00:08:58.810> is<00:08:58.839> util<00:08:59.170> in 00:08:59.280 --> 00:08:59.290 align:start position:0% good morning everyone my name is util in 00:08:59.290 --> 00:09:02.430 align:start position:0% good morning everyone my name is util in front<00:08:59.860> of<00:09:00.040> me<00:09:00.420> to<00:09:01.420> get<00:09:01.570> started<00:09:01.930> I<00:09:02.110> would<00:09:02.290> like 00:09:02.430 --> 00:09:02.440 align:start position:0% front of me to get started I would like 00:09:02.440 --> 00:09:03.990 align:start position:0% front of me to get started I would like to<00:09:02.620> quickly<00:09:02.920> introduce<00:09:03.100> Amy 00:09:03.990 --> 00:09:04.000 align:start position:0% to quickly introduce Amy 00:09:04.000 --> 00:09:06.329 align:start position:0% to quickly introduce Amy and<00:09:04.089> what<00:09:04.420> we<00:09:04.540> are<00:09:04.570> doing<00:09:04.690> there<00:09:05.050> I<00:09:05.260> mean<00:09:06.220> it's 00:09:06.329 --> 00:09:06.339 align:start position:0% and what we are doing there I mean it's 00:09:06.339 --> 00:09:08.160 align:start position:0% and what we are doing there I mean it's a<00:09:06.459> blockchain<00:09:06.820> service<00:09:07.270> company<00:09:07.690> based<00:09:08.050> in 00:09:08.160 --> 00:09:08.170 align:start position:0% a blockchain service company based in 00:09:08.170 --> 00:09:11.100 align:start position:0% a blockchain service company based in Taiwan<00:09:08.410> we<00:09:09.370> provide<00:09:09.730> launching<00:09:10.600> services 00:09:11.100 --> 00:09:11.110 align:start position:0% Taiwan we provide launching services 00:09:11.110 --> 00:09:12.810 align:start position:0% Taiwan we provide launching services include<00:09:11.529> blockchain<00:09:12.250> infrastructure 00:09:12.810 --> 00:09:12.820 align:start position:0% include blockchain infrastructure 00:09:12.820 --> 00:09:15.180 align:start position:0% include blockchain infrastructure planning<00:09:13.390> applications<00:09:14.080> and<00:09:14.440> plots<00:09:15.040> and 00:09:15.180 --> 00:09:15.190 align:start position:0% planning applications and plots and 00:09:15.190 --> 00:09:17.850 align:start position:0% planning applications and plots and research<00:09:15.570> our<00:09:16.570> most<00:09:16.870> well<00:09:17.050> known<00:09:17.110> projects 00:09:17.850 --> 00:09:17.860 align:start position:0% research our most well known projects 00:09:17.860 --> 00:09:21.420 align:start position:0% research our most well known projects are<00:09:18.330> Istanbul<00:09:19.330> P<00:09:19.480> of<00:09:19.570> T<00:09:19.800> which<00:09:20.800> are<00:09:20.950> we<00:09:21.279> are 00:09:21.420 --> 00:09:21.430 align:start position:0% are Istanbul P of T which are we are 00:09:21.430 --> 00:09:23.280 align:start position:0% are Istanbul P of T which are we are presenting<00:09:21.850> today<00:09:22.089> and<00:09:22.120> the<00:09:22.930> decentralized 00:09:23.280 --> 00:09:23.290 align:start position:0% presenting today and the decentralized 00:09:23.290 --> 00:09:25.320 align:start position:0% presenting today and the decentralized ledger<00:09:23.709> for<00:09:24.100> cost<00:09:24.310> bank<00:09:24.550> transactions<00:09:25.120> in 00:09:25.320 --> 00:09:25.330 align:start position:0% ledger for cost bank transactions in 00:09:25.330 --> 00:09:27.810 align:start position:0% ledger for cost bank transactions in Taiwan<00:09:25.920> while<00:09:26.920> doing<00:09:27.130> this<00:09:27.250> project<00:09:27.760> without 00:09:27.810 --> 00:09:27.820 align:start position:0% Taiwan while doing this project without 00:09:27.820 --> 00:09:30.120 align:start position:0% Taiwan while doing this project without current<00:09:28.540> pows<00:09:29.110> i<00:09:29.260> doesn't<00:09:29.560> quite<00:09:29.770> meet<00:09:29.920> our 00:09:30.120 --> 00:09:30.130 align:start position:0% current pows i doesn't quite meet our 00:09:30.130 --> 00:09:32.430 align:start position:0% current pows i doesn't quite meet our knee<00:09:30.339> and<00:09:30.580> that's<00:09:31.480> why<00:09:31.630> we<00:09:31.839> implemented 00:09:32.430 --> 00:09:32.440 align:start position:0% knee and that's why we implemented 00:09:32.440 --> 00:09:36.600 align:start position:0% knee and that's why we implemented Istanbul<00:09:33.070> P<00:09:33.190> of<00:09:33.279> T<00:09:34.440> Istanbul<00:09:35.440> PFT<00:09:35.860> or<00:09:36.070> IB<00:09:36.339> ft 00:09:36.600 --> 00:09:36.610 align:start position:0% Istanbul P of T Istanbul PFT or IB ft 00:09:36.610 --> 00:09:39.750 align:start position:0% Istanbul P of T Istanbul PFT or IB ft was<00:09:36.910> inspired<00:09:37.390> by<00:09:37.600> casual<00:09:38.589> risk<00:09:38.800> of<00:09:39.010> practical 00:09:39.750 --> 00:09:39.760 align:start position:0% was inspired by casual risk of practical 00:09:39.760 --> 00:09:41.579 align:start position:0% was inspired by casual risk of practical Byzantine<00:09:40.149> for<00:09:40.360> tolerance<00:09:40.690> paper<00:09:40.990> publishing 00:09:41.579 --> 00:09:41.589 align:start position:0% Byzantine for tolerance paper publishing 00:09:41.589 --> 00:09:42.840 align:start position:0% Byzantine for tolerance paper publishing in<00:09:42.190> 99 00:09:42.840 --> 00:09:42.850 align:start position:0% in 99 00:09:42.850 --> 00:09:45.120 align:start position:0% in 99 without<00:09:43.779> blood<00:09:44.020> tonight's<00:09:44.410> implementation 00:09:45.120 --> 00:09:45.130 align:start position:0% without blood tonight's implementation 00:09:45.130 --> 00:09:47.850 align:start position:0% without blood tonight's implementation yes<00:09:45.670> of<00:09:45.790> the<00:09:45.850> following<00:09:46.149> key<00:09:46.360> features<00:09:46.860> first 00:09:47.850 --> 00:09:47.860 align:start position:0% yes of the following key features first 00:09:47.860 --> 00:09:51.060 align:start position:0% yes of the following key features first of<00:09:48.010> all<00:09:48.190> blocks<00:09:48.730> in<00:09:49.000> IB<00:09:49.240> FD<00:09:49.480> R<00:09:49.660> final<00:09:50.070> which 00:09:51.060 --> 00:09:51.070 align:start position:0% of all blocks in IB FD R final which 00:09:51.070 --> 00:09:54.329 align:start position:0% of all blocks in IB FD R final which means<00:09:51.339> no<00:09:52.330> fork<00:09:52.870> is<00:09:53.050> possible<00:09:53.589> and<00:09:53.740> no 00:09:54.329 --> 00:09:54.339 align:start position:0% means no fork is possible and no 00:09:54.339 --> 00:09:57.510 align:start position:0% means no fork is possible and no complements<00:09:55.029> are<00:09:55.180> necessary<00:09:55.630> anymore<00:09:56.520> in 00:09:57.510 --> 00:09:57.520 align:start position:0% complements are necessary anymore in 00:09:57.520 --> 00:09:59.699 align:start position:0% complements are necessary anymore in terms<00:09:57.579> of<00:09:57.910> governance<00:09:58.270> he<00:09:59.050> has<00:09:59.170> a<00:09:59.200> manageable 00:09:59.699 --> 00:09:59.709 align:start position:0% terms of governance he has a manageable 00:09:59.709 --> 00:10:03.510 align:start position:0% terms of governance he has a manageable they<00:10:00.220> did<00:10:00.399> have<00:10:00.550> set<00:10:00.810> so<00:10:01.810> that<00:10:02.250> editors<00:10:03.250> can 00:10:03.510 --> 00:10:03.520 align:start position:0% they did have set so that editors can 00:10:03.520 --> 00:10:05.240 align:start position:0% they did have set so that editors can add<00:10:03.790> or<00:10:04.029> remove<00:10:04.060> other<00:10:04.570> waiters 00:10:05.240 --> 00:10:05.250 align:start position:0% add or remove other waiters 00:10:05.250 --> 00:10:08.880 align:start position:0% add or remove other waiters dynamically<00:10:06.250> by<00:10:06.579> building<00:10:07.230> on<00:10:08.230> performance 00:10:08.880 --> 00:10:08.890 align:start position:0% dynamically by building on performance 00:10:08.890 --> 00:10:11.460 align:start position:0% dynamically by building on performance you<00:10:09.579> can<00:10:09.760> process<00:10:09.970> around<00:10:10.329> 800<00:10:10.990> transactions 00:10:11.460 --> 00:10:11.470 align:start position:0% you can process around 800 transactions 00:10:11.470 --> 00:10:13.620 align:start position:0% you can process around 800 transactions per<00:10:11.680> second<00:10:12.070> at<00:10:12.190> the<00:10:12.730> same<00:10:12.910> time<00:10:13.120> he<00:10:13.300> has<00:10:13.450> the 00:10:13.620 --> 00:10:13.630 align:start position:0% per second at the same time he has the 00:10:13.630 --> 00:10:17.579 align:start position:0% per second at the same time he has the same<00:10:13.810> no<00:10:13.959> scalability<00:10:14.649> as<00:10:14.800> is<00:10:15.010> -<00:10:15.250> this<00:10:15.630> and<00:10:16.630> in 00:10:17.579 --> 00:10:17.589 align:start position:0% same no scalability as is - this and in 00:10:17.589 --> 00:10:20.190 align:start position:0% same no scalability as is - this and in order<00:10:17.800> put<00:10:18.040> in<00:10:18.430> order<00:10:18.670> to<00:10:18.820> make<00:10:19.060> blocks<00:10:19.570> self 00:10:20.190 --> 00:10:20.200 align:start position:0% order put in order to make blocks self 00:10:20.200 --> 00:10:22.949 align:start position:0% order put in order to make blocks self verifiable<00:10:20.980> when<00:10:21.579> put<00:10:21.790> consensus<00:10:22.270> proof<00:10:22.600> into 00:10:22.949 --> 00:10:22.959 align:start position:0% verifiable when put consensus proof into 00:10:22.959 --> 00:10:25.550 align:start position:0% verifiable when put consensus proof into block<00:10:23.170> headers<00:10:23.579> which<00:10:24.579> also<00:10:24.790> means 00:10:25.550 --> 00:10:25.560 align:start position:0% block headers which also means 00:10:25.560 --> 00:10:27.810 align:start position:0% block headers which also means implementing<00:10:26.560> like<00:10:26.980> client<00:10:27.399> will<00:10:27.490> be<00:10:27.579> quite 00:10:27.810 --> 00:10:27.820 align:start position:0% implementing like client will be quite 00:10:27.820 --> 00:10:31.170 align:start position:0% implementing like client will be quite simple<00:10:28.230> last<00:10:29.230> but<00:10:29.410> not<00:10:29.529> least<00:10:29.820> IP<00:10:30.820> of<00:10:31.029> the 00:10:31.170 --> 00:10:31.180 align:start position:0% simple last but not least IP of the 00:10:31.180 --> 00:10:34.050 align:start position:0% simple last but not least IP of the implemented<00:10:31.750> gossip<00:10:32.110> network<00:10:32.700> so<00:10:33.700> strong 00:10:34.050 --> 00:10:34.060 align:start position:0% implemented gossip network so strong 00:10:34.060 --> 00:10:36.090 align:start position:0% implemented gossip network so strong connection<00:10:34.600> are<00:10:34.839> not<00:10:35.079> required<00:10:35.500> to<00:10:35.740> make<00:10:35.920> the 00:10:36.090 --> 00:10:36.100 align:start position:0% connection are not required to make the 00:10:36.100 --> 00:10:42.000 align:start position:0% connection are not required to make the consensus<00:10:36.610> work<00:10:36.850> a<00:10:39.360> B<00:10:40.360> of<00:10:40.420> T<00:10:40.600> is<00:10:40.839> a<00:10:41.050> three-phase 00:10:42.000 --> 00:10:42.010 align:start position:0% consensus work a B of T is a three-phase 00:10:42.010 --> 00:10:45.000 align:start position:0% consensus work a B of T is a three-phase state<00:10:42.820> machine<00:10:43.089> replication<00:10:43.720> algorithm<00:10:44.230> here 00:10:45.000 --> 00:10:45.010 align:start position:0% state machine replication algorithm here 00:10:45.010 --> 00:10:47.040 align:start position:0% state machine replication algorithm here I<00:10:45.070> like<00:10:45.339> to<00:10:45.370> use<00:10:45.670> a<00:10:45.700> simple<00:10:46.149> network<00:10:46.540> setup<00:10:46.779> to 00:10:47.040 --> 00:10:47.050 align:start position:0% I like to use a simple network setup to 00:10:47.050 --> 00:10:50.490 align:start position:0% I like to use a simple network setup to demonstrate<00:10:47.529> how<00:10:47.680> i<00:10:47.709> IP<00:10:48.279> FD<00:10:48.670> works<00:10:49.290> say<00:10:50.290> there 00:10:50.490 --> 00:10:50.500 align:start position:0% demonstrate how i IP FD works say there 00:10:50.500 --> 00:10:53.970 align:start position:0% demonstrate how i IP FD works say there are<00:10:50.589> four<00:10:50.800> waiters<00:10:51.310> in<00:10:51.579> this<00:10:51.760> network<00:10:52.290> in<00:10:53.290> the 00:10:53.970 --> 00:10:53.980 align:start position:0% are four waiters in this network in the 00:10:53.980 --> 00:10:56.880 align:start position:0% are four waiters in this network in the first<00:10:54.250> step<00:10:54.579> or<00:10:54.820> pre<00:10:55.300> prepare<00:10:55.630> staff<00:10:55.930> one<00:10:56.709> of 00:10:56.880 --> 00:10:56.890 align:start position:0% first step or pre prepare staff one of 00:10:56.890 --> 00:10:58.769 align:start position:0% first step or pre prepare staff one of the<00:10:57.070> waiters<00:10:57.430> will<00:10:57.820> be<00:10:57.910> selected<00:10:58.360> as<00:10:58.570> the 00:10:58.769 --> 00:10:58.779 align:start position:0% the waiters will be selected as the 00:10:58.779 --> 00:10:59.310 align:start position:0% the waiters will be selected as the proposer 00:10:59.310 --> 00:10:59.320 align:start position:0% proposer 00:10:59.320 --> 00:11:02.160 align:start position:0% proposer who<00:11:00.190> is<00:11:00.339> in<00:11:00.579> charge<00:11:00.850> of<00:11:01.029> proposed<00:11:01.570> a<00:11:01.720> new<00:11:01.900> block 00:11:02.160 --> 00:11:02.170 align:start position:0% who is in charge of proposed a new block 00:11:02.170 --> 00:11:04.970 align:start position:0% who is in charge of proposed a new block proposal 00:11:04.970 --> 00:11:04.980 align:start position:0% 00:11:04.980 --> 00:11:09.389 align:start position:0% the<00:11:05.980> waiters<00:11:06.460> can't<00:11:07.050> accept<00:11:08.050> that<00:11:08.140> to<00:11:09.010> ignore 00:11:09.389 --> 00:11:09.399 align:start position:0% the waiters can't accept that to ignore 00:11:09.399 --> 00:11:12.360 align:start position:0% the waiters can't accept that to ignore that<00:11:09.640> or<00:11:09.850> start<00:11:10.540> a<00:11:10.630> round<00:11:10.779> change<00:11:11.160> say<00:11:12.160> they 00:11:12.360 --> 00:11:12.370 align:start position:0% that or start a round change say they 00:11:12.370 --> 00:11:14.970 align:start position:0% that or start a round change say they accept<00:11:13.000> that<00:11:13.060> then<00:11:13.899> they<00:11:14.350> will<00:11:14.529> go<00:11:14.710> cast 00:11:14.970 --> 00:11:14.980 align:start position:0% accept that then they will go cast 00:11:14.980 --> 00:11:19.310 align:start position:0% accept that then they will go cast prepare<00:11:15.580> messages<00:11:16.149> to<00:11:16.570> other<00:11:16.750> validators 00:11:19.310 --> 00:11:19.320 align:start position:0% prepare messages to other validators 00:11:19.320 --> 00:11:21.930 align:start position:0% prepare messages to other validators when<00:11:20.320> they<00:11:20.440> receive<00:11:20.800> more<00:11:21.250> than<00:11:21.310> 2/3<00:11:21.910> of 00:11:21.930 --> 00:11:21.940 align:start position:0% when they receive more than 2/3 of 00:11:21.940 --> 00:11:25.079 align:start position:0% when they receive more than 2/3 of prepare<00:11:22.810> messages<00:11:23.260> and<00:11:23.500> agree<00:11:24.459> on<00:11:24.640> committing 00:11:25.079 --> 00:11:25.089 align:start position:0% prepare messages and agree on committing 00:11:25.089 --> 00:11:27.540 align:start position:0% prepare messages and agree on committing the<00:11:25.300> plug<00:11:25.510> into<00:11:25.720> blockchain<00:11:26.260> they<00:11:27.010> will 00:11:27.540 --> 00:11:27.550 align:start position:0% the plug into blockchain they will 00:11:27.550 --> 00:11:29.760 align:start position:0% the plug into blockchain they will forecast<00:11:28.480> coming<00:11:28.810> messages<00:11:29.320> to<00:11:29.589> other 00:11:29.760 --> 00:11:29.770 align:start position:0% forecast coming messages to other 00:11:29.770 --> 00:11:34.170 align:start position:0% forecast coming messages to other validators<00:11:31.860> finally<00:11:32.860> when<00:11:33.670> they<00:11:33.760> received 00:11:34.170 --> 00:11:34.180 align:start position:0% validators finally when they received 00:11:34.180 --> 00:11:36.720 align:start position:0% validators finally when they received more<00:11:34.390> than<00:11:34.450> 2/3<00:11:34.990> of<00:11:35.020> coming<00:11:35.500> messages<00:11:35.920> they 00:11:36.720 --> 00:11:36.730 align:start position:0% more than 2/3 of coming messages they 00:11:36.730 --> 00:11:38.370 align:start position:0% more than 2/3 of coming messages they can<00:11:36.880> install<00:11:37.120> a<00:11:37.240> plug-in<00:11:37.480> to<00:11:37.690> blockchain<00:11:38.260> and 00:11:38.370 --> 00:11:38.380 align:start position:0% can install a plug-in to blockchain and 00:11:38.380 --> 00:11:42.680 align:start position:0% can install a plug-in to blockchain and broadcasted<00:11:39.250> the<00:11:39.580> block<00:11:39.820> to<00:11:40.120> other<00:11:40.270> nodes<00:11:40.770> and 00:11:42.680 --> 00:11:42.690 align:start position:0% broadcasted the block to other nodes and 00:11:42.690 --> 00:11:46.320 align:start position:0% broadcasted the block to other nodes and this<00:11:43.890> concludes<00:11:44.890> us<00:11:45.040> wrong<00:11:45.310> so<00:11:45.880> in<00:11:46.029> the<00:11:46.120> nest 00:11:46.320 --> 00:11:46.330 align:start position:0% this concludes us wrong so in the nest 00:11:46.330 --> 00:11:48.389 align:start position:0% this concludes us wrong so in the nest wrong<00:11:46.570> the<00:11:46.959> nest<00:11:47.170> proposal<00:11:47.770> will<00:11:47.860> be<00:11:47.890> selected 00:11:48.389 --> 00:11:48.399 align:start position:0% wrong the nest proposal will be selected 00:11:48.399 --> 00:11:54.720 align:start position:0% wrong the nest proposal will be selected and<00:11:48.520> proposal<00:11:49.360> next<00:11:49.540> block<00:11:52.740> IB<00:11:53.740> of<00:11:54.010> T<00:11:54.190> can<00:11:54.459> take 00:11:54.720 --> 00:11:54.730 align:start position:0% and proposal next block IB of T can take 00:11:54.730 --> 00:11:59.430 align:start position:0% and proposal next block IB of T can take up<00:11:54.910> to<00:11:54.940> 1/3<00:11:55.600> of<00:11:55.810> 40<00:11:56.320> nodes<00:11:57.810> here<00:11:58.810> I<00:11:58.839> like<00:11:59.080> to<00:11:59.260> use 00:11:59.430 --> 00:11:59.440 align:start position:0% up to 1/3 of 40 nodes here I like to use 00:11:59.440 --> 00:12:01.440 align:start position:0% up to 1/3 of 40 nodes here I like to use a<00:11:59.470> simple<00:12:00.070> example<00:12:00.520> to<00:12:00.550> demonstrate<00:12:00.760> how<00:12:01.390> the 00:12:01.440 --> 00:12:01.450 align:start position:0% a simple example to demonstrate how the 00:12:01.450 --> 00:12:05.280 align:start position:0% a simple example to demonstrate how the network<00:12:01.839> react<00:12:02.350> to<00:12:02.640> malicious<00:12:03.640> behaviour<00:12:04.290> say 00:12:05.280 --> 00:12:05.290 align:start position:0% network react to malicious behaviour say 00:12:05.290 --> 00:12:09.240 align:start position:0% network react to malicious behaviour say there<00:12:05.560> is<00:12:05.680> a<00:12:06.180> dishonest<00:12:07.290> proposer<00:12:08.290> who<00:12:09.070> always 00:12:09.240 --> 00:12:09.250 align:start position:0% there is a dishonest proposer who always 00:12:09.250 --> 00:12:13.079 align:start position:0% there is a dishonest proposer who always propose<00:12:09.850> invalid<00:12:10.450> block<00:12:11.610> the<00:12:12.610> network<00:12:12.970> would 00:12:13.079 --> 00:12:13.089 align:start position:0% propose invalid block the network would 00:12:13.089 --> 00:12:16.310 align:start position:0% propose invalid block the network would detect<00:12:13.450> that<00:12:13.920> install<00:12:14.920> a<00:12:14.950> run<00:12:15.220> change<00:12:15.459> process 00:12:16.310 --> 00:12:16.320 align:start position:0% detect that install a run change process 00:12:16.320 --> 00:12:18.810 align:start position:0% detect that install a run change process the<00:12:17.320> wrong<00:12:17.500> change<00:12:17.740> process<00:12:18.160> is<00:12:18.400> trying<00:12:18.640> to 00:12:18.810 --> 00:12:18.820 align:start position:0% the wrong change process is trying to 00:12:18.820 --> 00:12:22.010 align:start position:0% the wrong change process is trying to find<00:12:19.029> out<00:12:19.209> who<00:12:19.570> becomes<00:12:19.930> the<00:12:20.050> next<00:12:20.140> proposer 00:12:22.010 --> 00:12:22.020 align:start position:0% find out who becomes the next proposer 00:12:22.020 --> 00:12:25.530 align:start position:0% find out who becomes the next proposer once<00:12:23.020> this<00:12:23.230> is<00:12:23.410> a<00:12:23.440> decided<00:12:24.010> the<00:12:25.000> next<00:12:25.270> proposal 00:12:25.530 --> 00:12:25.540 align:start position:0% once this is a decided the next proposal 00:12:25.540 --> 00:12:27.630 align:start position:0% once this is a decided the next proposal would<00:12:25.870> propose<00:12:26.230> a<00:12:26.290> new<00:12:26.589> block<00:12:26.860> and<00:12:27.100> the<00:12:27.610> block 00:12:27.630 --> 00:12:27.640 align:start position:0% would propose a new block and the block 00:12:27.640 --> 00:12:32.880 align:start position:0% would propose a new block and the block generation<00:12:28.330> consensus<00:12:28.810> will<00:12:28.959> continue<00:12:29.410> a<00:12:31.890> PFD 00:12:32.880 --> 00:12:32.890 align:start position:0% generation consensus will continue a PFD 00:12:32.890 --> 00:12:36.510 align:start position:0% generation consensus will continue a PFD can<00:12:33.279> explicitly<00:12:34.089> detect<00:12:35.050> cup<00:12:35.260> of<00:12:35.520> malicious 00:12:36.510 --> 00:12:36.520 align:start position:0% can explicitly detect cup of malicious 00:12:36.520 --> 00:12:38.160 align:start position:0% can explicitly detect cup of malicious behaviors<00:12:37.060> to<00:12:37.690> name<00:12:37.839> a<00:12:37.870> few 00:12:38.160 --> 00:12:38.170 align:start position:0% behaviors to name a few 00:12:38.170 --> 00:12:40.650 align:start position:0% behaviors to name a few they<00:12:38.440> are<00:12:38.589> stove<00:12:39.010> editors<00:12:39.550> mixed<00:12:40.330> message 00:12:40.650 --> 00:12:40.660 align:start position:0% they are stove editors mixed message 00:12:40.660 --> 00:12:44.490 align:start position:0% they are stove editors mixed message codes<00:12:41.010> for<00:12:42.010> signatures<00:12:43.140> proposal<00:12:44.140> disguise 00:12:44.490 --> 00:12:44.500 align:start position:0% codes for signatures proposal disguise 00:12:44.500 --> 00:12:47.310 align:start position:0% codes for signatures proposal disguise round<00:12:45.370> changes<00:12:45.670> spamming<00:12:46.029> and<00:12:46.180> invalid<00:12:47.079> block 00:12:47.310 --> 00:12:47.320 align:start position:0% round changes spamming and invalid block 00:12:47.320 --> 00:12:49.310 align:start position:0% round changes spamming and invalid block proposal 00:12:49.310 --> 00:12:49.320 align:start position:0% proposal 00:12:49.320 --> 00:12:52.110 align:start position:0% proposal right<00:12:50.320> back<00:12:50.529> to<00:12:50.560> corner<00:12:50.950> a<00:12:50.980> little<00:12:51.190> bit<00:12:51.339> why 00:12:52.110 --> 00:12:52.120 align:start position:0% right back to corner a little bit why 00:12:52.120 --> 00:12:55.110 align:start position:0% right back to corner a little bit why the<00:12:52.180> MEP<00:12:52.839> corn<00:12:53.700> there<00:12:54.700> are<00:12:54.790> a<00:12:54.820> couple<00:12:54.970> of 00:12:55.110 --> 00:12:55.120 align:start position:0% the MEP corn there are a couple of 00:12:55.120 --> 00:12:57.870 align:start position:0% the MEP corn there are a couple of reasons<00:12:55.329> first<00:12:56.170> of<00:12:56.350> all<00:12:56.500> corn<00:12:57.130> is<00:12:57.279> compatible 00:12:57.870 --> 00:12:57.880 align:start position:0% reasons first of all corn is compatible 00:12:57.880 --> 00:13:01.050 align:start position:0% reasons first of all corn is compatible with<00:12:57.940> and<00:12:58.360> close<00:12:58.810> to<00:12:58.990> Papa<00:12:59.350> Experion<00:13:00.060> actually 00:13:01.050 --> 00:13:01.060 align:start position:0% with and close to Papa Experion actually 00:13:01.060 --> 00:13:04.440 align:start position:0% with and close to Papa Experion actually we<00:13:01.209> have<00:13:01.329> implemented<00:13:01.810> our<00:13:02.760> IBM<00:13:03.760> T<00:13:03.880> on<00:13:04.089> top<00:13:04.270> of 00:13:04.440 --> 00:13:04.450 align:start position:0% we have implemented our IBM T on top of 00:13:04.450 --> 00:13:07.380 align:start position:0% we have implemented our IBM T on top of possible<00:13:05.079> consensus<00:13:05.560> engine<00:13:06.120> so<00:13:07.120> we<00:13:07.270> have 00:13:07.380 --> 00:13:07.390 align:start position:0% possible consensus engine so we have 00:13:07.390 --> 00:13:09.540 align:start position:0% possible consensus engine so we have used<00:13:07.630> the<00:13:07.750> same<00:13:07.990> code<00:13:08.140> base<00:13:08.220> send<00:13:09.220> a<00:13:09.339> pull 00:13:09.540 --> 00:13:09.550 align:start position:0% used the same code base send a pull 00:13:09.550 --> 00:13:12.120 align:start position:0% used the same code base send a pull request<00:13:09.579> to<00:13:10.120> public<00:13:10.720> go<00:13:10.839> Assyrian<00:13:11.350> please 00:13:12.120 --> 00:13:12.130 align:start position:0% request to public go Assyrian please 00:13:12.130 --> 00:13:14.970 align:start position:0% request to public go Assyrian please check<00:13:12.370> out<00:13:12.520> the<00:13:12.640> IP<00:13:12.790> six<00:13:13.209> five<00:13:13.510> zero<00:13:13.540> again<00:13:14.410> the 00:13:14.970 --> 00:13:14.980 align:start position:0% check out the IP six five zero again the 00:13:14.980 --> 00:13:18.049 align:start position:0% check out the IP six five zero again the IP<00:13:15.130> 6<00:13:15.610> 5<00:13:15.880> 0<00:13:15.910> for<00:13:16.540> more<00:13:16.720> detail 00:13:18.049 --> 00:13:18.059 align:start position:0% IP 6 5 0 for more detail 00:13:18.059 --> 00:13:20.699 align:start position:0% IP 6 5 0 for more detail also<00:13:19.059> current<00:13:19.869> and<00:13:19.989> army<00:13:20.230> are<00:13:20.259> trying<00:13:20.589> to 00:13:20.699 --> 00:13:20.709 align:start position:0% also current and army are trying to 00:13:20.709 --> 00:13:22.889 align:start position:0% also current and army are trying to solve<00:13:20.889> the<00:13:21.129> same<00:13:21.249> problem<00:13:21.730> not<00:13:22.569> only<00:13:22.600> for 00:13:22.889 --> 00:13:22.899 align:start position:0% solve the same problem not only for 00:13:22.899 --> 00:13:24.900 align:start position:0% solve the same problem not only for banking<00:13:23.350> systems<00:13:23.799> but<00:13:24.309> also<00:13:24.369> under 00:13:24.900 --> 00:13:24.910 align:start position:0% banking systems but also under 00:13:24.910 --> 00:13:27.479 align:start position:0% banking systems but also under regulatory<00:13:25.319> environments<00:13:26.339> Kern<00:13:27.339> has 00:13:27.479 --> 00:13:27.489 align:start position:0% regulatory environments Kern has 00:13:27.489 --> 00:13:31.079 align:start position:0% regulatory environments Kern has supported<00:13:27.970> three<00:13:29.279> consensus<00:13:30.279> options<00:13:30.730> which 00:13:31.079 --> 00:13:31.089 align:start position:0% supported three consensus options which 00:13:31.089 --> 00:13:33.449 align:start position:0% supported three consensus options which are<00:13:31.239> really<00:13:31.420> useful<00:13:31.540> in<00:13:31.989> these<00:13:32.109> cases<00:13:32.459> they 00:13:33.449 --> 00:13:33.459 align:start position:0% are really useful in these cases they 00:13:33.459 --> 00:13:35.789 align:start position:0% are really useful in these cases they are<00:13:33.549> car<00:13:33.819> engine<00:13:34.149> revved<00:13:34.629> and<00:13:34.809> now<00:13:35.139> I<00:13:35.169> BFG<00:13:35.649> as 00:13:35.789 --> 00:13:35.799 align:start position:0% are car engine revved and now I BFG as 00:13:35.799 --> 00:13:39.269 align:start position:0% are car engine revved and now I BFG as well<00:13:36.329> that's<00:13:37.329> but<00:13:37.569> not<00:13:37.689> least<00:13:37.899> with<00:13:38.889> JP<00:13:39.249> Morgan 00:13:39.269 --> 00:13:39.279 align:start position:0% well that's but not least with JP Morgan 00:13:39.279 --> 00:13:41.669 align:start position:0% well that's but not least with JP Morgan back<00:13:39.730> in<00:13:39.910> Korin<00:13:40.329> it<00:13:40.660> builds<00:13:40.929> up<00:13:41.019> trust<00:13:41.350> while 00:13:41.669 --> 00:13:41.679 align:start position:0% back in Korin it builds up trust while 00:13:41.679 --> 00:13:44.789 align:start position:0% back in Korin it builds up trust while working<00:13:41.889> for<00:13:42.129> banking<00:13:42.429> systems<00:13:43.379> all<00:13:44.379> right<00:13:44.559> we 00:13:44.789 --> 00:13:44.799 align:start position:0% working for banking systems all right we 00:13:44.799 --> 00:13:46.499 align:start position:0% working for banking systems all right we have<00:13:44.889> escaped<00:13:45.220> a<00:13:45.369> lot<00:13:45.519> of<00:13:45.669> technical<00:13:46.149> details 00:13:46.499 --> 00:13:46.509 align:start position:0% have escaped a lot of technical details 00:13:46.509 --> 00:13:48.030 align:start position:0% have escaped a lot of technical details if<00:13:46.989> you<00:13:47.169> are<00:13:47.259> interested<00:13:47.649> in<00:13:47.769> learning<00:13:47.859> more 00:13:48.030 --> 00:13:48.040 align:start position:0% if you are interested in learning more 00:13:48.040 --> 00:13:50.549 align:start position:0% if you are interested in learning more please<00:13:48.339> come<00:13:48.970> to<00:13:49.059> us<00:13:49.209> all<00:13:49.749> thing<00:13:49.989> is<00:13:50.109> here<00:13:50.379> and 00:13:50.549 --> 00:13:50.559 align:start position:0% please come to us all thing is here and 00:13:50.559 --> 00:14:00.539 align:start position:0% please come to us all thing is here and we<00:13:50.679> are<00:13:50.799> way<00:13:50.919> I<00:13:50.949> mean<00:13:51.309> teachers<00:13:51.639> thank<00:13:52.299> you<00:13:59.549> so 00:14:00.539 --> 00:14:00.549 align:start position:0% we are way I mean teachers thank you so 00:14:00.549 --> 00:14:01.349 align:start position:0% we are way I mean teachers thank you so yeah 00:14:01.349 --> 00:14:01.359 align:start position:0% yeah 00:14:01.359 --> 00:14:03.659 align:start position:0% yeah assemble<00:14:01.869> now<00:14:01.899> is<00:14:02.290> available<00:14:02.919> in<00:14:03.160> quorum 00:14:03.659 --> 00:14:03.669 align:start position:0% assemble now is available in quorum 00:14:03.669 --> 00:14:05.549 align:start position:0% assemble now is available in quorum which<00:14:03.910> we<00:14:04.059> are<00:14:04.419> extremely<00:14:04.839> excited<00:14:05.049> about<00:14:05.230> it 00:14:05.549 --> 00:14:05.559 align:start position:0% which we are extremely excited about it 00:14:05.559 --> 00:14:07.019 align:start position:0% which we are extremely excited about it gives<00:14:05.709> us<00:14:05.859> that<00:14:05.889> all-important<00:14:06.639> Byzantine 00:14:07.019 --> 00:14:07.029 align:start position:0% gives us that all-important Byzantine 00:14:07.029 --> 00:14:08.970 align:start position:0% gives us that all-important Byzantine fault<00:14:07.239> tolerant<00:14:07.629> consensus<00:14:08.049> mechanism<00:14:08.589> has 00:14:08.970 --> 00:14:08.980 align:start position:0% fault tolerant consensus mechanism has 00:14:08.980 --> 00:14:10.530 align:start position:0% fault tolerant consensus mechanism has really<00:14:09.189> been<00:14:09.339> on<00:14:09.459> the<00:14:09.549> roadmap<00:14:09.730> since<00:14:10.179> day<00:14:10.329> one 00:14:10.530 --> 00:14:10.540 align:start position:0% really been on the roadmap since day one 00:14:10.540 --> 00:14:13.349 align:start position:0% really been on the roadmap since day one but<00:14:11.290> I<00:14:11.319> think<00:14:11.379> the<00:14:11.649> story<00:14:11.919> is<00:14:12.189> much<00:14:13.179> bigger 00:14:13.349 --> 00:14:13.359 align:start position:0% but I think the story is much bigger 00:14:13.359 --> 00:14:15.929 align:start position:0% but I think the story is much bigger than<00:14:13.540> just<00:14:13.739> consensus<00:14:14.739> yeah<00:14:14.949> so<00:14:15.249> if<00:14:15.699> we<00:14:15.819> look 00:14:15.929 --> 00:14:15.939 align:start position:0% than just consensus yeah so if we look 00:14:15.939 --> 00:14:17.699 align:start position:0% than just consensus yeah so if we look at<00:14:15.999> what's<00:14:16.179> happened<00:14:16.540> in<00:14:16.779> Coram<00:14:17.350> over<00:14:17.619> the 00:14:17.699 --> 00:14:17.709 align:start position:0% at what's happened in Coram over the 00:14:17.709 --> 00:14:20.249 align:start position:0% at what's happened in Coram over the last<00:14:17.829> year<00:14:18.279> we<00:14:18.850> really<00:14:19.089> have<00:14:19.209> this<00:14:19.329> nice 00:14:20.249 --> 00:14:20.259 align:start position:0% last year we really have this nice 00:14:20.259 --> 00:14:22.319 align:start position:0% last year we really have this nice collaborative<00:14:21.040> environment<00:14:21.579> that<00:14:21.730> is<00:14:21.879> has 00:14:22.319 --> 00:14:22.329 align:start position:0% collaborative environment that is has 00:14:22.329 --> 00:14:25.139 align:start position:0% collaborative environment that is has taken<00:14:22.480> place<00:14:22.749> so<00:14:23.259> the<00:14:24.160> Istanbul 00:14:25.139 --> 00:14:25.149 align:start position:0% taken place so the Istanbul 00:14:25.149 --> 00:14:27.059 align:start position:0% taken place so the Istanbul implementation<00:14:25.869> has<00:14:25.989> actually<00:14:26.379> resulted<00:14:26.589> in 00:14:27.059 --> 00:14:27.069 align:start position:0% implementation has actually resulted in 00:14:27.069 --> 00:14:29.850 align:start position:0% implementation has actually resulted in me<00:14:27.699> submitting<00:14:28.119> a<00:14:28.179> PR<00:14:28.509> back<00:14:28.779> to<00:14:28.989> get<00:14:29.230> to 00:14:29.850 --> 00:14:29.860 align:start position:0% me submitting a PR back to get to 00:14:29.860 --> 00:14:31.769 align:start position:0% me submitting a PR back to get to improve<00:14:30.189> the<00:14:30.309> pluggable<00:14:30.779> consensus 00:14:31.769 --> 00:14:31.779 align:start position:0% improve the pluggable consensus 00:14:31.779 --> 00:14:34.169 align:start position:0% improve the pluggable consensus interface<00:14:32.199> and<00:14:32.759> we've<00:14:33.759> also<00:14:33.910> partnered 00:14:34.169 --> 00:14:34.179 align:start position:0% interface and we've also partnered 00:14:34.179 --> 00:14:36.449 align:start position:0% interface and we've also partnered obviously<00:14:34.689> as<00:14:34.779> I<00:14:34.809> said<00:14:35.079> with<00:14:35.230> Z<00:14:35.379> cash<00:14:35.589> for<00:14:36.369> the 00:14:36.449 --> 00:14:36.459 align:start position:0% obviously as I said with Z cash for the 00:14:36.459 --> 00:14:38.519 align:start position:0% obviously as I said with Z cash for the first<00:14:36.699> full<00:14:37.689> zero<00:14:38.199> knowledge<00:14:38.379> proof 00:14:38.519 --> 00:14:38.529 align:start position:0% first full zero knowledge proof 00:14:38.529 --> 00:14:40.590 align:start position:0% first full zero knowledge proof simplement<00:14:39.160> ation<00:14:39.519> in<00:14:39.730> an<00:14:39.910> aetherium<00:14:40.269> client 00:14:40.590 --> 00:14:40.600 align:start position:0% simplement ation in an aetherium client 00:14:40.600 --> 00:14:43.079 align:start position:0% simplement ation in an aetherium client and<00:14:40.779> what<00:14:41.649> this<00:14:41.799> really<00:14:42.129> gives<00:14:42.279> is<00:14:42.579> a<00:14:42.819> really 00:14:43.079 --> 00:14:43.089 align:start position:0% and what this really gives is a really 00:14:43.089 --> 00:14:45.929 align:start position:0% and what this really gives is a really nice<00:14:43.239> reference<00:14:43.720> implementation<00:14:44.619> for<00:14:44.939> zero 00:14:45.929 --> 00:14:45.939 align:start position:0% nice reference implementation for zero 00:14:45.939 --> 00:14:47.579 align:start position:0% nice reference implementation for zero knowledge<00:14:46.059> proof<00:14:46.209> going<00:14:46.929> forward<00:14:47.319> within 00:14:47.579 --> 00:14:47.589 align:start position:0% knowledge proof going forward within 00:14:47.589 --> 00:14:50.220 align:start position:0% knowledge proof going forward within within<00:14:48.100> public<00:14:48.549> aetherium<00:14:48.970> we've<00:14:49.809> also 00:14:50.220 --> 00:14:50.230 align:start position:0% within public aetherium we've also 00:14:50.230 --> 00:14:52.199 align:start position:0% within public aetherium we've also collaborated<00:14:50.799> with<00:14:50.829> block<00:14:51.309> apps<00:14:51.489> who 00:14:52.199 --> 00:14:52.209 align:start position:0% collaborated with block apps who 00:14:52.209 --> 00:14:54.269 align:start position:0% collaborated with block apps who developed<00:14:52.689> a<00:14:52.869> tool<00:14:53.199> called<00:14:53.470> ëthe<00:14:53.829> pruner 00:14:54.269 --> 00:14:54.279 align:start position:0% developed a tool called ëthe pruner 00:14:54.279 --> 00:14:56.369 align:start position:0% developed a tool called ëthe pruner which<00:14:54.910> allows<00:14:55.209> us<00:14:55.449> to<00:14:55.660> archive<00:14:56.230> all 00:14:56.369 --> 00:14:56.379 align:start position:0% which allows us to archive all 00:14:56.379 --> 00:14:58.350 align:start position:0% which allows us to archive all historical<00:14:56.980> states<00:14:57.249> which<00:14:58.059> obviously 00:14:58.350 --> 00:14:58.360 align:start position:0% historical states which obviously 00:14:58.360 --> 00:15:00.960 align:start position:0% historical states which obviously reduces<00:14:58.869> blockchain<00:14:59.379> blurt<00:14:59.759> improves<00:15:00.759> the 00:15:00.960 --> 00:15:00.970 align:start position:0% reduces blockchain blurt improves the 00:15:00.970 --> 00:15:03.569 align:start position:0% reduces blockchain blurt improves the performance<00:15:01.149> of<00:15:01.629> the<00:15:01.869> of<00:15:02.139> the<00:15:02.230> network<00:15:02.559> and<00:15:02.799> as 00:15:03.569 --> 00:15:03.579 align:start position:0% performance of the of the network and as 00:15:03.579 --> 00:15:05.909 align:start position:0% performance of the of the network and as the<00:15:03.699> name<00:15:03.850> says<00:15:04.089> f<00:15:04.449> pruner<00:15:04.839> this<00:15:05.019> is<00:15:05.169> not<00:15:05.679> just 00:15:05.909 --> 00:15:05.919 align:start position:0% the name says f pruner this is not just 00:15:05.919 --> 00:15:07.590 align:start position:0% the name says f pruner this is not just something<00:15:06.069> that's<00:15:06.220> targeted<00:15:06.970> at<00:15:07.029> quorum<00:15:07.419> but 00:15:07.590 --> 00:15:07.600 align:start position:0% something that's targeted at quorum but 00:15:07.600 --> 00:15:09.329 align:start position:0% something that's targeted at quorum but also<00:15:07.749> something<00:15:08.049> as<00:15:08.259> targeted<00:15:08.739> and<00:15:08.949> used 00:15:09.329 --> 00:15:09.339 align:start position:0% also something as targeted and used 00:15:09.339 --> 00:15:11.850 align:start position:0% also something as targeted and used unusable<00:15:10.089> for<00:15:10.169> the<00:15:11.169> actual<00:15:11.589> main<00:15:11.709> line 00:15:11.850 --> 00:15:11.860 align:start position:0% unusable for the actual main line 00:15:11.860 --> 00:15:14.129 align:start position:0% unusable for the actual main line theorem<00:15:12.339> code<00:15:12.519> base<00:15:12.839> excuse<00:15:13.839> me 00:15:14.129 --> 00:15:14.139 align:start position:0% theorem code base excuse me 00:15:14.139 --> 00:15:16.799 align:start position:0% theorem code base excuse me and<00:15:14.230> then<00:15:14.559> finally<00:15:14.980> with<00:15:15.759> como<00:15:16.269> technologies 00:15:16.799 --> 00:15:16.809 align:start position:0% and then finally with como technologies 00:15:16.809 --> 00:15:19.619 align:start position:0% and then finally with como technologies who<00:15:17.109> developed<00:15:17.980> porosity<00:15:18.429> which<00:15:18.850> is<00:15:18.999> an<00:15:19.149> EVM 00:15:19.619 --> 00:15:19.629 align:start position:0% who developed porosity which is an EVM 00:15:19.629 --> 00:15:22.139 align:start position:0% who developed porosity which is an EVM decompiler<00:15:20.379> decompiling<00:15:21.220> by<00:15:21.429> coded<00:15:21.850> into 00:15:22.139 --> 00:15:22.149 align:start position:0% decompiler decompiling by coded into 00:15:22.149 --> 00:15:24.359 align:start position:0% decompiler decompiling by coded into solidity<00:15:22.539> contracts<00:15:23.169> that<00:15:23.679> helps<00:15:24.100> from<00:15:24.249> a 00:15:24.359 --> 00:15:24.369 align:start position:0% solidity contracts that helps from a 00:15:24.369 --> 00:15:26.220 align:start position:0% solidity contracts that helps from a quorum<00:15:24.639> perspective<00:15:25.089> to<00:15:25.329> identify 00:15:26.220 --> 00:15:26.230 align:start position:0% quorum perspective to identify 00:15:26.230 --> 00:15:28.679 align:start position:0% quorum perspective to identify vulnerabilities<00:15:26.699> in<00:15:27.699> smart<00:15:27.999> contracts<00:15:28.509> and 00:15:28.679 --> 00:15:28.689 align:start position:0% vulnerabilities in smart contracts and 00:15:28.689 --> 00:15:30.060 align:start position:0% vulnerabilities in smart contracts and of<00:15:29.110> course<00:15:29.350> given<00:15:29.829> that 00:15:30.060 --> 00:15:30.070 align:start position:0% of course given that 00:15:30.070 --> 00:15:31.470 align:start position:0% of course given that chorim<00:15:30.490> and<00:15:30.580> etherium<00:15:31.030> are<00:15:31.150> very<00:15:31.300> close 00:15:31.470 --> 00:15:31.480 align:start position:0% chorim and etherium are very close 00:15:31.480 --> 00:15:33.600 align:start position:0% chorim and etherium are very close together<00:15:31.690> it's<00:15:32.440> directly<00:15:32.800> usable<00:15:33.130> within 00:15:33.600 --> 00:15:33.610 align:start position:0% together it's directly usable within 00:15:33.610 --> 00:15:36.180 align:start position:0% together it's directly usable within public<00:15:34.210> aetherium<00:15:34.660> too<00:15:34.870> so<00:15:35.710> I<00:15:35.740> think<00:15:35.860> what<00:15:36.100> you 00:15:36.180 --> 00:15:36.190 align:start position:0% public aetherium too so I think what you 00:15:36.190 --> 00:15:39.350 align:start position:0% public aetherium too so I think what you have<00:15:36.400> is<00:15:36.610> this<00:15:36.790> in<00:15:37.420> a<00:15:37.510> really<00:15:37.750> nice<00:15:37.870> two-way 00:15:39.350 --> 00:15:39.360 align:start position:0% have is this in a really nice two-way 00:15:39.360 --> 00:15:41.460 align:start position:0% have is this in a really nice two-way movement<00:15:40.360> of<00:15:40.510> innovation<00:15:40.990> between<00:15:41.140> the 00:15:41.460 --> 00:15:41.470 align:start position:0% movement of innovation between the 00:15:41.470 --> 00:15:43.770 align:start position:0% movement of innovation between the public<00:15:41.770> if<00:15:42.070> they're<00:15:42.550> in<00:15:42.670> space<00:15:42.940> and<00:15:43.270> also<00:15:43.390> from 00:15:43.770 --> 00:15:43.780 align:start position:0% public if they're in space and also from 00:15:43.780 --> 00:15:46.410 align:start position:0% public if they're in space and also from the<00:15:43.960> permission<00:15:44.440> in<00:15:44.980> submission<00:15:45.880> environment 00:15:46.410 --> 00:15:46.420 align:start position:0% the permission in submission environment 00:15:46.420 --> 00:15:48.390 align:start position:0% the permission in submission environment back<00:15:46.570> to<00:15:46.750> public<00:15:46.990> aetherium<00:15:47.530> and<00:15:47.740> when<00:15:48.310> you 00:15:48.390 --> 00:15:48.400 align:start position:0% back to public aetherium and when you 00:15:48.400 --> 00:15:51.930 align:start position:0% back to public aetherium and when you couple<00:15:48.580> that<00:15:48.730> with<00:15:49.320> the<00:15:50.320> number<00:15:51.100> of<00:15:51.130> companies 00:15:51.930 --> 00:15:51.940 align:start position:0% couple that with the number of companies 00:15:51.940 --> 00:15:54.120 align:start position:0% couple that with the number of companies that<00:15:52.210> are<00:15:52.450> now<00:15:52.540> looking<00:15:52.750> at<00:15:52.990> chorim<00:15:53.350> building 00:15:54.120 --> 00:15:54.130 align:start position:0% that are now looking at chorim building 00:15:54.130 --> 00:15:55.950 align:start position:0% that are now looking at chorim building on<00:15:54.250> top<00:15:54.370> of<00:15:54.430> chorim<00:15:54.910> building<00:15:55.390> projects<00:15:55.810> and 00:15:55.950 --> 00:15:55.960 align:start position:0% on top of chorim building projects and 00:15:55.960 --> 00:15:59.010 align:start position:0% on top of chorim building projects and on<00:15:56.350> chorim<00:15:57.000> building<00:15:58.000> tools<00:15:58.270> around<00:15:58.450> chorim 00:15:59.010 --> 00:15:59.020 align:start position:0% on chorim building tools around chorim 00:15:59.020 --> 00:16:01.320 align:start position:0% on chorim building tools around chorim this<00:15:59.530> is<00:15:59.680> all<00:15:59.860> directly<00:16:00.490> relevant<00:16:01.000> and<00:16:01.180> useful 00:16:01.320 --> 00:16:01.330 align:start position:0% this is all directly relevant and useful 00:16:01.330 --> 00:16:04.110 align:start position:0% this is all directly relevant and useful to<00:16:01.990> public<00:16:02.500> aetherium<00:16:02.920> as<00:16:03.040> well<00:16:03.220> so<00:16:03.850> we<00:16:03.970> have 00:16:04.110 --> 00:16:04.120 align:start position:0% to public aetherium as well so we have 00:16:04.120 --> 00:16:06.480 align:start position:0% to public aetherium as well so we have an<00:16:04.270> increase<00:16:04.630> in<00:16:04.900> focus<00:16:05.590> on<00:16:05.770> etherium<00:16:06.190> we<00:16:06.340> have 00:16:06.480 --> 00:16:06.490 align:start position:0% an increase in focus on etherium we have 00:16:06.490 --> 00:16:08.100 align:start position:0% an increase in focus on etherium we have an<00:16:06.610> increase<00:16:06.940> in<00:16:07.090> acceptability<00:16:07.570> within 00:16:08.100 --> 00:16:08.110 align:start position:0% an increase in acceptability within 00:16:08.110 --> 00:16:10.440 align:start position:0% an increase in acceptability within enterprise<00:16:08.890> of<00:16:09.100> the<00:16:09.160> theorem<00:16:09.490> and<00:16:09.670> ultimately 00:16:10.440 --> 00:16:10.450 align:start position:0% enterprise of the theorem and ultimately 00:16:10.450 --> 00:16:11.490 align:start position:0% enterprise of the theorem and ultimately I<00:16:10.570> think<00:16:10.810> in<00:16:10.900> terms<00:16:11.110> of<00:16:11.230> what<00:16:11.350> we<00:16:11.470> are 00:16:11.490 --> 00:16:11.500 align:start position:0% I think in terms of what we are 00:16:11.500 --> 00:16:13.620 align:start position:0% I think in terms of what we are collectively<00:16:12.070> trying<00:16:12.370> to<00:16:12.490> do<00:16:12.640> that<00:16:13.330> can<00:16:13.480> only 00:16:13.620 --> 00:16:13.630 align:start position:0% collectively trying to do that can only 00:16:13.630 --> 00:16:16.170 align:start position:0% collectively trying to do that can only be<00:16:13.810> a<00:16:13.840> good<00:16:14.140> thing<00:16:14.200> so<00:16:15.130> that's<00:16:15.610> a<00:16:15.760> that's<00:16:16.060> our 00:16:16.170 --> 00:16:16.180 align:start position:0% be a good thing so that's a that's our 00:16:16.180 --> 00:16:17.340 align:start position:0% be a good thing so that's a that's our talk<00:16:16.390> today<00:16:16.540> thank<00:16:16.870> you<00:16:16.930> so<00:16:17.110> much<00:16:17.230> for 00:16:17.340 --> 00:16:17.350 align:start position:0% talk today thank you so much for 00:16:17.350 --> 00:16:18.990 align:start position:0% talk today thank you so much for listening<00:16:17.500> if<00:16:18.280> you<00:16:18.400> want<00:16:18.580> to<00:16:18.670> have<00:16:18.790> more 00:16:18.990 --> 00:16:19.000 align:start position:0% listening if you want to have more 00:16:19.000 --> 00:16:21.220 align:start position:0% listening if you want to have more information<00:16:19.710> go<00:16:20.710> to<00:16:20.740> these<00:16:20.890> places 00:16:21.220 --> 00:16:21.230 align:start position:0% information go to these places 00:16:21.230 --> 00:16:29.210 align:start position:0% information go to these places [Applause] 00:16:29.210 --> 00:16:29.220 align:start position:0% 00:16:29.220 --> 00:16:31.279 align:start position:0% you