WEBVTT Kind: captions Language: en 00:00:15.800 --> 00:00:23.750 align:start position:0% okay<00:00:16.820> so<00:00:18.680> networking<00:00:22.220> one<00:00:23.220> of<00:00:23.400> the<00:00:23.519> most 00:00:23.750 --> 00:00:23.760 align:start position:0% okay so networking one of the most 00:00:23.760 --> 00:00:26.870 align:start position:0% okay so networking one of the most common<00:00:24.449> questions<00:00:25.220> when<00:00:26.220> asked<00:00:26.820> about 00:00:26.870 --> 00:00:26.880 align:start position:0% common questions when asked about 00:00:26.880 --> 00:00:31.910 align:start position:0% common questions when asked about athyrium<00:00:27.660> is<00:00:27.930> how<00:00:28.859> is<00:00:29.039> it<00:00:29.189> different<00:00:30.890> how's<00:00:31.890> it 00:00:31.910 --> 00:00:31.920 align:start position:0% athyrium is how is it different how's it 00:00:31.920 --> 00:00:36.020 align:start position:0% athyrium is how is it different how's it different<00:00:32.189> from<00:00:32.450> bitcoin<00:00:33.450> specifically<00:00:35.030> and 00:00:36.020 --> 00:00:36.030 align:start position:0% different from bitcoin specifically and 00:00:36.030 --> 00:00:39.680 align:start position:0% different from bitcoin specifically and i<00:00:36.780> think<00:00:37.280> networking<00:00:38.280> is<00:00:38.730> probably<00:00:39.270> one<00:00:39.660> of 00:00:39.680 --> 00:00:39.690 align:start position:0% i think networking is probably one of 00:00:39.690 --> 00:00:43.430 align:start position:0% i think networking is probably one of the<00:00:40.170> areas<00:00:40.940> where<00:00:42.290> athyrium<00:00:43.290> is 00:00:43.430 --> 00:00:43.440 align:start position:0% the areas where athyrium is 00:00:43.440 --> 00:00:53.410 align:start position:0% the areas where athyrium is significantly<00:00:44.040> different<00:00:47.180> so<00:00:49.700> yeah 00:00:53.410 --> 00:00:53.420 align:start position:0% 00:00:53.420 --> 00:00:58.220 align:start position:0% networking<00:00:55.039> what<00:00:56.039> is<00:00:56.160> the<00:00:56.280> network<00:00:57.230> everyone 00:00:58.220 --> 00:00:58.230 align:start position:0% networking what is the network everyone 00:00:58.230 --> 00:01:03.500 align:start position:0% networking what is the network everyone here<00:00:58.590> is<00:00:58.770> a<00:00:59.309> network<00:01:00.980> they<00:01:01.980> say<00:01:02.550> that<00:01:02.579> the<00:01:03.329> way 00:01:03.500 --> 00:01:03.510 align:start position:0% here is a network they say that the way 00:01:03.510 --> 00:01:05.390 align:start position:0% here is a network they say that the way that<00:01:03.719> our<00:01:03.750> brains<00:01:04.140> work<00:01:04.439> is<00:01:04.739> the<00:01:04.979> neural 00:01:05.390 --> 00:01:05.400 align:start position:0% that our brains work is the neural 00:01:05.400 --> 00:01:10.820 align:start position:0% that our brains work is the neural network<00:01:05.729> so<00:01:06.860> it<00:01:08.659> only<00:01:09.659> makes<00:01:09.780> sense<00:01:10.080> that<00:01:10.409> we 00:01:10.820 --> 00:01:10.830 align:start position:0% network so it only makes sense that we 00:01:10.830 --> 00:01:13.370 align:start position:0% network so it only makes sense that we created<00:01:11.280> the<00:01:11.460> internet<00:01:11.840> which<00:01:12.840> is<00:01:12.869> also<00:01:13.229> a 00:01:13.370 --> 00:01:13.380 align:start position:0% created the internet which is also a 00:01:13.380 --> 00:01:16.210 align:start position:0% created the internet which is also a network<00:01:13.710> to<00:01:14.070> connect<00:01:14.700> all<00:01:14.790> of<00:01:14.850> us<00:01:15.060> together 00:01:16.210 --> 00:01:16.220 align:start position:0% network to connect all of us together 00:01:16.220 --> 00:01:22.390 align:start position:0% network to connect all of us together and<00:01:19.880> we've<00:01:20.880> become<00:01:21.240> very<00:01:21.299> dependent<00:01:21.720> on<00:01:22.110> this 00:01:22.390 --> 00:01:22.400 align:start position:0% and we've become very dependent on this 00:01:22.400 --> 00:01:27.770 align:start position:0% and we've become very dependent on this our<00:01:23.540> economy<00:01:24.540> functions<00:01:25.530> on<00:01:26.070> networks<00:01:26.780> our 00:01:27.770 --> 00:01:27.780 align:start position:0% our economy functions on networks our 00:01:27.780 --> 00:01:29.780 align:start position:0% our economy functions on networks our cell<00:01:28.080> phones<00:01:28.350> function<00:01:28.829> on<00:01:29.040> networks<00:01:29.490> are 00:01:29.780 --> 00:01:29.790 align:start position:0% cell phones function on networks are 00:01:29.790 --> 00:01:35.679 align:start position:0% cell phones function on networks are corporations<00:01:30.659> function<00:01:31.350> on<00:01:31.470> networks<00:01:32.180> and<00:01:33.950> as 00:01:35.679 --> 00:01:35.689 align:start position:0% corporations function on networks and as 00:01:35.689 --> 00:01:44.120 align:start position:0% corporations function on networks and as engineers<00:01:36.689> we<00:01:36.780> found<00:01:37.740> ways<00:01:38.009> to<00:01:40.159> to<00:01:43.130> define 00:01:44.120 --> 00:01:44.130 align:start position:0% engineers we found ways to to define 00:01:44.130 --> 00:01:47.840 align:start position:0% engineers we found ways to to define networking<00:01:44.820> and<00:01:45.140> to<00:01:46.140> define<00:01:47.100> its<00:01:47.369> function 00:01:47.840 --> 00:01:47.850 align:start position:0% networking and to define its function 00:01:47.850 --> 00:01:50.149 align:start position:0% networking and to define its function and<00:01:48.030> to<00:01:48.509> replicate<00:01:49.110> that<00:01:49.140> and<00:01:49.590> to<00:01:49.799> build<00:01:50.009> on 00:01:50.149 --> 00:01:50.159 align:start position:0% and to replicate that and to build on 00:01:50.159 --> 00:01:57.980 align:start position:0% and to replicate that and to build on top<00:01:50.310> of<00:01:50.520> that<00:01:51.860> this<00:01:52.860> is<00:01:53.100> a<00:01:55.250> image<00:01:56.250> of<00:01:56.990> various 00:01:57.980 --> 00:01:57.990 align:start position:0% top of that this is a image of various 00:01:57.990 --> 00:02:04.789 align:start position:0% top of that this is a image of various systems<00:01:59.060> used<00:02:00.060> to<00:02:00.360> power<00:02:01.259> the<00:02:01.469> internet<00:02:03.799> I'm 00:02:04.789 --> 00:02:04.799 align:start position:0% systems used to power the internet I'm 00:02:04.799 --> 00:02:08.350 align:start position:0% systems used to power the internet I'm sure<00:02:05.100> everyone<00:02:05.430> here<00:02:05.820> has<00:02:05.969> heard<00:02:06.149> of<00:02:06.390> ethernet 00:02:08.350 --> 00:02:08.360 align:start position:0% sure everyone here has heard of ethernet 00:02:08.360 --> 00:02:10.699 align:start position:0% sure everyone here has heard of ethernet networking<00:02:09.360> equipment<00:02:09.720> switching<00:02:10.500> equipment 00:02:10.699 --> 00:02:10.709 align:start position:0% networking equipment switching equipment 00:02:10.709 --> 00:02:12.580 align:start position:0% networking equipment switching equipment IT<00:02:11.310> operations 00:02:12.580 --> 00:02:12.590 align:start position:0% IT operations 00:02:12.590 --> 00:02:15.250 align:start position:0% IT operations a<00:02:13.190> lot<00:02:13.819> of<00:02:13.849> systems<00:02:14.420> today<00:02:14.599> now<00:02:14.989> run<00:02:15.230> on 00:02:15.250 --> 00:02:15.260 align:start position:0% a lot of systems today now run on 00:02:15.260 --> 00:02:17.259 align:start position:0% a lot of systems today now run on Ethernet<00:02:15.950> and<00:02:16.129> that<00:02:16.489> used<00:02:16.670> to<00:02:16.819> not<00:02:16.970> always<00:02:17.120> be 00:02:17.259 --> 00:02:17.269 align:start position:0% Ethernet and that used to not always be 00:02:17.269 --> 00:02:20.380 align:start position:0% Ethernet and that used to not always be the<00:02:17.450> case<00:02:18.459> one<00:02:19.459> interesting<00:02:19.849> story<00:02:20.330> about 00:02:20.380 --> 00:02:20.390 align:start position:0% the case one interesting story about 00:02:20.390 --> 00:02:26.949 align:start position:0% the case one interesting story about Ethernet<00:02:21.080> though<00:02:22.420> is<00:02:23.420> that<00:02:25.540> get<00:02:26.540> a<00:02:26.569> little<00:02:26.840> bit 00:02:26.949 --> 00:02:26.959 align:start position:0% Ethernet though is that get a little bit 00:02:26.959 --> 00:02:31.979 align:start position:0% Ethernet though is that get a little bit of<00:02:27.050> feedback<00:02:27.200> is<00:02:28.239> that<00:02:29.239> it<00:02:29.540> used<00:02:29.750> to<00:02:29.900> be<00:02:30.049> a<00:02:30.319> hub 00:02:31.979 --> 00:02:31.989 align:start position:0% of feedback is that it used to be a hub 00:02:31.989 --> 00:02:36.190 align:start position:0% of feedback is that it used to be a hub broadcast<00:02:32.989> based<00:02:33.319> system<00:02:33.769> and<00:02:35.049> what<00:02:36.049> this 00:02:36.190 --> 00:02:36.200 align:start position:0% broadcast based system and what this 00:02:36.200 --> 00:02:39.759 align:start position:0% broadcast based system and what this means<00:02:36.260> is<00:02:36.769> that<00:02:37.030> when<00:02:38.030> one<00:02:38.629> device<00:02:38.989> sends<00:02:39.650> out 00:02:39.759 --> 00:02:39.769 align:start position:0% means is that when one device sends out 00:02:39.769 --> 00:02:42.539 align:start position:0% means is that when one device sends out a<00:02:39.799> packet<00:02:40.099> it<00:02:40.730> goes<00:02:40.910> to<00:02:41.090> all<00:02:41.209> of<00:02:41.360> the<00:02:41.480> devices 00:02:42.539 --> 00:02:42.549 align:start position:0% a packet it goes to all of the devices 00:02:42.549 --> 00:02:46.410 align:start position:0% a packet it goes to all of the devices there<00:02:43.549> was<00:02:43.760> no<00:02:43.970> filtering<00:02:44.420> there<00:02:44.959> was<00:02:45.140> no 00:02:46.410 --> 00:02:46.420 align:start position:0% there was no filtering there was no 00:02:46.420 --> 00:02:49.839 align:start position:0% there was no filtering there was no there<00:02:47.420> were<00:02:47.510> no<00:02:47.540> limitations<00:02:48.260> so<00:02:48.709> if<00:02:48.980> you<00:02:49.519> had 00:02:49.839 --> 00:02:49.849 align:start position:0% there were no limitations so if you had 00:02:49.849 --> 00:02:53.080 align:start position:0% there were no limitations so if you had a<00:02:50.180> system<00:02:50.690> with<00:02:50.900> 10<00:02:51.230> devices<00:02:51.560> on<00:02:51.920> it<00:02:52.069> you'd<00:02:52.880> be 00:02:53.080 --> 00:02:53.090 align:start position:0% a system with 10 devices on it you'd be 00:02:53.090 --> 00:02:54.789 align:start position:0% a system with 10 devices on it you'd be fine<00:02:53.329> if<00:02:53.569> you<00:02:53.989> went<00:02:54.140> to<00:02:54.200> a<00:02:54.290> hundred<00:02:54.500> or<00:02:54.769> a 00:02:54.789 --> 00:02:54.799 align:start position:0% fine if you went to a hundred or a 00:02:54.799 --> 00:02:56.289 align:start position:0% fine if you went to a hundred or a thousand<00:02:55.190> devices<00:02:55.579> it<00:02:55.730> just<00:02:56.000> wouldn't<00:02:56.150> work 00:02:56.289 --> 00:02:56.299 align:start position:0% thousand devices it just wouldn't work 00:02:56.299 --> 00:02:58.479 align:start position:0% thousand devices it just wouldn't work because<00:02:56.930> the<00:02:57.739> network<00:02:57.920> would<00:02:58.250> try<00:02:58.430> and 00:02:58.479 --> 00:02:58.489 align:start position:0% because the network would try and 00:02:58.489 --> 00:03:01.720 align:start position:0% because the network would try and deliver<00:02:58.849> every<00:02:59.420> message<00:02:59.750> to<00:02:59.959> everyone<00:03:00.730> for 00:03:01.720 --> 00:03:01.730 align:start position:0% deliver every message to everyone for 00:03:01.730 --> 00:03:07.119 align:start position:0% deliver every message to everyone for every<00:03:01.940> packet<00:03:03.579> so<00:03:04.579> to<00:03:05.650> to<00:03:06.650> resolve<00:03:06.950> that<00:03:07.069> issue 00:03:07.119 --> 00:03:07.129 align:start position:0% every packet so to to resolve that issue 00:03:07.129 --> 00:03:10.720 align:start position:0% every packet so to to resolve that issue they<00:03:07.910> came<00:03:08.269> up<00:03:08.299> with<00:03:08.450> switched<00:03:08.959> networks<00:03:09.730> and 00:03:10.720 --> 00:03:10.730 align:start position:0% they came up with switched networks and 00:03:10.730 --> 00:03:12.640 align:start position:0% they came up with switched networks and today<00:03:11.239> we<00:03:11.420> have<00:03:11.569> switch<00:03:11.840> Ethernet<00:03:12.349> we<00:03:12.500> also 00:03:12.640 --> 00:03:12.650 align:start position:0% today we have switch Ethernet we also 00:03:12.650 --> 00:03:15.610 align:start position:0% today we have switch Ethernet we also have<00:03:13.180> another<00:03:14.180> virtual<00:03:14.629> layer<00:03:14.870> of<00:03:15.140> Ethernet 00:03:15.610 --> 00:03:15.620 align:start position:0% have another virtual layer of Ethernet 00:03:15.620 --> 00:03:21.610 align:start position:0% have another virtual layer of Ethernet called<00:03:15.860> VPN<00:03:16.370> a<00:03:17.239> sorry<00:03:18.170> V<00:03:18.410> win<00:03:19.120> and<00:03:20.380> that<00:03:21.380> is 00:03:21.610 --> 00:03:21.620 align:start position:0% called VPN a sorry V win and that is 00:03:21.620 --> 00:03:28.710 align:start position:0% called VPN a sorry V win and that is used<00:03:21.889> to<00:03:22.160> further<00:03:23.739> allow<00:03:26.019> switch<00:03:27.019> networks<00:03:27.530> to 00:03:28.710 --> 00:03:28.720 align:start position:0% used to further allow switch networks to 00:03:28.720 --> 00:03:32.500 align:start position:0% used to further allow switch networks to filter<00:03:29.720> and<00:03:29.989> route<00:03:30.560> traffic<00:03:30.859> in<00:03:31.250> a<00:03:31.340> way<00:03:31.519> that 00:03:32.500 --> 00:03:32.510 align:start position:0% filter and route traffic in a way that 00:03:32.510 --> 00:03:34.960 align:start position:0% filter and route traffic in a way that is<00:03:32.810> can<00:03:33.530> be<00:03:33.650> optimized<00:03:34.130> for<00:03:34.280> the<00:03:34.489> network<00:03:34.790> that 00:03:34.960 --> 00:03:34.970 align:start position:0% is can be optimized for the network that 00:03:34.970 --> 00:03:38.440 align:start position:0% is can be optimized for the network that is<00:03:35.120> built<00:03:35.329> for<00:03:36.790> so<00:03:37.790> why<00:03:38.000> is<00:03:38.060> that<00:03:38.180> interesting 00:03:38.440 --> 00:03:38.450 align:start position:0% is built for so why is that interesting 00:03:38.450 --> 00:03:40.870 align:start position:0% is built for so why is that interesting I<00:03:39.049> think<00:03:39.950> that's<00:03:40.069> interesting<00:03:40.609> because<00:03:40.700> I 00:03:40.870 --> 00:03:40.880 align:start position:0% I think that's interesting because I 00:03:40.880 --> 00:03:45.550 align:start position:0% I think that's interesting because I think<00:03:41.269> today<00:03:41.450> with<00:03:42.079> Bitcoin<00:03:42.530> and<00:03:42.919> athyrium<00:03:44.560> we 00:03:45.550 --> 00:03:45.560 align:start position:0% think today with Bitcoin and athyrium we 00:03:45.560 --> 00:03:51.159 align:start position:0% think today with Bitcoin and athyrium we are<00:03:45.859> at<00:03:46.099> that<00:03:46.310> stage<00:03:46.549> so<00:03:47.450> with<00:03:49.030> with<00:03:50.030> with<00:03:50.359> with 00:03:51.159 --> 00:03:51.169 align:start position:0% are at that stage so with with with with 00:03:51.169 --> 00:03:53.250 align:start position:0% are at that stage so with with with with Bitcoin<00:03:51.620> and<00:03:51.859> athyrium<00:03:52.310> and<00:03:52.579> any<00:03:52.790> kind<00:03:53.060> of 00:03:53.250 --> 00:03:53.260 align:start position:0% Bitcoin and athyrium and any kind of 00:03:53.260 --> 00:03:55.809 align:start position:0% Bitcoin and athyrium and any kind of distributed<00:03:54.260> period<00:03:54.590> most<00:03:55.160> distributed 00:03:55.809 --> 00:03:55.819 align:start position:0% distributed period most distributed 00:03:55.819 --> 00:03:58.180 align:start position:0% distributed period most distributed peer-to-peer<00:03:56.030> applications<00:03:57.190> their 00:03:58.180 --> 00:03:58.190 align:start position:0% peer-to-peer applications their 00:03:58.190 --> 00:04:00.849 align:start position:0% peer-to-peer applications their broadcast<00:03:58.819> based<00:03:59.139> so<00:04:00.139> they're<00:04:00.620> they're 00:04:00.849 --> 00:04:00.859 align:start position:0% broadcast based so they're they're 00:04:00.859 --> 00:04:02.640 align:start position:0% broadcast based so they're they're either<00:04:00.980> broadcast<00:04:01.579> based<00:04:01.790> or<00:04:02.030> they're<00:04:02.209> very 00:04:02.640 --> 00:04:02.650 align:start position:0% either broadcast based or they're very 00:04:02.650 --> 00:04:06.400 align:start position:0% either broadcast based or they're very exclusive<00:04:03.650> and<00:04:04.190> that<00:04:04.569> they<00:04:05.569> are<00:04:05.810> broadcast 00:04:06.400 --> 00:04:06.410 align:start position:0% exclusive and that they are broadcast 00:04:06.410 --> 00:04:08.589 align:start position:0% exclusive and that they are broadcast base<00:04:06.620> but<00:04:06.919> you<00:04:07.220> have<00:04:07.430> like<00:04:07.700> a<00:04:07.730> swarm<00:04:08.060> of<00:04:08.239> peers 00:04:08.589 --> 00:04:08.599 align:start position:0% base but you have like a swarm of peers 00:04:08.599 --> 00:04:12.309 align:start position:0% base but you have like a swarm of peers and<00:04:08.870> they're<00:04:09.169> all<00:04:10.750> they're<00:04:11.750> all<00:04:11.780> concerned 00:04:12.309 --> 00:04:12.319 align:start position:0% and they're all they're all concerned 00:04:12.319 --> 00:04:15.949 align:start position:0% and they're all they're all concerned with<00:04:12.470> a<00:04:12.500> single<00:04:12.919> torrent<00:04:13.310> hash<00:04:13.459> or<00:04:13.700> something 00:04:15.949 --> 00:04:15.959 align:start position:0% with a single torrent hash or something 00:04:15.959 --> 00:04:20.069 align:start position:0% with a single torrent hash or something as<00:04:16.959> we<00:04:17.590> move<00:04:17.799> forward<00:04:18.040> like<00:04:18.940> as<00:04:19.120> we<00:04:19.420> define<00:04:19.810> the 00:04:20.069 --> 00:04:20.079 align:start position:0% as we move forward like as we define the 00:04:20.079 --> 00:04:22.590 align:start position:0% as we move forward like as we define the way<00:04:20.230> that<00:04:20.500> the<00:04:20.620> networking<00:04:21.010> of<00:04:21.600> Bitcoin 00:04:22.590 --> 00:04:22.600 align:start position:0% way that the networking of Bitcoin 00:04:22.600 --> 00:04:26.750 align:start position:0% way that the networking of Bitcoin athyrium<00:04:23.110> works<00:04:24.240> we're<00:04:25.240> going<00:04:25.480> to<00:04:25.630> begin 00:04:26.750 --> 00:04:26.760 align:start position:0% athyrium works we're going to begin 00:04:26.760 --> 00:04:29.610 align:start position:0% athyrium works we're going to begin addressing<00:04:27.760> scalability<00:04:28.630> and<00:04:28.780> I<00:04:29.260> think<00:04:29.500> that 00:04:29.610 --> 00:04:29.620 align:start position:0% addressing scalability and I think that 00:04:29.620 --> 00:04:32.060 align:start position:0% addressing scalability and I think that that's<00:04:29.710> going<00:04:29.890> to<00:04:29.950> look<00:04:30.100> similar<00:04:30.550> to<00:04:30.930> switched 00:04:32.060 --> 00:04:32.070 align:start position:0% that's going to look similar to switched 00:04:32.070 --> 00:04:39.120 align:start position:0% that's going to look similar to switched switch<00:04:33.070> networks<00:04:34.890> IP<00:04:35.890> of<00:04:36.430> course<00:04:37.770> runs<00:04:38.770> on<00:04:38.950> top 00:04:39.120 --> 00:04:39.130 align:start position:0% switch networks IP of course runs on top 00:04:39.130 --> 00:04:42.810 align:start position:0% switch networks IP of course runs on top of<00:04:39.220> Ethernet<00:04:39.730> so<00:04:40.300> this<00:04:41.200> is<00:04:41.410> a<00:04:42.010> kind<00:04:42.430> of<00:04:42.580> layered 00:04:42.810 --> 00:04:42.820 align:start position:0% of Ethernet so this is a kind of layered 00:04:42.820 --> 00:04:46.320 align:start position:0% of Ethernet so this is a kind of layered we<00:04:43.120> have<00:04:43.300> physical<00:04:44.110> and<00:04:44.350> then<00:04:45.330> adjustability 00:04:46.320 --> 00:04:46.330 align:start position:0% we have physical and then adjustability 00:04:46.330 --> 00:04:49.830 align:start position:0% we have physical and then adjustability and<00:04:46.720> then<00:04:47.350> application<00:04:48.190> and<00:04:48.540> it's<00:04:49.540> kind<00:04:49.720> of<00:04:49.750> a 00:04:49.830 --> 00:04:49.840 align:start position:0% and then application and it's kind of a 00:04:49.840 --> 00:04:56.780 align:start position:0% and then application and it's kind of a generalized<00:04:50.350> stack<00:04:51.160> layers<00:04:52.440> and<00:04:55.200> etherium<00:04:56.200> is 00:04:56.780 --> 00:04:56.790 align:start position:0% generalized stack layers and etherium is 00:04:56.790 --> 00:04:59.550 align:start position:0% generalized stack layers and etherium is built<00:04:57.790> on<00:04:57.910> a<00:04:57.970> network<00:04:58.210> stack<00:04:58.570> that<00:04:58.960> is<00:04:59.230> very 00:04:59.550 --> 00:04:59.560 align:start position:0% built on a network stack that is very 00:04:59.560 --> 00:05:11.520 align:start position:0% built on a network stack that is very similar<00:04:59.800> to<00:04:59.950> this<00:05:03.540> so<00:05:05.190> I<00:05:10.290> tell<00:05:11.290> you<00:05:11.380> a<00:05:11.410> little 00:05:11.520 --> 00:05:11.530 align:start position:0% similar to this so I tell you a little 00:05:11.530 --> 00:05:14.880 align:start position:0% similar to this so I tell you a little bit<00:05:11.620> about<00:05:11.860> myself<00:05:12.210> real<00:05:13.210> quick<00:05:13.710> I've<00:05:14.710> always 00:05:14.880 --> 00:05:14.890 align:start position:0% bit about myself real quick I've always 00:05:14.890 --> 00:05:19.770 align:start position:0% bit about myself real quick I've always been<00:05:15.250> into<00:05:15.760> networking<00:05:16.330> security<00:05:18.600> picked<00:05:19.600> up 00:05:19.770 --> 00:05:19.780 align:start position:0% been into networking security picked up 00:05:19.780 --> 00:05:22.460 align:start position:0% been into networking security picked up programming<00:05:20.500> just<00:05:21.310> after<00:05:21.460> high<00:05:21.729> school 00:05:22.460 --> 00:05:22.470 align:start position:0% programming just after high school 00:05:22.470 --> 00:05:26.090 align:start position:0% programming just after high school working<00:05:23.470> at<00:05:23.770> a<00:05:24.120> telecommunications<00:05:25.120> company 00:05:26.090 --> 00:05:26.100 align:start position:0% working at a telecommunications company 00:05:26.100 --> 00:05:35.219 align:start position:0% working at a telecommunications company and<00:05:32.220> became<00:05:33.220> very<00:05:33.880> interested<00:05:34.180> in<00:05:34.840> the<00:05:35.140> way 00:05:35.219 --> 00:05:35.229 align:start position:0% and became very interested in the way 00:05:35.229 --> 00:05:41.850 align:start position:0% and became very interested in the way that<00:05:35.500> networks<00:05:36.010> work<00:05:37.800> so<00:05:39.419> today<00:05:40.419> if<00:05:40.990> you<00:05:41.740> were 00:05:41.850 --> 00:05:41.860 align:start position:0% that networks work so today if you were 00:05:41.860 --> 00:05:43.740 align:start position:0% that networks work so today if you were to<00:05:42.100> open<00:05:42.310> your<00:05:42.550> browser<00:05:42.760> if<00:05:43.150> you<00:05:43.450> were<00:05:43.510> to<00:05:43.630> use 00:05:43.740 --> 00:05:43.750 align:start position:0% to open your browser if you were to use 00:05:43.750 --> 00:05:45.840 align:start position:0% to open your browser if you were to use her<00:05:43.870> cell<00:05:44.050> phone<00:05:44.320> if<00:05:44.620> you<00:05:44.919> were<00:05:45.040> to<00:05:45.250> run<00:05:45.550> any 00:05:45.840 --> 00:05:45.850 align:start position:0% her cell phone if you were to run any 00:05:45.850 --> 00:05:48.480 align:start position:0% her cell phone if you were to run any kind<00:05:46.270> of<00:05:46.360> application<00:05:46.830> it's<00:05:47.830> probably<00:05:48.070> going 00:05:48.480 --> 00:05:48.490 align:start position:0% kind of application it's probably going 00:05:48.490 --> 00:05:53.340 align:start position:0% kind of application it's probably going to<00:05:48.610> connect<00:05:49.030> with<00:05:49.200> TLS<00:05:51.120> and<00:05:52.120> this<00:05:52.900> was<00:05:53.080> a<00:05:53.110> case 00:05:53.340 --> 00:05:53.350 align:start position:0% to connect with TLS and this was a case 00:05:53.350 --> 00:05:59.040 align:start position:0% to connect with TLS and this was a case in<00:05:54.300> 2000<00:05:55.300> with<00:05:55.810> ssl<00:05:57.450> when<00:05:58.450> i<00:05:58.479> first<00:05:58.720> started 00:05:59.040 --> 00:05:59.050 align:start position:0% in 2000 with ssl when i first started 00:05:59.050 --> 00:06:03.480 align:start position:0% in 2000 with ssl when i first started getting<00:05:59.320> into<00:05:59.620> networking<00:06:00.100> and<00:06:00.870> and<00:06:02.490> software 00:06:03.480 --> 00:06:03.490 align:start position:0% getting into networking and and software 00:06:03.490 --> 00:06:12.030 align:start position:0% getting into networking and and software applications<00:06:04.860> so<00:06:07.169> TLS<00:06:08.169> was<00:06:10.680> previously<00:06:11.680> was 00:06:12.030 --> 00:06:12.040 align:start position:0% applications so TLS was previously was 00:06:12.040 --> 00:06:17.159 align:start position:0% applications so TLS was previously was SSL<00:06:12.580> and<00:06:13.510> its<00:06:14.200> name<00:06:14.530> came<00:06:15.070> from<00:06:16.169> Microsoft 00:06:17.159 --> 00:06:17.169 align:start position:0% SSL and its name came from Microsoft 00:06:17.169 --> 00:06:20.120 align:start position:0% SSL and its name came from Microsoft agreeing<00:06:17.590> to<00:06:17.770> use<00:06:17.950> the<00:06:18.250> Netscape<00:06:18.760> technology 00:06:20.120 --> 00:06:20.130 align:start position:0% agreeing to use the Netscape technology 00:06:20.130 --> 00:06:22.560 align:start position:0% agreeing to use the Netscape technology which<00:06:21.130> is<00:06:21.310> great<00:06:21.580> because<00:06:22.090> that's<00:06:22.450> a 00:06:22.560 --> 00:06:22.570 align:start position:0% which is great because that's a 00:06:22.570 --> 00:06:24.140 align:start position:0% which is great because that's a demonstration<00:06:23.200> of 00:06:24.140 --> 00:06:24.150 align:start position:0% demonstration of 00:06:24.150 --> 00:06:27.260 align:start position:0% demonstration of two<00:06:25.110> really<00:06:25.500> amazing<00:06:26.040> technology<00:06:26.820> companies 00:06:27.260 --> 00:06:27.270 align:start position:0% two really amazing technology companies 00:06:27.270 --> 00:06:29.360 align:start position:0% two really amazing technology companies coming<00:06:27.690> together<00:06:27.930> to<00:06:28.410> standardize<00:06:29.070> on 00:06:29.360 --> 00:06:29.370 align:start position:0% coming together to standardize on 00:06:29.370 --> 00:06:34.460 align:start position:0% coming together to standardize on encryption<00:06:31.250> so<00:06:32.250> last<00:06:32.850> week<00:06:33.030> I<00:06:33.480> talked<00:06:34.020> to<00:06:34.080> one 00:06:34.460 --> 00:06:34.470 align:start position:0% encryption so last week I talked to one 00:06:34.470 --> 00:06:38.530 align:start position:0% encryption so last week I talked to one of<00:06:34.590> the<00:06:36.350> one<00:06:37.350> of<00:06:37.440> the<00:06:37.530> individuals<00:06:37.770> that 00:06:38.530 --> 00:06:38.540 align:start position:0% of the one of the individuals that 00:06:38.540 --> 00:06:43.790 align:start position:0% of the one of the individuals that worked<00:06:39.540> on<00:06:39.750> TLS<00:06:40.490> and<00:06:42.080> started<00:06:43.080> to<00:06:43.230> explain<00:06:43.530> how 00:06:43.790 --> 00:06:43.800 align:start position:0% worked on TLS and started to explain how 00:06:43.800 --> 00:06:46.430 align:start position:0% worked on TLS and started to explain how I<00:06:43.830> felt<00:06:44.190> about<00:06:44.280> the<00:06:44.550> protocol<00:06:44.940> and<00:06:45.660> he<00:06:46.230> said 00:06:46.430 --> 00:06:46.440 align:start position:0% I felt about the protocol and he said 00:06:46.440 --> 00:06:50.750 align:start position:0% I felt about the protocol and he said yep<00:06:47.060> completely<00:06:48.060> agree<00:06:48.300> so<00:06:49.050> when<00:06:49.590> SSL<00:06:50.520> and<00:06:50.550> TLS 00:06:50.750 --> 00:06:50.760 align:start position:0% yep completely agree so when SSL and TLS 00:06:50.760 --> 00:06:54.880 align:start position:0% yep completely agree so when SSL and TLS was<00:06:51.270> created<00:06:52.520> we<00:06:53.520> did<00:06:53.820> not<00:06:53.940> have<00:06:54.150> some<00:06:54.570> of<00:06:54.690> the 00:06:54.880 --> 00:06:54.890 align:start position:0% was created we did not have some of the 00:06:54.890 --> 00:06:59.390 align:start position:0% was created we did not have some of the strong<00:06:57.740> assertions<00:06:58.740> about<00:06:58.890> cryptography 00:06:59.390 --> 00:06:59.400 align:start position:0% strong assertions about cryptography 00:06:59.400 --> 00:07:03.050 align:start position:0% strong assertions about cryptography that<00:06:59.790> we<00:06:59.910> have<00:07:00.150> today<00:07:00.770> and<00:07:01.770> we<00:07:02.310> did<00:07:02.520> we<00:07:02.820> didn't 00:07:03.050 --> 00:07:03.060 align:start position:0% that we have today and we did we didn't 00:07:03.060 --> 00:07:07.250 align:start position:0% that we have today and we did we didn't have<00:07:03.150> the<00:07:03.270> same<00:07:03.980> computational<00:07:04.980> power<00:07:06.260> then 00:07:07.250 --> 00:07:07.260 align:start position:0% have the same computational power then 00:07:07.260 --> 00:07:09.500 align:start position:0% have the same computational power then that<00:07:07.530> we<00:07:07.590> had<00:07:07.740> today<00:07:07.920> as<00:07:08.130> well<00:07:08.340> so<00:07:09.000> there's 00:07:09.500 --> 00:07:09.510 align:start position:0% that we had today as well so there's 00:07:09.510 --> 00:07:11.660 align:start position:0% that we had today as well so there's general<00:07:09.900> agreement<00:07:10.020> that<00:07:10.530> what<00:07:10.980> we<00:07:11.130> have<00:07:11.400> now 00:07:11.660 --> 00:07:11.670 align:start position:0% general agreement that what we have now 00:07:11.670 --> 00:07:19.220 align:start position:0% general agreement that what we have now can<00:07:12.150> be<00:07:12.540> improved<00:07:17.510> getting<00:07:18.510> into<00:07:18.750> atheneum 00:07:19.220 --> 00:07:19.230 align:start position:0% can be improved getting into atheneum 00:07:19.230 --> 00:07:25.570 align:start position:0% can be improved getting into atheneum development<00:07:22.010> started<00:07:23.010> chatting<00:07:23.550> with<00:07:24.120> Gavin 00:07:25.570 --> 00:07:25.580 align:start position:0% development started chatting with Gavin 00:07:25.580 --> 00:07:28.880 align:start position:0% development started chatting with Gavin early<00:07:26.580> last<00:07:26.790> year<00:07:27.150> and<00:07:27.590> started<00:07:28.590> working<00:07:28.680> on 00:07:28.880 --> 00:07:28.890 align:start position:0% early last year and started working on 00:07:28.890 --> 00:07:33.080 align:start position:0% early last year and started working on the<00:07:29.010> c++<00:07:29.520> client<00:07:29.910> and<00:07:31.580> just<00:07:32.580> prior<00:07:32.790> to<00:07:32.850> that 00:07:33.080 --> 00:07:33.090 align:start position:0% the c++ client and just prior to that 00:07:33.090 --> 00:07:35.230 align:start position:0% the c++ client and just prior to that metallic<00:07:33.540> add<00:07:33.690> released<00:07:34.080> the<00:07:34.260> white<00:07:34.530> paper 00:07:35.230 --> 00:07:35.240 align:start position:0% metallic add released the white paper 00:07:35.240 --> 00:07:40.670 align:start position:0% metallic add released the white paper and<00:07:38.330> talking<00:07:39.330> to<00:07:39.420> Gavin<00:07:39.750> it<00:07:39.960> seemed<00:07:40.170> like<00:07:40.380> we 00:07:40.670 --> 00:07:40.680 align:start position:0% and talking to Gavin it seemed like we 00:07:40.680 --> 00:07:45.440 align:start position:0% and talking to Gavin it seemed like we all<00:07:41.070> agreed<00:07:41.430> that<00:07:44.150> etherium<00:07:45.150> could<00:07:45.300> be<00:07:45.420> a 00:07:45.440 --> 00:07:45.450 align:start position:0% all agreed that etherium could be a 00:07:45.450 --> 00:07:47.600 align:start position:0% all agreed that etherium could be a great<00:07:45.690> opportunity<00:07:45.960> to<00:07:46.350> improve<00:07:47.010> networking 00:07:47.600 --> 00:07:47.610 align:start position:0% great opportunity to improve networking 00:07:47.610 --> 00:07:51.500 align:start position:0% great opportunity to improve networking to<00:07:48.060> improve<00:07:49.640> the<00:07:50.640> general<00:07:51.000> state<00:07:51.210> of<00:07:51.270> things 00:07:51.500 --> 00:07:51.510 align:start position:0% to improve the general state of things 00:07:51.510 --> 00:07:55.850 align:start position:0% to improve the general state of things with<00:07:51.780> regard<00:07:52.140> to<00:07:52.230> encryption<00:07:53.810> so<00:07:54.810> if<00:07:55.650> we're 00:07:55.850 --> 00:07:55.860 align:start position:0% with regard to encryption so if we're 00:07:55.860 --> 00:07:59.060 align:start position:0% with regard to encryption so if we're going<00:07:56.100> to<00:07:56.750> build<00:07:57.750> out<00:07:57.960> a<00:07:57.990> new<00:07:58.380> network<00:07:58.680> for 00:07:59.060 --> 00:07:59.070 align:start position:0% going to build out a new network for 00:07:59.070 --> 00:08:03.410 align:start position:0% going to build out a new network for applications<00:08:00.590> for<00:08:01.590> smart<00:08:01.890> contracts<00:08:02.420> let's 00:08:03.410 --> 00:08:03.420 align:start position:0% applications for smart contracts let's 00:08:03.420 --> 00:08:06.640 align:start position:0% applications for smart contracts let's see<00:08:03.570> if<00:08:03.660> we<00:08:03.780> can<00:08:03.930> also<00:08:04.110> improve<00:08:04.500> the<00:08:04.710> network 00:08:06.640 --> 00:08:06.650 align:start position:0% see if we can also improve the network 00:08:06.650 --> 00:08:09.710 align:start position:0% see if we can also improve the network there's<00:08:07.650> an<00:08:07.890> interesting<00:08:08.460> talk<00:08:08.670> by<00:08:08.970> Daniel 00:08:09.710 --> 00:08:09.720 align:start position:0% there's an interesting talk by Daniel 00:08:09.720 --> 00:08:13.970 align:start position:0% there's an interesting talk by Daniel Jay<00:08:09.930> Bernstein<00:08:10.580> where<00:08:11.580> he<00:08:12.890> presents<00:08:13.890> himself 00:08:13.970 --> 00:08:13.980 align:start position:0% Jay Bernstein where he presents himself 00:08:13.980 --> 00:08:17.840 align:start position:0% Jay Bernstein where he presents himself as<00:08:14.400> an<00:08:14.640> employee<00:08:15.000> of<00:08:15.120> Verizon<00:08:15.690> and<00:08:16.650> it's<00:08:17.580> great 00:08:17.840 --> 00:08:17.850 align:start position:0% as an employee of Verizon and it's great 00:08:17.850 --> 00:08:20.300 align:start position:0% as an employee of Verizon and it's great if<00:08:18.450> you<00:08:18.600> can<00:08:18.780> find<00:08:18.930> that<00:08:19.080> it's<00:08:19.440> it's<00:08:19.800> it's<00:08:20.160> a 00:08:20.300 --> 00:08:20.310 align:start position:0% if you can find that it's it's it's a 00:08:20.310 --> 00:08:22.850 align:start position:0% if you can find that it's it's it's a it's<00:08:20.550> good<00:08:21.060> to<00:08:21.210> watch<00:08:21.390> especially<00:08:21.690> if<00:08:22.260> you<00:08:22.560> are 00:08:22.850 --> 00:08:22.860 align:start position:0% it's good to watch especially if you are 00:08:22.860 --> 00:08:30.050 align:start position:0% it's good to watch especially if you are in<00:08:23.570> if<00:08:24.570> you're<00:08:25.170> in<00:08:25.410> any<00:08:25.800> kind<00:08:26.190> of<00:08:26.930> if<00:08:28.610> if<00:08:29.610> you 00:08:30.050 --> 00:08:30.060 align:start position:0% in if you're in any kind of if if you 00:08:30.060 --> 00:08:32.870 align:start position:0% in if you're in any kind of if if you work<00:08:30.960> on<00:08:31.170> a<00:08:31.200> system<00:08:31.500> that<00:08:32.040> is<00:08:32.340> built<00:08:32.640> to 00:08:32.870 --> 00:08:32.880 align:start position:0% work on a system that is built to 00:08:32.880 --> 00:08:35.330 align:start position:0% work on a system that is built to exchange<00:08:33.450> information<00:08:33.660> and<00:08:34.200> you<00:08:34.620> are<00:08:34.860> the<00:08:35.190> man 00:08:35.330 --> 00:08:35.340 align:start position:0% exchange information and you are the man 00:08:35.340 --> 00:08:35.680 align:start position:0% exchange information and you are the man in<00:08:35.520> the 00:08:35.680 --> 00:08:35.690 align:start position:0% in the 00:08:35.690 --> 00:08:38.200 align:start position:0% in the so<00:08:36.590> if<00:08:36.950> you're<00:08:37.220> a<00:08:37.280> telecommunications 00:08:38.200 --> 00:08:38.210 align:start position:0% so if you're a telecommunications 00:08:38.210 --> 00:08:41.070 align:start position:0% so if you're a telecommunications provider<00:08:38.570> if<00:08:38.870> you're<00:08:39.050> a<00:08:39.080> bank<00:08:39.380> if<00:08:39.710> you're 00:08:41.070 --> 00:08:41.080 align:start position:0% provider if you're a bank if you're 00:08:41.080 --> 00:08:44.770 align:start position:0% provider if you're a bank if you're operate<00:08:42.080> point-of-sale<00:08:43.039> systems<00:08:43.780> anywhere 00:08:44.770 --> 00:08:44.780 align:start position:0% operate point-of-sale systems anywhere 00:08:44.780 --> 00:08:47.760 align:start position:0% operate point-of-sale systems anywhere where<00:08:45.050> you<00:08:45.080> have<00:08:45.320> a<00:08:45.560> massive<00:08:46.010> amount<00:08:46.850> of<00:08:47.000> data 00:08:47.760 --> 00:08:47.770 align:start position:0% where you have a massive amount of data 00:08:47.770 --> 00:08:52.240 align:start position:0% where you have a massive amount of data going<00:08:48.770> through<00:08:48.980> your<00:08:49.100> system<00:08:50.890> it's<00:08:51.890> good<00:08:52.130> to 00:08:52.240 --> 00:08:52.250 align:start position:0% going through your system it's good to 00:08:52.250 --> 00:08:55.410 align:start position:0% going through your system it's good to actually<00:08:52.400> step<00:08:52.850> back<00:08:53.060> and<00:08:53.330> realize<00:08:53.840> this<00:08:54.370> and 00:08:55.410 --> 00:08:55.420 align:start position:0% actually step back and realize this and 00:08:55.420 --> 00:08:59.620 align:start position:0% actually step back and realize this and realize<00:08:56.420> that<00:08:56.750> if<00:08:56.960> there's<00:08:57.230> a<00:08:57.320> breach<00:08:58.630> you 00:08:59.620 --> 00:08:59.630 align:start position:0% realize that if there's a breach you 00:08:59.630 --> 00:09:02.890 align:start position:0% realize that if there's a breach you you're<00:09:00.320> so<00:09:01.130> it's<00:09:01.430> you<00:09:02.030> get<00:09:02.180> a<00:09:02.210> lot<00:09:02.390> of<00:09:02.420> value 00:09:02.890 --> 00:09:02.900 align:start position:0% you're so it's you get a lot of value 00:09:02.900 --> 00:09:05.860 align:start position:0% you're so it's you get a lot of value out<00:09:03.140> of<00:09:03.380> being<00:09:03.680> the<00:09:03.800> man<00:09:03.980> in<00:09:04.130> the<00:09:04.190> middle<00:09:04.870> but 00:09:05.860 --> 00:09:05.870 align:start position:0% out of being the man in the middle but 00:09:05.870 --> 00:09:08.980 align:start position:0% out of being the man in the middle but if<00:09:06.080> there's<00:09:06.590> a<00:09:06.680> breach<00:09:06.950> now<00:09:07.790> maybe<00:09:08.600> you're 00:09:08.980 --> 00:09:08.990 align:start position:0% if there's a breach now maybe you're 00:09:08.990 --> 00:09:16.240 align:start position:0% if there's a breach now maybe you're liable<00:09:10.750> but<00:09:11.750> not<00:09:11.930> only<00:09:12.110> that<00:09:13.030> maybe<00:09:14.620> as<00:09:15.620> we 00:09:16.240 --> 00:09:16.250 align:start position:0% liable but not only that maybe as we 00:09:16.250 --> 00:09:17.380 align:start position:0% liable but not only that maybe as we start<00:09:16.460> building<00:09:16.790> decentralized 00:09:17.380 --> 00:09:17.390 align:start position:0% start building decentralized 00:09:17.390 --> 00:09:20.920 align:start position:0% start building decentralized applications<00:09:19.030> you<00:09:20.030> may<00:09:20.180> be<00:09:20.240> able<00:09:20.360> to<00:09:20.510> offload 00:09:20.920 --> 00:09:20.930 align:start position:0% applications you may be able to offload 00:09:20.930 --> 00:09:24.610 align:start position:0% applications you may be able to offload that<00:09:21.110> to<00:09:21.650> the<00:09:21.890> network<00:09:22.420> and<00:09:23.420> both<00:09:24.200> be<00:09:24.410> able<00:09:24.560> to 00:09:24.610 --> 00:09:24.620 align:start position:0% that to the network and both be able to 00:09:24.620 --> 00:09:27.070 align:start position:0% that to the network and both be able to provide<00:09:24.860> value<00:09:25.340> and<00:09:25.610> not<00:09:26.060> have<00:09:26.360> the<00:09:26.570> liability 00:09:27.070 --> 00:09:27.080 align:start position:0% provide value and not have the liability 00:09:27.080 --> 00:09:30.430 align:start position:0% provide value and not have the liability so<00:09:27.550> to<00:09:28.550> provide<00:09:28.850> privacy<00:09:29.420> in<00:09:29.660> in<00:09:30.050> in<00:09:30.320> in 00:09:30.430 --> 00:09:30.440 align:start position:0% so to provide privacy in in in in 00:09:30.440 --> 00:09:40.230 align:start position:0% so to provide privacy in in in in addition<00:09:31.280> to<00:09:31.460> value<00:09:34.240> so<00:09:35.560> today<00:09:38.110> networking 00:09:40.230 --> 00:09:40.240 align:start position:0% addition to value so today networking 00:09:40.240 --> 00:09:44.950 align:start position:0% addition to value so today networking principally<00:09:41.240> is<00:09:41.980> based<00:09:42.980> on<00:09:43.510> at<00:09:44.510> a<00:09:44.720> low<00:09:44.930> level 00:09:44.950 --> 00:09:44.960 align:start position:0% principally is based on at a low level 00:09:44.960 --> 00:09:48.760 align:start position:0% principally is based on at a low level routing<00:09:45.890> information<00:09:46.130> so<00:09:47.000> IP<00:09:47.450> headers<00:09:48.050> have<00:09:48.440> a 00:09:48.760 --> 00:09:48.770 align:start position:0% routing information so IP headers have a 00:09:48.770 --> 00:09:52.330 align:start position:0% routing information so IP headers have a source<00:09:49.190> and<00:09:49.460> a<00:09:49.580> destination<00:09:50.030> address<00:09:51.190> this<00:09:52.190> is 00:09:52.330 --> 00:09:52.340 align:start position:0% source and a destination address this is 00:09:52.340 --> 00:09:57.780 align:start position:0% source and a destination address this is really<00:09:52.490> similar<00:09:52.760> to<00:09:52.940> Bitcoin<00:09:53.890> so<00:09:54.890> bitcoin 00:09:57.780 --> 00:09:57.790 align:start position:0% 00:09:57.790 --> 00:10:03.850 align:start position:0% bitcoin<00:09:58.790> has<00:09:59.360> a<00:10:00.760> signer<00:10:01.760> and<00:10:02.060> then<00:10:02.960> it<00:10:03.080> has<00:10:03.260> the 00:10:03.850 --> 00:10:03.860 align:start position:0% bitcoin has a signer and then it has the 00:10:03.860 --> 00:10:06.090 align:start position:0% bitcoin has a signer and then it has the destination<00:10:04.460> address<00:10:04.760> and<00:10:04.940> a<00:10:05.000> change<00:10:05.240> address 00:10:06.090 --> 00:10:06.100 align:start position:0% destination address and a change address 00:10:06.100 --> 00:10:09.880 align:start position:0% destination address and a change address and<00:10:07.150> this<00:10:08.150> is<00:10:08.300> very<00:10:08.420> similar<00:10:08.750> to<00:10:08.900> forwarding<00:10:09.800> a 00:10:09.880 --> 00:10:09.890 align:start position:0% and this is very similar to forwarding a 00:10:09.890 --> 00:10:12.400 align:start position:0% and this is very similar to forwarding a packet<00:10:10.250> across<00:10:10.580> the<00:10:10.700> internet<00:10:11.140> except<00:10:12.140> you 00:10:12.400 --> 00:10:12.410 align:start position:0% packet across the internet except you 00:10:12.410 --> 00:10:15.370 align:start position:0% packet across the internet except you might<00:10:12.650> split<00:10:12.950> back<00:10:13.220> at<00:10:13.400> half<00:10:13.670> and<00:10:14.230> let's<00:10:15.230> not<00:10:15.290> a 00:10:15.370 --> 00:10:15.380 align:start position:0% might split back at half and let's not a 00:10:15.380 --> 00:10:17.880 align:start position:0% might split back at half and let's not a call<00:10:15.530> it<00:10:15.650> a<00:10:15.710> packet<00:10:16.040> let's<00:10:16.220> call<00:10:16.370> it<00:10:16.460> a<00:10:16.520> payload 00:10:17.880 --> 00:10:17.890 align:start position:0% call it a packet let's call it a payload 00:10:17.890 --> 00:10:20.590 align:start position:0% call it a packet let's call it a payload and<00:10:18.890> so<00:10:19.220> with<00:10:19.370> with<00:10:19.730> with<00:10:20.060> Bitcoin<00:10:20.420> you've 00:10:20.590 --> 00:10:20.600 align:start position:0% and so with with with Bitcoin you've 00:10:20.600 --> 00:10:22.690 align:start position:0% and so with with with Bitcoin you've basically<00:10:20.870> got<00:10:21.200> all<00:10:21.589> these<00:10:21.830> payloads<00:10:22.310> being 00:10:22.690 --> 00:10:22.700 align:start position:0% basically got all these payloads being 00:10:22.700 --> 00:10:27.570 align:start position:0% basically got all these payloads being routed<00:10:23.150> through<00:10:23.660> all<00:10:23.930> of<00:10:23.960> these<00:10:24.200> accounts<00:10:25.839> and 00:10:27.570 --> 00:10:27.580 align:start position:0% routed through all of these accounts and 00:10:27.580 --> 00:10:30.040 align:start position:0% routed through all of these accounts and this<00:10:28.580> is<00:10:28.700> very<00:10:28.790> similar<00:10:29.089> to<00:10:29.270> email<00:10:29.600> except 00:10:30.040 --> 00:10:30.050 align:start position:0% this is very similar to email except 00:10:30.050 --> 00:10:32.110 align:start position:0% this is very similar to email except it's<00:10:30.290> secure<00:10:30.770> and<00:10:30.950> there's<00:10:31.760> some<00:10:31.970> value 00:10:32.110 --> 00:10:32.120 align:start position:0% it's secure and there's some value 00:10:32.120 --> 00:10:34.390 align:start position:0% it's secure and there's some value attached<00:10:32.780> to<00:10:33.170> that<00:10:33.710> trip<00:10:34.010> to<00:10:34.250> that 00:10:34.390 --> 00:10:34.400 align:start position:0% attached to that trip to that 00:10:34.400 --> 00:10:38.829 align:start position:0% attached to that trip to that transaction<00:10:36.670> athyrium<00:10:37.670> by<00:10:38.450> the<00:10:38.510> way<00:10:38.720> we 00:10:38.829 --> 00:10:38.839 align:start position:0% transaction athyrium by the way we 00:10:38.839 --> 00:10:40.800 align:start position:0% transaction athyrium by the way we actually<00:10:39.320> do<00:10:39.440> this<00:10:39.560> a<00:10:39.589> little<00:10:39.710> differently 00:10:40.800 --> 00:10:40.810 align:start position:0% actually do this a little differently 00:10:40.810 --> 00:10:44.020 align:start position:0% actually do this a little differently the<00:10:41.810> the<00:10:42.740> way<00:10:42.860> that<00:10:43.040> the<00:10:43.220> signature<00:10:43.670> system 00:10:44.020 --> 00:10:44.030 align:start position:0% the the way that the signature system 00:10:44.030 --> 00:10:46.840 align:start position:0% the the way that the signature system works<00:10:44.410> you<00:10:45.410> can<00:10:45.530> look<00:10:45.770> at<00:10:45.920> it<00:10:45.950> similar<00:10:46.580> to 00:10:46.840 --> 00:10:46.850 align:start position:0% works you can look at it similar to 00:10:46.850 --> 00:10:47.929 align:start position:0% works you can look at it similar to Bitcoin<00:10:47.210> was<00:10:47.330> actually<00:10:47.690> quite 00:10:47.929 --> 00:10:47.939 align:start position:0% Bitcoin was actually quite 00:10:47.939 --> 00:10:53.719 align:start position:0% Bitcoin was actually quite different<00:10:49.129> you<00:10:50.689> sign<00:10:51.689> the<00:10:51.899> transaction<00:10:52.729> and 00:10:53.719 --> 00:10:53.729 align:start position:0% different you sign the transaction and 00:10:53.729 --> 00:10:56.559 align:start position:0% different you sign the transaction and the<00:10:53.849> person<00:10:54.149> that<00:10:54.239> wants<00:10:54.419> to<00:10:54.509> verify<00:10:54.929> it<00:10:55.459> they 00:10:56.559 --> 00:10:56.569 align:start position:0% the person that wants to verify it they 00:10:56.569 --> 00:10:58.849 align:start position:0% the person that wants to verify it they they<00:10:57.569> recover<00:10:57.929> your<00:10:58.079> public<00:10:58.439> key<00:10:58.470> out<00:10:58.709> of<00:10:58.739> the 00:10:58.849 --> 00:10:58.859 align:start position:0% they recover your public key out of the 00:10:58.859 --> 00:11:00.409 align:start position:0% they recover your public key out of the transaction<00:10:59.459> and<00:10:59.639> then<00:10:59.729> verify<00:11:00.179> that<00:11:00.389> that 00:11:00.409 --> 00:11:00.419 align:start position:0% transaction and then verify that that 00:11:00.419 --> 00:11:02.389 align:start position:0% transaction and then verify that that that<00:11:00.899> that's<00:11:01.109> accurate<00:11:01.379> and<00:11:01.769> then<00:11:02.099> take<00:11:02.279> the 00:11:02.389 --> 00:11:02.399 align:start position:0% that that's accurate and then take the 00:11:02.399 --> 00:11:06.499 align:start position:0% that that's accurate and then take the information<00:11:02.519> that's<00:11:03.119> been<00:11:03.299> signed<00:11:03.829> and<00:11:05.509> then 00:11:06.499 --> 00:11:06.509 align:start position:0% information that's been signed and then 00:11:06.509 --> 00:11:12.829 align:start position:0% information that's been signed and then process<00:11:06.989> that<00:11:08.269> so<00:11:10.729> what's<00:11:11.729> significant<00:11:12.659> there 00:11:12.829 --> 00:11:12.839 align:start position:0% process that so what's significant there 00:11:12.839 --> 00:11:17.269 align:start position:0% process that so what's significant there is<00:11:13.049> that<00:11:14.209> its<00:11:15.209> application<00:11:15.869> oriented<00:11:16.279> instead 00:11:17.269 --> 00:11:17.279 align:start position:0% is that its application oriented instead 00:11:17.279 --> 00:11:23.210 align:start position:0% is that its application oriented instead of<00:11:17.809> networking<00:11:21.229> so<00:11:22.229> applications<00:11:23.009> have<00:11:23.159> a 00:11:23.210 --> 00:11:23.220 align:start position:0% of networking so applications have a 00:11:23.220 --> 00:11:25.129 align:start position:0% of networking so applications have a different<00:11:23.549> challenge<00:11:23.729> and<00:11:24.149> that<00:11:24.179> is 00:11:25.129 --> 00:11:25.139 align:start position:0% different challenge and that is 00:11:25.139 --> 00:11:30.019 align:start position:0% different challenge and that is discovery<00:11:26.839> if<00:11:27.839> you<00:11:28.589> have<00:11:28.979> a<00:11:29.009> network<00:11:29.549> and<00:11:29.879> your 00:11:30.019 --> 00:11:30.029 align:start position:0% discovery if you have a network and your 00:11:30.029 --> 00:11:34.279 align:start position:0% discovery if you have a network and your routing<00:11:30.299> information<00:11:30.689> everywhere<00:11:33.169> this<00:11:34.169> is 00:11:34.279 --> 00:11:34.289 align:start position:0% routing information everywhere this is 00:11:34.289 --> 00:11:39.049 align:start position:0% routing information everywhere this is very<00:11:34.470> useful<00:11:35.029> but<00:11:37.489> especially<00:11:38.489> if<00:11:38.789> you<00:11:38.879> can 00:11:39.049 --> 00:11:39.059 align:start position:0% very useful but especially if you can 00:11:39.059 --> 00:11:40.339 align:start position:0% very useful but especially if you can decentralize<00:11:39.659> all<00:11:39.809> of<00:11:39.899> it<00:11:39.989> right<00:11:40.139> so 00:11:40.339 --> 00:11:40.349 align:start position:0% decentralize all of it right so 00:11:40.349 --> 00:11:42.139 align:start position:0% decentralize all of it right so decentralize<00:11:41.039> all<00:11:41.189> the<00:11:41.309> things<00:11:41.519> and<00:11:41.759> that's 00:11:42.139 --> 00:11:42.149 align:start position:0% decentralize all the things and that's 00:11:42.149 --> 00:11:44.929 align:start position:0% decentralize all the things and that's useful<00:11:42.979> well<00:11:43.979> actually<00:11:44.279> it<00:11:44.519> turns<00:11:44.669> out<00:11:44.759> it's 00:11:44.929 --> 00:11:44.939 align:start position:0% useful well actually it turns out it's 00:11:44.939 --> 00:11:47.899 align:start position:0% useful well actually it turns out it's not<00:11:45.319> if<00:11:46.319> UD<00:11:46.649> centralize<00:11:47.129> all<00:11:47.159> the<00:11:47.399> things<00:11:47.639> and 00:11:47.899 --> 00:11:47.909 align:start position:0% not if UD centralize all the things and 00:11:47.909 --> 00:11:50.739 align:start position:0% not if UD centralize all the things and you<00:11:48.329> don't<00:11:48.659> know<00:11:48.809> where<00:11:49.139> all<00:11:49.289> the<00:11:49.409> things<00:11:49.619> are 00:11:50.739 --> 00:11:50.749 align:start position:0% you don't know where all the things are 00:11:50.749 --> 00:11:53.169 align:start position:0% you don't know where all the things are your<00:11:51.749> applications<00:11:52.319> can't<00:11:52.559> use<00:11:52.679> the<00:11:52.799> network 00:11:53.169 --> 00:11:53.179 align:start position:0% your applications can't use the network 00:11:53.179 --> 00:11:55.369 align:start position:0% your applications can't use the network so<00:11:54.179> what<00:11:54.539> you<00:11:54.599> have<00:11:54.659> to<00:11:54.779> do<00:11:54.989> when<00:11:55.229> you're 00:11:55.369 --> 00:11:55.379 align:start position:0% so what you have to do when you're 00:11:55.379 --> 00:11:56.989 align:start position:0% so what you have to do when you're building<00:11:55.499> your<00:11:55.709> application<00:11:56.309> is<00:11:56.519> in<00:11:56.819> your 00:11:56.989 --> 00:11:56.999 align:start position:0% building your application is in your 00:11:56.999 --> 00:11:58.909 align:start position:0% building your application is in your application<00:11:57.569> you<00:11:58.079> have<00:11:58.169> to<00:11:58.289> build<00:11:58.499> something 00:11:58.909 --> 00:11:58.919 align:start position:0% application you have to build something 00:11:58.919 --> 00:12:02.119 align:start position:0% application you have to build something that<00:12:00.049> organizes<00:12:01.049> all<00:12:01.259> of<00:12:01.619> the<00:12:01.709> things<00:12:01.889> that 00:12:02.119 --> 00:12:02.129 align:start position:0% that organizes all of the things that 00:12:02.129 --> 00:12:07.089 align:start position:0% that organizes all of the things that you've<00:12:02.339> you've<00:12:02.849> decentralized<00:12:04.699> so<00:12:05.699> this<00:12:06.599> is 00:12:07.089 --> 00:12:07.099 align:start position:0% you've you've decentralized so this is 00:12:07.099 --> 00:12:10.969 align:start position:0% you've you've decentralized so this is known<00:12:08.099> as<00:12:08.209> routing<00:12:09.209> there<00:12:09.509> dhts<00:12:10.229> there's<00:12:10.889> a 00:12:10.969 --> 00:12:10.979 align:start position:0% known as routing there dhts there's a 00:12:10.979 --> 00:12:13.849 align:start position:0% known as routing there dhts there's a lot<00:12:11.039> of<00:12:11.189> technology<00:12:12.169> they<00:12:13.169> can<00:12:13.349> do<00:12:13.439> this<00:12:13.619> and 00:12:13.849 --> 00:12:13.859 align:start position:0% lot of technology they can do this and 00:12:13.859 --> 00:12:17.599 align:start position:0% lot of technology they can do this and protocols<00:12:14.419> and<00:12:15.889> what<00:12:16.889> they<00:12:17.009> basically<00:12:17.339> do<00:12:17.579> is 00:12:17.599 --> 00:12:17.609 align:start position:0% protocols and what they basically do is 00:12:17.609 --> 00:12:21.139 align:start position:0% protocols and what they basically do is they<00:12:18.679> let<00:12:19.679> you<00:12:19.859> determine<00:12:20.099> exactly<00:12:20.759> where<00:12:21.029> the 00:12:21.139 --> 00:12:21.149 align:start position:0% they let you determine exactly where the 00:12:21.149 --> 00:12:24.289 align:start position:0% they let you determine exactly where the information<00:12:21.389> is<00:12:21.749> that<00:12:21.929> you<00:12:22.019> need<00:12:22.459> and<00:12:23.459> then 00:12:24.289 --> 00:12:24.299 align:start position:0% information is that you need and then 00:12:24.299 --> 00:12:27.799 align:start position:0% information is that you need and then get<00:12:24.539> you<00:12:24.629> that<00:12:24.779> information<00:12:25.489> and<00:12:26.599> this<00:12:27.599> is 00:12:27.799 --> 00:12:27.809 align:start position:0% get you that information and this is 00:12:27.809 --> 00:12:30.399 align:start position:0% get you that information and this is again<00:12:28.199> becoming<00:12:28.949> very<00:12:29.189> different<00:12:29.579> than 00:12:30.399 --> 00:12:30.409 align:start position:0% again becoming very different than 00:12:30.409 --> 00:12:34.129 align:start position:0% again becoming very different than networking<00:12:31.409> of<00:12:31.529> the<00:12:31.649> past<00:12:32.720> with<00:12:33.720> vitarium 00:12:34.129 --> 00:12:34.139 align:start position:0% networking of the past with vitarium 00:12:34.139 --> 00:12:38.179 align:start position:0% networking of the past with vitarium with<00:12:34.379> applications<00:12:36.589> you<00:12:37.589> will<00:12:37.619> connect<00:12:38.069> to 00:12:38.179 --> 00:12:38.189 align:start position:0% with applications you will connect to 00:12:38.189 --> 00:12:44.809 align:start position:0% with applications you will connect to your<00:12:38.279> peers<00:12:38.639> and<00:12:40.309> be<00:12:41.309> able<00:12:41.429> to<00:12:42.409> advertise<00:12:43.819> what 00:12:44.809 --> 00:12:44.819 align:start position:0% your peers and be able to advertise what 00:12:44.819 --> 00:12:46.189 align:start position:0% your peers and be able to advertise what you<00:12:44.970> need<00:12:45.179> or<00:12:45.209> what<00:12:45.449> you're<00:12:45.629> interested<00:12:45.869> in 00:12:46.189 --> 00:12:46.199 align:start position:0% you need or what you're interested in 00:12:46.199 --> 00:12:48.079 align:start position:0% you need or what you're interested in and<00:12:46.379> then<00:12:46.769> the<00:12:46.889> network<00:12:47.279> will<00:12:47.579> bring<00:12:47.789> it<00:12:47.909> to 00:12:48.079 --> 00:12:48.089 align:start position:0% and then the network will bring it to 00:12:48.089 --> 00:12:56.989 align:start position:0% and then the network will bring it to you<00:12:49.609> and<00:12:51.709> this<00:12:52.709> is<00:12:52.889> very<00:12:53.069> useful<00:12:53.209> and<00:12:55.879> we<00:12:56.879> have 00:12:56.989 --> 00:12:56.999 align:start position:0% you and this is very useful and we have 00:12:56.999 --> 00:12:59.029 align:start position:0% you and this is very useful and we have to<00:12:57.119> be<00:12:57.149> careful<00:12:57.389> though<00:12:57.679> we<00:12:58.679> have<00:12:58.799> to<00:12:58.889> build 00:12:59.029 --> 00:12:59.039 align:start position:0% to be careful though we have to build 00:12:59.039 --> 00:13:00.220 align:start position:0% to be careful though we have to build this<00:12:59.220> slowly 00:13:00.220 --> 00:13:00.230 align:start position:0% this slowly 00:13:00.230 --> 00:13:02.740 align:start position:0% this slowly and<00:13:00.560> we<00:13:00.800> have<00:13:00.920> to<00:13:01.040> do<00:13:01.160> it<00:13:01.250> right<00:13:01.430> because<00:13:02.360> while 00:13:02.740 --> 00:13:02.750 align:start position:0% and we have to do it right because while 00:13:02.750 --> 00:13:04.330 align:start position:0% and we have to do it right because while it<00:13:02.960> can<00:13:03.080> be<00:13:03.230> really<00:13:03.380> useful<00:13:03.470> and<00:13:04.010> everyone 00:13:04.330 --> 00:13:04.340 align:start position:0% it can be really useful and everyone 00:13:04.340 --> 00:13:07.360 align:start position:0% it can be really useful and everyone agrees<00:13:04.940> that<00:13:05.410> that<00:13:06.410> we<00:13:06.500> need<00:13:06.650> to<00:13:06.770> improve<00:13:07.040> here 00:13:07.360 --> 00:13:07.370 align:start position:0% agrees that that we need to improve here 00:13:07.370 --> 00:13:10.030 align:start position:0% agrees that that we need to improve here and<00:13:07.550> this<00:13:08.300> general<00:13:08.840> stack<00:13:09.080> of<00:13:09.320> networking<00:13:09.860> and 00:13:10.030 --> 00:13:10.040 align:start position:0% and this general stack of networking and 00:13:10.040 --> 00:13:11.530 align:start position:0% and this general stack of networking and applications<00:13:10.580> everything's<00:13:11.090> talking<00:13:11.450> to 00:13:11.530 --> 00:13:11.540 align:start position:0% applications everything's talking to 00:13:11.540 --> 00:13:13.900 align:start position:0% applications everything's talking to each<00:13:11.660> other<00:13:12.070> we<00:13:13.070> have<00:13:13.190> to<00:13:13.280> be<00:13:13.370> careful<00:13:13.520> that<00:13:13.730> we 00:13:13.900 --> 00:13:13.910 align:start position:0% each other we have to be careful that we 00:13:13.910 --> 00:13:18.750 align:start position:0% each other we have to be careful that we don't<00:13:13.940> mess<00:13:14.210> it<00:13:14.240> up<00:13:16.450> so<00:13:17.450> in<00:13:17.870> order<00:13:18.470> to 00:13:18.750 --> 00:13:18.760 align:start position:0% don't mess it up so in order to 00:13:18.760 --> 00:13:26.800 align:start position:0% don't mess it up so in order to facilitate<00:13:22.900> application<00:13:23.900> that<00:13:24.080> works<00:13:25.810> we 00:13:26.800 --> 00:13:26.810 align:start position:0% facilitate application that works we 00:13:26.810 --> 00:13:31.530 align:start position:0% facilitate application that works we have<00:13:27.290> a<00:13:27.770> network<00:13:28.670> protocol<00:13:29.980> with<00:13:30.980> athyrium 00:13:31.530 --> 00:13:31.540 align:start position:0% have a network protocol with athyrium 00:13:31.540 --> 00:13:36.240 align:start position:0% have a network protocol with athyrium for<00:13:32.540> athyrium<00:13:32.930> notes<00:13:33.610> which<00:13:34.610> is<00:13:34.880> encrypted 00:13:36.240 --> 00:13:36.250 align:start position:0% for athyrium notes which is encrypted 00:13:36.250 --> 00:13:39.220 align:start position:0% for athyrium notes which is encrypted throughout<00:13:37.250> the<00:13:37.430> network<00:13:37.610> and<00:13:38.200> has<00:13:39.200> a 00:13:39.220 --> 00:13:39.230 align:start position:0% throughout the network and has a 00:13:39.230 --> 00:13:45.250 align:start position:0% throughout the network and has a separate<00:13:39.740> node<00:13:40.250> discovery<00:13:40.820> system<00:13:44.020> so<00:13:45.020> quick 00:13:45.250 --> 00:13:45.260 align:start position:0% separate node discovery system so quick 00:13:45.260 --> 00:13:50.290 align:start position:0% separate node discovery system so quick clarification<00:13:45.440> node<00:13:46.310> can<00:13:47.060> be<00:13:47.210> anything<00:13:49.300> right 00:13:50.290 --> 00:13:50.300 align:start position:0% clarification node can be anything right 00:13:50.300 --> 00:13:54.310 align:start position:0% clarification node can be anything right now<00:13:50.600> we<00:13:51.320> have<00:13:51.350> a<00:13:51.500> system<00:13:51.800> for<00:13:52.840> peers<00:13:53.840> who<00:13:54.290> are 00:13:54.310 --> 00:13:54.320 align:start position:0% now we have a system for peers who are 00:13:54.320 --> 00:13:57.700 align:start position:0% now we have a system for peers who are the<00:13:54.560> notes<00:13:54.740> to<00:13:55.490> form<00:13:56.120> a<00:13:56.300> network<00:13:56.560> to<00:13:57.560> be<00:13:57.680> able 00:13:57.700 --> 00:13:57.710 align:start position:0% the notes to form a network to be able 00:13:57.710 --> 00:14:05.410 align:start position:0% the notes to form a network to be able to<00:13:57.920> broadcast<00:13:58.070> transactions<00:13:59.470> and<00:14:04.270> what<00:14:05.270> that 00:14:05.410 --> 00:14:05.420 align:start position:0% to broadcast transactions and what that 00:14:05.420 --> 00:14:10.530 align:start position:0% to broadcast transactions and what that gets<00:14:05.540> us<00:14:05.750> today<00:14:06.050> is<00:14:06.290> a<00:14:07.070> stable<00:14:07.340> network<00:14:08.620> for 00:14:10.530 --> 00:14:10.540 align:start position:0% gets us today is a stable network for 00:14:10.540 --> 00:14:12.760 align:start position:0% gets us today is a stable network for transaction<00:14:11.540> delivery<00:14:11.930> block<00:14:12.290> delivery 00:14:12.760 --> 00:14:12.770 align:start position:0% transaction delivery block delivery 00:14:12.770 --> 00:14:16.890 align:start position:0% transaction delivery block delivery downloads<00:14:13.430> etc<00:14:14.950> we've<00:14:15.950> recently<00:14:16.280> added 00:14:16.890 --> 00:14:16.900 align:start position:0% downloads etc we've recently added 00:14:16.900 --> 00:14:19.360 align:start position:0% downloads etc we've recently added framing<00:14:17.900> and<00:14:18.320> we'll<00:14:18.410> be<00:14:18.530> adding<00:14:18.680> flow<00:14:19.010> control 00:14:19.360 --> 00:14:19.370 align:start position:0% framing and we'll be adding flow control 00:14:19.370 --> 00:14:22.990 align:start position:0% framing and we'll be adding flow control soon<00:14:19.870> and<00:14:20.870> what<00:14:21.350> this<00:14:21.470> means<00:14:21.530> is<00:14:21.980> that<00:14:22.040> you<00:14:22.670> can 00:14:22.990 --> 00:14:23.000 align:start position:0% soon and what this means is that you can 00:14:23.000 --> 00:14:26.590 align:start position:0% soon and what this means is that you can create<00:14:23.210> a<00:14:23.480> sub<00:14:23.780> protocol<00:14:24.790> that<00:14:25.790> runs<00:14:26.180> on<00:14:26.450> the 00:14:26.590 --> 00:14:26.600 align:start position:0% create a sub protocol that runs on the 00:14:26.600 --> 00:14:34.240 align:start position:0% create a sub protocol that runs on the etherium<00:14:26.960> network<00:14:27.730> so<00:14:31.750> let's<00:14:32.750> get<00:14:32.960> that<00:14:33.250> so 00:14:34.240 --> 00:14:34.250 align:start position:0% etherium network so let's get that so 00:14:34.250 --> 00:14:36.970 align:start position:0% etherium network so let's get that so we're<00:14:34.910> doing<00:14:35.030> that<00:14:35.210> ourselves<00:14:35.240> and<00:14:35.900> the<00:14:36.560> sub 00:14:36.970 --> 00:14:36.980 align:start position:0% we're doing that ourselves and the sub 00:14:36.980 --> 00:14:38.640 align:start position:0% we're doing that ourselves and the sub protocols<00:14:37.400> that<00:14:37.460> we're<00:14:37.670> going<00:14:37.790> to<00:14:37.850> run<00:14:37.970> our 00:14:38.640 --> 00:14:38.650 align:start position:0% protocols that we're going to run our 00:14:38.650 --> 00:14:43.270 align:start position:0% protocols that we're going to run our there's<00:14:39.650> 'if<00:14:40.010> for<00:14:40.460> the<00:14:40.850> blockchain<00:14:42.280> whisper 00:14:43.270 --> 00:14:43.280 align:start position:0% there's 'if for the blockchain whisper 00:14:43.280 --> 00:14:49.780 align:start position:0% there's 'if for the blockchain whisper which<00:14:43.760> is<00:14:43.910> and<00:14:44.770> this<00:14:45.770> is<00:14:45.920> which<00:14:46.370> is<00:14:46.670> swarm<00:14:48.790> you 00:14:49.780 --> 00:14:49.790 align:start position:0% which is and this is which is swarm you 00:14:49.790 --> 00:14:55.990 align:start position:0% which is and this is which is swarm you can<00:14:49.970> add<00:14:50.120> your<00:14:50.270> protocol<00:14:50.690> here<00:14:50.950> and<00:14:54.580> each<00:14:55.580> one 00:14:55.990 --> 00:14:56.000 align:start position:0% can add your protocol here and each one 00:14:56.000 --> 00:14:58.810 align:start position:0% can add your protocol here and each one of<00:14:56.030> these<00:14:56.270> protocols<00:14:57.200> is<00:14:57.620> its<00:14:58.100> own<00:14:58.310> set<00:14:58.790> of 00:14:58.810 --> 00:14:58.820 align:start position:0% of these protocols is its own set of 00:14:58.820 --> 00:15:04.690 align:start position:0% of these protocols is its own set of nodes<00:15:00.820> and<00:15:02.050> what<00:15:03.050> this<00:15:03.230> means<00:15:03.440> at<00:15:04.340> the<00:15:04.520> end<00:15:04.550> of 00:15:04.690 --> 00:15:04.700 align:start position:0% nodes and what this means at the end of 00:15:04.700 --> 00:15:09.970 align:start position:0% nodes and what this means at the end of the<00:15:04.820> day<00:15:04.970> is<00:15:06.520> that<00:15:07.990> today<00:15:08.990> everything<00:15:09.860> is<00:15:09.920> a 00:15:09.970 --> 00:15:09.980 align:start position:0% the day is that today everything is a 00:15:09.980 --> 00:15:11.060 align:start position:0% the day is that today everything is a thin<00:15:10.220> client 00:15:11.060 --> 00:15:11.070 align:start position:0% thin client 00:15:11.070 --> 00:15:15.560 align:start position:0% thin client so<00:15:11.870> today<00:15:12.870> everything<00:15:13.530> is<00:15:13.680> HTML<00:15:14.210> and<00:15:15.210> if<00:15:15.450> we 00:15:15.560 --> 00:15:15.570 align:start position:0% so today everything is HTML and if we 00:15:15.570 --> 00:15:17.840 align:start position:0% so today everything is HTML and if we wanted<00:15:15.840> to<00:15:15.900> go<00:15:15.990> into<00:15:16.470> gmail<00:15:17.040> and<00:15:17.280> say<00:15:17.460> okay<00:15:17.820> i 00:15:17.840 --> 00:15:17.850 align:start position:0% wanted to go into gmail and say okay i 00:15:17.850 --> 00:15:19.520 align:start position:0% wanted to go into gmail and say okay i want<00:15:18.120> to<00:15:18.210> send<00:15:18.390> an<00:15:18.480> email<00:15:18.600> i<00:15:18.960> want<00:15:19.290> to<00:15:19.350> some 00:15:19.520 --> 00:15:19.530 align:start position:0% want to send an email i want to some 00:15:19.530 --> 00:15:23.270 align:start position:0% want to send an email i want to some Bitcoin<00:15:19.890> to<00:15:20.550> one<00:15:20.670> of<00:15:20.760> my<00:15:21.140> contacts<00:15:22.140> or<00:15:22.350> i<00:15:22.410> want 00:15:23.270 --> 00:15:23.280 align:start position:0% Bitcoin to one of my contacts or i want 00:15:23.280 --> 00:15:25.400 align:start position:0% Bitcoin to one of my contacts or i want to<00:15:23.400> sign<00:15:23.640> an<00:15:23.910> a<00:15:24.000> you<00:15:24.390> know<00:15:24.510> theriyum<00:15:24.960> contract 00:15:25.400 --> 00:15:25.410 align:start position:0% to sign an a you know theriyum contract 00:15:25.410 --> 00:15:28.040 align:start position:0% to sign an a you know theriyum contract like<00:15:25.610> executed<00:15:26.610> athyrium<00:15:26.910> contract<00:15:27.360> with<00:15:27.870> one 00:15:28.040 --> 00:15:28.050 align:start position:0% like executed athyrium contract with one 00:15:28.050 --> 00:15:29.330 align:start position:0% like executed athyrium contract with one of<00:15:28.140> my<00:15:28.200> contacts<00:15:28.680> I<00:15:28.770> can't<00:15:28.980> really<00:15:29.100> do<00:15:29.310> that 00:15:29.330 --> 00:15:29.340 align:start position:0% of my contacts I can't really do that 00:15:29.340 --> 00:15:31.760 align:start position:0% of my contacts I can't really do that like<00:15:30.180> there's<00:15:30.600> not<00:15:30.750> an<00:15:30.900> interface<00:15:31.380> in<00:15:31.650> the 00:15:31.760 --> 00:15:31.770 align:start position:0% like there's not an interface in the 00:15:31.770 --> 00:15:35.210 align:start position:0% like there's not an interface in the browser<00:15:31.920> to<00:15:32.310> say<00:15:32.870> okay<00:15:34.100> execute<00:15:35.100> this 00:15:35.210 --> 00:15:35.220 align:start position:0% browser to say okay execute this 00:15:35.220 --> 00:15:38.650 align:start position:0% browser to say okay execute this function<00:15:35.640> with<00:15:35.970> this<00:15:36.180> application<00:15:36.660> network 00:15:38.650 --> 00:15:38.660 align:start position:0% function with this application network 00:15:38.660 --> 00:15:44.810 align:start position:0% function with this application network and<00:15:40.850> a<00:15:42.740> lot<00:15:43.740> of<00:15:43.830> times<00:15:44.070> if<00:15:44.370> you<00:15:44.580> want<00:15:44.760> to 00:15:44.810 --> 00:15:44.820 align:start position:0% and a lot of times if you want to 00:15:44.820 --> 00:15:46.700 align:start position:0% and a lot of times if you want to actually<00:15:44.940> do<00:15:45.210> that<00:15:45.330> you<00:15:45.570> have<00:15:46.050> to<00:15:46.200> put<00:15:46.470> have<00:15:46.680> a 00:15:46.700 --> 00:15:46.710 align:start position:0% actually do that you have to put have a 00:15:46.710 --> 00:15:50.540 align:start position:0% actually do that you have to put have a have<00:15:47.070> a<00:15:47.100> plug-in<00:15:47.990> so<00:15:49.010> what<00:15:50.010> we're<00:15:50.160> going<00:15:50.280> to<00:15:50.460> be 00:15:50.540 --> 00:15:50.550 align:start position:0% have a plug-in so what we're going to be 00:15:50.550 --> 00:15:54.230 align:start position:0% have a plug-in so what we're going to be building<00:15:50.990> with<00:15:51.990> athyrium<00:15:52.560> and<00:15:52.880> exposing<00:15:53.880> for 00:15:54.230 --> 00:15:54.240 align:start position:0% building with athyrium and exposing for 00:15:54.240 --> 00:15:58.190 align:start position:0% building with athyrium and exposing for your<00:15:54.540> applications<00:15:55.760> is<00:15:56.780> the<00:15:57.780> ability<00:15:57.960> for 00:15:58.190 --> 00:15:58.200 align:start position:0% your applications is the ability for 00:15:58.200 --> 00:16:00.080 align:start position:0% your applications is the ability for your<00:15:58.500> applications<00:15:59.100> do<00:15:59.340> you<00:15:59.430> have<00:15:59.700> networks 00:16:00.080 --> 00:16:00.090 align:start position:0% your applications do you have networks 00:16:00.090 --> 00:16:03.310 align:start position:0% your applications do you have networks and<00:16:00.590> have<00:16:01.590> networks<00:16:01.980> of<00:16:02.310> networks<00:16:02.430> which 00:16:03.310 --> 00:16:03.320 align:start position:0% and have networks of networks which 00:16:03.320 --> 00:16:06.530 align:start position:0% and have networks of networks which Bitcoin<00:16:04.320> the<00:16:04.890> etherium<00:16:05.280> blockchain<00:16:05.550> these 00:16:06.530 --> 00:16:06.540 align:start position:0% Bitcoin the etherium blockchain these 00:16:06.540 --> 00:16:10.130 align:start position:0% Bitcoin the etherium blockchain these are<00:16:06.720> these<00:16:07.140> are<00:16:07.200> networks<00:16:08.570> to<00:16:09.570> interface<00:16:10.110> with 00:16:10.130 --> 00:16:10.140 align:start position:0% are these are networks to interface with 00:16:10.140 --> 00:16:12.560 align:start position:0% are these are networks to interface with each<00:16:10.350> other<00:16:10.710> to<00:16:11.220> pass<00:16:11.400> messages<00:16:11.640> to<00:16:12.480> each 00:16:12.560 --> 00:16:12.570 align:start position:0% each other to pass messages to each 00:16:12.570 --> 00:16:17.890 align:start position:0% each other to pass messages to each other<00:16:12.950> and<00:16:13.950> to<00:16:14.610> communicate<00:16:15.200> in<00:16:16.200> a<00:16:16.380> way<00:16:16.460> that 00:16:17.890 --> 00:16:17.900 align:start position:0% other and to communicate in a way that 00:16:17.900 --> 00:16:23.150 align:start position:0% other and to communicate in a way that this<00:16:18.900> not<00:16:19.320> previously<00:16:19.590> available<00:16:20.540> so<00:16:22.160> and 00:16:23.150 --> 00:16:23.160 align:start position:0% this not previously available so and 00:16:23.160 --> 00:16:29.929 align:start position:0% this not previously available so and that's<00:16:23.490> it 00:16:29.929 --> 00:16:29.939 align:start position:0% 00:16:29.939 --> 00:16:31.999 align:start position:0% you