WEBVTT Kind: captions Language: en 00:00:04.580 --> 00:00:07.090 align:start position:0% good<00:00:05.480> morning<00:00:05.720> everybody<00:00:06.140> it's<00:00:06.590> great<00:00:06.830> to<00:00:06.950> be 00:00:07.090 --> 00:00:07.100 align:start position:0% good morning everybody it's great to be 00:00:07.100 --> 00:00:08.920 align:start position:0% good morning everybody it's great to be here<00:00:07.310> at<00:00:07.430> DEFCON<00:00:08.000> I<00:00:08.210> hope<00:00:08.360> everybody's<00:00:08.809> having 00:00:08.920 --> 00:00:08.930 align:start position:0% here at DEFCON I hope everybody's having 00:00:08.930 --> 00:00:12.100 align:start position:0% here at DEFCON I hope everybody's having a<00:00:09.110> great<00:00:09.230> week<00:00:10.270> my<00:00:11.270> name<00:00:11.389> is<00:00:11.480> rich<00:00:11.660> I<00:00:11.780> work<00:00:11.960> on<00:00:12.080> a 00:00:12.100 --> 00:00:12.110 align:start position:0% a great week my name is rich I work on a 00:00:12.110 --> 00:00:14.200 align:start position:0% a great week my name is rich I work on a project<00:00:12.350> called<00:00:12.560> wireline<00:00:13.220> and<00:00:13.490> what<00:00:14.120> I'm 00:00:14.200 --> 00:00:14.210 align:start position:0% project called wireline and what I'm 00:00:14.210 --> 00:00:15.970 align:start position:0% project called wireline and what I'm going<00:00:14.300> to<00:00:14.360> do<00:00:14.510> this<00:00:14.660> morning<00:00:14.960> is<00:00:15.140> demo<00:00:15.530> a<00:00:15.680> new 00:00:15.970 --> 00:00:15.980 align:start position:0% going to do this morning is demo a new 00:00:15.980 --> 00:00:18.400 align:start position:0% going to do this morning is demo a new kind<00:00:16.309> of<00:00:16.430> peer-to-peer<00:00:16.760> platform<00:00:17.689> for 00:00:18.400 --> 00:00:18.410 align:start position:0% kind of peer-to-peer platform for 00:00:18.410 --> 00:00:20.109 align:start position:0% kind of peer-to-peer platform for privacy<00:00:18.800> preserving<00:00:19.130> and<00:00:19.730> censorship 00:00:20.109 --> 00:00:20.119 align:start position:0% privacy preserving and censorship 00:00:20.119 --> 00:00:22.030 align:start position:0% privacy preserving and censorship resistant<00:00:20.720> applications<00:00:21.380> and<00:00:21.860> I'm<00:00:21.950> gonna 00:00:22.030 --> 00:00:22.040 align:start position:0% resistant applications and I'm gonna 00:00:22.040 --> 00:00:24.220 align:start position:0% resistant applications and I'm gonna show<00:00:22.279> how<00:00:22.490> easy<00:00:22.759> it<00:00:23.000> is<00:00:23.090> to<00:00:23.360> build<00:00:23.509> these<00:00:23.750> apps 00:00:24.220 --> 00:00:24.230 align:start position:0% show how easy it is to build these apps 00:00:24.230 --> 00:00:26.080 align:start position:0% show how easy it is to build these apps these<00:00:24.680> aren't<00:00:24.890> doubts<00:00:25.189> these<00:00:25.460> are<00:00:25.640> the<00:00:25.730> kinds 00:00:26.080 --> 00:00:26.090 align:start position:0% these aren't doubts these are the kinds 00:00:26.090 --> 00:00:28.030 align:start position:0% these aren't doubts these are the kinds of<00:00:26.180> apps<00:00:26.360> that<00:00:26.509> we<00:00:26.779> could<00:00:26.960> use<00:00:27.140> ourselves<00:00:27.380> to 00:00:28.030 --> 00:00:28.040 align:start position:0% of apps that we could use ourselves to 00:00:28.040 --> 00:00:29.560 align:start position:0% of apps that we could use ourselves to organize<00:00:28.460> and<00:00:28.820> manage<00:00:29.239> your<00:00:29.509> own 00:00:29.560 --> 00:00:29.570 align:start position:0% organize and manage your own 00:00:29.570 --> 00:00:32.740 align:start position:0% organize and manage your own decentralized<00:00:30.380> projects<00:00:31.480> but<00:00:32.480> first<00:00:32.660> thing 00:00:32.740 --> 00:00:32.750 align:start position:0% decentralized projects but first thing 00:00:32.750 --> 00:00:34.120 align:start position:0% decentralized projects but first thing when<00:00:32.840> I<00:00:32.899> talk<00:00:33.050> a<00:00:33.079> little<00:00:33.320> bit<00:00:33.560> about<00:00:33.860> what<00:00:34.100> I 00:00:34.120 --> 00:00:34.130 align:start position:0% when I talk a little bit about what I 00:00:34.130 --> 00:00:35.560 align:start position:0% when I talk a little bit about what I think<00:00:34.250> are<00:00:34.399> some<00:00:34.610> of<00:00:34.700> the<00:00:34.820> challenges<00:00:35.000> and 00:00:35.560 --> 00:00:35.570 align:start position:0% think are some of the challenges and 00:00:35.570 --> 00:00:38.110 align:start position:0% think are some of the challenges and opportunities<00:00:35.949> that<00:00:36.949> we<00:00:37.190> face<00:00:37.219> together<00:00:37.940> as<00:00:38.090> a 00:00:38.110 --> 00:00:38.120 align:start position:0% opportunities that we face together as a 00:00:38.120 --> 00:00:41.349 align:start position:0% opportunities that we face together as a community<00:00:38.649> so<00:00:39.649> I<00:00:39.890> used<00:00:40.370> to<00:00:40.519> work<00:00:40.699> for<00:00:41.120> Google 00:00:41.349 --> 00:00:41.359 align:start position:0% community so I used to work for Google 00:00:41.359 --> 00:00:45.240 align:start position:0% community so I used to work for Google it's<00:00:42.230> a<00:00:42.320> large<00:00:42.920> cloud<00:00:43.219> company<00:00:43.989> and<00:00:44.989> I'm<00:00:45.199> a 00:00:45.240 --> 00:00:45.250 align:start position:0% it's a large cloud company and I'm a 00:00:45.250 --> 00:00:48.250 align:start position:0% it's a large cloud company and I'm a distributed<00:00:46.250> systems<00:00:46.940> engineer<00:00:47.359> I<00:00:47.629> worked<00:00:48.050> on 00:00:48.250 --> 00:00:48.260 align:start position:0% distributed systems engineer I worked on 00:00:48.260 --> 00:00:49.689 align:start position:0% distributed systems engineer I worked on cloud<00:00:48.559> technologies<00:00:49.100> for<00:00:49.280> about<00:00:49.399> 10<00:00:49.670> years 00:00:49.689 --> 00:00:49.699 align:start position:0% cloud technologies for about 10 years 00:00:49.699 --> 00:00:51.430 align:start position:0% cloud technologies for about 10 years and<00:00:50.179> some<00:00:50.359> of<00:00:50.449> the<00:00:50.570> technologies<00:00:51.109> that<00:00:51.320> go 00:00:51.430 --> 00:00:51.440 align:start position:0% and some of the technologies that go 00:00:51.440 --> 00:00:53.319 align:start position:0% and some of the technologies that go into<00:00:51.589> Google<00:00:52.429> Docs<00:00:52.609> and<00:00:52.850> Gmail 00:00:53.319 --> 00:00:53.329 align:start position:0% into Google Docs and Gmail 00:00:53.329 --> 00:00:56.229 align:start position:0% into Google Docs and Gmail now<00:00:54.079> since<00:00:55.010> the<00:00:55.160> Cambridge<00:00:55.550> analytical 00:00:56.229 --> 00:00:56.239 align:start position:0% now since the Cambridge analytical 00:00:56.239 --> 00:00:59.529 align:start position:0% now since the Cambridge analytical crisis<00:00:56.960> last<00:00:57.199> year<00:00:57.620> there's<00:00:58.579> been<00:00:58.640> a<00:00:58.789> general 00:00:59.529 --> 00:00:59.539 align:start position:0% crisis last year there's been a general 00:00:59.539 --> 00:01:02.200 align:start position:0% crisis last year there's been a general increase<00:01:00.410> of<00:01:00.679> awareness<00:01:00.980> inside<00:01:01.670> the<00:01:01.879> general 00:01:02.200 --> 00:01:02.210 align:start position:0% increase of awareness inside the general 00:01:02.210 --> 00:01:04.210 align:start position:0% increase of awareness inside the general public<00:01:02.600> about<00:01:03.140> some<00:01:03.350> of<00:01:03.440> the<00:01:03.499> dangers<00:01:03.890> of<00:01:03.920> big 00:01:04.210 --> 00:01:04.220 align:start position:0% public about some of the dangers of big 00:01:04.220 --> 00:01:06.160 align:start position:0% public about some of the dangers of big tech<00:01:04.489> and<00:01:05.089> obviously<00:01:05.420> we<00:01:05.570> know<00:01:05.750> all<00:01:05.960> about 00:01:06.160 --> 00:01:06.170 align:start position:0% tech and obviously we know all about 00:01:06.170 --> 00:01:08.730 align:start position:0% tech and obviously we know all about that<00:01:06.409> but<00:01:07.159> there's<00:01:07.340> an<00:01:07.430> elephant<00:01:07.670> in<00:01:07.940> the<00:01:08.090> room 00:01:08.730 --> 00:01:08.740 align:start position:0% that but there's an elephant in the room 00:01:08.740 --> 00:01:11.200 align:start position:0% that but there's an elephant in the room despite<00:01:09.740> our<00:01:09.920> passion<00:01:10.370> for<00:01:10.400> decentralization 00:01:11.200 --> 00:01:11.210 align:start position:0% despite our passion for decentralization 00:01:11.210 --> 00:01:14.110 align:start position:0% despite our passion for decentralization most<00:01:11.990> of<00:01:12.200> us<00:01:12.350> are<00:01:12.650> still<00:01:12.980> using<00:01:13.550> applications 00:01:14.110 --> 00:01:14.120 align:start position:0% most of us are still using applications 00:01:14.120 --> 00:01:16.660 align:start position:0% most of us are still using applications like<00:01:14.300> Google<00:01:14.360> Docs<00:01:14.810> and<00:01:15.290> G<00:01:15.950> suite<00:01:16.280> and<00:01:16.550> other 00:01:16.660 --> 00:01:16.670 align:start position:0% like Google Docs and G suite and other 00:01:16.670 --> 00:01:18.790 align:start position:0% like Google Docs and G suite and other kinds<00:01:17.090> of<00:01:17.210> centralized<00:01:17.990> applications<00:01:18.620> to 00:01:18.790 --> 00:01:18.800 align:start position:0% kinds of centralized applications to 00:01:18.800 --> 00:01:21.370 align:start position:0% kinds of centralized applications to manage<00:01:19.070> our<00:01:19.190> projects<00:01:19.730> and<00:01:20.000> in<00:01:20.870> case<00:01:21.200> you're 00:01:21.370 --> 00:01:21.380 align:start position:0% manage our projects and in case you're 00:01:21.380 --> 00:01:23.050 align:start position:0% manage our projects and in case you're feeling<00:01:21.500> complacent<00:01:22.460> we<00:01:22.670> put<00:01:22.820> this<00:01:22.910> slide 00:01:23.050 --> 00:01:23.060 align:start position:0% feeling complacent we put this slide 00:01:23.060 --> 00:01:25.420 align:start position:0% feeling complacent we put this slide together<00:01:23.390> this<00:01:23.690> morning<00:01:23.960> from<00:01:24.800> certain 00:01:25.420 --> 00:01:25.430 align:start position:0% together this morning from certain 00:01:25.430 --> 00:01:26.560 align:start position:0% together this morning from certain things<00:01:25.640> that<00:01:25.700> have<00:01:25.850> been<00:01:25.910> happening<00:01:26.360> over<00:01:26.420> the 00:01:26.560 --> 00:01:26.570 align:start position:0% things that have been happening over the 00:01:26.570 --> 00:01:28.900 align:start position:0% things that have been happening over the last<00:01:26.660> couple<00:01:27.110> of<00:01:27.140> weeks<00:01:27.230> including<00:01:28.010> Adobe 00:01:28.900 --> 00:01:28.910 align:start position:0% last couple of weeks including Adobe 00:01:28.910 --> 00:01:33.700 align:start position:0% last couple of weeks including Adobe banning<00:01:29.360> users<00:01:30.350> in<00:01:30.500> Venezuela<00:01:32.290> this<00:01:33.290> is<00:01:33.470> Gmail 00:01:33.700 --> 00:01:33.710 align:start position:0% banning users in Venezuela this is Gmail 00:01:33.710 --> 00:01:35.860 align:start position:0% banning users in Venezuela this is Gmail this<00:01:34.280> was<00:01:34.400> a<00:01:34.430> revolutionary<00:01:35.180> app<00:01:35.510> when<00:01:35.840> it 00:01:35.860 --> 00:01:35.870 align:start position:0% this was a revolutionary app when it 00:01:35.870 --> 00:01:39.880 align:start position:0% this was a revolutionary app when it launched<00:01:36.350> on<00:01:36.560> April<00:01:37.070> the<00:01:37.100> 1st<00:01:37.570> 2004<00:01:38.710> in<00:01:39.710> fact 00:01:39.880 --> 00:01:39.890 align:start position:0% launched on April the 1st 2004 in fact 00:01:39.890 --> 00:01:41.320 align:start position:0% launched on April the 1st 2004 in fact it<00:01:39.980> was<00:01:40.070> so<00:01:40.220> revolutionary<00:01:40.520> people<00:01:41.150> thought 00:01:41.320 --> 00:01:41.330 align:start position:0% it was so revolutionary people thought 00:01:41.330 --> 00:01:42.670 align:start position:0% it was so revolutionary people thought it<00:01:41.450> was<00:01:41.480> a<00:01:41.570> joke<00:01:41.900> thought<00:01:42.200> it<00:01:42.320> was<00:01:42.410> an<00:01:42.500> April 00:01:42.670 --> 00:01:42.680 align:start position:0% it was a joke thought it was an April 00:01:42.680 --> 00:01:44.860 align:start position:0% it was a joke thought it was an April Fool's<00:01:42.950> joke<00:01:43.040> and<00:01:43.520> the<00:01:44.120> reason<00:01:44.450> for<00:01:44.480> that<00:01:44.630> is 00:01:44.860 --> 00:01:44.870 align:start position:0% Fool's joke and the reason for that is 00:01:44.870 --> 00:01:47.230 align:start position:0% Fool's joke and the reason for that is it<00:01:45.080> offered<00:01:45.410> free<00:01:45.710> storage<00:01:46.280> this<00:01:47.030> is<00:01:47.180> the 00:01:47.230 --> 00:01:47.240 align:start position:0% it offered free storage this is the 00:01:47.240 --> 00:01:50.140 align:start position:0% it offered free storage this is the unprecedented<00:01:47.980> kind<00:01:48.980> of<00:01:49.130> business<00:01:49.700> model<00:01:49.910> at 00:01:50.140 --> 00:01:50.150 align:start position:0% unprecedented kind of business model at 00:01:50.150 --> 00:01:52.420 align:start position:0% unprecedented kind of business model at the<00:01:50.240> time<00:01:50.480> and<00:01:50.930> the<00:01:51.680> reason<00:01:51.950> it<00:01:52.010> was<00:01:52.070> able<00:01:52.340> to 00:01:52.420 --> 00:01:52.430 align:start position:0% the time and the reason it was able to 00:01:52.430 --> 00:01:53.920 align:start position:0% the time and the reason it was able to do<00:01:52.580> that<00:01:52.760> was<00:01:53.000> through<00:01:53.030> a<00:01:53.210> technological 00:01:53.920 --> 00:01:53.930 align:start position:0% do that was through a technological 00:01:53.930 --> 00:01:55.540 align:start position:0% do that was through a technological breakthrough<00:01:53.960> called<00:01:54.650> BigTable<00:01:55.340> that 00:01:55.540 --> 00:01:55.550 align:start position:0% breakthrough called BigTable that 00:01:55.550 --> 00:01:58.240 align:start position:0% breakthrough called BigTable that offered<00:01:55.850> near<00:01:56.030> infinite<00:01:56.570> scale<00:01:56.930> storage<00:01:57.440> and 00:01:58.240 --> 00:01:58.250 align:start position:0% offered near infinite scale storage and 00:01:58.250 --> 00:01:59.860 align:start position:0% offered near infinite scale storage and it's<00:01:58.370> these<00:01:58.520> breakthroughs<00:01:58.850> that<00:01:59.480> changed 00:01:59.860 --> 00:01:59.870 align:start position:0% it's these breakthroughs that changed 00:01:59.870 --> 00:02:01.540 align:start position:0% it's these breakthroughs that changed the<00:01:59.990> paradigm<00:02:00.170> that<00:02:00.770> it's<00:02:01.160> been<00:02:01.370> happening 00:02:01.540 --> 00:02:01.550 align:start position:0% the paradigm that it's been happening 00:02:01.550 --> 00:02:03.610 align:start position:0% the paradigm that it's been happening every<00:02:02.090> 10<00:02:02.300> years<00:02:02.330> or<00:02:02.660> so<00:02:02.870> over<00:02:02.960> the<00:02:03.110> last<00:02:03.230> 40 00:02:03.610 --> 00:02:03.620 align:start position:0% every 10 years or so over the last 40 00:02:03.620 --> 00:02:05.950 align:start position:0% every 10 years or so over the last 40 years<00:02:03.850> it's<00:02:04.850> ultimately<00:02:05.240> led<00:02:05.480> to<00:02:05.510> what<00:02:05.840> we 00:02:05.950 --> 00:02:05.960 align:start position:0% years it's ultimately led to what we 00:02:05.960 --> 00:02:08.740 align:start position:0% years it's ultimately led to what we think<00:02:06.230> of<00:02:06.320> as<00:02:06.410> the<00:02:06.590> web<00:02:06.740> today<00:02:06.950> but<00:02:07.730> jima<00:02:08.539> was 00:02:08.740 --> 00:02:08.750 align:start position:0% think of as the web today but jima was 00:02:08.750 --> 00:02:11.110 align:start position:0% think of as the web today but jima was started<00:02:09.140> by<00:02:09.259> a<00:02:09.289> small<00:02:09.679> team<00:02:09.709> and<00:02:10.280> they<00:02:11.060> were 00:02:11.110 --> 00:02:11.120 align:start position:0% started by a small team and they were 00:02:11.120 --> 00:02:13.060 align:start position:0% started by a small team and they were trying<00:02:11.599> to<00:02:11.780> do<00:02:11.930> something<00:02:12.290> that<00:02:12.410> was<00:02:12.500> more<00:02:12.710> to 00:02:13.060 --> 00:02:13.070 align:start position:0% trying to do something that was more to 00:02:13.070 --> 00:02:14.650 align:start position:0% trying to do something that was more to build<00:02:13.250> apps<00:02:13.460> that<00:02:13.670> were<00:02:13.730> more<00:02:13.910> responsive<00:02:14.630> to 00:02:14.650 --> 00:02:14.660 align:start position:0% build apps that were more responsive to 00:02:14.660 --> 00:02:17.200 align:start position:0% build apps that were more responsive to create<00:02:15.110> better<00:02:15.260> user<00:02:15.620> experiences<00:02:16.490> and<00:02:16.820> it's 00:02:17.200 --> 00:02:17.210 align:start position:0% create better user experiences and it's 00:02:17.210 --> 00:02:18.080 align:start position:0% create better user experiences and it's this 00:02:18.080 --> 00:02:18.090 align:start position:0% this 00:02:18.090 --> 00:02:21.380 align:start position:0% this more<00:02:18.470> responsive<00:02:19.470> UX<00:02:20.340> that's<00:02:20.730> become<00:02:21.180> known 00:02:21.380 --> 00:02:21.390 align:start position:0% more responsive UX that's become known 00:02:21.390 --> 00:02:24.350 align:start position:0% more responsive UX that's become known as<00:02:21.569> web<00:02:21.750> 2-0<00:02:22.349> that<00:02:22.890> drove<00:02:23.220> the<00:02:23.459> rapid<00:02:23.910> adoption 00:02:24.350 --> 00:02:24.360 align:start position:0% as web 2-0 that drove the rapid adoption 00:02:24.360 --> 00:02:29.089 align:start position:0% as web 2-0 that drove the rapid adoption of<00:02:24.810> these<00:02:25.319> technologies<00:02:27.200> the<00:02:28.200> Gmail<00:02:28.769> also 00:02:29.089 --> 00:02:29.099 align:start position:0% of these technologies the Gmail also 00:02:29.099 --> 00:02:30.800 align:start position:0% of these technologies the Gmail also introduced<00:02:29.580> something<00:02:29.910> else<00:02:30.060> a<00:02:30.300> new<00:02:30.540> business 00:02:30.800 --> 00:02:30.810 align:start position:0% introduced something else a new business 00:02:30.810 --> 00:02:34.100 align:start position:0% introduced something else a new business model<00:02:31.080> free<00:02:31.920> and<00:02:32.400> not<00:02:32.940> open<00:02:33.420> as<00:02:33.690> in<00:02:33.870> free 00:02:34.100 --> 00:02:34.110 align:start position:0% model free and not open as in free 00:02:34.110 --> 00:02:36.440 align:start position:0% model free and not open as in free software<00:02:34.590> foundation<00:02:35.280> but<00:02:35.730> free<00:02:36.030> meaning 00:02:36.440 --> 00:02:36.450 align:start position:0% software foundation but free meaning 00:02:36.450 --> 00:02:38.210 align:start position:0% software foundation but free meaning we'll<00:02:37.049> figure<00:02:37.290> out<00:02:37.470> what<00:02:37.620> the<00:02:37.709> monetization 00:02:38.210 --> 00:02:38.220 align:start position:0% we'll figure out what the monetization 00:02:38.220 --> 00:02:42.140 align:start position:0% we'll figure out what the monetization strategy<00:02:38.819> is<00:02:38.940> later<00:02:39.209> and<00:02:40.310> so<00:02:41.310> 15<00:02:41.730> years<00:02:42.000> later 00:02:42.140 --> 00:02:42.150 align:start position:0% strategy is later and so 15 years later 00:02:42.150 --> 00:02:44.660 align:start position:0% strategy is later and so 15 years later we've<00:02:42.450> got<00:02:42.569> a<00:02:42.930> billion<00:02:43.230> point<00:02:43.709> two<00:02:43.950> users<00:02:44.430> on 00:02:44.660 --> 00:02:44.670 align:start position:0% we've got a billion point two users on 00:02:44.670 --> 00:02:47.390 align:start position:0% we've got a billion point two users on the<00:02:44.760> Gmail<00:02:45.090> platform<00:02:45.860> but<00:02:46.860> the<00:02:46.920> app<00:02:47.099> itself 00:02:47.390 --> 00:02:47.400 align:start position:0% the Gmail platform but the app itself 00:02:47.400 --> 00:02:49.520 align:start position:0% the Gmail platform but the app itself hasn't<00:02:47.700> changed<00:02:47.970> very<00:02:48.030> much<00:02:48.239> jima<00:02:49.200> email 00:02:49.520 --> 00:02:49.530 align:start position:0% hasn't changed very much jima email 00:02:49.530 --> 00:02:51.199 align:start position:0% hasn't changed very much jima email itself<00:02:49.830> hasn't<00:02:50.190> changed<00:02:50.489> in<00:02:50.579> the<00:02:50.640> last<00:02:50.760> 50 00:02:51.199 --> 00:02:51.209 align:start position:0% itself hasn't changed in the last 50 00:02:51.209 --> 00:02:54.410 align:start position:0% itself hasn't changed in the last 50 years<00:02:51.769> dominant<00:02:52.769> companies<00:02:53.340> resist<00:02:53.970> change 00:02:54.410 --> 00:02:54.420 align:start position:0% years dominant companies resist change 00:02:54.420 --> 00:02:56.569 align:start position:0% years dominant companies resist change they<00:02:54.720> don't<00:02:54.900> want<00:02:55.079> to<00:02:55.310> cannibalize<00:02:56.310> their 00:02:56.569 --> 00:02:56.579 align:start position:0% they don't want to cannibalize their 00:02:56.579 --> 00:02:59.030 align:start position:0% they don't want to cannibalize their existing<00:02:57.090> products<00:02:57.480> in<00:02:57.810> fact<00:02:58.709> the<00:02:58.769> strong 00:02:59.030 --> 00:02:59.040 align:start position:0% existing products in fact the strong 00:02:59.040 --> 00:03:01.130 align:start position:0% existing products in fact the strong incentives<00:02:59.579> within<00:02:59.819> the<00:03:00.060> companies<00:03:00.510> that 00:03:01.130 --> 00:03:01.140 align:start position:0% incentives within the companies that 00:03:01.140 --> 00:03:02.690 align:start position:0% incentives within the companies that growth<00:03:01.440> is<00:03:01.650> the<00:03:01.829> only<00:03:01.950> thing<00:03:02.220> that<00:03:02.370> matters 00:03:02.690 --> 00:03:02.700 align:start position:0% growth is the only thing that matters 00:03:02.700 --> 00:03:04.789 align:start position:0% growth is the only thing that matters and<00:03:02.879> so<00:03:03.060> innovation<00:03:03.420> really<00:03:03.870> tapers<00:03:04.319> off<00:03:04.470> and 00:03:04.789 --> 00:03:04.799 align:start position:0% and so innovation really tapers off and 00:03:04.799 --> 00:03:07.430 align:start position:0% and so innovation really tapers off and because<00:03:05.489> it's<00:03:05.670> a<00:03:05.790> closed<00:03:06.030> system<00:03:06.299> none<00:03:07.260> of<00:03:07.349> us 00:03:07.430 --> 00:03:07.440 align:start position:0% because it's a closed system none of us 00:03:07.440 --> 00:03:10.640 align:start position:0% because it's a closed system none of us can<00:03:07.709> change<00:03:08.700> the<00:03:09.030> functionality<00:03:09.480> fixed<00:03:10.379> bugs 00:03:10.640 --> 00:03:10.650 align:start position:0% can change the functionality fixed bugs 00:03:10.650 --> 00:03:13.580 align:start position:0% can change the functionality fixed bugs add<00:03:10.980> new<00:03:11.370> features<00:03:11.579> or<00:03:11.910> even<00:03:12.150> verify<00:03:12.750> that<00:03:13.470> the 00:03:13.580 --> 00:03:13.590 align:start position:0% add new features or even verify that the 00:03:13.590 --> 00:03:14.750 align:start position:0% add new features or even verify that the application<00:03:14.099> is<00:03:14.220> doing<00:03:14.370> what<00:03:14.579> it's<00:03:14.700> supposed 00:03:14.750 --> 00:03:14.760 align:start position:0% application is doing what it's supposed 00:03:14.760 --> 00:03:17.300 align:start position:0% application is doing what it's supposed to<00:03:15.120> be<00:03:15.299> doing<00:03:15.480> and<00:03:15.930> if<00:03:16.890> you're<00:03:17.010> an<00:03:17.099> independent 00:03:17.300 --> 00:03:17.310 align:start position:0% to be doing and if you're an independent 00:03:17.310 --> 00:03:19.759 align:start position:0% to be doing and if you're an independent software<00:03:17.970> developer<00:03:18.720> competing<00:03:19.260> with<00:03:19.440> a<00:03:19.470> free 00:03:19.759 --> 00:03:19.769 align:start position:0% software developer competing with a free 00:03:19.769 --> 00:03:21.350 align:start position:0% software developer competing with a free business<00:03:20.069> model<00:03:20.610> is<00:03:20.760> really<00:03:21.000> difficult 00:03:21.350 --> 00:03:21.360 align:start position:0% business model is really difficult 00:03:21.360 --> 00:03:24.170 align:start position:0% business model is really difficult unless<00:03:21.870> your<00:03:22.680> business<00:03:23.010> model<00:03:23.250> is<00:03:23.579> to<00:03:23.970> try<00:03:24.120> to 00:03:24.170 --> 00:03:24.180 align:start position:0% unless your business model is to try to 00:03:24.180 --> 00:03:28.759 align:start position:0% unless your business model is to try to get<00:03:24.359> acquired<00:03:24.720> by<00:03:25.380> Google<00:03:26.120> so<00:03:27.380> gmail<00:03:28.380> is<00:03:28.470> part 00:03:28.759 --> 00:03:28.769 align:start position:0% get acquired by Google so gmail is part 00:03:28.769 --> 00:03:30.379 align:start position:0% get acquired by Google so gmail is part of<00:03:28.889> a<00:03:28.980> set<00:03:29.250> of<00:03:29.370> applications<00:03:29.880> called<00:03:30.060> the<00:03:30.209> G 00:03:30.379 --> 00:03:30.389 align:start position:0% of a set of applications called the G 00:03:30.389 --> 00:03:32.840 align:start position:0% of a set of applications called the G suite<00:03:30.690> and<00:03:31.380> the<00:03:31.470> G<00:03:31.650> suite<00:03:31.889> is<00:03:32.010> a<00:03:32.040> platform<00:03:32.670> and 00:03:32.840 --> 00:03:32.850 align:start position:0% suite and the G suite is a platform and 00:03:32.850 --> 00:03:34.339 align:start position:0% suite and the G suite is a platform and platforms<00:03:33.299> go<00:03:33.450> through<00:03:33.660> the<00:03:33.780> same<00:03:34.019> growth 00:03:34.339 --> 00:03:34.349 align:start position:0% platforms go through the same growth 00:03:34.349 --> 00:03:36.770 align:start position:0% platforms go through the same growth cycle<00:03:34.950> the<00:03:35.310> ones<00:03:35.489> that<00:03:35.670> succeed<00:03:36.090> there's<00:03:36.690> a 00:03:36.770 --> 00:03:36.780 align:start position:0% cycle the ones that succeed there's a 00:03:36.780 --> 00:03:39.410 align:start position:0% cycle the ones that succeed there's a large<00:03:37.530> adoption<00:03:38.250> curve<00:03:38.970> at<00:03:39.209> the<00:03:39.299> beginning 00:03:39.410 --> 00:03:39.420 align:start position:0% large adoption curve at the beginning 00:03:39.420 --> 00:03:43.129 align:start position:0% large adoption curve at the beginning and<00:03:39.989> then<00:03:40.799> at<00:03:40.920> a<00:03:41.010> certain<00:03:41.040> point<00:03:41.569> the<00:03:42.569> platform 00:03:43.129 --> 00:03:43.139 align:start position:0% and then at a certain point the platform 00:03:43.139 --> 00:03:45.410 align:start position:0% and then at a certain point the platform switches<00:03:43.769> from<00:03:43.920> being<00:03:44.130> an<00:03:44.190> innovator<00:03:44.549> into<00:03:45.389> a 00:03:45.410 --> 00:03:45.420 align:start position:0% switches from being an innovator into a 00:03:45.420 --> 00:03:47.300 align:start position:0% switches from being an innovator into a rent<00:03:45.720> seeker<00:03:46.200> and<00:03:46.349> it's<00:03:46.680> that<00:03:46.829> point<00:03:47.069> that 00:03:47.300 --> 00:03:47.310 align:start position:0% rent seeker and it's that point that 00:03:47.310 --> 00:03:49.339 align:start position:0% rent seeker and it's that point that they<00:03:47.400> start<00:03:47.669> to<00:03:47.730> monetize<00:03:48.209> the<00:03:48.480> platform<00:03:48.989> and 00:03:49.339 --> 00:03:49.349 align:start position:0% they start to monetize the platform and 00:03:49.349 --> 00:03:51.199 align:start position:0% they start to monetize the platform and often<00:03:49.919> these<00:03:50.010> monetization<00:03:50.549> strategies 00:03:51.199 --> 00:03:51.209 align:start position:0% often these monetization strategies 00:03:51.209 --> 00:03:54.979 align:start position:0% often these monetization strategies conflict<00:03:51.690> with<00:03:51.840> our<00:03:51.989> interests<00:03:52.319> as<00:03:52.620> users<00:03:53.989> for 00:03:54.979 --> 00:03:54.989 align:start position:0% conflict with our interests as users for 00:03:54.989 --> 00:03:57.289 align:start position:0% conflict with our interests as users for developers<00:03:55.500> as<00:03:55.769> taxes<00:03:56.340> imposed<00:03:56.549> on<00:03:57.209> the 00:03:57.289 --> 00:03:57.299 align:start position:0% developers as taxes imposed on the 00:03:57.299 --> 00:03:59.420 align:start position:0% developers as taxes imposed on the platform<00:03:57.780> and<00:03:58.049> restrictions<00:03:58.889> on<00:03:59.010> the<00:03:59.099> kinds 00:03:59.420 --> 00:03:59.430 align:start position:0% platform and restrictions on the kinds 00:03:59.430 --> 00:04:00.949 align:start position:0% platform and restrictions on the kinds of<00:03:59.549> applications<00:04:00.060> that<00:04:00.150> can<00:04:00.359> be<00:04:00.419> built<00:04:00.690> and 00:04:00.949 --> 00:04:00.959 align:start position:0% of applications that can be built and 00:04:00.959 --> 00:04:07.150 align:start position:0% of applications that can be built and for<00:04:01.680> users<00:04:02.010> are<00:04:02.160> the<00:04:02.340> obvious<00:04:02.840> privacy<00:04:03.840> issues 00:04:07.150 --> 00:04:07.160 align:start position:0% 00:04:07.160 --> 00:04:12.289 align:start position:0% so<00:04:10.489> this<00:04:11.489> should<00:04:11.639> be<00:04:11.669> a<00:04:11.760> really<00:04:12.000> big 00:04:12.289 --> 00:04:12.299 align:start position:0% so this should be a really big 00:04:12.299 --> 00:04:15.740 align:start position:0% so this should be a really big opportunity<00:04:12.480> for<00:04:13.109> us<00:04:13.260> the<00:04:13.549> the<00:04:14.750> complacency 00:04:15.740 --> 00:04:15.750 align:start position:0% opportunity for us the the complacency 00:04:15.750 --> 00:04:18.409 align:start position:0% opportunity for us the the complacency of<00:04:15.780> the<00:04:16.079> dominant<00:04:16.530> players<00:04:17.120> why<00:04:18.120> aren't<00:04:18.329> we 00:04:18.409 --> 00:04:18.419 align:start position:0% of the dominant players why aren't we 00:04:18.419 --> 00:04:20.839 align:start position:0% of the dominant players why aren't we seeing<00:04:18.660> more<00:04:19.410> widespread<00:04:19.849> decentralized 00:04:20.839 --> 00:04:20.849 align:start position:0% seeing more widespread decentralized 00:04:20.849 --> 00:04:22.420 align:start position:0% seeing more widespread decentralized applications<00:04:21.299> why<00:04:21.900> aren't<00:04:22.079> we<00:04:22.200> seeing 00:04:22.420 --> 00:04:22.430 align:start position:0% applications why aren't we seeing 00:04:22.430 --> 00:04:25.779 align:start position:0% applications why aren't we seeing adoption<00:04:23.430> of<00:04:23.610> these<00:04:23.789> kinds<00:04:24.180> of<00:04:24.270> technologies 00:04:25.779 --> 00:04:25.789 align:start position:0% adoption of these kinds of technologies 00:04:25.789 --> 00:04:29.390 align:start position:0% adoption of these kinds of technologies well<00:04:26.789> the<00:04:26.880> truth<00:04:27.330> is<00:04:27.770> building<00:04:28.770> web<00:04:29.039> scale 00:04:29.390 --> 00:04:29.400 align:start position:0% well the truth is building web scale 00:04:29.400 --> 00:04:31.640 align:start position:0% well the truth is building web scale applications<00:04:30.150> is<00:04:30.330> really<00:04:30.390> difficult 00:04:31.640 --> 00:04:31.650 align:start position:0% applications is really difficult 00:04:31.650 --> 00:04:33.230 align:start position:0% applications is really difficult and<00:04:31.740> there's<00:04:32.220> been<00:04:32.340> 15<00:04:32.729> years<00:04:32.910> of<00:04:33.090> innovation 00:04:33.230 --> 00:04:33.240 align:start position:0% and there's been 15 years of innovation 00:04:33.240 --> 00:04:36.050 align:start position:0% and there's been 15 years of innovation in<00:04:33.930> the<00:04:34.290> tools<00:04:34.560> platforms<00:04:35.280> frameworks<00:04:35.820> and 00:04:36.050 --> 00:04:36.060 align:start position:0% in the tools platforms frameworks and 00:04:36.060 --> 00:04:38.510 align:start position:0% in the tools platforms frameworks and api's<00:04:36.509> that<00:04:37.199> we<00:04:37.350> have<00:04:37.560> to<00:04:37.770> build<00:04:37.979> web 00:04:38.510 --> 00:04:38.520 align:start position:0% api's that we have to build web 00:04:38.520 --> 00:04:40.129 align:start position:0% api's that we have to build web applications<00:04:39.270> and<00:04:39.449> we<00:04:39.509> just<00:04:39.720> don't<00:04:39.990> have 00:04:40.129 --> 00:04:40.139 align:start position:0% applications and we just don't have 00:04:40.139 --> 00:04:42.439 align:start position:0% applications and we just don't have those<00:04:40.470> today<00:04:40.800> so<00:04:41.039> I<00:04:41.490> thought<00:04:41.699> what<00:04:41.820> I<00:04:41.850> do<00:04:41.970> is 00:04:42.439 --> 00:04:42.449 align:start position:0% those today so I thought what I do is 00:04:42.449 --> 00:04:44.540 align:start position:0% those today so I thought what I do is quickly<00:04:43.020> go<00:04:43.199> through<00:04:43.380> some<00:04:43.650> of<00:04:43.949> the<00:04:44.039> elemental 00:04:44.540 --> 00:04:44.550 align:start position:0% quickly go through some of the elemental 00:04:44.550 --> 00:04:47.629 align:start position:0% quickly go through some of the elemental structures<00:04:45.030> required<00:04:45.479> to<00:04:46.259> build<00:04:46.530> web<00:04:47.370> scale 00:04:47.629 --> 00:04:47.639 align:start position:0% structures required to build web scale 00:04:47.639 --> 00:04:51.650 align:start position:0% structures required to build web scale applications<00:04:49.789> if<00:04:50.789> we<00:04:51.030> were<00:04:51.120> editing<00:04:51.300> a 00:04:51.650 --> 00:04:51.660 align:start position:0% applications if we were editing a 00:04:51.660 --> 00:04:53.360 align:start position:0% applications if we were editing a document<00:04:51.690> together<00:04:52.530> in<00:04:52.740> this<00:04:52.889> hall<00:04:53.160> this 00:04:53.360 --> 00:04:53.370 align:start position:0% document together in this hall this 00:04:53.370 --> 00:04:55.820 align:start position:0% document together in this hall this morning<00:04:53.430> it<00:04:54.030> makes<00:04:54.330> absolutely<00:04:54.990> no<00:04:55.110> sense<00:04:55.229> for 00:04:55.820 --> 00:04:55.830 align:start position:0% morning it makes absolutely no sense for 00:04:55.830 --> 00:04:57.560 align:start position:0% morning it makes absolutely no sense for each<00:04:55.860> of<00:04:56.039> our<00:04:56.100> keystrokes<00:04:56.729> to<00:04:56.940> be<00:04:57.060> sent<00:04:57.330> to<00:04:57.539> a 00:04:57.560 --> 00:04:57.570 align:start position:0% each of our keystrokes to be sent to a 00:04:57.570 --> 00:05:00.590 align:start position:0% each of our keystrokes to be sent to a server<00:04:58.259> in<00:04:58.590> Mountain<00:04:59.340> View<00:04:59.610> or<00:04:59.789> in<00:05:00.180> Tokyo<00:05:00.570> for 00:05:00.590 --> 00:05:00.600 align:start position:0% server in Mountain View or in Tokyo for 00:05:00.600 --> 00:05:03.680 align:start position:0% server in Mountain View or in Tokyo for that<00:05:00.870> matter<00:05:01.280> we<00:05:02.280> think<00:05:02.310> peer-to-peer<00:05:02.940> is<00:05:03.539> the 00:05:03.680 --> 00:05:03.690 align:start position:0% that matter we think peer-to-peer is the 00:05:03.690 --> 00:05:05.990 align:start position:0% that matter we think peer-to-peer is the obvious<00:05:04.050> solution<00:05:04.229> to<00:05:04.530> this<00:05:04.800> but<00:05:05.729> we<00:05:05.820> have<00:05:05.970> to 00:05:05.990 --> 00:05:06.000 align:start position:0% obvious solution to this but we have to 00:05:06.000 --> 00:05:07.430 align:start position:0% obvious solution to this but we have to add<00:05:06.180> additional<00:05:06.330> infrastructure<00:05:07.139> to<00:05:07.320> make 00:05:07.430 --> 00:05:07.440 align:start position:0% add additional infrastructure to make 00:05:07.440 --> 00:05:09.200 align:start position:0% add additional infrastructure to make peer-to-peer<00:05:07.770> work<00:05:08.310> seamlessly<00:05:08.669> in<00:05:09.090> the 00:05:09.200 --> 00:05:09.210 align:start position:0% peer-to-peer work seamlessly in the 00:05:09.210 --> 00:05:11.629 align:start position:0% peer-to-peer work seamlessly in the browser<00:05:09.440> we<00:05:10.440> need<00:05:10.590> stun<00:05:10.889> servers<00:05:11.430> and 00:05:11.629 --> 00:05:11.639 align:start position:0% browser we need stun servers and 00:05:11.639 --> 00:05:13.189 align:start position:0% browser we need stun servers and signaling<00:05:12.090> servers<00:05:12.510> so<00:05:12.660> that<00:05:12.690> the<00:05:12.900> different 00:05:13.189 --> 00:05:13.199 align:start position:0% signaling servers so that the different 00:05:13.199 --> 00:05:15.020 align:start position:0% signaling servers so that the different peers<00:05:13.410> can<00:05:13.560> find<00:05:13.830> each<00:05:13.979> other<00:05:14.190> and<00:05:14.639> we<00:05:14.760> have<00:05:14.880> to 00:05:15.020 --> 00:05:15.030 align:start position:0% peers can find each other and we have to 00:05:15.030 --> 00:05:16.610 align:start position:0% peers can find each other and we have to do<00:05:15.180> this<00:05:15.330> in<00:05:15.539> a<00:05:15.630> way<00:05:15.840> that<00:05:16.380> doesn't 00:05:16.610 --> 00:05:16.620 align:start position:0% do this in a way that doesn't 00:05:16.620 --> 00:05:19.360 align:start position:0% do this in a way that doesn't reintroduce<00:05:17.400> new<00:05:17.760> centralized<00:05:18.300> dependencies 00:05:19.360 --> 00:05:19.370 align:start position:0% reintroduce new centralized dependencies 00:05:19.370 --> 00:05:21.950 align:start position:0% reintroduce new centralized dependencies if<00:05:20.370> we<00:05:20.820> were<00:05:20.910> building<00:05:21.030> these<00:05:21.360> apps<00:05:21.630> on<00:05:21.870> the 00:05:21.950 --> 00:05:21.960 align:start position:0% if we were building these apps on the 00:05:21.960 --> 00:05:23.659 align:start position:0% if we were building these apps on the cloud<00:05:22.139> today<00:05:22.350> we<00:05:22.590> have<00:05:22.740> dozens<00:05:23.190> of<00:05:23.370> different 00:05:23.659 --> 00:05:23.669 align:start position:0% cloud today we have dozens of different 00:05:23.669 --> 00:05:25.310 align:start position:0% cloud today we have dozens of different database<00:05:24.090> solutions<00:05:24.599> that<00:05:24.810> we<00:05:24.900> could<00:05:25.080> use 00:05:25.310 --> 00:05:25.320 align:start position:0% database solutions that we could use 00:05:25.320 --> 00:05:27.140 align:start position:0% database solutions that we could use that<00:05:25.770> give<00:05:25.979> us<00:05:26.160> the<00:05:26.340> scale<00:05:26.639> that<00:05:26.849> we<00:05:27.000> would 00:05:27.140 --> 00:05:27.150 align:start position:0% that give us the scale that we would 00:05:27.150 --> 00:05:30.890 align:start position:0% that give us the scale that we would like<00:05:27.740> now<00:05:28.740> on<00:05:29.099> the<00:05:29.639> peer-to-peer<00:05:29.880> side<00:05:30.780> of 00:05:30.890 --> 00:05:30.900 align:start position:0% like now on the peer-to-peer side of 00:05:30.900 --> 00:05:32.990 align:start position:0% like now on the peer-to-peer side of things<00:05:31.169> BitTorrent<00:05:32.009> was<00:05:32.130> the<00:05:32.340> killer<00:05:32.550> app<00:05:32.759> and 00:05:32.990 --> 00:05:33.000 align:start position:0% things BitTorrent was the killer app and 00:05:33.000 --> 00:05:35.750 align:start position:0% things BitTorrent was the killer app and enabled<00:05:33.419> this<00:05:33.570> massive<00:05:34.199> scale<00:05:34.760> replication 00:05:35.750 --> 00:05:35.760 align:start position:0% enabled this massive scale replication 00:05:35.760 --> 00:05:38.300 align:start position:0% enabled this massive scale replication of<00:05:35.880> files<00:05:36.180> but<00:05:36.990> it<00:05:37.080> also<00:05:37.229> had<00:05:37.650> centralized 00:05:38.300 --> 00:05:38.310 align:start position:0% of files but it also had centralized 00:05:38.310 --> 00:05:40.550 align:start position:0% of files but it also had centralized dependencies<00:05:38.970> for<00:05:39.180> the<00:05:39.240> index<00:05:39.750> for<00:05:40.320> where<00:05:40.440> you 00:05:40.550 --> 00:05:40.560 align:start position:0% dependencies for the index for where you 00:05:40.560 --> 00:05:42.050 align:start position:0% dependencies for the index for where you actually<00:05:40.710> found<00:05:41.070> the<00:05:41.250> files<00:05:41.490> that<00:05:41.669> were<00:05:41.849> being 00:05:42.050 --> 00:05:42.060 align:start position:0% actually found the files that were being 00:05:42.060 --> 00:05:42.700 align:start position:0% actually found the files that were being shared 00:05:42.700 --> 00:05:42.710 align:start position:0% shared 00:05:42.710 --> 00:05:44.960 align:start position:0% shared but<00:05:43.710> the<00:05:43.800> BitTorrent<00:05:43.979> technologies<00:05:44.789> have 00:05:44.960 --> 00:05:44.970 align:start position:0% but the BitTorrent technologies have 00:05:44.970 --> 00:05:46.550 align:start position:0% but the BitTorrent technologies have evolved<00:05:45.479> into<00:05:45.690> different<00:05:45.990> kinds<00:05:46.349> of 00:05:46.550 --> 00:05:46.560 align:start position:0% evolved into different kinds of 00:05:46.560 --> 00:05:49.129 align:start position:0% evolved into different kinds of chain-linked<00:05:47.310> real<00:05:47.970> time<00:05:48.240> data<00:05:48.570> exchange 00:05:49.129 --> 00:05:49.139 align:start position:0% chain-linked real time data exchange 00:05:49.139 --> 00:05:51.589 align:start position:0% chain-linked real time data exchange protocols<00:05:49.740> like<00:05:50.010> secure<00:05:50.849> scuttle<00:05:51.270> des<00:05:51.389> and 00:05:51.589 --> 00:05:51.599 align:start position:0% protocols like secure scuttle des and 00:05:51.599 --> 00:05:53.839 align:start position:0% protocols like secure scuttle des and that<00:05:51.840> and<00:05:52.199> we<00:05:52.590> can<00:05:52.740> start<00:05:52.979> to<00:05:53.130> use<00:05:53.159> these<00:05:53.610> to 00:05:53.839 --> 00:05:53.849 align:start position:0% that and we can start to use these to 00:05:53.849 --> 00:05:57.379 align:start position:0% that and we can start to use these to build<00:05:54.169> replicated<00:05:55.169> databases<00:05:55.909> but<00:05:56.909> real-time 00:05:57.379 --> 00:05:57.389 align:start position:0% build replicated databases but real-time 00:05:57.389 --> 00:05:59.600 align:start position:0% build replicated databases but real-time collaboration<00:05:58.020> is<00:05:58.560> still<00:05:58.860> inherently<00:05:59.520> a 00:05:59.600 --> 00:05:59.610 align:start position:0% collaboration is still inherently a 00:05:59.610 --> 00:06:02.260 align:start position:0% collaboration is still inherently a really<00:06:00.060> difficult<00:06:00.270> problem<00:06:00.870> to<00:06:00.900> solve<00:06:01.229> in 00:06:02.260 --> 00:06:02.270 align:start position:0% really difficult problem to solve in 00:06:02.270 --> 00:06:04.820 align:start position:0% really difficult problem to solve in 2007<00:06:03.270> we're<00:06:03.720> working<00:06:04.020> on<00:06:04.110> technologies<00:06:04.680> at 00:06:04.820 --> 00:06:04.830 align:start position:0% 2007 we're working on technologies at 00:06:04.830 --> 00:06:05.960 align:start position:0% 2007 we're working on technologies at Google<00:06:05.130> called<00:06:05.310> operational 00:06:05.960 --> 00:06:05.970 align:start position:0% Google called operational 00:06:05.970 --> 00:06:07.879 align:start position:0% Google called operational transformations<00:06:06.810> this<00:06:07.320> was<00:06:07.500> for<00:06:07.680> a<00:06:07.710> project 00:06:07.879 --> 00:06:07.889 align:start position:0% transformations this was for a project 00:06:07.889 --> 00:06:09.920 align:start position:0% transformations this was for a project called<00:06:08.340> wave<00:06:08.580> that<00:06:09.030> some<00:06:09.570> of<00:06:09.690> you<00:06:09.780> will 00:06:09.920 --> 00:06:09.930 align:start position:0% called wave that some of you will 00:06:09.930 --> 00:06:11.480 align:start position:0% called wave that some of you will remember<00:06:10.050> and<00:06:10.680> this<00:06:10.949> is<00:06:11.099> what<00:06:11.250> enables 00:06:11.480 --> 00:06:11.490 align:start position:0% remember and this is what enables 00:06:11.490 --> 00:06:14.029 align:start position:0% remember and this is what enables different<00:06:11.880> clients<00:06:12.539> to<00:06:12.720> interoperate<00:06:13.229> at<00:06:13.889> the 00:06:14.029 --> 00:06:14.039 align:start position:0% different clients to interoperate at the 00:06:14.039 --> 00:06:17.000 align:start position:0% different clients to interoperate at the same<00:06:14.250> time<00:06:14.580> across<00:06:15.479> the<00:06:15.630> internet<00:06:16.050> but<00:06:16.740> again 00:06:17.000 --> 00:06:17.010 align:start position:0% same time across the internet but again 00:06:17.010 --> 00:06:20.110 align:start position:0% same time across the internet but again this<00:06:17.220> requires<00:06:17.610> centralized<00:06:18.240> infrastructure 00:06:20.110 --> 00:06:20.120 align:start position:0% this requires centralized infrastructure 00:06:20.120 --> 00:06:22.460 align:start position:0% this requires centralized infrastructure most<00:06:21.120> of<00:06:21.270> compute<00:06:21.780> today<00:06:22.020> is<00:06:22.080> done<00:06:22.289> in<00:06:22.380> the 00:06:22.460 --> 00:06:22.470 align:start position:0% most of compute today is done in the 00:06:22.470 --> 00:06:24.500 align:start position:0% most of compute today is done in the cloud<00:06:22.710> and<00:06:23.070> with<00:06:23.580> layer<00:06:23.760> two<00:06:23.970> solutions 00:06:24.500 --> 00:06:24.510 align:start position:0% cloud and with layer two solutions 00:06:24.510 --> 00:06:26.210 align:start position:0% cloud and with layer two solutions solving<00:06:25.139> some<00:06:25.349> of<00:06:25.380> the<00:06:25.590> scalability 00:06:26.210 --> 00:06:26.220 align:start position:0% solving some of the scalability 00:06:26.220 --> 00:06:28.760 align:start position:0% solving some of the scalability bottlenecks<00:06:27.000> bottlenecks<00:06:27.870> for<00:06:28.289> blockchain 00:06:28.760 --> 00:06:28.770 align:start position:0% bottlenecks bottlenecks for blockchain 00:06:28.770 --> 00:06:29.960 align:start position:0% bottlenecks bottlenecks for blockchain we're<00:06:29.370> going<00:06:29.490> to<00:06:29.550> have<00:06:29.669> more<00:06:29.789> and<00:06:29.880> more 00:06:29.960 --> 00:06:29.970 align:start position:0% we're going to have more and more 00:06:29.970 --> 00:06:32.600 align:start position:0% we're going to have more and more applications<00:06:30.539> for<00:06:30.630> blog<00:06:30.900> chains<00:06:31.490> but<00:06:32.490> as<00:06:32.580> a 00:06:32.600 --> 00:06:32.610 align:start position:0% applications for blog chains but as a 00:06:32.610 --> 00:06:35.029 align:start position:0% applications for blog chains but as a general<00:06:33.030> principle<00:06:33.360> of<00:06:33.990> decentralization<00:06:34.740> we 00:06:35.029 --> 00:06:35.039 align:start position:0% general principle of decentralization we 00:06:35.039 --> 00:06:37.250 align:start position:0% general principle of decentralization we should<00:06:35.250> be<00:06:35.340> moving<00:06:35.699> as<00:06:35.820> much<00:06:36.090> compute<00:06:37.080> as 00:06:37.250 --> 00:06:37.260 align:start position:0% should be moving as much compute as 00:06:37.260 --> 00:06:39.230 align:start position:0% should be moving as much compute as possible<00:06:37.860> to<00:06:37.979> the<00:06:38.099> edges<00:06:38.460> and<00:06:38.909> that<00:06:39.060> means 00:06:39.230 --> 00:06:39.240 align:start position:0% possible to the edges and that means 00:06:39.240 --> 00:06:42.080 align:start position:0% possible to the edges and that means doing<00:06:39.479> more<00:06:39.599> work<00:06:39.930> in<00:06:40.200> the<00:06:40.320> browser<00:06:40.940> now<00:06:41.940> we're 00:06:42.080 --> 00:06:42.090 align:start position:0% doing more work in the browser now we're 00:06:42.090 --> 00:06:43.670 align:start position:0% doing more work in the browser now we're also<00:06:42.240> going<00:06:42.570> to<00:06:42.659> need<00:06:42.810> to<00:06:42.960> have<00:06:43.110> long-running 00:06:43.670 --> 00:06:43.680 align:start position:0% also going to need to have long-running 00:06:43.680 --> 00:06:45.260 align:start position:0% also going to need to have long-running processes<00:06:44.370> so<00:06:44.580> that<00:06:44.760> for<00:06:44.909> example 00:06:45.260 --> 00:06:45.270 align:start position:0% processes so that for example 00:06:45.270 --> 00:06:47.180 align:start position:0% processes so that for example if<00:06:45.390> we<00:06:45.510> wanted<00:06:45.750> to<00:06:45.810> index<00:06:46.260> our<00:06:46.500> documents<00:06:47.070> so 00:06:47.180 --> 00:06:47.190 align:start position:0% if we wanted to index our documents so 00:06:47.190 --> 00:06:48.890 align:start position:0% if we wanted to index our documents so we<00:06:47.220> could<00:06:47.430> search<00:06:47.640> them<00:06:47.940> we'd<00:06:48.510> have<00:06:48.690> to<00:06:48.810> do 00:06:48.890 --> 00:06:48.900 align:start position:0% we could search them we'd have to do 00:06:48.900 --> 00:06:51.050 align:start position:0% we could search them we'd have to do that<00:06:49.050> outside<00:06:49.260> of<00:06:49.560> the<00:06:49.680> browser<00:06:49.890> and<00:06:50.250> we<00:06:50.310> can 00:06:51.050 --> 00:06:51.060 align:start position:0% that outside of the browser and we can 00:06:51.060 --> 00:06:53.180 align:start position:0% that outside of the browser and we can adapt<00:06:51.360> technologies<00:06:52.170> from<00:06:52.440> the<00:06:52.530> cloud<00:06:52.860> like 00:06:53.180 --> 00:06:53.190 align:start position:0% adapt technologies from the cloud like 00:06:53.190 --> 00:06:55.460 align:start position:0% adapt technologies from the cloud like function<00:06:53.670> as<00:06:53.790> a<00:06:53.820> service<00:06:54.300> which<00:06:55.020> has<00:06:55.200> great 00:06:55.460 --> 00:06:55.470 align:start position:0% function as a service which has great 00:06:55.470 --> 00:06:57.590 align:start position:0% function as a service which has great scaling<00:06:56.010> characteristics<00:06:56.760> but<00:06:57.480> the 00:06:57.590 --> 00:06:57.600 align:start position:0% scaling characteristics but the 00:06:57.600 --> 00:06:58.820 align:start position:0% scaling characteristics but the challenge<00:06:57.930> is<00:06:58.020> to<00:06:58.140> make<00:06:58.290> that<00:06:58.410> work<00:06:58.590> in<00:06:58.620> a 00:06:58.820 --> 00:06:58.830 align:start position:0% challenge is to make that work in a 00:06:58.830 --> 00:07:00.770 align:start position:0% challenge is to make that work in a peer-to-peer<00:06:59.070> environment<00:06:59.940> and<00:07:00.090> to<00:07:00.450> make<00:07:00.600> it 00:07:00.770 --> 00:07:00.780 align:start position:0% peer-to-peer environment and to make it 00:07:00.780 --> 00:07:03.740 align:start position:0% peer-to-peer environment and to make it as<00:07:01.140> secure<00:07:01.560> as<00:07:01.800> possible<00:07:01.860> and<00:07:02.700> then<00:07:03.300> finally 00:07:03.740 --> 00:07:03.750 align:start position:0% as secure as possible and then finally 00:07:03.750 --> 00:07:07.280 align:start position:0% as secure as possible and then finally identity<00:07:04.380> there<00:07:05.310> are<00:07:05.400> many<00:07:05.550> places<00:07:06.540> and<00:07:07.050> times 00:07:07.280 --> 00:07:07.290 align:start position:0% identity there are many places and times 00:07:07.290 --> 00:07:09.410 align:start position:0% identity there are many places and times where<00:07:07.620> anonymity<00:07:08.250> is<00:07:08.520> really<00:07:08.820> important<00:07:09.300> to 00:07:09.410 --> 00:07:09.420 align:start position:0% where anonymity is really important to 00:07:09.420 --> 00:07:12.110 align:start position:0% where anonymity is really important to us<00:07:09.570> but<00:07:10.410> we're<00:07:10.560> social<00:07:10.920> beings<00:07:10.950> and<00:07:11.640> so<00:07:12.000> we 00:07:12.110 --> 00:07:12.120 align:start position:0% us but we're social beings and so we 00:07:12.120 --> 00:07:13.550 align:start position:0% us but we're social beings and so we need<00:07:12.240> a<00:07:12.270> mechanism<00:07:12.570> to<00:07:12.990> represent<00:07:13.410> our 00:07:13.550 --> 00:07:13.560 align:start position:0% need a mechanism to represent our 00:07:13.560 --> 00:07:16.040 align:start position:0% need a mechanism to represent our identity<00:07:14.190> and<00:07:14.520> the<00:07:14.910> identity<00:07:15.480> of<00:07:15.720> the 00:07:16.040 --> 00:07:16.050 align:start position:0% identity and the identity of the 00:07:16.050 --> 00:07:18.160 align:start position:0% identity and the identity of the services<00:07:16.770> that<00:07:16.830> we<00:07:17.070> interact<00:07:17.490> with<00:07:17.880> online 00:07:18.160 --> 00:07:18.170 align:start position:0% services that we interact with online 00:07:18.170 --> 00:07:20.480 align:start position:0% services that we interact with online there<00:07:19.170> were<00:07:19.200> hundreds<00:07:19.740> of<00:07:19.950> identity 00:07:20.480 --> 00:07:20.490 align:start position:0% there were hundreds of identity 00:07:20.490 --> 00:07:22.970 align:start position:0% there were hundreds of identity providers<00:07:20.970> today<00:07:21.150> and<00:07:21.660> some<00:07:22.410> people<00:07:22.710> use 00:07:22.970 --> 00:07:22.980 align:start position:0% providers today and some people use 00:07:22.980 --> 00:07:25.700 align:start position:0% providers today and some people use single<00:07:23.550> sign-on<00:07:23.820> as<00:07:24.120> a<00:07:24.150> convenience<00:07:24.840> to<00:07:25.170> login 00:07:25.700 --> 00:07:25.710 align:start position:0% single sign-on as a convenience to login 00:07:25.710 --> 00:07:27.740 align:start position:0% single sign-on as a convenience to login to<00:07:25.890> all<00:07:26.130> of<00:07:26.220> these<00:07:26.340> different<00:07:26.730> services<00:07:26.910> but 00:07:27.740 --> 00:07:27.750 align:start position:0% to all of these different services but 00:07:27.750 --> 00:07:30.110 align:start position:0% to all of these different services but there's<00:07:27.930> a<00:07:27.990> danger<00:07:28.170> there<00:07:28.590> at<00:07:29.370> any<00:07:29.520> point<00:07:29.850> that 00:07:30.110 --> 00:07:30.120 align:start position:0% there's a danger there at any point that 00:07:30.120 --> 00:07:31.700 align:start position:0% there's a danger there at any point that service<00:07:30.570> provider<00:07:30.900> could<00:07:31.080> switch<00:07:31.380> off<00:07:31.560> our 00:07:31.700 --> 00:07:31.710 align:start position:0% service provider could switch off our 00:07:31.710 --> 00:07:34.850 align:start position:0% service provider could switch off our identity<00:07:32.280> without<00:07:32.430> any<00:07:32.700> course<00:07:33.420> of<00:07:33.690> or<00:07:34.110> repeal 00:07:34.850 --> 00:07:34.860 align:start position:0% identity without any course of or repeal 00:07:34.860 --> 00:07:38.120 align:start position:0% identity without any course of or repeal and<00:07:35.930> they<00:07:36.930> can<00:07:37.080> track<00:07:37.320> our<00:07:37.470> movements<00:07:37.950> across 00:07:38.120 --> 00:07:38.130 align:start position:0% and they can track our movements across 00:07:38.130 --> 00:07:41.870 align:start position:0% and they can track our movements across the<00:07:38.400> web<00:07:38.580> so<00:07:39.570> we<00:07:39.600> have<00:07:39.780> standards<00:07:40.380> like<00:07:40.880> self 00:07:41.870 --> 00:07:41.880 align:start position:0% the web so we have standards like self 00:07:41.880 --> 00:07:43.460 align:start position:0% the web so we have standards like self sovereign<00:07:42.180> identity<00:07:42.690> and<00:07:42.960> verifiable 00:07:43.460 --> 00:07:43.470 align:start position:0% sovereign identity and verifiable 00:07:43.470 --> 00:07:45.890 align:start position:0% sovereign identity and verifiable credentials<00:07:44.070> where<00:07:44.880> users<00:07:45.360> can<00:07:45.600> control 00:07:45.890 --> 00:07:45.900 align:start position:0% credentials where users can control 00:07:45.900 --> 00:07:47.600 align:start position:0% credentials where users can control their<00:07:46.140> identity<00:07:46.620> with<00:07:46.770> public<00:07:47.130> private<00:07:47.310> key 00:07:47.600 --> 00:07:47.610 align:start position:0% their identity with public private key 00:07:47.610 --> 00:07:49.760 align:start position:0% their identity with public private key pairs<00:07:47.880> but<00:07:48.780> even<00:07:48.990> if<00:07:49.080> you're<00:07:49.200> an<00:07:49.290> expert<00:07:49.710> in 00:07:49.760 --> 00:07:49.770 align:start position:0% pairs but even if you're an expert in 00:07:49.770 --> 00:07:51.770 align:start position:0% pairs but even if you're an expert in this<00:07:50.010> technology<00:07:50.400> it<00:07:51.090> still<00:07:51.450> really 00:07:51.770 --> 00:07:51.780 align:start position:0% this technology it still really 00:07:51.780 --> 00:07:53.840 align:start position:0% this technology it still really cumbersome<00:07:52.440> to<00:07:52.620> use<00:07:52.830> to<00:07:53.040> do<00:07:53.160> things<00:07:53.370> like<00:07:53.610> key 00:07:53.840 --> 00:07:53.850 align:start position:0% cumbersome to use to do things like key 00:07:53.850 --> 00:07:57.790 align:start position:0% cumbersome to use to do things like key management<00:07:54.210> key<00:07:54.960> rotation<00:07:55.620> and<00:07:55.770> key<00:07:55.890> recovery 00:07:57.790 --> 00:07:57.800 align:start position:0% management key rotation and key recovery 00:07:57.800 --> 00:07:59.900 align:start position:0% management key rotation and key recovery we<00:07:58.800> think<00:07:59.010> the<00:07:59.100> solution<00:07:59.520> is<00:07:59.640> going<00:07:59.700> to<00:07:59.790> be<00:07:59.850> a 00:07:59.900 --> 00:07:59.910 align:start position:0% we think the solution is going to be a 00:07:59.910 --> 00:08:02.030 align:start position:0% we think the solution is going to be a hybrid<00:08:00.180> of<00:08:00.480> different<00:08:00.870> technologies<00:08:01.440> so<00:08:01.890> the 00:08:02.030 --> 00:08:02.040 align:start position:0% hybrid of different technologies so the 00:08:02.040 --> 00:08:04.280 align:start position:0% hybrid of different technologies so the cloud<00:08:02.250> isn't<00:08:02.490> going<00:08:02.700> to<00:08:02.760> go<00:08:02.880> away<00:08:03.150> it's<00:08:03.870> a<00:08:04.020> good 00:08:04.280 --> 00:08:04.290 align:start position:0% cloud isn't going to go away it's a good 00:08:04.290 --> 00:08:07.340 align:start position:0% cloud isn't going to go away it's a good cheap<00:08:04.740> resource<00:08:05.340> for<00:08:05.990> high<00:08:06.990> scale 00:08:07.340 --> 00:08:07.350 align:start position:0% cheap resource for high scale 00:08:07.350 --> 00:08:10.520 align:start position:0% cheap resource for high scale computation<00:08:08.310> and<00:08:08.910> storage<00:08:09.290> we're<00:08:10.290> gonna<00:08:10.380> have 00:08:10.520 --> 00:08:10.530 align:start position:0% computation and storage we're gonna have 00:08:10.530 --> 00:08:12.350 align:start position:0% computation and storage we're gonna have more<00:08:10.740> and<00:08:10.800> more<00:08:11.040> use<00:08:11.250> cases<00:08:11.370> for<00:08:11.880> blockchain 00:08:12.350 --> 00:08:12.360 align:start position:0% more and more use cases for blockchain 00:08:12.360 --> 00:08:13.700 align:start position:0% more and more use cases for blockchain especially<00:08:12.930> with<00:08:13.050> innovations<00:08:13.590> like 00:08:13.700 --> 00:08:13.710 align:start position:0% especially with innovations like 00:08:13.710 --> 00:08:16.070 align:start position:0% especially with innovations like aetherium<00:08:14.040> 2.0<00:08:14.760> but<00:08:15.510> what<00:08:15.660> we've<00:08:15.870> been 00:08:16.070 --> 00:08:16.080 align:start position:0% aetherium 2.0 but what we've been 00:08:16.080 --> 00:08:18.650 align:start position:0% aetherium 2.0 but what we've been focusing<00:08:16.590> on<00:08:16.740> is<00:08:17.070> the<00:08:17.280> missing<00:08:17.700> middle<00:08:18.390> tier 00:08:18.650 --> 00:08:18.660 align:start position:0% focusing on is the missing middle tier 00:08:18.660 --> 00:08:20.660 align:start position:0% focusing on is the missing middle tier the<00:08:18.900> peer-to-peer<00:08:19.230> tier<00:08:19.920> and<00:08:20.130> that's<00:08:20.520> what 00:08:20.660 --> 00:08:20.670 align:start position:0% the peer-to-peer tier and that's what 00:08:20.670 --> 00:08:23.030 align:start position:0% the peer-to-peer tier and that's what we're<00:08:20.790> going<00:08:20.910> to<00:08:20.970> demo<00:08:21.150> this<00:08:21.390> morning<00:08:22.040> but 00:08:23.030 --> 00:08:23.040 align:start position:0% we're going to demo this morning but 00:08:23.040 --> 00:08:24.680 align:start position:0% we're going to demo this morning but suppose<00:08:23.610> we<00:08:23.640> could<00:08:23.910> solve<00:08:24.150> all<00:08:24.420> of<00:08:24.480> these 00:08:24.680 --> 00:08:24.690 align:start position:0% suppose we could solve all of these 00:08:24.690 --> 00:08:27.590 align:start position:0% suppose we could solve all of these technical<00:08:25.200> problems<00:08:25.820> unless<00:08:26.820> we<00:08:27.210> can<00:08:27.360> deliver 00:08:27.590 --> 00:08:27.600 align:start position:0% technical problems unless we can deliver 00:08:27.600 --> 00:08:30.320 align:start position:0% technical problems unless we can deliver user<00:08:27.990> experiences<00:08:28.890> that<00:08:29.100> are<00:08:29.250> as<00:08:29.520> good<00:08:29.760> as<00:08:29.820> or 00:08:30.320 --> 00:08:30.330 align:start position:0% user experiences that are as good as or 00:08:30.330 --> 00:08:32.110 align:start position:0% user experiences that are as good as or better<00:08:30.600> than<00:08:30.810> the<00:08:31.170> existing<00:08:31.710> cloud 00:08:32.110 --> 00:08:32.120 align:start position:0% better than the existing cloud 00:08:32.120 --> 00:08:34.580 align:start position:0% better than the existing cloud technologies<00:08:33.120> today<00:08:33.330> we're<00:08:34.020> not<00:08:34.200> going<00:08:34.470> to 00:08:34.580 --> 00:08:34.590 align:start position:0% technologies today we're not going to 00:08:34.590 --> 00:08:37.460 align:start position:0% technologies today we're not going to see<00:08:34.880> widespread<00:08:35.880> adoption<00:08:36.000> of<00:08:36.810> decentralized 00:08:37.460 --> 00:08:37.470 align:start position:0% see widespread adoption of decentralized 00:08:37.470 --> 00:08:38.960 align:start position:0% see widespread adoption of decentralized technology<00:08:37.620> so<00:08:38.220> that's<00:08:38.400> something<00:08:38.820> that 00:08:38.960 --> 00:08:38.970 align:start position:0% technology so that's something that 00:08:38.970 --> 00:08:41.570 align:start position:0% technology so that's something that we're<00:08:39.120> going<00:08:39.270> to<00:08:39.390> show<00:08:40.350> in<00:08:40.710> the<00:08:41.280> demo<00:08:41.550> that 00:08:41.570 --> 00:08:41.580 align:start position:0% we're going to show in the demo that 00:08:41.580 --> 00:08:48.140 align:start position:0% we're going to show in the demo that we're<00:08:41.820> going<00:08:41.910> to<00:08:42.000> do<00:08:42.150> next<00:08:46.760> so<00:08:47.760> this<00:08:47.910> is<00:08:48.030> an 00:08:48.140 --> 00:08:48.150 align:start position:0% we're going to do next so this is an 00:08:48.150 --> 00:08:49.670 align:start position:0% we're going to do next so this is an application<00:08:48.690> we<00:08:48.780> built<00:08:49.020> on<00:08:49.230> the<00:08:49.350> wireline 00:08:49.670 --> 00:08:49.680 align:start position:0% application we built on the wireline 00:08:49.680 --> 00:08:53.030 align:start position:0% application we built on the wireline platform<00:08:50.280> it's<00:08:50.430> called<00:08:50.610> Launchpad<00:08:51.350> it's<00:08:52.350> kind 00:08:53.030 --> 00:08:53.040 align:start position:0% platform it's called Launchpad it's kind 00:08:53.040 --> 00:08:53.600 align:start position:0% platform it's called Launchpad it's kind of<00:08:53.070> like<00:08:53.220> an<00:08:53.340> app's 00:08:53.600 --> 00:08:53.610 align:start position:0% of like an app's 00:08:53.610 --> 00:08:55.610 align:start position:0% of like an app's App<00:08:53.820> Store<00:08:54.240> or<00:08:54.270> home<00:08:54.720> screen<00:08:55.110> it's<00:08:55.320> a<00:08:55.410> place 00:08:55.610 --> 00:08:55.620 align:start position:0% App Store or home screen it's a place 00:08:55.620 --> 00:08:58.100 align:start position:0% App Store or home screen it's a place where<00:08:56.010> users<00:08:56.640> can<00:08:56.850> discover<00:08:57.030> a<00:08:57.450> search<00:08:57.780> and 00:08:58.100 --> 00:08:58.110 align:start position:0% where users can discover a search and 00:08:58.110 --> 00:09:00.830 align:start position:0% where users can discover a search and install<00:08:58.730> peer-to-peer<00:08:59.730> applications<00:09:00.120> that 00:09:00.830 --> 00:09:00.840 align:start position:0% install peer-to-peer applications that 00:09:00.840 --> 00:09:02.240 align:start position:0% install peer-to-peer applications that don't<00:09:00.990> require<00:09:01.320> any<00:09:01.620> centralized 00:09:02.240 --> 00:09:02.250 align:start position:0% don't require any centralized 00:09:02.250 --> 00:09:05.180 align:start position:0% don't require any centralized infrastructure<00:09:03.120> it<00:09:03.720> uses<00:09:04.140> the<00:09:04.320> Y<00:09:04.530> line<00:09:04.770> naming 00:09:05.180 --> 00:09:05.190 align:start position:0% infrastructure it uses the Y line naming 00:09:05.190 --> 00:09:07.100 align:start position:0% infrastructure it uses the Y line naming service<00:09:05.670> which<00:09:06.420> is<00:09:06.570> a<00:09:06.600> permissionless 00:09:07.100 --> 00:09:07.110 align:start position:0% service which is a permissionless 00:09:07.110 --> 00:09:09.290 align:start position:0% service which is a permissionless blockchain<00:09:07.770> that<00:09:08.310> lets<00:09:08.490> any<00:09:08.700> developer 00:09:09.290 --> 00:09:09.300 align:start position:0% blockchain that lets any developer 00:09:09.300 --> 00:09:11.240 align:start position:0% blockchain that lets any developer publish<00:09:09.750> an<00:09:09.870> application<00:09:10.020> without<00:09:10.920> any 00:09:11.240 --> 00:09:11.250 align:start position:0% publish an application without any 00:09:11.250 --> 00:09:13.010 align:start position:0% publish an application without any censorship<00:09:11.670> without<00:09:12.120> any<00:09:12.270> taxes<00:09:12.870> or<00:09:12.990> other 00:09:13.010 --> 00:09:13.020 align:start position:0% censorship without any taxes or other 00:09:13.020 --> 00:09:16.220 align:start position:0% censorship without any taxes or other restrictions<00:09:13.800> placed<00:09:14.400> by<00:09:14.850> the<00:09:14.910> platform<00:09:15.510> so 00:09:16.220 --> 00:09:16.230 align:start position:0% restrictions placed by the platform so 00:09:16.230 --> 00:09:17.960 align:start position:0% restrictions placed by the platform so I'm<00:09:16.290> going<00:09:16.410> to<00:09:16.440> show<00:09:16.590> a<00:09:16.620> couple<00:09:16.800> of<00:09:17.010> example 00:09:17.960 --> 00:09:17.970 align:start position:0% I'm going to show a couple of example 00:09:17.970 --> 00:09:19.490 align:start position:0% I'm going to show a couple of example applications<00:09:18.540> that<00:09:18.750> have<00:09:18.840> been<00:09:18.990> built<00:09:19.230> on<00:09:19.410> the 00:09:19.490 --> 00:09:19.500 align:start position:0% applications that have been built on the 00:09:19.500 --> 00:09:22.340 align:start position:0% applications that have been built on the platform<00:09:19.890> already<00:09:20.210> so<00:09:21.210> we<00:09:21.360> have<00:09:21.540> simple 00:09:22.340 --> 00:09:22.350 align:start position:0% platform already so we have simple 00:09:22.350 --> 00:09:24.800 align:start position:0% platform already so we have simple collaborative<00:09:22.920> calendars<00:09:23.810> spreadsheet 00:09:24.800 --> 00:09:24.810 align:start position:0% collaborative calendars spreadsheet 00:09:24.810 --> 00:09:27.530 align:start position:0% collaborative calendars spreadsheet there's<00:09:25.770> a<00:09:25.860> planning<00:09:26.280> tool<00:09:26.490> which<00:09:26.790> is<00:09:26.940> a<00:09:26.970> kind 00:09:27.530 --> 00:09:27.540 align:start position:0% there's a planning tool which is a kind 00:09:27.540 --> 00:09:30.290 align:start position:0% there's a planning tool which is a kind of<00:09:27.660> Kanban<00:09:28.110> and<00:09:28.380> even<00:09:29.370> the<00:09:29.460> slides<00:09:29.760> that<00:09:29.970> I<00:09:30.090> was 00:09:30.290 --> 00:09:30.300 align:start position:0% of Kanban and even the slides that I was 00:09:30.300 --> 00:09:32.810 align:start position:0% of Kanban and even the slides that I was presenting<00:09:30.900> were<00:09:31.350> written<00:09:31.860> with<00:09:32.220> an 00:09:32.810 --> 00:09:32.820 align:start position:0% presenting were written with an 00:09:32.820 --> 00:09:34.310 align:start position:0% presenting were written with an application<00:09:33.600> that<00:09:33.720> was<00:09:33.810> built<00:09:34.050> on<00:09:34.170> this 00:09:34.310 --> 00:09:34.320 align:start position:0% application that was built on this 00:09:34.320 --> 00:09:36.260 align:start position:0% application that was built on this platform<00:09:34.560> so<00:09:34.890> we're<00:09:35.670> eating<00:09:35.970> our<00:09:36.120> own<00:09:36.150> dog 00:09:36.260 --> 00:09:36.270 align:start position:0% platform so we're eating our own dog 00:09:36.270 --> 00:09:39.470 align:start position:0% platform so we're eating our own dog food<00:09:36.740> we've<00:09:37.740> also<00:09:37.890> got<00:09:38.160> a<00:09:38.190> map<00:09:38.730> application 00:09:39.470 --> 00:09:39.480 align:start position:0% food we've also got a map application 00:09:39.480 --> 00:09:43.970 align:start position:0% food we've also got a map application and<00:09:41.240> I'm<00:09:42.240> gonna<00:09:42.510> create<00:09:42.780> here<00:09:43.200> a<00:09:43.230> simple<00:09:43.740> text 00:09:43.970 --> 00:09:43.980 align:start position:0% and I'm gonna create here a simple text 00:09:43.980 --> 00:09:50.390 align:start position:0% and I'm gonna create here a simple text document<00:09:47.570> and<00:09:48.570> as<00:09:49.560> I<00:09:49.710> mentioned<00:09:50.040> earlier<00:09:50.280> one 00:09:50.390 --> 00:09:50.400 align:start position:0% document and as I mentioned earlier one 00:09:50.400 --> 00:09:52.250 align:start position:0% document and as I mentioned earlier one of<00:09:50.430> the<00:09:50.550> most<00:09:50.790> difficult<00:09:51.270> things<00:09:51.540> to<00:09:51.690> do<00:09:51.930> with 00:09:52.250 --> 00:09:52.260 align:start position:0% of the most difficult things to do with 00:09:52.260 --> 00:09:53.990 align:start position:0% of the most difficult things to do with collaborative<00:09:52.980> applications<00:09:53.610> is<00:09:53.970> the 00:09:53.990 --> 00:09:54.000 align:start position:0% collaborative applications is the 00:09:54.000 --> 00:09:55.760 align:start position:0% collaborative applications is the real-time<00:09:54.630> interaction<00:09:55.260> between<00:09:55.590> different 00:09:55.760 --> 00:09:55.770 align:start position:0% real-time interaction between different 00:09:55.770 --> 00:09:58.190 align:start position:0% real-time interaction between different users<00:09:56.520> especially<00:09:57.420> when<00:09:57.540> you<00:09:57.660> don't<00:09:57.810> have<00:09:58.050> any 00:09:58.190 --> 00:09:58.200 align:start position:0% users especially when you don't have any 00:09:58.200 --> 00:10:00.080 align:start position:0% users especially when you don't have any cloud<00:09:58.440> infrastructure<00:09:59.040> so<00:09:59.760> what<00:09:59.910> I'm<00:10:00.000> going 00:10:00.080 --> 00:10:00.090 align:start position:0% cloud infrastructure so what I'm going 00:10:00.090 --> 00:10:01.790 align:start position:0% cloud infrastructure so what I'm going to<00:10:00.150> do<00:10:00.300> here<00:10:00.720> is<00:10:00.930> invite<00:10:01.320> some<00:10:01.650> of<00:10:01.680> my 00:10:01.790 --> 00:10:01.800 align:start position:0% to do here is invite some of my 00:10:01.800 --> 00:10:03.800 align:start position:0% to do here is invite some of my colleagues<00:10:02.310> who<00:10:02.670> are<00:10:02.700> here<00:10:03.150> on<00:10:03.270> the<00:10:03.360> front<00:10:03.600> row 00:10:03.800 --> 00:10:03.810 align:start position:0% colleagues who are here on the front row 00:10:03.810 --> 00:10:07.010 align:start position:0% colleagues who are here on the front row to<00:10:04.590> join<00:10:04.920> me<00:10:05.220> in<00:10:05.460> editing<00:10:06.180> this<00:10:06.300> document<00:10:06.870> so 00:10:07.010 --> 00:10:07.020 align:start position:0% to join me in editing this document so 00:10:07.020 --> 00:10:11.590 align:start position:0% to join me in editing this document so I'm<00:10:07.110> going<00:10:07.380> to<00:10:07.670> send<00:10:08.670> them<00:10:08.820> an<00:10:08.970> invite<00:10:09.360> and 00:10:11.590 --> 00:10:11.600 align:start position:0% I'm going to send them an invite and 00:10:11.600 --> 00:10:14.780 align:start position:0% I'm going to send them an invite and they<00:10:12.600> that<00:10:12.930> should<00:10:13.110> enable<00:10:13.350> their<00:10:13.740> peers<00:10:14.310> to 00:10:14.780 --> 00:10:14.790 align:start position:0% they that should enable their peers to 00:10:14.790 --> 00:10:17.810 align:start position:0% they that should enable their peers to swarm<00:10:15.180> and<00:10:15.480> connect<00:10:15.870> to<00:10:16.080> my<00:10:16.350> peer<00:10:17.160> on<00:10:17.370> on<00:10:17.580> the 00:10:17.810 --> 00:10:17.820 align:start position:0% swarm and connect to my peer on on the 00:10:17.820 --> 00:10:19.370 align:start position:0% swarm and connect to my peer on on the stage<00:10:18.000> here<00:10:18.420> and<00:10:18.600> we<00:10:18.870> can<00:10:19.020> collaboratively 00:10:19.370 --> 00:10:19.380 align:start position:0% stage here and we can collaboratively 00:10:19.380 --> 00:10:22.010 align:start position:0% stage here and we can collaboratively edit<00:10:19.920> the<00:10:20.010> document<00:10:20.520> so<00:10:21.090> I'll<00:10:21.360> just<00:10:21.570> demo 00:10:22.010 --> 00:10:22.020 align:start position:0% edit the document so I'll just demo 00:10:22.020 --> 00:10:23.510 align:start position:0% edit the document so I'll just demo first<00:10:22.410> of<00:10:22.620> all<00:10:22.740> that<00:10:22.950> we're<00:10:23.130> completely 00:10:23.510 --> 00:10:23.520 align:start position:0% first of all that we're completely 00:10:23.520 --> 00:10:25.730 align:start position:0% first of all that we're completely offline<00:10:23.820> here<00:10:24.300> if<00:10:24.420> I<00:10:24.540> do<00:10:24.600> a<00:10:24.690> web<00:10:25.140> search<00:10:25.200> it's 00:10:25.730 --> 00:10:25.740 align:start position:0% offline here if I do a web search it's 00:10:25.740 --> 00:10:28.040 align:start position:0% offline here if I do a web search it's not<00:10:25.950> going<00:10:26.130> to<00:10:26.190> get<00:10:26.310> resolved<00:10:26.820> and<00:10:27.030> I<00:10:27.840> should 00:10:28.040 --> 00:10:28.050 align:start position:0% not going to get resolved and I should 00:10:28.050 --> 00:10:31.550 align:start position:0% not going to get resolved and I should see<00:10:28.230> if<00:10:28.260> I<00:10:28.410> open<00:10:28.650> the<00:10:28.740> debug<00:10:28.890> panel<00:10:29.250> the<00:10:30.560> Salar 00:10:31.550 --> 00:10:31.560 align:start position:0% see if I open the debug panel the Salar 00:10:31.560 --> 00:10:34.310 align:start position:0% see if I open the debug panel the Salar and<00:10:31.890> ashwin<00:10:32.250> have<00:10:32.430> joined<00:10:32.790> this<00:10:33.480> what<00:10:34.050> we<00:10:34.170> call 00:10:34.310 --> 00:10:34.320 align:start position:0% and ashwin have joined this what we call 00:10:34.320 --> 00:10:36.230 align:start position:0% and ashwin have joined this what we call a<00:10:34.350> party<00:10:34.860> this<00:10:35.100> is<00:10:35.250> a<00:10:35.280> collaborative<00:10:35.970> space 00:10:36.230 --> 00:10:36.240 align:start position:0% a party this is a collaborative space 00:10:36.240 --> 00:10:39.680 align:start position:0% a party this is a collaborative space where<00:10:36.510> these<00:10:36.630> documents<00:10:37.230> live<00:10:37.440> and<00:10:38.540> we<00:10:39.540> can 00:10:39.680 --> 00:10:39.690 align:start position:0% where these documents live and we can 00:10:39.690 --> 00:10:42.230 align:start position:0% where these documents live and we can see<00:10:39.870> that<00:10:40.050> they're<00:10:40.460> typing<00:10:41.460> along<00:10:41.670> I<00:10:41.880> can<00:10:41.940> type 00:10:42.230 --> 00:10:42.240 align:start position:0% see that they're typing along I can type 00:10:42.240 --> 00:10:48.680 align:start position:0% see that they're typing along I can type at<00:10:42.390> the<00:10:42.450> same<00:10:42.660> time<00:10:43.400> this<00:10:46.700> and<00:10:47.700> so<00:10:48.360> we've<00:10:48.510> got 00:10:48.680 --> 00:10:48.690 align:start position:0% at the same time this and so we've got 00:10:48.690 --> 00:10:50.540 align:start position:0% at the same time this and so we've got this<00:10:48.810> technology<00:10:49.500> now<00:10:49.680> like<00:10:49.920> operational 00:10:50.540 --> 00:10:50.550 align:start position:0% this technology now like operational 00:10:50.550 --> 00:10:52.610 align:start position:0% this technology now like operational transformations<00:10:51.330> where<00:10:51.720> we<00:10:51.840> can<00:10:52.050> collaborate 00:10:52.610 --> 00:10:52.620 align:start position:0% transformations where we can collaborate 00:10:52.620 --> 00:10:54.410 align:start position:0% transformations where we can collaborate in<00:10:52.920> real<00:10:53.100> time<00:10:53.400> across<00:10:53.790> all<00:10:54.120> of<00:10:54.300> these 00:10:54.410 --> 00:10:54.420 align:start position:0% in real time across all of these 00:10:54.420 --> 00:10:56.270 align:start position:0% in real time across all of these different<00:10:54.810> applications<00:10:54.900> it<00:10:55.890> uses<00:10:56.250> a 00:10:56.270 --> 00:10:56.280 align:start position:0% different applications it uses a 00:10:56.280 --> 00:10:57.290 align:start position:0% different applications it uses a technology<00:10:56.910> called 00:10:57.290 --> 00:10:57.300 align:start position:0% technology called 00:10:57.300 --> 00:10:59.740 align:start position:0% technology called CR<00:10:57.900> DT<00:10:58.320> which<00:10:58.830> is<00:10:58.860> a<00:10:58.980> very<00:10:59.280> early-stage 00:10:59.740 --> 00:10:59.750 align:start position:0% CR DT which is a very early-stage 00:10:59.750 --> 00:11:02.300 align:start position:0% CR DT which is a very early-stage experimental<00:11:00.750> technology<00:11:01.320> that<00:11:01.530> has<00:11:01.710> some 00:11:02.300 --> 00:11:02.310 align:start position:0% experimental technology that has some 00:11:02.310 --> 00:11:04.700 align:start position:0% experimental technology that has some limitations<00:11:02.850> in<00:11:03.060> terms<00:11:03.090> of<00:11:03.480> scale<00:11:03.780> but<00:11:04.560> we're 00:11:04.700 --> 00:11:04.710 align:start position:0% limitations in terms of scale but we're 00:11:04.710 --> 00:11:06.230 align:start position:0% limitations in terms of scale but we're working<00:11:04.890> to<00:11:05.190> improve<00:11:05.460> some<00:11:05.790> of<00:11:05.880> those<00:11:06.000> things 00:11:06.230 --> 00:11:06.240 align:start position:0% working to improve some of those things 00:11:06.240 --> 00:11:08.319 align:start position:0% working to improve some of those things you<00:11:07.080> can<00:11:07.230> see<00:11:07.410> Solara<00:11:07.830> has<00:11:08.010> been 00:11:08.319 --> 00:11:08.329 align:start position:0% you can see Solara has been 00:11:08.329 --> 00:11:12.910 align:start position:0% you can see Solara has been learning<00:11:08.540> Japanese<00:11:11.559> one<00:11:12.559> of<00:11:12.679> the<00:11:12.769> other 00:11:12.910 --> 00:11:12.920 align:start position:0% learning Japanese one of the other 00:11:12.920 --> 00:11:15.549 align:start position:0% learning Japanese one of the other properties<00:11:13.459> about<00:11:13.929> applications<00:11:14.929> on<00:11:15.199> the 00:11:15.549 --> 00:11:15.559 align:start position:0% properties about applications on the 00:11:15.559 --> 00:11:17.530 align:start position:0% properties about applications on the platform<00:11:16.279> is<00:11:16.519> that<00:11:16.670> these<00:11:16.790> applications<00:11:16.970> are 00:11:17.530 --> 00:11:17.540 align:start position:0% platform is that these applications are 00:11:17.540 --> 00:11:19.449 align:start position:0% platform is that these applications are all<00:11:17.629> modular<00:11:18.019> and<00:11:18.559> even<00:11:19.069> though<00:11:19.160> they've<00:11:19.309> been 00:11:19.449 --> 00:11:19.459 align:start position:0% all modular and even though they've been 00:11:19.459 --> 00:11:20.530 align:start position:0% all modular and even though they've been built<00:11:19.699> by<00:11:19.819> different<00:11:20.239> third-party 00:11:20.530 --> 00:11:20.540 align:start position:0% built by different third-party 00:11:20.540 --> 00:11:22.929 align:start position:0% built by different third-party developers<00:11:21.529> we<00:11:21.980> can<00:11:22.129> combine<00:11:22.369> them<00:11:22.730> together 00:11:22.929 --> 00:11:22.939 align:start position:0% developers we can combine them together 00:11:22.939 --> 00:11:25.569 align:start position:0% developers we can combine them together in<00:11:23.239> interesting<00:11:23.389> ways<00:11:23.809> so<00:11:24.799> for<00:11:25.009> example<00:11:25.399> we 00:11:25.569 --> 00:11:25.579 align:start position:0% in interesting ways so for example we 00:11:25.579 --> 00:11:27.340 align:start position:0% in interesting ways so for example we could<00:11:25.730> insert<00:11:26.059> a<00:11:26.119> spreadsheet<00:11:26.600> into<00:11:27.230> this 00:11:27.340 --> 00:11:27.350 align:start position:0% could insert a spreadsheet into this 00:11:27.350 --> 00:11:30.400 align:start position:0% could insert a spreadsheet into this document<00:11:27.920> I<00:11:28.100> see<00:11:28.670> solarz<00:11:29.029> done<00:11:29.299> that<00:11:29.480> here<00:11:29.749> and 00:11:30.400 --> 00:11:30.410 align:start position:0% document I see solarz done that here and 00:11:30.410 --> 00:11:33.489 align:start position:0% document I see solarz done that here and I<00:11:30.709> could<00:11:30.920> create<00:11:31.399> for<00:11:31.549> example<00:11:31.989> let<00:11:32.989> me<00:11:33.110> insert 00:11:33.489 --> 00:11:33.499 align:start position:0% I could create for example let me insert 00:11:33.499 --> 00:11:36.129 align:start position:0% I could create for example let me insert our<00:11:33.829> trip<00:11:34.160> mount<00:11:34.459> into<00:11:35.360> this<00:11:35.480> document<00:11:36.019> and 00:11:36.129 --> 00:11:36.139 align:start position:0% our trip mount into this document and 00:11:36.139 --> 00:11:39.369 align:start position:0% our trip mount into this document and you<00:11:36.259> can<00:11:36.290> see<00:11:36.559> this<00:11:36.679> is<00:11:36.860> live<00:11:37.720> these<00:11:38.720> different 00:11:39.369 --> 00:11:39.379 align:start position:0% you can see this is live these different 00:11:39.379 --> 00:11:41.439 align:start position:0% you can see this is live these different applications<00:11:39.499> have<00:11:40.459> access<00:11:40.999> to<00:11:41.360> this 00:11:41.439 --> 00:11:41.449 align:start position:0% applications have access to this 00:11:41.449 --> 00:11:43.900 align:start position:0% applications have access to this replicated<00:11:42.230> database<00:11:42.739> that<00:11:43.309> is<00:11:43.459> securely 00:11:43.900 --> 00:11:43.910 align:start position:0% replicated database that is securely 00:11:43.910 --> 00:11:46.210 align:start position:0% replicated database that is securely replicated<00:11:44.660> between<00:11:44.779> the<00:11:45.559> colleagues<00:11:45.949> that 00:11:46.210 --> 00:11:46.220 align:start position:0% replicated between the colleagues that 00:11:46.220 --> 00:11:48.249 align:start position:0% replicated between the colleagues that I've<00:11:46.369> invited<00:11:46.670> into<00:11:47.239> this<00:11:47.809> shared 00:11:48.249 --> 00:11:48.259 align:start position:0% I've invited into this shared 00:11:48.259 --> 00:11:50.769 align:start position:0% I've invited into this shared environment<00:11:49.059> so<00:11:50.059> at<00:11:50.179> this<00:11:50.299> point<00:11:50.509> we're<00:11:50.749> going 00:11:50.769 --> 00:11:50.779 align:start position:0% environment so at this point we're going 00:11:50.779 --> 00:11:52.629 align:start position:0% environment so at this point we're going to<00:11:50.899> change<00:11:51.139> gears<00:11:51.379> and<00:11:51.679> quickly<00:11:52.100> in<00:11:52.339> five 00:11:52.629 --> 00:11:52.639 align:start position:0% to change gears and quickly in five 00:11:52.639 --> 00:11:54.519 align:start position:0% to change gears and quickly in five minutes<00:11:53.029> build<00:11:53.389> an<00:11:53.660> application<00:11:53.809> from 00:11:54.519 --> 00:11:54.529 align:start position:0% minutes build an application from 00:11:54.529 --> 00:11:58.090 align:start position:0% minutes build an application from scratch<00:11:55.209> so<00:11:56.499> what<00:11:57.499> I'm<00:11:57.559> going<00:11:57.709> to<00:11:57.739> do<00:11:57.860> is<00:11:57.949> use 00:11:58.090 --> 00:11:58.100 align:start position:0% scratch so what I'm going to do is use 00:11:58.100 --> 00:12:00.579 align:start position:0% scratch so what I'm going to do is use the<00:11:58.249> wireline<00:11:58.579> SDK<00:11:59.119> and<00:11:59.540> I'm<00:12:00.079> going<00:12:00.230> to<00:12:00.259> fork 00:12:00.579 --> 00:12:00.589 align:start position:0% the wireline SDK and I'm going to fork 00:12:00.589 --> 00:12:04.809 align:start position:0% the wireline SDK and I'm going to fork an<00:12:00.769> existing<00:12:01.279> project<00:12:01.519> so<00:12:02.199> it's<00:12:03.279> using<00:12:04.279> the 00:12:04.809 --> 00:12:04.819 align:start position:0% an existing project so it's using the 00:12:04.819 --> 00:12:06.460 align:start position:0% an existing project so it's using the the<00:12:05.119> CLI<00:12:05.509> which<00:12:05.720> is<00:12:05.839> called<00:12:06.079> wire 00:12:06.460 --> 00:12:06.470 align:start position:0% the CLI which is called wire 00:12:06.470 --> 00:12:08.859 align:start position:0% the CLI which is called wire so<00:12:07.009> why<00:12:07.220> iPad<00:12:07.549> create<00:12:07.970> will<00:12:08.209> create<00:12:08.449> a<00:12:08.629> new 00:12:08.859 --> 00:12:08.869 align:start position:0% so why iPad create will create a new 00:12:08.869 --> 00:12:12.160 align:start position:0% so why iPad create will create a new application<00:12:09.549> I'm<00:12:10.549> going<00:12:10.819> to<00:12:10.879> open<00:12:11.059> up<00:12:11.329> the 00:12:12.160 --> 00:12:12.170 align:start position:0% application I'm going to open up the 00:12:12.170 --> 00:12:21.100 align:start position:0% application I'm going to open up the code<00:12:12.769> here<00:12:18.790> and<00:12:19.790> look<00:12:20.269> at<00:12:20.360> that<00:12:20.419> in<00:12:20.540> vs<00:12:20.809> code 00:12:21.100 --> 00:12:21.110 align:start position:0% code here and look at that in vs code 00:12:21.110 --> 00:12:24.009 align:start position:0% code here and look at that in vs code and<00:12:21.459> just<00:12:22.459> take<00:12:22.610> a<00:12:22.639> quick<00:12:22.850> look<00:12:23.119> it's<00:12:23.329> there's 00:12:24.009 --> 00:12:24.019 align:start position:0% and just take a quick look it's there's 00:12:24.019 --> 00:12:27.009 align:start position:0% and just take a quick look it's there's a<00:12:24.139> definition<00:12:24.529> style<00:12:24.949> and<00:12:25.100> there's<00:12:25.220> a<00:12:25.309> pad<00:12:26.019> the 00:12:27.009 --> 00:12:27.019 align:start position:0% a definition style and there's a pad the 00:12:27.019 --> 00:12:29.530 align:start position:0% a definition style and there's a pad the pad<00:12:27.259> is<00:12:27.529> a<00:12:27.559> simple<00:12:28.069> react<00:12:28.519> component<00:12:29.209> so<00:12:29.389> we're 00:12:29.530 --> 00:12:29.540 align:start position:0% pad is a simple react component so we're 00:12:29.540 --> 00:12:31.749 align:start position:0% pad is a simple react component so we're trying<00:12:29.660> to<00:12:29.779> make<00:12:29.929> the<00:12:30.110> SDK<00:12:30.559> as<00:12:30.769> simple<00:12:31.579> as 00:12:31.749 --> 00:12:31.759 align:start position:0% trying to make the SDK as simple as 00:12:31.759 --> 00:12:33.909 align:start position:0% trying to make the SDK as simple as possible<00:12:31.999> and<00:12:32.329> as<00:12:32.480> natural<00:12:32.899> as<00:12:32.989> possible<00:12:33.529> to 00:12:33.909 --> 00:12:33.919 align:start position:0% possible and as natural as possible to 00:12:33.919 --> 00:12:36.819 align:start position:0% possible and as natural as possible to existing<00:12:34.429> web<00:12:34.639> developers<00:12:35.239> so<00:12:36.079> what<00:12:36.739> I'm 00:12:36.819 --> 00:12:36.829 align:start position:0% existing web developers so what I'm 00:12:36.829 --> 00:12:40.479 align:start position:0% existing web developers so what I'm gonna<00:12:36.919> do<00:12:37.189> here<00:12:37.639> is<00:12:38.499> register<00:12:39.499> the<00:12:39.679> pad<00:12:39.889> with 00:12:40.479 --> 00:12:40.489 align:start position:0% gonna do here is register the pad with 00:12:40.489 --> 00:12:42.340 align:start position:0% gonna do here is register the pad with the<00:12:40.519> Waialae<00:12:40.970> naming<00:12:41.299> service<00:12:41.660> so<00:12:41.839> why<00:12:42.019> a<00:12:42.049> pad 00:12:42.340 --> 00:12:42.350 align:start position:0% the Waialae naming service so why a pad 00:12:42.350 --> 00:12:48.210 align:start position:0% the Waialae naming service so why a pad and<00:12:42.619> register<00:12:43.069> and<00:12:44.049> then<00:12:45.049> I'm<00:12:45.169> gonna<00:12:45.259> build<00:12:45.470> it 00:12:48.210 --> 00:12:48.220 align:start position:0% 00:12:48.220 --> 00:12:51.609 align:start position:0% and<00:12:49.220> with<00:12:49.399> that<00:12:49.579> out<00:12:49.699> of<00:12:49.730> the<00:12:49.850> way<00:12:50.119> the<00:12:50.899> launch 00:12:51.609 --> 00:12:51.619 align:start position:0% and with that out of the way the launch 00:12:51.619 --> 00:12:54.699 align:start position:0% and with that out of the way the launch pad<00:12:51.889> here<00:12:52.160> in<00:12:52.429> debug<00:12:53.059> mode<00:12:53.110> should<00:12:54.110> see<00:12:54.350> that 00:12:54.699 --> 00:12:54.709 align:start position:0% pad here in debug mode should see that 00:12:54.709 --> 00:12:57.999 align:start position:0% pad here in debug mode should see that the<00:12:56.230> application<00:12:57.230> has<00:12:57.290> been<00:12:57.350> registered<00:12:57.679> with 00:12:57.999 --> 00:12:58.009 align:start position:0% the application has been registered with 00:12:58.009 --> 00:13:01.239 align:start position:0% the application has been registered with the<00:12:58.220> chain<00:12:58.459> and<00:12:58.910> now<00:12:59.449> it<00:12:59.779> shows<00:13:00.110> the<00:13:00.470> new<00:13:00.649> tasks 00:13:01.239 --> 00:13:01.249 align:start position:0% the chain and now it shows the new tasks 00:13:01.249 --> 00:13:02.679 align:start position:0% the chain and now it shows the new tasks application<00:13:01.819> which<00:13:01.939> was<00:13:02.089> the<00:13:02.209> application 00:13:02.679 --> 00:13:02.689 align:start position:0% application which was the application 00:13:02.689 --> 00:13:04.569 align:start position:0% application which was the application that<00:13:02.809> we<00:13:02.899> forked<00:13:03.319> so<00:13:04.040> we're<00:13:04.160> going<00:13:04.309> to<00:13:04.369> create 00:13:04.569 --> 00:13:04.579 align:start position:0% that we forked so we're going to create 00:13:04.579 --> 00:13:07.749 align:start position:0% that we forked so we're going to create a<00:13:04.639> new<00:13:04.819> instance<00:13:05.209> of<00:13:05.389> that<00:13:06.069> and<00:13:07.069> write<00:13:07.489> some 00:13:07.749 --> 00:13:07.759 align:start position:0% a new instance of that and write some 00:13:07.759 --> 00:13:10.359 align:start position:0% a new instance of that and write some tasks<00:13:08.209> down<00:13:08.389> here<00:13:08.779> and<00:13:09.259> out<00:13:09.619> of<00:13:09.739> order<00:13:10.040> so<00:13:10.279> I've 00:13:10.359 --> 00:13:10.369 align:start position:0% tasks down here and out of order so I've 00:13:10.369 --> 00:13:13.720 align:start position:0% tasks down here and out of order so I've done<00:13:10.579> that<00:13:10.959> haven't<00:13:11.959> done<00:13:12.079> any<00:13:12.230> of<00:13:12.350> these<00:13:12.730> and 00:13:13.720 --> 00:13:13.730 align:start position:0% done that haven't done any of these and 00:13:13.730 --> 00:13:16.299 align:start position:0% done that haven't done any of these and because<00:13:14.600> the<00:13:15.169> framework<00:13:15.619> is<00:13:15.769> naturally 00:13:16.299 --> 00:13:16.309 align:start position:0% because the framework is naturally 00:13:16.309 --> 00:13:18.609 align:start position:0% because the framework is naturally collaborative<00:13:16.939> and<00:13:17.660> Ashwin<00:13:18.079> is<00:13:18.169> currently 00:13:18.609 --> 00:13:18.619 align:start position:0% collaborative and Ashwin is currently 00:13:18.619 --> 00:13:21.350 align:start position:0% collaborative and Ashwin is currently inside<00:13:19.039> this<00:13:19.279> party<00:13:19.759> I<00:13:19.939> can<00:13:20.360> see<00:13:20.509> that<00:13:20.660> with 00:13:21.350 --> 00:13:21.360 align:start position:0% inside this party I can see that with 00:13:21.360 --> 00:13:23.590 align:start position:0% inside this party I can see that with me<00:13:21.480> doing<00:13:21.750> any<00:13:21.870> more<00:13:22.050> coding<00:13:22.380> he's<00:13:22.920> able<00:13:23.100> to 00:13:23.590 --> 00:13:23.600 align:start position:0% me doing any more coding he's able to 00:13:23.600 --> 00:13:25.819 align:start position:0% me doing any more coding he's able to interoperate<00:13:24.600> with<00:13:24.630> this<00:13:25.050> interact<00:13:25.560> with 00:13:25.819 --> 00:13:25.829 align:start position:0% interoperate with this interact with 00:13:25.829 --> 00:13:28.250 align:start position:0% interoperate with this interact with this<00:13:26.040> this<00:13:26.399> new<00:13:26.610> pad<00:13:26.850> okay<00:13:27.779> so<00:13:27.839> we're<00:13:28.019> gonna<00:13:28.140> do 00:13:28.250 --> 00:13:28.260 align:start position:0% this this new pad okay so we're gonna do 00:13:28.260 --> 00:13:29.540 align:start position:0% this this new pad okay so we're gonna do something<00:13:28.470> different<00:13:28.560> we<00:13:28.890> gonna<00:13:29.010> change<00:13:29.339> this 00:13:29.540 --> 00:13:29.550 align:start position:0% something different we gonna change this 00:13:29.550 --> 00:13:31.579 align:start position:0% something different we gonna change this pad<00:13:29.820> and<00:13:30.510> we're<00:13:30.630> gonna<00:13:30.720> build<00:13:30.959> we<00:13:31.200> usually<00:13:31.470> do 00:13:31.579 --> 00:13:31.589 align:start position:0% pad and we're gonna build we usually do 00:13:31.589 --> 00:13:33.740 align:start position:0% pad and we're gonna build we usually do chess<00:13:31.890> as<00:13:32.160> an<00:13:32.279> example<00:13:32.640> but<00:13:32.970> since<00:13:33.540> we're<00:13:33.690> in 00:13:33.740 --> 00:13:33.750 align:start position:0% chess as an example but since we're in 00:13:33.750 --> 00:13:36.139 align:start position:0% chess as an example but since we're in Japan<00:13:34.170> we're<00:13:34.800> gonna<00:13:34.920> build<00:13:35.160> a<00:13:35.430> shogi<00:13:35.940> game 00:13:36.139 --> 00:13:36.149 align:start position:0% Japan we're gonna build a shogi game 00:13:36.149 --> 00:13:40.790 align:start position:0% Japan we're gonna build a shogi game which<00:13:36.630> is<00:13:36.779> Japanese<00:13:37.230> chess<00:13:37.700> so<00:13:39.560> the<00:13:40.560> first 00:13:40.790 --> 00:13:40.800 align:start position:0% which is Japanese chess so the first 00:13:40.800 --> 00:13:43.449 align:start position:0% which is Japanese chess so the first thing<00:13:40.950> I<00:13:41.040> do<00:13:41.100> is<00:13:41.459> change<00:13:41.700> the<00:13:41.910> render<00:13:42.209> method 00:13:43.449 --> 00:13:43.459 align:start position:0% thing I do is change the render method 00:13:43.459 --> 00:13:46.370 align:start position:0% thing I do is change the render method and<00:13:44.459> we've<00:13:44.640> got<00:13:44.820> some<00:13:45.120> of<00:13:45.360> the<00:13:45.750> code<00:13:46.170> already 00:13:46.370 --> 00:13:46.380 align:start position:0% and we've got some of the code already 00:13:46.380 --> 00:13:50.060 align:start position:0% and we've got some of the code already in<00:13:47.100> place<00:13:47.399> so<00:13:47.670> we're<00:13:47.820> using<00:13:48.060> a<00:13:48.680> standard<00:13:49.680> react 00:13:50.060 --> 00:13:50.070 align:start position:0% in place so we're using a standard react 00:13:50.070 --> 00:13:54.740 align:start position:0% in place so we're using a standard react components<00:13:50.850> that<00:13:51.060> we<00:13:51.240> found<00:13:51.450> on<00:13:51.810> NPM<00:13:53.240> that<00:13:54.240> has 00:13:54.740 --> 00:13:54.750 align:start position:0% components that we found on NPM that has 00:13:54.750 --> 00:13:58.699 align:start position:0% components that we found on NPM that has a<00:13:55.079> shogi<00:13:55.410> board<00:13:55.620> and<00:13:56.990> we're<00:13:57.990> going<00:13:58.140> to<00:13:58.200> just<00:13:58.440> we 00:13:58.699 --> 00:13:58.709 align:start position:0% a shogi board and we're going to just we 00:13:58.709 --> 00:14:00.650 align:start position:0% a shogi board and we're going to just we can<00:13:58.829> get<00:13:58.980> rid<00:13:59.100> of<00:13:59.130> most<00:13:59.370> of<00:13:59.579> these<00:13:59.730> code<00:14:00.269> here 00:14:00.650 --> 00:14:00.660 align:start position:0% can get rid of most of these code here 00:14:00.660 --> 00:14:02.720 align:start position:0% can get rid of most of these code here so<00:14:01.500> we've<00:14:01.620> got<00:14:01.709> a<00:14:01.740> simple<00:14:01.980> render<00:14:02.550> function 00:14:02.720 --> 00:14:02.730 align:start position:0% so we've got a simple render function 00:14:02.730 --> 00:14:04.610 align:start position:0% so we've got a simple render function and<00:14:03.630> we're<00:14:03.779> going<00:14:03.810> to<00:14:04.019> set<00:14:04.260> the<00:14:04.440> initial 00:14:04.610 --> 00:14:04.620 align:start position:0% and we're going to set the initial 00:14:04.620 --> 00:14:08.769 align:start position:0% and we're going to set the initial States<00:14:06.440> here<00:14:07.440> and<00:14:07.649> then<00:14:07.769> just<00:14:07.950> save<00:14:08.130> the<00:14:08.310> pad 00:14:08.769 --> 00:14:08.779 align:start position:0% States here and then just save the pad 00:14:08.779 --> 00:14:11.090 align:start position:0% States here and then just save the pad and<00:14:09.779> then<00:14:09.930> going<00:14:10.140> to<00:14:10.170> definitions<00:14:10.800> I'm<00:14:10.980> going 00:14:11.090 --> 00:14:11.100 align:start position:0% and then going to definitions I'm going 00:14:11.100 --> 00:14:15.110 align:start position:0% and then going to definitions I'm going to<00:14:11.160> change<00:14:11.430> the<00:14:11.730> icon<00:14:13.310> I'm<00:14:14.310> gonna<00:14:14.490> change<00:14:14.850> the 00:14:15.110 --> 00:14:15.120 align:start position:0% to change the icon I'm gonna change the 00:14:15.120 --> 00:14:18.560 align:start position:0% to change the icon I'm gonna change the name<00:14:15.329> of<00:14:15.510> the<00:14:15.600> app<00:14:15.720> to<00:14:15.930> shogi<00:14:16.350> and<00:14:17.570> the 00:14:18.560 --> 00:14:18.570 align:start position:0% name of the app to shogi and the 00:14:18.570 --> 00:14:22.100 align:start position:0% name of the app to shogi and the database<00:14:19.079> name<00:14:19.829> here<00:14:20.120> and<00:14:21.120> we<00:14:21.240> should<00:14:21.390> see<00:14:21.600> the 00:14:22.100 --> 00:14:22.110 align:start position:0% database name here and we should see the 00:14:22.110 --> 00:14:27.470 align:start position:0% database name here and we should see the pad<00:14:22.560> update<00:14:23.130> once<00:14:23.490> it's<00:14:24.269> rebuilt<00:14:25.850> and<00:14:26.850> now<00:14:27.420> we 00:14:27.470 --> 00:14:27.480 align:start position:0% pad update once it's rebuilt and now we 00:14:27.480 --> 00:14:30.259 align:start position:0% pad update once it's rebuilt and now we can<00:14:27.720> see<00:14:27.899> our<00:14:28.050> show<00:14:28.230> keyboard<00:14:29.060> okay<00:14:30.060> so<00:14:30.120> we 00:14:30.259 --> 00:14:30.269 align:start position:0% can see our show keyboard okay so we 00:14:30.269 --> 00:14:31.880 align:start position:0% can see our show keyboard okay so we have<00:14:30.360> the<00:14:30.420> starting<00:14:30.750> point<00:14:30.990> of<00:14:31.140> a<00:14:31.260> new<00:14:31.290> game<00:14:31.620> I 00:14:31.880 --> 00:14:31.890 align:start position:0% have the starting point of a new game I 00:14:31.890 --> 00:14:36.019 align:start position:0% have the starting point of a new game I can<00:14:32.699> move<00:14:32.880> pieces<00:14:34.040> but<00:14:35.040> obviously<00:14:35.370> if<00:14:35.490> I<00:14:35.550> reset 00:14:36.019 --> 00:14:36.029 align:start position:0% can move pieces but obviously if I reset 00:14:36.029 --> 00:14:37.400 align:start position:0% can move pieces but obviously if I reset the<00:14:36.060> browser<00:14:36.390> at<00:14:36.690> this<00:14:36.870> point<00:14:37.140> we're<00:14:37.260> going<00:14:37.350> to 00:14:37.400 --> 00:14:37.410 align:start position:0% the browser at this point we're going to 00:14:37.410 --> 00:14:38.660 align:start position:0% the browser at this point we're going to lose<00:14:37.589> the<00:14:37.769> state<00:14:38.010> because<00:14:38.190> we're<00:14:38.310> not<00:14:38.399> writing 00:14:38.660 --> 00:14:38.670 align:start position:0% lose the state because we're not writing 00:14:38.670 --> 00:14:40.130 align:start position:0% lose the state because we're not writing that<00:14:38.850> to<00:14:39.029> the<00:14:39.120> database<00:14:39.510> anywhere<00:14:39.870> so<00:14:40.050> that's 00:14:40.130 --> 00:14:40.140 align:start position:0% that to the database anywhere so that's 00:14:40.140 --> 00:14:42.290 align:start position:0% that to the database anywhere so that's the<00:14:40.260> next<00:14:40.410> thing<00:14:40.529> I'm<00:14:40.740> going<00:14:40.769> to<00:14:40.920> do<00:14:41.209> there's<00:14:42.209> a 00:14:42.290 --> 00:14:42.300 align:start position:0% the next thing I'm going to do there's a 00:14:42.300 --> 00:14:44.240 align:start position:0% the next thing I'm going to do there's a common<00:14:42.839> react<00:14:43.290> idiom<00:14:43.680> called<00:14:43.890> a<00:14:43.949> higher-order 00:14:44.240 --> 00:14:44.250 align:start position:0% common react idiom called a higher-order 00:14:44.250 --> 00:14:46.790 align:start position:0% common react idiom called a higher-order components<00:14:45.120> that<00:14:45.630> and<00:14:45.839> we're<00:14:46.170> using<00:14:46.380> that<00:14:46.529> to 00:14:46.790 --> 00:14:46.800 align:start position:0% components that and we're using that to 00:14:46.800 --> 00:14:48.710 align:start position:0% components that and we're using that to inject<00:14:47.220> the<00:14:47.430> peer-to-peer<00:14:47.730> database<00:14:48.360> into 00:14:48.710 --> 00:14:48.720 align:start position:0% inject the peer-to-peer database into 00:14:48.720 --> 00:14:50.509 align:start position:0% inject the peer-to-peer database into this<00:14:48.839> react<00:14:49.110> control<00:14:49.500> so<00:14:50.160> what<00:14:50.310> I'm<00:14:50.370> going<00:14:50.459> to 00:14:50.509 --> 00:14:50.519 align:start position:0% this react control so what I'm going to 00:14:50.519 --> 00:14:59.590 align:start position:0% this react control so what I'm going to do<00:14:50.640> here<00:14:50.910> is<00:14:51.029> I'm<00:14:51.360> gonna<00:14:51.540> add<00:14:51.750> a<00:14:53.420> handler<00:14:58.519> and 00:14:59.590 --> 00:14:59.600 align:start position:0% do here is I'm gonna add a handler and 00:14:59.600 --> 00:15:01.639 align:start position:0% do here is I'm gonna add a handler and what<00:15:00.600> I'm<00:15:00.720> doing<00:15:00.959> here<00:15:01.079> is<00:15:01.140> I'm<00:15:01.230> getting<00:15:01.500> the 00:15:01.639 --> 00:15:01.649 align:start position:0% what I'm doing here is I'm getting the 00:15:01.649 --> 00:15:03.800 align:start position:0% what I'm doing here is I'm getting the event<00:15:01.800> for<00:15:02.310> the<00:15:02.399> actual<00:15:02.790> drop<00:15:03.240> of<00:15:03.480> the<00:15:03.600> piece 00:15:03.800 --> 00:15:03.810 align:start position:0% event for the actual drop of the piece 00:15:03.810 --> 00:15:05.569 align:start position:0% event for the actual drop of the piece I'm<00:15:04.350> gonna<00:15:04.589> validate<00:15:04.829> that<00:15:05.220> that's<00:15:05.370> actually 00:15:05.569 --> 00:15:05.579 align:start position:0% I'm gonna validate that that's actually 00:15:05.579 --> 00:15:08.090 align:start position:0% I'm gonna validate that that's actually a<00:15:05.760> legal<00:15:06.029> move<00:15:06.209> and<00:15:06.570> then<00:15:06.720> if<00:15:06.839> it<00:15:06.959> is<00:15:07.140> I'm<00:15:07.920> gonna 00:15:08.090 --> 00:15:08.100 align:start position:0% a legal move and then if it is I'm gonna 00:15:08.100 --> 00:15:11.210 align:start position:0% a legal move and then if it is I'm gonna append<00:15:08.760> that<00:15:08.910> move<00:15:09.300> onto<00:15:09.720> the<00:15:10.500> replicated 00:15:11.210 --> 00:15:11.220 align:start position:0% append that move onto the replicated 00:15:11.220 --> 00:15:13.699 align:start position:0% append that move onto the replicated database<00:15:11.670> log<00:15:11.970> that's<00:15:12.329> this<00:15:12.510> view<00:15:13.199> property 00:15:13.699 --> 00:15:13.709 align:start position:0% database log that's this view property 00:15:13.709 --> 00:15:15.650 align:start position:0% database log that's this view property that's<00:15:13.890> been<00:15:14.130> inserted<00:15:14.490> into<00:15:14.910> the<00:15:15.149> control 00:15:15.650 --> 00:15:15.660 align:start position:0% that's been inserted into the control 00:15:15.660 --> 00:15:19.040 align:start position:0% that's been inserted into the control now<00:15:16.500> it's<00:15:16.649> a<00:15:16.709> handle<00:15:17.100> the<00:15:18.089> moves<00:15:18.329> coming<00:15:18.930> in 00:15:19.040 --> 00:15:19.050 align:start position:0% now it's a handle the moves coming in 00:15:19.050 --> 00:15:21.470 align:start position:0% now it's a handle the moves coming in from<00:15:19.350> other<00:15:19.500> peers<00:15:19.829> on<00:15:20.100> the<00:15:20.250> network<00:15:20.610> I'm 00:15:21.470 --> 00:15:21.480 align:start position:0% from other peers on the network I'm 00:15:21.480 --> 00:15:24.500 align:start position:0% from other peers on the network I'm going<00:15:21.930> to<00:15:21.990> add<00:15:22.260> in<00:15:22.910> another<00:15:23.910> piece<00:15:24.149> of<00:15:24.300> code 00:15:24.500 --> 00:15:24.510 align:start position:0% going to add in another piece of code 00:15:24.510 --> 00:15:29.780 align:start position:0% going to add in another piece of code here<00:15:25.699> which<00:15:27.110> takes<00:15:28.110> the<00:15:28.649> log<00:15:28.860> I'm<00:15:29.579> going<00:15:29.730> to 00:15:29.780 --> 00:15:29.790 align:start position:0% here which takes the log I'm going to 00:15:29.790 --> 00:15:32.420 align:start position:0% here which takes the log I'm going to iterate<00:15:30.240> through<00:15:30.540> it<00:15:30.779> and<00:15:31.140> then<00:15:31.589> update<00:15:32.250> the 00:15:32.420 --> 00:15:32.430 align:start position:0% iterate through it and then update the 00:15:32.430 --> 00:15:34.220 align:start position:0% iterate through it and then update the state<00:15:32.730> of<00:15:32.970> the<00:15:33.089> game<00:15:33.240> and<00:15:33.600> then 00:15:34.220 --> 00:15:34.230 align:start position:0% state of the game and then 00:15:34.230 --> 00:15:36.230 align:start position:0% state of the game and then set<00:15:34.620> that<00:15:34.800> as<00:15:34.950> the<00:15:34.980> state<00:15:35.310> property<00:15:35.790> in<00:15:36.060> the 00:15:36.230 --> 00:15:36.240 align:start position:0% set that as the state property in the 00:15:36.240 --> 00:15:38.960 align:start position:0% set that as the state property in the application<00:15:36.810> and<00:15:37.380> so<00:15:37.560> now<00:15:37.740> if<00:15:37.980> I<00:15:38.130> go<00:15:38.310> into<00:15:38.490> the 00:15:38.960 --> 00:15:38.970 align:start position:0% application and so now if I go into the 00:15:38.970 --> 00:15:41.270 align:start position:0% application and so now if I go into the chat<00:15:39.210> room<00:15:39.240> once<00:15:40.140> the<00:15:40.320> app<00:15:40.440> is<00:15:40.560> reloaded<00:15:41.040> I<00:15:41.160> can 00:15:41.270 --> 00:15:41.280 align:start position:0% chat room once the app is reloaded I can 00:15:41.280 --> 00:15:44.050 align:start position:0% chat room once the app is reloaded I can say<00:15:41.490> hey<00:15:42.150> Ashwin<00:15:42.480> are<00:15:43.020> you<00:15:43.110> there 00:15:44.050 --> 00:15:44.060 align:start position:0% say hey Ashwin are you there 00:15:44.060 --> 00:15:49.880 align:start position:0% say hey Ashwin are you there apologies<00:15:45.060> for<00:15:45.240> the<00:15:45.390> typo<00:15:46.610> let's<00:15:47.610> play<00:15:48.890> shogi 00:15:49.880 --> 00:15:49.890 align:start position:0% apologies for the typo let's play shogi 00:15:49.890 --> 00:15:53.510 align:start position:0% apologies for the typo let's play shogi and<00:15:50.900> so<00:15:51.900> here<00:15:52.110> I'm<00:15:52.230> creating<00:15:52.440> a<00:15:52.740> new<00:15:52.920> game<00:15:53.160> from 00:15:53.510 --> 00:15:53.520 align:start position:0% and so here I'm creating a new game from 00:15:53.520 --> 00:15:55.790 align:start position:0% and so here I'm creating a new game from kind<00:15:54.300> of<00:15:54.360> slack<00:15:54.690> application<00:15:55.470> our<00:15:55.590> chat 00:15:55.790 --> 00:15:55.800 align:start position:0% kind of slack application our chat 00:15:55.800 --> 00:15:57.920 align:start position:0% kind of slack application our chat application<00:15:56.400> and<00:15:56.760> if<00:15:57.060> I<00:15:57.180> click<00:15:57.390> on<00:15:57.450> the<00:15:57.690> link 00:15:57.920 --> 00:15:57.930 align:start position:0% application and if I click on the link 00:15:57.930 --> 00:16:00.610 align:start position:0% application and if I click on the link here<00:15:58.260> it<00:15:58.530> should<00:15:58.710> take<00:15:58.950> me<00:15:59.160> into<00:15:59.370> the<00:15:59.670> game<00:15:59.820> and 00:16:00.610 --> 00:16:00.620 align:start position:0% here it should take me into the game and 00:16:00.620 --> 00:16:02.680 align:start position:0% here it should take me into the game and just<00:16:01.620> because<00:16:01.980> the<00:16:02.070> action<00:16:02.430> and<00:16:02.520> I<00:16:02.610> know 00:16:02.680 --> 00:16:02.690 align:start position:0% just because the action and I know 00:16:02.690 --> 00:16:05.570 align:start position:0% just because the action and I know swarming<00:16:03.690> on<00:16:03.780> the<00:16:03.930> same<00:16:04.170> node<00:16:04.950> on<00:16:05.340> this 00:16:05.570 --> 00:16:05.580 align:start position:0% swarming on the same node on this 00:16:05.580 --> 00:16:07.190 align:start position:0% swarming on the same node on this peer-to-peer<00:16:05.790> network<00:16:06.270> that<00:16:06.810> should<00:16:06.990> allow 00:16:07.190 --> 00:16:07.200 align:start position:0% peer-to-peer network that should allow 00:16:07.200 --> 00:16:09.320 align:start position:0% peer-to-peer network that should allow his<00:16:07.500> peer<00:16:07.800> to<00:16:08.010> dynamically<00:16:08.730> load<00:16:09.000> this 00:16:09.320 --> 00:16:09.330 align:start position:0% his peer to dynamically load this 00:16:09.330 --> 00:16:13.430 align:start position:0% his peer to dynamically load this application<00:16:10.050> so<00:16:10.710> now<00:16:10.860> if<00:16:10.980> I<00:16:11.070> make<00:16:11.250> a<00:16:11.280> move<00:16:12.440> that 00:16:13.430 --> 00:16:13.440 align:start position:0% application so now if I make a move that 00:16:13.440 --> 00:16:17.090 align:start position:0% application so now if I make a move that see<00:16:13.740> if<00:16:13.830> a<00:16:13.950> shrinkin<00:16:14.460> can<00:16:14.870> play<00:16:15.870> okay<00:16:16.290> so<00:16:16.620> I'll 00:16:17.090 --> 00:16:17.100 align:start position:0% see if a shrinkin can play okay so I'll 00:16:17.100 --> 00:16:20.540 align:start position:0% see if a shrinkin can play okay so I'll just<00:16:17.310> move<00:16:18.060> my<00:16:18.200> Kaku<00:16:19.200> Bishop<00:16:19.710> over<00:16:19.950> here<00:16:20.280> and 00:16:20.540 --> 00:16:20.550 align:start position:0% just move my Kaku Bishop over here and 00:16:20.550 --> 00:16:23.750 align:start position:0% just move my Kaku Bishop over here and take<00:16:20.730> his<00:16:20.910> piece<00:16:21.890> and<00:16:22.890> we<00:16:23.130> have<00:16:23.250> the<00:16:23.340> beginning 00:16:23.750 --> 00:16:23.760 align:start position:0% take his piece and we have the beginning 00:16:23.760 --> 00:16:25.100 align:start position:0% take his piece and we have the beginning of<00:16:23.850> a<00:16:23.970> collaborative<00:16:24.390> game<00:16:24.690> again<00:16:24.990> without 00:16:25.100 --> 00:16:25.110 align:start position:0% of a collaborative game again without 00:16:25.110 --> 00:16:26.960 align:start position:0% of a collaborative game again without having<00:16:25.350> to<00:16:25.590> do<00:16:25.710> having<00:16:26.190> to<00:16:26.280> manage<00:16:26.490> any<00:16:26.790> of 00:16:26.960 --> 00:16:26.970 align:start position:0% having to do having to manage any of 00:16:26.970 --> 00:16:29.210 align:start position:0% having to do having to manage any of that<00:16:27.090> replicated<00:16:27.600> State<00:16:27.930> so<00:16:28.770> I've<00:16:28.860> got<00:16:29.010> a 00:16:29.210 --> 00:16:29.220 align:start position:0% that replicated State so I've got a 00:16:29.220 --> 00:16:32.030 align:start position:0% that replicated State so I've got a minute<00:16:29.850> and<00:16:30.000> 16<00:16:30.600> seconds<00:16:31.200> left<00:16:31.290> that<00:16:31.770> should 00:16:32.030 --> 00:16:32.040 align:start position:0% minute and 16 seconds left that should 00:16:32.040 --> 00:16:34.190 align:start position:0% minute and 16 seconds left that should be<00:16:32.160> plenty<00:16:32.430> of<00:16:32.580> time<00:16:32.820> to<00:16:32.850> create<00:16:33.330> a<00:16:33.510> super<00:16:34.020> AI 00:16:34.190 --> 00:16:34.200 align:start position:0% be plenty of time to create a super AI 00:16:34.200 --> 00:16:37.570 align:start position:0% be plenty of time to create a super AI that<00:16:34.770> is<00:16:34.890> going<00:16:35.070> to<00:16:35.130> play<00:16:35.280> shogi<00:16:35.670> with<00:16:36.000> me<00:16:36.210> so 00:16:37.570 --> 00:16:37.580 align:start position:0% that is going to play shogi with me so 00:16:37.580 --> 00:16:39.980 align:start position:0% that is going to play shogi with me so we're<00:16:38.580> going<00:16:38.730> to<00:16:38.790> use<00:16:39.000> the<00:16:39.150> wireline<00:16:39.420> SDK 00:16:39.980 --> 00:16:39.990 align:start position:0% we're going to use the wireline SDK 00:16:39.990 --> 00:16:43.610 align:start position:0% we're going to use the wireline SDK again<00:16:40.440> I'm<00:16:41.100> going<00:16:41.310> to<00:16:41.370> say<00:16:41.580> wire<00:16:42.230> bot<00:16:43.230> create 00:16:43.610 --> 00:16:43.620 align:start position:0% again I'm going to say wire bot create 00:16:43.620 --> 00:16:46.310 align:start position:0% again I'm going to say wire bot create again<00:16:44.010> forking<00:16:44.550> an<00:16:44.730> existing<00:16:45.330> project<00:16:45.630> now 00:16:46.310 --> 00:16:46.320 align:start position:0% again forking an existing project now 00:16:46.320 --> 00:16:49.250 align:start position:0% again forking an existing project now bots<00:16:46.620> are<00:16:46.920> these<00:16:47.100> asynchronous<00:16:48.260> autonomous 00:16:49.250 --> 00:16:49.260 align:start position:0% bots are these asynchronous autonomous 00:16:49.260 --> 00:16:50.750 align:start position:0% bots are these asynchronous autonomous agents<00:16:49.740> that<00:16:49.920> live<00:16:50.130> on<00:16:50.370> the<00:16:50.520> peer-to-peer 00:16:50.750 --> 00:16:50.760 align:start position:0% agents that live on the peer-to-peer 00:16:50.760 --> 00:16:55.520 align:start position:0% agents that live on the peer-to-peer network<00:16:50.820> and<00:16:52.910> they're<00:16:53.910> modeled<00:16:54.780> after<00:16:54.930> simple 00:16:55.520 --> 00:16:55.530 align:start position:0% network and they're modeled after simple 00:16:55.530 --> 00:16:57.230 align:start position:0% network and they're modeled after simple lambda<00:16:55.890> or<00:16:55.980> function<00:16:56.280> as<00:16:56.400> a<00:16:56.430> service<00:16:56.850> function 00:16:57.230 --> 00:16:57.240 align:start position:0% lambda or function as a service function 00:16:57.240 --> 00:17:02.210 align:start position:0% lambda or function as a service function so<00:16:57.360> they're<00:16:57.480> really<00:16:57.660> easy<00:16:57.780> to<00:16:58.290> develop<00:17:01.220> open 00:17:02.210 --> 00:17:02.220 align:start position:0% so they're really easy to develop open 00:17:02.220 --> 00:17:06.400 align:start position:0% so they're really easy to develop open up<00:17:02.490> the<00:17:02.610> code<00:17:02.820> here<00:17:03.210> and<00:17:04.820> there's<00:17:05.820> a 00:17:06.400 --> 00:17:06.410 align:start position:0% up the code here and there's a 00:17:06.410 --> 00:17:09.050 align:start position:0% up the code here and there's a definition<00:17:07.410> file<00:17:07.680> there's<00:17:08.160> the<00:17:08.280> bot<00:17:08.459> code<00:17:08.730> and 00:17:09.050 --> 00:17:09.060 align:start position:0% definition file there's the bot code and 00:17:09.060 --> 00:17:11.240 align:start position:0% definition file there's the bot code and that's<00:17:09.180> a<00:17:09.440> configuration<00:17:10.440> file<00:17:10.800> so<00:17:10.980> the<00:17:11.040> first 00:17:11.240 --> 00:17:11.250 align:start position:0% that's a configuration file so the first 00:17:11.250 --> 00:17:12.680 align:start position:0% that's a configuration file so the first thing<00:17:11.339> I'm<00:17:11.430> going<00:17:11.550> to<00:17:11.610> do<00:17:11.760> is<00:17:11.940> change<00:17:12.270> the<00:17:12.510> name 00:17:12.680 --> 00:17:12.690 align:start position:0% thing I'm going to do is change the name 00:17:12.690 --> 00:17:19.069 align:start position:0% thing I'm going to do is change the name of<00:17:12.720> this<00:17:13.050> to<00:17:13.320> shogi<00:17:14.130> bot<00:17:17.630> I'm<00:17:18.630> going<00:17:18.810> to<00:17:18.870> change 00:17:19.069 --> 00:17:19.079 align:start position:0% of this to shogi bot I'm going to change 00:17:19.079 --> 00:17:21.319 align:start position:0% of this to shogi bot I'm going to change the<00:17:19.230> definitions<00:17:19.800> to<00:17:19.949> use<00:17:20.190> the<00:17:20.459> same<00:17:20.699> database 00:17:21.319 --> 00:17:21.329 align:start position:0% the definitions to use the same database 00:17:21.329 --> 00:17:23.870 align:start position:0% the definitions to use the same database table<00:17:22.079> that<00:17:22.260> I've<00:17:22.380> set<00:17:22.890> up<00:17:22.920> for<00:17:23.310> the<00:17:23.370> pad<00:17:23.579> so 00:17:23.870 --> 00:17:23.880 align:start position:0% table that I've set up for the pad so 00:17:23.880 --> 00:17:25.310 align:start position:0% table that I've set up for the pad so that<00:17:23.910> they<00:17:24.120> can<00:17:24.270> interoperate<00:17:24.810> with<00:17:25.110> each 00:17:25.310 --> 00:17:25.320 align:start position:0% that they can interoperate with each 00:17:25.320 --> 00:17:27.350 align:start position:0% that they can interoperate with each other<00:17:25.530> and<00:17:25.860> then<00:17:26.550> I'm<00:17:26.790> gonna<00:17:26.940> use<00:17:27.150> the<00:17:27.329> same 00:17:27.350 --> 00:17:27.360 align:start position:0% other and then I'm gonna use the same 00:17:27.360 --> 00:17:30.910 align:start position:0% other and then I'm gonna use the same standard<00:17:28.079> library<00:17:28.590> that<00:17:29.490> we<00:17:29.790> used<00:17:30.150> on<00:17:30.420> the<00:17:30.690> pad 00:17:30.910 --> 00:17:30.920 align:start position:0% standard library that we used on the pad 00:17:30.920 --> 00:17:38.600 align:start position:0% standard library that we used on the pad so<00:17:31.920> I'm<00:17:32.130> gonna<00:17:32.870> here<00:17:33.870> I<00:17:37.370> don't<00:17:38.370> know<00:17:38.460> if<00:17:38.520> you 00:17:38.600 --> 00:17:38.610 align:start position:0% so I'm gonna here I don't know if you 00:17:38.610 --> 00:17:40.400 align:start position:0% so I'm gonna here I don't know if you can<00:17:38.790> see<00:17:39.030> this<00:17:39.240> but<00:17:39.660> I'm<00:17:39.930> going<00:17:40.170> to<00:17:40.200> iterate 00:17:40.400 --> 00:17:40.410 align:start position:0% can see this but I'm going to iterate 00:17:40.410 --> 00:17:43.070 align:start position:0% can see this but I'm going to iterate through<00:17:41.040> the<00:17:41.370> log<00:17:41.760> of<00:17:42.090> moves<00:17:42.450> that<00:17:42.660> have<00:17:42.900> been 00:17:43.070 --> 00:17:43.080 align:start position:0% through the log of moves that have been 00:17:43.080 --> 00:17:45.410 align:start position:0% through the log of moves that have been replicated<00:17:43.800> to<00:17:43.920> this<00:17:44.040> peer<00:17:44.430> and<00:17:44.700> update<00:17:45.300> the 00:17:45.410 --> 00:17:45.420 align:start position:0% replicated to this peer and update the 00:17:45.420 --> 00:17:48.140 align:start position:0% replicated to this peer and update the state<00:17:45.630> so<00:17:46.620> now<00:17:46.800> if<00:17:47.040> I 00:17:48.140 --> 00:17:48.150 align:start position:0% state so now if I 00:17:48.150 --> 00:17:50.780 align:start position:0% state so now if I go<00:17:48.660> into<00:17:48.960> the<00:17:49.080> terminal<00:17:49.400> and<00:17:50.400> I'm<00:17:50.550> gonna<00:17:50.700> do 00:17:50.780 --> 00:17:50.790 align:start position:0% go into the terminal and I'm gonna do 00:17:50.790 --> 00:17:53.000 align:start position:0% go into the terminal and I'm gonna do the<00:17:50.910> same<00:17:50.940> thing<00:17:51.150> here<00:17:51.600> why<00:17:51.870> are<00:17:51.930> not<00:17:52.320> register 00:17:53.000 --> 00:17:53.010 align:start position:0% the same thing here why are not register 00:17:53.010 --> 00:17:55.100 align:start position:0% the same thing here why are not register and<00:17:53.460> so<00:17:53.580> this<00:17:53.730> is<00:17:53.880> registering<00:17:54.480> the<00:17:54.600> spot<00:17:54.870> with 00:17:55.100 --> 00:17:55.110 align:start position:0% and so this is registering the spot with 00:17:55.110 --> 00:17:56.299 align:start position:0% and so this is registering the spot with the<00:17:55.230> blockchain<00:17:55.559> and<00:17:55.860> we<00:17:55.920> have<00:17:56.040> a<00:17:56.070> full 00:17:56.299 --> 00:17:56.309 align:start position:0% the blockchain and we have a full 00:17:56.309 --> 00:17:57.860 align:start position:0% the blockchain and we have a full blockchain<00:17:56.760> node<00:17:57.000> running<00:17:57.270> here<00:17:57.660> on<00:17:57.690> this 00:17:57.860 --> 00:17:57.870 align:start position:0% blockchain node running here on this 00:17:57.870 --> 00:18:02.450 align:start position:0% blockchain node running here on this peer<00:17:58.200> and<00:17:58.880> wire<00:17:59.880> run<00:18:00.780> this<00:18:01.620> will<00:18:01.830> run<00:18:02.010> the<00:18:02.070> bot 00:18:02.450 --> 00:18:02.460 align:start position:0% peer and wire run this will run the bot 00:18:02.460 --> 00:18:05.210 align:start position:0% peer and wire run this will run the bot in<00:18:02.730> a<00:18:03.090> debug<00:18:03.450> mode<00:18:03.559> so<00:18:04.559> I<00:18:04.590> can<00:18:04.800> see<00:18:04.950> that<00:18:04.980> it 00:18:05.210 --> 00:18:05.220 align:start position:0% in a debug mode so I can see that it 00:18:05.220 --> 00:18:08.750 align:start position:0% in a debug mode so I can see that it started<00:18:05.730> here<00:18:06.260> and<00:18:07.260> now<00:18:07.470> the<00:18:08.010> bot<00:18:08.220> has<00:18:08.400> its<00:18:08.610> own 00:18:08.750 --> 00:18:08.760 align:start position:0% started here and now the bot has its own 00:18:08.760 --> 00:18:12.020 align:start position:0% started here and now the bot has its own identity<00:18:09.110> so<00:18:10.110> if<00:18:10.350> I<00:18:10.470> open<00:18:10.710> up<00:18:10.800> the<00:18:11.130> side<00:18:11.790> by 00:18:12.020 --> 00:18:12.030 align:start position:0% identity so if I open up the side by 00:18:12.030 --> 00:18:14.090 align:start position:0% identity so if I open up the side by here<00:18:12.330> I<00:18:12.510> can<00:18:12.870> go<00:18:13.080> here<00:18:13.470> and<00:18:13.680> query<00:18:14.010> the 00:18:14.090 --> 00:18:14.100 align:start position:0% here I can go here and query the 00:18:14.100 --> 00:18:17.180 align:start position:0% here I can go here and query the blockchain<00:18:14.430> I<00:18:15.030> finally<00:18:15.900> bought<00:18:16.190> registered 00:18:17.180 --> 00:18:17.190 align:start position:0% blockchain I finally bought registered 00:18:17.190 --> 00:18:18.890 align:start position:0% blockchain I finally bought registered there<00:18:17.370> and<00:18:17.550> I<00:18:17.610> can<00:18:17.730> invite<00:18:18.030> it<00:18:18.270> to<00:18:18.420> the<00:18:18.510> party 00:18:18.890 --> 00:18:18.900 align:start position:0% there and I can invite it to the party 00:18:18.900 --> 00:18:21.740 align:start position:0% there and I can invite it to the party and<00:18:19.170> so<00:18:19.710> I<00:18:19.740> can<00:18:19.920> see<00:18:20.100> here<00:18:20.340> both<00:18:20.610> Ashwin<00:18:21.600> and 00:18:21.740 --> 00:18:21.750 align:start position:0% and so I can see here both Ashwin and 00:18:21.750 --> 00:18:23.720 align:start position:0% and so I can see here both Ashwin and the<00:18:22.500> bots<00:18:22.710> are<00:18:22.950> now<00:18:23.070> part<00:18:23.400> of<00:18:23.520> this 00:18:23.720 --> 00:18:23.730 align:start position:0% the bots are now part of this 00:18:23.730 --> 00:18:25.910 align:start position:0% the bots are now part of this collaborative<00:18:24.450> space<00:18:24.870> and<00:18:25.470> we<00:18:25.590> can<00:18:25.679> see<00:18:25.890> that 00:18:25.910 --> 00:18:25.920 align:start position:0% collaborative space and we can see that 00:18:25.920 --> 00:18:28.010 align:start position:0% collaborative space and we can see that the<00:18:26.130> bot<00:18:26.309> has<00:18:26.520> logged<00:18:26.760> the<00:18:27.000> current<00:18:27.360> state<00:18:27.809> of 00:18:28.010 --> 00:18:28.020 align:start position:0% the bot has logged the current state of 00:18:28.020 --> 00:18:30.470 align:start position:0% the bot has logged the current state of this<00:18:28.470> shogi<00:18:29.309> game<00:18:29.340> if<00:18:29.670> you<00:18:29.880> see<00:18:30.030> if<00:18:30.090> I<00:18:30.179> move<00:18:30.390> the 00:18:30.470 --> 00:18:30.480 align:start position:0% this shogi game if you see if I move the 00:18:30.480 --> 00:18:33.560 align:start position:0% this shogi game if you see if I move the piece<00:18:30.720> then<00:18:31.470> this<00:18:31.980> piece<00:18:32.670> gets<00:18:32.940> updated<00:18:33.330> here 00:18:33.560 --> 00:18:33.570 align:start position:0% piece then this piece gets updated here 00:18:33.570 --> 00:18:34.850 align:start position:0% piece then this piece gets updated here so<00:18:33.960> the<00:18:34.020> last<00:18:34.050> thing<00:18:34.320> I'm<00:18:34.410> going<00:18:34.500> to<00:18:34.559> do<00:18:34.679> really 00:18:34.850 --> 00:18:34.860 align:start position:0% so the last thing I'm going to do really 00:18:34.860 --> 00:18:35.710 align:start position:0% so the last thing I'm going to do really quickly 00:18:35.710 --> 00:18:35.720 align:start position:0% quickly 00:18:35.720 --> 00:18:38.919 align:start position:0% quickly we're<00:18:36.720> going<00:18:36.870> to<00:18:36.929> do<00:18:36.990> the<00:18:37.080> AI<00:18:37.200> piece<00:18:37.620> so<00:18:38.280> I 00:18:38.919 --> 00:18:38.929 align:start position:0% we're going to do the AI piece so I 00:18:38.929 --> 00:18:42.110 align:start position:0% we're going to do the AI piece so I guess<00:18:39.929> we'll<00:18:40.170> keep<00:18:40.350> that<00:18:40.559> simple<00:18:41.040> we're<00:18:41.880> going 00:18:42.110 --> 00:18:42.120 align:start position:0% guess we'll keep that simple we're going 00:18:42.120 --> 00:18:44.930 align:start position:0% guess we'll keep that simple we're going to<00:18:42.470> get<00:18:43.470> a<00:18:43.530> list<00:18:43.770> of<00:18:43.890> valid<00:18:44.220> rules<00:18:44.429> and<00:18:44.760> pick 00:18:44.930 --> 00:18:44.940 align:start position:0% to get a list of valid rules and pick 00:18:44.940 --> 00:18:47.240 align:start position:0% to get a list of valid rules and pick one<00:18:45.090> at<00:18:45.210> random<00:18:45.240> and<00:18:45.780> then<00:18:45.870> post<00:18:46.290> that<00:18:46.440> move<00:18:46.830> to 00:18:47.240 --> 00:18:47.250 align:start position:0% one at random and then post that move to 00:18:47.250 --> 00:18:49.250 align:start position:0% one at random and then post that move to the<00:18:47.400> feed<00:18:48.090> and<00:18:48.420> see<00:18:48.600> if<00:18:48.720> the<00:18:48.840> replication 00:18:49.250 --> 00:18:49.260 align:start position:0% the feed and see if the replication 00:18:49.260 --> 00:18:51.530 align:start position:0% the feed and see if the replication happens<00:18:49.800> so<00:18:49.980> if<00:18:50.070> I<00:18:50.160> save<00:18:50.429> that<00:18:50.460> it<00:18:51.270> should 00:18:51.530 --> 00:18:51.540 align:start position:0% happens so if I save that it should 00:18:51.540 --> 00:18:54.980 align:start position:0% happens so if I save that it should restart<00:18:52.020> the<00:18:52.320> bot<00:18:52.559> and<00:18:52.850> if<00:18:53.850> I<00:18:54.030> now<00:18:54.330> create<00:18:54.900> a 00:18:54.980 --> 00:18:54.990 align:start position:0% restart the bot and if I now create a 00:18:54.990 --> 00:18:58.270 align:start position:0% restart the bot and if I now create a new<00:18:55.170> game<00:18:55.380> and<00:18:55.820> I<00:18:56.820> make<00:18:56.850> the<00:18:57.120> first<00:18:57.510> move 00:18:58.270 --> 00:18:58.280 align:start position:0% new game and I make the first move 00:18:58.280 --> 00:19:00.590 align:start position:0% new game and I make the first move we<00:18:59.280> should<00:18:59.460> see<00:18:59.640> that<00:18:59.670> show<00:18:59.970> he<00:19:00.120> bought<00:19:00.300> is<00:19:00.420> now 00:19:00.590 --> 00:19:00.600 align:start position:0% we should see that show he bought is now 00:19:00.600 --> 00:19:03.340 align:start position:0% we should see that show he bought is now alive<00:19:00.929> so<00:19:01.650> we've<00:19:01.830> built<00:19:02.070> a<00:19:02.490> complete 00:19:03.340 --> 00:19:03.350 align:start position:0% alive so we've built a complete 00:19:03.350 --> 00:19:06.890 align:start position:0% alive so we've built a complete peer-to-peer<00:19:04.350> application<00:19:05.340> in<00:19:05.570> just<00:19:06.570> a<00:19:06.720> few 00:19:06.890 --> 00:19:06.900 align:start position:0% peer-to-peer application in just a few 00:19:06.900 --> 00:19:16.910 align:start position:0% peer-to-peer application in just a few minutes<00:19:09.230> so<00:19:10.230> I'll<00:19:10.410> finish<00:19:10.830> off<00:19:11.160> here<00:19:15.710> we<00:19:16.710> see 00:19:16.910 --> 00:19:16.920 align:start position:0% minutes so I'll finish off here we see 00:19:16.920 --> 00:19:19.669 align:start position:0% minutes so I'll finish off here we see the<00:19:17.040> web<00:19:17.250> evolving<00:19:18.120> into<00:19:18.420> a<00:19:18.660> hybrid<00:19:19.200> of 00:19:19.669 --> 00:19:19.679 align:start position:0% the web evolving into a hybrid of 00:19:19.679 --> 00:19:23.090 align:start position:0% the web evolving into a hybrid of different<00:19:20.400> decentralized<00:19:21.090> systems<00:19:22.100> the 00:19:23.090 --> 00:19:23.100 align:start position:0% different decentralized systems the 00:19:23.100 --> 00:19:24.200 align:start position:0% different decentralized systems the while<00:19:23.280> a<00:19:23.309> naming<00:19:23.580> service<00:19:24.030> is<00:19:24.179> a 00:19:24.200 --> 00:19:24.210 align:start position:0% while a naming service is a 00:19:24.210 --> 00:19:26.240 align:start position:0% while a naming service is a permissionless<00:19:24.660> blockchain<00:19:25.320> and<00:19:25.650> it's<00:19:26.070> the 00:19:26.240 --> 00:19:26.250 align:start position:0% permissionless blockchain and it's the 00:19:26.250 --> 00:19:28.190 align:start position:0% permissionless blockchain and it's the registry<00:19:26.880> for<00:19:26.910> all<00:19:27.270> the<00:19:27.450> applications<00:19:28.080> that 00:19:28.190 --> 00:19:28.200 align:start position:0% registry for all the applications that 00:19:28.200 --> 00:19:29.780 align:start position:0% registry for all the applications that run<00:19:28.410> on<00:19:28.470> the<00:19:28.650> peer-to-peer<00:19:28.860> network<00:19:28.950> it's<00:19:29.640> the 00:19:29.780 --> 00:19:29.790 align:start position:0% run on the peer-to-peer network it's the 00:19:29.790 --> 00:19:32.299 align:start position:0% run on the peer-to-peer network it's the source<00:19:30.059> of<00:19:30.240> truth<00:19:30.570> it's<00:19:31.080> also<00:19:31.440> a<00:19:31.890> mechanism 00:19:32.299 --> 00:19:32.309 align:start position:0% source of truth it's also a mechanism 00:19:32.309 --> 00:19:34.400 align:start position:0% source of truth it's also a mechanism that<00:19:32.550> enables<00:19:32.730> payments<00:19:33.480> to<00:19:33.990> work<00:19:34.140> between 00:19:34.400 --> 00:19:34.410 align:start position:0% that enables payments to work between 00:19:34.410 --> 00:19:36.020 align:start position:0% that enables payments to work between the<00:19:34.590> different<00:19:34.890> applications<00:19:35.429> and<00:19:35.550> users<00:19:35.880> on 00:19:36.020 --> 00:19:36.030 align:start position:0% the different applications and users on 00:19:36.030 --> 00:19:38.990 align:start position:0% the different applications and users on the<00:19:36.120> network<00:19:36.450> we've<00:19:37.290> got<00:19:37.470> wire<00:19:37.679> compute<00:19:38.250> which 00:19:38.990 --> 00:19:39.000 align:start position:0% the network we've got wire compute which 00:19:39.000 --> 00:19:42.020 align:start position:0% the network we've got wire compute which is<00:19:39.210> a<00:19:39.420> decentralized<00:19:40.429> computation<00:19:41.429> process 00:19:42.020 --> 00:19:42.030 align:start position:0% is a decentralized computation process 00:19:42.030 --> 00:19:44.960 align:start position:0% is a decentralized computation process platform<00:19:42.960> for<00:19:43.530> long<00:19:43.800> running<00:19:44.040> processes<00:19:44.610> and 00:19:44.960 --> 00:19:44.970 align:start position:0% platform for long running processes and 00:19:44.970 --> 00:19:46.910 align:start position:0% platform for long running processes and then<00:19:45.450> we've<00:19:45.600> got<00:19:45.720> wire<00:19:45.900> p2p<00:19:46.500> which<00:19:46.710> is<00:19:46.890> a 00:19:46.910 --> 00:19:46.920 align:start position:0% then we've got wire p2p which is a 00:19:46.920 --> 00:19:49.160 align:start position:0% then we've got wire p2p which is a peer-to-peer<00:19:47.400> network<00:19:48.030> now<00:19:48.870> we've<00:19:49.020> been 00:19:49.160 --> 00:19:49.170 align:start position:0% peer-to-peer network now we've been 00:19:49.170 --> 00:19:50.540 align:start position:0% peer-to-peer network now we've been working<00:19:49.230> on<00:19:49.620> these<00:19:49.710> technologies<00:19:50.070> for<00:19:50.490> the 00:19:50.540 --> 00:19:50.550 align:start position:0% working on these technologies for the 00:19:50.550 --> 00:19:53.320 align:start position:0% working on these technologies for the last<00:19:50.670> 12<00:19:50.940> months<00:19:51.410> we're<00:19:52.410> getting<00:19:52.710> ready<00:19:52.830> for<00:19:52.980> a 00:19:53.320 --> 00:19:53.330 align:start position:0% last 12 months we're getting ready for a 00:19:53.330 --> 00:19:56.180 align:start position:0% last 12 months we're getting ready for a public<00:19:54.330> beta<00:19:54.510> and<00:19:55.020> our<00:19:55.230> test<00:19:55.530> net<00:19:55.740> launched<00:19:55.950> in 00:19:56.180 --> 00:19:56.190 align:start position:0% public beta and our test net launched in 00:19:56.190 --> 00:19:58.160 align:start position:0% public beta and our test net launched in q1<00:19:56.460> of<00:19:56.610> next<00:19:57.000> year<00:19:57.210> and<00:19:57.570> we're<00:19:57.840> starting<00:19:58.140> to 00:19:58.160 --> 00:19:58.170 align:start position:0% q1 of next year and we're starting to 00:19:58.170 --> 00:20:00.919 align:start position:0% q1 of next year and we're starting to work<00:19:58.440> with<00:19:58.470> some<00:19:59.780> independent<00:20:00.780> software 00:20:00.919 --> 00:20:00.929 align:start position:0% work with some independent software 00:20:00.929 --> 00:20:01.700 align:start position:0% work with some independent software companies 00:20:01.700 --> 00:20:01.710 align:start position:0% companies 00:20:01.710 --> 00:20:04.190 align:start position:0% companies to<00:20:02.100> build<00:20:02.310> an<00:20:02.580> individual<00:20:03.270> contributors<00:20:03.750> to 00:20:04.190 --> 00:20:04.200 align:start position:0% to build an individual contributors to 00:20:04.200 --> 00:20:05.540 align:start position:0% to build an individual contributors to build<00:20:04.410> out<00:20:04.560> the<00:20:04.680> infrastructure<00:20:05.250> and<00:20:05.430> to 00:20:05.540 --> 00:20:05.550 align:start position:0% build out the infrastructure and to 00:20:05.550 --> 00:20:07.460 align:start position:0% build out the infrastructure and to build<00:20:05.730> some<00:20:05.970> of<00:20:06.090> the<00:20:06.210> applications<00:20:07.200> on<00:20:07.350> this 00:20:07.460 --> 00:20:07.470 align:start position:0% build some of the applications on this 00:20:07.470 --> 00:20:09.710 align:start position:0% build some of the applications on this platform<00:20:07.790> if<00:20:08.790> you're<00:20:09.000> interested<00:20:09.420> in<00:20:09.510> any<00:20:09.630> of 00:20:09.710 --> 00:20:09.720 align:start position:0% platform if you're interested in any of 00:20:09.720 --> 00:20:11.480 align:start position:0% platform if you're interested in any of these<00:20:09.810> technologies<00:20:10.440> or<00:20:10.590> you'd<00:20:11.040> like<00:20:11.220> to<00:20:11.340> come 00:20:11.480 --> 00:20:11.490 align:start position:0% these technologies or you'd like to come 00:20:11.490 --> 00:20:13.670 align:start position:0% these technologies or you'd like to come and<00:20:11.520> collaborate<00:20:12.060> with<00:20:12.180> us<00:20:12.330> that<00:20:13.110> the<00:20:13.320> team<00:20:13.530> is 00:20:13.670 --> 00:20:13.680 align:start position:0% and collaborate with us that the team is 00:20:13.680 --> 00:20:15.440 align:start position:0% and collaborate with us that the team is here<00:20:13.890> this<00:20:14.040> week<00:20:14.340> please<00:20:14.700> come<00:20:14.970> and<00:20:15.000> approach 00:20:15.440 --> 00:20:15.450 align:start position:0% here this week please come and approach 00:20:15.450 --> 00:20:17.150 align:start position:0% here this week please come and approach us<00:20:15.630> and<00:20:15.780> we'd<00:20:15.870> love<00:20:15.990> to<00:20:16.050> talk<00:20:16.170> to<00:20:16.350> you<00:20:16.530> and 00:20:17.150 --> 00:20:17.160 align:start position:0% us and we'd love to talk to you and 00:20:17.160 --> 00:20:18.650 align:start position:0% us and we'd love to talk to you and thanks<00:20:17.640> very<00:20:17.700> much<00:20:17.850> for<00:20:17.970> taking<00:20:18.180> a<00:20:18.360> first<00:20:18.540> look 00:20:18.650 --> 00:20:18.660 align:start position:0% thanks very much for taking a first look 00:20:18.660 --> 00:20:21.170 align:start position:0% thanks very much for taking a first look at<00:20:18.840> wireline<00:20:19.910> Thanks 00:20:21.170 --> 00:20:21.180 align:start position:0% at wireline Thanks 00:20:21.180 --> 00:20:31.460 align:start position:0% at wireline Thanks [Applause] 00:20:31.460 --> 00:20:31.470 align:start position:0% 00:20:31.470 --> 00:20:33.530 align:start position:0% you