WEBVTT Kind: captions Language: en 00:00:18.580 --> 00:00:21.490 align:start position:0% hello<00:00:19.580> everyone<00:00:19.970> this<00:00:20.180> talk<00:00:20.870> is<00:00:21.140> aimed 00:00:21.490 --> 00:00:21.500 align:start position:0% hello everyone this talk is aimed 00:00:21.500 --> 00:00:25.000 align:start position:0% hello everyone this talk is aimed primarily<00:00:22.160> at<00:00:23.110> application<00:00:24.110> developers<00:00:24.650> and 00:00:25.000 --> 00:00:25.010 align:start position:0% primarily at application developers and 00:00:25.010 --> 00:00:27.790 align:start position:0% primarily at application developers and I<00:00:25.520> would<00:00:25.670> like<00:00:25.880> to<00:00:25.910> give<00:00:26.270> a<00:00:26.540> quick<00:00:26.570> overview<00:00:27.050> of 00:00:27.790 --> 00:00:27.800 align:start position:0% I would like to give a quick overview of 00:00:27.800 --> 00:00:30.999 align:start position:0% I would like to give a quick overview of the<00:00:28.760> architectural<00:00:29.600> considerations<00:00:30.529> behind 00:00:30.999 --> 00:00:31.009 align:start position:0% the architectural considerations behind 00:00:31.009 --> 00:00:34.510 align:start position:0% the architectural considerations behind developing<00:00:32.860> decentralized<00:00:33.860> applications 00:00:34.510 --> 00:00:34.520 align:start position:0% developing decentralized applications 00:00:34.520 --> 00:00:40.270 align:start position:0% developing decentralized applications for<00:00:34.880> aetherium<00:00:35.750> on<00:00:36.050> top<00:00:36.260> of<00:00:36.380> s'more<00:00:37.600> so<00:00:39.280> what's 00:00:40.270 --> 00:00:40.280 align:start position:0% for aetherium on top of s'more so what's 00:00:40.280 --> 00:00:42.460 align:start position:0% for aetherium on top of s'more so what's wrong<00:00:40.640> with<00:00:40.880> the<00:00:41.090> web<00:00:41.239> to<00:00:41.480> model<00:00:41.900> well 00:00:42.460 --> 00:00:42.470 align:start position:0% wrong with the web to model well 00:00:42.470 --> 00:00:45.250 align:start position:0% wrong with the web to model well yesterday<00:00:43.400> we<00:00:43.940> have<00:00:44.060> already<00:00:44.360> heard<00:00:44.630> that<00:00:44.989> the 00:00:45.250 --> 00:00:45.260 align:start position:0% yesterday we have already heard that the 00:00:45.260 --> 00:00:48.100 align:start position:0% yesterday we have already heard that the web<00:00:45.410> is<00:00:45.440> kind<00:00:45.860> of<00:00:46.010> broken<00:00:46.360> so<00:00:47.360> it<00:00:47.600> has<00:00:47.840> these 00:00:48.100 --> 00:00:48.110 align:start position:0% web is kind of broken so it has these 00:00:48.110 --> 00:00:50.230 align:start position:0% web is kind of broken so it has these problems<00:00:48.800> that<00:00:49.070> you<00:00:49.280> have<00:00:49.430> a<00:00:49.460> centralized 00:00:50.230 --> 00:00:50.240 align:start position:0% problems that you have a centralized 00:00:50.240 --> 00:00:53.440 align:start position:0% problems that you have a centralized trust<00:00:51.080> management<00:00:51.320> based<00:00:52.070> on<00:00:52.450> certification 00:00:53.440 --> 00:00:53.450 align:start position:0% trust management based on certification 00:00:53.450 --> 00:00:55.930 align:start position:0% trust management based on certification authorities<00:00:54.110> you<00:00:54.950> cannot<00:00:55.340> really<00:00:55.640> trust 00:00:55.930 --> 00:00:55.940 align:start position:0% authorities you cannot really trust 00:00:55.940 --> 00:01:02.050 align:start position:0% authorities you cannot really trust content<00:00:56.600> delivery<00:00:56.960> networks<00:00:57.530> and<00:01:00.610> so<00:01:01.610> there's 00:01:02.050 --> 00:01:02.060 align:start position:0% content delivery networks and so there's 00:01:02.060 --> 00:01:07.300 align:start position:0% content delivery networks and so there's this<00:01:02.600> other<00:01:02.840> problem<00:01:03.260> that<00:01:03.830> scaling<00:01:04.400> is<00:01:06.310> so 00:01:07.300 --> 00:01:07.310 align:start position:0% this other problem that scaling is so 00:01:07.310 --> 00:01:10.020 align:start position:0% this other problem that scaling is so it's<00:01:07.549> buying<00:01:07.970> more<00:01:08.540> power<00:01:08.960> from<00:01:09.560> data<00:01:09.830> centers 00:01:10.020 --> 00:01:10.030 align:start position:0% it's buying more power from data centers 00:01:10.030 --> 00:01:13.149 align:start position:0% it's buying more power from data centers by<00:01:11.030> the<00:01:11.350> person<00:01:12.350> who<00:01:12.500> provides<00:01:12.890> the 00:01:13.149 --> 00:01:13.159 align:start position:0% by the person who provides the 00:01:13.159 --> 00:01:15.550 align:start position:0% by the person who provides the application<00:01:13.880> whereas<00:01:14.299> demand<00:01:14.780> is<00:01:14.990> just<00:01:15.290> users 00:01:15.550 --> 00:01:15.560 align:start position:0% application whereas demand is just users 00:01:15.560 --> 00:01:18.190 align:start position:0% application whereas demand is just users pounding<00:01:16.310> it<00:01:16.549> and<00:01:16.729> there<00:01:17.150> all<00:01:17.299> sorts<00:01:17.720> of<00:01:17.900> like 00:01:18.190 --> 00:01:18.200 align:start position:0% pounding it and there all sorts of like 00:01:18.200 --> 00:01:20.950 align:start position:0% pounding it and there all sorts of like elastic<00:01:18.619> solutions<00:01:19.430> but<00:01:20.000> none<00:01:20.240> of<00:01:20.270> them<00:01:20.630> so 00:01:20.950 --> 00:01:20.960 align:start position:0% elastic solutions but none of them so 00:01:20.960 --> 00:01:23.320 align:start position:0% elastic solutions but none of them so they're<00:01:21.560> ugly<00:01:21.920> they're<00:01:22.580> just<00:01:22.970> a<00:01:23.090> hairy 00:01:23.320 --> 00:01:23.330 align:start position:0% they're ugly they're just a hairy 00:01:23.330 --> 00:01:25.780 align:start position:0% they're ugly they're just a hairy solution<00:01:23.990> to<00:01:24.409> providing<00:01:24.830> more<00:01:25.070> computing 00:01:25.780 --> 00:01:25.790 align:start position:0% solution to providing more computing 00:01:25.790 --> 00:01:28.270 align:start position:0% solution to providing more computing power<00:01:26.060> as<00:01:26.390> you<00:01:26.690> have<00:01:27.050> more<00:01:27.290> clients<00:01:27.590> even 00:01:28.270 --> 00:01:28.280 align:start position:0% power as you have more clients even 00:01:28.280 --> 00:01:30.280 align:start position:0% power as you have more clients even though<00:01:28.730> there's<00:01:29.060> this<00:01:29.120> natural<00:01:29.480> thing<00:01:30.050> that 00:01:30.280 --> 00:01:30.290 align:start position:0% though there's this natural thing that 00:01:30.290 --> 00:01:32.560 align:start position:0% though there's this natural thing that every<00:01:30.590> client<00:01:31.040> who<00:01:31.220> comes<00:01:31.520> they<00:01:32.150> come<00:01:32.390> with<00:01:32.540> a 00:01:32.560 --> 00:01:32.570 align:start position:0% every client who comes they come with a 00:01:32.570 --> 00:01:36.190 align:start position:0% every client who comes they come with a computer<00:01:33.110> that<00:01:33.409> could<00:01:33.620> just<00:01:33.890> be<00:01:33.979> used<00:01:34.550> so<00:01:35.390> it 00:01:36.190 --> 00:01:36.200 align:start position:0% computer that could just be used so it 00:01:36.200 --> 00:01:38.140 align:start position:0% computer that could just be used so it would<00:01:36.500> be<00:01:36.650> really<00:01:36.860> natural<00:01:37.159> to<00:01:37.760> scale 00:01:38.140 --> 00:01:38.150 align:start position:0% would be really natural to scale 00:01:38.150 --> 00:01:41.260 align:start position:0% would be really natural to scale computing<00:01:38.930> power<00:01:39.200> by<00:01:40.040> using<00:01:40.550> the<00:01:40.940> actual 00:01:41.260 --> 00:01:41.270 align:start position:0% computing power by using the actual 00:01:41.270 --> 00:01:46.170 align:start position:0% computing power by using the actual computers<00:01:41.930> that<00:01:42.229> the<00:01:42.620> users<00:01:43.580> come<00:01:43.850> with<00:01:44.060> and 00:01:46.170 --> 00:01:46.180 align:start position:0% computers that the users come with and 00:01:46.180 --> 00:01:52.060 align:start position:0% computers that the users come with and the<00:01:47.180> problem<00:01:47.600> however<00:01:47.780> is<00:01:48.080> that<00:01:50.409> so<00:01:51.409> trustless 00:01:52.060 --> 00:01:52.070 align:start position:0% the problem however is that so trustless 00:01:52.070 --> 00:01:54.490 align:start position:0% the problem however is that so trustless computing<00:01:52.760> it<00:01:53.000> comes<00:01:53.360> with<00:01:53.600> overhead<00:01:54.080> costs 00:01:54.490 --> 00:01:54.500 align:start position:0% computing it comes with overhead costs 00:01:54.500 --> 00:01:57.700 align:start position:0% computing it comes with overhead costs that<00:01:54.650> are<00:01:54.830> not<00:01:55.040> going<00:01:55.280> to<00:01:55.490> go<00:01:55.640> away<00:01:55.760> so<00:01:56.710> for 00:01:57.700 --> 00:01:57.710 align:start position:0% that are not going to go away so for 00:01:57.710 --> 00:02:00.850 align:start position:0% that are not going to go away so for example<00:01:58.280> if<00:01:58.490> you<00:01:58.790> are<00:01:58.820> trying<00:01:59.540> to<00:02:00.049> host<00:02:00.500> a 00:02:00.850 --> 00:02:00.860 align:start position:0% example if you are trying to host a 00:02:00.860 --> 00:02:04.000 align:start position:0% example if you are trying to host a number<00:02:01.520> of<00:02:01.729> movies<00:02:02.510> it<00:02:02.869> will<00:02:03.350> be<00:02:03.560> always 00:02:04.000 --> 00:02:04.010 align:start position:0% number of movies it will be always 00:02:04.010 --> 00:02:06.609 align:start position:0% number of movies it will be always cheaper<00:02:04.460> to<00:02:04.640> do<00:02:04.790> that<00:02:05.000> in<00:02:05.210> a<00:02:05.299> data<00:02:05.540> center<00:02:05.869> than 00:02:06.609 --> 00:02:06.619 align:start position:0% cheaper to do that in a data center than 00:02:06.619 --> 00:02:09.490 align:start position:0% cheaper to do that in a data center than to<00:02:06.830> do<00:02:07.040> it<00:02:07.070> on<00:02:07.490> a<00:02:07.850> trustless<00:02:08.360> network<00:02:08.869> so 00:02:09.490 --> 00:02:09.500 align:start position:0% to do it on a trustless network so 00:02:09.500 --> 00:02:10.990 align:start position:0% to do it on a trustless network so there's<00:02:09.679> always<00:02:09.920> going<00:02:10.220> to<00:02:10.310> be<00:02:10.369> an<00:02:10.519> overhead 00:02:10.990 --> 00:02:11.000 align:start position:0% there's always going to be an overhead 00:02:11.000 --> 00:02:13.979 align:start position:0% there's always going to be an overhead and<00:02:11.239> somebody<00:02:11.989> will<00:02:12.230> have<00:02:12.379> to<00:02:12.590> pay<00:02:12.769> for<00:02:13.040> it<00:02:13.189> and 00:02:13.979 --> 00:02:13.989 align:start position:0% and somebody will have to pay for it and 00:02:13.989 --> 00:02:17.559 align:start position:0% and somebody will have to pay for it and you<00:02:14.989> need<00:02:15.170> to<00:02:15.379> keep<00:02:15.830> that<00:02:16.069> in<00:02:16.280> mind<00:02:16.549> but<00:02:17.299> we're 00:02:17.559 --> 00:02:17.569 align:start position:0% you need to keep that in mind but we're 00:02:17.569 --> 00:02:20.619 align:start position:0% you need to keep that in mind but we're working<00:02:17.780> really<00:02:18.019> hard<00:02:18.319> to<00:02:18.739> reduce<00:02:18.920> that<00:02:19.629> that 00:02:20.619 --> 00:02:20.629 align:start position:0% working really hard to reduce that that 00:02:20.629 --> 00:02:24.010 align:start position:0% working really hard to reduce that that overhead<00:02:21.260> to<00:02:21.860> a<00:02:21.890> acceptable<00:02:22.819> level<00:02:23.300> so<00:02:23.990> that 00:02:24.010 --> 00:02:24.020 align:start position:0% overhead to a acceptable level so that 00:02:24.020 --> 00:02:26.770 align:start position:0% overhead to a acceptable level so that the<00:02:24.770> other<00:02:24.950> overheads<00:02:25.760> that<00:02:26.150> centralized 00:02:26.770 --> 00:02:26.780 align:start position:0% the other overheads that centralized 00:02:26.780 --> 00:02:27.520 align:start position:0% the other overheads that centralized solutions 00:02:27.520 --> 00:02:27.530 align:start position:0% solutions 00:02:27.530 --> 00:02:32.340 align:start position:0% solutions like<00:02:28.310> the<00:02:28.550> profits<00:02:29.060> of<00:02:30.700> unrelated<00:02:31.700> people 00:02:32.340 --> 00:02:32.350 align:start position:0% like the profits of unrelated people 00:02:32.350 --> 00:02:35.800 align:start position:0% like the profits of unrelated people they<00:02:33.350> will<00:02:33.680> be<00:02:33.740> comparable<00:02:34.730> or<00:02:35.030> maybe<00:02:35.420> even 00:02:35.800 --> 00:02:35.810 align:start position:0% they will be comparable or maybe even 00:02:35.810 --> 00:02:41.530 align:start position:0% they will be comparable or maybe even lower<00:02:36.310> so<00:02:38.980> so<00:02:39.980> how<00:02:40.160> do<00:02:40.220> we<00:02:40.370> get<00:02:40.610> from<00:02:40.880> web<00:02:41.090> to<00:02:41.120> to 00:02:41.530 --> 00:02:41.540 align:start position:0% lower so so how do we get from web to to 00:02:41.540 --> 00:02:47.320 align:start position:0% lower so so how do we get from web to to app<00:02:41.720> three<00:02:42.850> first<00:02:43.850> of<00:02:44.090> all<00:02:45.520> you<00:02:46.520> may<00:02:46.760> want<00:02:47.090> to 00:02:47.320 --> 00:02:47.330 align:start position:0% app three first of all you may want to 00:02:47.330 --> 00:02:50.590 align:start position:0% app three first of all you may want to dispose<00:02:48.140> with<00:02:48.440> the<00:02:48.620> notion<00:02:49.160> of<00:02:49.420> clients<00:02:50.420> and 00:02:50.590 --> 00:02:50.600 align:start position:0% dispose with the notion of clients and 00:02:50.600 --> 00:02:56.050 align:start position:0% dispose with the notion of clients and servers<00:02:51.070> so<00:02:52.070> for<00:02:52.790> now<00:02:53.800> aetherium<00:02:55.060> ecosystem 00:02:56.050 --> 00:02:56.060 align:start position:0% servers so for now aetherium ecosystem 00:02:56.060 --> 00:02:58.900 align:start position:0% servers so for now aetherium ecosystem the<00:02:56.209> app<00:02:56.330> dab<00:02:56.750> the<00:02:56.990> ecosystem<00:02:57.860> is<00:02:58.070> still<00:02:58.400> very 00:02:58.900 --> 00:02:58.910 align:start position:0% the app dab the ecosystem is still very 00:02:58.910 --> 00:03:01.870 align:start position:0% the app dab the ecosystem is still very reminiscent<00:02:59.750> of<00:03:00.320> the<00:03:00.590> old<00:03:00.890> ways<00:03:01.160> so<00:03:01.550> we<00:03:01.700> have 00:03:01.870 --> 00:03:01.880 align:start position:0% reminiscent of the old ways so we have 00:03:01.880 --> 00:03:04.720 align:start position:0% reminiscent of the old ways so we have the<00:03:02.120> nodes<00:03:02.420> and<00:03:02.750> we<00:03:02.870> have<00:03:03.020> the<00:03:03.200> clients<00:03:03.800> and<00:03:04.010> we 00:03:04.720 --> 00:03:04.730 align:start position:0% the nodes and we have the clients and we 00:03:04.730 --> 00:03:07.750 align:start position:0% the nodes and we have the clients and we have<00:03:04.910> these<00:03:05.360> things<00:03:05.720> like<00:03:05.989> meter<00:03:06.290> mask<00:03:06.620> and<00:03:06.980> it 00:03:07.750 --> 00:03:07.760 align:start position:0% have these things like meter mask and it 00:03:07.760 --> 00:03:10.300 align:start position:0% have these things like meter mask and it looks<00:03:08.060> like<00:03:08.239> we're<00:03:08.690> running<00:03:08.959> a<00:03:09.350> client-server 00:03:10.300 --> 00:03:10.310 align:start position:0% looks like we're running a client-server 00:03:10.310 --> 00:03:11.800 align:start position:0% looks like we're running a client-server network<00:03:10.790> but<00:03:11.030> really<00:03:11.330> it's<00:03:11.480> a<00:03:11.600> peer-to-peer 00:03:11.800 --> 00:03:11.810 align:start position:0% network but really it's a peer-to-peer 00:03:11.810 --> 00:03:14.770 align:start position:0% network but really it's a peer-to-peer network<00:03:12.530> so<00:03:12.830> as<00:03:13.190> you<00:03:13.640> could<00:03:13.850> see<00:03:13.880> from<00:03:14.180> today's 00:03:14.770 --> 00:03:14.780 align:start position:0% network so as you could see from today's 00:03:14.780 --> 00:03:16.840 align:start position:0% network so as you could see from today's presentations<00:03:15.709> we're<00:03:15.920> really<00:03:16.130> moving<00:03:16.550> in<00:03:16.700> the 00:03:16.840 --> 00:03:16.850 align:start position:0% presentations we're really moving in the 00:03:16.850 --> 00:03:19.479 align:start position:0% presentations we're really moving in the direction<00:03:17.000> that<00:03:17.750> there's<00:03:17.989> going<00:03:18.320> to<00:03:18.440> be<00:03:18.650> some 00:03:19.479 --> 00:03:19.489 align:start position:0% direction that there's going to be some 00:03:19.489 --> 00:03:22.360 align:start position:0% direction that there's going to be some kind<00:03:19.730> of<00:03:19.910> ethereal<00:03:20.270> node<00:03:20.750> everywhere<00:03:21.370> there 00:03:22.360 --> 00:03:22.370 align:start position:0% kind of ethereal node everywhere there 00:03:22.370 --> 00:03:24.100 align:start position:0% kind of ethereal node everywhere there most<00:03:22.730> of<00:03:22.910> them<00:03:23.090> will<00:03:23.270> be<00:03:23.300> light<00:03:23.660> and<00:03:23.930> very 00:03:24.100 --> 00:03:24.110 align:start position:0% most of them will be light and very 00:03:24.110 --> 00:03:26.710 align:start position:0% most of them will be light and very light<00:03:24.350> nodes<00:03:24.709> but<00:03:25.250> still<00:03:25.550> we're<00:03:26.239> going<00:03:26.510> to 00:03:26.710 --> 00:03:26.720 align:start position:0% light nodes but still we're going to 00:03:26.720 --> 00:03:29.710 align:start position:0% light nodes but still we're going to have<00:03:26.930> a<00:03:27.489> network<00:03:28.489> where<00:03:28.820> there<00:03:29.120> are<00:03:29.270> many<00:03:29.540> many 00:03:29.710 --> 00:03:29.720 align:start position:0% have a network where there are many many 00:03:29.720 --> 00:03:33.490 align:start position:0% have a network where there are many many nodes<00:03:30.200> and<00:03:30.910> you<00:03:31.910> typically<00:03:32.390> don't<00:03:32.720> connect<00:03:33.230> to 00:03:33.490 --> 00:03:33.500 align:start position:0% nodes and you typically don't connect to 00:03:33.500 --> 00:03:37.240 align:start position:0% nodes and you typically don't connect to high<00:03:33.920> powered<00:03:34.340> nodes<00:03:35.230> for<00:03:36.230> your<00:03:36.650> needs<00:03:36.980> you 00:03:37.240 --> 00:03:37.250 align:start position:0% high powered nodes for your needs you 00:03:37.250 --> 00:03:41.920 align:start position:0% high powered nodes for your needs you have<00:03:37.430> your<00:03:37.640> own<00:03:37.820> node<00:03:39.160> so<00:03:40.160> the<00:03:40.940> backends<00:03:41.690> that 00:03:41.920 --> 00:03:41.930 align:start position:0% have your own node so the backends that 00:03:41.930 --> 00:03:43.810 align:start position:0% have your own node so the backends that we're<00:03:42.110> going<00:03:42.380> to<00:03:42.560> have<00:03:42.799> their<00:03:43.160> old<00:03:43.370> general 00:03:43.810 --> 00:03:43.820 align:start position:0% we're going to have their old general 00:03:43.820 --> 00:03:46.680 align:start position:0% we're going to have their old general purpose<00:03:44.239> they're<00:03:44.870> distributed<00:03:45.650> and 00:03:46.680 --> 00:03:46.690 align:start position:0% purpose they're distributed and 00:03:46.690 --> 00:03:50.080 align:start position:0% purpose they're distributed and basically<00:03:47.690> the<00:03:48.290> the<00:03:49.070> ones<00:03:49.280> that<00:03:49.549> you<00:03:49.700> need<00:03:49.880> to 00:03:50.080 --> 00:03:50.090 align:start position:0% basically the the ones that you need to 00:03:50.090 --> 00:03:52.270 align:start position:0% basically the the ones that you need to rely<00:03:50.450> on<00:03:50.480> and<00:03:50.930> the<00:03:51.080> are<00:03:51.290> the<00:03:51.440> three<00:03:51.709> listed<00:03:52.130> on 00:03:52.270 --> 00:03:52.280 align:start position:0% rely on and the are the three listed on 00:03:52.280 --> 00:03:54.880 align:start position:0% rely on and the are the three listed on the<00:03:52.430> slides<00:03:52.730> so<00:03:53.090> you're<00:03:53.989> going<00:03:54.290> to<00:03:54.440> have<00:03:54.650> a 00:03:54.880 --> 00:03:54.890 align:start position:0% the slides so you're going to have a 00:03:54.890 --> 00:03:57.759 align:start position:0% the slides so you're going to have a contract<00:03:55.400> content<00:03:56.000> address<00:03:56.390> storage<00:03:56.840> which 00:03:57.759 --> 00:03:57.769 align:start position:0% contract content address storage which 00:03:57.769 --> 00:04:01.780 align:start position:0% contract content address storage which will<00:03:58.070> be<00:03:59.049> something<00:04:00.049> so<00:04:00.709> in<00:04:00.980> this<00:04:01.250> case<00:04:01.519> it's 00:04:01.780 --> 00:04:01.790 align:start position:0% will be something so in this case it's 00:04:01.790 --> 00:04:06.940 align:start position:0% will be something so in this case it's warm<00:04:02.440> IP<00:04:03.440> FS<00:04:03.980> is<00:04:05.049> hopefully<00:04:06.049> so<00:04:06.320> hopefully<00:04:06.350> we 00:04:06.940 --> 00:04:06.950 align:start position:0% warm IP FS is hopefully so hopefully we 00:04:06.950 --> 00:04:09.490 align:start position:0% warm IP FS is hopefully so hopefully we are<00:04:07.010> going<00:04:07.280> to<00:04:07.459> make<00:04:07.640> swarm<00:04:08.150> ipfs<00:04:08.870> compliant 00:04:09.490 --> 00:04:09.500 align:start position:0% are going to make swarm ipfs compliant 00:04:09.500 --> 00:04:11.800 align:start position:0% are going to make swarm ipfs compliant and<00:04:09.680> the<00:04:09.910> addressing<00:04:10.910> mechanism<00:04:11.570> and<00:04:11.690> the 00:04:11.800 --> 00:04:11.810 align:start position:0% and the addressing mechanism and the 00:04:11.810 --> 00:04:13.720 align:start position:0% and the addressing mechanism and the access<00:04:12.110> mechanism<00:04:12.709> will<00:04:12.829> be<00:04:12.860> compatible<00:04:13.610> or 00:04:13.720 --> 00:04:13.730 align:start position:0% access mechanism will be compatible or 00:04:13.730 --> 00:04:16.509 align:start position:0% access mechanism will be compatible or even<00:04:13.970> the<00:04:14.120> same<00:04:14.500> so<00:04:15.500> what<00:04:15.739> I'm<00:04:15.890> going<00:04:16.100> to<00:04:16.190> tell 00:04:16.509 --> 00:04:16.519 align:start position:0% even the same so what I'm going to tell 00:04:16.519 --> 00:04:19.270 align:start position:0% even the same so what I'm going to tell here<00:04:16.880> applies<00:04:17.239> directly<00:04:17.540> to<00:04:17.930> ipfs<00:04:18.709> as<00:04:18.919> well<00:04:19.130> as 00:04:19.270 --> 00:04:19.280 align:start position:0% here applies directly to ipfs as well as 00:04:19.280 --> 00:04:21.310 align:start position:0% here applies directly to ipfs as well as it<00:04:19.400> applies<00:04:19.760> to<00:04:19.790> swarm<00:04:20.359> hopefully<00:04:20.930> it<00:04:21.019> will<00:04:21.140> be 00:04:21.310 --> 00:04:21.320 align:start position:0% it applies to swarm hopefully it will be 00:04:21.320 --> 00:04:23.040 align:start position:0% it applies to swarm hopefully it will be the<00:04:21.350> same<00:04:21.650> thing 00:04:23.040 --> 00:04:23.050 align:start position:0% the same thing 00:04:23.050 --> 00:04:25.630 align:start position:0% the same thing there's<00:04:24.050> the<00:04:24.229> blockchain<00:04:24.470> based<00:04:24.919> on<00:04:25.160> census 00:04:25.630 --> 00:04:25.640 align:start position:0% there's the blockchain based on census 00:04:25.640 --> 00:04:28.300 align:start position:0% there's the blockchain based on census so<00:04:25.850> wherever<00:04:26.150> you<00:04:26.390> need<00:04:26.600> global<00:04:27.320> consistency 00:04:28.300 --> 00:04:28.310 align:start position:0% so wherever you need global consistency 00:04:28.310 --> 00:04:30.969 align:start position:0% so wherever you need global consistency you<00:04:28.430> can<00:04:28.490> solve<00:04:28.880> the<00:04:29.000> blockchain<00:04:29.510> and<00:04:29.979> you 00:04:30.969 --> 00:04:30.979 align:start position:0% you can solve the blockchain and you 00:04:30.979 --> 00:04:34.360 align:start position:0% you can solve the blockchain and you will<00:04:31.160> have<00:04:31.400> a<00:04:31.640> synchronous<00:04:32.180> messaging<00:04:33.370> so 00:04:34.360 --> 00:04:34.370 align:start position:0% will have a synchronous messaging so 00:04:34.370 --> 00:04:36.670 align:start position:0% will have a synchronous messaging so that's<00:04:34.640> that's<00:04:35.450> the<00:04:35.750> things<00:04:36.020> that<00:04:36.260> you<00:04:36.470> can 00:04:36.670 --> 00:04:36.680 align:start position:0% that's that's the things that you can 00:04:36.680 --> 00:04:38.830 align:start position:0% that's that's the things that you can think<00:04:36.950> of<00:04:37.070> as<00:04:37.220> a<00:04:37.370> back-end<00:04:37.640> but<00:04:38.090> you<00:04:38.510> will<00:04:38.660> not 00:04:38.830 --> 00:04:38.840 align:start position:0% think of as a back-end but you will not 00:04:38.840 --> 00:04:39.439 align:start position:0% think of as a back-end but you will not have 00:04:39.439 --> 00:04:39.449 align:start position:0% have 00:04:39.449 --> 00:04:41.959 align:start position:0% have cific<00:04:39.840> databases<00:04:40.469> that<00:04:41.069> you<00:04:41.129> need<00:04:41.460> to<00:04:41.669> query 00:04:41.959 --> 00:04:41.969 align:start position:0% cific databases that you need to query 00:04:41.969 --> 00:04:45.890 align:start position:0% cific databases that you need to query and<00:04:42.300> so<00:04:42.539> on<00:04:43.460> which<00:04:44.460> has<00:04:44.759> this<00:04:44.939> funny<00:04:45.240> property 00:04:45.890 --> 00:04:45.900 align:start position:0% and so on which has this funny property 00:04:45.900 --> 00:04:49.339 align:start position:0% and so on which has this funny property that<00:04:46.289> particular<00:04:47.189> business<00:04:47.610> logic<00:04:48.349> the 00:04:49.339 --> 00:04:49.349 align:start position:0% that particular business logic the 00:04:49.349 --> 00:04:51.529 align:start position:0% that particular business logic the business<00:04:49.740> logic<00:04:49.949> of<00:04:50.309> your<00:04:50.339> application<00:04:51.300> will 00:04:51.529 --> 00:04:51.539 align:start position:0% business logic of your application will 00:04:51.539 --> 00:04:55.909 align:start position:0% business logic of your application will mostly<00:04:52.020> run<00:04:52.379> on<00:04:52.589> the<00:04:52.889> clients<00:04:54.650> which<00:04:55.650> is 00:04:55.909 --> 00:04:55.919 align:start position:0% mostly run on the clients which is 00:04:55.919 --> 00:04:57.860 align:start position:0% mostly run on the clients which is either<00:04:56.249> web<00:04:56.639> applications<00:04:57.360> written<00:04:57.599> in 00:04:57.860 --> 00:04:57.870 align:start position:0% either web applications written in 00:04:57.870 --> 00:05:00.369 align:start position:0% either web applications written in JavaScript<00:04:58.589> or<00:04:58.770> native<00:04:59.219> mobile<00:04:59.430> applications 00:05:00.369 --> 00:05:00.379 align:start position:0% JavaScript or native mobile applications 00:05:00.379 --> 00:05:03.499 align:start position:0% JavaScript or native mobile applications so<00:05:01.379> you<00:05:01.439> will<00:05:01.710> have<00:05:01.919> to<00:05:02.249> actually<00:05:02.909> consider 00:05:03.499 --> 00:05:03.509 align:start position:0% so you will have to actually consider 00:05:03.509 --> 00:05:06.350 align:start position:0% so you will have to actually consider that<00:05:04.379> much<00:05:04.830> of<00:05:05.039> your<00:05:05.249> business<00:05:05.669> logic<00:05:05.939> is 00:05:06.350 --> 00:05:06.360 align:start position:0% that much of your business logic is 00:05:06.360 --> 00:05:08.299 align:start position:0% that much of your business logic is going<00:05:06.659> to<00:05:06.839> be<00:05:06.960> run<00:05:07.169> on<00:05:07.289> the<00:05:07.439> client<00:05:07.650> it<00:05:07.949> doesn't 00:05:08.299 --> 00:05:08.309 align:start position:0% going to be run on the client it doesn't 00:05:08.309 --> 00:05:12.559 align:start position:0% going to be run on the client it doesn't mean<00:05:08.520> that<00:05:08.550> the<00:05:08.879> API<00:05:09.330> will<00:05:09.809> be<00:05:10.139> such<00:05:10.620> that<00:05:11.569> you 00:05:12.559 --> 00:05:12.569 align:start position:0% mean that the API will be such that you 00:05:12.569 --> 00:05:15.829 align:start position:0% mean that the API will be such that you will<00:05:13.050> have<00:05:13.229> to<00:05:13.580> do<00:05:14.580> the<00:05:14.819> index<00:05:15.180> traversal 00:05:15.829 --> 00:05:15.839 align:start position:0% will have to do the index traversal 00:05:15.839 --> 00:05:20.749 align:start position:0% will have to do the index traversal yourself<00:05:16.379> but<00:05:17.310> in<00:05:18.029> reality<00:05:18.620> it<00:05:19.620> is<00:05:20.129> the<00:05:20.279> client 00:05:20.749 --> 00:05:20.759 align:start position:0% yourself but in reality it is the client 00:05:20.759 --> 00:05:22.610 align:start position:0% yourself but in reality it is the client that<00:05:20.909> is<00:05:21.060> going<00:05:21.330> to<00:05:21.539> traverse<00:05:21.870> the<00:05:22.110> index<00:05:22.379> for 00:05:22.610 --> 00:05:22.620 align:start position:0% that is going to traverse the index for 00:05:22.620 --> 00:05:25.969 align:start position:0% that is going to traverse the index for you<00:05:22.830> so<00:05:23.639> the<00:05:23.909> you<00:05:24.659> will<00:05:24.839> not<00:05:25.050> send<00:05:25.409> queries 00:05:25.969 --> 00:05:25.979 align:start position:0% you so the you will not send queries 00:05:25.979 --> 00:05:28.909 align:start position:0% you so the you will not send queries across<00:05:26.249> the<00:05:26.729> network<00:05:27.199> you<00:05:28.199> will<00:05:28.349> actually 00:05:28.909 --> 00:05:28.919 align:start position:0% across the network you will actually 00:05:28.919 --> 00:05:30.950 align:start position:0% across the network you will actually traverse<00:05:29.310> the<00:05:29.580> indices<00:05:30.029> as<00:05:30.270> you<00:05:30.419> access<00:05:30.749> them 00:05:30.950 --> 00:05:30.960 align:start position:0% traverse the indices as you access them 00:05:30.960 --> 00:05:33.950 align:start position:0% traverse the indices as you access them from<00:05:31.020> the<00:05:31.409> content<00:05:31.770> address<00:05:32.159> storage<00:05:32.550> and<00:05:32.960> you 00:05:33.950 --> 00:05:33.960 align:start position:0% from the content address storage and you 00:05:33.960 --> 00:05:36.230 align:start position:0% from the content address storage and you can<00:05:34.139> only<00:05:34.439> send<00:05:34.800> the<00:05:34.889> query<00:05:35.189> to<00:05:35.520> the<00:05:35.639> API<00:05:35.969> and 00:05:36.230 --> 00:05:36.240 align:start position:0% can only send the query to the API and 00:05:36.240 --> 00:05:42.589 align:start position:0% can only send the query to the API and it<00:05:36.389> will<00:05:36.599> be<00:05:36.719> executed<00:05:37.349> locally<00:05:40.729> so<00:05:41.729> here's 00:05:42.589 --> 00:05:42.599 align:start position:0% it will be executed locally so here's 00:05:42.599 --> 00:05:46.040 align:start position:0% it will be executed locally so here's here's<00:05:42.960> an<00:05:43.110> example<00:05:43.469> of<00:05:43.830> how<00:05:43.889> the<00:05:44.849> HTTP<00:05:45.719> is<00:05:45.870> the 00:05:46.040 --> 00:05:46.050 align:start position:0% here's an example of how the HTTP is the 00:05:46.050 --> 00:05:47.659 align:start position:0% here's an example of how the HTTP is the the<00:05:46.409> Web<00:05:46.649> API 00:05:47.659 --> 00:05:47.669 align:start position:0% the Web API 00:05:47.669 --> 00:05:51.290 align:start position:0% the Web API it<00:05:48.060> works<00:05:48.240> with<00:05:48.539> swarm<00:05:48.899> so<00:05:49.740> the<00:05:50.129> URLs<00:05:50.639> begin 00:05:51.290 --> 00:05:51.300 align:start position:0% it works with swarm so the URLs begin 00:05:51.300 --> 00:05:54.350 align:start position:0% it works with swarm so the URLs begin with<00:05:51.659> the<00:05:51.960> root<00:05:52.349> hash<00:05:52.620> of<00:05:52.949> a<00:05:53.339> collection<00:05:54.149> a 00:05:54.350 --> 00:05:54.360 align:start position:0% with the root hash of a collection a 00:05:54.360 --> 00:05:57.679 align:start position:0% with the root hash of a collection a collection<00:05:55.189> is<00:05:56.189> basically<00:05:57.120> a<00:05:57.149> collection<00:05:57.419> of 00:05:57.679 --> 00:05:57.689 align:start position:0% collection is basically a collection of 00:05:57.689 --> 00:06:02.649 align:start position:0% collection is basically a collection of objects<00:05:58.229> objects<00:05:58.889> are<00:05:59.039> binary<00:05:59.520> files<00:05:59.849> with<00:06:00.270> a 00:06:02.649 --> 00:06:02.659 align:start position:0% 00:06:02.659 --> 00:06:06.260 align:start position:0% mime<00:06:03.659> type<00:06:03.930> so<00:06:04.889> for<00:06:05.069> example<00:06:05.490> it<00:06:05.550> can<00:06:05.729> be<00:06:05.759> a<00:06:05.909> PNG 00:06:06.260 --> 00:06:06.270 align:start position:0% mime type so for example it can be a PNG 00:06:06.270 --> 00:06:13.010 align:start position:0% mime type so for example it can be a PNG image<00:06:09.020> but<00:06:10.610> so<00:06:11.610> it<00:06:11.909> looks<00:06:12.240> very<00:06:12.509> much<00:06:12.749> like<00:06:12.779> a 00:06:13.010 --> 00:06:13.020 align:start position:0% image but so it looks very much like a 00:06:13.020 --> 00:06:16.070 align:start position:0% image but so it looks very much like a directory<00:06:13.740> but<00:06:14.129> it<00:06:14.279> really<00:06:14.459> isn't<00:06:14.870> so<00:06:15.870> for 00:06:16.070 --> 00:06:16.080 align:start position:0% directory but it really isn't so for 00:06:16.080 --> 00:06:18.980 align:start position:0% directory but it really isn't so for example<00:06:16.649> the<00:06:16.889> second<00:06:17.279> example<00:06:17.729> is<00:06:18.060> a<00:06:18.180> map<00:06:18.659> tile 00:06:18.980 --> 00:06:18.990 align:start position:0% example the second example is a map tile 00:06:18.990 --> 00:06:23.360 align:start position:0% example the second example is a map tile where<00:06:19.680> that<00:06:19.889> long<00:06:20.219> code<00:06:20.610> is<00:06:20.909> the<00:06:22.370> hierarchical 00:06:23.360 --> 00:06:23.370 align:start position:0% where that long code is the hierarchical 00:06:23.370 --> 00:06:27.050 align:start position:0% where that long code is the hierarchical tile<00:06:24.270> code<00:06:24.629> for<00:06:25.439> for<00:06:26.039> map<00:06:26.279> slides<00:06:26.610> so<00:06:26.819> in<00:06:26.969> a 00:06:27.050 --> 00:06:27.060 align:start position:0% tile code for for map slides so in a 00:06:27.060 --> 00:06:29.540 align:start position:0% tile code for for map slides so in a single<00:06:27.449> directory<00:06:27.599> you<00:06:28.560> will<00:06:28.740> have<00:06:28.949> thousands 00:06:29.540 --> 00:06:29.550 align:start position:0% single directory you will have thousands 00:06:29.550 --> 00:06:31.459 align:start position:0% single directory you will have thousands or<00:06:30.240> hundreds<00:06:30.719> of<00:06:30.839> thousands<00:06:31.319> or<00:06:31.409> even 00:06:31.459 --> 00:06:31.469 align:start position:0% or hundreds of thousands or even 00:06:31.469 --> 00:06:34.399 align:start position:0% or hundreds of thousands or even millions<00:06:31.740> of<00:06:32.399> files<00:06:32.729> if<00:06:33.240> you<00:06:33.539> think<00:06:33.930> about<00:06:34.080> it 00:06:34.399 --> 00:06:34.409 align:start position:0% millions of files if you think about it 00:06:34.409 --> 00:06:36.499 align:start position:0% millions of files if you think about it as<00:06:34.560> files<00:06:34.830> but<00:06:35.099> you<00:06:35.219> really<00:06:35.490> shouldn't<00:06:35.849> so 00:06:36.499 --> 00:06:36.509 align:start position:0% as files but you really shouldn't so 00:06:36.509 --> 00:06:40.730 align:start position:0% as files but you really shouldn't so it's<00:06:36.689> really<00:06:36.990> a<00:06:37.319> a<00:06:37.800> database<00:06:38.430> and<00:06:39.740> whenever 00:06:40.730 --> 00:06:40.740 align:start position:0% it's really a a database and whenever 00:06:40.740 --> 00:06:43.429 align:start position:0% it's really a a database and whenever you<00:06:41.009> access<00:06:41.459> something<00:06:41.729> like<00:06:42.209> this<00:06:42.539> map<00:06:43.110> tile 00:06:43.429 --> 00:06:43.439 align:start position:0% you access something like this map tile 00:06:43.439 --> 00:06:45.760 align:start position:0% you access something like this map tile you're<00:06:44.129> actually<00:06:44.669> doing<00:06:44.939> the<00:06:45.180> know<00:06:45.389> the 00:06:45.760 --> 00:06:45.770 align:start position:0% you're actually doing the know the 00:06:45.770 --> 00:06:49.279 align:start position:0% you're actually doing the know the indexed<00:06:46.770> River<00:06:47.009> so<00:06:47.310> locally<00:06:48.120> which<00:06:48.990> is<00:06:49.139> of 00:06:49.279 --> 00:06:49.289 align:start position:0% indexed River so locally which is of 00:06:49.289 --> 00:06:51.210 align:start position:0% indexed River so locally which is of course<00:06:49.469> fast<00:06:49.800> because<00:06:50.250> it's<00:06:50.459> it's 00:06:51.210 --> 00:06:51.220 align:start position:0% course fast because it's it's 00:06:51.220 --> 00:06:52.710 align:start position:0% course fast because it's it's done<00:06:51.370> efficiently<00:06:52.000> but<00:06:52.150> it's<00:06:52.330> still<00:06:52.540> done 00:06:52.710 --> 00:06:52.720 align:start position:0% done efficiently but it's still done 00:06:52.720 --> 00:06:56.250 align:start position:0% done efficiently but it's still done locally<00:06:52.960> and<00:06:53.910> the<00:06:54.910> property<00:06:55.570> of<00:06:55.660> the<00:06:55.810> API<00:06:56.170> is 00:06:56.250 --> 00:06:56.260 align:start position:0% locally and the property of the API is 00:06:56.260 --> 00:06:58.380 align:start position:0% locally and the property of the API is that<00:06:56.440> if<00:06:57.010> you<00:06:57.190> change<00:06:57.490> anything<00:06:57.970> in<00:06:58.360> the 00:06:58.380 --> 00:06:58.390 align:start position:0% that if you change anything in the 00:06:58.390 --> 00:07:01.590 align:start position:0% that if you change anything in the collection<00:06:58.660> it<00:06:59.650> also<00:06:59.920> happens<00:07:00.460> fast<00:07:00.760> but<00:07:01.450> it 00:07:01.590 --> 00:07:01.600 align:start position:0% collection it also happens fast but it 00:07:01.600 --> 00:07:04.530 align:start position:0% collection it also happens fast but it changes<00:07:02.020> the<00:07:02.230> route<00:07:02.380> -<00:07:02.590> so<00:07:03.250> any<00:07:03.460> put<00:07:03.790> or<00:07:04.030> delete 00:07:04.530 --> 00:07:04.540 align:start position:0% changes the route - so any put or delete 00:07:04.540 --> 00:07:07.020 align:start position:0% changes the route - so any put or delete method<00:07:04.990> will<00:07:05.560> result<00:07:06.040> in<00:07:06.250> a<00:07:06.370> different<00:07:06.790> hash 00:07:07.020 --> 00:07:07.030 align:start position:0% method will result in a different hash 00:07:07.030 --> 00:07:10.140 align:start position:0% method will result in a different hash and<00:07:07.570> it<00:07:07.900> will<00:07:08.110> it<00:07:09.040> will<00:07:09.220> return<00:07:09.640> to<00:07:09.940> you<00:07:10.120> the 00:07:10.140 --> 00:07:10.150 align:start position:0% and it will it will return to you the 00:07:10.150 --> 00:07:14.910 align:start position:0% and it will it will return to you the the<00:07:10.780> new<00:07:10.930> hash<00:07:11.910> and<00:07:12.910> of<00:07:13.750> course<00:07:14.080> if<00:07:14.350> you<00:07:14.650> want 00:07:14.910 --> 00:07:14.920 align:start position:0% the new hash and of course if you want 00:07:14.920 --> 00:07:17.490 align:start position:0% the new hash and of course if you want to<00:07:15.160> have<00:07:15.370> some<00:07:15.850> global<00:07:16.570> state<00:07:16.870> that<00:07:17.290> is 00:07:17.490 --> 00:07:17.500 align:start position:0% to have some global state that is 00:07:17.500 --> 00:07:19.890 align:start position:0% to have some global state that is consistent<00:07:18.160> across<00:07:18.550> all<00:07:18.940> the<00:07:19.150> all<00:07:19.480> all<00:07:19.750> the 00:07:19.890 --> 00:07:19.900 align:start position:0% consistent across all the all all the 00:07:19.900 --> 00:07:22.350 align:start position:0% consistent across all the all all the users<00:07:20.260> then<00:07:20.890> you<00:07:21.070> can<00:07:21.310> register<00:07:21.490> these<00:07:22.120> route 00:07:22.350 --> 00:07:22.360 align:start position:0% users then you can register these route 00:07:22.360 --> 00:07:25.200 align:start position:0% users then you can register these route hashes<00:07:22.930> on<00:07:23.170> the<00:07:23.380> blockchain<00:07:23.620> for<00:07:24.400> example<00:07:25.000> in 00:07:25.200 --> 00:07:25.210 align:start position:0% hashes on the blockchain for example in 00:07:25.210 --> 00:07:29.280 align:start position:0% hashes on the blockchain for example in hierarchical<00:07:26.250> in<00:07:27.250> hierarchical<00:07:28.290> name 00:07:29.280 --> 00:07:29.290 align:start position:0% hierarchical in hierarchical name 00:07:29.290 --> 00:07:31.770 align:start position:0% hierarchical in hierarchical name registry<00:07:29.770> contracts<00:07:30.370> so<00:07:30.940> in<00:07:31.180> the<00:07:31.420> last 00:07:31.770 --> 00:07:31.780 align:start position:0% registry contracts so in the last 00:07:31.780 --> 00:07:35.880 align:start position:0% registry contracts so in the last example<00:07:32.220> you<00:07:33.220> see<00:07:33.580> an<00:07:33.880> image<00:07:34.860> which<00:07:35.860> is 00:07:35.880 --> 00:07:35.890 align:start position:0% example you see an image which is 00:07:35.890 --> 00:07:38.640 align:start position:0% example you see an image which is registered<00:07:36.490> in<00:07:37.300> an<00:07:37.540> album<00:07:37.990> a<00:07:38.140> photo<00:07:38.440> album 00:07:38.640 --> 00:07:38.650 align:start position:0% registered in an album a photo album 00:07:38.650 --> 00:07:42.000 align:start position:0% registered in an album a photo album that<00:07:38.920> is<00:07:39.540> actually<00:07:40.540> Joe's<00:07:41.110> personal<00:07:41.560> photo 00:07:42.000 --> 00:07:42.010 align:start position:0% that is actually Joe's personal photo 00:07:42.010 --> 00:07:47.730 align:start position:0% that is actually Joe's personal photo album<00:07:44.040> the<00:07:45.040> user<00:07:45.250> experience<00:07:46.030> is<00:07:46.350> going<00:07:47.350> to<00:07:47.620> be 00:07:47.730 --> 00:07:47.740 align:start position:0% album the user experience is going to be 00:07:47.740 --> 00:07:49.740 align:start position:0% album the user experience is going to be very<00:07:48.010> familiar<00:07:48.220> to<00:07:48.730> web<00:07:48.880> users<00:07:49.270> that's<00:07:49.510> what 00:07:49.740 --> 00:07:49.750 align:start position:0% very familiar to web users that's what 00:07:49.750 --> 00:07:53.360 align:start position:0% very familiar to web users that's what we're<00:07:49.930> aiming<00:07:50.140> at<00:07:50.700> so<00:07:52.320> interactive 00:07:53.360 --> 00:07:53.370 align:start position:0% we're aiming at so interactive 00:07:53.370 --> 00:07:56.659 align:start position:0% we're aiming at so interactive responsive<00:07:54.370> intuitive<00:07:54.940> and<00:07:55.120> so<00:07:55.330> on<00:07:55.450> however 00:07:56.659 --> 00:07:56.669 align:start position:0% responsive intuitive and so on however 00:07:56.669 --> 00:08:00.020 align:start position:0% responsive intuitive and so on however Identity<00:07:57.669> Management<00:07:58.030> will<00:07:58.570> also<00:07:58.930> be<00:07:59.110> done<00:07:59.320> on 00:08:00.020 --> 00:08:00.030 align:start position:0% Identity Management will also be done on 00:08:00.030 --> 00:08:03.630 align:start position:0% Identity Management will also be done on the<00:08:01.030> client<00:08:01.150> on<00:08:01.510> the<00:08:01.720> browser<00:08:02.350> side<00:08:02.770> so<00:08:03.130> you 00:08:03.630 --> 00:08:03.640 align:start position:0% the client on the browser side so you 00:08:03.640 --> 00:08:04.860 align:start position:0% the client on the browser side so you don't<00:08:03.850> have<00:08:04.030> to<00:08:04.240> implement<00:08:04.660> your<00:08:04.810> own 00:08:04.860 --> 00:08:04.870 align:start position:0% don't have to implement your own 00:08:04.870 --> 00:08:06.960 align:start position:0% don't have to implement your own identity<00:08:05.620> management<00:08:05.890> with<00:08:06.280> each<00:08:06.400> DAP<00:08:06.700> you 00:08:06.960 --> 00:08:06.970 align:start position:0% identity management with each DAP you 00:08:06.970 --> 00:08:10.590 align:start position:0% identity management with each DAP you you<00:08:07.210> get<00:08:07.600> it<00:08:07.780> ready<00:08:08.020> and<00:08:09.240> you're<00:08:10.240> going<00:08:10.570> to 00:08:10.590 --> 00:08:10.600 align:start position:0% you get it ready and you're going to 00:08:10.600 --> 00:08:15.030 align:start position:0% you get it ready and you're going to have<00:08:11.160> legal<00:08:12.160> and<00:08:12.340> financial<00:08:12.660> interactions<00:08:14.040> so 00:08:15.030 --> 00:08:15.040 align:start position:0% have legal and financial interactions so 00:08:15.040 --> 00:08:17.580 align:start position:0% have legal and financial interactions so it's<00:08:15.820> no<00:08:16.090> longer<00:08:16.120> a<00:08:16.479> click-through<00:08:16.810> contract 00:08:17.580 --> 00:08:17.590 align:start position:0% it's no longer a click-through contract 00:08:17.590 --> 00:08:19.500 align:start position:0% it's no longer a click-through contract it's<00:08:18.130> something<00:08:18.640> that<00:08:18.820> actually<00:08:19.000> has 00:08:19.500 --> 00:08:19.510 align:start position:0% it's something that actually has 00:08:19.510 --> 00:08:24.510 align:start position:0% it's something that actually has consequences<00:08:22.470> so<00:08:23.470> it<00:08:23.650> comes<00:08:23.890> with<00:08:24.040> all<00:08:24.310> those 00:08:24.510 --> 00:08:24.520 align:start position:0% consequences so it comes with all those 00:08:24.520 --> 00:08:28.310 align:start position:0% consequences so it comes with all those things<00:08:24.820> that<00:08:25.030> are<00:08:25.150> also<00:08:25.270> listed<00:08:25.930> on<00:08:26.050> the<00:08:26.169> slide 00:08:28.310 --> 00:08:28.320 align:start position:0% things that are also listed on the slide 00:08:28.320 --> 00:08:32.029 align:start position:0% things that are also listed on the slide so<00:08:29.320> now<00:08:29.830> I<00:08:29.860> will<00:08:30.370> show<00:08:30.729> you<00:08:30.790> a<00:08:30.940> few<00:08:31.300> examples 00:08:32.029 --> 00:08:32.039 align:start position:0% so now I will show you a few examples 00:08:32.039 --> 00:08:34.920 align:start position:0% so now I will show you a few examples some<00:08:33.039> of<00:08:33.190> them<00:08:33.400> are<00:08:33.580> already<00:08:34.089> implemented<00:08:34.780> and 00:08:34.920 --> 00:08:34.930 align:start position:0% some of them are already implemented and 00:08:34.930 --> 00:08:37.740 align:start position:0% some of them are already implemented and downloadable<00:08:35.500> from<00:08:36.010> a<00:08:36.250> source<00:08:37.030> repository 00:08:37.740 --> 00:08:37.750 align:start position:0% downloadable from a source repository 00:08:37.750 --> 00:08:41.430 align:start position:0% downloadable from a source repository some<00:08:38.110> of<00:08:38.229> them<00:08:38.469> are<00:08:38.680> tearaway<00:08:39.159> vaporware<00:08:40.440> but 00:08:41.430 --> 00:08:41.440 align:start position:0% some of them are tearaway vaporware but 00:08:41.440 --> 00:08:44.450 align:start position:0% some of them are tearaway vaporware but all<00:08:41.680> of<00:08:41.830> them<00:08:42.070> have<00:08:42.280> these<00:08:42.490> basic<00:08:43.320> properties 00:08:44.450 --> 00:08:44.460 align:start position:0% all of them have these basic properties 00:08:44.460 --> 00:08:47.430 align:start position:0% all of them have these basic properties so<00:08:45.460> the<00:08:45.700> current<00:08:46.060> route<00:08:46.270> hash<00:08:46.540> is<00:08:46.870> registered 00:08:47.430 --> 00:08:47.440 align:start position:0% so the current route hash is registered 00:08:47.440 --> 00:08:50.579 align:start position:0% so the current route hash is registered on<00:08:47.620> blockchain<00:08:47.890> so<00:08:48.460> that<00:08:48.700> every<00:08:49.390> every<00:08:50.320> user 00:08:50.579 --> 00:08:50.589 align:start position:0% on blockchain so that every every user 00:08:50.589 --> 00:08:53.130 align:start position:0% on blockchain so that every every user can<00:08:51.040> check<00:08:51.850> on<00:08:52.000> the<00:08:52.120> blockchain<00:08:52.360> which<00:08:52.780> is<00:08:52.960> the 00:08:53.130 --> 00:08:53.140 align:start position:0% can check on the blockchain which is the 00:08:53.140 --> 00:08:54.990 align:start position:0% can check on the blockchain which is the current<00:08:53.440> version<00:08:53.589> of<00:08:53.890> the<00:08:53.950> DAT<00:08:54.250> and<00:08:54.610> that's 00:08:54.990 --> 00:08:55.000 align:start position:0% current version of the DAT and that's 00:08:55.000 --> 00:08:57.090 align:start position:0% current version of the DAT and that's where<00:08:55.240> they<00:08:55.390> that's<00:08:56.140> where<00:08:56.440> they<00:08:56.620> proceed 00:08:57.090 --> 00:08:57.100 align:start position:0% where they that's where they proceed 00:08:57.100 --> 00:08:59.850 align:start position:0% where they that's where they proceed from<00:08:57.280> so<00:08:58.060> we<00:08:58.240> have<00:08:58.420> done<00:08:58.660> away<00:08:58.810> with<00:08:59.230> the 00:08:59.850 --> 00:08:59.860 align:start position:0% from so we have done away with the 00:08:59.860 --> 00:09:03.380 align:start position:0% from so we have done away with the problem<00:09:00.670> of<00:09:01.120> security<00:09:02.080> in<00:09:02.800> her<00:09:03.010> in 00:09:03.380 --> 00:09:03.390 align:start position:0% problem of security in her in 00:09:03.390 --> 00:09:06.980 align:start position:0% problem of security in her in and<00:09:03.570> in<00:09:04.610> HTTP<00:09:05.610> but<00:09:06.120> you<00:09:06.300> need<00:09:06.480> to<00:09:06.690> trust 00:09:06.980 --> 00:09:06.990 align:start position:0% and in HTTP but you need to trust 00:09:06.990 --> 00:09:11.180 align:start position:0% and in HTTP but you need to trust something<00:09:07.710> else<00:09:08.040> on<00:09:08.280> the<00:09:08.400> blockchain<00:09:10.190> most 00:09:11.180 --> 00:09:11.190 align:start position:0% something else on the blockchain most 00:09:11.190 --> 00:09:13.910 align:start position:0% something else on the blockchain most static<00:09:11.670> and<00:09:11.820> dynamic<00:09:11.940> data<00:09:12.570> are<00:09:12.960> stored<00:09:13.320> in<00:09:13.710> a 00:09:13.910 --> 00:09:13.920 align:start position:0% static and dynamic data are stored in a 00:09:13.920 --> 00:09:17.870 align:start position:0% static and dynamic data are stored in a content<00:09:14.340> address<00:09:14.730> storage<00:09:15.120> and<00:09:16.550> global<00:09:17.550> state 00:09:17.870 --> 00:09:17.880 align:start position:0% content address storage and global state 00:09:17.880 --> 00:09:20.600 align:start position:0% content address storage and global state changes<00:09:18.540> are<00:09:18.810> registered<00:09:19.680> on<00:09:19.950> the<00:09:20.370> blockchain 00:09:20.600 --> 00:09:20.610 align:start position:0% changes are registered on the blockchain 00:09:20.610 --> 00:09:23.750 align:start position:0% changes are registered on the blockchain so<00:09:21.420> it's<00:09:21.540> usually<00:09:21.870> global<00:09:22.800> state<00:09:23.070> changes<00:09:23.580> are 00:09:23.750 --> 00:09:23.760 align:start position:0% so it's usually global state changes are 00:09:23.760 --> 00:09:25.790 align:start position:0% so it's usually global state changes are simply<00:09:24.150> changes<00:09:24.630> in<00:09:24.780> a<00:09:24.870> hash<00:09:25.080> if<00:09:25.380> you<00:09:25.560> don't 00:09:25.790 --> 00:09:25.800 align:start position:0% simply changes in a hash if you don't 00:09:25.800 --> 00:09:27.530 align:start position:0% simply changes in a hash if you don't store<00:09:26.190> a<00:09:26.370> lot<00:09:26.550> of<00:09:26.580> state<00:09:26.970> data<00:09:27.210> in<00:09:27.450> the 00:09:27.530 --> 00:09:27.540 align:start position:0% store a lot of state data in the 00:09:27.540 --> 00:09:28.840 align:start position:0% store a lot of state data in the blockchain<00:09:27.780> because<00:09:28.200> that's<00:09:28.410> expensive 00:09:28.840 --> 00:09:28.850 align:start position:0% blockchain because that's expensive 00:09:28.850 --> 00:09:32.270 align:start position:0% blockchain because that's expensive however<00:09:29.850> you<00:09:30.360> still<00:09:30.660> need<00:09:30.930> to<00:09:31.350> to<00:09:31.830> get<00:09:32.010> those 00:09:32.270 --> 00:09:32.280 align:start position:0% however you still need to to get those 00:09:32.280 --> 00:09:33.950 align:start position:0% however you still need to to get those change<00:09:32.790> changes<00:09:33.360> to<00:09:33.630> the<00:09:33.750> blockchain 00:09:33.950 --> 00:09:33.960 align:start position:0% change changes to the blockchain 00:09:33.960 --> 00:09:36.590 align:start position:0% change changes to the blockchain eventually<00:09:34.740> so<00:09:35.280> that<00:09:35.520> there's<00:09:36.000> a<00:09:36.120> global 00:09:36.590 --> 00:09:36.600 align:start position:0% eventually so that there's a global 00:09:36.600 --> 00:09:39.800 align:start position:0% eventually so that there's a global consistency<00:09:37.560> and<00:09:38.310> I<00:09:38.970> have<00:09:39.150> already<00:09:39.390> talked 00:09:39.800 --> 00:09:39.810 align:start position:0% consistency and I have already talked 00:09:39.810 --> 00:09:44.480 align:start position:0% consistency and I have already talked about<00:09:41.810> about<00:09:42.810> the<00:09:43.020> other<00:09:43.140> things<00:09:43.500> so<00:09:44.040> whenever 00:09:44.480 --> 00:09:44.490 align:start position:0% about about the other things so whenever 00:09:44.490 --> 00:09:47.090 align:start position:0% about about the other things so whenever you<00:09:44.820> have<00:09:44.970> some<00:09:45.270> local<00:09:45.660> data<00:09:45.870> local<00:09:46.800> state 00:09:47.090 --> 00:09:47.100 align:start position:0% you have some local data local state 00:09:47.100 --> 00:09:48.860 align:start position:0% you have some local data local state like<00:09:47.400> what<00:09:47.580> the<00:09:47.730> user<00:09:47.880> is<00:09:48.120> working<00:09:48.300> with<00:09:48.720> you 00:09:48.860 --> 00:09:48.870 align:start position:0% like what the user is working with you 00:09:48.870 --> 00:09:50.360 align:start position:0% like what the user is working with you keep<00:09:49.080> it<00:09:49.230> locally<00:09:49.650> you<00:09:49.710> don't<00:09:49.920> submit<00:09:50.130> it 00:09:50.360 --> 00:09:50.370 align:start position:0% keep it locally you don't submit it 00:09:50.370 --> 00:09:52.670 align:start position:0% keep it locally you don't submit it anywhere<00:09:50.760> you<00:09:51.510> can<00:09:51.720> back<00:09:51.900> it<00:09:51.930> up<00:09:52.170> if<00:09:52.350> you<00:09:52.380> want 00:09:52.670 --> 00:09:52.680 align:start position:0% anywhere you can back it up if you want 00:09:52.680 --> 00:09:56.750 align:start position:0% anywhere you can back it up if you want to<00:09:53.750> so<00:09:54.750> the<00:09:54.930> first<00:09:55.140> example<00:09:55.350> is<00:09:55.890> a<00:09:55.950> distributed 00:09:56.750 --> 00:09:56.760 align:start position:0% to so the first example is a distributed 00:09:56.760 --> 00:10:00.140 align:start position:0% to so the first example is a distributed photo<00:09:57.000> album<00:09:57.450> this<00:09:57.780> is<00:09:57.840> already<00:09:58.410> existing<00:09:59.150> it 00:10:00.140 --> 00:10:00.150 align:start position:0% photo album this is already existing it 00:10:00.150 --> 00:10:02.720 align:start position:0% photo album this is already existing it can<00:10:00.420> be<00:10:00.630> you<00:10:01.620> know<00:10:01.770> you<00:10:01.860> can<00:10:02.040> download<00:10:02.280> it<00:10:02.610> you 00:10:02.720 --> 00:10:02.730 align:start position:0% can be you know you can download it you 00:10:02.730 --> 00:10:04.130 align:start position:0% can be you know you can download it you can<00:10:02.760> look<00:10:03.060> at<00:10:03.180> the<00:10:03.330> source<00:10:03.600> you<00:10:03.780> can<00:10:03.930> learn 00:10:04.130 --> 00:10:04.140 align:start position:0% can look at the source you can learn 00:10:04.140 --> 00:10:05.690 align:start position:0% can look at the source you can learn from<00:10:04.350> it<00:10:04.560> you<00:10:04.680> can<00:10:04.710> take<00:10:05.040> parts<00:10:05.370> so<00:10:05.460> it<00:10:05.580> is 00:10:05.690 --> 00:10:05.700 align:start position:0% from it you can take parts so it is 00:10:05.700 --> 00:10:09.770 align:start position:0% from it you can take parts so it is completely<00:10:05.940> open<00:10:06.270> source<00:10:07.850> so<00:10:08.850> both<00:10:09.210> the<00:10:09.540> data 00:10:09.770 --> 00:10:09.780 align:start position:0% completely open source so both the data 00:10:09.780 --> 00:10:12.890 align:start position:0% completely open source so both the data and<00:10:10.260> the<00:10:10.500> web<00:10:10.890> app<00:10:11.070> are<00:10:11.400> hosted<00:10:12.000> in<00:10:12.180> a<00:10:12.270> swarm 00:10:12.890 --> 00:10:12.900 align:start position:0% and the web app are hosted in a swarm 00:10:12.900 --> 00:10:14.930 align:start position:0% and the web app are hosted in a swarm and<00:10:13.170> they<00:10:13.560> are<00:10:13.800> hosted<00:10:14.340> in<00:10:14.520> the<00:10:14.550> same 00:10:14.930 --> 00:10:14.940 align:start position:0% and they are hosted in the same 00:10:14.940 --> 00:10:17.420 align:start position:0% and they are hosted in the same collection<00:10:15.480> that's<00:10:15.690> very<00:10:15.930> important<00:10:16.440> so<00:10:17.370> you 00:10:17.420 --> 00:10:17.430 align:start position:0% collection that's very important so you 00:10:17.430 --> 00:10:19.790 align:start position:0% collection that's very important so you don't<00:10:17.880> have<00:10:18.060> a<00:10:18.120> separate<00:10:18.810> root<00:10:19.050> hash<00:10:19.320> for<00:10:19.620> the 00:10:19.790 --> 00:10:19.800 align:start position:0% don't have a separate root hash for the 00:10:19.800 --> 00:10:22.910 align:start position:0% don't have a separate root hash for the data<00:10:20.010> and<00:10:20.310> that<00:10:20.430> it<00:10:21.300> is<00:10:21.600> the<00:10:21.810> depth<00:10:22.050> and<00:10:22.410> the 00:10:22.910 --> 00:10:22.920 align:start position:0% data and that it is the depth and the 00:10:22.920 --> 00:10:24.770 align:start position:0% data and that it is the depth and the data<00:10:23.130> together<00:10:23.610> that<00:10:23.970> have<00:10:24.150> the<00:10:24.330> same<00:10:24.540> root 00:10:24.770 --> 00:10:24.780 align:start position:0% data together that have the same root 00:10:24.780 --> 00:10:31.370 align:start position:0% data together that have the same root hash<00:10:25.670> so<00:10:28.610> you<00:10:29.610> can<00:10:29.820> register<00:10:30.060> a<00:10:30.510> photo<00:10:30.930> albums 00:10:31.370 --> 00:10:31.380 align:start position:0% hash so you can register a photo albums 00:10:31.380 --> 00:10:32.660 align:start position:0% hash so you can register a photo albums particular<00:10:32.010> State 00:10:32.660 --> 00:10:32.670 align:start position:0% particular State 00:10:32.670 --> 00:10:34.910 align:start position:0% particular State which<00:10:32.790> means<00:10:33.150> the<00:10:33.480> photos<00:10:34.140> in<00:10:34.380> it<00:10:34.530> and<00:10:34.770> the 00:10:34.910 --> 00:10:34.920 align:start position:0% which means the photos in it and the 00:10:34.920 --> 00:10:38.260 align:start position:0% which means the photos in it and the ordering<00:10:35.250> in<00:10:35.580> which<00:10:35.610> they<00:10:36.000> are<00:10:36.090> presented 00:10:38.260 --> 00:10:38.270 align:start position:0% ordering in which they are presented 00:10:38.270 --> 00:10:41.930 align:start position:0% ordering in which they are presented long<00:10:39.270> term<00:10:39.540> incentives<00:10:40.200> of<00:10:40.530> swarm<00:10:41.100> will<00:10:41.430> make 00:10:41.930 --> 00:10:41.940 align:start position:0% long term incentives of swarm will make 00:10:41.940 --> 00:10:43.670 align:start position:0% long term incentives of swarm will make sure<00:10:42.210> that<00:10:42.480> it's<00:10:42.660> not<00:10:42.810> garbage<00:10:43.020> collected 00:10:43.670 --> 00:10:43.680 align:start position:0% sure that it's not garbage collected 00:10:43.680 --> 00:10:46.510 align:start position:0% sure that it's not garbage collected that's<00:10:43.890> actually<00:10:44.310> not<00:10:44.460> implemented<00:10:45.330> yet 00:10:46.510 --> 00:10:46.520 align:start position:0% that's actually not implemented yet 00:10:46.520 --> 00:10:49.730 align:start position:0% that's actually not implemented yet short<00:10:47.520> terms<00:10:47.730> incentives<00:10:48.510> will<00:10:48.930> have<00:10:49.410> the 00:10:49.730 --> 00:10:49.740 align:start position:0% short terms incentives will have the 00:10:49.740 --> 00:10:52.280 align:start position:0% short terms incentives will have the publishing<00:10:50.160> Goes<00:10:50.550> Down<00:10:50.940> which<00:10:51.450> means<00:10:51.780> that<00:10:52.080> if 00:10:52.280 --> 00:10:52.290 align:start position:0% publishing Goes Down which means that if 00:10:52.290 --> 00:10:54.380 align:start position:0% publishing Goes Down which means that if your<00:10:52.470> photo<00:10:52.740> album<00:10:53.190> for<00:10:53.400> some<00:10:53.640> reason<00:10:54.000> becomes 00:10:54.380 --> 00:10:54.390 align:start position:0% your photo album for some reason becomes 00:10:54.390 --> 00:10:56.900 align:start position:0% your photo album for some reason becomes hugely<00:10:54.990> popular<00:10:55.590> and<00:10:55.830> half<00:10:56.070> the<00:10:56.250> web<00:10:56.400> wants<00:10:56.760> to 00:10:56.900 --> 00:10:56.910 align:start position:0% hugely popular and half the web wants to 00:10:56.910 --> 00:11:00.190 align:start position:0% hugely popular and half the web wants to see<00:10:57.150> it<00:10:57.330> it<00:10:58.140> will<00:10:58.410> not<00:10:58.590> be<00:10:58.740> a<00:10:58.770> problem<00:10:59.040> for<00:10:59.250> you 00:11:00.190 --> 00:11:00.200 align:start position:0% see it it will not be a problem for you 00:11:00.200 --> 00:11:05.120 align:start position:0% see it it will not be a problem for you and<00:11:02.840> it<00:11:03.840> will<00:11:04.080> not<00:11:04.230> be<00:11:04.380> a<00:11:04.410> problem<00:11:04.590> for<00:11:04.830> your 00:11:05.120 --> 00:11:05.130 align:start position:0% and it will not be a problem for your 00:11:05.130 --> 00:11:09.050 align:start position:0% and it will not be a problem for your users<00:11:05.490> either<00:11:05.730> because<00:11:06.330> the<00:11:07.790> performance<00:11:08.790> is 00:11:09.050 --> 00:11:09.060 align:start position:0% users either because the performance is 00:11:09.060 --> 00:11:12.020 align:start position:0% users either because the performance is guaranteed<00:11:09.890> performance<00:11:10.890> is<00:11:11.490> improving 00:11:12.020 --> 00:11:12.030 align:start position:0% guaranteed performance is improving 00:11:12.030 --> 00:11:16.850 align:start position:0% guaranteed performance is improving together<00:11:12.660> with<00:11:12.930> popularity<00:11:15.230> the<00:11:16.230> easy<00:11:16.440> part 00:11:16.850 --> 00:11:16.860 align:start position:0% together with popularity the easy part 00:11:16.860 --> 00:11:17.210 align:start position:0% together with popularity the easy part is 00:11:17.210 --> 00:11:17.220 align:start position:0% is 00:11:17.220 --> 00:11:19.129 align:start position:0% is that<00:11:17.370> there's<00:11:17.639> no<00:11:17.819> concurrent<00:11:18.329> editing<00:11:18.810> and 00:11:19.129 --> 00:11:19.139 align:start position:0% that there's no concurrent editing and 00:11:19.139 --> 00:11:22.160 align:start position:0% that there's no concurrent editing and no<00:11:19.439> comments<00:11:20.069> rating<00:11:20.610> so<00:11:21.000> we<00:11:21.240> have<00:11:21.449> styves<00:11:21.870> up 00:11:22.160 --> 00:11:22.170 align:start position:0% no comments rating so we have styves up 00:11:22.170 --> 00:11:23.720 align:start position:0% no comments rating so we have styves up the<00:11:22.379> few<00:11:22.560> difficult<00:11:22.980> problems<00:11:23.430> of<00:11:23.579> that 00:11:23.720 --> 00:11:23.730 align:start position:0% the few difficult problems of that 00:11:23.730 --> 00:11:25.309 align:start position:0% the few difficult problems of that development<00:11:24.209> in<00:11:24.509> this<00:11:24.660> particular<00:11:25.170> example 00:11:25.309 --> 00:11:25.319 align:start position:0% development in this particular example 00:11:25.319 --> 00:11:27.920 align:start position:0% development in this particular example however<00:11:26.250> it's<00:11:26.819> still<00:11:27.000> worth<00:11:27.360> looking<00:11:27.750> behind 00:11:27.920 --> 00:11:27.930 align:start position:0% however it's still worth looking behind 00:11:27.930 --> 00:11:29.869 align:start position:0% however it's still worth looking behind the<00:11:28.170> scenes<00:11:28.470> so<00:11:29.100> one<00:11:29.310> thing<00:11:29.519> that<00:11:29.730> is 00:11:29.869 --> 00:11:29.879 align:start position:0% the scenes so one thing that is 00:11:29.879 --> 00:11:33.160 align:start position:0% the scenes so one thing that is happening<00:11:29.910> here<00:11:30.660> is<00:11:30.839> that<00:11:31.459> the<00:11:32.459> blurred 00:11:33.160 --> 00:11:33.170 align:start position:0% happening here is that the blurred 00:11:33.170 --> 00:11:35.840 align:start position:0% happening here is that the blurred backgrounds<00:11:34.170> and<00:11:34.290> the<00:11:34.439> thumbnails<00:11:34.949> they<00:11:35.610> get 00:11:35.840 --> 00:11:35.850 align:start position:0% backgrounds and the thumbnails they get 00:11:35.850 --> 00:11:37.730 align:start position:0% backgrounds and the thumbnails they get generated<00:11:36.569> on<00:11:36.750> the<00:11:36.779> client<00:11:37.230> side<00:11:37.290> during 00:11:37.730 --> 00:11:37.740 align:start position:0% generated on the client side during 00:11:37.740 --> 00:11:40.340 align:start position:0% generated on the client side during upload<00:11:38.310> which<00:11:39.149> is<00:11:39.329> fine<00:11:39.600> for<00:11:39.810> a<00:11:39.870> photo<00:11:40.139> album 00:11:40.340 --> 00:11:40.350 align:start position:0% upload which is fine for a photo album 00:11:40.350 --> 00:11:42.769 align:start position:0% upload which is fine for a photo album but<00:11:41.100> let's<00:11:41.370> say<00:11:41.579> you<00:11:41.639> want<00:11:41.790> to<00:11:42.029> move<00:11:42.300> on<00:11:42.540> and 00:11:42.769 --> 00:11:42.779 align:start position:0% but let's say you want to move on and 00:11:42.779 --> 00:11:44.809 align:start position:0% but let's say you want to move on and you<00:11:42.930> want<00:11:43.079> to<00:11:43.319> do<00:11:43.529> something<00:11:43.860> distributed 00:11:44.809 --> 00:11:44.819 align:start position:0% you want to do something distributed 00:11:44.819 --> 00:11:48.110 align:start position:0% you want to do something distributed like<00:11:45.810> you<00:11:46.259> so<00:11:46.589> you<00:11:46.649> want<00:11:46.889> to<00:11:47.040> do<00:11:47.250> something 00:11:48.110 --> 00:11:48.120 align:start position:0% like you so you want to do something 00:11:48.120 --> 00:11:52.639 align:start position:0% like you so you want to do something like<00:11:48.269> YouTube<00:11:48.509> in<00:11:48.870> a<00:11:49.019> distributed<00:11:49.379> fashion<00:11:51.649> in 00:11:52.639 --> 00:11:52.649 align:start position:0% like YouTube in a distributed fashion in 00:11:52.649 --> 00:11:54.800 align:start position:0% like YouTube in a distributed fashion in that<00:11:52.980> case<00:11:53.250> you<00:11:53.430> need<00:11:53.579> to<00:11:53.790> transport<00:11:54.269> huge 00:11:54.800 --> 00:11:54.810 align:start position:0% that case you need to transport huge 00:11:54.810 --> 00:11:57.650 align:start position:0% that case you need to transport huge video<00:11:55.199> files<00:11:55.560> or<00:11:56.069> you<00:11:56.279> want<00:11:56.550> to<00:11:56.850> transform 00:11:57.650 --> 00:11:57.660 align:start position:0% video files or you want to transform 00:11:57.660 --> 00:12:00.350 align:start position:0% video files or you want to transform projections<00:11:58.620> for<00:11:58.920> immersive<00:11:59.250> panoramas<00:11:59.970> and 00:12:00.350 --> 00:12:00.360 align:start position:0% projections for immersive panoramas and 00:12:00.360 --> 00:12:01.429 align:start position:0% projections for immersive panoramas and things<00:12:00.689> like<00:12:00.870> that<00:12:01.079> which<00:12:01.290> are 00:12:01.429 --> 00:12:01.439 align:start position:0% things like that which are 00:12:01.439 --> 00:12:04.790 align:start position:0% things like that which are computationally<00:12:02.279> expensive<00:12:02.870> so<00:12:03.870> all<00:12:04.529> that 00:12:04.790 --> 00:12:04.800 align:start position:0% computationally expensive so all that 00:12:04.800 --> 00:12:06.889 align:start position:0% computationally expensive so all that stuff<00:12:05.040> can<00:12:05.430> you<00:12:05.579> do<00:12:05.759> that<00:12:05.910> in<00:12:06.180> a<00:12:06.269> mobile<00:12:06.629> phone 00:12:06.889 --> 00:12:06.899 align:start position:0% stuff can you do that in a mobile phone 00:12:06.899 --> 00:12:09.050 align:start position:0% stuff can you do that in a mobile phone well<00:12:07.319> you<00:12:07.529> can<00:12:07.800> but<00:12:08.100> you<00:12:08.220> probably<00:12:08.459> don't<00:12:08.730> want 00:12:09.050 --> 00:12:09.060 align:start position:0% well you can but you probably don't want 00:12:09.060 --> 00:12:11.809 align:start position:0% well you can but you probably don't want to<00:12:09.379> so<00:12:10.379> in<00:12:10.529> that<00:12:10.709> case<00:12:11.040> you<00:12:11.250> need<00:12:11.430> to<00:12:11.490> do 00:12:11.809 --> 00:12:11.819 align:start position:0% to so in that case you need to do 00:12:11.819 --> 00:12:16.460 align:start position:0% to so in that case you need to do delegated<00:12:12.540> computations<00:12:13.970> in<00:12:14.970> which<00:12:15.300> case<00:12:15.660> you 00:12:16.460 --> 00:12:16.470 align:start position:0% delegated computations in which case you 00:12:16.470 --> 00:12:19.280 align:start position:0% delegated computations in which case you submit<00:12:17.009> the<00:12:17.459> data<00:12:17.670> and<00:12:18.180> the<00:12:18.360> specification 00:12:19.280 --> 00:12:19.290 align:start position:0% submit the data and the specification 00:12:19.290 --> 00:12:22.819 align:start position:0% submit the data and the specification and<00:12:19.439> the<00:12:19.589> reward<00:12:20.009> and<00:12:20.300> you<00:12:21.300> want<00:12:21.829> eventually 00:12:22.819 --> 00:12:22.829 align:start position:0% and the reward and you want eventually 00:12:22.829 --> 00:12:25.249 align:start position:0% and the reward and you want eventually to<00:12:23.069> have<00:12:23.279> a<00:12:23.519> result<00:12:24.059> of<00:12:24.180> that<00:12:24.329> computation<00:12:25.079> and 00:12:25.249 --> 00:12:25.259 align:start position:0% to have a result of that computation and 00:12:25.259 --> 00:12:27.829 align:start position:0% to have a result of that computation and the<00:12:25.709> proof<00:12:25.980> that<00:12:26.279> it<00:12:26.459> is<00:12:26.490> correct<00:12:26.970> so<00:12:27.600> there's 00:12:27.829 --> 00:12:27.839 align:start position:0% the proof that it is correct so there's 00:12:27.839 --> 00:12:30.699 align:start position:0% the proof that it is correct so there's gonna<00:12:28.050> be<00:12:28.199> other<00:12:28.589> talks<00:12:29.040> in<00:12:29.850> this<00:12:30.449> session 00:12:30.699 --> 00:12:30.709 align:start position:0% gonna be other talks in this session 00:12:30.709 --> 00:12:35.329 align:start position:0% gonna be other talks in this session which<00:12:31.709> we'll<00:12:32.100> delve<00:12:32.819> into<00:12:33.149> that<00:12:34.129> what<00:12:35.129> I<00:12:35.160> would 00:12:35.329 --> 00:12:35.339 align:start position:0% which we'll delve into that what I would 00:12:35.339 --> 00:12:37.220 align:start position:0% which we'll delve into that what I would really<00:12:35.699> like<00:12:35.910> to<00:12:35.939> highlight<00:12:36.540> that<00:12:36.930> there<00:12:37.170> are 00:12:37.220 --> 00:12:37.230 align:start position:0% really like to highlight that there are 00:12:37.230 --> 00:12:39.590 align:start position:0% really like to highlight that there are two<00:12:37.410> ways<00:12:37.589> to<00:12:37.620> go<00:12:37.920> about<00:12:37.949> it<00:12:38.490> either<00:12:39.000> you 00:12:39.590 --> 00:12:39.600 align:start position:0% two ways to go about it either you 00:12:39.600 --> 00:12:42.379 align:start position:0% two ways to go about it either you specify<00:12:40.319> in<00:12:40.709> an<00:12:40.920> imperative<00:12:41.370> fashion<00:12:42.059> in<00:12:42.269> a 00:12:42.379 --> 00:12:42.389 align:start position:0% specify in an imperative fashion in a 00:12:42.389 --> 00:12:44.990 align:start position:0% specify in an imperative fashion in a special<00:12:42.930> blockchain<00:12:43.470> in<00:12:44.040> a<00:12:44.129> special<00:12:44.579> virtual 00:12:44.990 --> 00:12:45.000 align:start position:0% special blockchain in a special virtual 00:12:45.000 --> 00:12:47.059 align:start position:0% special blockchain in a special virtual machine<00:12:45.420> what<00:12:45.959> computations<00:12:46.680> you<00:12:46.860> want 00:12:47.059 --> 00:12:47.069 align:start position:0% machine what computations you want 00:12:47.069 --> 00:12:49.689 align:start position:0% machine what computations you want performed<00:12:47.699> or<00:12:48.149> you<00:12:48.389> just<00:12:48.629> make<00:12:48.959> declarations 00:12:49.689 --> 00:12:49.699 align:start position:0% performed or you just make declarations 00:12:49.699 --> 00:12:52.280 align:start position:0% performed or you just make declarations about<00:12:50.699> the<00:12:51.149> result<00:12:51.540> you<00:12:51.660> don't<00:12:51.870> care<00:12:52.110> how 00:12:52.280 --> 00:12:52.290 align:start position:0% about the result you don't care how 00:12:52.290 --> 00:12:55.749 align:start position:0% about the result you don't care how people<00:12:52.500> actually<00:12:52.980> compute<00:12:53.699> that<00:12:53.939> you<00:12:54.480> simply 00:12:55.749 --> 00:12:55.759 align:start position:0% people actually compute that you simply 00:12:55.759 --> 00:12:58.670 align:start position:0% people actually compute that you simply verify<00:12:56.759> that<00:12:56.970> it's<00:12:57.180> correct<00:12:57.600> and<00:12:57.899> then<00:12:58.470> you 00:12:58.670 --> 00:12:58.680 align:start position:0% verify that it's correct and then you 00:12:58.680 --> 00:13:01.059 align:start position:0% verify that it's correct and then you need<00:12:58.889> to<00:12:58.920> arbitrate<00:12:59.699> it<00:12:59.910> on<00:13:00.089> the<00:13:00.300> blockchain 00:13:01.059 --> 00:13:01.069 align:start position:0% need to arbitrate it on the blockchain 00:13:01.069 --> 00:13:03.230 align:start position:0% need to arbitrate it on the blockchain please<00:13:02.069> talk<00:13:02.309> to<00:13:02.339> me<00:13:02.639> after<00:13:02.970> the<00:13:03.120> presentation 00:13:03.230 --> 00:13:03.240 align:start position:0% please talk to me after the presentation 00:13:03.240 --> 00:13:06.530 align:start position:0% please talk to me after the presentation I<00:13:03.839> don't<00:13:04.079> have<00:13:04.199> enough<00:13:04.439> time<00:13:04.709> to<00:13:05.009> to<00:13:05.970> to 00:13:06.530 --> 00:13:06.540 align:start position:0% I don't have enough time to to to 00:13:06.540 --> 00:13:08.869 align:start position:0% I don't have enough time to to to explain<00:13:07.470> arbitration<00:13:08.160> here<00:13:08.370> but<00:13:08.550> I<00:13:08.579> think 00:13:08.869 --> 00:13:08.879 align:start position:0% explain arbitration here but I think 00:13:08.879 --> 00:13:10.100 align:start position:0% explain arbitration here but I think it's<00:13:09.029> really<00:13:09.269> crucial<00:13:09.449> and<00:13:09.720> a<00:13:09.870> really 00:13:10.100 --> 00:13:10.110 align:start position:0% it's really crucial and a really 00:13:10.110 --> 00:13:13.819 align:start position:0% it's really crucial and a really interesting<00:13:10.589> part<00:13:10.800> of<00:13:10.980> it<00:13:12.410> the<00:13:13.410> second 00:13:13.819 --> 00:13:13.829 align:start position:0% interesting part of it the second 00:13:13.829 --> 00:13:16.629 align:start position:0% interesting part of it the second example<00:13:14.790> is<00:13:15.120> something<00:13:15.629> like<00:13:15.779> Dropbox 00:13:16.629 --> 00:13:16.639 align:start position:0% example is something like Dropbox 00:13:16.639 --> 00:13:18.619 align:start position:0% example is something like Dropbox distributing<00:13:17.639> Dropbox<00:13:18.089> there's<00:13:18.269> a<00:13:18.360> huge 00:13:18.619 --> 00:13:18.629 align:start position:0% distributing Dropbox there's a huge 00:13:18.629 --> 00:13:20.900 align:start position:0% distributing Dropbox there's a huge demand<00:13:18.959> for<00:13:19.050> that<00:13:19.199> kind<00:13:19.589> of<00:13:19.680> stuff 00:13:20.900 --> 00:13:20.910 align:start position:0% demand for that kind of stuff 00:13:20.910 --> 00:13:24.829 align:start position:0% demand for that kind of stuff it<00:13:21.449> has<00:13:22.050> a<00:13:22.680> web<00:13:23.309> app<00:13:23.519> and<00:13:23.759> a<00:13:24.360> locally 00:13:24.829 --> 00:13:24.839 align:start position:0% it has a web app and a locally 00:13:24.839 --> 00:13:26.749 align:start position:0% it has a web app and a locally synchronized<00:13:25.380> folder<00:13:25.829> the<00:13:26.040> first<00:13:26.220> one<00:13:26.550> is 00:13:26.749 --> 00:13:26.759 align:start position:0% synchronized folder the first one is 00:13:26.759 --> 00:13:29.049 align:start position:0% synchronized folder the first one is already<00:13:27.449> in<00:13:27.750> the<00:13:27.959> works<00:13:28.139> it's 00:13:29.049 --> 00:13:29.059 align:start position:0% already in the works it's 00:13:29.059 --> 00:13:32.049 align:start position:0% already in the works it's I<00:13:29.869> mean<00:13:30.439> it's<00:13:30.619> already<00:13:30.829> usable<00:13:31.519> it's<00:13:31.759> just<00:13:31.939> not 00:13:32.049 --> 00:13:32.059 align:start position:0% I mean it's already usable it's just not 00:13:32.059 --> 00:13:35.919 align:start position:0% I mean it's already usable it's just not feature<00:13:32.299> complete<00:13:33.579> again<00:13:34.579> here<00:13:35.449> you<00:13:35.719> have 00:13:35.919 --> 00:13:35.929 align:start position:0% feature complete again here you have 00:13:35.929 --> 00:13:38.409 align:start position:0% feature complete again here you have concurrent<00:13:36.499> changes<00:13:37.219> but<00:13:37.669> they're<00:13:37.849> not<00:13:38.029> not 00:13:38.409 --> 00:13:38.419 align:start position:0% concurrent changes but they're not not 00:13:38.419 --> 00:13:40.149 align:start position:0% concurrent changes but they're not not typical<00:13:38.929> when<00:13:39.079> you're<00:13:39.259> syncing<00:13:39.649> between<00:13:39.679> two 00:13:40.149 --> 00:13:40.159 align:start position:0% typical when you're syncing between two 00:13:40.159 --> 00:13:43.889 align:start position:0% typical when you're syncing between two devices<00:13:40.459> of<00:13:40.849> yours<00:13:41.179> or<00:13:41.359> between<00:13:41.629> a<00:13:41.749> few<00:13:41.989> users 00:13:43.889 --> 00:13:43.899 align:start position:0% devices of yours or between a few users 00:13:43.899 --> 00:13:48.369 align:start position:0% devices of yours or between a few users and<00:13:45.159> also<00:13:46.209> there's<00:13:47.209> gonna<00:13:47.599> be<00:13:47.839> a<00:13:47.869> separate 00:13:48.369 --> 00:13:48.379 align:start position:0% and also there's gonna be a separate 00:13:48.379 --> 00:13:50.859 align:start position:0% and also there's gonna be a separate talk<00:13:48.739> about<00:13:49.339> implementing<00:13:50.209> something<00:13:50.659> like 00:13:50.859 --> 00:13:50.869 align:start position:0% talk about implementing something like 00:13:50.869 --> 00:13:55.889 align:start position:0% talk about implementing something like github<00:13:51.319> in<00:13:51.769> this<00:13:52.489> distributed<00:13:53.329> fashion<00:13:54.339> so 00:13:55.889 --> 00:13:55.899 align:start position:0% github in this distributed fashion so 00:13:55.899 --> 00:13:59.619 align:start position:0% github in this distributed fashion so the<00:13:56.899> third<00:13:57.199> example<00:13:58.029> which<00:13:59.029> would<00:13:59.359> be<00:13:59.599> a 00:13:59.619 --> 00:13:59.629 align:start position:0% the third example which would be a 00:13:59.629 --> 00:14:02.199 align:start position:0% the third example which would be a distributed<00:14:00.439> social<00:14:00.889> network<00:14:01.339> and<00:14:01.639> the 00:14:02.199 --> 00:14:02.209 align:start position:0% distributed social network and the 00:14:02.209 --> 00:14:04.959 align:start position:0% distributed social network and the fourth<00:14:02.479> example<00:14:02.689> a<00:14:03.289> map<00:14:03.649> or<00:14:03.919> a<00:14:03.969> encyclopedia 00:14:04.959 --> 00:14:04.969 align:start position:0% fourth example a map or a encyclopedia 00:14:04.969 --> 00:14:07.509 align:start position:0% fourth example a map or a encyclopedia with<00:14:05.149> no<00:14:05.329> official<00:14:05.839> truth<00:14:06.079> so<00:14:06.859> these<00:14:07.189> things 00:14:07.509 --> 00:14:07.519 align:start position:0% with no official truth so these things 00:14:07.519 --> 00:14:10.059 align:start position:0% with no official truth so these things they<00:14:07.969> are<00:14:07.999> pure<00:14:08.659> vapor<00:14:08.959> where<00:14:09.499> now<00:14:09.739> although 00:14:10.059 --> 00:14:10.069 align:start position:0% they are pure vapor where now although 00:14:10.069 --> 00:14:11.889 align:start position:0% they are pure vapor where now although I'm<00:14:10.489> aware<00:14:10.789> of<00:14:10.849> some<00:14:11.239> teams<00:14:11.479> that<00:14:11.599> are<00:14:11.869> working 00:14:11.889 --> 00:14:11.899 align:start position:0% I'm aware of some teams that are working 00:14:11.899 --> 00:14:15.519 align:start position:0% I'm aware of some teams that are working on<00:14:12.409> projects<00:14:12.889> like<00:14:12.919> this<00:14:13.279> so<00:14:13.639> maybe<00:14:14.599> we<00:14:15.319> will 00:14:15.519 --> 00:14:15.529 align:start position:0% on projects like this so maybe we will 00:14:15.529 --> 00:14:18.249 align:start position:0% on projects like this so maybe we will see<00:14:15.739> something<00:14:16.009> like<00:14:16.159> this<00:14:16.699> in<00:14:17.029> the<00:14:17.209> not<00:14:18.049> very 00:14:18.249 --> 00:14:18.259 align:start position:0% see something like this in the not very 00:14:18.259 --> 00:14:22.329 align:start position:0% see something like this in the not very distant<00:14:18.769> future<00:14:20.199> so<00:14:21.199> there<00:14:21.379> are<00:14:21.469> also<00:14:21.589> ways<00:14:22.009> of 00:14:22.329 --> 00:14:22.339 align:start position:0% distant future so there are also ways of 00:14:22.339 --> 00:14:27.429 align:start position:0% distant future so there are also ways of doing<00:14:23.079> doing<00:14:24.079> things<00:14:24.349> like<00:14:24.439> this<00:14:26.259> in<00:14:27.259> a 00:14:27.429 --> 00:14:27.439 align:start position:0% doing doing things like this in a 00:14:27.439 --> 00:14:28.629 align:start position:0% doing doing things like this in a distributed<00:14:27.829> fashion 00:14:28.629 --> 00:14:28.639 align:start position:0% distributed fashion 00:14:28.639 --> 00:14:30.699 align:start position:0% distributed fashion moreover<00:14:29.299> doing<00:14:29.869> it<00:14:30.049> in<00:14:30.199> a<00:14:30.319> distributed 00:14:30.699 --> 00:14:30.709 align:start position:0% moreover doing it in a distributed 00:14:30.709 --> 00:14:32.969 align:start position:0% moreover doing it in a distributed fashion<00:14:31.009> in<00:14:31.459> a<00:14:31.549> Content<00:14:31.939> address<00:14:32.299> storage 00:14:32.969 --> 00:14:32.979 align:start position:0% fashion in a Content address storage 00:14:32.979 --> 00:14:35.499 align:start position:0% fashion in a Content address storage actually<00:14:33.979> opens<00:14:34.339> up<00:14:34.519> possibilities<00:14:34.669> which 00:14:35.499 --> 00:14:35.509 align:start position:0% actually opens up possibilities which 00:14:35.509 --> 00:14:37.659 align:start position:0% actually opens up possibilities which are<00:14:35.719> plain<00:14:35.989> impossible<00:14:36.199> to<00:14:36.859> do<00:14:36.979> in<00:14:37.219> the<00:14:37.369> web 00:14:37.659 --> 00:14:37.669 align:start position:0% are plain impossible to do in the web 00:14:37.669 --> 00:14:40.839 align:start position:0% are plain impossible to do in the web 2.0<00:14:38.419> way<00:14:38.599> so<00:14:39.289> thank<00:14:39.979> you<00:14:40.069> for<00:14:40.219> your<00:14:40.399> time<00:14:40.639> and 00:14:40.839 --> 00:14:40.849 align:start position:0% 2.0 way so thank you for your time and 00:14:40.849 --> 00:14:42.759 align:start position:0% 2.0 way so thank you for your time and if<00:14:41.389> you<00:14:41.539> will<00:14:41.689> have<00:14:41.899> questions<00:14:42.109> I<00:14:42.559> will<00:14:42.619> be 00:14:42.759 --> 00:14:42.769 align:start position:0% if you will have questions I will be 00:14:42.769 --> 00:14:45.939 align:start position:0% if you will have questions I will be happy<00:14:43.279> to<00:14:43.309> answer<00:14:43.429> them