WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:09.940 align:start position:0% [Applause] 00:00:09.940 --> 00:00:09.950 align:start position:0% 00:00:09.950 --> 00:00:16.240 align:start position:0% I<00:00:12.760> am<00:00:13.760> often<00:00:14.090> forum<00:00:14.750> reacts<00:00:15.290> and<00:00:15.590> what<00:00:16.130> I<00:00:16.160> am 00:00:16.240 --> 00:00:16.250 align:start position:0% I am often forum reacts and what I am 00:00:16.250 --> 00:00:19.390 align:start position:0% I am often forum reacts and what I am doing<00:00:16.460> is<00:00:16.790> currently<00:00:17.720> works<00:00:18.020> for<00:00:18.400> privacy 00:00:19.390 --> 00:00:19.400 align:start position:0% doing is currently works for privacy 00:00:19.400 --> 00:00:22.030 align:start position:0% doing is currently works for privacy solutions<00:00:19.970> to<00:00:20.119> the<00:00:20.240> protein<00:00:20.660> networked<00:00:21.140> so<00:00:21.560> of 00:00:22.030 --> 00:00:22.040 align:start position:0% solutions to the protein networked so of 00:00:22.040 --> 00:00:24.519 align:start position:0% solutions to the protein networked so of digital<00:00:22.790> Jam<00:00:23.029> product<00:00:23.450> also<00:00:23.900> the<00:00:24.080> privacy 00:00:24.519 --> 00:00:24.529 align:start position:0% digital Jam product also the privacy 00:00:24.529 --> 00:00:27.160 align:start position:0% digital Jam product also the privacy preserving<00:00:24.920> approaches<00:00:25.640> so<00:00:26.000> I'm<00:00:26.600> happy<00:00:26.840> to<00:00:27.110> be 00:00:27.160 --> 00:00:27.170 align:start position:0% preserving approaches so I'm happy to be 00:00:27.170 --> 00:00:31.990 align:start position:0% preserving approaches so I'm happy to be here<00:00:27.380> to<00:00:27.619> talk<00:00:27.830> about<00:00:27.860> it<00:00:30.609> let's<00:00:31.609> start<00:00:31.730> off<00:00:31.970> by 00:00:31.990 --> 00:00:32.000 align:start position:0% here to talk about it let's start off by 00:00:32.000 --> 00:00:35.260 align:start position:0% here to talk about it let's start off by briefly<00:00:33.100> defining<00:00:34.100> what<00:00:34.370> data<00:00:34.580> privacy<00:00:34.970> the 00:00:35.260 --> 00:00:35.270 align:start position:0% briefly defining what data privacy the 00:00:35.270 --> 00:00:38.590 align:start position:0% briefly defining what data privacy the blockchain<00:00:35.480> context<00:00:36.699> we<00:00:37.699> can<00:00:37.730> see<00:00:38.090> the<00:00:38.300> whole 00:00:38.590 --> 00:00:38.600 align:start position:0% blockchain context we can see the whole 00:00:38.600 --> 00:00:41.049 align:start position:0% blockchain context we can see the whole production<00:00:38.900> system<00:00:39.620> can<00:00:40.010> decompose<00:00:40.699> maybe 00:00:41.049 --> 00:00:41.059 align:start position:0% production system can decompose maybe 00:00:41.059 --> 00:00:46.750 align:start position:0% production system can decompose maybe 2/3<00:00:42.190> radio<00:00:43.190> and<00:00:43.780> progeria<00:00:44.780> and<00:00:45.290> the<00:00:46.159> Justin<00:00:46.640> is 00:00:46.750 --> 00:00:46.760 align:start position:0% 2/3 radio and progeria and the Justin is 00:00:46.760 --> 00:00:49.930 align:start position:0% 2/3 radio and progeria and the Justin is my<00:00:46.909> talk<00:00:47.180> I<00:00:47.449> recommend<00:00:48.350> you<00:00:48.470> find<00:00:48.500> the<00:00:48.949> premise 00:00:49.930 --> 00:00:49.940 align:start position:0% my talk I recommend you find the premise 00:00:49.940 --> 00:00:51.130 align:start position:0% my talk I recommend you find the premise in<00:00:50.120> future<00:00:50.570> itself 00:00:51.130 --> 00:00:51.140 align:start position:0% in future itself 00:00:51.140 --> 00:00:53.410 align:start position:0% in future itself kalimera<00:00:51.949> come<00:00:52.309> first<00:00:52.760> also<00:00:53.180> that 00:00:53.410 --> 00:00:53.420 align:start position:0% kalimera come first also that 00:00:53.420 --> 00:00:55.660 align:start position:0% kalimera come first also that confidentiality<00:00:54.229> features<00:00:54.890> after<00:00:55.339> landing 00:00:55.660 --> 00:00:55.670 align:start position:0% confidentiality features after landing 00:00:55.670 --> 00:00:59.710 align:start position:0% confidentiality features after landing has<00:00:55.850> features<00:00:57.909> competition<00:00:58.909> for<00:00:59.510> the 00:00:59.710 --> 00:00:59.720 align:start position:0% has features competition for the 00:00:59.720 --> 00:01:02.950 align:start position:0% has features competition for the networking<00:01:00.170> layer<00:01:00.320> means<00:01:00.879> hiding<00:01:01.960> translated 00:01:02.950 --> 00:01:02.960 align:start position:0% networking layer means hiding translated 00:01:02.960 --> 00:01:07.539 align:start position:0% networking layer means hiding translated and<00:01:03.489> anonymity<00:01:04.489> for<00:01:05.030> networking<00:01:05.630> really<00:01:06.549> high 00:01:07.539 --> 00:01:07.549 align:start position:0% and anonymity for networking really high 00:01:07.549 --> 00:01:11.350 align:start position:0% and anonymity for networking really high degree<00:01:07.790> of<00:01:08.000> analysis<00:01:09.610> whereas<00:01:10.610> the<00:01:10.760> condition 00:01:11.350 --> 00:01:11.360 align:start position:0% degree of analysis whereas the condition 00:01:11.360 --> 00:01:13.990 align:start position:0% degree of analysis whereas the condition for<00:01:11.810> the<00:01:11.990> rock<00:01:12.229> generation<00:01:12.260> means<00:01:13.010> highly 00:01:13.990 --> 00:01:14.000 align:start position:0% for the rock generation means highly 00:01:14.000 --> 00:01:16.469 align:start position:0% for the rock generation means highly transferred<00:01:14.600> amount<00:01:14.930> so<00:01:15.469> when<00:01:15.829> you<00:01:15.950> set<00:01:16.219> up 00:01:16.469 --> 00:01:16.479 align:start position:0% transferred amount so when you set up 00:01:16.479 --> 00:01:19.209 align:start position:0% transferred amount so when you set up transport<00:01:17.479> or<00:01:17.810> point<00:01:18.020> in<00:01:18.170> the<00:01:18.320> same<00:01:18.590> for 00:01:19.209 --> 00:01:19.219 align:start position:0% transport or point in the same for 00:01:19.219 --> 00:01:20.920 align:start position:0% transport or point in the same for everyone<00:01:19.520> see<00:01:19.850> how<00:01:19.880> much<00:01:20.240> use<00:01:20.450> Center<00:01:20.840> is 00:01:20.920 --> 00:01:20.930 align:start position:0% everyone see how much use Center is 00:01:20.930 --> 00:01:24.700 align:start position:0% everyone see how much use Center is available<00:01:21.109> the<00:01:21.710> data<00:01:21.890> and<00:01:22.990> anonymity<00:01:23.990> for<00:01:24.530> the 00:01:24.700 --> 00:01:24.710 align:start position:0% available the data and anonymity for the 00:01:24.710 --> 00:01:28.539 align:start position:0% available the data and anonymity for the route<00:01:24.920> generator<00:01:25.429> went<00:01:25.909> into<00:01:27.340> hiding<00:01:28.340> on 00:01:28.539 --> 00:01:28.549 align:start position:0% route generator went into hiding on 00:01:28.549 --> 00:01:30.550 align:start position:0% route generator went into hiding on transaction<00:01:29.119> graph<00:01:29.329> so<00:01:29.630> again<00:01:29.990> when<00:01:30.200> you<00:01:30.320> send 00:01:30.550 --> 00:01:30.560 align:start position:0% transaction graph so again when you send 00:01:30.560 --> 00:01:33.279 align:start position:0% transaction graph so again when you send the<00:01:30.649> transaction<00:01:30.890> of<00:01:31.579> everyone<00:01:32.479> see<00:01:32.689> the 00:01:33.279 --> 00:01:33.289 align:start position:0% the transaction of everyone see the 00:01:33.289 --> 00:01:35.260 align:start position:0% the transaction of everyone see the transaction<00:01:33.890> when<00:01:34.039> come<00:01:34.340> home<00:01:34.609> or<00:01:34.939> where<00:01:35.240> to 00:01:35.260 --> 00:01:35.270 align:start position:0% transaction when come home or where to 00:01:35.270 --> 00:01:38.139 align:start position:0% transaction when come home or where to go<00:01:35.600> so<00:01:36.560> in<00:01:37.130> this<00:01:37.280> mental<00:01:37.640> cramming<00:01:38.030> on 00:01:38.139 --> 00:01:38.149 align:start position:0% go so in this mental cramming on 00:01:38.149 --> 00:01:40.630 align:start position:0% go so in this mental cramming on focusing<00:01:38.749> on<00:01:38.960> the<00:01:39.259> privacy<00:01:39.859> features<00:01:40.369> for 00:01:40.630 --> 00:01:40.640 align:start position:0% focusing on the privacy features for 00:01:40.640 --> 00:01:46.330 align:start position:0% focusing on the privacy features for dist<00:01:40.909> approach<00:01:41.299> generation<00:01:44.380> in<00:01:45.380> the<00:01:45.710> midpoint 00:01:46.330 --> 00:01:46.340 align:start position:0% dist approach generation in the midpoint 00:01:46.340 --> 00:01:49.680 align:start position:0% dist approach generation in the midpoint ym<00:01:46.729> standard<00:01:47.270> transaction 00:01:49.680 --> 00:01:49.690 align:start position:0% ym standard transaction 00:01:49.690 --> 00:01:52.590 align:start position:0% ym standard transaction pogchamp<00:01:50.230> and<00:01:50.830> when<00:01:51.100> your<00:01:51.430> sanctum<00:01:52.000> same 00:01:52.590 --> 00:01:52.600 align:start position:0% pogchamp and when your sanctum same 00:01:52.600 --> 00:01:54.960 align:start position:0% pogchamp and when your sanctum same transaction<00:01:53.110> citizen<00:01:53.530> rupture<00:01:54.040> will<00:01:54.910> be 00:01:54.960 --> 00:01:54.970 align:start position:0% transaction citizen rupture will be 00:01:54.970 --> 00:01:57.150 align:start position:0% transaction citizen rupture will be attached<00:01:55.300> to<00:01:55.330> one<00:01:55.600> of<00:01:56.110> centers<00:01:56.710> private 00:01:57.150 --> 00:01:57.160 align:start position:0% attached to one of centers private 00:01:57.160 --> 00:02:00.300 align:start position:0% attached to one of centers private private<00:01:57.490> to<00:01:57.580> keep<00:01:57.760> a<00:01:58.000> public<00:01:58.600> key<00:01:58.810> and<00:01:59.310> to 00:02:00.300 --> 00:02:00.310 align:start position:0% private to keep a public key and to 00:02:00.310 --> 00:02:03.210 align:start position:0% private to keep a public key and to verify<00:02:00.880> the<00:02:00.990> signature<00:02:01.990> question<00:02:02.470> to<00:02:02.890> verify 00:02:03.210 --> 00:02:03.220 align:start position:0% verify the signature question to verify 00:02:03.220 --> 00:02:05.969 align:start position:0% verify the signature question to verify the<00:02:03.280> craftsmanship<00:02:03.880> of<00:02:04.210> the<00:02:04.480> signature<00:02:04.990> but 00:02:05.969 --> 00:02:05.979 align:start position:0% the craftsmanship of the signature but 00:02:05.979 --> 00:02:08.310 align:start position:0% the craftsmanship of the signature but it<00:02:06.190> always<00:02:06.490> reveals<00:02:07.030> a<00:02:07.180> transaction<00:02:08.020> where 00:02:08.310 --> 00:02:08.320 align:start position:0% it always reveals a transaction where 00:02:08.320 --> 00:02:13.410 align:start position:0% it always reveals a transaction where confirm<00:02:08.860> and<00:02:10.350> so<00:02:11.350> inaudible<00:02:11.740> data<00:02:12.460> type<00:02:13.180> of 00:02:13.410 --> 00:02:13.420 align:start position:0% confirm and so inaudible data type of 00:02:13.420 --> 00:02:15.990 align:start position:0% confirm and so inaudible data type of the<00:02:13.600> data<00:02:13.720> linkage<00:02:14.260> in<00:02:15.160> the<00:02:15.280> module<00:02:15.760> is<00:02:15.970> a 00:02:15.990 --> 00:02:16.000 align:start position:0% the data linkage in the module is a 00:02:16.000 --> 00:02:17.970 align:start position:0% the data linkage in the module is a special<00:02:16.540> signatures<00:02:17.110> called<00:02:17.470> real 00:02:17.970 --> 00:02:17.980 align:start position:0% special signatures called real 00:02:17.980 --> 00:02:21.449 align:start position:0% special signatures called real signatures<00:02:18.580> and<00:02:18.940> the<00:02:19.890> signatures<00:02:20.890> basically 00:02:21.449 --> 00:02:21.459 align:start position:0% signatures and the signatures basically 00:02:21.459 --> 00:02:24.600 align:start position:0% signatures and the signatures basically a<00:02:21.490> lot<00:02:21.820> it'll<00:02:22.270> be<00:02:22.360> attested<00:02:22.690> not<00:02:23.080> just<00:02:23.680> one<00:02:24.250> of 00:02:24.600 --> 00:02:24.610 align:start position:0% a lot it'll be attested not just one of 00:02:24.610 --> 00:02:28.650 align:start position:0% a lot it'll be attested not just one of center<00:02:24.970> pipe<00:02:25.180> type<00:02:25.930> int<00:02:26.340> but<00:02:27.420> management<00:02:28.420> with 00:02:28.650 --> 00:02:28.660 align:start position:0% center pipe type int but management with 00:02:28.660 --> 00:02:32.490 align:start position:0% center pipe type int but management with some<00:02:29.310> damn<00:02:30.310> authority<00:02:31.000> and<00:02:31.239> the<00:02:31.959> difficut 00:02:32.490 --> 00:02:32.500 align:start position:0% some damn authority and the difficut 00:02:32.500 --> 00:02:36.470 align:start position:0% some damn authority and the difficut effects<00:02:33.340> from<00:02:33.580> the<00:02:33.910> maharaja<00:02:34.630> network<00:02:35.020> and 00:02:36.470 --> 00:02:36.480 align:start position:0% effects from the maharaja network and 00:02:36.480 --> 00:02:40.590 align:start position:0% effects from the maharaja network and the<00:02:37.480> kids<00:02:37.840> also<00:02:38.130> safety<00:02:39.130> in<00:02:39.820> the<00:02:40.090> infant 00:02:40.590 --> 00:02:40.600 align:start position:0% the kids also safety in the infant 00:02:40.600 --> 00:02:46.620 align:start position:0% the kids also safety in the infant sectionalism<00:02:44.190> so<00:02:45.190> signatures<00:02:46.150> basically 00:02:46.620 --> 00:02:46.630 align:start position:0% sectionalism so signatures basically 00:02:46.630 --> 00:02:49.290 align:start position:0% sectionalism so signatures basically ensures<00:02:46.959> that<00:02:46.989> our<00:02:47.530> it's<00:02:47.860> time<00:02:48.190> to<00:02:48.430> buy<00:02:49.060> one 00:02:49.290 --> 00:02:49.300 align:start position:0% ensures that our it's time to buy one 00:02:49.300 --> 00:02:51.900 align:start position:0% ensures that our it's time to buy one private<00:02:49.780> key<00:02:50.170> corresponding<00:02:50.980> to<00:02:51.040> one<00:02:51.459> of<00:02:51.670> the 00:02:51.900 --> 00:02:51.910 align:start position:0% private key corresponding to one of the 00:02:51.910 --> 00:02:54.810 align:start position:0% private key corresponding to one of the remembers<00:02:52.510> a<00:02:52.630> public<00:02:53.049> key<00:02:53.260> and<00:02:53.370> as<00:02:54.370> a<00:02:54.549> kid 00:02:54.810 --> 00:02:54.820 align:start position:0% remembers a public key and as a kid 00:02:54.820 --> 00:02:59.520 align:start position:0% remembers a public key and as a kid works<00:02:55.209> as<00:02:55.510> a<00:02:55.570> dummy<00:02:56.080> private<00:02:56.620> key<00:02:56.830> so<00:02:57.340> this<00:02:58.530> in 00:02:59.520 --> 00:02:59.530 align:start position:0% works as a dummy private key so this in 00:02:59.530 --> 00:03:02.070 align:start position:0% works as a dummy private key so this in this<00:02:59.709> picture<00:03:00.220> the<00:03:00.280> red<00:03:00.820> one<00:03:01.150> is<00:03:01.420> on<00:03:01.690> europe 00:03:02.070 --> 00:03:02.080 align:start position:0% this picture the red one is on europe 00:03:02.080 --> 00:03:05.729 align:start position:0% this picture the red one is on europe center<00:03:03.010> actual<00:03:03.600> territory<00:03:04.600> and<00:03:04.870> as<00:03:05.410> a<00:03:05.440> kid<00:03:05.680> I 00:03:05.729 --> 00:03:05.739 align:start position:0% center actual territory and as a kid I 00:03:05.739 --> 00:03:06.509 align:start position:0% center actual territory and as a kid I washed<00:03:06.040> them 00:03:06.509 --> 00:03:06.519 align:start position:0% washed them 00:03:06.519 --> 00:03:09.210 align:start position:0% washed them damnit<00:03:06.910> Oprah<00:03:07.330> private<00:03:07.720> key<00:03:07.900> and<00:03:08.170> this<00:03:09.040> is<00:03:09.190> a 00:03:09.210 --> 00:03:09.220 align:start position:0% damnit Oprah private key and this is a 00:03:09.220 --> 00:03:12.930 align:start position:0% damnit Oprah private key and this is a white<00:03:09.580> to<00:03:09.940> advocate<00:03:10.980> to<00:03:11.980> give<00:03:12.730> their 00:03:12.930 --> 00:03:12.940 align:start position:0% white to advocate to give their 00:03:12.940 --> 00:03:15.479 align:start position:0% white to advocate to give their anonymity<00:03:13.330> features<00:03:13.959> for<00:03:14.290> the<00:03:14.530> sender<00:03:15.070> others 00:03:15.479 --> 00:03:15.489 align:start position:0% anonymity features for the sender others 00:03:15.489 --> 00:03:19.229 align:start position:0% anonymity features for the sender others in<00:03:15.700> in<00:03:15.850> the<00:03:15.940> morning<00:03:16.209> protocol<00:03:16.660> and<00:03:18.239> Paul 00:03:19.229 --> 00:03:19.239 align:start position:0% in in the morning protocol and Paul 00:03:19.239 --> 00:03:22.530 align:start position:0% in in the morning protocol and Paul gives<00:03:20.250> confidentiality<00:03:21.250> features<00:03:21.760> to<00:03:22.299> the 00:03:22.530 --> 00:03:22.540 align:start position:0% gives confidentiality features to the 00:03:22.540 --> 00:03:25.800 align:start position:0% gives confidentiality features to the morning<00:03:23.220> centers<00:03:24.220> tender<00:03:24.820> very<00:03:25.060> commitment 00:03:25.800 --> 00:03:25.810 align:start position:0% morning centers tender very commitment 00:03:25.810 --> 00:03:28.800 align:start position:0% morning centers tender very commitment hour<00:03:26.130> instead<00:03:27.130> of<00:03:27.489> the<00:03:27.730> low<00:03:28.060> edge<00:03:28.420> of<00:03:28.630> the 00:03:28.800 --> 00:03:28.810 align:start position:0% hour instead of the low edge of the 00:03:28.810 --> 00:03:32.310 align:start position:0% hour instead of the low edge of the volume<00:03:29.110> and<00:03:29.910> if<00:03:30.910> we<00:03:31.120> attach<00:03:31.480> the<00:03:31.780> arranged 00:03:32.310 --> 00:03:32.320 align:start position:0% volume and if we attach the arranged 00:03:32.320 --> 00:03:33.030 align:start position:0% volume and if we attach the arranged roost 00:03:33.030 --> 00:03:33.040 align:start position:0% roost 00:03:33.040 --> 00:03:36.660 align:start position:0% roost there<00:03:33.819> are<00:03:34.000> sprinting<00:03:34.299> systems<00:03:34.959> and<00:03:35.459> the<00:03:36.459> each 00:03:36.660 --> 00:03:36.670 align:start position:0% there are sprinting systems and the each 00:03:36.670 --> 00:03:40.380 align:start position:0% there are sprinting systems and the each of<00:03:37.209> the<00:03:38.010> provides<00:03:39.010> Authority<00:03:39.129> officer<00:03:40.090> within 00:03:40.380 --> 00:03:40.390 align:start position:0% of the provides Authority officer within 00:03:40.390 --> 00:03:43.170 align:start position:0% of the provides Authority officer within themself<00:03:41.109> value<00:03:42.069> is<00:03:42.370> in<00:03:42.519> the<00:03:42.670> back<00:03:42.819> the<00:03:42.969> range 00:03:43.170 --> 00:03:43.180 align:start position:0% themself value is in the back the range 00:03:43.180 --> 00:03:46.619 align:start position:0% themself value is in the back the range and<00:03:44.219> some<00:03:45.219> fundraisers<00:03:45.849> there<00:03:46.209> are<00:03:46.269> services 00:03:46.619 --> 00:03:46.629 align:start position:0% and some fundraisers there are services 00:03:46.629 --> 00:03:48.929 align:start position:0% and some fundraisers there are services of<00:03:46.840> all<00:03:46.959> sorts<00:03:47.290> of<00:03:47.379> animated<00:03:48.310> features<00:03:48.700> to 00:03:48.929 --> 00:03:48.939 align:start position:0% of all sorts of animated features to 00:03:48.939 --> 00:03:55.500 align:start position:0% of all sorts of animated features to give<00:03:49.299> the<00:03:51.329> recipe<00:03:52.329> and<00:03:52.599> jealousies<00:03:54.390> if<00:03:55.390> the 00:03:55.500 --> 00:03:55.510 align:start position:0% give the recipe and jealousies if the 00:03:55.510 --> 00:03:59.490 align:start position:0% give the recipe and jealousies if the teacher<00:03:55.810> also<00:03:56.819> likes<00:03:57.819> a<00:03:58.090> utak<00:03:58.450> so<00:03:58.659> right<00:03:58.870> model 00:03:59.490 --> 00:03:59.500 align:start position:0% teacher also likes a utak so right model 00:03:59.500 --> 00:04:06.089 align:start position:0% teacher also likes a utak so right model in<00:03:59.769> the<00:03:59.859> world<00:03:59.889> champ<00:04:00.340> and<00:04:00.609> I<00:04:01.540> guess<00:04:01.870> that<00:04:05.099> the 00:04:06.089 --> 00:04:06.099 align:start position:0% in the world champ and I guess that the 00:04:06.099 --> 00:04:08.580 align:start position:0% in the world champ and I guess that the mandatory<00:04:06.489> not<00:04:07.180> commitment<00:04:07.750> is<00:04:07.840> admittedly 00:04:08.580 --> 00:04:08.590 align:start position:0% mandatory not commitment is admittedly 00:04:08.590 --> 00:04:12.929 align:start position:0% mandatory not commitment is admittedly to<00:04:08.980> the<00:04:09.159> Magna<00:04:09.519> tree<00:04:09.730> and<00:04:11.010> it<00:04:12.010> was<00:04:12.040> like<00:04:12.579> yo 00:04:12.929 --> 00:04:12.939 align:start position:0% to the Magna tree and it was like yo 00:04:12.939 --> 00:04:14.869 align:start position:0% to the Magna tree and it was like yo Jeff<00:04:13.150> saw<00:04:13.329> set<00:04:13.569> in<00:04:13.720> the<00:04:13.810> world<00:04:13.989> champ 00:04:14.869 --> 00:04:14.879 align:start position:0% Jeff saw set in the world champ 00:04:14.879 --> 00:04:21.290 align:start position:0% Jeff saw set in the world champ so<00:04:15.879> that<00:04:17.579> centered<00:04:18.579> on<00:04:19.299> stands<00:04:19.810> that<00:04:19.959> a<00:04:20.650> child 00:04:21.290 --> 00:04:21.300 align:start position:0% so that centered on stands that a child 00:04:21.300 --> 00:04:24.570 align:start position:0% so that centered on stands that a child buried<00:04:22.300> under<00:04:22.780> it<00:04:22.900> to<00:04:23.050> be<00:04:23.310> communities<00:04:24.310> enough 00:04:24.570 --> 00:04:24.580 align:start position:0% buried under it to be communities enough 00:04:24.580 --> 00:04:27.570 align:start position:0% buried under it to be communities enough commitment<00:04:24.910> and<00:04:25.389> so<00:04:26.229> it<00:04:26.860> to<00:04:26.949> be<00:04:27.070> highly<00:04:27.370> this 00:04:27.570 --> 00:04:27.580 align:start position:0% commitment and so it to be highly this 00:04:27.580 --> 00:04:31.409 align:start position:0% commitment and so it to be highly this is<00:04:27.820> a<00:04:27.849> actual<00:04:28.780> amount<00:04:29.560> and<00:04:29.970> there's<00:04:30.970> an 00:04:31.409 --> 00:04:31.419 align:start position:0% is a actual amount and there's an 00:04:31.419 --> 00:04:34.110 align:start position:0% is a actual amount and there's an important<00:04:31.900> thing<00:04:32.080> is<00:04:32.349> that<00:04:32.410> this<00:04:33.310> Clinton 00:04:34.110 --> 00:04:34.120 align:start position:0% important thing is that this Clinton 00:04:34.120 --> 00:04:38.339 align:start position:0% important thing is that this Clinton this<00:04:34.720> Magna<00:04:35.320> tree<00:04:35.530> is<00:04:35.770> regarded<00:04:36.550> so<00:04:37.419> in<00:04:37.810> center 00:04:38.339 --> 00:04:38.349 align:start position:0% this Magna tree is regarded so in center 00:04:38.349 --> 00:04:43.830 align:start position:0% this Magna tree is regarded so in center to<00:04:38.740> a<00:04:38.770> payment<00:04:40.050> into<00:04:41.050> the<00:04:41.260> it<00:04:41.470> not<00:04:42.659> update<00:04:43.659> is 00:04:43.830 --> 00:04:43.840 align:start position:0% to a payment into the it not update is 00:04:43.840 --> 00:04:47.670 align:start position:0% to a payment into the it not update is also<00:04:44.169> not<00:04:44.380> commitment<00:04:45.599> instead<00:04:46.599> of<00:04:47.020> it<00:04:47.409> will 00:04:47.670 --> 00:04:47.680 align:start position:0% also not commitment instead of it will 00:04:47.680 --> 00:04:50.399 align:start position:0% also not commitment instead of it will be<00:04:47.770> an<00:04:48.070> eternal<00:04:48.639> fire<00:04:48.820> data<00:04:49.180> which<00:04:50.169> is<00:04:50.380> a 00:04:50.399 --> 00:04:50.409 align:start position:0% be an eternal fire data which is a 00:04:50.409 --> 00:04:53.750 align:start position:0% be an eternal fire data which is a unique<00:04:50.740> and<00:04:51.150> radical<00:04:52.150> to<00:04:52.479> the<00:04:52.539> specific<00:04:53.440> is<00:04:53.590> a 00:04:53.750 --> 00:04:53.760 align:start position:0% unique and radical to the specific is a 00:04:53.760 --> 00:04:57.149 align:start position:0% unique and radical to the specific is a consuming<00:04:54.760> commitment<00:04:55.599> and<00:04:55.960> that<00:04:56.560> the<00:04:56.949> fire 00:04:57.149 --> 00:04:57.159 align:start position:0% consuming commitment and that the fire 00:04:57.159 --> 00:05:00.120 align:start position:0% consuming commitment and that the fire data<00:04:57.490> will<00:04:57.789> be<00:04:58.000> added<00:04:58.479> to<00:04:58.810> the<00:04:58.990> very<00:04:59.349> fire<00:04:59.560> set 00:05:00.120 --> 00:05:00.130 align:start position:0% data will be added to the very fire set 00:05:00.130 --> 00:05:04.670 align:start position:0% data will be added to the very fire set drawn<00:05:00.610> in<00:05:00.789> fire<00:05:01.000> set<00:05:01.300> and<00:05:01.570> which<00:05:02.500> is<00:05:03.150> to 00:05:04.670 --> 00:05:04.680 align:start position:0% drawn in fire set and which is to 00:05:04.680 --> 00:05:10.290 align:start position:0% drawn in fire set and which is to prevent<00:05:05.680> from<00:05:05.949> status<00:05:06.430> pending<00:05:08.280> so<00:05:09.280> that<00:05:09.610> they 00:05:10.290 --> 00:05:10.300 align:start position:0% prevent from status pending so that they 00:05:10.300 --> 00:05:11.010 align:start position:0% prevent from status pending so that they just<00:05:10.479> max 00:05:11.010 --> 00:05:11.020 align:start position:0% just max 00:05:11.020 --> 00:05:14.040 align:start position:0% just max prove<00:05:11.590> that<00:05:12.250> all<00:05:12.880> these<00:05:13.270> computational 00:05:14.040 --> 00:05:14.050 align:start position:0% prove that all these computational 00:05:14.050 --> 00:05:16.890 align:start position:0% prove that all these computational processes<00:05:14.590> are<00:05:14.770> actually<00:05:15.460> do<00:05:15.940> or<00:05:16.510> without 00:05:16.890 --> 00:05:16.900 align:start position:0% processes are actually do or without 00:05:16.900 --> 00:05:20.530 align:start position:0% processes are actually do or without revealing<00:05:17.229> just<00:05:17.560> hands<00:05:17.800> together<00:05:18.389> such<00:05:19.389> as<00:05:19.599> a 00:05:20.530 --> 00:05:20.540 align:start position:0% revealing just hands together such as a 00:05:20.540 --> 00:05:24.040 align:start position:0% revealing just hands together such as a Senna's<00:05:21.080> privacy<00:05:21.680> and<00:05:22.450> actually<00:05:23.450> transform 00:05:24.040 --> 00:05:24.050 align:start position:0% Senna's privacy and actually transform 00:05:24.050 --> 00:05:29.530 align:start position:0% Senna's privacy and actually transform art<00:05:24.850> so<00:05:25.850> these<00:05:26.480> are<00:05:26.900> major<00:05:28.090> privacy<00:05:29.090> focusing 00:05:29.530 --> 00:05:29.540 align:start position:0% art so these are major privacy focusing 00:05:29.540 --> 00:05:34.630 align:start position:0% art so these are major privacy focusing proteges<00:05:30.050> objects<00:05:30.970> units<00:05:31.970> of<00:05:32.090> Westeros<00:05:33.640> but 00:05:34.630 --> 00:05:34.640 align:start position:0% proteges objects units of Westeros but 00:05:34.640 --> 00:05:36.460 align:start position:0% proteges objects units of Westeros but how<00:05:34.880> can<00:05:34.940> we<00:05:35.210> achieve<00:05:35.270> there<00:05:35.750> is<00:05:35.840> a<00:05:35.870> future<00:05:36.200> in 00:05:36.460 --> 00:05:36.470 align:start position:0% how can we achieve there is a future in 00:05:36.470 --> 00:05:39.220 align:start position:0% how can we achieve there is a future in the<00:05:36.650> cattle<00:05:36.950> based<00:05:37.100> approach<00:05:37.490> so<00:05:38.420> it<00:05:38.750> means<00:05:38.990> it 00:05:39.220 --> 00:05:39.230 align:start position:0% the cattle based approach so it means it 00:05:39.230 --> 00:05:41.860 align:start position:0% the cattle based approach so it means it can<00:05:39.620> be<00:05:39.650> achieved<00:05:39.800> at<00:05:40.420> confidential<00:05:41.420> features 00:05:41.860 --> 00:05:41.870 align:start position:0% can be achieved at confidential features 00:05:41.870 --> 00:05:44.020 align:start position:0% can be achieved at confidential features form<00:05:42.170> so<00:05:42.590> when<00:05:42.890> you<00:05:43.040> send<00:05:43.340> a<00:05:43.430> transaction 00:05:44.020 --> 00:05:44.030 align:start position:0% form so when you send a transaction 00:05:44.030 --> 00:05:46.660 align:start position:0% form so when you send a transaction how<00:05:44.930> can<00:05:45.170> we<00:05:45.290> achieve<00:05:45.380> America's<00:05:46.250> features 00:05:46.660 --> 00:05:46.670 align:start position:0% how can we achieve America's features 00:05:46.670 --> 00:05:51.700 align:start position:0% how can we achieve America's features for<00:05:46.970> when<00:05:47.960> you<00:05:48.050> settle<00:05:48.580> transactions<00:05:50.710> so 00:05:51.700 --> 00:05:51.710 align:start position:0% for when you settle transactions so 00:05:51.710 --> 00:05:56.350 align:start position:0% for when you settle transactions so Delta<00:05:52.370> Y<00:05:52.990> Delta<00:05:53.990> Z<00:05:54.250> Chang<00:05:55.250> is<00:05:55.550> a<00:05:55.610> privacy 00:05:56.350 --> 00:05:56.360 align:start position:0% Delta Y Delta Z Chang is a privacy 00:05:56.360 --> 00:05:58.900 align:start position:0% Delta Y Delta Z Chang is a privacy preserving<00:05:56.720> culture<00:05:57.530> and<00:05:57.830> supporting<00:05:58.730> data 00:05:58.900 --> 00:05:58.910 align:start position:0% preserving culture and supporting data 00:05:58.910 --> 00:06:02.320 align:start position:0% preserving culture and supporting data based<00:05:59.360> approach<00:05:59.810> and<00:06:00.460> we<00:06:01.460> are<00:06:01.640> currently<00:06:01.970> not 00:06:02.320 --> 00:06:02.330 align:start position:0% based approach and we are currently not 00:06:02.330 --> 00:06:05.500 align:start position:0% based approach and we are currently not on<00:06:02.630> top<00:06:02.810> of<00:06:02.990> Osibisa<00:06:03.320> you<00:06:03.800> know<00:06:03.860> we<00:06:04.640> talk<00:06:05.360> of 00:06:05.500 --> 00:06:05.510 align:start position:0% on top of Osibisa you know we talk of 00:06:05.510 --> 00:06:10.870 align:start position:0% on top of Osibisa you know we talk of ins<00:06:05.720> substrate<00:06:06.590> and<00:06:07.570> we<00:06:09.190> especially<00:06:10.190> provided 00:06:10.870 --> 00:06:10.880 align:start position:0% ins substrate and we especially provided 00:06:10.880 --> 00:06:13.960 align:start position:0% ins substrate and we especially provided some<00:06:11.210> substrate<00:06:11.780> on<00:06:12.620> shamrocks<00:06:13.340> called 00:06:13.960 --> 00:06:13.970 align:start position:0% some substrate on shamrocks called 00:06:13.970 --> 00:06:17.800 align:start position:0% some substrate on shamrocks called ourselves<00:06:14.240> 12<00:06:14.690> modules<00:06:15.140> and<00:06:16.450> some<00:06:17.450> Cherokee 00:06:17.800 --> 00:06:17.810 align:start position:0% ourselves 12 modules and some Cherokee 00:06:17.810 --> 00:06:19.690 align:start position:0% ourselves 12 modules and some Cherokee to<00:06:17.960> follow<00:06:18.230> protecting<00:06:18.830> the<00:06:18.950> same<00:06:19.100> stipulated 00:06:19.690 --> 00:06:19.700 align:start position:0% to follow protecting the same stipulated 00:06:19.700 --> 00:06:25.540 align:start position:0% to follow protecting the same stipulated R<00:06:19.880> which<00:06:20.030> is<00:06:20.060> a<00:06:20.300> strain<00:06:22.180> and<00:06:23.860> let<00:06:24.860> me<00:06:25.040> jump<00:06:25.250> into 00:06:25.540 --> 00:06:25.550 align:start position:0% R which is a strain and let me jump into 00:06:25.550 --> 00:06:30.930 align:start position:0% R which is a strain and let me jump into my<00:06:25.880> privacy<00:06:28.030> solutions<00:06:29.030> in<00:06:29.570> this<00:06:29.720> JAL<00:06:30.140> JA<00:06:30.380> let 00:06:30.930 --> 00:06:30.940 align:start position:0% my privacy solutions in this JAL JA let 00:06:30.940 --> 00:06:33.460 align:start position:0% my privacy solutions in this JAL JA let me<00:06:31.940> talk<00:06:32.150> a<00:06:32.270> little<00:06:32.300> bit<00:06:32.600> about<00:06:32.630> the<00:06:33.020> what<00:06:33.170> is<00:06:33.380> a 00:06:33.460 --> 00:06:33.470 align:start position:0% me talk a little bit about the what is a 00:06:33.470 --> 00:06:36.340 align:start position:0% me talk a little bit about the what is a substrate<00:06:33.830> is<00:06:34.330> some<00:06:35.330> strenght<00:06:35.630> is<00:06:35.810> best<00:06:36.140> very 00:06:36.340 --> 00:06:36.350 align:start position:0% substrate is some strenght is best very 00:06:36.350 --> 00:06:38.740 align:start position:0% substrate is some strenght is best very approach<00:06:36.650> a<00:06:36.860> framework<00:06:37.220> which<00:06:37.880> is<00:06:38.030> developed 00:06:38.740 --> 00:06:38.750 align:start position:0% approach a framework which is developed 00:06:38.750 --> 00:06:45.430 align:start position:0% approach a framework which is developed by<00:06:38.960> parity<00:06:39.380> technologies<00:06:40.100> and<00:06:43.480> the<00:06:44.480> substrate 00:06:45.430 --> 00:06:45.440 align:start position:0% by parity technologies and the substrate 00:06:45.440 --> 00:06:48.190 align:start position:0% by parity technologies and the substrate provides<00:06:46.010> a<00:06:46.240> basic<00:06:47.240> block<00:06:47.480> chain<00:06:47.720> component 00:06:48.190 --> 00:06:48.200 align:start position:0% provides a basic block chain component 00:06:48.200 --> 00:06:51.760 align:start position:0% provides a basic block chain component or<00:06:48.500> such<00:06:49.280> as<00:06:49.460> a<00:06:49.490> database<00:06:49.760> so<00:06:50.720> in<00:06:51.050> the<00:06:51.200> chair 00:06:51.760 --> 00:06:51.770 align:start position:0% or such as a database so in the chair 00:06:51.770 --> 00:06:53.190 align:start position:0% or such as a database so in the chair force<00:06:52.070> during<00:06:52.310> transaction 00:06:53.190 --> 00:06:53.200 align:start position:0% force during transaction 00:06:53.200 --> 00:06:55.860 align:start position:0% force during transaction and<00:06:53.850> peer-to-peer<00:06:54.850> networking<00:06:55.510> to 00:06:55.860 --> 00:06:55.870 align:start position:0% and peer-to-peer networking to 00:06:55.870 --> 00:06:57.630 align:start position:0% and peer-to-peer networking to precipitously<00:06:56.500> transitions<00:06:57.250> in<00:06:57.400> general 00:06:57.630 --> 00:06:57.640 align:start position:0% precipitously transitions in general 00:06:57.640 --> 00:06:59.700 align:start position:0% precipitously transitions in general stream<00:06:57.880> network<00:06:58.330> and<00:06:58.600> the<00:06:59.050> consensus 00:06:59.700 --> 00:06:59.710 align:start position:0% stream network and the consensus 00:06:59.710 --> 00:07:02.940 align:start position:0% stream network and the consensus mechanism<00:07:00.310> to<00:07:01.240> provide<00:07:01.630> the<00:07:01.950> incentive 00:07:02.940 --> 00:07:02.950 align:start position:0% mechanism to provide the incentive 00:07:02.950 --> 00:07:04.920 align:start position:0% mechanism to provide the incentive mechanism<00:07:03.400> entities<00:07:03.640> abrupted<00:07:04.270> network<00:07:04.600> and 00:07:04.920 --> 00:07:04.930 align:start position:0% mechanism entities abrupted network and 00:07:04.930 --> 00:07:07.200 align:start position:0% mechanism entities abrupted network and attractive<00:07:05.550> transaction<00:07:06.550> here<00:07:06.700> and<00:07:06.850> so<00:07:07.030> on 00:07:07.200 --> 00:07:07.210 align:start position:0% attractive transaction here and so on 00:07:07.210 --> 00:07:11.370 align:start position:0% attractive transaction here and so on and<00:07:07.890> the<00:07:08.890> teeth<00:07:09.460> protein<00:07:10.390> component<00:07:10.960> might<00:07:11.170> be 00:07:11.370 --> 00:07:11.380 align:start position:0% and the teeth protein component might be 00:07:11.380 --> 00:07:15.180 align:start position:0% and the teeth protein component might be most<00:07:11.640> complex<00:07:12.640> and<00:07:13.090> difficult<00:07:13.960> part<00:07:14.590> when<00:07:15.010> you 00:07:15.180 --> 00:07:15.190 align:start position:0% most complex and difficult part when you 00:07:15.190 --> 00:07:19.020 align:start position:0% most complex and difficult part when you edit<00:07:15.400> your<00:07:15.910> own<00:07:16.180> proteges<00:07:16.860> but<00:07:17.860> if<00:07:18.490> you<00:07:18.760> be 00:07:19.020 --> 00:07:19.030 align:start position:0% edit your own proteges but if you be 00:07:19.030 --> 00:07:20.850 align:start position:0% edit your own proteges but if you be reached<00:07:19.240> on<00:07:19.480> the<00:07:19.660> substrate<00:07:20.080> oh<00:07:20.320> you<00:07:20.410> don't 00:07:20.850 --> 00:07:20.860 align:start position:0% reached on the substrate oh you don't 00:07:20.860 --> 00:07:24.240 align:start position:0% reached on the substrate oh you don't need<00:07:21.310> to<00:07:21.840> implement<00:07:22.840> disease<00:07:23.320> in<00:07:23.500> compressed 00:07:24.240 --> 00:07:24.250 align:start position:0% need to implement disease in compressed 00:07:24.250 --> 00:07:27.420 align:start position:0% need to implement disease in compressed complex<00:07:25.030> component<00:07:25.810> so<00:07:26.530> all<00:07:26.680> you<00:07:26.920> need<00:07:27.130> to<00:07:27.190> do 00:07:27.420 --> 00:07:27.430 align:start position:0% complex component so all you need to do 00:07:27.430 --> 00:07:30.300 align:start position:0% complex component so all you need to do is<00:07:27.580> that<00:07:27.790> you<00:07:27.850> just<00:07:28.150> build<00:07:28.840> some<00:07:29.800> substrate 00:07:30.300 --> 00:07:30.310 align:start position:0% is that you just build some substrate 00:07:30.310 --> 00:07:37.080 align:start position:0% is that you just build some substrate modules<00:07:30.760> and<00:07:31.290> substrate<00:07:32.290> ranting<00:07:34.260> and<00:07:36.090> this 00:07:37.080 --> 00:07:37.090 align:start position:0% modules and substrate ranting and this 00:07:37.090 --> 00:07:40.080 align:start position:0% modules and substrate ranting and this is<00:07:37.210> the<00:07:37.420> white<00:07:38.170> to<00:07:38.820> configure<00:07:39.820> the<00:07:39.880> sensor 00:07:40.080 --> 00:07:40.090 align:start position:0% is the white to configure the sensor 00:07:40.090 --> 00:07:44.240 align:start position:0% is the white to configure the sensor modules<00:07:40.810> into<00:07:41.140> the<00:07:41.850> substrate<00:07:42.850> want<00:07:43.240> em 00:07:44.240 --> 00:07:44.250 align:start position:0% modules into the substrate want em 00:07:44.250 --> 00:07:47.280 align:start position:0% modules into the substrate want em they're<00:07:45.250> a<00:07:45.310> bunch<00:07:45.550> of<00:07:45.760> substrate<00:07:46.360> modules<00:07:46.870> and 00:07:47.280 --> 00:07:47.290 align:start position:0% they're a bunch of substrate modules and 00:07:47.290 --> 00:07:50.220 align:start position:0% they're a bunch of substrate modules and this<00:07:47.500> though<00:07:48.400> each<00:07:48.640> module<00:07:49.120> provides<00:07:50.050> a 00:07:50.220 --> 00:07:50.230 align:start position:0% this though each module provides a 00:07:50.230 --> 00:07:56.340 align:start position:0% this though each module provides a specific<00:07:50.820> features<00:07:51.820> such<00:07:52.810> as<00:07:54.780> the<00:07:55.780> timestamp 00:07:56.340 --> 00:07:56.350 align:start position:0% specific features such as the timestamp 00:07:56.350 --> 00:07:58.650 align:start position:0% specific features such as the timestamp module<00:07:56.650> provides<00:07:57.100> just<00:07:57.340> a<00:07:57.460> text<00:07:57.850> and<00:07:58.060> we 00:07:58.650 --> 00:07:58.660 align:start position:0% module provides just a text and we 00:07:58.660 --> 00:08:01.590 align:start position:0% module provides just a text and we deserve<00:07:59.280> approaching<00:08:00.280> and<00:08:00.490> the<00:08:01.120> parentage 00:08:01.590 --> 00:08:01.600 align:start position:0% deserve approaching and the parentage 00:08:01.600 --> 00:08:03.630 align:start position:0% deserve approaching and the parentage module<00:08:01.960> provides<00:08:02.380> the<00:08:02.590> amazing<00:08:03.160> the<00:08:03.310> fancy 00:08:03.630 --> 00:08:03.640 align:start position:0% module provides the amazing the fancy 00:08:03.640 --> 00:08:05.660 align:start position:0% module provides the amazing the fancy process<00:08:04.030> the<00:08:04.360> production<00:08:04.780> system<00:08:05.320> and 00:08:05.660 --> 00:08:05.670 align:start position:0% process the production system and 00:08:05.670 --> 00:08:10.260 align:start position:0% process the production system and especially<00:08:06.670> you<00:08:07.090> know<00:08:07.150> and<00:08:07.690> we<00:08:08.280> provided<00:08:09.280> some 00:08:10.260 --> 00:08:10.270 align:start position:0% especially you know and we provided some 00:08:10.270 --> 00:08:14.030 align:start position:0% especially you know and we provided some Travis<00:08:10.690> it<00:08:10.840> was<00:08:11.020> focusing<00:08:11.620> modules<00:08:12.240> such<00:08:13.240> as<00:08:13.270> a 00:08:14.030 --> 00:08:14.040 align:start position:0% Travis it was focusing modules such as a 00:08:14.040 --> 00:08:16.560 align:start position:0% Travis it was focusing modules such as a bankrupted<00:08:15.040> parties<00:08:15.640> module<00:08:15.940> provides<00:08:16.360> the 00:08:16.560 --> 00:08:16.570 align:start position:0% bankrupted parties module provides the 00:08:16.570 --> 00:08:19.310 align:start position:0% bankrupted parties module provides the white<00:08:17.200> is<00:08:17.500> a<00:08:17.620> confidential<00:08:18.130> transpose<00:08:18.850> into 00:08:19.310 --> 00:08:19.320 align:start position:0% white is a confidential transpose into 00:08:19.320 --> 00:08:22.200 align:start position:0% white is a confidential transpose into one<00:08:20.320> time<00:08:20.560> and<00:08:20.890> animus<00:08:21.400> policies<00:08:21.850> module 00:08:22.200 --> 00:08:22.210 align:start position:0% one time and animus policies module 00:08:22.210 --> 00:08:25.260 align:start position:0% one time and animus policies module provides<00:08:22.770> management<00:08:23.770> was<00:08:24.130> passed<00:08:24.430> into<00:08:24.970> the 00:08:25.260 --> 00:08:25.270 align:start position:0% provides management was passed into the 00:08:25.270 --> 00:08:28.000 align:start position:0% provides management was passed into the water 00:08:28.000 --> 00:08:28.010 align:start position:0% water 00:08:28.010 --> 00:08:31.480 align:start position:0% water and<00:08:28.250> the<00:08:28.960> this<00:08:29.960> is<00:08:30.140> a<00:08:30.170> self<00:08:30.530> chance<00:08:30.770> variables 00:08:31.480 --> 00:08:31.490 align:start position:0% and the this is a self chance variables 00:08:31.490 --> 00:08:34.750 align:start position:0% and the this is a self chance variables again<00:08:32.450> we<00:08:32.630> are<00:08:32.750> toppled<00:08:33.110> on<00:08:33.520> service<00:08:34.520> right 00:08:34.750 --> 00:08:34.760 align:start position:0% again we are toppled on service right 00:08:34.760 --> 00:08:37.620 align:start position:0% again we are toppled on service right and<00:08:36.010> xeljanz 00:08:37.620 --> 00:08:37.630 align:start position:0% and xeljanz 00:08:37.630 --> 00:08:40.210 align:start position:0% and xeljanz architecture<00:08:38.630> is<00:08:38.900> a<00:08:38.930> permutation<00:08:39.410> of<00:08:39.919> the 00:08:40.210 --> 00:08:40.220 align:start position:0% architecture is a permutation of the 00:08:40.220 --> 00:08:43.870 align:start position:0% architecture is a permutation of the laser<00:08:40.550> and<00:08:41.710> also<00:08:42.710> who<00:08:42.860> is<00:08:42.919> a<00:08:43.130> teacher<00:08:43.460> snacks 00:08:43.870 --> 00:08:43.880 align:start position:0% laser and also who is a teacher snacks 00:08:43.880 --> 00:08:48.520 align:start position:0% laser and also who is a teacher snacks as<00:08:44.180> as<00:08:44.390> a<00:08:44.420> knowledge<00:08:44.930> proving<00:08:45.350> systems<00:08:45.800> and<00:08:47.530> we 00:08:48.520 --> 00:08:48.530 align:start position:0% as as a knowledge proving systems and we 00:08:48.530 --> 00:08:51.850 align:start position:0% as as a knowledge proving systems and we can<00:08:48.770> on<00:08:49.700> top<00:08:49.760> of<00:08:50.150> it<00:08:50.270> we<00:08:50.510> can<00:08:50.720> build<00:08:51.050> privacy 00:08:51.850 --> 00:08:51.860 align:start position:0% can on top of it we can build privacy 00:08:51.860 --> 00:08:54.130 align:start position:0% can on top of it we can build privacy oriented<00:08:52.280> applications<00:08:53.030> of<00:08:53.270> intelligent 00:08:54.130 --> 00:08:54.140 align:start position:0% oriented applications of intelligent 00:08:54.140 --> 00:08:57.070 align:start position:0% oriented applications of intelligent protocol<00:08:54.590> such<00:08:55.580> as<00:08:55.640> a<00:08:55.820> confidential<00:08:56.390> and 00:08:57.070 --> 00:08:57.080 align:start position:0% protocol such as a confidential and 00:08:57.080 --> 00:09:01.000 align:start position:0% protocol such as a confidential and animals<00:08:57.590> payment<00:08:57.980> applications<00:08:58.730> and<00:09:00.010> privacy 00:09:01.000 --> 00:09:01.010 align:start position:0% animals payment applications and privacy 00:09:01.010 --> 00:09:02.650 align:start position:0% animals payment applications and privacy features<00:09:01.520> financial<00:09:02.210> statement 00:09:02.650 --> 00:09:02.660 align:start position:0% features financial statement 00:09:02.660 --> 00:09:04.600 align:start position:0% features financial statement applications<00:09:03.410> of<00:09:03.620> the<00:09:03.890> portage<00:09:04.310> urgent 00:09:04.600 --> 00:09:04.610 align:start position:0% applications of the portage urgent 00:09:04.610 --> 00:09:14.110 align:start position:0% applications of the portage urgent protocol<00:09:07.150> and<00:09:09.460> what<00:09:10.460> it<00:09:10.610> is<00:09:11.170> this<00:09:12.170> is<00:09:12.650> a<00:09:13.120> paper 00:09:14.110 --> 00:09:14.120 align:start position:0% protocol and what it is this is a paper 00:09:14.120 --> 00:09:17.110 align:start position:0% protocol and what it is this is a paper published<00:09:14.390> by<00:09:14.920> when<00:09:15.920> experience<00:09:16.460> after<00:09:16.550> in 00:09:17.110 --> 00:09:17.120 align:start position:0% published by when experience after in 00:09:17.120 --> 00:09:21.100 align:start position:0% published by when experience after in earlier<00:09:17.840> this<00:09:18.050> year<00:09:18.110> and<00:09:18.770> it<00:09:19.730> is<00:09:19.790> allowed<00:09:20.300> rest 00:09:21.100 --> 00:09:21.110 align:start position:0% earlier this year and it is allowed rest 00:09:21.110 --> 00:09:23.370 align:start position:0% earlier this year and it is allowed rest area<00:09:21.380> Church<00:09:21.980> free<00:09:22.370> decentralized<00:09:23.030> and 00:09:23.370 --> 00:09:23.380 align:start position:0% area Church free decentralized and 00:09:23.380 --> 00:09:25.930 align:start position:0% area Church free decentralized and conformational<00:09:24.380> payment<00:09:24.830> memorizing<00:09:25.340> all 00:09:25.930 --> 00:09:25.940 align:start position:0% conformational payment memorizing all 00:09:25.940 --> 00:09:28.360 align:start position:0% conformational payment memorizing all that<00:09:26.180> isn't<00:09:26.840> always<00:09:27.020> a<00:09:27.170> smart<00:09:27.500> contract<00:09:28.070> or 00:09:28.360 --> 00:09:28.370 align:start position:0% that isn't always a smart contract or 00:09:28.370 --> 00:09:33.340 align:start position:0% that isn't always a smart contract or form<00:09:29.090> and<00:09:29.890> the<00:09:30.970> basic<00:09:31.970> idea<00:09:32.240> is<00:09:32.270> that<00:09:32.420> common 00:09:33.340 --> 00:09:33.350 align:start position:0% form and the basic idea is that common 00:09:33.350 --> 00:09:35.830 align:start position:0% form and the basic idea is that common fix<00:09:33.590> deep<00:09:34.190> encryption<00:09:34.880> scheme<00:09:35.150> hide<00:09:35.390> or 00:09:35.830 --> 00:09:35.840 align:start position:0% fix deep encryption scheme hide or 00:09:35.840 --> 00:09:40.150 align:start position:0% fix deep encryption scheme hide or transfer<00:09:36.650> amount<00:09:37.010> and<00:09:37.310> conferences<00:09:38.090> and<00:09:39.160> also 00:09:40.150 --> 00:09:40.160 align:start position:0% transfer amount and conferences and also 00:09:40.160 --> 00:09:43.120 align:start position:0% transfer amount and conferences and also it<00:09:40.400> takes<00:09:40.670> a<00:09:40.910> tanto<00:09:41.270> based<00:09:41.450> approach<00:09:41.930> for<00:09:42.530> some 00:09:43.120 --> 00:09:43.130 align:start position:0% it takes a tanto based approach for some 00:09:43.130 --> 00:09:46.570 align:start position:0% it takes a tanto based approach for some reason<00:09:43.490> observation<00:09:44.330> CSM<00:09:45.140> usability<00:09:45.800> and 00:09:46.570 --> 00:09:46.580 align:start position:0% reason observation CSM usability and 00:09:46.580 --> 00:09:49.000 align:start position:0% reason observation CSM usability and thus<00:09:47.300> all<00:09:47.480> video<00:09:47.780> quality<00:09:48.010> music 00:09:49.000 --> 00:09:49.010 align:start position:0% thus all video quality music 00:09:49.010 --> 00:09:53.130 align:start position:0% thus all video quality music circulations<00:09:49.760> in<00:09:50.090> don't<00:09:50.330> change<00:09:50.690> and<00:09:51.400> the 00:09:53.130 --> 00:09:53.140 align:start position:0% circulations in don't change and the 00:09:53.140 --> 00:09:55.840 align:start position:0% circulations in don't change and the result<00:09:54.140> is<00:09:54.260> I<00:09:54.470> used<00:09:54.680> is<00:09:54.830> a<00:09:54.860> sigma<00:09:55.220> brent<00:09:55.610> of 00:09:55.840 --> 00:09:55.850 align:start position:0% result is I used is a sigma brent of 00:09:55.850 --> 00:09:57.610 align:start position:0% result is I used is a sigma brent of called 00:09:57.610 --> 00:09:57.620 align:start position:0% called 00:09:57.620 --> 00:09:59.950 align:start position:0% called signal<00:09:58.220> printer<00:09:58.580> which<00:09:58.760> is<00:09:58.940> find<00:09:59.540> out<00:09:59.720> that 00:09:59.950 --> 00:09:59.960 align:start position:0% signal printer which is find out that 00:09:59.960 --> 00:10:03.000 align:start position:0% signal printer which is find out that they<00:10:00.140> are<00:10:00.170> not<00:10:00.290> building<00:10:00.620> systems<00:10:01.240> but<00:10:02.240> we<00:10:02.630> use 00:10:03.000 --> 00:10:03.010 align:start position:0% they are not building systems but we use 00:10:03.010 --> 00:10:07.720 align:start position:0% they are not building systems but we use instead<00:10:04.150> it<00:10:05.150> is<00:10:05.180> next<00:10:06.340> now<00:10:07.340> the<00:10:07.400> statement 00:10:07.720 --> 00:10:07.730 align:start position:0% instead it is next now the statement 00:10:07.730 --> 00:10:09.790 align:start position:0% instead it is next now the statement itself<00:10:08.270> that<00:10:08.600> they<00:10:08.690> just<00:10:08.840> not<00:10:09.080> sell<00:10:09.380> based<00:10:09.590> on 00:10:09.790 --> 00:10:09.800 align:start position:0% itself that they just not sell based on 00:10:09.800 --> 00:10:14.700 align:start position:0% itself that they just not sell based on teaser<00:10:10.220> vertical<00:10:11.620> permeability<00:10:12.620> just<00:10:13.370> max 00:10:14.700 --> 00:10:14.710 align:start position:0% teaser vertical permeability just max 00:10:14.710 --> 00:10:17.530 align:start position:0% teaser vertical permeability just max because<00:10:15.710> one<00:10:16.250> of<00:10:16.340> the<00:10:16.430> problem<00:10:16.880> of<00:10:17.150> the 00:10:17.530 --> 00:10:17.540 align:start position:0% because one of the problem of the 00:10:17.540 --> 00:10:21.160 align:start position:0% because one of the problem of the anonymity<00:10:18.230> say<00:10:18.740> it's<00:10:18.980> so<00:10:19.280> expensive<00:10:19.810> so<00:10:20.810> we 00:10:21.160 --> 00:10:21.170 align:start position:0% anonymity say it's so expensive so we 00:10:21.170 --> 00:10:27.530 align:start position:0% anonymity say it's so expensive so we want<00:10:21.410> to<00:10:21.620> work<00:10:22.390> small<00:10:23.390> troops<00:10:23.840> and<00:10:25.930> shelter 00:10:27.530 --> 00:10:27.540 align:start position:0% want to work small troops and shelter 00:10:27.540 --> 00:10:29.960 align:start position:0% want to work small troops and shelter verifications<00:10:28.410> in<00:10:28.829> Internet<00:10:29.399> services<00:10:29.759> in 00:10:29.960 --> 00:10:29.970 align:start position:0% verifications in Internet services in 00:10:29.970 --> 00:10:33.170 align:start position:0% verifications in Internet services in our<00:10:30.120> competition<00:10:30.690> and<00:10:31.490> also<00:10:32.490> the<00:10:32.639> distance<00:10:32.820> as 00:10:33.170 --> 00:10:33.180 align:start position:0% our competition and also the distance as 00:10:33.180 --> 00:10:36.170 align:start position:0% our competition and also the distance as a<00:10:33.529> great<00:10:34.529> community<00:10:35.040> and<00:10:35.070> a<00:10:35.370> lot<00:10:35.399> of<00:10:35.610> project 00:10:36.170 --> 00:10:36.180 align:start position:0% a great community and a lot of project 00:10:36.180 --> 00:10:39.050 align:start position:0% a great community and a lot of project using<00:10:36.540> as<00:10:36.660> it<00:10:36.810> effects<00:10:37.350> libraries<00:10:37.889> and<00:10:38.190> their 00:10:39.050 --> 00:10:39.060 align:start position:0% using as it effects libraries and their 00:10:39.060 --> 00:10:42.170 align:start position:0% using as it effects libraries and their existing<00:10:39.720> that<00:10:39.870> what<00:10:40.079> was<00:10:40.350> a<00:10:41.180> awesome 00:10:42.170 --> 00:10:42.180 align:start position:0% existing that what was a awesome 00:10:42.180 --> 00:10:46.160 align:start position:0% existing that what was a awesome libraries<00:10:43.139> for<00:10:43.440> they<00:10:43.740> just<00:10:43.949> next<00:10:44.839> but<00:10:45.839> as<00:10:46.019> you 00:10:46.160 --> 00:10:46.170 align:start position:0% libraries for they just next but as you 00:10:46.170 --> 00:10:48.829 align:start position:0% libraries for they just next but as you know<00:10:46.380> one<00:10:47.009> of<00:10:47.250> the<00:10:47.550> downside<00:10:48.000> is<00:10:48.300> a<00:10:48.329> necessity 00:10:48.829 --> 00:10:48.839 align:start position:0% know one of the downside is a necessity 00:10:48.839 --> 00:10:52.249 align:start position:0% know one of the downside is a necessity of<00:10:49.380> the<00:10:49.620> Transit<00:10:50.009> Center<00:10:50.040> and<00:10:50.970> the<00:10:51.839> practice 00:10:52.249 --> 00:10:52.259 align:start position:0% of the Transit Center and the practice 00:10:52.259 --> 00:10:54.410 align:start position:0% of the Transit Center and the practice tests<00:10:52.529> and<00:10:52.649> there<00:10:53.250> are<00:10:53.370> some<00:10:53.550> solutions<00:10:53.910> and 00:10:54.410 --> 00:10:54.420 align:start position:0% tests and there are some solutions and 00:10:54.420 --> 00:10:59.350 align:start position:0% tests and there are some solutions and some<00:10:54.630> applications<00:10:55.819> turn<00:10:56.819> to<00:10:57.779> the<00:10:58.339> transitive 00:10:59.350 --> 00:10:59.360 align:start position:0% some applications turn to the transitive 00:10:59.360 --> 00:11:01.309 align:start position:0% some applications turn to the transitive one<00:11:00.360> thing<00:11:00.540> it's<00:11:00.690> at<00:11:00.839> much<00:11:01.050> much 00:11:01.309 --> 00:11:01.319 align:start position:0% one thing it's at much much 00:11:01.319 --> 00:11:03.499 align:start position:0% one thing it's at much much computational<00:11:02.130> which<00:11:02.430> is<00:11:02.579> to<00:11:02.759> by<00:11:03.000> the<00:11:03.060> Zetas 00:11:03.499 --> 00:11:03.509 align:start position:0% computational which is to by the Zetas 00:11:03.509 --> 00:11:08.030 align:start position:0% computational which is to by the Zetas protocol<00:11:04.019> and<00:11:05.120> some<00:11:06.120> Universal<00:11:06.839> and<00:11:07.139> updated 00:11:08.030 --> 00:11:08.040 align:start position:0% protocol and some Universal and updated 00:11:08.040 --> 00:11:11.360 align:start position:0% protocol and some Universal and updated service<00:11:08.490> so<00:11:08.850> which<00:11:09.810> is<00:11:09.990> a<00:11:10.470> lot<00:11:10.769> of<00:11:10.889> researchers 00:11:11.360 --> 00:11:11.370 align:start position:0% service so which is a lot of researchers 00:11:11.370 --> 00:11:17.780 align:start position:0% service so which is a lot of researchers in<00:11:11.639> Germany<00:11:12.170> century<00:11:15.529> and<00:11:16.529> how<00:11:17.009> it<00:11:17.069> works<00:11:17.399> are 00:11:17.780 --> 00:11:17.790 align:start position:0% in Germany century and how it works are 00:11:17.790 --> 00:11:19.840 align:start position:0% in Germany century and how it works are actually<00:11:18.300> in<00:11:18.420> the<00:11:18.660> confidential 00:11:19.840 --> 00:11:19.850 align:start position:0% actually in the confidential 00:11:19.850 --> 00:11:24.139 align:start position:0% actually in the confidential transposition<00:11:21.350> read<00:11:22.350> six<00:11:22.709> simple<00:11:23.220> cases<00:11:23.579> so 00:11:24.139 --> 00:11:24.149 align:start position:0% transposition read six simple cases so 00:11:24.149 --> 00:11:26.480 align:start position:0% transposition read six simple cases so re<00:11:24.600> standard<00:11:25.230> include<00:11:25.829> the<00:11:26.009> three<00:11:26.190> coins 00:11:26.480 --> 00:11:26.490 align:start position:0% re standard include the three coins 00:11:26.490 --> 00:11:30.379 align:start position:0% re standard include the three coins table<00:11:26.970> so<00:11:27.839> here<00:11:28.529> we<00:11:28.709> are<00:11:28.740> take<00:11:29.670> is<00:11:29.819> a<00:11:29.910> catalyzer 00:11:30.379 --> 00:11:30.389 align:start position:0% table so here we are take is a catalyzer 00:11:30.389 --> 00:11:33.500 align:start position:0% table so here we are take is a catalyzer process<00:11:30.930> or<00:11:31.110> one<00:11:31.319> share<00:11:31.529> a<00:11:31.680> we<00:11:32.180> re<00:11:33.180> starting 00:11:33.500 --> 00:11:33.510 align:start position:0% process or one share a we re starting 00:11:33.510 --> 00:11:35.900 align:start position:0% process or one share a we re starting point<00:11:34.199> and<00:11:34.440> the<00:11:34.709> board<00:11:34.889> has<00:11:35.220> five<00:11:35.610> points 00:11:35.900 --> 00:11:35.910 align:start position:0% point and the board has five points 00:11:35.910 --> 00:11:39.050 align:start position:0% point and the board has five points correctly<00:11:36.810> and<00:11:37.160> but<00:11:38.160> obviously<00:11:38.639> to<00:11:38.850> be 00:11:39.050 --> 00:11:39.060 align:start position:0% correctly and but obviously to be 00:11:39.060 --> 00:11:40.639 align:start position:0% correctly and but obviously to be readapted 00:11:40.639 --> 00:11:40.649 align:start position:0% readapted 00:11:40.649 --> 00:11:44.420 align:start position:0% readapted everyone<00:11:41.370> see<00:11:41.670> how<00:11:42.029> much<00:11:42.510> they<00:11:42.810> have<00:11:42.839> now<00:11:43.430> so 00:11:44.420 --> 00:11:44.430 align:start position:0% everyone see how much they have now so 00:11:44.430 --> 00:11:45.620 align:start position:0% everyone see how much they have now so if<00:11:44.610> you<00:11:44.699> don't<00:11:44.850> have<00:11:44.940> to<00:11:45.029> have<00:11:45.240> it 00:11:45.620 --> 00:11:45.630 align:start position:0% if you don't have to have it 00:11:45.630 --> 00:11:48.889 align:start position:0% if you don't have to have it we<00:11:45.990> need<00:11:46.139> to<00:11:46.290> encrypt<00:11:46.589> it<00:11:46.920> those<00:11:47.190> a<00:11:47.579> month<00:11:48.000> by 00:11:48.889 --> 00:11:48.899 align:start position:0% we need to encrypt it those a month by 00:11:48.899 --> 00:11:52.540 align:start position:0% we need to encrypt it those a month by the<00:11:48.930> Livity<00:11:49.709> to<00:11:49.829> carry<00:11:50.310> encryption<00:11:50.910> and<00:11:51.199> this 00:11:52.540 --> 00:11:52.550 align:start position:0% the Livity to carry encryption and this 00:11:52.550 --> 00:11:57.829 align:start position:0% the Livity to carry encryption and this missions<00:11:53.550> team<00:11:54.000> has<00:11:54.870> a<00:11:54.899> home<00:11:55.230> for<00:11:55.709> body<00:11:56.180> so<00:11:57.180> we 00:11:57.829 --> 00:11:57.839 align:start position:0% missions team has a home for body so we 00:11:57.839 --> 00:12:01.370 align:start position:0% missions team has a home for body so we can<00:11:57.870> calculate<00:11:58.800> to<00:11:59.220> be<00:11:59.339> the<00:11:59.399> encrypted<00:11:59.940> way<00:12:00.380> so 00:12:01.370 --> 00:12:01.380 align:start position:0% can calculate to be the encrypted way so 00:12:01.380 --> 00:12:05.639 align:start position:0% can calculate to be the encrypted way so very<00:12:01.800> stable<00:12:02.269> and<00:12:03.269> it<00:12:03.630> is<00:12:03.750> very<00:12:04.160> constituent 00:12:05.639 --> 00:12:05.649 align:start position:0% very stable and it is very constituent 00:12:05.649 --> 00:12:09.600 align:start position:0% very stable and it is very constituent transaction<00:12:06.579> and<00:12:06.670> this<00:12:07.509> so<00:12:07.839> this<00:12:08.740> is<00:12:09.100> a 00:12:09.600 --> 00:12:09.610 align:start position:0% transaction and this so this is a 00:12:09.610 --> 00:12:13.980 align:start position:0% transaction and this so this is a materiality<00:12:10.360> the<00:12:11.160> public<00:12:12.300> balances<00:12:13.300> and<00:12:13.600> some 00:12:13.980 --> 00:12:13.990 align:start position:0% materiality the public balances and some 00:12:13.990 --> 00:12:15.769 align:start position:0% materiality the public balances and some selected<00:12:14.589> fountain 00:12:15.769 --> 00:12:15.779 align:start position:0% selected fountain 00:12:15.779 --> 00:12:22.069 align:start position:0% selected fountain heiresses<00:12:16.779> balances<00:12:17.290> and<00:12:19.949> we<00:12:20.949> can<00:12:21.160> calculate 00:12:22.069 --> 00:12:22.079 align:start position:0% heiresses balances and we can calculate 00:12:22.079 --> 00:12:26.910 align:start position:0% heiresses balances and we can calculate function<00:12:23.079> with<00:12:23.679> ourself<00:12:24.129> of<00:12:24.579> tipped<00:12:24.790> away<00:12:25.920> so 00:12:26.910 --> 00:12:26.920 align:start position:0% function with ourself of tipped away so 00:12:26.920 --> 00:12:29.639 align:start position:0% function with ourself of tipped away so no<00:12:27.579> one<00:12:27.610> cannot<00:12:27.939> see<00:12:28.209> those<00:12:28.420> actual<00:12:28.869> madam 00:12:29.639 --> 00:12:29.649 align:start position:0% no one cannot see those actual madam 00:12:29.649 --> 00:12:32.850 align:start position:0% no one cannot see those actual madam chair<00:12:29.980> and<00:12:30.660> the<00:12:31.660> auspice<00:12:32.019> artist<00:12:32.319> can<00:12:32.529> see<00:12:32.679> how 00:12:32.850 --> 00:12:32.860 align:start position:0% chair and the auspice artist can see how 00:12:32.860 --> 00:12:35.309 align:start position:0% chair and the auspice artist can see how on<00:12:33.100> bass<00:12:33.309> is<00:12:33.579> by<00:12:33.759> using<00:12:33.999> her<00:12:34.360> decryption<00:12:35.139> key 00:12:35.309 --> 00:12:35.319 align:start position:0% on bass is by using her decryption key 00:12:35.319 --> 00:12:39.359 align:start position:0% on bass is by using her decryption key which<00:12:35.529> is<00:12:35.709> one<00:12:36.009> of<00:12:36.279> the<00:12:36.519> private<00:12:37.149> to<00:12:37.240> do<00:12:38.369> so 00:12:39.359 --> 00:12:39.369 align:start position:0% which is one of the private to do so 00:12:39.369 --> 00:12:41.970 align:start position:0% which is one of the private to do so this<00:12:39.639> is<00:12:39.759> a<00:12:39.790> or<00:12:40.569> Robert<00:12:41.170> Scalia<00:12:41.589> or<00:12:41.679> the 00:12:41.970 --> 00:12:41.980 align:start position:0% this is a or Robert Scalia or the 00:12:41.980 --> 00:12:44.840 align:start position:0% this is a or Robert Scalia or the confidential<00:12:42.519> transferring<00:12:43.149> the<00:12:43.300> church<00:12:44.199> and 00:12:44.840 --> 00:12:44.850 align:start position:0% confidential transferring the church and 00:12:44.850 --> 00:12:49.199 align:start position:0% confidential transferring the church and about<00:12:45.850> the<00:12:45.970> problem<00:12:46.329> is<00:12:46.449> that<00:12:47.819> how<00:12:48.819> our 00:12:49.199 --> 00:12:49.209 align:start position:0% about the problem is that how our 00:12:49.209 --> 00:12:52.439 align:start position:0% about the problem is that how our auction<00:12:49.779> knowledge<00:12:50.139> imbalance<00:12:50.829> this<00:12:51.449> anklet 00:12:52.439 --> 00:12:52.449 align:start position:0% auction knowledge imbalance this anklet 00:12:52.449 --> 00:12:58.079 align:start position:0% auction knowledge imbalance this anklet element<00:12:52.929> I<00:12:53.850> mean<00:12:55.559> this<00:12:56.559> so<00:12:56.829> encrypted<00:12:57.459> three 00:12:58.079 --> 00:12:58.089 align:start position:0% element I mean this so encrypted three 00:12:58.089 --> 00:13:00.359 align:start position:0% element I mean this so encrypted three coins<00:12:58.420> it<00:12:58.689> looks<00:12:58.869> actually<00:12:59.170> just<00:12:59.769> sixty<00:13:00.160> forty 00:13:00.359 --> 00:13:00.369 align:start position:0% coins it looks actually just sixty forty 00:13:00.369 --> 00:13:04.350 align:start position:0% coins it looks actually just sixty forty virtually<00:13:00.970> so<00:13:02.339> easily<00:13:03.339> to<00:13:03.819> convince<00:13:04.269> that 00:13:04.350 --> 00:13:04.360 align:start position:0% virtually so easily to convince that 00:13:04.360 --> 00:13:07.309 align:start position:0% virtually so easily to convince that this<00:13:05.100> 60/40<00:13:06.100> by<00:13:06.249> the<00:13:06.309> reins<00:13:06.639> actually 00:13:07.309 --> 00:13:07.319 align:start position:0% this 60/40 by the reins actually 00:13:07.319 --> 00:13:10.639 align:start position:0% this 60/40 by the reins actually encrypted<00:13:08.319> three<00:13:08.559> coins<00:13:08.889> by 00:13:10.639 --> 00:13:10.649 align:start position:0% encrypted three coins by 00:13:10.649 --> 00:13:14.999 align:start position:0% encrypted three coins by corrected<00:13:11.649> correcting<00:13:12.329> encryption<00:13:13.329> key<00:13:14.009> so 00:13:14.999 --> 00:13:15.009 align:start position:0% corrected correcting encryption key so 00:13:15.009 --> 00:13:18.799 align:start position:0% corrected correcting encryption key so your<00:13:15.429> touch<00:13:15.699> is<00:13:16.740> wheels<00:13:17.740> of<00:13:17.889> the<00:13:18.009> conspiracy 00:13:18.799 --> 00:13:18.809 align:start position:0% your touch is wheels of the conspiracy 00:13:18.809 --> 00:13:22.489 align:start position:0% your touch is wheels of the conspiracy because<00:13:19.809> the<00:13:20.379> kiss<00:13:20.559> next<00:13:20.769> basically<00:13:21.429> profile 00:13:22.489 --> 00:13:22.499 align:start position:0% because the kiss next basically profile 00:13:22.499 --> 00:13:25.619 align:start position:0% because the kiss next basically profile provides<00:13:23.499> ample<00:13:23.860> if<00:13:24.129> that<00:13:24.490> statement<00:13:24.939> some 00:13:25.619 --> 00:13:25.629 align:start position:0% provides ample if that statement some 00:13:25.629 --> 00:13:27.739 align:start position:0% provides ample if that statement some statement<00:13:26.139> is<00:13:26.379> actually<00:13:26.800> correct 00:13:27.739 --> 00:13:27.749 align:start position:0% statement is actually correct 00:13:27.749 --> 00:13:32.970 align:start position:0% statement is actually correct so<00:13:28.749> in<00:13:29.139> this<00:13:29.620> confident<00:13:30.429> the<00:13:31.149> statements<00:13:31.990> the 00:13:32.970 --> 00:13:32.980 align:start position:0% so in this confident the statements the 00:13:32.980 --> 00:13:35.129 align:start position:0% so in this confident the statements the transform<00:13:33.819> a<00:13:33.999> tree<00:13:34.240> is<00:13:34.300> within<00:13:34.629> the<00:13:34.870> Buried 00:13:35.129 --> 00:13:35.139 align:start position:0% transform a tree is within the Buried 00:13:35.139 --> 00:13:38.850 align:start position:0% transform a tree is within the Buried arranged<00:13:35.759> so<00:13:36.759> that<00:13:37.019> is<00:13:38.019> not<00:13:38.230> a<00:13:38.259> negative 00:13:38.850 --> 00:13:38.860 align:start position:0% arranged so that is not a negative 00:13:38.860 --> 00:13:43.019 align:start position:0% arranged so that is not a negative amount<00:13:39.129> was<00:13:39.610> not<00:13:39.970> overbroad<00:13:40.449> or<00:13:41.790> Center<00:13:42.790> has 00:13:43.019 --> 00:13:43.029 align:start position:0% amount was not overbroad or Center has 00:13:43.029 --> 00:13:47.220 align:start position:0% amount was not overbroad or Center has an<00:13:43.209> imbalances<00:13:43.870> and<00:13:45.300> it's<00:13:46.300> anchored<00:13:46.839> by<00:13:47.170> the 00:13:47.220 --> 00:13:47.230 align:start position:0% an imbalances and it's anchored by the 00:13:47.230 --> 00:13:50.910 align:start position:0% an imbalances and it's anchored by the great<00:13:47.949> change<00:13:48.279> Shanti<00:13:49.470> so<00:13:50.470> if<00:13:50.649> it<00:13:50.769> is 00:13:50.910 --> 00:13:50.920 align:start position:0% great change Shanti so if it is 00:13:50.920 --> 00:13:55.350 align:start position:0% great change Shanti so if it is statement<00:13:51.759> is<00:13:52.089> actually<00:13:52.600> correct<00:13:52.929> and<00:13:54.360> the 00:13:55.350 --> 00:13:55.360 align:start position:0% statement is actually correct and the 00:13:55.360 --> 00:14:01.310 align:start position:0% statement is actually correct and the snacks<00:13:55.749> not<00:13:56.259> videos 00:14:01.310 --> 00:14:01.320 align:start position:0% 00:14:01.320 --> 00:14:04.250 align:start position:0% and<00:14:02.320> not<00:14:02.470> only<00:14:02.500> research<00:14:03.010> at<00:14:03.250> Immanuel 00:14:04.250 --> 00:14:04.260 align:start position:0% and not only research at Immanuel 00:14:04.260 --> 00:14:08.460 align:start position:0% and not only research at Immanuel sensitive<00:14:05.260> data<00:14:05.500> such<00:14:05.680> as<00:14:05.860> a<00:14:06.040> travesty<00:14:06.790> and<00:14:07.470> if 00:14:08.460 --> 00:14:08.470 align:start position:0% sensitive data such as a travesty and if 00:14:08.470 --> 00:14:10.830 align:start position:0% sensitive data such as a travesty and if the<00:14:08.710> statement<00:14:09.250> object<00:14:09.490> corrected<00:14:10.150> by<00:14:10.630> fire 00:14:10.830 --> 00:14:10.840 align:start position:0% the statement object corrected by fire 00:14:10.840 --> 00:14:13.650 align:start position:0% the statement object corrected by fire function<00:14:11.380> on<00:14:11.590> Jamie<00:14:11.920> test<00:14:12.250> children<00:14:12.570> and<00:14:13.570> the 00:14:13.650 --> 00:14:13.660 align:start position:0% function on Jamie test children and the 00:14:13.660 --> 00:14:20.070 align:start position:0% function on Jamie test children and the camera<00:14:14.020> dead<00:14:14.230> its<00:14:14.440> own<00:14:14.620> collagen<00:14:15.070> and<00:14:19.080> the 00:14:20.070 --> 00:14:20.080 align:start position:0% camera dead its own collagen and the 00:14:20.080 --> 00:14:22.700 align:start position:0% camera dead its own collagen and the case<00:14:20.290> of<00:14:20.500> them<00:14:20.680> and<00:14:20.950> I'm<00:14:21.040> a<00:14:21.160> trans<00:14:21.460> person<00:14:21.690> just 00:14:22.700 --> 00:14:22.710 align:start position:0% case of them and I'm a trans person just 00:14:22.710 --> 00:14:25.470 align:start position:0% case of them and I'm a trans person just that<00:14:23.710> over<00:14:23.920> processes<00:14:24.550> similarities<00:14:25.450> are 00:14:25.470 --> 00:14:25.480 align:start position:0% that over processes similarities are 00:14:25.480 --> 00:14:27.870 align:start position:0% that over processes similarities are confidential<00:14:25.990> to<00:14:26.200> hospital<00:14:26.710> or<00:14:26.980> as<00:14:27.430> I 00:14:27.870 --> 00:14:27.880 align:start position:0% confidential to hospital or as I 00:14:27.880 --> 00:14:31.140 align:start position:0% confidential to hospital or as I explained<00:14:28.810> earlier<00:14:29.520> but<00:14:30.520> the<00:14:30.610> difference<00:14:30.970> is 00:14:31.140 --> 00:14:31.150 align:start position:0% explained earlier but the difference is 00:14:31.150 --> 00:14:34.050 align:start position:0% explained earlier but the difference is that<00:14:31.180> to<00:14:31.870> meet<00:14:32.080> some<00:14:32.800> dummy<00:14:33.070> addresses<00:14:33.790> and 00:14:34.050 --> 00:14:34.060 align:start position:0% that to meet some dummy addresses and 00:14:34.060 --> 00:14:36.810 align:start position:0% that to meet some dummy addresses and Simon<00:14:34.480> and<00:14:34.630> Peter<00:14:34.720> a<00:14:35.290> month<00:14:36.040> will<00:14:36.370> be<00:14:36.490> added 00:14:36.810 --> 00:14:36.820 align:start position:0% Simon and Peter a month will be added 00:14:36.820 --> 00:14:39.780 align:start position:0% Simon and Peter a month will be added into<00:14:37.030> the<00:14:37.350> transactions<00:14:38.350> so<00:14:39.280> this<00:14:39.640> is<00:14:39.760> a 00:14:39.780 --> 00:14:39.790 align:start position:0% into the transactions so this is a 00:14:39.790 --> 00:14:42.350 align:start position:0% into the transactions so this is a similar<00:14:40.060> point<00:14:40.330> to<00:14:40.660> the<00:14:40.960> monitors<00:14:41.890> approach 00:14:42.350 --> 00:14:42.360 align:start position:0% similar point to the monitors approach 00:14:42.360 --> 00:14:47.040 align:start position:0% similar point to the monitors approach because<00:14:43.360> it<00:14:43.780> will<00:14:43.990> be<00:14:44.470> propagated<00:14:45.720> because<00:14:46.720> of 00:14:47.040 --> 00:14:47.050 align:start position:0% because it will be propagated because of 00:14:47.050 --> 00:14:51.420 align:start position:0% because it will be propagated because of the<00:14:47.230> damien<00:14:47.620> data<00:14:48.420> so<00:14:49.420> that's<00:14:50.410> point<00:14:51.010> is<00:14:51.220> that 00:14:51.420 --> 00:14:51.430 align:start position:0% the damien data so that's point is that 00:14:51.430 --> 00:14:53.610 align:start position:0% the damien data so that's point is that other<00:14:52.420> people<00:14:52.870> cannot<00:14:53.110> tell<00:14:53.410> the<00:14:53.590> difference 00:14:53.610 --> 00:14:53.620 align:start position:0% other people cannot tell the difference 00:14:53.620 --> 00:14:57.000 align:start position:0% other people cannot tell the difference between<00:14:54.220> the<00:14:54.810> actual<00:14:55.810> data<00:14:56.320> such<00:14:56.770> as<00:14:56.800> a 00:14:57.000 --> 00:14:57.010 align:start position:0% between the actual data such as a 00:14:57.010 --> 00:15:02.940 align:start position:0% between the actual data such as a recipient<00:14:57.460> and<00:14:58.920> Dominator<00:14:59.920> and<00:15:01.680> as<00:15:02.680> father 00:15:02.940 --> 00:15:02.950 align:start position:0% recipient and Dominator and as father 00:15:02.950 --> 00:15:05.990 align:start position:0% recipient and Dominator and as father launched<00:15:03.550> operation<00:15:04.120> after<00:15:04.510> part<00:15:05.170> finger 00:15:05.990 --> 00:15:06.000 align:start position:0% launched operation after part finger 00:15:06.000 --> 00:15:11.100 align:start position:0% launched operation after part finger which<00:15:07.000> is<00:15:07.590> verifying<00:15:08.590> fraction<00:15:10.110> operating 00:15:11.100 --> 00:15:11.110 align:start position:0% which is verifying fraction operating 00:15:11.110 --> 00:15:13.550 align:start position:0% which is verifying fraction operating the<00:15:11.260> anklet<00:15:11.620> appearances<00:15:12.190> will<00:15:13.180> be 00:15:13.550 --> 00:15:13.560 align:start position:0% the anklet appearances will be 00:15:13.560 --> 00:15:16.290 align:start position:0% the anklet appearances will be calculated<00:15:14.560> in<00:15:14.680> their<00:15:14.890> own<00:15:15.010> chain<00:15:15.280> and<00:15:15.520> these 00:15:16.290 --> 00:15:16.300 align:start position:0% calculated in their own chain and these 00:15:16.300 --> 00:15:22.110 align:start position:0% calculated in their own chain and these changes<00:15:17.290> will<00:15:17.560> be<00:15:17.880> uniformly<00:15:18.880> and<00:15:21.120> this 00:15:22.110 --> 00:15:22.120 align:start position:0% changes will be uniformly and this 00:15:22.120 --> 00:15:25.380 align:start position:0% changes will be uniformly and this encrypted<00:15:22.900> the<00:15:23.620> accoutrement<00:15:24.490> for<00:15:24.850> Damien 00:15:25.380 --> 00:15:25.390 align:start position:0% encrypted the accoutrement for Damien 00:15:25.390 --> 00:15:28.590 align:start position:0% encrypted the accoutrement for Damien disease<00:15:25.660> is<00:15:25.990> actually<00:15:26.820> equal<00:15:27.820> to<00:15:27.880> Jeremiah's 00:15:28.590 --> 00:15:28.600 align:start position:0% disease is actually equal to Jeremiah's 00:15:28.600 --> 00:15:32.070 align:start position:0% disease is actually equal to Jeremiah's so<00:15:29.790> that<00:15:30.790> we<00:15:30.940> address<00:15:31.300> disposal<00:15:31.870> in 00:15:32.070 --> 00:15:32.080 align:start position:0% so that we address disposal in 00:15:32.080 --> 00:15:35.910 align:start position:0% so that we address disposal in authorities<00:15:32.680> will<00:15:32.950> not<00:15:33.280> change<00:15:34.350> the<00:15:35.350> father 00:15:35.910 --> 00:15:35.920 align:start position:0% authorities will not change the father 00:15:35.920 --> 00:15:39.180 align:start position:0% authorities will not change the father Archer<00:15:36.550> balances<00:15:37.200> this<00:15:38.200> is<00:15:38.410> change<00:15:38.800> just<00:15:39.070> to 00:15:39.180 --> 00:15:39.190 align:start position:0% Archer balances this is change just to 00:15:39.190 --> 00:15:44.650 align:start position:0% Archer balances this is change just to save<00:15:39.430> our<00:15:39.610> taste 00:15:44.650 --> 00:15:44.660 align:start position:0% 00:15:44.660 --> 00:15:49.230 align:start position:0% and<00:15:45.110> this<00:15:45.890> is<00:15:46.070> a<00:15:46.100> bench<00:15:46.940> mass<00:15:47.210> I<00:15:47.540> was<00:15:47.840> a<00:15:47.920> surgeon 00:15:49.230 --> 00:15:49.240 align:start position:0% and this is a bench mass I was a surgeon 00:15:49.240 --> 00:15:55.750 align:start position:0% and this is a bench mass I was a surgeon as<00:15:50.240> this<00:15:50.420> is<00:15:50.630> a<00:15:51.910> console<00:15:52.910> right<00:15:53.000> side<00:15:54.520> of<00:15:55.520> the 00:15:55.750 --> 00:15:55.760 align:start position:0% as this is a console right side of the 00:15:55.760 --> 00:15:58.870 align:start position:0% as this is a console right side of the teachers<00:15:56.180> is<00:15:56.960> a<00:15:57.020> constant<00:15:57.770> against<00:15:58.250> an<00:15:58.490> empty 00:15:58.870 --> 00:15:58.880 align:start position:0% teachers is a constant against an empty 00:15:58.880 --> 00:16:01.450 align:start position:0% teachers is a constant against an empty sides<00:15:59.120> because<00:15:59.540> of<00:15:59.720> the<00:16:00.010> accumulated<00:16:01.010> up 00:16:01.450 --> 00:16:01.460 align:start position:0% sides because of the accumulated up 00:16:01.460 --> 00:16:03.960 align:start position:0% sides because of the accumulated up approach<00:16:01.940> or<00:16:02.240> which<00:16:02.420> is<00:16:02.540> I<00:16:02.660> explained<00:16:03.140> earlier 00:16:03.960 --> 00:16:03.970 align:start position:0% approach or which is I explained earlier 00:16:03.970 --> 00:16:07.600 align:start position:0% approach or which is I explained earlier whereas<00:16:04.970> the<00:16:05.180> console<00:16:05.840> rentals<00:16:06.170> ehm<00:16:06.800> groves 00:16:07.600 --> 00:16:07.610 align:start position:0% whereas the console rentals ehm groves 00:16:07.610 --> 00:16:11.290 align:start position:0% whereas the console rentals ehm groves opinion<00:16:08.000> against<00:16:09.190> anonymity<00:16:10.190> size<00:16:10.550> because 00:16:11.290 --> 00:16:11.300 align:start position:0% opinion against anonymity size because 00:16:11.300 --> 00:16:14.710 align:start position:0% opinion against anonymity size because we<00:16:11.840> need<00:16:12.020> to<00:16:12.200> today's<00:16:12.500> show<00:16:12.950> yep<00:16:13.700> it's<00:16:14.480> a 00:16:14.710 --> 00:16:14.720 align:start position:0% we need to today's show yep it's a 00:16:14.720 --> 00:16:18.220 align:start position:0% we need to today's show yep it's a limited<00:16:15.200> size<00:16:15.380> in<00:16:15.650> this<00:16:16.750> foreseeability<00:16:17.750> size 00:16:18.220 --> 00:16:18.230 align:start position:0% limited size in this foreseeability size 00:16:18.230 --> 00:16:24.760 align:start position:0% limited size in this foreseeability size or<00:16:18.950> in<00:16:19.100> this<00:16:19.250> title<00:16:19.580> is<00:16:22.810> our<00:16:23.810> any<00:16:24.290> size<00:16:24.500> is<00:16:24.740> a 00:16:24.760 --> 00:16:24.770 align:start position:0% or in this title is our any size is a 00:16:24.770 --> 00:16:29.650 align:start position:0% or in this title is our any size is a number<00:16:25.570> of<00:16:26.570> the<00:16:26.870> entity<00:16:27.620> sets<00:16:27.890> so<00:16:28.310> in<00:16:28.940> this<00:16:29.210> so 00:16:29.650 --> 00:16:29.660 align:start position:0% number of the entity sets so in this so 00:16:29.660 --> 00:16:36.100 align:start position:0% number of the entity sets so in this so in<00:16:30.050> this<00:16:30.280> features<00:16:31.450> 40 00:16:36.100 --> 00:16:36.110 align:start position:0% 00:16:36.110 --> 00:16:40.120 align:start position:0% in<00:16:38.020> 47<00:16:39.020> in<00:16:39.230> cell<00:16:39.560> 14 00:16:40.120 --> 00:16:40.130 align:start position:0% in 47 in cell 14 00:16:40.130 --> 00:16:47.500 align:start position:0% in 47 in cell 14 yes<00:16:41.000> it's<00:16:41.540> quite<00:16:41.780> smooth<00:16:44.560> yes<00:16:45.560> but<00:16:45.890> I<00:16:46.490> want<00:16:47.360> to 00:16:47.500 --> 00:16:47.510 align:start position:0% yes it's quite smooth yes but I want to 00:16:47.510 --> 00:16:50.140 align:start position:0% yes it's quite smooth yes but I want to come<00:16:47.780> I<00:16:48.200> want<00:16:48.560> to<00:16:48.680> compare<00:16:49.130> that<00:16:49.190> yesterday 00:16:50.140 --> 00:16:50.150 align:start position:0% come I want to compare that yesterday 00:16:50.150 --> 00:16:52.660 align:start position:0% come I want to compare that yesterday just<00:16:50.410> concentrate<00:16:51.410> and<00:16:51.680> object<00:16:52.160> constraints 00:16:52.660 --> 00:16:52.670 align:start position:0% just concentrate and object constraints 00:16:52.670 --> 00:16:59.230 align:start position:0% just concentrate and object constraints so<00:16:52.910> it's<00:16:53.240> a<00:16:53.330> small<00:16:56.320> sum<00:16:57.320> without<00:16:58.010> cause<00:16:58.970> rent 00:16:59.230 --> 00:16:59.240 align:start position:0% so it's a small sum without cause rent 00:16:59.240 --> 00:17:02.260 align:start position:0% so it's a small sum without cause rent of<00:16:59.390> the<00:16:59.480> general<00:17:00.110> in<00:17:00.350> area<00:17:00.620> yesterday<00:17:01.270> sites 00:17:02.260 --> 00:17:02.270 align:start position:0% of the general in area yesterday sites 00:17:02.270 --> 00:17:05.890 align:start position:0% of the general in area yesterday sites so<00:17:03.080> that<00:17:03.730> they'll<00:17:04.730> just<00:17:04.940> consoling<00:17:05.390> context 00:17:05.890 --> 00:17:05.900 align:start position:0% so that they'll just consoling context 00:17:05.900 --> 00:17:09.420 align:start position:0% so that they'll just consoling context over<00:17:06.230> land<00:17:07.240> 26<00:17:08.240> and<00:17:08.510> 27 00:17:09.420 --> 00:17:09.430 align:start position:0% over land 26 and 27 00:17:09.430 --> 00:17:15.720 align:start position:0% over land 26 and 27 so<00:17:10.430> in<00:17:10.880> the<00:17:11.060> just<00:17:12.670> constraint<00:17:13.670> sanity<00:17:14.150> side 00:17:15.720 --> 00:17:15.730 align:start position:0% so in the just constraint sanity side 00:17:15.730 --> 00:17:22.449 align:start position:0% so in the just constraint sanity side the<00:17:17.920> as<00:17:18.920> a<00:17:18.980> reference<00:17:19.640> I<00:17:20.620> decided<00:17:21.620> upon<00:17:22.010> our<00:17:22.160> is 00:17:22.449 --> 00:17:22.459 align:start position:0% the as a reference I decided upon our is 00:17:22.459 --> 00:17:27.520 align:start position:0% the as a reference I decided upon our is a<00:17:22.490> German<00:17:23.390> territory<00:17:23.959> and<00:17:25.570> we<00:17:26.570> can<00:17:26.750> achieve<00:17:26.930> of 00:17:27.520 --> 00:17:27.530 align:start position:0% a German territory and we can achieve of 00:17:27.530 --> 00:17:30.280 align:start position:0% a German territory and we can achieve of searching<00:17:28.070> our<00:17:28.280> children<00:17:28.880> the<00:17:29.630> UH<00:17:29.780> narrative 00:17:30.280 --> 00:17:30.290 align:start position:0% searching our children the UH narrative 00:17:30.290 --> 00:17:34.450 align:start position:0% searching our children the UH narrative feature<00:17:30.590> levels<00:17:31.040> of<00:17:31.490> the<00:17:31.930> mana<00:17:32.930> with<00:17:33.560> half<00:17:34.280> of 00:17:34.450 --> 00:17:34.460 align:start position:0% feature levels of the mana with half of 00:17:34.460 --> 00:17:39.720 align:start position:0% feature levels of the mana with half of the<00:17:34.640> Z<00:17:34.790> just<00:17:34.970> constraint<00:17:35.600> southeast<00:17:37.480> 15,000 00:17:39.720 --> 00:17:39.730 align:start position:0% the Z just constraint southeast 15,000 00:17:39.730 --> 00:17:42.910 align:start position:0% the Z just constraint southeast 15,000 constraint<00:17:40.900> so<00:17:41.900> by<00:17:42.050> the<00:17:42.110> way<00:17:42.260> the<00:17:42.320> constraint 00:17:42.910 --> 00:17:42.920 align:start position:0% constraint so by the way the constraint 00:17:42.920 --> 00:17:46.560 align:start position:0% constraint so by the way the constraint is<00:17:43.250> a<00:17:43.900> computational<00:17:44.980> complexity<00:17:45.980> in<00:17:46.250> the 00:17:46.560 --> 00:17:46.570 align:start position:0% is a computational complexity in the 00:17:46.570 --> 00:17:51.090 align:start position:0% is a computational complexity in the geological<00:17:47.570> thing 00:17:51.090 --> 00:17:51.100 align:start position:0% 00:17:51.100 --> 00:17:54.240 align:start position:0% and<00:17:51.730> the<00:17:52.270> next<00:17:52.660> thing<00:17:52.870> I<00:17:53.020> would<00:17:53.320> like<00:17:53.560> to<00:17:53.980> talk 00:17:54.240 --> 00:17:54.250 align:start position:0% and the next thing I would like to talk 00:17:54.250 --> 00:17:56.340 align:start position:0% and the next thing I would like to talk about<00:17:54.460> is<00:17:54.790> our<00:17:55.030> ability<00:17:55.450> for<00:17:55.840> some<00:17:56.050> privacy 00:17:56.340 --> 00:17:56.350 align:start position:0% about is our ability for some privacy 00:17:56.350 --> 00:17:58.740 align:start position:0% about is our ability for some privacy coins<00:17:56.800> and<00:17:57.070> the<00:17:57.880> name<00:17:58.030> is<00:17:58.270> a<00:17:58.330> selective 00:17:58.740 --> 00:17:58.750 align:start position:0% coins and the name is a selective 00:17:58.750 --> 00:18:01.230 align:start position:0% coins and the name is a selective disclosure<00:17:59.220> because<00:18:00.220> for<00:18:00.880> the<00:18:01.000> other<00:18:01.120> the 00:18:01.230 --> 00:18:01.240 align:start position:0% disclosure because for the other the 00:18:01.240 --> 00:18:03.810 align:start position:0% disclosure because for the other the water<00:18:01.420> usage<00:18:01.660> among<00:18:02.020> some<00:18:02.410> Enterprise<00:18:03.400> usage 00:18:03.810 --> 00:18:03.820 align:start position:0% water usage among some Enterprise usage 00:18:03.820 --> 00:18:08.300 align:start position:0% water usage among some Enterprise usage possibility<00:18:04.690> to<00:18:04.840> so<00:18:05.020> important<00:18:05.590> aspect<00:18:05.950> and 00:18:08.300 --> 00:18:08.310 align:start position:0% possibility to so important aspect and 00:18:08.310 --> 00:18:11.940 align:start position:0% possibility to so important aspect and because<00:18:09.310> they<00:18:10.270> need<00:18:10.540> to<00:18:10.570> comply<00:18:11.410> with<00:18:11.710> some 00:18:11.940 --> 00:18:11.950 align:start position:0% because they need to comply with some 00:18:11.950 --> 00:18:14.340 align:start position:0% because they need to comply with some regulations<00:18:12.550> and<00:18:12.880> to<00:18:13.450> be<00:18:13.570> some<00:18:13.810> protecting 00:18:14.340 --> 00:18:14.350 align:start position:0% regulations and to be some protecting 00:18:14.350 --> 00:18:18.030 align:start position:0% regulations and to be some protecting from<00:18:14.590> the<00:18:14.890> like<00:18:15.760> that<00:18:15.970> money<00:18:16.270> laundering<00:18:17.040> so 00:18:18.030 --> 00:18:18.040 align:start position:0% from the like that money laundering so 00:18:18.040 --> 00:18:21.330 align:start position:0% from the like that money laundering so it<00:18:18.610> means<00:18:18.790> a<00:18:18.970> profit<00:18:19.870> entity<00:18:20.350> should<00:18:20.410> be<00:18:20.830> able 00:18:21.330 --> 00:18:21.340 align:start position:0% it means a profit entity should be able 00:18:21.340 --> 00:18:24.720 align:start position:0% it means a profit entity should be able to<00:18:21.610> or<00:18:22.120> it<00:18:22.390> to<00:18:22.540> certain<00:18:22.930> users<00:18:23.080> maestro<00:18:23.950> in<00:18:24.460> the 00:18:24.720 --> 00:18:24.730 align:start position:0% to or it to certain users maestro in the 00:18:24.730 --> 00:18:29.520 align:start position:0% to or it to certain users maestro in the financials<00:18:25.510> 10<00:18:25.750> videos<00:18:26.080> cases<00:18:27.060> and<00:18:28.530> the 00:18:29.520 --> 00:18:29.530 align:start position:0% financials 10 videos cases and the 00:18:29.530 --> 00:18:32.910 align:start position:0% financials 10 videos cases and the reenter<00:18:29.890> tips<00:18:30.310> as<00:18:30.520> such<00:18:31.470> or<00:18:32.470> it<00:18:32.590> ability 00:18:32.910 --> 00:18:32.920 align:start position:0% reenter tips as such or it ability 00:18:32.920 --> 00:18:34.950 align:start position:0% reenter tips as such or it ability features<00:18:33.310> or<00:18:33.700> we<00:18:34.090> prepare<00:18:34.540> some<00:18:34.720> key 00:18:34.950 --> 00:18:34.960 align:start position:0% features or we prepare some key 00:18:34.960 --> 00:18:37.800 align:start position:0% features or we prepare some key component<00:18:35.560> for<00:18:35.890> getting<00:18:36.880> accountability<00:18:37.600> and 00:18:37.800 --> 00:18:37.810 align:start position:0% component for getting accountability and 00:18:37.810 --> 00:18:41.760 align:start position:0% component for getting accountability and the<00:18:38.650> Apache<00:18:39.250> which<00:18:39.370> appears<00:18:39.930> but<00:18:40.930> importance 00:18:41.760 --> 00:18:41.770 align:start position:0% the Apache which appears but importance 00:18:41.770 --> 00:18:45.960 align:start position:0% the Apache which appears but importance key<00:18:42.370> is<00:18:42.430> this<00:18:42.760> difficulty<00:18:43.600> because<00:18:44.790> all<00:18:45.790> the 00:18:45.960 --> 00:18:45.970 align:start position:0% key is this difficulty because all the 00:18:45.970 --> 00:18:48.450 align:start position:0% key is this difficulty because all the transfer<00:18:46.360> of<00:18:46.390> handle<00:18:46.990> and<00:18:47.200> anklet<00:18:47.920> devices 00:18:48.450 --> 00:18:48.460 align:start position:0% transfer of handle and anklet devices 00:18:48.460 --> 00:18:52.590 align:start position:0% transfer of handle and anklet devices will<00:18:48.670> be<00:18:49.300> encrypted<00:18:49.950> and<00:18:50.970> distinguish<00:18:51.970> aunty 00:18:52.590 --> 00:18:52.600 align:start position:0% will be encrypted and distinguish aunty 00:18:52.600 --> 00:18:57.330 align:start position:0% will be encrypted and distinguish aunty and<00:18:54.240> if<00:18:55.240> user<00:18:55.810> pass<00:18:56.260> this<00:18:56.560> deficient<00:18:56.980> I 00:18:57.330 --> 00:18:57.340 align:start position:0% and if user pass this deficient I 00:18:57.340 --> 00:18:58.970 align:start position:0% and if user pass this deficient I believe<00:18:57.580> she'll<00:18:57.850> be<00:18:58.000> through<00:18:58.180> some<00:18:58.330> monitors 00:18:58.970 --> 00:18:58.980 align:start position:0% believe she'll be through some monitors 00:18:58.980 --> 00:19:02.490 align:start position:0% believe she'll be through some monitors orders<00:18:59.980> can<00:19:00.250> decrypt<00:19:00.670> it<00:19:01.480> by<00:19:01.780> using<00:19:02.050> the<00:19:02.320> stick 00:19:02.490 --> 00:19:02.500 align:start position:0% orders can decrypt it by using the stick 00:19:02.500 --> 00:19:07.740 align:start position:0% orders can decrypt it by using the stick love<00:19:02.710> shopping<00:19:02.980> but<00:19:03.870> the<00:19:04.870> order<00:19:05.230> cannot<00:19:06.750> spend 00:19:07.740 --> 00:19:07.750 align:start position:0% love shopping but the order cannot spend 00:19:07.750 --> 00:19:12.120 align:start position:0% love shopping but the order cannot spend their<00:19:08.110> users<00:19:08.880> coin<00:19:09.880> because<00:19:10.210> they<00:19:11.200> don't<00:19:12.040> have 00:19:12.120 --> 00:19:12.130 align:start position:0% their users coin because they don't have 00:19:12.130 --> 00:19:17.190 align:start position:0% their users coin because they don't have the<00:19:12.400> spending<00:19:13.120> t<00:19:13.360> the<00:19:15.030> decryption<00:19:16.030> t<00:19:16.450> cannot 00:19:17.190 --> 00:19:17.200 align:start position:0% the spending t the decryption t cannot 00:19:17.200 --> 00:19:18.990 align:start position:0% the spending t the decryption t cannot be<00:19:17.440> announced<00:19:17.710> a<00:19:17.980> new<00:19:18.160> key<00:19:18.310> cannot<00:19:18.580> be<00:19:18.730> derived 00:19:18.990 --> 00:19:19.000 align:start position:0% be announced a new key cannot be derived 00:19:19.000 --> 00:19:23.150 align:start position:0% be announced a new key cannot be derived from<00:19:19.330> this<00:19:19.630> equation<00:19:20.440> t 00:19:23.150 --> 00:19:23.160 align:start position:0% 00:19:23.160 --> 00:19:27.290 align:start position:0% I<00:19:23.190> mean<00:19:25.130> so<00:19:26.130> as<00:19:26.400> harmony<00:19:26.700> what<00:19:26.910> is<00:19:27.060> a<00:19:27.090> good 00:19:27.290 --> 00:19:27.300 align:start position:0% I mean so as harmony what is a good 00:19:27.300 --> 00:19:31.550 align:start position:0% I mean so as harmony what is a good point<00:19:27.570> I<00:19:27.960> was<00:19:28.110> a<00:19:28.140> cutter<00:19:28.890> based<00:19:29.160> approach<00:19:30.560> the 00:19:31.550 --> 00:19:31.560 align:start position:0% point I was a cutter based approach the 00:19:31.560 --> 00:19:33.980 align:start position:0% point I was a cutter based approach the factorial<00:19:32.250> thing<00:19:32.460> with<00:19:32.640> a<00:19:32.940> syringe<00:19:33.360> battery 00:19:33.980 --> 00:19:33.990 align:start position:0% factorial thing with a syringe battery 00:19:33.990 --> 00:19:36.470 align:start position:0% factorial thing with a syringe battery because<00:19:34.800> or<00:19:35.220> you<00:19:35.250> can<00:19:35.520> ferment<00:19:35.820> the<00:19:36.090> YouTube 00:19:36.470 --> 00:19:36.480 align:start position:0% because or you can ferment the YouTube 00:19:36.480 --> 00:19:38.630 align:start position:0% because or you can ferment the YouTube so<00:19:36.660> based<00:19:36.840> approach<00:19:37.290> if<00:19:37.590> it<00:19:38.070> is<00:19:38.280> a<00:19:38.400> smart 00:19:38.630 --> 00:19:38.640 align:start position:0% so based approach if it is a smart 00:19:38.640 --> 00:19:43.040 align:start position:0% so based approach if it is a smart contract<00:19:38.880> but<00:19:40.940> it's<00:19:41.940> too<00:19:42.150> expensive<00:19:42.180> and<00:19:42.900> all 00:19:43.040 --> 00:19:43.050 align:start position:0% contract but it's too expensive and all 00:19:43.050 --> 00:19:45.800 align:start position:0% contract but it's too expensive and all you<00:19:43.590> need<00:19:43.800> to<00:19:43.830> all<00:19:44.130> you<00:19:44.400> tics<00:19:44.670> or<00:19:44.820> set<00:19:45.060> and<00:19:45.390> or 00:19:45.800 --> 00:19:45.810 align:start position:0% you need to all you tics or set and or 00:19:45.810 --> 00:19:47.600 align:start position:0% you need to all you tics or set and or Spencer<00:19:46.260> attachments<00:19:46.800> such<00:19:46.950> as<00:19:46.980> a<00:19:47.160> nerd<00:19:47.430> via 00:19:47.600 --> 00:19:47.610 align:start position:0% Spencer attachments such as a nerd via 00:19:47.610 --> 00:19:50.720 align:start position:0% Spencer attachments such as a nerd via data<00:19:47.850> need<00:19:48.270> to<00:19:48.480> be<00:19:48.890> stirred<00:19:49.890> into<00:19:50.190> the<00:19:50.460> smart 00:19:50.720 --> 00:19:50.730 align:start position:0% data need to be stirred into the smart 00:19:50.730 --> 00:19:53.930 align:start position:0% data need to be stirred into the smart contract<00:19:51.350> and<00:19:52.350> also<00:19:52.650> or<00:19:53.100> we<00:19:53.250> can<00:19:53.460> achieve<00:19:53.730> is<00:19:53.910> a 00:19:53.930 --> 00:19:53.940 align:start position:0% contract and also or we can achieve is a 00:19:53.940 --> 00:19:56.570 align:start position:0% contract and also or we can achieve is a confidential<00:19:54.650> cap<00:19:55.650> to<00:19:55.830> talk<00:19:56.040> means<00:19:56.310> that<00:19:56.460> not 00:19:56.570 --> 00:19:56.580 align:start position:0% confidential cap to talk means that not 00:19:56.580 --> 00:20:01.400 align:start position:0% confidential cap to talk means that not the<00:19:56.700> best<00:19:56.820> approach<00:19:57.060> for<00:19:57.950> example<00:19:58.950> or<00:19:59.190> if<00:20:00.410> so 00:20:01.400 --> 00:20:01.410 align:start position:0% the best approach for example or if so 00:20:01.410 --> 00:20:04.340 align:start position:0% the best approach for example or if so if<00:20:01.920> you<00:20:02.190> want<00:20:02.550> to<00:20:02.610> prove<00:20:03.120> that<00:20:03.330> a<00:20:03.570> scout<00:20:03.960> has<00:20:04.290> a 00:20:04.340 --> 00:20:04.350 align:start position:0% if you want to prove that a scout has a 00:20:04.350 --> 00:20:07.760 align:start position:0% if you want to prove that a scout has a security<00:20:04.920> tokens<00:20:05.550> over<00:20:06.270> 4%<00:20:06.630> of<00:20:07.380> the<00:20:07.620> total 00:20:07.760 --> 00:20:07.770 align:start position:0% security tokens over 4% of the total 00:20:07.770 --> 00:20:10.460 align:start position:0% security tokens over 4% of the total supply<00:20:08.070> in<00:20:08.970> a<00:20:09.090> confidential<00:20:09.480> manner<00:20:09.690> but<00:20:10.290> in 00:20:10.460 --> 00:20:10.470 align:start position:0% supply in a confidential manner but in 00:20:10.470 --> 00:20:12.320 align:start position:0% supply in a confidential manner but in the<00:20:10.590> YouTube<00:20:10.920> service<00:20:11.220> approach<00:20:11.580> or<00:20:12.000> you<00:20:12.150> need 00:20:12.320 --> 00:20:12.330 align:start position:0% the YouTube service approach or you need 00:20:12.330 --> 00:20:15.230 align:start position:0% the YouTube service approach or you need to<00:20:12.650> activate<00:20:13.650> the<00:20:13.710> correct<00:20:14.160> order<00:20:14.790> of<00:20:14.970> the 00:20:15.230 --> 00:20:15.240 align:start position:0% to activate the correct order of the 00:20:15.240 --> 00:20:18.080 align:start position:0% to activate the correct order of the YouTube<00:20:15.870> so<00:20:16.050> set<00:20:16.320> on<00:20:16.710> channel<00:20:17.250> so<00:20:17.700> it's<00:20:17.910> too 00:20:18.080 --> 00:20:18.090 align:start position:0% YouTube so set on channel so it's too 00:20:18.090 --> 00:20:23.810 align:start position:0% YouTube so set on channel so it's too expensive<00:20:18.800> and<00:20:21.350> it's<00:20:22.350> easy<00:20:22.800> notice<00:20:23.370> was<00:20:23.640> it 00:20:23.810 --> 00:20:23.820 align:start position:0% expensive and it's easy notice was it 00:20:23.820 --> 00:20:26.390 align:start position:0% expensive and it's easy notice was it went<00:20:24.330> easy<00:20:24.540> to<00:20:24.930> get<00:20:25.290> the<00:20:25.440> automated<00:20:26.010> features 00:20:26.390 --> 00:20:26.400 align:start position:0% went easy to get the automated features 00:20:26.400 --> 00:20:30.050 align:start position:0% went easy to get the automated features in<00:20:26.850> a<00:20:26.970> cut<00:20:27.150> best<00:20:27.420> approach<00:20:27.810> because<00:20:28.940> in<00:20:29.940> the 00:20:30.050 --> 00:20:30.060 align:start position:0% in a cut best approach because in the 00:20:30.060 --> 00:20:32.330 align:start position:0% in a cut best approach because in the YouTube<00:20:30.420> saw<00:20:30.600> best<00:20:30.810> approach<00:20:31.230> alter<00:20:31.920> need<00:20:32.160> to 00:20:32.330 --> 00:20:32.340 align:start position:0% YouTube saw best approach alter need to 00:20:32.340 --> 00:20:35.060 align:start position:0% YouTube saw best approach alter need to try<00:20:32.640> try<00:20:33.150> to<00:20:33.270> distributive<00:20:34.230> over<00:20:34.380> several 00:20:35.060 --> 00:20:35.070 align:start position:0% try try to distributive over several 00:20:35.070 --> 00:20:37.520 align:start position:0% try try to distributive over several days<00:20:35.370> to<00:20:35.430> including<00:20:36.060> their<00:20:36.270> our<00:20:36.420> history<00:20:37.350> of 00:20:37.520 --> 00:20:37.530 align:start position:0% days to including their our history of 00:20:37.530 --> 00:20:41.360 align:start position:0% days to including their our history of the<00:20:37.710> transaction<00:20:38.340> and<00:20:39.060> so<00:20:39.570> it's<00:20:40.160> it's<00:20:41.160> too 00:20:41.360 --> 00:20:41.370 align:start position:0% the transaction and so it's it's too 00:20:41.370 --> 00:20:44.300 align:start position:0% the transaction and so it's it's too expensive<00:20:41.760> and<00:20:42.210> but<00:20:43.020> the<00:20:43.560> counter<00:20:44.100> based 00:20:44.300 --> 00:20:44.310 align:start position:0% expensive and but the counter based 00:20:44.310 --> 00:20:47.600 align:start position:0% expensive and but the counter based approach<00:20:44.750> all<00:20:45.750> it'll<00:20:46.110> just<00:20:46.470> all<00:20:46.980> fetches<00:20:47.490> a 00:20:47.600 --> 00:20:47.610 align:start position:0% approach all it'll just all fetches a 00:20:47.610 --> 00:20:50.360 align:start position:0% approach all it'll just all fetches a specific<00:20:48.120> group<00:20:48.390> or<00:20:48.660> intuitive<00:20:49.440> oxygen<00:20:50.130> forms 00:20:50.360 --> 00:20:50.370 align:start position:0% specific group or intuitive oxygen forms 00:20:50.370 --> 00:20:53.300 align:start position:0% specific group or intuitive oxygen forms abruption<00:20:50.670> Network<00:20:51.210> and<00:20:51.770> difficulty<00:20:52.770> it<00:20:53.040> and 00:20:53.300 --> 00:20:53.310 align:start position:0% abruption Network and difficulty it and 00:20:53.310 --> 00:20:58.090 align:start position:0% abruption Network and difficulty it and we<00:20:53.580> get<00:20:53.760> the<00:20:53.820> single<00:20:54.510> register<00:20:55.080> parent 00:20:58.090 --> 00:20:58.100 align:start position:0% 00:20:58.100 --> 00:21:01.650 align:start position:0% and<00:20:58.640> so<00:20:59.510> you<00:20:59.780> know<00:20:59.960> we<00:21:00.200> are<00:21:00.230> all<00:21:00.650> open<00:21:00.950> salsa 00:21:01.650 --> 00:21:01.660 align:start position:0% and so you know we are all open salsa 00:21:01.660 --> 00:21:04.930 align:start position:0% and so you know we are all open salsa argumentation<00:21:02.660> Hotel<00:21:03.110> champ<00:21:03.380> and<00:21:03.940> implement 00:21:04.930 --> 00:21:04.940 align:start position:0% argumentation Hotel champ and implement 00:21:04.940 --> 00:21:08.050 align:start position:0% argumentation Hotel champ and implement or<00:21:05.060> implementation<00:21:05.810> interpreting<00:21:06.290> last<00:21:07.060> and 00:21:08.050 --> 00:21:08.060 align:start position:0% or implementation interpreting last and 00:21:08.060 --> 00:21:09.700 align:start position:0% or implementation interpreting last and but<00:21:08.330> it's<00:21:08.510> at<00:21:08.720> the<00:21:08.870> development<00:21:09.470> for<00:21:09.680> our 00:21:09.700 --> 00:21:09.710 align:start position:0% but it's at the development for our 00:21:09.710 --> 00:21:12.670 align:start position:0% but it's at the development for our production<00:21:10.190> already<00:21:10.460> or<00:21:11.000> you<00:21:11.150> can<00:21:11.360> check<00:21:11.680> out 00:21:12.670 --> 00:21:12.680 align:start position:0% production already or you can check out 00:21:12.680 --> 00:21:28.330 align:start position:0% production already or you can check out Patriots<00:21:13.310> come<00:21:13.610> -<00:21:14.350> okay<00:21:17.020> so<00:21:18.430> this<00:21:19.430> is<00:21:19.490> a<00:21:19.640> demo 00:21:28.330 --> 00:21:28.340 align:start position:0% 00:21:28.340 --> 00:21:33.820 align:start position:0% oh<00:21:29.650> so<00:21:30.650> we<00:21:30.920> have<00:21:30.950> the<00:21:31.340> several<00:21:32.210> hundred<00:21:32.830> one 00:21:33.820 --> 00:21:33.830 align:start position:0% oh so we have the several hundred one 00:21:33.830 --> 00:21:38.440 align:start position:0% oh so we have the several hundred one thousand<00:21:34.250> points<00:21:34.610> now<00:21:34.820> and<00:21:36.580> best<00:21:37.580> hands<00:21:37.880> has<00:21:38.000> a 00:21:38.440 --> 00:21:38.450 align:start position:0% thousand points now and best hands has a 00:21:38.450 --> 00:21:40.570 align:start position:0% thousand points now and best hands has a logic<00:21:38.960> is<00:21:39.110> a<00:21:39.140> search<00:21:39.740> and<00:21:39.950> not<00:21:40.130> randomly 00:21:40.570 --> 00:21:40.580 align:start position:0% logic is a search and not randomly 00:21:40.580 --> 00:21:43.440 align:start position:0% logic is a search and not randomly lotteries<00:21:41.150> and<00:21:41.390> the<00:21:42.080> rats<00:21:42.290> have<00:21:42.560> is<00:21:42.770> a 00:21:43.440 --> 00:21:43.450 align:start position:0% lotteries and the rats have is a 00:21:43.450 --> 00:21:47.650 align:start position:0% lotteries and the rats have is a whatever<00:21:44.470> desktop<00:21:45.470> client<00:21:46.090> on<00:21:47.090> Lister 00:21:47.650 --> 00:21:47.660 align:start position:0% whatever desktop client on Lister 00:21:47.660 --> 00:21:52.960 align:start position:0% whatever desktop client on Lister granted<00:21:48.880> I'm<00:21:49.880> gonna<00:21:50.240> send<00:21:51.230> a<00:21:51.470> 100<00:21:52.400> points<00:21:52.910> to 00:21:52.960 --> 00:21:52.970 align:start position:0% granted I'm gonna send a 100 points to 00:21:52.970 --> 00:21:56.470 align:start position:0% granted I'm gonna send a 100 points to Aris<00:21:53.450> and<00:21:53.630> submit<00:21:54.320> is<00:21:54.470> an<00:21:54.590> integrated<00:21:55.450> to<00:21:56.450> the 00:21:56.470 --> 00:21:56.480 align:start position:0% Aris and submit is an integrated to the 00:21:56.480 --> 00:21:59.860 align:start position:0% Aris and submit is an integrated to the generally<00:21:57.230> and<00:21:57.730> cementation<00:21:58.730> skin<00:21:59.090> and<00:21:59.720> the 00:21:59.860 --> 00:21:59.870 align:start position:0% generally and cementation skin and the 00:21:59.870 --> 00:22:02.730 align:start position:0% generally and cementation skin and the by<00:22:00.020> five-minute<00:22:00.470> in<00:22:01.070> with<00:22:01.640> internal<00:22:02.210> Chandana 00:22:02.730 --> 00:22:02.740 align:start position:0% by five-minute in with internal Chandana 00:22:02.740 --> 00:22:07.180 align:start position:0% by five-minute in with internal Chandana and<00:22:05.650> transferred<00:22:06.650> amount<00:22:06.920> will<00:22:07.160> be 00:22:07.180 --> 00:22:07.190 align:start position:0% and transferred amount will be 00:22:07.190 --> 00:22:10.350 align:start position:0% and transferred amount will be subtracted<00:22:08.030> from<00:22:08.240> my<00:22:08.740> balances<00:22:09.740> and<00:22:09.980> the 00:22:10.350 --> 00:22:10.360 align:start position:0% subtracted from my balances and the 00:22:10.360 --> 00:22:15.040 align:start position:0% subtracted from my balances and the change<00:22:11.360> that<00:22:12.610> the<00:22:13.610> forward<00:22:13.910> to<00:22:14.180> others<00:22:14.570> into 00:22:15.040 --> 00:22:15.050 align:start position:0% change that the forward to others into 00:22:15.050 --> 00:22:22.670 align:start position:0% change that the forward to others into the<00:22:15.110> best<00:22:15.860> authorities 00:22:22.670 --> 00:22:22.680 align:start position:0% 00:22:22.680 --> 00:22:28.650 align:start position:0% I'll<00:22:23.680> check<00:22:24.040> the<00:22:25.140> origin<00:22:26.140> now<00:22:26.380> let's<00:22:26.830> get<00:22:27.660> 100 00:22:28.650 --> 00:22:28.660 align:start position:0% I'll check the origin now let's get 100 00:22:28.660 --> 00:22:35.810 align:start position:0% I'll check the origin now let's get 100 coins<00:22:30.630> thanks<00:22:31.630> so<00:22:31.690> much 00:22:35.810 --> 00:22:35.820 align:start position:0% 00:22:35.820 --> 00:22:42.410 align:start position:0% [Applause]