WEBVTT Kind: captions Language: en 00:00:09.180 --> 00:00:17.020 align:start position:0% [Music] 00:00:17.020 --> 00:00:17.030 align:start position:0% 00:00:17.030 --> 00:00:21.580 align:start position:0% yeah<00:00:17.420> hello<00:00:17.720> everyone<00:00:19.330> I'm<00:00:20.330> very<00:00:21.170> happy<00:00:21.470> to 00:00:21.580 --> 00:00:21.590 align:start position:0% yeah hello everyone I'm very happy to 00:00:21.590 --> 00:00:22.960 align:start position:0% yeah hello everyone I'm very happy to start<00:00:21.920> us<00:00:22.010> off<00:00:22.130> on<00:00:22.310> the<00:00:22.400> update<00:00:22.700> from<00:00:22.820> the 00:00:22.960 --> 00:00:22.970 align:start position:0% start us off on the update from the 00:00:22.970 --> 00:00:27.070 align:start position:0% start us off on the update from the swarm<00:00:23.210> team<00:00:24.070> so<00:00:25.390> today<00:00:26.390> we're<00:00:26.600> gonna<00:00:26.720> talk<00:00:27.020> a 00:00:27.070 --> 00:00:27.080 align:start position:0% swarm team so today we're gonna talk a 00:00:27.080 --> 00:00:30.670 align:start position:0% swarm team so today we're gonna talk a little<00:00:27.320> bit<00:00:27.500> about<00:00:28.480> well<00:00:29.480> what<00:00:29.750> swarm<00:00:30.050> is<00:00:30.200> just 00:00:30.670 --> 00:00:30.680 align:start position:0% little bit about well what swarm is just 00:00:30.680 --> 00:00:32.549 align:start position:0% little bit about well what swarm is just make<00:00:31.010> sure<00:00:31.190> we're<00:00:31.310> all<00:00:31.400> in<00:00:31.430> the<00:00:31.610> same<00:00:31.640> page 00:00:32.549 --> 00:00:32.559 align:start position:0% make sure we're all in the same page 00:00:32.559 --> 00:00:35.020 align:start position:0% make sure we're all in the same page what<00:00:33.559> the<00:00:33.770> status<00:00:34.100> of<00:00:34.220> the<00:00:34.310> swarm<00:00:34.550> project<00:00:34.910> is 00:00:35.020 --> 00:00:35.030 align:start position:0% what the status of the swarm project is 00:00:35.030 --> 00:00:36.640 align:start position:0% what the status of the swarm project is and<00:00:35.300> also<00:00:35.450> where<00:00:35.690> it's<00:00:35.840> going<00:00:36.200> we've<00:00:36.320> got<00:00:36.470> some 00:00:36.640 --> 00:00:36.650 align:start position:0% and also where it's going we've got some 00:00:36.650 --> 00:00:38.890 align:start position:0% and also where it's going we've got some new<00:00:36.770> sub<00:00:37.070> projects<00:00:37.640> it's<00:00:38.480> going<00:00:38.720> in<00:00:38.810> different 00:00:38.890 --> 00:00:38.900 align:start position:0% new sub projects it's going in different 00:00:38.900 --> 00:00:43.450 align:start position:0% new sub projects it's going in different directions<00:00:39.140> and<00:00:40.390> the<00:00:41.390> general<00:00:42.190> scope<00:00:43.190> of<00:00:43.400> the 00:00:43.450 --> 00:00:43.460 align:start position:0% directions and the general scope of the 00:00:43.460 --> 00:00:45.910 align:start position:0% directions and the general scope of the swarm<00:00:43.700> has<00:00:43.850> grown<00:00:44.329> and<00:00:44.840> so<00:00:45.590> we're<00:00:45.710> going<00:00:45.829> to 00:00:45.910 --> 00:00:45.920 align:start position:0% swarm has grown and so we're going to 00:00:45.920 --> 00:00:47.920 align:start position:0% swarm has grown and so we're going to talk<00:00:46.070> about<00:00:46.100> where<00:00:46.550> we're<00:00:46.670> going<00:00:46.880> but<00:00:47.780> I'm 00:00:47.920 --> 00:00:47.930 align:start position:0% talk about where we're going but I'm 00:00:47.930 --> 00:00:49.389 align:start position:0% talk about where we're going but I'm just<00:00:47.989> gonna<00:00:48.200> start<00:00:48.530> you<00:00:48.649> off<00:00:48.680> with<00:00:49.070> what<00:00:49.370> is 00:00:49.389 --> 00:00:49.399 align:start position:0% just gonna start you off with what is 00:00:49.399 --> 00:00:53.310 align:start position:0% just gonna start you off with what is swarm<00:00:49.850> to<00:00:50.420> make<00:00:50.570> sure<00:00:50.750> we're<00:00:50.899> all<00:00:51.160> you<00:00:52.160> know 00:00:53.310 --> 00:00:53.320 align:start position:0% swarm to make sure we're all you know 00:00:53.320 --> 00:00:56.110 align:start position:0% swarm to make sure we're all you know understand<00:00:54.320> each<00:00:54.440> other<00:00:54.649> you<00:00:54.890> probably<00:00:55.880> know 00:00:56.110 --> 00:00:56.120 align:start position:0% understand each other you probably know 00:00:56.120 --> 00:00:59.290 align:start position:0% understand each other you probably know swarm<00:00:56.809> does<00:00:57.230> a<00:00:57.530> network<00:00:57.950> of<00:00:58.070> computers<00:00:58.579> share 00:00:59.290 --> 00:00:59.300 align:start position:0% swarm does a network of computers share 00:00:59.300 --> 00:01:03.719 align:start position:0% swarm does a network of computers share data<00:00:59.570> in<00:00:59.989> a<00:01:00.320> decentralized<00:01:00.980> way<00:01:01.960> to<00:01:02.960> give<00:01:03.140> us<00:01:03.380> a 00:01:03.719 --> 00:01:03.729 align:start position:0% data in a decentralized way to give us a 00:01:03.729 --> 00:01:07.090 align:start position:0% data in a decentralized way to give us a peer-to-peer<00:01:04.729> decentralized<00:01:05.690> storage<00:01:06.110> with 00:01:07.090 --> 00:01:07.100 align:start position:0% peer-to-peer decentralized storage with 00:01:07.100 --> 00:01:11.170 align:start position:0% peer-to-peer decentralized storage with all<00:01:07.220> the<00:01:07.370> benefits<00:01:07.850> that<00:01:07.970> come<00:01:08.330> from<00:01:10.180> from 00:01:11.170 --> 00:01:11.180 align:start position:0% all the benefits that come from from 00:01:11.180 --> 00:01:13.380 align:start position:0% all the benefits that come from from being<00:01:11.450> a<00:01:11.540> peer-to-peer<00:01:12.049> network<00:01:12.590> such<00:01:13.130> as 00:01:13.380 --> 00:01:13.390 align:start position:0% being a peer-to-peer network such as 00:01:13.390 --> 00:01:17.109 align:start position:0% being a peer-to-peer network such as resilience<00:01:14.390> against<00:01:15.170> network<00:01:15.890> outages<00:01:16.280> DDoS 00:01:17.109 --> 00:01:17.119 align:start position:0% resilience against network outages DDoS 00:01:17.119 --> 00:01:21.940 align:start position:0% resilience against network outages DDoS attacks<00:01:17.479> and<00:01:17.690> the<00:01:17.750> rest<00:01:19.690> but<00:01:20.740> what<00:01:21.740> you<00:01:21.830> may 00:01:21.940 --> 00:01:21.950 align:start position:0% attacks and the rest but what you may 00:01:21.950 --> 00:01:23.620 align:start position:0% attacks and the rest but what you may not<00:01:22.040> know<00:01:22.130> it's<00:01:22.369> really<00:01:23.119> the<00:01:23.210> same 00:01:23.620 --> 00:01:23.630 align:start position:0% not know it's really the same 00:01:23.630 --> 00:01:27.609 align:start position:0% not know it's really the same connections<00:01:24.470> as<00:01:24.850> etherium<00:01:25.880> so<00:01:26.500> same<00:01:27.500> with 00:01:27.609 --> 00:01:27.619 align:start position:0% connections as etherium so same with 00:01:27.619 --> 00:01:29.350 align:start position:0% connections as etherium so same with Nazareth<00:01:28.100> because<00:01:28.250> right<00:01:28.549> now<00:01:28.729> swarm<00:01:29.030> client 00:01:29.350 --> 00:01:29.360 align:start position:0% Nazareth because right now swarm client 00:01:29.360 --> 00:01:31.510 align:start position:0% Nazareth because right now swarm client is<00:01:29.450> still<00:01:29.540> separate<00:01:30.020> but<00:01:30.680> the<00:01:30.890> vision<00:01:31.369> is<00:01:31.490> that 00:01:31.510 --> 00:01:31.520 align:start position:0% is still separate but the vision is that 00:01:31.520 --> 00:01:33.789 align:start position:0% is still separate but the vision is that it's<00:01:32.330> part<00:01:32.750> of<00:01:32.869> the<00:01:32.930> same<00:01:33.140> package<00:01:33.530> of 00:01:33.789 --> 00:01:33.799 align:start position:0% it's part of the same package of 00:01:33.799 --> 00:01:35.710 align:start position:0% it's part of the same package of protocols<00:01:34.310> that<00:01:34.490> would<00:01:34.640> run<00:01:34.820> over<00:01:35.119> there<00:01:35.240> p2p 00:01:35.710 --> 00:01:35.720 align:start position:0% protocols that would run over there p2p 00:01:35.720 --> 00:01:38.140 align:start position:0% protocols that would run over there p2p so<00:01:35.990> your<00:01:36.229> swarm<00:01:36.560> know<00:01:36.710> your<00:01:37.040> eath<00:01:37.610> node<00:01:37.880> could 00:01:38.140 --> 00:01:38.150 align:start position:0% so your swarm know your eath node could 00:01:38.150 --> 00:01:40.000 align:start position:0% so your swarm know your eath node could talk<00:01:38.450> the<00:01:38.720> eath<00:01:38.869> protocol<00:01:39.380> or<00:01:39.650> the<00:01:39.680> swarm 00:01:40.000 --> 00:01:40.010 align:start position:0% talk the eath protocol or the swarm 00:01:40.010 --> 00:01:43.410 align:start position:0% talk the eath protocol or the swarm protocol<00:01:40.960> all<00:01:41.960> of<00:01:42.350> the<00:01:42.470> same<00:01:42.650> connections<00:01:43.130> so 00:01:43.410 --> 00:01:43.420 align:start position:0% protocol all of the same connections so 00:01:43.420 --> 00:01:45.640 align:start position:0% protocol all of the same connections so it's<00:01:44.420> really<00:01:44.570> tightly<00:01:44.990> integrated<00:01:45.500> with 00:01:45.640 --> 00:01:45.650 align:start position:0% it's really tightly integrated with 00:01:45.650 --> 00:01:49.450 align:start position:0% it's really tightly integrated with aetherium<00:01:46.750> so<00:01:47.750> let<00:01:47.990> me<00:01:48.049> give<00:01:48.200> you<00:01:48.290> the<00:01:48.460> basic 00:01:49.450 --> 00:01:49.460 align:start position:0% aetherium so let me give you the basic 00:01:49.460 --> 00:01:51.670 align:start position:0% aetherium so let me give you the basic first<00:01:49.759> use<00:01:50.000> case<00:01:50.090> the<00:01:50.630> sort<00:01:50.810> of<00:01:50.869> baby<00:01:51.080> example 00:01:51.670 --> 00:01:51.680 align:start position:0% first use case the sort of baby example 00:01:51.680 --> 00:01:55.300 align:start position:0% first use case the sort of baby example of<00:01:51.860> what<00:01:52.490> swarm<00:01:52.790> is<00:01:52.909> for<00:01:53.619> the<00:01:54.619> decentralized 00:01:55.300 --> 00:01:55.310 align:start position:0% of what swarm is for the decentralized 00:01:55.310 --> 00:01:58.300 align:start position:0% of what swarm is for the decentralized storage<00:01:55.700> of<00:01:55.850> app<00:01:56.240> data<00:01:56.799> so<00:01:57.799> the<00:01:58.040> blockchain 00:01:58.300 --> 00:01:58.310 align:start position:0% storage of app data so the blockchain 00:01:58.310 --> 00:02:01.109 align:start position:0% storage of app data so the blockchain the<00:01:58.970> iam<00:01:59.240> blockchain<00:01:59.630> is<00:01:59.780> great<00:01:59.990> to<00:02:00.380> store 00:02:01.109 --> 00:02:01.119 align:start position:0% the iam blockchain is great to store 00:02:01.119 --> 00:02:03.340 align:start position:0% the iam blockchain is great to store critical<00:02:02.119> information<00:02:02.360> about<00:02:02.869> your<00:02:02.960> DAP 00:02:03.340 --> 00:02:03.350 align:start position:0% critical information about your DAP 00:02:03.350 --> 00:02:05.380 align:start position:0% critical information about your DAP maybe<00:02:03.500> user<00:02:04.130> name<00:02:04.369> registrations<00:02:05.210> or 00:02:05.380 --> 00:02:05.390 align:start position:0% maybe user name registrations or 00:02:05.390 --> 00:02:07.810 align:start position:0% maybe user name registrations or something<00:02:05.750> like<00:02:05.869> that<00:02:06.159> but<00:02:07.159> your<00:02:07.340> dad<00:02:07.490> still 00:02:07.810 --> 00:02:07.820 align:start position:0% something like that but your dad still 00:02:07.820 --> 00:02:11.229 align:start position:0% something like that but your dad still needs<00:02:08.110> images<00:02:09.110> HTML<00:02:09.759> Javascript<00:02:10.759> and<00:02:10.970> all<00:02:11.120> the 00:02:11.229 --> 00:02:11.239 align:start position:0% needs images HTML Javascript and all the 00:02:11.239 --> 00:02:13.150 align:start position:0% needs images HTML Javascript and all the rest<00:02:11.420> and<00:02:11.690> right<00:02:12.170> now<00:02:12.349> you<00:02:12.410> probably<00:02:12.770> need<00:02:13.130> to 00:02:13.150 --> 00:02:13.160 align:start position:0% rest and right now you probably need to 00:02:13.160 --> 00:02:14.590 align:start position:0% rest and right now you probably need to host<00:02:13.430> them<00:02:13.640> on<00:02:13.730> a<00:02:13.790> server 00:02:14.590 --> 00:02:14.600 align:start position:0% host them on a server 00:02:14.600 --> 00:02:16.810 align:start position:0% host them on a server and<00:02:14.690> swarm<00:02:15.560> is<00:02:15.770> there<00:02:16.010> to<00:02:16.190> allow<00:02:16.400> us<00:02:16.550> to<00:02:16.670> have 00:02:16.810 --> 00:02:16.820 align:start position:0% and swarm is there to allow us to have 00:02:16.820 --> 00:02:20.020 align:start position:0% and swarm is there to allow us to have this<00:02:16.970> in<00:02:17.240> a<00:02:17.330> completely<00:02:17.840> decentralized<00:02:19.030> way 00:02:20.020 --> 00:02:20.030 align:start position:0% this in a completely decentralized way 00:02:20.030 --> 00:02:22.570 align:start position:0% this in a completely decentralized way so<00:02:20.140> here's<00:02:21.140> how<00:02:21.260> that<00:02:21.320> would<00:02:21.590> work<00:02:21.620> you'd<00:02:22.340> go 00:02:22.570 --> 00:02:22.580 align:start position:0% so here's how that would work you'd go 00:02:22.580 --> 00:02:25.090 align:start position:0% so here's how that would work you'd go to<00:02:22.640> your<00:02:22.850> swarm<00:02:23.270> enabled<00:02:23.570> browser<00:02:23.810> and<00:02:24.170> type 00:02:25.090 --> 00:02:25.100 align:start position:0% to your swarm enabled browser and type 00:02:25.100 --> 00:02:28.360 align:start position:0% to your swarm enabled browser and type bzz<00:02:25.790> which<00:02:26.180> is<00:02:26.360> a<00:02:26.390> swarm<00:02:26.750> protocol<00:02:27.230> the<00:02:28.190> name 00:02:28.360 --> 00:02:28.370 align:start position:0% bzz which is a swarm protocol the name 00:02:28.370 --> 00:02:32.050 align:start position:0% bzz which is a swarm protocol the name of<00:02:28.550> your<00:02:28.790> DAP<00:02:29.180> eath<00:02:30.070> then<00:02:31.070> the<00:02:31.490> theorem<00:02:31.850> named 00:02:32.050 --> 00:02:32.060 align:start position:0% of your DAP eath then the theorem named 00:02:32.060 --> 00:02:34.030 align:start position:0% of your DAP eath then the theorem named service<00:02:32.450> would<00:02:32.630> turn<00:02:32.870> that<00:02:33.080> name<00:02:33.470> dot<00:02:33.770> eath 00:02:34.030 --> 00:02:34.040 align:start position:0% service would turn that name dot eath 00:02:34.040 --> 00:02:35.130 align:start position:0% service would turn that name dot eath into<00:02:34.460> a<00:02:34.490> hash 00:02:35.130 --> 00:02:35.140 align:start position:0% into a hash 00:02:35.140 --> 00:02:38.920 align:start position:0% into a hash so<00:02:36.140> the<00:02:36.320> ENS<00:02:36.650> record<00:02:37.070> has<00:02:37.700> an<00:02:38.090> address<00:02:38.600> field 00:02:38.920 --> 00:02:38.930 align:start position:0% so the ENS record has an address field 00:02:38.930 --> 00:02:40.630 align:start position:0% so the ENS record has an address field where<00:02:39.230> you<00:02:39.260> can<00:02:39.350> store<00:02:39.710> your<00:02:39.740> wallet<00:02:40.220> address 00:02:40.630 --> 00:02:40.640 align:start position:0% where you can store your wallet address 00:02:40.640 --> 00:02:42.760 align:start position:0% where you can store your wallet address and<00:02:40.850> that's<00:02:41.000> what<00:02:41.240> address<00:02:42.020> would<00:02:42.350> get<00:02:42.530> paid 00:02:42.760 --> 00:02:42.770 align:start position:0% and that's what address would get paid 00:02:42.770 --> 00:02:45.220 align:start position:0% and that's what address would get paid if<00:02:43.040> somebody<00:02:43.370> sends<00:02:43.790> payment<00:02:44.510> to<00:02:44.840> that<00:02:44.990> name 00:02:45.220 --> 00:02:45.230 align:start position:0% if somebody sends payment to that name 00:02:45.230 --> 00:02:48.160 align:start position:0% if somebody sends payment to that name but<00:02:46.190> the<00:02:46.340> standard<00:02:46.730> ENS<00:02:47.090> resolver<00:02:47.630> also<00:02:47.990> has<00:02:48.140> a 00:02:48.160 --> 00:02:48.170 align:start position:0% but the standard ENS resolver also has a 00:02:48.170 --> 00:02:51.430 align:start position:0% but the standard ENS resolver also has a field<00:02:48.530> called<00:02:48.890> content<00:02:49.610> and<00:02:49.940> in<00:02:50.810> that<00:02:51.020> you<00:02:51.290> can 00:02:51.430 --> 00:02:51.440 align:start position:0% field called content and in that you can 00:02:51.440 --> 00:02:54.340 align:start position:0% field called content and in that you can store<00:02:51.680> a<00:02:51.710> hash<00:02:52.300> that's<00:02:53.300> referencing<00:02:53.810> content 00:02:54.340 --> 00:02:54.350 align:start position:0% store a hash that's referencing content 00:02:54.350 --> 00:02:58.000 align:start position:0% store a hash that's referencing content on<00:02:54.530> swarm<00:02:55.100> for<00:02:55.400> example<00:02:55.850> so<00:02:56.480> you<00:02:56.800> use<00:02:57.800> this 00:02:58.000 --> 00:02:58.010 align:start position:0% on swarm for example so you use this 00:02:58.010 --> 00:03:00.340 align:start position:0% on swarm for example so you use this hash<00:02:58.280> of<00:02:58.580> content<00:02:59.180> to<00:02:59.420> query<00:02:59.750> your<00:02:59.870> swarm 00:03:00.340 --> 00:03:00.350 align:start position:0% hash of content to query your swarm 00:03:00.350 --> 00:03:03.730 align:start position:0% hash of content to query your swarm peers<00:03:00.650> for<00:03:01.190> the<00:03:01.280> data<00:03:01.490> and<00:03:01.880> in<00:03:02.810> return<00:03:03.140> they 00:03:03.730 --> 00:03:03.740 align:start position:0% peers for the data and in return they 00:03:03.740 --> 00:03:06.490 align:start position:0% peers for the data and in return they will<00:03:03.890> supply<00:03:04.160> the<00:03:04.280> data<00:03:04.580> to<00:03:05.180> you<00:03:05.300> and<00:03:05.570> anyone 00:03:06.490 --> 00:03:06.500 align:start position:0% will supply the data to you and anyone 00:03:06.500 --> 00:03:08.170 align:start position:0% will supply the data to you and anyone who<00:03:06.620> supplies<00:03:06.980> you<00:03:07.250> with<00:03:07.370> data<00:03:07.550> that<00:03:07.730> you<00:03:07.970> want 00:03:08.170 --> 00:03:08.180 align:start position:0% who supplies you with data that you want 00:03:08.180 --> 00:03:10.030 align:start position:0% who supplies you with data that you want you<00:03:08.390> compensate<00:03:08.930> them<00:03:09.140> using<00:03:09.590> a<00:03:09.650> theorem 00:03:10.030 --> 00:03:10.040 align:start position:0% you compensate them using a theorem 00:03:10.040 --> 00:03:12.760 align:start position:0% you compensate them using a theorem based<00:03:10.250> micropayments<00:03:10.880> and<00:03:11.330> then<00:03:12.260> the<00:03:12.620> last 00:03:12.760 --> 00:03:12.770 align:start position:0% based micropayments and then the last 00:03:12.770 --> 00:03:15.280 align:start position:0% based micropayments and then the last step<00:03:13.040> is<00:03:13.310> to<00:03:13.700> just<00:03:13.880> use<00:03:14.180> that<00:03:14.660> data<00:03:14.870> to<00:03:15.140> render 00:03:15.280 --> 00:03:15.290 align:start position:0% step is to just use that data to render 00:03:15.290 --> 00:03:19.060 align:start position:0% step is to just use that data to render your<00:03:15.590> DAP<00:03:15.800> so<00:03:16.870> the<00:03:17.870> hash<00:03:18.050> gives<00:03:18.320> you<00:03:18.410> integrity 00:03:19.060 --> 00:03:19.070 align:start position:0% your DAP so the hash gives you integrity 00:03:19.070 --> 00:03:20.620 align:start position:0% your DAP so the hash gives you integrity protection<00:03:19.250> you<00:03:19.880> don't<00:03:19.910> care<00:03:20.210> where<00:03:20.360> the<00:03:20.450> data 00:03:20.620 --> 00:03:20.630 align:start position:0% protection you don't care where the data 00:03:20.630 --> 00:03:22.090 align:start position:0% protection you don't care where the data comes<00:03:20.840> from<00:03:21.110> you<00:03:21.260> know<00:03:21.290> it's<00:03:21.560> the<00:03:21.710> right<00:03:21.830> data 00:03:22.090 --> 00:03:22.100 align:start position:0% comes from you know it's the right data 00:03:22.100 --> 00:03:25.450 align:start position:0% comes from you know it's the right data and<00:03:22.600> gives<00:03:23.600> us<00:03:23.750> a<00:03:23.900> server<00:03:24.410> less<00:03:24.680> completely 00:03:25.450 --> 00:03:25.460 align:start position:0% and gives us a server less completely 00:03:25.460 --> 00:03:30.490 align:start position:0% and gives us a server less completely decentralized<00:03:25.820> way<00:03:26.150> to<00:03:26.840> host<00:03:27.110> Bond<00:03:27.890> apps<00:03:29.500> so 00:03:30.490 --> 00:03:30.500 align:start position:0% decentralized way to host Bond apps so 00:03:30.500 --> 00:03:33.070 align:start position:0% decentralized way to host Bond apps so that's<00:03:30.650> great<00:03:30.860> so<00:03:31.160> let<00:03:32.150> me<00:03:32.240> also<00:03:32.600> tell<00:03:32.990> you 00:03:33.070 --> 00:03:33.080 align:start position:0% that's great so let me also tell you 00:03:33.080 --> 00:03:36.010 align:start position:0% that's great so let me also tell you what's<00:03:33.290> happening<00:03:33.620> under<00:03:33.920> the<00:03:33.950> hood<00:03:34.630> on<00:03:35.630> swarm 00:03:36.010 --> 00:03:36.020 align:start position:0% what's happening under the hood on swarm 00:03:36.020 --> 00:03:39.660 align:start position:0% what's happening under the hood on swarm when<00:03:36.530> you<00:03:36.650> have<00:03:36.800> a<00:03:36.830> file<00:03:37.160> or<00:03:37.370> any<00:03:37.520> content 00:03:39.660 --> 00:03:39.670 align:start position:0% when you have a file or any content 00:03:39.670 --> 00:03:42.310 align:start position:0% when you have a file or any content swarm<00:03:40.670> is<00:03:40.760> agnostic<00:03:41.270> to<00:03:41.300> what<00:03:41.600> the<00:03:41.810> content<00:03:42.020> is 00:03:42.310 --> 00:03:42.320 align:start position:0% swarm is agnostic to what the content is 00:03:42.320 --> 00:03:44.440 align:start position:0% swarm is agnostic to what the content is it's<00:03:42.620> gonna<00:03:42.830> take<00:03:43.340> anything<00:03:43.610> you<00:03:43.790> throw<00:03:44.120> at<00:03:44.210> it 00:03:44.440 --> 00:03:44.450 align:start position:0% it's gonna take anything you throw at it 00:03:44.450 --> 00:03:46.930 align:start position:0% it's gonna take anything you throw at it and<00:03:44.660> break<00:03:45.230> it<00:03:45.380> into<00:03:45.500> little<00:03:45.590> chunks<00:03:45.830> but<00:03:46.610> for 00:03:46.930 --> 00:03:46.940 align:start position:0% and break it into little chunks but for 00:03:46.940 --> 00:03:51.430 align:start position:0% and break it into little chunks but for kilobyte<00:03:47.450> each<00:03:48.670> and<00:03:49.670> the<00:03:50.480> hashes<00:03:50.930> of<00:03:51.170> those 00:03:51.430 --> 00:03:51.440 align:start position:0% kilobyte each and the hashes of those 00:03:51.440 --> 00:03:54.970 align:start position:0% kilobyte each and the hashes of those chunks<00:03:51.950> are<00:03:52.360> collected<00:03:53.360> into<00:03:53.810> a<00:03:53.840> Merkle<00:03:54.560> tree 00:03:54.970 --> 00:03:54.980 align:start position:0% chunks are collected into a Merkle tree 00:03:54.980 --> 00:03:57.310 align:start position:0% chunks are collected into a Merkle tree everything<00:03:55.610> is<00:03:55.730> murk<00:03:55.910> alized<00:03:56.330> and<00:03:56.450> the<00:03:57.170> root 00:03:57.310 --> 00:03:57.320 align:start position:0% everything is murk alized and the root 00:03:57.320 --> 00:03:59.170 align:start position:0% everything is murk alized and the root hash<00:03:57.560> of<00:03:57.740> that<00:03:57.770> Merkle<00:03:58.190> tree<00:03:58.340> is<00:03:58.490> the<00:03:58.640> ID<00:03:58.850> of 00:03:59.170 --> 00:03:59.180 align:start position:0% hash of that Merkle tree is the ID of 00:03:59.180 --> 00:04:02.860 align:start position:0% hash of that Merkle tree is the ID of this<00:03:59.350> file<00:04:00.350> or<00:04:00.620> this<00:04:00.770> content<00:04:01.460> in<00:04:01.610> swarm<00:04:01.940> and 00:04:02.860 --> 00:04:02.870 align:start position:0% this file or this content in swarm and 00:04:02.870 --> 00:04:04.720 align:start position:0% this file or this content in swarm and the<00:04:03.170> chunks<00:04:03.500> they're<00:04:04.130> all<00:04:04.250> being<00:04:04.430> sent<00:04:04.640> to 00:04:04.720 --> 00:04:04.730 align:start position:0% the chunks they're all being sent to 00:04:04.730 --> 00:04:07.420 align:start position:0% the chunks they're all being sent to different<00:04:05.120> swarm<00:04:05.360> nodes<00:04:05.600> for<00:04:05.870> storage<00:04:06.430> what's 00:04:07.420 --> 00:04:07.430 align:start position:0% different swarm nodes for storage what's 00:04:07.430 --> 00:04:09.610 align:start position:0% different swarm nodes for storage what's really<00:04:07.670> happening<00:04:08.090> is<00:04:08.300> that<00:04:08.450> the<00:04:08.840> hash<00:04:09.140> is<00:04:09.470> the 00:04:09.610 --> 00:04:09.620 align:start position:0% really happening is that the hash is the 00:04:09.620 --> 00:04:12.310 align:start position:0% really happening is that the hash is the ID<00:04:09.800> of<00:04:09.920> the<00:04:10.130> chunk<00:04:10.490> and<00:04:10.840> every<00:04:11.840> chunk<00:04:12.050> gets 00:04:12.310 --> 00:04:12.320 align:start position:0% ID of the chunk and every chunk gets 00:04:12.320 --> 00:04:15.070 align:start position:0% ID of the chunk and every chunk gets stored<00:04:12.650> with<00:04:13.010> whatever<00:04:13.370> node<00:04:13.970> has<00:04:14.270> an<00:04:14.540> address 00:04:15.070 --> 00:04:15.080 align:start position:0% stored with whatever node has an address 00:04:15.080 --> 00:04:18.280 align:start position:0% stored with whatever node has an address which<00:04:15.260> is<00:04:15.410> closest<00:04:16.040> to<00:04:16.370> that<00:04:17.090> chunk<00:04:17.390> hash<00:04:17.600> so 00:04:18.280 --> 00:04:18.290 align:start position:0% which is closest to that chunk hash so 00:04:18.290 --> 00:04:23.170 align:start position:0% which is closest to that chunk hash so really<00:04:18.799> spread<00:04:19.640> out<00:04:19.790> the<00:04:19.940> data<00:04:20.090> and<00:04:22.030> your<00:04:23.030> DAP 00:04:23.170 --> 00:04:23.180 align:start position:0% really spread out the data and your DAP 00:04:23.180 --> 00:04:24.909 align:start position:0% really spread out the data and your DAP data<00:04:23.360> is<00:04:23.510> uniformly<00:04:24.050> stored<00:04:24.410> throughout<00:04:24.590> the 00:04:24.909 --> 00:04:24.919 align:start position:0% data is uniformly stored throughout the 00:04:24.919 --> 00:04:28.990 align:start position:0% data is uniformly stored throughout the swarm<00:04:25.220> network 00:04:28.990 --> 00:04:29.000 align:start position:0% 00:04:29.000 --> 00:04:34.909 align:start position:0% the<00:04:30.000> nodes<00:04:30.620> share<00:04:33.439> services<00:04:34.439> with<00:04:34.620> each<00:04:34.740> other 00:04:34.909 --> 00:04:34.919 align:start position:0% the nodes share services with each other 00:04:34.919 --> 00:04:39.730 align:start position:0% the nodes share services with each other it<00:04:35.280> could<00:04:35.460> be<00:04:35.960> data<00:04:36.960> chunk<00:04:37.590> retrieval<00:04:38.460> and 00:04:39.730 --> 00:04:39.740 align:start position:0% it could be data chunk retrieval and 00:04:39.740 --> 00:04:42.679 align:start position:0% it could be data chunk retrieval and serving<00:04:40.740> data<00:04:40.860> or<00:04:41.430> other<00:04:41.580> services<00:04:42.150> but<00:04:42.389> so 00:04:42.679 --> 00:04:42.689 align:start position:0% serving data or other services but so 00:04:42.689 --> 00:04:44.629 align:start position:0% serving data or other services but so the<00:04:42.840> accounting<00:04:43.289> how<00:04:43.979> much<00:04:44.159> you<00:04:44.340> have<00:04:44.490> to<00:04:44.520> pay 00:04:44.629 --> 00:04:44.639 align:start position:0% the accounting how much you have to pay 00:04:44.639 --> 00:04:47.510 align:start position:0% the accounting how much you have to pay how<00:04:45.360> much<00:04:45.539> you<00:04:45.689> get<00:04:45.840> paid<00:04:45.870> is<00:04:46.379> done<00:04:46.740> by<00:04:46.919> this<00:04:47.099> so 00:04:47.510 --> 00:04:47.520 align:start position:0% how much you get paid is done by this so 00:04:47.520 --> 00:04:50.540 align:start position:0% how much you get paid is done by this so called<00:04:47.669> swap<00:04:48.919> so<00:04:49.919> here's<00:04:50.129> how<00:04:50.250> that<00:04:50.310> might 00:04:50.540 --> 00:04:50.550 align:start position:0% called swap so here's how that might 00:04:50.550 --> 00:04:50.959 align:start position:0% called swap so here's how that might work 00:04:50.959 --> 00:04:50.969 align:start position:0% work 00:04:50.969 --> 00:04:53.420 align:start position:0% work suppose<00:04:51.419> node<00:04:51.780> 2<00:04:52.050> is<00:04:52.080> asking<00:04:52.770> for<00:04:52.979> a<00:04:53.009> DAP<00:04:53.219> and 00:04:53.420 --> 00:04:53.430 align:start position:0% suppose node 2 is asking for a DAP and 00:04:53.430 --> 00:04:55.159 align:start position:0% suppose node 2 is asking for a DAP and node<00:04:53.729> 1<00:04:53.939> happens<00:04:54.330> to<00:04:54.449> have<00:04:54.569> the<00:04:54.750> chunks<00:04:55.080> in 00:04:55.159 --> 00:04:55.169 align:start position:0% node 1 happens to have the chunks in 00:04:55.169 --> 00:04:58.939 align:start position:0% node 1 happens to have the chunks in question<00:04:55.560> and<00:04:55.740> gets<00:04:55.889> to<00:04:56.039> serve<00:04:56.250> them<00:04:56.460> so<00:04:57.949> you 00:04:58.939 --> 00:04:58.949 align:start position:0% question and gets to serve them so you 00:04:58.949 --> 00:05:01.159 align:start position:0% question and gets to serve them so you know<00:04:59.069> like<00:04:59.370> that<00:04:59.550> it's<00:05:00.330> my<00:05:00.479> own<00:05:00.599> animation<00:05:01.020> I'm 00:05:01.159 --> 00:05:01.169 align:start position:0% know like that it's my own animation I'm 00:05:01.169 --> 00:05:03.589 align:start position:0% know like that it's my own animation I'm proud<00:05:01.379> of<00:05:01.409> that<00:05:01.819> and<00:05:02.819> if<00:05:03.210> there's<00:05:03.389> more<00:05:03.449> than 00:05:03.589 --> 00:05:03.599 align:start position:0% proud of that and if there's more than 00:05:03.599 --> 00:05:06.170 align:start position:0% proud of that and if there's more than one<00:05:03.750> chunk<00:05:04.050> both<00:05:04.680> nodes<00:05:04.979> keep<00:05:05.370> count<00:05:05.610> so<00:05:06.060> there 00:05:06.170 --> 00:05:06.180 align:start position:0% one chunk both nodes keep count so there 00:05:06.180 --> 00:05:09.200 align:start position:0% one chunk both nodes keep count so there might<00:05:06.270> be<00:05:06.300> two<00:05:06.509> four<00:05:07.080> six<00:05:07.639> after<00:05:08.639> a<00:05:08.669> while<00:05:08.879> if 00:05:09.200 --> 00:05:09.210 align:start position:0% might be two four six after a while if 00:05:09.210 --> 00:05:11.990 align:start position:0% might be two four six after a while if node<00:05:09.509> one<00:05:09.719> is<00:05:09.870> not<00:05:10.020> consuming<00:05:10.530> any<00:05:10.620> data<00:05:11.000> node 00:05:11.990 --> 00:05:12.000 align:start position:0% node one is not consuming any data node 00:05:12.000 --> 00:05:13.760 align:start position:0% node one is not consuming any data node two<00:05:12.419> is<00:05:12.479> doing<00:05:12.780> all<00:05:12.900> the<00:05:13.020> consumption<00:05:13.500> no<00:05:13.710> two 00:05:13.760 --> 00:05:13.770 align:start position:0% two is doing all the consumption no two 00:05:13.770 --> 00:05:16.459 align:start position:0% two is doing all the consumption no two will<00:05:14.069> have<00:05:14.159> to<00:05:14.340> pay<00:05:14.550> node<00:05:14.819> one<00:05:15.060> so<00:05:15.569> it<00:05:16.259> would 00:05:16.459 --> 00:05:16.469 align:start position:0% will have to pay node one so it would 00:05:16.469 --> 00:05:20.269 align:start position:0% will have to pay node one so it would use<00:05:16.650> our<00:05:17.599> checkbook<00:05:18.599> payment<00:05:19.259> contract<00:05:19.949> to 00:05:20.269 --> 00:05:20.279 align:start position:0% use our checkbook payment contract to 00:05:20.279 --> 00:05:22.430 align:start position:0% use our checkbook payment contract to send<00:05:20.490> a<00:05:20.580> check<00:05:20.759> to<00:05:21.029> node<00:05:21.180> one<00:05:21.389> at<00:05:21.930> that<00:05:22.110> point 00:05:22.430 --> 00:05:22.440 align:start position:0% send a check to node one at that point 00:05:22.440 --> 00:05:26.029 align:start position:0% send a check to node one at that point the<00:05:23.310> channel<00:05:24.270> we<00:05:24.479> call<00:05:24.659> it<00:05:24.779> balanced<00:05:25.289> you<00:05:25.979> know 00:05:26.029 --> 00:05:26.039 align:start position:0% the channel we call it balanced you know 00:05:26.039 --> 00:05:27.800 align:start position:0% the channel we call it balanced you know whether<00:05:26.370> it's<00:05:26.610> chunk<00:05:26.939> four<00:05:27.150> chunk<00:05:27.389> or<00:05:27.569> check 00:05:27.800 --> 00:05:27.810 align:start position:0% whether it's chunk four chunk or check 00:05:27.810 --> 00:05:30.860 align:start position:0% whether it's chunk four chunk or check for<00:05:28.080> chunk<00:05:28.319> doesn't<00:05:29.009> matter<00:05:29.129> and<00:05:29.750> when<00:05:30.750> it's 00:05:30.860 --> 00:05:30.870 align:start position:0% for chunk doesn't matter and when it's 00:05:30.870 --> 00:05:32.540 align:start position:0% for chunk doesn't matter and when it's balanced<00:05:31.259> we<00:05:31.379> can<00:05:31.560> go<00:05:31.680> back<00:05:31.860> and<00:05:32.099> continue 00:05:32.540 --> 00:05:32.550 align:start position:0% balanced we can go back and continue 00:05:32.550 --> 00:05:35.809 align:start position:0% balanced we can go back and continue consuming<00:05:33.180> services<00:05:34.279> so<00:05:35.279> what's<00:05:35.430> happening 00:05:35.809 --> 00:05:35.819 align:start position:0% consuming services so what's happening 00:05:35.819 --> 00:05:38.869 align:start position:0% consuming services so what's happening is<00:05:36.029> in<00:05:36.419> within<00:05:36.750> this<00:05:36.870> form<00:05:37.139> a<00:05:37.379> swap<00:05:37.770> channel<00:05:38.159> in 00:05:38.869 --> 00:05:38.879 align:start position:0% is in within this form a swap channel in 00:05:38.879 --> 00:05:40.459 align:start position:0% is in within this form a swap channel in the<00:05:39.000> middle<00:05:39.270> where<00:05:39.479> zero<00:05:39.750> balance<00:05:40.139> neither 00:05:40.459 --> 00:05:40.469 align:start position:0% the middle where zero balance neither 00:05:40.469 --> 00:05:43.519 align:start position:0% the middle where zero balance neither node<00:05:40.770> owes<00:05:41.069> any<00:05:41.460> node<00:05:42.060> anything<00:05:42.719> and<00:05:42.930> as<00:05:43.259> soon 00:05:43.519 --> 00:05:43.529 align:start position:0% node owes any node anything and as soon 00:05:43.529 --> 00:05:46.369 align:start position:0% node owes any node anything and as soon as<00:05:43.680> services<00:05:44.250> get<00:05:44.520> consumed<00:05:45.080> the<00:05:46.080> balance 00:05:46.369 --> 00:05:46.379 align:start position:0% as services get consumed the balance 00:05:46.379 --> 00:05:49.100 align:start position:0% as services get consumed the balance moves<00:05:46.710> off<00:05:46.949> towards<00:05:47.400> one<00:05:47.580> side<00:05:47.849> at<00:05:48.659> some<00:05:48.900> point 00:05:49.100 --> 00:05:49.110 align:start position:0% moves off towards one side at some point 00:05:49.110 --> 00:05:50.360 align:start position:0% moves off towards one side at some point you're<00:05:49.379> gonna<00:05:49.469> hit<00:05:49.620> the<00:05:49.680> payment<00:05:50.159> threshold 00:05:50.360 --> 00:05:50.370 align:start position:0% you're gonna hit the payment threshold 00:05:50.370 --> 00:05:53.269 align:start position:0% you're gonna hit the payment threshold and<00:05:50.879> at<00:05:51.360> that<00:05:51.539> point<00:05:51.810> the<00:05:52.680> node<00:05:52.889> that's<00:05:53.069> in 00:05:53.269 --> 00:05:53.279 align:start position:0% and at that point the node that's in 00:05:53.279 --> 00:05:54.890 align:start position:0% and at that point the node that's in debt<00:05:53.460> would<00:05:53.759> have<00:05:53.940> to<00:05:54.060> issue<00:05:54.180> another<00:05:54.509> check 00:05:54.890 --> 00:05:54.900 align:start position:0% debt would have to issue another check 00:05:54.900 --> 00:05:58.309 align:start position:0% debt would have to issue another check to<00:05:55.500> the<00:05:55.620> node<00:05:56.330> to<00:05:57.330> the<00:05:57.419> debtor<00:05:57.569> so<00:05:57.930> that<00:05:58.110> to 00:05:58.309 --> 00:05:58.319 align:start position:0% to the node to the debtor so that to 00:05:58.319 --> 00:06:00.890 align:start position:0% to the node to the debtor so that to bring<00:05:58.560> the<00:05:58.770> balance<00:05:59.250> back<00:05:59.460> at<00:05:59.759> zero<00:05:59.969> so<00:06:00.449> you 00:06:00.890 --> 00:06:00.900 align:start position:0% bring the balance back at zero so you 00:06:00.900 --> 00:06:02.809 align:start position:0% bring the balance back at zero so you know<00:06:01.020> what's<00:06:01.139> always<00:06:01.349> working<00:06:01.680> to<00:06:01.800> keep<00:06:01.979> the 00:06:02.809 --> 00:06:02.819 align:start position:0% know what's always working to keep the 00:06:02.819 --> 00:06:05.420 align:start position:0% know what's always working to keep the swap<00:06:03.089> within<00:06:03.449> that<00:06:03.629> middle<00:06:03.960> range<00:06:03.990> and<00:06:04.500> if<00:06:05.310> you 00:06:05.420 --> 00:06:05.430 align:start position:0% swap within that middle range and if you 00:06:05.430 --> 00:06:09.350 align:start position:0% swap within that middle range and if you slide<00:06:06.060> too<00:06:06.300> far<00:06:06.569> off<00:06:06.719> to<00:06:06.870> the<00:06:06.960> side<00:06:07.199> well<00:06:08.360> then 00:06:09.350 --> 00:06:09.360 align:start position:0% slide too far off to the side well then 00:06:09.360 --> 00:06:11.059 align:start position:0% slide too far off to the side well then you<00:06:09.900> get<00:06:10.050> disconnected<00:06:10.349> that's<00:06:10.889> the 00:06:11.059 --> 00:06:11.069 align:start position:0% you get disconnected that's the 00:06:11.069 --> 00:06:13.490 align:start position:0% you get disconnected that's the punishment<00:06:11.669> the<00:06:12.539> ultimate<00:06:12.870> punishment<00:06:13.050> in<00:06:13.440> a 00:06:13.490 --> 00:06:13.500 align:start position:0% punishment the ultimate punishment in a 00:06:13.500 --> 00:06:14.869 align:start position:0% punishment the ultimate punishment in a peer-to-peer<00:06:13.710> network<00:06:13.770> nobody<00:06:14.610> wants<00:06:14.789> to 00:06:14.869 --> 00:06:14.879 align:start position:0% peer-to-peer network nobody wants to 00:06:14.879 --> 00:06:18.920 align:start position:0% peer-to-peer network nobody wants to talk<00:06:15.120> to<00:06:15.300> you<00:06:15.389> anymore<00:06:17.240> this<00:06:18.240> in<00:06:18.509> payment 00:06:18.920 --> 00:06:18.930 align:start position:0% talk to you anymore this in payment 00:06:18.930 --> 00:06:22.149 align:start position:0% talk to you anymore this in payment infrastructure<00:06:19.680> that<00:06:20.219> swap<00:06:21.210> is<00:06:21.360> a<00:06:21.389> part<00:06:21.659> of<00:06:21.779> is 00:06:22.149 --> 00:06:22.159 align:start position:0% infrastructure that swap is a part of is 00:06:22.159 --> 00:06:24.709 align:start position:0% infrastructure that swap is a part of is very<00:06:23.159> modular<00:06:23.520> it<00:06:23.940> can<00:06:24.150> go<00:06:24.270> in<00:06:24.389> many<00:06:24.539> different 00:06:24.709 --> 00:06:24.719 align:start position:0% very modular it can go in many different 00:06:24.719 --> 00:06:26.450 align:start position:0% very modular it can go in many different directions<00:06:24.930> it<00:06:25.529> was<00:06:25.680> originally<00:06:26.250> designed 00:06:26.450 --> 00:06:26.460 align:start position:0% directions it was originally designed 00:06:26.460 --> 00:06:29.689 align:start position:0% directions it was originally designed for<00:06:27.349> data<00:06:28.349> delivery<00:06:28.860> content<00:06:29.250> delivery<00:06:29.669> and 00:06:29.689 --> 00:06:29.699 align:start position:0% for data delivery content delivery and 00:06:29.699 --> 00:06:32.719 align:start position:0% for data delivery content delivery and storage<00:06:30.409> long-term<00:06:31.409> storage<00:06:31.710> as<00:06:31.949> described 00:06:32.719 --> 00:06:32.729 align:start position:0% storage long-term storage as described 00:06:32.729 --> 00:06:37.219 align:start position:0% storage long-term storage as described in<00:06:32.940> our<00:06:33.469> orange<00:06:34.469> paper<00:06:34.909> but<00:06:35.909> it's<00:06:36.180> it's<00:06:36.870> become 00:06:37.219 --> 00:06:37.229 align:start position:0% in our orange paper but it's it's become 00:06:37.229 --> 00:06:39.350 align:start position:0% in our orange paper but it's it's become much<00:06:37.500> more<00:06:37.740> modular 00:06:39.350 --> 00:06:39.360 align:start position:0% much more modular 00:06:39.360 --> 00:06:41.959 align:start position:0% much more modular and<00:06:40.009> we're<00:06:41.009> gonna<00:06:41.129> extend<00:06:41.430> it<00:06:41.639> and<00:06:41.759> we're 00:06:41.959 --> 00:06:41.969 align:start position:0% and we're gonna extend it and we're 00:06:41.969 --> 00:06:44.600 align:start position:0% and we're gonna extend it and we're talking<00:06:42.270> about<00:06:42.419> this<00:06:42.599> on<00:06:42.840> Saturday<00:06:43.430> in<00:06:44.430> the 00:06:44.600 --> 00:06:44.610 align:start position:0% talking about this on Saturday in the 00:06:44.610 --> 00:06:46.550 align:start position:0% talking about this on Saturday in the talk<00:06:44.909> called<00:06:45.180> swaps<00:06:45.479> we're<00:06:45.780> in<00:06:45.900> swindle<00:06:46.319> games 00:06:46.550 --> 00:06:46.560 align:start position:0% talk called swaps we're in swindle games 00:06:46.560 --> 00:06:51.050 align:start position:0% talk called swaps we're in swindle games where<00:06:46.979> we<00:06:47.099> describe<00:06:47.550> just<00:06:47.939> how<00:06:49.639> how<00:06:50.639> this<00:06:50.849> can 00:06:51.050 --> 00:06:51.060 align:start position:0% where we describe just how how this can 00:06:51.060 --> 00:06:54.260 align:start position:0% where we describe just how how this can learn<00:06:51.830> well<00:06:52.830> how<00:06:53.039> I<00:06:53.069> can<00:06:53.340> accommodate<00:06:54.120> all 00:06:54.260 --> 00:06:54.270 align:start position:0% learn well how I can accommodate all 00:06:54.270 --> 00:06:56.119 align:start position:0% learn well how I can accommodate all kinds<00:06:54.750> of<00:06:54.810> different<00:06:54.990> services<00:06:55.560> beyond<00:06:55.919> just 00:06:56.119 --> 00:06:56.129 align:start position:0% kinds of different services beyond just 00:06:56.129 --> 00:06:58.659 align:start position:0% kinds of different services beyond just storage 00:06:58.659 --> 00:06:58.669 align:start position:0% storage 00:06:58.669 --> 00:07:03.170 align:start position:0% storage the<00:06:59.669> status<00:07:01.069> well<00:07:02.069> some<00:07:02.759> of<00:07:02.849> you<00:07:02.939> may<00:07:03.060> have 00:07:03.170 --> 00:07:03.180 align:start position:0% the status well some of you may have 00:07:03.180 --> 00:07:05.240 align:start position:0% the status well some of you may have tried<00:07:03.419> swarm<00:07:03.840> already<00:07:04.169> if<00:07:04.500> you<00:07:04.560> have<00:07:04.919> tried 00:07:05.240 --> 00:07:05.250 align:start position:0% tried swarm already if you have tried 00:07:05.250 --> 00:07:06.950 align:start position:0% tried swarm already if you have tried swarm<00:07:05.669> you've<00:07:06.210> been<00:07:06.360> playing<00:07:06.599> around<00:07:06.689> with 00:07:06.950 --> 00:07:06.960 align:start position:0% swarm you've been playing around with 00:07:06.960 --> 00:07:11.360 align:start position:0% swarm you've been playing around with our<00:07:07.349> release<00:07:07.650> POC<00:07:08.449> 0.2<00:07:09.449> and<00:07:09.860> that<00:07:10.860> really<00:07:11.189> is<00:07:11.340> a 00:07:11.360 --> 00:07:11.370 align:start position:0% our release POC 0.2 and that really is a 00:07:11.370 --> 00:07:13.640 align:start position:0% our release POC 0.2 and that really is a proof-of-concept<00:07:11.939> release<00:07:12.719> it's<00:07:13.319> not<00:07:13.620> a 00:07:13.640 --> 00:07:13.650 align:start position:0% proof-of-concept release it's not a 00:07:13.650 --> 00:07:16.939 align:start position:0% proof-of-concept release it's not a final<00:07:14.009> release<00:07:15.229> so<00:07:16.229> the<00:07:16.409> the 00:07:16.939 --> 00:07:16.949 align:start position:0% final release so the the 00:07:16.949 --> 00:07:18.260 align:start position:0% final release so the the proof-of-concept<00:07:17.250> showed<00:07:17.819> us<00:07:18.000> that<00:07:18.150> the 00:07:18.260 --> 00:07:18.270 align:start position:0% proof-of-concept showed us that the 00:07:18.270 --> 00:07:20.719 align:start position:0% proof-of-concept showed us that the basic<00:07:18.629> idea<00:07:18.719> works<00:07:19.169> and<00:07:19.560> we've<00:07:20.159> had<00:07:20.340> some<00:07:20.550> fun 00:07:20.719 --> 00:07:20.729 align:start position:0% basic idea works and we've had some fun 00:07:20.729 --> 00:07:22.369 align:start position:0% basic idea works and we've had some fun in<00:07:20.909> a<00:07:20.969> hosting<00:07:21.389> content<00:07:21.629> and<00:07:21.960> trying<00:07:22.199> it<00:07:22.319> out 00:07:22.369 --> 00:07:22.379 align:start position:0% in a hosting content and trying it out 00:07:22.379 --> 00:07:24.589 align:start position:0% in a hosting content and trying it out and<00:07:22.560> playing<00:07:22.740> with<00:07:22.949> it<00:07:23.069> but<00:07:23.939> the<00:07:24.060> performance 00:07:24.589 --> 00:07:24.599 align:start position:0% and playing with it but the performance 00:07:24.599 --> 00:07:27.379 align:start position:0% and playing with it but the performance has<00:07:24.810> been<00:07:25.219> really<00:07:26.219> slow<00:07:26.460> we've<00:07:27.060> had<00:07:27.210> data 00:07:27.379 --> 00:07:27.389 align:start position:0% has been really slow we've had data 00:07:27.389 --> 00:07:28.909 align:start position:0% has been really slow we've had data availability<00:07:27.930> problems<00:07:28.529> throughout<00:07:28.770> the 00:07:28.909 --> 00:07:28.919 align:start position:0% availability problems throughout the 00:07:28.919 --> 00:07:30.619 align:start position:0% availability problems throughout the network<00:07:29.069> data<00:07:29.729> that<00:07:29.969> hasn't<00:07:30.180> reached<00:07:30.330> where 00:07:30.619 --> 00:07:30.629 align:start position:0% network data that hasn't reached where 00:07:30.629 --> 00:07:33.769 align:start position:0% network data that hasn't reached where it's<00:07:30.750> supposed<00:07:30.840> to<00:07:31.110> go<00:07:32.360> but<00:07:33.360> so<00:07:33.539> as<00:07:33.750> a 00:07:33.769 --> 00:07:33.779 align:start position:0% it's supposed to go but so as a 00:07:33.779 --> 00:07:37.070 align:start position:0% it's supposed to go but so as a proof-of-concept<00:07:34.110> it<00:07:34.620> was<00:07:34.740> successful<00:07:36.080> and 00:07:37.070 --> 00:07:37.080 align:start position:0% proof-of-concept it was successful and 00:07:37.080 --> 00:07:39.260 align:start position:0% proof-of-concept it was successful and the<00:07:37.169> testament<00:07:37.500> has<00:07:37.710> taught<00:07:37.949> us<00:07:37.979> a<00:07:38.129> lot<00:07:38.370> and<00:07:38.639> as 00:07:39.260 --> 00:07:39.270 align:start position:0% the testament has taught us a lot and as 00:07:39.270 --> 00:07:41.149 align:start position:0% the testament has taught us a lot and as a<00:07:39.300> result<00:07:39.659> several<00:07:39.870> of<00:07:40.110> the<00:07:40.229> core<00:07:40.469> components 00:07:41.149 --> 00:07:41.159 align:start position:0% a result several of the core components 00:07:41.159 --> 00:07:42.589 align:start position:0% a result several of the core components are<00:07:41.279> being<00:07:41.490> rewritten<00:07:41.909> or<00:07:42.210> have<00:07:42.389> been 00:07:42.589 --> 00:07:42.599 align:start position:0% are being rewritten or have been 00:07:42.599 --> 00:07:47.180 align:start position:0% are being rewritten or have been rewritten<00:07:43.370> completely<00:07:45.979> yes<00:07:46.979> and 00:07:47.180 --> 00:07:47.190 align:start position:0% rewritten completely yes and 00:07:47.190 --> 00:07:49.309 align:start position:0% rewritten completely yes and additionally<00:07:47.639> the<00:07:48.270> scope<00:07:48.659> of<00:07:48.930> the<00:07:49.110> project 00:07:49.309 --> 00:07:49.319 align:start position:0% additionally the scope of the project 00:07:49.319 --> 00:07:51.189 align:start position:0% additionally the scope of the project has<00:07:49.710> grown<00:07:49.919> as<00:07:50.279> I've<00:07:50.430> mentioned<00:07:50.550> before 00:07:51.189 --> 00:07:51.199 align:start position:0% has grown as I've mentioned before 00:07:51.199 --> 00:07:54.260 align:start position:0% has grown as I've mentioned before people<00:07:52.199> are<00:07:52.409> using<00:07:52.589> swarm<00:07:53.190> not<00:07:53.430> just<00:07:53.639> to<00:07:53.879> host 00:07:54.260 --> 00:07:54.270 align:start position:0% people are using swarm not just to host 00:07:54.270 --> 00:07:57.379 align:start position:0% people are using swarm not just to host content<00:07:54.810> but<00:07:55.490> for<00:07:56.490> example<00:07:56.550> the<00:07:56.909> live<00:07:57.089> peer 00:07:57.379 --> 00:07:57.389 align:start position:0% content but for example the live peer 00:07:57.389 --> 00:07:59.719 align:start position:0% content but for example the live peer group<00:07:57.599> are<00:07:57.810> using<00:07:58.440> it<00:07:58.529> for<00:07:58.830> broadcast 00:07:59.719 --> 00:07:59.729 align:start position:0% group are using it for broadcast 00:07:59.729 --> 00:08:01.969 align:start position:0% group are using it for broadcast streaming<00:08:00.360> video<00:08:00.629> and<00:08:00.719> audio<00:08:01.110> really<00:08:01.770> cool 00:08:01.969 --> 00:08:01.979 align:start position:0% streaming video and audio really cool 00:08:01.979 --> 00:08:04.249 align:start position:0% streaming video and audio really cool they're<00:08:02.279> also<00:08:02.400> talking<00:08:02.849> on<00:08:02.940> Saturday<00:08:03.360> another 00:08:04.249 --> 00:08:04.259 align:start position:0% they're also talking on Saturday another 00:08:04.259 --> 00:08:06.140 align:start position:0% they're also talking on Saturday another project<00:08:05.009> that's<00:08:05.370> developed<00:08:05.699> is<00:08:05.819> about 00:08:06.140 --> 00:08:06.150 align:start position:0% project that's developed is about 00:08:06.150 --> 00:08:07.850 align:start position:0% project that's developed is about communication<00:08:06.839> direct<00:08:07.440> node<00:08:07.650> to<00:08:07.830> node 00:08:07.850 --> 00:08:07.860 align:start position:0% communication direct node to node 00:08:07.860 --> 00:08:10.550 align:start position:0% communication direct node to node communication<00:08:08.610> and<00:08:08.930> to<00:08:09.930> say<00:08:10.080> tell<00:08:10.289> us<00:08:10.319> more 00:08:10.550 --> 00:08:10.560 align:start position:0% communication and to say tell us more 00:08:10.560 --> 00:08:13.519 align:start position:0% communication and to say tell us more about<00:08:10.710> that<00:08:10.770> I'd<00:08:11.189> like<00:08:11.339> to<00:08:11.370> introduce<00:08:11.580> Luis<00:08:12.529> to 00:08:13.519 --> 00:08:13.529 align:start position:0% about that I'd like to introduce Luis to 00:08:13.529 --> 00:08:19.570 align:start position:0% about that I'd like to introduce Luis to talk<00:08:13.680> about<00:08:13.770> PSS 00:08:19.570 --> 00:08:19.580 align:start position:0% 00:08:19.580 --> 00:08:24.790 align:start position:0% [Applause] 00:08:24.790 --> 00:08:24.800 align:start position:0% 00:08:24.800 --> 00:08:28.010 align:start position:0% hello<00:08:25.800> everyone<00:08:26.280> I'm<00:08:26.610> Lois<00:08:26.970> this<00:08:27.390> is<00:08:27.540> my<00:08:27.690> first 00:08:28.010 --> 00:08:28.020 align:start position:0% hello everyone I'm Lois this is my first 00:08:28.020 --> 00:08:29.410 align:start position:0% hello everyone I'm Lois this is my first Devcon 00:08:29.410 --> 00:08:29.420 align:start position:0% Devcon 00:08:29.420 --> 00:08:33.290 align:start position:0% Devcon actually<00:08:31.039> I'm<00:08:32.039> a<00:08:32.099> classical<00:08:32.610> pianist<00:08:32.789> turned 00:08:33.290 --> 00:08:33.300 align:start position:0% actually I'm a classical pianist turned 00:08:33.300 --> 00:08:36.409 align:start position:0% actually I'm a classical pianist turned cultural<00:08:33.960> magazine<00:08:34.800> editor<00:08:35.219> turned<00:08:35.490> funding 00:08:36.409 --> 00:08:36.419 align:start position:0% cultural magazine editor turned funding 00:08:36.419 --> 00:08:38.209 align:start position:0% cultural magazine editor turned funding bureaucrat<00:08:36.870> turned<00:08:37.260> band<00:08:37.620> manager<00:08:38.039> turned 00:08:38.209 --> 00:08:38.219 align:start position:0% bureaucrat turned band manager turned 00:08:38.219 --> 00:08:41.300 align:start position:0% bureaucrat turned band manager turned taxi<00:08:38.700> driver<00:08:39.380> and<00:08:40.380> I<00:08:40.500> was<00:08:40.740> privileged<00:08:41.219> enough 00:08:41.300 --> 00:08:41.310 align:start position:0% taxi driver and I was privileged enough 00:08:41.310 --> 00:08:43.159 align:start position:0% taxi driver and I was privileged enough to<00:08:41.760> get<00:08:42.090> a<00:08:42.120> ride<00:08:42.330> with<00:08:42.570> some<00:08:42.690> blockchain 00:08:43.159 --> 00:08:43.169 align:start position:0% to get a ride with some blockchain 00:08:43.169 --> 00:08:45.350 align:start position:0% to get a ride with some blockchain people<00:08:43.620> in<00:08:43.800> Berlin<00:08:44.099> where<00:08:44.370> I<00:08:44.400> worked<00:08:44.730> in<00:08:45.150> my 00:08:45.350 --> 00:08:45.360 align:start position:0% people in Berlin where I worked in my 00:08:45.360 --> 00:08:47.770 align:start position:0% people in Berlin where I worked in my taxi<00:08:45.840> and<00:08:46.380> then<00:08:47.010> told<00:08:47.220> me<00:08:47.370> all<00:08:47.490> about<00:08:47.640> that 00:08:47.770 --> 00:08:47.780 align:start position:0% taxi and then told me all about that 00:08:47.780 --> 00:08:50.750 align:start position:0% taxi and then told me all about that centralized<00:08:48.780> consensus<00:08:49.500> war<00:08:49.800> on<00:08:49.950> privacy<00:08:50.340> and 00:08:50.750 --> 00:08:50.760 align:start position:0% centralized consensus war on privacy and 00:08:50.760 --> 00:08:52.760 align:start position:0% centralized consensus war on privacy and the<00:08:50.910> looming<00:08:51.270> dangers<00:08:51.840> of<00:08:52.290> opaque 00:08:52.760 --> 00:08:52.770 align:start position:0% the looming dangers of opaque 00:08:52.770 --> 00:08:54.740 align:start position:0% the looming dangers of opaque algorithmically<00:08:53.580> driven<00:08:54.090> societal 00:08:54.740 --> 00:08:54.750 align:start position:0% algorithmically driven societal 00:08:54.750 --> 00:08:57.470 align:start position:0% algorithmically driven societal conformity<00:08:55.530> and<00:08:55.860> this<00:08:56.610> brought<00:08:56.880> me<00:08:57.060> back<00:08:57.210> to 00:08:57.470 --> 00:08:57.480 align:start position:0% conformity and this brought me back to 00:08:57.480 --> 00:08:59.570 align:start position:0% conformity and this brought me back to the<00:08:57.660> world<00:08:58.020> of<00:08:58.110> computers<00:08:58.590> that's<00:08:59.010> I've<00:08:59.340> been 00:08:59.570 --> 00:08:59.580 align:start position:0% the world of computers that's I've been 00:08:59.580 --> 00:09:02.420 align:start position:0% the world of computers that's I've been in<00:08:59.760> all<00:09:00.210> my<00:09:00.360> life<00:09:00.510> in<00:09:00.780> varying<00:09:01.080> degrees<00:09:01.400> now<00:09:02.400> I 00:09:02.420 --> 00:09:02.430 align:start position:0% in all my life in varying degrees now I 00:09:02.430 --> 00:09:06.680 align:start position:0% in all my life in varying degrees now I work<00:09:02.850> for<00:09:02.880> Jack<00:09:04.220> part<00:09:05.220> of<00:09:05.310> the<00:09:05.370> Jack<00:09:05.610> team<00:09:05.910> Jack 00:09:06.680 --> 00:09:06.690 align:start position:0% work for Jack part of the Jack team Jack 00:09:06.690 --> 00:09:09.950 align:start position:0% work for Jack part of the Jack team Jack is<00:09:07.020> a<00:09:07.080> company<00:09:07.620> first<00:09:08.400> of<00:09:08.610> all<00:09:08.730> I<00:09:08.960> very 00:09:09.950 --> 00:09:09.960 align:start position:0% is a company first of all I very 00:09:09.960 --> 00:09:11.900 align:start position:0% is a company first of all I very clumsily<00:09:10.440> forgot<00:09:10.920> to<00:09:11.100> include<00:09:11.370> the<00:09:11.490> logo<00:09:11.820> of 00:09:11.900 --> 00:09:11.910 align:start position:0% clumsily forgot to include the logo of 00:09:11.910 --> 00:09:20.600 align:start position:0% clumsily forgot to include the logo of Jack<00:09:12.120> here<00:09:12.480> but<00:09:18.320> that's<00:09:19.320> the<00:09:19.620> logo<00:09:19.800> they're<00:09:20.580> a 00:09:20.600 --> 00:09:20.610 align:start position:0% Jack here but that's the logo they're a 00:09:20.610 --> 00:09:23.750 align:start position:0% Jack here but that's the logo they're a sponsor<00:09:21.150> we<00:09:21.450> are<00:09:21.630> a<00:09:21.660> sponsor<00:09:21.900> so<00:09:22.740> Jack<00:09:23.400> built 00:09:23.750 --> 00:09:23.760 align:start position:0% sponsor we are a sponsor so Jack built 00:09:23.760 --> 00:09:26.030 align:start position:0% sponsor we are a sponsor so Jack built son<00:09:23.940> swarm<00:09:24.300> and<00:09:24.510> we<00:09:25.140> want<00:09:25.320> to<00:09:25.440> contribute<00:09:25.800> to 00:09:26.030 --> 00:09:26.040 align:start position:0% son swarm and we want to contribute to 00:09:26.040 --> 00:09:27.770 align:start position:0% son swarm and we want to contribute to swarm<00:09:26.339> as<00:09:26.430> much<00:09:26.610> as<00:09:26.760> possible<00:09:26.970> of<00:09:27.300> course<00:09:27.360> and 00:09:27.770 --> 00:09:27.780 align:start position:0% swarm as much as possible of course and 00:09:27.780 --> 00:09:30.110 align:start position:0% swarm as much as possible of course and therefore<00:09:28.470> I<00:09:28.530> was<00:09:28.680> very<00:09:28.860> excited<00:09:29.430> when<00:09:29.460> Viktor 00:09:30.110 --> 00:09:30.120 align:start position:0% therefore I was very excited when Viktor 00:09:30.120 --> 00:09:33.079 align:start position:0% therefore I was very excited when Viktor Tron<00:09:30.390> came<00:09:30.690> to<00:09:30.839> me<00:09:30.960> and<00:09:31.170> and<00:09:31.850> challenged<00:09:32.850> me<00:09:33.060> to 00:09:33.079 --> 00:09:33.089 align:start position:0% Tron came to me and and challenged me to 00:09:33.089 --> 00:09:35.990 align:start position:0% Tron came to me and and challenged me to do<00:09:33.930> the<00:09:34.080> PSS<00:09:34.530> work<00:09:34.770> and<00:09:35.040> that's<00:09:35.670> what<00:09:35.910> I've 00:09:35.990 --> 00:09:36.000 align:start position:0% do the PSS work and that's what I've 00:09:36.000 --> 00:09:37.070 align:start position:0% do the PSS work and that's what I've been<00:09:36.089> working<00:09:36.240> on<00:09:36.510> the<00:09:36.630> last<00:09:36.720> seven<00:09:37.050> months 00:09:37.070 --> 00:09:37.080 align:start position:0% been working on the last seven months 00:09:37.080 --> 00:09:40.760 align:start position:0% been working on the last seven months now<00:09:38.480> notice<00:09:39.480> that<00:09:39.510> among<00:09:40.230> the<00:09:40.380> things<00:09:40.440> I<00:09:40.710> said 00:09:40.760 --> 00:09:40.770 align:start position:0% now notice that among the things I said 00:09:40.770 --> 00:09:43.280 align:start position:0% now notice that among the things I said I<00:09:40.920> was<00:09:41.220> I<00:09:41.610> didn't<00:09:42.120> mention<00:09:42.240> public<00:09:42.690> speaker<00:09:43.110> so 00:09:43.280 --> 00:09:43.290 align:start position:0% I was I didn't mention public speaker so 00:09:43.290 --> 00:09:46.040 align:start position:0% I was I didn't mention public speaker so that's<00:09:43.470> why<00:09:43.560> I<00:09:43.620> have<00:09:43.800> this<00:09:44.270> not<00:09:45.270> to<00:09:45.420> panic<00:09:45.630> I 00:09:46.040 --> 00:09:46.050 align:start position:0% that's why I have this not to panic I 00:09:46.050 --> 00:09:48.200 align:start position:0% that's why I have this not to panic I will<00:09:46.890> be<00:09:46.980> looking<00:09:47.250> at<00:09:47.339> more<00:09:47.670> at<00:09:47.790> this<00:09:48.000> than 00:09:48.200 --> 00:09:48.210 align:start position:0% will be looking at more at this than 00:09:48.210 --> 00:09:50.500 align:start position:0% will be looking at more at this than it's<00:09:48.330> you<00:09:48.480> don't<00:09:48.810> take<00:09:49.020> it<00:09:49.110> personally<00:09:49.500> please 00:09:50.500 --> 00:09:50.510 align:start position:0% it's you don't take it personally please 00:09:50.510 --> 00:09:57.500 align:start position:0% it's you don't take it personally please now<00:09:52.520> swarm<00:09:53.520> is<00:09:53.730> a<00:09:54.060> network<00:09:54.510> of<00:09:54.720> nodes<00:09:55.400> and<00:09:56.510> not 00:09:57.500 --> 00:09:57.510 align:start position:0% now swarm is a network of nodes and not 00:09:57.510 --> 00:09:59.810 align:start position:0% now swarm is a network of nodes and not only<00:09:57.720> that<00:09:57.870> but<00:09:58.410> swarm<00:09:58.800> is<00:09:58.980> network<00:09:59.430> of<00:09:59.610> nodes 00:09:59.810 --> 00:09:59.820 align:start position:0% only that but swarm is network of nodes 00:09:59.820 --> 00:10:02.810 align:start position:0% only that but swarm is network of nodes that<00:10:00.480> speak<00:10:00.750> the<00:10:00.900> same<00:10:01.050> language<00:10:01.820> this 00:10:02.810 --> 00:10:02.820 align:start position:0% that speak the same language this 00:10:02.820 --> 00:10:05.390 align:start position:0% that speak the same language this language<00:10:03.180> is<00:10:03.800> communicated<00:10:04.800> on<00:10:04.980> top<00:10:05.250> of 00:10:05.390 --> 00:10:05.400 align:start position:0% language is communicated on top of 00:10:05.400 --> 00:10:07.400 align:start position:0% language is communicated on top of Internet<00:10:05.790> protocols<00:10:06.270> and<00:10:06.540> is<00:10:06.660> regulated<00:10:07.230> by<00:10:07.260> a 00:10:07.400 --> 00:10:07.410 align:start position:0% Internet protocols and is regulated by a 00:10:07.410 --> 00:10:10.160 align:start position:0% Internet protocols and is regulated by a protocol<00:10:07.890> framework<00:10:08.510> and<00:10:09.510> go<00:10:09.690> a<00:10:09.720> theorem<00:10:10.020> this 00:10:10.160 --> 00:10:10.170 align:start position:0% protocol framework and go a theorem this 00:10:10.170 --> 00:10:15.230 align:start position:0% protocol framework and go a theorem this is<00:10:10.290> called<00:10:10.500> dev<00:10:10.740> p2p<00:10:13.190> swarm<00:10:14.190> nodes<00:10:14.430> uses<00:10:15.030> this 00:10:15.230 --> 00:10:15.240 align:start position:0% is called dev p2p swarm nodes uses this 00:10:15.240 --> 00:10:17.270 align:start position:0% is called dev p2p swarm nodes uses this language<00:10:15.510> to<00:10:16.020> find<00:10:16.260> their<00:10:16.440> most<00:10:16.650> advantageous 00:10:17.270 --> 00:10:17.280 align:start position:0% language to find their most advantageous 00:10:17.280 --> 00:10:20.270 align:start position:0% language to find their most advantageous place<00:10:18.210> in<00:10:18.480> the<00:10:18.570> network<00:10:18.960> and<00:10:19.260> to<00:10:19.980> figure<00:10:20.160> out 00:10:20.270 --> 00:10:20.280 align:start position:0% place in the network and to figure out 00:10:20.280 --> 00:10:23.540 align:start position:0% place in the network and to figure out who<00:10:20.550> to<00:10:20.730> share<00:10:20.970> content<00:10:21.390> with<00:10:22.010> but<00:10:23.010> content 00:10:23.540 --> 00:10:23.550 align:start position:0% who to share content with but content 00:10:23.550 --> 00:10:25.220 align:start position:0% who to share content with but content doesn't<00:10:23.940> necessarily<00:10:24.570> just<00:10:24.780> have<00:10:24.960> to<00:10:25.110> mean 00:10:25.220 --> 00:10:25.230 align:start position:0% doesn't necessarily just have to mean 00:10:25.230 --> 00:10:29.000 align:start position:0% doesn't necessarily just have to mean files<00:10:25.560> a<00:10:26.330> message<00:10:27.330> for<00:10:27.510> example<00:10:27.570> is<00:10:28.140> just<00:10:28.830> as 00:10:29.000 --> 00:10:29.010 align:start position:0% files a message for example is just as 00:10:29.010 --> 00:10:32.810 align:start position:0% files a message for example is just as much<00:10:29.220> worthy<00:10:29.670> of<00:10:29.730> the<00:10:29.820> term<00:10:31.250> thus<00:10:32.250> comes<00:10:32.640> the 00:10:32.810 --> 00:10:32.820 align:start position:0% much worthy of the term thus comes the 00:10:32.820 --> 00:10:35.460 align:start position:0% much worthy of the term thus comes the idea<00:10:33.089> if<00:10:33.930> we<00:10:34.140> can<00:10:34.260> use<00:10:34.350> swarm<00:10:34.680> to<00:10:34.860> send<00:10:35.070> bits 00:10:35.460 --> 00:10:35.470 align:start position:0% idea if we can use swarm to send bits 00:10:35.470 --> 00:10:38.370 align:start position:0% idea if we can use swarm to send bits pieces<00:10:35.890> of<00:10:35.920> file<00:10:36.400> surround<00:10:36.990> why<00:10:37.990> can't<00:10:38.290> we<00:10:38.350> use 00:10:38.370 --> 00:10:38.380 align:start position:0% pieces of file surround why can't we use 00:10:38.380 --> 00:10:41.940 align:start position:0% pieces of file surround why can't we use it<00:10:38.530> to<00:10:39.280> send<00:10:39.490> messages<00:10:39.910> as<00:10:40.120> well<00:10:40.650> now<00:10:41.650> wait<00:10:41.860> a 00:10:41.940 --> 00:10:41.950 align:start position:0% it to send messages as well now wait a 00:10:41.950 --> 00:10:44.280 align:start position:0% it to send messages as well now wait a minute<00:10:42.010> you<00:10:42.250> might<00:10:42.430> say<00:10:42.730> there<00:10:43.540> is<00:10:43.720> already<00:10:44.020> a 00:10:44.280 --> 00:10:44.290 align:start position:0% minute you might say there is already a 00:10:44.290 --> 00:10:45.870 align:start position:0% minute you might say there is already a messaging<00:10:44.740> platform<00:10:45.220> in<00:10:45.310> aetherium<00:10:45.730> and 00:10:45.870 --> 00:10:45.880 align:start position:0% messaging platform in aetherium and 00:10:45.880 --> 00:10:48.800 align:start position:0% messaging platform in aetherium and that's<00:10:46.150> called<00:10:46.420> whisper<00:10:46.840> and<00:10:47.080> this<00:10:48.070> is<00:10:48.220> true 00:10:48.800 --> 00:10:48.810 align:start position:0% that's called whisper and this is true 00:10:48.810 --> 00:10:51.330 align:start position:0% that's called whisper and this is true but<00:10:49.810> the<00:10:49.960> mission<00:10:50.170> of<00:10:50.410> whisper<00:10:50.740> is<00:10:50.830> somewhat 00:10:51.330 --> 00:10:51.340 align:start position:0% but the mission of whisper is somewhat 00:10:51.340 --> 00:10:55.230 align:start position:0% but the mission of whisper is somewhat different<00:10:51.910> from<00:10:52.330> PSS<00:10:52.930> its<00:10:53.770> focus<00:10:54.310> is<00:10:54.520> to<00:10:54.940> serve 00:10:55.230 --> 00:10:55.240 align:start position:0% different from PSS its focus is to serve 00:10:55.240 --> 00:10:57.600 align:start position:0% different from PSS its focus is to serve the<00:10:55.630> need<00:10:55.840> of<00:10:55.870> total<00:10:56.440> anonymity<00:10:56.710> and<00:10:57.460> to 00:10:57.600 --> 00:10:57.610 align:start position:0% the need of total anonymity and to 00:10:57.610 --> 00:11:00.510 align:start position:0% the need of total anonymity and to secure<00:10:58.000> freedom<00:10:58.390> of<00:10:58.480> expression<00:10:59.200> at<00:10:59.410> cost<00:11:00.220> of 00:11:00.510 --> 00:11:00.520 align:start position:0% secure freedom of expression at cost of 00:11:00.520 --> 00:11:01.500 align:start position:0% secure freedom of expression at cost of performance 00:11:01.500 --> 00:11:01.510 align:start position:0% performance 00:11:01.510 --> 00:11:04.830 align:start position:0% performance now<00:11:02.350> since<00:11:02.680> the<00:11:02.830> swarm<00:11:03.160> network<00:11:03.550> is<00:11:03.730> routed<00:11:04.180> it 00:11:04.830 --> 00:11:04.840 align:start position:0% now since the swarm network is routed it 00:11:04.840 --> 00:11:07.860 align:start position:0% now since the swarm network is routed it knows<00:11:05.140> that<00:11:05.170> the<00:11:05.500> shortest<00:11:05.890> way<00:11:06.420> to<00:11:07.420> the<00:11:07.540> final 00:11:07.860 --> 00:11:07.870 align:start position:0% knows that the shortest way to the final 00:11:07.870 --> 00:11:10.320 align:start position:0% knows that the shortest way to the final destination<00:11:08.500> is<00:11:08.680> and<00:11:08.890> therefore<00:11:09.310> PSS<00:11:10.090> can 00:11:10.320 --> 00:11:10.330 align:start position:0% destination is and therefore PSS can 00:11:10.330 --> 00:11:12.600 align:start position:0% destination is and therefore PSS can deliver<00:11:10.600> messages<00:11:11.170> fast<00:11:11.530> and<00:11:11.950> with<00:11:12.250> a<00:11:12.280> minimum 00:11:12.600 --> 00:11:12.610 align:start position:0% deliver messages fast and with a minimum 00:11:12.610 --> 00:11:15.720 align:start position:0% deliver messages fast and with a minimum of<00:11:12.820> network<00:11:13.240> load<00:11:13.860> simply<00:11:14.860> it<00:11:15.070> serves<00:11:15.430> a 00:11:15.720 --> 00:11:15.730 align:start position:0% of network load simply it serves a 00:11:15.730 --> 00:11:19.500 align:start position:0% of network load simply it serves a different<00:11:15.970> purpose<00:11:17.460> so<00:11:18.460> this<00:11:18.610> is<00:11:18.790> what<00:11:18.970> PSS<00:11:19.480> is 00:11:19.500 --> 00:11:19.510 align:start position:0% different purpose so this is what PSS is 00:11:19.510 --> 00:11:23.280 align:start position:0% different purpose so this is what PSS is it's<00:11:20.410> a<00:11:20.590> postal<00:11:21.160> service<00:11:21.610> over<00:11:21.970> swarm<00:11:22.290> now 00:11:23.280 --> 00:11:23.290 align:start position:0% it's a postal service over swarm now 00:11:23.290 --> 00:11:25.680 align:start position:0% it's a postal service over swarm now this<00:11:23.500> sense<00:11:23.740> sounds<00:11:24.370> easy<00:11:24.550> right<00:11:24.730> if<00:11:25.090> you<00:11:25.510> want 00:11:25.680 --> 00:11:25.690 align:start position:0% this sense sounds easy right if you want 00:11:25.690 --> 00:11:27.990 align:start position:0% this sense sounds easy right if you want to<00:11:25.780> send<00:11:25.990> a<00:11:26.050> message<00:11:26.170> to<00:11:26.380> someone<00:11:26.980> you<00:11:27.970> just 00:11:27.990 --> 00:11:28.000 align:start position:0% to send a message to someone you just 00:11:28.000 --> 00:11:29.930 align:start position:0% to send a message to someone you just slap<00:11:28.360> an<00:11:28.540> address<00:11:28.840> on<00:11:28.990> it<00:11:29.230> and<00:11:29.380> away<00:11:29.770> it<00:11:29.860> goes 00:11:29.930 --> 00:11:29.940 align:start position:0% slap an address on it and away it goes 00:11:29.940 --> 00:11:32.990 align:start position:0% slap an address on it and away it goes well<00:11:30.940> it's<00:11:31.120> not<00:11:31.210> quite<00:11:31.390> that<00:11:31.690> easy 00:11:32.990 --> 00:11:33.000 align:start position:0% well it's not quite that easy 00:11:33.000 --> 00:11:35.460 align:start position:0% well it's not quite that easy since<00:11:34.000> messages<00:11:34.510> potentially<00:11:35.080> pass<00:11:35.290> through 00:11:35.460 --> 00:11:35.470 align:start position:0% since messages potentially pass through 00:11:35.470 --> 00:11:36.780 align:start position:0% since messages potentially pass through unknown<00:11:35.830> nodes<00:11:36.100> to<00:11:36.310> get<00:11:36.460> where<00:11:36.640> they're 00:11:36.780 --> 00:11:36.790 align:start position:0% unknown nodes to get where they're 00:11:36.790 --> 00:11:37.740 align:start position:0% unknown nodes to get where they're supposed<00:11:37.150> to<00:11:37.330> be 00:11:37.740 --> 00:11:37.750 align:start position:0% supposed to be 00:11:37.750 --> 00:11:40.230 align:start position:0% supposed to be they<00:11:38.530> should<00:11:38.770> be<00:11:38.890> encrypted<00:11:39.430> so<00:11:39.760> that<00:11:39.790> people 00:11:40.230 --> 00:11:40.240 align:start position:0% they should be encrypted so that people 00:11:40.240 --> 00:11:43.350 align:start position:0% they should be encrypted so that people can't<00:11:40.420> snoop<00:11:40.690> on<00:11:40.840> the<00:11:40.930> contents<00:11:41.940> that<00:11:42.940> means 00:11:43.350 --> 00:11:43.360 align:start position:0% can't snoop on the contents that means 00:11:43.360 --> 00:11:45.330 align:start position:0% can't snoop on the contents that means that<00:11:43.630> the<00:11:43.750> actual<00:11:44.290> definition<00:11:44.980> of<00:11:45.160> a 00:11:45.330 --> 00:11:45.340 align:start position:0% that the actual definition of a 00:11:45.340 --> 00:11:47.850 align:start position:0% that the actual definition of a recipient<00:11:45.820> in<00:11:46.090> PSS<00:11:46.600> is<00:11:46.630> not<00:11:46.990> only<00:11:47.560> the<00:11:47.680> actual 00:11:47.850 --> 00:11:47.860 align:start position:0% recipient in PSS is not only the actual 00:11:47.860 --> 00:11:51.060 align:start position:0% recipient in PSS is not only the actual address<00:11:48.280> of<00:11:48.580> the<00:11:48.730> node<00:11:48.910> but<00:11:49.630> who<00:11:49.960> can<00:11:50.350> actually 00:11:51.060 --> 00:11:51.070 align:start position:0% address of the node but who can actually 00:11:51.070 --> 00:11:55.410 align:start position:0% address of the node but who can actually decrypt<00:11:51.220> the<00:11:51.610> message<00:11:53.550> actually<00:11:54.550> the<00:11:55.240> node 00:11:55.410 --> 00:11:55.420 align:start position:0% decrypt the message actually the node 00:11:55.420 --> 00:11:58.980 align:start position:0% decrypt the message actually the node address<00:11:55.870> in<00:11:56.050> the<00:11:56.200> end<00:11:56.370> doesn't<00:11:57.990> unambiguously 00:11:58.980 --> 00:11:58.990 align:start position:0% address in the end doesn't unambiguously 00:11:58.990 --> 00:12:02.430 align:start position:0% address in the end doesn't unambiguously define<00:11:59.440> a<00:11:59.470> recipient<00:12:00.690> yes<00:12:01.690> to<00:12:02.050> route<00:12:02.260> the 00:12:02.430 --> 00:12:02.440 align:start position:0% define a recipient yes to route the 00:12:02.440 --> 00:12:04.680 align:start position:0% define a recipient yes to route the message<00:12:02.710> service<00:12:02.860> swarm<00:12:03.220> using<00:12:03.550> PSS<00:12:04.060> you<00:12:04.450> pass 00:12:04.680 --> 00:12:04.690 align:start position:0% message service swarm using PSS you pass 00:12:04.690 --> 00:12:07.560 align:start position:0% message service swarm using PSS you pass it<00:12:04.960> to<00:12:05.440> them<00:12:05.650> you<00:12:06.250> pass<00:12:06.430> it<00:12:06.580> the<00:12:06.670> message<00:12:06.850> you 00:12:07.560 --> 00:12:07.570 align:start position:0% it to them you pass it the message you 00:12:07.570 --> 00:12:10.580 align:start position:0% it to them you pass it the message you want<00:12:07.600> to<00:12:07.810> send<00:12:07.900> and<00:12:08.410> an<00:12:08.860> address<00:12:09.040> to<00:12:09.370> send<00:12:09.610> to 00:12:10.580 --> 00:12:10.590 align:start position:0% want to send and an address to send to 00:12:10.590 --> 00:12:12.750 align:start position:0% want to send and an address to send to but<00:12:11.590> let's<00:12:11.920> say<00:12:12.070> you<00:12:12.130> don't<00:12:12.370> want<00:12:12.490> to<00:12:12.580> tell 00:12:12.750 --> 00:12:12.760 align:start position:0% but let's say you don't want to tell 00:12:12.760 --> 00:12:14.550 align:start position:0% but let's say you don't want to tell everybody<00:12:13.030> on<00:12:13.270> the<00:12:13.420> network<00:12:13.450> who<00:12:14.380> you're 00:12:14.550 --> 00:12:14.560 align:start position:0% everybody on the network who you're 00:12:14.560 --> 00:12:17.100 align:start position:0% everybody on the network who you're actually<00:12:14.710> messaging<00:12:15.400> with<00:12:15.600> now<00:12:16.600> this<00:12:16.780> is<00:12:16.930> easy 00:12:17.100 --> 00:12:17.110 align:start position:0% actually messaging with now this is easy 00:12:17.110 --> 00:12:19.610 align:start position:0% actually messaging with now this is easy just<00:12:17.320> disclose<00:12:18.160> a<00:12:18.400> part<00:12:18.970> of<00:12:19.150> the<00:12:19.270> address 00:12:19.610 --> 00:12:19.620 align:start position:0% just disclose a part of the address 00:12:19.620 --> 00:12:21.690 align:start position:0% just disclose a part of the address swarm<00:12:20.620> routing<00:12:21.010> will<00:12:21.130> still<00:12:21.340> route<00:12:21.550> the 00:12:21.690 --> 00:12:21.700 align:start position:0% swarm routing will still route the 00:12:21.700 --> 00:12:23.280 align:start position:0% swarm routing will still route the message<00:12:22.060> the<00:12:22.240> best<00:12:22.450> it<00:12:22.630> can<00:12:22.810> from<00:12:23.170> the 00:12:23.280 --> 00:12:23.290 align:start position:0% message the best it can from the 00:12:23.290 --> 00:12:25.650 align:start position:0% message the best it can from the knowledge<00:12:23.620> it<00:12:23.770> has<00:12:23.980> so<00:12:24.850> it<00:12:24.970> will<00:12:25.060> land<00:12:25.270> in<00:12:25.450> some 00:12:25.650 --> 00:12:25.660 align:start position:0% knowledge it has so it will land in some 00:12:25.660 --> 00:12:27.480 align:start position:0% knowledge it has so it will land in some neighborhood<00:12:26.110> of<00:12:26.230> nodes<00:12:26.440> closer<00:12:27.100> to<00:12:27.400> the 00:12:27.480 --> 00:12:27.490 align:start position:0% neighborhood of nodes closer to the 00:12:27.490 --> 00:12:30.180 align:start position:0% neighborhood of nodes closer to the recipient<00:12:28.000> than<00:12:28.150> you<00:12:28.620> and<00:12:29.620> ask<00:12:29.800> before 00:12:30.180 --> 00:12:30.190 align:start position:0% recipient than you and ask before 00:12:30.190 --> 00:12:31.560 align:start position:0% recipient than you and ask before whoever<00:12:30.370> in<00:12:30.640> that<00:12:30.760> neighborhood<00:12:31.180> can<00:12:31.330> decrypt 00:12:31.560 --> 00:12:31.570 align:start position:0% whoever in that neighborhood can decrypt 00:12:31.570 --> 00:12:34.040 align:start position:0% whoever in that neighborhood can decrypt the<00:12:31.750> message<00:12:32.080> history<00:12:32.260> recipient<00:12:32.890> or 00:12:34.040 --> 00:12:34.050 align:start position:0% the message history recipient or 00:12:34.050 --> 00:12:37.530 align:start position:0% the message history recipient or recipients<00:12:35.880> doesn't<00:12:36.880> necessarily<00:12:37.390> have<00:12:37.510> to 00:12:37.530 --> 00:12:37.540 align:start position:0% recipients doesn't necessarily have to 00:12:37.540 --> 00:12:40.710 align:start position:0% recipients doesn't necessarily have to be<00:12:37.780> only<00:12:37.930> one<00:12:38.820> now<00:12:39.820> whatever<00:12:40.060> we<00:12:40.300> don't<00:12:40.480> give 00:12:40.710 --> 00:12:40.720 align:start position:0% be only one now whatever we don't give 00:12:40.720 --> 00:12:44.010 align:start position:0% be only one now whatever we don't give address<00:12:40.870> at<00:12:41.200> all<00:12:42.120> this<00:12:43.120> is<00:12:43.330> analogous<00:12:43.720> to<00:12:43.870> what 00:12:44.010 --> 00:12:44.020 align:start position:0% address at all this is analogous to what 00:12:44.020 --> 00:12:46.740 align:start position:0% address at all this is analogous to what whisperer<00:12:44.500> does<00:12:44.910> and<00:12:45.910> the<00:12:46.000> consequence<00:12:46.600> is 00:12:46.740 --> 00:12:46.750 align:start position:0% whisperer does and the consequence is 00:12:46.750 --> 00:12:48.420 align:start position:0% whisperer does and the consequence is that<00:12:46.780> all<00:12:47.080> messages<00:12:47.440> gets<00:12:47.800> passed<00:12:48.040> to<00:12:48.190> all 00:12:48.420 --> 00:12:48.430 align:start position:0% that all messages gets passed to all 00:12:48.430 --> 00:12:49.710 align:start position:0% that all messages gets passed to all nodes<00:12:48.730> by<00:12:48.970> all<00:12:49.240> nodes 00:12:49.710 --> 00:12:49.720 align:start position:0% nodes by all nodes 00:12:49.720 --> 00:12:51.480 align:start position:0% nodes by all nodes this<00:12:50.379> has<00:12:50.529> nothing<00:12:50.680> to<00:12:50.889> do<00:12:51.040> with<00:12:51.069> routing<00:12:51.370> at 00:12:51.480 --> 00:12:51.490 align:start position:0% this has nothing to do with routing at 00:12:51.490 --> 00:12:53.790 align:start position:0% this has nothing to do with routing at all<00:12:51.670> obviously<00:12:52.180> but<00:12:53.019> it<00:12:53.110> might<00:12:53.259> be<00:12:53.350> in<00:12:53.470> handy 00:12:53.790 --> 00:12:53.800 align:start position:0% all obviously but it might be in handy 00:12:53.800 --> 00:12:56.040 align:start position:0% all obviously but it might be in handy in<00:12:53.980> some<00:12:54.519> stages<00:12:54.939> of<00:12:55.060> the<00:12:55.149> communication<00:12:55.750> like 00:12:56.040 --> 00:12:56.050 align:start position:0% in some stages of the communication like 00:12:56.050 --> 00:12:58.439 align:start position:0% in some stages of the communication like when<00:12:56.829> you<00:12:56.920> send<00:12:57.160> a<00:12:57.250> broadcast<00:12:57.399> at<00:12:57.879> probe<00:12:58.120> to 00:12:58.439 --> 00:12:58.449 align:start position:0% when you send a broadcast at probe to 00:12:58.449 --> 00:13:00.329 align:start position:0% when you send a broadcast at probe to enable<00:12:58.750> a<00:12:58.810> pair<00:12:58.959> to<00:12:59.079> send<00:12:59.290> you<00:12:59.350> its<00:12:59.620> address 00:13:00.329 --> 00:13:00.339 align:start position:0% enable a pair to send you its address 00:13:00.339 --> 00:13:03.900 align:start position:0% enable a pair to send you its address but<00:13:00.730> encrypted<00:13:01.329> or<00:13:02.189> to<00:13:03.189> get<00:13:03.399> some<00:13:03.639> temporary 00:13:03.900 --> 00:13:03.910 align:start position:0% but encrypted or to get some temporary 00:13:03.910 --> 00:13:05.340 align:start position:0% but encrypted or to get some temporary encrypted<00:13:04.449> keys<00:13:04.629> that<00:13:04.810> can<00:13:04.930> be<00:13:05.050> discarded 00:13:05.340 --> 00:13:05.350 align:start position:0% encrypted keys that can be discarded 00:13:05.350 --> 00:13:08.579 align:start position:0% encrypted keys that can be discarded later<00:13:06.029> now<00:13:07.029> to<00:13:07.089> make<00:13:07.420> life<00:13:07.660> even<00:13:08.110> harder<00:13:08.139> for 00:13:08.579 --> 00:13:08.589 align:start position:0% later now to make life even harder for 00:13:08.589 --> 00:13:12.240 align:start position:0% later now to make life even harder for screw<00:13:09.160> toe<00:13:09.339> files<00:13:10.290> PSS<00:13:11.290> also<00:13:11.740> employs<00:13:12.160> a 00:13:12.240 --> 00:13:12.250 align:start position:0% screw toe files PSS also employs a 00:13:12.250 --> 00:13:13.949 align:start position:0% screw toe files PSS also employs a redundant<00:13:12.850> routing<00:13:13.269> and<00:13:13.420> this<00:13:13.569> means<00:13:13.810> that 00:13:13.949 --> 00:13:13.959 align:start position:0% redundant routing and this means that 00:13:13.959 --> 00:13:15.660 align:start position:0% redundant routing and this means that when<00:13:14.170> a<00:13:14.230> message<00:13:14.709> enters<00:13:15.189> into<00:13:15.459> the 00:13:15.660 --> 00:13:15.670 align:start position:0% when a message enters into the 00:13:15.670 --> 00:13:17.759 align:start position:0% when a message enters into the neighbourhood<00:13:16.209> of<00:13:16.389> the<00:13:16.540> destination<00:13:17.110> the 00:13:17.759 --> 00:13:17.769 align:start position:0% neighbourhood of the destination the 00:13:17.769 --> 00:13:19.559 align:start position:0% neighbourhood of the destination the node<00:13:18.009> that<00:13:18.040> receives<00:13:18.670> the<00:13:18.939> message<00:13:19.089> for 00:13:19.559 --> 00:13:19.569 align:start position:0% node that receives the message for 00:13:19.569 --> 00:13:22.110 align:start position:0% node that receives the message for forwarding<00:13:20.079> will<00:13:20.560> pass<00:13:20.800> on<00:13:21.040> the<00:13:21.189> messages<00:13:21.610> to 00:13:22.110 --> 00:13:22.120 align:start position:0% forwarding will pass on the messages to 00:13:22.120 --> 00:13:25.530 align:start position:0% forwarding will pass on the messages to more<00:13:22.389> than<00:13:22.600> one<00:13:22.810> peer<00:13:23.250> this<00:13:24.250> happens<00:13:24.730> even<00:13:25.060> if 00:13:25.530 --> 00:13:25.540 align:start position:0% more than one peer this happens even if 00:13:25.540 --> 00:13:27.420 align:start position:0% more than one peer this happens even if the<00:13:25.779> node<00:13:26.019> can<00:13:26.290> successfully<00:13:26.740> decrypt<00:13:27.310> the 00:13:27.420 --> 00:13:27.430 align:start position:0% the node can successfully decrypt the 00:13:27.430 --> 00:13:30.449 align:start position:0% the node can successfully decrypt the message<00:13:27.730> this<00:13:28.540> one<00:13:28.810> anyone<00:13:29.740> trying<00:13:30.069> to<00:13:30.220> trace 00:13:30.449 --> 00:13:30.459 align:start position:0% message this one anyone trying to trace 00:13:30.459 --> 00:13:32.699 align:start position:0% message this one anyone trying to trace a<00:13:30.490> message<00:13:30.970> path<00:13:31.269> through<00:13:31.720> the<00:13:31.839> network<00:13:31.870> will 00:13:32.699 --> 00:13:32.709 align:start position:0% a message path through the network will 00:13:32.709 --> 00:13:35.129 align:start position:0% a message path through the network will have<00:13:32.949> difficulty<00:13:33.579> finding<00:13:33.819> out<00:13:34.329> where<00:13:34.959> the 00:13:35.129 --> 00:13:35.139 align:start position:0% have difficulty finding out where the 00:13:35.139 --> 00:13:37.710 align:start position:0% have difficulty finding out where the message<00:13:35.439> actually<00:13:35.649> stopped<00:13:36.240> that<00:13:37.240> is<00:13:37.389> to<00:13:37.509> say 00:13:37.710 --> 00:13:37.720 align:start position:0% message actually stopped that is to say 00:13:37.720 --> 00:13:40.350 align:start position:0% message actually stopped that is to say the<00:13:38.139> node<00:13:38.290> not<00:13:38.560> passing<00:13:39.310> the<00:13:39.579> message<00:13:39.730> anymore 00:13:40.350 --> 00:13:40.360 align:start position:0% the node not passing the message anymore 00:13:40.360 --> 00:13:42.660 align:start position:0% the node not passing the message anymore are<00:13:40.569> not<00:13:41.050> guaranteed<00:13:41.290> to<00:13:41.740> be<00:13:41.889> the<00:13:42.040> one<00:13:42.220> the 00:13:42.660 --> 00:13:42.670 align:start position:0% are not guaranteed to be the one the 00:13:42.670 --> 00:13:45.600 align:start position:0% are not guaranteed to be the one the message<00:13:42.970> was<00:13:43.120> actually<00:13:43.269> for<00:13:43.720> in<00:13:44.050> fact<00:13:44.889> most 00:13:45.600 --> 00:13:45.610 align:start position:0% message was actually for in fact most 00:13:45.610 --> 00:13:48.960 align:start position:0% message was actually for in fact most likely<00:13:45.699> it<00:13:46.209> won't<00:13:46.480> be<00:13:47.129> so<00:13:48.129> all<00:13:48.579> good<00:13:48.850> and<00:13:48.939> well 00:13:48.960 --> 00:13:48.970 align:start position:0% likely it won't be so all good and well 00:13:48.970 --> 00:13:50.970 align:start position:0% likely it won't be so all good and well you<00:13:49.089> got<00:13:49.300> the<00:13:49.389> message<00:13:49.540> you<00:13:50.350> can<00:13:50.500> encrypt<00:13:50.740> it 00:13:50.970 --> 00:13:50.980 align:start position:0% you got the message you can encrypt it 00:13:50.980 --> 00:13:54.269 align:start position:0% you got the message you can encrypt it what<00:13:51.279> do<00:13:51.339> you<00:13:51.399> do<00:13:51.579> with<00:13:51.699> it<00:13:51.870> well<00:13:52.870> for<00:13:53.470> this<00:13:53.620> PSS 00:13:54.269 --> 00:13:54.279 align:start position:0% what do you do with it well for this PSS 00:13:54.279 --> 00:13:56.549 align:start position:0% what do you do with it well for this PSS has<00:13:54.490> the<00:13:54.639> notion<00:13:54.939> of<00:13:55.029> topics<00:13:55.480> all<00:13:55.990> messages 00:13:56.549 --> 00:13:56.559 align:start position:0% has the notion of topics all messages 00:13:56.559 --> 00:13:58.170 align:start position:0% has the notion of topics all messages that<00:13:56.740> are<00:13:56.860> sent<00:13:56.889> belong<00:13:57.370> to<00:13:57.550> a<00:13:57.579> specific<00:13:57.759> part 00:13:58.170 --> 00:13:58.180 align:start position:0% that are sent belong to a specific part 00:13:58.180 --> 00:14:01.049 align:start position:0% that are sent belong to a specific part topic<00:13:58.629> which<00:13:59.470> could<00:13:59.680> be<00:13:59.829> any<00:14:00.069> four<00:14:00.490> byte<00:14:00.670> value 00:14:01.049 --> 00:14:01.059 align:start position:0% topic which could be any four byte value 00:14:01.059 --> 00:14:03.480 align:start position:0% topic which could be any four byte value but<00:14:01.509> intended<00:14:01.959> to<00:14:02.079> be<00:14:02.170> the<00:14:02.319> first<00:14:02.559> four<00:14:03.129> bytes 00:14:03.480 --> 00:14:03.490 align:start position:0% but intended to be the first four bytes 00:14:03.490 --> 00:14:08.129 align:start position:0% but intended to be the first four bytes of<00:14:03.819> the<00:14:03.910> hash<00:14:04.120> of<00:14:04.480> an<00:14:04.629> arbitrary<00:14:05.290> value<00:14:07.139> PSS 00:14:08.129 --> 00:14:08.139 align:start position:0% of the hash of an arbitrary value PSS 00:14:08.139 --> 00:14:10.110 align:start position:0% of the hash of an arbitrary value PSS provides<00:14:08.470> a<00:14:08.559> registration<00:14:09.009> method<00:14:09.519> method<00:14:10.000> to 00:14:10.110 --> 00:14:10.120 align:start position:0% provides a registration method method to 00:14:10.120 --> 00:14:13.290 align:start position:0% provides a registration method method to attach<00:14:10.240> code<00:14:10.839> to<00:14:11.110> these<00:14:11.259> topics<00:14:12.300> therefore 00:14:13.290 --> 00:14:13.300 align:start position:0% attach code to these topics therefore 00:14:13.300 --> 00:14:14.579 align:start position:0% attach code to these topics therefore when<00:14:13.449> a<00:14:13.480> node<00:14:13.660> gets<00:14:13.899> a<00:14:14.019> message<00:14:14.199> with<00:14:14.529> a 00:14:14.579 --> 00:14:14.589 align:start position:0% when a node gets a message with a 00:14:14.589 --> 00:14:16.110 align:start position:0% when a node gets a message with a certain<00:14:14.860> topic<00:14:15.040> on<00:14:15.309> it<00:14:15.430> it<00:14:15.579> knows<00:14:15.759> exactly 00:14:16.110 --> 00:14:16.120 align:start position:0% certain topic on it it knows exactly 00:14:16.120 --> 00:14:19.439 align:start position:0% certain topic on it it knows exactly what<00:14:16.449> to<00:14:16.540> do<00:14:16.629> with<00:14:16.779> it<00:14:17.639> the<00:14:18.639> topic<00:14:18.879> structure 00:14:19.439 --> 00:14:19.449 align:start position:0% what to do with it the topic structure 00:14:19.449 --> 00:14:21.240 align:start position:0% what to do with it the topic structure is<00:14:19.629> the<00:14:19.750> same<00:14:19.930> topic<00:14:20.350> structure<00:14:20.740> as<00:14:20.860> whisper 00:14:21.240 --> 00:14:21.250 align:start position:0% is the same topic structure as whisper 00:14:21.250 --> 00:14:23.280 align:start position:0% is the same topic structure as whisper uses<00:14:21.519> Forsyth's<00:14:21.970> envelopes<00:14:22.480> envelopes<00:14:23.079> here 00:14:23.280 --> 00:14:23.290 align:start position:0% uses Forsyth's envelopes envelopes here 00:14:23.290 --> 00:14:25.110 align:start position:0% uses Forsyth's envelopes envelopes here meaning<00:14:23.500> the<00:14:23.620> entity<00:14:24.279> that<00:14:24.490> encapsulates 00:14:25.110 --> 00:14:25.120 align:start position:0% meaning the entity that encapsulates 00:14:25.120 --> 00:14:28.949 align:start position:0% meaning the entity that encapsulates contents<00:14:26.110> in<00:14:26.230> the<00:14:26.319> sshh<00:14:27.220> protocol<00:14:27.819> in<00:14:28.029> fact 00:14:28.949 --> 00:14:28.959 align:start position:0% contents in the sshh protocol in fact 00:14:28.959 --> 00:14:31.110 align:start position:0% contents in the sshh protocol in fact PSS<00:14:29.470> actually<00:14:29.889> cheekily<00:14:30.279> steals<00:14:30.699> this 00:14:31.110 --> 00:14:31.120 align:start position:0% PSS actually cheekily steals this 00:14:31.120 --> 00:14:33.749 align:start position:0% PSS actually cheekily steals this whisper<00:14:31.809> envelope<00:14:32.259> to<00:14:32.470> wrap<00:14:32.620> messages<00:14:33.129> in 00:14:33.749 --> 00:14:33.759 align:start position:0% whisper envelope to wrap messages in 00:14:33.759 --> 00:14:37.049 align:start position:0% whisper envelope to wrap messages in reality<00:14:34.569> all<00:14:34.959> PSS<00:14:35.829> does<00:14:36.040> is<00:14:36.250> just<00:14:36.490> to<00:14:36.610> slap<00:14:36.819> an 00:14:37.049 --> 00:14:37.059 align:start position:0% reality all PSS does is just to slap an 00:14:37.059 --> 00:14:43.530 align:start position:0% reality all PSS does is just to slap an address<00:14:37.779> on<00:14:37.930> top<00:14:38.110> of<00:14:38.230> it<00:14:38.319> or<00:14:39.220> not<00:14:41.879> the<00:14:42.879> whisper 00:14:43.530 --> 00:14:43.540 align:start position:0% address on top of it or not the whisper 00:14:43.540 --> 00:14:45.900 align:start position:0% address on top of it or not the whisper envelope<00:14:44.470> also<00:14:44.949> provides<00:14:45.309> an<00:14:45.490> expiry 00:14:45.900 --> 00:14:45.910 align:start position:0% envelope also provides an expiry 00:14:45.910 --> 00:14:48.030 align:start position:0% envelope also provides an expiry parameter<00:14:46.360> this<00:14:46.809> is<00:14:46.959> used<00:14:47.170> by<00:14:47.259> PSS<00:14:47.680> to<00:14:47.829> stop 00:14:48.030 --> 00:14:48.040 align:start position:0% parameter this is used by PSS to stop 00:14:48.040 --> 00:14:49.619 align:start position:0% parameter this is used by PSS to stop messages<00:14:48.490> in<00:14:48.579> from<00:14:48.699> circulating<00:14:49.360> in<00:14:49.569> the 00:14:49.619 --> 00:14:49.629 align:start position:0% messages in from circulating in the 00:14:49.629 --> 00:14:52.439 align:start position:0% messages in from circulating in the network<00:14:49.959> perpetually<00:14:50.470> and<00:14:50.769> finally<00:14:51.759> PSS<00:14:52.149> uses 00:14:52.439 --> 00:14:52.449 align:start position:0% network perpetually and finally PSS uses 00:14:52.449 --> 00:14:53.790 align:start position:0% network perpetually and finally PSS uses whisper<00:14:52.779> also<00:14:53.079> has<00:14:53.170> a<00:14:53.199> back-end<00:14:53.470> for 00:14:53.790 --> 00:14:53.800 align:start position:0% whisper also has a back-end for 00:14:53.800 --> 00:14:56.299 align:start position:0% whisper also has a back-end for encryption<00:14:54.100> and<00:14:54.459> handling<00:14:55.180> of<00:14:55.269> keys<00:14:55.509> as 00:14:56.299 --> 00:14:56.309 align:start position:0% encryption and handling of keys as 00:14:56.309 --> 00:15:00.299 align:start position:0% encryption and handling of keys as whisper<00:14:57.309> psst<00:14:58.889> cryptography<00:14:59.889> as<00:14:59.980> well<00:15:00.160> as<00:15:00.279> a 00:15:00.299 --> 00:15:00.309 align:start position:0% whisper psst cryptography as well as a 00:15:00.309 --> 00:15:03.090 align:start position:0% whisper psst cryptography as well as a symmetric<00:15:00.970> arbitrary<00:15:01.929> symmetric<00:15:02.589> encryption 00:15:03.090 --> 00:15:03.100 align:start position:0% symmetric arbitrary symmetric encryption 00:15:03.100 --> 00:15:06.150 align:start position:0% symmetric arbitrary symmetric encryption so<00:15:03.460> any<00:15:03.720> 32-byte<00:15:04.720> value<00:15:05.260> is<00:15:05.440> actually<00:15:05.800> valid 00:15:06.150 --> 00:15:06.160 align:start position:0% so any 32-byte value is actually valid 00:15:06.160 --> 00:15:08.490 align:start position:0% so any 32-byte value is actually valid as<00:15:06.400> a<00:15:06.670> symmetric<00:15:07.150> key<00:15:07.180> and<00:15:07.420> PSS<00:15:07.810> and<00:15:08.140> can<00:15:08.410> be 00:15:08.490 --> 00:15:08.500 align:start position:0% as a symmetric key and PSS and can be 00:15:08.500 --> 00:15:11.220 align:start position:0% as a symmetric key and PSS and can be set<00:15:08.710> at<00:15:08.860> the<00:15:08.890> developers<00:15:09.400> discretion<00:15:10.140> so<00:15:11.140> to 00:15:11.220 --> 00:15:11.230 align:start position:0% set at the developers discretion so to 00:15:11.230 --> 00:15:14.040 align:start position:0% set at the developers discretion so to sum<00:15:11.560> up<00:15:11.590> to<00:15:12.070> send<00:15:12.280> a<00:15:12.340> message<00:15:12.640> in<00:15:12.820> a<00:15:12.910> to<00:15:13.570> a<00:15:13.600> PSS 00:15:14.040 --> 00:15:14.050 align:start position:0% sum up to send a message in a to a PSS 00:15:14.050 --> 00:15:17.400 align:start position:0% sum up to send a message in a to a PSS note<00:15:14.290> all<00:15:14.530> you<00:15:14.740> need<00:15:14.920> is<00:15:15.460> a<00:15:15.490> key<00:15:15.790> the<00:15:16.690> topic<00:15:17.140> and 00:15:17.400 --> 00:15:17.410 align:start position:0% note all you need is a key the topic and 00:15:17.410 --> 00:15:22.440 align:start position:0% note all you need is a key the topic and an<00:15:18.100> address<00:15:18.390> or<00:15:19.390> not<00:15:20.700> so<00:15:21.700> what<00:15:21.820> exactly<00:15:22.000> right 00:15:22.440 --> 00:15:22.450 align:start position:0% an address or not so what exactly right 00:15:22.450 --> 00:15:25.050 align:start position:0% an address or not so what exactly right now<00:15:22.600> this<00:15:22.840> PSS<00:15:23.200> implement<00:15:23.650> the<00:15:24.550> encryption 00:15:25.050 --> 00:15:25.060 align:start position:0% now this PSS implement the encryption 00:15:25.060 --> 00:15:28.650 align:start position:0% now this PSS implement the encryption has<00:15:25.210> said<00:15:26.160> luminosity<00:15:27.160> control<00:15:27.850> which<00:15:28.480> is<00:15:28.510> a 00:15:28.650 --> 00:15:28.660 align:start position:0% has said luminosity control which is a 00:15:28.660 --> 00:15:30.540 align:start position:0% has said luminosity control which is a fancy<00:15:29.080> word<00:15:29.200> for<00:15:29.260> deciding<00:15:29.830> how<00:15:29.950> many<00:15:30.010> address 00:15:30.540 --> 00:15:30.550 align:start position:0% fancy word for deciding how many address 00:15:30.550 --> 00:15:33.600 align:start position:0% fancy word for deciding how many address bytes<00:15:30.880> who<00:15:31.150> disclose<00:15:31.920> we<00:15:32.920> have<00:15:33.070> a<00:15:33.100> generic 00:15:33.600 --> 00:15:33.610 align:start position:0% bytes who disclose we have a generic 00:15:33.610 --> 00:15:35.520 align:start position:0% bytes who disclose we have a generic handshake<00:15:34.210> module<00:15:34.600> which<00:15:34.810> gives<00:15:35.230> you<00:15:35.470> a 00:15:35.520 --> 00:15:35.530 align:start position:0% handshake module which gives you a 00:15:35.530 --> 00:15:37.710 align:start position:0% handshake module which gives you a simple<00:15:35.980> diffie-hellman<00:15:36.370> exchange<00:15:36.940> of<00:15:37.540> keys 00:15:37.710 --> 00:15:37.720 align:start position:0% simple diffie-hellman exchange of keys 00:15:37.720 --> 00:15:39.420 align:start position:0% simple diffie-hellman exchange of keys in<00:15:37.930> case<00:15:38.110> you're<00:15:38.380> too<00:15:38.500> lazy<00:15:38.710> to<00:15:38.980> make<00:15:39.130> your<00:15:39.310> own 00:15:39.420 --> 00:15:39.430 align:start position:0% in case you're too lazy to make your own 00:15:39.430 --> 00:15:41.910 align:start position:0% in case you're too lazy to make your own and<00:15:39.820> the<00:15:40.780> keys<00:15:40.930> generated<00:15:41.440> by<00:15:41.500> the<00:15:41.560> handshake 00:15:41.910 --> 00:15:41.920 align:start position:0% and the keys generated by the handshake 00:15:41.920 --> 00:15:43.410 align:start position:0% and the keys generated by the handshake module<00:15:42.250> are<00:15:42.430> valid<00:15:42.820> only<00:15:42.940> for<00:15:43.090> a<00:15:43.240> certain 00:15:43.410 --> 00:15:43.420 align:start position:0% module are valid only for a certain 00:15:43.420 --> 00:15:45.180 align:start position:0% module are valid only for a certain number<00:15:43.930> of<00:15:43.990> messages<00:15:44.380> that<00:15:44.620> is<00:15:44.890> to<00:15:45.040> say 00:15:45.180 --> 00:15:45.190 align:start position:0% number of messages that is to say 00:15:45.190 --> 00:15:47.520 align:start position:0% number of messages that is to say they're<00:15:45.430> ephemeral<00:15:46.290> handshakes<00:15:47.290> can<00:15:47.470> be 00:15:47.520 --> 00:15:47.530 align:start position:0% they're ephemeral handshakes can be 00:15:47.530 --> 00:15:49.380 align:start position:0% they're ephemeral handshakes can be optionally<00:15:48.250> also<00:15:48.460> left<00:15:48.970> out<00:15:49.180> of<00:15:49.210> the 00:15:49.380 --> 00:15:49.390 align:start position:0% optionally also left out of the 00:15:49.390 --> 00:15:51.960 align:start position:0% optionally also left out of the compilation<00:15:49.690> of<00:15:49.990> go<00:15:50.140> etherion<00:15:50.700> there<00:15:51.700> is<00:15:51.820> an 00:15:51.960 --> 00:15:51.970 align:start position:0% compilation of go etherion there is an 00:15:51.970 --> 00:15:54.420 align:start position:0% compilation of go etherion there is an API<00:15:52.240> of<00:15:52.570> course<00:15:52.810> available<00:15:53.170> over<00:15:53.590> IPC<00:15:54.100> and 00:15:54.420 --> 00:15:54.430 align:start position:0% API of course available over IPC and 00:15:54.430 --> 00:15:56.490 align:start position:0% API of course available over IPC and WebSockets<00:15:55.390> for<00:15:55.570> key<00:15:55.720> handling<00:15:56.110> message 00:15:56.490 --> 00:15:56.500 align:start position:0% WebSockets for key handling message 00:15:56.500 --> 00:15:58.950 align:start position:0% WebSockets for key handling message passing<00:15:56.770> handshakes<00:15:57.610> and<00:15:58.000> common<00:15:58.570> supporting 00:15:58.950 --> 00:15:58.960 align:start position:0% passing handshakes and common supporting 00:15:58.960 --> 00:16:01.290 align:start position:0% passing handshakes and common supporting functions<00:15:59.080> that<00:15:59.470> are<00:15:59.590> needed<00:15:59.830> a<00:16:00.010> simple<00:16:00.970> flood 00:16:01.290 --> 00:16:01.300 align:start position:0% functions that are needed a simple flood 00:16:01.300 --> 00:16:03.180 align:start position:0% functions that are needed a simple flood protection<00:16:01.480> all<00:16:02.050> nodes<00:16:02.590> that<00:16:02.800> get<00:16:03.040> the 00:16:03.180 --> 00:16:03.190 align:start position:0% protection all nodes that get the 00:16:03.190 --> 00:16:05.100 align:start position:0% protection all nodes that get the message<00:16:03.520> store<00:16:03.820> the<00:16:03.940> message<00:16:04.060> on<00:16:04.360> swarm<00:16:04.810> and 00:16:05.100 --> 00:16:05.110 align:start position:0% message store the message on swarm and 00:16:05.110 --> 00:16:07.530 align:start position:0% message store the message on swarm and use<00:16:05.680> the<00:16:05.920> hash<00:16:06.130> of<00:16:06.460> the<00:16:06.610> message<00:16:06.640> or<00:16:07.150> the<00:16:07.180> chunk 00:16:07.530 --> 00:16:07.540 align:start position:0% use the hash of the message or the chunk 00:16:07.540 --> 00:16:09.510 align:start position:0% use the hash of the message or the chunk to<00:16:07.870> determine<00:16:08.470> if<00:16:08.620> they've<00:16:08.830> seen<00:16:09.310> this 00:16:09.510 --> 00:16:09.520 align:start position:0% to determine if they've seen this 00:16:09.520 --> 00:16:10.800 align:start position:0% to determine if they've seen this message<00:16:09.880> just<00:16:10.030> before<00:16:10.390> and<00:16:10.540> can<00:16:10.600> optionally 00:16:10.800 --> 00:16:10.810 align:start position:0% message just before and can optionally 00:16:10.810 --> 00:16:14.310 align:start position:0% message just before and can optionally have<00:16:11.200> not<00:16:12.190> forward<00:16:12.730> it<00:16:12.850> and<00:16:13.030> finally<00:16:13.810> you<00:16:14.170> can 00:16:14.310 --> 00:16:14.320 align:start position:0% have not forward it and finally you can 00:16:14.320 --> 00:16:17.730 align:start position:0% have not forward it and finally you can actually<00:16:14.500> use<00:16:15.010> PSS<00:16:15.790> with<00:16:16.690> the<00:16:16.960> dev<00:16:17.170> p2p 00:16:17.730 --> 00:16:17.740 align:start position:0% actually use PSS with the dev p2p 00:16:17.740 --> 00:16:19.500 align:start position:0% actually use PSS with the dev p2p protocol<00:16:18.310> structure<00:16:18.790> that<00:16:18.910> exists<00:16:19.390> already 00:16:19.500 --> 00:16:19.510 align:start position:0% protocol structure that exists already 00:16:19.510 --> 00:16:21.780 align:start position:0% protocol structure that exists already the<00:16:19.870> logic<00:16:20.320> so<00:16:21.010> this<00:16:21.160> means<00:16:21.370> you<00:16:21.460> can<00:16:21.580> reuse 00:16:21.780 --> 00:16:21.790 align:start position:0% the logic so this means you can reuse 00:16:21.790 --> 00:16:23.610 align:start position:0% the logic so this means you can reuse Stephie<00:16:22.420> TP<00:16:22.690> code<00:16:22.900> that's<00:16:23.080> already<00:16:23.170> there 00:16:23.610 --> 00:16:23.620 align:start position:0% Stephie TP code that's already there 00:16:23.620 --> 00:16:26.400 align:start position:0% Stephie TP code that's already there this<00:16:24.460> can<00:16:24.700> be<00:16:24.850> either<00:16:25.150> integrated<00:16:26.020> into<00:16:26.320> the 00:16:26.400 --> 00:16:26.410 align:start position:0% this can be either integrated into the 00:16:26.410 --> 00:16:28.920 align:start position:0% this can be either integrated into the code<00:16:26.620> of<00:16:26.770> the<00:16:26.920> node<00:16:27.190> itself<00:16:27.520> or<00:16:28.240> the<00:16:28.540> results 00:16:28.920 --> 00:16:28.930 align:start position:0% code of the node itself or the results 00:16:28.930 --> 00:16:31.200 align:start position:0% code of the node itself or the results to<00:16:28.990> a<00:16:29.020> module<00:16:29.290> that<00:16:29.830> enables<00:16:30.310> you<00:16:30.460> to<00:16:30.490> use<00:16:30.670> to 00:16:31.200 --> 00:16:31.210 align:start position:0% to a module that enables you to use to 00:16:31.210 --> 00:16:32.910 align:start position:0% to a module that enables you to use to do<00:16:31.330> this<00:16:31.510> in<00:16:31.660> a<00:16:31.750> separate<00:16:32.050> process<00:16:32.200> using 00:16:32.910 --> 00:16:32.920 align:start position:0% do this in a separate process using 00:16:32.920 --> 00:16:36.090 align:start position:0% do this in a separate process using WebSockets<00:16:33.310> as<00:16:33.730> the<00:16:33.880> transport<00:16:34.240> layer<00:16:34.650> now<00:16:35.650> I 00:16:36.090 --> 00:16:36.100 align:start position:0% WebSockets as the transport layer now I 00:16:36.100 --> 00:16:39.120 align:start position:0% WebSockets as the transport layer now I probably<00:16:36.520> overstayed<00:16:37.090> my<00:16:37.120> time<00:16:38.110> I'm<00:16:38.770> not<00:16:39.100> sure 00:16:39.120 --> 00:16:39.130 align:start position:0% probably overstayed my time I'm not sure 00:16:39.130 --> 00:16:41.820 align:start position:0% probably overstayed my time I'm not sure but<00:16:39.520> anyway<00:16:40.300> there<00:16:40.720> is<00:16:41.020> a<00:16:41.050> more<00:16:41.500> thorough 00:16:41.820 --> 00:16:41.830 align:start position:0% but anyway there is a more thorough 00:16:41.830 --> 00:16:44.640 align:start position:0% but anyway there is a more thorough walkthrough<00:16:42.220> of<00:16:42.820> PSS<00:16:43.690> on<00:16:43.990> Saturday<00:16:44.500> in<00:16:44.620> the 00:16:44.640 --> 00:16:44.650 align:start position:0% walkthrough of PSS on Saturday in the 00:16:44.650 --> 00:16:47.250 align:start position:0% walkthrough of PSS on Saturday in the breakout<00:16:45.070> session<00:16:45.610> quarter<00:16:46.480> past<00:16:46.690> two<00:16:46.990> in 00:16:47.250 --> 00:16:47.260 align:start position:0% breakout session quarter past two in 00:16:47.260 --> 00:16:50.310 align:start position:0% breakout session quarter past two in this<00:16:48.030> go<00:16:49.030> through<00:16:49.870> a<00:16:49.900> bit<00:16:50.080> more 00:16:50.310 --> 00:16:50.320 align:start position:0% this go through a bit more 00:16:50.320 --> 00:16:52.740 align:start position:0% this go through a bit more through<00:16:51.130> a<00:16:51.220> bit<00:16:51.370> more<00:16:51.550> of<00:16:51.640> the<00:16:51.730> internals<00:16:52.270> what 00:16:52.740 --> 00:16:52.750 align:start position:0% through a bit more of the internals what 00:16:52.750 --> 00:16:57.180 align:start position:0% through a bit more of the internals what makes<00:16:52.990> PSS<00:16:53.440> tick<00:16:54.510> the<00:16:55.510> API<00:16:55.840> will<00:16:56.590> present<00:16:56.980> that 00:16:57.180 --> 00:16:57.190 align:start position:0% makes PSS tick the API will present that 00:16:57.190 --> 00:16:59.370 align:start position:0% makes PSS tick the API will present that and<00:16:57.550> there<00:16:58.060> will<00:16:58.120> also<00:16:58.240> be<00:16:58.450> a<00:16:58.600> demonstration 00:16:59.370 --> 00:16:59.380 align:start position:0% and there will also be a demonstration 00:16:59.380 --> 00:17:03.390 align:start position:0% and there will also be a demonstration of<00:16:59.980> a<00:17:00.430> chat<00:17:00.820> app<00:17:01.060> that's<00:17:01.750> actually<00:17:02.380> using<00:17:02.920> PSS 00:17:03.390 --> 00:17:03.400 align:start position:0% of a chat app that's actually using PSS 00:17:03.400 --> 00:17:04.949 align:start position:0% of a chat app that's actually using PSS right<00:17:03.670> now<00:17:03.940> I<00:17:03.970> mean<00:17:04.300> it's<00:17:04.480> not<00:17:04.600> a<00:17:04.660> production 00:17:04.949 --> 00:17:04.959 align:start position:0% right now I mean it's not a production 00:17:04.959 --> 00:17:07.550 align:start position:0% right now I mean it's not a production ready<00:17:05.230> thing<00:17:05.530> as<00:17:05.650> a<00:17:05.680> demonstration<00:17:06.310> prototype 00:17:07.550 --> 00:17:07.560 align:start position:0% ready thing as a demonstration prototype 00:17:07.560 --> 00:17:11.250 align:start position:0% ready thing as a demonstration prototype so<00:17:08.560> and<00:17:09.280> this<00:17:09.760> is<00:17:10.089> not<00:17:10.390> only<00:17:10.540> demonstration 00:17:11.250 --> 00:17:11.260 align:start position:0% so and this is not only demonstration 00:17:11.260 --> 00:17:12.840 align:start position:0% so and this is not only demonstration from<00:17:11.560> the<00:17:11.709> screen<00:17:12.010> but<00:17:12.280> actually<00:17:12.730> the 00:17:12.840 --> 00:17:12.850 align:start position:0% from the screen but actually the 00:17:12.850 --> 00:17:16.050 align:start position:0% from the screen but actually the audience<00:17:13.110> will<00:17:14.110> be<00:17:14.260> you<00:17:14.470> guys<00:17:14.730> will<00:17:15.730> be<00:17:15.760> able 00:17:16.050 --> 00:17:16.060 align:start position:0% audience will be you guys will be able 00:17:16.060 --> 00:17:16.860 align:start position:0% audience will be you guys will be able to 00:17:16.860 --> 00:17:16.870 align:start position:0% to 00:17:16.870 --> 00:17:19.319 align:start position:0% to install<00:17:17.289> the<00:17:17.470> app<00:17:17.620> and<00:17:17.890> chat<00:17:18.370> with<00:17:18.760> us<00:17:18.939> live 00:17:19.319 --> 00:17:19.329 align:start position:0% install the app and chat with us live 00:17:19.329 --> 00:17:25.679 align:start position:0% install the app and chat with us live air<00:17:19.870> photos<00:17:20.650> well<00:17:21.010> that<00:17:21.279> is<00:17:21.429> to<00:17:21.549> say<00:17:24.120> yes<00:17:25.120> so<00:17:25.480> if 00:17:25.679 --> 00:17:25.689 align:start position:0% air photos well that is to say yes so if 00:17:25.689 --> 00:17:27.990 align:start position:0% air photos well that is to say yes so if you<00:17:25.809> can't<00:17:26.020> wait<00:17:26.260> till<00:17:26.470> then<00:17:26.740> there<00:17:27.699> are<00:17:27.880> some 00:17:27.990 --> 00:17:28.000 align:start position:0% you can't wait till then there are some 00:17:28.000 --> 00:17:30.120 align:start position:0% you can't wait till then there are some links<00:17:28.209> on<00:17:28.809> top<00:17:29.080> is<00:17:29.320> the<00:17:29.470> branch<00:17:29.710> where<00:17:30.039> the 00:17:30.120 --> 00:17:30.130 align:start position:0% links on top is the branch where the 00:17:30.130 --> 00:17:32.850 align:start position:0% links on top is the branch where the active<00:17:30.549> PSS<00:17:30.909> code<00:17:31.120> is<00:17:31.240> now<00:17:31.470> PSS<00:17:32.470> will<00:17:32.740> be<00:17:32.830> a 00:17:32.850 --> 00:17:32.860 align:start position:0% active PSS code is now PSS will be a 00:17:32.860 --> 00:17:35.100 align:start position:0% active PSS code is now PSS will be a part<00:17:33.100> of<00:17:33.190> POC<00:17:33.490> 3<00:17:34.029> for<00:17:34.299> swarm<00:17:34.570> so<00:17:34.779> this<00:17:34.900> means 00:17:35.100 --> 00:17:35.110 align:start position:0% part of POC 3 for swarm so this means 00:17:35.110 --> 00:17:37.019 align:start position:0% part of POC 3 for swarm so this means you<00:17:35.260> won't<00:17:35.350> find<00:17:35.710> it<00:17:35.860> in<00:17:36.010> the<00:17:36.130> ethereal<00:17:36.429> master 00:17:37.019 --> 00:17:37.029 align:start position:0% you won't find it in the ethereal master 00:17:37.029 --> 00:17:39.149 align:start position:0% you won't find it in the ethereal master repo<00:17:37.630> now<00:17:38.020> it'll<00:17:38.590> be<00:17:38.620> later<00:17:38.890> on 00:17:39.149 --> 00:17:39.159 align:start position:0% repo now it'll be later on 00:17:39.159 --> 00:17:41.640 align:start position:0% repo now it'll be later on there<00:17:40.000> is<00:17:40.120> a<00:17:40.150> description<00:17:40.570> of<00:17:40.779> the<00:17:40.840> API<00:17:41.200> and 00:17:41.640 --> 00:17:41.650 align:start position:0% there is a description of the API and 00:17:41.650 --> 00:17:44.730 align:start position:0% there is a description of the API and also<00:17:42.159> there<00:17:42.669> are<00:17:42.820> some<00:17:43.179> code<00:17:43.450> examples<00:17:43.740> for 00:17:44.730 --> 00:17:44.740 align:start position:0% also there are some code examples for 00:17:44.740 --> 00:17:47.130 align:start position:0% also there are some code examples for both<00:17:45.070> the<00:17:45.370> generator<00:17:46.179> generate<00:17:46.659> p2p 00:17:47.130 --> 00:17:47.140 align:start position:0% both the generator generate p2p 00:17:47.140 --> 00:17:50.700 align:start position:0% both the generator generate p2p programming<00:17:47.950> in<00:17:48.419> Goa<00:17:49.419> theorem<00:17:49.809> along<00:17:50.470> with<00:17:50.679> a 00:17:50.700 --> 00:17:50.710 align:start position:0% programming in Goa theorem along with a 00:17:50.710 --> 00:17:53.100 align:start position:0% programming in Goa theorem along with a bunch<00:17:50.860> of<00:17:51.039> PSS<00:17:51.520> examples<00:17:52.419> on<00:17:52.570> the<00:17:52.659> bottom<00:17:52.929> link 00:17:53.100 --> 00:17:53.110 align:start position:0% bunch of PSS examples on the bottom link 00:17:53.110 --> 00:18:01.110 align:start position:0% bunch of PSS examples on the bottom link there<00:17:53.350> and<00:17:54.309> I<00:17:54.370> think<00:17:54.640> that<00:17:54.850> was<00:17:55.029> it<00:17:55.539> yes<00:18:00.120> Donnie 00:18:01.110 --> 00:18:01.120 align:start position:0% there and I think that was it yes Donnie 00:18:01.120 --> 00:18:09.480 align:start position:0% there and I think that was it yes Donnie what<00:18:01.539> a<00:18:01.570> good<00:18:01.809> scene<00:18:07.020> hello<00:18:08.020> everyone<00:18:08.490> I'm 00:18:09.480 --> 00:18:09.490 align:start position:0% what a good scene hello everyone I'm 00:18:09.490 --> 00:18:12.990 align:start position:0% what a good scene hello everyone I'm going<00:18:09.850> to<00:18:10.029> talk<00:18:10.270> about<00:18:10.600> the<00:18:11.529> first<00:18:12.039> swarm 00:18:12.990 --> 00:18:13.000 align:start position:0% going to talk about the first swarm 00:18:13.000 --> 00:18:17.070 align:start position:0% going to talk about the first swarm based<00:18:13.799> application<00:18:14.799> that<00:18:15.520> is<00:18:15.850> aimed<00:18:16.210> at<00:18:16.570> a 00:18:17.070 --> 00:18:17.080 align:start position:0% based application that is aimed at a 00:18:17.080 --> 00:18:19.680 align:start position:0% based application that is aimed at a wide<00:18:18.070> audience<00:18:18.309> basically<00:18:19.090> the<00:18:19.539> general 00:18:19.680 --> 00:18:19.690 align:start position:0% wide audience basically the general 00:18:19.690 --> 00:18:27.539 align:start position:0% wide audience basically the general public<00:18:22.350> so<00:18:23.640> this<00:18:24.640> is<00:18:24.880> a<00:18:25.799> cloud<00:18:26.799> service<00:18:27.159> that 00:18:27.539 --> 00:18:27.549 align:start position:0% public so this is a cloud service that 00:18:27.549 --> 00:18:31.799 align:start position:0% public so this is a cloud service that allows<00:18:28.029> people<00:18:28.450> to<00:18:28.690> share<00:18:29.940> files<00:18:30.940> between<00:18:31.240> one 00:18:31.799 --> 00:18:31.809 align:start position:0% allows people to share files between one 00:18:31.809 --> 00:18:34.159 align:start position:0% allows people to share files between one another<00:18:32.080> and<00:18:32.470> also<00:18:32.799> to<00:18:33.100> sync<00:18:33.520> files<00:18:33.909> between 00:18:34.159 --> 00:18:34.169 align:start position:0% another and also to sync files between 00:18:34.169 --> 00:18:38.070 align:start position:0% another and also to sync files between different<00:18:35.169> devices<00:18:35.470> so<00:18:36.390> this<00:18:37.390> is<00:18:37.600> a<00:18:37.750> fairly 00:18:38.070 --> 00:18:38.080 align:start position:0% different devices so this is a fairly 00:18:38.080 --> 00:18:40.080 align:start position:0% different devices so this is a fairly this<00:18:38.500> is<00:18:38.620> expected<00:18:39.130> to<00:18:39.279> be<00:18:39.429> a<00:18:39.460> fairly<00:18:39.820> popular 00:18:40.080 --> 00:18:40.090 align:start position:0% this is expected to be a fairly popular 00:18:40.090 --> 00:18:42.899 align:start position:0% this is expected to be a fairly popular use<00:18:40.480> case<00:18:40.630> and<00:18:41.080> what<00:18:41.950> we<00:18:42.159> hope<00:18:42.309> to<00:18:42.520> get<00:18:42.640> out<00:18:42.700> of 00:18:42.899 --> 00:18:42.909 align:start position:0% use case and what we hope to get out of 00:18:42.909 --> 00:18:48.600 align:start position:0% use case and what we hope to get out of it<00:18:43.179> is<00:18:44.789> that<00:18:45.789> we<00:18:46.240> are<00:18:46.510> going<00:18:46.779> to<00:18:46.990> see<00:18:47.289> how<00:18:48.039> swarm 00:18:48.600 --> 00:18:48.610 align:start position:0% it is that we are going to see how swarm 00:18:48.610 --> 00:18:51.539 align:start position:0% it is that we are going to see how swarm actually<00:18:49.149> performs<00:18:49.659> at<00:18:49.840> scale<00:18:50.110> so<00:18:51.039> we<00:18:51.490> are 00:18:51.539 --> 00:18:51.549 align:start position:0% actually performs at scale so we are 00:18:51.549 --> 00:18:54.990 align:start position:0% actually performs at scale so we are really<00:18:51.820> hoping<00:18:52.149> to<00:18:52.330> get<00:18:53.370> extensive<00:18:54.370> analytics 00:18:54.990 --> 00:18:55.000 align:start position:0% really hoping to get extensive analytics 00:18:55.000 --> 00:18:59.639 align:start position:0% really hoping to get extensive analytics and<00:18:55.350> user<00:18:56.350> feedback<00:18:56.649> out<00:18:57.010> of<00:18:57.159> it<00:18:57.250> and<00:18:58.649> also 00:18:59.639 --> 00:18:59.649 align:start position:0% and user feedback out of it and also 00:18:59.649 --> 00:19:02.549 align:start position:0% and user feedback out of it and also eventually<00:19:00.640> it<00:19:00.850> will<00:19:01.120> allow<00:19:01.510> us<00:19:01.809> the<00:19:02.230> swarm 00:19:02.549 --> 00:19:02.559 align:start position:0% eventually it will allow us the swarm 00:19:02.559 --> 00:19:04.799 align:start position:0% eventually it will allow us the swarm team<00:19:02.799> but<00:19:03.130> also<00:19:03.340> the<00:19:03.760> etherium<00:19:04.149> project<00:19:04.659> in 00:19:04.799 --> 00:19:04.809 align:start position:0% team but also the etherium project in 00:19:04.809 --> 00:19:08.330 align:start position:0% team but also the etherium project in general<00:19:05.039> to<00:19:06.039> sort<00:19:06.399> of<00:19:06.640> use<00:19:07.390> whatever 00:19:08.330 --> 00:19:08.340 align:start position:0% general to sort of use whatever 00:19:08.340 --> 00:19:12.500 align:start position:0% general to sort of use whatever infrastructure<00:19:09.340> we<00:19:09.490> have<00:19:09.520> built<00:19:09.970> in<00:19:10.690> order<00:19:11.140> to 00:19:12.500 --> 00:19:12.510 align:start position:0% infrastructure we have built in order to 00:19:12.510 --> 00:19:16.080 align:start position:0% infrastructure we have built in order to host<00:19:13.510> our<00:19:14.289> documentation<00:19:15.039> our<00:19:15.520> source<00:19:15.940> code 00:19:16.080 --> 00:19:16.090 align:start position:0% host our documentation our source code 00:19:16.090 --> 00:19:18.960 align:start position:0% host our documentation our source code our<00:19:16.570> web<00:19:17.169> pages<00:19:17.440> and<00:19:17.830> so<00:19:18.309> on<00:19:18.340> in<00:19:18.760> a 00:19:18.960 --> 00:19:18.970 align:start position:0% our web pages and so on in a 00:19:18.970 --> 00:19:21.930 align:start position:0% our web pages and so on in a decentralized<00:19:19.409> and<00:19:20.409> censorship<00:19:21.250> resistant 00:19:21.930 --> 00:19:21.940 align:start position:0% decentralized and censorship resistant 00:19:21.940 --> 00:19:25.340 align:start position:0% decentralized and censorship resistant fashion<00:19:22.330> and<00:19:22.659> in<00:19:23.620> particular 00:19:25.340 --> 00:19:25.350 align:start position:0% fashion and in particular 00:19:25.350 --> 00:19:28.940 align:start position:0% fashion and in particular I<00:19:25.670> was<00:19:26.670> always<00:19:26.820> baffled<00:19:27.480> by<00:19:28.110> the<00:19:28.170> fact<00:19:28.740> that 00:19:28.940 --> 00:19:28.950 align:start position:0% I was always baffled by the fact that 00:19:28.950 --> 00:19:31.670 align:start position:0% I was always baffled by the fact that little<00:19:29.910> store<00:19:30.120> waltz<00:19:30.480> has<00:19:30.750> given<00:19:31.290> us<00:19:31.440> a 00:19:31.670 --> 00:19:31.680 align:start position:0% little store waltz has given us a 00:19:31.680 --> 00:19:33.650 align:start position:0% little store waltz has given us a wonderful<00:19:32.300> distributed<00:19:33.300> source<00:19:33.570> control 00:19:33.650 --> 00:19:33.660 align:start position:0% wonderful distributed source control 00:19:33.660 --> 00:19:37.160 align:start position:0% wonderful distributed source control system<00:19:34.380> get<00:19:34.620> and<00:19:34.860> then<00:19:35.640> everybody<00:19:36.600> started 00:19:37.160 --> 00:19:37.170 align:start position:0% system get and then everybody started 00:19:37.170 --> 00:19:39.350 align:start position:0% system get and then everybody started using<00:19:37.410> github<00:19:37.830> which<00:19:38.490> is<00:19:38.670> a<00:19:38.700> centralized 00:19:39.350 --> 00:19:39.360 align:start position:0% using github which is a centralized 00:19:39.360 --> 00:19:41.480 align:start position:0% using github which is a centralized service<00:19:39.750> it's<00:19:40.020> a<00:19:40.140> great<00:19:40.320> service<00:19:40.740> very<00:19:41.310> happy 00:19:41.480 --> 00:19:41.490 align:start position:0% service it's a great service very happy 00:19:41.490 --> 00:19:46.510 align:start position:0% service it's a great service very happy with<00:19:41.730> it<00:19:41.880> but<00:19:42.920> but<00:19:43.920> it's<00:19:44.100> centralized<00:19:44.580> and 00:19:46.510 --> 00:19:46.520 align:start position:0% with it but but it's centralized and 00:19:46.520 --> 00:19:51.790 align:start position:0% with it but but it's centralized and there's<00:19:47.520> already<00:19:47.880> work<00:19:48.570> going<00:19:49.020> on<00:19:49.670> for<00:19:50.670> a 00:19:51.790 --> 00:19:51.800 align:start position:0% there's already work going on for a 00:19:51.800 --> 00:19:56.150 align:start position:0% there's already work going on for a module<00:19:52.800> for<00:19:53.130> get<00:19:53.450> on<00:19:54.450> top<00:19:54.690> of<00:19:54.810> swarm<00:19:55.160> Alex 00:19:56.150 --> 00:19:56.160 align:start position:0% module for get on top of swarm Alex 00:19:56.160 --> 00:19:58.940 align:start position:0% module for get on top of swarm Alex barracks<00:19:56.460> RC<00:19:56.790> is<00:19:56.850> working<00:19:57.180> on<00:19:57.330> it<00:19:57.950> so 00:19:58.940 --> 00:19:58.950 align:start position:0% barracks RC is working on it so 00:19:58.950 --> 00:20:01.280 align:start position:0% barracks RC is working on it so hopefully<00:19:59.580> in<00:20:00.330> the<00:20:00.570> not<00:20:00.690> too<00:20:00.900> distant<00:20:00.930> future 00:20:01.280 --> 00:20:01.290 align:start position:0% hopefully in the not too distant future 00:20:01.290 --> 00:20:04.660 align:start position:0% hopefully in the not too distant future we're<00:20:02.280> going<00:20:02.550> to<00:20:02.820> be<00:20:02.940> able<00:20:03.090> to<00:20:03.510> host<00:20:03.750> all<00:20:04.140> the 00:20:04.660 --> 00:20:04.670 align:start position:0% we're going to be able to host all the 00:20:04.670 --> 00:20:09.410 align:start position:0% we're going to be able to host all the sources<00:20:05.670> of<00:20:06.920> aetherium<00:20:07.920> on<00:20:08.100> swarm<00:20:08.580> and<00:20:08.880> have 00:20:09.410 --> 00:20:09.420 align:start position:0% sources of aetherium on swarm and have 00:20:09.420 --> 00:20:12.590 align:start position:0% sources of aetherium on swarm and have the<00:20:09.780> development<00:20:10.700> repository<00:20:11.700> basically<00:20:12.300> be 00:20:12.590 --> 00:20:12.600 align:start position:0% the development repository basically be 00:20:12.600 --> 00:20:18.080 align:start position:0% the development repository basically be stored<00:20:12.990> in<00:20:13.500> a<00:20:13.920> distributed<00:20:14.550> fashion<00:20:17.090> the 00:20:18.080 --> 00:20:18.090 align:start position:0% stored in a distributed fashion the 00:20:18.090 --> 00:20:20.870 align:start position:0% stored in a distributed fashion the first<00:20:18.360> thing<00:20:18.630> that<00:20:18.840> we<00:20:19.020> did<00:20:19.230> you<00:20:20.190> know<00:20:20.430> for 00:20:20.870 --> 00:20:20.880 align:start position:0% first thing that we did you know for 00:20:20.880 --> 00:20:25.970 align:start position:0% first thing that we did you know for this<00:20:21.170> application<00:20:22.170> was<00:20:22.950> a<00:20:23.310> GUI<00:20:24.060> based<00:20:24.980> file 00:20:25.970 --> 00:20:25.980 align:start position:0% this application was a GUI based file 00:20:25.980 --> 00:20:32.860 align:start position:0% this application was a GUI based file manager<00:20:26.460> it<00:20:27.120> was<00:20:29.090> released<00:20:30.090> last<00:20:30.660> September 00:20:32.860 --> 00:20:32.870 align:start position:0% manager it was released last September 00:20:32.870 --> 00:20:38.330 align:start position:0% manager it was released last September it's<00:20:33.870> over<00:20:34.140> a<00:20:34.170> year<00:20:34.380> ago<00:20:36.050> it<00:20:37.050> is<00:20:37.140> itself<00:20:38.010> a 00:20:38.330 --> 00:20:38.340 align:start position:0% it's over a year ago it is itself a 00:20:38.340 --> 00:20:41.180 align:start position:0% it's over a year ago it is itself a swarm<00:20:38.820> hosted<00:20:39.890> web-based 00:20:41.180 --> 00:20:41.190 align:start position:0% swarm hosted web-based 00:20:41.190 --> 00:20:43.730 align:start position:0% swarm hosted web-based distributed<00:20:41.880> application<00:20:42.540> and<00:20:42.810> it<00:20:43.410> allows 00:20:43.730 --> 00:20:43.740 align:start position:0% distributed application and it allows 00:20:43.740 --> 00:20:46.850 align:start position:0% distributed application and it allows people<00:20:44.100> to<00:20:44.370> manage<00:20:45.000> folders<00:20:45.390> and<00:20:45.810> files<00:20:46.080> in<00:20:46.590> a 00:20:46.850 --> 00:20:46.860 align:start position:0% people to manage folders and files in a 00:20:46.860 --> 00:20:52.300 align:start position:0% people to manage folders and files in a very<00:20:47.430> familiar<00:20:48.060> and<00:20:49.100> intuitive<00:20:50.100> fashion 00:20:52.300 --> 00:20:52.310 align:start position:0% very familiar and intuitive fashion 00:20:52.310 --> 00:20:56.210 align:start position:0% very familiar and intuitive fashion it<00:20:53.310> also<00:20:53.610> has<00:20:54.290> pluggable<00:20:55.290> pre<00:20:55.500> viewers<00:20:55.890> for 00:20:56.210 --> 00:20:56.220 align:start position:0% it also has pluggable pre viewers for 00:20:56.220 --> 00:20:58.490 align:start position:0% it also has pluggable pre viewers for various<00:20:56.580> types<00:20:56.850> of<00:20:57.030> content<00:20:57.480> so<00:20:57.840> you<00:20:57.930> can<00:20:58.230> view 00:20:58.490 --> 00:20:58.500 align:start position:0% various types of content so you can view 00:20:58.500 --> 00:21:03.470 align:start position:0% various types of content so you can view images<00:20:58.880> movies<00:20:59.880> and<00:21:00.980> later<00:21:01.980> perhaps<00:21:02.400> PDF<00:21:03.090> and 00:21:03.470 --> 00:21:03.480 align:start position:0% images movies and later perhaps PDF and 00:21:03.480 --> 00:21:07.040 align:start position:0% images movies and later perhaps PDF and whatever<00:21:03.870> people<00:21:04.380> can<00:21:04.530> think<00:21:04.680> about<00:21:06.050> so 00:21:07.040 --> 00:21:07.050 align:start position:0% whatever people can think about so 00:21:07.050 --> 00:21:08.420 align:start position:0% whatever people can think about so that's<00:21:07.290> the<00:21:07.590> first<00:21:07.860> thing<00:21:07.950> that<00:21:08.070> we<00:21:08.340> have 00:21:08.420 --> 00:21:08.430 align:start position:0% that's the first thing that we have 00:21:08.430 --> 00:21:14.840 align:start position:0% that's the first thing that we have built<00:21:09.950> then<00:21:11.120> Rahul<00:21:12.120> Mohammed<00:21:12.540> has<00:21:13.050> in<00:21:14.010> this 00:21:14.840 --> 00:21:14.850 align:start position:0% built then Rahul Mohammed has in this 00:21:14.850 --> 00:21:17.870 align:start position:0% built then Rahul Mohammed has in this summer<00:21:15.180> released<00:21:15.840> a<00:21:16.140> fuse<00:21:16.740> module<00:21:17.160> which 00:21:17.870 --> 00:21:17.880 align:start position:0% summer released a fuse module which 00:21:17.880 --> 00:21:21.340 align:start position:0% summer released a fuse module which means<00:21:18.210> that<00:21:18.990> you<00:21:19.590> can<00:21:19.800> actually<00:21:20.430> mount<00:21:20.700> a 00:21:21.340 --> 00:21:21.350 align:start position:0% means that you can actually mount a 00:21:21.350 --> 00:21:26.360 align:start position:0% means that you can actually mount a swarm<00:21:22.350> volume<00:21:23.070> as<00:21:23.690> a<00:21:24.690> directory<00:21:25.530> into<00:21:26.190> your 00:21:26.360 --> 00:21:26.370 align:start position:0% swarm volume as a directory into your 00:21:26.370 --> 00:21:28.940 align:start position:0% swarm volume as a directory into your file<00:21:26.580> system<00:21:27.090> if<00:21:27.570> you're<00:21:27.870> using<00:21:28.140> a<00:21:28.560> POSIX 00:21:28.940 --> 00:21:28.950 align:start position:0% file system if you're using a POSIX 00:21:28.950 --> 00:21:31.040 align:start position:0% file system if you're using a POSIX compatible<00:21:29.550> file<00:21:29.730> system<00:21:30.180> so<00:21:30.360> it<00:21:30.480> works<00:21:30.750> on 00:21:31.040 --> 00:21:31.050 align:start position:0% compatible file system so it works on 00:21:31.050 --> 00:21:36.820 align:start position:0% compatible file system so it works on linux<00:21:31.500> and<00:21:31.650> mac<00:21:31.740> know<00:21:32.670> in<00:21:32.850> the<00:21:32.970> support<00:21:33.450> yet 00:21:36.820 --> 00:21:36.830 align:start position:0% 00:21:36.830 --> 00:21:41.649 align:start position:0% it<00:21:37.830> already<00:21:38.399> has<00:21:38.970> read<00:21:39.299> and<00:21:39.510> write<00:21:39.720> support 00:21:41.649 --> 00:21:41.659 align:start position:0% it already has read and write support 00:21:41.659 --> 00:21:45.460 align:start position:0% it already has read and write support you<00:21:42.659> can<00:21:42.870> already<00:21:43.289> mount<00:21:43.740> Els<00:21:44.669> registered 00:21:45.460 --> 00:21:45.470 align:start position:0% you can already mount Els registered 00:21:45.470 --> 00:21:49.190 align:start position:0% you can already mount Els registered volumes<00:21:46.470> and<00:21:46.940> there's<00:21:47.940> one<00:21:48.299> thing<00:21:48.600> missing 00:21:49.190 --> 00:21:49.200 align:start position:0% volumes and there's one thing missing 00:21:49.200 --> 00:21:53.180 align:start position:0% volumes and there's one thing missing which<00:21:50.039> is<00:21:50.340> sort<00:21:51.210> of<00:21:51.360> a<00:21:51.480> safe<00:21:51.840> -<00:21:52.110> ENS<00:21:52.590> kind<00:21:53.010> of 00:21:53.180 --> 00:21:53.190 align:start position:0% which is sort of a safe - ENS kind of 00:21:53.190 --> 00:21:55.370 align:start position:0% which is sort of a safe - ENS kind of functionality<00:21:54.000> where<00:21:54.450> you<00:21:54.600> can<00:21:54.809> update<00:21:55.080> the 00:21:55.370 --> 00:21:55.380 align:start position:0% functionality where you can update the 00:21:55.380 --> 00:21:58.669 align:start position:0% functionality where you can update the Els<00:21:56.220> resolver<00:21:57.000> with<00:21:57.600> the<00:21:57.809> new<00:21:57.960> content 00:21:58.669 --> 00:21:58.679 align:start position:0% Els resolver with the new content 00:21:58.679 --> 00:22:02.659 align:start position:0% Els resolver with the new content after<00:21:59.309> you<00:21:59.490> have<00:21:59.640> modified<00:22:00.200> the<00:22:01.490> content<00:22:02.490> of 00:22:02.659 --> 00:22:02.669 align:start position:0% after you have modified the content of 00:22:02.669 --> 00:22:06.220 align:start position:0% after you have modified the content of the<00:22:03.350> swarm<00:22:04.350> volume<00:22:04.769> that<00:22:04.980> you<00:22:05.159> have<00:22:05.279> mounted 00:22:06.220 --> 00:22:06.230 align:start position:0% the swarm volume that you have mounted 00:22:06.230 --> 00:22:10.090 align:start position:0% the swarm volume that you have mounted so<00:22:07.230> this<00:22:07.470> is<00:22:07.649> also<00:22:08.039> available<00:22:08.789> for<00:22:09.510> download 00:22:10.090 --> 00:22:10.100 align:start position:0% so this is also available for download 00:22:10.100 --> 00:22:12.980 align:start position:0% so this is also available for download and<00:22:11.100> you<00:22:11.220> can<00:22:11.429> you're<00:22:11.909> also<00:22:12.059> very<00:22:12.240> welcome<00:22:12.840> to 00:22:12.980 --> 00:22:12.990 align:start position:0% and you can you're also very welcome to 00:22:12.990 --> 00:22:18.169 align:start position:0% and you can you're also very welcome to play<00:22:13.139> with<00:22:13.289> it<00:22:15.679> this<00:22:16.679> is<00:22:17.010> a<00:22:17.100> big<00:22:17.429> one<00:22:17.639> so 00:22:18.169 --> 00:22:18.179 align:start position:0% play with it this is a big one so 00:22:18.179 --> 00:22:20.600 align:start position:0% play with it this is a big one so currently<00:22:18.690> all<00:22:19.110> swarm<00:22:19.740> content<00:22:20.399> is 00:22:20.600 --> 00:22:20.610 align:start position:0% currently all swarm content is 00:22:20.610 --> 00:22:23.180 align:start position:0% currently all swarm content is unencrypted<00:22:21.510> and<00:22:21.659> in<00:22:22.049> the<00:22:22.200> open<00:22:22.470> and<00:22:22.649> this<00:22:23.010> of 00:22:23.180 --> 00:22:23.190 align:start position:0% unencrypted and in the open and this of 00:22:23.190 --> 00:22:25.340 align:start position:0% unencrypted and in the open and this of course<00:22:23.220> makes<00:22:23.789> it<00:22:24.059> completely<00:22:24.539> unsuited<00:22:25.320> for 00:22:25.340 --> 00:22:25.350 align:start position:0% course makes it completely unsuited for 00:22:25.350 --> 00:22:29.539 align:start position:0% course makes it completely unsuited for any<00:22:25.799> serious<00:22:26.190> use<00:22:26.779> but<00:22:27.779> and<00:22:28.409> this<00:22:28.649> is<00:22:28.710> what<00:22:29.309> I 00:22:29.539 --> 00:22:29.549 align:start position:0% any serious use but and this is what I 00:22:29.549 --> 00:22:33.340 align:start position:0% any serious use but and this is what I am<00:22:29.820> currently<00:22:30.120> working<00:22:30.360> on<00:22:31.250> privacy<00:22:32.250> and 00:22:33.340 --> 00:22:33.350 align:start position:0% am currently working on privacy and 00:22:33.350 --> 00:22:38.779 align:start position:0% am currently working on privacy and security<00:22:34.370> encryption<00:22:36.860> so<00:22:37.860> here<00:22:38.220> you<00:22:38.370> need<00:22:38.580> to 00:22:38.779 --> 00:22:38.789 align:start position:0% security encryption so here you need to 00:22:38.789 --> 00:22:40.879 align:start position:0% security encryption so here you need to understand<00:22:39.419> that<00:22:39.600> this<00:22:39.960> fundamentally 00:22:40.879 --> 00:22:40.889 align:start position:0% understand that this fundamentally 00:22:40.889 --> 00:22:46.159 align:start position:0% understand that this fundamentally differs<00:22:41.340> from<00:22:42.179> a<00:22:44.149> traditional<00:22:45.149> cloud<00:22:45.600> hosted 00:22:46.159 --> 00:22:46.169 align:start position:0% differs from a traditional cloud hosted 00:22:46.169 --> 00:22:48.230 align:start position:0% differs from a traditional cloud hosted server<00:22:46.440> client<00:22:46.789> application<00:22:47.789> because 00:22:48.230 --> 00:22:48.240 align:start position:0% server client application because 00:22:48.240 --> 00:22:51.740 align:start position:0% server client application because obviously<00:22:48.990> you<00:22:49.409> cannot<00:22:49.830> force<00:22:50.279> people<00:22:50.750> like 00:22:51.740 --> 00:22:51.750 align:start position:0% obviously you cannot force people like 00:22:51.750 --> 00:22:54.230 align:start position:0% obviously you cannot force people like not<00:22:52.019> to<00:22:52.289> share<00:22:52.590> certain<00:22:53.070> information<00:22:53.399> so 00:22:54.230 --> 00:22:54.240 align:start position:0% not to share certain information so 00:22:54.240 --> 00:22:56.389 align:start position:0% not to share certain information so access<00:22:54.720> control<00:22:55.200> needs<00:22:55.529> to<00:22:55.769> be<00:22:55.919> implemented 00:22:56.389 --> 00:22:56.399 align:start position:0% access control needs to be implemented 00:22:56.399 --> 00:22:58.190 align:start position:0% access control needs to be implemented in<00:22:56.820> a<00:22:57.090> different<00:22:57.570> way 00:22:58.190 --> 00:22:58.200 align:start position:0% in a different way 00:22:58.200 --> 00:23:03.350 align:start position:0% in a different way so<00:22:59.659> essentially<00:23:00.659> right<00:23:01.289> control<00:23:01.860> so<00:23:02.850> who<00:23:03.090> is 00:23:03.350 --> 00:23:03.360 align:start position:0% so essentially right control so who is 00:23:03.360 --> 00:23:06.190 align:start position:0% so essentially right control so who is allowed<00:23:04.110> to<00:23:04.169> modify<00:23:04.950> something<00:23:05.580> is 00:23:06.190 --> 00:23:06.200 align:start position:0% allowed to modify something is 00:23:06.200 --> 00:23:11.600 align:start position:0% allowed to modify something is equivalent<00:23:07.200> to<00:23:08.120> the<00:23:09.590> permission<00:23:10.590> to<00:23:11.070> update 00:23:11.600 --> 00:23:11.610 align:start position:0% equivalent to the permission to update 00:23:11.610 --> 00:23:15.500 align:start position:0% equivalent to the permission to update the<00:23:12.029> root<00:23:12.210> hash<00:23:12.590> in<00:23:13.590> ENS<00:23:14.250> so<00:23:14.820> it<00:23:15.029> is<00:23:15.210> something 00:23:15.500 --> 00:23:15.510 align:start position:0% the root hash in ENS so it is something 00:23:15.510 --> 00:23:18.350 align:start position:0% the root hash in ENS so it is something that<00:23:15.779> is<00:23:16.409> controlled<00:23:17.039> by<00:23:17.159> a<00:23:17.279> smart<00:23:17.639> contract<00:23:18.090> a 00:23:18.350 --> 00:23:18.360 align:start position:0% that is controlled by a smart contract a 00:23:18.360 --> 00:23:20.930 align:start position:0% that is controlled by a smart contract a smart<00:23:18.870> contract<00:23:19.110> is<00:23:19.649> what<00:23:20.100> takes<00:23:20.370> care<00:23:20.730> of 00:23:20.930 --> 00:23:20.940 align:start position:0% smart contract is what takes care of 00:23:20.940 --> 00:23:24.320 align:start position:0% smart contract is what takes care of write<00:23:21.570> permissions<00:23:22.309> read<00:23:23.309> permissions<00:23:24.029> are 00:23:24.320 --> 00:23:24.330 align:start position:0% write permissions read permissions are 00:23:24.330 --> 00:23:28.759 align:start position:0% write permissions read permissions are even<00:23:25.260> trickier<00:23:25.679> because<00:23:27.320> you<00:23:28.320> know<00:23:28.500> where 00:23:28.759 --> 00:23:28.769 align:start position:0% even trickier because you know where 00:23:28.769 --> 00:23:31.460 align:start position:0% even trickier because you know where swarm<00:23:29.250> content<00:23:29.730> ends<00:23:30.059> up<00:23:30.299> it<00:23:30.659> cannot<00:23:31.260> be 00:23:31.460 --> 00:23:31.470 align:start position:0% swarm content ends up it cannot be 00:23:31.470 --> 00:23:35.120 align:start position:0% swarm content ends up it cannot be controlled<00:23:32.309> it<00:23:32.970> just<00:23:33.470> goes<00:23:34.470> all<00:23:34.740> over<00:23:34.769> in<00:23:35.070> the 00:23:35.120 --> 00:23:35.130 align:start position:0% controlled it just goes all over in the 00:23:35.130 --> 00:23:38.480 align:start position:0% controlled it just goes all over in the network<00:23:35.490> you<00:23:35.760> cannot<00:23:36.600> hide<00:23:37.470> swarm<00:23:38.010> content 00:23:38.480 --> 00:23:38.490 align:start position:0% network you cannot hide swarm content 00:23:38.490 --> 00:23:41.269 align:start position:0% network you cannot hide swarm content you<00:23:38.820> can<00:23:38.970> only<00:23:39.149> encrypt<00:23:39.539> it<00:23:39.809> so<00:23:40.649> what<00:23:40.889> you<00:23:41.039> can 00:23:41.269 --> 00:23:41.279 align:start position:0% you can only encrypt it so what you can 00:23:41.279 --> 00:23:45.250 align:start position:0% you can only encrypt it so what you can do<00:23:41.519> is<00:23:41.820> you<00:23:42.720> can<00:23:42.990> encrypt<00:23:43.919> swarm<00:23:44.370> content<00:23:44.850> and 00:23:45.250 --> 00:23:45.260 align:start position:0% do is you can encrypt swarm content and 00:23:45.260 --> 00:23:47.590 align:start position:0% do is you can encrypt swarm content and read<00:23:46.260> permission 00:23:47.590 --> 00:23:47.600 align:start position:0% read permission 00:23:47.600 --> 00:23:52.270 align:start position:0% read permission means<00:23:48.110> the<00:23:48.679> ability<00:23:48.799> to<00:23:49.280> decrypt<00:23:50.030> it<00:23:50.240> and<00:23:51.280> if 00:23:52.270 --> 00:23:52.280 align:start position:0% means the ability to decrypt it and if 00:23:52.280 --> 00:23:55.180 align:start position:0% means the ability to decrypt it and if you<00:23:52.580> want<00:23:52.850> to<00:23:53.059> have<00:23:53.270> access<00:23:53.600> control<00:23:54.230> lists<00:23:54.650> so 00:23:55.180 --> 00:23:55.190 align:start position:0% you want to have access control lists so 00:23:55.190 --> 00:24:00.039 align:start position:0% you want to have access control lists so you<00:23:55.220> want<00:23:55.640> a<00:23:55.850> large<00:23:56.600> piece<00:23:56.960> of<00:23:57.309> data<00:23:58.309> to<00:23:59.049> be 00:24:00.039 --> 00:24:00.049 align:start position:0% you want a large piece of data to be 00:24:00.049 --> 00:24:02.890 align:start position:0% you want a large piece of data to be readable<00:24:00.500> for<00:24:01.280> some<00:24:01.549> parties<00:24:02.000> but<00:24:02.299> not<00:24:02.539> others 00:24:02.890 --> 00:24:02.900 align:start position:0% readable for some parties but not others 00:24:02.900 --> 00:24:05.980 align:start position:0% readable for some parties but not others then<00:24:03.559> what<00:24:03.830> you<00:24:03.950> can<00:24:04.160> do<00:24:04.429> is<00:24:04.730> you<00:24:05.360> can<00:24:05.510> take<00:24:05.809> the 00:24:05.980 --> 00:24:05.990 align:start position:0% then what you can do is you can take the 00:24:05.990 --> 00:24:08.919 align:start position:0% then what you can do is you can take the symmetric<00:24:06.530> key<00:24:06.770> with<00:24:07.370> which<00:24:07.400> this<00:24:08.000> data<00:24:08.600> is 00:24:08.919 --> 00:24:08.929 align:start position:0% symmetric key with which this data is 00:24:08.929 --> 00:24:12.310 align:start position:0% symmetric key with which this data is encrypted<00:24:09.230> and<00:24:10.000> encrypt<00:24:11.000> that<00:24:11.360> symmetric<00:24:11.840> key 00:24:12.310 --> 00:24:12.320 align:start position:0% encrypted and encrypt that symmetric key 00:24:12.320 --> 00:24:16.330 align:start position:0% encrypted and encrypt that symmetric key with<00:24:12.950> a<00:24:13.220> number<00:24:14.030> of<00:24:14.240> public<00:24:14.809> keys<00:24:14.990> of<00:24:15.340> the 00:24:16.330 --> 00:24:16.340 align:start position:0% with a number of public keys of the 00:24:16.340 --> 00:24:18.760 align:start position:0% with a number of public keys of the parties<00:24:16.760> that<00:24:16.789> have<00:24:17.270> reaper<00:24:17.630> mission<00:24:17.990> and<00:24:18.230> use 00:24:18.760 --> 00:24:18.770 align:start position:0% parties that have reaper mission and use 00:24:18.770 --> 00:24:24.360 align:start position:0% parties that have reaper mission and use that<00:24:19.070> as<00:24:19.460> a<00:24:19.789> access<00:24:20.210> control<00:24:20.600> list<00:24:21.070> and<00:24:22.690> this 00:24:24.360 --> 00:24:24.370 align:start position:0% that as a access control list and this 00:24:24.370 --> 00:24:27.880 align:start position:0% that as a access control list and this obviously<00:24:25.370> affects<00:24:25.880> how<00:24:26.620> content<00:24:27.620> can<00:24:27.860> be 00:24:27.880 --> 00:24:27.890 align:start position:0% obviously affects how content can be 00:24:27.890 --> 00:24:28.750 align:start position:0% obviously affects how content can be referenced 00:24:28.750 --> 00:24:28.760 align:start position:0% referenced 00:24:28.760 --> 00:24:31.899 align:start position:0% referenced so<00:24:29.150> in<00:24:29.360> unencrypted<00:24:30.049> Swarm<00:24:30.830> the<00:24:31.400> standard 00:24:31.899 --> 00:24:31.909 align:start position:0% so in unencrypted Swarm the standard 00:24:31.909 --> 00:24:34.779 align:start position:0% so in unencrypted Swarm the standard reference<00:24:32.120> to<00:24:32.750> content<00:24:33.380> is<00:24:33.559> the<00:24:34.190> swarm<00:24:34.520> hash 00:24:34.779 --> 00:24:34.789 align:start position:0% reference to content is the swarm hash 00:24:34.789 --> 00:24:38.919 align:start position:0% reference to content is the swarm hash of<00:24:35.120> the<00:24:35.390> manifest<00:24:35.809> in<00:24:37.150> encrypted<00:24:38.150> swarm<00:24:38.480> in 00:24:38.919 --> 00:24:38.929 align:start position:0% of the manifest in encrypted swarm in 00:24:38.929 --> 00:24:41.740 align:start position:0% of the manifest in encrypted swarm in addition<00:24:39.500> to<00:24:39.679> the<00:24:39.830> root<00:24:40.100> hash<00:24:40.340> you<00:24:40.970> also<00:24:41.210> need 00:24:41.740 --> 00:24:41.750 align:start position:0% addition to the root hash you also need 00:24:41.750 --> 00:24:46.720 align:start position:0% addition to the root hash you also need the<00:24:42.289> decryption<00:24:42.770> key<00:24:43.039> of<00:24:43.490> the<00:24:44.419> route<00:24:45.549> how<00:24:46.549> this 00:24:46.720 --> 00:24:46.730 align:start position:0% the decryption key of the route how this 00:24:46.730 --> 00:24:52.090 align:start position:0% the decryption key of the route how this encryption<00:24:47.299> works<00:24:47.890> so<00:24:48.890> as<00:24:50.260> Aaron<00:24:51.260> has<00:24:51.500> already 00:24:52.090 --> 00:24:52.100 align:start position:0% encryption works so as Aaron has already 00:24:52.100 --> 00:24:54.640 align:start position:0% encryption works so as Aaron has already told<00:24:52.340> before<00:24:52.820> me<00:24:53.000> swarm<00:24:53.720> chunks<00:24:54.260> of<00:24:54.440> content 00:24:54.640 --> 00:24:54.650 align:start position:0% told before me swarm chunks of content 00:24:54.650 --> 00:24:56.740 align:start position:0% told before me swarm chunks of content into<00:24:55.100> small<00:24:55.460> pieces<00:24:55.669> and<00:24:55.909> organizes<00:24:56.720> them 00:24:56.740 --> 00:24:56.750 align:start position:0% into small pieces and organizes them 00:24:56.750 --> 00:25:00.549 align:start position:0% into small pieces and organizes them into<00:24:56.929> a<00:24:57.260> miracle<00:24:57.620> tree<00:24:57.799> and<00:24:58.390> in<00:24:59.390> swarm<00:24:59.900> every 00:25:00.549 --> 00:25:00.559 align:start position:0% into a miracle tree and in swarm every 00:25:00.559 --> 00:25:02.620 align:start position:0% into a miracle tree and in swarm every chunk<00:25:00.950> is<00:25:01.190> going<00:25:01.460> to<00:25:01.669> be<00:25:01.760> encrypted<00:25:02.120> with<00:25:02.419> a 00:25:02.620 --> 00:25:02.630 align:start position:0% chunk is going to be encrypted with a 00:25:02.630 --> 00:25:08.470 align:start position:0% chunk is going to be encrypted with a unique<00:25:03.220> key<00:25:04.220> and<00:25:04.929> each<00:25:05.929> edge<00:25:07.030> in<00:25:08.030> the 00:25:08.470 --> 00:25:08.480 align:start position:0% unique key and each edge in the 00:25:08.480 --> 00:25:11.380 align:start position:0% unique key and each edge in the encrypted<00:25:09.320> Merkle<00:25:09.770> tree<00:25:09.980> contains<00:25:10.700> not<00:25:11.059> only 00:25:11.380 --> 00:25:11.390 align:start position:0% encrypted Merkle tree contains not only 00:25:11.390 --> 00:25:14.080 align:start position:0% encrypted Merkle tree contains not only the<00:25:11.510> hash<00:25:11.750> but<00:25:12.200> also<00:25:12.409> the<00:25:12.830> decryption<00:25:13.220> key<00:25:13.429> for 00:25:14.080 --> 00:25:14.090 align:start position:0% the hash but also the decryption key for 00:25:14.090 --> 00:25:17.409 align:start position:0% the hash but also the decryption key for that<00:25:14.120> particular<00:25:14.870> chunk<00:25:15.730> which<00:25:16.730> means<00:25:17.030> that 00:25:17.409 --> 00:25:17.419 align:start position:0% that particular chunk which means that 00:25:17.419 --> 00:25:21.909 align:start position:0% that particular chunk which means that if<00:25:17.659> you<00:25:17.840> reveal<00:25:18.350> a<00:25:19.030> key<00:25:20.030> at<00:25:20.780> some<00:25:21.200> point<00:25:21.530> in 00:25:21.909 --> 00:25:21.919 align:start position:0% if you reveal a key at some point in 00:25:21.919 --> 00:25:25.060 align:start position:0% if you reveal a key at some point in this<00:25:22.250> tree<00:25:22.580> so<00:25:22.940> one<00:25:23.450> of<00:25:23.480> the<00:25:23.840> Merkle<00:25:24.830> trees 00:25:25.060 --> 00:25:25.070 align:start position:0% this tree so one of the Merkle trees 00:25:25.070 --> 00:25:28.270 align:start position:0% this tree so one of the Merkle trees nodes<00:25:25.460> key<00:25:25.940> gets<00:25:26.210> compromised<00:25:26.809> it<00:25:27.559> means<00:25:27.919> that 00:25:28.270 --> 00:25:28.280 align:start position:0% nodes key gets compromised it means that 00:25:28.280 --> 00:25:32.520 align:start position:0% nodes key gets compromised it means that only<00:25:28.490> the<00:25:28.850> subtree<00:25:29.390> under<00:25:29.929> it<00:25:30.340> is<00:25:31.340> compromised 00:25:32.520 --> 00:25:32.530 align:start position:0% only the subtree under it is compromised 00:25:32.530 --> 00:25:35.950 align:start position:0% only the subtree under it is compromised which<00:25:33.530> is<00:25:33.830> kind<00:25:34.460> of<00:25:34.580> a<00:25:34.669> stopgap<00:25:34.970> measure<00:25:35.210> for 00:25:35.950 --> 00:25:35.960 align:start position:0% which is kind of a stopgap measure for 00:25:35.960 --> 00:25:39.100 align:start position:0% which is kind of a stopgap measure for catastrophic<00:25:36.530> failures<00:25:37.630> against<00:25:38.630> losing 00:25:39.100 --> 00:25:39.110 align:start position:0% catastrophic failures against losing 00:25:39.110 --> 00:25:42.610 align:start position:0% catastrophic failures against losing keys<00:25:39.350> and<00:25:39.650> also<00:25:40.640> it<00:25:41.030> allows<00:25:41.620> different 00:25:42.610 --> 00:25:42.620 align:start position:0% keys and also it allows different 00:25:42.620 --> 00:25:47.409 align:start position:0% keys and also it allows different directories<00:25:43.610> to<00:25:43.909> be<00:25:44.059> shared<00:25:44.500> among<00:25:46.419> different 00:25:47.409 --> 00:25:47.419 align:start position:0% directories to be shared among different 00:25:47.419 --> 00:25:52.740 align:start position:0% directories to be shared among different parties<00:25:48.169> as<00:25:48.470> a<00:25:49.280> sub<00:25:49.730> directory<00:25:50.330> of<00:25:51.190> different 00:25:52.740 --> 00:25:52.750 align:start position:0% parties as a sub directory of different 00:25:52.750 --> 00:25:58.450 align:start position:0% parties as a sub directory of different directory<00:25:53.750> structures<00:25:54.940> and<00:25:57.040> so<00:25:58.040> I<00:25:58.070> would<00:25:58.309> like 00:25:58.450 --> 00:25:58.460 align:start position:0% directory structures and so I would like 00:25:58.460 --> 00:26:00.720 align:start position:0% directory structures and so I would like to<00:25:58.520> invite<00:25:59.330> Aaron<00:26:00.049> back<00:26:00.260> to 00:26:00.720 --> 00:26:00.730 align:start position:0% to invite Aaron back to 00:26:00.730 --> 00:26:03.390 align:start position:0% to invite Aaron back to talk<00:26:00.880> about<00:26:01.090> the<00:26:01.630> network<00:26:02.500> testing<00:26:02.980> framework 00:26:03.390 --> 00:26:03.400 align:start position:0% talk about the network testing framework 00:26:03.400 --> 00:26:11.340 align:start position:0% talk about the network testing framework that<00:26:03.580> we<00:26:03.760> have<00:26:03.790> built<00:26:09.630> yeah<00:26:10.630> hello<00:26:10.900> again 00:26:11.340 --> 00:26:11.350 align:start position:0% that we have built yeah hello again 00:26:11.350 --> 00:26:13.680 align:start position:0% that we have built yeah hello again I'm<00:26:11.590> filling<00:26:12.190> in<00:26:12.280> for<00:26:12.309> Victor<00:26:12.880> our<00:26:13.210> team<00:26:13.480> lead 00:26:13.680 --> 00:26:13.690 align:start position:0% I'm filling in for Victor our team lead 00:26:13.690 --> 00:26:15.690 align:start position:0% I'm filling in for Victor our team lead who<00:26:14.110> is<00:26:14.230> here<00:26:14.500> but<00:26:14.620> not<00:26:14.919> able<00:26:15.100> to<00:26:15.190> speak<00:26:15.520> right 00:26:15.690 --> 00:26:15.700 align:start position:0% who is here but not able to speak right 00:26:15.700 --> 00:26:18.090 align:start position:0% who is here but not able to speak right now<00:26:15.880> so<00:26:16.750> I<00:26:16.780> want<00:26:16.960> to<00:26:17.020> talk<00:26:17.260> a<00:26:17.470> little<00:26:17.620> bit<00:26:17.770> about 00:26:18.090 --> 00:26:18.100 align:start position:0% now so I want to talk a little bit about 00:26:18.100 --> 00:26:20.970 align:start position:0% now so I want to talk a little bit about the<00:26:18.669> network<00:26:19.030> testing<00:26:19.540> well<00:26:19.990> the<00:26:20.140> full<00:26:20.620> title 00:26:20.970 --> 00:26:20.980 align:start position:0% the network testing well the full title 00:26:20.980 --> 00:26:22.620 align:start position:0% the network testing well the full title is<00:26:21.010> the<00:26:21.160> network<00:26:21.490> simulation<00:26:22.090> and<00:26:22.240> testing 00:26:22.620 --> 00:26:22.630 align:start position:0% is the network simulation and testing 00:26:22.630 --> 00:26:26.280 align:start position:0% is the network simulation and testing framework<00:26:23.110> and<00:26:23.940> I<00:26:24.940> have<00:26:25.450> to<00:26:25.690> admit<00:26:25.990> at<00:26:26.169> this 00:26:26.280 --> 00:26:26.290 align:start position:0% framework and I have to admit at this 00:26:26.290 --> 00:26:28.260 align:start position:0% framework and I have to admit at this point<00:26:26.500> I'm<00:26:26.830> not<00:26:26.890> the<00:26:27.250> right<00:26:27.429> person<00:26:27.700> to<00:26:28.000> talk 00:26:28.260 --> 00:26:28.270 align:start position:0% point I'm not the right person to talk 00:26:28.270 --> 00:26:30.539 align:start position:0% point I'm not the right person to talk you<00:26:28.450> through<00:26:28.600> this<00:26:28.780> diagram<00:26:29.049> in<00:26:29.380> detail<00:26:29.740> but 00:26:30.539 --> 00:26:30.549 align:start position:0% you through this diagram in detail but 00:26:30.549 --> 00:26:32.070 align:start position:0% you through this diagram in detail but that<00:26:30.700> means<00:26:30.850> I'm<00:26:31.150> the<00:26:31.330> right<00:26:31.450> person<00:26:31.660> to<00:26:31.870> give 00:26:32.070 --> 00:26:32.080 align:start position:0% that means I'm the right person to give 00:26:32.080 --> 00:26:33.840 align:start position:0% that means I'm the right person to give you<00:26:32.200> an<00:26:32.290> easy-to-understand<00:26:33.250> high-level 00:26:33.840 --> 00:26:33.850 align:start position:0% you an easy-to-understand high-level 00:26:33.850 --> 00:26:36.630 align:start position:0% you an easy-to-understand high-level overview<00:26:34.000> of<00:26:34.419> what's<00:26:34.690> going<00:26:34.780> on<00:26:35.400> so<00:26:36.400> I'm<00:26:36.460> gonna 00:26:36.630 --> 00:26:36.640 align:start position:0% overview of what's going on so I'm gonna 00:26:36.640 --> 00:26:38.820 align:start position:0% overview of what's going on so I'm gonna start<00:26:36.970> from<00:26:37.390> the<00:26:37.450> right<00:26:37.690> and<00:26:37.960> talk<00:26:38.500> my<00:26:38.710> way 00:26:38.820 --> 00:26:38.830 align:start position:0% start from the right and talk my way 00:26:38.830 --> 00:26:41.580 align:start position:0% start from the right and talk my way over<00:26:39.070> to<00:26:39.190> the<00:26:39.309> left<00:26:39.390> in<00:26:40.390> the<00:26:40.929> top<00:26:40.960> right<00:26:41.380> what 00:26:41.580 --> 00:26:41.590 align:start position:0% over to the left in the top right what 00:26:41.590 --> 00:26:45.049 align:start position:0% over to the left in the top right what you<00:26:41.710> see<00:26:41.860> is<00:26:41.980> our<00:26:42.130> network<00:26:42.340> visualizer<00:26:43.470> it<00:26:44.470> is 00:26:45.049 --> 00:26:45.059 align:start position:0% you see is our network visualizer it is 00:26:45.059 --> 00:26:49.980 align:start position:0% you see is our network visualizer it is it's<00:26:46.059> a<00:26:46.360> web-based<00:26:47.230> or<00:26:48.100> a<00:26:48.160> browser-based<00:26:48.990> view 00:26:49.980 --> 00:26:49.990 align:start position:0% it's a web-based or a browser-based view 00:26:49.990 --> 00:26:52.919 align:start position:0% it's a web-based or a browser-based view of<00:26:50.200> a<00:26:50.530> swarm<00:26:50.770> network<00:26:51.250> so<00:26:51.669> all<00:26:52.179> those<00:26:52.480> dots<00:26:52.750> in 00:26:52.919 --> 00:26:52.929 align:start position:0% of a swarm network so all those dots in 00:26:52.929 --> 00:26:54.390 align:start position:0% of a swarm network so all those dots in there<00:26:53.110> would<00:26:53.260> be<00:26:53.290> swarm<00:26:53.799> nodes<00:26:54.010> and 00:26:54.390 --> 00:26:54.400 align:start position:0% there would be swarm nodes and 00:26:54.400 --> 00:26:57.330 align:start position:0% there would be swarm nodes and connections<00:26:54.820> between<00:26:55.120> swarm<00:26:55.630> nodes<00:26:56.340> this 00:26:57.330 --> 00:26:57.340 align:start position:0% connections between swarm nodes this 00:26:57.340 --> 00:26:59.490 align:start position:0% connections between swarm nodes this interface<00:26:57.790> allows<00:26:58.059> us<00:26:58.210> to<00:26:58.360> query<00:26:58.690> any<00:26:59.080> swarm 00:26:59.490 --> 00:26:59.500 align:start position:0% interface allows us to query any swarm 00:26:59.500 --> 00:27:01.530 align:start position:0% interface allows us to query any swarm node<00:26:59.679> what's<00:27:00.040> its<00:27:00.220> current<00:27:00.520> status<00:27:00.970> stored 00:27:01.530 --> 00:27:01.540 align:start position:0% node what's its current status stored 00:27:01.540 --> 00:27:03.720 align:start position:0% node what's its current status stored chunks<00:27:01.990> every<00:27:02.350> connection<00:27:02.740> the<00:27:03.429> swap 00:27:03.720 --> 00:27:03.730 align:start position:0% chunks every connection the swap 00:27:03.730 --> 00:27:05.730 align:start position:0% chunks every connection the swap connection<00:27:04.330> was<00:27:04.510> to<00:27:04.720> swap<00:27:04.990> balance<00:27:05.380> what<00:27:05.620> are 00:27:05.730 --> 00:27:05.740 align:start position:0% connection was to swap balance what are 00:27:05.740 --> 00:27:08.610 align:start position:0% connection was to swap balance what are the<00:27:05.830> payments<00:27:06.309> and<00:27:06.490> so<00:27:06.760> on<00:27:07.140> so<00:27:08.140> it<00:27:08.230> gives<00:27:08.380> us<00:27:08.500> a 00:27:08.610 --> 00:27:08.620 align:start position:0% the payments and so on so it gives us a 00:27:08.620 --> 00:27:12.659 align:start position:0% the payments and so on so it gives us a very<00:27:10.380> great<00:27:11.380> overview<00:27:11.710> of<00:27:11.950> a<00:27:12.040> swarm<00:27:12.280> network 00:27:12.659 --> 00:27:12.669 align:start position:0% very great overview of a swarm network 00:27:12.669 --> 00:27:14.370 align:start position:0% very great overview of a swarm network of<00:27:12.790> a<00:27:12.850> test<00:27:13.059> network<00:27:13.390> to<00:27:13.570> see<00:27:13.750> what's<00:27:13.929> going<00:27:14.200> on 00:27:14.370 --> 00:27:14.380 align:start position:0% of a test network to see what's going on 00:27:14.380 --> 00:27:18.900 align:start position:0% of a test network to see what's going on and<00:27:15.900> it<00:27:16.900> also<00:27:17.110> allows<00:27:17.410> us<00:27:17.440> to<00:27:17.620> input<00:27:17.980> changes 00:27:18.900 --> 00:27:18.910 align:start position:0% and it also allows us to input changes 00:27:18.910 --> 00:27:20.880 align:start position:0% and it also allows us to input changes we<00:27:19.059> can<00:27:19.210> click<00:27:19.660> on<00:27:19.840> a<00:27:19.870> node<00:27:20.049> and<00:27:20.290> tell<00:27:20.470> it<00:27:20.590> to<00:27:20.770> go 00:27:20.880 --> 00:27:20.890 align:start position:0% we can click on a node and tell it to go 00:27:20.890 --> 00:27:23.070 align:start position:0% we can click on a node and tell it to go offline<00:27:21.280> tell<00:27:21.730> it<00:27:21.850> to<00:27:22.000> initiate<00:27:22.570> a<00:27:22.780> data 00:27:23.070 --> 00:27:23.080 align:start position:0% offline tell it to initiate a data 00:27:23.080 --> 00:27:25.860 align:start position:0% offline tell it to initiate a data retrieval<00:27:23.559> whatever<00:27:24.070> we<00:27:24.190> want<00:27:24.720> that<00:27:25.720> would 00:27:25.860 --> 00:27:25.870 align:start position:0% retrieval whatever we want that would 00:27:25.870 --> 00:27:28.289 align:start position:0% retrieval whatever we want that would take<00:27:26.049> us<00:27:26.200> into<00:27:26.380> events<00:27:26.919> so<00:27:27.490> these<00:27:27.730> events<00:27:28.120> we 00:27:28.289 --> 00:27:28.299 align:start position:0% take us into events so these events we 00:27:28.299 --> 00:27:30.930 align:start position:0% take us into events so these events we can<00:27:28.450> fill<00:27:28.809> in<00:27:28.960> to<00:27:29.080> network<00:27:29.440> so<00:27:30.160> simulating 00:27:30.930 --> 00:27:30.940 align:start position:0% can fill in to network so simulating 00:27:30.940 --> 00:27:33.390 align:start position:0% can fill in to network so simulating activity<00:27:31.510> on<00:27:31.780> the<00:27:32.200> network<00:27:32.290> telling<00:27:32.890> nodes<00:27:33.100> to 00:27:33.390 --> 00:27:33.400 align:start position:0% activity on the network telling nodes to 00:27:33.400 --> 00:27:35.370 align:start position:0% activity on the network telling nodes to drop<00:27:33.700> offline<00:27:34.030> come<00:27:34.299> online<00:27:34.600> do<00:27:35.049> various 00:27:35.370 --> 00:27:35.380 align:start position:0% drop offline come online do various 00:27:35.380 --> 00:27:39.539 align:start position:0% drop offline come online do various things<00:27:35.470> and<00:27:37.200> these<00:27:38.200> events<00:27:38.410> get<00:27:38.770> packaged 00:27:39.539 --> 00:27:39.549 align:start position:0% things and these events get packaged 00:27:39.549 --> 00:27:42.690 align:start position:0% things and these events get packaged into<00:27:39.790> whole<00:27:40.090> scenarios<00:27:40.750> so<00:27:40.960> we<00:27:41.080> can<00:27:41.260> write<00:27:41.830> a 00:27:42.690 --> 00:27:42.700 align:start position:0% into whole scenarios so we can write a 00:27:42.700 --> 00:27:44.789 align:start position:0% into whole scenarios so we can write a network<00:27:43.299> scenario<00:27:43.480> of<00:27:43.929> nodes<00:27:44.169> coming<00:27:44.590> online 00:27:44.789 --> 00:27:44.799 align:start position:0% network scenario of nodes coming online 00:27:44.799 --> 00:27:47.220 align:start position:0% network scenario of nodes coming online sharing<00:27:45.549> content<00:27:46.120> downloading<00:27:47.080> content 00:27:47.220 --> 00:27:47.230 align:start position:0% sharing content downloading content 00:27:47.230 --> 00:27:49.289 align:start position:0% sharing content downloading content paying<00:27:47.710> each<00:27:47.830> other<00:27:48.070> refusing<00:27:48.700> to<00:27:48.820> page<00:27:49.030> other 00:27:49.289 --> 00:27:49.299 align:start position:0% paying each other refusing to page other 00:27:49.299 --> 00:27:51.150 align:start position:0% paying each other refusing to page other whatever<00:27:49.600> we<00:27:49.809> want<00:27:49.990> and<00:27:50.140> we<00:27:50.260> can<00:27:50.380> observe<00:27:50.650> how 00:27:51.150 --> 00:27:51.160 align:start position:0% whatever we want and we can observe how 00:27:51.160 --> 00:27:54.600 align:start position:0% whatever we want and we can observe how the<00:27:51.220> network<00:27:52.890> behaves<00:27:53.890> like<00:27:54.130> what<00:27:54.309> did<00:27:54.429> what 00:27:54.600 --> 00:27:54.610 align:start position:0% the network behaves like what did what 00:27:54.610 --> 00:27:56.100 align:start position:0% the network behaves like what did what the<00:27:54.820> network<00:27:55.179> does<00:27:55.360> what<00:27:55.570> the<00:27:55.690> emergent 00:27:56.100 --> 00:27:56.110 align:start position:0% the network does what the emergent 00:27:56.110 --> 00:27:59.340 align:start position:0% the network does what the emergent behavior<00:27:56.650> is<00:27:57.299> in<00:27:58.299> the<00:27:58.480> backend<00:27:58.660> which<00:27:59.169> is 00:27:59.340 --> 00:27:59.350 align:start position:0% behavior is in the backend which is 00:27:59.350 --> 00:28:00.480 align:start position:0% behavior is in the backend which is further<00:27:59.740> towards<00:28:00.070> left 00:28:00.480 --> 00:28:00.490 align:start position:0% further towards left 00:28:00.490 --> 00:28:03.240 align:start position:0% further towards left we<00:28:01.419> can<00:28:01.540> either<00:28:01.660> simulate<00:28:02.230> the<00:28:02.710> swarm<00:28:03.040> nodes 00:28:03.240 --> 00:28:03.250 align:start position:0% we can either simulate the swarm nodes 00:28:03.250 --> 00:28:06.510 align:start position:0% we can either simulate the swarm nodes in<00:28:03.669> process<00:28:04.179> very<00:28:04.720> quickly<00:28:04.990> and<00:28:05.380> or<00:28:06.070> we<00:28:06.340> could 00:28:06.510 --> 00:28:06.520 align:start position:0% in process very quickly and or we could 00:28:06.520 --> 00:28:09.980 align:start position:0% in process very quickly and or we could launch<00:28:06.880> a<00:28:07.059> bunch<00:28:07.240> of<00:28:07.360> Dockers<00:28:07.780> with<00:28:08.350> various 00:28:09.980 --> 00:28:09.990 align:start position:0% launch a bunch of Dockers with various 00:28:09.990 --> 00:28:12.360 align:start position:0% launch a bunch of Dockers with various so<00:28:10.990> we<00:28:11.110> could<00:28:11.260> host<00:28:11.440> a<00:28:11.590> cluster<00:28:11.980> of<00:28:12.100> swarm 00:28:12.360 --> 00:28:12.370 align:start position:0% so we could host a cluster of swarm 00:28:12.370 --> 00:28:13.420 align:start position:0% so we could host a cluster of swarm nodes 00:28:13.420 --> 00:28:13.430 align:start position:0% nodes 00:28:13.430 --> 00:28:16.240 align:start position:0% nodes and<00:28:13.580> and<00:28:14.270> actually<00:28:14.720> run<00:28:15.080> them<00:28:15.440> in<00:28:15.559> full<00:28:15.800> or<00:28:16.040> we 00:28:16.240 --> 00:28:16.250 align:start position:0% and and actually run them in full or we 00:28:16.250 --> 00:28:18.370 align:start position:0% and and actually run them in full or we can<00:28:16.370> simulate<00:28:16.730> them<00:28:17.120> so<00:28:17.660> these<00:28:17.840> scenarios<00:28:18.110> are 00:28:18.370 --> 00:28:18.380 align:start position:0% can simulate them so these scenarios are 00:28:18.380 --> 00:28:20.590 align:start position:0% can simulate them so these scenarios are portable<00:28:18.920> so<00:28:19.250> separating<00:28:19.880> out<00:28:20.000> what<00:28:20.330> we<00:28:20.420> want 00:28:20.590 --> 00:28:20.600 align:start position:0% portable so separating out what we want 00:28:20.600 --> 00:28:22.690 align:start position:0% portable so separating out what we want to<00:28:20.690> happen<00:28:20.809> on<00:28:21.050> the<00:28:21.140> network<00:28:21.470> and<00:28:21.740> the<00:28:22.400> level 00:28:22.690 --> 00:28:22.700 align:start position:0% to happen on the network and the level 00:28:22.700 --> 00:28:24.100 align:start position:0% to happen on the network and the level of<00:28:22.790> simulation<00:28:23.390> whether<00:28:23.570> we<00:28:23.690> just<00:28:23.870> want<00:28:24.020> to 00:28:24.100 --> 00:28:24.110 align:start position:0% of simulation whether we just want to 00:28:24.110 --> 00:28:26.560 align:start position:0% of simulation whether we just want to simulate<00:28:24.530> the<00:28:24.740> process<00:28:24.920> or<00:28:25.280> actually<00:28:25.790> you 00:28:26.560 --> 00:28:26.570 align:start position:0% simulate the process or actually you 00:28:26.570 --> 00:28:28.510 align:start position:0% simulate the process or actually you know<00:28:26.660> there's<00:28:27.500> also<00:28:27.650> also<00:28:28.190> one<00:28:28.309> to<00:28:28.400> rather 00:28:28.510 --> 00:28:28.520 align:start position:0% know there's also also one to rather 00:28:28.520 --> 00:28:30.400 align:start position:0% know there's also also one to rather like<00:28:28.700> a<00:28:28.730> back-end<00:28:29.270> to<00:28:29.570> our<00:28:29.720> cluster<00:28:30.170> where<00:28:30.320> we 00:28:30.400 --> 00:28:30.410 align:start position:0% like a back-end to our cluster where we 00:28:30.410 --> 00:28:31.780 align:start position:0% like a back-end to our cluster where we can<00:28:30.590> have<00:28:30.770> our<00:28:30.800> whole<00:28:31.070> cluster<00:28:31.430> of<00:28:31.460> machines 00:28:31.780 --> 00:28:31.790 align:start position:0% can have our whole cluster of machines 00:28:31.790 --> 00:28:33.100 align:start position:0% can have our whole cluster of machines running<00:28:32.059> a<00:28:32.210> whole<00:28:32.360> bunch<00:28:32.540> of<00:28:32.660> swarm<00:28:32.930> nodes 00:28:33.100 --> 00:28:33.110 align:start position:0% running a whole bunch of swarm nodes 00:28:33.110 --> 00:28:35.640 align:start position:0% running a whole bunch of swarm nodes doing<00:28:33.970> running<00:28:34.970> through<00:28:35.210> these<00:28:35.360> scenarios 00:28:35.640 --> 00:28:35.650 align:start position:0% doing running through these scenarios 00:28:35.650 --> 00:28:39.250 align:start position:0% doing running through these scenarios and<00:28:36.650> the<00:28:37.640> reason<00:28:37.970> why<00:28:38.660> we're<00:28:38.930> so<00:28:39.050> excited 00:28:39.250 --> 00:28:39.260 align:start position:0% and the reason why we're so excited 00:28:39.260 --> 00:28:41.410 align:start position:0% and the reason why we're so excited about<00:28:39.410> this<00:28:39.590> or<00:28:39.770> why<00:28:39.890> we're<00:28:40.100> developing<00:28:40.550> this 00:28:41.410 --> 00:28:41.420 align:start position:0% about this or why we're developing this 00:28:41.420 --> 00:28:45.190 align:start position:0% about this or why we're developing this is<00:28:41.740> to<00:28:42.740> test<00:28:43.600> emergent<00:28:44.600> behavior<00:28:44.990> of<00:28:45.080> the 00:28:45.190 --> 00:28:45.200 align:start position:0% is to test emergent behavior of the 00:28:45.200 --> 00:28:46.560 align:start position:0% is to test emergent behavior of the network<00:28:45.320> so<00:28:45.710> normally<00:28:46.040> when<00:28:46.160> we<00:28:46.340> talk<00:28:46.490> about 00:28:46.560 --> 00:28:46.570 align:start position:0% network so normally when we talk about 00:28:46.570 --> 00:28:49.060 align:start position:0% network so normally when we talk about testing<00:28:47.570> a<00:28:47.660> client<00:28:48.080> you're<00:28:48.559> running<00:28:48.800> code 00:28:49.060 --> 00:28:49.070 align:start position:0% testing a client you're running code 00:28:49.070 --> 00:28:50.710 align:start position:0% testing a client you're running code tests<00:28:49.400> to<00:28:49.580> see<00:28:49.790> whether<00:28:49.970> a<00:28:50.120> swarm<00:28:50.540> node 00:28:50.710 --> 00:28:50.720 align:start position:0% tests to see whether a swarm node 00:28:50.720 --> 00:28:53.919 align:start position:0% tests to see whether a swarm node behaves<00:28:51.440> the<00:28:51.679> way<00:28:51.710> you<00:28:51.890> expected<00:28:52.670> to<00:28:52.910> but<00:28:53.720> a 00:28:53.919 --> 00:28:53.929 align:start position:0% behaves the way you expected to but a 00:28:53.929 --> 00:28:56.880 align:start position:0% behaves the way you expected to but a lot<00:28:53.960> of<00:28:54.200> the<00:28:54.520> intricacies<00:28:55.520> the<00:28:55.820> subtleties<00:28:56.360> of 00:28:56.880 --> 00:28:56.890 align:start position:0% lot of the intricacies the subtleties of 00:28:56.890 --> 00:29:01.600 align:start position:0% lot of the intricacies the subtleties of swarm<00:28:58.660> arise<00:28:59.660> from<00:28:59.929> the<00:29:00.080> interaction<00:29:00.890> of<00:29:01.040> the 00:29:01.600 --> 00:29:01.610 align:start position:0% swarm arise from the interaction of the 00:29:01.610 --> 00:29:03.220 align:start position:0% swarm arise from the interaction of the different<00:29:02.000> nodes<00:29:02.210> in<00:29:02.540> the<00:29:02.720> network<00:29:03.050> the 00:29:03.220 --> 00:29:03.230 align:start position:0% different nodes in the network the 00:29:03.230 --> 00:29:05.440 align:start position:0% different nodes in the network the emergent<00:29:03.679> behavior<00:29:04.220> like<00:29:04.700> how<00:29:04.970> data<00:29:05.300> is 00:29:05.440 --> 00:29:05.450 align:start position:0% emergent behavior like how data is 00:29:05.450 --> 00:29:08.049 align:start position:0% emergent behavior like how data is distributed<00:29:06.320> one<00:29:06.800> node<00:29:07.010> requests<00:29:07.580> data<00:29:07.760> the 00:29:08.049 --> 00:29:08.059 align:start position:0% distributed one node requests data the 00:29:08.059 --> 00:29:10.150 align:start position:0% distributed one node requests data the other<00:29:08.210> ones<00:29:08.450> forward<00:29:09.320> the<00:29:09.470> request<00:29:09.830> the<00:29:10.010> data 00:29:10.150 --> 00:29:10.160 align:start position:0% other ones forward the request the data 00:29:10.160 --> 00:29:12.310 align:start position:0% other ones forward the request the data has<00:29:10.400> found<00:29:10.640> handed<00:29:11.150> back<00:29:11.360> all<00:29:11.720> the<00:29:11.900> nodes<00:29:12.080> have 00:29:12.310 --> 00:29:12.320 align:start position:0% has found handed back all the nodes have 00:29:12.320 --> 00:29:14.410 align:start position:0% has found handed back all the nodes have to<00:29:12.470> do<00:29:12.559> the<00:29:12.679> accounting<00:29:13.070> and<00:29:13.250> if<00:29:14.090> you<00:29:14.179> want<00:29:14.330> to 00:29:14.410 --> 00:29:14.420 align:start position:0% to do the accounting and if you want to 00:29:14.420 --> 00:29:17.560 align:start position:0% to do the accounting and if you want to see<00:29:14.929> how<00:29:15.140> this<00:29:15.410> network<00:29:16.190> behaves<00:29:16.880> we<00:29:17.360> really 00:29:17.560 --> 00:29:17.570 align:start position:0% see how this network behaves we really 00:29:17.570 --> 00:29:19.270 align:start position:0% see how this network behaves we really have<00:29:17.690> to<00:29:17.840> simulate<00:29:18.050> a<00:29:18.290> full<00:29:18.530> network<00:29:18.920> and<00:29:19.070> test 00:29:19.270 --> 00:29:19.280 align:start position:0% have to simulate a full network and test 00:29:19.280 --> 00:29:21.490 align:start position:0% have to simulate a full network and test the<00:29:19.460> network<00:29:19.610> so<00:29:20.390> this<00:29:20.510> testing<00:29:21.080> framework 00:29:21.490 --> 00:29:21.500 align:start position:0% the network so this testing framework 00:29:21.500 --> 00:29:24.820 align:start position:0% the network so this testing framework allows<00:29:21.860> us<00:29:22.070> to<00:29:22.250> do<00:29:22.809> protocol<00:29:23.809> testing<00:29:24.380> you 00:29:24.820 --> 00:29:24.830 align:start position:0% allows us to do protocol testing you 00:29:24.830 --> 00:29:27.780 align:start position:0% allows us to do protocol testing you write<00:29:25.040> a<00:29:25.070> scenario<00:29:25.660> what<00:29:26.660> you<00:29:26.840> want<00:29:27.080> to<00:29:27.530> happen 00:29:27.780 --> 00:29:27.790 align:start position:0% write a scenario what you want to happen 00:29:27.790 --> 00:29:31.450 align:start position:0% write a scenario what you want to happen one<00:29:28.790> node<00:29:29.030> uploads<00:29:29.570> content<00:29:30.110> and<00:29:30.350> then<00:29:31.160> what 00:29:31.450 --> 00:29:31.460 align:start position:0% one node uploads content and then what 00:29:31.460 --> 00:29:33.100 align:start position:0% one node uploads content and then what you<00:29:31.580> expect<00:29:31.940> to<00:29:32.000> happen<00:29:32.090> you<00:29:32.390> expect<00:29:32.750> the<00:29:32.900> data 00:29:33.100 --> 00:29:33.110 align:start position:0% you expect to happen you expect the data 00:29:33.110 --> 00:29:35.110 align:start position:0% you expect to happen you expect the data to<00:29:33.440> be<00:29:33.559> handed<00:29:34.040> from<00:29:34.100> node<00:29:34.370> to<00:29:34.520> node<00:29:34.550> stored 00:29:35.110 --> 00:29:35.120 align:start position:0% to be handed from node to node stored 00:29:35.120 --> 00:29:37.600 align:start position:0% to be handed from node to node stored here<00:29:35.600> you<00:29:36.470> know<00:29:36.590> and<00:29:36.830> all<00:29:37.040> that<00:29:37.070> kind<00:29:37.429> of<00:29:37.490> stuff 00:29:37.600 --> 00:29:37.610 align:start position:0% here you know and all that kind of stuff 00:29:37.610 --> 00:29:39.580 align:start position:0% here you know and all that kind of stuff so<00:29:37.940> it's<00:29:38.510> more<00:29:38.720> than<00:29:38.840> just<00:29:38.900> testing<00:29:39.470> an 00:29:39.580 --> 00:29:39.590 align:start position:0% so it's more than just testing an 00:29:39.590 --> 00:29:41.440 align:start position:0% so it's more than just testing an individual<00:29:40.130> node<00:29:40.280> is<00:29:40.490> testing<00:29:40.910> that<00:29:41.030> all<00:29:41.300> the 00:29:41.440 --> 00:29:41.450 align:start position:0% individual node is testing that all the 00:29:41.450 --> 00:29:44.560 align:start position:0% individual node is testing that all the parts<00:29:41.750> work<00:29:41.929> together<00:29:42.140> and<00:29:43.270> this<00:29:44.270> framework 00:29:44.560 --> 00:29:44.570 align:start position:0% parts work together and this framework 00:29:44.570 --> 00:29:46.990 align:start position:0% parts work together and this framework is<00:29:45.470> not<00:29:45.679> is<00:29:45.860> about<00:29:46.070> you<00:29:46.340> know<00:29:46.429> it<00:29:46.580> allows<00:29:46.820> you 00:29:46.990 --> 00:29:47.000 align:start position:0% is not is about you know it allows you 00:29:47.000 --> 00:29:50.380 align:start position:0% is not is about you know it allows you to<00:29:47.120> test<00:29:47.300> PSS<00:29:48.040> storage<00:29:49.040> retrieval<00:29:49.220> the<00:29:49.580> entire 00:29:50.380 --> 00:29:50.390 align:start position:0% to test PSS storage retrieval the entire 00:29:50.390 --> 00:29:53.169 align:start position:0% to test PSS storage retrieval the entire you<00:29:51.320> know<00:29:51.410> the<00:29:51.500> whole<00:29:51.620> package<00:29:51.950> and<00:29:52.179> that's 00:29:53.169 --> 00:29:53.179 align:start position:0% you know the whole package and that's 00:29:53.179 --> 00:29:55.900 align:start position:0% you know the whole package and that's all<00:29:53.330> I'm<00:29:53.450> gonna<00:29:53.570> say<00:29:53.840> about<00:29:53.960> this<00:29:54.260> today<00:29:54.910> will 00:29:55.900 --> 00:29:55.910 align:start position:0% all I'm gonna say about this today will 00:29:55.910 --> 00:29:57.730 align:start position:0% all I'm gonna say about this today will be<00:29:56.030> give<00:29:56.600> more<00:29:56.840> about<00:29:57.020> all<00:29:57.230> of<00:29:57.350> this<00:29:57.470> on 00:29:57.730 --> 00:29:57.740 align:start position:0% be give more about all of this on 00:29:57.740 --> 00:30:02.380 align:start position:0% be give more about all of this on Saturday<00:29:59.260> so<00:30:00.580> upcoming<00:30:01.580> stuff<00:30:01.850> what's<00:30:02.120> on<00:30:02.270> the 00:30:02.380 --> 00:30:02.390 align:start position:0% Saturday so upcoming stuff what's on the 00:30:02.390 --> 00:30:05.560 align:start position:0% Saturday so upcoming stuff what's on the roadmap<00:30:02.570> so<00:30:03.970> one<00:30:04.970> of<00:30:05.090> the<00:30:05.179> things<00:30:05.390> that's 00:30:05.560 --> 00:30:05.570 align:start position:0% roadmap so one of the things that's 00:30:05.570 --> 00:30:08.290 align:start position:0% roadmap so one of the things that's changing<00:30:06.140> is<00:30:06.380> the<00:30:06.640> hashing<00:30:07.640> algorithm 00:30:08.290 --> 00:30:08.300 align:start position:0% changing is the hashing algorithm 00:30:08.300 --> 00:30:10.570 align:start position:0% changing is the hashing algorithm earlier<00:30:08.960> I<00:30:09.020> said<00:30:09.170> when<00:30:09.559> you<00:30:09.650> have<00:30:09.800> a<00:30:09.830> chunk<00:30:10.340> of 00:30:10.570 --> 00:30:10.580 align:start position:0% earlier I said when you have a chunk of 00:30:10.580 --> 00:30:12.430 align:start position:0% earlier I said when you have a chunk of data<00:30:10.760> you<00:30:11.210> hash<00:30:11.450> it<00:30:11.690> and<00:30:11.870> that<00:30:11.990> is<00:30:12.110> its<00:30:12.260> ID 00:30:12.430 --> 00:30:12.440 align:start position:0% data you hash it and that is its ID 00:30:12.440 --> 00:30:15.130 align:start position:0% data you hash it and that is its ID we're<00:30:13.400> changing<00:30:13.850> that<00:30:13.970> to<00:30:14.390> actually<00:30:14.690> make<00:30:14.840> the 00:30:15.130 --> 00:30:15.140 align:start position:0% we're changing that to actually make the 00:30:15.140 --> 00:30:18.610 align:start position:0% we're changing that to actually make the ID<00:30:15.740> of<00:30:15.980> a<00:30:16.070> chunk<00:30:16.340> be<00:30:16.550> the<00:30:16.820> merkel<00:30:17.510> root<00:30:17.929> of<00:30:18.140> a 00:30:18.610 --> 00:30:18.620 align:start position:0% ID of a chunk be the merkel root of a 00:30:18.620 --> 00:30:20.410 align:start position:0% ID of a chunk be the merkel root of a Merkel<00:30:19.160> tree<00:30:19.460> that<00:30:19.730> we<00:30:19.850> make<00:30:20.000> out<00:30:20.210> of<00:30:20.330> the 00:30:20.410 --> 00:30:20.420 align:start position:0% Merkel tree that we make out of the 00:30:20.420 --> 00:30:22.810 align:start position:0% Merkel tree that we make out of the chunks<00:30:20.780> out<00:30:20.929> of<00:30:21.260> the<00:30:21.440> 32<00:30:21.950> byte<00:30:22.130> segments<00:30:22.730> and 00:30:22.810 --> 00:30:22.820 align:start position:0% chunks out of the 32 byte segments and 00:30:22.820 --> 00:30:26.110 align:start position:0% chunks out of the 32 byte segments and this<00:30:22.970> allows<00:30:24.340> far<00:30:25.340> more<00:30:25.490> fine-grained 00:30:26.110 --> 00:30:26.120 align:start position:0% this allows far more fine-grained 00:30:26.120 --> 00:30:26.860 align:start position:0% this allows far more fine-grained resolution 00:30:26.860 --> 00:30:26.870 align:start position:0% resolution 00:30:26.870 --> 00:30:29.230 align:start position:0% resolution proof<00:30:27.140> of<00:30:27.410> inclusion<00:30:27.950> and<00:30:28.340> and<00:30:28.880> proofs<00:30:29.150> of 00:30:29.230 --> 00:30:29.240 align:start position:0% proof of inclusion and and proofs of 00:30:29.240 --> 00:30:32.740 align:start position:0% proof of inclusion and and proofs of custody<00:30:29.660> this<00:30:29.780> is<00:30:29.960> where<00:30:30.260> that<00:30:30.860> comes<00:30:30.920> in<00:30:31.750> then 00:30:32.740 --> 00:30:32.750 align:start position:0% custody this is where that comes in then 00:30:32.750 --> 00:30:34.780 align:start position:0% custody this is where that comes in then the<00:30:33.260> syncing<00:30:33.650> protocol<00:30:34.100> has<00:30:34.280> been<00:30:34.430> rewritten 00:30:34.780 --> 00:30:34.790 align:start position:0% the syncing protocol has been rewritten 00:30:34.790 --> 00:30:37.270 align:start position:0% the syncing protocol has been rewritten the<00:30:35.390> syncing<00:30:35.809> protocol<00:30:36.350> is<00:30:36.559> the<00:30:36.860> protocol 00:30:37.270 --> 00:30:37.280 align:start position:0% the syncing protocol is the protocol 00:30:37.280 --> 00:30:40.180 align:start position:0% the syncing protocol is the protocol that<00:30:37.420> governs<00:30:38.420> how<00:30:38.780> swarm<00:30:39.260> nodes<00:30:39.500> share<00:30:39.920> data 00:30:40.180 --> 00:30:40.190 align:start position:0% that governs how swarm nodes share data 00:30:40.190 --> 00:30:42.010 align:start position:0% that governs how swarm nodes share data how<00:30:40.490> the<00:30:40.550> chunks<00:30:41.330> make<00:30:41.570> it<00:30:41.750> to<00:30:41.870> their 00:30:42.010 --> 00:30:42.020 align:start position:0% how the chunks make it to their 00:30:42.020 --> 00:30:44.200 align:start position:0% how the chunks make it to their destination<00:30:42.230> and<00:30:42.860> that's<00:30:43.520> the<00:30:43.760> one<00:30:43.910> that<00:30:44.059> was 00:30:44.200 --> 00:30:44.210 align:start position:0% destination and that's the one that was 00:30:44.210 --> 00:30:46.150 align:start position:0% destination and that's the one that was causing<00:30:44.510> us<00:30:44.750> the<00:30:44.960> most<00:30:45.140> headaches<00:30:45.620> in<00:30:45.920> terms 00:30:46.150 --> 00:30:46.160 align:start position:0% causing us the most headaches in terms 00:30:46.160 --> 00:30:47.890 align:start position:0% causing us the most headaches in terms of<00:30:46.280> performance<00:30:46.790> on<00:30:46.970> the<00:30:47.000> test<00:30:47.240> network<00:30:47.690> and 00:30:47.890 --> 00:30:47.900 align:start position:0% of performance on the test network and 00:30:47.900 --> 00:30:49.480 align:start position:0% of performance on the test network and why<00:30:48.020> if<00:30:48.530> you<00:30:48.680> were<00:30:48.770> playing<00:30:48.950> around<00:30:49.160> with<00:30:49.370> that 00:30:49.480 --> 00:30:49.490 align:start position:0% why if you were playing around with that 00:30:49.490 --> 00:30:51.280 align:start position:0% why if you were playing around with that you<00:30:49.580> got<00:30:49.730> so<00:30:49.940> many<00:30:50.059> four<00:30:50.750> or<00:30:50.870> four<00:30:51.050> errors 00:30:51.280 --> 00:30:51.290 align:start position:0% you got so many four or four errors 00:30:51.290 --> 00:30:54.370 align:start position:0% you got so many four or four errors where<00:30:51.590> files<00:30:51.890> weren't<00:30:52.610> found<00:30:52.790> because<00:30:53.380> the 00:30:54.370 --> 00:30:54.380 align:start position:0% where files weren't found because the 00:30:54.380 --> 00:30:56.230 align:start position:0% where files weren't found because the data<00:30:55.070> wasn't<00:30:55.340> being<00:30:55.550> passed<00:30:55.760> all<00:30:55.970> in<00:30:56.059> the<00:30:56.150> way 00:30:56.230 --> 00:30:56.240 align:start position:0% data wasn't being passed all in the way 00:30:56.240 --> 00:30:57.700 align:start position:0% data wasn't being passed all in the way it<00:30:56.300> was<00:30:56.390> supposed<00:30:56.720> to<00:30:56.780> so<00:30:57.350> that's<00:30:57.440> been 00:30:57.700 --> 00:30:57.710 align:start position:0% it was supposed to so that's been 00:30:57.710 --> 00:30:59.260 align:start position:0% it was supposed to so that's been rewritten<00:30:58.070> and<00:30:58.370> it<00:30:58.550> will<00:30:58.640> be<00:30:58.760> merged<00:30:58.970> soon 00:30:59.260 --> 00:30:59.270 align:start position:0% rewritten and it will be merged soon 00:30:59.270 --> 00:31:01.450 align:start position:0% rewritten and it will be merged soon indeed<00:31:00.020> the<00:31:00.200> entire<00:31:00.500> network<00:31:00.710> layer<00:31:01.100> and<00:31:01.370> the 00:31:01.450 --> 00:31:01.460 align:start position:0% indeed the entire network layer and the 00:31:01.460 --> 00:31:03.160 align:start position:0% indeed the entire network layer and the connection<00:31:02.059> management<00:31:02.330> has<00:31:02.600> also<00:31:02.780> been 00:31:03.160 --> 00:31:03.170 align:start position:0% connection management has also been 00:31:03.170 --> 00:31:04.960 align:start position:0% connection management has also been rewritten<00:31:03.470> and<00:31:03.740> is<00:31:03.890> ready<00:31:04.160> to<00:31:04.250> be<00:31:04.370> merged<00:31:04.670> and 00:31:04.960 --> 00:31:04.970 align:start position:0% rewritten and is ready to be merged and 00:31:04.970 --> 00:31:10.780 align:start position:0% rewritten and is ready to be merged and these<00:31:05.809> changes<00:31:06.380> are<00:31:06.550> breaking<00:31:07.550> so<00:31:09.790> that 00:31:10.780 --> 00:31:10.790 align:start position:0% these changes are breaking so that 00:31:10.790 --> 00:31:13.690 align:start position:0% these changes are breaking so that hashes<00:31:11.480> need<00:31:11.990> to<00:31:12.140> change<00:31:12.380> the<00:31:12.650> ENS<00:31:13.010> entries 00:31:13.690 --> 00:31:13.700 align:start position:0% hashes need to change the ENS entries 00:31:13.700 --> 00:31:15.610 align:start position:0% hashes need to change the ENS entries would<00:31:13.880> need<00:31:14.030> to<00:31:14.120> change<00:31:14.390> and<00:31:14.809> in<00:31:15.200> fact<00:31:15.350> we're 00:31:15.610 --> 00:31:15.620 align:start position:0% would need to change and in fact we're 00:31:15.620 --> 00:31:17.799 align:start position:0% would need to change and in fact we're gonna<00:31:15.740> have<00:31:16.100> a<00:31:16.130> complete<00:31:16.640> reset<00:31:17.179> of<00:31:17.360> the<00:31:17.540> swarm 00:31:17.799 --> 00:31:17.809 align:start position:0% gonna have a complete reset of the swarm 00:31:17.809 --> 00:31:19.870 align:start position:0% gonna have a complete reset of the swarm test<00:31:18.080> net<00:31:18.260> soon<00:31:18.530> once<00:31:19.220> these<00:31:19.429> things<00:31:19.670> are 00:31:19.870 --> 00:31:19.880 align:start position:0% test net soon once these things are 00:31:19.880 --> 00:31:21.280 align:start position:0% test net soon once these things are merged<00:31:20.090> and<00:31:20.390> then<00:31:20.510> hopefully<00:31:20.960> we'll<00:31:21.050> have<00:31:21.230> a 00:31:21.280 --> 00:31:21.290 align:start position:0% merged and then hopefully we'll have a 00:31:21.290 --> 00:31:23.140 align:start position:0% merged and then hopefully we'll have a formal<00:31:21.710> performance<00:31:21.860> test<00:31:22.429> network<00:31:22.760> to<00:31:22.940> play 00:31:23.140 --> 00:31:23.150 align:start position:0% formal performance test network to play 00:31:23.150 --> 00:31:24.280 align:start position:0% formal performance test network to play with 00:31:24.280 --> 00:31:24.290 align:start position:0% with 00:31:24.290 --> 00:31:29.049 align:start position:0% with from<00:31:24.710> then<00:31:24.860> on<00:31:27.160> yeah<00:31:28.160> so<00:31:28.429> ongoing<00:31:28.880> work 00:31:29.049 --> 00:31:29.059 align:start position:0% from then on yeah so ongoing work 00:31:29.059 --> 00:31:30.850 align:start position:0% from then on yeah so ongoing work encryption<00:31:29.660> erasure<00:31:29.900> coating<00:31:30.350> plausible 00:31:30.850 --> 00:31:30.860 align:start position:0% encryption erasure coating plausible 00:31:30.860 --> 00:31:33.850 align:start position:0% encryption erasure coating plausible deniability<00:31:31.130> that<00:31:31.730> is<00:31:31.880> Donny's<00:31:32.620> he<00:31:33.620> talked 00:31:33.850 --> 00:31:33.860 align:start position:0% deniability that is Donny's he talked 00:31:33.860 --> 00:31:35.320 align:start position:0% deniability that is Donny's he talked about<00:31:33.920> that<00:31:34.130> that's<00:31:34.309> what<00:31:34.520> he's<00:31:34.670> working<00:31:34.880> on 00:31:35.320 --> 00:31:35.330 align:start position:0% about that that's what he's working on 00:31:35.330 --> 00:31:40.780 align:start position:0% about that that's what he's working on PSS<00:31:36.400> under<00:31:37.400> active<00:31:37.700> development<00:31:37.760> and<00:31:39.790> yeah 00:31:40.780 --> 00:31:40.790 align:start position:0% PSS under active development and yeah 00:31:40.790 --> 00:31:42.430 align:start position:0% PSS under active development and yeah the<00:31:40.910> contracts<00:31:41.450> for<00:31:41.480> storage<00:31:41.900> insurance<00:31:42.290> we 00:31:42.430 --> 00:31:42.440 align:start position:0% the contracts for storage insurance we 00:31:42.440 --> 00:31:44.710 align:start position:0% the contracts for storage insurance we didn't<00:31:42.679> talk<00:31:42.800> much<00:31:42.860> about<00:31:43.070> today<00:31:43.429> but<00:31:43.720> they 00:31:44.710 --> 00:31:44.720 align:start position:0% didn't talk much about today but they 00:31:44.720 --> 00:31:46.690 align:start position:0% didn't talk much about today but they were<00:31:44.780> in<00:31:45.200> our<00:31:45.320> original<00:31:45.710> orange<00:31:45.980> papers<00:31:46.460> and 00:31:46.690 --> 00:31:46.700 align:start position:0% were in our original orange papers and 00:31:46.700 --> 00:31:49.330 align:start position:0% were in our original orange papers and they<00:31:47.000> are<00:31:47.030> being<00:31:47.870> developed<00:31:48.679> and<00:31:48.830> tested<00:31:48.980> no 00:31:49.330 --> 00:31:49.340 align:start position:0% they are being developed and tested no 00:31:49.340 --> 00:31:51.280 align:start position:0% they are being developed and tested no they<00:31:49.520> haven't<00:31:49.670> been<00:31:49.850> deployed<00:31:50.179> yet<00:31:50.360> all<00:31:51.020> we 00:31:51.280 --> 00:31:51.290 align:start position:0% they haven't been deployed yet all we 00:31:51.290 --> 00:31:55.240 align:start position:0% they haven't been deployed yet all we have<00:31:51.470> so<00:31:51.740> far<00:31:51.950> is<00:31:52.220> contract<00:31:52.850> for<00:31:54.250> for 00:31:55.240 --> 00:31:55.250 align:start position:0% have so far is contract for for 00:31:55.250 --> 00:31:57.760 align:start position:0% have so far is contract for for retrieval<00:31:55.880> and<00:31:56.090> like<00:31:56.990> the<00:31:57.260> bandwidth 00:31:57.760 --> 00:31:57.770 align:start position:0% retrieval and like the bandwidth 00:31:57.770 --> 00:31:59.320 align:start position:0% retrieval and like the bandwidth incentives<00:31:58.340> but<00:31:58.460> the<00:31:58.580> storage<00:31:58.880> incentive 00:31:59.320 --> 00:31:59.330 align:start position:0% incentives but the storage incentive 00:31:59.330 --> 00:32:01.600 align:start position:0% incentives but the storage incentive part<00:31:59.630> from<00:32:00.470> the<00:32:00.590> orange<00:32:00.950> papers<00:32:01.250> is<00:32:01.370> being 00:32:01.600 --> 00:32:01.610 align:start position:0% part from the orange papers is being 00:32:01.610 --> 00:32:04.720 align:start position:0% part from the orange papers is being developed<00:32:02.150> to<00:32:02.630> and<00:32:03.280> then<00:32:04.280> the<00:32:04.400> testing 00:32:04.720 --> 00:32:04.730 align:start position:0% developed to and then the testing 00:32:04.730 --> 00:32:06.010 align:start position:0% developed to and then the testing framework<00:32:04.910> is<00:32:05.300> undergoing<00:32:05.660> active 00:32:06.010 --> 00:32:06.020 align:start position:0% framework is undergoing active 00:32:06.020 --> 00:32:12.400 align:start position:0% framework is undergoing active development<00:32:06.620> and<00:32:10.059> then<00:32:11.059> also<00:32:11.809> on<00:32:12.140> the<00:32:12.170> roadmap 00:32:12.400 --> 00:32:12.410 align:start position:0% development and then also on the roadmap 00:32:12.410 --> 00:32:14.799 align:start position:0% development and then also on the roadmap I<00:32:12.679> want<00:32:12.830> to<00:32:12.920> highlight<00:32:13.130> a<00:32:13.460> few<00:32:13.520> things<00:32:13.850> a<00:32:14.300> light 00:32:14.799 --> 00:32:14.809 align:start position:0% I want to highlight a few things a light 00:32:14.809 --> 00:32:16.840 align:start position:0% I want to highlight a few things a light swarm<00:32:15.230> node<00:32:15.440> we've<00:32:15.679> been<00:32:15.830> contacted<00:32:16.670> by 00:32:16.840 --> 00:32:16.850 align:start position:0% swarm node we've been contacted by 00:32:16.850 --> 00:32:18.450 align:start position:0% swarm node we've been contacted by people<00:32:16.910> who<00:32:17.450> doing<00:32:17.720> mobile<00:32:17.900> development 00:32:18.450 --> 00:32:18.460 align:start position:0% people who doing mobile development 00:32:18.460 --> 00:32:21.850 align:start position:0% people who doing mobile development saying<00:32:19.460> we<00:32:20.120> cannot<00:32:20.480> assume<00:32:20.929> that<00:32:21.020> every<00:32:21.559> swarm 00:32:21.850 --> 00:32:21.860 align:start position:0% saying we cannot assume that every swarm 00:32:21.860 --> 00:32:23.680 align:start position:0% saying we cannot assume that every swarm node<00:32:22.040> will<00:32:22.309> want<00:32:22.580> to<00:32:22.640> store<00:32:23.000> a<00:32:23.030> bunch<00:32:23.330> of<00:32:23.450> data 00:32:23.680 --> 00:32:23.690 align:start position:0% node will want to store a bunch of data 00:32:23.690 --> 00:32:25.540 align:start position:0% node will want to store a bunch of data and<00:32:23.929> serve<00:32:24.140> it<00:32:24.320> and<00:32:24.500> earn<00:32:24.800> revenue<00:32:25.309> some 00:32:25.540 --> 00:32:25.550 align:start position:0% and serve it and earn revenue some 00:32:25.550 --> 00:32:27.520 align:start position:0% and serve it and earn revenue some people<00:32:25.820> just<00:32:26.000> want<00:32:26.179> to<00:32:26.330> join<00:32:26.840> the<00:32:27.020> network<00:32:27.140> and 00:32:27.520 --> 00:32:27.530 align:start position:0% people just want to join the network and 00:32:27.530 --> 00:32:29.650 align:start position:0% people just want to join the network and only<00:32:27.800> consume<00:32:28.220> very<00:32:28.550> limited<00:32:29.030> data<00:32:29.179> that<00:32:29.540> they 00:32:29.650 --> 00:32:29.660 align:start position:0% only consume very limited data that they 00:32:29.660 --> 00:32:31.690 align:start position:0% only consume very limited data that they want<00:32:29.870> you<00:32:30.620> know<00:32:30.710> if<00:32:31.130> you<00:32:31.220> have<00:32:31.309> limited 00:32:31.690 --> 00:32:31.700 align:start position:0% want you know if you have limited 00:32:31.700 --> 00:32:34.330 align:start position:0% want you know if you have limited bandwidth<00:32:32.620> so<00:32:33.620> we<00:32:33.710> talked<00:32:33.920> about<00:32:33.980> various 00:32:34.330 --> 00:32:34.340 align:start position:0% bandwidth so we talked about various 00:32:34.340 --> 00:32:36.490 align:start position:0% bandwidth so we talked about various light<00:32:34.610> modes<00:32:34.880> of<00:32:35.030> operation<00:32:35.540> nodes<00:32:36.260> without 00:32:36.490 --> 00:32:36.500 align:start position:0% light modes of operation nodes without 00:32:36.500 --> 00:32:38.350 align:start position:0% light modes of operation nodes without storage<00:32:37.190> or<00:32:37.429> nodes<00:32:37.640> without<00:32:37.820> a<00:32:38.000> lot<00:32:38.270> of 00:32:38.350 --> 00:32:38.360 align:start position:0% storage or nodes without a lot of 00:32:38.360 --> 00:32:39.800 align:start position:0% storage or nodes without a lot of bandwidth 00:32:39.800 --> 00:32:39.810 align:start position:0% bandwidth 00:32:39.810 --> 00:32:42.140 align:start position:0% bandwidth so<00:32:40.380> we've<00:32:40.710> been<00:32:40.890> developing<00:32:41.340> the<00:32:41.730> theoretical 00:32:42.140 --> 00:32:42.150 align:start position:0% so we've been developing the theoretical 00:32:42.150 --> 00:32:43.640 align:start position:0% so we've been developing the theoretical framework<00:32:42.540> how<00:32:42.720> those<00:32:42.930> four<00:32:43.230> nodes<00:32:43.440> should 00:32:43.640 --> 00:32:43.650 align:start position:0% framework how those four nodes should 00:32:43.650 --> 00:32:47.260 align:start position:0% framework how those four nodes should fit<00:32:43.800> into<00:32:43.950> the<00:32:44.160> network<00:32:44.490> and<00:32:44.660> we<00:32:45.660> intend<00:32:46.410> to 00:32:47.260 --> 00:32:47.270 align:start position:0% fit into the network and we intend to 00:32:47.270 --> 00:32:49.610 align:start position:0% fit into the network and we intend to develop<00:32:48.270> those<00:32:48.540> to<00:32:48.780> some<00:32:49.020> various<00:32:49.410> light 00:32:49.610 --> 00:32:49.620 align:start position:0% develop those to some various light 00:32:49.620 --> 00:32:51.560 align:start position:0% develop those to some various light modes<00:32:49.860> of<00:32:50.010> operation<00:32:50.490> to<00:32:51.060> make<00:32:51.180> it<00:32:51.270> easier<00:32:51.540> for 00:32:51.560 --> 00:32:51.570 align:start position:0% modes of operation to make it easier for 00:32:51.570 --> 00:32:55.280 align:start position:0% modes of operation to make it easier for mobile<00:32:51.960> science<00:32:52.320> and<00:32:52.500> other<00:32:52.620> light<00:32:52.860> lines<00:32:54.290> the 00:32:55.280 --> 00:32:55.290 align:start position:0% mobile science and other light lines the 00:32:55.290 --> 00:32:58.160 align:start position:0% mobile science and other light lines the payment<00:32:55.980> infrastructure<00:32:56.670> as<00:32:56.910> I<00:32:57.660> alluded<00:32:58.140> to 00:32:58.160 --> 00:32:58.170 align:start position:0% payment infrastructure as I alluded to 00:32:58.170 --> 00:33:00.440 align:start position:0% payment infrastructure as I alluded to earlier<00:32:58.290> is<00:32:58.770> being<00:32:59.640> developed<00:33:00.000> to<00:33:00.090> be<00:33:00.180> far 00:33:00.440 --> 00:33:00.450 align:start position:0% earlier is being developed to be far 00:33:00.450 --> 00:33:02.870 align:start position:0% earlier is being developed to be far more<00:33:00.480> generic<00:33:01.080> and<00:33:01.290> to<00:33:01.440> allow<00:33:01.680> for<00:33:02.010> four 00:33:02.870 --> 00:33:02.880 align:start position:0% more generic and to allow for four 00:33:02.880 --> 00:33:04.700 align:start position:0% more generic and to allow for four different<00:33:02.970> services<00:33:03.630> than<00:33:03.900> data<00:33:04.140> storage<00:33:04.560> and 00:33:04.700 --> 00:33:04.710 align:start position:0% different services than data storage and 00:33:04.710 --> 00:33:06.890 align:start position:0% different services than data storage and retrieval<00:33:05.180> one<00:33:06.180> of<00:33:06.300> them<00:33:06.450> being<00:33:06.660> you<00:33:06.810> know 00:33:06.890 --> 00:33:06.900 align:start position:0% retrieval one of them being you know 00:33:06.900 --> 00:33:08.540 align:start position:0% retrieval one of them being you know communications<00:33:07.500> broadcasts<00:33:08.280> and<00:33:08.430> other 00:33:08.540 --> 00:33:08.550 align:start position:0% communications broadcasts and other 00:33:08.550 --> 00:33:11.420 align:start position:0% communications broadcasts and other things<00:33:08.840> service<00:33:09.840> networks<00:33:10.260> but<00:33:11.190> they<00:33:11.280> will 00:33:11.420 --> 00:33:11.430 align:start position:0% things service networks but they will 00:33:11.430 --> 00:33:13.910 align:start position:0% things service networks but they will talk<00:33:11.610> about<00:33:11.700> on<00:33:11.910> Saturday<00:33:12.060> and<00:33:12.740> Victor<00:33:13.740> will 00:33:13.910 --> 00:33:13.920 align:start position:0% talk about on Saturday and Victor will 00:33:13.920 --> 00:33:15.410 align:start position:0% talk about on Saturday and Victor will also<00:33:14.160> be<00:33:14.250> talking<00:33:14.430> about<00:33:14.580> distributed 00:33:15.410 --> 00:33:15.420 align:start position:0% also be talking about distributed 00:33:15.420 --> 00:33:17.360 align:start position:0% also be talking about distributed database<00:33:15.840> services<00:33:16.380> and<00:33:16.650> how<00:33:16.830> they<00:33:16.860> fit<00:33:17.220> into 00:33:17.360 --> 00:33:17.370 align:start position:0% database services and how they fit into 00:33:17.370 --> 00:33:20.360 align:start position:0% database services and how they fit into both<00:33:18.300> the<00:33:18.630> swarm<00:33:19.140> network<00:33:19.500> itself<00:33:19.920> and<00:33:20.220> the 00:33:20.360 --> 00:33:20.370 align:start position:0% both the swarm network itself and the 00:33:20.370 --> 00:33:24.650 align:start position:0% both the swarm network itself and the incentive<00:33:20.820> layer<00:33:22.370> so<00:33:23.370> that's<00:33:23.850> that<00:33:24.210> the 00:33:24.650 --> 00:33:24.660 align:start position:0% incentive layer so that's that the 00:33:24.660 --> 00:33:26.840 align:start position:0% incentive layer so that's that the update<00:33:24.960> from<00:33:25.110> us<00:33:25.230> our<00:33:25.470> team<00:33:25.770> is<00:33:26.130> Victor<00:33:26.580> Donny 00:33:26.840 --> 00:33:26.850 align:start position:0% update from us our team is Victor Donny 00:33:26.850 --> 00:33:29.120 align:start position:0% update from us our team is Victor Donny Fabia<00:33:27.360> who<00:33:27.630> and<00:33:27.900> Anton<00:33:28.260> from<00:33:28.500> the<00:33:28.620> foundation 00:33:29.120 --> 00:33:29.130 align:start position:0% Fabia who and Anton from the foundation 00:33:29.130 --> 00:33:31.820 align:start position:0% Fabia who and Anton from the foundation and<00:33:29.280> from<00:33:29.910> Jack<00:33:30.150> we've<00:33:30.390> had<00:33:30.780> a<00:33:30.810> not<00:33:31.470> just<00:33:31.590> one 00:33:31.820 --> 00:33:31.830 align:start position:0% and from Jack we've had a not just one 00:33:31.830 --> 00:33:34.910 align:start position:0% and from Jack we've had a not just one but<00:33:31.980> two<00:33:32.040> Lewis's<00:33:32.760> giving<00:33:33.510> us<00:33:33.630> great<00:33:33.900> a<00:33:34.260> lot<00:33:34.770> of 00:33:34.910 --> 00:33:34.920 align:start position:0% but two Lewis's giving us great a lot of 00:33:34.920 --> 00:33:37.430 align:start position:0% but two Lewis's giving us great a lot of time<00:33:35.130> and<00:33:35.340> code<00:33:35.550> so<00:33:35.850> big<00:33:36.540> thanks<00:33:36.930> to<00:33:36.990> them<00:33:37.170> and 00:33:37.430 --> 00:33:37.440 align:start position:0% time and code so big thanks to them and 00:33:37.440 --> 00:33:39.670 align:start position:0% time and code so big thanks to them and this<00:33:38.250> forum<00:33:38.490> team<00:33:38.640> is<00:33:38.820> still<00:33:39.030> growing<00:33:39.210> we're 00:33:39.670 --> 00:33:39.680 align:start position:0% this forum team is still growing we're 00:33:39.680 --> 00:33:42.170 align:start position:0% this forum team is still growing we're very<00:33:40.680> active<00:33:41.040> development<00:33:41.370> and<00:33:41.670> adding 00:33:42.170 --> 00:33:42.180 align:start position:0% very active development and adding 00:33:42.180 --> 00:33:45.710 align:start position:0% very active development and adding people<00:33:43.760> yeah<00:33:44.760> so<00:33:44.970> there's<00:33:45.150> even<00:33:45.300> more<00:33:45.420> coming 00:33:45.710 --> 00:33:45.720 align:start position:0% people yeah so there's even more coming 00:33:45.720 --> 00:33:48.940 align:start position:0% people yeah so there's even more coming and<00:33:46.460> so<00:33:47.460> I<00:33:47.490> want<00:33:47.760> to<00:33:47.790> make<00:33:47.940> special 00:33:48.940 --> 00:33:48.950 align:start position:0% and so I want to make special 00:33:48.950 --> 00:33:51.020 align:start position:0% and so I want to make special advertisement<00:33:49.950> to<00:33:50.040> our<00:33:50.130> breakout<00:33:50.430> session<00:33:50.820> on 00:33:51.020 --> 00:33:51.030 align:start position:0% advertisement to our breakout session on 00:33:51.030 --> 00:33:54.560 align:start position:0% advertisement to our breakout session on Saturday<00:33:51.960> the<00:33:52.590> session<00:33:53.310> on<00:33:53.400> p2p<00:33:53.700> technologies 00:33:54.560 --> 00:33:54.570 align:start position:0% Saturday the session on p2p technologies 00:33:54.570 --> 00:33:56.930 align:start position:0% Saturday the session on p2p technologies blockchains<00:33:55.470> in<00:33:55.650> data<00:33:55.860> and<00:33:56.100> communication 00:33:56.930 --> 00:33:56.940 align:start position:0% blockchains in data and communication 00:33:56.940 --> 00:33:58.940 align:start position:0% blockchains in data and communication there'll<00:33:57.330> be<00:33:57.360> updates<00:33:57.840> from<00:33:58.230> the<00:33:58.440> swarm<00:33:58.710> team 00:33:58.940 --> 00:33:58.950 align:start position:0% there'll be updates from the swarm team 00:33:58.950 --> 00:34:00.950 align:start position:0% there'll be updates from the swarm team will<00:33:59.430> talk<00:33:59.580> about<00:33:59.760> swaps<00:34:00.150> where<00:34:00.420> and<00:34:00.570> swindle 00:34:00.950 --> 00:34:00.960 align:start position:0% will talk about swaps where and swindle 00:34:00.960 --> 00:34:02.620 align:start position:0% will talk about swaps where and swindle will<00:34:01.200> talk<00:34:01.380> about<00:34:01.590> distributed<00:34:02.100> databases 00:34:02.620 --> 00:34:02.630 align:start position:0% will talk about distributed databases 00:34:02.630 --> 00:34:05.060 align:start position:0% will talk about distributed databases there'll<00:34:03.630> be<00:34:03.660> a<00:34:03.750> PSS<00:34:04.290> update<00:34:04.680> there'll<00:34:04.950> be<00:34:04.980> a 00:34:05.060 --> 00:34:05.070 align:start position:0% there'll be a PSS update there'll be a 00:34:05.070 --> 00:34:08.030 align:start position:0% there'll be a PSS update there'll be a interactive<00:34:06.060> chat<00:34:06.450> demo<00:34:06.810> and<00:34:07.050> updates<00:34:07.920> from 00:34:08.030 --> 00:34:08.040 align:start position:0% interactive chat demo and updates from 00:34:08.040 --> 00:34:09.680 align:start position:0% interactive chat demo and updates from other<00:34:08.250> teams<00:34:08.520> live<00:34:08.820> pier<00:34:09.180> will<00:34:09.360> be<00:34:09.480> talking 00:34:09.680 --> 00:34:09.690 align:start position:0% other teams live pier will be talking 00:34:09.690 --> 00:34:11.480 align:start position:0% other teams live pier will be talking about<00:34:09.870> streaming<00:34:10.230> services<00:34:10.860> of<00:34:11.010> a<00:34:11.070> swarms<00:34:11.370> a 00:34:11.480 --> 00:34:11.490 align:start position:0% about streaming services of a swarms a 00:34:11.490 --> 00:34:13.520 align:start position:0% about streaming services of a swarms a lot<00:34:11.610> of<00:34:11.730> good<00:34:11.880> stuff<00:34:12.120> so<00:34:12.390> we<00:34:13.050> hope<00:34:13.200> to<00:34:13.350> see 00:34:13.520 --> 00:34:13.530 align:start position:0% lot of good stuff so we hope to see 00:34:13.530 --> 00:34:15.230 align:start position:0% lot of good stuff so we hope to see there<00:34:13.710> and<00:34:13.950> with<00:34:14.520> that<00:34:14.640> I'm<00:34:14.760> going<00:34:14.880> to<00:34:14.910> end<00:34:15.060> a 00:34:15.230 --> 00:34:15.240 align:start position:0% there and with that I'm going to end a 00:34:15.240 --> 00:34:17.120 align:start position:0% there and with that I'm going to end a little<00:34:15.330> bit<00:34:15.480> early<00:34:15.710> but<00:34:16.710> thank<00:34:16.890> you<00:34:16.920> for<00:34:17.010> your 00:34:17.120 --> 00:34:17.130 align:start position:0% little bit early but thank you for your 00:34:17.130 --> 00:34:27.419 align:start position:0% little bit early but thank you for your attention 00:34:27.419 --> 00:34:27.429 align:start position:0% 00:34:27.429 --> 00:34:35.009 align:start position:0% [Music]