WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:18.000 align:start position:0% [Music] 00:00:18.000 --> 00:00:18.010 align:start position:0% 00:00:18.010 --> 00:00:22.570 align:start position:0% hello<00:00:19.010> everyone<00:00:19.840> I'm<00:00:20.840> Jen<00:00:21.260> yeah<00:00:21.560> I'm<00:00:22.040> the<00:00:22.370> CEO 00:00:22.570 --> 00:00:22.580 align:start position:0% hello everyone I'm Jen yeah I'm the CEO 00:00:22.580 --> 00:00:25.660 align:start position:0% hello everyone I'm Jen yeah I'm the CEO of<00:00:22.760> crib<00:00:23.480> tape<00:00:23.720> which<00:00:24.110> is<00:00:24.140> a<00:00:24.500> blockchain<00:00:25.190> start 00:00:25.660 --> 00:00:25.670 align:start position:0% of crib tape which is a blockchain start 00:00:25.670 --> 00:00:29.440 align:start position:0% of crib tape which is a blockchain start of<00:00:25.850> Base<00:00:26.360> in<00:00:26.570> China<00:00:26.870> and<00:00:27.200> I<00:00:27.890> was<00:00:28.130> a<00:00:28.460> Syrian 00:00:29.440 --> 00:00:29.450 align:start position:0% of Base in China and I was a Syrian 00:00:29.450 --> 00:00:32.619 align:start position:0% of Base in China and I was a Syrian developer<00:00:30.200> in<00:00:30.500> the<00:00:31.490> italics<00:00:31.910> research<00:00:32.329> team 00:00:32.619 --> 00:00:32.629 align:start position:0% developer in the italics research team 00:00:32.629 --> 00:00:37.870 align:start position:0% developer in the italics research team and<00:00:33.200> now<00:00:33.350> I'm<00:00:34.150> fully<00:00:35.150> committed<00:00:35.480> to<00:00:35.810> our<00:00:36.880> our 00:00:37.870 --> 00:00:37.880 align:start position:0% and now I'm fully committed to our our 00:00:37.880 --> 00:00:40.390 align:start position:0% and now I'm fully committed to our our own<00:00:37.910> blood<00:00:38.450> and<00:00:38.720> product<00:00:39.170> name<00:00:39.440> Silla<00:00:39.829> which 00:00:40.390 --> 00:00:40.400 align:start position:0% own blood and product name Silla which 00:00:40.400 --> 00:00:43.270 align:start position:0% own blood and product name Silla which is<00:00:40.640> a<00:00:40.910> permission<00:00:41.840> blood<00:00:42.200> chain<00:00:42.470> and<00:00:42.770> today<00:00:43.190> I 00:00:43.270 --> 00:00:43.280 align:start position:0% is a permission blood chain and today I 00:00:43.280 --> 00:00:47.740 align:start position:0% is a permission blood chain and today I want<00:00:43.460> to<00:00:43.579> share<00:00:43.790> with<00:00:43.970> you<00:00:46.570> the<00:00:47.570> most 00:00:47.740 --> 00:00:47.750 align:start position:0% want to share with you the most 00:00:47.750 --> 00:00:50.080 align:start position:0% want to share with you the most important<00:00:48.380> design<00:00:48.500> the<00:00:49.489> most<00:00:49.670> important 00:00:50.080 --> 00:00:50.090 align:start position:0% important design the most important 00:00:50.090 --> 00:00:52.690 align:start position:0% important design the most important design<00:00:50.360> choice<00:00:50.630> of<00:00:50.899> ceará<00:00:51.140> and<00:00:51.380> why<00:00:52.190> it<00:00:52.250> makes 00:00:52.690 --> 00:00:52.700 align:start position:0% design choice of ceará and why it makes 00:00:52.700 --> 00:00:58.990 align:start position:0% design choice of ceará and why it makes it<00:00:53.030> a<00:00:53.059> unique<00:00:56.079> and<00:00:57.079> the<00:00:57.200> topic<00:00:57.500> is<00:00:58.000> scalable 00:00:58.990 --> 00:00:59.000 align:start position:0% it a unique and the topic is scalable 00:00:59.000 --> 00:01:02.380 align:start position:0% it a unique and the topic is scalable blockchain<00:00:59.600> for<00:00:59.780> enterprise<00:01:00.880> which<00:01:01.880> is<00:01:02.120> a 00:01:02.380 --> 00:01:02.390 align:start position:0% blockchain for enterprise which is a 00:01:02.390 --> 00:01:08.070 align:start position:0% blockchain for enterprise which is a scalable<00:01:03.020> solution<00:01:03.890> you<00:01:04.699> can<00:01:04.879> use<00:01:04.909> the<00:01:05.210> day 00:01:08.070 --> 00:01:08.080 align:start position:0% 00:01:08.080 --> 00:01:11.649 align:start position:0% with<00:01:09.080> the<00:01:09.290> advent<00:01:09.890> of<00:01:10.100> a<00:01:10.310> theorem<00:01:10.729> we<00:01:10.909> can<00:01:11.150> be 00:01:11.649 --> 00:01:11.659 align:start position:0% with the advent of a theorem we can be 00:01:11.659 --> 00:01:14.110 align:start position:0% with the advent of a theorem we can be decentralized<00:01:12.290> application<00:01:13.159> very<00:01:13.400> easily<00:01:13.700> on 00:01:14.110 --> 00:01:14.120 align:start position:0% decentralized application very easily on 00:01:14.120 --> 00:01:17.620 align:start position:0% decentralized application very easily on Owen<00:01:14.960> theorem<00:01:15.320> and<00:01:15.549> encrypted<00:01:16.549> we<00:01:16.729> provide 00:01:17.620 --> 00:01:17.630 align:start position:0% Owen theorem and encrypted we provide 00:01:17.630 --> 00:01:19.780 align:start position:0% Owen theorem and encrypted we provide all<00:01:17.840> kinds<00:01:17.869> of<00:01:18.260> consultancy<00:01:19.070> services<00:01:19.520> to<00:01:19.760> our 00:01:19.780 --> 00:01:19.790 align:start position:0% all kinds of consultancy services to our 00:01:19.790 --> 00:01:23.649 align:start position:0% all kinds of consultancy services to our customers<00:01:20.409> include<00:01:21.409> notary<00:01:22.340> crypto<00:01:23.119> assets 00:01:23.649 --> 00:01:23.659 align:start position:0% customers include notary crypto assets 00:01:23.659 --> 00:01:26.920 align:start position:0% customers include notary crypto assets to<00:01:24.080> settle<00:01:24.650> many<00:01:24.799> supply<00:01:25.220> chain<00:01:25.520> we<00:01:26.390> build<00:01:26.630> all 00:01:26.920 --> 00:01:26.930 align:start position:0% to settle many supply chain we build all 00:01:26.930 --> 00:01:29.500 align:start position:0% to settle many supply chain we build all kinds<00:01:26.990> of<00:01:27.560> prototypes<00:01:28.180> but<00:01:29.180> the<00:01:29.299> most 00:01:29.500 --> 00:01:29.510 align:start position:0% kinds of prototypes but the most 00:01:29.510 --> 00:01:32.230 align:start position:0% kinds of prototypes but the most question<00:01:30.110> we've<00:01:30.979> been<00:01:31.010> asked<00:01:31.700> by<00:01:32.060> our 00:01:32.230 --> 00:01:32.240 align:start position:0% question we've been asked by our 00:01:32.240 --> 00:01:37.000 align:start position:0% question we've been asked by our customers<00:01:32.900> is<00:01:34.390> is<00:01:35.390> the<00:01:35.659> solutions<00:01:36.200> you<00:01:36.710> built 00:01:37.000 --> 00:01:37.010 align:start position:0% customers is is the solutions you built 00:01:37.010 --> 00:01:44.050 align:start position:0% customers is is the solutions you built for<00:01:37.040> us<00:01:37.750> scale<00:01:41.290> what<00:01:42.290> if<00:01:42.439> what<00:01:43.130> if<00:01:43.159> the<00:01:43.580> what<00:01:44.030> if 00:01:44.050 --> 00:01:44.060 align:start position:0% for us scale what if what if the what if 00:01:44.060 --> 00:01:46.480 align:start position:0% for us scale what if what if the what if the<00:01:44.240> blockchain<00:01:44.990> application<00:01:45.680> becomes<00:01:45.830> super 00:01:46.480 --> 00:01:46.490 align:start position:0% the blockchain application becomes super 00:01:46.490 --> 00:01:48.789 align:start position:0% the blockchain application becomes super success<00:01:46.970> and<00:01:47.270> there<00:01:47.960> are<00:01:48.020> a<00:01:48.080> lot<00:01:48.170> of<00:01:48.320> our<00:01:48.619> users 00:01:48.789 --> 00:01:48.799 align:start position:0% success and there are a lot of our users 00:01:48.799 --> 00:01:52.810 align:start position:0% success and there are a lot of our users using<00:01:49.460> it<00:01:50.710> it's<00:01:51.710> the<00:01:51.920> solution<00:01:52.070> can<00:01:52.460> handle 00:01:52.810 --> 00:01:52.820 align:start position:0% using it it's the solution can handle 00:01:52.820 --> 00:01:59.020 align:start position:0% using it it's the solution can handle that<00:01:53.630> much<00:01:54.250> users<00:01:55.250> right<00:01:56.000> but<00:01:56.600> all<00:01:57.009> of<00:01:58.009> not<00:01:58.220> all 00:01:59.020 --> 00:01:59.030 align:start position:0% that much users right but all of not all 00:01:59.030 --> 00:02:03.130 align:start position:0% that much users right but all of not all of<00:01:59.450> us<00:01:59.750> know<00:02:01.299> platin<00:02:02.299> has<00:02:02.689> its<00:02:02.960> own 00:02:03.130 --> 00:02:03.140 align:start position:0% of us know platin has its own 00:02:03.140 --> 00:02:06.880 align:start position:0% of us know platin has its own scalability<00:02:03.939> problem<00:02:04.990> because<00:02:05.990> in<00:02:06.560> blood 00:02:06.880 --> 00:02:06.890 align:start position:0% scalability problem because in blood 00:02:06.890 --> 00:02:09.460 align:start position:0% scalability problem because in blood sure<00:02:07.100> we<00:02:07.250> need<00:02:07.430> to<00:02:07.610> replicate<00:02:08.149> or<00:02:08.360> we<00:02:08.959> need<00:02:09.349> to 00:02:09.460 --> 00:02:09.470 align:start position:0% sure we need to replicate or we need to 00:02:09.470 --> 00:02:13.270 align:start position:0% sure we need to replicate or we need to replicate<00:02:09.709> the<00:02:10.190> transactions<00:02:10.940> as<00:02:12.280> many 00:02:13.270 --> 00:02:13.280 align:start position:0% replicate the transactions as many 00:02:13.280 --> 00:02:14.570 align:start position:0% replicate the transactions as many copies 00:02:14.570 --> 00:02:14.580 align:start position:0% copies 00:02:14.580 --> 00:02:18.590 align:start position:0% copies the<00:02:14.820> nose<00:02:15.060> in<00:02:15.330> the<00:02:15.420> network<00:02:15.840> and<00:02:17.600> broadcaster 00:02:18.590 --> 00:02:18.600 align:start position:0% the nose in the network and broadcaster 00:02:18.600 --> 00:02:20.300 align:start position:0% the nose in the network and broadcaster replicates<00:02:19.320> to<00:02:19.560> ordinals 00:02:20.300 --> 00:02:20.310 align:start position:0% replicates to ordinals 00:02:20.310 --> 00:02:23.000 align:start position:0% replicates to ordinals and<00:02:20.490> ordinals<00:02:21.090> need<00:02:21.570> to<00:02:21.750> process<00:02:22.380> the<00:02:22.770> same 00:02:23.000 --> 00:02:23.010 align:start position:0% and ordinals need to process the same 00:02:23.010 --> 00:02:25.370 align:start position:0% and ordinals need to process the same task<00:02:23.310> again<00:02:23.850> again<00:02:24.240> and<00:02:24.270> again<00:02:24.690> and<00:02:24.870> then 00:02:25.370 --> 00:02:25.380 align:start position:0% task again again and again and then 00:02:25.380 --> 00:02:28.250 align:start position:0% task again again and again and then votes<00:02:25.620> so<00:02:26.490> no<00:02:26.670> matter<00:02:26.910> how<00:02:27.240> many<00:02:27.450> notes<00:02:27.780> in<00:02:28.110> the 00:02:28.250 --> 00:02:28.260 align:start position:0% votes so no matter how many notes in the 00:02:28.260 --> 00:02:31.970 align:start position:0% votes so no matter how many notes in the network<00:02:28.650> you<00:02:29.900> the<00:02:30.900> whole<00:02:31.110> the<00:02:31.620> whole<00:02:31.770> network 00:02:31.970 --> 00:02:31.980 align:start position:0% network you the whole the whole network 00:02:31.980 --> 00:02:34.250 align:start position:0% network you the whole the whole network that<00:02:32.520> the<00:02:33.120> throughput<00:02:33.390> of<00:02:33.660> the<00:02:33.900> whole<00:02:34.110> network 00:02:34.250 --> 00:02:34.260 align:start position:0% that the throughput of the whole network 00:02:34.260 --> 00:02:38.960 align:start position:0% that the throughput of the whole network is<00:02:34.650> the<00:02:34.830> same<00:02:35.040> as<00:02:35.280> a<00:02:35.520> single<00:02:36.330> note<00:02:37.460> you<00:02:38.460> can<00:02:38.730> you 00:02:38.960 --> 00:02:38.970 align:start position:0% is the same as a single note you can you 00:02:38.970 --> 00:02:42.580 align:start position:0% is the same as a single note you can you can<00:02:39.180> increase<00:02:39.600> the<00:02:39.930> network<00:02:40.620> throughput<00:02:41.220> or 00:02:42.580 --> 00:02:42.590 align:start position:0% can increase the network throughput or 00:02:42.590 --> 00:02:47.980 align:start position:0% can increase the network throughput or by<00:02:43.590> simply<00:02:44.300> adding<00:02:45.300> notes<00:02:46.400> into<00:02:47.400> the<00:02:47.550> network 00:02:47.980 --> 00:02:47.990 align:start position:0% by simply adding notes into the network 00:02:47.990 --> 00:02:52.400 align:start position:0% by simply adding notes into the network so<00:02:48.990> how<00:02:49.140> do<00:02:49.200> we<00:02:49.440> solve<00:02:50.010> the<00:02:50.190> problem<00:02:51.410> there 00:02:52.400 --> 00:02:52.410 align:start position:0% so how do we solve the problem there 00:02:52.410 --> 00:02:56.090 align:start position:0% so how do we solve the problem there there<00:02:53.100> are<00:02:53.250> actually<00:02:53.730> two<00:02:54.020> solutions<00:02:55.100> the 00:02:56.090 --> 00:02:56.100 align:start position:0% there are actually two solutions the 00:02:56.100 --> 00:02:59.590 align:start position:0% there are actually two solutions the hard<00:02:56.400> way<00:02:56.610> is<00:02:56.910> what<00:02:57.360> a<00:02:57.660> theorem<00:02:58.410> of<00:02:58.590> italic<00:02:59.010> is 00:02:59.590 --> 00:02:59.600 align:start position:0% hard way is what a theorem of italic is 00:02:59.600 --> 00:03:05.530 align:start position:0% hard way is what a theorem of italic is doing<00:03:00.600> now<00:03:00.780> is<00:03:00.920> scale<00:03:01.920> out<00:03:02.160> by<00:03:03.000> sharding<00:03:03.650> right 00:03:05.530 --> 00:03:05.540 align:start position:0% doing now is scale out by sharding right 00:03:05.540 --> 00:03:09.950 align:start position:0% doing now is scale out by sharding right what<00:03:06.540> if<00:03:06.710> what<00:03:07.710> if<00:03:07.860> we<00:03:08.190> don't<00:03:08.490> replicate<00:03:08.960> each 00:03:09.950 --> 00:03:09.960 align:start position:0% what if what if we don't replicate each 00:03:09.960 --> 00:03:12.410 align:start position:0% what if what if we don't replicate each transaction<00:03:10.710> that<00:03:11.130> many<00:03:11.430> time<00:03:11.760> what<00:03:12.030> if<00:03:12.180> we 00:03:12.410 --> 00:03:12.420 align:start position:0% transaction that many time what if we 00:03:12.420 --> 00:03:15.110 align:start position:0% transaction that many time what if we split<00:03:13.170> transaction<00:03:13.920> into<00:03:14.040> groups<00:03:14.460> and<00:03:14.700> we 00:03:15.110 --> 00:03:15.120 align:start position:0% split transaction into groups and we 00:03:15.120 --> 00:03:18.650 align:start position:0% split transaction into groups and we also<00:03:15.330> split<00:03:15.840> nodes<00:03:16.710> into<00:03:17.100> groups<00:03:17.550> and<00:03:17.760> each 00:03:18.650 --> 00:03:18.660 align:start position:0% also split nodes into groups and each 00:03:18.660 --> 00:03:21.890 align:start position:0% also split nodes into groups and each group<00:03:18.720> of<00:03:19.410> nodes<00:03:19.760> only<00:03:20.760> need<00:03:20.940> to<00:03:21.090> process<00:03:21.570> a 00:03:21.890 --> 00:03:21.900 align:start position:0% group of nodes only need to process a 00:03:21.900 --> 00:03:24.800 align:start position:0% group of nodes only need to process a subgroup<00:03:22.890> of<00:03:23.160> transactions<00:03:23.850> and<00:03:24.360> each<00:03:24.570> group 00:03:24.800 --> 00:03:24.810 align:start position:0% subgroup of transactions and each group 00:03:24.810 --> 00:03:27.590 align:start position:0% subgroup of transactions and each group of<00:03:25.110> nodes<00:03:25.470> only<00:03:25.709> need<00:03:26.040> to<00:03:26.190> maintain<00:03:26.970> a<00:03:27.239> sub 00:03:27.590 --> 00:03:27.600 align:start position:0% of nodes only need to maintain a sub 00:03:27.600 --> 00:03:31.610 align:start position:0% of nodes only need to maintain a sub state<00:03:27.870> of<00:03:28.050> the<00:03:28.200> blockchain<00:03:30.050> that's<00:03:31.050> that 00:03:31.610 --> 00:03:31.620 align:start position:0% state of the blockchain that's that 00:03:31.620 --> 00:03:33.740 align:start position:0% state of the blockchain that's that that's<00:03:32.100> what<00:03:32.340> shot<00:03:32.610> in<00:03:32.760> doing<00:03:33.060> but<00:03:33.300> shutting 00:03:33.740 --> 00:03:33.750 align:start position:0% that's what shot in doing but shutting 00:03:33.750 --> 00:03:38.150 align:start position:0% that's what shot in doing but shutting is<00:03:33.930> hard<00:03:34.700> if<00:03:35.700> you<00:03:35.970> if<00:03:36.360> you<00:03:36.720> have<00:03:36.959> if<00:03:37.680> you<00:03:37.830> listen 00:03:38.150 --> 00:03:38.160 align:start position:0% is hard if you if you have if you listen 00:03:38.160 --> 00:03:41.810 align:start position:0% is hard if you if you have if you listen to<00:03:38.540> metallics<00:03:39.540> talked<00:03:40.530> yesterday<00:03:40.920> you<00:03:41.760> know 00:03:41.810 --> 00:03:41.820 align:start position:0% to metallics talked yesterday you know 00:03:41.820 --> 00:03:46.220 align:start position:0% to metallics talked yesterday you know there<00:03:42.209> is<00:03:42.390> a<00:03:42.860> Shalamar<00:03:43.860> in<00:03:44.070> in<00:03:44.459> in<00:03:45.270> the<00:03:45.450> sky<00:03:45.750> in 00:03:46.220 --> 00:03:46.230 align:start position:0% there is a Shalamar in in in the sky in 00:03:46.230 --> 00:03:48.800 align:start position:0% there is a Shalamar in in in the sky in a<00:03:46.410> scalability<00:03:46.770> problem<00:03:47.580> you<00:03:47.940> can<00:03:48.209> you<00:03:48.570> can 00:03:48.800 --> 00:03:48.810 align:start position:0% a scalability problem you can you can 00:03:48.810 --> 00:03:52.670 align:start position:0% a scalability problem you can you can reach<00:03:50.450> you<00:03:51.450> can<00:03:51.660> reach<00:03:51.870> decentralization 00:03:52.670 --> 00:03:52.680 align:start position:0% reach you can reach decentralization 00:03:52.680 --> 00:03:54.920 align:start position:0% reach you can reach decentralization scalability<00:03:53.489> and<00:03:53.880> security<00:03:54.450> at<00:03:54.630> the<00:03:54.720> same 00:03:54.920 --> 00:03:54.930 align:start position:0% scalability and security at the same 00:03:54.930 --> 00:03:59.740 align:start position:0% scalability and security at the same time<00:03:55.200> so<00:03:55.739> in<00:03:56.640> ensuring<00:03:57.510> the<00:03:57.660> most<00:03:58.070> hard<00:03:59.070> part 00:03:59.740 --> 00:03:59.750 align:start position:0% time so in ensuring the most hard part 00:03:59.750 --> 00:04:04.370 align:start position:0% time so in ensuring the most hard part is<00:04:00.750> security<00:04:01.590> how<00:04:02.370> can<00:04:02.610> you<00:04:02.760> do<00:04:03.510> it<00:04:03.540> in<00:04:03.989> a<00:04:04.140> safe 00:04:04.370 --> 00:04:04.380 align:start position:0% is security how can you do it in a safe 00:04:04.380 --> 00:04:08.540 align:start position:0% is security how can you do it in a safe way<00:04:04.440> so<00:04:05.420> it's<00:04:06.420> very<00:04:06.630> hard<00:04:06.930> and<00:04:07.230> it's<00:04:08.220> theorem 00:04:08.540 --> 00:04:08.550 align:start position:0% way so it's very hard and it's theorem 00:04:08.550 --> 00:04:10.610 align:start position:0% way so it's very hard and it's theorem team<00:04:08.730> is<00:04:08.880> working<00:04:09.090> hard<00:04:09.270> on<00:04:09.570> this<00:04:09.780> and<00:04:10.050> maybe 00:04:10.610 --> 00:04:10.620 align:start position:0% team is working hard on this and maybe 00:04:10.620 --> 00:04:16.699 align:start position:0% team is working hard on this and maybe we<00:04:10.920> and<00:04:11.900> we<00:04:12.900> don't<00:04:13.140> have<00:04:13.290> it<00:04:13.470> today<00:04:15.530> the<00:04:16.530> other 00:04:16.699 --> 00:04:16.709 align:start position:0% we and we don't have it today the other 00:04:16.709 --> 00:04:21.289 align:start position:0% we and we don't have it today the other way<00:04:17.010> or<00:04:17.280> the<00:04:17.840> easier<00:04:18.840> way<00:04:19.049> is<00:04:19.320> scale-up<00:04:20.299> right 00:04:21.289 --> 00:04:21.299 align:start position:0% way or the easier way is scale-up right 00:04:21.299 --> 00:04:25.310 align:start position:0% way or the easier way is scale-up right if<00:04:21.780> the<00:04:22.049> whole<00:04:22.610> if<00:04:23.610> the<00:04:24.419> spirit<00:04:24.840> of<00:04:24.990> the<00:04:25.140> whole 00:04:25.310 --> 00:04:25.320 align:start position:0% if the whole if the spirit of the whole 00:04:25.320 --> 00:04:26.660 align:start position:0% if the whole if the spirit of the whole network 00:04:26.660 --> 00:04:26.670 align:start position:0% network 00:04:26.670 --> 00:04:30.560 align:start position:0% network is<00:04:26.760> the<00:04:27.030> same<00:04:27.360> as<00:04:27.540> a<00:04:27.960> single<00:04:28.920> node<00:04:29.340> in<00:04:29.610> the 00:04:30.560 --> 00:04:30.570 align:start position:0% is the same as a single node in the 00:04:30.570 --> 00:04:33.290 align:start position:0% is the same as a single node in the network<00:04:30.740> what<00:04:31.740> if<00:04:31.920> we<00:04:32.160> just<00:04:32.190> upgrade<00:04:32.940> a<00:04:32.970> node 00:04:33.290 --> 00:04:33.300 align:start position:0% network what if we just upgrade a node 00:04:33.300 --> 00:04:36.740 align:start position:0% network what if we just upgrade a node in<00:04:33.540> the<00:04:33.570> network<00:04:34.400> we<00:04:35.400> can<00:04:35.430> use<00:04:35.790> a<00:04:36.000> workstation 00:04:36.740 --> 00:04:36.750 align:start position:0% in the network we can use a workstation 00:04:36.750 --> 00:04:40.850 align:start position:0% in the network we can use a workstation even<00:04:37.560> mainframe<00:04:38.100> instead<00:04:39.060> of<00:04:39.270> a<00:04:39.450> laptop<00:04:39.860> to 00:04:40.850 --> 00:04:40.860 align:start position:0% even mainframe instead of a laptop to 00:04:40.860 --> 00:04:44.450 align:start position:0% even mainframe instead of a laptop to run<00:04:41.070> a<00:04:41.100> node<00:04:41.840> then<00:04:42.840> the<00:04:43.050> the<00:04:43.650> through<00:04:44.100> book<00:04:44.250> of 00:04:44.450 --> 00:04:44.460 align:start position:0% run a node then the the through book of 00:04:44.460 --> 00:04:46.600 align:start position:0% run a node then the the through book of the<00:04:44.700> whole<00:04:45.390> system<00:04:45.570> will<00:04:45.930> naturally<00:04:46.170> increase 00:04:46.600 --> 00:04:46.610 align:start position:0% the whole system will naturally increase 00:04:46.610 --> 00:04:53.090 align:start position:0% the whole system will naturally increase right<00:04:49.820> that's<00:04:50.820> the<00:04:51.000> solution<00:04:51.860> promoted<00:04:52.860> by 00:04:53.090 --> 00:04:53.100 align:start position:0% right that's the solution promoted by 00:04:53.100 --> 00:04:57.910 align:start position:0% right that's the solution promoted by some<00:04:54.030> big<00:04:54.330> names<00:04:54.570> in<00:04:54.870> this<00:04:55.080> industry<00:04:56.330> if<00:04:57.330> it's 00:04:57.910 --> 00:04:57.920 align:start position:0% some big names in this industry if it's 00:04:57.920 --> 00:05:01.100 align:start position:0% some big names in this industry if it's so<00:04:58.920> good<00:04:59.100> why<00:04:59.160> why<00:04:59.910> don't<00:05:00.150> I<00:05:00.270> serum<00:05:00.600> just<00:05:00.840> use 00:05:01.100 --> 00:05:01.110 align:start position:0% so good why why don't I serum just use 00:05:01.110 --> 00:05:08.150 align:start position:0% so good why why don't I serum just use this<00:05:01.650> solution<00:05:05.930> the<00:05:06.930> problems<00:05:07.470> of<00:05:07.650> scale<00:05:07.830> of 00:05:08.150 --> 00:05:08.160 align:start position:0% this solution the problems of scale of 00:05:08.160 --> 00:05:13.940 align:start position:0% this solution the problems of scale of solution<00:05:08.670> is<00:05:08.900> obvious<00:05:11.870> if<00:05:12.870> you<00:05:13.110> if<00:05:13.560> you<00:05:13.740> want 00:05:13.940 --> 00:05:13.950 align:start position:0% solution is obvious if you if you want 00:05:13.950 --> 00:05:17.170 align:start position:0% solution is obvious if you if you want to<00:05:14.040> build<00:05:14.280> a<00:05:14.510> very<00:05:15.510> decentralized<00:05:15.930> network 00:05:17.170 --> 00:05:17.180 align:start position:0% to build a very decentralized network 00:05:17.180 --> 00:05:21.440 align:start position:0% to build a very decentralized network you<00:05:18.180> have<00:05:18.390> to<00:05:19.280> make<00:05:20.280> the<00:05:20.460> cost<00:05:20.760> of<00:05:21.000> rannian 00:05:21.440 --> 00:05:21.450 align:start position:0% you have to make the cost of rannian 00:05:21.450 --> 00:05:25.790 align:start position:0% you have to make the cost of rannian node<00:05:21.630> very<00:05:21.960> low<00:05:22.490> if<00:05:23.490> you<00:05:23.730> if<00:05:24.450> it<00:05:24.720> if<00:05:25.290> you<00:05:25.410> need<00:05:25.620> a 00:05:25.790 --> 00:05:25.800 align:start position:0% node very low if you if it if you need a 00:05:25.800 --> 00:05:30.320 align:start position:0% node very low if you if it if you need a mainframe<00:05:26.280> to<00:05:26.880> run<00:05:27.060> a<00:05:27.090> full<00:05:27.450> node<00:05:27.660> a<00:05:29.330> any 00:05:30.320 --> 00:05:30.330 align:start position:0% mainframe to run a full node a any 00:05:30.330 --> 00:05:33.340 align:start position:0% mainframe to run a full node a any individual<00:05:31.050> cannot<00:05:31.500> afford<00:05:31.860> that<00:05:32.040> cost<00:05:32.400> and 00:05:33.340 --> 00:05:33.350 align:start position:0% individual cannot afford that cost and 00:05:33.350 --> 00:05:36.040 align:start position:0% individual cannot afford that cost and you<00:05:34.350> mean<00:05:34.560> you<00:05:34.860> may<00:05:35.010> also<00:05:35.190> need<00:05:35.520> very<00:05:35.910> good 00:05:36.040 --> 00:05:36.050 align:start position:0% you mean you may also need very good 00:05:36.050 --> 00:05:39.710 align:start position:0% you mean you may also need very good network<00:05:37.050> condition<00:05:38.150> for<00:05:39.150> that<00:05:39.300> for<00:05:39.540> node 00:05:39.710 --> 00:05:39.720 align:start position:0% network condition for that for node 00:05:39.720 --> 00:05:41.990 align:start position:0% network condition for that for node right<00:05:40.080> so<00:05:40.320> the<00:05:40.440> cost<00:05:40.650> is<00:05:40.770> very<00:05:40.830> high<00:05:41.340> for<00:05:41.370> scale 00:05:41.990 --> 00:05:42.000 align:start position:0% right so the cost is very high for scale 00:05:42.000 --> 00:05:49.220 align:start position:0% right so the cost is very high for scale for<00:05:42.780> for<00:05:43.620> a<00:05:46.130> mint<00:05:47.130> mainframe<00:05:48.000> node<00:05:48.270> and<00:05:48.600> the 00:05:49.220 --> 00:05:49.230 align:start position:0% for for a mint mainframe node and the 00:05:49.230 --> 00:05:52.670 align:start position:0% for for a mint mainframe node and the other<00:05:49.460> problem<00:05:50.460> is<00:05:50.550> centralization<00:05:51.450> if<00:05:52.140> the 00:05:52.670 --> 00:05:52.680 align:start position:0% other problem is centralization if the 00:05:52.680 --> 00:05:54.830 align:start position:0% other problem is centralization if the if<00:05:52.980> the<00:05:53.220> cost<00:05:53.460> is<00:05:53.610> so<00:05:53.880> high<00:05:53.910> then<00:05:54.540> any 00:05:54.830 --> 00:05:54.840 align:start position:0% if the cost is so high then any 00:05:54.840 --> 00:05:57.590 align:start position:0% if the cost is so high then any individual<00:05:55.500> cannot<00:05:55.770> afford<00:05:56.160> it<00:05:56.340> then<00:05:57.120> only 00:05:57.590 --> 00:05:57.600 align:start position:0% individual cannot afford it then only 00:05:57.600 --> 00:06:02.690 align:start position:0% individual cannot afford it then only people<00:05:59.570> with<00:06:00.570> a<00:06:01.050> lot<00:06:01.410> of<00:06:01.440> money<00:06:01.770> can<00:06:02.040> run<00:06:02.250> a<00:06:02.400> 4 00:06:02.690 --> 00:06:02.700 align:start position:0% people with a lot of money can run a 4 00:06:02.700 --> 00:06:05.600 align:start position:0% people with a lot of money can run a 4 node<00:06:02.880> in<00:06:03.030> the<00:06:03.150> network<00:06:03.500> so<00:06:04.500> the<00:06:05.130> solution<00:06:05.550> is 00:06:05.600 --> 00:06:05.610 align:start position:0% node in the network so the solution is 00:06:05.610 --> 00:06:11.240 align:start position:0% node in the network so the solution is not<00:06:05.880> suitable<00:06:06.420> for<00:06:06.480> a<00:06:06.990> public<00:06:07.860> chain<00:06:08.630> but<00:06:10.250> for 00:06:11.240 --> 00:06:11.250 align:start position:0% not suitable for a public chain but for 00:06:11.250 --> 00:06:13.070 align:start position:0% not suitable for a public chain but for for<00:06:11.640> crypt<00:06:11.850> tape<00:06:12.030> or<00:06:12.240> for<00:06:12.660> a<00:06:12.690> permission 00:06:13.070 --> 00:06:13.080 align:start position:0% for crypt tape or for a permission 00:06:13.080 --> 00:06:17.230 align:start position:0% for crypt tape or for a permission blockchain<00:06:15.110> the<00:06:16.110> context<00:06:16.590> is<00:06:16.770> different 00:06:17.230 --> 00:06:17.240 align:start position:0% blockchain the context is different 00:06:17.240 --> 00:06:22.430 align:start position:0% blockchain the context is different right<00:06:18.530> the<00:06:19.530> users<00:06:20.340> in<00:06:20.670> the<00:06:20.700> network<00:06:21.480> or 00:06:22.430 --> 00:06:22.440 align:start position:0% right the users in the network or 00:06:22.440 --> 00:06:25.520 align:start position:0% right the users in the network or enterprises<00:06:23.330> they<00:06:24.330> they<00:06:24.750> can<00:06:24.960> afford<00:06:25.350> the 00:06:25.520 --> 00:06:25.530 align:start position:0% enterprises they they can afford the 00:06:25.530 --> 00:06:31.160 align:start position:0% enterprises they they can afford the cost<00:06:25.770> and<00:06:27.740> information<00:06:28.740> blockchain<00:06:29.310> we<00:06:30.300> can 00:06:31.160 --> 00:06:31.170 align:start position:0% cost and information blockchain we can 00:06:31.170 --> 00:06:36.380 align:start position:0% cost and information blockchain we can set<00:06:31.470> a<00:06:31.500> barrier<00:06:32.100> for<00:06:32.790> for<00:06:33.570> enter<00:06:33.870> so<00:06:34.470> if<00:06:34.980> you<00:06:35.390> if 00:06:36.380 --> 00:06:36.390 align:start position:0% set a barrier for for enter so if you if 00:06:36.390 --> 00:06:39.520 align:start position:0% set a barrier for for enter so if you if you<00:06:36.570> want<00:06:36.780> to<00:06:36.930> join<00:06:37.200> to<00:06:37.800> be<00:06:38.010> a<00:06:38.190> validation 00:06:39.520 --> 00:06:39.530 align:start position:0% you want to join to be a validation 00:06:39.530 --> 00:06:43.270 align:start position:0% you want to join to be a validation we<00:06:39.980> can<00:06:40.160> ask<00:06:40.430> you<00:06:40.700> to<00:06:41.120> buy<00:06:41.870> some<00:06:42.740> minimum 00:06:43.270 --> 00:06:43.280 align:start position:0% we can ask you to buy some minimum 00:06:43.280 --> 00:06:48.310 align:start position:0% we can ask you to buy some minimum hardware<00:06:43.610> to<00:06:44.480> become<00:06:44.840> a<00:06:45.340> validation<00:06:46.340> node<00:06:47.320> so 00:06:48.310 --> 00:06:48.320 align:start position:0% hardware to become a validation node so 00:06:48.320 --> 00:06:54.400 align:start position:0% hardware to become a validation node so scale-up<00:06:48.830> solution<00:06:52.720> can<00:06:53.720> be<00:06:53.870> used<00:06:54.110> in 00:06:54.400 --> 00:06:54.410 align:start position:0% scale-up solution can be used in 00:06:54.410 --> 00:07:01.210 align:start position:0% scale-up solution can be used in permission<00:06:55.250> blockchain<00:06:57.160> and<00:06:59.320> we<00:07:00.320> have<00:07:00.530> a<00:07:00.740> even 00:07:01.210 --> 00:07:01.220 align:start position:0% permission blockchain and we have a even 00:07:01.220 --> 00:07:04.870 align:start position:0% permission blockchain and we have a even better<00:07:01.370> way<00:07:01.700> to<00:07:01.760> do<00:07:02.030> that<00:07:02.680> how<00:07:03.680> we<00:07:04.490> don't<00:07:04.700> need 00:07:04.870 --> 00:07:04.880 align:start position:0% better way to do that how we don't need 00:07:04.880 --> 00:07:09.990 align:start position:0% better way to do that how we don't need a<00:07:05.060> mainframe<00:07:05.530> that's<00:07:06.530> not<00:07:06.740> the<00:07:07.120> way<00:07:08.120> today<00:07:08.480> we 00:07:09.990 --> 00:07:10.000 align:start position:0% a mainframe that's not the way today we 00:07:10.000 --> 00:07:13.210 align:start position:0% a mainframe that's not the way today we we<00:07:11.000> can<00:07:11.180> use<00:07:11.420> the<00:07:12.080> same<00:07:12.350> technique<00:07:12.800> used<00:07:13.070> by 00:07:13.210 --> 00:07:13.220 align:start position:0% we can use the same technique used by 00:07:13.220 --> 00:07:17.280 align:start position:0% we can use the same technique used by all<00:07:13.730> those<00:07:14.090> internet<00:07:14.570> companies<00:07:15.610> so<00:07:16.610> insider' 00:07:17.280 --> 00:07:17.290 align:start position:0% all those internet companies so insider' 00:07:17.290 --> 00:07:20.830 align:start position:0% all those internet companies so insider' will<00:07:18.290> redesign<00:07:18.680> the<00:07:19.100> architecture<00:07:19.820> of<00:07:20.030> a<00:07:20.540> full 00:07:20.830 --> 00:07:20.840 align:start position:0% will redesign the architecture of a full 00:07:20.840 --> 00:07:25.890 align:start position:0% will redesign the architecture of a full node<00:07:21.080> to<00:07:21.710> use<00:07:21.890> micro<00:07:22.400> services<00:07:23.860> we<00:07:24.860> break<00:07:25.190> the 00:07:25.890 --> 00:07:25.900 align:start position:0% node to use micro services we break the 00:07:25.900 --> 00:07:29.910 align:start position:0% node to use micro services we break the functionalities<00:07:26.900> of<00:07:26.930> a<00:07:27.410> four<00:07:27.680> node<00:07:27.940> into<00:07:28.940> many 00:07:29.910 --> 00:07:29.920 align:start position:0% functionalities of a four node into many 00:07:29.920 --> 00:07:33.550 align:start position:0% functionalities of a four node into many independent<00:07:31.150> modules<00:07:32.150> and<00:07:32.420> each<00:07:32.780> module<00:07:33.050> can 00:07:33.550 --> 00:07:33.560 align:start position:0% independent modules and each module can 00:07:33.560 --> 00:07:38.620 align:start position:0% independent modules and each module can run<00:07:33.860> as<00:07:34.100> a<00:07:34.360> independent<00:07:35.360> process<00:07:37.150> all<00:07:38.150> of 00:07:38.620 --> 00:07:38.630 align:start position:0% run as a independent process all of 00:07:38.630 --> 00:07:44.740 align:start position:0% run as a independent process all of those<00:07:38.840> processes<00:07:39.370> can<00:07:40.370> run<00:07:42.970> each<00:07:43.970> process<00:07:44.510> can 00:07:44.740 --> 00:07:44.750 align:start position:0% those processes can run each process can 00:07:44.750 --> 00:07:47.830 align:start position:0% those processes can run each process can run<00:07:44.930> on<00:07:45.140> an<00:07:45.740> independent<00:07:46.190> server<00:07:46.820> so<00:07:47.510> you<00:07:47.570> can 00:07:47.830 --> 00:07:47.840 align:start position:0% run on an independent server so you can 00:07:47.840 --> 00:07:53.280 align:start position:0% run on an independent server so you can use<00:07:48.080> a<00:07:48.490> server<00:07:49.490> cluster<00:07:50.120> to<00:07:50.960> run<00:07:51.170> a<00:07:51.380> full<00:07:51.710> node 00:07:53.280 --> 00:07:53.290 align:start position:0% use a server cluster to run a full node 00:07:53.290 --> 00:07:59.140 align:start position:0% use a server cluster to run a full node that's<00:07:54.290> very<00:07:54.560> different<00:07:54.800> from<00:07:57.130> the<00:07:58.130> full<00:07:58.700> four 00:07:59.140 --> 00:07:59.150 align:start position:0% that's very different from the full four 00:07:59.150 --> 00:08:02.080 align:start position:0% that's very different from the full four node<00:07:59.330> clients<00:07:59.900> of<00:08:00.160> other<00:08:01.160> blockchains<00:08:01.730> today 00:08:02.080 --> 00:08:02.090 align:start position:0% node clients of other blockchains today 00:08:02.090 --> 00:08:07.030 align:start position:0% node clients of other blockchains today because<00:08:03.640> public<00:08:04.640> Bloch<00:08:04.970> and<00:08:05.180> clients<00:08:06.020> goal<00:08:06.770> is 00:08:07.030 --> 00:08:07.040 align:start position:0% because public Bloch and clients goal is 00:08:07.040 --> 00:08:11.830 align:start position:0% because public Bloch and clients goal is to<00:08:07.340> have<00:08:08.150> individual<00:08:09.970> round<00:08:10.970> the<00:08:11.330> phone<00:08:11.660> out 00:08:11.830 --> 00:08:11.840 align:start position:0% to have individual round the phone out 00:08:11.840 --> 00:08:15.810 align:start position:0% to have individual round the phone out on<00:08:12.080> their<00:08:12.290> laptop<00:08:12.740> but<00:08:13.550> for<00:08:13.760> enterprise<00:08:14.240> users 00:08:15.810 --> 00:08:15.820 align:start position:0% on their laptop but for enterprise users 00:08:15.820 --> 00:08:19.300 align:start position:0% on their laptop but for enterprise users they<00:08:16.820> can<00:08:17.030> afford<00:08:17.420> a<00:08:17.630> cluster<00:08:18.200> and<00:08:18.440> they<00:08:19.070> have 00:08:19.300 --> 00:08:19.310 align:start position:0% they can afford a cluster and they have 00:08:19.310 --> 00:08:23.040 align:start position:0% they can afford a cluster and they have the<00:08:19.490> operators<00:08:20.030> to<00:08:20.240> maintain<00:08:20.720> cluster<00:08:21.350> right 00:08:23.040 --> 00:08:23.050 align:start position:0% the operators to maintain cluster right 00:08:23.050 --> 00:08:26.460 align:start position:0% the operators to maintain cluster right this<00:08:24.050> architecture<00:08:24.860> can<00:08:25.070> fully<00:08:25.430> unleash<00:08:25.910> the 00:08:26.460 --> 00:08:26.470 align:start position:0% this architecture can fully unleash the 00:08:26.470 --> 00:08:30.460 align:start position:0% this architecture can fully unleash the resources<00:08:27.470> owned<00:08:27.770> by<00:08:28.130> enterprise<00:08:29.090> users<00:08:29.470> so 00:08:30.460 --> 00:08:30.470 align:start position:0% resources owned by enterprise users so 00:08:30.470 --> 00:08:34.480 align:start position:0% resources owned by enterprise users so insider'<00:08:30.940> we<00:08:31.940> have<00:08:32.210> consensus<00:08:33.020> service<00:08:33.950> which 00:08:34.480 --> 00:08:34.490 align:start position:0% insider' we have consensus service which 00:08:34.490 --> 00:08:37.180 align:start position:0% insider' we have consensus service which is<00:08:34.700> in<00:08:34.880> charge<00:08:34.910> of<00:08:35.479> ordering<00:08:36.290> all<00:08:36.950> the 00:08:37.180 --> 00:08:37.190 align:start position:0% is in charge of ordering all the 00:08:37.190 --> 00:08:41.350 align:start position:0% is in charge of ordering all the transactions<00:08:38.290> received<00:08:39.290> by<00:08:39.560> node<00:08:39.830> and<00:08:40.360> we 00:08:41.350 --> 00:08:41.360 align:start position:0% transactions received by node and we 00:08:41.360 --> 00:08:46.120 align:start position:0% transactions received by node and we have<00:08:41.540> executed<00:08:42.910> to<00:08:43.910> process<00:08:44.690> transactions<00:08:45.410> we 00:08:46.120 --> 00:08:46.130 align:start position:0% have executed to process transactions we 00:08:46.130 --> 00:08:48.730 align:start position:0% have executed to process transactions we have<00:08:46.310> authentication<00:08:46.760> service<00:08:47.690> RPC<00:08:48.410> service 00:08:48.730 --> 00:08:48.740 align:start position:0% have authentication service RPC service 00:08:48.740 --> 00:08:51.550 align:start position:0% have authentication service RPC service and<00:08:49.010> all<00:08:49.460> the<00:08:49.490> micro<00:08:49.940> services<00:08:50.570> exchange 00:08:51.550 --> 00:08:51.560 align:start position:0% and all the micro services exchange 00:08:51.560 --> 00:08:52.519 align:start position:0% and all the micro services exchange messages 00:08:52.519 --> 00:08:52.529 align:start position:0% messages 00:08:52.529 --> 00:08:55.730 align:start position:0% messages each<00:08:52.649> other<00:08:52.889> through<00:08:53.519> a<00:08:54.230> message<00:08:55.230> bus 00:08:55.730 --> 00:08:55.740 align:start position:0% each other through a message bus 00:08:55.740 --> 00:08:59.449 align:start position:0% each other through a message bus currently<00:08:56.579> we<00:08:56.819> use<00:08:56.970> Rebbe<00:08:57.420> MQ<00:08:57.899> as<00:08:58.079> the<00:08:58.649> message 00:08:59.449 --> 00:08:59.459 align:start position:0% currently we use Rebbe MQ as the message 00:08:59.459 --> 00:09:06.230 align:start position:0% currently we use Rebbe MQ as the message bus<00:08:59.670> between<00:09:00.300> those<00:09:01.040> micro-services<00:09:04.490> so<00:09:05.490> we 00:09:06.230 --> 00:09:06.240 align:start position:0% bus between those micro-services so we 00:09:06.240 --> 00:09:10.759 align:start position:0% bus between those micro-services so we turn<00:09:06.720> the<00:09:06.990> scale<00:09:07.829> up<00:09:08.040> note<00:09:09.079> we<00:09:10.079> turn<00:09:10.319> the<00:09:10.499> scale 00:09:10.759 --> 00:09:10.769 align:start position:0% turn the scale up note we turn the scale 00:09:10.769 --> 00:09:15.519 align:start position:0% turn the scale up note we turn the scale up<00:09:10.980> solution<00:09:11.809> into<00:09:12.809> a<00:09:13.579> scale<00:09:14.579> out<00:09:14.790> solution 00:09:15.519 --> 00:09:15.529 align:start position:0% up solution into a scale out solution 00:09:15.529 --> 00:09:19.069 align:start position:0% up solution into a scale out solution inside<00:09:16.529> a<00:09:16.829> logical<00:09:17.639> node<00:09:17.850> what<00:09:18.300> is<00:09:18.449> a<00:09:18.629> logical 00:09:19.069 --> 00:09:19.079 align:start position:0% inside a logical node what is a logical 00:09:19.079 --> 00:09:21.920 align:start position:0% inside a logical node what is a logical node<00:09:19.529> because<00:09:19.889> in<00:09:20.519> Siddha<00:09:20.850> a<00:09:21.029> faunal<00:09:21.509> is<00:09:21.689> not 00:09:21.920 --> 00:09:21.930 align:start position:0% node because in Siddha a faunal is not 00:09:21.930 --> 00:09:26.150 align:start position:0% node because in Siddha a faunal is not necessarily<00:09:22.499> our<00:09:23.220> server<00:09:23.730> so<00:09:24.689> we<00:09:25.499> call<00:09:25.769> we 00:09:26.150 --> 00:09:26.160 align:start position:0% necessarily our server so we call we 00:09:26.160 --> 00:09:29.929 align:start position:0% necessarily our server so we call we recorded<00:09:26.790> a<00:09:26.910> logical<00:09:27.569> node<00:09:27.749> because<00:09:28.279> it<00:09:29.279> may 00:09:29.929 --> 00:09:29.939 align:start position:0% recorded a logical node because it may 00:09:29.939 --> 00:09:37.069 align:start position:0% recorded a logical node because it may run<00:09:30.240> on<00:09:30.509> a<00:09:30.569> server<00:09:31.319> cluster<00:09:33.110> so<00:09:35.749> on<00:09:36.749> the<00:09:36.930> right 00:09:37.069 --> 00:09:37.079 align:start position:0% run on a server cluster so on the right 00:09:37.079 --> 00:09:39.920 align:start position:0% run on a server cluster so on the right side<00:09:37.110> is<00:09:37.620> a<00:09:38.069> logical<00:09:38.699> node<00:09:38.910> with<00:09:39.149> many<00:09:39.449> servers 00:09:39.920 --> 00:09:39.930 align:start position:0% side is a logical node with many servers 00:09:39.930 --> 00:09:43.160 align:start position:0% side is a logical node with many servers inside<00:09:40.499> it<00:09:40.769> from<00:09:41.699> the<00:09:41.910> other<00:09:42.120> phone<00:09:42.660> as<00:09:42.839> point 00:09:43.160 --> 00:09:43.170 align:start position:0% inside it from the other phone as point 00:09:43.170 --> 00:09:46.730 align:start position:0% inside it from the other phone as point of<00:09:43.319> view<00:09:43.559> point<00:09:44.459> of<00:09:44.579> view<00:09:44.759> it<00:09:45.749> doesn't<00:09:46.019> know<00:09:46.379> if 00:09:46.730 --> 00:09:46.740 align:start position:0% of view point of view it doesn't know if 00:09:46.740 --> 00:09:51.799 align:start position:0% of view point of view it doesn't know if the<00:09:47.959> other<00:09:48.959> funnel<00:09:49.589> is<00:09:49.800> wrong<00:09:50.279> is<00:09:50.629> running<00:09:51.629> on 00:09:51.799 --> 00:09:51.809 align:start position:0% the other funnel is wrong is running on 00:09:51.809 --> 00:09:56.900 align:start position:0% the other funnel is wrong is running on 10<00:09:52.079> servers<00:09:52.709> or<00:09:53.009> hundred<00:09:53.670> of<00:09:53.759> servers<00:09:55.910> so 00:09:56.900 --> 00:09:56.910 align:start position:0% 10 servers or hundred of servers so 00:09:56.910 --> 00:10:00.429 align:start position:0% 10 servers or hundred of servers so what's<00:09:57.120> the<00:09:57.240> benefit<00:09:57.829> if<00:09:58.829> we<00:09:59.100> break<00:09:59.430> the 00:10:00.429 --> 00:10:00.439 align:start position:0% what's the benefit if we break the 00:10:00.439 --> 00:10:02.600 align:start position:0% what's the benefit if we break the functionalities<00:10:01.439> into<00:10:01.920> independent 00:10:02.600 --> 00:10:02.610 align:start position:0% functionalities into independent 00:10:02.610 --> 00:10:06.559 align:start position:0% functionalities into independent processes<00:10:03.120> we<00:10:03.990> can<00:10:04.170> do<00:10:04.319> a<00:10:04.350> lot<00:10:04.680> of<00:10:05.569> concurrent 00:10:06.559 --> 00:10:06.569 align:start position:0% processes we can do a lot of concurrent 00:10:06.569 --> 00:10:10.220 align:start position:0% processes we can do a lot of concurrent and<00:10:06.689> parallel<00:10:07.579> optimizations<00:10:08.750> for<00:10:09.750> example 00:10:10.220 --> 00:10:10.230 align:start position:0% and parallel optimizations for example 00:10:10.230 --> 00:10:13.389 align:start position:0% and parallel optimizations for example in<00:10:10.470> Siddha<00:10:11.129> we<00:10:11.370> have<00:10:12.199> implemented 00:10:13.389 --> 00:10:13.399 align:start position:0% in Siddha we have implemented 00:10:13.399 --> 00:10:16.069 align:start position:0% in Siddha we have implemented asynchronous<00:10:14.399> transaction<00:10:15.300> validation<00:10:15.899> and 00:10:16.069 --> 00:10:16.079 align:start position:0% asynchronous transaction validation and 00:10:16.079 --> 00:10:20.809 align:start position:0% asynchronous transaction validation and execution<00:10:16.829> what<00:10:17.129> does<00:10:17.279> it<00:10:17.459> mean<00:10:19.309> when<00:10:20.309> a<00:10:20.519> foo 00:10:20.809 --> 00:10:20.819 align:start position:0% execution what does it mean when a foo 00:10:20.819 --> 00:10:24.590 align:start position:0% execution what does it mean when a foo note<00:10:21.059> when<00:10:21.990> foo<00:10:22.290> node<00:10:22.529> receives<00:10:22.769> a<00:10:23.339> new<00:10:24.240> block 00:10:24.590 --> 00:10:24.600 align:start position:0% note when foo node receives a new block 00:10:24.600 --> 00:10:27.740 align:start position:0% note when foo node receives a new block the<00:10:25.559> new<00:10:25.769> block<00:10:26.040> will<00:10:26.309> be<00:10:26.550> broadcast<00:10:27.449> to 00:10:27.740 --> 00:10:27.750 align:start position:0% the new block will be broadcast to 00:10:27.750 --> 00:10:30.350 align:start position:0% the new block will be broadcast to execute<00:10:28.589> an<00:10:28.829> hour<00:10:29.100> service<00:10:29.550> at<00:10:29.730> the<00:10:29.850> same<00:10:30.089> time 00:10:30.350 --> 00:10:30.360 align:start position:0% execute an hour service at the same time 00:10:30.360 --> 00:10:34.400 align:start position:0% execute an hour service at the same time and<00:10:30.740> us<00:10:31.740> and<00:10:32.420> executed<00:10:33.420> service<00:10:33.809> can 00:10:34.400 --> 00:10:34.410 align:start position:0% and us and executed service can 00:10:34.410 --> 00:10:38.480 align:start position:0% and us and executed service can optimistically<00:10:35.509> pre<00:10:36.509> compute<00:10:37.110> the<00:10:37.949> new<00:10:38.189> block 00:10:38.480 --> 00:10:38.490 align:start position:0% optimistically pre compute the new block 00:10:38.490 --> 00:10:41.509 align:start position:0% optimistically pre compute the new block and<00:10:38.759> validate<00:10:39.360> transactions<00:10:40.019> in<00:10:40.259> in<00:10:41.189> the<00:10:41.370> new 00:10:41.509 --> 00:10:41.519 align:start position:0% and validate transactions in in the new 00:10:41.519 --> 00:10:47.079 align:start position:0% and validate transactions in in the new block<00:10:43.759> it's<00:10:44.759> our<00:10:45.089> concurrent<00:10:45.750> process<00:10:46.259> and 00:10:47.079 --> 00:10:47.089 align:start position:0% block it's our concurrent process and 00:10:47.089 --> 00:10:50.449 align:start position:0% block it's our concurrent process and this<00:10:48.089> change<00:10:48.420> will<00:10:48.779> largely<00:10:49.589> increase<00:10:50.160> the 00:10:50.449 --> 00:10:50.459 align:start position:0% this change will largely increase the 00:10:50.459 --> 00:10:59.020 align:start position:0% this change will largely increase the system's<00:10:53.059> efficient<00:10:54.589> efficiency 00:10:59.020 --> 00:10:59.030 align:start position:0% 00:10:59.030 --> 00:11:00.970 align:start position:0% this<00:10:59.120> is<00:10:59.270> a<00:10:59.450> synchrony<00:11:00.050> in<00:11:00.290> a<00:11:00.380> single<00:11:00.740> block 00:11:00.970 --> 00:11:00.980 align:start position:0% this is a synchrony in a single block 00:11:00.980 --> 00:11:06.940 align:start position:0% this is a synchrony in a single block and<00:11:01.810> we<00:11:02.810> because<00:11:03.470> much<00:11:04.370> farther<00:11:04.670> than<00:11:04.820> that<00:11:05.950> we 00:11:06.940 --> 00:11:06.950 align:start position:0% and we because much farther than that we 00:11:06.950 --> 00:11:09.730 align:start position:0% and we because much farther than that we separate<00:11:07.520> consensus<00:11:08.180> service<00:11:08.690> and<00:11:08.930> executor 00:11:09.730 --> 00:11:09.740 align:start position:0% separate consensus service and executor 00:11:09.740 --> 00:11:14.800 align:start position:0% separate consensus service and executor service<00:11:10.300> completely<00:11:11.320> so<00:11:13.030> when<00:11:14.030> the<00:11:14.300> system 00:11:14.800 --> 00:11:14.810 align:start position:0% service completely so when the system 00:11:14.810 --> 00:11:19.780 align:start position:0% service completely so when the system load<00:11:15.080> of<00:11:15.380> a<00:11:16.250> is<00:11:17.090> super<00:11:17.360> high<00:11:17.690> and<00:11:18.580> all<00:11:19.580> the 00:11:19.780 --> 00:11:19.790 align:start position:0% load of a is super high and all the 00:11:19.790 --> 00:11:22.360 align:start position:0% load of a is super high and all the transactions<00:11:20.330> cannot<00:11:20.750> be<00:11:20.960> processed<00:11:21.260> in<00:11:21.800> one 00:11:22.360 --> 00:11:22.370 align:start position:0% transactions cannot be processed in one 00:11:22.370 --> 00:11:24.580 align:start position:0% transactions cannot be processed in one block<00:11:22.640> time<00:11:22.940> which<00:11:23.480> is<00:11:23.660> three<00:11:24.020> seconds<00:11:24.380> in 00:11:24.580 --> 00:11:24.590 align:start position:0% block time which is three seconds in 00:11:24.590 --> 00:11:30.700 align:start position:0% block time which is three seconds in Serie<00:11:25.270> the<00:11:26.350> the<00:11:27.350> execution<00:11:28.130> can<00:11:28.750> last<00:11:29.750> across 00:11:30.700 --> 00:11:30.710 align:start position:0% Serie the the execution can last across 00:11:30.710 --> 00:11:33.340 align:start position:0% Serie the the execution can last across many<00:11:31.070> blocks<00:11:31.460> and<00:11:31.790> the<00:11:32.510> state<00:11:32.720> route<00:11:32.960> of<00:11:33.170> the 00:11:33.340 --> 00:11:33.350 align:start position:0% many blocks and the state route of the 00:11:33.350 --> 00:11:37.300 align:start position:0% many blocks and the state route of the final<00:11:33.800> result<00:11:34.160> will<00:11:34.490> be<00:11:35.060> right<00:11:35.720> back<00:11:35.990> to<00:11:36.310> will 00:11:37.300 --> 00:11:37.310 align:start position:0% final result will be right back to will 00:11:37.310 --> 00:11:39.370 align:start position:0% final result will be right back to will be<00:11:37.430> written<00:11:37.610> back<00:11:37.910> to<00:11:37.940> the<00:11:38.270> block<00:11:38.510> when<00:11:39.200> it's 00:11:39.370 --> 00:11:39.380 align:start position:0% be written back to the block when it's 00:11:39.380 --> 00:11:41.910 align:start position:0% be written back to the block when it's finished<00:11:39.770> maybe<00:11:40.070> it's<00:11:40.250> three<00:11:40.430> blocks<00:11:40.730> later 00:11:41.910 --> 00:11:41.920 align:start position:0% finished maybe it's three blocks later 00:11:41.920 --> 00:11:50.710 align:start position:0% finished maybe it's three blocks later and<00:11:43.600> we<00:11:44.680> also<00:11:48.310> we<00:11:49.310> also<00:11:49.550> do<00:11:49.850> a<00:11:49.880> lot<00:11:50.090> of<00:11:50.150> parallel 00:11:50.710 --> 00:11:50.720 align:start position:0% and we also we also do a lot of parallel 00:11:50.720 --> 00:11:56.230 align:start position:0% and we also we also do a lot of parallel optimizations<00:11:51.590> in<00:11:51.830> Silla<00:11:54.850> so<00:11:55.850> this<00:11:56.060> is<00:11:56.210> a 00:11:56.230 --> 00:11:56.240 align:start position:0% optimizations in Silla so this is a 00:11:56.240 --> 00:11:58.680 align:start position:0% optimizations in Silla so this is a better<00:11:56.540> picture<00:11:56.810> than<00:11:57.040> previous<00:11:58.040> one<00:11:58.250> right 00:11:58.680 --> 00:11:58.690 align:start position:0% better picture than previous one right 00:11:58.690 --> 00:12:02.860 align:start position:0% better picture than previous one right instead<00:11:59.690> of<00:11:59.870> only<00:12:00.110> one<00:12:00.460> service<00:12:01.460> we<00:12:02.450> can<00:12:02.660> run 00:12:02.860 --> 00:12:02.870 align:start position:0% instead of only one service we can run 00:12:02.870 --> 00:12:06.690 align:start position:0% instead of only one service we can run many<00:12:03.170> service<00:12:03.740> instances<00:12:04.370> for<00:12:04.790> for<00:12:05.270> any<00:12:05.480> of 00:12:06.690 --> 00:12:06.700 align:start position:0% many service instances for for any of 00:12:06.700 --> 00:12:09.450 align:start position:0% many service instances for for any of the<00:12:07.700> macro<00:12:08.120> service<00:12:08.450> we<00:12:08.600> can<00:12:08.720> have<00:12:08.900> three 00:12:09.450 --> 00:12:09.460 align:start position:0% the macro service we can have three 00:12:09.460 --> 00:12:11.560 align:start position:0% the macro service we can have three authentication<00:12:10.460> service<00:12:10.880> to<00:12:11.150> validate 00:12:11.560 --> 00:12:11.570 align:start position:0% authentication service to validate 00:12:11.570 --> 00:12:14.470 align:start position:0% authentication service to validate transaction<00:12:12.200> signatures<00:12:12.800> we<00:12:13.490> can<00:12:13.670> have<00:12:13.880> three 00:12:14.470 --> 00:12:14.480 align:start position:0% transaction signatures we can have three 00:12:14.480 --> 00:12:17.860 align:start position:0% transaction signatures we can have three RPC<00:12:15.410> service<00:12:15.730> instances<00:12:16.730> to<00:12:17.090> receive 00:12:17.860 --> 00:12:17.870 align:start position:0% RPC service instances to receive 00:12:17.870 --> 00:12:20.860 align:start position:0% RPC service instances to receive requests<00:12:18.590> from<00:12:19.040> clients<00:12:19.370> and<00:12:19.910> we<00:12:20.510> can<00:12:20.690> have 00:12:20.860 --> 00:12:20.870 align:start position:0% requests from clients and we can have 00:12:20.870 --> 00:12:23.860 align:start position:0% requests from clients and we can have many<00:12:21.200> executors<00:12:22.010> to<00:12:22.340> round<00:12:22.940> transactions<00:12:23.630> in 00:12:23.860 --> 00:12:23.870 align:start position:0% many executors to round transactions in 00:12:23.870 --> 00:12:30.940 align:start position:0% many executors to round transactions in parallel<00:12:27.670> so<00:12:28.670> this<00:12:28.880> is<00:12:29.090> the<00:12:29.590> this<00:12:30.590> is<00:12:30.650> a 00:12:30.940 --> 00:12:30.950 align:start position:0% parallel so this is the this is a 00:12:30.950 --> 00:12:34.870 align:start position:0% parallel so this is the this is a benchmark<00:12:31.490> result<00:12:31.910> of<00:12:32.120> Syrah<00:12:32.450> we<00:12:33.320> did<00:12:33.880> one 00:12:34.870 --> 00:12:34.880 align:start position:0% benchmark result of Syrah we did one 00:12:34.880 --> 00:12:39.250 align:start position:0% benchmark result of Syrah we did one week<00:12:35.060> ago<00:12:35.240> we<00:12:36.760> we<00:12:37.760> deployed<00:12:38.210> a<00:12:38.510> network<00:12:39.050> with 00:12:39.250 --> 00:12:39.260 align:start position:0% week ago we we deployed a network with 00:12:39.260 --> 00:12:45.210 align:start position:0% week ago we we deployed a network with ten<00:12:39.560> logical<00:12:40.070> nodes<00:12:40.310> on<00:12:40.640> a<00:12:41.330> cloud<00:12:41.810> service<00:12:42.170> and 00:12:45.210 --> 00:12:45.220 align:start position:0% 00:12:45.220 --> 00:12:48.730 align:start position:0% the<00:12:46.220> throughput<00:12:46.520> of<00:12:46.880> the<00:12:47.060> ten<00:12:47.300> node<00:12:47.740> network 00:12:48.730 --> 00:12:48.740 align:start position:0% the throughput of the ten node network 00:12:48.740 --> 00:12:52.030 align:start position:0% the throughput of the ten node network is<00:12:49.010> 15<00:12:49.880> thousands<00:12:50.630> transactions<00:12:51.470> per<00:12:51.620> second 00:12:52.030 --> 00:12:52.040 align:start position:0% is 15 thousands transactions per second 00:12:52.040 --> 00:12:58.270 align:start position:0% is 15 thousands transactions per second and<00:12:52.930> in<00:12:53.930> comparison<00:12:56.080> some<00:12:57.080> other<00:12:57.320> blockchain 00:12:58.270 --> 00:12:58.280 align:start position:0% and in comparison some other blockchain 00:12:58.280 --> 00:13:01.540 align:start position:0% and in comparison some other blockchain solution<00:12:58.850> or<00:12:59.450> the<00:13:00.200> the<00:13:00.980> most<00:13:01.190> popular 00:13:01.540 --> 00:13:01.550 align:start position:0% solution or the the most popular 00:13:01.550 --> 00:13:04.870 align:start position:0% solution or the the most popular approach<00:13:01.790> and<00:13:01.970> solution<00:13:02.330> today<00:13:03.700> can<00:13:04.700> reach 00:13:04.870 --> 00:13:04.880 align:start position:0% approach and solution today can reach 00:13:04.880 --> 00:13:07.920 align:start position:0% approach and solution today can reach only<00:13:05.360> fifteen<00:13:06.160> fifteen<00:13:07.160> hundred 00:13:07.920 --> 00:13:07.930 align:start position:0% only fifteen fifteen hundred 00:13:07.930 --> 00:13:10.510 align:start position:0% only fifteen fifteen hundred transactions<00:13:08.930> per<00:13:09.080> second<00:13:09.440> so<00:13:10.010> it's<00:13:10.190> a<00:13:10.280> ten 00:13:10.510 --> 00:13:10.520 align:start position:0% transactions per second so it's a ten 00:13:10.520 --> 00:13:11.910 align:start position:0% transactions per second so it's a ten times<00:13:10.850> difference 00:13:11.910 --> 00:13:11.920 align:start position:0% times difference 00:13:11.920 --> 00:13:15.509 align:start position:0% times difference and<00:13:12.040> we<00:13:12.639> found<00:13:12.880> that<00:13:13.470> the<00:13:14.470> throughput<00:13:15.040> of<00:13:15.310> the 00:13:15.509 --> 00:13:15.519 align:start position:0% and we found that the throughput of the 00:13:15.519 --> 00:13:18.319 align:start position:0% and we found that the throughput of the whole<00:13:15.670> network<00:13:16.350> will<00:13:17.350> increase 00:13:18.319 --> 00:13:18.329 align:start position:0% whole network will increase 00:13:18.329 --> 00:13:25.680 align:start position:0% whole network will increase proportionally<00:13:19.329> to<00:13:19.480> the<00:13:21.120> to<00:13:22.120> the<00:13:23.070> to<00:13:24.070> the<00:13:24.690> to 00:13:25.680 --> 00:13:25.690 align:start position:0% proportionally to the to the to the to 00:13:25.690 --> 00:13:27.780 align:start position:0% proportionally to the to the to the to the<00:13:25.810> ability<00:13:26.230> of<00:13:26.380> a<00:13:26.740> single<00:13:27.250> node<00:13:27.399> in<00:13:27.430> the 00:13:27.780 --> 00:13:27.790 align:start position:0% the ability of a single node in the 00:13:27.790 --> 00:13:33.629 align:start position:0% the ability of a single node in the system<00:13:29.339> like<00:13:30.339> the<00:13:30.639> orange<00:13:31.630> bar<00:13:31.899> we<00:13:32.350> use<00:13:32.560> a<00:13:32.800> 4x 00:13:33.629 --> 00:13:33.639 align:start position:0% system like the orange bar we use a 4x 00:13:33.639 --> 00:13:38.129 align:start position:0% system like the orange bar we use a 4x large<00:13:33.940> server<00:13:34.540> and<00:13:35.820> blue<00:13:36.820> in<00:13:37.209> in<00:13:37.660> the<00:13:37.779> blue<00:13:37.959> and 00:13:38.129 --> 00:13:38.139 align:start position:0% large server and blue in in the blue and 00:13:38.139 --> 00:13:42.360 align:start position:0% large server and blue in in the blue and red<00:13:38.230> deployment<00:13:39.040> they<00:13:39.699> use<00:13:40.589> twice<00:13:41.589> powerful 00:13:42.360 --> 00:13:42.370 align:start position:0% red deployment they use twice powerful 00:13:42.370 --> 00:13:46.530 align:start position:0% red deployment they use twice powerful hardware<00:13:42.959> and<00:13:44.579> another<00:13:45.579> interesting<00:13:46.149> thing 00:13:46.530 --> 00:13:46.540 align:start position:0% hardware and another interesting thing 00:13:46.540 --> 00:13:51.590 align:start position:0% hardware and another interesting thing is<00:13:48.120> we<00:13:49.120> find<00:13:49.480> that<00:13:49.660> the<00:13:50.019> blue<00:13:50.470> deployment<00:13:51.160> and 00:13:51.590 --> 00:13:51.600 align:start position:0% is we find that the blue deployment and 00:13:51.600 --> 00:13:54.960 align:start position:0% is we find that the blue deployment and the<00:13:52.600> performance<00:13:53.380> of<00:13:53.560> blue<00:13:53.800> deployment<00:13:54.430> is 00:13:54.960 --> 00:13:54.970 align:start position:0% the performance of blue deployment is 00:13:54.970 --> 00:13:57.720 align:start position:0% the performance of blue deployment is almost<00:13:55.750> the<00:13:55.930> same<00:13:56.170> as<00:13:56.440> red<00:13:56.680> deployment<00:13:57.279> but 00:13:57.720 --> 00:13:57.730 align:start position:0% almost the same as red deployment but 00:13:57.730 --> 00:14:00.540 align:start position:0% almost the same as red deployment but the<00:13:57.910> blue<00:13:58.120> one<00:13:58.149> uses<00:13:59.079> a<00:13:59.260> single<00:13:59.800> server<00:14:00.130> for<00:14:00.519> a 00:14:00.540 --> 00:14:00.550 align:start position:0% the blue one uses a single server for a 00:14:00.550 --> 00:14:03.650 align:start position:0% the blue one uses a single server for a logical<00:14:01.089> node<00:14:01.269> but<00:14:01.540> the<00:14:01.720> red<00:14:01.930> one<00:14:02.170> use<00:14:02.639> three 00:14:03.650 --> 00:14:03.660 align:start position:0% logical node but the red one use three 00:14:03.660 --> 00:14:07.910 align:start position:0% logical node but the red one use three lower<00:14:04.660> grades<00:14:05.110> servers<00:14:05.980> for<00:14:06.490> a<00:14:06.550> single<00:14:07.089> node 00:14:07.910 --> 00:14:07.920 align:start position:0% lower grades servers for a single node 00:14:07.920 --> 00:14:11.370 align:start position:0% lower grades servers for a single node for<00:14:08.920> a<00:14:08.949> single<00:14:09.250> logical<00:14:09.670> node<00:14:10.120> so<00:14:10.930> the<00:14:11.050> result 00:14:11.370 --> 00:14:11.380 align:start position:0% for a single logical node so the result 00:14:11.380 --> 00:14:14.759 align:start position:0% for a single logical node so the result is<00:14:11.470> very<00:14:11.769> promising<00:14:12.399> and<00:14:13.019> all<00:14:14.019> of<00:14:14.380> this<00:14:14.529> is 00:14:14.759 --> 00:14:14.769 align:start position:0% is very promising and all of this is 00:14:14.769 --> 00:14:15.780 align:start position:0% is very promising and all of this is just<00:14:14.800> a<00:14:15.220> beginning 00:14:15.780 --> 00:14:15.790 align:start position:0% just a beginning 00:14:15.790 --> 00:14:18.780 align:start position:0% just a beginning we<00:14:16.360> are<00:14:16.440> still<00:14:17.440> pushing<00:14:17.829> very<00:14:18.010> hard<00:14:18.250> to 00:14:18.780 --> 00:14:18.790 align:start position:0% we are still pushing very hard to 00:14:18.790 --> 00:14:20.310 align:start position:0% we are still pushing very hard to increase<00:14:19.420> the<00:14:19.690> system's 00:14:20.310 --> 00:14:20.320 align:start position:0% increase the system's 00:14:20.320 --> 00:14:25.259 align:start position:0% increase the system's Ruppert<00:14:20.910> to<00:14:21.910> do<00:14:22.089> more<00:14:22.839> parallelism<00:14:23.970> in<00:14:24.970> silla 00:14:25.259 --> 00:14:25.269 align:start position:0% Ruppert to do more parallelism in silla 00:14:25.269 --> 00:14:31.800 align:start position:0% Ruppert to do more parallelism in silla and<00:14:29.610> actually<00:14:30.610> the<00:14:31.060> micro<00:14:31.480> service 00:14:31.800 --> 00:14:31.810 align:start position:0% and actually the micro service 00:14:31.810 --> 00:14:33.930 align:start position:0% and actually the micro service architecture<00:14:32.019> is<00:14:32.500> the<00:14:32.560> only<00:14:32.890> cloud<00:14:33.370> friendly 00:14:33.930 --> 00:14:33.940 align:start position:0% architecture is the only cloud friendly 00:14:33.940 --> 00:14:37.110 align:start position:0% architecture is the only cloud friendly architecture<00:14:34.630> the<00:14:34.750> de<00:14:35.850> cloud<00:14:36.850> for<00:14:37.029> any 00:14:37.110 --> 00:14:37.120 align:start position:0% architecture the de cloud for any 00:14:37.120 --> 00:14:42.449 align:start position:0% architecture the de cloud for any blotching<00:14:37.540> architecture<00:14:38.110> today<00:14:40.649> because<00:14:41.649> you 00:14:42.449 --> 00:14:42.459 align:start position:0% blotching architecture today because you 00:14:42.459 --> 00:14:46.800 align:start position:0% blotching architecture today because you can<00:14:43.110> fully<00:14:44.110> utilize<00:14:44.820> the<00:14:45.820> server<00:14:46.089> instances 00:14:46.800 --> 00:14:46.810 align:start position:0% can fully utilize the server instances 00:14:46.810 --> 00:14:49.259 align:start position:0% can fully utilize the server instances on<00:14:47.110> cloud<00:14:47.440> you<00:14:48.250> can<00:14:48.430> run<00:14:48.579> many<00:14:48.820> server 00:14:49.259 --> 00:14:49.269 align:start position:0% on cloud you can run many server 00:14:49.269 --> 00:14:54.769 align:start position:0% on cloud you can run many server instances<00:14:49.890> to<00:14:50.890> power<00:14:51.370> a<00:14:51.519> phone<00:14:52.089> note<00:14:53.399> and 00:14:54.769 --> 00:14:54.779 align:start position:0% instances to power a phone note and 00:14:54.779 --> 00:14:57.660 align:start position:0% instances to power a phone note and there<00:14:55.779> are<00:14:55.870> many<00:14:56.079> other<00:14:56.529> interesting<00:14:57.279> designs 00:14:57.660 --> 00:14:57.670 align:start position:0% there are many other interesting designs 00:14:57.670 --> 00:15:01.189 align:start position:0% there are many other interesting designs and<00:14:58.060> I<00:14:58.240> I<00:14:58.569> can<00:14:58.990> no<00:14:59.170> not<00:14:59.740> not<00:14:59.949> enough<00:15:00.220> time<00:15:00.459> but 00:15:01.189 --> 00:15:01.199 align:start position:0% and I I can no not not enough time but 00:15:01.199 --> 00:15:05.460 align:start position:0% and I I can no not not enough time but well<00:15:02.760> we<00:15:03.760> have<00:15:03.910> native<00:15:04.120> contract<00:15:04.779> other<00:15:05.140> than 00:15:05.460 --> 00:15:05.470 align:start position:0% well we have native contract other than 00:15:05.470 --> 00:15:06.780 align:start position:0% well we have native contract other than EVM<00:15:06.100> Conchetta 00:15:06.780 --> 00:15:06.790 align:start position:0% EVM Conchetta 00:15:06.790 --> 00:15:10.110 align:start position:0% EVM Conchetta in<00:15:07.569> the<00:15:07.870> default<00:15:08.410> see<00:15:08.709> that<00:15:08.889> stack<00:15:09.430> with 00:15:10.110 --> 00:15:10.120 align:start position:0% in the default see that stack with 00:15:10.120 --> 00:15:12.600 align:start position:0% in the default see that stack with support<00:15:10.540> EVM<00:15:10.930> concha<00:15:11.440> by<00:15:11.709> default<00:15:12.069> but<00:15:12.550> you 00:15:12.600 --> 00:15:12.610 align:start position:0% support EVM concha by default but you 00:15:12.610 --> 00:15:15.660 align:start position:0% support EVM concha by default but you can<00:15:12.790> always<00:15:13.750> rewrite<00:15:14.079> your<00:15:14.529> solidity<00:15:15.250> country 00:15:15.660 --> 00:15:15.670 align:start position:0% can always rewrite your solidity country 00:15:15.670 --> 00:15:18.059 align:start position:0% can always rewrite your solidity country with<00:15:15.850> native<00:15:16.269> code<00:15:16.540> and<00:15:16.720> our<00:15:17.680> native 00:15:18.059 --> 00:15:18.069 align:start position:0% with native code and our native 00:15:18.069 --> 00:15:21.930 align:start position:0% with native code and our native conscious<00:15:18.699> support<00:15:19.540> solidity<00:15:20.319> ABI<00:15:20.709> and<00:15:21.160> it 00:15:21.930 --> 00:15:21.940 align:start position:0% conscious support solidity ABI and it 00:15:21.940 --> 00:15:24.720 align:start position:0% conscious support solidity ABI and it provides<00:15:22.470> solidity<00:15:23.470> compatible<00:15:24.160> storage 00:15:24.720 --> 00:15:24.730 align:start position:0% provides solidity compatible storage 00:15:24.730 --> 00:15:30.360 align:start position:0% provides solidity compatible storage API<00:15:25.029> so<00:15:25.360> you<00:15:25.389> can<00:15:25.740> use<00:15:26.740> mappings<00:15:28.290> those<00:15:29.370> data 00:15:30.360 --> 00:15:30.370 align:start position:0% API so you can use mappings those data 00:15:30.370 --> 00:15:34.319 align:start position:0% API so you can use mappings those data structures<00:15:30.760> in<00:15:31.240> native<00:15:32.050> concept<00:15:32.560> and<00:15:33.329> a 00:15:34.319 --> 00:15:34.329 align:start position:0% structures in native concept and a 00:15:34.329 --> 00:15:37.050 align:start position:0% structures in native concept and a solidity<00:15:35.170> country<00:15:35.620> can<00:15:35.800> go<00:15:36.010> into<00:15:36.250> native 00:15:37.050 --> 00:15:37.060 align:start position:0% solidity country can go into native 00:15:37.060 --> 00:15:40.490 align:start position:0% solidity country can go into native concept<00:15:38.100> naturally<00:15:39.100> without<00:15:39.519> any<00:15:39.880> change 00:15:40.490 --> 00:15:40.500 align:start position:0% concept naturally without any change 00:15:40.500 --> 00:15:44.100 align:start position:0% concept naturally without any change this<00:15:41.500> is<00:15:41.680> an<00:15:41.920> example<00:15:42.579> in<00:15:42.730> rust<00:15:42.970> by<00:15:43.899> the<00:15:43.959> way 00:15:44.100 --> 00:15:44.110 align:start position:0% this is an example in rust by the way 00:15:44.110 --> 00:15:52.769 align:start position:0% this is an example in rust by the way Siddha<00:15:44.470> is<00:15:44.649> written<00:15:45.310> in<00:15:45.459> rust<00:15:46.829> and<00:15:51.779> the 00:15:52.769 --> 00:15:52.779 align:start position:0% Siddha is written in rust and the 00:15:52.779 --> 00:15:55.170 align:start position:0% Siddha is written in rust and the beautiful<00:15:53.410> of<00:15:53.500> the<00:15:53.740> the<00:15:54.070> scale<00:15:54.310> of<00:15:54.519> solution 00:15:55.170 --> 00:15:55.180 align:start position:0% beautiful of the the scale of solution 00:15:55.180 --> 00:15:58.650 align:start position:0% beautiful of the the scale of solution is<00:15:55.329> that<00:15:55.600> the<00:15:56.260> solution<00:15:56.740> is<00:15:56.769> of<00:15:57.329> orthogonal<00:15:58.329> to 00:15:58.650 --> 00:15:58.660 align:start position:0% is that the solution is of orthogonal to 00:15:58.660 --> 00:16:03.180 align:start position:0% is that the solution is of orthogonal to all<00:15:58.899> the<00:15:59.079> future<00:16:01.019> scaling<00:16:02.019> solutions<00:16:02.589> like 00:16:03.180 --> 00:16:03.190 align:start position:0% all the future scaling solutions like 00:16:03.190 --> 00:16:06.389 align:start position:0% all the future scaling solutions like sharding<00:16:03.730> plasma<00:16:04.630> state<00:16:04.959> channel<00:16:05.380> you<00:16:06.250> can 00:16:06.389 --> 00:16:06.399 align:start position:0% sharding plasma state channel you can 00:16:06.399 --> 00:16:11.060 align:start position:0% sharding plasma state channel you can use<00:16:06.550> them<00:16:06.760> together<00:16:06.959> and<00:16:07.959> I<00:16:08.350> believe<00:16:08.740> even<00:16:09.010> in 00:16:11.060 --> 00:16:11.070 align:start position:0% use them together and I believe even in 00:16:11.070 --> 00:16:14.519 align:start position:0% use them together and I believe even in scalability<00:16:12.070> solution<00:16:12.699> like<00:16:12.850> plasma<00:16:13.529> the 00:16:14.519 --> 00:16:14.529 align:start position:0% scalability solution like plasma the 00:16:14.529 --> 00:16:20.460 align:start position:0% scalability solution like plasma the root<00:16:14.769> chain<00:16:15.269> still<00:16:16.269> need<00:16:16.510> very<00:16:19.199> very<00:16:20.199> high 00:16:20.460 --> 00:16:20.470 align:start position:0% root chain still need very very high 00:16:20.470 --> 00:16:23.579 align:start position:0% root chain still need very very high performance<00:16:20.980> still<00:16:21.459> need<00:16:21.699> to<00:16:22.570> do<00:16:22.870> a<00:16:23.199> lot<00:16:23.560> of 00:16:23.579 --> 00:16:23.589 align:start position:0% performance still need to do a lot of 00:16:23.589 --> 00:16:26.220 align:start position:0% performance still need to do a lot of things<00:16:23.980> like<00:16:24.220> we<00:16:24.430> did<00:16:24.760> in<00:16:24.970> Siddha<00:16:25.209> to<00:16:25.810> support 00:16:26.220 --> 00:16:26.230 align:start position:0% things like we did in Siddha to support 00:16:26.230 --> 00:16:31.829 align:start position:0% things like we did in Siddha to support all<00:16:26.440> those<00:16:26.589> orders<00:16:27.630> child<00:16:28.630> chains<00:16:30.000> and<00:16:31.000> this 00:16:31.829 --> 00:16:31.839 align:start position:0% all those orders child chains and this 00:16:31.839 --> 00:16:36.480 align:start position:0% all those orders child chains and this is<00:16:32.019> a<00:16:32.260> typical<00:16:32.620> network<00:16:33.250> of<00:16:33.519> Siddha<00:16:35.100> so<00:16:36.100> we 00:16:36.480 --> 00:16:36.490 align:start position:0% is a typical network of Siddha so we 00:16:36.490 --> 00:16:38.730 align:start position:0% is a typical network of Siddha so we build<00:16:36.730> this<00:16:36.880> neck<00:16:37.209> we<00:16:37.750> built<00:16:38.319> this<00:16:38.440> network 00:16:38.730 --> 00:16:38.740 align:start position:0% build this neck we built this network 00:16:38.740 --> 00:16:41.400 align:start position:0% build this neck we built this network for<00:16:39.130> enterprise<00:16:39.639> users<00:16:39.940> each<00:16:40.779> enterprise 00:16:41.400 --> 00:16:41.410 align:start position:0% for enterprise users each enterprise 00:16:41.410 --> 00:16:44.069 align:start position:0% for enterprise users each enterprise user<00:16:41.680> can<00:16:42.040> run<00:16:42.250> a<00:16:42.279> full<00:16:42.670> node<00:16:42.940> which<00:16:43.630> include 00:16:44.069 --> 00:16:44.079 align:start position:0% user can run a full node which include 00:16:44.079 --> 00:16:48.150 align:start position:0% user can run a full node which include many<00:16:44.410> micro<00:16:45.010> services<00:16:45.490> and<00:16:45.730> their<00:16:46.860> users<00:16:47.860> can 00:16:48.150 --> 00:16:48.160 align:start position:0% many micro services and their users can 00:16:48.160 --> 00:16:50.819 align:start position:0% many micro services and their users can get<00:16:48.639> access<00:16:48.910> to<00:16:49.180> the<00:16:49.510> network<00:16:49.720> through<00:16:50.589> their 00:16:50.819 --> 00:16:50.829 align:start position:0% get access to the network through their 00:16:50.829 --> 00:16:56.460 align:start position:0% get access to the network through their phone<00:16:51.190> out<00:16:51.630> this<00:16:52.630> Hebron<00:16:53.230> model<00:16:54.959> within<00:16:55.959> this 00:16:56.460 --> 00:16:56.470 align:start position:0% phone out this Hebron model within this 00:16:56.470 --> 00:16:59.550 align:start position:0% phone out this Hebron model within this hybrid<00:16:56.980> model<00:16:57.010> deserves<00:16:57.639> more<00:16:58.560> consideration 00:16:59.550 --> 00:16:59.560 align:start position:0% hybrid model deserves more consideration 00:16:59.560 --> 00:17:03.509 align:start position:0% hybrid model deserves more consideration and<00:16:59.740> more<00:17:00.550> research<00:17:00.880> and<00:17:02.100> we<00:17:03.100> can<00:17:03.279> build 00:17:03.509 --> 00:17:03.519 align:start position:0% and more research and we can build 00:17:03.519 --> 00:17:05.429 align:start position:0% and more research and we can build decentralized<00:17:03.760> enterprise<00:17:04.750> application<00:17:05.350> on 00:17:05.429 --> 00:17:05.439 align:start position:0% decentralized enterprise application on 00:17:05.439 --> 00:17:07.620 align:start position:0% decentralized enterprise application on this<00:17:05.559> network<00:17:06.040> and<00:17:06.549> if<00:17:06.970> you<00:17:07.089> are<00:17:07.179> interested 00:17:07.620 --> 00:17:07.630 align:start position:0% this network and if you are interested 00:17:07.630 --> 00:17:10.890 align:start position:0% this network and if you are interested in<00:17:07.870> Sita<00:17:08.110> Sita<00:17:08.410> is<00:17:08.589> fully<00:17:09.370> open<00:17:09.970> sourced<00:17:10.329> and 00:17:10.890 --> 00:17:10.900 align:start position:0% in Sita Sita is fully open sourced and 00:17:10.900 --> 00:17:12.960 align:start position:0% in Sita Sita is fully open sourced and you<00:17:11.020> will<00:17:11.230> you<00:17:11.530> can<00:17:11.650> find<00:17:11.949> his<00:17:12.130> white<00:17:12.309> paper<00:17:12.579> is 00:17:12.960 --> 00:17:12.970 align:start position:0% you will you can find his white paper is 00:17:12.970 --> 00:17:17.360 align:start position:0% you will you can find his white paper is all<00:17:13.329> of<00:17:13.660> its<00:17:13.809> code<00:17:14.079> and<00:17:14.380> we<00:17:15.309> view<00:17:15.760> talker<00:17:16.240> image 00:17:17.360 --> 00:17:17.370 align:start position:0% all of its code and we view talker image 00:17:17.370 --> 00:17:20.610 align:start position:0% all of its code and we view talker image and<00:17:18.370> we<00:17:18.579> provide<00:17:18.970> some<00:17:19.299> a<00:17:19.600> simple<00:17:20.260> bootstrap 00:17:20.610 --> 00:17:20.620 align:start position:0% and we provide some a simple bootstrap 00:17:20.620 --> 00:17:22.620 align:start position:0% and we provide some a simple bootstrap document<00:17:21.160> so<00:17:21.339> you<00:17:21.400> can<00:17:21.579> follow<00:17:21.790> the<00:17:22.030> steps<00:17:22.089> and 00:17:22.620 --> 00:17:22.630 align:start position:0% document so you can follow the steps and 00:17:22.630 --> 00:17:28.439 align:start position:0% document so you can follow the steps and run<00:17:23.500> a<00:17:23.650> set<00:17:23.860> of<00:17:23.980> network<00:17:24.160> and<00:17:24.750> benchmark<00:17:25.750> it<00:17:27.449> we 00:17:28.439 --> 00:17:28.449 align:start position:0% run a set of network and benchmark it we 00:17:28.449 --> 00:17:32.000 align:start position:0% run a set of network and benchmark it we have<00:17:28.600> many<00:17:28.840> customs<00:17:29.460> yet<00:17:30.460> this<00:17:30.820> is<00:17:31.000> why<00:17:31.210> we<00:17:31.480> we 00:17:32.000 --> 00:17:32.010 align:start position:0% have many customs yet this is why we we 00:17:32.010 --> 00:17:35.070 align:start position:0% have many customs yet this is why we we we<00:17:33.010> need<00:17:33.220> such<00:17:33.460> high<00:17:33.730> throughput<00:17:34.120> such<00:17:34.900> high 00:17:35.070 --> 00:17:35.080 align:start position:0% we need such high throughput such high 00:17:35.080 --> 00:17:37.350 align:start position:0% we need such high throughput such high performance<00:17:35.620> because<00:17:36.370> our<00:17:36.640> cost 00:17:37.350 --> 00:17:37.360 align:start position:0% performance because our cost 00:17:37.360 --> 00:17:39.990 align:start position:0% performance because our cost must<00:17:37.540> include<00:17:37.870> like<00:17:38.590> China<00:17:39.490> banknote 00:17:39.990 --> 00:17:40.000 align:start position:0% must include like China banknote 00:17:40.000 --> 00:17:42.600 align:start position:0% must include like China banknote printing<00:17:40.240> and<00:17:40.720> minting<00:17:41.260> company<00:17:41.860> their 00:17:42.600 --> 00:17:42.610 align:start position:0% printing and minting company their 00:17:42.610 --> 00:17:45.620 align:start position:0% printing and minting company their product<00:17:43.330> literally<00:17:44.260> has<00:17:44.679> billions<00:17:45.250> of<00:17:45.400> users 00:17:45.620 --> 00:17:45.630 align:start position:0% product literally has billions of users 00:17:45.630 --> 00:17:51.370 align:start position:0% product literally has billions of users right<00:17:47.549> thank<00:17:48.549> you 00:17:51.370 --> 00:17:51.380 align:start position:0% 00:17:51.380 --> 00:17:57.900 align:start position:0% [Applause] 00:17:57.900 --> 00:17:57.910 align:start position:0% 00:17:57.910 --> 00:18:05.489 align:start position:0% [Music]