WEBVTT Kind: captions Language: en 00:00:16.460 --> 00:00:18.769 align:start position:0% alright<00:00:17.460> shall<00:00:18.240> we<00:00:18.270> begin 00:00:18.769 --> 00:00:18.779 align:start position:0% alright shall we begin 00:00:18.779 --> 00:00:24.170 align:start position:0% alright shall we begin let's<00:00:19.740> do<00:00:19.890> it<00:00:21.060> so<00:00:21.390> my<00:00:22.050> name<00:00:22.170> is<00:00:22.199> Juan<00:00:23.090> one<00:00:24.090> of 00:00:24.170 --> 00:00:24.180 align:start position:0% let's do it so my name is Juan one of 00:00:24.180 --> 00:00:27.259 align:start position:0% let's do it so my name is Juan one of the<00:00:24.300> people<00:00:24.510> behind<00:00:24.869> ipfs<00:00:25.650> and<00:00:26.150> today<00:00:27.150> I'm 00:00:27.259 --> 00:00:27.269 align:start position:0% the people behind ipfs and today I'm 00:00:27.269 --> 00:00:29.120 align:start position:0% the people behind ipfs and today I'm gonna<00:00:27.359> talk<00:00:27.630> to<00:00:27.660> you<00:00:27.869> about<00:00:27.990> data<00:00:28.410> and<00:00:28.710> data 00:00:29.120 --> 00:00:29.130 align:start position:0% gonna talk to you about data and data 00:00:29.130 --> 00:00:32.299 align:start position:0% gonna talk to you about data and data structures<00:00:30.260> so<00:00:31.260> the<00:00:31.560> talk<00:00:31.859> is<00:00:31.980> structured 00:00:32.299 --> 00:00:32.309 align:start position:0% structures so the talk is structured 00:00:32.309 --> 00:00:33.410 align:start position:0% structures so the talk is structured this<00:00:32.460> way<00:00:32.520> I'll<00:00:32.880> give<00:00:33.000> you<00:00:33.090> a<00:00:33.180> brief 00:00:33.410 --> 00:00:33.420 align:start position:0% this way I'll give you a brief 00:00:33.420 --> 00:00:36.049 align:start position:0% this way I'll give you a brief introduction<00:00:33.870> to<00:00:34.110> ipfs<00:00:34.880> actually<00:00:35.880> how<00:00:36.000> many 00:00:36.049 --> 00:00:36.059 align:start position:0% introduction to ipfs actually how many 00:00:36.059 --> 00:00:38.090 align:start position:0% introduction to ipfs actually how many people<00:00:36.420> here<00:00:36.660> know<00:00:36.690> already<00:00:37.620> what<00:00:37.860> I<00:00:37.890> think<00:00:38.040> if 00:00:38.090 --> 00:00:38.100 align:start position:0% people here know already what I think if 00:00:38.100 --> 00:00:41.569 align:start position:0% people here know already what I think if sis<00:00:38.399> Wow<00:00:39.300> awesome<00:00:40.309> that's<00:00:41.309> a<00:00:41.430> great 00:00:41.569 --> 00:00:41.579 align:start position:0% sis Wow awesome that's a great 00:00:41.579 --> 00:00:44.930 align:start position:0% sis Wow awesome that's a great distribution<00:00:42.530> so<00:00:43.530> that'll<00:00:44.129> go<00:00:44.250> really<00:00:44.399> quick 00:00:44.930 --> 00:00:44.940 align:start position:0% distribution so that'll go really quick 00:00:44.940 --> 00:00:49.040 align:start position:0% distribution so that'll go really quick we'll<00:00:45.719> cover<00:00:46.140> the<00:00:46.410> IP<00:00:46.680> LD<00:00:47.280> data<00:00:47.789> model<00:00:48.090> and 00:00:49.040 --> 00:00:49.050 align:start position:0% we'll cover the IP LD data model and 00:00:49.050 --> 00:00:50.450 align:start position:0% we'll cover the IP LD data model and then<00:00:49.200> we'll<00:00:49.379> talk<00:00:49.559> about<00:00:49.620> use<00:00:49.980> cases<00:00:50.190> and 00:00:50.450 --> 00:00:50.460 align:start position:0% then we'll talk about use cases and 00:00:50.460 --> 00:00:53.180 align:start position:0% then we'll talk about use cases and examples<00:00:50.940> of<00:00:51.149> ipfs<00:00:52.079> and<00:00:52.379> data<00:00:52.530> structures<00:00:52.829> and 00:00:53.180 --> 00:00:53.190 align:start position:0% examples of ipfs and data structures and 00:00:53.190 --> 00:00:54.970 align:start position:0% examples of ipfs and data structures and so<00:00:53.340> on 00:00:54.970 --> 00:00:54.980 align:start position:0% so on 00:00:54.980 --> 00:00:57.950 align:start position:0% so on alright<00:00:55.980> so<00:00:56.219> ipfs<00:00:57.000> another<00:00:57.420> name<00:00:57.629> for<00:00:57.780> it<00:00:57.840> is 00:00:57.950 --> 00:00:57.960 align:start position:0% alright so ipfs another name for it is 00:00:57.960 --> 00:01:00.650 align:start position:0% alright so ipfs another name for it is the<00:00:58.109> distributed<00:00:58.800> web<00:00:58.980> or<00:00:59.280> the<00:00:59.730> permanent<00:01:00.149> web 00:01:00.650 --> 00:01:00.660 align:start position:0% the distributed web or the permanent web 00:01:00.660 --> 00:01:03.349 align:start position:0% the distributed web or the permanent web or<00:01:00.899> the<00:01:01.410> merkel<00:01:02.010> web<00:01:02.399> in<00:01:02.730> honor<00:01:02.940> of<00:01:03.030> ralph 00:01:03.349 --> 00:01:03.359 align:start position:0% or the merkel web in honor of ralph 00:01:03.359 --> 00:01:07.670 align:start position:0% or the merkel web in honor of ralph merkle<00:01:03.949> and<00:01:04.949> in<00:01:05.129> a<00:01:05.220> sense<00:01:05.430> it's<00:01:05.760> this<00:01:06.650> kind<00:01:07.650> of 00:01:07.670 --> 00:01:07.680 align:start position:0% merkle and in a sense it's this kind of 00:01:07.680 --> 00:01:10.399 align:start position:0% merkle and in a sense it's this kind of evolution<00:01:07.920> of<00:01:08.600> how<00:01:09.600> the<00:01:09.659> NRI<00:01:09.960> on<00:01:10.080> the<00:01:10.170> web<00:01:10.290> were 00:01:10.399 --> 00:01:10.409 align:start position:0% evolution of how the NRI on the web were 00:01:10.409 --> 00:01:11.690 align:start position:0% evolution of how the NRI on the web were structured<00:01:10.799> and<00:01:10.979> I<00:01:11.010> think<00:01:11.159> everyone<00:01:11.430> here 00:01:11.690 --> 00:01:11.700 align:start position:0% structured and I think everyone here 00:01:11.700 --> 00:01:15.410 align:start position:0% structured and I think everyone here both<00:01:12.680> coming<00:01:13.680> from<00:01:13.799> blockchain<00:01:14.640> history<00:01:15.030> 2 00:01:15.410 --> 00:01:15.420 align:start position:0% both coming from blockchain history 2 00:01:15.420 --> 00:01:17.330 align:start position:0% both coming from blockchain history 2 through<00:01:15.990> aetherium<00:01:16.290> and<00:01:16.770> a<00:01:16.950> whole<00:01:17.130> bunch<00:01:17.280> of 00:01:17.330 --> 00:01:17.340 align:start position:0% through aetherium and a whole bunch of 00:01:17.340 --> 00:01:18.830 align:start position:0% through aetherium and a whole bunch of other<00:01:17.490> interesting<00:01:18.030> technologies<00:01:18.570> that<00:01:18.720> are 00:01:18.830 --> 00:01:18.840 align:start position:0% other interesting technologies that are 00:01:18.840 --> 00:01:19.550 align:start position:0% other interesting technologies that are happening<00:01:18.990> right<00:01:19.290> now 00:01:19.550 --> 00:01:19.560 align:start position:0% happening right now 00:01:19.560 --> 00:01:22.130 align:start position:0% happening right now sort<00:01:20.400> of<00:01:20.490> see<00:01:20.700> what's<00:01:21.119> going<00:01:21.450> on<00:01:21.630> or<00:01:21.840> what<00:01:21.990> has 00:01:22.130 --> 00:01:22.140 align:start position:0% sort of see what's going on or what has 00:01:22.140 --> 00:01:23.570 align:start position:0% sort of see what's going on or what has been<00:01:22.290> going<00:01:22.560> on<00:01:22.650> for<00:01:22.860> the<00:01:22.920> last<00:01:22.950> three<00:01:23.280> years 00:01:23.570 --> 00:01:23.580 align:start position:0% been going on for the last three years 00:01:23.580 --> 00:01:26.060 align:start position:0% been going on for the last three years as<00:01:23.790> this<00:01:23.970> this<00:01:24.479> total<00:01:24.900> reinvention<00:01:25.080> of<00:01:25.740> how<00:01:26.009> to 00:01:26.060 --> 00:01:26.070 align:start position:0% as this this total reinvention of how to 00:01:26.070 --> 00:01:28.730 align:start position:0% as this this total reinvention of how to do<00:01:26.810> distributed<00:01:27.810> computing<00:01:28.170> and<00:01:28.320> distributed 00:01:28.730 --> 00:01:28.740 align:start position:0% do distributed computing and distributed 00:01:28.740 --> 00:01:32.149 align:start position:0% do distributed computing and distributed networks<00:01:29.400> and<00:01:29.640> in<00:01:29.909> general<00:01:30.270> and<00:01:31.049> so<00:01:31.890> this<00:01:32.040> is 00:01:32.149 --> 00:01:32.159 align:start position:0% networks and in general and so this is 00:01:32.159 --> 00:01:34.280 align:start position:0% networks and in general and so this is this<00:01:32.400> of<00:01:32.579> course<00:01:32.670> layers<00:01:33.210> on<00:01:33.509> top<00:01:33.689> of<00:01:33.869> the<00:01:34.140> old 00:01:34.280 --> 00:01:34.290 align:start position:0% this of course layers on top of the old 00:01:34.290 --> 00:01:36.289 align:start position:0% this of course layers on top of the old internet<00:01:34.770> and<00:01:34.920> so<00:01:35.040> on<00:01:35.189> but<00:01:35.970> what's<00:01:36.180> really 00:01:36.289 --> 00:01:36.299 align:start position:0% internet and so on but what's really 00:01:36.299 --> 00:01:37.999 align:start position:0% internet and so on but what's really happening<00:01:36.780> is<00:01:36.900> that<00:01:36.990> we're<00:01:37.140> taking<00:01:37.290> the<00:01:37.530> web 00:01:37.999 --> 00:01:38.009 align:start position:0% happening is that we're taking the web 00:01:38.009 --> 00:01:40.370 align:start position:0% happening is that we're taking the web applications<00:01:38.579> of<00:01:38.820> the<00:01:39.000> you<00:01:39.390> know<00:01:39.509> web<00:01:39.659> 1.0<00:01:40.350> or 00:01:40.370 --> 00:01:40.380 align:start position:0% applications of the you know web 1.0 or 00:01:40.380 --> 00:01:44.240 align:start position:0% applications of the you know web 1.0 or web<00:01:40.650> 2.0<00:01:41.100> world<00:01:41.430> and<00:01:41.869> we<00:01:42.869> are<00:01:43.070> separating<00:01:44.070> them 00:01:44.240 --> 00:01:44.250 align:start position:0% web 2.0 world and we are separating them 00:01:44.250 --> 00:01:48.109 align:start position:0% web 2.0 world and we are separating them from<00:01:44.280> their<00:01:45.149> physical<00:01:45.509> location<00:01:45.869> in<00:01:47.119> servers 00:01:48.109 --> 00:01:48.119 align:start position:0% from their physical location in servers 00:01:48.119 --> 00:01:49.999 align:start position:0% from their physical location in servers and<00:01:48.210> so<00:01:48.390> on<00:01:48.570> and<00:01:48.780> distributed<00:01:49.470> distributing 00:01:49.999 --> 00:01:50.009 align:start position:0% and so on and distributed distributing 00:01:50.009 --> 00:01:55.100 align:start position:0% and so on and distributed distributing them<00:01:50.280> across<00:01:50.520> different<00:01:51.509> hosts<00:01:52.579> so<00:01:53.869> ipfs<00:01:54.869> is<00:01:55.079> a 00:01:55.100 --> 00:01:55.110 align:start position:0% them across different hosts so ipfs is a 00:01:55.110 --> 00:01:56.810 align:start position:0% them across different hosts so ipfs is a protocol<00:01:55.619> to<00:01:55.799> upgrade<00:01:56.219> the<00:01:56.340> web<00:01:56.490> because<00:01:56.790> the 00:01:56.810 --> 00:01:56.820 align:start position:0% protocol to upgrade the web because the 00:01:56.820 --> 00:01:58.249 align:start position:0% protocol to upgrade the web because the web<00:01:56.939> has<00:01:57.240> some<00:01:57.390> problems<00:01:57.750> I<00:01:57.960> won't<00:01:58.110> go<00:01:58.229> over 00:01:58.249 --> 00:01:58.259 align:start position:0% web has some problems I won't go over 00:01:58.259 --> 00:02:01.100 align:start position:0% web has some problems I won't go over these<00:01:58.700> there<00:01:59.700> it's<00:02:00.030> I<00:02:00.329> think<00:02:00.509> most<00:02:00.780> of<00:02:00.899> you<00:02:00.990> are 00:02:01.100 --> 00:02:01.110 align:start position:0% these there it's I think most of you are 00:02:01.110 --> 00:02:02.300 align:start position:0% these there it's I think most of you are familiar<00:02:01.170> with<00:02:01.439> them<00:02:01.649> it's<00:02:01.860> an<00:02:01.950> efficient 00:02:02.300 --> 00:02:02.310 align:start position:0% familiar with them it's an efficient 00:02:02.310 --> 00:02:05.539 align:start position:0% familiar with them it's an efficient doesn't<00:02:02.700> work<00:02:02.820> offline<00:02:03.590> links<00:02:04.590> break<00:02:04.890> central 00:02:05.539 --> 00:02:05.549 align:start position:0% doesn't work offline links break central 00:02:05.549 --> 00:02:09.020 align:start position:0% doesn't work offline links break central points<00:02:06.090> of<00:02:06.180> failure<00:02:06.270> and<00:02:06.600> so<00:02:06.780> on<00:02:07.009> and<00:02:08.009> the<00:02:08.759> gist 00:02:09.020 --> 00:02:09.030 align:start position:0% points of failure and so on and the gist 00:02:09.030 --> 00:02:11.070 align:start position:0% points of failure and so on and the gist is<00:02:09.149> to<00:02:09.300> try<00:02:09.509> and<00:02:09.569> creates<00:02:10.050> what 00:02:11.070 --> 00:02:11.080 align:start position:0% is to try and creates what 00:02:11.080 --> 00:02:13.440 align:start position:0% is to try and creates what the<00:02:11.200> web<00:02:11.350> look<00:02:11.620> like<00:02:11.860> if<00:02:12.100> you<00:02:12.160> took<00:02:12.550> a<00:02:12.790> Merkel 00:02:13.440 --> 00:02:13.450 align:start position:0% the web look like if you took a Merkel 00:02:13.450 --> 00:02:15.270 align:start position:0% the web look like if you took a Merkel tree<00:02:13.630> or<00:02:13.810> a<00:02:13.840> Merkel<00:02:14.110> chain<00:02:14.320> and<00:02:14.620> put<00:02:15.190> it 00:02:15.270 --> 00:02:15.280 align:start position:0% tree or a Merkel chain and put it 00:02:15.280 --> 00:02:17.910 align:start position:0% tree or a Merkel chain and put it underneath<00:02:15.640> the<00:02:16.060> web<00:02:16.210> itself<00:02:16.540> so<00:02:16.900> what<00:02:17.800> would 00:02:17.910 --> 00:02:17.920 align:start position:0% underneath the web itself so what would 00:02:17.920 --> 00:02:21.420 align:start position:0% underneath the web itself so what would happen<00:02:18.160> if<00:02:18.520> you<00:02:18.820> gained<00:02:19.150> immutability<00:02:20.430> for 00:02:21.420 --> 00:02:21.430 align:start position:0% happen if you gained immutability for 00:02:21.430 --> 00:02:25.500 align:start position:0% happen if you gained immutability for distributing<00:02:22.060> content<00:02:22.300> on<00:02:22.720> the<00:02:23.020> web<00:02:23.550> I<00:02:24.550> you 00:02:25.500 --> 00:02:25.510 align:start position:0% distributing content on the web I you 00:02:25.510 --> 00:02:26.970 align:start position:0% distributing content on the web I you can<00:02:25.660> think<00:02:25.840> of<00:02:25.900> data<00:02:26.140> structures<00:02:26.530> like<00:02:26.590> gits 00:02:26.970 --> 00:02:26.980 align:start position:0% can think of data structures like gits 00:02:26.980 --> 00:02:29.580 align:start position:0% can think of data structures like gits and<00:02:27.610> the<00:02:27.790> amazing<00:02:28.300> power<00:02:28.810> of<00:02:29.140> distributed 00:02:29.580 --> 00:02:29.590 align:start position:0% and the amazing power of distributed 00:02:29.590 --> 00:02:30.810 align:start position:0% and the amazing power of distributed computing<00:02:29.620> that<00:02:30.040> you<00:02:30.100> get<00:02:30.250> out<00:02:30.340> of<00:02:30.460> that<00:02:30.550> or 00:02:30.810 --> 00:02:30.820 align:start position:0% computing that you get out of that or 00:02:30.820 --> 00:02:32.370 align:start position:0% computing that you get out of that or just<00:02:30.850> version<00:02:31.450> control<00:02:31.750> the<00:02:31.960> tribute<00:02:32.170> version 00:02:32.370 --> 00:02:32.380 align:start position:0% just version control the tribute version 00:02:32.380 --> 00:02:35.160 align:start position:0% just version control the tribute version control<00:02:32.790> you<00:02:33.790> can<00:02:33.970> think<00:02:34.360> about<00:02:34.450> aetherium 00:02:35.160 --> 00:02:35.170 align:start position:0% control you can think about aetherium 00:02:35.170 --> 00:02:37.680 align:start position:0% control you can think about aetherium and<00:02:35.380> the<00:02:35.440> amazing<00:02:35.770> powers<00:02:36.100> of<00:02:36.570> contracts<00:02:37.570> and 00:02:37.680 --> 00:02:37.690 align:start position:0% and the amazing powers of contracts and 00:02:37.690 --> 00:02:39.810 align:start position:0% and the amazing powers of contracts and running<00:02:38.080> programs<00:02:38.500> you<00:02:39.370> know<00:02:39.460> the<00:02:39.550> tribute<00:02:39.760> of 00:02:39.810 --> 00:02:39.820 align:start position:0% running programs you know the tribute of 00:02:39.820 --> 00:02:42.030 align:start position:0% running programs you know the tribute of sense<00:02:39.970> and<00:02:40.240> of<00:02:40.300> course<00:02:40.510> before<00:02:41.230> the<00:02:41.530> etherium 00:02:42.030 --> 00:02:42.040 align:start position:0% sense and of course before the etherium 00:02:42.040 --> 00:02:43.440 align:start position:0% sense and of course before the etherium bitcoin<00:02:42.400> and<00:02:42.550> so<00:02:42.640> on<00:02:42.790> all<00:02:42.970> of<00:02:43.120> these<00:02:43.270> are 00:02:43.440 --> 00:02:43.450 align:start position:0% bitcoin and so on all of these are 00:02:43.450 --> 00:02:46.650 align:start position:0% bitcoin and so on all of these are Merkel<00:02:44.230> trees<00:02:44.470> and<00:02:44.830> what<00:02:45.490> ipfs<00:02:45.820> really<00:02:46.150> is<00:02:46.360> is 00:02:46.650 --> 00:02:46.660 align:start position:0% Merkel trees and what ipfs really is is 00:02:46.660 --> 00:02:48.870 align:start position:0% Merkel trees and what ipfs really is is this<00:02:46.780> massive<00:02:47.140> Merkel<00:02:47.860> forest<00:02:48.280> that's<00:02:48.670> kind 00:02:48.870 --> 00:02:48.880 align:start position:0% this massive Merkel forest that's kind 00:02:48.880 --> 00:02:50.790 align:start position:0% this massive Merkel forest that's kind of<00:02:48.940> like<00:02:49.120> the<00:02:49.270> the<00:02:49.300> intuitive<00:02:49.930> description<00:02:50.530> of 00:02:50.790 --> 00:02:50.800 align:start position:0% of like the the intuitive description of 00:02:50.800 --> 00:02:53.160 align:start position:0% of like the the intuitive description of IPF<00:02:51.280> assets<00:02:51.640> saying<00:02:51.850> let's<00:02:52.150> take<00:02:52.450> let's<00:02:52.930> write 00:02:53.160 --> 00:02:53.170 align:start position:0% IPF assets saying let's take let's write 00:02:53.170 --> 00:02:56.430 align:start position:0% IPF assets saying let's take let's write one<00:02:53.470> transport<00:02:54.130> protocol<00:02:54.520> to<00:02:55.440> layer 00:02:56.430 --> 00:02:56.440 align:start position:0% one transport protocol to layer 00:02:56.440 --> 00:02:58.350 align:start position:0% one transport protocol to layer underneath<00:02:56.860> the<00:02:57.160> web<00:02:57.310> and<00:02:57.580> other<00:02:58.000> protocols 00:02:58.350 --> 00:02:58.360 align:start position:0% underneath the web and other protocols 00:02:58.360 --> 00:03:02.910 align:start position:0% underneath the web and other protocols as<00:02:58.750> well<00:02:58.780> and<00:02:59.430> build<00:03:00.430> this<00:03:00.750> distributed<00:03:01.920> data 00:03:02.910 --> 00:03:02.920 align:start position:0% as well and build this distributed data 00:03:02.920 --> 00:03:06.660 align:start position:0% as well and build this distributed data structure<00:03:03.840> transport<00:03:04.840> that<00:03:05.770> is<00:03:05.830> all<00:03:06.130> Merkel 00:03:06.660 --> 00:03:06.670 align:start position:0% structure transport that is all Merkel 00:03:06.670 --> 00:03:09.780 align:start position:0% structure transport that is all Merkel addressed<00:03:07.680> cool<00:03:08.770> so<00:03:08.860> imagine<00:03:09.340> being<00:03:09.550> able<00:03:09.640> to 00:03:09.780 --> 00:03:09.790 align:start position:0% addressed cool so imagine being able to 00:03:09.790 --> 00:03:13.170 align:start position:0% addressed cool so imagine being able to link<00:03:10.030> across<00:03:11.220> different<00:03:12.220> aetherium<00:03:12.910> chains 00:03:13.170 --> 00:03:13.180 align:start position:0% link across different aetherium chains 00:03:13.180 --> 00:03:15.540 align:start position:0% link across different aetherium chains and<00:03:13.660> being<00:03:13.930> able<00:03:13.990> to<00:03:14.110> link<00:03:14.320> across<00:03:14.560> Bitcoin 00:03:15.540 --> 00:03:15.550 align:start position:0% and being able to link across Bitcoin 00:03:15.550 --> 00:03:17.130 align:start position:0% and being able to link across Bitcoin and<00:03:15.730> aetherium<00:03:16.150> and<00:03:16.300> being<00:03:16.450> able<00:03:16.540> to<00:03:16.660> link<00:03:16.870> to 00:03:17.130 --> 00:03:17.140 align:start position:0% and aetherium and being able to link to 00:03:17.140 --> 00:03:18.780 align:start position:0% and aetherium and being able to link to get<00:03:17.440> repos<00:03:17.830> and<00:03:18.190> be<00:03:18.310> able<00:03:18.400> to<00:03:18.519> link<00:03:18.700> to 00:03:18.780 --> 00:03:18.790 align:start position:0% get repos and be able to link to 00:03:18.790 --> 00:03:21.600 align:start position:0% get repos and be able to link to BitTorrent<00:03:19.780> torrents<00:03:20.470> or<00:03:20.769> being<00:03:21.010> able<00:03:21.430> to 00:03:21.600 --> 00:03:21.610 align:start position:0% BitTorrent torrents or being able to 00:03:21.610 --> 00:03:23.850 align:start position:0% BitTorrent torrents or being able to link<00:03:21.820> directly<00:03:22.150> into<00:03:22.810> specific<00:03:23.290> commits 00:03:23.850 --> 00:03:23.860 align:start position:0% link directly into specific commits 00:03:23.860 --> 00:03:25.620 align:start position:0% link directly into specific commits inside<00:03:24.730> github<00:03:25.090> so<00:03:25.209> you<00:03:25.300> could<00:03:25.420> create<00:03:25.510> a 00:03:25.620 --> 00:03:25.630 align:start position:0% inside github so you could create a 00:03:25.630 --> 00:03:28.110 align:start position:0% inside github so you could create a contract<00:03:26.050> and<00:03:26.170> say<00:03:26.290> whoever<00:03:27.250> you<00:03:28.030> know 00:03:28.110 --> 00:03:28.120 align:start position:0% contract and say whoever you know 00:03:28.120 --> 00:03:29.610 align:start position:0% contract and say whoever you know patches<00:03:28.480> this<00:03:28.600> commit<00:03:28.959> or<00:03:29.290> something 00:03:29.610 --> 00:03:29.620 align:start position:0% patches this commit or something 00:03:29.620 --> 00:03:33.170 align:start position:0% patches this commit or something successfully<00:03:30.450> get<00:03:31.450> some<00:03:31.660> money<00:03:31.780> or<00:03:31.900> something 00:03:33.170 --> 00:03:33.180 align:start position:0% successfully get some money or something 00:03:33.180 --> 00:03:37.530 align:start position:0% successfully get some money or something and<00:03:34.180> in<00:03:34.930> the<00:03:35.140> ipfs<00:03:35.680> world<00:03:36.010> which<00:03:36.580> is<00:03:36.910> a<00:03:37.060> world 00:03:37.530 --> 00:03:37.540 align:start position:0% and in the ipfs world which is a world 00:03:37.540 --> 00:03:39.930 align:start position:0% and in the ipfs world which is a world on<00:03:37.840> its<00:03:37.989> own<00:03:38.310> there's<00:03:39.310> a<00:03:39.400> whole<00:03:39.610> bunch<00:03:39.790> of 00:03:39.930 --> 00:03:39.940 align:start position:0% on its own there's a whole bunch of 00:03:39.940 --> 00:03:41.280 align:start position:0% on its own there's a whole bunch of different<00:03:40.120> protocols<00:03:40.510> and<00:03:40.900> we<00:03:40.989> have<00:03:41.140> this 00:03:41.280 --> 00:03:41.290 align:start position:0% different protocols and we have this 00:03:41.290 --> 00:03:44.130 align:start position:0% different protocols and we have this this<00:03:42.239> view<00:03:43.239> of<00:03:43.269> the<00:03:43.450> world<00:03:43.570> that<00:03:43.870> looks<00:03:44.080> a 00:03:44.130 --> 00:03:44.140 align:start position:0% this view of the world that looks a 00:03:44.140 --> 00:03:45.300 align:start position:0% this view of the world that looks a little<00:03:44.230> bit<00:03:44.380> like<00:03:44.530> this<00:03:44.650> with<00:03:44.890> a<00:03:44.920> whole<00:03:45.130> bunch 00:03:45.300 --> 00:03:45.310 align:start position:0% little bit like this with a whole bunch 00:03:45.310 --> 00:03:47.759 align:start position:0% little bit like this with a whole bunch of<00:03:45.370> different<00:03:46.080> sections<00:03:47.080> for<00:03:47.200> these 00:03:47.759 --> 00:03:47.769 align:start position:0% of different sections for these 00:03:47.769 --> 00:03:48.600 align:start position:0% of different sections for these protocols 00:03:48.600 --> 00:03:48.610 align:start position:0% protocols 00:03:48.610 --> 00:03:51.060 align:start position:0% protocols kind<00:03:49.510> of<00:03:49.570> on<00:03:49.660> top<00:03:49.810> of<00:03:49.959> the<00:03:50.080> on<00:03:50.320> the<00:03:50.470> lower<00:03:50.739> level 00:03:51.060 --> 00:03:51.070 align:start position:0% kind of on top of the on the lower level 00:03:51.070 --> 00:03:53.160 align:start position:0% kind of on top of the on the lower level Network<00:03:51.580> and<00:03:51.850> this<00:03:52.209> is<00:03:52.360> of<00:03:52.570> course<00:03:52.720> all<00:03:52.930> sits 00:03:53.160 --> 00:03:53.170 align:start position:0% Network and this is of course all sits 00:03:53.170 --> 00:03:55.100 align:start position:0% Network and this is of course all sits on<00:03:53.260> top<00:03:53.350> of<00:03:53.470> IP<00:03:53.560> although<00:03:54.340> it<00:03:54.430> doesn't<00:03:54.580> need<00:03:54.790> to 00:03:55.100 --> 00:03:55.110 align:start position:0% on top of IP although it doesn't need to 00:03:55.110 --> 00:03:58.259 align:start position:0% on top of IP although it doesn't need to on<00:03:56.110> top<00:03:56.290> of<00:03:56.440> transports<00:03:57.070> on<00:03:57.280> top<00:03:57.430> of<00:03:57.550> different 00:03:58.259 --> 00:03:58.269 align:start position:0% on top of transports on top of different 00:03:58.269 --> 00:04:00.600 align:start position:0% on top of transports on top of different routing<00:03:58.890> different<00:03:59.890> ways<00:04:00.010> of<00:04:00.100> doing<00:04:00.190> routing 00:04:00.600 --> 00:04:00.610 align:start position:0% routing different ways of doing routing 00:04:00.610 --> 00:04:03.990 align:start position:0% routing different ways of doing routing we<00:04:01.510> want<00:04:01.780> to<00:04:01.870> layer<00:04:02.140> what<00:04:03.130> we're<00:04:03.250> calling<00:04:03.400> IPL 00:04:03.990 --> 00:04:04.000 align:start position:0% we want to layer what we're calling IPL 00:04:04.000 --> 00:04:06.270 align:start position:0% we want to layer what we're calling IPL D<00:04:04.180> which<00:04:04.510> is<00:04:04.540> the<00:04:04.720> Merkel<00:04:05.410> dog<00:04:05.560> or<00:04:05.830> the<00:04:06.010> Merkel 00:04:06.270 --> 00:04:06.280 align:start position:0% D which is the Merkel dog or the Merkel 00:04:06.280 --> 00:04:09.509 align:start position:0% D which is the Merkel dog or the Merkel web<00:04:06.420> as<00:04:07.420> this<00:04:07.959> common<00:04:08.739> data<00:04:09.010> structure<00:04:09.489> that 00:04:09.509 --> 00:04:09.519 align:start position:0% web as this common data structure that 00:04:09.519 --> 00:04:13.229 align:start position:0% web as this common data structure that we<00:04:09.790> can<00:04:09.910> all<00:04:10.290> use<00:04:11.290> for<00:04:11.709> expressing<00:04:12.700> our<00:04:12.940> data 00:04:13.229 --> 00:04:13.239 align:start position:0% we can all use for expressing our data 00:04:13.239 --> 00:04:15.270 align:start position:0% we can all use for expressing our data structures<00:04:13.630> it's<00:04:14.080> kind<00:04:14.290> of<00:04:14.350> the<00:04:14.470> same<00:04:14.650> idea<00:04:14.680> as 00:04:15.270 --> 00:04:15.280 align:start position:0% structures it's kind of the same idea as 00:04:15.280 --> 00:04:17.880 align:start position:0% structures it's kind of the same idea as the<00:04:15.760> Semantic<00:04:16.180> Web<00:04:16.209> but<00:04:17.200> instead<00:04:17.470> of<00:04:17.620> just 00:04:17.880 --> 00:04:17.890 align:start position:0% the Semantic Web but instead of just 00:04:17.890 --> 00:04:19.770 align:start position:0% the Semantic Web but instead of just having<00:04:18.310> an<00:04:18.400> object<00:04:18.519> definition<00:04:19.209> imagine<00:04:19.660> if 00:04:19.770 --> 00:04:19.780 align:start position:0% having an object definition imagine if 00:04:19.780 --> 00:04:21.570 align:start position:0% having an object definition imagine if the<00:04:19.900> object<00:04:20.200> definition<00:04:20.590> linked<00:04:21.070> between 00:04:21.570 --> 00:04:21.580 align:start position:0% the object definition linked between 00:04:21.580 --> 00:04:23.550 align:start position:0% the object definition linked between objects<00:04:22.270> with<00:04:22.870> hashes 00:04:23.550 --> 00:04:23.560 align:start position:0% objects with hashes 00:04:23.560 --> 00:04:26.100 align:start position:0% objects with hashes that<00:04:24.220> that's<00:04:24.430> the<00:04:24.730> the<00:04:24.970> heart<00:04:25.300> of<00:04:25.510> ipfs<00:04:25.900> that's 00:04:26.100 --> 00:04:26.110 align:start position:0% that that's the the heart of ipfs that's 00:04:26.110 --> 00:04:28.620 align:start position:0% that that's the the heart of ipfs that's like<00:04:26.200> the<00:04:26.350> core<00:04:26.889> what<00:04:27.760> happens<00:04:28.150> when<00:04:28.419> instead 00:04:28.620 --> 00:04:28.630 align:start position:0% like the core what happens when instead 00:04:28.630 --> 00:04:32.190 align:start position:0% like the core what happens when instead of<00:04:28.990> of<00:04:29.380> having<00:04:29.980> a<00:04:30.070> URL<00:04:30.490> that<00:04:30.669> points<00:04:30.870> from<00:04:31.870> one 00:04:32.190 --> 00:04:32.200 align:start position:0% of of having a URL that points from one 00:04:32.200 --> 00:04:34.350 align:start position:0% of of having a URL that points from one object<00:04:32.470> to<00:04:32.860> another<00:04:32.980> using<00:04:33.520> a<00:04:33.700> location<00:04:34.120> what 00:04:34.350 --> 00:04:34.360 align:start position:0% object to another using a location what 00:04:34.360 --> 00:04:37.400 align:start position:0% object to another using a location what happens<00:04:34.690> when<00:04:34.900> you<00:04:35.020> point<00:04:35.320> using<00:04:35.889> hashes<00:04:36.700> and 00:04:37.400 --> 00:04:37.410 align:start position:0% happens when you point using hashes and 00:04:37.410 --> 00:04:39.510 align:start position:0% happens when you point using hashes and this<00:04:38.410> vide<00:04:38.560> has<00:04:38.650> all<00:04:38.830> that's<00:04:39.070> been<00:04:39.190> around<00:04:39.280> for 00:04:39.510 --> 00:04:39.520 align:start position:0% this vide has all that's been around for 00:04:39.520 --> 00:04:42.360 align:start position:0% this vide has all that's been around for a<00:04:39.550> while<00:04:39.700> but<00:04:40.110> this<00:04:41.110> talk<00:04:41.680> will<00:04:41.950> be<00:04:41.980> mostly 00:04:42.360 --> 00:04:42.370 align:start position:0% a while but this talk will be mostly 00:04:42.370 --> 00:04:44.460 align:start position:0% a while but this talk will be mostly about<00:04:42.639> what<00:04:43.150> we're<00:04:43.300> sort<00:04:43.660> of<00:04:43.690> loosely 00:04:44.460 --> 00:04:44.470 align:start position:0% about what we're sort of loosely 00:04:44.470 --> 00:04:46.350 align:start position:0% about what we're sort of loosely describing<00:04:45.160> as<00:04:45.280> the<00:04:45.400> Internet<00:04:45.790> of<00:04:45.820> data<00:04:46.090> or 00:04:46.350 --> 00:04:46.360 align:start position:0% describing as the Internet of data or 00:04:46.360 --> 00:04:48.480 align:start position:0% describing as the Internet of data or Internet<00:04:46.750> of<00:04:46.780> data<00:04:47.020> structures<00:04:47.380> to<00:04:48.160> write<00:04:48.340> on 00:04:48.480 --> 00:04:48.490 align:start position:0% Internet of data structures to write on 00:04:48.490 --> 00:04:51.629 align:start position:0% Internet of data structures to write on top<00:04:48.610> of<00:04:48.820> IP<00:04:49.720> LD<00:04:50.110> and<00:04:50.320> so<00:04:50.950> you've<00:04:51.100> probably<00:04:51.280> seen 00:04:51.629 --> 00:04:51.639 align:start position:0% top of IP LD and so you've probably seen 00:04:51.639 --> 00:04:53.670 align:start position:0% top of IP LD and so you've probably seen something<00:04:51.880> like<00:04:52.000> this<00:04:52.240> where<00:04:52.510> the<00:04:52.930> ipfs<00:04:53.350> model 00:04:53.670 --> 00:04:53.680 align:start position:0% something like this where the ipfs model 00:04:53.680 --> 00:04:56.700 align:start position:0% something like this where the ipfs model is<00:04:53.950> you<00:04:54.550> you<00:04:55.360> take<00:04:55.540> the<00:04:55.630> original<00:04:55.750> HTTP<00:04:56.500> world 00:04:56.700 --> 00:04:56.710 align:start position:0% is you you take the original HTTP world 00:04:56.710 --> 00:04:59.730 align:start position:0% is you you take the original HTTP world of<00:04:57.360> mapping<00:04:58.360> a<00:04:58.419> dns<00:04:58.720> name<00:04:58.900> to<00:04:59.169> an<00:04:59.440> IP<00:04:59.560> address 00:04:59.730 --> 00:04:59.740 align:start position:0% of mapping a dns name to an IP address 00:04:59.740 --> 00:05:01.770 align:start position:0% of mapping a dns name to an IP address which<00:05:00.460> looks<00:05:01.030> kind<00:05:01.270> of<00:05:01.300> like<00:05:01.389> this<00:05:01.570> where 00:05:01.770 --> 00:05:01.780 align:start position:0% which looks kind of like this where 00:05:01.780 --> 00:05:03.000 align:start position:0% which looks kind of like this where you're<00:05:01.900> resolving<00:05:02.260> through<00:05:02.500> the<00:05:02.560> network<00:05:02.860> to 00:05:03.000 --> 00:05:03.010 align:start position:0% you're resolving through the network to 00:05:03.010 --> 00:05:05.760 align:start position:0% you're resolving through the network to a<00:05:03.040> specific<00:05:03.639> host<00:05:03.990> and<00:05:04.990> you<00:05:05.139> instead<00:05:05.380> say<00:05:05.590> hey 00:05:05.760 --> 00:05:05.770 align:start position:0% a specific host and you instead say hey 00:05:05.770 --> 00:05:07.890 align:start position:0% a specific host and you instead say hey let's<00:05:06.100> just<00:05:06.190> take<00:05:06.520> the<00:05:06.729> hash<00:05:07.210> of<00:05:07.450> the<00:05:07.540> content 00:05:07.890 --> 00:05:07.900 align:start position:0% let's just take the hash of the content 00:05:07.900 --> 00:05:10.920 align:start position:0% let's just take the hash of the content itself<00:05:08.139> and<00:05:08.470> use<00:05:08.950> that<00:05:09.130> to<00:05:09.340> address<00:05:09.690> the<00:05:10.690> files 00:05:10.920 --> 00:05:10.930 align:start position:0% itself and use that to address the files 00:05:10.930 --> 00:05:14.610 align:start position:0% itself and use that to address the files and<00:05:11.710> it<00:05:12.400> looks<00:05:12.930> instead<00:05:13.930> of<00:05:14.020> that<00:05:14.260> you<00:05:14.290> get 00:05:14.610 --> 00:05:14.620 align:start position:0% and it looks instead of that you get 00:05:14.620 --> 00:05:16.050 align:start position:0% and it looks instead of that you get something<00:05:14.860> like<00:05:15.010> this<00:05:15.190> where<00:05:15.430> anybody<00:05:15.910> in<00:05:16.030> the 00:05:16.050 --> 00:05:16.060 align:start position:0% something like this where anybody in the 00:05:16.060 --> 00:05:17.879 align:start position:0% something like this where anybody in the network<00:05:16.419> that<00:05:16.450> has<00:05:16.750> the<00:05:16.900> file<00:05:17.080> can<00:05:17.590> serve<00:05:17.770> it 00:05:17.879 --> 00:05:17.889 align:start position:0% network that has the file can serve it 00:05:17.889 --> 00:05:20.219 align:start position:0% network that has the file can serve it to<00:05:17.979> you<00:05:18.100> right<00:05:18.580> this<00:05:18.700> is<00:05:18.850> all<00:05:19.000> super<00:05:19.690> intro 00:05:20.219 --> 00:05:20.229 align:start position:0% to you right this is all super intro 00:05:20.229 --> 00:05:24.960 align:start position:0% to you right this is all super intro ipfs<00:05:21.070> stuff<00:05:22.020> and<00:05:23.220> in<00:05:24.220> a<00:05:24.400> sense<00:05:24.550> what's<00:05:24.760> really 00:05:24.960 --> 00:05:24.970 align:start position:0% ipfs stuff and in a sense what's really 00:05:24.970 --> 00:05:26.430 align:start position:0% ipfs stuff and in a sense what's really going<00:05:25.210> on<00:05:25.330> underneath<00:05:25.540> the<00:05:25.900> hood<00:05:25.930> is<00:05:26.260> that 00:05:26.430 --> 00:05:26.440 align:start position:0% going on underneath the hood is that 00:05:26.440 --> 00:05:29.580 align:start position:0% going on underneath the hood is that that<00:05:26.560> hash<00:05:26.889> is<00:05:27.190> a<00:05:27.940> pointer<00:05:28.630> to<00:05:28.660> a<00:05:29.050> directory 00:05:29.580 --> 00:05:29.590 align:start position:0% that hash is a pointer to a directory 00:05:29.590 --> 00:05:31.350 align:start position:0% that hash is a pointer to a directory you<00:05:30.340> can<00:05:30.370> retrieve<00:05:30.729> the<00:05:30.850> directory<00:05:31.180> because 00:05:31.350 --> 00:05:31.360 align:start position:0% you can retrieve the directory because 00:05:31.360 --> 00:05:34.020 align:start position:0% you can retrieve the directory because you<00:05:32.169> can<00:05:32.320> check<00:05:32.560> you<00:05:33.160> can<00:05:33.310> ask<00:05:33.520> the<00:05:33.729> network 00:05:34.020 --> 00:05:34.030 align:start position:0% you can check you can ask the network 00:05:34.030 --> 00:05:35.640 align:start position:0% you can check you can ask the network for<00:05:34.210> the<00:05:34.300> directory<00:05:34.660> people<00:05:35.080> can<00:05:35.229> return<00:05:35.410> the 00:05:35.640 --> 00:05:35.650 align:start position:0% for the directory people can return the 00:05:35.650 --> 00:05:37.050 align:start position:0% for the directory people can return the directory<00:05:35.979> to<00:05:36.160> you<00:05:36.310> you<00:05:36.490> can<00:05:36.669> check<00:05:36.910> the 00:05:37.050 --> 00:05:37.060 align:start position:0% directory to you you can check the 00:05:37.060 --> 00:05:39.570 align:start position:0% directory to you you can check the content<00:05:37.990> make<00:05:38.140> sure<00:05:38.169> it<00:05:38.380> matches<00:05:38.919> the<00:05:39.130> hash<00:05:39.310> so 00:05:39.570 --> 00:05:39.580 align:start position:0% content make sure it matches the hash so 00:05:39.580 --> 00:05:40.740 align:start position:0% content make sure it matches the hash so that<00:05:39.729> way<00:05:39.820> you<00:05:39.880> don't<00:05:40.060> have<00:05:40.150> to<00:05:40.300> trust<00:05:40.510> anyone 00:05:40.740 --> 00:05:40.750 align:start position:0% that way you don't have to trust anyone 00:05:40.750 --> 00:05:44.190 align:start position:0% that way you don't have to trust anyone and<00:05:41.190> within<00:05:42.190> that<00:05:42.460> you<00:05:42.520> look<00:05:43.180> at<00:05:43.330> look<00:05:43.870> for<00:05:44.050> foo 00:05:44.190 --> 00:05:44.200 align:start position:0% and within that you look at look for foo 00:05:44.200 --> 00:05:46.170 align:start position:0% and within that you look at look for foo and<00:05:44.410> what<00:05:44.530> that<00:05:44.620> means<00:05:44.830> is<00:05:45.039> that<00:05:45.220> inside<00:05:46.000> that 00:05:46.170 --> 00:05:46.180 align:start position:0% and what that means is that inside that 00:05:46.180 --> 00:05:49.140 align:start position:0% and what that means is that inside that object<00:05:46.300> who<00:05:46.810> is<00:05:47.110> a<00:05:47.440> link<00:05:47.800> that<00:05:48.250> is<00:05:48.310> pointing<00:05:49.030> to 00:05:49.140 --> 00:05:49.150 align:start position:0% object who is a link that is pointing to 00:05:49.150 --> 00:05:51.029 align:start position:0% object who is a link that is pointing to another<00:05:49.240> hash<00:05:49.600> and<00:05:49.900> you're<00:05:50.320> using<00:05:50.560> you<00:05:50.860> use 00:05:51.029 --> 00:05:51.039 align:start position:0% another hash and you're using you use 00:05:51.039 --> 00:05:53.070 align:start position:0% another hash and you're using you use that<00:05:51.190> to<00:05:51.430> resolve<00:05:51.760> for<00:05:52.030> the<00:05:52.150> next<00:05:52.360> step<00:05:52.539> and<00:05:52.780> so 00:05:53.070 --> 00:05:53.080 align:start position:0% that to resolve for the next step and so 00:05:53.080 --> 00:05:55.800 align:start position:0% that to resolve for the next step and so on<00:05:53.110> down<00:05:53.440> right<00:05:53.800> this<00:05:53.889> is<00:05:54.150> taking<00:05:55.150> the<00:05:55.389> idea<00:05:55.630> of 00:05:55.800 --> 00:05:55.810 align:start position:0% on down right this is taking the idea of 00:05:55.810 --> 00:05:57.930 align:start position:0% on down right this is taking the idea of file<00:05:55.990> system<00:05:56.380> with<00:05:56.650> inodes<00:05:57.130> but<00:05:57.490> replace<00:05:57.789> an 00:05:57.930 --> 00:05:57.940 align:start position:0% file system with inodes but replace an 00:05:57.940 --> 00:06:02.340 align:start position:0% file system with inodes but replace an inode<00:05:58.150> with<00:05:58.690> a<00:05:58.960> hash<00:05:59.500> and<00:06:00.810> of<00:06:01.810> course<00:06:02.050> this<00:06:02.169> is 00:06:02.340 --> 00:06:02.350 align:start position:0% inode with a hash and of course this is 00:06:02.350 --> 00:06:05.010 align:start position:0% inode with a hash and of course this is merkel<00:06:02.950> linking<00:06:03.220> and<00:06:03.760> you<00:06:03.880> get<00:06:04.000> full<00:06:04.270> path 00:06:05.010 --> 00:06:05.020 align:start position:0% merkel linking and you get full path 00:06:05.020 --> 00:06:08.360 align:start position:0% merkel linking and you get full path reversals<00:06:05.680> down<00:06:06.190> down<00:06:06.700> this<00:06:06.850> kind<00:06:07.000> of<00:06:07.090> graph 00:06:08.360 --> 00:06:08.370 align:start position:0% reversals down down this kind of graph 00:06:08.370 --> 00:06:11.219 align:start position:0% reversals down down this kind of graph so<00:06:09.370> if<00:06:09.700> you<00:06:09.850> imagine<00:06:09.940> a<00:06:10.270> blockchain<00:06:10.510> layered 00:06:11.219 --> 00:06:11.229 align:start position:0% so if you imagine a blockchain layered 00:06:11.229 --> 00:06:13.110 align:start position:0% so if you imagine a blockchain layered like<00:06:11.470> that<00:06:11.710> you<00:06:11.950> would<00:06:12.100> have<00:06:12.250> a<00:06:12.280> massive<00:06:12.669> path 00:06:13.110 --> 00:06:13.120 align:start position:0% like that you would have a massive path 00:06:13.120 --> 00:06:14.820 align:start position:0% like that you would have a massive path going<00:06:13.450> like<00:06:13.690> parent<00:06:14.050> parent<00:06:14.320> parent<00:06:14.590> Peron 00:06:14.820 --> 00:06:14.830 align:start position:0% going like parent parent parent Peron 00:06:14.830 --> 00:06:15.749 align:start position:0% going like parent parent parent Peron Peron<00:06:15.010> Peron 00:06:15.749 --> 00:06:15.759 align:start position:0% Peron Peron 00:06:15.759 --> 00:06:17.339 align:start position:0% Peron Peron and<00:06:16.060> someone<00:06:16.419> down<00:06:16.569> right<00:06:16.780> but<00:06:16.900> you<00:06:16.990> imagine 00:06:17.339 --> 00:06:17.349 align:start position:0% and someone down right but you imagine 00:06:17.349 --> 00:06:18.719 align:start position:0% and someone down right but you imagine you<00:06:17.440> you'll<00:06:17.680> be<00:06:17.800> able<00:06:17.860> to<00:06:18.009> index<00:06:18.430> directly 00:06:18.719 --> 00:06:18.729 align:start position:0% you you'll be able to index directly 00:06:18.729 --> 00:06:21.089 align:start position:0% you you'll be able to index directly into<00:06:19.270> a<00:06:19.300> specific<00:06:19.780> block<00:06:20.410> and<00:06:20.680> be<00:06:20.770> able<00:06:20.919> to<00:06:20.979> go 00:06:21.089 --> 00:06:21.099 align:start position:0% into a specific block and be able to go 00:06:21.099 --> 00:06:24.480 align:start position:0% into a specific block and be able to go down<00:06:21.280> into<00:06:21.490> the<00:06:21.639> transactions<00:06:22.240> and<00:06:22.449> so<00:06:22.539> on<00:06:23.490> and 00:06:24.480 --> 00:06:24.490 align:start position:0% down into the transactions and so on and 00:06:24.490 --> 00:06:28.589 align:start position:0% down into the transactions and so on and so<00:06:24.729> the<00:06:25.330> the<00:06:25.630> IPS<00:06:26.020> link<00:06:26.639> sphere<00:06:27.639> I<00:06:27.669> guess<00:06:28.000> is 00:06:28.589 --> 00:06:28.599 align:start position:0% so the the IPS link sphere I guess is 00:06:28.599 --> 00:06:30.390 align:start position:0% so the the IPS link sphere I guess is that<00:06:28.810> you<00:06:28.990> first<00:06:29.289> have<00:06:29.530> content<00:06:30.039> addressed 00:06:30.390 --> 00:06:30.400 align:start position:0% that you first have content addressed 00:06:30.400 --> 00:06:33.689 align:start position:0% that you first have content addressed links<00:06:30.910> where<00:06:31.569> they<00:06:32.319> start<00:06:32.650> with<00:06:32.800> slash<00:06:33.160> ipfs 00:06:33.689 --> 00:06:33.699 align:start position:0% links where they start with slash ipfs 00:06:33.699 --> 00:06:36.330 align:start position:0% links where they start with slash ipfs then<00:06:34.660> you<00:06:34.750> have<00:06:34.930> a<00:06:34.960> hash<00:06:35.259> and<00:06:35.590> then<00:06:35.979> the<00:06:36.130> rest 00:06:36.330 --> 00:06:36.340 align:start position:0% then you have a hash and then the rest 00:06:36.340 --> 00:06:37.559 align:start position:0% then you have a hash and then the rest of<00:06:36.520> that<00:06:36.639> stuff<00:06:36.880> and<00:06:37.090> by<00:06:37.240> the<00:06:37.300> way<00:06:37.419> those<00:06:37.539> are 00:06:37.559 --> 00:06:37.569 align:start position:0% of that stuff and by the way those are 00:06:37.569 --> 00:06:40.350 align:start position:0% of that stuff and by the way those are shortened<00:06:38.289> hashes<00:06:38.650> I<00:06:39.220> haven't<00:06:39.849> yet<00:06:39.940> found<00:06:40.000> a 00:06:40.350 --> 00:06:40.360 align:start position:0% shortened hashes I haven't yet found a 00:06:40.360 --> 00:06:42.210 align:start position:0% shortened hashes I haven't yet found a way<00:06:40.479> to<00:06:40.509> compress<00:06:41.319> information<00:06:41.530> magically 00:06:42.210 --> 00:06:42.220 align:start position:0% way to compress information magically 00:06:42.220 --> 00:06:43.469 align:start position:0% way to compress information magically that's<00:06:42.610> what<00:06:42.729> that's<00:06:42.970> suppose<00:06:43.150> to<00:06:43.180> be<00:06:43.240> I<00:06:43.330> shot 00:06:43.469 --> 00:06:43.479 align:start position:0% that's what that's suppose to be I shot 00:06:43.479 --> 00:06:47.040 align:start position:0% that's what that's suppose to be I shot 256<00:06:44.139> but<00:06:44.289> it's<00:06:44.440> turned<00:06:44.770> so<00:06:45.669> it<00:06:45.759> fits<00:06:45.940> here<00:06:46.120> and 00:06:47.040 --> 00:06:47.050 align:start position:0% 256 but it's turned so it fits here and 00:06:47.050 --> 00:06:48.180 align:start position:0% 256 but it's turned so it fits here and yeah<00:06:47.199> of<00:06:47.319> course<00:06:47.530> we<00:06:47.710> have<00:06:47.860> the<00:06:48.009> scheme 00:06:48.180 --> 00:06:48.190 align:start position:0% yeah of course we have the scheme 00:06:48.190 --> 00:06:50.540 align:start position:0% yeah of course we have the scheme identifier<00:06:48.610> if<00:06:48.759> you<00:06:48.819> want<00:06:48.970> to<00:06:49.030> use<00:06:49.150> it<00:06:49.300> but<00:06:49.840> we 00:06:50.540 --> 00:06:50.550 align:start position:0% identifier if you want to use it but we 00:06:50.550 --> 00:06:52.649 align:start position:0% identifier if you want to use it but we recommend<00:06:51.550> that<00:06:51.610> you<00:06:51.759> don't<00:06:51.970> use<00:06:52.360> the<00:06:52.509> scheme 00:06:52.649 --> 00:06:52.659 align:start position:0% recommend that you don't use the scheme 00:06:52.659 --> 00:06:55.140 align:start position:0% recommend that you don't use the scheme identifier<00:06:53.110> because<00:06:53.500> we<00:06:53.650> the<00:06:54.520> way<00:06:54.639> we<00:06:54.669> look<00:06:55.030> at 00:06:55.140 --> 00:06:55.150 align:start position:0% identifier because we the way we look at 00:06:55.150 --> 00:06:59.580 align:start position:0% identifier because we the way we look at the<00:06:55.210> world<00:06:55.349> the<00:06:56.490> regular<00:06:57.630> w3c<00:06:58.630> based<00:06:58.840> scheme 00:06:59.580 --> 00:06:59.590 align:start position:0% the world the regular w3c based scheme 00:06:59.590 --> 00:07:01.529 align:start position:0% the world the regular w3c based scheme identifier<00:07:00.009> broke<00:07:00.370> compatibility<00:07:00.970> with<00:07:01.120> Unix 00:07:01.529 --> 00:07:01.539 align:start position:0% identifier broke compatibility with Unix 00:07:01.539 --> 00:07:03.779 align:start position:0% identifier broke compatibility with Unix so<00:07:02.050> you<00:07:02.139> can't<00:07:02.319> we're<00:07:02.889> making<00:07:03.130> everything<00:07:03.460> so 00:07:03.779 --> 00:07:03.789 align:start position:0% so you can't we're making everything so 00:07:03.789 --> 00:07:06.629 align:start position:0% so you can't we're making everything so you<00:07:03.849> can<00:07:04.030> layer<00:07:04.270> it<00:07:04.300> directly<00:07:04.979> on<00:07:05.979> top<00:07:06.340> of<00:07:06.370> any 00:07:06.629 --> 00:07:06.639 align:start position:0% you can layer it directly on top of any 00:07:06.639 --> 00:07:08.490 align:start position:0% you can layer it directly on top of any politics<00:07:07.000> machine<00:07:07.360> so<00:07:07.810> you<00:07:07.900> can<00:07:08.020> mount<00:07:08.259> it 00:07:08.490 --> 00:07:08.500 align:start position:0% politics machine so you can mount it 00:07:08.500 --> 00:07:11.159 align:start position:0% politics machine so you can mount it directly<00:07:09.099> so<00:07:09.400> you<00:07:09.610> can<00:07:09.729> you<00:07:09.970> can<00:07:10.120> mount<00:07:10.690> ipfs 00:07:11.159 --> 00:07:11.169 align:start position:0% directly so you can you can mount ipfs 00:07:11.169 --> 00:07:12.899 align:start position:0% directly so you can you can mount ipfs and<00:07:11.319> you<00:07:11.380> can<00:07:11.500> fetch<00:07:11.710> data<00:07:12.009> and<00:07:12.250> write<00:07:12.430> data<00:07:12.580> to 00:07:12.899 --> 00:07:12.909 align:start position:0% and you can fetch data and write data to 00:07:12.909 --> 00:07:15.330 align:start position:0% and you can fetch data and write data to the<00:07:13.180> network<00:07:13.569> with<00:07:13.960> standard<00:07:14.590> old-style 00:07:15.330 --> 00:07:15.340 align:start position:0% the network with standard old-style 00:07:15.340 --> 00:07:16.860 align:start position:0% the network with standard old-style applications<00:07:15.880> you<00:07:16.030> don't<00:07:16.180> have<00:07:16.360> to<00:07:16.539> teach 00:07:16.860 --> 00:07:16.870 align:start position:0% applications you don't have to teach 00:07:16.870 --> 00:07:20.180 align:start position:0% applications you don't have to teach them<00:07:17.110> to<00:07:18.039> speak<00:07:18.130> over<00:07:18.550> some<00:07:18.909> other<00:07:19.030> protocol 00:07:20.180 --> 00:07:20.190 align:start position:0% them to speak over some other protocol 00:07:20.190 --> 00:07:22.620 align:start position:0% them to speak over some other protocol and<00:07:21.190> on<00:07:21.340> top<00:07:21.490> of<00:07:21.520> on<00:07:22.000> top<00:07:22.120> of<00:07:22.240> the<00:07:22.360> merkel 00:07:22.620 --> 00:07:22.630 align:start position:0% and on top of on top of the merkel 00:07:22.630 --> 00:07:24.209 align:start position:0% and on top of on top of the merkel linking<00:07:23.020> which<00:07:23.349> which<00:07:23.800> is<00:07:23.919> sort<00:07:24.039> of<00:07:24.070> like<00:07:24.130> a 00:07:24.209 --> 00:07:24.219 align:start position:0% linking which which is sort of like a 00:07:24.219 --> 00:07:28.230 align:start position:0% linking which which is sort of like a URI<00:07:24.490> and<00:07:25.300> I<00:07:26.080> say<00:07:26.229> URI<00:07:26.469> with<00:07:26.650> quotes<00:07:26.919> because<00:07:27.340> we 00:07:28.230 --> 00:07:28.240 align:start position:0% URI and I say URI with quotes because we 00:07:28.240 --> 00:07:31.200 align:start position:0% URI and I say URI with quotes because we do<00:07:28.590> prefer<00:07:29.590> people<00:07:29.919> not<00:07:30.219> to<00:07:30.400> use<00:07:30.430> the<00:07:31.000> schema 00:07:31.200 --> 00:07:31.210 align:start position:0% do prefer people not to use the schema 00:07:31.210 --> 00:07:33.990 align:start position:0% do prefer people not to use the schema identifier<00:07:32.039> we'll<00:07:33.039> have<00:07:33.310> everything<00:07:33.639> working 00:07:33.990 --> 00:07:34.000 align:start position:0% identifier we'll have everything working 00:07:34.000 --> 00:07:35.219 align:start position:0% identifier we'll have everything working and<00:07:34.240> resolving<00:07:34.539> with<00:07:34.690> just<00:07:34.930> straight-up 00:07:35.219 --> 00:07:35.229 align:start position:0% and resolving with just straight-up 00:07:35.229 --> 00:07:38.490 align:start position:0% and resolving with just straight-up paths<00:07:36.180> on<00:07:37.180> top<00:07:37.330> of<00:07:37.419> that<00:07:37.509> we<00:07:37.719> layer<00:07:37.900> what<00:07:38.139> we're 00:07:38.490 --> 00:07:38.500 align:start position:0% paths on top of that we layer what we're 00:07:38.500 --> 00:07:41.010 align:start position:0% paths on top of that we layer what we're calling<00:07:38.620> also<00:07:39.009> Meszaros<00:07:39.610> links<00:07:40.030> this<00:07:40.509> is<00:07:40.570> for 00:07:41.010 --> 00:07:41.020 align:start position:0% calling also Meszaros links this is for 00:07:41.020 --> 00:07:42.899 align:start position:0% calling also Meszaros links this is for David<00:07:41.229> missouri's<00:07:41.710> who<00:07:41.889> author<00:07:42.490> of<00:07:42.699> Kadhim 00:07:42.899 --> 00:07:42.909 align:start position:0% David missouri's who author of Kadhim 00:07:42.909 --> 00:07:45.059 align:start position:0% David missouri's who author of Kadhim Leah<00:07:43.060> sort<00:07:43.479> of<00:07:43.539> stellar<00:07:43.719> author<00:07:44.229> of<00:07:44.440> SF<00:07:44.680> s<00:07:44.830> way 00:07:45.059 --> 00:07:45.069 align:start position:0% Leah sort of stellar author of SF s way 00:07:45.069 --> 00:07:47.070 align:start position:0% Leah sort of stellar author of SF s way before<00:07:45.310> that<00:07:45.509> and<00:07:46.509> he<00:07:46.599> came<00:07:46.690> up<00:07:46.810> with<00:07:46.870> a<00:07:46.990> great 00:07:47.070 --> 00:07:47.080 align:start position:0% before that and he came up with a great 00:07:47.080 --> 00:07:50.490 align:start position:0% before that and he came up with a great idea<00:07:47.229> in<00:07:48.099> nessip<00:07:48.460> s<00:07:48.610> and<00:07:49.569> one<00:07:49.690> go<00:07:49.810> through<00:07:50.349> the 00:07:50.490 --> 00:07:50.500 align:start position:0% idea in nessip s and one go through the 00:07:50.500 --> 00:07:51.990 align:start position:0% idea in nessip s and one go through the whole<00:07:50.650> thing<00:07:50.830> but<00:07:50.979> the<00:07:51.069> basic<00:07:51.400> notion<00:07:51.729> here<00:07:51.969> is 00:07:51.990 --> 00:07:52.000 align:start position:0% whole thing but the basic notion here is 00:07:52.000 --> 00:07:54.839 align:start position:0% whole thing but the basic notion here is that<00:07:52.409> the<00:07:53.409> way<00:07:53.650> you<00:07:53.710> achieve<00:07:53.949> mutability<00:07:54.639> in 00:07:54.839 --> 00:07:54.849 align:start position:0% that the way you achieve mutability in 00:07:54.849 --> 00:07:57.600 align:start position:0% that the way you achieve mutability in ipfs<00:07:55.330> is<00:07:55.569> that<00:07:55.810> you<00:07:55.930> use<00:07:56.199> the<00:07:57.099> hashes<00:07:57.460> of 00:07:57.600 --> 00:07:57.610 align:start position:0% ipfs is that you use the hashes of 00:07:57.610 --> 00:08:00.209 align:start position:0% ipfs is that you use the hashes of public<00:07:57.909> keys<00:07:58.120> and<00:07:58.419> use<00:07:59.110> those<00:07:59.319> to<00:07:59.560> resolve<00:07:59.919> for 00:08:00.209 --> 00:08:00.219 align:start position:0% public keys and use those to resolve for 00:08:00.219 --> 00:08:01.860 align:start position:0% public keys and use those to resolve for pointers<00:08:00.639> that<00:08:00.880> have<00:08:01.000> been<00:08:01.120> signed<00:08:01.419> with<00:08:01.840> a 00:08:01.860 --> 00:08:01.870 align:start position:0% pointers that have been signed with a 00:08:01.870 --> 00:08:02.939 align:start position:0% pointers that have been signed with a private<00:08:02.199> key 00:08:02.939 --> 00:08:02.949 align:start position:0% private key 00:08:02.949 --> 00:08:05.850 align:start position:0% private key oh<00:08:03.630> it's<00:08:04.630> explained<00:08:05.139> better<00:08:05.289> or<00:08:05.500> somewhere<00:08:05.800> in 00:08:05.850 --> 00:08:05.860 align:start position:0% oh it's explained better or somewhere in 00:08:05.860 --> 00:08:06.809 align:start position:0% oh it's explained better or somewhere in the<00:08:05.919> web<00:08:06.009> but<00:08:06.130> there's<00:08:06.340> more<00:08:06.460> interesting 00:08:06.809 --> 00:08:06.819 align:start position:0% the web but there's more interesting 00:08:06.819 --> 00:08:09.209 align:start position:0% the web but there's more interesting stuff<00:08:07.000> here<00:08:07.210> but<00:08:08.199> it's<00:08:08.319> a<00:08:08.380> very<00:08:08.530> subtle<00:08:08.830> idea 00:08:09.209 --> 00:08:09.219 align:start position:0% stuff here but it's a very subtle idea 00:08:09.219 --> 00:08:12.480 align:start position:0% stuff here but it's a very subtle idea that<00:08:09.460> gives<00:08:09.669> you<00:08:09.880> a<00:08:10.210> way<00:08:11.020> to<00:08:11.500> achieve<00:08:11.770> naming 00:08:12.480 --> 00:08:12.490 align:start position:0% that gives you a way to achieve naming 00:08:12.490 --> 00:08:14.550 align:start position:0% that gives you a way to achieve naming and<00:08:12.909> this<00:08:13.030> is<00:08:13.180> naming<00:08:13.719> that<00:08:13.960> it's<00:08:14.080> not<00:08:14.199> human 00:08:14.550 --> 00:08:14.560 align:start position:0% and this is naming that it's not human 00:08:14.560 --> 00:08:15.930 align:start position:0% and this is naming that it's not human readable<00:08:14.919> but<00:08:15.490> it's<00:08:15.610> a<00:08:15.639> way<00:08:15.759> to<00:08:15.819> achieve 00:08:15.930 --> 00:08:15.940 align:start position:0% readable but it's a way to achieve 00:08:15.940 --> 00:08:17.279 align:start position:0% readable but it's a way to achieve naming<00:08:16.479> that's<00:08:16.719> cryptographically 00:08:17.279 --> 00:08:17.289 align:start position:0% naming that's cryptographically 00:08:17.289 --> 00:08:20.550 align:start position:0% naming that's cryptographically addressed<00:08:17.919> or<00:08:18.690> cryptographically<00:08:19.690> mediated 00:08:20.550 --> 00:08:20.560 align:start position:0% addressed or cryptographically mediated 00:08:20.560 --> 00:08:22.469 align:start position:0% addressed or cryptographically mediated instead<00:08:21.039> of<00:08:21.159> through<00:08:21.430> some<00:08:21.849> central 00:08:22.469 --> 00:08:22.479 align:start position:0% instead of through some central 00:08:22.479 --> 00:08:24.629 align:start position:0% instead of through some central authority<00:08:22.539> right<00:08:22.990> and<00:08:23.349> on<00:08:24.339> top<00:08:24.490> of<00:08:24.520> that 00:08:24.629 --> 00:08:24.639 align:start position:0% authority right and on top of that 00:08:24.639 --> 00:08:26.420 align:start position:0% authority right and on top of that mutable<00:08:25.180> link<00:08:25.389> then<00:08:25.690> you<00:08:25.719> can<00:08:25.960> layer<00:08:26.110> names 00:08:26.420 --> 00:08:26.430 align:start position:0% mutable link then you can layer names 00:08:26.430 --> 00:08:29.159 align:start position:0% mutable link then you can layer names and<00:08:27.430> so<00:08:27.639> here's<00:08:27.880> the<00:08:28.240> old<00:08:28.419> style<00:08:28.719> DNA 00:08:29.159 --> 00:08:29.169 align:start position:0% and so here's the old style DNA 00:08:29.169 --> 00:08:31.290 align:start position:0% and so here's the old style DNA world<00:08:29.439> we<00:08:29.710> work<00:08:30.099> exactly<00:08:30.580> with<00:08:30.789> DNS<00:08:30.999> so<00:08:31.180> you 00:08:31.290 --> 00:08:31.300 align:start position:0% world we work exactly with DNS so you 00:08:31.300 --> 00:08:33.930 align:start position:0% world we work exactly with DNS so you can<00:08:31.449> add<00:08:32.320> a<00:08:32.349> text<00:08:32.620> record<00:08:32.979> into<00:08:33.190> your<00:08:33.370> domain 00:08:33.930 --> 00:08:33.940 align:start position:0% can add a text record into your domain 00:08:33.940 --> 00:08:35.879 align:start position:0% can add a text record into your domain and<00:08:33.969> now<00:08:34.240> you<00:08:34.300> can<00:08:34.539> resolve<00:08:34.779> through<00:08:35.139> IP<00:08:35.380> NS<00:08:35.709> or 00:08:35.879 --> 00:08:35.889 align:start position:0% and now you can resolve through IP NS or 00:08:35.889 --> 00:08:38.850 align:start position:0% and now you can resolve through IP NS or directly<00:08:36.490> to<00:08:36.579> my<00:08:36.639> PFS<00:08:37.349> and<00:08:38.349> of<00:08:38.440> course<00:08:38.620> you<00:08:38.740> can 00:08:38.850 --> 00:08:38.860 align:start position:0% directly to my PFS and of course you can 00:08:38.860 --> 00:08:40.800 align:start position:0% directly to my PFS and of course you can have<00:08:39.039> etherium<00:08:39.550> names<00:08:39.760> the<00:08:40.000> same<00:08:40.180> way<00:08:40.329> right 00:08:40.800 --> 00:08:40.810 align:start position:0% have etherium names the same way right 00:08:40.810 --> 00:08:42.440 align:start position:0% have etherium names the same way right and<00:08:40.990> so<00:08:41.079> you<00:08:41.200> could<00:08:41.349> you<00:08:41.560> can<00:08:42.070> imagine 00:08:42.440 --> 00:08:42.450 align:start position:0% and so you could you can imagine 00:08:42.450 --> 00:08:45.540 align:start position:0% and so you could you can imagine resolving<00:08:43.450> if<00:08:44.019> your<00:08:44.229> names<00:08:44.680> directly<00:08:45.160> into 00:08:45.540 --> 00:08:45.550 align:start position:0% resolving if your names directly into 00:08:45.550 --> 00:08:48.569 align:start position:0% resolving if your names directly into ipfs<00:08:46.360> content<00:08:46.750> the<00:08:46.870> exact<00:08:47.529> same<00:08:47.680> way 00:08:48.569 --> 00:08:48.579 align:start position:0% ipfs content the exact same way 00:08:48.579 --> 00:08:50.639 align:start position:0% ipfs content the exact same way what's<00:08:48.910> amazingly<00:08:49.360> interesting<00:08:50.260> about<00:08:50.440> these 00:08:50.639 --> 00:08:50.649 align:start position:0% what's amazingly interesting about these 00:08:50.649 --> 00:08:52.199 align:start position:0% what's amazingly interesting about these kinds<00:08:50.949> of<00:08:51.040> names<00:08:51.220> is<00:08:51.519> that<00:08:51.699> you<00:08:51.820> no<00:08:52.029> longer 00:08:52.199 --> 00:08:52.209 align:start position:0% kinds of names is that you no longer 00:08:52.209 --> 00:08:53.879 align:start position:0% kinds of names is that you no longer have<00:08:52.570> to<00:08:52.600> have<00:08:52.839> any<00:08:53.199> machine<00:08:53.620> running 00:08:53.879 --> 00:08:53.889 align:start position:0% have to have any machine running 00:08:53.889 --> 00:08:56.370 align:start position:0% have to have any machine running yourself<00:08:54.130> you<00:08:55.089> can<00:08:55.269> create<00:08:55.600> the<00:08:55.750> content<00:08:56.110> and 00:08:56.370 --> 00:08:56.380 align:start position:0% yourself you can create the content and 00:08:56.380 --> 00:08:58.170 align:start position:0% yourself you can create the content and add<00:08:56.589> it<00:08:56.709> to<00:08:56.800> the<00:08:56.889> network<00:08:57.040> you<00:08:57.610> can<00:08:57.730> create<00:08:58.029> the 00:08:58.170 --> 00:08:58.180 align:start position:0% add it to the network you can create the 00:08:58.180 --> 00:09:00.720 align:start position:0% add it to the network you can create the names<00:08:58.420> and<00:08:58.779> the<00:08:59.170> key<00:08:59.949> names<00:09:00.190> and<00:09:00.459> sign 00:09:00.720 --> 00:09:00.730 align:start position:0% names and the key names and sign 00:09:00.730 --> 00:09:02.490 align:start position:0% names and the key names and sign contents<00:09:01.600> and<00:09:01.690> distribute<00:09:02.079> to<00:09:02.110> the<00:09:02.260> network 00:09:02.490 --> 00:09:02.500 align:start position:0% contents and distribute to the network 00:09:02.500 --> 00:09:04.470 align:start position:0% contents and distribute to the network and<00:09:02.709> then<00:09:02.769> you<00:09:03.370> can<00:09:03.519> register<00:09:03.730> some<00:09:04.120> name<00:09:04.300> and 00:09:04.470 --> 00:09:04.480 align:start position:0% and then you can register some name and 00:09:04.480 --> 00:09:05.910 align:start position:0% and then you can register some name and point<00:09:04.690> it<00:09:04.779> to<00:09:04.870> the<00:09:05.019> house<00:09:05.320> of<00:09:05.470> a<00:09:05.529> public<00:09:05.800> key 00:09:05.910 --> 00:09:05.920 align:start position:0% point it to the house of a public key 00:09:05.920 --> 00:09:08.670 align:start position:0% point it to the house of a public key and<00:09:06.220> now<00:09:06.820> you<00:09:07.240> can<00:09:07.389> just<00:09:07.420> disappear<00:09:07.660> just<00:09:08.230> add 00:09:08.670 --> 00:09:08.680 align:start position:0% and now you can just disappear just add 00:09:08.680 --> 00:09:10.259 align:start position:0% and now you can just disappear just add content<00:09:09.040> to<00:09:09.100> the<00:09:09.190> network<00:09:09.430> and<00:09:09.579> walk<00:09:09.730> away<00:09:09.850> and 00:09:10.259 --> 00:09:10.269 align:start position:0% content to the network and walk away and 00:09:10.269 --> 00:09:12.150 align:start position:0% content to the network and walk away and if<00:09:10.839> the<00:09:10.930> network<00:09:11.079> will<00:09:11.440> continue<00:09:11.860> serving 00:09:12.150 --> 00:09:12.160 align:start position:0% if the network will continue serving 00:09:12.160 --> 00:09:13.590 align:start position:0% if the network will continue serving your<00:09:12.279> stuff<00:09:12.550> and<00:09:12.790> that's<00:09:12.970> you<00:09:13.269> know<00:09:13.389> an 00:09:13.590 --> 00:09:13.600 align:start position:0% your stuff and that's you know an 00:09:13.600 --> 00:09:16.259 align:start position:0% your stuff and that's you know an asterisk<00:09:14.050> there<00:09:15.029> everything<00:09:16.029> will<00:09:16.180> continue 00:09:16.259 --> 00:09:16.269 align:start position:0% asterisk there everything will continue 00:09:16.269 --> 00:09:17.819 align:start position:0% asterisk there everything will continue working<00:09:16.660> right<00:09:17.290> and<00:09:17.470> that's<00:09:17.620> something 00:09:17.819 --> 00:09:17.829 align:start position:0% working right and that's something 00:09:17.829 --> 00:09:19.590 align:start position:0% working right and that's something that's<00:09:18.160> very<00:09:18.670> different<00:09:18.910> you<00:09:19.149> don't<00:09:19.300> have<00:09:19.480> to 00:09:19.590 --> 00:09:19.600 align:start position:0% that's very different you don't have to 00:09:19.600 --> 00:09:24.360 align:start position:0% that's very different you don't have to maintain<00:09:19.750> your<00:09:20.139> own<00:09:20.290> infrastructure<00:09:22.529> so<00:09:23.529> this 00:09:24.360 --> 00:09:24.370 align:start position:0% maintain your own infrastructure so this 00:09:24.370 --> 00:09:28.199 align:start position:0% maintain your own infrastructure so this is<00:09:25.019> often<00:09:26.019> non-obvious<00:09:26.529> so<00:09:27.220> I'll<00:09:27.339> kind<00:09:27.519> of<00:09:27.639> go 00:09:28.199 --> 00:09:28.209 align:start position:0% is often non-obvious so I'll kind of go 00:09:28.209 --> 00:09:30.449 align:start position:0% is often non-obvious so I'll kind of go through<00:09:28.240> the<00:09:29.050> ifs<00:09:29.410> content<00:09:29.889> and<00:09:30.070> replication 00:09:30.449 --> 00:09:30.459 align:start position:0% through the ifs content and replication 00:09:30.459 --> 00:09:32.519 align:start position:0% through the ifs content and replication model<00:09:30.670> this<00:09:31.329> this<00:09:31.630> is<00:09:31.750> kind<00:09:31.930> of<00:09:31.959> like<00:09:32.139> what 00:09:32.519 --> 00:09:32.529 align:start position:0% model this this is kind of like what 00:09:32.529 --> 00:09:34.380 align:start position:0% model this this is kind of like what most<00:09:32.889> people<00:09:33.160> don't<00:09:33.490> expect<00:09:33.910> it<00:09:34.089> here<00:09:34.240> they're 00:09:34.380 --> 00:09:34.390 align:start position:0% most people don't expect it here they're 00:09:34.390 --> 00:09:37.230 align:start position:0% most people don't expect it here they're like<00:09:34.449> what<00:09:35.250> but<00:09:36.250> it<00:09:36.699> makes<00:09:36.880> sense<00:09:37.000> to<00:09:37.149> go 00:09:37.230 --> 00:09:37.240 align:start position:0% like what but it makes sense to go 00:09:37.240 --> 00:09:39.540 align:start position:0% like what but it makes sense to go through<00:09:37.390> so<00:09:37.540> there<00:09:38.470> are<00:09:38.740> three<00:09:38.949> important 00:09:39.540 --> 00:09:39.550 align:start position:0% through so there are three important 00:09:39.550 --> 00:09:41.130 align:start position:0% through so there are three important points<00:09:39.670> that<00:09:39.940> bear<00:09:40.089> mentioning<00:09:40.630> here<00:09:40.839> other 00:09:41.130 --> 00:09:41.140 align:start position:0% points that bear mentioning here other 00:09:41.140 --> 00:09:43.110 align:start position:0% points that bear mentioning here other than<00:09:41.260> a<00:09:41.949> whole<00:09:42.430> bunch<00:09:42.610> of<00:09:42.670> others<00:09:42.910> that<00:09:43.029> you 00:09:43.110 --> 00:09:43.120 align:start position:0% than a whole bunch of others that you 00:09:43.120 --> 00:09:45.509 align:start position:0% than a whole bunch of others that you probably<00:09:43.420> can<00:09:43.750> assume<00:09:43.959> but<00:09:44.199> number<00:09:45.160> one<00:09:45.339> is 00:09:45.509 --> 00:09:45.519 align:start position:0% probably can assume but number one is 00:09:45.519 --> 00:09:48.180 align:start position:0% probably can assume but number one is that<00:09:45.550> we<00:09:46.029> want<00:09:46.060> I<00:09:46.570> P<00:09:46.750> FS<00:09:47.050> to<00:09:47.260> be<00:09:47.380> able<00:09:47.589> to<00:09:47.740> go<00:09:47.980> as 00:09:48.180 --> 00:09:48.190 align:start position:0% that we want I P FS to be able to go as 00:09:48.190 --> 00:09:50.610 align:start position:0% that we want I P FS to be able to go as fast<00:09:48.550> as<00:09:48.790> the<00:09:49.089> underlying<00:09:49.390> network<00:09:49.930> so<00:09:50.350> we 00:09:50.610 --> 00:09:50.620 align:start position:0% fast as the underlying network so we 00:09:50.620 --> 00:09:53.939 align:start position:0% fast as the underlying network so we need<00:09:50.860> to<00:09:51.040> not<00:09:51.880> we<00:09:52.870> need<00:09:52.930> to<00:09:53.050> allow<00:09:53.380> users<00:09:53.920> to 00:09:53.939 --> 00:09:53.949 align:start position:0% need to not we need to allow users to 00:09:53.949 --> 00:09:57.540 align:start position:0% need to not we need to allow users to dial<00:09:54.399> between<00:09:55.029> efficiency<00:09:55.870> and<00:09:55.990> privacy<00:09:56.649> so 00:09:57.540 --> 00:09:57.550 align:start position:0% dial between efficiency and privacy so 00:09:57.550 --> 00:10:00.840 align:start position:0% dial between efficiency and privacy so as<00:09:58.000> you<00:09:58.420> know<00:09:59.130> systems<00:10:00.130> like<00:10:00.279> tour<00:10:00.490> and<00:10:00.640> ITP 00:10:00.840 --> 00:10:00.850 align:start position:0% as you know systems like tour and ITP 00:10:00.850 --> 00:10:02.850 align:start position:0% as you know systems like tour and ITP and<00:10:01.060> so<00:10:01.149> on<00:10:01.300> that<00:10:01.870> are<00:10:01.899> focused<00:10:02.829> around 00:10:02.850 --> 00:10:02.860 align:start position:0% and so on that are focused around 00:10:02.860 --> 00:10:04.740 align:start position:0% and so on that are focused around privacy<00:10:03.190> have<00:10:03.640> to<00:10:03.760> do<00:10:03.910> a<00:10:03.940> whole<00:10:04.240> bunch<00:10:04.360> of<00:10:04.510> work 00:10:04.740 --> 00:10:04.750 align:start position:0% privacy have to do a whole bunch of work 00:10:04.750 --> 00:10:06.420 align:start position:0% privacy have to do a whole bunch of work routing<00:10:05.500> packets<00:10:05.709> and<00:10:05.980> moving<00:10:06.220> them<00:10:06.339> around 00:10:06.420 --> 00:10:06.430 align:start position:0% routing packets and moving them around 00:10:06.430 --> 00:10:09.540 align:start position:0% routing packets and moving them around and<00:10:06.820> you<00:10:06.880> spend<00:10:07.870> a<00:10:08.079> bunch<00:10:08.320> of<00:10:08.550> bandwidth 00:10:09.540 --> 00:10:09.550 align:start position:0% and you spend a bunch of bandwidth 00:10:09.550 --> 00:10:13.880 align:start position:0% and you spend a bunch of bandwidth hiding<00:10:11.519> hiding<00:10:12.519> the<00:10:12.640> traces<00:10:12.970> of<00:10:13.269> people's 00:10:13.880 --> 00:10:13.890 align:start position:0% hiding hiding the traces of people's 00:10:13.890 --> 00:10:16.139 align:start position:0% hiding hiding the traces of people's accesses<00:10:14.890> in<00:10:14.980> the<00:10:15.069> network<00:10:15.339> and<00:10:15.519> this<00:10:15.940> is<00:10:16.060> how 00:10:16.139 --> 00:10:16.149 align:start position:0% accesses in the network and this is how 00:10:16.149 --> 00:10:18.809 align:start position:0% accesses in the network and this is how you<00:10:16.209> achieve<00:10:16.390> privacy<00:10:17.040> but<00:10:18.040> that's<00:10:18.220> not<00:10:18.399> fast 00:10:18.809 --> 00:10:18.819 align:start position:0% you achieve privacy but that's not fast 00:10:18.819 --> 00:10:23.509 align:start position:0% you achieve privacy but that's not fast right<00:10:19.540> so<00:10:19.569> you're<00:10:19.990> trading<00:10:20.470> off<00:10:21.089> the<00:10:22.089> speed<00:10:22.360> of 00:10:23.509 --> 00:10:23.519 align:start position:0% right so you're trading off the speed of 00:10:23.519 --> 00:10:26.730 align:start position:0% right so you're trading off the speed of transfer<00:10:24.519> there<00:10:24.699> to<00:10:25.180> gain<00:10:25.300> some<00:10:25.480> privacy<00:10:25.750> but 00:10:26.730 --> 00:10:26.740 align:start position:0% transfer there to gain some privacy but 00:10:26.740 --> 00:10:29.309 align:start position:0% transfer there to gain some privacy but the<00:10:26.889> users<00:10:27.250> of<00:10:27.310> ipfs<00:10:27.790> are<00:10:28.329> very<00:10:28.600> some<00:10:29.050> people 00:10:29.309 --> 00:10:29.319 align:start position:0% the users of ipfs are very some people 00:10:29.319 --> 00:10:31.259 align:start position:0% the users of ipfs are very some people really<00:10:29.589> want<00:10:29.829> that<00:10:29.980> use<00:10:30.160> case<00:10:30.370> and<00:10:30.579> layer<00:10:30.760> ipfs 00:10:31.259 --> 00:10:31.269 align:start position:0% really want that use case and layer ipfs 00:10:31.269 --> 00:10:33.480 align:start position:0% really want that use case and layer ipfs directly<00:10:31.630> over<00:10:31.779> to<00:10:31.930> our<00:10:31.990> ITP<00:10:32.290> and<00:10:32.620> some<00:10:33.190> users 00:10:33.480 --> 00:10:33.490 align:start position:0% directly over to our ITP and some users 00:10:33.490 --> 00:10:34.860 align:start position:0% directly over to our ITP and some users don't<00:10:33.760> care<00:10:33.940> at<00:10:34.060> all<00:10:34.149> about<00:10:34.209> that<00:10:34.630> they're 00:10:34.860 --> 00:10:34.870 align:start position:0% don't care at all about that they're 00:10:34.870 --> 00:10:36.689 align:start position:0% don't care at all about that they're using<00:10:35.230> IP<00:10:35.500> FS<00:10:35.680> inside<00:10:35.949> data<00:10:36.160> centers<00:10:36.490> or 00:10:36.689 --> 00:10:36.699 align:start position:0% using IP FS inside data centers or 00:10:36.699 --> 00:10:38.220 align:start position:0% using IP FS inside data centers or they're<00:10:36.819> using<00:10:36.940> it<00:10:37.149> in<00:10:37.180> some<00:10:37.360> other<00:10:37.420> way<00:10:37.569> and 00:10:38.220 --> 00:10:38.230 align:start position:0% they're using it in some other way and 00:10:38.230 --> 00:10:39.990 align:start position:0% they're using it in some other way and they<00:10:38.589> really<00:10:38.980> want<00:10:39.160> it<00:10:39.220> to<00:10:39.279> be<00:10:39.370> as<00:10:39.519> efficient 00:10:39.990 --> 00:10:40.000 align:start position:0% they really want it to be as efficient 00:10:40.000 --> 00:10:41.480 align:start position:0% they really want it to be as efficient as<00:10:40.060> possible<00:10:40.149> right<00:10:40.630> like<00:10:40.779> do<00:10:41.110> you 00:10:41.480 --> 00:10:41.490 align:start position:0% as possible right like do you 00:10:41.490 --> 00:10:43.579 align:start position:0% as possible right like do you need<00:10:41.700> to<00:10:41.850> route<00:10:42.029> through<00:10:42.240> tour<00:10:42.510> to<00:10:43.230> go<00:10:43.380> from 00:10:43.579 --> 00:10:43.589 align:start position:0% need to route through tour to go from 00:10:43.589 --> 00:10:45.769 align:start position:0% need to route through tour to go from like<00:10:43.770> your<00:10:44.160> computer<00:10:44.700> your<00:10:45.209> laptop<00:10:45.390> to<00:10:45.750> your 00:10:45.769 --> 00:10:45.779 align:start position:0% like your computer your laptop to your 00:10:45.779 --> 00:10:48.440 align:start position:0% like your computer your laptop to your mobile<00:10:46.140> phone<00:10:46.320> in<00:10:46.560> the<00:10:46.740> same<00:10:46.920> room<00:10:47.459> maybe<00:10:48.240> not 00:10:48.440 --> 00:10:48.450 align:start position:0% mobile phone in the same room maybe not 00:10:48.450 --> 00:10:50.750 align:start position:0% mobile phone in the same room maybe not or<00:10:48.870> maybe<00:10:49.050> you<00:10:49.170> do<00:10:49.260> it<00:10:49.350> depends<00:10:49.980> on<00:10:50.070> what<00:10:50.580> kind 00:10:50.750 --> 00:10:50.760 align:start position:0% or maybe you do it depends on what kind 00:10:50.760 --> 00:10:54.230 align:start position:0% or maybe you do it depends on what kind of<00:10:50.820> home<00:10:50.970> you<00:10:51.089> have<00:10:51.890> but<00:10:52.890> you<00:10:52.920> know<00:10:53.240> and 00:10:54.230 --> 00:10:54.240 align:start position:0% of home you have but you know and 00:10:54.240 --> 00:10:57.380 align:start position:0% of home you have but you know and another<00:10:54.540> point<00:10:55.140> here<00:10:55.410> is<00:10:55.560> that<00:10:55.970> ipfs<00:10:56.970> only 00:10:57.380 --> 00:10:57.390 align:start position:0% another point here is that ipfs only 00:10:57.390 --> 00:11:00.500 align:start position:0% another point here is that ipfs only downloads<00:10:57.920> explicitly<00:10:58.920> requested<00:10:59.339> data<00:10:59.550> you 00:11:00.500 --> 00:11:00.510 align:start position:0% downloads explicitly requested data you 00:11:00.510 --> 00:11:02.030 align:start position:0% downloads explicitly requested data you do<00:11:00.600> not<00:11:00.720> download<00:11:01.020> other<00:11:01.380> people's<00:11:01.740> stuff<00:11:01.920> and 00:11:02.030 --> 00:11:02.040 align:start position:0% do not download other people's stuff and 00:11:02.040 --> 00:11:03.740 align:start position:0% do not download other people's stuff and this<00:11:02.160> is<00:11:02.310> an<00:11:02.399> important<00:11:02.820> piece<00:11:03.060> from<00:11:03.600> a 00:11:03.740 --> 00:11:03.750 align:start position:0% this is an important piece from a 00:11:03.750 --> 00:11:05.600 align:start position:0% this is an important piece from a legality<00:11:04.140> perspective<00:11:04.560> right<00:11:04.770> so<00:11:04.950> there's 00:11:05.600 --> 00:11:05.610 align:start position:0% legality perspective right so there's 00:11:05.610 --> 00:11:07.880 align:start position:0% legality perspective right so there's been<00:11:05.970> a<00:11:06.300> whole<00:11:06.750> bunch<00:11:06.779> of<00:11:07.410> problems<00:11:07.770> around 00:11:07.880 --> 00:11:07.890 align:start position:0% been a whole bunch of problems around 00:11:07.890 --> 00:11:09.590 align:start position:0% been a whole bunch of problems around peer-to-peer<00:11:08.220> systems<00:11:08.730> where<00:11:09.029> they<00:11:09.270> download 00:11:09.590 --> 00:11:09.600 align:start position:0% peer-to-peer systems where they download 00:11:09.600 --> 00:11:11.990 align:start position:0% peer-to-peer systems where they download other<00:11:09.720> data<00:11:10.200> as<00:11:10.950> part<00:11:11.250> of<00:11:11.370> the<00:11:11.580> peer-to-peer 00:11:11.990 --> 00:11:12.000 align:start position:0% other data as part of the peer-to-peer 00:11:12.000 --> 00:11:13.820 align:start position:0% other data as part of the peer-to-peer algorithm<00:11:12.630> and<00:11:12.839> the<00:11:13.170> end<00:11:13.290> of<00:11:13.410> downloading 00:11:13.820 --> 00:11:13.830 align:start position:0% algorithm and the end of downloading 00:11:13.830 --> 00:11:16.070 align:start position:0% algorithm and the end of downloading stuff<00:11:14.010> that's<00:11:14.190> illegal<00:11:14.480> this<00:11:15.480> prevents<00:11:16.020> the 00:11:16.070 --> 00:11:16.080 align:start position:0% stuff that's illegal this prevents the 00:11:16.080 --> 00:11:18.380 align:start position:0% stuff that's illegal this prevents the adoption<00:11:16.649> of<00:11:16.770> these<00:11:16.950> systems<00:11:17.370> in<00:11:17.610> companies 00:11:18.380 --> 00:11:18.390 align:start position:0% adoption of these systems in companies 00:11:18.390 --> 00:11:20.000 align:start position:0% adoption of these systems in companies because<00:11:18.810> companies<00:11:19.170> just<00:11:19.350> cannot<00:11:19.620> afford<00:11:19.890> to 00:11:20.000 --> 00:11:20.010 align:start position:0% because companies just cannot afford to 00:11:20.010 --> 00:11:23.449 align:start position:0% because companies just cannot afford to do<00:11:20.100> that<00:11:20.250> so<00:11:21.120> n<00:11:22.020> ipfs<00:11:22.529> those<00:11:22.770> are<00:11:22.920> policies 00:11:23.449 --> 00:11:23.459 align:start position:0% do that so n ipfs those are policies 00:11:23.459 --> 00:11:25.460 align:start position:0% do that so n ipfs those are policies that<00:11:23.490> are<00:11:23.700> expressed<00:11:24.149> and<00:11:24.330> that<00:11:24.390> can<00:11:24.630> be<00:11:24.750> added 00:11:25.460 --> 00:11:25.470 align:start position:0% that are expressed and that can be added 00:11:25.470 --> 00:11:27.110 align:start position:0% that are expressed and that can be added on<00:11:25.589> top<00:11:25.830> right<00:11:26.070> so<00:11:26.190> if<00:11:26.279> you<00:11:26.399> want<00:11:26.580> to<00:11:26.670> organize 00:11:27.110 --> 00:11:27.120 align:start position:0% on top right so if you want to organize 00:11:27.120 --> 00:11:28.910 align:start position:0% on top right so if you want to organize a<00:11:27.330> cluster<00:11:27.810> that<00:11:27.990> moves<00:11:28.200> around<00:11:28.350> and<00:11:28.649> shares 00:11:28.910 --> 00:11:28.920 align:start position:0% a cluster that moves around and shares 00:11:28.920 --> 00:11:31.430 align:start position:0% a cluster that moves around and shares data<00:11:29.490> and<00:11:29.820> so<00:11:30.000> on<00:11:30.149> you<00:11:30.810> can<00:11:30.930> do<00:11:31.050> that<00:11:31.080> but 00:11:31.430 --> 00:11:31.440 align:start position:0% data and so on you can do that but 00:11:31.440 --> 00:11:33.500 align:start position:0% data and so on you can do that but that's<00:11:31.589> a<00:11:31.680> policy<00:11:31.950> that<00:11:32.130> becomes<00:11:32.430> that<00:11:33.360> is 00:11:33.500 --> 00:11:33.510 align:start position:0% that's a policy that becomes that is 00:11:33.510 --> 00:11:36.650 align:start position:0% that's a policy that becomes that is layered<00:11:33.750> above<00:11:34.260> ipfs<00:11:34.920> so<00:11:35.580> there's<00:11:36.120> a<00:11:36.209> strong 00:11:36.650 --> 00:11:36.660 align:start position:0% layered above ipfs so there's a strong 00:11:36.660 --> 00:11:38.060 align:start position:0% layered above ipfs so there's a strong commitment<00:11:36.899> there<00:11:37.230> of<00:11:37.440> being<00:11:37.740> able<00:11:37.830> to<00:11:37.950> say 00:11:38.060 --> 00:11:38.070 align:start position:0% commitment there of being able to say 00:11:38.070 --> 00:11:40.100 align:start position:0% commitment there of being able to say look<00:11:38.339> you<00:11:38.580> can<00:11:39.000> use<00:11:39.149> ipfs<00:11:39.570> and<00:11:39.750> not<00:11:39.839> have<00:11:39.990> to 00:11:40.100 --> 00:11:40.110 align:start position:0% look you can use ipfs and not have to 00:11:40.110 --> 00:11:41.840 align:start position:0% look you can use ipfs and not have to worry<00:11:40.290> about<00:11:40.350> other<00:11:41.160> people<00:11:41.490> who<00:11:41.640> are<00:11:41.730> other 00:11:41.840 --> 00:11:41.850 align:start position:0% worry about other people who are other 00:11:41.850 --> 00:11:43.389 align:start position:0% worry about other people who are other people<00:11:42.089> are<00:11:42.180> adding<00:11:42.360> to<00:11:42.450> the<00:11:42.510> network<00:11:42.750> and 00:11:43.389 --> 00:11:43.399 align:start position:0% people are adding to the network and 00:11:43.399 --> 00:11:46.519 align:start position:0% people are adding to the network and yeah<00:11:44.399> so<00:11:44.580> I<00:11:45.060> think<00:11:45.390> that's<00:11:45.630> this<00:11:45.720> is<00:11:45.899> able<00:11:46.200> to 00:11:46.519 --> 00:11:46.529 align:start position:0% yeah so I think that's this is able to 00:11:46.529 --> 00:11:49.160 align:start position:0% yeah so I think that's this is able to follow<00:11:47.459> what<00:11:47.610> the<00:11:47.820> user<00:11:48.000> programs<00:11:48.570> and<00:11:48.899> so 00:11:49.160 --> 00:11:49.170 align:start position:0% follow what the user programs and so 00:11:49.170 --> 00:11:52.819 align:start position:0% follow what the user programs and so these<00:11:49.320> policies<00:11:49.860> that<00:11:49.890> will<00:11:50.579> be<00:11:51.470> we<00:11:52.470> haven't 00:11:52.819 --> 00:11:52.829 align:start position:0% these policies that will be we haven't 00:11:52.829 --> 00:11:54.949 align:start position:0% these policies that will be we haven't done<00:11:52.920> as<00:11:53.010> much<00:11:53.040> work<00:11:53.339> here<00:11:53.640> will<00:11:54.060> be<00:11:54.089> doing 00:11:54.949 --> 00:11:54.959 align:start position:0% done as much work here will be doing 00:11:54.959 --> 00:11:56.240 align:start position:0% done as much work here will be doing some<00:11:55.200> interesting<00:11:55.380> stuff<00:11:55.740> there<00:11:55.920> to<00:11:56.100> be<00:11:56.190> able 00:11:56.240 --> 00:11:56.250 align:start position:0% some interesting stuff there to be able 00:11:56.250 --> 00:11:59.030 align:start position:0% some interesting stuff there to be able to<00:11:56.339> express<00:11:56.690> how<00:11:57.690> you<00:11:57.750> might<00:11:58.140> trust<00:11:58.770> other 00:11:59.030 --> 00:11:59.040 align:start position:0% to express how you might trust other 00:11:59.040 --> 00:12:00.769 align:start position:0% to express how you might trust other keys<00:11:59.459> and<00:11:59.790> trust<00:12:00.120> the<00:12:00.209> content<00:12:00.570> from<00:12:00.660> other 00:12:00.769 --> 00:12:00.779 align:start position:0% keys and trust the content from other 00:12:00.779 --> 00:12:02.569 align:start position:0% keys and trust the content from other keys<00:12:00.990> and<00:12:01.260> being<00:12:01.920> able<00:12:02.010> to<00:12:02.100> give<00:12:02.279> people 00:12:02.569 --> 00:12:02.579 align:start position:0% keys and being able to give people 00:12:02.579 --> 00:12:05.740 align:start position:0% keys and being able to give people capabilities<00:12:03.270> to<00:12:04.079> add<00:12:04.620> stuff<00:12:04.950> to<00:12:05.070> your<00:12:05.160> note 00:12:05.740 --> 00:12:05.750 align:start position:0% capabilities to add stuff to your note 00:12:05.750 --> 00:12:08.810 align:start position:0% capabilities to add stuff to your note so<00:12:06.750> yeah<00:12:06.899> on<00:12:07.050> this<00:12:07.200> on<00:12:07.380> this<00:12:07.529> only<00:12:07.820> downloads 00:12:08.810 --> 00:12:08.820 align:start position:0% so yeah on this on this only downloads 00:12:08.820 --> 00:12:10.190 align:start position:0% so yeah on this on this only downloads explicitly<00:12:09.300> requested<00:12:09.630> data<00:12:09.750> so<00:12:09.959> this<00:12:10.050> is<00:12:10.170> a 00:12:10.190 --> 00:12:10.200 align:start position:0% explicitly requested data so this is a 00:12:10.200 --> 00:12:11.420 align:start position:0% explicitly requested data so this is a huge<00:12:10.410> surprise<00:12:10.500> for<00:12:10.740> most<00:12:10.980> people<00:12:11.310> because 00:12:11.420 --> 00:12:11.430 align:start position:0% huge surprise for most people because 00:12:11.430 --> 00:12:13.040 align:start position:0% huge surprise for most people because they're<00:12:11.640> like<00:12:11.730> wait<00:12:11.910> what<00:12:12.360> you<00:12:12.720> have<00:12:12.870> this 00:12:13.040 --> 00:12:13.050 align:start position:0% they're like wait what you have this 00:12:13.050 --> 00:12:14.389 align:start position:0% they're like wait what you have this distributed<00:12:13.560> file<00:12:13.680> system<00:12:14.040> it's<00:12:14.160> supposed<00:12:14.339> to 00:12:14.389 --> 00:12:14.399 align:start position:0% distributed file system it's supposed to 00:12:14.399 --> 00:12:16.910 align:start position:0% distributed file system it's supposed to be<00:12:14.490> pure<00:12:14.610> appear<00:12:14.940> and<00:12:15.180> like<00:12:15.600> why<00:12:16.200> we're<00:12:16.560> like 00:12:16.910 --> 00:12:16.920 align:start position:0% be pure appear and like why we're like 00:12:16.920 --> 00:12:19.760 align:start position:0% be pure appear and like why we're like if<00:12:17.130> I<00:12:17.220> add<00:12:17.339> content<00:12:18.200> how<00:12:19.200> do<00:12:19.260> I<00:12:19.380> back<00:12:19.529> it<00:12:19.649> up 00:12:19.760 --> 00:12:19.770 align:start position:0% if I add content how do I back it up 00:12:19.770 --> 00:12:22.460 align:start position:0% if I add content how do I back it up right<00:12:20.279> like<00:12:20.820> that's<00:12:21.180> what<00:12:21.959> if<00:12:22.050> I<00:12:22.110> disappear 00:12:22.460 --> 00:12:22.470 align:start position:0% right like that's what if I disappear 00:12:22.470 --> 00:12:24.139 align:start position:0% right like that's what if I disappear from<00:12:22.529> the<00:12:22.649> network<00:12:22.890> it<00:12:23.220> pulse<00:12:23.520> it<00:12:23.790> falls<00:12:24.000> off 00:12:24.139 --> 00:12:24.149 align:start position:0% from the network it pulse it falls off 00:12:24.149 --> 00:12:26.120 align:start position:0% from the network it pulse it falls off and<00:12:25.020> the<00:12:25.079> idea<00:12:25.230> here<00:12:25.410> is<00:12:25.470> that<00:12:25.620> when<00:12:25.860> you<00:12:25.890> add 00:12:26.120 --> 00:12:26.130 align:start position:0% and the idea here is that when you add 00:12:26.130 --> 00:12:27.470 align:start position:0% and the idea here is that when you add content<00:12:26.339> to<00:12:26.550> the<00:12:26.640> network<00:12:26.970> you're<00:12:27.180> explicitly 00:12:27.470 --> 00:12:27.480 align:start position:0% content to the network you're explicitly 00:12:27.480 --> 00:12:29.630 align:start position:0% content to the network you're explicitly publishing<00:12:28.200> something<00:12:28.440> so<00:12:29.190> the<00:12:29.310> rest<00:12:29.459> of<00:12:29.550> the 00:12:29.630 --> 00:12:29.640 align:start position:0% publishing something so the rest of the 00:12:29.640 --> 00:12:32.389 align:start position:0% publishing something so the rest of the network<00:12:29.940> has<00:12:30.899> an<00:12:31.079> option<00:12:31.440> either<00:12:31.589> they<00:12:31.890> spend 00:12:32.389 --> 00:12:32.399 align:start position:0% network has an option either they spend 00:12:32.399 --> 00:12:34.819 align:start position:0% network has an option either they spend energy<00:12:32.839> maintaining<00:12:33.839> this<00:12:34.020> online<00:12:34.200> or<00:12:34.620> they 00:12:34.819 --> 00:12:34.829 align:start position:0% energy maintaining this online or they 00:12:34.829 --> 00:12:36.319 align:start position:0% energy maintaining this online or they don't<00:12:34.950> and<00:12:35.190> if<00:12:35.550> they<00:12:35.670> do<00:12:35.730> it's<00:12:36.000> because<00:12:36.089> they 00:12:36.319 --> 00:12:36.329 align:start position:0% don't and if they do it's because they 00:12:36.329 --> 00:12:38.150 align:start position:0% don't and if they do it's because they care<00:12:36.570> about<00:12:36.750> this<00:12:36.870> thing<00:12:36.930> so<00:12:37.410> if<00:12:37.829> they<00:12:38.040> don't 00:12:38.150 --> 00:12:38.160 align:start position:0% care about this thing so if they don't 00:12:38.160 --> 00:12:40.670 align:start position:0% care about this thing so if they don't care<00:12:38.579> about<00:12:38.700> what<00:12:39.060> you<00:12:39.149> have<00:12:39.180> to<00:12:39.329> say<00:12:39.680> because 00:12:40.670 --> 00:12:40.680 align:start position:0% care about what you have to say because 00:12:40.680 --> 00:12:42.319 align:start position:0% care about what you have to say because they<00:12:41.010> just<00:12:41.399> what<00:12:41.850> you<00:12:41.910> say<00:12:42.029> it's<00:12:42.149> not<00:12:42.209> that 00:12:42.319 --> 00:12:42.329 align:start position:0% they just what you say it's not that 00:12:42.329 --> 00:12:44.240 align:start position:0% they just what you say it's not that interesting<00:12:42.450> then<00:12:43.410> you<00:12:43.470> can<00:12:43.589> just<00:12:43.740> pay<00:12:44.070> them 00:12:44.240 --> 00:12:44.250 align:start position:0% interesting then you can just pay them 00:12:44.250 --> 00:12:46.010 align:start position:0% interesting then you can just pay them to<00:12:44.579> care<00:12:44.760> and<00:12:45.000> this<00:12:45.420> is<00:12:45.540> where<00:12:45.660> something<00:12:45.839> like 00:12:46.010 --> 00:12:46.020 align:start position:0% to care and this is where something like 00:12:46.020 --> 00:12:49.850 align:start position:0% to care and this is where something like Falcone<00:12:46.410> comes<00:12:46.620> in<00:12:46.770> so<00:12:47.480> HTTP<00:12:48.480> maps<00:12:48.959> to<00:12:49.320> ipfs 00:12:49.850 --> 00:12:49.860 align:start position:0% Falcone comes in so HTTP maps to ipfs 00:12:49.860 --> 00:12:52.890 align:start position:0% Falcone comes in so HTTP maps to ipfs and<00:12:50.190> AWS<00:12:51.150> s3<00:12:51.240> maps<00:12:51.870> to 00:12:52.890 --> 00:12:52.900 align:start position:0% and AWS s3 maps to 00:12:52.900 --> 00:12:56.400 align:start position:0% and AWS s3 maps to Pal<00:12:53.050> coined<00:12:53.290> or<00:12:53.440> swarm<00:12:54.220> or<00:12:54.610> really<00:12:55.150> AWS<00:12:55.900> and 00:12:56.400 --> 00:12:56.410 align:start position:0% Pal coined or swarm or really AWS and 00:12:56.410 --> 00:12:58.610 align:start position:0% Pal coined or swarm or really AWS and Windows<00:12:57.160> Azure<00:12:57.279> and<00:12:57.610> so<00:12:57.730> on<00:12:57.850> right<00:12:58.060> so<00:12:58.210> there's 00:12:58.610 --> 00:12:58.620 align:start position:0% Windows Azure and so on right so there's 00:12:58.620 --> 00:13:01.200 align:start position:0% Windows Azure and so on right so there's that<00:12:59.620> how<00:12:59.890> you<00:12:59.950> maintain<00:13:00.279> stuff<00:13:00.850> in<00:13:01.060> the 00:13:01.200 --> 00:13:01.210 align:start position:0% that how you maintain stuff in the 00:13:01.210 --> 00:13:05.190 align:start position:0% that how you maintain stuff in the network<00:13:01.620> it's<00:13:02.620> a<00:13:02.740> separate<00:13:03.339> part<00:13:04.200> different 00:13:05.190 --> 00:13:05.200 align:start position:0% network it's a separate part different 00:13:05.200 --> 00:13:07.050 align:start position:0% network it's a separate part different from<00:13:05.529> how<00:13:05.800> you<00:13:05.860> move<00:13:06.310> stuff<00:13:06.580> in<00:13:06.700> the<00:13:06.760> network 00:13:07.050 --> 00:13:07.060 align:start position:0% from how you move stuff in the network 00:13:07.060 --> 00:13:08.850 align:start position:0% from how you move stuff in the network so<00:13:07.270> IP<00:13:07.480> office<00:13:07.750> is<00:13:07.870> strictly<00:13:08.170> about<00:13:08.320> how<00:13:08.800> you 00:13:08.850 --> 00:13:08.860 align:start position:0% so IP office is strictly about how you 00:13:08.860 --> 00:13:12.079 align:start position:0% so IP office is strictly about how you address<00:13:09.339> and<00:13:09.550> move<00:13:10.120> content<00:13:10.510> in<00:13:10.660> the<00:13:10.839> network 00:13:12.079 --> 00:13:12.089 align:start position:0% address and move content in the network 00:13:12.089 --> 00:13:15.600 align:start position:0% address and move content in the network so<00:13:13.089> and<00:13:13.960> this<00:13:14.350> and<00:13:14.589> so<00:13:14.710> these<00:13:15.040> protocols 00:13:15.600 --> 00:13:15.610 align:start position:0% so and this and so these protocols 00:13:15.610 --> 00:13:19.490 align:start position:0% so and this and so these protocols around<00:13:16.440> incentivized<00:13:17.440> organized 00:13:19.490 --> 00:13:19.500 align:start position:0% around incentivized organized 00:13:19.500 --> 00:13:22.079 align:start position:0% around incentivized organized distributed<00:13:20.500> storage<00:13:20.650> those<00:13:21.250> layer<00:13:21.580> on<00:13:21.880> top 00:13:22.079 --> 00:13:22.089 align:start position:0% distributed storage those layer on top 00:13:22.089 --> 00:13:24.960 align:start position:0% distributed storage those layer on top of<00:13:22.210> IP<00:13:22.330> FS<00:13:22.660> and<00:13:23.460> so<00:13:24.460> an<00:13:24.550> interesting<00:13:24.730> thought 00:13:24.960 --> 00:13:24.970 align:start position:0% of IP FS and so an interesting thought 00:13:24.970 --> 00:13:26.430 align:start position:0% of IP FS and so an interesting thought is<00:13:25.150> a<00:13:25.420> lot<00:13:25.660> of<00:13:25.720> people<00:13:25.900> say<00:13:25.990> well<00:13:26.140> how<00:13:26.320> could 00:13:26.430 --> 00:13:26.440 align:start position:0% is a lot of people say well how could 00:13:26.440 --> 00:13:29.040 align:start position:0% is a lot of people say well how could you<00:13:26.500> ever<00:13:26.740> hope<00:13:27.700> to<00:13:27.730> compete<00:13:28.630> with<00:13:28.810> something 00:13:29.040 --> 00:13:29.050 align:start position:0% you ever hope to compete with something 00:13:29.050 --> 00:13:30.840 align:start position:0% you ever hope to compete with something as<00:13:29.350> big<00:13:29.529> as<00:13:29.589> you<00:13:29.860> know<00:13:29.950> Amazon<00:13:30.130> and<00:13:30.490> Google<00:13:30.580> and 00:13:30.840 --> 00:13:30.850 align:start position:0% as big as you know Amazon and Google and 00:13:30.850 --> 00:13:32.280 align:start position:0% as big as you know Amazon and Google and Microsoft<00:13:30.970> and<00:13:31.270> so<00:13:31.420> on<00:13:31.570> which<00:13:32.020> have<00:13:32.170> these 00:13:32.280 --> 00:13:32.290 align:start position:0% Microsoft and so on which have these 00:13:32.290 --> 00:13:35.040 align:start position:0% Microsoft and so on which have these massive<00:13:32.650> infrastructures<00:13:33.520> and<00:13:34.300> then<00:13:34.900> I<00:13:34.930> just 00:13:35.040 --> 00:13:35.050 align:start position:0% massive infrastructures and then I just 00:13:35.050 --> 00:13:36.540 align:start position:0% massive infrastructures and then I just kind<00:13:35.200> of<00:13:35.230> point<00:13:35.440> to<00:13:35.500> them<00:13:35.620> point<00:13:36.130> this<00:13:36.339> out 00:13:36.540 --> 00:13:36.550 align:start position:0% kind of point to them point this out 00:13:36.550 --> 00:13:38.460 align:start position:0% kind of point to them point this out right<00:13:36.790> so<00:13:36.940> this<00:13:37.029> is<00:13:37.089> the<00:13:37.270> hash<00:13:37.450> rate<00:13:37.750> of<00:13:37.990> the 00:13:38.460 --> 00:13:38.470 align:start position:0% right so this is the hash rate of the 00:13:38.470 --> 00:13:40.530 align:start position:0% right so this is the hash rate of the Bitcoin<00:13:38.770> network<00:13:38.830> and<00:13:39.790> like<00:13:40.150> the<00:13:40.300> massive 00:13:40.530 --> 00:13:40.540 align:start position:0% Bitcoin network and like the massive 00:13:40.540 --> 00:13:42.900 align:start position:0% Bitcoin network and like the massive spike<00:13:40.990> and<00:13:41.710> this<00:13:42.070> is<00:13:42.190> what<00:13:42.310> happens<00:13:42.640> when<00:13:42.790> you 00:13:42.900 --> 00:13:42.910 align:start position:0% spike and this is what happens when you 00:13:42.910 --> 00:13:47.700 align:start position:0% spike and this is what happens when you get<00:13:43.060> a<00:13:43.750> an<00:13:44.710> economic<00:13:45.610> model<00:13:46.290> coupled<00:13:47.290> with<00:13:47.380> a 00:13:47.700 --> 00:13:47.710 align:start position:0% get a an economic model coupled with a 00:13:47.710 --> 00:13:50.220 align:start position:0% get a an economic model coupled with a very<00:13:48.040> easy<00:13:48.130> to<00:13:48.520> enter<00:13:48.760> market<00:13:49.089> and<00:13:49.990> so 00:13:50.220 --> 00:13:50.230 align:start position:0% very easy to enter market and so 00:13:50.230 --> 00:13:52.290 align:start position:0% very easy to enter market and so somewhere<00:13:51.220> along<00:13:51.400> this<00:13:51.610> graph<00:13:51.760> way<00:13:52.029> before 00:13:52.290 --> 00:13:52.300 align:start position:0% somewhere along this graph way before 00:13:52.300 --> 00:13:55.410 align:start position:0% somewhere along this graph way before the<00:13:52.450> knee<00:13:52.740> the<00:13:53.740> hash<00:13:54.400> rate<00:13:54.700> of<00:13:54.940> bitcoins 00:13:55.410 --> 00:13:55.420 align:start position:0% the knee the hash rate of bitcoins 00:13:55.420 --> 00:13:58.500 align:start position:0% the knee the hash rate of bitcoins surpassed<00:13:56.100> the<00:13:57.100> equivalent<00:13:57.610> of<00:13:57.790> the<00:13:58.209> world's 00:13:58.500 --> 00:13:58.510 align:start position:0% surpassed the equivalent of the world's 00:13:58.510 --> 00:14:00.360 align:start position:0% surpassed the equivalent of the world's most<00:13:58.630> powerful<00:13:59.140> supercomputer<00:13:59.680> and<00:13:59.830> then<00:14:00.250> the 00:14:00.360 --> 00:14:00.370 align:start position:0% most powerful supercomputer and then the 00:14:00.370 --> 00:14:02.130 align:start position:0% most powerful supercomputer and then the world's<00:14:00.640> 500<00:14:01.270> supercomputers<00:14:01.600> put<00:14:02.020> together 00:14:02.130 --> 00:14:02.140 align:start position:0% world's 500 supercomputers put together 00:14:02.140 --> 00:14:04.500 align:start position:0% world's 500 supercomputers put together before<00:14:02.800> the<00:14:03.220> knee<00:14:03.310> of<00:14:03.430> the<00:14:03.459> curve<00:14:03.550> so<00:14:04.480> that 00:14:04.500 --> 00:14:04.510 align:start position:0% before the knee of the curve so that 00:14:04.510 --> 00:14:06.540 align:start position:0% before the knee of the curve so that gives<00:14:04.720> you<00:14:04.839> a<00:14:04.870> sense<00:14:05.080> of<00:14:05.260> just<00:14:05.320> how<00:14:05.680> insanely 00:14:06.540 --> 00:14:06.550 align:start position:0% gives you a sense of just how insanely 00:14:06.550 --> 00:14:08.790 align:start position:0% gives you a sense of just how insanely powerful<00:14:07.060> the<00:14:07.510> the<00:14:08.110> hash<00:14:08.320> rate<00:14:08.560> of<00:14:08.709> that 00:14:08.790 --> 00:14:08.800 align:start position:0% powerful the the hash rate of that 00:14:08.800 --> 00:14:11.100 align:start position:0% powerful the the hash rate of that network<00:14:09.070> is<00:14:09.450> sadly<00:14:10.450> all<00:14:10.570> that<00:14:10.750> is<00:14:10.839> going<00:14:10.959> to 00:14:11.100 --> 00:14:11.110 align:start position:0% network is sadly all that is going to 00:14:11.110 --> 00:14:13.470 align:start position:0% network is sadly all that is going to waste<00:14:11.260> so<00:14:11.740> hopefully<00:14:12.730> we'll<00:14:13.150> get<00:14:13.270> proved 00:14:13.470 --> 00:14:13.480 align:start position:0% waste so hopefully we'll get proved 00:14:13.480 --> 00:14:15.150 align:start position:0% waste so hopefully we'll get proved mistake<00:14:13.750> working<00:14:14.410> correctly<00:14:14.620> so<00:14:14.950> we<00:14:15.040> don't 00:14:15.150 --> 00:14:15.160 align:start position:0% mistake working correctly so we don't 00:14:15.160 --> 00:14:17.070 align:start position:0% mistake working correctly so we don't have<00:14:15.220> to<00:14:15.339> like<00:14:15.430> waste<00:14:15.820> this<00:14:15.970> but<00:14:16.180> when<00:14:16.900> you 00:14:17.070 --> 00:14:17.080 align:start position:0% have to like waste this but when you 00:14:17.080 --> 00:14:18.570 align:start position:0% have to like waste this but when you when<00:14:17.290> you<00:14:17.410> think<00:14:17.650> about<00:14:17.800> this<00:14:17.950> model<00:14:18.310> and<00:14:18.459> you 00:14:18.570 --> 00:14:18.580 align:start position:0% when you think about this model and you 00:14:18.580 --> 00:14:21.470 align:start position:0% when you think about this model and you apply<00:14:18.850> it<00:14:18.880> to<00:14:19.029> doing<00:14:19.690> something<00:14:19.990> useful<00:14:20.200> like 00:14:21.470 --> 00:14:21.480 align:start position:0% apply it to doing something useful like 00:14:21.480 --> 00:14:25.440 align:start position:0% apply it to doing something useful like storing<00:14:22.480> content<00:14:22.959> you<00:14:23.920> can<00:14:24.100> get<00:14:24.490> an<00:14:24.670> enormous 00:14:25.440 --> 00:14:25.450 align:start position:0% storing content you can get an enormous 00:14:25.450 --> 00:14:27.060 align:start position:0% storing content you can get an enormous amount<00:14:25.630> of<00:14:25.810> storage<00:14:26.020> wired<00:14:26.680> up<00:14:26.830> into<00:14:27.010> the 00:14:27.060 --> 00:14:27.070 align:start position:0% amount of storage wired up into the 00:14:27.070 --> 00:14:29.760 align:start position:0% amount of storage wired up into the network<00:14:27.310> so<00:14:27.790> you'll<00:14:28.150> steal<00:14:28.360> so<00:14:28.510> mark<00:14:29.350> my<00:14:29.500> words 00:14:29.760 --> 00:14:29.770 align:start position:0% network so you'll steal so mark my words 00:14:29.770 --> 00:14:31.860 align:start position:0% network so you'll steal so mark my words in<00:14:30.070> the<00:14:30.250> next<00:14:30.459> year<00:14:30.700> and<00:14:30.820> two<00:14:30.970> years<00:14:31.209> you<00:14:31.779> will 00:14:31.860 --> 00:14:31.870 align:start position:0% in the next year and two years you will 00:14:31.870 --> 00:14:35.400 align:start position:0% in the next year and two years you will see<00:14:31.930> enormous<00:14:33.390> distributed<00:14:34.390> systems<00:14:34.750> with 00:14:35.400 --> 00:14:35.410 align:start position:0% see enormous distributed systems with 00:14:35.410 --> 00:14:37.140 align:start position:0% see enormous distributed systems with storage<00:14:35.770> popping<00:14:36.370> up<00:14:36.459> into<00:14:36.580> the<00:14:36.700> network<00:14:36.970> and 00:14:37.140 --> 00:14:37.150 align:start position:0% storage popping up into the network and 00:14:37.150 --> 00:14:39.510 align:start position:0% storage popping up into the network and they're<00:14:37.540> already<00:14:37.720> getting<00:14:37.870> started<00:14:38.320> but<00:14:39.279> oh 00:14:39.510 --> 00:14:39.520 align:start position:0% they're already getting started but oh 00:14:39.520 --> 00:14:41.400 align:start position:0% they're already getting started but oh come<00:14:39.940> and<00:14:40.150> so<00:14:40.690> you<00:14:40.779> have<00:14:40.959> something<00:14:41.290> that 00:14:41.400 --> 00:14:41.410 align:start position:0% come and so you have something that 00:14:41.410 --> 00:14:42.750 align:start position:0% come and so you have something that looks<00:14:41.589> like<00:14:41.680> this<00:14:41.950> which<00:14:42.160> are<00:14:42.279> the<00:14:42.370> Bitcoin 00:14:42.750 --> 00:14:42.760 align:start position:0% looks like this which are the Bitcoin 00:14:42.760 --> 00:14:47.460 align:start position:0% looks like this which are the Bitcoin mines<00:14:43.029> but<00:14:43.690> for<00:14:43.900> storage<00:14:45.600> all<00:14:46.600> right<00:14:46.750> so<00:14:46.900> now 00:14:47.460 --> 00:14:47.470 align:start position:0% mines but for storage all right so now 00:14:47.470 --> 00:14:49.949 align:start position:0% mines but for storage all right so now that<00:14:47.529> I've<00:14:47.709> kind<00:14:47.860> of<00:14:48.390> made<00:14:49.390> a<00:14:49.450> claim<00:14:49.690> about<00:14:49.810> the 00:14:49.949 --> 00:14:49.959 align:start position:0% that I've kind of made a claim about the 00:14:49.959 --> 00:14:51.630 align:start position:0% that I've kind of made a claim about the future<00:14:50.200> let's<00:14:50.770> have<00:14:50.890> a<00:14:50.920> dose<00:14:51.130> of<00:14:51.279> like<00:14:51.490> web 00:14:51.630 --> 00:14:51.640 align:start position:0% future let's have a dose of like web 00:14:51.640 --> 00:14:52.920 align:start position:0% future let's have a dose of like web reality<00:14:52.060> today<00:14:52.209> to<00:14:52.330> like 00:14:52.920 --> 00:14:52.930 align:start position:0% reality today to like 00:14:52.930 --> 00:14:54.930 align:start position:0% reality today to like cleanse<00:14:53.320> our<00:14:53.470> minds<00:14:53.650> right<00:14:53.950> so<00:14:54.190> so<00:14:54.670> the<00:14:54.760> web 00:14:54.930 --> 00:14:54.940 align:start position:0% cleanse our minds right so so the web 00:14:54.940 --> 00:14:57.900 align:start position:0% cleanse our minds right so so the web here<00:14:55.330> and<00:14:55.510> these<00:14:56.470> are<00:14:56.800> strictly<00:14:57.400> kind<00:14:57.760> of<00:14:57.820> like 00:14:57.900 --> 00:14:57.910 align:start position:0% here and these are strictly kind of like 00:14:57.910 --> 00:15:01.530 align:start position:0% here and these are strictly kind of like web<00:14:58.060> 1.0<00:14:58.480> web<00:14:58.959> 2.0<00:14:59.350> companies<00:14:59.740> or<00:15:00.360> web<00:15:01.360> sites 00:15:01.530 --> 00:15:01.540 align:start position:0% web 1.0 web 2.0 companies or web sites 00:15:01.540 --> 00:15:04.380 align:start position:0% web 1.0 web 2.0 companies or web sites in<00:15:01.660> general<00:15:01.780> that<00:15:02.140> I've<00:15:02.230> put<00:15:02.560> up<00:15:02.650> there 00:15:04.380 --> 00:15:04.390 align:start position:0% in general that I've put up there 00:15:04.390 --> 00:15:07.180 align:start position:0% in general that I've put up there these<00:15:05.390> applications<00:15:06.110> kind<00:15:06.560> of<00:15:06.680> run<00:15:06.830> your<00:15:07.010> life 00:15:07.180 --> 00:15:07.190 align:start position:0% these applications kind of run your life 00:15:07.190 --> 00:15:09.430 align:start position:0% these applications kind of run your life right<00:15:07.460> so<00:15:07.670> everything<00:15:08.300> that<00:15:08.420> you<00:15:08.480> do<00:15:08.630> nowadays 00:15:09.430 --> 00:15:09.440 align:start position:0% right so everything that you do nowadays 00:15:09.440 --> 00:15:12.190 align:start position:0% right so everything that you do nowadays revolves<00:15:10.100> in<00:15:10.160> some<00:15:10.339> way<00:15:10.520> around<00:15:10.760> these<00:15:11.750> these 00:15:12.190 --> 00:15:12.200 align:start position:0% revolves in some way around these these 00:15:12.200 --> 00:15:15.190 align:start position:0% revolves in some way around these these applications<00:15:12.860> right<00:15:13.070> so<00:15:13.900> your<00:15:14.900> personal 00:15:15.190 --> 00:15:15.200 align:start position:0% applications right so your personal 00:15:15.200 --> 00:15:20.290 align:start position:0% applications right so your personal communications<00:15:15.770> your<00:15:16.730> work<00:15:18.880> how<00:15:19.880> you<00:15:19.910> learn 00:15:20.290 --> 00:15:20.300 align:start position:0% communications your work how you learn 00:15:20.300 --> 00:15:23.310 align:start position:0% communications your work how you learn how<00:15:20.810> you<00:15:20.870> get<00:15:21.529> stuff<00:15:22.070> how<00:15:22.490> do<00:15:22.550> you<00:15:22.670> buy<00:15:22.850> food 00:15:23.310 --> 00:15:23.320 align:start position:0% how you get stuff how do you buy food 00:15:23.320 --> 00:15:26.050 align:start position:0% how you get stuff how do you buy food everything<00:15:24.320> is<00:15:24.650> now<00:15:25.220> mediated<00:15:25.730> not<00:15:25.880> only 00:15:26.050 --> 00:15:26.060 align:start position:0% everything is now mediated not only 00:15:26.060 --> 00:15:26.950 align:start position:0% everything is now mediated not only through<00:15:26.240> the<00:15:26.300> internet<00:15:26.330> but<00:15:26.779> through 00:15:26.950 --> 00:15:26.960 align:start position:0% through the internet but through 00:15:26.960 --> 00:15:29.200 align:start position:0% through the internet but through specifically<00:15:27.589> web<00:15:27.920> applications<00:15:28.490> and<00:15:28.760> this 00:15:29.200 --> 00:15:29.210 align:start position:0% specifically web applications and this 00:15:29.210 --> 00:15:31.360 align:start position:0% specifically web applications and this means<00:15:29.510> that<00:15:29.690> all<00:15:29.870> of<00:15:29.900> your<00:15:30.650> capabilities<00:15:31.339> are 00:15:31.360 --> 00:15:31.370 align:start position:0% means that all of your capabilities are 00:15:31.370 --> 00:15:33.870 align:start position:0% means that all of your capabilities are tied<00:15:31.820> to<00:15:32.150> specific<00:15:32.830> organizations 00:15:33.870 --> 00:15:33.880 align:start position:0% tied to specific organizations 00:15:33.880 --> 00:15:36.130 align:start position:0% tied to specific organizations maintaining<00:15:34.880> specific<00:15:35.480> infrastructures 00:15:36.130 --> 00:15:36.140 align:start position:0% maintaining specific infrastructures 00:15:36.140 --> 00:15:37.470 align:start position:0% maintaining specific infrastructures online 00:15:37.470 --> 00:15:37.480 align:start position:0% online 00:15:37.480 --> 00:15:40.060 align:start position:0% online it's<00:15:38.480> got<00:15:38.600> scary<00:15:38.839> right<00:15:39.320> because<00:15:39.620> those<00:15:39.860> could 00:15:40.060 --> 00:15:40.070 align:start position:0% it's got scary right because those could 00:15:40.070 --> 00:15:41.890 align:start position:0% it's got scary right because those could be<00:15:40.100> this<00:15:40.910> wouldn't<00:15:41.120> disappear<00:15:41.420> at<00:15:41.540> any<00:15:41.570> moment 00:15:41.890 --> 00:15:41.900 align:start position:0% be this wouldn't disappear at any moment 00:15:41.900 --> 00:15:43.660 align:start position:0% be this wouldn't disappear at any moment in<00:15:41.960> time<00:15:41.990> or<00:15:42.350> those<00:15:42.529> could<00:15:42.740> just<00:15:42.980> stop<00:15:43.370> wanting 00:15:43.660 --> 00:15:43.670 align:start position:0% in time or those could just stop wanting 00:15:43.670 --> 00:15:47.740 align:start position:0% in time or those could just stop wanting to<00:15:43.760> serve<00:15:43.910> you<00:15:44.060> or<00:15:44.330> blah<00:15:45.140> blah<00:15:45.620> right<00:15:46.750> but 00:15:47.740 --> 00:15:47.750 align:start position:0% to serve you or blah blah right but 00:15:47.750 --> 00:15:50.140 align:start position:0% to serve you or blah blah right but these<00:15:47.930> I<00:15:48.470> like<00:15:49.339> pointing<00:15:49.820> these<00:15:49.940> out 00:15:50.140 --> 00:15:50.150 align:start position:0% these I like pointing these out 00:15:50.150 --> 00:15:52.540 align:start position:0% these I like pointing these out especially<00:15:50.360> in<00:15:50.930> this<00:15:51.110> crowd<00:15:51.380> because<00:15:51.770> this<00:15:52.339> is 00:15:52.540 --> 00:15:52.550 align:start position:0% especially in this crowd because this is 00:15:52.550 --> 00:15:53.920 align:start position:0% especially in this crowd because this is kind<00:15:52.790> of<00:15:52.850> the<00:15:52.970> competition<00:15:53.450> right<00:15:53.600> so<00:15:53.750> if<00:15:53.839> we 00:15:53.920 --> 00:15:53.930 align:start position:0% kind of the competition right so if we 00:15:53.930 --> 00:15:55.329 align:start position:0% kind of the competition right so if we want<00:15:54.110> to<00:15:54.140> push<00:15:54.350> this<00:15:54.500> very<00:15:54.710> different<00:15:55.070> model 00:15:55.329 --> 00:15:55.339 align:start position:0% want to push this very different model 00:15:55.339 --> 00:15:57.070 align:start position:0% want to push this very different model of<00:15:55.430> computation<00:15:55.670> very<00:15:56.390> different<00:15:56.690> model<00:15:56.960> of 00:15:57.070 --> 00:15:57.080 align:start position:0% of computation very different model of 00:15:57.080 --> 00:16:01.390 align:start position:0% of computation very different model of storage<00:15:57.410> and<00:15:59.380> actually<00:16:00.380> upgrade<00:16:00.860> how<00:16:01.070> the<00:16:01.130> web 00:16:01.390 --> 00:16:01.400 align:start position:0% storage and actually upgrade how the web 00:16:01.400 --> 00:16:04.240 align:start position:0% storage and actually upgrade how the web works<00:16:01.430> we<00:16:02.210> have<00:16:02.390> to<00:16:02.510> work<00:16:02.830> equally<00:16:03.830> well<00:16:03.920> at 00:16:04.240 --> 00:16:04.250 align:start position:0% works we have to work equally well at 00:16:04.250 --> 00:16:07.000 align:start position:0% works we have to work equally well at least<00:16:04.550> and<00:16:04.910> ideally<00:16:05.420> better<00:16:05.890> than<00:16:06.890> these 00:16:07.000 --> 00:16:07.010 align:start position:0% least and ideally better than these 00:16:07.010 --> 00:16:08.769 align:start position:0% least and ideally better than these systems<00:16:07.370> in<00:16:07.520> fact<00:16:07.700> not<00:16:07.970> only<00:16:08.180> do<00:16:08.390> we<00:16:08.510> have<00:16:08.630> to 00:16:08.769 --> 00:16:08.779 align:start position:0% systems in fact not only do we have to 00:16:08.779 --> 00:16:11.290 align:start position:0% systems in fact not only do we have to work<00:16:08.930> equally<00:16:09.260> well<00:16:09.350> ideally<00:16:10.040> better<00:16:10.310> we<00:16:10.850> must 00:16:11.290 --> 00:16:11.300 align:start position:0% work equally well ideally better we must 00:16:11.300 --> 00:16:15.940 align:start position:0% work equally well ideally better we must be<00:16:11.779> way<00:16:12.440> more<00:16:12.820> weight<00:16:13.820> we<00:16:14.330> have<00:16:14.540> to<00:16:14.750> have<00:16:14.990> much 00:16:15.940 --> 00:16:15.950 align:start position:0% be way more weight we have to have much 00:16:15.950 --> 00:16:17.650 align:start position:0% be way more weight we have to have much higher<00:16:16.190> performance<00:16:16.430> or<00:16:16.970> none<00:16:17.480> of<00:16:17.510> these 00:16:17.650 --> 00:16:17.660 align:start position:0% higher performance or none of these 00:16:17.660 --> 00:16:19.660 align:start position:0% higher performance or none of these people<00:16:17.930> will<00:16:18.050> adopt<00:16:18.290> this<00:16:18.470> stuff<00:16:18.680> right<00:16:19.430> and 00:16:19.660 --> 00:16:19.670 align:start position:0% people will adopt this stuff right and 00:16:19.670 --> 00:16:21.610 align:start position:0% people will adopt this stuff right and so<00:16:19.790> this<00:16:20.420> is<00:16:20.600> what<00:16:20.750> I<00:16:20.779> mean<00:16:20.930> by<00:16:21.080> like<00:16:21.230> a<00:16:21.260> dose<00:16:21.529> of 00:16:21.610 --> 00:16:21.620 align:start position:0% so this is what I mean by like a dose of 00:16:21.620 --> 00:16:22.720 align:start position:0% so this is what I mean by like a dose of reality<00:16:21.800> and<00:16:22.100> they're<00:16:22.220> like<00:16:22.339> when<00:16:22.550> you<00:16:22.640> think 00:16:22.720 --> 00:16:22.730 align:start position:0% reality and they're like when you think 00:16:22.730 --> 00:16:25.240 align:start position:0% reality and they're like when you think about<00:16:22.850> the<00:16:23.060> data<00:16:23.209> on<00:16:23.360> the<00:16:23.450> web<00:16:23.570> today<00:16:24.010> you<00:16:25.010> have 00:16:25.240 --> 00:16:25.250 align:start position:0% about the data on the web today you have 00:16:25.250 --> 00:16:26.800 align:start position:0% about the data on the web today you have like<00:16:25.550> these<00:16:25.670> massive<00:16:26.000> infrastructure 00:16:26.800 --> 00:16:26.810 align:start position:0% like these massive infrastructure 00:16:26.810 --> 00:16:29.320 align:start position:0% like these massive infrastructure providers<00:16:27.230> that<00:16:27.410> are<00:16:27.470> there<00:16:27.860> have<00:16:28.220> huge<00:16:29.150> high 00:16:29.320 --> 00:16:29.330 align:start position:0% providers that are there have huge high 00:16:29.330 --> 00:16:31.510 align:start position:0% providers that are there have huge high performance<00:16:29.720> databases<00:16:30.230> and<00:16:31.100> and<00:16:31.310> sort<00:16:31.490> of 00:16:31.510 --> 00:16:31.520 align:start position:0% performance databases and and sort of 00:16:31.520 --> 00:16:33.820 align:start position:0% performance databases and and sort of the<00:16:31.610> model<00:16:31.910> is<00:16:32.120> that<00:16:32.620> people<00:16:33.620> have<00:16:33.740> these 00:16:33.820 --> 00:16:33.830 align:start position:0% the model is that people have these 00:16:33.830 --> 00:16:35.290 align:start position:0% the model is that people have these business<00:16:34.190> logic<00:16:34.339> services<00:16:34.880> and<00:16:35.000> they<00:16:35.060> have<00:16:35.089> to 00:16:35.290 --> 00:16:35.300 align:start position:0% business logic services and they have to 00:16:35.300 --> 00:16:37.860 align:start position:0% business logic services and they have to maintain<00:16:35.420> them<00:16:35.779> and<00:16:36.290> this<00:16:36.680> is<00:16:36.800> where<00:16:36.980> perhaps 00:16:37.860 --> 00:16:37.870 align:start position:0% maintain them and this is where perhaps 00:16:37.870 --> 00:16:40.630 align:start position:0% maintain them and this is where perhaps these<00:16:38.870> systems<00:16:39.320> can<00:16:39.529> come<00:16:39.709> in<00:16:39.860> and<00:16:40.100> change<00:16:40.550> the 00:16:40.630 --> 00:16:40.640 align:start position:0% these systems can come in and change the 00:16:40.640 --> 00:16:41.949 align:start position:0% these systems can come in and change the model<00:16:41.000> where<00:16:41.150> the<00:16:41.270> people<00:16:41.690> don't<00:16:41.839> actually 00:16:41.949 --> 00:16:41.959 align:start position:0% model where the people don't actually 00:16:41.959 --> 00:16:43.810 align:start position:0% model where the people don't actually have<00:16:42.410> to<00:16:42.470> maintain<00:16:42.820> infrastructure 00:16:43.810 --> 00:16:43.820 align:start position:0% have to maintain infrastructure 00:16:43.820 --> 00:16:45.340 align:start position:0% have to maintain infrastructure themselves<00:16:44.360> it<00:16:44.450> becomes<00:16:44.660> a<00:16:44.690> lot<00:16:44.870> cheaper<00:16:45.080> if 00:16:45.340 --> 00:16:45.350 align:start position:0% themselves it becomes a lot cheaper if 00:16:45.350 --> 00:16:48.220 align:start position:0% themselves it becomes a lot cheaper if they<00:16:45.440> don't<00:16:45.589> have<00:16:45.709> to<00:16:45.770> do<00:16:45.860> that<00:16:46.930> but<00:16:47.930> you<00:16:48.140> know 00:16:48.220 --> 00:16:48.230 align:start position:0% they don't have to do that but you know 00:16:48.230 --> 00:16:49.870 align:start position:0% they don't have to do that but you know this<00:16:48.770> is<00:16:48.890> the<00:16:49.070> competition<00:16:49.279> right<00:16:49.640> like<00:16:49.760> this 00:16:49.870 --> 00:16:49.880 align:start position:0% this is the competition right like this 00:16:49.880 --> 00:16:51.940 align:start position:0% this is the competition right like this is<00:16:50.000> something<00:16:50.180> it's<00:16:50.810> an<00:16:50.959> diagram<00:16:51.470> from<00:16:51.560> Amazon 00:16:51.940 --> 00:16:51.950 align:start position:0% is something it's an diagram from Amazon 00:16:51.950 --> 00:16:55.269 align:start position:0% is something it's an diagram from Amazon itself<00:16:52.570> it<00:16:53.570> has<00:16:53.810> like<00:16:54.140> think<00:16:54.980> about<00:16:55.130> how<00:16:55.220> many 00:16:55.269 --> 00:16:55.279 align:start position:0% itself it has like think about how many 00:16:55.279 --> 00:16:57.610 align:start position:0% itself it has like think about how many machines<00:16:55.760> here<00:16:56.089> are<00:16:56.270> involved<00:16:56.779> in<00:16:56.959> just<00:16:57.350> like 00:16:57.610 --> 00:16:57.620 align:start position:0% machines here are involved in just like 00:16:57.620 --> 00:16:59.650 align:start position:0% machines here are involved in just like one<00:16:58.400> application<00:16:59.000> right<00:16:59.240> this<00:16:59.360> is<00:16:59.450> kind<00:16:59.570> of 00:16:59.650 --> 00:16:59.660 align:start position:0% one application right this is kind of 00:16:59.660 --> 00:17:01.060 align:start position:0% one application right this is kind of like<00:16:59.779> if<00:17:00.020> you<00:17:00.230> if<00:17:00.529> you're<00:17:00.650> a<00:17:00.680> legit 00:17:01.060 --> 00:17:01.070 align:start position:0% like if you if you're a legit 00:17:01.070 --> 00:17:02.530 align:start position:0% like if you if you're a legit application<00:17:01.580> this<00:17:01.730> is<00:17:01.790> what<00:17:01.970> you<00:17:02.060> do<00:17:02.180> you<00:17:02.390> have 00:17:02.530 --> 00:17:02.540 align:start position:0% application this is what you do you have 00:17:02.540 --> 00:17:04.840 align:start position:0% application this is what you do you have like<00:17:02.690> a<00:17:02.720> DNS<00:17:03.110> resolution<00:17:03.230> machine<00:17:03.850> connected 00:17:04.840 --> 00:17:04.850 align:start position:0% like a DNS resolution machine connected 00:17:04.850 --> 00:17:07.660 align:start position:0% like a DNS resolution machine connected to<00:17:04.880> like<00:17:05.059> a<00:17:05.089> CDN<00:17:05.600> connected<00:17:06.319> to<00:17:06.410> like<00:17:06.589> a<00:17:06.800> bunch 00:17:07.660 --> 00:17:07.670 align:start position:0% to like a CDN connected to like a bunch 00:17:07.670 --> 00:17:09.850 align:start position:0% to like a CDN connected to like a bunch of<00:17:07.760> static<00:17:07.970> content<00:17:08.660> buckets<00:17:09.260> connected<00:17:09.740> to<00:17:09.829> a 00:17:09.850 --> 00:17:09.860 align:start position:0% of static content buckets connected to a 00:17:09.860 --> 00:17:11.199 align:start position:0% of static content buckets connected to a whole<00:17:10.100> bunch<00:17:10.130> of<00:17:10.370> web<00:17:10.490> servers<00:17:10.760> that<00:17:10.910> all<00:17:11.089> the 00:17:11.199 --> 00:17:11.209 align:start position:0% whole bunch of web servers that all the 00:17:11.209 --> 00:17:12.910 align:start position:0% whole bunch of web servers that all the scale<00:17:11.510> connected<00:17:11.929> to<00:17:11.990> like<00:17:12.140> routers<00:17:12.620> which 00:17:12.910 --> 00:17:12.920 align:start position:0% scale connected to like routers which 00:17:12.920 --> 00:17:15.069 align:start position:0% scale connected to like routers which hit<00:17:13.730> your<00:17:13.880> application<00:17:14.390> servers<00:17:14.750> and<00:17:14.990> then 00:17:15.069 --> 00:17:15.079 align:start position:0% hit your application servers and then 00:17:15.079 --> 00:17:16.360 align:start position:0% hit your application servers and then going<00:17:15.319> all<00:17:15.439> the<00:17:15.500> way<00:17:15.560> to<00:17:15.650> the<00:17:15.800> databases<00:17:16.130> like 00:17:16.360 --> 00:17:16.370 align:start position:0% going all the way to the databases like 00:17:16.370 --> 00:17:17.120 align:start position:0% going all the way to the databases like it's 00:17:17.120 --> 00:17:17.130 align:start position:0% it's 00:17:17.130 --> 00:17:20.120 align:start position:0% it's madness<00:17:17.730> right<00:17:18.120> and<00:17:18.390> this<00:17:18.870> is<00:17:19.050> all<00:17:19.230> up<00:17:19.440> all<00:17:19.709> for 00:17:20.120 --> 00:17:20.130 align:start position:0% madness right and this is all up all for 00:17:20.130 --> 00:17:22.730 align:start position:0% madness right and this is all up all for like<00:17:20.250> optimizing<00:17:21.150> really<00:17:21.630> fast<00:17:21.930> accesses<00:17:22.589> on 00:17:22.730 --> 00:17:22.740 align:start position:0% like optimizing really fast accesses on 00:17:22.740 --> 00:17:24.890 align:start position:0% like optimizing really fast accesses on the<00:17:22.829> network<00:17:23.130> like<00:17:23.339> when<00:17:24.180> I<00:17:24.209> user<00:17:24.449> hits<00:17:24.750> your 00:17:24.890 --> 00:17:24.900 align:start position:0% the network like when I user hits your 00:17:24.900 --> 00:17:26.420 align:start position:0% the network like when I user hits your web<00:17:25.020> page<00:17:25.199> they<00:17:25.380> have<00:17:25.560> to<00:17:25.709> get<00:17:25.860> the<00:17:25.980> stuff<00:17:26.190> like 00:17:26.420 --> 00:17:26.430 align:start position:0% web page they have to get the stuff like 00:17:26.430 --> 00:17:28.850 align:start position:0% web page they have to get the stuff like within<00:17:26.970> a<00:17:27.120> second<00:17:27.540> or<00:17:27.720> like<00:17:27.959> it<00:17:28.140> so<00:17:28.380> game<00:17:28.590> over 00:17:28.850 --> 00:17:28.860 align:start position:0% within a second or like it so game over 00:17:28.860 --> 00:17:30.170 align:start position:0% within a second or like it so game over right<00:17:29.010> like<00:17:29.130> they'll<00:17:29.310> leave<00:17:29.790> and<00:17:30.000> they'll<00:17:30.090> go 00:17:30.170 --> 00:17:30.180 align:start position:0% right like they'll leave and they'll go 00:17:30.180 --> 00:17:31.760 align:start position:0% right like they'll leave and they'll go to<00:17:30.210> somewhere<00:17:30.480> else<00:17:30.540> and<00:17:31.200> so<00:17:31.290> this<00:17:31.500> is<00:17:31.650> like 00:17:31.760 --> 00:17:31.770 align:start position:0% to somewhere else and so this is like 00:17:31.770 --> 00:17:33.890 align:start position:0% to somewhere else and so this is like the<00:17:31.860> beasts<00:17:32.370> lying<00:17:32.940> in<00:17:33.270> the<00:17:33.360> center<00:17:33.660> of<00:17:33.810> the 00:17:33.890 --> 00:17:33.900 align:start position:0% the beasts lying in the center of the 00:17:33.900 --> 00:17:36.110 align:start position:0% the beasts lying in the center of the backbone<00:17:34.290> like<00:17:34.770> to<00:17:34.980> just<00:17:35.280> be<00:17:35.580> able<00:17:35.790> to<00:17:35.910> manage 00:17:36.110 --> 00:17:36.120 align:start position:0% backbone like to just be able to manage 00:17:36.120 --> 00:17:39.920 align:start position:0% backbone like to just be able to manage that<00:17:37.100> but<00:17:38.100> and<00:17:38.490> we<00:17:38.970> have<00:17:39.150> this<00:17:39.270> enormous 00:17:39.920 --> 00:17:39.930 align:start position:0% that but and we have this enormous 00:17:39.930 --> 00:17:42.890 align:start position:0% that but and we have this enormous explosion<00:17:40.200> of<00:17:40.710> like<00:17:40.830> databases<00:17:41.220> right<00:17:41.600> and<00:17:42.600> so 00:17:42.890 --> 00:17:42.900 align:start position:0% explosion of like databases right and so 00:17:42.900 --> 00:17:44.600 align:start position:0% explosion of like databases right and so the<00:17:43.290> constraints<00:17:43.860> are<00:17:43.950> around<00:17:44.190> like<00:17:44.400> being 00:17:44.600 --> 00:17:44.610 align:start position:0% the constraints are around like being 00:17:44.610 --> 00:17:46.250 align:start position:0% the constraints are around like being able<00:17:44.700> to<00:17:44.790> do<00:17:44.940> billions<00:17:45.630> of<00:17:45.750> transactions<00:17:46.230> per 00:17:46.250 --> 00:17:46.260 align:start position:0% able to do billions of transactions per 00:17:46.260 --> 00:17:46.960 align:start position:0% able to do billions of transactions per second 00:17:46.960 --> 00:17:46.970 align:start position:0% second 00:17:46.970 --> 00:17:50.090 align:start position:0% second handling<00:17:47.970> billions<00:17:48.420> of<00:17:48.480> users<00:17:49.010> millions<00:17:50.010> or 00:17:50.090 --> 00:17:50.100 align:start position:0% handling billions of users millions or 00:17:50.100 --> 00:17:51.410 align:start position:0% handling billions of users millions or hundreds<00:17:50.430> of<00:17:50.460> millions<00:17:50.550> of<00:17:50.910> simultaneous 00:17:51.410 --> 00:17:51.420 align:start position:0% hundreds of millions of simultaneous 00:17:51.420 --> 00:17:53.990 align:start position:0% hundreds of millions of simultaneous users<00:17:51.570> were<00:17:51.840> the<00:17:51.930> big<00:17:52.050> ones<00:17:52.190> sub<00:17:53.190> 100 00:17:53.990 --> 00:17:54.000 align:start position:0% users were the big ones sub 100 00:17:54.000 --> 00:17:55.790 align:start position:0% users were the big ones sub 100 millisecond<00:17:54.570> latency<00:17:54.750> like<00:17:55.470> from<00:17:55.680> the 00:17:55.790 --> 00:17:55.800 align:start position:0% millisecond latency like from the 00:17:55.800 --> 00:17:57.920 align:start position:0% millisecond latency like from the backbone<00:17:56.100> to<00:17:56.220> the<00:17:56.250> user<00:17:56.490> or<00:17:56.640> ideally<00:17:57.180> just 00:17:57.920 --> 00:17:57.930 align:start position:0% backbone to the user or ideally just 00:17:57.930 --> 00:18:00.200 align:start position:0% backbone to the user or ideally just from<00:17:58.050> the<00:17:58.170> user<00:17:58.350> to<00:17:58.470> the<00:17:58.560> application<00:17:59.210> and 00:18:00.200 --> 00:18:00.210 align:start position:0% from the user to the application and 00:18:00.210 --> 00:18:01.430 align:start position:0% from the user to the application and we're<00:18:00.390> talking<00:18:00.630> about<00:18:00.690> terabytes<00:18:01.200> petabytes 00:18:01.430 --> 00:18:01.440 align:start position:0% we're talking about terabytes petabytes 00:18:01.440 --> 00:18:03.860 align:start position:0% we're talking about terabytes petabytes and<00:18:01.830> exabytes<00:18:02.220> scale<00:18:02.490> so<00:18:02.730> terabyte<00:18:03.150> scales<00:18:03.600> if 00:18:03.860 --> 00:18:03.870 align:start position:0% and exabytes scale so terabyte scales if 00:18:03.870 --> 00:18:05.900 align:start position:0% and exabytes scale so terabyte scales if you're<00:18:04.020> a<00:18:04.050> small<00:18:04.320> company<00:18:04.610> exabytes<00:18:05.610> scales 00:18:05.900 --> 00:18:05.910 align:start position:0% you're a small company exabytes scales 00:18:05.910 --> 00:18:07.580 align:start position:0% you're a small company exabytes scales if<00:18:06.180> you're<00:18:06.330> you<00:18:06.720> know<00:18:06.810> basically<00:18:07.170> Facebook 00:18:07.580 --> 00:18:07.590 align:start position:0% if you're you know basically Facebook 00:18:07.590 --> 00:18:10.160 align:start position:0% if you're you know basically Facebook and<00:18:07.740> so<00:18:07.860> on<00:18:08.060> and<00:18:09.060> of<00:18:09.150> course<00:18:09.240> so<00:18:09.810> when<00:18:09.930> I<00:18:09.960> hear 00:18:10.160 --> 00:18:10.170 align:start position:0% and so on and of course so when I hear 00:18:10.170 --> 00:18:13.130 align:start position:0% and so on and of course so when I hear like<00:18:10.320> blotching<00:18:10.710> technology<00:18:11.250> right<00:18:12.030> like<00:18:12.210> how 00:18:13.130 --> 00:18:13.140 align:start position:0% like blotching technology right like how 00:18:13.140 --> 00:18:14.660 align:start position:0% like blotching technology right like how is<00:18:13.410> it<00:18:13.530> gonna<00:18:13.650> deal<00:18:13.890> with<00:18:13.920> this<00:18:14.220> right<00:18:14.520> like 00:18:14.660 --> 00:18:14.670 align:start position:0% is it gonna deal with this right like 00:18:14.670 --> 00:18:19.640 align:start position:0% is it gonna deal with this right like how<00:18:14.970> are<00:18:15.270> we<00:18:15.650> what<00:18:17.120> but<00:18:18.260> here's<00:18:19.260> the<00:18:19.500> magic 00:18:19.640 --> 00:18:19.650 align:start position:0% how are we what but here's the magic 00:18:19.650 --> 00:18:22.640 align:start position:0% how are we what but here's the magic right<00:18:20.220> but<00:18:21.060> but<00:18:21.450> here's<00:18:21.780> the<00:18:21.900> magic<00:18:22.020> right<00:18:22.500> so 00:18:22.640 --> 00:18:22.650 align:start position:0% right but but here's the magic right so 00:18:22.650 --> 00:18:24.280 align:start position:0% right but but here's the magic right so the<00:18:23.010> thing<00:18:23.130> is<00:18:23.340> that<00:18:23.520> it's<00:18:23.760> not<00:18:23.940> about 00:18:24.280 --> 00:18:24.290 align:start position:0% the thing is that it's not about 00:18:24.290 --> 00:18:27.320 align:start position:0% the thing is that it's not about matching<00:18:25.290> the<00:18:25.320> capabilities<00:18:26.040> today<00:18:26.330> it's 00:18:27.320 --> 00:18:27.330 align:start position:0% matching the capabilities today it's 00:18:27.330 --> 00:18:29.840 align:start position:0% matching the capabilities today it's about<00:18:28.340> proving<00:18:29.340> that<00:18:29.460> those<00:18:29.580> capabilities 00:18:29.840 --> 00:18:29.850 align:start position:0% about proving that those capabilities 00:18:29.850 --> 00:18:32.390 align:start position:0% about proving that those capabilities can<00:18:30.120> be<00:18:30.240> achieved<00:18:30.600> but<00:18:31.350> complementing<00:18:32.250> them 00:18:32.390 --> 00:18:32.400 align:start position:0% can be achieved but complementing them 00:18:32.400 --> 00:18:34.010 align:start position:0% can be achieved but complementing them with<00:18:32.550> a<00:18:32.610> whole<00:18:32.910> bunch<00:18:33.150> of<00:18:33.330> capabilities<00:18:33.930> that 00:18:34.010 --> 00:18:34.020 align:start position:0% with a whole bunch of capabilities that 00:18:34.020 --> 00:18:36.140 align:start position:0% with a whole bunch of capabilities that were<00:18:34.200> in<00:18:34.320> there<00:18:34.500> before<00:18:34.920> right<00:18:35.190> so<00:18:35.820> stuff<00:18:36.120> like 00:18:36.140 --> 00:18:36.150 align:start position:0% were in there before right so stuff like 00:18:36.150 --> 00:18:38.180 align:start position:0% were in there before right so stuff like like<00:18:36.840> the<00:18:37.140> idea<00:18:37.380> be<00:18:37.530> kind<00:18:37.710> of<00:18:37.800> blocking<00:18:38.100> is 00:18:38.180 --> 00:18:38.190 align:start position:0% like the idea be kind of blocking is 00:18:38.190 --> 00:18:39.590 align:start position:0% like the idea be kind of blocking is being<00:18:38.370> able<00:18:38.460> to<00:18:38.580> do<00:18:38.730> multi-party<00:18:39.360> computation 00:18:39.590 --> 00:18:39.600 align:start position:0% being able to do multi-party computation 00:18:39.600 --> 00:18:41.870 align:start position:0% being able to do multi-party computation but<00:18:40.200> it's<00:18:40.320> verifiable<00:18:40.890> and<00:18:41.070> trustless<00:18:41.430> you 00:18:41.870 --> 00:18:41.880 align:start position:0% but it's verifiable and trustless you 00:18:41.880 --> 00:18:43.430 align:start position:0% but it's verifiable and trustless you don't<00:18:42.030> get<00:18:42.120> that<00:18:42.240> at<00:18:42.420> all<00:18:42.510> today<00:18:42.690> and<00:18:42.810> web<00:18:43.050> 2.0 00:18:43.430 --> 00:18:43.440 align:start position:0% don't get that at all today and web 2.0 00:18:43.440 --> 00:18:45.350 align:start position:0% don't get that at all today and web 2.0 being<00:18:44.220> able<00:18:44.310> to<00:18:44.400> do<00:18:44.520> trustless 00:18:45.350 --> 00:18:45.360 align:start position:0% being able to do trustless 00:18:45.360 --> 00:18:47.300 align:start position:0% being able to do trustless trusses<00:18:46.290> Ledger's<00:18:46.620> like<00:18:46.920> being<00:18:47.130> able<00:18:47.190> to 00:18:47.300 --> 00:18:47.310 align:start position:0% trusses Ledger's like being able to 00:18:47.310 --> 00:18:48.620 align:start position:0% trusses Ledger's like being able to account<00:18:47.790> that<00:18:48.000> things<00:18:48.360> are<00:18:48.510> actually 00:18:48.620 --> 00:18:48.630 align:start position:0% account that things are actually 00:18:48.630 --> 00:18:50.720 align:start position:0% account that things are actually happening<00:18:48.960> time<00:18:49.470> stamping<00:18:49.890> being<00:18:50.550> able<00:18:50.610> to 00:18:50.720 --> 00:18:50.730 align:start position:0% happening time stamping being able to 00:18:50.730 --> 00:18:52.550 align:start position:0% happening time stamping being able to like<00:18:50.940> run<00:18:51.210> contracts<00:18:51.810> that<00:18:51.900> are<00:18:51.990> verifiable 00:18:52.550 --> 00:18:52.560 align:start position:0% like run contracts that are verifiable 00:18:52.560 --> 00:18:54.710 align:start position:0% like run contracts that are verifiable but<00:18:52.770> like<00:18:52.920> you<00:18:53.400> just<00:18:53.430> write<00:18:54.210> the<00:18:54.360> source<00:18:54.510> code 00:18:54.710 --> 00:18:54.720 align:start position:0% but like you just write the source code 00:18:54.720 --> 00:18:56.300 align:start position:0% but like you just write the source code out<00:18:54.840> there<00:18:55.020> put<00:18:55.230> it<00:18:55.320> up<00:18:55.440> there<00:18:55.680> and<00:18:55.830> it<00:18:56.160> just 00:18:56.300 --> 00:18:56.310 align:start position:0% out there put it up there and it just 00:18:56.310 --> 00:18:57.530 align:start position:0% out there put it up there and it just runs<00:18:56.430> on<00:18:56.580> its<00:18:56.760> own<00:18:56.910> and<00:18:57.120> you<00:18:57.150> don't<00:18:57.210> have<00:18:57.420> to 00:18:57.530 --> 00:18:57.540 align:start position:0% runs on its own and you don't have to 00:18:57.540 --> 00:18:58.850 align:start position:0% runs on its own and you don't have to like<00:18:57.630> maintain<00:18:57.960> it<00:18:58.080> and<00:18:58.170> nobody<00:18:58.410> has<00:18:58.440> to<00:18:58.590> do<00:18:58.680> it 00:18:58.850 --> 00:18:58.860 align:start position:0% like maintain it and nobody has to do it 00:18:58.860 --> 00:19:00.890 align:start position:0% like maintain it and nobody has to do it being<00:18:59.550> able<00:18:59.640> to<00:18:59.730> like<00:18:59.910> write<00:19:00.180> decentralized 00:19:00.890 --> 00:19:00.900 align:start position:0% being able to like write decentralized 00:19:00.900 --> 00:19:02.180 align:start position:0% being able to like write decentralized and<00:19:01.020> distributed<00:19:01.050> application<00:19:01.860> is<00:19:01.950> things 00:19:02.180 --> 00:19:02.190 align:start position:0% and distributed application is things 00:19:02.190 --> 00:19:04.130 align:start position:0% and distributed application is things where<00:19:02.490> you<00:19:02.970> write<00:19:03.150> them<00:19:03.300> once<00:19:03.510> you<00:19:03.720> sign<00:19:03.930> them 00:19:04.130 --> 00:19:04.140 align:start position:0% where you write them once you sign them 00:19:04.140 --> 00:19:05.810 align:start position:0% where you write them once you sign them drop<00:19:04.560> them<00:19:04.710> into<00:19:04.830> the<00:19:04.920> network<00:19:05.220> and<00:19:05.310> disappear 00:19:05.810 --> 00:19:05.820 align:start position:0% drop them into the network and disappear 00:19:05.820 --> 00:19:07.700 align:start position:0% drop them into the network and disappear and<00:19:05.970> the<00:19:06.420> people<00:19:06.720> can<00:19:06.900> carry<00:19:07.200> them<00:19:07.350> on<00:19:07.470> you 00:19:07.700 --> 00:19:07.710 align:start position:0% and the people can carry them on you 00:19:07.710 --> 00:19:08.990 align:start position:0% and the people can carry them on you could<00:19:07.860> disappear<00:19:08.070> as<00:19:08.310> an<00:19:08.400> organization<00:19:08.880> in<00:19:08.970> a 00:19:08.990 --> 00:19:09.000 align:start position:0% could disappear as an organization in a 00:19:09.000 --> 00:19:10.820 align:start position:0% could disappear as an organization in a company<00:19:09.330> and<00:19:09.480> people<00:19:10.140> could<00:19:10.260> continue<00:19:10.680> to<00:19:10.710> use 00:19:10.820 --> 00:19:10.830 align:start position:0% company and people could continue to use 00:19:10.830 --> 00:19:11.900 align:start position:0% company and people could continue to use this<00:19:10.980> application<00:19:11.130> it's<00:19:11.580> like<00:19:11.670> these<00:19:11.790> are 00:19:11.900 --> 00:19:11.910 align:start position:0% this application it's like these are 00:19:11.910 --> 00:19:13.820 align:start position:0% this application it's like these are real<00:19:12.120> capabilities<00:19:12.720> that<00:19:12.810> give<00:19:12.990> people<00:19:13.140> that 00:19:13.820 --> 00:19:13.830 align:start position:0% real capabilities that give people that 00:19:13.830 --> 00:19:15.710 align:start position:0% real capabilities that give people that you<00:19:14.130> cannot<00:19:14.340> take<00:19:14.550> away<00:19:14.580> and<00:19:15.510> that's 00:19:15.710 --> 00:19:15.720 align:start position:0% you cannot take away and that's 00:19:15.720 --> 00:19:17.120 align:start position:0% you cannot take away and that's extremely<00:19:15.990> interesting<00:19:16.560> that's<00:19:16.770> where<00:19:17.010> like 00:19:17.120 --> 00:19:17.130 align:start position:0% extremely interesting that's where like 00:19:17.130 --> 00:19:18.880 align:start position:0% extremely interesting that's where like there's<00:19:17.400> a<00:19:17.490> completely<00:19:18.120> unfair<00:19:18.480> advantage 00:19:18.880 --> 00:19:18.890 align:start position:0% there's a completely unfair advantage 00:19:18.890 --> 00:19:22.400 align:start position:0% there's a completely unfair advantage compared<00:19:19.890> to<00:19:19.920> the<00:19:20.070> web<00:19:20.190> web<00:19:20.610> 2.0<00:19:21.030> right<00:19:21.270> and<00:19:22.260> so 00:19:22.400 --> 00:19:22.410 align:start position:0% compared to the web web 2.0 right and so 00:19:22.410 --> 00:19:25.010 align:start position:0% compared to the web web 2.0 right and so we're<00:19:22.530> talking<00:19:22.650> about<00:19:22.830> building<00:19:23.840> taking<00:19:24.840> data 00:19:25.010 --> 00:19:25.020 align:start position:0% we're talking about building taking data 00:19:25.020 --> 00:19:27.620 align:start position:0% we're talking about building taking data and<00:19:25.170> code<00:19:25.680> and<00:19:25.920> execution<00:19:26.520> in<00:19:26.760> a<00:19:27.210> completely 00:19:27.620 --> 00:19:27.630 align:start position:0% and code and execution in a completely 00:19:27.630 --> 00:19:30.080 align:start position:0% and code and execution in a completely different<00:19:27.840> verifiable<00:19:28.620> model 00:19:30.080 --> 00:19:30.090 align:start position:0% different verifiable model 00:19:30.090 --> 00:19:32.330 align:start position:0% different verifiable model and<00:19:30.330> of<00:19:30.750> course<00:19:30.990> being<00:19:31.590> able<00:19:31.710> to<00:19:31.860> secure<00:19:32.250> an 00:19:32.330 --> 00:19:32.340 align:start position:0% and of course being able to secure an 00:19:32.340 --> 00:19:33.830 align:start position:0% and of course being able to secure an encryption<00:19:32.580> in<00:19:32.850> a<00:19:32.910> way<00:19:33.090> that<00:19:33.270> the<00:19:33.330> web<00:19:33.420> 2.0 00:19:33.830 --> 00:19:33.840 align:start position:0% encryption in a way that the web 2.0 00:19:33.840 --> 00:19:38.420 align:start position:0% encryption in a way that the web 2.0 people<00:19:34.800> can't<00:19:35.210> because<00:19:36.210> a<00:19:36.890> lot<00:19:37.890> of<00:19:37.980> web<00:19:38.070> 2.0 00:19:38.420 --> 00:19:38.430 align:start position:0% people can't because a lot of web 2.0 00:19:38.430 --> 00:19:40.010 align:start position:0% people can't because a lot of web 2.0 relies<00:19:38.700> in<00:19:38.730> advertising<00:19:39.240> and<00:19:39.450> so<00:19:39.600> on<00:19:39.750> which 00:19:40.010 --> 00:19:40.020 align:start position:0% relies in advertising and so on which 00:19:40.020 --> 00:19:41.390 align:start position:0% relies in advertising and so on which means<00:19:40.170> that<00:19:40.410> they<00:19:40.500> can't<00:19:40.710> really<00:19:40.980> do<00:19:41.130> end<00:19:41.310> to 00:19:41.390 --> 00:19:41.400 align:start position:0% means that they can't really do end to 00:19:41.400 --> 00:19:44.120 align:start position:0% means that they can't really do end to end<00:19:41.520> encryption<00:19:42.290> so<00:19:43.290> that's<00:19:43.530> a<00:19:43.710> huge 00:19:44.120 --> 00:19:44.130 align:start position:0% end encryption so that's a huge 00:19:44.130 --> 00:19:46.070 align:start position:0% end encryption so that's a huge advantage<00:19:44.790> right<00:19:45.240> because<00:19:45.540> we<00:19:45.690> don't<00:19:45.870> have<00:19:45.990> to 00:19:46.070 --> 00:19:46.080 align:start position:0% advantage right because we don't have to 00:19:46.080 --> 00:19:48.290 align:start position:0% advantage right because we don't have to deal<00:19:46.200> with<00:19:46.260> that<00:19:46.500> we<00:19:46.950> can<00:19:47.130> just<00:19:47.310> do<00:19:47.760> end<00:19:48.060> to<00:19:48.210> an 00:19:48.290 --> 00:19:48.300 align:start position:0% deal with that we can just do end to an 00:19:48.300 --> 00:19:49.280 align:start position:0% deal with that we can just do end to an encryption<00:19:48.540> for<00:19:48.780> users 00:19:49.280 --> 00:19:49.290 align:start position:0% encryption for users 00:19:49.290 --> 00:19:53.450 align:start position:0% encryption for users we<00:19:49.620> don't<00:19:49.770> need<00:19:49.890> users<00:19:50.280> data<00:19:50.610> at<00:19:50.760> all<00:19:51.140> and<00:19:52.460> this 00:19:53.450 --> 00:19:53.460 align:start position:0% we don't need users data at all and this 00:19:53.460 --> 00:19:55.220 align:start position:0% we don't need users data at all and this is<00:19:53.670> a<00:19:53.820> strong<00:19:54.450> reason<00:19:54.630> to<00:19:54.840> be<00:19:54.900> able<00:19:55.050> to<00:19:55.110> move 00:19:55.220 --> 00:19:55.230 align:start position:0% is a strong reason to be able to move 00:19:55.230 --> 00:19:58.370 align:start position:0% is a strong reason to be able to move move<00:19:55.560> in<00:19:55.650> this<00:19:55.740> direction<00:19:56.420> cool<00:19:57.450> let<00:19:57.690> me<00:19:57.750> check 00:19:58.370 --> 00:19:58.380 align:start position:0% move in this direction cool let me check 00:19:58.380 --> 00:20:02.210 align:start position:0% move in this direction cool let me check timing<00:19:58.740> because<00:20:00.260> sweet<00:20:01.260> so<00:20:01.830> that<00:20:01.860> was<00:20:02.130> like 00:20:02.210 --> 00:20:02.220 align:start position:0% timing because sweet so that was like 00:20:02.220 --> 00:20:03.980 align:start position:0% timing because sweet so that was like the<00:20:02.370> interlude<00:20:02.820> so<00:20:03.300> what<00:20:03.600> people<00:20:03.810> know<00:20:03.870> is 00:20:03.980 --> 00:20:03.990 align:start position:0% the interlude so what people know is 00:20:03.990 --> 00:20:05.270 align:start position:0% the interlude so what people know is kind<00:20:04.260> of<00:20:04.320> about<00:20:04.530> having<00:20:04.830> these<00:20:04.950> like 00:20:05.270 --> 00:20:05.280 align:start position:0% kind of about having these like 00:20:05.280 --> 00:20:07.400 align:start position:0% kind of about having these like databases<00:20:06.210> talking<00:20:06.750> to<00:20:06.840> each<00:20:06.930> other<00:20:07.110> with 00:20:07.400 --> 00:20:07.410 align:start position:0% databases talking to each other with 00:20:07.410 --> 00:20:10.310 align:start position:0% databases talking to each other with data<00:20:07.650> behind<00:20:08.040> the<00:20:08.130> scenes<00:20:08.370> and<00:20:08.790> what<00:20:09.390> web<00:20:09.870> 2.0 00:20:10.310 --> 00:20:10.320 align:start position:0% data behind the scenes and what web 2.0 00:20:10.320 --> 00:20:12.740 align:start position:0% data behind the scenes and what web 2.0 is<00:20:10.500> about<00:20:10.710> taking<00:20:11.040> the<00:20:11.580> the<00:20:11.850> logic<00:20:12.360> and<00:20:12.600> the 00:20:12.740 --> 00:20:12.750 align:start position:0% is about taking the the logic and the 00:20:12.750 --> 00:20:15.050 align:start position:0% is about taking the the logic and the data<00:20:12.960> itself<00:20:13.440> and<00:20:13.680> putting<00:20:14.220> those<00:20:14.490> into<00:20:14.880> the 00:20:15.050 --> 00:20:15.060 align:start position:0% data itself and putting those into the 00:20:15.060 --> 00:20:16.310 align:start position:0% data itself and putting those into the network<00:20:15.390> and<00:20:15.600> allowing<00:20:16.050> those<00:20:16.170> to 00:20:16.310 --> 00:20:16.320 align:start position:0% network and allowing those to 00:20:16.320 --> 00:20:18.650 align:start position:0% network and allowing those to communicate<00:20:16.800> and<00:20:17.010> making<00:20:17.670> the<00:20:17.850> axle<00:20:18.300> hardware 00:20:18.650 --> 00:20:18.660 align:start position:0% communicate and making the axle hardware 00:20:18.660 --> 00:20:22.550 align:start position:0% communicate and making the axle hardware secondary<00:20:20.870> alright<00:20:21.870> that<00:20:22.140> was<00:20:22.230> the<00:20:22.350> intern 00:20:22.550 --> 00:20:22.560 align:start position:0% secondary alright that was the intern 00:20:22.560 --> 00:20:24.560 align:start position:0% secondary alright that was the intern okay<00:20:22.800> okay<00:20:23.460> have<00:20:24.030> to<00:20:24.180> rush<00:20:24.330> through<00:20:24.480> this 00:20:24.560 --> 00:20:24.570 align:start position:0% okay okay have to rush through this 00:20:24.570 --> 00:20:25.070 align:start position:0% okay okay have to rush through this stuff 00:20:25.070 --> 00:20:25.080 align:start position:0% stuff 00:20:25.080 --> 00:20:27.260 align:start position:0% stuff five<00:20:26.010> minutes<00:20:26.250> but<00:20:26.460> we'll<00:20:26.670> see<00:20:26.790> alright<00:20:26.940> so<00:20:27.120> I 00:20:27.260 --> 00:20:27.270 align:start position:0% five minutes but we'll see alright so I 00:20:27.270 --> 00:20:29.690 align:start position:0% five minutes but we'll see alright so I feel<00:20:27.450> D<00:20:27.680> that<00:20:28.680> this<00:20:28.860> is<00:20:28.950> the<00:20:29.010> heart<00:20:29.190> of<00:20:29.220> ipfs 00:20:29.690 --> 00:20:29.700 align:start position:0% feel D that this is the heart of ipfs 00:20:29.700 --> 00:20:33.100 align:start position:0% feel D that this is the heart of ipfs it's<00:20:30.030> a<00:20:30.210> common<00:20:30.570> format<00:20:31.260> for<00:20:31.320> hash<00:20:32.040> chain<00:20:32.070> or 00:20:33.100 --> 00:20:33.110 align:start position:0% it's a common format for hash chain or 00:20:33.110 --> 00:20:34.970 align:start position:0% it's a common format for hash chain or distribute<00:20:34.110> data<00:20:34.200> structures<00:20:34.590> based<00:20:34.800> on 00:20:34.970 --> 00:20:34.980 align:start position:0% distribute data structures based on 00:20:34.980 --> 00:20:37.340 align:start position:0% distribute data structures based on Merkle<00:20:35.340> trees<00:20:35.690> and<00:20:36.690> so<00:20:36.810> what<00:20:36.990> I<00:20:37.020> showed<00:20:37.200> before 00:20:37.340 --> 00:20:37.350 align:start position:0% Merkle trees and so what I showed before 00:20:37.350 --> 00:20:38.990 align:start position:0% Merkle trees and so what I showed before with<00:20:37.530> these<00:20:37.770> files<00:20:37.980> these<00:20:38.280> aren't<00:20:38.490> actually 00:20:38.990 --> 00:20:39.000 align:start position:0% with these files these aren't actually 00:20:39.000 --> 00:20:41.270 align:start position:0% with these files these aren't actually files<00:20:39.270> they<00:20:39.690> are<00:20:39.770> so<00:20:40.770> when<00:20:40.890> you<00:20:40.950> add<00:20:41.070> something 00:20:41.270 --> 00:20:41.280 align:start position:0% files they are so when you add something 00:20:41.280 --> 00:20:42.290 align:start position:0% files they are so when you add something to<00:20:41.430> a<00:20:41.460> professor<00:20:41.760> it<00:20:41.880> kind<00:20:42.030> of<00:20:42.060> looks<00:20:42.210> like 00:20:42.290 --> 00:20:42.300 align:start position:0% to a professor it kind of looks like 00:20:42.300 --> 00:20:44.270 align:start position:0% to a professor it kind of looks like this<00:20:42.480> you<00:20:42.690> your<00:20:42.960> add<00:20:43.140> all<00:20:43.290> this<00:20:43.410> stuff<00:20:43.710> well 00:20:44.270 --> 00:20:44.280 align:start position:0% this you your add all this stuff well 00:20:44.280 --> 00:20:45.560 align:start position:0% this you your add all this stuff well these<00:20:44.370> aren't<00:20:44.580> files<00:20:44.880> these<00:20:45.090> are<00:20:45.240> actually 00:20:45.560 --> 00:20:45.570 align:start position:0% these aren't files these are actually 00:20:45.570 --> 00:20:48.710 align:start position:0% these aren't files these are actually nodes<00:20:46.050> in<00:20:46.350> a<00:20:46.440> graph<00:20:46.490> and<00:20:47.490> these<00:20:48.180> nodes<00:20:48.480> in<00:20:48.630> a 00:20:48.710 --> 00:20:48.720 align:start position:0% nodes in a graph and these nodes in a 00:20:48.720 --> 00:20:52.580 align:start position:0% nodes in a graph and these nodes in a graph<00:20:49.370> there<00:20:50.630> there<00:20:51.630> is<00:20:51.780> stored<00:20:52.170> in<00:20:52.290> that<00:20:52.320> in<00:20:52.500> a 00:20:52.580 --> 00:20:52.590 align:start position:0% graph there there is stored in that in a 00:20:52.590 --> 00:20:54.980 align:start position:0% graph there there is stored in that in a format<00:20:52.890> that<00:20:52.950> we<00:20:53.130> are<00:20:53.220> calling<00:20:53.400> IPL<00:20:53.820> D<00:20:53.970> that<00:20:54.900> is 00:20:54.980 --> 00:20:54.990 align:start position:0% format that we are calling IPL D that is 00:20:54.990 --> 00:20:57.740 align:start position:0% format that we are calling IPL D that is basically<00:20:55.500> like<00:20:56.090> something<00:20:57.090> like<00:20:57.240> JSON<00:20:57.570> it's 00:20:57.740 --> 00:20:57.750 align:start position:0% basically like something like JSON it's 00:20:57.750 --> 00:20:59.240 align:start position:0% basically like something like JSON it's not<00:20:57.840> exactly<00:20:58.080> JSON<00:20:58.470> because<00:20:58.620> it's<00:20:58.920> it's 00:20:59.240 --> 00:20:59.250 align:start position:0% not exactly JSON because it's it's 00:20:59.250 --> 00:21:03.110 align:start position:0% not exactly JSON because it's it's serialize<00:20:59.610> to<00:20:59.700> be<00:20:59.790> fast<00:21:01.190> but<00:21:02.190> it's<00:21:02.370> it's<00:21:02.700> the 00:21:03.110 --> 00:21:03.120 align:start position:0% serialize to be fast but it's it's the 00:21:03.120 --> 00:21:04.100 align:start position:0% serialize to be fast but it's it's the whole<00:21:03.300> point<00:21:03.480> that<00:21:03.540> you<00:21:03.720> have<00:21:03.840> a<00:21:03.870> very 00:21:04.100 --> 00:21:04.110 align:start position:0% whole point that you have a very 00:21:04.110 --> 00:21:05.870 align:start position:0% whole point that you have a very flexible<00:21:04.380> data<00:21:04.800> model<00:21:05.160> so<00:21:05.520> you<00:21:05.550> can<00:21:05.640> take 00:21:05.870 --> 00:21:05.880 align:start position:0% flexible data model so you can take 00:21:05.880 --> 00:21:08.690 align:start position:0% flexible data model so you can take entire<00:21:06.240> api's<00:21:06.750> of<00:21:06.990> today<00:21:07.230> and<00:21:07.500> just<00:21:07.890> dump<00:21:08.550> them 00:21:08.690 --> 00:21:08.700 align:start position:0% entire api's of today and just dump them 00:21:08.700 --> 00:21:11.450 align:start position:0% entire api's of today and just dump them straight<00:21:09.000> into<00:21:09.120> ipfs<00:21:09.510> so<00:21:09.600> you<00:21:09.660> can<00:21:09.750> take<00:21:10.460> some 00:21:11.450 --> 00:21:11.460 align:start position:0% straight into ipfs so you can take some 00:21:11.460 --> 00:21:14.330 align:start position:0% straight into ipfs so you can take some data<00:21:12.210> API<00:21:12.690> that<00:21:12.870> you<00:21:12.960> have<00:21:13.140> and<00:21:13.500> just<00:21:13.740> straight 00:21:14.330 --> 00:21:14.340 align:start position:0% data API that you have and just straight 00:21:14.340 --> 00:21:15.800 align:start position:0% data API that you have and just straight up<00:21:14.370> import<00:21:14.880> all<00:21:15.030> of<00:21:15.150> that<00:21:15.270> into<00:21:15.450> our<00:21:15.480> BFS<00:21:15.780> and 00:21:15.800 --> 00:21:15.810 align:start position:0% up import all of that into our BFS and 00:21:15.810 --> 00:21:18.230 align:start position:0% up import all of that into our BFS and like<00:21:16.080> merkel<00:21:16.380> is<00:21:16.440> the<00:21:16.590> whole<00:21:16.740> thing<00:21:17.000> that<00:21:18.000> it's 00:21:18.230 --> 00:21:18.240 align:start position:0% like merkel is the whole thing that it's 00:21:18.240 --> 00:21:19.400 align:start position:0% like merkel is the whole thing that it's not<00:21:18.360> perfect<00:21:18.750> and<00:21:18.840> you<00:21:18.930> have<00:21:19.110> to<00:21:19.170> like<00:21:19.260> work 00:21:19.400 --> 00:21:19.410 align:start position:0% not perfect and you have to like work 00:21:19.410 --> 00:21:21.050 align:start position:0% not perfect and you have to like work hard<00:21:19.620> to<00:21:19.710> make<00:21:19.830> it<00:21:19.860> really<00:21:20.460> a<00:21:20.490> good<00:21:20.670> distribute 00:21:21.050 --> 00:21:21.060 align:start position:0% hard to make it really a good distribute 00:21:21.060 --> 00:21:22.730 align:start position:0% hard to make it really a good distribute application<00:21:21.480> but<00:21:22.020> that's<00:21:22.140> kind<00:21:22.380> of<00:21:22.410> like<00:21:22.500> step 00:21:22.730 --> 00:21:22.740 align:start position:0% application but that's kind of like step 00:21:22.740 --> 00:21:23.120 align:start position:0% application but that's kind of like step one 00:21:23.120 --> 00:21:23.130 align:start position:0% one 00:21:23.130 --> 00:21:26.030 align:start position:0% one and<00:21:23.490> so<00:21:24.390> we<00:21:24.510> see<00:21:24.810> us<00:21:24.900> as<00:21:25.050> new<00:21:25.320> thin<00:21:25.560> way<00:21:25.740> so<00:21:25.800> the 00:21:26.030 --> 00:21:26.040 align:start position:0% and so we see us as new thin way so the 00:21:26.040 --> 00:21:27.490 align:start position:0% and so we see us as new thin way so the internet<00:21:26.310> the<00:21:26.640> internet<00:21:26.670> of<00:21:26.940> data<00:21:27.090> structures 00:21:27.490 --> 00:21:27.500 align:start position:0% internet the internet of data structures 00:21:27.500 --> 00:21:30.380 align:start position:0% internet the internet of data structures and<00:21:28.500> it<00:21:29.280> gives<00:21:29.490> you<00:21:29.640> like<00:21:29.790> Merkel<00:21:30.090> links<00:21:30.300> that 00:21:30.380 --> 00:21:30.390 align:start position:0% and it gives you like Merkel links that 00:21:30.390 --> 00:21:31.550 align:start position:0% and it gives you like Merkel links that are<00:21:30.480> secure<00:21:30.720> and<00:21:30.750> immutable<00:21:30.990> it<00:21:31.320> gives<00:21:31.470> you 00:21:31.550 --> 00:21:31.560 align:start position:0% are secure and immutable it gives you 00:21:31.560 --> 00:21:33.620 align:start position:0% are secure and immutable it gives you merkel<00:21:31.860> paths<00:21:32.610> meaning<00:21:33.150> you<00:21:33.240> can<00:21:33.390> resolve 00:21:33.620 --> 00:21:33.630 align:start position:0% merkel paths meaning you can resolve 00:21:33.630 --> 00:21:35.300 align:start position:0% merkel paths meaning you can resolve through<00:21:33.870> the<00:21:33.990> through<00:21:34.260> the<00:21:34.380> graph 00:21:35.300 --> 00:21:35.310 align:start position:0% through the through the graph 00:21:35.310 --> 00:21:37.299 align:start position:0% through the through the graph they're<00:21:35.640> sort<00:21:35.820> of<00:21:35.880> universal<00:21:36.390> and<00:21:36.540> there 00:21:37.299 --> 00:21:37.309 align:start position:0% they're sort of universal and there 00:21:37.309 --> 00:21:39.600 align:start position:0% they're sort of universal and there kind<00:21:37.700> of<00:21:37.789> your<00:21:38.000> URLs<00:21:38.630> as<00:21:38.840> we<00:21:39.020> said<00:21:39.409> before 00:21:39.600 --> 00:21:39.610 align:start position:0% kind of your URLs as we said before 00:21:39.610 --> 00:21:42.039 align:start position:0% kind of your URLs as we said before though<00:21:40.610> it's<00:21:40.789> not<00:21:40.880> location-based<00:21:41.450> right<00:21:41.900> so 00:21:42.039 --> 00:21:42.049 align:start position:0% though it's not location-based right so 00:21:42.049 --> 00:21:44.230 align:start position:0% though it's not location-based right so like<00:21:42.169> it<00:21:42.289> doesn't<00:21:42.590> it<00:21:42.950> I<00:21:43.190> mentioned<00:21:43.820> here<00:21:43.940> URL 00:21:44.230 --> 00:21:44.240 align:start position:0% like it doesn't it I mentioned here URL 00:21:44.240 --> 00:21:45.159 align:start position:0% like it doesn't it I mentioned here URL because<00:21:44.480> most<00:21:44.630> people<00:21:44.809> are<00:21:44.870> familiar<00:21:44.960> with 00:21:45.159 --> 00:21:45.169 align:start position:0% because most people are familiar with 00:21:45.169 --> 00:21:46.299 align:start position:0% because most people are familiar with that<00:21:45.320> term<00:21:45.590> but<00:21:45.799> it's<00:21:45.919> not<00:21:46.039> actually 00:21:46.299 --> 00:21:46.309 align:start position:0% that term but it's not actually 00:21:46.309 --> 00:21:48.310 align:start position:0% that term but it's not actually location-based<00:21:46.720> and<00:21:47.720> in<00:21:48.020> terms<00:21:48.169> of 00:21:48.310 --> 00:21:48.320 align:start position:0% location-based and in terms of 00:21:48.320 --> 00:21:49.690 align:start position:0% location-based and in terms of serialization<00:21:48.919> you<00:21:49.070> can<00:21:49.220> do<00:21:49.309> anything<00:21:49.520> you 00:21:49.690 --> 00:21:49.700 align:start position:0% serialization you can do anything you 00:21:49.700 --> 00:21:53.799 align:start position:0% serialization you can do anything you want<00:21:49.850> you<00:21:49.940> can<00:21:50.059> use<00:21:50.090> JSON<00:21:50.419> protocol<00:21:51.230> XML<00:21:52.809> RLP 00:21:53.799 --> 00:21:53.809 align:start position:0% want you can use JSON protocol XML RLP 00:21:53.809 --> 00:21:55.260 align:start position:0% want you can use JSON protocol XML RLP or<00:21:53.990> whatever<00:21:54.260> whatever<00:21:54.620> it<00:21:54.830> is<00:21:54.919> that<00:21:55.039> you<00:21:55.130> use 00:21:55.260 --> 00:21:55.270 align:start position:0% or whatever whatever it is that you use 00:21:55.270 --> 00:21:57.399 align:start position:0% or whatever whatever it is that you use you<00:21:56.270> can<00:21:56.390> use<00:21:56.510> a<00:21:56.539> serialization<00:21:56.929> format 00:21:57.399 --> 00:21:57.409 align:start position:0% you can use a serialization format 00:21:57.409 --> 00:21:59.860 align:start position:0% you can use a serialization format underneath<00:21:57.860> the<00:21:58.010> hood<00:21:58.330> there<00:21:59.330> is<00:21:59.450> a<00:21:59.480> canonical 00:21:59.860 --> 00:21:59.870 align:start position:0% underneath the hood there is a canonical 00:21:59.870 --> 00:22:02.080 align:start position:0% underneath the hood there is a canonical way<00:22:00.350> of<00:22:00.559> describing<00:22:00.890> which<00:22:01.250> serialization 00:22:02.080 --> 00:22:02.090 align:start position:0% way of describing which serialization 00:22:02.090 --> 00:22:03.700 align:start position:0% way of describing which serialization thing<00:22:02.210> to<00:22:02.299> use<00:22:02.480> so<00:22:02.929> that<00:22:03.049> everyone<00:22:03.350> has<00:22:03.470> it's 00:22:03.700 --> 00:22:03.710 align:start position:0% thing to use so that everyone has it's 00:22:03.710 --> 00:22:06.399 align:start position:0% thing to use so that everyone has it's the<00:22:03.799> same<00:22:03.980> thing<00:22:04.130> and<00:22:04.690> so<00:22:05.690> if<00:22:06.110> you<00:22:06.260> had 00:22:06.399 --> 00:22:06.409 align:start position:0% the same thing and so if you had 00:22:06.409 --> 00:22:07.779 align:start position:0% the same thing and so if you had something<00:22:06.650> like<00:22:06.770> this<00:22:06.980> in<00:22:07.159> case<00:22:07.280> on<00:22:07.490> where<00:22:07.640> you 00:22:07.779 --> 00:22:07.789 align:start position:0% something like this in case on where you 00:22:07.789 --> 00:22:09.760 align:start position:0% something like this in case on where you were<00:22:07.940> you<00:22:08.390> know<00:22:08.480> you<00:22:08.539> outlined<00:22:09.289> the<00:22:09.409> followers 00:22:09.760 --> 00:22:09.770 align:start position:0% were you know you outlined the followers 00:22:09.770 --> 00:22:13.270 align:start position:0% were you know you outlined the followers of<00:22:09.860> a<00:22:09.950> user<00:22:10.659> this<00:22:11.659> way<00:22:11.900> this<00:22:12.830> is<00:22:12.950> kind<00:22:13.070> of<00:22:13.100> like 00:22:13.270 --> 00:22:13.280 align:start position:0% of a user this way this is kind of like 00:22:13.280 --> 00:22:15.700 align:start position:0% of a user this way this is kind of like mush<00:22:13.549> right<00:22:13.820> look<00:22:13.970> what<00:22:14.390> is<00:22:14.539> at<00:22:14.750> Vannevar<00:22:15.559> bush 00:22:15.700 --> 00:22:15.710 align:start position:0% mush right look what is at Vannevar bush 00:22:15.710 --> 00:22:18.430 align:start position:0% mush right look what is at Vannevar bush mean<00:22:16.100> right<00:22:16.880> could<00:22:17.179> some<00:22:17.360> user<00:22:17.600> somewhere<00:22:18.230> but 00:22:18.430 --> 00:22:18.440 align:start position:0% mean right could some user somewhere but 00:22:18.440 --> 00:22:20.560 align:start position:0% mean right could some user somewhere but like<00:22:18.559> you<00:22:18.679> don't<00:22:19.220> know<00:22:19.490> what<00:22:19.820> context<00:22:20.419> that 00:22:20.560 --> 00:22:20.570 align:start position:0% like you don't know what context that 00:22:20.570 --> 00:22:22.419 align:start position:0% like you don't know what context that that<00:22:20.870> comes<00:22:21.049> from<00:22:21.200> right<00:22:21.440> you<00:22:22.070> have<00:22:22.220> to<00:22:22.309> know 00:22:22.419 --> 00:22:22.429 align:start position:0% that comes from right you have to know 00:22:22.429 --> 00:22:23.560 align:start position:0% that comes from right you have to know that<00:22:22.460> this<00:22:22.610> would<00:22:22.820> be<00:22:22.940> Twitter<00:22:23.179> or<00:22:23.330> something 00:22:23.560 --> 00:22:23.570 align:start position:0% that this would be Twitter or something 00:22:23.570 --> 00:22:25.539 align:start position:0% that this would be Twitter or something else<00:22:23.720> just<00:22:23.960> from<00:22:24.530> the<00:22:24.860> endpoint<00:22:25.159> that<00:22:25.429> you're 00:22:25.539 --> 00:22:25.549 align:start position:0% else just from the endpoint that you're 00:22:25.549 --> 00:22:27.669 align:start position:0% else just from the endpoint that you're accessing<00:22:25.820> this<00:22:26.150> from<00:22:26.510> but<00:22:27.260> what<00:22:27.470> if<00:22:27.559> these 00:22:27.669 --> 00:22:27.679 align:start position:0% accessing this from but what if these 00:22:27.679 --> 00:22:30.220 align:start position:0% accessing this from but what if these actually<00:22:28.370> link<00:22:28.640> to<00:22:28.730> content<00:22:29.510> address<00:22:29.840> things 00:22:30.220 --> 00:22:30.230 align:start position:0% actually link to content address things 00:22:30.230 --> 00:22:32.560 align:start position:0% actually link to content address things right<00:22:30.710> like<00:22:30.740> the<00:22:31.100> resources<00:22:31.909> were<00:22:32.030> actually 00:22:32.560 --> 00:22:32.570 align:start position:0% right like the resources were actually 00:22:32.570 --> 00:22:34.990 align:start position:0% right like the resources were actually based<00:22:32.840> on<00:22:33.080> hashes<00:22:33.590> then<00:22:34.280> you<00:22:34.669> don't<00:22:34.820> have<00:22:34.909> to 00:22:34.990 --> 00:22:35.000 align:start position:0% based on hashes then you don't have to 00:22:35.000 --> 00:22:36.880 align:start position:0% based on hashes then you don't have to know<00:22:35.480> anything<00:22:35.720> about<00:22:36.020> the<00:22:36.380> way<00:22:36.710> you're 00:22:36.880 --> 00:22:36.890 align:start position:0% know anything about the way you're 00:22:36.890 --> 00:22:38.890 align:start position:0% know anything about the way you're accessing<00:22:37.159> at<00:22:37.429> all<00:22:37.520> because<00:22:38.390> the<00:22:38.539> content 00:22:38.890 --> 00:22:38.900 align:start position:0% accessing at all because the content 00:22:38.900 --> 00:22:40.899 align:start position:0% accessing at all because the content itself<00:22:39.169> or<00:22:39.440> like<00:22:39.559> tells<00:22:40.130> you<00:22:40.340> what<00:22:40.640> it's<00:22:40.789> about 00:22:40.899 --> 00:22:40.909 align:start position:0% itself or like tells you what it's about 00:22:40.909 --> 00:22:44.830 align:start position:0% itself or like tells you what it's about right<00:22:42.250> and<00:22:43.250> it<00:22:44.000> would<00:22:44.210> I<00:22:44.240> feel<00:22:44.480> that<00:22:44.630> you<00:22:44.720> can 00:22:44.830 --> 00:22:44.840 align:start position:0% right and it would I feel that you can 00:22:44.840 --> 00:22:46.630 align:start position:0% right and it would I feel that you can do<00:22:44.929> llamó<00:22:45.200> you<00:22:45.320> can<00:22:45.440> do<00:22:45.500> whatever<00:22:45.740> format<00:22:46.580> you 00:22:46.630 --> 00:22:46.640 align:start position:0% do llamó you can do whatever format you 00:22:46.640 --> 00:22:49.840 align:start position:0% do llamó you can do whatever format you want<00:22:46.909> and<00:22:47.120> so<00:22:47.240> on<00:22:47.390> so<00:22:48.230> the<00:22:48.679> point<00:22:49.520> here<00:22:49.580> is<00:22:49.730> to 00:22:49.840 --> 00:22:49.850 align:start position:0% want and so on so the point here is to 00:22:49.850 --> 00:22:52.860 align:start position:0% want and so on so the point here is to build<00:22:50.030> something<00:22:50.270> as<00:22:50.600> easy<00:22:50.990> to<00:22:51.169> use<00:22:51.500> as<00:22:51.679> JSON 00:22:52.860 --> 00:22:52.870 align:start position:0% build something as easy to use as JSON 00:22:52.870 --> 00:22:56.320 align:start position:0% build something as easy to use as JSON but<00:22:53.870> when<00:22:54.530> you<00:22:54.830> merkel<00:22:55.340> eyes<00:22:55.460> it<00:22:55.669> and<00:22:55.880> you<00:22:55.970> turn 00:22:56.320 --> 00:22:56.330 align:start position:0% but when you merkel eyes it and you turn 00:22:56.330 --> 00:22:58.510 align:start position:0% but when you merkel eyes it and you turn these<00:22:56.510> normal<00:22:57.200> graphs<00:22:57.980> you<00:22:58.130> you<00:22:58.309> should<00:22:58.490> be 00:22:58.510 --> 00:22:58.520 align:start position:0% these normal graphs you you should be 00:22:58.520 --> 00:23:02.529 align:start position:0% these normal graphs you you should be able<00:22:58.640> to<00:23:00.520> have<00:23:01.520> the<00:23:01.610> exact<00:23:01.880> same<00:23:01.909> architecture 00:23:02.529 --> 00:23:02.539 align:start position:0% able to have the exact same architecture 00:23:02.539 --> 00:23:05.110 align:start position:0% able to have the exact same architecture of<00:23:02.780> your<00:23:02.960> data<00:23:03.169> but<00:23:03.890> where<00:23:04.370> before<00:23:04.730> you<00:23:05.000> would 00:23:05.110 --> 00:23:05.120 align:start position:0% of your data but where before you would 00:23:05.120 --> 00:23:06.430 align:start position:0% of your data but where before you would just<00:23:05.240> have<00:23:05.360> some<00:23:05.570> strings<00:23:06.049> that<00:23:06.200> you<00:23:06.260> then 00:23:06.430 --> 00:23:06.440 align:start position:0% just have some strings that you then 00:23:06.440 --> 00:23:08.380 align:start position:0% just have some strings that you then would<00:23:06.710> have<00:23:06.830> to<00:23:06.950> look<00:23:07.130> up<00:23:07.309> in<00:23:07.400> a<00:23:07.460> database<00:23:07.730> here 00:23:08.380 --> 00:23:08.390 align:start position:0% would have to look up in a database here 00:23:08.390 --> 00:23:12.010 align:start position:0% would have to look up in a database here you<00:23:08.510> have<00:23:08.659> hash<00:23:08.929> lengths<00:23:10.299> and<00:23:11.299> so<00:23:11.450> you<00:23:11.840> can 00:23:12.010 --> 00:23:12.020 align:start position:0% you have hash lengths and so you can 00:23:12.020 --> 00:23:14.560 align:start position:0% you have hash lengths and so you can follow<00:23:12.919> you<00:23:13.280> can<00:23:13.610> resolve<00:23:14.090> through<00:23:14.330> the<00:23:14.419> hash 00:23:14.560 --> 00:23:14.570 align:start position:0% follow you can resolve through the hash 00:23:14.570 --> 00:23:17.230 align:start position:0% follow you can resolve through the hash line<00:23:14.809> so<00:23:14.960> here<00:23:15.590> in<00:23:15.799> the<00:23:15.950> second<00:23:16.250> layer<00:23:16.789> i<00:23:16.820> have 00:23:17.230 --> 00:23:17.240 align:start position:0% line so here in the second layer i have 00:23:17.240 --> 00:23:18.940 align:start position:0% line so here in the second layer i have your<00:23:17.990> going<00:23:18.140> through<00:23:18.260> the<00:23:18.350> hash<00:23:18.590> and<00:23:18.860> then 00:23:18.940 --> 00:23:18.950 align:start position:0% your going through the hash and then 00:23:18.950 --> 00:23:20.350 align:start position:0% your going through the hash and then slash<00:23:19.280> followers<00:23:19.789> meaning<00:23:20.120> that<00:23:20.210> you're 00:23:20.350 --> 00:23:20.360 align:start position:0% slash followers meaning that you're 00:23:20.360 --> 00:23:24.190 align:start position:0% slash followers meaning that you're you're<00:23:20.780> accessing<00:23:21.260> into<00:23:22.010> the<00:23:22.580> json<00:23:23.059> object<00:23:23.510> so 00:23:24.190 --> 00:23:24.200 align:start position:0% you're accessing into the json object so 00:23:24.200 --> 00:23:25.659 align:start position:0% you're accessing into the json object so you're<00:23:24.350> like<00:23:24.440> putting<00:23:24.860> a<00:23:25.070> JSON<00:23:25.280> object<00:23:25.340> and 00:23:25.659 --> 00:23:25.669 align:start position:0% you're like putting a JSON object and 00:23:25.669 --> 00:23:27.760 align:start position:0% you're like putting a JSON object and accessing<00:23:26.120> through<00:23:26.360> it<00:23:26.510> to<00:23:27.169> get<00:23:27.289> like<00:23:27.440> another 00:23:27.760 --> 00:23:27.770 align:start position:0% accessing through it to get like another 00:23:27.770 --> 00:23:31.750 align:start position:0% accessing through it to get like another piece<00:23:28.039> of<00:23:28.190> the<00:23:28.610> data<00:23:29.200> and<00:23:30.200> you<00:23:30.320> can<00:23:30.470> like<00:23:30.760> do 00:23:31.750 --> 00:23:31.760 align:start position:0% piece of the data and you can like do 00:23:31.760 --> 00:23:32.830 align:start position:0% piece of the data and you can like do whatever<00:23:31.940> right<00:23:32.179> so<00:23:32.270> you<00:23:32.360> can<00:23:32.480> take<00:23:32.600> like<00:23:32.750> the 00:23:32.830 --> 00:23:32.840 align:start position:0% whatever right so you can take like the 00:23:32.840 --> 00:23:34.450 align:start position:0% whatever right so you can take like the somebody's<00:23:33.230> followers<00:23:33.679> those<00:23:34.159> slash 00:23:34.450 --> 00:23:34.460 align:start position:0% somebody's followers those slash 00:23:34.460 --> 00:23:36.520 align:start position:0% somebody's followers those slash followers<00:23:34.909> to<00:23:35.210> get<00:23:35.360> pull<00:23:35.600> that<00:23:35.720> array<00:23:35.960> out<00:23:36.169> and 00:23:36.520 --> 00:23:36.530 align:start position:0% followers to get pull that array out and 00:23:36.530 --> 00:23:38.529 align:start position:0% followers to get pull that array out and then<00:23:37.010> go<00:23:37.190> like<00:23:37.370> slash<00:23:37.610> zero<00:23:37.940> to<00:23:38.030> pull<00:23:38.299> out<00:23:38.419> the 00:23:38.529 --> 00:23:38.539 align:start position:0% then go like slash zero to pull out the 00:23:38.539 --> 00:23:40.330 align:start position:0% then go like slash zero to pull out the first<00:23:38.750> entry<00:23:39.080> and<00:23:39.289> now<00:23:39.770> you<00:23:39.830> get<00:23:40.070> something 00:23:40.330 --> 00:23:40.340 align:start position:0% first entry and now you get something 00:23:40.340 --> 00:23:42.580 align:start position:0% first entry and now you get something and<00:23:40.460> this<00:23:40.640> is<00:23:40.850> resolving<00:23:41.330> through<00:23:41.690> merkel 00:23:42.580 --> 00:23:42.590 align:start position:0% and this is resolving through merkel 00:23:42.590 --> 00:23:44.380 align:start position:0% and this is resolving through merkel links<00:23:42.860> the<00:23:43.159> idea<00:23:43.370> there<00:23:43.520> is<00:23:43.549> that<00:23:43.669> like<00:23:43.940> you 00:23:44.380 --> 00:23:44.390 align:start position:0% links the idea there is that like you 00:23:44.390 --> 00:23:46.000 align:start position:0% links the idea there is that like you would<00:23:44.510> pull<00:23:44.690> one<00:23:44.840> object<00:23:45.169> out<00:23:45.350> and<00:23:45.649> then<00:23:45.799> you 00:23:46.000 --> 00:23:46.010 align:start position:0% would pull one object out and then you 00:23:46.010 --> 00:23:48.070 align:start position:0% would pull one object out and then you would<00:23:46.159> look<00:23:47.000> into<00:23:47.210> it<00:23:47.299> pull<00:23:47.690> up<00:23:47.780> pull<00:23:48.020> out 00:23:48.070 --> 00:23:48.080 align:start position:0% would look into it pull up pull out 00:23:48.080 --> 00:23:50.030 align:start position:0% would look into it pull up pull out another<00:23:48.440> link<00:23:48.710> and<00:23:48.860> resolve<00:23:49.130> it<00:23:49.220> through 00:23:50.030 --> 00:23:50.040 align:start position:0% another link and resolve it through 00:23:50.040 --> 00:23:52.400 align:start position:0% another link and resolve it through through<00:23:50.160> the<00:23:50.250> network<00:23:50.490> and<00:23:51.420> everything<00:23:52.320> is 00:23:52.400 --> 00:23:52.410 align:start position:0% through the network and everything is 00:23:52.410 --> 00:23:53.990 align:start position:0% through the network and everything is integrity<00:23:52.650> text<00:23:53.100> so<00:23:53.190> you<00:23:53.310> can<00:23:53.460> just<00:23:53.610> dump<00:23:53.760> all 00:23:53.990 --> 00:23:54.000 align:start position:0% integrity text so you can just dump all 00:23:54.000 --> 00:23:55.370 align:start position:0% integrity text so you can just dump all of<00:23:54.030> this<00:23:54.240> content<00:23:54.570> into<00:23:54.780> the<00:23:54.900> network<00:23:55.170> and 00:23:55.370 --> 00:23:55.380 align:start position:0% of this content into the network and 00:23:55.380 --> 00:23:57.170 align:start position:0% of this content into the network and anybody<00:23:56.100> can<00:23:56.370> serve<00:23:56.520> it<00:23:56.640> to<00:23:56.700> you<00:23:56.820> and<00:23:57.060> you 00:23:57.170 --> 00:23:57.180 align:start position:0% anybody can serve it to you and you 00:23:57.180 --> 00:23:59.810 align:start position:0% anybody can serve it to you and you don't<00:23:57.330> have<00:23:57.420> to<00:23:57.540> worry<00:23:57.690> about<00:23:57.780> that<00:23:58.700> you<00:23:59.700> have 00:23:59.810 --> 00:23:59.820 align:start position:0% don't have to worry about that you have 00:23:59.820 --> 00:24:01.010 align:start position:0% don't have to worry about that you have to<00:23:59.880> worry<00:24:00.000> about<00:24:00.150> it<00:24:00.240> in<00:24:00.390> terms<00:24:00.480> of<00:24:00.660> privacy 00:24:01.010 --> 00:24:01.020 align:start position:0% to worry about it in terms of privacy 00:24:01.020 --> 00:24:01.850 align:start position:0% to worry about it in terms of privacy but<00:24:01.110> that's<00:24:01.260> a<00:24:01.320> whole<00:24:01.470> different<00:24:01.770> question 00:24:01.850 --> 00:24:01.860 align:start position:0% but that's a whole different question 00:24:01.860 --> 00:24:05.120 align:start position:0% but that's a whole different question and<00:24:02.900> anyway<00:24:03.900> so<00:24:03.960> you<00:24:04.080> can<00:24:04.290> model<00:24:04.680> things<00:24:04.890> right 00:24:05.120 --> 00:24:05.130 align:start position:0% and anyway so you can model things right 00:24:05.130 --> 00:24:06.830 align:start position:0% and anyway so you can model things right you<00:24:05.580> can<00:24:05.700> pretty<00:24:05.940> much<00:24:06.030> mobile<00:24:06.300> anything<00:24:06.660> one 00:24:06.830 --> 00:24:06.840 align:start position:0% you can pretty much mobile anything one 00:24:06.840 --> 00:24:08.630 align:start position:0% you can pretty much mobile anything one you<00:24:07.020> get<00:24:07.170> you<00:24:07.770> get<00:24:07.890> to<00:24:07.980> be<00:24:08.070> able<00:24:08.130> to<00:24:08.280> annotate 00:24:08.630 --> 00:24:08.640 align:start position:0% you get you get to be able to annotate 00:24:08.640 --> 00:24:11.450 align:start position:0% you get you get to be able to annotate links<00:24:09.060> with<00:24:09.240> other<00:24:09.360> data<00:24:10.130> here's<00:24:11.130> like<00:24:11.280> what<00:24:11.430> a 00:24:11.450 --> 00:24:11.460 align:start position:0% links with other data here's like what a 00:24:11.460 --> 00:24:13.100 align:start position:0% links with other data here's like what a directory<00:24:11.880> would<00:24:12.030> look<00:24:12.210> like<00:24:12.360> you<00:24:12.930> could<00:24:13.050> do 00:24:13.100 --> 00:24:13.110 align:start position:0% directory would look like you could do 00:24:13.110 --> 00:24:14.720 align:start position:0% directory would look like you could do like<00:24:13.230> version<00:24:13.590> data<00:24:13.830> structures<00:24:14.220> this<00:24:14.400> is<00:24:14.460> for 00:24:14.720 --> 00:24:14.730 align:start position:0% like version data structures this is for 00:24:14.730 --> 00:24:17.450 align:start position:0% like version data structures this is for example<00:24:14.850> a<00:24:15.090> git<00:24:15.300> commit<00:24:15.600> and<00:24:16.260> so<00:24:17.070> on<00:24:17.220> and<00:24:17.370> so 00:24:17.450 --> 00:24:17.460 align:start position:0% example a git commit and so on and so 00:24:17.460 --> 00:24:19.160 align:start position:0% example a git commit and so on and so these<00:24:17.610> these<00:24:17.910> will<00:24:18.030> be<00:24:18.150> completely<00:24:18.630> native<00:24:18.810> in 00:24:19.160 --> 00:24:19.170 align:start position:0% these these will be completely native in 00:24:19.170 --> 00:24:20.570 align:start position:0% these these will be completely native in ipfs<00:24:19.620> you'll<00:24:19.830> be<00:24:19.890> able<00:24:19.950> to<00:24:20.130> write<00:24:20.250> all<00:24:20.430> these 00:24:20.570 --> 00:24:20.580 align:start position:0% ipfs you'll be able to write all these 00:24:20.580 --> 00:24:22.370 align:start position:0% ipfs you'll be able to write all these data<00:24:20.760> structures<00:24:21.030> and<00:24:21.360> have<00:24:21.810> them<00:24:21.990> write<00:24:22.200> on 00:24:22.370 --> 00:24:22.380 align:start position:0% data structures and have them write on 00:24:22.380 --> 00:24:23.720 align:start position:0% data structures and have them write on this<00:24:22.530> this<00:24:22.830> transport<00:24:23.310> right<00:24:23.430> like<00:24:23.610> the 00:24:23.720 --> 00:24:23.730 align:start position:0% this this transport right like the 00:24:23.730 --> 00:24:24.950 align:start position:0% this this transport right like the forest<00:24:24.210> thing<00:24:24.360> that<00:24:24.510> I<00:24:24.570> described<00:24:24.870> earlier 00:24:24.950 --> 00:24:24.960 align:start position:0% forest thing that I described earlier 00:24:24.960 --> 00:24:27.170 align:start position:0% forest thing that I described earlier and<00:24:25.380> so<00:24:25.950> this<00:24:26.070> is<00:24:26.220> really<00:24:26.520> how<00:24:26.640> you<00:24:26.670> we<00:24:26.940> start 00:24:27.170 --> 00:24:27.180 align:start position:0% and so this is really how you we start 00:24:27.180 --> 00:24:29.000 align:start position:0% and so this is really how you we start doing<00:24:27.390> web<00:24:27.600> 2.0<00:24:28.020> where<00:24:28.290> we<00:24:28.440> take<00:24:28.770> all<00:24:28.920> these 00:24:29.000 --> 00:24:29.010 align:start position:0% doing web 2.0 where we take all these 00:24:29.010 --> 00:24:30.500 align:start position:0% doing web 2.0 where we take all these data<00:24:29.250> structures<00:24:29.490> than<00:24:29.820> these<00:24:29.970> these<00:24:30.240> KPIs 00:24:30.500 --> 00:24:30.510 align:start position:0% data structures than these these KPIs 00:24:30.510 --> 00:24:32.270 align:start position:0% data structures than these these KPIs and<00:24:30.900> model<00:24:31.230> our<00:24:31.350> applications<00:24:31.860> around 00:24:32.270 --> 00:24:32.280 align:start position:0% and model our applications around 00:24:32.280 --> 00:24:34.520 align:start position:0% and model our applications around content<00:24:33.030> that<00:24:33.210> we<00:24:33.300> were<00:24:33.390> just<00:24:33.570> putting<00:24:34.230> into 00:24:34.520 --> 00:24:34.530 align:start position:0% content that we were just putting into 00:24:34.530 --> 00:24:36.620 align:start position:0% content that we were just putting into the<00:24:34.620> network<00:24:34.920> and<00:24:35.130> addressing<00:24:35.850> through 00:24:36.620 --> 00:24:36.630 align:start position:0% the network and addressing through 00:24:36.630 --> 00:24:39.280 align:start position:0% the network and addressing through content<00:24:37.380> addressing<00:24:37.770> and<00:24:37.890> key<00:24:38.010> addressing 00:24:39.280 --> 00:24:39.290 align:start position:0% content addressing and key addressing 00:24:39.290 --> 00:24:41.900 align:start position:0% content addressing and key addressing and<00:24:40.290> so<00:24:40.410> in<00:24:41.010> a<00:24:41.160> sense<00:24:41.370> when<00:24:41.550> you<00:24:41.640> think<00:24:41.850> about 00:24:41.900 --> 00:24:41.910 align:start position:0% and so in a sense when you think about 00:24:41.910 --> 00:24:43.370 align:start position:0% and so in a sense when you think about model<00:24:42.300> in<00:24:42.420> your<00:24:42.540> application<00:24:42.990> and<00:24:43.140> you<00:24:43.230> think 00:24:43.370 --> 00:24:43.380 align:start position:0% model in your application and you think 00:24:43.380 --> 00:24:45.110 align:start position:0% model in your application and you think about<00:24:43.440> like<00:24:43.680> the<00:24:44.070> data<00:24:44.250> model<00:24:44.640> right<00:24:44.790> like<00:24:44.970> oh 00:24:45.110 --> 00:24:45.120 align:start position:0% about like the data model right like oh 00:24:45.120 --> 00:24:46.790 align:start position:0% about like the data model right like oh do<00:24:45.570> I<00:24:45.600> have<00:24:45.720> users<00:24:46.080> that<00:24:46.350> they<00:24:46.470> follow<00:24:46.710> each 00:24:46.790 --> 00:24:46.800 align:start position:0% do I have users that they follow each 00:24:46.800 --> 00:24:48.070 align:start position:0% do I have users that they follow each other<00:24:47.070> like<00:24:47.370> what<00:24:47.550> are<00:24:47.640> all<00:24:47.760> these 00:24:48.070 --> 00:24:48.080 align:start position:0% other like what are all these 00:24:48.080 --> 00:24:51.410 align:start position:0% other like what are all these relationships<00:24:49.460> you<00:24:50.460> can<00:24:50.610> take<00:24:50.760> those<00:24:50.910> direct 00:24:51.410 --> 00:24:51.420 align:start position:0% relationships you can take those direct 00:24:51.420 --> 00:24:53.780 align:start position:0% relationships you can take those direct objects<00:24:52.020> and<00:24:52.200> put<00:24:52.710> them<00:24:52.890> straight<00:24:53.100> into<00:24:53.310> ipfs 00:24:53.780 --> 00:24:53.790 align:start position:0% objects and put them straight into ipfs 00:24:53.790 --> 00:24:55.250 align:start position:0% objects and put them straight into ipfs like<00:24:54.000> you<00:24:54.090> don't<00:24:54.270> have<00:24:54.390> to<00:24:54.510> go<00:24:54.600> to<00:24:54.690> the<00:24:54.840> Twitter 00:24:55.250 --> 00:24:55.260 align:start position:0% like you don't have to go to the Twitter 00:24:55.260 --> 00:24:56.780 align:start position:0% like you don't have to go to the Twitter data<00:24:55.290> base<00:24:55.530> at<00:24:55.650> all<00:24:55.710> you<00:24:56.070> can<00:24:56.190> just<00:24:56.220> add<00:24:56.580> them 00:24:56.780 --> 00:24:56.790 align:start position:0% data base at all you can just add them 00:24:56.790 --> 00:24:58.430 align:start position:0% data base at all you can just add them straight<00:24:57.030> to<00:24:57.090> my<00:24:57.180> PFS<00:24:57.330> and<00:24:57.690> what<00:24:57.780> you<00:24:57.900> gain<00:24:58.140> is 00:24:58.430 --> 00:24:58.440 align:start position:0% straight to my PFS and what you gain is 00:24:58.440 --> 00:25:00.710 align:start position:0% straight to my PFS and what you gain is that<00:24:58.770> when<00:24:59.130> an<00:24:59.310> application<00:24:59.760> pulls<00:25:00.240> those<00:25:00.450> in 00:25:00.710 --> 00:25:00.720 align:start position:0% that when an application pulls those in 00:25:00.720 --> 00:25:02.180 align:start position:0% that when an application pulls those in if<00:25:00.990> there's<00:25:01.470> nothing<00:25:01.710> that<00:25:01.830> has<00:25:01.950> changed 00:25:02.180 --> 00:25:02.190 align:start position:0% if there's nothing that has changed 00:25:02.190 --> 00:25:04.280 align:start position:0% if there's nothing that has changed nothing<00:25:02.790> has<00:25:02.880> to<00:25:03.000> be<00:25:03.090> updated<00:25:03.510> so<00:25:03.690> you<00:25:03.960> beat 00:25:04.280 --> 00:25:04.290 align:start position:0% nothing has to be updated so you beat 00:25:04.290 --> 00:25:06.920 align:start position:0% nothing has to be updated so you beat the<00:25:04.440> speed<00:25:04.620> of<00:25:04.740> light<00:25:04.920> because<00:25:05.670> if<00:25:05.910> it's<00:25:06.090> if<00:25:06.690> I 00:25:06.920 --> 00:25:06.930 align:start position:0% the speed of light because if it's if I 00:25:06.930 --> 00:25:08.540 align:start position:0% the speed of light because if it's if I if<00:25:07.230> I'm<00:25:07.350> using<00:25:07.500> an<00:25:07.710> application<00:25:07.860> here<00:25:08.340> and<00:25:08.490> I 00:25:08.540 --> 00:25:08.550 align:start position:0% if I'm using an application here and I 00:25:08.550 --> 00:25:09.920 align:start position:0% if I'm using an application here and I request<00:25:08.880> some<00:25:09.000> set<00:25:09.150> of<00:25:09.180> objects<00:25:09.540> and<00:25:09.690> I<00:25:09.720> pulled 00:25:09.920 --> 00:25:09.930 align:start position:0% request some set of objects and I pulled 00:25:09.930 --> 00:25:11.540 align:start position:0% request some set of objects and I pulled them<00:25:10.020> down<00:25:10.200> through<00:25:10.440> the<00:25:10.560> network<00:25:10.830> and<00:25:11.040> I<00:25:11.370> have 00:25:11.540 --> 00:25:11.550 align:start position:0% them down through the network and I have 00:25:11.550 --> 00:25:13.700 align:start position:0% them down through the network and I have them<00:25:11.700> locally<00:25:12.030> and<00:25:13.020> I<00:25:13.110> have<00:25:13.230> to<00:25:13.350> fetch<00:25:13.530> them 00:25:13.700 --> 00:25:13.710 align:start position:0% them locally and I have to fetch them 00:25:13.710 --> 00:25:16.610 align:start position:0% them locally and I have to fetch them again<00:25:14.450> normally<00:25:15.450> HTTP<00:25:15.780> would<00:25:15.930> say<00:25:16.020> oh<00:25:16.200> you 00:25:16.610 --> 00:25:16.620 align:start position:0% again normally HTTP would say oh you 00:25:16.620 --> 00:25:18.530 align:start position:0% again normally HTTP would say oh you know<00:25:16.740> like<00:25:17.010> go<00:25:17.580> and<00:25:17.820> like<00:25:18.000> talk<00:25:18.360> to<00:25:18.390> the 00:25:18.530 --> 00:25:18.540 align:start position:0% know like go and like talk to the 00:25:18.540 --> 00:25:20.300 align:start position:0% know like go and like talk to the network<00:25:18.690> and<00:25:19.020> see<00:25:19.140> if<00:25:19.290> it<00:25:19.380> has<00:25:19.470> changed<00:25:19.860> but 00:25:20.300 --> 00:25:20.310 align:start position:0% network and see if it has changed but 00:25:20.310 --> 00:25:22.190 align:start position:0% network and see if it has changed but would<00:25:20.490> ipfs<00:25:20.850> we<00:25:20.940> can<00:25:21.060> be<00:25:21.120> like<00:25:21.210> well<00:25:21.360> no<00:25:21.600> I<00:25:21.960> have 00:25:22.190 --> 00:25:22.200 align:start position:0% would ipfs we can be like well no I have 00:25:22.200 --> 00:25:24.470 align:start position:0% would ipfs we can be like well no I have the<00:25:22.290> hash<00:25:22.470> I<00:25:22.800> have<00:25:22.950> the<00:25:23.070> content<00:25:23.430> it<00:25:23.760> sits<00:25:24.420> here 00:25:24.470 --> 00:25:24.480 align:start position:0% the hash I have the content it sits here 00:25:24.480 --> 00:25:26.180 align:start position:0% the hash I have the content it sits here already<00:25:24.900> we<00:25:25.320> don't<00:25:25.680> have<00:25:25.860> to<00:25:25.950> go<00:25:26.040> to<00:25:26.100> the 00:25:26.180 --> 00:25:26.190 align:start position:0% already we don't have to go to the 00:25:26.190 --> 00:25:28.160 align:start position:0% already we don't have to go to the network<00:25:26.570> and<00:25:27.570> of<00:25:27.660> course<00:25:27.780> you<00:25:27.870> can<00:25:27.990> do<00:25:28.050> this 00:25:28.160 --> 00:25:28.170 align:start position:0% network and of course you can do this 00:25:28.170 --> 00:25:29.990 align:start position:0% network and of course you can do this with<00:25:28.320> like<00:25:28.530> all<00:25:28.740> kinds<00:25:29.070> of<00:25:29.130> like<00:25:29.310> legal 00:25:29.990 --> 00:25:30.000 align:start position:0% with like all kinds of like legal 00:25:30.000 --> 00:25:31.580 align:start position:0% with like all kinds of like legal records<00:25:30.270> and<00:25:30.390> so<00:25:30.480> on<00:25:30.600> like<00:25:30.840> admit<00:25:31.140> legal 00:25:31.580 --> 00:25:31.590 align:start position:0% records and so on like admit legal 00:25:31.590 --> 00:25:33.380 align:start position:0% records and so on like admit legal records<00:25:31.830> is<00:25:31.980> a<00:25:32.010> great<00:25:32.220> example<00:25:32.820> of<00:25:33.120> like<00:25:33.300> why 00:25:33.380 --> 00:25:33.390 align:start position:0% records is a great example of like why 00:25:33.390 --> 00:25:35.540 align:start position:0% records is a great example of like why people<00:25:33.450> want<00:25:33.810> to<00:25:33.900> use<00:25:33.930> block<00:25:34.560> chains<00:25:34.800> kind<00:25:35.490> of 00:25:35.540 --> 00:25:35.550 align:start position:0% people want to use block chains kind of 00:25:35.550 --> 00:25:38.300 align:start position:0% people want to use block chains kind of like<00:25:35.670> in<00:25:35.760> the<00:25:35.880> in<00:25:36.180> the<00:25:36.300> real<00:25:36.450> world<00:25:36.770> it's<00:25:37.770> it's 00:25:38.300 --> 00:25:38.310 align:start position:0% like in the in the real world it's it's 00:25:38.310 --> 00:25:41.330 align:start position:0% like in the in the real world it's it's to<00:25:38.580> like<00:25:38.760> do<00:25:39.690> careful<00:25:40.410> time<00:25:40.770> stamping<00:25:41.160> of 00:25:41.330 --> 00:25:41.340 align:start position:0% to like do careful time stamping of 00:25:41.340 --> 00:25:44.120 align:start position:0% to like do careful time stamping of legal<00:25:42.180> documents<00:25:42.270> right<00:25:42.750> so<00:25:43.740> you<00:25:43.830> can<00:25:43.920> do<00:25:44.010> all 00:25:44.120 --> 00:25:44.130 align:start position:0% legal documents right so you can do all 00:25:44.130 --> 00:25:45.560 align:start position:0% legal documents right so you can do all this<00:25:44.280> and<00:25:44.340> so<00:25:44.550> in<00:25:44.760> reality<00:25:45.120> we're<00:25:45.240> building 00:25:45.560 --> 00:25:45.570 align:start position:0% this and so in reality we're building 00:25:45.570 --> 00:25:47.750 align:start position:0% this and so in reality we're building not<00:25:46.350> exactly<00:25:46.650> the<00:25:46.860> web<00:25:47.040> but<00:25:47.220> it's<00:25:47.370> really<00:25:47.520> like 00:25:47.750 --> 00:25:47.760 align:start position:0% not exactly the web but it's really like 00:25:47.760 --> 00:25:50.180 align:start position:0% not exactly the web but it's really like more<00:25:48.060> like<00:25:48.420> a<00:25:48.510> strong<00:25:48.960> mesh<00:25:49.410> that<00:25:49.680> is<00:25:49.770> secured 00:25:50.180 --> 00:25:50.190 align:start position:0% more like a strong mesh that is secured 00:25:50.190 --> 00:25:52.010 align:start position:0% more like a strong mesh that is secured right<00:25:50.760> like<00:25:50.880> you<00:25:50.970> can<00:25:51.240> think<00:25:51.450> of<00:25:51.540> it<00:25:51.660> it<00:25:51.990> is 00:25:52.010 --> 00:25:52.020 align:start position:0% right like you can think of it it is 00:25:52.020 --> 00:25:54.290 align:start position:0% right like you can think of it it is like<00:25:52.140> a<00:25:52.320> secure<00:25:52.770> web<00:25:53.010> or<00:25:53.520> the<00:25:53.700> links<00:25:54.000> can't 00:25:54.290 --> 00:25:54.300 align:start position:0% like a secure web or the links can't 00:25:54.300 --> 00:25:56.510 align:start position:0% like a secure web or the links can't break<00:25:54.570> because<00:25:55.530> they're<00:25:55.650> their<00:25:55.950> content 00:25:56.510 --> 00:25:56.520 align:start position:0% break because they're their content 00:25:56.520 --> 00:25:57.830 align:start position:0% break because they're their content addressed<00:25:56.790> so<00:25:57.090> you<00:25:57.150> don't<00:25:57.390> have<00:25:57.570> to<00:25:57.720> maintain 00:25:57.830 --> 00:25:57.840 align:start position:0% addressed so you don't have to maintain 00:25:57.840 --> 00:25:59.840 align:start position:0% addressed so you don't have to maintain infrastructure<00:25:58.440> and<00:25:58.740> worry<00:25:59.310> that<00:25:59.400> like<00:25:59.700> your 00:25:59.840 --> 00:25:59.850 align:start position:0% infrastructure and worry that like your 00:25:59.850 --> 00:26:01.430 align:start position:0% infrastructure and worry that like your link<00:26:00.060> now<00:26:00.330> is<00:26:00.540> slightly<00:26:00.750> different<00:26:01.170> and<00:26:01.350> so 00:26:01.430 --> 00:26:01.440 align:start position:0% link now is slightly different and so 00:26:01.440 --> 00:26:02.900 align:start position:0% link now is slightly different and so everything<00:26:01.740> will<00:26:01.860> fall<00:26:01.950> apart<00:26:02.010> you<00:26:02.700> just 00:26:02.900 --> 00:26:02.910 align:start position:0% everything will fall apart you just 00:26:02.910 --> 00:26:03.830 align:start position:0% everything will fall apart you just create<00:26:03.120> content<00:26:03.300> you 00:26:03.830 --> 00:26:03.840 align:start position:0% create content you 00:26:03.840 --> 00:26:05.539 align:start position:0% create content you get<00:26:04.020> securely<00:26:04.440> and<00:26:04.770> you<00:26:05.100> just<00:26:05.250> release<00:26:05.520> it 00:26:05.539 --> 00:26:05.549 align:start position:0% get securely and you just release it 00:26:05.549 --> 00:26:08.899 align:start position:0% get securely and you just release it into<00:26:05.789> the<00:26:05.909> network<00:26:07.429> and<00:26:08.429> so<00:26:08.520> I<00:26:08.549> mentioned<00:26:08.730> that 00:26:08.899 --> 00:26:08.909 align:start position:0% into the network and so I mentioned that 00:26:08.909 --> 00:26:11.029 align:start position:0% into the network and so I mentioned that that<00:26:09.270> I<00:26:09.600> peeled<00:26:09.809> evening<00:26:10.140> is<00:26:10.289> suspect<00:26:10.950> in 00:26:11.029 --> 00:26:11.039 align:start position:0% that I peeled evening is suspect in 00:26:11.039 --> 00:26:13.130 align:start position:0% that I peeled evening is suspect in progress<00:26:11.510> some<00:26:12.510> of<00:26:12.539> the<00:26:12.690> interesting<00:26:13.049> stuff 00:26:13.130 --> 00:26:13.140 align:start position:0% progress some of the interesting stuff 00:26:13.140 --> 00:26:14.630 align:start position:0% progress some of the interesting stuff that<00:26:13.200> we're<00:26:13.350> doing<00:26:13.440> is<00:26:13.740> we<00:26:13.980> are<00:26:14.010> coming<00:26:14.429> with<00:26:14.610> a 00:26:14.630 --> 00:26:14.640 align:start position:0% that we're doing is we are coming with a 00:26:14.640 --> 00:26:16.299 align:start position:0% that we're doing is we are coming with a coming<00:26:15.480> up<00:26:15.539> with<00:26:15.630> a<00:26:15.690> right<00:26:15.900> way<00:26:16.049> of<00:26:16.169> doing 00:26:16.299 --> 00:26:16.309 align:start position:0% coming up with a right way of doing 00:26:16.309 --> 00:26:18.680 align:start position:0% coming up with a right way of doing traversals<00:26:17.309> through<00:26:17.880> the<00:26:18.120> graph<00:26:18.299> so<00:26:18.480> being 00:26:18.680 --> 00:26:18.690 align:start position:0% traversals through the graph so being 00:26:18.690 --> 00:26:21.350 align:start position:0% traversals through the graph so being able<00:26:18.809> to<00:26:18.929> express<00:26:19.880> descending<00:26:20.880> down<00:26:21.000> a<00:26:21.059> path 00:26:21.350 --> 00:26:21.360 align:start position:0% able to express descending down a path 00:26:21.360 --> 00:26:23.570 align:start position:0% able to express descending down a path in<00:26:21.539> the<00:26:21.960> graph<00:26:22.049> things<00:26:22.950> like<00:26:23.190> being<00:26:23.370> able<00:26:23.429> to 00:26:23.570 --> 00:26:23.580 align:start position:0% in the graph things like being able to 00:26:23.580 --> 00:26:25.360 align:start position:0% in the graph things like being able to address<00:26:24.059> one<00:26:24.539> level<00:26:24.720> deep<00:26:24.960> or<00:26:25.200> like 00:26:25.360 --> 00:26:25.370 align:start position:0% address one level deep or like 00:26:25.370 --> 00:26:27.320 align:start position:0% address one level deep or like everything<00:26:26.370> underneath<00:26:26.669> it<00:26:26.820> or<00:26:27.029> being<00:26:27.240> able 00:26:27.320 --> 00:26:27.330 align:start position:0% everything underneath it or being able 00:26:27.330 --> 00:26:29.380 align:start position:0% everything underneath it or being able to<00:26:27.419> like<00:26:27.570> look<00:26:28.140> into<00:26:28.289> something 00:26:29.380 --> 00:26:29.390 align:start position:0% to like look into something 00:26:29.390 --> 00:26:31.399 align:start position:0% to like look into something but<00:26:30.390> then<00:26:30.480> something<00:26:30.779> more<00:26:30.990> interesting<00:26:31.200> like 00:26:31.399 --> 00:26:31.409 align:start position:0% but then something more interesting like 00:26:31.409 --> 00:26:33.049 align:start position:0% but then something more interesting like being<00:26:31.710> able<00:26:31.830> to<00:26:32.010> so<00:26:32.460> this<00:26:32.580> last<00:26:32.789> expression 00:26:33.049 --> 00:26:33.059 align:start position:0% being able to so this last expression 00:26:33.059 --> 00:26:37.100 align:start position:0% being able to so this last expression would<00:26:33.539> be<00:26:33.600> able<00:26:34.380> to<00:26:35.000> in<00:26:36.000> in<00:26:36.270> a<00:26:36.330> huge<00:26:36.600> graph<00:26:36.870> that 00:26:37.100 --> 00:26:37.110 align:start position:0% would be able to in in a huge graph that 00:26:37.110 --> 00:26:38.779 align:start position:0% would be able to in in a huge graph that represents<00:26:37.169> a<00:26:37.679> movie<00:26:37.950> being<00:26:38.220> able<00:26:38.370> being<00:26:38.730> able 00:26:38.779 --> 00:26:38.789 align:start position:0% represents a movie being able being able 00:26:38.789 --> 00:26:40.310 align:start position:0% represents a movie being able being able to<00:26:38.940> walk<00:26:39.149> down<00:26:39.179> the<00:26:39.539> first<00:26:39.750> path<00:26:39.990> and 00:26:40.310 --> 00:26:40.320 align:start position:0% to walk down the first path and 00:26:40.320 --> 00:26:43.070 align:start position:0% to walk down the first path and retrieving<00:26:40.799> the<00:26:40.919> first<00:26:41.159> set<00:26:41.309> of<00:26:41.340> blocks<00:26:41.669> in<00:26:42.360> so 00:26:43.070 --> 00:26:43.080 align:start position:0% retrieving the first set of blocks in so 00:26:43.080 --> 00:26:44.779 align:start position:0% retrieving the first set of blocks in so that<00:26:43.200> with<00:26:43.380> that<00:26:43.590> you<00:26:43.860> are<00:26:44.159> able<00:26:44.250> to<00:26:44.340> just<00:26:44.520> pull 00:26:44.779 --> 00:26:44.789 align:start position:0% that with that you are able to just pull 00:26:44.789 --> 00:26:46.159 align:start position:0% that with that you are able to just pull out<00:26:44.820> the<00:26:44.940> first<00:26:45.240> few<00:26:45.480> things<00:26:45.690> that<00:26:45.929> have<00:26:46.080> the 00:26:46.159 --> 00:26:46.169 align:start position:0% out the first few things that have the 00:26:46.169 --> 00:26:47.960 align:start position:0% out the first few things that have the data<00:26:46.350> and<00:26:46.620> then<00:26:46.950> start<00:26:47.220> showing<00:26:47.610> the<00:26:47.789> user 00:26:47.960 --> 00:26:47.970 align:start position:0% data and then start showing the user 00:26:47.970 --> 00:26:51.289 align:start position:0% data and then start showing the user like<00:26:48.270> the<00:26:48.649> like<00:26:49.669> beginning<00:26:50.669> of<00:26:50.850> a<00:26:50.909> movie<00:26:51.120> right 00:26:51.289 --> 00:26:51.299 align:start position:0% like the like beginning of a movie right 00:26:51.299 --> 00:26:53.060 align:start position:0% like the like beginning of a movie right so<00:26:52.049> being<00:26:52.200> able<00:26:52.260> to<00:26:52.350> express<00:26:52.710> these<00:26:52.890> things 00:26:53.060 --> 00:26:53.070 align:start position:0% so being able to express these things 00:26:53.070 --> 00:26:54.409 align:start position:0% so being able to express these things this<00:26:53.250> way<00:26:53.429> it's<00:26:53.640> extremely<00:26:54.000> useful<00:26:54.149> for 00:26:54.409 --> 00:26:54.419 align:start position:0% this way it's extremely useful for 00:26:54.419 --> 00:26:56.120 align:start position:0% this way it's extremely useful for replication<00:26:54.809> protocols<00:26:55.289> it's<00:26:55.770> extremely 00:26:56.120 --> 00:26:56.130 align:start position:0% replication protocols it's extremely 00:26:56.130 --> 00:26:58.340 align:start position:0% replication protocols it's extremely useful<00:26:56.250> to<00:26:56.490> be<00:26:56.580> able<00:26:56.610> to<00:26:56.760> like<00:26:56.990> point<00:26:57.990> stuff 00:26:58.340 --> 00:26:58.350 align:start position:0% useful to be able to like point stuff 00:26:58.350 --> 00:27:00.740 align:start position:0% useful to be able to like point stuff out<00:26:58.529> in<00:26:58.830> contracts<00:26:59.309> and<00:26:59.399> so<00:26:59.549> on<00:26:59.669> so<00:27:00.570> this<00:27:00.659> is 00:27:00.740 --> 00:27:00.750 align:start position:0% out in contracts and so on so this is 00:27:00.750 --> 00:27:02.120 align:start position:0% out in contracts and so on so this is kind<00:27:00.870> of<00:27:00.899> an<00:27:01.020> interesting<00:27:01.200> thing<00:27:01.470> another<00:27:01.950> one 00:27:02.120 --> 00:27:02.130 align:start position:0% kind of an interesting thing another one 00:27:02.130 --> 00:27:03.799 align:start position:0% kind of an interesting thing another one here<00:27:02.340> is<00:27:02.399> where<00:27:02.549> you<00:27:02.700> would<00:27:02.820> like<00:27:03.029> embed 00:27:03.799 --> 00:27:03.809 align:start position:0% here is where you would like embed 00:27:03.809 --> 00:27:05.570 align:start position:0% here is where you would like embed replicas<00:27:04.440> like<00:27:04.559> yeah<00:27:04.649> but<00:27:04.860> one<00:27:05.070> expression<00:27:05.399> is 00:27:05.570 --> 00:27:05.580 align:start position:0% replicas like yeah but one expression is 00:27:05.580 --> 00:27:07.490 align:start position:0% replicas like yeah but one expression is that<00:27:05.610> another<00:27:05.880> expression<00:27:06.149> so<00:27:06.899> if<00:27:07.110> you<00:27:07.260> if<00:27:07.409> you 00:27:07.490 --> 00:27:07.500 align:start position:0% that another expression so if you if you 00:27:07.500 --> 00:27:08.750 align:start position:0% that another expression so if you if you like<00:27:07.620> this<00:27:07.830> kind<00:27:08.010> of<00:27:08.039> language<00:27:08.220> and<00:27:08.580> stuff 00:27:08.750 --> 00:27:08.760 align:start position:0% like this kind of language and stuff 00:27:08.760 --> 00:27:11.240 align:start position:0% like this kind of language and stuff come<00:27:09.510> talk<00:27:09.659> to<00:27:09.690> make<00:27:09.870> is<00:27:10.130> getting<00:27:11.130> those 00:27:11.240 --> 00:27:11.250 align:start position:0% come talk to make is getting those 00:27:11.250 --> 00:27:14.240 align:start position:0% come talk to make is getting those languages<00:27:11.549> right<00:27:11.789> as<00:27:11.909> important<00:27:13.010> cool<00:27:14.039> so 00:27:14.240 --> 00:27:14.250 align:start position:0% languages right as important cool so 00:27:14.250 --> 00:27:17.060 align:start position:0% languages right as important cool so last<00:27:15.000> section<00:27:15.330> use<00:27:15.929> cases<00:27:16.140> and<00:27:16.350> examples<00:27:16.440> so 00:27:17.060 --> 00:27:17.070 align:start position:0% last section use cases and examples so 00:27:17.070 --> 00:27:18.799 align:start position:0% last section use cases and examples so this<00:27:17.340> might<00:27:17.520> be<00:27:17.549> the<00:27:17.909> most<00:27:18.390> interesting<00:27:18.600> to 00:27:18.799 --> 00:27:18.809 align:start position:0% this might be the most interesting to 00:27:18.809 --> 00:27:19.100 align:start position:0% this might be the most interesting to you 00:27:19.100 --> 00:27:19.110 align:start position:0% you 00:27:19.110 --> 00:27:21.980 align:start position:0% you so<00:27:19.890> I<00:27:19.919> BFS<00:27:20.279> a<00:27:20.820> lot<00:27:21.360> of<00:27:21.450> people<00:27:21.600> are<00:27:21.690> like<00:27:21.750> okay 00:27:21.980 --> 00:27:21.990 align:start position:0% so I BFS a lot of people are like okay 00:27:21.990 --> 00:27:23.840 align:start position:0% so I BFS a lot of people are like okay well<00:27:22.140> what<00:27:22.710> is<00:27:22.799> IP<00:27:23.039> passed<00:27:23.220> for<00:27:23.490> what<00:27:23.700> do<00:27:23.760> you 00:27:23.840 --> 00:27:23.850 align:start position:0% well what is IP passed for what do you 00:27:23.850 --> 00:27:26.149 align:start position:0% well what is IP passed for what do you use<00:27:24.000> it<00:27:24.179> with<00:27:24.480> like<00:27:24.779> what<00:27:25.529> is<00:27:25.620> this<00:27:25.710> thing<00:27:25.770> and 00:27:26.149 --> 00:27:26.159 align:start position:0% use it with like what is this thing and 00:27:26.159 --> 00:27:27.320 align:start position:0% use it with like what is this thing and they<00:27:26.279> want<00:27:26.399> me<00:27:26.580> to<00:27:26.700> tell<00:27:26.880> you<00:27:27.029> like<00:27:27.179> the 00:27:27.320 --> 00:27:27.330 align:start position:0% they want me to tell you like the 00:27:27.330 --> 00:27:29.539 align:start position:0% they want me to tell you like the specific<00:27:27.600> set<00:27:28.230> of<00:27:28.350> users<00:27:28.679> that<00:27:28.860> like<00:27:28.980> are<00:27:29.340> only 00:27:29.539 --> 00:27:29.549 align:start position:0% specific set of users that like are only 00:27:29.549 --> 00:27:31.519 align:start position:0% specific set of users that like are only gonna<00:27:29.789> use<00:27:29.880> it<00:27:30.120> for<00:27:30.149> one<00:27:30.390> thing<00:27:30.419> and<00:27:30.990> in<00:27:31.470> the 00:27:31.519 --> 00:27:31.529 align:start position:0% gonna use it for one thing and in the 00:27:31.529 --> 00:27:32.930 align:start position:0% gonna use it for one thing and in the thing<00:27:31.679> about<00:27:31.830> ipfs<00:27:32.190> is<00:27:32.309> that<00:27:32.429> it's<00:27:32.549> a<00:27:32.610> Transfer 00:27:32.930 --> 00:27:32.940 align:start position:0% thing about ipfs is that it's a Transfer 00:27:32.940 --> 00:27:35.330 align:start position:0% thing about ipfs is that it's a Transfer Protocol<00:27:33.330> meant<00:27:33.570> to<00:27:33.690> like<00:27:33.950> help<00:27:34.950> the<00:27:35.130> web 00:27:35.330 --> 00:27:35.340 align:start position:0% Protocol meant to like help the web 00:27:35.340 --> 00:27:37.460 align:start position:0% Protocol meant to like help the web right<00:27:36.000> and<00:27:36.179> said<00:27:36.270> like<00:27:36.419> what<00:27:36.720> is<00:27:36.809> the<00:27:36.929> web<00:27:37.110> used 00:27:37.460 --> 00:27:37.470 align:start position:0% right and said like what is the web used 00:27:37.470 --> 00:27:42.440 align:start position:0% right and said like what is the web used for<00:27:39.500> everything<00:27:40.500> and<00:27:41.130> then<00:27:41.760> people<00:27:42.000> just<00:27:42.120> say 00:27:42.440 --> 00:27:42.450 align:start position:0% for everything and then people just say 00:27:42.450 --> 00:27:44.330 align:start position:0% for everything and then people just say like<00:27:42.570> oh<00:27:42.840> that's<00:27:43.169> you<00:27:43.860> haven't<00:27:44.220> thought<00:27:44.279> about 00:27:44.330 --> 00:27:44.340 align:start position:0% like oh that's you haven't thought about 00:27:44.340 --> 00:27:45.919 align:start position:0% like oh that's you haven't thought about this<00:27:44.549> and<00:27:44.669> I'm<00:27:44.909> like<00:27:45.059> no<00:27:45.270> I'm<00:27:45.390> serious<00:27:45.779> like 00:27:45.919 --> 00:27:45.929 align:start position:0% this and I'm like no I'm serious like 00:27:45.929 --> 00:27:48.049 align:start position:0% this and I'm like no I'm serious like you<00:27:46.020> can<00:27:46.140> use<00:27:46.260> this<00:27:46.380> for<00:27:46.559> everything<00:27:46.940> let<00:27:47.940> me 00:27:48.049 --> 00:27:48.059 align:start position:0% you can use this for everything let me 00:27:48.059 --> 00:27:49.850 align:start position:0% you can use this for everything let me let<00:27:48.299> me<00:27:48.330> list<00:27:48.600> out<00:27:48.840> the<00:27:48.899> reasons<00:27:49.529> right<00:27:49.710> look 00:27:49.850 --> 00:27:49.860 align:start position:0% let me list out the reasons right look 00:27:49.860 --> 00:27:51.019 align:start position:0% let me list out the reasons right look you<00:27:50.220> can<00:27:50.340> use<00:27:50.460> it<00:27:50.580> to<00:27:50.669> do<00:27:50.760> peer-to-peer 00:27:51.019 --> 00:27:51.029 align:start position:0% you can use it to do peer-to-peer 00:27:51.029 --> 00:27:52.760 align:start position:0% you can use it to do peer-to-peer content<00:27:51.659> delivery<00:27:51.929> ready<00:27:52.169> to<00:27:52.350> think<00:27:52.590> about<00:27:52.740> a 00:27:52.760 --> 00:27:52.770 align:start position:0% content delivery ready to think about a 00:27:52.770 --> 00:27:55.549 align:start position:0% content delivery ready to think about a CDN<00:27:53.159> but<00:27:53.640> like<00:27:53.760> a<00:27:53.789> distributed<00:27:54.360> CDN<00:27:54.870> the 00:27:55.549 --> 00:27:55.559 align:start position:0% CDN but like a distributed CDN the 00:27:55.559 --> 00:27:57.320 align:start position:0% CDN but like a distributed CDN the superdude<00:27:55.950> content<00:27:56.309> distribution<00:27:56.549> network 00:27:57.320 --> 00:27:57.330 align:start position:0% superdude content distribution network 00:27:57.330 --> 00:27:59.840 align:start position:0% superdude content distribution network you<00:27:58.049> could<00:27:58.140> do<00:27:58.230> like<00:27:58.380> a<00:27:58.440> decentralized<00:27:59.429> links 00:27:59.840 --> 00:27:59.850 align:start position:0% you could do like a decentralized links 00:27:59.850 --> 00:28:01.580 align:start position:0% you could do like a decentralized links things<00:28:00.210> where<00:28:00.450> where<00:28:00.929> no<00:28:01.080> authority 00:28:01.580 --> 00:28:01.590 align:start position:0% things where where no authority 00:28:01.590 --> 00:28:03.649 align:start position:0% things where where no authority determines<00:28:02.340> the<00:28:02.460> link<00:28:02.669> you<00:28:02.820> just<00:28:02.850> add<00:28:03.179> content 00:28:03.649 --> 00:28:03.659 align:start position:0% determines the link you just add content 00:28:03.659 --> 00:28:05.090 align:start position:0% determines the link you just add content on<00:28:03.779> the<00:28:03.840> content<00:28:04.140> is<00:28:04.230> now<00:28:04.380> part<00:28:04.950> of<00:28:05.010> the 00:28:05.090 --> 00:28:05.100 align:start position:0% on the content is now part of the 00:28:05.100 --> 00:28:06.980 align:start position:0% on the content is now part of the network<00:28:05.340> where<00:28:06.059> we've<00:28:06.210> talked<00:28:06.630> about<00:28:06.690> before 00:28:06.980 --> 00:28:06.990 align:start position:0% network where we've talked about before 00:28:06.990 --> 00:28:08.779 align:start position:0% network where we've talked about before you<00:28:07.529> can<00:28:07.649> take<00:28:07.799> applications<00:28:08.010> entire 00:28:08.779 --> 00:28:08.789 align:start position:0% you can take applications entire 00:28:08.789 --> 00:28:10.490 align:start position:0% you can take applications entire applications<00:28:09.299> and<00:28:09.450> define<00:28:09.750> them<00:28:09.990> with<00:28:10.260> an<00:28:10.350> IP 00:28:10.490 --> 00:28:10.500 align:start position:0% applications and define them with an IP 00:28:10.500 --> 00:28:13.279 align:start position:0% applications and define them with an IP FS<00:28:10.830> then<00:28:11.610> give<00:28:12.299> people<00:28:12.480> a<00:28:12.690> reference<00:28:13.049> to<00:28:13.140> that 00:28:13.279 --> 00:28:13.289 align:start position:0% FS then give people a reference to that 00:28:13.289 --> 00:28:14.539 align:start position:0% FS then give people a reference to that application<00:28:13.409> that's<00:28:13.860> the<00:28:13.950> link<00:28:14.130> they 00:28:14.539 --> 00:28:14.549 align:start position:0% application that's the link they 00:28:14.549 --> 00:28:16.520 align:start position:0% application that's the link they download<00:28:15.000> it<00:28:15.030> they<00:28:15.270> run<00:28:15.480> the<00:28:15.600> code<00:28:15.809> and<00:28:16.049> they 00:28:16.520 --> 00:28:16.530 align:start position:0% download it they run the code and they 00:28:16.530 --> 00:28:17.580 align:start position:0% download it they run the code and they just<00:28:16.799> do<00:28:16.950> everything<00:28:17.309> on<00:28:17.399> there 00:28:17.580 --> 00:28:17.590 align:start position:0% just do everything on there 00:28:17.590 --> 00:28:20.190 align:start position:0% just do everything on there side<00:28:17.770> so<00:28:18.730> they<00:28:19.090> it's<00:28:19.600> not<00:28:19.870> only<00:28:20.080> the 00:28:20.190 --> 00:28:20.200 align:start position:0% side so they it's not only the 00:28:20.200 --> 00:28:21.630 align:start position:0% side so they it's not only the distribution<00:28:20.470> of<00:28:20.770> the<00:28:20.860> application<00:28:21.279> it's 00:28:21.630 --> 00:28:21.640 align:start position:0% distribution of the application it's 00:28:21.640 --> 00:28:23.149 align:start position:0% distribution of the application it's also<00:28:21.760> the<00:28:21.909> definition<00:28:22.029> of<00:28:22.450> the<00:28:22.539> application 00:28:23.149 --> 00:28:23.159 align:start position:0% also the definition of the application 00:28:23.159 --> 00:28:26.130 align:start position:0% also the definition of the application in<00:28:24.159> an<00:28:24.520> example<00:28:25.179> here<00:28:25.510> it's<00:28:25.630> like<00:28:25.720> people<00:28:25.929> have 00:28:26.130 --> 00:28:26.140 align:start position:0% in an example here it's like people have 00:28:26.140 --> 00:28:27.840 align:start position:0% in an example here it's like people have written<00:28:26.350> video<00:28:26.710> players<00:28:26.950> that<00:28:27.250> go<00:28:27.669> over<00:28:27.760> I 00:28:27.840 --> 00:28:27.850 align:start position:0% written video players that go over I 00:28:27.850 --> 00:28:29.789 align:start position:0% written video players that go over I confess<00:28:28.179> people<00:28:28.480> have<00:28:28.600> taken<00:28:28.809> entire<00:28:29.590> like 00:28:29.789 --> 00:28:29.799 align:start position:0% confess people have taken entire like 00:28:29.799 --> 00:28:32.310 align:start position:0% confess people have taken entire like legal<00:28:30.100> codes<00:28:30.370> people<00:28:31.240> have<00:28:31.360> made<00:28:31.750> like<00:28:31.929> imager 00:28:32.310 --> 00:28:32.320 align:start position:0% legal codes people have made like imager 00:28:32.320 --> 00:28:35.340 align:start position:0% legal codes people have made like imager salad<00:28:32.710> clones<00:28:33.600> people<00:28:34.600> are<00:28:34.720> able<00:28:34.929> to<00:28:34.960> do<00:28:35.140> like 00:28:35.340 --> 00:28:35.350 align:start position:0% salad clones people are able to do like 00:28:35.350 --> 00:28:37.830 align:start position:0% salad clones people are able to do like three<00:28:35.950> models<00:28:36.460> of<00:28:37.090> stuff<00:28:37.360> and<00:28:37.510> be<00:28:37.600> able<00:28:37.750> to 00:28:37.830 --> 00:28:37.840 align:start position:0% three models of stuff and be able to 00:28:37.840 --> 00:28:39.269 align:start position:0% three models of stuff and be able to share<00:28:38.080> them<00:28:38.260> with<00:28:38.289> ipfs<00:28:38.740> because<00:28:39.070> these<00:28:39.130> are 00:28:39.269 --> 00:28:39.279 align:start position:0% share them with ipfs because these are 00:28:39.279 --> 00:28:41.399 align:start position:0% share them with ipfs because these are data<00:28:39.640> intensive<00:28:39.940> kinds<00:28:40.900> of<00:28:40.960> applications 00:28:41.399 --> 00:28:41.409 align:start position:0% data intensive kinds of applications 00:28:41.409 --> 00:28:43.350 align:start position:0% data intensive kinds of applications people<00:28:41.919> are<00:28:42.159> this<00:28:42.370> is<00:28:42.460> not<00:28:42.580> this<00:28:42.909> is<00:28:43.000> the<00:28:43.059> only 00:28:43.350 --> 00:28:43.360 align:start position:0% people are this is not this is the only 00:28:43.360 --> 00:28:44.850 align:start position:0% people are this is not this is the only one<00:28:43.570> in<00:28:43.690> this<00:28:43.809> set<00:28:43.990> that<00:28:44.020> it's<00:28:44.200> not<00:28:44.320> an<00:28:44.470> actual 00:28:44.850 --> 00:28:44.860 align:start position:0% one in this set that it's not an actual 00:28:44.860 --> 00:28:45.990 align:start position:0% one in this set that it's not an actual IP<00:28:45.190> Office<00:28:45.309> application<00:28:45.730> this<00:28:45.820> is<00:28:45.880> a 00:28:45.990 --> 00:28:46.000 align:start position:0% IP Office application this is a 00:28:46.000 --> 00:28:47.610 align:start position:0% IP Office application this is a Minecraft<00:28:46.630> but<00:28:47.200> people<00:28:47.440> are<00:28:47.529> taking 00:28:47.610 --> 00:28:47.620 align:start position:0% Minecraft but people are taking 00:28:47.620 --> 00:28:49.019 align:start position:0% Minecraft but people are taking minecraft<00:28:48.130> and<00:28:48.279> making<00:28:48.520> it<00:28:48.610> so<00:28:48.730> that<00:28:48.850> there's 00:28:49.019 --> 00:28:49.029 align:start position:0% minecraft and making it so that there's 00:28:49.029 --> 00:28:51.299 align:start position:0% minecraft and making it so that there's links<00:28:49.390> between<00:28:49.539> worlds<00:28:50.260> so<00:28:50.710> you're<00:28:51.039> walking 00:28:51.299 --> 00:28:51.309 align:start position:0% links between worlds so you're walking 00:28:51.309 --> 00:28:52.590 align:start position:0% links between worlds so you're walking through<00:28:51.640> a<00:28:51.700> Minecraft<00:28:52.029> world<00:28:52.120> and<00:28:52.299> then<00:28:52.390> you 00:28:52.590 --> 00:28:52.600 align:start position:0% through a Minecraft world and then you 00:28:52.600 --> 00:28:53.880 align:start position:0% through a Minecraft world and then you find<00:28:52.779> a<00:28:52.870> link<00:28:53.020> and<00:28:53.409> you<00:28:53.559> watch<00:28:53.679> this<00:28:53.770> on 00:28:53.880 --> 00:28:53.890 align:start position:0% find a link and you watch this on 00:28:53.890 --> 00:28:55.500 align:start position:0% find a link and you watch this on something<00:28:54.190> somewhere<00:28:54.610> else<00:28:54.730> and<00:28:54.970> all<00:28:55.360> of<00:28:55.480> that 00:28:55.500 --> 00:28:55.510 align:start position:0% something somewhere else and all of that 00:28:55.510 --> 00:28:58.440 align:start position:0% something somewhere else and all of that is<00:28:55.750> served<00:28:55.990> over<00:28:56.230> ipfs<00:28:57.059> people<00:28:58.059> are<00:28:58.149> throwing 00:28:58.440 --> 00:28:58.450 align:start position:0% is served over ipfs people are throwing 00:28:58.450 --> 00:29:01.200 align:start position:0% is served over ipfs people are throwing documents<00:28:59.020> blogs<00:28:59.620> and<00:29:00.130> so<00:29:00.279> on 00:29:01.200 --> 00:29:01.210 align:start position:0% documents blogs and so on 00:29:01.210 --> 00:29:03.269 align:start position:0% documents blogs and so on you<00:29:01.809> can<00:29:01.929> do<00:29:01.990> containers<00:29:02.320> on<00:29:02.409> VMs<00:29:02.770> definition 00:29:03.269 --> 00:29:03.279 align:start position:0% you can do containers on VMs definition 00:29:03.279 --> 00:29:05.100 align:start position:0% you can do containers on VMs definition and<00:29:03.370> distribution<00:29:03.549> of<00:29:03.820> these<00:29:03.970> you<00:29:04.510> can<00:29:04.899> think 00:29:05.100 --> 00:29:05.110 align:start position:0% and distribution of these you can think 00:29:05.110 --> 00:29:07.590 align:start position:0% and distribution of these you can think of<00:29:05.200> these<00:29:05.320> as<00:29:05.440> like<00:29:05.679> merkel<00:29:06.159> containers<00:29:06.600> where 00:29:07.590 --> 00:29:07.600 align:start position:0% of these as like merkel containers where 00:29:07.600 --> 00:29:10.740 align:start position:0% of these as like merkel containers where like<00:29:08.190> the<00:29:09.190> entire<00:29:09.610> application<00:29:09.820> and<00:29:10.539> like<00:29:10.659> the 00:29:10.740 --> 00:29:10.750 align:start position:0% like the entire application and like the 00:29:10.750 --> 00:29:12.630 align:start position:0% like the entire application and like the graph<00:29:10.960> is<00:29:11.200> defined<00:29:11.350> as<00:29:11.710> a<00:29:11.860> proper<00:29:12.340> Merkel 00:29:12.630 --> 00:29:12.640 align:start position:0% graph is defined as a proper Merkel 00:29:12.640 --> 00:29:15.389 align:start position:0% graph is defined as a proper Merkel Merkel<00:29:13.029> graph<00:29:14.039> we<00:29:15.039> should<00:29:15.159> have<00:29:15.250> been<00:29:15.340> the 00:29:15.389 --> 00:29:15.399 align:start position:0% Merkel graph we should have been the 00:29:15.399 --> 00:29:16.980 align:start position:0% Merkel graph we should have been the case<00:29:15.520> from<00:29:15.640> the<00:29:15.760> beginning<00:29:16.000> but<00:29:16.210> anyway<00:29:16.570> you 00:29:16.980 --> 00:29:16.990 align:start position:0% case from the beginning but anyway you 00:29:16.990 --> 00:29:18.750 align:start position:0% case from the beginning but anyway you can<00:29:17.140> do<00:29:17.590> whole<00:29:17.890> package<00:29:18.159> managers<00:29:18.580> and 00:29:18.750 --> 00:29:18.760 align:start position:0% can do whole package managers and 00:29:18.760 --> 00:29:20.010 align:start position:0% can do whole package managers and distribute<00:29:19.090> of<00:29:19.149> them<00:29:19.240> this<00:29:19.419> way<00:29:19.570> so<00:29:19.630> we're 00:29:20.010 --> 00:29:20.020 align:start position:0% distribute of them this way so we're 00:29:20.020 --> 00:29:22.049 align:start position:0% distribute of them this way so we're already<00:29:20.140> working<00:29:20.409> on<00:29:20.830> doing<00:29:21.490> this<00:29:21.700> to<00:29:21.880> several 00:29:22.049 --> 00:29:22.059 align:start position:0% already working on doing this to several 00:29:22.059 --> 00:29:24.659 align:start position:0% already working on doing this to several of<00:29:22.510> these<00:29:22.659> package<00:29:22.990> managers<00:29:23.380> we're<00:29:24.309> taking 00:29:24.659 --> 00:29:24.669 align:start position:0% of these package managers we're taking 00:29:24.669 --> 00:29:26.510 align:start position:0% of these package managers we're taking all<00:29:24.940> of<00:29:25.000> the<00:29:25.270> code<00:29:25.480> or<00:29:25.690> all<00:29:25.809> the<00:29:26.049> actual 00:29:26.510 --> 00:29:26.520 align:start position:0% all of the code or all the actual 00:29:26.520 --> 00:29:28.860 align:start position:0% all of the code or all the actual compiled<00:29:27.520> binaries<00:29:28.029> and<00:29:28.270> adding<00:29:28.630> them<00:29:28.750> to 00:29:28.860 --> 00:29:28.870 align:start position:0% compiled binaries and adding them to 00:29:28.870 --> 00:29:31.200 align:start position:0% compiled binaries and adding them to ipfs<00:29:29.289> usually<00:29:30.070> first<00:29:30.520> of<00:29:30.640> all<00:29:30.730> you<00:29:30.820> get<00:29:30.909> a<00:29:30.970> huge 00:29:31.200 --> 00:29:31.210 align:start position:0% ipfs usually first of all you get a huge 00:29:31.210 --> 00:29:32.820 align:start position:0% ipfs usually first of all you get a huge space<00:29:31.510> savings<00:29:31.840> because<00:29:32.140> tons<00:29:32.529> of<00:29:32.620> stuff<00:29:32.740> is 00:29:32.820 --> 00:29:32.830 align:start position:0% space savings because tons of stuff is 00:29:32.830 --> 00:29:34.950 align:start position:0% space savings because tons of stuff is duplicated<00:29:33.309> but<00:29:33.789> then<00:29:33.909> you<00:29:34.059> also<00:29:34.240> get<00:29:34.480> get<00:29:34.899> to 00:29:34.950 --> 00:29:34.960 align:start position:0% duplicated but then you also get get to 00:29:34.960 --> 00:29:36.990 align:start position:0% duplicated but then you also get get to distribute<00:29:35.470> them<00:29:35.620> faster<00:29:36.549> because<00:29:36.850> if 00:29:36.990 --> 00:29:37.000 align:start position:0% distribute them faster because if 00:29:37.000 --> 00:29:38.730 align:start position:0% distribute them faster because if machines<00:29:37.419> in<00:29:37.539> the<00:29:37.600> same<00:29:37.750> data<00:29:38.140> center<00:29:38.169> have<00:29:38.590> it 00:29:38.730 --> 00:29:38.740 align:start position:0% machines in the same data center have it 00:29:38.740 --> 00:29:41.639 align:start position:0% machines in the same data center have it then<00:29:38.980> things<00:29:39.880> move<00:29:40.059> faster<00:29:40.360> key<00:29:41.289> addressing 00:29:41.639 --> 00:29:41.649 align:start position:0% then things move faster key addressing 00:29:41.649 --> 00:29:43.289 align:start position:0% then things move faster key addressing archiving<00:29:42.159> backup<00:29:42.669> everything<00:29:42.970> people<00:29:43.120> are 00:29:43.289 --> 00:29:43.299 align:start position:0% archiving backup everything people are 00:29:43.299 --> 00:29:46.380 align:start position:0% archiving backup everything people are like<00:29:43.450> archiving<00:29:44.020> all<00:29:44.110> that<00:29:44.340> stuff<00:29:45.340> all<00:29:46.179> these 00:29:46.380 --> 00:29:46.390 align:start position:0% like archiving all that stuff all these 00:29:46.390 --> 00:29:48.120 align:start position:0% like archiving all that stuff all these cut<00:29:46.600> a<00:29:46.870> whole<00:29:47.200> bunch<00:29:47.350> of<00:29:47.409> the<00:29:47.500> data<00:29:47.649> here<00:29:47.950> you 00:29:48.120 --> 00:29:48.130 align:start position:0% cut a whole bunch of the data here you 00:29:48.130 --> 00:29:49.680 align:start position:0% cut a whole bunch of the data here you can<00:29:48.279> archive<00:29:48.669> what<00:29:48.820> ipfs<00:29:49.179> and<00:29:49.390> there's 00:29:49.680 --> 00:29:49.690 align:start position:0% can archive what ipfs and there's 00:29:49.690 --> 00:29:52.260 align:start position:0% can archive what ipfs and there's efforts<00:29:49.960> on<00:29:50.350> this<00:29:50.640> now<00:29:51.640> when<00:29:51.880> it<00:29:51.970> comes<00:29:52.029> to<00:29:52.179> the 00:29:52.260 --> 00:29:52.270 align:start position:0% efforts on this now when it comes to the 00:29:52.270 --> 00:29:53.909 align:start position:0% efforts on this now when it comes to the etherium<00:29:52.659> and<00:29:52.870> this<00:29:53.289> is<00:29:53.409> like<00:29:53.529> the<00:29:53.620> last<00:29:53.770> line 00:29:53.909 --> 00:29:53.919 align:start position:0% etherium and this is like the last line 00:29:53.919 --> 00:29:55.860 align:start position:0% etherium and this is like the last line I<00:29:53.950> promise<00:29:54.309> when<00:29:55.000> it<00:29:55.090> comes<00:29:55.240> to<00:29:55.330> theorem<00:29:55.659> and 00:29:55.860 --> 00:29:55.870 align:start position:0% I promise when it comes to theorem and 00:29:55.870 --> 00:29:57.720 align:start position:0% I promise when it comes to theorem and by<00:29:56.110> the<00:29:56.169> way<00:29:56.289> the<00:29:56.409> logos<00:29:57.010> fit<00:29:57.250> really<00:29:57.460> nicely 00:29:57.720 --> 00:29:57.730 align:start position:0% by the way the logos fit really nicely 00:29:57.730 --> 00:30:00.840 align:start position:0% by the way the logos fit really nicely together<00:29:57.970> it's<00:29:58.510> fine<00:29:58.690> too 00:30:00.840 --> 00:30:00.850 align:start position:0% together it's fine too 00:30:00.850 --> 00:30:03.720 align:start position:0% together it's fine too so<00:30:01.330> so<00:30:01.960> you<00:30:02.440> can<00:30:02.470> use<00:30:02.799> it<00:30:02.950> for<00:30:03.070> alkane<00:30:03.490> data 00:30:03.720 --> 00:30:03.730 align:start position:0% so so you can use it for alkane data 00:30:03.730 --> 00:30:05.970 align:start position:0% so so you can use it for alkane data right<00:30:04.029> so<00:30:04.120> you<00:30:04.210> can<00:30:04.360> the<00:30:05.200> very<00:30:05.409> first<00:30:05.679> thing 00:30:05.970 --> 00:30:05.980 align:start position:0% right so you can the very first thing 00:30:05.980 --> 00:30:07.799 align:start position:0% right so you can the very first thing that<00:30:06.130> you<00:30:06.190> can<00:30:06.220> think<00:30:06.399> of<00:30:06.549> is<00:30:06.700> like<00:30:06.820> anything 00:30:07.799 --> 00:30:07.809 align:start position:0% that you can think of is like anything 00:30:07.809 --> 00:30:09.000 align:start position:0% that you can think of is like anything that<00:30:07.960> just<00:30:08.110> shouldn't<00:30:08.440> be<00:30:08.649> on<00:30:08.740> the<00:30:08.799> blockchain 00:30:09.000 --> 00:30:09.010 align:start position:0% that just shouldn't be on the blockchain 00:30:09.010 --> 00:30:10.580 align:start position:0% that just shouldn't be on the blockchain because<00:30:09.340> it's<00:30:09.490> too<00:30:09.640> big 00:30:10.580 --> 00:30:10.590 align:start position:0% because it's too big 00:30:10.590 --> 00:30:13.110 align:start position:0% because it's too big put<00:30:11.590> a<00:30:11.620> put<00:30:11.890> it<00:30:11.950> on<00:30:12.039> ipfs<00:30:12.370> take<00:30:12.580> a<00:30:12.610> link<00:30:12.880> and 00:30:13.110 --> 00:30:13.120 align:start position:0% put a put it on ipfs take a link and 00:30:13.120 --> 00:30:15.299 align:start position:0% put a put it on ipfs take a link and then<00:30:13.539> serve<00:30:14.020> that<00:30:14.260> link<00:30:14.500> with<00:30:14.740> your<00:30:14.950> own<00:30:15.070> note 00:30:15.299 --> 00:30:15.309 align:start position:0% then serve that link with your own note 00:30:15.309 --> 00:30:16.860 align:start position:0% then serve that link with your own note but<00:30:15.549> that<00:30:15.640> means<00:30:15.820> that<00:30:16.029> anybody<00:30:16.270> else<00:30:16.570> can 00:30:16.860 --> 00:30:16.870 align:start position:0% but that means that anybody else can 00:30:16.870 --> 00:30:18.870 align:start position:0% but that means that anybody else can serve<00:30:17.289> it<00:30:17.409> as<00:30:17.500> well<00:30:17.710> and<00:30:17.919> it<00:30:18.279> means<00:30:18.429> that<00:30:18.640> you 00:30:18.870 --> 00:30:18.880 align:start position:0% serve it as well and it means that you 00:30:18.880 --> 00:30:21.299 align:start position:0% serve it as well and it means that you can<00:30:19.029> disappear<00:30:19.450> and<00:30:19.659> the<00:30:20.620> content<00:30:21.190> doesn't 00:30:21.299 --> 00:30:21.309 align:start position:0% can disappear and the content doesn't 00:30:21.309 --> 00:30:24.960 align:start position:0% can disappear and the content doesn't disappear<00:30:21.669> right<00:30:22.799> so<00:30:23.799> you<00:30:24.100> know<00:30:24.190> big<00:30:24.789> stuff 00:30:24.960 --> 00:30:24.970 align:start position:0% disappear right so you know big stuff 00:30:24.970 --> 00:30:27.360 align:start position:0% disappear right so you know big stuff you<00:30:25.720> can<00:30:26.049> use<00:30:26.230> them<00:30:26.409> again<00:30:26.559> to<00:30:26.980> define<00:30:27.220> and 00:30:27.360 --> 00:30:27.370 align:start position:0% you can use them again to define and 00:30:27.370 --> 00:30:29.070 align:start position:0% you can use them again to define and distribute<00:30:27.700> these<00:30:27.820> to<00:30:28.330> distribute<00:30:28.929> apps 00:30:29.070 --> 00:30:29.080 align:start position:0% distribute these to distribute apps 00:30:29.080 --> 00:30:30.690 align:start position:0% distribute these to distribute apps right<00:30:29.409> so<00:30:29.590> these<00:30:29.740> these<00:30:29.980> centralized 00:30:30.690 --> 00:30:30.700 align:start position:0% right so these these centralized 00:30:30.700 --> 00:30:32.399 align:start position:0% right so these these centralized distribute<00:30:31.120> applications<00:30:31.600> you<00:30:32.080> can<00:30:32.200> write 00:30:32.399 --> 00:30:32.409 align:start position:0% distribute applications you can write 00:30:32.409 --> 00:30:34.080 align:start position:0% distribute applications you can write them<00:30:32.559> put<00:30:33.190> them<00:30:33.309> on<00:30:33.370> a<00:30:33.460> fast<00:30:33.760> put<00:30:33.909> all<00:30:34.000> the 00:30:34.080 --> 00:30:34.090 align:start position:0% them put them on a fast put all the 00:30:34.090 --> 00:30:35.250 align:start position:0% them put them on a fast put all the assets<00:30:34.360> there<00:30:34.510> people<00:30:34.750> are<00:30:34.840> already<00:30:35.080> doing 00:30:35.250 --> 00:30:35.260 align:start position:0% assets there people are already doing 00:30:35.260 --> 00:30:38.310 align:start position:0% assets there people are already doing this<00:30:35.440> and<00:30:36.399> so<00:30:36.640> on<00:30:36.750> so<00:30:37.750> you<00:30:37.780> have<00:30:37.929> the<00:30:38.020> code<00:30:38.200> and 00:30:38.310 --> 00:30:38.320 align:start position:0% this and so on so you have the code and 00:30:38.320 --> 00:30:39.570 align:start position:0% this and so on so you have the code and the<00:30:38.409> assets<00:30:38.710> and<00:30:38.830> everything<00:30:39.130> but<00:30:39.280> also<00:30:39.429> the 00:30:39.570 --> 00:30:39.580 align:start position:0% the assets and everything but also the 00:30:39.580 --> 00:30:42.270 align:start position:0% the assets and everything but also the users<00:30:39.880> data<00:30:40.380> this<00:30:41.380> is<00:30:41.530> an<00:30:41.649> example<00:30:41.890> of<00:30:42.010> one<00:30:42.190> of 00:30:42.270 --> 00:30:42.280 align:start position:0% users data this is an example of one of 00:30:42.280 --> 00:30:44.340 align:start position:0% users data this is an example of one of them<00:30:42.370> this<00:30:42.610> is<00:30:42.730> ours<00:30:43.059> it's<00:30:43.330> our<00:30:43.480> web<00:30:43.659> UI<00:30:43.899> for<00:30:44.169> an 00:30:44.340 --> 00:30:44.350 align:start position:0% them this is ours it's our web UI for an 00:30:44.350 --> 00:30:47.549 align:start position:0% them this is ours it's our web UI for an IP<00:30:44.530> FS<00:30:44.710> node<00:30:45.659> all<00:30:46.659> of<00:30:46.899> the<00:30:46.990> code<00:30:47.140> for<00:30:47.289> this<00:30:47.409> is 00:30:47.549 --> 00:30:47.559 align:start position:0% IP FS node all of the code for this is 00:30:47.559 --> 00:30:49.919 align:start position:0% IP FS node all of the code for this is when<00:30:47.649> ipfs<00:30:48.039> you<00:30:48.610> pull<00:30:48.909> it<00:30:49.030> out<00:30:49.149> you<00:30:49.330> run<00:30:49.480> it<00:30:49.630> and 00:30:49.919 --> 00:30:49.929 align:start position:0% when ipfs you pull it out you run it and 00:30:49.929 --> 00:30:54.210 align:start position:0% when ipfs you pull it out you run it and it's<00:30:50.260> completely<00:30:50.620> distributed<00:30:51.610> so<00:30:51.880> like<00:30:53.220> all 00:30:54.210 --> 00:30:54.220 align:start position:0% it's completely distributed so like all 00:30:54.220 --> 00:30:56.250 align:start position:0% it's completely distributed so like all it's<00:30:55.120> a<00:30:55.240> very<00:30:55.270> cool<00:30:55.539> experience<00:30:55.659> when<00:30:56.110> you<00:30:56.169> do 00:30:56.250 --> 00:30:56.260 align:start position:0% it's a very cool experience when you do 00:30:56.260 --> 00:30:58.169 align:start position:0% it's a very cool experience when you do is<00:30:56.380> me<00:30:56.500> like<00:30:56.649> whoa<00:30:56.799> not<00:30:57.250> touching<00:30:57.610> what<00:30:57.970> server 00:30:58.169 --> 00:30:58.179 align:start position:0% is me like whoa not touching what server 00:30:58.179 --> 00:31:00.419 align:start position:0% is me like whoa not touching what server ever<00:30:58.450> like<00:30:58.929> it<00:30:59.110> just<00:30:59.440> my<00:30:59.590> browser<00:30:59.799> does<00:31:00.309> it 00:31:00.419 --> 00:31:00.429 align:start position:0% ever like it just my browser does it 00:31:00.429 --> 00:31:02.220 align:start position:0% ever like it just my browser does it here<00:31:00.909> swamped<00:31:01.240> ran<00:31:01.390> an<00:31:01.539> example<00:31:01.870> of<00:31:02.020> like<00:31:02.169> a 00:31:02.220 --> 00:31:02.230 align:start position:0% here swamped ran an example of like a 00:31:02.230 --> 00:31:04.820 align:start position:0% here swamped ran an example of like a like<00:31:02.620> a<00:31:02.649> B<00:31:02.980> style<00:31:03.280> a<00:31:03.549> four<00:31:04.090> times<00:31:04.240> outboard 00:31:04.820 --> 00:31:04.830 align:start position:0% like a B style a four times outboard 00:31:04.830 --> 00:31:07.110 align:start position:0% like a B style a four times outboard done<00:31:05.830> with<00:31:05.950> Ikea<00:31:06.159> pheasant<00:31:06.399> etherium<00:31:06.760> so<00:31:07.030> you 00:31:07.110 --> 00:31:07.120 align:start position:0% done with Ikea pheasant etherium so you 00:31:07.120 --> 00:31:11.250 align:start position:0% done with Ikea pheasant etherium so you actually<00:31:07.390> pay<00:31:07.510> ether<00:31:07.899> to<00:31:08.110> be<00:31:08.230> able<00:31:08.289> to<00:31:08.409> post<00:31:10.260> so 00:31:11.250 --> 00:31:11.260 align:start position:0% actually pay ether to be able to post so 00:31:11.260 --> 00:31:12.570 align:start position:0% actually pay ether to be able to post so you<00:31:11.500> could<00:31:11.620> do<00:31:11.710> the<00:31:11.799> trunk<00:31:11.980> base<00:31:12.100> for<00:31:12.309> just 00:31:12.570 --> 00:31:12.580 align:start position:0% you could do the trunk base for just 00:31:12.580 --> 00:31:15.029 align:start position:0% you could do the trunk base for just formless<00:31:12.970> pointing<00:31:13.270> out<00:31:13.390> that<00:31:13.539> and<00:31:14.230> you<00:31:14.919> can 00:31:15.029 --> 00:31:15.039 align:start position:0% formless pointing out that and you can 00:31:15.039 --> 00:31:17.820 align:start position:0% formless pointing out that and you can do<00:31:15.159> the<00:31:15.640> two<00:31:16.299> interesting<00:31:16.750> things<00:31:16.780> here<00:31:17.200> and 00:31:17.820 --> 00:31:17.830 align:start position:0% do the two interesting things here and 00:31:17.830 --> 00:31:20.039 align:start position:0% do the two interesting things here and sort<00:31:18.190> of<00:31:18.250> London<00:31:18.789> stuck<00:31:18.970> this<00:31:19.090> way<00:31:19.270> that<00:31:19.929> the 00:31:20.039 --> 00:31:20.049 align:start position:0% sort of London stuck this way that the 00:31:20.049 --> 00:31:22.440 align:start position:0% sort of London stuck this way that the most<00:31:20.230> interesting<00:31:20.440> things<00:31:20.860> where<00:31:21.250> where<00:31:21.610> i<00:31:21.970> p 00:31:22.440 --> 00:31:22.450 align:start position:0% most interesting things where where i p 00:31:22.450 --> 00:31:24.419 align:start position:0% most interesting things where where i p FS<00:31:22.690> could<00:31:22.899> be<00:31:22.960> useful<00:31:23.289> for<00:31:23.470> aetherium<00:31:23.770> and<00:31:24.100> i 00:31:24.419 --> 00:31:24.429 align:start position:0% FS could be useful for aetherium and i 00:31:24.429 --> 00:31:26.430 align:start position:0% FS could be useful for aetherium and i worth<00:31:24.690> investigating<00:31:25.690> carefully<00:31:26.200> is 00:31:26.430 --> 00:31:26.440 align:start position:0% worth investigating carefully is 00:31:26.440 --> 00:31:28.500 align:start position:0% worth investigating carefully is representing<00:31:27.340> the<00:31:27.460> entire<00:31:27.580> merkel<00:31:28.240> patricia 00:31:28.500 --> 00:31:28.510 align:start position:0% representing the entire merkel patricia 00:31:28.510 --> 00:31:31.710 align:start position:0% representing the entire merkel patricia 3<00:31:28.750> state<00:31:29.289> s<00:31:30.070> ipfs<00:31:30.580> notes<00:31:30.820> so<00:31:31.120> that<00:31:31.270> you<00:31:31.360> are 00:31:31.710 --> 00:31:31.720 align:start position:0% 3 state s ipfs notes so that you are 00:31:31.720 --> 00:31:33.930 align:start position:0% 3 state s ipfs notes so that you are able<00:31:31.780> to<00:31:32.020> directly<00:31:32.710> index<00:31:33.190> into<00:31:33.610> the<00:31:33.730> state 00:31:33.930 --> 00:31:33.940 align:start position:0% able to directly index into the state 00:31:33.940 --> 00:31:36.779 align:start position:0% able to directly index into the state tree<00:31:34.149> and<00:31:34.330> pull<00:31:34.510> things<00:31:34.630> out<00:31:34.870> and<00:31:35.740> and<00:31:36.399> use<00:31:36.760> a 00:31:36.779 --> 00:31:36.789 align:start position:0% tree and pull things out and and use a 00:31:36.789 --> 00:31:38.610 align:start position:0% tree and pull things out and and use a bunch<00:31:37.120> of<00:31:37.179> ipfs<00:31:37.570> nodes<00:31:37.780> that<00:31:37.929> may<00:31:38.049> not<00:31:38.230> speak 00:31:38.610 --> 00:31:38.620 align:start position:0% bunch of ipfs nodes that may not speak 00:31:38.620 --> 00:31:40.680 align:start position:0% bunch of ipfs nodes that may not speak aetherium<00:31:39.010> yet<00:31:39.280> but<00:31:39.460> they<00:31:39.549> speak<00:31:39.730> ipfs<00:31:40.179> you 00:31:40.680 --> 00:31:40.690 align:start position:0% aetherium yet but they speak ipfs you 00:31:40.690 --> 00:31:41.899 align:start position:0% aetherium yet but they speak ipfs you can<00:31:40.870> then<00:31:41.020> start<00:31:41.200> addressing 00:31:41.899 --> 00:31:41.909 align:start position:0% can then start addressing 00:31:41.909 --> 00:31:44.940 align:start position:0% can then start addressing etherium<00:31:42.909> state<00:31:43.179> with<00:31:43.780> them<00:31:44.020> and<00:31:44.230> use<00:31:44.649> them<00:31:44.830> to 00:31:44.940 --> 00:31:44.950 align:start position:0% etherium state with them and use them to 00:31:44.950 --> 00:31:46.200 align:start position:0% etherium state with them and use them to move<00:31:45.039> around<00:31:45.159> the<00:31:45.340> theorem<00:31:45.610> state<00:31:45.820> it's<00:31:46.090> just 00:31:46.200 --> 00:31:46.210 align:start position:0% move around the theorem state it's just 00:31:46.210 --> 00:31:47.909 align:start position:0% move around the theorem state it's just really<00:31:46.330> cool<00:31:46.510> and<00:31:46.780> you<00:31:47.409> can<00:31:47.440> do<00:31:47.620> that<00:31:47.710> to<00:31:47.830> the 00:31:47.909 --> 00:31:47.919 align:start position:0% really cool and you can do that to the 00:31:47.919 --> 00:31:50.279 align:start position:0% really cool and you can do that to the blockchain<00:31:48.130> itself<00:31:48.899> you<00:31:49.899> can<00:31:50.020> take<00:31:50.169> the 00:31:50.279 --> 00:31:50.289 align:start position:0% blockchain itself you can take the 00:31:50.289 --> 00:31:52.169 align:start position:0% blockchain itself you can take the entire<00:31:50.559> definition<00:31:51.340> of<00:31:51.580> the<00:31:51.639> blockchain<00:31:51.850> and 00:31:52.169 --> 00:31:52.179 align:start position:0% entire definition of the blockchain and 00:31:52.179 --> 00:31:54.270 align:start position:0% entire definition of the blockchain and just<00:31:52.480> like<00:31:52.600> imported<00:31:52.960> into<00:31:53.230> ipfs<00:31:53.649> and<00:31:53.919> then 00:31:54.270 --> 00:31:54.280 align:start position:0% just like imported into ipfs and then 00:31:54.280 --> 00:31:56.730 align:start position:0% just like imported into ipfs and then distribute<00:31:54.760> all<00:31:54.850> the<00:31:54.909> content<00:31:55.240> this<00:31:55.330> way<00:31:55.740> and 00:31:56.730 --> 00:31:56.740 align:start position:0% distribute all the content this way and 00:31:56.740 --> 00:31:59.700 align:start position:0% distribute all the content this way and so<00:31:57.460> the<00:31:57.580> this<00:31:57.909> is<00:31:58.059> a<00:31:58.149> blog<00:31:58.389> post<00:31:58.570> from<00:31:58.750> chris 00:31:59.700 --> 00:31:59.710 align:start position:0% so the this is a blog post from chris 00:31:59.710 --> 00:32:01.350 align:start position:0% so the this is a blog post from chris that<00:31:59.860> talks<00:32:00.159> a<00:32:00.220> little<00:32:00.340> bit<00:32:00.460> about<00:32:00.549> this<00:32:00.789> very 00:32:01.350 --> 00:32:01.360 align:start position:0% that talks a little bit about this very 00:32:01.360 --> 00:32:03.750 align:start position:0% that talks a little bit about this very cool<00:32:01.539> so<00:32:01.720> check<00:32:01.990> it<00:32:02.080> out<00:32:02.139> all<00:32:02.889> right<00:32:02.950> so<00:32:03.370> that's 00:32:03.750 --> 00:32:03.760 align:start position:0% cool so check it out all right so that's 00:32:03.760 --> 00:32:06.240 align:start position:0% cool so check it out all right so that's Ivan<00:32:04.120> cousin<00:32:04.360> did<00:32:04.480> it<00:32:04.570> Dan<00:32:04.870> instructors<00:32:05.440> thank 00:32:06.240 --> 00:32:06.250 align:start position:0% Ivan cousin did it Dan instructors thank 00:32:06.250 --> 00:32:08.370 align:start position:0% Ivan cousin did it Dan instructors thank you