WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:16.390 align:start position:0% [Music] 00:00:16.390 --> 00:00:16.400 align:start position:0% 00:00:16.400 --> 00:00:18.529 align:start position:0% thank<00:00:17.400> you<00:00:17.520> for<00:00:17.640> starting<00:00:17.820> the<00:00:18.060> morning<00:00:18.240> with 00:00:18.529 --> 00:00:18.539 align:start position:0% thank you for starting the morning with 00:00:18.539 --> 00:00:21.290 align:start position:0% thank you for starting the morning with us<00:00:18.720> I'm<00:00:19.380> here<00:00:19.560> to<00:00:19.680> introduce<00:00:20.039> Andrew<00:00:20.460> millik 00:00:21.290 --> 00:00:21.300 align:start position:0% us I'm here to introduce Andrew millik 00:00:21.300 --> 00:00:24.050 align:start position:0% us I'm here to introduce Andrew millik he's<00:00:21.720> the<00:00:21.900> co-founder<00:00:22.320> and<00:00:22.560> CEO<00:00:22.859> of<00:00:22.980> skiff 00:00:24.050 --> 00:00:24.060 align:start position:0% he's the co-founder and CEO of skiff 00:00:24.060 --> 00:00:26.150 align:start position:0% he's the co-founder and CEO of skiff which<00:00:24.480> is<00:00:24.600> an<00:00:24.779> end-to-end<00:00:25.260> encrypted<00:00:25.740> privacy 00:00:26.150 --> 00:00:26.160 align:start position:0% which is an end-to-end encrypted privacy 00:00:26.160 --> 00:00:28.550 align:start position:0% which is an end-to-end encrypted privacy first<00:00:26.519> wallet<00:00:27.300> native<00:00:27.539> communication<00:00:28.140> and 00:00:28.550 --> 00:00:28.560 align:start position:0% first wallet native communication and 00:00:28.560 --> 00:00:31.009 align:start position:0% first wallet native communication and collaboration<00:00:29.039> platform<00:00:29.580> Andrew<00:00:30.359> previously 00:00:31.009 --> 00:00:31.019 align:start position:0% collaboration platform Andrew previously 00:00:31.019 --> 00:00:33.290 align:start position:0% collaboration platform Andrew previously worked<00:00:31.320> on<00:00:31.439> spacecraft<00:00:31.980> at<00:00:32.460> eight<00:00:32.640> SpaceX 00:00:33.290 --> 00:00:33.300 align:start position:0% worked on spacecraft at eight SpaceX 00:00:33.300 --> 00:00:36.049 align:start position:0% worked on spacecraft at eight SpaceX operating<00:00:34.200> systems<00:00:34.860> and<00:00:35.219> spend<00:00:35.520> time<00:00:35.700> working 00:00:36.049 --> 00:00:36.059 align:start position:0% operating systems and spend time working 00:00:36.059 --> 00:00:38.750 align:start position:0% operating systems and spend time working all<00:00:36.360> over<00:00:36.540> Asia<00:00:37.020> and<00:00:37.260> Eastern<00:00:37.620> Europe<00:00:37.800> before 00:00:38.750 --> 00:00:38.760 align:start position:0% all over Asia and Eastern Europe before 00:00:38.760 --> 00:00:41.150 align:start position:0% all over Asia and Eastern Europe before that<00:00:39.059> Andrew<00:00:39.480> graduated<00:00:40.079> as<00:00:40.379> the<00:00:40.559> Henry<00:00:40.920> Ford 00:00:41.150 --> 00:00:41.160 align:start position:0% that Andrew graduated as the Henry Ford 00:00:41.160 --> 00:00:44.510 align:start position:0% that Andrew graduated as the Henry Ford the<00:00:42.059> second<00:00:42.180> scholar<00:00:42.660> from<00:00:43.079> Stanford<00:00:43.980> welcome 00:00:44.510 --> 00:00:44.520 align:start position:0% the second scholar from Stanford welcome 00:00:44.520 --> 00:00:46.729 align:start position:0% the second scholar from Stanford welcome Ender<00:00:45.059> thank<00:00:45.540> you<00:00:45.660> so<00:00:45.840> much<00:00:45.960> and<00:00:46.440> hi<00:00:46.559> everyone 00:00:46.729 --> 00:00:46.739 align:start position:0% Ender thank you so much and hi everyone 00:00:46.739 --> 00:00:50.270 align:start position:0% Ender thank you so much and hi everyone nice<00:00:47.160> to<00:00:47.280> meet<00:00:47.399> you<00:00:47.940> I've<00:00:48.600> got<00:00:48.840> a 00:00:50.270 --> 00:00:50.280 align:start position:0% nice to meet you I've got a 00:00:50.280 --> 00:00:51.529 align:start position:0% nice to meet you I've got a great<00:00:50.700> group 00:00:51.529 --> 00:00:51.539 align:start position:0% great group 00:00:51.539 --> 00:00:53.330 align:start position:0% great group so<00:00:51.960> yeah<00:00:52.140> we're<00:00:52.559> going<00:00:52.680> to<00:00:52.800> start<00:00:52.920> by<00:00:53.100> talking 00:00:53.330 --> 00:00:53.340 align:start position:0% so yeah we're going to start by talking 00:00:53.340 --> 00:00:55.430 align:start position:0% so yeah we're going to start by talking about<00:00:53.579> basically<00:00:54.180> the<00:00:54.539> stack<00:00:54.780> of<00:00:55.020> how<00:00:55.199> you'd 00:00:55.430 --> 00:00:55.440 align:start position:0% about basically the stack of how you'd 00:00:55.440 --> 00:00:58.310 align:start position:0% about basically the stack of how you'd build<00:00:55.559> consumer<00:00:56.160> applications<00:00:56.640> in<00:00:57.360> web3<00:00:57.780> and 00:00:58.310 --> 00:00:58.320 align:start position:0% build consumer applications in web3 and 00:00:58.320 --> 00:00:59.869 align:start position:0% build consumer applications in web3 and so<00:00:58.440> what<00:00:58.620> does<00:00:58.739> that<00:00:58.860> mean<00:00:59.039> not<00:00:59.399> just<00:00:59.520> for 00:00:59.869 --> 00:00:59.879 align:start position:0% so what does that mean not just for 00:00:59.879 --> 00:01:01.850 align:start position:0% so what does that mean not just for applications<00:01:00.420> in<00:01:00.719> defy<00:01:01.199> and<00:01:01.379> finance<00:01:01.680> and 00:01:01.850 --> 00:01:01.860 align:start position:0% applications in defy and finance and 00:01:01.860 --> 00:01:03.889 align:start position:0% applications in defy and finance and trading<00:01:02.219> and<00:01:02.460> exchanges<00:01:03.000> but<00:01:03.539> how<00:01:03.660> can<00:01:03.780> we 00:01:03.889 --> 00:01:03.899 align:start position:0% trading and exchanges but how can we 00:01:03.899 --> 00:01:05.570 align:start position:0% trading and exchanges but how can we actually<00:01:04.080> build<00:01:04.320> applications<00:01:04.799> that<00:01:05.220> we<00:01:05.400> use 00:01:05.570 --> 00:01:05.580 align:start position:0% actually build applications that we use 00:01:05.580 --> 00:01:07.730 align:start position:0% actually build applications that we use every<00:01:06.000> single<00:01:06.240> day<00:01:06.420> and<00:01:07.020> ideally<00:01:07.380> every 00:01:07.730 --> 00:01:07.740 align:start position:0% every single day and ideally every 00:01:07.740 --> 00:01:09.410 align:start position:0% every single day and ideally every single<00:01:07.979> hour<00:01:08.159> so<00:01:08.520> you<00:01:08.640> wake<00:01:08.820> up<00:01:09.000> you<00:01:09.240> check 00:01:09.410 --> 00:01:09.420 align:start position:0% single hour so you wake up you check 00:01:09.420 --> 00:01:11.210 align:start position:0% single hour so you wake up you check your<00:01:09.600> email<00:01:09.720> you<00:01:09.960> check<00:01:10.140> your<00:01:10.320> messages<00:01:10.500> how 00:01:11.210 --> 00:01:11.220 align:start position:0% your email you check your messages how 00:01:11.220 --> 00:01:12.890 align:start position:0% your email you check your messages how can<00:01:11.340> we<00:01:11.460> rebuild<00:01:11.820> the<00:01:12.119> stack<00:01:12.360> of<00:01:12.659> the<00:01:12.780> way 00:01:12.890 --> 00:01:12.900 align:start position:0% can we rebuild the stack of the way 00:01:12.900 --> 00:01:14.390 align:start position:0% can we rebuild the stack of the way consumers<00:01:13.380> live<00:01:13.619> and<00:01:13.799> work<00:01:13.920> on<00:01:14.159> the<00:01:14.280> internet 00:01:14.390 --> 00:01:14.400 align:start position:0% consumers live and work on the internet 00:01:14.400 --> 00:01:16.730 align:start position:0% consumers live and work on the internet to<00:01:15.060> be<00:01:15.180> more<00:01:15.360> private<00:01:15.720> and<00:01:15.960> use<00:01:16.080> our<00:01:16.260> own<00:01:16.439> so 00:01:16.730 --> 00:01:16.740 align:start position:0% to be more private and use our own so 00:01:16.740 --> 00:01:17.690 align:start position:0% to be more private and use our own so we'll<00:01:16.860> start<00:01:16.979> with<00:01:17.159> just<00:01:17.340> some<00:01:17.520> of<00:01:17.640> the 00:01:17.690 --> 00:01:17.700 align:start position:0% we'll start with just some of the 00:01:17.700 --> 00:01:19.490 align:start position:0% we'll start with just some of the attributes<00:01:18.119> of<00:01:18.360> what<00:01:18.540> we<00:01:18.659> look<00:01:18.900> for<00:01:19.020> in<00:01:19.320> our 00:01:19.490 --> 00:01:19.500 align:start position:0% attributes of what we look for in our 00:01:19.500 --> 00:01:21.410 align:start position:0% attributes of what we look for in our application<00:01:19.860> and<00:01:20.159> also<00:01:20.460> in<00:01:20.759> all<00:01:21.000> applications 00:01:21.410 --> 00:01:21.420 align:start position:0% application and also in all applications 00:01:21.420 --> 00:01:23.929 align:start position:0% application and also in all applications in<00:01:21.780> this<00:01:22.020> sector<00:01:22.439> we'll<00:01:23.220> start<00:01:23.400> with<00:01:23.580> privacy 00:01:23.929 --> 00:01:23.939 align:start position:0% in this sector we'll start with privacy 00:01:23.939 --> 00:01:26.270 align:start position:0% in this sector we'll start with privacy first<00:01:24.180> and<00:01:25.080> this<00:01:25.200> actually<00:01:25.380> for<00:01:25.619> us<00:01:25.799> at<00:01:25.920> skiff 00:01:26.270 --> 00:01:26.280 align:start position:0% first and this actually for us at skiff 00:01:26.280 --> 00:01:27.530 align:start position:0% first and this actually for us at skiff is<00:01:26.580> probably<00:01:26.759> the<00:01:26.939> most<00:01:27.119> important 00:01:27.530 --> 00:01:27.540 align:start position:0% is probably the most important 00:01:27.540 --> 00:01:29.450 align:start position:0% is probably the most important fundamental<00:01:28.140> layer<00:01:28.500> of<00:01:28.680> how<00:01:28.860> we<00:01:28.979> build<00:01:29.159> things 00:01:29.450 --> 00:01:29.460 align:start position:0% fundamental layer of how we build things 00:01:29.460 --> 00:01:31.969 align:start position:0% fundamental layer of how we build things so<00:01:30.060> what<00:01:30.180> that<00:01:30.360> means<00:01:30.659> is<00:01:31.080> all<00:01:31.500> of<00:01:31.560> your<00:01:31.680> data 00:01:31.969 --> 00:01:31.979 align:start position:0% so what that means is all of your data 00:01:31.979 --> 00:01:33.950 align:start position:0% so what that means is all of your data is<00:01:32.159> owned<00:01:32.460> by<00:01:32.580> you<00:01:32.759> and<00:01:33.180> it's<00:01:33.299> private<00:01:33.659> to<00:01:33.840> you 00:01:33.950 --> 00:01:33.960 align:start position:0% is owned by you and it's private to you 00:01:33.960 --> 00:01:36.230 align:start position:0% is owned by you and it's private to you so<00:01:34.560> no<00:01:34.799> one<00:01:34.920> else<00:01:35.100> not<00:01:35.460> some<00:01:35.759> technology 00:01:36.230 --> 00:01:36.240 align:start position:0% so no one else not some technology 00:01:36.240 --> 00:01:38.929 align:start position:0% so no one else not some technology provider<00:01:36.840> or<00:01:37.079> platform<00:01:37.560> will<00:01:38.159> have<00:01:38.340> access<00:01:38.579> to 00:01:38.929 --> 00:01:38.939 align:start position:0% provider or platform will have access to 00:01:38.939 --> 00:01:40.429 align:start position:0% provider or platform will have access to it<00:01:39.060> and<00:01:39.360> so<00:01:39.540> it's<00:01:39.659> really<00:01:39.900> only<00:01:40.140> something 00:01:40.429 --> 00:01:40.439 align:start position:0% it and so it's really only something 00:01:40.439 --> 00:01:43.069 align:start position:0% it and so it's really only something that<00:01:41.040> you<00:01:41.820> should<00:01:41.939> have<00:01:42.060> access<00:01:42.299> to<00:01:42.600> which<00:01:42.960> is 00:01:43.069 --> 00:01:43.079 align:start position:0% that you should have access to which is 00:01:43.079 --> 00:01:44.810 align:start position:0% that you should have access to which is just<00:01:43.259> also<00:01:43.560> a<00:01:43.740> lot<00:01:43.799> more<00:01:43.979> intuitive<00:01:44.400> for<00:01:44.700> the 00:01:44.810 --> 00:01:44.820 align:start position:0% just also a lot more intuitive for the 00:01:44.820 --> 00:01:46.910 align:start position:0% just also a lot more intuitive for the way<00:01:44.939> we<00:01:45.180> use<00:01:45.420> these<00:01:46.320> really<00:01:46.380> sensitive 00:01:46.910 --> 00:01:46.920 align:start position:0% way we use these really sensitive 00:01:46.920 --> 00:01:48.649 align:start position:0% way we use these really sensitive applications<00:01:47.400> whether<00:01:47.880> it's<00:01:48.119> file<00:01:48.360> storage 00:01:48.649 --> 00:01:48.659 align:start position:0% applications whether it's file storage 00:01:48.659 --> 00:01:51.469 align:start position:0% applications whether it's file storage or<00:01:49.079> messaging<00:01:49.619> or<00:01:50.159> communication<00:01:50.700> all<00:01:51.360> the 00:01:51.469 --> 00:01:51.479 align:start position:0% or messaging or communication all the 00:01:51.479 --> 00:01:52.850 align:start position:0% or messaging or communication all the the<00:01:51.899> things<00:01:52.020> that<00:01:52.200> we<00:01:52.320> store<00:01:52.500> on<00:01:52.680> those 00:01:52.850 --> 00:01:52.860 align:start position:0% the things that we store on those 00:01:52.860 --> 00:01:54.889 align:start position:0% the things that we store on those products<00:01:53.220> should<00:01:53.520> really<00:01:53.700> only<00:01:53.939> be<00:01:54.240> known<00:01:54.659> to 00:01:54.889 --> 00:01:54.899 align:start position:0% products should really only be known to 00:01:54.899 --> 00:01:56.990 align:start position:0% products should really only be known to us<00:01:55.079> and<00:01:55.740> that's<00:01:55.920> not<00:01:56.159> an<00:01:56.280> expectation<00:01:56.700> that 00:01:56.990 --> 00:01:57.000 align:start position:0% us and that's not an expectation that 00:01:57.000 --> 00:01:59.870 align:start position:0% us and that's not an expectation that people<00:01:57.240> certainly<00:01:57.899> have<00:01:58.320> today 00:01:59.870 --> 00:01:59.880 align:start position:0% people certainly have today 00:01:59.880 --> 00:02:01.310 align:start position:0% people certainly have today beyond<00:02:00.420> that<00:02:00.540> and<00:02:00.720> we'll<00:02:00.840> talk<00:02:01.020> more<00:02:01.140> about 00:02:01.310 --> 00:02:01.320 align:start position:0% beyond that and we'll talk more about 00:02:01.320 --> 00:02:02.569 align:start position:0% beyond that and we'll talk more about this<00:02:01.439> later<00:02:01.680> we<00:02:02.100> think<00:02:02.220> it<00:02:02.340> should<00:02:02.460> be 00:02:02.569 --> 00:02:02.579 align:start position:0% this later we think it should be 00:02:02.579 --> 00:02:04.550 align:start position:0% this later we think it should be decentralized<00:02:03.299> and<00:02:03.720> what<00:02:03.840> that<00:02:03.960> means<00:02:04.200> isn't 00:02:04.550 --> 00:02:04.560 align:start position:0% decentralized and what that means isn't 00:02:04.560 --> 00:02:06.469 align:start position:0% decentralized and what that means isn't always<00:02:04.740> that<00:02:05.219> you<00:02:05.460> know<00:02:05.520> compute<00:02:06.060> is<00:02:06.180> taking 00:02:06.469 --> 00:02:06.479 align:start position:0% always that you know compute is taking 00:02:06.479 --> 00:02:10.010 align:start position:0% always that you know compute is taking place<00:02:06.780> all<00:02:07.140> across<00:02:07.560> the<00:02:07.680> world<00:02:07.920> on<00:02:08.459> chain<00:02:08.700> or 00:02:10.010 --> 00:02:10.020 align:start position:0% place all across the world on chain or 00:02:10.020 --> 00:02:12.110 align:start position:0% place all across the world on chain or um<00:02:10.080> always<00:02:10.259> on<00:02:10.560> a<00:02:10.679> decentralized<00:02:11.220> network<00:02:11.400> but 00:02:12.110 --> 00:02:12.120 align:start position:0% um always on a decentralized network but 00:02:12.120 --> 00:02:13.970 align:start position:0% um always on a decentralized network but it<00:02:12.239> should<00:02:12.360> be<00:02:12.480> architected<00:02:13.080> in<00:02:13.379> a<00:02:13.500> way<00:02:13.620> where 00:02:13.970 --> 00:02:13.980 align:start position:0% it should be architected in a way where 00:02:13.980 --> 00:02:15.710 align:start position:0% it should be architected in a way where your<00:02:14.160> data<00:02:14.520> and<00:02:14.760> your<00:02:14.940> compute<00:02:15.239> isn't<00:02:15.540> always 00:02:15.710 --> 00:02:15.720 align:start position:0% your data and your compute isn't always 00:02:15.720 --> 00:02:17.869 align:start position:0% your data and your compute isn't always entrusted<00:02:16.319> to<00:02:16.500> a<00:02:16.680> platform<00:02:16.980> and<00:02:17.700> that 00:02:17.869 --> 00:02:17.879 align:start position:0% entrusted to a platform and that 00:02:17.879 --> 00:02:19.910 align:start position:0% entrusted to a platform and that translates<00:02:18.239> into<00:02:18.480> the<00:02:18.780> data<00:02:19.080> structures<00:02:19.440> that 00:02:19.910 --> 00:02:19.920 align:start position:0% translates into the data structures that 00:02:19.920 --> 00:02:21.110 align:start position:0% translates into the data structures that you<00:02:20.040> might<00:02:20.160> use<00:02:20.459> into<00:02:20.760> the<00:02:21.000> way 00:02:21.110 --> 00:02:21.120 align:start position:0% you might use into the way 00:02:21.120 --> 00:02:22.790 align:start position:0% you might use into the way authentication<00:02:21.720> and<00:02:22.020> identity<00:02:22.379> might<00:02:22.560> work 00:02:22.790 --> 00:02:22.800 align:start position:0% authentication and identity might work 00:02:22.800 --> 00:02:25.070 align:start position:0% authentication and identity might work and<00:02:23.580> also<00:02:23.819> into<00:02:24.000> so<00:02:24.300> much<00:02:24.420> more<00:02:24.660> from<00:02:24.900> an 00:02:25.070 --> 00:02:25.080 align:start position:0% and also into so much more from an 00:02:25.080 --> 00:02:27.410 align:start position:0% and also into so much more from an ideological<00:02:25.620> side<00:02:25.920> of<00:02:26.520> how<00:02:26.700> might<00:02:26.879> your<00:02:27.120> data 00:02:27.410 --> 00:02:27.420 align:start position:0% ideological side of how might your data 00:02:27.420 --> 00:02:29.210 align:start position:0% ideological side of how might your data be<00:02:27.540> de-platformed<00:02:28.379> if<00:02:28.620> you're<00:02:28.739> removed<00:02:29.099> from 00:02:29.210 --> 00:02:29.220 align:start position:0% be de-platformed if you're removed from 00:02:29.220 --> 00:02:31.010 align:start position:0% be de-platformed if you're removed from it<00:02:29.400> how<00:02:29.940> would<00:02:30.060> you<00:02:30.180> think<00:02:30.300> about<00:02:30.480> censorship 00:02:31.010 --> 00:02:31.020 align:start position:0% it how would you think about censorship 00:02:31.020 --> 00:02:32.990 align:start position:0% it how would you think about censorship resistance<00:02:31.620> how<00:02:32.160> do<00:02:32.220> you<00:02:32.340> think<00:02:32.459> about<00:02:32.580> access 00:02:32.990 --> 00:02:33.000 align:start position:0% resistance how do you think about access 00:02:33.000 --> 00:02:34.850 align:start position:0% resistance how do you think about access to<00:02:33.360> it<00:02:33.480> that's<00:02:33.780> always<00:02:34.020> permanent<00:02:34.500> and<00:02:34.680> always 00:02:34.850 --> 00:02:34.860 align:start position:0% to it that's always permanent and always 00:02:34.860 --> 00:02:37.010 align:start position:0% to it that's always permanent and always accessible<00:02:35.400> and<00:02:36.180> then<00:02:36.300> also<00:02:36.540> how<00:02:36.780> would<00:02:36.900> you 00:02:37.010 --> 00:02:37.020 align:start position:0% accessible and then also how would you 00:02:37.020 --> 00:02:38.750 align:start position:0% accessible and then also how would you think<00:02:37.140> about<00:02:37.260> just<00:02:37.620> incorporating<00:02:38.160> privacy 00:02:38.750 --> 00:02:38.760 align:start position:0% think about just incorporating privacy 00:02:38.760 --> 00:02:40.910 align:start position:0% think about just incorporating privacy into<00:02:39.360> every<00:02:39.780> single<00:02:40.020> piece<00:02:40.319> of<00:02:40.379> your<00:02:40.680> data 00:02:40.910 --> 00:02:40.920 align:start position:0% into every single piece of your data 00:02:40.920 --> 00:02:42.890 align:start position:0% into every single piece of your data storage<00:02:41.099> and<00:02:41.340> identity 00:02:42.890 --> 00:02:42.900 align:start position:0% storage and identity 00:02:42.900 --> 00:02:44.509 align:start position:0% storage and identity finally<00:02:43.500> this<00:02:43.739> one's<00:02:43.920> a<00:02:44.040> little<00:02:44.099> interesting 00:02:44.509 --> 00:02:44.519 align:start position:0% finally this one's a little interesting 00:02:44.519 --> 00:02:46.130 align:start position:0% finally this one's a little interesting we<00:02:45.060> think<00:02:45.180> that<00:02:45.360> application<00:02:45.780> should<00:02:46.019> be 00:02:46.130 --> 00:02:46.140 align:start position:0% we think that application should be 00:02:46.140 --> 00:02:47.930 align:start position:0% we think that application should be interoperable<00:02:46.680> so<00:02:47.280> when<00:02:47.400> you're<00:02:47.519> no<00:02:47.700> longer 00:02:47.930 --> 00:02:47.940 align:start position:0% interoperable so when you're no longer 00:02:47.940 --> 00:02:50.089 align:start position:0% interoperable so when you're no longer asking<00:02:48.420> an<00:02:48.780> oauth<00:02:49.200> application<00:02:49.560> like<00:02:49.860> Google 00:02:50.089 --> 00:02:50.099 align:start position:0% asking an oauth application like Google 00:02:50.099 --> 00:02:52.009 align:start position:0% asking an oauth application like Google for<00:02:50.400> your<00:02:50.580> identity<00:02:50.940> we<00:02:51.480> want<00:02:51.599> you<00:02:51.720> to<00:02:51.840> be<00:02:51.900> able 00:02:52.009 --> 00:02:52.019 align:start position:0% for your identity we want you to be able 00:02:52.019 --> 00:02:53.750 align:start position:0% for your identity we want you to be able to<00:02:52.140> use<00:02:52.260> that<00:02:52.500> information<00:02:52.739> in<00:02:53.400> other<00:02:53.580> parts 00:02:53.750 --> 00:02:53.760 align:start position:0% to use that information in other parts 00:02:53.760 --> 00:02:55.610 align:start position:0% to use that information in other parts of<00:02:53.940> the<00:02:54.060> web<00:02:54.180> so<00:02:54.540> whether<00:02:54.720> it's<00:02:55.019> logging<00:02:55.500> into 00:02:55.610 --> 00:02:55.620 align:start position:0% of the web so whether it's logging into 00:02:55.620 --> 00:02:58.130 align:start position:0% of the web so whether it's logging into another<00:02:55.860> product<00:02:56.300> uh<00:02:57.300> storing<00:02:57.660> your<00:02:57.840> data 00:02:58.130 --> 00:02:58.140 align:start position:0% another product uh storing your data 00:02:58.140 --> 00:03:00.770 align:start position:0% another product uh storing your data elsewhere<00:02:58.500> or<00:02:59.160> building<00:02:59.459> really<00:02:59.819> cool<00:03:00.060> API 00:03:00.770 --> 00:03:00.780 align:start position:0% elsewhere or building really cool API 00:03:00.780 --> 00:03:02.869 align:start position:0% elsewhere or building really cool API and<00:03:01.140> programmatic<00:03:01.680> Integrations<00:03:02.160> to<00:03:02.580> all<00:03:02.760> the 00:03:02.869 --> 00:03:02.879 align:start position:0% and programmatic Integrations to all the 00:03:02.879 --> 00:03:04.910 align:start position:0% and programmatic Integrations to all the files<00:03:03.239> and<00:03:03.420> things<00:03:03.540> that<00:03:03.720> you<00:03:03.900> create 00:03:04.910 --> 00:03:04.920 align:start position:0% files and things that you create 00:03:04.920 --> 00:03:06.350 align:start position:0% files and things that you create and<00:03:05.340> lastly<00:03:05.580> we'll<00:03:05.760> just<00:03:05.879> say<00:03:06.000> this<00:03:06.180> very 00:03:06.350 --> 00:03:06.360 align:start position:0% and lastly we'll just say this very 00:03:06.360 --> 00:03:07.670 align:start position:0% and lastly we'll just say this very briefly<00:03:06.720> we<00:03:07.080> think<00:03:07.200> it<00:03:07.319> should<00:03:07.440> be<00:03:07.560> open 00:03:07.670 --> 00:03:07.680 align:start position:0% briefly we think it should be open 00:03:07.680 --> 00:03:08.990 align:start position:0% briefly we think it should be open source<00:03:08.160> which<00:03:08.459> is<00:03:08.519> something<00:03:08.700> we've 00:03:08.990 --> 00:03:09.000 align:start position:0% source which is something we've 00:03:09.000 --> 00:03:11.089 align:start position:0% source which is something we've committed<00:03:09.300> to<00:03:09.480> at<00:03:09.660> skiff<00:03:10.019> but<00:03:10.620> also<00:03:10.860> I<00:03:10.980> think 00:03:11.089 --> 00:03:11.099 align:start position:0% committed to at skiff but also I think 00:03:11.099 --> 00:03:13.070 align:start position:0% committed to at skiff but also I think something<00:03:11.400> that<00:03:11.879> uh<00:03:12.480> in<00:03:12.720> the<00:03:12.840> entire 00:03:13.070 --> 00:03:13.080 align:start position:0% something that uh in the entire 00:03:13.080 --> 00:03:15.470 align:start position:0% something that uh in the entire community<00:03:13.379> of<00:03:14.040> just<00:03:14.700> ethereum<00:03:15.180> and<00:03:15.360> the 00:03:15.470 --> 00:03:15.480 align:start position:0% community of just ethereum and the 00:03:15.480 --> 00:03:17.390 align:start position:0% community of just ethereum and the crypto<00:03:15.659> ecosystem<00:03:16.140> is<00:03:16.620> really<00:03:16.860> important<00:03:17.159> to 00:03:17.390 --> 00:03:17.400 align:start position:0% crypto ecosystem is really important to 00:03:17.400 --> 00:03:19.190 align:start position:0% crypto ecosystem is really important to make<00:03:17.519> sure<00:03:17.700> people<00:03:17.879> trust<00:03:18.360> what<00:03:18.780> you<00:03:18.900> can<00:03:19.080> do 00:03:19.190 --> 00:03:19.200 align:start position:0% make sure people trust what you can do 00:03:19.200 --> 00:03:22.869 align:start position:0% make sure people trust what you can do and<00:03:19.319> also<00:03:19.620> can<00:03:19.739> replicate<00:03:20.159> it 00:03:22.869 --> 00:03:22.879 align:start position:0% 00:03:22.879 --> 00:03:25.910 align:start position:0% so<00:03:23.879> we'll<00:03:24.000> start<00:03:24.180> with<00:03:24.300> privacy<00:03:24.659> first<00:03:24.900> with<00:03:25.620> a 00:03:25.910 --> 00:03:25.920 align:start position:0% so we'll start with privacy first with a 00:03:25.920 --> 00:03:28.309 align:start position:0% so we'll start with privacy first with a pretty<00:03:26.040> intuitive<00:03:26.459> saying<00:03:27.120> which<00:03:27.360> is<00:03:27.540> if<00:03:28.200> you 00:03:28.309 --> 00:03:28.319 align:start position:0% pretty intuitive saying which is if you 00:03:28.319 --> 00:03:31.130 align:start position:0% pretty intuitive saying which is if you own<00:03:28.500> the<00:03:28.620> keys<00:03:28.920> you<00:03:29.159> also<00:03:29.340> own<00:03:29.459> the<00:03:29.640> data 00:03:31.130 --> 00:03:31.140 align:start position:0% own the keys you also own the data 00:03:31.140 --> 00:03:33.170 align:start position:0% own the keys you also own the data um<00:03:31.319> and<00:03:31.860> so<00:03:31.980> basically<00:03:32.400> everything<00:03:32.760> on<00:03:33.060> the 00:03:33.170 --> 00:03:33.180 align:start position:0% um and so basically everything on the 00:03:33.180 --> 00:03:35.089 align:start position:0% um and so basically everything on the plot<00:03:33.360> the<00:03:33.720> product<00:03:33.840> should<00:03:34.200> be<00:03:34.260> n10<00:03:34.620> encrypted 00:03:35.089 --> 00:03:35.099 align:start position:0% plot the product should be n10 encrypted 00:03:35.099 --> 00:03:36.530 align:start position:0% plot the product should be n10 encrypted from<00:03:35.280> the<00:03:35.400> ground<00:03:35.519> up<00:03:35.700> so<00:03:36.000> you're<00:03:36.120> sending<00:03:36.420> a 00:03:36.530 --> 00:03:36.540 align:start position:0% from the ground up so you're sending a 00:03:36.540 --> 00:03:38.149 align:start position:0% from the ground up so you're sending a message<00:03:36.720> keep<00:03:37.080> that<00:03:37.319> message<00:03:37.500> private<00:03:38.040> only 00:03:38.149 --> 00:03:38.159 align:start position:0% message keep that message private only 00:03:38.159 --> 00:03:39.649 align:start position:0% message keep that message private only to<00:03:38.400> you<00:03:38.519> and<00:03:38.640> the<00:03:38.760> recipient<00:03:39.120> if<00:03:39.540> you're 00:03:39.649 --> 00:03:39.659 align:start position:0% to you and the recipient if you're 00:03:39.659 --> 00:03:40.910 align:start position:0% to you and the recipient if you're uploading<00:03:40.019> a<00:03:40.140> file<00:03:40.319> or<00:03:40.440> piece<00:03:40.739> of<00:03:40.799> information 00:03:40.910 --> 00:03:40.920 align:start position:0% uploading a file or piece of information 00:03:40.920 --> 00:03:43.190 align:start position:0% uploading a file or piece of information make<00:03:41.519> sure<00:03:41.640> that's<00:03:41.819> also<00:03:42.239> private<00:03:42.780> only<00:03:42.959> to 00:03:43.190 --> 00:03:43.200 align:start position:0% make sure that's also private only to 00:03:43.200 --> 00:03:45.289 align:start position:0% make sure that's also private only to you<00:03:43.379> we've<00:03:44.340> basically<00:03:44.519> just<00:03:44.640> seen<00:03:44.879> countless 00:03:45.289 --> 00:03:45.299 align:start position:0% you we've basically just seen countless 00:03:45.299 --> 00:03:47.089 align:start position:0% you we've basically just seen countless examples<00:03:45.780> in<00:03:46.080> the<00:03:46.200> last<00:03:46.319> two<00:03:46.560> years<00:03:46.739> with 00:03:47.089 --> 00:03:47.099 align:start position:0% examples in the last two years with 00:03:47.099 --> 00:03:48.890 align:start position:0% examples in the last two years with people<00:03:47.340> storing<00:03:48.000> things<00:03:48.180> on<00:03:48.420> the<00:03:48.480> cloud<00:03:48.659> and 00:03:48.890 --> 00:03:48.900 align:start position:0% people storing things on the cloud and 00:03:48.900 --> 00:03:51.050 align:start position:0% people storing things on the cloud and being<00:03:49.080> de-platformed<00:03:49.980> targeted<00:03:50.760> for<00:03:50.940> the 00:03:51.050 --> 00:03:51.060 align:start position:0% being de-platformed targeted for the 00:03:51.060 --> 00:03:52.130 align:start position:0% being de-platformed targeted for the things<00:03:51.239> that<00:03:51.420> they<00:03:51.599> store<00:03:51.720> in<00:03:51.900> a<00:03:52.080> cloud 00:03:52.130 --> 00:03:52.140 align:start position:0% things that they store in a cloud 00:03:52.140 --> 00:03:54.050 align:start position:0% things that they store in a cloud provider<00:03:52.680> or<00:03:53.159> just<00:03:53.340> not<00:03:53.519> really<00:03:53.700> able<00:03:53.940> to 00:03:54.050 --> 00:03:54.060 align:start position:0% provider or just not really able to 00:03:54.060 --> 00:03:55.670 align:start position:0% provider or just not really able to understand<00:03:54.360> and<00:03:54.780> Trust<00:03:54.959> where<00:03:55.200> their<00:03:55.379> data<00:03:55.620> is 00:03:55.670 --> 00:03:55.680 align:start position:0% understand and Trust where their data is 00:03:55.680 --> 00:03:57.949 align:start position:0% understand and Trust where their data is being<00:03:55.860> used<00:03:56.099> is<00:03:56.760> it<00:03:56.879> being<00:03:57.060> dropped<00:03:57.540> into<00:03:57.659> some 00:03:57.949 --> 00:03:57.959 align:start position:0% being used is it being dropped into some 00:03:57.959 --> 00:04:00.050 align:start position:0% being used is it being dropped into some massive<00:03:58.620> machine<00:03:58.799> learning<00:03:59.220> model<00:03:59.400> is<00:03:59.879> it 00:04:00.050 --> 00:04:00.060 align:start position:0% massive machine learning model is it 00:04:00.060 --> 00:04:01.369 align:start position:0% massive machine learning model is it being<00:04:00.239> used<00:04:00.420> in<00:04:00.659> some<00:04:00.840> massive<00:04:01.200> search 00:04:01.369 --> 00:04:01.379 align:start position:0% being used in some massive search 00:04:01.379 --> 00:04:03.770 align:start position:0% being used in some massive search indexing<00:04:01.920> algorithm<00:04:02.459> that's<00:04:02.700> also<00:04:03.060> just<00:04:03.360> used 00:04:03.770 --> 00:04:03.780 align:start position:0% indexing algorithm that's also just used 00:04:03.780 --> 00:04:06.470 align:start position:0% indexing algorithm that's also just used across<00:04:04.260> 500<00:04:04.680> million<00:04:04.980> other<00:04:05.159> users<00:04:05.519> your<00:04:06.180> data 00:04:06.470 --> 00:04:06.480 align:start position:0% across 500 million other users your data 00:04:06.480 --> 00:04:07.610 align:start position:0% across 500 million other users your data should<00:04:06.599> be<00:04:06.720> private<00:04:07.019> to<00:04:07.140> you<00:04:07.260> and<00:04:07.379> n10 00:04:07.610 --> 00:04:07.620 align:start position:0% should be private to you and n10 00:04:07.620 --> 00:04:09.229 align:start position:0% should be private to you and n10 encrypted 00:04:09.229 --> 00:04:09.239 align:start position:0% encrypted 00:04:09.239 --> 00:04:11.449 align:start position:0% encrypted I<00:04:09.720> skipped<00:04:10.019> over<00:04:10.080> this<00:04:10.319> but<00:04:10.500> we<00:04:10.920> also<00:04:11.159> want<00:04:11.340> to 00:04:11.449 --> 00:04:11.459 align:start position:0% I skipped over this but we also want to 00:04:11.459 --> 00:04:12.530 align:start position:0% I skipped over this but we also want to make<00:04:11.640> sure<00:04:11.760> there's<00:04:12.000> no<00:04:12.239> personally 00:04:12.530 --> 00:04:12.540 align:start position:0% make sure there's no personally 00:04:12.540 --> 00:04:14.330 align:start position:0% make sure there's no personally identifying<00:04:13.140> information<00:04:13.319> inside<00:04:13.980> these 00:04:14.330 --> 00:04:14.340 align:start position:0% identifying information inside these 00:04:14.340 --> 00:04:16.969 align:start position:0% identifying information inside these products<00:04:14.700> this<00:04:15.540> is<00:04:15.720> slightly<00:04:16.199> controversial 00:04:16.969 --> 00:04:16.979 align:start position:0% products this is slightly controversial 00:04:16.979 --> 00:04:20.509 align:start position:0% products this is slightly controversial uh<00:04:17.519> depending<00:04:17.880> on<00:04:18.000> the<00:04:18.120> application<00:04:18.620> but<00:04:19.620> uh 00:04:20.509 --> 00:04:20.519 align:start position:0% uh depending on the application but uh 00:04:20.519 --> 00:04:22.069 align:start position:0% uh depending on the application but uh in<00:04:20.820> the<00:04:20.880> encrypted<00:04:21.299> messaging<00:04:21.660> space<00:04:21.840> and 00:04:22.069 --> 00:04:22.079 align:start position:0% in the encrypted messaging space and 00:04:22.079 --> 00:04:23.930 align:start position:0% in the encrypted messaging space and antenna<00:04:22.380> encrypted<00:04:22.740> Communications<00:04:23.160> it's 00:04:23.930 --> 00:04:23.940 align:start position:0% antenna encrypted Communications it's 00:04:23.940 --> 00:04:25.310 align:start position:0% antenna encrypted Communications it's really<00:04:24.120> kind<00:04:24.300> of<00:04:24.419> this<00:04:24.600> Ground<00:04:24.840> Zero 00:04:25.310 --> 00:04:25.320 align:start position:0% really kind of this Ground Zero 00:04:25.320 --> 00:04:27.230 align:start position:0% really kind of this Ground Zero expectation<00:04:25.800> that<00:04:26.040> people<00:04:26.220> have<00:04:26.520> where<00:04:27.000> you 00:04:27.230 --> 00:04:27.240 align:start position:0% expectation that people have where you 00:04:27.240 --> 00:04:28.430 align:start position:0% expectation that people have where you want<00:04:27.300> to<00:04:27.419> be<00:04:27.479> able<00:04:27.600> to<00:04:27.720> use<00:04:27.900> a<00:04:28.080> messaging 00:04:28.430 --> 00:04:28.440 align:start position:0% want to be able to use a messaging 00:04:28.440 --> 00:04:29.749 align:start position:0% want to be able to use a messaging product<00:04:28.620> you<00:04:28.979> want<00:04:29.100> to<00:04:29.220> be<00:04:29.280> able<00:04:29.340> to<00:04:29.460> use<00:04:29.580> a 00:04:29.749 --> 00:04:29.759 align:start position:0% product you want to be able to use a 00:04:29.759 --> 00:04:31.490 align:start position:0% product you want to be able to use a communication<00:04:30.120> product<00:04:30.419> without<00:04:31.020> giving<00:04:31.320> out 00:04:31.490 --> 00:04:31.500 align:start position:0% communication product without giving out 00:04:31.500 --> 00:04:34.070 align:start position:0% communication product without giving out a<00:04:31.680> phone<00:04:31.800> number<00:04:31.979> or<00:04:32.220> a<00:04:32.340> real<00:04:32.460> name<00:04:32.940> Etc<00:04:33.120> and<00:04:33.900> so 00:04:34.070 --> 00:04:34.080 align:start position:0% a phone number or a real name Etc and so 00:04:34.080 --> 00:04:35.570 align:start position:0% a phone number or a real name Etc and so many<00:04:34.199> places<00:04:34.380> in<00:04:34.620> the<00:04:34.740> world<00:04:34.860> now<00:04:35.100> make<00:04:35.400> it 00:04:35.570 --> 00:04:35.580 align:start position:0% many places in the world now make it 00:04:35.580 --> 00:04:37.310 align:start position:0% many places in the world now make it harder<00:04:36.000> and<00:04:36.060> harder<00:04:36.360> to<00:04:36.419> do<00:04:36.600> that<00:04:36.780> whether<00:04:37.139> you 00:04:37.310 --> 00:04:37.320 align:start position:0% harder and harder to do that whether you 00:04:37.320 --> 00:04:39.050 align:start position:0% harder and harder to do that whether you need<00:04:37.440> to<00:04:37.560> submit<00:04:37.800> an<00:04:37.919> ID<00:04:38.100> to<00:04:38.460> buy<00:04:38.580> a<00:04:38.759> SIM<00:04:38.880> card 00:04:39.050 --> 00:04:39.060 align:start position:0% need to submit an ID to buy a SIM card 00:04:39.060 --> 00:04:40.730 align:start position:0% need to submit an ID to buy a SIM card or<00:04:39.780> you<00:04:39.960> need<00:04:40.020> to<00:04:40.139> go<00:04:40.259> through<00:04:40.440> an<00:04:40.620> internet 00:04:40.730 --> 00:04:40.740 align:start position:0% or you need to go through an internet 00:04:40.740 --> 00:04:42.409 align:start position:0% or you need to go through an internet provider<00:04:41.340> or<00:04:41.520> an<00:04:41.639> email<00:04:41.759> provider<00:04:42.240> and 00:04:42.409 --> 00:04:42.419 align:start position:0% provider or an email provider and 00:04:42.419 --> 00:04:44.030 align:start position:0% provider or an email provider and provide<00:04:42.720> another<00:04:42.900> address<00:04:43.199> or<00:04:43.560> some<00:04:43.800> sort<00:04:43.979> of 00:04:44.030 --> 00:04:44.040 align:start position:0% provide another address or some sort of 00:04:44.040 --> 00:04:46.010 align:start position:0% provide another address or some sort of accountability<00:04:44.520> chain<00:04:44.880> so<00:04:45.540> that<00:04:45.720> first<00:04:45.840> one 00:04:46.010 --> 00:04:46.020 align:start position:0% accountability chain so that first one 00:04:46.020 --> 00:04:48.110 align:start position:0% accountability chain so that first one is<00:04:46.139> also<00:04:46.380> really<00:04:46.500> important<00:04:46.860> to<00:04:47.040> us<00:04:47.160> and 00:04:48.110 --> 00:04:48.120 align:start position:0% is also really important to us and 00:04:48.120 --> 00:04:50.749 align:start position:0% is also really important to us and finally<00:04:48.419> a<00:04:49.259> lot<00:04:49.380> of<00:04:49.560> this<00:04:49.800> these<00:04:50.400> bullet 00:04:50.749 --> 00:04:50.759 align:start position:0% finally a lot of this these bullet 00:04:50.759 --> 00:04:52.370 align:start position:0% finally a lot of this these bullet points<00:04:51.060> actually<00:04:51.300> rest<00:04:51.600> on<00:04:51.900> the<00:04:52.080> idea<00:04:52.259> of 00:04:52.370 --> 00:04:52.380 align:start position:0% points actually rest on the idea of 00:04:52.380 --> 00:04:54.290 align:start position:0% points actually rest on the idea of non-custodial<00:04:53.160> wallets<00:04:53.520> or<00:04:53.699> non-custodial 00:04:54.290 --> 00:04:54.300 align:start position:0% non-custodial wallets or non-custodial 00:04:54.300 --> 00:04:56.330 align:start position:0% non-custodial wallets or non-custodial public<00:04:54.540> keys<00:04:55.020> where<00:04:55.560> if<00:04:55.680> you're<00:04:55.800> doing<00:04:55.979> n10 00:04:56.330 --> 00:04:56.340 align:start position:0% public keys where if you're doing n10 00:04:56.340 --> 00:04:58.189 align:start position:0% public keys where if you're doing n10 encryption<00:04:56.880> you<00:04:57.360> kind<00:04:57.479> of<00:04:57.600> have<00:04:57.720> to<00:04:57.840> own<00:04:57.960> your 00:04:58.189 --> 00:04:58.199 align:start position:0% encryption you kind of have to own your 00:04:58.199 --> 00:05:00.469 align:start position:0% encryption you kind of have to own your own<00:04:58.320> key<00:04:58.500> pair<00:04:58.740> and<00:04:59.340> so<00:04:59.520> that<00:04:59.820> poses<00:05:00.240> a<00:05:00.360> bunch 00:05:00.469 --> 00:05:00.479 align:start position:0% own key pair and so that poses a bunch 00:05:00.479 --> 00:05:01.730 align:start position:0% own key pair and so that poses a bunch of<00:05:00.600> interesting<00:05:01.020> consumer<00:05:01.560> product 00:05:01.730 --> 00:05:01.740 align:start position:0% of interesting consumer product 00:05:01.740 --> 00:05:04.610 align:start position:0% of interesting consumer product challenges<00:05:02.280> that<00:05:02.820> we'll<00:05:02.940> get<00:05:03.120> to<00:05:03.180> shortly 00:05:04.610 --> 00:05:04.620 align:start position:0% challenges that we'll get to shortly 00:05:04.620 --> 00:05:06.830 align:start position:0% challenges that we'll get to shortly so<00:05:05.040> on<00:05:05.220> that<00:05:05.400> next<00:05:05.520> point<00:05:05.759> of<00:05:06.060> decentralized 00:05:06.830 --> 00:05:06.840 align:start position:0% so on that next point of decentralized 00:05:06.840 --> 00:05:08.810 align:start position:0% so on that next point of decentralized we<00:05:07.199> talked<00:05:07.440> a<00:05:07.500> bit<00:05:07.620> about<00:05:07.740> how<00:05:08.100> decentralized 00:05:08.810 --> 00:05:08.820 align:start position:0% we talked a bit about how decentralized 00:05:08.820 --> 00:05:10.730 align:start position:0% we talked a bit about how decentralized can<00:05:08.940> lead<00:05:09.060> to<00:05:09.240> censorship<00:05:09.600> resistance<00:05:10.139> where 00:05:10.730 --> 00:05:10.740 align:start position:0% can lead to censorship resistance where 00:05:10.740 --> 00:05:12.290 align:start position:0% can lead to censorship resistance where there<00:05:10.979> isn't<00:05:11.220> a<00:05:11.340> single<00:05:11.580> kind<00:05:11.759> of<00:05:11.880> point<00:05:12.120> of 00:05:12.290 --> 00:05:12.300 align:start position:0% there isn't a single kind of point of 00:05:12.300 --> 00:05:13.790 align:start position:0% there isn't a single kind of point of de-platforming<00:05:13.020> where<00:05:13.199> you<00:05:13.320> can<00:05:13.380> get<00:05:13.500> kicked 00:05:13.790 --> 00:05:13.800 align:start position:0% de-platforming where you can get kicked 00:05:13.800 --> 00:05:15.110 align:start position:0% de-platforming where you can get kicked out<00:05:13.860> of<00:05:13.979> your<00:05:14.100> identity<00:05:14.460> or<00:05:14.639> kicked<00:05:14.940> out<00:05:15.000> of 00:05:15.110 --> 00:05:15.120 align:start position:0% out of your identity or kicked out of 00:05:15.120 --> 00:05:17.150 align:start position:0% out of your identity or kicked out of your<00:05:15.240> product<00:05:15.419> and<00:05:16.380> also<00:05:16.620> with<00:05:16.800> n10 00:05:17.150 --> 00:05:17.160 align:start position:0% your product and also with n10 00:05:17.160 --> 00:05:19.430 align:start position:0% your product and also with n10 encryption<00:05:17.699> it's<00:05:18.240> really<00:05:18.360> unclear<00:05:18.840> even<00:05:19.020> who 00:05:19.430 --> 00:05:19.440 align:start position:0% encryption it's really unclear even who 00:05:19.440 --> 00:05:21.110 align:start position:0% encryption it's really unclear even who is<00:05:19.560> using<00:05:19.919> that<00:05:20.040> data<00:05:20.340> or<00:05:20.520> how<00:05:20.699> it's<00:05:20.820> going<00:05:21.000> to 00:05:21.110 --> 00:05:21.120 align:start position:0% is using that data or how it's going to 00:05:21.120 --> 00:05:22.850 align:start position:0% is using that data or how it's going to be<00:05:21.240> processed<00:05:21.780> Beyond<00:05:22.199> just<00:05:22.380> the<00:05:22.560> things<00:05:22.680> that 00:05:22.850 --> 00:05:22.860 align:start position:0% be processed Beyond just the things that 00:05:22.860 --> 00:05:24.170 align:start position:0% be processed Beyond just the things that you<00:05:22.979> do<00:05:23.100> with<00:05:23.280> it 00:05:24.170 --> 00:05:24.180 align:start position:0% you do with it 00:05:24.180 --> 00:05:26.450 align:start position:0% you do with it this<00:05:24.600> also<00:05:24.900> translates<00:05:25.259> into<00:05:25.680> client-side 00:05:26.450 --> 00:05:26.460 align:start position:0% this also translates into client-side 00:05:26.460 --> 00:05:29.150 align:start position:0% this also translates into client-side data<00:05:26.940> storage<00:05:27.060> data<00:05:27.840> structures<00:05:28.259> sharing 00:05:29.150 --> 00:05:29.160 align:start position:0% data storage data structures sharing 00:05:29.160 --> 00:05:31.790 align:start position:0% data storage data structures sharing search<00:05:29.820> collaboration<00:05:30.419> and<00:05:30.720> more<00:05:30.900> so<00:05:31.560> once 00:05:31.790 --> 00:05:31.800 align:start position:0% search collaboration and more so once 00:05:31.800 --> 00:05:33.050 align:start position:0% search collaboration and more so once you've<00:05:31.919> gone<00:05:32.100> down<00:05:32.340> the<00:05:32.460> path<00:05:32.639> of<00:05:32.820> n10 00:05:33.050 --> 00:05:33.060 align:start position:0% you've gone down the path of n10 00:05:33.060 --> 00:05:35.150 align:start position:0% you've gone down the path of n10 encryption<00:05:33.600> any<00:05:34.320> product<00:05:34.560> that<00:05:34.860> you<00:05:35.039> build 00:05:35.150 --> 00:05:35.160 align:start position:0% encryption any product that you build 00:05:35.160 --> 00:05:37.610 align:start position:0% encryption any product that you build will<00:05:35.699> not<00:05:35.940> have<00:05:36.060> access<00:05:36.300> to<00:05:36.539> user<00:05:36.900> data<00:05:37.199> and 00:05:37.610 --> 00:05:37.620 align:start position:0% will not have access to user data and 00:05:37.620 --> 00:05:39.170 align:start position:0% will not have access to user data and what<00:05:37.740> that<00:05:37.919> means<00:05:38.160> is<00:05:38.340> you've<00:05:38.639> kind<00:05:38.759> of<00:05:38.820> set<00:05:39.000> up 00:05:39.170 --> 00:05:39.180 align:start position:0% what that means is you've kind of set up 00:05:39.180 --> 00:05:40.969 align:start position:0% what that means is you've kind of set up an<00:05:39.479> entire<00:05:39.780> sequence<00:05:40.199> of<00:05:40.380> challenges<00:05:40.800> and 00:05:40.969 --> 00:05:40.979 align:start position:0% an entire sequence of challenges and 00:05:40.979 --> 00:05:42.110 align:start position:0% an entire sequence of challenges and Hoops<00:05:41.340> that<00:05:41.400> you<00:05:41.520> have<00:05:41.639> to<00:05:41.759> jump<00:05:41.880> through 00:05:42.110 --> 00:05:42.120 align:start position:0% Hoops that you have to jump through 00:05:42.120 --> 00:05:44.390 align:start position:0% Hoops that you have to jump through whether<00:05:42.840> it's<00:05:43.020> rebuilding<00:05:43.560> how<00:05:43.740> search<00:05:43.979> works 00:05:44.390 --> 00:05:44.400 align:start position:0% whether it's rebuilding how search works 00:05:44.400 --> 00:05:45.830 align:start position:0% whether it's rebuilding how search works you<00:05:44.699> know<00:05:44.759> searching<00:05:45.120> on<00:05:45.300> someone's<00:05:45.660> device 00:05:45.830 --> 00:05:45.840 align:start position:0% you know searching on someone's device 00:05:45.840 --> 00:05:48.110 align:start position:0% you know searching on someone's device or<00:05:46.680> rebuilding<00:05:47.160> how<00:05:47.280> you<00:05:47.460> share<00:05:47.639> that<00:05:47.820> data 00:05:48.110 --> 00:05:48.120 align:start position:0% or rebuilding how you share that data 00:05:48.120 --> 00:05:49.670 align:start position:0% or rebuilding how you share that data with<00:05:48.240> other<00:05:48.419> people<00:05:48.600> so<00:05:48.960> if<00:05:49.139> I<00:05:49.259> want<00:05:49.380> to<00:05:49.500> share 00:05:49.670 --> 00:05:49.680 align:start position:0% with other people so if I want to share 00:05:49.680 --> 00:05:51.050 align:start position:0% with other people so if I want to share a<00:05:49.860> file<00:05:50.039> or<00:05:50.220> a<00:05:50.340> document<00:05:50.580> with<00:05:50.880> another 00:05:51.050 --> 00:05:51.060 align:start position:0% a file or a document with another 00:05:51.060 --> 00:05:53.570 align:start position:0% a file or a document with another collaborator<00:05:51.720> how<00:05:52.560> can<00:05:52.740> you<00:05:53.039> know<00:05:53.100> I<00:05:53.220> as<00:05:53.460> a 00:05:53.570 --> 00:05:53.580 align:start position:0% collaborator how can you know I as a 00:05:53.580 --> 00:05:55.370 align:start position:0% collaborator how can you know I as a user<00:05:53.820> do<00:05:53.940> that<00:05:54.060> but<00:05:54.360> the<00:05:54.479> platform<00:05:54.840> never<00:05:55.199> be 00:05:55.370 --> 00:05:55.380 align:start position:0% user do that but the platform never be 00:05:55.380 --> 00:05:57.529 align:start position:0% user do that but the platform never be able<00:05:55.560> to<00:05:55.680> do<00:05:55.800> something<00:05:56.039> like<00:05:56.340> that 00:05:57.529 --> 00:05:57.539 align:start position:0% able to do something like that 00:05:57.539 --> 00:05:59.689 align:start position:0% able to do something like that finally<00:05:58.259> one<00:05:58.680> super<00:05:58.860> important<00:05:59.220> point<00:05:59.460> is 00:05:59.689 --> 00:05:59.699 align:start position:0% finally one super important point is 00:05:59.699 --> 00:06:01.370 align:start position:0% finally one super important point is also<00:05:59.940> how<00:06:00.120> you<00:06:00.300> trust<00:06:00.600> the<00:06:00.780> platform<00:06:01.020> in<00:06:01.199> the 00:06:01.370 --> 00:06:01.380 align:start position:0% also how you trust the platform in the 00:06:01.380 --> 00:06:03.110 align:start position:0% also how you trust the platform in the product<00:06:01.500> as<00:06:01.800> well<00:06:01.979> and<00:06:02.460> so<00:06:02.639> that<00:06:02.759> comes<00:06:03.000> from 00:06:03.110 --> 00:06:03.120 align:start position:0% product as well and so that comes from 00:06:03.120 --> 00:06:04.370 align:start position:0% product as well and so that comes from how<00:06:03.300> you<00:06:03.419> might<00:06:03.539> actually<00:06:03.720> look<00:06:03.960> up<00:06:04.080> other 00:06:04.370 --> 00:06:04.380 align:start position:0% how you might actually look up other 00:06:04.380 --> 00:06:06.469 align:start position:0% how you might actually look up other users<00:06:04.680> public<00:06:04.919> keys<00:06:05.400> and<00:06:05.940> we'll<00:06:06.060> get<00:06:06.240> to<00:06:06.300> this 00:06:06.469 --> 00:06:06.479 align:start position:0% users public keys and we'll get to this 00:06:06.479 --> 00:06:08.150 align:start position:0% users public keys and we'll get to this later<00:06:06.600> but<00:06:06.900> this<00:06:07.080> is<00:06:07.139> one<00:06:07.320> of<00:06:07.440> the<00:06:07.500> biggest<00:06:07.740> you 00:06:08.150 --> 00:06:08.160 align:start position:0% later but this is one of the biggest you 00:06:08.160 --> 00:06:09.830 align:start position:0% later but this is one of the biggest you know<00:06:08.220> age-old<00:06:08.639> questions<00:06:09.000> in<00:06:09.360> communication 00:06:09.830 --> 00:06:09.840 align:start position:0% know age-old questions in communication 00:06:09.840 --> 00:06:11.930 align:start position:0% know age-old questions in communication how<00:06:10.500> do<00:06:10.620> I<00:06:10.740> send<00:06:10.919> a<00:06:11.100> secure<00:06:11.340> email<00:06:11.520> to<00:06:11.759> someone 00:06:11.930 --> 00:06:11.940 align:start position:0% how do I send a secure email to someone 00:06:11.940 --> 00:06:13.790 align:start position:0% how do I send a secure email to someone how<00:06:12.300> do<00:06:12.419> I<00:06:12.479> look<00:06:12.600> up<00:06:12.780> someone's<00:06:13.139> public<00:06:13.320> key<00:06:13.560> if 00:06:13.790 --> 00:06:13.800 align:start position:0% how do I look up someone's public key if 00:06:13.800 --> 00:06:16.129 align:start position:0% how do I look up someone's public key if I'm<00:06:13.979> using<00:06:14.280> you<00:06:14.820> know<00:06:14.880> signal<00:06:15.539> or<00:06:15.720> a<00:06:15.900> telegram 00:06:16.129 --> 00:06:16.139 align:start position:0% I'm using you know signal or a telegram 00:06:16.139 --> 00:06:21.770 align:start position:0% I'm using you know signal or a telegram secret<00:06:16.440> chat<00:06:16.919> or<00:06:17.280> pgp<00:06:17.820> email<00:06:18.000> back<00:06:18.479> in<00:06:18.600> the<00:06:18.720> 90s 00:06:21.770 --> 00:06:21.780 align:start position:0% 00:06:21.780 --> 00:06:24.650 align:start position:0% and<00:06:22.199> then<00:06:22.319> on<00:06:22.560> that<00:06:22.740> interoperable<00:06:23.520> point<00:06:23.819> a 00:06:24.650 --> 00:06:24.660 align:start position:0% and then on that interoperable point a 00:06:24.660 --> 00:06:26.150 align:start position:0% and then on that interoperable point a lot<00:06:24.780> of<00:06:24.900> similar<00:06:25.259> things<00:06:25.440> about<00:06:25.740> basically 00:06:26.150 --> 00:06:26.160 align:start position:0% lot of similar things about basically 00:06:26.160 --> 00:06:27.590 align:start position:0% lot of similar things about basically giving<00:06:26.400> people<00:06:26.639> ownership<00:06:27.060> of<00:06:27.419> their 00:06:27.590 --> 00:06:27.600 align:start position:0% giving people ownership of their 00:06:27.600 --> 00:06:29.390 align:start position:0% giving people ownership of their identity<00:06:27.960> through<00:06:28.259> self-custody<00:06:28.979> of<00:06:29.280> their 00:06:29.390 --> 00:06:29.400 align:start position:0% identity through self-custody of their 00:06:29.400 --> 00:06:32.210 align:start position:0% identity through self-custody of their keys<00:06:29.699> or<00:06:29.819> wallets<00:06:30.120> and<00:06:30.960> then<00:06:31.139> also<00:06:31.500> just<00:06:31.860> using 00:06:32.210 --> 00:06:32.220 align:start position:0% keys or wallets and then also just using 00:06:32.220 --> 00:06:34.490 align:start position:0% keys or wallets and then also just using a<00:06:32.460> much<00:06:32.580> more<00:06:32.819> local<00:06:33.120> first<00:06:33.479> on<00:06:33.900> device<00:06:34.139> model 00:06:34.490 --> 00:06:34.500 align:start position:0% a much more local first on device model 00:06:34.500 --> 00:06:36.350 align:start position:0% a much more local first on device model where<00:06:35.100> data<00:06:35.460> can<00:06:35.580> still<00:06:35.699> be<00:06:35.880> synced<00:06:36.240> or 00:06:36.350 --> 00:06:36.360 align:start position:0% where data can still be synced or 00:06:36.360 --> 00:06:37.909 align:start position:0% where data can still be synced or synchronized<00:06:36.900> across<00:06:37.199> the<00:06:37.319> devices<00:06:37.620> and 00:06:37.909 --> 00:06:37.919 align:start position:0% synchronized across the devices and 00:06:37.919 --> 00:06:40.070 align:start position:0% synchronized across the devices and things<00:06:38.100> that<00:06:38.280> you<00:06:38.400> use<00:06:38.639> but<00:06:39.300> because<00:06:39.419> it's<00:06:39.660> n10 00:06:40.070 --> 00:06:40.080 align:start position:0% things that you use but because it's n10 00:06:40.080 --> 00:06:42.050 align:start position:0% things that you use but because it's n10 encrypted<00:06:40.560> a<00:06:40.919> lot<00:06:41.039> of<00:06:41.100> that<00:06:41.280> actual<00:06:41.639> computing 00:06:42.050 --> 00:06:42.060 align:start position:0% encrypted a lot of that actual computing 00:06:42.060 --> 00:06:43.969 align:start position:0% encrypted a lot of that actual computing power<00:06:42.300> and<00:06:42.539> Computing<00:06:42.900> Authority<00:06:43.319> is<00:06:43.860> no 00:06:43.969 --> 00:06:43.979 align:start position:0% power and Computing Authority is no 00:06:43.979 --> 00:06:46.370 align:start position:0% power and Computing Authority is no longer<00:06:44.220> with<00:06:44.460> the<00:06:44.580> technology<00:06:44.880> provider 00:06:46.370 --> 00:06:46.380 align:start position:0% longer with the technology provider 00:06:46.380 --> 00:06:48.590 align:start position:0% longer with the technology provider uh<00:06:47.100> and<00:06:47.340> then<00:06:47.520> we'll<00:06:47.940> cover<00:06:48.120> some<00:06:48.360> of<00:06:48.479> that 00:06:48.590 --> 00:06:48.600 align:start position:0% uh and then we'll cover some of that 00:06:48.600 --> 00:06:50.990 align:start position:0% uh and then we'll cover some of that last<00:06:48.720> point<00:06:48.960> about<00:06:49.139> command<00:06:49.800> line<00:06:49.919> access<00:06:50.220> or 00:06:50.990 --> 00:06:51.000 align:start position:0% last point about command line access or 00:06:51.000 --> 00:06:54.050 align:start position:0% last point about command line access or programmatic<00:06:51.600> access<00:06:51.780> for<00:06:52.139> your<00:06:52.319> content 00:06:54.050 --> 00:06:54.060 align:start position:0% programmatic access for your content 00:06:54.060 --> 00:06:55.430 align:start position:0% programmatic access for your content so<00:06:54.419> I<00:06:54.479> guess<00:06:54.600> let's<00:06:54.720> get<00:06:54.900> into<00:06:55.020> some<00:06:55.199> of<00:06:55.319> the 00:06:55.430 --> 00:06:55.440 align:start position:0% so I guess let's get into some of the 00:06:55.440 --> 00:06:58.550 align:start position:0% so I guess let's get into some of the actual<00:06:55.740> technical<00:06:56.400> parts<00:06:56.699> of<00:06:56.940> the<00:06:57.060> stack 00:06:58.550 --> 00:06:58.560 align:start position:0% actual technical parts of the stack 00:06:58.560 --> 00:07:00.890 align:start position:0% actual technical parts of the stack uh<00:06:59.280> how<00:06:59.580> is<00:06:59.759> actually<00:07:00.000> intent<00:07:00.539> encryption 00:07:00.890 --> 00:07:00.900 align:start position:0% uh how is actually intent encryption 00:07:00.900 --> 00:07:02.809 align:start position:0% uh how is actually intent encryption communication<00:07:01.440> been<00:07:02.220> done<00:07:02.400> in<00:07:02.580> the<00:07:02.699> past 00:07:02.809 --> 00:07:02.819 align:start position:0% communication been done in the past 00:07:02.819 --> 00:07:05.090 align:start position:0% communication been done in the past we'll<00:07:03.300> start<00:07:03.479> with<00:07:03.660> pgp<00:07:04.199> I<00:07:04.680> don't<00:07:04.860> know<00:07:04.919> Has 00:07:05.090 --> 00:07:05.100 align:start position:0% we'll start with pgp I don't know Has 00:07:05.100 --> 00:07:09.230 align:start position:0% we'll start with pgp I don't know Has anyone<00:07:05.340> used<00:07:05.819> pgp<00:07:06.360> or<00:07:06.600> uses<00:07:06.900> it<00:07:07.080> regularly 00:07:09.230 --> 00:07:09.240 align:start position:0% anyone used pgp or uses it regularly 00:07:09.240 --> 00:07:12.830 align:start position:0% anyone used pgp or uses it regularly okay<00:07:09.600> so<00:07:09.840> a<00:07:10.020> little<00:07:10.139> bit<00:07:10.259> so<00:07:10.860> pgp<00:07:11.400> is<00:07:11.819> uh<00:07:12.479> I 00:07:12.830 --> 00:07:12.840 align:start position:0% okay so a little bit so pgp is uh I 00:07:12.840 --> 00:07:15.350 align:start position:0% okay so a little bit so pgp is uh I think<00:07:12.960> a<00:07:13.440> little<00:07:13.560> over<00:07:13.740> 30<00:07:13.919> years<00:07:14.160> old<00:07:14.400> now<00:07:14.639> uh 00:07:15.350 --> 00:07:15.360 align:start position:0% think a little over 30 years old now uh 00:07:15.360 --> 00:07:17.629 align:start position:0% think a little over 30 years old now uh it<00:07:15.539> was<00:07:15.780> invented<00:07:16.620> or<00:07:16.919> published<00:07:17.340> in<00:07:17.460> the 00:07:17.629 --> 00:07:17.639 align:start position:0% it was invented or published in the 00:07:17.639 --> 00:07:20.930 align:start position:0% it was invented or published in the 1990s<00:07:18.120> I<00:07:18.300> think<00:07:18.419> 91<00:07:19.160> and<00:07:20.160> unfortunately<00:07:20.580> it's 00:07:20.930 --> 00:07:20.940 align:start position:0% 1990s I think 91 and unfortunately it's 00:07:20.940 --> 00:07:23.510 align:start position:0% 1990s I think 91 and unfortunately it's become<00:07:21.300> pretty<00:07:21.599> clunky<00:07:22.080> pretty<00:07:22.440> clunky<00:07:22.979> very 00:07:23.510 --> 00:07:23.520 align:start position:0% become pretty clunky pretty clunky very 00:07:23.520 --> 00:07:25.490 align:start position:0% become pretty clunky pretty clunky very complex<00:07:23.880> and<00:07:24.180> pretty<00:07:24.360> inefficient<00:07:24.900> where 00:07:25.490 --> 00:07:25.500 align:start position:0% complex and pretty inefficient where 00:07:25.500 --> 00:07:27.230 align:start position:0% complex and pretty inefficient where there<00:07:25.740> were<00:07:25.860> proprietary<00:07:26.340> formats<00:07:26.880> owned<00:07:27.180> by 00:07:27.230 --> 00:07:27.240 align:start position:0% there were proprietary formats owned by 00:07:27.240 --> 00:07:29.450 align:start position:0% there were proprietary formats owned by corporations<00:07:27.720> open<00:07:28.259> source<00:07:28.680> formats<00:07:29.099> owned 00:07:29.450 --> 00:07:29.460 align:start position:0% corporations open source formats owned 00:07:29.460 --> 00:07:31.370 align:start position:0% corporations open source formats owned by<00:07:29.580> you<00:07:30.000> know<00:07:30.120> open<00:07:30.240> source<00:07:30.660> standards<00:07:31.080> and 00:07:31.370 --> 00:07:31.380 align:start position:0% by you know open source standards and 00:07:31.380 --> 00:07:33.830 align:start position:0% by you know open source standards and now<00:07:31.560> just<00:07:31.919> other<00:07:32.639> basically<00:07:33.120> open<00:07:33.360> source 00:07:33.830 --> 00:07:33.840 align:start position:0% now just other basically open source 00:07:33.840 --> 00:07:35.809 align:start position:0% now just other basically open source Publications<00:07:34.440> compliance<00:07:35.160> standards<00:07:35.639> Etc 00:07:35.809 --> 00:07:35.819 align:start position:0% Publications compliance standards Etc 00:07:35.819 --> 00:07:38.150 align:start position:0% Publications compliance standards Etc that<00:07:36.539> try<00:07:36.720> and<00:07:36.840> take<00:07:37.020> this<00:07:37.199> age-old<00:07:37.620> 30<00:07:37.919> year 00:07:38.150 --> 00:07:38.160 align:start position:0% that try and take this age-old 30 year 00:07:38.160 --> 00:07:39.650 align:start position:0% that try and take this age-old 30 year old<00:07:38.280> standard<00:07:38.699> and<00:07:38.880> updated<00:07:39.240> for<00:07:39.479> modern 00:07:39.650 --> 00:07:39.660 align:start position:0% old standard and updated for modern 00:07:39.660 --> 00:07:42.409 align:start position:0% old standard and updated for modern cryptography<00:07:40.860> and<00:07:41.580> secretly<00:07:42.000> it<00:07:42.120> seems<00:07:42.360> like 00:07:42.409 --> 00:07:42.419 align:start position:0% cryptography and secretly it seems like 00:07:42.419 --> 00:07:44.930 align:start position:0% cryptography and secretly it seems like we<00:07:42.599> have<00:07:42.780> a<00:07:42.900> few<00:07:43.020> pgp<00:07:43.560> users<00:07:43.919> here<00:07:44.220> but<00:07:44.699> I'm 00:07:44.930 --> 00:07:44.940 align:start position:0% we have a few pgp users here but I'm 00:07:44.940 --> 00:07:46.189 align:start position:0% we have a few pgp users here but I'm just<00:07:45.060> going<00:07:45.180> to<00:07:45.240> say<00:07:45.360> that<00:07:45.539> almost<00:07:45.780> no<00:07:46.020> one 00:07:46.189 --> 00:07:46.199 align:start position:0% just going to say that almost no one 00:07:46.199 --> 00:07:48.290 align:start position:0% just going to say that almost no one actually<00:07:46.500> uses<00:07:46.919> it<00:07:47.039> it's<00:07:47.639> estimated<00:07:48.060> that 00:07:48.290 --> 00:07:48.300 align:start position:0% actually uses it it's estimated that 00:07:48.300 --> 00:07:50.629 align:start position:0% actually uses it it's estimated that literally<00:07:48.599> 50<00:07:49.199> 000<00:07:49.319> people<00:07:49.500> worldwide<00:07:50.280> still 00:07:50.629 --> 00:07:50.639 align:start position:0% literally 50 000 people worldwide still 00:07:50.639 --> 00:07:53.330 align:start position:0% literally 50 000 people worldwide still maintain<00:07:51.000> pgp<00:07:51.599> key<00:07:51.780> Pairs<00:07:52.259> and<00:07:52.680> if<00:07:52.800> we<00:07:52.919> look<00:07:53.099> at 00:07:53.330 --> 00:07:53.340 align:start position:0% maintain pgp key Pairs and if we look at 00:07:53.340 --> 00:07:55.249 align:start position:0% maintain pgp key Pairs and if we look at the<00:07:53.819> other<00:07:54.000> option<00:07:54.300> for<00:07:54.479> n10<00:07:54.780> encrypted 00:07:55.249 --> 00:07:55.259 align:start position:0% the other option for n10 encrypted 00:07:55.259 --> 00:07:57.110 align:start position:0% the other option for n10 encrypted private<00:07:55.620> communication<00:07:56.099> we're<00:07:56.759> literally 00:07:57.110 --> 00:07:57.120 align:start position:0% private communication we're literally 00:07:57.120 --> 00:07:59.029 align:start position:0% private communication we're literally looking<00:07:57.300> at<00:07:57.599> many<00:07:57.960> three<00:07:58.319> four<00:07:58.560> orders<00:07:58.919> of 00:07:59.029 --> 00:07:59.039 align:start position:0% looking at many three four orders of 00:07:59.039 --> 00:08:01.070 align:start position:0% looking at many three four orders of magnitude<00:07:59.520> of<00:07:59.759> different<00:07:59.940> scale<00:08:00.419> and<00:08:00.840> so<00:08:00.960> you 00:08:01.070 --> 00:08:01.080 align:start position:0% magnitude of different scale and so you 00:08:01.080 --> 00:08:02.749 align:start position:0% magnitude of different scale and so you can<00:08:01.199> understand<00:08:01.319> why<00:08:01.919> maintaining<00:08:02.520> your<00:08:02.639> own 00:08:02.749 --> 00:08:02.759 align:start position:0% can understand why maintaining your own 00:08:02.759 --> 00:08:05.450 align:start position:0% can understand why maintaining your own pgp<00:08:03.300> care<00:08:03.599> or<00:08:04.139> key<00:08:04.319> pair<00:08:04.620> is<00:08:05.039> probably<00:08:05.160> a<00:08:05.340> thing 00:08:05.450 --> 00:08:05.460 align:start position:0% pgp care or key pair is probably a thing 00:08:05.460 --> 00:08:06.409 align:start position:0% pgp care or key pair is probably a thing of<00:08:05.639> the<00:08:05.759> past 00:08:06.409 --> 00:08:06.419 align:start position:0% of the past 00:08:06.419 --> 00:08:08.510 align:start position:0% of the past so<00:08:06.780> if<00:08:06.840> we<00:08:07.020> look<00:08:07.139> at<00:08:07.380> signal<00:08:07.860> and<00:08:07.979> telegram<00:08:08.340> as 00:08:08.510 --> 00:08:08.520 align:start position:0% so if we look at signal and telegram as 00:08:08.520 --> 00:08:10.490 align:start position:0% so if we look at signal and telegram as examples<00:08:08.940> where<00:08:09.240> signal<00:08:09.599> is<00:08:09.780> default<00:08:10.080> antenna 00:08:10.490 --> 00:08:10.500 align:start position:0% examples where signal is default antenna 00:08:10.500 --> 00:08:12.589 align:start position:0% examples where signal is default antenna encrypted<00:08:10.919> using<00:08:11.280> the<00:08:11.400> signal<00:08:11.639> protocol<00:08:12.000> and 00:08:12.589 --> 00:08:12.599 align:start position:0% encrypted using the signal protocol and 00:08:12.599 --> 00:08:14.270 align:start position:0% encrypted using the signal protocol and telegram<00:08:12.900> is<00:08:13.080> n10<00:08:13.380> encrypted<00:08:13.800> using<00:08:14.099> secret 00:08:14.270 --> 00:08:14.280 align:start position:0% telegram is n10 encrypted using secret 00:08:14.280 --> 00:08:15.350 align:start position:0% telegram is n10 encrypted using secret chats 00:08:15.350 --> 00:08:15.360 align:start position:0% chats 00:08:15.360 --> 00:08:18.589 align:start position:0% chats we<00:08:16.020> get<00:08:16.259> so<00:08:16.620> much<00:08:16.800> more<00:08:17.160> privacy<00:08:17.940> built<00:08:18.539> in 00:08:18.589 --> 00:08:18.599 align:start position:0% we get so much more privacy built in 00:08:18.599 --> 00:08:20.869 align:start position:0% we get so much more privacy built in right<00:08:18.840> out<00:08:19.020> of<00:08:19.139> the<00:08:19.259> box<00:08:19.379> so<00:08:20.099> the<00:08:20.400> protocols 00:08:20.869 --> 00:08:20.879 align:start position:0% right out of the box so the protocols 00:08:20.879 --> 00:08:22.610 align:start position:0% right out of the box so the protocols handle<00:08:21.180> all<00:08:21.479> the<00:08:21.599> stuff<00:08:21.720> around<00:08:21.900> key<00:08:22.259> exchange 00:08:22.610 --> 00:08:22.620 align:start position:0% handle all the stuff around key exchange 00:08:22.620 --> 00:08:25.189 align:start position:0% handle all the stuff around key exchange key<00:08:22.979> downloading<00:08:23.520> and<00:08:24.300> actual<00:08:24.660> encryption<00:08:25.020> of 00:08:25.189 --> 00:08:25.199 align:start position:0% key downloading and actual encryption of 00:08:25.199 --> 00:08:27.529 align:start position:0% key downloading and actual encryption of messages<00:08:25.379> and<00:08:26.280> then<00:08:26.340> that<00:08:26.580> leads<00:08:26.879> to<00:08:27.000> you<00:08:27.479> know 00:08:27.529 --> 00:08:27.539 align:start position:0% messages and then that leads to you know 00:08:27.539 --> 00:08:29.330 align:start position:0% messages and then that leads to you know 700<00:08:27.960> million<00:08:28.259> monthly<00:08:28.560> active<00:08:28.860> users<00:08:29.160> on 00:08:29.330 --> 00:08:29.340 align:start position:0% 700 million monthly active users on 00:08:29.340 --> 00:08:32.269 align:start position:0% 700 million monthly active users on Telegram<00:08:29.639> and<00:08:30.120> over<00:08:30.240> 100<00:08:30.419> million<00:08:30.900> on<00:08:31.020> Signal 00:08:32.269 --> 00:08:32.279 align:start position:0% Telegram and over 100 million on Signal 00:08:32.279 --> 00:08:34.430 align:start position:0% Telegram and over 100 million on Signal finally<00:08:32.820> one<00:08:33.180> piece<00:08:33.419> of<00:08:33.539> this<00:08:33.719> that<00:08:34.080> you<00:08:34.320> know 00:08:34.430 --> 00:08:34.440 align:start position:0% finally one piece of this that you know 00:08:34.440 --> 00:08:36.230 align:start position:0% finally one piece of this that you know is<00:08:34.500> somewhat<00:08:34.800> of<00:08:34.919> an<00:08:35.039> advantage<00:08:35.339> but<00:08:35.580> also<00:08:35.940> can 00:08:36.230 --> 00:08:36.240 align:start position:0% is somewhat of an advantage but also can 00:08:36.240 --> 00:08:38.269 align:start position:0% is somewhat of an advantage but also can bite<00:08:36.419> you<00:08:36.599> in<00:08:36.719> the<00:08:36.839> back<00:08:36.899> in<00:08:37.080> the<00:08:37.260> end<00:08:37.380> is<00:08:38.099> a 00:08:38.269 --> 00:08:38.279 align:start position:0% bite you in the back in the end is a 00:08:38.279 --> 00:08:40.430 align:start position:0% bite you in the back in the end is a complex<00:08:38.580> story<00:08:38.940> around<00:08:39.300> key<00:08:39.599> ownership<00:08:39.959> sign 00:08:40.430 --> 00:08:40.440 align:start position:0% complex story around key ownership sign 00:08:40.440 --> 00:08:42.290 align:start position:0% complex story around key ownership sign up<00:08:40.620> and<00:08:40.740> metadata<00:08:41.339> where<00:08:41.700> if<00:08:41.880> you<00:08:41.940> look<00:08:42.060> at<00:08:42.180> a 00:08:42.290 --> 00:08:42.300 align:start position:0% up and metadata where if you look at a 00:08:42.300 --> 00:08:43.730 align:start position:0% up and metadata where if you look at a product<00:08:42.419> like<00:08:42.659> telegram<00:08:43.140> they're<00:08:43.500> often 00:08:43.730 --> 00:08:43.740 align:start position:0% product like telegram they're often 00:08:43.740 --> 00:08:45.170 align:start position:0% product like telegram they're often criticized<00:08:44.159> for<00:08:44.339> not<00:08:44.580> being<00:08:44.700> fully<00:08:45.000> open 00:08:45.170 --> 00:08:45.180 align:start position:0% criticized for not being fully open 00:08:45.180 --> 00:08:47.210 align:start position:0% criticized for not being fully open source<00:08:45.600> even<00:08:46.140> if<00:08:46.320> some<00:08:46.440> of<00:08:46.560> the<00:08:46.620> protocol<00:08:46.920> is 00:08:47.210 --> 00:08:47.220 align:start position:0% source even if some of the protocol is 00:08:47.220 --> 00:08:49.430 align:start position:0% source even if some of the protocol is and<00:08:48.000> Signal<00:08:48.300> often<00:08:48.660> is<00:08:48.779> criticized<00:08:49.260> for 00:08:49.430 --> 00:08:49.440 align:start position:0% and Signal often is criticized for 00:08:49.440 --> 00:08:50.870 align:start position:0% and Signal often is criticized for requiring<00:08:49.800> a<00:08:49.980> phone<00:08:50.100> number<00:08:50.279> on<00:08:50.519> sign<00:08:50.700> up 00:08:50.870 --> 00:08:50.880 align:start position:0% requiring a phone number on sign up 00:08:50.880 --> 00:08:52.370 align:start position:0% requiring a phone number on sign up which<00:08:51.180> for<00:08:51.360> some<00:08:51.480> of<00:08:51.600> us<00:08:51.720> may<00:08:52.019> not<00:08:52.200> matter 00:08:52.370 --> 00:08:52.380 align:start position:0% which for some of us may not matter 00:08:52.380 --> 00:08:54.170 align:start position:0% which for some of us may not matter because<00:08:52.620> we'll<00:08:52.980> you<00:08:53.399> know<00:08:53.519> happily<00:08:53.820> share<00:08:54.060> a 00:08:54.170 --> 00:08:54.180 align:start position:0% because we'll you know happily share a 00:08:54.180 --> 00:08:56.090 align:start position:0% because we'll you know happily share a phone<00:08:54.300> number<00:08:54.480> with<00:08:54.720> friends<00:08:54.899> but<00:08:55.560> for<00:08:55.740> others 00:08:56.090 --> 00:08:56.100 align:start position:0% phone number with friends but for others 00:08:56.100 --> 00:08:57.949 align:start position:0% phone number with friends but for others it<00:08:56.580> can<00:08:56.700> really<00:08:56.820> defeat<00:08:57.240> the<00:08:57.360> purpose<00:08:57.600> of<00:08:57.779> a 00:08:57.949 --> 00:08:57.959 align:start position:0% it can really defeat the purpose of a 00:08:57.959 --> 00:09:03.470 align:start position:0% it can really defeat the purpose of a privacy<00:08:58.260> first<00:08:58.440> messaging<00:08:59.040> product 00:09:03.470 --> 00:09:03.480 align:start position:0% 00:09:03.480 --> 00:09:05.570 align:start position:0% now<00:09:03.959> we'll<00:09:04.140> look<00:09:04.260> at<00:09:04.380> one<00:09:04.620> last<00:09:04.800> piece<00:09:05.160> of<00:09:05.339> the 00:09:05.570 --> 00:09:05.580 align:start position:0% now we'll look at one last piece of the 00:09:05.580 --> 00:09:08.210 align:start position:0% now we'll look at one last piece of the current<00:09:05.820> uh<00:09:06.540> authentication<00:09:07.380> framework<00:09:07.860> so 00:09:08.210 --> 00:09:08.220 align:start position:0% current uh authentication framework so 00:09:08.220 --> 00:09:10.310 align:start position:0% current uh authentication framework so the<00:09:08.399> last<00:09:08.519> is<00:09:08.700> oauth<00:09:09.240> which<00:09:09.720> I<00:09:09.899> think<00:09:10.019> is<00:09:10.140> one 00:09:10.310 --> 00:09:10.320 align:start position:0% the last is oauth which I think is one 00:09:10.320 --> 00:09:12.290 align:start position:0% the last is oauth which I think is one of<00:09:10.380> the<00:09:10.440> most<00:09:10.560> painful<00:09:10.980> uh<00:09:11.700> forms<00:09:12.000> of<00:09:12.180> doing 00:09:12.290 --> 00:09:12.300 align:start position:0% of the most painful uh forms of doing 00:09:12.300 --> 00:09:14.210 align:start position:0% of the most painful uh forms of doing authentication<00:09:12.899> today<00:09:13.200> because<00:09:13.920> it's 00:09:14.210 --> 00:09:14.220 align:start position:0% authentication today because it's 00:09:14.220 --> 00:09:16.370 align:start position:0% authentication today because it's basically<00:09:14.580> putting<00:09:14.940> your<00:09:15.120> identity<00:09:15.540> in<00:09:16.200> the 00:09:16.370 --> 00:09:16.380 align:start position:0% basically putting your identity in the 00:09:16.380 --> 00:09:18.410 align:start position:0% basically putting your identity in the hands<00:09:16.620> of<00:09:16.800> one<00:09:17.160> single<00:09:17.459> server<00:09:17.760> and<00:09:17.940> provider 00:09:18.410 --> 00:09:18.420 align:start position:0% hands of one single server and provider 00:09:18.420 --> 00:09:20.389 align:start position:0% hands of one single server and provider and<00:09:18.899> so<00:09:19.019> whether<00:09:19.200> it's<00:09:19.560> you<00:09:19.920> know<00:09:19.980> your<00:09:20.279> Gmail 00:09:20.389 --> 00:09:20.399 align:start position:0% and so whether it's you know your Gmail 00:09:20.399 --> 00:09:22.490 align:start position:0% and so whether it's you know your Gmail account<00:09:20.760> or<00:09:21.180> another<00:09:21.300> product<00:09:21.660> you've 00:09:22.490 --> 00:09:22.500 align:start position:0% account or another product you've 00:09:22.500 --> 00:09:23.990 align:start position:0% account or another product you've basically<00:09:22.740> made<00:09:22.980> that<00:09:23.220> to<00:09:23.399> you<00:09:23.580> know<00:09:23.700> become 00:09:23.990 --> 00:09:24.000 align:start position:0% basically made that to you know become 00:09:24.000 --> 00:09:26.030 align:start position:0% basically made that to you know become your<00:09:24.240> identity<00:09:24.600> around<00:09:24.839> the<00:09:25.200> web<00:09:25.380> Without 00:09:26.030 --> 00:09:26.040 align:start position:0% your identity around the web Without 00:09:26.040 --> 00:09:27.650 align:start position:0% your identity around the web Without Really<00:09:26.399> knowing<00:09:26.700> that<00:09:26.940> you<00:09:27.060> really<00:09:27.240> own<00:09:27.480> it 00:09:27.650 --> 00:09:27.660 align:start position:0% Really knowing that you really own it 00:09:27.660 --> 00:09:30.290 align:start position:0% Really knowing that you really own it and<00:09:28.140> so<00:09:28.260> the<00:09:28.380> way<00:09:28.500> oauth<00:09:28.920> works<00:09:29.279> is<00:09:29.519> just<00:09:29.940> for<00:09:30.120> a 00:09:30.290 --> 00:09:30.300 align:start position:0% and so the way oauth works is just for a 00:09:30.300 --> 00:09:32.210 align:start position:0% and so the way oauth works is just for a quick<00:09:30.480> overview<00:09:31.080> you<00:09:31.740> know<00:09:31.800> you'll<00:09:32.040> plug 00:09:32.210 --> 00:09:32.220 align:start position:0% quick overview you know you'll plug 00:09:32.220 --> 00:09:34.250 align:start position:0% quick overview you know you'll plug oauth<00:09:32.700> into<00:09:32.820> your<00:09:33.000> app<00:09:33.120> in<00:09:33.360> five<00:09:33.600> minutes<00:09:33.779> you 00:09:34.250 --> 00:09:34.260 align:start position:0% oauth into your app in five minutes you 00:09:34.260 --> 00:09:35.570 align:start position:0% oauth into your app in five minutes you know<00:09:34.320> developers<00:09:34.740> have<00:09:34.920> made<00:09:35.100> that<00:09:35.279> so<00:09:35.459> easy 00:09:35.570 --> 00:09:35.580 align:start position:0% know developers have made that so easy 00:09:35.580 --> 00:09:38.210 align:start position:0% know developers have made that so easy you<00:09:36.120> can<00:09:36.240> query<00:09:36.480> for<00:09:36.779> a<00:09:36.899> scoped<00:09:37.260> token<00:09:37.620> so<00:09:37.980> ask 00:09:38.210 --> 00:09:38.220 align:start position:0% you can query for a scoped token so ask 00:09:38.220 --> 00:09:40.190 align:start position:0% you can query for a scoped token so ask for<00:09:38.399> my<00:09:38.700> birthday<00:09:38.880> or<00:09:39.300> my<00:09:39.540> favorite<00:09:39.660> color<00:09:39.899> or 00:09:40.190 --> 00:09:40.200 align:start position:0% for my birthday or my favorite color or 00:09:40.200 --> 00:09:41.930 align:start position:0% for my birthday or my favorite color or my<00:09:40.380> email<00:09:40.440> address<00:09:40.740> and<00:09:41.580> get<00:09:41.760> back 00:09:41.930 --> 00:09:41.940 align:start position:0% my email address and get back 00:09:41.940 --> 00:09:43.670 align:start position:0% my email address and get back credentials<00:09:42.660> that<00:09:42.839> can<00:09:42.959> be<00:09:43.080> refreshed 00:09:43.670 --> 00:09:43.680 align:start position:0% credentials that can be refreshed 00:09:43.680 --> 00:09:46.009 align:start position:0% credentials that can be refreshed possibly<00:09:44.459> indefinitely<00:09:45.000> for<00:09:45.360> access<00:09:45.540> to<00:09:45.839> an 00:09:46.009 --> 00:09:46.019 align:start position:0% possibly indefinitely for access to an 00:09:46.019 --> 00:09:47.509 align:start position:0% possibly indefinitely for access to an application 00:09:47.509 --> 00:09:47.519 align:start position:0% application 00:09:47.519 --> 00:09:49.670 align:start position:0% application so<00:09:48.420> a<00:09:48.839> lot<00:09:48.959> of<00:09:49.019> these<00:09:49.200> standards<00:09:49.500> have 00:09:49.670 --> 00:09:49.680 align:start position:0% so a lot of these standards have 00:09:49.680 --> 00:09:51.470 align:start position:0% so a lot of these standards have developed<00:09:50.040> as<00:09:50.399> we<00:09:50.580> you<00:09:50.760> know<00:09:50.880> the<00:09:51.060> identity 00:09:51.470 --> 00:09:51.480 align:start position:0% developed as we you know the identity 00:09:51.480 --> 00:09:53.090 align:start position:0% developed as we you know the identity story<00:09:51.839> gets<00:09:52.260> more<00:09:52.440> and<00:09:52.560> more<00:09:52.740> complicated 00:09:53.090 --> 00:09:53.100 align:start position:0% story gets more and more complicated 00:09:53.100 --> 00:09:55.130 align:start position:0% story gets more and more complicated around<00:09:53.339> the<00:09:53.580> web<00:09:53.700> as<00:09:54.300> centralized<00:09:54.720> providers 00:09:55.130 --> 00:09:55.140 align:start position:0% around the web as centralized providers 00:09:55.140 --> 00:09:57.350 align:start position:0% around the web as centralized providers store<00:09:55.380> more<00:09:55.620> information<00:09:55.800> about<00:09:56.220> us<00:09:56.519> and<00:09:57.120> also 00:09:57.350 --> 00:09:57.360 align:start position:0% store more information about us and also 00:09:57.360 --> 00:09:59.090 align:start position:0% store more information about us and also just<00:09:57.480> keep<00:09:57.720> enlarging<00:09:58.200> these<00:09:58.380> scopes<00:09:58.680> of<00:09:58.860> data 00:09:59.090 --> 00:09:59.100 align:start position:0% just keep enlarging these scopes of data 00:09:59.100 --> 00:10:01.790 align:start position:0% just keep enlarging these scopes of data that<00:09:59.220> you<00:09:59.339> could<00:09:59.459> access 00:10:01.790 --> 00:10:01.800 align:start position:0% 00:10:01.800 --> 00:10:03.350 align:start position:0% now<00:10:02.220> we'll<00:10:02.399> just<00:10:02.519> flip<00:10:02.760> the<00:10:02.940> Paradigm 00:10:03.350 --> 00:10:03.360 align:start position:0% now we'll just flip the Paradigm 00:10:03.360 --> 00:10:04.730 align:start position:0% now we'll just flip the Paradigm completely<00:10:03.660> on<00:10:03.839> its<00:10:04.080> head 00:10:04.730 --> 00:10:04.740 align:start position:0% completely on its head 00:10:04.740 --> 00:10:07.070 align:start position:0% completely on its head we<00:10:05.100> at<00:10:05.279> skip<00:10:05.459> think<00:10:05.700> wallets<00:10:06.120> are<00:10:06.420> just<00:10:06.600> a 00:10:07.070 --> 00:10:07.080 align:start position:0% we at skip think wallets are just a 00:10:07.080 --> 00:10:09.050 align:start position:0% we at skip think wallets are just a natural<00:10:07.320> successor<00:10:07.920> to<00:10:08.100> this<00:10:08.279> problem<00:10:08.459> across 00:10:09.050 --> 00:10:09.060 align:start position:0% natural successor to this problem across 00:10:09.060 --> 00:10:10.850 align:start position:0% natural successor to this problem across encryption<00:10:09.480> across<00:10:09.899> identity<00:10:10.260> and<00:10:10.500> across 00:10:10.850 --> 00:10:10.860 align:start position:0% encryption across identity and across 00:10:10.860 --> 00:10:12.110 align:start position:0% encryption across identity and across data<00:10:11.100> ownership 00:10:12.110 --> 00:10:12.120 align:start position:0% data ownership 00:10:12.120 --> 00:10:14.150 align:start position:0% data ownership so<00:10:12.480> we've<00:10:12.720> actually<00:10:12.839> seen<00:10:13.260> wallets<00:10:13.800> start<00:10:13.980> to 00:10:14.150 --> 00:10:14.160 align:start position:0% so we've actually seen wallets start to 00:10:14.160 --> 00:10:15.769 align:start position:0% so we've actually seen wallets start to be<00:10:14.279> used<00:10:14.459> as<00:10:14.760> the<00:10:14.880> basis<00:10:15.180> for<00:10:15.360> generating 00:10:15.769 --> 00:10:15.779 align:start position:0% be used as the basis for generating 00:10:15.779 --> 00:10:17.750 align:start position:0% be used as the basis for generating end-to-encrypted<00:10:16.620> key<00:10:16.800> Pairs<00:10:17.160> and<00:10:17.519> so<00:10:17.640> if 00:10:17.750 --> 00:10:17.760 align:start position:0% end-to-encrypted key Pairs and so if 00:10:17.760 --> 00:10:20.210 align:start position:0% end-to-encrypted key Pairs and so if you're<00:10:17.880> familiar<00:10:18.240> with<00:10:18.600> the<00:10:19.380> method<00:10:19.680> eth<00:10:20.040> get 00:10:20.210 --> 00:10:20.220 align:start position:0% you're familiar with the method eth get 00:10:20.220 --> 00:10:22.070 align:start position:0% you're familiar with the method eth get encryption<00:10:20.580> public<00:10:20.820> key<00:10:21.060> this<00:10:21.839> is<00:10:21.959> actually 00:10:22.070 --> 00:10:22.080 align:start position:0% encryption public key this is actually 00:10:22.080 --> 00:10:23.750 align:start position:0% encryption public key this is actually an<00:10:22.320> Innovative<00:10:22.620> thing<00:10:22.860> published<00:10:23.339> by<00:10:23.459> the 00:10:23.750 --> 00:10:23.760 align:start position:0% an Innovative thing published by the 00:10:23.760 --> 00:10:25.130 align:start position:0% an Innovative thing published by the metamask<00:10:24.180> community<00:10:24.480> and<00:10:24.839> then<00:10:24.959> later 00:10:25.130 --> 00:10:25.140 align:start position:0% metamask community and then later 00:10:25.140 --> 00:10:27.170 align:start position:0% metamask community and then later adopted<00:10:25.620> into<00:10:25.740> Brave<00:10:26.100> wallet<00:10:26.519> where<00:10:27.000> you'll 00:10:27.170 --> 00:10:27.180 align:start position:0% adopted into Brave wallet where you'll 00:10:27.180 --> 00:10:29.269 align:start position:0% adopted into Brave wallet where you'll turn<00:10:27.420> an<00:10:27.600> ethereum<00:10:28.080> public<00:10:28.380> key<00:10:28.680> or<00:10:28.860> ethereum 00:10:29.269 --> 00:10:29.279 align:start position:0% turn an ethereum public key or ethereum 00:10:29.279 --> 00:10:32.930 align:start position:0% turn an ethereum public key or ethereum key<00:10:29.519> pair<00:10:29.820> into<00:10:30.600> a<00:10:31.019> curve<00:10:31.399> 25519<00:10:32.399> encryption 00:10:32.930 --> 00:10:32.940 align:start position:0% key pair into a curve 25519 encryption 00:10:32.940 --> 00:10:34.670 align:start position:0% key pair into a curve 25519 encryption key<00:10:33.120> pair<00:10:33.360> which<00:10:33.899> can<00:10:34.080> be<00:10:34.200> used<00:10:34.320> to<00:10:34.500> just 00:10:34.670 --> 00:10:34.680 align:start position:0% key pair which can be used to just 00:10:34.680 --> 00:10:36.170 align:start position:0% key pair which can be used to just encrypt<00:10:35.040> and<00:10:35.160> decrypt<00:10:35.580> data<00:10:35.820> with<00:10:36.060> your 00:10:36.170 --> 00:10:36.180 align:start position:0% encrypt and decrypt data with your 00:10:36.180 --> 00:10:37.910 align:start position:0% encrypt and decrypt data with your metamask<00:10:36.540> or<00:10:36.720> Brave<00:10:36.959> wallet 00:10:37.910 --> 00:10:37.920 align:start position:0% metamask or Brave wallet 00:10:37.920 --> 00:10:39.590 align:start position:0% metamask or Brave wallet uh<00:10:38.459> there's<00:10:38.640> a<00:10:38.760> bit<00:10:38.880> of<00:10:39.000> complication<00:10:39.360> around 00:10:39.590 --> 00:10:39.600 align:start position:0% uh there's a bit of complication around 00:10:39.600 --> 00:10:41.030 align:start position:0% uh there's a bit of complication around that<00:10:39.839> as<00:10:40.080> some<00:10:40.260> of<00:10:40.320> the<00:10:40.380> cryptography<00:10:40.920> is 00:10:41.030 --> 00:10:41.040 align:start position:0% that as some of the cryptography is 00:10:41.040 --> 00:10:43.070 align:start position:0% that as some of the cryptography is ironed<00:10:41.459> out<00:10:41.580> but<00:10:41.940> it's<00:10:42.120> this<00:10:42.420> much<00:10:42.720> more 00:10:43.070 --> 00:10:43.080 align:start position:0% ironed out but it's this much more 00:10:43.080 --> 00:10:45.530 align:start position:0% ironed out but it's this much more simple<00:10:43.440> and<00:10:43.740> intuitive<00:10:44.160> way<00:10:44.399> of<00:10:44.940> going<00:10:45.120> from<00:10:45.360> a 00:10:45.530 --> 00:10:45.540 align:start position:0% simple and intuitive way of going from a 00:10:45.540 --> 00:10:47.569 align:start position:0% simple and intuitive way of going from a key<00:10:45.720> that<00:10:45.959> you<00:10:46.079> own<00:10:46.260> to<00:10:46.740> an<00:10:46.920> entire<00:10:47.220> framework 00:10:47.569 --> 00:10:47.579 align:start position:0% key that you own to an entire framework 00:10:47.579 --> 00:10:49.850 align:start position:0% key that you own to an entire framework for<00:10:47.820> end-10<00:10:48.120> encryption 00:10:49.850 --> 00:10:49.860 align:start position:0% for end-10 encryption 00:10:49.860 --> 00:10:51.769 align:start position:0% for end-10 encryption instead<00:10:50.399> of<00:10:50.519> access<00:10:50.700> grants<00:10:51.180> we'll<00:10:51.420> where 00:10:51.769 --> 00:10:51.779 align:start position:0% instead of access grants we'll where 00:10:51.779 --> 00:10:53.750 align:start position:0% instead of access grants we'll where we'll<00:10:52.019> ask<00:10:52.260> Google<00:10:52.560> or<00:10:52.800> a<00:10:52.980> provider<00:10:53.339> for<00:10:53.579> more 00:10:53.750 --> 00:10:53.760 align:start position:0% we'll ask Google or a provider for more 00:10:53.760 --> 00:10:55.490 align:start position:0% we'll ask Google or a provider for more data<00:10:54.120> all<00:10:54.779> of<00:10:54.899> this<00:10:55.019> will<00:10:55.200> be<00:10:55.320> super 00:10:55.490 --> 00:10:55.500 align:start position:0% data all of this will be super 00:10:55.500 --> 00:10:57.230 align:start position:0% data all of this will be super transparent<00:10:56.100> to<00:10:56.220> users<00:10:56.459> where<00:10:56.700> you<00:10:56.880> sign<00:10:57.060> a 00:10:57.230 --> 00:10:57.240 align:start position:0% transparent to users where you sign a 00:10:57.240 --> 00:10:58.910 align:start position:0% transparent to users where you sign a token<00:10:57.540> giving<00:10:57.839> access<00:10:58.079> or<00:10:58.440> authenticating 00:10:58.910 --> 00:10:58.920 align:start position:0% token giving access or authenticating 00:10:58.920 --> 00:11:00.710 align:start position:0% token giving access or authenticating exactly<00:10:59.459> what<00:10:59.579> you<00:10:59.760> want<00:10:59.880> or<00:11:00.060> exactly<00:11:00.420> who<00:11:00.540> you 00:11:00.710 --> 00:11:00.720 align:start position:0% exactly what you want or exactly who you 00:11:00.720 --> 00:11:01.430 align:start position:0% exactly what you want or exactly who you are 00:11:01.430 --> 00:11:01.440 align:start position:0% are 00:11:01.440 --> 00:11:03.050 align:start position:0% are and<00:11:01.740> then<00:11:01.920> finally<00:11:02.220> on<00:11:02.519> the<00:11:02.640> distribute 00:11:03.050 --> 00:11:03.060 align:start position:0% and then finally on the distribute 00:11:03.060 --> 00:11:05.509 align:start position:0% and then finally on the distribute distributed<00:11:03.779> public<00:11:03.959> key<00:11:04.200> directory<00:11:04.740> I<00:11:05.399> think 00:11:05.509 --> 00:11:05.519 align:start position:0% distributed public key directory I think 00:11:05.519 --> 00:11:07.190 align:start position:0% distributed public key directory I think no<00:11:05.760> one<00:11:05.880> here<00:11:06.060> wants<00:11:06.420> to<00:11:06.480> put<00:11:06.600> up<00:11:06.720> one<00:11:06.959> of<00:11:07.079> those 00:11:07.190 --> 00:11:07.200 align:start position:0% no one here wants to put up one of those 00:11:07.200 --> 00:11:10.069 align:start position:0% no one here wants to put up one of those you<00:11:07.560> know<00:11:07.620> HTML<00:11:08.220> only<00:11:08.519> personal<00:11:09.300> pages<00:11:09.720> with 00:11:10.069 --> 00:11:10.079 align:start position:0% you know HTML only personal pages with 00:11:10.079 --> 00:11:12.230 align:start position:0% you know HTML only personal pages with your<00:11:10.260> pgp<00:11:10.680> key<00:11:10.920> and<00:11:11.399> then<00:11:11.519> just<00:11:11.700> expect<00:11:11.880> people 00:11:12.230 --> 00:11:12.240 align:start position:0% your pgp key and then just expect people 00:11:12.240 --> 00:11:13.490 align:start position:0% your pgp key and then just expect people to<00:11:12.480> go<00:11:12.600> to<00:11:12.720> that<00:11:12.839> if<00:11:13.079> they<00:11:13.200> want<00:11:13.380> to 00:11:13.490 --> 00:11:13.500 align:start position:0% to go to that if they want to 00:11:13.500 --> 00:11:15.530 align:start position:0% to go to that if they want to communicate<00:11:13.860> securely<00:11:14.220> with<00:11:14.519> you<00:11:14.640> with 00:11:15.530 --> 00:11:15.540 align:start position:0% communicate securely with you with 00:11:15.540 --> 00:11:17.090 align:start position:0% communicate securely with you with wallets<00:11:15.959> and<00:11:16.200> things<00:11:16.380> like<00:11:16.500> naming<00:11:16.860> Services 00:11:17.090 --> 00:11:17.100 align:start position:0% wallets and things like naming Services 00:11:17.100 --> 00:11:19.610 align:start position:0% wallets and things like naming Services we<00:11:18.000> get<00:11:18.120> a<00:11:18.300> much<00:11:18.420> simpler<00:11:18.779> way<00:11:18.959> of<00:11:19.200> going<00:11:19.320> from 00:11:19.610 --> 00:11:19.620 align:start position:0% we get a much simpler way of going from 00:11:19.620 --> 00:11:22.430 align:start position:0% we get a much simpler way of going from a<00:11:19.740> human<00:11:19.860> readable<00:11:20.279> name<00:11:20.519> like<00:11:20.880> skip.eth<00:11:21.660> to<00:11:22.200> a 00:11:22.430 --> 00:11:22.440 align:start position:0% a human readable name like skip.eth to a 00:11:22.440 --> 00:11:24.110 align:start position:0% a human readable name like skip.eth to a public<00:11:22.560> key<00:11:22.800> and<00:11:23.100> we<00:11:23.220> have<00:11:23.279> some<00:11:23.459> people<00:11:23.640> from 00:11:24.110 --> 00:11:24.120 align:start position:0% public key and we have some people from 00:11:24.120 --> 00:11:26.509 align:start position:0% public key and we have some people from the<00:11:24.720> dm3<00:11:25.140> team<00:11:25.380> here<00:11:25.620> who<00:11:25.920> are<00:11:26.040> working<00:11:26.220> on 00:11:26.509 --> 00:11:26.519 align:start position:0% the dm3 team here who are working on 00:11:26.519 --> 00:11:28.550 align:start position:0% the dm3 team here who are working on that<00:11:27.180> exact<00:11:27.420> problem 00:11:28.550 --> 00:11:28.560 align:start position:0% that exact problem 00:11:28.560 --> 00:11:30.350 align:start position:0% that exact problem uh<00:11:28.980> we'll<00:11:29.160> talk<00:11:29.339> about<00:11:29.459> this<00:11:29.640> more<00:11:29.760> later<00:11:30.000> but 00:11:30.350 --> 00:11:30.360 align:start position:0% uh we'll talk about this more later but 00:11:30.360 --> 00:11:31.910 align:start position:0% uh we'll talk about this more later but it<00:11:30.480> does<00:11:30.660> introduce<00:11:31.200> some<00:11:31.380> problems<00:11:31.620> on<00:11:31.860> the 00:11:31.910 --> 00:11:31.920 align:start position:0% it does introduce some problems on the 00:11:31.920 --> 00:11:34.370 align:start position:0% it does introduce some problems on the consumer<00:11:32.339> side<00:11:32.519> with<00:11:33.240> recovery<00:11:33.839> and 00:11:34.370 --> 00:11:34.380 align:start position:0% consumer side with recovery and 00:11:34.380 --> 00:11:36.170 align:start position:0% consumer side with recovery and basically<00:11:34.680> account<00:11:34.920> reset<00:11:35.459> as<00:11:35.820> we<00:11:35.940> all<00:11:36.060> know 00:11:36.170 --> 00:11:36.180 align:start position:0% basically account reset as we all know 00:11:36.180 --> 00:11:38.030 align:start position:0% basically account reset as we all know and<00:11:36.360> using<00:11:36.660> a<00:11:36.779> wallet 00:11:38.030 --> 00:11:38.040 align:start position:0% and using a wallet 00:11:38.040 --> 00:11:39.769 align:start position:0% and using a wallet so<00:11:38.339> just<00:11:38.459> to<00:11:38.640> recap<00:11:38.880> what's<00:11:39.180> this<00:11:39.360> new<00:11:39.600> model 00:11:39.769 --> 00:11:39.779 align:start position:0% so just to recap what's this new model 00:11:39.779 --> 00:11:41.750 align:start position:0% so just to recap what's this new model for<00:11:40.019> authentication<00:11:40.620> we'll<00:11:41.279> start<00:11:41.519> with<00:11:41.640> a 00:11:41.750 --> 00:11:41.760 align:start position:0% for authentication we'll start with a 00:11:41.760 --> 00:11:43.610 align:start position:0% for authentication we'll start with a human<00:11:41.880> readable<00:11:42.300> name<00:11:42.540> like<00:11:43.019> you<00:11:43.440> know<00:11:43.500> an 00:11:43.610 --> 00:11:43.620 align:start position:0% human readable name like you know an 00:11:43.620 --> 00:11:45.889 align:start position:0% human readable name like you know an email<00:11:43.800> address<00:11:44.040> or<00:11:44.339> even<00:11:44.459> simpler<00:11:44.940> we'll<00:11:45.660> take 00:11:45.889 --> 00:11:45.899 align:start position:0% email address or even simpler we'll take 00:11:45.899 --> 00:11:47.210 align:start position:0% email address or even simpler we'll take that<00:11:46.079> and<00:11:46.200> transform<00:11:46.500> it<00:11:46.680> to<00:11:46.800> a<00:11:46.920> wallet 00:11:47.210 --> 00:11:47.220 align:start position:0% that and transform it to a wallet 00:11:47.220 --> 00:11:48.650 align:start position:0% that and transform it to a wallet address<00:11:47.339> which<00:11:47.760> is<00:11:47.820> done<00:11:48.060> using<00:11:48.480> a 00:11:48.650 --> 00:11:48.660 align:start position:0% address which is done using a 00:11:48.660 --> 00:11:51.290 align:start position:0% address which is done using a transparent<00:11:49.200> on-chain<00:11:49.860> lookup<00:11:50.459> and<00:11:51.180> then 00:11:51.290 --> 00:11:51.300 align:start position:0% transparent on-chain lookup and then 00:11:51.300 --> 00:11:53.210 align:start position:0% transparent on-chain lookup and then finally<00:11:51.660> we'll<00:11:51.959> recover<00:11:52.260> a<00:11:52.500> public<00:11:52.680> key<00:11:52.920> from 00:11:53.210 --> 00:11:53.220 align:start position:0% finally we'll recover a public key from 00:11:53.220 --> 00:11:55.130 align:start position:0% finally we'll recover a public key from that<00:11:53.459> and<00:11:53.940> so<00:11:54.120> in<00:11:54.240> certain<00:11:54.420> cases<00:11:54.720> we'll<00:11:54.959> get 00:11:55.130 --> 00:11:55.140 align:start position:0% that and so in certain cases we'll get 00:11:55.140 --> 00:11:57.769 align:start position:0% that and so in certain cases we'll get back<00:11:55.320> an<00:11:55.560> ethereum<00:11:56.040> key<00:11:56.339> pair<00:11:56.640> or<00:11:57.240> in<00:11:57.360> others 00:11:57.769 --> 00:11:57.779 align:start position:0% back an ethereum key pair or in others 00:11:57.779 --> 00:11:59.870 align:start position:0% back an ethereum key pair or in others like<00:11:58.079> that<00:11:58.320> uh<00:11:58.800> kind<00:11:59.040> of<00:11:59.100> experimental<00:11:59.640> method 00:11:59.870 --> 00:11:59.880 align:start position:0% like that uh kind of experimental method 00:11:59.880 --> 00:12:01.610 align:start position:0% like that uh kind of experimental method I<00:12:00.060> talked<00:12:00.300> about<00:12:00.360> we<00:12:01.019> could<00:12:01.140> actually<00:12:01.320> figure 00:12:01.610 --> 00:12:01.620 align:start position:0% I talked about we could actually figure 00:12:01.620 --> 00:12:03.590 align:start position:0% I talked about we could actually figure out<00:12:01.800> a<00:12:01.980> way<00:12:02.100> to<00:12:02.339> get<00:12:02.519> a<00:12:02.940> really<00:12:03.060> well<00:12:03.240> suited 00:12:03.590 --> 00:12:03.600 align:start position:0% out a way to get a really well suited 00:12:03.600 --> 00:12:05.269 align:start position:0% out a way to get a really well suited encryption<00:12:04.019> key<00:12:04.200> pair<00:12:04.380> to<00:12:04.740> send<00:12:04.860> data<00:12:05.160> to 00:12:05.269 --> 00:12:05.279 align:start position:0% encryption key pair to send data to 00:12:05.279 --> 00:12:07.490 align:start position:0% encryption key pair to send data to people<00:12:05.459> end-to-end<00:12:06.060> encrypted<00:12:06.480> so<00:12:07.140> now<00:12:07.320> we'll 00:12:07.490 --> 00:12:07.500 align:start position:0% people end-to-end encrypted so now we'll 00:12:07.500 --> 00:12:09.410 align:start position:0% people end-to-end encrypted so now we'll go<00:12:07.680> we'll<00:12:07.980> kind<00:12:08.220> of<00:12:08.339> completely<00:12:08.880> erase<00:12:09.240> the 00:12:09.410 --> 00:12:09.420 align:start position:0% go we'll kind of completely erase the 00:12:09.420 --> 00:12:11.930 align:start position:0% go we'll kind of completely erase the pgp<00:12:09.899> stack<00:12:10.200> We'll<00:12:10.380> erase<00:12:10.680> oauth<00:12:11.220> and<00:12:11.579> we'll<00:12:11.700> go 00:12:11.930 --> 00:12:11.940 align:start position:0% pgp stack We'll erase oauth and we'll go 00:12:11.940 --> 00:12:13.730 align:start position:0% pgp stack We'll erase oauth and we'll go from<00:12:12.240> this<00:12:12.540> you<00:12:12.839> know<00:12:12.899> human<00:12:13.079> readable<00:12:13.500> name 00:12:13.730 --> 00:12:13.740 align:start position:0% from this you know human readable name 00:12:13.740 --> 00:12:15.949 align:start position:0% from this you know human readable name all<00:12:14.279> the<00:12:14.459> way<00:12:14.519> to<00:12:14.700> n10<00:12:15.000> encryption<00:12:15.480> much 00:12:15.949 --> 00:12:15.959 align:start position:0% all the way to n10 encryption much 00:12:15.959 --> 00:12:17.389 align:start position:0% all the way to n10 encryption much easier<00:12:16.260> than<00:12:16.440> signal<00:12:16.800> much<00:12:17.100> easier<00:12:17.279> than 00:12:17.389 --> 00:12:17.399 align:start position:0% easier than signal much easier than 00:12:17.399 --> 00:12:20.150 align:start position:0% easier than signal much easier than Telegram<00:12:17.880> and<00:12:18.720> so<00:12:19.019> much<00:12:19.140> easier<00:12:19.440> than<00:12:19.620> pgp 00:12:20.150 --> 00:12:20.160 align:start position:0% Telegram and so much easier than pgp 00:12:20.160 --> 00:12:23.509 align:start position:0% Telegram and so much easier than pgp which<00:12:20.519> is<00:12:20.579> why<00:12:20.820> people<00:12:21.000> don't<00:12:21.300> use<00:12:21.720> it 00:12:23.509 --> 00:12:23.519 align:start position:0% which is why people don't use it 00:12:23.519 --> 00:12:24.769 align:start position:0% which is why people don't use it um so<00:12:23.700> then<00:12:23.820> we'll<00:12:24.000> just<00:12:24.120> cover<00:12:24.300> some<00:12:24.600> about 00:12:24.769 --> 00:12:24.779 align:start position:0% um so then we'll just cover some about 00:12:24.779 --> 00:12:26.870 align:start position:0% um so then we'll just cover some about storage<00:12:25.440> and<00:12:25.740> interoperability<00:12:26.399> a<00:12:26.760> little 00:12:26.870 --> 00:12:26.880 align:start position:0% storage and interoperability a little 00:12:26.880 --> 00:12:29.870 align:start position:0% storage and interoperability a little more<00:12:27.000> on<00:12:27.180> the<00:12:27.300> technical<00:12:27.600> side 00:12:29.870 --> 00:12:29.880 align:start position:0% 00:12:29.880 --> 00:12:32.090 align:start position:0% so<00:12:30.360> this<00:12:30.720> is<00:12:30.779> a<00:12:30.899> point<00:12:31.019> that<00:12:31.320> I've<00:12:31.500> made<00:12:31.800> a<00:12:31.980> lot 00:12:32.090 --> 00:12:32.100 align:start position:0% so this is a point that I've made a lot 00:12:32.100 --> 00:12:34.190 align:start position:0% so this is a point that I've made a lot but<00:12:32.399> I<00:12:32.519> think<00:12:32.640> is<00:12:32.880> pretty<00:12:33.180> intuitive<00:12:33.600> as<00:12:33.839> well 00:12:34.190 --> 00:12:34.200 align:start position:0% but I think is pretty intuitive as well 00:12:34.200 --> 00:12:35.870 align:start position:0% but I think is pretty intuitive as well if<00:12:34.800> we're<00:12:34.920> moving<00:12:35.160> to<00:12:35.339> a<00:12:35.519> world<00:12:35.640> where 00:12:35.870 --> 00:12:35.880 align:start position:0% if we're moving to a world where 00:12:35.880 --> 00:12:37.670 align:start position:0% if we're moving to a world where decentralized<00:12:36.540> storage<00:12:36.720> actually<00:12:37.200> works<00:12:37.620> for 00:12:37.670 --> 00:12:37.680 align:start position:0% decentralized storage actually works for 00:12:37.680 --> 00:12:40.430 align:start position:0% decentralized storage actually works for products<00:12:38.100> we<00:12:38.459> also<00:12:38.700> need<00:12:38.880> n10<00:12:39.300> encryption<00:12:39.839> if 00:12:40.430 --> 00:12:40.440 align:start position:0% products we also need n10 encryption if 00:12:40.440 --> 00:12:41.930 align:start position:0% products we also need n10 encryption if you're<00:12:40.560> storing<00:12:40.860> data<00:12:41.100> on<00:12:41.279> a<00:12:41.399> decentralized 00:12:41.930 --> 00:12:41.940 align:start position:0% you're storing data on a decentralized 00:12:41.940 --> 00:12:43.310 align:start position:0% you're storing data on a decentralized network<00:12:42.120> you<00:12:42.660> wouldn't<00:12:42.720> want<00:12:42.899> to<00:12:43.019> store<00:12:43.139> it 00:12:43.310 --> 00:12:43.320 align:start position:0% network you wouldn't want to store it 00:12:43.320 --> 00:12:44.990 align:start position:0% network you wouldn't want to store it all<00:12:43.440> in<00:12:43.560> plain<00:12:43.740> text<00:12:43.980> you<00:12:44.399> know<00:12:44.519> I<00:12:44.639> write<00:12:44.820> a 00:12:44.990 --> 00:12:45.000 align:start position:0% all in plain text you know I write a 00:12:45.000 --> 00:12:47.569 align:start position:0% all in plain text you know I write a note<00:12:45.180> I<00:12:45.660> write<00:12:45.839> my<00:12:46.139> PhD<00:12:46.560> thesis<00:12:47.040> I<00:12:47.519> don't 00:12:47.569 --> 00:12:47.579 align:start position:0% note I write my PhD thesis I don't 00:12:47.579 --> 00:12:49.190 align:start position:0% note I write my PhD thesis I don't always<00:12:47.820> want<00:12:48.120> every<00:12:48.360> single<00:12:48.660> draft<00:12:48.779> of<00:12:49.079> that 00:12:49.190 --> 00:12:49.200 align:start position:0% always want every single draft of that 00:12:49.200 --> 00:12:50.750 align:start position:0% always want every single draft of that to<00:12:49.380> just<00:12:49.500> be<00:12:49.680> stored<00:12:50.040> you<00:12:50.279> know<00:12:50.339> sharded 00:12:50.750 --> 00:12:50.760 align:start position:0% to just be stored you know sharded 00:12:50.760 --> 00:12:52.790 align:start position:0% to just be stored you know sharded around<00:12:50.880> the<00:12:51.060> internet<00:12:51.180> in<00:12:51.540> plain<00:12:51.779> text<00:12:51.959> so 00:12:52.790 --> 00:12:52.800 align:start position:0% around the internet in plain text so 00:12:52.800 --> 00:12:54.530 align:start position:0% around the internet in plain text so instead<00:12:53.100> I<00:12:53.220> want<00:12:53.399> that<00:12:53.519> to<00:12:53.639> be<00:12:53.760> encrypted<00:12:54.240> and 00:12:54.530 --> 00:12:54.540 align:start position:0% instead I want that to be encrypted and 00:12:54.540 --> 00:12:56.030 align:start position:0% instead I want that to be encrypted and I<00:12:54.660> don't<00:12:54.779> want<00:12:54.899> that<00:12:55.019> to<00:12:55.200> be<00:12:55.260> encrypted<00:12:55.680> with 00:12:56.030 --> 00:12:56.040 align:start position:0% I don't want that to be encrypted with 00:12:56.040 --> 00:12:57.769 align:start position:0% I don't want that to be encrypted with some<00:12:56.339> random<00:12:56.700> person's<00:12:57.060> key<00:12:57.180> I<00:12:57.420> want<00:12:57.540> it<00:12:57.660> to<00:12:57.720> be 00:12:57.769 --> 00:12:57.779 align:start position:0% some random person's key I want it to be 00:12:57.779 --> 00:12:59.569 align:start position:0% some random person's key I want it to be encrypted<00:12:58.139> with<00:12:58.260> my<00:12:58.500> key<00:12:58.740> and<00:12:59.100> that's<00:12:59.279> exactly 00:12:59.569 --> 00:12:59.579 align:start position:0% encrypted with my key and that's exactly 00:12:59.579 --> 00:13:01.850 align:start position:0% encrypted with my key and that's exactly what<00:12:59.700> n10<00:13:00.000> encryption<00:13:00.480> means<00:13:00.779> so<00:13:01.500> to<00:13:01.680> get 00:13:01.850 --> 00:13:01.860 align:start position:0% what n10 encryption means so to get 00:13:01.860 --> 00:13:03.650 align:start position:0% what n10 encryption means so to get basically<00:13:02.220> this<00:13:02.519> value<00:13:02.700> alignment<00:13:03.240> across 00:13:03.650 --> 00:13:03.660 align:start position:0% basically this value alignment across 00:13:03.660 --> 00:13:05.329 align:start position:0% basically this value alignment across end-to-end<00:13:04.079> encryption<00:13:04.440> and<00:13:04.680> decentralized 00:13:05.329 --> 00:13:05.339 align:start position:0% end-to-end encryption and decentralized 00:13:05.339 --> 00:13:07.129 align:start position:0% end-to-end encryption and decentralized storage<00:13:05.519> wallets<00:13:06.480> are<00:13:06.660> an<00:13:06.839> excellent 00:13:07.129 --> 00:13:07.139 align:start position:0% storage wallets are an excellent 00:13:07.139 --> 00:13:08.629 align:start position:0% storage wallets are an excellent solution<00:13:07.440> for<00:13:07.740> that 00:13:08.629 --> 00:13:08.639 align:start position:0% solution for that 00:13:08.639 --> 00:13:10.190 align:start position:0% solution for that and<00:13:09.120> then<00:13:09.240> once<00:13:09.480> you've<00:13:09.660> actually<00:13:09.779> published 00:13:10.190 --> 00:13:10.200 align:start position:0% and then once you've actually published 00:13:10.200 --> 00:13:12.170 align:start position:0% and then once you've actually published things<00:13:10.380> to<00:13:10.620> a<00:13:10.740> decentralized<00:13:11.279> network<00:13:11.459> you 00:13:12.170 --> 00:13:12.180 align:start position:0% things to a decentralized network you 00:13:12.180 --> 00:13:13.910 align:start position:0% things to a decentralized network you can<00:13:12.300> use<00:13:12.480> that<00:13:12.720> Network<00:13:12.899> to<00:13:13.320> query<00:13:13.560> for<00:13:13.800> it 00:13:13.910 --> 00:13:13.920 align:start position:0% can use that Network to query for it 00:13:13.920 --> 00:13:16.129 align:start position:0% can use that Network to query for it maintain<00:13:14.399> a<00:13:14.579> list<00:13:14.700> of<00:13:14.820> identifiers<00:13:15.480> and<00:13:15.959> have 00:13:16.129 --> 00:13:16.139 align:start position:0% maintain a list of identifiers and have 00:13:16.139 --> 00:13:17.990 align:start position:0% maintain a list of identifiers and have permanent<00:13:16.560> access<00:13:16.800> to<00:13:17.100> that<00:13:17.220> outside<00:13:17.579> of<00:13:17.880> any 00:13:17.990 --> 00:13:18.000 align:start position:0% permanent access to that outside of any 00:13:18.000 --> 00:13:19.970 align:start position:0% permanent access to that outside of any sort<00:13:18.180> of<00:13:18.300> platform<00:13:18.660> which<00:13:19.200> gets<00:13:19.560> back<00:13:19.620> to<00:13:19.800> that 00:13:19.970 --> 00:13:19.980 align:start position:0% sort of platform which gets back to that 00:13:19.980 --> 00:13:23.269 align:start position:0% sort of platform which gets back to that importance<00:13:20.339> of<00:13:20.519> censorship<00:13:21.000> resistance 00:13:23.269 --> 00:13:23.279 align:start position:0% importance of censorship resistance 00:13:23.279 --> 00:13:24.949 align:start position:0% importance of censorship resistance then<00:13:23.639> we'll<00:13:23.760> also<00:13:24.060> just<00:13:24.120> talk<00:13:24.300> about<00:13:24.420> the<00:13:24.660> data 00:13:24.949 --> 00:13:24.959 align:start position:0% then we'll also just talk about the data 00:13:24.959 --> 00:13:27.110 align:start position:0% then we'll also just talk about the data structures<00:13:25.320> let's<00:13:26.160> say<00:13:26.279> you're<00:13:26.519> now<00:13:26.700> using<00:13:27.000> an 00:13:27.110 --> 00:13:27.120 align:start position:0% structures let's say you're now using an 00:13:27.120 --> 00:13:28.910 align:start position:0% structures let's say you're now using an n10<00:13:27.420> encrypted<00:13:27.899> product<00:13:28.019> that<00:13:28.380> has<00:13:28.560> no<00:13:28.740> access 00:13:28.910 --> 00:13:28.920 align:start position:0% n10 encrypted product that has no access 00:13:28.920 --> 00:13:30.290 align:start position:0% n10 encrypted product that has no access to<00:13:29.220> the<00:13:29.339> things<00:13:29.519> that<00:13:29.700> you're<00:13:29.820> writing<00:13:30.120> you're 00:13:30.290 --> 00:13:30.300 align:start position:0% to the things that you're writing you're 00:13:30.300 --> 00:13:32.569 align:start position:0% to the things that you're writing you're typing<00:13:30.600> your<00:13:30.839> notes<00:13:31.079> your<00:13:31.260> documents<00:13:31.800> all<00:13:32.519> of 00:13:32.569 --> 00:13:32.579 align:start position:0% typing your notes your documents all of 00:13:32.579 --> 00:13:34.190 align:start position:0% typing your notes your documents all of a<00:13:32.639> sudden<00:13:32.820> you<00:13:33.120> can't<00:13:33.180> use<00:13:33.420> a<00:13:33.660> single<00:13:33.899> server 00:13:34.190 --> 00:13:34.200 align:start position:0% a sudden you can't use a single server 00:13:34.200 --> 00:13:36.650 align:start position:0% a sudden you can't use a single server like<00:13:34.560> the<00:13:34.800> Google<00:13:34.980> model<00:13:35.339> or<00:13:36.000> you<00:13:36.480> know<00:13:36.540> the 00:13:36.650 --> 00:13:36.660 align:start position:0% like the Google model or you know the 00:13:36.660 --> 00:13:38.569 align:start position:0% like the Google model or you know the centralized<00:13:37.139> model<00:13:37.320> of<00:13:37.500> collaborating<00:13:37.980> you 00:13:38.569 --> 00:13:38.579 align:start position:0% centralized model of collaborating you 00:13:38.579 --> 00:13:40.190 align:start position:0% centralized model of collaborating you have<00:13:38.700> to<00:13:38.820> use<00:13:39.000> a<00:13:39.240> new<00:13:39.300> set<00:13:39.480> of<00:13:39.600> data<00:13:39.899> structures 00:13:40.190 --> 00:13:40.200 align:start position:0% have to use a new set of data structures 00:13:40.200 --> 00:13:41.990 align:start position:0% have to use a new set of data structures and<00:13:40.860> so<00:13:40.980> we'll<00:13:41.100> cover<00:13:41.220> this<00:13:41.459> briefly<00:13:41.820> because 00:13:41.990 --> 00:13:42.000 align:start position:0% and so we'll cover this briefly because 00:13:42.000 --> 00:13:43.610 align:start position:0% and so we'll cover this briefly because it's<00:13:42.240> probably<00:13:42.480> a<00:13:42.720> little<00:13:42.779> bit<00:13:42.959> of<00:13:43.139> a<00:13:43.260> tangent 00:13:43.610 --> 00:13:43.620 align:start position:0% it's probably a little bit of a tangent 00:13:43.620 --> 00:13:45.470 align:start position:0% it's probably a little bit of a tangent but<00:13:44.220> there<00:13:44.399> are<00:13:44.519> actually<00:13:44.639> really<00:13:44.880> good<00:13:45.120> data 00:13:45.470 --> 00:13:45.480 align:start position:0% but there are actually really good data 00:13:45.480 --> 00:13:46.850 align:start position:0% but there are actually really good data structures<00:13:45.779> that<00:13:46.139> are<00:13:46.260> now<00:13:46.440> coming<00:13:46.620> into 00:13:46.850 --> 00:13:46.860 align:start position:0% structures that are now coming into 00:13:46.860 --> 00:13:49.610 align:start position:0% structures that are now coming into modern<00:13:47.100> production<00:13:47.639> use<00:13:47.940> like<00:13:48.480> crdts<00:13:49.380> which 00:13:49.610 --> 00:13:49.620 align:start position:0% modern production use like crdts which 00:13:49.620 --> 00:13:52.190 align:start position:0% modern production use like crdts which are<00:13:49.940> conflict-free<00:13:50.940> replicated<00:13:51.540> data<00:13:51.959> types 00:13:52.190 --> 00:13:52.200 align:start position:0% are conflict-free replicated data types 00:13:52.200 --> 00:13:54.050 align:start position:0% are conflict-free replicated data types that<00:13:52.740> actually<00:13:52.920> allow<00:13:53.339> for<00:13:53.519> composable 00:13:54.050 --> 00:13:54.060 align:start position:0% that actually allow for composable 00:13:54.060 --> 00:13:55.850 align:start position:0% that actually allow for composable operations<00:13:54.600> to<00:13:54.959> be<00:13:55.079> done<00:13:55.260> on<00:13:55.440> these<00:13:55.560> data 00:13:55.850 --> 00:13:55.860 align:start position:0% operations to be done on these data 00:13:55.860 --> 00:13:58.550 align:start position:0% operations to be done on these data structures<00:13:56.160> from<00:13:56.760> around<00:13:56.940> the<00:13:57.180> world<00:13:57.300> so<00:13:58.260> I 00:13:58.550 --> 00:13:58.560 align:start position:0% structures from around the world so I 00:13:58.560 --> 00:13:59.870 align:start position:0% structures from around the world so I increment<00:13:58.860> some<00:13:59.100> number<00:13:59.279> and<00:13:59.519> someone<00:13:59.700> else 00:13:59.870 --> 00:13:59.880 align:start position:0% increment some number and someone else 00:13:59.880 --> 00:14:01.730 align:start position:0% increment some number and someone else across<00:14:00.240> the<00:14:00.300> world<00:14:00.420> decrements<00:14:01.019> it<00:14:01.200> you<00:14:01.620> can 00:14:01.730 --> 00:14:01.740 align:start position:0% across the world decrements it you can 00:14:01.740 --> 00:14:03.470 align:start position:0% across the world decrements it you can see<00:14:01.860> how<00:14:01.980> that<00:14:02.160> operation<00:14:02.459> is<00:14:02.700> composable<00:14:03.180> and 00:14:03.470 --> 00:14:03.480 align:start position:0% see how that operation is composable and 00:14:03.480 --> 00:14:05.569 align:start position:0% see how that operation is composable and so<00:14:03.600> even<00:14:03.720> if<00:14:03.899> we<00:14:04.019> there's<00:14:04.380> some<00:14:04.560> latency<00:14:04.920> or 00:14:05.569 --> 00:14:05.579 align:start position:0% so even if we there's some latency or 00:14:05.579 --> 00:14:07.610 align:start position:0% so even if we there's some latency or someone<00:14:05.760> gets<00:14:06.120> disconnected<00:14:06.660> we<00:14:07.200> can<00:14:07.320> arrive 00:14:07.610 --> 00:14:07.620 align:start position:0% someone gets disconnected we can arrive 00:14:07.620 --> 00:14:10.009 align:start position:0% someone gets disconnected we can arrive at<00:14:07.800> a<00:14:08.040> really<00:14:08.220> consensus<00:14:08.940> based<00:14:09.480> version<00:14:09.600> of<00:14:09.899> a 00:14:10.009 --> 00:14:10.019 align:start position:0% at a really consensus based version of a 00:14:10.019 --> 00:14:15.829 align:start position:0% at a really consensus based version of a final<00:14:10.200> product<00:14:10.560> without<00:14:11.279> having<00:14:11.639> a<00:14:11.880> server 00:14:15.829 --> 00:14:15.839 align:start position:0% 00:14:15.839 --> 00:14:17.930 align:start position:0% the<00:14:16.440> last<00:14:16.560> point<00:14:16.680> about<00:14:16.860> interoperability<00:14:17.639> is 00:14:17.930 --> 00:14:17.940 align:start position:0% the last point about interoperability is 00:14:17.940 --> 00:14:20.030 align:start position:0% the last point about interoperability is that<00:14:18.060> it<00:14:18.240> makes<00:14:18.420> account<00:14:18.720> transfer<00:14:19.380> sales<00:14:19.740> and 00:14:20.030 --> 00:14:20.040 align:start position:0% that it makes account transfer sales and 00:14:20.040 --> 00:14:22.430 align:start position:0% that it makes account transfer sales and auctions<00:14:20.579> so<00:14:20.760> much<00:14:20.880> simpler<00:14:21.300> so<00:14:22.079> when<00:14:22.200> an 00:14:22.430 --> 00:14:22.440 align:start position:0% auctions so much simpler so when an 00:14:22.440 --> 00:14:23.870 align:start position:0% auctions so much simpler so when an account<00:14:22.560> or<00:14:22.740> identity<00:14:23.160> is<00:14:23.339> transferred<00:14:23.760> on 00:14:23.870 --> 00:14:23.880 align:start position:0% account or identity is transferred on 00:14:23.880 --> 00:14:25.970 align:start position:0% account or identity is transferred on chain<00:14:24.120> we'll<00:14:24.720> just<00:14:24.899> do<00:14:25.079> that<00:14:25.200> same<00:14:25.380> lookup<00:14:25.740> and 00:14:25.970 --> 00:14:25.980 align:start position:0% chain we'll just do that same lookup and 00:14:25.980 --> 00:14:27.410 align:start position:0% chain we'll just do that same lookup and the<00:14:26.160> new<00:14:26.279> owner<00:14:26.579> gets<00:14:26.880> access<00:14:27.000> to<00:14:27.300> that 00:14:27.410 --> 00:14:27.420 align:start position:0% the new owner gets access to that 00:14:27.420 --> 00:14:29.150 align:start position:0% the new owner gets access to that username<00:14:27.839> or<00:14:28.079> will<00:14:28.260> just<00:14:28.440> automatically<00:14:28.920> have 00:14:29.150 --> 00:14:29.160 align:start position:0% username or will just automatically have 00:14:29.160 --> 00:14:31.670 align:start position:0% username or will just automatically have access<00:14:29.339> to<00:14:29.579> that's<00:14:29.700> gift.heath<00:14:30.899> it'll<00:14:31.440> also 00:14:31.670 --> 00:14:31.680 align:start position:0% access to that's gift.heath it'll also 00:14:31.680 --> 00:14:33.470 align:start position:0% access to that's gift.heath it'll also mean<00:14:31.860> that<00:14:32.160> users<00:14:32.459> can<00:14:32.700> choose<00:14:33.060> their<00:14:33.300> own 00:14:33.470 --> 00:14:33.480 align:start position:0% mean that users can choose their own 00:14:33.480 --> 00:14:36.410 align:start position:0% mean that users can choose their own history<00:14:34.260> and<00:14:34.620> path<00:14:34.860> around<00:14:35.279> things<00:14:35.579> like<00:14:35.760> 2fa 00:14:36.410 --> 00:14:36.420 align:start position:0% history and path around things like 2fa 00:14:36.420 --> 00:14:39.530 align:start position:0% history and path around things like 2fa you<00:14:37.079> know<00:14:37.139> account<00:14:37.519> uh<00:14:38.519> signatures<00:14:39.120> and<00:14:39.360> login 00:14:39.530 --> 00:14:39.540 align:start position:0% you know account uh signatures and login 00:14:39.540 --> 00:14:41.389 align:start position:0% you know account uh signatures and login and<00:14:39.899> all<00:14:40.079> that<00:14:40.199> sort<00:14:40.320> of<00:14:40.440> stuff<00:14:40.620> so<00:14:41.160> if<00:14:41.279> you 00:14:41.389 --> 00:14:41.399 align:start position:0% and all that sort of stuff so if you 00:14:41.399 --> 00:14:43.069 align:start position:0% and all that sort of stuff so if you want<00:14:41.519> to<00:14:41.639> use<00:14:41.699> a<00:14:41.940> multi-sig<00:14:42.420> wallet<00:14:42.779> for 00:14:43.069 --> 00:14:43.079 align:start position:0% want to use a multi-sig wallet for 00:14:43.079 --> 00:14:45.350 align:start position:0% want to use a multi-sig wallet for skip.eth<00:14:43.800> or<00:14:44.459> you<00:14:44.579> want<00:14:44.699> to<00:14:44.820> set<00:14:44.940> some<00:14:45.180> sort<00:14:45.300> of 00:14:45.350 --> 00:14:45.360 align:start position:0% skip.eth or you want to set some sort of 00:14:45.360 --> 00:14:47.329 align:start position:0% skip.eth or you want to set some sort of 2fa<00:14:45.839> mechanism<00:14:46.199> or<00:14:46.440> use<00:14:46.620> a<00:14:46.740> hardware<00:14:46.860> wallet 00:14:47.329 --> 00:14:47.339 align:start position:0% 2fa mechanism or use a hardware wallet 00:14:47.339 --> 00:14:49.009 align:start position:0% 2fa mechanism or use a hardware wallet you'll<00:14:47.880> get<00:14:48.060> to<00:14:48.180> choose<00:14:48.420> your<00:14:48.600> own<00:14:48.720> security 00:14:49.009 --> 00:14:49.019 align:start position:0% you'll get to choose your own security 00:14:49.019 --> 00:14:51.470 align:start position:0% you'll get to choose your own security posture<00:14:49.620> and<00:14:50.279> so<00:14:50.399> that<00:14:50.519> has<00:14:50.699> a<00:14:50.880> lot<00:14:50.940> of<00:14:51.060> Pros 00:14:51.470 --> 00:14:51.480 align:start position:0% posture and so that has a lot of Pros 00:14:51.480 --> 00:14:53.210 align:start position:0% posture and so that has a lot of Pros for<00:14:51.660> more<00:14:51.839> advanced<00:14:52.199> users<00:14:52.500> it<00:14:52.860> means<00:14:53.100> that 00:14:53.210 --> 00:14:53.220 align:start position:0% for more advanced users it means that 00:14:53.220 --> 00:14:54.710 align:start position:0% for more advanced users it means that people<00:14:53.459> can<00:14:53.699> choose<00:14:53.940> their<00:14:54.120> own<00:14:54.240> way<00:14:54.480> of 00:14:54.710 --> 00:14:54.720 align:start position:0% people can choose their own way of 00:14:54.720 --> 00:14:56.990 align:start position:0% people can choose their own way of securing<00:14:55.139> their<00:14:55.440> their<00:14:55.620> private<00:14:55.980> keys<00:14:56.339> but<00:14:56.880> it 00:14:56.990 --> 00:14:57.000 align:start position:0% securing their their private keys but it 00:14:57.000 --> 00:14:58.790 align:start position:0% securing their their private keys but it also<00:14:57.240> means<00:14:57.540> that<00:14:57.660> platforms<00:14:58.199> no<00:14:58.440> longer<00:14:58.680> have 00:14:58.790 --> 00:14:58.800 align:start position:0% also means that platforms no longer have 00:14:58.800 --> 00:15:00.110 align:start position:0% also means that platforms no longer have to<00:14:58.920> deal<00:14:59.040> with<00:14:59.220> some<00:14:59.399> of<00:14:59.519> that<00:14:59.579> risk<00:14:59.880> of 00:15:00.110 --> 00:15:00.120 align:start position:0% to deal with some of that risk of 00:15:00.120 --> 00:15:01.790 align:start position:0% to deal with some of that risk of accidentally<00:15:00.779> de-platforming<00:15:01.560> people 00:15:01.790 --> 00:15:01.800 align:start position:0% accidentally de-platforming people 00:15:01.800 --> 00:15:04.009 align:start position:0% accidentally de-platforming people having<00:15:02.459> 2fa<00:15:03.120> and<00:15:03.240> complicated<00:15:03.600> reset 00:15:04.009 --> 00:15:04.019 align:start position:0% having 2fa and complicated reset 00:15:04.019 --> 00:15:05.870 align:start position:0% having 2fa and complicated reset mechanisms<00:15:04.620> and<00:15:05.040> you<00:15:05.160> can<00:15:05.279> make<00:15:05.459> sure<00:15:05.639> that 00:15:05.870 --> 00:15:05.880 align:start position:0% mechanisms and you can make sure that 00:15:05.880 --> 00:15:07.250 align:start position:0% mechanisms and you can make sure that the<00:15:06.060> right<00:15:06.180> identity<00:15:06.600> is<00:15:06.720> going<00:15:06.899> to<00:15:07.019> the<00:15:07.139> right 00:15:07.250 --> 00:15:07.260 align:start position:0% the right identity is going to the right 00:15:07.260 --> 00:15:08.150 align:start position:0% the right identity is going to the right person 00:15:08.150 --> 00:15:08.160 align:start position:0% person 00:15:08.160 --> 00:15:10.250 align:start position:0% person it<00:15:08.699> does<00:15:08.880> however<00:15:09.240> introduce<00:15:09.720> complications 00:15:10.250 --> 00:15:10.260 align:start position:0% it does however introduce complications 00:15:10.260 --> 00:15:12.170 align:start position:0% it does however introduce complications around<00:15:10.680> account<00:15:10.980> reset<00:15:11.459> so<00:15:11.760> we'll<00:15:11.880> just<00:15:12.060> be 00:15:12.170 --> 00:15:12.180 align:start position:0% around account reset so we'll just be 00:15:12.180 --> 00:15:13.850 align:start position:0% around account reset so we'll just be transparent<00:15:12.600> about<00:15:12.779> that<00:15:13.019> you<00:15:13.560> know<00:15:13.680> how 00:15:13.850 --> 00:15:13.860 align:start position:0% transparent about that you know how 00:15:13.860 --> 00:15:15.290 align:start position:0% transparent about that you know how difficult<00:15:14.100> it<00:15:14.279> is<00:15:14.459> to<00:15:14.639> remember<00:15:14.760> a<00:15:15.060> seed 00:15:15.290 --> 00:15:15.300 align:start position:0% difficult it is to remember a seed 00:15:15.300 --> 00:15:16.970 align:start position:0% difficult it is to remember a seed phrase<00:15:15.540> maybe<00:15:15.839> you<00:15:16.019> wrote<00:15:16.199> it<00:15:16.380> down<00:15:16.500> or<00:15:16.680> put<00:15:16.860> it 00:15:16.970 --> 00:15:16.980 align:start position:0% phrase maybe you wrote it down or put it 00:15:16.980 --> 00:15:19.310 align:start position:0% phrase maybe you wrote it down or put it in<00:15:17.100> a<00:15:17.220> safety<00:15:17.639> deposit<00:15:18.000> box<00:15:18.180> or<00:15:18.839> you<00:15:18.959> split<00:15:19.199> up 00:15:19.310 --> 00:15:19.320 align:start position:0% in a safety deposit box or you split up 00:15:19.320 --> 00:15:21.350 align:start position:0% in a safety deposit box or you split up pieces<00:15:19.680> and<00:15:19.860> gave<00:15:19.980> them<00:15:20.160> to<00:15:20.339> your<00:15:20.519> friend<00:15:20.699> but 00:15:21.350 --> 00:15:21.360 align:start position:0% pieces and gave them to your friend but 00:15:21.360 --> 00:15:22.850 align:start position:0% pieces and gave them to your friend but that<00:15:21.540> makes<00:15:21.720> building<00:15:21.959> consumer<00:15:22.500> apps<00:15:22.800> a 00:15:22.850 --> 00:15:22.860 align:start position:0% that makes building consumer apps a 00:15:22.860 --> 00:15:24.530 align:start position:0% that makes building consumer apps a little<00:15:22.980> more<00:15:23.100> challenging<00:15:23.579> too<00:15:23.760> like<00:15:24.240> if<00:15:24.360> I 00:15:24.530 --> 00:15:24.540 align:start position:0% little more challenging too like if I 00:15:24.540 --> 00:15:26.090 align:start position:0% little more challenging too like if I want<00:15:24.600> to<00:15:24.720> reset<00:15:24.959> my<00:15:25.199> email<00:15:25.380> address<00:15:25.620> or<00:15:25.860> my 00:15:26.090 --> 00:15:26.100 align:start position:0% want to reset my email address or my 00:15:26.100 --> 00:15:28.009 align:start position:0% want to reset my email address or my messaging<00:15:26.459> app<00:15:26.639> it's<00:15:27.240> a<00:15:27.360> little<00:15:27.480> weird<00:15:27.660> to<00:15:27.899> ask 00:15:28.009 --> 00:15:28.019 align:start position:0% messaging app it's a little weird to ask 00:15:28.019 --> 00:15:29.449 align:start position:0% messaging app it's a little weird to ask my<00:15:28.199> friend<00:15:28.320> to<00:15:28.560> click<00:15:28.740> a<00:15:28.860> button<00:15:29.100> or<00:15:29.220> three<00:15:29.339> of 00:15:29.449 --> 00:15:29.459 align:start position:0% my friend to click a button or three of 00:15:29.459 --> 00:15:31.009 align:start position:0% my friend to click a button or three of them<00:15:29.579> to<00:15:29.699> click<00:15:29.880> a<00:15:30.000> button<00:15:30.240> and<00:15:30.360> give<00:15:30.540> me<00:15:30.660> their 00:15:31.009 --> 00:15:31.019 align:start position:0% them to click a button and give me their 00:15:31.019 --> 00:15:32.449 align:start position:0% them to click a button and give me their you<00:15:31.320> know<00:15:31.380> secret<00:15:31.560> out<00:15:31.920> of<00:15:32.100> a<00:15:32.220> few<00:15:32.339> different 00:15:32.449 --> 00:15:32.459 align:start position:0% you know secret out of a few different 00:15:32.459 --> 00:15:34.970 align:start position:0% you know secret out of a few different secret<00:15:32.699> shares<00:15:33.300> or<00:15:34.019> to<00:15:34.260> use<00:15:34.380> a<00:15:34.560> multi-sig 00:15:34.970 --> 00:15:34.980 align:start position:0% secret shares or to use a multi-sig 00:15:34.980 --> 00:15:36.530 align:start position:0% secret shares or to use a multi-sig wallet<00:15:35.339> to<00:15:35.519> log<00:15:35.639> into<00:15:35.820> a<00:15:36.180> single 00:15:36.530 --> 00:15:36.540 align:start position:0% wallet to log into a single 00:15:36.540 --> 00:15:38.810 align:start position:0% wallet to log into a single collaborative<00:15:37.019> product<00:15:37.260> so 00:15:38.810 --> 00:15:38.820 align:start position:0% collaborative product so 00:15:38.820 --> 00:15:40.790 align:start position:0% collaborative product so it<00:15:39.360> gives<00:15:39.480> users<00:15:39.839> a<00:15:40.019> lot<00:15:40.139> more<00:15:40.260> freedom<00:15:40.620> and 00:15:40.790 --> 00:15:40.800 align:start position:0% it gives users a lot more freedom and 00:15:40.800 --> 00:15:42.410 align:start position:0% it gives users a lot more freedom and empowerment<00:15:41.160> over<00:15:41.459> how<00:15:41.760> they<00:15:41.880> can<00:15:42.000> use<00:15:42.120> these 00:15:42.410 --> 00:15:42.420 align:start position:0% empowerment over how they can use these 00:15:42.420 --> 00:15:44.269 align:start position:0% empowerment over how they can use these products<00:15:42.720> and<00:15:43.260> lets<00:15:43.500> you<00:15:43.560> choose<00:15:43.920> your<00:15:44.160> own 00:15:44.269 --> 00:15:44.279 align:start position:0% products and lets you choose your own 00:15:44.279 --> 00:15:46.550 align:start position:0% products and lets you choose your own security<00:15:44.579> Journey<00:15:45.120> but<00:15:45.779> it<00:15:45.899> also<00:15:46.139> means<00:15:46.380> that 00:15:46.550 --> 00:15:46.560 align:start position:0% security Journey but it also means that 00:15:46.560 --> 00:15:47.810 align:start position:0% security Journey but it also means that there's<00:15:46.740> more<00:15:46.920> complexity<00:15:47.339> around<00:15:47.579> account 00:15:47.810 --> 00:15:47.820 align:start position:0% there's more complexity around account 00:15:47.820 --> 00:15:50.569 align:start position:0% there's more complexity around account reset<00:15:48.300> identity<00:15:48.839> and<00:15:49.380> all<00:15:49.560> those<00:15:49.680> areas<00:15:50.100> that 00:15:50.569 --> 00:15:50.579 align:start position:0% reset identity and all those areas that 00:15:50.579 --> 00:15:52.250 align:start position:0% reset identity and all those areas that frankly<00:15:51.060> a<00:15:51.240> lot<00:15:51.360> of<00:15:51.420> the<00:15:51.540> regular<00:15:51.779> consumers 00:15:52.250 --> 00:15:52.260 align:start position:0% frankly a lot of the regular consumers 00:15:52.260 --> 00:15:54.050 align:start position:0% frankly a lot of the regular consumers will<00:15:52.440> get<00:15:52.620> to<00:15:52.800> and<00:15:53.459> so<00:15:53.579> that's<00:15:53.699> something<00:15:53.880> we 00:15:54.050 --> 00:15:54.060 align:start position:0% will get to and so that's something we 00:15:54.060 --> 00:15:56.090 align:start position:0% will get to and so that's something we spend<00:15:54.360> a<00:15:54.480> lot<00:15:54.540> of<00:15:54.660> time<00:15:54.779> on<00:15:54.959> at<00:15:55.079> skip<00:15:55.320> how<00:15:55.980> can 00:15:56.090 --> 00:15:56.100 align:start position:0% spend a lot of time on at skip how can 00:15:56.100 --> 00:15:57.710 align:start position:0% spend a lot of time on at skip how can you<00:15:56.220> make<00:15:56.339> products<00:15:56.760> really<00:15:57.120> simple<00:15:57.300> really 00:15:57.710 --> 00:15:57.720 align:start position:0% you make products really simple really 00:15:57.720 --> 00:15:59.389 align:start position:0% you make products really simple really easy<00:15:57.959> to<00:15:58.139> use<00:15:58.260> and<00:15:58.500> really<00:15:58.680> easy<00:15:58.860> to<00:15:59.100> sign<00:15:59.220> up 00:15:59.389 --> 00:15:59.399 align:start position:0% easy to use and really easy to sign up 00:15:59.399 --> 00:16:01.910 align:start position:0% easy to use and really easy to sign up and<00:16:00.060> so<00:16:00.180> once<00:16:00.420> you<00:16:00.480> get<00:16:00.660> to<00:16:00.779> users<00:16:01.139> who<00:16:01.560> you 00:16:01.910 --> 00:16:01.920 align:start position:0% and so once you get to users who you 00:16:01.920 --> 00:16:03.170 align:start position:0% and so once you get to users who you know<00:16:02.040> don't<00:16:02.279> want<00:16:02.459> to<00:16:02.579> remember<00:16:02.699> a<00:16:03.000> seed 00:16:03.170 --> 00:16:03.180 align:start position:0% know don't want to remember a seed 00:16:03.180 --> 00:16:04.730 align:start position:0% know don't want to remember a seed phrase<00:16:03.480> or<00:16:03.660> write<00:16:03.959> it<00:16:04.139> down<00:16:04.260> on<00:16:04.380> their<00:16:04.560> desk 00:16:04.730 --> 00:16:04.740 align:start position:0% phrase or write it down on their desk 00:16:04.740 --> 00:16:06.829 align:start position:0% phrase or write it down on their desk you<00:16:05.399> actually<00:16:05.519> get<00:16:05.760> people<00:16:06.060> who<00:16:06.480> you<00:16:06.779> know 00:16:06.829 --> 00:16:06.839 align:start position:0% you actually get people who you know 00:16:06.839 --> 00:16:08.150 align:start position:0% you actually get people who you know have<00:16:06.959> access<00:16:07.199> to<00:16:07.500> all<00:16:07.680> these<00:16:07.860> amazing 00:16:08.150 --> 00:16:08.160 align:start position:0% have access to all these amazing 00:16:08.160 --> 00:16:09.949 align:start position:0% have access to all these amazing benefits<00:16:08.579> of<00:16:08.880> end-to-end<00:16:09.420> encryption<00:16:09.779> and 00:16:09.949 --> 00:16:09.959 align:start position:0% benefits of end-to-end encryption and 00:16:09.959 --> 00:16:12.530 align:start position:0% benefits of end-to-end encryption and you<00:16:10.620> know<00:16:10.680> easy<00:16:10.860> to<00:16:11.100> use<00:16:11.220> collaboration<00:16:11.760> but 00:16:12.530 --> 00:16:12.540 align:start position:0% you know easy to use collaboration but 00:16:12.540 --> 00:16:14.150 align:start position:0% you know easy to use collaboration but then<00:16:12.660> if<00:16:12.839> they<00:16:12.959> lose<00:16:13.139> their<00:16:13.320> seed<00:16:13.620> phrase<00:16:13.860> it's 00:16:14.150 --> 00:16:14.160 align:start position:0% then if they lose their seed phrase it's 00:16:14.160 --> 00:16:19.009 align:start position:0% then if they lose their seed phrase it's harder<00:16:14.459> to<00:16:14.579> reset<00:16:14.880> your<00:16:15.060> account 00:16:19.009 --> 00:16:19.019 align:start position:0% 00:16:19.019 --> 00:16:21.530 align:start position:0% so<00:16:19.440> to<00:16:19.620> recap<00:16:19.920> on<00:16:20.100> the<00:16:20.220> stack<00:16:20.399> we<00:16:21.120> talked<00:16:21.420> first 00:16:21.530 --> 00:16:21.540 align:start position:0% so to recap on the stack we talked first 00:16:21.540 --> 00:16:23.509 align:start position:0% so to recap on the stack we talked first about<00:16:21.779> the<00:16:22.019> auth<00:16:22.199> layer<00:16:22.560> where<00:16:23.160> wallets 00:16:23.509 --> 00:16:23.519 align:start position:0% about the auth layer where wallets 00:16:23.519 --> 00:16:25.250 align:start position:0% about the auth layer where wallets basically<00:16:23.820> enable<00:16:24.180> this<00:16:24.540> entirely<00:16:24.959> new 00:16:25.250 --> 00:16:25.260 align:start position:0% basically enable this entirely new 00:16:25.260 --> 00:16:27.350 align:start position:0% basically enable this entirely new user-owned<00:16:26.040> flow<00:16:26.339> for<00:16:26.579> authenticating<00:16:27.060> and 00:16:27.350 --> 00:16:27.360 align:start position:0% user-owned flow for authenticating and 00:16:27.360 --> 00:16:29.569 align:start position:0% user-owned flow for authenticating and logging<00:16:27.720> into<00:16:27.779> products<00:16:28.320> they<00:16:28.980> also<00:16:29.279> give<00:16:29.399> us 00:16:29.569 --> 00:16:29.579 align:start position:0% logging into products they also give us 00:16:29.579 --> 00:16:31.009 align:start position:0% logging into products they also give us a<00:16:29.820> much<00:16:29.940> simpler<00:16:30.360> mechanism<00:16:30.720> for 00:16:31.009 --> 00:16:31.019 align:start position:0% a much simpler mechanism for 00:16:31.019 --> 00:16:33.230 align:start position:0% a much simpler mechanism for Distributing<00:16:31.440> public<00:16:31.740> keys<00:16:32.220> so<00:16:32.820> don't<00:16:33.060> run 00:16:33.230 --> 00:16:33.240 align:start position:0% Distributing public keys so don't run 00:16:33.240 --> 00:16:35.030 align:start position:0% Distributing public keys so don't run your<00:16:33.480> own<00:16:33.600> personal<00:16:33.779> site<00:16:34.139> with<00:16:34.380> a<00:16:34.500> pgp<00:16:34.860> key 00:16:35.030 --> 00:16:35.040 align:start position:0% your own personal site with a pgp key 00:16:35.040 --> 00:16:37.610 align:start position:0% your own personal site with a pgp key pair<00:16:35.279> run<00:16:36.120> your<00:16:36.540> wallet<00:16:36.959> and<00:16:37.199> just<00:16:37.380> basically 00:16:37.610 --> 00:16:37.620 align:start position:0% pair run your wallet and just basically 00:16:37.620 --> 00:16:39.769 align:start position:0% pair run your wallet and just basically add<00:16:37.920> that<00:16:38.100> data<00:16:38.459> on<00:16:38.639> chain<00:16:38.880> so<00:16:39.180> we<00:16:39.300> can<00:16:39.420> go<00:16:39.600> from 00:16:39.769 --> 00:16:39.779 align:start position:0% add that data on chain so we can go from 00:16:39.779 --> 00:16:41.629 align:start position:0% add that data on chain so we can go from your<00:16:40.079> human<00:16:40.259> readable<00:16:40.680> name<00:16:40.920> to<00:16:41.220> your<00:16:41.339> wallet 00:16:41.629 --> 00:16:41.639 align:start position:0% your human readable name to your wallet 00:16:41.639 --> 00:16:44.030 align:start position:0% your human readable name to your wallet address<00:16:41.759> to<00:16:42.420> a<00:16:42.600> public<00:16:42.720> key<00:16:43.019> to<00:16:43.620> end<00:16:43.800> 10 00:16:44.030 --> 00:16:44.040 align:start position:0% address to a public key to end 10 00:16:44.040 --> 00:16:44.990 align:start position:0% address to a public key to end 10 encryption 00:16:44.990 --> 00:16:45.000 align:start position:0% encryption 00:16:45.000 --> 00:16:47.030 align:start position:0% encryption from<00:16:45.480> there<00:16:45.600> the<00:16:45.899> storage<00:16:46.139> layer<00:16:46.560> of<00:16:46.800> using 00:16:47.030 --> 00:16:47.040 align:start position:0% from there the storage layer of using 00:16:47.040 --> 00:16:49.430 align:start position:0% from there the storage layer of using decentralization<00:16:47.820> and<00:16:48.180> n10<00:16:48.480> encryption<00:16:48.959> give 00:16:49.430 --> 00:16:49.440 align:start position:0% decentralization and n10 encryption give 00:16:49.440 --> 00:16:51.170 align:start position:0% decentralization and n10 encryption give us<00:16:49.620> so<00:16:49.740> much<00:16:49.920> more<00:16:50.040> flexibility<00:16:50.519> you<00:16:51.120> can 00:16:51.170 --> 00:16:51.180 align:start position:0% us so much more flexibility you can 00:16:51.180 --> 00:16:53.150 align:start position:0% us so much more flexibility you can basically<00:16:51.480> store<00:16:51.779> data<00:16:52.139> in<00:16:52.259> more<00:16:52.440> places<00:16:52.680> or 00:16:53.150 --> 00:16:53.160 align:start position:0% basically store data in more places or 00:16:53.160 --> 00:16:55.189 align:start position:0% basically store data in more places or in<00:16:53.279> a<00:16:53.459> decentralized<00:16:53.940> network<00:16:54.180> if<00:16:54.839> that<00:16:55.019> data 00:16:55.189 --> 00:16:55.199 align:start position:0% in a decentralized network if that data 00:16:55.199 --> 00:16:57.170 align:start position:0% in a decentralized network if that data is<00:16:55.259> encrypted<00:16:55.680> with<00:16:55.800> your<00:16:55.980> key<00:16:56.100> pair<00:16:56.339> it<00:16:57.000> also 00:16:57.170 --> 00:16:57.180 align:start position:0% is encrypted with your key pair it also 00:16:57.180 --> 00:16:58.910 align:start position:0% is encrypted with your key pair it also means<00:16:57.420> that<00:16:57.540> data<00:16:57.839> is<00:16:57.959> portable<00:16:58.320> so<00:16:58.620> you<00:16:58.800> want 00:16:58.910 --> 00:16:58.920 align:start position:0% means that data is portable so you want 00:16:58.920 --> 00:17:00.829 align:start position:0% means that data is portable so you want to<00:16:58.980> access<00:16:59.100> it<00:16:59.339> via<00:16:59.639> program<00:16:59.880> or<00:17:00.360> via<00:17:00.600> some 00:17:00.829 --> 00:17:00.839 align:start position:0% to access it via program or via some 00:17:00.839 --> 00:17:02.870 align:start position:0% to access it via program or via some sort<00:17:01.019> of<00:17:01.199> command<00:17:01.860> line<00:17:01.980> tool<00:17:02.339> and<00:17:02.519> change<00:17:02.699> it 00:17:02.870 --> 00:17:02.880 align:start position:0% sort of command line tool and change it 00:17:02.880 --> 00:17:04.730 align:start position:0% sort of command line tool and change it or<00:17:03.060> edit<00:17:03.300> it<00:17:03.360> or<00:17:03.540> download<00:17:03.720> it<00:17:03.959> you<00:17:04.439> can<00:17:04.559> do 00:17:04.730 --> 00:17:04.740 align:start position:0% or edit it or download it you can do 00:17:04.740 --> 00:17:07.130 align:start position:0% or edit it or download it you can do that<00:17:04.919> all<00:17:05.280> from<00:17:05.579> the<00:17:06.299> decentralized<00:17:06.959> network 00:17:07.130 --> 00:17:07.140 align:start position:0% that all from the decentralized network 00:17:07.140 --> 00:17:09.949 align:start position:0% that all from the decentralized network then<00:17:08.100> finally<00:17:08.400> on<00:17:08.640> the<00:17:08.760> app<00:17:08.880> layer<00:17:09.299> there's 00:17:09.949 --> 00:17:09.959 align:start position:0% then finally on the app layer there's 00:17:09.959 --> 00:17:11.689 align:start position:0% then finally on the app layer there's still<00:17:10.140> a<00:17:10.260> lot<00:17:10.380> of<00:17:10.620> progress<00:17:10.919> that<00:17:11.220> has<00:17:11.459> to<00:17:11.579> be 00:17:11.689 --> 00:17:11.699 align:start position:0% still a lot of progress that has to be 00:17:11.699 --> 00:17:14.150 align:start position:0% still a lot of progress that has to be made<00:17:11.939> so<00:17:12.720> this<00:17:13.260> is<00:17:13.380> basically<00:17:13.679> a<00:17:13.919> whole<00:17:13.980> new 00:17:14.150 --> 00:17:14.160 align:start position:0% made so this is basically a whole new 00:17:14.160 --> 00:17:15.590 align:start position:0% made so this is basically a whole new paradigm<00:17:14.699> for<00:17:14.880> building<00:17:15.059> a<00:17:15.299> product<00:17:15.360> like 00:17:15.590 --> 00:17:15.600 align:start position:0% paradigm for building a product like 00:17:15.600 --> 00:17:17.870 align:start position:0% paradigm for building a product like Gmail<00:17:15.900> or<00:17:16.199> Dropbox<00:17:16.620> or<00:17:16.919> drive<00:17:17.100> or<00:17:17.400> OneDrive 00:17:17.870 --> 00:17:17.880 align:start position:0% Gmail or Dropbox or drive or OneDrive 00:17:17.880 --> 00:17:19.909 align:start position:0% Gmail or Dropbox or drive or OneDrive I've<00:17:18.419> tested<00:17:18.839> you<00:17:19.199> know<00:17:19.260> or<00:17:19.439> our<00:17:19.559> team<00:17:19.740> has 00:17:19.909 --> 00:17:19.919 align:start position:0% I've tested you know or our team has 00:17:19.919 --> 00:17:21.650 align:start position:0% I've tested you know or our team has tested<00:17:20.280> every<00:17:20.640> single<00:17:20.880> email<00:17:21.059> product<00:17:21.360> out 00:17:21.650 --> 00:17:21.660 align:start position:0% tested every single email product out 00:17:21.660 --> 00:17:23.270 align:start position:0% tested every single email product out there<00:17:21.839> every<00:17:22.140> single<00:17:22.380> storage<00:17:22.559> product<00:17:22.919> out 00:17:23.270 --> 00:17:23.280 align:start position:0% there every single storage product out 00:17:23.280 --> 00:17:25.250 align:start position:0% there every single storage product out there<00:17:23.459> and<00:17:24.179> it's<00:17:24.299> radically<00:17:24.720> different<00:17:24.959> to 00:17:25.250 --> 00:17:25.260 align:start position:0% there and it's radically different to 00:17:25.260 --> 00:17:26.870 align:start position:0% there and it's radically different to build<00:17:25.380> one<00:17:25.620> that's<00:17:25.860> n10<00:17:26.220> encrypted<00:17:26.640> from<00:17:26.760> the 00:17:26.870 --> 00:17:26.880 align:start position:0% build one that's n10 encrypted from the 00:17:26.880 --> 00:17:28.250 align:start position:0% build one that's n10 encrypted from the ground<00:17:27.000> up<00:17:27.240> and<00:17:27.540> works<00:17:27.780> with<00:17:27.900> people's 00:17:28.250 --> 00:17:28.260 align:start position:0% ground up and works with people's 00:17:28.260 --> 00:17:30.830 align:start position:0% ground up and works with people's wallets<00:17:28.980> so<00:17:29.520> it<00:17:29.700> gives<00:17:29.820> us<00:17:30.000> a<00:17:30.179> lot<00:17:30.240> of<00:17:30.360> benefits 00:17:30.830 --> 00:17:30.840 align:start position:0% wallets so it gives us a lot of benefits 00:17:30.840 --> 00:17:32.810 align:start position:0% wallets so it gives us a lot of benefits of<00:17:31.020> basically<00:17:31.440> this<00:17:31.799> you<00:17:32.100> know<00:17:32.160> natural<00:17:32.400> path 00:17:32.810 --> 00:17:32.820 align:start position:0% of basically this you know natural path 00:17:32.820 --> 00:17:35.390 align:start position:0% of basically this you know natural path from<00:17:33.299> Identity<00:17:33.720> to<00:17:33.900> key<00:17:34.020> pair<00:17:34.260> but<00:17:35.039> it<00:17:35.160> also 00:17:35.390 --> 00:17:35.400 align:start position:0% from Identity to key pair but it also 00:17:35.400 --> 00:17:36.890 align:start position:0% from Identity to key pair but it also means<00:17:35.640> that<00:17:35.700> we<00:17:35.880> have<00:17:36.000> to<00:17:36.120> rebuild<00:17:36.419> a<00:17:36.840> new 00:17:36.890 --> 00:17:36.900 align:start position:0% means that we have to rebuild a new 00:17:36.900 --> 00:17:38.690 align:start position:0% means that we have to rebuild a new stack<00:17:37.140> of<00:17:37.320> consumer<00:17:37.740> apps<00:17:38.100> that<00:17:38.220> do<00:17:38.400> this<00:17:38.580> all 00:17:38.690 --> 00:17:38.700 align:start position:0% stack of consumer apps that do this all 00:17:38.700 --> 00:17:40.549 align:start position:0% stack of consumer apps that do this all behind<00:17:39.059> the<00:17:39.179> scenes<00:17:39.539> you<00:17:40.080> know<00:17:40.140> simply 00:17:40.549 --> 00:17:40.559 align:start position:0% behind the scenes you know simply 00:17:40.559 --> 00:17:42.470 align:start position:0% behind the scenes you know simply naturally<00:17:41.100> and<00:17:41.460> also<00:17:41.700> really<00:17:41.880> performantly 00:17:42.470 --> 00:17:42.480 align:start position:0% naturally and also really performantly 00:17:42.480 --> 00:17:46.130 align:start position:0% naturally and also really performantly so<00:17:42.840> that<00:17:43.020> lookup<00:17:43.320> process<00:17:43.620> gets<00:17:44.039> complicated 00:17:46.130 --> 00:17:46.140 align:start position:0% so that lookup process gets complicated 00:17:46.140 --> 00:17:47.029 align:start position:0% so that lookup process gets complicated um 00:17:47.029 --> 00:17:47.039 align:start position:0% um 00:17:47.039 --> 00:17:48.590 align:start position:0% um so<00:17:47.400> I<00:17:47.460> think<00:17:47.580> from<00:17:47.760> there<00:17:47.940> yeah<00:17:48.179> I<00:17:48.360> just<00:17:48.480> wanted 00:17:48.590 --> 00:17:48.600 align:start position:0% so I think from there yeah I just wanted 00:17:48.600 --> 00:17:50.150 align:start position:0% so I think from there yeah I just wanted to<00:17:48.780> add<00:17:48.840> a<00:17:49.020> couple<00:17:49.080> notes<00:17:49.440> about<00:17:49.679> basically 00:17:50.150 --> 00:17:50.160 align:start position:0% to add a couple notes about basically 00:17:50.160 --> 00:17:52.250 align:start position:0% to add a couple notes about basically how<00:17:50.460> we<00:17:50.580> think<00:17:50.760> this<00:17:51.120> benefits<00:17:51.780> the<00:17:52.020> entire 00:17:52.250 --> 00:17:52.260 align:start position:0% how we think this benefits the entire 00:17:52.260 --> 00:17:54.350 align:start position:0% how we think this benefits the entire community<00:17:52.500> and<00:17:52.799> ecosystem<00:17:53.280> and<00:17:54.120> then<00:17:54.179> we'll 00:17:54.350 --> 00:17:54.360 align:start position:0% community and ecosystem and then we'll 00:17:54.360 --> 00:17:56.990 align:start position:0% community and ecosystem and then we'll do<00:17:54.539> questions<00:17:54.860> so<00:17:55.860> my<00:17:56.160> background<00:17:56.460> is<00:17:56.700> I've 00:17:56.990 --> 00:17:57.000 align:start position:0% do questions so my background is I've 00:17:57.000 --> 00:17:58.549 align:start position:0% do questions so my background is I've been<00:17:57.120> a<00:17:57.240> software<00:17:57.539> Engineers<00:17:57.840> my<00:17:58.320> whole<00:17:58.440> life 00:17:58.549 --> 00:17:58.559 align:start position:0% been a software Engineers my whole life 00:17:58.559 --> 00:18:00.169 align:start position:0% been a software Engineers my whole life since<00:17:58.980> I<00:17:59.160> was<00:17:59.280> probably<00:17:59.460> five<00:17:59.760> or<00:17:59.880> six<00:18:00.059> years 00:18:00.169 --> 00:18:00.179 align:start position:0% since I was probably five or six years 00:18:00.179 --> 00:18:01.610 align:start position:0% since I was probably five or six years old<00:18:00.360> although<00:18:00.720> I<00:18:00.840> was<00:18:00.960> not<00:18:01.140> a<00:18:01.320> professional 00:18:01.610 --> 00:18:01.620 align:start position:0% old although I was not a professional 00:18:01.620 --> 00:18:04.130 align:start position:0% old although I was not a professional engineer<00:18:02.100> at<00:18:02.820> that<00:18:03.000> point<00:18:03.179> and<00:18:03.780> now<00:18:03.960> actually 00:18:04.130 --> 00:18:04.140 align:start position:0% engineer at that point and now actually 00:18:04.140 --> 00:18:06.169 align:start position:0% engineer at that point and now actually doing<00:18:04.500> this<00:18:04.679> for<00:18:04.919> real<00:18:05.100> you<00:18:05.700> can<00:18:05.760> see<00:18:05.940> that 00:18:06.169 --> 00:18:06.179 align:start position:0% doing this for real you can see that 00:18:06.179 --> 00:18:08.270 align:start position:0% doing this for real you can see that this<00:18:06.480> model<00:18:06.840> of<00:18:07.200> Building<00:18:07.320> Products<00:18:07.860> is<00:18:08.160> just 00:18:08.270 --> 00:18:08.280 align:start position:0% this model of Building Products is just 00:18:08.280 --> 00:18:10.070 align:start position:0% this model of Building Products is just so<00:18:08.520> much<00:18:08.640> more<00:18:08.820> intuitive<00:18:09.299> and<00:18:09.660> better<00:18:09.840> for 00:18:10.070 --> 00:18:10.080 align:start position:0% so much more intuitive and better for 00:18:10.080 --> 00:18:12.049 align:start position:0% so much more intuitive and better for people<00:18:10.260> and<00:18:10.500> their<00:18:10.679> identity<00:18:11.039> so<00:18:11.640> if<00:18:11.760> you<00:18:11.940> have 00:18:12.049 --> 00:18:12.059 align:start position:0% people and their identity so if you have 00:18:12.059 --> 00:18:13.850 align:start position:0% people and their identity so if you have a<00:18:12.240> you<00:18:12.360> know<00:18:12.480> a<00:18:12.600> wallet<00:18:12.840> or<00:18:12.960> a<00:18:13.080> keeper<00:18:13.380> that<00:18:13.740> you 00:18:13.850 --> 00:18:13.860 align:start position:0% a you know a wallet or a keeper that you 00:18:13.860 --> 00:18:15.169 align:start position:0% a you know a wallet or a keeper that you really<00:18:13.980> trust<00:18:14.280> and<00:18:14.460> you<00:18:14.640> want<00:18:14.700> to<00:18:14.820> keep<00:18:14.940> track 00:18:15.169 --> 00:18:15.179 align:start position:0% really trust and you want to keep track 00:18:15.179 --> 00:18:17.210 align:start position:0% really trust and you want to keep track of<00:18:15.360> you<00:18:15.960> get<00:18:16.080> to<00:18:16.260> choose<00:18:16.500> your<00:18:16.740> own<00:18:16.919> security 00:18:17.210 --> 00:18:17.220 align:start position:0% of you get to choose your own security 00:18:17.220 --> 00:18:19.190 align:start position:0% of you get to choose your own security mechanisms<00:18:17.940> and<00:18:18.179> safety<00:18:18.480> mechanisms<00:18:18.960> for 00:18:19.190 --> 00:18:19.200 align:start position:0% mechanisms and safety mechanisms for 00:18:19.200 --> 00:18:21.289 align:start position:0% mechanisms and safety mechanisms for owning<00:18:19.500> that<00:18:19.679> private<00:18:19.980> key<00:18:20.160> if<00:18:20.820> you<00:18:20.940> want<00:18:21.179> to 00:18:21.289 --> 00:18:21.299 align:start position:0% owning that private key if you want to 00:18:21.299 --> 00:18:22.669 align:start position:0% owning that private key if you want to communicate<00:18:21.660> with<00:18:21.900> people<00:18:22.020> around<00:18:22.260> the<00:18:22.500> girl 00:18:22.669 --> 00:18:22.679 align:start position:0% communicate with people around the girl 00:18:22.679 --> 00:18:24.710 align:start position:0% communicate with people around the girl the<00:18:23.039> world<00:18:23.160> with<00:18:23.460> end-to-end<00:18:23.940> encryption<00:18:24.240> you 00:18:24.710 --> 00:18:24.720 align:start position:0% the world with end-to-end encryption you 00:18:24.720 --> 00:18:26.990 align:start position:0% the world with end-to-end encryption you can<00:18:24.840> now<00:18:24.960> get<00:18:25.200> that<00:18:25.440> an<00:18:25.799> entirely<00:18:26.220> new<00:18:26.580> kind<00:18:26.940> of 00:18:26.990 --> 00:18:27.000 align:start position:0% can now get that an entirely new kind of 00:18:27.000 --> 00:18:29.450 align:start position:0% can now get that an entirely new kind of more<00:18:27.240> user-owned<00:18:27.960> stack<00:18:28.260> of<00:18:28.380> products<00:18:28.860> I've 00:18:29.450 --> 00:18:29.460 align:start position:0% more user-owned stack of products I've 00:18:29.460 --> 00:18:31.010 align:start position:0% more user-owned stack of products I've been<00:18:29.580> a<00:18:29.760> big<00:18:29.820> fan<00:18:30.000> and<00:18:30.240> so<00:18:30.360> is<00:18:30.539> our<00:18:30.720> team<00:18:30.840> of 00:18:31.010 --> 00:18:31.020 align:start position:0% been a big fan and so is our team of 00:18:31.020 --> 00:18:33.289 align:start position:0% been a big fan and so is our team of decentralized<00:18:31.740> storage<00:18:31.860> and<00:18:32.520> n10<00:18:32.820> encryption 00:18:33.289 --> 00:18:33.299 align:start position:0% decentralized storage and n10 encryption 00:18:33.299 --> 00:18:34.850 align:start position:0% decentralized storage and n10 encryption is<00:18:33.480> one<00:18:33.660> of<00:18:33.780> the<00:18:33.840> biggest<00:18:33.960> enablers<00:18:34.559> for 00:18:34.850 --> 00:18:34.860 align:start position:0% is one of the biggest enablers for 00:18:34.860 --> 00:18:36.470 align:start position:0% is one of the biggest enablers for actually<00:18:35.039> building<00:18:35.280> consumer<00:18:35.880> apps<00:18:36.179> on<00:18:36.360> top 00:18:36.470 --> 00:18:36.480 align:start position:0% actually building consumer apps on top 00:18:36.480 --> 00:18:38.570 align:start position:0% actually building consumer apps on top of<00:18:36.660> it<00:18:36.780> so<00:18:37.440> there's<00:18:37.679> still<00:18:37.860> so<00:18:38.100> much<00:18:38.220> work<00:18:38.400> to 00:18:38.570 --> 00:18:38.580 align:start position:0% of it so there's still so much work to 00:18:38.580 --> 00:18:40.789 align:start position:0% of it so there's still so much work to be<00:18:38.640> done<00:18:38.820> on<00:18:39.059> the<00:18:39.179> product<00:18:39.240> side<00:18:39.600> but<00:18:40.440> we<00:18:40.679> think 00:18:40.789 --> 00:18:40.799 align:start position:0% be done on the product side but we think 00:18:40.799 --> 00:18:42.710 align:start position:0% be done on the product side but we think that<00:18:41.039> basically<00:18:41.400> going<00:18:41.760> from<00:18:42.120> you<00:18:42.419> know<00:18:42.480> this 00:18:42.710 --> 00:18:42.720 align:start position:0% that basically going from you know this 00:18:42.720 --> 00:18:44.990 align:start position:0% that basically going from you know this distributed<00:18:43.140> consensus<00:18:43.740> around<00:18:44.160> public<00:18:44.520> keys 00:18:44.990 --> 00:18:45.000 align:start position:0% distributed consensus around public keys 00:18:45.000 --> 00:18:47.450 align:start position:0% distributed consensus around public keys to<00:18:45.600> end<00:18:45.780> time<00:18:45.960> encryption<00:18:46.440> to<00:18:46.740> a<00:18:46.860> lot<00:18:46.980> more 00:18:47.450 --> 00:18:47.460 align:start position:0% to end time encryption to a lot more 00:18:47.460 --> 00:18:48.770 align:start position:0% to end time encryption to a lot more flexibility<00:18:47.940> on<00:18:48.299> storage<00:18:48.539> and 00:18:48.770 --> 00:18:48.780 align:start position:0% flexibility on storage and 00:18:48.780 --> 00:18:50.870 align:start position:0% flexibility on storage and interoperability<00:18:49.500> it's<00:18:50.160> just<00:18:50.340> a<00:18:50.580> much<00:18:50.700> more 00:18:50.870 --> 00:18:50.880 align:start position:0% interoperability it's just a much more 00:18:50.880 --> 00:18:53.270 align:start position:0% interoperability it's just a much more intuitive<00:18:51.299> better<00:18:51.720> and<00:18:52.020> simpler<00:18:52.380> future<00:18:52.620> that 00:18:53.270 --> 00:18:53.280 align:start position:0% intuitive better and simpler future that 00:18:53.280 --> 00:18:54.710 align:start position:0% intuitive better and simpler future that the<00:18:53.520> end<00:18:53.580> of<00:18:53.700> the<00:18:53.820> day<00:18:53.940> is<00:18:54.240> giving<00:18:54.419> people 00:18:54.710 --> 00:18:54.720 align:start position:0% the end of the day is giving people 00:18:54.720 --> 00:18:57.110 align:start position:0% the end of the day is giving people access<00:18:55.020> to<00:18:55.440> what<00:18:55.620> we<00:18:55.740> see<00:18:55.919> as<00:18:56.160> a<00:18:56.460> fundamental 00:18:57.110 --> 00:18:57.120 align:start position:0% access to what we see as a fundamental 00:18:57.120 --> 00:18:58.789 align:start position:0% access to what we see as a fundamental right<00:18:57.299> which<00:18:57.720> is<00:18:57.840> private<00:18:58.380> communication 00:18:58.789 --> 00:18:58.799 align:start position:0% right which is private communication 00:18:58.799 --> 00:19:00.710 align:start position:0% right which is private communication private<00:18:59.460> writing<00:18:59.820> private<00:19:00.299> collaboration 00:19:00.710 --> 00:19:00.720 align:start position:0% private writing private collaboration 00:19:00.720 --> 00:19:03.770 align:start position:0% private writing private collaboration and<00:19:01.620> owning<00:19:01.980> your<00:19:02.100> own<00:19:02.220> key<00:19:02.460> pairs<00:19:02.880> so<00:19:03.419> I<00:19:03.660> think 00:19:03.770 --> 00:19:03.780 align:start position:0% and owning your own key pairs so I think 00:19:03.780 --> 00:19:05.690 align:start position:0% and owning your own key pairs so I think we've<00:19:04.020> got<00:19:04.140> five<00:19:04.679> six<00:19:04.919> minutes<00:19:05.160> for<00:19:05.460> questions 00:19:05.690 --> 00:19:05.700 align:start position:0% we've got five six minutes for questions 00:19:05.700 --> 00:19:07.850 align:start position:0% we've got five six minutes for questions thank<00:19:06.539> you<00:19:06.660> all<00:19:06.780> for<00:19:06.900> coming<00:19:07.080> I<00:19:07.380> know<00:19:07.500> it's<00:19:07.620> uh 00:19:07.850 --> 00:19:07.860 align:start position:0% thank you all for coming I know it's uh 00:19:07.860 --> 00:19:09.529 align:start position:0% thank you all for coming I know it's uh early 00:19:09.529 --> 00:19:09.539 align:start position:0% early 00:19:09.539 --> 00:19:14.870 align:start position:0% early go<00:19:09.900> ahead 00:19:14.870 --> 00:19:14.880 align:start position:0% 00:19:14.880 --> 00:19:16.430 align:start position:0% ah<00:19:15.480> so<00:19:15.600> this<00:19:15.720> is<00:19:15.840> a<00:19:15.900> great<00:19:16.020> question<00:19:16.140> the 00:19:16.430 --> 00:19:16.440 align:start position:0% ah so this is a great question the 00:19:16.440 --> 00:19:17.750 align:start position:0% ah so this is a great question the question<00:19:16.559> was<00:19:16.740> what<00:19:16.919> are<00:19:17.100> the<00:19:17.160> nuances<00:19:17.580> of 00:19:17.750 --> 00:19:17.760 align:start position:0% question was what are the nuances of 00:19:17.760 --> 00:19:19.549 align:start position:0% question was what are the nuances of going<00:19:18.000> from<00:19:18.419> uh<00:19:18.960> I<00:19:19.080> think<00:19:19.200> it's<00:19:19.320> just 00:19:19.549 --> 00:19:19.559 align:start position:0% going from uh I think it's just 00:19:19.559 --> 00:19:22.130 align:start position:0% going from uh I think it's just basically<00:19:19.919> a<00:19:20.160> wallet<00:19:20.460> address<00:19:20.640> to<00:19:21.360> a<00:19:21.780> actual 00:19:22.130 --> 00:19:22.140 align:start position:0% basically a wallet address to a actual 00:19:22.140 --> 00:19:23.990 align:start position:0% basically a wallet address to a actual public<00:19:22.380> key<00:19:22.679> that<00:19:23.220> you<00:19:23.340> might<00:19:23.400> use<00:19:23.580> to<00:19:23.700> encrypt 00:19:23.990 --> 00:19:24.000 align:start position:0% public key that you might use to encrypt 00:19:24.000 --> 00:19:26.330 align:start position:0% public key that you might use to encrypt data<00:19:24.360> so<00:19:24.780> the<00:19:24.960> nuances<00:19:25.380> are<00:19:25.679> like<00:19:25.919> a<00:19:26.039> wallet 00:19:26.330 --> 00:19:26.340 align:start position:0% data so the nuances are like a wallet 00:19:26.340 --> 00:19:28.010 align:start position:0% data so the nuances are like a wallet address<00:19:26.520> is<00:19:26.880> derived<00:19:27.240> from<00:19:27.360> a<00:19:27.480> public<00:19:27.600> key<00:19:27.840> so 00:19:28.010 --> 00:19:28.020 align:start position:0% address is derived from a public key so 00:19:28.020 --> 00:19:30.470 align:start position:0% address is derived from a public key so it<00:19:28.140> might<00:19:28.260> be<00:19:28.320> a<00:19:28.500> hash<00:19:28.620> Republic<00:19:28.980> Key<00:19:29.400> or<00:19:30.120> you 00:19:30.470 --> 00:19:30.480 align:start position:0% it might be a hash Republic Key or you 00:19:30.480 --> 00:19:31.970 align:start position:0% it might be a hash Republic Key or you know<00:19:30.600> a<00:19:30.720> hash<00:19:30.900> and<00:19:31.020> a<00:19:31.140> truncation<00:19:31.500> of<00:19:31.740> a<00:19:31.860> public 00:19:31.970 --> 00:19:31.980 align:start position:0% know a hash and a truncation of a public 00:19:31.980 --> 00:19:33.529 align:start position:0% know a hash and a truncation of a public key<00:19:32.160> and<00:19:32.280> that's<00:19:32.340> how<00:19:32.520> you<00:19:32.640> get<00:19:32.760> the<00:19:33.059> you<00:19:33.419> know 00:19:33.529 --> 00:19:33.539 align:start position:0% key and that's how you get the you know 00:19:33.539 --> 00:19:36.710 align:start position:0% key and that's how you get the you know the<00:19:33.660> hex<00:19:34.020> 0x<00:19:34.740> whatever<00:19:35.280> you<00:19:36.120> can't<00:19:36.240> use<00:19:36.480> that 00:19:36.710 --> 00:19:36.720 align:start position:0% the hex 0x whatever you can't use that 00:19:36.720 --> 00:19:38.870 align:start position:0% the hex 0x whatever you can't use that hex<00:19:37.080> to<00:19:37.559> encrypt<00:19:37.980> data<00:19:38.280> it's<00:19:38.400> just<00:19:38.640> basically 00:19:38.870 --> 00:19:38.880 align:start position:0% hex to encrypt data it's just basically 00:19:38.880 --> 00:19:40.310 align:start position:0% hex to encrypt data it's just basically the<00:19:39.059> hash<00:19:39.179> Republic<00:19:39.480> Key<00:19:39.840> and<00:19:39.960> not<00:19:40.080> a<00:19:40.200> public 00:19:40.310 --> 00:19:40.320 align:start position:0% the hash Republic Key and not a public 00:19:40.320 --> 00:19:42.890 align:start position:0% the hash Republic Key and not a public key<00:19:40.620> so<00:19:41.280> that<00:19:41.460> gives<00:19:41.700> us<00:19:41.880> I'll<00:19:42.419> just<00:19:42.600> go<00:19:42.720> back 00:19:42.890 --> 00:19:42.900 align:start position:0% key so that gives us I'll just go back 00:19:42.900 --> 00:19:45.470 align:start position:0% key so that gives us I'll just go back to<00:19:43.080> the 00:19:45.470 --> 00:19:45.480 align:start position:0% 00:19:45.480 --> 00:19:49.130 align:start position:0% the<00:19:46.020> diagram<00:19:46.700> so<00:19:47.700> because<00:19:47.880> we<00:19:48.780> can't<00:19:48.960> actually 00:19:49.130 --> 00:19:49.140 align:start position:0% the diagram so because we can't actually 00:19:49.140 --> 00:19:51.049 align:start position:0% the diagram so because we can't actually do<00:19:49.380> that<00:19:49.500> there's<00:19:49.799> now<00:19:49.980> two<00:19:50.220> options<00:19:50.580> to<00:19:50.820> go<00:19:50.940> to 00:19:51.049 --> 00:19:51.059 align:start position:0% do that there's now two options to go to 00:19:51.059 --> 00:19:52.669 align:start position:0% do that there's now two options to go to a<00:19:51.179> public<00:19:51.419> key<00:19:51.660> we<00:19:51.840> can<00:19:51.960> use<00:19:52.020> for<00:19:52.200> encryption 00:19:52.669 --> 00:19:52.679 align:start position:0% a public key we can use for encryption 00:19:52.679 --> 00:19:55.430 align:start position:0% a public key we can use for encryption one<00:19:53.340> is<00:19:53.520> we<00:19:53.700> generate<00:19:54.059> a<00:19:54.360> new<00:19:54.480> key<00:19:54.660> pair<00:19:54.840> that's 00:19:55.430 --> 00:19:55.440 align:start position:0% one is we generate a new key pair that's 00:19:55.440 --> 00:19:56.990 align:start position:0% one is we generate a new key pair that's derived<00:19:55.919> from<00:19:56.039> your<00:19:56.220> wallet<00:19:56.460> address<00:19:56.700> so 00:19:56.990 --> 00:19:57.000 align:start position:0% derived from your wallet address so 00:19:57.000 --> 00:19:58.850 align:start position:0% derived from your wallet address so derived<00:19:57.480> from<00:19:57.539> your<00:19:57.660> wallet<00:19:57.960> private<00:19:58.320> key<00:19:58.440> for 00:19:58.850 --> 00:19:58.860 align:start position:0% derived from your wallet private key for 00:19:58.860 --> 00:20:00.529 align:start position:0% derived from your wallet private key for encryption<00:19:59.340> so<00:19:59.820> you<00:19:59.940> can<00:20:00.059> use<00:20:00.240> whatever 00:20:00.529 --> 00:20:00.539 align:start position:0% encryption so you can use whatever 00:20:00.539 --> 00:20:02.150 align:start position:0% encryption so you can use whatever elliptic<00:20:01.140> curve<00:20:01.380> you<00:20:01.500> want<00:20:01.620> so<00:20:01.799> one<00:20:02.039> that's 00:20:02.150 --> 00:20:02.160 align:start position:0% elliptic curve you want so one that's 00:20:02.160 --> 00:20:03.710 align:start position:0% elliptic curve you want so one that's really<00:20:02.400> well<00:20:02.580> suited<00:20:02.880> for<00:20:03.059> that<00:20:03.179> and<00:20:03.360> generate 00:20:03.710 --> 00:20:03.720 align:start position:0% really well suited for that and generate 00:20:03.720 --> 00:20:05.870 align:start position:0% really well suited for that and generate a<00:20:03.900> new<00:20:04.020> key<00:20:04.140> pair<00:20:04.380> or<00:20:05.220> in<00:20:05.400> the<00:20:05.520> ethereum 00:20:05.870 --> 00:20:05.880 align:start position:0% a new key pair or in the ethereum 00:20:05.880 --> 00:20:07.669 align:start position:0% a new key pair or in the ethereum context<00:20:06.240> you<00:20:06.539> could<00:20:06.660> use<00:20:06.840> an<00:20:07.020> ethereum<00:20:07.440> public 00:20:07.669 --> 00:20:07.679 align:start position:0% context you could use an ethereum public 00:20:07.679 --> 00:20:09.669 align:start position:0% context you could use an ethereum public key<00:20:07.919> so<00:20:08.220> a<00:20:08.460> curve 00:20:09.669 --> 00:20:09.679 align:start position:0% key so a curve 00:20:09.679 --> 00:20:13.070 align:start position:0% key so a curve scp-256k<00:20:10.679> public<00:20:11.340> key<00:20:11.640> which<00:20:12.299> is<00:20:12.480> not<00:20:12.780> really 00:20:13.070 --> 00:20:13.080 align:start position:0% scp-256k public key which is not really 00:20:13.080 --> 00:20:14.690 align:start position:0% scp-256k public key which is not really quite<00:20:13.380> as<00:20:13.500> well<00:20:13.679> suited<00:20:13.980> for<00:20:14.160> encryption<00:20:14.520> it's 00:20:14.690 --> 00:20:14.700 align:start position:0% quite as well suited for encryption it's 00:20:14.700 --> 00:20:16.789 align:start position:0% quite as well suited for encryption it's a<00:20:14.820> little<00:20:14.880> slower<00:20:15.240> and<00:20:15.720> generally<00:20:16.620> not 00:20:16.789 --> 00:20:16.799 align:start position:0% a little slower and generally not 00:20:16.799 --> 00:20:18.890 align:start position:0% a little slower and generally not preferred<00:20:17.220> over<00:20:17.580> you<00:20:18.120> know<00:20:18.179> like<00:20:18.360> a<00:20:18.600> curve 00:20:18.890 --> 00:20:18.900 align:start position:0% preferred over you know like a curve 00:20:18.900 --> 00:20:21.289 align:start position:0% preferred over you know like a curve 25519<00:20:19.860> public<00:20:20.220> key<00:20:20.520> but<00:20:20.940> yeah<00:20:21.059> I<00:20:21.179> think 00:20:21.289 --> 00:20:21.299 align:start position:0% 25519 public key but yeah I think 00:20:21.299 --> 00:20:23.450 align:start position:0% 25519 public key but yeah I think there's<00:20:21.539> still<00:20:21.720> a<00:20:21.960> lot<00:20:22.080> of<00:20:22.260> lack<00:20:22.740> of<00:20:22.860> consensus 00:20:23.450 --> 00:20:23.460 align:start position:0% there's still a lot of lack of consensus 00:20:23.460 --> 00:20:26.210 align:start position:0% there's still a lot of lack of consensus on<00:20:24.059> how<00:20:24.419> to<00:20:24.600> go<00:20:24.780> from<00:20:25.080> a<00:20:25.500> wallet<00:20:25.799> address<00:20:25.860> to<00:20:26.100> a 00:20:26.210 --> 00:20:26.220 align:start position:0% on how to go from a wallet address to a 00:20:26.220 --> 00:20:27.890 align:start position:0% on how to go from a wallet address to a public<00:20:26.340> key<00:20:26.520> or<00:20:26.760> how<00:20:26.880> to<00:20:27.000> use<00:20:27.179> you<00:20:27.660> know<00:20:27.780> do 00:20:27.890 --> 00:20:27.900 align:start position:0% public key or how to use you know do 00:20:27.900 --> 00:20:29.690 align:start position:0% public key or how to use you know do encryption<00:20:28.260> and<00:20:28.380> decryption<00:20:28.799> via<00:20:29.039> wallets<00:20:29.340> is 00:20:29.690 --> 00:20:29.700 align:start position:0% encryption and decryption via wallets is 00:20:29.700 --> 00:20:32.330 align:start position:0% encryption and decryption via wallets is that<00:20:29.880> uh<00:20:30.360> the<00:20:30.720> data<00:20:31.440> can<00:20:31.620> be<00:20:31.740> stored<00:20:32.100> in<00:20:32.160> a 00:20:32.330 --> 00:20:32.340 align:start position:0% that uh the data can be stored in a 00:20:32.340 --> 00:20:35.090 align:start position:0% that uh the data can be stored in a decentralized<00:20:32.760> way<00:20:32.940> into<00:20:33.120> showed<00:20:33.480> ipfs<00:20:34.100> how 00:20:35.090 --> 00:20:35.100 align:start position:0% decentralized way into showed ipfs how 00:20:35.100 --> 00:20:37.850 align:start position:0% decentralized way into showed ipfs how is<00:20:35.280> this<00:20:35.460> real<00:20:35.760> estate<00:20:35.940> in<00:20:36.179> practice<00:20:36.360> on<00:20:37.080> crdts 00:20:37.850 --> 00:20:37.860 align:start position:0% is this real estate in practice on crdts 00:20:37.860 --> 00:20:39.890 align:start position:0% is this real estate in practice on crdts when<00:20:37.980> that<00:20:38.160> user<00:20:38.520> presses<00:20:38.880> the<00:20:39.059> keys<00:20:39.419> that<00:20:39.720> the 00:20:39.890 --> 00:20:39.900 align:start position:0% when that user presses the keys that the 00:20:39.900 --> 00:20:42.529 align:start position:0% when that user presses the keys that the new<00:20:40.140> ipfs<00:20:40.679> hash<00:20:40.919> every<00:20:41.160> time<00:20:41.340> or<00:20:41.880> how<00:20:42.240> does<00:20:42.419> it 00:20:42.529 --> 00:20:42.539 align:start position:0% new ipfs hash every time or how does it 00:20:42.539 --> 00:20:44.510 align:start position:0% new ipfs hash every time or how does it work<00:20:42.780> yeah<00:20:43.140> this<00:20:43.380> is<00:20:43.500> a<00:20:43.620> good<00:20:43.740> question<00:20:43.919> so 00:20:44.510 --> 00:20:44.520 align:start position:0% work yeah this is a good question so 00:20:44.520 --> 00:20:46.250 align:start position:0% work yeah this is a good question so right<00:20:44.880> now<00:20:45.000> basically<00:20:45.240> the<00:20:45.299> way<00:20:45.419> way<00:20:45.960> our 00:20:46.250 --> 00:20:46.260 align:start position:0% right now basically the way way our 00:20:46.260 --> 00:20:47.870 align:start position:0% right now basically the way way our products<00:20:46.559> work<00:20:46.740> is<00:20:46.980> when<00:20:47.160> a<00:20:47.280> user<00:20:47.460> presses<00:20:47.760> a 00:20:47.870 --> 00:20:47.880 align:start position:0% products work is when a user presses a 00:20:47.880 --> 00:20:49.789 align:start position:0% products work is when a user presses a key<00:20:48.059> it's<00:20:48.360> applied<00:20:48.660> locally<00:20:49.020> to<00:20:49.320> your<00:20:49.440> editor 00:20:49.789 --> 00:20:49.799 align:start position:0% key it's applied locally to your editor 00:20:49.799 --> 00:20:51.409 align:start position:0% key it's applied locally to your editor State<00:20:49.980> your<00:20:50.340> editor<00:20:50.580> state<00:20:50.760> is<00:20:50.940> some<00:20:51.120> data 00:20:51.409 --> 00:20:51.419 align:start position:0% State your editor state is some data 00:20:51.419 --> 00:20:53.029 align:start position:0% State your editor state is some data structure<00:20:51.720> that's<00:20:51.900> like<00:20:52.140> editors<00:20:52.860> are 00:20:53.029 --> 00:20:53.039 align:start position:0% structure that's like editors are 00:20:53.039 --> 00:20:54.470 align:start position:0% structure that's like editors are actually<00:20:53.220> super<00:20:53.520> complicated<00:20:54.059> you<00:20:54.299> know<00:20:54.360> we 00:20:54.470 --> 00:20:54.480 align:start position:0% actually super complicated you know we 00:20:54.480 --> 00:20:55.610 align:start position:0% actually super complicated you know we should<00:20:54.600> all<00:20:54.720> go<00:20:54.840> to<00:20:54.900> a<00:20:55.020> conference<00:20:55.260> on<00:20:55.440> text 00:20:55.610 --> 00:20:55.620 align:start position:0% should all go to a conference on text 00:20:55.620 --> 00:20:58.310 align:start position:0% should all go to a conference on text editing<00:20:56.100> but<00:20:56.640> basically<00:20:57.000> editors<00:20:57.539> store<00:20:57.840> some 00:20:58.310 --> 00:20:58.320 align:start position:0% editing but basically editors store some 00:20:58.320 --> 00:21:01.730 align:start position:0% editing but basically editors store some array<00:20:59.100> of<00:20:59.340> values<00:20:59.880> like<00:21:00.179> headers<00:21:00.600> body<00:21:01.020> text 00:21:01.730 --> 00:21:01.740 align:start position:0% array of values like headers body text 00:21:01.740 --> 00:21:04.430 align:start position:0% array of values like headers body text Etc<00:21:01.919> so<00:21:02.760> that<00:21:02.880> gets<00:21:03.179> mapped<00:21:03.419> to<00:21:03.539> a<00:21:03.660> crdt<00:21:04.140> state 00:21:04.430 --> 00:21:04.440 align:start position:0% Etc so that gets mapped to a crdt state 00:21:04.440 --> 00:21:06.470 align:start position:0% Etc so that gets mapped to a crdt state which<00:21:04.799> is<00:21:04.860> just<00:21:05.039> a<00:21:05.160> data<00:21:05.460> structure<00:21:05.820> which 00:21:06.470 --> 00:21:06.480 align:start position:0% which is just a data structure which 00:21:06.480 --> 00:21:08.750 align:start position:0% which is just a data structure which basically<00:21:07.080> like<00:21:07.200> a<00:21:07.380> set<00:21:07.500> of<00:21:07.679> operations<00:21:08.100> on<00:21:08.580> an 00:21:08.750 --> 00:21:08.760 align:start position:0% basically like a set of operations on an 00:21:08.760 --> 00:21:10.789 align:start position:0% basically like a set of operations on an empty<00:21:09.059> State<00:21:09.240> and<00:21:09.720> so<00:21:09.840> that<00:21:10.020> operation<00:21:10.440> you 00:21:10.789 --> 00:21:10.799 align:start position:0% empty State and so that operation you 00:21:10.799 --> 00:21:13.310 align:start position:0% empty State and so that operation you know<00:21:10.860> I<00:21:10.980> typed<00:21:11.220> a<00:21:11.340> key<00:21:11.460> at<00:21:11.700> position<00:21:11.820> 500<00:21:12.720> is 00:21:13.310 --> 00:21:13.320 align:start position:0% know I typed a key at position 500 is 00:21:13.320 --> 00:21:15.409 align:start position:0% know I typed a key at position 500 is then<00:21:13.559> sent<00:21:13.860> or<00:21:14.160> it's<00:21:14.340> n10<00:21:14.700> encrypted<00:21:15.120> sent 00:21:15.409 --> 00:21:15.419 align:start position:0% then sent or it's n10 encrypted sent 00:21:15.419 --> 00:21:16.730 align:start position:0% then sent or it's n10 encrypted sent across<00:21:15.780> the<00:21:15.840> network<00:21:16.020> to<00:21:16.260> other<00:21:16.380> people<00:21:16.559> who 00:21:16.730 --> 00:21:16.740 align:start position:0% across the network to other people who 00:21:16.740 --> 00:21:18.590 align:start position:0% across the network to other people who are<00:21:16.860> collaborating<00:21:17.340> and<00:21:17.880> they<00:21:18.059> also<00:21:18.360> apply 00:21:18.590 --> 00:21:18.600 align:start position:0% are collaborating and they also apply 00:21:18.600 --> 00:21:20.270 align:start position:0% are collaborating and they also apply that<00:21:18.780> operation<00:21:19.140> and<00:21:19.440> so<00:21:19.559> you<00:21:19.679> do<00:21:19.860> both<00:21:20.100> do 00:21:20.270 --> 00:21:20.280 align:start position:0% that operation and so you do both do 00:21:20.280 --> 00:21:21.770 align:start position:0% that operation and so you do both do that<00:21:20.460> composibly<00:21:20.940> and<00:21:21.179> end<00:21:21.299> up<00:21:21.419> at<00:21:21.539> a<00:21:21.660> final 00:21:21.770 --> 00:21:21.780 align:start position:0% that composibly and end up at a final 00:21:21.780 --> 00:21:24.529 align:start position:0% that composibly and end up at a final state<00:21:22.160> from<00:21:23.160> there<00:21:23.340> every<00:21:23.820> so<00:21:24.000> often<00:21:24.360> and 00:21:24.529 --> 00:21:24.539 align:start position:0% state from there every so often and 00:21:24.539 --> 00:21:26.450 align:start position:0% state from there every so often and there's<00:21:24.720> another<00:21:24.900> I<00:21:25.860> guess<00:21:26.039> like<00:21:26.220> a<00:21:26.340> few 00:21:26.450 --> 00:21:26.460 align:start position:0% there's another I guess like a few 00:21:26.460 --> 00:21:28.970 align:start position:0% there's another I guess like a few little<00:21:26.640> kinks<00:21:27.059> to<00:21:27.179> iron<00:21:27.419> out<00:21:27.720> here<00:21:27.900> from<00:21:28.799> there 00:21:28.970 --> 00:21:28.980 align:start position:0% little kinks to iron out here from there 00:21:28.980 --> 00:21:31.130 align:start position:0% little kinks to iron out here from there your<00:21:29.460> document<00:21:29.820> is<00:21:30.120> intent<00:21:30.600> encrypted<00:21:30.960> so 00:21:31.130 --> 00:21:31.140 align:start position:0% your document is intent encrypted so 00:21:31.140 --> 00:21:32.390 align:start position:0% your document is intent encrypted so encrypted<00:21:31.500> with<00:21:31.620> a<00:21:31.740> key<00:21:31.860> that<00:21:32.100> you<00:21:32.280> have 00:21:32.390 --> 00:21:32.400 align:start position:0% encrypted with a key that you have 00:21:32.400 --> 00:21:33.890 align:start position:0% encrypted with a key that you have access<00:21:32.520> to<00:21:32.760> in<00:21:32.880> your<00:21:33.000> collaborators<00:21:33.480> do<00:21:33.720> but 00:21:33.890 --> 00:21:33.900 align:start position:0% access to in your collaborators do but 00:21:33.900 --> 00:21:35.750 align:start position:0% access to in your collaborators do but no<00:21:34.080> one<00:21:34.200> else<00:21:34.320> does<00:21:34.559> and<00:21:35.220> then<00:21:35.280> from<00:21:35.460> there<00:21:35.640> it 00:21:35.750 --> 00:21:35.760 align:start position:0% no one else does and then from there it 00:21:35.760 --> 00:21:37.610 align:start position:0% no one else does and then from there it can<00:21:35.880> be<00:21:35.940> uploaded<00:21:36.299> to<00:21:36.419> ipfs<00:21:36.900> and<00:21:37.200> so<00:21:37.320> there's<00:21:37.440> a 00:21:37.610 --> 00:21:37.620 align:start position:0% can be uploaded to ipfs and so there's a 00:21:37.620 --> 00:21:39.649 align:start position:0% can be uploaded to ipfs and so there's a few<00:21:37.679> nuances<00:21:38.159> of<00:21:38.400> not<00:21:38.640> everything<00:21:39.240> in<00:21:39.480> real 00:21:39.649 --> 00:21:39.659 align:start position:0% few nuances of not everything in real 00:21:39.659 --> 00:21:41.630 align:start position:0% few nuances of not everything in real time<00:21:39.840> on<00:21:40.080> our<00:21:40.200> products<00:21:40.500> is<00:21:40.679> uploaded<00:21:41.039> to<00:21:41.159> ipfs 00:21:41.630 --> 00:21:41.640 align:start position:0% time on our products is uploaded to ipfs 00:21:41.640 --> 00:21:44.029 align:start position:0% time on our products is uploaded to ipfs but<00:21:42.360> things<00:21:42.600> that<00:21:42.840> are<00:21:42.960> immutable<00:21:43.440> or<00:21:43.620> static 00:21:44.029 --> 00:21:44.039 align:start position:0% but things that are immutable or static 00:21:44.039 --> 00:21:46.610 align:start position:0% but things that are immutable or static or<00:21:44.220> published<00:21:44.640> can<00:21:45.000> be<00:21:45.120> so<00:21:45.360> so<00:21:45.960> that's<00:21:46.380> how 00:21:46.610 --> 00:21:46.620 align:start position:0% or published can be so so that's how 00:21:46.620 --> 00:21:48.350 align:start position:0% or published can be so so that's how that's<00:21:46.740> done<00:21:46.919> today<00:21:47.100> but 00:21:48.350 --> 00:21:48.360 align:start position:0% that's done today but 00:21:48.360 --> 00:21:50.090 align:start position:0% that's done today but um<00:21:48.419> yeah<00:21:48.900> the<00:21:49.140> whole<00:21:49.320> decentralized<00:21:49.860> storage 00:21:50.090 --> 00:21:50.100 align:start position:0% um yeah the whole decentralized storage 00:21:50.100 --> 00:21:51.950 align:start position:0% um yeah the whole decentralized storage kind<00:21:50.820> of<00:21:50.940> network<00:21:51.179> choosing<00:21:51.659> is<00:21:51.840> another 00:21:51.950 --> 00:21:51.960 align:start position:0% kind of network choosing is another 00:21:51.960 --> 00:21:53.990 align:start position:0% kind of network choosing is another whole<00:21:52.320> area<00:21:52.799> go<00:21:53.280> ahead 00:21:53.990 --> 00:21:54.000 align:start position:0% whole area go ahead 00:21:54.000 --> 00:21:56.810 align:start position:0% whole area go ahead sorry<00:21:54.419> can<00:21:54.720> I<00:21:54.840> just<00:21:54.960> ask<00:21:55.200> then<00:21:55.799> are<00:21:56.520> your 00:21:56.810 --> 00:21:56.820 align:start position:0% sorry can I just ask then are your 00:21:56.820 --> 00:21:57.890 align:start position:0% sorry can I just ask then are your servers 00:21:57.890 --> 00:21:57.900 align:start position:0% servers 00:21:57.900 --> 00:21:59.630 align:start position:0% servers they're<00:21:58.320> providing<00:21:58.679> the<00:21:58.799> ipfs<00:21:59.400> services 00:21:59.630 --> 00:21:59.640 align:start position:0% they're providing the ipfs services 00:21:59.640 --> 00:22:02.990 align:start position:0% they're providing the ipfs services that's<00:22:00.539> not<00:22:00.840> decentralized<00:22:01.620> as<00:22:02.159> of<00:22:02.340> yet<00:22:02.520> do 00:22:02.990 --> 00:22:03.000 align:start position:0% that's not decentralized as of yet do 00:22:03.000 --> 00:22:05.690 align:start position:0% that's not decentralized as of yet do you<00:22:03.179> have<00:22:03.240> any<00:22:03.419> plans<00:22:04.080> around<00:22:04.260> that<00:22:04.559> or<00:22:05.100> yeah 00:22:05.690 --> 00:22:05.700 align:start position:0% you have any plans around that or yeah 00:22:05.700 --> 00:22:08.450 align:start position:0% you have any plans around that or yeah so<00:22:06.179> I<00:22:06.659> don't<00:22:06.780> think<00:22:06.960> we<00:22:07.200> I've<00:22:07.980> been<00:22:08.100> a<00:22:08.280> big<00:22:08.340> fan 00:22:08.450 --> 00:22:08.460 align:start position:0% so I don't think we I've been a big fan 00:22:08.460 --> 00:22:11.210 align:start position:0% so I don't think we I've been a big fan of<00:22:08.640> ipfs<00:22:09.240> for<00:22:10.080> like<00:22:10.140> five<00:22:10.380> years<00:22:10.559> and<00:22:10.799> what<00:22:10.980> you 00:22:11.210 --> 00:22:11.220 align:start position:0% of ipfs for like five years and what you 00:22:11.220 --> 00:22:12.649 align:start position:0% of ipfs for like five years and what you know<00:22:11.280> tried<00:22:11.520> running<00:22:11.700> my<00:22:11.940> own<00:22:12.059> notes<00:22:12.360> all<00:22:12.480> that 00:22:12.649 --> 00:22:12.659 align:start position:0% know tried running my own notes all that 00:22:12.659 --> 00:22:15.350 align:start position:0% know tried running my own notes all that I<00:22:13.260> don't<00:22:13.380> think<00:22:13.679> it's<00:22:14.340> totally<00:22:14.640> feasible<00:22:15.059> for 00:22:15.350 --> 00:22:15.360 align:start position:0% I don't think it's totally feasible for 00:22:15.360 --> 00:22:17.270 align:start position:0% I don't think it's totally feasible for everyone<00:22:15.419> to<00:22:15.720> be<00:22:15.840> running<00:22:15.960> their<00:22:16.380> own<00:22:16.559> kind<00:22:17.159> of 00:22:17.270 --> 00:22:17.280 align:start position:0% everyone to be running their own kind of 00:22:17.280 --> 00:22:18.590 align:start position:0% everyone to be running their own kind of nodes<00:22:17.460> in<00:22:17.640> a<00:22:17.820> decentralized<00:22:18.179> network<00:22:18.419> so 00:22:18.590 --> 00:22:18.600 align:start position:0% nodes in a decentralized network so 00:22:18.600 --> 00:22:20.810 align:start position:0% nodes in a decentralized network so they're<00:22:18.780> a<00:22:18.960> really<00:22:19.080> great<00:22:19.200> ipfs<00:22:19.799> gateways<00:22:20.400> you 00:22:20.810 --> 00:22:20.820 align:start position:0% they're a really great ipfs gateways you 00:22:20.820 --> 00:22:22.850 align:start position:0% they're a really great ipfs gateways you know<00:22:20.880> for<00:22:21.000> upload<00:22:21.419> and<00:22:21.600> even<00:22:21.780> cloudflare<00:22:22.380> runs 00:22:22.850 --> 00:22:22.860 align:start position:0% know for upload and even cloudflare runs 00:22:22.860 --> 00:22:25.250 align:start position:0% know for upload and even cloudflare runs a<00:22:23.039> really<00:22:23.220> fast<00:22:23.460> kind<00:22:23.820> of<00:22:23.940> caching<00:22:24.299> layer<00:22:24.659> on 00:22:25.250 --> 00:22:25.260 align:start position:0% a really fast kind of caching layer on 00:22:25.260 --> 00:22:28.490 align:start position:0% a really fast kind of caching layer on top<00:22:25.380> of<00:22:25.500> the<00:22:25.620> download<00:22:25.799> part<00:22:26.159> of<00:22:26.280> ipfs<00:22:26.960> so<00:22:27.960> I 00:22:28.490 --> 00:22:28.500 align:start position:0% top of the download part of ipfs so I 00:22:28.500 --> 00:22:30.409 align:start position:0% top of the download part of ipfs so I think<00:22:28.559> basically<00:22:28.980> yes<00:22:29.220> there's<00:22:29.640> some<00:22:29.940> you 00:22:30.409 --> 00:22:30.419 align:start position:0% think basically yes there's some you 00:22:30.419 --> 00:22:31.490 align:start position:0% think basically yes there's some you know<00:22:30.480> antenna<00:22:30.900> encryption<00:22:31.140> which<00:22:31.320> is<00:22:31.380> done 00:22:31.490 --> 00:22:31.500 align:start position:0% know antenna encryption which is done 00:22:31.500 --> 00:22:33.230 align:start position:0% know antenna encryption which is done client-side<00:22:32.100> then<00:22:32.460> it<00:22:32.640> gets<00:22:32.880> passed<00:22:33.179> through 00:22:33.230 --> 00:22:33.240 align:start position:0% client-side then it gets passed through 00:22:33.240 --> 00:22:34.669 align:start position:0% client-side then it gets passed through some<00:22:33.480> sort<00:22:33.659> of<00:22:33.720> Gateway<00:22:34.020> which<00:22:34.320> is<00:22:34.380> generally 00:22:34.669 --> 00:22:34.679 align:start position:0% some sort of Gateway which is generally 00:22:34.679 --> 00:22:36.590 align:start position:0% some sort of Gateway which is generally centralized<00:22:35.400> and<00:22:35.820> then<00:22:35.880> it<00:22:36.000> gets<00:22:36.240> put<00:22:36.360> on<00:22:36.480> a 00:22:36.590 --> 00:22:36.600 align:start position:0% centralized and then it gets put on a 00:22:36.600 --> 00:22:38.090 align:start position:0% centralized and then it gets put on a network<00:22:36.780> and<00:22:37.080> like<00:22:37.320> the<00:22:37.440> user<00:22:37.679> at<00:22:37.799> the<00:22:37.919> end<00:22:37.980> of 00:22:38.090 --> 00:22:38.100 align:start position:0% network and like the user at the end of 00:22:38.100 --> 00:22:39.710 align:start position:0% network and like the user at the end of the<00:22:38.159> day<00:22:38.280> can<00:22:38.520> get<00:22:38.700> access<00:22:38.880> to<00:22:39.179> those 00:22:39.710 --> 00:22:39.720 align:start position:0% the day can get access to those 00:22:39.720 --> 00:22:41.750 align:start position:0% the day can get access to those identifiers<00:22:40.380> so<00:22:40.919> at<00:22:40.980> the<00:22:41.100> end<00:22:41.220> of<00:22:41.340> the<00:22:41.400> day<00:22:41.520> you 00:22:41.750 --> 00:22:41.760 align:start position:0% identifiers so at the end of the day you 00:22:41.760 --> 00:22:43.130 align:start position:0% identifiers so at the end of the day you still<00:22:41.880> get<00:22:42.000> the<00:22:42.120> benefit<00:22:42.299> of<00:22:42.659> you<00:22:42.960> know<00:22:43.020> your 00:22:43.130 --> 00:22:43.140 align:start position:0% still get the benefit of you know your 00:22:43.140 --> 00:22:44.510 align:start position:0% still get the benefit of you know your data's<00:22:43.440> on<00:22:43.559> 10<00:22:43.679> encrypted<00:22:43.980> it's<00:22:44.100> put<00:22:44.280> on<00:22:44.400> a 00:22:44.510 --> 00:22:44.520 align:start position:0% data's on 10 encrypted it's put on a 00:22:44.520 --> 00:22:45.529 align:start position:0% data's on 10 encrypted it's put on a network<00:22:44.580> you<00:22:44.880> can<00:22:45.000> get<00:22:45.120> access<00:22:45.240> to<00:22:45.419> the 00:22:45.529 --> 00:22:45.539 align:start position:0% network you can get access to the 00:22:45.539 --> 00:22:47.510 align:start position:0% network you can get access to the identifier<00:22:45.900> in<00:22:46.080> the<00:22:46.260> key<00:22:46.380> but<00:22:46.980> it's<00:22:47.100> not<00:22:47.280> you 00:22:47.510 --> 00:22:47.520 align:start position:0% identifier in the key but it's not you 00:22:47.520 --> 00:22:48.710 align:start position:0% identifier in the key but it's not you know<00:22:47.640> every<00:22:47.760> single<00:22:48.059> part<00:22:48.179> of<00:22:48.299> that<00:22:48.419> process 00:22:48.710 --> 00:22:48.720 align:start position:0% know every single part of that process 00:22:48.720 --> 00:22:51.710 align:start position:0% know every single part of that process isn't<00:22:49.440> uh<00:22:50.039> totally<00:22:50.340> distributed<00:22:50.820> uh<00:22:51.419> well<00:22:51.600> if 00:22:51.710 --> 00:22:51.720 align:start position:0% isn't uh totally distributed uh well if 00:22:51.720 --> 00:22:53.570 align:start position:0% isn't uh totally distributed uh well if any<00:22:51.900> last<00:22:52.080> quick<00:22:52.380> things<00:22:52.559> either<00:22:52.860> come<00:22:53.280> grab 00:22:53.570 --> 00:22:53.580 align:start position:0% any last quick things either come grab 00:22:53.580 --> 00:22:55.490 align:start position:0% any last quick things either come grab me<00:22:53.700> thank<00:22:54.000> you<00:22:54.120> all<00:22:54.240> for<00:22:54.360> coming<00:22:54.539> and<00:22:55.260> yeah<00:22:55.380> I 00:22:55.490 --> 00:22:55.500 align:start position:0% me thank you all for coming and yeah I 00:22:55.500 --> 00:22:57.409 align:start position:0% me thank you all for coming and yeah I guess<00:22:55.620> we<00:22:55.740> had<00:22:55.919> that<00:22:56.159> whole<00:22:56.400> uh<00:22:56.700> Power<00:22:57.000> scare 00:22:57.409 --> 00:22:57.419 align:start position:0% guess we had that whole uh Power scare 00:22:57.419 --> 00:22:59.870 align:start position:0% guess we had that whole uh Power scare so<00:22:57.840> someone<00:22:58.440> you<00:22:58.980> know<00:22:59.039> did<00:22:59.460> some<00:22:59.640> sort<00:22:59.820> of 00:22:59.870 --> 00:22:59.880 align:start position:0% so someone you know did some sort of 00:22:59.880 --> 00:23:01.450 align:start position:0% so someone you know did some sort of search 00:23:01.450 --> 00:23:01.460 align:start position:0% search 00:23:01.460 --> 00:23:06.710 align:start position:0% search [Applause]