WEBVTT Kind: captions Language: en 00:00:00.540 --> 00:00:18.100 align:start position:0% [Music] 00:00:18.100 --> 00:00:18.110 align:start position:0% 00:00:18.110 --> 00:00:20.780 align:start position:0% hi<00:00:19.110> everyone<00:00:19.350> I'm<00:00:19.740> David<00:00:20.100> and<00:00:20.369> I<00:00:20.520> work<00:00:20.670> for 00:00:20.780 --> 00:00:20.790 align:start position:0% hi everyone I'm David and I work for 00:00:20.790 --> 00:00:22.160 align:start position:0% hi everyone I'm David and I work for protocol<00:00:21.030> apps<00:00:21.360> I'm<00:00:21.720> a<00:00:21.780> software<00:00:22.080> engineer 00:00:22.160 --> 00:00:22.170 align:start position:0% protocol apps I'm a software engineer 00:00:22.170 --> 00:00:25.250 align:start position:0% protocol apps I'm a software engineer responsible<00:00:23.070> and<00:00:23.520> focused<00:00:23.939> on<00:00:24.119> the<00:00:24.390> JSI<00:00:24.930> PFS 00:00:25.250 --> 00:00:25.260 align:start position:0% responsible and focused on the JSI PFS 00:00:25.260 --> 00:00:26.830 align:start position:0% responsible and focused on the JSI PFS and<00:00:25.560> the<00:00:25.650> way<00:00:25.770> peer-to-peer<00:00:26.070> projects 00:00:26.830 --> 00:00:26.840 align:start position:0% and the way peer-to-peer projects 00:00:26.840 --> 00:00:29.090 align:start position:0% and the way peer-to-peer projects throughout<00:00:27.840> this<00:00:28.050> amazing<00:00:28.410> conference<00:00:28.710> we 00:00:29.090 --> 00:00:29.100 align:start position:0% throughout this amazing conference we 00:00:29.100 --> 00:00:30.589 align:start position:0% throughout this amazing conference we have<00:00:29.189> been<00:00:29.340> seeing<00:00:29.580> a<00:00:29.670> lot<00:00:29.820> of<00:00:29.880> technologies 00:00:30.589 --> 00:00:30.599 align:start position:0% have been seeing a lot of technologies 00:00:30.599 --> 00:00:32.180 align:start position:0% have been seeing a lot of technologies and<00:00:30.900> solutions<00:00:31.200> to<00:00:31.680> build<00:00:32.040> decentralized 00:00:32.180 --> 00:00:32.190 align:start position:0% and solutions to build decentralized 00:00:32.190 --> 00:00:35.119 align:start position:0% and solutions to build decentralized applications<00:00:33.020> pushing<00:00:34.020> the<00:00:34.110> boundaries<00:00:34.440> to<00:00:35.100> a 00:00:35.119 --> 00:00:35.129 align:start position:0% applications pushing the boundaries to a 00:00:35.129 --> 00:00:37.549 align:start position:0% applications pushing the boundaries to a complete<00:00:35.610> distributed<00:00:36.239> scenarios<00:00:36.690> however 00:00:37.549 --> 00:00:37.559 align:start position:0% complete distributed scenarios however 00:00:37.559 --> 00:00:40.070 align:start position:0% complete distributed scenarios however something<00:00:38.400> that<00:00:38.580> hasn't<00:00:38.940> been<00:00:39.150> covered<00:00:39.480> as 00:00:40.070 --> 00:00:40.080 align:start position:0% something that hasn't been covered as 00:00:40.080 --> 00:00:43.720 align:start position:0% something that hasn't been covered as much<00:00:40.140> is<00:00:40.650> the<00:00:41.640> networking<00:00:42.059> level<00:00:42.480> it<00:00:43.290> is 00:00:43.720 --> 00:00:43.730 align:start position:0% much is the networking level it is 00:00:43.730 --> 00:00:46.549 align:start position:0% much is the networking level it is required<00:00:44.730> to<00:00:44.940> do<00:00:45.180> a<00:00:45.210> lot<00:00:45.510> of<00:00:45.540> magic<00:00:46.290> I<00:00:46.320> might 00:00:46.549 --> 00:00:46.559 align:start position:0% required to do a lot of magic I might 00:00:46.559 --> 00:00:49.100 align:start position:0% required to do a lot of magic I might even<00:00:46.710> dare<00:00:46.949> to<00:00:47.159> say<00:00:47.339> black<00:00:47.699> magic<00:00:48.180> to<00:00:48.809> be<00:00:48.989> able 00:00:49.100 --> 00:00:49.110 align:start position:0% even dare to say black magic to be able 00:00:49.110 --> 00:00:50.689 align:start position:0% even dare to say black magic to be able to<00:00:49.500> do<00:00:49.739> these<00:00:50.070> peer-to-peer<00:00:50.400> applications 00:00:50.689 --> 00:00:50.699 align:start position:0% to do these peer-to-peer applications 00:00:50.699 --> 00:00:53.149 align:start position:0% to do these peer-to-peer applications work<00:00:51.420> in<00:00:51.720> the<00:00:52.199> infrastructure<00:00:52.680> that<00:00:52.800> we<00:00:52.949> have 00:00:53.149 --> 00:00:53.159 align:start position:0% work in the infrastructure that we have 00:00:53.159 --> 00:00:55.360 align:start position:0% work in the infrastructure that we have today<00:00:53.699> things<00:00:54.600> like 00:00:55.360 --> 00:00:55.370 align:start position:0% today things like 00:00:55.370 --> 00:00:59.530 align:start position:0% today things like Nats<00:00:56.720> firewalls<00:00:57.720> lack<00:00:58.620> of<00:00:58.769> cognitive<00:00:58.949> 'ti 00:00:59.530 --> 00:00:59.540 align:start position:0% Nats firewalls lack of cognitive 'ti 00:00:59.540 --> 00:01:02.329 align:start position:0% Nats firewalls lack of cognitive 'ti completely<00:01:00.540> offline<00:01:00.690> scenarios<00:01:01.440> sensor 00:01:02.329 --> 00:01:02.339 align:start position:0% completely offline scenarios sensor 00:01:02.339 --> 00:01:04.039 align:start position:0% completely offline scenarios sensor networks<00:01:02.760> are<00:01:03.030> some<00:01:03.269> of<00:01:03.390> the<00:01:03.510> problems<00:01:03.900> that 00:01:04.039 --> 00:01:04.049 align:start position:0% networks are some of the problems that 00:01:04.049 --> 00:01:06.860 align:start position:0% networks are some of the problems that we<00:01:04.530> peer-to-peer<00:01:05.190> software<00:01:05.790> developers<00:01:06.510> have 00:01:06.860 --> 00:01:06.870 align:start position:0% we peer-to-peer software developers have 00:01:06.870 --> 00:01:09.050 align:start position:0% we peer-to-peer software developers have to<00:01:07.200> overcome<00:01:07.560> in<00:01:07.860> order<00:01:08.159> to<00:01:08.310> build<00:01:08.460> these 00:01:09.050 --> 00:01:09.060 align:start position:0% to overcome in order to build these 00:01:09.060 --> 00:01:11.230 align:start position:0% to overcome in order to build these decentralized<00:01:09.720> applications<00:01:09.900> and 00:01:11.230 --> 00:01:11.240 align:start position:0% decentralized applications and 00:01:11.240 --> 00:01:15.200 align:start position:0% decentralized applications and it<00:01:12.240> is<00:01:12.479> not<00:01:12.630> by<00:01:12.840> chance<00:01:13.320> that<00:01:13.680> like<00:01:13.979> both<00:01:14.610> ipfs 00:01:15.200 --> 00:01:15.210 align:start position:0% it is not by chance that like both ipfs 00:01:15.210 --> 00:01:18.170 align:start position:0% it is not by chance that like both ipfs and<00:01:15.510> it<00:01:16.080> Helium<00:01:16.440> have<00:01:16.650> built<00:01:17.100> fully<00:01:17.640> matured 00:01:18.170 --> 00:01:18.180 align:start position:0% and it Helium have built fully matured 00:01:18.180 --> 00:01:20.690 align:start position:0% and it Helium have built fully matured networking<00:01:19.170> stacks<00:01:19.470> from<00:01:19.770> the<00:01:20.010> ground<00:01:20.220> up<00:01:20.370> to 00:01:20.690 --> 00:01:20.700 align:start position:0% networking stacks from the ground up to 00:01:20.700 --> 00:01:23.030 align:start position:0% networking stacks from the ground up to solve<00:01:21.000> these<00:01:21.540> challenges<00:01:21.770> we<00:01:22.770> peer-to-peer 00:01:23.030 --> 00:01:23.040 align:start position:0% solve these challenges we peer-to-peer 00:01:23.040 --> 00:01:24.980 align:start position:0% solve these challenges we peer-to-peer for<00:01:23.580> the<00:01:23.670> case<00:01:23.790> of<00:01:23.910> ipfs<00:01:24.330> and<00:01:24.540> DEF 00:01:24.980 --> 00:01:24.990 align:start position:0% for the case of ipfs and DEF 00:01:24.990 --> 00:01:28.100 align:start position:0% for the case of ipfs and DEF peer-to-peer<00:01:25.260> for<00:01:26.220> it<00:01:26.370> here<00:01:26.550> IAM<00:01:26.700> and<00:01:26.930> this<00:01:27.930> is 00:01:28.100 --> 00:01:28.110 align:start position:0% peer-to-peer for it here IAM and this is 00:01:28.110 --> 00:01:30.440 align:start position:0% peer-to-peer for it here IAM and this is simply<00:01:28.620> because<00:01:28.800> there<00:01:29.190> was<00:01:29.370> no<00:01:29.610> transport<00:01:30.210> in 00:01:30.440 --> 00:01:30.450 align:start position:0% simply because there was no transport in 00:01:30.450 --> 00:01:32.510 align:start position:0% simply because there was no transport in your<00:01:30.570> network<00:01:30.930> that<00:01:31.170> offered<00:01:31.890> the<00:01:32.040> primitives 00:01:32.510 --> 00:01:32.520 align:start position:0% your network that offered the primitives 00:01:32.520 --> 00:01:35.450 align:start position:0% your network that offered the primitives that<00:01:32.790> ipfs<00:01:33.660> and<00:01:33.960> it<00:01:34.050> even<00:01:34.260> needed<00:01:34.560> things<00:01:35.250> like 00:01:35.450 --> 00:01:35.460 align:start position:0% that ipfs and it even needed things like 00:01:35.460 --> 00:01:37.880 align:start position:0% that ipfs and it even needed things like authentication<00:01:36.150> and<00:01:36.390> encryption<00:01:36.740> being<00:01:37.740> able 00:01:37.880 --> 00:01:37.890 align:start position:0% authentication and encryption being able 00:01:37.890 --> 00:01:39.740 align:start position:0% authentication and encryption being able to<00:01:38.010> cope<00:01:38.310> with<00:01:38.460> several<00:01:38.850> network<00:01:39.180> topologies 00:01:39.740 --> 00:01:39.750 align:start position:0% to cope with several network topologies 00:01:39.750 --> 00:01:41.960 align:start position:0% to cope with several network topologies in<00:01:39.780> several<00:01:40.260> different<00:01:40.380> scenarios<00:01:40.710> are<00:01:41.250> some 00:01:41.960 --> 00:01:41.970 align:start position:0% in several different scenarios are some 00:01:41.970 --> 00:01:44.060 align:start position:0% in several different scenarios are some of<00:01:42.180> the<00:01:42.630> challenges<00:01:42.840> that<00:01:43.350> we<00:01:43.650> must<00:01:43.890> overcome 00:01:44.060 --> 00:01:44.070 align:start position:0% of the challenges that we must overcome 00:01:44.070 --> 00:01:46.160 align:start position:0% of the challenges that we must overcome and<00:01:44.640> like<00:01:44.970> face<00:01:45.210> when<00:01:45.600> we<00:01:45.720> are<00:01:45.810> building<00:01:46.050> these 00:01:46.160 --> 00:01:46.170 align:start position:0% and like face when we are building these 00:01:46.170 --> 00:01:50.600 align:start position:0% and like face when we are building these systems<00:01:46.700> however<00:01:47.700> there<00:01:48.690> is<00:01:48.810> a<00:01:48.840> key<00:01:49.260> small<00:01:50.220> key 00:01:50.600 --> 00:01:50.610 align:start position:0% systems however there is a key small key 00:01:50.610 --> 00:01:52.490 align:start position:0% systems however there is a key small key difference<00:01:50.970> between<00:01:51.420> the<00:01:51.510> designs<00:01:51.810> of<00:01:51.990> these 00:01:52.490 --> 00:01:52.500 align:start position:0% difference between the designs of these 00:01:52.500 --> 00:01:54.770 align:start position:0% difference between the designs of these networking<00:01:53.010> stacks<00:01:53.280> we<00:01:54.000> peer-to-peer<00:01:54.240> is 00:01:54.770 --> 00:01:54.780 align:start position:0% networking stacks we peer-to-peer is 00:01:54.780 --> 00:01:57.740 align:start position:0% networking stacks we peer-to-peer is modular<00:01:55.440> this<00:01:56.430> modularity<00:01:56.910> gives<00:01:57.450> us<00:01:57.600> the 00:01:57.740 --> 00:01:57.750 align:start position:0% modular this modularity gives us the 00:01:57.750 --> 00:02:01.220 align:start position:0% modular this modularity gives us the ability<00:01:57.870> to<00:01:58.640> increase<00:01:59.640> our<00:02:00.240> reach<00:02:00.750> in<00:02:01.080> terms 00:02:01.220 --> 00:02:01.230 align:start position:0% ability to increase our reach in terms 00:02:01.230 --> 00:02:03.890 align:start position:0% ability to increase our reach in terms of<00:02:01.409> devices<00:02:01.680> by<00:02:02.520> using<00:02:02.790> the<00:02:03.330> capabilities 00:02:03.890 --> 00:02:03.900 align:start position:0% of devices by using the capabilities 00:02:03.900 --> 00:02:05.690 align:start position:0% of devices by using the capabilities that<00:02:03.990> the<00:02:04.110> system<00:02:04.409> has<00:02:04.530> to<00:02:04.560> offer<00:02:05.100> every 00:02:05.690 --> 00:02:05.700 align:start position:0% that the system has to offer every 00:02:05.700 --> 00:02:08.960 align:start position:0% that the system has to offer every single<00:02:06.060> module<00:02:06.480> in<00:02:06.960> we<00:02:07.710> peer-to-peer<00:02:07.970> exposes 00:02:08.960 --> 00:02:08.970 align:start position:0% single module in we peer-to-peer exposes 00:02:08.970 --> 00:02:11.149 align:start position:0% single module in we peer-to-peer exposes a<00:02:09.000> well-defined<00:02:09.840> interface<00:02:10.289> for<00:02:10.920> peer 00:02:11.149 --> 00:02:11.159 align:start position:0% a well-defined interface for peer 00:02:11.159 --> 00:02:13.430 align:start position:0% a well-defined interface for peer discovery<00:02:11.700> for<00:02:12.060> routing<00:02:12.300> for<00:02:12.840> transports 00:02:13.430 --> 00:02:13.440 align:start position:0% discovery for routing for transports 00:02:13.440 --> 00:02:15.619 align:start position:0% discovery for routing for transports three<00:02:14.040> multiplexing<00:02:14.640> encryption<00:02:15.239> you<00:02:15.450> name 00:02:15.619 --> 00:02:15.629 align:start position:0% three multiplexing encryption you name 00:02:15.629 --> 00:02:19.640 align:start position:0% three multiplexing encryption you name it<00:02:15.780> and<00:02:16.050> we<00:02:17.040> can<00:02:17.310> pick<00:02:18.269> the<00:02:18.659> components<00:02:19.560> that 00:02:19.640 --> 00:02:19.650 align:start position:0% it and we can pick the components that 00:02:19.650 --> 00:02:21.619 align:start position:0% it and we can pick the components that we<00:02:19.890> want<00:02:20.129> and<00:02:20.310> bake<00:02:20.819> our<00:02:21.090> early<00:02:21.390> peer-to-peer 00:02:21.619 --> 00:02:21.629 align:start position:0% we want and bake our early peer-to-peer 00:02:21.629 --> 00:02:23.780 align:start position:0% we want and bake our early peer-to-peer solution<00:02:22.349> for<00:02:22.799> the<00:02:22.889> device<00:02:23.129> that<00:02:23.340> we<00:02:23.459> want<00:02:23.670> to 00:02:23.780 --> 00:02:23.790 align:start position:0% solution for the device that we want to 00:02:23.790 --> 00:02:26.809 align:start position:0% solution for the device that we want to run<00:02:23.969> this<00:02:24.840> modularity<00:02:25.379> gives<00:02:25.859> us<00:02:26.040> the 00:02:26.809 --> 00:02:26.819 align:start position:0% run this modularity gives us the 00:02:26.819 --> 00:02:29.420 align:start position:0% run this modularity gives us the opportunity<00:02:26.999> to<00:02:27.450> keep<00:02:28.330> our<00:02:28.510> primitives<00:02:29.200> for 00:02:29.420 --> 00:02:29.430 align:start position:0% opportunity to keep our primitives for 00:02:29.430 --> 00:02:32.550 align:start position:0% opportunity to keep our primitives for authenticated<00:02:30.630> process<00:02:31.630> addressing<00:02:32.110> intact 00:02:32.550 --> 00:02:32.560 align:start position:0% authenticated process addressing intact 00:02:32.560 --> 00:02:34.590 align:start position:0% authenticated process addressing intact it<00:02:32.770> is<00:02:33.040> a<00:02:33.070> very<00:02:33.370> powerful<00:02:33.610> construct<00:02:34.150> to<00:02:34.480> be 00:02:34.590 --> 00:02:34.600 align:start position:0% it is a very powerful construct to be 00:02:34.600 --> 00:02:37.140 align:start position:0% it is a very powerful construct to be able<00:02:34.690> to<00:02:34.870> address<00:02:35.680> any<00:02:35.980> other<00:02:36.160> process<00:02:36.760> in<00:02:36.940> the 00:02:37.140 --> 00:02:37.150 align:start position:0% able to address any other process in the 00:02:37.150 --> 00:02:39.570 align:start position:0% able to address any other process in the network<00:02:37.480> just<00:02:37.750> by<00:02:38.290> a<00:02:38.440> public<00:02:38.890> key<00:02:39.040> so<00:02:39.280> that<00:02:39.310> we 00:02:39.570 --> 00:02:39.580 align:start position:0% network just by a public key so that we 00:02:39.580 --> 00:02:41.520 align:start position:0% network just by a public key so that we can<00:02:39.760> find<00:02:40.390> the<00:02:40.540> process<00:02:40.870> in<00:02:40.990> the<00:02:41.050> network<00:02:41.380> and 00:02:41.520 --> 00:02:41.530 align:start position:0% can find the process in the network and 00:02:41.530 --> 00:02:43.680 align:start position:0% can find the process in the network and not<00:02:41.710> only<00:02:41.920> dial<00:02:42.310> to<00:02:42.550> it<00:02:42.640> but<00:02:43.210> also<00:02:43.360> make<00:02:43.660> sure 00:02:43.680 --> 00:02:43.690 align:start position:0% not only dial to it but also make sure 00:02:43.690 --> 00:02:44.910 align:start position:0% not only dial to it but also make sure that<00:02:43.960> we<00:02:44.080> are<00:02:44.170> talking<00:02:44.290> with<00:02:44.590> the<00:02:44.650> right 00:02:44.910 --> 00:02:44.920 align:start position:0% that we are talking with the right 00:02:44.920 --> 00:02:48.420 align:start position:0% that we are talking with the right endpoint<00:02:45.750> so<00:02:46.750> this<00:02:47.530> means<00:02:47.830> that<00:02:47.980> like<00:02:48.160> we<00:02:48.280> can 00:02:48.420 --> 00:02:48.430 align:start position:0% endpoint so this means that like we can 00:02:48.430 --> 00:02:51.240 align:start position:0% endpoint so this means that like we can go<00:02:48.610> from<00:02:48.910> the<00:02:49.120> traditional<00:02:49.660> physical<00:02:50.590> network 00:02:51.240 --> 00:02:51.250 align:start position:0% go from the traditional physical network 00:02:51.250 --> 00:02:53.910 align:start position:0% go from the traditional physical network to<00:02:51.970> a<00:02:52.000> super<00:02:52.510> connected<00:02:52.990> graph<00:02:53.230> with<00:02:53.890> a 00:02:53.910 --> 00:02:53.920 align:start position:0% to a super connected graph with a 00:02:53.920 --> 00:02:56.760 align:start position:0% to a super connected graph with a physical<00:02:54.490> and<00:02:54.820> virtual<00:02:55.120> over<00:02:55.690> on<00:02:55.960> physical 00:02:56.760 --> 00:02:56.770 align:start position:0% physical and virtual over on physical 00:02:56.770 --> 00:02:59.060 align:start position:0% physical and virtual over on physical and<00:02:56.920> virtual<00:02:57.430> overlay 00:02:59.060 --> 00:02:59.070 align:start position:0% and virtual overlay 00:02:59.070 --> 00:03:01.860 align:start position:0% and virtual overlay that<00:03:00.070> is<00:03:00.310> not<00:03:00.520> bound<00:03:00.880> by<00:03:01.150> the<00:03:01.330> capabilities<00:03:01.810> of 00:03:01.860 --> 00:03:01.870 align:start position:0% that is not bound by the capabilities of 00:03:01.870 --> 00:03:04.620 align:start position:0% that is not bound by the capabilities of the<00:03:02.050> system<00:03:02.230> we<00:03:02.950> can<00:03:02.980> use<00:03:03.580> things<00:03:03.850> like<00:03:04.060> butta 00:03:04.620 --> 00:03:04.630 align:start position:0% the system we can use things like butta 00:03:04.630 --> 00:03:06.390 align:start position:0% the system we can use things like butta to<00:03:04.840> create<00:03:05.140> some<00:03:05.260> of<00:03:05.290> these<00:03:05.470> channels<00:03:05.890> even 00:03:06.390 --> 00:03:06.400 align:start position:0% to create some of these channels even 00:03:06.400 --> 00:03:09.240 align:start position:0% to create some of these channels even radio<00:03:06.910> or<00:03:07.150> audio<00:03:07.540> can<00:03:07.720> be<00:03:07.750> transports<00:03:08.440> we<00:03:09.010> can 00:03:09.240 --> 00:03:09.250 align:start position:0% radio or audio can be transports we can 00:03:09.250 --> 00:03:11.400 align:start position:0% radio or audio can be transports we can upgrade<00:03:09.720> unreliable<00:03:10.720> channels<00:03:11.080> to<00:03:11.200> become 00:03:11.400 --> 00:03:11.410 align:start position:0% upgrade unreliable channels to become 00:03:11.410 --> 00:03:14.340 align:start position:0% upgrade unreliable channels to become reliable<00:03:11.950> with<00:03:12.190> reliability<00:03:13.150> upgrades<00:03:13.810> we 00:03:14.340 --> 00:03:14.350 align:start position:0% reliable with reliability upgrades we 00:03:14.350 --> 00:03:15.960 align:start position:0% reliable with reliability upgrades we can<00:03:14.530> encrypt<00:03:14.800> any<00:03:15.250> channel<00:03:15.520> that<00:03:15.550> we<00:03:15.730> want 00:03:15.960 --> 00:03:15.970 align:start position:0% can encrypt any channel that we want 00:03:15.970 --> 00:03:19.560 align:start position:0% can encrypt any channel that we want with<00:03:16.450> sekai<00:03:16.780> l<00:03:16.930> TLS<00:03:17.500> curve<00:03:18.040> DP<00:03:18.370> and<00:03:18.640> others<00:03:19.240> and 00:03:19.560 --> 00:03:19.570 align:start position:0% with sekai l TLS curve DP and others and 00:03:19.570 --> 00:03:22.590 align:start position:0% with sekai l TLS curve DP and others and this<00:03:20.560> means<00:03:20.830> that<00:03:20.980> we<00:03:21.130> can<00:03:21.160> also<00:03:21.280> enter<00:03:21.850> in<00:03:22.300> the 00:03:22.590 --> 00:03:22.600 align:start position:0% this means that we can also enter in the 00:03:22.600 --> 00:03:25.280 align:start position:0% this means that we can also enter in the ecosystems<00:03:23.260> that<00:03:23.380> don't<00:03:23.890> have<00:03:24.100> the<00:03:24.520> full 00:03:25.280 --> 00:03:25.290 align:start position:0% ecosystems that don't have the full 00:03:25.290 --> 00:03:27.600 align:start position:0% ecosystems that don't have the full networking<00:03:26.290> stacks<00:03:26.500> that<00:03:26.560> we<00:03:26.740> are<00:03:26.890> typically 00:03:27.600 --> 00:03:27.610 align:start position:0% networking stacks that we are typically 00:03:27.610 --> 00:03:30.780 align:start position:0% networking stacks that we are typically used<00:03:28.060> to<00:03:28.150> huge<00:03:28.960> cases<00:03:29.350> for<00:03:29.530> this<00:03:29.650> is<00:03:29.890> for 00:03:30.780 --> 00:03:30.790 align:start position:0% used to huge cases for this is for 00:03:30.790 --> 00:03:33.180 align:start position:0% used to huge cases for this is for example<00:03:31.060> the<00:03:31.150> browser<00:03:31.500> which<00:03:32.500> is<00:03:32.709> constrained 00:03:33.180 --> 00:03:33.190 align:start position:0% example the browser which is constrained 00:03:33.190 --> 00:03:36.210 align:start position:0% example the browser which is constrained to<00:03:33.340> just<00:03:33.640> have<00:03:33.790> WebSockets<00:03:34.450> HTTP<00:03:35.230> and<00:03:35.440> WebRTC 00:03:36.210 --> 00:03:36.220 align:start position:0% to just have WebSockets HTTP and WebRTC 00:03:36.220 --> 00:03:38.100 align:start position:0% to just have WebSockets HTTP and WebRTC or<00:03:36.430> Internet<00:03:37.180> of<00:03:37.209> Things<00:03:37.330> devices<00:03:37.810> that 00:03:38.100 --> 00:03:38.110 align:start position:0% or Internet of Things devices that 00:03:38.110 --> 00:03:40.140 align:start position:0% or Internet of Things devices that sometime<00:03:38.410> don't<00:03:38.620> even<00:03:38.860> have<00:03:39.070> TCP<00:03:39.640> stacks<00:03:39.910> you 00:03:40.140 --> 00:03:40.150 align:start position:0% sometime don't even have TCP stacks you 00:03:40.150 --> 00:03:43.229 align:start position:0% sometime don't even have TCP stacks you have<00:03:40.360> you<00:03:40.630> are<00:03:40.950> you<00:03:41.950> have<00:03:42.070> to<00:03:42.190> rely<00:03:42.520> on<00:03:42.790> some 00:03:43.229 --> 00:03:43.239 align:start position:0% have you are you have to rely on some 00:03:43.239 --> 00:03:46.050 align:start position:0% have you are you have to rely on some radio<00:03:43.770> protocol<00:03:44.770> in<00:03:45.040> order<00:03:45.250> to<00:03:45.640> be<00:03:45.760> able<00:03:45.820> to 00:03:46.050 --> 00:03:46.060 align:start position:0% radio protocol in order to be able to 00:03:46.060 --> 00:03:48.229 align:start position:0% radio protocol in order to be able to dial<00:03:46.239> out<00:03:46.450> of<00:03:46.720> that<00:03:47.050> device<00:03:47.350> for 00:03:48.229 --> 00:03:48.239 align:start position:0% dial out of that device for 00:03:48.239 --> 00:03:49.850 align:start position:0% dial out of that device for example 00:03:49.850 --> 00:03:49.860 align:start position:0% example 00:03:49.860 --> 00:03:53.280 align:start position:0% example the<00:03:50.860> one<00:03:51.610> very<00:03:51.850> good<00:03:51.910> example<00:03:52.300> of<00:03:52.630> our<00:03:52.810> reputed 00:03:53.280 --> 00:03:53.290 align:start position:0% the one very good example of our reputed 00:03:53.290 --> 00:03:55.020 align:start position:0% the one very good example of our reputed peers<00:03:53.500> of<00:03:53.620> pluggable<00:03:54.040> is<00:03:54.190> that<00:03:54.310> our<00:03:54.489> friends 00:03:55.020 --> 00:03:55.030 align:start position:0% peers of pluggable is that our friends 00:03:55.030 --> 00:03:57.360 align:start position:0% peers of pluggable is that our friends from<00:03:55.239> open<00:03:55.660> Bazaar<00:03:55.959> needed<00:03:56.860> and<00:03:57.010> wanted<00:03:57.160> to 00:03:57.360 --> 00:03:57.370 align:start position:0% from open Bazaar needed and wanted to 00:03:57.370 --> 00:04:00.390 align:start position:0% from open Bazaar needed and wanted to have<00:03:57.580> a<00:03:57.670> tour<00:03:58.000> transport<00:03:58.570> for<00:03:58.989> their<00:03:59.920> their 00:04:00.390 --> 00:04:00.400 align:start position:0% have a tour transport for their their 00:04:00.400 --> 00:04:03.090 align:start position:0% have a tour transport for their their use<00:04:00.580> and<00:04:00.840> all<00:04:01.840> they<00:04:02.050> needed<00:04:02.290> to<00:04:02.440> do<00:04:02.680> was<00:04:03.070> to 00:04:03.090 --> 00:04:03.100 align:start position:0% use and all they needed to do was to 00:04:03.100 --> 00:04:05.310 align:start position:0% use and all they needed to do was to create<00:04:03.400> a<00:04:03.580> tour<00:04:03.880> transport<00:04:04.390> that<00:04:04.510> fulfill<00:04:05.050> the 00:04:05.310 --> 00:04:05.320 align:start position:0% create a tour transport that fulfill the 00:04:05.320 --> 00:04:07.620 align:start position:0% create a tour transport that fulfill the same<00:04:05.500> interface<00:04:05.950> as<00:04:06.220> the<00:04:06.790> other<00:04:06.940> transports 00:04:07.620 --> 00:04:07.630 align:start position:0% same interface as the other transports 00:04:07.630 --> 00:04:09.840 align:start position:0% same interface as the other transports only<00:04:07.780> peer-to-peer<00:04:08.230> and<00:04:08.709> they<00:04:09.160> can<00:04:09.340> just<00:04:09.520> plug 00:04:09.840 --> 00:04:09.850 align:start position:0% only peer-to-peer and they can just plug 00:04:09.850 --> 00:04:12.120 align:start position:0% only peer-to-peer and they can just plug it<00:04:09.970> right<00:04:10.120> in<00:04:10.300> and<00:04:10.330> once<00:04:11.050> that<00:04:11.530> is<00:04:11.590> done<00:04:11.739> every 00:04:12.120 --> 00:04:12.130 align:start position:0% it right in and once that is done every 00:04:12.130 --> 00:04:13.830 align:start position:0% it right in and once that is done every other<00:04:12.520> application<00:04:12.790> that<00:04:13.360> wants<00:04:13.480> to<00:04:13.690> use<00:04:13.810> that 00:04:13.830 --> 00:04:13.840 align:start position:0% other application that wants to use that 00:04:13.840 --> 00:04:15.930 align:start position:0% other application that wants to use that transport<00:04:14.350> can<00:04:14.530> just<00:04:14.739> bring<00:04:14.980> it<00:04:15.160> and<00:04:15.340> you 00:04:15.930 --> 00:04:15.940 align:start position:0% transport can just bring it and you 00:04:15.940 --> 00:04:18.060 align:start position:0% transport can just bring it and you don't<00:04:16.090> have<00:04:16.239> to<00:04:16.390> change<00:04:16.660> anything<00:04:17.290> from<00:04:17.890> the 00:04:18.060 --> 00:04:18.070 align:start position:0% don't have to change anything from the 00:04:18.070 --> 00:04:20.180 align:start position:0% don't have to change anything from the codebase<00:04:18.400> of<00:04:18.700> your<00:04:19.359> application<00:04:19.840> the 00:04:20.180 --> 00:04:20.190 align:start position:0% codebase of your application the 00:04:20.190 --> 00:04:22.890 align:start position:0% codebase of your application the primitives<00:04:21.190> stay<00:04:21.549> the<00:04:21.700> same<00:04:21.880> it<00:04:22.419> is<00:04:22.570> really 00:04:22.890 --> 00:04:22.900 align:start position:0% primitives stay the same it is really 00:04:22.900 --> 00:04:25.110 align:start position:0% primitives stay the same it is really powerful<00:04:23.050> think<00:04:23.620> like<00:04:24.100> having<00:04:24.520> fully<00:04:24.850> team 00:04:25.110 --> 00:04:25.120 align:start position:0% powerful think like having fully team 00:04:25.120 --> 00:04:27.120 align:start position:0% powerful think like having fully team notes<00:04:25.390> running<00:04:26.200> in<00:04:26.380> every<00:04:26.620> single<00:04:27.010> device 00:04:27.120 --> 00:04:27.130 align:start position:0% notes running in every single device 00:04:27.130 --> 00:04:30.740 align:start position:0% notes running in every single device with<00:04:27.790> no<00:04:27.820> limitations 00:04:30.740 --> 00:04:30.750 align:start position:0% 00:04:30.750 --> 00:04:35.520 align:start position:0% so<00:04:32.160> we<00:04:33.160> think<00:04:33.430> and<00:04:33.700> we<00:04:34.000> see<00:04:34.600> deaf<00:04:34.900> p2p<00:04:35.410> era 00:04:35.520 --> 00:04:35.530 align:start position:0% so we think and we see deaf p2p era 00:04:35.530 --> 00:04:36.770 align:start position:0% so we think and we see deaf p2p era peer-to-peer 00:04:36.770 --> 00:04:36.780 align:start position:0% peer-to-peer 00:04:36.780 --> 00:04:39.390 align:start position:0% peer-to-peer being<00:04:37.780> able<00:04:37.900> to<00:04:38.050> converge<00:04:38.590> and<00:04:38.919> like<00:04:39.070> to<00:04:39.220> join 00:04:39.390 --> 00:04:39.400 align:start position:0% being able to converge and like to join 00:04:39.400 --> 00:04:42.269 align:start position:0% being able to converge and like to join efforts<00:04:39.640> to<00:04:40.120> make<00:04:40.510> a<00:04:40.810> way 00:04:42.269 --> 00:04:42.279 align:start position:0% efforts to make a way 00:04:42.279 --> 00:04:44.909 align:start position:0% efforts to make a way ecosystem<00:04:43.029> for<00:04:43.329> the<00:04:43.779> community<00:04:44.199> that<00:04:44.439> uses 00:04:44.909 --> 00:04:44.919 align:start position:0% ecosystem for the community that uses 00:04:44.919 --> 00:04:47.189 align:start position:0% ecosystem for the community that uses these<00:04:45.069> networks<00:04:45.609> tax<00:04:45.819> their<00:04:46.629> future<00:04:46.929> pier 00:04:47.189 --> 00:04:47.199 align:start position:0% these networks tax their future pier 00:04:47.199 --> 00:04:49.439 align:start position:0% these networks tax their future pier offers<00:04:47.649> a<00:04:47.679> lot<00:04:47.949> of<00:04:47.979> primitives<00:04:48.519> that<00:04:49.119> can 00:04:49.439 --> 00:04:49.449 align:start position:0% offers a lot of primitives that can 00:04:49.449 --> 00:04:52.429 align:start position:0% offers a lot of primitives that can augment<00:04:49.899> this<00:04:50.289> ecosystem<00:04:50.739> and 00:04:52.429 --> 00:04:52.439 align:start position:0% augment this ecosystem and 00:04:52.439 --> 00:04:54.769 align:start position:0% augment this ecosystem and since<00:04:53.439> we 00:04:54.769 --> 00:04:54.779 align:start position:0% since we 00:04:54.779 --> 00:04:57.149 align:start position:0% since we already<00:04:55.779> did<00:04:55.959> the<00:04:56.079> work<00:04:56.109> as<00:04:56.529> one<00:04:56.829> mentioned 00:04:57.149 --> 00:04:57.159 align:start position:0% already did the work as one mentioned 00:04:57.159 --> 00:04:59.039 align:start position:0% already did the work as one mentioned earlier<00:04:57.459> of<00:04:57.699> getting<00:04:58.149> ipfs<00:04:58.629> running<00:04:58.899> on<00:04:58.959> the 00:04:59.039 --> 00:04:59.049 align:start position:0% earlier of getting ipfs running on the 00:04:59.049 --> 00:05:01.289 align:start position:0% earlier of getting ipfs running on the browser<00:04:59.259> we<00:04:59.979> kind<00:05:00.159> of<00:05:00.249> like<00:05:00.399> went<00:05:00.729> ahead<00:05:00.879> and 00:05:01.289 --> 00:05:01.299 align:start position:0% browser we kind of like went ahead and 00:05:01.299 --> 00:05:02.239 align:start position:0% browser we kind of like went ahead and asked<00:05:01.569> ourselves 00:05:02.239 --> 00:05:02.249 align:start position:0% asked ourselves 00:05:02.249 --> 00:05:06.059 align:start position:0% asked ourselves what<00:05:03.249> would<00:05:03.489> we<00:05:03.729> have<00:05:03.849> to<00:05:04.149> do<00:05:04.449> in<00:05:05.049> order<00:05:05.469> to<00:05:05.649> get 00:05:06.059 --> 00:05:06.069 align:start position:0% what would we have to do in order to get 00:05:06.069 --> 00:05:10.489 align:start position:0% what would we have to do in order to get any<00:05:06.519> tem<00:05:06.909> node<00:05:07.139> running<00:05:08.139> on<00:05:08.439> the<00:05:08.529> browser<00:05:09.059> so 00:05:10.489 --> 00:05:10.499 align:start position:0% any tem node running on the browser so 00:05:10.499 --> 00:05:13.889 align:start position:0% any tem node running on the browser so I'll<00:05:11.499> just<00:05:11.679> show<00:05:12.219> like<00:05:12.669> we<00:05:13.149> started<00:05:13.569> hacking 00:05:13.889 --> 00:05:13.899 align:start position:0% I'll just show like we started hacking 00:05:13.899 --> 00:05:15.049 align:start position:0% I'll just show like we started hacking something 00:05:15.049 --> 00:05:15.059 align:start position:0% something 00:05:15.059 --> 00:05:18.779 align:start position:0% something it<00:05:16.059> is<00:05:16.389> very<00:05:16.829> in<00:05:17.829> the<00:05:17.979> beginning<00:05:18.339> a<00:05:18.429> very<00:05:18.610> early 00:05:18.779 --> 00:05:18.789 align:start position:0% it is very in the beginning a very early 00:05:18.789 --> 00:05:21.659 align:start position:0% it is very in the beginning a very early stage<00:05:19.119> it's<00:05:19.569> a<00:05:19.659> humble<00:05:19.929> beginning<00:05:20.349> but<00:05:21.129> we 00:05:21.659 --> 00:05:21.669 align:start position:0% stage it's a humble beginning but we 00:05:21.669 --> 00:05:22.949 align:start position:0% stage it's a humble beginning but we want<00:05:21.849> to<00:05:21.939> show<00:05:22.059> you<00:05:22.089> the<00:05:22.299> process<00:05:22.509> the 00:05:22.949 --> 00:05:22.959 align:start position:0% want to show you the process the 00:05:22.959 --> 00:05:26.239 align:start position:0% want to show you the process the progress<00:05:23.319> I<00:05:23.789> have<00:05:24.789> two<00:05:24.939> demos<00:05:25.119> for<00:05:25.329> you 00:05:26.239 --> 00:05:26.249 align:start position:0% progress I have two demos for you 00:05:26.249 --> 00:05:28.069 align:start position:0% progress I have two demos for you so 00:05:28.069 --> 00:05:28.079 align:start position:0% so 00:05:28.079 --> 00:05:31.039 align:start position:0% so looking<00:05:29.079> for<00:05:29.229> the<00:05:29.319> demo<00:05:29.499> one 00:05:31.039 --> 00:05:31.049 align:start position:0% looking for the demo one 00:05:31.049 --> 00:05:33.509 align:start position:0% looking for the demo one so<00:05:32.049> the<00:05:32.169> first<00:05:32.349> challenge<00:05:32.529> is<00:05:32.860> really<00:05:33.069> getting 00:05:33.509 --> 00:05:33.519 align:start position:0% so the first challenge is really getting 00:05:33.519 --> 00:05:35.819 align:start position:0% so the first challenge is really getting the<00:05:33.669> etherium<00:05:34.059> vm<00:05:34.389> working<00:05:35.289> on<00:05:35.469> the<00:05:35.619> browser 00:05:35.819 --> 00:05:35.829 align:start position:0% the etherium vm working on the browser 00:05:35.829 --> 00:05:38.969 align:start position:0% the etherium vm working on the browser here<00:05:36.759> basically<00:05:37.589> you<00:05:38.589> might<00:05:38.709> be<00:05:38.829> familiar 00:05:38.969 --> 00:05:38.979 align:start position:0% here basically you might be familiar 00:05:38.979 --> 00:05:41.579 align:start position:0% here basically you might be familiar with<00:05:39.339> the<00:05:39.519> standard<00:05:39.959> setup<00:05:40.959> of<00:05:41.229> getting<00:05:41.499> a 00:05:41.579 --> 00:05:41.589 align:start position:0% with the standard setup of getting a 00:05:41.589 --> 00:05:43.289 align:start position:0% with the standard setup of getting a browser<00:05:41.799> app<00:05:41.979> nowadays<00:05:42.459> running<00:05:43.029> on<00:05:43.179> the 00:05:43.289 --> 00:05:43.299 align:start position:0% browser app nowadays running on the 00:05:43.299 --> 00:05:46.379 align:start position:0% browser app nowadays running on the browser<00:05:43.479> you<00:05:43.989> have<00:05:44.649> to<00:05:44.909> physically<00:05:45.909> transpile 00:05:46.379 --> 00:05:46.389 align:start position:0% browser you have to physically transpile 00:05:46.389 --> 00:05:48.929 align:start position:0% browser you have to physically transpile everything<00:05:46.779> and<00:05:47.079> then<00:05:47.559> once<00:05:47.949> it's<00:05:48.399> transpiled 00:05:48.929 --> 00:05:48.939 align:start position:0% everything and then once it's transpiled 00:05:48.939 --> 00:05:51.569 align:start position:0% everything and then once it's transpiled we<00:05:49.179> can<00:05:49.360> load<00:05:49.629> it<00:05:49.779> and<00:05:50.159> we<00:05:51.159> prepared<00:05:51.489> this 00:05:51.569 --> 00:05:51.579 align:start position:0% we can load it and we prepared this 00:05:51.579 --> 00:05:53.100 align:start position:0% we can load it and we prepared this really<00:05:51.939> nice<00:05:52.029> fresh<00:05:52.299> world<00:05:52.569> so<00:05:52.719> you<00:05:52.809> can<00:05:52.839> see 00:05:53.100 --> 00:05:53.110 align:start position:0% really nice fresh world so you can see 00:05:53.110 --> 00:05:55.019 align:start position:0% really nice fresh world so you can see what's<00:05:53.259> going<00:05:53.349> on<00:05:53.619> and<00:05:53.860> here<00:05:54.489> we<00:05:54.639> are<00:05:54.669> going<00:05:54.819> to 00:05:55.019 --> 00:05:55.029 align:start position:0% what's going on and here we are going to 00:05:55.029 --> 00:05:57.239 align:start position:0% what's going on and here we are going to get<00:05:55.179> like<00:05:55.449> simulate<00:05:55.959> d2<00:05:56.619> in<00:05:56.739> blockchain<00:05:57.099> we 00:05:57.239 --> 00:05:57.249 align:start position:0% get like simulate d2 in blockchain we 00:05:57.249 --> 00:05:58.769 align:start position:0% get like simulate d2 in blockchain we are<00:05:57.339> going<00:05:57.459> to<00:05:57.549> create<00:05:57.729> some<00:05:57.789> blocks<00:05:58.119> and<00:05:58.329> we 00:05:58.769 --> 00:05:58.779 align:start position:0% are going to create some blocks and we 00:05:58.779 --> 00:06:00.689 align:start position:0% are going to create some blocks and we are<00:05:58.869> going<00:05:59.049> to<00:05:59.169> process<00:05:59.439> them<00:06:00.189> through<00:06:00.579> the 00:06:00.689 --> 00:06:00.699 align:start position:0% are going to process them through the 00:06:00.699 --> 00:06:03.359 align:start position:0% are going to process them through the etherium<00:06:00.999> vm<00:06:01.269> there<00:06:02.049> is<00:06:02.139> always<00:06:02.529> like<00:06:02.829> since 00:06:03.359 --> 00:06:03.369 align:start position:0% etherium vm there is always like since 00:06:03.369 --> 00:06:04.949 align:start position:0% etherium vm there is always like since these<00:06:03.669> operations<00:06:04.179> are<00:06:04.269> very<00:06:04.299> CPU<00:06:04.869> intensive 00:06:04.949 --> 00:06:04.959 align:start position:0% these operations are very CPU intensive 00:06:04.959 --> 00:06:07.319 align:start position:0% these operations are very CPU intensive it<00:06:05.589> takes<00:06:06.099> a<00:06:06.189> little<00:06:06.339> bit<00:06:06.549> to<00:06:06.669> warm<00:06:06.819> up<00:06:07.029> but 00:06:07.319 --> 00:06:07.329 align:start position:0% it takes a little bit to warm up but 00:06:07.329 --> 00:06:09.419 align:start position:0% it takes a little bit to warm up but once<00:06:07.389> it's<00:06:07.719> there<00:06:07.779> you<00:06:08.289> can<00:06:08.439> just<00:06:08.589> run<00:06:09.069> it<00:06:09.099> rest 00:06:09.419 --> 00:06:09.429 align:start position:0% once it's there you can just run it rest 00:06:09.429 --> 00:06:12.779 align:start position:0% once it's there you can just run it rest check<00:06:09.669> country<00:06:10.119> we<00:06:10.749> get<00:06:10.959> helium<00:06:11.769> VM<00:06:12.369> on<00:06:12.610> the 00:06:12.779 --> 00:06:12.789 align:start position:0% check country we get helium VM on the 00:06:12.789 --> 00:06:15.119 align:start position:0% check country we get helium VM on the browser<00:06:12.999> running<00:06:13.839> blocks<00:06:14.589> from<00:06:14.769> the<00:06:14.919> GM 00:06:15.119 --> 00:06:15.129 align:start position:0% browser running blocks from the GM 00:06:15.129 --> 00:06:17.399 align:start position:0% browser running blocks from the GM blockchain<00:06:15.519> but<00:06:16.029> there<00:06:16.329> is<00:06:16.419> more<00:06:16.569> so<00:06:17.079> now<00:06:17.229> I'm 00:06:17.399 --> 00:06:17.409 align:start position:0% blockchain but there is more so now I'm 00:06:17.409 --> 00:06:20.519 align:start position:0% blockchain but there is more so now I'm opening<00:06:17.769> another<00:06:18.039> tab<00:06:18.399> and<00:06:18.669> I'm<00:06:19.529> basically 00:06:20.519 --> 00:06:20.529 align:start position:0% opening another tab and I'm basically 00:06:20.529 --> 00:06:22.350 align:start position:0% opening another tab and I'm basically connecting<00:06:21.309> to<00:06:21.519> the<00:06:21.639> other<00:06:21.789> peer<00:06:22.029> that<00:06:22.209> was 00:06:22.350 --> 00:06:22.360 align:start position:0% connecting to the other peer that was 00:06:22.360 --> 00:06:24.539 align:start position:0% connecting to the other peer that was open<00:06:22.869> before<00:06:23.199> and<00:06:23.499> I'm<00:06:23.739> connecting<00:06:24.189> these<00:06:24.489> two 00:06:24.539 --> 00:06:24.549 align:start position:0% open before and I'm connecting these two 00:06:24.549 --> 00:06:26.789 align:start position:0% open before and I'm connecting these two browser<00:06:24.879> tabs<00:06:25.179> so<00:06:25.419> instead<00:06:25.779> of<00:06:25.929> generating 00:06:26.789 --> 00:06:26.799 align:start position:0% browser tabs so instead of generating 00:06:26.799 --> 00:06:28.679 align:start position:0% browser tabs so instead of generating blocks<00:06:27.189> I'm<00:06:27.459> just<00:06:27.729> going<00:06:27.939> to<00:06:28.029> ask<00:06:28.149> that<00:06:28.269> peer 00:06:28.679 --> 00:06:28.689 align:start position:0% blocks I'm just going to ask that peer 00:06:28.689 --> 00:06:31.259 align:start position:0% blocks I'm just going to ask that peer to<00:06:29.289> give<00:06:29.559> me<00:06:29.649> the<00:06:29.769> box<00:06:29.979> so<00:06:30.610> it<00:06:30.999> happens 00:06:31.259 --> 00:06:31.269 align:start position:0% to give me the box so it happens 00:06:31.269 --> 00:06:33.119 align:start position:0% to give me the box so it happens seamlessly<00:06:31.419> like<00:06:31.929> I<00:06:32.019> just<00:06:32.079> said<00:06:32.409> dial<00:06:32.799> to<00:06:33.009> this 00:06:33.119 --> 00:06:33.129 align:start position:0% seamlessly like I just said dial to this 00:06:33.129 --> 00:06:36.119 align:start position:0% seamlessly like I just said dial to this other<00:06:33.339> peer<00:06:33.699> it<00:06:34.269> found<00:06:34.659> the<00:06:34.809> peer<00:06:35.110> and<00:06:35.259> fetch 00:06:36.119 --> 00:06:36.129 align:start position:0% other peer it found the peer and fetch 00:06:36.129 --> 00:06:38.699 align:start position:0% other peer it found the peer and fetch the<00:06:36.339> blocks<00:06:36.579> from<00:06:36.759> that<00:06:36.999> network<00:06:37.360> so<00:06:37.539> we<00:06:38.499> can 00:06:38.699 --> 00:06:38.709 align:start position:0% the blocks from that network so we can 00:06:38.709 --> 00:06:41.339 align:start position:0% the blocks from that network so we can get<00:06:39.489> the<00:06:40.179> TMV<00:06:40.479> I'm<00:06:40.629> running<00:06:40.959> on<00:06:41.049> the<00:06:41.139> browser 00:06:41.339 --> 00:06:41.349 align:start position:0% get the TMV I'm running on the browser 00:06:41.349 --> 00:06:43.350 align:start position:0% get the TMV I'm running on the browser and<00:06:41.679> finding<00:06:42.189> blocks<00:06:42.429> from<00:06:42.549> other<00:06:42.759> nodes<00:06:42.969> this 00:06:43.350 --> 00:06:43.360 align:start position:0% and finding blocks from other nodes this 00:06:43.360 --> 00:06:44.869 align:start position:0% and finding blocks from other nodes this is<00:06:43.539> pretty<00:06:43.809> exciting 00:06:44.869 --> 00:06:44.879 align:start position:0% is pretty exciting 00:06:44.879 --> 00:06:47.399 align:start position:0% is pretty exciting but<00:06:45.879> there<00:06:45.999> is<00:06:46.089> more<00:06:46.269> so<00:06:46.599> you<00:06:46.689> can<00:06:46.719> see<00:06:46.869> I<00:06:47.049> can 00:06:47.399 --> 00:06:47.409 align:start position:0% but there is more so you can see I can 00:06:47.409 --> 00:06:48.959 align:start position:0% but there is more so you can see I can pop<00:06:47.799> more<00:06:48.009> nodes<00:06:48.219> and<00:06:48.459> like<00:06:48.549> they<00:06:48.669> find<00:06:48.879> each 00:06:48.959 --> 00:06:48.969 align:start position:0% pop more nodes and like they find each 00:06:48.969 --> 00:06:51.989 align:start position:0% pop more nodes and like they find each other<00:06:49.179> very<00:06:49.479> quickly<00:06:49.949> but<00:06:50.949> now<00:06:51.069> like<00:06:51.550> the<00:06:51.789> real 00:06:51.989 --> 00:06:51.999 align:start position:0% other very quickly but now like the real 00:06:51.999 --> 00:06:53.609 align:start position:0% other very quickly but now like the real interesting<00:06:52.419> demo<00:06:52.659> is<00:06:52.779> like<00:06:52.959> can<00:06:53.229> we<00:06:53.259> get 00:06:53.609 --> 00:06:53.619 align:start position:0% interesting demo is like can we get 00:06:53.619 --> 00:06:55.800 align:start position:0% interesting demo is like can we get these<00:06:54.309> browser<00:06:54.729> nodes 00:06:55.800 --> 00:06:55.810 align:start position:0% these browser nodes 00:06:55.810 --> 00:06:58.460 align:start position:0% these browser nodes connecting<00:06:56.650> to<00:06:56.680> the<00:06:56.860> real<00:06:57.220> etherium<00:06:57.940> network 00:06:58.460 --> 00:06:58.470 align:start position:0% connecting to the real etherium network 00:06:58.470 --> 00:07:01.170 align:start position:0% connecting to the real etherium network let's<00:06:59.470> see<00:06:59.800> demos<00:07:00.430> ooh<00:07:00.550> I<00:07:00.669> already<00:07:01.000> played 00:07:01.170 --> 00:07:01.180 align:start position:0% let's see demos ooh I already played 00:07:01.180 --> 00:07:04.440 align:start position:0% let's see demos ooh I already played awesome<00:07:01.960> okay<00:07:02.410> so<00:07:02.470> same<00:07:03.160> dance<00:07:03.430> getting<00:07:04.210> the 00:07:04.440 --> 00:07:04.450 align:start position:0% awesome okay so same dance getting the 00:07:04.450 --> 00:07:07.140 align:start position:0% awesome okay so same dance getting the application<00:07:05.110> to<00:07:05.200> run<00:07:05.490> but<00:07:06.490> here<00:07:06.790> we<00:07:06.910> are<00:07:06.940> doing 00:07:07.140 --> 00:07:07.150 align:start position:0% application to run but here we are doing 00:07:07.150 --> 00:07:09.420 align:start position:0% application to run but here we are doing something<00:07:07.660> extra<00:07:08.500> we<00:07:08.860> are<00:07:08.980> going<00:07:09.160> to<00:07:09.250> run<00:07:09.400> a 00:07:09.420 --> 00:07:09.430 align:start position:0% something extra we are going to run a 00:07:09.430 --> 00:07:11.430 align:start position:0% something extra we are going to run a gayageum<00:07:10.060> notes<00:07:10.630> patch<00:07:11.020> through<00:07:11.320> the 00:07:11.430 --> 00:07:11.440 align:start position:0% gayageum notes patch through the 00:07:11.440 --> 00:07:14.370 align:start position:0% gayageum notes patch through the peer-to-peer<00:07:11.860> so<00:07:12.760> it<00:07:12.910> does<00:07:13.090> an<00:07:13.389> address<00:07:14.110> in 00:07:14.370 --> 00:07:14.380 align:start position:0% peer-to-peer so it does an address in 00:07:14.380 --> 00:07:17.310 align:start position:0% peer-to-peer so it does an address in the<00:07:14.500> way<00:07:14.590> peer-to-peer<00:07:15.220> echo<00:07:15.790> system<00:07:16.020> and<00:07:17.020> now 00:07:17.310 --> 00:07:17.320 align:start position:0% the way peer-to-peer echo system and now 00:07:17.320 --> 00:07:18.570 align:start position:0% the way peer-to-peer echo system and now instead<00:07:17.620> of<00:07:17.770> like<00:07:17.980> simulating<00:07:18.520> the 00:07:18.570 --> 00:07:18.580 align:start position:0% instead of like simulating the 00:07:18.580 --> 00:07:20.280 align:start position:0% instead of like simulating the blockchain<00:07:18.850> I'm<00:07:19.180> just<00:07:19.600> going<00:07:19.810> to<00:07:19.840> dial<00:07:20.110> to 00:07:20.280 --> 00:07:20.290 align:start position:0% blockchain I'm just going to dial to 00:07:20.290 --> 00:07:22.710 align:start position:0% blockchain I'm just going to dial to that<00:07:20.410> girl<00:07:20.800> with<00:07:20.980> helium<00:07:21.220> note<00:07:21.430> and<00:07:21.669> fetch<00:07:22.480> the 00:07:22.710 --> 00:07:22.720 align:start position:0% that girl with helium note and fetch the 00:07:22.720 --> 00:07:24.150 align:start position:0% that girl with helium note and fetch the blocks<00:07:22.990> like<00:07:23.380> basically<00:07:23.770> I'm<00:07:23.860> using<00:07:23.919> this 00:07:24.150 --> 00:07:24.160 align:start position:0% blocks like basically I'm using this 00:07:24.160 --> 00:07:26.670 align:start position:0% blocks like basically I'm using this game<00:07:24.490> note<00:07:24.940> that<00:07:25.510> was<00:07:25.900> augmented<00:07:26.410> with<00:07:26.620> the 00:07:26.670 --> 00:07:26.680 align:start position:0% game note that was augmented with the 00:07:26.680 --> 00:07:28.800 align:start position:0% game note that was augmented with the peer-to-peer<00:07:27.040> to<00:07:27.880> connect<00:07:28.210> to<00:07:28.300> the<00:07:28.389> rest<00:07:28.570> of 00:07:28.800 --> 00:07:28.810 align:start position:0% peer-to-peer to connect to the rest of 00:07:28.810 --> 00:07:31.340 align:start position:0% peer-to-peer to connect to the rest of the<00:07:28.900> network<00:07:29.280> again<00:07:30.310> the 00:07:31.340 --> 00:07:31.350 align:start position:0% the network again the 00:07:31.350 --> 00:07:33.659 align:start position:0% the network again the generating<00:07:32.350> the<00:07:32.500> Genesis<00:07:32.919> block<00:07:33.040> dance<00:07:33.340> takes 00:07:33.659 --> 00:07:33.669 align:start position:0% generating the Genesis block dance takes 00:07:33.669 --> 00:07:35.250 align:start position:0% generating the Genesis block dance takes a<00:07:33.760> little<00:07:33.880> bit<00:07:34.300> this<00:07:34.750> can<00:07:34.930> be<00:07:35.050> greatly 00:07:35.250 --> 00:07:35.260 align:start position:0% a little bit this can be greatly 00:07:35.260 --> 00:07:36.990 align:start position:0% a little bit this can be greatly improved<00:07:35.440> especially<00:07:35.830> with<00:07:36.310> recent<00:07:36.700> work 00:07:36.990 --> 00:07:37.000 align:start position:0% improved especially with recent work 00:07:37.000 --> 00:07:40.230 align:start position:0% improved especially with recent work from<00:07:37.030> marketing<00:07:37.479> on<00:07:37.690> Ella<00:07:38.020> zoom<00:07:38.380> I'm<00:07:38.530> sure<00:07:39.240> but 00:07:40.230 --> 00:07:40.240 align:start position:0% from marketing on Ella zoom I'm sure but 00:07:40.240 --> 00:07:42.000 align:start position:0% from marketing on Ella zoom I'm sure but once<00:07:40.450> that's<00:07:40.630> there<00:07:41.020> we'll<00:07:41.470> start<00:07:41.740> receiving 00:07:42.000 --> 00:07:42.010 align:start position:0% once that's there we'll start receiving 00:07:42.010 --> 00:07:44.930 align:start position:0% once that's there we'll start receiving all<00:07:42.310> of<00:07:42.340> these<00:07:42.550> blocks 00:07:44.930 --> 00:07:44.940 align:start position:0% 00:07:44.940 --> 00:07:47.340 align:start position:0% there<00:07:45.940> you<00:07:46.000> go<00:07:46.180> and<00:07:46.540> you<00:07:46.690> can<00:07:46.840> see<00:07:47.020> like<00:07:47.200> this 00:07:47.340 --> 00:07:47.350 align:start position:0% there you go and you can see like this 00:07:47.350 --> 00:07:48.810 align:start position:0% there you go and you can see like this is<00:07:47.440> like<00:07:47.530> fetching<00:07:48.070> from<00:07:48.190> the<00:07:48.370> real<00:07:48.550> live 00:07:48.810 --> 00:07:48.820 align:start position:0% is like fetching from the real live 00:07:48.820 --> 00:07:50.820 align:start position:0% is like fetching from the real live network<00:07:49.090> it's<00:07:49.630> pulling<00:07:50.200> all<00:07:50.290> the<00:07:50.440> blocks<00:07:50.650> in 00:07:50.820 --> 00:07:50.830 align:start position:0% network it's pulling all the blocks in 00:07:50.830 --> 00:07:54.490 align:start position:0% network it's pulling all the blocks in into<00:07:51.370> the<00:07:51.490> browser 00:07:54.490 --> 00:07:54.500 align:start position:0% 00:07:54.500 --> 00:07:59.730 align:start position:0% [Applause] 00:07:59.730 --> 00:07:59.740 align:start position:0% [Applause] 00:07:59.740 --> 00:08:03.310 align:start position:0% [Applause] awesome<00:08:00.740> so<00:08:00.980> let<00:08:01.940> me<00:08:02.060> explain<00:08:02.360> in<00:08:02.840> a<00:08:03.080> graph 00:08:03.310 --> 00:08:03.320 align:start position:0% awesome so let me explain in a graph 00:08:03.320 --> 00:08:06.340 align:start position:0% awesome so let me explain in a graph what<00:08:03.710> and<00:08:04.070> it<00:08:04.430> keeps<00:08:04.610> going<00:08:04.990> it<00:08:05.990> might<00:08:06.200> take<00:08:06.320> a 00:08:06.340 --> 00:08:06.350 align:start position:0% what and it keeps going it might take a 00:08:06.350 --> 00:08:07.480 align:start position:0% what and it keeps going it might take a while<00:08:06.500> if<00:08:06.710> you<00:08:06.830> have<00:08:06.860> downloaded<00:08:07.310> the 00:08:07.480 --> 00:08:07.490 align:start position:0% while if you have downloaded the 00:08:07.490 --> 00:08:09.070 align:start position:0% while if you have downloaded the blockchain<00:08:07.700> before<00:08:08.120> you<00:08:08.390> know<00:08:08.510> you<00:08:08.960> might 00:08:09.070 --> 00:08:09.080 align:start position:0% blockchain before you know you might 00:08:09.080 --> 00:08:14.310 align:start position:0% blockchain before you know you might know<00:08:09.200> that<00:08:09.230> can<00:08:09.710> you<00:08:09.860> go<00:08:09.980> back<00:08:10.100> to<00:08:10.160> the<00:08:10.280> slides 00:08:14.310 --> 00:08:14.320 align:start position:0% 00:08:14.320 --> 00:08:20.270 align:start position:0% okay 00:08:20.270 --> 00:08:20.280 align:start position:0% 00:08:20.280 --> 00:08:22.020 align:start position:0% [Music] 00:08:22.020 --> 00:08:22.030 align:start position:0% [Music] 00:08:22.030 --> 00:08:27.520 align:start position:0% [Music] okay<00:08:23.030> thank<00:08:23.570> you<00:08:23.600> okay 00:08:27.520 --> 00:08:27.530 align:start position:0% 00:08:27.530 --> 00:08:29.470 align:start position:0% so<00:08:27.740> what<00:08:28.160> is<00:08:28.280> happening<00:08:28.640> so<00:08:28.760> we<00:08:28.880> know<00:08:29.000> we<00:08:29.360> have 00:08:29.470 --> 00:08:29.480 align:start position:0% so what is happening so we know we have 00:08:29.480 --> 00:08:31.300 align:start position:0% so what is happening so we know we have the<00:08:29.660> acuity<00:08:29.930> met<00:08:30.170> work<00:08:30.350> that<00:08:30.620> already<00:08:30.920> exists 00:08:31.300 --> 00:08:31.310 align:start position:0% the acuity met work that already exists 00:08:31.310 --> 00:08:33.490 align:start position:0% the acuity met work that already exists and<00:08:31.460> pretty<00:08:31.820> well<00:08:31.940> connected<00:08:32.210> to<00:08:32.599> their<00:08:33.260> field 00:08:33.490 --> 00:08:33.500 align:start position:0% and pretty well connected to their field 00:08:33.500 --> 00:08:37.149 align:start position:0% and pretty well connected to their field of<00:08:33.560> view<00:08:33.710> and<00:08:33.890> then<00:08:34.610> we<00:08:35.200> added<00:08:36.200> this<00:08:36.320> Goethe 00:08:37.149 --> 00:08:37.159 align:start position:0% of view and then we added this Goethe 00:08:37.159 --> 00:08:39.480 align:start position:0% of view and then we added this Goethe Leonel<00:08:37.460> patched<00:08:37.909> with 00:08:39.480 --> 00:08:39.490 align:start position:0% Leonel patched with 00:08:39.490 --> 00:08:41.649 align:start position:0% Leonel patched with we<00:08:40.490> peer-to-peer<00:08:40.729> so<00:08:41.180> that<00:08:41.330> does<00:08:41.419> like<00:08:41.539> a 00:08:41.649 --> 00:08:41.659 align:start position:0% we peer-to-peer so that does like a 00:08:41.659 --> 00:08:44.020 align:start position:0% we peer-to-peer so that does like a presence<00:08:42.050> on<00:08:42.200> double<00:08:42.440> p2p<00:08:42.770> Network<00:08:43.070> and<00:08:43.250> then 00:08:44.020 --> 00:08:44.030 align:start position:0% presence on double p2p Network and then 00:08:44.030 --> 00:08:46.200 align:start position:0% presence on double p2p Network and then we<00:08:44.420> throw<00:08:44.630> the<00:08:44.840> node.js<00:08:45.080> snails 00:08:46.200 --> 00:08:46.210 align:start position:0% we throw the node.js snails 00:08:46.210 --> 00:08:48.810 align:start position:0% we throw the node.js snails running<00:08:47.210> loop<00:08:47.360> peer-to-peer<00:08:47.510> as<00:08:47.810> well<00:08:48.020> and 00:08:48.810 --> 00:08:48.820 align:start position:0% running loop peer-to-peer as well and 00:08:48.820 --> 00:08:52.300 align:start position:0% running loop peer-to-peer as well and then<00:08:49.820> we<00:08:50.000> have<00:08:50.270> our<00:08:50.720> browser<00:08:51.080> that<00:08:51.740> connects 00:08:52.300 --> 00:08:52.310 align:start position:0% then we have our browser that connects 00:08:52.310 --> 00:08:54.880 align:start position:0% then we have our browser that connects to<00:08:52.430> this<00:08:52.550> node.js<00:08:52.820> know<00:08:53.180> that<00:08:53.710> connects<00:08:54.710> to 00:08:54.880 --> 00:08:54.890 align:start position:0% to this node.js know that connects to 00:08:54.890 --> 00:08:56.520 align:start position:0% to this node.js know that connects to the<00:08:55.010> rest<00:08:55.190> of<00:08:55.250> the<00:08:55.340> network<00:08:55.490> to<00:08:55.790> the<00:08:55.820> other 00:08:56.520 --> 00:08:56.530 align:start position:0% the rest of the network to the other 00:08:56.530 --> 00:09:00.370 align:start position:0% the rest of the network to the other go<00:08:57.530> Jess<00:08:58.130> node<00:08:58.430> good<00:08:58.910> girl<00:08:59.390> just<00:08:59.420> node<00:08:59.870> to<00:09:00.290> go 00:09:00.370 --> 00:09:00.380 align:start position:0% go Jess node good girl just node to go 00:09:00.380 --> 00:09:01.780 align:start position:0% go Jess node good girl just node to go it<00:09:00.530> through<00:09:00.680> your<00:09:00.830> note<00:09:00.980> so<00:09:01.310> you<00:09:01.340> can<00:09:01.520> see<00:09:01.640> we 00:09:01.780 --> 00:09:01.790 align:start position:0% it through your note so you can see we 00:09:01.790 --> 00:09:03.190 align:start position:0% it through your note so you can see we already<00:09:01.910> like<00:09:02.150> using<00:09:02.360> multiple<00:09:02.780> transports 00:09:03.190 --> 00:09:03.200 align:start position:0% already like using multiple transports 00:09:03.200 --> 00:09:05.230 align:start position:0% already like using multiple transports here<00:09:03.380> like<00:09:03.560> I'm<00:09:03.680> using<00:09:03.860> TCP<00:09:04.310> to<00:09:04.490> connect<00:09:04.760> girl 00:09:05.230 --> 00:09:05.240 align:start position:0% here like I'm using TCP to connect girl 00:09:05.240 --> 00:09:07.420 align:start position:0% here like I'm using TCP to connect girl between<00:09:05.540> node<00:09:06.320> and<00:09:06.680> then<00:09:06.770> I'm<00:09:07.040> using<00:09:07.070> web 00:09:07.420 --> 00:09:07.430 align:start position:0% between node and then I'm using web 00:09:07.430 --> 00:09:10.690 align:start position:0% between node and then I'm using web sockets<00:09:07.610> from<00:09:08.150> nodes<00:09:08.600> to<00:09:08.840> the<00:09:09.200> browser<00:09:10.070> next 00:09:10.690 --> 00:09:10.700 align:start position:0% sockets from nodes to the browser next 00:09:10.700 --> 00:09:12.700 align:start position:0% sockets from nodes to the browser next up<00:09:10.820> like<00:09:11.510> I<00:09:11.690> can<00:09:11.930> connect<00:09:12.320> several<00:09:12.470> browsers 00:09:12.700 --> 00:09:12.710 align:start position:0% up like I can connect several browsers 00:09:12.710 --> 00:09:14.410 align:start position:0% up like I can connect several browsers together<00:09:13.190> right<00:09:13.430> so<00:09:13.610> what<00:09:13.940> I'm<00:09:14.030> going<00:09:14.210> to<00:09:14.270> do 00:09:14.410 --> 00:09:14.420 align:start position:0% together right so what I'm going to do 00:09:14.420 --> 00:09:16.000 align:start position:0% together right so what I'm going to do is<00:09:14.540> just<00:09:14.660> use<00:09:14.930> WebRTC<00:09:15.140> the<00:09:15.770> peer-to-peer 00:09:16.000 --> 00:09:16.010 align:start position:0% is just use WebRTC the peer-to-peer 00:09:16.010 --> 00:09:18.610 align:start position:0% is just use WebRTC the peer-to-peer transport<00:09:16.700> of<00:09:16.820> the<00:09:16.970> browser<00:09:17.180> and<00:09:17.510> I<00:09:18.050> just<00:09:18.350> put 00:09:18.610 --> 00:09:18.620 align:start position:0% transport of the browser and I just put 00:09:18.620 --> 00:09:20.680 align:start position:0% transport of the browser and I just put it<00:09:18.770> on<00:09:18.860> top<00:09:18.980> what<00:09:19.190> I<00:09:19.220> can<00:09:19.400> do<00:09:19.520> is<00:09:19.700> I<00:09:20.060> can<00:09:20.270> connect 00:09:20.680 --> 00:09:20.690 align:start position:0% it on top what I can do is I can connect 00:09:20.690 --> 00:09:22.180 align:start position:0% it on top what I can do is I can connect the<00:09:20.810> browser<00:09:20.990> again<00:09:21.320> to<00:09:21.500> the<00:09:21.620> girl<00:09:21.800> with<00:09:22.040> your 00:09:22.180 --> 00:09:22.190 align:start position:0% the browser again to the girl with your 00:09:22.190 --> 00:09:25.270 align:start position:0% the browser again to the girl with your note<00:09:22.400> and<00:09:22.610> this<00:09:23.360> way<00:09:23.540> like<00:09:23.930> any<00:09:24.500> browser<00:09:24.890> that 00:09:25.270 --> 00:09:25.280 align:start position:0% note and this way like any browser that 00:09:25.280 --> 00:09:28.360 align:start position:0% note and this way like any browser that has<00:09:25.640> a<00:09:26.510> common<00:09:27.050> transport<00:09:27.500> can<00:09:27.650> dial<00:09:27.890> to 00:09:28.360 --> 00:09:28.370 align:start position:0% has a common transport can dial to 00:09:28.370 --> 00:09:30.100 align:start position:0% has a common transport can dial to another<00:09:28.970> nail<00:09:29.150> that<00:09:29.450> supports<00:09:29.930> we 00:09:30.100 --> 00:09:30.110 align:start position:0% another nail that supports we 00:09:30.110 --> 00:09:32.110 align:start position:0% another nail that supports we peer-to-peer<00:09:30.800> this<00:09:31.430> is<00:09:31.550> pretty<00:09:31.730> exciting 00:09:32.110 --> 00:09:32.120 align:start position:0% peer-to-peer this is pretty exciting 00:09:32.120 --> 00:09:33.940 align:start position:0% peer-to-peer this is pretty exciting like<00:09:32.240> this<00:09:32.630> means<00:09:32.810> like<00:09:32.930> we<00:09:33.110> can<00:09:33.260> have<00:09:33.410> finally 00:09:33.940 --> 00:09:33.950 align:start position:0% like this means like we can have finally 00:09:33.950 --> 00:09:36.490 align:start position:0% like this means like we can have finally it<00:09:34.280> helium<00:09:34.820> in<00:09:35.030> the<00:09:35.210> browser<00:09:35.450> running<00:09:36.170> like 00:09:36.490 --> 00:09:36.500 align:start position:0% it helium in the browser running like 00:09:36.500 --> 00:09:38.230 align:start position:0% it helium in the browser running like fully<00:09:36.830> three<00:09:37.010> nodes<00:09:37.280> and<00:09:37.520> it's<00:09:37.820> just<00:09:38.000> a<00:09:38.120> little 00:09:38.230 --> 00:09:38.240 align:start position:0% fully three nodes and it's just a little 00:09:38.240 --> 00:09:39.850 align:start position:0% fully three nodes and it's just a little browser<00:09:38.510> is<00:09:38.750> basically<00:09:39.050> any<00:09:39.200> device<00:09:39.500> with<00:09:39.800> any 00:09:39.850 --> 00:09:39.860 align:start position:0% browser is basically any device with any 00:09:39.860 --> 00:09:41.530 align:start position:0% browser is basically any device with any network<00:09:40.070> capabilities<00:09:40.850> the<00:09:41.030> network<00:09:41.360> is<00:09:41.510> not 00:09:41.530 --> 00:09:41.540 align:start position:0% network capabilities the network is not 00:09:41.540 --> 00:09:44.440 align:start position:0% network capabilities the network is not the<00:09:42.260> problem<00:09:42.650> anymore<00:09:42.710> I<00:09:43.220> would<00:09:43.760> like<00:09:43.970> to<00:09:44.210> give 00:09:44.440 --> 00:09:44.450 align:start position:0% the problem anymore I would like to give 00:09:44.450 --> 00:09:46.660 align:start position:0% the problem anymore I would like to give a<00:09:44.750> huge<00:09:45.170> shout<00:09:45.470> to<00:09:45.680> Martin<00:09:46.040> because<00:09:46.430> Martin 00:09:46.660 --> 00:09:46.670 align:start position:0% a huge shout to Martin because Martin 00:09:46.670 --> 00:09:48.400 align:start position:0% a huge shout to Martin because Martin basically<00:09:47.060> did<00:09:47.360> all<00:09:47.510> of<00:09:47.630> the<00:09:47.870> magic<00:09:48.260> of 00:09:48.400 --> 00:09:48.410 align:start position:0% basically did all of the magic of 00:09:48.410 --> 00:09:53.769 align:start position:0% basically did all of the magic of getting<00:09:48.740> aetherium<00:09:49.100> running<00:09:49.490> on<00:09:49.670> the<00:09:50.120> browser 00:09:53.769 --> 00:09:53.779 align:start position:0% 00:09:53.779 --> 00:09:57.480 align:start position:0% I 00:09:57.480 --> 00:09:57.490 align:start position:0% 00:09:57.490 --> 00:10:00.100 align:start position:0% just<00:09:58.490> had<00:09:58.639> to<00:09:58.759> plug<00:09:59.180> the<00:09:59.269> wires<00:09:59.449> together<00:09:59.750> that 00:10:00.100 --> 00:10:00.110 align:start position:0% just had to plug the wires together that 00:10:00.110 --> 00:10:02.259 align:start position:0% just had to plug the wires together that was<00:10:00.259> easy<00:10:00.769> thank<00:10:01.550> you<00:10:01.610> so<00:10:01.730> much<00:10:01.790> for<00:10:02.029> all<00:10:02.120> the 00:10:02.259 --> 00:10:02.269 align:start position:0% was easy thank you so much for all the 00:10:02.269 --> 00:10:04.749 align:start position:0% was easy thank you so much for all the wealth<00:10:02.449> and<00:10:02.689> like<00:10:03.439> what<00:10:04.069> you've<00:10:04.250> seen<00:10:04.399> here 00:10:04.749 --> 00:10:04.759 align:start position:0% wealth and like what you've seen here 00:10:04.759 --> 00:10:06.519 align:start position:0% wealth and like what you've seen here was<00:10:04.939> basically<00:10:05.300> like<00:10:05.750> a<00:10:05.930> couple<00:10:06.230> of<00:10:06.319> nights 00:10:06.519 --> 00:10:06.529 align:start position:0% was basically like a couple of nights 00:10:06.529 --> 00:10:08.290 align:start position:0% was basically like a couple of nights hacking<00:10:07.009> it<00:10:07.370> was<00:10:07.550> actually<00:10:07.850> very<00:10:07.910> impressive 00:10:08.290 --> 00:10:08.300 align:start position:0% hacking it was actually very impressive 00:10:08.300 --> 00:10:10.869 align:start position:0% hacking it was actually very impressive oh<00:10:08.629> it<00:10:09.019> was<00:10:09.170> so<00:10:09.350> easy<00:10:09.379> to<00:10:10.160> attach<00:10:10.370> we<00:10:10.610> peer<00:10:10.790> to 00:10:10.869 --> 00:10:10.879 align:start position:0% oh it was so easy to attach we peer to 00:10:10.879 --> 00:10:13.540 align:start position:0% oh it was so easy to attach we peer to peer<00:10:11.060> to<00:10:11.300> go<00:10:11.600> with<00:10:11.750> helium<00:10:12.079> and<00:10:12.319> to<00:10:12.740> bring<00:10:12.980> the 00:10:13.540 --> 00:10:13.550 align:start position:0% peer to go with helium and to bring the 00:10:13.550 --> 00:10:15.280 align:start position:0% peer to go with helium and to bring the blocks<00:10:13.790> to<00:10:14.029> the<00:10:14.060> browser<00:10:14.389> and<00:10:14.540> run<00:10:14.870> them<00:10:15.110> on 00:10:15.280 --> 00:10:15.290 align:start position:0% blocks to the browser and run them on 00:10:15.290 --> 00:10:19.420 align:start position:0% blocks to the browser and run them on the<00:10:15.529> TMJ<00:10:15.800> SVM<00:10:16.370> it's<00:10:16.850> pretty<00:10:17.029> exciting<00:10:17.329> so<00:10:18.430> we 00:10:19.420 --> 00:10:19.430 align:start position:0% the TMJ SVM it's pretty exciting so we 00:10:19.430 --> 00:10:22.030 align:start position:0% the TMJ SVM it's pretty exciting so we will<00:10:19.639> continue<00:10:19.819> pursuit<00:10:20.509> this<00:10:20.810> endeavor<00:10:21.350> you 00:10:22.030 --> 00:10:22.040 align:start position:0% will continue pursuit this endeavor you 00:10:22.040 --> 00:10:24.400 align:start position:0% will continue pursuit this endeavor you can<00:10:22.189> follow<00:10:22.399> the<00:10:23.269> development<00:10:23.839> on<00:10:24.050> the<00:10:24.290> leap 00:10:24.400 --> 00:10:24.410 align:start position:0% can follow the development on the leap 00:10:24.410 --> 00:10:26.439 align:start position:0% can follow the development on the leap UTP<00:10:24.709> organization<00:10:25.160> on<00:10:25.250> gear<00:10:25.430> the<00:10:26.060> deaf<00:10:26.240> ear<00:10:26.420> to 00:10:26.439 --> 00:10:26.449 align:start position:0% UTP organization on gear the deaf ear to 00:10:26.449 --> 00:10:27.929 align:start position:0% UTP organization on gear the deaf ear to peer 00:10:27.929 --> 00:10:27.939 align:start position:0% peer 00:10:27.939 --> 00:10:30.550 align:start position:0% peer development<00:10:28.939> on<00:10:29.120> the<00:10:29.269> theorem<00:10:29.569> org<00:10:29.750> and<00:10:30.050> you 00:10:30.550 --> 00:10:30.560 align:start position:0% development on the theorem org and you 00:10:30.560 --> 00:10:32.619 align:start position:0% development on the theorem org and you can<00:10:30.740> check<00:10:30.980> all<00:10:31.220> of<00:10:31.250> those<00:10:31.459> examples<00:10:31.819> all<00:10:32.360> that 00:10:32.619 --> 00:10:32.629 align:start position:0% can check all of those examples all that 00:10:32.629 --> 00:10:35.499 align:start position:0% can check all of those examples all that demo<00:10:32.930> on<00:10:33.170> a<00:10:33.230> repo<00:10:34.040> called<00:10:34.370> jazz<00:10:34.730> idiom<00:10:35.060> with 00:10:35.499 --> 00:10:35.509 align:start position:0% demo on a repo called jazz idiom with 00:10:35.509 --> 00:10:37.720 align:start position:0% demo on a repo called jazz idiom with peer-to-peer<00:10:35.689> I<00:10:36.079> can<00:10:36.410> post<00:10:36.680> the<00:10:37.100> links<00:10:37.550> after 00:10:37.720 --> 00:10:37.730 align:start position:0% peer-to-peer I can post the links after 00:10:37.730 --> 00:10:39.369 align:start position:0% peer-to-peer I can post the links after in<00:10:38.060> Twitter<00:10:38.300> if<00:10:38.569> someone<00:10:38.839> is<00:10:38.930> interested<00:10:39.079> to 00:10:39.369 --> 00:10:39.379 align:start position:0% in Twitter if someone is interested to 00:10:39.379 --> 00:10:41.410 align:start position:0% in Twitter if someone is interested to check<00:10:39.410> it<00:10:39.620> out<00:10:39.680> that's<00:10:40.220> awesome<00:10:40.670> thank<00:10:41.300> you<00:10:41.360> so 00:10:41.410 --> 00:10:41.420 align:start position:0% check it out that's awesome thank you so 00:10:41.420 --> 00:10:48.110 align:start position:0% check it out that's awesome thank you so much 00:10:48.110 --> 00:10:48.120 align:start position:0% 00:10:48.120 --> 00:10:51.460 align:start position:0% [Music]