WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.129 align:start position:0% [Applause] 00:00:12.129 --> 00:00:12.139 align:start position:0% 00:00:12.139 --> 00:00:15.949 align:start position:0% hi<00:00:13.139> everybody<00:00:13.459> my<00:00:14.459> name<00:00:14.700> is<00:00:14.789> Anne<00:00:15.059> Walker<00:00:15.330> I'm 00:00:15.949 --> 00:00:15.959 align:start position:0% hi everybody my name is Anne Walker I'm 00:00:15.959 --> 00:00:19.519 align:start position:0% hi everybody my name is Anne Walker I'm an<00:00:16.230> animator<00:00:16.560> at<00:00:17.010> eros<00:00:17.550> watch<00:00:18.349> this<00:00:19.349> is<00:00:19.439> a 00:00:19.519 --> 00:00:19.529 align:start position:0% an animator at eros watch this is a 00:00:19.529 --> 00:00:22.400 align:start position:0% an animator at eros watch this is a workshop<00:00:19.950> about<00:00:20.580> keyspace<00:00:21.180> which<00:00:21.779> is<00:00:21.990> a 00:00:22.400 --> 00:00:22.410 align:start position:0% workshop about keyspace which is a 00:00:22.410 --> 00:00:24.200 align:start position:0% workshop about keyspace which is a protocol<00:00:22.980> for<00:00:23.039> end-to-end<00:00:23.550> encryption 00:00:24.200 --> 00:00:24.210 align:start position:0% protocol for end-to-end encryption 00:00:24.210 --> 00:00:31.640 align:start position:0% protocol for end-to-end encryption amusing<00:00:24.779> and<00:00:24.960> aetherium<00:00:25.349> and<00:00:25.740> IBSS<00:00:30.230> before<00:00:31.230> I 00:00:31.640 --> 00:00:31.650 align:start position:0% amusing and aetherium and IBSS before I 00:00:31.650 --> 00:00:33.770 align:start position:0% amusing and aetherium and IBSS before I get<00:00:31.859> started<00:00:32.129> I<00:00:32.550> wanted<00:00:32.879> to<00:00:33.000> give<00:00:33.150> a<00:00:33.390> bit<00:00:33.629> of<00:00:33.660> a 00:00:33.770 --> 00:00:33.780 align:start position:0% get started I wanted to give a bit of a 00:00:33.780 --> 00:00:36.560 align:start position:0% get started I wanted to give a bit of a prologue<00:00:34.260> for<00:00:34.650> prettiest<00:00:35.460> piece<00:00:36.449> of 00:00:36.560 --> 00:00:36.570 align:start position:0% prologue for prettiest piece of 00:00:36.570 --> 00:00:38.840 align:start position:0% prologue for prettiest piece of technology<00:00:37.080> in<00:00:37.199> kind<00:00:37.410> of<00:00:37.470> a<00:00:37.620> larger<00:00:38.339> context 00:00:38.840 --> 00:00:38.850 align:start position:0% technology in kind of a larger context 00:00:38.850 --> 00:00:40.610 align:start position:0% technology in kind of a larger context of<00:00:38.940> what<00:00:39.059> I<00:00:39.089> see<00:00:39.330> of<00:00:39.449> kind<00:00:40.170> of<00:00:40.230> emerging 00:00:40.610 --> 00:00:40.620 align:start position:0% of what I see of kind of emerging 00:00:40.620 --> 00:00:43.610 align:start position:0% of what I see of kind of emerging technologies<00:00:41.690> so<00:00:42.690> that<00:00:42.720> inspiration<00:00:43.290> for<00:00:43.470> key 00:00:43.610 --> 00:00:43.620 align:start position:0% technologies so that inspiration for key 00:00:43.620 --> 00:00:46.880 align:start position:0% technologies so that inspiration for key space<00:00:43.799> first<00:00:44.370> came<00:00:44.549> to<00:00:44.729> me<00:00:44.879> about<00:00:45.330> a<00:00:45.769> year<00:00:46.769> ago 00:00:46.880 --> 00:00:46.890 align:start position:0% space first came to me about a year ago 00:00:46.890 --> 00:00:50.060 align:start position:0% space first came to me about a year ago I<00:00:47.100> was<00:00:47.280> listening<00:00:47.610> to<00:00:47.640> a<00:00:47.820> podcast<00:00:48.500> by<00:00:49.500> Arthur 00:00:50.060 --> 00:00:50.070 align:start position:0% I was listening to a podcast by Arthur 00:00:50.070 --> 00:00:52.759 align:start position:0% I was listening to a podcast by Arthur Falls<00:00:50.400> called<00:00:50.850> the<00:00:51.000> third<00:00:51.210> one<00:00:51.650> he<00:00:52.650> was 00:00:52.759 --> 00:00:52.769 align:start position:0% Falls called the third one he was 00:00:52.769 --> 00:00:55.340 align:start position:0% Falls called the third one he was interviewing<00:00:53.190> a<00:00:53.699> developer<00:00:54.330> named<00:00:54.989> Dominic 00:00:55.340 --> 00:00:55.350 align:start position:0% interviewing a developer named Dominic 00:00:55.350 --> 00:00:59.810 align:start position:0% interviewing a developer named Dominic Tarr<00:00:55.799> he's<00:00:56.129> the<00:00:56.930> who<00:00:57.930> develops<00:00:58.290> a<00:00:58.820> distributed 00:00:59.810 --> 00:00:59.820 align:start position:0% Tarr he's the who develops a distributed 00:00:59.820 --> 00:01:02.570 align:start position:0% Tarr he's the who develops a distributed social<00:01:00.269> media<00:01:00.750> network<00:01:01.220> called<00:01:02.220> secure 00:01:02.570 --> 00:01:02.580 align:start position:0% social media network called secure 00:01:02.580 --> 00:01:04.700 align:start position:0% social media network called secure Scotland<00:01:03.059> of<00:01:03.299> end-of-year<00:01:03.960> familiar<00:01:04.530> with 00:01:04.700 --> 00:01:04.710 align:start position:0% Scotland of end-of-year familiar with 00:01:04.710 --> 00:01:08.359 align:start position:0% Scotland of end-of-year familiar with that<00:01:05.479> but<00:01:06.479> the<00:01:07.380> thing<00:01:07.560> I<00:01:07.650> really<00:01:07.830> liked<00:01:08.010> in<00:01:08.189> the 00:01:08.359 --> 00:01:08.369 align:start position:0% that but the thing I really liked in the 00:01:08.369 --> 00:01:10.130 align:start position:0% that but the thing I really liked in the in<00:01:08.880> an<00:01:09.030> interview<00:01:09.330> was<00:01:09.570> he<00:01:09.659> talked<00:01:09.869> about<00:01:09.930> this 00:01:10.130 --> 00:01:10.140 align:start position:0% in an interview was he talked about this 00:01:10.140 --> 00:01:14.990 align:start position:0% in an interview was he talked about this concept<00:01:10.350> called<00:01:11.090> cyberspace<00:01:12.090> so<00:01:14.000> cyberspace 00:01:14.990 --> 00:01:15.000 align:start position:0% concept called cyberspace so cyberspace 00:01:15.000 --> 00:01:20.139 align:start position:0% concept called cyberspace so cyberspace is<00:01:15.270> what<00:01:16.200> he<00:01:16.590> sees<00:01:16.890> as<00:01:17.310> kind<00:01:17.969> of<00:01:18.030> an<00:01:18.630> emerging 00:01:20.139 --> 00:01:20.149 align:start position:0% is what he sees as kind of an emerging 00:01:20.149 --> 00:01:23.270 align:start position:0% is what he sees as kind of an emerging style<00:01:21.149> of<00:01:21.659> application<00:01:22.439> development<00:01:22.469> on<00:01:23.159> the 00:01:23.270 --> 00:01:23.280 align:start position:0% style of application development on the 00:01:23.280 --> 00:01:27.349 align:start position:0% style of application development on the net<00:01:23.460> or<00:01:24.030> on<00:01:24.240> the<00:01:24.329> web<00:01:25.460> has<00:01:26.460> a<00:01:26.490> kind<00:01:26.850> of<00:01:26.880> a<00:01:26.969> proper 00:01:27.349 --> 00:01:27.359 align:start position:0% net or on the web has a kind of a proper 00:01:27.359 --> 00:01:28.999 align:start position:0% net or on the web has a kind of a proper abstraction<00:01:27.929> between<00:01:28.079> the<00:01:28.409> networking<00:01:28.799> layer 00:01:28.999 --> 00:01:29.009 align:start position:0% abstraction between the networking layer 00:01:29.009 --> 00:01:31.669 align:start position:0% abstraction between the networking layer and<00:01:29.310> the<00:01:30.270> application<00:01:30.299> layer<00:01:30.960> and<00:01:31.259> that 00:01:31.669 --> 00:01:31.679 align:start position:0% and the application layer and that 00:01:31.679 --> 00:01:33.679 align:start position:0% and the application layer and that proper<00:01:32.189> abstraction<00:01:32.729> is<00:01:32.850> enabled<00:01:33.270> the<00:01:33.450> first 00:01:33.679 --> 00:01:33.689 align:start position:0% proper abstraction is enabled the first 00:01:33.689 --> 00:01:36.310 align:start position:0% proper abstraction is enabled the first time<00:01:33.869> really<00:01:34.079> by<00:01:34.409> use<00:01:35.219> of<00:01:35.249> different 00:01:36.310 --> 00:01:36.320 align:start position:0% time really by use of different 00:01:36.320 --> 00:01:43.039 align:start position:0% time really by use of different cryptographic<00:01:37.320> premises<00:01:37.950> I<00:01:39.049> think<00:01:42.049> having 00:01:43.039 --> 00:01:43.049 align:start position:0% cryptographic premises I think having 00:01:43.049 --> 00:01:45.859 align:start position:0% cryptographic premises I think having your<00:01:43.429> application<00:01:44.429> logic<00:01:44.600> divorced<00:01:45.600> from 00:01:45.859 --> 00:01:45.869 align:start position:0% your application logic divorced from 00:01:45.869 --> 00:01:49.489 align:start position:0% your application logic divorced from your<00:01:46.729> network<00:01:47.729> network<00:01:48.359> in<00:01:48.630> logic<00:01:48.929> looks<00:01:49.259> kind 00:01:49.489 --> 00:01:49.499 align:start position:0% your network network in logic looks kind 00:01:49.499 --> 00:01:53.239 align:start position:0% your network network in logic looks kind of<00:01:49.649> like<00:01:49.859> a<00:01:50.689> graph<00:01:51.689> QL<00:01:51.840> in<00:01:52.619> that<00:01:52.859> you<00:01:53.069> know<00:01:53.189> you 00:01:53.239 --> 00:01:53.249 align:start position:0% of like a graph QL in that you know you 00:01:53.249 --> 00:01:56.270 align:start position:0% of like a graph QL in that you know you can<00:01:53.639> kind<00:01:53.759> of<00:01:53.880> specify<00:01:55.159> what<00:01:56.159> your 00:01:56.270 --> 00:01:56.280 align:start position:0% can kind of specify what your 00:01:56.280 --> 00:01:58.069 align:start position:0% can kind of specify what your application<00:01:56.759> needs<00:01:56.969> but<00:01:57.600> you<00:01:57.689> don't<00:01:57.869> have<00:01:57.960> to 00:01:58.069 --> 00:01:58.079 align:start position:0% application needs but you don't have to 00:01:58.079 --> 00:02:00.709 align:start position:0% application needs but you don't have to worry<00:01:58.259> about<00:01:58.319> how<00:01:58.619> it<00:01:58.740> gets<00:01:58.920> to<00:01:59.039> you<00:01:59.240> so<00:02:00.240> I 00:02:00.709 --> 00:02:00.719 align:start position:0% worry about how it gets to you so I 00:02:00.719 --> 00:02:02.929 align:start position:0% worry about how it gets to you so I think<00:02:01.079> some<00:02:01.679> more<00:02:01.770> concrete<00:02:02.249> examples<00:02:02.700> of 00:02:02.929 --> 00:02:02.939 align:start position:0% think some more concrete examples of 00:02:02.939 --> 00:02:05.899 align:start position:0% think some more concrete examples of like<00:02:03.539> what<00:02:04.049> cyberspace<00:02:04.740> is<00:02:05.009> and<00:02:05.490> how<00:02:05.670> this 00:02:05.899 --> 00:02:05.909 align:start position:0% like what cyberspace is and how this 00:02:05.909 --> 00:02:08.980 align:start position:0% like what cyberspace is and how this kind<00:02:06.569> of<00:02:06.689> development<00:02:07.679> methodology 00:02:08.980 --> 00:02:08.990 align:start position:0% kind of development methodology 00:02:08.990 --> 00:02:11.200 align:start position:0% kind of development methodology in<00:02:09.350> the<00:02:09.440> future<00:02:09.620> it's<00:02:10.520> going<00:02:10.640> to<00:02:10.730> be<00:02:10.820> made 00:02:11.200 --> 00:02:11.210 align:start position:0% in the future it's going to be made 00:02:11.210 --> 00:02:14.530 align:start position:0% in the future it's going to be made clear<00:02:11.510> and<00:02:12.200> some<00:02:12.380> later<00:02:12.560> examples<00:02:13.070> but<00:02:13.540> just 00:02:14.530 --> 00:02:14.540 align:start position:0% clear and some later examples but just 00:02:14.540 --> 00:02:16.600 align:start position:0% clear and some later examples but just to<00:02:14.990> have<00:02:15.080> that<00:02:15.140> context<00:02:15.740> at<00:02:15.800> you<00:02:15.920> is<00:02:16.250> you<00:02:16.400> kind 00:02:16.600 --> 00:02:16.610 align:start position:0% to have that context at you is you kind 00:02:16.610 --> 00:02:20.950 align:start position:0% to have that context at you is you kind of<00:02:17.560> watch<00:02:18.560> this<00:02:18.680> presentation<00:02:19.570> so<00:02:20.570> this<00:02:20.870> is 00:02:20.950 --> 00:02:20.960 align:start position:0% of watch this presentation so this is 00:02:20.960 --> 00:02:22.960 align:start position:0% of watch this presentation so this is the<00:02:21.020> agenda<00:02:21.230> we're<00:02:22.220> gonna<00:02:22.310> start<00:02:22.580> out<00:02:22.700> pile 00:02:22.960 --> 00:02:22.970 align:start position:0% the agenda we're gonna start out pile 00:02:22.970 --> 00:02:26.050 align:start position:0% the agenda we're gonna start out pile high<00:02:23.240> level<00:02:23.540> and<00:02:23.780> just<00:02:24.590> answer<00:02:25.340> what<00:02:25.730> is<00:02:25.880> this 00:02:26.050 --> 00:02:26.060 align:start position:0% high level and just answer what is this 00:02:26.060 --> 00:02:27.850 align:start position:0% high level and just answer what is this bit<00:02:26.270> so<00:02:26.600> why<00:02:26.840> was<00:02:26.990> the<00:02:27.080> build<00:02:27.290> similar<00:02:27.560> its 00:02:27.850 --> 00:02:27.860 align:start position:0% bit so why was the build similar its 00:02:27.860 --> 00:02:30.160 align:start position:0% bit so why was the build similar its core<00:02:28.070> dependence<00:02:28.630> then<00:02:29.630> we're<00:02:29.720> gonna<00:02:29.840> zoom<00:02:30.080> in 00:02:30.160 --> 00:02:30.170 align:start position:0% core dependence then we're gonna zoom in 00:02:30.170 --> 00:02:31.690 align:start position:0% core dependence then we're gonna zoom in a<00:02:30.260> little<00:02:30.350> bit<00:02:30.500> more<00:02:30.800> with<00:02:31.040> the<00:02:31.070> in-depth 00:02:31.690 --> 00:02:31.700 align:start position:0% a little bit more with the in-depth 00:02:31.700 --> 00:02:34.150 align:start position:0% a little bit more with the in-depth technical<00:02:31.910> description<00:02:32.860> there's<00:02:33.860> kind<00:02:34.130> of 00:02:34.150 --> 00:02:34.160 align:start position:0% technical description there's kind of 00:02:34.160 --> 00:02:36.010 align:start position:0% technical description there's kind of three<00:02:34.430> main<00:02:34.700> stages<00:02:34.970> and<00:02:35.390> the<00:02:35.450> user<00:02:35.630> life 00:02:36.010 --> 00:02:36.020 align:start position:0% three main stages and the user life 00:02:36.020 --> 00:02:38.050 align:start position:0% three main stages and the user life cycle<00:02:36.380> within<00:02:36.500> the<00:02:36.680> protocol<00:02:37.040> we're<00:02:37.970> gonna 00:02:38.050 --> 00:02:38.060 align:start position:0% cycle within the protocol we're gonna 00:02:38.060 --> 00:02:40.510 align:start position:0% cycle within the protocol we're gonna work<00:02:38.390> through<00:02:38.570> each<00:02:38.600> of<00:02:38.810> those<00:02:39.250> after<00:02:40.250> that<00:02:40.400> is 00:02:40.510 --> 00:02:40.520 align:start position:0% work through each of those after that is 00:02:40.520 --> 00:02:43.360 align:start position:0% work through each of those after that is the<00:02:40.550> fun<00:02:40.790> part<00:02:40.820> the<00:02:41.470> interactive<00:02:42.470> examples<00:02:42.950> it 00:02:43.360 --> 00:02:43.370 align:start position:0% the fun part the interactive examples it 00:02:43.370 --> 00:02:45.250 align:start position:0% the fun part the interactive examples it is<00:02:43.460> kind<00:02:43.640> of<00:02:43.700> a<00:02:43.790> donut<00:02:44.180> app<00:02:44.330> that<00:02:44.600> you<00:02:44.720> all<00:02:44.960> can 00:02:45.250 --> 00:02:45.260 align:start position:0% is kind of a donut app that you all can 00:02:45.260 --> 00:02:47.470 align:start position:0% is kind of a donut app that you all can load<00:02:45.470> up<00:02:45.830> on<00:02:46.280> either<00:02:46.490> desktop<00:02:47.000> to<00:02:47.090> your<00:02:47.210> fans 00:02:47.470 --> 00:02:47.480 align:start position:0% load up on either desktop to your fans 00:02:47.480 --> 00:02:50.130 align:start position:0% load up on either desktop to your fans and<00:02:47.750> we<00:02:48.290> can<00:02:48.470> kind<00:02:48.860> of<00:02:48.890> do<00:02:49.100> some<00:02:49.340> cute<00:02:49.610> adhere 00:02:50.130 --> 00:02:50.140 align:start position:0% and we can kind of do some cute adhere 00:02:50.140 --> 00:02:52.900 align:start position:0% and we can kind of do some cute adhere encrypted<00:02:51.140> group<00:02:51.980> messaging<00:02:52.370> amongst<00:02:52.760> each 00:02:52.900 --> 00:02:52.910 align:start position:0% encrypted group messaging amongst each 00:02:52.910 --> 00:02:56.290 align:start position:0% encrypted group messaging amongst each other<00:02:53.000> and<00:02:53.620> then<00:02:54.970> after<00:02:55.970> that<00:02:56.060> we'll<00:02:56.240> have 00:02:56.290 --> 00:02:56.300 align:start position:0% other and then after that we'll have 00:02:56.300 --> 00:02:58.090 align:start position:0% other and then after that we'll have some<00:02:56.420> time<00:02:56.690> for<00:02:56.720> questions<00:02:57.110> or<00:02:57.530> exploration 00:02:58.090 --> 00:02:58.100 align:start position:0% some time for questions or exploration 00:02:58.100 --> 00:03:01.330 align:start position:0% some time for questions or exploration on<00:02:58.430> just<00:02:58.850> meeting<00:02:59.060> you<00:02:59.810> know<00:03:00.010> what<00:03:01.010> we<00:03:01.100> can<00:03:01.220> do 00:03:01.330 --> 00:03:01.340 align:start position:0% on just meeting you know what we can do 00:03:01.340 --> 00:03:05.320 align:start position:0% on just meeting you know what we can do with<00:03:01.460> this<00:03:01.550> kind<00:03:01.670> of<00:03:01.790> protocol<00:03:03.790> so<00:03:04.790> free<00:03:05.000> study 00:03:05.320 --> 00:03:05.330 align:start position:0% with this kind of protocol so free study 00:03:05.330 --> 00:03:08.050 align:start position:0% with this kind of protocol so free study definitions<00:03:05.900> what<00:03:06.650> is<00:03:06.770> key<00:03:06.920> space<00:03:07.130> I<00:03:07.460> think 00:03:08.050 --> 00:03:08.060 align:start position:0% definitions what is key space I think 00:03:08.060 --> 00:03:10.480 align:start position:0% definitions what is key space I think the<00:03:08.150> simplest<00:03:08.600> way<00:03:08.870> to<00:03:08.900> sum<00:03:09.440> it<00:03:09.470> up<00:03:09.590> is<00:03:09.800> the<00:03:10.160> key 00:03:10.480 --> 00:03:10.490 align:start position:0% the simplest way to sum it up is the key 00:03:10.490 --> 00:03:13.030 align:start position:0% the simplest way to sum it up is the key space<00:03:10.760> is<00:03:10.970> at<00:03:11.120> restless<00:03:11.660> token<00:03:12.500> PGP 00:03:13.030 --> 00:03:13.040 align:start position:0% space is at restless token PGP 00:03:13.040 --> 00:03:14.890 align:start position:0% space is at restless token PGP implementation<00:03:13.820> developed<00:03:14.300> on<00:03:14.390> top<00:03:14.630> of 00:03:14.890 --> 00:03:14.900 align:start position:0% implementation developed on top of 00:03:14.900 --> 00:03:18.310 align:start position:0% implementation developed on top of theorems<00:03:15.520> existing<00:03:16.520> cryptographic<00:03:17.180> key<00:03:17.930> to 00:03:18.310 --> 00:03:18.320 align:start position:0% theorems existing cryptographic key to 00:03:18.320 --> 00:03:22.450 align:start position:0% theorems existing cryptographic key to winning<00:03:18.680> so<00:03:19.750> some<00:03:20.750> obvious<00:03:21.740> questions<00:03:21.830> come 00:03:22.450 --> 00:03:22.460 align:start position:0% winning so some obvious questions come 00:03:22.460 --> 00:03:25.690 align:start position:0% winning so some obvious questions come up<00:03:22.490> from<00:03:22.760> this<00:03:22.880> definition<00:03:24.070> first<00:03:25.070> of<00:03:25.220> all<00:03:25.340> for 00:03:25.690 --> 00:03:25.700 align:start position:0% up from this definition first of all for 00:03:25.700 --> 00:03:28.810 align:start position:0% up from this definition first of all for those<00:03:25.790> unfamiliar<00:03:26.630> with<00:03:27.820> cryptographic 00:03:28.810 --> 00:03:28.820 align:start position:0% those unfamiliar with cryptographic 00:03:28.820 --> 00:03:32.800 align:start position:0% those unfamiliar with cryptographic protocols<00:03:29.480> ways<00:03:29.930> open<00:03:30.200> PGP<00:03:30.530> and<00:03:31.510> secondly<00:03:32.510> why 00:03:32.800 --> 00:03:32.810 align:start position:0% protocols ways open PGP and secondly why 00:03:32.810 --> 00:03:38.410 align:start position:0% protocols ways open PGP and secondly why we<00:03:33.020> need<00:03:33.200> open<00:03:33.530> PGP<00:03:33.830> on<00:03:34.190> there<00:03:36.790> so<00:03:37.790> teaching 00:03:38.410 --> 00:03:38.420 align:start position:0% we need open PGP on there so teaching 00:03:38.420 --> 00:03:40.900 align:start position:0% we need open PGP on there so teaching these<00:03:38.660> stands<00:03:38.930> for<00:03:39.170> freedom<00:03:39.530> privacy<00:03:40.130> it's<00:03:40.760> an 00:03:40.900 --> 00:03:40.910 align:start position:0% these stands for freedom privacy it's an 00:03:40.910 --> 00:03:42.400 align:start position:0% these stands for freedom privacy it's an encryption<00:03:41.150> program<00:03:41.630> that<00:03:41.810> provided<00:03:42.140> to 00:03:42.400 --> 00:03:42.410 align:start position:0% encryption program that provided to 00:03:42.410 --> 00:03:43.900 align:start position:0% encryption program that provided to cryptographic<00:03:42.710> privacy<00:03:43.430> and<00:03:43.640> authentication 00:03:43.900 --> 00:03:43.910 align:start position:0% cryptographic privacy and authentication 00:03:43.910 --> 00:03:47.140 align:start position:0% cryptographic privacy and authentication for<00:03:44.600> data<00:03:44.900> communication<00:03:45.670> PGP<00:03:46.670> is<00:03:46.700> used<00:03:47.000> for 00:03:47.140 --> 00:03:47.150 align:start position:0% for data communication PGP is used for 00:03:47.150 --> 00:03:49.090 align:start position:0% for data communication PGP is used for signing<00:03:47.510> encrypting<00:03:47.960> and<00:03:48.200> decrypting<00:03:48.440> text 00:03:49.090 --> 00:03:49.100 align:start position:0% signing encrypting and decrypting text 00:03:49.100 --> 00:03:51.490 align:start position:0% signing encrypting and decrypting text emails<00:03:49.460> files<00:03:49.820> directories<00:03:50.570> and<00:03:50.900> holy<00:03:51.260> disk 00:03:51.490 --> 00:03:51.500 align:start position:0% emails files directories and holy disk 00:03:51.500 --> 00:03:53.740 align:start position:0% emails files directories and holy disk partitions<00:03:52.070> and<00:03:52.610> to<00:03:52.790> increase<00:03:53.030> the<00:03:53.270> security 00:03:53.740 --> 00:03:53.750 align:start position:0% partitions and to increase the security 00:03:53.750 --> 00:03:55.030 align:start position:0% partitions and to increase the security of<00:03:53.960> the<00:03:54.050> email<00:03:54.260> communication<00:03:54.770> so<00:03:54.980> if 00:03:55.030 --> 00:03:55.040 align:start position:0% of the email communication so if 00:03:55.040 --> 00:03:56.229 align:start position:0% of the email communication so if legislation 00:03:56.229 --> 00:03:56.239 align:start position:0% legislation 00:03:56.239 --> 00:04:00.009 align:start position:0% legislation um<00:03:56.980> so<00:03:57.980> BGP<00:03:58.819> a<00:03:59.090> little<00:03:59.329> background<00:03:59.480> myth<00:03:59.870> it 00:04:00.009 --> 00:04:00.019 align:start position:0% um so BGP a little background myth it 00:04:00.019 --> 00:04:01.449 align:start position:0% um so BGP a little background myth it was<00:04:00.049> developed<00:04:00.439> by<00:04:00.560> a<00:04:00.590> photographer<00:04:00.859> named 00:04:01.449 --> 00:04:01.459 align:start position:0% was developed by a photographer named 00:04:01.459 --> 00:04:04.089 align:start position:0% was developed by a photographer named Phil<00:04:01.730> Zimmerman<00:04:02.090> in<00:04:02.420> the<00:04:02.569> nineties<00:04:03.010> it<00:04:04.010> was 00:04:04.089 --> 00:04:04.099 align:start position:0% Phil Zimmerman in the nineties it was 00:04:04.099 --> 00:04:10.720 align:start position:0% Phil Zimmerman in the nineties it was first<00:04:04.310> of<00:04:04.430> all<00:04:04.519> to<00:04:04.579> zEnterprise<00:04:05.180> software<00:04:09.730> but 00:04:10.720 --> 00:04:10.730 align:start position:0% first of all to zEnterprise software but 00:04:10.730 --> 00:04:12.339 align:start position:0% first of all to zEnterprise software but it<00:04:10.790> was<00:04:10.909> first<00:04:11.120> developed<00:04:11.269> as<00:04:11.750> enterprise 00:04:12.339 --> 00:04:12.349 align:start position:0% it was first developed as enterprise 00:04:12.349 --> 00:04:18.279 align:start position:0% it was first developed as enterprise software<00:04:12.530> and<00:04:13.150> 1991<00:04:14.409> around<00:04:15.409> 97<00:04:16.690> Phil<00:04:17.690> decided 00:04:18.279 --> 00:04:18.289 align:start position:0% software and 1991 around 97 Phil decided 00:04:18.289 --> 00:04:21.219 align:start position:0% software and 1991 around 97 Phil decided that<00:04:18.620> this<00:04:19.609> would<00:04:19.970> only<00:04:20.090> work<00:04:20.419> if<00:04:20.570> it<00:04:20.750> was<00:04:20.900> open 00:04:21.219 --> 00:04:21.229 align:start position:0% that this would only work if it was open 00:04:21.229 --> 00:04:23.080 align:start position:0% that this would only work if it was open source<00:04:21.440> so<00:04:21.739> he<00:04:21.799> started<00:04:22.220> the<00:04:22.370> open<00:04:22.880> PGP 00:04:23.080 --> 00:04:23.090 align:start position:0% source so he started the open PGP 00:04:23.090 --> 00:04:27.510 align:start position:0% source so he started the open PGP initiative<00:04:24.520> then<00:04:25.520> around<00:04:25.750> 2014<00:04:26.750> is<00:04:26.960> when 00:04:27.510 --> 00:04:27.520 align:start position:0% initiative then around 2014 is when 00:04:27.520 --> 00:04:30.550 align:start position:0% initiative then around 2014 is when elliptic<00:04:28.520> Kirk<00:04:28.699> ography<00:04:29.449> was<00:04:29.630> added<00:04:29.930> to<00:04:30.080> the 00:04:30.550 --> 00:04:30.560 align:start position:0% elliptic Kirk ography was added to the 00:04:30.560 --> 00:04:33.189 align:start position:0% elliptic Kirk ography was added to the particular<00:04:31.009> spec<00:04:31.280> which<00:04:31.849> is<00:04:32.000> much<00:04:32.509> lighter 00:04:33.189 --> 00:04:33.199 align:start position:0% particular spec which is much lighter 00:04:33.199 --> 00:04:36.219 align:start position:0% particular spec which is much lighter weight<00:04:33.500> than<00:04:34.060> the<00:04:35.060> older<00:04:35.720> form<00:04:35.900> it's<00:04:36.139> an 00:04:36.219 --> 00:04:36.229 align:start position:0% weight than the older form it's an 00:04:36.229 --> 00:04:38.159 align:start position:0% weight than the older form it's an encryption<00:04:36.500> at<00:04:36.710> the<00:04:36.770> protocol<00:04:37.099> used<00:04:37.400> like<00:04:37.610> RSA 00:04:38.159 --> 00:04:38.169 align:start position:0% encryption at the protocol used like RSA 00:04:38.169 --> 00:04:40.990 align:start position:0% encryption at the protocol used like RSA this<00:04:39.169> kind<00:04:39.410> of<00:04:39.470> lighter<00:04:39.830> footprint<00:04:40.340> a<00:04:40.580> lot<00:04:40.729> to 00:04:40.990 --> 00:04:41.000 align:start position:0% this kind of lighter footprint a lot to 00:04:41.000 --> 00:04:42.640 align:start position:0% this kind of lighter footprint a lot to be<00:04:41.150> more<00:04:41.630> realistically<00:04:42.139> used<00:04:42.410> in<00:04:42.590> the 00:04:42.640 --> 00:04:42.650 align:start position:0% be more realistically used in the 00:04:42.650 --> 00:04:46.749 align:start position:0% be more realistically used in the browser<00:04:43.150> so<00:04:44.150> open<00:04:44.539> PGP<00:04:44.720> j/s<00:04:45.440> was<00:04:45.770> about<00:04:46.639> the 00:04:46.749 --> 00:04:46.759 align:start position:0% browser so open PGP j/s was about the 00:04:46.759 --> 00:04:49.870 align:start position:0% browser so open PGP j/s was about the same<00:04:46.880> time<00:04:46.940> um<00:04:47.570> kind<00:04:48.530> of<00:04:48.699> opening<00:04:49.699> the<00:04:49.820> door 00:04:49.870 --> 00:04:49.880 align:start position:0% same time um kind of opening the door 00:04:49.880 --> 00:04:53.379 align:start position:0% same time um kind of opening the door for<00:04:50.030> an<00:04:50.479> encryption<00:04:52.030> screen<00:04:53.030> to<00:04:53.150> screen 00:04:53.379 --> 00:04:53.389 align:start position:0% for an encryption screen to screen 00:04:53.389 --> 00:04:57.610 align:start position:0% for an encryption screen to screen encryption<00:04:54.080> so<00:04:54.349> there's<00:04:55.130> no<00:04:56.229> you<00:04:57.229> know<00:04:57.289> it's 00:04:57.610 --> 00:04:57.620 align:start position:0% encryption so there's no you know it's 00:04:57.620 --> 00:04:59.110 align:start position:0% encryption so there's no you know it's it's<00:04:57.979> kind<00:04:58.160> of<00:04:58.190> the<00:04:58.370> the<00:04:58.669> standard<00:04:59.030> of 00:04:59.110 --> 00:04:59.120 align:start position:0% it's kind of the the standard of 00:04:59.120 --> 00:05:00.339 align:start position:0% it's kind of the the standard of encryption<00:04:59.389> that<00:04:59.630> we'd<00:04:59.750> like<00:04:59.960> to<00:05:00.020> have<00:05:00.110> today 00:05:00.339 --> 00:05:00.349 align:start position:0% encryption that we'd like to have today 00:05:00.349 --> 00:05:02.260 align:start position:0% encryption that we'd like to have today which<00:05:00.889> is<00:05:01.039> what<00:05:01.280> I<00:05:01.310> like<00:05:01.430> telegram<00:05:01.849> for<00:05:01.970> signal 00:05:02.260 --> 00:05:02.270 align:start position:0% which is what I like telegram for signal 00:05:02.270 --> 00:05:06.760 align:start position:0% which is what I like telegram for signal or<00:05:02.479> other<00:05:02.659> things<00:05:02.840> like<00:05:02.900> that<00:05:05.050> so<00:05:06.050> why<00:05:06.560> do<00:05:06.620> I 00:05:06.760 --> 00:05:06.770 align:start position:0% or other things like that so why do I 00:05:06.770 --> 00:05:09.279 align:start position:0% or other things like that so why do I need<00:05:06.889> to<00:05:06.949> bring<00:05:07.130> PGP<00:05:07.639> Aman<00:05:07.970> Atheneum<00:05:08.419> so<00:05:08.870> a 00:05:09.279 --> 00:05:09.289 align:start position:0% need to bring PGP Aman Atheneum so a 00:05:09.289 --> 00:05:12.219 align:start position:0% need to bring PGP Aman Atheneum so a little<00:05:09.530> background<00:05:09.830> this<00:05:10.610> came<00:05:11.199> to<00:05:12.199> be 00:05:12.219 --> 00:05:12.229 align:start position:0% little background this came to be 00:05:12.229 --> 00:05:14.890 align:start position:0% little background this came to be because<00:05:12.590> of<00:05:12.919> specific<00:05:13.539> kind<00:05:14.539> of<00:05:14.570> business 00:05:14.890 --> 00:05:14.900 align:start position:0% because of specific kind of business 00:05:14.900 --> 00:05:19.060 align:start position:0% because of specific kind of business needs<00:05:15.080> that<00:05:15.320> Harris<00:05:15.500> had<00:05:15.530> um<00:05:17.289> so<00:05:18.289> in<00:05:18.770> kind<00:05:19.010> of 00:05:19.060 --> 00:05:19.070 align:start position:0% needs that Harris had um so in kind of 00:05:19.070 --> 00:05:22.360 align:start position:0% needs that Harris had um so in kind of the<00:05:19.699> history<00:05:20.000> like<00:05:20.270> Dex<00:05:20.750> development<00:05:21.370> the 00:05:22.360 --> 00:05:22.370 align:start position:0% the history like Dex development the 00:05:22.370 --> 00:05:24.339 align:start position:0% the history like Dex development the first<00:05:22.639> popular<00:05:23.150> Dex<00:05:23.330> is<00:05:23.479> like<00:05:23.750> ether<00:05:23.900> Delta 00:05:24.339 --> 00:05:24.349 align:start position:0% first popular Dex is like ether Delta 00:05:24.349 --> 00:05:28.029 align:start position:0% first popular Dex is like ether Delta all<00:05:25.250> the<00:05:25.400> information<00:05:25.909> was<00:05:26.150> held<00:05:26.479> on<00:05:27.050> like<00:05:27.889> in 00:05:28.029 --> 00:05:28.039 align:start position:0% all the information was held on like in 00:05:28.039 --> 00:05:30.339 align:start position:0% all the information was held on like in a<00:05:28.130> smart<00:05:28.340> contract<00:05:28.759> so<00:05:28.970> that<00:05:29.000> order<00:05:29.870> posting 00:05:30.339 --> 00:05:30.349 align:start position:0% a smart contract so that order posting 00:05:30.349 --> 00:05:32.620 align:start position:0% a smart contract so that order posting order<00:05:30.680> matching<00:05:30.860> and<00:05:31.460> order<00:05:32.000> settlement<00:05:32.449> all 00:05:32.620 --> 00:05:32.630 align:start position:0% order matching and order settlement all 00:05:32.630 --> 00:05:35.469 align:start position:0% order matching and order settlement all happened<00:05:32.990> on<00:05:33.110> chain<00:05:33.380> um<00:05:33.759> kind<00:05:34.759> of<00:05:34.820> second 00:05:35.469 --> 00:05:35.479 align:start position:0% happened on chain um kind of second 00:05:35.479 --> 00:05:39.490 align:start position:0% happened on chain um kind of second generation<00:05:36.490> Dex<00:05:37.490> is<00:05:37.729> had<00:05:38.720> some<00:05:39.050> improvements 00:05:39.490 --> 00:05:39.500 align:start position:0% generation Dex is had some improvements 00:05:39.500 --> 00:05:42.879 align:start position:0% generation Dex is had some improvements upon<00:05:39.590> this<00:05:39.919> to<00:05:40.009> save<00:05:40.190> gas<00:05:40.400> so<00:05:41.180> um<00:05:41.889> protocols 00:05:42.879 --> 00:05:42.889 align:start position:0% upon this to save gas so um protocols 00:05:42.889 --> 00:05:47.170 align:start position:0% upon this to save gas so um protocols like<00:05:43.190> pair<00:05:43.599> Swasey<00:05:44.599> rho<00:05:44.659> x<00:05:44.840> 8x<00:05:45.580> DX<00:05:46.580> is<00:05:46.909> hydra 00:05:47.170 --> 00:05:47.180 align:start position:0% like pair Swasey rho x 8x DX is hydra 00:05:47.180 --> 00:05:48.620 align:start position:0% like pair Swasey rho x 8x DX is hydra protocol<00:05:47.570> and<00:05:47.900> do<00:05:48.139> i 00:05:48.620 --> 00:05:48.630 align:start position:0% protocol and do i 00:05:48.630 --> 00:05:51.800 align:start position:0% protocol and do i where<00:05:49.230> is<00:05:49.380> all<00:05:49.980> kind<00:05:50.400> of<00:05:50.460> used<00:05:50.790> a<00:05:51.180> similar 00:05:51.800 --> 00:05:51.810 align:start position:0% where is all kind of used a similar 00:05:51.810 --> 00:05:54.560 align:start position:0% where is all kind of used a similar approach<00:05:52.110> for<00:05:52.530> a<00:05:52.560> gas<00:05:52.740> saving<00:05:53.160> where<00:05:53.460> an<00:05:54.330> order 00:05:54.560 --> 00:05:54.570 align:start position:0% approach for a gas saving where an order 00:05:54.570 --> 00:05:59.000 align:start position:0% approach for a gas saving where an order is<00:05:54.720> signed<00:05:54.930> off<00:05:55.650> chain<00:05:56.150> its<00:05:57.830> first<00:05:58.830> in 00:05:59.000 --> 00:05:59.010 align:start position:0% is signed off chain its first in 00:05:59.010 --> 00:06:00.680 align:start position:0% is signed off chain its first in somewhere<00:05:59.340> matched<00:05:59.820> off<00:06:00.060> chain<00:06:00.330> and<00:06:00.600> then 00:06:00.680 --> 00:06:00.690 align:start position:0% somewhere matched off chain and then 00:06:00.690 --> 00:06:03.890 align:start position:0% somewhere matched off chain and then settled<00:06:01.020> on<00:06:01.170> chain<00:06:01.410> on<00:06:02.000> so<00:06:03.000> on<00:06:03.360> Harris<00:06:03.660> off<00:06:03.750> in 00:06:03.890 --> 00:06:03.900 align:start position:0% settled on chain on so on Harris off in 00:06:03.900 --> 00:06:07.310 align:start position:0% settled on chain on so on Harris off in particular<00:06:04.320> but<00:06:04.820> the<00:06:05.820> way<00:06:05.940> that<00:06:06.210> the<00:06:06.960> protocol 00:06:07.310 --> 00:06:07.320 align:start position:0% particular but the way that the protocol 00:06:07.320 --> 00:06:10.430 align:start position:0% particular but the way that the protocol works<00:06:07.470> is<00:06:07.770> that<00:06:08.630> order<00:06:09.630> posting<00:06:10.050> happens 00:06:10.430 --> 00:06:10.440 align:start position:0% works is that order posting happens 00:06:10.440 --> 00:06:12.320 align:start position:0% works is that order posting happens peered<00:06:10.680> up<00:06:10.770> here<00:06:10.980> so<00:06:11.370> makers<00:06:11.940> sent<00:06:12.180> orders 00:06:12.320 --> 00:06:12.330 align:start position:0% peered up here so makers sent orders 00:06:12.330 --> 00:06:15.230 align:start position:0% peered up here so makers sent orders directly<00:06:12.900> to<00:06:13.080> takers<00:06:13.760> matching<00:06:14.760> happens<00:06:15.060> when 00:06:15.230 --> 00:06:15.240 align:start position:0% directly to takers matching happens when 00:06:15.240 --> 00:06:16.550 align:start position:0% directly to takers matching happens when the<00:06:15.330> taker<00:06:15.510> decides<00:06:15.870> that<00:06:16.020> they<00:06:16.140> want<00:06:16.320> to<00:06:16.380> fill 00:06:16.550 --> 00:06:16.560 align:start position:0% the taker decides that they want to fill 00:06:16.560 --> 00:06:18.470 align:start position:0% the taker decides that they want to fill the<00:06:16.650> order<00:06:16.920> and<00:06:17.160> then<00:06:17.340> the<00:06:17.790> actual<00:06:18.030> settlement 00:06:18.470 --> 00:06:18.480 align:start position:0% the order and then the actual settlement 00:06:18.480 --> 00:06:21.100 align:start position:0% the order and then the actual settlement happens<00:06:18.960> when<00:06:19.110> the<00:06:19.200> word<00:06:19.350> is<00:06:19.470> filled<00:06:19.680> on<00:06:19.830> chain 00:06:21.100 --> 00:06:21.110 align:start position:0% happens when the word is filled on chain 00:06:21.110 --> 00:06:23.630 align:start position:0% happens when the word is filled on chain but<00:06:22.110> since<00:06:22.410> all<00:06:22.650> of<00:06:22.680> this<00:06:22.830> is<00:06:23.010> being<00:06:23.190> moved<00:06:23.460> off 00:06:23.630 --> 00:06:23.640 align:start position:0% but since all of this is being moved off 00:06:23.640 --> 00:06:26.330 align:start position:0% but since all of this is being moved off chain<00:06:24.060> into<00:06:24.660> messaging<00:06:25.080> that<00:06:25.560> messaging<00:06:26.040> has 00:06:26.330 --> 00:06:26.340 align:start position:0% chain into messaging that messaging has 00:06:26.340 --> 00:06:32.300 align:start position:0% chain into messaging that messaging has to<00:06:26.640> happen<00:06:27.330> somewhere<00:06:27.900> um<00:06:28.370> so<00:06:29.370> okay<00:06:31.250> there's<00:06:32.250> a 00:06:32.300 --> 00:06:32.310 align:start position:0% to happen somewhere um so okay there's a 00:06:32.310 --> 00:06:33.860 align:start position:0% to happen somewhere um so okay there's a possible<00:06:32.640> information<00:06:33.240> asymmetry<00:06:33.720> that 00:06:33.860 --> 00:06:33.870 align:start position:0% possible information asymmetry that 00:06:33.870 --> 00:06:35.630 align:start position:0% possible information asymmetry that arises<00:06:34.080> because<00:06:34.830> like<00:06:35.010> for<00:06:35.220> example<00:06:35.340> a 00:06:35.630 --> 00:06:35.640 align:start position:0% arises because like for example a 00:06:35.640 --> 00:06:37.580 align:start position:0% arises because like for example a Tarasov<00:06:36.000> is<00:06:36.180> hosting<00:06:36.570> the<00:06:37.170> messaging 00:06:37.580 --> 00:06:37.590 align:start position:0% Tarasov is hosting the messaging 00:06:37.590 --> 00:06:39.410 align:start position:0% Tarasov is hosting the messaging platform<00:06:38.010> then<00:06:38.520> we<00:06:38.640> kind<00:06:38.820> of<00:06:38.850> have<00:06:38.910> a<00:06:39.030> global 00:06:39.410 --> 00:06:39.420 align:start position:0% platform then we kind of have a global 00:06:39.420 --> 00:06:40.640 align:start position:0% platform then we kind of have a global view<00:06:39.570> into<00:06:39.840> all<00:06:39.870> the<00:06:40.140> messaging<00:06:40.500> that's 00:06:40.640 --> 00:06:40.650 align:start position:0% view into all the messaging that's 00:06:40.650 --> 00:06:42.620 align:start position:0% view into all the messaging that's happening<00:06:41.040> that<00:06:41.670> could<00:06:41.910> potentially<00:06:42.060> give<00:06:42.420> us 00:06:42.620 --> 00:06:42.630 align:start position:0% happening that could potentially give us 00:06:42.630 --> 00:06:44.900 align:start position:0% happening that could potentially give us like<00:06:42.780> an<00:06:42.900> unfair<00:06:43.290> advantage<00:06:43.380> of<00:06:43.860> like<00:06:44.040> you 00:06:44.900 --> 00:06:44.910 align:start position:0% like an unfair advantage of like you 00:06:44.910 --> 00:06:45.950 align:start position:0% like an unfair advantage of like you know<00:06:45.000> seeing<00:06:45.390> this<00:06:45.480> trade<00:06:45.690> that's<00:06:45.870> gonna 00:06:45.950 --> 00:06:45.960 align:start position:0% know seeing this trade that's gonna 00:06:45.960 --> 00:06:48.890 align:start position:0% know seeing this trade that's gonna happen<00:06:46.350> before<00:06:46.560> it<00:06:46.860> happens<00:06:47.390> or<00:06:48.390> you<00:06:48.780> know 00:06:48.890 --> 00:06:48.900 align:start position:0% happen before it happens or you know 00:06:48.900 --> 00:06:51.230 align:start position:0% happen before it happens or you know more<00:06:49.620> a<00:06:49.680> G<00:06:49.950> C<00:06:50.100> style<00:06:50.370> interaction<00:06:50.850> we<00:06:50.970> can<00:06:51.090> see 00:06:51.230 --> 00:06:51.240 align:start position:0% more a G C style interaction we can see 00:06:51.240 --> 00:06:54.640 align:start position:0% more a G C style interaction we can see people<00:06:51.540> negotiating<00:06:52.020> a<00:06:52.080> table<00:06:52.830> name<00:06:52.920> text<00:06:53.040> so 00:06:54.640 --> 00:06:54.650 align:start position:0% people negotiating a table name text so 00:06:54.650 --> 00:06:57.290 align:start position:0% people negotiating a table name text so so<00:06:55.650> you<00:06:55.740> kind<00:06:55.920> of<00:06:55.980> eliminate<00:06:56.820> this<00:06:57.000> kind<00:06:57.240> of 00:06:57.290 --> 00:06:57.300 align:start position:0% so you kind of eliminate this kind of 00:06:57.300 --> 00:07:00.080 align:start position:0% so you kind of eliminate this kind of unfair<00:06:57.840> angle<00:06:58.260> or<00:06:58.380> this<00:06:58.500> unfair<00:06:58.920> of<00:06:59.010> you<00:06:59.220> we 00:07:00.080 --> 00:07:00.090 align:start position:0% unfair angle or this unfair of you we 00:07:00.090 --> 00:07:02.960 align:start position:0% unfair angle or this unfair of you we need<00:07:00.210> encryption<00:07:00.720> so<00:07:01.320> if<00:07:01.920> all<00:07:02.490> messages 00:07:02.960 --> 00:07:02.970 align:start position:0% need encryption so if all messages 00:07:02.970 --> 00:07:04.610 align:start position:0% need encryption so if all messages between<00:07:03.150> makers<00:07:03.630> and<00:07:03.780> takers<00:07:03.870> are<00:07:04.170> encrypted 00:07:04.610 --> 00:07:04.620 align:start position:0% between makers and takers are encrypted 00:07:04.620 --> 00:07:07.940 align:start position:0% between makers and takers are encrypted then<00:07:06.080> they<00:07:07.080> are<00:07:07.140> the<00:07:07.260> only<00:07:07.380> ones<00:07:07.560> who<00:07:07.680> are<00:07:07.740> able 00:07:07.940 --> 00:07:07.950 align:start position:0% then they are the only ones who are able 00:07:07.950 --> 00:07:09.770 align:start position:0% then they are the only ones who are able to<00:07:07.980> see<00:07:08.160> it<00:07:08.310> and<00:07:08.490> there<00:07:09.210> isn't<00:07:09.450> a<00:07:09.480> kind<00:07:09.690> of 00:07:09.770 --> 00:07:09.780 align:start position:0% to see it and there isn't a kind of 00:07:09.780 --> 00:07:13.010 align:start position:0% to see it and there isn't a kind of global<00:07:10.020> view<00:07:10.380> to<00:07:11.190> exploit<00:07:11.580> from<00:07:12.510> the<00:07:12.660> angle<00:07:12.930> of 00:07:13.010 --> 00:07:13.020 align:start position:0% global view to exploit from the angle of 00:07:13.020 --> 00:07:16.100 align:start position:0% global view to exploit from the angle of being<00:07:13.230> a<00:07:13.350> more<00:07:14.010> technical<00:07:14.370> party<00:07:14.730> or<00:07:15.050> kind<00:07:16.050> of 00:07:16.100 --> 00:07:16.110 align:start position:0% being a more technical party or kind of 00:07:16.110 --> 00:07:18.590 align:start position:0% being a more technical party or kind of having<00:07:16.350> a<00:07:16.410> global<00:07:16.620> access<00:07:17.430> to<00:07:17.580> the<00:07:17.670> system<00:07:17.970> um 00:07:18.590 --> 00:07:18.600 align:start position:0% having a global access to the system um 00:07:18.600 --> 00:07:20.840 align:start position:0% having a global access to the system um so<00:07:19.470> we<00:07:19.590> need<00:07:19.710> both<00:07:19.860> encryption<00:07:20.610> for<00:07:20.730> that 00:07:20.840 --> 00:07:20.850 align:start position:0% so we need both encryption for that 00:07:20.850 --> 00:07:21.680 align:start position:0% so we need both encryption for that reason<00:07:21.180> and<00:07:21.360> then<00:07:21.450> we<00:07:21.510> need<00:07:21.630> an 00:07:21.680 --> 00:07:21.690 align:start position:0% reason and then we need an 00:07:21.690 --> 00:07:24.620 align:start position:0% reason and then we need an authentication<00:07:22.140> to<00:07:23.330> basically<00:07:24.330> tie<00:07:24.570> the 00:07:24.620 --> 00:07:24.630 align:start position:0% authentication to basically tie the 00:07:24.630 --> 00:07:26.030 align:start position:0% authentication to basically tie the messages<00:07:25.170> that<00:07:25.200> are<00:07:25.380> created<00:07:25.860> to<00:07:26.010> a 00:07:26.030 --> 00:07:26.040 align:start position:0% messages that are created to a 00:07:26.040 --> 00:07:28.880 align:start position:0% messages that are created to a particular<00:07:26.520> thing<00:07:26.670> address<00:07:27.210> um<00:07:27.420> so<00:07:28.410> that<00:07:28.590> if 00:07:28.880 --> 00:07:28.890 align:start position:0% particular thing address um so that if 00:07:28.890 --> 00:07:31.150 align:start position:0% particular thing address um so that if somebody<00:07:29.130> is<00:07:29.610> being<00:07:30.000> abusive<00:07:30.390> messages 00:07:31.150 --> 00:07:31.160 align:start position:0% somebody is being abusive messages 00:07:31.160 --> 00:07:32.890 align:start position:0% somebody is being abusive messages they<00:07:31.250> send<00:07:31.490> for<00:07:31.610> example<00:07:32.060> trying<00:07:32.300> to<00:07:32.390> ddos<00:07:32.660> the 00:07:32.890 --> 00:07:32.900 align:start position:0% they send for example trying to ddos the 00:07:32.900 --> 00:07:34.960 align:start position:0% they send for example trying to ddos the network<00:07:33.200> we<00:07:33.770> can<00:07:33.800> say<00:07:34.100> okay<00:07:34.370> these<00:07:34.550> messages 00:07:34.960 --> 00:07:34.970 align:start position:0% network we can say okay these messages 00:07:34.970 --> 00:07:37.180 align:start position:0% network we can say okay these messages are<00:07:35.270> cryptographically<00:07:36.140> verifiable<00:07:37.040> as 00:07:37.180 --> 00:07:37.190 align:start position:0% are cryptographically verifiable as 00:07:37.190 --> 00:07:39.970 align:start position:0% are cryptographically verifiable as having<00:07:37.460> come<00:07:37.640> from<00:07:37.730> this<00:07:37.880> address<00:07:38.150> um<00:07:38.980> we're 00:07:39.970 --> 00:07:39.980 align:start position:0% having come from this address um we're 00:07:39.980 --> 00:07:42.130 align:start position:0% having come from this address um we're gonna<00:07:40.070> like<00:07:40.370> disable<00:07:40.850> you<00:07:41.300> know<00:07:41.420> how<00:07:41.870> to<00:07:41.930> does 00:07:42.130 --> 00:07:42.140 align:start position:0% gonna like disable you know how to does 00:07:42.140 --> 00:07:43.540 align:start position:0% gonna like disable you know how to does can't<00:07:42.350> send<00:07:42.560> messages<00:07:42.860> anymore<00:07:43.070> and<00:07:43.370> then<00:07:43.490> we 00:07:43.540 --> 00:07:43.550 align:start position:0% can't send messages anymore and then we 00:07:43.550 --> 00:07:45.370 align:start position:0% can't send messages anymore and then we can<00:07:43.700> kind<00:07:43.850> of<00:07:43.880> see<00:07:44.090> if<00:07:44.660> assets<00:07:45.050> transferred 00:07:45.370 --> 00:07:45.380 align:start position:0% can kind of see if assets transferred 00:07:45.380 --> 00:07:46.480 align:start position:0% can kind of see if assets transferred between<00:07:45.650> that<00:07:45.860> addressed<00:07:46.160> and<00:07:46.310> another 00:07:46.480 --> 00:07:46.490 align:start position:0% between that addressed and another 00:07:46.490 --> 00:07:48.310 align:start position:0% between that addressed and another address<00:07:46.700> we<00:07:47.030> can<00:07:47.210> you<00:07:47.540> know<00:07:47.630> basically<00:07:48.080> figure 00:07:48.310 --> 00:07:48.320 align:start position:0% address we can you know basically figure 00:07:48.320 --> 00:07:51.070 align:start position:0% address we can you know basically figure out<00:07:48.440> Q's<00:07:49.000> using<00:07:50.000> the<00:07:50.090> network<00:07:50.330> or<00:07:50.750> how<00:07:50.840> some 00:07:51.070 --> 00:07:51.080 align:start position:0% out Q's using the network or how some 00:07:51.080 --> 00:07:53.080 align:start position:0% out Q's using the network or how some standard<00:07:51.560> where<00:07:52.130> we<00:07:52.160> can<00:07:52.460> have<00:07:52.640> economic 00:07:53.080 --> 00:07:53.090 align:start position:0% standard where we can have economic 00:07:53.090 --> 00:07:54.670 align:start position:0% standard where we can have economic incentives<00:07:53.690> for<00:07:53.870> behaving<00:07:54.260> correctly 00:07:54.670 --> 00:07:54.680 align:start position:0% incentives for behaving correctly 00:07:54.680 --> 00:07:58.510 align:start position:0% incentives for behaving correctly um<00:07:55.300> so<00:07:56.530> obviously<00:07:57.530> uh<00:07:57.620> if<00:07:58.040> my<00:07:58.160> authentication 00:07:58.510 --> 00:07:58.520 align:start position:0% um so obviously uh if my authentication 00:07:58.520 --> 00:08:01.530 align:start position:0% um so obviously uh if my authentication I<00:07:58.910> just<00:07:59.150> mean<00:07:59.270> a<00:07:59.300> signature<00:08:00.050> verification<00:08:00.320> of 00:08:01.530 --> 00:08:01.540 align:start position:0% I just mean a signature verification of 00:08:01.540 --> 00:08:04.780 align:start position:0% I just mean a signature verification of messages<00:08:02.540> um<00:08:03.160> so<00:08:04.160> there's<00:08:04.490> a<00:08:04.580> lot<00:08:04.760> of 00:08:04.780 --> 00:08:04.790 align:start position:0% messages um so there's a lot of 00:08:04.790 --> 00:08:06.580 align:start position:0% messages um so there's a lot of different<00:08:05.240> cryptographic<00:08:05.660> protocols<00:08:06.410> that 00:08:06.580 --> 00:08:06.590 align:start position:0% different cryptographic protocols that 00:08:06.590 --> 00:08:08.200 align:start position:0% different cryptographic protocols that you<00:08:06.710> can<00:08:06.860> use<00:08:07.070> for<00:08:07.310> your<00:08:07.460> authentication<00:08:07.760> and 00:08:08.200 --> 00:08:08.210 align:start position:0% you can use for your authentication and 00:08:08.210 --> 00:08:11.410 align:start position:0% you can use for your authentication and encryption<00:08:08.330> of<00:08:09.220> messaging<00:08:10.220> but<00:08:10.550> a<00:08:10.610> PGP<00:08:11.090> seems 00:08:11.410 --> 00:08:11.420 align:start position:0% encryption of messaging but a PGP seems 00:08:11.420 --> 00:08:14.230 align:start position:0% encryption of messaging but a PGP seems like<00:08:11.660> the<00:08:11.900> right<00:08:12.140> choice<00:08:12.410> for<00:08:13.240> multiple 00:08:14.230 --> 00:08:14.240 align:start position:0% like the right choice for multiple 00:08:14.240 --> 00:08:17.260 align:start position:0% like the right choice for multiple reasons<00:08:15.520> one<00:08:16.520> of<00:08:16.550> the<00:08:16.640> main<00:08:16.670> ones<00:08:16.940> is<00:08:17.060> that 00:08:17.260 --> 00:08:17.270 align:start position:0% reasons one of the main ones is that 00:08:17.270 --> 00:08:19.990 align:start position:0% reasons one of the main ones is that it's<00:08:17.390> the<00:08:17.600> right<00:08:17.810> age<00:08:18.110> and<00:08:18.680> what<00:08:19.640> I<00:08:19.670> mean<00:08:19.880> by 00:08:19.990 --> 00:08:20.000 align:start position:0% it's the right age and what I mean by 00:08:20.000 --> 00:08:21.550 align:start position:0% it's the right age and what I mean by that<00:08:20.030> is<00:08:20.270> that<00:08:20.300> it's<00:08:20.870> been<00:08:21.050> around<00:08:21.170> long 00:08:21.550 --> 00:08:21.560 align:start position:0% that is that it's been around long 00:08:21.560 --> 00:08:26.110 align:start position:0% that is that it's been around long enough<00:08:21.590> that<00:08:22.130> it's<00:08:22.550> it's<00:08:23.090> fairly<00:08:23.450> safe<00:08:24.460> it<00:08:25.460> is 00:08:26.110 --> 00:08:26.120 align:start position:0% enough that it's it's fairly safe it is 00:08:26.120 --> 00:08:30.070 align:start position:0% enough that it's it's fairly safe it is um<00:08:26.990> you<00:08:27.710> know<00:08:27.800> very<00:08:28.400> robust<00:08:28.760> it's<00:08:29.570> used<00:08:29.900> all 00:08:30.070 --> 00:08:30.080 align:start position:0% um you know very robust it's used all 00:08:30.080 --> 00:08:33.040 align:start position:0% um you know very robust it's used all over<00:08:30.110> the<00:08:30.260> world<00:08:30.350> and<00:08:31.570> it's<00:08:32.570> been<00:08:32.630> around<00:08:32.780> long 00:08:33.040 --> 00:08:33.050 align:start position:0% over the world and it's been around long 00:08:33.050 --> 00:08:34.209 align:start position:0% over the world and it's been around long enough<00:08:33.080> that<00:08:33.320> it<00:08:33.410> has<00:08:33.500> a<00:08:33.530> great<00:08:33.740> tool<00:08:33.979> you<00:08:34.160> can 00:08:34.209 --> 00:08:34.219 align:start position:0% enough that it has a great tool you can 00:08:34.219 --> 00:08:35.620 align:start position:0% enough that it has a great tool you can associated<00:08:34.729> with<00:08:34.820> it<00:08:35.030> which<00:08:35.120> kind<00:08:35.360> of<00:08:35.419> like 00:08:35.620 --> 00:08:35.630 align:start position:0% associated with it which kind of like 00:08:35.630 --> 00:08:37.480 align:start position:0% associated with it which kind of like helps<00:08:36.229> on<00:08:36.320> the<00:08:36.410> developer<00:08:36.860> lived<00:08:37.039> events<00:08:37.370> my 00:08:37.480 --> 00:08:37.490 align:start position:0% helps on the developer lived events my 00:08:37.490 --> 00:08:39.790 align:start position:0% helps on the developer lived events my hair<00:08:37.669> vertical<00:08:38.030> like<00:08:38.150> this<00:08:38.530> but<00:08:39.530> then<00:08:39.680> it's 00:08:39.790 --> 00:08:39.800 align:start position:0% hair vertical like this but then it's 00:08:39.800 --> 00:08:42.700 align:start position:0% hair vertical like this but then it's also<00:08:39.950> simultaneously<00:08:40.610> new<00:08:41.150> enough<00:08:41.419> that<00:08:41.840> you 00:08:42.700 --> 00:08:42.710 align:start position:0% also simultaneously new enough that you 00:08:42.710 --> 00:08:45.190 align:start position:0% also simultaneously new enough that you know<00:08:42.800> it<00:08:43.070> uses<00:08:43.550> cryptographic<00:08:44.480> algorithms 00:08:45.190 --> 00:08:45.200 align:start position:0% know it uses cryptographic algorithms 00:08:45.200 --> 00:08:47.020 align:start position:0% know it uses cryptographic algorithms like<00:08:45.470> you<00:08:45.710> know<00:08:45.800> with<00:08:46.070> elliptic<00:08:46.790> curve 00:08:47.020 --> 00:08:47.030 align:start position:0% like you know with elliptic curve 00:08:47.030 --> 00:08:48.880 align:start position:0% like you know with elliptic curve cryptography<00:08:47.120> which<00:08:47.990> is<00:08:48.140> like<00:08:48.320> wait<00:08:48.650> enough 00:08:48.880 --> 00:08:48.890 align:start position:0% cryptography which is like wait enough 00:08:48.890 --> 00:08:50.800 align:start position:0% cryptography which is like wait enough to<00:08:49.040> use<00:08:49.160> in<00:08:49.280> the<00:08:49.340> browser<00:08:49.580> without<00:08:49.820> negatively 00:08:50.800 --> 00:08:50.810 align:start position:0% to use in the browser without negatively 00:08:50.810 --> 00:08:55.390 align:start position:0% to use in the browser without negatively impacting<00:08:50.930> and<00:08:51.770> user<00:08:52.310> screens 00:08:55.390 --> 00:08:55.400 align:start position:0% 00:08:55.400 --> 00:08:57.950 align:start position:0% okay<00:08:56.400> so<00:08:57.270> that's<00:08:57.420> kind<00:08:57.570> of<00:08:57.660> like<00:08:57.750> the 00:08:57.950 --> 00:08:57.960 align:start position:0% okay so that's kind of like the 00:08:57.960 --> 00:09:00.560 align:start position:0% okay so that's kind of like the high-level<00:08:58.320> view<00:08:58.560> of<00:08:58.880> why<00:08:59.880> we<00:09:00.150> needed<00:09:00.330> to 00:09:00.560 --> 00:09:00.570 align:start position:0% high-level view of why we needed to 00:09:00.570 --> 00:09:03.050 align:start position:0% high-level view of why we needed to implement<00:09:01.380> this<00:09:01.770> trustless<00:09:02.370> version<00:09:02.700> of<00:09:02.790> PGP 00:09:03.050 --> 00:09:03.060 align:start position:0% implement this trustless version of PGP 00:09:03.060 --> 00:09:05.390 align:start position:0% implement this trustless version of PGP on<00:09:03.240> ethereum<00:09:03.450> so<00:09:03.930> we're<00:09:04.530> going<00:09:04.740> to<00:09:04.830> zoom<00:09:05.010> you 00:09:05.390 --> 00:09:05.400 align:start position:0% on ethereum so we're going to zoom you 00:09:05.400 --> 00:09:07.070 align:start position:0% on ethereum so we're going to zoom you zoom<00:09:05.610> in<00:09:05.760> a<00:09:05.790> little<00:09:05.970> bit<00:09:06.150> and<00:09:06.390> talk<00:09:06.510> about<00:09:06.570> kind 00:09:07.070 --> 00:09:07.080 align:start position:0% zoom in a little bit and talk about kind 00:09:07.080 --> 00:09:09.890 align:start position:0% zoom in a little bit and talk about kind of<00:09:07.170> a<00:09:07.290> specific<00:09:07.530> implementation<00:09:08.520> and<00:09:08.730> how<00:09:09.660> it 00:09:09.890 --> 00:09:09.900 align:start position:0% of a specific implementation and how it 00:09:09.900 --> 00:09:13.100 align:start position:0% of a specific implementation and how it how<00:09:10.170> it<00:09:10.200> looks<00:09:10.470> and<00:09:10.650> feels<00:09:10.800> for<00:09:11.100> you<00:09:11.130> um<00:09:11.990> so<00:09:12.990> the 00:09:13.100 --> 00:09:13.110 align:start position:0% how it looks and feels for you um so the 00:09:13.110 --> 00:09:15.560 align:start position:0% how it looks and feels for you um so the first<00:09:13.320> step<00:09:13.950> in<00:09:14.100> that<00:09:14.130> is<00:09:14.520> a<00:09:14.580> key<00:09:15.150> generation 00:09:15.560 --> 00:09:15.570 align:start position:0% first step in that is a key generation 00:09:15.570 --> 00:09:19.580 align:start position:0% first step in that is a key generation in<00:09:15.960> recovery<00:09:16.380> so<00:09:17.750> what<00:09:18.750> this<00:09:18.930> means<00:09:18.990> is<00:09:19.560> that 00:09:19.580 --> 00:09:19.590 align:start position:0% in recovery so what this means is that 00:09:19.590 --> 00:09:22.250 align:start position:0% in recovery so what this means is that we're<00:09:19.980> trying<00:09:20.310> to<00:09:21.020> deterministic<00:09:22.020> lead 00:09:22.250 --> 00:09:22.260 align:start position:0% we're trying to deterministic lead 00:09:22.260 --> 00:09:25.550 align:start position:0% we're trying to deterministic lead generate<00:09:23.100> the<00:09:23.430> PGP<00:09:24.000> keep<00:09:24.360> it<00:09:24.570> from<00:09:25.410> an 00:09:25.550 --> 00:09:25.560 align:start position:0% generate the PGP keep it from an 00:09:25.560 --> 00:09:27.560 align:start position:0% generate the PGP keep it from an Athenian<00:09:25.980> key<00:09:26.160> pairs<00:09:26.400> such<00:09:26.670> that<00:09:26.940> we<00:09:27.420> can 00:09:27.560 --> 00:09:27.570 align:start position:0% Athenian key pairs such that we can 00:09:27.570 --> 00:09:29.660 align:start position:0% Athenian key pairs such that we can verify<00:09:27.780> that<00:09:28.050> this<00:09:28.980> is<00:09:29.130> pyramid<00:09:29.370> rest 00:09:29.660 --> 00:09:29.670 align:start position:0% verify that this is pyramid rest 00:09:29.670 --> 00:09:32.120 align:start position:0% verify that this is pyramid rest generated<00:09:30.300> this<00:09:30.390> PGP<00:09:30.900> key<00:09:30.930> and<00:09:31.530> that<00:09:31.860> if<00:09:32.010> the 00:09:32.120 --> 00:09:32.130 align:start position:0% generated this PGP key and that if the 00:09:32.130 --> 00:09:35.360 align:start position:0% generated this PGP key and that if the PGP<00:09:32.580> key<00:09:32.610> is<00:09:32.880> lost<00:09:33.290> for<00:09:34.290> whatever<00:09:34.440> reason<00:09:34.890> we 00:09:35.360 --> 00:09:35.370 align:start position:0% PGP key is lost for whatever reason we 00:09:35.370 --> 00:09:37.070 align:start position:0% PGP key is lost for whatever reason we can't<00:09:35.580> regenerate<00:09:36.090> it<00:09:36.390> as<00:09:36.570> long<00:09:36.750> as<00:09:36.900> you<00:09:36.960> have 00:09:37.070 --> 00:09:37.080 align:start position:0% can't regenerate it as long as you have 00:09:37.080 --> 00:09:39.290 align:start position:0% can't regenerate it as long as you have control<00:09:37.410> of<00:09:37.440> the<00:09:37.650> wallet<00:09:37.950> so<00:09:38.580> kind<00:09:39.180> of<00:09:39.210> a 00:09:39.290 --> 00:09:39.300 align:start position:0% control of the wallet so kind of a 00:09:39.300 --> 00:09:41.300 align:start position:0% control of the wallet so kind of a practical<00:09:39.750> example<00:09:39.840> of<00:09:40.200> this<00:09:40.350> is<00:09:40.620> if<00:09:41.130> I<00:09:41.280> have 00:09:41.300 --> 00:09:41.310 align:start position:0% practical example of this is if I have 00:09:41.310 --> 00:09:44.600 align:start position:0% practical example of this is if I have my<00:09:41.970> ledger<00:09:42.210> and<00:09:42.570> I<00:09:43.050> generate<00:09:43.500> my<00:09:43.650> keys<00:09:43.920> on<00:09:44.340> one 00:09:44.600 --> 00:09:44.610 align:start position:0% my ledger and I generate my keys on one 00:09:44.610 --> 00:09:46.700 align:start position:0% my ledger and I generate my keys on one computer<00:09:44.940> and<00:09:45.300> I<00:09:45.420> use<00:09:45.630> those<00:09:45.780> keys<00:09:46.080> to<00:09:46.350> read<00:09:46.530> my 00:09:46.700 --> 00:09:46.710 align:start position:0% computer and I use those keys to read my 00:09:46.710 --> 00:09:49.460 align:start position:0% computer and I use those keys to read my encrypted<00:09:46.980> messages<00:09:47.520> I<00:09:47.730> can<00:09:48.360> then<00:09:48.540> terminate 00:09:49.460 --> 00:09:49.470 align:start position:0% encrypted messages I can then terminate 00:09:49.470 --> 00:09:50.690 align:start position:0% encrypted messages I can then terminate that<00:09:49.620> session<00:09:49.830> wipe<00:09:50.220> out<00:09:50.340> that<00:09:50.370> information 00:09:50.690 --> 00:09:50.700 align:start position:0% that session wipe out that information 00:09:50.700 --> 00:09:53.480 align:start position:0% that session wipe out that information plug<00:09:51.270> my<00:09:51.390> ledger<00:09:51.600> into<00:09:51.840> another<00:09:52.110> computer<00:09:52.560> to 00:09:53.480 --> 00:09:53.490 align:start position:0% plug my ledger into another computer to 00:09:53.490 --> 00:09:55.490 align:start position:0% plug my ledger into another computer to regenerate<00:09:54.060> my<00:09:54.180> PGP<00:09:54.660> keys<00:09:54.900> and<00:09:55.170> use<00:09:55.260> them<00:09:55.470> to 00:09:55.490 --> 00:09:55.500 align:start position:0% regenerate my PGP keys and use them to 00:09:55.500 --> 00:09:57.500 align:start position:0% regenerate my PGP keys and use them to decrypt<00:09:55.830> the<00:09:55.980> same<00:09:56.130> messages<00:09:56.520> so<00:09:57.180> it's<00:09:57.330> kind 00:09:57.500 --> 00:09:57.510 align:start position:0% decrypt the same messages so it's kind 00:09:57.510 --> 00:10:00.350 align:start position:0% decrypt the same messages so it's kind of<00:09:57.600> a<00:09:57.840> stateless<00:09:58.830> in<00:09:59.130> a<00:09:59.250> way<00:09:59.400> it's 00:10:00.350 --> 00:10:00.360 align:start position:0% of a stateless in a way it's 00:10:00.360 --> 00:10:02.180 align:start position:0% of a stateless in a way it's deterministic<00:10:00.870> and<00:10:01.200> so<00:10:01.290> that's<00:10:01.470> just<00:10:01.560> kind<00:10:02.100> of 00:10:02.180 --> 00:10:02.190 align:start position:0% deterministic and so that's just kind of 00:10:02.190 --> 00:10:03.260 align:start position:0% deterministic and so that's just kind of one<00:10:02.280> of<00:10:02.370> the<00:10:02.430> properties<00:10:02.610> we<00:10:02.910> wanted<00:10:03.090> to<00:10:03.150> have 00:10:03.260 --> 00:10:03.270 align:start position:0% one of the properties we wanted to have 00:10:03.270 --> 00:10:07.160 align:start position:0% one of the properties we wanted to have in<00:10:03.420> the<00:10:03.480> system<00:10:03.840> on<00:10:04.580> the<00:10:05.580> the<00:10:06.030> next<00:10:06.180> step<00:10:06.900> after 00:10:07.160 --> 00:10:07.170 align:start position:0% in the system on the the next step after 00:10:07.170 --> 00:10:09.590 align:start position:0% in the system on the the next step after keys<00:10:07.530> are<00:10:07.710> generated<00:10:07.920> is<00:10:08.580> a<00:10:08.610> key<00:10:09.030> distribution 00:10:09.590 --> 00:10:09.600 align:start position:0% keys are generated is a key distribution 00:10:09.600 --> 00:10:12.170 align:start position:0% keys are generated is a key distribution and<00:10:09.720> lookup<00:10:09.990> so<00:10:10.680> if<00:10:11.130> I<00:10:11.310> want<00:10:11.580> to<00:10:11.640> send<00:10:11.850> a 00:10:12.170 --> 00:10:12.180 align:start position:0% and lookup so if I want to send a 00:10:12.180 --> 00:10:14.750 align:start position:0% and lookup so if I want to send a encrypted<00:10:12.900> message<00:10:13.170> to<00:10:13.620> you<00:10:13.860> by<00:10:14.280> knowing<00:10:14.730> your 00:10:14.750 --> 00:10:14.760 align:start position:0% encrypted message to you by knowing your 00:10:14.760 --> 00:10:16.700 align:start position:0% encrypted message to you by knowing your theum<00:10:15.180> address<00:10:15.420> I<00:10:15.660> have<00:10:16.080> to<00:10:16.200> have<00:10:16.290> some<00:10:16.530> way<00:10:16.680> to 00:10:16.700 --> 00:10:16.710 align:start position:0% theum address I have to have some way to 00:10:16.710 --> 00:10:18.290 align:start position:0% theum address I have to have some way to you<00:10:17.370> know<00:10:17.460> look<00:10:17.610> up<00:10:17.790> that<00:10:17.880> at<00:10:18.030> 3:00<00:10:18.180> in<00:10:18.270> the 00:10:18.290 --> 00:10:18.300 align:start position:0% you know look up that at 3:00 in the 00:10:18.300 --> 00:10:22.070 align:start position:0% you know look up that at 3:00 in the dress<00:10:18.540> and<00:10:19.070> find<00:10:20.070> here<00:10:20.190> PGP<00:10:20.610> key<00:10:20.640> and<00:10:21.240> I<00:10:21.570> need 00:10:22.070 --> 00:10:22.080 align:start position:0% dress and find here PGP key and I need 00:10:22.080 --> 00:10:23.510 align:start position:0% dress and find here PGP key and I need to<00:10:22.170> be<00:10:22.230> able<00:10:22.290> to<00:10:22.380> cryptographically<00:10:22.920> verify 00:10:23.510 --> 00:10:23.520 align:start position:0% to be able to cryptographically verify 00:10:23.520 --> 00:10:26.420 align:start position:0% to be able to cryptographically verify that<00:10:23.820> that<00:10:24.420> is<00:10:24.600> indeed<00:10:24.810> your<00:10:25.080> PGP<00:10:25.500> key<00:10:25.530> which<00:10:26.070> I 00:10:26.420 --> 00:10:26.430 align:start position:0% that that is indeed your PGP key which I 00:10:26.430 --> 00:10:28.160 align:start position:0% that that is indeed your PGP key which I can<00:10:26.730> then<00:10:26.760> use<00:10:27.150> that<00:10:27.360> public<00:10:27.570> key<00:10:27.930> to<00:10:27.960> encrypt 00:10:28.160 --> 00:10:28.170 align:start position:0% can then use that public key to encrypt 00:10:28.170 --> 00:10:31.190 align:start position:0% can then use that public key to encrypt a<00:10:28.470> message<00:10:28.500> and<00:10:28.920> send<00:10:29.070> it<00:10:29.190> to<00:10:29.630> so<00:10:30.630> there<00:10:31.050> needs 00:10:31.190 --> 00:10:31.200 align:start position:0% a message and send it to so there needs 00:10:31.200 --> 00:10:33.410 align:start position:0% a message and send it to so there needs to<00:10:31.290> be<00:10:31.350> some<00:10:31.650> sort<00:10:31.680> of<00:10:32.100> directory<00:10:32.940> basically 00:10:33.410 --> 00:10:33.420 align:start position:0% to be some sort of directory basically 00:10:33.420 --> 00:10:36.170 align:start position:0% to be some sort of directory basically the<00:10:33.930> initial<00:10:34.620> implement<00:10:35.250> implementation<00:10:36.090> of 00:10:36.170 --> 00:10:36.180 align:start position:0% the initial implement implementation of 00:10:36.180 --> 00:10:38.060 align:start position:0% the initial implement implementation of this<00:10:36.300> actually<00:10:36.900> for<00:10:37.500> us<00:10:37.530> was<00:10:37.740> a<00:10:37.770> smart 00:10:38.060 --> 00:10:38.070 align:start position:0% this actually for us was a smart 00:10:38.070 --> 00:10:40.700 align:start position:0% this actually for us was a smart contract<00:10:38.220> so<00:10:39.000> you<00:10:39.390> basically<00:10:39.630> stored<00:10:40.560> your 00:10:40.700 --> 00:10:40.710 align:start position:0% contract so you basically stored your 00:10:40.710 --> 00:10:45.530 align:start position:0% contract so you basically stored your PGP<00:10:41.160> key<00:10:41.360> on<00:10:42.360> I<00:10:42.990> give<00:10:43.170> us<00:10:43.700> took<00:10:44.700> that<00:10:44.850> ifs<00:10:45.270> hash 00:10:45.530 --> 00:10:45.540 align:start position:0% PGP key on I give us took that ifs hash 00:10:45.540 --> 00:10:47.720 align:start position:0% PGP key on I give us took that ifs hash of<00:10:45.900> that<00:10:46.080> key<00:10:46.260> and<00:10:46.500> sorry<00:10:46.890> the<00:10:47.100> smart<00:10:47.310> contract 00:10:47.720 --> 00:10:47.730 align:start position:0% of that key and sorry the smart contract 00:10:47.730 --> 00:10:49.970 align:start position:0% of that key and sorry the smart contract and<00:10:47.970> then<00:10:48.450> when<00:10:48.570> I<00:10:48.630> wanted<00:10:48.840> to<00:10:48.930> find<00:10:49.170> the<00:10:49.470> key 00:10:49.970 --> 00:10:49.980 align:start position:0% and then when I wanted to find the key 00:10:49.980 --> 00:10:51.340 align:start position:0% and then when I wanted to find the key associated<00:10:50.340> with<00:10:50.640> your<00:10:50.760> address 00:10:51.340 --> 00:10:51.350 align:start position:0% associated with your address 00:10:51.350 --> 00:10:54.280 align:start position:0% associated with your address look<00:10:51.500> it<00:10:51.620> up<00:10:51.650> in<00:10:51.830> a<00:10:51.890> smart<00:10:52.100> contract<00:10:52.280> um<00:10:53.290> pretty 00:10:54.280 --> 00:10:54.290 align:start position:0% look it up in a smart contract um pretty 00:10:54.290 --> 00:10:55.990 align:start position:0% look it up in a smart contract um pretty soon<00:10:54.560> then<00:10:54.830> we<00:10:54.950> discovered<00:10:55.370> that<00:10:55.550> there<00:10:55.880> is 00:10:55.990 --> 00:10:56.000 align:start position:0% soon then we discovered that there is 00:10:56.000 --> 00:10:58.630 align:start position:0% soon then we discovered that there is like<00:10:56.150> a<00:10:56.240> whole<00:10:56.420> swath<00:10:56.720> of<00:10:56.930> users<00:10:57.290> Hugh<00:10:58.010> didn't 00:10:58.630 --> 00:10:58.640 align:start position:0% like a whole swath of users Hugh didn't 00:10:58.640 --> 00:11:00.550 align:start position:0% like a whole swath of users Hugh didn't want<00:10:58.910> he<00:10:59.240> wanted<00:10:59.540> to<00:10:59.690> basically<00:11:00.050> try<00:11:00.500> an 00:11:00.550 --> 00:11:00.560 align:start position:0% want he wanted to basically try an 00:11:00.560 --> 00:11:02.650 align:start position:0% want he wanted to basically try an application<00:11:01.160> without<00:11:01.280> paying<00:11:01.820> gas<00:11:02.120> upfront 00:11:02.650 --> 00:11:02.660 align:start position:0% application without paying gas upfront 00:11:02.660 --> 00:11:04.990 align:start position:0% application without paying gas upfront um<00:11:03.010> you<00:11:04.010> know<00:11:04.100> as<00:11:04.250> soon<00:11:04.370> as<00:11:04.430> like<00:11:04.700> you<00:11:04.820> have<00:11:04.910> to 00:11:04.990 --> 00:11:05.000 align:start position:0% um you know as soon as like you have to 00:11:05.000 --> 00:11:06.580 align:start position:0% um you know as soon as like you have to pay<00:11:05.150> for<00:11:05.330> a<00:11:05.360> transaction<00:11:05.690> they<00:11:06.110> weren't<00:11:06.320> you 00:11:06.580 --> 00:11:06.590 align:start position:0% pay for a transaction they weren't you 00:11:06.590 --> 00:11:08.440 align:start position:0% pay for a transaction they weren't you know<00:11:06.740> as<00:11:06.950> interested<00:11:07.490> in<00:11:07.610> in<00:11:07.970> using<00:11:08.300> that 00:11:08.440 --> 00:11:08.450 align:start position:0% know as interested in in using that 00:11:08.450 --> 00:11:10.660 align:start position:0% know as interested in in using that application<00:11:08.540> so<00:11:09.260> um<00:11:09.920> there's<00:11:10.610> another 00:11:10.660 --> 00:11:10.670 align:start position:0% application so um there's another 00:11:10.670 --> 00:11:13.090 align:start position:0% application so um there's another alternative<00:11:11.270> way<00:11:11.810> of<00:11:11.870> storing<00:11:12.200> these<00:11:12.440> keys 00:11:13.090 --> 00:11:13.100 align:start position:0% alternative way of storing these keys 00:11:13.100 --> 00:11:16.360 align:start position:0% alternative way of storing these keys where<00:11:13.400> instead<00:11:13.850> of<00:11:14.170> storing<00:11:15.170> a<00:11:15.320> contract<00:11:15.860> you 00:11:16.360 --> 00:11:16.370 align:start position:0% where instead of storing a contract you 00:11:16.370 --> 00:11:19.270 align:start position:0% where instead of storing a contract you sign<00:11:16.820> it<00:11:17.030> so<00:11:17.570> that<00:11:17.810> you<00:11:18.020> can<00:11:18.200> verify<00:11:18.620> it<00:11:18.920> as 00:11:19.270 --> 00:11:19.280 align:start position:0% sign it so that you can verify it as 00:11:19.280 --> 00:11:21.250 align:start position:0% sign it so that you can verify it as yours<00:11:19.610> and<00:11:20.000> then<00:11:20.120> the<00:11:20.450> signature<00:11:20.780> together 00:11:21.250 --> 00:11:21.260 align:start position:0% yours and then the signature together 00:11:21.260 --> 00:11:22.720 align:start position:0% yours and then the signature together with<00:11:21.410> the<00:11:21.500> key<00:11:21.680> can<00:11:21.950> just<00:11:22.160> be<00:11:22.250> served<00:11:22.490> in<00:11:22.610> any 00:11:22.720 --> 00:11:22.730 align:start position:0% with the key can just be served in any 00:11:22.730 --> 00:11:25.240 align:start position:0% with the key can just be served in any database<00:11:22.970> and<00:11:23.560> since<00:11:24.560> that<00:11:24.650> signature<00:11:24.980> always 00:11:25.240 --> 00:11:25.250 align:start position:0% database and since that signature always 00:11:25.250 --> 00:11:26.980 align:start position:0% database and since that signature always exists<00:11:25.670> next<00:11:26.060> with<00:11:26.180> it<00:11:26.270> you<00:11:26.420> can<00:11:26.540> just<00:11:26.570> pull<00:11:26.750> it 00:11:26.980 --> 00:11:26.990 align:start position:0% exists next with it you can just pull it 00:11:26.990 --> 00:11:28.690 align:start position:0% exists next with it you can just pull it and<00:11:27.080> look<00:11:27.230> it<00:11:27.350> up<00:11:27.380> it<00:11:27.980> doesn't<00:11:28.130> have<00:11:28.340> the<00:11:28.490> same 00:11:28.690 --> 00:11:28.700 align:start position:0% and look it up it doesn't have the same 00:11:28.700 --> 00:11:30.610 align:start position:0% and look it up it doesn't have the same guarantee<00:11:29.480> you<00:11:29.600> availability<00:11:30.260> to<00:11:30.410> smart 00:11:30.610 --> 00:11:30.620 align:start position:0% guarantee you availability to smart 00:11:30.620 --> 00:11:32.860 align:start position:0% guarantee you availability to smart contracts<00:11:31.040> so<00:11:31.310> currently<00:11:31.880> that<00:11:32.150> database<00:11:32.570> is 00:11:32.860 --> 00:11:32.870 align:start position:0% contracts so currently that database is 00:11:32.870 --> 00:11:35.320 align:start position:0% contracts so currently that database is hosted<00:11:33.230> by<00:11:33.260> as<00:11:33.560> well<00:11:33.740> and<00:11:33.950> you<00:11:34.790> know<00:11:34.820> if<00:11:35.240> the 00:11:35.320 --> 00:11:35.330 align:start position:0% hosted by as well and you know if the 00:11:35.330 --> 00:11:36.730 align:start position:0% hosted by as well and you know if the Paris<00:11:35.510> walking<00:11:35.780> away<00:11:35.870> then<00:11:36.290> that<00:11:36.500> database 00:11:36.730 --> 00:11:36.740 align:start position:0% Paris walking away then that database 00:11:36.740 --> 00:11:39.580 align:start position:0% Paris walking away then that database wouldn't<00:11:37.310> be<00:11:37.370> hosted<00:11:37.760> but<00:11:38.090> for<00:11:38.810> those<00:11:39.020> user<00:11:39.350> is 00:11:39.580 --> 00:11:39.590 align:start position:0% wouldn't be hosted but for those user is 00:11:39.590 --> 00:11:40.930 align:start position:0% wouldn't be hosted but for those user is like<00:11:39.980> you<00:11:40.250> know<00:11:40.340> they<00:11:40.460> would<00:11:40.580> just<00:11:40.670> have<00:11:40.820> to 00:11:40.930 --> 00:11:40.940 align:start position:0% like you know they would just have to 00:11:40.940 --> 00:11:42.130 align:start position:0% like you know they would just have to regenerate<00:11:41.210> their<00:11:41.450> keys<00:11:41.660> and<00:11:41.840> they<00:11:41.900> can<00:11:42.050> begin 00:11:42.130 --> 00:11:42.140 align:start position:0% regenerate their keys and they can begin 00:11:42.140 --> 00:11:43.930 align:start position:0% regenerate their keys and they can begin using<00:11:42.350> the<00:11:42.560> system<00:11:42.860> again<00:11:43.100> so<00:11:43.580> there's<00:11:43.760> kind 00:11:43.930 --> 00:11:43.940 align:start position:0% using the system again so there's kind 00:11:43.940 --> 00:11:45.400 align:start position:0% using the system again so there's kind of<00:11:43.970> different<00:11:44.330> options<00:11:44.480> of<00:11:44.900> like<00:11:45.140> you<00:11:45.320> know 00:11:45.400 --> 00:11:45.410 align:start position:0% of different options of like you know 00:11:45.410 --> 00:11:47.530 align:start position:0% of different options of like you know based<00:11:45.650> on<00:11:45.890> like<00:11:46.130> the<00:11:46.310> longevity<00:11:47.090> the 00:11:47.530 --> 00:11:47.540 align:start position:0% based on like the longevity the 00:11:47.540 --> 00:11:52.570 align:start position:0% based on like the longevity the dependability<00:11:48.140> that<00:11:48.470> you<00:11:48.560> need<00:11:48.710> um<00:11:48.950> and<00:11:51.580> you 00:11:52.570 --> 00:11:52.580 align:start position:0% dependability that you need um and you 00:11:52.580 --> 00:11:54.130 align:start position:0% dependability that you need um and you know<00:11:52.670> the<00:11:52.820> level<00:11:53.150> of<00:11:53.330> trust<00:11:53.570> lessness<00:11:53.780> to<00:11:54.050> be 00:11:54.130 --> 00:11:54.140 align:start position:0% know the level of trust lessness to be 00:11:54.140 --> 00:11:55.720 align:start position:0% know the level of trust lessness to be desired<00:11:54.470> and<00:11:54.860> you<00:11:55.040> need<00:11:55.250> to<00:11:55.310> pay<00:11:55.520> more<00:11:55.700> for 00:11:55.720 --> 00:11:55.730 align:start position:0% desired and you need to pay more for 00:11:55.730 --> 00:11:57.520 align:start position:0% desired and you need to pay more for that<00:11:56.000> or<00:11:56.540> kind<00:11:56.750> of<00:11:56.780> have<00:11:56.960> more<00:11:57.230> of<00:11:57.290> a<00:11:57.350> low 00:11:57.520 --> 00:11:57.530 align:start position:0% that or kind of have more of a low 00:11:57.530 --> 00:12:01.510 align:start position:0% that or kind of have more of a low investment<00:11:57.770> alternatives<00:11:58.640> um<00:11:59.420> so<00:12:00.350> the<00:12:00.980> the 00:12:01.510 --> 00:12:01.520 align:start position:0% investment alternatives um so the the 00:12:01.520 --> 00:12:03.430 align:start position:0% investment alternatives um so the the threat<00:12:01.700> stuff<00:12:01.970> in<00:12:02.060> this<00:12:02.180> is<00:12:02.420> a<00:12:02.480> passive 00:12:03.430 --> 00:12:03.440 align:start position:0% threat stuff in this is a passive 00:12:03.440 --> 00:12:07.030 align:start position:0% threat stuff in this is a passive authentication<00:12:03.740> and<00:12:04.400> privacy<00:12:04.790> um<00:12:05.350> so<00:12:06.350> after 00:12:07.030 --> 00:12:07.040 align:start position:0% authentication and privacy um so after 00:12:07.040 --> 00:12:08.890 align:start position:0% authentication and privacy um so after everything's<00:12:07.520> set<00:12:07.730> up<00:12:07.760> basically<00:12:08.240> you<00:12:08.780> know 00:12:08.890 --> 00:12:08.900 align:start position:0% everything's set up basically you know 00:12:08.900 --> 00:12:11.740 align:start position:0% everything's set up basically you know keys<00:12:09.140> are<00:12:09.290> generated<00:12:10.210> they're<00:12:11.210> distributed 00:12:11.740 --> 00:12:11.750 align:start position:0% keys are generated they're distributed 00:12:11.750 --> 00:12:14.950 align:start position:0% keys are generated they're distributed and<00:12:11.990> they<00:12:12.470> can<00:12:12.620> be<00:12:12.710> looked<00:12:12.890> up<00:12:13.010> then<00:12:13.810> we<00:12:14.810> can 00:12:14.950 --> 00:12:14.960 align:start position:0% and they can be looked up then we can 00:12:14.960 --> 00:12:16.060 align:start position:0% and they can be looked up then we can use<00:12:15.110> them<00:12:15.260> at<00:12:15.350> the<00:12:15.440> application<00:12:15.950> level 00:12:16.060 --> 00:12:16.070 align:start position:0% use them at the application level 00:12:16.070 --> 00:12:18.340 align:start position:0% use them at the application level without<00:12:16.880> really<00:12:17.270> having<00:12:17.510> to<00:12:17.840> understand 00:12:18.340 --> 00:12:18.350 align:start position:0% without really having to understand 00:12:18.350 --> 00:12:20.470 align:start position:0% without really having to understand anything<00:12:18.590> about<00:12:18.800> the<00:12:19.300> you<00:12:20.300> know<00:12:20.360> the 00:12:20.470 --> 00:12:20.480 align:start position:0% anything about the you know the 00:12:20.480 --> 00:12:22.780 align:start position:0% anything about the you know the underlying<00:12:20.720> cryptography<00:12:21.470> so<00:12:21.740> just<00:12:22.520> all 00:12:22.780 --> 00:12:22.790 align:start position:0% underlying cryptography so just all 00:12:22.790 --> 00:12:24.870 align:start position:0% underlying cryptography so just all messages<00:12:23.210> between<00:12:23.600> computers<00:12:24.020> or<00:12:24.170> how<00:12:24.710> the 00:12:24.870 --> 00:12:24.880 align:start position:0% messages between computers or how the 00:12:24.880 --> 00:12:27.340 align:start position:0% messages between computers or how the simultaneous<00:12:25.880> guarantee<00:12:26.360> you<00:12:26.510> if<00:12:27.110> you 00:12:27.340 --> 00:12:27.350 align:start position:0% simultaneous guarantee you if you 00:12:27.350 --> 00:12:29.200 align:start position:0% simultaneous guarantee you if you receive<00:12:27.650> a<00:12:27.680> message<00:12:27.890> you<00:12:28.640> know<00:12:28.790> for<00:12:29.030> sure<00:12:29.060> that 00:12:29.200 --> 00:12:29.210 align:start position:0% receive a message you know for sure that 00:12:29.210 --> 00:12:31.240 align:start position:0% receive a message you know for sure that the<00:12:29.600> etherium<00:12:29.990> address<00:12:30.260> that<00:12:30.770> sent<00:12:31.040> you<00:12:31.100> that 00:12:31.240 --> 00:12:31.250 align:start position:0% the etherium address that sent you that 00:12:31.250 --> 00:12:34.300 align:start position:0% the etherium address that sent you that message<00:12:31.310> um<00:12:32.090> is<00:12:32.660> who<00:12:33.200> they<00:12:33.380> claim<00:12:33.800> to<00:12:33.830> be<00:12:34.040> and 00:12:34.300 --> 00:12:34.310 align:start position:0% message um is who they claim to be and 00:12:34.310 --> 00:12:36.550 align:start position:0% message um is who they claim to be and when<00:12:35.300> you<00:12:35.390> send<00:12:35.600> a<00:12:35.690> message<00:12:35.960> you<00:12:36.260> know<00:12:36.380> that 00:12:36.550 --> 00:12:36.560 align:start position:0% when you send a message you know that 00:12:36.560 --> 00:12:38.110 align:start position:0% when you send a message you know that nobody<00:12:36.920> other<00:12:37.160> than<00:12:37.310> the<00:12:37.490> etherium<00:12:37.880> address 00:12:38.110 --> 00:12:38.120 align:start position:0% nobody other than the etherium address 00:12:38.120 --> 00:12:40.710 align:start position:0% nobody other than the etherium address that<00:12:38.690> you<00:12:38.870> intend<00:12:39.200> to<00:12:39.260> read<00:12:39.440> it<00:12:39.530> will<00:12:39.740> read<00:12:39.890> it 00:12:40.710 --> 00:12:40.720 align:start position:0% that you intend to read it will read it 00:12:40.720 --> 00:12:44.730 align:start position:0% that you intend to read it will read it so<00:12:41.720> that's<00:12:41.870> kind<00:12:42.050> of<00:12:42.080> like<00:12:42.200> high-level<00:12:42.740> on 00:12:44.730 --> 00:12:44.740 align:start position:0% so that's kind of like high-level on 00:12:44.740 --> 00:12:48.280 align:start position:0% so that's kind of like high-level on boarding<00:12:45.800> um<00:12:45.980> so<00:12:46.820> zooming<00:12:47.450> in<00:12:47.630> on<00:12:47.720> a<00:12:47.780> key 00:12:48.280 --> 00:12:48.290 align:start position:0% boarding um so zooming in on a key 00:12:48.290 --> 00:12:52.170 align:start position:0% boarding um so zooming in on a key generation<00:12:48.620> um<00:12:49.840> so<00:12:50.840> there's<00:12:51.110> actually<00:12:51.230> some 00:12:52.170 --> 00:12:52.180 align:start position:0% generation um so there's actually some 00:12:52.180 --> 00:12:54.510 align:start position:0% generation um so there's actually some you<00:12:53.180> know<00:12:53.300> we're<00:12:53.480> not<00:12:53.540> the<00:12:53.600> first<00:12:53.720> people<00:12:54.110> to 00:12:54.510 --> 00:12:54.520 align:start position:0% you know we're not the first people to 00:12:54.520 --> 00:12:55.810 align:start position:0% you know we're not the first people to kind 00:12:55.810 --> 00:12:55.820 align:start position:0% kind 00:12:55.820 --> 00:12:59.140 align:start position:0% kind again<00:12:56.120> some<00:12:56.300> of<00:12:56.390> these<00:12:56.450> problems<00:12:56.690> and<00:12:57.310> a<00:12:58.310> lot 00:12:59.140 --> 00:12:59.150 align:start position:0% again some of these problems and a lot 00:12:59.150 --> 00:13:01.270 align:start position:0% again some of these problems and a lot of<00:12:59.180> the<00:12:59.800> many<00:13:00.800> of<00:13:00.920> the<00:13:01.010> cryptographic 00:13:01.270 --> 00:13:01.280 align:start position:0% of the many of the cryptographic 00:13:01.280 --> 00:13:03.100 align:start position:0% of the many of the cryptographic libraries<00:13:01.880> of<00:13:02.090> wallets<00:13:02.450> like<00:13:02.600> madam<00:13:02.990> asked 00:13:03.100 --> 00:13:03.110 align:start position:0% libraries of wallets like madam asked 00:13:03.110 --> 00:13:05.710 align:start position:0% libraries of wallets like madam asked for<00:13:03.260> example<00:13:03.560> depend<00:13:03.860> on<00:13:04.040> like<00:13:04.790> provide 00:13:05.710 --> 00:13:05.720 align:start position:0% for example depend on like provide 00:13:05.720 --> 00:13:08.440 align:start position:0% for example depend on like provide methods<00:13:06.110> of<00:13:06.530> deriving<00:13:06.940> secondary<00:13:07.940> keys<00:13:08.180> from 00:13:08.440 --> 00:13:08.450 align:start position:0% methods of deriving secondary keys from 00:13:08.450 --> 00:13:13.090 align:start position:0% methods of deriving secondary keys from primary<00:13:08.840> keys<00:13:09.050> but<00:13:10.600> unfortunately<00:13:11.600> the<00:13:12.350> zero 00:13:13.090 --> 00:13:13.100 align:start position:0% primary keys but unfortunately the zero 00:13:13.100 --> 00:13:15.490 align:start position:0% primary keys but unfortunately the zero on<00:13:13.250> there's<00:13:13.580> an<00:13:13.730> RPC<00:13:14.150> static<00:13:14.600> for<00:13:14.870> kind<00:13:15.410> of 00:13:15.490 --> 00:13:15.500 align:start position:0% on there's an RPC static for kind of 00:13:15.500 --> 00:13:17.650 align:start position:0% on there's an RPC static for kind of exposing<00:13:16.100> these<00:13:16.190> methods<00:13:16.610> to<00:13:16.940> like<00:13:17.390> the<00:13:17.540> end 00:13:17.650 --> 00:13:17.660 align:start position:0% exposing these methods to like the end 00:13:17.660 --> 00:13:20.410 align:start position:0% exposing these methods to like the end user<00:13:17.870> ended<00:13:18.170> up<00:13:18.320> but<00:13:19.130> on<00:13:19.370> so<00:13:20.000> the<00:13:20.090> way<00:13:20.180> that<00:13:20.210> we 00:13:20.410 --> 00:13:20.420 align:start position:0% user ended up but on so the way that we 00:13:20.420 --> 00:13:23.640 align:start position:0% user ended up but on so the way that we get<00:13:20.540> around<00:13:20.690> that<00:13:20.810> is<00:13:21.200> a<00:13:22.030> key<00:13:23.030> generation 00:13:23.640 --> 00:13:23.650 align:start position:0% get around that is a key generation 00:13:23.650 --> 00:13:27.760 align:start position:0% get around that is a key generation happens<00:13:24.650> by<00:13:24.890> taking<00:13:25.430> a<00:13:25.820> pass<00:13:26.390> phrase<00:13:26.680> which<00:13:27.680> is 00:13:27.760 --> 00:13:27.770 align:start position:0% happens by taking a pass phrase which is 00:13:27.770 --> 00:13:30.610 align:start position:0% happens by taking a pass phrase which is just<00:13:27.920> the<00:13:27.980> plaintext<00:13:28.340> word<00:13:28.780> or<00:13:29.780> set<00:13:30.380> of<00:13:30.470> words 00:13:30.610 --> 00:13:30.620 align:start position:0% just the plaintext word or set of words 00:13:30.620 --> 00:13:33.220 align:start position:0% just the plaintext word or set of words and<00:13:30.890> then<00:13:31.400> sign<00:13:31.880> it<00:13:32.120> and<00:13:32.270> then<00:13:32.480> using<00:13:32.780> that<00:13:32.810> pet 00:13:33.220 --> 00:13:33.230 align:start position:0% and then sign it and then using that pet 00:13:33.230 --> 00:13:35.290 align:start position:0% and then sign it and then using that pet string<00:13:33.560> that's<00:13:33.710> generated<00:13:34.280> as<00:13:34.520> kind<00:13:34.850> of<00:13:34.940> the 00:13:35.290 --> 00:13:35.300 align:start position:0% string that's generated as kind of the 00:13:35.300 --> 00:13:38.380 align:start position:0% string that's generated as kind of the encryption<00:13:35.810> key<00:13:36.020> for<00:13:36.910> that<00:13:37.910> encrypts<00:13:38.270> your 00:13:38.380 --> 00:13:38.390 align:start position:0% encryption key for that encrypts your 00:13:38.390 --> 00:13:42.250 align:start position:0% encryption key for that encrypts your private<00:13:38.720> PG<00:13:39.230> PG<00:13:39.560> basically<00:13:40.400> so<00:13:40.780> open<00:13:41.780> PGP<00:13:41.960> is 00:13:42.250 --> 00:13:42.260 align:start position:0% private PG PG basically so open PGP is 00:13:42.260 --> 00:13:45.190 align:start position:0% private PG PG basically so open PGP is when<00:13:42.950> you<00:13:43.040> generate<00:13:43.220> a<00:13:43.610> new<00:13:44.240> key<00:13:44.270> pair<00:13:44.450> you 00:13:45.190 --> 00:13:45.200 align:start position:0% when you generate a new key pair you 00:13:45.200 --> 00:13:46.210 align:start position:0% when you generate a new key pair you have<00:13:45.290> the<00:13:45.380> option<00:13:45.680> to<00:13:45.740> pass<00:13:45.980> in<00:13:46.160> the 00:13:46.210 --> 00:13:46.220 align:start position:0% have the option to pass in the 00:13:46.220 --> 00:13:46.660 align:start position:0% have the option to pass in the passphrase 00:13:46.660 --> 00:13:46.670 align:start position:0% passphrase 00:13:46.670 --> 00:13:47.950 align:start position:0% passphrase that's<00:13:47.060> kind<00:13:47.270> of<00:13:47.300> the<00:13:47.420> encryption<00:13:47.840> password 00:13:47.950 --> 00:13:47.960 align:start position:0% that's kind of the encryption password 00:13:47.960 --> 00:13:50.770 align:start position:0% that's kind of the encryption password so<00:13:48.890> that<00:13:48.920> sign<00:13:49.370> message<00:13:49.820> becomes<00:13:50.270> eviction 00:13:50.770 --> 00:13:50.780 align:start position:0% so that sign message becomes eviction 00:13:50.780 --> 00:13:52.990 align:start position:0% so that sign message becomes eviction password<00:13:51.260> for<00:13:51.440> your<00:13:51.560> key<00:13:51.740> pair<00:13:51.920> basically<00:13:52.490> so 00:13:52.990 --> 00:13:53.000 align:start position:0% password for your key pair basically so 00:13:53.000 --> 00:13:55.690 align:start position:0% password for your key pair basically so that's<00:13:53.180> kind<00:13:53.420> of<00:13:53.480> a<00:13:53.830> low<00:13:54.830> level<00:13:54.890> of<00:13:55.250> others<00:13:55.490> to 00:13:55.690 --> 00:13:55.700 align:start position:0% that's kind of a low level of others to 00:13:55.700 --> 00:13:59.140 align:start position:0% that's kind of a low level of others to were<00:13:55.790> associated<00:13:56.500> and<00:13:57.500> then<00:13:57.860> once<00:13:58.790> that<00:13:58.910> key 00:13:59.140 --> 00:13:59.150 align:start position:0% were associated and then once that key 00:13:59.150 --> 00:14:01.510 align:start position:0% were associated and then once that key is<00:13:59.240> created<00:13:59.630> ipfs<00:14:00.380> provides<00:14:00.770> kind<00:14:01.190> of<00:14:01.310> cheap 00:14:01.510 --> 00:14:01.520 align:start position:0% is created ipfs provides kind of cheap 00:14:01.520 --> 00:14:04.420 align:start position:0% is created ipfs provides kind of cheap reliable<00:14:01.700> storage<00:14:02.150> um<00:14:02.890> so<00:14:03.890> the<00:14:04.310> way<00:14:04.400> that 00:14:04.420 --> 00:14:04.430 align:start position:0% reliable storage um so the way that 00:14:04.430 --> 00:14:08.820 align:start position:0% reliable storage um so the way that works<00:14:04.700> for<00:14:04.820> us<00:14:04.970> is<00:14:05.240> that<00:14:05.270> we<00:14:06.260> store<00:14:07.160> the<00:14:07.280> ipfs 00:14:08.820 --> 00:14:08.830 align:start position:0% works for us is that we store the ipfs 00:14:08.830 --> 00:14:11.470 align:start position:0% works for us is that we store the ipfs we<00:14:09.830> swear<00:14:10.040> the<00:14:10.130> keeper<00:14:10.400> and<00:14:10.730> i<00:14:10.820> give<00:14:11.030> us<00:14:11.240> and 00:14:11.470 --> 00:14:11.480 align:start position:0% we swear the keeper and i give us and 00:14:11.480 --> 00:14:14.920 align:start position:0% we swear the keeper and i give us and like<00:14:11.720> basically<00:14:11.930> a<00:14:12.650> redundant<00:14:13.660> set<00:14:14.660> of<00:14:14.750> layers 00:14:14.920 --> 00:14:14.930 align:start position:0% like basically a redundant set of layers 00:14:14.930 --> 00:14:17.500 align:start position:0% like basically a redundant set of layers so<00:14:15.140> using<00:14:15.860> the<00:14:15.920> pin<00:14:16.100> set<00:14:16.340> so<00:14:16.640> you<00:14:17.210> know<00:14:17.270> they<00:14:17.390> go 00:14:17.500 --> 00:14:17.510 align:start position:0% so using the pin set so you know they go 00:14:17.510 --> 00:14:20.760 align:start position:0% so using the pin set so you know they go from<00:14:17.710> pure<00:14:18.710> a<00:14:18.740> to<00:14:19.010> pinata<00:14:19.310> at<00:14:19.460> or<00:14:19.760> on<00:14:19.910> I<00:14:20.150> give<00:14:20.450> us 00:14:20.760 --> 00:14:20.770 align:start position:0% from pure a to pinata at or on I give us 00:14:20.770 --> 00:14:25.900 align:start position:0% from pure a to pinata at or on I give us node<00:14:21.770> onto<00:14:22.900> a<00:14:23.900> cloud<00:14:24.290> fire<00:14:24.620> and<00:14:25.160> some<00:14:25.700> others 00:14:25.900 --> 00:14:25.910 align:start position:0% node onto a cloud fire and some others 00:14:25.910 --> 00:14:28.000 align:start position:0% node onto a cloud fire and some others so<00:14:26.120> we<00:14:26.270> kind<00:14:26.480> of<00:14:26.540> use<00:14:26.690> that<00:14:26.720> that<00:14:27.410> pen<00:14:27.620> sets<00:14:27.860> are 00:14:28.000 --> 00:14:28.010 align:start position:0% so we kind of use that that pen sets are 00:14:28.010 --> 00:14:30.370 align:start position:0% so we kind of use that that pen sets are like<00:14:28.160> replicate<00:14:28.610> across<00:14:28.700> all<00:14:29.060> of<00:14:29.180> his<00:14:29.270> nose<00:14:29.420> so 00:14:30.370 --> 00:14:30.380 align:start position:0% like replicate across all of his nose so 00:14:30.380 --> 00:14:34.200 align:start position:0% like replicate across all of his nose so that<00:14:30.500> kind<00:14:30.710> of<00:14:30.770> makes<00:14:31.640> these<00:14:31.940> keep<00:14:32.450> areas 00:14:34.200 --> 00:14:34.210 align:start position:0% that kind of makes these keep areas 00:14:34.210 --> 00:14:36.970 align:start position:0% that kind of makes these keep areas reliably<00:14:35.210> available<00:14:35.390> without<00:14:36.110> having<00:14:36.590> to 00:14:36.970 --> 00:14:36.980 align:start position:0% reliably available without having to 00:14:36.980 --> 00:14:38.710 align:start position:0% reliably available without having to store<00:14:37.160> them<00:14:37.340> like<00:14:37.940> on<00:14:38.090> a<00:14:38.120> certain<00:14:38.420> contract 00:14:38.710 --> 00:14:38.720 align:start position:0% store them like on a certain contract 00:14:38.720 --> 00:14:43.410 align:start position:0% store them like on a certain contract basically<00:14:41.350> so 00:14:43.410 --> 00:14:43.420 align:start position:0% basically so 00:14:43.420 --> 00:14:46.230 align:start position:0% basically so key<00:14:43.930> distribution<00:14:44.560> so<00:14:44.950> this<00:14:45.579> is<00:14:45.760> kind<00:14:45.940> of<00:14:46.029> like 00:14:46.230 --> 00:14:46.240 align:start position:0% key distribution so this is kind of like 00:14:46.240 --> 00:14:48.600 align:start position:0% key distribution so this is kind of like the<00:14:46.480> directory<00:14:46.899> or<00:14:47.140> the<00:14:47.200> index<00:14:47.560> that<00:14:47.950> I<00:14:48.010> talked 00:14:48.600 --> 00:14:48.610 align:start position:0% the directory or the index that I talked 00:14:48.610 --> 00:14:51.389 align:start position:0% the directory or the index that I talked about<00:14:48.700> before<00:14:48.910> um<00:14:49.630> I<00:14:50.440> think<00:14:50.890> I<00:14:51.100> actually 00:14:51.389 --> 00:14:51.399 align:start position:0% about before um I think I actually 00:14:51.399 --> 00:14:54.060 align:start position:0% about before um I think I actually covered<00:14:51.700> missed<00:14:51.970> this<00:14:52.180> already<00:14:52.420> but<00:14:53.070> one 00:14:54.060 --> 00:14:54.070 align:start position:0% covered missed this already but one 00:14:54.070 --> 00:14:56.100 align:start position:0% covered missed this already but one thing<00:14:54.250> I<00:14:54.310> wanted<00:14:54.490> to<00:14:54.579> touch<00:14:54.760> on<00:14:54.970> was<00:14:55.360> this<00:14:55.930> idea 00:14:56.100 --> 00:14:56.110 align:start position:0% thing I wanted to touch on was this idea 00:14:56.110 --> 00:14:59.250 align:start position:0% thing I wanted to touch on was this idea of<00:14:56.290> multiplexing<00:14:57.190> which<00:14:57.940> is<00:14:58.180> an<00:14:58.390> idea<00:14:59.140> that 00:14:59.250 --> 00:14:59.260 align:start position:0% of multiplexing which is an idea that 00:14:59.260 --> 00:15:02.910 align:start position:0% of multiplexing which is an idea that kind<00:14:59.890> of<00:14:59.980> comes<00:15:00.220> from<00:15:00.459> lip<00:15:01.120> d2d<00:15:01.630> basically<00:15:02.380> so 00:15:02.910 --> 00:15:02.920 align:start position:0% kind of comes from lip d2d basically so 00:15:02.920 --> 00:15:06.870 align:start position:0% kind of comes from lip d2d basically so if<00:15:03.190> you<00:15:03.339> if<00:15:04.500> there's<00:15:05.500> basically<00:15:05.950> like<00:15:06.339> it's 00:15:06.870 --> 00:15:06.880 align:start position:0% if you if there's basically like it's 00:15:06.880 --> 00:15:09.120 align:start position:0% if you if there's basically like it's kind<00:15:07.089> of<00:15:07.149> like<00:15:07.930> function<00:15:08.350> overriding<00:15:08.800> but 00:15:09.120 --> 00:15:09.130 align:start position:0% kind of like function overriding but 00:15:09.130 --> 00:15:12.030 align:start position:0% kind of like function overriding but like<00:15:09.279> on<00:15:09.459> a<00:15:09.490> network<00:15:09.760> level<00:15:10.060> so<00:15:10.510> if<00:15:11.050> I<00:15:11.320> want<00:15:11.740> for 00:15:12.030 --> 00:15:12.040 align:start position:0% like on a network level so if I want for 00:15:12.040 --> 00:15:14.009 align:start position:0% like on a network level so if I want for example<00:15:12.279> to<00:15:12.670> request<00:15:12.970> some<00:15:13.149> information<00:15:13.660> and 00:15:14.009 --> 00:15:14.019 align:start position:0% example to request some information and 00:15:14.019 --> 00:15:16.530 align:start position:0% example to request some information and I<00:15:14.800> shouldn't<00:15:15.100> have<00:15:15.160> to<00:15:15.339> care<00:15:15.579> about<00:15:15.910> how<00:15:16.269> that 00:15:16.530 --> 00:15:16.540 align:start position:0% I shouldn't have to care about how that 00:15:16.540 --> 00:15:19.380 align:start position:0% I shouldn't have to care about how that information<00:15:16.810> is<00:15:17.380> stored<00:15:17.829> long<00:15:18.579> or<00:15:19.029> how<00:15:19.209> it's 00:15:19.380 --> 00:15:19.390 align:start position:0% information is stored long or how it's 00:15:19.390 --> 00:15:21.600 align:start position:0% information is stored long or how it's fetched<00:15:19.810> I<00:15:20.050> should<00:15:20.500> just<00:15:20.680> be<00:15:20.829> able<00:15:20.890> to<00:15:21.190> you 00:15:21.600 --> 00:15:21.610 align:start position:0% fetched I should just be able to you 00:15:21.610 --> 00:15:23.579 align:start position:0% fetched I should just be able to you know<00:15:21.730> ask<00:15:22.180> it<00:15:22.510> ask<00:15:22.839> for<00:15:23.110> it<00:15:23.170> and<00:15:23.260> have<00:15:23.380> some 00:15:23.579 --> 00:15:23.589 align:start position:0% know ask it ask for it and have some 00:15:23.589 --> 00:15:25.500 align:start position:0% know ask it ask for it and have some guarantee<00:15:23.980> about<00:15:24.490> you<00:15:24.790> know<00:15:24.910> how<00:15:25.060> it<00:15:25.180> gets<00:15:25.360> to 00:15:25.500 --> 00:15:25.510 align:start position:0% guarantee about you know how it gets to 00:15:25.510 --> 00:15:28.440 align:start position:0% guarantee about you know how it gets to me<00:15:25.600> so<00:15:26.200> kind<00:15:26.860> of<00:15:26.950> the<00:15:27.220> multiplex<00:15:28.120> here<00:15:28.269> in<00:15:28.329> this 00:15:28.440 --> 00:15:28.450 align:start position:0% me so kind of the multiplex here in this 00:15:28.450 --> 00:15:31.590 align:start position:0% me so kind of the multiplex here in this case<00:15:28.660> if<00:15:29.160> we<00:15:30.160> have<00:15:30.190> keys<00:15:30.579> that<00:15:31.089> can<00:15:31.240> be<00:15:31.329> certain 00:15:31.590 --> 00:15:31.600 align:start position:0% case if we have keys that can be certain 00:15:31.600 --> 00:15:33.240 align:start position:0% case if we have keys that can be certain on<00:15:31.660> our<00:15:31.990> contract<00:15:32.440> or<00:15:32.649> keys<00:15:32.920> that<00:15:33.040> can<00:15:33.190> be 00:15:33.240 --> 00:15:33.250 align:start position:0% on our contract or keys that can be 00:15:33.250 --> 00:15:34.860 align:start position:0% on our contract or keys that can be stored<00:15:33.399> in<00:15:33.490> a<00:15:33.579> database<00:15:33.700> and<00:15:34.570> when<00:15:34.660> you<00:15:34.720> look 00:15:34.860 --> 00:15:34.870 align:start position:0% stored in a database and when you look 00:15:34.870 --> 00:15:36.630 align:start position:0% stored in a database and when you look up<00:15:35.050> you<00:15:35.079> kind<00:15:35.500> of<00:15:35.560> do<00:15:35.709> that<00:15:35.890> lookup<00:15:36.220> of<00:15:36.459> both 00:15:36.630 --> 00:15:36.640 align:start position:0% up you kind of do that lookup of both 00:15:36.640 --> 00:15:38.310 align:start position:0% up you kind of do that lookup of both the<00:15:36.790> smart<00:15:37.029> contract<00:15:37.149> and<00:15:37.600> the<00:15:37.690> database<00:15:38.079> in 00:15:38.310 --> 00:15:38.320 align:start position:0% the smart contract and the database in 00:15:38.320 --> 00:15:43.860 align:start position:0% the smart contract and the database in parallel<00:15:38.740> um<00:15:39.060> and<00:15:40.709> on<00:15:41.709> the<00:15:42.750> application<00:15:43.750> level 00:15:43.860 --> 00:15:43.870 align:start position:0% parallel um and on the application level 00:15:43.870 --> 00:15:45.630 align:start position:0% parallel um and on the application level you<00:15:44.260> know<00:15:44.380> you<00:15:45.010> don't<00:15:45.130> really<00:15:45.279> care<00:15:45.370> about 00:15:45.630 --> 00:15:45.640 align:start position:0% you know you don't really care about 00:15:45.640 --> 00:15:47.220 align:start position:0% you know you don't really care about where<00:15:46.000> the<00:15:46.120> key<00:15:46.300> is<00:15:46.329> stored<00:15:46.570> you<00:15:46.779> can<00:15:46.930> just<00:15:47.079> use 00:15:47.220 --> 00:15:47.230 align:start position:0% where the key is stored you can just use 00:15:47.230 --> 00:15:50.130 align:start position:0% where the key is stored you can just use it<00:15:47.260> and<00:15:47.620> this<00:15:48.490> also<00:15:48.699> allows<00:15:49.029> for<00:15:49.060> the<00:15:49.630> addition 00:15:50.130 --> 00:15:50.140 align:start position:0% it and this also allows for the addition 00:15:50.140 --> 00:15:53.189 align:start position:0% it and this also allows for the addition of<00:15:50.850> other<00:15:51.850> types<00:15:52.209> that<00:15:52.390> data<00:15:52.570> stores<00:15:52.810> for 00:15:53.189 --> 00:15:53.199 align:start position:0% of other types that data stores for 00:15:53.199 --> 00:15:55.710 align:start position:0% of other types that data stores for mystery<00:15:53.800> and<00:15:53.980> the<00:15:54.040> keys<00:15:54.220> one<00:15:54.910> of<00:15:55.000> which<00:15:55.120> we<00:15:55.300> we 00:15:55.710 --> 00:15:55.720 align:start position:0% mystery and the keys one of which we we 00:15:55.720 --> 00:15:59.240 align:start position:0% mystery and the keys one of which we we use<00:15:55.930> in<00:15:56.110> our<00:15:56.199> demo<00:15:56.440> which<00:15:57.100> is<00:15:57.220> kind<00:15:57.399> of<00:15:57.490> tricky 00:15:59.240 --> 00:15:59.250 align:start position:0% use in our demo which is kind of tricky 00:15:59.250 --> 00:16:03.509 align:start position:0% use in our demo which is kind of tricky so<00:16:00.250> often<00:16:01.000> privacy<00:16:01.740> so<00:16:02.740> this<00:16:02.890> is<00:16:03.010> kind<00:16:03.220> of<00:16:03.279> the 00:16:03.509 --> 00:16:03.519 align:start position:0% so often privacy so this is kind of the 00:16:03.519 --> 00:16:05.880 align:start position:0% so often privacy so this is kind of the last<00:16:04.329> step<00:16:04.600> that<00:16:04.750> needs<00:16:04.810> your<00:16:05.019> lifecycle<00:16:05.350> said 00:16:05.880 --> 00:16:05.890 align:start position:0% last step that needs your lifecycle said 00:16:05.890 --> 00:16:07.199 align:start position:0% last step that needs your lifecycle said this<00:16:06.040> is<00:16:06.160> like<00:16:06.339> after<00:16:06.670> everything<00:16:06.910> is 00:16:07.199 --> 00:16:07.209 align:start position:0% this is like after everything is 00:16:07.209 --> 00:16:10.590 align:start position:0% this is like after everything is generated<00:16:08.199> and<00:16:08.440> distributed<00:16:09.300> we<00:16:10.300> can<00:16:10.420> just 00:16:10.590 --> 00:16:10.600 align:start position:0% generated and distributed we can just 00:16:10.600 --> 00:16:13.050 align:start position:0% generated and distributed we can just enjoy<00:16:10.990> the<00:16:11.170> benefits<00:16:11.529> of<00:16:11.769> everything<00:16:12.760> that 00:16:13.050 --> 00:16:13.060 align:start position:0% enjoy the benefits of everything that 00:16:13.060 --> 00:16:16.259 align:start position:0% enjoy the benefits of everything that the<00:16:13.180> open<00:16:13.420> bgp<00:16:13.839> library<00:16:14.170> offers<00:16:14.350> on<00:16:14.910> so<00:16:15.910> on<00:16:16.060> key 00:16:16.259 --> 00:16:16.269 align:start position:0% the open bgp library offers on so on key 00:16:16.269 --> 00:16:18.960 align:start position:0% the open bgp library offers on so on key space<00:16:16.510> on<00:16:17.170> a<00:16:17.230> key<00:16:17.440> space<00:16:17.620> class<00:16:17.860> there<00:16:18.370> is<00:16:18.550> four 00:16:18.960 --> 00:16:18.970 align:start position:0% space on a key space class there is four 00:16:18.970 --> 00:16:20.880 align:start position:0% space on a key space class there is four function<00:16:19.870> types<00:16:20.019> that<00:16:20.260> are<00:16:20.380> pretty<00:16:20.769> much 00:16:20.880 --> 00:16:20.890 align:start position:0% function types that are pretty much 00:16:20.890 --> 00:16:23.100 align:start position:0% function types that are pretty much everything<00:16:21.190> they're<00:16:21.339> going<00:16:21.459> to<00:16:21.519> use<00:16:22.110> other 00:16:23.100 --> 00:16:23.110 align:start position:0% everything they're going to use other 00:16:23.110 --> 00:16:25.710 align:start position:0% everything they're going to use other than<00:16:23.230> encrypt<00:16:24.070> which<00:16:24.519> takes<00:16:24.940> a<00:16:25.060> message<00:16:25.240> the 00:16:25.710 --> 00:16:25.720 align:start position:0% than encrypt which takes a message the 00:16:25.720 --> 00:16:28.699 align:start position:0% than encrypt which takes a message the plaintext<00:16:26.079> message<00:16:26.529> and<00:16:26.769> the<00:16:27.430> address<00:16:27.760> that 00:16:28.699 --> 00:16:28.709 align:start position:0% plaintext message and the address that 00:16:28.709 --> 00:16:30.689 align:start position:0% plaintext message and the address that you're<00:16:29.709> going<00:16:30.010> to<00:16:30.100> send<00:16:30.430> an<00:16:30.579> encrypted 00:16:30.689 --> 00:16:30.699 align:start position:0% you're going to send an encrypted 00:16:30.699 --> 00:16:33.569 align:start position:0% you're going to send an encrypted message<00:16:30.970> to<00:16:31.890> decrypt<00:16:32.890> which<00:16:33.100> tasted 00:16:33.569 --> 00:16:33.579 align:start position:0% message to decrypt which tasted 00:16:33.579 --> 00:16:35.370 align:start position:0% message to decrypt which tasted encrypted<00:16:34.329> message<00:16:34.600> in<00:16:34.720> the<00:16:34.810> from<00:16:34.990> address<00:16:35.230> so 00:16:35.370 --> 00:16:35.380 align:start position:0% encrypted message in the from address so 00:16:35.380 --> 00:16:37.680 align:start position:0% encrypted message in the from address so you<00:16:35.470> can<00:16:35.529> verify<00:16:35.769> you<00:16:36.730> know<00:16:36.880> that<00:16:37.149> it<00:16:37.240> was<00:16:37.420> sent 00:16:37.680 --> 00:16:37.690 align:start position:0% you can verify you know that it was sent 00:16:37.690 --> 00:16:41.040 align:start position:0% you can verify you know that it was sent by<00:16:37.779> the<00:16:37.810> address<00:16:38.170> you<00:16:38.500> find<00:16:38.740> us<00:16:38.920> on<00:16:39.040> it<00:16:39.190> and<00:16:40.050> you 00:16:41.040 --> 00:16:41.050 align:start position:0% by the address you find us on it and you 00:16:41.050 --> 00:16:42.090 align:start position:0% by the address you find us on it and you know<00:16:41.110> that<00:16:41.140> you<00:16:41.350> can<00:16:41.470> just<00:16:41.709> get 00:16:42.090 --> 00:16:42.100 align:start position:0% know that you can just get 00:16:42.100 --> 00:16:45.840 align:start position:0% know that you can just get that's<00:16:42.850> meant<00:16:43.360> for<00:16:43.509> you<00:16:43.600> and<00:16:43.949> then<00:16:44.949> we<00:16:45.069> also<00:16:45.220> in 00:16:45.840 --> 00:16:45.850 align:start position:0% that's meant for you and then we also in 00:16:45.850 --> 00:16:49.019 align:start position:0% that's meant for you and then we also in isolation<00:16:46.300> provide<00:16:47.019> a<00:16:47.350> sign<00:16:47.769> and<00:16:48.160> validate<00:16:48.850> as 00:16:49.019 --> 00:16:49.029 align:start position:0% isolation provide a sign and validate as 00:16:49.029 --> 00:16:55.199 align:start position:0% isolation provide a sign and validate as well<00:16:50.759> so<00:16:51.759> that's<00:16:52.329> all<00:16:52.569> for<00:16:53.110> the<00:16:54.209> high-level 00:16:55.199 --> 00:16:55.209 align:start position:0% well so that's all for the high-level 00:16:55.209 --> 00:16:58.920 align:start position:0% well so that's all for the high-level review<00:16:55.420> now<00:16:56.079> is<00:16:56.290> the<00:16:56.410> fun<00:16:56.620> part<00:16:56.850> which<00:16:57.850> is<00:16:57.930> the 00:16:58.920 --> 00:16:58.930 align:start position:0% review now is the fun part which is the 00:16:58.930 --> 00:17:03.500 align:start position:0% review now is the fun part which is the demo<00:16:59.170> so<00:17:00.029> this<00:17:01.029> demo<00:17:01.389> will<00:17:01.630> work<00:17:01.870> on<00:17:02.199> both<00:17:02.529> your 00:17:03.500 --> 00:17:03.510 align:start position:0% demo so this demo will work on both your 00:17:03.510 --> 00:17:06.270 align:start position:0% demo so this demo will work on both your laptops<00:17:04.510> and<00:17:04.809> phones<00:17:04.900> as<00:17:05.770> long<00:17:05.949> as<00:17:06.069> they<00:17:06.160> get 00:17:06.270 --> 00:17:06.280 align:start position:0% laptops and phones as long as they get 00:17:06.280 --> 00:17:09.569 align:start position:0% laptops and phones as long as they get connected<00:17:06.459> to<00:17:06.730> the<00:17:06.789> internet<00:17:07.120> on<00:17:07.360> so<00:17:08.429> you<00:17:09.429> can 00:17:09.569 --> 00:17:09.579 align:start position:0% connected to the internet on so you can 00:17:09.579 --> 00:17:12.090 align:start position:0% connected to the internet on so you can go<00:17:09.880> to<00:17:09.939> the<00:17:10.329> the<00:17:11.020> top<00:17:11.230> link<00:17:11.439> there<00:17:11.679> where<00:17:11.709> the 00:17:12.090 --> 00:17:12.100 align:start position:0% go to the the top link there where the 00:17:12.100 --> 00:17:15.689 align:start position:0% go to the the top link there where the light<00:17:12.549> of<00:17:13.179> that<00:17:13.270> is<00:17:13.569> on<00:17:14.230> the<00:17:14.620> airsoft<00:17:15.039> github 00:17:15.689 --> 00:17:15.699 align:start position:0% light of that is on the airsoft github 00:17:15.699 --> 00:17:18.870 align:start position:0% light of that is on the airsoft github that<00:17:15.730> hyeri<00:17:16.390> /<00:17:16.480> keyspace<00:17:17.319> /<00:17:18.220> that's<00:17:18.520> common 00:17:18.870 --> 00:17:18.880 align:start position:0% that hyeri / keyspace / that's common 00:17:18.880 --> 00:17:23.069 align:start position:0% that hyeri / keyspace / that's common sorry<00:17:19.870> that<00:17:20.020> link<00:17:20.199> is<00:17:20.350> not<00:17:20.500> sure<00:17:22.079> originally 00:17:23.069 --> 00:17:23.079 align:start position:0% sorry that link is not sure originally 00:17:23.079 --> 00:17:25.439 align:start position:0% sorry that link is not sure originally this<00:17:23.230> is<00:17:23.350> a<00:17:23.439> mystery<00:17:24.069> on<00:17:24.640> kind<00:17:25.120> of<00:17:25.179> a<00:17:25.240> lot<00:17:25.360> of 00:17:25.439 --> 00:17:25.449 align:start position:0% this is a mystery on kind of a lot of 00:17:25.449 --> 00:17:27.600 align:start position:0% this is a mystery on kind of a lot of cloning<00:17:25.809> repos<00:17:26.140> and<00:17:26.589> interactive<00:17:27.280> recruiting 00:17:27.600 --> 00:17:27.610 align:start position:0% cloning repos and interactive recruiting 00:17:27.610 --> 00:17:30.750 align:start position:0% cloning repos and interactive recruiting depend<00:17:28.000> kind<00:17:28.960> of<00:17:29.080> I<00:17:29.230> saw<00:17:30.100> like<00:17:30.429> all<00:17:30.580> the 00:17:30.750 --> 00:17:30.760 align:start position:0% depend kind of I saw like all the 00:17:30.760 --> 00:17:32.520 align:start position:0% depend kind of I saw like all the network<00:17:31.090> limitations<00:17:31.630> we<00:17:31.750> seem<00:17:31.900> too<00:17:32.020> happy<00:17:32.140> so 00:17:32.520 --> 00:17:32.530 align:start position:0% network limitations we seem too happy so 00:17:32.530 --> 00:17:34.350 align:start position:0% network limitations we seem too happy so I<00:17:32.559> just<00:17:32.740> kind<00:17:32.950> of<00:17:32.980> spun<00:17:33.250> up<00:17:33.370> this<00:17:33.520> app<00:17:33.700> quickly 00:17:34.350 --> 00:17:34.360 align:start position:0% I just kind of spun up this app quickly 00:17:34.360 --> 00:17:36.659 align:start position:0% I just kind of spun up this app quickly which<00:17:34.690> I<00:17:34.809> think<00:17:35.020> should<00:17:35.950> we're<00:17:36.130> gonna<00:17:36.340> play 00:17:36.659 --> 00:17:36.669 align:start position:0% which I think should we're gonna play 00:17:36.669 --> 00:17:38.010 align:start position:0% which I think should we're gonna play tested<00:17:37.000> on<00:17:37.090> tree<00:17:37.299> throttle<00:17:37.659> Internet 00:17:38.010 --> 00:17:38.020 align:start position:0% tested on tree throttle Internet 00:17:38.020 --> 00:17:41.250 align:start position:0% tested on tree throttle Internet consideration<00:17:38.470> report<00:17:38.770> all<00:17:38.890> right<00:17:39.100> um<00:17:39.809> but<00:17:40.809> I 00:17:41.250 --> 00:17:41.260 align:start position:0% consideration report all right um but I 00:17:41.260 --> 00:17:43.260 align:start position:0% consideration report all right um but I think<00:17:41.500> this<00:17:41.620> kind<00:17:41.799> of<00:17:41.890> will<00:17:42.039> give<00:17:42.190> us<00:17:42.340> a<00:17:42.549> view 00:17:43.260 --> 00:17:43.270 align:start position:0% think this kind of will give us a view 00:17:43.270 --> 00:17:45.360 align:start position:0% think this kind of will give us a view to<00:17:43.510> kind<00:17:43.720> of<00:17:43.750> like<00:17:43.929> the<00:17:44.470> inner<00:17:44.950> workings<00:17:45.280> of 00:17:45.360 --> 00:17:45.370 align:start position:0% to kind of like the inner workings of 00:17:45.370 --> 00:17:49.980 align:start position:0% to kind of like the inner workings of the<00:17:45.460> protocol<00:17:45.820> without<00:17:48.480> having<00:17:49.480> too<00:17:49.659> much<00:17:49.809> of 00:17:49.980 --> 00:17:49.990 align:start position:0% the protocol without having too much of 00:17:49.990 --> 00:17:53.250 align:start position:0% the protocol without having too much of a<00:17:50.049> bandwidth<00:17:50.679> limitation<00:17:51.190> so<00:17:52.030> I'll<00:17:53.020> let<00:17:53.169> her 00:17:53.250 --> 00:17:53.260 align:start position:0% a bandwidth limitation so I'll let her 00:17:53.260 --> 00:17:57.270 align:start position:0% a bandwidth limitation so I'll let her be<00:17:53.470> pull<00:17:53.679> out<00:17:54.299> and<00:17:55.299> then<00:17:55.480> I<00:17:55.600> will<00:17:56.070> pull<00:17:57.070> it<00:17:57.190> up 00:17:57.270 --> 00:17:57.280 align:start position:0% be pull out and then I will pull it up 00:17:57.280 --> 00:17:59.220 align:start position:0% be pull out and then I will pull it up on<00:17:57.429> mine<00:17:57.669> and<00:17:57.970> kind<00:17:58.419> of<00:17:58.510> walk<00:17:58.900> everybody 00:17:59.220 --> 00:17:59.230 align:start position:0% on mine and kind of walk everybody 00:17:59.230 --> 00:18:10.320 align:start position:0% on mine and kind of walk everybody through<00:17:59.380> how<00:17:59.770> it's<00:17:59.950> working 00:18:10.320 --> 00:18:10.330 align:start position:0% 00:18:10.330 --> 00:18:16.620 align:start position:0% so<00:18:11.730> the<00:18:14.340> it's<00:18:15.340> basically<00:18:15.460> just<00:18:15.760> it's<00:18:16.330> a<00:18:16.390> react 00:18:16.620 --> 00:18:16.630 align:start position:0% so the it's basically just it's a react 00:18:16.630 --> 00:18:19.500 align:start position:0% so the it's basically just it's a react front-end<00:18:16.990> application<00:18:17.530> that<00:18:17.860> uses<00:18:18.510> ipfs 00:18:19.500 --> 00:18:19.510 align:start position:0% front-end application that uses ipfs 00:18:19.510 --> 00:18:21.930 align:start position:0% front-end application that uses ipfs pub/sub<00:18:20.020> to<00:18:20.290> kind<00:18:20.470> of<00:18:20.530> have<00:18:21.250> your<00:18:21.280> messaging 00:18:21.930 --> 00:18:21.940 align:start position:0% pub/sub to kind of have your messaging 00:18:21.940 --> 00:18:24.720 align:start position:0% pub/sub to kind of have your messaging so<00:18:22.210> the<00:18:23.200> one<00:18:23.950> of<00:18:24.010> the<00:18:24.070> cool<00:18:24.190> things<00:18:24.220> about<00:18:24.490> this 00:18:24.720 --> 00:18:24.730 align:start position:0% so the one of the cool things about this 00:18:24.730 --> 00:18:27.660 align:start position:0% so the one of the cool things about this since<00:18:24.970> up<00:18:25.090> days<00:18:25.240> it's<00:18:25.720> a<00:18:25.900> group<00:18:26.680> chat<00:18:26.980> app<00:18:27.220> that 00:18:27.660 --> 00:18:27.670 align:start position:0% since up days it's a group chat app that 00:18:27.670 --> 00:18:30.660 align:start position:0% since up days it's a group chat app that doesn't<00:18:28.390> have<00:18:29.380> any<00:18:29.590> central<00:18:30.100> surgery<00:18:30.400> to<00:18:30.520> it 00:18:30.660 --> 00:18:30.670 align:start position:0% doesn't have any central surgery to it 00:18:30.670 --> 00:18:33.450 align:start position:0% doesn't have any central surgery to it so<00:18:31.300> basically<00:18:32.140> everybody's<00:18:33.010> fairing<00:18:33.280> and 00:18:33.450 --> 00:18:33.460 align:start position:0% so basically everybody's fairing and 00:18:33.460 --> 00:18:35.730 align:start position:0% so basically everybody's fairing and laptop<00:18:33.910> kind<00:18:34.750> of<00:18:34.810> in<00:18:34.900> the<00:18:34.990> room<00:18:35.170> is<00:18:35.380> kind<00:18:35.680> of 00:18:35.730 --> 00:18:35.740 align:start position:0% laptop kind of in the room is kind of 00:18:35.740 --> 00:18:38.730 align:start position:0% laptop kind of in the room is kind of going<00:18:36.340> to<00:18:36.400> be<00:18:36.490> networked<00:18:36.760> together<00:18:36.940> and<00:18:37.740> it's 00:18:38.730 --> 00:18:38.740 align:start position:0% going to be networked together and it's 00:18:38.740 --> 00:18:40.200 align:start position:0% going to be networked together and it's kind<00:18:38.890> of<00:18:38.920> form<00:18:39.160> a<00:18:39.370> two-tiered<00:18:40.060> chat 00:18:40.200 --> 00:18:40.210 align:start position:0% kind of form a two-tiered chat 00:18:40.210 --> 00:18:43.860 align:start position:0% kind of form a two-tiered chat application<00:18:40.750> um<00:18:41.020> oh<00:18:42.010> yeah<00:18:42.310> and<00:18:42.730> also<00:18:43.390> sorry<00:18:43.810> I 00:18:43.860 --> 00:18:43.870 align:start position:0% application um oh yeah and also sorry I 00:18:43.870 --> 00:18:45.570 align:start position:0% application um oh yeah and also sorry I should<00:18:44.050> have<00:18:44.080> mentioned<00:18:44.340> when<00:18:45.340> you<00:18:45.430> first 00:18:45.570 --> 00:18:45.580 align:start position:0% should have mentioned when you first 00:18:45.580 --> 00:18:47.220 align:start position:0% should have mentioned when you first look<00:18:45.760> the<00:18:45.850> application<00:18:46.390> and<00:18:46.900> I'm<00:18:47.050> not 00:18:47.220 --> 00:18:47.230 align:start position:0% look the application and I'm not 00:18:47.230 --> 00:18:49.020 align:start position:0% look the application and I'm not connected<00:18:48.010> and<00:18:48.100> then<00:18:48.190> I'm<00:18:48.280> asked<00:18:48.400> which<00:18:48.610> that 00:18:49.020 --> 00:18:49.030 align:start position:0% connected and then I'm asked which that 00:18:49.030 --> 00:18:51.510 align:start position:0% connected and then I'm asked which that also<00:18:49.300> working<00:18:49.450> like<00:18:49.660> a<00:18:49.690> little<00:18:49.960> bit<00:18:50.050> trust<00:18:50.520> you 00:18:51.510 --> 00:18:51.520 align:start position:0% also working like a little bit trust you 00:18:51.520 --> 00:18:52.890 align:start position:0% also working like a little bit trust you can<00:18:51.640> also<00:18:51.730> say<00:18:51.850> just<00:18:52.060> generate<00:18:52.420> a<00:18:52.450> wallet 00:18:52.890 --> 00:18:52.900 align:start position:0% can also say just generate a wallet 00:18:52.900 --> 00:18:55.140 align:start position:0% can also say just generate a wallet inside<00:18:53.740> the<00:18:53.860> app<00:18:53.950> generator<00:18:54.580> temporary 00:18:55.140 --> 00:18:55.150 align:start position:0% inside the app generator temporary 00:18:55.150 --> 00:18:58.770 align:start position:0% inside the app generator temporary wallet<00:18:55.390> which<00:18:55.660> will<00:18:57.120> you<00:18:58.120> can<00:18:58.240> still<00:18:58.480> you<00:18:58.720> know 00:18:58.770 --> 00:18:58.780 align:start position:0% wallet which will you can still you know 00:18:58.780 --> 00:19:00.210 align:start position:0% wallet which will you can still you know use<00:18:58.930> that<00:18:59.080> to<00:18:59.230> communicate<00:18:59.380> since<00:18:59.980> it<00:19:00.100> doesn't 00:19:00.210 --> 00:19:00.220 align:start position:0% use that to communicate since it doesn't 00:19:00.220 --> 00:19:04.560 align:start position:0% use that to communicate since it doesn't currently<00:19:00.760> use<00:19:01.030> any<00:19:01.210> gas<00:19:01.390> um<00:19:03.090> so<00:19:04.090> you<00:19:04.150> do<00:19:04.330> miss 00:19:04.560 --> 00:19:04.570 align:start position:0% currently use any gas um so you do miss 00:19:04.570 --> 00:19:08.390 align:start position:0% currently use any gas um so you do miss people<00:19:04.870> that<00:19:05.170> are<00:19:05.260> gonna<00:19:05.350> put<00:19:05.680> up<00:19:05.800> habit<00:19:06.130> of 00:19:08.390 --> 00:19:08.400 align:start position:0% 00:19:08.400 --> 00:19:18.970 align:start position:0% anybody<00:19:09.400> still<00:19:09.550> typing<00:19:11.970> forget<00:19:12.970> it<00:19:13.030> okay 00:19:18.970 --> 00:19:18.980 align:start position:0% 00:19:18.980 --> 00:19:20.860 align:start position:0% alright<00:19:19.640> so<00:19:19.820> I'm<00:19:20.240> gonna<00:19:20.360> get<00:19:20.510> these<00:19:20.630> tips 00:19:20.860 --> 00:19:20.870 align:start position:0% alright so I'm gonna get these tips 00:19:20.870 --> 00:19:30.460 align:start position:0% alright so I'm gonna get these tips myself<00:19:22.240> I'll<00:19:23.240> generate<00:19:23.540> a<00:19:23.630> temporary<00:19:23.960> wallet 00:19:30.460 --> 00:19:30.470 align:start position:0% 00:19:30.470 --> 00:19:35.249 align:start position:0% so<00:19:32.289> I'm<00:19:33.289> the<00:19:33.440> only<00:19:33.559> tear<00:19:33.830> that<00:19:33.950> I<00:19:34.039> found<00:19:34.279> so<00:19:34.460> far 00:19:35.249 --> 00:19:35.259 align:start position:0% so I'm the only tear that I found so far 00:19:35.259 --> 00:19:37.930 align:start position:0% so I'm the only tear that I found so far hopefully<00:19:36.259> over<00:19:36.409> time<00:19:36.500> I'm<00:19:37.039> gonna<00:19:37.220> find<00:19:37.669> all 00:19:37.930 --> 00:19:37.940 align:start position:0% hopefully over time I'm gonna find all 00:19:37.940 --> 00:19:39.549 align:start position:0% hopefully over time I'm gonna find all of<00:19:37.970> you<00:19:38.210> it's<00:19:38.450> our<00:19:38.840> other<00:19:38.990> people<00:19:39.230> at<00:19:39.440> this 00:19:39.549 --> 00:19:39.559 align:start position:0% of you it's our other people at this 00:19:39.559 --> 00:19:45.269 align:start position:0% of you it's our other people at this screen<00:19:39.860> after<00:19:40.399> generating<00:19:40.730> the<00:19:40.850> wallet<00:19:41.059> okay 00:19:45.269 --> 00:19:45.279 align:start position:0% 00:19:45.279 --> 00:19:47.950 align:start position:0% hey<00:19:46.450> everybody 00:19:47.950 --> 00:19:47.960 align:start position:0% hey everybody 00:19:47.960 --> 00:19:51.009 align:start position:0% hey everybody okay<00:19:48.620> so<00:19:49.570> nice 00:19:51.009 --> 00:19:51.019 align:start position:0% okay so nice 00:19:51.019 --> 00:19:54.549 align:start position:0% okay so nice I<00:19:52.659> hope<00:19:53.659> the<00:19:53.809> mobile<00:19:54.049> was<00:19:54.139> placed<00:19:54.379> over 00:19:54.549 --> 00:19:54.559 align:start position:0% I hope the mobile was placed over 00:19:54.559 --> 00:19:56.619 align:start position:0% I hope the mobile was placed over expelling<00:19:55.159> these<00:19:55.340> addresses<00:19:55.820> that<00:19:55.970> I<00:19:56.419> wasn't 00:19:56.619 --> 00:19:56.629 align:start position:0% expelling these addresses that I wasn't 00:19:56.629 --> 00:19:58.480 align:start position:0% expelling these addresses that I wasn't able<00:19:56.779> to<00:19:56.960> test<00:19:57.200> without<00:19:57.409> these<00:19:57.590> people<00:19:57.889> okay 00:19:58.480 --> 00:19:58.490 align:start position:0% able to test without these people okay 00:19:58.490 --> 00:20:07.990 align:start position:0% able to test without these people okay so<00:19:59.259> I'm<00:20:00.259> gonna<00:20:00.440> be<00:20:00.679> Sammy<00:20:02.440> okay<00:20:03.440> so<00:20:06.850> okay<00:20:07.850> so 00:20:07.990 --> 00:20:08.000 align:start position:0% so I'm gonna be Sammy okay so okay so 00:20:08.000 --> 00:20:10.450 align:start position:0% so I'm gonna be Sammy okay so okay so this<00:20:08.570> is<00:20:08.720> everybody<00:20:09.049> sharing<00:20:09.440> their<00:20:09.889> PGP<00:20:10.279> keys 00:20:10.450 --> 00:20:10.460 align:start position:0% this is everybody sharing their PGP keys 00:20:10.460 --> 00:20:18.490 align:start position:0% this is everybody sharing their PGP keys with<00:20:10.669> each<00:20:10.789> other<00:20:15.759> okay<00:20:16.990> it<00:20:17.990> does<00:20:18.169> that<00:20:18.350> not 00:20:18.490 --> 00:20:18.500 align:start position:0% with each other okay it does that not 00:20:18.500 --> 00:20:20.590 align:start position:0% with each other okay it does that not has<00:20:18.710> to<00:20:18.830> do<00:20:18.919> with<00:20:19.009> this<00:20:19.159> much<00:20:19.309> scale<00:20:19.549> yet<00:20:19.789> but 00:20:20.590 --> 00:20:20.600 align:start position:0% has to do with this much scale yet but 00:20:20.600 --> 00:20:29.249 align:start position:0% has to do with this much scale yet but it's<00:20:20.779> a<00:20:20.990> seems<00:20:21.620> like<00:20:21.740> it's<00:20:21.860> working<00:20:22.100> okay<00:20:28.210> yeah 00:20:29.249 --> 00:20:29.259 align:start position:0% it's a seems like it's working okay yeah 00:20:29.259 --> 00:20:31.779 align:start position:0% it's a seems like it's working okay yeah okay<00:20:30.259> second<00:20:30.769> I<00:20:30.950> can<00:20:31.100> get<00:20:31.220> into<00:20:31.399> a<00:20:31.519> little<00:20:31.669> bit 00:20:31.779 --> 00:20:31.789 align:start position:0% okay second I can get into a little bit 00:20:31.789 --> 00:20:36.909 align:start position:0% okay second I can get into a little bit of<00:20:33.970> I<00:20:34.970> can<00:20:35.779> go<00:20:35.870> into<00:20:36.019> a<00:20:36.110> little<00:20:36.259> little<00:20:36.769> bit<00:20:36.889> of 00:20:36.909 --> 00:20:36.919 align:start position:0% of I can go into a little little bit of 00:20:36.919 --> 00:20:42.720 align:start position:0% of I can go into a little little bit of what's<00:20:37.129> going<00:20:37.279> on<00:20:37.460> um<00:20:38.259> so<00:20:39.259> basically<00:20:41.110> this 00:20:42.720 --> 00:20:42.730 align:start position:0% what's going on um so basically this 00:20:42.730 --> 00:20:45.310 align:start position:0% what's going on um so basically this this<00:20:43.730> font<00:20:43.940> tab<00:20:44.120> I<00:20:44.419> think<00:20:44.659> it<00:20:44.720> says<00:20:44.899> Peter<00:20:45.169> on 00:20:45.310 --> 00:20:45.320 align:start position:0% this font tab I think it says Peter on 00:20:45.320 --> 00:20:48.159 align:start position:0% this font tab I think it says Peter on your<00:20:45.440> fan<00:20:46.210> on<00:20:47.210> the<00:20:47.269> desktop<00:20:47.750> that<00:20:47.779> says<00:20:47.990> peer 00:20:48.159 --> 00:20:48.169 align:start position:0% your fan on the desktop that says peer 00:20:48.169 --> 00:20:50.889 align:start position:0% your fan on the desktop that says peer discovery<00:20:48.500> protocol<00:20:48.860> so<00:20:49.519> basically<00:20:49.909> this<00:20:50.690> is 00:20:50.889 --> 00:20:50.899 align:start position:0% discovery protocol so basically this is 00:20:50.899 --> 00:20:53.649 align:start position:0% discovery protocol so basically this is a<00:20:51.200> instead<00:20:51.799> of<00:20:51.889> using<00:20:52.100> a<00:20:52.309> database<00:20:52.580> on<00:20:53.029> a 00:20:53.649 --> 00:20:53.659 align:start position:0% a instead of using a database on a 00:20:53.659 --> 00:20:57.279 align:start position:0% a instead of using a database on a contract<00:20:54.620> to<00:20:54.769> distribute<00:20:55.190> keys<00:20:55.879> on<00:20:56.200> we<00:20:57.200> all 00:20:57.279 --> 00:20:57.289 align:start position:0% contract to distribute keys on we all 00:20:57.289 --> 00:21:00.129 align:start position:0% contract to distribute keys on we all connect<00:20:57.679> achieve<00:20:58.009> the<00:20:58.190> same<00:20:58.429> I<00:20:58.820> give<00:20:59.000> us<00:20:59.179> a<00:20:59.539> pub 00:21:00.129 --> 00:21:00.139 align:start position:0% connect achieve the same I give us a pub 00:21:00.139 --> 00:21:03.100 align:start position:0% connect achieve the same I give us a pub set<00:21:00.379> of<00:21:00.470> topics<00:21:00.679> so<00:21:01.129> there's<00:21:01.850> basically<00:21:02.110> one 00:21:03.100 --> 00:21:03.110 align:start position:0% set of topics so there's basically one 00:21:03.110 --> 00:21:06.399 align:start position:0% set of topics so there's basically one idea<00:21:03.799> that's<00:21:03.830> a<00:21:04.279> server<00:21:05.090> that<00:21:05.120> we<00:21:06.049> reach<00:21:06.230> out 00:21:06.399 --> 00:21:06.409 align:start position:0% idea that's a server that we reach out 00:21:06.409 --> 00:21:09.519 align:start position:0% idea that's a server that we reach out to<00:21:06.440> you<00:21:06.620> and<00:21:06.799> say<00:21:07.299> hey<00:21:08.299> I'm<00:21:08.570> listening<00:21:09.320> to<00:21:09.440> this 00:21:09.519 --> 00:21:09.529 align:start position:0% to you and say hey I'm listening to this 00:21:09.529 --> 00:21:13.899 align:start position:0% to you and say hey I'm listening to this topic<00:21:10.299> then<00:21:11.299> when<00:21:11.690> other<00:21:12.639> people<00:21:13.639> connect 00:21:13.899 --> 00:21:13.909 align:start position:0% topic then when other people connect 00:21:13.909 --> 00:21:15.310 align:start position:0% topic then when other people connect they<00:21:14.029> also<00:21:14.210> reach<00:21:14.570> out<00:21:14.720> to<00:21:14.809> that<00:21:14.870> same<00:21:15.080> server 00:21:15.310 --> 00:21:15.320 align:start position:0% they also reach out to that same server 00:21:15.320 --> 00:21:16.570 align:start position:0% they also reach out to that same server and<00:21:15.470> say<00:21:15.590> I'm<00:21:15.710> listening<00:21:15.980> to<00:21:16.100> this<00:21:16.190> topic<00:21:16.399> and 00:21:16.570 --> 00:21:16.580 align:start position:0% and say I'm listening to this topic and 00:21:16.580 --> 00:21:19.029 align:start position:0% and say I'm listening to this topic and we<00:21:17.360> kind<00:21:17.509> of<00:21:17.600> find<00:21:17.990> each<00:21:18.110> other<00:21:18.289> all<00:21:18.470> to<00:21:18.889> that 00:21:19.029 --> 00:21:19.039 align:start position:0% we kind of find each other all to that 00:21:19.039 --> 00:21:20.980 align:start position:0% we kind of find each other all to that way<00:21:19.220> and<00:21:19.429> then<00:21:19.850> appeared<00:21:20.480> directly<00:21:20.809> with<00:21:20.960> each 00:21:20.980 --> 00:21:20.990 align:start position:0% way and then appeared directly with each 00:21:20.990 --> 00:21:23.030 align:start position:0% way and then appeared directly with each other<00:21:21.490> then 00:21:23.030 --> 00:21:23.040 align:start position:0% other then 00:21:23.040 --> 00:21:27.430 align:start position:0% other then after<00:21:23.220> we're<00:21:24.210> all<00:21:24.270> clear<00:21:24.720> we'd<00:21:25.320> broadcast<00:21:26.270> we 00:21:27.430 --> 00:21:27.440 align:start position:0% after we're all clear we'd broadcast we 00:21:27.440 --> 00:21:30.410 align:start position:0% after we're all clear we'd broadcast we broadcast<00:21:28.440> our<00:21:28.590> key<00:21:28.740> and<00:21:29.010> then<00:21:29.130> we<00:21:29.360> send<00:21:30.360> a 00:21:30.410 --> 00:21:30.420 align:start position:0% broadcast our key and then we send a 00:21:30.420 --> 00:21:32.030 align:start position:0% broadcast our key and then we send a message<00:21:30.720> which<00:21:31.140> is<00:21:31.290> what<00:21:31.650> we<00:21:31.740> call<00:21:31.920> it 00:21:32.030 --> 00:21:32.040 align:start position:0% message which is what we call it 00:21:32.040 --> 00:21:34.130 align:start position:0% message which is what we call it requests<00:21:32.370> introduction<00:21:32.940> which<00:21:33.540> basically<00:21:33.840> is 00:21:34.130 --> 00:21:34.140 align:start position:0% requests introduction which basically is 00:21:34.140 --> 00:21:37.010 align:start position:0% requests introduction which basically is like<00:21:34.320> a<00:21:34.910> we<00:21:35.910> send<00:21:36.120> a<00:21:36.150> message<00:21:36.180> to<00:21:36.540> the<00:21:36.690> pub<00:21:36.810> sub 00:21:37.010 --> 00:21:37.020 align:start position:0% like a we send a message to the pub sub 00:21:37.020 --> 00:21:40.850 align:start position:0% like a we send a message to the pub sub topic<00:21:37.380> that<00:21:38.870> is<00:21:39.870> asking<00:21:40.320> other<00:21:40.440> people<00:21:40.530> for 00:21:40.850 --> 00:21:40.860 align:start position:0% topic that is asking other people for 00:21:40.860 --> 00:21:42.950 align:start position:0% topic that is asking other people for the<00:21:41.130> keys<00:21:41.370> and<00:21:41.970> then<00:21:42.180> everybody<00:21:42.900> else 00:21:42.950 --> 00:21:42.960 align:start position:0% the keys and then everybody else 00:21:42.960 --> 00:21:44.510 align:start position:0% the keys and then everybody else responds<00:21:43.500> to<00:21:43.560> that<00:21:43.710> person<00:21:44.070> with<00:21:44.190> their<00:21:44.340> keys 00:21:44.510 --> 00:21:44.520 align:start position:0% responds to that person with their keys 00:21:44.520 --> 00:21:45.920 align:start position:0% responds to that person with their keys basically<00:21:45.030> so<00:21:45.180> it's<00:21:45.300> kind<00:21:45.480> of<00:21:45.510> like<00:21:45.660> a<00:21:45.690> many 00:21:45.920 --> 00:21:45.930 align:start position:0% basically so it's kind of like a many 00:21:45.930 --> 00:21:48.260 align:start position:0% basically so it's kind of like a many many<00:21:46.130> messaging<00:21:47.130> system<00:21:47.490> for<00:21:47.610> kind<00:21:47.790> of<00:21:47.820> Italy 00:21:48.260 --> 00:21:48.270 align:start position:0% many messaging system for kind of Italy 00:21:48.270 --> 00:21:49.940 align:start position:0% many messaging system for kind of Italy in<00:21:48.330> this<00:21:48.450> dynamic<00:21:48.660> database<00:21:49.290> of<00:21:49.470> keys<00:21:49.650> and 00:21:49.940 --> 00:21:49.950 align:start position:0% in this dynamic database of keys and 00:21:49.950 --> 00:21:53.360 align:start position:0% in this dynamic database of keys and like<00:21:50.420> so<00:21:51.420> as<00:21:51.810> you<00:21:51.930> can<00:21:52.050> see<00:21:52.110> the<00:21:52.470> more<00:21:53.100> people 00:21:53.360 --> 00:21:53.370 align:start position:0% like so as you can see the more people 00:21:53.370 --> 00:21:57.830 align:start position:0% like so as you can see the more people that<00:21:53.600> are<00:21:54.600> having<00:21:55.380> the<00:21:56.160> more<00:21:56.640> messaging<00:21:57.630> or 00:21:57.830 --> 00:21:57.840 align:start position:0% that are having the more messaging or 00:21:57.840 --> 00:21:59.960 align:start position:0% that are having the more messaging or more<00:21:58.560> people<00:21:58.680> requesting<00:21:59.340> that<00:21:59.520> everyone's 00:21:59.960 --> 00:21:59.970 align:start position:0% more people requesting that everyone's 00:21:59.970 --> 00:22:01.340 align:start position:0% more people requesting that everyone's keys<00:22:00.180> than<00:22:00.390> where<00:22:00.480> messages<00:22:00.750> are<00:22:00.990> sent 00:22:01.340 --> 00:22:01.350 align:start position:0% keys than where messages are sent 00:22:01.350 --> 00:22:02.420 align:start position:0% keys than where messages are sent so<00:22:01.500> that's<00:22:01.680> just<00:22:01.830> kind<00:22:01.920> of<00:22:02.070> good<00:22:02.190> crazy 00:22:02.420 --> 00:22:02.430 align:start position:0% so that's just kind of good crazy 00:22:02.430 --> 00:22:07.160 align:start position:0% so that's just kind of good crazy probably<00:22:02.670> right<00:22:02.910> now<00:22:03.060> um<00:22:03.770> so<00:22:04.770> then<00:22:05.870> down<00:22:06.870> here 00:22:07.160 --> 00:22:07.170 align:start position:0% probably right now um so then down here 00:22:07.170 --> 00:22:10.790 align:start position:0% probably right now um so then down here on<00:22:07.560> the<00:22:07.680> no<00:22:07.800> imperius<00:22:08.130> screen<00:22:08.430> um<00:22:09.330> oh<00:22:09.990> yeah<00:22:10.740> I 00:22:10.790 --> 00:22:10.800 align:start position:0% on the no imperius screen um oh yeah I 00:22:10.800 --> 00:22:12.710 align:start position:0% on the no imperius screen um oh yeah I definitely<00:22:11.430> did<00:22:11.520> not<00:22:11.550> design<00:22:12.060> this<00:22:12.240> for<00:22:12.480> this 00:22:12.710 --> 00:22:12.720 align:start position:0% definitely did not design this for this 00:22:12.720 --> 00:22:15.350 align:start position:0% definitely did not design this for this many<00:22:12.900> people<00:22:12.960> TV<00:22:13.380> news<00:22:13.680> I<00:22:14.000> bought<00:22:15.000> this<00:22:15.120> like 00:22:15.350 --> 00:22:15.360 align:start position:0% many people TV news I bought this like 00:22:15.360 --> 00:22:21.800 align:start position:0% many people TV news I bought this like this<00:22:16.400> um<00:22:17.400> so<00:22:18.360> you<00:22:18.960> can<00:22:19.170> basically<00:22:19.970> choose<00:22:20.970> the 00:22:21.800 --> 00:22:21.810 align:start position:0% this um so you can basically choose the 00:22:21.810 --> 00:22:24.290 align:start position:0% this um so you can basically choose the keys<00:22:22.100> or<00:22:23.100> the<00:22:23.220> identities<00:22:23.670> that<00:22:23.700> you<00:22:23.880> actually 00:22:24.290 --> 00:22:24.300 align:start position:0% keys or the identities that you actually 00:22:24.300 --> 00:22:27.380 align:start position:0% keys or the identities that you actually want<00:22:24.540> to<00:22:24.570> send<00:22:24.980> encrypted<00:22:25.980> messages<00:22:26.640> to<00:22:26.820> and 00:22:27.380 --> 00:22:27.390 align:start position:0% want to send encrypted messages to and 00:22:27.390 --> 00:22:42.470 align:start position:0% want to send encrypted messages to and then<00:22:27.600> when<00:22:28.050> you<00:22:35.240> on<00:22:36.290> and<00:22:37.670> then<00:22:38.670> every<00:22:40.610> but<00:22:41.610> in 00:22:42.470 --> 00:22:42.480 align:start position:0% then when you on and then every but in 00:22:42.480 --> 00:22:45.830 align:start position:0% then when you on and then every but in example<00:22:42.960> um<00:22:44.150> answer<00:22:45.150> then<00:22:45.300> basically 00:22:45.830 --> 00:22:45.840 align:start position:0% example um answer then basically 00:22:45.840 --> 00:22:48.160 align:start position:0% example um answer then basically everybody<00:22:46.170> that<00:22:46.320> I<00:22:46.350> selected<00:22:46.860> will<00:22:47.280> get<00:22:47.580> a 00:22:48.160 --> 00:22:48.170 align:start position:0% everybody that I selected will get a 00:22:48.170 --> 00:22:50.330 align:start position:0% everybody that I selected will get a copy<00:22:49.170> of<00:22:49.380> that<00:22:49.440> message<00:22:49.860> that<00:22:49.980> they<00:22:50.160> can 00:22:50.330 --> 00:22:50.340 align:start position:0% copy of that message that they can 00:22:50.340 --> 00:22:52.490 align:start position:0% copy of that message that they can decrypt<00:22:50.640> but<00:22:51.240> everybody<00:22:51.720> gets<00:22:51.990> everybody's 00:22:52.490 --> 00:22:52.500 align:start position:0% decrypt but everybody gets everybody's 00:22:52.500 --> 00:22:54.650 align:start position:0% decrypt but everybody gets everybody's message<00:22:52.830> so<00:22:53.280> but<00:22:53.820> the<00:22:53.940> thing<00:22:53.970> is<00:22:54.240> that<00:22:54.510> only 00:22:54.650 --> 00:22:54.660 align:start position:0% message so but the thing is that only 00:22:54.660 --> 00:22:56.840 align:start position:0% message so but the thing is that only the<00:22:55.020> people<00:22:55.170> if<00:22:55.440> you<00:22:55.590> buy<00:22:56.130> encrypted<00:22:56.820> that 00:22:56.840 --> 00:22:56.850 align:start position:0% the people if you buy encrypted that 00:22:56.850 --> 00:23:00.130 align:start position:0% the people if you buy encrypted that message<00:22:57.270> specifically<00:22:57.720> for<00:22:58.080> will<00:22:58.680> be<00:22:58.830> able<00:22:59.130> to 00:23:00.130 --> 00:23:00.140 align:start position:0% message specifically for will be able to 00:23:00.140 --> 00:23:04.070 align:start position:0% message specifically for will be able to decrypt<00:23:01.140> it<00:23:02.420> I'm<00:23:03.420> going<00:23:03.630> to<00:23:03.660> refresh<00:23:03.930> this 00:23:04.070 --> 00:23:04.080 align:start position:0% decrypt it I'm going to refresh this 00:23:04.080 --> 00:23:05.780 align:start position:0% decrypt it I'm going to refresh this page<00:23:04.140> because<00:23:04.500> all<00:23:04.980> the<00:23:05.100> people<00:23:05.220> joined<00:23:05.670> have 00:23:05.780 --> 00:23:05.790 align:start position:0% page because all the people joined have 00:23:05.790 --> 00:23:11.180 align:start position:0% page because all the people joined have a<00:23:05.820> pair<00:23:06.090> of<00:23:06.120> mine<00:23:06.330> with<00:23:06.600> you<00:23:06.780> um<00:23:08.600> so<00:23:09.980> to<00:23:10.980> take<00:23:11.130> it 00:23:11.180 --> 00:23:11.190 align:start position:0% a pair of mine with you um so to take it 00:23:11.190 --> 00:23:17.600 align:start position:0% a pair of mine with you um so to take it kind<00:23:11.550> of<00:23:11.580> back<00:23:11.820> to<00:23:11.850> the<00:23:13.040> original<00:23:16.340> prologue<00:23:17.340> of 00:23:17.600 --> 00:23:17.610 align:start position:0% kind of back to the original prologue of 00:23:17.610 --> 00:23:23.890 align:start position:0% kind of back to the original prologue of the<00:23:17.700> top<00:23:17.880> and<00:23:20.510> the<00:23:21.510> idea<00:23:21.720> of<00:23:21.780> cyberspace<00:23:22.160> um 00:23:23.890 --> 00:23:23.900 align:start position:0% the top and the idea of cyberspace um 00:23:23.900 --> 00:23:27.950 align:start position:0% the top and the idea of cyberspace um that's<00:23:24.900> kind<00:23:25.200> of<00:23:25.350> what<00:23:26.340> I<00:23:26.370> built<00:23:26.640> this 00:23:27.950 --> 00:23:27.960 align:start position:0% that's kind of what I built this 00:23:27.960 --> 00:23:31.549 align:start position:0% that's kind of what I built this of<00:23:28.860> an<00:23:28.980> example<00:23:29.249> of<00:23:29.460> so<00:23:30.090> the<00:23:30.600> actual<00:23:31.019> data 00:23:31.549 --> 00:23:31.559 align:start position:0% of an example of so the actual data 00:23:31.559 --> 00:23:33.680 align:start position:0% of an example of so the actual data transport<00:23:32.279> like<00:23:32.730> layer<00:23:33.090> of<00:23:33.389> this<00:23:33.509> application 00:23:33.680 --> 00:23:33.690 align:start position:0% transport like layer of this application 00:23:33.690 --> 00:23:37.039 align:start position:0% transport like layer of this application is<00:23:34.940> completely<00:23:35.940> public<00:23:36.419> and<00:23:36.629> then<00:23:36.869> anybody 00:23:37.039 --> 00:23:37.049 align:start position:0% is completely public and then anybody 00:23:37.049 --> 00:23:39.230 align:start position:0% is completely public and then anybody can<00:23:37.350> read<00:23:37.529> it<00:23:37.679> it<00:23:38.129> just<00:23:38.309> it<00:23:38.549> takes<00:23:38.759> place<00:23:38.940> on<00:23:39.179> a 00:23:39.230 --> 00:23:39.240 align:start position:0% can read it it just it takes place on a 00:23:39.240 --> 00:23:42.379 align:start position:0% can read it it just it takes place on a public<00:23:39.899> ID<00:23:40.080> FS<00:23:40.409> topic<00:23:41.009> but<00:23:41.639> there<00:23:41.789> actually<00:23:42.269> is 00:23:42.379 --> 00:23:42.389 align:start position:0% public ID FS topic but there actually is 00:23:42.389 --> 00:23:44.960 align:start position:0% public ID FS topic but there actually is a<00:23:42.450> complex<00:23:43.379> application<00:23:44.100> logic<00:23:44.220> of<00:23:44.669> you<00:23:44.879> know 00:23:44.960 --> 00:23:44.970 align:start position:0% a complex application logic of you know 00:23:44.970 --> 00:23:48.680 align:start position:0% a complex application logic of you know a<00:23:44.999> permission<00:23:45.389> group<00:23:45.899> chat<00:23:47.480> happening<00:23:48.480> in 00:23:48.680 --> 00:23:48.690 align:start position:0% a permission group chat happening in 00:23:48.690 --> 00:23:51.230 align:start position:0% a permission group chat happening in this<00:23:48.809> public<00:23:49.230> forum<00:23:49.470> so<00:23:50.220> this<00:23:50.549> is<00:23:50.700> kind<00:23:50.909> of<00:23:51.059> the 00:23:51.230 --> 00:23:51.240 align:start position:0% this public forum so this is kind of the 00:23:51.240 --> 00:23:53.450 align:start position:0% this public forum so this is kind of the idea<00:23:51.509> of<00:23:51.600> cyberspace<00:23:52.019> that<00:23:52.350> we<00:23:52.529> can<00:23:52.799> kind<00:23:53.309> of 00:23:53.450 --> 00:23:53.460 align:start position:0% idea of cyberspace that we can kind of 00:23:53.460 --> 00:23:56.989 align:start position:0% idea of cyberspace that we can kind of divorce<00:23:54.320> application<00:23:55.320> logic<00:23:55.529> from<00:23:56.340> transport 00:23:56.989 --> 00:23:56.999 align:start position:0% divorce application logic from transport 00:23:56.999 --> 00:23:59.749 align:start position:0% divorce application logic from transport network<00:23:57.570> logic<00:23:58.019> and<00:23:58.289> even<00:23:58.740> database<00:23:59.399> storage 00:23:59.749 --> 00:23:59.759 align:start position:0% network logic and even database storage 00:23:59.759 --> 00:24:01.369 align:start position:0% network logic and even database storage logic<00:24:00.240> but<00:24:00.419> we<00:24:00.539> shouldn't<00:24:00.840> have<00:24:00.990> to<00:24:01.169> care 00:24:01.369 --> 00:24:01.379 align:start position:0% logic but we shouldn't have to care 00:24:01.379 --> 00:24:03.109 align:start position:0% logic but we shouldn't have to care about<00:24:01.710> where<00:24:02.460> the<00:24:02.669> data<00:24:02.789> for<00:24:03.029> this 00:24:03.109 --> 00:24:03.119 align:start position:0% about where the data for this 00:24:03.119 --> 00:24:05.180 align:start position:0% about where the data for this application<00:24:03.299> lives<00:24:03.899> all<00:24:04.619> we<00:24:04.799> have<00:24:04.919> to<00:24:05.039> care 00:24:05.180 --> 00:24:05.190 align:start position:0% application lives all we have to care 00:24:05.190 --> 00:24:07.220 align:start position:0% application lives all we have to care about<00:24:05.220> is<00:24:05.519> availability<00:24:06.149> that<00:24:06.600> product<00:24:07.080> still 00:24:07.220 --> 00:24:07.230 align:start position:0% about is availability that product still 00:24:07.230 --> 00:24:11.109 align:start position:0% about is availability that product still hasn't<00:24:07.440> really<00:24:07.559> been<00:24:07.710> solved<00:24:07.980> yet<00:24:08.159> but<00:24:09.919> and 00:24:11.109 --> 00:24:11.119 align:start position:0% hasn't really been solved yet but and 00:24:11.119 --> 00:24:13.430 align:start position:0% hasn't really been solved yet but and then<00:24:12.119> just<00:24:12.330> write<00:24:12.570> our<00:24:12.720> own<00:24:12.749> application 00:24:13.430 --> 00:24:13.440 align:start position:0% then just write our own application 00:24:13.440 --> 00:24:15.169 align:start position:0% then just write our own application logic<00:24:13.529> using<00:24:14.100> you<00:24:14.549> know<00:24:14.669> these<00:24:15.059> different 00:24:15.169 --> 00:24:15.179 align:start position:0% logic using you know these different 00:24:15.179 --> 00:24:16.820 align:start position:0% logic using you know these different cryptographic<00:24:15.600> primitives<00:24:16.409> to<00:24:16.499> kind<00:24:16.769> of 00:24:16.820 --> 00:24:16.830 align:start position:0% cryptographic primitives to kind of 00:24:16.830 --> 00:24:20.090 align:start position:0% cryptographic primitives to kind of enforce<00:24:17.309> our<00:24:17.490> rules<00:24:17.789> of<00:24:17.940> our<00:24:17.999> applications<00:24:19.100> so 00:24:20.090 --> 00:24:20.100 align:start position:0% enforce our rules of our applications so 00:24:20.100 --> 00:24:23.090 align:start position:0% enforce our rules of our applications so this<00:24:21.090> application<00:24:21.269> you<00:24:21.990> know<00:24:22.110> it's<00:24:22.350> certainly 00:24:23.090 --> 00:24:23.100 align:start position:0% this application you know it's certainly 00:24:23.100 --> 00:24:25.669 align:start position:0% this application you know it's certainly pretty<00:24:23.340> peer<00:24:23.610> just<00:24:23.850> exists<00:24:24.299> on<00:24:24.539> all<00:24:25.379> of<00:24:25.590> our 00:24:25.669 --> 00:24:25.679 align:start position:0% pretty peer just exists on all of our 00:24:25.679 --> 00:24:28.149 align:start position:0% pretty peer just exists on all of our friends<00:24:26.070> and<00:24:26.190> our<00:24:26.249> laptops<00:24:26.669> in<00:24:26.820> this<00:24:26.940> room<00:24:27.179> and 00:24:28.149 --> 00:24:28.159 align:start position:0% friends and our laptops in this room and 00:24:28.159 --> 00:24:30.560 align:start position:0% friends and our laptops in this room and you<00:24:29.159> know<00:24:29.249> we're<00:24:29.399> basically<00:24:30.090> sending<00:24:30.419> each 00:24:30.560 --> 00:24:30.570 align:start position:0% you know we're basically sending each 00:24:30.570 --> 00:24:33.230 align:start position:0% you know we're basically sending each other<00:24:30.720> plain<00:24:30.990> text<00:24:31.230> messages<00:24:31.619> but<00:24:31.889> then<00:24:32.240> all 00:24:33.230 --> 00:24:33.240 align:start position:0% other plain text messages but then all 00:24:33.240 --> 00:24:34.820 align:start position:0% other plain text messages but then all these<00:24:33.419> different<00:24:33.720> cryptographic<00:24:33.990> tools<00:24:34.409> kind 00:24:34.820 --> 00:24:34.830 align:start position:0% these different cryptographic tools kind 00:24:34.830 --> 00:24:37.639 align:start position:0% these different cryptographic tools kind of<00:24:34.919> allow<00:24:35.129> us<00:24:35.309> to<00:24:35.639> have<00:24:36.450> a<00:24:36.529> you<00:24:37.529> know<00:24:37.619> a 00:24:37.639 --> 00:24:37.649 align:start position:0% of allow us to have a you know a 00:24:37.649 --> 00:24:40.340 align:start position:0% of allow us to have a you know a structured<00:24:38.279> application<00:24:38.960> built<00:24:39.960> in<00:24:40.200> this 00:24:40.340 --> 00:24:40.350 align:start position:0% structured application built in this 00:24:40.350 --> 00:24:44.720 align:start position:0% structured application built in this really<00:24:40.559> simple<00:24:40.889> context<00:24:41.899> so<00:24:42.899> oh<00:24:43.320> and<00:24:43.950> for 00:24:44.720 --> 00:24:44.730 align:start position:0% really simple context so oh and for 00:24:44.730 --> 00:24:46.850 align:start position:0% really simple context so oh and for those<00:24:44.820> of<00:24:44.879> you<00:24:45.149> on<00:24:45.269> desktop<00:24:45.710> it's<00:24:46.710> gonna 00:24:46.850 --> 00:24:46.860 align:start position:0% those of you on desktop it's gonna 00:24:46.860 --> 00:24:48.019 align:start position:0% those of you on desktop it's gonna really<00:24:46.980> fit<00:24:47.190> in<00:24:47.279> the<00:24:47.340> mobile<00:24:47.580> view<00:24:47.730> but<00:24:47.999> you 00:24:48.019 --> 00:24:48.029 align:start position:0% really fit in the mobile view but you 00:24:48.029 --> 00:24:52.249 align:start position:0% really fit in the mobile view but you can<00:24:48.299> actually<00:24:48.450> look<00:24:48.720> at<00:24:49.369> the<00:24:51.049> Mickey<00:24:52.049> space 00:24:52.249 --> 00:24:52.259 align:start position:0% can actually look at the Mickey space 00:24:52.259 --> 00:24:53.389 align:start position:0% can actually look at the Mickey space parameters<00:24:52.649> that<00:24:52.799> I<00:24:52.889> kind<00:24:53.070> of<00:24:53.100> talked<00:24:53.279> through 00:24:53.389 --> 00:24:53.399 align:start position:0% parameters that I kind of talked through 00:24:53.399 --> 00:24:55.549 align:start position:0% parameters that I kind of talked through Annie<00:24:53.759> and<00:24:54.149> the<00:24:54.419> first<00:24:54.629> portion<00:24:54.869> so<00:24:55.289> you<00:24:55.379> have 00:24:55.549 --> 00:24:55.559 align:start position:0% Annie and the first portion so you have 00:24:55.559 --> 00:24:57.529 align:start position:0% Annie and the first portion so you have like<00:24:55.740> your<00:24:56.249> unassigned<00:24:56.639> seat<00:24:56.850> so<00:24:57.179> this<00:24:57.360> is 00:24:57.529 --> 00:24:57.539 align:start position:0% like your unassigned seat so this is 00:24:57.539 --> 00:24:59.210 align:start position:0% like your unassigned seat so this is like<00:24:57.720> what<00:24:58.230> do<00:24:58.289> you<00:24:58.350> sign<00:24:58.559> to<00:24:58.799> generate<00:24:59.100> your 00:24:59.210 --> 00:24:59.220 align:start position:0% like what do you sign to generate your 00:24:59.220 --> 00:25:03.169 align:start position:0% like what do you sign to generate your password<00:24:59.869> this<00:25:00.869> is<00:25:01.110> the<00:25:01.379> the<00:25:02.149> password<00:25:03.149> that 00:25:03.169 --> 00:25:03.179 align:start position:0% password this is the the password that 00:25:03.179 --> 00:25:04.860 align:start position:0% password this is the the password that basically<00:25:04.110> encrypts<00:25:04.590> your 00:25:04.860 --> 00:25:04.870 align:start position:0% basically encrypts your 00:25:04.870 --> 00:25:08.040 align:start position:0% basically encrypts your Keep<00:25:05.230> Calm<00:25:05.850> then<00:25:06.850> this<00:25:07.030> is<00:25:07.180> the<00:25:07.330> gtp<00:25:07.720> public 00:25:08.040 --> 00:25:08.050 align:start position:0% Keep Calm then this is the gtp public 00:25:08.050 --> 00:25:10.710 align:start position:0% Keep Calm then this is the gtp public key<00:25:08.200> and<00:25:08.500> the<00:25:08.620> encrypted<00:25:09.220> PTV<00:25:09.580> private<00:25:10.030> key<00:25:10.180> so 00:25:10.710 --> 00:25:10.720 align:start position:0% key and the encrypted PTV private key so 00:25:10.720 --> 00:25:12.180 align:start position:0% key and the encrypted PTV private key so these<00:25:10.840> are<00:25:11.020> kind<00:25:11.230> of<00:25:11.320> the<00:25:11.530> you<00:25:11.980> know<00:25:12.040> the 00:25:12.180 --> 00:25:12.190 align:start position:0% these are kind of the you know the 00:25:12.190 --> 00:25:13.950 align:start position:0% these are kind of the you know the building<00:25:12.490> blocks<00:25:12.760> that<00:25:13.059> were<00:25:13.240> using<00:25:13.660> to<00:25:13.809> build 00:25:13.950 --> 00:25:13.960 align:start position:0% building blocks that were using to build 00:25:13.960 --> 00:25:19.170 align:start position:0% building blocks that were using to build this<00:25:14.110> application<00:25:16.410> I<00:25:18.000> think<00:25:19.000> if<00:25:19.059> there's 00:25:19.170 --> 00:25:19.180 align:start position:0% this application I think if there's 00:25:19.180 --> 00:25:23.160 align:start position:0% this application I think if there's anything<00:25:19.210> else<00:25:19.510> about<00:25:19.660> this<00:25:19.809> one<00:25:20.020> oh<00:25:20.580> yeah<00:25:22.170> the 00:25:23.160 --> 00:25:23.170 align:start position:0% anything else about this one oh yeah the 00:25:23.170 --> 00:25:24.990 align:start position:0% anything else about this one oh yeah the nickname<00:25:23.559> I<00:25:23.860> can't<00:25:24.430> get<00:25:24.550> to<00:25:24.700> it<00:25:24.730> because 00:25:24.990 --> 00:25:25.000 align:start position:0% nickname I can't get to it because 00:25:25.000 --> 00:25:27.330 align:start position:0% nickname I can't get to it because there's<00:25:25.150> too<00:25:25.210> many<00:25:25.270> people<00:25:25.390> but<00:25:26.350> as<00:25:26.890> those<00:25:27.190> of 00:25:27.330 --> 00:25:27.340 align:start position:0% there's too many people but as those of 00:25:27.340 --> 00:25:29.520 align:start position:0% there's too many people but as those of you<00:25:27.430> have<00:25:27.670> said<00:25:28.270> it<00:25:28.390> you<00:25:28.570> know<00:25:28.600> the<00:25:29.170> nickname 00:25:29.520 --> 00:25:29.530 align:start position:0% you have said it you know the nickname 00:25:29.530 --> 00:25:31.799 align:start position:0% you have said it you know the nickname is<00:25:29.559> just<00:25:29.860> exists<00:25:30.850> as<00:25:31.000> one<00:25:31.270> other<00:25:31.450> type<00:25:31.660> of 00:25:31.799 --> 00:25:31.809 align:start position:0% is just exists as one other type of 00:25:31.809 --> 00:25:33.630 align:start position:0% is just exists as one other type of specialized<00:25:32.230> message<00:25:32.890> on<00:25:33.040> the<00:25:33.130> network<00:25:33.430> so 00:25:33.630 --> 00:25:33.640 align:start position:0% specialized message on the network so 00:25:33.640 --> 00:25:35.760 align:start position:0% specialized message on the network so you<00:25:33.760> can<00:25:33.880> kind<00:25:34.059> of<00:25:34.150> announce<00:25:34.840> your<00:25:35.410> nickname 00:25:35.760 --> 00:25:35.770 align:start position:0% you can kind of announce your nickname 00:25:35.770 --> 00:25:38.360 align:start position:0% you can kind of announce your nickname when<00:25:35.920> you<00:25:36.070> announce<00:25:36.340> your<00:25:36.580> your<00:25:37.210> your<00:25:37.600> teacher 00:25:38.360 --> 00:25:38.370 align:start position:0% when you announce your your your teacher 00:25:38.370 --> 00:25:45.360 align:start position:0% when you announce your your your teacher um<00:25:39.990> yeah<00:25:40.990> that<00:25:41.020> said<00:25:42.720> that's<00:25:43.720> it<00:25:43.990> for<00:25:44.170> the<00:25:44.370> oh 00:25:45.360 --> 00:25:45.370 align:start position:0% um yeah that said that's it for the oh 00:25:45.370 --> 00:25:50.610 align:start position:0% um yeah that said that's it for the oh yeah<00:25:45.880> I'm<00:25:45.970> sorry<00:25:46.179> I<00:25:46.420> have<00:25:46.840> a<00:25:46.870> thing<00:25:49.230> so<00:25:50.230> if<00:25:50.500> you 00:25:50.610 --> 00:25:50.620 align:start position:0% yeah I'm sorry I have a thing so if you 00:25:50.620 --> 00:25:54.030 align:start position:0% yeah I'm sorry I have a thing so if you have<00:25:50.770> this<00:25:50.920> loaded<00:25:51.309> and<00:25:52.030> you<00:25:52.690> actually<00:25:53.050> want 00:25:54.030 --> 00:25:54.040 align:start position:0% have this loaded and you actually want 00:25:54.040 --> 00:25:56.669 align:start position:0% have this loaded and you actually want to<00:25:54.100> look<00:25:54.190> at<00:25:54.520> some<00:25:55.390> of<00:25:55.420> the<00:25:55.630> code<00:25:55.840> for<00:25:56.590> the 00:25:56.669 --> 00:25:56.679 align:start position:0% to look at some of the code for the 00:25:56.679 --> 00:25:59.580 align:start position:0% to look at some of the code for the application<00:25:57.150> um<00:25:58.150> you<00:25:59.020> can<00:25:59.140> click<00:25:59.380> the 00:25:59.580 --> 00:25:59.590 align:start position:0% application um you can click the 00:25:59.590 --> 00:26:01.350 align:start position:0% application um you can click the question<00:26:00.100> mark<00:26:00.280> in<00:26:00.520> the<00:26:00.580> top<00:26:00.640> right<00:26:00.820> and<00:26:01.210> it'll 00:26:01.350 --> 00:26:01.360 align:start position:0% question mark in the top right and it'll 00:26:01.360 --> 00:26:06.120 align:start position:0% question mark in the top right and it'll open<00:26:01.690> up<00:26:01.960> to<00:26:02.080> github<00:26:02.200> um<00:26:04.200> kind<00:26:05.200> of<00:26:05.350> talks<00:26:06.040> a 00:26:06.120 --> 00:26:06.130 align:start position:0% open up to github um kind of talks a 00:26:06.130 --> 00:26:09.240 align:start position:0% open up to github um kind of talks a little<00:26:06.280> bit<00:26:06.400> about<00:26:06.600> what<00:26:07.600> it<00:26:07.690> is<00:26:08.160> to<00:26:09.160> the 00:26:09.240 --> 00:26:09.250 align:start position:0% little bit about what it is to the 00:26:09.250 --> 00:26:11.520 align:start position:0% little bit about what it is to the application<00:26:09.820> links<00:26:10.809> to<00:26:10.900> the<00:26:11.020> slides<00:26:11.260> in<00:26:11.440> the 00:26:11.520 --> 00:26:11.530 align:start position:0% application links to the slides in the 00:26:11.530 --> 00:26:15.299 align:start position:0% application links to the slides in the slideshow<00:26:11.770> and<00:26:12.340> then<00:26:13.380> links<00:26:14.380> to<00:26:14.590> key<00:26:15.100> space 00:26:15.299 --> 00:26:15.309 align:start position:0% slideshow and then links to key space 00:26:15.309 --> 00:26:17.160 align:start position:0% slideshow and then links to key space which<00:26:15.580> is<00:26:15.760> ondol<00:26:16.420> this<00:26:16.540> part<00:26:16.720> over<00:26:16.780> here<00:26:16.870> swatc 00:26:17.160 --> 00:26:17.170 align:start position:0% which is ondol this part over here swatc 00:26:17.170 --> 00:26:20.520 align:start position:0% which is ondol this part over here swatc I<00:26:17.320> guess<00:26:18.030> you<00:26:19.030> can<00:26:19.270> look<00:26:19.960> at<00:26:20.050> the<00:26:20.110> code<00:26:20.260> of<00:26:20.380> the 00:26:20.520 --> 00:26:20.530 align:start position:0% I guess you can look at the code of the 00:26:20.530 --> 00:26:21.840 align:start position:0% I guess you can look at the code of the application<00:26:20.650> even<00:26:21.309> though<00:26:21.400> I<00:26:21.429> wrote<00:26:21.700> it 00:26:21.840 --> 00:26:21.850 align:start position:0% application even though I wrote it 00:26:21.850 --> 00:26:23.580 align:start position:0% application even though I wrote it really<00:26:22.030> fast<00:26:22.300> so<00:26:22.870> it's<00:26:23.050> not<00:26:23.170> very<00:26:23.380> good 00:26:23.580 --> 00:26:23.590 align:start position:0% really fast so it's not very good 00:26:23.590 --> 00:26:27.210 align:start position:0% really fast so it's not very good alright<00:26:24.130> it<00:26:24.370> spits<00:26:24.580> nasty<00:26:24.940> but<00:26:25.270> uh<00:26:25.830> I<00:26:26.830> would 00:26:27.210 --> 00:26:27.220 align:start position:0% alright it spits nasty but uh I would 00:26:27.220 --> 00:26:29.220 align:start position:0% alright it spits nasty but uh I would instead<00:26:28.059> suggest<00:26:28.450> they<00:26:28.540> actually<00:26:28.870> look<00:26:29.080> at 00:26:29.220 --> 00:26:29.230 align:start position:0% instead suggest they actually look at 00:26:29.230 --> 00:26:32.730 align:start position:0% instead suggest they actually look at the<00:26:30.190> key<00:26:30.400> space<00:26:30.690> and<00:26:31.690> then<00:26:32.140> your<00:26:32.290> soft<00:26:32.530> jazz 00:26:32.730 --> 00:26:32.740 align:start position:0% the key space and then your soft jazz 00:26:32.740 --> 00:26:35.760 align:start position:0% the key space and then your soft jazz library<00:26:33.100> which<00:26:34.030> actually<00:26:34.360> has<00:26:34.510> some<00:26:35.440> better 00:26:35.760 --> 00:26:35.770 align:start position:0% library which actually has some better 00:26:35.770 --> 00:26:38.040 align:start position:0% library which actually has some better examples<00:26:35.920> of<00:26:36.429> documentation<00:26:36.850> and<00:26:37.059> his 00:26:38.040 --> 00:26:38.050 align:start position:0% examples of documentation and his 00:26:38.050 --> 00:26:41.070 align:start position:0% examples of documentation and his interviews<00:26:38.650> um<00:26:39.570> so<00:26:40.570> yeah<00:26:40.690> after<00:26:40.900> when<00:26:41.020> I 00:26:41.070 --> 00:26:41.080 align:start position:0% interviews um so yeah after when I 00:26:41.080 --> 00:26:43.380 align:start position:0% interviews um so yeah after when I include<00:26:41.530> a<00:26:41.559> key<00:26:42.429> space<00:26:42.580> in<00:26:42.760> your<00:26:42.850> application 00:26:43.380 --> 00:26:43.390 align:start position:0% include a key space in your application 00:26:43.390 --> 00:26:45.360 align:start position:0% include a key space in your application um<00:26:43.690> this<00:26:44.140> is<00:26:44.290> where<00:26:44.440> you<00:26:44.559> would<00:26:44.650> go<00:26:45.070> to<00:26:45.100> figure 00:26:45.360 --> 00:26:45.370 align:start position:0% um this is where you would go to figure 00:26:45.370 --> 00:26:48.790 align:start position:0% um this is where you would go to figure out<00:26:45.520> you<00:26:45.850> know<00:26:45.970> um<00:26:47.010> yeah<00:26:48.010> I<00:26:48.280> think 00:26:48.790 --> 00:26:48.800 align:start position:0% out you know um yeah I think 00:26:48.800 --> 00:26:54.610 align:start position:0% out you know um yeah I think is<00:26:48.940> that's<00:26:49.940> it<00:26:50.180> for<00:26:50.360> my<00:26:50.480> demo<00:26:50.930> um<00:26:51.410> I<00:26:52.270> think<00:26:53.620> yeah 00:26:54.610 --> 00:26:54.620 align:start position:0% is that's it for my demo um I think yeah 00:26:54.620 --> 00:26:57.130 align:start position:0% is that's it for my demo um I think yeah so<00:26:54.890> my<00:26:55.010> head<00:26:55.130> blog<00:26:55.340> was<00:26:55.610> about<00:26:56.420> putting<00:26:56.870> it<00:26:57.080> in 00:26:57.130 --> 00:26:57.140 align:start position:0% so my head blog was about putting it in 00:26:57.140 --> 00:27:00.490 align:start position:0% so my head blog was about putting it in the<00:26:57.200> context<00:26:57.710> of<00:26:57.880> cyberspace<00:26:58.880> and<00:26:59.380> you<00:27:00.380> know 00:27:00.490 --> 00:27:00.500 align:start position:0% the context of cyberspace and you know 00:27:00.500 --> 00:27:02.500 align:start position:0% the context of cyberspace and you know this<00:27:00.980> this<00:27:01.280> kind<00:27:01.490> of<00:27:01.520> application<00:27:01.670> right<00:27:02.360> now 00:27:02.500 --> 00:27:02.510 align:start position:0% this this kind of application right now 00:27:02.510 --> 00:27:05.560 align:start position:0% this this kind of application right now it's<00:27:02.660> turning<00:27:03.260> in<00:27:03.350> public<00:27:03.760> by<00:27:04.760> DFS<00:27:05.240> but<00:27:05.270> it 00:27:05.560 --> 00:27:05.570 align:start position:0% it's turning in public by DFS but it 00:27:05.570 --> 00:27:06.790 align:start position:0% it's turning in public by DFS but it could<00:27:05.690> be<00:27:05.780> running<00:27:06.050> on<00:27:06.170> any<00:27:06.410> kind<00:27:06.710> of 00:27:06.790 --> 00:27:06.800 align:start position:0% could be running on any kind of 00:27:06.800 --> 00:27:09.070 align:start position:0% could be running on any kind of transport<00:27:07.310> you<00:27:07.400> know<00:27:07.520> you<00:27:08.240> any<00:27:08.570> like 00:27:09.070 --> 00:27:09.080 align:start position:0% transport you know you any like 00:27:09.080 --> 00:27:10.450 align:start position:0% transport you know you any like messaging<00:27:09.590> system<00:27:09.980> you<00:27:10.130> could<00:27:10.280> have<00:27:10.370> an 00:27:10.450 --> 00:27:10.460 align:start position:0% messaging system you could have an 00:27:10.460 --> 00:27:12.250 align:start position:0% messaging system you could have an encrypted<00:27:10.880> messaging<00:27:11.420> system<00:27:11.750> built<00:27:11.930> inside 00:27:12.250 --> 00:27:12.260 align:start position:0% encrypted messaging system built inside 00:27:12.260 --> 00:27:14.950 align:start position:0% encrypted messaging system built inside of<00:27:12.410> it<00:27:12.530> and<00:27:13.180> you<00:27:14.180> know<00:27:14.240> the<00:27:14.540> stories<00:27:14.810> can 00:27:14.950 --> 00:27:14.960 align:start position:0% of it and you know the stories can 00:27:14.960 --> 00:27:19.240 align:start position:0% of it and you know the stories can happen<00:27:15.200> anywhere<00:27:15.470> so<00:27:16.310> I<00:27:16.640> think<00:27:17.360> that<00:27:17.720> um<00:27:18.250> the 00:27:19.240 --> 00:27:19.250 align:start position:0% happen anywhere so I think that um the 00:27:19.250 --> 00:27:23.110 align:start position:0% happen anywhere so I think that um the initial<00:27:20.470> Eris<00:27:21.470> walk<00:27:21.620> trading<00:27:21.950> network<00:27:22.190> was 00:27:23.110 --> 00:27:23.120 align:start position:0% initial Eris walk trading network was 00:27:23.120 --> 00:27:26.320 align:start position:0% initial Eris walk trading network was built<00:27:23.150> on<00:27:23.620> RabbitMQ<00:27:24.620> and<00:27:24.980> it's<00:27:25.610> easily 00:27:26.320 --> 00:27:26.330 align:start position:0% built on RabbitMQ and it's easily 00:27:26.330 --> 00:27:29.800 align:start position:0% built on RabbitMQ and it's easily portable<00:27:26.810> now<00:27:26.990> that<00:27:27.140> ipfs<00:27:27.590> because<00:27:28.490> of<00:27:29.390> like 00:27:29.800 --> 00:27:29.810 align:start position:0% portable now that ipfs because of like 00:27:29.810 --> 00:27:31.390 align:start position:0% portable now that ipfs because of like separation<00:27:30.500> of<00:27:30.710> concerns<00:27:30.830> that<00:27:31.160> we<00:27:31.280> were 00:27:31.390 --> 00:27:31.400 align:start position:0% separation of concerns that we were 00:27:31.400 --> 00:27:35.890 align:start position:0% separation of concerns that we were talking<00:27:31.640> about<00:27:31.700> so<00:27:32.570> I<00:27:33.350> think<00:27:33.950> that's<00:27:34.840> at<00:27:35.840> least 00:27:35.890 --> 00:27:35.900 align:start position:0% talking about so I think that's at least 00:27:35.900 --> 00:27:38.440 align:start position:0% talking about so I think that's at least what<00:27:36.110> I<00:27:36.140> believe<00:27:36.440> is<00:27:36.590> that<00:27:36.740> like<00:27:36.950> I<00:27:37.310> think<00:27:38.240> that 00:27:38.440 --> 00:27:38.450 align:start position:0% what I believe is that like I think that 00:27:38.450 --> 00:27:40.660 align:start position:0% what I believe is that like I think that if<00:27:38.870> we<00:27:39.110> follow<00:27:39.380> a<00:27:39.470> kind<00:27:39.680> of<00:27:39.800> this<00:27:39.890> paradigm<00:27:40.340> I 00:27:40.660 --> 00:27:40.670 align:start position:0% if we follow a kind of this paradigm I 00:27:40.670 --> 00:27:43.090 align:start position:0% if we follow a kind of this paradigm I think<00:27:41.120> that<00:27:41.360> like<00:27:41.770> applications<00:27:42.770> that<00:27:43.010> we 00:27:43.090 --> 00:27:43.100 align:start position:0% think that like applications that we 00:27:43.100 --> 00:27:44.290 align:start position:0% think that like applications that we build<00:27:43.340> in<00:27:43.460> the<00:27:43.490> future<00:27:43.700> that<00:27:44.270> are 00:27:44.290 --> 00:27:44.300 align:start position:0% build in the future that are 00:27:44.300 --> 00:27:47.350 align:start position:0% build in the future that are intrinsically<00:27:45.140> tied<00:27:45.640> to<00:27:46.640> a<00:27:46.670> certain<00:27:47.090> type<00:27:47.330> of 00:27:47.350 --> 00:27:47.360 align:start position:0% intrinsically tied to a certain type of 00:27:47.360 --> 00:27:49.090 align:start position:0% intrinsically tied to a certain type of what<00:27:48.020> transport<00:27:48.500> layer<00:27:48.680> like<00:27:48.920> for<00:27:49.040> example 00:27:49.090 --> 00:27:49.100 align:start position:0% what transport layer like for example 00:27:49.100 --> 00:27:51.610 align:start position:0% what transport layer like for example fetching<00:27:49.790> data<00:27:49.910> over<00:27:50.180> HTTP<00:27:50.810> fetching 00:27:51.610 --> 00:27:51.620 align:start position:0% fetching data over HTTP fetching 00:27:51.620 --> 00:27:52.870 align:start position:0% fetching data over HTTP fetching something<00:27:51.830> from<00:27:52.010> WebSocket<00:27:52.520> it's<00:27:52.670> going<00:27:52.820> to 00:27:52.870 --> 00:27:52.880 align:start position:0% something from WebSocket it's going to 00:27:52.880 --> 00:27:54.640 align:start position:0% something from WebSocket it's going to start<00:27:53.060> to<00:27:53.180> feel<00:27:53.330> like<00:27:53.510> spaghetti<00:27:53.870> code<00:27:54.080> is 00:27:54.640 --> 00:27:54.650 align:start position:0% start to feel like spaghetti code is 00:27:54.650 --> 00:27:55.960 align:start position:0% start to feel like spaghetti code is gonna<00:27:54.860> start<00:27:55.100> to<00:27:55.190> feel<00:27:55.370> like<00:27:55.550> expensive 00:27:55.960 --> 00:27:55.970 align:start position:0% gonna start to feel like expensive 00:27:55.970 --> 00:27:58.600 align:start position:0% gonna start to feel like expensive influx<00:27:56.720> debt<00:27:56.900> because<00:27:57.530> it's<00:27:57.680> hard<00:27:57.920> to<00:27:58.100> port 00:27:58.600 --> 00:27:58.610 align:start position:0% influx debt because it's hard to port 00:27:58.610 --> 00:28:00.400 align:start position:0% influx debt because it's hard to port it's<00:27:58.880> hard<00:27:59.060> to<00:27:59.360> you<00:28:00.020> have<00:28:00.200> all<00:28:00.320> these 00:28:00.400 --> 00:28:00.410 align:start position:0% it's hard to you have all these 00:28:00.410 --> 00:28:03.160 align:start position:0% it's hard to you have all these functions<00:28:00.980> in<00:28:01.370> your<00:28:01.430> code<00:28:01.790> about<00:28:02.120> like<00:28:02.450> how 00:28:03.160 --> 00:28:03.170 align:start position:0% functions in your code about like how 00:28:03.170 --> 00:28:06.340 align:start position:0% functions in your code about like how the<00:28:03.890> data<00:28:04.240> comes<00:28:05.240> to<00:28:05.420> you<00:28:05.540> how<00:28:05.780> its<00:28:05.930> available 00:28:06.340 --> 00:28:06.350 align:start position:0% the data comes to you how its available 00:28:06.350 --> 00:28:08.950 align:start position:0% the data comes to you how its available within<00:28:06.590> the<00:28:06.830> kind<00:28:07.010> of<00:28:07.070> areas<00:28:07.310> are<00:28:07.780> laughs<00:28:08.780> when 00:28:08.950 --> 00:28:08.960 align:start position:0% within the kind of areas are laughs when 00:28:08.960 --> 00:28:12.970 align:start position:0% within the kind of areas are laughs when you<00:28:09.050> fetch<00:28:09.230> it<00:28:09.260> and<00:28:09.970> I<00:28:10.970> think<00:28:11.210> that<00:28:11.450> with<00:28:12.440> this 00:28:12.970 --> 00:28:12.980 align:start position:0% you fetch it and I think that with this 00:28:12.980 --> 00:28:14.320 align:start position:0% you fetch it and I think that with this kind<00:28:13.280> of<00:28:13.550> approach<00:28:14.000> to<00:28:14.030> building 00:28:14.320 --> 00:28:14.330 align:start position:0% kind of approach to building 00:28:14.330 --> 00:28:16.480 align:start position:0% kind of approach to building applications<00:28:14.990> you<00:28:15.710> have<00:28:15.830> the<00:28:15.920> separation<00:28:16.280> of 00:28:16.480 --> 00:28:16.490 align:start position:0% applications you have the separation of 00:28:16.490 --> 00:28:19.150 align:start position:0% applications you have the separation of concerns<00:28:16.930> such<00:28:17.930> that<00:28:18.110> you<00:28:18.230> can<00:28:18.380> like<00:28:18.560> actually 00:28:19.150 --> 00:28:19.160 align:start position:0% concerns such that you can like actually 00:28:19.160 --> 00:28:21.460 align:start position:0% concerns such that you can like actually port<00:28:20.060> your<00:28:20.180> application<00:28:20.720> to<00:28:20.960> different<00:28:21.110> types 00:28:21.460 --> 00:28:21.470 align:start position:0% port your application to different types 00:28:21.470 --> 00:28:25.300 align:start position:0% port your application to different types of<00:28:21.590> transports<00:28:22.240> without<00:28:23.240> having<00:28:24.190> you<00:28:25.190> know<00:28:25.280> a 00:28:25.300 --> 00:28:25.310 align:start position:0% of transports without having you know a 00:28:25.310 --> 00:28:26.670 align:start position:0% of transports without having you know a lot<00:28:25.460> of<00:28:25.550> tech<00:28:25.730> tip<00:28:25.880> that<00:28:26.030> you<00:28:26.090> have<00:28:26.180> to<00:28:26.270> resolve 00:28:26.670 --> 00:28:26.680 align:start position:0% lot of tech tip that you have to resolve 00:28:26.680 --> 00:28:28.750 align:start position:0% lot of tech tip that you have to resolve so<00:28:27.680> yeah<00:28:27.800> that's<00:28:27.980> a<00:28:28.130> that's<00:28:28.430> it<00:28:28.550> for<00:28:28.670> my 00:28:28.750 --> 00:28:28.760 align:start position:0% so yeah that's a that's it for my 00:28:28.760 --> 00:28:40.960 align:start position:0% so yeah that's a that's it for my presentation<00:28:29.680> time<00:28:30.680> for<00:28:30.830> some<00:28:31.190> questions 00:28:40.960 --> 00:28:40.970 align:start position:0% 00:28:40.970 --> 00:28:44.240 align:start position:0% yeah<00:28:42.409> why<00:28:43.409> do<00:28:43.470> you<00:28:43.679> choose<00:28:43.890> certain 00:28:44.240 --> 00:28:44.250 align:start position:0% yeah why do you choose certain 00:28:44.250 --> 00:28:46.730 align:start position:0% yeah why do you choose certain particular<00:28:44.610> using<00:28:45.390> a<00:28:45.570> password<00:28:45.900> rather<00:28:46.470> than 00:28:46.730 --> 00:28:46.740 align:start position:0% particular using a password rather than 00:28:46.740 --> 00:28:51.799 align:start position:0% particular using a password rather than using<00:28:46.980> the<00:28:48.110> diffie-hellman<00:28:49.110> to<00:28:49.500> listen<00:28:50.809> with 00:28:51.799 --> 00:28:51.809 align:start position:0% using the diffie-hellman to listen with 00:28:51.809 --> 00:28:53.390 align:start position:0% using the diffie-hellman to listen with the<00:28:51.900> elliptic<00:28:52.320> curve<00:28:52.529> that<00:28:52.830> you<00:28:52.950> already<00:28:53.070> have 00:28:53.390 --> 00:28:53.400 align:start position:0% the elliptic curve that you already have 00:28:53.400 --> 00:28:56.510 align:start position:0% the elliptic curve that you already have from<00:28:53.820> hearing<00:28:54.390> address<00:28:54.779> huh<00:28:55.260> I<00:28:55.740> think<00:28:56.130> it's 00:28:56.510 --> 00:28:56.520 align:start position:0% from hearing address huh I think it's 00:28:56.520 --> 00:29:00.289 align:start position:0% from hearing address huh I think it's because<00:28:56.789> it's<00:28:57.000> not<00:28:57.409> available<00:28:58.460> to<00:28:59.460> deaf<00:29:00.000> users 00:29:00.289 --> 00:29:00.299 align:start position:0% because it's not available to deaf users 00:29:00.299 --> 00:29:03.019 align:start position:0% because it's not available to deaf users over<00:29:00.960> like<00:29:01.340> json-rpc 00:29:03.019 --> 00:29:03.029 align:start position:0% over like json-rpc 00:29:03.029 --> 00:29:05.000 align:start position:0% over like json-rpc like<00:29:03.690> Messick<00:29:04.200> it's<00:29:04.289> not<00:29:04.440> part<00:29:04.770> of<00:29:04.799> like<00:29:04.919> this 00:29:05.000 --> 00:29:05.010 align:start position:0% like Messick it's not part of like this 00:29:05.010 --> 00:29:08.570 align:start position:0% like Messick it's not part of like this standard<00:29:05.340> JSON<00:29:05.549> RPC<00:29:05.820> message<00:29:06.270> a<00:29:07.549> format<00:29:08.549> for 00:29:08.570 --> 00:29:08.580 align:start position:0% standard JSON RPC message a format for 00:29:08.580 --> 00:29:10.250 align:start position:0% standard JSON RPC message a format for like<00:29:09.090> interaction<00:29:09.630> with<00:29:09.750> a<00:29:09.809> private<00:29:10.110> key 00:29:10.250 --> 00:29:10.260 align:start position:0% like interaction with a private key 00:29:10.260 --> 00:29:12.380 align:start position:0% like interaction with a private key basically<00:29:10.830> say<00:29:11.070> like<00:29:11.250> the<00:29:11.700> only<00:29:11.970> like 00:29:12.380 --> 00:29:12.390 align:start position:0% basically say like the only like 00:29:12.390 --> 00:29:14.299 align:start position:0% basically say like the only like cryptographic<00:29:13.260> functioning<00:29:13.950> that<00:29:14.010> we<00:29:14.130> have 00:29:14.299 --> 00:29:14.309 align:start position:0% cryptographic functioning that we have 00:29:14.309 --> 00:29:17.360 align:start position:0% cryptographic functioning that we have available<00:29:14.549> to<00:29:14.909> us<00:29:14.940> as<00:29:15.890> people<00:29:16.890> who<00:29:17.159> build 00:29:17.360 --> 00:29:17.370 align:start position:0% available to us as people who build 00:29:17.370 --> 00:29:19.250 align:start position:0% available to us as people who build applications<00:29:18.059> that<00:29:18.210> work<00:29:18.450> on<00:29:18.600> top<00:29:18.720> of<00:29:18.899> wallets 00:29:19.250 --> 00:29:19.260 align:start position:0% applications that work on top of wallets 00:29:19.260 --> 00:29:21.529 align:start position:0% applications that work on top of wallets are<00:29:19.799> basically<00:29:20.130> like<00:29:20.340> you<00:29:20.700> know<00:29:20.730> personal 00:29:21.529 --> 00:29:21.539 align:start position:0% are basically like you know personal 00:29:21.539 --> 00:29:25.100 align:start position:0% are basically like you know personal sign<00:29:22.580> sent<00:29:23.580> trans<00:29:23.730> actually<00:29:24.090> and<00:29:24.299> is<00:29:24.539> we<00:29:24.960> don't 00:29:25.100 --> 00:29:25.110 align:start position:0% sign sent trans actually and is we don't 00:29:25.110 --> 00:29:27.080 align:start position:0% sign sent trans actually and is we don't there's<00:29:25.770> a<00:29:25.830> lot<00:29:26.070> of<00:29:26.340> cryptographic 00:29:27.080 --> 00:29:27.090 align:start position:0% there's a lot of cryptographic 00:29:27.090 --> 00:29:28.519 align:start position:0% there's a lot of cryptographic primitives<00:29:27.809> that<00:29:27.929> would<00:29:28.020> be<00:29:28.110> useful 00:29:28.519 --> 00:29:28.529 align:start position:0% primitives that would be useful 00:29:28.529 --> 00:29:30.590 align:start position:0% primitives that would be useful like<00:29:29.130> when<00:29:29.789> I<00:29:29.820> was<00:29:29.970> first<00:29:30.120> building<00:29:30.480> this 00:29:30.590 --> 00:29:30.600 align:start position:0% like when I was first building this 00:29:30.600 --> 00:29:32.240 align:start position:0% like when I was first building this thing<00:29:30.659> that<00:29:31.020> I<00:29:31.080> needed<00:29:31.380> for<00:29:31.649> encryption<00:29:31.980> I 00:29:32.240 --> 00:29:32.250 align:start position:0% thing that I needed for encryption I 00:29:32.250 --> 00:29:34.159 align:start position:0% thing that I needed for encryption I wanted<00:29:32.580> to<00:29:32.669> actually<00:29:32.850> you<00:29:33.659> know<00:29:33.690> I<00:29:33.809> was<00:29:34.049> like 00:29:34.159 --> 00:29:34.169 align:start position:0% wanted to actually you know I was like 00:29:34.169 --> 00:29:37.070 align:start position:0% wanted to actually you know I was like well<00:29:34.350> why<00:29:34.529> can't<00:29:34.770> I<00:29:34.830> use<00:29:35.010> the<00:29:35.659> you<00:29:36.659> know<00:29:36.779> the 00:29:37.070 --> 00:29:37.080 align:start position:0% well why can't I use the you know the 00:29:37.080 --> 00:29:38.840 align:start position:0% well why can't I use the you know the etherion<00:29:37.440> private<00:29:37.770> key<00:29:37.890> to<00:29:38.130> encrypt<00:29:38.309> data<00:29:38.549> you 00:29:38.840 --> 00:29:38.850 align:start position:0% etherion private key to encrypt data you 00:29:38.850 --> 00:29:41.630 align:start position:0% etherion private key to encrypt data you know<00:29:39.020> reticular<00:29:40.020> data<00:29:40.230> but<00:29:40.470> it's<00:29:41.010> possible 00:29:41.630 --> 00:29:41.640 align:start position:0% know reticular data but it's possible 00:29:41.640 --> 00:29:43.909 align:start position:0% know reticular data but it's possible like<00:29:42.029> theoretically<00:29:42.690> it's<00:29:42.840> possible<00:29:42.919> those 00:29:43.909 --> 00:29:43.919 align:start position:0% like theoretically it's possible those 00:29:43.919 --> 00:29:45.080 align:start position:0% like theoretically it's possible those functions<00:29:44.399> are<00:29:44.520> in<00:29:44.669> the<00:29:44.820> underlying 00:29:45.080 --> 00:29:45.090 align:start position:0% functions are in the underlying 00:29:45.090 --> 00:29:47.330 align:start position:0% functions are in the underlying cryptographic<00:29:45.419> libraries<00:29:46.169> that<00:29:46.470> you<00:29:47.190> know<00:29:47.309> a 00:29:47.330 --> 00:29:47.340 align:start position:0% cryptographic libraries that you know a 00:29:47.340 --> 00:29:49.970 align:start position:0% cryptographic libraries that you know a wallet<00:29:47.760> like<00:29:47.940> ledger<00:29:48.390> or<00:29:48.539> meta<00:29:48.809> mask<00:29:49.020> uses<00:29:49.409> but 00:29:49.970 --> 00:29:49.980 align:start position:0% wallet like ledger or meta mask uses but 00:29:49.980 --> 00:29:52.190 align:start position:0% wallet like ledger or meta mask uses but it's<00:29:50.130> just<00:29:50.309> like<00:29:50.490> the<00:29:51.000> respect<00:29:51.690> for<00:29:51.899> making 00:29:52.190 --> 00:29:52.200 align:start position:0% it's just like the respect for making 00:29:52.200 --> 00:29:54.799 align:start position:0% it's just like the respect for making those<00:29:52.380> functions<00:29:52.830> available<00:29:53.010> like<00:29:53.880> is<00:29:54.120> you 00:29:54.799 --> 00:29:54.809 align:start position:0% those functions available like is you 00:29:54.809 --> 00:29:56.779 align:start position:0% those functions available like is you know<00:29:54.960> it's<00:29:55.799> far<00:29:55.890> away<00:29:56.039> it's<00:29:56.370> gonna<00:29:56.460> be<00:29:56.580> a<00:29:56.640> long 00:29:56.779 --> 00:29:56.789 align:start position:0% know it's far away it's gonna be a long 00:29:56.789 --> 00:29:58.279 align:start position:0% know it's far away it's gonna be a long time<00:29:57.029> tell<00:29:57.330> anything<00:29:57.659> like<00:29:57.750> that<00:29:57.779> is<00:29:58.080> so<00:29:58.200> this 00:29:58.279 --> 00:29:58.289 align:start position:0% time tell anything like that is so this 00:29:58.289 --> 00:30:00.649 align:start position:0% time tell anything like that is so this is<00:29:58.440> kind<00:29:58.620> of<00:29:58.649> like<00:29:58.830> a<00:29:58.860> way<00:29:59.730> of<00:29:59.760> working<00:30:00.390> around 00:30:00.649 --> 00:30:00.659 align:start position:0% is kind of like a way of working around 00:30:00.659 --> 00:30:06.049 align:start position:0% is kind of like a way of working around that<00:30:00.840> limitation<00:30:04.520> do<00:30:05.520> you<00:30:05.610> have<00:30:05.730> to<00:30:05.880> assign 00:30:06.049 --> 00:30:06.059 align:start position:0% that limitation do you have to assign 00:30:06.059 --> 00:30:07.789 align:start position:0% that limitation do you have to assign the<00:30:06.270> same<00:30:06.419> message<00:30:06.840> every<00:30:07.110> time<00:30:07.320> to<00:30:07.529> get<00:30:07.679> the 00:30:07.789 --> 00:30:07.799 align:start position:0% the same message every time to get the 00:30:07.799 --> 00:30:12.080 align:start position:0% the same message every time to get the password<00:30:08.279> yeah<00:30:09.090> so<00:30:09.510> basically<00:30:10.200> on<00:30:11.029> kind<00:30:12.029> of 00:30:12.080 --> 00:30:12.090 align:start position:0% password yeah so basically on kind of 00:30:12.090 --> 00:30:13.669 align:start position:0% password yeah so basically on kind of what<00:30:12.419> I<00:30:12.450> was<00:30:12.570> talking<00:30:12.809> about<00:30:12.870> earlier<00:30:12.990> like<00:30:13.500> is 00:30:13.669 --> 00:30:13.679 align:start position:0% what I was talking about earlier like is 00:30:13.679 --> 00:30:15.169 align:start position:0% what I was talking about earlier like is there's<00:30:14.100> a<00:30:14.159> bunch<00:30:14.340> of<00:30:14.460> different<00:30:14.730> types<00:30:15.000> of 00:30:15.169 --> 00:30:15.179 align:start position:0% there's a bunch of different types of 00:30:15.179 --> 00:30:17.149 align:start position:0% there's a bunch of different types of users<00:30:15.419> who<00:30:16.260> want<00:30:16.409> to<00:30:16.529> use<00:30:16.679> an<00:30:16.799> application 00:30:17.149 --> 00:30:17.159 align:start position:0% users who want to use an application 00:30:17.159 --> 00:30:19.430 align:start position:0% users who want to use an application like<00:30:17.399> this<00:30:17.429> some<00:30:18.270> are<00:30:18.299> more<00:30:18.600> hardcore<00:30:18.960> about 00:30:19.430 --> 00:30:19.440 align:start position:0% like this some are more hardcore about 00:30:19.440 --> 00:30:22.220 align:start position:0% like this some are more hardcore about like<00:30:19.890> their<00:30:20.580> privacy<00:30:20.760> and<00:30:21.419> some<00:30:21.630> people<00:30:21.929> want 00:30:22.220 --> 00:30:22.230 align:start position:0% like their privacy and some people want 00:30:22.230 --> 00:30:23.450 align:start position:0% like their privacy and some people want something<00:30:22.559> that's<00:30:22.710> more<00:30:22.770> convenient<00:30:23.429> that 00:30:23.450 --> 00:30:23.460 align:start position:0% something that's more convenient that 00:30:23.460 --> 00:30:24.300 align:start position:0% something that's more convenient that they<00:30:23.640> don't<00:30:23.789> have<00:30:23.880> to<00:30:23.970> think 00:30:24.300 --> 00:30:24.310 align:start position:0% they don't have to think 00:30:24.310 --> 00:30:28.860 align:start position:0% they don't have to think very<00:30:24.490> much<00:30:25.840> so<00:30:26.080> if<00:30:26.530> you<00:30:26.800> want<00:30:27.310> to<00:30:27.750> for<00:30:28.750> those 00:30:28.860 --> 00:30:28.870 align:start position:0% very much so if you want to for those 00:30:28.870 --> 00:30:30.350 align:start position:0% very much so if you want to for those users<00:30:29.110> who<00:30:29.260> want<00:30:29.470> something<00:30:29.650> that's<00:30:29.890> very 00:30:30.350 --> 00:30:30.360 align:start position:0% users who want something that's very 00:30:30.360 --> 00:30:33.300 align:start position:0% users who want something that's very convenient<00:30:31.360> and<00:30:31.620> they're<00:30:32.620> not<00:30:32.770> as<00:30:33.040> like 00:30:33.300 --> 00:30:33.310 align:start position:0% convenient and they're not as like 00:30:33.310 --> 00:30:35.220 align:start position:0% convenient and they're not as like worried<00:30:33.730> about<00:30:33.850> privacy<00:30:34.060> basically<00:30:34.990> you<00:30:35.110> can 00:30:35.220 --> 00:30:35.230 align:start position:0% worried about privacy basically you can 00:30:35.230 --> 00:30:37.800 align:start position:0% worried about privacy basically you can just<00:30:35.260> kind<00:30:35.560> of<00:30:35.650> sign<00:30:36.280> a<00:30:36.310> you<00:30:36.940> know<00:30:37.120> a<00:30:37.360> default 00:30:37.800 --> 00:30:37.810 align:start position:0% just kind of sign a you know a default 00:30:37.810 --> 00:30:39.630 align:start position:0% just kind of sign a you know a default phrase<00:30:38.200> that<00:30:38.500> we<00:30:38.590> choose<00:30:38.770> you<00:30:39.100> know<00:30:39.220> kind<00:30:39.580> of 00:30:39.630 --> 00:30:39.640 align:start position:0% phrase that we choose you know kind of 00:30:39.640 --> 00:30:42.000 align:start position:0% phrase that we choose you know kind of provide<00:30:39.880> to<00:30:40.060> you<00:30:40.120> every<00:30:40.390> time<00:30:40.540> son<00:30:40.960> um<00:30:41.560> so<00:30:41.890> then 00:30:42.000 --> 00:30:42.010 align:start position:0% provide to you every time son um so then 00:30:42.010 --> 00:30:43.140 align:start position:0% provide to you every time son um so then it's<00:30:42.130> kind<00:30:42.340> of<00:30:42.370> like<00:30:42.490> you<00:30:42.730> don't<00:30:42.820> have<00:30:43.030> to 00:30:43.140 --> 00:30:43.150 align:start position:0% it's kind of like you don't have to 00:30:43.150 --> 00:30:44.610 align:start position:0% it's kind of like you don't have to remember<00:30:43.360> the<00:30:43.600> passphrase<00:30:43.780> and<00:30:44.110> you<00:30:44.320> can<00:30:44.440> kind 00:30:44.610 --> 00:30:44.620 align:start position:0% remember the passphrase and you can kind 00:30:44.620 --> 00:30:47.010 align:start position:0% remember the passphrase and you can kind of<00:30:44.650> determine<00:30:44.830> its<00:30:45.220> to<00:30:45.310> be<00:30:45.460> regenerated<00:30:46.030> um<00:30:46.360> if 00:30:47.010 --> 00:30:47.020 align:start position:0% of determine its to be regenerated um if 00:30:47.020 --> 00:30:48.630 align:start position:0% of determine its to be regenerated um if you<00:30:47.140> want<00:30:47.320> another<00:30:47.500> layer<00:30:47.740> of<00:30:47.890> privacy<00:30:48.070> you 00:30:48.630 --> 00:30:48.640 align:start position:0% you want another layer of privacy you 00:30:48.640 --> 00:30:52.080 align:start position:0% you want another layer of privacy you know<00:30:48.760> you<00:30:48.820> can<00:30:49.120> on<00:30:50.670> choose<00:30:51.670> your<00:30:51.820> own<00:30:51.850> that's 00:30:52.080 --> 00:30:52.090 align:start position:0% know you can on choose your own that's 00:30:52.090 --> 00:30:53.490 align:start position:0% know you can on choose your own that's pretty<00:30:52.330> sadistic<00:30:52.630> your<00:30:52.930> teeth<00:30:53.080> and<00:30:53.410> they'll 00:30:53.490 --> 00:30:53.500 align:start position:0% pretty sadistic your teeth and they'll 00:30:53.500 --> 00:30:55.380 align:start position:0% pretty sadistic your teeth and they'll be<00:30:53.590> able<00:30:53.680> snails<00:30:53.950> but<00:30:54.190> then<00:30:54.310> if<00:30:54.400> you<00:30:54.490> lose<00:30:55.240> that 00:30:55.380 --> 00:30:55.390 align:start position:0% be able snails but then if you lose that 00:30:55.390 --> 00:30:57.810 align:start position:0% be able snails but then if you lose that passphrase<00:30:55.990> and<00:30:56.350> you<00:30:56.620> know<00:30:56.740> you<00:30:56.800> lose<00:30:57.460> access 00:30:57.810 --> 00:30:57.820 align:start position:0% passphrase and you know you lose access 00:30:57.820 --> 00:30:59.910 align:start position:0% passphrase and you know you lose access to<00:30:58.000> your<00:30:58.150> messages<00:30:58.450> so<00:30:58.930> but<00:30:59.590> that's<00:30:59.710> available 00:30:59.910 --> 00:30:59.920 align:start position:0% to your messages so but that's available 00:30:59.920 --> 00:31:02.730 align:start position:0% to your messages so but that's available to<00:31:00.250> users<00:31:00.610> who<00:31:00.850> want<00:31:00.940> a<00:31:01.060> better<00:31:01.750> layer<00:31:02.650> of 00:31:02.730 --> 00:31:02.740 align:start position:0% to users who want a better layer of 00:31:02.740 --> 00:31:07.950 align:start position:0% to users who want a better layer of privacy<00:31:02.920> yep<00:31:05.610> think<00:31:06.610> of<00:31:06.760> any<00:31:07.240> practical<00:31:07.480> use 00:31:07.950 --> 00:31:07.960 align:start position:0% privacy yep think of any practical use 00:31:07.960 --> 00:31:16.770 align:start position:0% privacy yep think of any practical use cases<00:31:08.290> to<00:31:08.680> employ<00:31:09.510> uses<00:31:11.640> exactly<00:31:12.640> just<00:31:13.830> um<00:31:15.780> so 00:31:16.770 --> 00:31:16.780 align:start position:0% cases to employ uses exactly just um so 00:31:16.780 --> 00:31:22.190 align:start position:0% cases to employ uses exactly just um so it's<00:31:17.640> one<00:31:18.640> thing<00:31:18.850> that<00:31:20.220> did<00:31:21.220> the<00:31:21.550> initial 00:31:22.190 --> 00:31:22.200 align:start position:0% it's one thing that did the initial 00:31:22.200 --> 00:31:28.560 align:start position:0% it's one thing that did the initial implementation<00:31:23.200> of<00:31:25.800> PGP<00:31:26.800> like<00:31:27.460> functions<00:31:28.180> is 00:31:28.560 --> 00:31:28.570 align:start position:0% implementation of PGP like functions is 00:31:28.570 --> 00:31:31.530 align:start position:0% implementation of PGP like functions is this<00:31:29.200> concept<00:31:29.650> called<00:31:29.800> the<00:31:29.950> web<00:31:30.100> of<00:31:30.280> trust<00:31:30.540> the 00:31:31.530 --> 00:31:31.540 align:start position:0% this concept called the web of trust the 00:31:31.540 --> 00:31:33.840 align:start position:0% this concept called the web of trust the function<00:31:31.870> which<00:31:31.990> is<00:31:32.110> basically<00:31:32.470> like<00:31:32.850> people 00:31:33.840 --> 00:31:33.850 align:start position:0% function which is basically like people 00:31:33.850 --> 00:31:36.150 align:start position:0% function which is basically like people can<00:31:34.030> trust<00:31:34.270> PGP<00:31:34.750> keys<00:31:34.990> if<00:31:35.260> other<00:31:35.620> keys<00:31:35.920> that 00:31:36.150 --> 00:31:36.160 align:start position:0% can trust PGP keys if other keys that 00:31:36.160 --> 00:31:38.040 align:start position:0% can trust PGP keys if other keys that they<00:31:36.280> already<00:31:36.520> trust<00:31:36.820> also<00:31:37.390> trust<00:31:37.630> that<00:31:37.780> those 00:31:38.040 --> 00:31:38.050 align:start position:0% they already trust also trust that those 00:31:38.050 --> 00:31:41.460 align:start position:0% they already trust also trust that those PGP<00:31:38.530> keys<00:31:38.740> so<00:31:39.340> like<00:31:39.550> when<00:31:40.510> the<00:31:40.570> critical<00:31:40.960> was 00:31:41.460 --> 00:31:41.470 align:start position:0% PGP keys so like when the critical was 00:31:41.470 --> 00:31:44.300 align:start position:0% PGP keys so like when the critical was first<00:31:41.710> developed<00:31:41.890> you<00:31:42.340> know<00:31:42.870> like<00:31:43.870> all<00:31:44.200> the 00:31:44.300 --> 00:31:44.310 align:start position:0% first developed you know like all the 00:31:44.310 --> 00:31:46.320 align:start position:0% first developed you know like all the academic<00:31:45.310> nerds<00:31:45.490> would<00:31:45.730> have<00:31:45.850> signing 00:31:46.320 --> 00:31:46.330 align:start position:0% academic nerds would have signing 00:31:46.330 --> 00:31:49.410 align:start position:0% academic nerds would have signing parties<00:31:46.690> and<00:31:46.990> get<00:31:47.770> together<00:31:47.920> and<00:31:48.310> you<00:31:48.910> know 00:31:49.410 --> 00:31:49.420 align:start position:0% parties and get together and you know 00:31:49.420 --> 00:31:51.510 align:start position:0% parties and get together and you know trachy<00:31:50.140> GT<00:31:50.410> keys<00:31:50.590> in<00:31:50.740> person<00:31:51.100> so<00:31:51.250> they<00:31:51.370> could 00:31:51.510 --> 00:31:51.520 align:start position:0% trachy GT keys in person so they could 00:31:51.520 --> 00:31:52.830 align:start position:0% trachy GT keys in person so they could kind<00:31:51.700> of<00:31:51.760> have<00:31:51.880> that<00:31:52.060> base<00:31:52.240> level<00:31:52.480> of<00:31:52.660> trust 00:31:52.830 --> 00:31:52.840 align:start position:0% kind of have that base level of trust 00:31:52.840 --> 00:31:54.240 align:start position:0% kind of have that base level of trust and<00:31:53.080> build<00:31:53.320> this<00:31:53.440> like<00:31:53.650> kind<00:31:53.890> of<00:31:53.950> trusted 00:31:54.240 --> 00:31:54.250 align:start position:0% and build this like kind of trusted 00:31:54.250 --> 00:31:56.190 align:start position:0% and build this like kind of trusted network<00:31:54.550> and<00:31:54.820> then<00:31:54.910> off<00:31:55.390> of<00:31:55.450> that<00:31:55.630> they<00:31:55.960> like 00:31:56.190 --> 00:31:56.200 align:start position:0% network and then off of that they like 00:31:56.200 --> 00:31:57.810 align:start position:0% network and then off of that they like you<00:31:56.410> know<00:31:56.470> builds<00:31:56.860> a<00:31:56.950> larger<00:31:57.220> network<00:31:57.520> and<00:31:57.760> it 00:31:57.810 --> 00:31:57.820 align:start position:0% you know builds a larger network and it 00:31:57.820 --> 00:32:00.240 align:start position:0% you know builds a larger network and it was<00:31:57.910> kind<00:31:58.120> of<00:31:58.180> like<00:31:58.360> if<00:31:59.200> that<00:31:59.410> was<00:31:59.470> how<00:31:59.710> Trust 00:32:00.240 --> 00:32:00.250 align:start position:0% was kind of like if that was how Trust 00:32:00.250 --> 00:32:03.870 align:start position:0% was kind of like if that was how Trust was<00:32:00.520> like<00:32:00.820> built<00:32:01.150> like<00:32:01.570> initially<00:32:02.020> um<00:32:02.880> like 00:32:03.870 --> 00:32:03.880 align:start position:0% was like built like initially um like 00:32:03.880 --> 00:32:06.600 align:start position:0% was like built like initially um like which<00:32:04.720> is<00:32:04.750> kind<00:32:05.050> of<00:32:05.110> actually<00:32:05.560> now<00:32:05.740> a<00:32:06.160> sighted 00:32:06.600 --> 00:32:06.610 align:start position:0% which is kind of actually now a sighted 00:32:06.610 --> 00:32:08.910 align:start position:0% which is kind of actually now a sighted as<00:32:06.670> kind<00:32:06.850> of<00:32:06.880> a<00:32:07.080> it's<00:32:08.080> more<00:32:08.260> of<00:32:08.320> a<00:32:08.410> critique<00:32:08.560> of 00:32:08.910 --> 00:32:08.920 align:start position:0% as kind of a it's more of a critique of 00:32:08.920 --> 00:32:10.350 align:start position:0% as kind of a it's more of a critique of PGP<00:32:09.580> that<00:32:09.790> that's<00:32:09.940> kind<00:32:10.150> of<00:32:10.180> like<00:32:10.330> a 00:32:10.350 --> 00:32:10.360 align:start position:0% PGP that that's kind of like a 00:32:10.360 --> 00:32:14.430 align:start position:0% PGP that that's kind of like a limitation<00:32:11.260> of<00:32:11.320> the<00:32:11.410> protocol<00:32:13.020> key<00:32:14.020> space<00:32:14.230> is 00:32:14.430 --> 00:32:14.440 align:start position:0% limitation of the protocol key space is 00:32:14.440 --> 00:32:16.680 align:start position:0% limitation of the protocol key space is more<00:32:14.730> limited<00:32:15.730> in<00:32:15.790> scope<00:32:16.060> since<00:32:16.420> it's<00:32:16.570> only 00:32:16.680 --> 00:32:16.690 align:start position:0% more limited in scope since it's only 00:32:16.690 --> 00:32:18.690 align:start position:0% more limited in scope since it's only about<00:32:17.050> instead<00:32:17.410> of<00:32:17.470> finding<00:32:18.010> identities<00:32:18.460> to 00:32:18.690 --> 00:32:18.700 align:start position:0% about instead of finding identities to 00:32:18.700 --> 00:32:21.590 align:start position:0% about instead of finding identities to real<00:32:18.880> person<00:32:19.360> you're<00:32:19.930> binding<00:32:20.170> identities<00:32:20.800> to 00:32:21.590 --> 00:32:21.600 align:start position:0% real person you're binding identities to 00:32:21.600 --> 00:32:24.240 align:start position:0% real person you're binding identities to you<00:32:22.600> know<00:32:22.720> an<00:32:23.020> ethereal<00:32:23.350> address<00:32:23.650> basically 00:32:24.240 --> 00:32:24.250 align:start position:0% you know an ethereal address basically 00:32:24.250 --> 00:32:26.250 align:start position:0% you know an ethereal address basically but<00:32:24.880> you<00:32:25.240> don't<00:32:25.420> have<00:32:25.540> to<00:32:25.720> worry<00:32:25.900> about<00:32:26.050> that 00:32:26.250 --> 00:32:26.260 align:start position:0% but you don't have to worry about that 00:32:26.260 --> 00:32:28.200 align:start position:0% but you don't have to worry about that same<00:32:26.500> kind<00:32:26.950> of<00:32:27.010> web<00:32:27.430> of<00:32:27.580> trust<00:32:27.730> which<00:32:28.060> has 00:32:28.200 --> 00:32:28.210 align:start position:0% same kind of web of trust which has 00:32:28.210 --> 00:32:30.480 align:start position:0% same kind of web of trust which has seems<00:32:28.450> kind<00:32:28.660> of<00:32:28.720> scalability<00:32:29.350> issues<00:32:29.620> but<00:32:30.280> I 00:32:30.480 --> 00:32:30.490 align:start position:0% seems kind of scalability issues but I 00:32:30.490 --> 00:32:32.900 align:start position:0% seems kind of scalability issues but I think<00:32:30.520> there<00:32:30.880> are<00:32:31.210> some<00:32:31.560> some<00:32:32.560> interesting 00:32:32.900 --> 00:32:32.910 align:start position:0% think there are some some interesting 00:32:32.910 --> 00:32:36.780 align:start position:0% think there are some some interesting opportunities<00:32:33.910> but<00:32:34.800> with<00:32:35.800> like<00:32:36.040> connecting 00:32:36.780 --> 00:32:36.790 align:start position:0% opportunities but with like connecting 00:32:36.790 --> 00:32:39.090 align:start position:0% opportunities but with like connecting to<00:32:36.850> systems<00:32:37.180> like<00:32:37.330> he's<00:32:37.540> he<00:32:38.320> not<00:32:38.800> keyspace 00:32:39.090 --> 00:32:39.100 align:start position:0% to systems like he's he not keyspace 00:32:39.100 --> 00:32:44.760 align:start position:0% to systems like he's he not keyspace Keita's<00:32:40.030> um<00:32:40.530> where<00:32:41.530> like<00:32:41.800> a<00:32:42.270> identity<00:32:43.270> and<00:32:43.770> a 00:32:44.760 --> 00:32:44.770 align:start position:0% Keita's um where like a identity and a 00:32:44.770 --> 00:32:47.670 align:start position:0% Keita's um where like a identity and a cryptographic<00:32:45.490> key<00:32:45.940> are<00:32:46.150> already<00:32:46.630> bound<00:32:47.230> by 00:32:47.670 --> 00:32:47.680 align:start position:0% cryptographic key are already bound by 00:32:47.680 --> 00:32:50.190 align:start position:0% cryptographic key are already bound by other<00:32:47.920> means<00:32:48.330> so<00:32:49.330> then<00:32:49.480> it<00:32:49.600> kind<00:32:49.870> of<00:32:49.960> like 00:32:50.190 --> 00:32:50.200 align:start position:0% other means so then it kind of like 00:32:50.200 --> 00:32:53.910 align:start position:0% other means so then it kind of like philosophy<00:32:51.130> use<00:32:51.460> PGP<00:32:52.050> more<00:32:53.050> you<00:32:53.470> know<00:32:53.620> more 00:32:53.910 --> 00:32:53.920 align:start position:0% philosophy use PGP more you know more 00:32:53.920 --> 00:32:56.540 align:start position:0% philosophy use PGP more you know more modular<00:32:54.400> you<00:32:54.760> know<00:32:54.850> where<00:32:55.000> you<00:32:55.060> can<00:32:55.180> kind<00:32:55.360> of 00:32:56.540 --> 00:32:56.550 align:start position:0% modular you know where you can kind of 00:32:56.550 --> 00:32:59.790 align:start position:0% modular you know where you can kind of strap<00:32:57.550> it<00:32:57.700> on<00:32:57.820> to<00:32:57.970> other<00:32:58.150> existing<00:32:58.800> networks 00:32:59.790 --> 00:32:59.800 align:start position:0% strap it on to other existing networks 00:32:59.800 --> 00:33:01.950 align:start position:0% strap it on to other existing networks that<00:33:00.010> specifically<00:33:00.970> as<00:33:01.510> long<00:33:01.630> as<00:33:01.780> they<00:33:01.840> have 00:33:01.950 --> 00:33:01.960 align:start position:0% that specifically as long as they have 00:33:01.960 --> 00:33:13.610 align:start position:0% that specifically as long as they have cryptographic<00:33:02.380> capabilities 00:33:13.610 --> 00:33:13.620 align:start position:0% 00:33:13.620 --> 00:33:19.540 align:start position:0% all<00:33:14.620> right<00:33:14.950> all<00:33:15.730> right<00:33:15.790> that's<00:33:16.030> it<00:33:16.230> thank<00:33:17.230> you 00:33:19.540 --> 00:33:19.550 align:start position:0% 00:33:19.550 --> 00:33:26.320 align:start position:0% [Applause]