WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:18.060 align:start position:0% [Music] 00:00:18.060 --> 00:00:18.070 align:start position:0% 00:00:18.070 --> 00:00:19.780 align:start position:0% cool 00:00:19.780 --> 00:00:19.790 align:start position:0% cool 00:00:19.790 --> 00:00:22.000 align:start position:0% cool yeah<00:00:20.180> hi<00:00:20.390> I'm<00:00:20.570> Jared<00:00:21.050> I<00:00:21.260> am<00:00:21.410> the<00:00:21.590> main 00:00:22.000 --> 00:00:22.010 align:start position:0% yeah hi I'm Jared I am the main 00:00:22.010 --> 00:00:24.820 align:start position:0% yeah hi I'm Jared I am the main organizer<00:00:22.430> and<00:00:22.910> thought<00:00:23.300> leader<00:00:23.540> on<00:00:23.930> open 00:00:24.820 --> 00:00:24.830 align:start position:0% organizer and thought leader on open 00:00:24.830 --> 00:00:27.070 align:start position:0% organizer and thought leader on open source<00:00:24.980> mobile<00:00:25.250> therem<00:00:25.760> client<00:00:26.150> called 00:00:27.070 --> 00:00:27.080 align:start position:0% source mobile therem client called 00:00:27.080 --> 00:00:29.680 align:start position:0% source mobile therem client called status<00:00:27.910> show<00:00:28.910> hands<00:00:29.210> who's<00:00:29.330> actually<00:00:29.570> heard 00:00:29.680 --> 00:00:29.690 align:start position:0% status show hands who's actually heard 00:00:29.690 --> 00:00:31.139 align:start position:0% status show hands who's actually heard of<00:00:29.780> us 00:00:31.139 --> 00:00:31.149 align:start position:0% of us 00:00:31.149 --> 00:00:35.140 align:start position:0% of us amazing<00:00:32.180> whoo<00:00:33.250> cool<00:00:34.250> for<00:00:34.730> those<00:00:34.790> who<00:00:34.940> don't 00:00:35.140 --> 00:00:35.150 align:start position:0% amazing whoo cool for those who don't 00:00:35.150 --> 00:00:37.030 align:start position:0% amazing whoo cool for those who don't know<00:00:35.240> status<00:00:36.020> is<00:00:36.170> something<00:00:36.500> like<00:00:36.620> a<00:00:36.680> hybrid 00:00:37.030 --> 00:00:37.040 align:start position:0% know status is something like a hybrid 00:00:37.040 --> 00:00:40.140 align:start position:0% know status is something like a hybrid Instant<00:00:37.550> Messenger<00:00:37.850> and<00:00:38.350> mobile<00:00:39.350> dab<00:00:39.620> browser 00:00:40.140 --> 00:00:40.150 align:start position:0% Instant Messenger and mobile dab browser 00:00:40.150 --> 00:00:42.790 align:start position:0% Instant Messenger and mobile dab browser and<00:00:41.150> really<00:00:41.360> we<00:00:41.480> have<00:00:41.630> one<00:00:41.930> goal<00:00:42.260> and<00:00:42.530> that's 00:00:42.790 --> 00:00:42.800 align:start position:0% and really we have one goal and that's 00:00:42.800 --> 00:00:44.800 align:start position:0% and really we have one goal and that's to<00:00:42.890> take<00:00:43.040> ethereum<00:00:43.489> technologies<00:00:44.060> and<00:00:44.390> put 00:00:44.800 --> 00:00:44.810 align:start position:0% to take ethereum technologies and put 00:00:44.810 --> 00:00:47.590 align:start position:0% to take ethereum technologies and put them<00:00:44.900> in<00:00:44.989> the<00:00:45.079> hands<00:00:45.470> of<00:00:45.560> people<00:00:46.329> what<00:00:47.329> I<00:00:47.360> love 00:00:47.590 --> 00:00:47.600 align:start position:0% them in the hands of people what I love 00:00:47.600 --> 00:00:49.360 align:start position:0% them in the hands of people what I love about<00:00:48.050> the<00:00:48.200> etheric<00:00:48.500> immunity<00:00:48.890> is<00:00:49.070> we've 00:00:49.360 --> 00:00:49.370 align:start position:0% about the etheric immunity is we've 00:00:49.370 --> 00:00:51.580 align:start position:0% about the etheric immunity is we've taken<00:00:49.520> this<00:00:49.790> further<00:00:50.180> for<00:00:50.630> crypto<00:00:51.020> but<00:00:51.230> we've 00:00:51.580 --> 00:00:51.590 align:start position:0% taken this further for crypto but we've 00:00:51.590 --> 00:00:53.860 align:start position:0% taken this further for crypto but we've tempered<00:00:52.040> it<00:00:52.160> with<00:00:52.280> pragmatism<00:00:52.850> and<00:00:53.480> this<00:00:53.780> is 00:00:53.860 --> 00:00:53.870 align:start position:0% tempered it with pragmatism and this is 00:00:53.870 --> 00:00:56.040 align:start position:0% tempered it with pragmatism and this is my<00:00:53.989> book<00:00:54.230> chain<00:00:54.470> technology<00:00:54.680> palatable<00:00:55.579> for 00:00:56.040 --> 00:00:56.050 align:start position:0% my book chain technology palatable for 00:00:56.050 --> 00:00:58.389 align:start position:0% my book chain technology palatable for organizations<00:00:57.050> banks<00:00:57.680> and<00:00:57.920> governments 00:00:58.389 --> 00:00:58.399 align:start position:0% organizations banks and governments 00:00:58.399 --> 00:01:01.030 align:start position:0% organizations banks and governments alike<00:00:58.870> however<00:00:59.870> this<00:01:00.200> pragmatism<00:01:00.680> has<00:01:00.829> been 00:01:01.030 --> 00:01:01.040 align:start position:0% alike however this pragmatism has been 00:01:01.040 --> 00:01:02.979 align:start position:0% alike however this pragmatism has been somewhat<00:01:01.399> of<00:01:01.430> a<00:01:01.610> double-edged<00:01:01.969> sword<00:01:02.000> when<00:01:02.870> it 00:01:02.979 --> 00:01:02.989 align:start position:0% somewhat of a double-edged sword when it 00:01:02.989 --> 00:01:04.509 align:start position:0% somewhat of a double-edged sword when it comes<00:01:03.230> to<00:01:03.410> taking<00:01:03.620> this<00:01:03.800> technology<00:01:04.309> and 00:01:04.509 --> 00:01:04.519 align:start position:0% comes to taking this technology and 00:01:04.519 --> 00:01:06.430 align:start position:0% comes to taking this technology and putting<00:01:04.790> it<00:01:04.879> in<00:01:04.939> the<00:01:05.000> hands<00:01:05.299> of<00:01:05.390> people<00:01:05.630> and 00:01:06.430 --> 00:01:06.440 align:start position:0% putting it in the hands of people and 00:01:06.440 --> 00:01:08.020 align:start position:0% putting it in the hands of people and I'd<00:01:06.830> like<00:01:06.950> to<00:01:07.070> start<00:01:07.250> off<00:01:07.310> with<00:01:07.490> a<00:01:07.520> short<00:01:07.790> story 00:01:08.020 --> 00:01:08.030 align:start position:0% I'd like to start off with a short story 00:01:08.030 --> 00:01:12.280 align:start position:0% I'd like to start off with a short story that<00:01:08.420> I<00:01:08.450> think<00:01:08.690> illustrates<00:01:08.870> this<00:01:09.320> point<00:01:11.290> so 00:01:12.280 --> 00:01:12.290 align:start position:0% that I think illustrates this point so 00:01:12.290 --> 00:01:15.610 align:start position:0% that I think illustrates this point so on<00:01:12.860> October<00:01:13.070> 1st<00:01:13.960> an<00:01:14.960> autonomous<00:01:15.500> community 00:01:15.610 --> 00:01:15.620 align:start position:0% on October 1st an autonomous community 00:01:15.620 --> 00:01:18.370 align:start position:0% on October 1st an autonomous community of<00:01:15.979> Spain<00:01:16.280> Catalonia<00:01:16.790> held<00:01:17.630> a<00:01:17.720> referendum<00:01:17.869> of 00:01:18.370 --> 00:01:18.380 align:start position:0% of Spain Catalonia held a referendum of 00:01:18.380 --> 00:01:20.980 align:start position:0% of Spain Catalonia held a referendum of independence<00:01:19.150> leading<00:01:20.150> up<00:01:20.240> to<00:01:20.270> the<00:01:20.540> event 00:01:20.980 --> 00:01:20.990 align:start position:0% independence leading up to the event 00:01:20.990 --> 00:01:23.740 align:start position:0% independence leading up to the event they<00:01:21.590> used<00:01:21.920> a<00:01:22.310> superb<00:01:22.850> decentralized<00:01:23.510> file 00:01:23.740 --> 00:01:23.750 align:start position:0% they used a superb decentralized file 00:01:23.750 --> 00:01:26.830 align:start position:0% they used a superb decentralized file storage<00:01:24.110> technology<00:01:24.619> called<00:01:25.130> ipfs<00:01:25.840> to 00:01:26.830 --> 00:01:26.840 align:start position:0% storage technology called ipfs to 00:01:26.840 --> 00:01:28.260 align:start position:0% storage technology called ipfs to organize<00:01:27.320> their<00:01:27.619> votes 00:01:28.260 --> 00:01:28.270 align:start position:0% organize their votes 00:01:28.270 --> 00:01:30.940 align:start position:0% organize their votes however<00:01:29.270> non-technical<00:01:29.990> people<00:01:30.200> were<00:01:30.740> using 00:01:30.940 --> 00:01:30.950 align:start position:0% however non-technical people were using 00:01:30.950 --> 00:01:34.120 align:start position:0% however non-technical people were using a<00:01:31.220> centralized<00:01:31.880> HTTP<00:01:32.360> proxy<00:01:32.720> and<00:01:33.439> access<00:01:33.890> this 00:01:34.120 --> 00:01:34.130 align:start position:0% a centralized HTTP proxy and access this 00:01:34.130 --> 00:01:36.340 align:start position:0% a centralized HTTP proxy and access this information<00:01:34.630> through<00:01:35.630> the<00:01:35.810> comfort<00:01:36.140> of<00:01:36.229> their 00:01:36.340 --> 00:01:36.350 align:start position:0% information through the comfort of their 00:01:36.350 --> 00:01:41.109 align:start position:0% information through the comfort of their own<00:01:36.409> browsers<00:01:39.100> leading<00:01:40.100> up<00:01:40.189> to<00:01:40.220> the<00:01:40.369> events<00:01:40.670> on 00:01:41.109 --> 00:01:41.119 align:start position:0% own browsers leading up to the events on 00:01:41.119 --> 00:01:43.780 align:start position:0% own browsers leading up to the events on the<00:01:41.360> September<00:01:41.570> 26<00:01:42.229> I<00:01:42.320> believe<00:01:42.530> it<00:01:42.650> was<00:01:42.790> Spain 00:01:43.780 --> 00:01:43.790 align:start position:0% the September 26 I believe it was Spain 00:01:43.790 --> 00:01:47.289 align:start position:0% the September 26 I believe it was Spain issued<00:01:44.330> blockade<00:01:45.110> of<00:01:45.140> 140<00:01:46.009> domains<00:01:46.369> one<00:01:47.119> of 00:01:47.289 --> 00:01:47.299 align:start position:0% issued blockade of 140 domains one of 00:01:47.299 --> 00:01:51.300 align:start position:0% issued blockade of 140 domains one of which<00:01:47.540> was<00:01:48.049> this<00:01:48.409> gateway<00:01:49.570> politics<00:01:50.570> aside 00:01:51.300 --> 00:01:51.310 align:start position:0% which was this gateway politics aside 00:01:51.310 --> 00:01:55.710 align:start position:0% which was this gateway politics aside disrupting<00:01:52.310> a<00:01:52.520> vote<00:01:53.060> shouldn't<00:01:54.020> be<00:01:54.110> that<00:01:54.290> easy 00:01:55.710 --> 00:01:55.720 align:start position:0% disrupting a vote shouldn't be that easy 00:01:55.720 --> 00:01:59.230 align:start position:0% disrupting a vote shouldn't be that easy at<00:01:56.720> the<00:01:57.409> same<00:01:57.619> time<00:01:57.920> the<00:01:58.310> Tor<00:01:58.579> project<00:01:58.610> saw<00:01:59.210> a 00:01:59.230 --> 00:01:59.240 align:start position:0% at the same time the Tor project saw a 00:01:59.240 --> 00:02:00.580 align:start position:0% at the same time the Tor project saw a surge<00:01:59.600> in<00:01:59.780> the<00:01:59.869> downloads<00:02:00.320> of<00:02:00.470> their 00:02:00.580 --> 00:02:00.590 align:start position:0% surge in the downloads of their 00:02:00.590 --> 00:02:03.999 align:start position:0% surge in the downloads of their messenger<00:02:01.130> this<00:02:01.939> is<00:02:02.150> the<00:02:02.299> Catalans<00:02:03.009> hardening 00:02:03.999 --> 00:02:04.009 align:start position:0% messenger this is the Catalans hardening 00:02:04.009 --> 00:02:06.520 align:start position:0% messenger this is the Catalans hardening their<00:02:04.220> communications<00:02:04.939> and<00:02:05.329> one<00:02:06.229> of<00:02:06.320> the<00:02:06.380> many 00:02:06.520 --> 00:02:06.530 align:start position:0% their communications and one of the many 00:02:06.530 --> 00:02:07.539 align:start position:0% their communications and one of the many things<00:02:06.710> we<00:02:06.860> can<00:02:07.009> applaud<00:02:07.250> the<00:02:07.369> Tor<00:02:07.520> project 00:02:07.539 --> 00:02:07.549 align:start position:0% things we can applaud the Tor project 00:02:07.549 --> 00:02:09.790 align:start position:0% things we can applaud the Tor project for<00:02:08.119> is<00:02:08.299> that<00:02:08.629> they<00:02:08.720> understand<00:02:09.379> their<00:02:09.649> need 00:02:09.790 --> 00:02:09.800 align:start position:0% for is that they understand their need 00:02:09.800 --> 00:02:11.650 align:start position:0% for is that they understand their need to<00:02:09.920> package<00:02:10.160> and<00:02:10.550> make<00:02:10.789> their<00:02:11.000> sophisticated 00:02:11.650 --> 00:02:11.660 align:start position:0% to package and make their sophisticated 00:02:11.660 --> 00:02:14.050 align:start position:0% to package and make their sophisticated software<00:02:11.900> easy<00:02:12.680> for<00:02:13.280> the<00:02:13.340> average<00:02:13.489> user<00:02:13.819> to 00:02:14.050 --> 00:02:14.060 align:start position:0% software easy for the average user to 00:02:14.060 --> 00:02:15.790 align:start position:0% software easy for the average user to use<00:02:14.270> without<00:02:14.870> compromise 00:02:15.790 --> 00:02:15.800 align:start position:0% use without compromise 00:02:15.800 --> 00:02:17.350 align:start position:0% use without compromise on<00:02:16.070> the<00:02:16.160> integrity<00:02:16.490> of<00:02:16.730> that<00:02:16.820> software 00:02:17.350 --> 00:02:17.360 align:start position:0% on the integrity of that software 00:02:17.360 --> 00:02:19.290 align:start position:0% on the integrity of that software because<00:02:18.140> when<00:02:18.290> push<00:02:18.530> comes<00:02:18.800> to<00:02:18.860> shove 00:02:19.290 --> 00:02:19.300 align:start position:0% because when push comes to shove 00:02:19.300 --> 00:02:24.400 align:start position:0% because when push comes to shove decentralization<00:02:20.300> matters<00:02:21.550> and<00:02:22.900> so<00:02:23.900> how<00:02:24.380> we 00:02:24.400 --> 00:02:24.410 align:start position:0% decentralization matters and so how we 00:02:24.410 --> 00:02:26.290 align:start position:0% decentralization matters and so how we package<00:02:24.770> disseminate<00:02:25.730> and<00:02:25.880> present<00:02:26.210> these 00:02:26.290 --> 00:02:26.300 align:start position:0% package disseminate and present these 00:02:26.300 --> 00:02:28.600 align:start position:0% package disseminate and present these technologies<00:02:26.900> to<00:02:27.080> the<00:02:27.110> end-user<00:02:27.610> enables 00:02:28.600 --> 00:02:28.610 align:start position:0% technologies to the end-user enables 00:02:28.610 --> 00:02:30.250 align:start position:0% technologies to the end-user enables them<00:02:28.820> in<00:02:29.090> ways<00:02:29.300> that<00:02:29.570> we<00:02:29.630> haven't<00:02:29.990> been<00:02:30.080> able 00:02:30.250 --> 00:02:30.260 align:start position:0% them in ways that we haven't been able 00:02:30.260 --> 00:02:32.830 align:start position:0% them in ways that we haven't been able to<00:02:30.440> do<00:02:30.620> before<00:02:30.800> and<00:02:31.220> this<00:02:32.210> is<00:02:32.270> really<00:02:32.540> the<00:02:32.690> core 00:02:32.830 --> 00:02:32.840 align:start position:0% to do before and this is really the core 00:02:32.840 --> 00:02:37.020 align:start position:0% to do before and this is really the core problem<00:02:33.320> that<00:02:33.770> we<00:02:33.860> aim<00:02:34.040> to<00:02:34.070> solve<00:02:34.460> at<00:02:34.790> status 00:02:37.020 --> 00:02:37.030 align:start position:0% problem that we aim to solve at status 00:02:37.030 --> 00:02:40.870 align:start position:0% problem that we aim to solve at status so<00:02:38.030> since<00:02:39.020> our<00:02:39.170> last<00:02:39.410> DEFCON<00:02:39.950> we<00:02:40.460> spent<00:02:40.700> a<00:02:40.730> lot 00:02:40.870 --> 00:02:40.880 align:start position:0% so since our last DEFCON we spent a lot 00:02:40.880 --> 00:02:42.730 align:start position:0% so since our last DEFCON we spent a lot of<00:02:40.910> time<00:02:41.180> thinking<00:02:41.660> about<00:02:41.780> the<00:02:42.140> overall<00:02:42.530> user 00:02:42.730 --> 00:02:42.740 align:start position:0% of time thinking about the overall user 00:02:42.740 --> 00:02:45.280 align:start position:0% of time thinking about the overall user experience<00:02:43.370> and<00:02:43.610> design<00:02:44.450> of<00:02:44.480> the<00:02:44.840> perfect 00:02:45.280 --> 00:02:45.290 align:start position:0% experience and design of the perfect 00:02:45.290 --> 00:02:47.740 align:start position:0% experience and design of the perfect ethereum<00:02:45.680> client<00:02:46.130> and<00:02:46.310> nothing<00:02:47.180> matters<00:02:47.480> more 00:02:47.740 --> 00:02:47.750 align:start position:0% ethereum client and nothing matters more 00:02:47.750 --> 00:02:50.230 align:start position:0% ethereum client and nothing matters more than<00:02:47.960> that<00:02:48.320> first<00:02:48.530> run<00:02:49.000> together<00:02:50.000> with<00:02:50.150> our 00:02:50.230 --> 00:02:50.240 align:start position:0% than that first run together with our 00:02:50.240 --> 00:02:52.570 align:start position:0% than that first run together with our community<00:02:50.660> we've<00:02:51.050> decel<00:02:51.500> discovered<00:02:52.130> what<00:02:52.400> we 00:02:52.570 --> 00:02:52.580 align:start position:0% community we've decel discovered what we 00:02:52.580 --> 00:02:55.060 align:start position:0% community we've decel discovered what we think<00:02:52.880> is<00:02:53.120> the<00:02:53.510> typical<00:02:54.050> emotional<00:02:54.590> narrative 00:02:55.060 --> 00:02:55.070 align:start position:0% think is the typical emotional narrative 00:02:55.070 --> 00:02:57.370 align:start position:0% think is the typical emotional narrative that's<00:02:55.730> a<00:02:55.910> new<00:02:56.270> person<00:02:56.660> coming<00:02:56.990> into<00:02:57.200> the 00:02:57.370 --> 00:02:57.380 align:start position:0% that's a new person coming into the 00:02:57.380 --> 00:03:00.130 align:start position:0% that's a new person coming into the crypto<00:02:57.740> world<00:02:57.920> is<00:02:58.220> likely<00:02:58.760> to<00:02:59.000> experience<00:02:59.390> and 00:03:00.130 --> 00:03:00.140 align:start position:0% crypto world is likely to experience and 00:03:00.140 --> 00:03:02.080 align:start position:0% crypto world is likely to experience and on<00:03:00.620> that<00:03:00.740> first<00:03:00.980> run<00:03:01.100> we<00:03:01.670> want<00:03:01.850> to<00:03:01.940> make<00:03:02.060> sure 00:03:02.080 --> 00:03:02.090 align:start position:0% on that first run we want to make sure 00:03:02.090 --> 00:03:04.600 align:start position:0% on that first run we want to make sure they<00:03:02.390> feel<00:03:02.540> safe<00:03:02.930> in<00:03:03.260> control<00:03:03.950> not 00:03:04.600 --> 00:03:04.610 align:start position:0% they feel safe in control not 00:03:04.610 --> 00:03:06.390 align:start position:0% they feel safe in control not overwhelmed<00:03:05.300> while<00:03:05.840> at<00:03:05.960> the<00:03:06.050> same<00:03:06.080> time 00:03:06.390 --> 00:03:06.400 align:start position:0% overwhelmed while at the same time 00:03:06.400 --> 00:03:08.440 align:start position:0% overwhelmed while at the same time connecting<00:03:07.400> them<00:03:07.520> with<00:03:07.550> their<00:03:07.760> goals<00:03:08.060> and 00:03:08.440 --> 00:03:08.450 align:start position:0% connecting them with their goals and 00:03:08.450 --> 00:03:10.660 align:start position:0% connecting them with their goals and allowing<00:03:09.290> them<00:03:09.440> to<00:03:09.560> explore<00:03:09.950> therom<00:03:10.370> how<00:03:10.520> they 00:03:10.660 --> 00:03:10.670 align:start position:0% allowing them to explore therom how they 00:03:10.670 --> 00:03:15.370 align:start position:0% allowing them to explore therom how they wish<00:03:13.270> what<00:03:14.270> at<00:03:14.390> the<00:03:14.450> same<00:03:14.630> while<00:03:15.020> at<00:03:15.140> the<00:03:15.200> same 00:03:15.370 --> 00:03:15.380 align:start position:0% wish what at the same while at the same 00:03:15.380 --> 00:03:19.600 align:start position:0% wish what at the same while at the same time<00:03:17.050> we<00:03:18.050> don't<00:03:18.260> want<00:03:18.500> to<00:03:18.620> overwhelm<00:03:19.160> them<00:03:19.460> or 00:03:19.600 --> 00:03:19.610 align:start position:0% time we don't want to overwhelm them or 00:03:19.610 --> 00:03:21.910 align:start position:0% time we don't want to overwhelm them or demand<00:03:19.970> information<00:03:20.570> from<00:03:20.780> them<00:03:21.050> unless<00:03:21.230> it's 00:03:21.910 --> 00:03:21.920 align:start position:0% demand information from them unless it's 00:03:21.920 --> 00:03:25.690 align:start position:0% demand information from them unless it's absolutely<00:03:22.100> necessary<00:03:22.820> for<00:03:23.590> example<00:03:24.700> we 00:03:25.690 --> 00:03:25.700 align:start position:0% absolutely necessary for example we 00:03:25.700 --> 00:03:27.220 align:start position:0% absolutely necessary for example we don't<00:03:25.910> need<00:03:26.060> them<00:03:26.270> to<00:03:26.480> backup<00:03:26.690> their<00:03:26.990> key 00:03:27.220 --> 00:03:27.230 align:start position:0% don't need them to backup their key 00:03:27.230 --> 00:03:29.260 align:start position:0% don't need them to backup their key phrase<00:03:27.500> until<00:03:28.310> they<00:03:28.400> actually<00:03:28.520> have<00:03:29.030> real 00:03:29.260 --> 00:03:29.270 align:start position:0% phrase until they actually have real 00:03:29.270 --> 00:03:32.500 align:start position:0% phrase until they actually have real value<00:03:29.540> in<00:03:29.959> their<00:03:30.200> in<00:03:30.500> their<00:03:30.709> accounts<00:03:31.390> and<00:03:32.390> at 00:03:32.500 --> 00:03:32.510 align:start position:0% value in their in their accounts and at 00:03:32.510 --> 00:03:34.630 align:start position:0% value in their in their accounts and at which<00:03:32.630> point<00:03:32.930> it<00:03:33.290> backing<00:03:34.190> up<00:03:34.310> their<00:03:34.459> key 00:03:34.630 --> 00:03:34.640 align:start position:0% which point it backing up their key 00:03:34.640 --> 00:03:36.520 align:start position:0% which point it backing up their key phrase<00:03:34.880> does<00:03:35.180> become<00:03:35.510> completely<00:03:35.900> vital<00:03:36.320> and 00:03:36.520 --> 00:03:36.530 align:start position:0% phrase does become completely vital and 00:03:36.530 --> 00:03:38.380 align:start position:0% phrase does become completely vital and they<00:03:36.950> have<00:03:37.100> a<00:03:37.130> reason<00:03:37.610> to<00:03:37.640> do<00:03:37.880> so<00:03:38.150> and<00:03:38.330> so 00:03:38.380 --> 00:03:38.390 align:start position:0% they have a reason to do so and so 00:03:38.390 --> 00:03:42.850 align:start position:0% they have a reason to do so and so that's<00:03:39.020> when<00:03:39.170> we<00:03:39.260> educate<00:03:39.410> them<00:03:41.680> we're<00:03:42.680> also 00:03:42.850 --> 00:03:42.860 align:start position:0% that's when we educate them we're also 00:03:42.860 --> 00:03:45.850 align:start position:0% that's when we educate them we're also introducing<00:03:43.490> an<00:03:43.640> omni<00:03:44.000> bar<00:03:44.530> into<00:03:45.530> status 00:03:45.850 --> 00:03:45.860 align:start position:0% introducing an omni bar into status 00:03:45.860 --> 00:03:48.010 align:start position:0% introducing an omni bar into status which<00:03:46.430> means<00:03:46.700> that<00:03:46.910> you<00:03:47.000> can<00:03:47.150> access<00:03:47.390> anything 00:03:48.010 --> 00:03:48.020 align:start position:0% which means that you can access anything 00:03:48.020 --> 00:03:49.660 align:start position:0% which means that you can access anything you<00:03:48.110> want<00:03:48.260> to<00:03:48.350> do<00:03:48.500> with<00:03:48.650> an<00:03:48.740> aetherium<00:03:49.160> within 00:03:49.660 --> 00:03:49.670 align:start position:0% you want to do with an aetherium within 00:03:49.670 --> 00:03:51.640 align:start position:0% you want to do with an aetherium within just<00:03:49.940> a<00:03:50.030> few<00:03:50.209> taps<00:03:50.450> whether<00:03:51.050> that's<00:03:51.260> accessing 00:03:51.640 --> 00:03:51.650 align:start position:0% just a few taps whether that's accessing 00:03:51.650 --> 00:03:54.340 align:start position:0% just a few taps whether that's accessing taps<00:03:52.040> finding<00:03:52.820> your<00:03:52.940> friends<00:03:53.170> opening<00:03:54.170> new 00:03:54.340 --> 00:03:54.350 align:start position:0% taps finding your friends opening new 00:03:54.350 --> 00:03:59.650 align:start position:0% taps finding your friends opening new tabs<00:03:54.680> or<00:03:54.950> signing<00:03:55.340> a<00:03:55.400> transaction<00:03:58.480> we've<00:03:59.480> also 00:03:59.650 --> 00:03:59.660 align:start position:0% tabs or signing a transaction we've also 00:03:59.660 --> 00:04:01.090 align:start position:0% tabs or signing a transaction we've also worked<00:03:59.959> together<00:04:00.140> with<00:04:00.380> our<00:04:00.470> community<00:04:00.920> to 00:04:01.090 --> 00:04:01.100 align:start position:0% worked together with our community to 00:04:01.100 --> 00:04:02.590 align:start position:0% worked together with our community to develop<00:04:01.610> what<00:04:01.760> I<00:04:01.790> think<00:04:02.090> is<00:04:02.180> one<00:04:02.330> of<00:04:02.360> the<00:04:02.420> most 00:04:02.590 --> 00:04:02.600 align:start position:0% develop what I think is one of the most 00:04:02.600 --> 00:04:04.750 align:start position:0% develop what I think is one of the most visually<00:04:03.080> stunning<00:04:03.350> and<00:04:03.620> intuitive<00:04:04.459> wallet 00:04:04.750 --> 00:04:04.760 align:start position:0% visually stunning and intuitive wallet 00:04:04.760 --> 00:04:06.970 align:start position:0% visually stunning and intuitive wallet experiences<00:04:05.480> that<00:04:06.200> frames<00:04:06.500> your<00:04:06.620> digital 00:04:06.970 --> 00:04:06.980 align:start position:0% experiences that frames your digital 00:04:06.980 --> 00:04:11.890 align:start position:0% experiences that frames your digital assets<00:04:07.330> perfectly<00:04:10.330> we've<00:04:11.330> also<00:04:11.660> wanted<00:04:11.870> to 00:04:11.890 --> 00:04:11.900 align:start position:0% assets perfectly we've also wanted to 00:04:11.900 --> 00:04:14.500 align:start position:0% assets perfectly we've also wanted to make<00:04:12.050> assigning<00:04:12.739> transactions<00:04:13.430> as<00:04:13.760> less 00:04:14.500 --> 00:04:14.510 align:start position:0% make assigning transactions as less 00:04:14.510 --> 00:04:16.570 align:start position:0% make assigning transactions as less intimidating<00:04:15.260> as<00:04:15.350> possible<00:04:15.830> while<00:04:16.370> at<00:04:16.400> the 00:04:16.570 --> 00:04:16.580 align:start position:0% intimidating as possible while at the 00:04:16.580 --> 00:04:18.699 align:start position:0% intimidating as possible while at the same<00:04:16.609> time<00:04:17.109> bolstering<00:04:18.109> a<00:04:18.260> protection 00:04:18.699 --> 00:04:18.709 align:start position:0% same time bolstering a protection 00:04:18.709 --> 00:04:20.740 align:start position:0% same time bolstering a protection against<00:04:18.980> phishing<00:04:19.130> attacks<00:04:19.580> with<00:04:20.239> a<00:04:20.270> signing 00:04:20.740 --> 00:04:20.750 align:start position:0% against phishing attacks with a signing 00:04:20.750 --> 00:04:27.460 align:start position:0% against phishing attacks with a signing phrase<00:04:21.049> of<00:04:21.350> three<00:04:21.770> words<00:04:25.630> why<00:04:26.630> will<00:04:26.870> building 00:04:27.460 --> 00:04:27.470 align:start position:0% phrase of three words why will building 00:04:27.470 --> 00:04:29.620 align:start position:0% phrase of three words why will building out<00:04:27.620> that<00:04:27.650> that<00:04:28.490> signing<00:04:28.880> phrase<00:04:29.090> we 00:04:29.620 --> 00:04:29.630 align:start position:0% out that that signing phrase we 00:04:29.630 --> 00:04:31.240 align:start position:0% out that that signing phrase we actually<00:04:29.990> found<00:04:30.260> out<00:04:30.500> that<00:04:30.800> many<00:04:31.010> of<00:04:31.130> our 00:04:31.240 --> 00:04:31.250 align:start position:0% actually found out that many of our 00:04:31.250 --> 00:04:33.610 align:start position:0% actually found out that many of our users<00:04:31.520> want<00:04:32.150> to<00:04:32.210> store<00:04:32.480> sums<00:04:32.780> of<00:04:32.990> value<00:04:33.380> and 00:04:33.610 --> 00:04:33.620 align:start position:0% users want to store sums of value and 00:04:33.620 --> 00:04:35.500 align:start position:0% users want to store sums of value and control<00:04:34.310> them<00:04:34.520> from<00:04:34.760> their<00:04:34.910> mobile<00:04:35.090> phones 00:04:35.500 --> 00:04:35.510 align:start position:0% control them from their mobile phones 00:04:35.510 --> 00:04:37.660 align:start position:0% control them from their mobile phones which<00:04:36.080> are<00:04:36.230> much<00:04:36.440> larger<00:04:36.740> than<00:04:37.400> what<00:04:37.520> I<00:04:37.550> would 00:04:37.660 --> 00:04:37.670 align:start position:0% which are much larger than what I would 00:04:37.670 --> 00:04:40.150 align:start position:0% which are much larger than what I would fit<00:04:37.910> in<00:04:37.940> their<00:04:38.270> normal<00:04:38.630> analog<00:04:39.080> wallets<00:04:39.440> and 00:04:40.150 --> 00:04:40.160 align:start position:0% fit in their normal analog wallets and 00:04:40.160 --> 00:04:41.860 align:start position:0% fit in their normal analog wallets and we<00:04:40.250> realized<00:04:40.700> that<00:04:40.850> the<00:04:40.970> software<00:04:41.390> key<00:04:41.600> pair 00:04:41.860 --> 00:04:41.870 align:start position:0% we realized that the software key pair 00:04:41.870 --> 00:04:44.380 align:start position:0% we realized that the software key pair it's<00:04:42.290> just<00:04:42.530> not<00:04:42.650> going<00:04:42.800> to<00:04:42.860> cut<00:04:43.040> it<00:04:43.070> so<00:04:43.390> today 00:04:44.380 --> 00:04:44.390 align:start position:0% it's just not going to cut it so today 00:04:44.390 --> 00:04:46.270 align:start position:0% it's just not going to cut it so today I'd<00:04:44.510> like<00:04:44.570> to<00:04:44.690> introduce<00:04:44.810> you<00:04:45.350> to<00:04:45.830> a<00:04:45.860> new 00:04:46.270 --> 00:04:46.280 align:start position:0% I'd like to introduce you to a new 00:04:46.280 --> 00:04:47.980 align:start position:0% I'd like to introduce you to a new initiative<00:04:46.700> which<00:04:47.030> is<00:04:47.150> the<00:04:47.240> status<00:04:47.570> hardware 00:04:47.980 --> 00:04:47.990 align:start position:0% initiative which is the status hardware 00:04:47.990 --> 00:04:50.110 align:start position:0% initiative which is the status hardware wallets<00:04:48.380> this<00:04:48.890> is<00:04:49.040> an<00:04:49.160> open<00:04:49.460> source<00:04:49.670> of<00:04:49.910> Java 00:04:50.110 --> 00:04:50.120 align:start position:0% wallets this is an open source of Java 00:04:50.120 --> 00:04:52.150 align:start position:0% wallets this is an open source of Java card<00:04:50.450> that<00:04:50.990> allows<00:04:51.200> you<00:04:51.350> to<00:04:51.380> take<00:04:51.590> the<00:04:51.650> trust 00:04:52.150 --> 00:04:52.160 align:start position:0% card that allows you to take the trust 00:04:52.160 --> 00:04:54.580 align:start position:0% card that allows you to take the trust safety<00:04:52.880> and<00:04:53.060> security<00:04:53.510> of<00:04:53.840> a<00:04:53.930> hardware<00:04:54.230> wallet 00:04:54.580 --> 00:04:54.590 align:start position:0% safety and security of a hardware wallet 00:04:54.590 --> 00:04:58.150 align:start position:0% safety and security of a hardware wallet but<00:04:54.980> use<00:04:55.220> it<00:04:55.400> on<00:04:55.550> the<00:04:55.730> go<00:04:56.440> it<00:04:57.440> has<00:04:57.590> two<00:04:57.830> modes<00:04:57.980> of 00:04:58.150 --> 00:04:58.160 align:start position:0% but use it on the go it has two modes of 00:04:58.160 --> 00:05:00.430 align:start position:0% but use it on the go it has two modes of operation<00:04:58.280> the<00:04:59.240> first<00:04:59.510> of<00:04:59.690> which<00:04:59.900> you<00:05:00.230> can 00:05:00.430 --> 00:05:00.440 align:start position:0% operation the first of which you can 00:05:00.440 --> 00:05:02.500 align:start position:0% operation the first of which you can sign<00:05:00.680> transactions<00:05:01.490> directly<00:05:01.880> on<00:05:02.000> the<00:05:02.120> on<00:05:02.330> the 00:05:02.500 --> 00:05:02.510 align:start position:0% sign transactions directly on the on the 00:05:02.510 --> 00:05:05.290 align:start position:0% sign transactions directly on the on the card<00:05:02.720> of<00:05:02.930> arbitrary<00:05:03.710> sizes<00:05:04.220> however<00:05:05.150> this 00:05:05.290 --> 00:05:05.300 align:start position:0% card of arbitrary sizes however this 00:05:05.300 --> 00:05:06.880 align:start position:0% card of arbitrary sizes however this requires<00:05:05.690> the<00:05:05.810> vendor<00:05:06.050> specific<00:05:06.470> hardware 00:05:06.880 --> 00:05:06.890 align:start position:0% requires the vendor specific hardware 00:05:06.890 --> 00:05:09.930 align:start position:0% requires the vendor specific hardware namely<00:05:07.820> to<00:05:07.880> support<00:05:08.360> catch<00:05:08.630> act<00:05:08.870> 256<00:05:09.440> and 00:05:09.930 --> 00:05:09.940 align:start position:0% namely to support catch act 256 and 00:05:09.940 --> 00:05:13.660 align:start position:0% namely to support catch act 256 and proper<00:05:10.940> EC<00:05:11.240> point<00:05:11.510> multiplication<00:05:12.310> it<00:05:13.310> is<00:05:13.490> in 00:05:13.660 --> 00:05:13.670 align:start position:0% proper EC point multiplication it is in 00:05:13.670 --> 00:05:16.090 align:start position:0% proper EC point multiplication it is in the<00:05:13.760> 305<00:05:14.090> spec<00:05:14.690> but<00:05:15.200> finding<00:05:15.590> a<00:05:15.680> vendor<00:05:15.980> that 00:05:16.090 --> 00:05:16.100 align:start position:0% the 305 spec but finding a vendor that 00:05:16.100 --> 00:05:18.760 align:start position:0% the 305 spec but finding a vendor that properly<00:05:16.340> supports<00:05:16.790> it<00:05:16.940> is<00:05:17.060> somewhat<00:05:17.770> an 00:05:18.760 --> 00:05:18.770 align:start position:0% properly supports it is somewhat an 00:05:18.770 --> 00:05:21.700 align:start position:0% properly supports it is somewhat an interesting<00:05:19.190> problem<00:05:19.550> and<00:05:20.140> also<00:05:21.140> to<00:05:21.320> support 00:05:21.700 --> 00:05:21.710 align:start position:0% interesting problem and also to support 00:05:21.710 --> 00:05:23.860 align:start position:0% interesting problem and also to support Bluetooth<00:05:22.400> as<00:05:22.910> another<00:05:23.180> communications 00:05:23.860 --> 00:05:23.870 align:start position:0% Bluetooth as another communications 00:05:23.870 --> 00:05:28.420 align:start position:0% Bluetooth as another communications protocol<00:05:24.350> aside<00:05:24.920> from<00:05:24.950> NFC<00:05:25.550> and<00:05:25.820> contact<00:05:27.430> the 00:05:28.420 --> 00:05:28.430 align:start position:0% protocol aside from NFC and contact the 00:05:28.430 --> 00:05:30.280 align:start position:0% protocol aside from NFC and contact the second<00:05:28.790> mode<00:05:29.480> of<00:05:29.600> operation<00:05:30.020> of<00:05:30.140> which 00:05:30.280 --> 00:05:30.290 align:start position:0% second mode of operation of which 00:05:30.290 --> 00:05:33.060 align:start position:0% second mode of operation of which science<00:05:30.980> transactions<00:05:31.610> generated<00:05:32.060> off<00:05:32.240> card 00:05:33.060 --> 00:05:33.070 align:start position:0% science transactions generated off card 00:05:33.070 --> 00:05:36.940 align:start position:0% science transactions generated off card ultra<00:05:34.070> all<00:05:34.310> signing<00:05:35.090> is<00:05:35.330> pin<00:05:35.630> bound<00:05:35.950> however 00:05:36.940 --> 00:05:36.950 align:start position:0% ultra all signing is pin bound however 00:05:36.950 --> 00:05:40.410 align:start position:0% ultra all signing is pin bound however we<00:05:37.880> do<00:05:38.150> support<00:05:38.570> key<00:05:38.780> pairs<00:05:39.050> and<00:05:39.320> HD<00:05:40.010> wallets 00:05:40.410 --> 00:05:40.420 align:start position:0% we do support key pairs and HD wallets 00:05:40.420 --> 00:05:42.760 align:start position:0% we do support key pairs and HD wallets with<00:05:41.420> the<00:05:41.510> HD<00:05:41.810> wallets<00:05:42.080> having<00:05:42.320> two<00:05:42.470> extra 00:05:42.760 --> 00:05:42.770 align:start position:0% with the HD wallets having two extra 00:05:42.770 --> 00:05:45.730 align:start position:0% with the HD wallets having two extra features<00:05:43.160> the<00:05:43.970> first<00:05:44.180> of<00:05:44.390> which<00:05:44.570> is<00:05:44.840> to<00:05:45.260> a 00:05:45.730 --> 00:05:45.740 align:start position:0% features the first of which is to a 00:05:45.740 --> 00:05:48.220 align:start position:0% features the first of which is to a store<00:05:46.670> and<00:05:46.700> export<00:05:47.300> your<00:05:47.330> whisper<00:05:47.720> identity 00:05:48.220 --> 00:05:48.230 align:start position:0% store and export your whisper identity 00:05:48.230 --> 00:05:50.650 align:start position:0% store and export your whisper identity and<00:05:48.440> the<00:05:49.310> second<00:05:49.610> of<00:05:49.700> which<00:05:49.850> is<00:05:50.090> to<00:05:50.540> actually 00:05:50.650 --> 00:05:50.660 align:start position:0% and the second of which is to actually 00:05:50.660 --> 00:05:54.340 align:start position:0% and the second of which is to actually make<00:05:51.020> one<00:05:51.290> derivation<00:05:51.650> path<00:05:52.240> pinless<00:05:53.350> and 00:05:54.340 --> 00:05:54.350 align:start position:0% make one derivation path pinless and 00:05:54.350 --> 00:05:56.470 align:start position:0% make one derivation path pinless and therefore<00:05:55.310> this<00:05:55.460> account<00:05:55.790> becomes<00:05:55.940> balance 00:05:56.470 --> 00:05:56.480 align:start position:0% therefore this account becomes balance 00:05:56.480 --> 00:05:58.060 align:start position:0% therefore this account becomes balance bound<00:05:56.750> but<00:05:57.320> allows<00:05:57.560> you<00:05:57.740> to<00:05:57.860> have 00:05:58.060 --> 00:05:58.070 align:start position:0% bound but allows you to have 00:05:58.070 --> 00:06:03.790 align:start position:0% bound but allows you to have frictionless<00:05:58.820> transactions<00:06:01.660> but<00:06:02.800> signing 00:06:03.790 --> 00:06:03.800 align:start position:0% frictionless transactions but signing 00:06:03.800 --> 00:06:05.800 align:start position:0% frictionless transactions but signing transactions<00:06:04.460> doesn't<00:06:05.270> really<00:06:05.420> mean<00:06:05.660> that 00:06:05.800 --> 00:06:05.810 align:start position:0% transactions doesn't really mean that 00:06:05.810 --> 00:06:07.990 align:start position:0% transactions doesn't really mean that much<00:06:05.990> unless<00:06:06.410> you've<00:06:06.650> got<00:06:06.860> someone<00:06:07.370> to<00:06:07.610> send 00:06:07.990 --> 00:06:08.000 align:start position:0% much unless you've got someone to send 00:06:08.000 --> 00:06:10.450 align:start position:0% much unless you've got someone to send transactions<00:06:08.720> to<00:06:08.960> or<00:06:09.170> something 00:06:10.450 --> 00:06:10.460 align:start position:0% transactions to or something 00:06:10.460 --> 00:06:13.780 align:start position:0% transactions to or something and<00:06:10.940> so<00:06:11.210> with<00:06:12.080> discover<00:06:12.830> we<00:06:13.340> really<00:06:13.580> want<00:06:13.730> to 00:06:13.780 --> 00:06:13.790 align:start position:0% and so with discover we really want to 00:06:13.790 --> 00:06:16.420 align:start position:0% and so with discover we really want to connect<00:06:14.390> you<00:06:14.540> with<00:06:14.570> people<00:06:15.080> and<00:06:15.650> apps<00:06:16.040> and 00:06:16.420 --> 00:06:16.430 align:start position:0% connect you with people and apps and 00:06:16.430 --> 00:06:19.900 align:start position:0% connect you with people and apps and communities<00:06:17.260> so<00:06:18.260> we're<00:06:18.410> solving<00:06:18.620> a<00:06:19.040> research 00:06:19.900 --> 00:06:19.910 align:start position:0% communities so we're solving a research 00:06:19.910 --> 00:06:22.000 align:start position:0% communities so we're solving a research problem<00:06:20.180> in<00:06:20.540> a<00:06:20.660> decentralized<00:06:21.050> manner<00:06:21.470> and 00:06:22.000 --> 00:06:22.010 align:start position:0% problem in a decentralized manner and 00:06:22.010 --> 00:06:25.080 align:start position:0% problem in a decentralized manner and this<00:06:22.220> is<00:06:22.370> what<00:06:22.490> we<00:06:22.550> do<00:06:22.700> with<00:06:22.820> the<00:06:22.880> discover 00:06:25.080 --> 00:06:25.090 align:start position:0% this is what we do with the discover 00:06:25.090 --> 00:06:27.970 align:start position:0% this is what we do with the discover discover<00:06:26.090> is<00:06:26.330> basically<00:06:26.840> a<00:06:26.960> naive<00:06:27.350> epidemic 00:06:27.970 --> 00:06:27.980 align:start position:0% discover is basically a naive epidemic 00:06:27.980 --> 00:06:32.440 align:start position:0% discover is basically a naive epidemic protocol<00:06:28.430> in<00:06:28.670> which<00:06:29.140> users<00:06:30.580> publish<00:06:31.580> public 00:06:32.440 --> 00:06:32.450 align:start position:0% protocol in which users publish public 00:06:32.450 --> 00:06:34.960 align:start position:0% protocol in which users publish public statuses<00:06:32.930> with<00:06:33.170> the<00:06:33.260> use<00:06:33.380> of<00:06:33.410> hashtags<00:06:33.980> and 00:06:34.960 --> 00:06:34.970 align:start position:0% statuses with the use of hashtags and 00:06:34.970 --> 00:06:38.610 align:start position:0% statuses with the use of hashtags and this<00:06:35.510> is<00:06:35.900> propagated<00:06:36.470> to<00:06:36.620> their<00:06:36.800> friends 00:06:38.610 --> 00:06:38.620 align:start position:0% this is propagated to their friends 00:06:38.620 --> 00:06:42.120 align:start position:0% this is propagated to their friends every<00:06:39.620> user<00:06:39.890> then<00:06:40.880> collects<00:06:41.300> a<00:06:41.510> case<00:06:41.750> of 00:06:42.120 --> 00:06:42.130 align:start position:0% every user then collects a case of 00:06:42.130 --> 00:06:43.270 align:start position:0% every user then collects a case of messages 00:06:43.270 --> 00:06:43.280 align:start position:0% messages 00:06:43.280 --> 00:06:46.210 align:start position:0% messages they've<00:06:43.400> seen<00:06:43.730> and<00:06:44.740> periodically<00:06:45.740> they 00:06:46.210 --> 00:06:46.220 align:start position:0% they've seen and periodically they 00:06:46.220 --> 00:06:48.190 align:start position:0% they've seen and periodically they generate<00:06:46.700> a<00:06:46.730> preference<00:06:47.270> list<00:06:47.510> and<00:06:47.780> then 00:06:48.190 --> 00:06:48.200 align:start position:0% generate a preference list and then 00:06:48.200 --> 00:06:50.950 align:start position:0% generate a preference list and then share<00:06:48.500> that<00:06:48.680> subset<00:06:49.190> with<00:06:50.060> all<00:06:50.180> of<00:06:50.360> the<00:06:50.450> all<00:06:50.780> of 00:06:50.950 --> 00:06:50.960 align:start position:0% share that subset with all of the all of 00:06:50.960 --> 00:06:53.920 align:start position:0% share that subset with all of the all of their<00:06:51.110> contacts<00:06:52.150> this<00:06:53.150> preference<00:06:53.600> list<00:06:53.750> is 00:06:53.920 --> 00:06:53.930 align:start position:0% their contacts this preference list is 00:06:53.930 --> 00:06:56.290 align:start position:0% their contacts this preference list is generated<00:06:54.680> by<00:06:55.610> a<00:06:55.639> bunch<00:06:55.880> of<00:06:56.000> different 00:06:56.290 --> 00:06:56.300 align:start position:0% generated by a bunch of different 00:06:56.300 --> 00:06:58.930 align:start position:0% generated by a bunch of different weighting<00:06:56.570> factors<00:06:57.020> for<00:06:57.889> example<00:06:57.980> if<00:06:58.639> they're 00:06:58.930 --> 00:06:58.940 align:start position:0% weighting factors for example if they're 00:06:58.940 --> 00:07:02.260 align:start position:0% weighting factors for example if they're mutual<00:06:59.330> friends<00:07:00.160> but<00:07:01.160> they're<00:07:01.340> like<00:07:02.120> how 00:07:02.260 --> 00:07:02.270 align:start position:0% mutual friends but they're like how 00:07:02.270 --> 00:07:06.060 align:start position:0% mutual friends but they're like how recent<00:07:02.750> it<00:07:03.380> is<00:07:03.530> if<00:07:03.830> they're<00:07:03.980> online 00:07:06.060 --> 00:07:06.070 align:start position:0% recent it is if they're online 00:07:06.070 --> 00:07:10.870 align:start position:0% recent it is if they're online there's<00:07:07.070> a<00:07:07.130> bunch<00:07:07.490> others<00:07:07.790> oh<00:07:09.160> yeah<00:07:10.190> like<00:07:10.430> if 00:07:10.870 --> 00:07:10.880 align:start position:0% there's a bunch others oh yeah like if 00:07:10.880 --> 00:07:12.730 align:start position:0% there's a bunch others oh yeah like if they're<00:07:11.300> been<00:07:11.510> chatting<00:07:12.200> with<00:07:12.320> that<00:07:12.410> person 00:07:12.730 --> 00:07:12.740 align:start position:0% they're been chatting with that person 00:07:12.740 --> 00:07:14.230 align:start position:0% they're been chatting with that person or<00:07:12.770> interacting<00:07:13.280> with<00:07:13.310> that<00:07:13.490> dap<00:07:13.700> for<00:07:14.030> a<00:07:14.060> long 00:07:14.230 --> 00:07:14.240 align:start position:0% or interacting with that dap for a long 00:07:14.240 --> 00:07:17.409 align:start position:0% or interacting with that dap for a long period<00:07:14.570> of<00:07:14.630> time<00:07:14.980> and<00:07:15.980> if<00:07:16.520> they<00:07:16.760> trust<00:07:17.060> them 00:07:17.409 --> 00:07:17.419 align:start position:0% period of time and if they trust them 00:07:17.419 --> 00:07:21.159 align:start position:0% period of time and if they trust them and<00:07:18.430> so<00:07:19.430> in<00:07:19.940> status<00:07:20.360> we're<00:07:20.690> actually<00:07:20.810> going<00:07:21.080> to 00:07:21.159 --> 00:07:21.169 align:start position:0% and so in status we're actually going to 00:07:21.169 --> 00:07:24.400 align:start position:0% and so in status we're actually going to be<00:07:21.260> building<00:07:21.440> multiple<00:07:21.710> layers<00:07:22.130> of<00:07:22.250> trust<00:07:23.410> and 00:07:24.400 --> 00:07:24.410 align:start position:0% be building multiple layers of trust and 00:07:24.410 --> 00:07:26.380 align:start position:0% be building multiple layers of trust and this<00:07:24.770> is<00:07:24.830> the<00:07:25.040> only<00:07:25.220> the<00:07:25.310> first<00:07:25.550> layer<00:07:25.790> which 00:07:26.380 --> 00:07:26.390 align:start position:0% this is the only the first layer which 00:07:26.390 --> 00:07:28.720 align:start position:0% this is the only the first layer which is<00:07:26.419> basically<00:07:26.930> automated<00:07:27.590> because<00:07:28.490> when<00:07:28.669> the 00:07:28.720 --> 00:07:28.730 align:start position:0% is basically automated because when the 00:07:28.730 --> 00:07:30.730 align:start position:0% is basically automated because when the status<00:07:29.060> is<00:07:29.210> shared<00:07:29.510> I<00:07:29.750> just<00:07:30.200> signed<00:07:30.500> by<00:07:30.680> the 00:07:30.730 --> 00:07:30.740 align:start position:0% status is shared I just signed by the 00:07:30.740 --> 00:07:32.530 align:start position:0% status is shared I just signed by the propagator<00:07:31.250> this<00:07:31.880> allows<00:07:32.150> us<00:07:32.300> to<00:07:32.390> build 00:07:32.530 --> 00:07:32.540 align:start position:0% propagator this allows us to build 00:07:32.540 --> 00:07:37.000 align:start position:0% propagator this allows us to build chains<00:07:32.840> of<00:07:33.680> propagation<00:07:34.340> to<00:07:34.669> see<00:07:35.770> how<00:07:36.770> far 00:07:37.000 --> 00:07:37.010 align:start position:0% chains of propagation to see how far 00:07:37.010 --> 00:07:38.950 align:start position:0% chains of propagation to see how far something<00:07:37.220> is<00:07:37.340> propagated<00:07:37.940> I<00:07:38.180> hope<00:07:38.419> by<00:07:38.630> and 00:07:38.950 --> 00:07:38.960 align:start position:0% something is propagated I hope by and 00:07:38.960 --> 00:07:46.290 align:start position:0% something is propagated I hope by and the<00:07:39.890> same<00:07:40.130> with<00:07:40.460> moderation<00:07:41.419> and<00:07:41.570> reporting 00:07:46.290 --> 00:07:46.300 align:start position:0% 00:07:46.300 --> 00:07:49.870 align:start position:0% so<00:07:47.300> as<00:07:47.600> you<00:07:47.930> may<00:07:48.080> know<00:07:48.580> status<00:07:49.580> was<00:07:49.700> built 00:07:49.870 --> 00:07:49.880 align:start position:0% so as you may know status was built 00:07:49.880 --> 00:07:51.670 align:start position:0% so as you may know status was built entirely<00:07:50.240> on<00:07:50.419> ethereum<00:07:50.780> protocols<00:07:51.440> and 00:07:51.670 --> 00:07:51.680 align:start position:0% entirely on ethereum protocols and 00:07:51.680 --> 00:07:54.159 align:start position:0% entirely on ethereum protocols and therefore<00:07:52.340> we<00:07:52.430> use<00:07:52.460> whisper<00:07:53.150> as<00:07:53.870> our 00:07:54.159 --> 00:07:54.169 align:start position:0% therefore we use whisper as our 00:07:54.169 --> 00:07:57.610 align:start position:0% therefore we use whisper as our messaging<00:07:54.710> transport<00:07:56.410> whisperer<00:07:57.410> has 00:07:57.610 --> 00:07:57.620 align:start position:0% messaging transport whisperer has 00:07:57.620 --> 00:07:59.820 align:start position:0% messaging transport whisperer has amazing<00:07:58.190> privacy<00:07:58.669> features<00:07:59.000> built<00:07:59.270> into<00:07:59.419> it 00:07:59.820 --> 00:07:59.830 align:start position:0% amazing privacy features built into it 00:07:59.830 --> 00:08:01.960 align:start position:0% amazing privacy features built into it however<00:08:00.830> it<00:08:01.130> does<00:08:01.250> it<00:08:01.400> isn't<00:08:01.760> without<00:08:01.820> its 00:08:01.960 --> 00:08:01.970 align:start position:0% however it does it isn't without its 00:08:01.970 --> 00:08:05.730 align:start position:0% however it does it isn't without its problems<00:08:02.240> and<00:08:02.950> one<00:08:03.950> of<00:08:04.070> these<00:08:04.250> is<00:08:04.610> essentially 00:08:05.730 --> 00:08:05.740 align:start position:0% problems and one of these is essentially 00:08:05.740 --> 00:08:08.050 align:start position:0% problems and one of these is essentially both<00:08:06.740> peers<00:08:07.070> need<00:08:07.310> to<00:08:07.400> be<00:08:07.520> online<00:08:07.640> when 00:08:08.050 --> 00:08:08.060 align:start position:0% both peers need to be online when 00:08:08.060 --> 00:08:11.860 align:start position:0% both peers need to be online when communicating<00:08:08.770> in<00:08:09.770> normal<00:08:10.160> usage<00:08:10.310> a<00:08:11.210> sender 00:08:11.860 --> 00:08:11.870 align:start position:0% communicating in normal usage a sender 00:08:11.870 --> 00:08:13.600 align:start position:0% communicating in normal usage a sender will<00:08:12.020> send<00:08:12.350> their<00:08:12.560> message<00:08:12.919> to<00:08:13.100> a<00:08:13.130> recipient 00:08:13.600 --> 00:08:13.610 align:start position:0% will send their message to a recipient 00:08:13.610 --> 00:08:14.920 align:start position:0% will send their message to a recipient it'll<00:08:14.060> bounce<00:08:14.180> around<00:08:14.479> the<00:08:14.690> network 00:08:14.920 --> 00:08:14.930 align:start position:0% it'll bounce around the network 00:08:14.930 --> 00:08:17.700 align:start position:0% it'll bounce around the network eventually<00:08:15.610> arrive<00:08:16.610> at<00:08:16.760> its<00:08:16.880> destination<00:08:17.090> and 00:08:17.700 --> 00:08:17.710 align:start position:0% eventually arrive at its destination and 00:08:17.710 --> 00:08:20.350 align:start position:0% eventually arrive at its destination and this<00:08:18.710> receive<00:08:19.039> as<00:08:19.280> recipient<00:08:20.000> will<00:08:20.120> send<00:08:20.270> an 00:08:20.350 --> 00:08:20.360 align:start position:0% this receive as recipient will send an 00:08:20.360 --> 00:08:23.670 align:start position:0% this receive as recipient will send an acknowledgement<00:08:20.930> of<00:08:21.020> that<00:08:21.320> that<00:08:22.220> message 00:08:23.670 --> 00:08:23.680 align:start position:0% acknowledgement of that that message 00:08:23.680 --> 00:08:27.790 align:start position:0% acknowledgement of that that message however<00:08:24.820> if<00:08:25.820> the<00:08:25.970> recipient<00:08:26.419> is<00:08:26.479> offline<00:08:27.050> the 00:08:27.790 --> 00:08:27.800 align:start position:0% however if the recipient is offline the 00:08:27.800 --> 00:08:29.770 align:start position:0% however if the recipient is offline the messenger<00:08:28.250> the<00:08:28.850> sender<00:08:29.180> will<00:08:29.330> send<00:08:29.630> out<00:08:29.750> a 00:08:29.770 --> 00:08:29.780 align:start position:0% messenger the sender will send out a 00:08:29.780 --> 00:08:33.670 align:start position:0% messenger the sender will send out a message<00:08:30.050> and<00:08:30.979> periodically<00:08:31.700> resend<00:08:32.330> it<00:08:32.680> but 00:08:33.670 --> 00:08:33.680 align:start position:0% message and periodically resend it but 00:08:33.680 --> 00:08:35.890 align:start position:0% message and periodically resend it but the<00:08:34.190> recipient<00:08:34.669> is<00:08:34.849> both<00:08:35.240> unaware<00:08:35.870> that 00:08:35.890 --> 00:08:35.900 align:start position:0% the recipient is both unaware that 00:08:35.900 --> 00:08:38.649 align:start position:0% the recipient is both unaware that they've<00:08:36.260> received<00:08:36.409> a<00:08:36.680> message<00:08:37.039> and<00:08:37.450> they<00:08:38.450> need 00:08:38.649 --> 00:08:38.659 align:start position:0% they've received a message and they need 00:08:38.659 --> 00:08:40.510 align:start position:0% they've received a message and they need to<00:08:38.810> be<00:08:38.900> needing<00:08:39.530> to<00:08:39.589> come<00:08:39.680> back<00:08:39.860> online<00:08:40.039> and 00:08:40.510 --> 00:08:40.520 align:start position:0% to be needing to come back online and 00:08:40.520 --> 00:08:42.250 align:start position:0% to be needing to come back online and wait<00:08:40.760> for<00:08:40.909> the<00:08:41.000> sender<00:08:41.360> to<00:08:41.510> rebuild<00:08:42.110> their 00:08:42.250 --> 00:08:42.260 align:start position:0% wait for the sender to rebuild their 00:08:42.260 --> 00:08:46.630 align:start position:0% wait for the sender to rebuild their chat<00:08:42.469> history<00:08:44.260> so<00:08:45.260> we<00:08:45.890> are<00:08:46.010> introducing 00:08:46.630 --> 00:08:46.640 align:start position:0% chat history so we are introducing 00:08:46.640 --> 00:08:48.790 align:start position:0% chat history so we are introducing status<00:08:47.330> nodes<00:08:47.570> which<00:08:48.080> act<00:08:48.320> as<00:08:48.470> offline 00:08:48.790 --> 00:08:48.800 align:start position:0% status nodes which act as offline 00:08:48.800 --> 00:08:51.100 align:start position:0% status nodes which act as offline inboxes<00:08:49.490> are<00:08:49.670> four<00:08:49.970> whisper<00:08:50.270> as<00:08:50.390> well<00:08:50.900> as 00:08:51.100 --> 00:08:51.110 align:start position:0% inboxes are four whisper as well as 00:08:51.110 --> 00:08:54.730 align:start position:0% inboxes are four whisper as well as helpers<00:08:52.100> for<00:08:52.610> external<00:08:53.120> services<00:08:53.810> such<00:08:54.589> as 00:08:54.730 --> 00:08:54.740 align:start position:0% helpers for external services such as 00:08:54.740 --> 00:08:57.369 align:start position:0% helpers for external services such as push<00:08:54.950> notifications<00:08:55.750> it<00:08:56.750> basically 00:08:57.369 --> 00:08:57.379 align:start position:0% push notifications it basically 00:08:57.379 --> 00:09:00.479 align:start position:0% push notifications it basically works<00:08:57.499> on<00:08:57.709> a<00:08:57.769> promise<00:08:58.669> challenge<00:08:59.089> deposit<00:08:59.539> and 00:09:00.479 --> 00:09:00.489 align:start position:0% works on a promise challenge deposit and 00:09:00.489 --> 00:09:04.239 align:start position:0% works on a promise challenge deposit and it<00:09:01.489> allows<00:09:01.759> the<00:09:01.939> sender<00:09:02.329> to<00:09:02.359> send<00:09:03.249> these 00:09:04.239 --> 00:09:04.249 align:start position:0% it allows the sender to send these 00:09:04.249 --> 00:09:05.919 align:start position:0% it allows the sender to send these messages<00:09:04.669> out<00:09:04.819> they<00:09:05.119> get<00:09:05.269> collected<00:09:05.660> in<00:09:05.779> these 00:09:05.919 --> 00:09:05.929 align:start position:0% messages out they get collected in these 00:09:05.929 --> 00:09:08.169 align:start position:0% messages out they get collected in these nodes<00:09:06.289> there<00:09:07.220> are<00:09:07.249> sipping<00:09:07.579> that<00:09:07.729> can<00:09:07.879> be<00:09:07.970> then 00:09:08.169 --> 00:09:08.179 align:start position:0% nodes there are sipping that can be then 00:09:08.179 --> 00:09:11.379 align:start position:0% nodes there are sipping that can be then informed<00:09:08.779> come<00:09:09.319> back<00:09:09.499> online<00:09:09.709> and<00:09:10.389> rebuild 00:09:11.379 --> 00:09:11.389 align:start position:0% informed come back online and rebuild 00:09:11.389 --> 00:09:13.569 align:start position:0% informed come back online and rebuild their<00:09:11.539> history<00:09:11.929> with<00:09:12.109> a<00:09:12.169> note<00:09:12.439> even<00:09:12.979> if<00:09:13.160> the 00:09:13.569 --> 00:09:13.579 align:start position:0% their history with a note even if the 00:09:13.579 --> 00:09:18.399 align:start position:0% their history with a note even if the sender<00:09:13.909> is<00:09:14.059> not<00:09:14.179> available<00:09:16.539> well<00:09:17.539> you<00:09:18.259> may<00:09:18.379> be 00:09:18.399 --> 00:09:18.409 align:start position:0% sender is not available well you may be 00:09:18.409 --> 00:09:19.869 align:start position:0% sender is not available well you may be wondering<00:09:18.889> well<00:09:19.099> who<00:09:19.189> is<00:09:19.309> going<00:09:19.489> to<00:09:19.609> run<00:09:19.729> these 00:09:19.869 --> 00:09:19.879 align:start position:0% wondering well who is going to run these 00:09:19.879 --> 00:09:22.179 align:start position:0% wondering well who is going to run these notes<00:09:20.149> and<00:09:20.509> of<00:09:20.779> course<00:09:20.989> if<00:09:21.229> somebody<00:09:21.529> has<00:09:22.159> a 00:09:22.179 --> 00:09:22.189 align:start position:0% notes and of course if somebody has a 00:09:22.189 --> 00:09:24.869 align:start position:0% notes and of course if somebody has a server<00:09:22.579> they<00:09:22.879> can<00:09:23.029> run<00:09:23.179> it<00:09:23.299> in<00:09:23.389> a<00:09:23.809> headless<00:09:24.169> way 00:09:24.869 --> 00:09:24.879 align:start position:0% server they can run it in a headless way 00:09:24.879 --> 00:09:26.949 align:start position:0% server they can run it in a headless way but<00:09:25.879> really<00:09:26.029> we<00:09:26.329> think<00:09:26.509> it<00:09:26.569> can<00:09:26.689> do<00:09:26.779> a<00:09:26.809> bit 00:09:26.949 --> 00:09:26.959 align:start position:0% but really we think it can do a bit 00:09:26.959 --> 00:09:29.710 align:start position:0% but really we think it can do a bit better<00:09:27.109> than<00:09:27.319> that<00:09:27.349> and<00:09:27.859> so<00:09:28.729> we<00:09:29.569> actually 00:09:29.710 --> 00:09:29.720 align:start position:0% better than that and so we actually 00:09:29.720 --> 00:09:33.129 align:start position:0% better than that and so we actually think<00:09:30.249> you<00:09:31.249> can<00:09:31.429> do<00:09:31.549> it<00:09:31.959> because<00:09:32.959> we're 00:09:33.129 --> 00:09:33.139 align:start position:0% think you can do it because we're 00:09:33.139 --> 00:09:35.979 align:start position:0% think you can do it because we're actually<00:09:33.259> expanding<00:09:34.220> our<00:09:34.459> platform<00:09:34.970> reach<00:09:35.209> so 00:09:35.979 --> 00:09:35.989 align:start position:0% actually expanding our platform reach so 00:09:35.989 --> 00:09:37.269 align:start position:0% actually expanding our platform reach so we're<00:09:36.109> not<00:09:36.169> targeting<00:09:36.379> Android<00:09:36.979> and<00:09:37.129> iOS 00:09:37.269 --> 00:09:37.279 align:start position:0% we're not targeting Android and iOS 00:09:37.279 --> 00:09:39.669 align:start position:0% we're not targeting Android and iOS anymore<00:09:38.089> but<00:09:38.419> we're<00:09:38.539> also<00:09:38.689> targeting<00:09:39.319> Linux 00:09:39.669 --> 00:09:39.679 align:start position:0% anymore but we're also targeting Linux 00:09:39.679 --> 00:09:48.400 align:start position:0% anymore but we're also targeting Linux Mac<00:09:40.129> OS<00:09:40.159> and<00:09:40.579> windows 00:09:48.400 --> 00:09:48.410 align:start position:0% 00:09:48.410 --> 00:09:51.880 align:start position:0% and<00:09:49.270> so<00:09:50.270> with<00:09:50.420> this<00:09:50.630> you<00:09:51.230> are<00:09:51.500> we're<00:09:51.650> going<00:09:51.800> to 00:09:51.880 --> 00:09:51.890 align:start position:0% and so with this you are we're going to 00:09:51.890 --> 00:09:53.770 align:start position:0% and so with this you are we're going to make<00:09:51.980> it<00:09:52.100> dead<00:09:52.340> easy<00:09:52.550> for<00:09:53.120> you<00:09:53.210> to<00:09:53.360> set<00:09:53.600> up<00:09:53.630> a 00:09:53.770 --> 00:09:53.780 align:start position:0% make it dead easy for you to set up a 00:09:53.780 --> 00:09:56.470 align:start position:0% make it dead easy for you to set up a status<00:09:54.110> node<00:09:54.380> and<00:09:54.950> integrate<00:09:55.850> with<00:09:55.970> external 00:09:56.470 --> 00:09:56.480 align:start position:0% status node and integrate with external 00:09:56.480 --> 00:09:58.360 align:start position:0% status node and integrate with external services<00:09:56.990> whether<00:09:57.710> there<00:09:57.890> are<00:09:57.920> other<00:09:58.010> chat 00:09:58.360 --> 00:09:58.370 align:start position:0% services whether there are other chat 00:09:58.370 --> 00:10:02.440 align:start position:0% services whether there are other chat protocols<00:09:58.970> or<00:09:59.270> push<00:09:59.600> notifications<00:10:00.700> and<00:10:01.700> at 00:10:02.440 --> 00:10:02.450 align:start position:0% protocols or push notifications and at 00:10:02.450 --> 00:10:04.800 align:start position:0% protocols or push notifications and at the<00:10:02.510> moment<00:10:02.660> we<00:10:02.900> have<00:10:03.170> an<00:10:03.860> in<00:10:03.980> an<00:10:04.370> internal 00:10:04.800 --> 00:10:04.810 align:start position:0% the moment we have an in an internal 00:10:04.810 --> 00:10:08.290 align:start position:0% the moment we have an in an internal friendly<00:10:05.810> competition<00:10:06.470> we<00:10:07.310> do<00:10:07.820> build<00:10:08.060> status 00:10:08.290 --> 00:10:08.300 align:start position:0% friendly competition we do build status 00:10:08.300 --> 00:10:10.870 align:start position:0% friendly competition we do build status on<00:10:08.630> a<00:10:08.690> single<00:10:09.260> code<00:10:09.470> base<00:10:09.500> and<00:10:10.010> that<00:10:10.460> rests<00:10:10.790> on 00:10:10.870 --> 00:10:10.880 align:start position:0% on a single code base and that rests on 00:10:10.880 --> 00:10:13.960 align:start position:0% on a single code base and that rests on top<00:10:11.000> of<00:10:11.150> react<00:10:11.450> native<00:10:11.980> so<00:10:12.980> on<00:10:13.340> the<00:10:13.610> the<00:10:13.790> more 00:10:13.960 --> 00:10:13.970 align:start position:0% top of react native so on the the more 00:10:13.970 --> 00:10:16.210 align:start position:0% top of react native so on the the more developed<00:10:14.180> version<00:10:14.540> there<00:10:15.290> is<00:10:15.650> actually 00:10:16.210 --> 00:10:16.220 align:start position:0% developed version there is actually 00:10:16.220 --> 00:10:19.150 align:start position:0% developed version there is actually using<00:10:16.490> react<00:10:16.730> native<00:10:16.940> web<00:10:17.300> and<00:10:17.860> the<00:10:18.860> others 00:10:19.150 --> 00:10:19.160 align:start position:0% using react native web and the others 00:10:19.160 --> 00:10:22.360 align:start position:0% using react native web and the others other<00:10:19.490> one<00:10:19.760> is<00:10:20.140> another<00:10:21.140> fork<00:10:21.530> of<00:10:21.680> a<00:10:21.800> conical 00:10:22.360 --> 00:10:22.370 align:start position:0% other one is another fork of a conical 00:10:22.370 --> 00:10:24.990 align:start position:0% other one is another fork of a conical project<00:10:22.960> where<00:10:23.960> we're<00:10:24.140> actually<00:10:24.260> building 00:10:24.990 --> 00:10:25.000 align:start position:0% project where we're actually building 00:10:25.000 --> 00:10:27.190 align:start position:0% project where we're actually building react<00:10:26.000> native<00:10:26.180> from<00:10:26.510> the<00:10:26.600> ground<00:10:26.840> up<00:10:27.020> for 00:10:27.190 --> 00:10:27.200 align:start position:0% react native from the ground up for 00:10:27.200 --> 00:10:30.430 align:start position:0% react native from the ground up for desktop<00:10:27.650> based<00:10:28.520> on<00:10:28.790> QT<00:10:29.240> and<00:10:29.480> currently<00:10:30.290> we 00:10:30.430 --> 00:10:30.440 align:start position:0% desktop based on QT and currently we 00:10:30.440 --> 00:10:34.510 align:start position:0% desktop based on QT and currently we have<00:10:30.470> 60%<00:10:31.480> component<00:10:32.480> coverage<00:10:32.810> on<00:10:32.990> that<00:10:33.520> so 00:10:34.510 --> 00:10:34.520 align:start position:0% have 60% component coverage on that so 00:10:34.520 --> 00:10:39.310 align:start position:0% have 60% component coverage on that so exciting<00:10:34.940> times<00:10:35.090> for<00:10:35.270> us<00:10:37.900> in<00:10:38.900> addition<00:10:39.230> to 00:10:39.310 --> 00:10:39.320 align:start position:0% exciting times for us in addition to 00:10:39.320 --> 00:10:43.300 align:start position:0% exciting times for us in addition to this<00:10:41.230> another<00:10:42.230> problem<00:10:42.440> that<00:10:42.650> we've<00:10:42.920> we 00:10:43.300 --> 00:10:43.310 align:start position:0% this another problem that we've we 00:10:43.310 --> 00:10:45.910 align:start position:0% this another problem that we've we really<00:10:43.610> faced<00:10:43.910> in<00:10:44.660> growing<00:10:44.990> our<00:10:45.140> organization 00:10:45.910 --> 00:10:45.920 align:start position:0% really faced in growing our organization 00:10:45.920 --> 00:10:49.090 align:start position:0% really faced in growing our organization is<00:10:46.130> that<00:10:46.940> the<00:10:47.420> talent<00:10:47.870> pool<00:10:48.110> in<00:10:48.680> the<00:10:48.830> crypto 00:10:49.090 --> 00:10:49.100 align:start position:0% is that the talent pool in the crypto 00:10:49.100 --> 00:10:52.240 align:start position:0% is that the talent pool in the crypto community<00:10:49.520> is<00:10:49.700> exceedingly<00:10:50.540> small<00:10:51.160> so<00:10:52.160> we 00:10:52.240 --> 00:10:52.250 align:start position:0% community is exceedingly small so we 00:10:52.250 --> 00:10:53.680 align:start position:0% community is exceedingly small so we want<00:10:52.400> to<00:10:52.460> take<00:10:52.580> the<00:10:52.670> strengths<00:10:53.120> of<00:10:53.270> being<00:10:53.570> an 00:10:53.680 --> 00:10:53.690 align:start position:0% want to take the strengths of being an 00:10:53.690 --> 00:10:56.250 align:start position:0% want to take the strengths of being an open<00:10:53.960> source<00:10:54.200> project<00:10:54.500> and<00:10:54.980> help<00:10:55.610> incentivize 00:10:56.250 --> 00:10:56.260 align:start position:0% open source project and help incentivize 00:10:56.260 --> 00:10:58.750 align:start position:0% open source project and help incentivize contributions<00:10:57.260> and<00:10:57.650> this<00:10:58.370> is<00:10:58.490> what<00:10:58.640> we're 00:10:58.750 --> 00:10:58.760 align:start position:0% contributions and this is what we're 00:10:58.760 --> 00:11:01.270 align:start position:0% contributions and this is what we're doing<00:10:58.880> with<00:10:59.210> open<00:10:59.540> bounty<00:10:59.960> this<00:11:00.680> allows<00:11:00.980> you 00:11:01.270 --> 00:11:01.280 align:start position:0% doing with open bounty this allows you 00:11:01.280 --> 00:11:05.320 align:start position:0% doing with open bounty this allows you to<00:11:01.700> assay<00:11:02.090> to<00:11:02.990> to<00:11:03.830> take<00:11:04.010> any<00:11:04.220> github<00:11:04.700> issue<00:11:04.940> and 00:11:05.320 --> 00:11:05.330 align:start position:0% to assay to to take any github issue and 00:11:05.330 --> 00:11:08.470 align:start position:0% to assay to to take any github issue and create<00:11:06.170> a<00:11:06.500> bounty<00:11:07.160> for<00:11:07.370> it<00:11:07.520> that<00:11:07.970> anyone<00:11:08.240> can 00:11:08.470 --> 00:11:08.480 align:start position:0% create a bounty for it that anyone can 00:11:08.480 --> 00:11:10.390 align:start position:0% create a bounty for it that anyone can then<00:11:08.630> contribute<00:11:09.110> to<00:11:09.290> whether<00:11:09.770> it's<00:11:10.010> earth<00:11:10.190> or 00:11:10.390 --> 00:11:10.400 align:start position:0% then contribute to whether it's earth or 00:11:10.400 --> 00:11:13.510 align:start position:0% then contribute to whether it's earth or any<00:11:10.550> RC<00:11:11.240> 20<00:11:11.510> tokens<00:11:12.250> but<00:11:13.250> we're<00:11:13.370> actually 00:11:13.510 --> 00:11:13.520 align:start position:0% any RC 20 tokens but we're actually 00:11:13.520 --> 00:11:15.460 align:start position:0% any RC 20 tokens but we're actually taking<00:11:13.910> this<00:11:14.030> a<00:11:14.180> step<00:11:14.450> further<00:11:14.510> from<00:11:15.080> just<00:11:15.380> the 00:11:15.460 --> 00:11:15.470 align:start position:0% taking this a step further from just the 00:11:15.470 --> 00:11:17.200 align:start position:0% taking this a step further from just the general<00:11:15.830> mechanism<00:11:16.010> which<00:11:16.640> we've<00:11:16.820> had<00:11:16.940> for<00:11:17.000> a 00:11:17.200 --> 00:11:17.210 align:start position:0% general mechanism which we've had for a 00:11:17.210 --> 00:11:19.240 align:start position:0% general mechanism which we've had for a while<00:11:17.450> and<00:11:17.690> we're<00:11:18.260> actually<00:11:18.410> building<00:11:18.920> out 00:11:19.240 --> 00:11:19.250 align:start position:0% while and we're actually building out 00:11:19.250 --> 00:11:21.790 align:start position:0% while and we're actually building out our<00:11:19.490> talent<00:11:20.000> scouting<00:11:20.330> and<00:11:20.720> human<00:11:21.290> resources 00:11:21.790 --> 00:11:21.800 align:start position:0% our talent scouting and human resources 00:11:21.800 --> 00:11:23.560 align:start position:0% our talent scouting and human resources around<00:11:22.040> this<00:11:22.430> so<00:11:22.970> we<00:11:23.060> can<00:11:23.150> help<00:11:23.360> other 00:11:23.560 --> 00:11:23.570 align:start position:0% around this so we can help other 00:11:23.570 --> 00:11:26.710 align:start position:0% around this so we can help other decentralize<00:11:24.260> organizations<00:11:25.180> build<00:11:26.180> their 00:11:26.710 --> 00:11:26.720 align:start position:0% decentralize organizations build their 00:11:26.720 --> 00:11:30.850 align:start position:0% decentralize organizations build their builder<00:11:27.620> software<00:11:27.830> just<00:11:28.610> like<00:11:28.730> we<00:11:29.030> are<00:11:29.710> and<00:11:30.710> in 00:11:30.850 --> 00:11:30.860 align:start position:0% builder software just like we are and in 00:11:30.860 --> 00:11:32.680 align:start position:0% builder software just like we are and in fact<00:11:30.890> we<00:11:31.220> also<00:11:31.430> have<00:11:31.790> a<00:11:32.180> million-dollar 00:11:32.680 --> 00:11:32.690 align:start position:0% fact we also have a million-dollar 00:11:32.690 --> 00:11:34.990 align:start position:0% fact we also have a million-dollar bounty<00:11:33.250> coming<00:11:34.250> up<00:11:34.370> to<00:11:34.640> help<00:11:34.820> other 00:11:34.990 --> 00:11:35.000 align:start position:0% bounty coming up to help other 00:11:35.000 --> 00:11:40.270 align:start position:0% bounty coming up to help other organizations<00:11:35.260> get<00:11:36.260> involved<00:11:39.070> so<00:11:40.070> please 00:11:40.270 --> 00:11:40.280 align:start position:0% organizations get involved so please 00:11:40.280 --> 00:11:42.040 align:start position:0% organizations get involved so please come<00:11:40.460> join<00:11:40.490> us<00:11:40.700> at<00:11:41.000> our<00:11:41.180> open<00:11:41.510> bounty<00:11:41.840> door 00:11:42.040 --> 00:11:42.050 align:start position:0% come join us at our open bounty door 00:11:42.050 --> 00:11:43.450 align:start position:0% come join us at our open bounty door status<00:11:42.230> tour<00:11:42.500> I<00:11:42.590> am<00:11:42.620> if<00:11:42.950> this<00:11:43.100> is<00:11:43.220> interesting 00:11:43.450 --> 00:11:43.460 align:start position:0% status tour I am if this is interesting 00:11:43.460 --> 00:11:48.840 align:start position:0% status tour I am if this is interesting to<00:11:43.670> you<00:11:46.030> in<00:11:47.030> terms<00:11:47.270> of<00:11:47.390> our<00:11:47.480> next<00:11:47.690> steps<00:11:47.930> well 00:11:48.840 --> 00:11:48.850 align:start position:0% to you in terms of our next steps well 00:11:48.850 --> 00:11:51.100 align:start position:0% to you in terms of our next steps well now<00:11:49.850> we<00:11:49.910> need<00:11:50.090> to<00:11:50.180> focus<00:11:50.330> on<00:11:50.600> optimization 00:11:51.100 --> 00:11:51.110 align:start position:0% now we need to focus on optimization 00:11:51.110 --> 00:11:53.620 align:start position:0% now we need to focus on optimization we're<00:11:52.010> good<00:11:52.160> preparing<00:11:52.610> our<00:11:52.730> security<00:11:53.270> audits 00:11:53.620 --> 00:11:53.630 align:start position:0% we're good preparing our security audits 00:11:53.630 --> 00:11:55.300 align:start position:0% we're good preparing our security audits which<00:11:54.170> allow<00:11:54.410> us<00:11:54.470> to<00:11:54.680> move<00:11:54.800> into<00:11:54.950> production 00:11:55.300 --> 00:11:55.310 align:start position:0% which allow us to move into production 00:11:55.310 --> 00:11:57.880 align:start position:0% which allow us to move into production we're<00:11:56.300> also<00:11:56.450> supporting<00:11:56.839> identity<00:11:57.410> standards 00:11:57.880 --> 00:11:57.890 align:start position:0% we're also supporting identity standards 00:11:57.890 --> 00:12:00.790 align:start position:0% we're also supporting identity standards and<00:11:58.130> we're<00:11:58.940> experimenting<00:11:59.300> with<00:11:59.990> the<00:12:00.290> swarm 00:12:00.790 --> 00:12:00.800 align:start position:0% and we're experimenting with the swarm 00:12:00.800 --> 00:12:02.420 align:start position:0% and we're experimenting with the swarm messaging<00:12:01.250> service 00:12:02.420 --> 00:12:02.430 align:start position:0% messaging service 00:12:02.430 --> 00:12:06.350 align:start position:0% messaging service for<00:12:03.000> more<00:12:03.120> convenience<00:12:04.670> so<00:12:05.670> that's<00:12:05.820> it<00:12:05.910> for<00:12:06.060> me 00:12:06.350 --> 00:12:06.360 align:start position:0% for more convenience so that's it for me 00:12:06.360 --> 00:12:09.020 align:start position:0% for more convenience so that's it for me thank<00:12:06.930> you<00:12:07.020> so<00:12:07.170> much<00:12:07.410> and<00:12:07.710> I<00:12:08.490> hope<00:12:08.820> you're<00:12:09.000> all 00:12:09.020 --> 00:12:09.030 align:start position:0% thank you so much and I hope you're all 00:12:09.030 --> 00:12:11.060 align:start position:0% thank you so much and I hope you're all using<00:12:09.360> status 00:12:11.060 --> 00:12:11.070 align:start position:0% using status 00:12:11.070 --> 00:12:21.370 align:start position:0% using status [Applause] 00:12:21.370 --> 00:12:21.380 align:start position:0% 00:12:21.380 --> 00:12:28.970 align:start position:0% [Music]