WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.470 align:start position:0% [Applause] 00:00:12.470 --> 00:00:12.480 align:start position:0% 00:00:12.480 --> 00:00:16.560 align:start position:0% okay<00:00:13.510> hi<00:00:14.379> everyone<00:00:14.740> the<00:00:15.549> panel<00:00:16.299> that<00:00:16.420> we're 00:00:16.560 --> 00:00:16.570 align:start position:0% okay hi everyone the panel that we're 00:00:16.570 --> 00:00:18.330 align:start position:0% okay hi everyone the panel that we're doing<00:00:16.689> right<00:00:16.960> now<00:00:16.990> is<00:00:17.380> called<00:00:17.410> house<00:00:17.800> scaling 00:00:18.330 --> 00:00:18.340 align:start position:0% doing right now is called house scaling 00:00:18.340 --> 00:00:21.030 align:start position:0% doing right now is called house scaling and<00:00:18.550> tax<00:00:18.790> privacy<00:00:19.360> I<00:00:19.570> apologize<00:00:20.500> my<00:00:20.650> voice<00:00:20.860> is 00:00:21.030 --> 00:00:21.040 align:start position:0% and tax privacy I apologize my voice is 00:00:21.040 --> 00:00:22.740 align:start position:0% and tax privacy I apologize my voice is a<00:00:21.070> little<00:00:21.130> rough<00:00:21.460> today<00:00:21.610> but<00:00:22.060> I<00:00:22.270> think<00:00:22.509> I<00:00:22.599> can 00:00:22.740 --> 00:00:22.750 align:start position:0% a little rough today but I think I can 00:00:22.750 --> 00:00:25.859 align:start position:0% a little rough today but I think I can manage<00:00:23.130> my<00:00:24.130> name<00:00:24.279> is<00:00:24.460> Liz<00:00:24.669> Steiner<00:00:25.150> I<00:00:25.450> work<00:00:25.720> at 00:00:25.859 --> 00:00:25.869 align:start position:0% manage my name is Liz Steiner I work at 00:00:25.869 --> 00:00:28.080 align:start position:0% manage my name is Liz Steiner I work at the<00:00:25.960> authority<00:00:26.529> but<00:00:27.220> I'm<00:00:27.489> just<00:00:27.730> here<00:00:27.910> to 00:00:28.080 --> 00:00:28.090 align:start position:0% the authority but I'm just here to 00:00:28.090 --> 00:00:30.659 align:start position:0% the authority but I'm just here to moderate<00:00:28.419> a<00:00:28.480> panel<00:00:28.570> and<00:00:29.099> we<00:00:30.099> have<00:00:30.309> four 00:00:30.659 --> 00:00:30.669 align:start position:0% moderate a panel and we have four 00:00:30.669 --> 00:00:33.360 align:start position:0% moderate a panel and we have four wonderful<00:00:30.989> panelists<00:00:31.989> to<00:00:32.739> talk<00:00:33.070> about<00:00:33.280> this 00:00:33.360 --> 00:00:33.370 align:start position:0% wonderful panelists to talk about this 00:00:33.370 --> 00:00:35.880 align:start position:0% wonderful panelists to talk about this topic<00:00:33.610> today<00:00:33.880> and<00:00:34.230> I'm<00:00:35.230> going<00:00:35.469> to<00:00:35.559> let<00:00:35.739> them 00:00:35.880 --> 00:00:35.890 align:start position:0% topic today and I'm going to let them 00:00:35.890 --> 00:00:39.030 align:start position:0% topic today and I'm going to let them introduce<00:00:36.160> themselves<00:00:37.260> and<00:00:38.260> then<00:00:38.530> we'll<00:00:38.800> also 00:00:39.030 --> 00:00:39.040 align:start position:0% introduce themselves and then we'll also 00:00:39.040 --> 00:00:42.350 align:start position:0% introduce themselves and then we'll also in<00:00:39.430> the<00:00:39.489> more<00:00:39.610> concerning 00:00:42.350 --> 00:00:42.360 align:start position:0% 00:00:42.360 --> 00:00:45.780 align:start position:0% I'm<00:00:43.360> Josh<00:00:44.170> Cincinnati<00:00:44.860> I'm<00:00:45.160> the<00:00:45.400> executive 00:00:45.780 --> 00:00:45.790 align:start position:0% I'm Josh Cincinnati I'm the executive 00:00:45.790 --> 00:00:47.910 align:start position:0% I'm Josh Cincinnati I'm the executive director<00:00:46.180> of<00:00:46.600> the<00:00:46.780> CGI<00:00:47.110> Foundation<00:00:47.710> a 00:00:47.910 --> 00:00:47.920 align:start position:0% director of the CGI Foundation a 00:00:47.920 --> 00:00:52.160 align:start position:0% director of the CGI Foundation a us-based<00:00:49.200> biomimicry<00:00:50.200> nonprofit<00:00:50.890> focused<00:00:51.340> on 00:00:52.160 --> 00:00:52.170 align:start position:0% us-based biomimicry nonprofit focused on 00:00:52.170 --> 00:00:55.110 align:start position:0% us-based biomimicry nonprofit focused on pricy<00:00:53.490> financial<00:00:54.490> transactions<00:00:54.970> online 00:00:55.110 --> 00:00:55.120 align:start position:0% pricy financial transactions online 00:00:55.120 --> 00:00:57.960 align:start position:0% pricy financial transactions online permanently<00:00:55.810> through<00:00:56.260> through<00:00:56.800> some<00:00:56.980> cash 00:00:57.960 --> 00:00:57.970 align:start position:0% permanently through through some cash 00:00:57.970 --> 00:00:59.940 align:start position:0% permanently through through some cash I'm<00:00:58.630> very<00:00:58.810> excited<00:00:59.170> talk<00:00:59.350> about<00:00:59.500> all<00:00:59.590> this<00:00:59.710> day 00:00:59.940 --> 00:00:59.950 align:start position:0% I'm very excited talk about all this day 00:00:59.950 --> 00:01:02.160 align:start position:0% I'm very excited talk about all this day this<00:01:00.910> breezy<00:01:01.210> said<00:01:01.570> the<00:01:01.720> camera<00:01:02.020> a<00:01:02.050> little 00:01:02.160 --> 00:01:02.170 align:start position:0% this breezy said the camera a little 00:01:02.170 --> 00:01:04.859 align:start position:0% this breezy said the camera a little rant<00:01:02.590> about<00:01:02.950> privacy<00:01:03.760> as<00:01:04.119> per<00:01:04.329> this<00:01:04.479> reduction 00:01:04.859 --> 00:01:04.869 align:start position:0% rant about privacy as per this reduction 00:01:04.869 --> 00:01:09.120 align:start position:0% rant about privacy as per this reduction so<00:01:05.259> what<00:01:05.590> yeah<00:01:06.040> we<00:01:06.759> had<00:01:07.119> that<00:01:07.560> so<00:01:08.560> yeah<00:01:08.799> why 00:01:09.120 --> 00:01:09.130 align:start position:0% so what yeah we had that so yeah why 00:01:09.130 --> 00:01:12.780 align:start position:0% so what yeah we had that so yeah why just<00:01:09.610> scaling<00:01:10.710> how<00:01:11.710> do<00:01:11.770> you<00:01:11.920> think<00:01:12.070> scaling<00:01:12.579> in 00:01:12.780 --> 00:01:12.790 align:start position:0% just scaling how do you think scaling in 00:01:12.790 --> 00:01:14.500 align:start position:0% just scaling how do you think scaling in pets<00:01:13.000> plants<00:01:13.270> you<00:01:13.570> might<00:01:13.720> even<00:01:13.960> get<00:01:14.079> my 00:01:14.500 --> 00:01:14.510 align:start position:0% pets plants you might even get my 00:01:14.510 --> 00:01:18.610 align:start position:0% pets plants you might even get my it's<00:01:15.020> discussion<00:01:15.500> on<00:01:16.010> yeah<00:01:16.220> for<00:01:16.940> me<00:01:17.120> I<00:01:17.780> think 00:01:18.610 --> 00:01:18.620 align:start position:0% it's discussion on yeah for me I think 00:01:18.620 --> 00:01:20.830 align:start position:0% it's discussion on yeah for me I think somebody's<00:01:19.340> becoming<00:01:19.670> apparently<00:01:20.180> liquor 00:01:20.830 --> 00:01:20.840 align:start position:0% somebody's becoming apparently liquor 00:01:20.840 --> 00:01:24.850 align:start position:0% somebody's becoming apparently liquor apparent<00:01:21.620> is<00:01:22.520> that<00:01:22.760> oftentimes<00:01:23.860> the 00:01:24.850 --> 00:01:24.860 align:start position:0% apparent is that oftentimes the 00:01:24.860 --> 00:01:27.730 align:start position:0% apparent is that oftentimes the discussion<00:01:25.340> around<00:01:25.930> practices<00:01:26.930> is<00:01:27.290> at<00:01:27.470> odds 00:01:27.730 --> 00:01:27.740 align:start position:0% discussion around practices is at odds 00:01:27.740 --> 00:01:32.080 align:start position:0% discussion around practices is at odds with<00:01:28.450> what<00:01:29.450> we<00:01:29.540> can<00:01:29.720> do<00:01:30.070> the<00:01:31.070> things<00:01:31.340> that<00:01:31.580> can 00:01:32.080 --> 00:01:32.090 align:start position:0% with what we can do the things that can 00:01:32.090 --> 00:01:35.020 align:start position:0% with what we can do the things that can able<00:01:32.270> scalability<00:01:33.080> and<00:01:33.230> I<00:01:33.290> sacrifice<00:01:33.950> one<00:01:34.910> in 00:01:35.020 --> 00:01:35.030 align:start position:0% able scalability and I sacrifice one in 00:01:35.030 --> 00:01:37.960 align:start position:0% able scalability and I sacrifice one in order<00:01:35.240> to<00:01:35.450> have<00:01:36.200> the<00:01:36.380> other<00:01:36.560> the<00:01:37.460> other<00:01:37.610> the 00:01:37.960 --> 00:01:37.970 align:start position:0% order to have the other the other the 00:01:37.970 --> 00:01:40.060 align:start position:0% order to have the other the other the other<00:01:38.030> thing<00:01:38.180> that<00:01:38.420> I'm<00:01:38.840> like<00:01:39.770> really 00:01:40.060 --> 00:01:40.070 align:start position:0% other thing that I'm like really 00:01:40.070 --> 00:01:41.290 align:start position:0% other thing that I'm like really fundamentally<00:01:40.670> concerned<00:01:41.000> about<00:01:41.210> is 00:01:41.290 --> 00:01:41.300 align:start position:0% fundamentally concerned about is 00:01:41.300 --> 00:01:45.490 align:start position:0% fundamentally concerned about is actually<00:01:41.450> more<00:01:41.750> about<00:01:41.980> scaling<00:01:44.290> but<00:01:45.290> scaling 00:01:45.490 --> 00:01:45.500 align:start position:0% actually more about scaling but scaling 00:01:45.500 --> 00:01:48.300 align:start position:0% actually more about scaling but scaling a<00:01:45.710> public<00:01:46.070> discussion<00:01:46.490> around 00:01:48.300 --> 00:01:48.310 align:start position:0% a public discussion around 00:01:48.310 --> 00:01:51.130 align:start position:0% a public discussion around Whiteface<00:01:49.310> is<00:01:49.580> important<00:01:50.150> because<00:01:50.360> if<00:01:50.840> we 00:01:51.130 --> 00:01:51.140 align:start position:0% Whiteface is important because if we 00:01:51.140 --> 00:01:53.800 align:start position:0% Whiteface is important because if we don't<00:01:51.350> really<00:01:52.150> socially<00:01:53.150> agree<00:01:53.420> that<00:01:53.570> it<00:01:53.660> is 00:01:53.800 --> 00:01:53.810 align:start position:0% don't really socially agree that it is 00:01:53.810 --> 00:01:55.750 align:start position:0% don't really socially agree that it is we're<00:01:54.680> going<00:01:54.860> to<00:01:54.979> have<00:01:55.100> a<00:01:55.130> very<00:01:55.460> hard<00:01:55.640> time 00:01:55.750 --> 00:01:55.760 align:start position:0% we're going to have a very hard time 00:01:55.760 --> 00:01:58.270 align:start position:0% we're going to have a very hard time actually<00:01:56.410> convincing<00:01:57.410> people<00:01:57.560> to<00:01:57.710> integrate 00:01:58.270 --> 00:01:58.280 align:start position:0% actually convincing people to integrate 00:01:58.280 --> 00:02:00.010 align:start position:0% actually convincing people to integrate the<00:01:58.460> things<00:01:58.700> necessary<00:01:58.910> to<00:01:59.450> make<00:01:59.840> this 00:02:00.010 --> 00:02:00.020 align:start position:0% the things necessary to make this 00:02:00.020 --> 00:02:05.200 align:start position:0% the things necessary to make this awesome<00:02:03.280> hi<00:02:04.280> I'm<00:02:04.490> Ellie 00:02:05.200 --> 00:02:05.210 align:start position:0% awesome hi I'm Ellie 00:02:05.210 --> 00:02:07.870 align:start position:0% awesome hi I'm Ellie I<00:02:05.390> am<00:02:05.770> co-founder<00:02:06.770> and<00:02:06.950> chief<00:02:07.130> scientist<00:02:07.700> at 00:02:07.870 --> 00:02:07.880 align:start position:0% I am co-founder and chief scientist at 00:02:07.880 --> 00:02:10.150 align:start position:0% I am co-founder and chief scientist at off<00:02:08.030> chain<00:02:08.300> labs<00:02:08.570> I'm<00:02:08.929> a<00:02:09.590> professor<00:02:09.920> at 00:02:10.150 --> 00:02:10.160 align:start position:0% off chain labs I'm a professor at 00:02:10.160 --> 00:02:12.220 align:start position:0% off chain labs I'm a professor at Princeton<00:02:10.670> and<00:02:10.790> some<00:02:11.120> time<00:02:11.360> US<00:02:11.780> government 00:02:12.220 --> 00:02:12.230 align:start position:0% Princeton and some time US government 00:02:12.230 --> 00:02:21.430 align:start position:0% Princeton and some time US government official<00:02:13.510> so<00:02:17.470> so<00:02:19.120> for<00:02:20.120> me<00:02:20.270> they<00:02:20.570> one<00:02:21.290> of<00:02:21.320> the 00:02:21.430 --> 00:02:21.440 align:start position:0% official so so for me they one of the 00:02:21.440 --> 00:02:24.160 align:start position:0% official so so for me they one of the big<00:02:21.590> issues<00:02:21.770> about<00:02:22.640> scaling<00:02:23.180> and<00:02:23.420> privacy<00:02:23.959> is 00:02:24.160 --> 00:02:24.170 align:start position:0% big issues about scaling and privacy is 00:02:24.170 --> 00:02:28.420 align:start position:0% big issues about scaling and privacy is what<00:02:24.650> happens<00:02:25.130> as<00:02:25.310> we<00:02:25.630> try<00:02:26.630> to<00:02:27.250> meet<00:02:28.250> this 00:02:28.420 --> 00:02:28.430 align:start position:0% what happens as we try to meet this 00:02:28.430 --> 00:02:30.790 align:start position:0% what happens as we try to meet this vision<00:02:28.910> of<00:02:29.090> web<00:02:29.420> 3<00:02:29.840> of<00:02:30.050> scaling<00:02:30.500> up<00:02:30.620> this 00:02:30.790 --> 00:02:30.800 align:start position:0% vision of web 3 of scaling up this 00:02:30.800 --> 00:02:32.290 align:start position:0% vision of web 3 of scaling up this technology<00:02:31.430> to<00:02:31.640> the<00:02:31.730> point<00:02:31.760> where<00:02:32.180> it's 00:02:32.290 --> 00:02:32.300 align:start position:0% technology to the point where it's 00:02:32.300 --> 00:02:34.420 align:start position:0% technology to the point where it's something<00:02:32.690> that<00:02:32.959> everybody<00:02:33.620> uses<00:02:33.980> all<00:02:34.310> the 00:02:34.420 --> 00:02:34.430 align:start position:0% something that everybody uses all the 00:02:34.430 --> 00:02:36.520 align:start position:0% something that everybody uses all the time<00:02:34.670> and<00:02:35.510> I<00:02:35.600> think<00:02:35.660> there's<00:02:35.930> a<00:02:36.019> lot<00:02:36.200> we<00:02:36.380> can 00:02:36.520 --> 00:02:36.530 align:start position:0% time and I think there's a lot we can 00:02:36.530 --> 00:02:38.500 align:start position:0% time and I think there's a lot we can learn<00:02:36.590> from<00:02:36.830> the<00:02:37.250> history<00:02:37.610> of<00:02:37.730> privacy<00:02:38.239> on<00:02:38.480> the 00:02:38.500 --> 00:02:38.510 align:start position:0% learn from the history of privacy on the 00:02:38.510 --> 00:02:39.160 align:start position:0% learn from the history of privacy on the web 00:02:39.160 --> 00:02:39.170 align:start position:0% web 00:02:39.170 --> 00:02:43.180 align:start position:0% web in<00:02:39.260> web<00:02:39.500> 2<00:02:40.000> which<00:02:41.000> were<00:02:41.300> not<00:02:41.960> good<00:02:42.290> people<00:02:43.100> are 00:02:43.180 --> 00:02:43.190 align:start position:0% in web 2 which were not good people are 00:02:43.190 --> 00:02:44.860 align:start position:0% in web 2 which were not good people are very<00:02:43.400> unhappy<00:02:43.790> with<00:02:44.090> how<00:02:44.270> that<00:02:44.330> worked<00:02:44.690> out 00:02:44.860 --> 00:02:44.870 align:start position:0% very unhappy with how that worked out 00:02:44.870 --> 00:02:47.080 align:start position:0% very unhappy with how that worked out and<00:02:45.440> it's<00:02:45.650> not<00:02:45.860> because<00:02:46.370> there<00:02:46.700> was<00:02:46.730> not 00:02:47.080 --> 00:02:47.090 align:start position:0% and it's not because there was not 00:02:47.090 --> 00:02:49.630 align:start position:0% and it's not because there was not useful<00:02:47.480> privacy<00:02:48.200> technology<00:02:48.620> there<00:02:49.220> we<00:02:49.459> knew 00:02:49.630 --> 00:02:49.640 align:start position:0% useful privacy technology there we knew 00:02:49.640 --> 00:02:51.760 align:start position:0% useful privacy technology there we knew how<00:02:49.790> to<00:02:49.850> do<00:02:50.030> end-to-end<00:02:50.390> description<00:02:51.140> we<00:02:51.620> knew 00:02:51.760 --> 00:02:51.770 align:start position:0% how to do end-to-end description we knew 00:02:51.770 --> 00:02:53.770 align:start position:0% how to do end-to-end description we knew how<00:02:51.920> to<00:02:51.980> encrypt<00:02:52.370> it<00:02:52.610> in<00:02:52.700> place<00:02:52.940> we<00:02:53.510> knew<00:02:53.660> how 00:02:53.770 --> 00:02:53.780 align:start position:0% how to encrypt it in place we knew how 00:02:53.780 --> 00:02:56.199 align:start position:0% how to encrypt it in place we knew how to<00:02:53.840> do<00:02:54.050> strong<00:02:54.350> authentication<00:02:54.820> we<00:02:55.820> knew<00:02:56.030> how 00:02:56.199 --> 00:02:56.209 align:start position:0% to do strong authentication we knew how 00:02:56.209 --> 00:02:59.110 align:start position:0% to do strong authentication we knew how to<00:02:56.270> do<00:02:56.510> a<00:02:56.540> lot<00:02:56.840> of<00:02:56.959> things<00:02:57.260> that<00:02:57.740> somehow<00:02:58.730> did 00:02:59.110 --> 00:02:59.120 align:start position:0% to do a lot of things that somehow did 00:02:59.120 --> 00:03:01.060 align:start position:0% to do a lot of things that somehow did not<00:02:59.150> actually<00:02:59.600> get<00:03:00.050> done<00:03:00.260> in<00:03:00.410> practice<00:03:00.650> with 00:03:01.060 --> 00:03:01.070 align:start position:0% not actually get done in practice with 00:03:01.070 --> 00:03:03.970 align:start position:0% not actually get done in practice with our<00:03:01.280> name<00:03:01.690> we<00:03:02.690> had<00:03:02.900> horrible<00:03:03.170> problems<00:03:03.740> with 00:03:03.970 --> 00:03:03.980 align:start position:0% our name we had horrible problems with 00:03:03.980 --> 00:03:05.620 align:start position:0% our name we had horrible problems with endpoint<00:03:04.430> security<00:03:04.610> we<00:03:05.150> have<00:03:05.270> all<00:03:05.450> the 00:03:05.620 --> 00:03:05.630 align:start position:0% endpoint security we have all the 00:03:05.630 --> 00:03:07.270 align:start position:0% endpoint security we have all the problems<00:03:06.080> with<00:03:06.290> all<00:03:06.440> of<00:03:06.590> our<00:03:06.680> data<00:03:06.950> is<00:03:07.040> sitting 00:03:07.270 --> 00:03:07.280 align:start position:0% problems with all of our data is sitting 00:03:07.280 --> 00:03:09.190 align:start position:0% problems with all of our data is sitting in<00:03:07.700> corporate<00:03:08.090> servers<00:03:08.510> where<00:03:08.750> who<00:03:09.170> knows 00:03:09.190 --> 00:03:09.200 align:start position:0% in corporate servers where who knows 00:03:09.200 --> 00:03:11.800 align:start position:0% in corporate servers where who knows what<00:03:09.590> happens<00:03:09.980> to<00:03:10.160> it<00:03:10.310> the<00:03:10.880> point<00:03:11.180> being<00:03:11.420> that 00:03:11.800 --> 00:03:11.810 align:start position:0% what happens to it the point being that 00:03:11.810 --> 00:03:14.050 align:start position:0% what happens to it the point being that having<00:03:12.350> the<00:03:12.530> technological<00:03:13.340> tools<00:03:13.640> there<00:03:14.030> is 00:03:14.050 --> 00:03:14.060 align:start position:0% having the technological tools there is 00:03:14.060 --> 00:03:16.750 align:start position:0% having the technological tools there is not<00:03:14.540> enough<00:03:14.840> if<00:03:15.080> we<00:03:15.680> just<00:03:15.920> redo<00:03:16.370> everything 00:03:16.750 --> 00:03:16.760 align:start position:0% not enough if we just redo everything 00:03:16.760 --> 00:03:18.790 align:start position:0% not enough if we just redo everything that<00:03:17.030> happened<00:03:17.390> in<00:03:17.510> web-one<00:03:17.720> and<00:03:18.110> web<00:03:18.290> 2<00:03:18.530> but 00:03:18.790 --> 00:03:18.800 align:start position:0% that happened in web-one and web 2 but 00:03:18.800 --> 00:03:20.860 align:start position:0% that happened in web-one and web 2 but now<00:03:19.010> with<00:03:19.430> more<00:03:19.730> stuff<00:03:20.060> on<00:03:20.239> a<00:03:20.300> public<00:03:20.690> ledger 00:03:20.860 --> 00:03:20.870 align:start position:0% now with more stuff on a public ledger 00:03:20.870 --> 00:03:23.050 align:start position:0% now with more stuff on a public ledger we're<00:03:21.680> going<00:03:21.800> to<00:03:21.890> get<00:03:22.010> a<00:03:22.070> result<00:03:22.250> that<00:03:22.670> is<00:03:22.730> no 00:03:23.050 --> 00:03:23.060 align:start position:0% we're going to get a result that is no 00:03:23.060 --> 00:03:25.479 align:start position:0% we're going to get a result that is no better<00:03:23.330> and<00:03:24.290> so<00:03:24.470> we<00:03:24.560> have<00:03:24.709> to<00:03:24.860> think<00:03:25.100> beyond 00:03:25.479 --> 00:03:25.489 align:start position:0% better and so we have to think beyond 00:03:25.489 --> 00:03:28.449 align:start position:0% better and so we have to think beyond just<00:03:25.970> building<00:03:26.480> the<00:03:26.870> technological<00:03:27.620> tools<00:03:27.890> we 00:03:28.449 --> 00:03:28.459 align:start position:0% just building the technological tools we 00:03:28.459 --> 00:03:31.240 align:start position:0% just building the technological tools we have<00:03:28.610> to<00:03:28.760> understand<00:03:29.330> how<00:03:29.690> to<00:03:29.720> build<00:03:30.170> a<00:03:30.530> market 00:03:31.240 --> 00:03:31.250 align:start position:0% have to understand how to build a market 00:03:31.250 --> 00:03:32.830 align:start position:0% have to understand how to build a market and<00:03:31.459> how<00:03:31.610> to<00:03:31.670> build<00:03:31.970> a<00:03:32.120> structure<00:03:32.450> in<00:03:32.750> the 00:03:32.830 --> 00:03:32.840 align:start position:0% and how to build a structure in the 00:03:32.840 --> 00:03:34.390 align:start position:0% and how to build a structure in the community<00:03:33.350> that's<00:03:33.890> going<00:03:34.190> to<00:03:34.280> behave 00:03:34.390 --> 00:03:34.400 align:start position:0% community that's going to behave 00:03:34.400 --> 00:03:37.380 align:start position:0% community that's going to behave differently<00:03:34.580> and<00:03:35.480> then<00:03:35.810> others<00:03:36.680> have<00:03:36.890> before 00:03:37.380 --> 00:03:37.390 align:start position:0% differently and then others have before 00:03:37.390 --> 00:03:42.759 align:start position:0% differently and then others have before when<00:03:38.390> the<00:03:39.200> big<00:03:39.380> money<00:03:39.650> shows<00:03:39.980> up<00:03:41.260> hi<00:03:42.260> so<00:03:42.739> my 00:03:42.759 --> 00:03:42.769 align:start position:0% when the big money shows up hi so my 00:03:42.769 --> 00:03:45.699 align:start position:0% when the big money shows up hi so my name<00:03:43.070> is<00:03:43.220> Ian<00:03:43.519> virus<00:03:43.989> the<00:03:44.989> shopping 00:03:45.699 --> 00:03:45.709 align:start position:0% name is Ian virus the shopping 00:03:45.709 --> 00:03:48.030 align:start position:0% name is Ian virus the shopping scientists<00:03:46.190> see<00:03:46.670> Josh<00:03:46.940> and<00:03:47.299> that's 00:03:48.030 --> 00:03:48.040 align:start position:0% scientists see Josh and that's 00:03:48.040 --> 00:03:49.830 align:start position:0% scientists see Josh and that's that's<00:03:48.340> all<00:03:48.670> for<00:03:49.090> the<00:03:49.390> University<00:03:49.810> of 00:03:49.830 --> 00:03:49.840 align:start position:0% that's all for the University of 00:03:49.840 --> 00:03:53.130 align:start position:0% that's all for the University of Maryland<00:03:50.189> loan<00:03:51.480> first<00:03:52.480> time<00:03:52.629> cryptocurrency 00:03:53.130 --> 00:03:53.140 align:start position:0% Maryland loan first time cryptocurrency 00:03:53.140 --> 00:03:54.929 align:start position:0% Maryland loan first time cryptocurrency because<00:03:53.709> I<00:03:53.950> was<00:03:54.159> worried<00:03:54.400> about<00:03:54.459> kind<00:03:54.879> of 00:03:54.929 --> 00:03:54.939 align:start position:0% because I was worried about kind of 00:03:54.939 --> 00:03:57.569 align:start position:0% because I was worried about kind of aspects<00:03:55.689> of<00:03:55.840> it<00:03:55.959> because<00:03:56.290> if<00:03:57.129> occurrence<00:03:57.489> is 00:03:57.569 --> 00:03:57.579 align:start position:0% aspects of it because if occurrence is 00:03:57.579 --> 00:03:59.839 align:start position:0% aspects of it because if occurrence is basically<00:03:57.849> Twitter<00:03:58.239> for<00:03:58.480> your<00:03:58.599> bank<00:03:58.780> account 00:03:59.839 --> 00:03:59.849 align:start position:0% basically Twitter for your bank account 00:03:59.849 --> 00:04:02.069 align:start position:0% basically Twitter for your bank account everything's<00:04:00.849> help<00:04:01.120> everybody<00:04:01.480> that's<00:04:01.780> not 00:04:02.069 --> 00:04:02.079 align:start position:0% everything's help everybody that's not 00:04:02.079 --> 00:04:03.750 align:start position:0% everything's help everybody that's not accepted<00:04:02.620> for<00:04:02.739> the<00:04:02.799> same<00:04:02.980> reasons<00:04:03.310> that<00:04:03.370> this 00:04:03.750 --> 00:04:03.760 align:start position:0% accepted for the same reasons that this 00:04:03.760 --> 00:04:06.569 align:start position:0% accepted for the same reasons that this said<00:04:04.239> that's<00:04:05.140> also<00:04:05.440> an<00:04:05.530> actually<00:04:06.099> link<00:04:06.400> I 00:04:06.569 --> 00:04:06.579 align:start position:0% said that's also an actually link I 00:04:06.579 --> 00:04:09.360 align:start position:0% said that's also an actually link I think<00:04:06.610> to<00:04:07.209> the<00:04:07.390> scaling<00:04:07.810> problem<00:04:08.290> like<00:04:09.099> a<00:04:09.129> lot 00:04:09.360 --> 00:04:09.370 align:start position:0% think to the scaling problem like a lot 00:04:09.370 --> 00:04:10.819 align:start position:0% think to the scaling problem like a lot of<00:04:09.459> people<00:04:09.700> think<00:04:09.879> that<00:04:09.970> privacy<00:04:10.299> it<00:04:10.569> needs 00:04:10.819 --> 00:04:10.829 align:start position:0% of people think that privacy it needs 00:04:10.829 --> 00:04:13.110 align:start position:0% of people think that privacy it needs bonuses<00:04:11.829> here<00:04:12.040> they<00:04:12.250> make<00:04:12.430> sting<00:04:12.700> a<00:04:12.730> part<00:04:13.060> of 00:04:13.110 --> 00:04:13.120 align:start position:0% bonuses here they make sting a part of 00:04:13.120 --> 00:04:14.880 align:start position:0% bonuses here they make sting a part of the<00:04:13.360> things<00:04:13.569> like<00:04:13.720> the<00:04:13.900> it's<00:04:14.109> not<00:04:14.290> spam<00:04:14.620> or 00:04:14.880 --> 00:04:14.890 align:start position:0% the things like the it's not spam or 00:04:14.890 --> 00:04:17.819 align:start position:0% the things like the it's not spam or slow<00:04:15.269> when<00:04:16.269> it<00:04:16.299> comes<00:04:16.660> to<00:04:16.840> you<00:04:16.930> verified<00:04:17.440> in<00:04:17.680> on 00:04:17.819 --> 00:04:17.829 align:start position:0% slow when it comes to you verified in on 00:04:17.829 --> 00:04:20.000 align:start position:0% slow when it comes to you verified in on watching<00:04:18.459> it<00:04:18.729> actually<00:04:19.090> makes<00:04:19.269> things<00:04:19.449> faster 00:04:20.000 --> 00:04:20.010 align:start position:0% watching it actually makes things faster 00:04:20.010 --> 00:04:22.800 align:start position:0% watching it actually makes things faster because<00:04:21.030> Twitter<00:04:22.030> for<00:04:22.210> your<00:04:22.300> bank<00:04:22.479> account 00:04:22.800 --> 00:04:22.810 align:start position:0% because Twitter for your bank account 00:04:22.810 --> 00:04:25.439 align:start position:0% because Twitter for your bank account also<00:04:23.050> distress<00:04:23.560> stealing<00:04:24.100> problem<00:04:24.580> somewhat 00:04:25.439 --> 00:04:25.449 align:start position:0% also distress stealing problem somewhat 00:04:25.449 --> 00:04:26.820 align:start position:0% also distress stealing problem somewhat actually<00:04:25.840> the<00:04:26.080> Twitter<00:04:26.410> have<00:04:26.680> these 00:04:26.820 --> 00:04:26.830 align:start position:0% actually the Twitter have these 00:04:26.830 --> 00:04:28.770 align:start position:0% actually the Twitter have these hilarious<00:04:27.340> problems<00:04:28.210> when<00:04:28.479> they<00:04:28.600> first 00:04:28.770 --> 00:04:28.780 align:start position:0% hilarious problems when they first 00:04:28.780 --> 00:04:30.300 align:start position:0% hilarious problems when they first started<00:04:29.199> is<00:04:29.530> they<00:04:29.680> were<00:04:29.770> trying<00:04:29.800> to<00:04:30.039> broadcast 00:04:30.300 --> 00:04:30.310 align:start position:0% started is they were trying to broadcast 00:04:30.310 --> 00:04:33.180 align:start position:0% started is they were trying to broadcast huge<00:04:30.910> amounts<00:04:31.240> of<00:04:31.300> data<00:04:31.510> to<00:04:31.690> everybody<00:04:32.320> and<00:04:33.010> so 00:04:33.180 --> 00:04:33.190 align:start position:0% huge amounts of data to everybody and so 00:04:33.190 --> 00:04:35.189 align:start position:0% huge amounts of data to everybody and so you<00:04:33.310> solve<00:04:33.610> the<00:04:34.090> privacy<00:04:34.840> problem<00:04:35.110> by 00:04:35.189 --> 00:04:35.199 align:start position:0% you solve the privacy problem by 00:04:35.199 --> 00:04:37.439 align:start position:0% you solve the privacy problem by removing<00:04:35.350> that<00:04:35.680> data<00:04:36.039> and<00:04:36.430> they<00:04:37.000> came<00:04:37.180> closer 00:04:37.439 --> 00:04:37.449 align:start position:0% removing that data and they came closer 00:04:37.449 --> 00:04:39.360 align:start position:0% removing that data and they came closer verify<00:04:37.990> you've<00:04:38.229> also<00:04:38.530> apparently<00:04:38.979> solved 00:04:39.360 --> 00:04:39.370 align:start position:0% verify you've also apparently solved 00:04:39.370 --> 00:04:41.100 align:start position:0% verify you've also apparently solved scaling<00:04:39.789> problem<00:04:40.150> so<00:04:40.300> I<00:04:40.360> think<00:04:40.449> these<00:04:40.690> two 00:04:41.100 --> 00:04:41.110 align:start position:0% scaling problem so I think these two 00:04:41.110 --> 00:04:43.080 align:start position:0% scaling problem so I think these two things<00:04:41.350> are<00:04:41.500> linked<00:04:42.430> they're<00:04:42.639> actually<00:04:42.940> thing 00:04:43.080 --> 00:04:43.090 align:start position:0% things are linked they're actually thing 00:04:43.090 --> 00:04:47.719 align:start position:0% things are linked they're actually thing where<00:04:43.270> you<00:04:43.630> can<00:04:43.750> ask<00:04:43.870> energies<00:04:44.320> between<00:04:44.530> them 00:04:47.719 --> 00:04:47.729 align:start position:0% 00:04:47.729 --> 00:04:52.980 align:start position:0% my<00:04:48.729> name<00:04:48.789> is<00:04:49.060> Jacob<00:04:49.630> Evos<00:04:51.090> I'm<00:04:52.090> a<00:04:52.150> research<00:04:52.750> at 00:04:52.980 --> 00:04:52.990 align:start position:0% my name is Jacob Evos I'm a research at 00:04:52.990 --> 00:04:57.140 align:start position:0% my name is Jacob Evos I'm a research at Technical<00:04:53.770> University<00:04:53.880> of<00:04:54.880> Berlin<00:04:55.360> and<00:04:56.130> so 00:04:57.140 --> 00:04:57.150 align:start position:0% Technical University of Berlin and so 00:04:57.150 --> 00:04:59.640 align:start position:0% Technical University of Berlin and so why<00:04:58.150> I'm<00:04:58.330> here<00:04:58.599> is<00:04:58.810> I<00:04:58.840> work<00:04:59.139> on<00:04:59.410> different 00:04:59.640 --> 00:04:59.650 align:start position:0% why I'm here is I work on different 00:04:59.650 --> 00:05:01.110 align:start position:0% why I'm here is I work on different things<00:04:59.949> that<00:05:00.340> the<00:05:00.460> contacts<00:05:00.820> are<00:05:00.940> off 00:05:01.110 --> 00:05:01.120 align:start position:0% things that the contacts are off 00:05:01.120 --> 00:05:03.930 align:start position:0% things that the contacts are off changing<00:05:01.599> and<00:05:01.840> one<00:05:01.990> of<00:05:02.110> these<00:05:02.289> things<00:05:02.770> was<00:05:03.610> to 00:05:03.930 --> 00:05:03.940 align:start position:0% changing and one of these things was to 00:05:03.940 --> 00:05:05.909 align:start position:0% changing and one of these things was to Socrates<00:05:04.479> framework<00:05:05.139> which<00:05:05.380> is<00:05:05.530> kind<00:05:05.740> of 00:05:05.909 --> 00:05:05.919 align:start position:0% Socrates framework which is kind of 00:05:05.919 --> 00:05:08.250 align:start position:0% Socrates framework which is kind of programming<00:05:06.849> language<00:05:07.210> in<00:05:07.389> school<00:05:07.630> box<00:05:07.840> that 00:05:08.250 --> 00:05:08.260 align:start position:0% programming language in school box that 00:05:08.260 --> 00:05:10.830 align:start position:0% programming language in school box that allows<00:05:08.440> you<00:05:08.710> to<00:05:08.919> easily<00:05:09.580> were<00:05:10.180> boring<00:05:10.479> to<00:05:10.720> be 00:05:10.830 --> 00:05:10.840 align:start position:0% allows you to easily were boring to be 00:05:10.840 --> 00:05:12.089 align:start position:0% allows you to easily were boring to be specified 00:05:12.089 --> 00:05:12.099 align:start position:0% specified 00:05:12.099 --> 00:05:14.520 align:start position:0% specified programs<00:05:12.699> that<00:05:12.910> are<00:05:13.060> provable<00:05:13.479> in<00:05:13.750> CK<00:05:14.169> smarts 00:05:14.520 --> 00:05:14.530 align:start position:0% programs that are provable in CK smarts 00:05:14.530 --> 00:05:17.430 align:start position:0% programs that are provable in CK smarts and<00:05:14.740> verify<00:05:15.490> them<00:05:15.729> conveniently<00:05:16.419> on<00:05:17.139> the 00:05:17.430 --> 00:05:17.440 align:start position:0% and verify them conveniently on the 00:05:17.440 --> 00:05:18.900 align:start position:0% and verify them conveniently on the blockchain<00:05:17.650> what's<00:05:18.190> really<00:05:18.430> interesting<00:05:18.639> to 00:05:18.900 --> 00:05:18.910 align:start position:0% blockchain what's really interesting to 00:05:18.910 --> 00:05:21.870 align:start position:0% blockchain what's really interesting to note<00:05:19.180> here<00:05:19.360> is<00:05:19.630> like<00:05:20.440> me<00:05:20.710> indicated<00:05:21.430> at<00:05:21.520> CK's 00:05:21.870 --> 00:05:21.880 align:start position:0% note here is like me indicated at CK's 00:05:21.880 --> 00:05:23.460 align:start position:0% note here is like me indicated at CK's March<00:05:22.150> than<00:05:22.419> these<00:05:22.599> things<00:05:23.020> that<00:05:23.320> are<00:05:23.440> not 00:05:23.460 --> 00:05:23.470 align:start position:0% March than these things that are not 00:05:23.470 --> 00:05:26.909 align:start position:0% March than these things that are not often<00:05:23.949> categorized<00:05:24.340> as<00:05:24.639> privacy<00:05:24.970> tech<00:05:25.919> we're 00:05:26.909 --> 00:05:26.919 align:start position:0% often categorized as privacy tech we're 00:05:26.919 --> 00:05:29.100 align:start position:0% often categorized as privacy tech we're like<00:05:27.490> privacy<00:05:27.849> was<00:05:28.090> not<00:05:28.270> when<00:05:28.449> the<00:05:28.510> motivation 00:05:29.100 --> 00:05:29.110 align:start position:0% like privacy was not when the motivation 00:05:29.110 --> 00:05:31.050 align:start position:0% like privacy was not when the motivation to<00:05:29.320> do<00:05:29.440> that<00:05:29.470> it<00:05:30.039> was<00:05:30.190> actually<00:05:30.610> scaling 00:05:31.050 --> 00:05:31.060 align:start position:0% to do that it was actually scaling 00:05:31.060 --> 00:05:34.230 align:start position:0% to do that it was actually scaling because<00:05:31.510> the<00:05:32.500> idea<00:05:32.860> was<00:05:32.919> if<00:05:33.370> there<00:05:33.849> is<00:05:33.970> a<00:05:34.000> way 00:05:34.230 --> 00:05:34.240 align:start position:0% because the idea was if there is a way 00:05:34.240 --> 00:05:36.590 align:start position:0% because the idea was if there is a way to<00:05:34.270> verify<00:05:34.750> a<00:05:35.380> very<00:05:35.650> complex 00:05:36.590 --> 00:05:36.600 align:start position:0% to verify a very complex 00:05:36.600 --> 00:05:39.260 align:start position:0% to verify a very complex station<00:05:36.930> with<00:05:37.650> a<00:05:37.920> constant<00:05:38.550> amount<00:05:39.030> of 00:05:39.260 --> 00:05:39.270 align:start position:0% station with a constant amount of 00:05:39.270 --> 00:05:41.750 align:start position:0% station with a constant amount of computational<00:05:40.110> effort<00:05:40.590> and<00:05:40.860> we<00:05:41.250> can<00:05:41.460> do<00:05:41.580> that 00:05:41.750 --> 00:05:41.760 align:start position:0% computational effort and we can do that 00:05:41.760 --> 00:05:44.330 align:start position:0% computational effort and we can do that on<00:05:42.060> the<00:05:42.210> blockchain<00:05:42.420> then<00:05:43.380> we<00:05:43.560> can<00:05:43.740> scale<00:05:43.980> very 00:05:44.330 --> 00:05:44.340 align:start position:0% on the blockchain then we can scale very 00:05:44.340 --> 00:05:46.850 align:start position:0% on the blockchain then we can scale very well<00:05:44.580> so<00:05:44.970> I<00:05:45.000> do<00:05:45.240> three<00:05:45.600> that<00:05:45.840> these<00:05:46.080> things<00:05:46.470> are 00:05:46.850 --> 00:05:46.860 align:start position:0% well so I do three that these things are 00:05:46.860 --> 00:05:49.520 align:start position:0% well so I do three that these things are not<00:05:47.460> opposed<00:05:47.850> at<00:05:48.150> all<00:05:48.300> and<00:05:48.570> if<00:05:48.690> the<00:05:49.050> scaling 00:05:49.520 --> 00:05:49.530 align:start position:0% not opposed at all and if the scaling 00:05:49.530 --> 00:05:50.990 align:start position:0% not opposed at all and if the scaling things<00:05:49.680> will<00:05:49.950> actually<00:05:50.100> brought<00:05:50.610> me<00:05:50.760> there 00:05:50.990 --> 00:05:51.000 align:start position:0% things will actually brought me there 00:05:51.000 --> 00:05:53.690 align:start position:0% things will actually brought me there and<00:05:51.180> now<00:05:51.750> it's<00:05:52.320> also<00:05:52.560> nice<00:05:52.860> to<00:05:52.920> to<00:05:53.460> address 00:05:53.690 --> 00:05:53.700 align:start position:0% and now it's also nice to to address 00:05:53.700 --> 00:05:57.260 align:start position:0% and now it's also nice to to address privacy<00:05:54.620> my<00:05:55.620> take<00:05:55.950> on<00:05:56.160> privacy<00:05:56.760> and<00:05:57.060> security 00:05:57.260 --> 00:05:57.270 align:start position:0% privacy my take on privacy and security 00:05:57.270 --> 00:06:00.200 align:start position:0% privacy my take on privacy and security and<00:05:58.050> how<00:05:58.320> they<00:05:58.500> relate<00:05:58.890> is<00:05:59.100> both<00:05:59.430> are<00:05:59.730> key 00:06:00.200 --> 00:06:00.210 align:start position:0% and how they relate is both are key 00:06:00.210 --> 00:06:02.840 align:start position:0% and how they relate is both are key challenges<00:06:01.200> that<00:06:01.440> need<00:06:02.040> to<00:06:02.190> be<00:06:02.220> addressed<00:06:02.700> for 00:06:02.840 --> 00:06:02.850 align:start position:0% challenges that need to be addressed for 00:06:02.850 --> 00:06:05.150 align:start position:0% challenges that need to be addressed for DES<00:06:03.330> to<00:06:03.630> actually<00:06:04.020> become<00:06:04.320> successful<00:06:04.530> and 00:06:05.150 --> 00:06:05.160 align:start position:0% DES to actually become successful and 00:06:05.160 --> 00:06:07.880 align:start position:0% DES to actually become successful and make<00:06:05.850> mainstream<00:06:06.450> usage<00:06:06.660> because<00:06:07.260> I<00:06:07.290> do<00:06:07.440> think 00:06:07.880 --> 00:06:07.890 align:start position:0% make mainstream usage because I do think 00:06:07.890 --> 00:06:10.280 align:start position:0% make mainstream usage because I do think people<00:06:08.130> will<00:06:08.820> not<00:06:08.970> become<00:06:09.330> comfortable 00:06:10.280 --> 00:06:10.290 align:start position:0% people will not become comfortable 00:06:10.290 --> 00:06:13.480 align:start position:0% people will not become comfortable tweeting<00:06:11.040> not<00:06:11.370> only<00:06:11.760> their<00:06:11.970> financials 00:06:13.480 --> 00:06:13.490 align:start position:0% tweeting not only their financials 00:06:13.490 --> 00:06:15.920 align:start position:0% tweeting not only their financials transactions<00:06:14.490> or<00:06:14.670> web<00:06:14.820> block<00:06:15.060> chains<00:06:15.390> but 00:06:15.920 --> 00:06:15.930 align:start position:0% transactions or web block chains but 00:06:15.930 --> 00:06:18.440 align:start position:0% transactions or web block chains but actually<00:06:16.350> all<00:06:16.860> their<00:06:17.310> interaction<00:06:17.940> with<00:06:18.150> any 00:06:18.440 --> 00:06:18.450 align:start position:0% actually all their interaction with any 00:06:18.450 --> 00:06:21.320 align:start position:0% actually all their interaction with any IT<00:06:18.900> Service<00:06:19.350> over<00:06:19.680> to<00:06:19.800> watching<00:06:20.040> so<00:06:20.700> let's<00:06:20.970> say 00:06:21.320 --> 00:06:21.330 align:start position:0% IT Service over to watching so let's say 00:06:21.330 --> 00:06:23.630 align:start position:0% IT Service over to watching so let's say we<00:06:21.540> solve<00:06:21.780> scaling<00:06:22.350> in<00:06:22.500> a<00:06:22.560> year<00:06:22.830> and<00:06:23.010> drive 00:06:23.630 --> 00:06:23.640 align:start position:0% we solve scaling in a year and drive 00:06:23.640 --> 00:06:25.700 align:start position:0% we solve scaling in a year and drive asou<00:06:23.910> tech<00:06:24.120> does<00:06:24.360> not<00:06:24.510> keep<00:06:24.720> up<00:06:24.930> I<00:06:25.140> don't<00:06:25.290> think 00:06:25.700 --> 00:06:25.710 align:start position:0% asou tech does not keep up I don't think 00:06:25.710 --> 00:06:28.060 align:start position:0% asou tech does not keep up I don't think we<00:06:25.860> will<00:06:26.040> see<00:06:26.100> mainstream<00:06:26.880> adoption<00:06:27.030> off<00:06:27.690> maps 00:06:28.060 --> 00:06:28.070 align:start position:0% we will see mainstream adoption off maps 00:06:28.070 --> 00:06:32.960 align:start position:0% we will see mainstream adoption off maps right<00:06:29.070> so<00:06:29.580> for<00:06:29.760> me<00:06:29.880> it's<00:06:30.060> a<00:06:30.180> key<00:06:30.360> enabler<00:06:31.970> great 00:06:32.960 --> 00:06:32.970 align:start position:0% right so for me it's a key enabler great 00:06:32.970 --> 00:06:35.270 align:start position:0% right so for me it's a key enabler great two<00:06:33.330> things<00:06:33.600> everything<00:06:34.110> else<00:06:34.740> for<00:06:34.980> your 00:06:35.270 --> 00:06:35.280 align:start position:0% two things everything else for your 00:06:35.280 --> 00:06:38.030 align:start position:0% two things everything else for your introductions<00:06:35.880> until<00:06:36.330> we've<00:06:36.870> covered<00:06:37.140> a<00:06:37.470> few 00:06:38.030 --> 00:06:38.040 align:start position:0% introductions until we've covered a few 00:06:38.040 --> 00:06:40.760 align:start position:0% introductions until we've covered a few different<00:06:38.340> things<00:06:38.850> here<00:06:39.690> well<00:06:40.590> actually 00:06:40.760 --> 00:06:40.770 align:start position:0% different things here well actually 00:06:40.770 --> 00:06:42.530 align:start position:0% different things here well actually there's<00:06:41.070> a<00:06:41.130> lot<00:06:41.250> just<00:06:41.490> captured<00:06:41.820> my<00:06:41.940> parents 00:06:42.530 --> 00:06:42.540 align:start position:0% there's a lot just captured my parents 00:06:42.540 --> 00:06:45.290 align:start position:0% there's a lot just captured my parents for<00:06:42.720> statements<00:06:43.260> so<00:06:43.890> um<00:06:44.250> let's<00:06:44.880> talk<00:06:45.060> about 00:06:45.290 --> 00:06:45.300 align:start position:0% for statements so um let's talk about 00:06:45.300 --> 00:06:47.750 align:start position:0% for statements so um let's talk about how<00:06:45.750> things<00:06:45.990> are<00:06:46.350> working<00:06:46.890> now<00:06:47.070> and<00:06:47.310> why<00:06:47.520> we 00:06:47.750 --> 00:06:47.760 align:start position:0% how things are working now and why we 00:06:47.760 --> 00:06:49.610 align:start position:0% how things are working now and why we should<00:06:47.790> why<00:06:48.360> we<00:06:48.510> should<00:06:48.660> care<00:06:48.900> let's<00:06:49.260> dig<00:06:49.470> into 00:06:49.610 --> 00:06:49.620 align:start position:0% should why we should care let's dig into 00:06:49.620 --> 00:06:52.360 align:start position:0% should why we should care let's dig into that<00:06:49.770> a<00:06:49.830> little<00:06:49.980> bit<00:06:50.130> more<00:06:50.510> so<00:06:51.510> right<00:06:51.990> now 00:06:52.360 --> 00:06:52.370 align:start position:0% that a little bit more so right now 00:06:52.370 --> 00:06:54.470 align:start position:0% that a little bit more so right now sometimes<00:06:53.370> projects 00:06:54.470 --> 00:06:54.480 align:start position:0% sometimes projects 00:06:54.480 --> 00:06:56.270 align:start position:0% sometimes projects in<00:06:54.570> space<00:06:55.170> that<00:06:55.410> it's<00:06:55.560> more<00:06:55.740> important<00:06:56.040> sauce 00:06:56.270 --> 00:06:56.280 align:start position:0% in space that it's more important sauce 00:06:56.280 --> 00:06:58.160 align:start position:0% in space that it's more important sauce and<00:06:56.550> technical<00:06:56.910> problems<00:06:57.390> to<00:06:57.540> solve<00:06:57.750> like<00:06:58.020> you 00:06:58.160 --> 00:06:58.170 align:start position:0% and technical problems to solve like you 00:06:58.170 --> 00:07:00.320 align:start position:0% and technical problems to solve like you know<00:06:58.230> use<00:06:58.500> case<00:06:58.740> problem<00:06:59.160> and<00:06:59.640> well<00:06:59.820> they<00:07:00.180> are 00:07:00.320 --> 00:07:00.330 align:start position:0% know use case problem and well they are 00:07:00.330 --> 00:07:04.250 align:start position:0% know use case problem and well they are privacy<00:07:00.750> on<00:07:00.990> top<00:07:01.230> later<00:07:01.640> or<00:07:02.640> that<00:07:03.330> yeah<00:07:03.870> that 00:07:04.250 --> 00:07:04.260 align:start position:0% privacy on top later or that yeah that 00:07:04.260 --> 00:07:06.650 align:start position:0% privacy on top later or that yeah that let's<00:07:04.920> get<00:07:05.160> the<00:07:05.280> scaling<00:07:05.700> first<00:07:06.120> and<00:07:06.540> then 00:07:06.650 --> 00:07:06.660 align:start position:0% let's get the scaling first and then 00:07:06.660 --> 00:07:08.600 align:start position:0% let's get the scaling first and then we'll<00:07:06.870> do<00:07:07.020> the<00:07:07.140> privacy<00:07:07.620> part<00:07:07.890> because<00:07:08.280> you 00:07:08.600 --> 00:07:08.610 align:start position:0% we'll do the privacy part because you 00:07:08.610 --> 00:07:10.760 align:start position:0% we'll do the privacy part because you know<00:07:08.730> there's<00:07:09.060> not<00:07:09.360> that<00:07:09.600> much<00:07:09.810> we<00:07:10.500> shouldn't 00:07:10.760 --> 00:07:10.770 align:start position:0% know there's not that much we shouldn't 00:07:10.770 --> 00:07:12.800 align:start position:0% know there's not that much we shouldn't be<00:07:10.830> too<00:07:10.980> worried<00:07:11.240> so<00:07:12.240> let's<00:07:12.420> talk<00:07:12.510> a<00:07:12.570> little 00:07:12.800 --> 00:07:12.810 align:start position:0% be too worried so let's talk a little 00:07:12.810 --> 00:07:16.670 align:start position:0% be too worried so let's talk a little bit<00:07:12.960> about<00:07:12.990> maybe<00:07:13.920> what<00:07:14.700> is<00:07:15.470> what<00:07:16.470> is<00:07:16.500> the 00:07:16.670 --> 00:07:16.680 align:start position:0% bit about maybe what is what is the 00:07:16.680 --> 00:07:19.370 align:start position:0% bit about maybe what is what is the concern<00:07:17.070> right<00:07:17.310> now<00:07:17.370> with<00:07:18.150> the<00:07:18.810> technology 00:07:19.370 --> 00:07:19.380 align:start position:0% concern right now with the technology 00:07:19.380 --> 00:07:22.250 align:start position:0% concern right now with the technology that's<00:07:19.560> being<00:07:19.710> used<00:07:20.100> and<00:07:20.550> how<00:07:20.970> is<00:07:21.420> it<00:07:21.570> not<00:07:21.840> good 00:07:22.250 --> 00:07:22.260 align:start position:0% that's being used and how is it not good 00:07:22.260 --> 00:07:24.350 align:start position:0% that's being used and how is it not good for<00:07:22.440> privacy<00:07:22.920> now<00:07:23.100> and<00:07:23.370> how<00:07:23.460> this<00:07:23.730> could<00:07:24.000> scale 00:07:24.350 --> 00:07:24.360 align:start position:0% for privacy now and how this could scale 00:07:24.360 --> 00:07:26.030 align:start position:0% for privacy now and how this could scale up<00:07:24.540> and<00:07:24.780> it's<00:07:24.900> beast<00:07:25.140> think<00:07:25.440> maker<00:07:25.650> in<00:07:25.950> the 00:07:26.030 --> 00:07:26.040 align:start position:0% up and it's beast think maker in the 00:07:26.040 --> 00:07:39.650 align:start position:0% up and it's beast think maker in the future<00:07:36.440> so<00:07:37.440> I<00:07:37.770> mean<00:07:38.250> the<00:07:38.910> way<00:07:39.060> it<00:07:39.120> works<00:07:39.360> now 00:07:39.650 --> 00:07:39.660 align:start position:0% future so I mean the way it works now 00:07:39.660 --> 00:07:41.480 align:start position:0% future so I mean the way it works now for<00:07:39.690> anyone<00:07:40.170> that<00:07:40.380> is<00:07:40.620> I'm<00:07:41.040> going<00:07:41.190> to<00:07:41.250> use<00:07:41.310> this 00:07:41.480 --> 00:07:41.490 align:start position:0% for anyone that is I'm going to use this 00:07:41.490 --> 00:07:44.630 align:start position:0% for anyone that is I'm going to use this material<00:07:42.590> or<00:07:43.590> many<00:07:44.250> other<00:07:44.460> people 00:07:44.630 --> 00:07:44.640 align:start position:0% material or many other people 00:07:44.640 --> 00:07:46.220 align:start position:0% material or many other people differently<00:07:45.450> actually<00:07:45.930> you<00:07:46.050> have<00:07:46.200> a 00:07:46.220 --> 00:07:46.230 align:start position:0% differently actually you have a 00:07:46.230 --> 00:07:49.850 align:start position:0% differently actually you have a procedure<00:07:46.580> they<00:07:47.580> use<00:07:47.970> it<00:07:48.150> now<00:07:48.410> it<00:07:49.410> is<00:07:49.560> that 00:07:49.850 --> 00:07:49.860 align:start position:0% procedure they use it now it is that 00:07:49.860 --> 00:07:52.310 align:start position:0% procedure they use it now it is that they<00:07:50.730> use<00:07:50.880> working<00:07:51.450> the<00:07:51.510> system<00:07:51.750> that 00:07:52.310 --> 00:07:52.320 align:start position:0% they use working the system that 00:07:52.320 --> 00:07:53.090 align:start position:0% they use working the system that effectively 00:07:53.090 --> 00:07:53.100 align:start position:0% effectively 00:07:53.100 --> 00:07:55.820 align:start position:0% effectively Peet's<00:07:53.760> the<00:07:54.090> transaction<00:07:54.720> graph<00:07:54.870> for<00:07:55.350> anybody 00:07:55.820 --> 00:07:55.830 align:start position:0% Peet's the transaction graph for anybody 00:07:55.830 --> 00:08:01.070 align:start position:0% Peet's the transaction graph for anybody to<00:07:56.040> see<00:07:56.250> and<00:07:57.080> it<00:07:58.080> only<00:07:58.260> takes<00:07:58.680> like<00:07:59.130> one<00:08:00.080> short 00:08:01.070 --> 00:08:01.080 align:start position:0% to see and it only takes like one short 00:08:01.080 --> 00:08:03.410 align:start position:0% to see and it only takes like one short conversation<00:08:01.860> with<00:08:01.890> a<00:08:02.160> watching<00:08:02.850> analytics 00:08:03.410 --> 00:08:03.420 align:start position:0% conversation with a watching analytics 00:08:03.420 --> 00:08:06.680 align:start position:0% conversation with a watching analytics firm<00:08:03.780> to<00:08:04.350> realize<00:08:04.890> that<00:08:05.430> this<00:08:05.880> system<00:08:06.330> as<00:08:06.510> it 00:08:06.680 --> 00:08:06.690 align:start position:0% firm to realize that this system as it 00:08:06.690 --> 00:08:09.200 align:start position:0% firm to realize that this system as it exists<00:08:07.140> today<00:08:07.200> it<00:08:07.770> within<00:08:08.400> all<00:08:08.670> of<00:08:09.000> these 00:08:09.200 --> 00:08:09.210 align:start position:0% exists today it within all of these 00:08:09.210 --> 00:08:12.620 align:start position:0% exists today it within all of these projects<00:08:09.780> is<00:08:10.460> measurably<00:08:11.460> worse<00:08:12.030> than<00:08:12.510> the 00:08:12.620 --> 00:08:12.630 align:start position:0% projects is measurably worse than the 00:08:12.630 --> 00:08:16.310 align:start position:0% projects is measurably worse than the patchwork<00:08:12.990> of<00:08:13.620> offline<00:08:14.490> cash<00:08:15.320> transactions 00:08:16.310 --> 00:08:16.320 align:start position:0% patchwork of offline cash transactions 00:08:16.320 --> 00:08:18.380 align:start position:0% patchwork of offline cash transactions and<00:08:16.590> various<00:08:17.430> financial<00:08:17.820> intermediaries 00:08:18.380 --> 00:08:18.390 align:start position:0% and various financial intermediaries 00:08:18.390 --> 00:08:20.020 align:start position:0% and various financial intermediaries that<00:08:18.540> actually<00:08:18.900> do<00:08:19.080> have<00:08:19.260> some<00:08:19.500> degree<00:08:19.590> of 00:08:20.020 --> 00:08:20.030 align:start position:0% that actually do have some degree of 00:08:20.030 --> 00:08:23.630 align:start position:0% that actually do have some degree of privacy<00:08:21.030> guarantees<00:08:22.160> and<00:08:23.160> the<00:08:23.190> way<00:08:23.370> they<00:08:23.490> the 00:08:23.630 --> 00:08:23.640 align:start position:0% privacy guarantees and the way they the 00:08:23.640 --> 00:08:24.380 align:start position:0% privacy guarantees and the way they the way<00:08:23.760> works<00:08:24.000> today 00:08:24.380 --> 00:08:24.390 align:start position:0% way works today 00:08:24.390 --> 00:08:27.800 align:start position:0% way works today so<00:08:24.540> I<00:08:24.810> think<00:08:25.680> we<00:08:26.340> can<00:08:26.490> all<00:08:26.670> hang<00:08:26.880> universally 00:08:27.800 --> 00:08:27.810 align:start position:0% so I think we can all hang universally 00:08:27.810 --> 00:08:30.560 align:start position:0% so I think we can all hang universally agree<00:08:28.140> that<00:08:28.380> like<00:08:28.590> these<00:08:29.400> systems<00:08:29.970> need<00:08:30.300> to 00:08:30.560 --> 00:08:30.570 align:start position:0% agree that like these systems need to 00:08:30.570 --> 00:08:33.110 align:start position:0% agree that like these systems need to need<00:08:31.110> to<00:08:31.140> change<00:08:31.620> in<00:08:32.430> order<00:08:32.490> for<00:08:32.940> us<00:08:32.970> to 00:08:33.110 --> 00:08:33.120 align:start position:0% need to change in order for us to 00:08:33.120 --> 00:08:37.040 align:start position:0% need to change in order for us to actually<00:08:34.040> feel<00:08:35.040> comfortable<00:08:35.700> using<00:08:36.210> them 00:08:37.040 --> 00:08:37.050 align:start position:0% actually feel comfortable using them 00:08:37.050 --> 00:08:39.050 align:start position:0% actually feel comfortable using them and<00:08:37.140> I<00:08:37.290> don't<00:08:37.350> know<00:08:37.590> day<00:08:37.980> to<00:08:38.010> day<00:08:38.310> and<00:08:38.490> a<00:08:38.790> broad 00:08:39.050 --> 00:08:39.060 align:start position:0% and I don't know day to day and a broad 00:08:39.060 --> 00:08:40.970 align:start position:0% and I don't know day to day and a broad basis<00:08:39.540> because<00:08:39.780> otherwise<00:08:39.960> it's<00:08:40.650> gonna<00:08:40.740> learn 00:08:40.970 --> 00:08:40.980 align:start position:0% basis because otherwise it's gonna learn 00:08:40.980 --> 00:08:43.270 align:start position:0% basis because otherwise it's gonna learn that<00:08:41.010> happening<00:08:41.700> is<00:08:41.850> we're<00:08:42.690> going<00:08:42.840> to 00:08:43.270 --> 00:08:43.280 align:start position:0% that happening is we're going to 00:08:43.280 --> 00:08:45.770 align:start position:0% that happening is we're going to recreate<00:08:44.280> this<00:08:44.550> brand-new<00:08:44.970> financial<00:08:45.450> system 00:08:45.770 --> 00:08:45.780 align:start position:0% recreate this brand-new financial system 00:08:45.780 --> 00:08:46.940 align:start position:0% recreate this brand-new financial system but<00:08:45.930> then<00:08:46.050> people<00:08:46.380> actually<00:08:46.590> feel 00:08:46.940 --> 00:08:46.950 align:start position:0% but then people actually feel 00:08:46.950 --> 00:08:49.580 align:start position:0% but then people actually feel comfortable<00:08:47.400> using<00:08:47.580> gaps<00:08:48.290> because<00:08:49.290> they'll 00:08:49.580 --> 00:08:49.590 align:start position:0% comfortable using gaps because they'll 00:08:49.590 --> 00:08:52.820 align:start position:0% comfortable using gaps because they'll know<00:08:49.800> that<00:08:49.830> all<00:08:50.580> the<00:08:50.820> data<00:08:51.000> can<00:08:51.240> be<00:08:51.470> traced<00:08:52.470> and 00:08:52.820 --> 00:08:52.830 align:start position:0% know that all the data can be traced and 00:08:52.830 --> 00:08:56.240 align:start position:0% know that all the data can be traced and open<00:08:53.220> for<00:08:53.520> their<00:08:54.270> competitors<00:08:54.870> to<00:08:54.900> see<00:08:55.470> people 00:08:56.240 --> 00:08:56.250 align:start position:0% open for their competitors to see people 00:08:56.250 --> 00:08:58.310 align:start position:0% open for their competitors to see people won't<00:08:56.520> actually<00:08:56.700> engaging<00:08:57.360> in<00:08:57.750> any<00:08:57.990> crypto 00:08:58.310 --> 00:08:58.320 align:start position:0% won't actually engaging in any crypto 00:08:58.320 --> 00:09:00.020 align:start position:0% won't actually engaging in any crypto currency<00:08:58.770> transactions<00:08:59.370> because<00:08:59.580> they<00:08:59.850> know 00:09:00.020 --> 00:09:00.030 align:start position:0% currency transactions because they know 00:09:00.030 --> 00:09:04.220 align:start position:0% currency transactions because they know that<00:09:01.010> companies<00:09:02.010> and<00:09:03.080> governments<00:09:04.080> will<00:09:04.200> be 00:09:04.220 --> 00:09:04.230 align:start position:0% that companies and governments will be 00:09:04.230 --> 00:09:06.560 align:start position:0% that companies and governments will be surveilling<00:09:04.650> earlier<00:09:05.160> and<00:09:06.120> that's<00:09:06.300> like<00:09:06.450> a 00:09:06.560 --> 00:09:06.570 align:start position:0% surveilling earlier and that's like a 00:09:06.570 --> 00:09:08.740 align:start position:0% surveilling earlier and that's like a very<00:09:06.780> frightening<00:09:07.290> thought 00:09:08.740 --> 00:09:08.750 align:start position:0% very frightening thought 00:09:08.750 --> 00:09:11.560 align:start position:0% very frightening thought so<00:09:09.750> I<00:09:09.780> like<00:09:10.350> how<00:09:10.500> you<00:09:10.560> fix<00:09:10.920> that 00:09:11.560 --> 00:09:11.570 align:start position:0% so I like how you fix that 00:09:11.570 --> 00:09:14.450 align:start position:0% so I like how you fix that Tomita<00:09:12.570> to<00:09:12.840> smart<00:09:13.470> people<00:09:13.800> to<00:09:13.890> figure<00:09:14.130> that 00:09:14.450 --> 00:09:14.460 align:start position:0% Tomita to smart people to figure that 00:09:14.460 --> 00:09:17.000 align:start position:0% Tomita to smart people to figure that out<00:09:14.640> but<00:09:14.880> I<00:09:15.420> mean<00:09:15.720> one<00:09:16.290> of<00:09:16.320> the<00:09:16.470> ways<00:09:16.590> to<00:09:16.620> do<00:09:16.890> is 00:09:17.000 --> 00:09:17.010 align:start position:0% out but I mean one of the ways to do is 00:09:17.010 --> 00:09:19.820 align:start position:0% out but I mean one of the ways to do is to<00:09:17.190> figure<00:09:17.310> out<00:09:17.550> how<00:09:18.120> many<00:09:18.180> I<00:09:18.780> need<00:09:19.290> sanitize 00:09:19.820 --> 00:09:19.830 align:start position:0% to figure out how many I need sanitize 00:09:19.830 --> 00:09:22.790 align:start position:0% to figure out how many I need sanitize privacy<00:09:20.820> on<00:09:21.540> this<00:09:21.750> chain<00:09:22.050> right<00:09:22.470> how<00:09:22.680> do<00:09:22.740> we 00:09:22.790 --> 00:09:22.800 align:start position:0% privacy on this chain right how do we 00:09:22.800 --> 00:09:25.190 align:start position:0% privacy on this chain right how do we get<00:09:23.040> people<00:09:23.250> to<00:09:23.460> actually<00:09:23.700> say<00:09:24.690> that<00:09:24.930> there's 00:09:25.190 --> 00:09:25.200 align:start position:0% get people to actually say that there's 00:09:25.200 --> 00:09:29.540 align:start position:0% get people to actually say that there's it's<00:09:25.820> cheaper<00:09:26.820> to<00:09:27.720> do<00:09:27.870> this<00:09:28.250> various<00:09:29.250> chains 00:09:29.540 --> 00:09:29.550 align:start position:0% it's cheaper to do this various chains 00:09:29.550 --> 00:09:32.540 align:start position:0% it's cheaper to do this various chains and<00:09:30.180> socially<00:09:30.870> how<00:09:31.140> do<00:09:31.200> we<00:09:31.320> connect<00:09:31.770> the 00:09:32.540 --> 00:09:32.550 align:start position:0% and socially how do we connect the 00:09:32.550 --> 00:09:35.420 align:start position:0% and socially how do we connect the really<00:09:33.330> saw<00:09:33.900> the<00:09:33.960> disconnects<00:09:34.830> that<00:09:34.950> people 00:09:35.420 --> 00:09:35.430 align:start position:0% really saw the disconnects that people 00:09:35.430 --> 00:09:38.210 align:start position:0% really saw the disconnects that people have<00:09:35.700> of<00:09:36.330> like<00:09:36.540> great<00:09:36.780> right<00:09:37.110> now<00:09:37.410> we<00:09:37.740> talked 00:09:38.210 --> 00:09:38.220 align:start position:0% have of like great right now we talked 00:09:38.220 --> 00:09:39.340 align:start position:0% have of like great right now we talked about<00:09:38.250> this<00:09:38.550> before 00:09:39.340 --> 00:09:39.350 align:start position:0% about this before 00:09:39.350 --> 00:09:42.230 align:start position:0% about this before Elizabeth<00:09:40.350> McGlynn<00:09:40.740> when<00:09:41.430> people<00:09:41.790> interact 00:09:42.230 --> 00:09:42.240 align:start position:0% Elizabeth McGlynn when people interact 00:09:42.240 --> 00:09:43.850 align:start position:0% Elizabeth McGlynn when people interact and<00:09:42.420> buy<00:09:42.630> something<00:09:43.050> online<00:09:43.230> at<00:09:43.440> their<00:09:43.590> credit 00:09:43.850 --> 00:09:43.860 align:start position:0% and buy something online at their credit 00:09:43.860 --> 00:09:45.710 align:start position:0% and buy something online at their credit card<00:09:44.100> or<00:09:44.280> use<00:09:44.550> music<00:09:45.270> rip<00:09:45.390> to<00:09:45.480> currency 00:09:45.710 --> 00:09:45.720 align:start position:0% card or use music rip to currency 00:09:45.720 --> 00:09:48.410 align:start position:0% card or use music rip to currency without<00:09:45.900> any<00:09:46.170> kind<00:09:46.560> of<00:09:46.650> protection<00:09:47.240> the<00:09:48.240> only 00:09:48.410 --> 00:09:48.420 align:start position:0% without any kind of protection the only 00:09:48.420 --> 00:09:50.720 align:start position:0% without any kind of protection the only they<00:09:48.780> don't<00:09:48.900> really<00:09:48.990> think<00:09:49.290> about<00:09:49.670> how<00:09:50.670> many 00:09:50.720 --> 00:09:50.730 align:start position:0% they don't really think about how many 00:09:50.730 --> 00:09:52.790 align:start position:0% they don't really think about how many people<00:09:51.330> can<00:09:51.570> actually<00:09:51.810> surveil<00:09:52.590> and 00:09:52.790 --> 00:09:52.800 align:start position:0% people can actually surveil and 00:09:52.800 --> 00:09:56.240 align:start position:0% people can actually surveil and understand<00:09:53.190> the<00:09:53.550> data<00:09:53.790> as<00:09:54.240> being<00:09:54.830> sold<00:09:55.830> on 00:09:56.240 --> 00:09:56.250 align:start position:0% understand the data as being sold on 00:09:56.250 --> 00:09:57.680 align:start position:0% understand the data as being sold on their<00:09:56.430> behalf<00:09:56.730> or<00:09:57.000> observed<00:09:57.330> and<00:09:57.570> their 00:09:57.680 --> 00:09:57.690 align:start position:0% their behalf or observed and their 00:09:57.690 --> 00:09:58.250 align:start position:0% their behalf or observed and their behalf 00:09:58.250 --> 00:09:58.260 align:start position:0% behalf 00:09:58.260 --> 00:09:59.630 align:start position:0% behalf they<00:09:58.380> can<00:09:58.500> you<00:09:58.590> imagine<00:09:58.740> going<00:09:59.250> into<00:09:59.430> a 00:09:59.630 --> 00:09:59.640 align:start position:0% they can you imagine going into a 00:09:59.640 --> 00:10:02.810 align:start position:0% they can you imagine going into a stories<00:10:00.120> and<00:10:00.300> casually<00:10:00.810> buy<00:10:00.990> a<00:10:01.020> newspaper<00:10:01.820> the 00:10:02.810 --> 00:10:02.820 align:start position:0% stories and casually buy a newspaper the 00:10:02.820 --> 00:10:04.850 align:start position:0% stories and casually buy a newspaper the online<00:10:03.360> equivalent<00:10:03.600> their<00:10:03.990> glyph<00:10:04.200> 30<00:10:04.590> people 00:10:04.850 --> 00:10:04.860 align:start position:0% online equivalent their glyph 30 people 00:10:04.860 --> 00:10:06.830 align:start position:0% online equivalent their glyph 30 people in<00:10:05.010> the<00:10:05.040> room<00:10:05.100> watching<00:10:05.730> you<00:10:06.090> do<00:10:06.360> that<00:10:06.600> and 00:10:06.830 --> 00:10:06.840 align:start position:0% in the room watching you do that and 00:10:06.840 --> 00:10:10.310 align:start position:0% in the room watching you do that and then<00:10:07.470> taking<00:10:08.040> notes<00:10:08.280> and<00:10:08.700> then<00:10:09.420> recommending 00:10:10.310 --> 00:10:10.320 align:start position:0% then taking notes and then recommending 00:10:10.320 --> 00:10:12.500 align:start position:0% then taking notes and then recommending other<00:10:10.440> newspapers<00:10:11.010> really<00:10:11.370> buy<00:10:11.550> while<00:10:12.180> your 00:10:12.500 --> 00:10:12.510 align:start position:0% other newspapers really buy while your 00:10:12.510 --> 00:10:14.180 align:start position:0% other newspapers really buy while your process<00:10:13.320> of<00:10:13.410> doing<00:10:13.530> that<00:10:13.800> and<00:10:13.950> most<00:10:14.100> people 00:10:14.180 --> 00:10:14.190 align:start position:0% process of doing that and most people 00:10:14.190 --> 00:10:15.950 align:start position:0% process of doing that and most people don't<00:10:14.460> view<00:10:14.700> it<00:10:14.760> that<00:10:14.970> way<00:10:15.180> so<00:10:15.630> if<00:10:15.750> you<00:10:15.780> have<00:10:15.930> a 00:10:15.950 --> 00:10:15.960 align:start position:0% don't view it that way so if you have a 00:10:15.960 --> 00:10:17.540 align:start position:0% don't view it that way so if you have a big<00:10:16.170> social<00:10:16.560> challenge<00:10:17.160> in<00:10:17.310> terms<00:10:17.400> of 00:10:17.540 --> 00:10:17.550 align:start position:0% big social challenge in terms of 00:10:17.550 --> 00:10:22.070 align:start position:0% big social challenge in terms of convincing<00:10:18.030> people<00:10:18.090> that<00:10:18.450> that<00:10:19.110> is<00:10:19.290> I<00:10:21.020> want<00:10:22.020> to 00:10:22.070 --> 00:10:22.080 align:start position:0% convincing people that that is I want to 00:10:22.080 --> 00:10:24.560 align:start position:0% convincing people that that is I want to just<00:10:22.710> sort<00:10:22.860> of<00:10:22.950> take<00:10:23.640> issue<00:10:23.940> with<00:10:24.120> the 00:10:24.560 --> 00:10:24.570 align:start position:0% just sort of take issue with the 00:10:24.570 --> 00:10:27.650 align:start position:0% just sort of take issue with the approach<00:10:25.230> of<00:10:25.460> which<00:10:26.460> you<00:10:26.940> talked<00:10:27.180> about<00:10:27.300> that 00:10:27.650 --> 00:10:27.660 align:start position:0% approach of which you talked about that 00:10:27.660 --> 00:10:31.220 align:start position:0% approach of which you talked about that obviously<00:10:28.440> weren't<00:10:28.620> suggesting<00:10:29.450> that<00:10:30.450> we'll 00:10:31.220 --> 00:10:31.230 align:start position:0% obviously weren't suggesting that we'll 00:10:31.230 --> 00:10:33.140 align:start position:0% obviously weren't suggesting that we'll just<00:10:31.260> build<00:10:31.620> a<00:10:31.800> thing<00:10:31.950> first<00:10:32.280> and<00:10:32.520> then<00:10:32.880> we 00:10:33.140 --> 00:10:33.150 align:start position:0% just build a thing first and then we 00:10:33.150 --> 00:10:34.170 align:start position:0% just build a thing first and then we will<00:10:33.420> figure<00:10:33.840> out 00:10:34.170 --> 00:10:34.180 align:start position:0% will figure out 00:10:34.180 --> 00:10:37.020 align:start position:0% will figure out privacy<00:10:35.080> later<00:10:35.430> because<00:10:36.430> if<00:10:36.700> you<00:10:36.820> say<00:10:37.000> that 00:10:37.020 --> 00:10:37.030 align:start position:0% privacy later because if you say that 00:10:37.030 --> 00:10:39.450 align:start position:0% privacy later because if you say that what<00:10:37.420> you're<00:10:37.540> essentially<00:10:37.930> saying<00:10:38.350> is<00:10:38.800> we're 00:10:39.450 --> 00:10:39.460 align:start position:0% what you're essentially saying is we're 00:10:39.460 --> 00:10:41.430 align:start position:0% what you're essentially saying is we're going<00:10:39.580> to<00:10:39.640> design<00:10:39.850> a<00:10:40.090> system<00:10:40.300> in<00:10:40.840> a<00:10:40.930> particular 00:10:41.430 --> 00:10:41.440 align:start position:0% going to design a system in a particular 00:10:41.440 --> 00:10:43.860 align:start position:0% going to design a system in a particular way<00:10:41.650> and<00:10:41.890> once<00:10:42.790> we've<00:10:42.970> invested<00:10:43.480> a<00:10:43.510> lot<00:10:43.750> of 00:10:43.860 --> 00:10:43.870 align:start position:0% way and once we've invested a lot of 00:10:43.870 --> 00:10:45.420 align:start position:0% way and once we've invested a lot of engineering<00:10:44.410> effort<00:10:44.530> and<00:10:44.860> we<00:10:44.980> have<00:10:45.130> a<00:10:45.160> big 00:10:45.420 --> 00:10:45.430 align:start position:0% engineering effort and we have a big 00:10:45.430 --> 00:10:47.400 align:start position:0% engineering effort and we have a big installed<00:10:45.880> base<00:10:46.150> then<00:10:46.900> we're<00:10:47.170> going<00:10:47.380> to 00:10:47.400 --> 00:10:47.410 align:start position:0% installed base then we're going to 00:10:47.410 --> 00:10:50.340 align:start position:0% installed base then we're going to fundamentally<00:10:48.040> redesign<00:10:48.520> it<00:10:49.110> that's<00:10:50.110> not 00:10:50.340 --> 00:10:50.350 align:start position:0% fundamentally redesign it that's not 00:10:50.350 --> 00:10:52.620 align:start position:0% fundamentally redesign it that's not gonna<00:10:50.500> work<00:10:50.650> if<00:10:51.460> you<00:10:51.730> don't<00:10:51.880> start<00:10:52.270> out<00:10:52.420> with 00:10:52.620 --> 00:10:52.630 align:start position:0% gonna work if you don't start out with 00:10:52.630 --> 00:10:54.240 align:start position:0% gonna work if you don't start out with privacy<00:10:53.020> of<00:10:53.260> mine<00:10:53.440> if<00:10:53.620> you<00:10:53.680> don't<00:10:53.860> start<00:10:54.100> out 00:10:54.240 --> 00:10:54.250 align:start position:0% privacy of mine if you don't start out 00:10:54.250 --> 00:10:56.460 align:start position:0% privacy of mine if you don't start out these<00:10:54.520> thinking<00:10:54.970> about<00:10:55.270> what<00:10:55.900> your<00:10:56.020> privacy 00:10:56.460 --> 00:10:56.470 align:start position:0% these thinking about what your privacy 00:10:56.470 --> 00:10:58.440 align:start position:0% these thinking about what your privacy strategy<00:10:56.980> is<00:10:57.040> going<00:10:57.280> to<00:10:57.430> be<00:10:57.610> and<00:10:57.880> at<00:10:58.180> the<00:10:58.300> very 00:10:58.440 --> 00:10:58.450 align:start position:0% strategy is going to be and at the very 00:10:58.450 --> 00:11:00.450 align:start position:0% strategy is going to be and at the very least<00:10:58.810> not<00:10:58.990> engineering<00:10:59.920> in<00:11:00.010> a<00:11:00.100> way<00:11:00.220> that's 00:11:00.450 --> 00:11:00.460 align:start position:0% least not engineering in a way that's 00:11:00.460 --> 00:11:02.670 align:start position:0% least not engineering in a way that's inconsistent<00:11:01.060> with<00:11:01.330> that<00:11:01.630> strategy<00:11:01.900> you're 00:11:02.670 --> 00:11:02.680 align:start position:0% inconsistent with that strategy you're 00:11:02.680 --> 00:11:04.920 align:start position:0% inconsistent with that strategy you're gonna<00:11:02.770> find<00:11:03.070> yourself<00:11:03.220> locked<00:11:03.730> in<00:11:04.060> to<00:11:04.450> a 00:11:04.920 --> 00:11:04.930 align:start position:0% gonna find yourself locked in to a 00:11:04.930 --> 00:11:08.400 align:start position:0% gonna find yourself locked in to a design<00:11:05.620> later<00:11:05.950> that<00:11:06.340> is<00:11:06.610> very<00:11:07.000> difficult<00:11:07.540> from 00:11:08.400 --> 00:11:08.410 align:start position:0% design later that is very difficult from 00:11:08.410 --> 00:11:11.810 align:start position:0% design later that is very difficult from a<00:11:08.440> privacy<00:11:08.830> standpoint<00:11:09.160> just<00:11:10.770> apathetic 00:11:11.810 --> 00:11:11.820 align:start position:0% a privacy standpoint just apathetic 00:11:11.820 --> 00:11:14.760 align:start position:0% a privacy standpoint just apathetic continue<00:11:12.820> to<00:11:12.940> think<00:11:13.270> that<00:11:14.140> you<00:11:14.290> don't<00:11:14.500> need 00:11:14.760 --> 00:11:14.770 align:start position:0% continue to think that you don't need 00:11:14.770 --> 00:11:16.950 align:start position:0% continue to think that you don't need privacy<00:11:15.010> if<00:11:15.430> you're<00:11:15.580> not<00:11:15.730> doing<00:11:15.940> pass<00:11:16.300> so 00:11:16.950 --> 00:11:16.960 align:start position:0% privacy if you're not doing pass so 00:11:16.960 --> 00:11:19.020 align:start position:0% privacy if you're not doing pass so actually<00:11:17.230> Josh<00:11:17.800> you<00:11:18.070> want<00:11:18.250> me<00:11:18.640> to<00:11:18.790> give<00:11:18.910> the 00:11:19.020 --> 00:11:19.030 align:start position:0% actually Josh you want me to give the 00:11:19.030 --> 00:11:21.090 align:start position:0% actually Josh you want me to give the first<00:11:19.240> answer<00:11:19.660> I<00:11:19.930> think<00:11:20.320> you<00:11:20.440> expected<00:11:20.950> me<00:11:21.070> to 00:11:21.090 --> 00:11:21.100 align:start position:0% first answer I think you expected me to 00:11:21.100 --> 00:11:23.160 align:start position:0% first answer I think you expected me to give<00:11:21.310> the<00:11:21.460> standards<00:11:21.970> feel<00:11:22.270> like<00:11:22.540> it<00:11:22.720> though 00:11:23.160 --> 00:11:23.170 align:start position:0% give the standards feel like it though 00:11:23.170 --> 00:11:26.280 align:start position:0% give the standards feel like it though well<00:11:23.680> we<00:11:23.860> can't<00:11:24.130> do<00:11:24.310> it<00:11:24.430> even<00:11:24.870> than<00:11:25.870> Republic 00:11:26.280 --> 00:11:26.290 align:start position:0% well we can't do it even than Republic 00:11:26.290 --> 00:11:27.660 align:start position:0% well we can't do it even than Republic it's<00:11:26.440> Twitter<00:11:26.680> for<00:11:26.860> your<00:11:26.950> bank<00:11:27.130> account<00:11:27.460> you 00:11:27.660 --> 00:11:27.670 align:start position:0% it's Twitter for your bank account you 00:11:27.670 --> 00:11:29.520 align:start position:0% it's Twitter for your bank account you you<00:11:28.060> could<00:11:28.240> stock<00:11:28.510> whether<00:11:28.780> ex<00:11:28.990> girlfriend<00:11:29.440> or 00:11:29.520 --> 00:11:29.530 align:start position:0% you could stock whether ex girlfriend or 00:11:29.530 --> 00:11:31.320 align:start position:0% you could stock whether ex girlfriend or boyfriend<00:11:29.560> your<00:11:30.430> business<00:11:30.730> competitors<00:11:31.180> will 00:11:31.320 --> 00:11:31.330 align:start position:0% boyfriend your business competitors will 00:11:31.330 --> 00:11:32.700 align:start position:0% boyfriend your business competitors will see<00:11:31.450> what<00:11:31.540> you're<00:11:31.690> doing<00:11:31.990> foreign 00:11:32.700 --> 00:11:32.710 align:start position:0% see what you're doing foreign 00:11:32.710 --> 00:11:33.660 align:start position:0% see what you're doing foreign governments<00:11:33.220> use<00:11:33.400> it<00:11:33.550> for 00:11:33.660 --> 00:11:33.670 align:start position:0% governments use it for 00:11:33.670 --> 00:11:36.030 align:start position:0% governments use it for counterintelligence<00:11:34.120> this<00:11:34.660> is<00:11:34.840> a<00:11:35.110> rant<00:11:35.860> I 00:11:36.030 --> 00:11:36.040 align:start position:0% counterintelligence this is a rant I 00:11:36.040 --> 00:11:38.850 align:start position:0% counterintelligence this is a rant I think<00:11:36.250> for<00:11:36.610> 20<00:11:36.880> minutes<00:11:37.150> but<00:11:37.960> it's<00:11:38.290> tempting<00:11:38.650> I 00:11:38.850 --> 00:11:38.860 align:start position:0% think for 20 minutes but it's tempting I 00:11:38.860 --> 00:11:40.380 align:start position:0% think for 20 minutes but it's tempting I think<00:11:39.100> particularly<00:11:39.430> for<00:11:39.580> this<00:11:39.820> audience<00:11:40.150> to 00:11:40.380 --> 00:11:40.390 align:start position:0% think particularly for this audience to 00:11:40.390 --> 00:11:42.540 align:start position:0% think particularly for this audience to go<00:11:40.510> well<00:11:40.780> if<00:11:41.200> I'm<00:11:41.380> not<00:11:41.410> doing<00:11:41.830> the<00:11:41.890> payments<00:11:42.400> if 00:11:42.540 --> 00:11:42.550 align:start position:0% go well if I'm not doing the payments if 00:11:42.550 --> 00:11:44.550 align:start position:0% go well if I'm not doing the payments if I'm<00:11:42.700> doing<00:11:43.030> crypto<00:11:43.510> kitty<00:11:43.750> if<00:11:44.050> I'm<00:11:44.200> doing 00:11:44.550 --> 00:11:44.560 align:start position:0% I'm doing crypto kitty if I'm doing 00:11:44.560 --> 00:11:46.620 align:start position:0% I'm doing crypto kitty if I'm doing something<00:11:45.250> a<00:11:45.370> little<00:11:45.460> bit<00:11:45.670> different<00:11:46.090> then 00:11:46.620 --> 00:11:46.630 align:start position:0% something a little bit different then 00:11:46.630 --> 00:11:48.270 align:start position:0% something a little bit different then there's<00:11:46.840> no<00:11:47.020> progress<00:11:47.350> the<00:11:47.620> problem<00:11:48.040> because 00:11:48.270 --> 00:11:48.280 align:start position:0% there's no progress the problem because 00:11:48.280 --> 00:11:49.830 align:start position:0% there's no progress the problem because you<00:11:48.400> just<00:11:48.550> can't<00:11:48.820> think<00:11:49.060> in<00:11:49.270> terms<00:11:49.510> of<00:11:49.660> what 00:11:49.830 --> 00:11:49.840 align:start position:0% you just can't think in terms of what 00:11:49.840 --> 00:11:52.050 align:start position:0% you just can't think in terms of what will<00:11:49.990> be<00:11:50.170> actually<00:11:50.980> I<00:11:51.070> have<00:11:51.310> that<00:11:51.460> problem<00:11:51.700> too 00:11:52.050 --> 00:11:52.060 align:start position:0% will be actually I have that problem too 00:11:52.060 --> 00:11:54.480 align:start position:0% will be actually I have that problem too what<00:11:52.270> about<00:11:52.570> small<00:11:52.960> contracts<00:11:53.440> but<00:11:54.130> it's<00:11:54.310> not 00:11:54.480 --> 00:11:54.490 align:start position:0% what about small contracts but it's not 00:11:54.490 --> 00:11:56.040 align:start position:0% what about small contracts but it's not the<00:11:54.670> case<00:11:54.880> right<00:11:55.090> there<00:11:55.420> will<00:11:55.630> be<00:11:55.660> some 00:11:56.040 --> 00:11:56.050 align:start position:0% the case right there will be some 00:11:56.050 --> 00:11:57.870 align:start position:0% the case right there will be some privacy<00:11:56.500> problem<00:11:56.890> that<00:11:57.010> stuff<00:11:57.220> succeeds<00:11:57.670> if 00:11:57.870 --> 00:11:57.880 align:start position:0% privacy problem that stuff succeeds if 00:11:57.880 --> 00:11:58.920 align:start position:0% privacy problem that stuff succeeds if your<00:11:58.030> stuff<00:11:58.240> is<00:11:58.360> worth<00:11:58.540> money 00:11:58.920 --> 00:11:58.930 align:start position:0% your stuff is worth money 00:11:58.930 --> 00:12:00.480 align:start position:0% your stuff is worth money someone<00:11:59.470> will<00:11:59.620> want<00:11:59.980> to<00:12:00.010> know<00:12:00.070> what<00:12:00.280> the<00:12:00.370> data 00:12:00.480 --> 00:12:00.490 align:start position:0% someone will want to know what the data 00:12:00.490 --> 00:12:02.730 align:start position:0% someone will want to know what the data is<00:12:00.760> I<00:12:01.090> think<00:12:01.600> you<00:12:01.750> have<00:12:02.140> a<00:12:02.170> very<00:12:02.290> good<00:12:02.470> point 00:12:02.730 --> 00:12:02.740 align:start position:0% is I think you have a very good point 00:12:02.740 --> 00:12:03.930 align:start position:0% is I think you have a very good point where<00:12:02.920> we're<00:12:03.010> planning<00:12:03.370> this<00:12:03.460> event<00:12:03.610> like 00:12:03.930 --> 00:12:03.940 align:start position:0% where we're planning this event like 00:12:03.940 --> 00:12:04.400 align:start position:0% where we're planning this event like that 00:12:04.400 --> 00:12:04.410 align:start position:0% that 00:12:04.410 --> 00:12:08.220 align:start position:0% that so<00:12:05.410> actual<00:12:05.950> contracts<00:12:06.670> right<00:12:07.000> you<00:12:07.660> don't<00:12:07.870> weep 00:12:08.220 --> 00:12:08.230 align:start position:0% so actual contracts right you don't weep 00:12:08.230 --> 00:12:09.570 align:start position:0% so actual contracts right you don't weep the<00:12:08.440> fact<00:12:08.650> there's<00:12:08.830> a<00:12:08.920> business<00:12:09.100> relationship 00:12:09.570 --> 00:12:09.580 align:start position:0% the fact there's a business relationship 00:12:09.580 --> 00:12:11.550 align:start position:0% the fact there's a business relationship between<00:12:10.000> two<00:12:10.300> different<00:12:10.600> parties<00:12:10.900> every<00:12:11.380> time 00:12:11.550 --> 00:12:11.560 align:start position:0% between two different parties every time 00:12:11.560 --> 00:12:14.700 align:start position:0% between two different parties every time you<00:12:11.680> sign<00:12:11.890> up<00:12:12.160> is<00:12:12.370> right<00:12:12.700> but<00:12:13.390> in<00:12:13.540> a<00:12:13.570> watch<00:12:14.170> when 00:12:14.700 --> 00:12:14.710 align:start position:0% you sign up is right but in a watch when 00:12:14.710 --> 00:12:15.780 align:start position:0% you sign up is right but in a watch when you<00:12:14.800> establish<00:12:15.220> that<00:12:15.250> kind<00:12:15.430> of<00:12:15.520> relationship 00:12:15.780 --> 00:12:15.790 align:start position:0% you establish that kind of relationship 00:12:15.790 --> 00:12:18.180 align:start position:0% you establish that kind of relationship it's<00:12:16.210> public<00:12:16.570> everybody<00:12:16.960> and<00:12:17.830> that's<00:12:17.980> just 00:12:18.180 --> 00:12:18.190 align:start position:0% it's public everybody and that's just 00:12:18.190 --> 00:12:20.310 align:start position:0% it's public everybody and that's just not<00:12:18.400> a<00:12:18.460> thing<00:12:18.610> companies<00:12:19.540> or<00:12:19.720> enterprises<00:12:20.260> you 00:12:20.310 --> 00:12:20.320 align:start position:0% not a thing companies or enterprises you 00:12:20.320 --> 00:12:22.320 align:start position:0% not a thing companies or enterprises you want<00:12:20.500> to<00:12:20.560> do<00:12:20.710> and<00:12:21.040> so<00:12:21.550> this<00:12:21.670> goes<00:12:21.880> back<00:12:22.090> to<00:12:22.120> your 00:12:22.320 --> 00:12:22.330 align:start position:0% want to do and so this goes back to your 00:12:22.330 --> 00:12:24.390 align:start position:0% want to do and so this goes back to your point<00:12:22.390> then<00:12:22.930> if<00:12:23.620> we<00:12:23.800> don't<00:12:23.920> solve<00:12:24.220> these 00:12:24.390 --> 00:12:24.400 align:start position:0% point then if we don't solve these 00:12:24.400 --> 00:12:26.040 align:start position:0% point then if we don't solve these privacy<00:12:24.850> problems<00:12:25.210> even<00:12:25.540> for<00:12:25.690> things<00:12:25.840> that 00:12:26.040 --> 00:12:26.050 align:start position:0% privacy problems even for things that 00:12:26.050 --> 00:12:28.110 align:start position:0% privacy problems even for things that are<00:12:26.260> quite<00:12:26.470> money<00:12:26.830> it's<00:12:27.490> going<00:12:27.700> to<00:12:27.760> be<00:12:27.820> a<00:12:27.850> major 00:12:28.110 --> 00:12:28.120 align:start position:0% are quite money it's going to be a major 00:12:28.120 --> 00:12:32.520 align:start position:0% are quite money it's going to be a major barrier<00:12:28.510> to<00:12:28.780> adoption<00:12:28.990> I<00:12:30.900> think<00:12:31.900> you<00:12:32.080> made<00:12:32.500> a 00:12:32.520 --> 00:12:32.530 align:start position:0% barrier to adoption I think you made a 00:12:32.530 --> 00:12:33.630 align:start position:0% barrier to adoption I think you made a very<00:12:32.650> good<00:12:32.770> point 00:12:33.630 --> 00:12:33.640 align:start position:0% very good point 00:12:33.640 --> 00:12:35.010 align:start position:0% very good point privacy<00:12:34.060> needs<00:12:34.270> to<00:12:34.390> be 00:12:35.010 --> 00:12:35.020 align:start position:0% privacy needs to be 00:12:35.020 --> 00:12:36.960 align:start position:0% privacy needs to be early<00:12:35.650> in<00:12:35.800> the<00:12:35.890> process<00:12:36.130> of<00:12:36.580> designing 00:12:36.960 --> 00:12:36.970 align:start position:0% early in the process of designing 00:12:36.970 --> 00:12:39.690 align:start position:0% early in the process of designing applications<00:12:37.300> and<00:12:38.080> also<00:12:38.290> platforms<00:12:38.860> but<00:12:39.340> in 00:12:39.690 --> 00:12:39.700 align:start position:0% applications and also platforms but in 00:12:39.700 --> 00:12:43.050 align:start position:0% applications and also platforms but in light<00:12:40.420> my<00:12:40.870> perspective<00:12:41.530> is<00:12:41.710> that<00:12:42.190> the<00:12:42.760> people 00:12:43.050 --> 00:12:43.060 align:start position:0% light my perspective is that the people 00:12:43.060 --> 00:12:45.510 align:start position:0% light my perspective is that the people are<00:12:43.450> also<00:12:43.690> ill-equipped<00:12:44.170> to<00:12:44.710> attract<00:12:45.280> these 00:12:45.510 --> 00:12:45.520 align:start position:0% are also ill-equipped to attract these 00:12:45.520 --> 00:12:47.610 align:start position:0% are also ill-equipped to attract these privacy<00:12:46.000> concerns<00:12:46.480> from<00:12:47.170> a<00:12:47.200> technological 00:12:47.610 --> 00:12:47.620 align:start position:0% privacy concerns from a technological 00:12:47.620 --> 00:12:50.370 align:start position:0% privacy concerns from a technological perspective<00:12:48.160> right<00:12:49.030> we<00:12:49.390> build<00:12:49.840> two<00:12:50.020> theorem 00:12:50.370 --> 00:12:50.380 align:start position:0% perspective right we build two theorem 00:12:50.380 --> 00:12:52.610 align:start position:0% perspective right we build two theorem as<00:12:50.650> platform<00:12:51.250> that<00:12:51.640> allows<00:12:51.910> you<00:12:52.120> to<00:12:52.330> do 00:12:52.610 --> 00:12:52.620 align:start position:0% as platform that allows you to do 00:12:52.620 --> 00:12:55.920 align:start position:0% as platform that allows you to do something<00:12:53.620> you<00:12:54.220> could<00:12:54.520> some<00:12:54.880> people<00:12:55.270> say<00:12:55.450> also 00:12:55.920 --> 00:12:55.930 align:start position:0% something you could some people say also 00:12:55.930 --> 00:12:58.620 align:start position:0% something you could some people say also do<00:12:56.110> a<00:12:56.140> Bitcoin<00:12:56.740> to<00:12:56.980> large-screen<00:12:57.460> degree<00:12:58.240> but 00:12:58.620 --> 00:12:58.630 align:start position:0% do a Bitcoin to large-screen degree but 00:12:58.630 --> 00:13:00.480 align:start position:0% do a Bitcoin to large-screen degree but it<00:12:58.720> was<00:12:58.870> super<00:12:59.230> complex<00:12:59.740> so<00:12:59.890> the<00:12:59.920> theorem<00:13:00.250> came 00:13:00.480 --> 00:13:00.490 align:start position:0% it was super complex so the theorem came 00:13:00.490 --> 00:13:02.640 align:start position:0% it was super complex so the theorem came along<00:13:00.760> act<00:13:01.210> as<00:13:01.390> nice<00:13:01.600> programming<00:13:02.170> wall<00:13:02.350> and 00:13:02.640 --> 00:13:02.650 align:start position:0% along act as nice programming wall and 00:13:02.650 --> 00:13:04.470 align:start position:0% along act as nice programming wall and smart<00:13:02.890> contracts<00:13:03.340> that<00:13:03.700> added<00:13:04.090> general 00:13:04.470 --> 00:13:04.480 align:start position:0% smart contracts that added general 00:13:04.480 --> 00:13:06.960 align:start position:0% smart contracts that added general opportunity<00:13:04.990> to<00:13:05.200> the<00:13:05.290> field<00:13:05.500> the<00:13:06.340> problem<00:13:06.820> is 00:13:06.960 --> 00:13:06.970 align:start position:0% opportunity to the field the problem is 00:13:06.970 --> 00:13:09.990 align:start position:0% opportunity to the field the problem is now<00:13:07.620> seat<00:13:08.620> has<00:13:08.860> Walter<00:13:09.130> forbid<00:13:09.580> convert 00:13:09.990 --> 00:13:10.000 align:start position:0% now seat has Walter forbid convert 00:13:10.000 --> 00:13:12.180 align:start position:0% now seat has Walter forbid convert resolves<00:13:10.480> to<00:13:10.540> same<00:13:10.810> issue<00:13:11.200> for<00:13:11.590> a<00:13:11.620> theorem<00:13:12.040> the 00:13:12.180 --> 00:13:12.190 align:start position:0% resolves to same issue for a theorem the 00:13:12.190 --> 00:13:14.820 align:start position:0% resolves to same issue for a theorem the theorem<00:13:12.400> is<00:13:12.610> much<00:13:12.820> more<00:13:13.120> generic<00:13:14.020> and<00:13:14.620> there 00:13:14.820 --> 00:13:14.830 align:start position:0% theorem is much more generic and there 00:13:14.830 --> 00:13:17.820 align:start position:0% theorem is much more generic and there will<00:13:15.040> be<00:13:15.280> no<00:13:16.210> there<00:13:16.690> will<00:13:16.870> not<00:13:17.020> be<00:13:17.050> a<00:13:17.440> privacy 00:13:17.820 --> 00:13:17.830 align:start position:0% will be no there will not be a privacy 00:13:17.830 --> 00:13:20.640 align:start position:0% will be no there will not be a privacy solution<00:13:18.750> technical<00:13:19.750> solution<00:13:20.200> that<00:13:20.620> fits 00:13:20.640 --> 00:13:20.650 align:start position:0% solution technical solution that fits 00:13:20.650 --> 00:13:23.220 align:start position:0% solution technical solution that fits all<00:13:21.250> the<00:13:21.490> new<00:13:21.610> spaces<00:13:22.180> that<00:13:22.330> can<00:13:22.540> be<00:13:22.780> built<00:13:23.020> on 00:13:23.220 --> 00:13:23.230 align:start position:0% all the new spaces that can be built on 00:13:23.230 --> 00:13:25.740 align:start position:0% all the new spaces that can be built on the<00:13:23.500> platform<00:13:23.980> so<00:13:24.370> from<00:13:24.640> my<00:13:24.790> perspective<00:13:25.090> it's 00:13:25.740 --> 00:13:25.750 align:start position:0% the platform so from my perspective it's 00:13:25.750 --> 00:13:28.020 align:start position:0% the platform so from my perspective it's key<00:13:26.080> that<00:13:26.110> we<00:13:26.500> establish<00:13:27.100> good<00:13:27.340> schooling<00:13:27.790> and 00:13:28.020 --> 00:13:28.030 align:start position:0% key that we establish good schooling and 00:13:28.030 --> 00:13:30.300 align:start position:0% key that we establish good schooling and equip<00:13:28.660> the<00:13:29.080> engineers<00:13:29.620> that<00:13:29.890> built<00:13:29.950> II 00:13:30.300 --> 00:13:30.310 align:start position:0% equip the engineers that built II 00:13:30.310 --> 00:13:32.730 align:start position:0% equip the engineers that built II centralized<00:13:30.730> applications<00:13:31.420> with<00:13:32.110> the<00:13:32.440> tools 00:13:32.730 --> 00:13:32.740 align:start position:0% centralized applications with the tools 00:13:32.740 --> 00:13:35.310 align:start position:0% centralized applications with the tools they<00:13:33.100> need<00:13:33.310> to<00:13:33.670> make<00:13:34.060> their<00:13:34.480> stuff<00:13:34.780> privacy 00:13:35.310 --> 00:13:35.320 align:start position:0% they need to make their stuff privacy 00:13:35.320 --> 00:13:37.800 align:start position:0% they need to make their stuff privacy where<00:13:35.590> and<00:13:35.920> I'm<00:13:36.310> not<00:13:36.520> only<00:13:36.850> talking<00:13:37.270> about<00:13:37.600> the 00:13:37.800 --> 00:13:37.810 align:start position:0% where and I'm not only talking about the 00:13:37.810 --> 00:13:41.490 align:start position:0% where and I'm not only talking about the traffic<00:13:38.700> mechanisms<00:13:39.700> or<00:13:40.240> but<00:13:40.750> I<00:13:40.900> think<00:13:41.230> they 00:13:41.490 --> 00:13:41.500 align:start position:0% traffic mechanisms or but I think they 00:13:41.500 --> 00:13:43.950 align:start position:0% traffic mechanisms or but I think they could<00:13:41.740> bring<00:13:42.250> you<00:13:42.430> a<00:13:42.460> long<00:13:42.670> wave<00:13:42.910> as<00:13:43.270> community 00:13:43.950 --> 00:13:43.960 align:start position:0% could bring you a long wave as community 00:13:43.960 --> 00:13:47.040 align:start position:0% could bring you a long wave as community we<00:13:44.230> need<00:13:44.410> to<00:13:44.590> think<00:13:44.740> about<00:13:44.890> how<00:13:45.730> we<00:13:46.050> enable 00:13:47.040 --> 00:13:47.050 align:start position:0% we need to think about how we enable 00:13:47.050 --> 00:13:49.200 align:start position:0% we need to think about how we enable people<00:13:47.080> to<00:13:47.740> build<00:13:48.430> privacy<00:13:49.030> where 00:13:49.200 --> 00:13:49.210 align:start position:0% people to build privacy where 00:13:49.210 --> 00:13:51.420 align:start position:0% people to build privacy where applications<00:13:49.780> because<00:13:50.110> now<00:13:50.320> even<00:13:50.800> if<00:13:50.920> people 00:13:51.420 --> 00:13:51.430 align:start position:0% applications because now even if people 00:13:51.430 --> 00:13:53.370 align:start position:0% applications because now even if people think<00:13:51.580> about<00:13:51.910> it<00:13:52.210> I<00:13:52.330> think<00:13:52.810> they<00:13:52.960> can<00:13:53.170> often 00:13:53.370 --> 00:13:53.380 align:start position:0% think about it I think they can often 00:13:53.380 --> 00:13:56.040 align:start position:0% think about it I think they can often just<00:13:53.560> not<00:13:53.890> pull<00:13:54.100> it<00:13:54.130> off<00:13:54.630> another<00:13:55.630> everybody 00:13:56.040 --> 00:13:56.050 align:start position:0% just not pull it off another everybody 00:13:56.050 --> 00:13:59.220 align:start position:0% just not pull it off another everybody has<00:13:56.200> to<00:13:56.350> see<00:13:56.500> cache<00:13:56.710> engineering<00:13:57.310> -<00:13:57.960> well<00:13:58.960> one 00:13:59.220 --> 00:13:59.230 align:start position:0% has to see cache engineering - well one 00:13:59.230 --> 00:14:01.020 align:start position:0% has to see cache engineering - well one more<00:13:59.500> sort<00:13:59.920> of<00:13:59.980> engineering<00:14:00.610> you<00:14:00.640> don't<00:14:00.820> hear 00:14:01.020 --> 00:14:01.030 align:start position:0% more sort of engineering you don't hear 00:14:01.030 --> 00:14:03.030 align:start position:0% more sort of engineering you don't hear and<00:14:01.540> that<00:14:01.690> is<00:14:01.780> obviously<00:14:02.350> is<00:14:02.500> a<00:14:02.530> safety 00:14:03.030 --> 00:14:03.040 align:start position:0% and that is obviously is a safety 00:14:03.040 --> 00:14:05.250 align:start position:0% and that is obviously is a safety property<00:14:03.610> and<00:14:03.760> a<00:14:03.910> safety<00:14:04.210> property<00:14:04.780> can<00:14:05.050> be 00:14:05.250 --> 00:14:05.260 align:start position:0% property and a safety property can be 00:14:05.260 --> 00:14:07.800 align:start position:0% property and a safety property can be lost<00:14:05.530> at<00:14:05.860> any<00:14:06.040> layer<00:14:06.340> in<00:14:06.610> the<00:14:06.700> system<00:14:07.150> so<00:14:07.780> you 00:14:07.800 --> 00:14:07.810 align:start position:0% lost at any layer in the system so you 00:14:07.810 --> 00:14:10.260 align:start position:0% lost at any layer in the system so you can<00:14:07.960> have<00:14:08.320> the<00:14:08.500> strongest<00:14:09.010> possible<00:14:09.400> platform 00:14:10.260 --> 00:14:10.270 align:start position:0% can have the strongest possible platform 00:14:10.270 --> 00:14:12.360 align:start position:0% can have the strongest possible platform underneath<00:14:10.660> you<00:14:11.050> this<00:14:11.590> privacy<00:14:12.040> preserving 00:14:12.360 --> 00:14:12.370 align:start position:0% underneath you this privacy preserving 00:14:12.370 --> 00:14:13.950 align:start position:0% underneath you this privacy preserving but<00:14:12.850> you<00:14:12.970> can<00:14:13.150> still<00:14:13.390> build<00:14:13.600> an<00:14:13.810> application 00:14:13.950 --> 00:14:13.960 align:start position:0% but you can still build an application 00:14:13.960 --> 00:14:15.850 align:start position:0% but you can still build an application on<00:14:14.560> top<00:14:14.770> of<00:14:14.950> that<00:14:15.070> the<00:14:15.310> disgrace 00:14:15.850 --> 00:14:15.860 align:start position:0% on top of that the disgrace 00:14:15.860 --> 00:14:18.250 align:start position:0% on top of that the disgrace in<00:14:16.670> the<00:14:16.820> same<00:14:17.090> way<00:14:17.300> that<00:14:17.540> the<00:14:17.690> fact<00:14:17.960> that<00:14:18.170> you 00:14:18.250 --> 00:14:18.260 align:start position:0% in the same way that the fact that you 00:14:18.260 --> 00:14:21.310 align:start position:0% in the same way that the fact that you have<00:14:18.440> HTTP<00:14:19.250> to<00:14:19.460> transmit<00:14:19.940> data<00:14:19.970> across<00:14:20.540> the 00:14:21.310 --> 00:14:21.320 align:start position:0% have HTTP to transmit data across the 00:14:21.320 --> 00:14:23.830 align:start position:0% have HTTP to transmit data across the internet<00:14:21.770> is<00:14:22.010> an<00:14:22.640> excellent<00:14:23.180> way<00:14:23.330> to<00:14:23.360> protect 00:14:23.830 --> 00:14:23.840 align:start position:0% internet is an excellent way to protect 00:14:23.840 --> 00:14:25.450 align:start position:0% internet is an excellent way to protect the<00:14:23.930> privacy<00:14:24.320> of<00:14:24.440> that<00:14:24.680> data<00:14:24.950> but<00:14:25.130> there<00:14:25.340> are 00:14:25.450 --> 00:14:25.460 align:start position:0% the privacy of that data but there are 00:14:25.460 --> 00:14:29.530 align:start position:0% the privacy of that data but there are plenty<00:14:25.760> of<00:14:26.950> services<00:14:27.950> that<00:14:28.220> use<00:14:28.460> HTTPS<00:14:29.300> and 00:14:29.530 --> 00:14:29.540 align:start position:0% plenty of services that use HTTPS and 00:14:29.540 --> 00:14:31.660 align:start position:0% plenty of services that use HTTPS and yet<00:14:29.690> that<00:14:29.840> terrible<00:14:30.200> price<00:14:30.460> because<00:14:31.460> of<00:14:31.580> the 00:14:31.660 --> 00:14:31.670 align:start position:0% yet that terrible price because of the 00:14:31.670 --> 00:14:33.190 align:start position:0% yet that terrible price because of the application<00:14:32.270> level<00:14:32.450> they<00:14:32.750> give<00:14:32.930> away 00:14:33.190 --> 00:14:33.200 align:start position:0% application level they give away 00:14:33.200 --> 00:14:34.900 align:start position:0% application level they give away everything<00:14:33.560> to<00:14:33.890> be<00:14:34.010> gained<00:14:34.280> at<00:14:34.580> the<00:14:34.730> lower 00:14:34.900 --> 00:14:34.910 align:start position:0% everything to be gained at the lower 00:14:34.910 --> 00:14:39.970 align:start position:0% everything to be gained at the lower levels<00:14:36.340> so<00:14:37.340> um<00:14:37.730> so<00:14:38.420> some<00:14:38.780> one<00:14:38.930> thing<00:14:39.170> that<00:14:39.500> you 00:14:39.970 --> 00:14:39.980 align:start position:0% levels so um so some one thing that you 00:14:39.980 --> 00:14:41.950 align:start position:0% levels so um so some one thing that you were<00:14:40.100> saying<00:14:40.340> is<00:14:40.670> that<00:14:41.060> looking<00:14:41.750> to<00:14:41.870> the 00:14:41.950 --> 00:14:41.960 align:start position:0% were saying is that looking to the 00:14:41.960 --> 00:14:44.860 align:start position:0% were saying is that looking to the future<00:14:42.260> we're<00:14:43.130> just<00:14:43.310> we<00:14:43.520> try<00:14:43.760> to<00:14:43.820> avoid<00:14:44.540> the 00:14:44.860 --> 00:14:44.870 align:start position:0% future we're just we try to avoid the 00:14:44.870 --> 00:14:46.330 align:start position:0% future we're just we try to avoid the mistakes<00:14:45.200> that<00:14:45.290> we<00:14:45.410> make<00:14:45.560> with<00:14:45.680> red<00:14:45.860> one<00:14:46.130> and 00:14:46.330 --> 00:14:46.340 align:start position:0% mistakes that we make with red one and 00:14:46.340 --> 00:14:48.580 align:start position:0% mistakes that we make with red one and one<00:14:46.490> two<00:14:46.790> and<00:14:47.060> do<00:14:47.600> one<00:14:47.780> three<00:14:48.050> different<00:14:48.380> and 00:14:48.580 --> 00:14:48.590 align:start position:0% one two and do one three different and 00:14:48.590 --> 00:14:50.620 align:start position:0% one two and do one three different and so<00:14:48.680> the<00:14:49.010> answer<00:14:49.310> is<00:14:49.340> privacy<00:14:49.700> by<00:14:49.940> design<00:14:49.970> that 00:14:50.620 --> 00:14:50.630 align:start position:0% so the answer is privacy by design that 00:14:50.630 --> 00:14:52.240 align:start position:0% so the answer is privacy by design that privacy<00:14:50.990> tool<00:14:51.320> many<00:14:51.530> things<00:14:51.800> like<00:14:52.040> that 00:14:52.240 --> 00:14:52.250 align:start position:0% privacy tool many things like that 00:14:52.250 --> 00:14:54.550 align:start position:0% privacy tool many things like that giving<00:14:52.610> developer<00:14:53.120> to<00:14:53.240> see<00:14:53.290> opportunity<00:14:54.290> and 00:14:54.550 --> 00:14:54.560 align:start position:0% giving developer to see opportunity and 00:14:54.560 --> 00:14:57.460 align:start position:0% giving developer to see opportunity and the<00:14:55.250> knowledge<00:14:55.430> to<00:14:56.030> build<00:14:56.660> in<00:14:56.930> privacy<00:14:57.260> by 00:14:57.460 --> 00:14:57.470 align:start position:0% the knowledge to build in privacy by 00:14:57.470 --> 00:15:00.370 align:start position:0% the knowledge to build in privacy by design<00:14:57.500> and<00:14:57.950> make<00:14:58.100> it<00:14:58.220> easy<00:14:58.490> for<00:14:58.730> them<00:14:58.910> so<00:14:59.570> do 00:15:00.370 --> 00:15:00.380 align:start position:0% design and make it easy for them so do 00:15:00.380 --> 00:15:05.050 align:start position:0% design and make it easy for them so do we<00:15:00.500> just<00:15:01.990> that's<00:15:02.990> how<00:15:03.140> we<00:15:03.200> get<00:15:03.380> web<00:15:03.560> three<00:15:04.060> we 00:15:05.050 --> 00:15:05.060 align:start position:0% we just that's how we get web three we 00:15:05.060 --> 00:15:07.570 align:start position:0% we just that's how we get web three we will<00:15:05.360> really<00:15:05.960> help<00:15:06.230> run<00:15:06.470> a<00:15:06.530> scaling<00:15:06.980> issue<00:15:07.160> and 00:15:07.570 --> 00:15:07.580 align:start position:0% will really help run a scaling issue and 00:15:07.580 --> 00:15:14.860 align:start position:0% will really help run a scaling issue and not<00:15:07.730> have<00:15:08.030> to<00:15:10.510> well<00:15:11.510> I<00:15:12.370> think<00:15:13.370> if<00:15:13.940> all<00:15:14.480> of<00:15:14.750> the 00:15:14.860 --> 00:15:14.870 align:start position:0% not have to well I think if all of the 00:15:14.870 --> 00:15:16.960 align:start position:0% not have to well I think if all of the engineers<00:15:15.440> in<00:15:15.650> the<00:15:15.770> world<00:15:15.800> could<00:15:16.310> make<00:15:16.340> a<00:15:16.550> pact 00:15:16.960 --> 00:15:16.970 align:start position:0% engineers in the world could make a pact 00:15:16.970 --> 00:15:19.720 align:start position:0% engineers in the world could make a pact that<00:15:17.270> we<00:15:17.510> would<00:15:17.720> only<00:15:17.870> build<00:15:18.730> privacy 00:15:19.720 --> 00:15:19.730 align:start position:0% that we would only build privacy 00:15:19.730 --> 00:15:21.370 align:start position:0% that we would only build privacy friendly<00:15:20.120> technologies<00:15:20.750> for<00:15:20.990> the<00:15:21.080> rest<00:15:21.260> of 00:15:21.370 --> 00:15:21.380 align:start position:0% friendly technologies for the rest of 00:15:21.380 --> 00:15:24.070 align:start position:0% friendly technologies for the rest of our<00:15:21.470> lives<00:15:21.680> and<00:15:22.070> be<00:15:22.820> careful<00:15:23.180> about<00:15:23.420> who<00:15:23.600> else 00:15:24.070 --> 00:15:24.080 align:start position:0% our lives and be careful about who else 00:15:24.080 --> 00:15:25.780 align:start position:0% our lives and be careful about who else we<00:15:24.320> train<00:15:24.560> to<00:15:24.710> be<00:15:24.830> an<00:15:24.920> engineer<00:15:25.340> than<00:15:25.490> we'd<00:15:25.670> be 00:15:25.780 --> 00:15:25.790 align:start position:0% we train to be an engineer than we'd be 00:15:25.790 --> 00:15:26.350 align:start position:0% we train to be an engineer than we'd be in<00:15:25.940> good<00:15:26.090> shape 00:15:26.350 --> 00:15:26.360 align:start position:0% in good shape 00:15:26.360 --> 00:15:28.360 align:start position:0% in good shape but<00:15:26.930> given<00:15:27.260> the<00:15:27.350> incentive<00:15:27.800> structure<00:15:28.220> that 00:15:28.360 --> 00:15:28.370 align:start position:0% but given the incentive structure that 00:15:28.370 --> 00:15:30.010 align:start position:0% but given the incentive structure that we're<00:15:28.550> being<00:15:28.700> given<00:15:29.150> how<00:15:29.270> everything<00:15:29.780> works 00:15:30.010 --> 00:15:30.020 align:start position:0% we're being given how everything works 00:15:30.020 --> 00:15:31.630 align:start position:0% we're being given how everything works we<00:15:30.230> have<00:15:30.260> to<00:15:30.470> be<00:15:30.590> concerned<00:15:30.950> about<00:15:31.310> what<00:15:31.490> kind 00:15:31.630 --> 00:15:31.640 align:start position:0% we have to be concerned about what kind 00:15:31.640 --> 00:15:33.730 align:start position:0% we have to be concerned about what kind of<00:15:31.790> market<00:15:32.150> develops<00:15:32.600> and<00:15:32.870> avoiding<00:15:33.650> the 00:15:33.730 --> 00:15:33.740 align:start position:0% of market develops and avoiding the 00:15:33.740 --> 00:15:35.080 align:start position:0% of market develops and avoiding the situation<00:15:33.890> where<00:15:34.460> there's<00:15:34.640> a<00:15:34.730> race<00:15:34.880> to<00:15:34.910> the 00:15:35.080 --> 00:15:35.090 align:start position:0% situation where there's a race to the 00:15:35.090 --> 00:15:37.570 align:start position:0% situation where there's a race to the bottom<00:15:35.380> and<00:15:36.380> that<00:15:36.560> means<00:15:36.740> we<00:15:36.950> need<00:15:37.160> to<00:15:37.370> think 00:15:37.570 --> 00:15:37.580 align:start position:0% bottom and that means we need to think 00:15:37.580 --> 00:15:40.000 align:start position:0% bottom and that means we need to think about<00:15:37.790> how<00:15:38.180> about<00:15:38.780> governance<00:15:39.320> because<00:15:39.800> there 00:15:40.000 --> 00:15:40.010 align:start position:0% about how about governance because there 00:15:40.010 --> 00:15:42.310 align:start position:0% about how about governance because there is<00:15:40.160> a<00:15:40.190> competitive<00:15:40.910> dynamic<00:15:41.480> that<00:15:41.960> will<00:15:42.110> drive 00:15:42.310 --> 00:15:42.320 align:start position:0% is a competitive dynamic that will drive 00:15:42.320 --> 00:15:44.350 align:start position:0% is a competitive dynamic that will drive everyone<00:15:42.890> to<00:15:43.010> try<00:15:43.160> to<00:15:43.250> collect<00:15:43.550> and<00:15:43.910> exploit 00:15:44.350 --> 00:15:44.360 align:start position:0% everyone to try to collect and exploit 00:15:44.360 --> 00:15:46.030 align:start position:0% everyone to try to collect and exploit more<00:15:44.570> data<00:15:44.810> than<00:15:45.050> the<00:15:45.170> other<00:15:45.320> person<00:15:45.770> in<00:15:45.890> order 00:15:46.030 --> 00:15:46.040 align:start position:0% more data than the other person in order 00:15:46.040 --> 00:15:48.130 align:start position:0% more data than the other person in order to<00:15:46.250> eke<00:15:46.400> out<00:15:46.550> a<00:15:46.610> little<00:15:46.880> bit<00:15:47.060> more<00:15:47.210> profit<00:15:47.660> gain 00:15:48.130 --> 00:15:48.140 align:start position:0% to eke out a little bit more profit gain 00:15:48.140 --> 00:15:49.810 align:start position:0% to eke out a little bit more profit gain a<00:15:48.170> little<00:15:48.350> bit<00:15:48.560> of<00:15:48.680> a<00:15:48.740> business<00:15:49.040> advantage<00:15:49.490> I 00:15:49.810 --> 00:15:49.820 align:start position:0% a little bit of a business advantage I 00:15:49.820 --> 00:15:52.510 align:start position:0% a little bit of a business advantage I don't<00:15:50.480> think<00:15:50.840> we<00:15:50.990> can<00:15:51.140> solve<00:15:51.410> this<00:15:51.710> by<00:15:51.980> just 00:15:52.510 --> 00:15:52.520 align:start position:0% don't think we can solve this by just 00:15:52.520 --> 00:15:55.930 align:start position:0% don't think we can solve this by just all<00:15:52.760> agreeing<00:15:53.120> to<00:15:53.450> not<00:15:53.900> be<00:15:54.050> evil<00:15:54.550> and<00:15:55.550> I<00:15:55.880> don't 00:15:55.930 --> 00:15:55.940 align:start position:0% all agreeing to not be evil and I don't 00:15:55.940 --> 00:15:58.130 align:start position:0% all agreeing to not be evil and I don't think<00:15:56.300> we<00:15:56.420> can<00:15:56.630> solve<00:15:56.900> it<00:15:57.140> by 00:15:58.130 --> 00:15:58.140 align:start position:0% think we can solve it by 00:15:58.140 --> 00:16:02.180 align:start position:0% think we can solve it by bill<00:15:58.430> later<00:15:59.430> one<00:15:59.790> boring<00:16:00.660> Aleya<00:16:01.050> -<00:16:01.410> which<00:16:02.010> is 00:16:02.180 --> 00:16:02.190 align:start position:0% bill later one boring Aleya - which is 00:16:02.190 --> 00:16:06.800 align:start position:0% bill later one boring Aleya - which is going<00:16:02.430> to<00:16:02.550> make<00:16:04.310> make<00:16:05.310> insecure<00:16:06.120> or<00:16:06.390> London 00:16:06.800 --> 00:16:06.810 align:start position:0% going to make make insecure or London 00:16:06.810 --> 00:16:09.530 align:start position:0% going to make make insecure or London private<00:16:07.850> applications<00:16:08.850> on<00:16:09.030> top<00:16:09.210> of<00:16:09.390> them 00:16:09.530 --> 00:16:09.540 align:start position:0% private applications on top of them 00:16:09.540 --> 00:16:11.660 align:start position:0% private applications on top of them impossible<00:16:10.140> we<00:16:10.650> need<00:16:10.800> to<00:16:10.890> have<00:16:11.100> some<00:16:11.430> way<00:16:11.640> of 00:16:11.660 --> 00:16:11.670 align:start position:0% impossible we need to have some way of 00:16:11.670 --> 00:16:13.700 align:start position:0% impossible we need to have some way of governing<00:16:12.270> our<00:16:12.420> behavior<00:16:12.930> that<00:16:13.110> is<00:16:13.230> stronger 00:16:13.700 --> 00:16:13.710 align:start position:0% governing our behavior that is stronger 00:16:13.710 --> 00:16:17.000 align:start position:0% governing our behavior that is stronger than<00:16:13.950> just<00:16:14.420> than<00:16:15.420> just<00:16:15.660> slogans<00:16:16.110> and<00:16:16.830> that 00:16:17.000 --> 00:16:17.010 align:start position:0% than just than just slogans and that 00:16:17.010 --> 00:16:18.590 align:start position:0% than just than just slogans and that means<00:16:17.220> that<00:16:17.460> we<00:16:17.580> need<00:16:17.700> to<00:16:17.820> think<00:16:18.000> about<00:16:18.420> how 00:16:18.590 --> 00:16:18.600 align:start position:0% means that we need to think about how 00:16:18.600 --> 00:16:20.000 align:start position:0% means that we need to think about how we're<00:16:18.780> going<00:16:18.870> to<00:16:18.930> operate<00:16:19.260> we<00:16:19.530> need<00:16:19.680> to<00:16:19.770> think 00:16:20.000 --> 00:16:20.010 align:start position:0% we're going to operate we need to think 00:16:20.010 --> 00:16:21.920 align:start position:0% we're going to operate we need to think about<00:16:20.160> rules<00:16:20.550> of<00:16:20.760> the<00:16:20.880> road<00:16:21.060> for<00:16:21.120> the<00:16:21.690> sector 00:16:21.920 --> 00:16:21.930 align:start position:0% about rules of the road for the sector 00:16:21.930 --> 00:16:24.370 align:start position:0% about rules of the road for the sector and<00:16:22.560> we<00:16:22.710> can<00:16:22.860> try<00:16:23.070> to<00:16:23.100> set<00:16:23.400> those<00:16:23.580> ourselves 00:16:24.370 --> 00:16:24.380 align:start position:0% and we can try to set those ourselves 00:16:24.380 --> 00:16:26.750 align:start position:0% and we can try to set those ourselves governments<00:16:25.380> will<00:16:25.560> try<00:16:25.770> to<00:16:25.800> set<00:16:26.130> them<00:16:26.310> for<00:16:26.610> us 00:16:26.750 --> 00:16:26.760 align:start position:0% governments will try to set them for us 00:16:26.760 --> 00:16:29.000 align:start position:0% governments will try to set them for us sometimes<00:16:27.720> governments<00:16:28.410> will<00:16:28.560> actually<00:16:28.890> be 00:16:29.000 --> 00:16:29.010 align:start position:0% sometimes governments will actually be 00:16:29.010 --> 00:16:31.220 align:start position:0% sometimes governments will actually be helping<00:16:29.310> us<00:16:29.430> when<00:16:29.670> they<00:16:29.790> do<00:16:29.850> that<00:16:30.150> but<00:16:31.020> they're 00:16:31.220 --> 00:16:31.230 align:start position:0% helping us when they do that but they're 00:16:31.230 --> 00:16:33.170 align:start position:0% helping us when they do that but they're gonna<00:16:31.380> have<00:16:31.590> to<00:16:31.740> be<00:16:31.860> rules<00:16:32.130> because<00:16:32.580> the 00:16:33.170 --> 00:16:33.180 align:start position:0% gonna have to be rules because the 00:16:33.180 --> 00:16:35.780 align:start position:0% gonna have to be rules because the market<00:16:33.750> by<00:16:33.900> itself<00:16:34.320> leads<00:16:34.710> to<00:16:34.980> an<00:16:35.100> outcome<00:16:35.310> - 00:16:35.780 --> 00:16:35.790 align:start position:0% market by itself leads to an outcome - 00:16:35.790 --> 00:16:47.780 align:start position:0% market by itself leads to an outcome - surprise<00:16:40.130> sir<00:16:45.320> no<00:16:46.320> I<00:16:46.620> just<00:16:46.860> wanted<00:16:47.400> to<00:16:47.580> add<00:16:47.760> to 00:16:47.780 --> 00:16:47.790 align:start position:0% surprise sir no I just wanted to add to 00:16:47.790 --> 00:16:51.110 align:start position:0% surprise sir no I just wanted to add to that<00:16:48.060> that<00:16:48.450> I<00:16:48.570> see<00:16:49.020> the<00:16:49.580> decentralized<00:16:50.580> space 00:16:51.110 --> 00:16:51.120 align:start position:0% that that I see the decentralized space 00:16:51.120 --> 00:16:54.500 align:start position:0% that that I see the decentralized space also<00:16:52.110> as<00:16:52.260> a<00:16:52.290> kind<00:16:52.680> of<00:16:52.890> opportunity<00:16:53.670> because<00:16:54.360> it 00:16:54.500 --> 00:16:54.510 align:start position:0% also as a kind of opportunity because it 00:16:54.510 --> 00:16:58.100 align:start position:0% also as a kind of opportunity because it just<00:16:54.660> show<00:16:55.050> buddy<00:16:55.970> where<00:16:56.970> which<00:16:57.480> data<00:16:57.900> is 00:16:58.100 --> 00:16:58.110 align:start position:0% just show buddy where which data is 00:16:58.110 --> 00:16:59.840 align:start position:0% just show buddy where which data is collected<00:16:58.470> and<00:16:59.070> that<00:16:59.100> it<00:16:59.460> needs<00:16:59.670> protection 00:16:59.840 --> 00:16:59.850 align:start position:0% collected and that it needs protection 00:16:59.850 --> 00:17:02.630 align:start position:0% collected and that it needs protection whereas<00:17:00.780> in<00:17:00.990> the<00:17:01.080> current<00:17:01.380> system<00:17:01.590> it's<00:17:02.190> kind 00:17:02.630 --> 00:17:02.640 align:start position:0% whereas in the current system it's kind 00:17:02.640 --> 00:17:06.110 align:start position:0% whereas in the current system it's kind of<00:17:02.760> hidden<00:17:03.000> behind<00:17:03.860> API<00:17:04.860> or<00:17:05.220> company<00:17:05.880> walls 00:17:06.110 --> 00:17:06.120 align:start position:0% of hidden behind API or company walls 00:17:06.120 --> 00:17:08.449 align:start position:0% of hidden behind API or company walls and<00:17:06.449> we<00:17:06.690> do<00:17:06.839> not<00:17:07.020> really<00:17:07.440> know<00:17:07.770> because<00:17:08.250> we 00:17:08.449 --> 00:17:08.459 align:start position:0% and we do not really know because we 00:17:08.459 --> 00:17:09.980 align:start position:0% and we do not really know because we cannot<00:17:08.820> personally<00:17:09.150> track<00:17:09.660> what's<00:17:09.930> happening 00:17:09.980 --> 00:17:09.990 align:start position:0% cannot personally track what's happening 00:17:09.990 --> 00:17:13.520 align:start position:0% cannot personally track what's happening behind<00:17:10.560> that<00:17:10.980> so<00:17:11.490> why<00:17:11.730> if<00:17:12.270> by<00:17:12.720> making<00:17:13.380> this 00:17:13.520 --> 00:17:13.530 align:start position:0% behind that so why if by making this 00:17:13.530 --> 00:17:15.590 align:start position:0% behind that so why if by making this issue<00:17:13.829> a<00:17:13.980> very<00:17:14.250> prominent<00:17:14.730> issue<00:17:15.089> by<00:17:15.360> showing 00:17:15.590 --> 00:17:15.600 align:start position:0% issue a very prominent issue by showing 00:17:15.600 --> 00:17:17.810 align:start position:0% issue a very prominent issue by showing everybody<00:17:16.050> hey<00:17:16.500> here<00:17:16.860> later<00:17:17.070> stare<00:17:17.490> into<00:17:17.790> the 00:17:17.810 --> 00:17:17.820 align:start position:0% everybody hey here later stare into the 00:17:17.820 --> 00:17:18.290 align:start position:0% everybody hey here later stare into the attacks 00:17:18.290 --> 00:17:18.300 align:start position:0% attacks 00:17:18.300 --> 00:17:20.180 align:start position:0% attacks it<00:17:18.690> will<00:17:18.900> probably<00:17:19.140> encourage<00:17:19.709> this<00:17:19.980> process 00:17:20.180 --> 00:17:20.190 align:start position:0% it will probably encourage this process 00:17:20.190 --> 00:17:24.710 align:start position:0% it will probably encourage this process of<00:17:20.579> speeded<00:17:20.940> up<00:17:21.030> and<00:17:23.089> one<00:17:24.089> sort<00:17:24.270> of<00:17:24.329> follow-up 00:17:24.710 --> 00:17:24.720 align:start position:0% of speeded up and one sort of follow-up 00:17:24.720 --> 00:17:27.500 align:start position:0% of speeded up and one sort of follow-up question<00:17:25.110> I<00:17:25.230> have<00:17:25.410> for<00:17:25.620> you<00:17:26.250> and<00:17:26.490> on<00:17:26.790> the<00:17:27.030> idea 00:17:27.500 --> 00:17:27.510 align:start position:0% question I have for you and on the idea 00:17:27.510 --> 00:17:30.830 align:start position:0% question I have for you and on the idea of<00:17:27.740> how<00:17:29.090> governments<00:17:30.090> to<00:17:30.270> potentially 00:17:30.830 --> 00:17:30.840 align:start position:0% of how governments to potentially 00:17:30.840 --> 00:17:35.090 align:start position:0% of how governments to potentially provide<00:17:31.700> you<00:17:32.700> know<00:17:32.760> gas<00:17:33.150> or<00:17:33.510> were<00:17:34.100> additional 00:17:35.090 --> 00:17:35.100 align:start position:0% provide you know gas or were additional 00:17:35.100 --> 00:17:37.480 align:start position:0% provide you know gas or were additional incentive<00:17:35.550> for<00:17:35.730> us<00:17:35.880> to<00:17:36.120> consider<00:17:36.480> privacy 00:17:37.480 --> 00:17:37.490 align:start position:0% incentive for us to consider privacy 00:17:37.490 --> 00:17:39.370 align:start position:0% incentive for us to consider privacy as<00:17:37.970> a<00:17:38.030> peasant<00:17:38.240> sort<00:17:38.660> of<00:17:38.720> central<00:17:39.020> technology 00:17:39.370 --> 00:17:39.380 align:start position:0% as a peasant sort of central technology 00:17:39.380 --> 00:17:42.130 align:start position:0% as a peasant sort of central technology systems<00:17:39.950> do<00:17:40.370> you<00:17:40.460> think<00:17:40.640> like<00:17:40.790> things<00:17:41.780> like 00:17:42.130 --> 00:17:42.140 align:start position:0% systems do you think like things like 00:17:42.140 --> 00:17:45.910 align:start position:0% systems do you think like things like GPR<00:17:43.150> that<00:17:44.150> kind<00:17:44.450> of<00:17:44.510> transform<00:17:45.080> user<00:17:45.620> data 00:17:45.910 --> 00:17:45.920 align:start position:0% GPR that kind of transform user data 00:17:45.920 --> 00:17:48.940 align:start position:0% GPR that kind of transform user data into<00:17:46.550> a<00:17:46.610> much<00:17:46.850> bigger<00:17:46.880> liability<00:17:47.950> for 00:17:48.940 --> 00:17:48.950 align:start position:0% into a much bigger liability for 00:17:48.950 --> 00:17:50.440 align:start position:0% into a much bigger liability for companies<00:17:49.430> and<00:17:49.640> business<00:17:49.880> entities<00:17:50.240> do<00:17:50.360> you 00:17:50.440 --> 00:17:50.450 align:start position:0% companies and business entities do you 00:17:50.450 --> 00:17:51.820 align:start position:0% companies and business entities do you think<00:17:50.600> actions<00:17:51.020> like<00:17:51.440> that<00:17:51.590> in<00:17:51.710> other 00:17:51.820 --> 00:17:51.830 align:start position:0% think actions like that in other 00:17:51.830 --> 00:17:54.190 align:start position:0% think actions like that in other governments<00:17:52.820> or<00:17:53.000> raid<00:17:53.480> agents<00:17:53.870> event<00:17:54.110> of 00:17:54.190 --> 00:17:54.200 align:start position:0% governments or raid agents event of 00:17:54.200 --> 00:17:57.280 align:start position:0% governments or raid agents event of their<00:17:54.260> variants<00:17:54.650> might<00:17:55.220> serve<00:17:55.640> to<00:17:56.290> compel 00:17:57.280 --> 00:17:57.290 align:start position:0% their variants might serve to compel 00:17:57.290 --> 00:18:00.280 align:start position:0% their variants might serve to compel people<00:17:57.320> to<00:17:58.720> effectively<00:17:59.720> change<00:17:59.750> the 00:18:00.280 --> 00:18:00.290 align:start position:0% people to effectively change the 00:18:00.290 --> 00:18:02.530 align:start position:0% people to effectively change the behavior<00:18:00.830> in<00:18:01.070> most<00:18:01.250> businesses<00:18:01.940> approaching 00:18:02.530 --> 00:18:02.540 align:start position:0% behavior in most businesses approaching 00:18:02.540 --> 00:18:05.160 align:start position:0% behavior in most businesses approaching these<00:18:02.690> systems<00:18:03.110> I<00:18:03.430> mean<00:18:04.430> I<00:18:04.490> think<00:18:04.700> ultimately 00:18:05.160 --> 00:18:05.170 align:start position:0% these systems I mean I think ultimately 00:18:05.170 --> 00:18:09.130 align:start position:0% these systems I mean I think ultimately when<00:18:06.170> businesses<00:18:06.860> think<00:18:07.250> of<00:18:07.490> large<00:18:08.480> holdings 00:18:09.130 --> 00:18:09.140 align:start position:0% when businesses think of large holdings 00:18:09.140 --> 00:18:12.390 align:start position:0% when businesses think of large holdings of<00:18:09.320> data<00:18:09.620> as<00:18:09.920> a<00:18:09.950> source<00:18:10.400> of<00:18:10.580> risk<00:18:10.820> then<00:18:11.570> they're 00:18:12.390 --> 00:18:12.400 align:start position:0% of data as a source of risk then they're 00:18:12.400 --> 00:18:15.910 align:start position:0% of data as a source of risk then they're then<00:18:13.400> they're<00:18:13.840> they're<00:18:14.840> calculations<00:18:15.470> will 00:18:15.910 --> 00:18:15.920 align:start position:0% then they're they're calculations will 00:18:15.920 --> 00:18:18.820 align:start position:0% then they're they're calculations will change<00:18:16.750> GPR<00:18:17.750> is<00:18:17.780> one<00:18:18.140> of<00:18:18.230> the<00:18:18.320> things<00:18:18.560> that 00:18:18.820 --> 00:18:18.830 align:start position:0% change GPR is one of the things that 00:18:18.830 --> 00:18:20.500 align:start position:0% change GPR is one of the things that does<00:18:19.100> that<00:18:19.370> it's<00:18:19.550> legal<00:18:19.970> risk<00:18:20.210> its 00:18:20.500 --> 00:18:20.510 align:start position:0% does that it's legal risk its 00:18:20.510 --> 00:18:22.210 align:start position:0% does that it's legal risk its reputational<00:18:21.260> risk<00:18:21.470> and<00:18:21.710> other<00:18:21.800> kinds<00:18:22.130> of 00:18:22.210 --> 00:18:22.220 align:start position:0% reputational risk and other kinds of 00:18:22.220 --> 00:18:24.580 align:start position:0% reputational risk and other kinds of risks<00:18:22.520> that<00:18:23.030> can<00:18:23.480> comfortable<00:18:24.080> in<00:18:24.260> day<00:18:24.440> the 00:18:24.580 --> 00:18:24.590 align:start position:0% risks that can comfortable in day the 00:18:24.590 --> 00:18:26.290 align:start position:0% risks that can comfortable in day the government's<00:18:25.160> will<00:18:25.460> be<00:18:25.670> tightening<00:18:26.090> the 00:18:26.290 --> 00:18:26.300 align:start position:0% government's will be tightening the 00:18:26.300 --> 00:18:28.570 align:start position:0% government's will be tightening the screws<00:18:26.600> because<00:18:27.560> there's<00:18:27.980> a<00:18:28.100> perception 00:18:28.570 --> 00:18:28.580 align:start position:0% screws because there's a perception 00:18:28.580 --> 00:18:31.960 align:start position:0% screws because there's a perception probably<00:18:29.360> correct<00:18:29.780> that<00:18:30.410> privacy<00:18:31.310> has<00:18:31.610> gotten 00:18:31.960 --> 00:18:31.970 align:start position:0% probably correct that privacy has gotten 00:18:31.970 --> 00:18:34.000 align:start position:0% probably correct that privacy has gotten worse<00:18:32.390> over<00:18:32.870> time<00:18:32.900> and<00:18:33.410> companies<00:18:33.860> have 00:18:34.000 --> 00:18:34.010 align:start position:0% worse over time and companies have 00:18:34.010 --> 00:18:35.530 align:start position:0% worse over time and companies have become<00:18:34.340> more<00:18:34.580> careless<00:18:34.820> with<00:18:35.210> these<00:18:35.360> super 00:18:35.530 --> 00:18:35.540 align:start position:0% become more careless with these super 00:18:35.540 --> 00:18:38.140 align:start position:0% become more careless with these super days<00:18:35.780> data<00:18:36.500> over<00:18:36.830> time<00:18:37.040> and<00:18:37.400> if<00:18:37.700> this<00:18:37.790> sector 00:18:38.140 --> 00:18:38.150 align:start position:0% days data over time and if this sector 00:18:38.150 --> 00:18:39.610 align:start position:0% days data over time and if this sector is<00:18:38.240> going<00:18:38.360> to<00:18:38.510> be<00:18:38.630> better<00:18:38.840> something's<00:18:39.380> going 00:18:39.610 --> 00:18:39.620 align:start position:0% is going to be better something's going 00:18:39.620 --> 00:18:41.850 align:start position:0% is going to be better something's going to<00:18:39.650> have<00:18:39.800> to<00:18:39.950> happen<00:18:40.100> to<00:18:40.400> me<00:18:40.550> that<00:18:40.850> happened 00:18:41.850 --> 00:18:41.860 align:start position:0% to have to happen to me that happened 00:18:41.860 --> 00:18:45.190 align:start position:0% to have to happen to me that happened the<00:18:42.860> anybody<00:18:43.850> in<00:18:44.150> this<00:18:44.360> sector<00:18:44.630> or<00:18:44.810> any<00:18:44.960> other 00:18:45.190 --> 00:18:45.200 align:start position:0% the anybody in this sector or any other 00:18:45.200 --> 00:18:47.400 align:start position:0% the anybody in this sector or any other sector<00:18:45.560> who<00:18:45.830> gets<00:18:46.040> big<00:18:46.310> enough<00:18:46.550> to<00:18:46.760> matter 00:18:47.400 --> 00:18:47.410 align:start position:0% sector who gets big enough to matter 00:18:47.410 --> 00:18:50.200 align:start position:0% sector who gets big enough to matter it's<00:18:48.410> big<00:18:48.650> enough<00:18:48.800> that<00:18:48.950> your<00:18:49.400> investors<00:18:50.060> are 00:18:50.200 --> 00:18:50.210 align:start position:0% it's big enough that your investors are 00:18:50.210 --> 00:18:53.320 align:start position:0% it's big enough that your investors are happy<00:18:50.590> you<00:18:51.590> will<00:18:51.740> be<00:18:51.770> visible<00:18:52.220> to<00:18:52.370> to 00:18:53.320 --> 00:18:53.330 align:start position:0% happy you will be visible to to 00:18:53.330 --> 00:18:55.180 align:start position:0% happy you will be visible to to policymakers<00:18:54.080> and<00:18:54.230> regulators<00:18:54.530> and<00:18:54.980> if<00:18:55.100> you 00:18:55.180 --> 00:18:55.190 align:start position:0% policymakers and regulators and if you 00:18:55.190 --> 00:18:57.550 align:start position:0% policymakers and regulators and if you are<00:18:55.310> not<00:18:55.490> behaving<00:18:55.880> well<00:18:56.320> you're<00:18:57.320> going<00:18:57.500> to 00:18:57.550 --> 00:18:57.560 align:start position:0% are not behaving well you're going to 00:18:57.560 --> 00:19:00.040 align:start position:0% are not behaving well you're going to find<00:18:57.650> out<00:18:58.010> in<00:18:58.910> the<00:18:59.060> same<00:18:59.240> way<00:18:59.300> that<00:18:59.720> I<00:18:59.810> seal 00:19:00.040 --> 00:19:00.050 align:start position:0% find out in the same way that I seal 00:19:00.050 --> 00:19:02.560 align:start position:0% find out in the same way that I seal markets<00:19:00.590> FCU<00:19:01.220> crackdowns<00:19:01.820> we're<00:19:02.360> going<00:19:02.510> to 00:19:02.560 --> 00:19:02.570 align:start position:0% markets FCU crackdowns we're going to 00:19:02.570 --> 00:19:05.080 align:start position:0% markets FCU crackdowns we're going to see<00:19:02.720> I<00:19:03.020> think<00:19:03.070> crackdowns<00:19:04.070> upon<00:19:04.400> privacy<00:19:04.970> if 00:19:05.080 --> 00:19:05.090 align:start position:0% see I think crackdowns upon privacy if 00:19:05.090 --> 00:19:07.930 align:start position:0% see I think crackdowns upon privacy if people<00:19:05.420> are<00:19:05.540> really<00:19:05.660> careless<00:19:06.490> sorry<00:19:07.490> because 00:19:07.930 --> 00:19:07.940 align:start position:0% people are really careless sorry because 00:19:07.940 --> 00:19:10.899 align:start position:0% people are really careless sorry because my<00:19:08.120> question<00:19:08.630> through<00:19:08.840> I<00:19:09.220> think 00:19:10.899 --> 00:19:10.909 align:start position:0% my question through I think 00:19:10.909 --> 00:19:13.359 align:start position:0% my question through I think how<00:19:11.389> we<00:19:11.450> make<00:19:11.749> sure<00:19:11.779> you<00:19:12.019> get<00:19:12.200> prized<00:19:13.070> is 00:19:13.359 --> 00:19:13.369 align:start position:0% how we make sure you get prized is 00:19:13.369 --> 00:19:15.159 align:start position:0% how we make sure you get prized is actually<00:19:13.700> good<00:19:13.970> and<00:19:14.149> not<00:19:14.330> just<00:19:14.509> the<00:19:14.690> illusion 00:19:15.159 --> 00:19:15.169 align:start position:0% actually good and not just the illusion 00:19:15.169 --> 00:19:17.619 align:start position:0% actually good and not just the illusion of<00:19:15.320> compliance<00:19:16.190> right<00:19:16.460> we've<00:19:16.700> seen<00:19:16.940> this<00:19:17.119> in 00:19:17.619 --> 00:19:17.629 align:start position:0% of compliance right we've seen this in 00:19:17.629 --> 00:19:21.029 align:start position:0% of compliance right we've seen this in for<00:19:18.590> payments<00:19:19.039> and<00:19:19.389> Victorian<00:19:20.389> securities 00:19:21.029 --> 00:19:21.039 align:start position:0% for payments and Victorian securities 00:19:21.039 --> 00:19:24.100 align:start position:0% for payments and Victorian securities privacy<00:19:22.039> needs<00:19:22.340> that<00:19:22.610> like<00:19:22.759> lukla<00:19:23.210> think<00:19:23.480> work 00:19:24.100 --> 00:19:24.110 align:start position:0% privacy needs that like lukla think work 00:19:24.110 --> 00:19:26.859 align:start position:0% privacy needs that like lukla think work now<00:19:24.820> but<00:19:25.820> they<00:19:25.970> really<00:19:26.240> don't<00:19:26.389> and<00:19:26.659> so<00:19:26.749> the 00:19:26.859 --> 00:19:26.869 align:start position:0% now but they really don't and so the 00:19:26.869 --> 00:19:28.419 align:start position:0% now but they really don't and so the anyone<00:19:27.139> who's<00:19:27.320> just<00:19:27.350> has<00:19:27.679> a<00:19:27.710> public<00:19:27.950> dataset 00:19:28.419 --> 00:19:28.429 align:start position:0% anyone who's just has a public dataset 00:19:28.429 --> 00:19:31.330 align:start position:0% anyone who's just has a public dataset you<00:19:29.240> can<00:19:29.389> think<00:19:29.749> you're<00:19:30.320> safe<00:19:30.619> but<00:19:31.100> then<00:19:31.220> when 00:19:31.330 --> 00:19:31.340 align:start position:0% you can think you're safe but then when 00:19:31.340 --> 00:19:32.830 align:start position:0% you can think you're safe but then when you<00:19:31.429> start<00:19:31.700> working<00:19:32.029> at<00:19:32.090> sophisticated 00:19:32.830 --> 00:19:32.840 align:start position:0% you start working at sophisticated 00:19:32.840 --> 00:19:35.440 align:start position:0% you start working at sophisticated analysis<00:19:33.440> when<00:19:33.919> people<00:19:34.369> have<00:19:34.549> access<00:19:34.940> to<00:19:35.360> data 00:19:35.440 --> 00:19:35.450 align:start position:0% analysis when people have access to data 00:19:35.450 --> 00:19:38.230 align:start position:0% analysis when people have access to data it's<00:19:35.720> also<00:19:36.159> public<00:19:37.159> then<00:19:37.700> this<00:19:37.909> stuff<00:19:38.090> all 00:19:38.230 --> 00:19:38.240 align:start position:0% it's also public then this stuff all 00:19:38.240 --> 00:19:40.810 align:start position:0% it's also public then this stuff all breaks<00:19:38.509> down<00:19:38.600> and<00:19:39.110> it<00:19:39.230> seems<00:19:39.470> like<00:19:39.740> the<00:19:40.039> reader 00:19:40.810 --> 00:19:40.820 align:start position:0% breaks down and it seems like the reader 00:19:40.820 --> 00:19:43.330 align:start position:0% breaks down and it seems like the reader reaction<00:19:41.389> or<00:19:41.539> yeah<00:19:41.809> an<00:19:42.200> anticipation<00:19:42.710> of<00:19:42.980> GDP 00:19:43.330 --> 00:19:43.340 align:start position:0% reaction or yeah an anticipation of GDP 00:19:43.340 --> 00:19:44.769 align:start position:0% reaction or yeah an anticipation of GDP are<00:19:43.519> anything<00:19:43.879> else<00:19:44.090> is<00:19:44.299> someone<00:19:44.600> does 00:19:44.769 --> 00:19:44.779 align:start position:0% are anything else is someone does 00:19:44.779 --> 00:19:46.720 align:start position:0% are anything else is someone does something<00:19:44.809> completely<00:19:45.740> broken<00:19:46.460> piece<00:19:46.700> of 00:19:46.720 --> 00:19:46.730 align:start position:0% something completely broken piece of 00:19:46.730 --> 00:19:48.580 align:start position:0% something completely broken piece of cryptography<00:19:47.179> that's<00:19:47.629> like<00:19:47.779> good<00:19:47.990> enough<00:19:48.139> to 00:19:48.580 --> 00:19:48.590 align:start position:0% cryptography that's like good enough to 00:19:48.590 --> 00:19:50.980 align:start position:0% cryptography that's like good enough to get<00:19:48.740> past<00:19:48.950> compliance<00:19:49.639> until<00:19:50.570> five<00:19:50.749> years 00:19:50.980 --> 00:19:50.990 align:start position:0% get past compliance until five years 00:19:50.990 --> 00:19:52.149 align:start position:0% get past compliance until five years later<00:19:51.230> where<00:19:51.470> they<00:19:51.529> find<00:19:51.710> their<00:19:51.830> cousin 00:19:52.149 --> 00:19:52.159 align:start position:0% later where they find their cousin 00:19:52.159 --> 00:19:55.210 align:start position:0% later where they find their cousin actually<00:19:52.460> warning<00:19:52.789> yeah<00:19:53.590> so<00:19:54.590> I<00:19:54.860> wanna<00:19:55.009> speak 00:19:55.210 --> 00:19:55.220 align:start position:0% actually warning yeah so I wanna speak 00:19:55.220 --> 00:19:57.039 align:start position:0% actually warning yeah so I wanna speak to<00:19:55.340> this<00:19:55.460> one<00:19:55.669> because<00:19:55.999> I<00:19:56.240> was<00:19:56.539> at<00:19:56.840> one<00:19:57.019> point 00:19:57.039 --> 00:19:57.049 align:start position:0% to this one because I was at one point 00:19:57.049 --> 00:19:59.259 align:start position:0% to this one because I was at one point the<00:19:57.470> CTO<00:19:57.830> at<00:19:58.190> the<00:19:58.369> Federal<00:19:58.669> Trade<00:19:58.820> Commission 00:19:59.259 --> 00:19:59.269 align:start position:0% the CTO at the Federal Trade Commission 00:19:59.269 --> 00:20:01.840 align:start position:0% the CTO at the Federal Trade Commission which<00:19:59.450> is<00:19:59.629> the<00:19:59.860> US<00:20:00.860> government<00:20:01.249> agency<00:20:01.639> that 00:20:01.840 --> 00:20:01.850 align:start position:0% which is the US government agency that 00:20:01.850 --> 00:20:03.730 align:start position:0% which is the US government agency that is<00:20:02.090> most<00:20:02.480> responsible<00:20:03.139> for<00:20:03.350> enforcing 00:20:03.730 --> 00:20:03.740 align:start position:0% is most responsible for enforcing 00:20:03.740 --> 00:20:05.590 align:start position:0% is most responsible for enforcing privacy<00:20:04.159> laws<00:20:04.340> and<00:20:04.639> one<00:20:04.999> of<00:20:05.090> the<00:20:05.179> things<00:20:05.419> in 00:20:05.590 --> 00:20:05.600 align:start position:0% privacy laws and one of the things in 00:20:05.600 --> 00:20:07.359 align:start position:0% privacy laws and one of the things in that<00:20:05.779> wall<00:20:05.990> that<00:20:06.019> drove<00:20:06.409> me<00:20:06.559> absolutely<00:20:06.740> crazy 00:20:07.359 --> 00:20:07.369 align:start position:0% that wall that drove me absolutely crazy 00:20:07.369 --> 00:20:10.389 align:start position:0% that wall that drove me absolutely crazy was<00:20:08.090> when<00:20:08.119> companies<00:20:08.990> made<00:20:09.399> blatantly 00:20:10.389 --> 00:20:10.399 align:start position:0% was when companies made blatantly 00:20:10.399 --> 00:20:12.669 align:start position:0% was when companies made blatantly technically<00:20:10.999> false<00:20:11.299> statements<00:20:11.960> about<00:20:12.350> a 00:20:12.669 --> 00:20:12.679 align:start position:0% technically false statements about a 00:20:12.679 --> 00:20:15.430 align:start position:0% technically false statements about a privacy<00:20:13.369> protection<00:20:13.879> for<00:20:14.450> example<00:20:14.960> claiming 00:20:15.430 --> 00:20:15.440 align:start position:0% privacy protection for example claiming 00:20:15.440 --> 00:20:17.859 align:start position:0% privacy protection for example claiming that<00:20:15.679> we<00:20:16.009> only<00:20:16.159> store<00:20:16.580> the<00:20:16.610> hash<00:20:16.940> of<00:20:17.299> the<00:20:17.450> 32 00:20:17.859 --> 00:20:17.869 align:start position:0% that we only store the hash of the 32 00:20:17.869 --> 00:20:20.169 align:start position:0% that we only store the hash of the 32 bit<00:20:18.049> IP<00:20:18.230> address<00:20:18.740> therefore<00:20:19.549> we<00:20:19.700> have<00:20:19.789> no<00:20:19.999> way 00:20:20.169 --> 00:20:20.179 align:start position:0% bit IP address therefore we have no way 00:20:20.179 --> 00:20:22.029 align:start position:0% bit IP address therefore we have no way to<00:20:20.210> know<00:20:20.389> what<00:20:20.720> the<00:20:20.749> IP<00:20:20.960> address<00:20:21.169> is<00:20:21.440> or<00:20:21.799> even 00:20:22.029 --> 00:20:22.039 align:start position:0% to know what the IP address is or even 00:20:22.039 --> 00:20:24.039 align:start position:0% to know what the IP address is or even people<00:20:22.190> who<00:20:22.429> claim<00:20:22.669> we<00:20:23.210> have<00:20:23.240> the<00:20:23.509> hash<00:20:23.690> of<00:20:23.960> the 00:20:24.039 --> 00:20:24.049 align:start position:0% people who claim we have the hash of the 00:20:24.049 --> 00:20:27.070 align:start position:0% people who claim we have the hash of the 10-digit<00:20:24.409> phone<00:20:24.619> number<00:20:25.159> and<00:20:25.340> therefore<00:20:25.820> we 00:20:27.070 --> 00:20:27.080 align:start position:0% 10-digit phone number and therefore we 00:20:27.080 --> 00:20:29.379 align:start position:0% 10-digit phone number and therefore we but<00:20:27.860> it<00:20:27.980> is<00:20:28.159> and<00:20:28.610> saying<00:20:28.999> that<00:20:29.179> with<00:20:29.360> a 00:20:29.379 --> 00:20:29.389 align:start position:0% but it is and saying that with a 00:20:29.389 --> 00:20:30.700 align:start position:0% but it is and saying that with a straight<00:20:29.509> face<00:20:29.809> I've<00:20:30.350> seen<00:20:30.379> your 00:20:30.700 --> 00:20:30.710 align:start position:0% straight face I've seen your 00:20:30.710 --> 00:20:35.350 align:start position:0% straight face I've seen your policymakers<00:20:31.509> and<00:20:32.649> so<00:20:33.649> I<00:20:34.610> think<00:20:34.970> over<00:20:35.330> time 00:20:35.350 --> 00:20:35.360 align:start position:0% policymakers and so I think over time 00:20:35.360 --> 00:20:37.570 align:start position:0% policymakers and so I think over time governments<00:20:36.289> can<00:20:36.619> get<00:20:36.919> smarter<00:20:37.399> they're 00:20:37.570 --> 00:20:37.580 align:start position:0% governments can get smarter they're 00:20:37.580 --> 00:20:40.060 align:start position:0% governments can get smarter they're hiring<00:20:37.759> people<00:20:37.940> who<00:20:38.299> know<00:20:38.659> how<00:20:38.899> to<00:20:38.960> call<00:20:39.559> BS<00:20:39.889> on 00:20:40.060 --> 00:20:40.070 align:start position:0% hiring people who know how to call BS on 00:20:40.070 --> 00:20:42.279 align:start position:0% hiring people who know how to call BS on those<00:20:40.279> things<00:20:40.549> I<00:20:40.820> mean<00:20:41.659> that's<00:20:41.840> part<00:20:42.049> of<00:20:42.169> it 00:20:42.279 --> 00:20:42.289 align:start position:0% those things I mean that's part of it 00:20:42.289 --> 00:20:44.200 align:start position:0% those things I mean that's part of it right<00:20:42.470> part<00:20:42.830> of<00:20:42.889> it<00:20:43.039> is<00:20:43.279> we<00:20:43.580> have<00:20:43.730> to<00:20:43.759> create<00:20:44.059> an 00:20:44.200 --> 00:20:44.210 align:start position:0% right part of it is we have to create an 00:20:44.210 --> 00:20:46.029 align:start position:0% right part of it is we have to create an environment<00:20:44.779> where<00:20:44.929> people<00:20:45.259> just<00:20:45.440> can't<00:20:45.799> get 00:20:46.029 --> 00:20:46.039 align:start position:0% environment where people just can't get 00:20:46.039 --> 00:20:48.580 align:start position:0% environment where people just can't get away<00:20:46.129> with<00:20:46.610> bogus<00:20:47.360> arguments<00:20:47.899> about<00:20:47.989> privacy 00:20:48.580 --> 00:20:48.590 align:start position:0% away with bogus arguments about privacy 00:20:48.590 --> 00:20:51.970 align:start position:0% away with bogus arguments about privacy right<00:20:49.159> and<00:20:49.460> we<00:20:50.029> need<00:20:50.299> to<00:20:50.450> call<00:20:50.659> them<00:20:50.809> out<00:20:51.019> if 00:20:51.970 --> 00:20:51.980 align:start position:0% right and we need to call them out if 00:20:51.980 --> 00:20:53.590 align:start position:0% right and we need to call them out if somebody's<00:20:52.399> making<00:20:52.429> a<00:20:52.789> bogus<00:20:53.119> privacy 00:20:53.590 --> 00:20:53.600 align:start position:0% somebody's making a bogus privacy 00:20:53.600 --> 00:20:55.389 align:start position:0% somebody's making a bogus privacy argument<00:20:53.779> they<00:20:54.320> should<00:20:54.619> be<00:20:54.769> called<00:20:55.009> out<00:20:55.190> by 00:20:55.389 --> 00:20:55.399 align:start position:0% argument they should be called out by 00:20:55.399 --> 00:20:57.460 align:start position:0% argument they should be called out by their<00:20:55.610> peers<00:20:55.820> publicly<00:20:56.419> and<00:20:57.169> it<00:20:57.259> should 00:20:57.460 --> 00:20:57.470 align:start position:0% their peers publicly and it should 00:20:57.470 --> 00:20:59.229 align:start position:0% their peers publicly and it should affect<00:20:57.559> their<00:20:57.950> reputation<00:20:58.220> governments<00:20:59.090> will 00:20:59.229 --> 00:20:59.239 align:start position:0% affect their reputation governments will 00:20:59.239 --> 00:21:00.399 align:start position:0% affect their reputation governments will listen<00:20:59.389> to<00:20:59.629> that<00:20:59.779> stuff 00:21:00.399 --> 00:21:00.409 align:start position:0% listen to that stuff 00:21:00.409 --> 00:21:02.259 align:start position:0% listen to that stuff but<00:21:00.769> most<00:21:01.100> people<00:21:01.429> but<00:21:01.609> more<00:21:01.789> importantly 00:21:02.259 --> 00:21:02.269 align:start position:0% but most people but more importantly 00:21:02.269 --> 00:21:04.119 align:start position:0% but most people but more importantly prospective<00:21:02.899> employers<00:21:03.470> perspective 00:21:04.119 --> 00:21:04.129 align:start position:0% prospective employers perspective 00:21:04.129 --> 00:21:06.369 align:start position:0% prospective employers perspective investors<00:21:04.279> and<00:21:04.850> so<00:21:04.999> on<00:21:05.210> will<00:21:05.720> listen<00:21:05.869> as<00:21:06.109> well 00:21:06.369 --> 00:21:06.379 align:start position:0% investors and so on will listen as well 00:21:06.379 --> 00:21:08.799 align:start position:0% investors and so on will listen as well it's<00:21:06.859> sort<00:21:07.039> of<00:21:07.070> up<00:21:07.309> to<00:21:07.460> us<00:21:07.639> to<00:21:07.999> copy<00:21:08.239> us<00:21:08.480> on<00:21:08.690> each 00:21:08.799 --> 00:21:08.809 align:start position:0% it's sort of up to us to copy us on each 00:21:08.809 --> 00:21:10.479 align:start position:0% it's sort of up to us to copy us on each other<00:21:09.049> when<00:21:09.289> somebody<00:21:09.710> is<00:21:09.830> saying<00:21:10.009> something 00:21:10.479 --> 00:21:10.489 align:start position:0% other when somebody is saying something 00:21:10.489 --> 00:21:13.029 align:start position:0% other when somebody is saying something that<00:21:10.690> it's<00:21:11.690> really<00:21:12.169> misleading<00:21:12.409> to<00:21:12.889> their 00:21:13.029 --> 00:21:13.039 align:start position:0% that it's really misleading to their 00:21:13.039 --> 00:21:16.720 align:start position:0% that it's really misleading to their customers<00:21:14.019> so<00:21:15.019> besides<00:21:15.649> some<00:21:16.129> the<00:21:16.549> good 00:21:16.720 --> 00:21:16.730 align:start position:0% customers so besides some the good 00:21:16.730 --> 00:21:18.820 align:start position:0% customers so besides some the good nature<00:21:16.970> of<00:21:17.419> developers<00:21:18.259> in<00:21:18.350> the<00:21:18.409> community 00:21:18.820 --> 00:21:18.830 align:start position:0% nature of developers in the community 00:21:18.830 --> 00:21:20.440 align:start position:0% nature of developers in the community saying<00:21:19.669> that<00:21:19.850> they're<00:21:19.970> not<00:21:19.999> going<00:21:20.389> to 00:21:20.440 --> 00:21:20.450 align:start position:0% saying that they're not going to 00:21:20.450 --> 00:21:21.940 align:start position:0% saying that they're not going to personal<00:21:21.289> data<00:21:21.470> and<00:21:21.649> they<00:21:21.739> care<00:21:21.889> about 00:21:21.940 --> 00:21:21.950 align:start position:0% personal data and they care about 00:21:21.950 --> 00:21:26.590 align:start position:0% personal data and they care about privacy<00:21:22.629> also<00:21:23.629> government<00:21:24.440> regulations<00:21:25.600> and 00:21:26.590 --> 00:21:26.600 align:start position:0% privacy also government regulations and 00:21:26.600 --> 00:21:30.460 align:start position:0% privacy also government regulations and these<00:21:27.340> are<00:21:28.340> and<00:21:28.549> also<00:21:29.090> just<00:21:29.350> catching<00:21:30.350> each 00:21:30.460 --> 00:21:30.470 align:start position:0% these are and also just catching each 00:21:30.470 --> 00:21:33.399 align:start position:0% these are and also just catching each other<00:21:30.850> on<00:21:31.850> each<00:21:31.999> other<00:21:32.210> what<00:21:32.749> else<00:21:32.960> can<00:21:33.139> we<00:21:33.259> do 00:21:33.399 --> 00:21:33.409 align:start position:0% other on each other what else can we do 00:21:33.409 --> 00:21:47.830 align:start position:0% other on each other what else can we do to<00:21:33.590> incentivize<00:21:34.840> privacy<00:21:35.840> be<00:21:35.989> effective 00:21:47.830 --> 00:21:47.840 align:start position:0% 00:21:47.840 --> 00:21:49.960 align:start position:0% well<00:21:48.380> I<00:21:48.410> guess<00:21:48.980> this<00:21:49.130> will<00:21:49.280> go<00:21:49.550> back<00:21:49.700> to<00:21:49.850> my 00:21:49.960 --> 00:21:49.970 align:start position:0% well I guess this will go back to my 00:21:49.970 --> 00:21:52.630 align:start position:0% well I guess this will go back to my previous<00:21:50.510> might<00:21:51.020> a<00:21:51.260> little<00:21:51.320> bit<00:21:51.650> but<00:21:51.950> you 00:21:52.630 --> 00:21:52.640 align:start position:0% previous might a little bit but you 00:21:52.640 --> 00:21:54.280 align:start position:0% previous might a little bit but you really<00:21:52.970> have<00:21:53.090> to<00:21:53.120> make<00:21:53.420> to<00:21:53.720> get<00:21:53.870> major<00:21:54.080> the 00:21:54.280 --> 00:21:54.290 align:start position:0% really have to make to get major the 00:21:54.290 --> 00:21:57.430 align:start position:0% really have to make to get major the users<00:21:54.620> want<00:21:55.040> it<00:21:55.250> like<00:21:56.090> I<00:21:56.240> honestly<00:21:56.750> think<00:21:57.290> that 00:21:57.430 --> 00:21:57.440 align:start position:0% users want it like I honestly think that 00:21:57.440 --> 00:21:59.440 align:start position:0% users want it like I honestly think that if<00:21:57.740> you<00:21:57.920> so<00:21:58.640> there<00:21:58.790> they're<00:21:59.090> all<00:21:59.180> these<00:21:59.330> two 00:21:59.440 --> 00:21:59.450 align:start position:0% if you so there they're all these two 00:21:59.450 --> 00:22:01.630 align:start position:0% if you so there they're all these two external<00:21:59.780> incentives<00:22:00.410> and<00:22:00.620> and<00:22:01.100> but<00:22:01.460> one 00:22:01.630 --> 00:22:01.640 align:start position:0% external incentives and and but one 00:22:01.640 --> 00:22:03.070 align:start position:0% external incentives and and but one thing<00:22:01.880> that<00:22:01.910> people<00:22:02.690> should<00:22:02.840> be 00:22:03.070 --> 00:22:03.080 align:start position:0% thing that people should be 00:22:03.080 --> 00:22:05.230 align:start position:0% thing that people should be intrinsically<00:22:03.800> motivated<00:22:04.490> about<00:22:04.760> at<00:22:05.090> least 00:22:05.230 --> 00:22:05.240 align:start position:0% intrinsically motivated about at least 00:22:05.240 --> 00:22:07.630 align:start position:0% intrinsically motivated about at least you<00:22:05.900> know<00:22:06.020> as<00:22:06.110> it<00:22:06.260> as<00:22:06.380> an<00:22:06.500> American<00:22:07.250> coming 00:22:07.630 --> 00:22:07.640 align:start position:0% you know as it as an American coming 00:22:07.640 --> 00:22:09.490 align:start position:0% you know as it as an American coming from<00:22:07.820> this<00:22:08.150> sort<00:22:08.330> of<00:22:08.360> constitutional<00:22:09.290> rights 00:22:09.490 --> 00:22:09.500 align:start position:0% from this sort of constitutional rights 00:22:09.500 --> 00:22:12.460 align:start position:0% from this sort of constitutional rights perspective<00:22:09.860> like<00:22:10.520> you<00:22:11.390> should<00:22:11.570> care<00:22:12.200> about<00:22:12.230> a 00:22:12.460 --> 00:22:12.470 align:start position:0% perspective like you should care about a 00:22:12.470 --> 00:22:14.140 align:start position:0% perspective like you should care about a Fourth<00:22:12.770> Amendment<00:22:12.830> rights<00:22:13.310> care<00:22:13.580> about<00:22:13.820> us<00:22:13.970> or 00:22:14.140 --> 00:22:14.150 align:start position:0% Fourth Amendment rights care about us or 00:22:14.150 --> 00:22:17.380 align:start position:0% Fourth Amendment rights care about us or right<00:22:14.690> two<00:22:15.020> fundamental<00:22:15.800> privacy<00:22:16.370> that<00:22:17.000> is 00:22:17.380 --> 00:22:17.390 align:start position:0% right two fundamental privacy that is 00:22:17.390 --> 00:22:19.780 align:start position:0% right two fundamental privacy that is enshrined<00:22:17.870> by<00:22:18.320> these<00:22:19.190> fundamental<00:22:19.700> legal 00:22:19.780 --> 00:22:19.790 align:start position:0% enshrined by these fundamental legal 00:22:19.790 --> 00:22:25.150 align:start position:0% enshrined by these fundamental legal rights<00:22:21.970> but<00:22:22.970> I<00:22:23.330> do<00:22:24.050> agree<00:22:24.320> that<00:22:24.590> oftentimes 00:22:25.150 --> 00:22:25.160 align:start position:0% rights but I do agree that oftentimes 00:22:25.160 --> 00:22:27.160 align:start position:0% rights but I do agree that oftentimes like<00:22:25.520> in<00:22:25.700> practice<00:22:26.150> I<00:22:26.330> think<00:22:26.390> the<00:22:26.690> user<00:22:26.900> has 00:22:27.160 --> 00:22:27.170 align:start position:0% like in practice I think the user has 00:22:27.170 --> 00:22:29.320 align:start position:0% like in practice I think the user has created<00:22:27.470> bad<00:22:27.890> trade-offs<00:22:28.340> there<00:22:28.580> is<00:22:29.060> one 00:22:29.320 --> 00:22:29.330 align:start position:0% created bad trade-offs there is one 00:22:29.330 --> 00:22:31.300 align:start position:0% created bad trade-offs there is one service<00:22:29.720> that<00:22:29.750> is<00:22:30.110> very<00:22:30.200> nice<00:22:30.530> and<00:22:30.890> easy<00:22:31.070> to 00:22:31.300 --> 00:22:31.310 align:start position:0% service that is very nice and easy to 00:22:31.310 --> 00:22:33.730 align:start position:0% service that is very nice and easy to use<00:22:31.360> it<00:22:32.360> doesn't<00:22:32.390> care<00:22:32.810> about<00:22:33.020> privacy<00:22:33.260> and 00:22:33.730 --> 00:22:33.740 align:start position:0% use it doesn't care about privacy and 00:22:33.740 --> 00:22:36.040 align:start position:0% use it doesn't care about privacy and then<00:22:34.070> you<00:22:34.220> can<00:22:34.430> do<00:22:34.610> see<00:22:35.420> cash<00:22:35.660> legal 00:22:36.040 --> 00:22:36.050 align:start position:0% then you can do see cash legal 00:22:36.050 --> 00:22:38.380 align:start position:0% then you can do see cash legal transaction<00:22:36.590> which<00:22:36.800> is<00:22:36.980> very<00:22:37.700> complex<00:22:38.180> in 00:22:38.380 --> 00:22:38.390 align:start position:0% transaction which is very complex in 00:22:38.390 --> 00:22:41.200 align:start position:0% transaction which is very complex in comparison<00:22:38.900> to<00:22:38.930> paintball<00:22:39.500> right<00:22:39.770> so<00:22:40.220> I<00:22:40.580> think 00:22:41.200 --> 00:22:41.210 align:start position:0% comparison to paintball right so I think 00:22:41.210 --> 00:22:42.880 align:start position:0% comparison to paintball right so I think it's<00:22:41.510> maybe<00:22:42.050> that's<00:22:42.320> not<00:22:42.440> the<00:22:42.500> best<00:22:42.770> example 00:22:42.880 --> 00:22:42.890 align:start position:0% it's maybe that's not the best example 00:22:42.890 --> 00:22:44.800 align:start position:0% it's maybe that's not the best example but<00:22:43.340> it's<00:22:43.430> also<00:22:43.580> like<00:22:43.820> just<00:22:43.850> clicking<00:22:44.270> except 00:22:44.800 --> 00:22:44.810 align:start position:0% but it's also like just clicking except 00:22:44.810 --> 00:22:46.720 align:start position:0% but it's also like just clicking except on<00:22:45.110> the<00:22:45.200> website<00:22:45.620> for<00:22:45.950> something<00:22:46.250> so<00:22:46.400> we<00:22:46.520> need 00:22:46.720 --> 00:22:46.730 align:start position:0% on the website for something so we need 00:22:46.730 --> 00:22:48.730 align:start position:0% on the website for something so we need to<00:22:47.180> provide<00:22:47.630> better<00:22:47.690> trade<00:22:48.230> also<00:22:48.530> maybe 00:22:48.730 --> 00:22:48.740 align:start position:0% to provide better trade also maybe 00:22:48.740 --> 00:22:51.040 align:start position:0% to provide better trade also maybe regulatory<00:22:49.490> force<00:22:49.970> people<00:22:50.300> to<00:22:50.510> let<00:22:50.870> better 00:22:51.040 --> 00:22:51.050 align:start position:0% regulatory force people to let better 00:22:51.050 --> 00:22:53.830 align:start position:0% regulatory force people to let better chance<00:22:51.380> I<00:22:51.880> think<00:22:52.880> we<00:22:52.970> also<00:22:53.360> need<00:22:53.510> to<00:22:53.690> provide 00:22:53.830 --> 00:22:53.840 align:start position:0% chance I think we also need to provide 00:22:53.840 --> 00:22:57.070 align:start position:0% chance I think we also need to provide better<00:22:54.170> attacks<00:22:55.420> it'd<00:22:56.420> be<00:22:56.600> really<00:22:56.810> good<00:22:57.020> to 00:22:57.070 --> 00:22:57.080 align:start position:0% better attacks it'd be really good to 00:22:57.080 --> 00:22:59.560 align:start position:0% better attacks it'd be really good to demonstrate<00:22:57.980> to<00:22:58.100> people<00:22:58.250> watching<00:22:58.730> off<00:22:59.000> so<00:22:59.540> a 00:22:59.560 --> 00:22:59.570 align:start position:0% demonstrate to people watching off so a 00:22:59.570 --> 00:23:02.170 align:start position:0% demonstrate to people watching off so a good<00:22:59.840> example<00:22:59.960> this<00:23:00.380> is<00:23:00.670> didn't<00:23:01.670> know<00:23:01.790> which 00:23:02.170 --> 00:23:02.180 align:start position:0% good example this is didn't know which 00:23:02.180 --> 00:23:03.970 align:start position:0% good example this is didn't know which us<00:23:02.840> is<00:23:02.990> an<00:23:03.080> app<00:23:03.200> used 00:23:03.970 --> 00:23:03.980 align:start position:0% us is an app used 00:23:03.980 --> 00:23:05.380 align:start position:0% us is an app used it's<00:23:04.280> for<00:23:04.460> dinner<00:23:04.640> that's<00:23:04.850> we<00:23:05.030> don't<00:23:05.150> have<00:23:05.360> a 00:23:05.380 --> 00:23:05.390 align:start position:0% it's for dinner that's we don't have a 00:23:05.390 --> 00:23:06.909 align:start position:0% it's for dinner that's we don't have a good<00:23:05.570> banking<00:23:05.870> system<00:23:06.230> to<00:23:06.260> transfer<00:23:06.620> money 00:23:06.909 --> 00:23:06.919 align:start position:0% good banking system to transfer money 00:23:06.919 --> 00:23:11.470 align:start position:0% good banking system to transfer money that<00:23:07.220> way<00:23:07.370> and<00:23:09.520> for<00:23:10.520> a<00:23:10.580> long<00:23:10.760> time<00:23:11.030> for<00:23:11.210> much<00:23:11.330> of 00:23:11.470 --> 00:23:11.480 align:start position:0% that way and for a long time for much of 00:23:11.480 --> 00:23:13.480 align:start position:0% that way and for a long time for much of people<00:23:11.809> knew<00:23:12.169> that<00:23:12.440> bill<00:23:12.590> had<00:23:12.919> this<00:23:13.070> default 00:23:13.480 --> 00:23:13.490 align:start position:0% people knew that bill had this default 00:23:13.490 --> 00:23:16.299 align:start position:0% people knew that bill had this default public<00:23:14.110> each<00:23:15.110> other<00:23:15.320> literally<00:23:15.710> was<00:23:15.980> Twitter 00:23:16.299 --> 00:23:16.309 align:start position:0% public each other literally was Twitter 00:23:16.309 --> 00:23:17.680 align:start position:0% public each other literally was Twitter for<00:23:16.460> your<00:23:16.580> bank<00:23:16.700> account<00:23:17.059> was<00:23:17.210> a<00:23:17.240> web<00:23:17.450> pages 00:23:17.680 --> 00:23:17.690 align:start position:0% for your bank account was a web pages 00:23:17.690 --> 00:23:19.270 align:start position:0% for your bank account was a web pages where<00:23:17.960> he<00:23:18.140> understood<00:23:18.590> everything<00:23:18.799> that<00:23:19.070> one 00:23:19.270 --> 00:23:19.280 align:start position:0% where he understood everything that one 00:23:19.280 --> 00:23:22.600 align:start position:0% where he understood everything that one bit<00:23:19.630> but<00:23:20.630> we<00:23:21.020> were<00:23:21.140> all<00:23:21.290> showing<00:23:21.650> me<00:23:21.980> win<00:23:22.250> and 00:23:22.600 --> 00:23:22.610 align:start position:0% bit but we were all showing me win and 00:23:22.610 --> 00:23:24.820 align:start position:0% bit but we were all showing me win and then<00:23:22.760> someone<00:23:23.150> made<00:23:23.299> an<00:23:23.480> art<00:23:23.720> project<00:23:24.020> where 00:23:24.820 --> 00:23:24.830 align:start position:0% then someone made an art project where 00:23:24.830 --> 00:23:26.350 align:start position:0% then someone made an art project where they<00:23:24.980> have<00:23:25.160> this<00:23:25.309> website<00:23:25.880> with<00:23:26.059> all<00:23:26.179> this 00:23:26.350 --> 00:23:26.360 align:start position:0% they have this website with all this 00:23:26.360 --> 00:23:28.690 align:start position:0% they have this website with all this stuff<00:23:26.630> on<00:23:26.809> it<00:23:26.990> and<00:23:27.410> an<00:23:27.500> era<00:23:27.710> and<00:23:28.190> all<00:23:28.549> of<00:23:28.640> a 00:23:28.690 --> 00:23:28.700 align:start position:0% stuff on it and an era and all of a 00:23:28.700 --> 00:23:30.490 align:start position:0% stuff on it and an era and all of a sudden<00:23:28.730> people<00:23:29.210> started<00:23:29.690> caring<00:23:30.020> about<00:23:30.200> this 00:23:30.490 --> 00:23:30.500 align:start position:0% sudden people started caring about this 00:23:30.500 --> 00:23:32.409 align:start position:0% sudden people started caring about this and<00:23:30.799> so<00:23:30.919> similarly<00:23:31.250> for<00:23:31.340> watching<00:23:32.000> I<00:23:32.150> think<00:23:32.179> we 00:23:32.409 --> 00:23:32.419 align:start position:0% and so similarly for watching I think we 00:23:32.419 --> 00:23:35.049 align:start position:0% and so similarly for watching I think we actually<00:23:32.840> never<00:23:32.990> go<00:23:33.290> writing<00:23:33.770> tools<00:23:34.669> but 00:23:35.049 --> 00:23:35.059 align:start position:0% actually never go writing tools but 00:23:35.059 --> 00:23:37.510 align:start position:0% actually never go writing tools but advise<00:23:35.299> your<00:23:35.630> eyes<00:23:35.750> look<00:23:36.350> your<00:23:36.950> something<00:23:37.400> in 00:23:37.510 --> 00:23:37.520 align:start position:0% advise your eyes look your something in 00:23:37.520 --> 00:23:39.220 align:start position:0% advise your eyes look your something in there<00:23:37.700> you<00:23:37.790> can<00:23:37.940> find<00:23:38.150> out<00:23:38.360> about<00:23:38.450> you<00:23:38.809> don't 00:23:39.220 --> 00:23:39.230 align:start position:0% there you can find out about you don't 00:23:39.230 --> 00:23:41.200 align:start position:0% there you can find out about you don't you<00:23:39.410> music<00:23:39.770> wish<00:23:39.950> you<00:23:40.160> have<00:23:40.340> made<00:23:40.640> this<00:23:40.760> a<00:23:40.820> sec 00:23:41.200 --> 00:23:41.210 align:start position:0% you music wish you have made this a sec 00:23:41.210 --> 00:23:43.840 align:start position:0% you music wish you have made this a sec right<00:23:42.169> and<00:23:42.500> until<00:23:42.740> we<00:23:43.040> do<00:23:43.160> that<00:23:43.190> it's<00:23:43.580> just<00:23:43.760> a 00:23:43.840 --> 00:23:43.850 align:start position:0% right and until we do that it's just a 00:23:43.850 --> 00:23:45.580 align:start position:0% right and until we do that it's just a hypothetical<00:23:44.120> oh<00:23:44.480> I<00:23:44.660> can<00:23:44.960> tell<00:23:45.169> you<00:23:45.320> that<00:23:45.470> my 00:23:45.580 --> 00:23:45.590 align:start position:0% hypothetical oh I can tell you that my 00:23:45.590 --> 00:23:47.230 align:start position:0% hypothetical oh I can tell you that my arrow<00:23:45.770> is<00:23:45.860> work<00:23:46.280> well<00:23:46.549> I<00:23:46.580> can<00:23:46.880> tell<00:23:47.030> you<00:23:47.090> that 00:23:47.230 --> 00:23:47.240 align:start position:0% arrow is work well I can tell you that 00:23:47.240 --> 00:23:50.710 align:start position:0% arrow is work well I can tell you that this<00:23:47.419> vessel<00:23:47.600> back<00:23:48.380> up<00:23:48.559> it<00:23:49.220> it's<00:23:49.970> not<00:23:50.150> really<00:23:50.540> I 00:23:50.710 --> 00:23:50.720 align:start position:0% this vessel back up it it's not really I 00:23:50.720 --> 00:23:53.110 align:start position:0% this vessel back up it it's not really I mean<00:23:51.020> another<00:23:51.590> thing<00:23:51.860> we<00:23:52.010> can<00:23:52.160> do<00:23:52.400> is<00:23:52.669> give 00:23:53.110 --> 00:23:53.120 align:start position:0% mean another thing we can do is give 00:23:53.120 --> 00:23:54.730 align:start position:0% mean another thing we can do is give users<00:23:53.419> some<00:23:54.230> hope 00:23:54.730 --> 00:23:54.740 align:start position:0% users some hope 00:23:54.740 --> 00:23:57.430 align:start position:0% users some hope I<00:23:54.770> think<00:23:55.610> most<00:23:55.850> users<00:23:56.240> most<00:23:56.600> of<00:23:56.809> the<00:23:56.929> time<00:23:57.169> when 00:23:57.430 --> 00:23:57.440 align:start position:0% I think most users most of the time when 00:23:57.440 --> 00:23:58.930 align:start position:0% I think most users most of the time when they<00:23:57.530> use<00:23:57.710> technology<00:23:57.919> just<00:23:58.669> said<00:23:58.820> this 00:23:58.930 --> 00:23:58.940 align:start position:0% they use technology just said this 00:23:58.940 --> 00:24:01.870 align:start position:0% they use technology just said this fatalistic<00:23:59.630> attitude<00:23:59.950> whatever<00:24:00.950> I<00:24:01.040> do<00:24:01.220> my 00:24:01.870 --> 00:24:01.880 align:start position:0% fatalistic attitude whatever I do my 00:24:01.880 --> 00:24:04.360 align:start position:0% fatalistic attitude whatever I do my date<00:24:02.090> is<00:24:02.240> going<00:24:02.450> to<00:24:02.540> go<00:24:02.720> everywhere<00:24:03.140> right<00:24:04.100> and 00:24:04.360 --> 00:24:04.370 align:start position:0% date is going to go everywhere right and 00:24:04.370 --> 00:24:05.980 align:start position:0% date is going to go everywhere right and so<00:24:04.640> it<00:24:04.850> doesn't<00:24:05.030> really<00:24:05.299> matter<00:24:05.570> what<00:24:05.929> I 00:24:05.980 --> 00:24:05.990 align:start position:0% so it doesn't really matter what I 00:24:05.990 --> 00:24:07.780 align:start position:0% so it doesn't really matter what I choose<00:24:06.080> people<00:24:06.679> don't<00:24:06.919> really<00:24:07.130> believe<00:24:07.280> that 00:24:07.780 --> 00:24:07.790 align:start position:0% choose people don't really believe that 00:24:07.790 --> 00:24:09.669 align:start position:0% choose people don't really believe that if<00:24:07.880> they<00:24:08.000> choose<00:24:08.179> product<00:24:08.690> Abril<00:24:09.110> and<00:24:09.350> product 00:24:09.669 --> 00:24:09.679 align:start position:0% if they choose product Abril and product 00:24:09.679 --> 00:24:12.039 align:start position:0% if they choose product Abril and product B<00:24:09.860> they'll<00:24:10.400> be<00:24:10.610> in<00:24:10.700> them<00:24:10.880> they'll<00:24:11.600> be<00:24:11.780> in<00:24:11.900> a 00:24:12.039 --> 00:24:12.049 align:start position:0% B they'll be in them they'll be in a 00:24:12.049 --> 00:24:13.780 align:start position:0% B they'll be in them they'll be in a significantly<00:24:12.890> better<00:24:13.100> position<00:24:13.610> with 00:24:13.780 --> 00:24:13.790 align:start position:0% significantly better position with 00:24:13.790 --> 00:24:17.289 align:start position:0% significantly better position with respect<00:24:13.910> to<00:24:14.210> privacy<00:24:14.950> and<00:24:15.950> in<00:24:16.730> that<00:24:16.970> kind<00:24:17.240> of 00:24:17.289 --> 00:24:17.299 align:start position:0% respect to privacy and in that kind of 00:24:17.299 --> 00:24:20.169 align:start position:0% respect to privacy and in that kind of environment<00:24:17.480> if<00:24:18.080> there<00:24:18.500> is<00:24:18.799> a<00:24:19.130> product<00:24:19.790> a 00:24:20.169 --> 00:24:20.179 align:start position:0% environment if there is a product a 00:24:20.179 --> 00:24:22.990 align:start position:0% environment if there is a product a stack<00:24:20.929> if<00:24:21.679> there<00:24:21.980> is<00:24:22.100> some<00:24:22.370> environment 00:24:22.990 --> 00:24:23.000 align:start position:0% stack if there is some environment 00:24:23.000 --> 00:24:24.549 align:start position:0% stack if there is some environment that's<00:24:23.120> available<00:24:23.330> to<00:24:23.660> people<00:24:23.809> that<00:24:24.110> actually 00:24:24.549 --> 00:24:24.559 align:start position:0% that's available to people that actually 00:24:24.559 --> 00:24:30.130 align:start position:0% that's available to people that actually does<00:24:24.830> offer<00:24:25.100> better<00:24:25.370> privacy<00:24:25.940> and<00:24:26.870> we<00:24:29.140> talked 00:24:30.130 --> 00:24:30.140 align:start position:0% does offer better privacy and we talked 00:24:30.140 --> 00:24:32.650 align:start position:0% does offer better privacy and we talked about<00:24:30.169> the<00:24:30.710> idea<00:24:31.160> that<00:24:31.250> it<00:24:31.549> is<00:24:31.700> possible<00:24:32.390> to<00:24:32.419> do 00:24:32.650 --> 00:24:32.660 align:start position:0% about the idea that it is possible to do 00:24:32.660 --> 00:24:36.880 align:start position:0% about the idea that it is possible to do this<00:24:33.280> because<00:24:34.280> I<00:24:34.820> think<00:24:35.090> in<00:24:35.510> the<00:24:35.750> in<00:24:36.679> the 00:24:36.880 --> 00:24:36.890 align:start position:0% this because I think in the in the 00:24:36.890 --> 00:24:39.370 align:start position:0% this because I think in the in the legacy<00:24:37.070> tech<00:24:37.580> space<00:24:37.880> their<00:24:38.570> narrative<00:24:39.200> that 00:24:39.370 --> 00:24:39.380 align:start position:0% legacy tech space their narrative that 00:24:39.380 --> 00:24:42.700 align:start position:0% legacy tech space their narrative that you<00:24:39.530> hear<00:24:39.890> is<00:24:40.090> that<00:24:41.110> you<00:24:42.110> know<00:24:42.230> we<00:24:42.380> really 00:24:42.700 --> 00:24:42.710 align:start position:0% you hear is that you know we really 00:24:42.710 --> 00:24:44.380 align:start position:0% you hear is that you know we really don't<00:24:42.919> want<00:24:43.280> to<00:24:43.340> have<00:24:43.490> all<00:24:43.669> your<00:24:43.700> data<00:24:44.000> but<00:24:44.270> we 00:24:44.380 --> 00:24:44.390 align:start position:0% don't want to have all your data but we 00:24:44.390 --> 00:24:46.060 align:start position:0% don't want to have all your data but we just<00:24:44.510> need<00:24:44.809> it<00:24:44.960> to<00:24:44.990> run<00:24:45.290> our<00:24:45.440> business<00:24:45.470> it's 00:24:46.060 --> 00:24:46.070 align:start position:0% just need it to run our business it's 00:24:46.070 --> 00:24:47.770 align:start position:0% just need it to run our business it's just<00:24:46.160> a<00:24:46.490> thing<00:24:46.700> that's<00:24:46.910> necessary<00:24:47.510> to<00:24:47.750> make 00:24:47.770 --> 00:24:47.780 align:start position:0% just a thing that's necessary to make 00:24:47.780 --> 00:24:51.539 align:start position:0% just a thing that's necessary to make the<00:24:48.049> sector<00:24:48.440> go<00:24:48.880> and<00:24:49.880> I<00:24:50.510> don't<00:24:50.780> think<00:24:50.929> that's 00:24:51.539 --> 00:24:51.549 align:start position:0% the sector go and I don't think that's 00:24:51.549 --> 00:24:54.299 align:start position:0% the sector go and I don't think that's true<00:24:52.149> but<00:24:52.720> to<00:24:52.899> the<00:24:53.019> extent<00:24:53.440> that<00:24:53.559> this<00:24:53.889> is<00:24:54.129> the 00:24:54.299 --> 00:24:54.309 align:start position:0% true but to the extent that this is the 00:24:54.309 --> 00:24:56.820 align:start position:0% true but to the extent that this is the way<00:24:54.489> that<00:24:54.820> our<00:24:55.090> community<00:24:55.659> talks<00:24:55.929> about<00:24:56.259> these 00:24:56.820 --> 00:24:56.830 align:start position:0% way that our community talks about these 00:24:56.830 --> 00:24:58.889 align:start position:0% way that our community talks about these things<00:24:57.159> we<00:24:57.909> will<00:24:57.940> make<00:24:58.239> it<00:24:58.419> true 00:24:58.889 --> 00:24:58.899 align:start position:0% things we will make it true 00:24:58.899 --> 00:25:01.379 align:start position:0% things we will make it true so<00:24:59.860> we<00:25:00.009> need<00:25:00.129> to<00:25:00.220> work<00:25:00.369> hard<00:25:00.639> I<00:25:00.820> think<00:25:01.029> to<00:25:01.239> try 00:25:01.379 --> 00:25:01.389 align:start position:0% so we need to work hard I think to try 00:25:01.389 --> 00:25:03.690 align:start position:0% so we need to work hard I think to try to<00:25:01.480> give<00:25:01.749> users<00:25:01.960> hope<00:25:02.320> and<00:25:02.619> to<00:25:02.769> try<00:25:02.950> to<00:25:02.980> talk 00:25:03.690 --> 00:25:03.700 align:start position:0% to give users hope and to try to talk 00:25:03.700 --> 00:25:05.220 align:start position:0% to give users hope and to try to talk about<00:25:03.879> holding<00:25:04.419> ourselves<00:25:04.539> to<00:25:04.960> a<00:25:04.989> higher 00:25:05.220 --> 00:25:05.230 align:start position:0% about holding ourselves to a higher 00:25:05.230 --> 00:25:07.080 align:start position:0% about holding ourselves to a higher standard<00:25:05.259> that<00:25:05.950> we<00:25:06.220> can<00:25:06.549> solve<00:25:06.940> these 00:25:07.080 --> 00:25:07.090 align:start position:0% standard that we can solve these 00:25:07.090 --> 00:25:08.999 align:start position:0% standard that we can solve these problems<00:25:07.600> and<00:25:07.749> we<00:25:08.139> don't<00:25:08.259> have<00:25:08.649> to<00:25:08.799> just 00:25:08.999 --> 00:25:09.009 align:start position:0% problems and we don't have to just 00:25:09.009 --> 00:25:10.499 align:start position:0% problems and we don't have to just collect<00:25:09.309> everything<00:25:09.669> in<00:25:09.940> order<00:25:10.059> to<00:25:10.210> make<00:25:10.360> our 00:25:10.499 --> 00:25:10.509 align:start position:0% collect everything in order to make our 00:25:10.509 --> 00:25:16.680 align:start position:0% collect everything in order to make our businesses<00:25:10.899> governor<00:25:15.149> we're<00:25:16.149> not<00:25:16.299> talking 00:25:16.680 --> 00:25:16.690 align:start position:0% businesses governor we're not talking 00:25:16.690 --> 00:25:18.239 align:start position:0% businesses governor we're not talking about<00:25:16.869> do<00:25:16.960> you<00:25:17.049> trust<00:25:17.289> Google<00:25:17.799> with<00:25:17.950> your<00:25:17.980> data 00:25:18.239 --> 00:25:18.249 align:start position:0% about do you trust Google with your data 00:25:18.249 --> 00:25:19.769 align:start position:0% about do you trust Google with your data or<00:25:18.489> Facebook<00:25:18.970> with<00:25:19.119> your<00:25:19.239> data<00:25:19.419> but<00:25:19.659> it's 00:25:19.769 --> 00:25:19.779 align:start position:0% or Facebook with your data but it's 00:25:19.779 --> 00:25:21.989 align:start position:0% or Facebook with your data but it's actually<00:25:20.110> do<00:25:20.230> you<00:25:20.320> trust<00:25:20.610> some<00:25:21.610> part<00:25:21.789> of<00:25:21.879> your 00:25:21.989 --> 00:25:21.999 align:start position:0% actually do you trust some part of your 00:25:21.999 --> 00:25:24.450 align:start position:0% actually do you trust some part of your data<00:25:22.090> or<00:25:22.360> is<00:25:22.450> it<00:25:22.570> public<00:25:22.749> everybody<00:25:23.259> it's<00:25:24.220> not 00:25:24.450 --> 00:25:24.460 align:start position:0% data or is it public everybody it's not 00:25:24.460 --> 00:25:26.509 align:start position:0% data or is it public everybody it's not just<00:25:24.730> this<00:25:24.909> trade<00:25:25.239> off<00:25:25.269> maybe<00:25:25.749> give<00:25:26.080> us<00:25:26.109> some 00:25:26.509 --> 00:25:26.519 align:start position:0% just this trade off maybe give us some 00:25:26.519 --> 00:25:32.009 align:start position:0% just this trade off maybe give us some better<00:25:27.519> ability<00:25:30.330> you<00:25:31.330> can<00:25:31.419> at<00:25:31.570> least<00:25:31.600> -<00:25:31.840> thank 00:25:32.009 --> 00:25:32.019 align:start position:0% better ability you can at least - thank 00:25:32.019 --> 00:25:40.109 align:start position:0% better ability you can at least - thank you<00:25:32.139> only<00:25:32.289> trust<00:25:37.470> like<00:25:38.470> or<00:25:39.220> maybe<00:25:39.789> have<00:25:40.090> a 00:25:40.109 --> 00:25:40.119 align:start position:0% you only trust like or maybe have a 00:25:40.119 --> 00:25:41.759 align:start position:0% you only trust like or maybe have a follow-up<00:25:40.480> question<00:25:40.539> do<00:25:41.080> you<00:25:41.169> think<00:25:41.409> there's 00:25:41.759 --> 00:25:41.769 align:start position:0% follow-up question do you think there's 00:25:41.769 --> 00:25:44.009 align:start position:0% follow-up question do you think there's really<00:25:42.039> that<00:25:42.429> much<00:25:42.669> of<00:25:42.730> a<00:25:42.999> choice<00:25:43.330> you<00:25:43.629> haven't 00:25:44.009 --> 00:25:44.019 align:start position:0% really that much of a choice you haven't 00:25:44.019 --> 00:25:46.349 align:start position:0% really that much of a choice you haven't back<00:25:44.169> three<00:25:44.470> or<00:25:44.499> is<00:25:44.919> it<00:25:45.129> rather<00:25:45.369> there<00:25:46.059> is<00:25:46.090> an 00:25:46.349 --> 00:25:46.359 align:start position:0% back three or is it rather there is an 00:25:46.359 --> 00:25:47.999 align:start position:0% back three or is it rather there is an implementation<00:25:46.629> that<00:25:47.109> gives<00:25:47.470> you<00:25:47.590> privacy 00:25:47.999 --> 00:25:48.009 align:start position:0% implementation that gives you privacy 00:25:48.009 --> 00:25:50.039 align:start position:0% implementation that gives you privacy property<00:25:48.759> is<00:25:48.820> technically<00:25:49.330> where<00:25:49.720> you<00:25:49.869> have 00:25:50.039 --> 00:25:50.049 align:start position:0% property is technically where you have 00:25:50.049 --> 00:25:52.529 align:start position:0% property is technically where you have zero<00:25:50.409> for<00:25:51.039> me<00:25:51.159> it's<00:25:51.309> muscle<00:25:51.549> binary<00:25:52.119> in<00:25:52.330> that 00:25:52.529 --> 00:25:52.539 align:start position:0% zero for me it's muscle binary in that 00:25:52.539 --> 00:25:54.509 align:start position:0% zero for me it's muscle binary in that space<00:25:52.840> because<00:25:53.049> the<00:25:53.350> longer<00:25:53.559> company<00:25:54.129> that 00:25:54.509 --> 00:25:54.519 align:start position:0% space because the longer company that 00:25:54.519 --> 00:25:57.720 align:start position:0% space because the longer company that has<00:25:54.700> data<00:25:55.090> and<00:25:55.419> can<00:25:55.600> act<00:25:56.039> that's<00:25:57.039> just<00:25:57.220> me 00:25:57.720 --> 00:25:57.730 align:start position:0% has data and can act that's just me 00:25:57.730 --> 00:26:02.700 align:start position:0% has data and can act that's just me or<00:25:58.200> be<00:25:59.200> yeah<00:25:59.619> be<00:25:59.950> good<00:26:00.159> with<00:26:00.369> the<00:26:00.460> data<00:26:01.109> well<00:26:02.109> in 00:26:02.700 --> 00:26:02.710 align:start position:0% or be yeah be good with the data well in 00:26:02.710 --> 00:26:05.940 align:start position:0% or be yeah be good with the data well in the<00:26:02.859> in<00:26:03.129> the<00:26:03.309> legacy<00:26:03.639> tech<00:26:03.879> space<00:26:04.119> the<00:26:04.529> a<00:26:05.529> lot 00:26:05.940 --> 00:26:05.950 align:start position:0% the in the legacy tech space the a lot 00:26:05.950 --> 00:26:10.019 align:start position:0% the in the legacy tech space the a lot of<00:26:06.100> privacy<00:26:07.529> action<00:26:08.529> or<00:26:08.950> trouble<00:26:09.369> happens<00:26:09.820> at 00:26:10.019 --> 00:26:10.029 align:start position:0% of privacy action or trouble happens at 00:26:10.029 --> 00:26:13.519 align:start position:0% of privacy action or trouble happens at higher<00:26:10.269> levels<00:26:10.629> of<00:26:10.720> the<00:26:10.840> staff<00:26:11.639> right<00:26:12.639> so 00:26:13.519 --> 00:26:13.529 align:start position:0% higher levels of the staff right so 00:26:13.529 --> 00:26:16.320 align:start position:0% higher levels of the staff right so anything<00:26:14.529> that<00:26:14.559> is<00:26:15.039> a<00:26:15.460> real<00:26:15.609> risk<00:26:15.820> here<00:26:16.210> in 00:26:16.320 --> 00:26:16.330 align:start position:0% anything that is a real risk here in 00:26:16.330 --> 00:26:19.200 align:start position:0% anything that is a real risk here in this<00:26:16.419> space<00:26:16.690> as<00:26:16.869> well<00:26:17.460> that<00:26:18.460> at<00:26:18.730> higher<00:26:18.879> levels 00:26:19.200 --> 00:26:19.210 align:start position:0% this space as well that at higher levels 00:26:19.210 --> 00:26:20.519 align:start position:0% this space as well that at higher levels of<00:26:19.269> the<00:26:19.330> stack<00:26:19.570> you<00:26:19.869> might<00:26:20.019> see<00:26:20.169> more<00:26:20.320> data 00:26:20.519 --> 00:26:20.529 align:start position:0% of the stack you might see more data 00:26:20.529 --> 00:26:23.759 align:start position:0% of the stack you might see more data collection<00:26:21.119> you<00:26:22.119> know<00:26:22.230> from<00:26:23.230> a<00:26:23.320> fundamental 00:26:23.759 --> 00:26:23.769 align:start position:0% collection you know from a fundamental 00:26:23.769 --> 00:26:25.440 align:start position:0% collection you know from a fundamental technology<00:26:24.279> standpoint<00:26:24.549> you<00:26:24.940> an<00:26:25.090> answer<00:26:25.239> to 00:26:25.440 --> 00:26:25.450 align:start position:0% technology standpoint you an answer to 00:26:25.450 --> 00:26:28.029 align:start position:0% technology standpoint you an answer to your<00:26:25.570> question<00:26:25.989> I<00:26:26.109> think<00:26:26.139> there<00:26:26.529> are<00:26:26.649> pros<00:26:26.889> and 00:26:28.029 --> 00:26:28.039 align:start position:0% your question I think there are pros and 00:26:28.039 --> 00:26:31.399 align:start position:0% your question I think there are pros and compared<00:26:29.039> to<00:26:29.100> what<00:26:29.730> came<00:26:29.909> before<00:26:30.289> also<00:26:31.289> this 00:26:31.399 --> 00:26:31.409 align:start position:0% compared to what came before also this 00:26:31.409 --> 00:26:33.259 align:start position:0% compared to what came before also this is<00:26:31.590> a<00:26:31.619> do-over<00:26:31.919> on<00:26:32.340> some<00:26:32.669> of<00:26:32.789> the<00:26:32.879> structures 00:26:33.259 --> 00:26:33.269 align:start position:0% is a do-over on some of the structures 00:26:33.269 --> 00:26:35.779 align:start position:0% is a do-over on some of the structures and<00:26:33.480> approaches<00:26:33.899> that<00:26:33.929> happened<00:26:34.710> before<00:26:35.129> and 00:26:35.779 --> 00:26:35.789 align:start position:0% and approaches that happened before and 00:26:35.789 --> 00:26:37.399 align:start position:0% and approaches that happened before and maybe<00:26:36.059> we're<00:26:36.269> a<00:26:36.299> little<00:26:36.450> bit<00:26:36.659> wiser<00:26:36.869> about<00:26:37.259> how 00:26:37.399 --> 00:26:37.409 align:start position:0% maybe we're a little bit wiser about how 00:26:37.409 --> 00:26:38.409 align:start position:0% maybe we're a little bit wiser about how to<00:26:37.470> do<00:26:37.649> it 00:26:38.409 --> 00:26:38.419 align:start position:0% to do it 00:26:38.419 --> 00:26:40.759 align:start position:0% to do it so<00:26:39.419> speaking<00:26:39.659> of<00:26:39.840> being<00:26:39.989> Liza<00:26:40.259> that's<00:26:40.619> a 00:26:40.759 --> 00:26:40.769 align:start position:0% so speaking of being Liza that's a 00:26:40.769 --> 00:26:42.499 align:start position:0% so speaking of being Liza that's a little<00:26:41.070> bit<00:26:41.220> about<00:26:41.399> the<00:26:41.580> technology<00:26:42.360> and 00:26:42.499 --> 00:26:42.509 align:start position:0% little bit about the technology and 00:26:42.509 --> 00:26:44.450 align:start position:0% little bit about the technology and people<00:26:42.690> actually<00:26:43.139> speaking<00:26:43.649> of<00:26:43.739> them<00:26:43.919> let's 00:26:44.450 --> 00:26:44.460 align:start position:0% people actually speaking of them let's 00:26:44.460 --> 00:26:46.340 align:start position:0% people actually speaking of them let's talk<00:26:44.610> a<00:26:44.639> little<00:26:44.730> bit<00:26:44.970> more<00:26:45.749> about<00:26:46.019> the 00:26:46.340 --> 00:26:46.350 align:start position:0% talk a little bit more about the 00:26:46.350 --> 00:26:49.239 align:start position:0% talk a little bit more about the technology<00:26:46.769> and<00:26:47.399> incentives<00:26:48.179> that<00:26:48.749> can<00:26:48.960> be 00:26:49.239 --> 00:26:49.249 align:start position:0% technology and incentives that can be 00:26:49.249 --> 00:26:51.499 align:start position:0% technology and incentives that can be combined<00:26:50.249> perhaps<00:26:50.820> like<00:26:51.119> we<00:26:51.239> were<00:26:51.360> talking 00:26:51.499 --> 00:26:51.509 align:start position:0% combined perhaps like we were talking 00:26:51.509 --> 00:26:53.659 align:start position:0% combined perhaps like we were talking earlier<00:26:51.690> about<00:26:52.049> scalability<00:26:52.619> and<00:26:53.190> privacy 00:26:53.659 --> 00:26:53.669 align:start position:0% earlier about scalability and privacy 00:26:53.669 --> 00:26:56.090 align:start position:0% earlier about scalability and privacy can<00:26:54.059> be<00:26:54.119> done<00:26:54.450> at<00:26:54.869> the<00:26:54.960> same<00:26:55.169> time<00:26:55.409> with 00:26:56.090 --> 00:26:56.100 align:start position:0% can be done at the same time with 00:26:56.100 --> 00:26:58.820 align:start position:0% can be done at the same time with technology<00:26:56.460> I<00:26:57.210> think<00:26:57.269> it's<00:26:57.539> good<00:26:57.720> to<00:26:57.830> explore 00:26:58.820 --> 00:26:58.830 align:start position:0% technology I think it's good to explore 00:26:58.830 --> 00:27:01.220 align:start position:0% technology I think it's good to explore that<00:26:59.159> kind<00:26:59.369> of<00:26:59.489> thing<00:26:59.669> too<00:26:59.909> it's<00:27:00.090> an<00:27:00.840> extra 00:27:01.220 --> 00:27:01.230 align:start position:0% that kind of thing too it's an extra 00:27:01.230 --> 00:27:03.950 align:start position:0% that kind of thing too it's an extra opportunity<00:27:02.039> for<00:27:02.489> incentive<00:27:03.029> that<00:27:03.659> perhaps 00:27:03.950 --> 00:27:03.960 align:start position:0% opportunity for incentive that perhaps 00:27:03.960 --> 00:27:06.830 align:start position:0% opportunity for incentive that perhaps is<00:27:04.320> not<00:27:04.350> better<00:27:04.739> and<00:27:05.070> what<00:27:05.669> beautiful<00:27:05.909> and 00:27:06.830 --> 00:27:06.840 align:start position:0% is not better and what beautiful and 00:27:06.840 --> 00:27:10.009 align:start position:0% is not better and what beautiful and stuff<00:27:07.249> so<00:27:08.249> yeah<00:27:08.609> do<00:27:09.210> you<00:27:09.509> want<00:27:09.659> to<00:27:09.690> talk<00:27:09.869> about 00:27:10.009 --> 00:27:10.019 align:start position:0% stuff so yeah do you want to talk about 00:27:10.019 --> 00:27:12.950 align:start position:0% stuff so yeah do you want to talk about some<00:27:10.409> of<00:27:10.440> the<00:27:11.359> abilities<00:27:12.359> that<00:27:12.389> we<00:27:12.659> can<00:27:12.809> do 00:27:12.950 --> 00:27:12.960 align:start position:0% some of the abilities that we can do 00:27:12.960 --> 00:27:15.409 align:start position:0% some of the abilities that we can do with<00:27:13.230> the<00:27:14.159> things<00:27:14.369> that<00:27:14.519> we<00:27:14.609> can<00:27:14.789> capability 00:27:15.409 --> 00:27:15.419 align:start position:0% with the things that we can capability 00:27:15.419 --> 00:27:17.299 align:start position:0% with the things that we can capability that<00:27:15.480> we<00:27:15.600> have<00:27:15.809> when<00:27:16.169> were<00:27:16.350> doing<00:27:17.129> an 00:27:17.299 --> 00:27:17.309 align:start position:0% that we have when were doing an 00:27:17.309 --> 00:27:21.080 align:start position:0% that we have when were doing an assessment<00:27:17.789> not<00:27:18.299> so<00:27:18.869> my<00:27:19.619> usual<00:27:20.519> thing<00:27:20.879> at<00:27:20.970> work 00:27:21.080 --> 00:27:21.090 align:start position:0% assessment not so my usual thing at work 00:27:21.090 --> 00:27:22.549 align:start position:0% assessment not so my usual thing at work with<00:27:21.299> this<00:27:21.359> newer<00:27:21.600> knowledge<00:27:21.929> of<00:27:22.019> proofs<00:27:22.230> and 00:27:22.549 --> 00:27:22.559 align:start position:0% with this newer knowledge of proofs and 00:27:22.559 --> 00:27:24.289 align:start position:0% with this newer knowledge of proofs and we've<00:27:22.679> seen<00:27:22.889> a<00:27:22.919> massive<00:27:23.489> amount<00:27:23.909> of<00:27:24.090> new 00:27:24.289 --> 00:27:24.299 align:start position:0% we've seen a massive amount of new 00:27:24.299 --> 00:27:27.379 align:start position:0% we've seen a massive amount of new excitement<00:27:24.749> of<00:27:25.379> what<00:27:25.590> we<00:27:25.739> can<00:27:25.859> do<00:27:26.129> and<00:27:26.639> it's 00:27:27.379 --> 00:27:27.389 align:start position:0% excitement of what we can do and it's 00:27:27.389 --> 00:27:28.970 align:start position:0% excitement of what we can do and it's quite<00:27:27.749> interesting<00:27:28.320> but<00:27:28.409> I<00:27:28.499> think<00:27:28.529> we're<00:27:28.830> sort 00:27:28.970 --> 00:27:28.980 align:start position:0% quite interesting but I think we're sort 00:27:28.980 --> 00:27:32.029 align:start position:0% quite interesting but I think we're sort of<00:27:29.869> people<00:27:30.869> getting<00:27:31.169> distracted<00:27:31.619> by<00:27:31.889> they'll 00:27:32.029 --> 00:27:32.039 align:start position:0% of people getting distracted by they'll 00:27:32.039 --> 00:27:34.190 align:start position:0% of people getting distracted by they'll get<00:27:32.220> just<00:27:32.489> the<00:27:32.850> new<00:27:33.269> exciting<00:27:33.659> little<00:27:34.019> pieces 00:27:34.190 --> 00:27:34.200 align:start position:0% get just the new exciting little pieces 00:27:34.200 --> 00:27:36.320 align:start position:0% get just the new exciting little pieces of<00:27:34.379> it<00:27:34.529> or<00:27:34.619> not<00:27:34.769> the<00:27:35.070> like<00:27:35.279> general<00:27:35.730> pattern<00:27:36.179> of 00:27:36.320 --> 00:27:36.330 align:start position:0% of it or not the like general pattern of 00:27:36.330 --> 00:27:38.899 align:start position:0% of it or not the like general pattern of use<00:27:37.169> the<00:27:37.350> tools<00:27:37.619> here's<00:27:37.980> the<00:27:38.100> techniques<00:27:38.489> so<00:27:38.879> a 00:27:38.899 --> 00:27:38.909 align:start position:0% use the tools here's the techniques so a 00:27:38.909 --> 00:27:40.759 align:start position:0% use the tools here's the techniques so a common<00:27:39.299> thing<00:27:39.389> people<00:27:39.450> think<00:27:39.690> of<00:27:39.929> is<00:27:39.989> without 00:27:40.759 --> 00:27:40.769 align:start position:0% common thing people think of is without 00:27:40.769 --> 00:27:42.289 align:start position:0% common thing people think of is without new<00:27:41.070> piece<00:27:41.220> of<00:27:41.369> photography<00:27:41.489> to<00:27:41.940> get<00:27:42.119> there 00:27:42.289 --> 00:27:42.299 align:start position:0% new piece of photography to get there 00:27:42.299 --> 00:27:43.820 align:start position:0% new piece of photography to get there then<00:27:42.509> a<00:27:42.539> bunch<00:27:42.779> of<00:27:42.929> these<00:27:43.080> things<00:27:43.350> to<00:27:43.529> do<00:27:43.649> this 00:27:43.820 --> 00:27:43.830 align:start position:0% then a bunch of these things to do this 00:27:43.830 --> 00:27:46.249 align:start position:0% then a bunch of these things to do this this<00:27:44.549> is<00:27:44.609> the<00:27:45.029> existing<00:27:45.749> techniques<00:27:46.109> for 00:27:46.249 --> 00:27:46.259 align:start position:0% this is the existing techniques for 00:27:46.259 --> 00:27:48.080 align:start position:0% this is the existing techniques for doing<00:27:46.379> like<00:27:46.649> it<00:27:46.980> helps<00:27:47.190> me<00:27:47.279> catch<00:27:47.460> some<00:27:47.970> air 00:27:48.080 --> 00:27:48.090 align:start position:0% doing like it helps me catch some air 00:27:48.090 --> 00:27:51.049 align:start position:0% doing like it helps me catch some air pollution<00:27:48.809> well<00:27:48.989> or<00:27:49.529> as<00:27:49.619> well<00:27:49.859> and<00:27:50.220> then<00:27:50.789> also 00:27:51.049 --> 00:27:51.059 align:start position:0% pollution well or as well and then also 00:27:51.059 --> 00:27:54.409 align:start position:0% pollution well or as well and then also that<00:27:51.690> like<00:27:52.220> people<00:27:53.220> miss<00:27:53.789> I<00:27:53.909> need<00:27:54.059> to<00:27:54.149> get<00:27:54.239> hung 00:27:54.409 --> 00:27:54.419 align:start position:0% that like people miss I need to get hung 00:27:54.419 --> 00:27:55.729 align:start position:0% that like people miss I need to get hung up<00:27:54.539> I'm<00:27:54.720> like<00:27:54.840> oh<00:27:54.960> we're<00:27:55.230> in<00:27:55.259> the<00:27:55.409> account 00:27:55.729 --> 00:27:55.739 align:start position:0% up I'm like oh we're in the account 00:27:55.739 --> 00:27:57.649 align:start position:0% up I'm like oh we're in the account about<00:27:55.889> bitcoins<00:27:56.580> at<00:27:56.730> UT<00:27:56.999> Excel<00:27:57.330> bottom 00:27:57.649 --> 00:27:57.659 align:start position:0% about bitcoins at UT Excel bottom 00:27:57.659 --> 00:27:59.720 align:start position:0% about bitcoins at UT Excel bottom different<00:27:58.049> none<00:27:58.230> of<00:27:58.379> the<00:27:58.529> techniques<00:27:58.889> over 00:27:59.720 --> 00:27:59.730 align:start position:0% different none of the techniques over 00:27:59.730 --> 00:28:01.489 align:start position:0% different none of the techniques over there<00:27:59.940> or<00:28:00.929> over<00:28:00.960> here 00:28:01.489 --> 00:28:01.499 align:start position:0% there or over here 00:28:01.499 --> 00:28:03.229 align:start position:0% there or over here right<00:28:02.220> and<00:28:02.460> it's<00:28:02.609> actually<00:28:02.730> these<00:28:03.029> are<00:28:03.179> all 00:28:03.229 --> 00:28:03.239 align:start position:0% right and it's actually these are all 00:28:03.239 --> 00:28:04.160 align:start position:0% right and it's actually these are all pretty 00:28:04.160 --> 00:28:04.170 align:start position:0% pretty 00:28:04.170 --> 00:28:05.810 align:start position:0% pretty you<00:28:04.440> use<00:28:04.620> most<00:28:04.950> of<00:28:05.070> these<00:28:05.190> developments<00:28:05.730> on 00:28:05.810 --> 00:28:05.820 align:start position:0% you use most of these developments on 00:28:05.820 --> 00:28:08.210 align:start position:0% you use most of these developments on anything<00:28:06.180> so<00:28:06.870> it<00:28:06.990> seems<00:28:07.200> that<00:28:07.350> in<00:28:07.500> fact<00:28:07.710> the 00:28:08.210 --> 00:28:08.220 align:start position:0% anything so it seems that in fact the 00:28:08.220 --> 00:28:09.770 align:start position:0% anything so it seems that in fact the incentives<00:28:08.700> of<00:28:08.850> these<00:28:08.970> face<00:28:09.330> right<00:28:09.510> now<00:28:09.660> I'm 00:28:09.770 --> 00:28:09.780 align:start position:0% incentives of these face right now I'm 00:28:09.780 --> 00:28:12.410 align:start position:0% incentives of these face right now I'm getting<00:28:09.990> very<00:28:10.140> excited<00:28:10.740> about<00:28:11.240> what's<00:28:12.240> my 00:28:12.410 --> 00:28:12.420 align:start position:0% getting very excited about what's my 00:28:12.420 --> 00:28:13.850 align:start position:0% getting very excited about what's my priority<00:28:12.630> subscribe<00:28:13.200> there<00:28:13.350> were<00:28:13.440> actually 00:28:13.850 --> 00:28:13.860 align:start position:0% priority subscribe there were actually 00:28:13.860 --> 00:28:16.100 align:start position:0% priority subscribe there were actually many<00:28:14.460> shows<00:28:14.850> like<00:28:15.030> what<00:28:15.210> health<00:28:15.420> inside<00:28:15.960> your 00:28:16.100 --> 00:28:16.110 align:start position:0% many shows like what health inside your 00:28:16.110 --> 00:28:21.080 align:start position:0% many shows like what health inside your car<00:28:16.320> it's<00:28:16.650> the<00:28:17.510> biggest<00:28:18.510> thing<00:28:19.880> there<00:28:20.880> are 00:28:21.080 --> 00:28:21.090 align:start position:0% car it's the biggest thing there are 00:28:21.090 --> 00:28:23.480 align:start position:0% car it's the biggest thing there are also<00:28:21.360> things<00:28:21.930> that<00:28:22.080> you<00:28:22.290> can<00:28:22.710> do<00:28:22.860> in<00:28:23.070> terms<00:28:23.250> of 00:28:23.480 --> 00:28:23.490 align:start position:0% also things that you can do in terms of 00:28:23.490 --> 00:28:28.100 align:start position:0% also things that you can do in terms of design<00:28:23.880> that<00:28:24.450> don't<00:28:25.140> rely<00:28:25.530> on<00:28:25.830> the<00:28:27.110> absolutely 00:28:28.100 --> 00:28:28.110 align:start position:0% design that don't rely on the absolutely 00:28:28.110 --> 00:28:29.830 align:start position:0% design that don't rely on the absolutely newest<00:28:28.590> Chinese<00:28:29.070> most<00:28:29.370> complicated 00:28:29.830 --> 00:28:29.840 align:start position:0% newest Chinese most complicated 00:28:29.840 --> 00:28:33.200 align:start position:0% newest Chinese most complicated cryptography<00:28:31.070> so<00:28:32.070> you<00:28:32.460> know<00:28:32.550> looking<00:28:32.790> at<00:28:33.000> what 00:28:33.200 --> 00:28:33.210 align:start position:0% cryptography so you know looking at what 00:28:33.210 --> 00:28:36.020 align:start position:0% cryptography so you know looking at what we're<00:28:33.390> doing<00:28:33.630> at<00:28:34.020> opportune<00:28:34.350> laughs<00:28:35.030> we've 00:28:36.020 --> 00:28:36.030 align:start position:0% we're doing at opportune laughs we've 00:28:36.030 --> 00:28:38.570 align:start position:0% we're doing at opportune laughs we've done<00:28:36.180> a<00:28:36.210> lot<00:28:36.420> of<00:28:36.450> work<00:28:36.690> to<00:28:36.840> try<00:28:36.870> to<00:28:37.110> move<00:28:37.580> state 00:28:38.570 --> 00:28:38.580 align:start position:0% done a lot of work to try to move state 00:28:38.580 --> 00:28:40.730 align:start position:0% done a lot of work to try to move state of<00:28:38.700> states<00:28:39.030> and<00:28:39.180> contracts<00:28:39.660> off<00:28:40.020> chain<00:28:40.350> we<00:28:40.560> did 00:28:40.730 --> 00:28:40.740 align:start position:0% of states and contracts off chain we did 00:28:40.740 --> 00:28:42.560 align:start position:0% of states and contracts off chain we did that<00:28:40.940> originally<00:28:41.940> way<00:28:42.090> back<00:28:42.300> in<00:28:42.450> the 00:28:42.560 --> 00:28:42.570 align:start position:0% that originally way back in the 00:28:42.570 --> 00:28:44.840 align:start position:0% that originally way back in the beginning<00:28:42.900> motivated<00:28:43.530> by<00:28:43.650> scalability<00:28:44.340> but 00:28:44.840 --> 00:28:44.850 align:start position:0% beginning motivated by scalability but 00:28:44.850 --> 00:28:47.780 align:start position:0% beginning motivated by scalability but when<00:28:45.090> you<00:28:45.270> move<00:28:45.510> stuff<00:28:45.810> off<00:28:46.080> chain<00:28:46.410> you<00:28:47.040> when 00:28:47.780 --> 00:28:47.790 align:start position:0% when you move stuff off chain you when 00:28:47.790 --> 00:28:49.580 align:start position:0% when you move stuff off chain you when you<00:28:47.940> reduce<00:28:48.270> the<00:28:48.480> footprint<00:28:48.840> on<00:28:49.050> chain<00:28:49.320> you 00:28:49.580 --> 00:28:49.590 align:start position:0% you reduce the footprint on chain you 00:28:49.590 --> 00:28:52.550 align:start position:0% you reduce the footprint on chain you also<00:28:49.800> have<00:28:50.310> a<00:28:50.340> significant<00:28:51.240> privacy<00:28:51.560> benefits 00:28:52.550 --> 00:28:52.560 align:start position:0% also have a significant privacy benefits 00:28:52.560 --> 00:28:55.370 align:start position:0% also have a significant privacy benefits so<00:28:53.520> you<00:28:53.580> don't<00:28:53.820> need<00:28:54.000> to<00:28:54.240> use<00:28:54.510> the<00:28:55.110> highest 00:28:55.370 --> 00:28:55.380 align:start position:0% so you don't need to use the highest 00:28:55.380 --> 00:28:57.710 align:start position:0% so you don't need to use the highest tech<00:28:55.830> stuff<00:28:56.190> there<00:28:56.910> stuff<00:28:57.180> you<00:28:57.330> can<00:28:57.540> do<00:28:57.690> with 00:28:57.710 --> 00:28:57.720 align:start position:0% tech stuff there stuff you can do with 00:28:57.720 --> 00:28:59.240 align:start position:0% tech stuff there stuff you can do with in<00:28:58.080> this<00:28:58.260> sort<00:28:58.470> of<00:28:58.530> traditional<00:28:59.070> engineering 00:28:59.240 --> 00:28:59.250 align:start position:0% in this sort of traditional engineering 00:28:59.250 --> 00:29:01.280 align:start position:0% in this sort of traditional engineering frameworks<00:29:00.120> and<00:29:00.420> there<00:29:00.780> is<00:29:00.900> a<00:29:00.930> synergy 00:29:01.280 --> 00:29:01.290 align:start position:0% frameworks and there is a synergy 00:29:01.290 --> 00:29:03.770 align:start position:0% frameworks and there is a synergy between<00:29:01.560> efficiency<00:29:02.370> and<00:29:02.550> privacy<00:29:03.180> in<00:29:03.630> a 00:29:03.770 --> 00:29:03.780 align:start position:0% between efficiency and privacy in a 00:29:03.780 --> 00:29:07.820 align:start position:0% between efficiency and privacy in a space<00:29:04.080> where<00:29:04.490> the<00:29:05.780> public<00:29:06.780> more<00:29:07.110> public<00:29:07.650> on 00:29:07.820 --> 00:29:07.830 align:start position:0% space where the public more public on 00:29:07.830 --> 00:29:10.700 align:start position:0% space where the public more public on chain<00:29:08.280> say<00:29:08.610> is<00:29:09.030> more<00:29:09.450> expensive<00:29:10.110> than<00:29:10.560> what 00:29:10.700 --> 00:29:10.710 align:start position:0% chain say is more expensive than what 00:29:10.710 --> 00:29:12.920 align:start position:0% chain say is more expensive than what you<00:29:10.830> can<00:29:10.980> do<00:29:11.130> privately<00:29:11.550> that's<00:29:12.420> not<00:29:12.570> to<00:29:12.690> say 00:29:12.920 --> 00:29:12.930 align:start position:0% you can do privately that's not to say 00:29:12.930 --> 00:29:16.790 align:start position:0% you can do privately that's not to say that<00:29:12.960> you<00:29:13.830> should<00:29:14.040> never<00:29:14.280> use<00:29:14.430> the<00:29:15.650> the<00:29:16.650> high 00:29:16.790 --> 00:29:16.800 align:start position:0% that you should never use the the high 00:29:16.800 --> 00:29:18.410 align:start position:0% that you should never use the the high tech<00:29:17.040> stuff<00:29:17.160> or<00:29:17.490> that<00:29:17.550> we<00:29:17.700> would<00:29:17.850> never<00:29:17.970> use<00:29:18.240> it 00:29:18.410 --> 00:29:18.420 align:start position:0% tech stuff or that we would never use it 00:29:18.420 --> 00:29:21.080 align:start position:0% tech stuff or that we would never use it but<00:29:18.770> but<00:29:19.770> you<00:29:19.920> can<00:29:20.070> get<00:29:20.250> a<00:29:20.280> lot<00:29:20.490> without 00:29:21.080 --> 00:29:21.090 align:start position:0% but but you can get a lot without 00:29:21.090 --> 00:29:23.890 align:start position:0% but but you can get a lot without needing<00:29:21.690> to<00:29:21.720> you<00:29:22.500> didn't<00:29:22.740> use<00:29:22.890> that<00:29:23.100> stuff<00:29:23.370> I 00:29:23.890 --> 00:29:23.900 align:start position:0% needing to you didn't use that stuff I 00:29:23.900 --> 00:29:25.970 align:start position:0% needing to you didn't use that stuff I was<00:29:24.900> only<00:29:25.050> in<00:29:25.170> three<00:29:25.380> and<00:29:25.560> I<00:29:25.590> would<00:29:25.710> like<00:29:25.860> to 00:29:25.970 --> 00:29:25.980 align:start position:0% was only in three and I would like to 00:29:25.980 --> 00:29:28.190 align:start position:0% was only in three and I would like to ask<00:29:26.100> a<00:29:26.400> question<00:29:27.060> to<00:29:27.240> the<00:29:27.270> other<00:29:27.510> panelists 00:29:28.190 --> 00:29:28.200 align:start position:0% ask a question to the other panelists 00:29:28.200 --> 00:29:31.490 align:start position:0% ask a question to the other panelists because<00:29:28.950> it<00:29:29.310> was<00:29:30.030> my<00:29:30.330> initial<00:29:30.780> question<00:29:30.960> was 00:29:31.490 --> 00:29:31.500 align:start position:0% because it was my initial question was 00:29:31.500 --> 00:29:34.630 align:start position:0% because it was my initial question was like<00:29:31.650> where<00:29:31.830> unit<00:29:32.100> is<00:29:32.580> like<00:29:33.330> how<00:29:33.810> do<00:29:33.870> we<00:29:34.140> have 00:29:34.630 --> 00:29:34.640 align:start position:0% like where unit is like how do we have 00:29:34.640 --> 00:29:38.410 align:start position:0% like where unit is like how do we have privacy<00:29:35.640> while<00:29:36.390> you're<00:29:36.720> scaling<00:29:37.070> for<00:29:38.070> me 00:29:38.410 --> 00:29:38.420 align:start position:0% privacy while you're scaling for me 00:29:38.420 --> 00:29:40.850 align:start position:0% privacy while you're scaling for me oftentimes<00:29:39.420> the<00:29:39.660> answer<00:29:40.050> to<00:29:40.320> privacy<00:29:40.740> and 00:29:40.850 --> 00:29:40.860 align:start position:0% oftentimes the answer to privacy and 00:29:40.860 --> 00:29:43.580 align:start position:0% oftentimes the answer to privacy and scaling<00:29:41.460> poisons<00:29:42.420> the<00:29:42.510> same<00:29:42.720> direction<00:29:43.230> as 00:29:43.580 --> 00:29:43.590 align:start position:0% scaling poisons the same direction as 00:29:43.590 --> 00:29:45.920 align:start position:0% scaling poisons the same direction as least<00:29:43.860> because<00:29:44.220> it's<00:29:44.610> like<00:29:44.850> reducing<00:29:45.630> block 00:29:45.920 --> 00:29:45.930 align:start position:0% least because it's like reducing block 00:29:45.930 --> 00:29:47.480 align:start position:0% least because it's like reducing block chains<00:29:46.230> to<00:29:46.470> what<00:29:46.650> they're<00:29:46.800> actually 00:29:47.480 --> 00:29:47.490 align:start position:0% chains to what they're actually 00:29:47.490 --> 00:29:50.330 align:start position:0% chains to what they're actually that<00:29:47.789> and<00:29:48.029> not<00:29:48.870> doing<00:29:49.200> as<00:29:49.649> much<00:29:49.679> as<00:29:49.919> possible 00:29:50.330 --> 00:29:50.340 align:start position:0% that and not doing as much as possible 00:29:50.340 --> 00:29:52.750 align:start position:0% that and not doing as much as possible on<00:29:50.760> the<00:29:50.909> blockchain<00:29:51.179> and<00:29:51.600> if<00:29:51.690> you<00:29:51.840> remove 00:29:52.750 --> 00:29:52.760 align:start position:0% on the blockchain and if you remove 00:29:52.760 --> 00:29:56.360 align:start position:0% on the blockchain and if you remove computation<00:29:53.760> steps<00:29:54.090> and<00:29:54.390> then<00:29:54.659> like<00:29:55.200> to<00:29:55.710> to 00:29:56.360 --> 00:29:56.370 align:start position:0% computation steps and then like to to 00:29:56.370 --> 00:29:58.460 align:start position:0% computation steps and then like to to verify<00:29:56.940> the<00:29:57.000> montane<00:29:57.480> you<00:29:57.659> can<00:29:57.840> use<00:29:58.080> different 00:29:58.460 --> 00:29:58.470 align:start position:0% verify the montane you can use different 00:29:58.470 --> 00:30:00.649 align:start position:0% verify the montane you can use different techniques<00:29:58.950> that<00:29:59.190> can<00:29:59.460> be<00:29:59.520> simple<00:30:00.059> integrity 00:30:00.649 --> 00:30:00.659 align:start position:0% techniques that can be simple integrity 00:30:00.659 --> 00:30:03.440 align:start position:0% techniques that can be simple integrity checks<00:30:00.960> with<00:30:01.200> hashes<00:30:01.710> it<00:30:02.010> can<00:30:02.220> be<00:30:02.450> complex 00:30:03.440 --> 00:30:03.450 align:start position:0% checks with hashes it can be complex 00:30:03.450 --> 00:30:05.720 align:start position:0% checks with hashes it can be complex mechanisms<00:30:04.230> like<00:30:04.440> stock<00:30:04.740> starts<00:30:05.250> whatsoever 00:30:05.720 --> 00:30:05.730 align:start position:0% mechanisms like stock starts whatsoever 00:30:05.730 --> 00:30:07.580 align:start position:0% mechanisms like stock starts whatsoever it<00:30:05.909> doesn't<00:30:06.210> matter<00:30:06.360> but<00:30:06.750> the<00:30:06.899> key<00:30:07.049> aspect<00:30:07.470> is 00:30:07.580 --> 00:30:07.590 align:start position:0% it doesn't matter but the key aspect is 00:30:07.590 --> 00:30:09.740 align:start position:0% it doesn't matter but the key aspect is we<00:30:07.890> move<00:30:08.100> stuff<00:30:08.429> away<00:30:08.669> from<00:30:08.880> the<00:30:09.179> clock<00:30:09.480> chain 00:30:09.740 --> 00:30:09.750 align:start position:0% we move stuff away from the clock chain 00:30:09.750 --> 00:30:12.019 align:start position:0% we move stuff away from the clock chain keep<00:30:10.230> as<00:30:10.409> much<00:30:10.559> of<00:30:10.620> the<00:30:10.950> information<00:30:11.190> off<00:30:11.970> that 00:30:12.019 --> 00:30:12.029 align:start position:0% keep as much of the information off that 00:30:12.029 --> 00:30:14.360 align:start position:0% keep as much of the information off that public<00:30:12.809> lecture<00:30:13.260> in<00:30:13.620> the<00:30:13.710> first<00:30:13.919> place<00:30:14.130> and 00:30:14.360 --> 00:30:14.370 align:start position:0% public lecture in the first place and 00:30:14.370 --> 00:30:16.610 align:start position:0% public lecture in the first place and then<00:30:14.970> there's<00:30:15.330> much<00:30:15.600> less<00:30:15.899> we<00:30:16.140> need<00:30:16.289> to<00:30:16.409> bother 00:30:16.610 --> 00:30:16.620 align:start position:0% then there's much less we need to bother 00:30:16.620 --> 00:30:19.430 align:start position:0% then there's much less we need to bother about<00:30:16.740> and<00:30:17.159> at<00:30:17.250> the<00:30:17.399> same<00:30:17.580> time<00:30:17.880> we<00:30:18.179> push<00:30:18.510> this 00:30:19.430 --> 00:30:19.440 align:start position:0% about and at the same time we push this 00:30:19.440 --> 00:30:21.710 align:start position:0% about and at the same time we push this loan<00:30:20.070> on<00:30:20.429> the<00:30:20.549> blockchain<00:30:20.760> so<00:30:21.090> it's<00:30:21.240> naturally 00:30:21.710 --> 00:30:21.720 align:start position:0% loan on the blockchain so it's naturally 00:30:21.720 --> 00:30:24.350 align:start position:0% loan on the blockchain so it's naturally gonna<00:30:21.960> not<00:30:22.679> scared<00:30:23.039> better<00:30:23.250> but<00:30:23.789> for<00:30:23.820> the<00:30:24.120> same 00:30:24.350 --> 00:30:24.360 align:start position:0% gonna not scared better but for the same 00:30:24.360 --> 00:30:28.840 align:start position:0% gonna not scared better but for the same amount<00:30:24.750> of<00:30:25.110> utility<00:30:27.140> require<00:30:28.140> less 00:30:28.840 --> 00:30:28.850 align:start position:0% amount of utility require less 00:30:28.850 --> 00:30:31.010 align:start position:0% amount of utility require less computation<00:30:29.850> to<00:30:30.059> be<00:30:30.210> done<00:30:30.360> mantra<00:30:30.750> in<00:30:30.960> the 00:30:31.010 --> 00:30:31.020 align:start position:0% computation to be done mantra in the 00:30:31.020 --> 00:30:34.340 align:start position:0% computation to be done mantra in the first<00:30:31.230> place<00:30:31.409> so<00:30:32.120> do<00:30:33.120> you<00:30:33.210> think<00:30:33.240> there<00:30:34.140> is<00:30:34.320> a 00:30:34.340 --> 00:30:34.350 align:start position:0% first place so do you think there is a 00:30:34.350 --> 00:30:37.940 align:start position:0% first place so do you think there is a synergy<00:30:35.070> between<00:30:35.779> privacy<00:30:36.779> and<00:30:36.960> scalability 00:30:37.940 --> 00:30:37.950 align:start position:0% synergy between privacy and scalability 00:30:37.950 --> 00:30:44.600 align:start position:0% synergy between privacy and scalability or<00:30:37.980> a<00:30:38.220> trade-off<00:30:42.380> so<00:30:43.380> I<00:30:43.409> I<00:30:43.649> think<00:30:43.919> I'm<00:30:44.220> the<00:30:44.340> lone 00:30:44.600 --> 00:30:44.610 align:start position:0% or a trade-off so I I think I'm the lone 00:30:44.610 --> 00:30:46.580 align:start position:0% or a trade-off so I I think I'm the lone panelist<00:30:45.090> who<00:30:45.299> who<00:30:45.779> said<00:30:46.049> that<00:30:46.169> there<00:30:46.409> was<00:30:46.559> a 00:30:46.580 --> 00:30:46.590 align:start position:0% panelist who who said that there was a 00:30:46.590 --> 00:30:49.789 align:start position:0% panelist who who said that there was a trade-off<00:30:47.779> and<00:30:48.779> I<00:30:48.840> was<00:30:48.960> at<00:30:49.110> least<00:30:49.289> technical 00:30:49.789 --> 00:30:49.799 align:start position:0% trade-off and I was at least technical 00:30:49.799 --> 00:30:53.570 align:start position:0% trade-off and I was at least technical in<00:30:49.950> years<00:30:50.190> maybe<00:30:50.580> I<00:30:50.700> wrong<00:30:50.960> but<00:30:51.960> I<00:30:52.580> actually 00:30:53.570 --> 00:30:53.580 align:start position:0% in years maybe I wrong but I actually 00:30:53.580 --> 00:30:55.549 align:start position:0% in years maybe I wrong but I actually like<00:30:53.940> I<00:30:54.299> think<00:30:54.809> there<00:30:55.049> is<00:30:55.080> a<00:30:55.200> trade-off 00:30:55.549 --> 00:30:55.559 align:start position:0% like I think there is a trade-off 00:30:55.559 --> 00:30:58.310 align:start position:0% like I think there is a trade-off present<00:30:56.190> that<00:30:56.309> because<00:30:56.580> it<00:30:56.730> creates<00:30:57.320> it 00:30:58.310 --> 00:30:58.320 align:start position:0% present that because it creates it 00:30:58.320 --> 00:31:01.190 align:start position:0% present that because it creates it creates<00:30:58.380> a<00:30:58.679> degree<00:30:58.980> of<00:30:59.010> user<00:30:59.370> complexity<00:31:00.210> for 00:31:01.190 --> 00:31:01.200 align:start position:0% creates a degree of user complexity for 00:31:01.200 --> 00:31:02.750 align:start position:0% creates a degree of user complexity for one<00:31:01.320> thing<00:31:01.620> when<00:31:01.950> you<00:31:02.039> start<00:31:02.100> offloading 00:31:02.750 --> 00:31:02.760 align:start position:0% one thing when you start offloading 00:31:02.760 --> 00:31:05.269 align:start position:0% one thing when you start offloading stuff<00:31:03.299> into<00:31:03.539> other<00:31:03.630> layers<00:31:04.020> and<00:31:04.470> doing<00:31:05.130> things 00:31:05.269 --> 00:31:05.279 align:start position:0% stuff into other layers and doing things 00:31:05.279 --> 00:31:06.769 align:start position:0% stuff into other layers and doing things if<00:31:05.460> you<00:31:05.580> roll<00:31:05.760> up<00:31:05.940> something<00:31:06.270> like<00:31:06.299> but<00:31:06.690> you 00:31:06.769 --> 00:31:06.779 align:start position:0% if you roll up something like but you 00:31:06.779 --> 00:31:09.620 align:start position:0% if you roll up something like but you have<00:31:06.929> to<00:31:07.049> figure<00:31:07.230> out<00:31:07.500> then<00:31:08.220> how<00:31:08.789> you<00:31:08.850> actually 00:31:09.620 --> 00:31:09.630 align:start position:0% have to figure out then how you actually 00:31:09.630 --> 00:31:11.240 align:start position:0% have to figure out then how you actually engage<00:31:10.320> that<00:31:10.679> interaction 00:31:11.240 --> 00:31:11.250 align:start position:0% engage that interaction 00:31:11.250 --> 00:31:13.610 align:start position:0% engage that interaction layer<00:31:11.610> on<00:31:11.760> the<00:31:11.850> user<00:31:12.059> side<00:31:12.419> then<00:31:13.320> the<00:31:13.440> other 00:31:13.610 --> 00:31:13.620 align:start position:0% layer on the user side then the other 00:31:13.620 --> 00:31:17.210 align:start position:0% layer on the user side then the other thing<00:31:14.429> that<00:31:14.460> I<00:31:14.610> I<00:31:14.760> think<00:31:15.059> it<00:31:15.480> creates<00:31:16.020> is<00:31:16.289> you 00:31:17.210 --> 00:31:17.220 align:start position:0% thing that I I think it creates is you 00:31:17.220 --> 00:31:19.580 align:start position:0% thing that I I think it creates is you know<00:31:17.279> it<00:31:17.370> does<00:31:17.580> require<00:31:18.029> like<00:31:18.809> shiny<00:31:19.140> or<00:31:19.320> newer 00:31:19.580 --> 00:31:19.590 align:start position:0% know it does require like shiny or newer 00:31:19.590 --> 00:31:22.220 align:start position:0% know it does require like shiny or newer photography<00:31:20.340> that<00:31:20.850> has<00:31:21.120> potentially<00:31:22.020> like 00:31:22.220 --> 00:31:22.230 align:start position:0% photography that has potentially like 00:31:22.230 --> 00:31:25.159 align:start position:0% photography that has potentially like unknown<00:31:23.220> unknowns<00:31:23.580> about<00:31:24.000> what<00:31:24.929> way<00:31:25.140> are 00:31:25.159 --> 00:31:25.169 align:start position:0% unknown unknowns about what way are 00:31:25.169 --> 00:31:27.020 align:start position:0% unknown unknowns about what way are built<00:31:25.470> really<00:31:25.679> play<00:31:26.070> something 00:31:27.020 --> 00:31:27.030 align:start position:0% built really play something 00:31:27.030 --> 00:31:30.110 align:start position:0% built really play something hello<00:31:27.300> where<00:31:28.020> there<00:31:28.590> is<00:31:28.830> Vista<00:31:29.550> to<00:31:29.640> be<00:31:29.790> like<00:31:29.940> a 00:31:30.110 --> 00:31:30.120 align:start position:0% hello where there is Vista to be like a 00:31:30.120 --> 00:31:32.690 align:start position:0% hello where there is Vista to be like a weakling<00:31:30.510> trustless<00:31:30.960> every<00:31:31.380> cursive<00:31:31.700> you 00:31:32.690 --> 00:31:32.700 align:start position:0% weakling trustless every cursive you 00:31:32.700 --> 00:31:36.590 align:start position:0% weakling trustless every cursive you know<00:31:32.790> the<00:31:33.470> trilogy<00:31:34.470> privacy<00:31:35.070> but<00:31:35.550> there's<00:31:36.420> so 00:31:36.590 --> 00:31:36.600 align:start position:0% know the trilogy privacy but there's so 00:31:36.600 --> 00:31:38.480 align:start position:0% know the trilogy privacy but there's so much<00:31:36.750> that's<00:31:36.810> not<00:31:37.110> known<00:31:37.320> about<00:31:37.530> it<00:31:37.830> and<00:31:37.980> you 00:31:38.480 --> 00:31:38.490 align:start position:0% much that's not known about it and you 00:31:38.490 --> 00:31:40.490 align:start position:0% much that's not known about it and you said<00:31:38.640> to<00:31:38.790> understand<00:31:39.600> those<00:31:39.750> trade-offs<00:31:40.200> when 00:31:40.490 --> 00:31:40.500 align:start position:0% said to understand those trade-offs when 00:31:40.500 --> 00:31:42.670 align:start position:0% said to understand those trade-offs when when<00:31:41.490> approaching<00:31:41.790> this<00:31:42.030> doesn't<00:31:42.360> say<00:31:42.480> that 00:31:42.670 --> 00:31:42.680 align:start position:0% when approaching this doesn't say that 00:31:42.680 --> 00:31:45.620 align:start position:0% when approaching this doesn't say that there<00:31:43.680> isn't<00:31:43.920> still<00:31:44.430> some<00:31:44.610> alignment<00:31:45.150> on<00:31:45.390> like 00:31:45.620 --> 00:31:45.630 align:start position:0% there isn't still some alignment on like 00:31:45.630 --> 00:31:48.710 align:start position:0% there isn't still some alignment on like yeah<00:31:46.500> there<00:31:46.920> being<00:31:47.220> a<00:31:47.730> mutual<00:31:48.270> advantage<00:31:48.600> to 00:31:48.710 --> 00:31:48.720 align:start position:0% yeah there being a mutual advantage to 00:31:48.720 --> 00:31:50.930 align:start position:0% yeah there being a mutual advantage to having<00:31:49.020> less<00:31:49.500> state<00:31:49.860> I'm<00:31:50.130> getting<00:31:50.430> blockchain 00:31:50.930 --> 00:31:50.940 align:start position:0% having less state I'm getting blockchain 00:31:50.940 --> 00:31:53.450 align:start position:0% having less state I'm getting blockchain and<00:31:51.180> more<00:31:51.780> of<00:31:51.870> it<00:31:51.990> sort<00:31:52.560> of<00:31:52.650> private<00:31:53.070> and<00:31:53.310> an 00:31:53.450 --> 00:31:53.460 align:start position:0% and more of it sort of private and an 00:31:53.460 --> 00:31:56.480 align:start position:0% and more of it sort of private and an ulcer<00:31:53.730> that<00:31:53.940> just<00:31:54.120> creates<00:31:54.540> new<00:31:55.490> complexities 00:31:56.480 --> 00:31:56.490 align:start position:0% ulcer that just creates new complexities 00:31:56.490 --> 00:31:59.150 align:start position:0% ulcer that just creates new complexities that<00:31:56.520> have<00:31:56.850> to<00:31:56.970> deal<00:31:57.150> with<00:31:57.180> like<00:31:58.130> Josh<00:31:59.130> is 00:31:59.150 --> 00:31:59.160 align:start position:0% that have to deal with like Josh is 00:31:59.160 --> 00:32:02.330 align:start position:0% that have to deal with like Josh is saying<00:31:59.550> at<00:31:59.700> the<00:32:00.110> technical<00:32:01.110> level<00:32:01.140> that<00:32:01.830> seems 00:32:02.330 --> 00:32:02.340 align:start position:0% saying at the technical level that seems 00:32:02.340 --> 00:32:03.980 align:start position:0% saying at the technical level that seems to<00:32:02.640> be<00:32:02.730> true<00:32:03.120> which<00:32:03.540> is<00:32:03.660> an<00:32:03.750> interesting 00:32:03.980 --> 00:32:03.990 align:start position:0% to be true which is an interesting 00:32:03.990 --> 00:32:06.470 align:start position:0% to be true which is an interesting switch<00:32:04.470> because<00:32:04.890> usually<00:32:05.670> in<00:32:06.000> traditional 00:32:06.470 --> 00:32:06.480 align:start position:0% switch because usually in traditional 00:32:06.480 --> 00:32:08.050 align:start position:0% switch because usually in traditional centralized<00:32:06.990> systems<00:32:07.380> when<00:32:07.560> you<00:32:07.680> added 00:32:08.050 --> 00:32:08.060 align:start position:0% centralized systems when you added 00:32:08.060 --> 00:32:10.730 align:start position:0% centralized systems when you added cryptography<00:32:09.090> maybe<00:32:09.510> it's<00:32:09.660> slower<00:32:09.990> and<00:32:10.230> so 00:32:10.730 --> 00:32:10.740 align:start position:0% cryptography maybe it's slower and so 00:32:10.740 --> 00:32:12.950 align:start position:0% cryptography maybe it's slower and so you<00:32:10.800> make<00:32:10.950> a<00:32:10.980> justified<00:32:11.580> vs.<00:32:12.090> here<00:32:12.570> it's 00:32:12.950 --> 00:32:12.960 align:start position:0% you make a justified vs. here it's 00:32:12.960 --> 00:32:14.840 align:start position:0% you make a justified vs. here it's reflective<00:32:13.350> of<00:32:13.440> your<00:32:13.500> new<00:32:13.770> feed<00:32:14.010> data<00:32:14.280> an 00:32:14.840 --> 00:32:14.850 align:start position:0% reflective of your new feed data an 00:32:14.850 --> 00:32:15.920 align:start position:0% reflective of your new feed data an assistant<00:32:15.270> that's<00:32:15.330> all<00:32:15.480> the<00:32:15.570> burden<00:32:15.900> that 00:32:15.920 --> 00:32:15.930 align:start position:0% assistant that's all the burden that 00:32:15.930 --> 00:32:19.190 align:start position:0% assistant that's all the burden that makes<00:32:16.170> a<00:32:16.290> pass<00:32:16.530> code<00:32:16.820> but<00:32:17.820> the<00:32:18.630> social 00:32:19.190 --> 00:32:19.200 align:start position:0% makes a pass code but the social 00:32:19.200 --> 00:32:21.380 align:start position:0% makes a pass code but the social complexity<00:32:19.830> of<00:32:20.100> the<00:32:20.310> spike<00:32:20.610> shedding<00:32:21.060> of<00:32:21.150> rich 00:32:21.380 --> 00:32:21.390 align:start position:0% complexity of the spike shedding of rich 00:32:21.390 --> 00:32:23.660 align:start position:0% complexity of the spike shedding of rich photography<00:32:22.170> do<00:32:22.320> we<00:32:22.560> use<00:32:22.770> or<00:32:23.040> hopefully<00:32:23.430> if<00:32:23.580> it 00:32:23.660 --> 00:32:23.670 align:start position:0% photography do we use or hopefully if it 00:32:23.670 --> 00:32:25.670 align:start position:0% photography do we use or hopefully if it is<00:32:23.820> not<00:32:24.000> common<00:32:24.300> sense<00:32:24.570> I'll<00:32:24.930> write<00:32:25.470> this 00:32:25.670 --> 00:32:25.680 align:start position:0% is not common sense I'll write this 00:32:25.680 --> 00:32:26.960 align:start position:0% is not common sense I'll write this whole<00:32:25.860> debate<00:32:26.130> up<00:32:26.310> which<00:32:26.520> weights 00:32:26.960 --> 00:32:26.970 align:start position:0% whole debate up which weights 00:32:26.970 --> 00:32:28.850 align:start position:0% whole debate up which weights assumptions<00:32:27.510> which<00:32:27.720> elliptic<00:32:28.200> curves<00:32:28.470> right 00:32:28.850 --> 00:32:28.860 align:start position:0% assumptions which elliptic curves right 00:32:28.860 --> 00:32:31.610 align:start position:0% assumptions which elliptic curves right which<00:32:29.100> you<00:32:29.700> know<00:32:29.850> do<00:32:30.300> we<00:32:30.420> believe<00:32:30.960> in<00:32:31.170> falsify 00:32:31.610 --> 00:32:31.620 align:start position:0% which you know do we believe in falsify 00:32:31.620 --> 00:32:33.110 align:start position:0% which you know do we believe in falsify about<00:32:31.860> subject<00:32:32.280> you've<00:32:32.610> seen<00:32:32.820> these<00:32:33.000> things 00:32:33.110 --> 00:32:33.120 align:start position:0% about subject you've seen these things 00:32:33.120 --> 00:32:35.420 align:start position:0% about subject you've seen these things on<00:32:33.300> Twitter<00:32:33.480> can<00:32:34.230> slow<00:32:34.500> things<00:32:34.710> down<00:32:34.860> it's 00:32:35.420 --> 00:32:35.430 align:start position:0% on Twitter can slow things down it's 00:32:35.430 --> 00:32:36.920 align:start position:0% on Twitter can slow things down it's very<00:32:35.640> impractical<00:32:35.970> from<00:32:36.450> a<00:32:36.510> socialist 00:32:36.920 --> 00:32:36.930 align:start position:0% very impractical from a socialist 00:32:36.930 --> 00:32:39.070 align:start position:0% very impractical from a socialist perspective<00:32:37.080> developers<00:32:37.770> well<00:32:38.220> in<00:32:38.640> the 00:32:39.070 --> 00:32:39.080 align:start position:0% perspective developers well in the 00:32:39.080 --> 00:32:41.540 align:start position:0% perspective developers well in the interests<00:32:40.080> of<00:32:40.140> scaling<00:32:40.650> the<00:32:40.860> debate<00:32:41.190> and 00:32:41.540 --> 00:32:41.550 align:start position:0% interests of scaling the debate and 00:32:41.550 --> 00:32:43.190 align:start position:0% interests of scaling the debate and scaling<00:32:41.970> the<00:32:42.060> system<00:32:42.390> we're<00:32:42.630> gonna<00:32:42.750> put<00:32:43.050> those 00:32:43.190 --> 00:32:43.200 align:start position:0% scaling the system we're gonna put those 00:32:43.200 --> 00:32:45.200 align:start position:0% scaling the system we're gonna put those off<00:32:43.380> for<00:32:43.410> five<00:32:43.830> years<00:32:44.130> and<00:32:44.370> what<00:32:44.940> it's<00:32:45.060> going 00:32:45.200 --> 00:32:45.210 align:start position:0% off for five years and what it's going 00:32:45.210 --> 00:32:49.820 align:start position:0% off for five years and what it's going to<00:32:45.270> ignore<00:32:46.110> and<00:32:46.850> that<00:32:47.850> is<00:32:48.480> tempting<00:32:48.960> but<00:32:49.320> if<00:32:49.470> we 00:32:49.820 --> 00:32:49.830 align:start position:0% to ignore and that is tempting but if we 00:32:49.830 --> 00:32:51.530 align:start position:0% to ignore and that is tempting but if we do<00:32:49.950> that<00:32:49.980> we<00:32:50.370> will<00:32:50.490> find<00:32:50.550> out<00:32:50.880> five<00:32:51.120> years<00:32:51.360> that 00:32:51.530 --> 00:32:51.540 align:start position:0% do that we will find out five years that 00:32:51.540 --> 00:32:53.020 align:start position:0% do that we will find out five years that we<00:32:51.630> can't<00:32:51.870> have<00:32:52.050> privacy 00:32:53.020 --> 00:32:53.030 align:start position:0% we can't have privacy 00:32:53.030 --> 00:32:57.080 align:start position:0% we can't have privacy and<00:32:54.030> we'll<00:32:54.420> be<00:32:54.480> doing<00:32:54.630> the<00:32:54.870> pixel<00:32:55.970> there's<00:32:56.970> a 00:32:57.080 --> 00:32:57.090 align:start position:0% and we'll be doing the pixel there's a 00:32:57.090 --> 00:32:58.850 align:start position:0% and we'll be doing the pixel there's a role<00:32:57.330> for<00:32:57.360> Standardization<00:32:58.260> here<00:32:58.530> as<00:32:58.650> well 00:32:58.850 --> 00:32:58.860 align:start position:0% role for Standardization here as well 00:32:58.860 --> 00:33:00.320 align:start position:0% role for Standardization here as well and<00:32:59.040> doing<00:32:59.280> with<00:32:59.400> the<00:32:59.520> issue<00:32:59.670> that<00:32:59.970> ian<00:33:00.240> is 00:33:00.320 --> 00:33:00.330 align:start position:0% and doing with the issue that ian is 00:33:00.330 --> 00:33:03.470 align:start position:0% and doing with the issue that ian is talking<00:33:00.720> about<00:33:01.280> that<00:33:02.280> you<00:33:03.000> know<00:33:03.120> the<00:33:03.210> sort<00:33:03.420> of 00:33:03.470 --> 00:33:03.480 align:start position:0% talking about that you know the sort of 00:33:03.480 --> 00:33:05.990 align:start position:0% talking about that you know the sort of prank<00:33:03.630> mutation<00:33:04.140> of<00:33:04.320> the<00:33:04.350> complexity<00:33:05.040> you<00:33:05.820> see 00:33:05.990 --> 00:33:06.000 align:start position:0% prank mutation of the complexity you see 00:33:06.000 --> 00:33:08.299 align:start position:0% prank mutation of the complexity you see this<00:33:06.120> in<00:33:06.299> other<00:33:06.450> areas<00:33:06.870> as<00:33:07.049> well<00:33:07.080> where<00:33:07.710> those 00:33:08.299 --> 00:33:08.309 align:start position:0% this in other areas as well where those 00:33:08.309 --> 00:33:13.240 align:start position:0% this in other areas as well where those things<00:33:09.299> that<00:33:09.720> are<00:33:09.929> similar<00:33:10.530> across<00:33:10.830> products 00:33:13.240 --> 00:33:13.250 align:start position:0% things that are similar across products 00:33:13.250 --> 00:33:15.500 align:start position:0% things that are similar across products can<00:33:14.250> be<00:33:14.280> standardized<00:33:15.000> while<00:33:15.270> allowing 00:33:15.500 --> 00:33:15.510 align:start position:0% can be standardized while allowing 00:33:15.510 --> 00:33:17.299 align:start position:0% can be standardized while allowing people<00:33:15.900> still<00:33:16.170> compete<00:33:16.559> in<00:33:16.710> the<00:33:16.799> areas<00:33:17.100> where 00:33:17.299 --> 00:33:17.309 align:start position:0% people still compete in the areas where 00:33:17.309 --> 00:33:19.070 align:start position:0% people still compete in the areas where there's<00:33:17.460> more<00:33:17.640> innovation<00:33:18.150> we<00:33:18.299> saw<00:33:18.480> that<00:33:18.660> you 00:33:19.070 --> 00:33:19.080 align:start position:0% there's more innovation we saw that you 00:33:19.080 --> 00:33:20.810 align:start position:0% there's more innovation we saw that you seen<00:33:19.290> that<00:33:19.410> in<00:33:19.530> cryptography<00:33:19.860> for<00:33:20.400> example 00:33:20.810 --> 00:33:20.820 align:start position:0% seen that in cryptography for example 00:33:20.820 --> 00:33:23.210 align:start position:0% seen that in cryptography for example right<00:33:20.970> there<00:33:21.000> are<00:33:21.299> standard<00:33:21.780> ways<00:33:21.990> to<00:33:22.260> do<00:33:22.440> many 00:33:23.210 --> 00:33:23.220 align:start position:0% right there are standard ways to do many 00:33:23.220 --> 00:33:25.970 align:start position:0% right there are standard ways to do many of<00:33:23.309> the<00:33:23.520> older<00:33:24.290> cryptographic<00:33:25.290> primitives 00:33:25.970 --> 00:33:25.980 align:start position:0% of the older cryptographic primitives 00:33:25.980 --> 00:33:27.980 align:start position:0% of the older cryptographic primitives it's<00:33:26.220> understood<00:33:26.790> how<00:33:27.030> to<00:33:27.059> do<00:33:27.330> them<00:33:27.540> like<00:33:27.780> key 00:33:27.980 --> 00:33:27.990 align:start position:0% it's understood how to do them like key 00:33:27.990 --> 00:33:29.930 align:start position:0% it's understood how to do them like key size<00:33:28.230> to<00:33:28.470> me<00:33:28.590> how<00:33:28.830> to<00:33:28.890> generate<00:33:29.340> this<00:33:29.549> or<00:33:29.760> that 00:33:29.930 --> 00:33:29.940 align:start position:0% size to me how to generate this or that 00:33:29.940 --> 00:33:32.270 align:start position:0% size to me how to generate this or that even<00:33:30.600> formats<00:33:31.049> and<00:33:31.260> so<00:33:31.470> on<00:33:31.650> are<00:33:31.770> standardized 00:33:32.270 --> 00:33:32.280 align:start position:0% even formats and so on are standardized 00:33:32.280 --> 00:33:34.820 align:start position:0% even formats and so on are standardized and<00:33:32.490> that's<00:33:32.669> all<00:33:32.850> useful<00:33:33.530> for<00:33:34.530> a<00:33:34.559> bunch<00:33:34.740> of 00:33:34.820 --> 00:33:34.830 align:start position:0% and that's all useful for a bunch of 00:33:34.830 --> 00:33:37.580 align:start position:0% and that's all useful for a bunch of reasons<00:33:34.890> one<00:33:35.340> first<00:33:36.299> because<00:33:36.750> it<00:33:37.080> allows<00:33:37.320> more 00:33:37.580 --> 00:33:37.590 align:start position:0% reasons one first because it allows more 00:33:37.590 --> 00:33:39.770 align:start position:0% reasons one first because it allows more vetting<00:33:37.980> by<00:33:38.010> the<00:33:38.220> community<00:33:38.760> of<00:33:39.059> particular 00:33:39.770 --> 00:33:39.780 align:start position:0% vetting by the community of particular 00:33:39.780 --> 00:33:41.419 align:start position:0% vetting by the community of particular approaches<00:33:40.230> but<00:33:40.410> also<00:33:40.559> because<00:33:41.010> it<00:33:41.130> helps 00:33:41.419 --> 00:33:41.429 align:start position:0% approaches but also because it helps 00:33:41.429 --> 00:33:43.250 align:start position:0% approaches but also because it helps with<00:33:41.490> the<00:33:41.640> emergence<00:33:42.179> of<00:33:42.240> open<00:33:43.049> source 00:33:43.250 --> 00:33:43.260 align:start position:0% with the emergence of open source 00:33:43.260 --> 00:33:45.200 align:start position:0% with the emergence of open source implementations<00:33:44.100> so<00:33:44.610> you<00:33:44.669> don't<00:33:44.880> have<00:33:45.030> people 00:33:45.200 --> 00:33:45.210 align:start position:0% implementations so you don't have people 00:33:45.210 --> 00:33:48.380 align:start position:0% implementations so you don't have people reemployment<00:33:45.870> in<00:33:46.140> the<00:33:46.260> same<00:33:46.470> stuff<00:33:46.740> so<00:33:47.330> how<00:33:48.330> do 00:33:48.380 --> 00:33:48.390 align:start position:0% reemployment in the same stuff so how do 00:33:48.390 --> 00:33:50.180 align:start position:0% reemployment in the same stuff so how do you<00:33:48.480> think<00:33:48.540> that<00:33:48.750> interacts<00:33:49.140> with<00:33:49.320> what<00:33:49.890> seems 00:33:50.180 --> 00:33:50.190 align:start position:0% you think that interacts with what seems 00:33:50.190 --> 00:33:51.789 align:start position:0% you think that interacts with what seems to<00:33:50.280> be<00:33:50.429> emerging<00:33:50.669> there<00:33:51.059> where<00:33:51.270> we<00:33:51.390> have 00:33:51.789 --> 00:33:51.799 align:start position:0% to be emerging there where we have 00:33:51.799 --> 00:33:54.289 align:start position:0% to be emerging there where we have companies<00:33:52.799> that<00:33:53.040> are<00:33:53.160> basically<00:33:53.520> marketing 00:33:54.289 --> 00:33:54.299 align:start position:0% companies that are basically marketing 00:33:54.299 --> 00:33:57.110 align:start position:0% companies that are basically marketing not<00:33:55.169> product<00:33:55.740> but<00:33:55.890> literally<00:33:56.190> go<00:33:56.429> away<00:33:56.669> we 00:33:57.110 --> 00:33:57.120 align:start position:0% not product but literally go away we 00:33:57.120 --> 00:33:58.400 align:start position:0% not product but literally go away we don't<00:33:57.270> see<00:33:57.419> where<00:33:57.570> knowledge<00:33:57.690> encryption 00:33:58.400 --> 00:33:58.410 align:start position:0% don't see where knowledge encryption 00:33:58.410 --> 00:34:00.380 align:start position:0% don't see where knowledge encryption proof<00:33:58.650> that<00:33:58.890> like<00:33:59.610> trying<00:33:59.820> to<00:33:59.910> push<00:34:00.150> these 00:34:00.380 --> 00:34:00.390 align:start position:0% proof that like trying to push these 00:34:00.390 --> 00:34:02.120 align:start position:0% proof that like trying to push these things<00:34:00.450> so<00:34:00.990> you're<00:34:01.110> gonna<00:34:01.200> that<00:34:01.980> could 00:34:02.120 --> 00:34:02.130 align:start position:0% things so you're gonna that could 00:34:02.130 --> 00:34:03.860 align:start position:0% things so you're gonna that could disappear<00:34:02.580> in<00:34:02.640> like<00:34:02.850> five<00:34:03.090> years<00:34:03.360> that<00:34:03.660> just 00:34:03.860 --> 00:34:03.870 align:start position:0% disappear in like five years that just 00:34:03.870 --> 00:34:06.440 align:start position:0% disappear in like five years that just effective<00:34:04.830> practice<00:34:05.190> is<00:34:05.340> a<00:34:05.400> very<00:34:05.610> nascent 00:34:06.440 --> 00:34:06.450 align:start position:0% effective practice is a very nascent 00:34:06.450 --> 00:34:08.930 align:start position:0% effective practice is a very nascent new<00:34:06.900> system<00:34:07.410> is<00:34:07.620> this<00:34:07.770> be<00:34:08.070> a<00:34:08.100> problem<00:34:08.609> of<00:34:08.760> like 00:34:08.930 --> 00:34:08.940 align:start position:0% new system is this be a problem of like 00:34:08.940 --> 00:34:10.940 align:start position:0% new system is this be a problem of like you're<00:34:09.389> not<00:34:09.540> gonna<00:34:09.720> standardize<00:34:10.290> this<00:34:10.500> is<00:34:10.679> one 00:34:10.940 --> 00:34:10.950 align:start position:0% you're not gonna standardize this is one 00:34:10.950 --> 00:34:12.700 align:start position:0% you're not gonna standardize this is one guy<00:34:11.100> says<00:34:11.340> they<00:34:11.460> want<00:34:11.609> to<00:34:11.669> standardize<00:34:11.940> on 00:34:12.700 --> 00:34:12.710 align:start position:0% guy says they want to standardize on 00:34:12.710 --> 00:34:15.470 align:start position:0% guy says they want to standardize on they<00:34:13.710> and<00:34:14.250> someone<00:34:14.879> saying<00:34:15.359> something 00:34:15.470 --> 00:34:15.480 align:start position:0% they and someone saying something 00:34:15.480 --> 00:34:17.780 align:start position:0% they and someone saying something completely<00:34:15.960> different<00:34:16.399> but<00:34:17.399> if<00:34:17.520> we<00:34:17.609> have<00:34:17.760> a 00:34:17.780 --> 00:34:17.790 align:start position:0% completely different but if we have a 00:34:17.790 --> 00:34:19.700 align:start position:0% completely different but if we have a strong<00:34:18.030> cryptography<00:34:18.419> stood<00:34:19.290> on<00:34:19.440> a<00:34:19.470> you'll 00:34:19.700 --> 00:34:19.710 align:start position:0% strong cryptography stood on a you'll 00:34:19.710 --> 00:34:22.490 align:start position:0% strong cryptography stood on a you'll remember<00:34:19.919> I<00:34:20.389> mean<00:34:21.389> this<00:34:21.600> standardization 00:34:22.490 --> 00:34:22.500 align:start position:0% remember I mean this standardization 00:34:22.500 --> 00:34:25.700 align:start position:0% remember I mean this standardization works<00:34:23.159> where<00:34:23.580> there<00:34:23.879> is<00:34:24.149> enough<00:34:24.750> agreement<00:34:25.530> on 00:34:25.700 --> 00:34:25.710 align:start position:0% works where there is enough agreement on 00:34:25.710 --> 00:34:28.220 align:start position:0% works where there is enough agreement on where<00:34:26.310> how<00:34:26.820> some<00:34:27.179> part<00:34:27.450> of<00:34:27.510> the<00:34:27.600> system<00:34:27.929> would 00:34:28.220 --> 00:34:28.230 align:start position:0% where how some part of the system would 00:34:28.230 --> 00:34:30.409 align:start position:0% where how some part of the system would work<00:34:28.609> you<00:34:29.609> know<00:34:29.700> you<00:34:29.760> can<00:34:30.030> come<00:34:30.270> up<00:34:30.300> with 00:34:30.409 --> 00:34:30.419 align:start position:0% work you know you can come up with 00:34:30.419 --> 00:34:33.050 align:start position:0% work you know you can come up with standards<00:34:30.899> for<00:34:31.409> state<00:34:31.919> verification<00:34:32.220> of<00:34:32.850> zero 00:34:33.050 --> 00:34:33.060 align:start position:0% standards for state verification of zero 00:34:33.060 --> 00:34:35.510 align:start position:0% standards for state verification of zero knowledge<00:34:33.270> proof<00:34:33.450> maybe<00:34:34.010> without<00:34:35.010> needing<00:34:35.490> to 00:34:35.510 --> 00:34:35.520 align:start position:0% knowledge proof maybe without needing to 00:34:35.520 --> 00:34:36.770 align:start position:0% knowledge proof maybe without needing to have<00:34:35.730> a<00:34:35.760> standard<00:34:36.240> for<00:34:36.389> how 00:34:36.770 --> 00:34:36.780 align:start position:0% have a standard for how 00:34:36.780 --> 00:34:38.570 align:start position:0% have a standard for how generate<00:34:37.200> the<00:34:37.350> proof<00:34:37.590> for<00:34:37.830> what<00:34:37.980> sir<00:34:38.220> how<00:34:38.490> you 00:34:38.570 --> 00:34:38.580 align:start position:0% generate the proof for what sir how you 00:34:38.580 --> 00:34:39.919 align:start position:0% generate the proof for what sir how you build<00:34:38.820> the<00:34:38.880> circuit<00:34:39.300> that<00:34:39.419> you're<00:34:39.570> proving 00:34:39.919 --> 00:34:39.929 align:start position:0% build the circuit that you're proving 00:34:39.929 --> 00:34:44.000 align:start position:0% build the circuit that you're proving and<00:34:40.050> so<00:34:40.200> on<00:34:40.940> so<00:34:42.110> you<00:34:43.110> know<00:34:43.140> and<00:34:43.440> similarly<00:34:43.800> in 00:34:44.000 --> 00:34:44.010 align:start position:0% and so on so you know and similarly in 00:34:44.010 --> 00:34:46.390 align:start position:0% and so on so you know and similarly in other<00:34:44.159> systems<00:34:44.429> there<00:34:45.060> are<00:34:45.240> parts<00:34:45.600> that<00:34:45.690> are 00:34:46.390 --> 00:34:46.400 align:start position:0% other systems there are parts that are 00:34:46.400 --> 00:34:49.040 align:start position:0% other systems there are parts that are standardized<00:34:47.400> and<00:34:47.909> the<00:34:48.419> standards<00:34:48.840> can<00:34:48.990> be 00:34:49.040 --> 00:34:49.050 align:start position:0% standardized and the standards can be 00:34:49.050 --> 00:34:50.720 align:start position:0% standardized and the standards can be pluggable<00:34:49.590> where<00:34:49.740> people<00:34:50.040> can<00:34:50.190> plug<00:34:50.429> in<00:34:50.580> their 00:34:50.720 --> 00:34:50.730 align:start position:0% pluggable where people can plug in their 00:34:50.730 --> 00:34:52.640 align:start position:0% pluggable where people can plug in their own<00:34:50.909> secret<00:34:51.300> sauce<00:34:51.540> in<00:34:52.080> the<00:34:52.290> areas<00:34:52.620> where 00:34:52.640 --> 00:34:52.650 align:start position:0% own secret sauce in the areas where 00:34:52.650 --> 00:34:54.470 align:start position:0% own secret sauce in the areas where there<00:34:53.040> is<00:34:53.220> a<00:34:53.250> lot<00:34:53.550> of<00:34:53.640> innovation<00:34:53.850> and<00:34:54.300> where 00:34:54.470 --> 00:34:54.480 align:start position:0% there is a lot of innovation and where 00:34:54.480 --> 00:34:56.840 align:start position:0% there is a lot of innovation and where it's<00:34:54.659> a<00:34:54.750> little<00:34:54.929> bit<00:34:55.020> less<00:34:55.169> so<00:34:55.409> I'm<00:34:56.400> not<00:34:56.640> an 00:34:56.840 --> 00:34:56.850 align:start position:0% it's a little bit less so I'm not an 00:34:56.850 --> 00:34:58.250 align:start position:0% it's a little bit less so I'm not an expert<00:34:57.210> on<00:34:57.450> the<00:34:57.600> history<00:34:57.720> of<00:34:57.960> cryptography 00:34:58.250 --> 00:34:58.260 align:start position:0% expert on the history of cryptography 00:34:58.260 --> 00:35:00.890 align:start position:0% expert on the history of cryptography but<00:34:58.980> I<00:34:59.160> do<00:34:59.220> think<00:34:59.550> that<00:34:59.790> there<00:35:00.210> was<00:35:00.420> kind<00:35:00.780> of 00:35:00.890 --> 00:35:00.900 align:start position:0% but I do think that there was kind of 00:35:00.900 --> 00:35:03.650 align:start position:0% but I do think that there was kind of similar<00:35:01.200> things<00:35:02.190> taking<00:35:02.670> place<00:35:02.910> with<00:35:03.210> early 00:35:03.650 --> 00:35:03.660 align:start position:0% similar things taking place with early 00:35:03.660 --> 00:35:06.830 align:start position:0% similar things taking place with early encryption<00:35:04.230> right<00:35:04.500> where<00:35:04.860> it<00:35:04.980> was<00:35:05.190> in<00:35:06.030> private 00:35:06.830 --> 00:35:06.840 align:start position:0% encryption right where it was in private 00:35:06.840 --> 00:35:08.480 align:start position:0% encryption right where it was in private companies<00:35:06.990> and<00:35:07.530> they<00:35:07.740> selected<00:35:08.310> some 00:35:08.480 --> 00:35:08.490 align:start position:0% companies and they selected some 00:35:08.490 --> 00:35:10.640 align:start position:0% companies and they selected some parameters<00:35:09.120> and<00:35:09.360> was<00:35:09.480> like<00:35:09.660> old<00:35:09.900> doc<00:35:10.140> magic 00:35:10.640 --> 00:35:10.650 align:start position:0% parameters and was like old doc magic 00:35:10.650 --> 00:35:12.830 align:start position:0% parameters and was like old doc magic and<00:35:11.040> over<00:35:11.310> time<00:35:11.580> these<00:35:11.820> things<00:35:12.150> where 00:35:12.830 --> 00:35:12.840 align:start position:0% and over time these things where 00:35:12.840 --> 00:35:13.730 align:start position:0% and over time these things where battle-tested 00:35:13.730 --> 00:35:13.740 align:start position:0% battle-tested 00:35:13.740 --> 00:35:16.490 align:start position:0% battle-tested became<00:35:14.070> established<00:35:14.730> were<00:35:15.110> republished<00:35:16.110> and 00:35:16.490 --> 00:35:16.500 align:start position:0% became established were republished and 00:35:16.500 --> 00:35:18.770 align:start position:0% became established were republished and more<00:35:16.860> open<00:35:17.190> source<00:35:17.340> wait<00:35:17.730> so<00:35:18.210> maybe<00:35:18.480> we're 00:35:18.770 --> 00:35:18.780 align:start position:0% more open source wait so maybe we're 00:35:18.780 --> 00:35:21.500 align:start position:0% more open source wait so maybe we're just<00:35:19.050> on<00:35:19.500> track<00:35:19.860> but<00:35:20.280> I<00:35:20.340> do<00:35:20.970> see<00:35:21.180> what<00:35:21.360> they're 00:35:21.500 --> 00:35:21.510 align:start position:0% just on track but I do see what they're 00:35:21.510 --> 00:35:23.140 align:start position:0% just on track but I do see what they're getting<00:35:21.630> at<00:35:21.930> that<00:35:22.110> this<00:35:22.350> could<00:35:22.620> be<00:35:22.770> an<00:35:22.830> issue 00:35:23.140 --> 00:35:23.150 align:start position:0% getting at that this could be an issue 00:35:23.150 --> 00:35:25.730 align:start position:0% getting at that this could be an issue the<00:35:24.150> reason<00:35:24.420> I<00:35:24.480> mentioned<00:35:24.840> it<00:35:25.260> seems<00:35:25.500> to<00:35:25.650> be 00:35:25.730 --> 00:35:25.740 align:start position:0% the reason I mentioned it seems to be 00:35:25.740 --> 00:35:28.370 align:start position:0% the reason I mentioned it seems to be middle<00:35:26.010> that's<00:35:26.730> exactly<00:35:27.150> right<00:35:27.180> or<00:35:27.780> something 00:35:28.370 --> 00:35:28.380 align:start position:0% middle that's exactly right or something 00:35:28.380 --> 00:35:30.650 align:start position:0% middle that's exactly right or something like<00:35:28.620> this<00:35:28.980> and<00:35:29.280> such<00:35:29.490> but<00:35:30.180> a<00:35:30.210> lot<00:35:30.360> of<00:35:30.480> it<00:35:30.570> was 00:35:30.650 --> 00:35:30.660 align:start position:0% like this and such but a lot of it was 00:35:30.660 --> 00:35:32.900 align:start position:0% like this and such but a lot of it was all<00:35:30.780> done<00:35:30.990> by<00:35:31.050> RSA<00:35:31.680> for<00:35:31.710> the<00:35:32.160> basic<00:35:32.640> encryption 00:35:32.900 --> 00:35:32.910 align:start position:0% all done by RSA for the basic encryption 00:35:32.910 --> 00:35:37.790 align:start position:0% all done by RSA for the basic encryption and<00:35:33.330> then<00:35:33.470> Netscape<00:35:34.470> for<00:35:36.290> plsss<00:35:37.290> all<00:35:37.410> the<00:35:37.620> time 00:35:37.790 --> 00:35:37.800 align:start position:0% and then Netscape for plsss all the time 00:35:37.800 --> 00:35:40.100 align:start position:0% and then Netscape for plsss all the time but<00:35:38.460> it<00:35:38.550> seems<00:35:38.730> like<00:35:39.030> in<00:35:39.420> those<00:35:39.600> cases<00:35:39.870> there 00:35:40.100 --> 00:35:40.110 align:start position:0% but it seems like in those cases there 00:35:40.110 --> 00:35:43.460 align:start position:0% but it seems like in those cases there was<00:35:40.200> one<00:35:40.440> comment<00:35:41.960> expertise<00:35:42.960> and<00:35:43.200> now<00:35:43.350> in 00:35:43.460 --> 00:35:43.470 align:start position:0% was one comment expertise and now in 00:35:43.470 --> 00:35:45.560 align:start position:0% was one comment expertise and now in this<00:35:43.590> cases<00:35:43.940> democratized<00:35:44.940> which<00:35:45.180> is<00:35:45.300> good 00:35:45.560 --> 00:35:45.570 align:start position:0% this cases democratized which is good 00:35:45.570 --> 00:35:48.830 align:start position:0% this cases democratized which is good but<00:35:46.410> there's<00:35:46.680> now<00:35:46.800> more<00:35:46.830> head<00:35:47.340> fighting<00:35:47.840> and 00:35:48.830 --> 00:35:48.840 align:start position:0% but there's now more head fighting and 00:35:48.840 --> 00:35:50.330 align:start position:0% but there's now more head fighting and that<00:35:49.020> sounds<00:35:49.620> different<00:35:49.950> but<00:35:50.040> that<00:35:50.190> may<00:35:50.310> be 00:35:50.330 --> 00:35:50.340 align:start position:0% that sounds different but that may be 00:35:50.340 --> 00:35:53.630 align:start position:0% that sounds different but that may be because<00:35:50.520> I'm<00:35:50.700> just<00:35:50.820> sitting<00:35:51.540> I<00:35:52.350> mean<00:35:52.920> if<00:35:53.460> you 00:35:53.630 --> 00:35:53.640 align:start position:0% because I'm just sitting I mean if you 00:35:53.640 --> 00:35:55.130 align:start position:0% because I'm just sitting I mean if you look<00:35:53.790> at<00:35:53.820> cryptographic<00:35:54.150> standards<00:35:54.570> some<00:35:55.020> of 00:35:55.130 --> 00:35:55.140 align:start position:0% look at cryptographic standards some of 00:35:55.140 --> 00:35:57.110 align:start position:0% look at cryptographic standards some of the<00:35:55.230> most<00:35:55.470> popular<00:35:56.130> standards<00:35:56.640> like<00:35:56.790> the<00:35:56.850> hash 00:35:57.110 --> 00:35:57.120 align:start position:0% the most popular standards like the hash 00:35:57.120 --> 00:35:59.360 align:start position:0% the most popular standards like the hash function<00:35:57.330> standards<00:35:57.960> for<00:35:58.170> example<00:35:58.260> or<00:35:58.830> a<00:35:58.860> yes 00:35:59.360 --> 00:35:59.370 align:start position:0% function standards for example or a yes 00:35:59.370 --> 00:36:02.930 align:start position:0% function standards for example or a yes we're<00:36:00.150> done<00:36:00.360> through<00:36:01.340> government<00:36:02.340> organized 00:36:02.930 --> 00:36:02.940 align:start position:0% we're done through government organized 00:36:02.940 --> 00:36:04.940 align:start position:0% we're done through government organized processes<00:36:03.810> although<00:36:04.110> they<00:36:04.440> were<00:36:04.500> open 00:36:04.940 --> 00:36:04.950 align:start position:0% processes although they were open 00:36:04.950 --> 00:36:07.250 align:start position:0% processes although they were open competitions<00:36:05.700> and<00:36:06.630> that<00:36:06.810> was<00:36:06.930> a<00:36:06.960> way<00:36:07.230> of 00:36:07.250 --> 00:36:07.260 align:start position:0% competitions and that was a way of 00:36:07.260 --> 00:36:09.860 align:start position:0% competitions and that was a way of organizing<00:36:07.980> the<00:36:08.760> community<00:36:08.940> and<00:36:09.510> you<00:36:09.630> had<00:36:09.840> a 00:36:09.860 --> 00:36:09.870 align:start position:0% organizing the community and you had a 00:36:09.870 --> 00:36:17.120 align:start position:0% organizing the community and you had a lot<00:36:10.170> of<00:36:10.340> it<00:36:11.340> was<00:36:11.610> community<00:36:12.180> work<00:36:12.510> and<00:36:15.170> so<00:36:16.170> lots 00:36:17.120 --> 00:36:17.130 align:start position:0% lot of it was community work and so lots 00:36:17.130 --> 00:36:20.270 align:start position:0% lot of it was community work and so lots of<00:36:17.660> lots<00:36:18.660> of<00:36:18.870> diversity<00:36:19.260> different<00:36:19.860> opinions 00:36:20.270 --> 00:36:20.280 align:start position:0% of lots of diversity different opinions 00:36:20.280 --> 00:36:22.100 align:start position:0% of lots of diversity different opinions about<00:36:20.430> how<00:36:20.700> to<00:36:20.760> do<00:36:20.970> that<00:36:21.150> but<00:36:21.360> yeah<00:36:21.600> a<00:36:21.780> strong 00:36:22.100 --> 00:36:22.110 align:start position:0% about how to do that but yeah a strong 00:36:22.110 --> 00:36:24.770 align:start position:0% about how to do that but yeah a strong standard<00:36:22.650> emerged<00:36:22.950> and<00:36:23.250> one<00:36:23.400> thing<00:36:23.580> that<00:36:23.790> got 00:36:24.770 --> 00:36:24.780 align:start position:0% standard emerged and one thing that got 00:36:24.780 --> 00:36:26.870 align:start position:0% standard emerged and one thing that got trust<00:36:25.050> out<00:36:25.260> with<00:36:25.410> that<00:36:25.530> process<00:36:25.880> obviously 00:36:26.870 --> 00:36:26.880 align:start position:0% trust out with that process obviously 00:36:26.880 --> 00:36:29.840 align:start position:0% trust out with that process obviously governments<00:36:27.630> can't<00:36:27.870> run<00:36:28.170> these<00:36:28.920> things<00:36:29.490> badly 00:36:29.840 --> 00:36:29.850 align:start position:0% governments can't run these things badly 00:36:29.850 --> 00:36:32.840 align:start position:0% governments can't run these things badly and<00:36:30.300> the<00:36:30.390> result<00:36:30.720> of<00:36:30.870> that<00:36:31.050> can<00:36:31.320> be<00:36:31.820> can<00:36:32.820> be 00:36:32.840 --> 00:36:32.850 align:start position:0% and the result of that can be can be 00:36:32.850 --> 00:36:35.960 align:start position:0% and the result of that can be can be worse<00:36:33.120> than<00:36:33.330> nothing<00:36:33.690> as<00:36:34.500> we<00:36:34.740> don't<00:36:34.830> know<00:36:34.970> but 00:36:35.960 --> 00:36:35.970 align:start position:0% worse than nothing as we don't know but 00:36:35.970 --> 00:36:37.880 align:start position:0% worse than nothing as we don't know but there<00:36:36.090> are<00:36:36.270> good<00:36:36.480> examples<00:36:36.630> good<00:36:37.290> the<00:36:37.620> good 00:36:37.880 --> 00:36:37.890 align:start position:0% there are good examples good the good 00:36:37.890 --> 00:36:40.190 align:start position:0% there are good examples good the good existence<00:36:38.670> proofs<00:36:39.030> that<00:36:39.330> this<00:36:39.570> can<00:36:39.840> be<00:36:39.990> done 00:36:40.190 --> 00:36:40.200 align:start position:0% existence proofs that this can be done 00:36:40.200 --> 00:36:42.770 align:start position:0% existence proofs that this can be done well<00:36:40.490> and<00:36:41.490> you<00:36:41.640> can<00:36:41.820> get<00:36:41.940> to<00:36:42.090> standards<00:36:42.540> even 00:36:42.770 --> 00:36:42.780 align:start position:0% well and you can get to standards even 00:36:42.780 --> 00:36:43.790 align:start position:0% well and you can get to standards even for<00:36:43.080> things<00:36:43.260> like 00:36:43.790 --> 00:36:43.800 align:start position:0% for things like 00:36:43.800 --> 00:36:47.450 align:start position:0% for things like Cyprus<00:36:44.700> where<00:36:45.300> there's<00:36:45.540> a<00:36:45.600> lot<00:36:46.020> of<00:36:46.320> a<00:36:46.920> lot<00:36:47.430> of 00:36:47.450 --> 00:36:47.460 align:start position:0% Cyprus where there's a lot of a lot of 00:36:47.460 --> 00:36:51.020 align:start position:0% Cyprus where there's a lot of a lot of different<00:36:47.790> ideas<00:36:47.850> about<00:36:48.240> how<00:36:48.360> to<00:36:48.390> do<00:36:48.600> it<00:36:49.070> and<00:36:50.070> I 00:36:51.020 --> 00:36:51.030 align:start position:0% different ideas about how to do it and I 00:36:51.030 --> 00:36:52.700 align:start position:0% different ideas about how to do it and I guess<00:36:51.330> standardization<00:36:52.200> will<00:36:52.380> help<00:36:52.560> with 00:36:52.700 --> 00:36:52.710 align:start position:0% guess standardization will help with 00:36:52.710 --> 00:36:55.610 align:start position:0% guess standardization will help with making<00:36:52.920> easier<00:36:53.460> tools<00:36:53.760> for<00:36:54.330> privacy<00:36:55.140> medicine 00:36:55.610 --> 00:36:55.620 align:start position:0% making easier tools for privacy medicine 00:36:55.620 --> 00:36:58.790 align:start position:0% making easier tools for privacy medicine so<00:36:56.600> yeah<00:36:57.600> is<00:36:57.840> there<00:36:57.930> anything<00:36:58.170> else<00:36:58.380> that<00:36:58.650> you 00:36:58.790 --> 00:36:58.800 align:start position:0% so yeah is there anything else that you 00:36:58.800 --> 00:37:00.170 align:start position:0% so yeah is there anything else that you won't<00:36:59.010> want<00:36:59.190> to<00:36:59.280> say<00:36:59.430> before<00:36:59.490> we<00:36:59.850> open<00:37:00.120> up 00:37:00.170 --> 00:37:00.180 align:start position:0% won't want to say before we open up 00:37:00.180 --> 00:37:03.850 align:start position:0% won't want to say before we open up through<00:37:00.450> our<00:37:00.510> questions 00:37:03.850 --> 00:37:03.860 align:start position:0% 00:37:03.860 --> 00:37:06.860 align:start position:0% okay<00:37:04.860> just<00:37:05.550> are<00:37:05.730> there<00:37:05.850> any<00:37:06.030> questions<00:37:06.540> from 00:37:06.860 --> 00:37:06.870 align:start position:0% okay just are there any questions from 00:37:06.870 --> 00:37:16.780 align:start position:0% okay just are there any questions from the<00:37:06.960> audience<00:37:07.080> for 00:37:16.780 --> 00:37:16.790 align:start position:0% 00:37:16.790 --> 00:37:21.410 align:start position:0% it's<00:37:17.790> like<00:37:18.150> no<00:37:18.450> I<00:37:18.840> think<00:37:19.050> some<00:37:19.380> rest 00:37:21.410 --> 00:37:21.420 align:start position:0% it's like no I think some rest 00:37:21.420 --> 00:37:24.110 align:start position:0% it's like no I think some rest could<00:37:21.930> you<00:37:22.050> talk<00:37:22.320> about<00:37:22.380> the<00:37:22.740> role<00:37:22.890> of<00:37:23.190> crypto 00:37:24.110 --> 00:37:24.120 align:start position:0% could you talk about the role of crypto 00:37:24.120 --> 00:37:26.600 align:start position:0% could you talk about the role of crypto currency<00:37:24.600> exchanges<00:37:25.320> in<00:37:25.620> this<00:37:25.770> debate<00:37:25.950> and 00:37:26.600 --> 00:37:26.610 align:start position:0% currency exchanges in this debate and 00:37:26.610 --> 00:37:29.090 align:start position:0% currency exchanges in this debate and pass<00:37:26.880> in<00:37:27.180> your<00:37:27.210> answers<00:37:27.720> could<00:37:27.960> you<00:37:28.140> debate 00:37:29.090 --> 00:37:29.100 align:start position:0% pass in your answers could you debate 00:37:29.100 --> 00:37:31.460 align:start position:0% pass in your answers could you debate amongst<00:37:29.340> yourselves<00:37:29.700> or<00:37:29.970> talk<00:37:30.200> about<00:37:31.200> what 00:37:31.460 --> 00:37:31.470 align:start position:0% amongst yourselves or talk about what 00:37:31.470 --> 00:37:33.680 align:start position:0% amongst yourselves or talk about what you'd<00:37:31.620> like<00:37:31.650> to<00:37:32.070> see<00:37:32.250> press<00:37:32.760> of<00:37:33.180> what<00:37:33.390> you 00:37:33.680 --> 00:37:33.690 align:start position:0% you'd like to see press of what you 00:37:33.690 --> 00:37:36.680 align:start position:0% you'd like to see press of what you think<00:37:34.290> will<00:37:34.530> happen<00:37:35.120> so<00:37:36.120> the<00:37:36.330> question<00:37:36.630> was 00:37:36.680 --> 00:37:36.690 align:start position:0% think will happen so the question was 00:37:36.690 --> 00:37:42.320 align:start position:0% think will happen so the question was how<00:37:36.750> can<00:37:36.960> exchanges<00:37:37.920> in<00:37:38.430> the<00:37:38.610> future<00:37:41.150> scale<00:37:42.150> in 00:37:42.320 --> 00:37:42.330 align:start position:0% how can exchanges in the future scale in 00:37:42.330 --> 00:37:44.900 align:start position:0% how can exchanges in the future scale in the<00:37:42.420> taxi<00:37:42.900> market<00:37:43.830> is<00:37:44.460> going<00:37:44.640> to<00:37:44.700> be<00:37:44.760> very 00:37:44.900 --> 00:37:44.910 align:start position:0% the taxi market is going to be very 00:37:44.910 --> 00:37:47.030 align:start position:0% the taxi market is going to be very creepy<00:37:45.300> but<00:37:45.510> with<00:37:45.930> exchanges<00:37:46.530> my<00:37:46.800> major 00:37:47.030 --> 00:37:47.040 align:start position:0% creepy but with exchanges my major 00:37:47.040 --> 00:37:49.070 align:start position:0% creepy but with exchanges my major concern<00:37:47.520> is<00:37:47.670> the<00:37:47.850> last<00:37:48.030> exchanges<00:37:48.570> maybe<00:37:48.780> for 00:37:49.070 --> 00:37:49.080 align:start position:0% concern is the last exchanges maybe for 00:37:49.080 --> 00:37:51.410 align:start position:0% concern is the last exchanges maybe for a<00:37:49.110> bit<00:37:49.260> but<00:37:49.650> maybe<00:37:49.890> users<00:37:50.400> and<00:37:50.730> users<00:37:51.060> behavior 00:37:51.410 --> 00:37:51.420 align:start position:0% a bit but maybe users and users behavior 00:37:51.420 --> 00:37:54.380 align:start position:0% a bit but maybe users and users behavior and<00:37:51.870> it<00:37:52.020> goes<00:37:52.410> back<00:37:52.710> to<00:37:52.950> privacy<00:37:53.580> and<00:37:53.760> Trust 00:37:54.380 --> 00:37:54.390 align:start position:0% and it goes back to privacy and Trust 00:37:54.390 --> 00:37:57.050 align:start position:0% and it goes back to privacy and Trust and<00:37:54.780> like<00:37:55.470> the<00:37:55.950> new<00:37:56.070> responsibilities<00:37:56.880> of 00:37:57.050 --> 00:37:57.060 align:start position:0% and like the new responsibilities of 00:37:57.060 --> 00:37:58.520 align:start position:0% and like the new responsibilities of users<00:37:57.390> as<00:37:57.630> well<00:37:57.780> because<00:37:58.140> if<00:37:58.260> it<00:37:58.350> looks 00:37:58.520 --> 00:37:58.530 align:start position:0% users as well because if it looks 00:37:58.530 --> 00:38:00.890 align:start position:0% users as well because if it looks statistics<00:37:59.130> how<00:37:59.550> many<00:37:59.760> people<00:38:00.180> actually<00:38:00.450> keep 00:38:00.890 --> 00:38:00.900 align:start position:0% statistics how many people actually keep 00:38:00.900 --> 00:38:03.230 align:start position:0% statistics how many people actually keep private<00:38:01.140> keys<00:38:01.560> themselves<00:38:02.400> and<00:38:02.820> how<00:38:03.000> many 00:38:03.230 --> 00:38:03.240 align:start position:0% private keys themselves and how many 00:38:03.240 --> 00:38:06.470 align:start position:0% private keys themselves and how many people<00:38:03.630> trust<00:38:04.440> exchanges<00:38:05.130> with<00:38:05.340> it<00:38:05.520> it's<00:38:06.150> kind 00:38:06.470 --> 00:38:06.480 align:start position:0% people trust exchanges with it it's kind 00:38:06.480 --> 00:38:09.260 align:start position:0% people trust exchanges with it it's kind of<00:38:06.600> worrying<00:38:06.990> to<00:38:07.770> think<00:38:08.100> what<00:38:08.370> I<00:38:08.610> don't<00:38:09.210> think 00:38:09.260 --> 00:38:09.270 align:start position:0% of worrying to think what I don't think 00:38:09.270 --> 00:38:12.620 align:start position:0% of worrying to think what I don't think we<00:38:09.840> can<00:38:10.050> think<00:38:10.260> that<00:38:10.410> these<00:38:10.710> people<00:38:10.970> will<00:38:11.970> take 00:38:12.620 --> 00:38:12.630 align:start position:0% we can think that these people will take 00:38:12.630 --> 00:38:18.160 align:start position:0% we can think that these people will take responsibility<00:38:13.620> for<00:38:13.650> privacy 00:38:18.160 --> 00:38:18.170 align:start position:0% 00:38:18.170 --> 00:38:22.490 align:start position:0% yeah<00:38:19.170> if<00:38:20.210> if<00:38:21.210> we<00:38:21.300> all<00:38:21.420> view<00:38:21.540> data<00:38:22.020> as<00:38:22.470> a 00:38:22.490 --> 00:38:22.500 align:start position:0% yeah if if we all view data as a 00:38:22.500 --> 00:38:25.640 align:start position:0% yeah if if we all view data as a liability<00:38:23.280> then<00:38:24.060> exchanges<00:38:24.990> are<00:38:25.140> effectively 00:38:25.640 --> 00:38:25.650 align:start position:0% liability then exchanges are effectively 00:38:25.650 --> 00:38:28.760 align:start position:0% liability then exchanges are effectively like<00:38:26.150> centralized<00:38:27.150> channels<00:38:27.630> are<00:38:28.109> legally 00:38:28.760 --> 00:38:28.770 align:start position:0% like centralized channels are legally 00:38:28.770 --> 00:38:32.450 align:start position:0% like centralized channels are legally mandated<00:38:29.089> nuclear-waste<00:38:30.089> ups<00:38:30.480> the<00:38:31.290> like<00:38:31.500> they 00:38:32.450 --> 00:38:32.460 align:start position:0% mandated nuclear-waste ups the like they 00:38:32.460 --> 00:38:36.500 align:start position:0% mandated nuclear-waste ups the like they they're<00:38:33.270> worth<00:38:34.430> everyone's<00:38:35.430> data<00:38:35.790> that<00:38:36.210> goes 00:38:36.500 --> 00:38:36.510 align:start position:0% they're worth everyone's data that goes 00:38:36.510 --> 00:38:39.440 align:start position:0% they're worth everyone's data that goes and<00:38:37.140> they're<00:38:37.829> legally<00:38:38.310> required<00:38:38.730> to<00:38:39.030> write 00:38:39.440 --> 00:38:39.450 align:start position:0% and they're legally required to write 00:38:39.450 --> 00:38:42.200 align:start position:0% and they're legally required to write like<00:38:39.720> and<00:38:39.900> I<00:38:39.960> don't<00:38:40.260> see<00:38:40.560> that<00:38:40.589> changing<00:38:41.119> to<00:38:42.119> be 00:38:42.200 --> 00:38:42.210 align:start position:0% like and I don't see that changing to be 00:38:42.210 --> 00:38:48.349 align:start position:0% like and I don't see that changing to be honest<00:38:43.130> so<00:38:44.130> I<00:38:44.160> my<00:38:45.349> preferred<00:38:46.849> outcome<00:38:47.849> that<00:38:48.300> I 00:38:48.349 --> 00:38:48.359 align:start position:0% honest so I my preferred outcome that I 00:38:48.359 --> 00:38:49.700 align:start position:0% honest so I my preferred outcome that I don't<00:38:48.599> think<00:38:48.750> it's<00:38:48.869> actually<00:38:49.200> likely<00:38:49.380> to<00:38:49.560> be 00:38:49.700 --> 00:38:49.710 align:start position:0% don't think it's actually likely to be 00:38:49.710 --> 00:38:51.920 align:start position:0% don't think it's actually likely to be honest<00:38:50.069> is<00:38:50.280> that<00:38:50.550> at<00:38:51.359> least<00:38:51.450> Senate<00:38:51.780> not 00:38:51.920 --> 00:38:51.930 align:start position:0% honest is that at least Senate not 00:38:51.930 --> 00:38:55.099 align:start position:0% honest is that at least Senate not assume<00:38:52.520> is<00:38:53.520> that<00:38:53.760> people<00:38:54.089> figure<00:38:54.329> out<00:38:54.420> other 00:38:55.099 --> 00:38:55.109 align:start position:0% assume is that people figure out other 00:38:55.109 --> 00:38:58.160 align:start position:0% assume is that people figure out other ways<00:38:55.290> to<00:38:56.010> exchange<00:38:56.970> against<00:38:57.569> these<00:38:57.810> systems 00:38:58.160 --> 00:38:58.170 align:start position:0% ways to exchange against these systems 00:38:58.170 --> 00:38:59.890 align:start position:0% ways to exchange against these systems that<00:38:58.349> do<00:38:58.589> actually<00:38:58.950> preserve<00:38:59.250> privacy 00:38:59.890 --> 00:38:59.900 align:start position:0% that do actually preserve privacy 00:38:59.900 --> 00:39:03.710 align:start position:0% that do actually preserve privacy without<00:39:00.900> having<00:39:01.410> to<00:39:01.589> go<00:39:01.770> through<00:39:01.800> the<00:39:02.720> nuclear 00:39:03.710 --> 00:39:03.720 align:start position:0% without having to go through the nuclear 00:39:03.720 --> 00:39:14.630 align:start position:0% without having to go through the nuclear waste<00:39:03.930> stuff<00:39:07.010> any<00:39:08.010> other<00:39:08.220> questions<00:39:10.220> like 00:39:14.630 --> 00:39:14.640 align:start position:0% 00:39:14.640 --> 00:39:19.950 align:start position:0% yeah<00:39:15.640> questions<00:39:16.510> I<00:39:16.570> guess<00:39:16.750> in<00:39:17.530> terms<00:39:17.740> of<00:39:18.960> the 00:39:19.950 --> 00:39:19.960 align:start position:0% yeah questions I guess in terms of the 00:39:19.960 --> 00:39:21.360 align:start position:0% yeah questions I guess in terms of the pattern<00:39:20.350> of<00:39:20.590> saying<00:39:20.710> I<00:39:20.830> see<00:39:20.890> repeat<00:39:21.250> in 00:39:21.360 --> 00:39:21.370 align:start position:0% pattern of saying I see repeat in 00:39:21.370 --> 00:39:23.700 align:start position:0% pattern of saying I see repeat in America<00:39:21.790> but<00:39:22.210> our<00:39:22.570> neck<00:39:22.720> the<00:39:22.930> most<00:39:23.140> users<00:39:23.470> are 00:39:23.700 --> 00:39:23.710 align:start position:0% America but our neck the most users are 00:39:23.710 --> 00:39:25.740 align:start position:0% America but our neck the most users are or<00:39:23.950> will<00:39:24.220> be<00:39:24.340> in<00:39:24.370> the<00:39:24.700> most<00:39:25.060> in<00:39:25.210> Asia<00:39:25.390> China 00:39:25.740 --> 00:39:25.750 align:start position:0% or will be in the most in Asia China 00:39:25.750 --> 00:39:28.110 align:start position:0% or will be in the most in Asia China independent<00:39:26.560> of<00:39:27.070> what<00:39:27.370> does<00:39:27.490> your<00:39:27.610> experience 00:39:28.110 --> 00:39:28.120 align:start position:0% independent of what does your experience 00:39:28.120 --> 00:39:29.610 align:start position:0% independent of what does your experience which<00:39:28.720> in<00:39:28.840> that<00:39:28.990> sense<00:39:29.260> is<00:39:29.350> there<00:39:29.440> anything 00:39:29.610 --> 00:39:29.620 align:start position:0% which in that sense is there anything 00:39:29.620 --> 00:39:32.940 align:start position:0% which in that sense is there anything like<00:39:29.890> we<00:39:30.640> can<00:39:30.790> see<00:39:30.940> if<00:39:31.090> there's<00:39:32.020> developments 00:39:32.940 --> 00:39:32.950 align:start position:0% like we can see if there's developments 00:39:32.950 --> 00:39:37.470 align:start position:0% like we can see if there's developments there<00:39:33.130> or<00:39:33.430> or<00:39:33.810> or<00:39:34.810> certain<00:39:35.140> thing<00:39:35.230> about<00:39:35.440> me<00:39:36.480> so 00:39:37.470 --> 00:39:37.480 align:start position:0% there or or or certain thing about me so 00:39:37.480 --> 00:39:40.740 align:start position:0% there or or or certain thing about me so I<00:39:37.990> have<00:39:38.590> last<00:39:39.220> month<00:39:39.550> I<00:39:39.700> was<00:39:39.850> in<00:39:39.910> Tokyo<00:39:40.240> on<00:39:40.720> a 00:39:40.740 --> 00:39:40.750 align:start position:0% I have last month I was in Tokyo on a 00:39:40.750 --> 00:39:43.380 align:start position:0% I have last month I was in Tokyo on a panel<00:39:41.260> with<00:39:41.290> some<00:39:41.800> people<00:39:41.980> from<00:39:42.240> campus<00:39:43.240> a 00:39:43.380 --> 00:39:43.390 align:start position:0% panel with some people from campus a 00:39:43.390 --> 00:39:46.140 align:start position:0% panel with some people from campus a which<00:39:43.660> is<00:39:43.840> the<00:39:44.110> Japanese<00:39:44.950> financial<00:39:45.730> services 00:39:46.140 --> 00:39:46.150 align:start position:0% which is the Japanese financial services 00:39:46.150 --> 00:39:48.000 align:start position:0% which is the Japanese financial services administration<00:39:46.720> I<00:39:46.900> believe<00:39:47.200> and<00:39:47.860> they 00:39:48.000 --> 00:39:48.010 align:start position:0% administration I believe and they 00:39:48.010 --> 00:39:50.970 align:start position:0% administration I believe and they regulate<00:39:48.490> cryptocurrency<00:39:49.330> and<00:39:49.630> that<00:39:50.050> -<00:39:50.560> in 00:39:50.970 --> 00:39:50.980 align:start position:0% regulate cryptocurrency and that - in 00:39:50.980 --> 00:39:53.820 align:start position:0% regulate cryptocurrency and that - in Japan<00:39:51.400> and<00:39:51.850> that<00:39:52.240> was<00:39:52.540> actually<00:39:52.900> interesting 00:39:53.820 --> 00:39:53.830 align:start position:0% Japan and that was actually interesting 00:39:53.830 --> 00:39:56.520 align:start position:0% Japan and that was actually interesting because<00:39:54.100> there<00:39:55.000> was<00:39:55.120> an<00:39:55.240> appreciation<00:39:55.420> of<00:39:55.990> the 00:39:56.520 --> 00:39:56.530 align:start position:0% because there was an appreciation of the 00:39:56.530 --> 00:39:58.110 align:start position:0% because there was an appreciation of the privacy<00:39:57.040> wasn't<00:39:57.400> English<00:39:57.670> should<00:39:57.760> be<00:39:57.910> aware 00:39:58.110 --> 00:39:58.120 align:start position:0% privacy wasn't English should be aware 00:39:58.120 --> 00:40:00.840 align:start position:0% privacy wasn't English should be aware of<00:39:58.440> they<00:39:59.440> wanted<00:39:59.800> to<00:39:59.890> do<00:40:00.010> all<00:40:00.130> of<00:40:00.280> its<00:40:00.550> first 00:40:00.840 --> 00:40:00.850 align:start position:0% of they wanted to do all of its first 00:40:00.850 --> 00:40:02.010 align:start position:0% of they wanted to do all of its first but<00:40:01.090> that<00:40:01.150> actually<00:40:01.450> wasn't<00:40:01.600> think<00:40:01.840> they<00:40:01.930> were 00:40:02.010 --> 00:40:02.020 align:start position:0% but that actually wasn't think they were 00:40:02.020 --> 00:40:03.600 align:start position:0% but that actually wasn't think they were concerned<00:40:02.380> about<00:40:02.500> they<00:40:02.800> acknowledged<00:40:03.310> that 00:40:03.600 --> 00:40:03.610 align:start position:0% concerned about they acknowledged that 00:40:03.610 --> 00:40:05.880 align:start position:0% concerned about they acknowledged that needed<00:40:04.450> genuinely<00:40:05.020> to<00:40:05.170> have<00:40:05.290> privacy<00:40:05.650> of 00:40:05.880 --> 00:40:05.890 align:start position:0% needed genuinely to have privacy of 00:40:05.890 --> 00:40:08.010 align:start position:0% needed genuinely to have privacy of these<00:40:05.980> things<00:40:06.450> they're<00:40:07.450> really<00:40:07.480> interested 00:40:08.010 --> 00:40:08.020 align:start position:0% these things they're really interested 00:40:08.020 --> 00:40:09.240 align:start position:0% these things they're really interested in<00:40:08.110> male<00:40:08.380> is<00:40:08.650> that<00:40:08.830> the<00:40:08.920> regulatory 00:40:09.240 --> 00:40:09.250 align:start position:0% in male is that the regulatory 00:40:09.250 --> 00:40:10.650 align:start position:0% in male is that the regulatory environment 00:40:10.650 --> 00:40:10.660 align:start position:0% environment 00:40:10.660 --> 00:40:12.690 align:start position:0% environment janma<00:40:11.380> say<00:40:11.650> is<00:40:11.770> responsible<00:40:11.920> both<00:40:12.520> for 00:40:12.690 --> 00:40:12.700 align:start position:0% janma say is responsible both for 00:40:12.700 --> 00:40:15.150 align:start position:0% janma say is responsible both for consumer<00:40:13.240> protection<00:40:13.720> and<00:40:13.810> privacy<00:40:13.990> and<00:40:14.560> for 00:40:15.150 --> 00:40:15.160 align:start position:0% consumer protection and privacy and for 00:40:15.160 --> 00:40:16.860 align:start position:0% consumer protection and privacy and for enforcing<00:40:15.520> like<00:40:15.730> act<00:40:15.970> money<00:40:16.210> water<00:40:16.450> and<00:40:16.660> stuff 00:40:16.860 --> 00:40:16.870 align:start position:0% enforcing like act money water and stuff 00:40:16.870 --> 00:40:19.140 align:start position:0% enforcing like act money water and stuff versus<00:40:17.230> in<00:40:17.320> the<00:40:17.410> u.s.<00:40:17.680> the<00:40:18.430> guys<00:40:18.640> who<00:40:18.970> you 00:40:19.140 --> 00:40:19.150 align:start position:0% versus in the u.s. the guys who you 00:40:19.150 --> 00:40:21.750 align:start position:0% versus in the u.s. the guys who you money<00:40:20.020> laundering<00:40:20.440> is<00:40:20.710> Treasury<00:40:21.370> Department 00:40:21.750 --> 00:40:21.760 align:start position:0% money laundering is Treasury Department 00:40:21.760 --> 00:40:23.520 align:start position:0% money laundering is Treasury Department Vinson<00:40:22.240> and<00:40:22.870> when<00:40:22.990> you<00:40:23.050> talk<00:40:23.230> to<00:40:23.350> them<00:40:23.470> about 00:40:23.520 --> 00:40:23.530 align:start position:0% Vinson and when you talk to them about 00:40:23.530 --> 00:40:26.490 align:start position:0% Vinson and when you talk to them about privacy<00:40:24.070> they<00:40:24.340> basically<00:40:24.670> go<00:40:24.970> yeah<00:40:25.960> you<00:40:26.110> sound 00:40:26.490 --> 00:40:26.500 align:start position:0% privacy they basically go yeah you sound 00:40:26.500 --> 00:40:28.590 align:start position:0% privacy they basically go yeah you sound right<00:40:26.710> but<00:40:26.890> that's<00:40:27.100> not<00:40:27.310> our<00:40:27.340> problem<00:40:27.460> so<00:40:28.180> why 00:40:28.590 --> 00:40:28.600 align:start position:0% right but that's not our problem so why 00:40:28.600 --> 00:40:30.000 align:start position:0% right but that's not our problem so why are<00:40:28.660> you<00:40:28.840> getting<00:40:29.080> our<00:40:29.170> way<00:40:29.410> so<00:40:29.680> I<00:40:29.710> think<00:40:29.830> there 00:40:30.000 --> 00:40:30.010 align:start position:0% are you getting our way so I think there 00:40:30.010 --> 00:40:35.330 align:start position:0% are you getting our way so I think there may<00:40:30.160> be<00:40:30.190> some<00:40:31.770> better<00:40:32.770> hope<00:40:33.040> in<00:40:33.660> parts<00:40:34.660> of<00:40:34.900> Asia 00:40:35.330 --> 00:40:35.340 align:start position:0% may be some better hope in parts of Asia 00:40:35.340 --> 00:40:38.610 align:start position:0% may be some better hope in parts of Asia in<00:40:36.340> other<00:40:36.520> places<00:40:36.850> well<00:40:37.840> I'm<00:40:38.050> not<00:40:38.380> gonna 00:40:38.610 --> 00:40:38.620 align:start position:0% in other places well I'm not gonna 00:40:38.620 --> 00:40:41.360 align:start position:0% in other places well I'm not gonna comment<00:40:38.980> further<00:40:39.310> on<00:40:39.460> that<00:40:39.580> anybody<00:40:40.450> else<00:40:40.570> I 00:40:41.360 --> 00:40:41.370 align:start position:0% comment further on that anybody else I 00:40:41.370 --> 00:40:43.080 align:start position:0% comment further on that anybody else I mean<00:40:42.370> there's<00:40:42.490> also<00:40:42.640> going<00:40:42.820> to<00:40:42.880> be<00:40:42.970> the 00:40:43.080 --> 00:40:43.090 align:start position:0% mean there's also going to be the 00:40:43.090 --> 00:40:44.050 align:start position:0% mean there's also going to be the difference<00:40:43.420> between 00:40:44.050 --> 00:40:44.060 align:start position:0% difference between 00:40:44.060 --> 00:40:46.450 align:start position:0% difference between -<00:40:44.450> ether<00:40:44.780> companies<00:40:45.380> versus<00:40:45.740> fantasy<00:40:45.980> the 00:40:46.450 --> 00:40:46.460 align:start position:0% - ether companies versus fantasy the 00:40:46.460 --> 00:40:50.170 align:start position:0% - ether companies versus fantasy the individuals<00:40:47.330> -<00:40:48.250> right<00:40:49.250> there<00:40:49.850> any<00:40:50.030> other 00:40:50.170 --> 00:40:50.180 align:start position:0% individuals - right there any other 00:40:50.180 --> 00:40:51.550 align:start position:0% individuals - right there any other thing<00:40:50.390> that<00:40:50.600> but<00:40:50.780> even<00:40:51.080> in<00:40:51.350> the<00:40:51.440> most 00:40:51.550 --> 00:40:51.560 align:start position:0% thing that but even in the most 00:40:51.560 --> 00:40:54.280 align:start position:0% thing that but even in the most permissive<00:40:52.220> hostile<00:40:53.020> government<00:40:54.020> you<00:40:54.140> can 00:40:54.280 --> 00:40:54.290 align:start position:0% permissive hostile government you can 00:40:54.290 --> 00:40:57.190 align:start position:0% permissive hostile government you can think<00:40:54.530> of<00:40:54.970> those<00:40:55.970> governments<00:40:56.540> have<00:40:56.720> enemies 00:40:57.190 --> 00:40:57.200 align:start position:0% think of those governments have enemies 00:40:57.200 --> 00:40:59.020 align:start position:0% think of those governments have enemies leader<00:40:57.470> other<00:40:57.620> governments<00:40:58.160> they<00:40:58.760> don't<00:40:58.940> let 00:40:59.020 --> 00:40:59.030 align:start position:0% leader other governments they don't let 00:40:59.030 --> 00:41:00.220 align:start position:0% leader other governments they don't let those<00:40:59.240> other<00:40:59.480> governments<00:40:59.990> seeing 00:41:00.220 --> 00:41:00.230 align:start position:0% those other governments seeing 00:41:00.230 --> 00:41:01.600 align:start position:0% those other governments seeing everything<00:41:00.470> but<00:41:00.830> just<00:41:00.920> imagine<00:41:01.070> what<00:41:01.520> would 00:41:01.600 --> 00:41:01.610 align:start position:0% everything but just imagine what would 00:41:01.610 --> 00:41:05.680 align:start position:0% everything but just imagine what would happen<00:41:01.790> if<00:41:02.000> you<00:41:02.540> go<00:41:02.780> looking<00:41:03.140> everybody<00:41:04.690> who 00:41:05.680 --> 00:41:05.690 align:start position:0% happen if you go looking everybody who 00:41:05.690 --> 00:41:07.120 align:start position:0% happen if you go looking everybody who worked<00:41:05.900> in<00:41:06.050> the<00:41:06.170> security<00:41:06.590> service<00:41:06.860> of<00:41:06.920> a 00:41:07.120 --> 00:41:07.130 align:start position:0% worked in the security service of a 00:41:07.130 --> 00:41:10.090 align:start position:0% worked in the security service of a company<00:41:07.460> go<00:41:07.610> oh<00:41:07.990> yeah<00:41:08.990> that<00:41:09.410> guy<00:41:09.440> there<00:41:09.920> is 00:41:10.090 --> 00:41:10.100 align:start position:0% company go oh yeah that guy there is 00:41:10.100 --> 00:41:13.020 align:start position:0% company go oh yeah that guy there is having<00:41:10.430> trouble<00:41:10.730> paying<00:41:10.910> his<00:41:11.120> rent 00:41:13.020 --> 00:41:13.030 align:start position:0% having trouble paying his rent 00:41:13.030 --> 00:41:15.430 align:start position:0% having trouble paying his rent Hugh<00:41:14.030> Trevor<00:41:14.450> I<00:41:14.690> would<00:41:14.870> be<00:41:14.990> there<00:41:15.080> going<00:41:15.320> all 00:41:15.430 --> 00:41:15.440 align:start position:0% Hugh Trevor I would be there going all 00:41:15.440 --> 00:41:16.510 align:start position:0% Hugh Trevor I would be there going all over<00:41:15.470> that<00:41:15.770> they<00:41:16.040> give<00:41:16.190> us<00:41:16.310> all<00:41:16.400> the 00:41:16.510 --> 00:41:16.520 align:start position:0% over that they give us all the 00:41:16.520 --> 00:41:18.130 align:start position:0% over that they give us all the classified<00:41:16.970> documents<00:41:17.000> it<00:41:17.510> has<00:41:17.660> right<00:41:17.990> so 00:41:18.130 --> 00:41:18.140 align:start position:0% classified documents it has right so 00:41:18.140 --> 00:41:19.150 align:start position:0% classified documents it has right so there<00:41:18.260> is<00:41:18.350> an<00:41:18.440> incentive 00:41:19.150 --> 00:41:19.160 align:start position:0% there is an incentive 00:41:19.160 --> 00:41:21.850 align:start position:0% there is an incentive even<00:41:20.000> in<00:41:20.150> regimes<00:41:20.780> at<00:41:20.960> the<00:41:21.020> hospital<00:41:21.440> privacy 00:41:21.850 --> 00:41:21.860 align:start position:0% even in regimes at the hospital privacy 00:41:21.860 --> 00:41:24.670 align:start position:0% even in regimes at the hospital privacy what<00:41:22.070> these<00:41:22.250> have<00:41:22.630> security<00:41:23.630> from<00:41:24.110> other 00:41:24.670 --> 00:41:24.680 align:start position:0% what these have security from other 00:41:24.680 --> 00:41:26.200 align:start position:0% what these have security from other governments<00:41:25.280> they<00:41:25.370> don't<00:41:25.520> apply<00:41:25.700> so<00:41:26.060> it's 00:41:26.200 --> 00:41:26.210 align:start position:0% governments they don't apply so it's 00:41:26.210 --> 00:41:27.640 align:start position:0% governments they don't apply so it's kind<00:41:26.450> of<00:41:26.510> any<00:41:26.750> funny<00:41:27.050> to<00:41:27.200> see<00:41:27.380> how<00:41:27.440> it's<00:41:27.590> been 00:41:27.640 --> 00:41:27.650 align:start position:0% kind of any funny to see how it's been 00:41:27.650 --> 00:41:36.110 align:start position:0% kind of any funny to see how it's been at<00:41:27.890> a<00:41:27.920> place<00:41:28.220> out<00:41:28.400> in<00:41:30.310> the<00:41:31.310> questions 00:41:36.110 --> 00:41:36.120 align:start position:0% 00:41:36.120 --> 00:41:40.060 align:start position:0% well<00:41:36.480> then<00:41:36.600> I'm<00:41:36.750> gonna<00:41:36.990> ask<00:41:37.170> a<00:41:37.380> fun<00:41:37.590> question 00:41:40.060 --> 00:41:40.070 align:start position:0% 00:41:40.070 --> 00:41:48.050 align:start position:0% all<00:41:41.070> right<00:41:41.280> so<00:41:42.830> so<00:41:43.830> if<00:41:44.130> you<00:41:44.370> could<00:41:44.670> so<00:41:45.180> we<00:41:47.060> like 00:41:48.050 --> 00:41:48.060 align:start position:0% all right so so if you could so we like 00:41:48.060 --> 00:41:51.830 align:start position:0% all right so so if you could so we like before<00:41:48.390> the<00:41:48.570> internet<00:41:50.000> do<00:41:51.000> or<00:41:51.210> have<00:41:51.390> some<00:41:51.570> idea 00:41:51.830 --> 00:41:51.840 align:start position:0% before the internet do or have some idea 00:41:51.840 --> 00:41:53.480 align:start position:0% before the internet do or have some idea of<00:41:52.140> what<00:41:52.680> life<00:41:52.800> was<00:41:52.980> like<00:41:53.040> before<00:41:53.190> the 00:41:53.480 --> 00:41:53.490 align:start position:0% of what life was like before the 00:41:53.490 --> 00:41:53.930 align:start position:0% of what life was like before the Internet 00:41:53.930 --> 00:41:53.940 align:start position:0% Internet 00:41:53.940 --> 00:41:56.300 align:start position:0% Internet here<00:41:54.120> we<00:41:54.270> go<00:41:54.390> again<00:41:54.660> load<00:41:55.050> three<00:41:55.380> what<00:41:56.100> is 00:41:56.300 --> 00:41:56.310 align:start position:0% here we go again load three what is 00:41:56.310 --> 00:41:59.480 align:start position:0% here we go again load three what is looks<00:41:57.150> like<00:41:57.300> maybe<00:41:58.020> think<00:41:58.740> about<00:41:58.800> what<00:41:59.310> would 00:41:59.480 --> 00:41:59.490 align:start position:0% looks like maybe think about what would 00:41:59.490 --> 00:42:03.440 align:start position:0% looks like maybe think about what would be<00:41:59.670> your<00:42:00.290> coolest<00:42:01.290> training<00:42:02.040> for<00:42:02.550> three 00:42:03.440 --> 00:42:03.450 align:start position:0% be your coolest training for three 00:42:03.450 --> 00:42:05.180 align:start position:0% be your coolest training for three outcomes<00:42:03.990> and<00:42:04.350> what's<00:42:04.560> life<00:42:04.740> gonna<00:42:04.980> be<00:42:05.070> like 00:42:05.180 --> 00:42:05.190 align:start position:0% outcomes and what's life gonna be like 00:42:05.190 --> 00:42:09.620 align:start position:0% outcomes and what's life gonna be like if<00:42:06.030> everything<00:42:06.450> works<00:42:06.660> out<00:42:06.810> as<00:42:06.990> we<00:42:07.110> want<00:42:08.630> for 00:42:09.620 --> 00:42:09.630 align:start position:0% if everything works out as we want for 00:42:09.630 --> 00:42:11.510 align:start position:0% if everything works out as we want for some<00:42:10.170> aspect<00:42:10.650> of<00:42:10.770> that<00:42:10.830> I<00:42:10.980> just<00:42:11.040> think<00:42:11.250> in<00:42:11.490> the 00:42:11.510 --> 00:42:11.520 align:start position:0% some aspect of that I just think in the 00:42:11.520 --> 00:42:13.460 align:start position:0% some aspect of that I just think in the future<00:42:11.670> you're<00:42:12.450> gonna<00:42:12.570> do<00:42:12.720> or<00:42:12.870> the<00:42:12.960> opposite 00:42:13.460 --> 00:42:13.470 align:start position:0% future you're gonna do or the opposite 00:42:13.470 --> 00:42:15.110 align:start position:0% future you're gonna do or the opposite like<00:42:13.740> what<00:42:13.950> was<00:42:14.070> it<00:42:14.190> like<00:42:14.310> back<00:42:14.610> in<00:42:14.820> the<00:42:14.940> end 00:42:15.110 --> 00:42:15.120 align:start position:0% like what was it like back in the end 00:42:15.120 --> 00:42:17.210 align:start position:0% like what was it like back in the end before<00:42:15.360> we<00:42:15.660> like<00:42:15.840> you<00:42:16.050> know<00:42:16.170> you're<00:42:16.860> the 00:42:17.210 --> 00:42:17.220 align:start position:0% before we like you know you're the 00:42:17.220 --> 00:42:18.890 align:start position:0% before we like you know you're the person<00:42:17.400> who<00:42:17.700> I<00:42:17.730> date<00:42:18.030> with<00:42:18.270> to<00:42:18.450> find<00:42:18.690> out<00:42:18.810> that 00:42:18.890 --> 00:42:18.900 align:start position:0% person who I date with to find out that 00:42:18.900 --> 00:42:20.420 align:start position:0% person who I date with to find out that we<00:42:19.050> did<00:42:19.200> you<00:42:19.320> everywhere<00:42:19.950> you've<00:42:20.130> been<00:42:20.160> and 00:42:20.420 --> 00:42:20.430 align:start position:0% we did you everywhere you've been and 00:42:20.430 --> 00:42:22.280 align:start position:0% we did you everywhere you've been and everything<00:42:20.580> you<00:42:20.820> Bob<00:42:21.030> just<00:42:21.300> googled<00:42:21.810> address 00:42:22.280 --> 00:42:22.290 align:start position:0% everything you Bob just googled address 00:42:22.290 --> 00:42:27.800 align:start position:0% everything you Bob just googled address right<00:42:25.190> yeah<00:42:26.190> it's<00:42:26.580> some<00:42:26.820> poll<00:42:27.060> but<00:42:27.240> I<00:42:27.390> just 00:42:27.800 --> 00:42:27.810 align:start position:0% right yeah it's some poll but I just 00:42:27.810 --> 00:42:31.520 align:start position:0% right yeah it's some poll but I just hope<00:42:28.200> that<00:42:28.560> this<00:42:28.950> could<00:42:29.310> be<00:42:29.520> like<00:42:30.530> like 00:42:31.520 --> 00:42:31.530 align:start position:0% hope that this could be like like 00:42:31.530 --> 00:42:34.760 align:start position:0% hope that this could be like like computing<00:42:32.460> infrastructure<00:42:33.150> as<00:42:33.770> powerful 00:42:34.760 --> 00:42:34.770 align:start position:0% computing infrastructure as powerful 00:42:34.770 --> 00:42:37.580 align:start position:0% computing infrastructure as powerful with<00:42:35.250> better<00:42:35.580> privacy<00:42:36.210> with<00:42:36.630> less<00:42:36.900> dependency 00:42:37.580 --> 00:42:37.590 align:start position:0% with better privacy with less dependency 00:42:37.590 --> 00:42:39.770 align:start position:0% with better privacy with less dependency because<00:42:38.310> as<00:42:38.610> it<00:42:38.760> turns<00:42:38.970> out<00:42:39.120> information 00:42:39.770 --> 00:42:39.780 align:start position:0% because as it turns out information 00:42:39.780 --> 00:42:42.620 align:start position:0% because as it turns out information technologies<00:42:40.500> like<00:42:40.740> a<00:42:40.770> key<00:42:41.100> Trier<00:42:41.630> nowadays 00:42:42.620 --> 00:42:42.630 align:start position:0% technologies like a key Trier nowadays 00:42:42.630 --> 00:42:46.340 align:start position:0% technologies like a key Trier nowadays and<00:42:42.930> that<00:42:43.800> access<00:42:44.520> and<00:42:44.780> solid<00:42:45.780> infrastructure 00:42:46.340 --> 00:42:46.350 align:start position:0% and that access and solid infrastructure 00:42:46.350 --> 00:42:47.150 align:start position:0% and that access and solid infrastructure would<00:42:46.590> be<00:42:46.650> nice 00:42:47.150 --> 00:42:47.160 align:start position:0% would be nice 00:42:47.160 --> 00:42:50.120 align:start position:0% would be nice one<00:42:47.550> more<00:42:47.880> daily<00:42:48.510> life<00:42:48.990> level<00:42:49.560> I<00:42:49.770> think 00:42:50.120 --> 00:42:50.130 align:start position:0% one more daily life level I think 00:42:50.130 --> 00:42:52.180 align:start position:0% one more daily life level I think there's<00:42:50.610> still<00:42:50.760> huge<00:42:51.090> opportunities<00:42:52.080> for 00:42:52.180 --> 00:42:52.190 align:start position:0% there's still huge opportunities for 00:42:52.190 --> 00:42:55.520 align:start position:0% there's still huge opportunities for integrating<00:42:53.190> services<00:42:53.900> reducing<00:42:54.900> vanderhoff 00:42:55.520 --> 00:42:55.530 align:start position:0% integrating services reducing vanderhoff 00:42:55.530 --> 00:42:57.320 align:start position:0% integrating services reducing vanderhoff in<00:42:55.740> all<00:42:56.340> these<00:42:56.490> kind<00:42:56.760> of<00:42:56.820> things<00:42:57.060> that<00:42:57.180> just 00:42:57.320 --> 00:42:57.330 align:start position:0% in all these kind of things that just 00:42:57.330 --> 00:42:59.900 align:start position:0% in all these kind of things that just make<00:42:57.690> your<00:42:57.870> daily<00:42:58.290> life<00:42:58.590> better<00:42:58.920> but<00:42:59.400> mail<00:42:59.640> see 00:42:59.900 --> 00:42:59.910 align:start position:0% make your daily life better but mail see 00:42:59.910 --> 00:43:00.910 align:start position:0% make your daily life better but mail see on<00:43:00.180> Spencer 00:43:00.910 --> 00:43:00.920 align:start position:0% on Spencer 00:43:00.920 --> 00:43:06.010 align:start position:0% on Spencer over<00:43:01.100> the<00:43:01.250> next<00:43:01.460> 10<00:43:01.760> years<00:43:04.540> my<00:43:05.540> biggest<00:43:05.750> hope 00:43:06.010 --> 00:43:06.020 align:start position:0% over the next 10 years my biggest hope 00:43:06.020 --> 00:43:10.060 align:start position:0% over the next 10 years my biggest hope is<00:43:06.230> that<00:43:06.830> we<00:43:07.250> learn<00:43:08.210> from<00:43:08.720> what<00:43:09.560> has<00:43:09.680> happened 00:43:10.060 --> 00:43:10.070 align:start position:0% is that we learn from what has happened 00:43:10.070 --> 00:43:12.370 align:start position:0% is that we learn from what has happened before<00:43:10.220> us<00:43:10.580> we<00:43:11.270> have<00:43:11.420> a<00:43:11.450> chance<00:43:11.810> planet<00:43:12.230> to 00:43:12.370 --> 00:43:12.380 align:start position:0% before us we have a chance planet to 00:43:12.380 --> 00:43:15.340 align:start position:0% before us we have a chance planet to before<00:43:12.830> I<00:43:12.860> do<00:43:13.070> over<00:43:13.400> to<00:43:14.090> rebuild<00:43:15.080> the 00:43:15.340 --> 00:43:15.350 align:start position:0% before I do over to rebuild the 00:43:15.350 --> 00:43:17.970 align:start position:0% before I do over to rebuild the technology<00:43:15.920> stack<00:43:16.190> that<00:43:16.460> people<00:43:16.970> rely<00:43:17.300> on<00:43:17.330> and 00:43:17.970 --> 00:43:17.980 align:start position:0% technology stack that people rely on and 00:43:17.980 --> 00:43:20.500 align:start position:0% technology stack that people rely on and we<00:43:18.980> have<00:43:19.160> a<00:43:19.190> real<00:43:19.400> opportunity<00:43:19.550> to<00:43:20.150> do<00:43:20.480> a 00:43:20.500 --> 00:43:20.510 align:start position:0% we have a real opportunity to do a 00:43:20.510 --> 00:43:23.800 align:start position:0% we have a real opportunity to do a better<00:43:20.810> job<00:43:21.100> it<00:43:22.100> is<00:43:22.370> probably<00:43:22.910> not<00:43:22.970> as<00:43:23.300> easy<00:43:23.600> as 00:43:23.800 --> 00:43:23.810 align:start position:0% better job it is probably not as easy as 00:43:23.810 --> 00:43:25.780 align:start position:0% better job it is probably not as easy as we<00:43:24.020> think<00:43:24.230> to<00:43:24.470> do<00:43:24.590> that<00:43:24.620> people<00:43:25.370> who<00:43:25.610> came 00:43:25.780 --> 00:43:25.790 align:start position:0% we think to do that people who came 00:43:25.790 --> 00:43:27.790 align:start position:0% we think to do that people who came before<00:43:26.000> us<00:43:26.240> faced<00:43:26.810> a<00:43:26.990> lot<00:43:27.110> of<00:43:27.170> trade-offs<00:43:27.470> they 00:43:27.790 --> 00:43:27.800 align:start position:0% before us faced a lot of trade-offs they 00:43:27.800 --> 00:43:29.470 align:start position:0% before us faced a lot of trade-offs they made<00:43:27.950> a<00:43:27.980> lot<00:43:28.190> of<00:43:28.220> decisions<00:43:28.400> most<00:43:29.090> of<00:43:29.300> them 00:43:29.470 --> 00:43:29.480 align:start position:0% made a lot of decisions most of them 00:43:29.480 --> 00:43:31.450 align:start position:0% made a lot of decisions most of them still<00:43:29.810> seem<00:43:30.080> like<00:43:30.290> the<00:43:30.470> decisions<00:43:30.950> in 00:43:31.450 --> 00:43:31.460 align:start position:0% still seem like the decisions in 00:43:31.460 --> 00:43:33.190 align:start position:0% still seem like the decisions in hindsight<00:43:31.880> and<00:43:32.300> yet<00:43:32.450> they<00:43:32.600> ended<00:43:32.870> up<00:43:32.960> in<00:43:33.110> a 00:43:33.190 --> 00:43:33.200 align:start position:0% hindsight and yet they ended up in a 00:43:33.200 --> 00:43:35.530 align:start position:0% hindsight and yet they ended up in a place<00:43:33.440> that<00:43:33.520> has<00:43:34.520> some<00:43:34.730> real<00:43:34.880> disadvantages 00:43:35.530 --> 00:43:35.540 align:start position:0% place that has some real disadvantages 00:43:35.540 --> 00:43:37.840 align:start position:0% place that has some real disadvantages but<00:43:35.990> I<00:43:36.050> hope<00:43:36.260> that<00:43:36.470> we<00:43:36.590> do<00:43:36.740> better<00:43:36.920> this<00:43:37.160> time 00:43:37.840 --> 00:43:37.850 align:start position:0% but I hope that we do better this time 00:43:37.850 --> 00:43:39.400 align:start position:0% but I hope that we do better this time and<00:43:37.940> I<00:43:38.330> think<00:43:38.540> one<00:43:38.720> of<00:43:38.750> the<00:43:38.840> keys<00:43:39.050> to<00:43:39.260> doing 00:43:39.400 --> 00:43:39.410 align:start position:0% and I think one of the keys to doing 00:43:39.410 --> 00:43:43.120 align:start position:0% and I think one of the keys to doing that<00:43:39.710> is<00:43:39.950> to<00:43:41.140> get<00:43:42.140> well<00:43:42.380> two<00:43:42.620> keys<00:43:42.830> to<00:43:42.860> doing 00:43:43.120 --> 00:43:43.130 align:start position:0% that is to get well two keys to doing 00:43:43.130 --> 00:43:45.580 align:start position:0% that is to get well two keys to doing that<00:43:43.370> at<00:43:43.490> first<00:43:43.700> to<00:43:44.000> really<00:43:44.810> pay<00:43:45.050> attention<00:43:45.080> to 00:43:45.580 --> 00:43:45.590 align:start position:0% that at first to really pay attention to 00:43:45.590 --> 00:43:46.990 align:start position:0% that at first to really pay attention to what<00:43:45.740> happened<00:43:46.040> before<00:43:46.400> and<00:43:46.550> learn<00:43:46.700> from<00:43:46.850> it 00:43:46.990 --> 00:43:47.000 align:start position:0% what happened before and learn from it 00:43:47.000 --> 00:43:49.690 align:start position:0% what happened before and learn from it and<00:43:47.750> to<00:43:48.080> not<00:43:48.410> to<00:43:48.620> give<00:43:48.800> ourselves<00:43:48.950> too<00:43:49.490> much 00:43:49.690 --> 00:43:49.700 align:start position:0% and to not to give ourselves too much 00:43:49.700 --> 00:43:51.850 align:start position:0% and to not to give ourselves too much credit<00:43:50.180> for<00:43:50.720> being<00:43:50.870> able<00:43:51.080> to<00:43:51.260> see<00:43:51.530> ahead<00:43:51.680> for 00:43:51.850 --> 00:43:51.860 align:start position:0% credit for being able to see ahead for 00:43:51.860 --> 00:43:54.130 align:start position:0% credit for being able to see ahead for being<00:43:52.460> more<00:43:52.640> altruistic<00:43:52.970> than<00:43:53.570> we<00:43:53.840> actually 00:43:54.130 --> 00:43:54.140 align:start position:0% being more altruistic than we actually 00:43:54.140 --> 00:43:59.440 align:start position:0% being more altruistic than we actually will<00:43:54.680> turn<00:43:54.830> out<00:43:55.010> to<00:43:55.130> be<00:43:57.520> yeah<00:43:58.520> if<00:43:58.760> I<00:43:59.120> couldn't 00:43:59.440 --> 00:43:59.450 align:start position:0% will turn out to be yeah if I couldn't 00:43:59.450 --> 00:44:03.310 align:start position:0% will turn out to be yeah if I couldn't describe<00:43:59.780> like<00:44:00.380> my<00:44:00.590> ideal<00:44:01.160> view<00:44:01.490> for<00:44:02.210> what<00:44:03.200> the 00:44:03.310 --> 00:44:03.320 align:start position:0% describe like my ideal view for what the 00:44:03.320 --> 00:44:05.950 align:start position:0% describe like my ideal view for what the end<00:44:03.470> result<00:44:03.830> of<00:44:04.130> this<00:44:04.280> movement<00:44:04.880> might<00:44:05.720> be 00:44:05.950 --> 00:44:05.960 align:start position:0% end result of this movement might be 00:44:05.960 --> 00:44:09.570 align:start position:0% end result of this movement might be like<00:44:06.440> I<00:44:06.530> actually<00:44:06.830> I<00:44:07.040> think<00:44:07.280> it'd<00:44:07.340> be<00:44:07.370> more 00:44:09.570 --> 00:44:09.580 align:start position:0% like I actually I think it'd be more 00:44:09.580 --> 00:44:12.190 align:start position:0% like I actually I think it'd be more this<00:44:10.580> in<00:44:10.700> my<00:44:10.850> in<00:44:11.120> my<00:44:11.240> day-to-day<00:44:11.450> I<00:44:11.720> would<00:44:11.990> like 00:44:12.190 --> 00:44:12.200 align:start position:0% this in my in my day-to-day I would like 00:44:12.200 --> 00:44:15.310 align:start position:0% this in my in my day-to-day I would like to<00:44:12.410> have<00:44:12.920> the<00:44:13.100> device<00:44:13.400> on<00:44:13.760> me<00:44:14.000> that<00:44:14.660> is<00:44:15.020> not 00:44:15.310 --> 00:44:15.320 align:start position:0% to have the device on me that is not 00:44:15.320 --> 00:44:17.890 align:start position:0% to have the device on me that is not tracking<00:44:15.770> me<00:44:15.920> that<00:44:16.460> when<00:44:16.610> I<00:44:16.640> go<00:44:16.940> to<00:44:16.970> buy<00:44:17.390> a<00:44:17.420> book 00:44:17.890 --> 00:44:17.900 align:start position:0% tracking me that when I go to buy a book 00:44:17.900 --> 00:44:21.160 align:start position:0% tracking me that when I go to buy a book it<00:44:18.770> doesn't<00:44:19.040> it<00:44:19.100> the<00:44:19.280> rme<00:44:19.550> on<00:44:19.760> it<00:44:19.910> I<00:44:20.150> paid<00:44:20.810> for 00:44:21.160 --> 00:44:21.170 align:start position:0% it doesn't it the rme on it I paid for 00:44:21.170 --> 00:44:23.650 align:start position:0% it doesn't it the rme on it I paid for it<00:44:21.460> without<00:44:22.460> having<00:44:22.640> to<00:44:22.820> enter<00:44:23.000> in<00:44:23.210> my<00:44:23.330> email 00:44:23.650 --> 00:44:23.660 align:start position:0% it without having to enter in my email 00:44:23.660 --> 00:44:25.420 align:start position:0% it without having to enter in my email or<00:44:23.780> user<00:44:24.080> account<00:44:24.470> and<00:44:24.740> without<00:44:25.040> anyone 00:44:25.420 --> 00:44:25.430 align:start position:0% or user account and without anyone 00:44:25.430 --> 00:44:27.900 align:start position:0% or user account and without anyone knowing<00:44:25.820> who<00:44:26.300> I<00:44:26.360> am<00:44:26.630> buying<00:44:27.110> that 00:44:27.900 --> 00:44:27.910 align:start position:0% knowing who I am buying that 00:44:27.910 --> 00:44:30.510 align:start position:0% knowing who I am buying that information<00:44:28.480> I<00:44:29.289> just<00:44:29.740> want<00:44:29.980> to<00:44:30.039> live<00:44:30.280> in<00:44:30.460> a 00:44:30.510 --> 00:44:30.520 align:start position:0% information I just want to live in a 00:44:30.520 --> 00:44:33.210 align:start position:0% information I just want to live in a world<00:44:30.760> where<00:44:31.270> it<00:44:31.869> kind<00:44:32.200> of<00:44:32.260> emulates<00:44:32.770> like 00:44:33.210 --> 00:44:33.220 align:start position:0% world where it kind of emulates like 00:44:33.220 --> 00:44:34.890 align:start position:0% world where it kind of emulates like what<00:44:33.819> it<00:44:33.910> was<00:44:34.030> like<00:44:34.210> when<00:44:34.420> you<00:44:34.539> went<00:44:34.720> into<00:44:34.869> a 00:44:34.890 --> 00:44:34.900 align:start position:0% what it was like when you went into a 00:44:34.900 --> 00:44:42.240 align:start position:0% what it was like when you went into a bookstore<00:44:35.140> and<00:44:40.530> they<00:44:41.530> actually<00:44:41.680> feel<00:44:42.099> like 00:44:42.240 --> 00:44:42.250 align:start position:0% bookstore and they actually feel like 00:44:42.250 --> 00:44:44.430 align:start position:0% bookstore and they actually feel like that's<00:44:42.400> a<00:44:42.520> return<00:44:42.880> to<00:44:43.180> form<00:44:43.450> and<00:44:44.109> that<00:44:44.260> we 00:44:44.430 --> 00:44:44.440 align:start position:0% that's a return to form and that we 00:44:44.440 --> 00:44:47.370 align:start position:0% that's a return to form and that we could<00:44:44.710> build<00:44:45.369> that<00:44:45.670> under<00:44:46.150> formal<00:44:46.539> gaining 00:44:47.370 --> 00:44:47.380 align:start position:0% could build that under formal gaining 00:44:47.380 --> 00:44:49.380 align:start position:0% could build that under formal gaining all<00:44:47.530> the<00:44:47.680> convenience<00:44:48.190> that<00:44:48.309> we<00:44:48.640> have<00:44:49.180> in 00:44:49.380 --> 00:44:49.390 align:start position:0% all the convenience that we have in 00:44:49.390 --> 00:44:51.000 align:start position:0% all the convenience that we have in today's<00:44:49.569> society<00:44:49.900> so<00:44:50.500> you're<00:44:50.680> saying<00:44:50.890> you 00:44:51.000 --> 00:44:51.010 align:start position:0% today's society so you're saying you 00:44:51.010 --> 00:44:53.039 align:start position:0% today's society so you're saying you want<00:44:51.160> to<00:44:51.400> look<00:44:51.549> like<00:44:51.780> you're<00:44:52.780> saying<00:44:52.960> you 00:44:53.039 --> 00:44:53.049 align:start position:0% want to look like you're saying you 00:44:53.049 --> 00:44:54.240 align:start position:0% want to look like you're saying you wanted<00:44:53.289> to<00:44:53.349> look<00:44:53.470> like<00:44:53.650> what<00:44:53.829> it<00:44:53.920> was<00:44:54.039> before 00:44:54.240 --> 00:44:54.250 align:start position:0% wanted to look like what it was before 00:44:54.250 --> 00:45:00.180 align:start position:0% wanted to look like what it was before they<00:44:54.579> lost<00:44:54.789> the<00:44:54.910> other<00:44:55.059> half<00:44:58.740> so<00:44:59.740> we<00:44:59.890> want<00:45:00.069> the 00:45:00.180 --> 00:45:00.190 align:start position:0% they lost the other half so we want the 00:45:00.190 --> 00:45:02.309 align:start position:0% they lost the other half so we want the mobile<00:45:00.520> device<00:45:00.789> in<00:45:00.970> our<00:45:01.089> pocket<00:45:01.480> that's<00:45:01.690> not 00:45:02.309 --> 00:45:02.319 align:start position:0% mobile device in our pocket that's not 00:45:02.319 --> 00:45:04.109 align:start position:0% mobile device in our pocket that's not acting<00:45:02.799> like<00:45:02.829> the<00:45:02.980> mobile<00:45:03.220> device<00:45:03.609> trapping 00:45:04.109 --> 00:45:04.119 align:start position:0% acting like the mobile device trapping 00:45:04.119 --> 00:45:06.000 align:start position:0% acting like the mobile device trapping us<00:45:04.240> in<00:45:04.270> a<00:45:04.420> pocket<00:45:04.750> that<00:45:04.780> we<00:45:04.930> separate<00:45:05.230> out<00:45:05.410> and 00:45:06.000 --> 00:45:06.010 align:start position:0% us in a pocket that we separate out and 00:45:06.010 --> 00:45:07.620 align:start position:0% us in a pocket that we separate out and we<00:45:06.190> once<00:45:06.400> have<00:45:06.579> been<00:45:06.640> with<00:45:06.880> a<00:45:06.910> cache<00:45:07.150> but 00:45:07.620 --> 00:45:07.630 align:start position:0% we once have been with a cache but 00:45:07.630 --> 00:45:13.589 align:start position:0% we once have been with a cache but that's<00:45:07.839> digital<00:45:08.049> all<00:45:11.579> right<00:45:12.579> and<00:45:13.000> here's<00:45:13.450> our 00:45:13.589 --> 00:45:13.599 align:start position:0% that's digital all right and here's our 00:45:13.599 --> 00:45:29.740 align:start position:0% that's digital all right and here's our last<00:45:13.930> comment<00:45:15.210> that<00:45:17.190> 617<00:45:18.190> seconds<00:45:18.990> over<00:45:19.990> time 00:45:29.740 --> 00:45:29.750 align:start position:0% 00:45:29.750 --> 00:45:37.150 align:start position:0% [Applause]