WEBVTT Kind: captions Language: en 00:00:00.370 --> 00:00:04.590 align:start position:0% so<00:00:01.270> yeah<00:00:01.720> I'm<00:00:02.050> Liz<00:00:02.469> Steinem<00:00:03.070> gir<00:00:03.330> with<00:00:04.330> least 00:00:04.590 --> 00:00:04.600 align:start position:0% so yeah I'm Liz Steinem gir with least 00:00:04.600 --> 00:00:06.300 align:start position:0% so yeah I'm Liz Steinem gir with least authority<00:00:05.140> I'm<00:00:05.350> going<00:00:05.530> to<00:00:05.590> talk<00:00:05.770> today<00:00:05.980> about 00:00:06.300 --> 00:00:06.310 align:start position:0% authority I'm going to talk today about 00:00:06.310 --> 00:00:08.520 align:start position:0% authority I'm going to talk today about something<00:00:06.790> that<00:00:07.030> we're<00:00:07.180> calling<00:00:07.330> p4<00:00:08.080> because 00:00:08.520 --> 00:00:08.530 align:start position:0% something that we're calling p4 because 00:00:08.530 --> 00:00:09.810 align:start position:0% something that we're calling p4 because we<00:00:08.650> like<00:00:08.800> to<00:00:08.830> play<00:00:09.010> with<00:00:09.220> numbers<00:00:09.550> and<00:00:09.700> letters 00:00:09.810 --> 00:00:09.820 align:start position:0% we like to play with numbers and letters 00:00:09.820 --> 00:00:13.259 align:start position:0% we like to play with numbers and letters and<00:00:10.180> the<00:00:10.720> P<00:00:11.080> the<00:00:11.860> four<00:00:12.099> p's<00:00:12.370> are<00:00:12.730> private 00:00:13.259 --> 00:00:13.269 align:start position:0% and the P the four p's are private 00:00:13.269 --> 00:00:17.250 align:start position:0% and the P the four p's are private periodic<00:00:13.870> payment<00:00:14.410> protocol<00:00:15.010> and<00:00:15.280> so<00:00:16.260> yeah 00:00:17.250 --> 00:00:17.260 align:start position:0% periodic payment protocol and so yeah 00:00:17.260 --> 00:00:18.750 align:start position:0% periodic payment protocol and so yeah just<00:00:17.560> gonna<00:00:17.680> tell<00:00:17.890> you<00:00:18.010> guys<00:00:18.160> about<00:00:18.310> what<00:00:18.580> our 00:00:18.750 --> 00:00:18.760 align:start position:0% just gonna tell you guys about what our 00:00:18.760 --> 00:00:20.850 align:start position:0% just gonna tell you guys about what our work<00:00:19.180> is<00:00:19.300> with<00:00:19.480> this<00:00:19.630> and<00:00:19.930> why<00:00:20.320> we're<00:00:20.529> doing<00:00:20.650> it 00:00:20.850 --> 00:00:20.860 align:start position:0% work is with this and why we're doing it 00:00:20.860 --> 00:00:26.040 align:start position:0% work is with this and why we're doing it so<00:00:23.640> like<00:00:24.640> I<00:00:24.730> said<00:00:24.789> I'm<00:00:25.060> Liz<00:00:25.300> Steinem<00:00:25.750> girl<00:00:25.869> from 00:00:26.040 --> 00:00:26.050 align:start position:0% so like I said I'm Liz Steinem girl from 00:00:26.050 --> 00:00:28.439 align:start position:0% so like I said I'm Liz Steinem girl from least<00:00:26.289> authority<00:00:26.800> we<00:00:27.640> believe<00:00:27.939> that<00:00:28.180> people 00:00:28.439 --> 00:00:28.449 align:start position:0% least authority we believe that people 00:00:28.449 --> 00:00:31.140 align:start position:0% least authority we believe that people have<00:00:28.630> a<00:00:28.689> right<00:00:28.779> to<00:00:29.080> privacy<00:00:29.260> our<00:00:30.029> mission<00:00:31.029> is 00:00:31.140 --> 00:00:31.150 align:start position:0% have a right to privacy our mission is 00:00:31.150 --> 00:00:33.030 align:start position:0% have a right to privacy our mission is to<00:00:31.180> make<00:00:31.300> security<00:00:31.869> easy<00:00:32.079> to<00:00:32.410> use<00:00:32.590> and 00:00:33.030 --> 00:00:33.040 align:start position:0% to make security easy to use and 00:00:33.040 --> 00:00:35.610 align:start position:0% to make security easy to use and available<00:00:33.520> to<00:00:33.670> everyone<00:00:33.940> we<00:00:34.840> help<00:00:35.050> others<00:00:35.380> to 00:00:35.610 --> 00:00:35.620 align:start position:0% available to everyone we help others to 00:00:35.620 --> 00:00:37.500 align:start position:0% available to everyone we help others to improve<00:00:35.770> their<00:00:36.130> technologies<00:00:36.820> to<00:00:37.210> be<00:00:37.329> more 00:00:37.500 --> 00:00:37.510 align:start position:0% improve their technologies to be more 00:00:37.510 --> 00:00:39.840 align:start position:0% improve their technologies to be more secure<00:00:37.870> through<00:00:38.230> security<00:00:38.680> audits<00:00:38.980> of<00:00:39.190> things 00:00:39.840 --> 00:00:39.850 align:start position:0% secure through security audits of things 00:00:39.850 --> 00:00:41.940 align:start position:0% secure through security audits of things like<00:00:40.120> distributed<00:00:40.690> ledger<00:00:41.140> technologies 00:00:41.940 --> 00:00:41.950 align:start position:0% like distributed ledger technologies 00:00:41.950 --> 00:00:44.160 align:start position:0% like distributed ledger technologies blockchain<00:00:42.700> projects<00:00:43.270> and<00:00:43.420> related 00:00:44.160 --> 00:00:44.170 align:start position:0% blockchain projects and related 00:00:44.170 --> 00:00:47.880 align:start position:0% blockchain projects and related cryptographic<00:00:44.559> efforts<00:00:46.290> we<00:00:47.290> also<00:00:47.469> build 00:00:47.880 --> 00:00:47.890 align:start position:0% cryptographic efforts we also build 00:00:47.890 --> 00:00:49.709 align:start position:0% cryptographic efforts we also build technical<00:00:48.430> solutions<00:00:48.969> that<00:00:49.180> incorporate 00:00:49.709 --> 00:00:49.719 align:start position:0% technical solutions that incorporate 00:00:49.719 --> 00:00:52.650 align:start position:0% technical solutions that incorporate these<00:00:49.899> values<00:00:50.350> using<00:00:51.309> things<00:00:51.879> like<00:00:52.000> privacy 00:00:52.650 --> 00:00:52.660 align:start position:0% these values using things like privacy 00:00:52.660 --> 00:00:54.959 align:start position:0% these values using things like privacy by<00:00:52.809> design<00:00:52.950> empowering<00:00:53.950> users<00:00:54.219> to<00:00:54.579> control 00:00:54.959 --> 00:00:54.969 align:start position:0% by design empowering users to control 00:00:54.969 --> 00:00:57.540 align:start position:0% by design empowering users to control their<00:00:55.149> own<00:00:55.270> data<00:00:55.570> and<00:00:55.809> also<00:00:56.800> minimizing<00:00:57.399> the 00:00:57.540 --> 00:00:57.550 align:start position:0% their own data and also minimizing the 00:00:57.550 --> 00:01:00.029 align:start position:0% their own data and also minimizing the access<00:00:58.000> that<00:00:58.449> service<00:00:58.719> providers<00:00:59.320> have<00:00:59.649> to 00:01:00.029 --> 00:01:00.039 align:start position:0% access that service providers have to 00:01:00.039 --> 00:01:02.610 align:start position:0% access that service providers have to the<00:01:00.670> user<00:01:00.820> data<00:01:01.059> or<00:01:01.210> personal<00:01:01.809> data<00:01:02.020> data 00:01:02.610 --> 00:01:02.620 align:start position:0% the user data or personal data data 00:01:02.620 --> 00:01:05.580 align:start position:0% the user data or personal data data minimization<00:01:03.479> we<00:01:04.479> also<00:01:04.659> like<00:01:04.959> to<00:01:05.109> participate 00:01:05.580 --> 00:01:05.590 align:start position:0% minimization we also like to participate 00:01:05.590 --> 00:01:08.340 align:start position:0% minimization we also like to participate with<00:01:05.740> other<00:01:05.950> communities<00:01:06.639> and<00:01:07.139> work<00:01:08.139> together 00:01:08.340 --> 00:01:08.350 align:start position:0% with other communities and work together 00:01:08.350 --> 00:01:16.789 align:start position:0% with other communities and work together on<00:01:08.709> particular<00:01:09.279> efforts<00:01:09.670> to<00:01:09.969> these<00:01:10.119> goals<00:01:10.389> - 00:01:16.789 --> 00:01:16.799 align:start position:0% 00:01:16.799 --> 00:01:19.139 align:start position:0% I'm<00:01:17.799> sorry<00:01:17.950> I<00:01:18.099> just<00:01:18.340> realized<00:01:18.639> my<00:01:18.729> whole<00:01:18.939> slide 00:01:19.139 --> 00:01:19.149 align:start position:0% I'm sorry I just realized my whole slide 00:01:19.149 --> 00:01:27.989 align:start position:0% I'm sorry I just realized my whole slide is<00:01:19.359> not<00:01:19.450> showing<00:01:22.649> technical<00:01:23.649> problems<00:01:26.999> there 00:01:27.989 --> 00:01:27.999 align:start position:0% is not showing technical problems there 00:01:27.999 --> 00:01:31.159 align:start position:0% is not showing technical problems there we<00:01:28.090> go<00:01:28.209> okay<00:01:28.959> so<00:01:29.169> we<00:01:30.159> operate<00:01:30.669> a 00:01:31.159 --> 00:01:31.169 align:start position:0% we go okay so we operate a 00:01:31.169 --> 00:01:34.830 align:start position:0% we go okay so we operate a subscription-based<00:01:32.169> service<00:01:32.700> that's<00:01:33.840> secure 00:01:34.830 --> 00:01:34.840 align:start position:0% subscription-based service that's secure 00:01:34.840 --> 00:01:36.959 align:start position:0% subscription-based service that's secure distributed<00:01:35.380> storage<00:01:35.590> product<00:01:36.159> and<00:01:36.369> we<00:01:36.819> call 00:01:36.959 --> 00:01:36.969 align:start position:0% distributed storage product and we call 00:01:36.969 --> 00:01:39.330 align:start position:0% distributed storage product and we call it<00:01:37.060> s4<00:01:37.479> again<00:01:38.229> we<00:01:38.529> like<00:01:38.679> our<00:01:38.889> letters<00:01:39.159> and 00:01:39.330 --> 00:01:39.340 align:start position:0% it s4 again we like our letters and 00:01:39.340 --> 00:01:42.749 align:start position:0% it s4 again we like our letters and numbers<00:01:39.459> and<00:01:39.849> s4<00:01:40.630> stands<00:01:41.049> for<00:01:41.399> simple<00:01:42.399> secure 00:01:42.749 --> 00:01:42.759 align:start position:0% numbers and s4 stands for simple secure 00:01:42.759 --> 00:01:45.899 align:start position:0% numbers and s4 stands for simple secure storage<00:01:43.119> service<00:01:43.749> and<00:01:44.549> it's<00:01:45.549> built<00:01:45.759> using 00:01:45.899 --> 00:01:45.909 align:start position:0% storage service and it's built using 00:01:45.909 --> 00:01:48.659 align:start position:0% storage service and it's built using open<00:01:46.389> source<00:01:46.739> technology<00:01:47.739> and<00:01:47.979> enables 00:01:48.659 --> 00:01:48.669 align:start position:0% open source technology and enables 00:01:48.669 --> 00:01:50.639 align:start position:0% open source technology and enables client-side<00:01:49.239> encryption<00:01:49.299> so<00:01:50.079> that<00:01:50.200> the<00:01:50.319> users 00:01:50.639 --> 00:01:50.649 align:start position:0% client-side encryption so that the users 00:01:50.649 --> 00:01:52.769 align:start position:0% client-side encryption so that the users can<00:01:50.829> hold<00:01:51.039> the<00:01:51.189> keys<00:01:51.369> to<00:01:51.399> their<00:01:51.669> data<00:01:51.909> not<00:01:52.569> us 00:01:52.769 --> 00:01:52.779 align:start position:0% can hold the keys to their data not us 00:01:52.779 --> 00:01:54.809 align:start position:0% can hold the keys to their data not us one<00:01:53.770> of<00:01:53.799> the<00:01:53.919> projects<00:01:54.369> that<00:01:54.399> it<00:01:54.549> uses<00:01:54.700> that 00:01:54.809 --> 00:01:54.819 align:start position:0% one of the projects that it uses that 00:01:54.819 --> 00:01:57.179 align:start position:0% one of the projects that it uses that you'd<00:01:55.029> eliza's<00:01:55.450> is<00:01:55.659> called<00:01:55.869> Tahoe<00:01:56.259> laughs<00:01:56.649> la 00:01:57.179 --> 00:01:57.189 align:start position:0% you'd eliza's is called Tahoe laughs la 00:01:57.189 --> 00:01:59.339 align:start position:0% you'd eliza's is called Tahoe laughs la FS<00:01:57.489> which<00:01:58.209> stands<00:01:58.479> for<00:01:58.599> at<00:01:58.779> least<00:01:58.869> Authority 00:01:59.339 --> 00:01:59.349 align:start position:0% FS which stands for at least Authority 00:01:59.349 --> 00:02:04.889 align:start position:0% FS which stands for at least Authority file<00:01:59.529> store<00:01:59.889> and<00:02:01.979> Tahoe<00:02:02.979> laughs<00:02:03.340> and<00:02:03.639> our<00:02:04.149> s4 00:02:04.889 --> 00:02:04.899 align:start position:0% file store and Tahoe laughs and our s4 00:02:04.899 --> 00:02:06.690 align:start position:0% file store and Tahoe laughs and our s4 service<00:02:05.289> doesn't<00:02:05.739> operate<00:02:05.979> on<00:02:06.309> access 00:02:06.690 --> 00:02:06.700 align:start position:0% service doesn't operate on access 00:02:06.700 --> 00:02:09.330 align:start position:0% service doesn't operate on access control<00:02:07.059> lists<00:02:07.450> or<00:02:07.689> ACL<00:02:08.500> or<00:02:08.649> user<00:02:08.829> accounts 00:02:09.330 --> 00:02:09.340 align:start position:0% control lists or ACL or user accounts 00:02:09.340 --> 00:02:11.069 align:start position:0% control lists or ACL or user accounts but<00:02:09.579> instead<00:02:09.879> works<00:02:10.179> using<00:02:10.629> object 00:02:11.069 --> 00:02:11.079 align:start position:0% but instead works using object 00:02:11.079 --> 00:02:13.170 align:start position:0% but instead works using object capability<00:02:11.709> model<00:02:11.860> oh<00:02:12.159> cap<00:02:12.489> or<00:02:12.790> key<00:02:13.000> based 00:02:13.170 --> 00:02:13.180 align:start position:0% capability model oh cap or key based 00:02:13.180 --> 00:02:14.150 align:start position:0% capability model oh cap or key based access 00:02:14.150 --> 00:02:14.160 align:start position:0% access 00:02:14.160 --> 00:02:16.740 align:start position:0% access this<00:02:15.160> is<00:02:15.310> similar<00:02:15.670> to<00:02:15.880> how<00:02:16.000> cryptocurrency 00:02:16.740 --> 00:02:16.750 align:start position:0% this is similar to how cryptocurrency 00:02:16.750 --> 00:02:19.559 align:start position:0% this is similar to how cryptocurrency works<00:02:17.260> in<00:02:17.800> a<00:02:18.340> high<00:02:18.459> level<00:02:18.670> it's<00:02:19.030> similar<00:02:19.239> in 00:02:19.559 --> 00:02:19.569 align:start position:0% works in a high level it's similar in 00:02:19.569 --> 00:02:22.110 align:start position:0% works in a high level it's similar in the<00:02:20.440> sense<00:02:20.650> that<00:02:20.770> if<00:02:21.130> you<00:02:21.430> have<00:02:21.670> the<00:02:21.819> private 00:02:22.110 --> 00:02:22.120 align:start position:0% the sense that if you have the private 00:02:22.120 --> 00:02:24.630 align:start position:0% the sense that if you have the private key<00:02:22.239> you<00:02:22.510> have<00:02:22.810> access<00:02:23.349> to<00:02:23.530> the<00:02:23.650> crypto<00:02:24.130> to<00:02:24.520> the 00:02:24.630 --> 00:02:24.640 align:start position:0% key you have access to the crypto to the 00:02:24.640 --> 00:02:25.380 align:start position:0% key you have access to the crypto to the cryptocurrency 00:02:25.380 --> 00:02:25.390 align:start position:0% cryptocurrency 00:02:25.390 --> 00:02:27.930 align:start position:0% cryptocurrency and<00:02:25.569> there's<00:02:26.020> no<00:02:26.200> user<00:02:26.470> lists<00:02:26.830> no<00:02:27.430> centralized 00:02:27.930 --> 00:02:27.940 align:start position:0% and there's no user lists no centralized 00:02:27.940 --> 00:02:30.270 align:start position:0% and there's no user lists no centralized party<00:02:28.330> that<00:02:28.870> is<00:02:29.080> kept<00:02:29.380> that's<00:02:29.739> saying<00:02:30.010> that 00:02:30.270 --> 00:02:30.280 align:start position:0% party that is kept that's saying that 00:02:30.280 --> 00:02:32.220 align:start position:0% party that is kept that's saying that this<00:02:30.489> particular<00:02:30.760> cryptocurrency<00:02:31.660> belongs 00:02:32.220 --> 00:02:32.230 align:start position:0% this particular cryptocurrency belongs 00:02:32.230 --> 00:02:36.030 align:start position:0% this particular cryptocurrency belongs to<00:02:32.500> you<00:02:32.620> personally<00:02:34.200> so<00:02:35.200> we<00:02:35.500> don't<00:02:35.680> have<00:02:35.830> any 00:02:36.030 --> 00:02:36.040 align:start position:0% to you personally so we don't have any 00:02:36.040 --> 00:02:37.440 align:start position:0% to you personally so we don't have any personal<00:02:36.430> account<00:02:36.760> information<00:02:37.300> with<00:02:37.420> our 00:02:37.440 --> 00:02:37.450 align:start position:0% personal account information with our 00:02:37.450 --> 00:02:39.630 align:start position:0% personal account information with our system<00:02:37.900> about<00:02:38.380> this<00:02:38.650> so<00:02:39.069> we<00:02:39.160> don't<00:02:39.310> have<00:02:39.459> any 00:02:39.630 --> 00:02:39.640 align:start position:0% system about this so we don't have any 00:02:39.640 --> 00:02:40.920 align:start position:0% system about this so we don't have any personal<00:02:39.970> account<00:02:40.269> information<00:02:40.690> about<00:02:40.840> the 00:02:40.920 --> 00:02:40.930 align:start position:0% personal account information about the 00:02:40.930 --> 00:02:44.370 align:start position:0% personal account information about the ciphertext<00:02:41.500> that<00:02:41.530> we're<00:02:41.739> storing<00:02:42.040> and<00:02:43.380> you 00:02:44.370 --> 00:02:44.380 align:start position:0% ciphertext that we're storing and you 00:02:44.380 --> 00:02:46.199 align:start position:0% ciphertext that we're storing and you either<00:02:44.530> have<00:02:44.769> the<00:02:44.800> capability<00:02:45.459> to<00:02:45.489> access<00:02:45.940> it 00:02:46.199 --> 00:02:46.209 align:start position:0% either have the capability to access it 00:02:46.209 --> 00:02:52.380 align:start position:0% either have the capability to access it the<00:02:46.540> key<00:02:46.720> or<00:02:47.019> you<00:02:47.200> don't<00:02:50.220> so<00:02:51.220> this<00:02:51.819> brings<00:02:52.180> us 00:02:52.380 --> 00:02:52.390 align:start position:0% the key or you don't so this brings us 00:02:52.390 --> 00:02:54.780 align:start position:0% the key or you don't so this brings us to<00:02:52.450> our<00:02:53.019> problem<00:02:53.650> and<00:02:53.860> why<00:02:54.100> we<00:02:54.340> started<00:02:54.670> this 00:02:54.780 --> 00:02:54.790 align:start position:0% to our problem and why we started this 00:02:54.790 --> 00:02:58.410 align:start position:0% to our problem and why we started this effort<00:02:54.940> to<00:02:55.239> begin<00:02:55.360> with<00:02:56.370> we<00:02:57.370> have<00:02:57.400> to<00:02:57.700> use<00:02:57.880> fiat 00:02:58.410 --> 00:02:58.420 align:start position:0% effort to begin with we have to use fiat 00:02:58.420 --> 00:03:02.130 align:start position:0% effort to begin with we have to use fiat currency<00:02:58.930> with<00:02:59.380> this<00:02:59.910> so<00:03:00.910> anyway<00:03:01.120> so<00:03:01.599> with<00:03:01.989> our 00:03:02.130 --> 00:03:02.140 align:start position:0% currency with this so anyway so with our 00:03:02.140 --> 00:03:03.930 align:start position:0% currency with this so anyway so with our secure<00:03:02.470> storage<00:03:02.769> product<00:03:03.130> we<00:03:03.640> need<00:03:03.760> to 00:03:03.930 --> 00:03:03.940 align:start position:0% secure storage product we need to 00:03:03.940 --> 00:03:06.509 align:start position:0% secure storage product we need to collect<00:03:04.660> these<00:03:04.840> subscription<00:03:05.440> payments<00:03:05.950> this 00:03:06.509 --> 00:03:06.519 align:start position:0% collect these subscription payments this 00:03:06.519 --> 00:03:09.210 align:start position:0% collect these subscription payments this is<00:03:06.580> our<00:03:06.849> business<00:03:07.180> model<00:03:07.450> with<00:03:07.569> it<00:03:07.720> and<00:03:07.900> in<00:03:08.709> so 00:03:09.210 --> 00:03:09.220 align:start position:0% is our business model with it and in so 00:03:09.220 --> 00:03:10.620 align:start position:0% is our business model with it and in so however<00:03:09.549> in<00:03:09.910> the<00:03:10.000> world<00:03:10.150> of<00:03:10.360> fiat<00:03:10.599> currency 00:03:10.620 --> 00:03:10.630 align:start position:0% however in the world of fiat currency 00:03:10.630 --> 00:03:12.990 align:start position:0% however in the world of fiat currency and<00:03:11.140> online<00:03:11.680> tools<00:03:11.950> this<00:03:12.370> results<00:03:12.790> in<00:03:12.880> us 00:03:12.990 --> 00:03:13.000 align:start position:0% and online tools this results in us 00:03:13.000 --> 00:03:17.370 align:start position:0% and online tools this results in us collecting<00:03:13.450> personal<00:03:13.690> data<00:03:13.930> by<00:03:14.890> using<00:03:16.380> by 00:03:17.370 --> 00:03:17.380 align:start position:0% collecting personal data by using by 00:03:17.380 --> 00:03:19.229 align:start position:0% collecting personal data by using by using<00:03:17.410> things<00:03:17.799> like<00:03:17.950> stripe<00:03:18.340> and<00:03:18.579> charge<00:03:19.000> B 00:03:19.229 --> 00:03:19.239 align:start position:0% using things like stripe and charge B 00:03:19.239 --> 00:03:21.240 align:start position:0% using things like stripe and charge B and<00:03:19.480> we<00:03:19.989> are<00:03:20.079> collecting<00:03:20.500> this<00:03:20.650> personal<00:03:21.040> data 00:03:21.240 --> 00:03:21.250 align:start position:0% and we are collecting this personal data 00:03:21.250 --> 00:03:22.979 align:start position:0% and we are collecting this personal data only<00:03:21.579> for<00:03:21.910> the<00:03:21.970> purpose<00:03:22.299> of<00:03:22.390> processing 00:03:22.979 --> 00:03:22.989 align:start position:0% only for the purpose of processing 00:03:22.989 --> 00:03:25.289 align:start position:0% only for the purpose of processing payments<00:03:23.530> not<00:03:24.160> for<00:03:24.370> operating<00:03:24.850> the<00:03:24.940> service 00:03:25.289 --> 00:03:25.299 align:start position:0% payments not for operating the service 00:03:25.299 --> 00:03:31.860 align:start position:0% payments not for operating the service itself<00:03:28.829> so<00:03:29.829> right<00:03:30.430> now<00:03:30.579> we<00:03:31.150> use<00:03:31.180> stripe<00:03:31.660> and 00:03:31.860 --> 00:03:31.870 align:start position:0% itself so right now we use stripe and 00:03:31.870 --> 00:03:33.870 align:start position:0% itself so right now we use stripe and charge<00:03:32.049> B<00:03:32.260> and<00:03:32.500> only<00:03:32.920> collect<00:03:33.160> this<00:03:33.310> personal 00:03:33.870 --> 00:03:33.880 align:start position:0% charge B and only collect this personal 00:03:33.880 --> 00:03:37.039 align:start position:0% charge B and only collect this personal data<00:03:34.260> and<00:03:35.260> not<00:03:35.530> for<00:03:35.739> any<00:03:35.890> account<00:03:36.220> management 00:03:37.039 --> 00:03:37.049 align:start position:0% data and not for any account management 00:03:37.049 --> 00:03:40.500 align:start position:0% data and not for any account management because<00:03:38.049> of<00:03:38.230> the<00:03:38.319> o<00:03:38.350> cap<00:03:38.620> model<00:03:39.120> so<00:03:40.120> we<00:03:40.269> didn't 00:03:40.500 --> 00:03:40.510 align:start position:0% because of the o cap model so we didn't 00:03:40.510 --> 00:03:42.509 align:start position:0% because of the o cap model so we didn't like<00:03:40.660> this<00:03:40.959> so<00:03:41.350> we<00:03:41.470> started<00:03:41.739> talking<00:03:41.920> amongst 00:03:42.509 --> 00:03:42.519 align:start position:0% like this so we started talking amongst 00:03:42.519 --> 00:03:44.129 align:start position:0% like this so we started talking amongst ourselves<00:03:42.579> about<00:03:43.150> how<00:03:43.569> we<00:03:43.630> could<00:03:43.989> potentially 00:03:44.129 --> 00:03:44.139 align:start position:0% ourselves about how we could potentially 00:03:44.139 --> 00:03:46.559 align:start position:0% ourselves about how we could potentially use<00:03:44.560> cryptocurrency<00:03:45.430> to<00:03:45.880> help<00:03:46.090> us<00:03:46.239> avoid 00:03:46.559 --> 00:03:46.569 align:start position:0% use cryptocurrency to help us avoid 00:03:46.569 --> 00:03:48.390 align:start position:0% use cryptocurrency to help us avoid using<00:03:47.019> these<00:03:47.139> centralized<00:03:47.739> systems<00:03:48.130> that<00:03:48.310> are 00:03:48.390 --> 00:03:48.400 align:start position:0% using these centralized systems that are 00:03:48.400 --> 00:03:50.550 align:start position:0% using these centralized systems that are collecting<00:03:48.819> personal<00:03:49.030> data<00:03:49.269> this<00:03:50.200> came<00:03:50.380> about 00:03:50.550 --> 00:03:50.560 align:start position:0% collecting personal data this came about 00:03:50.560 --> 00:03:52.559 align:start position:0% collecting personal data this came about from<00:03:50.889> discussions<00:03:51.250> about<00:03:51.670> GDP<00:03:52.359> our 00:03:52.559 --> 00:03:52.569 align:start position:0% from discussions about GDP our 00:03:52.569 --> 00:03:54.210 align:start position:0% from discussions about GDP our compliance<00:03:52.900> which<00:03:53.380> is<00:03:53.530> the<00:03:53.680> general<00:03:53.980> data 00:03:54.210 --> 00:03:54.220 align:start position:0% compliance which is the general data 00:03:54.220 --> 00:03:56.430 align:start position:0% compliance which is the general data protection<00:03:54.609> regulation<00:03:55.329> it's<00:03:55.900> in<00:03:56.079> the<00:03:56.139> EU 00:03:56.430 --> 00:03:56.440 align:start position:0% protection regulation it's in the EU 00:03:56.440 --> 00:03:58.470 align:start position:0% protection regulation it's in the EU about<00:03:56.859> how<00:03:57.130> personal<00:03:57.940> data<00:03:58.120> should<00:03:58.329> be 00:03:58.470 --> 00:03:58.480 align:start position:0% about how personal data should be 00:03:58.480 --> 00:04:01.650 align:start position:0% about how personal data should be managed<00:03:58.889> and<00:03:59.889> so<00:04:00.310> amongst<00:04:01.150> ourselves<00:04:01.269> we 00:04:01.650 --> 00:04:01.660 align:start position:0% managed and so amongst ourselves we 00:04:01.660 --> 00:04:03.180 align:start position:0% managed and so amongst ourselves we figured<00:04:01.930> out<00:04:02.079> that<00:04:02.109> this<00:04:02.350> was<00:04:02.410> a<00:04:02.560> problem<00:04:02.799> and 00:04:03.180 --> 00:04:03.190 align:start position:0% figured out that this was a problem and 00:04:03.190 --> 00:04:05.729 align:start position:0% figured out that this was a problem and so<00:04:03.940> we<00:04:04.359> thought<00:04:04.600> okay<00:04:05.049> what<00:04:05.290> could<00:04:05.440> we<00:04:05.590> do<00:04:05.709> with 00:04:05.729 --> 00:04:05.739 align:start position:0% so we thought okay what could we do with 00:04:05.739 --> 00:04:09.150 align:start position:0% so we thought okay what could we do with cryptocurrency<00:04:07.590> so<00:04:08.590> we<00:04:08.680> started<00:04:09.069> looking 00:04:09.150 --> 00:04:09.160 align:start position:0% cryptocurrency so we started looking 00:04:09.160 --> 00:04:11.430 align:start position:0% cryptocurrency so we started looking around<00:04:09.400> and<00:04:09.910> how<00:04:10.389> we<00:04:10.450> could<00:04:10.720> accept<00:04:11.109> private 00:04:11.430 --> 00:04:11.440 align:start position:0% around and how we could accept private 00:04:11.440 --> 00:04:13.590 align:start position:0% around and how we could accept private payments<00:04:12.069> for<00:04:12.430> the<00:04:12.519> subscription<00:04:13.000> service 00:04:13.590 --> 00:04:13.600 align:start position:0% payments for the subscription service 00:04:13.600 --> 00:04:16.170 align:start position:0% payments for the subscription service and<00:04:13.840> that<00:04:14.560> would<00:04:14.709> also<00:04:14.889> allow<00:04:15.430> us<00:04:15.459> to<00:04:15.760> do<00:04:15.880> and 00:04:16.170 --> 00:04:16.180 align:start position:0% and that would also allow us to do and 00:04:16.180 --> 00:04:18.479 align:start position:0% and that would also allow us to do and and<00:04:16.510> privacy<00:04:17.169> for<00:04:17.200> people<00:04:17.560> just<00:04:17.979> like<00:04:18.100> we<00:04:18.250> are 00:04:18.479 --> 00:04:18.489 align:start position:0% and privacy for people just like we are 00:04:18.489 --> 00:04:19.949 align:start position:0% and privacy for people just like we are able<00:04:18.700> to<00:04:18.850> offer<00:04:19.090> them<00:04:19.359> end<00:04:19.539> to<00:04:19.570> end<00:04:19.690> encryption 00:04:19.949 --> 00:04:19.959 align:start position:0% able to offer them end to end encryption 00:04:19.959 --> 00:04:22.230 align:start position:0% able to offer them end to end encryption and<00:04:20.530> privacy<00:04:21.400> with<00:04:21.549> the<00:04:21.700> data<00:04:21.880> storage 00:04:22.230 --> 00:04:22.240 align:start position:0% and privacy with the data storage 00:04:22.240 --> 00:04:25.980 align:start position:0% and privacy with the data storage service<00:04:22.630> itself<00:04:22.960> and<00:04:24.120> so<00:04:25.120> of<00:04:25.419> course<00:04:25.450> this<00:04:25.870> is 00:04:25.980 --> 00:04:25.990 align:start position:0% service itself and so of course this is 00:04:25.990 --> 00:04:27.100 align:start position:0% service itself and so of course this is a<00:04:26.020> problem 00:04:27.100 --> 00:04:27.110 align:start position:0% a problem 00:04:27.110 --> 00:04:28.390 align:start position:0% a problem now<00:04:27.319> it's<00:04:27.530> expensive<00:04:27.800> to<00:04:28.039> make<00:04:28.159> things 00:04:28.390 --> 00:04:28.400 align:start position:0% now it's expensive to make things 00:04:28.400 --> 00:04:30.360 align:start position:0% now it's expensive to make things private<00:04:28.849> and<00:04:29.030> cheap<00:04:29.270> to<00:04:29.449> make<00:04:29.569> them<00:04:29.750> public 00:04:30.360 --> 00:04:30.370 align:start position:0% private and cheap to make them public 00:04:30.370 --> 00:04:32.379 align:start position:0% private and cheap to make them public unfortunately<00:04:31.370> this<00:04:31.580> seems<00:04:31.789> to<00:04:31.970> be<00:04:32.000> the<00:04:32.210> case 00:04:32.379 --> 00:04:32.389 align:start position:0% unfortunately this seems to be the case 00:04:32.389 --> 00:04:34.629 align:start position:0% unfortunately this seems to be the case right<00:04:32.659> now<00:04:32.689> and<00:04:33.080> we're<00:04:33.860> trying<00:04:33.889> to<00:04:34.340> work<00:04:34.460> on 00:04:34.629 --> 00:04:34.639 align:start position:0% right now and we're trying to work on 00:04:34.639 --> 00:04:37.360 align:start position:0% right now and we're trying to work on making<00:04:35.000> this<00:04:35.120> not<00:04:35.360> the<00:04:35.539> case<00:04:35.719> an<00:04:36.159> expensive<00:04:37.159> is 00:04:37.360 --> 00:04:37.370 align:start position:0% making this not the case an expensive is 00:04:37.370 --> 00:04:39.309 align:start position:0% making this not the case an expensive is relative<00:04:38.060> and<00:04:38.300> I<00:04:38.659> think<00:04:38.870> that<00:04:38.990> this<00:04:39.080> issue 00:04:39.309 --> 00:04:39.319 align:start position:0% relative and I think that this issue 00:04:39.319 --> 00:04:41.260 align:start position:0% relative and I think that this issue could<00:04:39.680> be<00:04:39.740> easily<00:04:40.009> challenged<00:04:40.849> with<00:04:41.060> new 00:04:41.260 --> 00:04:41.270 align:start position:0% could be easily challenged with new 00:04:41.270 --> 00:04:45.999 align:start position:0% could be easily challenged with new technology<00:04:43.750> so<00:04:44.750> here<00:04:45.199> are<00:04:45.349> the<00:04:45.500> layers<00:04:45.710> of 00:04:45.999 --> 00:04:46.009 align:start position:0% technology so here are the layers of 00:04:46.009 --> 00:04:47.920 align:start position:0% technology so here are the layers of privacy<00:04:46.460> that<00:04:46.490> we're<00:04:46.759> considering<00:04:47.150> when<00:04:47.780> we 00:04:47.920 --> 00:04:47.930 align:start position:0% privacy that we're considering when we 00:04:47.930 --> 00:04:49.270 align:start position:0% privacy that we're considering when we won't<00:04:48.110> say<00:04:48.289> that<00:04:48.500> we<00:04:48.590> want<00:04:48.740> to<00:04:48.800> do<00:04:48.919> something 00:04:49.270 --> 00:04:49.280 align:start position:0% won't say that we want to do something 00:04:49.280 --> 00:04:54.040 align:start position:0% won't say that we want to do something that's<00:04:49.460> end<00:04:49.699> and<00:04:50.000> private<00:04:50.419> for<00:04:50.599> the<00:04:50.659> user<00:04:53.050> we 00:04:54.040 --> 00:04:54.050 align:start position:0% that's end and private for the user we 00:04:54.050 --> 00:04:55.749 align:start position:0% that's end and private for the user we need<00:04:54.289> to<00:04:54.409> preserve<00:04:54.590> this<00:04:54.949> customers<00:04:55.400> privacy 00:04:55.749 --> 00:04:55.759 align:start position:0% need to preserve this customers privacy 00:04:55.759 --> 00:04:58.510 align:start position:0% need to preserve this customers privacy at<00:04:55.939> all<00:04:56.090> these<00:04:56.270> levels<00:04:56.659> and<00:04:57.219> these<00:04:58.219> are<00:04:58.430> the 00:04:58.510 --> 00:04:58.520 align:start position:0% at all these levels and these are the 00:04:58.520 --> 00:05:00.100 align:start position:0% at all these levels and these are the different<00:04:58.819> layers<00:04:58.939> and<00:04:59.150> systems<00:04:59.750> that<00:05:00.020> we 00:05:00.100 --> 00:05:00.110 align:start position:0% different layers and systems that we 00:05:00.110 --> 00:05:01.659 align:start position:0% different layers and systems that we need<00:05:00.259> to<00:05:00.379> have<00:05:00.530> interacting<00:05:01.129> with<00:05:01.280> about 00:05:01.659 --> 00:05:01.669 align:start position:0% need to have interacting with about 00:05:01.669 --> 00:05:03.040 align:start position:0% need to have interacting with about whether<00:05:01.849> or<00:05:01.969> not<00:05:02.060> there's<00:05:02.300> any<00:05:02.449> personal<00:05:02.930> data 00:05:03.040 --> 00:05:03.050 align:start position:0% whether or not there's any personal data 00:05:03.050 --> 00:05:05.290 align:start position:0% whether or not there's any personal data that<00:05:03.409> would<00:05:03.500> be<00:05:03.650> leaked<00:05:03.919> or<00:05:04.190> any<00:05:04.789> metadata 00:05:05.290 --> 00:05:05.300 align:start position:0% that would be leaked or any metadata 00:05:05.300 --> 00:05:07.600 align:start position:0% that would be leaked or any metadata that<00:05:06.110> could<00:05:06.289> be<00:05:06.409> correlated<00:05:06.979> with<00:05:07.099> other<00:05:07.129> data 00:05:07.600 --> 00:05:07.610 align:start position:0% that could be correlated with other data 00:05:07.610 --> 00:05:10.540 align:start position:0% that could be correlated with other data to<00:05:08.000> become<00:05:08.180> personal<00:05:08.690> data<00:05:09.080> the<00:05:09.379> same<00:05:10.310> way 00:05:10.540 --> 00:05:10.550 align:start position:0% to become personal data the same way 00:05:10.550 --> 00:05:13.540 align:start position:0% to become personal data the same way that<00:05:11.229> the<00:05:12.229> same<00:05:12.440> way<00:05:12.620> that<00:05:12.830> like<00:05:13.159> things<00:05:13.400> like 00:05:13.540 --> 00:05:13.550 align:start position:0% that the same way that like things like 00:05:13.550 --> 00:05:15.219 align:start position:0% that the same way that like things like Bitcoin<00:05:13.759> and<00:05:14.120> aetherium<00:05:14.569> the<00:05:14.659> addresses 00:05:15.219 --> 00:05:15.229 align:start position:0% Bitcoin and aetherium the addresses 00:05:15.229 --> 00:05:17.830 align:start position:0% Bitcoin and aetherium the addresses could<00:05:15.949> be<00:05:16.159> you<00:05:16.580> you<00:05:17.180> know<00:05:17.300> looked<00:05:17.659> at 00:05:17.830 --> 00:05:17.840 align:start position:0% could be you you know looked at 00:05:17.840 --> 00:05:19.600 align:start position:0% could be you you know looked at correlated<00:05:18.469> with<00:05:18.620> other<00:05:18.770> data<00:05:19.069> in<00:05:19.250> order<00:05:19.490> to 00:05:19.600 --> 00:05:19.610 align:start position:0% correlated with other data in order to 00:05:19.610 --> 00:05:21.670 align:start position:0% correlated with other data in order to figure<00:05:19.789> out<00:05:19.940> people<00:05:20.509> so<00:05:20.779> that<00:05:21.110> figure<00:05:21.620> out 00:05:21.670 --> 00:05:21.680 align:start position:0% figure out people so that figure out 00:05:21.680 --> 00:05:24.070 align:start position:0% figure out people so that figure out personal<00:05:22.099> identities<00:05:22.520> so<00:05:23.240> that<00:05:23.509> are<00:05:23.629> not<00:05:23.750> true 00:05:24.070 --> 00:05:24.080 align:start position:0% personal identities so that are not true 00:05:24.080 --> 00:05:29.320 align:start position:0% personal identities so that are not true anonymity<00:05:24.469> but<00:05:24.800> pseudonym<00:05:25.400> anonymity<00:05:28.330> so 00:05:29.320 --> 00:05:29.330 align:start position:0% anonymity but pseudonym anonymity so 00:05:29.330 --> 00:05:30.969 align:start position:0% anonymity but pseudonym anonymity so starting<00:05:29.779> from<00:05:29.930> the<00:05:30.050> bottom<00:05:30.169> and<00:05:30.379> moving<00:05:30.860> to 00:05:30.969 --> 00:05:30.979 align:start position:0% starting from the bottom and moving to 00:05:30.979 --> 00:05:32.680 align:start position:0% starting from the bottom and moving to the<00:05:31.069> top<00:05:31.250> we<00:05:31.729> decided<00:05:32.120> to<00:05:32.210> use<00:05:32.330> tor<00:05:32.659> for 00:05:32.680 --> 00:05:32.690 align:start position:0% the top we decided to use tor for 00:05:32.690 --> 00:05:35.800 align:start position:0% the top we decided to use tor for network<00:05:33.139> layer<00:05:33.379> privacy<00:05:34.250> because<00:05:35.060> it<00:05:35.389> exists 00:05:35.800 --> 00:05:35.810 align:start position:0% network layer privacy because it exists 00:05:35.810 --> 00:05:38.200 align:start position:0% network layer privacy because it exists right<00:05:35.930> now<00:05:36.110> and<00:05:36.680> it's<00:05:36.919> usable<00:05:37.310> some<00:05:37.879> of<00:05:38.029> our 00:05:38.200 --> 00:05:38.210 align:start position:0% right now and it's usable some of our 00:05:38.210 --> 00:05:39.700 align:start position:0% right now and it's usable some of our team<00:05:38.419> members<00:05:38.449> contribute<00:05:39.349> to<00:05:39.440> the<00:05:39.560> Tor 00:05:39.700 --> 00:05:39.710 align:start position:0% team members contribute to the Tor 00:05:39.710 --> 00:05:41.619 align:start position:0% team members contribute to the Tor project<00:05:39.740> which<00:05:40.430> is<00:05:40.580> an<00:05:40.699> anonymity<00:05:41.150> network 00:05:41.619 --> 00:05:41.629 align:start position:0% project which is an anonymity network 00:05:41.629 --> 00:05:43.390 align:start position:0% project which is an anonymity network that<00:05:41.870> allows<00:05:42.050> users<00:05:42.529> to<00:05:42.560> not<00:05:42.889> reveal<00:05:43.190> personal 00:05:43.390 --> 00:05:43.400 align:start position:0% that allows users to not reveal personal 00:05:43.400 --> 00:05:46.149 align:start position:0% that allows users to not reveal personal data<00:05:43.819> on<00:05:44.089> the<00:05:44.599> network<00:05:44.870> and<00:05:45.080> this<00:05:45.740> protects 00:05:46.149 --> 00:05:46.159 align:start position:0% data on the network and this protects 00:05:46.159 --> 00:05:47.890 align:start position:0% data on the network and this protects against<00:05:46.639> leaking<00:05:46.969> any<00:05:47.120> IP<00:05:47.389> address 00:05:47.890 --> 00:05:47.900 align:start position:0% against leaking any IP address 00:05:47.900 --> 00:05:49.540 align:start position:0% against leaking any IP address information<00:05:48.199> which<00:05:48.680> can<00:05:48.919> be<00:05:48.979> considered 00:05:49.540 --> 00:05:49.550 align:start position:0% information which can be considered 00:05:49.550 --> 00:05:53.709 align:start position:0% information which can be considered personal<00:05:49.969> data<00:05:50.229> and<00:05:51.789> then<00:05:52.789> Tahoe<00:05:53.240> laughs<00:05:53.479> is 00:05:53.709 --> 00:05:53.719 align:start position:0% personal data and then Tahoe laughs is 00:05:53.719 --> 00:05:55.420 align:start position:0% personal data and then Tahoe laughs is the<00:05:53.810> technology<00:05:54.110> as<00:05:54.650> I<00:05:54.710> mentioned<00:05:55.129> before 00:05:55.420 --> 00:05:55.430 align:start position:0% the technology as I mentioned before 00:05:55.430 --> 00:05:58.659 align:start position:0% the technology as I mentioned before that<00:05:55.909> we<00:05:56.000> use<00:05:56.210> with<00:05:56.419> s4<00:05:56.930> and<00:05:57.279> this<00:05:58.279> offers 00:05:58.659 --> 00:05:58.669 align:start position:0% that we use with s4 and this offers 00:05:58.669 --> 00:06:00.610 align:start position:0% that we use with s4 and this offers storage<00:05:58.969> laver<00:05:59.360> layer<00:05:59.690> privacy<00:06:00.319> with 00:06:00.610 --> 00:06:00.620 align:start position:0% storage laver layer privacy with 00:06:00.620 --> 00:06:05.320 align:start position:0% storage laver layer privacy with client-side<00:06:01.129> encryption<00:06:01.190> and<00:06:02.020> lastly<00:06:04.330> we 00:06:05.320 --> 00:06:05.330 align:start position:0% client-side encryption and lastly we 00:06:05.330 --> 00:06:08.829 align:start position:0% client-side encryption and lastly we also<00:06:05.539> use<00:06:06.259> or<00:06:07.069> not<00:06:07.190> not<00:06:07.310> Leslie<00:06:07.460> sorry<00:06:08.029> and 00:06:08.829 --> 00:06:08.839 align:start position:0% also use or not not Leslie sorry and 00:06:08.839 --> 00:06:13.269 align:start position:0% also use or not not Leslie sorry and then<00:06:09.650> we<00:06:09.800> have<00:06:10.550> Z<00:06:11.150> cache<00:06:11.360> I<00:06:11.659> think<00:06:11.870> I<00:06:11.990> I<00:06:12.740> missed 00:06:13.269 --> 00:06:13.279 align:start position:0% then we have Z cache I think I I missed 00:06:13.279 --> 00:06:14.890 align:start position:0% then we have Z cache I think I I missed that<00:06:13.430> sorry<00:06:13.669> going<00:06:13.940> up<00:06:14.060> I<00:06:14.210> skipped<00:06:14.509> over<00:06:14.599> Z 00:06:14.890 --> 00:06:14.900 align:start position:0% that sorry going up I skipped over Z 00:06:14.900 --> 00:06:16.779 align:start position:0% that sorry going up I skipped over Z cache<00:06:15.080> see<00:06:15.800> cache<00:06:15.979> I'll<00:06:16.190> talk<00:06:16.339> more<00:06:16.370> about<00:06:16.580> it 00:06:16.779 --> 00:06:16.789 align:start position:0% cache see cache I'll talk more about it 00:06:16.789 --> 00:06:18.610 align:start position:0% cache see cache I'll talk more about it in<00:06:16.849> the<00:06:16.879> next<00:06:17.000> slide<00:06:17.270> but<00:06:17.810> Z<00:06:17.990> cache<00:06:18.199> sue 00:06:18.610 --> 00:06:18.620 align:start position:0% in the next slide but Z cache sue 00:06:18.620 --> 00:06:20.529 align:start position:0% in the next slide but Z cache sue shielded<00:06:19.009> transactions<00:06:19.639> help<00:06:20.210> us<00:06:20.330> with 00:06:20.529 --> 00:06:20.539 align:start position:0% shielded transactions help us with 00:06:20.539 --> 00:06:22.540 align:start position:0% shielded transactions help us with financial<00:06:20.750> privacy<00:06:21.199> and<00:06:21.800> then<00:06:21.979> Tahoe<00:06:22.310> laughs 00:06:22.540 --> 00:06:22.550 align:start position:0% financial privacy and then Tahoe laughs 00:06:22.550 --> 00:06:24.189 align:start position:0% financial privacy and then Tahoe laughs again<00:06:22.849> helps<00:06:23.150> us<00:06:23.300> with<00:06:23.479> the<00:06:23.509> storage<00:06:23.990> layer 00:06:24.189 --> 00:06:24.199 align:start position:0% again helps us with the storage layer 00:06:24.199 --> 00:06:26.920 align:start position:0% again helps us with the storage layer privacy<00:06:24.830> and<00:06:25.039> then<00:06:25.819> going<00:06:26.270> at<00:06:26.419> the<00:06:26.539> top<00:06:26.719> we 00:06:26.920 --> 00:06:26.930 align:start position:0% privacy and then going at the top we 00:06:26.930 --> 00:06:28.839 align:start position:0% privacy and then going at the top we have<00:06:27.080> the<00:06:27.229> client<00:06:27.589> application<00:06:27.740> which<00:06:28.639> is 00:06:28.839 --> 00:06:28.849 align:start position:0% have the client application which is 00:06:28.849 --> 00:06:30.939 align:start position:0% have the client application which is grid<00:06:29.120> sync<00:06:29.449> that<00:06:29.629> we're<00:06:29.810> using<00:06:29.990> for<00:06:30.169> ours<00:06:30.589> but 00:06:30.939 --> 00:06:30.949 align:start position:0% grid sync that we're using for ours but 00:06:30.949 --> 00:06:32.980 align:start position:0% grid sync that we're using for ours but this<00:06:31.159> also<00:06:31.400> applies<00:06:31.909> to<00:06:31.940> the<00:06:32.330> Z<00:06:32.509> cash<00:06:32.690> wallets 00:06:32.980 --> 00:06:32.990 align:start position:0% this also applies to the Z cash wallets 00:06:32.990 --> 00:06:35.260 align:start position:0% this also applies to the Z cash wallets and<00:06:33.349> this<00:06:33.770> gives<00:06:34.039> users<00:06:34.310> control<00:06:34.789> over<00:06:35.120> their 00:06:35.260 --> 00:06:35.270 align:start position:0% and this gives users control over their 00:06:35.270 --> 00:06:39.980 align:start position:0% and this gives users control over their payments<00:06:35.750> and<00:06:37.509> all<00:06:38.509> of<00:06:38.719> this<00:06:38.839> is<00:06:39.020> combined 00:06:39.980 --> 00:06:39.990 align:start position:0% payments and all of this is combined 00:06:39.990 --> 00:06:42.140 align:start position:0% payments and all of this is combined what<00:06:40.200> we<00:06:40.290> need<00:06:40.470> to<00:06:40.500> give<00:06:40.890> us<00:06:41.010> and<00:06:41.280> and<00:06:41.550> privacy 00:06:42.140 --> 00:06:42.150 align:start position:0% what we need to give us and and privacy 00:06:42.150 --> 00:06:44.810 align:start position:0% what we need to give us and and privacy for<00:06:42.420> our<00:06:42.510> subscription<00:06:43.110> customers<00:06:43.350> and<00:06:43.920> why 00:06:44.810 --> 00:06:44.820 align:start position:0% for our subscription customers and why 00:06:44.820 --> 00:06:46.310 align:start position:0% for our subscription customers and why we<00:06:45.030> particularly<00:06:45.510> like<00:06:45.690> doing<00:06:46.020> it<00:06:46.140> this<00:06:46.260> way 00:06:46.310 --> 00:06:46.320 align:start position:0% we particularly like doing it this way 00:06:46.320 --> 00:06:48.260 align:start position:0% we particularly like doing it this way is<00:06:46.680> because<00:06:46.800> these<00:06:47.130> all<00:06:47.370> these<00:06:47.610> things<00:06:47.880> exist 00:06:48.260 --> 00:06:48.270 align:start position:0% is because these all these things exist 00:06:48.270 --> 00:06:49.550 align:start position:0% is because these all these things exist right<00:06:48.450> now<00:06:48.510> and<00:06:48.900> we<00:06:48.960> can<00:06:49.110> put<00:06:49.260> them<00:06:49.350> together 00:06:49.550 --> 00:06:49.560 align:start position:0% right now and we can put them together 00:06:49.560 --> 00:06:52.250 align:start position:0% right now and we can put them together to<00:06:49.980> have<00:06:50.610> this<00:06:50.730> implemented<00:06:51.330> in<00:06:51.870> a<00:06:52.050> short 00:06:52.250 --> 00:06:52.260 align:start position:0% to have this implemented in a short 00:06:52.260 --> 00:06:56.150 align:start position:0% to have this implemented in a short amount<00:06:52.290> of<00:06:52.500> time<00:06:52.560> so<00:06:54.740> about<00:06:55.740> cryptocurrency 00:06:56.150 --> 00:06:56.160 align:start position:0% amount of time so about cryptocurrency 00:06:56.160 --> 00:06:59.480 align:start position:0% amount of time so about cryptocurrency payments<00:06:57.830> cryptocurrencies<00:06:58.830> have<00:06:59.280> some 00:06:59.480 --> 00:06:59.490 align:start position:0% payments cryptocurrencies have some 00:06:59.490 --> 00:07:00.710 align:start position:0% payments cryptocurrencies have some technical<00:06:59.880> features<00:07:00.240> that<00:07:00.510> could<00:07:00.660> be 00:07:00.710 --> 00:07:00.720 align:start position:0% technical features that could be 00:07:00.720 --> 00:07:02.750 align:start position:0% technical features that could be utilized<00:07:01.200> including<00:07:01.890> some<00:07:02.070> privacy<00:07:02.370> features 00:07:02.750 --> 00:07:02.760 align:start position:0% utilized including some privacy features 00:07:02.760 --> 00:07:04.550 align:start position:0% utilized including some privacy features one<00:07:03.270> blockchain<00:07:03.750> that<00:07:03.900> we<00:07:03.990> are<00:07:04.110> familiar<00:07:04.320> with 00:07:04.550 --> 00:07:04.560 align:start position:0% one blockchain that we are familiar with 00:07:04.560 --> 00:07:06.500 align:start position:0% one blockchain that we are familiar with is<00:07:04.920> the<00:07:05.070> cache<00:07:05.220> our<00:07:05.850> company's<00:07:06.300> share 00:07:06.500 --> 00:07:06.510 align:start position:0% is the cache our company's share 00:07:06.510 --> 00:07:07.910 align:start position:0% is the cache our company's share founders<00:07:06.990> and<00:07:07.290> although<00:07:07.440> there<00:07:07.770> are<00:07:07.830> two 00:07:07.910 --> 00:07:07.920 align:start position:0% founders and although there are two 00:07:07.920 --> 00:07:11.300 align:start position:0% founders and although there are two separate<00:07:08.310> companies<00:07:08.640> now<00:07:09.140> so<00:07:10.140> we<00:07:10.980> should<00:07:11.010> also 00:07:11.300 --> 00:07:11.310 align:start position:0% separate companies now so we should also 00:07:11.310 --> 00:07:13.430 align:start position:0% separate companies now so we should also share<00:07:11.610> mission<00:07:11.970> for<00:07:12.390> privacy<00:07:12.810> for<00:07:12.930> everyone 00:07:13.430 --> 00:07:13.440 align:start position:0% share mission for privacy for everyone 00:07:13.440 --> 00:07:15.380 align:start position:0% share mission for privacy for everyone so<00:07:13.740> we<00:07:13.770> looked<00:07:14.040> at<00:07:14.160> how<00:07:14.280> we<00:07:14.310> could<00:07:14.460> use<00:07:14.610> utilize 00:07:15.380 --> 00:07:15.390 align:start position:0% so we looked at how we could use utilize 00:07:15.390 --> 00:07:17.990 align:start position:0% so we looked at how we could use utilize D<00:07:15.600> caches<00:07:16.020> privacy<00:07:16.800> features<00:07:17.130> to<00:07:17.730> help<00:07:17.820> us 00:07:17.990 --> 00:07:18.000 align:start position:0% D caches privacy features to help us 00:07:18.000 --> 00:07:20.060 align:start position:0% D caches privacy features to help us preserve<00:07:18.330> privacy<00:07:18.630> in<00:07:19.140> our<00:07:19.320> processing<00:07:19.860> of 00:07:20.060 --> 00:07:20.070 align:start position:0% preserve privacy in our processing of 00:07:20.070 --> 00:07:23.300 align:start position:0% preserve privacy in our processing of customer<00:07:20.670> payments<00:07:21.090> and<00:07:21.500> of<00:07:22.500> course<00:07:22.740> Z<00:07:23.160> cache 00:07:23.300 --> 00:07:23.310 align:start position:0% customer payments and of course Z cache 00:07:23.310 --> 00:07:24.920 align:start position:0% customer payments and of course Z cache offers<00:07:23.700> two<00:07:23.880> types<00:07:23.910> of<00:07:24.180> payments<00:07:24.600> one<00:07:24.780> that 00:07:24.920 --> 00:07:24.930 align:start position:0% offers two types of payments one that 00:07:24.930 --> 00:07:27.410 align:start position:0% offers two types of payments one that our<00:07:25.020> trend<00:07:25.460> transparents<00:07:26.490> transparent 00:07:27.410 --> 00:07:27.420 align:start position:0% our trend transparents transparent 00:07:27.420 --> 00:07:29.810 align:start position:0% our trend transparents transparent transactions<00:07:28.050> and<00:07:28.320> that<00:07:28.950> which<00:07:29.190> are<00:07:29.370> is<00:07:29.580> more 00:07:29.810 --> 00:07:29.820 align:start position:0% transactions and that which are is more 00:07:29.820 --> 00:07:31.910 align:start position:0% transactions and that which are is more like<00:07:30.000> Bitcoin<00:07:30.420> and<00:07:30.660> then<00:07:30.780> also<00:07:30.990> the<00:07:31.350> shielded 00:07:31.910 --> 00:07:31.920 align:start position:0% like Bitcoin and then also the shielded 00:07:31.920 --> 00:07:34.220 align:start position:0% like Bitcoin and then also the shielded transactions<00:07:32.580> which<00:07:32.940> utilize<00:07:33.630> a<00:07:33.660> particular 00:07:34.220 --> 00:07:34.230 align:start position:0% transactions which utilize a particular 00:07:34.230 --> 00:07:36.110 align:start position:0% transactions which utilize a particular type<00:07:34.440> of<00:07:34.470> zero<00:07:34.890> knowledge<00:07:35.100> proof<00:07:35.250> called<00:07:35.820> ZK 00:07:36.110 --> 00:07:36.120 align:start position:0% type of zero knowledge proof called ZK 00:07:36.120 --> 00:07:41.960 align:start position:0% type of zero knowledge proof called ZK snarks<00:07:37.040> and<00:07:38.570> so<00:07:39.570> this<00:07:39.780> assures<00:07:40.760> so<00:07:41.760> for 00:07:41.960 --> 00:07:41.970 align:start position:0% snarks and so this assures so for 00:07:41.970 --> 00:07:44.090 align:start position:0% snarks and so this assures so for subscriptions<00:07:42.570> we<00:07:42.810> need<00:07:43.020> to<00:07:43.290> establish<00:07:43.950> a 00:07:44.090 --> 00:07:44.100 align:start position:0% subscriptions we need to establish a 00:07:44.100 --> 00:07:45.530 align:start position:0% subscriptions we need to establish a relationship<00:07:44.220> between<00:07:44.700> the<00:07:45.060> customer<00:07:45.510> and 00:07:45.530 --> 00:07:45.540 align:start position:0% relationship between the customer and 00:07:45.540 --> 00:07:48.020 align:start position:0% relationship between the customer and the<00:07:45.750> merchant<00:07:46.170> to<00:07:46.680> facilitate<00:07:47.340> payments<00:07:47.580> that 00:07:48.020 --> 00:07:48.030 align:start position:0% the merchant to facilitate payments that 00:07:48.030 --> 00:07:52.370 align:start position:0% the merchant to facilitate payments that repeat<00:07:48.750> at<00:07:48.960> specific<00:07:49.470> intervals<00:07:50.960> so<00:07:51.960> we<00:07:52.230> went 00:07:52.370 --> 00:07:52.380 align:start position:0% repeat at specific intervals so we went 00:07:52.380 --> 00:07:54.020 align:start position:0% repeat at specific intervals so we went on<00:07:52.560> to<00:07:52.770> look<00:07:52.800> at<00:07:53.040> subscriptions<00:07:53.670> with 00:07:54.020 --> 00:07:54.030 align:start position:0% on to look at subscriptions with 00:07:54.030 --> 00:07:56.750 align:start position:0% on to look at subscriptions with cryptocurrency<00:07:54.620> so<00:07:55.620> when<00:07:56.100> we<00:07:56.250> researched 00:07:56.750 --> 00:07:56.760 align:start position:0% cryptocurrency so when we researched 00:07:56.760 --> 00:07:58.700 align:start position:0% cryptocurrency so when we researched what<00:07:57.060> was<00:07:57.180> out<00:07:57.360> there<00:07:57.390> and<00:07:57.900> the<00:07:58.110> standards<00:07:58.500> for 00:07:58.700 --> 00:07:58.710 align:start position:0% what was out there and the standards for 00:07:58.710 --> 00:08:00.320 align:start position:0% what was out there and the standards for doing<00:07:58.920> subscription<00:07:59.490> payments<00:07:59.880> with<00:08:00.000> crypto 00:08:00.320 --> 00:08:00.330 align:start position:0% doing subscription payments with crypto 00:08:00.330 --> 00:08:02.720 align:start position:0% doing subscription payments with crypto currencies<00:08:00.810> what<00:08:01.800> we<00:08:01.890> found<00:08:02.070> was<00:08:02.340> a<00:08:02.370> bit 00:08:02.720 --> 00:08:02.730 align:start position:0% currencies what we found was a bit 00:08:02.730 --> 00:08:04.520 align:start position:0% currencies what we found was a bit limiting<00:08:03.150> and<00:08:03.390> didn't<00:08:03.780> quite<00:08:04.020> meet<00:08:04.200> our<00:08:04.320> needs 00:08:04.520 --> 00:08:04.530 align:start position:0% limiting and didn't quite meet our needs 00:08:04.530 --> 00:08:05.930 align:start position:0% limiting and didn't quite meet our needs especially<00:08:04.860> in<00:08:05.190> the<00:08:05.280> case<00:08:05.460> of<00:08:05.640> end-to-end 00:08:05.930 --> 00:08:05.940 align:start position:0% especially in the case of end-to-end 00:08:05.940 --> 00:08:09.920 align:start position:0% especially in the case of end-to-end privacy<00:08:07.400> one<00:08:08.400> current<00:08:08.820> use<00:08:09.060> of<00:08:09.090> ZK<00:08:09.540> shielded 00:08:09.920 --> 00:08:09.930 align:start position:0% privacy one current use of ZK shielded 00:08:09.930 --> 00:08:11.930 align:start position:0% privacy one current use of ZK shielded transactions<00:08:10.590> is<00:08:10.800> to<00:08:10.920> have<00:08:11.070> people<00:08:11.310> prepay 00:08:11.930 --> 00:08:11.940 align:start position:0% transactions is to have people prepay 00:08:11.940 --> 00:08:16.040 align:start position:0% transactions is to have people prepay for<00:08:11.970> their<00:08:12.360> subscriptions<00:08:13.340> this<00:08:14.340> this<00:08:15.050> works 00:08:16.040 --> 00:08:16.050 align:start position:0% for their subscriptions this this works 00:08:16.050 --> 00:08:18.560 align:start position:0% for their subscriptions this this works okay<00:08:16.920> this<00:08:17.100> is<00:08:17.220> not<00:08:17.370> ideal<00:08:17.520> for<00:08:18.000> subscriptions 00:08:18.560 --> 00:08:18.570 align:start position:0% okay this is not ideal for subscriptions 00:08:18.570 --> 00:08:20.750 align:start position:0% okay this is not ideal for subscriptions but<00:08:19.200> this<00:08:19.350> does<00:08:19.560> work<00:08:19.800> for<00:08:20.040> some<00:08:20.100> service 00:08:20.750 --> 00:08:20.760 align:start position:0% but this does work for some service 00:08:20.760 --> 00:08:22.250 align:start position:0% but this does work for some service offerings<00:08:21.270> where<00:08:21.510> you<00:08:21.600> can<00:08:21.750> turn<00:08:21.900> off<00:08:22.110> the 00:08:22.250 --> 00:08:22.260 align:start position:0% offerings where you can turn off the 00:08:22.260 --> 00:08:24.680 align:start position:0% offerings where you can turn off the service<00:08:22.650> when<00:08:23.370> a<00:08:23.400> payment<00:08:23.730> lapses<00:08:24.360> and<00:08:24.570> then 00:08:24.680 --> 00:08:24.690 align:start position:0% service when a payment lapses and then 00:08:24.690 --> 00:08:26.540 align:start position:0% service when a payment lapses and then turn<00:08:24.840> it<00:08:24.960> back<00:08:25.080> on<00:08:25.230> later<00:08:25.530> after<00:08:26.040> new<00:08:26.160> payment 00:08:26.540 --> 00:08:26.550 align:start position:0% turn it back on later after new payment 00:08:26.550 --> 00:08:28.730 align:start position:0% turn it back on later after new payment and<00:08:26.730> like<00:08:27.450> for<00:08:27.840> example<00:08:27.900> electricity 00:08:28.730 --> 00:08:28.740 align:start position:0% and like for example electricity 00:08:28.740 --> 00:08:31.160 align:start position:0% and like for example electricity payments<00:08:29.450> however<00:08:30.450> in<00:08:30.690> our<00:08:30.840> case<00:08:31.140> because 00:08:31.160 --> 00:08:31.170 align:start position:0% payments however in our case because 00:08:31.170 --> 00:08:33.920 align:start position:0% payments however in our case because people<00:08:31.830> are<00:08:31.920> uploading<00:08:32.070> data<00:08:32.670> to<00:08:33.270> be<00:08:33.630> stored 00:08:33.920 --> 00:08:33.930 align:start position:0% people are uploading data to be stored 00:08:33.930 --> 00:08:36.230 align:start position:0% people are uploading data to be stored on<00:08:34.200> our<00:08:34.230> storage<00:08:34.980> service<00:08:35.520> this<00:08:35.790> is<00:08:35.940> not<00:08:36.090> an 00:08:36.230 --> 00:08:36.240 align:start position:0% on our storage service this is not an 00:08:36.240 --> 00:08:39.830 align:start position:0% on our storage service this is not an ideal<00:08:36.480> user<00:08:36.920> experience<00:08:37.920> because<00:08:38.340> if<00:08:38.880> they 00:08:39.830 --> 00:08:39.840 align:start position:0% ideal user experience because if they 00:08:39.840 --> 00:08:42.590 align:start position:0% ideal user experience because if they stop<00:08:40.440> their<00:08:40.650> server<00:08:40.860> because<00:08:41.340> of<00:08:41.550> the<00:08:41.790> need<00:08:42.360> to 00:08:42.590 --> 00:08:42.600 align:start position:0% stop their server because of the need to 00:08:42.600 --> 00:08:44.450 align:start position:0% stop their server because of the need to re-upload<00:08:43.050> that<00:08:43.350> data<00:08:43.590> every<00:08:43.830> single<00:08:44.250> time 00:08:44.450 --> 00:08:44.460 align:start position:0% re-upload that data every single time 00:08:44.460 --> 00:08:47.840 align:start position:0% re-upload that data every single time and<00:08:44.760> so<00:08:45.510> amongst<00:08:46.410> other<00:08:46.560> downsides<00:08:47.520> to<00:08:47.760> this 00:08:47.840 --> 00:08:47.850 align:start position:0% and so amongst other downsides to this 00:08:47.850 --> 00:08:50.570 align:start position:0% and so amongst other downsides to this approach<00:08:48.090> -<00:08:48.450> and<00:08:48.800> then<00:08:49.800> another<00:08:50.040> option<00:08:50.460> is<00:08:50.550> to 00:08:50.570 --> 00:08:50.580 align:start position:0% approach - and then another option is to 00:08:50.580 --> 00:08:52.430 align:start position:0% approach - and then another option is to do<00:08:50.790> post<00:08:51.060> paid<00:08:51.300> subscriptions<00:08:51.930> but<00:08:52.200> this<00:08:52.320> is 00:08:52.430 --> 00:08:52.440 align:start position:0% do post paid subscriptions but this is 00:08:52.440 --> 00:08:53.870 align:start position:0% do post paid subscriptions but this is also<00:08:52.620> not<00:08:52.770> ideal<00:08:52.950> and<00:08:53.640> it<00:08:53.700> may 00:08:53.870 --> 00:08:53.880 align:start position:0% also not ideal and it may 00:08:53.880 --> 00:08:55.970 align:start position:0% also not ideal and it may renewal<00:08:54.480> or<00:08:54.660> payment<00:08:55.020> periodicity<00:08:55.530> a 00:08:55.970 --> 00:08:55.980 align:start position:0% renewal or payment periodicity a 00:08:55.980 --> 00:08:59.450 align:start position:0% renewal or payment periodicity a challenge<00:08:56.810> and<00:08:57.810> of<00:08:58.410> course<00:08:58.650> you<00:08:59.160> can<00:08:59.310> use 00:08:59.450 --> 00:08:59.460 align:start position:0% challenge and of course you can use 00:08:59.460 --> 00:09:00.890 align:start position:0% challenge and of course you can use smart<00:08:59.670> contracts<00:09:00.150> for<00:09:00.300> managing<00:09:00.690> some 00:09:00.890 --> 00:09:00.900 align:start position:0% smart contracts for managing some 00:09:00.900 --> 00:09:03.620 align:start position:0% smart contracts for managing some aspects<00:09:01.350> of<00:09:01.500> subscriptions<00:09:02.130> but<00:09:02.820> this<00:09:03.060> and 00:09:03.620 --> 00:09:03.630 align:start position:0% aspects of subscriptions but this and 00:09:03.630 --> 00:09:05.270 align:start position:0% aspects of subscriptions but this and this<00:09:03.780> is<00:09:03.930> an<00:09:04.050> option<00:09:04.380> with<00:09:04.530> aetherium<00:09:05.010> and 00:09:05.270 --> 00:09:05.280 align:start position:0% this is an option with aetherium and 00:09:05.280 --> 00:09:07.460 align:start position:0% this is an option with aetherium and other<00:09:05.700> platforms<00:09:06.420> but<00:09:06.720> it<00:09:07.020> doesn't<00:09:07.350> really 00:09:07.460 --> 00:09:07.470 align:start position:0% other platforms but it doesn't really 00:09:07.470 --> 00:09:09.980 align:start position:0% other platforms but it doesn't really offer<00:09:07.680> much<00:09:08.070> in<00:09:08.490> terms<00:09:08.970> of<00:09:09.270> privacy<00:09:09.660> at<00:09:09.870> the 00:09:09.980 --> 00:09:09.990 align:start position:0% offer much in terms of privacy at the 00:09:09.990 --> 00:09:12.770 align:start position:0% offer much in terms of privacy at the moment<00:09:10.320> and<00:09:10.550> you<00:09:11.550> can't<00:09:11.790> do<00:09:12.000> those<00:09:12.180> on<00:09:12.450> the<00:09:12.660> Z 00:09:12.770 --> 00:09:12.780 align:start position:0% moment and you can't do those on the Z 00:09:12.780 --> 00:09:14.300 align:start position:0% moment and you can't do those on the Z cash<00:09:12.960> blockchain<00:09:13.440> at<00:09:13.650> the<00:09:13.740> moment<00:09:14.070> and<00:09:14.160> I<00:09:14.190> hope 00:09:14.300 --> 00:09:14.310 align:start position:0% cash blockchain at the moment and I hope 00:09:14.310 --> 00:09:15.920 align:start position:0% cash blockchain at the moment and I hope to<00:09:14.520> see<00:09:14.640> both<00:09:14.790> of<00:09:14.910> those<00:09:15.000> things<00:09:15.240> change<00:09:15.600> soon 00:09:15.920 --> 00:09:15.930 align:start position:0% to see both of those things change soon 00:09:15.930 --> 00:09:19.220 align:start position:0% to see both of those things change soon too<00:09:16.400> so<00:09:17.400> this<00:09:18.090> meant<00:09:18.630> what<00:09:18.780> this<00:09:18.900> meant<00:09:19.080> is 00:09:19.220 --> 00:09:19.230 align:start position:0% too so this meant what this meant is 00:09:19.230 --> 00:09:21.020 align:start position:0% too so this meant what this meant is that<00:09:19.560> we<00:09:19.680> need<00:09:19.860> to<00:09:19.890> do<00:09:20.100> some<00:09:20.370> work<00:09:20.550> on<00:09:20.700> defied 00:09:21.020 --> 00:09:21.030 align:start position:0% that we need to do some work on defied 00:09:21.030 --> 00:09:22.550 align:start position:0% that we need to do some work on defied and<00:09:21.240> defining<00:09:21.720> how<00:09:21.870> to<00:09:21.930> preserve<00:09:22.170> privacy 00:09:22.550 --> 00:09:22.560 align:start position:0% and defining how to preserve privacy 00:09:22.560 --> 00:09:24.470 align:start position:0% and defining how to preserve privacy while<00:09:22.980> still<00:09:23.220> establishing<00:09:23.880> the<00:09:24.000> necessary 00:09:24.470 --> 00:09:24.480 align:start position:0% while still establishing the necessary 00:09:24.480 --> 00:09:26.120 align:start position:0% while still establishing the necessary relationship<00:09:25.020> for<00:09:25.410> these<00:09:25.530> reoccurring 00:09:26.120 --> 00:09:26.130 align:start position:0% relationship for these reoccurring 00:09:26.130 --> 00:09:27.680 align:start position:0% relationship for these reoccurring cryptocurrency<00:09:26.760> payments<00:09:27.450> for<00:09:27.660> a 00:09:27.680 --> 00:09:27.690 align:start position:0% cryptocurrency payments for a 00:09:27.690 --> 00:09:31.070 align:start position:0% cryptocurrency payments for a subscription<00:09:28.550> so<00:09:29.550> this<00:09:30.030> is<00:09:30.210> what<00:09:30.360> we<00:09:30.480> came<00:09:31.020> up 00:09:31.070 --> 00:09:31.080 align:start position:0% subscription so this is what we came up 00:09:31.080 --> 00:09:34.970 align:start position:0% subscription so this is what we came up with<00:09:32.120> for<00:09:33.120> p4<00:09:33.540> on<00:09:33.720> the<00:09:34.170> left<00:09:34.380> side<00:09:34.590> there's<00:09:34.920> a 00:09:34.970 --> 00:09:34.980 align:start position:0% with for p4 on the left side there's a 00:09:34.980 --> 00:09:36.980 align:start position:0% with for p4 on the left side there's a list<00:09:35.220> of<00:09:35.370> basic<00:09:35.730> tasks<00:09:36.240> that<00:09:36.420> we<00:09:36.570> could<00:09:36.780> that 00:09:36.980 --> 00:09:36.990 align:start position:0% list of basic tasks that we could that 00:09:36.990 --> 00:09:38.150 align:start position:0% list of basic tasks that we could that we<00:09:37.080> need<00:09:37.260> to<00:09:37.380> have<00:09:37.530> completed<00:09:37.830> by<00:09:38.130> a 00:09:38.150 --> 00:09:38.160 align:start position:0% we need to have completed by a 00:09:38.160 --> 00:09:41.030 align:start position:0% we need to have completed by a subscription<00:09:38.790> and<00:09:39.030> on<00:09:39.270> the<00:09:39.540> right<00:09:40.470> side<00:09:40.680> you 00:09:41.030 --> 00:09:41.040 align:start position:0% subscription and on the right side you 00:09:41.040 --> 00:09:43.460 align:start position:0% subscription and on the right side you can<00:09:41.070> see<00:09:41.400> the<00:09:41.550> various<00:09:41.940> pieces<00:09:42.750> that<00:09:43.260> the 00:09:43.460 --> 00:09:43.470 align:start position:0% can see the various pieces that the 00:09:43.470 --> 00:09:44.900 align:start position:0% can see the various pieces that the various<00:09:43.920> layers<00:09:44.130> the<00:09:44.460> pieces<00:09:44.760> that<00:09:44.880> I 00:09:44.900 --> 00:09:44.910 align:start position:0% various layers the pieces that I 00:09:44.910 --> 00:09:46.850 align:start position:0% various layers the pieces that I mentioned<00:09:45.270> earlier<00:09:45.570> and<00:09:45.810> they're<00:09:46.350> part<00:09:46.650> in 00:09:46.850 --> 00:09:46.860 align:start position:0% mentioned earlier and they're part in 00:09:46.860 --> 00:09:48.890 align:start position:0% mentioned earlier and they're part in these<00:09:46.980> different<00:09:47.430> steps<00:09:47.640> and<00:09:48.000> then<00:09:48.570> this<00:09:48.720> is 00:09:48.890 --> 00:09:48.900 align:start position:0% these different steps and then this is 00:09:48.900 --> 00:09:53.210 align:start position:0% these different steps and then this is all<00:09:49.080> done<00:09:49.290> over<00:09:49.440> the<00:09:49.680> Tor<00:09:49.860> network<00:09:51.680> so<00:09:52.680> in<00:09:53.100> the 00:09:53.210 --> 00:09:53.220 align:start position:0% all done over the Tor network so in the 00:09:53.220 --> 00:09:54.620 align:start position:0% all done over the Tor network so in the first<00:09:53.370> step<00:09:53.700> we<00:09:54.030> have<00:09:54.060> the<00:09:54.420> subscription 00:09:54.620 --> 00:09:54.630 align:start position:0% first step we have the subscription 00:09:54.630 --> 00:09:57.320 align:start position:0% first step we have the subscription initiation<00:09:55.470> the<00:09:56.340> customer<00:09:56.730> visits<00:09:57.120> a<00:09:57.180> web 00:09:57.320 --> 00:09:57.330 align:start position:0% initiation the customer visits a web 00:09:57.330 --> 00:09:58.910 align:start position:0% initiation the customer visits a web page<00:09:57.510> and<00:09:57.840> completes<00:09:58.170> the<00:09:58.290> subscription 00:09:58.910 --> 00:09:58.920 align:start position:0% page and completes the subscription 00:09:58.920 --> 00:10:01.130 align:start position:0% page and completes the subscription request<00:09:59.280> now<00:09:59.910> because<00:10:00.360> we're<00:10:00.540> not<00:10:00.570> caring<00:10:01.080> for 00:10:01.130 --> 00:10:01.140 align:start position:0% request now because we're not caring for 00:10:01.140 --> 00:10:03.440 align:start position:0% request now because we're not caring for much<00:10:01.530> personal<00:10:02.010> data<00:10:02.190> this<00:10:02.490> is<00:10:02.880> probably<00:10:03.330> just 00:10:03.440 --> 00:10:03.450 align:start position:0% much personal data this is probably just 00:10:03.450 --> 00:10:05.660 align:start position:0% much personal data this is probably just a<00:10:03.690> button<00:10:03.870> actually<00:10:04.860> right<00:10:05.010> now<00:10:05.160> it<00:10:05.280> is<00:10:05.370> just<00:10:05.610> a 00:10:05.660 --> 00:10:05.670 align:start position:0% a button actually right now it is just a 00:10:05.670 --> 00:10:07.190 align:start position:0% a button actually right now it is just a button<00:10:05.820> we<00:10:06.210> don't<00:10:06.390> have<00:10:06.540> any<00:10:06.690> fields<00:10:07.050> or<00:10:07.170> a 00:10:07.190 --> 00:10:07.200 align:start position:0% button we don't have any fields or a 00:10:07.200 --> 00:10:08.900 align:start position:0% button we don't have any fields or a form<00:10:07.470> for<00:10:07.680> them<00:10:07.770> to<00:10:07.800> fill<00:10:07.950> out<00:10:08.190> because<00:10:08.760> we 00:10:08.900 --> 00:10:08.910 align:start position:0% form for them to fill out because we 00:10:08.910 --> 00:10:10.070 align:start position:0% form for them to fill out because we don't<00:10:09.030> want<00:10:09.180> any<00:10:09.300> more<00:10:09.390> data<00:10:09.570> we<00:10:09.720> just<00:10:09.840> want<00:10:10.020> to 00:10:10.070 --> 00:10:10.080 align:start position:0% don't want any more data we just want to 00:10:10.080 --> 00:10:11.900 align:start position:0% don't want any more data we just want to know<00:10:10.170> that<00:10:10.290> they<00:10:10.380> want<00:10:10.530> to<00:10:10.620> do<00:10:10.710> this<00:10:10.830> and<00:10:11.130> so 00:10:11.900 --> 00:10:11.910 align:start position:0% know that they want to do this and so 00:10:11.910 --> 00:10:14.600 align:start position:0% know that they want to do this and so and<00:10:12.300> then<00:10:12.990> the<00:10:13.080> second<00:10:13.440> step<00:10:13.590> is<00:10:13.890> subscription 00:10:14.600 --> 00:10:14.610 align:start position:0% and then the second step is subscription 00:10:14.610 --> 00:10:17.240 align:start position:0% and then the second step is subscription creation<00:10:15.150> and<00:10:15.480> invitation<00:10:16.290> and<00:10:16.350> byte<00:10:16.560> code<00:10:16.800> so 00:10:17.240 --> 00:10:17.250 align:start position:0% creation and invitation and byte code so 00:10:17.250 --> 00:10:20.000 align:start position:0% creation and invitation and byte code so we<00:10:17.460> the<00:10:17.610> merchant<00:10:18.000> create<00:10:18.390> Z<00:10:19.290> cash<00:10:19.470> address 00:10:20.000 --> 00:10:20.010 align:start position:0% we the merchant create Z cash address 00:10:20.010 --> 00:10:22.730 align:start position:0% we the merchant create Z cash address and<00:10:20.280> the<00:10:20.460> and<00:10:20.760> an<00:10:21.150> initial<00:10:21.420> database<00:10:21.840> entry<00:10:22.410> to 00:10:22.730 --> 00:10:22.740 align:start position:0% and the and an initial database entry to 00:10:22.740 --> 00:10:24.680 align:start position:0% and the and an initial database entry to link<00:10:22.950> the<00:10:23.070> subscription<00:10:23.640> ID<00:10:23.820> to<00:10:24.180> the<00:10:24.300> Z<00:10:24.480> cash 00:10:24.680 --> 00:10:24.690 align:start position:0% link the subscription ID to the Z cash 00:10:24.690 --> 00:10:27.230 align:start position:0% link the subscription ID to the Z cash address<00:10:25.170> we<00:10:25.920> generate<00:10:26.340> a<00:10:26.370> special<00:10:26.850> invite 00:10:27.230 --> 00:10:27.240 align:start position:0% address we generate a special invite 00:10:27.240 --> 00:10:30.200 align:start position:0% address we generate a special invite code<00:10:27.540> for<00:10:27.870> the<00:10:27.960> subscription<00:10:28.670> that<00:10:29.670> includes 00:10:30.200 --> 00:10:30.210 align:start position:0% code for the subscription that includes 00:10:30.210 --> 00:10:32.900 align:start position:0% code for the subscription that includes configuration<00:10:31.110> details<00:10:31.530> to<00:10:32.310> access<00:10:32.760> our 00:10:32.900 --> 00:10:32.910 align:start position:0% configuration details to access our 00:10:32.910 --> 00:10:34.910 align:start position:0% configuration details to access our storage<00:10:33.210> servers<00:10:33.720> the<00:10:34.110> capability<00:10:34.740> that<00:10:34.860> I 00:10:34.910 --> 00:10:34.920 align:start position:0% storage servers the capability that I 00:10:34.920 --> 00:10:37.550 align:start position:0% storage servers the capability that I mentioned<00:10:35.310> before<00:10:35.400> and<00:10:35.900> it<00:10:36.900> also<00:10:37.050> includes 00:10:37.550 --> 00:10:37.560 align:start position:0% mentioned before and it also includes 00:10:37.560 --> 00:10:39.790 align:start position:0% mentioned before and it also includes the<00:10:37.680> initial<00:10:37.890> invoice<00:10:38.370> for<00:10:38.700> the<00:10:38.730> service<00:10:39.150> and 00:10:39.790 --> 00:10:39.800 align:start position:0% the initial invoice for the service and 00:10:39.800 --> 00:10:42.860 align:start position:0% the initial invoice for the service and in<00:10:40.800> that<00:10:40.950> invoice<00:10:41.340> is<00:10:41.610> a<00:10:41.640> signature<00:10:42.030> so<00:10:42.720> that 00:10:42.860 --> 00:10:42.870 align:start position:0% in that invoice is a signature so that 00:10:42.870 --> 00:10:44.330 align:start position:0% in that invoice is a signature so that they<00:10:42.960> can<00:10:43.110> also<00:10:43.230> verify<00:10:43.560> us<00:10:43.890> in<00:10:44.010> the<00:10:44.070> future 00:10:44.330 --> 00:10:44.340 align:start position:0% they can also verify us in the future 00:10:44.340 --> 00:10:47.090 align:start position:0% they can also verify us in the future and<00:10:44.660> then<00:10:45.660> the<00:10:45.780> third<00:10:45.960> step<00:10:46.260> is<00:10:46.500> client<00:10:46.770> side 00:10:47.090 --> 00:10:47.100 align:start position:0% and then the third step is client side 00:10:47.100 --> 00:10:49.910 align:start position:0% and then the third step is client side subscription<00:10:48.090> configuration<00:10:48.840> the<00:10:49.470> customers 00:10:49.910 --> 00:10:49.920 align:start position:0% subscription configuration the customers 00:10:49.920 --> 00:10:52.670 align:start position:0% subscription configuration the customers client<00:10:50.370> a<00:10:50.490> desktop<00:10:50.970> application<00:10:51.150> in<00:10:52.140> our<00:10:52.410> case 00:10:52.670 --> 00:10:52.680 align:start position:0% client a desktop application in our case 00:10:52.680 --> 00:10:54.190 align:start position:0% client a desktop application in our case grid<00:10:53.010> sync<00:10:53.250> that<00:10:53.580> I<00:10:53.610> mentioned<00:10:54.000> earlier 00:10:54.190 --> 00:10:54.200 align:start position:0% grid sync that I mentioned earlier 00:10:54.200 --> 00:10:56.840 align:start position:0% grid sync that I mentioned earlier securely<00:10:55.200> connects<00:10:55.620> to<00:10:55.830> us<00:10:55.950> receives<00:10:56.520> and 00:10:56.840 --> 00:10:56.850 align:start position:0% securely connects to us receives and 00:10:56.850 --> 00:10:58.700 align:start position:0% securely connects to us receives and receives<00:10:57.330> the<00:10:57.510> invite<00:10:57.840> code<00:10:58.020> and<00:10:58.320> then<00:10:58.500> gets 00:10:58.700 --> 00:10:58.710 align:start position:0% receives the invite code and then gets 00:10:58.710 --> 00:11:00.380 align:start position:0% receives the invite code and then gets configured<00:10:59.280> for<00:10:59.490> both<00:10:59.610> managing<00:11:00.120> the<00:11:00.240> data 00:11:00.380 --> 00:11:00.390 align:start position:0% configured for both managing the data 00:11:00.390 --> 00:11:03.110 align:start position:0% configured for both managing the data they<00:11:01.350> will<00:11:01.590> store<00:11:01.800> on<00:11:01.950> our<00:11:02.070> service<00:11:02.490> and<00:11:02.730> also 00:11:03.110 --> 00:11:03.120 align:start position:0% they will store on our service and also 00:11:03.120 --> 00:11:04.730 align:start position:0% they will store on our service and also the<00:11:03.240> invoices<00:11:03.780> they<00:11:03.900> will<00:11:04.020> receive<00:11:04.350> for<00:11:04.620> it 00:11:04.730 --> 00:11:04.740 align:start position:0% the invoices they will receive for it 00:11:04.740 --> 00:11:07.850 align:start position:0% the invoices they will receive for it and<00:11:05.930> the<00:11:06.930> fourth<00:11:07.170> step<00:11:07.440> is 00:11:07.850 --> 00:11:07.860 align:start position:0% and the fourth step is 00:11:07.860 --> 00:11:10.100 align:start position:0% and the fourth step is payment<00:11:08.160> and<00:11:08.279> server<00:11:08.519> update<00:11:09.089> next<00:11:09.899> the 00:11:10.100 --> 00:11:10.110 align:start position:0% payment and server update next the 00:11:10.110 --> 00:11:11.329 align:start position:0% payment and server update next the customer<00:11:10.440> has<00:11:10.589> to<00:11:10.620> actually<00:11:10.829> send<00:11:11.190> their 00:11:11.329 --> 00:11:11.339 align:start position:0% customer has to actually send their 00:11:11.339 --> 00:11:14.389 align:start position:0% customer has to actually send their first<00:11:11.519> payment<00:11:11.910> for<00:11:12.480> the<00:11:12.570> service<00:11:13.339> for<00:11:14.339> the 00:11:14.389 --> 00:11:14.399 align:start position:0% first payment for the service for the 00:11:14.399 --> 00:11:16.280 align:start position:0% first payment for the service for the service<00:11:14.760> per<00:11:15.209> the<00:11:15.390> invoice<00:11:15.690> that<00:11:15.720> they<00:11:16.050> just 00:11:16.280 --> 00:11:16.290 align:start position:0% service per the invoice that they just 00:11:16.290 --> 00:11:17.900 align:start position:0% service per the invoice that they just received<00:11:16.620> and<00:11:16.950> they<00:11:17.339> need<00:11:17.519> to<00:11:17.640> do<00:11:17.760> this 00:11:17.900 --> 00:11:17.910 align:start position:0% received and they need to do this 00:11:17.910 --> 00:11:20.930 align:start position:0% received and they need to do this payment<00:11:18.180> via<00:11:18.570> a<00:11:18.690> Z<00:11:18.959> cash<00:11:19.140> wallet<00:11:19.550> that<00:11:20.550> payment 00:11:20.930 --> 00:11:20.940 align:start position:0% payment via a Z cash wallet that payment 00:11:20.940 --> 00:11:22.610 align:start position:0% payment via a Z cash wallet that payment is<00:11:21.029> processed<00:11:21.209> on<00:11:21.600> the<00:11:21.660> Z<00:11:21.870> cash<00:11:22.050> blockchain 00:11:22.610 --> 00:11:22.620 align:start position:0% is processed on the Z cash blockchain 00:11:22.620 --> 00:11:25.069 align:start position:0% is processed on the Z cash blockchain and<00:11:22.860> we<00:11:23.430> consider<00:11:23.790> it<00:11:23.910> a<00:11:24.000> confirmed<00:11:24.660> after<00:11:24.899> a 00:11:25.069 --> 00:11:25.079 align:start position:0% and we consider it a confirmed after a 00:11:25.079 --> 00:11:27.250 align:start position:0% and we consider it a confirmed after a certain<00:11:25.350> number<00:11:25.500> of<00:11:25.800> blocks<00:11:26.610> are<00:11:26.790> written 00:11:27.250 --> 00:11:27.260 align:start position:0% certain number of blocks are written 00:11:27.260 --> 00:11:29.540 align:start position:0% certain number of blocks are written that<00:11:28.260> might<00:11:28.620> not<00:11:28.740> take<00:11:28.920> too<00:11:29.070> long<00:11:29.190> maybe<00:11:29.430> about 00:11:29.540 --> 00:11:29.550 align:start position:0% that might not take too long maybe about 00:11:29.550 --> 00:11:31.430 align:start position:0% that might not take too long maybe about an<00:11:29.850> hour<00:11:30.060> I<00:11:30.390> think<00:11:30.720> right<00:11:30.899> now<00:11:30.930> we're<00:11:31.260> thinking 00:11:31.430 --> 00:11:31.440 align:start position:0% an hour I think right now we're thinking 00:11:31.440 --> 00:11:33.829 align:start position:0% an hour I think right now we're thinking about<00:11:31.649> 24<00:11:32.100> blocks<00:11:32.250> and<00:11:32.640> then<00:11:33.329> this<00:11:33.450> triggers 00:11:33.829 --> 00:11:33.839 align:start position:0% about 24 blocks and then this triggers 00:11:33.839 --> 00:11:37.449 align:start position:0% about 24 blocks and then this triggers the<00:11:34.050> publishing<00:11:34.440> of<00:11:34.769> the<00:11:35.010> next<00:11:35.339> invoice<00:11:36.230> so 00:11:37.449 --> 00:11:37.459 align:start position:0% the publishing of the next invoice so 00:11:37.459 --> 00:11:39.920 align:start position:0% the publishing of the next invoice so the<00:11:38.459> fifth<00:11:38.670> step<00:11:38.880> then<00:11:39.089> is<00:11:39.300> the<00:11:39.480> recurring 00:11:39.920 --> 00:11:39.930 align:start position:0% the fifth step then is the recurring 00:11:39.930 --> 00:11:41.780 align:start position:0% the fifth step then is the recurring invoice<00:11:40.230> and<00:11:40.470> payment<00:11:40.829> process<00:11:41.190> from<00:11:41.640> this 00:11:41.780 --> 00:11:41.790 align:start position:0% invoice and payment process from this 00:11:41.790 --> 00:11:43.910 align:start position:0% invoice and payment process from this point<00:11:42.089> the<00:11:42.300> client<00:11:42.480> monitors<00:11:43.019> the<00:11:43.440> next<00:11:43.709> for 00:11:43.910 --> 00:11:43.920 align:start position:0% point the client monitors the next for 00:11:43.920 --> 00:11:45.980 align:start position:0% point the client monitors the next for the<00:11:43.980> next<00:11:44.070> invoice<00:11:44.570> displays<00:11:45.570> it<00:11:45.779> to<00:11:45.899> the 00:11:45.980 --> 00:11:45.990 align:start position:0% the next invoice displays it to the 00:11:45.990 --> 00:11:47.810 align:start position:0% the next invoice displays it to the customer<00:11:46.410> and<00:11:46.589> continues<00:11:47.100> to<00:11:47.279> do<00:11:47.399> this<00:11:47.519> loop 00:11:47.810 --> 00:11:47.820 align:start position:0% customer and continues to do this loop 00:11:47.820 --> 00:11:50.019 align:start position:0% customer and continues to do this loop after<00:11:48.060> subsequent<00:11:48.779> payments<00:11:49.140> are<00:11:49.260> made<00:11:49.380> and 00:11:50.019 --> 00:11:50.029 align:start position:0% after subsequent payments are made and 00:11:50.029 --> 00:11:52.819 align:start position:0% after subsequent payments are made and within<00:11:51.050> when<00:11:52.050> they<00:11:52.140> go<00:11:52.320> checked<00:11:52.589> on<00:11:52.680> the 00:11:52.819 --> 00:11:52.829 align:start position:0% within when they go checked on the 00:11:52.829 --> 00:11:54.650 align:start position:0% within when they go checked on the invoice<00:11:53.100> there's<00:11:53.490> we<00:11:53.730> are<00:11:53.850> also<00:11:53.970> utilizing 00:11:54.650 --> 00:11:54.660 align:start position:0% invoice there's we are also utilizing 00:11:54.660 --> 00:11:59.030 align:start position:0% invoice there's we are also utilizing payment<00:11:55.050> codes<00:11:55.290> to<00:11:55.890> be<00:11:56.010> able<00:11:56.070> to<00:11:57.769> like<00:11:58.769> to 00:11:59.030 --> 00:11:59.040 align:start position:0% payment codes to be able to like to 00:11:59.040 --> 00:12:00.680 align:start position:0% payment codes to be able to like to communicate<00:11:59.220> to<00:11:59.640> them<00:11:59.760> the<00:11:59.880> status<00:12:00.209> of<00:12:00.480> the 00:12:00.680 --> 00:12:00.690 align:start position:0% communicate to them the status of the 00:12:00.690 --> 00:12:03.530 align:start position:0% communicate to them the status of the payment<00:12:00.870> and<00:12:01.140> then<00:12:01.800> also<00:12:02.130> Cigna<00:12:03.120> they<00:12:03.390> can 00:12:03.530 --> 00:12:03.540 align:start position:0% payment and then also Cigna they can 00:12:03.540 --> 00:12:05.480 align:start position:0% payment and then also Cigna they can also<00:12:03.660> verify<00:12:03.930> the<00:12:04.140> signature<00:12:04.649> with<00:12:05.190> each<00:12:05.339> of 00:12:05.480 --> 00:12:05.490 align:start position:0% also verify the signature with each of 00:12:05.490 --> 00:12:07.639 align:start position:0% also verify the signature with each of these<00:12:05.550> and<00:12:06.000> then<00:12:06.329> if<00:12:06.600> they<00:12:06.779> stop<00:12:07.050> paying<00:12:07.290> then 00:12:07.639 --> 00:12:07.649 align:start position:0% these and then if they stop paying then 00:12:07.649 --> 00:12:10.880 align:start position:0% these and then if they stop paying then their<00:12:07.800> service<00:12:08.100> is<00:12:08.250> stopped<00:12:09.140> so<00:12:10.140> privacy<00:12:10.769> is 00:12:10.880 --> 00:12:10.890 align:start position:0% their service is stopped so privacy is 00:12:10.890 --> 00:12:12.439 align:start position:0% their service is stopped so privacy is maintained<00:12:11.399> by<00:12:11.640> pushing<00:12:11.880> many<00:12:12.209> of<00:12:12.360> the 00:12:12.439 --> 00:12:12.449 align:start position:0% maintained by pushing many of the 00:12:12.449 --> 00:12:14.150 align:start position:0% maintained by pushing many of the subscription<00:12:12.839> management<00:12:13.140> activities<00:12:13.980> to 00:12:14.150 --> 00:12:14.160 align:start position:0% subscription management activities to 00:12:14.160 --> 00:12:16.220 align:start position:0% subscription management activities to the<00:12:14.250> users<00:12:14.519> device<00:12:14.880> into<00:12:15.690> their<00:12:15.810> client 00:12:16.220 --> 00:12:16.230 align:start position:0% the users device into their client 00:12:16.230 --> 00:12:18.530 align:start position:0% the users device into their client client<00:12:16.890> so<00:12:17.459> client<00:12:17.820> side<00:12:18.000> instead<00:12:18.480> of 00:12:18.530 --> 00:12:18.540 align:start position:0% client so client side instead of 00:12:18.540 --> 00:12:19.790 align:start position:0% client so client side instead of gathering<00:12:18.810> the<00:12:19.140> data<00:12:19.260> in<00:12:19.560> a<00:12:19.649> central 00:12:19.790 --> 00:12:19.800 align:start position:0% gathering the data in a central 00:12:19.800 --> 00:12:23.180 align:start position:0% gathering the data in a central repository<00:12:20.220> by<00:12:20.790> a<00:12:20.820> service<00:12:21.240> like<00:12:21.449> stripe<00:12:22.190> or 00:12:23.180 --> 00:12:23.190 align:start position:0% repository by a service like stripe or 00:12:23.190 --> 00:12:26.810 align:start position:0% repository by a service like stripe or the<00:12:23.430> equivalent<00:12:23.820> of<00:12:24.120> stripe<00:12:24.360> and<00:12:25.820> this 00:12:26.810 --> 00:12:26.820 align:start position:0% the equivalent of stripe and this 00:12:26.820 --> 00:12:28.759 align:start position:0% the equivalent of stripe and this decentralization<00:12:27.750> of<00:12:28.019> subscription<00:12:28.560> data 00:12:28.759 --> 00:12:28.769 align:start position:0% decentralization of subscription data 00:12:28.769 --> 00:12:30.319 align:start position:0% decentralization of subscription data along<00:12:29.279> with<00:12:29.490> the<00:12:29.610> Z<00:12:29.760> cache<00:12:29.940> shielded 00:12:30.319 --> 00:12:30.329 align:start position:0% along with the Z cache shielded 00:12:30.329 --> 00:12:32.540 align:start position:0% along with the Z cache shielded transactions<00:12:30.990> and<00:12:31.230> use<00:12:31.440> of<00:12:31.620> the<00:12:31.740> Tor<00:12:31.949> network 00:12:32.540 --> 00:12:32.550 align:start position:0% transactions and use of the Tor network 00:12:32.550 --> 00:12:35.300 align:start position:0% transactions and use of the Tor network allow<00:12:33.390> us<00:12:33.690> to<00:12:34.140> not<00:12:34.529> gather<00:12:34.800> personal 00:12:35.300 --> 00:12:35.310 align:start position:0% allow us to not gather personal 00:12:35.310 --> 00:12:36.860 align:start position:0% allow us to not gather personal information<00:12:35.790> about<00:12:35.880> customers<00:12:36.149> or<00:12:36.690> any 00:12:36.860 --> 00:12:36.870 align:start position:0% information about customers or any 00:12:36.870 --> 00:12:39.170 align:start position:0% information about customers or any metadata<00:12:37.410> that<00:12:37.560> could<00:12:37.860> be<00:12:37.980> correlated<00:12:38.310> for 00:12:39.170 --> 00:12:39.180 align:start position:0% metadata that could be correlated for 00:12:39.180 --> 00:12:43.670 align:start position:0% metadata that could be correlated for suggestions<00:12:39.600> on<00:12:40.040> who<00:12:41.040> the<00:12:41.190> user<00:12:41.399> is<00:12:42.529> so<00:12:43.529> we'll 00:12:43.670 --> 00:12:43.680 align:start position:0% suggestions on who the user is so we'll 00:12:43.680 --> 00:12:46.420 align:start position:0% suggestions on who the user is so we'll go<00:12:43.800> into<00:12:43.949> more<00:12:44.190> details<00:12:44.550> this<00:12:45.269> is<00:12:45.480> the<00:12:45.690> invoice 00:12:46.420 --> 00:12:46.430 align:start position:0% go into more details this is the invoice 00:12:46.430 --> 00:12:49.819 align:start position:0% go into more details this is the invoice so<00:12:47.430> as<00:12:47.730> for<00:12:47.940> data<00:12:48.089> standards<00:12:48.570> again<00:12:49.470> we<00:12:49.620> looked 00:12:49.819 --> 00:12:49.829 align:start position:0% so as for data standards again we looked 00:12:49.829 --> 00:12:51.380 align:start position:0% so as for data standards again we looked around<00:12:50.010> at<00:12:50.250> things<00:12:50.519> that<00:12:50.670> are<00:12:50.790> existing<00:12:51.060> right 00:12:51.380 --> 00:12:51.390 align:start position:0% around at things that are existing right 00:12:51.390 --> 00:12:54.740 align:start position:0% around at things that are existing right now<00:12:51.420> and<00:12:51.779> we<00:12:51.899> didn't<00:12:52.140> see<00:12:52.350> any<00:12:53.040> kind<00:12:53.399> of<00:12:53.750> common 00:12:54.740 --> 00:12:54.750 align:start position:0% now and we didn't see any kind of common 00:12:54.750 --> 00:12:56.630 align:start position:0% now and we didn't see any kind of common language<00:12:55.230> or<00:12:55.380> agreed-upon<00:12:55.709> protocol<00:12:56.399> for 00:12:56.630 --> 00:12:56.640 align:start position:0% language or agreed-upon protocol for 00:12:56.640 --> 00:12:58.460 align:start position:0% language or agreed-upon protocol for expressing<00:12:57.149> notions<00:12:57.540> like<00:12:57.660> billing<00:12:58.110> period 00:12:58.460 --> 00:12:58.470 align:start position:0% expressing notions like billing period 00:12:58.470 --> 00:13:00.199 align:start position:0% expressing notions like billing period due<00:12:58.649> date<00:12:58.829> grace<00:12:59.130> period<00:12:59.550> and<00:12:59.640> late<00:12:59.790> penalties 00:13:00.199 --> 00:13:00.209 align:start position:0% due date grace period and late penalties 00:13:00.209 --> 00:13:02.509 align:start position:0% due date grace period and late penalties so<00:13:01.079> we<00:13:01.470> designed<00:13:01.800> a<00:13:01.949> simple<00:13:02.100> invoice 00:13:02.509 --> 00:13:02.519 align:start position:0% so we designed a simple invoice 00:13:02.519 --> 00:13:03.949 align:start position:0% so we designed a simple invoice structure<00:13:02.940> to<00:13:03.149> allow<00:13:03.269> us<00:13:03.540> to<00:13:03.690> communicate 00:13:03.949 --> 00:13:03.959 align:start position:0% structure to allow us to communicate 00:13:03.959 --> 00:13:06.139 align:start position:0% structure to allow us to communicate this<00:13:04.290> information<00:13:04.500> on<00:13:05.160> the<00:13:05.670> right<00:13:05.820> you<00:13:05.970> see<00:13:06.000> a 00:13:06.139 --> 00:13:06.149 align:start position:0% this information on the right you see a 00:13:06.149 --> 00:13:07.910 align:start position:0% this information on the right you see a basic<00:13:06.510> list<00:13:06.630> of<00:13:06.810> data<00:13:07.019> that<00:13:07.350> we<00:13:07.470> need<00:13:07.500> to<00:13:07.740> have 00:13:07.910 --> 00:13:07.920 align:start position:0% basic list of data that we need to have 00:13:07.920 --> 00:13:10.069 align:start position:0% basic list of data that we need to have in<00:13:08.100> our<00:13:08.190> invoices<00:13:08.790> which<00:13:09.029> could<00:13:09.300> be<00:13:09.449> expanded 00:13:10.069 --> 00:13:10.079 align:start position:0% in our invoices which could be expanded 00:13:10.079 --> 00:13:12.259 align:start position:0% in our invoices which could be expanded to<00:13:10.290> include<00:13:10.800> more<00:13:11.370> data<00:13:11.640> for<00:13:11.910> additional 00:13:12.259 --> 00:13:12.269 align:start position:0% to include more data for additional 00:13:12.269 --> 00:13:14.480 align:start position:0% to include more data for additional features<00:13:12.570> in<00:13:12.720> the<00:13:12.779> future<00:13:12.899> and<00:13:13.890> on<00:13:14.130> the<00:13:14.279> left 00:13:14.480 --> 00:13:14.490 align:start position:0% features in the future and on the left 00:13:14.490 --> 00:13:17.120 align:start position:0% features in the future and on the left this<00:13:15.300> is<00:13:15.360> what<00:13:16.140> the<00:13:16.260> string<00:13:16.529> of<00:13:16.709> the<00:13:16.890> invoice 00:13:17.120 --> 00:13:17.130 align:start position:0% this is what the string of the invoice 00:13:17.130 --> 00:13:19.280 align:start position:0% this is what the string of the invoice data<00:13:17.399> actually<00:13:17.850> looks<00:13:18.060> like<00:13:18.209> in<00:13:18.480> this<00:13:18.930> example 00:13:19.280 --> 00:13:19.290 align:start position:0% data actually looks like in this example 00:13:19.290 --> 00:13:21.620 align:start position:0% data actually looks like in this example a<00:13:19.770> customer<00:13:20.550> is<00:13:20.850> being<00:13:21.060> asked 00:13:21.620 --> 00:13:21.630 align:start position:0% a customer is being asked 00:13:21.630 --> 00:13:24.680 align:start position:0% a customer is being asked point1<00:13:22.350> Zack<00:13:22.710> by<00:13:23.370> a<00:13:23.400> particular<00:13:23.940> date<00:13:24.000> here 00:13:24.680 --> 00:13:24.690 align:start position:0% point1 Zack by a particular date here 00:13:24.690 --> 00:13:26.360 align:start position:0% point1 Zack by a particular date here September<00:13:24.930> 4th<00:13:25.380> for<00:13:25.740> the<00:13:25.800> service<00:13:26.160> least 00:13:26.360 --> 00:13:26.370 align:start position:0% September 4th for the service least 00:13:26.370 --> 00:13:28.370 align:start position:0% September 4th for the service least authority<00:13:26.790> s<00:13:26.910> for<00:13:27.180> if<00:13:27.450> the<00:13:27.900> payment<00:13:28.260> is<00:13:28.350> made 00:13:28.370 --> 00:13:28.380 align:start position:0% authority s for if the payment is made 00:13:28.380 --> 00:13:30.320 align:start position:0% authority s for if the payment is made by<00:13:28.950> a<00:13:28.980> given<00:13:29.310> deadline<00:13:29.760> then<00:13:30.180> the 00:13:30.320 --> 00:13:30.330 align:start position:0% by a given deadline then the 00:13:30.330 --> 00:13:31.910 align:start position:0% by a given deadline then the subscription<00:13:30.840> will<00:13:30.990> be<00:13:31.080> extended<00:13:31.650> for<00:13:31.890> a 00:13:31.910 --> 00:13:31.920 align:start position:0% subscription will be extended for a 00:13:31.920 --> 00:13:34.940 align:start position:0% subscription will be extended for a month<00:13:32.250> 2.5<00:13:33.060> million<00:13:33.270> seconds<00:13:33.780> until<00:13:34.500> October 00:13:34.940 --> 00:13:34.950 align:start position:0% month 2.5 million seconds until October 00:13:34.950 --> 00:13:38.600 align:start position:0% month 2.5 million seconds until October 4th<00:13:35.250> 2018<00:13:36.180> and<00:13:36.780> I<00:13:37.680> think<00:13:37.920> in<00:13:38.040> the<00:13:38.130> future<00:13:38.250> we 00:13:38.600 --> 00:13:38.610 align:start position:0% 4th 2018 and I think in the future we 00:13:38.610 --> 00:13:41.420 align:start position:0% 4th 2018 and I think in the future we need<00:13:38.760> to<00:13:38.880> include<00:13:39.150> things<00:13:39.540> like<00:13:40.310> you<00:13:41.310> know 00:13:41.420 --> 00:13:41.430 align:start position:0% need to include things like you know 00:13:41.430 --> 00:13:43.790 align:start position:0% need to include things like you know trial<00:13:41.850> periods<00:13:42.330> refunds<00:13:42.960> things<00:13:43.410> like<00:13:43.620> that 00:13:43.790 --> 00:13:43.800 align:start position:0% trial periods refunds things like that 00:13:43.800 --> 00:13:45.500 align:start position:0% trial periods refunds things like that could<00:13:44.130> be<00:13:44.280> also<00:13:44.430> included<00:13:44.970> in<00:13:45.090> this<00:13:45.180> but<00:13:45.390> this 00:13:45.500 --> 00:13:45.510 align:start position:0% could be also included in this but this 00:13:45.510 --> 00:13:48.890 align:start position:0% could be also included in this but this was<00:13:45.660> just<00:13:45.690> basically<00:13:46.170> the<00:13:46.320> the<00:13:47.510> short<00:13:48.510> list<00:13:48.720> of 00:13:48.890 --> 00:13:48.900 align:start position:0% was just basically the the short list of 00:13:48.900 --> 00:13:50.420 align:start position:0% was just basically the the short list of data<00:13:49.110> that<00:13:49.320> we<00:13:49.440> need<00:13:49.620> to<00:13:49.770> just<00:13:49.950> process<00:13:50.340> an 00:13:50.420 --> 00:13:50.430 align:start position:0% data that we need to just process an 00:13:50.430 --> 00:13:56.840 align:start position:0% data that we need to just process an invoice<00:13:50.640> for<00:13:50.940> the<00:13:51.060> subscription<00:13:54.110> so<00:13:55.550> yeah<00:13:56.550> to 00:13:56.840 --> 00:13:56.850 align:start position:0% invoice for the subscription so yeah to 00:13:56.850 --> 00:13:58.970 align:start position:0% invoice for the subscription so yeah to start<00:13:57.090> to<00:13:57.210> talk<00:13:57.390> about<00:13:57.420> next<00:13:58.410> steps<00:13:58.560> and<00:13:58.860> where 00:13:58.970 --> 00:13:58.980 align:start position:0% start to talk about next steps and where 00:13:58.980 --> 00:13:59.780 align:start position:0% start to talk about next steps and where we're<00:13:59.130> at<00:13:59.220> right<00:13:59.250> now 00:13:59.780 --> 00:13:59.790 align:start position:0% we're at right now 00:13:59.790 --> 00:14:01.610 align:start position:0% we're at right now so<00:14:00.330> we're<00:14:00.480> wrapping<00:14:00.810> up<00:14:00.900> the<00:14:01.020> edits<00:14:01.320> to<00:14:01.500> our 00:14:01.610 --> 00:14:01.620 align:start position:0% so we're wrapping up the edits to our 00:14:01.620 --> 00:14:04.040 align:start position:0% so we're wrapping up the edits to our paper<00:14:01.830> about<00:14:02.460> this<00:14:02.670> work<00:14:02.910> and<00:14:03.150> the<00:14:03.720> privacy 00:14:04.040 --> 00:14:04.050 align:start position:0% paper about this work and the privacy 00:14:04.050 --> 00:14:06.140 align:start position:0% paper about this work and the privacy considerations<00:14:04.470> that<00:14:05.130> we've<00:14:05.250> made<00:14:05.520> in<00:14:05.820> the 00:14:06.140 --> 00:14:06.150 align:start position:0% considerations that we've made in the 00:14:06.150 --> 00:14:08.000 align:start position:0% considerations that we've made in the designing<00:14:06.750> of<00:14:06.840> it<00:14:06.990> we<00:14:07.200> think<00:14:07.410> that<00:14:07.560> by<00:14:07.680> also 00:14:08.000 --> 00:14:08.010 align:start position:0% designing of it we think that by also 00:14:08.010 --> 00:14:09.650 align:start position:0% designing of it we think that by also sharing<00:14:08.310> you<00:14:09.060> know<00:14:09.090> these<00:14:09.300> privacy 00:14:09.650 --> 00:14:09.660 align:start position:0% sharing you know these privacy 00:14:09.660 --> 00:14:11.360 align:start position:0% sharing you know these privacy considerations<00:14:10.020> not<00:14:10.710> just<00:14:10.950> the<00:14:11.070> technical 00:14:11.360 --> 00:14:11.370 align:start position:0% considerations not just the technical 00:14:11.370 --> 00:14:13.400 align:start position:0% considerations not just the technical specifications<00:14:12.270> of<00:14:12.360> what<00:14:12.420> we're<00:14:12.660> doing<00:14:12.750> that 00:14:13.400 --> 00:14:13.410 align:start position:0% specifications of what we're doing that 00:14:13.410 --> 00:14:15.020 align:start position:0% specifications of what we're doing that we<00:14:13.500> can<00:14:13.590> help<00:14:13.800> people<00:14:14.070> understand<00:14:14.640> more<00:14:14.970> about 00:14:15.020 --> 00:14:15.030 align:start position:0% we can help people understand more about 00:14:15.030 --> 00:14:17.300 align:start position:0% we can help people understand more about how<00:14:15.330> to<00:14:15.390> do<00:14:15.630> privacy<00:14:16.080> by<00:14:16.200> design<00:14:16.230> or<00:14:16.710> just<00:14:17.100> at 00:14:17.300 --> 00:14:17.310 align:start position:0% how to do privacy by design or just at 00:14:17.310 --> 00:14:19.160 align:start position:0% how to do privacy by design or just at least<00:14:17.520> explain<00:14:17.880> how<00:14:18.180> we're<00:14:18.600> trying<00:14:18.870> to<00:14:18.960> do<00:14:19.050> it 00:14:19.160 --> 00:14:19.170 align:start position:0% least explain how we're trying to do it 00:14:19.170 --> 00:14:22.490 align:start position:0% least explain how we're trying to do it and<00:14:20.150> we'll<00:14:21.150> be<00:14:21.270> publishing<00:14:21.870> that<00:14:21.990> paper<00:14:22.170> soon 00:14:22.490 --> 00:14:22.500 align:start position:0% and we'll be publishing that paper soon 00:14:22.500 --> 00:14:24.650 align:start position:0% and we'll be publishing that paper soon and<00:14:22.770> we've<00:14:23.370> already<00:14:23.640> started<00:14:24.210> implementing 00:14:24.650 --> 00:14:24.660 align:start position:0% and we've already started implementing 00:14:24.660 --> 00:14:27.050 align:start position:0% and we've already started implementing this<00:14:24.930> for<00:14:25.140> our<00:14:25.260> s4<00:14:25.710> service<00:14:26.130> we<00:14:26.400> hope<00:14:26.670> to<00:14:26.910> have 00:14:27.050 --> 00:14:27.060 align:start position:0% this for our s4 service we hope to have 00:14:27.060 --> 00:14:30.860 align:start position:0% this for our s4 service we hope to have this<00:14:28.280> we<00:14:29.280> hope<00:14:29.400> to<00:14:29.550> have<00:14:29.640> this<00:14:29.790> available<00:14:30.480> to 00:14:30.860 --> 00:14:30.870 align:start position:0% this we hope to have this available to 00:14:30.870 --> 00:14:32.870 align:start position:0% this we hope to have this available to pay<00:14:31.050> I<00:14:31.080> mean<00:14:31.530> to<00:14:31.680> use<00:14:31.950> ZK<00:14:32.490> shouldered 00:14:32.870 --> 00:14:32.880 align:start position:0% pay I mean to use ZK shouldered 00:14:32.880 --> 00:14:34.340 align:start position:0% pay I mean to use ZK shouldered transactions<00:14:33.420> to<00:14:33.540> pay<00:14:33.660> for<00:14:33.870> our<00:14:33.930> service 00:14:34.340 --> 00:14:34.350 align:start position:0% transactions to pay for our service 00:14:34.350 --> 00:14:37.340 align:start position:0% transactions to pay for our service subscription<00:14:34.760> sometime<00:14:35.760> in<00:14:35.940> a<00:14:36.000> few<00:14:36.180> weeks<00:14:36.350> and 00:14:37.340 --> 00:14:37.350 align:start position:0% subscription sometime in a few weeks and 00:14:37.350 --> 00:14:38.840 align:start position:0% subscription sometime in a few weeks and this<00:14:37.470> includes<00:14:37.860> making<00:14:38.130> updates<00:14:38.430> to<00:14:38.820> our 00:14:38.840 --> 00:14:38.850 align:start position:0% this includes making updates to our 00:14:38.850 --> 00:14:43.370 align:start position:0% this includes making updates to our desktop<00:14:39.300> client<00:14:39.690> grid<00:14:40.320> sync<00:14:40.590> and<00:14:40.890> also<00:14:42.380> yeah 00:14:43.370 --> 00:14:43.380 align:start position:0% desktop client grid sync and also yeah 00:14:43.380 --> 00:14:44.870 align:start position:0% desktop client grid sync and also yeah just<00:14:43.650> making<00:14:43.920> sure<00:14:44.130> that<00:14:44.370> the<00:14:44.610> you<00:14:44.850> know 00:14:44.870 --> 00:14:44.880 align:start position:0% just making sure that the you know 00:14:44.880 --> 00:14:46.880 align:start position:0% just making sure that the you know setting<00:14:45.210> up<00:14:45.330> this<00:14:45.990> also<00:14:46.200> includes<00:14:46.530> setting<00:14:46.710> up 00:14:46.880 --> 00:14:46.890 align:start position:0% setting up this also includes setting up 00:14:46.890 --> 00:14:49.130 align:start position:0% setting up this also includes setting up a<00:14:46.980> separate<00:14:47.250> tour<00:14:47.520> website<00:14:47.760> for<00:14:48.690> people<00:14:48.810> to 00:14:49.130 --> 00:14:49.140 align:start position:0% a separate tour website for people to 00:14:49.140 --> 00:14:51.680 align:start position:0% a separate tour website for people to visit<00:14:49.290> and<00:14:50.130> things<00:14:50.730> like<00:14:50.910> that<00:14:50.970> because<00:14:51.570> we 00:14:51.680 --> 00:14:51.690 align:start position:0% visit and things like that because we 00:14:51.690 --> 00:14:53.420 align:start position:0% visit and things like that because we need<00:14:51.780> to<00:14:51.960> force<00:14:52.170> people<00:14:52.380> even<00:14:52.770> from<00:14:53.100> the<00:14:53.250> time 00:14:53.420 --> 00:14:53.430 align:start position:0% need to force people even from the time 00:14:53.430 --> 00:14:55.400 align:start position:0% need to force people even from the time that<00:14:53.490> they're<00:14:53.760> interested<00:14:54.360> they're<00:14:54.780> browsing 00:14:55.400 --> 00:14:55.410 align:start position:0% that they're interested they're browsing 00:14:55.410 --> 00:14:57.290 align:start position:0% that they're interested they're browsing trying<00:14:56.340> to<00:14:56.460> figure<00:14:56.640> out<00:14:56.700> if<00:14:56.850> they<00:14:57.000> want<00:14:57.150> to 00:14:57.290 --> 00:14:57.300 align:start position:0% trying to figure out if they want to 00:14:57.300 --> 00:14:59.600 align:start position:0% trying to figure out if they want to subscribe<00:14:58.110> to<00:14:58.350> our<00:14:58.500> service<00:14:58.920> to<00:14:59.160> start<00:14:59.310> to<00:14:59.490> use 00:14:59.600 --> 00:14:59.610 align:start position:0% subscribe to our service to start to use 00:14:59.610 --> 00:15:01.190 align:start position:0% subscribe to our service to start to use tor<00:14:59.880> so<00:15:00.120> that<00:15:00.240> we<00:15:00.330> don't<00:15:00.480> get<00:15:00.630> that<00:15:00.690> IP<00:15:01.170> address 00:15:01.190 --> 00:15:01.200 align:start position:0% tor so that we don't get that IP address 00:15:01.200 --> 00:15:07.070 align:start position:0% tor so that we don't get that IP address that<00:15:01.620> we<00:15:01.710> can<00:15:01.860> correlate<00:15:02.160> later<00:15:05.000> yeah<00:15:06.000> so<00:15:06.420> also 00:15:07.070 --> 00:15:07.080 align:start position:0% that we can correlate later yeah so also 00:15:07.080 --> 00:15:09.050 align:start position:0% that we can correlate later yeah so also the<00:15:07.560> sapling<00:15:07.980> upgrade<00:15:08.340> to<00:15:08.490> Z<00:15:08.640> cache<00:15:08.820> just 00:15:09.050 --> 00:15:09.060 align:start position:0% the sapling upgrade to Z cache just 00:15:09.060 --> 00:15:10.580 align:start position:0% the sapling upgrade to Z cache just recently<00:15:09.360> happened<00:15:09.570> and<00:15:09.990> that<00:15:10.050> how<00:15:10.200> it<00:15:10.350> helps 00:15:10.580 --> 00:15:10.590 align:start position:0% recently happened and that how it helps 00:15:10.590 --> 00:15:14.240 align:start position:0% recently happened and that how it helps for<00:15:10.830> faster<00:15:12.260> to<00:15:13.260> make<00:15:13.380> a<00:15:13.410> Z<00:15:13.590> cache<00:15:13.770> faster 00:15:14.240 --> 00:15:14.250 align:start position:0% for faster to make a Z cache faster 00:15:14.250 --> 00:15:16.220 align:start position:0% for faster to make a Z cache faster especially<00:15:14.970> as<00:15:15.060> shielded<00:15:15.390> transactions<00:15:15.990> and 00:15:16.220 --> 00:15:16.230 align:start position:0% especially as shielded transactions and 00:15:16.230 --> 00:15:17.870 align:start position:0% especially as shielded transactions and then<00:15:16.830> we<00:15:16.980> hope<00:15:17.160> to<00:15:17.310> get<00:15:17.430> lots<00:15:17.580> of<00:15:17.730> feedback 00:15:17.870 --> 00:15:17.880 align:start position:0% then we hope to get lots of feedback 00:15:17.880 --> 00:15:20.750 align:start position:0% then we hope to get lots of feedback from<00:15:18.270> various<00:15:18.690> communities<00:15:19.580> especially<00:15:20.580> this 00:15:20.750 --> 00:15:20.760 align:start position:0% from various communities especially this 00:15:20.760 --> 00:15:25.130 align:start position:0% from various communities especially this community<00:15:21.210> on<00:15:23.330> to<00:15:24.330> help<00:15:24.510> us<00:15:24.630> iterate<00:15:24.990> and 00:15:25.130 --> 00:15:25.140 align:start position:0% community on to help us iterate and 00:15:25.140 --> 00:15:27.290 align:start position:0% community on to help us iterate and improve<00:15:25.230> this<00:15:25.760> we<00:15:26.760> would<00:15:26.910> like<00:15:27.000> to<00:15:27.150> coordinate 00:15:27.290 --> 00:15:27.300 align:start position:0% improve this we would like to coordinate 00:15:27.300 --> 00:15:28.520 align:start position:0% improve this we would like to coordinate efforts<00:15:27.600> with<00:15:27.960> other<00:15:28.080> people<00:15:28.350> who<00:15:28.500> are 00:15:28.520 --> 00:15:28.530 align:start position:0% efforts with other people who are 00:15:28.530 --> 00:15:30.560 align:start position:0% efforts with other people who are working<00:15:28.770> in<00:15:29.010> the<00:15:29.160> area<00:15:29.430> of<00:15:29.570> subscription 00:15:30.560 --> 00:15:30.570 align:start position:0% working in the area of subscription 00:15:30.570 --> 00:15:32.750 align:start position:0% working in the area of subscription subscription<00:15:31.440> services<00:15:32.310> and<00:15:32.490> management 00:15:32.750 --> 00:15:32.760 align:start position:0% subscription services and management 00:15:32.760 --> 00:15:34.840 align:start position:0% subscription services and management within<00:15:33.390> with<00:15:33.750> cryptocurrency<00:15:34.260> and<00:15:34.560> all 00:15:34.840 --> 00:15:34.850 align:start position:0% within with cryptocurrency and all 00:15:34.850 --> 00:15:36.420 align:start position:0% within with cryptocurrency and all so<00:15:34.940> people<00:15:35.089> who<00:15:35.300> care<00:15:35.600> about<00:15:35.630> privacy 00:15:36.420 --> 00:15:36.430 align:start position:0% so people who care about privacy 00:15:36.430 --> 00:15:38.579 align:start position:0% so people who care about privacy payments<00:15:37.430> and<00:15:37.579> stuff<00:15:37.759> like<00:15:37.880> that 00:15:38.579 --> 00:15:38.589 align:start position:0% payments and stuff like that 00:15:38.589 --> 00:15:41.110 align:start position:0% payments and stuff like that so<00:15:39.589> for<00:15:40.040> example<00:15:40.490> and<00:15:40.610> then<00:15:40.730> we<00:15:40.819> were<00:15:40.940> also 00:15:41.110 --> 00:15:41.120 align:start position:0% so for example and then we were also 00:15:41.120 --> 00:15:42.939 align:start position:0% so for example and then we were also thinking<00:15:41.420> about<00:15:41.569> all<00:15:41.810> kinds<00:15:42.110> of<00:15:42.170> great<00:15:42.920> things 00:15:42.939 --> 00:15:42.949 align:start position:0% thinking about all kinds of great things 00:15:42.949 --> 00:15:44.499 align:start position:0% thinking about all kinds of great things that<00:15:43.310> we<00:15:43.430> could<00:15:43.579> do<00:15:43.670> in<00:15:43.759> the<00:15:43.819> future<00:15:43.850> with<00:15:44.329> this 00:15:44.499 --> 00:15:44.509 align:start position:0% that we could do in the future with this 00:15:44.509 --> 00:15:46.629 align:start position:0% that we could do in the future with this for<00:15:45.230> example<00:15:45.440> we<00:15:45.709> could<00:15:45.860> implement<00:15:46.190> a<00:15:46.459> more 00:15:46.629 --> 00:15:46.639 align:start position:0% for example we could implement a more 00:15:46.639 --> 00:15:48.249 align:start position:0% for example we could implement a more robust<00:15:47.000> communication<00:15:47.720> channel<00:15:48.050> for 00:15:48.249 --> 00:15:48.259 align:start position:0% robust communication channel for 00:15:48.259 --> 00:15:50.230 align:start position:0% robust communication channel for subscription<00:15:48.740> management<00:15:49.000> via<00:15:50.000> the 00:15:50.230 --> 00:15:50.240 align:start position:0% subscription management via the 00:15:50.240 --> 00:15:51.910 align:start position:0% subscription management via the encrypted<00:15:50.779> memo<00:15:51.079> field<00:15:51.319> and<00:15:51.589> Z<00:15:51.709> cash 00:15:51.910 --> 00:15:51.920 align:start position:0% encrypted memo field and Z cash 00:15:51.920 --> 00:15:55.090 align:start position:0% encrypted memo field and Z cash transactions<00:15:52.670> or<00:15:53.149> data<00:15:53.449> can<00:15:53.720> be<00:15:53.750> passed<00:15:54.100> like 00:15:55.090 --> 00:15:55.100 align:start position:0% transactions or data can be passed like 00:15:55.100 --> 00:15:56.499 align:start position:0% transactions or data can be passed like where<00:15:55.279> that<00:15:55.399> invoice<00:15:55.699> data<00:15:55.940> could<00:15:56.149> be<00:15:56.209> passed 00:15:56.499 --> 00:15:56.509 align:start position:0% where that invoice data could be passed 00:15:56.509 --> 00:15:59.319 align:start position:0% where that invoice data could be passed back<00:15:56.779> and<00:15:56.839> forth<00:15:57.190> as<00:15:58.190> a<00:15:58.329> in-band 00:15:59.319 --> 00:15:59.329 align:start position:0% back and forth as a in-band 00:15:59.329 --> 00:16:01.329 align:start position:0% back and forth as a in-band communication<00:16:00.170> channel<00:16:00.500> we're<00:16:00.829> also<00:16:01.009> looking 00:16:01.329 --> 00:16:01.339 align:start position:0% communication channel we're also looking 00:16:01.339 --> 00:16:05.050 align:start position:0% communication channel we're also looking at<00:16:02.259> expanding<00:16:03.259> on<00:16:03.560> features<00:16:04.459> within<00:16:04.639> Tahoe 00:16:05.050 --> 00:16:05.060 align:start position:0% at expanding on features within Tahoe 00:16:05.060 --> 00:16:07.389 align:start position:0% at expanding on features within Tahoe laughs<00:16:05.269> to<00:16:05.660> create<00:16:05.990> a<00:16:06.190> communication<00:16:07.190> channel 00:16:07.389 --> 00:16:07.399 align:start position:0% laughs to create a communication channel 00:16:07.399 --> 00:16:09.999 align:start position:0% laughs to create a communication channel there<00:16:07.730> too<00:16:08.000> and<00:16:08.269> seeing<00:16:08.870> if<00:16:09.079> that<00:16:09.110> would<00:16:09.410> that 00:16:09.999 --> 00:16:10.009 align:start position:0% there too and seeing if that would that 00:16:10.009 --> 00:16:12.400 align:start position:0% there too and seeing if that would that would<00:16:10.100> help<00:16:10.220> and<00:16:10.990> looking<00:16:11.990> at<00:16:12.110> improvements 00:16:12.400 --> 00:16:12.410 align:start position:0% would help and looking at improvements 00:16:12.410 --> 00:16:14.530 align:start position:0% would help and looking at improvements too<00:16:12.860> or<00:16:13.160> integrations<00:16:13.819> with<00:16:14.029> customer 00:16:14.530 --> 00:16:14.540 align:start position:0% too or integrations with customer 00:16:14.540 --> 00:16:16.240 align:start position:0% too or integrations with customer wallets<00:16:14.959> to<00:16:15.319> support<00:16:15.769> this<00:16:15.949> type<00:16:16.190> of 00:16:16.240 --> 00:16:16.250 align:start position:0% wallets to support this type of 00:16:16.250 --> 00:16:21.490 align:start position:0% wallets to support this type of invoicing<00:16:18.160> data<00:16:19.160> and<00:16:19.610> also<00:16:20.509> the<00:16:21.050> advanced 00:16:21.490 --> 00:16:21.500 align:start position:0% invoicing data and also the advanced 00:16:21.500 --> 00:16:23.230 align:start position:0% invoicing data and also the advanced features<00:16:21.860> of<00:16:21.889> things<00:16:22.220> like<00:16:22.399> trial<00:16:22.699> periods 00:16:23.230 --> 00:16:23.240 align:start position:0% features of things like trial periods 00:16:23.240 --> 00:16:25.780 align:start position:0% features of things like trial periods refunds<00:16:23.690> and<00:16:23.990> stuff<00:16:24.199> like<00:16:24.319> that<00:16:24.529> and<00:16:24.829> we'd 00:16:25.780 --> 00:16:25.790 align:start position:0% refunds and stuff like that and we'd 00:16:25.790 --> 00:16:27.519 align:start position:0% refunds and stuff like that and we'd like<00:16:25.970> to<00:16:26.149> see<00:16:26.300> the<00:16:26.480> development<00:16:27.050> of<00:16:27.170> merchants 00:16:27.519 --> 00:16:27.529 align:start position:0% like to see the development of merchants 00:16:27.529 --> 00:16:30.160 align:start position:0% like to see the development of merchants facing<00:16:27.889> payment<00:16:28.279> frameworks<00:16:28.759> to<00:16:29.750> support 00:16:30.160 --> 00:16:30.170 align:start position:0% facing payment frameworks to support 00:16:30.170 --> 00:16:31.960 align:start position:0% facing payment frameworks to support subscriptions<00:16:30.889> and<00:16:31.190> management<00:16:31.730> of<00:16:31.850> those 00:16:31.960 --> 00:16:31.970 align:start position:0% subscriptions and management of those 00:16:31.970 --> 00:16:34.360 align:start position:0% subscriptions and management of those subscriptions<00:16:32.449> for<00:16:32.899> companies<00:16:33.829> that<00:16:33.860> want<00:16:34.190> to 00:16:34.360 --> 00:16:34.370 align:start position:0% subscriptions for companies that want to 00:16:34.370 --> 00:16:36.600 align:start position:0% subscriptions for companies that want to utilize<00:16:34.579> cryptocurrency<00:16:35.300> payments<00:16:35.959> and 00:16:36.600 --> 00:16:36.610 align:start position:0% utilize cryptocurrency payments and 00:16:36.610 --> 00:16:38.620 align:start position:0% utilize cryptocurrency payments and lastly<00:16:37.610> we<00:16:37.730> just<00:16:37.759> hope<00:16:38.060> that<00:16:38.089> this<00:16:38.360> inspires 00:16:38.620 --> 00:16:38.630 align:start position:0% lastly we just hope that this inspires 00:16:38.630 --> 00:16:41.410 align:start position:0% lastly we just hope that this inspires other<00:16:39.139> subscription<00:16:39.740> services<00:16:40.250> to<00:16:41.180> use 00:16:41.410 --> 00:16:41.420 align:start position:0% other subscription services to use 00:16:41.420 --> 00:16:43.059 align:start position:0% other subscription services to use cryptocurrency<00:16:42.079> in<00:16:42.470> a<00:16:42.560> privacy-preserving 00:16:43.059 --> 00:16:43.069 align:start position:0% cryptocurrency in a privacy-preserving 00:16:43.069 --> 00:16:48.519 align:start position:0% cryptocurrency in a privacy-preserving way<00:16:43.990> while<00:16:44.990> experimenting<00:16:45.620> with<00:16:45.980> tech<00:16:47.529> we 00:16:48.519 --> 00:16:48.529 align:start position:0% way while experimenting with tech we 00:16:48.529 --> 00:16:50.110 align:start position:0% way while experimenting with tech we understand<00:16:49.040> that<00:16:49.189> maybe<00:16:49.339> privacy<00:16:49.910> can<00:16:50.060> be 00:16:50.110 --> 00:16:50.120 align:start position:0% understand that maybe privacy can be 00:16:50.120 --> 00:16:51.579 align:start position:0% understand that maybe privacy can be like<00:16:50.389> an<00:16:50.540> afterthought<00:16:51.110> when<00:16:51.290> you're<00:16:51.410> doing 00:16:51.579 --> 00:16:51.589 align:start position:0% like an afterthought when you're doing 00:16:51.589 --> 00:16:54.220 align:start position:0% like an afterthought when you're doing experimentation<00:16:52.310> but<00:16:53.029> if<00:16:53.180> we<00:16:53.329> do<00:16:53.540> want<00:16:53.750> to<00:16:53.899> see 00:16:54.220 --> 00:16:54.230 align:start position:0% experimentation but if we do want to see 00:16:54.230 --> 00:16:57.069 align:start position:0% experimentation but if we do want to see this<00:16:54.610> because<00:16:55.610> that<00:16:56.300> in<00:16:56.449> order<00:16:56.689> for<00:16:56.720> this<00:16:56.959> to 00:16:57.069 --> 00:16:57.079 align:start position:0% this because that in order for this to 00:16:57.079 --> 00:16:58.800 align:start position:0% this because that in order for this to become<00:16:57.230> mass<00:16:58.040> adoption 00:16:58.800 --> 00:16:58.810 align:start position:0% become mass adoption 00:16:58.810 --> 00:17:00.790 align:start position:0% become mass adoption especially<00:16:59.810> for<00:16:59.930> cryptocurrency<00:17:00.380> for 00:17:00.790 --> 00:17:00.800 align:start position:0% especially for cryptocurrency for 00:17:00.800 --> 00:17:02.559 align:start position:0% especially for cryptocurrency for subscription<00:17:01.279> payments<00:17:01.730> I<00:17:01.880> think<00:17:02.240> that<00:17:02.449> there 00:17:02.559 --> 00:17:02.569 align:start position:0% subscription payments I think that there 00:17:02.569 --> 00:17:04.419 align:start position:0% subscription payments I think that there needs<00:17:02.810> to<00:17:02.899> be<00:17:02.990> some<00:17:03.259> privacy<00:17:03.740> in<00:17:04.010> those 00:17:04.419 --> 00:17:04.429 align:start position:0% needs to be some privacy in those 00:17:04.429 --> 00:17:06.250 align:start position:0% needs to be some privacy in those payments<00:17:04.880> otherwise<00:17:05.240> the<00:17:05.510> world<00:17:05.630> can<00:17:06.049> see 00:17:06.250 --> 00:17:06.260 align:start position:0% payments otherwise the world can see 00:17:06.260 --> 00:17:07.720 align:start position:0% payments otherwise the world can see everything<00:17:06.770> that<00:17:06.860> you're<00:17:06.980> subscribing<00:17:07.459> to 00:17:07.720 --> 00:17:07.730 align:start position:0% everything that you're subscribing to 00:17:07.730 --> 00:17:10.710 align:start position:0% everything that you're subscribing to and<00:17:07.939> that's<00:17:08.539> not<00:17:08.720> so<00:17:08.929> cool<00:17:09.169> other<00:17:10.130> and<00:17:10.280> also 00:17:10.710 --> 00:17:10.720 align:start position:0% and that's not so cool other and also 00:17:10.720 --> 00:17:13.240 align:start position:0% and that's not so cool other and also even<00:17:11.720> if<00:17:11.990> it's<00:17:12.199> not<00:17:12.319> so<00:17:12.500> obvious<00:17:12.530> what<00:17:13.130> that 00:17:13.240 --> 00:17:13.250 align:start position:0% even if it's not so obvious what that 00:17:13.250 --> 00:17:15.520 align:start position:0% even if it's not so obvious what that data<00:17:13.429> is<00:17:13.579> if<00:17:14.150> it's<00:17:14.419> just<00:17:14.720> like<00:17:14.870> metadata<00:17:15.350> or 00:17:15.520 --> 00:17:15.530 align:start position:0% data is if it's just like metadata or 00:17:15.530 --> 00:17:18.429 align:start position:0% data is if it's just like metadata or something<00:17:15.890> with<00:17:16.579> big<00:17:16.789> data<00:17:17.030> analytic<00:17:17.870> capable 00:17:18.429 --> 00:17:18.439 align:start position:0% something with big data analytic capable 00:17:18.439 --> 00:17:20.500 align:start position:0% something with big data analytic capable it<00:17:18.799> of<00:17:18.890> capable<00:17:19.309> capabilities<00:17:20.150> that<00:17:20.270> are<00:17:20.419> out 00:17:20.500 --> 00:17:20.510 align:start position:0% it of capable capabilities that are out 00:17:20.510 --> 00:17:22.120 align:start position:0% it of capable capabilities that are out there<00:17:20.689> right<00:17:20.839> now<00:17:20.900> people<00:17:21.409> could<00:17:21.679> start<00:17:21.980> to 00:17:22.120 --> 00:17:22.130 align:start position:0% there right now people could start to 00:17:22.130 --> 00:17:24.460 align:start position:0% there right now people could start to easily<00:17:22.610> correlate<00:17:23.120> that<00:17:23.150> data<00:17:23.510> to<00:17:23.870> other<00:17:24.110> data 00:17:24.460 --> 00:17:24.470 align:start position:0% easily correlate that data to other data 00:17:24.470 --> 00:17:26.439 align:start position:0% easily correlate that data to other data that's<00:17:24.559> out<00:17:24.919> there<00:17:25.130> and<00:17:25.339> figure<00:17:26.000> out<00:17:26.059> more 00:17:26.439 --> 00:17:26.449 align:start position:0% that's out there and figure out more 00:17:26.449 --> 00:17:29.080 align:start position:0% that's out there and figure out more about<00:17:26.689> you<00:17:26.839> too<00:17:27.459> so<00:17:28.459> any<00:17:28.789> current 00:17:29.080 --> 00:17:29.090 align:start position:0% about you too so any current 00:17:29.090 --> 00:17:31.330 align:start position:0% about you too so any current pseudonymity<00:17:29.750> pseudo<00:17:30.350> anonymity<00:17:30.740> that<00:17:30.950> we 00:17:31.330 --> 00:17:31.340 align:start position:0% pseudonymity pseudo anonymity that we 00:17:31.340 --> 00:17:33.159 align:start position:0% pseudonymity pseudo anonymity that we have<00:17:31.490> right<00:17:31.669> now<00:17:31.700> will<00:17:32.179> be<00:17:32.270> quickly<00:17:32.480> lost<00:17:32.780> and 00:17:33.159 --> 00:17:33.169 align:start position:0% have right now will be quickly lost and 00:17:33.169 --> 00:17:35.980 align:start position:0% have right now will be quickly lost and a<00:17:33.740> major<00:17:33.919> factor<00:17:34.309> in<00:17:34.659> decentralization<00:17:35.659> is 00:17:35.980 --> 00:17:35.990 align:start position:0% a major factor in decentralization is 00:17:35.990 --> 00:17:37.899 align:start position:0% a major factor in decentralization is removing<00:17:36.530> such<00:17:37.159> power<00:17:37.400> from<00:17:37.760> big 00:17:37.899 --> 00:17:37.909 align:start position:0% removing such power from big 00:17:37.909 --> 00:17:39.820 align:start position:0% removing such power from big corporations<00:17:38.360> Central's<00:17:39.169> central 00:17:39.820 --> 00:17:39.830 align:start position:0% corporations Central's central 00:17:39.830 --> 00:17:42.130 align:start position:0% corporations Central's central organizations<00:17:40.490> and<00:17:40.789> giving<00:17:41.419> it<00:17:41.570> to<00:17:41.600> us<00:17:41.990> as 00:17:42.130 --> 00:17:42.140 align:start position:0% organizations and giving it to us as 00:17:42.140 --> 00:17:43.930 align:start position:0% organizations and giving it to us as individuals<00:17:42.770> to<00:17:42.980> manage<00:17:43.070> our<00:17:43.400> subscriptions 00:17:43.930 --> 00:17:43.940 align:start position:0% individuals to manage our subscriptions 00:17:43.940 --> 00:17:46.899 align:start position:0% individuals to manage our subscriptions ourselves<00:17:44.360> so<00:17:45.080> usability<00:17:45.890> will<00:17:46.040> be<00:17:46.190> very<00:17:46.640> key 00:17:46.899 --> 00:17:46.909 align:start position:0% ourselves so usability will be very key 00:17:46.909 --> 00:17:48.760 align:start position:0% ourselves so usability will be very key in<00:17:47.120> this<00:17:47.270> too<00:17:47.510> so<00:17:48.110> I<00:17:48.320> look 00:17:48.760 --> 00:17:48.770 align:start position:0% in this too so I look 00:17:48.770 --> 00:17:51.370 align:start position:0% in this too so I look forward<00:17:48.980> to<00:17:49.240> hearing<00:17:50.240> from<00:17:50.510> people<00:17:50.840> about 00:17:51.370 --> 00:17:51.380 align:start position:0% forward to hearing from people about 00:17:51.380 --> 00:17:52.780 align:start position:0% forward to hearing from people about these<00:17:51.770> efforts<00:17:51.950> and<00:17:52.250> how<00:17:52.370> we<00:17:52.430> can<00:17:52.640> move 00:17:52.780 --> 00:17:52.790 align:start position:0% these efforts and how we can move 00:17:52.790 --> 00:17:54.970 align:start position:0% these efforts and how we can move forward<00:17:53.590> thank<00:17:54.590> you 00:17:54.970 --> 00:17:54.980 align:start position:0% forward thank you 00:17:54.980 --> 00:18:01.330 align:start position:0% forward thank you thanks<00:17:59.200> yeah<00:18:00.200> we<00:18:00.350> have<00:18:00.500> about<00:18:00.710> four<00:18:01.010> minutes 00:18:01.330 --> 00:18:01.340 align:start position:0% thanks yeah we have about four minutes 00:18:01.340 --> 00:18:05.140 align:start position:0% thanks yeah we have about four minutes for<00:18:01.550> questions<00:18:01.940> does<00:18:02.210> anyone<00:18:02.480> have<00:18:02.630> any<00:18:03.430> hi<00:18:04.430> is 00:18:05.140 --> 00:18:05.150 align:start position:0% for questions does anyone have any hi is 00:18:05.150 --> 00:18:09.280 align:start position:0% for questions does anyone have any hi is there<00:18:05.360> any<00:18:06.700> anything<00:18:07.700> that's<00:18:08.270> in<00:18:08.810> that's 00:18:09.280 --> 00:18:09.290 align:start position:0% there any anything that's in that's 00:18:09.290 --> 00:18:12.340 align:start position:0% there any anything that's in that's stored<00:18:09.920> in<00:18:10.040> the<00:18:10.250> data<00:18:10.760> that<00:18:10.910> allows<00:18:11.600> me<00:18:11.840> to<00:18:12.050> if 00:18:12.340 --> 00:18:12.350 align:start position:0% stored in the data that allows me to if 00:18:12.350 --> 00:18:14.320 align:start position:0% stored in the data that allows me to if I<00:18:12.530> was<00:18:12.620> a<00:18:12.680> user<00:18:12.860> to<00:18:13.160> get<00:18:13.370> any<00:18:13.670> kind<00:18:13.850> of<00:18:13.940> proof 00:18:14.320 --> 00:18:14.330 align:start position:0% I was a user to get any kind of proof 00:18:14.330 --> 00:18:16.720 align:start position:0% I was a user to get any kind of proof that<00:18:14.360> says<00:18:14.900> my<00:18:15.410> data<00:18:15.650> is<00:18:15.830> being<00:18:16.040> stored<00:18:16.250> and 00:18:16.720 --> 00:18:16.730 align:start position:0% that says my data is being stored and 00:18:16.730 --> 00:18:19.630 align:start position:0% that says my data is being stored and and<00:18:17.360> is<00:18:17.450> retrievable<00:18:18.050> if<00:18:18.830> I'm<00:18:19.010> subscribed<00:18:19.490> to 00:18:19.630 --> 00:18:19.640 align:start position:0% and is retrievable if I'm subscribed to 00:18:19.640 --> 00:18:22.120 align:start position:0% and is retrievable if I'm subscribed to a<00:18:19.670> service<00:18:20.000> like<00:18:20.150> this<00:18:20.380> yeah<00:18:21.380> so<00:18:21.590> in<00:18:21.770> Tahoe 00:18:22.120 --> 00:18:22.130 align:start position:0% a service like this yeah so in Tahoe 00:18:22.130 --> 00:18:24.190 align:start position:0% a service like this yeah so in Tahoe laughs<00:18:22.460> if<00:18:22.850> there's<00:18:23.090> proof<00:18:23.390> of<00:18:23.600> storage<00:18:24.050> I 00:18:24.190 --> 00:18:24.200 align:start position:0% laughs if there's proof of storage I 00:18:24.200 --> 00:18:26.530 align:start position:0% laughs if there's proof of storage I don't<00:18:24.410> think<00:18:24.650> so<00:18:24.830> right<00:18:24.860> now<00:18:25.220> I<00:18:26.000> think<00:18:26.360> that 00:18:26.530 --> 00:18:26.540 align:start position:0% don't think so right now I think that 00:18:26.540 --> 00:18:28.840 align:start position:0% don't think so right now I think that there's<00:18:27.100> yeah<00:18:28.100> there's<00:18:28.130> maybe<00:18:28.460> some<00:18:28.700> other 00:18:28.840 --> 00:18:28.850 align:start position:0% there's yeah there's maybe some other 00:18:28.850 --> 00:18:30.310 align:start position:0% there's yeah there's maybe some other ways<00:18:28.970> to<00:18:29.090> do<00:18:29.180> it<00:18:29.210> but<00:18:29.300> not<00:18:29.510> not<00:18:29.840> in<00:18:29.990> the<00:18:30.110> sense 00:18:30.310 --> 00:18:30.320 align:start position:0% ways to do it but not not in the sense 00:18:30.320 --> 00:18:31.750 align:start position:0% ways to do it but not not in the sense that<00:18:30.410> there<00:18:30.770> yeah 00:18:31.750 --> 00:18:31.760 align:start position:0% that there yeah 00:18:31.760 --> 00:18:33.100 align:start position:0% that there yeah not<00:18:32.120> in<00:18:32.210> the<00:18:32.270> sense<00:18:32.360> of<00:18:32.480> the<00:18:32.570> other<00:18:32.720> projects 00:18:33.100 --> 00:18:33.110 align:start position:0% not in the sense of the other projects 00:18:33.110 --> 00:18:46.120 align:start position:0% not in the sense of the other projects that<00:18:33.200> have<00:18:33.350> that<00:18:33.500> right<00:18:33.590> now<00:18:40.660> which<00:18:44.770> I'm<00:18:45.770> sorry 00:18:46.120 --> 00:18:46.130 align:start position:0% that have that right now which I'm sorry 00:18:46.130 --> 00:18:52.180 align:start position:0% that have that right now which I'm sorry Oh<00:18:49.810> merchant<00:18:50.810> networks<00:18:51.140> so<00:18:51.920> we're<00:18:52.070> the 00:18:52.180 --> 00:18:52.190 align:start position:0% Oh merchant networks so we're the 00:18:52.190 --> 00:18:54.310 align:start position:0% Oh merchant networks so we're the merchants<00:18:52.550> right<00:18:52.730> now<00:18:52.940> in<00:18:53.240> this<00:18:53.690> case<00:18:53.960> in<00:18:54.230> this 00:18:54.310 --> 00:18:54.320 align:start position:0% merchants right now in this case in this 00:18:54.320 --> 00:18:55.930 align:start position:0% merchants right now in this case in this use<00:18:54.500> case<00:18:54.530> where<00:18:54.950> the<00:18:55.070> merchants<00:18:55.400> and<00:18:55.550> this<00:18:55.790> is 00:18:55.930 --> 00:18:55.940 align:start position:0% use case where the merchants and this is 00:18:55.940 --> 00:18:57.220 align:start position:0% use case where the merchants and this is just<00:18:56.150> how<00:18:56.300> we're<00:18:56.510> going<00:18:56.600> to<00:18:56.660> handle<00:18:56.930> it<00:18:57.050> as<00:18:57.200> a 00:18:57.220 --> 00:18:57.230 align:start position:0% just how we're going to handle it as a 00:18:57.230 --> 00:18:59.890 align:start position:0% just how we're going to handle it as a merchant<00:18:57.520> in<00:18:58.520> terms<00:18:58.850> of<00:18:59.120> integrating<00:18:59.870> with 00:18:59.890 --> 00:18:59.900 align:start position:0% merchant in terms of integrating with 00:18:59.900 --> 00:19:01.360 align:start position:0% merchant in terms of integrating with other<00:19:00.110> merchant<00:19:00.560> networks<00:19:00.860> that<00:19:01.070> would<00:19:01.220> be 00:19:01.360 --> 00:19:01.370 align:start position:0% other merchant networks that would be 00:19:01.370 --> 00:19:02.590 align:start position:0% other merchant networks that would be something<00:19:01.670> that<00:19:01.790> we<00:19:01.970> could<00:19:02.060> talk<00:19:02.240> about<00:19:02.480> is 00:19:02.590 --> 00:19:02.600 align:start position:0% something that we could talk about is 00:19:02.600 --> 00:19:12.730 align:start position:0% something that we could talk about is like<00:19:02.750> a<00:19:02.780> future<00:19:03.260> possibility<00:19:04.100> and<00:19:11.560> you<00:19:12.560> mean 00:19:12.730 --> 00:19:12.740 align:start position:0% like a future possibility and you mean 00:19:12.740 --> 00:19:14.920 align:start position:0% like a future possibility and you mean other<00:19:12.920> companies<00:19:13.460> other<00:19:13.760> merchants<00:19:14.330> like 00:19:14.920 --> 00:19:14.930 align:start position:0% other companies other merchants like 00:19:14.930 --> 00:19:17.730 align:start position:0% other companies other merchants like Netflix<00:19:15.770> or<00:19:16.040> something<00:19:16.910> like<00:19:17.030> that<00:19:17.090> thank<00:19:17.600> you 00:19:17.730 --> 00:19:17.740 align:start position:0% Netflix or something like that thank you 00:19:17.740 --> 00:19:20.590 align:start position:0% Netflix or something like that thank you like<00:19:18.740> any<00:19:18.950> of<00:19:19.070> this<00:19:19.340> subscription<00:19:19.880> providers 00:19:20.590 --> 00:19:20.600 align:start position:0% like any of this subscription providers 00:19:20.600 --> 00:19:24.010 align:start position:0% like any of this subscription providers have<00:19:20.900> they<00:19:21.310> shown<00:19:22.310> interest<00:19:22.790> into<00:19:23.270> using<00:19:23.720> this 00:19:24.010 --> 00:19:24.020 align:start position:0% have they shown interest into using this 00:19:24.020 --> 00:19:28.660 align:start position:0% have they shown interest into using this kind<00:19:24.350> of<00:19:26.110> like<00:19:27.110> anonymous<00:19:27.590> payments<00:19:28.400> into 00:19:28.660 --> 00:19:28.670 align:start position:0% kind of like anonymous payments into 00:19:28.670 --> 00:19:33.490 align:start position:0% kind of like anonymous payments into their<00:19:29.020> service<00:19:31.000> well<00:19:32.000> yeah<00:19:32.270> so<00:19:32.510> other<00:19:32.720> so 00:19:33.490 --> 00:19:33.500 align:start position:0% their service well yeah so other so 00:19:33.500 --> 00:19:35.320 align:start position:0% their service well yeah so other so other<00:19:33.680> companies<00:19:34.190> have<00:19:34.430> said<00:19:34.820> that<00:19:34.970> they<00:19:35.090> want 00:19:35.320 --> 00:19:35.330 align:start position:0% other companies have said that they want 00:19:35.330 --> 00:19:37.210 align:start position:0% other companies have said that they want to<00:19:35.540> do<00:19:35.780> subscription<00:19:36.560> payments<00:19:37.070> with 00:19:37.210 --> 00:19:37.220 align:start position:0% to do subscription payments with 00:19:37.220 --> 00:19:40.060 align:start position:0% to do subscription payments with cryptocurrency<00:19:38.200> so<00:19:39.200> like<00:19:39.650> I<00:19:39.740> said<00:19:39.800> you<00:19:39.950> could 00:19:40.060 --> 00:19:40.070 align:start position:0% cryptocurrency so like I said you could 00:19:40.070 --> 00:19:42.550 align:start position:0% cryptocurrency so like I said you could do<00:19:40.300> right<00:19:41.300> now<00:19:41.450> subscription<00:19:41.870> payments<00:19:42.440> right 00:19:42.550 --> 00:19:42.560 align:start position:0% do right now subscription payments right 00:19:42.560 --> 00:19:44.020 align:start position:0% do right now subscription payments right now<00:19:42.710> we're<00:19:42.890> kind<00:19:43.130> of<00:19:43.220> difficult<00:19:43.670> there's<00:19:43.880> some 00:19:44.020 --> 00:19:44.030 align:start position:0% now we're kind of difficult there's some 00:19:44.030 --> 00:19:46.180 align:start position:0% now we're kind of difficult there's some workarounds<00:19:44.600> that<00:19:44.660> we<00:19:44.840> have<00:19:45.020> but<00:19:45.380> we<00:19:45.920> need<00:19:46.070> to 00:19:46.180 --> 00:19:46.190 align:start position:0% workarounds that we have but we need to 00:19:46.190 --> 00:19:47.200 align:start position:0% workarounds that we have but we need to make<00:19:46.340> those<00:19:46.460> easier<00:19:46.880> to<00:19:47.000> use<00:19:47.180> for 00:19:47.200 --> 00:19:47.210 align:start position:0% make those easier to use for 00:19:47.210 --> 00:19:50.170 align:start position:0% make those easier to use for cryptocurrency<00:19:47.870> in<00:19:48.230> general<00:19:48.620> and<00:19:48.860> then<00:19:49.400> when 00:19:50.170 --> 00:19:50.180 align:start position:0% cryptocurrency in general and then when 00:19:50.180 --> 00:19:52.090 align:start position:0% cryptocurrency in general and then when it<00:19:50.300> comes<00:19:50.510> to<00:19:50.750> the<00:19:50.870> angle<00:19:51.140> of<00:19:51.290> privacy<00:19:51.890> I<00:19:51.920> think 00:19:52.090 --> 00:19:52.100 align:start position:0% it comes to the angle of privacy I think 00:19:52.100 --> 00:19:54.910 align:start position:0% it comes to the angle of privacy I think that<00:19:52.550> well<00:19:52.910> it<00:19:53.240> might<00:19:53.420> be<00:19:53.570> okay<00:19:53.870> to<00:19:53.900> not<00:19:54.200> be<00:19:54.680> so 00:19:54.910 --> 00:19:54.920 align:start position:0% that well it might be okay to not be so 00:19:54.920 --> 00:19:56.530 align:start position:0% that well it might be okay to not be so worried<00:19:55.280> about<00:19:55.370> the<00:19:55.640> personal<00:19:56.060> data<00:19:56.240> that's 00:19:56.530 --> 00:19:56.540 align:start position:0% worried about the personal data that's 00:19:56.540 --> 00:19:58.420 align:start position:0% worried about the personal data that's being<00:19:56.690> leaked<00:19:56.960> in<00:19:57.530> the<00:19:57.590> experimental<00:19:58.190> phase 00:19:58.420 --> 00:19:58.430 align:start position:0% being leaked in the experimental phase 00:19:58.430 --> 00:20:01.590 align:start position:0% being leaked in the experimental phase in<00:19:58.820> the<00:19:58.910> short<00:19:59.120> term<00:19:59.300> that<00:19:59.900> if<00:20:00.260> we<00:20:00.500> want<00:20:00.680> to<00:20:00.740> see 00:20:01.590 --> 00:20:01.600 align:start position:0% in the short term that if we want to see 00:20:01.600 --> 00:20:03.090 align:start position:0% in the short term that if we want to see in<00:20:01.809> the<00:20:01.960> long<00:20:02.140> term<00:20:02.320> if<00:20:02.470> we<00:20:02.500> want<00:20:02.740> to<00:20:02.770> see<00:20:02.890> mass 00:20:03.090 --> 00:20:03.100 align:start position:0% in the long term if we want to see mass 00:20:03.100 --> 00:20:04.710 align:start position:0% in the long term if we want to see mass adoption<00:20:03.340> I<00:20:03.820> think<00:20:04.000> we<00:20:04.120> need<00:20:04.299> to<00:20:04.420> have<00:20:04.540> some 00:20:04.710 --> 00:20:04.720 align:start position:0% adoption I think we need to have some 00:20:04.720 --> 00:20:07.110 align:start position:0% adoption I think we need to have some privacy<00:20:05.049> preserving<00:20:05.860> features<00:20:06.610> in<00:20:06.940> these 00:20:07.110 --> 00:20:07.120 align:start position:0% privacy preserving features in these 00:20:07.120 --> 00:20:10.260 align:start position:0% privacy preserving features in these subscription<00:20:07.750> management<00:20:07.870> services<00:20:09.270> whether 00:20:10.260 --> 00:20:10.270 align:start position:0% subscription management services whether 00:20:10.270 --> 00:20:12.289 align:start position:0% subscription management services whether or<00:20:10.420> not<00:20:10.480> that's<00:20:10.660> true<00:20:10.750> anonymity<00:20:11.380> that's<00:20:11.710> a 00:20:12.289 --> 00:20:12.299 align:start position:0% or not that's true anonymity that's a 00:20:12.299 --> 00:20:16.080 align:start position:0% or not that's true anonymity that's a difficult<00:20:13.299> thing<00:20:13.360> but<00:20:14.170> um<00:20:14.549> yeah<00:20:15.549> I<00:20:15.580> just<00:20:15.790> I 00:20:16.080 --> 00:20:16.090 align:start position:0% difficult thing but um yeah I just I 00:20:16.090 --> 00:20:17.789 align:start position:0% difficult thing but um yeah I just I think<00:20:16.150> that<00:20:16.330> it<00:20:16.750> I<00:20:17.020> think<00:20:17.260> that<00:20:17.440> most<00:20:17.679> people 00:20:17.789 --> 00:20:17.799 align:start position:0% think that it I think that most people 00:20:17.799 --> 00:20:20.549 align:start position:0% think that it I think that most people out<00:20:18.190> there<00:20:18.240> just<00:20:19.240> will<00:20:19.510> not<00:20:19.690> want<00:20:19.990> to<00:20:20.260> do 00:20:20.549 --> 00:20:20.559 align:start position:0% out there just will not want to do 00:20:20.559 --> 00:20:22.260 align:start position:0% out there just will not want to do subscriptions<00:20:21.250> if<00:20:21.429> they<00:20:21.580> think<00:20:21.820> everybody 00:20:22.260 --> 00:20:22.270 align:start position:0% subscriptions if they think everybody 00:20:22.270 --> 00:20:24.120 align:start position:0% subscriptions if they think everybody else<00:20:22.450> in<00:20:22.630> the<00:20:22.750> world<00:20:22.780> knows<00:20:23.710> what<00:20:23.980> they're 00:20:24.120 --> 00:20:24.130 align:start position:0% else in the world knows what they're 00:20:24.130 --> 00:20:26.130 align:start position:0% else in the world knows what they're doing<00:20:24.160> what<00:20:25.090> they're<00:20:25.240> subscribed<00:20:25.480> into<00:20:25.900> that 00:20:26.130 --> 00:20:26.140 align:start position:0% doing what they're subscribed into that 00:20:26.140 --> 00:20:27.600 align:start position:0% doing what they're subscribed into that I<00:20:26.170> think<00:20:26.410> that<00:20:26.530> we<00:20:26.770> would<00:20:26.950> want<00:20:27.130> to<00:20:27.190> keep<00:20:27.490> that 00:20:27.600 --> 00:20:27.610 align:start position:0% I think that we would want to keep that 00:20:27.610 --> 00:20:29.370 align:start position:0% I think that we would want to keep that information<00:20:27.820> to<00:20:28.210> ourselves<00:20:28.809> and<00:20:28.990> only<00:20:29.049> share 00:20:29.370 --> 00:20:29.380 align:start position:0% information to ourselves and only share 00:20:29.380 --> 00:20:34.640 align:start position:0% information to ourselves and only share it<00:20:29.470> with<00:20:29.590> who<00:20:29.740> we<00:20:29.860> want<00:20:30.040> to<00:20:30.130> share<00:20:30.309> it<00:20:30.370> with 00:20:34.640 --> 00:20:34.650 align:start position:0% 00:20:34.650 --> 00:20:36.840 align:start position:0% have<00:20:35.650> you<00:20:35.799> had<00:20:35.919> a<00:20:35.950> chance<00:20:36.190> to<00:20:36.309> connect<00:20:36.700> with 00:20:36.840 --> 00:20:36.850 align:start position:0% have you had a chance to connect with 00:20:36.850 --> 00:20:41.250 align:start position:0% have you had a chance to connect with Kevin<00:20:37.210> from<00:20:37.600> who's<00:20:38.020> doing<00:20:38.380> VIP<00:20:39.419> 13:37<00:20:40.419> I<00:20:40.600> just 00:20:41.250 --> 00:20:41.260 align:start position:0% Kevin from who's doing VIP 13:37 I just 00:20:41.260 --> 00:20:42.960 align:start position:0% Kevin from who's doing VIP 13:37 I just talked<00:20:41.530> to<00:20:41.650> him<00:20:41.830> quickly<00:20:42.070> about<00:20:42.400> this<00:20:42.669> last 00:20:42.960 --> 00:20:42.970 align:start position:0% talked to him quickly about this last 00:20:42.970 --> 00:20:45.690 align:start position:0% talked to him quickly about this last night<00:20:43.240> and<00:20:43.780> yeah<00:20:44.740> well<00:20:45.100> we're<00:20:45.220> gonna<00:20:45.280> connect 00:20:45.690 --> 00:20:45.700 align:start position:0% night and yeah well we're gonna connect 00:20:45.700 --> 00:20:46.890 align:start position:0% night and yeah well we're gonna connect some<00:20:45.910> more<00:20:46.059> and<00:20:46.179> talk<00:20:46.360> about<00:20:46.510> it<00:20:46.720> some<00:20:46.870> more 00:20:46.890 --> 00:20:46.900 align:start position:0% some more and talk about it some more 00:20:46.900 --> 00:20:48.450 align:start position:0% some more and talk about it some more I'd<00:20:47.110> love<00:20:47.290> to<00:20:47.470> see<00:20:47.620> us<00:20:47.710> like<00:20:47.950> coordinate 00:20:48.450 --> 00:20:48.460 align:start position:0% I'd love to see us like coordinate 00:20:48.460 --> 00:20:50.640 align:start position:0% I'd love to see us like coordinate efforts<00:20:48.610> on<00:20:49.000> that<00:20:49.210> oh<00:20:49.419> I<00:20:49.660> see<00:20:49.960> you're<00:20:50.110> here<00:20:50.350> too 00:20:50.640 --> 00:20:50.650 align:start position:0% efforts on that oh I see you're here too 00:20:50.650 --> 00:20:53.130 align:start position:0% efforts on that oh I see you're here too awesome<00:20:51.210> yeah<00:20:52.210> I'd<00:20:52.450> want<00:20:52.480> us<00:20:52.780> to<00:20:52.929> coordinate 00:20:53.130 --> 00:20:53.140 align:start position:0% awesome yeah I'd want us to coordinate 00:20:53.140 --> 00:20:55.049 align:start position:0% awesome yeah I'd want us to coordinate efforts<00:20:53.500> on<00:20:53.860> that<00:20:54.010> because<00:20:54.100> I<00:20:54.190> think<00:20:54.580> that<00:20:54.790> it 00:20:55.049 --> 00:20:55.059 align:start position:0% efforts on that because I think that it 00:20:55.059 --> 00:20:57.419 align:start position:0% efforts on that because I think that it would<00:20:55.270> be<00:20:55.419> really<00:20:55.660> good<00:20:55.809> to<00:20:55.990> talk<00:20:56.140> to<00:20:56.429> make 00:20:57.419 --> 00:20:57.429 align:start position:0% would be really good to talk to make 00:20:57.429 --> 00:20:59.549 align:start position:0% would be really good to talk to make sure<00:20:57.640> that<00:20:57.820> like<00:20:58.059> you<00:20:58.660> know<00:20:58.780> we're<00:20:59.020> being 00:20:59.549 --> 00:20:59.559 align:start position:0% sure that like you know we're being 00:20:59.559 --> 00:21:01.440 align:start position:0% sure that like you know we're being consistent<00:21:00.220> on<00:21:00.309> how<00:21:00.460> we<00:21:00.520> define<00:21:00.790> things<00:21:01.179> like 00:21:01.440 --> 00:21:01.450 align:start position:0% consistent on how we define things like 00:21:01.450 --> 00:21:03.480 align:start position:0% consistent on how we define things like invoices<00:21:02.080> structure<00:21:02.650> and<00:21:02.890> stuff<00:21:03.070> like<00:21:03.250> that 00:21:03.480 --> 00:21:03.490 align:start position:0% invoices structure and stuff like that 00:21:03.490 --> 00:21:06.810 align:start position:0% invoices structure and stuff like that and<00:21:04.140> yeah<00:21:05.140> see<00:21:05.559> if<00:21:05.650> we<00:21:05.860> can<00:21:06.010> help<00:21:06.250> with<00:21:06.429> privacy 00:21:06.810 --> 00:21:06.820 align:start position:0% and yeah see if we can help with privacy 00:21:06.820 --> 00:21:10.080 align:start position:0% and yeah see if we can help with privacy on<00:21:07.030> the<00:21:07.120> etherium<00:21:07.510> Network<00:21:07.750> -<00:21:08.970> any<00:21:09.970> other 00:21:10.080 --> 00:21:10.090 align:start position:0% on the etherium Network - any other 00:21:10.090 --> 00:21:16.260 align:start position:0% on the etherium Network - any other questions<00:21:13.919> so<00:21:14.919> one<00:21:15.100> question<00:21:15.280> uh<00:21:15.460> you<00:21:16.030> say<00:21:16.240> you 00:21:16.260 --> 00:21:16.270 align:start position:0% questions so one question uh you say you 00:21:16.270 --> 00:21:19.710 align:start position:0% questions so one question uh you say you comply<00:21:16.870> with<00:21:17.020> gdpr<00:21:17.410> but<00:21:18.400> how<00:21:18.549> about<00:21:18.669> AML<00:21:19.270> anti 00:21:19.710 --> 00:21:19.720 align:start position:0% comply with gdpr but how about AML anti 00:21:19.720 --> 00:21:20.370 align:start position:0% comply with gdpr but how about AML anti money<00:21:19.870> laundering 00:21:20.370 --> 00:21:20.380 align:start position:0% money laundering 00:21:20.380 --> 00:21:23.840 align:start position:0% money laundering you're<00:21:20.799> opposed<00:21:21.190> to<00:21:21.660> monitor<00:21:22.660> transactions 00:21:23.840 --> 00:21:23.850 align:start position:0% you're opposed to monitor transactions 00:21:23.850 --> 00:21:26.909 align:start position:0% you're opposed to monitor transactions if<00:21:24.850> it's<00:21:25.150> recurring<00:21:25.809> payments<00:21:26.350> if<00:21:26.530> it's<00:21:26.679> over 00:21:26.909 --> 00:21:26.919 align:start position:0% if it's recurring payments if it's over 00:21:26.919 --> 00:21:28.860 align:start position:0% if it's recurring payments if it's over fifty<00:21:27.250> thousand<00:21:27.669> how<00:21:28.179> can<00:21:28.360> you<00:21:28.419> do<00:21:28.510> that<00:21:28.660> with 00:21:28.860 --> 00:21:28.870 align:start position:0% fifty thousand how can you do that with 00:21:28.870 --> 00:21:31.500 align:start position:0% fifty thousand how can you do that with uh<00:21:28.990> if<00:21:29.230> you<00:21:29.350> don't<00:21:29.470> know<00:21:29.650> your<00:21:29.860> customers<00:21:30.510> yes 00:21:31.500 --> 00:21:31.510 align:start position:0% uh if you don't know your customers yes 00:21:31.510 --> 00:21:34.680 align:start position:0% uh if you don't know your customers yes okay<00:21:31.900> I<00:21:31.929> see<00:21:32.290> AML<00:21:32.740> stuff<00:21:33.070> will<00:21:33.340> I<00:21:33.970> didn't<00:21:34.480> sure 00:21:34.680 --> 00:21:34.690 align:start position:0% okay I see AML stuff will I didn't sure 00:21:34.690 --> 00:21:36.240 align:start position:0% okay I see AML stuff will I didn't sure there's<00:21:34.929> yet<00:21:35.470> like<00:21:35.620> you<00:21:35.710> said<00:21:35.860> you<00:21:35.950> mentioned 00:21:36.240 --> 00:21:36.250 align:start position:0% there's yet like you said you mentioned 00:21:36.250 --> 00:21:38.490 align:start position:0% there's yet like you said you mentioned fifty<00:21:36.549> thousand<00:21:37.030> in<00:21:37.210> this<00:21:37.660> case<00:21:37.900> like<00:21:38.200> to 00:21:38.490 --> 00:21:38.500 align:start position:0% fifty thousand in this case like to 00:21:38.500 --> 00:21:40.230 align:start position:0% fifty thousand in this case like to subscribe<00:21:38.950> to<00:21:39.160> our<00:21:39.190> data<00:21:39.460> storage<00:21:39.850> service 00:21:40.230 --> 00:21:40.240 align:start position:0% subscribe to our data storage service 00:21:40.240 --> 00:21:43.020 align:start position:0% subscribe to our data storage service it's<00:21:40.450> definitely<00:21:40.929> not<00:21:41.049> fifty<00:21:41.380> thousand<00:21:42.030> it's 00:21:43.020 --> 00:21:43.030 align:start position:0% it's definitely not fifty thousand it's 00:21:43.030 --> 00:21:45.060 align:start position:0% it's definitely not fifty thousand it's much<00:21:43.240> cheaper<00:21:43.270> than<00:21:43.750> that<00:21:44.049> so<00:21:44.530> I<00:21:44.559> think<00:21:44.679> for 00:21:45.060 --> 00:21:45.070 align:start position:0% much cheaper than that so I think for 00:21:45.070 --> 00:21:46.740 align:start position:0% much cheaper than that so I think for like<00:21:45.250> the<00:21:45.460> day<00:21:45.669> to<00:21:45.730> day<00:21:45.940> subscriptions<00:21:46.660> that 00:21:46.740 --> 00:21:46.750 align:start position:0% like the day to day subscriptions that 00:21:46.750 --> 00:21:49.560 align:start position:0% like the day to day subscriptions that shouldn't<00:21:47.260> be<00:21:47.440> a<00:21:47.470> problem<00:21:47.650> but<00:21:48.220> I<00:21:48.850> can<00:21:49.179> tell 00:21:49.560 --> 00:21:49.570 align:start position:0% shouldn't be a problem but I can tell 00:21:49.570 --> 00:21:52.049 align:start position:0% shouldn't be a problem but I can tell you<00:21:49.750> once<00:21:50.020> we<00:21:50.230> implement<00:21:50.740> this<00:21:50.919> and<00:21:51.250> we<00:21:51.760> start 00:21:52.049 --> 00:21:52.059 align:start position:0% you once we implement this and we start 00:21:52.059 --> 00:21:55.080 align:start position:0% you once we implement this and we start actually<00:21:52.570> receiving<00:21:52.960> these<00:21:53.230> these<00:21:54.190> payments 00:21:55.080 --> 00:21:55.090 align:start position:0% actually receiving these these payments 00:21:55.090 --> 00:21:57.360 align:start position:0% actually receiving these these payments for<00:21:55.240> our<00:21:55.360> service<00:21:55.750> in<00:21:55.870> that<00:21:56.020> way<00:21:56.169> our<00:21:56.950> business 00:21:57.360 --> 00:21:57.370 align:start position:0% for our service in that way our business 00:21:57.370 --> 00:22:00.360 align:start position:0% for our service in that way our business will<00:21:57.549> definitely<00:21:58.320> and<00:21:59.320> before<00:21:59.650> that<00:21:59.679> -<00:21:59.950> but 00:22:00.360 --> 00:22:00.370 align:start position:0% will definitely and before that - but 00:22:00.370 --> 00:22:02.250 align:start position:0% will definitely and before that - but I'll<00:22:00.580> know<00:22:00.880> a<00:22:00.910> lot<00:22:01.210> more<00:22:01.450> about<00:22:01.750> how<00:22:01.960> this<00:22:02.200> is 00:22:02.250 --> 00:22:02.260 align:start position:0% I'll know a lot more about how this is 00:22:02.260 --> 00:22:03.570 align:start position:0% I'll know a lot more about how this is actually<00:22:02.559> going<00:22:02.860> to<00:22:02.950> be<00:22:03.040> handled<00:22:03.370> by<00:22:03.520> the 00:22:03.570 --> 00:22:03.580 align:start position:0% actually going to be handled by the 00:22:03.580 --> 00:22:06.510 align:start position:0% actually going to be handled by the regulator's<00:22:04.179> at<00:22:04.330> least<00:22:04.480> in<00:22:04.630> Germany<00:22:05.520> but 00:22:06.510 --> 00:22:06.520 align:start position:0% regulator's at least in Germany but 00:22:06.520 --> 00:22:08.159 align:start position:0% regulator's at least in Germany but right<00:22:06.940> now<00:22:07.059> it<00:22:07.210> doesn't<00:22:07.360> we<00:22:07.510> don't<00:22:07.540> foresee 00:22:08.159 --> 00:22:08.169 align:start position:0% right now it doesn't we don't foresee 00:22:08.169 --> 00:22:10.260 align:start position:0% right now it doesn't we don't foresee any<00:22:08.200> major<00:22:08.530> problems<00:22:09.160> about<00:22:09.610> that<00:22:09.880> because 00:22:10.260 --> 00:22:10.270 align:start position:0% any major problems about that because 00:22:10.270 --> 00:22:12.130 align:start position:0% any major problems about that because again<00:22:10.570> kyc<00:22:11.320> AML<00:22:11.679> is<00:22:11.830> more 00:22:12.130 --> 00:22:12.140 align:start position:0% again kyc AML is more 00:22:12.140 --> 00:22:15.340 align:start position:0% again kyc AML is more about<00:22:12.380> like<00:22:12.620> large<00:22:13.070> quantities<00:22:13.610> of<00:22:13.640> money<00:22:14.350> as 00:22:15.340 --> 00:22:15.350 align:start position:0% about like large quantities of money as 00:22:15.350 --> 00:22:16.840 align:start position:0% about like large quantities of money as far<00:22:15.620> as<00:22:15.680> I<00:22:15.770> understand<00:22:16.280> you're<00:22:16.490> shaking<00:22:16.820> your 00:22:16.840 --> 00:22:16.850 align:start position:0% far as I understand you're shaking your 00:22:16.850 --> 00:22:20.350 align:start position:0% far as I understand you're shaking your head<00:22:16.970> no<00:22:17.240> though<00:22:17.500> no<00:22:18.640> not<00:22:19.640> that's<00:22:19.940> not<00:22:20.120> my<00:22:20.210> area 00:22:20.350 --> 00:22:20.360 align:start position:0% head no though no not that's not my area 00:22:20.360 --> 00:22:22.930 align:start position:0% head no though no not that's not my area of<00:22:20.660> expertise<00:22:21.260> but<00:22:21.340> I<00:22:22.340> think<00:22:22.760> that<00:22:22.850> that's 00:22:22.930 --> 00:22:22.940 align:start position:0% of expertise but I think that that's 00:22:22.940 --> 00:22:24.070 align:start position:0% of expertise but I think that that's definitely<00:22:23.060> something<00:22:23.600> that<00:22:23.750> we<00:22:23.870> should 00:22:24.070 --> 00:22:24.080 align:start position:0% definitely something that we should 00:22:24.080 --> 00:22:25.510 align:start position:0% definitely something that we should explore<00:22:24.470> but<00:22:24.770> I<00:22:24.800> also<00:22:25.010> think<00:22:25.340> it's 00:22:25.510 --> 00:22:25.520 align:start position:0% explore but I also think it's 00:22:25.520 --> 00:22:27.430 align:start position:0% explore but I also think it's unrealistic<00:22:26.120> to<00:22:26.510> do<00:22:26.630> the<00:22:26.750> opposite<00:22:27.230> thing 00:22:27.430 --> 00:22:27.440 align:start position:0% unrealistic to do the opposite thing 00:22:27.440 --> 00:22:29.320 align:start position:0% unrealistic to do the opposite thing which<00:22:27.620> is<00:22:27.770> to<00:22:27.920> have<00:22:28.070> all<00:22:28.430> of<00:22:28.940> this<00:22:29.090> personal 00:22:29.320 --> 00:22:29.330 align:start position:0% which is to have all of this personal 00:22:29.330 --> 00:22:32.590 align:start position:0% which is to have all of this personal data<00:22:29.600> floating<00:22:30.260> around<00:22:30.380> in<00:22:30.890> public<00:22:31.130> too<00:22:31.910> so<00:22:32.300> we 00:22:32.590 --> 00:22:32.600 align:start position:0% data floating around in public too so we 00:22:32.600 --> 00:22:34.480 align:start position:0% data floating around in public too so we have<00:22:32.630> to<00:22:33.050> I<00:22:33.080> think<00:22:33.500> we<00:22:33.770> have<00:22:33.920> to<00:22:34.100> find<00:22:34.220> some 00:22:34.480 --> 00:22:34.490 align:start position:0% have to I think we have to find some 00:22:34.490 --> 00:22:36.720 align:start position:0% have to I think we have to find some sort<00:22:34.700> of<00:22:34.790> like<00:22:35.000> common<00:22:35.390> ground<00:22:35.690> between 00:22:36.720 --> 00:22:36.730 align:start position:0% sort of like common ground between 00:22:36.730 --> 00:22:39.220 align:start position:0% sort of like common ground between offering<00:22:37.730> more<00:22:37.910> privacy<00:22:38.390> for<00:22:38.540> subscription 00:22:39.220 --> 00:22:39.230 align:start position:0% offering more privacy for subscription 00:22:39.230 --> 00:22:41.320 align:start position:0% offering more privacy for subscription payments<00:22:39.620> you<00:22:39.710> with<00:22:40.310> cryptocurrency<00:22:40.670> and 00:22:41.320 --> 00:22:41.330 align:start position:0% payments you with cryptocurrency and 00:22:41.330 --> 00:22:52.659 align:start position:0% payments you with cryptocurrency and adhering<00:22:42.140> to<00:22:42.350> laws<00:22:42.770> and<00:22:42.800> regulations 00:22:52.659 --> 00:22:52.669 align:start position:0% 00:22:52.669 --> 00:22:54.730 align:start position:0% you