WEBVTT Kind: captions Language: en 00:00:00.540 --> 00:00:17.650 align:start position:0% [Music] 00:00:17.650 --> 00:00:17.660 align:start position:0% [Music] 00:00:17.660 --> 00:00:26.410 align:start position:0% [Music] hello<00:00:18.660> guys<00:00:18.870> nice<00:00:19.710> to<00:00:20.040> meet<00:00:20.220> you 00:00:26.410 --> 00:00:26.420 align:start position:0% 00:00:26.420 --> 00:00:29.570 align:start position:0% acronis<00:00:27.420> actually<00:00:27.900> is<00:00:27.960> not<00:00:28.260> a<00:00:28.619> start-up<00:00:29.279> as 00:00:29.570 --> 00:00:29.580 align:start position:0% acronis actually is not a start-up as 00:00:29.580 --> 00:00:33.160 align:start position:0% acronis actually is not a start-up as much<00:00:30.390> of<00:00:30.540> the<00:00:30.660> company's<00:00:31.110> presented<00:00:31.650> here 00:00:33.160 --> 00:00:33.170 align:start position:0% much of the company's presented here 00:00:33.170 --> 00:00:37.270 align:start position:0% much of the company's presented here with<00:00:34.309> Cronus's<00:00:35.309> really<00:00:35.879> big<00:00:36.390> company<00:00:36.870> with 00:00:37.270 --> 00:00:37.280 align:start position:0% with Cronus's really big company with 00:00:37.280 --> 00:00:40.790 align:start position:0% with Cronus's really big company with 800<00:00:38.280> some<00:00:38.400> place<00:00:38.640> in<00:00:39.150> more<00:00:39.510> than<00:00:39.660> 20<00:00:40.350> offices 00:00:40.790 --> 00:00:40.800 align:start position:0% 800 some place in more than 20 offices 00:00:40.800 --> 00:00:42.939 align:start position:0% 800 some place in more than 20 offices around<00:00:41.010> the<00:00:41.250> world 00:00:42.939 --> 00:00:42.949 align:start position:0% around the world 00:00:42.949 --> 00:00:45.890 align:start position:0% around the world and<00:00:43.949> millions<00:00:44.489> of<00:00:44.670> customers<00:00:44.910> and<00:00:45.540> business 00:00:45.890 --> 00:00:45.900 align:start position:0% and millions of customers and business 00:00:45.900 --> 00:00:48.009 align:start position:0% and millions of customers and business clients<00:00:46.410> though<00:00:46.650> it's<00:00:46.860> still<00:00:47.309> full<00:00:47.640> of 00:00:48.009 --> 00:00:48.019 align:start position:0% clients though it's still full of 00:00:48.019 --> 00:00:50.860 align:start position:0% clients though it's still full of entrepreneurial<00:00:49.019> entrepreneurial<00:00:49.949> spirit 00:00:50.860 --> 00:00:50.870 align:start position:0% entrepreneurial entrepreneurial spirit 00:00:50.870 --> 00:00:54.759 align:start position:0% entrepreneurial entrepreneurial spirit 20<00:00:51.870> is<00:00:51.930> well<00:00:52.170> known<00:00:52.470> as<00:00:53.309> a<00:00:53.370> provider<00:00:53.820> of<00:00:54.059> cloud 00:00:54.759 --> 00:00:54.769 align:start position:0% 20 is well known as a provider of cloud 00:00:54.769 --> 00:00:58.040 align:start position:0% 20 is well known as a provider of cloud and<00:00:56.030> on-premise<00:00:57.030> bakaba<00:00:57.510> disaster<00:00:57.960> recovery 00:00:58.040 --> 00:00:58.050 align:start position:0% and on-premise bakaba disaster recovery 00:00:58.050 --> 00:01:01.100 align:start position:0% and on-premise bakaba disaster recovery solutions<00:00:58.890> data<00:00:59.190> storage<00:00:59.820> file<00:01:00.540> sync<00:01:00.960> and 00:01:01.100 --> 00:01:01.110 align:start position:0% solutions data storage file sync and 00:01:01.110 --> 00:01:05.320 align:start position:0% solutions data storage file sync and share<00:01:01.170> solutions<00:01:02.180> of<00:01:03.180> course<00:01:03.989> not<00:01:04.379> all<00:01:04.680> there 00:01:05.320 --> 00:01:05.330 align:start position:0% share solutions of course not all there 00:01:05.330 --> 00:01:08.030 align:start position:0% share solutions of course not all there four<00:01:06.330> hundred<00:01:06.690> engineers<00:01:06.960> are<00:01:07.440> working<00:01:07.470> on 00:01:08.030 --> 00:01:08.040 align:start position:0% four hundred engineers are working on 00:01:08.040 --> 00:01:10.760 align:start position:0% four hundred engineers are working on the<00:01:08.340> blockchain<00:01:08.640> products<00:01:09.510> though<00:01:10.229> we<00:01:10.470> apply 00:01:10.760 --> 00:01:10.770 align:start position:0% the blockchain products though we apply 00:01:10.770 --> 00:01:13.430 align:start position:0% the blockchain products though we apply a<00:01:10.799> lot<00:01:11.070> of<00:01:11.250> efforts<00:01:11.940> in<00:01:12.120> this<00:01:12.270> direction<00:01:12.330> and<00:01:13.200> I 00:01:13.430 --> 00:01:13.440 align:start position:0% a lot of efforts in this direction and I 00:01:13.440 --> 00:01:16.390 align:start position:0% a lot of efforts in this direction and I would<00:01:13.560> like<00:01:13.740> to<00:01:13.770> share<00:01:14.100> with<00:01:14.280> you<00:01:14.520> our 00:01:16.390 --> 00:01:16.400 align:start position:0% would like to share with you our 00:01:16.400 --> 00:01:18.430 align:start position:0% would like to share with you our vision<00:01:17.400> to<00:01:17.640> tell<00:01:18.119> you<00:01:18.210> about<00:01:18.360> our 00:01:18.430 --> 00:01:18.440 align:start position:0% vision to tell you about our 00:01:18.440 --> 00:01:21.710 align:start position:0% vision to tell you about our achievements<00:01:19.440> use<00:01:19.620> cases<00:01:19.950> and<00:01:20.430> the<00:01:21.300> lessons 00:01:21.710 --> 00:01:21.720 align:start position:0% achievements use cases and the lessons 00:01:21.720 --> 00:01:24.250 align:start position:0% achievements use cases and the lessons you've<00:01:21.900> learned 00:01:24.250 --> 00:01:24.260 align:start position:0% 00:01:24.260 --> 00:01:28.790 align:start position:0% our<00:01:25.260> first<00:01:25.710> product<00:01:26.160> is<00:01:27.020> acronis<00:01:28.020> notary<00:01:28.500> it's 00:01:28.790 --> 00:01:28.800 align:start position:0% our first product is acronis notary it's 00:01:28.800 --> 00:01:31.940 align:start position:0% our first product is acronis notary it's a<00:01:29.220> it's<00:01:29.640> a<00:01:30.120> platform<00:01:30.750> that<00:01:30.960> allows<00:01:31.290> customers 00:01:31.940 --> 00:01:31.950 align:start position:0% a it's a platform that allows customers 00:01:31.950 --> 00:01:35.480 align:start position:0% a it's a platform that allows customers to<00:01:32.010> store<00:01:32.580> and<00:01:32.910> exchange<00:01:33.810> data<00:01:34.230> in<00:01:34.740> a<00:01:35.100> safe 00:01:35.480 --> 00:01:35.490 align:start position:0% to store and exchange data in a safe 00:01:35.490 --> 00:01:37.550 align:start position:0% to store and exchange data in a safe manner<00:01:35.820> a<00:01:36.420> bit<00:01:36.750> the<00:01:37.020> guarantee<00:01:37.530> of 00:01:37.550 --> 00:01:37.560 align:start position:0% manner a bit the guarantee of 00:01:37.560 --> 00:01:40.340 align:start position:0% manner a bit the guarantee of authenticity<00:01:38.220> and<00:01:39.150> integrity<00:01:39.360> of<00:01:39.810> this<00:01:40.050> data 00:01:40.340 --> 00:01:40.350 align:start position:0% authenticity and integrity of this data 00:01:40.350 --> 00:01:44.300 align:start position:0% authenticity and integrity of this data you<00:01:40.710> may<00:01:41.310> argue<00:01:41.730> that<00:01:42.380> the<00:01:43.380> mutability<00:01:43.800> probe 00:01:44.300 --> 00:01:44.310 align:start position:0% you may argue that the mutability probe 00:01:44.310 --> 00:01:46.040 align:start position:0% you may argue that the mutability probe that<00:01:44.550> the<00:01:44.730> immutability<00:01:45.150> property<00:01:45.840> of<00:01:45.900> the 00:01:46.040 --> 00:01:46.050 align:start position:0% that the immutability property of the 00:01:46.050 --> 00:01:49.850 align:start position:0% that the immutability property of the blockchain<00:01:46.290> is<00:01:46.890> not<00:01:47.160> in<00:01:48.120> use<00:01:48.510> but<00:01:48.990> what 00:01:49.850 --> 00:01:49.860 align:start position:0% blockchain is not in use but what 00:01:49.860 --> 00:01:52.580 align:start position:0% blockchain is not in use but what differs<00:01:50.310> a<00:01:50.550> whole<00:01:50.820> product<00:01:51.210> which<00:01:52.050> acronis 00:01:52.580 --> 00:01:52.590 align:start position:0% differs a whole product which acronis 00:01:52.590 --> 00:01:55.900 align:start position:0% differs a whole product which acronis notaries<00:01:53.160> and<00:01:53.400> the<00:01:53.610> feature<00:01:53.850> is<00:01:54.450> the<00:01:54.540> set<00:01:55.500> of 00:01:55.900 --> 00:01:55.910 align:start position:0% notaries and the feature is the set of 00:01:55.910 --> 00:01:59.080 align:start position:0% notaries and the feature is the set of interfaces<00:01:56.910> and 00:01:59.080 --> 00:01:59.090 align:start position:0% interfaces and 00:01:59.090 --> 00:02:01.700 align:start position:0% interfaces and features<00:02:00.090> that<00:02:00.300> allows<00:02:00.630> customers<00:02:01.290> to<00:02:01.350> solve 00:02:01.700 --> 00:02:01.710 align:start position:0% features that allows customers to solve 00:02:01.710 --> 00:02:03.920 align:start position:0% features that allows customers to solve their<00:02:01.950> problems<00:02:02.520> not<00:02:03.480> really<00:02:03.720> has<00:02:03.900> a 00:02:03.920 --> 00:02:03.930 align:start position:0% their problems not really has a 00:02:03.930 --> 00:02:06.220 align:start position:0% their problems not really has a combination<00:02:04.650> of<00:02:04.830> unique<00:02:05.159> features<00:02:05.190> such<00:02:05.850> as 00:02:06.220 --> 00:02:06.230 align:start position:0% combination of unique features such as 00:02:06.230 --> 00:02:10.309 align:start position:0% combination of unique features such as synchronization<00:02:07.459> between<00:02:08.459> nodes<00:02:09.330> advanced 00:02:10.309 --> 00:02:10.319 align:start position:0% synchronization between nodes advanced 00:02:10.319 --> 00:02:13.190 align:start position:0% synchronization between nodes advanced search<00:02:10.500> of<00:02:11.099> protected<00:02:11.730> metadata<00:02:12.540> built-in 00:02:13.190 --> 00:02:13.200 align:start position:0% search of protected metadata built-in 00:02:13.200 --> 00:02:15.920 align:start position:0% search of protected metadata built-in verification<00:02:13.920> of<00:02:14.010> stored<00:02:14.310> data<00:02:14.489> and<00:02:15.030> have<00:02:15.780> to 00:02:15.920 --> 00:02:15.930 align:start position:0% verification of stored data and have to 00:02:15.930 --> 00:02:18.140 align:start position:0% verification of stored data and have to put<00:02:16.140> algorithm<00:02:16.739> I<00:02:16.890> will<00:02:17.069> tell<00:02:17.400> you<00:02:17.610> in<00:02:18.000> ma 00:02:18.140 --> 00:02:18.150 align:start position:0% put algorithm I will tell you in ma 00:02:18.150 --> 00:02:24.910 align:start position:0% put algorithm I will tell you in ma details<00:02:18.540> about<00:02:19.290> it<00:02:19.560> later 00:02:24.910 --> 00:02:24.920 align:start position:0% 00:02:24.920 --> 00:02:28.709 align:start position:0% basically<00:02:26.060> the<00:02:27.060> blockchain<00:02:27.420> the<00:02:28.019> best<00:02:28.569> I<00:02:28.599> it 00:02:28.709 --> 00:02:28.719 align:start position:0% basically the blockchain the best I it 00:02:28.719 --> 00:02:31.580 align:start position:0% basically the blockchain the best I it for<00:02:28.989> cases<00:02:29.499> where<00:02:29.609> multiple<00:02:30.609> parties<00:02:31.150> and 00:02:31.580 --> 00:02:31.590 align:start position:0% for cases where multiple parties and 00:02:31.590 --> 00:02:33.869 align:start position:0% for cases where multiple parties and multiple<00:02:32.590> entities<00:02:32.889> involved<00:02:33.459> and 00:02:33.869 --> 00:02:33.879 align:start position:0% multiple entities involved and 00:02:33.879 --> 00:02:36.360 align:start position:0% multiple entities involved and especially<00:02:34.659> when<00:02:35.139> those<00:02:35.379> entities<00:02:35.859> do<00:02:36.219> not 00:02:36.360 --> 00:02:36.370 align:start position:0% especially when those entities do not 00:02:36.370 --> 00:02:38.039 align:start position:0% especially when those entities do not complete<00:02:36.790> the<00:02:36.819> trust<00:02:37.180> each<00:02:37.329> other<00:02:37.510> and<00:02:37.840> there 00:02:38.039 --> 00:02:38.049 align:start position:0% complete the trust each other and there 00:02:38.049 --> 00:02:40.099 align:start position:0% complete the trust each other and there is<00:02:38.139> no<00:02:38.290> a<00:02:38.319> trusted<00:02:38.859> intermediary 00:02:40.099 --> 00:02:40.109 align:start position:0% is no a trusted intermediary 00:02:40.109 --> 00:02:44.099 align:start position:0% is no a trusted intermediary that's<00:02:41.109> why<00:02:41.670> the<00:02:42.670> thing<00:02:42.939> that<00:02:43.180> our<00:02:43.389> solution 00:02:44.099 --> 00:02:44.109 align:start position:0% that's why the thing that our solution 00:02:44.109 --> 00:02:48.360 align:start position:0% that's why the thing that our solution is<00:02:44.319> best<00:02:44.799> used<00:02:45.340> for<00:02:45.549> a<00:02:46.439> consortium<00:02:47.439> that<00:02:47.799> needs 00:02:48.360 --> 00:02:48.370 align:start position:0% is best used for a consortium that needs 00:02:48.370 --> 00:02:51.509 align:start position:0% is best used for a consortium that needs to<00:02:48.790> exchange<00:02:49.629> data<00:02:49.719> and<00:02:50.319> sometimes<00:02:51.250> big 00:02:51.509 --> 00:02:51.519 align:start position:0% to exchange data and sometimes big 00:02:51.519 --> 00:02:54.240 align:start position:0% to exchange data and sometimes big chance<00:02:51.819> of<00:02:52.000> data<00:02:52.269> that<00:02:52.989> are<00:02:53.349> impractical<00:02:53.859> to 00:02:54.240 --> 00:02:54.250 align:start position:0% chance of data that are impractical to 00:02:54.250 --> 00:02:56.869 align:start position:0% chance of data that are impractical to store<00:02:54.700> in<00:02:54.969> a<00:02:55.209> blockchain 00:02:56.869 --> 00:02:56.879 align:start position:0% store in a blockchain 00:02:56.879 --> 00:03:00.270 align:start position:0% store in a blockchain you<00:02:57.879> may<00:02:58.060> argue<00:02:58.299> that<00:02:58.629> there<00:02:59.079> is<00:02:59.200> for<00:02:59.829> example 00:03:00.270 --> 00:03:00.280 align:start position:0% you may argue that there is for example 00:03:00.280 --> 00:03:04.589 align:start position:0% you may argue that there is for example I<00:03:00.430> PFS<00:03:01.000> for<00:03:01.299> that<00:03:01.480> right<00:03:02.340> but<00:03:03.340> it's<00:03:03.519> a<00:03:03.909> PFS<00:03:04.389> is 00:03:04.589 --> 00:03:04.599 align:start position:0% I PFS for that right but it's a PFS is 00:03:04.599 --> 00:03:06.170 align:start position:0% I PFS for that right but it's a PFS is good<00:03:04.810> to<00:03:05.019> share 00:03:06.170 --> 00:03:06.180 align:start position:0% good to share 00:03:06.180 --> 00:03:11.699 align:start position:0% good to share photos<00:03:07.180> of<00:03:07.599> your<00:03:07.870> dog<00:03:08.109> or<00:03:08.819> your<00:03:10.139> white<00:03:11.139> papers 00:03:11.699 --> 00:03:11.709 align:start position:0% photos of your dog or your white papers 00:03:11.709 --> 00:03:14.129 align:start position:0% photos of your dog or your white papers but<00:03:12.310> when<00:03:12.669> you<00:03:12.819> deal<00:03:13.030> with<00:03:13.060> medical<00:03:13.689> records 00:03:14.129 --> 00:03:14.139 align:start position:0% but when you deal with medical records 00:03:14.139 --> 00:03:16.949 align:start position:0% but when you deal with medical records and<00:03:14.379> personal<00:03:15.159> data<00:03:15.400> you<00:03:16.150> would<00:03:16.209> definitely 00:03:16.949 --> 00:03:16.959 align:start position:0% and personal data you would definitely 00:03:16.959 --> 00:03:20.819 align:start position:0% and personal data you would definitely prefer<00:03:17.469> to<00:03:18.719> to<00:03:19.719> do<00:03:19.840> with<00:03:20.049> something<00:03:20.409> more 00:03:20.819 --> 00:03:20.829 align:start position:0% prefer to to do with something more 00:03:20.829 --> 00:03:21.979 align:start position:0% prefer to to do with something more secure 00:03:21.979 --> 00:03:21.989 align:start position:0% secure 00:03:21.989 --> 00:03:25.289 align:start position:0% secure so<00:03:22.989> we<00:03:23.109> found<00:03:23.409> the<00:03:23.650> tower<00:03:23.889> product<00:03:24.579> works<00:03:25.000> well 00:03:25.289 --> 00:03:25.299 align:start position:0% so we found the tower product works well 00:03:25.299 --> 00:03:29.069 align:start position:0% so we found the tower product works well with<00:03:25.919> consortiums<00:03:26.919> where<00:03:27.389> data<00:03:28.389> is<00:03:28.810> shared 00:03:29.069 --> 00:03:29.079 align:start position:0% with consortiums where data is shared 00:03:29.079 --> 00:03:35.899 align:start position:0% with consortiums where data is shared between<00:03:29.319> the<00:03:29.620> parties 00:03:35.899 --> 00:03:35.909 align:start position:0% 00:03:35.909 --> 00:03:39.390 align:start position:0% let<00:03:36.909> me<00:03:37.120> say<00:03:37.299> few<00:03:37.540> words<00:03:37.569> about<00:03:38.280> features<00:03:39.280> of 00:03:39.390 --> 00:03:39.400 align:start position:0% let me say few words about features of 00:03:39.400 --> 00:03:42.449 align:start position:0% let me say few words about features of the<00:03:39.489> product<00:03:39.930> first<00:03:40.930> the<00:03:41.470> certificate<00:03:42.250> of 00:03:42.449 --> 00:03:42.459 align:start position:0% the product first the certificate of 00:03:42.459 --> 00:03:45.110 align:start position:0% the product first the certificate of course<00:03:43.239> when<00:03:44.169> you 00:03:45.110 --> 00:03:45.120 align:start position:0% course when you 00:03:45.120 --> 00:03:49.969 align:start position:0% course when you anchor<00:03:46.120> your<00:03:46.919> file<00:03:47.919> in 00:03:49.969 --> 00:03:49.979 align:start position:0% anchor your file in 00:03:49.979 --> 00:03:54.119 align:start position:0% anchor your file in in<00:03:50.979> a<00:03:51.449> fingerprint<00:03:52.449> of<00:03:52.629> your<00:03:52.930> data<00:03:53.169> in<00:03:53.620> in<00:03:53.979> the 00:03:54.119 --> 00:03:54.129 align:start position:0% in a fingerprint of your data in in the 00:03:54.129 --> 00:03:55.249 align:start position:0% in a fingerprint of your data in in the blockchain 00:03:55.249 --> 00:03:55.259 align:start position:0% blockchain 00:03:55.259 --> 00:03:58.289 align:start position:0% blockchain it's<00:03:56.259> not<00:03:56.500> it's<00:03:57.400> not<00:03:57.459> a<00:03:57.609> new<00:03:57.849> feature<00:03:58.120> of 00:03:58.289 --> 00:03:58.299 align:start position:0% it's not it's not a new feature of 00:03:58.299 --> 00:04:00.240 align:start position:0% it's not it's not a new feature of course<00:03:58.509> every<00:03:58.780> one<00:03:59.229> of<00:03:59.379> you<00:03:59.500> knows<00:03:59.709> about<00:03:59.979> it 00:04:00.240 --> 00:04:00.250 align:start position:0% course every one of you knows about it 00:04:00.250 --> 00:04:03.770 align:start position:0% course every one of you knows about it but<00:04:00.519> what<00:04:01.859> differs<00:04:02.859> our 00:04:03.770 --> 00:04:03.780 align:start position:0% but what differs our 00:04:03.780 --> 00:04:07.319 align:start position:0% but what differs our certificate<00:04:04.780> our<00:04:04.989> products<00:04:05.620> our<00:04:06.400> note<00:04:07.180> is 00:04:07.319 --> 00:04:07.329 align:start position:0% certificate our products our note is 00:04:07.329 --> 00:04:09.089 align:start position:0% certificate our products our note is written<00:04:07.449> authorization<00:04:08.169> certificate<00:04:08.769> allows 00:04:09.089 --> 00:04:09.099 align:start position:0% written authorization certificate allows 00:04:09.099 --> 00:04:11.849 align:start position:0% written authorization certificate allows you<00:04:09.370> to<00:04:09.609> verify<00:04:09.790> authenticity<00:04:10.299> of<00:04:10.930> your<00:04:11.590> file 00:04:11.849 --> 00:04:11.859 align:start position:0% you to verify authenticity of your file 00:04:11.859 --> 00:04:14.670 align:start position:0% you to verify authenticity of your file you're<00:04:12.250> safe<00:04:12.519> by<00:04:13.030> well<00:04:13.750> provide<00:04:14.139> you'd<00:04:14.409> be 00:04:14.670 --> 00:04:14.680 align:start position:0% you're safe by well provide you'd be 00:04:14.680 --> 00:04:16.379 align:start position:0% you're safe by well provide you'd be providing<00:04:15.189> you<00:04:15.370> with<00:04:15.400> all<00:04:15.790> the<00:04:16.000> necessary 00:04:16.379 --> 00:04:16.389 align:start position:0% providing you with all the necessary 00:04:16.389 --> 00:04:18.839 align:start position:0% providing you with all the necessary information<00:04:16.479> for<00:04:17.169> this<00:04:17.320> and<00:04:17.530> the<00:04:18.250> certificate 00:04:18.839 --> 00:04:18.849 align:start position:0% information for this and the certificate 00:04:18.849 --> 00:04:20.219 align:start position:0% information for this and the certificate contains<00:04:19.269> all<00:04:19.509> the<00:04:19.539> necessary<00:04:19.690> information 00:04:20.219 --> 00:04:20.229 align:start position:0% contains all the necessary information 00:04:20.229 --> 00:04:24.029 align:start position:0% contains all the necessary information for<00:04:20.889> this<00:04:21.419> and<00:04:22.419> you<00:04:23.020> can<00:04:23.050> prove<00:04:23.710> authenticity 00:04:24.029 --> 00:04:24.039 align:start position:0% for this and you can prove authenticity 00:04:24.039 --> 00:04:26.939 align:start position:0% for this and you can prove authenticity and<00:04:24.759> integrity<00:04:25.150> of<00:04:25.630> the<00:04:25.780> data<00:04:25.960> even<00:04:26.590> though 00:04:26.939 --> 00:04:26.949 align:start position:0% and integrity of the data even though 00:04:26.949 --> 00:04:29.520 align:start position:0% and integrity of the data even though you<00:04:27.009> would<00:04:27.940> have<00:04:28.270> stopped<00:04:28.750> using<00:04:29.110> our 00:04:29.520 --> 00:04:29.530 align:start position:0% you would have stopped using our 00:04:29.530 --> 00:04:31.200 align:start position:0% you would have stopped using our applications<00:04:30.250> so<00:04:30.430> it<00:04:30.520> could<00:04:30.969> be<00:04:31.000> done 00:04:31.200 --> 00:04:31.210 align:start position:0% applications so it could be done 00:04:31.210 --> 00:04:33.839 align:start position:0% applications so it could be done independently<00:04:31.770> the<00:04:32.770> verification<00:04:33.430> could<00:04:33.699> be 00:04:33.839 --> 00:04:33.849 align:start position:0% independently the verification could be 00:04:33.849 --> 00:04:37.439 align:start position:0% independently the verification could be done<00:04:34.030> manually<00:04:34.509> or<00:04:34.900> by<00:04:35.199> using<00:04:35.969> the<00:04:36.969> API<00:04:37.389> you 00:04:37.439 --> 00:04:37.449 align:start position:0% done manually or by using the API you 00:04:37.449 --> 00:04:38.810 align:start position:0% done manually or by using the API you provide<00:04:37.960> you 00:04:38.810 --> 00:04:38.820 align:start position:0% provide you 00:04:38.820 --> 00:04:41.610 align:start position:0% provide you verification<00:04:39.820> can<00:04:40.060> also<00:04:40.330> could<00:04:40.930> also<00:04:41.110> be<00:04:41.409> done 00:04:41.610 --> 00:04:41.620 align:start position:0% verification can also could also be done 00:04:41.620 --> 00:04:42.360 align:start position:0% verification can also could also be done in 00:04:42.360 --> 00:04:42.370 align:start position:0% in 00:04:42.370 --> 00:04:47.270 align:start position:0% in dently<00:04:42.699> by<00:04:43.210> a<00:04:43.240> third<00:04:43.720> parties 00:04:47.270 --> 00:04:47.280 align:start position:0% 00:04:47.280 --> 00:04:49.159 align:start position:0% search 00:04:49.159 --> 00:04:49.169 align:start position:0% search 00:04:49.169 --> 00:04:52.219 align:start position:0% search another<00:04:50.169> necessary<00:04:50.770> feature<00:04:51.070> is<00:04:51.639> the 00:04:52.219 --> 00:04:52.229 align:start position:0% another necessary feature is the 00:04:52.229 --> 00:04:55.460 align:start position:0% another necessary feature is the research<00:04:53.229> as<00:04:54.190> you<00:04:54.250> know<00:04:54.639> it's 00:04:55.460 --> 00:04:55.470 align:start position:0% research as you know it's 00:04:55.470 --> 00:04:59.070 align:start position:0% research as you know it's blockchain<00:04:56.470> and<00:04:57.040> athyrium<00:04:57.910> itself<00:04:58.270> are<00:04:58.930> not 00:04:59.070 --> 00:04:59.080 align:start position:0% blockchain and athyrium itself are not 00:04:59.080 --> 00:05:01.740 align:start position:0% blockchain and athyrium itself are not very<00:04:59.260> good<00:04:59.560> for<00:04:59.590> this<00:04:59.949> so<00:05:00.880> we<00:05:01.180> provide<00:05:01.570> this 00:05:01.740 --> 00:05:01.750 align:start position:0% very good for this so we provide this 00:05:01.750 --> 00:05:07.460 align:start position:0% very good for this so we provide this feature<00:05:02.229> for<00:05:02.470> you<00:05:02.560> you<00:05:02.770> can<00:05:03.010> you<00:05:03.940> can 00:05:07.460 --> 00:05:07.470 align:start position:0% 00:05:07.470 --> 00:05:11.520 align:start position:0% sometimes<00:05:08.470> you<00:05:08.650> need<00:05:08.800> to<00:05:09.340> know<00:05:09.850> who<00:05:09.880> and<00:05:10.530> when 00:05:11.520 --> 00:05:11.530 align:start position:0% sometimes you need to know who and when 00:05:11.530 --> 00:05:13.590 align:start position:0% sometimes you need to know who and when applauded<00:05:12.130> the<00:05:12.250> file<00:05:12.520> to<00:05:12.760> the<00:05:12.880> storage<00:05:13.180> as 00:05:13.590 --> 00:05:13.600 align:start position:0% applauded the file to the storage as 00:05:13.600 --> 00:05:16.379 align:start position:0% applauded the file to the storage as well<00:05:13.810> as<00:05:14.260> you<00:05:14.949> need<00:05:15.160> to<00:05:15.340> filter<00:05:15.580> your<00:05:15.729> data<00:05:15.880> by 00:05:16.379 --> 00:05:16.389 align:start position:0% well as you need to filter your data by 00:05:16.389 --> 00:05:20.370 align:start position:0% well as you need to filter your data by date<00:05:17.320> time<00:05:17.770> and<00:05:18.130> status<00:05:18.789> for<00:05:18.970> example<00:05:19.479> we 00:05:20.370 --> 00:05:20.380 align:start position:0% date time and status for example we 00:05:20.380 --> 00:05:22.590 align:start position:0% date time and status for example we developed<00:05:20.830> this<00:05:20.919> convenient<00:05:21.460> user<00:05:21.880> interface 00:05:22.590 --> 00:05:22.600 align:start position:0% developed this convenient user interface 00:05:22.600 --> 00:05:30.020 align:start position:0% developed this convenient user interface and<00:05:23.020> rest<00:05:23.289> rest<00:05:23.860> api<00:05:24.400> for<00:05:24.520> this 00:05:30.020 --> 00:05:30.030 align:start position:0% 00:05:30.030 --> 00:05:33.439 align:start position:0% another<00:05:31.030> feature<00:05:31.270> is<00:05:31.770> synchronization 00:05:33.439 --> 00:05:33.449 align:start position:0% another feature is synchronization 00:05:33.449 --> 00:05:36.680 align:start position:0% another feature is synchronization d<00:05:34.449> found<00:05:34.750> that<00:05:35.050> in<00:05:35.289> many<00:05:35.470> cases<00:05:35.590> especially 00:05:36.680 --> 00:05:36.690 align:start position:0% d found that in many cases especially 00:05:36.690 --> 00:05:40.650 align:start position:0% d found that in many cases especially when<00:05:37.800> private<00:05:38.800> block<00:05:39.460> chains<00:05:39.760> i<00:05:40.000> used<00:05:40.330> a 00:05:40.650 --> 00:05:40.660 align:start position:0% when private block chains i used a 00:05:40.660 --> 00:05:44.990 align:start position:0% when private block chains i used a party's<00:05:41.560> wants<00:05:42.039> to<00:05:42.190> have<00:05:42.490> this<00:05:43.620> sociability 00:05:44.990 --> 00:05:45.000 align:start position:0% party's wants to have this sociability 00:05:45.000 --> 00:05:48.860 align:start position:0% party's wants to have this sociability on<00:05:46.000> premises<00:05:46.630> on<00:05:46.900> their<00:05:47.380> own<00:05:47.680> they're<00:05:48.039> not 00:05:48.860 --> 00:05:48.870 align:start position:0% on premises on their own they're not 00:05:48.870 --> 00:05:50.960 align:start position:0% on premises on their own they're not that's<00:05:49.870> why 00:05:50.960 --> 00:05:50.970 align:start position:0% that's why 00:05:50.970 --> 00:05:54.120 align:start position:0% that's why that's<00:05:51.970> why<00:05:52.120> we<00:05:52.510> built<00:05:52.750> this<00:05:53.050> feature<00:05:53.710> that 00:05:54.120 --> 00:05:54.130 align:start position:0% that's why we built this feature that 00:05:54.130 --> 00:05:58.100 align:start position:0% that's why we built this feature that allows<00:05:54.539> users<00:05:55.539> to<00:05:55.570> synchronize<00:05:56.760> metadata 00:05:58.100 --> 00:05:58.110 align:start position:0% allows users to synchronize metadata 00:05:58.110 --> 00:06:00.870 align:start position:0% allows users to synchronize metadata metadata<00:05:59.110> using<00:05:59.919> etherium<00:06:00.550> blockchain 00:06:00.870 --> 00:06:00.880 align:start position:0% metadata using etherium blockchain 00:06:00.880 --> 00:06:08.610 align:start position:0% metadata using etherium blockchain mechanisms 00:06:08.610 --> 00:06:08.620 align:start position:0% 00:06:08.620 --> 00:06:11.980 align:start position:0% optimization<00:06:09.620> it's<00:06:09.980> also<00:06:10.850> not<00:06:11.120> a<00:06:11.420> big<00:06:11.720> news 00:06:11.980 --> 00:06:11.990 align:start position:0% optimization it's also not a big news 00:06:11.990 --> 00:06:14.320 align:start position:0% optimization it's also not a big news for<00:06:12.260> you<00:06:12.350> that<00:06:12.560> block<00:06:12.980> chains<00:06:13.310> have<00:06:13.700> a<00:06:13.910> limited 00:06:14.320 --> 00:06:14.330 align:start position:0% for you that block chains have a limited 00:06:14.330 --> 00:06:18.250 align:start position:0% for you that block chains have a limited throughput<00:06:14.840> and<00:06:15.110> in<00:06:15.860> case<00:06:16.130> when<00:06:17.020> you<00:06:18.020> need<00:06:18.230> to 00:06:18.250 --> 00:06:18.260 align:start position:0% throughput and in case when you need to 00:06:18.260 --> 00:06:20.950 align:start position:0% throughput and in case when you need to notarize<00:06:18.950> a<00:06:19.340> big<00:06:19.700> amount<00:06:20.210> of<00:06:20.540> files<00:06:20.720> like 00:06:20.950 --> 00:06:20.960 align:start position:0% notarize a big amount of files like 00:06:20.960 --> 00:06:23.530 align:start position:0% notarize a big amount of files like thousands<00:06:21.500> or<00:06:21.620> millions<00:06:22.010> of<00:06:22.130> files<00:06:22.340> as<00:06:22.670> we<00:06:23.330> did 00:06:23.530 --> 00:06:23.540 align:start position:0% thousands or millions of files as we did 00:06:23.540 --> 00:06:26.190 align:start position:0% thousands or millions of files as we did in<00:06:24.050> our<00:06:24.440> use<00:06:24.740> cases 00:06:26.190 --> 00:06:26.200 align:start position:0% in our use cases 00:06:26.200 --> 00:06:27.720 align:start position:0% in our use cases this 00:06:27.720 --> 00:06:27.730 align:start position:0% this 00:06:27.730 --> 00:06:31.180 align:start position:0% this limit<00:06:28.730> should<00:06:28.760> not<00:06:29.120> stop<00:06:29.480> you<00:06:29.860> moreover<00:06:30.860> it 00:06:31.180 --> 00:06:31.190 align:start position:0% limit should not stop you moreover it 00:06:31.190 --> 00:06:33.400 align:start position:0% limit should not stop you moreover it would<00:06:31.400> be<00:06:31.550> very<00:06:31.670> costly<00:06:32.030> with<00:06:32.780> public<00:06:33.260> block 00:06:33.400 --> 00:06:33.410 align:start position:0% would be very costly with public block 00:06:33.410 --> 00:06:36.010 align:start position:0% would be very costly with public block chains<00:06:33.680> if<00:06:33.950> you<00:06:34.310> would<00:06:34.550> not<00:06:34.850> arise<00:06:35.120> each<00:06:35.600> file 00:06:36.010 --> 00:06:36.020 align:start position:0% chains if you would not arise each file 00:06:36.020 --> 00:06:39.070 align:start position:0% chains if you would not arise each file in<00:06:36.320> the<00:06:36.710> blockchain<00:06:37.450> that's<00:06:38.450> why<00:06:38.630> we<00:06:38.690> use 00:06:39.070 --> 00:06:39.080 align:start position:0% in the blockchain that's why we use 00:06:39.080 --> 00:06:42.220 align:start position:0% in the blockchain that's why we use Patricia<00:06:39.800> a<00:06:39.950> miracle<00:06:40.340> tree<00:06:40.550> structure<00:06:41.230> with 00:06:42.220 --> 00:06:42.230 align:start position:0% Patricia a miracle tree structure with 00:06:42.230 --> 00:06:45.340 align:start position:0% Patricia a miracle tree structure with very<00:06:42.800> variable<00:06:43.510> chunk<00:06:44.510> size<00:06:44.690> to<00:06:45.020> solve<00:06:45.230> this 00:06:45.340 --> 00:06:45.350 align:start position:0% very variable chunk size to solve this 00:06:45.350 --> 00:06:53.280 align:start position:0% very variable chunk size to solve this problem 00:06:53.280 --> 00:06:53.290 align:start position:0% 00:06:53.290 --> 00:06:56.980 align:start position:0% so<00:06:54.290> how<00:06:54.770> does<00:06:55.250> it<00:06:55.520> work<00:06:55.760> there<00:06:56.360> have<00:06:56.510> two<00:06:56.780> basic 00:06:56.980 --> 00:06:56.990 align:start position:0% so how does it work there have two basic 00:06:56.990 --> 00:06:59.710 align:start position:0% so how does it work there have two basic scenarios<00:06:57.650> the<00:06:57.860> first<00:06:58.100> one<00:06:58.430> the<00:06:59.240> second<00:06:59.660> one 00:06:59.710 --> 00:06:59.720 align:start position:0% scenarios the first one the second one 00:06:59.720 --> 00:07:04.140 align:start position:0% scenarios the first one the second one is<00:07:00.440> when<00:07:00.860> you<00:07:01.160> upload<00:07:01.730> a<00:07:02.210> file<00:07:02.600> in<00:07:02.990> the<00:07:03.320> storage 00:07:04.140 --> 00:07:04.150 align:start position:0% is when you upload a file in the storage 00:07:04.150 --> 00:07:07.600 align:start position:0% is when you upload a file in the storage the<00:07:05.150> storage<00:07:05.450> sense<00:07:05.870> events<00:07:06.650> to<00:07:06.830> the<00:07:06.980> acronis 00:07:07.600 --> 00:07:07.610 align:start position:0% the storage sense events to the acronis 00:07:07.610 --> 00:07:10.860 align:start position:0% the storage sense events to the acronis notary<00:07:08.480> which<00:07:09.320> in<00:07:09.710> terms 00:07:10.860 --> 00:07:10.870 align:start position:0% notary which in terms 00:07:10.870 --> 00:07:12.850 align:start position:0% notary which in terms communicates<00:07:11.870> with<00:07:12.110> a<00:07:12.170> theory<00:07:12.440> on<00:07:12.560> blockchain 00:07:12.850 --> 00:07:12.860 align:start position:0% communicates with a theory on blockchain 00:07:12.860 --> 00:07:15.750 align:start position:0% communicates with a theory on blockchain and<00:07:13.490> receives 00:07:15.750 --> 00:07:15.760 align:start position:0% and receives 00:07:15.760 --> 00:07:18.910 align:start position:0% and receives data<00:07:16.760> from<00:07:17.090> the<00:07:17.180> tree<00:07:17.330> on<00:07:17.450> blockchain<00:07:17.920> proving 00:07:18.910 --> 00:07:18.920 align:start position:0% data from the tree on blockchain proving 00:07:18.920 --> 00:07:21.120 align:start position:0% data from the tree on blockchain proving that<00:07:19.130> the<00:07:19.340> data<00:07:19.520> was<00:07:19.670> recorded 00:07:21.120 --> 00:07:21.130 align:start position:0% that the data was recorded 00:07:21.130 --> 00:07:25.870 align:start position:0% that the data was recorded then<00:07:22.270> this<00:07:23.270> metadata<00:07:23.930> is<00:07:24.410> stored<00:07:24.440> in<00:07:25.130> acronis 00:07:25.870 --> 00:07:25.880 align:start position:0% then this metadata is stored in acronis 00:07:25.880 --> 00:07:27.490 align:start position:0% then this metadata is stored in acronis not<00:07:26.090> remade<00:07:26.420> a<00:07:26.450> data<00:07:26.750> storage<00:07:27.110> and 00:07:27.490 --> 00:07:27.500 align:start position:0% not remade a data storage and 00:07:27.500 --> 00:07:30.690 align:start position:0% not remade a data storage and distributed<00:07:28.340> between<00:07:28.960> the<00:07:29.960> nodes 00:07:30.690 --> 00:07:30.700 align:start position:0% distributed between the nodes 00:07:30.700 --> 00:07:34.330 align:start position:0% distributed between the nodes the<00:07:31.700> second<00:07:32.090> scenario<00:07:32.240> is<00:07:32.690> you<00:07:33.230> can<00:07:33.530> use<00:07:33.950> this 00:07:34.330 --> 00:07:34.340 align:start position:0% the second scenario is you can use this 00:07:34.340 --> 00:07:37.270 align:start position:0% the second scenario is you can use this product<00:07:34.820> with<00:07:35.390> your<00:07:35.990> own<00:07:36.110> application<00:07:36.860> not<00:07:37.070> on 00:07:37.270 --> 00:07:37.280 align:start position:0% product with your own application not on 00:07:37.280 --> 00:07:39.490 align:start position:0% product with your own application not on it<00:07:37.940> is<00:07:38.120> not<00:07:38.300> necessary<00:07:38.450> to<00:07:38.720> you<00:07:38.900> to<00:07:39.200> use<00:07:39.350> it 00:07:39.490 --> 00:07:39.500 align:start position:0% it is not necessary to you to use it 00:07:39.500 --> 00:07:42.220 align:start position:0% it is not necessary to you to use it with<00:07:39.740> the<00:07:40.010> storage<00:07:40.430> you<00:07:40.670> can<00:07:40.700> use<00:07:41.180> any<00:07:41.660> your 00:07:42.220 --> 00:07:42.230 align:start position:0% with the storage you can use any your 00:07:42.230 --> 00:07:44.130 align:start position:0% with the storage you can use any your application<00:07:42.860> and<00:07:43.070> send 00:07:44.130 --> 00:07:44.140 align:start position:0% application and send 00:07:44.140 --> 00:07:47.520 align:start position:0% application and send events<00:07:45.140> why<00:07:45.380> rest<00:07:45.800> api<00:07:46.190> or 00:07:47.520 --> 00:07:47.530 align:start position:0% events why rest api or 00:07:47.530 --> 00:07:52.200 align:start position:0% events why rest api or mpq<00:07:48.530> to<00:07:48.980> the<00:07:49.100> notary<00:07:49.400> storage<00:07:49.880> then<00:07:50.720> you<00:07:51.440> can 00:07:52.200 --> 00:07:52.210 align:start position:0% mpq to the notary storage then you can 00:07:52.210 --> 00:07:56.350 align:start position:0% mpq to the notary storage then you can search<00:07:53.210> and<00:07:53.800> send<00:07:54.800> purification<00:07:55.610> requests<00:07:56.120> or 00:07:56.350 --> 00:07:56.360 align:start position:0% search and send purification requests or 00:07:56.360 --> 00:07:57.900 align:start position:0% search and send purification requests or Krishna<00:07:56.750> tree<00:07:57.050> and 00:07:57.900 --> 00:07:57.910 align:start position:0% Krishna tree and 00:07:57.910 --> 00:08:05.680 align:start position:0% Krishna tree and do<00:07:58.910> the<00:07:59.120> blockchain 00:08:05.680 --> 00:08:05.690 align:start position:0% 00:08:05.690 --> 00:08:08.409 align:start position:0% how<00:08:06.690> a<00:08:06.720> theorem<00:08:07.199> is<00:08:07.350> used<00:08:07.620> here 00:08:08.409 --> 00:08:08.419 align:start position:0% how a theorem is used here 00:08:08.419 --> 00:08:12.490 align:start position:0% how a theorem is used here we<00:08:09.419> use<00:08:09.870> Marco<00:08:10.740> tracks<00:08:11.039> for<00:08:11.520> data<00:08:11.819> protection 00:08:12.490 --> 00:08:12.500 align:start position:0% we use Marco tracks for data protection 00:08:12.500 --> 00:08:15.710 align:start position:0% we use Marco tracks for data protection events<00:08:13.500> for<00:08:14.460> synchronization<00:08:14.940> miracle 00:08:15.710 --> 00:08:15.720 align:start position:0% events for synchronization miracle 00:08:15.720 --> 00:08:18.469 align:start position:0% events for synchronization miracle Patricia<00:08:16.319> tea<00:08:16.560> for<00:08:16.979> optimization<00:08:17.610> of<00:08:18.120> stored 00:08:18.469 --> 00:08:18.479 align:start position:0% Patricia tea for optimization of stored 00:08:18.479 --> 00:08:21.379 align:start position:0% Patricia tea for optimization of stored data<00:08:18.690> and<00:08:19.139> proof<00:08:20.009> of<00:08:20.160> work<00:08:20.460> in<00:08:20.819> the<00:08:21.150> public 00:08:21.379 --> 00:08:21.389 align:start position:0% data and proof of work in the public 00:08:21.389 --> 00:08:25.270 align:start position:0% data and proof of work in the public blog<00:08:21.870> chains<00:08:22.199> and<00:08:22.500> proof<00:08:23.099> of<00:08:23.280> authority<00:08:24.030> in 00:08:25.270 --> 00:08:25.280 align:start position:0% blog chains and proof of authority in 00:08:25.280 --> 00:08:31.360 align:start position:0% blog chains and proof of authority in private<00:08:26.280> block<00:08:26.460> chains 00:08:31.360 --> 00:08:31.370 align:start position:0% 00:08:31.370 --> 00:08:34.760 align:start position:0% acronis<00:08:32.370> uses<00:08:32.849> the<00:08:33.000> film<00:08:33.330> and<00:08:33.599> a<00:08:33.899> score<00:08:34.200> parity 00:08:34.760 --> 00:08:34.770 align:start position:0% acronis uses the film and a score parity 00:08:34.770 --> 00:08:37.279 align:start position:0% acronis uses the film and a score parity at<00:08:34.890> the<00:08:35.099> main<00:08:35.279> block<00:08:35.550> chain<00:08:35.760> components<00:08:36.479> the 00:08:37.279 --> 00:08:37.289 align:start position:0% at the main block chain components the 00:08:37.289 --> 00:08:39.440 align:start position:0% at the main block chain components the product<00:08:37.709> is<00:08:37.800> built<00:08:38.070> using<00:08:38.450> robust 00:08:39.440 --> 00:08:39.450 align:start position:0% product is built using robust 00:08:39.450 --> 00:08:42.500 align:start position:0% product is built using robust microservice<00:08:40.409> architecture<00:08:41.399> product<00:08:42.240> can<00:08:42.479> be 00:08:42.500 --> 00:08:42.510 align:start position:0% microservice architecture product can be 00:08:42.510 --> 00:08:45.500 align:start position:0% microservice architecture product can be deployed<00:08:42.930> in<00:08:43.860> the<00:08:44.310> cloud<00:08:44.700> in<00:08:45.120> the<00:08:45.149> acronis 00:08:45.500 --> 00:08:45.510 align:start position:0% deployed in the cloud in the acronis 00:08:45.510 --> 00:08:52.180 align:start position:0% deployed in the cloud in the acronis cloud<00:08:46.050> or<00:08:46.500> in<00:08:47.190> asia<00:08:47.459> or<00:08:47.880> on-premises 00:08:52.180 --> 00:08:52.190 align:start position:0% 00:08:52.190 --> 00:08:55.940 align:start position:0% let<00:08:53.190> me<00:08:53.550> say<00:08:54.060> a<00:08:54.089> few<00:08:54.120> words<00:08:54.330> about<00:08:54.830> use<00:08:55.830> cases 00:08:55.940 --> 00:08:55.950 align:start position:0% let me say a few words about use cases 00:08:55.950 --> 00:08:58.840 align:start position:0% let me say a few words about use cases some<00:08:56.790> of<00:08:56.940> them<00:08:57.120> are<00:08:57.330> already<00:08:57.720> in<00:08:58.320> production 00:08:58.840 --> 00:08:58.850 align:start position:0% some of them are already in production 00:08:58.850 --> 00:09:02.780 align:start position:0% some of them are already in production in<00:08:59.850> the<00:08:59.970> production<00:09:00.330> stage<00:09:00.779> some<00:09:01.230> still<00:09:01.649> in<00:09:01.890> in 00:09:02.780 --> 00:09:02.790 align:start position:0% in the production stage some still in in 00:09:02.790 --> 00:09:06.500 align:start position:0% in the production stage some still in in a<00:09:02.910> pilot<00:09:03.270> stage<00:09:03.800> first<00:09:04.800> storage<00:09:05.330> we<00:09:06.330> found 00:09:06.500 --> 00:09:06.510 align:start position:0% a pilot stage first storage we found 00:09:06.510 --> 00:09:07.970 align:start position:0% a pilot stage first storage we found that<00:09:06.690> there<00:09:06.930> are<00:09:07.050> several<00:09:07.200> very<00:09:07.800> good 00:09:07.970 --> 00:09:07.980 align:start position:0% that there are several very good 00:09:07.980 --> 00:09:11.360 align:start position:0% that there are several very good scenarios<00:09:08.490> for<00:09:08.790> it<00:09:09.079> for<00:09:10.079> this<00:09:10.170> usage<00:09:10.589> for 00:09:11.360 --> 00:09:11.370 align:start position:0% scenarios for it for this usage for 00:09:11.370 --> 00:09:14.569 align:start position:0% scenarios for it for this usage for example<00:09:11.910> it<00:09:12.120> could<00:09:12.779> be<00:09:13.020> used<00:09:13.260> for<00:09:13.579> long-term 00:09:14.569 --> 00:09:14.579 align:start position:0% example it could be used for long-term 00:09:14.579 --> 00:09:17.480 align:start position:0% example it could be used for long-term archiving<00:09:15.200> especially<00:09:16.200> in<00:09:16.440> the<00:09:16.920> industries 00:09:17.480 --> 00:09:17.490 align:start position:0% archiving especially in the industries 00:09:17.490 --> 00:09:19.880 align:start position:0% archiving especially in the industries in<00:09:17.760> the<00:09:18.029> industries<00:09:18.420> which<00:09:18.690> are<00:09:18.930> heavily 00:09:19.880 --> 00:09:19.890 align:start position:0% in the industries which are heavily 00:09:19.890 --> 00:09:21.940 align:start position:0% in the industries which are heavily regulated 00:09:21.940 --> 00:09:21.950 align:start position:0% regulated 00:09:21.950 --> 00:09:26.139 align:start position:0% regulated banking<00:09:22.950> industry<00:09:23.459> health<00:09:23.910> care 00:09:26.139 --> 00:09:26.149 align:start position:0% banking industry health care 00:09:26.149 --> 00:09:30.639 align:start position:0% banking industry health care it<00:09:27.149> also<00:09:27.810> could<00:09:28.350> be<00:09:28.410> used<00:09:28.920> for<00:09:29.450> for 00:09:30.639 --> 00:09:30.649 align:start position:0% it also could be used for for 00:09:30.649 --> 00:09:32.889 align:start position:0% it also could be used for for notarization<00:09:31.649> of 00:09:32.889 --> 00:09:32.899 align:start position:0% notarization of 00:09:32.899 --> 00:09:40.000 align:start position:0% notarization of footage<00:09:33.899> from<00:09:34.200> security<00:09:34.890> CCTV<00:09:35.070> cameras 00:09:40.000 --> 00:09:40.010 align:start position:0% 00:09:40.010 --> 00:09:43.400 align:start position:0% another<00:09:41.010> use<00:09:41.279> case<00:09:41.399> which<00:09:42.240> is<00:09:42.630> already<00:09:43.140> in 00:09:43.400 --> 00:09:43.410 align:start position:0% another use case which is already in 00:09:43.410 --> 00:09:45.430 align:start position:0% another use case which is already in production<00:09:43.589> mode 00:09:45.430 --> 00:09:45.440 align:start position:0% production mode 00:09:45.440 --> 00:09:48.740 align:start position:0% production mode open<00:09:46.440> pixel<00:09:46.860> is<00:09:47.070> an<00:09:47.430> open<00:09:47.880> source<00:09:48.120> tracking 00:09:48.740 --> 00:09:48.750 align:start position:0% open pixel is an open source tracking 00:09:48.750 --> 00:09:51.190 align:start position:0% open pixel is an open source tracking software<00:09:48.930> for<00:09:49.560> mobile<00:09:49.920> advertisement 00:09:51.190 --> 00:09:51.200 align:start position:0% software for mobile advertisement 00:09:51.200 --> 00:09:53.449 align:start position:0% software for mobile advertisement advertisers<00:09:52.200> publishers<00:09:52.950> and<00:09:53.220> that 00:09:53.449 --> 00:09:53.459 align:start position:0% advertisers publishers and that 00:09:53.459 --> 00:09:55.819 align:start position:0% advertisers publishers and that advertisement<00:09:54.270> network<00:09:54.750> not<00:09:55.110> usually<00:09:55.529> trust 00:09:55.819 --> 00:09:55.829 align:start position:0% advertisement network not usually trust 00:09:55.829 --> 00:09:59.060 align:start position:0% advertisement network not usually trust each<00:09:56.010> other<00:09:56.570> if<00:09:57.570> you<00:09:57.990> you<00:09:58.200> probably<00:09:58.470> face<00:09:58.829> this 00:09:59.060 --> 00:09:59.070 align:start position:0% each other if you you probably face this 00:09:59.070 --> 00:10:01.850 align:start position:0% each other if you you probably face this problem<00:09:59.310> already<00:10:00.110> it's<00:10:01.110> industry<00:10:01.680> when 00:10:01.850 --> 00:10:01.860 align:start position:0% problem already it's industry when 00:10:01.860 --> 00:10:05.900 align:start position:0% problem already it's industry when sometimes<00:10:02.700> you<00:10:03.209> download<00:10:03.990> logs<00:10:04.380> and<00:10:04.709> or<00:10:04.920> your 00:10:05.900 --> 00:10:05.910 align:start position:0% sometimes you download logs and or your 00:10:05.910 --> 00:10:08.949 align:start position:0% sometimes you download logs and or your provider<00:10:06.500> gives<00:10:07.500> you<00:10:07.680> logs<00:10:07.920> and<00:10:08.160> you<00:10:08.459> do<00:10:08.670> not 00:10:08.949 --> 00:10:08.959 align:start position:0% provider gives you logs and you do not 00:10:08.959 --> 00:10:12.190 align:start position:0% provider gives you logs and you do not really<00:10:09.959> believe<00:10:10.079> that<00:10:10.560> it's 00:10:12.190 --> 00:10:12.200 align:start position:0% really believe that it's 00:10:12.200 --> 00:10:15.519 align:start position:0% really believe that it's this<00:10:13.200> information<00:10:13.829> was<00:10:14.040> not<00:10:14.220> altered 00:10:15.519 --> 00:10:15.529 align:start position:0% this information was not altered 00:10:15.529 --> 00:10:19.490 align:start position:0% this information was not altered our<00:10:16.529> solution<00:10:17.360> increases<00:10:18.360> trust<00:10:19.290> build 00:10:19.490 --> 00:10:19.500 align:start position:0% our solution increases trust build 00:10:19.500 --> 00:10:23.629 align:start position:0% our solution increases trust build parties<00:10:20.009> by<00:10:20.570> neutralization<00:10:21.570> of<00:10:21.959> the<00:10:22.800> logs<00:10:23.040> in 00:10:23.629 --> 00:10:23.639 align:start position:0% parties by neutralization of the logs in 00:10:23.639 --> 00:10:26.350 align:start position:0% parties by neutralization of the logs in grantees<00:10:24.149> that<00:10:24.180> data<00:10:24.690> was<00:10:24.959> not<00:10:25.199> manipulated 00:10:26.350 --> 00:10:26.360 align:start position:0% grantees that data was not manipulated 00:10:26.360 --> 00:10:30.769 align:start position:0% grantees that data was not manipulated afterwards<00:10:27.360> and<00:10:27.709> it<00:10:28.709> actually<00:10:29.610> it's<00:10:30.000> not<00:10:30.480> for 00:10:30.769 --> 00:10:30.779 align:start position:0% afterwards and it actually it's not for 00:10:30.779 --> 00:10:33.170 align:start position:0% afterwards and it actually it's not for fun<00:10:30.959> it's<00:10:31.350> for<00:10:31.589> money<00:10:31.769> because<00:10:32.009> this<00:10:32.790> solution 00:10:33.170 --> 00:10:33.180 align:start position:0% fun it's for money because this solution 00:10:33.180 --> 00:10:35.120 align:start position:0% fun it's for money because this solution decreases<00:10:33.959> transaction<00:10:34.589> costs<00:10:34.889> between 00:10:35.120 --> 00:10:35.130 align:start position:0% decreases transaction costs between 00:10:35.130 --> 00:10:42.460 align:start position:0% decreases transaction costs between parties 00:10:42.460 --> 00:10:42.470 align:start position:0% 00:10:42.470 --> 00:10:46.939 align:start position:0% smart<00:10:43.470> contracts<00:10:44.160> for<00:10:44.550> a<00:10:45.060> company<00:10:45.949> for 00:10:46.939 --> 00:10:46.949 align:start position:0% smart contracts for a company for 00:10:46.949 --> 00:10:49.970 align:start position:0% smart contracts for a company for holding<00:10:47.370> company<00:10:47.880> this<00:10:48.269> case<00:10:48.990> is<00:10:49.410> also<00:10:49.889> in 00:10:49.970 --> 00:10:49.980 align:start position:0% holding company this case is also in 00:10:49.980 --> 00:10:51.519 align:start position:0% holding company this case is also in production<00:10:50.579> mode 00:10:51.519 --> 00:10:51.529 align:start position:0% production mode 00:10:51.529 --> 00:10:54.860 align:start position:0% production mode how<00:10:52.529> it<00:10:52.740> works<00:10:53.040> there's<00:10:53.819> a<00:10:53.940> holding<00:10:54.660> company 00:10:54.860 --> 00:10:54.870 align:start position:0% how it works there's a holding company 00:10:54.870 --> 00:10:57.680 align:start position:0% how it works there's a holding company which<00:10:55.500> was<00:10:55.889> developed<00:10:56.370> by<00:10:56.850> acquisition<00:10:57.569> of 00:10:57.680 --> 00:10:57.690 align:start position:0% which was developed by acquisition of 00:10:57.690 --> 00:11:00.800 align:start position:0% which was developed by acquisition of different<00:10:58.350> companies<00:10:58.800> that's<00:10:59.069> why<00:10:59.720> there<00:11:00.720> is 00:11:00.800 --> 00:11:00.810 align:start position:0% different companies that's why there is 00:11:00.810 --> 00:11:04.040 align:start position:0% different companies that's why there is a<00:11:01.019> zoo<00:11:01.410> of<00:11:01.680> different<00:11:02.600> earpiece<00:11:03.600> systems 00:11:04.040 --> 00:11:04.050 align:start position:0% a zoo of different earpiece systems 00:11:04.050 --> 00:11:06.769 align:start position:0% a zoo of different earpiece systems within<00:11:04.709> the<00:11:04.920> holding<00:11:05.310> company<00:11:05.759> and<00:11:05.940> they<00:11:06.509> need 00:11:06.769 --> 00:11:06.779 align:start position:0% within the holding company and they need 00:11:06.779 --> 00:11:08.870 align:start position:0% within the holding company and they need to<00:11:06.990> integrate<00:11:07.230> some<00:11:07.949> features<00:11:08.370> like<00:11:08.639> they 00:11:08.870 --> 00:11:08.880 align:start position:0% to integrate some features like they 00:11:08.880 --> 00:11:11.379 align:start position:0% to integrate some features like they need<00:11:09.149> to<00:11:09.420> approve<00:11:09.779> payments 00:11:11.379 --> 00:11:11.389 align:start position:0% need to approve payments 00:11:11.389 --> 00:11:14.629 align:start position:0% need to approve payments going<00:11:12.389> from<00:11:12.720> each<00:11:12.930> company<00:11:13.620> in<00:11:13.920> in<00:11:14.490> the 00:11:14.629 --> 00:11:14.639 align:start position:0% going from each company in in the 00:11:14.639 --> 00:11:16.480 align:start position:0% going from each company in in the headquarter 00:11:16.480 --> 00:11:16.490 align:start position:0% headquarter 00:11:16.490 --> 00:11:19.069 align:start position:0% headquarter actually<00:11:17.490> they<00:11:17.639> had<00:11:17.819> two<00:11:18.060> options<00:11:18.660> the<00:11:19.050> first 00:11:19.069 --> 00:11:19.079 align:start position:0% actually they had two options the first 00:11:19.079 --> 00:11:21.999 align:start position:0% actually they had two options the first one<00:11:19.589> is<00:11:19.920> to<00:11:20.339> hire 00:11:21.999 --> 00:11:22.009 align:start position:0% one is to hire 00:11:22.009 --> 00:11:26.210 align:start position:0% one is to hire is<00:11:23.009> to<00:11:23.250> hire<00:11:23.459> consultants<00:11:24.269> or<00:11:24.480> to<00:11:25.380> consultancy 00:11:26.210 --> 00:11:26.220 align:start position:0% is to hire consultants or to consultancy 00:11:26.220 --> 00:11:28.400 align:start position:0% is to hire consultants or to consultancy company<00:11:26.250> to<00:11:26.819> integrate<00:11:27.209> all<00:11:27.420> the<00:11:27.630> earpieces 00:11:28.400 --> 00:11:28.410 align:start position:0% company to integrate all the earpieces 00:11:28.410 --> 00:11:31.730 align:start position:0% company to integrate all the earpieces teams<00:11:28.680> it<00:11:28.860> would<00:11:29.040> be<00:11:29.190> very<00:11:29.459> costly<00:11:29.760> and<00:11:30.740> would 00:11:31.730 --> 00:11:31.740 align:start position:0% teams it would be very costly and would 00:11:31.740 --> 00:11:32.980 align:start position:0% teams it would be very costly and would take<00:11:31.980> a<00:11:32.010> long<00:11:32.250> time 00:11:32.980 --> 00:11:32.990 align:start position:0% take a long time 00:11:32.990 --> 00:11:36.370 align:start position:0% take a long time another<00:11:33.990> solution 00:11:36.370 --> 00:11:36.380 align:start position:0% 00:11:36.380 --> 00:11:39.410 align:start position:0% it<00:11:37.380> turned<00:11:37.829> out<00:11:37.980> to<00:11:38.250> be<00:11:38.370> very<00:11:38.399> simple<00:11:39.029> it<00:11:39.209> was 00:11:39.410 --> 00:11:39.420 align:start position:0% it turned out to be very simple it was 00:11:39.420 --> 00:11:41.480 align:start position:0% it turned out to be very simple it was the<00:11:40.019> integration<00:11:40.500> what<00:11:40.680> was<00:11:40.949> completed 00:11:41.480 --> 00:11:41.490 align:start position:0% the integration what was completed 00:11:41.490 --> 00:11:44.829 align:start position:0% the integration what was completed within<00:11:41.730> less<00:11:42.360> than<00:11:42.420> within<00:11:43.110> a<00:11:43.170> month 00:11:44.829 --> 00:11:44.839 align:start position:0% within less than within a month 00:11:44.839 --> 00:11:48.079 align:start position:0% within less than within a month earpiece<00:11:45.839> systems<00:11:46.260> was<00:11:46.670> integrated<00:11:47.670> using 00:11:48.079 --> 00:11:48.089 align:start position:0% earpiece systems was integrated using 00:11:48.089 --> 00:11:50.660 align:start position:0% earpiece systems was integrated using our<00:11:48.329> notary<00:11:49.170> feature<00:11:49.620> and<00:11:49.949> what<00:11:50.339> is<00:11:50.490> more 00:11:50.660 --> 00:11:50.670 align:start position:0% our notary feature and what is more 00:11:50.670 --> 00:11:54.769 align:start position:0% our notary feature and what is more important<00:11:51.240> it<00:11:51.660> allows<00:11:52.550> all<00:11:53.550> the<00:11:54.060> companies<00:11:54.600> to 00:11:54.769 --> 00:11:54.779 align:start position:0% important it allows all the companies to 00:11:54.779 --> 00:11:57.400 align:start position:0% important it allows all the companies to be<00:11:54.930> sure<00:11:55.199> that<00:11:55.589> the<00:11:55.740> data<00:11:55.949> was<00:11:56.610> not 00:11:57.400 --> 00:11:57.410 align:start position:0% be sure that the data was not 00:11:57.410 --> 00:12:01.850 align:start position:0% be sure that the data was not manipulated<00:11:58.610> the<00:11:59.610> major<00:12:00.389> takeaway<00:12:01.139> from<00:12:01.199> this 00:12:01.850 --> 00:12:01.860 align:start position:0% manipulated the major takeaway from this 00:12:01.860 --> 00:12:06.069 align:start position:0% manipulated the major takeaway from this use<00:12:02.399> case<00:12:02.430> at<00:12:02.910> that<00:12:03.180> usually 00:12:06.069 --> 00:12:06.079 align:start position:0% 00:12:06.079 --> 00:12:10.129 align:start position:0% it<00:12:07.079> usually<00:12:07.860> big<00:12:08.100> companies<00:12:08.990> consist<00:12:09.990> of 00:12:10.129 --> 00:12:10.139 align:start position:0% it usually big companies consist of 00:12:10.139 --> 00:12:12.439 align:start position:0% it usually big companies consist of several<00:12:10.439> entities<00:12:11.310> which<00:12:11.670> do<00:12:11.850> not<00:12:11.880> completely 00:12:12.439 --> 00:12:12.449 align:start position:0% several entities which do not completely 00:12:12.449 --> 00:12:14.600 align:start position:0% several entities which do not completely trust<00:12:12.779> us<00:12:12.930> at<00:12:13.079> each<00:12:13.260> other<00:12:13.500> for<00:12:13.620> example<00:12:14.250> each 00:12:14.600 --> 00:12:14.610 align:start position:0% trust us at each other for example each 00:12:14.610 --> 00:12:17.809 align:start position:0% trust us at each other for example each entity<00:12:15.209> in<00:12:15.480> the<00:12:15.509> holding<00:12:15.959> company<00:12:16.500> always<00:12:17.250> has 00:12:17.809 --> 00:12:17.819 align:start position:0% entity in the holding company always has 00:12:17.819 --> 00:12:19.389 align:start position:0% entity in the holding company always has its<00:12:18.089> own 00:12:19.389 --> 00:12:19.399 align:start position:0% its own 00:12:19.399 --> 00:12:24.620 align:start position:0% its own CTO<00:12:20.399> CEO<00:12:21.149> who<00:12:22.050> are<00:12:22.139> responsible<00:12:22.380> for<00:12:23.420> P&L<00:12:24.420> and 00:12:24.620 --> 00:12:24.630 align:start position:0% CTO CEO who are responsible for P&L and 00:12:24.630 --> 00:12:29.679 align:start position:0% CTO CEO who are responsible for P&L and budget 00:12:29.679 --> 00:12:29.689 align:start position:0% 00:12:29.689 --> 00:12:34.270 align:start position:0% the<00:12:30.689> last<00:12:30.899> use<00:12:31.110> case<00:12:31.699> became<00:12:32.699> for<00:12:33.510> I 00:12:34.270 --> 00:12:34.280 align:start position:0% the last use case became for I 00:12:34.280 --> 00:12:39.640 align:start position:0% the last use case became for I became<00:12:35.280> for<00:12:35.640> Ben<00:12:36.480> consortium<00:12:37.170> in<00:12:37.380> Russia 00:12:39.640 --> 00:12:39.650 align:start position:0% became for Ben consortium in Russia 00:12:39.650 --> 00:12:43.660 align:start position:0% became for Ben consortium in Russia banks<00:12:40.650> exchange<00:12:41.490> information<00:12:41.840> between 00:12:43.660 --> 00:12:43.670 align:start position:0% banks exchange information between 00:12:43.670 --> 00:12:45.400 align:start position:0% banks exchange information between each<00:12:44.670> other 00:12:45.400 --> 00:12:45.410 align:start position:0% each other 00:12:45.410 --> 00:12:49.180 align:start position:0% each other for<00:12:46.410> example<00:12:46.890> information<00:12:47.550> about 00:12:49.180 --> 00:12:49.190 align:start position:0% for example information about 00:12:49.190 --> 00:12:52.330 align:start position:0% for example information about people<00:12:50.190> who<00:12:50.430> try<00:12:50.700> to<00:12:50.760> prod<00:12:51.300> them<00:12:51.540> or 00:12:52.330 --> 00:12:52.340 align:start position:0% people who try to prod them or 00:12:52.340 --> 00:12:55.280 align:start position:0% people who try to prod them or exchange<00:12:53.340> information<00:12:53.610> on<00:12:54.150> credit<00:12:54.540> issues<00:12:55.050> to 00:12:55.280 --> 00:12:55.290 align:start position:0% exchange information on credit issues to 00:12:55.290 --> 00:12:58.190 align:start position:0% exchange information on credit issues to class<00:12:55.530> and<00:12:55.950> their<00:12:56.340> client<00:12:56.850> score<00:12:57.180> the<00:12:57.930> major 00:12:58.190 --> 00:12:58.200 align:start position:0% class and their client score the major 00:12:58.200 --> 00:13:01.480 align:start position:0% class and their client score the major takeaway<00:12:58.800> from<00:12:58.860> this<00:12:59.460> use<00:13:00.000> case<00:13:00.030> that 00:13:01.480 --> 00:13:01.490 align:start position:0% takeaway from this use case that 00:13:01.490 --> 00:13:04.070 align:start position:0% takeaway from this use case that usually<00:13:02.490> companies<00:13:03.330> in<00:13:03.570> many<00:13:03.780> industries 00:13:04.070 --> 00:13:04.080 align:start position:0% usually companies in many industries 00:13:04.080 --> 00:13:07.360 align:start position:0% usually companies in many industries find<00:13:05.040> have<00:13:05.700> already<00:13:05.850> found<00:13:06.300> the<00:13:06.630> way<00:13:06.780> to 00:13:07.360 --> 00:13:07.370 align:start position:0% find have already found the way to 00:13:07.370 --> 00:13:11.120 align:start position:0% find have already found the way to arrange<00:13:08.660> communication<00:13:09.660> for<00:13:10.200> major<00:13:10.890> use 00:13:11.120 --> 00:13:11.130 align:start position:0% arrange communication for major use 00:13:11.130 --> 00:13:12.940 align:start position:0% arrange communication for major use cases<00:13:11.460> like 00:13:12.940 --> 00:13:12.950 align:start position:0% cases like 00:13:12.950 --> 00:13:15.280 align:start position:0% cases like banks<00:13:13.950> already<00:13:14.280> have 00:13:15.280 --> 00:13:15.290 align:start position:0% banks already have 00:13:15.290 --> 00:13:19.000 align:start position:0% banks already have Visa<00:13:16.290> Mastercard<00:13:17.280> or 00:13:19.000 --> 00:13:19.010 align:start position:0% Visa Mastercard or 00:13:19.010 --> 00:13:21.560 align:start position:0% Visa Mastercard or field<00:13:20.010> because<00:13:20.400> they<00:13:20.640> cannot<00:13:21.030> live<00:13:21.270> without 00:13:21.560 --> 00:13:21.570 align:start position:0% field because they cannot live without 00:13:21.570 --> 00:13:24.640 align:start position:0% field because they cannot live without payments<00:13:22.200> but<00:13:22.770> when<00:13:23.280> it<00:13:23.430> comes<00:13:23.760> to<00:13:24.180> exchange 00:13:24.640 --> 00:13:24.650 align:start position:0% payments but when it comes to exchange 00:13:24.650 --> 00:13:27.610 align:start position:0% payments but when it comes to exchange information<00:13:25.650> in 00:13:27.610 --> 00:13:27.620 align:start position:0% information in 00:13:27.620 --> 00:13:31.310 align:start position:0% information in less<00:13:28.970> important<00:13:29.970> cases<00:13:30.210> like<00:13:30.570> exchange 00:13:31.310 --> 00:13:31.320 align:start position:0% less important cases like exchange 00:13:31.320 --> 00:13:33.200 align:start position:0% less important cases like exchange information<00:13:31.530> about<00:13:32.100> products<00:13:32.580> they<00:13:32.760> just 00:13:33.200 --> 00:13:33.210 align:start position:0% information about products they just 00:13:33.210 --> 00:13:36.050 align:start position:0% information about products they just cannot<00:13:33.720> arrange<00:13:34.140> consortiums<00:13:34.920> because<00:13:35.310> they 00:13:36.050 --> 00:13:36.060 align:start position:0% cannot arrange consortiums because they 00:13:36.060 --> 00:13:39.320 align:start position:0% cannot arrange consortiums because they would<00:13:36.300> need<00:13:36.570> to<00:13:36.750> arrange<00:13:36.990> a<00:13:37.490> company<00:13:38.490> elect 00:13:39.320 --> 00:13:39.330 align:start position:0% would need to arrange a company elect 00:13:39.330 --> 00:13:43.010 align:start position:0% would need to arrange a company elect the<00:13:39.510> CEO<00:13:40.310> distribute<00:13:41.310> shares<00:13:41.840> manage<00:13:42.840> the 00:13:43.010 --> 00:13:43.020 align:start position:0% the CEO distribute shares manage the 00:13:43.020 --> 00:13:44.630 align:start position:0% the CEO distribute shares manage the company<00:13:43.470> and<00:13:43.590> so<00:13:43.710> on<00:13:43.770> it's<00:13:43.950> it's<00:13:44.310> so 00:13:44.630 --> 00:13:44.640 align:start position:0% company and so on it's it's so 00:13:44.640 --> 00:13:47.090 align:start position:0% company and so on it's it's so cumbersome<00:13:45.210> that<00:13:45.450> no<00:13:45.870> one<00:13:46.110> is<00:13:46.320> going<00:13:46.530> to<00:13:46.680> do<00:13:46.980> it 00:13:47.090 --> 00:13:47.100 align:start position:0% cumbersome that no one is going to do it 00:13:47.100 --> 00:13:49.730 align:start position:0% cumbersome that no one is going to do it and<00:13:47.310> they<00:13:47.640> also<00:13:47.880> do<00:13:48.180> not<00:13:48.300> like<00:13:48.630> to<00:13:49.170> use<00:13:49.500> a 00:13:49.730 --> 00:13:49.740 align:start position:0% and they also do not like to use a 00:13:49.740 --> 00:13:51.130 align:start position:0% and they also do not like to use a single<00:13:50.010> provider 00:13:51.130 --> 00:13:51.140 align:start position:0% single provider 00:13:51.140 --> 00:13:56.390 align:start position:0% single provider to<00:13:52.140> to<00:13:52.710> help<00:13:52.950> them<00:13:53.360> that's<00:13:54.360> why<00:13:54.630> our<00:13:55.400> solution 00:13:56.390 --> 00:13:56.400 align:start position:0% to to help them that's why our solution 00:13:56.400 --> 00:14:00.890 align:start position:0% to to help them that's why our solution can<00:13:56.730> help<00:13:57.260> big<00:13:58.260> companies<00:13:58.530> in<00:13:59.300> not<00:14:00.300> only<00:14:00.480> big 00:14:00.890 --> 00:14:00.900 align:start position:0% can help big companies in not only big 00:14:00.900 --> 00:14:03.790 align:start position:0% can help big companies in not only big companies<00:14:01.440> in<00:14:01.650> many<00:14:01.890> industries<00:14:02.190> to<00:14:02.880> arrange 00:14:03.790 --> 00:14:03.800 align:start position:0% companies in many industries to arrange 00:14:03.800 --> 00:14:07.210 align:start position:0% companies in many industries to arrange consortiums 00:14:07.210 --> 00:14:07.220 align:start position:0% 00:14:07.220 --> 00:14:11.500 align:start position:0% it<00:14:08.220> is<00:14:08.400> very<00:14:08.940> pleasant<00:14:09.180> to<00:14:09.540> show<00:14:10.350> you<00:14:10.410> a 00:14:11.500 --> 00:14:11.510 align:start position:0% it is very pleasant to show you a 00:14:11.510 --> 00:14:17.110 align:start position:0% it is very pleasant to show you a smiling<00:14:12.510> faces<00:14:12.780> of<00:14:13.260> our<00:14:13.680> clients 00:14:17.110 --> 00:14:17.120 align:start position:0% 00:14:17.120 --> 00:14:22.510 align:start position:0% yes<00:14:18.120> I'm<00:14:18.450> I'm<00:14:18.960> closing<00:14:19.530> and<00:14:19.820> by<00:14:20.820> the<00:14:20.850> way 00:14:22.510 --> 00:14:22.520 align:start position:0% yes I'm I'm closing and by the way 00:14:22.520 --> 00:14:27.740 align:start position:0% yes I'm I'm closing and by the way if<00:14:23.520> someone<00:14:24.770> wants<00:14:25.770> to<00:14:25.830> share<00:14:26.670> your<00:14:26.970> ideas<00:14:27.510> or 00:14:27.740 --> 00:14:27.750 align:start position:0% if someone wants to share your ideas or 00:14:27.750 --> 00:14:31.580 align:start position:0% if someone wants to share your ideas or ask<00:14:28.110> me<00:14:28.350> equations<00:14:29.090> you<00:14:30.090> can<00:14:30.300> find<00:14:30.630> me<00:14:30.960> in<00:14:31.230> the 00:14:31.580 --> 00:14:31.590 align:start position:0% ask me equations you can find me in the 00:14:31.590 --> 00:14:33.470 align:start position:0% ask me equations you can find me in the whole<00:14:31.800> trading<00:14:32.400> your<00:14:32.640> questions<00:14:33.180> or<00:14:33.300> your 00:14:33.470 --> 00:14:33.480 align:start position:0% whole trading your questions or your 00:14:33.480 --> 00:14:36.470 align:start position:0% whole trading your questions or your ideas<00:14:33.900> for<00:14:34.110> this<00:14:34.310> funny<00:14:35.310> t-shirts<00:14:35.880> I<00:14:36.090> still 00:14:36.470 --> 00:14:36.480 align:start position:0% ideas for this funny t-shirts I still 00:14:36.480 --> 00:14:37.720 align:start position:0% ideas for this funny t-shirts I still have<00:14:36.690> some 00:14:37.720 --> 00:14:37.730 align:start position:0% have some 00:14:37.730 --> 00:14:39.680 align:start position:0% have some thank<00:14:38.730> you 00:14:39.680 --> 00:14:39.690 align:start position:0% thank you 00:14:39.690 --> 00:14:41.990 align:start position:0% thank you thank<00:14:40.170> you<00:14:40.320> very<00:14:40.350> much<00:14:40.680> Victor<00:14:41.280> much 00:14:41.990 --> 00:14:42.000 align:start position:0% thank you very much Victor much 00:14:42.000 --> 00:14:43.170 align:start position:0% thank you very much Victor much appreciated 00:14:43.170 --> 00:14:43.180 align:start position:0% appreciated 00:14:43.180 --> 00:14:51.559 align:start position:0% appreciated [Music]