WEBVTT Kind: captions Language: en 00:00:01.050 --> 00:00:03.110 align:start position:0% so<00:00:01.530> it's<00:00:01.829> my<00:00:02.010> pleasure<00:00:02.220> to<00:00:02.490> start<00:00:02.760> off<00:00:02.909> this 00:00:03.110 --> 00:00:03.120 align:start position:0% so it's my pleasure to start off this 00:00:03.120 --> 00:00:04.519 align:start position:0% so it's my pleasure to start off this team<00:00:03.360> update<00:00:03.720> we're<00:00:03.990> gonna<00:00:04.170> hear<00:00:04.410> from 00:00:04.519 --> 00:00:04.529 align:start position:0% team update we're gonna hear from 00:00:04.529 --> 00:00:06.349 align:start position:0% team update we're gonna hear from everyone<00:00:04.890> in<00:00:05.100> the<00:00:05.130> team<00:00:05.370> or<00:00:05.609> at<00:00:05.790> least<00:00:05.970> a<00:00:06.180> big 00:00:06.349 --> 00:00:06.359 align:start position:0% everyone in the team or at least a big 00:00:06.359 --> 00:00:07.579 align:start position:0% everyone in the team or at least a big part<00:00:06.600> of<00:00:06.660> the<00:00:06.750> team<00:00:06.930> on<00:00:07.049> everything<00:00:07.440> that's 00:00:07.579 --> 00:00:07.589 align:start position:0% part of the team on everything that's 00:00:07.589 --> 00:00:10.669 align:start position:0% part of the team on everything that's been<00:00:07.740> happening<00:00:07.799> with<00:00:08.189> swarm<00:00:08.780> so<00:00:09.780> normally<00:00:10.260> if 00:00:10.669 --> 00:00:10.679 align:start position:0% been happening with swarm so normally if 00:00:10.679 --> 00:00:12.230 align:start position:0% been happening with swarm so normally if you've<00:00:10.830> seen<00:00:11.040> my<00:00:11.160> talks<00:00:11.460> before<00:00:11.639> this<00:00:12.030> is<00:00:12.210> the 00:00:12.230 --> 00:00:12.240 align:start position:0% you've seen my talks before this is the 00:00:12.240 --> 00:00:13.669 align:start position:0% you've seen my talks before this is the part<00:00:12.450> where<00:00:12.690> I<00:00:12.750> tell<00:00:12.780> you<00:00:12.990> what's<00:00:13.259> forum<00:00:13.530> is 00:00:13.669 --> 00:00:13.679 align:start position:0% part where I tell you what's forum is 00:00:13.679 --> 00:00:15.169 align:start position:0% part where I tell you what's forum is and<00:00:13.920> how<00:00:14.009> it<00:00:14.160> works<00:00:14.400> it's<00:00:14.730> all<00:00:14.880> about 00:00:15.169 --> 00:00:15.179 align:start position:0% and how it works it's all about 00:00:15.179 --> 00:00:16.910 align:start position:0% and how it works it's all about decentralized<00:00:15.870> storage<00:00:16.289> server<00:00:16.650> less 00:00:16.910 --> 00:00:16.920 align:start position:0% decentralized storage server less 00:00:16.920 --> 00:00:19.370 align:start position:0% decentralized storage server less content<00:00:17.699> storage<00:00:17.910> distribution<00:00:18.660> and<00:00:19.140> all<00:00:19.230> the 00:00:19.370 --> 00:00:19.380 align:start position:0% content storage distribution and all the 00:00:19.380 --> 00:00:20.870 align:start position:0% content storage distribution and all the great<00:00:19.529> stuff<00:00:19.800> that<00:00:20.100> web<00:00:20.250> 3<00:00:20.490> needs 00:00:20.870 --> 00:00:20.880 align:start position:0% great stuff that web 3 needs 00:00:20.880 --> 00:00:24.140 align:start position:0% great stuff that web 3 needs appear<00:00:21.510> to<00:00:21.539> be<00:00:21.660> a<00:00:21.720> communication<00:00:22.439> in<00:00:23.220> all<00:00:23.910> that 00:00:24.140 --> 00:00:24.150 align:start position:0% appear to be a communication in all that 00:00:24.150 --> 00:00:25.700 align:start position:0% appear to be a communication in all that great<00:00:24.390> stuff<00:00:24.510> but<00:00:25.109> we<00:00:25.230> don't<00:00:25.410> have<00:00:25.470> time<00:00:25.650> for 00:00:25.700 --> 00:00:25.710 align:start position:0% great stuff but we don't have time for 00:00:25.710 --> 00:00:28.550 align:start position:0% great stuff but we don't have time for that<00:00:25.980> today<00:00:26.099> so<00:00:26.660> you<00:00:27.660> know<00:00:27.750> come<00:00:27.990> find<00:00:28.230> us<00:00:28.320> talk 00:00:28.550 --> 00:00:28.560 align:start position:0% that today so you know come find us talk 00:00:28.560 --> 00:00:29.450 align:start position:0% that today so you know come find us talk to<00:00:28.710> us<00:00:28.769> if<00:00:28.890> you<00:00:28.949> want<00:00:29.070> to<00:00:29.130> learn<00:00:29.250> more<00:00:29.400> about 00:00:29.450 --> 00:00:29.460 align:start position:0% to us if you want to learn more about 00:00:29.460 --> 00:00:31.070 align:start position:0% to us if you want to learn more about swarm<00:00:29.820> today<00:00:30.119> it's<00:00:30.240> all<00:00:30.390> about<00:00:30.420> the<00:00:30.630> updates 00:00:31.070 --> 00:00:31.080 align:start position:0% swarm today it's all about the updates 00:00:31.080 --> 00:00:32.930 align:start position:0% swarm today it's all about the updates what's<00:00:31.349> been<00:00:31.560> happening<00:00:31.980> so<00:00:32.579> one<00:00:32.730> of<00:00:32.759> the 00:00:32.930 --> 00:00:32.940 align:start position:0% what's been happening so one of the 00:00:32.940 --> 00:00:34.040 align:start position:0% what's been happening so one of the things<00:00:33.120> has<00:00:33.270> changed<00:00:33.300> in<00:00:33.750> the<00:00:33.809> last<00:00:33.870> year 00:00:34.040 --> 00:00:34.050 align:start position:0% things has changed in the last year 00:00:34.050 --> 00:00:35.900 align:start position:0% things has changed in the last year we've<00:00:34.320> updated<00:00:34.500> our<00:00:34.860> homepage<00:00:35.100> because<00:00:35.579> it 00:00:35.900 --> 00:00:35.910 align:start position:0% we've updated our homepage because it 00:00:35.910 --> 00:00:38.630 align:start position:0% we've updated our homepage because it needed<00:00:36.300> an<00:00:36.390> update<00:00:36.660> and<00:00:36.989> it<00:00:37.890> constantly<00:00:38.430> does 00:00:38.630 --> 00:00:38.640 align:start position:0% needed an update and it constantly does 00:00:38.640 --> 00:00:41.090 align:start position:0% needed an update and it constantly does but<00:00:38.910> anyway<00:00:39.300> we've<00:00:40.020> changed<00:00:40.290> the<00:00:40.440> address<00:00:40.530> so 00:00:41.090 --> 00:00:41.100 align:start position:0% but anyway we've changed the address so 00:00:41.100 --> 00:00:42.560 align:start position:0% but anyway we've changed the address so if<00:00:41.219> you<00:00:41.340> don't<00:00:41.520> remember<00:00:41.640> anything<00:00:41.879> just 00:00:42.560 --> 00:00:42.570 align:start position:0% if you don't remember anything just 00:00:42.570 --> 00:00:44.900 align:start position:0% if you don't remember anything just swarm<00:00:42.960> a<00:00:43.410> theoria<00:00:43.770> morgue<00:00:44.309> as<00:00:44.489> it<00:00:44.579> says<00:00:44.730> in<00:00:44.850> the 00:00:44.900 --> 00:00:44.910 align:start position:0% swarm a theoria morgue as it says in the 00:00:44.910 --> 00:00:46.220 align:start position:0% swarm a theoria morgue as it says in the bottom<00:00:45.120> that<00:00:45.270> will<00:00:45.450> redirect<00:00:45.719> you<00:00:46.020> to<00:00:46.050> the 00:00:46.220 --> 00:00:46.230 align:start position:0% bottom that will redirect you to the 00:00:46.230 --> 00:00:48.799 align:start position:0% bottom that will redirect you to the swarm<00:00:46.590> homepage<00:00:47.030> it'll<00:00:48.030> redirect<00:00:48.239> you<00:00:48.510> to<00:00:48.539> one 00:00:48.799 --> 00:00:48.809 align:start position:0% swarm homepage it'll redirect you to one 00:00:48.809 --> 00:00:51.290 align:start position:0% swarm homepage it'll redirect you to one hosted<00:00:49.200> on<00:00:49.379> swarm<00:00:49.739> so<00:00:50.309> most<00:00:50.789> of<00:00:50.879> the<00:00:50.940> time<00:00:51.120> it 00:00:51.290 --> 00:00:51.300 align:start position:0% hosted on swarm so most of the time it 00:00:51.300 --> 00:00:55.369 align:start position:0% hosted on swarm so most of the time it actually<00:00:51.570> works<00:00:53.360> hopefully<00:00:54.360> so<00:00:55.110> you<00:00:55.230> see<00:00:55.350> up 00:00:55.369 --> 00:00:55.379 align:start position:0% actually works hopefully so you see up 00:00:55.379 --> 00:00:57.020 align:start position:0% actually works hopefully so you see up there<00:00:55.500> that<00:00:55.980> I<00:00:56.100> want<00:00:56.340> to<00:00:56.399> point<00:00:56.550> out<00:00:56.640> it<00:00:56.850> says 00:00:57.020 --> 00:00:57.030 align:start position:0% there that I want to point out it says 00:00:57.030 --> 00:00:59.000 align:start position:0% there that I want to point out it says installation<00:00:57.750> downloads<00:00:58.289> and<00:00:58.500> documentation 00:00:59.000 --> 00:00:59.010 align:start position:0% installation downloads and documentation 00:00:59.010 --> 00:01:00.410 align:start position:0% installation downloads and documentation those<00:00:59.340> are<00:00:59.489> the<00:00:59.550> most<00:00:59.699> important<00:01:00.120> links 00:01:00.410 --> 00:01:00.420 align:start position:0% those are the most important links 00:01:00.420 --> 00:01:02.540 align:start position:0% those are the most important links because<00:01:01.230> I've<00:01:01.320> got<00:01:01.469> updated<00:01:01.980> documentation 00:01:02.540 --> 00:01:02.550 align:start position:0% because I've got updated documentation 00:01:02.550 --> 00:01:04.700 align:start position:0% because I've got updated documentation the<00:01:03.329> downloads<00:01:03.780> are<00:01:03.960> downloaded<00:01:04.500> bubble 00:01:04.700 --> 00:01:04.710 align:start position:0% the downloads are downloaded bubble 00:01:04.710 --> 00:01:05.899 align:start position:0% the downloads are downloaded bubble binaries<00:01:05.070> I'll<00:01:05.250> get<00:01:05.400> to<00:01:05.489> that<00:01:05.519> in<00:01:05.640> a<00:01:05.820> moment 00:01:05.899 --> 00:01:05.909 align:start position:0% binaries I'll get to that in a moment 00:01:05.909 --> 00:01:07.700 align:start position:0% binaries I'll get to that in a moment anyway<00:01:06.600> what<00:01:06.960> I<00:01:06.990> should<00:01:07.170> have<00:01:07.290> said<00:01:07.470> is<00:01:07.650> that 00:01:07.700 --> 00:01:07.710 align:start position:0% anyway what I should have said is that 00:01:07.710 --> 00:01:10.070 align:start position:0% anyway what I should have said is that the<00:01:08.250> swarm<00:01:08.490> homepage<00:01:08.880> is<00:01:09.030> that<00:01:09.150> bzz<00:01:09.689> dot<00:01:09.900> the 00:01:10.070 --> 00:01:10.080 align:start position:0% the swarm homepage is that bzz dot the 00:01:10.080 --> 00:01:11.870 align:start position:0% the swarm homepage is that bzz dot the swarm<00:01:10.350> dot<00:01:10.530> eath<00:01:10.799> but<00:01:11.340> for<00:01:11.490> that<00:01:11.580> you<00:01:11.790> will 00:01:11.870 --> 00:01:11.880 align:start position:0% swarm dot eath but for that you will 00:01:11.880 --> 00:01:14.240 align:start position:0% swarm dot eath but for that you will lead<00:01:12.000> us<00:01:12.119> form<00:01:12.360> compatible<00:01:12.840> browser<00:01:13.049> not<00:01:14.040> that 00:01:14.240 --> 00:01:14.250 align:start position:0% lead us form compatible browser not that 00:01:14.250 --> 00:01:17.120 align:start position:0% lead us form compatible browser not that many<00:01:14.430> around<00:01:14.520> but<00:01:15.290> this<00:01:16.290> is<00:01:16.350> advertising<00:01:17.009> for 00:01:17.120 --> 00:01:17.130 align:start position:0% many around but this is advertising for 00:01:17.130 --> 00:01:19.460 align:start position:0% many around but this is advertising for the<00:01:17.189> future<00:01:17.490> so<00:01:18.090> we<00:01:18.360> have<00:01:18.990> a<00:01:19.020> new<00:01:19.200> release 00:01:19.460 --> 00:01:19.470 align:start position:0% the future so we have a new release 00:01:19.470 --> 00:01:22.700 align:start position:0% the future so we have a new release process<00:01:19.790> and<00:01:20.790> swarm<00:01:21.360> now<00:01:21.570> lives<00:01:22.259> in<00:01:22.439> the<00:01:22.530> same 00:01:22.700 --> 00:01:22.710 align:start position:0% process and swarm now lives in the same 00:01:22.710 --> 00:01:25.820 align:start position:0% process and swarm now lives in the same github<00:01:23.100> repository<00:01:23.850> as<00:01:23.970> gift<00:01:24.240> so<00:01:24.990> we<00:01:25.470> used<00:01:25.680> to 00:01:25.820 --> 00:01:25.830 align:start position:0% github repository as gift so we used to 00:01:25.830 --> 00:01:27.289 align:start position:0% github repository as gift so we used to live<00:01:25.950> in<00:01:25.979> a<00:01:26.159> different<00:01:26.610> fork<00:01:27.030> different 00:01:27.289 --> 00:01:27.299 align:start position:0% live in a different fork different 00:01:27.299 --> 00:01:29.480 align:start position:0% live in a different fork different repositories<00:01:27.590> as<00:01:28.590> gift<00:01:28.829> if<00:01:29.009> you<00:01:29.040> get<00:01:29.250> gift 00:01:29.480 --> 00:01:29.490 align:start position:0% repositories as gift if you get gift 00:01:29.490 --> 00:01:31.249 align:start position:0% repositories as gift if you get gift code<00:01:29.729> you<00:01:29.909> get<00:01:30.000> swarm<00:01:30.299> code<00:01:30.540> that<00:01:31.110> means 00:01:31.249 --> 00:01:31.259 align:start position:0% code you get swarm code that means 00:01:31.259 --> 00:01:33.380 align:start position:0% code you get swarm code that means whenever<00:01:31.560> that<00:01:31.979> gift<00:01:32.250> release<00:01:32.820> is<00:01:33.030> triggered 00:01:33.380 --> 00:01:33.390 align:start position:0% whenever that gift release is triggered 00:01:33.390 --> 00:01:35.090 align:start position:0% whenever that gift release is triggered as<00:01:33.689> form<00:01:33.990> release<00:01:34.229> is<00:01:34.409> triggered<00:01:34.740> there's<00:01:34.979> no 00:01:35.090 --> 00:01:35.100 align:start position:0% as form release is triggered there's no 00:01:35.100 --> 00:01:36.710 align:start position:0% as form release is triggered there's no more<00:01:35.280> separatrices<00:01:35.640> they<00:01:36.180> all<00:01:36.299> come<00:01:36.509> at<00:01:36.600> the 00:01:36.710 --> 00:01:36.720 align:start position:0% more separatrices they all come at the 00:01:36.720 --> 00:01:38.350 align:start position:0% more separatrices they all come at the same<00:01:36.750> time<00:01:37.140> that<00:01:37.350> makes<00:01:37.530> it<00:01:37.680> nice<00:01:37.770> and<00:01:37.829> easy 00:01:38.350 --> 00:01:38.360 align:start position:0% same time that makes it nice and easy 00:01:38.360 --> 00:01:40.429 align:start position:0% same time that makes it nice and easy whenever<00:01:39.360> there<00:01:39.570> is<00:01:39.659> a<00:01:39.689> release<00:01:39.960> of<00:01:40.020> gifts 00:01:40.429 --> 00:01:40.439 align:start position:0% whenever there is a release of gifts 00:01:40.439 --> 00:01:41.780 align:start position:0% whenever there is a release of gifts that<00:01:40.619> there's<00:01:40.860> a<00:01:40.950> release<00:01:41.130> of<00:01:41.280> swarm<00:01:41.610> and 00:01:41.780 --> 00:01:41.790 align:start position:0% that there's a release of swarm and 00:01:41.790 --> 00:01:44.030 align:start position:0% that there's a release of swarm and simultaneously<00:01:42.630> all<00:01:42.930> of<00:01:43.140> the<00:01:43.259> nodes<00:01:43.439> on<00:01:43.740> our 00:01:44.030 --> 00:01:44.040 align:start position:0% simultaneously all of the nodes on our 00:01:44.040 --> 00:01:46.550 align:start position:0% simultaneously all of the nodes on our cluster<00:01:44.729> the<00:01:44.880> swarm<00:01:45.119> gateways<00:01:45.540> cluster<00:01:46.439> are 00:01:46.550 --> 00:01:46.560 align:start position:0% cluster the swarm gateways cluster are 00:01:46.560 --> 00:01:48.080 align:start position:0% cluster the swarm gateways cluster are updated<00:01:47.040> as<00:01:47.159> well<00:01:47.280> so<00:01:47.490> they're<00:01:47.640> always 00:01:48.080 --> 00:01:48.090 align:start position:0% updated as well so they're always 00:01:48.090 --> 00:01:49.520 align:start position:0% updated as well so they're always everything<00:01:48.450> is<00:01:48.689> running<00:01:48.899> at<00:01:49.110> the<00:01:49.229> newest 00:01:49.520 --> 00:01:49.530 align:start position:0% everything is running at the newest 00:01:49.530 --> 00:01:51.560 align:start position:0% everything is running at the newest release<00:01:49.860> version<00:01:50.369> the<00:01:50.460> lowest<00:01:50.729> get<00:01:51.240> release 00:01:51.560 --> 00:01:51.570 align:start position:0% release version the lowest get release 00:01:51.570 --> 00:01:54.649 align:start position:0% release version the lowest get release tag<00:01:51.930> and<00:01:52.909> we<00:01:53.909> are<00:01:54.030> under<00:01:54.360> heavy<00:01:54.390> development 00:01:54.649 --> 00:01:54.659 align:start position:0% tag and we are under heavy development 00:01:54.659 --> 00:01:57.230 align:start position:0% tag and we are under heavy development so<00:01:55.380> we<00:01:55.560> can<00:01:55.860> and<00:01:56.100> do<00:01:56.280> introduce<00:01:56.759> breaking 00:01:57.230 --> 00:01:57.240 align:start position:0% so we can and do introduce breaking 00:01:57.240 --> 00:02:00.530 align:start position:0% so we can and do introduce breaking changes<00:01:57.659> quite<00:01:57.869> regularly<00:01:58.850> so<00:01:59.850> always<00:02:00.270> make 00:02:00.530 --> 00:02:00.540 align:start position:0% changes quite regularly so always make 00:02:00.540 --> 00:02:02.300 align:start position:0% changes quite regularly so always make sure<00:02:00.960> to<00:02:01.110> update<00:02:01.229> to<00:02:01.680> this<00:02:01.770> latest<00:02:02.009> release 00:02:02.300 --> 00:02:02.310 align:start position:0% sure to update to this latest release 00:02:02.310 --> 00:02:04.760 align:start position:0% sure to update to this latest release and<00:02:02.939> there<00:02:03.719> is<00:02:03.840> actually<00:02:04.200> right<00:02:04.560> now<00:02:04.740> a 00:02:04.760 --> 00:02:04.770 align:start position:0% and there is actually right now a 00:02:04.770 --> 00:02:06.679 align:start position:0% and there is actually right now a breaking<00:02:05.369> change<00:02:05.670> in<00:02:05.880> the<00:02:05.969> master<00:02:06.240> branch<00:02:06.509> set 00:02:06.679 --> 00:02:06.689 align:start position:0% breaking change in the master branch set 00:02:06.689 --> 00:02:08.389 align:start position:0% breaking change in the master branch set the<00:02:06.810> next<00:02:06.930> guest<00:02:07.200> release<00:02:07.500> will<00:02:07.890> be<00:02:07.920> next<00:02:08.190> four 00:02:08.389 --> 00:02:08.399 align:start position:0% the next guest release will be next four 00:02:08.399 --> 00:02:09.889 align:start position:0% the next guest release will be next four release<00:02:08.610> that<00:02:08.849> breaks<00:02:09.119> changes<00:02:09.569> so<00:02:09.720> always 00:02:09.889 --> 00:02:09.899 align:start position:0% release that breaks changes so always 00:02:09.899 --> 00:02:11.900 align:start position:0% release that breaks changes so always stay<00:02:10.140> up<00:02:10.200> to<00:02:10.319> date<00:02:10.349> let<00:02:11.190> me<00:02:11.250> say<00:02:11.400> that<00:02:11.520> again<00:02:11.550> as 00:02:11.900 --> 00:02:11.910 align:start position:0% stay up to date let me say that again as 00:02:11.910 --> 00:02:13.790 align:start position:0% stay up to date let me say that again as important<00:02:12.330> always<00:02:12.930> go<00:02:13.080> for<00:02:13.260> the<00:02:13.290> latest 00:02:13.790 --> 00:02:13.800 align:start position:0% important always go for the latest 00:02:13.800 --> 00:02:16.250 align:start position:0% important always go for the latest before<00:02:14.190> you<00:02:14.280> ask<00:02:14.370> us<00:02:14.610> any<00:02:14.760> questions<00:02:15.240> okay<00:02:15.840> so 00:02:16.250 --> 00:02:16.260 align:start position:0% before you ask us any questions okay so 00:02:16.260 --> 00:02:17.990 align:start position:0% before you ask us any questions okay so having<00:02:16.740> said<00:02:17.010> that<00:02:17.040> let's<00:02:17.580> talk<00:02:17.730> about<00:02:17.790> how 00:02:17.990 --> 00:02:18.000 align:start position:0% having said that let's talk about how 00:02:18.000 --> 00:02:19.700 align:start position:0% having said that let's talk about how installation<00:02:18.660> works<00:02:18.840> because<00:02:19.170> that's<00:02:19.290> also 00:02:19.700 --> 00:02:19.710 align:start position:0% installation works because that's also 00:02:19.710 --> 00:02:21.350 align:start position:0% installation works because that's also gotten<00:02:19.980> a<00:02:20.040> lot<00:02:20.190> easier<00:02:20.640> in<00:02:20.820> the<00:02:20.970> past<00:02:21.180> few 00:02:21.350 --> 00:02:21.360 align:start position:0% gotten a lot easier in the past few 00:02:21.360 --> 00:02:24.620 align:start position:0% gotten a lot easier in the past few months<00:02:22.460> how<00:02:23.460> to<00:02:23.490> install<00:02:23.880> swarm<00:02:24.240> well<00:02:24.450> there's 00:02:24.620 --> 00:02:24.630 align:start position:0% months how to install swarm well there's 00:02:24.630 --> 00:02:25.910 align:start position:0% months how to install swarm well there's always<00:02:24.720> the<00:02:24.990> option<00:02:25.140> of<00:02:25.350> installing<00:02:25.530> from 00:02:25.910 --> 00:02:25.920 align:start position:0% always the option of installing from 00:02:25.920 --> 00:02:27.590 align:start position:0% always the option of installing from source<00:02:26.250> code<00:02:26.340> I<00:02:26.760> said<00:02:27.330> it's<00:02:27.510> the<00:02:27.570> same 00:02:27.590 --> 00:02:27.600 align:start position:0% source code I said it's the same 00:02:27.600 --> 00:02:29.840 align:start position:0% source code I said it's the same repository<00:02:28.350> as<00:02:28.410> guest<00:02:28.770> so<00:02:29.070> that's<00:02:29.280> no<00:02:29.490> mystery 00:02:29.840 --> 00:02:29.850 align:start position:0% repository as guest so that's no mystery 00:02:29.850 --> 00:02:32.720 align:start position:0% repository as guest so that's no mystery anymore<00:02:30.440> it's<00:02:31.440> the<00:02:31.530> go<00:02:31.710> a<00:02:31.740> theorem<00:02:32.160> repository 00:02:32.720 --> 00:02:32.730 align:start position:0% anymore it's the go a theorem repository 00:02:32.730 --> 00:02:34.730 align:start position:0% anymore it's the go a theorem repository the<00:02:33.240> second<00:02:33.570> one<00:02:33.660> is<00:02:33.750> to<00:02:33.870> download<00:02:34.080> binaries 00:02:34.730 --> 00:02:34.740 align:start position:0% the second one is to download binaries 00:02:34.740 --> 00:02:36.290 align:start position:0% the second one is to download binaries if<00:02:34.890> you<00:02:34.950> go<00:02:35.070> to<00:02:35.160> our<00:02:35.340> page<00:02:35.610> and<00:02:35.910> click<00:02:36.180> on 00:02:36.290 --> 00:02:36.300 align:start position:0% if you go to our page and click on 00:02:36.300 --> 00:02:37.910 align:start position:0% if you go to our page and click on download<00:02:36.690> so<00:02:36.870> the<00:02:36.960> compiled<00:02:37.320> binaries<00:02:37.740> for 00:02:37.910 --> 00:02:37.920 align:start position:0% download so the compiled binaries for 00:02:37.920 --> 00:02:40.010 align:start position:0% download so the compiled binaries for Windows<00:02:38.220> Mac<00:02:38.520> and<00:02:38.790> Linux<00:02:38.820> in<00:02:39.630> both<00:02:39.780> the 00:02:40.010 --> 00:02:40.020 align:start position:0% Windows Mac and Linux in both the 00:02:40.020 --> 00:02:43.100 align:start position:0% Windows Mac and Linux in both the release<00:02:40.380> branch<00:02:40.680> and<00:02:41.010> the<00:02:41.870> master<00:02:42.870> branch 00:02:43.100 --> 00:02:43.110 align:start position:0% release branch and the master branch 00:02:43.110 --> 00:02:46.340 align:start position:0% release branch and the master branch unstable<00:02:43.770> development<00:02:44.310> bleeding<00:02:44.640> edge<00:02:45.350> if 00:02:46.340 --> 00:02:46.350 align:start position:0% unstable development bleeding edge if 00:02:46.350 --> 00:02:47.870 align:start position:0% unstable development bleeding edge if you're<00:02:46.680> on<00:02:46.770> Ubuntu<00:02:47.190> it's<00:02:47.370> even<00:02:47.610> easier 00:02:47.870 --> 00:02:47.880 align:start position:0% you're on Ubuntu it's even easier 00:02:47.880 --> 00:02:51.050 align:start position:0% you're on Ubuntu it's even easier because<00:02:48.090> you<00:02:48.330> can<00:02:48.480> install<00:02:48.890> from<00:02:49.890> the<00:02:50.220> theorem 00:02:51.050 --> 00:02:51.060 align:start position:0% because you can install from the theorem 00:02:51.060 --> 00:02:53.660 align:start position:0% because you can install from the theorem PPA<00:02:51.720> and<00:02:51.810> then<00:02:52.140> you'll<00:02:52.470> it'll<00:02:53.130> automatically 00:02:53.660 --> 00:02:53.670 align:start position:0% PPA and then you'll it'll automatically 00:02:53.670 --> 00:02:55.070 align:start position:0% PPA and then you'll it'll automatically handle<00:02:54.030> the<00:02:54.120> updates<00:02:54.450> for<00:02:54.660> you<00:02:54.780> so<00:02:54.960> you 00:02:55.070 --> 00:02:55.080 align:start position:0% handle the updates for you so you 00:02:55.080 --> 00:02:57.080 align:start position:0% handle the updates for you so you install<00:02:55.380> it<00:02:55.530> from<00:02:55.710> there<00:02:55.890> once<00:02:56.100> the<00:02:56.220> theorem<00:02:56.940> - 00:02:57.080 --> 00:02:57.090 align:start position:0% install it from there once the theorem - 00:02:57.090 --> 00:02:58.670 align:start position:0% install it from there once the theorem - swarm<00:02:57.450> package<00:02:57.810> you<00:02:58.230> will<00:02:58.320> always 00:02:58.670 --> 00:02:58.680 align:start position:0% swarm package you will always 00:02:58.680 --> 00:03:00.170 align:start position:0% swarm package you will always automatically<00:02:59.280> be<00:02:59.490> on<00:02:59.610> the<00:02:59.700> latest<00:03:00.000> release 00:03:00.170 --> 00:03:00.180 align:start position:0% automatically be on the latest release 00:03:00.180 --> 00:03:03.320 align:start position:0% automatically be on the latest release and<00:03:00.750> finally<00:03:01.710> we<00:03:01.860> have<00:03:02.040> docker<00:03:02.340> images<00:03:02.850> also 00:03:03.320 --> 00:03:03.330 align:start position:0% and finally we have docker images also 00:03:03.330 --> 00:03:06.260 align:start position:0% and finally we have docker images also now<00:03:03.870> available<00:03:04.220> so<00:03:05.220> makes<00:03:05.730> it<00:03:05.850> easy<00:03:06.000> to<00:03:06.060> deploy 00:03:06.260 --> 00:03:06.270 align:start position:0% now available so makes it easy to deploy 00:03:06.270 --> 00:03:08.090 align:start position:0% now available so makes it easy to deploy it<00:03:06.510> in<00:03:06.600> a<00:03:06.630> dock<00:03:06.810> raised<00:03:07.050> environment<00:03:07.860> it's<00:03:08.010> the 00:03:08.090 --> 00:03:08.100 align:start position:0% it in a dock raised environment it's the 00:03:08.100 --> 00:03:12.800 align:start position:0% it in a dock raised environment it's the F<00:03:08.340> devups<00:03:09.980> swarm<00:03:10.980> repo<00:03:11.760> so<00:03:12.300> there<00:03:12.570> will<00:03:12.690> always 00:03:12.800 --> 00:03:12.810 align:start position:0% F devups swarm repo so there will always 00:03:12.810 --> 00:03:14.450 align:start position:0% F devups swarm repo so there will always be<00:03:12.930> newer<00:03:13.170> binaries<00:03:13.680> they<00:03:13.830> are<00:03:13.920> both<00:03:14.160> in<00:03:14.400> the 00:03:14.450 --> 00:03:14.460 align:start position:0% be newer binaries they are both in the 00:03:14.460 --> 00:03:16.490 align:start position:0% be newer binaries they are both in the the<00:03:15.270> latest<00:03:15.630> tag<00:03:15.870> will<00:03:16.080> be<00:03:16.170> the<00:03:16.290> release 00:03:16.490 --> 00:03:16.500 align:start position:0% the latest tag will be the release 00:03:16.500 --> 00:03:18.230 align:start position:0% the latest tag will be the release version<00:03:16.680> and<00:03:16.980> the<00:03:17.040> edge<00:03:17.190> tag<00:03:17.580> is<00:03:17.790> the<00:03:17.910> bleeding 00:03:18.230 --> 00:03:18.240 align:start position:0% version and the edge tag is the bleeding 00:03:18.240 --> 00:03:21.590 align:start position:0% version and the edge tag is the bleeding edge<00:03:19.100> okay<00:03:20.100> so<00:03:20.700> now<00:03:20.850> we're<00:03:21.030> gonna<00:03:21.120> move<00:03:21.300> on<00:03:21.450> to 00:03:21.590 --> 00:03:21.600 align:start position:0% edge okay so now we're gonna move on to 00:03:21.600 --> 00:03:23.150 align:start position:0% edge okay so now we're gonna move on to team<00:03:21.750> updates<00:03:22.110> we're<00:03:22.590> gonna<00:03:22.740> hear<00:03:22.950> from 00:03:23.150 --> 00:03:23.160 align:start position:0% team updates we're gonna hear from 00:03:23.160 --> 00:03:25.220 align:start position:0% team updates we're gonna hear from various<00:03:24.120> sub<00:03:24.270> project<00:03:24.690> we're<00:03:24.810> going<00:03:24.930> to<00:03:24.990> start 00:03:25.220 --> 00:03:25.230 align:start position:0% various sub project we're going to start 00:03:25.230 --> 00:03:26.930 align:start position:0% various sub project we're going to start off<00:03:25.320> with<00:03:25.500> feeds<00:03:25.770> which<00:03:26.100> is<00:03:26.310> a<00:03:26.340> nice<00:03:26.550> way<00:03:26.790> of 00:03:26.930 --> 00:03:26.940 align:start position:0% off with feeds which is a nice way of 00:03:26.940 --> 00:03:29.510 align:start position:0% off with feeds which is a nice way of doing<00:03:27.720> dynamic<00:03:27.900> change<00:03:28.650> constantly<00:03:28.920> changing 00:03:29.510 --> 00:03:29.520 align:start position:0% doing dynamic change constantly changing 00:03:29.520 --> 00:03:31.220 align:start position:0% doing dynamic change constantly changing data<00:03:29.670> in<00:03:29.910> swarm<00:03:30.209> with<00:03:30.450> only<00:03:30.600> a<00:03:30.690> single<00:03:30.900> on 00:03:31.220 --> 00:03:31.230 align:start position:0% data in swarm with only a single on 00:03:31.230 --> 00:03:34.190 align:start position:0% data in swarm with only a single on chain<00:03:31.590> transaction<00:03:32.160> to<00:03:32.280> the<00:03:32.310> NS<00:03:32.670> then<00:03:33.450> Donnie 00:03:34.190 --> 00:03:34.200 align:start position:0% chain transaction to the NS then Donnie 00:03:34.200 --> 00:03:35.600 align:start position:0% chain transaction to the NS then Donnie will<00:03:34.350> talk<00:03:34.500> about<00:03:34.560> encryption<00:03:35.010> and<00:03:35.250> access 00:03:35.600 --> 00:03:35.610 align:start position:0% will talk about encryption and access 00:03:35.610 --> 00:03:37.910 align:start position:0% will talk about encryption and access control<00:03:36.060> how<00:03:36.209> to<00:03:36.270> keep<00:03:36.570> data<00:03:37.260> secure<00:03:37.500> make 00:03:37.910 --> 00:03:37.920 align:start position:0% control how to keep data secure make 00:03:37.920 --> 00:03:40.070 align:start position:0% control how to keep data secure make sure<00:03:38.100> that<00:03:38.220> only<00:03:38.370> the<00:03:38.580> right<00:03:38.670> people<00:03:38.730> see<00:03:39.209> it 00:03:40.070 --> 00:03:40.080 align:start position:0% sure that only the right people see it 00:03:40.080 --> 00:03:41.180 align:start position:0% sure that only the right people see it Anton<00:03:40.650> is<00:03:40.740> going<00:03:40.890> to<00:03:40.950> talk<00:03:41.070> about 00:03:41.180 --> 00:03:41.190 align:start position:0% Anton is going to talk about 00:03:41.190 --> 00:03:44.390 align:start position:0% Anton is going to talk about observability<00:03:42.030> which<00:03:42.300> is<00:03:42.740> about<00:03:43.740> how<00:03:44.010> we<00:03:44.070> can 00:03:44.390 --> 00:03:44.400 align:start position:0% observability which is about how we can 00:03:44.400 --> 00:03:45.590 align:start position:0% observability which is about how we can actually<00:03:44.520> observe<00:03:44.760> what's<00:03:45.150> happening<00:03:45.510> in 00:03:45.590 --> 00:03:45.600 align:start position:0% actually observe what's happening in 00:03:45.600 --> 00:03:47.030 align:start position:0% actually observe what's happening in this<00:03:45.690> form<00:03:45.959> and<00:03:46.110> in<00:03:46.170> our<00:03:46.290> cluster<00:03:46.680> with<00:03:46.860> some 00:03:47.030 --> 00:03:47.040 align:start position:0% this form and in our cluster with some 00:03:47.040 --> 00:03:50.960 align:start position:0% this form and in our cluster with some real<00:03:47.730> nice<00:03:47.910> logging<00:03:48.840> and<00:03:48.959> tracing<00:03:49.970> Louis 00:03:50.960 --> 00:03:50.970 align:start position:0% real nice logging and tracing Louis 00:03:50.970 --> 00:03:52.280 align:start position:0% real nice logging and tracing Louis we'll<00:03:51.120> talk<00:03:51.270> about<00:03:51.420> PSS<00:03:51.840> which<00:03:52.050> is<00:03:52.170> the 00:03:52.280 --> 00:03:52.290 align:start position:0% we'll talk about PSS which is the 00:03:52.290 --> 00:03:53.720 align:start position:0% we'll talk about PSS which is the communications<00:03:53.010> protocol<00:03:53.550> that's 00:03:53.720 --> 00:03:53.730 align:start position:0% communications protocol that's 00:03:53.730 --> 00:03:56.830 align:start position:0% communications protocol that's piggybacking<00:03:54.390> on<00:03:54.540> top<00:03:54.720> of<00:03:54.870> the<00:03:54.990> swarm<00:03:55.459> network 00:03:56.830 --> 00:03:56.840 align:start position:0% piggybacking on top of the swarm network 00:03:56.840 --> 00:03:59.800 align:start position:0% piggybacking on top of the swarm network then<00:03:57.920> Victor<00:03:58.920> will<00:03:59.040> talk<00:03:59.190> a<00:03:59.220> little<00:03:59.430> bit<00:03:59.640> about 00:03:59.800 --> 00:03:59.810 align:start position:0% then Victor will talk a little bit about 00:03:59.810 --> 00:04:03.410 align:start position:0% then Victor will talk a little bit about light<00:04:00.810> nodes<00:04:01.050> how<00:04:01.320> we<00:04:01.380> plan<00:04:02.100> to<00:04:02.280> into<00:04:02.940> mobile 00:04:03.410 --> 00:04:03.420 align:start position:0% light nodes how we plan to into mobile 00:04:03.420 --> 00:04:06.260 align:start position:0% light nodes how we plan to into mobile phones<00:04:04.230> into<00:04:04.620> the<00:04:04.740> swarm<00:04:04.950> network<00:04:05.280> and<00:04:05.550> then 00:04:06.260 --> 00:04:06.270 align:start position:0% phones into the swarm network and then 00:04:06.270 --> 00:04:07.580 align:start position:0% phones into the swarm network and then what's<00:04:06.540> on<00:04:06.660> our<00:04:06.780> roadmap<00:04:06.930> what's<00:04:07.260> coming<00:04:07.530> up 00:04:07.580 --> 00:04:07.590 align:start position:0% what's on our roadmap what's coming up 00:04:07.590 --> 00:04:07.940 align:start position:0% what's on our roadmap what's coming up next 00:04:07.940 --> 00:04:07.950 align:start position:0% next 00:04:07.950 --> 00:04:13.140 align:start position:0% next so<00:04:08.480> yeah<00:04:09.480> let's<00:04:09.750> have<00:04:10.200> Xavier<00:04:10.620> pon<00:04:10.770> say<00:04:10.920> trees 00:04:13.140 --> 00:04:13.150 align:start position:0% 00:04:13.150 --> 00:04:18.050 align:start position:0% [Applause] 00:04:18.050 --> 00:04:18.060 align:start position:0% [Applause] 00:04:18.060 --> 00:04:21.569 align:start position:0% [Applause] all<00:04:19.060> right<00:04:19.650> thank<00:04:20.650> you<00:04:20.680> very<00:04:20.739> much<00:04:20.980> for<00:04:21.220> the 00:04:21.569 --> 00:04:21.579 align:start position:0% all right thank you very much for the 00:04:21.579 --> 00:04:23.340 align:start position:0% all right thank you very much for the chance<00:04:21.790> to<00:04:21.850> present<00:04:22.180> my<00:04:22.930> name<00:04:23.050> is<00:04:23.140> Javier 00:04:23.340 --> 00:04:23.350 align:start position:0% chance to present my name is Javier 00:04:23.350 --> 00:04:25.260 align:start position:0% chance to present my name is Javier played<00:04:23.530> here<00:04:23.680> I'm<00:04:24.220> the<00:04:24.400> city<00:04:24.520> of<00:04:24.760> epic<00:04:25.090> laughs 00:04:25.260 --> 00:04:25.270 align:start position:0% played here I'm the city of epic laughs 00:04:25.270 --> 00:04:28.710 align:start position:0% played here I'm the city of epic laughs I've<00:04:26.110> been<00:04:26.220> contributing<00:04:27.220> to<00:04:27.790> the<00:04:28.420> swarm 00:04:28.710 --> 00:04:28.720 align:start position:0% I've been contributing to the swarm 00:04:28.720 --> 00:04:33.240 align:start position:0% I've been contributing to the swarm since<00:04:29.080> since<00:04:30.070> May<00:04:30.250> since<00:04:30.700> this<00:04:30.940> May<00:04:31.470> and<00:04:32.470> today 00:04:33.240 --> 00:04:33.250 align:start position:0% since since May since this May and today 00:04:33.250 --> 00:04:34.500 align:start position:0% since since May since this May and today I'm<00:04:33.310> gonna<00:04:33.430> introduce<00:04:33.520> you<00:04:33.820> to<00:04:34.180> one<00:04:34.330> of<00:04:34.420> the 00:04:34.500 --> 00:04:34.510 align:start position:0% I'm gonna introduce you to one of the 00:04:34.510 --> 00:04:36.390 align:start position:0% I'm gonna introduce you to one of the features<00:04:34.780> that<00:04:34.840> I<00:04:34.960> worked<00:04:35.230> with<00:04:35.350> with<00:04:36.340> the 00:04:36.390 --> 00:04:36.400 align:start position:0% features that I worked with with the 00:04:36.400 --> 00:04:40.650 align:start position:0% features that I worked with with the rest<00:04:36.550> of<00:04:36.610> the<00:04:36.700> team<00:04:36.850> called<00:04:37.450> from<00:04:37.720> Fitz<00:04:39.660> so 00:04:40.650 --> 00:04:40.660 align:start position:0% rest of the team called from Fitz so 00:04:40.660 --> 00:04:44.730 align:start position:0% rest of the team called from Fitz so what<00:04:41.440> are<00:04:41.560> some<00:04:41.590> fits<00:04:42.210> in<00:04:43.210> a<00:04:43.420> in<00:04:43.720> a<00:04:43.840> nutshell<00:04:44.020> so 00:04:44.730 --> 00:04:44.740 align:start position:0% what are some fits in a in a nutshell so 00:04:44.740 --> 00:04:48.900 align:start position:0% what are some fits in a in a nutshell so as<00:04:45.010> a<00:04:46.380> as<00:04:47.380> a<00:04:47.440> summary<00:04:47.830> is<00:04:48.100> a<00:04:48.160> way<00:04:48.430> to<00:04:48.490> update 00:04:48.900 --> 00:04:48.910 align:start position:0% as a as a summary is a way to update 00:04:48.910 --> 00:04:52.770 align:start position:0% as a as a summary is a way to update content<00:04:49.480> in<00:04:49.690> swarm<00:04:50.020> okay<00:04:51.450> so<00:04:52.450> it's<00:04:52.660> a 00:04:52.770 --> 00:04:52.780 align:start position:0% content in swarm okay so it's a 00:04:52.780 --> 00:04:55.980 align:start position:0% content in swarm okay so it's a publisher<00:04:53.590> subscriber<00:04:54.160> system<00:04:54.669> okay<00:04:55.150> where 00:04:55.980 --> 00:04:55.990 align:start position:0% publisher subscriber system okay where 00:04:55.990 --> 00:04:57.840 align:start position:0% publisher subscriber system okay where you<00:04:56.080> can<00:04:56.230> post<00:04:56.380> updates<00:04:56.800> about<00:04:56.950> a<00:04:57.100> topic<00:04:57.340> and 00:04:57.840 --> 00:04:57.850 align:start position:0% you can post updates about a topic and 00:04:57.850 --> 00:05:00.930 align:start position:0% you can post updates about a topic and then<00:04:58.390> also<00:04:59.020> read<00:04:59.200> others<00:04:59.580> others<00:05:00.580> updates 00:05:00.930 --> 00:05:00.940 align:start position:0% then also read others others updates 00:05:00.940 --> 00:05:02.970 align:start position:0% then also read others others updates about<00:05:01.210> that<00:05:01.360> topic<00:05:01.570> okay<00:05:02.080> and<00:05:02.650> you<00:05:02.740> can<00:05:02.860> also 00:05:02.970 --> 00:05:02.980 align:start position:0% about that topic okay and you can also 00:05:02.980 --> 00:05:05.280 align:start position:0% about that topic okay and you can also retrieve<00:05:03.310> all<00:05:04.270> their<00:05:04.540> values<00:05:04.840> for<00:05:05.110> those 00:05:05.280 --> 00:05:05.290 align:start position:0% retrieve all their values for those 00:05:05.290 --> 00:05:09.000 align:start position:0% retrieve all their values for those posts<00:05:06.130> and<00:05:07.090> you<00:05:07.360> can<00:05:07.510> do<00:05:07.630> all<00:05:07.900> of<00:05:07.930> that<00:05:08.140> without 00:05:09.000 --> 00:05:09.010 align:start position:0% posts and you can do all of that without 00:05:09.010 --> 00:05:16.010 align:start position:0% posts and you can do all of that without any<00:05:09.340> single<00:05:11.040> blockchain<00:05:12.040> transaction<00:05:12.550> okay 00:05:16.010 --> 00:05:16.020 align:start position:0% 00:05:16.020 --> 00:05:18.840 align:start position:0% working<00:05:17.100> okay<00:05:18.100> so<00:05:18.160> you<00:05:18.340> can<00:05:18.550> think<00:05:18.760> about 00:05:18.840 --> 00:05:18.850 align:start position:0% working okay so you can think about 00:05:18.850 --> 00:05:22.980 align:start position:0% working okay so you can think about feeds<00:05:19.860> as<00:05:20.860> a<00:05:20.919> key<00:05:21.250> value<00:05:21.370> store<00:05:21.850> okay<00:05:22.450> where 00:05:22.980 --> 00:05:22.990 align:start position:0% feeds as a key value store okay where 00:05:22.990 --> 00:05:25.020 align:start position:0% feeds as a key value store okay where each<00:05:23.560> user<00:05:23.860> can<00:05:24.100> only<00:05:24.190> write<00:05:24.520> to<00:05:24.550> their<00:05:24.910> own 00:05:25.020 --> 00:05:25.030 align:start position:0% each user can only write to their own 00:05:25.030 --> 00:05:27.060 align:start position:0% each user can only write to their own key<00:05:25.270> space<00:05:25.570> okay<00:05:26.260> you<00:05:26.320> cannot<00:05:26.590> overwrite 00:05:27.060 --> 00:05:27.070 align:start position:0% key space okay you cannot overwrite 00:05:27.070 --> 00:05:30.719 align:start position:0% key space okay you cannot overwrite somebody<00:05:27.520> else's<00:05:28.229> value<00:05:29.229> okay<00:05:29.680> and<00:05:30.160> you<00:05:30.610> can 00:05:30.719 --> 00:05:30.729 align:start position:0% somebody else's value okay and you can 00:05:30.729 --> 00:05:33.120 align:start position:0% somebody else's value okay and you can read<00:05:30.910> your<00:05:31.330> own<00:05:31.390> values<00:05:31.810> okay<00:05:32.410> and<00:05:32.620> some<00:05:32.919> and 00:05:33.120 --> 00:05:33.130 align:start position:0% read your own values okay and some and 00:05:33.130 --> 00:05:34.830 align:start position:0% read your own values okay and some and everybody<00:05:33.550> else's<00:05:33.850> values<00:05:34.180> provided<00:05:34.780> that 00:05:34.830 --> 00:05:34.840 align:start position:0% everybody else's values provided that 00:05:34.840 --> 00:05:37.650 align:start position:0% everybody else's values provided that you<00:05:34.960> know<00:05:35.190> their<00:05:36.190> address<00:05:36.310> and<00:05:37.180> the<00:05:37.390> topic 00:05:37.650 --> 00:05:37.660 align:start position:0% you know their address and the topic 00:05:37.660 --> 00:05:39.719 align:start position:0% you know their address and the topic they<00:05:37.780> are<00:05:37.810> posting<00:05:38.200> at<00:05:38.500> and<00:05:39.340> you<00:05:39.460> can<00:05:39.580> also 00:05:39.719 --> 00:05:39.729 align:start position:0% they are posting at and you can also 00:05:39.729 --> 00:05:41.010 align:start position:0% they are posting at and you can also retrieve<00:05:40.030> all<00:05:40.300> their<00:05:40.479> versions<00:05:40.810> of<00:05:40.900> the 00:05:41.010 --> 00:05:41.020 align:start position:0% retrieve all their versions of the 00:05:41.020 --> 00:05:42.870 align:start position:0% retrieve all their versions of the values<00:05:41.229> that<00:05:41.260> you<00:05:41.380> post<00:05:41.650> okay<00:05:42.280> and<00:05:42.460> you<00:05:42.550> can<00:05:42.669> do 00:05:42.870 --> 00:05:42.880 align:start position:0% values that you post okay and you can do 00:05:42.880 --> 00:05:47.040 align:start position:0% values that you post okay and you can do all<00:05:43.000> this<00:05:43.240> without<00:05:45.180> any<00:05:46.180> serum<00:05:46.540> transaction 00:05:47.040 --> 00:05:47.050 align:start position:0% all this without any serum transaction 00:05:47.050 --> 00:05:50.840 align:start position:0% all this without any serum transaction okay<00:05:47.590> so<00:05:48.400> this<00:05:48.580> opens<00:05:49.030> up<00:05:49.210> the<00:05:49.419> door<00:05:49.810> to<00:05:50.140> many 00:05:50.840 --> 00:05:50.850 align:start position:0% okay so this opens up the door to many 00:05:50.850 --> 00:05:53.760 align:start position:0% okay so this opens up the door to many dubs<00:05:51.850> okay<00:05:52.450> that<00:05:52.660> do<00:05:53.110> not<00:05:53.229> have<00:05:53.380> to<00:05:53.500> do<00:05:53.590> any 00:05:53.760 --> 00:05:53.770 align:start position:0% dubs okay that do not have to do any 00:05:53.770 --> 00:05:56.700 align:start position:0% dubs okay that do not have to do any turn<00:05:53.890> instructions<00:05:54.100> at<00:05:54.430> all<00:05:55.200> okay<00:05:56.200> so 00:05:56.700 --> 00:05:56.710 align:start position:0% turn instructions at all okay so 00:05:56.710 --> 00:05:58.350 align:start position:0% turn instructions at all okay so applications<00:05:57.310> that<00:05:57.490> we<00:05:57.610> can<00:05:57.640> we<00:05:58.000> can<00:05:58.030> alter 00:05:58.350 --> 00:05:58.360 align:start position:0% applications that we can we can alter 00:05:58.360 --> 00:06:01.980 align:start position:0% applications that we can we can alter alter<00:05:58.780> continue<00:05:59.350> on<00:05:59.590> without<00:05:59.740> ens<00:06:00.310> okay<00:06:01.120> you 00:06:01.980 --> 00:06:01.990 align:start position:0% alter continue on without ens okay you 00:06:01.990 --> 00:06:04.140 align:start position:0% alter continue on without ens okay you can<00:06:02.140> use<00:06:02.260> ens<00:06:02.620> as<00:06:03.160> well<00:06:03.430> but<00:06:03.610> you<00:06:03.850> don't<00:06:04.000> have 00:06:04.140 --> 00:06:04.150 align:start position:0% can use ens as well but you don't have 00:06:04.150 --> 00:06:06.390 align:start position:0% can use ens as well but you don't have to<00:06:04.300> you<00:06:04.960> can<00:06:04.990> enable<00:06:05.410> taps<00:06:05.830> to<00:06:06.100> persist 00:06:06.390 --> 00:06:06.400 align:start position:0% to you can enable taps to persist 00:06:06.400 --> 00:06:08.640 align:start position:0% to you can enable taps to persist content<00:06:06.700> easily<00:06:06.880> so<00:06:07.540> from<00:06:07.780> the<00:06:07.870> browser<00:06:08.050> your 00:06:08.640 --> 00:06:08.650 align:start position:0% content easily so from the browser your 00:06:08.650 --> 00:06:11.010 align:start position:0% content easily so from the browser your browser<00:06:08.830> application<00:06:09.340> called<00:06:09.490> safe<00:06:09.760> to<00:06:10.750> swarm 00:06:11.010 --> 00:06:11.020 align:start position:0% browser application called safe to swarm 00:06:11.020 --> 00:06:14.250 align:start position:0% browser application called safe to swarm some<00:06:11.410> value<00:06:11.680> and<00:06:11.890> retrieve<00:06:12.190> it<00:06:12.280> later<00:06:13.260> you 00:06:14.250 --> 00:06:14.260 align:start position:0% some value and retrieve it later you 00:06:14.260 --> 00:06:16.860 align:start position:0% some value and retrieve it later you could<00:06:14.440> use<00:06:14.680> it<00:06:14.830> to<00:06:14.860> improve<00:06:15.870> communication 00:06:16.860 --> 00:06:16.870 align:start position:0% could use it to improve communication 00:06:16.870 --> 00:06:18.630 align:start position:0% could use it to improve communication protocol<00:06:17.229> among<00:06:17.350> your<00:06:17.590> applications<00:06:18.070> and 00:06:18.630 --> 00:06:18.640 align:start position:0% protocol among your applications and 00:06:18.640 --> 00:06:20.670 align:start position:0% protocol among your applications and also<00:06:19.000> a<00:06:19.030> iot<00:06:19.810> devices<00:06:19.840> could<00:06:20.440> push 00:06:20.670 --> 00:06:20.680 align:start position:0% also a iot devices could push 00:06:20.680 --> 00:06:23.490 align:start position:0% also a iot devices could push information<00:06:21.040> to<00:06:21.460> swarm<00:06:21.780> just<00:06:22.780> by<00:06:23.080> holding<00:06:23.260> a 00:06:23.490 --> 00:06:23.500 align:start position:0% information to swarm just by holding a 00:06:23.500 --> 00:06:26.040 align:start position:0% information to swarm just by holding a private<00:06:23.680> key<00:06:24.010> and<00:06:24.849> that's<00:06:25.240> it<00:06:25.390> okay<00:06:25.720> not<00:06:25.930> it 00:06:26.040 --> 00:06:26.050 align:start position:0% private key and that's it okay not it 00:06:26.050 --> 00:06:27.030 align:start position:0% private key and that's it okay not it not<00:06:26.200> even<00:06:26.470> ether 00:06:27.030 --> 00:06:27.040 align:start position:0% not even ether 00:06:27.040 --> 00:06:30.840 align:start position:0% not even ether not<00:06:27.160> private<00:06:27.460> key<00:06:28.650> so<00:06:29.650> how<00:06:29.860> does<00:06:30.220> from<00:06:30.670> feet 00:06:30.840 --> 00:06:30.850 align:start position:0% not private key so how does from feet 00:06:30.850 --> 00:06:33.840 align:start position:0% not private key so how does from feet work<00:06:31.570> okay<00:06:32.110> to<00:06:32.710> push<00:06:32.950> to<00:06:33.160> a<00:06:33.190> certain<00:06:33.520> feed<00:06:33.670> you 00:06:33.840 --> 00:06:33.850 align:start position:0% work okay to push to a certain feed you 00:06:33.850 --> 00:06:35.460 align:start position:0% work okay to push to a certain feed you need<00:06:34.000> just<00:06:34.150> two<00:06:34.390> things<00:06:34.570> you<00:06:34.930> need<00:06:35.020> a<00:06:35.140> private 00:06:35.460 --> 00:06:35.470 align:start position:0% need just two things you need a private 00:06:35.470 --> 00:06:39.720 align:start position:0% need just two things you need a private key<00:06:35.620> and<00:06:36.690> you<00:06:37.690> need<00:06:37.810> a<00:06:37.900> topic<00:06:38.200> to<00:06:38.530> post<00:06:38.770> that 00:06:39.720 --> 00:06:39.730 align:start position:0% key and you need a topic to post that 00:06:39.730 --> 00:06:42.960 align:start position:0% key and you need a topic to post that information<00:06:40.300> under<00:06:40.540> okay<00:06:41.140> I<00:06:42.130> didn't<00:06:42.700> say<00:06:42.820> that 00:06:42.960 --> 00:06:42.970 align:start position:0% information under okay I didn't say that 00:06:42.970 --> 00:06:44.850 align:start position:0% information under okay I didn't say that you<00:06:43.030> need<00:06:43.210> ethers<00:06:43.480> to<00:06:43.690> post<00:06:44.020> that<00:06:44.260> update<00:06:44.560> just 00:06:44.850 --> 00:06:44.860 align:start position:0% you need ethers to post that update just 00:06:44.860 --> 00:06:48.480 align:start position:0% you need ethers to post that update just a<00:06:45.130> private<00:06:46.000> key<00:06:46.150> that<00:06:46.390> you<00:06:46.480> can<00:06:46.600> generate<00:06:47.490> but 00:06:48.480 --> 00:06:48.490 align:start position:0% a private key that you can generate but 00:06:48.490 --> 00:06:50.220 align:start position:0% a private key that you can generate but and<00:06:48.730> to<00:06:48.940> read<00:06:49.090> a<00:06:49.240> certain<00:06:49.450> feed<00:06:49.660> the<00:06:50.080> only 00:06:50.220 --> 00:06:50.230 align:start position:0% and to read a certain feed the only 00:06:50.230 --> 00:06:53.010 align:start position:0% and to read a certain feed the only thing<00:06:50.410> that<00:06:50.680> you<00:06:50.770> need<00:06:50.890> is<00:06:51.070> the<00:06:51.640> users<00:06:52.000> et<00:06:52.720> Rome 00:06:53.010 --> 00:06:53.020 align:start position:0% thing that you need is the users et Rome 00:06:53.020 --> 00:06:54.510 align:start position:0% thing that you need is the users et Rome address<00:06:53.320> that<00:06:53.590> you<00:06:53.680> would<00:06:53.800> be<00:06:53.920> reading<00:06:54.190> the 00:06:54.510 --> 00:06:54.520 align:start position:0% address that you would be reading the 00:06:54.520 --> 00:06:56.850 align:start position:0% address that you would be reading the feet<00:06:54.760> from<00:06:54.940> and<00:06:55.300> the<00:06:55.900> topic<00:06:56.200> under<00:06:56.320> which<00:06:56.620> that 00:06:56.850 --> 00:06:56.860 align:start position:0% feet from and the topic under which that 00:06:56.860 --> 00:06:58.410 align:start position:0% feet from and the topic under which that user<00:06:57.070> is<00:06:57.370> posting<00:06:57.730> information<00:06:58.210> and 00:06:58.410 --> 00:06:58.420 align:start position:0% user is posting information and 00:06:58.420 --> 00:07:01.620 align:start position:0% user is posting information and optionally<00:06:59.610> if<00:07:00.610> you<00:07:00.760> want<00:07:00.970> you<00:07:01.270> can<00:07:01.390> provide 00:07:01.620 --> 00:07:01.630 align:start position:0% optionally if you want you can provide 00:07:01.630 --> 00:07:03.450 align:start position:0% optionally if you want you can provide also<00:07:01.810> timestamp<00:07:02.380> which<00:07:02.650> would<00:07:02.890> allow<00:07:03.100> you<00:07:03.160> to 00:07:03.450 --> 00:07:03.460 align:start position:0% also timestamp which would allow you to 00:07:03.460 --> 00:07:05.940 align:start position:0% also timestamp which would allow you to retrieve<00:07:04.090> data<00:07:04.360> in<00:07:04.840> the<00:07:05.050> past<00:07:05.170> okay<00:07:05.620> all<00:07:05.800> their 00:07:05.940 --> 00:07:05.950 align:start position:0% retrieve data in the past okay all their 00:07:05.950 --> 00:07:07.500 align:start position:0% retrieve data in the past okay all their values<00:07:06.220> for<00:07:06.400> that<00:07:06.550> key<00:07:06.760> you<00:07:07.090> could<00:07:07.180> retrieve 00:07:07.500 --> 00:07:07.510 align:start position:0% values for that key you could retrieve 00:07:07.510 --> 00:07:10.950 align:start position:0% values for that key you could retrieve as<00:07:07.600> well<00:07:08.220> so<00:07:09.220> just<00:07:09.700> to<00:07:10.030> put<00:07:10.150> up<00:07:10.300> an<00:07:10.480> example 00:07:10.950 --> 00:07:10.960 align:start position:0% as well so just to put up an example 00:07:10.960 --> 00:07:14.330 align:start position:0% as well so just to put up an example let's<00:07:11.320> imagine<00:07:11.530> that<00:07:11.740> we<00:07:12.700> have<00:07:12.880> these<00:07:13.030> sets<00:07:13.300> of 00:07:14.330 --> 00:07:14.340 align:start position:0% let's imagine that we have these sets of 00:07:14.340 --> 00:07:18.570 align:start position:0% let's imagine that we have these sets of of<00:07:15.340> topics<00:07:15.930> on<00:07:16.930> the<00:07:17.080> left<00:07:17.260> for<00:07:17.860> example<00:07:18.250> other 00:07:18.570 --> 00:07:18.580 align:start position:0% of topics on the left for example other 00:07:18.580 --> 00:07:20.040 align:start position:0% of topics on the left for example other it<00:07:18.700> could<00:07:18.790> be<00:07:18.940> avatar 00:07:20.040 --> 00:07:20.050 align:start position:0% it could be avatar 00:07:20.050 --> 00:07:21.900 align:start position:0% it could be avatar another<00:07:20.920> topic<00:07:21.160> could<00:07:21.280> be<00:07:21.430> local<00:07:21.700> weather 00:07:21.900 --> 00:07:21.910 align:start position:0% another topic could be local weather 00:07:21.910 --> 00:07:23.820 align:start position:0% another topic could be local weather another<00:07:22.240> topic<00:07:22.510> could<00:07:22.600> be<00:07:22.750> website<00:07:23.230> and<00:07:23.440> then 00:07:23.820 --> 00:07:23.830 align:start position:0% another topic could be website and then 00:07:23.830 --> 00:07:26.880 align:start position:0% another topic could be website and then we<00:07:23.860> have<00:07:24.070> publishers<00:07:24.970> or<00:07:25.540> users<00:07:25.960> on<00:07:26.320> top<00:07:26.740> you 00:07:26.880 --> 00:07:26.890 align:start position:0% we have publishers or users on top you 00:07:26.890 --> 00:07:29.250 align:start position:0% we have publishers or users on top you know<00:07:27.010> if<00:07:27.160> you're<00:07:27.280> a<00:07:27.430> user<00:07:27.670> be<00:07:27.940> and<00:07:28.210> user<00:07:28.420> see<00:07:28.570> so 00:07:29.250 --> 00:07:29.260 align:start position:0% know if you're a user be and user see so 00:07:29.260 --> 00:07:33.090 align:start position:0% know if you're a user be and user see so in<00:07:29.440> this<00:07:29.560> case<00:07:29.770> for<00:07:29.950> example<00:07:30.600> user<00:07:31.600> a<00:07:32.100> has 00:07:33.090 --> 00:07:33.100 align:start position:0% in this case for example user a has 00:07:33.100 --> 00:07:37.350 align:start position:0% in this case for example user a has posted<00:07:33.640> an<00:07:34.060> update<00:07:35.700> under<00:07:36.700> the<00:07:36.820> avatar<00:07:37.180> key 00:07:37.350 --> 00:07:37.360 align:start position:0% posted an update under the avatar key 00:07:37.360 --> 00:07:40.190 align:start position:0% posted an update under the avatar key and<00:07:37.630> the<00:07:37.810> update<00:07:38.050> is<00:07:38.170> well<00:07:38.730> her<00:07:39.730> profile 00:07:40.190 --> 00:07:40.200 align:start position:0% and the update is well her profile 00:07:40.200 --> 00:07:43.860 align:start position:0% and the update is well her profile information<00:07:41.200> here<00:07:41.920> profile<00:07:42.310> picture<00:07:42.580> so<00:07:43.300> if 00:07:43.860 --> 00:07:43.870 align:start position:0% information here profile picture so if 00:07:43.870 --> 00:07:46.320 align:start position:0% information here profile picture so if we<00:07:44.020> will<00:07:44.620> use<00:07:44.830> the<00:07:45.340> query<00:07:45.550> feed 00:07:46.320 --> 00:07:46.330 align:start position:0% we will use the query feed 00:07:46.330 --> 00:07:49.200 align:start position:0% we will use the query feed primitive<00:07:47.430> instruments<00:07:48.430> we<00:07:48.790> can<00:07:48.940> retrieve 00:07:49.200 --> 00:07:49.210 align:start position:0% primitive instruments we can retrieve 00:07:49.210 --> 00:07:52.290 align:start position:0% primitive instruments we can retrieve that<00:07:50.200> value<00:07:50.590> that<00:07:50.920> she<00:07:51.490> has<00:07:51.610> posted<00:07:51.850> which<00:07:52.150> is 00:07:52.290 --> 00:07:52.300 align:start position:0% that value that she has posted which is 00:07:52.300 --> 00:07:55.740 align:start position:0% that value that she has posted which is her<00:07:53.020> picture<00:07:53.230> okay<00:07:54.120> if<00:07:55.120> the<00:07:55.330> next<00:07:55.510> day<00:07:55.690> for 00:07:55.740 --> 00:07:55.750 align:start position:0% her picture okay if the next day for 00:07:55.750 --> 00:07:58.710 align:start position:0% her picture okay if the next day for example<00:07:56.520> she<00:07:57.520> updates<00:07:57.850> her<00:07:58.060> profile<00:07:58.420> picture 00:07:58.710 --> 00:07:58.720 align:start position:0% example she updates her profile picture 00:07:58.720 --> 00:08:02.760 align:start position:0% example she updates her profile picture the<00:07:59.440> same<00:07:59.980> primitive<00:08:00.940> code<00:08:01.360> which<00:08:02.110> is<00:08:02.260> a<00:08:02.470> query 00:08:02.760 --> 00:08:02.770 align:start position:0% the same primitive code which is a query 00:08:02.770 --> 00:08:05.280 align:start position:0% the same primitive code which is a query field<00:08:02.920> would<00:08:03.490> return<00:08:03.850> the<00:08:04.090> new<00:08:04.510> picture<00:08:05.110> but 00:08:05.280 --> 00:08:05.290 align:start position:0% field would return the new picture but 00:08:05.290 --> 00:08:08.340 align:start position:0% field would return the new picture but if<00:08:05.410> we<00:08:05.560> provide<00:08:05.890> a<00:08:06.730> timestamp<00:08:07.570> in<00:08:07.810> the<00:08:07.930> past<00:08:08.110> we 00:08:08.340 --> 00:08:08.350 align:start position:0% if we provide a timestamp in the past we 00:08:08.350 --> 00:08:10.320 align:start position:0% if we provide a timestamp in the past we can<00:08:08.470> retrieve<00:08:08.650> the<00:08:08.860> older<00:08:09.070> picture<00:08:10.030> as<00:08:10.180> well 00:08:10.320 --> 00:08:10.330 align:start position:0% can retrieve the older picture as well 00:08:10.330 --> 00:08:13.560 align:start position:0% can retrieve the older picture as well okay<00:08:10.810> so<00:08:11.440> this<00:08:11.560> enables<00:08:11.980> again<00:08:12.610> ended<00:08:13.180> up<00:08:13.330> to 00:08:13.560 --> 00:08:13.570 align:start position:0% okay so this enables again ended up to 00:08:13.570 --> 00:08:15.780 align:start position:0% okay so this enables again ended up to interact<00:08:14.380> with<00:08:14.440> farm<00:08:14.800> in<00:08:14.890> this<00:08:15.010> way<00:08:15.130> to<00:08:15.580> save 00:08:15.780 --> 00:08:15.790 align:start position:0% interact with farm in this way to save 00:08:15.790 --> 00:08:18.140 align:start position:0% interact with farm in this way to save information<00:08:15.970> and<00:08:16.480> the<00:08:16.540> polish<00:08:16.780> information 00:08:18.140 --> 00:08:18.150 align:start position:0% information and the polish information 00:08:18.150 --> 00:08:21.300 align:start position:0% information and the polish information okay<00:08:19.150> so<00:08:19.210> how<00:08:19.630> would<00:08:19.690> this<00:08:20.020> work<00:08:20.080> if<00:08:20.560> we<00:08:21.160> want 00:08:21.300 --> 00:08:21.310 align:start position:0% okay so how would this work if we want 00:08:21.310 --> 00:08:23.070 align:start position:0% okay so how would this work if we want to<00:08:21.430> use<00:08:21.670> this<00:08:21.850> to<00:08:22.210> publish<00:08:22.480> our<00:08:22.570> website<00:08:22.900> it's 00:08:23.070 --> 00:08:23.080 align:start position:0% to use this to publish our website it's 00:08:23.080 --> 00:08:24.390 align:start position:0% to use this to publish our website it's not<00:08:23.230> the<00:08:23.350> only<00:08:23.500> application<00:08:23.740> but<00:08:24.040> imagine 00:08:24.390 --> 00:08:24.400 align:start position:0% not the only application but imagine 00:08:24.400 --> 00:08:26.820 align:start position:0% not the only application but imagine that<00:08:24.520> we<00:08:24.580> want<00:08:24.760> to<00:08:24.850> use<00:08:24.970> it<00:08:25.120> to<00:08:25.590> update<00:08:26.590> that 00:08:26.820 --> 00:08:26.830 align:start position:0% that we want to use it to update that 00:08:26.830 --> 00:08:29.100 align:start position:0% that we want to use it to update that website<00:08:27.190> as<00:08:27.610> of<00:08:27.790> today<00:08:28.060> when<00:08:28.720> we<00:08:28.840> want<00:08:29.020> to 00:08:29.100 --> 00:08:29.110 align:start position:0% website as of today when we want to 00:08:29.110 --> 00:08:32.460 align:start position:0% website as of today when we want to publish<00:08:29.380> a<00:08:29.470> website<00:08:29.830> with<00:08:30.790> ens<00:08:31.210> what<00:08:32.200> we<00:08:32.320> have 00:08:32.460 --> 00:08:32.470 align:start position:0% publish a website with ens what we have 00:08:32.470 --> 00:08:34.710 align:start position:0% publish a website with ens what we have to<00:08:32.560> do<00:08:32.680> is<00:08:32.800> upload<00:08:32.950> the<00:08:33.220> content<00:08:33.550> to<00:08:33.610> form<00:08:33.849> and 00:08:34.710 --> 00:08:34.720 align:start position:0% to do is upload the content to form and 00:08:34.720 --> 00:08:36.839 align:start position:0% to do is upload the content to form and get<00:08:34.900> a<00:08:34.930> hash<00:08:35.140> out<00:08:35.349> of<00:08:35.530> that<00:08:35.650> and<00:08:35.800> then<00:08:36.219> we<00:08:36.400> do<00:08:36.700> an 00:08:36.839 --> 00:08:36.849 align:start position:0% get a hash out of that and then we do an 00:08:36.849 --> 00:08:38.370 align:start position:0% get a hash out of that and then we do an on<00:08:37.000> chain<00:08:37.210> transaction<00:08:37.750> to<00:08:37.900> part<00:08:38.080> with<00:08:38.200> their 00:08:38.370 --> 00:08:38.380 align:start position:0% on chain transaction to part with their 00:08:38.380 --> 00:08:39.480 align:start position:0% on chain transaction to part with their cash<00:08:38.410> and 00:08:39.480 --> 00:08:39.490 align:start position:0% cash and 00:08:39.490 --> 00:08:41.190 align:start position:0% cash and that<00:08:39.940> way<00:08:40.090> everybody<00:08:40.480> can<00:08:40.540> reach<00:08:40.780> the<00:08:40.870> content 00:08:41.190 --> 00:08:41.200 align:start position:0% that way everybody can reach the content 00:08:41.200 --> 00:08:43.860 align:start position:0% that way everybody can reach the content by<00:08:41.350> the<00:08:41.380> name<00:08:41.970> but<00:08:42.970> then<00:08:43.120> the<00:08:43.450> problem<00:08:43.750> is<00:08:43.810> that 00:08:43.860 --> 00:08:43.870 align:start position:0% by the name but then the problem is that 00:08:43.870 --> 00:08:47.310 align:start position:0% by the name but then the problem is that we<00:08:44.200> want<00:08:44.530> to<00:08:44.590> update<00:08:44.920> the<00:08:45.250> site<00:08:45.720> we<00:08:46.720> need<00:08:47.170> to 00:08:47.310 --> 00:08:47.320 align:start position:0% we want to update the site we need to 00:08:47.320 --> 00:08:48.840 align:start position:0% we want to update the site we need to publish<00:08:47.590> the<00:08:47.740> new<00:08:47.860> hash<00:08:48.130> and<00:08:48.400> that<00:08:48.640> means 00:08:48.840 --> 00:08:48.850 align:start position:0% publish the new hash and that means 00:08:48.850 --> 00:08:51.000 align:start position:0% publish the new hash and that means going<00:08:48.970> again<00:08:49.360> to<00:08:49.510> ENS<00:08:49.840> and<00:08:49.960> update<00:08:50.620> the<00:08:50.740> condom 00:08:51.000 --> 00:08:51.010 align:start position:0% going again to ENS and update the condom 00:08:51.010 --> 00:08:53.370 align:start position:0% going again to ENS and update the condom has<00:08:51.190> which<00:08:51.490> is<00:08:51.540> another<00:08:52.540> transaction<00:08:52.840> cost 00:08:53.370 --> 00:08:53.380 align:start position:0% has which is another transaction cost 00:08:53.380 --> 00:08:55.290 align:start position:0% has which is another transaction cost okay<00:08:53.830> so<00:08:54.400> it<00:08:54.490> means<00:08:54.640> that<00:08:54.760> every<00:08:54.910> time<00:08:54.940> we 00:08:55.290 --> 00:08:55.300 align:start position:0% okay so it means that every time we 00:08:55.300 --> 00:08:56.880 align:start position:0% okay so it means that every time we update<00:08:55.450> we<00:08:55.810> have<00:08:55.840> to<00:08:56.020> pay<00:08:56.140> a<00:08:56.170> transaction<00:08:56.530> cost 00:08:56.880 --> 00:08:56.890 align:start position:0% update we have to pay a transaction cost 00:08:56.890 --> 00:09:00.120 align:start position:0% update we have to pay a transaction cost withdrawn<00:08:57.550> feeds<00:08:57.760> this<00:08:58.690> is<00:08:58.870> simplified<00:08:59.440> in<00:09:00.010> a 00:09:00.120 --> 00:09:00.130 align:start position:0% withdrawn feeds this is simplified in a 00:09:00.130 --> 00:09:04.800 align:start position:0% withdrawn feeds this is simplified in a way<00:09:00.280> that<00:09:00.840> you<00:09:01.840> only<00:09:02.110> have<00:09:02.560> to<00:09:02.710> do<00:09:02.830> a<00:09:03.330> one<00:09:04.330> en<00:09:04.690> s 00:09:04.800 --> 00:09:04.810 align:start position:0% way that you only have to do a one en s 00:09:04.810 --> 00:09:07.140 align:start position:0% way that you only have to do a one en s transaction<00:09:05.350> just<00:09:05.530> to<00:09:05.710> have<00:09:06.370> that<00:09:06.400> en<00:09:06.790> s<00:09:06.910> trans 00:09:07.140 --> 00:09:07.150 align:start position:0% transaction just to have that en s trans 00:09:07.150 --> 00:09:09.810 align:start position:0% transaction just to have that en s trans NS<00:09:07.990> record<00:09:08.500> my<00:09:08.950> site<00:09:09.190> dot<00:09:09.370> if<00:09:09.550> for<00:09:09.760> example 00:09:09.810 --> 00:09:09.820 align:start position:0% NS record my site dot if for example 00:09:09.820 --> 00:09:12.750 align:start position:0% NS record my site dot if for example point<00:09:10.740> to<00:09:11.740> the<00:09:11.860> feed<00:09:12.040> instead<00:09:12.340> of<00:09:12.550> to<00:09:12.670> the 00:09:12.750 --> 00:09:12.760 align:start position:0% point to the feed instead of to the 00:09:12.760 --> 00:09:14.790 align:start position:0% point to the feed instead of to the direct<00:09:13.120> content<00:09:13.510> and<00:09:13.660> that<00:09:14.050> way<00:09:14.230> every<00:09:14.770> time 00:09:14.790 --> 00:09:14.800 align:start position:0% direct content and that way every time 00:09:14.800 --> 00:09:16.260 align:start position:0% direct content and that way every time that<00:09:15.040> you<00:09:15.100> want<00:09:15.220> to<00:09:15.340> update<00:09:15.550> the<00:09:15.640> site<00:09:15.820> the 00:09:16.260 --> 00:09:16.270 align:start position:0% that you want to update the site the 00:09:16.270 --> 00:09:18.660 align:start position:0% that you want to update the site the only<00:09:16.390> thing<00:09:16.540> that<00:09:16.690> you<00:09:16.750> need<00:09:16.900> to<00:09:16.930> do<00:09:17.140> is<00:09:17.500> to<00:09:17.800> to 00:09:18.660 --> 00:09:18.670 align:start position:0% only thing that you need to do is to to 00:09:18.670 --> 00:09:20.610 align:start position:0% only thing that you need to do is to to update<00:09:18.940> the<00:09:19.060> feed<00:09:19.210> instead<00:09:19.570> of<00:09:19.750> to<00:09:19.900> update<00:09:20.320> the 00:09:20.610 --> 00:09:20.620 align:start position:0% update the feed instead of to update the 00:09:20.620 --> 00:09:23.310 align:start position:0% update the feed instead of to update the contract<00:09:21.010> so<00:09:21.190> that<00:09:21.820> way<00:09:21.970> you<00:09:22.300> have<00:09:22.630> a<00:09:23.080> way<00:09:23.290> to 00:09:23.310 --> 00:09:23.320 align:start position:0% contract so that way you have a way to 00:09:23.320 --> 00:09:27.540 align:start position:0% contract so that way you have a way to have<00:09:24.220> data<00:09:24.400> site<00:09:24.730> without<00:09:25.030> having<00:09:25.450> to<00:09:25.570> pay<00:09:26.550> so 00:09:27.540 --> 00:09:27.550 align:start position:0% have data site without having to pay so 00:09:27.550 --> 00:09:33.540 align:start position:0% have data site without having to pay so meters<00:09:27.820> you<00:09:28.000> know<00:09:28.120> to<00:09:28.180> get<00:09:28.690> it<00:09:30.690> ok<00:09:31.690> so<00:09:32.250> the<00:09:33.250> key 00:09:33.540 --> 00:09:33.550 align:start position:0% meters you know to get it ok so the key 00:09:33.550 --> 00:09:35.640 align:start position:0% meters you know to get it ok so the key takeaway<00:09:33.910> here<00:09:33.940> is<00:09:34.270> you<00:09:34.930> can<00:09:35.080> update<00:09:35.350> content 00:09:35.640 --> 00:09:35.650 align:start position:0% takeaway here is you can update content 00:09:35.650 --> 00:09:37.860 align:start position:0% takeaway here is you can update content without<00:09:35.950> doing<00:09:36.160> transactions<00:09:36.730> and<00:09:37.600> you<00:09:37.630> can 00:09:37.860 --> 00:09:37.870 align:start position:0% without doing transactions and you can 00:09:37.870 --> 00:09:39.960 align:start position:0% without doing transactions and you can start<00:09:38.140> doing<00:09:38.230> that<00:09:38.500> now<00:09:38.830> because<00:09:39.670> this<00:09:39.820> is 00:09:39.960 --> 00:09:39.970 align:start position:0% start doing that now because this is 00:09:39.970 --> 00:09:41.880 align:start position:0% start doing that now because this is already<00:09:40.600> available<00:09:40.840> in<00:09:41.140> the<00:09:41.200> in<00:09:41.590> the<00:09:41.710> storm 00:09:41.880 --> 00:09:41.890 align:start position:0% already available in the in the storm 00:09:41.890 --> 00:09:44.370 align:start position:0% already available in the in the storm cluster<00:09:42.250> so<00:09:42.940> there's<00:09:43.180> the<00:09:43.780> front<00:09:43.960> guide<00:09:44.200> that 00:09:44.370 --> 00:09:44.380 align:start position:0% cluster so there's the front guide that 00:09:44.380 --> 00:09:45.780 align:start position:0% cluster so there's the front guide that explains<00:09:44.560> the<00:09:44.830> step-by-step<00:09:45.310> how<00:09:45.460> to<00:09:45.490> start 00:09:45.780 --> 00:09:45.790 align:start position:0% explains the step-by-step how to start 00:09:45.790 --> 00:09:47.520 align:start position:0% explains the step-by-step how to start messing<00:09:46.000> with<00:09:46.030> it<00:09:46.240> so<00:09:46.480> I<00:09:46.690> recommend<00:09:47.410> that<00:09:47.470> you 00:09:47.520 --> 00:09:47.530 align:start position:0% messing with it so I recommend that you 00:09:47.530 --> 00:09:50.640 align:start position:0% messing with it so I recommend that you guys<00:09:47.710> take<00:09:47.890> a<00:09:47.920> look<00:09:48.100> at<00:09:48.850> all<00:09:49.030> the<00:09:49.530> examples<00:09:50.530> in 00:09:50.640 --> 00:09:50.650 align:start position:0% guys take a look at all the examples in 00:09:50.650 --> 00:09:55.680 align:start position:0% guys take a look at all the examples in there<00:09:50.830> together<00:09:51.670> start<00:09:52.030> step-by-step<00:09:54.690> okay 00:09:55.680 --> 00:09:55.690 align:start position:0% there together start step-by-step okay 00:09:55.690 --> 00:09:58.130 align:start position:0% there together start step-by-step okay great 00:09:58.130 --> 00:09:58.140 align:start position:0% 00:09:58.140 --> 00:10:01.250 align:start position:0% yes<00:09:59.140> that<00:09:59.440> was<00:09:59.620> about<00:10:00.130> how<00:10:00.280> to<00:10:00.340> get<00:10:00.610> comped 00:10:01.250 --> 00:10:01.260 align:start position:0% yes that was about how to get comped 00:10:01.260 --> 00:10:03.720 align:start position:0% yes that was about how to get comped don't<00:10:02.260> dynamic<00:10:02.650> changing<00:10:03.070> data<00:10:03.250> in<00:10:03.460> swarm 00:10:03.720 --> 00:10:03.730 align:start position:0% don't dynamic changing data in swarm 00:10:03.730 --> 00:10:06.960 align:start position:0% don't dynamic changing data in swarm next<00:10:04.720> up<00:10:04.870> there<00:10:05.200> two<00:10:05.440> sections<00:10:05.860> are<00:10:06.070> by<00:10:06.280> Daniel 00:10:06.960 --> 00:10:06.970 align:start position:0% next up there two sections are by Daniel 00:10:06.970 --> 00:10:09.480 align:start position:0% next up there two sections are by Daniel he<00:10:07.660> will<00:10:07.810> talk<00:10:07.990> about<00:10:08.290> first<00:10:09.010> encryption 00:10:09.480 --> 00:10:09.490 align:start position:0% he will talk about first encryption 00:10:09.490 --> 00:10:11.010 align:start position:0% he will talk about first encryption which<00:10:09.670> is<00:10:09.820> the<00:10:09.940> low<00:10:10.060> level<00:10:10.090> encryption<00:10:10.630> of<00:10:10.930> all 00:10:11.010 --> 00:10:11.020 align:start position:0% which is the low level encryption of all 00:10:11.020 --> 00:10:12.600 align:start position:0% which is the low level encryption of all the<00:10:11.140> content<00:10:11.530> and<00:10:11.650> swarm<00:10:11.890> and<00:10:12.040> then<00:10:12.460> about 00:10:12.600 --> 00:10:12.610 align:start position:0% the content and swarm and then about 00:10:12.610 --> 00:10:14.340 align:start position:0% the content and swarm and then about access<00:10:13.060> control<00:10:13.450> which<00:10:13.630> is<00:10:13.780> making<00:10:13.960> sure<00:10:14.200> that 00:10:14.340 --> 00:10:14.350 align:start position:0% access control which is making sure that 00:10:14.350 --> 00:10:15.420 align:start position:0% access control which is making sure that only<00:10:14.410> the<00:10:14.680> right<00:10:14.710> people<00:10:15.100> with<00:10:15.250> the<00:10:15.280> right 00:10:15.420 --> 00:10:15.430 align:start position:0% only the right people with the right 00:10:15.430 --> 00:10:21.900 align:start position:0% only the right people with the right content<00:10:15.760> so<00:10:18.120> hello<00:10:19.120> everyone<00:10:19.920> so<00:10:20.920> I'm<00:10:21.550> going 00:10:21.900 --> 00:10:21.910 align:start position:0% content so hello everyone so I'm going 00:10:21.910 --> 00:10:26.460 align:start position:0% content so hello everyone so I'm going to<00:10:21.970> talk<00:10:22.330> about<00:10:23.880> how<00:10:24.880> you<00:10:24.940> store<00:10:25.570> confidential 00:10:26.460 --> 00:10:26.470 align:start position:0% to talk about how you store confidential 00:10:26.470 --> 00:10:30.750 align:start position:0% to talk about how you store confidential information<00:10:26.800> in<00:10:27.340> swarm<00:10:27.730> and<00:10:28.060> how<00:10:28.840> you<00:10:29.760> limit 00:10:30.750 --> 00:10:30.760 align:start position:0% information in swarm and how you limit 00:10:30.760 --> 00:10:35.360 align:start position:0% information in swarm and how you limit the<00:10:30.930> users<00:10:33.060> which<00:10:34.060> you<00:10:34.210> can<00:10:34.360> access<00:10:34.750> it<00:10:34.990> so 00:10:35.360 --> 00:10:35.370 align:start position:0% the users which you can access it so 00:10:35.370 --> 00:10:38.100 align:start position:0% the users which you can access it so confidential<00:10:36.370> information<00:10:36.670> is<00:10:37.150> in<00:10:37.420> swarm<00:10:37.900> is 00:10:38.100 --> 00:10:38.110 align:start position:0% confidential information is in swarm is 00:10:38.110 --> 00:10:39.990 align:start position:0% confidential information is in swarm is encrypted<00:10:38.620> using<00:10:39.070> counter<00:10:39.760> mode<00:10:39.970> encryption 00:10:39.990 --> 00:10:40.000 align:start position:0% encrypted using counter mode encryption 00:10:40.000 --> 00:10:42.240 align:start position:0% encrypted using counter mode encryption which<00:10:40.780> you<00:10:41.080> can<00:10:41.320> find<00:10:41.590> the<00:10:41.740> basic<00:10:42.100> security 00:10:42.240 --> 00:10:42.250 align:start position:0% which you can find the basic security 00:10:42.250 --> 00:10:45.960 align:start position:0% which you can find the basic security properties<00:10:43.090> in<00:10:43.270> Wikipedia<00:10:43.840> however<00:10:44.770> we<00:10:45.670> use 00:10:45.960 --> 00:10:45.970 align:start position:0% properties in Wikipedia however we use 00:10:45.970 --> 00:10:49.290 align:start position:0% properties in Wikipedia however we use our<00:10:46.300> own<00:10:46.600> version<00:10:47.260> of<00:10:47.410> it<00:10:47.710> which<00:10:47.980> is<00:10:48.280> a<00:10:48.730> slight 00:10:49.290 --> 00:10:49.300 align:start position:0% our own version of it which is a slight 00:10:49.300 --> 00:10:52.090 align:start position:0% our own version of it which is a slight modification<00:10:50.010> so<00:10:51.010> instead<00:10:51.580> of<00:10:51.640> the 00:10:52.090 --> 00:10:52.100 align:start position:0% modification so instead of the 00:10:52.100 --> 00:10:55.509 align:start position:0% modification so instead of the Seifer<00:10:52.699> which<00:10:52.910> really<00:10:53.240> is<00:10:53.480> just<00:10:53.509> a<00:10:54.519> one-way 00:10:55.509 --> 00:10:55.519 align:start position:0% Seifer which really is just a one-way 00:10:55.519 --> 00:10:57.699 align:start position:0% Seifer which really is just a one-way function<00:10:55.790> with<00:10:56.209> a<00:10:56.240> reverse<00:10:56.690> gear<00:10:57.019> which<00:10:57.230> CTR 00:10:57.699 --> 00:10:57.709 align:start position:0% function with a reverse gear which CTR 00:10:57.709 --> 00:11:03.069 align:start position:0% function with a reverse gear which CTR encryption<00:10:58.279> doesn't<00:10:58.639> use<00:10:58.790> any<00:10:59.060> way<00:11:01.779> we<00:11:02.779> use 00:11:03.069 --> 00:11:03.079 align:start position:0% encryption doesn't use any way we use 00:11:03.079 --> 00:11:07.240 align:start position:0% encryption doesn't use any way we use Shari<00:11:03.980> twice<00:11:04.930> which<00:11:05.930> is<00:11:06.139> the<00:11:06.350> same<00:11:06.620> hash 00:11:07.240 --> 00:11:07.250 align:start position:0% Shari twice which is the same hash 00:11:07.250 --> 00:11:08.620 align:start position:0% Shari twice which is the same hash function<00:11:07.730> that<00:11:07.880> is<00:11:08.060> used<00:11:08.329> throughout 00:11:08.620 --> 00:11:08.630 align:start position:0% function that is used throughout 00:11:08.630 --> 00:11:12.069 align:start position:0% function that is used throughout aetherium<00:11:09.350> and<00:11:09.680> we<00:11:10.639> use<00:11:10.819> it<00:11:10.850> twice<00:11:11.269> because 00:11:12.069 --> 00:11:12.079 align:start position:0% aetherium and we use it twice because 00:11:12.079 --> 00:11:15.069 align:start position:0% aetherium and we use it twice because with<00:11:13.009> accessing<00:11:13.880> that<00:11:14.060> little<00:11:14.449> piece<00:11:14.660> of<00:11:14.870> data 00:11:15.069 --> 00:11:15.079 align:start position:0% with accessing that little piece of data 00:11:15.079 --> 00:11:18.819 align:start position:0% with accessing that little piece of data that<00:11:15.500> is<00:11:15.680> denoted<00:11:16.100> by<00:11:16.399> that<00:11:16.940> pink<00:11:17.449> arrow<00:11:17.829> what 00:11:18.819 --> 00:11:18.829 align:start position:0% that is denoted by that pink arrow what 00:11:18.829 --> 00:11:21.749 align:start position:0% that is denoted by that pink arrow what you<00:11:18.980> can<00:11:19.190> do<00:11:19.430> is<00:11:19.699> you<00:11:19.940> can<00:11:20.120> partially<00:11:20.649> reveal 00:11:21.749 --> 00:11:21.759 align:start position:0% you can do is you can partially reveal 00:11:21.759 --> 00:11:26.259 align:start position:0% you can do is you can partially reveal plain<00:11:22.759> text<00:11:23.350> inside<00:11:24.350> a<00:11:24.680> encrypted<00:11:25.610> volume<00:11:25.819> or 00:11:26.259 --> 00:11:26.269 align:start position:0% plain text inside a encrypted volume or 00:11:26.269 --> 00:11:29.740 align:start position:0% plain text inside a encrypted volume or a<00:11:26.329> encrypted<00:11:27.230> file<00:11:27.529> in<00:11:28.339> such<00:11:28.699> a<00:11:28.730> way<00:11:29.089> that<00:11:29.420> a 00:11:29.740 --> 00:11:29.750 align:start position:0% a encrypted file in such a way that a 00:11:29.750 --> 00:11:31.809 align:start position:0% a encrypted file in such a way that a smart<00:11:30.139> contract<00:11:30.680> can<00:11:30.889> actually<00:11:31.279> verify<00:11:31.490> it 00:11:31.809 --> 00:11:31.819 align:start position:0% smart contract can actually verify it 00:11:31.819 --> 00:11:34.720 align:start position:0% smart contract can actually verify it which<00:11:32.630> means<00:11:32.990> that<00:11:33.620> you<00:11:33.800> can<00:11:34.009> make<00:11:34.220> various 00:11:34.720 --> 00:11:34.730 align:start position:0% which means that you can make various 00:11:34.730 --> 00:11:36.939 align:start position:0% which means that you can make various commitments<00:11:35.149> on<00:11:35.690> the<00:11:35.990> blockchain<00:11:36.230> in<00:11:36.649> smart 00:11:36.939 --> 00:11:36.949 align:start position:0% commitments on the blockchain in smart 00:11:36.949 --> 00:11:39.160 align:start position:0% commitments on the blockchain in smart contracts<00:11:37.490> regarding<00:11:37.699> the<00:11:38.329> plaintext<00:11:38.839> of 00:11:39.160 --> 00:11:39.170 align:start position:0% contracts regarding the plaintext of 00:11:39.170 --> 00:11:42.009 align:start position:0% contracts regarding the plaintext of certain<00:11:39.680> encrypted<00:11:40.160> content<00:11:40.399> and<00:11:40.910> if<00:11:41.720> there's 00:11:42.009 --> 00:11:42.019 align:start position:0% certain encrypted content and if there's 00:11:42.019 --> 00:11:45.249 align:start position:0% certain encrypted content and if there's a<00:11:42.079> dispute<00:11:42.740> you<00:11:43.009> can<00:11:43.490> reveal<00:11:43.880> a<00:11:44.180> piece<00:11:44.810> of<00:11:45.019> data 00:11:45.249 --> 00:11:45.259 align:start position:0% a dispute you can reveal a piece of data 00:11:45.259 --> 00:11:48.100 align:start position:0% a dispute you can reveal a piece of data that<00:11:46.040> does<00:11:46.399> not<00:11:46.610> reveal<00:11:47.029> your<00:11:47.329> access<00:11:47.690> keys<00:11:47.959> or 00:11:48.100 --> 00:11:48.110 align:start position:0% that does not reveal your access keys or 00:11:48.110 --> 00:11:51.819 align:start position:0% that does not reveal your access keys or anything<00:11:48.380> else<00:11:48.769> just<00:11:49.610> reveals<00:11:50.089> a<00:11:50.480> little<00:11:51.050> part 00:11:51.819 --> 00:11:51.829 align:start position:0% anything else just reveals a little part 00:11:51.829 --> 00:11:55.319 align:start position:0% anything else just reveals a little part of<00:11:52.069> your<00:11:52.579> encrypted<00:11:53.500> content<00:11:54.500> whatever<00:11:54.680> it<00:11:54.949> is 00:11:55.319 --> 00:11:55.329 align:start position:0% of your encrypted content whatever it is 00:11:55.329 --> 00:11:58.569 align:start position:0% of your encrypted content whatever it is this<00:11:56.329> is<00:11:56.860> vulnerable<00:11:57.860> to<00:11:57.920> what 00:11:58.569 --> 00:11:58.579 align:start position:0% this is vulnerable to what 00:11:58.579 --> 00:12:00.610 align:start position:0% this is vulnerable to what cryptographers<00:11:59.420> call<00:11:59.660> existential<00:12:00.410> forgery 00:12:00.610 --> 00:12:00.620 align:start position:0% cryptographers call existential forgery 00:12:00.620 --> 00:12:04.629 align:start position:0% cryptographers call existential forgery but<00:12:01.550> if<00:12:01.880> there's<00:12:02.180> any<00:12:03.430> integrity<00:12:04.430> protection 00:12:04.629 --> 00:12:04.639 align:start position:0% but if there's any integrity protection 00:12:04.639 --> 00:12:07.749 align:start position:0% but if there's any integrity protection in<00:12:05.120> place<00:12:05.199> then<00:12:06.199> this<00:12:06.829> is<00:12:07.009> not<00:12:07.189> actually<00:12:07.730> a 00:12:07.749 --> 00:12:07.759 align:start position:0% in place then this is not actually a 00:12:07.759 --> 00:12:11.050 align:start position:0% in place then this is not actually a security<00:12:08.120> problem<00:12:08.680> so<00:12:09.680> this<00:12:09.949> is<00:12:10.189> how<00:12:10.519> we 00:12:11.050 --> 00:12:11.060 align:start position:0% security problem so this is how we 00:12:11.060 --> 00:12:15.100 align:start position:0% security problem so this is how we encrypt<00:12:11.769> and<00:12:12.769> in<00:12:13.670> practice<00:12:14.209> for<00:12:14.480> application 00:12:15.100 --> 00:12:15.110 align:start position:0% encrypt and in practice for application 00:12:15.110 --> 00:12:17.499 align:start position:0% encrypt and in practice for application developers<00:12:15.680> this<00:12:15.949> means<00:12:16.220> the<00:12:16.399> following<00:12:16.579> that 00:12:17.499 --> 00:12:17.509 align:start position:0% developers this means the following that 00:12:17.509 --> 00:12:19.480 align:start position:0% developers this means the following that compared<00:12:18.139> to<00:12:18.290> unencrypted<00:12:18.920> Swarm 00:12:19.480 --> 00:12:19.490 align:start position:0% compared to unencrypted Swarm 00:12:19.490 --> 00:12:22.949 align:start position:0% compared to unencrypted Swarm the<00:12:20.180> references<00:12:20.959> are<00:12:21.259> no<00:12:21.500> longer<00:12:21.800> plainly 00:12:22.949 --> 00:12:22.959 align:start position:0% the references are no longer plainly 00:12:22.959 --> 00:12:27.460 align:start position:0% the references are no longer plainly route<00:12:23.959> ashes<00:12:24.529> but<00:12:25.250> hashes<00:12:26.149> of<00:12:26.389> the<00:12:26.899> ciphertext 00:12:27.460 --> 00:12:27.470 align:start position:0% route ashes but hashes of the ciphertext 00:12:27.470 --> 00:12:30.100 align:start position:0% route ashes but hashes of the ciphertext plus<00:12:28.459> the<00:12:28.790> decryption<00:12:29.180> key<00:12:29.389> so<00:12:29.779> they<00:12:29.959> have 00:12:30.100 --> 00:12:30.110 align:start position:0% plus the decryption key so they have 00:12:30.110 --> 00:12:33.639 align:start position:0% plus the decryption key so they have grown<00:12:30.439> from<00:12:30.829> 32<00:12:31.430> to<00:12:31.610> 64<00:12:31.639> bytes<00:12:32.480> but<00:12:33.290> otherwise 00:12:33.639 --> 00:12:33.649 align:start position:0% grown from 32 to 64 bytes but otherwise 00:12:33.649 --> 00:12:35.949 align:start position:0% grown from 32 to 64 bytes but otherwise nothing<00:12:34.160> else<00:12:34.579> has<00:12:34.850> changed<00:12:34.880> the<00:12:35.420> API<00:12:35.810> is 00:12:35.949 --> 00:12:35.959 align:start position:0% nothing else has changed the API is 00:12:35.959 --> 00:12:38.860 align:start position:0% nothing else has changed the API is exactly<00:12:36.620> the<00:12:36.769> same<00:12:37.040> and<00:12:37.399> so<00:12:38.300> is<00:12:38.449> the<00:12:38.660> data 00:12:38.860 --> 00:12:38.870 align:start position:0% exactly the same and so is the data 00:12:38.870 --> 00:12:42.129 align:start position:0% exactly the same and so is the data model<00:12:39.220> meaning<00:12:40.220> that<00:12:40.490> if<00:12:41.149> you<00:12:41.329> have<00:12:41.540> already 00:12:42.129 --> 00:12:42.139 align:start position:0% model meaning that if you have already 00:12:42.139 --> 00:12:44.559 align:start position:0% model meaning that if you have already written<00:12:42.579> distributed<00:12:43.579> applications<00:12:44.269> for 00:12:44.559 --> 00:12:44.569 align:start position:0% written distributed applications for 00:12:44.569 --> 00:12:47.740 align:start position:0% written distributed applications for swarm<00:12:44.990> or<00:12:45.230> looked<00:12:45.740> at<00:12:45.920> the<00:12:46.130> example<00:12:47.120> ones<00:12:47.540> that 00:12:47.740 --> 00:12:47.750 align:start position:0% swarm or looked at the example ones that 00:12:47.750 --> 00:12:49.840 align:start position:0% swarm or looked at the example ones that we<00:12:47.899> have<00:12:48.050> in<00:12:48.230> our<00:12:48.290> public<00:12:48.500> repository<00:12:49.370> they 00:12:49.840 --> 00:12:49.850 align:start position:0% we have in our public repository they 00:12:49.850 --> 00:12:52.540 align:start position:0% we have in our public repository they would<00:12:50.089> work<00:12:50.329> without<00:12:50.529> modification<00:12:51.529> on<00:12:52.040> the 00:12:52.540 --> 00:12:52.550 align:start position:0% would work without modification on the 00:12:52.550 --> 00:12:57.100 align:start position:0% would work without modification on the encrypted<00:12:54.189> swarm<00:12:55.189> so<00:12:55.850> this<00:12:56.120> is<00:12:56.360> a<00:12:56.569> native 00:12:57.100 --> 00:12:57.110 align:start position:0% encrypted swarm so this is a native 00:12:57.110 --> 00:13:00.429 align:start position:0% encrypted swarm so this is a native encryption<00:12:58.040> API<00:12:58.399> on<00:12:58.730> top<00:12:58.939> of<00:12:59.089> swarm<00:12:59.420> and<00:12:59.660> every 00:13:00.429 --> 00:13:00.439 align:start position:0% encryption API on top of swarm and every 00:13:00.439 --> 00:13:03.069 align:start position:0% encryption API on top of swarm and every swarm<00:13:00.800> node<00:13:01.010> supports<00:13:01.819> it<00:13:02.000> and<00:13:02.240> the<00:13:02.899> only 00:13:03.069 --> 00:13:03.079 align:start position:0% swarm node supports it and the only 00:13:03.079 --> 00:13:05.470 align:start position:0% swarm node supports it and the only cryptographic<00:13:03.680> assumption<00:13:04.550> that<00:13:04.579> we<00:13:04.970> make<00:13:05.209> is 00:13:05.470 --> 00:13:05.480 align:start position:0% cryptographic assumption that we make is 00:13:05.480 --> 00:13:06.610 align:start position:0% cryptographic assumption that we make is the<00:13:06.019> secure 00:13:06.610 --> 00:13:06.620 align:start position:0% the secure 00:13:06.620 --> 00:13:09.190 align:start position:0% the secure the<00:13:06.800> collision<00:13:07.430> resistance<00:13:08.120> of<00:13:08.360> the<00:13:08.480> SHA<00:13:08.900> tree 00:13:09.190 --> 00:13:09.200 align:start position:0% the collision resistance of the SHA tree 00:13:09.200 --> 00:13:12.550 align:start position:0% the collision resistance of the SHA tree hash<00:13:09.740> function<00:13:10.370> now<00:13:10.940> so<00:13:11.870> we<00:13:12.110> have<00:13:12.290> not 00:13:12.550 --> 00:13:12.560 align:start position:0% hash function now so we have not 00:13:12.560 --> 00:13:14.430 align:start position:0% hash function now so we have not actually<00:13:13.220> increased<00:13:13.670> the<00:13:13.880> attack<00:13:14.150> surface 00:13:14.430 --> 00:13:14.440 align:start position:0% actually increased the attack surface 00:13:14.440 --> 00:13:17.950 align:start position:0% actually increased the attack surface beyond<00:13:15.440> what<00:13:15.770> etherium<00:13:16.460> already<00:13:17.120> assumes<00:13:17.600> and 00:13:17.950 --> 00:13:17.960 align:start position:0% beyond what etherium already assumes and 00:13:17.960 --> 00:13:20.110 align:start position:0% beyond what etherium already assumes and you<00:13:18.440> know<00:13:18.560> if<00:13:18.710> char<00:13:18.980> tree<00:13:19.220> is<00:13:19.340> broken<00:13:19.640> then<00:13:19.940> we 00:13:20.110 --> 00:13:20.120 align:start position:0% you know if char tree is broken then we 00:13:20.120 --> 00:13:23.550 align:start position:0% you know if char tree is broken then we will<00:13:20.270> have<00:13:20.480> much<00:13:20.840> bigger<00:13:21.020> problems<00:13:22.060> and 00:13:23.550 --> 00:13:23.560 align:start position:0% will have much bigger problems and 00:13:23.560 --> 00:13:26.560 align:start position:0% will have much bigger problems and finally<00:13:24.560> we<00:13:24.890> have<00:13:25.100> designed<00:13:25.550> our<00:13:25.940> encryption 00:13:26.560 --> 00:13:26.570 align:start position:0% finally we have designed our encryption 00:13:26.570 --> 00:13:29.470 align:start position:0% finally we have designed our encryption so<00:13:27.170> that<00:13:27.410> it's<00:13:27.800> a<00:13:28.070> smart<00:13:28.610> contract<00:13:28.820> friendly 00:13:29.470 --> 00:13:29.480 align:start position:0% so that it's a smart contract friendly 00:13:29.480 --> 00:13:32.950 align:start position:0% so that it's a smart contract friendly as<00:13:29.690> possible<00:13:30.500> so<00:13:31.430> now<00:13:31.730> I'm<00:13:31.940> gonna<00:13:32.120> move<00:13:32.360> on<00:13:32.660> to 00:13:32.950 --> 00:13:32.960 align:start position:0% as possible so now I'm gonna move on to 00:13:32.960 --> 00:13:36.820 align:start position:0% as possible so now I'm gonna move on to access<00:13:33.440> control<00:13:34.040> in<00:13:34.190> swarm<00:13:34.870> which<00:13:35.870> basically 00:13:36.820 --> 00:13:36.830 align:start position:0% access control in swarm which basically 00:13:36.830 --> 00:13:41.170 align:start position:0% access control in swarm which basically boils<00:13:37.370> down<00:13:37.400> to<00:13:38.260> how<00:13:39.260> do<00:13:39.320> you<00:13:39.620> change<00:13:40.430> the<00:13:40.670> sets 00:13:41.170 --> 00:13:41.180 align:start position:0% boils down to how do you change the sets 00:13:41.180 --> 00:13:44.500 align:start position:0% boils down to how do you change the sets of<00:13:41.510> users<00:13:41.810> that<00:13:42.320> have<00:13:42.560> access<00:13:43.340> to<00:13:43.580> certain 00:13:44.500 --> 00:13:44.510 align:start position:0% of users that have access to certain 00:13:44.510 --> 00:13:46.960 align:start position:0% of users that have access to certain content<00:13:45.110> so<00:13:45.830> it's<00:13:46.130> important<00:13:46.730> to<00:13:46.850> emphasize 00:13:46.960 --> 00:13:46.970 align:start position:0% content so it's important to emphasize 00:13:46.970 --> 00:13:50.590 align:start position:0% content so it's important to emphasize that<00:13:47.720> in<00:13:48.050> a<00:13:48.460> permissionless<00:13:49.460> trustless<00:13:50.330> and 00:13:50.590 --> 00:13:50.600 align:start position:0% that in a permissionless trustless and 00:13:50.600 --> 00:13:54.610 align:start position:0% that in a permissionless trustless and distributive<00:13:51.230> system<00:13:51.740> you<00:13:52.550> can<00:13:52.900> not<00:13:53.900> really 00:13:54.610 --> 00:13:54.620 align:start position:0% distributive system you can not really 00:13:54.620 --> 00:13:57.280 align:start position:0% distributive system you can not really act<00:13:54.950> as<00:13:55.310> a<00:13:55.490> gatekeeper<00:13:55.790> or<00:13:56.360> you<00:13:56.630> cannot<00:13:57.020> really 00:13:57.280 --> 00:13:57.290 align:start position:0% act as a gatekeeper or you cannot really 00:13:57.290 --> 00:14:00.210 align:start position:0% act as a gatekeeper or you cannot really delegate<00:13:57.890> nodes<00:13:58.790> to<00:13:59.210> act<00:13:59.390> as<00:13:59.630> gatekeepers 00:14:00.210 --> 00:14:00.220 align:start position:0% delegate nodes to act as gatekeepers 00:14:00.220 --> 00:14:03.850 align:start position:0% delegate nodes to act as gatekeepers instead<00:14:01.220> read<00:14:01.850> access<00:14:02.360> corresponds<00:14:03.260> to<00:14:03.440> the 00:14:03.850 --> 00:14:03.860 align:start position:0% instead read access corresponds to the 00:14:03.860 --> 00:14:06.930 align:start position:0% instead read access corresponds to the ability<00:14:04.370> to<00:14:04.400> decrypt<00:14:05.000> and<00:14:05.530> write<00:14:06.530> access 00:14:06.930 --> 00:14:06.940 align:start position:0% ability to decrypt and write access 00:14:06.940 --> 00:14:09.330 align:start position:0% ability to decrypt and write access corresponds<00:14:07.940> to<00:14:08.060> the<00:14:08.510> ability<00:14:08.960> to<00:14:08.990> register 00:14:09.330 --> 00:14:09.340 align:start position:0% corresponds to the ability to register 00:14:09.340 --> 00:14:12.430 align:start position:0% corresponds to the ability to register so<00:14:10.340> registration<00:14:11.180> can<00:14:11.420> happen<00:14:11.900> on<00:14:12.050> swarm 00:14:12.430 --> 00:14:12.440 align:start position:0% so registration can happen on swarm 00:14:12.440 --> 00:14:15.340 align:start position:0% so registration can happen on swarm feeds<00:14:12.770> or<00:14:13.100> directly<00:14:13.670> in<00:14:14.060> the<00:14:14.570> blockchain<00:14:14.840> for 00:14:15.340 --> 00:14:15.350 align:start position:0% feeds or directly in the blockchain for 00:14:15.350 --> 00:14:17.950 align:start position:0% feeds or directly in the blockchain for example<00:14:15.800> in<00:14:15.890> an<00:14:16.040> ENS<00:14:16.430> contract<00:14:16.970> and<00:14:17.270> that's 00:14:17.950 --> 00:14:17.960 align:start position:0% example in an ENS contract and that's 00:14:17.960 --> 00:14:20.740 align:start position:0% example in an ENS contract and that's about<00:14:18.350> what<00:14:19.130> you<00:14:19.610> need<00:14:19.790> to<00:14:19.940> know<00:14:20.060> about<00:14:20.180> it 00:14:20.740 --> 00:14:20.750 align:start position:0% about what you need to know about it 00:14:20.750 --> 00:14:23.950 align:start position:0% about what you need to know about it but<00:14:21.410> read<00:14:21.890> access<00:14:22.400> which<00:14:22.970> is<00:14:23.180> the<00:14:23.510> ability<00:14:23.720> to 00:14:23.950 --> 00:14:23.960 align:start position:0% but read access which is the ability to 00:14:23.960 --> 00:14:26.530 align:start position:0% but read access which is the ability to the<00:14:24.230> crypt<00:14:24.530> is<00:14:24.800> a<00:14:25.640> bit<00:14:25.850> more<00:14:26.030> interesting<00:14:26.510> so 00:14:26.530 --> 00:14:26.540 align:start position:0% the crypt is a bit more interesting so 00:14:26.540 --> 00:14:30.460 align:start position:0% the crypt is a bit more interesting so I'm<00:14:26.900> going<00:14:27.140> to<00:14:27.260> talk<00:14:27.470> more<00:14:27.500> about<00:14:27.710> that<00:14:29.470> so 00:14:30.460 --> 00:14:30.470 align:start position:0% I'm going to talk more about that so 00:14:30.470 --> 00:14:33.010 align:start position:0% I'm going to talk more about that so there<00:14:30.770> are<00:14:31.010> three<00:14:31.400> strategies<00:14:31.700> in<00:14:32.420> which<00:14:32.780> you 00:14:33.010 --> 00:14:33.020 align:start position:0% there are three strategies in which you 00:14:33.020 --> 00:14:36.780 align:start position:0% there are three strategies in which you can<00:14:33.230> identify<00:14:34.840> authorized<00:14:35.840> users<00:14:36.320> to<00:14:36.530> access 00:14:36.780 --> 00:14:36.790 align:start position:0% can identify authorized users to access 00:14:36.790 --> 00:14:39.910 align:start position:0% can identify authorized users to access content<00:14:37.790> the<00:14:38.270> simplest<00:14:38.810> and<00:14:39.110> most<00:14:39.140> intuitive 00:14:39.910 --> 00:14:39.920 align:start position:0% content the simplest and most intuitive 00:14:39.920 --> 00:14:44.110 align:start position:0% content the simplest and most intuitive perhaps<00:14:40.490> is<00:14:40.820> a<00:14:41.720> passphrase<00:14:42.340> so<00:14:43.340> you<00:14:43.430> can<00:14:43.850> make 00:14:44.110 --> 00:14:44.120 align:start position:0% perhaps is a passphrase so you can make 00:14:44.120 --> 00:14:48.160 align:start position:0% perhaps is a passphrase so you can make content<00:14:44.630> accessible<00:14:45.470> to<00:14:45.860> users<00:14:46.450> that<00:14:47.450> know<00:14:48.140> a 00:14:48.160 --> 00:14:48.170 align:start position:0% content accessible to users that know a 00:14:48.170 --> 00:14:50.350 align:start position:0% content accessible to users that know a particular<00:14:48.590> passphrase<00:14:49.520> so<00:14:49.790> in<00:14:49.910> this<00:14:50.060> case 00:14:50.350 --> 00:14:50.360 align:start position:0% particular passphrase so in this case 00:14:50.360 --> 00:14:52.750 align:start position:0% particular passphrase so in this case both<00:14:50.660> the<00:14:50.720> publisher<00:14:51.410> and<00:14:51.590> the<00:14:52.220> consumer 00:14:52.750 --> 00:14:52.760 align:start position:0% both the publisher and the consumer 00:14:52.760 --> 00:14:55.210 align:start position:0% both the publisher and the consumer needs<00:14:52.940> to<00:14:53.240> know<00:14:53.390> that<00:14:53.420> passphrase<00:14:54.230> which<00:14:55.040> of 00:14:55.210 --> 00:14:55.220 align:start position:0% needs to know that passphrase which of 00:14:55.220 --> 00:14:58.240 align:start position:0% needs to know that passphrase which of course<00:14:55.250> has<00:14:55.700> the<00:14:55.730> disadvantage<00:14:56.210> if<00:14:56.930> that<00:14:57.890> if 00:14:58.240 --> 00:14:58.250 align:start position:0% course has the disadvantage if that if 00:14:58.250 --> 00:15:01.720 align:start position:0% course has the disadvantage if that if the<00:14:58.640> same<00:14:58.940> user<00:14:59.570> needs<00:15:00.200> to<00:15:00.350> access<00:15:00.650> content<00:15:01.580> by 00:15:01.720 --> 00:15:01.730 align:start position:0% the same user needs to access content by 00:15:01.730 --> 00:15:04.120 align:start position:0% the same user needs to access content by two<00:15:01.790> different<00:15:02.210> publishers<00:15:02.960> then<00:15:03.590> those<00:15:03.890> two 00:15:04.120 --> 00:15:04.130 align:start position:0% two different publishers then those two 00:15:04.130 --> 00:15:05.890 align:start position:0% two different publishers then those two publishers<00:15:04.700> can<00:15:04.910> also<00:15:05.120> access<00:15:05.420> each<00:15:05.780> other's 00:15:05.890 --> 00:15:05.900 align:start position:0% publishers can also access each other's 00:15:05.900 --> 00:15:10.240 align:start position:0% publishers can also access each other's content<00:15:07.150> so<00:15:08.150> in<00:15:08.390> order<00:15:08.780> to<00:15:09.020> mitigate<00:15:09.200> that<00:15:09.530> we 00:15:10.240 --> 00:15:10.250 align:start position:0% content so in order to mitigate that we 00:15:10.250 --> 00:15:12.670 align:start position:0% content so in order to mitigate that we have<00:15:10.460> a<00:15:10.490> more<00:15:10.880> sophisticated<00:15:11.290> access<00:15:12.290> control 00:15:12.670 --> 00:15:12.680 align:start position:0% have a more sophisticated access control 00:15:12.680 --> 00:15:15.250 align:start position:0% have a more sophisticated access control mechanism<00:15:13.250> which<00:15:13.760> is<00:15:13.940> public<00:15:14.570> keys<00:15:14.780> public 00:15:15.250 --> 00:15:15.260 align:start position:0% mechanism which is public keys public 00:15:15.260 --> 00:15:18.610 align:start position:0% mechanism which is public keys public private<00:15:15.470> key<00:15:15.830> pairs<00:15:16.270> and<00:15:17.270> at<00:15:17.840> this<00:15:18.050> point<00:15:18.350> I 00:15:18.610 --> 00:15:18.620 align:start position:0% private key pairs and at this point I 00:15:18.620 --> 00:15:19.870 align:start position:0% private key pairs and at this point I would<00:15:18.830> like<00:15:19.040> to 00:15:19.870 --> 00:15:19.880 align:start position:0% would like to 00:15:19.880 --> 00:15:22.540 align:start position:0% would like to draw<00:15:20.510> your<00:15:20.690> attention<00:15:21.320> as<00:15:21.500> developers<00:15:22.220> that 00:15:22.540 --> 00:15:22.550 align:start position:0% draw your attention as developers that 00:15:22.550 --> 00:15:24.610 align:start position:0% draw your attention as developers that these<00:15:22.790> public<00:15:23.300> keys<00:15:23.540> are<00:15:23.780> not<00:15:23.990> aetherium 00:15:24.610 --> 00:15:24.620 align:start position:0% these public keys are not aetherium 00:15:24.620 --> 00:15:27.070 align:start position:0% these public keys are not aetherium addresses<00:15:25.220> these<00:15:25.730> are<00:15:26.000> actually<00:15:26.600> points<00:15:26.930> on 00:15:27.070 --> 00:15:27.080 align:start position:0% addresses these are actually points on 00:15:27.080 --> 00:15:29.200 align:start position:0% addresses these are actually points on the<00:15:27.200> elliptic<00:15:27.410> curve<00:15:27.800> of<00:15:28.070> which<00:15:28.610> aetherium 00:15:29.200 --> 00:15:29.210 align:start position:0% the elliptic curve of which aetherium 00:15:29.210 --> 00:15:32.740 align:start position:0% the elliptic curve of which aetherium addresses<00:15:29.690> are<00:15:29.840> the<00:15:29.990> hashes<00:15:30.820> so<00:15:31.820> you<00:15:32.060> need<00:15:32.270> you 00:15:32.740 --> 00:15:32.750 align:start position:0% addresses are the hashes so you need you 00:15:32.750 --> 00:15:36.640 align:start position:0% addresses are the hashes so you need you need<00:15:32.990> those<00:15:33.230> in<00:15:33.560> order<00:15:33.830> to<00:15:34.780> as<00:15:35.780> a<00:15:35.810> publisher<00:15:36.470> to 00:15:36.640 --> 00:15:36.650 align:start position:0% need those in order to as a publisher to 00:15:36.650 --> 00:15:39.550 align:start position:0% need those in order to as a publisher to identify<00:15:37.340> your<00:15:37.850> consumers<00:15:38.810> and<00:15:39.080> as<00:15:39.530> a 00:15:39.550 --> 00:15:39.560 align:start position:0% identify your consumers and as a 00:15:39.560 --> 00:15:41.230 align:start position:0% identify your consumers and as a consumer<00:15:40.160> you<00:15:40.340> need<00:15:40.550> to<00:15:40.730> have<00:15:40.940> the 00:15:41.230 --> 00:15:41.240 align:start position:0% consumer you need to have the 00:15:41.240 --> 00:15:44.350 align:start position:0% consumer you need to have the corresponding<00:15:41.630> private<00:15:42.140> key<00:15:42.320> and<00:15:43.000> the<00:15:44.000> most 00:15:44.350 --> 00:15:44.360 align:start position:0% corresponding private key and the most 00:15:44.360 --> 00:15:46.840 align:start position:0% corresponding private key and the most sophisticated<00:15:44.750> and<00:15:45.530> most<00:15:45.770> finely<00:15:46.130> grained 00:15:46.840 --> 00:15:46.850 align:start position:0% sophisticated and most finely grained 00:15:46.850 --> 00:15:48.970 align:start position:0% sophisticated and most finely grained access<00:15:47.690> control<00:15:48.050> mechanism<00:15:48.590> that<00:15:48.710> we<00:15:48.860> have 00:15:48.970 --> 00:15:48.980 align:start position:0% access control mechanism that we have 00:15:48.980 --> 00:15:51.370 align:start position:0% access control mechanism that we have implemented<00:15:49.400> in<00:15:49.760> swarm<00:15:50.120> is<00:15:50.350> access<00:15:51.350> control 00:15:51.370 --> 00:15:51.380 align:start position:0% implemented in swarm is access control 00:15:51.380 --> 00:15:56.350 align:start position:0% implemented in swarm is access control try<00:15:52.190> or<00:15:52.970> act<00:15:53.540> for<00:15:53.960> short<00:15:54.260> this<00:15:55.130> is<00:15:55.190> basically<00:15:56.030> a 00:15:56.350 --> 00:15:56.360 align:start position:0% try or act for short this is basically a 00:15:56.360 --> 00:15:59.680 align:start position:0% try or act for short this is basically a efficient<00:15:57.760> organization<00:15:58.760> of<00:15:58.880> access<00:15:59.270> control 00:15:59.680 --> 00:15:59.690 align:start position:0% efficient organization of access control 00:15:59.690 --> 00:16:03.220 align:start position:0% efficient organization of access control lists<00:16:00.020> and<00:16:00.340> in<00:16:01.340> these<00:16:01.580> lists<00:16:02.120> you<00:16:02.630> can<00:16:02.660> have 00:16:03.220 --> 00:16:03.230 align:start position:0% lists and in these lists you can have 00:16:03.230 --> 00:16:06.520 align:start position:0% lists and in these lists you can have users<00:16:03.890> of<00:16:04.160> both<00:16:04.490> kind<00:16:04.910> so<00:16:05.600> both<00:16:05.870> pass<00:16:06.170> phrases 00:16:06.520 --> 00:16:06.530 align:start position:0% users of both kind so both pass phrases 00:16:06.530 --> 00:16:11.160 align:start position:0% users of both kind so both pass phrases and<00:16:07.010> public<00:16:07.550> keys<00:16:07.760> in<00:16:08.390> such<00:16:08.810> a<00:16:08.840> way<00:16:09.200> that 00:16:11.160 --> 00:16:11.170 align:start position:0% and public keys in such a way that 00:16:11.170 --> 00:16:15.730 align:start position:0% and public keys in such a way that there's<00:16:12.170> no<00:16:12.590> information<00:16:13.720> disclosed<00:16:14.740> beyond 00:16:15.730 --> 00:16:15.740 align:start position:0% there's no information disclosed beyond 00:16:15.740 --> 00:16:19.810 align:start position:0% there's no information disclosed beyond a<00:16:16.010> upper<00:16:16.520> bound<00:16:16.820> on<00:16:17.180> the<00:16:17.270> size<00:16:18.020> of<00:16:18.350> the<00:16:18.500> ACL<00:16:18.950> so 00:16:19.810 --> 00:16:19.820 align:start position:0% a upper bound on the size of the ACL so 00:16:19.820 --> 00:16:22.870 align:start position:0% a upper bound on the size of the ACL so anybody<00:16:20.450> who<00:16:20.840> can<00:16:21.050> access<00:16:21.320> the<00:16:22.010> access 00:16:22.870 --> 00:16:22.880 align:start position:0% anybody who can access the access 00:16:22.880 --> 00:16:26.140 align:start position:0% anybody who can access the access control<00:16:23.300> tri<00:16:23.600> can<00:16:24.350> have<00:16:24.650> a<00:16:24.980> upper<00:16:25.460> bound<00:16:25.490> on 00:16:26.140 --> 00:16:26.150 align:start position:0% control tri can have a upper bound on 00:16:26.150 --> 00:16:29.050 align:start position:0% control tri can have a upper bound on how<00:16:26.180> many<00:16:26.390> items<00:16:26.720> are<00:16:27.440> there<00:16:27.800> but<00:16:28.430> beyond<00:16:28.790> that 00:16:29.050 --> 00:16:29.060 align:start position:0% how many items are there but beyond that 00:16:29.060 --> 00:16:31.720 align:start position:0% how many items are there but beyond that they<00:16:29.270> have<00:16:29.450> no<00:16:29.660> clue<00:16:29.990> how<00:16:30.440> many<00:16:30.500> users<00:16:31.280> can 00:16:31.720 --> 00:16:31.730 align:start position:0% they have no clue how many users can 00:16:31.730 --> 00:16:33.820 align:start position:0% they have no clue how many users can actually<00:16:32.000> access<00:16:32.630> it<00:16:32.660> and<00:16:33.110> who<00:16:33.290> those<00:16:33.500> are 00:16:33.820 --> 00:16:33.830 align:start position:0% actually access it and who those are 00:16:33.830 --> 00:16:36.280 align:start position:0% actually access it and who those are even<00:16:34.460> if<00:16:34.580> you<00:16:34.700> are<00:16:34.790> one<00:16:34.970> of<00:16:35.000> them<00:16:35.270> you<00:16:35.930> can<00:16:36.110> only 00:16:36.280 --> 00:16:36.290 align:start position:0% even if you are one of them you can only 00:16:36.290 --> 00:16:38.050 align:start position:0% even if you are one of them you can only check<00:16:36.590> whether<00:16:36.890> or<00:16:37.160> not<00:16:37.310> you're<00:16:37.580> one<00:16:37.730> of<00:16:37.910> them 00:16:38.050 --> 00:16:38.060 align:start position:0% check whether or not you're one of them 00:16:38.060 --> 00:16:40.480 align:start position:0% check whether or not you're one of them but<00:16:38.300> you<00:16:38.390> cannot<00:16:38.750> peek<00:16:39.590> into<00:16:39.890> other<00:16:40.010> people's 00:16:40.480 --> 00:16:40.490 align:start position:0% but you cannot peek into other people's 00:16:40.490 --> 00:16:45.330 align:start position:0% but you cannot peek into other people's permissions<00:16:42.490> very<00:16:43.490> importantly<00:16:44.120> since 00:16:45.330 --> 00:16:45.340 align:start position:0% permissions very importantly since 00:16:45.340 --> 00:16:48.610 align:start position:0% permissions very importantly since access<00:16:46.340> means<00:16:46.790> ability<00:16:47.300> to<00:16:47.720> decrypt<00:16:48.140> you 00:16:48.610 --> 00:16:48.620 align:start position:0% access means ability to decrypt you 00:16:48.620 --> 00:16:51.250 align:start position:0% access means ability to decrypt you cannot<00:16:49.010> really<00:16:49.310> withdraw<00:16:49.940> access<00:16:50.570> what 00:16:51.250 --> 00:16:51.260 align:start position:0% cannot really withdraw access what 00:16:51.260 --> 00:16:54.190 align:start position:0% cannot really withdraw access what happens<00:16:51.710> if<00:16:51.950> you<00:16:52.160> exclude<00:16:52.730> somebody<00:16:53.570> from<00:16:53.840> the 00:16:54.190 --> 00:16:54.200 align:start position:0% happens if you exclude somebody from the 00:16:54.200 --> 00:16:56.320 align:start position:0% happens if you exclude somebody from the access<00:16:54.500> control<00:16:54.950> list<00:16:55.190> is<00:16:55.430> that<00:16:55.970> they're<00:16:56.150> not 00:16:56.320 --> 00:16:56.330 align:start position:0% access control list is that they're not 00:16:56.330 --> 00:16:58.630 align:start position:0% access control list is that they're not gonna<00:16:56.630> be<00:16:57.050> able<00:16:57.230> to<00:16:57.620> read<00:16:57.770> future<00:16:58.220> updates 00:16:58.630 --> 00:16:58.640 align:start position:0% gonna be able to read future updates 00:16:58.640 --> 00:17:00.940 align:start position:0% gonna be able to read future updates they're<00:16:59.270> still<00:16:59.570> gonna<00:16:59.750> be<00:16:59.870> able<00:17:00.080> to<00:17:00.290> read<00:17:00.680> what 00:17:00.940 --> 00:17:00.950 align:start position:0% they're still gonna be able to read what 00:17:00.950 --> 00:17:03.280 align:start position:0% they're still gonna be able to read what they<00:17:01.100> have<00:17:01.250> read<00:17:01.490> before<00:17:01.900> especially<00:17:02.900> if<00:17:03.050> if 00:17:03.280 --> 00:17:03.290 align:start position:0% they have read before especially if if 00:17:03.290 --> 00:17:05.770 align:start position:0% they have read before especially if if they<00:17:03.560> have<00:17:03.710> cashed<00:17:04.010> all<00:17:04.310> the<00:17:04.459> keys<00:17:05.329> that<00:17:05.360> they 00:17:05.770 --> 00:17:05.780 align:start position:0% they have cashed all the keys that they 00:17:05.780 --> 00:17:09.750 align:start position:0% they have cashed all the keys that they have<00:17:05.959> access<00:17:06.470> to<00:17:06.740> but<00:17:07.550> if<00:17:07.880> the<00:17:08.480> resource<00:17:09.199> is 00:17:09.750 --> 00:17:09.760 align:start position:0% have access to but if the resource is 00:17:09.760 --> 00:17:13.240 align:start position:0% have access to but if the resource is updated<00:17:10.760> then<00:17:11.689> they<00:17:12.320> won't<00:17:12.560> have<00:17:12.800> access<00:17:13.010> to 00:17:13.240 --> 00:17:13.250 align:start position:0% updated then they won't have access to 00:17:13.250 --> 00:17:15.220 align:start position:0% updated then they won't have access to the<00:17:13.430> update<00:17:13.820> anymore<00:17:14.270> only<00:17:14.449> to<00:17:14.750> the<00:17:14.870> old 00:17:15.220 --> 00:17:15.230 align:start position:0% the update anymore only to the old 00:17:15.230 --> 00:17:19.030 align:start position:0% the update anymore only to the old versions<00:17:15.850> but<00:17:16.850> it's<00:17:17.600> also<00:17:17.990> a<00:17:18.290> very<00:17:18.800> neat 00:17:19.030 --> 00:17:19.040 align:start position:0% versions but it's also a very neat 00:17:19.040 --> 00:17:22.030 align:start position:0% versions but it's also a very neat property<00:17:19.730> that<00:17:19.970> if<00:17:20.270> you<00:17:20.540> change<00:17:20.930> the<00:17:21.410> act 00:17:22.030 --> 00:17:22.040 align:start position:0% property that if you change the act 00:17:22.040 --> 00:17:24.280 align:start position:0% property that if you change the act you<00:17:22.339> don't<00:17:22.640> need<00:17:22.880> to<00:17:23.150> re-encrypt<00:17:23.600> the<00:17:23.839> content 00:17:24.280 --> 00:17:24.290 align:start position:0% you don't need to re-encrypt the content 00:17:24.290 --> 00:17:26.890 align:start position:0% you don't need to re-encrypt the content because<00:17:24.850> we're<00:17:25.850> using<00:17:26.060> multi<00:17:26.600> stage 00:17:26.890 --> 00:17:26.900 align:start position:0% because we're using multi stage 00:17:26.900 --> 00:17:29.020 align:start position:0% because we're using multi stage encryption<00:17:27.500> and<00:17:27.650> you<00:17:28.100> basically<00:17:28.280> only<00:17:28.700> need 00:17:29.020 --> 00:17:29.030 align:start position:0% encryption and you basically only need 00:17:29.030 --> 00:17:29.890 align:start position:0% encryption and you basically only need to<00:17:29.210> re-encrypt 00:17:29.890 --> 00:17:29.900 align:start position:0% to re-encrypt 00:17:29.900 --> 00:17:31.390 align:start position:0% to re-encrypt the<00:17:30.230> reference<00:17:30.650> that<00:17:30.860> I<00:17:31.010> talked<00:17:31.250> about 00:17:31.390 --> 00:17:31.400 align:start position:0% the reference that I talked about 00:17:31.400 --> 00:17:33.620 align:start position:0% the reference that I talked about earlier<00:17:31.580> the<00:17:32.060> 64 00:17:33.620 --> 00:17:33.630 align:start position:0% earlier the 64 00:17:33.630 --> 00:17:39.400 align:start position:0% earlier the 64 right<00:17:33.870> reference<00:17:36.710> also<00:17:37.970> granting<00:17:38.970> access 00:17:39.400 --> 00:17:39.410 align:start position:0% right reference also granting access 00:17:39.410 --> 00:17:43.789 align:start position:0% right reference also granting access extending<00:17:40.410> the<00:17:40.850> access<00:17:41.850> control<00:17:42.299> tribe<00:17:42.690> is<00:17:43.049> a 00:17:43.789 --> 00:17:43.799 align:start position:0% extending the access control tribe is a 00:17:43.799 --> 00:17:45.890 align:start position:0% extending the access control tribe is a logarithmic<00:17:44.160> operation<00:17:45.059> so<00:17:45.270> if<00:17:45.360> you<00:17:45.510> want<00:17:45.750> to 00:17:45.890 --> 00:17:45.900 align:start position:0% logarithmic operation so if you want to 00:17:45.900 --> 00:17:49.130 align:start position:0% logarithmic operation so if you want to add<00:17:46.049> another<00:17:46.530> party<00:17:47.130> to<00:17:47.429> your<00:17:47.700> access<00:17:48.210> then 00:17:49.130 --> 00:17:49.140 align:start position:0% add another party to your access then 00:17:49.140 --> 00:17:51.590 align:start position:0% add another party to your access then the<00:17:49.740> operate<00:17:50.250> the<00:17:50.460> number<00:17:50.789> of<00:17:50.970> encryptions 00:17:51.590 --> 00:17:51.600 align:start position:0% the operate the number of encryptions 00:17:51.600 --> 00:17:54.560 align:start position:0% the operate the number of encryptions that<00:17:51.900> you<00:17:52.080> need<00:17:52.289> to<00:17:52.530> do<00:17:52.710> is<00:17:52.950> a<00:17:53.730> logarithm<00:17:54.150> of 00:17:54.560 --> 00:17:54.570 align:start position:0% that you need to do is a logarithm of 00:17:54.570 --> 00:17:58.700 align:start position:0% that you need to do is a logarithm of the<00:17:54.990> number<00:17:55.559> of<00:17:56.070> grantees<00:17:57.470> revoking<00:17:58.470> is<00:17:58.679> a 00:17:58.700 --> 00:17:58.710 align:start position:0% the number of grantees revoking is a 00:17:58.710 --> 00:18:01.039 align:start position:0% the number of grantees revoking is a little<00:17:59.160> bit<00:17:59.340> more<00:17:59.520> expensive<00:18:00.179> it's<00:18:00.419> linear<00:18:00.840> in 00:18:01.039 --> 00:18:01.049 align:start position:0% little bit more expensive it's linear in 00:18:01.049 --> 00:18:03.650 align:start position:0% little bit more expensive it's linear in the<00:18:01.230> number<00:18:01.500> of<00:18:01.530> grantees<00:18:02.039> precisely<00:18:02.970> because 00:18:03.650 --> 00:18:03.660 align:start position:0% the number of grantees precisely because 00:18:03.660 --> 00:18:08.330 align:start position:0% the number of grantees precisely because you<00:18:03.870> want<00:18:04.110> to<00:18:04.200> reintroduce<00:18:07.340> cryptid 00:18:08.330 --> 00:18:08.340 align:start position:0% you want to reintroduce cryptid 00:18:08.340 --> 00:18:11.960 align:start position:0% you want to reintroduce cryptid reference<00:18:08.820> so<00:18:09.450> that<00:18:09.480> the<00:18:10.320> those<00:18:11.309> whom<00:18:11.820> you 00:18:11.960 --> 00:18:11.970 align:start position:0% reference so that the those whom you 00:18:11.970 --> 00:18:14.240 align:start position:0% reference so that the those whom you have<00:18:12.120> excluded<00:18:12.600> will<00:18:13.260> no<00:18:13.470> longer<00:18:13.710> have<00:18:13.980> access 00:18:14.240 --> 00:18:14.250 align:start position:0% have excluded will no longer have access 00:18:14.250 --> 00:18:18.799 align:start position:0% have excluded will no longer have access to<00:18:14.520> the<00:18:14.789> updates<00:18:15.150> and<00:18:16.460> finally<00:18:17.460> I<00:18:18.090> would<00:18:18.450> like 00:18:18.799 --> 00:18:18.809 align:start position:0% to the updates and finally I would like 00:18:18.809 --> 00:18:22.850 align:start position:0% to the updates and finally I would like to<00:18:19.220> draw<00:18:20.220> your<00:18:20.250> attention<00:18:20.429> that<00:18:21.860> the 00:18:22.850 --> 00:18:22.860 align:start position:0% to draw your attention that the 00:18:22.860 --> 00:18:25.909 align:start position:0% to draw your attention that the granularity<00:18:23.460> of<00:18:24.000> this<00:18:24.299> is<00:18:24.630> very<00:18:25.140> similar<00:18:25.679> to 00:18:25.909 --> 00:18:25.919 align:start position:0% granularity of this is very similar to 00:18:25.919 --> 00:18:28.279 align:start position:0% granularity of this is very similar to that<00:18:26.100> in<00:18:26.400> a<00:18:26.580> UNIX<00:18:26.909> file<00:18:27.120> system<00:18:27.150> so<00:18:27.929> you<00:18:27.990> can 00:18:28.279 --> 00:18:28.289 align:start position:0% that in a UNIX file system so you can 00:18:28.289 --> 00:18:31.100 align:start position:0% that in a UNIX file system so you can have<00:18:28.590> per<00:18:28.890> directory<00:18:29.429> permissions<00:18:30.120> per<00:18:30.809> file 00:18:31.100 --> 00:18:31.110 align:start position:0% have per directory permissions per file 00:18:31.110 --> 00:18:33.649 align:start position:0% have per directory permissions per file permissions<00:18:31.770> and<00:18:32.039> so<00:18:32.250> on<00:18:32.429> so<00:18:32.760> you<00:18:33.000> don't<00:18:33.360> need 00:18:33.649 --> 00:18:33.659 align:start position:0% permissions and so on so you don't need 00:18:33.659 --> 00:18:36.470 align:start position:0% permissions and so on so you don't need to<00:18:33.900> have<00:18:34.080> an<00:18:34.230> entire<00:18:34.590> swarm<00:18:35.039> volume<00:18:35.549> under<00:18:36.240> the 00:18:36.470 --> 00:18:36.480 align:start position:0% to have an entire swarm volume under the 00:18:36.480 --> 00:18:42.049 align:start position:0% to have an entire swarm volume under the same<00:18:36.860> access<00:18:37.860> control<00:18:39.710> so<00:18:40.710> before<00:18:41.190> I<00:18:41.220> finish<00:18:41.700> I 00:18:42.049 --> 00:18:42.059 align:start position:0% same access control so before I finish I 00:18:42.059 --> 00:18:45.110 align:start position:0% same access control so before I finish I would<00:18:42.600> like<00:18:42.840> to<00:18:43.200> give<00:18:43.409> you<00:18:43.620> one<00:18:44.340> warning<00:18:44.610> and 00:18:45.110 --> 00:18:45.120 align:start position:0% would like to give you one warning and 00:18:45.120 --> 00:18:47.539 align:start position:0% would like to give you one warning and this<00:18:45.900> is<00:18:46.080> the<00:18:46.230> last<00:18:46.440> thing<00:18:46.679> I'm<00:18:46.860> gonna<00:18:47.070> say<00:18:47.190> and 00:18:47.539 --> 00:18:47.549 align:start position:0% this is the last thing I'm gonna say and 00:18:47.549 --> 00:18:49.279 align:start position:0% this is the last thing I'm gonna say and hopefully<00:18:47.700> this<00:18:48.210> last<00:18:48.480> one<00:18:48.720> you<00:18:48.840> remember 00:18:49.279 --> 00:18:49.289 align:start position:0% hopefully this last one you remember 00:18:49.289 --> 00:18:52.250 align:start position:0% hopefully this last one you remember that<00:18:50.190> if<00:18:50.700> you're<00:18:51.150> dealing<00:18:51.419> with<00:18:51.630> access 00:18:52.250 --> 00:18:52.260 align:start position:0% that if you're dealing with access 00:18:52.260 --> 00:18:55.430 align:start position:0% that if you're dealing with access controlled<00:18:52.770> content<00:18:53.340> please<00:18:53.970> please<00:18:54.720> don't 00:18:55.430 --> 00:18:55.440 align:start position:0% controlled content please please don't 00:18:55.440 --> 00:18:58.370 align:start position:0% controlled content please please don't use<00:18:55.799> public<00:18:56.100> gateways<00:18:56.760> run<00:18:57.330> your<00:18:57.659> own<00:18:57.690> swarm 00:18:58.370 --> 00:18:58.380 align:start position:0% use public gateways run your own swarm 00:18:58.380 --> 00:19:01.370 align:start position:0% use public gateways run your own swarm node<00:18:58.620> because<00:18:59.580> if<00:19:00.030> you're<00:19:00.390> using<00:19:00.690> the<00:19:00.990> public 00:19:01.370 --> 00:19:01.380 align:start position:0% node because if you're using the public 00:19:01.380 --> 00:19:04.399 align:start position:0% node because if you're using the public gateway<00:19:01.890> that<00:19:02.429> Gateway<00:19:03.090> will<00:19:03.419> have<00:19:03.690> access<00:19:03.960> to 00:19:04.399 --> 00:19:04.409 align:start position:0% gateway that Gateway will have access to 00:19:04.409 --> 00:19:07.279 align:start position:0% gateway that Gateway will have access to the<00:19:04.530> same<00:19:04.770> access<00:19:05.280> controlled<00:19:06.020> content<00:19:07.020> and 00:19:07.279 --> 00:19:07.289 align:start position:0% the same access controlled content and 00:19:07.289 --> 00:19:09.710 align:start position:0% the same access controlled content and you<00:19:07.679> might<00:19:07.860> not<00:19:08.039> want<00:19:08.309> to<00:19:08.490> have<00:19:08.640> that<00:19:08.880> so<00:19:09.390> thank 00:19:09.710 --> 00:19:09.720 align:start position:0% you might not want to have that so thank 00:19:09.720 --> 00:19:10.720 align:start position:0% you might not want to have that so thank you<00:19:09.780> so<00:19:09.929> much 00:19:10.720 --> 00:19:10.730 align:start position:0% you so much 00:19:10.730 --> 00:19:15.060 align:start position:0% you so much [Applause] 00:19:15.060 --> 00:19:15.070 align:start position:0% [Applause] 00:19:15.070 --> 00:19:18.270 align:start position:0% [Applause] alright<00:19:15.790> so<00:19:16.780> next<00:19:16.900> up<00:19:17.110> is<00:19:17.320> Antone<00:19:17.950> about 00:19:18.270 --> 00:19:18.280 align:start position:0% alright so next up is Antone about 00:19:18.280 --> 00:19:22.290 align:start position:0% alright so next up is Antone about observability<00:19:19.770> hello<00:19:20.770> everyone<00:19:21.160> so<00:19:21.970> I'm 00:19:22.290 --> 00:19:22.300 align:start position:0% observability hello everyone so I'm 00:19:22.300 --> 00:19:24.900 align:start position:0% observability hello everyone so I'm going<00:19:22.570> to<00:19:22.600> talk<00:19:22.810> about<00:19:22.930> observability<00:19:23.830> in<00:19:24.760> the 00:19:24.900 --> 00:19:24.910 align:start position:0% going to talk about observability in the 00:19:24.910 --> 00:19:27.870 align:start position:0% going to talk about observability in the last<00:19:25.120> few<00:19:25.840> months<00:19:26.170> we've<00:19:26.470> implemented<00:19:27.040> a<00:19:27.490> lot 00:19:27.870 --> 00:19:27.880 align:start position:0% last few months we've implemented a lot 00:19:27.880 --> 00:19:30.540 align:start position:0% last few months we've implemented a lot of<00:19:28.170> observability<00:19:29.170> to<00:19:29.320> things<00:19:29.560> form<00:19:29.770> and<00:19:30.280> also 00:19:30.540 --> 00:19:30.550 align:start position:0% of observability to things form and also 00:19:30.550 --> 00:19:33.750 align:start position:0% of observability to things form and also instrumented<00:19:31.120> the<00:19:31.210> code<00:19:31.420> so<00:19:31.840> that<00:19:32.370> you<00:19:33.370> can 00:19:33.750 --> 00:19:33.760 align:start position:0% instrumented the code so that you can 00:19:33.760 --> 00:19:35.310 align:start position:0% instrumented the code so that you can use<00:19:33.880> those<00:19:34.090> tools 00:19:35.310 --> 00:19:35.320 align:start position:0% use those tools 00:19:35.320 --> 00:19:37.740 align:start position:0% use those tools what<00:19:35.920> is<00:19:36.070> observability<00:19:36.850> serve<00:19:37.270> abilities 00:19:37.740 --> 00:19:37.750 align:start position:0% what is observability serve abilities 00:19:37.750 --> 00:19:39.540 align:start position:0% what is observability serve abilities basically<00:19:38.590> answering<00:19:38.890> the<00:19:39.010> question<00:19:39.370> what<00:19:39.490> is 00:19:39.540 --> 00:19:39.550 align:start position:0% basically answering the question what is 00:19:39.550 --> 00:19:41.970 align:start position:0% basically answering the question what is nice<00:19:39.910> from<00:19:40.120> not<00:19:40.720> doing<00:19:41.140> at<00:19:41.470> the<00:19:41.590> moment 00:19:41.970 --> 00:19:41.980 align:start position:0% nice from not doing at the moment 00:19:41.980 --> 00:19:45.060 align:start position:0% nice from not doing at the moment and<00:19:42.300> if<00:19:43.300> you<00:19:43.540> are<00:19:43.900> an<00:19:44.170> operator<00:19:44.500> of<00:19:44.740> let's<00:19:44.950> say 00:19:45.060 --> 00:19:45.070 align:start position:0% and if you are an operator of let's say 00:19:45.070 --> 00:19:47.910 align:start position:0% and if you are an operator of let's say a<00:19:45.100> larger<00:19:45.460> deployment<00:19:46.030> like<00:19:46.600> us<00:19:47.440> for<00:19:47.830> the 00:19:47.910 --> 00:19:47.920 align:start position:0% a larger deployment like us for the 00:19:47.920 --> 00:19:50.880 align:start position:0% a larger deployment like us for the swarm<00:19:48.100> gateways<00:19:48.490> what<00:19:49.360> is<00:19:49.600> my<00:19:49.890> food 00:19:50.880 --> 00:19:50.890 align:start position:0% swarm gateways what is my food 00:19:50.890 --> 00:19:52.170 align:start position:0% swarm gateways what is my food deployment<00:19:51.370> doing<00:19:51.550> so<00:19:51.730> basically<00:19:52.030> an 00:19:52.170 --> 00:19:52.180 align:start position:0% deployment doing so basically an 00:19:52.180 --> 00:19:55.320 align:start position:0% deployment doing so basically an aggregate<00:19:52.570> view<00:19:52.810> of<00:19:53.140> is<00:19:53.620> your<00:19:54.010> network<00:19:54.730> coyote 00:19:55.320 --> 00:19:55.330 align:start position:0% aggregate view of is your network coyote 00:19:55.330 --> 00:20:01.190 align:start position:0% aggregate view of is your network coyote and<00:19:56.580> basically<00:19:57.840> how<00:19:58.840> our<00:19:59.410> abilities<00:20:00.280> so 00:20:01.190 --> 00:20:01.200 align:start position:0% and basically how our abilities so 00:20:01.200 --> 00:20:04.680 align:start position:0% and basically how our abilities so observability<00:20:02.200> inform<00:20:03.210> what<00:20:04.210> do<00:20:04.300> we<00:20:04.390> mean<00:20:04.510> by 00:20:04.680 --> 00:20:04.690 align:start position:0% observability inform what do we mean by 00:20:04.690 --> 00:20:07.110 align:start position:0% observability inform what do we mean by that<00:20:04.720> so<00:20:05.410> there<00:20:06.100> are<00:20:06.160> three<00:20:06.310> pillars<00:20:06.460> to<00:20:06.790> it<00:20:06.910> so 00:20:07.110 --> 00:20:07.120 align:start position:0% that so there are three pillars to it so 00:20:07.120 --> 00:20:09.840 align:start position:0% that so there are three pillars to it so logging<00:20:07.650> metrics<00:20:08.650> and<00:20:08.890> distributed<00:20:09.400> tracing 00:20:09.840 --> 00:20:09.850 align:start position:0% logging metrics and distributed tracing 00:20:09.850 --> 00:20:14.460 align:start position:0% logging metrics and distributed tracing so<00:20:10.360> we<00:20:11.170> do<00:20:11.320> aggregate<00:20:12.070> logging<00:20:12.790> on<00:20:13.180> our<00:20:13.900> soar 00:20:14.460 --> 00:20:14.470 align:start position:0% so we do aggregate logging on our soar 00:20:14.470 --> 00:20:16.140 align:start position:0% so we do aggregate logging on our soar nodes<00:20:14.740> so<00:20:15.070> that<00:20:15.220> we<00:20:15.340> can<00:20:15.520> basically<00:20:15.700> trace 00:20:16.140 --> 00:20:16.150 align:start position:0% nodes so that we can basically trace 00:20:16.150 --> 00:20:18.990 align:start position:0% nodes so that we can basically trace requests<00:20:16.510> from<00:20:16.630> one<00:20:16.840> to<00:20:16.990> another<00:20:17.850> we<00:20:18.850> do 00:20:18.990 --> 00:20:19.000 align:start position:0% requests from one to another we do 00:20:19.000 --> 00:20:21.330 align:start position:0% requests from one to another we do matrix<00:20:19.210> aggregation<00:20:20.080> and<00:20:20.200> statistics<00:20:20.800> and<00:20:21.040> we 00:20:21.330 --> 00:20:21.340 align:start position:0% matrix aggregation and statistics and we 00:20:21.340 --> 00:20:24.030 align:start position:0% matrix aggregation and statistics and we also<00:20:21.520> do<00:20:21.790> distributed<00:20:22.450> tracing<00:20:22.930> so<00:20:23.170> cross 00:20:24.030 --> 00:20:24.040 align:start position:0% also do distributed tracing so cross 00:20:24.040 --> 00:20:27.510 align:start position:0% also do distributed tracing so cross node<00:20:24.700> propagation<00:20:25.480> of<00:20:25.600> traces<00:20:26.430> logging<00:20:27.430> in 00:20:27.510 --> 00:20:27.520 align:start position:0% node propagation of traces logging in 00:20:27.520 --> 00:20:29.730 align:start position:0% node propagation of traces logging in matrix<00:20:28.050> even<00:20:29.050> though<00:20:29.170> they're<00:20:29.350> very<00:20:29.530> useful 00:20:29.730 --> 00:20:29.740 align:start position:0% matrix even though they're very useful 00:20:29.740 --> 00:20:31.770 align:start position:0% matrix even though they're very useful they're<00:20:30.130> not<00:20:30.250> very<00:20:31.150> interesting<00:20:31.600> they've 00:20:31.770 --> 00:20:31.780 align:start position:0% they're not very interesting they've 00:20:31.780 --> 00:20:33.480 align:start position:0% they're not very interesting they've been<00:20:31.960> in<00:20:32.080> the<00:20:32.230> going<00:20:32.560> to<00:20:32.650> VM<00:20:32.770> code<00:20:32.980> base<00:20:33.190> for<00:20:33.460> a 00:20:33.480 --> 00:20:33.490 align:start position:0% been in the going to VM code base for a 00:20:33.490 --> 00:20:36.180 align:start position:0% been in the going to VM code base for a while<00:20:33.730> now<00:20:33.880> what<00:20:34.570> we<00:20:34.780> introduced<00:20:35.230> is<00:20:35.560> the<00:20:35.830> open 00:20:36.180 --> 00:20:36.190 align:start position:0% while now what we introduced is the open 00:20:36.190 --> 00:20:38.100 align:start position:0% while now what we introduced is the open tracing<00:20:36.670> framework<00:20:37.060> and<00:20:37.450> we<00:20:37.750> instrumented 00:20:38.100 --> 00:20:38.110 align:start position:0% tracing framework and we instrumented 00:20:38.110 --> 00:20:40.770 align:start position:0% tracing framework and we instrumented the<00:20:38.620> holes<00:20:39.070> from<00:20:39.340> code<00:20:39.610> edit<00:20:39.910> which<00:20:40.570> is 00:20:40.770 --> 00:20:40.780 align:start position:0% the holes from code edit which is 00:20:40.780 --> 00:20:43.260 align:start position:0% the holes from code edit which is basically<00:20:41.320> vendor-neutral<00:20:42.040> api's<00:20:43.000> for 00:20:43.260 --> 00:20:43.270 align:start position:0% basically vendor-neutral api's for 00:20:43.270 --> 00:20:46.530 align:start position:0% basically vendor-neutral api's for instrumentation<00:20:44.700> so<00:20:45.700> what<00:20:46.240> do<00:20:46.390> we<00:20:46.420> actually 00:20:46.530 --> 00:20:46.540 align:start position:0% instrumentation so what do we actually 00:20:46.540 --> 00:20:48.930 align:start position:0% instrumentation so what do we actually measure<00:20:47.230> with<00:20:47.560> those<00:20:47.740> tools<00:20:48.040> as<00:20:48.520> you<00:20:48.760> can 00:20:48.930 --> 00:20:48.940 align:start position:0% measure with those tools as you can 00:20:48.940 --> 00:20:52.500 align:start position:0% measure with those tools as you can imagine<00:20:49.740> the<00:20:50.740> infrastructure<00:20:51.370> metric<00:20:51.820> so<00:20:52.030> CPU 00:20:52.500 --> 00:20:52.510 align:start position:0% imagine the infrastructure metric so CPU 00:20:52.510 --> 00:20:55.080 align:start position:0% imagine the infrastructure metric so CPU memory<00:20:53.260> disk<00:20:53.530> utilization<00:20:54.490> so<00:20:54.760> in<00:20:54.880> case<00:20:55.060> we 00:20:55.080 --> 00:20:55.090 align:start position:0% memory disk utilization so in case we 00:20:55.090 --> 00:20:58.140 align:start position:0% memory disk utilization so in case we have<00:20:55.330> a<00:20:55.360> backings<00:20:55.750> form<00:20:56.160> we<00:20:57.160> can<00:20:57.370> detect<00:20:57.670> like 00:20:58.140 --> 00:20:58.150 align:start position:0% have a backings form we can detect like 00:20:58.150 --> 00:21:00.750 align:start position:0% have a backings form we can detect like memory<00:20:58.540> leaks<00:20:58.780> or<00:20:59.110> CPU<00:20:59.500> starvation<00:21:00.130> if<00:21:00.400> we 00:21:00.750 --> 00:21:00.760 align:start position:0% memory leaks or CPU starvation if we 00:21:00.760 --> 00:21:04.560 align:start position:0% memory leaks or CPU starvation if we have<00:21:01.000> let's<00:21:01.780> say<00:21:01.930> goroutine<00:21:02.440> leaks<00:21:02.680> and<00:21:03.570> also 00:21:04.560 --> 00:21:04.570 align:start position:0% have let's say goroutine leaks and also 00:21:04.570 --> 00:21:06.420 align:start position:0% have let's say goroutine leaks and also very<00:21:05.020> useful<00:21:05.230> for<00:21:05.680> us<00:21:05.710> is<00:21:05.950> the<00:21:06.070> application 00:21:06.420 --> 00:21:06.430 align:start position:0% very useful for us is the application 00:21:06.430 --> 00:21:08.490 align:start position:0% very useful for us is the application matrix<00:21:06.940> so<00:21:07.240> basically<00:21:07.780> we<00:21:07.990> track<00:21:08.260> how<00:21:08.440> many 00:21:08.490 --> 00:21:08.500 align:start position:0% matrix so basically we track how many 00:21:08.500 --> 00:21:10.770 align:start position:0% matrix so basically we track how many errors<00:21:08.830> happen<00:21:09.460> how<00:21:09.820> many<00:21:10.030> warnings<00:21:10.480> and 00:21:10.770 --> 00:21:10.780 align:start position:0% errors happen how many warnings and 00:21:10.780 --> 00:21:13.560 align:start position:0% errors happen how many warnings and other<00:21:11.320> types<00:21:11.650> of<00:21:11.770> counters<00:21:12.250> when<00:21:13.180> I<00:21:13.210> say 00:21:13.560 --> 00:21:13.570 align:start position:0% other types of counters when I say 00:21:13.570 --> 00:21:15.600 align:start position:0% other types of counters when I say errors<00:21:13.990> I<00:21:14.170> mean<00:21:14.380> things<00:21:14.890> that<00:21:14.950> developers 00:21:15.600 --> 00:21:15.610 align:start position:0% errors I mean things that developers 00:21:15.610 --> 00:21:18.390 align:start position:0% errors I mean things that developers must<00:21:15.790> look<00:21:16.330> at<00:21:16.510> so<00:21:16.900> let's<00:21:17.470> say<00:21:17.710> that<00:21:17.980> we<00:21:18.160> have 00:21:18.390 --> 00:21:18.400 align:start position:0% must look at so let's say that we have 00:21:18.400 --> 00:21:21.060 align:start position:0% must look at so let's say that we have unit<00:21:18.790> I<00:21:19.000> mean<00:21:19.150> we<00:21:19.300> have<00:21:19.450> a<00:21:19.800> elaborate<00:21:20.800> unit 00:21:21.060 --> 00:21:21.070 align:start position:0% unit I mean we have a elaborate unit 00:21:21.070 --> 00:21:22.890 align:start position:0% unit I mean we have a elaborate unit tests<00:21:21.280> and<00:21:21.490> integration<00:21:21.670> tests<00:21:22.360> food<00:21:22.600> that 00:21:22.890 --> 00:21:22.900 align:start position:0% tests and integration tests food that 00:21:22.900 --> 00:21:25.590 align:start position:0% tests and integration tests food that catches<00:21:23.290> a<00:21:23.320> lot<00:21:23.470> of<00:21:23.620> things<00:21:23.830> but<00:21:24.390> errors<00:21:25.390> is 00:21:25.590 --> 00:21:25.600 align:start position:0% catches a lot of things but errors is 00:21:25.600 --> 00:21:26.830 align:start position:0% catches a lot of things but errors is what<00:21:26.050> might<00:21:26.290> happen 00:21:26.830 --> 00:21:26.840 align:start position:0% what might happen 00:21:26.840 --> 00:21:28.630 align:start position:0% what might happen saying<00:21:26.990> production<00:21:27.500> on<00:21:27.680> our<00:21:27.890> public<00:21:28.040> test<00:21:28.430> net 00:21:28.630 --> 00:21:28.640 align:start position:0% saying production on our public test net 00:21:28.640 --> 00:21:31.150 align:start position:0% saying production on our public test net and<00:21:28.820> that<00:21:29.300> helps<00:21:29.660> us<00:21:29.810> debug<00:21:30.380> problems<00:21:30.740> for 00:21:31.150 --> 00:21:31.160 align:start position:0% and that helps us debug problems for 00:21:31.160 --> 00:21:34.360 align:start position:0% and that helps us debug problems for which<00:21:31.340> the<00:21:32.090> test<00:21:32.300> suit<00:21:32.540> is<00:21:32.720> not<00:21:33.080> enough<00:21:33.410> other 00:21:34.360 --> 00:21:34.370 align:start position:0% which the test suit is not enough other 00:21:34.370 --> 00:21:37.420 align:start position:0% which the test suit is not enough other types<00:21:34.970> of<00:21:35.120> application<00:21:35.990> matrix<00:21:36.440> number<00:21:37.310> of 00:21:37.420 --> 00:21:37.430 align:start position:0% types of application matrix number of 00:21:37.430 --> 00:21:39.280 align:start position:0% types of application matrix number of peers<00:21:37.730> per<00:21:37.940> node<00:21:38.180> so<00:21:38.510> basically<00:21:39.080> the 00:21:39.280 --> 00:21:39.290 align:start position:0% peers per node so basically the 00:21:39.290 --> 00:21:41.170 align:start position:0% peers per node so basically the different<00:21:39.620> def<00:21:39.770> be<00:21:40.010> to<00:21:40.070> be<00:21:40.340> notes<00:21:40.730> that<00:21:41.030> your 00:21:41.170 --> 00:21:41.180 align:start position:0% different def be to be notes that your 00:21:41.180 --> 00:21:44.470 align:start position:0% different def be to be notes that your node<00:21:41.360> is<00:21:41.510> connected<00:21:41.660> to<00:21:42.790> different<00:21:43.790> protocol 00:21:44.470 --> 00:21:44.480 align:start position:0% node is connected to different protocol 00:21:44.480 --> 00:21:47.410 align:start position:0% node is connected to different protocol messages<00:21:44.630> between<00:21:45.290> the<00:21:45.740> peers<00:21:46.250> and<00:21:46.580> pretty 00:21:47.410 --> 00:21:47.420 align:start position:0% messages between the peers and pretty 00:21:47.420 --> 00:21:49.420 align:start position:0% messages between the peers and pretty much<00:21:47.630> anything<00:21:48.230> that<00:21:48.380> you're<00:21:48.650> not<00:21:48.800> is<00:21:49.100> running 00:21:49.420 --> 00:21:49.430 align:start position:0% much anything that you're not is running 00:21:49.430 --> 00:21:50.860 align:start position:0% much anything that you're not is running and<00:21:49.730> that<00:21:49.940> you<00:21:50.150> want<00:21:50.330> to<00:21:50.450> gain<00:21:50.630> visibility 00:21:50.860 --> 00:21:50.870 align:start position:0% and that you want to gain visibility 00:21:50.870 --> 00:21:55.360 align:start position:0% and that you want to gain visibility into<00:21:52.660> so<00:21:53.660> I'm<00:21:53.840> going<00:21:54.140> to<00:21:54.170> give<00:21:54.830> you<00:21:55.010> examples 00:21:55.360 --> 00:21:55.370 align:start position:0% into so I'm going to give you examples 00:21:55.370 --> 00:21:57.160 align:start position:0% into so I'm going to give you examples of<00:21:55.760> how<00:21:55.910> those<00:21:56.060> tools<00:21:56.330> look<00:21:56.510> like<00:21:56.720> so<00:21:56.990> that's 00:21:57.160 --> 00:21:57.170 align:start position:0% of how those tools look like so that's 00:21:57.170 --> 00:21:59.110 align:start position:0% of how those tools look like so that's one<00:21:57.410> of<00:21:57.440> them<00:21:57.680> we're<00:21:58.460> using<00:21:58.640> the<00:21:58.880> open<00:21:59.090> source 00:21:59.110 --> 00:21:59.120 align:start position:0% one of them we're using the open source 00:21:59.120 --> 00:22:02.740 align:start position:0% one of them we're using the open source here<00:21:59.570> girl<00:21:59.870> it's<00:22:00.140> a<00:22:00.740> tracer<00:22:01.610> that<00:22:01.640> hooks<00:22:02.600> up 00:22:02.740 --> 00:22:02.750 align:start position:0% here girl it's a tracer that hooks up 00:22:02.750 --> 00:22:04.300 align:start position:0% here girl it's a tracer that hooks up with<00:22:02.810> the<00:22:03.050> Opera<00:22:03.290> tracing<00:22:03.680> framework<00:22:03.890> and 00:22:04.300 --> 00:22:04.310 align:start position:0% with the Opera tracing framework and 00:22:04.310 --> 00:22:07.210 align:start position:0% with the Opera tracing framework and here<00:22:05.090> you<00:22:05.240> can<00:22:05.450> basically<00:22:05.840> see<00:22:06.290> a<00:22:06.740> request 00:22:07.210 --> 00:22:07.220 align:start position:0% here you can basically see a request 00:22:07.220 --> 00:22:09.070 align:start position:0% here you can basically see a request that<00:22:07.670> propagates<00:22:08.150> from<00:22:08.210> one's<00:22:08.510> form<00:22:08.720> not<00:22:08.900> to 00:22:09.070 --> 00:22:09.080 align:start position:0% that propagates from one's form not to 00:22:09.080 --> 00:22:11.290 align:start position:0% that propagates from one's form not to another<00:22:09.320> and<00:22:09.770> helps<00:22:10.280> you<00:22:10.460> get<00:22:10.700> understanding 00:22:11.290 --> 00:22:11.300 align:start position:0% another and helps you get understanding 00:22:11.300 --> 00:22:14.710 align:start position:0% another and helps you get understanding of<00:22:11.750> the<00:22:11.960> underlying<00:22:12.290> protocol<00:22:13.070> I<00:22:13.940> have<00:22:14.600> to 00:22:14.710 --> 00:22:14.720 align:start position:0% of the underlying protocol I have to 00:22:14.720 --> 00:22:16.210 align:start position:0% of the underlying protocol I have to mention<00:22:14.900> that<00:22:15.050> we<00:22:15.320> do<00:22:15.470> this<00:22:15.590> only<00:22:15.770> for<00:22:15.950> debug 00:22:16.210 --> 00:22:16.220 align:start position:0% mention that we do this only for debug 00:22:16.220 --> 00:22:18.880 align:start position:0% mention that we do this only for debug purposes<00:22:16.700> obviously<00:22:17.270> we<00:22:17.420> don't<00:22:17.900> run<00:22:18.590> this<00:22:18.710> in 00:22:18.880 --> 00:22:18.890 align:start position:0% purposes obviously we don't run this in 00:22:18.890 --> 00:22:20.680 align:start position:0% purposes obviously we don't run this in production<00:22:19.040> and<00:22:19.580> you<00:22:19.910> shouldn't<00:22:20.210> really<00:22:20.450> run 00:22:20.680 --> 00:22:20.690 align:start position:0% production and you shouldn't really run 00:22:20.690 --> 00:22:22.120 align:start position:0% production and you shouldn't really run it<00:22:20.750> in<00:22:20.870> production<00:22:21.020> but<00:22:21.500> it<00:22:21.650> helps<00:22:21.950> for 00:22:22.120 --> 00:22:22.130 align:start position:0% it in production but it helps for 00:22:22.130 --> 00:22:24.790 align:start position:0% it in production but it helps for development<00:22:23.030> purposes<00:22:23.300> and<00:22:23.870> if<00:22:24.560> you're 00:22:24.790 --> 00:22:24.800 align:start position:0% development purposes and if you're 00:22:24.800 --> 00:22:27.160 align:start position:0% development purposes and if you're building<00:22:25.010> on<00:22:25.310> top<00:22:25.490> of<00:22:25.550> swarm<00:22:25.910> these<00:22:26.450> tools<00:22:26.900> are 00:22:27.160 --> 00:22:27.170 align:start position:0% building on top of swarm these tools are 00:22:27.170 --> 00:22:30.040 align:start position:0% building on top of swarm these tools are available<00:22:27.500> for<00:22:27.860> you<00:22:28.130> to<00:22:28.310> use<00:22:28.550> and<00:22:29.090> basically 00:22:30.040 --> 00:22:30.050 align:start position:0% available for you to use and basically 00:22:30.050 --> 00:22:33.130 align:start position:0% available for you to use and basically gain<00:22:30.260> visibility<00:22:31.180> the<00:22:32.180> other<00:22:32.300> one<00:22:32.510> is<00:22:32.750> the 00:22:33.130 --> 00:22:33.140 align:start position:0% gain visibility the other one is the 00:22:33.140 --> 00:22:36.690 align:start position:0% gain visibility the other one is the aggregate<00:22:33.470> logging<00:22:33.980> so<00:22:34.540> as<00:22:35.540> I<00:22:35.750> said<00:22:35.960> we<00:22:36.080> have 00:22:36.690 --> 00:22:36.700 align:start position:0% aggregate logging so as I said we have 00:22:36.700 --> 00:22:39.580 align:start position:0% aggregate logging so as I said we have request<00:22:37.700> identifiers<00:22:38.240> so<00:22:38.690> correlation<00:22:38.990> IDs 00:22:39.580 --> 00:22:39.590 align:start position:0% request identifiers so correlation IDs 00:22:39.590 --> 00:22:42.460 align:start position:0% request identifiers so correlation IDs and<00:22:39.980> we<00:22:40.130> can<00:22:40.310> trace<00:22:40.580> requests<00:22:41.300> from<00:22:41.630> one 00:22:42.460 --> 00:22:42.470 align:start position:0% and we can trace requests from one 00:22:42.470 --> 00:22:46.270 align:start position:0% and we can trace requests from one internal<00:22:43.010> API<00:22:43.370> to<00:22:43.910> another<00:22:44.180> and<00:22:45.070> also<00:22:46.070> track 00:22:46.270 --> 00:22:46.280 align:start position:0% internal API to another and also track 00:22:46.280 --> 00:22:50.230 align:start position:0% internal API to another and also track them<00:22:46.460> across<00:22:46.910> different<00:22:47.660> nodes<00:22:48.940> all<00:22:49.940> those 00:22:50.230 --> 00:22:50.240 align:start position:0% them across different nodes all those 00:22:50.240 --> 00:22:53.080 align:start position:0% them across different nodes all those tools<00:22:50.570> are<00:22:50.920> available<00:22:51.920> within<00:22:52.520> the<00:22:52.730> repo 00:22:53.080 --> 00:22:53.090 align:start position:0% tools are available within the repo 00:22:53.090 --> 00:22:56.050 align:start position:0% tools are available within the repo there<00:22:53.420> is<00:22:53.650> swarm<00:22:54.650> readme<00:22:55.220> so<00:22:55.550> if<00:22:55.880> you're 00:22:56.050 --> 00:22:56.060 align:start position:0% there is swarm readme so if you're 00:22:56.060 --> 00:22:59.200 align:start position:0% there is swarm readme so if you're building<00:22:56.450> to<00:22:57.080> some<00:22:57.440> type<00:22:57.980> of<00:22:58.010> storm<00:22:58.400> this<00:22:58.910> will 00:22:59.200 --> 00:22:59.210 align:start position:0% building to some type of storm this will 00:22:59.210 --> 00:23:01.060 align:start position:0% building to some type of storm this will be<00:22:59.360> highly<00:22:59.810> useful<00:22:59.930> for<00:23:00.320> you<00:23:00.410> to<00:23:00.440> answer<00:23:00.950> the 00:23:01.060 --> 00:23:01.070 align:start position:0% be highly useful for you to answer the 00:23:01.070 --> 00:23:03.220 align:start position:0% be highly useful for you to answer the question<00:23:01.430> what<00:23:01.550> yours<00:23:01.790> forum<00:23:02.150> is<00:23:02.300> doing<00:23:03.050> can 00:23:03.220 --> 00:23:03.230 align:start position:0% question what yours forum is doing can 00:23:03.230 --> 00:23:06.580 align:start position:0% question what yours forum is doing can basically<00:23:03.470> gain<00:23:03.860> visibility<00:23:04.220> over<00:23:04.640> it<00:23:05.590> so 00:23:06.580 --> 00:23:06.590 align:start position:0% basically gain visibility over it so 00:23:06.590 --> 00:23:11.220 align:start position:0% basically gain visibility over it so next<00:23:08.080> yeah<00:23:09.080> thanks 00:23:11.220 --> 00:23:11.230 align:start position:0% next yeah thanks 00:23:11.230 --> 00:23:13.750 align:start position:0% next yeah thanks that's<00:23:12.230> actually<00:23:12.620> I<00:23:12.800> mean<00:23:13.130> it<00:23:13.250> sounds<00:23:13.610> you 00:23:13.750 --> 00:23:13.760 align:start position:0% that's actually I mean it sounds you 00:23:13.760 --> 00:23:15.130 align:start position:0% that's actually I mean it sounds you know<00:23:13.880> it<00:23:13.970> sounds<00:23:14.270> just<00:23:14.330> like<00:23:14.540> looking<00:23:14.780> at<00:23:14.900> logs 00:23:15.130 --> 00:23:15.140 align:start position:0% know it sounds just like looking at logs 00:23:15.140 --> 00:23:16.450 align:start position:0% know it sounds just like looking at logs but<00:23:15.320> that's<00:23:15.470> actually<00:23:15.590> really<00:23:15.890> cool<00:23:16.130> stuff 00:23:16.450 --> 00:23:16.460 align:start position:0% but that's actually really cool stuff 00:23:16.460 --> 00:23:18.340 align:start position:0% but that's actually really cool stuff when<00:23:16.790> like<00:23:17.090> you<00:23:17.360> see<00:23:17.540> an<00:23:17.660> action<00:23:17.960> triggered<00:23:18.260> in 00:23:18.340 --> 00:23:18.350 align:start position:0% when like you see an action triggered in 00:23:18.350 --> 00:23:20.290 align:start position:0% when like you see an action triggered in one<00:23:18.500> node<00:23:18.710> on<00:23:19.280> to<00:23:19.490> the<00:23:19.580> next<00:23:19.790> on<00:23:19.940> to<00:23:20.030> the<00:23:20.120> next 00:23:20.290 --> 00:23:20.300 align:start position:0% one node on to the next on to the next 00:23:20.300 --> 00:23:21.760 align:start position:0% one node on to the next on to the next time<00:23:20.480> so<00:23:20.570> next<00:23:20.780> you<00:23:20.870> can<00:23:20.990> track<00:23:21.260> like<00:23:21.620> the 00:23:21.760 --> 00:23:21.770 align:start position:0% time so next you can track like the 00:23:21.770 --> 00:23:23.320 align:start position:0% time so next you can track like the action<00:23:22.070> throughout<00:23:22.310> the<00:23:22.460> entire<00:23:22.730> network<00:23:22.940> if 00:23:23.320 --> 00:23:23.330 align:start position:0% action throughout the entire network if 00:23:23.330 --> 00:23:24.550 align:start position:0% action throughout the entire network if you<00:23:23.360> miss<00:23:23.600> that<00:23:23.750> that's<00:23:23.960> what<00:23:24.140> this<00:23:24.260> is<00:23:24.320> doing 00:23:24.550 --> 00:23:24.560 align:start position:0% you miss that that's what this is doing 00:23:24.560 --> 00:23:26.590 align:start position:0% you miss that that's what this is doing so<00:23:24.830> it's<00:23:24.950> really<00:23:25.190> cool<00:23:25.910> view<00:23:26.120> of<00:23:26.240> what's<00:23:26.390> going 00:23:26.590 --> 00:23:26.600 align:start position:0% so it's really cool view of what's going 00:23:26.600 --> 00:23:29.260 align:start position:0% so it's really cool view of what's going on<00:23:27.130> talking<00:23:28.130> of<00:23:28.280> moving<00:23:28.550> things<00:23:28.670> from<00:23:28.910> node<00:23:29.090> to 00:23:29.260 --> 00:23:29.270 align:start position:0% on talking of moving things from node to 00:23:29.270 --> 00:23:32.700 align:start position:0% on talking of moving things from node to node<00:23:29.300> our<00:23:29.840> next<00:23:30.230> speaker<00:23:30.530> is<00:23:30.560> Lewis<00:23:31.010> about<00:23:31.340> PSS 00:23:32.700 --> 00:23:32.710 align:start position:0% node our next speaker is Lewis about PSS 00:23:32.710 --> 00:23:35.139 align:start position:0% node our next speaker is Lewis about PSS hello<00:23:33.710> everyone 00:23:35.139 --> 00:23:35.149 align:start position:0% hello everyone 00:23:35.149 --> 00:23:39.919 align:start position:0% hello everyone how<00:23:36.149> does<00:23:36.330> this<00:23:36.450> work<00:23:37.730> the<00:23:38.730> green<00:23:39.450> button<00:23:39.899> to 00:23:39.919 --> 00:23:39.929 align:start position:0% how does this work the green button to 00:23:39.929 --> 00:23:41.690 align:start position:0% how does this work the green button to go<00:23:40.109> forward<00:23:40.470> and<00:23:40.649> the<00:23:40.830> red<00:23:40.980> to<00:23:41.190> go<00:23:41.309> backward 00:23:41.690 --> 00:23:41.700 align:start position:0% go forward and the red to go backward 00:23:41.700 --> 00:23:43.759 align:start position:0% go forward and the red to go backward this<00:23:42.269> is<00:23:42.389> pretty<00:23:42.570> clear<00:23:42.899> hello<00:23:43.320> I'm<00:23:43.619> Lois 00:23:43.759 --> 00:23:43.769 align:start position:0% this is pretty clear hello I'm Lois 00:23:43.769 --> 00:23:47.090 align:start position:0% this is pretty clear hello I'm Lois Holbrook<00:23:44.340> I'm<00:23:45.200> responsible<00:23:46.200> or<00:23:46.769> maybe<00:23:47.009> a 00:23:47.090 --> 00:23:47.100 align:start position:0% Holbrook I'm responsible or maybe a 00:23:47.100 --> 00:23:49.129 align:start position:0% Holbrook I'm responsible or maybe a responsible<00:23:47.789> party<00:23:48.179> of<00:23:48.330> the<00:23:48.450> implementation 00:23:49.129 --> 00:23:49.139 align:start position:0% responsible party of the implementation 00:23:49.139 --> 00:23:53.680 align:start position:0% responsible party of the implementation of<00:23:49.350> PSS<00:23:50.159> and<00:23:50.549> PSS<00:23:51.059> as<00:23:51.899> Erin<00:23:52.470> said<00:23:53.190> earlier 00:23:53.680 --> 00:23:53.690 align:start position:0% of PSS and PSS as Erin said earlier 00:23:53.690 --> 00:23:56.960 align:start position:0% of PSS and PSS as Erin said earlier messaging<00:23:54.690> platform<00:23:55.169> that<00:23:55.320> piggybacks<00:23:55.970> the 00:23:56.960 --> 00:23:56.970 align:start position:0% messaging platform that piggybacks the 00:23:56.970 --> 00:24:00.830 align:start position:0% messaging platform that piggybacks the doesn't<00:23:57.749> work<00:23:57.840> or<00:23:58.820> that<00:23:59.820> green<00:24:00.149> button<00:24:00.330> I<00:24:00.629> see 00:24:00.830 --> 00:24:00.840 align:start position:0% doesn't work or that green button I see 00:24:00.840 --> 00:24:04.369 align:start position:0% doesn't work or that green button I see yeah<00:24:01.590> that<00:24:01.859> piggybacks<00:24:02.580> to<00:24:02.970> swarm<00:24:03.379> routing 00:24:04.369 --> 00:24:04.379 align:start position:0% yeah that piggybacks to swarm routing 00:24:04.379 --> 00:24:07.879 align:start position:0% yeah that piggybacks to swarm routing mechanism<00:24:05.009> to<00:24:05.159> send<00:24:05.399> ephemeral<00:24:06.090> data<00:24:06.889> across 00:24:07.879 --> 00:24:07.889 align:start position:0% mechanism to send ephemeral data across 00:24:07.889 --> 00:24:11.349 align:start position:0% mechanism to send ephemeral data across the<00:24:08.249> across<00:24:08.879> the<00:24:09.090> network<00:24:09.889> enter<00:24:10.889> node 00:24:11.349 --> 00:24:11.359 align:start position:0% the across the network enter node 00:24:11.359 --> 00:24:15.799 align:start position:0% the across the network enter node messaging<00:24:12.769> and<00:24:13.769> what<00:24:14.730> does<00:24:14.909> that<00:24:14.940> mean<00:24:15.359> well 00:24:15.799 --> 00:24:15.809 align:start position:0% messaging and what does that mean well 00:24:15.809 --> 00:24:20.930 align:start position:0% messaging and what does that mean well it<00:24:15.840> means<00:24:16.169> that<00:24:16.559> we<00:24:19.129> that<00:24:20.129> we<00:24:20.399> increase<00:24:20.669> the 00:24:20.930 --> 00:24:20.940 align:start position:0% it means that we that we increase the 00:24:20.940 --> 00:24:24.489 align:start position:0% it means that we that we increase the efficiency<00:24:21.480> of<00:24:21.509> delivering<00:24:22.289> messages<00:24:22.440> and 00:24:24.489 --> 00:24:24.499 align:start position:0% efficiency of delivering messages and 00:24:24.499 --> 00:24:28.279 align:start position:0% efficiency of delivering messages and therefore<00:24:26.090> it<00:24:27.090> comes<00:24:27.359> at<00:24:27.690> the<00:24:27.840> expense<00:24:27.869> of 00:24:28.279 --> 00:24:28.289 align:start position:0% therefore it comes at the expense of 00:24:28.289 --> 00:24:30.229 align:start position:0% therefore it comes at the expense of secrecy<00:24:28.649> so<00:24:28.980> this<00:24:29.249> answers<00:24:29.669> a<00:24:29.700> question<00:24:29.879> that 00:24:30.229 --> 00:24:30.239 align:start position:0% secrecy so this answers a question that 00:24:30.239 --> 00:24:31.970 align:start position:0% secrecy so this answers a question that a<00:24:30.269> lot<00:24:30.450> of<00:24:30.480> people<00:24:30.869> answer<00:24:31.200> to<00:24:31.379> a<00:24:31.409> lot<00:24:31.950> of 00:24:31.970 --> 00:24:31.980 align:start position:0% a lot of people answer to a lot of 00:24:31.980 --> 00:24:33.889 align:start position:0% a lot of people answer to a lot of people<00:24:32.309> asks<00:24:32.669> and<00:24:32.820> really<00:24:32.970> about<00:24:33.179> why<00:24:33.629> do<00:24:33.690> we 00:24:33.889 --> 00:24:33.899 align:start position:0% people asks and really about why do we 00:24:33.899 --> 00:24:35.479 align:start position:0% people asks and really about why do we need<00:24:34.019> this<00:24:34.259> PSS<00:24:34.739> thing<00:24:35.009> when<00:24:35.190> we<00:24:35.279> have<00:24:35.429> the 00:24:35.479 --> 00:24:35.489 align:start position:0% need this PSS thing when we have the 00:24:35.489 --> 00:24:36.859 align:start position:0% need this PSS thing when we have the whispers<00:24:35.909> and<00:24:35.940> whisper<00:24:36.389> the<00:24:36.480> messaging 00:24:36.859 --> 00:24:36.869 align:start position:0% whispers and whisper the messaging 00:24:36.869 --> 00:24:39.859 align:start position:0% whispers and whisper the messaging platform<00:24:37.320> of<00:24:37.759> etherium<00:24:38.759> well<00:24:39.419> that's<00:24:39.720> your 00:24:39.859 --> 00:24:39.869 align:start position:0% platform of etherium well that's your 00:24:39.869 --> 00:24:42.919 align:start position:0% platform of etherium well that's your answer<00:24:39.989> that<00:24:40.440> is<00:24:41.039> whisper<00:24:41.730> primarily<00:24:42.480> focused 00:24:42.919 --> 00:24:42.929 align:start position:0% answer that is whisper primarily focused 00:24:42.929 --> 00:24:45.460 align:start position:0% answer that is whisper primarily focused on<00:24:43.049> the<00:24:43.109> property<00:24:43.889> of<00:24:44.039> privacy<00:24:44.460> in<00:24:44.549> darkness 00:24:45.460 --> 00:24:45.470 align:start position:0% on the property of privacy in darkness 00:24:45.470 --> 00:24:48.139 align:start position:0% on the property of privacy in darkness PSS<00:24:46.470> gives<00:24:46.980> you<00:24:47.159> the<00:24:47.279> possibility<00:24:47.429> to 00:24:48.139 --> 00:24:48.149 align:start position:0% PSS gives you the possibility to 00:24:48.149 --> 00:24:50.149 align:start position:0% PSS gives you the possibility to actually<00:24:48.299> efficiently<00:24:49.080> efficiently<00:24:49.919> root 00:24:50.149 --> 00:24:50.159 align:start position:0% actually efficiently efficiently root 00:24:50.159 --> 00:24:52.609 align:start position:0% actually efficiently efficiently root over<00:24:50.369> the<00:24:50.609> over<00:24:51.269> the<00:24:51.299> network<00:24:51.450> and<00:24:52.109> since<00:24:52.470> we 00:24:52.609 --> 00:24:52.619 align:start position:0% over the over the network and since we 00:24:52.619 --> 00:24:54.229 align:start position:0% over the over the network and since we all<00:24:52.710> know<00:24:52.739> that<00:24:53.009> there<00:24:53.190> are<00:24:53.369> no<00:24:53.700> such<00:24:53.940> things 00:24:54.229 --> 00:24:54.239 align:start position:0% all know that there are no such things 00:24:54.239 --> 00:24:56.119 align:start position:0% all know that there are no such things as<00:24:54.450> ninja<00:24:55.080> mail<00:24:55.259> man<00:24:55.470> you<00:24:55.619> kinda<00:24:55.919> have<00:24:56.100> to 00:24:56.119 --> 00:24:56.129 align:start position:0% as ninja mail man you kinda have to 00:24:56.129 --> 00:24:58.999 align:start position:0% as ninja mail man you kinda have to choose<00:24:56.669> between<00:24:56.970> one<00:24:57.330> or<00:24:57.359> the<00:24:57.570> other 00:24:58.999 --> 00:24:59.009 align:start position:0% choose between one or the other 00:24:59.009 --> 00:25:02.659 align:start position:0% choose between one or the other all<00:24:59.609> nodes<00:25:00.299> and<00:25:00.749> swarm<00:25:01.200> take<00:25:01.649> part<00:25:02.070> in<00:25:02.399> this 00:25:02.659 --> 00:25:02.669 align:start position:0% all nodes and swarm take part in this 00:25:02.669 --> 00:25:06.859 align:start position:0% all nodes and swarm take part in this routing<00:25:03.210> so<00:25:03.889> and<00:25:04.889> it's<00:25:05.730> also<00:25:06.149> unveiled<00:25:06.749> by 00:25:06.859 --> 00:25:06.869 align:start position:0% routing so and it's also unveiled by 00:25:06.869 --> 00:25:09.619 align:start position:0% routing so and it's also unveiled by default<00:25:07.259> so<00:25:07.440> you<00:25:07.470> can't<00:25:07.769> deactivate<00:25:08.299> PSS<00:25:09.299> from 00:25:09.619 --> 00:25:09.629 align:start position:0% default so you can't deactivate PSS from 00:25:09.629 --> 00:25:12.440 align:start position:0% default so you can't deactivate PSS from swarm<00:25:09.989> as<00:25:10.289> such<00:25:10.529> so<00:25:11.429> what<00:25:11.909> are<00:25:12.119> the<00:25:12.330> general 00:25:12.440 --> 00:25:12.450 align:start position:0% swarm as such so what are the general 00:25:12.450 --> 00:25:15.409 align:start position:0% swarm as such so what are the general features<00:25:12.779> of<00:25:12.989> swarm<00:25:13.470> well<00:25:13.739> first<00:25:14.100> of<00:25:14.279> all<00:25:14.419> this 00:25:15.409 --> 00:25:15.419 align:start position:0% features of swarm well first of all this 00:25:15.419 --> 00:25:18.619 align:start position:0% features of swarm well first of all this is<00:25:15.629> not<00:25:15.779> really<00:25:16.019> a<00:25:16.049> feature<00:25:16.350> but<00:25:16.879> I<00:25:17.879> already 00:25:18.619 --> 00:25:18.629 align:start position:0% is not really a feature but I already 00:25:18.629 --> 00:25:20.419 align:start position:0% is not really a feature but I already did<00:25:18.989> a<00:25:19.019> couple<00:25:19.139> of<00:25:19.289> talks<00:25:19.499> on<00:25:19.649> PSS<00:25:20.100> they<00:25:20.340> have 00:25:20.419 --> 00:25:20.429 align:start position:0% did a couple of talks on PSS they have 00:25:20.429 --> 00:25:21.830 align:start position:0% did a couple of talks on PSS they have gone<00:25:20.609> last<00:25:20.850> year<00:25:21.149> that's<00:25:21.330> why<00:25:21.480> I<00:25:21.509> won't<00:25:21.749> go 00:25:21.830 --> 00:25:21.840 align:start position:0% gone last year that's why I won't go 00:25:21.840 --> 00:25:23.239 align:start position:0% gone last year that's why I won't go into<00:25:21.989> technical<00:25:22.320> details<00:25:22.470> about<00:25:23.009> how<00:25:23.129> it 00:25:23.239 --> 00:25:23.249 align:start position:0% into technical details about how it 00:25:23.249 --> 00:25:25.940 align:start position:0% into technical details about how it works<00:25:23.460> but<00:25:23.940> at<00:25:24.090> that<00:25:24.299> time<00:25:24.720> it<00:25:25.019> was<00:25:25.440> in<00:25:25.470> a<00:25:25.739> very 00:25:25.940 --> 00:25:25.950 align:start position:0% works but at that time it was in a very 00:25:25.950 --> 00:25:28.220 align:start position:0% works but at that time it was in a very obscure<00:25:26.399> branch<00:25:26.669> in<00:25:26.909> development<00:25:27.389> since<00:25:27.720> then 00:25:28.220 --> 00:25:28.230 align:start position:0% obscure branch in development since then 00:25:28.230 --> 00:25:30.139 align:start position:0% obscure branch in development since then it's<00:25:28.470> actually<00:25:28.649> merged<00:25:29.190> into<00:25:29.489> main<00:25:29.759> code<00:25:29.970> base 00:25:30.139 --> 00:25:30.149 align:start position:0% it's actually merged into main code base 00:25:30.149 --> 00:25:32.029 align:start position:0% it's actually merged into main code base so<00:25:30.389> that<00:25:30.600> means<00:25:31.200> that<00:25:31.409> when<00:25:31.559> you<00:25:31.649> download<00:25:31.799> a 00:25:32.029 --> 00:25:32.039 align:start position:0% so that means that when you download a 00:25:32.039 --> 00:25:34.609 align:start position:0% so that means that when you download a swarm<00:25:32.340> binary<00:25:32.730> this<00:25:33.149> actually<00:25:33.659> has<00:25:33.840> PSS<00:25:34.409> and 00:25:34.609 --> 00:25:34.619 align:start position:0% swarm binary this actually has PSS and 00:25:34.619 --> 00:25:36.109 align:start position:0% swarm binary this actually has PSS and stuff<00:25:34.799> in<00:25:35.009> there<00:25:35.159> it<00:25:35.399> also<00:25:35.580> means<00:25:35.850> that<00:25:35.940> it 00:25:36.109 --> 00:25:36.119 align:start position:0% stuff in there it also means that it 00:25:36.119 --> 00:25:38.930 align:start position:0% stuff in there it also means that it passed<00:25:36.330> some<00:25:36.570> tests<00:25:37.369> which<00:25:38.369> is<00:25:38.399> good<00:25:38.759> news 00:25:38.930 --> 00:25:38.940 align:start position:0% passed some tests which is good news 00:25:38.940 --> 00:25:43.399 align:start position:0% passed some tests which is good news right<00:25:40.759> so<00:25:41.759> what<00:25:42.299> does<00:25:42.419> it<00:25:42.570> provide<00:25:42.840> custom 00:25:43.399 --> 00:25:43.409 align:start position:0% right so what does it provide custom 00:25:43.409 --> 00:25:46.210 align:start position:0% right so what does it provide custom luminosity<00:25:43.980> so<00:25:44.190> I<00:25:44.399> said<00:25:44.789> the 00:25:46.210 --> 00:25:46.220 align:start position:0% luminosity so I said the 00:25:46.220 --> 00:25:48.159 align:start position:0% luminosity so I said the DSS<00:25:47.029> gives<00:25:47.239> you<00:25:47.389> the<00:25:47.509> possibility<00:25:48.139> of 00:25:48.159 --> 00:25:48.169 align:start position:0% DSS gives you the possibility of 00:25:48.169 --> 00:25:50.350 align:start position:0% DSS gives you the possibility of efficiently<00:25:48.889> routing<00:25:49.279> so<00:25:49.549> it<00:25:49.759> means<00:25:50.029> that 00:25:50.350 --> 00:25:50.360 align:start position:0% efficiently routing so it means that 00:25:50.360 --> 00:25:56.320 align:start position:0% efficiently routing so it means that what<00:25:50.720> happened<00:25:51.049> now<00:25:54.669> yes<00:25:55.669> I<00:25:55.879> thought<00:25:56.090> well 00:25:56.320 --> 00:25:56.330 align:start position:0% what happened now yes I thought well 00:25:56.330 --> 00:25:57.940 align:start position:0% what happened now yes I thought well anyway<00:25:56.690> so<00:25:56.869> it<00:25:57.289> gives<00:25:57.499> you<00:25:57.649> the<00:25:57.769> possibility 00:25:57.940 --> 00:25:57.950 align:start position:0% anyway so it gives you the possibility 00:25:57.950 --> 00:26:01.060 align:start position:0% anyway so it gives you the possibility to<00:25:58.450> define<00:25:59.450> exactly<00:25:59.690> which<00:26:00.320> address<00:26:00.830> in<00:26:00.980> the 00:26:01.060 --> 00:26:01.070 align:start position:0% to define exactly which address in the 00:26:01.070 --> 00:26:02.820 align:start position:0% to define exactly which address in the network<00:26:01.399> you<00:26:01.549> want<00:26:01.580> to<00:26:01.820> send<00:26:02.059> the<00:26:02.149> message<00:26:02.419> to 00:26:02.820 --> 00:26:02.830 align:start position:0% network you want to send the message to 00:26:02.830 --> 00:26:07.029 align:start position:0% network you want to send the message to in<00:26:03.830> this<00:26:04.070> case<00:26:04.309> it<00:26:04.999> will<00:26:05.239> it<00:26:05.480> will<00:26:05.929> it<00:26:06.619> will 00:26:07.029 --> 00:26:07.039 align:start position:0% in this case it will it will it will 00:26:07.039 --> 00:26:08.830 align:start position:0% in this case it will it will it will reach<00:26:07.249> the<00:26:07.279> message<00:26:07.879> in<00:26:08.059> maximum<00:26:08.629> of<00:26:08.809> a 00:26:08.830 --> 00:26:08.840 align:start position:0% reach the message in maximum of a 00:26:08.840 --> 00:26:11.649 align:start position:0% reach the message in maximum of a logarithmic<00:26:09.259> ops<00:26:09.590> of<00:26:09.830> the<00:26:10.039> address<00:26:10.309> space<00:26:10.659> but 00:26:11.649 --> 00:26:11.659 align:start position:0% logarithmic ops of the address space but 00:26:11.659 --> 00:26:12.970 align:start position:0% logarithmic ops of the address space but it<00:26:11.749> also<00:26:11.899> gives<00:26:12.169> you<00:26:12.289> the<00:26:12.350> possibility<00:26:12.529> of 00:26:12.970 --> 00:26:12.980 align:start position:0% it also gives you the possibility of 00:26:12.980 --> 00:26:16.119 align:start position:0% it also gives you the possibility of partially<00:26:13.940> selecting<00:26:14.450> an<00:26:14.539> address<00:26:14.899> or<00:26:15.259> not 00:26:16.119 --> 00:26:16.129 align:start position:0% partially selecting an address or not 00:26:16.129 --> 00:26:18.220 align:start position:0% partially selecting an address or not selecting<00:26:16.669> matters<00:26:17.029> at<00:26:17.149> all<00:26:17.239> now<00:26:17.989> not 00:26:18.220 --> 00:26:18.230 align:start position:0% selecting matters at all now not 00:26:18.230 --> 00:26:20.109 align:start position:0% selecting matters at all now not selecting<00:26:18.710> a<00:26:18.799> dissolve<00:26:19.159> would<00:26:19.399> be<00:26:19.789> gave<00:26:19.999> it 00:26:20.109 --> 00:26:20.119 align:start position:0% selecting a dissolve would be gave it 00:26:20.119 --> 00:26:21.639 align:start position:0% selecting a dissolve would be gave it the<00:26:20.179> same<00:26:20.210> consequences<00:26:20.629> whisper<00:26:21.259> it<00:26:21.440> would 00:26:21.639 --> 00:26:21.649 align:start position:0% the same consequences whisper it would 00:26:21.649 --> 00:26:23.279 align:start position:0% the same consequences whisper it would be<00:26:21.739> spread<00:26:22.039> all<00:26:22.309> over<00:26:22.340> in<00:26:22.519> the<00:26:22.580> network<00:26:22.909> and 00:26:23.279 --> 00:26:23.289 align:start position:0% be spread all over in the network and 00:26:23.289 --> 00:26:25.419 align:start position:0% be spread all over in the network and whoever<00:26:24.289> can<00:26:24.499> decrypt<00:26:24.739> the<00:26:24.919> message<00:26:25.220> for 00:26:25.419 --> 00:26:25.429 align:start position:0% whoever can decrypt the message for 00:26:25.429 --> 00:26:26.769 align:start position:0% whoever can decrypt the message for example<00:26:25.820> list<00:26:25.970> and<00:26:26.179> tend<00:26:26.359> to<00:26:26.389> do<00:26:26.509> so<00:26:26.539> the 00:26:26.769 --> 00:26:26.779 align:start position:0% example list and tend to do so the 00:26:26.779 --> 00:26:28.629 align:start position:0% example list and tend to do so the recipient<00:26:27.080> still<00:26:27.830> no<00:26:27.980> slide<00:26:28.220> I<00:26:28.399> don't<00:26:28.580> know 00:26:28.629 --> 00:26:28.639 align:start position:0% recipient still no slide I don't know 00:26:28.639 --> 00:26:33.909 align:start position:0% recipient still no slide I don't know what's<00:26:28.789> going<00:26:28.970> on<00:26:29.440> and<00:26:30.440> oh<00:26:32.049> I<00:26:33.049> see<00:26:33.559> so<00:26:33.739> I<00:26:33.799> have 00:26:33.909 --> 00:26:33.919 align:start position:0% what's going on and oh I see so I have 00:26:33.919 --> 00:26:35.139 align:start position:0% what's going on and oh I see so I have to<00:26:34.009> remember<00:26:34.220> what<00:26:34.460> the<00:26:34.489> slides<00:26:34.759> are<00:26:34.909> that's 00:26:35.139 --> 00:26:35.149 align:start position:0% to remember what the slides are that's 00:26:35.149 --> 00:26:39.580 align:start position:0% to remember what the slides are that's pretty<00:26:35.359> cool<00:26:35.830> and<00:26:37.869> parcel<00:26:38.869> addressing<00:26:39.379> could 00:26:39.580 --> 00:26:39.590 align:start position:0% pretty cool and parcel addressing could 00:26:39.590 --> 00:26:41.560 align:start position:0% pretty cool and parcel addressing could be<00:26:39.739> you<00:26:39.980> know<00:26:40.100> for<00:26:40.309> example<00:26:40.369> you<00:26:40.909> send<00:26:41.330> in<00:26:41.480> that 00:26:41.560 --> 00:26:41.570 align:start position:0% be you know for example you send in that 00:26:41.570 --> 00:26:44.259 align:start position:0% be you know for example you send in that a<00:26:41.869> message<00:26:42.470> to<00:26:42.679> Prague<00:26:43.009> or<00:26:43.700> you<00:26:43.970> send<00:26:44.179> a 00:26:44.259 --> 00:26:44.269 align:start position:0% a message to Prague or you send a 00:26:44.269 --> 00:26:45.580 align:start position:0% a message to Prague or you send a message<00:26:44.359> to<00:26:44.539> the<00:26:44.720> Convention<00:26:45.169> Center<00:26:45.499> in 00:26:45.580 --> 00:26:45.590 align:start position:0% message to the Convention Center in 00:26:45.590 --> 00:26:48.070 align:start position:0% message to the Convention Center in Prague<00:26:45.830> or<00:26:46.190> you<00:26:46.429> send<00:26:46.669> a<00:26:46.789> message<00:26:47.090> to<00:26:47.119> Luis<00:26:47.779> at 00:26:48.070 --> 00:26:48.080 align:start position:0% Prague or you send a message to Luis at 00:26:48.080 --> 00:26:49.599 align:start position:0% Prague or you send a message to Luis at the<00:26:48.200> Cancer<00:26:48.559> Center<00:26:48.590> in<00:26:48.919> Prague<00:26:49.129> anomalies 00:26:49.599 --> 00:26:49.609 align:start position:0% the Cancer Center in Prague anomalies 00:26:49.609 --> 00:26:51.580 align:start position:0% the Cancer Center in Prague anomalies Luis<00:26:50.029> because<00:26:50.389> I'm<00:26:50.570> selfish<00:26:50.989> that's<00:26:51.259> my<00:26:51.409> name 00:26:51.580 --> 00:26:51.590 align:start position:0% Luis because I'm selfish that's my name 00:26:51.590 --> 00:26:52.960 align:start position:0% Luis because I'm selfish that's my name and<00:26:51.739> I<00:26:52.070> know<00:26:52.129> there<00:26:52.429> happens<00:26:52.730> to<00:26:52.789> be<00:26:52.850> another 00:26:52.960 --> 00:26:52.970 align:start position:0% and I know there happens to be another 00:26:52.970 --> 00:26:55.599 align:start position:0% and I know there happens to be another Luis<00:26:53.480> here<00:26:53.809> at<00:26:53.989> the<00:26:54.109> conference<00:26:54.320> or<00:26:55.129> you<00:26:55.460> could 00:26:55.599 --> 00:26:55.609 align:start position:0% Luis here at the conference or you could 00:26:55.609 --> 00:26:58.629 align:start position:0% Luis here at the conference or you could say<00:26:55.820> Luis<00:26:56.570> with<00:26:56.899> the<00:26:57.320> fried<00:26:57.590> egg<00:26:57.859> tie<00:26:58.159> at<00:26:58.429> the 00:26:58.629 --> 00:26:58.639 align:start position:0% say Luis with the fried egg tie at the 00:26:58.639 --> 00:27:00.039 align:start position:0% say Luis with the fried egg tie at the convention<00:26:59.059> center<00:26:59.450> in<00:26:59.539> Prague<00:26:59.779> which 00:27:00.039 --> 00:27:00.049 align:start position:0% convention center in Prague which 00:27:00.049 --> 00:27:01.749 align:start position:0% convention center in Prague which probably<00:27:00.499> pretty<00:27:01.129> much<00:27:01.340> would<00:27:01.519> narrow<00:27:01.669> it 00:27:01.749 --> 00:27:01.759 align:start position:0% probably pretty much would narrow it 00:27:01.759 --> 00:27:02.919 align:start position:0% probably pretty much would narrow it down<00:27:01.789> to<00:27:02.029> me<00:27:02.179> and<00:27:02.359> that<00:27:02.450> would<00:27:02.539> be<00:27:02.629> the<00:27:02.749> full 00:27:02.919 --> 00:27:02.929 align:start position:0% down to me and that would be the full 00:27:02.929 --> 00:27:06.700 align:start position:0% down to me and that would be the full address<00:27:03.139> oh<00:27:03.609> they're<00:27:04.609> back<00:27:04.759> and<00:27:05.119> I<00:27:05.590> let's<00:27:06.590> see 00:27:06.700 --> 00:27:06.710 align:start position:0% address oh they're back and I let's see 00:27:06.710 --> 00:27:10.720 align:start position:0% address oh they're back and I let's see we<00:27:07.429> can<00:27:07.639> go<00:27:07.759> back<00:27:07.999> right<00:27:08.779> swarm<00:27:09.590> has<00:27:09.830> the<00:27:10.309> PSS 00:27:10.720 --> 00:27:10.730 align:start position:0% we can go back right swarm has the PSS 00:27:10.730 --> 00:27:12.489 align:start position:0% we can go back right swarm has the PSS has<00:27:10.879> built<00:27:11.119> an<00:27:11.239> encryption<00:27:11.509> by<00:27:11.720> default<00:27:12.080> so<00:27:12.259> it 00:27:12.489 --> 00:27:12.499 align:start position:0% has built an encryption by default so it 00:27:12.499 --> 00:27:15.310 align:start position:0% has built an encryption by default so it means<00:27:12.710> that<00:27:12.950> it<00:27:13.070> handles<00:27:14.019> generation<00:27:15.019> of<00:27:15.139> keys 00:27:15.310 --> 00:27:15.320 align:start position:0% means that it handles generation of keys 00:27:15.320 --> 00:27:18.460 align:start position:0% means that it handles generation of keys and<00:27:15.619> also<00:27:16.330> sending<00:27:17.330> autumn<00:27:17.690> at<00:27:17.779> all<00:27:18.320> the 00:27:18.460 --> 00:27:18.470 align:start position:0% and also sending autumn at all the 00:27:18.470 --> 00:27:22.269 align:start position:0% and also sending autumn at all the encryption<00:27:18.889> happens<00:27:19.480> behind<00:27:20.480> the<00:27:20.749> API<00:27:21.279> there 00:27:22.269 --> 00:27:22.279 align:start position:0% encryption happens behind the API there 00:27:22.279 --> 00:27:23.619 align:start position:0% encryption happens behind the API there are<00:27:22.340> pluggable<00:27:22.789> called<00:27:22.970> handlers<00:27:23.419> which 00:27:23.619 --> 00:27:23.629 align:start position:0% are pluggable called handlers which 00:27:23.629 --> 00:27:26.259 align:start position:0% are pluggable called handlers which means<00:27:23.840> that<00:27:24.230> for<00:27:25.039> every<00:27:25.129> M<00:27:25.429> so<00:27:25.730> every<00:27:25.970> message 00:27:26.259 --> 00:27:26.269 align:start position:0% means that for every M so every message 00:27:26.269 --> 00:27:28.029 align:start position:0% means that for every M so every message has<00:27:26.450> a<00:27:26.480> certain<00:27:26.899> topic<00:27:27.080> and<00:27:27.440> associated<00:27:27.859> to 00:27:28.029 --> 00:27:28.039 align:start position:0% has a certain topic and associated to 00:27:28.039 --> 00:27:29.560 align:start position:0% has a certain topic and associated to that<00:27:28.190> topic<00:27:28.669> as<00:27:28.850> a<00:27:28.879> recipient 00:27:29.560 --> 00:27:29.570 align:start position:0% that topic as a recipient 00:27:29.570 --> 00:27:31.330 align:start position:0% that topic as a recipient you<00:27:29.929> can<00:27:30.139> register<00:27:30.320> code<00:27:30.950> to<00:27:31.190> be<00:27:31.309> executed 00:27:31.330 --> 00:27:31.340 align:start position:0% you can register code to be executed 00:27:31.340 --> 00:27:33.129 align:start position:0% you can register code to be executed when<00:27:31.970> you<00:27:32.090> get<00:27:32.210> a<00:27:32.239> message<00:27:32.450> for<00:27:32.749> that<00:27:32.840> topic 00:27:33.129 --> 00:27:33.139 align:start position:0% when you get a message for that topic 00:27:33.139 --> 00:27:35.379 align:start position:0% when you get a message for that topic and<00:27:33.619> it<00:27:33.769> can<00:27:33.889> be<00:27:33.980> any<00:27:34.159> number<00:27:34.369> of<00:27:34.730> handlers 00:27:35.379 --> 00:27:35.389 align:start position:0% and it can be any number of handlers 00:27:35.389 --> 00:27:38.499 align:start position:0% and it can be any number of handlers so<00:27:36.259> it's<00:27:36.470> extendable<00:27:37.309> very<00:27:37.519> flexible<00:27:37.970> there 00:27:38.499 --> 00:27:38.509 align:start position:0% so it's extendable very flexible there 00:27:38.509 --> 00:27:41.080 align:start position:0% so it's extendable very flexible there is<00:27:38.779> a<00:27:38.809> handshake<00:27:39.499> module<00:27:39.889> which<00:27:40.159> enables<00:27:40.970> you 00:27:41.080 --> 00:27:41.090 align:start position:0% is a handshake module which enables you 00:27:41.090 --> 00:27:42.759 align:start position:0% is a handshake module which enables you to<00:27:41.149> do<00:27:41.359> diffie-hellman<00:27:41.659> handshakes<00:27:42.440> and 00:27:42.759 --> 00:27:42.769 align:start position:0% to do diffie-hellman handshakes and 00:27:42.769 --> 00:27:45.479 align:start position:0% to do diffie-hellman handshakes and exchange<00:27:43.549> session<00:27:43.940> keys<00:27:44.119> behind-the-scenes 00:27:45.479 --> 00:27:45.489 align:start position:0% exchange session keys behind-the-scenes 00:27:45.489 --> 00:27:47.889 align:start position:0% exchange session keys behind-the-scenes happens<00:27:46.489> automatically<00:27:46.940> the<00:27:47.119> keys<00:27:47.299> are<00:27:47.539> valid 00:27:47.889 --> 00:27:47.899 align:start position:0% happens automatically the keys are valid 00:27:47.899 --> 00:27:49.599 align:start position:0% happens automatically the keys are valid for<00:27:47.929> a<00:27:48.080> certain<00:27:48.440> number<00:27:48.470> of<00:27:48.739> messages<00:27:49.249> and 00:27:49.599 --> 00:27:49.609 align:start position:0% for a certain number of messages and 00:27:49.609 --> 00:27:52.599 align:start position:0% for a certain number of messages and there<00:27:50.090> is<00:27:50.179> also<00:27:50.419> a<00:27:50.929> buffer<00:27:51.710> of<00:27:51.950> keys<00:27:52.220> so<00:27:52.580> that 00:27:52.599 --> 00:27:52.609 align:start position:0% there is also a buffer of keys so that 00:27:52.609 --> 00:27:56.169 align:start position:0% there is also a buffer of keys so that if<00:27:53.239> you<00:27:53.509> run<00:27:53.749> out<00:27:53.779> if<00:27:54.590> you<00:27:54.859> the<00:27:55.609> exchange<00:27:55.970> the 00:27:56.169 --> 00:27:56.179 align:start position:0% if you run out if you the exchange the 00:27:56.179 --> 00:27:57.820 align:start position:0% if you run out if you the exchange the refreshment<00:27:56.720> of<00:27:56.809> keys<00:27:57.019> happen<00:27:57.440> before<00:27:57.710> you 00:27:57.820 --> 00:27:57.830 align:start position:0% refreshment of keys happen before you 00:27:57.830 --> 00:27:58.749 align:start position:0% refreshment of keys happen before you run<00:27:57.980> out<00:27:58.009> of<00:27:58.129> keys<00:27:58.369> so 00:27:58.749 --> 00:27:58.759 align:start position:0% run out of keys so 00:27:58.759 --> 00:28:06.879 align:start position:0% run out of keys so that<00:27:58.909> you<00:27:58.999> won't<00:27:59.179> be<00:27:59.299> stuck<00:27:59.509> if<00:27:59.779> if<00:28:00.399> if<00:28:05.739> so<00:28:06.739> it's 00:28:06.879 --> 00:28:06.889 align:start position:0% that you won't be stuck if if if so it's 00:28:06.889 --> 00:28:13.169 align:start position:0% that you won't be stuck if if if so it's less<00:28:07.009> likely<00:28:07.039> get<00:28:07.579> stuck<00:28:09.159> protocols<00:28:10.159> yes<00:28:10.549> so 00:28:13.169 --> 00:28:13.179 align:start position:0% less likely get stuck protocols yes so 00:28:13.179 --> 00:28:15.639 align:start position:0% less likely get stuck protocols yes so it<00:28:14.179> has<00:28:14.329> a<00:28:14.359> framework<00:28:14.809> so<00:28:15.079> PSS<00:28:15.469> has<00:28:15.619> a 00:28:15.639 --> 00:28:15.649 align:start position:0% it has a framework so PSS has a 00:28:15.649 --> 00:28:17.099 align:start position:0% it has a framework so PSS has a framework<00:28:15.949> for<00:28:16.129> inter<00:28:16.639> machine 00:28:17.099 --> 00:28:17.109 align:start position:0% framework for inter machine 00:28:17.109 --> 00:28:19.930 align:start position:0% framework for inter machine communication<00:28:18.109> it<00:28:18.619> also<00:28:18.919> so<00:28:19.399> happens<00:28:19.879> that 00:28:19.930 --> 00:28:19.940 align:start position:0% communication it also so happens that 00:28:19.940 --> 00:28:21.459 align:start position:0% communication it also so happens that it's<00:28:20.149> assigned<00:28:20.419> away<00:28:20.659> so<00:28:20.719> that<00:28:20.839> if<00:28:21.079> you<00:28:21.259> have 00:28:21.459 --> 00:28:21.469 align:start position:0% it's assigned away so that if you have 00:28:21.469 --> 00:28:24.369 align:start position:0% it's assigned away so that if you have already<00:28:21.739> deal<00:28:22.279> dev<00:28:22.609> p2p<00:28:23.299> protocol<00:28:23.809> that 00:28:24.369 --> 00:28:24.379 align:start position:0% already deal dev p2p protocol that 00:28:24.379 --> 00:28:26.409 align:start position:0% already deal dev p2p protocol that exists<00:28:24.829> between<00:28:24.979> two<00:28:25.279> directly<00:28:25.969> connected 00:28:26.409 --> 00:28:26.419 align:start position:0% exists between two directly connected 00:28:26.419 --> 00:28:29.019 align:start position:0% exists between two directly connected peers<00:28:26.629> directly<00:28:27.349> in<00:28:27.440> the<00:28:27.529> sense<00:28:27.739> of<00:28:27.859> TCP<00:28:28.429> you 00:28:29.019 --> 00:28:29.029 align:start position:0% peers directly in the sense of TCP you 00:28:29.029 --> 00:28:31.479 align:start position:0% peers directly in the sense of TCP you can<00:28:29.239> with<00:28:29.449> minimal<00:28:30.019> minimal<00:28:30.229> code<00:28:30.799> actually 00:28:31.479 --> 00:28:31.489 align:start position:0% can with minimal minimal code actually 00:28:31.489 --> 00:28:37.029 align:start position:0% can with minimal minimal code actually port<00:28:32.059> this<00:28:32.359> to<00:28:32.599> PSS<00:28:34.599> so<00:28:35.599> by<00:28:35.899> newest<00:28:36.319> features<00:28:36.799> I 00:28:37.029 --> 00:28:37.039 align:start position:0% port this to PSS so by newest features I 00:28:37.039 --> 00:28:39.099 align:start position:0% port this to PSS so by newest features I mean<00:28:37.339> so<00:28:37.639> all<00:28:37.819> the<00:28:37.999> stuff<00:28:38.239> that<00:28:38.269> I<00:28:38.479> said<00:28:38.539> now<00:28:38.869> I 00:28:39.099 --> 00:28:39.109 align:start position:0% mean so all the stuff that I said now I 00:28:39.109 --> 00:28:41.799 align:start position:0% mean so all the stuff that I said now I kind<00:28:39.499> of<00:28:39.649> said<00:28:39.859> last<00:28:40.099> year<00:28:40.249> but<00:28:40.909> again<00:28:41.449> the 00:28:41.799 --> 00:28:41.809 align:start position:0% kind of said last year but again the 00:28:41.809 --> 00:28:43.419 align:start position:0% kind of said last year but again the difference<00:28:42.139> is<00:28:42.319> it's<00:28:42.559> in<00:28:42.679> the<00:28:42.709> code<00:28:42.949> base<00:28:43.129> now 00:28:43.419 --> 00:28:43.429 align:start position:0% difference is it's in the code base now 00:28:43.429 --> 00:28:45.099 align:start position:0% difference is it's in the code base now right<00:28:43.669> or<00:28:43.849> it's<00:28:44.029> in<00:28:44.179> the<00:28:44.359> incent<00:28:44.869> the<00:28:44.959> main 00:28:45.099 --> 00:28:45.109 align:start position:0% right or it's in the incent the main 00:28:45.109 --> 00:28:47.769 align:start position:0% right or it's in the incent the main binary<00:28:45.409> this<00:28:45.829> is<00:28:46.129> new<00:28:46.579> since<00:28:46.849> last<00:28:47.179> time<00:28:47.479> but 00:28:47.769 --> 00:28:47.779 align:start position:0% binary this is new since last time but 00:28:47.779 --> 00:28:49.809 align:start position:0% binary this is new since last time but also<00:28:47.959> part<00:28:48.440> of<00:28:48.469> the<00:28:48.559> merged<00:28:48.819> deduplication 00:28:49.809 --> 00:28:49.819 align:start position:0% also part of the merged deduplication 00:28:49.819 --> 00:28:53.049 align:start position:0% also part of the merged deduplication last<00:28:50.599> when<00:28:51.559> we<00:28:51.709> last<00:28:51.889> heard<00:28:52.039> from<00:28:52.099> this<00:28:52.369> yeah 00:28:53.049 --> 00:28:53.059 align:start position:0% last when we last heard from this yeah 00:28:53.059 --> 00:28:54.879 align:start position:0% last when we last heard from this yeah you<00:28:53.239> had<00:28:53.419> the<00:28:53.539> risk<00:28:53.659> of<00:28:53.899> getting<00:28:54.440> the<00:28:54.709> same 00:28:54.879 --> 00:28:54.889 align:start position:0% you had the risk of getting the same 00:28:54.889 --> 00:28:57.249 align:start position:0% you had the risk of getting the same message<00:28:54.919> twice<00:28:55.579> and<00:28:55.879> BSS<00:28:56.269> this<00:28:56.749> is<00:28:56.899> now<00:28:57.049> much 00:28:57.249 --> 00:28:57.259 align:start position:0% message twice and BSS this is now much 00:28:57.259 --> 00:29:02.799 align:start position:0% message twice and BSS this is now much less<00:28:57.440> likely<00:28:58.809> when<00:28:59.809> messages<00:29:00.199> are<00:29:01.809> exchanged 00:29:02.799 --> 00:29:02.809 align:start position:0% less likely when messages are exchanged 00:29:02.809 --> 00:29:05.680 align:start position:0% less likely when messages are exchanged on<00:29:02.989> the<00:29:03.489> PSS<00:29:04.489> network<00:29:04.789> they<00:29:04.969> have<00:29:05.119> an<00:29:05.239> expiry 00:29:05.680 --> 00:29:05.690 align:start position:0% on the PSS network they have an expiry 00:29:05.690 --> 00:29:09.579 align:start position:0% on the PSS network they have an expiry and<00:29:05.929> the<00:29:06.889> nodes<00:29:07.699> will<00:29:07.999> also<00:29:08.389> have<00:29:08.629> a<00:29:08.659> certain 00:29:09.579 --> 00:29:09.589 align:start position:0% and the nodes will also have a certain 00:29:09.589 --> 00:29:10.629 align:start position:0% and the nodes will also have a certain period<00:29:09.769> of<00:29:09.889> time<00:29:09.979> where<00:29:10.249> they<00:29:10.339> don't<00:29:10.459> allow 00:29:10.629 --> 00:29:10.639 align:start position:0% period of time where they don't allow 00:29:10.639 --> 00:29:12.819 align:start position:0% period of time where they don't allow the<00:29:10.789> same<00:29:11.149> the<00:29:11.599> message<00:29:11.899> an<00:29:12.259> identical 00:29:12.819 --> 00:29:12.829 align:start position:0% the same the message an identical 00:29:12.829 --> 00:29:15.129 align:start position:0% the same the message an identical message<00:29:13.099> to<00:29:13.279> pass<00:29:13.429> or<00:29:14.029> an<00:29:14.119> identical<00:29:14.929> message 00:29:15.129 --> 00:29:15.139 align:start position:0% message to pass or an identical message 00:29:15.139 --> 00:29:17.289 align:start position:0% message to pass or an identical message to<00:29:15.229> go<00:29:15.319> in<00:29:15.440> so<00:29:16.069> that<00:29:16.729> will<00:29:16.909> make<00:29:16.999> it<00:29:17.119> less 00:29:17.289 --> 00:29:17.299 align:start position:0% to go in so that will make it less 00:29:17.299 --> 00:29:18.399 align:start position:0% to go in so that will make it less likely<00:29:17.599> not<00:29:17.809> a<00:29:17.839> hundred-percent<00:29:18.229> guarantee 00:29:18.399 --> 00:29:18.409 align:start position:0% likely not a hundred-percent guarantee 00:29:18.409 --> 00:29:20.139 align:start position:0% likely not a hundred-percent guarantee but<00:29:18.799> actually<00:29:19.099> less<00:29:19.279> likely<00:29:19.669> that<00:29:19.699> you<00:29:19.879> have 00:29:20.139 --> 00:29:20.149 align:start position:0% but actually less likely that you have 00:29:20.149 --> 00:29:21.729 align:start position:0% but actually less likely that you have to<00:29:20.299> handle<00:29:20.629> the<00:29:20.749> duplication<00:29:21.259> messages 00:29:21.729 --> 00:29:21.739 align:start position:0% to handle the duplication messages 00:29:21.739 --> 00:29:24.999 align:start position:0% to handle the duplication messages yourself<00:29:21.940> raw<00:29:22.940> messages<00:29:23.599> which<00:29:23.809> means<00:29:24.079> it 00:29:24.999 --> 00:29:25.009 align:start position:0% yourself raw messages which means it 00:29:25.009 --> 00:29:27.939 align:start position:0% yourself raw messages which means it doesn't<00:29:26.049> you<00:29:27.049> actually<00:29:27.379> have<00:29:27.499> a<00:29:27.529> possibility 00:29:27.939 --> 00:29:27.949 align:start position:0% doesn't you actually have a possibility 00:29:27.949 --> 00:29:29.739 align:start position:0% doesn't you actually have a possibility of<00:29:28.129> handling<00:29:28.399> the<00:29:28.519> encryption<00:29:28.999> outside<00:29:29.599> of 00:29:29.739 --> 00:29:29.749 align:start position:0% of handling the encryption outside of 00:29:29.749 --> 00:29:32.319 align:start position:0% of handling the encryption outside of PSS<00:29:30.109> yourself<00:29:30.709> or<00:29:30.949> just<00:29:31.579> send<00:29:31.789> plain<00:29:31.969> thanks 00:29:32.319 --> 00:29:32.329 align:start position:0% PSS yourself or just send plain thanks 00:29:32.329 --> 00:29:35.229 align:start position:0% PSS yourself or just send plain thanks messages<00:29:32.539> if<00:29:32.929> you<00:29:33.049> will<00:29:33.229> if<00:29:33.440> if<00:29:33.949> the<00:29:34.609> secrecy 00:29:35.229 --> 00:29:35.239 align:start position:0% messages if you will if if the secrecy 00:29:35.239 --> 00:29:39.299 align:start position:0% messages if you will if if the secrecy is<00:29:35.629> not<00:29:36.369> important<00:29:37.369> and<00:29:37.749> last<00:29:38.749> of<00:29:38.899> all<00:29:39.049> a 00:29:39.299 --> 00:29:39.309 align:start position:0% is not important and last of all a 00:29:39.309 --> 00:29:41.680 align:start position:0% is not important and last of all a notifications<00:29:40.309> packet<00:29:40.999> so<00:29:41.269> it's<00:29:41.419> basically 00:29:41.680 --> 00:29:41.690 align:start position:0% notifications packet so it's basically 00:29:41.690 --> 00:29:42.999 align:start position:0% notifications packet so it's basically means<00:29:41.899> the<00:29:41.989> protocol<00:29:42.409> which<00:29:42.559> makes<00:29:42.739> it<00:29:42.889> really 00:29:42.999 --> 00:29:43.009 align:start position:0% means the protocol which makes it really 00:29:43.009 --> 00:29:46.149 align:start position:0% means the protocol which makes it really easy<00:29:43.129> to<00:29:43.749> subscribe<00:29:44.749> and<00:29:45.169> publish 00:29:46.149 --> 00:29:46.159 align:start position:0% easy to subscribe and publish 00:29:46.159 --> 00:29:50.469 align:start position:0% easy to subscribe and publish notifications<00:29:47.059> and<00:29:48.489> it<00:29:49.489> just<00:29:49.969> provides<00:29:50.209> a 00:29:50.469 --> 00:29:50.479 align:start position:0% notifications and it just provides a 00:29:50.479 --> 00:29:52.209 align:start position:0% notifications and it just provides a kind<00:29:50.659> of<00:29:50.749> a<00:29:50.839> channel<00:29:51.199> which<00:29:51.379> you<00:29:51.679> your<00:29:51.979> code 00:29:52.209 --> 00:29:52.219 align:start position:0% kind of a channel which you your code 00:29:52.219 --> 00:29:53.859 align:start position:0% kind of a channel which you your code can<00:29:52.429> pump<00:29:52.699> stuff<00:29:53.059> into<00:29:53.359> and<00:29:53.569> then<00:29:53.659> a<00:29:53.749> very 00:29:53.859 --> 00:29:53.869 align:start position:0% can pump stuff into and then a very 00:29:53.869 --> 00:29:57.089 align:start position:0% can pump stuff into and then a very simple<00:29:54.319> protocol<00:29:54.679> of<00:29:54.799> where<00:29:55.029> notes<00:29:56.029> send 00:29:57.089 --> 00:29:57.099 align:start position:0% simple protocol of where notes send 00:29:57.099 --> 00:29:59.499 align:start position:0% simple protocol of where notes send subscribe<00:29:58.099> message<00:29:58.549> to<00:29:58.879> know<00:29:59.269> that's 00:29:59.499 --> 00:29:59.509 align:start position:0% subscribe message to know that's 00:29:59.509 --> 00:30:02.309 align:start position:0% subscribe message to know that's publishing<00:30:00.229> and<00:30:00.499> then<00:30:00.859> automatically<00:30:01.429> gets 00:30:02.309 --> 00:30:02.319 align:start position:0% publishing and then automatically gets 00:30:02.319 --> 00:30:03.430 align:start position:0% publishing and then automatically gets notifications 00:30:03.430 --> 00:30:03.440 align:start position:0% notifications 00:30:03.440 --> 00:30:05.889 align:start position:0% notifications yep<00:30:03.979> ESS<00:30:04.369> for<00:30:04.549> example<00:30:04.999> in<00:30:05.119> combination<00:30:05.659> with 00:30:05.889 --> 00:30:05.899 align:start position:0% yep ESS for example in combination with 00:30:05.899 --> 00:30:08.680 align:start position:0% yep ESS for example in combination with swarm<00:30:06.739> feeds<00:30:06.979> as<00:30:07.190> we<00:30:07.339> heard<00:30:07.489> from<00:30:07.519> Xavier<00:30:08.239> this 00:30:08.680 --> 00:30:08.690 align:start position:0% swarm feeds as we heard from Xavier this 00:30:08.690 --> 00:30:10.269 align:start position:0% swarm feeds as we heard from Xavier this can<00:30:08.869> be<00:30:08.959> a<00:30:08.989> really<00:30:09.169> powerful<00:30:09.409> feature<00:30:09.799> yeah 00:30:10.269 --> 00:30:10.279 align:start position:0% can be a really powerful feature yeah 00:30:10.279 --> 00:30:11.650 align:start position:0% can be a really powerful feature yeah pool<00:30:10.549> as<00:30:10.700> well<00:30:10.879> as<00:30:11.029> push 00:30:11.650 --> 00:30:11.660 align:start position:0% pool as well as push 00:30:11.660 --> 00:30:15.580 align:start position:0% pool as well as push now<00:30:12.470> there<00:30:12.860> is<00:30:12.950> an<00:30:13.070> API<00:30:13.310> of<00:30:13.490> course<00:30:14.590> most 00:30:15.580 --> 00:30:15.590 align:start position:0% now there is an API of course most 00:30:15.590 --> 00:30:18.910 align:start position:0% now there is an API of course most applications<00:30:16.430> in<00:30:16.580> swarm<00:30:16.850> use<00:30:17.500> are<00:30:18.500> available 00:30:18.910 --> 00:30:18.920 align:start position:0% applications in swarm use are available 00:30:18.920 --> 00:30:22.120 align:start position:0% applications in swarm use are available through<00:30:19.100> IPC<00:30:19.520> WebSockets<00:30:20.180> HTTP<00:30:20.660> and<00:30:20.810> CLI<00:30:21.350> PSS 00:30:22.120 --> 00:30:22.130 align:start position:0% through IPC WebSockets HTTP and CLI PSS 00:30:22.130 --> 00:30:24.880 align:start position:0% through IPC WebSockets HTTP and CLI PSS unfortunately<00:30:22.970> or<00:30:23.330> it's<00:30:24.170> only<00:30:24.350> IPC<00:30:24.830> in 00:30:24.880 --> 00:30:24.890 align:start position:0% unfortunately or it's only IPC in 00:30:24.890 --> 00:30:26.680 align:start position:0% unfortunately or it's only IPC in WebSockets<00:30:25.490> because<00:30:25.790> we<00:30:25.910> need<00:30:26.060> subscriptions 00:30:26.680 --> 00:30:26.690 align:start position:0% WebSockets because we need subscriptions 00:30:26.690 --> 00:30:29.380 align:start position:0% WebSockets because we need subscriptions to<00:30:26.810> get<00:30:26.960> incoming<00:30:27.410> messages<00:30:27.800> there<00:30:28.400> is<00:30:28.580> API<00:30:29.270> is 00:30:29.380 --> 00:30:29.390 align:start position:0% to get incoming messages there is API is 00:30:29.390 --> 00:30:32.050 align:start position:0% to get incoming messages there is API is of<00:30:29.750> course<00:30:30.020> all<00:30:30.230> documented<00:30:31.060> unfortunately 00:30:32.050 --> 00:30:32.060 align:start position:0% of course all documented unfortunately 00:30:32.060 --> 00:30:33.670 align:start position:0% of course all documented unfortunately though<00:30:32.240> it's<00:30:32.450> kind<00:30:32.720> of<00:30:32.840> low-level<00:30:32.960> so<00:30:33.470> if<00:30:33.560> you 00:30:33.670 --> 00:30:33.680 align:start position:0% though it's kind of low-level so if you 00:30:33.680 --> 00:30:35.620 align:start position:0% though it's kind of low-level so if you want<00:30:33.860> to<00:30:33.980> interact<00:30:34.520> with<00:30:34.790> it<00:30:34.970> to<00:30:35.000> kind<00:30:35.360> of 00:30:35.620 --> 00:30:35.630 align:start position:0% want to interact with it to kind of 00:30:35.630 --> 00:30:37.960 align:start position:0% want to interact with it to kind of looks<00:30:35.870> like<00:30:36.080> this<00:30:36.590> at<00:30:37.190> least<00:30:37.280> that's<00:30:37.640> what<00:30:37.700> we 00:30:37.960 --> 00:30:37.970 align:start position:0% looks like this at least that's what we 00:30:37.970 --> 00:30:40.030 align:start position:0% looks like this at least that's what we provide<00:30:38.260> fortunately<00:30:39.260> there<00:30:39.410> is<00:30:39.500> a<00:30:39.530> community 00:30:40.030 --> 00:30:40.040 align:start position:0% provide fortunately there is a community 00:30:40.040 --> 00:30:43.000 align:start position:0% provide fortunately there is a community out<00:30:40.220> there<00:30:40.460> that<00:30:41.390> are<00:30:41.930> also<00:30:42.080> collaborating<00:30:42.560> to 00:30:43.000 --> 00:30:43.010 align:start position:0% out there that are also collaborating to 00:30:43.010 --> 00:30:44.830 align:start position:0% out there that are also collaborating to sperm<00:30:43.250> development<00:30:43.400> among<00:30:44.060> the<00:30:44.270> mainframe 00:30:44.830 --> 00:30:44.840 align:start position:0% sperm development among the mainframe 00:30:44.840 --> 00:30:47.700 align:start position:0% sperm development among the mainframe that<00:30:44.870> have<00:30:45.350> created<00:30:45.770> a<00:30:46.250> JavaScript<00:30:47.060> library 00:30:47.700 --> 00:30:47.710 align:start position:0% that have created a JavaScript library 00:30:47.710 --> 00:30:51.190 align:start position:0% that have created a JavaScript library called<00:30:48.710> Erebus<00:30:49.160> which<00:30:49.820> as<00:30:50.090> you<00:30:50.450> can<00:30:50.480> see<00:30:50.660> makes 00:30:51.190 --> 00:30:51.200 align:start position:0% called Erebus which as you can see makes 00:30:51.200 --> 00:30:52.930 align:start position:0% called Erebus which as you can see makes it<00:30:51.410> a<00:30:51.500> little<00:30:51.680> more<00:30:51.860> human-friendly<00:30:52.340> to 00:30:52.930 --> 00:30:52.940 align:start position:0% it a little more human-friendly to 00:30:52.940 --> 00:30:56.080 align:start position:0% it a little more human-friendly to interact<00:30:53.330> with<00:30:53.450> the<00:30:53.690> SS<00:30:54.020> as<00:30:54.170> such<00:30:54.410> so<00:30:55.190> for<00:30:56.030> the 00:30:56.080 --> 00:30:56.090 align:start position:0% interact with the SS as such so for the 00:30:56.090 --> 00:30:58.840 align:start position:0% interact with the SS as such so for the documentation<00:30:56.950> swarm<00:30:57.950> guide<00:30:58.160> of<00:30:58.580> course 00:30:58.840 --> 00:30:58.850 align:start position:0% documentation swarm guide of course 00:30:58.850 --> 00:31:01.510 align:start position:0% documentation swarm guide of course Erebos<00:30:59.660> also<00:31:00.140> has<00:31:00.320> some<00:31:00.680> documentation<00:31:01.340> page 00:31:01.510 --> 00:31:01.520 align:start position:0% Erebos also has some documentation page 00:31:01.520 --> 00:31:06.400 align:start position:0% Erebos also has some documentation page and<00:31:02.770> at<00:31:03.770> the<00:31:03.920> bottom<00:31:04.040> is<00:31:04.690> my<00:31:05.690> repository<00:31:05.960> where 00:31:06.400 --> 00:31:06.410 align:start position:0% and at the bottom is my repository where 00:31:06.410 --> 00:31:09.010 align:start position:0% and at the bottom is my repository where there<00:31:06.560> was<00:31:06.680> in<00:31:06.890> tutorial<00:31:07.490> except<00:31:07.910> more<00:31:08.030> code 00:31:09.010 --> 00:31:09.020 align:start position:0% there was in tutorial except more code 00:31:09.020 --> 00:31:11.410 align:start position:0% there was in tutorial except more code examples<00:31:09.500> for<00:31:09.650> tutorial<00:31:10.130> for<00:31:10.310> PSS<00:31:10.670> i<00:31:10.910> would 00:31:11.410 --> 00:31:11.420 align:start position:0% examples for tutorial for PSS i would 00:31:11.420 --> 00:31:13.570 align:start position:0% examples for tutorial for PSS i would also<00:31:11.570> like<00:31:11.750> to<00:31:11.900> mention<00:31:12.140> that<00:31:12.410> victor<00:31:12.800> is 00:31:13.570 --> 00:31:13.580 align:start position:0% also like to mention that victor is 00:31:13.580 --> 00:31:17.470 align:start position:0% also like to mention that victor is having<00:31:13.970> a<00:31:14.030> talk<00:31:14.210> later<00:31:14.480> today<00:31:14.750> on<00:31:16.270> the<00:31:17.270> higher 00:31:17.470 --> 00:31:17.480 align:start position:0% having a talk later today on the higher 00:31:17.480 --> 00:31:19.900 align:start position:0% having a talk later today on the higher level<00:31:17.750> vision<00:31:17.990> of<00:31:18.320> PSS<00:31:18.830> and<00:31:19.100> how<00:31:19.520> it<00:31:19.790> can 00:31:19.900 --> 00:31:19.910 align:start position:0% level vision of PSS and how it can 00:31:19.910 --> 00:31:21.430 align:start position:0% level vision of PSS and how it can interact<00:31:20.270> for<00:31:20.480> the<00:31:20.540> feets<00:31:20.750> as<00:31:20.960> i<00:31:21.080> mentioned 00:31:21.430 --> 00:31:21.440 align:start position:0% interact for the feets as i mentioned 00:31:21.440 --> 00:31:25.480 align:start position:0% interact for the feets as i mentioned also<00:31:21.650> access<00:31:22.580> control<00:31:23.000> as<00:31:24.370> Donghae<00:31:25.370> was 00:31:25.480 --> 00:31:25.490 align:start position:0% also access control as Donghae was 00:31:25.490 --> 00:31:27.760 align:start position:0% also access control as Donghae was talking<00:31:25.760> about<00:31:25.820> I<00:31:26.210> can't<00:31:26.780> remember<00:31:26.990> exactly 00:31:27.760 --> 00:31:27.770 align:start position:0% talking about I can't remember exactly 00:31:27.770 --> 00:31:29.710 align:start position:0% talking about I can't remember exactly the<00:31:27.860> where<00:31:28.190> it<00:31:28.490> was<00:31:28.670> or<00:31:28.880> when<00:31:29.030> it<00:31:29.120> was<00:31:29.270> but<00:31:29.570> if 00:31:29.710 --> 00:31:29.720 align:start position:0% the where it was or when it was but if 00:31:29.720 --> 00:31:31.240 align:start position:0% the where it was or when it was but if you<00:31:29.840> follow<00:31:30.050> this<00:31:30.200> link<00:31:30.410> I<00:31:30.650> mean<00:31:30.860> everybody 00:31:31.240 --> 00:31:31.250 align:start position:0% you follow this link I mean everybody 00:31:31.250 --> 00:31:32.680 align:start position:0% you follow this link I mean everybody takes<00:31:31.460> pictures<00:31:31.850> of<00:31:31.970> the<00:31:32.030> screen<00:31:32.330> right<00:31:32.360> then 00:31:32.680 --> 00:31:32.690 align:start position:0% takes pictures of the screen right then 00:31:32.690 --> 00:31:34.240 align:start position:0% takes pictures of the screen right then these<00:31:32.780> things<00:31:33.050> come<00:31:33.290> then<00:31:33.770> you<00:31:33.890> probably<00:31:34.040> can 00:31:34.240 --> 00:31:34.250 align:start position:0% these things come then you probably can 00:31:34.250 --> 00:31:37.210 align:start position:0% these things come then you probably can find<00:31:34.280> it<00:31:34.610> and<00:31:34.790> I<00:31:34.910> think<00:31:35.150> that's<00:31:35.360> it 00:31:37.210 --> 00:31:37.220 align:start position:0% find it and I think that's it 00:31:37.220 --> 00:31:45.109 align:start position:0% find it and I think that's it [Applause] 00:31:45.109 --> 00:31:45.119 align:start position:0% 00:31:45.119 --> 00:31:48.060 align:start position:0% so<00:31:46.119> yeah<00:31:46.269> the<00:31:46.840> talk<00:31:47.019> is<00:31:47.169> at<00:31:47.320> the<00:31:47.440> fluence<00:31:47.799> meet 00:31:48.060 --> 00:31:48.070 align:start position:0% so yeah the talk is at the fluence meet 00:31:48.070 --> 00:31:50.039 align:start position:0% so yeah the talk is at the fluence meet up<00:31:48.249> tonight<00:31:48.489> at<00:31:48.940> six<00:31:49.330> o'clock<00:31:49.450> there's<00:31:49.899> going 00:31:50.039 --> 00:31:50.049 align:start position:0% up tonight at six o'clock there's going 00:31:50.049 --> 00:31:52.649 align:start position:0% up tonight at six o'clock there's going to<00:31:50.109> be<00:31:50.169> four<00:31:50.590> hours<00:31:50.619> talking<00:31:51.039> from<00:31:51.369> line<00:31:52.179> life 00:31:52.649 --> 00:31:52.659 align:start position:0% to be four hours talking from line life 00:31:52.659 --> 00:31:56.340 align:start position:0% to be four hours talking from line life pier<00:31:52.960> new<00:31:53.499> cipher<00:31:53.979> fluent<00:31:54.759> sentence<00:31:55.299> warm<00:31:55.659> and 00:31:56.340 --> 00:31:56.350 align:start position:0% pier new cipher fluent sentence warm and 00:31:56.350 --> 00:31:57.779 align:start position:0% pier new cipher fluent sentence warm and I'm<00:31:56.470> going<00:31:56.619> to<00:31:56.649> talk<00:31:56.830> about<00:31:56.859> my<00:31:57.249> vision<00:31:57.549> of<00:31:57.609> how 00:31:57.779 --> 00:31:57.789 align:start position:0% I'm going to talk about my vision of how 00:31:57.789 --> 00:32:01.700 align:start position:0% I'm going to talk about my vision of how to<00:31:57.820> how<00:31:58.779> to<00:31:59.129> basically<00:32:00.129> reformulate 00:32:01.700 --> 00:32:01.710 align:start position:0% to how to basically reformulate 00:32:01.710 --> 00:32:04.379 align:start position:0% to how to basically reformulate communication<00:32:02.710> protocols<00:32:03.220> yes<00:32:03.580> you<00:32:04.029> heard<00:32:04.179> it 00:32:04.379 --> 00:32:04.389 align:start position:0% communication protocols yes you heard it 00:32:04.389 --> 00:32:08.180 align:start position:0% communication protocols yes you heard it well<00:32:04.600> all<00:32:04.749> of<00:32:04.929> them<00:32:05.759> in<00:32:06.759> terms<00:32:07.029> of<00:32:07.269> in<00:32:07.539> terms<00:32:07.720> of 00:32:08.180 --> 00:32:08.190 align:start position:0% well all of them in terms of in terms of 00:32:08.190 --> 00:32:11.129 align:start position:0% well all of them in terms of in terms of tools<00:32:09.190> that<00:32:09.309> are<00:32:09.789> available<00:32:09.940> for<00:32:10.509> web<00:32:10.659> 3<00:32:10.899> so 00:32:11.129 --> 00:32:11.139 align:start position:0% tools that are available for web 3 so 00:32:11.139 --> 00:32:13.049 align:start position:0% tools that are available for web 3 so basically<00:32:11.889> they<00:32:12.129> have<00:32:12.220> communication<00:32:12.909> that's 00:32:13.049 --> 00:32:13.059 align:start position:0% basically they have communication that's 00:32:13.059 --> 00:32:15.619 align:start position:0% basically they have communication that's decentralized<00:32:13.720> incentivized<00:32:14.379> and<00:32:14.529> secured 00:32:15.619 --> 00:32:15.629 align:start position:0% decentralized incentivized and secured 00:32:15.629 --> 00:32:18.690 align:start position:0% decentralized incentivized and secured thanks<00:32:16.629> to<00:32:16.749> our<00:32:16.779> friends<00:32:17.169> from<00:32:17.200> beefy<00:32:17.710> for<00:32:18.580> the 00:32:18.690 --> 00:32:18.700 align:start position:0% thanks to our friends from beefy for the 00:32:18.700 --> 00:32:20.029 align:start position:0% thanks to our friends from beefy for the motto 00:32:20.029 --> 00:32:20.039 align:start position:0% motto 00:32:20.039 --> 00:32:24.719 align:start position:0% motto now<00:32:21.039> talk<00:32:21.279> about<00:32:21.309> like<00:32:21.700> notes<00:32:21.999> so<00:32:22.840> we<00:32:23.729> realized 00:32:24.719 --> 00:32:24.729 align:start position:0% now talk about like notes so we realized 00:32:24.729 --> 00:32:26.909 align:start position:0% now talk about like notes so we realized early<00:32:24.940> on<00:32:25.149> that<00:32:25.269> we<00:32:26.019> need<00:32:26.349> to<00:32:26.470> distinguish 00:32:26.909 --> 00:32:26.919 align:start position:0% early on that we need to distinguish 00:32:26.919 --> 00:32:29.190 align:start position:0% early on that we need to distinguish between<00:32:27.039> two<00:32:27.489> types<00:32:27.759> of<00:32:28.119> notes<00:32:28.330> once<00:32:28.960> that 00:32:29.190 --> 00:32:29.200 align:start position:0% between two types of notes once that 00:32:29.200 --> 00:32:30.930 align:start position:0% between two types of notes once that that<00:32:29.619> are<00:32:29.799> constantly<00:32:30.220> online<00:32:30.399> and<00:32:30.789> therefore 00:32:30.930 --> 00:32:30.940 align:start position:0% that are constantly online and therefore 00:32:30.940 --> 00:32:33.269 align:start position:0% that are constantly online and therefore a<00:32:31.149> reliable<00:32:31.720> force<00:32:31.989> for<00:32:32.349> storing<00:32:32.710> chunks<00:32:33.099> and 00:32:33.269 --> 00:32:33.279 align:start position:0% a reliable force for storing chunks and 00:32:33.279 --> 00:32:35.849 align:start position:0% a reliable force for storing chunks and the<00:32:33.909> notes<00:32:34.059> that<00:32:34.210> have<00:32:34.690> high<00:32:34.869> churn<00:32:35.200> basically 00:32:35.849 --> 00:32:35.859 align:start position:0% the notes that have high churn basically 00:32:35.859 --> 00:32:37.409 align:start position:0% the notes that have high churn basically that<00:32:36.009> you<00:32:36.190> just<00:32:36.340> open<00:32:36.669> your<00:32:36.700> laptop<00:32:37.119> and<00:32:37.239> close 00:32:37.409 --> 00:32:37.419 align:start position:0% that you just open your laptop and close 00:32:37.419 --> 00:32:39.930 align:start position:0% that you just open your laptop and close it<00:32:37.629> and<00:32:37.899> we're<00:32:38.679> all<00:32:38.710> or<00:32:39.070> you<00:32:39.190> have<00:32:39.309> your<00:32:39.700> mobile 00:32:39.930 --> 00:32:39.940 align:start position:0% it and we're all or you have your mobile 00:32:39.940 --> 00:32:41.999 align:start position:0% it and we're all or you have your mobile device<00:32:40.389> and<00:32:40.869> in<00:32:40.989> general<00:32:41.320> that's<00:32:41.470> we<00:32:41.799> call 00:32:41.999 --> 00:32:42.009 align:start position:0% device and in general that's we call 00:32:42.009 --> 00:32:45.690 align:start position:0% device and in general that's we call this<00:32:42.580> this<00:32:42.929> is<00:32:43.929> distinction<00:32:44.499> light<00:32:45.249> load<00:32:45.519> as 00:32:45.690 --> 00:32:45.700 align:start position:0% this this is distinction light load as 00:32:45.700 --> 00:32:48.299 align:start position:0% this this is distinction light load as opposed<00:32:45.999> to<00:32:46.149> full<00:32:46.509> load<00:32:46.720> or<00:32:47.320> light<00:32:47.859> mode<00:32:48.129> of 00:32:48.299 --> 00:32:48.309 align:start position:0% opposed to full load or light mode of 00:32:48.309 --> 00:32:50.339 align:start position:0% opposed to full load or light mode of operation<00:32:48.909> maybe<00:32:49.210> you<00:32:49.389> can<00:32:49.539> call<00:32:49.690> it<00:32:49.840> it's 00:32:50.339 --> 00:32:50.349 align:start position:0% operation maybe you can call it it's 00:32:50.349 --> 00:32:51.960 align:start position:0% operation maybe you can call it it's basically<00:32:50.769> about<00:32:51.009> mobile<00:32:51.369> support<00:32:51.789> let's 00:32:51.960 --> 00:32:51.970 align:start position:0% basically about mobile support let's 00:32:51.970 --> 00:32:54.810 align:start position:0% basically about mobile support let's let's<00:32:52.299> let's<00:32:52.599> simplify<00:32:53.320> the<00:32:53.499> things<00:32:53.619> so<00:32:54.309> it's 00:32:54.810 --> 00:32:54.820 align:start position:0% let's let's simplify the things so it's 00:32:54.820 --> 00:32:56.759 align:start position:0% let's let's simplify the things so it's concerned<00:32:55.179> with<00:32:55.389> not<00:32:55.869> only<00:32:55.929> the<00:32:56.320> high<00:32:56.470> churn 00:32:56.759 --> 00:32:56.769 align:start position:0% concerned with not only the high churn 00:32:56.769 --> 00:32:59.519 align:start position:0% concerned with not only the high churn but<00:32:57.009> also<00:32:57.269> the<00:32:58.269> difference<00:32:58.869> in<00:32:59.049> the<00:32:59.200> in<00:32:59.349> the 00:32:59.519 --> 00:32:59.529 align:start position:0% but also the difference in the in the 00:32:59.529 --> 00:33:01.889 align:start position:0% but also the difference in the in the resources<00:33:00.340> of<00:33:00.489> the<00:33:00.759> environmental<00:33:01.359> resources 00:33:01.889 --> 00:33:01.899 align:start position:0% resources of the environmental resources 00:33:01.899 --> 00:33:04.440 align:start position:0% resources of the environmental resources that<00:33:02.379> are<00:33:02.529> available<00:33:02.619> for<00:33:03.159> swamp<00:33:03.460> solo<00:33:04.239> band 00:33:04.440 --> 00:33:04.450 align:start position:0% that are available for swamp solo band 00:33:04.450 --> 00:33:06.479 align:start position:0% that are available for swamp solo band it's<00:33:04.690> usually<00:33:04.809> probably<00:33:05.499> ole<00:33:05.799> ole<00:33:06.070> ole<00:33:06.190> memory 00:33:06.479 --> 00:33:06.489 align:start position:0% it's usually probably ole ole ole memory 00:33:06.489 --> 00:33:09.830 align:start position:0% it's usually probably ole ole ole memory as<00:33:06.669> well<00:33:06.849> and<00:33:07.179> short<00:33:07.570> on<00:33:07.690> disk<00:33:07.899> space<00:33:08.229> and<00:33:08.700> and 00:33:09.830 --> 00:33:09.840 align:start position:0% as well and short on disk space and and 00:33:09.840 --> 00:33:12.719 align:start position:0% as well and short on disk space and and there's<00:33:10.840> various<00:33:11.440> issues<00:33:11.619> that<00:33:11.830> we<00:33:12.159> came 00:33:12.719 --> 00:33:12.729 align:start position:0% there's various issues that we came 00:33:12.729 --> 00:33:14.729 align:start position:0% there's various issues that we came across<00:33:12.789> by<00:33:13.269> when<00:33:13.899> when<00:33:14.109> trying<00:33:14.320> to<00:33:14.440> support 00:33:14.729 --> 00:33:14.739 align:start position:0% across by when when trying to support 00:33:14.739 --> 00:33:17.279 align:start position:0% across by when when trying to support the<00:33:15.580> mobilize<00:33:15.909> the<00:33:16.539> some<00:33:16.720> of<00:33:16.749> them<00:33:16.989> are<00:33:17.109> kind 00:33:17.279 --> 00:33:17.289 align:start position:0% the mobilize the some of them are kind 00:33:17.289 --> 00:33:20.039 align:start position:0% the mobilize the some of them are kind of<00:33:17.349> boring<00:33:18.059> platform<00:33:19.059> specific<00:33:19.659> issues<00:33:19.899> I'm 00:33:20.039 --> 00:33:20.049 align:start position:0% of boring platform specific issues I'm 00:33:20.049 --> 00:33:21.570 align:start position:0% of boring platform specific issues I'm not<00:33:20.200> gonna<00:33:20.349> talk<00:33:20.529> about<00:33:20.799> the<00:33:20.919> permission 00:33:21.570 --> 00:33:21.580 align:start position:0% not gonna talk about the permission 00:33:21.580 --> 00:33:26.549 align:start position:0% not gonna talk about the permission issues<00:33:22.529> and<00:33:23.759> so<00:33:24.759> so<00:33:25.149> in<00:33:25.239> general<00:33:25.419> what<00:33:25.929> was<00:33:26.349> the 00:33:26.549 --> 00:33:26.559 align:start position:0% issues and so so in general what was the 00:33:26.559 --> 00:33:29.489 align:start position:0% issues and so so in general what was the was<00:33:27.009> the<00:33:27.159> chance<00:33:27.369> of<00:33:27.549> a<00:33:27.929> restricted<00:33:28.929> resource 00:33:29.489 --> 00:33:29.499 align:start position:0% was the chance of a restricted resource 00:33:29.499 --> 00:33:32.700 align:start position:0% was the chance of a restricted resource client<00:33:30.429> to<00:33:30.580> to<00:33:30.909> to<00:33:31.450> connect<00:33:31.749> to<00:33:31.840> swamp<00:33:32.139> where 00:33:32.700 --> 00:33:32.710 align:start position:0% client to to to connect to swamp where 00:33:32.710 --> 00:33:35.549 align:start position:0% client to to to connect to swamp where does<00:33:32.859> this<00:33:33.239> post<00:33:34.239> potential<00:33:34.840> gay<00:33:35.080> twist<00:33:35.379> like 00:33:35.549 --> 00:33:35.559 align:start position:0% does this post potential gay twist like 00:33:35.559 --> 00:33:37.499 align:start position:0% does this post potential gay twist like it<00:33:36.190> which<00:33:36.429> that<00:33:36.580> might<00:33:36.879> be<00:33:37.059> accessible 00:33:37.499 --> 00:33:37.509 align:start position:0% it which that might be accessible 00:33:37.509 --> 00:33:39.389 align:start position:0% it which that might be accessible through<00:33:38.049> adders<00:33:38.529> like<00:33:38.739> for<00:33:38.889> example<00:33:38.979> the<00:33:39.279> one 00:33:39.389 --> 00:33:39.399 align:start position:0% through adders like for example the one 00:33:39.399 --> 00:33:42.629 align:start position:0% through adders like for example the one that<00:33:39.429> the<00:33:40.090> this<00:33:40.749> one<00:33:40.960> team<00:33:41.769> were<00:33:42.009> the<00:33:42.249> Syrian 00:33:42.629 --> 00:33:42.639 align:start position:0% that the this one team were the Syrian 00:33:42.639 --> 00:33:44.399 align:start position:0% that the this one team were the Syrian foundation<00:33:43.179> is<00:33:43.269> running<00:33:43.570> the<00:33:43.720> Swan<00:33:43.989> cluster 00:33:44.399 --> 00:33:44.409 align:start position:0% foundation is running the Swan cluster 00:33:44.409 --> 00:33:46.589 align:start position:0% foundation is running the Swan cluster which<00:33:44.859> we<00:33:45.009> run<00:33:45.129> a<00:33:45.159> public<00:33:45.489> gateway<00:33:45.940> this<00:33:46.419> is 00:33:46.589 --> 00:33:46.599 align:start position:0% which we run a public gateway this is 00:33:46.599 --> 00:33:47.020 align:start position:0% which we run a public gateway this is not 00:33:47.020 --> 00:33:47.030 align:start position:0% not 00:33:47.030 --> 00:33:49.120 align:start position:0% not intended<00:33:47.870> to<00:33:47.990> be<00:33:48.110> long-term<00:33:48.500> this<00:33:48.710> is<00:33:48.860> kind<00:33:49.070> of 00:33:49.120 --> 00:33:49.130 align:start position:0% intended to be long-term this is kind of 00:33:49.130 --> 00:33:51.730 align:start position:0% intended to be long-term this is kind of a<00:33:49.250> just<00:33:49.850> fun<00:33:50.360> for<00:33:50.840> for<00:33:51.050> easy<00:33:51.200> access<00:33:51.350> now 00:33:51.730 --> 00:33:51.740 align:start position:0% a just fun for for easy access now 00:33:51.740 --> 00:33:53.680 align:start position:0% a just fun for for easy access now through<00:33:52.070> the<00:33:52.190> development<00:33:52.550> that<00:33:52.880> obviously 00:33:53.680 --> 00:33:53.690 align:start position:0% through the development that obviously 00:33:53.690 --> 00:33:55.840 align:start position:0% through the development that obviously when<00:33:54.350> the<00:33:54.500> incentive<00:33:54.890> is<00:33:54.980> Asian<00:33:55.250> is<00:33:55.400> coming<00:33:55.730> on 00:33:55.840 --> 00:33:55.850 align:start position:0% when the incentive is Asian is coming on 00:33:55.850 --> 00:33:58.360 align:start position:0% when the incentive is Asian is coming on the<00:33:55.970> main<00:33:56.120> that<00:33:56.300> is<00:33:56.810> gonna<00:33:56.960> cost<00:33:57.170> money<00:33:57.440> so<00:33:57.530> we 00:33:58.360 --> 00:33:58.370 align:start position:0% the main that is gonna cost money so we 00:33:58.370 --> 00:34:00.970 align:start position:0% the main that is gonna cost money so we might<00:33:59.240> only<00:33:59.630> do<00:33:59.840> that<00:33:59.960> for<00:34:00.170> marketing 00:34:00.970 --> 00:34:00.980 align:start position:0% might only do that for marketing 00:34:00.980 --> 00:34:03.610 align:start position:0% might only do that for marketing purposes<00:34:01.040> for<00:34:01.940> short<00:34:02.180> term<00:34:02.390> but<00:34:02.540> and<00:34:02.810> as<00:34:03.260> you 00:34:03.610 --> 00:34:03.620 align:start position:0% purposes for short term but and as you 00:34:03.620 --> 00:34:07.090 align:start position:0% purposes for short term but and as you heard<00:34:03.710> as<00:34:03.980> well<00:34:04.190> you<00:34:05.650> remote<00:34:06.650> gateways<00:34:07.070> are 00:34:07.090 --> 00:34:07.100 align:start position:0% heard as well you remote gateways are 00:34:07.100 --> 00:34:11.680 align:start position:0% heard as well you remote gateways are not<00:34:07.400> appropriate<00:34:07.940> for<00:34:07.970> for<00:34:09.040> hosting<00:34:10.480> to<00:34:11.480> to 00:34:11.680 --> 00:34:11.690 align:start position:0% not appropriate for for hosting to to 00:34:11.690 --> 00:34:13.950 align:start position:0% not appropriate for for hosting to to retrieve<00:34:12.020> the<00:34:12.230> encrypted<00:34:12.919> content<00:34:13.220> from 00:34:13.950 --> 00:34:13.960 align:start position:0% retrieve the encrypted content from 00:34:13.960 --> 00:34:16.450 align:start position:0% retrieve the encrypted content from there's<00:34:14.960> also<00:34:15.080> privately<00:34:15.590> free<00:34:15.860> solution<00:34:16.310> so 00:34:16.450 --> 00:34:16.460 align:start position:0% there's also privately free solution so 00:34:16.460 --> 00:34:18.669 align:start position:0% there's also privately free solution so you<00:34:16.490> run<00:34:16.820> your<00:34:16.879> own<00:34:17.060> remote<00:34:17.929> node<00:34:18.139> for<00:34:18.649> example 00:34:18.669 --> 00:34:18.679 align:start position:0% you run your own remote node for example 00:34:18.679 --> 00:34:23.250 align:start position:0% you run your own remote node for example then<00:34:19.429> that<00:34:19.610> notice<00:34:20.090> is<00:34:21.520> supporting<00:34:22.520> that<00:34:22.550> and 00:34:23.250 --> 00:34:23.260 align:start position:0% then that notice is supporting that and 00:34:23.260 --> 00:34:25.840 align:start position:0% then that notice is supporting that and what<00:34:24.260> we<00:34:24.409> are<00:34:24.800> going<00:34:24.830> to<00:34:25.010> talk<00:34:25.159> about<00:34:25.310> here<00:34:25.669> is 00:34:25.840 --> 00:34:25.850 align:start position:0% what we are going to talk about here is 00:34:25.850 --> 00:34:27.730 align:start position:0% what we are going to talk about here is just<00:34:26.149> light<00:34:26.629> mode<00:34:26.840> of<00:34:26.990> operation<00:34:27.500> which<00:34:27.620> is 00:34:27.730 --> 00:34:27.740 align:start position:0% just light mode of operation which is 00:34:27.740 --> 00:34:30.369 align:start position:0% just light mode of operation which is like<00:34:27.919> how<00:34:28.070> it<00:34:28.250> natively<00:34:28.790> support<00:34:29.600> this<00:34:30.139> this 00:34:30.369 --> 00:34:30.379 align:start position:0% like how it natively support this this 00:34:30.379 --> 00:34:32.169 align:start position:0% like how it natively support this this type<00:34:30.560> of<00:34:30.590> operation<00:34:31.070> where<00:34:31.429> you<00:34:31.879> have<00:34:32.000> low 00:34:32.169 --> 00:34:32.179 align:start position:0% type of operation where you have low 00:34:32.179 --> 00:34:34.930 align:start position:0% type of operation where you have low resource<00:34:32.570> environments<00:34:33.260> so<00:34:34.010> basically<00:34:34.730> we 00:34:34.930 --> 00:34:34.940 align:start position:0% resource environments so basically we 00:34:34.940 --> 00:34:36.909 align:start position:0% resource environments so basically we distinguish<00:34:35.600> these<00:34:35.750> two<00:34:35.810> doing<00:34:36.350> 200<00:34:36.590> types 00:34:36.909 --> 00:34:36.919 align:start position:0% distinguish these two doing 200 types 00:34:36.919 --> 00:34:39.340 align:start position:0% distinguish these two doing 200 types and<00:34:37.340> in<00:34:37.550> the<00:34:37.669> in<00:34:37.909> the<00:34:38.060> zero<00:34:38.600> phase<00:34:38.870> what<00:34:39.200> we 00:34:39.340 --> 00:34:39.350 align:start position:0% and in the in the zero phase what we 00:34:39.350 --> 00:34:41.110 align:start position:0% and in the in the zero phase what we already<00:34:39.470> accomplished<00:34:40.129> kind<00:34:40.669> of<00:34:40.820> almost 00:34:41.110 --> 00:34:41.120 align:start position:0% already accomplished kind of almost 00:34:41.120 --> 00:34:44.110 align:start position:0% already accomplished kind of almost almost<00:34:41.570> deaf<00:34:42.139> ready<00:34:42.350> is<00:34:42.889> that<00:34:42.950> light<00:34:43.850> nodes 00:34:44.110 --> 00:34:44.120 align:start position:0% almost deaf ready is that light nodes 00:34:44.120 --> 00:34:46.330 align:start position:0% almost deaf ready is that light nodes when<00:34:44.510> like<00:34:45.409> odds<00:34:45.620> are<00:34:45.800> are<00:34:45.980> treated 00:34:46.330 --> 00:34:46.340 align:start position:0% when like odds are are treated 00:34:46.340 --> 00:34:48.520 align:start position:0% when like odds are are treated differently<00:34:46.720> they<00:34:47.720> are<00:34:47.810> not<00:34:47.929> saved<00:34:48.169> in<00:34:48.409> the 00:34:48.520 --> 00:34:48.530 align:start position:0% differently they are not saved in the 00:34:48.530 --> 00:34:50.950 align:start position:0% differently they are not saved in the address<00:34:48.770> book<00:34:48.950> of<00:34:49.159> your<00:34:49.850> peers<00:34:50.120> they<00:34:50.750> are<00:34:50.810> not 00:34:50.950 --> 00:34:50.960 align:start position:0% address book of your peers they are not 00:34:50.960 --> 00:34:53.050 align:start position:0% address book of your peers they are not dialed<00:34:51.470> so<00:34:51.620> actively<00:34:52.040> looked<00:34:52.220> for<00:34:52.460> they<00:34:52.879> just 00:34:53.050 --> 00:34:53.060 align:start position:0% dialed so actively looked for they just 00:34:53.060 --> 00:34:55.360 align:start position:0% dialed so actively looked for they just accepted<00:34:53.570> as<00:34:53.780> a<00:34:53.840> connection<00:34:54.379> they<00:34:55.129> don't 00:34:55.360 --> 00:34:55.370 align:start position:0% accepted as a connection they don't 00:34:55.370 --> 00:34:56.980 align:start position:0% accepted as a connection they don't state<00:34:55.820> since<00:34:56.060> they<00:34:56.149> don't<00:34:56.270> store<00:34:56.720> Chiang 00:34:56.980 --> 00:34:56.990 align:start position:0% state since they don't store Chiang 00:34:56.990 --> 00:34:58.960 align:start position:0% state since they don't store Chiang state<00:34:57.260> they<00:34:57.440> also<00:34:57.590> not<00:34:57.890> doing<00:34:58.430> syncing 00:34:58.960 --> 00:34:58.970 align:start position:0% state they also not doing syncing 00:34:58.970 --> 00:35:01.000 align:start position:0% state they also not doing syncing process<00:34:59.150> so<00:34:59.840> they're<00:35:00.290> not<00:35:00.410> sinking 00:35:01.000 --> 00:35:01.010 align:start position:0% process so they're not sinking 00:35:01.010 --> 00:35:03.640 align:start position:0% process so they're not sinking but<00:35:01.370> taking<00:35:01.940> part<00:35:02.120> in<00:35:02.270> the<00:35:02.420> in<00:35:02.960> the<00:35:03.140> transport 00:35:03.640 --> 00:35:03.650 align:start position:0% but taking part in the in the transport 00:35:03.650 --> 00:35:07.000 align:start position:0% but taking part in the in the transport of<00:35:03.880> chunks<00:35:04.880> to<00:35:05.000> their<00:35:05.180> to<00:35:05.780> their<00:35:06.010> local 00:35:07.000 --> 00:35:07.010 align:start position:0% of chunks to their to their local 00:35:07.010 --> 00:35:09.850 align:start position:0% of chunks to their to their local neighborhood<00:35:07.550> where<00:35:07.730> they<00:35:07.880> belong<00:35:08.690> in<00:35:09.560> the 00:35:09.850 --> 00:35:09.860 align:start position:0% neighborhood where they belong in the 00:35:09.860 --> 00:35:12.640 align:start position:0% neighborhood where they belong in the distributed<00:35:10.280> storage<00:35:10.700> of<00:35:11.000> so<00:35:11.570> they're<00:35:12.500> not 00:35:12.640 --> 00:35:12.650 align:start position:0% distributed storage of so they're not 00:35:12.650 --> 00:35:14.320 align:start position:0% distributed storage of so they're not serving<00:35:12.860> retrieve<00:35:13.430> requests<00:35:13.820> since<00:35:14.150> they 00:35:14.320 --> 00:35:14.330 align:start position:0% serving retrieve requests since they 00:35:14.330 --> 00:35:17.620 align:start position:0% serving retrieve requests since they cannot<00:35:14.540> store<00:35:14.900> and<00:35:15.170> and<00:35:16.160> also<00:35:16.400> be<00:35:16.790> -<00:35:17.240> in<00:35:17.390> order 00:35:17.620 --> 00:35:17.630 align:start position:0% cannot store and and also be - in order 00:35:17.630 --> 00:35:19.660 align:start position:0% cannot store and and also be - in order to<00:35:17.810> respect<00:35:18.380> the<00:35:18.500> redundancy<00:35:19.100> properties<00:35:19.550> of 00:35:19.660 --> 00:35:19.670 align:start position:0% to respect the redundancy properties of 00:35:19.670 --> 00:35:21.460 align:start position:0% to respect the redundancy properties of swamp<00:35:19.940> they<00:35:20.090> also<00:35:20.390> not<00:35:20.540> counted<00:35:20.930> in<00:35:20.990> the<00:35:21.140> local 00:35:21.460 --> 00:35:21.470 align:start position:0% swamp they also not counted in the local 00:35:21.470 --> 00:35:24.130 align:start position:0% swamp they also not counted in the local neighborhood<00:35:21.640> so<00:35:22.640> once<00:35:22.940> we<00:35:23.090> have<00:35:23.210> that<00:35:23.240> we<00:35:23.630> we 00:35:24.130 --> 00:35:24.140 align:start position:0% neighborhood so once we have that we we 00:35:24.140 --> 00:35:25.830 align:start position:0% neighborhood so once we have that we we are<00:35:24.230> we<00:35:24.350> gonna<00:35:24.500> be<00:35:24.680> a<00:35:24.710> lot<00:35:24.980> more<00:35:25.190> tolerable 00:35:25.830 --> 00:35:25.840 align:start position:0% are we gonna be a lot more tolerable 00:35:25.840 --> 00:35:31.090 align:start position:0% are we gonna be a lot more tolerable towards<00:35:26.860> high<00:35:27.860> churn<00:35:28.160> and<00:35:29.770> especially<00:35:30.770> if<00:35:31.010> we 00:35:31.090 --> 00:35:31.100 align:start position:0% towards high churn and especially if we 00:35:31.100 --> 00:35:34.150 align:start position:0% towards high churn and especially if we set<00:35:31.310> the<00:35:32.000> the<00:35:32.030> light<00:35:32.450> node<00:35:32.690> as<00:35:32.960> as<00:35:33.320> the<00:35:33.770> default 00:35:34.150 --> 00:35:34.160 align:start position:0% set the the light node as as the default 00:35:34.160 --> 00:35:36.340 align:start position:0% set the the light node as as the default mode<00:35:34.310> of<00:35:34.490> operation<00:35:35.030> and<00:35:35.150> people<00:35:35.870> will<00:35:35.990> run 00:35:36.340 --> 00:35:36.350 align:start position:0% mode of operation and people will run 00:35:36.350 --> 00:35:38.230 align:start position:0% mode of operation and people will run like<00:35:36.410> permanent<00:35:37.130> nodes<00:35:37.340> we<00:35:37.460> explicitly<00:35:37.880> have 00:35:38.230 --> 00:35:38.240 align:start position:0% like permanent nodes we explicitly have 00:35:38.240 --> 00:35:40.810 align:start position:0% like permanent nodes we explicitly have to<00:35:38.420> set<00:35:38.630> it<00:35:38.660> to<00:35:39.080> full<00:35:39.260> nodes<00:35:39.470> so<00:35:40.400> this<00:35:40.580> this 00:35:40.810 --> 00:35:40.820 align:start position:0% to set it to full nodes so this this 00:35:40.820 --> 00:35:42.910 align:start position:0% to set it to full nodes so this this will<00:35:41.030> contribute<00:35:41.630> to<00:35:41.870> the<00:35:41.960> resilience<00:35:42.440> of<00:35:42.590> of 00:35:42.910 --> 00:35:42.920 align:start position:0% will contribute to the resilience of of 00:35:42.920 --> 00:35:47.200 align:start position:0% will contribute to the resilience of of our<00:35:43.070> network<00:35:43.460> now<00:35:44.860> I<00:35:45.880> talked<00:35:46.880> about<00:35:46.910> the 00:35:47.200 --> 00:35:47.210 align:start position:0% our network now I talked about the 00:35:47.210 --> 00:35:50.670 align:start position:0% our network now I talked about the roadmap<00:35:47.770> so<00:35:48.770> what's<00:35:49.040> coming<00:35:49.190> up<00:35:49.460> next<00:35:49.640> we 00:35:50.670 --> 00:35:50.680 align:start position:0% roadmap so what's coming up next we 00:35:50.680 --> 00:35:53.290 align:start position:0% roadmap so what's coming up next we started<00:35:51.680> rewriting<00:35:52.010> the<00:35:52.370> the<00:35:52.580> swap<00:35:52.820> protocol 00:35:53.290 --> 00:35:53.300 align:start position:0% started rewriting the the swap protocol 00:35:53.300 --> 00:35:55.360 align:start position:0% started rewriting the the swap protocol the<00:35:53.480> swarm<00:35:53.960> accounting<00:35:54.380> protocol<00:35:54.830> which<00:35:55.340> is 00:35:55.360 --> 00:35:55.370 align:start position:0% the swarm accounting protocol which is 00:35:55.370 --> 00:35:57.339 align:start position:0% the swarm accounting protocol which is basically<00:35:55.820> the<00:35:56.000> peer-to-peer 00:35:57.339 --> 00:35:57.349 align:start position:0% basically the peer-to-peer 00:35:57.349 --> 00:35:59.890 align:start position:0% basically the peer-to-peer for<00:35:57.499> tenth<00:35:57.680> accounting<00:35:58.220> that's<00:35:58.749> serving<00:35:59.749> as 00:35:59.890 --> 00:35:59.900 align:start position:0% for tenth accounting that's serving as 00:35:59.900 --> 00:36:03.509 align:start position:0% for tenth accounting that's serving as bandits<00:36:00.349> incentivization<00:36:01.309> and<00:36:01.609> serving<00:36:02.569> to 00:36:03.509 --> 00:36:03.519 align:start position:0% bandits incentivization and serving to 00:36:03.519 --> 00:36:05.549 align:start position:0% bandits incentivization and serving to regulate<00:36:04.519> and<00:36:04.759> and<00:36:04.940> basically<00:36:05.089> optimize 00:36:05.549 --> 00:36:05.559 align:start position:0% regulate and and basically optimize 00:36:05.559 --> 00:36:10.710 align:start position:0% regulate and and basically optimize bandits<00:36:06.559> resource<00:36:07.339> allocation<00:36:07.970> and<00:36:08.890> we 00:36:10.710 --> 00:36:10.720 align:start position:0% bandits resource allocation and we 00:36:10.720 --> 00:36:14.259 align:start position:0% bandits resource allocation and we reported<00:36:11.720> the<00:36:11.869> odd<00:36:12.019> code<00:36:12.289> and<00:36:12.470> and<00:36:13.269> actually 00:36:14.259 --> 00:36:14.269 align:start position:0% reported the odd code and and actually 00:36:14.269 --> 00:36:16.150 align:start position:0% reported the odd code and and actually we<00:36:14.509> really<00:36:14.930> were<00:36:15.019> quite<00:36:15.170> quite<00:36:15.619> a<00:36:15.650> bit<00:36:15.890> of<00:36:16.039> it 00:36:16.150 --> 00:36:16.160 align:start position:0% we really were quite quite a bit of it 00:36:16.160 --> 00:36:18.279 align:start position:0% we really were quite quite a bit of it and<00:36:16.339> simplified<00:36:16.849> the<00:36:16.999> code<00:36:17.210> so<00:36:17.420> that's<00:36:18.079> that's 00:36:18.279 --> 00:36:18.289 align:start position:0% and simplified the code so that's that's 00:36:18.289 --> 00:36:21.249 align:start position:0% and simplified the code so that's that's what's<00:36:18.529> gonna<00:36:18.680> come<00:36:18.920> up<00:36:19.160> next<00:36:19.549> in<00:36:19.700> in<00:36:20.420> a<00:36:21.079> few 00:36:21.249 --> 00:36:21.259 align:start position:0% what's gonna come up next in in a few 00:36:21.259 --> 00:36:24.370 align:start position:0% what's gonna come up next in in a few releases<00:36:21.529> time<00:36:21.950> we<00:36:22.880> have<00:36:23.059> been<00:36:23.239> planning<00:36:24.140> on 00:36:24.370 --> 00:36:24.380 align:start position:0% releases time we have been planning on 00:36:24.380 --> 00:36:27.099 align:start position:0% releases time we have been planning on introducing<00:36:25.420> spam<00:36:26.420> protection 00:36:27.099 --> 00:36:27.109 align:start position:0% introducing spam protection 00:36:27.109 --> 00:36:29.229 align:start position:0% introducing spam protection so<00:36:27.410> basically<00:36:27.710> protection<00:36:28.249> against<00:36:28.609> people 00:36:29.229 --> 00:36:29.239 align:start position:0% so basically protection against people 00:36:29.239 --> 00:36:31.660 align:start position:0% so basically protection against people flooding<00:36:29.660> justice<00:36:30.650> for<00:36:30.829> network<00:36:31.190> with<00:36:31.339> chunks 00:36:31.660 --> 00:36:31.670 align:start position:0% flooding justice for network with chunks 00:36:31.670 --> 00:36:35.259 align:start position:0% flooding justice for network with chunks by<00:36:32.289> having<00:36:33.289> to<00:36:33.470> attach<00:36:33.739> like<00:36:34.579> making<00:36:35.150> it 00:36:35.259 --> 00:36:35.269 align:start position:0% by having to attach like making it 00:36:35.269 --> 00:36:37.120 align:start position:0% by having to attach like making it making<00:36:35.539> sure<00:36:35.720> that<00:36:36.019> people<00:36:36.170> have<00:36:36.440> to<00:36:36.619> attach<00:36:36.859> a 00:36:37.120 --> 00:36:37.130 align:start position:0% making sure that people have to attach a 00:36:37.130 --> 00:36:40.059 align:start position:0% making sure that people have to attach a proof<00:36:37.579> of<00:36:37.729> burn<00:36:37.970> so<00:36:38.420> some<00:36:38.599> sort<00:36:38.839> of<00:36:39.069> basically 00:36:40.059 --> 00:36:40.069 align:start position:0% proof of burn so some sort of basically 00:36:40.069 --> 00:36:43.269 align:start position:0% proof of burn so some sort of basically proof<00:36:40.339> of<00:36:40.489> work<00:36:40.989> to<00:36:41.989> the<00:36:42.049> to<00:36:42.319> the<00:36:42.470> to<00:36:42.859> the<00:36:42.979> to 00:36:43.269 --> 00:36:43.279 align:start position:0% proof of work to the to the to the to 00:36:43.279 --> 00:36:46.359 align:start position:0% proof of work to the to the to the to the<00:36:43.369> chunks<00:36:43.729> and<00:36:44.059> and<00:36:44.900> also<00:36:45.289> the<00:36:45.859> first<00:36:46.099> phase 00:36:46.359 --> 00:36:46.369 align:start position:0% the chunks and and also the first phase 00:36:46.369 --> 00:36:47.650 align:start position:0% the chunks and and also the first phase of<00:36:46.489> the<00:36:46.609> ratio<00:36:46.849> coding<00:36:47.210> is<00:36:47.299> going<00:36:47.509> to<00:36:47.569> be 00:36:47.650 --> 00:36:47.660 align:start position:0% of the ratio coding is going to be 00:36:47.660 --> 00:36:51.160 align:start position:0% of the ratio coding is going to be implemented<00:36:48.200> very<00:36:48.410> soon<00:36:49.269> which<00:36:50.269> takes<00:36:50.900> care 00:36:51.160 --> 00:36:51.170 align:start position:0% implemented very soon which takes care 00:36:51.170 --> 00:36:55.650 align:start position:0% implemented very soon which takes care of<00:36:51.349> basically<00:36:52.130> it's<00:36:52.339> not<00:36:52.690> the<00:36:53.690> racial<00:36:54.229> coding 00:36:55.650 --> 00:36:55.660 align:start position:0% of basically it's not the racial coding 00:36:55.660 --> 00:36:58.239 align:start position:0% of basically it's not the racial coding so<00:36:56.660> that<00:36:56.690> this<00:36:57.019> two<00:36:57.170> layers<00:36:57.410> vary<00:36:57.710> according 00:36:58.239 --> 00:36:58.249 align:start position:0% so that this two layers vary according 00:36:58.249 --> 00:36:59.499 align:start position:0% so that this two layers vary according one<00:36:58.400> would<00:36:58.880> be<00:36:59.029> to<00:36:59.150> take<00:36:59.299> care<00:36:59.329> of 00:36:59.499 --> 00:36:59.509 align:start position:0% one would be to take care of 00:36:59.509 --> 00:37:01.450 align:start position:0% one would be to take care of catastrophic<00:37:00.229> loss<00:37:00.410> and<00:37:00.650> this<00:37:01.069> one<00:37:01.279> of<00:37:01.400> the 00:37:01.450 --> 00:37:01.460 align:start position:0% catastrophic loss and this one of the 00:37:01.460 --> 00:37:04.630 align:start position:0% catastrophic loss and this one of the first<00:37:01.999> twist<00:37:02.239> is<00:37:02.660> just<00:37:02.869> guarantees<00:37:03.640> basically 00:37:04.630 --> 00:37:04.640 align:start position:0% first twist is just guarantees basically 00:37:04.640 --> 00:37:06.670 align:start position:0% first twist is just guarantees basically gives<00:37:05.150> an<00:37:05.299> upper<00:37:05.450> bound<00:37:05.719> to<00:37:05.989> the<00:37:06.109> to<00:37:06.349> the<00:37:06.440> 3d 00:37:06.670 --> 00:37:06.680 align:start position:0% gives an upper bound to the to the 3d 00:37:06.680 --> 00:37:09.719 align:start position:0% gives an upper bound to the to the 3d Retriever<00:37:07.219> latency<00:37:07.789> in<00:37:08.390> the<00:37:08.569> network<00:37:08.900> so 00:37:09.719 --> 00:37:09.729 align:start position:0% Retriever latency in the network so 00:37:09.729 --> 00:37:12.729 align:start position:0% Retriever latency in the network so let's<00:37:10.729> let's<00:37:11.390> that<00:37:11.630> scene<00:37:11.809> in<00:37:12.380> the<00:37:12.440> immediate 00:37:12.729 --> 00:37:12.739 align:start position:0% let's let's that scene in the immediate 00:37:12.739 --> 00:37:15.190 align:start position:0% let's let's that scene in the immediate roadmap<00:37:13.369> also<00:37:14.089> under<00:37:14.390> on<00:37:14.539> the<00:37:14.719> immediate 00:37:15.190 --> 00:37:15.200 align:start position:0% roadmap also under on the immediate 00:37:15.200 --> 00:37:17.920 align:start position:0% roadmap also under on the immediate roadmap<00:37:15.739> that<00:37:15.890> we<00:37:16.489> were<00:37:16.789> kind<00:37:17.180> of<00:37:17.299> moving<00:37:17.660> to 00:37:17.920 --> 00:37:17.930 align:start position:0% roadmap that we were kind of moving to 00:37:17.930 --> 00:37:20.229 align:start position:0% roadmap that we were kind of moving to the<00:37:18.259> new<00:37:18.380> cluster<00:37:18.829> setting<00:37:19.190> so<00:37:19.969> we're<00:37:20.119> gonna 00:37:20.229 --> 00:37:20.239 align:start position:0% the new cluster setting so we're gonna 00:37:20.239 --> 00:37:23.289 align:start position:0% the new cluster setting so we're gonna be<00:37:20.390> able<00:37:20.660> to<00:37:20.779> spawn<00:37:21.160> really<00:37:22.160> big<00:37:22.309> scale<00:37:22.670> scale 00:37:23.289 --> 00:37:23.299 align:start position:0% be able to spawn really big scale scale 00:37:23.299 --> 00:37:26.979 align:start position:0% be able to spawn really big scale scale scale<00:37:23.359> in<00:37:24.170> the<00:37:24.849> network<00:37:25.849> test<00:37:26.089> in<00:37:26.479> a<00:37:26.569> real 00:37:26.979 --> 00:37:26.989 align:start position:0% scale in the network test in a real 00:37:26.989 --> 00:37:32.319 align:start position:0% scale in the network test in a real setting<00:37:27.339> so<00:37:28.339> that's<00:37:29.200> Anton<00:37:30.200> Anton<00:37:31.099> and<00:37:31.329> Rafael 00:37:32.319 --> 00:37:32.329 align:start position:0% setting so that's Anton Anton and Rafael 00:37:32.329 --> 00:37:33.549 align:start position:0% setting so that's Anton Anton and Rafael are<00:37:32.420> working<00:37:32.779> on<00:37:32.900> a<00:37:32.930> kubernetes<00:37:33.380> cluster 00:37:33.549 --> 00:37:33.559 align:start position:0% are working on a kubernetes cluster 00:37:33.559 --> 00:37:38.170 align:start position:0% are working on a kubernetes cluster that's<00:37:34.549> that's<00:37:34.940> gonna<00:37:35.390> be<00:37:35.660> able<00:37:35.749> to<00:37:37.180> start 00:37:38.170 --> 00:37:38.180 align:start position:0% that's that's gonna be able to start 00:37:38.180 --> 00:37:40.839 align:start position:0% that's that's gonna be able to start spotting<00:37:38.779> sense<00:37:39.019> this<00:37:39.170> end<00:37:39.440> and<00:37:39.849> therefore 00:37:40.839 --> 00:37:40.849 align:start position:0% spotting sense this end and therefore 00:37:40.849 --> 00:37:43.209 align:start position:0% spotting sense this end and therefore neural<00:37:41.269> network<00:37:41.599> testing<00:37:42.039> framework<00:37:43.039> is 00:37:43.209 --> 00:37:43.219 align:start position:0% neural network testing framework is 00:37:43.219 --> 00:37:45.640 align:start position:0% neural network testing framework is going<00:37:43.489> to<00:37:43.700> be<00:37:43.759> able<00:37:44.450> to<00:37:44.630> test<00:37:44.900> like<00:37:45.380> really 00:37:45.640 --> 00:37:45.650 align:start position:0% going to be able to test like really 00:37:45.650 --> 00:37:47.849 align:start position:0% going to be able to test like really complicated<00:37:46.249> emergent<00:37:46.729> Network<00:37:47.089> scenarios 00:37:47.849 --> 00:37:47.859 align:start position:0% complicated emergent Network scenarios 00:37:47.859 --> 00:37:51.690 align:start position:0% complicated emergent Network scenarios okay<00:37:48.859> so<00:37:48.920> what<00:37:49.670> what<00:37:49.910> si<00:37:50.239> is<00:37:50.509> on<00:37:50.630> the<00:37:50.719> roadmap 00:37:51.690 --> 00:37:51.700 align:start position:0% okay so what what si is on the roadmap 00:37:51.700 --> 00:37:56.620 align:start position:0% okay so what what si is on the roadmap well<00:37:52.700> as<00:37:52.940> usual<00:37:53.749> we<00:37:53.869> still<00:37:55.089> very<00:37:56.089> heavily 00:37:56.620 --> 00:37:56.630 align:start position:0% well as usual we still very heavily 00:37:56.630 --> 00:37:58.779 align:start position:0% well as usual we still very heavily researching<00:37:57.410> how<00:37:57.829> how<00:37:58.069> exactly<00:37:58.460> we<00:37:58.609> do 00:37:58.779 --> 00:37:58.789 align:start position:0% researching how how exactly we do 00:37:58.789 --> 00:38:01.209 align:start position:0% researching how how exactly we do storage<00:37:59.150> insurance<00:37:59.660> then<00:38:00.349> we<00:38:00.499> mean<00:38:01.009> let<00:38:01.190> me 00:38:01.209 --> 00:38:01.219 align:start position:0% storage insurance then we mean let me 00:38:01.219 --> 00:38:02.410 align:start position:0% storage insurance then we mean let me now 00:38:02.410 --> 00:38:02.420 align:start position:0% now 00:38:02.420 --> 00:38:04.569 align:start position:0% now have<00:38:02.510> like<00:38:02.660> a<00:38:02.720> two<00:38:02.960> layered<00:38:03.260> system<00:38:03.950> that's 00:38:04.569 --> 00:38:04.579 align:start position:0% have like a two layered system that's 00:38:04.579 --> 00:38:08.170 align:start position:0% have like a two layered system that's that's<00:38:05.000> we're<00:38:05.390> planning<00:38:05.980> the<00:38:06.980> the<00:38:07.430> substance 00:38:08.170 --> 00:38:08.180 align:start position:0% that's we're planning the the substance 00:38:08.180 --> 00:38:09.730 align:start position:0% that's we're planning the the substance window<00:38:08.569> frame<00:38:08.839> work<00:38:09.020> which<00:38:09.140> is<00:38:09.410> generic 00:38:09.730 --> 00:38:09.740 align:start position:0% window frame work which is generic 00:38:09.740 --> 00:38:13.030 align:start position:0% window frame work which is generic framework<00:38:09.950> for<00:38:10.460> four<00:38:11.230> basically<00:38:12.230> are<00:38:12.680> at<00:38:12.859> the 00:38:13.030 --> 00:38:13.040 align:start position:0% framework for four basically are at the 00:38:13.040 --> 00:38:15.930 align:start position:0% framework for four basically are at the Coney<00:38:13.309> station<00:38:13.880> or<00:38:14.000> networks<00:38:14.390> and<00:38:14.660> and<00:38:15.079> also<00:38:15.349> a 00:38:15.930 --> 00:38:15.940 align:start position:0% Coney station or networks and and also a 00:38:15.940 --> 00:38:20.319 align:start position:0% Coney station or networks and and also a contract<00:38:16.990> support<00:38:17.990> form<00:38:18.290> for<00:38:19.069> service<00:38:19.579> level 00:38:20.319 --> 00:38:20.329 align:start position:0% contract support form for service level 00:38:20.329 --> 00:38:22.569 align:start position:0% contract support form for service level agreements<00:38:20.869> that<00:38:21.410> are<00:38:21.530> challengeable<00:38:22.069> on<00:38:22.400> the 00:38:22.569 --> 00:38:22.579 align:start position:0% agreements that are challengeable on the 00:38:22.579 --> 00:38:25.270 align:start position:0% agreements that are challengeable on the blockchain<00:38:22.760> so<00:38:23.119> it's<00:38:23.480> kind<00:38:23.630> of<00:38:23.720> a<00:38:23.890> our<00:38:24.890> take<00:38:25.130> on 00:38:25.270 --> 00:38:25.280 align:start position:0% blockchain so it's kind of a our take on 00:38:25.280 --> 00:38:26.920 align:start position:0% blockchain so it's kind of a our take on state<00:38:25.549> channels<00:38:25.910> combined<00:38:26.599> with<00:38:26.809> the 00:38:26.920 --> 00:38:26.930 align:start position:0% state channels combined with the 00:38:26.930 --> 00:38:29.589 align:start position:0% state channels combined with the blockchain<00:38:27.829> as<00:38:28.160> a<00:38:28.190> judge<00:38:28.460> paradigm<00:38:28.970> so<00:38:29.510> the 00:38:29.589 --> 00:38:29.599 align:start position:0% blockchain as a judge paradigm so the 00:38:29.599 --> 00:38:31.329 align:start position:0% blockchain as a judge paradigm so the sorcerer<00:38:29.960> and<00:38:30.140> since<00:38:30.589> we<00:38:30.740> know<00:38:30.799> the<00:38:30.920> contracts 00:38:31.329 --> 00:38:31.339 align:start position:0% sorcerer and since we know the contracts 00:38:31.339 --> 00:38:37.329 align:start position:0% sorcerer and since we know the contracts which<00:38:31.490> has<00:38:32.329> been<00:38:32.589> developed<00:38:33.589> and<00:38:33.710> and<00:38:36.339> tested 00:38:37.329 --> 00:38:37.339 align:start position:0% which has been developed and and tested 00:38:37.339 --> 00:38:39.789 align:start position:0% which has been developed and and tested with<00:38:37.549> by<00:38:38.210> Bhairav<00:38:38.900> you'll<00:38:39.200> hear<00:38:39.349> from<00:38:39.380> from 00:38:39.789 --> 00:38:39.799 align:start position:0% with by Bhairav you'll hear from from 00:38:39.799 --> 00:38:40.299 align:start position:0% with by Bhairav you'll hear from from Riyadh 00:38:40.299 --> 00:38:40.309 align:start position:0% Riyadh 00:38:40.309 --> 00:38:42.670 align:start position:0% Riyadh so<00:38:40.819> our<00:38:41.030> it<00:38:41.510> so<00:38:41.630> narrowed<00:38:41.930> not<00:38:42.079> to<00:38:42.230> finish<00:38:42.530> this 00:38:42.670 --> 00:38:42.680 align:start position:0% so our it so narrowed not to finish this 00:38:42.680 --> 00:38:45.930 align:start position:0% so our it so narrowed not to finish this this<00:38:43.160> part<00:38:43.430> and<00:38:43.609> and<00:38:44.299> introduce<00:38:45.079> the<00:38:45.260> the 00:38:45.930 --> 00:38:45.940 align:start position:0% this part and and introduce the the 00:38:45.940 --> 00:38:48.280 align:start position:0% this part and and introduce the the option<00:38:46.940> to<00:38:47.059> have<00:38:47.119> like<00:38:47.329> service<00:38:47.690> networks<00:38:48.109> and 00:38:48.280 --> 00:38:48.290 align:start position:0% option to have like service networks and 00:38:48.290 --> 00:38:50.770 align:start position:0% option to have like service networks and so<00:38:48.410> on<00:38:48.500> the<00:38:49.250> Savi<00:38:49.490> research<00:38:49.880> on<00:38:50.119> on<00:38:50.299> databases 00:38:50.770 --> 00:38:50.780 align:start position:0% so on the Savi research on on databases 00:38:50.780 --> 00:38:54.250 align:start position:0% so on the Savi research on on databases or<00:38:51.079> swarm<00:38:51.349> and<00:38:51.650> we<00:38:52.400> we<00:38:53.150> realize<00:38:53.690> that<00:38:53.960> there's 00:38:54.250 --> 00:38:54.260 align:start position:0% or swarm and we we realize that there's 00:38:54.260 --> 00:38:55.870 align:start position:0% or swarm and we we realize that there's a<00:38:54.349> lot<00:38:54.500> of<00:38:54.530> usability<00:38:55.309> issues<00:38:55.549> in<00:38:55.760> general 00:38:55.870 --> 00:38:55.880 align:start position:0% a lot of usability issues in general 00:38:55.880 --> 00:38:58.539 align:start position:0% a lot of usability issues in general with<00:38:56.210> swarm<00:38:56.480> so<00:38:56.690> so<00:38:57.410> we're<00:38:57.740> gonna<00:38:57.829> put<00:38:58.309> a<00:38:58.339> lot 00:38:58.539 --> 00:38:58.549 align:start position:0% with swarm so so we're gonna put a lot 00:38:58.549 --> 00:39:00.910 align:start position:0% with swarm so so we're gonna put a lot more<00:38:58.579> effort<00:38:58.819> into<00:38:59.210> into<00:39:00.109> developing<00:39:00.770> and 00:39:00.910 --> 00:39:00.920 align:start position:0% more effort into into developing and 00:39:00.920 --> 00:39:03.940 align:start position:0% more effort into into developing and supporting<00:39:01.930> deaf<00:39:02.930> tooling<00:39:03.319> so<00:39:03.559> basically 00:39:03.940 --> 00:39:03.950 align:start position:0% supporting deaf tooling so basically 00:39:03.950 --> 00:39:06.130 align:start position:0% supporting deaf tooling so basically bindings<00:39:04.400> in<00:39:04.549> various<00:39:04.849> language<00:39:05.210> then<00:39:05.420> most 00:39:06.130 --> 00:39:06.140 align:start position:0% bindings in various language then most 00:39:06.140 --> 00:39:08.950 align:start position:0% bindings in various language then most prominently<00:39:07.030> provide<00:39:08.030> better<00:39:08.270> JavaScript 00:39:08.950 --> 00:39:08.960 align:start position:0% prominently provide better JavaScript 00:39:08.960 --> 00:39:11.680 align:start position:0% prominently provide better JavaScript support<00:39:09.460> together<00:39:10.460> with<00:39:10.819> some<00:39:11.270> of<00:39:11.420> my<00:39:11.450> friends 00:39:11.680 --> 00:39:11.690 align:start position:0% support together with some of my friends 00:39:11.690 --> 00:39:14.530 align:start position:0% support together with some of my friends and<00:39:12.020> and<00:39:12.349> allies<00:39:12.859> in<00:39:13.069> the<00:39:13.190> ecosystem<00:39:13.819> so 00:39:14.530 --> 00:39:14.540 align:start position:0% and and allies in the ecosystem so 00:39:14.540 --> 00:39:22.089 align:start position:0% and and allies in the ecosystem so that's<00:39:15.410> about<00:39:15.559> it<00:39:15.680> for<00:39:16.339> the<00:39:16.490> update<00:39:21.069> yeah 00:39:22.089 --> 00:39:22.099 align:start position:0% that's about it for the update yeah 00:39:22.099 --> 00:39:24.579 align:start position:0% that's about it for the update yeah Thank<00:39:22.640> You<00:39:22.700> Victor<00:39:23.180> so<00:39:23.900> I<00:39:23.930> said<00:39:24.170> that's<00:39:24.349> about 00:39:24.579 --> 00:39:24.589 align:start position:0% Thank You Victor so I said that's about 00:39:24.589 --> 00:39:27.280 align:start position:0% Thank You Victor so I said that's about it<00:39:24.880> it<00:39:25.880> would<00:39:26.119> be<00:39:26.210> a<00:39:26.240> mess<00:39:26.450> at<00:39:26.599> this<00:39:26.750> point<00:39:27.020> if 00:39:27.280 --> 00:39:27.290 align:start position:0% it it would be a mess at this point if 00:39:27.290 --> 00:39:28.809 align:start position:0% it it would be a mess at this point if we<00:39:27.319> didn't<00:39:27.680> mention<00:39:27.829> that<00:39:28.040> there's<00:39:28.430> more<00:39:28.640> to 00:39:28.809 --> 00:39:28.819 align:start position:0% we didn't mention that there's more to 00:39:28.819 --> 00:39:30.609 align:start position:0% we didn't mention that there's more to swarm<00:39:29.089> than<00:39:29.270> just<00:39:29.480> the<00:39:29.599> swarm<00:39:29.869> team<00:39:30.079> the 00:39:30.609 --> 00:39:30.619 align:start position:0% swarm than just the swarm team the 00:39:30.619 --> 00:39:31.960 align:start position:0% swarm than just the swarm team the community<00:39:31.069> has<00:39:31.190> grown<00:39:31.369> this<00:39:31.640> year<00:39:31.700> we've 00:39:31.960 --> 00:39:31.970 align:start position:0% community has grown this year we've 00:39:31.970 --> 00:39:33.760 align:start position:0% community has grown this year we've gotten<00:39:32.150> a<00:39:32.299> lot<00:39:32.450> of<00:39:32.630> contributions<00:39:32.960> from<00:39:33.349> third 00:39:33.760 --> 00:39:33.770 align:start position:0% gotten a lot of contributions from third 00:39:33.770 --> 00:39:35.760 align:start position:0% gotten a lot of contributions from third parties<00:39:34.130> the<00:39:34.430> always<00:39:34.730> awesome<00:39:34.910> mainframe 00:39:35.760 --> 00:39:35.770 align:start position:0% parties the always awesome mainframe 00:39:35.770 --> 00:39:37.890 align:start position:0% parties the always awesome mainframe status<00:39:36.770> has<00:39:36.920> been<00:39:37.069> helping<00:39:37.400> us<00:39:37.490> with<00:39:37.609> the 00:39:37.890 --> 00:39:37.900 align:start position:0% status has been helping us with the 00:39:37.900 --> 00:39:40.390 align:start position:0% status has been helping us with the mobile<00:39:38.900> devices<00:39:39.650> we've<00:39:39.829> got<00:39:39.950> volcon 00:39:40.390 --> 00:39:40.400 align:start position:0% mobile devices we've got volcon 00:39:40.400 --> 00:39:43.150 align:start position:0% mobile devices we've got volcon databases<00:39:41.119> data<00:39:41.869> fund<00:39:42.170> is<00:39:42.440> awesome<00:39:42.890> they<00:39:43.010> make 00:39:43.150 --> 00:39:43.160 align:start position:0% databases data fund is awesome they make 00:39:43.160 --> 00:39:44.980 align:start position:0% databases data fund is awesome they make orange<00:39:43.460> sweat<00:39:43.790> shirts<00:39:44.059> and<00:39:44.390> other<00:39:44.660> orange 00:39:44.980 --> 00:39:44.990 align:start position:0% orange sweat shirts and other orange 00:39:44.990 --> 00:39:47.620 align:start position:0% orange sweat shirts and other orange gear<00:39:45.200> for<00:39:45.440> us<00:39:45.530> that's<00:39:45.819> wonderful<00:39:46.819> guys<00:39:47.030> so 00:39:47.620 --> 00:39:47.630 align:start position:0% gear for us that's wonderful guys so 00:39:47.630 --> 00:39:49.150 align:start position:0% gear for us that's wonderful guys so thank<00:39:47.960> you<00:39:48.079> everyone<00:39:48.380> on<00:39:48.619> this<00:39:48.740> list<00:39:48.799> and 00:39:49.150 --> 00:39:49.160 align:start position:0% thank you everyone on this list and 00:39:49.160 --> 00:39:50.740 align:start position:0% thank you everyone on this list and everyone<00:39:49.490> else<00:39:49.640> who's<00:39:49.940> joining<00:39:50.299> the<00:39:50.510> swarm 00:39:50.740 --> 00:39:50.750 align:start position:0% everyone else who's joining the swarm 00:39:50.750 --> 00:39:53.349 align:start position:0% everyone else who's joining the swarm community<00:39:51.140> this<00:39:52.130> is<00:39:52.190> the<00:39:52.369> team<00:39:52.670> at<00:39:52.910> the<00:39:53.059> orange 00:39:53.349 --> 00:39:53.359 align:start position:0% community this is the team at the orange 00:39:53.359 --> 00:39:54.940 align:start position:0% community this is the team at the orange summit<00:39:53.690> last<00:39:53.809> year<00:39:54.109> we<00:39:54.260> have<00:39:54.380> once<00:39:54.650> warm 00:39:54.940 --> 00:39:54.950 align:start position:0% summit last year we have once warm 00:39:54.950 --> 00:39:57.280 align:start position:0% summit last year we have once warm orange<00:39:55.190> summit<00:39:55.609> every<00:39:55.880> year<00:39:56.119> we're<00:39:56.869> hopefully 00:39:57.280 --> 00:39:57.290 align:start position:0% orange summit every year we're hopefully 00:39:57.290 --> 00:39:59.380 align:start position:0% orange summit every year we're hopefully have<00:39:57.500> one<00:39:57.650> next<00:39:57.829> year<00:39:58.069> so<00:39:58.280> you're<00:39:59.030> welcome<00:39:59.210> to 00:39:59.380 --> 00:39:59.390 align:start position:0% have one next year so you're welcome to 00:39:59.390 --> 00:40:02.740 align:start position:0% have one next year so you're welcome to attend<00:39:59.809> keep<00:40:00.260> a<00:40:00.380> lookout<00:40:00.619> for<00:40:00.859> that<00:40:01.750> here's 00:40:02.740 --> 00:40:02.750 align:start position:0% attend keep a lookout for that here's 00:40:02.750 --> 00:40:05.380 align:start position:0% attend keep a lookout for that here's our<00:40:02.960> contact<00:40:03.500> we<00:40:03.799> have<00:40:04.150> I've<00:40:05.150> already 00:40:05.380 --> 00:40:05.390 align:start position:0% our contact we have I've already 00:40:05.390 --> 00:40:06.760 align:start position:0% our contact we have I've already mentioned<00:40:05.540> swarmed<00:40:05.960> of<00:40:06.020> the<00:40:06.109> theorem<00:40:06.380> org 00:40:06.760 --> 00:40:06.770 align:start position:0% mentioned swarmed of the theorem org 00:40:06.770 --> 00:40:08.740 align:start position:0% mentioned swarmed of the theorem org we've<00:40:07.010> started<00:40:07.309> our<00:40:07.520> own<00:40:07.549> Twitter<00:40:08.089> and<00:40:08.359> reddit 00:40:08.740 --> 00:40:08.750 align:start position:0% we've started our own Twitter and reddit 00:40:08.750 --> 00:40:11.680 align:start position:0% we've started our own Twitter and reddit called<00:40:09.319> eath<00:40:09.559> swarm<00:40:10.040> I<00:40:10.309> promise<00:40:11.210> there's<00:40:11.450> not 00:40:11.680 --> 00:40:11.690 align:start position:0% called eath swarm I promise there's not 00:40:11.690 --> 00:40:14.190 align:start position:0% called eath swarm I promise there's not a<00:40:11.720> lot<00:40:11.960> in<00:40:12.140> there<00:40:12.349> this<00:40:12.530> is<00:40:12.650> a<00:40:12.680> low 00:40:14.190 --> 00:40:14.200 align:start position:0% a lot in there this is a low 00:40:14.200 --> 00:40:15.539 align:start position:0% a lot in there this is a low environment<00:40:14.680> but<00:40:15.069> that's<00:40:15.249> where<00:40:15.400> you<00:40:15.460> get 00:40:15.539 --> 00:40:15.549 align:start position:0% environment but that's where you get 00:40:15.549 --> 00:40:17.640 align:start position:0% environment but that's where you get updates<00:40:15.999> will<00:40:16.359> make<00:40:16.509> release<00:40:16.900> announcements 00:40:17.640 --> 00:40:17.650 align:start position:0% updates will make release announcements 00:40:17.650 --> 00:40:20.160 align:start position:0% updates will make release announcements and<00:40:18.430> when<00:40:19.180> we<00:40:19.329> have<00:40:19.450> a<00:40:19.479> talk<00:40:19.719> somewhere<00:40:19.900> or 00:40:20.160 --> 00:40:20.170 align:start position:0% and when we have a talk somewhere or 00:40:20.170 --> 00:40:21.930 align:start position:0% and when we have a talk somewhere or when<00:40:20.349> our<00:40:20.499> or<00:40:20.680> in<00:40:20.799> some<00:40:21.039> it<00:40:21.219> is<00:40:21.249> coming<00:40:21.640> up 00:40:21.930 --> 00:40:21.940 align:start position:0% when our or in some it is coming up 00:40:21.940 --> 00:40:24.839 align:start position:0% when our or in some it is coming up that's<00:40:22.269> weird<00:40:22.509> look<00:40:23.589> that's<00:40:23.979> our<00:40:24.160> Gator<00:40:24.339> swarm 00:40:24.839 --> 00:40:24.849 align:start position:0% that's weird look that's our Gator swarm 00:40:24.849 --> 00:40:26.819 align:start position:0% that's weird look that's our Gator swarm at<00:40:24.999> a<00:40:25.029> theorem<00:40:25.420> org<00:40:25.779> if<00:40:25.930> you<00:40:25.989> want<00:40:26.170> to<00:40:26.259> talk<00:40:26.619> if 00:40:26.819 --> 00:40:26.829 align:start position:0% at a theorem org if you want to talk if 00:40:26.829 --> 00:40:27.539 align:start position:0% at a theorem org if you want to talk if you<00:40:26.859> want<00:40:27.069> to<00:40:27.130> write<00:40:27.249> to<00:40:27.400> us<00:40:27.430> directly 00:40:27.539 --> 00:40:27.549 align:start position:0% you want to write to us directly 00:40:27.549 --> 00:40:29.759 align:start position:0% you want to write to us directly otherwise<00:40:28.059> come<00:40:28.569> find<00:40:28.839> someone<00:40:29.200> in<00:40:29.319> orange<00:40:29.619> at 00:40:29.759 --> 00:40:29.769 align:start position:0% otherwise come find someone in orange at 00:40:29.769 --> 00:40:31.200 align:start position:0% otherwise come find someone in orange at the<00:40:29.890> conference<00:40:30.279> and<00:40:30.460> come<00:40:30.549> talk<00:40:30.729> to<00:40:30.759> us<00:40:30.910> thank 00:40:31.200 --> 00:40:31.210 align:start position:0% the conference and come talk to us thank 00:40:31.210 --> 00:40:31.820 align:start position:0% the conference and come talk to us thank you<00:40:31.239> very<00:40:31.359> much 00:40:31.820 --> 00:40:31.830 align:start position:0% you very much 00:40:31.830 --> 00:40:42.080 align:start position:0% you very much [Applause] 00:40:42.080 --> 00:40:42.090 align:start position:0% 00:40:42.090 --> 00:40:44.150 align:start position:0% you