WEBVTT Kind: captions Language: en 00:00:14.919 --> 00:00:19.330 align:start position:0% so<00:00:16.960> unlike<00:00:17.960> many<00:00:18.410> of<00:00:18.530> the<00:00:18.560> crypto<00:00:18.920> projects 00:00:19.330 --> 00:00:19.340 align:start position:0% so unlike many of the crypto projects 00:00:19.340 --> 00:00:21.250 align:start position:0% so unlike many of the crypto projects out<00:00:19.460> there<00:00:19.490> aetherium<00:00:20.450> isn't<00:00:20.990> really<00:00:21.170> an 00:00:21.250 --> 00:00:21.260 align:start position:0% out there aetherium isn't really an 00:00:21.260 --> 00:00:23.110 align:start position:0% out there aetherium isn't really an end-to-end<00:00:21.530> product<00:00:22.070> it's<00:00:22.280> it<00:00:22.520> has<00:00:22.940> always 00:00:23.110 --> 00:00:23.120 align:start position:0% end-to-end product it's it has always 00:00:23.120 --> 00:00:25.000 align:start position:0% end-to-end product it's it has always been<00:00:23.420> a<00:00:23.480> platform<00:00:23.720> by<00:00:24.170> developers<00:00:24.710> for 00:00:25.000 --> 00:00:25.010 align:start position:0% been a platform by developers for 00:00:25.010 --> 00:00:27.880 align:start position:0% been a platform by developers for developers<00:00:25.040> and<00:00:25.910> as<00:00:26.240> such<00:00:26.450> our<00:00:27.110> kind<00:00:27.530> of<00:00:27.620> our 00:00:27.880 --> 00:00:27.890 align:start position:0% developers and as such our kind of our 00:00:27.890 --> 00:00:30.250 align:start position:0% developers and as such our kind of our primary<00:00:28.370> task<00:00:28.700> is<00:00:29.000> to<00:00:29.060> make<00:00:29.180> developers<00:00:29.540> happy 00:00:30.250 --> 00:00:30.260 align:start position:0% primary task is to make developers happy 00:00:30.260 --> 00:00:32.290 align:start position:0% primary task is to make developers happy so<00:00:30.710> that<00:00:30.860> in<00:00:31.310> their<00:00:31.550> turn<00:00:31.760> there<00:00:31.940> can<00:00:32.119> make 00:00:32.290 --> 00:00:32.300 align:start position:0% so that in their turn there can make 00:00:32.300 --> 00:00:36.010 align:start position:0% so that in their turn there can make their<00:00:32.450> end<00:00:32.570> users<00:00:32.899> happy<00:00:33.520> now<00:00:34.520> for<00:00:35.480> to<00:00:35.750> achieve 00:00:36.010 --> 00:00:36.020 align:start position:0% their end users happy now for to achieve 00:00:36.020 --> 00:00:38.680 align:start position:0% their end users happy now for to achieve this<00:00:36.260> one<00:00:36.710> of<00:00:36.800> my<00:00:37.790> opinion<00:00:38.180> one<00:00:38.270> of<00:00:38.360> our<00:00:38.450> most 00:00:38.680 --> 00:00:38.690 align:start position:0% this one of my opinion one of our most 00:00:38.690 --> 00:00:40.660 align:start position:0% this one of my opinion one of our most important<00:00:39.140> roles<00:00:39.350> is<00:00:39.530> to<00:00:39.650> either<00:00:39.800> aid<00:00:40.310> the 00:00:40.660 --> 00:00:40.670 align:start position:0% important roles is to either aid the 00:00:40.670 --> 00:00:42.460 align:start position:0% important roles is to either aid the existing<00:00:41.120> tooling<00:00:41.540> developer<00:00:42.020> tooling<00:00:42.230> out 00:00:42.460 --> 00:00:42.470 align:start position:0% existing tooling developer tooling out 00:00:42.470 --> 00:00:45.040 align:start position:0% existing tooling developer tooling out in<00:00:42.650> the<00:00:42.710> community<00:00:43.160> or<00:00:43.670> maybe<00:00:44.030> fund<00:00:44.420> or<00:00:44.690> create 00:00:45.040 --> 00:00:45.050 align:start position:0% in the community or maybe fund or create 00:00:45.050 --> 00:00:46.750 align:start position:0% in the community or maybe fund or create new<00:00:45.079> ones<00:00:45.320> that<00:00:45.739> the<00:00:45.860> ecosystem<00:00:46.370> is<00:00:46.460> currently 00:00:46.750 --> 00:00:46.760 align:start position:0% new ones that the ecosystem is currently 00:00:46.760 --> 00:00:49.360 align:start position:0% new ones that the ecosystem is currently lacking<00:00:46.970> and<00:00:47.660> my<00:00:47.780> talk<00:00:47.989> would<00:00:48.170> be<00:00:48.230> about<00:00:49.160> one 00:00:49.360 --> 00:00:49.370 align:start position:0% lacking and my talk would be about one 00:00:49.370 --> 00:00:51.430 align:start position:0% lacking and my talk would be about one such<00:00:49.610> tool<00:00:49.880> that<00:00:50.090> we<00:00:50.239> wrote<00:00:50.420> but<00:00:50.989> before<00:00:51.320> we 00:00:51.430 --> 00:00:51.440 align:start position:0% such tool that we wrote but before we 00:00:51.440 --> 00:00:53.049 align:start position:0% such tool that we wrote but before we dive<00:00:51.590> in<00:00:51.800> let's<00:00:52.010> see<00:00:52.130> what<00:00:52.280> the<00:00:52.399> actual<00:00:52.850> pain 00:00:53.049 --> 00:00:53.059 align:start position:0% dive in let's see what the actual pain 00:00:53.059 --> 00:00:56.319 align:start position:0% dive in let's see what the actual pain point<00:00:53.329> are<00:00:53.570> usually<00:00:54.500> when<00:00:55.190> the<00:00:55.340> developers<00:00:56.120> to 00:00:56.319 --> 00:00:56.329 align:start position:0% point are usually when the developers to 00:00:56.329 --> 00:00:58.360 align:start position:0% point are usually when the developers to approach<00:00:56.690> it<00:00:56.870> even<00:00:57.110> for<00:00:57.230> the<00:00:57.320> first<00:00:57.350> time<00:00:57.860> they 00:00:58.360 --> 00:00:58.370 align:start position:0% approach it even for the first time they 00:00:58.370 --> 00:01:00.100 align:start position:0% approach it even for the first time they start<00:00:58.640> playing<00:00:58.880> around<00:00:59.030> with<00:00:59.270> remix<00:00:59.780> it's 00:01:00.100 --> 00:01:00.110 align:start position:0% start playing around with remix it's 00:01:00.110 --> 00:01:02.380 align:start position:0% start playing around with remix it's browser<00:01:00.380> solidity<00:01:01.130> playground<00:01:01.670> they<00:01:02.059> get<00:01:02.270> the 00:01:02.380 --> 00:01:02.390 align:start position:0% browser solidity playground they get the 00:01:02.390 --> 00:01:04.539 align:start position:0% browser solidity playground they get the hang<00:01:02.540> of<00:01:02.660> solidity<00:01:03.140> they<00:01:04.009> start<00:01:04.339> prototyping 00:01:04.539 --> 00:01:04.549 align:start position:0% hang of solidity they start prototyping 00:01:04.549 --> 00:01:06.730 align:start position:0% hang of solidity they start prototyping their<00:01:05.059> contract<00:01:05.540> now<00:01:05.990> unfortunately<00:01:06.620> quite 00:01:06.730 --> 00:01:06.740 align:start position:0% their contract now unfortunately quite 00:01:06.740 --> 00:01:09.010 align:start position:0% their contract now unfortunately quite fast<00:01:07.130> they<00:01:07.280> realize<00:01:07.700> that<00:01:07.840> developing<00:01:08.840> in<00:01:08.960> a 00:01:09.010 --> 00:01:09.020 align:start position:0% fast they realize that developing in a 00:01:09.020 --> 00:01:11.260 align:start position:0% fast they realize that developing in a web<00:01:09.140> browser<00:01:09.320> is<00:01:09.560> cumbersome<00:01:10.070> so<00:01:10.880> they<00:01:11.030> switch 00:01:11.260 --> 00:01:11.270 align:start position:0% web browser is cumbersome so they switch 00:01:11.270 --> 00:01:12.760 align:start position:0% web browser is cumbersome so they switch to<00:01:11.299> more<00:01:11.570> sophisticated<00:01:11.840> tools<00:01:12.500> such<00:01:12.740> as 00:01:12.760 --> 00:01:12.770 align:start position:0% to more sophisticated tools such as 00:01:12.770 --> 00:01:14.920 align:start position:0% to more sophisticated tools such as truffle<00:01:13.340> which<00:01:13.880> can<00:01:14.120> do<00:01:14.270> automated 00:01:14.920 --> 00:01:14.930 align:start position:0% truffle which can do automated 00:01:14.930 --> 00:01:19.590 align:start position:0% truffle which can do automated repeatable<00:01:15.799> testing<00:01:16.250> and<00:01:17.530> also<00:01:18.530> aided<00:01:18.860> by 00:01:19.590 --> 00:01:19.600 align:start position:0% repeatable testing and also aided by 00:01:19.600 --> 00:01:21.880 align:start position:0% repeatable testing and also aided by proof<00:01:20.600> of<00:01:20.750> authority<00:01:21.140> change<00:01:21.380> or<00:01:21.560> instant 00:01:21.880 --> 00:01:21.890 align:start position:0% proof of authority change or instant 00:01:21.890 --> 00:01:24.010 align:start position:0% proof of authority change or instant transactions<00:01:22.580> now<00:01:23.150> after<00:01:23.390> developers 00:01:24.010 --> 00:01:24.020 align:start position:0% transactions now after developers 00:01:24.020 --> 00:01:25.450 align:start position:0% transactions now after developers actually<00:01:24.200> finished<00:01:24.680> writing<00:01:25.040> their<00:01:25.190> code 00:01:25.450 --> 00:01:25.460 align:start position:0% actually finished writing their code 00:01:25.460 --> 00:01:27.190 align:start position:0% actually finished writing their code usually<00:01:25.760> the<00:01:26.270> procedure<00:01:26.690> is<00:01:26.930> that<00:01:26.960> they 00:01:27.190 --> 00:01:27.200 align:start position:0% usually the procedure is that they 00:01:27.200 --> 00:01:29.440 align:start position:0% usually the procedure is that they deploy<00:01:27.500> it<00:01:27.650> on<00:01:27.770> a<00:01:27.799> test<00:01:28.070> net<00:01:28.280> either<00:01:28.820> robson<00:01:29.330> or 00:01:29.440 --> 00:01:29.450 align:start position:0% deploy it on a test net either robson or 00:01:29.450 --> 00:01:31.660 align:start position:0% deploy it on a test net either robson or an<00:01:29.659> alternative<00:01:30.500> because<00:01:31.250> that's<00:01:31.520> really 00:01:31.660 --> 00:01:31.670 align:start position:0% an alternative because that's really 00:01:31.670 --> 00:01:34.090 align:start position:0% an alternative because that's really nice<00:01:31.880> it's<00:01:32.180> a<00:01:32.360> real<00:01:32.869> world<00:01:33.140> environment<00:01:33.290> many 00:01:34.090 --> 00:01:34.100 align:start position:0% nice it's a real world environment many 00:01:34.100 --> 00:01:37.780 align:start position:0% nice it's a real world environment many users<00:01:34.549> etc<00:01:35.210> now<00:01:36.200> the<00:01:36.470> problem<00:01:36.890> is<00:01:37.010> that<00:01:37.280> this 00:01:37.780 --> 00:01:37.790 align:start position:0% users etc now the problem is that this 00:01:37.790 --> 00:01:40.120 align:start position:0% users etc now the problem is that this perfect<00:01:38.330> testing<00:01:38.780> environment<00:01:39.380> often<00:01:39.920> goes 00:01:40.120 --> 00:01:40.130 align:start position:0% perfect testing environment often goes 00:01:40.130 --> 00:01:42.910 align:start position:0% perfect testing environment often goes belly-up<00:01:40.549> and<00:01:40.939> the<00:01:41.689> reason<00:01:41.990> is<00:01:42.110> one<00:01:42.740> of<00:01:42.830> the 00:01:42.910 --> 00:01:42.920 align:start position:0% belly-up and the reason is one of the 00:01:42.920 --> 00:01:44.410 align:start position:0% belly-up and the reason is one of the reasons<00:01:43.189> is<00:01:43.310> that<00:01:43.340> the<00:01:43.610> test<00:01:43.850> networks<00:01:44.210> are 00:01:44.410 --> 00:01:44.420 align:start position:0% reasons is that the test networks are 00:01:44.420 --> 00:01:47.020 align:start position:0% reasons is that the test networks are can<00:01:44.689> be<00:01:44.840> really<00:01:45.049> heavy<00:01:45.400> either<00:01:46.400> due<00:01:46.670> to<00:01:46.729> spam 00:01:47.020 --> 00:01:47.030 align:start position:0% can be really heavy either due to spam 00:01:47.030 --> 00:01:48.880 align:start position:0% can be really heavy either due to spam attacks<00:01:47.360> or<00:01:47.659> to<00:01:47.900> large<00:01:48.080> projects<00:01:48.710> such<00:01:48.860> as 00:01:48.880 --> 00:01:48.890 align:start position:0% attacks or to large projects such as 00:01:48.890 --> 00:01:52.090 align:start position:0% attacks or to large projects such as raid<00:01:49.220> on<00:01:49.400> doing<00:01:49.850> intensive<00:01:50.330> tests<00:01:50.830> these<00:01:51.830> can 00:01:52.090 --> 00:01:52.100 align:start position:0% raid on doing intensive tests these can 00:01:52.100 --> 00:01:54.429 align:start position:0% raid on doing intensive tests these can be<00:01:52.280> unstable<00:01:52.729> from<00:01:53.090> time<00:01:53.299> to<00:01:53.450> time<00:01:53.479> usually 00:01:54.429 --> 00:01:54.439 align:start position:0% be unstable from time to time usually 00:01:54.439 --> 00:01:56.830 align:start position:0% be unstable from time to time usually because<00:01:54.740> somebody<00:01:55.040> figures<00:01:55.700> it<00:01:56.299> would<00:01:56.509> be<00:01:56.630> fun 00:01:56.830 --> 00:01:56.840 align:start position:0% because somebody figures it would be fun 00:01:56.840 --> 00:02:00.490 align:start position:0% because somebody figures it would be fun to<00:01:57.049> reorganize<00:01:57.799> the<00:01:57.829> chain<00:01:58.189> and<00:01:58.780> lastly<00:01:59.780> it 00:02:00.490 --> 00:02:00.500 align:start position:0% to reorganize the chain and lastly it 00:02:00.500 --> 00:02:04.450 align:start position:0% to reorganize the chain and lastly it can<00:02:00.860> often<00:02:01.100> be<00:02:01.810> unfriendly<00:02:02.810> because<00:02:03.530> you<00:02:04.220> have 00:02:04.450 --> 00:02:04.460 align:start position:0% can often be unfriendly because you have 00:02:04.460 --> 00:02:05.830 align:start position:0% can often be unfriendly because you have this<00:02:04.640> awesome<00:02:04.820> project<00:02:05.150> you<00:02:05.390> want<00:02:05.540> to<00:02:05.600> deploy 00:02:05.830 --> 00:02:05.840 align:start position:0% this awesome project you want to deploy 00:02:05.840 --> 00:02:07.390 align:start position:0% this awesome project you want to deploy but<00:02:05.930> you<00:02:06.259> don't<00:02:06.409> have<00:02:06.560> tests<00:02:06.799> either<00:02:07.189> and 00:02:07.390 --> 00:02:07.400 align:start position:0% but you don't have tests either and 00:02:07.400 --> 00:02:10.600 align:start position:0% but you don't have tests either and that's<00:02:07.729> knowing<00:02:08.000> and<00:02:08.450> the<00:02:09.379> truth<00:02:09.619> is<00:02:09.800> that<00:02:09.830> if 00:02:10.600 --> 00:02:10.610 align:start position:0% that's knowing and the truth is that if 00:02:10.610 --> 00:02:12.610 align:start position:0% that's knowing and the truth is that if you<00:02:10.819> are<00:02:10.940> a<00:02:11.000> small<00:02:11.300> project<00:02:11.540> than<00:02:12.200> running 00:02:12.610 --> 00:02:12.620 align:start position:0% you are a small project than running 00:02:12.620 --> 00:02:13.500 align:start position:0% you are a small project than running tests 00:02:13.500 --> 00:02:13.510 align:start position:0% tests 00:02:13.510 --> 00:02:15.180 align:start position:0% tests on<00:02:13.659> the<00:02:13.750> test<00:02:13.930> that<00:02:14.050> is<00:02:14.170> fine<00:02:14.440> but<00:02:14.860> if<00:02:14.980> you're<00:02:15.099> a 00:02:15.180 --> 00:02:15.190 align:start position:0% on the test that is fine but if you're a 00:02:15.190 --> 00:02:17.399 align:start position:0% on the test that is fine but if you're a bit<00:02:15.340> larger<00:02:15.730> projects<00:02:16.209> such<00:02:16.330> as<00:02:16.360> radon<00:02:17.230> or 00:02:17.399 --> 00:02:17.409 align:start position:0% bit larger projects such as radon or 00:02:17.409 --> 00:02:18.690 align:start position:0% bit larger projects such as radon or maybe<00:02:17.590> have<00:02:17.769> many<00:02:17.980> projects<00:02:18.459> such<00:02:18.580> as 00:02:18.690 --> 00:02:18.700 align:start position:0% maybe have many projects such as 00:02:18.700 --> 00:02:22.470 align:start position:0% maybe have many projects such as consensus<00:02:19.390> or<00:02:19.900> perhaps<00:02:21.090> you<00:02:22.090> want<00:02:22.209> to<00:02:22.330> run<00:02:22.450> a 00:02:22.470 --> 00:02:22.480 align:start position:0% consensus or perhaps you want to run a 00:02:22.480 --> 00:02:24.869 align:start position:0% consensus or perhaps you want to run a hackathon<00:02:22.810> then<00:02:23.319> the<00:02:24.099> life<00:02:24.250> does<00:02:24.549> not<00:02:24.760> or 00:02:24.869 --> 00:02:24.879 align:start position:0% hackathon then the life does not or 00:02:24.879 --> 00:02:27.330 align:start position:0% hackathon then the life does not or isn't<00:02:25.239> really<00:02:25.480> ideal<00:02:25.590> so<00:02:26.590> the<00:02:26.709> ideal<00:02:26.920> solution 00:02:27.330 --> 00:02:27.340 align:start position:0% isn't really ideal so the ideal solution 00:02:27.340 --> 00:02:30.180 align:start position:0% isn't really ideal so the ideal solution is<00:02:27.400> actually<00:02:27.790> to<00:02:28.030> run<00:02:28.390> your<00:02:28.659> own<00:02:28.690> network<00:02:29.440> now 00:02:30.180 --> 00:02:30.190 align:start position:0% is actually to run your own network now 00:02:30.190 --> 00:02:32.220 align:start position:0% is actually to run your own network now this<00:02:30.430> might<00:02:30.760> seem<00:02:31.209> like<00:02:31.269> a<00:02:31.510> good<00:02:31.720> idea<00:02:31.870> at<00:02:32.140> the 00:02:32.220 --> 00:02:32.230 align:start position:0% this might seem like a good idea at the 00:02:32.230 --> 00:02:34.020 align:start position:0% this might seem like a good idea at the beginning<00:02:32.349> since<00:02:32.950> its<00:02:33.099> light<00:02:33.280> stable<00:02:33.879> you 00:02:34.020 --> 00:02:34.030 align:start position:0% beginning since its light stable you 00:02:34.030 --> 00:02:35.460 align:start position:0% beginning since its light stable you have<00:02:34.060> unlimited<00:02:34.360> funds<00:02:34.870> you<00:02:35.019> can<00:02:35.140> share<00:02:35.349> with 00:02:35.460 --> 00:02:35.470 align:start position:0% have unlimited funds you can share with 00:02:35.470 --> 00:02:37.589 align:start position:0% have unlimited funds you can share with everybody<00:02:35.769> but<00:02:36.760> when<00:02:37.000> you<00:02:37.090> actually<00:02:37.239> start 00:02:37.589 --> 00:02:37.599 align:start position:0% everybody but when you actually start 00:02:37.599 --> 00:02:40.410 align:start position:0% everybody but when you actually start configuring<00:02:37.959> your<00:02:38.530> private<00:02:39.250> network<00:02:39.420> horror 00:02:40.410 --> 00:02:40.420 align:start position:0% configuring your private network horror 00:02:40.420 --> 00:02:42.479 align:start position:0% configuring your private network horror strikes<00:02:40.870> in<00:02:41.110> so<00:02:41.379> it's<00:02:41.560> actually<00:02:41.860> quite<00:02:42.370> a 00:02:42.479 --> 00:02:42.489 align:start position:0% strikes in so it's actually quite a 00:02:42.489 --> 00:02:44.699 align:start position:0% strikes in so it's actually quite a nightmare<00:02:42.819> to<00:02:43.360> configure<00:02:43.930> because<00:02:44.409> it<00:02:44.530> has 00:02:44.699 --> 00:02:44.709 align:start position:0% nightmare to configure because it has 00:02:44.709 --> 00:02:45.990 align:start position:0% nightmare to configure because it has the<00:02:44.980> zillions<00:02:45.159> of<00:02:45.370> different<00:02:45.489> moving 00:02:45.990 --> 00:02:46.000 align:start position:0% the zillions of different moving 00:02:46.000 --> 00:02:49.559 align:start position:0% the zillions of different moving components<00:02:46.329> and<00:02:46.980> so<00:02:48.030> we've<00:02:49.030> been<00:02:49.180> working<00:02:49.329> for 00:02:49.559 --> 00:02:49.569 align:start position:0% components and so we've been working for 00:02:49.569 --> 00:02:52.559 align:start position:0% components and so we've been working for quite<00:02:50.019> long<00:02:50.049> on<00:02:50.530> a<00:02:50.680> tool<00:02:51.190> called<00:02:51.459> puppet<00:02:51.910> and 00:02:52.559 --> 00:02:52.569 align:start position:0% quite long on a tool called puppet and 00:02:52.569 --> 00:02:53.490 align:start position:0% quite long on a tool called puppet and the<00:02:52.810> goal 00:02:53.490 --> 00:02:53.500 align:start position:0% the goal 00:02:53.500 --> 00:02:55.080 align:start position:0% the goal our<00:02:53.680> primary<00:02:54.129> goal<00:02:54.310> with<00:02:54.579> puppet<00:02:54.879> was 00:02:55.080 --> 00:02:55.090 align:start position:0% our primary goal with puppet was 00:02:55.090 --> 00:02:57.420 align:start position:0% our primary goal with puppet was actually<00:02:55.540> to<00:02:55.750> run<00:02:56.230> the<00:02:56.379> rinkeby<00:02:56.620> test<00:02:56.920> not<00:02:57.129> on 00:02:57.420 --> 00:02:57.430 align:start position:0% actually to run the rinkeby test not on 00:02:57.430 --> 00:02:59.520 align:start position:0% actually to run the rinkeby test not on it<00:02:57.609> but<00:02:58.299> we<00:02:58.450> kind<00:02:58.629> of<00:02:58.690> realized<00:02:59.079> that<00:02:59.200> it<00:02:59.379> will 00:02:59.520 --> 00:02:59.530 align:start position:0% it but we kind of realized that it will 00:02:59.530 --> 00:03:01.380 align:start position:0% it but we kind of realized that it will be<00:02:59.620> an<00:02:59.709> amazing<00:02:59.890> tool<00:03:00.250> for<00:03:00.310> at<00:03:00.879> least<00:03:01.090> we<00:03:01.299> hope 00:03:01.380 --> 00:03:01.390 align:start position:0% be an amazing tool for at least we hope 00:03:01.390 --> 00:03:03.059 align:start position:0% be an amazing tool for at least we hope an<00:03:01.540> amazing<00:03:01.870> tool<00:03:02.019> for<00:03:02.200> other<00:03:02.290> projects<00:03:02.829> too 00:03:03.059 --> 00:03:03.069 align:start position:0% an amazing tool for other projects too 00:03:03.069 --> 00:03:06.150 align:start position:0% an amazing tool for other projects too so<00:03:03.549> we<00:03:03.760> kind<00:03:04.030> of<00:03:04.090> polished<00:03:04.480> it<00:03:04.629> up<00:03:04.750> and<00:03:05.129> gave<00:03:06.129> it 00:03:06.150 --> 00:03:06.160 align:start position:0% so we kind of polished it up and gave it 00:03:06.160 --> 00:03:08.670 align:start position:0% so we kind of polished it up and gave it out<00:03:06.430> to<00:03:06.609> the<00:03:06.700> community<00:03:07.180> and<00:03:07.379> for<00:03:08.379> the<00:03:08.470> rest<00:03:08.590> of 00:03:08.670 --> 00:03:08.680 align:start position:0% out to the community and for the rest of 00:03:08.680 --> 00:03:10.110 align:start position:0% out to the community and for the rest of my<00:03:08.829> talk<00:03:09.010> I'm<00:03:09.220> going<00:03:09.430> to<00:03:09.519> do<00:03:09.670> something<00:03:09.879> really 00:03:10.110 --> 00:03:10.120 align:start position:0% my talk I'm going to do something really 00:03:10.120 --> 00:03:12.300 align:start position:0% my talk I'm going to do something really crazy<00:03:10.359> I<00:03:10.780> would<00:03:10.930> like<00:03:11.470> to<00:03:11.620> demonstrate<00:03:11.769> what 00:03:12.300 --> 00:03:12.310 align:start position:0% crazy I would like to demonstrate what 00:03:12.310 --> 00:03:13.979 align:start position:0% crazy I would like to demonstrate what it<00:03:12.340> takes<00:03:12.670> to<00:03:12.849> actually<00:03:13.239> create<00:03:13.540> an<00:03:13.690> entire 00:03:13.979 --> 00:03:13.989 align:start position:0% it takes to actually create an entire 00:03:13.989 --> 00:03:15.930 align:start position:0% it takes to actually create an entire ethereal<00:03:14.530> network<00:03:14.859> with<00:03:15.099> bells<00:03:15.340> and<00:03:15.489> whistles 00:03:15.930 --> 00:03:15.940 align:start position:0% ethereal network with bells and whistles 00:03:15.940 --> 00:03:24.629 align:start position:0% ethereal network with bells and whistles live<00:03:16.480> on<00:03:16.810> stage<00:03:21.480> so<00:03:22.680> first<00:03:23.680> up<00:03:23.859> if<00:03:24.190> you<00:03:24.340> want<00:03:24.519> to 00:03:24.629 --> 00:03:24.639 align:start position:0% live on stage so first up if you want to 00:03:24.639 --> 00:03:26.009 align:start position:0% live on stage so first up if you want to actually<00:03:24.790> start<00:03:25.000> your<00:03:25.329> ethereal<00:03:25.510> Network 00:03:26.009 --> 00:03:26.019 align:start position:0% actually start your ethereal Network 00:03:26.019 --> 00:03:27.539 align:start position:0% actually start your ethereal Network obviously<00:03:26.680> you<00:03:26.739> need<00:03:26.859> to<00:03:27.040> configure<00:03:27.280> the 00:03:27.539 --> 00:03:27.549 align:start position:0% obviously you need to configure the 00:03:27.549 --> 00:03:29.039 align:start position:0% obviously you need to configure the Genesis<00:03:27.970> block<00:03:28.090> the<00:03:28.419> shared<00:03:28.660> initial 00:03:29.039 --> 00:03:29.049 align:start position:0% Genesis block the shared initial 00:03:29.049 --> 00:03:31.199 align:start position:0% Genesis block the shared initial accounts<00:03:29.530> the<00:03:29.680> balancers<00:03:30.250> and<00:03:30.430> you<00:03:30.970> have<00:03:31.120> to 00:03:31.199 --> 00:03:31.209 align:start position:0% accounts the balancers and you have to 00:03:31.209 --> 00:03:32.819 align:start position:0% accounts the balancers and you have to define<00:03:31.510> what<00:03:31.630> precompiled<00:03:32.290> contracts<00:03:32.709> you 00:03:32.819 --> 00:03:32.829 align:start position:0% define what precompiled contracts you 00:03:32.829 --> 00:03:34.770 align:start position:0% define what precompiled contracts you have<00:03:32.859> what<00:03:33.160> fees<00:03:33.400> they<00:03:33.609> have<00:03:33.849> now<00:03:34.419> there<00:03:34.630> are 00:03:34.770 --> 00:03:34.780 align:start position:0% have what fees they have now there are 00:03:34.780 --> 00:03:36.240 align:start position:0% have what fees they have now there are different<00:03:35.139> for<00:03:35.440> cruise<00:03:35.680> that<00:03:35.889> you<00:03:36.010> need<00:03:36.160> to 00:03:36.240 --> 00:03:36.250 align:start position:0% different for cruise that you need to 00:03:36.250 --> 00:03:38.280 align:start position:0% different for cruise that you need to take<00:03:36.459> care<00:03:36.700> of<00:03:36.760> and<00:03:37.150> if<00:03:37.630> this<00:03:37.750> wasn't<00:03:38.139> horrible 00:03:38.280 --> 00:03:38.290 align:start position:0% take care of and if this wasn't horrible 00:03:38.290 --> 00:03:40.500 align:start position:0% take care of and if this wasn't horrible enough<00:03:38.739> if<00:03:39.459> you<00:03:39.609> have<00:03:39.790> to<00:03:39.940> do<00:03:40.060> this<00:03:40.180> for<00:03:40.419> the 00:03:40.500 --> 00:03:40.510 align:start position:0% enough if you have to do this for the 00:03:40.510 --> 00:03:42.629 align:start position:0% enough if you have to do this for the five<00:03:40.690> primary<00:03:41.019> clients<00:03:41.680> that's<00:03:41.980> about<00:03:42.370> four 00:03:42.629 --> 00:03:42.639 align:start position:0% five primary clients that's about four 00:03:42.639 --> 00:03:44.339 align:start position:0% five primary clients that's about four hundred<00:03:42.730> and<00:03:43.060> fourteen<00:03:43.540> configuration 00:03:44.339 --> 00:03:44.349 align:start position:0% hundred and fourteen configuration 00:03:44.349 --> 00:03:46.890 align:start position:0% hundred and fourteen configuration values<00:03:44.500> and<00:03:45.150> that's<00:03:46.150> just<00:03:46.450> a<00:03:46.569> snippet<00:03:46.720> from 00:03:46.890 --> 00:03:46.900 align:start position:0% values and that's just a snippet from 00:03:46.900 --> 00:03:49.530 align:start position:0% values and that's just a snippet from parity<00:03:47.500> is<00:03:47.560> really<00:03:47.799> expensive<00:03:48.130> list<00:03:48.549> so 00:03:49.530 --> 00:03:49.540 align:start position:0% parity is really expensive list so 00:03:49.540 --> 00:03:51.589 align:start position:0% parity is really expensive list so that's<00:03:49.780> not<00:03:50.590> really<00:03:50.919> a<00:03:50.950> pleasant<00:03:51.370> experience 00:03:51.589 --> 00:03:51.599 align:start position:0% that's not really a pleasant experience 00:03:51.599 --> 00:03:54.960 align:start position:0% that's not really a pleasant experience however<00:03:52.599> if<00:03:53.139> we<00:03:53.500> try<00:03:53.709> puppet<00:03:54.099> now<00:03:54.519> puppet<00:03:54.819> is<00:03:54.940> a 00:03:54.960 --> 00:03:54.970 align:start position:0% however if we try puppet now puppet is a 00:03:54.970 --> 00:03:57.210 align:start position:0% however if we try puppet now puppet is a command-line<00:03:55.690> tool<00:03:56.049> but<00:03:56.620> kind<00:03:57.040> of<00:03:57.129> a 00:03:57.210 --> 00:03:57.220 align:start position:0% command-line tool but kind of a 00:03:57.220 --> 00:03:59.190 align:start position:0% command-line tool but kind of a command-line<00:03:57.639> wizard<00:03:58.030> to<00:03:58.269> help<00:03:58.299> you<00:03:58.599> so<00:03:59.109> the 00:03:59.190 --> 00:03:59.200 align:start position:0% command-line wizard to help you so the 00:03:59.200 --> 00:04:00.390 align:start position:0% command-line wizard to help you so the first<00:03:59.440> thing<00:03:59.590> it<00:03:59.709> just<00:03:59.739> greets<00:04:00.129> you<00:04:00.250> with<00:04:00.340> a 00:04:00.390 --> 00:04:00.400 align:start position:0% first thing it just greets you with a 00:04:00.400 --> 00:04:02.339 align:start position:0% first thing it just greets you with a nice<00:04:00.579> message<00:04:00.970> and<00:04:01.120> asks<00:04:01.450> what<00:04:01.660> network<00:04:02.200> would 00:04:02.339 --> 00:04:02.349 align:start position:0% nice message and asks what network would 00:04:02.349 --> 00:04:04.470 align:start position:0% nice message and asks what network would you<00:04:02.440> like<00:04:02.590> to<00:04:02.739> manage<00:04:02.919> we<00:04:03.340> just<00:04:03.639> type<00:04:03.819> Def<00:04:04.060> Con 00:04:04.470 --> 00:04:04.480 align:start position:0% you like to manage we just type Def Con 00:04:04.480 --> 00:04:06.930 align:start position:0% you like to manage we just type Def Con that's<00:04:04.629> a<00:04:04.690> nice<00:04:04.840> network<00:04:05.230> and<00:04:05.650> then<00:04:06.250> as<00:04:06.519> what 00:04:06.930 --> 00:04:06.940 align:start position:0% that's a nice network and then as what 00:04:06.940 --> 00:04:08.729 align:start position:0% that's a nice network and then as what would<00:04:07.090> you<00:04:07.180> like<00:04:07.329> to<00:04:07.510> do<00:04:07.660> well<00:04:08.260> we<00:04:08.500> don't<00:04:08.650> have 00:04:08.729 --> 00:04:08.739 align:start position:0% would you like to do well we don't have 00:04:08.739 --> 00:04:10.559 align:start position:0% would you like to do well we don't have Network<00:04:09.190> yet<00:04:09.639> so<00:04:09.849> we<00:04:09.940> don't<00:04:09.970> kind<00:04:10.329> of<00:04:10.389> shown 00:04:10.559 --> 00:04:10.569 align:start position:0% Network yet so we don't kind of shown 00:04:10.569 --> 00:04:12.270 align:start position:0% Network yet so we don't kind of shown that<00:04:10.720> for<00:04:10.900> statistics<00:04:11.440> but<00:04:11.620> we<00:04:11.739> can<00:04:11.919> configure 00:04:12.270 --> 00:04:12.280 align:start position:0% that for statistics but we can configure 00:04:12.280 --> 00:04:14.220 align:start position:0% that for statistics but we can configure the<00:04:12.519> Genesis<00:04:12.940> block<00:04:13.090> so<00:04:13.599> let's<00:04:13.780> just<00:04:13.989> switch 00:04:14.220 --> 00:04:14.230 align:start position:0% the Genesis block so let's just switch 00:04:14.230 --> 00:04:16.259 align:start position:0% the Genesis block so let's just switch that<00:04:14.440> and<00:04:14.799> what<00:04:15.400> kind<00:04:15.519> of<00:04:15.639> concerns<00:04:16.120> this 00:04:16.259 --> 00:04:16.269 align:start position:0% that and what kind of concerns this 00:04:16.269 --> 00:04:18.210 align:start position:0% that and what kind of concerns this engine<00:04:16.630> well<00:04:17.169> we<00:04:17.289> have<00:04:17.440> proof<00:04:17.620> of<00:04:17.769> Authority 00:04:18.210 --> 00:04:18.220 align:start position:0% engine well we have proof of Authority 00:04:18.220 --> 00:04:20.009 align:start position:0% engine well we have proof of Authority for<00:04:18.400> click<00:04:18.669> but<00:04:18.940> since<00:04:19.209> we<00:04:19.329> want<00:04:19.359> to<00:04:19.660> actually 00:04:20.009 --> 00:04:20.019 align:start position:0% for click but since we want to actually 00:04:20.019 --> 00:04:21.509 align:start position:0% for click but since we want to actually across<00:04:20.260> client<00:04:20.680> that's<00:04:20.799> what<00:04:20.979> let's<00:04:21.190> stick<00:04:21.400> to 00:04:21.509 --> 00:04:21.519 align:start position:0% across client that's what let's stick to 00:04:21.519 --> 00:04:23.790 align:start position:0% across client that's what let's stick to ET<00:04:21.789> hash<00:04:21.940> nice<00:04:22.659> do<00:04:22.930> we<00:04:23.020> want<00:04:23.140> to<00:04:23.229> fund<00:04:23.380> initial 00:04:23.790 --> 00:04:23.800 align:start position:0% ET hash nice do we want to fund initial 00:04:23.800 --> 00:04:24.920 align:start position:0% ET hash nice do we want to fund initial account<00:04:24.039> No 00:04:24.920 --> 00:04:24.930 align:start position:0% account No 00:04:24.930 --> 00:04:28.219 align:start position:0% account No and<00:04:25.370> do<00:04:26.370> we<00:04:26.490> want<00:04:26.520> asbestos<00:04:27.330> chain<00:04:27.600> Network 00:04:28.219 --> 00:04:28.229 align:start position:0% and do we want asbestos chain Network 00:04:28.229 --> 00:04:30.350 align:start position:0% and do we want asbestos chain Network chains<00:04:28.530> well<00:04:28.830> if<00:04:28.949> you<00:04:29.070> run<00:04:29.310> a<00:04:29.370> public<00:04:30.090> network 00:04:30.350 --> 00:04:30.360 align:start position:0% chains well if you run a public network 00:04:30.360 --> 00:04:32.810 align:start position:0% chains well if you run a public network maybe<00:04:30.870> it's<00:04:31.080> worth<00:04:31.259> I<00:04:31.440> know<00:04:31.740> for<00:04:32.400> now<00:04:32.580> we<00:04:32.790> just 00:04:32.810 --> 00:04:32.820 align:start position:0% maybe it's worth I know for now we just 00:04:32.820 --> 00:04:35.990 align:start position:0% maybe it's worth I know for now we just do<00:04:33.210> random<00:04:33.419> and<00:04:34.110> that<00:04:35.100> was<00:04:35.280> about<00:04:35.400> it<00:04:35.759> we 00:04:35.990 --> 00:04:36.000 align:start position:0% do random and that was about it we 00:04:36.000 --> 00:04:37.730 align:start position:0% do random and that was about it we actually<00:04:36.360> managed<00:04:36.660> to<00:04:36.690> configure<00:04:37.169> an<00:04:37.350> entire 00:04:37.730 --> 00:04:37.740 align:start position:0% actually managed to configure an entire 00:04:37.740 --> 00:04:40.550 align:start position:0% actually managed to configure an entire Genesee<00:04:38.550> state<00:04:38.850> for<00:04:39.180> five<00:04:39.690> different<00:04:39.900> clients 00:04:40.550 --> 00:04:40.560 align:start position:0% Genesee state for five different clients 00:04:40.560 --> 00:04:46.879 align:start position:0% Genesee state for five different clients without<00:04:40.729> doing<00:04:41.729> anything<00:04:43.039> now<00:04:44.360> of<00:04:45.360> course<00:04:45.889> if 00:04:46.879 --> 00:04:46.889 align:start position:0% without doing anything now of course if 00:04:46.889 --> 00:04:48.230 align:start position:0% without doing anything now of course if you<00:04:47.100> actually<00:04:47.430> want<00:04:47.729> to<00:04:47.789> run<00:04:47.970> your<00:04:48.120> own 00:04:48.230 --> 00:04:48.240 align:start position:0% you actually want to run your own 00:04:48.240 --> 00:04:50.510 align:start position:0% you actually want to run your own network<00:04:48.660> then<00:04:49.410> the<00:04:49.650> genesis<00:04:50.009> is<00:04:50.160> just<00:04:50.340> step 00:04:50.510 --> 00:04:50.520 align:start position:0% network then the genesis is just step 00:04:50.520 --> 00:04:51.920 align:start position:0% network then the genesis is just step one<00:04:50.550> you<00:04:50.880> will<00:04:51.000> need<00:04:51.120> to<00:04:51.240> get<00:04:51.360> some<00:04:51.720> nodes 00:04:51.920 --> 00:04:51.930 align:start position:0% one you will need to get some nodes 00:04:51.930 --> 00:04:55.340 align:start position:0% one you will need to get some nodes online<00:04:52.410> but<00:04:53.600> one<00:04:54.600> of<00:04:54.690> the<00:04:54.780> biggest<00:04:55.020> problems 00:04:55.340 --> 00:04:55.350 align:start position:0% online but one of the biggest problems 00:04:55.350 --> 00:04:56.570 align:start position:0% online but one of the biggest problems that<00:04:55.440> we<00:04:55.560> see<00:04:55.770> with<00:04:55.800> people<00:04:56.220> getting<00:04:56.310> those 00:04:56.570 --> 00:04:56.580 align:start position:0% that we see with people getting those 00:04:56.580 --> 00:04:57.770 align:start position:0% that we see with people getting those online<00:04:56.940> is<00:04:57.030> that<00:04:57.150> they<00:04:57.270> have<00:04:57.389> absolutely<00:04:57.690> no 00:04:57.770 --> 00:04:57.780 align:start position:0% online is that they have absolutely no 00:04:57.780 --> 00:04:59.570 align:start position:0% online is that they have absolutely no idea<00:04:57.870> what<00:04:58.169> the<00:04:58.289> nodes<00:04:58.560> are<00:04:58.770> doing<00:04:59.100> so<00:04:59.520> you 00:04:59.570 --> 00:04:59.580 align:start position:0% idea what the nodes are doing so you 00:04:59.580 --> 00:05:01.490 align:start position:0% idea what the nodes are doing so you really<00:04:59.880> need<00:05:00.030> to<00:05:00.360> monitor<00:05:00.510> the<00:05:00.900> node<00:05:01.050> somehow 00:05:01.490 --> 00:05:01.500 align:start position:0% really need to monitor the node somehow 00:05:01.500 --> 00:05:04.070 align:start position:0% really need to monitor the node somehow and<00:05:01.770> really<00:05:02.639> want<00:05:02.820> to<00:05:02.910> do<00:05:03.000> that<00:05:03.150> via<00:05:03.479> them<00:05:03.930> each 00:05:04.070 --> 00:05:04.080 align:start position:0% and really want to do that via them each 00:05:04.080 --> 00:05:05.840 align:start position:0% and really want to do that via them each stat<00:05:04.380> so<00:05:04.560> running<00:05:04.830> each<00:05:04.949> stats<00:05:05.250> which<00:05:05.610> isn't 00:05:05.840 --> 00:05:05.850 align:start position:0% stat so running each stats which isn't 00:05:05.850 --> 00:05:08.090 align:start position:0% stat so running each stats which isn't really<00:05:06.030> easy<00:05:06.449> to<00:05:06.720> do<00:05:06.870> but<00:05:07.320> I<00:05:07.470> see<00:05:07.620> how<00:05:07.740> puppet 00:05:08.090 --> 00:05:08.100 align:start position:0% really easy to do but I see how puppet 00:05:08.100 --> 00:05:09.800 align:start position:0% really easy to do but I see how puppet can<00:05:08.280> help<00:05:08.490> so<00:05:08.940> what<00:05:09.150> would<00:05:09.300> you<00:05:09.419> like<00:05:09.539> to<00:05:09.720> do 00:05:09.800 --> 00:05:09.810 align:start position:0% can help so what would you like to do 00:05:09.810 --> 00:05:11.779 align:start position:0% can help so what would you like to do puppet<00:05:10.110> asks<00:05:10.380> us<00:05:10.500> what<00:05:11.190> we'd<00:05:11.280> like<00:05:11.400> to<00:05:11.550> deploy 00:05:11.779 --> 00:05:11.789 align:start position:0% puppet asks us what we'd like to deploy 00:05:11.789 --> 00:05:13.580 align:start position:0% puppet asks us what we'd like to deploy a<00:05:11.880> new<00:05:11.970> network<00:05:12.389> component<00:05:12.960> it<00:05:13.199> gives<00:05:13.410> us<00:05:13.560> a 00:05:13.580 --> 00:05:13.590 align:start position:0% a new network component it gives us a 00:05:13.590 --> 00:05:16.070 align:start position:0% a new network component it gives us a choice<00:05:13.889> let's<00:05:14.520> stick<00:05:14.699> to<00:05:14.820> it's<00:05:15.000> it's<00:05:15.660> fat<00:05:15.900> and 00:05:16.070 --> 00:05:16.080 align:start position:0% choice let's stick to it's it's fat and 00:05:16.080 --> 00:05:17.390 align:start position:0% choice let's stick to it's it's fat and which<00:05:16.919> server 00:05:17.390 --> 00:05:17.400 align:start position:0% which server 00:05:17.400 --> 00:05:20.120 align:start position:0% which server well<00:05:17.729> that's<00:05:18.330> connector<00:05:18.750> server<00:05:19.020> we<00:05:19.710> have<00:05:19.740> a 00:05:20.120 --> 00:05:20.130 align:start position:0% well that's connector server we have a 00:05:20.130 --> 00:05:22.040 align:start position:0% well that's connector server we have a server<00:05:20.430> called<00:05:20.699> DEFCON<00:05:21.000> Network 00:05:22.040 --> 00:05:22.050 align:start position:0% server called DEFCON Network 00:05:22.050 --> 00:05:29.110 align:start position:0% server called DEFCON Network it's<00:05:22.410> a<00:05:22.500> registered<00:05:22.919> domain<00:05:23.220> name<00:05:23.520> oh<00:05:24.860> yeah 00:05:29.110 --> 00:05:29.120 align:start position:0% 00:05:29.120 --> 00:05:34.279 align:start position:0% and<00:05:30.680> yay<00:05:31.710> Wi-Fi<00:05:32.669> works<00:05:32.880> awesome<00:05:33.330> so<00:05:34.169> we 00:05:34.279 --> 00:05:34.289 align:start position:0% and yay Wi-Fi works awesome so we 00:05:34.289 --> 00:05:38.420 align:start position:0% and yay Wi-Fi works awesome so we managed<00:05:34.530> to<00:05:34.650> connect<00:05:36.979> that's<00:05:37.979> why<00:05:38.190> you<00:05:38.250> don't 00:05:38.420 --> 00:05:38.430 align:start position:0% managed to connect that's why you don't 00:05:38.430 --> 00:05:45.260 align:start position:0% managed to connect that's why you don't do<00:05:38.639> live<00:05:38.820> demos<00:05:42.620> do<00:05:43.620> we<00:05:43.770> trust<00:05:44.370> this<00:05:44.639> yes<00:05:45.060> we 00:05:45.260 --> 00:05:45.270 align:start position:0% do live demos do we trust this yes we 00:05:45.270 --> 00:05:48.310 align:start position:0% do live demos do we trust this yes we trust<00:05:45.539> the<00:05:45.750> remote<00:05:45.960> host 00:05:48.310 --> 00:05:48.320 align:start position:0% 00:05:48.320 --> 00:05:51.320 align:start position:0% now<00:05:49.320> what<00:05:49.470> where<00:05:50.430> do<00:05:50.550> you<00:05:50.669> want<00:05:50.789> to<00:05:50.909> deploy<00:05:51.120> it 00:05:51.320 --> 00:05:51.330 align:start position:0% now what where do you want to deploy it 00:05:51.330 --> 00:05:52.850 align:start position:0% now what where do you want to deploy it half<00:05:51.599> since<00:05:51.870> we<00:05:51.960> want<00:05:52.110> to<00:05:52.169> deploy<00:05:52.289> possibly 00:05:52.850 --> 00:05:52.860 align:start position:0% half since we want to deploy possibly 00:05:52.860 --> 00:05:55.460 align:start position:0% half since we want to deploy possibly multiple<00:05:53.010> websites<00:05:53.430> here<00:05:53.880> let's<00:05:54.260> deploy<00:05:55.260> it 00:05:55.460 --> 00:05:55.470 align:start position:0% multiple websites here let's deploy it 00:05:55.470 --> 00:05:58.550 align:start position:0% multiple websites here let's deploy it on<00:05:55.710> port<00:05:56.520> 80<00:05:56.729> and<00:05:57.120> do<00:05:57.840> we<00:05:57.930> want<00:05:58.050> to<00:05:58.229> share<00:05:58.440> the 00:05:58.550 --> 00:05:58.560 align:start position:0% on port 80 and do we want to share the 00:05:58.560 --> 00:06:01.399 align:start position:0% on port 80 and do we want to share the port<00:05:58.800> 8<00:05:58.919> with<00:05:59.099> others<00:05:59.370> yes<00:05:59.699> sure<00:06:00.000> now<00:06:00.870> when<00:06:01.260> we 00:06:01.399 --> 00:06:01.409 align:start position:0% port 8 with others yes sure now when we 00:06:01.409 --> 00:06:03.290 align:start position:0% port 8 with others yes sure now when we actually<00:06:01.889> say<00:06:02.070> we<00:06:02.190> want<00:06:02.310> to<00:06:02.430> SharePoint<00:06:02.880> port 00:06:03.290 --> 00:06:03.300 align:start position:0% actually say we want to SharePoint port 00:06:03.300 --> 00:06:05.689 align:start position:0% actually say we want to SharePoint port 80<00:06:03.479> purpose<00:06:04.380> will<00:06:04.560> deploy<00:06:04.860> a<00:06:04.889> reverse<00:06:05.310> engine 00:06:05.689 --> 00:06:05.699 align:start position:0% 80 purpose will deploy a reverse engine 00:06:05.699 --> 00:06:07.610 align:start position:0% 80 purpose will deploy a reverse engine X<00:06:05.820> proxy<00:06:06.300> automatically<00:06:07.289> configure 00:06:07.610 --> 00:06:07.620 align:start position:0% X proxy automatically configure 00:06:07.620 --> 00:06:08.899 align:start position:0% X proxy automatically configure everything<00:06:07.979> without<00:06:08.099> us<00:06:08.400> having<00:06:08.580> to<00:06:08.760> do 00:06:08.899 --> 00:06:08.909 align:start position:0% everything without us having to do 00:06:08.909 --> 00:06:12.339 align:start position:0% everything without us having to do anything<00:06:09.080> and<00:06:10.080> what<00:06:11.010> domain<00:06:11.250> do<00:06:11.490> we<00:06:11.550> want<00:06:11.729> to 00:06:12.339 --> 00:06:12.349 align:start position:0% anything and what domain do we want to 00:06:12.349 --> 00:06:17.469 align:start position:0% anything and what domain do we want to host<00:06:13.349> this<00:06:13.849> it<00:06:14.849> eats<00:06:15.300> that's<00:06:15.570> page<00:06:16.199> one<00:06:16.229> dot 00:06:17.469 --> 00:06:17.479 align:start position:0% host this it eats that's page one dot 00:06:17.479 --> 00:06:22.820 align:start position:0% host this it eats that's page one dot DEFCON<00:06:18.479> Network<00:06:21.320> okay<00:06:22.320> and<00:06:22.530> what's<00:06:22.680> the 00:06:22.820 --> 00:06:22.830 align:start position:0% DEFCON Network okay and what's the 00:06:22.830 --> 00:06:26.390 align:start position:0% DEFCON Network okay and what's the easiest<00:06:23.340> password<00:06:23.909> hello<00:06:24.949> hello<00:06:25.949> it<00:06:26.099> doesn't 00:06:26.390 --> 00:06:26.400 align:start position:0% easiest password hello hello it doesn't 00:06:26.400 --> 00:06:27.969 align:start position:0% easiest password hello hello it doesn't matter<00:06:26.520> yeah<00:06:27.120> it's<00:06:27.539> fine 00:06:27.969 --> 00:06:27.979 align:start position:0% matter yeah it's fine 00:06:27.979 --> 00:06:30.589 align:start position:0% matter yeah it's fine now<00:06:28.979> it<00:06:29.250> in<00:06:29.520> theory<00:06:29.760> public<00:06:30.150> now<00:06:30.270> runs<00:06:30.449> in<00:06:30.539> the 00:06:30.589 --> 00:06:30.599 align:start position:0% now it in theory public now runs in the 00:06:30.599 --> 00:06:32.990 align:start position:0% now it in theory public now runs in the background<00:06:31.010> starts<00:06:32.010> up<00:06:32.130> entirely<00:06:32.430> it's<00:06:32.699> fast 00:06:32.990 --> 00:06:33.000 align:start position:0% background starts up entirely it's fast 00:06:33.000 --> 00:06:36.469 align:start position:0% background starts up entirely it's fast and<00:06:33.150> everything<00:06:33.560> and<00:06:34.560> now<00:06:35.430> not<00:06:36.029> only<00:06:36.300> will<00:06:36.419> it 00:06:36.469 --> 00:06:36.479 align:start position:0% and everything and now not only will it 00:06:36.479 --> 00:06:38.780 align:start position:0% and everything and now not only will it start<00:06:36.719> it<00:06:36.870> up<00:06:36.990> it<00:06:37.229> also<00:06:37.500> lists<00:06:37.950> us<00:06:38.070> that<00:06:38.279> yes<00:06:38.490> we 00:06:38.780 --> 00:06:38.790 align:start position:0% start it up it also lists us that yes we 00:06:38.790 --> 00:06:40.490 align:start position:0% start it up it also lists us that yes we a<00:06:38.820> server<00:06:39.090> connected<00:06:39.570> the<00:06:39.720> IP<00:06:39.870> address<00:06:40.290> and 00:06:40.490 --> 00:06:40.500 align:start position:0% a server connected the IP address and 00:06:40.500 --> 00:06:42.590 align:start position:0% a server connected the IP address and what<00:06:40.650> services<00:06:41.070> it's<00:06:41.250> running<00:06:41.550> and<00:06:42.060> now<00:06:42.420> if 00:06:42.590 --> 00:06:42.600 align:start position:0% what services it's running and now if 00:06:42.600 --> 00:06:44.870 align:start position:0% what services it's running and now if you<00:06:42.720> load<00:06:42.930> up<00:06:43.140> a<00:06:43.290> web<00:06:43.470> browser<00:06:43.680> and<00:06:44.160> look<00:06:44.700> at 00:06:44.870 --> 00:06:44.880 align:start position:0% you load up a web browser and look at 00:06:44.880 --> 00:06:46.850 align:start position:0% you load up a web browser and look at the<00:06:45.000> actual<00:06:45.360> domain<00:06:45.570> name<00:06:45.960> then<00:06:46.350> hopefully 00:06:46.850 --> 00:06:46.860 align:start position:0% the actual domain name then hopefully 00:06:46.860 --> 00:06:50.210 align:start position:0% the actual domain name then hopefully yep<00:06:47.850> we<00:06:48.270> have<00:06:48.420> a<00:06:48.450> nice<00:06:48.630> test<00:06:48.900> running<00:06:49.140> and<00:06:49.500> you 00:06:50.210 --> 00:06:50.220 align:start position:0% yep we have a nice test running and you 00:06:50.220 --> 00:06:51.980 align:start position:0% yep we have a nice test running and you can<00:06:50.250> you<00:06:50.730> can<00:06:50.760> see<00:06:51.060> it<00:06:51.270> is<00:06:51.420> actually<00:06:51.570> not<00:06:51.780> an 00:06:51.980 --> 00:06:51.990 align:start position:0% can you can see it is actually not an 00:06:51.990 --> 00:06:57.530 align:start position:0% can you can see it is actually not an image<00:06:52.170> it's<00:06:52.350> alive<00:06:52.560> that<00:06:53.130> page<00:06:54.770> okay<00:06:56.150> now<00:06:57.150> we 00:06:57.530 --> 00:06:57.540 align:start position:0% image it's alive that page okay now we 00:06:57.540 --> 00:06:59.570 align:start position:0% image it's alive that page okay now we have<00:06:57.570> a<00:06:57.750> you<00:06:58.380> can<00:06:58.560> monitor<00:06:58.890> the<00:06:59.040> thing<00:06:59.250> but<00:06:59.460> we 00:06:59.570 --> 00:06:59.580 align:start position:0% have a you can monitor the thing but we 00:06:59.580 --> 00:07:01.070 align:start position:0% have a you can monitor the thing but we actually<00:06:59.820> have<00:06:59.940> to<00:07:00.060> boot<00:07:00.240> up<00:07:00.420> the<00:07:00.450> network 00:07:01.070 --> 00:07:01.080 align:start position:0% actually have to boot up the network 00:07:01.080 --> 00:07:04.400 align:start position:0% actually have to boot up the network so<00:07:01.230> let's<00:07:01.440> deploy<00:07:01.800> now<00:07:02.070> boot<00:07:03.060> node<00:07:03.380> yeah 00:07:04.400 --> 00:07:04.410 align:start position:0% so let's deploy now boot node yeah 00:07:04.410 --> 00:07:07.960 align:start position:0% so let's deploy now boot node yeah that's<00:07:04.710> sometimes<00:07:05.070> the<00:07:05.430> console<00:07:05.760> is<00:07:05.880> funky 00:07:07.960 --> 00:07:07.970 align:start position:0% that's sometimes the console is funky 00:07:07.970 --> 00:07:10.970 align:start position:0% that's sometimes the console is funky now<00:07:08.970> again<00:07:09.270> we<00:07:09.390> have<00:07:09.540> a<00:07:09.570> small<00:07:09.900> scan<00:07:10.560> so<00:07:10.740> let<00:07:10.860> me 00:07:10.970 --> 00:07:10.980 align:start position:0% now again we have a small scan so let me 00:07:10.980 --> 00:07:13.120 align:start position:0% now again we have a small scan so let me know<00:07:11.070> what<00:07:11.190> we're<00:07:11.400> up<00:07:11.550> to<00:07:11.610> and<00:07:12.000> that's 00:07:13.120 --> 00:07:13.130 align:start position:0% know what we're up to and that's 00:07:13.130 --> 00:07:17.450 align:start position:0% know what we're up to and that's deployment<00:07:15.680> and<00:07:16.680> where<00:07:17.040> do<00:07:17.160> we<00:07:17.250> want<00:07:17.400> to 00:07:17.450 --> 00:07:17.460 align:start position:0% deployment and where do we want to 00:07:17.460 --> 00:07:19.010 align:start position:0% deployment and where do we want to deploy<00:07:17.610> it<00:07:17.760> well<00:07:18.030> usually<00:07:18.390> don't<00:07:18.630> want<00:07:18.870> your 00:07:19.010 --> 00:07:19.020 align:start position:0% deploy it well usually don't want your 00:07:19.020 --> 00:07:20.330 align:start position:0% deploy it well usually don't want your boot<00:07:19.200> not<00:07:19.380> to<00:07:19.500> go<00:07:19.620> down<00:07:19.800> if<00:07:19.980> somebody's 00:07:20.330 --> 00:07:20.340 align:start position:0% boot not to go down if somebody's 00:07:20.340 --> 00:07:21.860 align:start position:0% boot not to go down if somebody's dusting<00:07:20.730> your<00:07:20.850> website<00:07:21.240> so<00:07:21.480> let's<00:07:21.510> just 00:07:21.860 --> 00:07:21.870 align:start position:0% dusting your website so let's just 00:07:21.870 --> 00:07:24.050 align:start position:0% dusting your website so let's just switch<00:07:22.080> to<00:07:22.410> a<00:07:22.620> new<00:07:22.770> server<00:07:23.100> let's<00:07:23.610> call<00:07:23.940> it 00:07:24.050 --> 00:07:24.060 align:start position:0% switch to a new server let's call it 00:07:24.060 --> 00:07:29.330 align:start position:0% switch to a new server let's call it boot<00:07:24.300> DEFCON<00:07:25.260> Network<00:07:26.900> and<00:07:27.900> yes<00:07:28.770> we<00:07:28.950> connected 00:07:29.330 --> 00:07:29.340 align:start position:0% boot DEFCON Network and yes we connected 00:07:29.340 --> 00:07:30.800 align:start position:0% boot DEFCON Network and yes we connected a<00:07:29.400> new<00:07:29.520> server<00:07:29.760> that's<00:07:30.060> fine<00:07:30.270> we<00:07:30.510> can<00:07:30.660> manage 00:07:30.800 --> 00:07:30.810 align:start position:0% a new server that's fine we can manage 00:07:30.810 --> 00:07:33.290 align:start position:0% a new server that's fine we can manage multiple<00:07:31.050> servers<00:07:31.560> at<00:07:31.680> the<00:07:31.710> same<00:07:31.950> time<00:07:32.300> where 00:07:33.290 --> 00:07:33.300 align:start position:0% multiple servers at the same time where 00:07:33.300 --> 00:07:34.970 align:start position:0% multiple servers at the same time where do<00:07:33.360> you<00:07:33.420> want<00:07:33.570> to<00:07:33.630> store<00:07:33.930> the<00:07:34.140> data<00:07:34.170> directory 00:07:34.970 --> 00:07:34.980 align:start position:0% do you want to store the data directory 00:07:34.980 --> 00:07:38.330 align:start position:0% do you want to store the data directory let's<00:07:35.490> call<00:07:35.700> it<00:07:35.850> DEFCON<00:07:37.160> server 00:07:38.330 --> 00:07:38.340 align:start position:0% let's call it DEFCON server 00:07:38.340 --> 00:07:41.090 align:start position:0% let's call it DEFCON server what<00:07:38.700> UDP<00:07:39.150> port<00:07:39.420> one<00:07:39.600> we'll<00:07:40.320> just<00:07:40.500> you<00:07:40.590> go<00:07:40.920> with 00:07:41.090 --> 00:07:41.100 align:start position:0% what UDP port one we'll just you go with 00:07:41.100 --> 00:07:43.070 align:start position:0% what UDP port one we'll just you go with the<00:07:41.160> default<00:07:41.600> configurations<00:07:42.600> they<00:07:42.810> aren't 00:07:43.070 --> 00:07:43.080 align:start position:0% the default configurations they aren't 00:07:43.080 --> 00:07:45.650 align:start position:0% the default configurations they aren't even<00:07:43.260> that<00:07:43.880> interesting<00:07:44.880> and<00:07:45.270> what<00:07:45.390> we<00:07:45.480> want 00:07:45.650 --> 00:07:45.660 align:start position:0% even that interesting and what we want 00:07:45.660 --> 00:07:47.090 align:start position:0% even that interesting and what we want to<00:07:45.750> call<00:07:45.960> the<00:07:46.110> booted<00:07:46.380> on<00:07:46.500> this<00:07:46.650> past<00:07:46.860> page 00:07:47.090 --> 00:07:47.100 align:start position:0% to call the booted on this past page 00:07:47.100 --> 00:07:50.570 align:start position:0% to call the booted on this past page that's<00:07:48.000> called<00:07:48.210> that<00:07:49.020> seems<00:07:49.290> about<00:07:49.530> as<00:07:49.830> dumb 00:07:50.570 --> 00:07:50.580 align:start position:0% that's called that seems about as dumb 00:07:50.580 --> 00:07:54.230 align:start position:0% that's called that seems about as dumb as<00:07:50.640> it<00:07:50.820> can<00:07:51.000> get<00:07:51.120> and<00:07:52.370> again<00:07:53.370> pop<00:07:53.640> it<00:07:53.790> does<00:07:54.060> it's 00:07:54.230 --> 00:07:54.240 align:start position:0% as it can get and again pop it does it's 00:07:54.240 --> 00:07:56.960 align:start position:0% as it can get and again pop it does it's funky<00:07:54.750> magic<00:07:55.020> in<00:07:55.140> the<00:07:55.230> background<00:07:55.650> and<00:07:56.220> if<00:07:56.730> we 00:07:56.960 --> 00:07:56.970 align:start position:0% funky magic in the background and if we 00:07:56.970 --> 00:08:01.850 align:start position:0% funky magic in the background and if we I<00:07:57.590> think<00:07:58.590> we<00:07:58.860> can<00:07:59.010> I<00:07:59.340> can<00:07:59.970> even<00:08:00.180> close<00:08:00.390> this<00:08:00.860> yep 00:08:01.850 --> 00:08:01.860 align:start position:0% I think we can I can even close this yep 00:08:01.860 --> 00:08:04.490 align:start position:0% I think we can I can even close this yep and<00:08:02.580> if<00:08:02.760> we<00:08:02.880> now<00:08:03.000> stack<00:08:03.360> I<00:08:03.720> checked<00:08:04.050> our<00:08:04.200> stats 00:08:04.490 --> 00:08:04.500 align:start position:0% and if we now stack I checked our stats 00:08:04.500 --> 00:08:07.820 align:start position:0% and if we now stack I checked our stats page<00:08:04.880> then<00:08:05.880> yep<00:08:06.590> fair<00:08:07.590> enough 00:08:07.820 --> 00:08:07.830 align:start position:0% page then yep fair enough 00:08:07.830 --> 00:08:09.890 align:start position:0% page then yep fair enough we<00:08:08.010> have<00:08:08.220> our<00:08:08.520> boot<00:08:08.790> notes<00:08:09.030> register<00:08:09.660> maybe 00:08:09.890 --> 00:08:09.900 align:start position:0% we have our boot notes register maybe 00:08:09.900 --> 00:08:13.070 align:start position:0% we have our boot notes register maybe it's<00:08:10.080> not<00:08:10.170> a<00:08:10.470> bit<00:08:11.160> tiny<00:08:11.430> but<00:08:11.670> we<00:08:12.630> have<00:08:12.780> a<00:08:12.810> boot 00:08:13.070 --> 00:08:13.080 align:start position:0% it's not a bit tiny but we have a boot 00:08:13.080 --> 00:08:14.780 align:start position:0% it's not a bit tiny but we have a boot running<00:08:13.590> and<00:08:13.800> it's<00:08:14.010> immediately<00:08:14.400> linked<00:08:14.640> to 00:08:14.780 --> 00:08:14.790 align:start position:0% running and it's immediately linked to 00:08:14.790 --> 00:08:16.160 align:start position:0% running and it's immediately linked to the<00:08:15.000> Status<00:08:15.300> page<00:08:15.360> we<00:08:15.570> didn't<00:08:15.780> even<00:08:15.870> have<00:08:15.960> to 00:08:16.160 --> 00:08:16.170 align:start position:0% the Status page we didn't even have to 00:08:16.170 --> 00:08:18.380 align:start position:0% the Status page we didn't even have to configure<00:08:16.440> everything<00:08:16.980> cool<00:08:17.400> now<00:08:18.030> we<00:08:18.090> have<00:08:18.360> a 00:08:18.380 --> 00:08:18.390 align:start position:0% configure everything cool now we have a 00:08:18.390 --> 00:08:20.000 align:start position:0% configure everything cool now we have a static<00:08:18.870> chain<00:08:19.200> that<00:08:19.320> doesn't<00:08:19.650> do<00:08:19.740> anything 00:08:20.000 --> 00:08:20.010 align:start position:0% static chain that doesn't do anything 00:08:20.010 --> 00:08:21.830 align:start position:0% static chain that doesn't do anything obviously<00:08:20.580> we<00:08:20.670> need<00:08:20.820> to<00:08:20.910> mine<00:08:21.150> on<00:08:21.420> the<00:08:21.600> chain 00:08:21.830 --> 00:08:21.840 align:start position:0% obviously we need to mine on the chain 00:08:21.840 --> 00:08:25.150 align:start position:0% obviously we need to mine on the chain to<00:08:22.320> make<00:08:22.560> it<00:08:22.620> progress<00:08:22.920> so<00:08:23.760> we<00:08:23.790> can<00:08:24.060> again<00:08:24.300> ask 00:08:25.150 --> 00:08:25.160 align:start position:0% to make it progress so we can again ask 00:08:25.160 --> 00:08:28.370 align:start position:0% to make it progress so we can again ask startup<00:08:26.160> puppet<00:08:26.520> ask<00:08:26.790> it<00:08:27.030> to<00:08:27.180> connect<00:08:27.480> to<00:08:27.690> our 00:08:28.370 --> 00:08:28.380 align:start position:0% startup puppet ask it to connect to our 00:08:28.380 --> 00:08:30.650 align:start position:0% startup puppet ask it to connect to our new<00:08:28.590> little<00:08:28.920> network<00:08:29.730> and<00:08:30.270> let's<00:08:30.420> see<00:08:30.540> how 00:08:30.650 --> 00:08:30.660 align:start position:0% new little network and let's see how 00:08:30.660 --> 00:08:32.420 align:start position:0% new little network and let's see how what<00:08:30.810> it<00:08:30.930> takes<00:08:31.110> to<00:08:31.260> deploy<00:08:31.590> our<00:08:31.620> mining<00:08:32.250> node 00:08:32.420 --> 00:08:32.430 align:start position:0% what it takes to deploy our mining node 00:08:32.430 --> 00:08:35.150 align:start position:0% what it takes to deploy our mining node now<00:08:33.330> we<00:08:33.390> want<00:08:33.630> to<00:08:33.720> deploy<00:08:33.990> a<00:08:34.380> new<00:08:34.919> network 00:08:35.150 --> 00:08:35.160 align:start position:0% now we want to deploy a new network 00:08:35.160 --> 00:08:37.670 align:start position:0% now we want to deploy a new network component<00:08:35.910> let's<00:08:36.390> deploy<00:08:36.660> a<00:08:37.050> mining<00:08:37.410> order 00:08:37.670 --> 00:08:37.680 align:start position:0% component let's deploy a mining order 00:08:37.680 --> 00:08:40.640 align:start position:0% component let's deploy a mining order sealer<00:08:37.979> again<00:08:38.760> miner<00:08:39.030> kind<00:08:39.419> of<00:08:39.510> takes<00:08:40.290> a<00:08:40.440> kick 00:08:40.640 --> 00:08:40.650 align:start position:0% sealer again miner kind of takes a kick 00:08:40.650 --> 00:08:41.630 align:start position:0% sealer again miner kind of takes a kick out<00:08:40.890> of<00:08:41.099> the<00:08:41.220> network 00:08:41.630 --> 00:08:41.640 align:start position:0% out of the network 00:08:41.640 --> 00:08:44.120 align:start position:0% out of the network machine<00:08:42.360> so<00:08:42.599> let's<00:08:42.810> do<00:08:43.050> put<00:08:43.380> it<00:08:43.500> on<00:08:43.680> the<00:08:43.890> miner 00:08:44.120 --> 00:08:44.130 align:start position:0% machine so let's do put it on the miner 00:08:44.130 --> 00:08:52.120 align:start position:0% machine so let's do put it on the miner dot<00:08:45.620> DEFCON<00:08:46.620> Network<00:08:47.750> machine<00:08:48.750> yep<00:08:49.850> and 00:08:52.120 --> 00:08:52.130 align:start position:0% dot DEFCON Network machine yep and 00:08:52.130 --> 00:08:54.249 align:start position:0% dot DEFCON Network machine yep and yeah<00:08:52.850> yeah<00:08:53.120> where<00:08:53.420> do<00:08:53.480> should<00:08:53.690> we<00:08:53.810> store<00:08:54.019> the 00:08:54.249 --> 00:08:54.259 align:start position:0% yeah yeah where do should we store the 00:08:54.259 --> 00:08:58.449 align:start position:0% yeah yeah where do should we store the data<00:08:54.800> DEFCON<00:08:55.899> Minor<00:08:56.899> and<00:08:57.350> we<00:08:58.040> should<00:08:58.220> destroy 00:08:58.449 --> 00:08:58.459 align:start position:0% data DEFCON Minor and we should destroy 00:08:58.459 --> 00:09:05.920 align:start position:0% data DEFCON Minor and we should destroy ET<00:08:58.819> hashtags<00:08:59.300> DEFCON<00:09:00.139> and<00:09:03.730> the<00:09:04.730> remainder<00:09:05.029> can 00:09:05.920 --> 00:09:05.930 align:start position:0% ET hashtags DEFCON and the remainder can 00:09:05.930 --> 00:09:07.569 align:start position:0% ET hashtags DEFCON and the remainder can be<00:09:06.139> the<00:09:06.470> connectivity<00:09:07.040> strings<00:09:07.279> can<00:09:07.490> be 00:09:07.569 --> 00:09:07.579 align:start position:0% be the connectivity strings can be 00:09:07.579 --> 00:09:09.840 align:start position:0% be the connectivity strings can be simple<00:09:07.910> and<00:09:08.060> we<00:09:08.180> want<00:09:08.360> to<00:09:08.449> register<00:09:08.569> it<00:09:09.170> on<00:09:09.410> the 00:09:09.840 --> 00:09:09.850 align:start position:0% simple and we want to register it on the 00:09:09.850 --> 00:09:13.120 align:start position:0% simple and we want to register it on the et<00:09:10.850> hash<00:09:11.000> page<00:09:11.300> as<00:09:12.079> a<00:09:12.230> listas<00:09:12.529> page<00:09:12.800> as<00:09:12.980> the 00:09:13.120 --> 00:09:13.130 align:start position:0% et hash page as a listas page as the 00:09:13.130 --> 00:09:13.509 align:start position:0% et hash page as a listas page as the minor 00:09:13.509 --> 00:09:13.519 align:start position:0% minor 00:09:13.519 --> 00:09:16.329 align:start position:0% minor now<00:09:13.790> what<00:09:13.970> ether<00:09:14.269> base<00:09:14.509> should<00:09:14.779> ooh<00:09:15.199> that<00:09:16.160> was 00:09:16.329 --> 00:09:16.339 align:start position:0% now what ether base should ooh that was 00:09:16.339 --> 00:09:20.710 align:start position:0% now what ether base should ooh that was fancy<00:09:17.560> what<00:09:18.759> address<00:09:19.759> such<00:09:20.120> a<00:09:20.240> minor<00:09:20.420> use 00:09:20.710 --> 00:09:20.720 align:start position:0% fancy what address such a minor use 00:09:20.720 --> 00:09:22.780 align:start position:0% fancy what address such a minor use we'll<00:09:21.110> just<00:09:21.290> copy<00:09:21.470> paste<00:09:21.560> this<00:09:21.920> here<00:09:21.980> and<00:09:22.459> what 00:09:22.780 --> 00:09:22.790 align:start position:0% we'll just copy paste this here and what 00:09:22.790 --> 00:09:25.180 align:start position:0% we'll just copy paste this here and what gas<00:09:23.449> price<00:09:23.750> and<00:09:24.050> gas<00:09:24.199> targets<00:09:24.680> we'll<00:09:25.009> just 00:09:25.180 --> 00:09:25.190 align:start position:0% gas price and gas targets we'll just 00:09:25.190 --> 00:09:26.889 align:start position:0% gas price and gas targets we'll just stick<00:09:25.339> to<00:09:25.490> the<00:09:25.610> default<00:09:26.000> it's<00:09:26.420> not<00:09:26.600> that 00:09:26.889 --> 00:09:26.899 align:start position:0% stick to the default it's not that 00:09:26.899 --> 00:09:28.870 align:start position:0% stick to the default it's not that important<00:09:27.560> and<00:09:27.709> the<00:09:27.980> game<00:09:28.130> puppet<00:09:28.430> is<00:09:28.550> pushing 00:09:28.870 --> 00:09:28.880 align:start position:0% important and the game puppet is pushing 00:09:28.880 --> 00:09:31.329 align:start position:0% important and the game puppet is pushing out<00:09:29.029> the<00:09:29.380> mining<00:09:30.380> note<00:09:30.560> to<00:09:30.680> our<00:09:30.740> remote<00:09:31.009> server 00:09:31.329 --> 00:09:31.339 align:start position:0% out the mining note to our remote server 00:09:31.339 --> 00:09:34.990 align:start position:0% out the mining note to our remote server and<00:09:32.199> it<00:09:33.199> should<00:09:33.560> finish<00:09:33.800> booting<00:09:34.339> any<00:09:34.579> moment 00:09:34.990 --> 00:09:35.000 align:start position:0% and it should finish booting any moment 00:09:35.000 --> 00:09:36.639 align:start position:0% and it should finish booting any moment it<00:09:35.120> does<00:09:35.269> a<00:09:35.300> quick<00:09:35.600> health<00:09:35.839> check<00:09:36.139> it<00:09:36.290> actually 00:09:36.639 --> 00:09:36.649 align:start position:0% it does a quick health check it actually 00:09:36.649 --> 00:09:37.870 align:start position:0% it does a quick health check it actually checks<00:09:36.829> whether<00:09:37.040> the<00:09:37.100> ports<00:09:37.430> are<00:09:37.550> reachable 00:09:37.870 --> 00:09:37.880 align:start position:0% checks whether the ports are reachable 00:09:37.880 --> 00:09:40.240 align:start position:0% checks whether the ports are reachable we<00:09:38.329> have<00:09:38.449> a<00:09:38.480> nice<00:09:38.720> dump<00:09:39.500> of<00:09:39.680> everything<00:09:40.130> we 00:09:40.240 --> 00:09:40.250 align:start position:0% we have a nice dump of everything we 00:09:40.250 --> 00:09:42.939 align:start position:0% we have a nice dump of everything we configure<00:09:40.639> until<00:09:40.970> now<00:09:41.149> and<00:09:41.509> if<00:09:42.500> we<00:09:42.649> look<00:09:42.800> at 00:09:42.939 --> 00:09:42.949 align:start position:0% configure until now and if we look at 00:09:42.949 --> 00:09:45.449 align:start position:0% configure until now and if we look at the<00:09:43.069> stats<00:09:43.339> page<00:09:43.610> fingers<00:09:44.029> crossed 00:09:45.449 --> 00:09:45.459 align:start position:0% the stats page fingers crossed 00:09:45.459 --> 00:09:48.490 align:start position:0% the stats page fingers crossed yep<00:09:46.459> we<00:09:46.790> actually<00:09:47.240> have<00:09:47.449> already<00:09:47.660> four<00:09:48.110> blocks 00:09:48.490 --> 00:09:48.500 align:start position:0% yep we actually have already four blocks 00:09:48.500 --> 00:09:54.340 align:start position:0% yep we actually have already four blocks mind<00:09:49.209> and<00:09:51.009> not<00:09:52.009> only<00:09:52.310> that<00:09:52.670> I'm<00:09:53.269> really<00:09:53.540> hoping 00:09:54.340 --> 00:09:54.350 align:start position:0% mind and not only that I'm really hoping 00:09:54.350 --> 00:09:56.230 align:start position:0% mind and not only that I'm really hoping that<00:09:54.529> the<00:09:54.649> boot<00:09:54.829> node<00:09:55.040> will<00:09:55.279> connect<00:09:55.670> soon<00:09:56.060> to 00:09:56.230 --> 00:09:56.240 align:start position:0% that the boot node will connect soon to 00:09:56.240 --> 00:09:58.749 align:start position:0% that the boot node will connect soon to the<00:09:56.360> mining<00:09:56.689> node<00:09:56.899> but<00:09:57.680> since<00:09:58.189> time<00:09:58.610> is 00:09:58.749 --> 00:09:58.759 align:start position:0% the mining node but since time is 00:09:58.759 --> 00:10:00.160 align:start position:0% the mining node but since time is limited<00:09:58.910> we'll<00:09:59.269> just<00:09:59.540> check<00:09:59.720> it<00:09:59.839> in<00:09:59.930> the<00:09:59.990> next 00:10:00.160 --> 00:10:00.170 align:start position:0% limited we'll just check it in the next 00:10:00.170 --> 00:10:00.850 align:start position:0% limited we'll just check it in the next slide 00:10:00.850 --> 00:10:00.860 align:start position:0% slide 00:10:00.860 --> 00:10:04.120 align:start position:0% slide yep<00:10:01.160> they've<00:10:01.370> connected<00:10:02.110> cool<00:10:03.380> so<00:10:03.800> of<00:10:03.949> course 00:10:04.120 --> 00:10:04.130 align:start position:0% yep they've connected cool so of course 00:10:04.130 --> 00:10:05.980 align:start position:0% yep they've connected cool so of course now<00:10:04.610> you<00:10:04.670> actually<00:10:05.029> have<00:10:05.389> an<00:10:05.509> entire<00:10:05.630> network 00:10:05.980 --> 00:10:05.990 align:start position:0% now you actually have an entire network 00:10:05.990 --> 00:10:07.900 align:start position:0% now you actually have an entire network up<00:10:06.319> and<00:10:06.439> running<00:10:06.529> but<00:10:07.189> if<00:10:07.370> you<00:10:07.519> tell<00:10:07.790> your 00:10:07.900 --> 00:10:07.910 align:start position:0% up and running but if you tell your 00:10:07.910 --> 00:10:09.160 align:start position:0% up and running but if you tell your friends<00:10:08.269> that<00:10:08.300> here<00:10:08.600> I<00:10:08.630> have<00:10:08.839> this<00:10:08.959> awesome 00:10:09.160 --> 00:10:09.170 align:start position:0% friends that here I have this awesome 00:10:09.170 --> 00:10:11.800 align:start position:0% friends that here I have this awesome Network<00:10:09.649> they<00:10:09.949> will<00:10:10.130> just<00:10:10.339> go<00:10:10.550> okay<00:10:11.329> and<00:10:11.660> how 00:10:11.800 --> 00:10:11.810 align:start position:0% Network they will just go okay and how 00:10:11.810 --> 00:10:14.499 align:start position:0% Network they will just go okay and how do<00:10:11.870> we<00:10:12.019> use<00:10:12.079> it<00:10:12.259> and<00:10:12.620> then<00:10:13.399> you<00:10:13.519> kind<00:10:13.819> of<00:10:13.910> start 00:10:14.499 --> 00:10:14.509 align:start position:0% do we use it and then you kind of start 00:10:14.509 --> 00:10:15.999 align:start position:0% do we use it and then you kind of start scratching<00:10:14.839> your<00:10:15.110> head<00:10:15.259> so<00:10:15.680> it<00:10:15.769> would<00:10:15.889> be 00:10:15.999 --> 00:10:16.009 align:start position:0% scratching your head so it would be 00:10:16.009 --> 00:10:18.490 align:start position:0% scratching your head so it would be really<00:10:16.130> nice<00:10:16.370> if<00:10:16.990> well<00:10:17.990> first<00:10:18.230> thing<00:10:18.350> first 00:10:18.490 --> 00:10:18.500 align:start position:0% really nice if well first thing first 00:10:18.500 --> 00:10:20.199 align:start position:0% really nice if well first thing first you<00:10:18.709> could<00:10:18.860> see<00:10:19.160> what<00:10:19.370> the<00:10:19.519> network<00:10:19.819> is<00:10:19.910> doing 00:10:20.199 --> 00:10:20.209 align:start position:0% you could see what the network is doing 00:10:20.209 --> 00:10:21.879 align:start position:0% you could see what the network is doing so<00:10:20.509> for<00:10:20.689> that<00:10:20.810> obviously<00:10:21.259> we<00:10:21.410> need<00:10:21.529> kind<00:10:21.769> of<00:10:21.800> a 00:10:21.879 --> 00:10:21.889 align:start position:0% so for that obviously we need kind of a 00:10:21.889 --> 00:10:25.509 align:start position:0% so for that obviously we need kind of a block<00:10:22.100> Explorer<00:10:23.139> which<00:10:24.310> currently<00:10:25.310> for 00:10:25.509 --> 00:10:25.519 align:start position:0% block Explorer which currently for 00:10:25.519 --> 00:10:27.610 align:start position:0% block Explorer which currently for example<00:10:25.850> there<00:10:25.970> is<00:10:26.060> no<00:10:26.230> open<00:10:27.230> source<00:10:27.439> block 00:10:27.610 --> 00:10:27.620 align:start position:0% example there is no open source block 00:10:27.620 --> 00:10:29.220 align:start position:0% example there is no open source block Explorer<00:10:28.009> that<00:10:28.250> supports 00:10:29.220 --> 00:10:29.230 align:start position:0% Explorer that supports 00:10:29.230 --> 00:10:32.170 align:start position:0% Explorer that supports Goethe<00:10:30.230> reham<00:10:30.709> as<00:10:30.800> a<00:10:30.860> back-end<00:10:31.160> but<00:10:31.579> however 00:10:32.170 --> 00:10:32.180 align:start position:0% Goethe reham as a back-end but however 00:10:32.180 --> 00:10:34.120 align:start position:0% Goethe reham as a back-end but however there<00:10:32.449> is<00:10:32.569> one<00:10:32.600> that<00:10:32.870> supports<00:10:33.230> parity<00:10:33.709> now 00:10:34.120 --> 00:10:34.130 align:start position:0% there is one that supports parity now 00:10:34.130 --> 00:10:35.980 align:start position:0% there is one that supports parity now can<00:10:34.399> we<00:10:34.579> actually<00:10:34.730> deploy<00:10:35.149> a<00:10:35.180> parity<00:10:35.660> note<00:10:35.810> so 00:10:35.980 --> 00:10:35.990 align:start position:0% can we actually deploy a parity note so 00:10:35.990 --> 00:10:36.569 align:start position:0% can we actually deploy a parity note so easily 00:10:36.569 --> 00:10:36.579 align:start position:0% easily 00:10:36.579 --> 00:10:39.220 align:start position:0% easily well<00:10:37.579> sure<00:10:37.850> let's<00:10:38.120> try<00:10:38.329> you<00:10:38.810> want<00:10:38.930> to<00:10:39.019> deploy 00:10:39.220 --> 00:10:39.230 align:start position:0% well sure let's try you want to deploy 00:10:39.230 --> 00:10:41.170 align:start position:0% well sure let's try you want to deploy on<00:10:39.380> your<00:10:39.470> network<00:10:39.740> component<00:10:40.339> let's<00:10:40.730> do<00:10:40.939> an 00:10:41.170 --> 00:10:41.180 align:start position:0% on your network component let's do an 00:10:41.180 --> 00:10:42.879 align:start position:0% on your network component let's do an explorer<00:10:41.689> where<00:10:42.199> do<00:10:42.290> we<00:10:42.350> want<00:10:42.470> to<00:10:42.560> deploy<00:10:42.769> it 00:10:42.879 --> 00:10:42.889 align:start position:0% explorer where do we want to deploy it 00:10:42.889 --> 00:10:44.379 align:start position:0% explorer where do we want to deploy it well<00:10:43.040> we<00:10:43.160> will<00:10:43.279> put<00:10:43.459> everything<00:10:43.790> all<00:10:44.089> our<00:10:44.209> web 00:10:44.379 --> 00:10:44.389 align:start position:0% well we will put everything all our web 00:10:44.389 --> 00:10:45.970 align:start position:0% well we will put everything all our web sites<00:10:44.630> on<00:10:44.720> the<00:10:44.810> same<00:10:45.019> machine<00:10:45.199> so<00:10:45.529> let's<00:10:45.709> use 00:10:45.970 --> 00:10:45.980 align:start position:0% sites on the same machine so let's use 00:10:45.980 --> 00:10:48.730 align:start position:0% sites on the same machine so let's use DEFCON<00:10:46.459> Network<00:10:46.490> as<00:10:46.970> the<00:10:47.089> machine<00:10:47.589> yes<00:10:48.589> we 00:10:48.730 --> 00:10:48.740 align:start position:0% DEFCON Network as the machine yes we 00:10:48.740 --> 00:10:51.519 align:start position:0% DEFCON Network as the machine yes we want<00:10:48.920> to<00:10:49.009> porch<00:10:49.250> share<00:10:49.730> port<00:10:50.000> 80<00:10:50.240> and<00:10:50.630> that's 00:10:51.519 --> 00:10:51.529 align:start position:0% want to porch share port 80 and that's 00:10:51.529 --> 00:10:58.540 align:start position:0% want to porch share port 80 and that's the<00:10:55.240> network<00:10:56.889> where<00:10:57.889> should<00:10:58.069> the<00:10:58.189> data<00:10:58.370> be 00:10:58.540 --> 00:10:58.550 align:start position:0% the network where should the data be 00:10:58.550 --> 00:11:03.870 align:start position:0% the network where should the data be stored<00:10:59.860> and<00:11:01.029> the<00:11:02.029> defaults 00:11:03.870 --> 00:11:03.880 align:start position:0% stored and the defaults 00:11:03.880 --> 00:11:06.430 align:start position:0% stored and the defaults let's<00:11:04.880> call<00:11:05.060> it<00:11:05.240> on<00:11:05.390> explore<00:11:05.960> on<00:11:06.110> the<00:11:06.200> stats 00:11:06.430 --> 00:11:06.440 align:start position:0% let's call it on explore on the stats 00:11:06.440 --> 00:11:08.950 align:start position:0% let's call it on explore on the stats page<00:11:06.560> and<00:11:07.280> again<00:11:07.640> it's<00:11:07.880> pushing<00:11:08.600> it<00:11:08.780> out 00:11:08.950 --> 00:11:08.960 align:start position:0% page and again it's pushing it out 00:11:08.960 --> 00:11:09.910 align:start position:0% page and again it's pushing it out fairly<00:11:09.200> fast 00:11:09.910 --> 00:11:09.920 align:start position:0% fairly fast 00:11:09.920 --> 00:11:12.940 align:start position:0% fairly fast hopefully<00:11:11.050> I'm<00:11:12.050> just<00:11:12.200> waiting<00:11:12.560> for<00:11:12.590> the<00:11:12.800> node 00:11:12.940 --> 00:11:12.950 align:start position:0% hopefully I'm just waiting for the node 00:11:12.950 --> 00:11:15.190 align:start position:0% hopefully I'm just waiting for the node to<00:11:13.100> finish<00:11:13.340> booting<00:11:13.760> yeah<00:11:14.510> I'll<00:11:14.750> just<00:11:14.780> close 00:11:15.190 --> 00:11:15.200 align:start position:0% to finish booting yeah I'll just close 00:11:15.200 --> 00:11:17.530 align:start position:0% to finish booting yeah I'll just close it<00:11:15.350> and<00:11:15.530> that's<00:11:15.950> it<00:11:16.130> does<00:11:16.400> it<00:11:17.000> actually<00:11:17.300> work 00:11:17.530 --> 00:11:17.540 align:start position:0% it and that's it does it actually work 00:11:17.540 --> 00:11:20.190 align:start position:0% it and that's it does it actually work fingers<00:11:18.530> crossed 00:11:20.190 --> 00:11:20.200 align:start position:0% fingers crossed 00:11:20.200 --> 00:11:23.140 align:start position:0% fingers crossed yep<00:11:21.200> we<00:11:21.830> have<00:11:22.010> our<00:11:22.190> block<00:11:22.460> Explorer<00:11:22.820> up<00:11:22.970> and 00:11:23.140 --> 00:11:23.150 align:start position:0% yep we have our block Explorer up and 00:11:23.150 --> 00:11:24.820 align:start position:0% yep we have our block Explorer up and running<00:11:23.450> and<00:11:23.630> we<00:11:23.810> have<00:11:23.930> already<00:11:24.230> 11<00:11:24.620> blocks 00:11:24.820 --> 00:11:24.830 align:start position:0% running and we have already 11 blocks 00:11:24.830 --> 00:11:27.040 align:start position:0% running and we have already 11 blocks mind<00:11:25.280> and<00:11:25.970> you<00:11:26.090> can<00:11:26.240> check<00:11:26.420> that<00:11:26.630> our<00:11:26.780> miner 00:11:27.040 --> 00:11:27.050 align:start position:0% mind and you can check that our miner 00:11:27.050 --> 00:11:32.470 align:start position:0% mind and you can check that our miner already<00:11:27.680> has<00:11:30.550> 42<00:11:31.550> ether<00:11:31.850> that's<00:11:32.270> a<00:11:32.330> nice 00:11:32.470 --> 00:11:32.480 align:start position:0% already has 42 ether that's a nice 00:11:32.480 --> 00:11:34.960 align:start position:0% already has 42 ether that's a nice number<00:11:32.630> and<00:11:33.220> of<00:11:34.220> course<00:11:34.430> if<00:11:34.580> you<00:11:34.670> check<00:11:34.850> the 00:11:34.960 --> 00:11:34.970 align:start position:0% number and of course if you check the 00:11:34.970 --> 00:11:36.850 align:start position:0% number and of course if you check the network<00:11:35.120> stats<00:11:35.570> then<00:11:36.230> again 00:11:36.850 --> 00:11:36.860 align:start position:0% network stats then again 00:11:36.860 --> 00:11:38.800 align:start position:0% network stats then again you<00:11:37.220> already<00:11:37.520> have<00:11:37.790> three<00:11:38.150> machines<00:11:38.540> running 00:11:38.800 --> 00:11:38.810 align:start position:0% you already have three machines running 00:11:38.810 --> 00:11:41.460 align:start position:0% you already have three machines running without<00:11:39.530> actually<00:11:40.130> configuring<00:11:40.880> too<00:11:41.210> much 00:11:41.460 --> 00:11:41.470 align:start position:0% without actually configuring too much 00:11:41.470 --> 00:11:44.170 align:start position:0% without actually configuring too much okay<00:11:42.500> now<00:11:43.010> we<00:11:43.100> have<00:11:43.400> we<00:11:43.580> know<00:11:43.700> what<00:11:43.880> the<00:11:44.000> chain 00:11:44.170 --> 00:11:44.180 align:start position:0% okay now we have we know what the chain 00:11:44.180 --> 00:11:45.460 align:start position:0% okay now we have we know what the chain is<00:11:44.300> doing<00:11:44.510> from<00:11:44.720> the<00:11:44.810> inside<00:11:45.110> and<00:11:45.230> from<00:11:45.320> the 00:11:45.460 --> 00:11:45.470 align:start position:0% is doing from the inside and from the 00:11:45.470 --> 00:11:47.590 align:start position:0% is doing from the inside and from the outside<00:11:45.590> can<00:11:46.190> we<00:11:46.310> ask<00:11:46.460> our<00:11:46.670> friends<00:11:47.030> to<00:11:47.180> use<00:11:47.420> it 00:11:47.590 --> 00:11:47.600 align:start position:0% outside can we ask our friends to use it 00:11:47.600 --> 00:11:49.750 align:start position:0% outside can we ask our friends to use it well<00:11:47.810> sure<00:11:48.410> but<00:11:48.710> it's<00:11:49.010> kind<00:11:49.220> of<00:11:49.280> hard<00:11:49.550> to<00:11:49.610> use 00:11:49.750 --> 00:11:49.760 align:start position:0% well sure but it's kind of hard to use 00:11:49.760 --> 00:11:51.700 align:start position:0% well sure but it's kind of hard to use it<00:11:49.880> for<00:11:50.000> a<00:11:50.060> simple<00:11:50.720> client<00:11:50.870> so<00:11:51.230> let's<00:11:51.410> try<00:11:51.650> to 00:11:51.700 --> 00:11:51.710 align:start position:0% it for a simple client so let's try to 00:11:51.710 --> 00:11:54.100 align:start position:0% it for a simple client so let's try to give<00:11:51.890> them<00:11:52.070> a<00:11:52.130> web<00:11:52.310> wallet<00:11:52.670> now<00:11:53.570> of<00:11:53.870> course 00:11:54.100 --> 00:11:54.110 align:start position:0% give them a web wallet now of course 00:11:54.110 --> 00:11:56.530 align:start position:0% give them a web wallet now of course everybody<00:11:54.410> knows<00:11:54.710> the<00:11:55.010> most<00:11:55.940> sophisticated 00:11:56.530 --> 00:11:56.540 align:start position:0% everybody knows the most sophisticated 00:11:56.540 --> 00:11:58.630 align:start position:0% everybody knows the most sophisticated web<00:11:57.110> wallet<00:11:57.410> currently<00:11:57.770> out<00:11:57.890> there<00:11:58.220> is<00:11:58.430> my 00:11:58.630 --> 00:11:58.640 align:start position:0% web wallet currently out there is my 00:11:58.640 --> 00:12:00.460 align:start position:0% web wallet currently out there is my Easter<00:11:58.940> wallet<00:11:59.240> so<00:11:59.480> let's<00:11:59.810> just<00:11:59.960> deploy<00:12:00.230> my 00:12:00.460 --> 00:12:00.470 align:start position:0% Easter wallet so let's just deploy my 00:12:00.470 --> 00:12:02.140 align:start position:0% Easter wallet so let's just deploy my service<00:12:00.980> to<00:12:01.130> our<00:12:01.160> little<00:12:01.490> custom<00:12:01.940> test 00:12:02.140 --> 00:12:02.150 align:start position:0% service to our little custom test 00:12:02.150 --> 00:12:04.780 align:start position:0% service to our little custom test Network<00:12:02.480> so<00:12:03.080> that's<00:12:03.320> just<00:12:03.640> deploying<00:12:04.640> you 00:12:04.780 --> 00:12:04.790 align:start position:0% Network so that's just deploying you 00:12:04.790 --> 00:12:06.550 align:start position:0% Network so that's just deploying you network<00:12:05.120> component<00:12:05.660> you<00:12:05.990> want<00:12:06.080> to<00:12:06.230> deploy<00:12:06.500> a 00:12:06.550 --> 00:12:06.560 align:start position:0% network component you want to deploy a 00:12:06.560 --> 00:12:09.520 align:start position:0% network component you want to deploy a wallet<00:12:06.950> to<00:12:07.400> our<00:12:07.550> website<00:12:08.030> website<00:12:08.330> server<00:12:08.810> yes 00:12:09.520 --> 00:12:09.530 align:start position:0% wallet to our website website server yes 00:12:09.530 --> 00:12:15.120 align:start position:0% wallet to our website website server yes you<00:12:09.650> want<00:12:09.800> to<00:12:09.830> share<00:12:10.100> port<00:12:10.400> 80<00:12:10.670> and<00:12:11.030> call<00:12:11.780> it 00:12:15.120 --> 00:12:15.130 align:start position:0% 00:12:15.130 --> 00:12:24.940 align:start position:0% Network<00:12:16.180> why<00:12:17.180> should<00:12:17.390> we<00:12:17.510> store<00:12:17.780> them<00:12:20.710> and<00:12:23.950> the 00:12:24.940 --> 00:12:24.950 align:start position:0% Network why should we store them and the 00:12:24.950 --> 00:12:28.270 align:start position:0% Network why should we store them and the default<00:12:25.280> a<00:12:25.460> bit<00:12:25.610> and<00:12:26.390> that's<00:12:26.600> cool<00:12:26.840> our<00:12:27.280> wallet 00:12:28.270 --> 00:12:28.280 align:start position:0% default a bit and that's cool our wallet 00:12:28.280 --> 00:12:30.190 align:start position:0% default a bit and that's cool our wallet on<00:12:28.550> the<00:12:28.730> Status<00:12:29.000> page<00:12:29.060> since<00:12:29.570> that<00:12:29.720> one's<00:12:29.990> also 00:12:30.190 --> 00:12:30.200 align:start position:0% on the Status page since that one's also 00:12:30.200 --> 00:12:31.960 align:start position:0% on the Status page since that one's also back<00:12:30.530> and<00:12:30.740> no<00:12:30.860> let's<00:12:31.070> just<00:12:31.250> call<00:12:31.460> it<00:12:31.490> wallet 00:12:31.960 --> 00:12:31.970 align:start position:0% back and no let's just call it wallet 00:12:31.970 --> 00:12:35.140 align:start position:0% back and no let's just call it wallet and<00:12:32.900> the<00:12:33.080> campus<00:12:33.350> is<00:12:33.680> just<00:12:34.150> configuring 00:12:35.140 --> 00:12:35.150 align:start position:0% and the campus is just configuring 00:12:35.150 --> 00:12:36.640 align:start position:0% and the campus is just configuring everything<00:12:35.270> in<00:12:35.660> the<00:12:35.720> background<00:12:36.110> for<00:12:36.290> us<00:12:36.410> and 00:12:36.640 --> 00:12:36.650 align:start position:0% everything in the background for us and 00:12:36.650 --> 00:12:41.440 align:start position:0% everything in the background for us and it<00:12:36.770> is<00:12:36.950> pushing<00:12:37.160> out<00:12:37.460> the<00:12:37.760> data<00:12:37.970> and<00:12:40.000> if<00:12:41.000> we 00:12:41.440 --> 00:12:41.450 align:start position:0% it is pushing out the data and if we 00:12:41.450 --> 00:12:45.610 align:start position:0% it is pushing out the data and if we check<00:12:41.720> our<00:12:42.050> wallet<00:12:42.770> now<00:12:44.140> this<00:12:45.140> is<00:12:45.290> something 00:12:45.610 --> 00:12:45.620 align:start position:0% check our wallet now this is something 00:12:45.620 --> 00:12:47.140 align:start position:0% check our wallet now this is something that<00:12:45.650> takes<00:12:45.890> usually<00:12:46.310> the<00:12:46.400> most<00:12:46.520> time<00:12:46.820> to<00:12:47.000> boot 00:12:47.140 --> 00:12:47.150 align:start position:0% that takes usually the most time to boot 00:12:47.150 --> 00:12:51.220 align:start position:0% that takes usually the most time to boot up<00:12:48.070> yeah<00:12:49.070> boom<00:12:49.760> we<00:12:50.360> have<00:12:50.510> our<00:12:50.600> wallet<00:12:50.900> and<00:12:51.170> that 00:12:51.220 --> 00:12:51.230 align:start position:0% up yeah boom we have our wallet and that 00:12:51.230 --> 00:12:53.440 align:start position:0% up yeah boom we have our wallet and that UK<00:12:51.920> as<00:12:52.040> you<00:12:52.130> can<00:12:52.280> see<00:12:52.490> it<00:12:52.940> is<00:12:53.120> actually 00:12:53.440 --> 00:12:53.450 align:start position:0% UK as you can see it is actually 00:12:53.450 --> 00:12:55.390 align:start position:0% UK as you can see it is actually configured<00:12:53.900> for<00:12:54.140> the<00:12:54.260> DEF<00:12:54.440> CON<00:12:54.650> Network<00:12:54.710> it 00:12:55.390 --> 00:12:55.400 align:start position:0% configured for the DEF CON Network it 00:12:55.400 --> 00:12:57.310 align:start position:0% configured for the DEF CON Network it deployed<00:12:55.880> a<00:12:56.000> back-end<00:12:56.210> node<00:12:56.570> to<00:12:56.750> connect<00:12:57.050> to 00:12:57.310 --> 00:12:57.320 align:start position:0% deployed a back-end node to connect to 00:12:57.320 --> 00:12:59.050 align:start position:0% deployed a back-end node to connect to we<00:12:57.500> have<00:12:57.650> the<00:12:57.770> front-end<00:12:58.280> and<00:12:58.400> everything 00:12:59.050 --> 00:12:59.060 align:start position:0% we have the front-end and everything 00:12:59.060 --> 00:13:03.550 align:start position:0% we have the front-end and everything seems<00:12:59.600> to<00:12:59.690> work<00:12:59.930> nicely<00:13:00.760> cool<00:13:01.810> so<00:13:02.810> that<00:13:03.320> one 00:13:03.550 --> 00:13:03.560 align:start position:0% seems to work nicely cool so that one 00:13:03.560 --> 00:13:05.590 align:start position:0% seems to work nicely cool so that one kind<00:13:03.980> of<00:13:04.040> was<00:13:04.250> easy<00:13:04.550> enough<00:13:04.790> to<00:13:04.850> deploy<00:13:05.300> all 00:13:05.590 --> 00:13:05.600 align:start position:0% kind of was easy enough to deploy all 00:13:05.600 --> 00:13:07.660 align:start position:0% kind of was easy enough to deploy all the<00:13:05.780> components<00:13:06.380> but<00:13:06.560> if<00:13:06.800> you<00:13:06.980> share<00:13:07.310> this 00:13:07.660 --> 00:13:07.670 align:start position:0% the components but if you share this 00:13:07.670 --> 00:13:09.820 align:start position:0% the components but if you share this with<00:13:07.910> your<00:13:08.060> friend<00:13:08.360> then<00:13:08.810> he'll<00:13:09.410> say<00:13:09.680> that 00:13:09.820 --> 00:13:09.830 align:start position:0% with your friend then he'll say that 00:13:09.830 --> 00:13:12.010 align:start position:0% with your friend then he'll say that okay<00:13:10.100> I<00:13:10.130> want<00:13:10.460> either<00:13:10.670> and<00:13:11.060> you<00:13:11.600> will<00:13:11.780> be<00:13:11.900> the 00:13:12.010 --> 00:13:12.020 align:start position:0% okay I want either and you will be the 00:13:12.020 --> 00:13:13.690 align:start position:0% okay I want either and you will be the one<00:13:12.140> who<00:13:12.380> has<00:13:12.560> to<00:13:12.770> give<00:13:12.920> them<00:13:13.160> ether<00:13:13.370> all<00:13:13.580> the 00:13:13.690 --> 00:13:13.700 align:start position:0% one who has to give them ether all the 00:13:13.700 --> 00:13:14.519 align:start position:0% one who has to give them ether all the time<00:13:13.940> which 00:13:14.519 --> 00:13:14.529 align:start position:0% time which 00:13:14.529 --> 00:13:16.650 align:start position:0% time which boring<00:13:14.920> really<00:13:15.069> fast<00:13:15.399> so<00:13:16.089> we<00:13:16.269> really<00:13:16.480> need<00:13:16.629> a 00:13:16.650 --> 00:13:16.660 align:start position:0% boring really fast so we really need a 00:13:16.660 --> 00:13:18.689 align:start position:0% boring really fast so we really need a faucet<00:13:17.170> that<00:13:17.319> you<00:13:17.470> can<00:13:17.620> just<00:13:17.829> start<00:13:18.129> up<00:13:18.310> and<00:13:18.550> it 00:13:18.689 --> 00:13:18.699 align:start position:0% faucet that you can just start up and it 00:13:18.699 --> 00:13:20.220 align:start position:0% faucet that you can just start up and it just<00:13:18.970> runs<00:13:19.300> there<00:13:19.569> and<00:13:19.720> everybody<00:13:20.079> can 00:13:20.220 --> 00:13:20.230 align:start position:0% just runs there and everybody can 00:13:20.230 --> 00:13:23.220 align:start position:0% just runs there and everybody can request<00:13:20.560> ether<00:13:21.040> and<00:13:21.399> to<00:13:22.329> do<00:13:22.449> that<00:13:22.629> we<00:13:23.050> have 00:13:23.220 --> 00:13:23.230 align:start position:0% request ether and to do that we have 00:13:23.230 --> 00:13:26.100 align:start position:0% request ether and to do that we have actually<00:13:23.680> go<00:13:24.550> a<00:13:24.579> theorem<00:13:24.970> has<00:13:25.120> a<00:13:25.180> faucet<00:13:25.810> built 00:13:26.100 --> 00:13:26.110 align:start position:0% actually go a theorem has a faucet built 00:13:26.110 --> 00:13:28.199 align:start position:0% actually go a theorem has a faucet built in<00:13:26.379> or<00:13:26.740> support<00:13:27.069> for<00:13:27.430> it<00:13:27.519> based<00:13:27.759> on<00:13:27.939> the<00:13:28.060> light 00:13:28.199 --> 00:13:28.209 align:start position:0% in or support for it based on the light 00:13:28.209 --> 00:13:30.840 align:start position:0% in or support for it based on the light client<00:13:28.689> so<00:13:29.350> let's<00:13:29.560> ask<00:13:29.800> Papa<00:13:30.129> to<00:13:30.220> deploy<00:13:30.639> that 00:13:30.840 --> 00:13:30.850 align:start position:0% client so let's ask Papa to deploy that 00:13:30.850 --> 00:13:32.369 align:start position:0% client so let's ask Papa to deploy that yep<00:13:31.180> we<00:13:31.360> want<00:13:31.540> to<00:13:31.600> deploy<00:13:31.809> a<00:13:31.899> new<00:13:31.930> network 00:13:32.369 --> 00:13:32.379 align:start position:0% yep we want to deploy a new network 00:13:32.379 --> 00:13:35.999 align:start position:0% yep we want to deploy a new network component<00:13:33.249> and<00:13:33.730> let's<00:13:34.689> do<00:13:34.899> faucet<00:13:35.439> that's<00:13:35.769> our 00:13:35.999 --> 00:13:36.009 align:start position:0% component and let's do faucet that's our 00:13:36.009 --> 00:13:38.429 align:start position:0% component and let's do faucet that's our sixth<00:13:36.430> on<00:13:36.699> the<00:13:36.759> list<00:13:37.059> and<00:13:37.959> we<00:13:38.079> want<00:13:38.230> to<00:13:38.319> deploy 00:13:38.429 --> 00:13:38.439 align:start position:0% sixth on the list and we want to deploy 00:13:38.439 --> 00:13:40.829 align:start position:0% sixth on the list and we want to deploy it<00:13:38.589> again<00:13:38.920> onto<00:13:39.100> our<00:13:39.370> web<00:13:39.819> server<00:13:40.120> we<00:13:40.540> deployed 00:13:40.829 --> 00:13:40.839 align:start position:0% it again onto our web server we deployed 00:13:40.839 --> 00:13:44.220 align:start position:0% it again onto our web server we deployed everything<00:13:41.259> there<00:13:41.499> faucet<00:13:42.189> DEFCON<00:13:43.059> that<00:13:43.509> work 00:13:44.220 --> 00:13:44.230 align:start position:0% everything there faucet DEFCON that work 00:13:44.230 --> 00:13:48.210 align:start position:0% everything there faucet DEFCON that work domain<00:13:44.920> name<00:13:46.980> sorry 00:13:48.210 --> 00:13:48.220 align:start position:0% domain name sorry 00:13:48.220 --> 00:14:03.480 align:start position:0% domain name sorry port<00:13:48.730> 81st<00:13:49.269> and<00:13:49.629> then<00:13:53.879> thank<00:13:54.879> you<00:14:01.949> okay<00:14:02.949> how 00:14:03.480 --> 00:14:03.490 align:start position:0% port 81st and then thank you okay how 00:14:03.490 --> 00:14:05.249 align:start position:0% port 81st and then thank you okay how many<00:14:03.670> do<00:14:04.089> we<00:14:04.120> want<00:14:04.360> to<00:14:04.509> the<00:14:04.569> faucet<00:14:04.930> to<00:14:04.959> release 00:14:05.249 --> 00:14:05.259 align:start position:0% many do we want to the faucet to release 00:14:05.259 --> 00:14:07.429 align:start position:0% many do we want to the faucet to release well<00:14:05.470> one<00:14:05.649> if<00:14:05.769> there<00:14:05.949> is<00:14:06.069> fine<00:14:06.309> for<00:14:06.639> 50<00:14:07.029> minutes 00:14:07.429 --> 00:14:07.439 align:start position:0% well one if there is fine for 50 minutes 00:14:07.439 --> 00:14:10.259 align:start position:0% well one if there is fine for 50 minutes we<00:14:08.439> want<00:14:08.800> three<00:14:09.160> tiers<00:14:09.459> if<00:14:09.670> you<00:14:09.759> wait<00:14:09.939> more<00:14:10.149> you 00:14:10.259 --> 00:14:10.269 align:start position:0% we want three tiers if you wait more you 00:14:10.269 --> 00:14:12.150 align:start position:0% we want three tiers if you wait more you get<00:14:10.420> more<00:14:10.480> ether<00:14:10.809> do<00:14:11.439> we<00:14:11.529> want<00:14:11.649> recapture 00:14:12.150 --> 00:14:12.160 align:start position:0% get more ether do we want recapture 00:14:12.160 --> 00:14:14.670 align:start position:0% get more ether do we want recapture protection<00:14:12.670> against<00:14:13.059> bots<00:14:13.360> no<00:14:14.110> it's<00:14:14.379> the<00:14:14.499> test 00:14:14.670 --> 00:14:14.680 align:start position:0% protection against bots no it's the test 00:14:14.680 --> 00:14:16.230 align:start position:0% protection against bots no it's the test Network<00:14:15.009> here<00:14:15.249> for<00:14:15.430> DEFCON<00:14:15.759> we<00:14:15.879> don't<00:14:16.059> care 00:14:16.230 --> 00:14:16.240 align:start position:0% Network here for DEFCON we don't care 00:14:16.240 --> 00:14:18.809 align:start position:0% Network here for DEFCON we don't care about<00:14:16.269> robots<00:14:17.249> where<00:14:18.249> should<00:14:18.399> we<00:14:18.490> store<00:14:18.699> the 00:14:18.809 --> 00:14:18.819 align:start position:0% about robots where should we store the 00:14:18.819 --> 00:14:19.340 align:start position:0% about robots where should we store the data 00:14:19.340 --> 00:14:19.350 align:start position:0% data 00:14:19.350 --> 00:14:22.790 align:start position:0% data DEFCON<00:14:20.350> Fawcett<00:14:21.250> sounds<00:14:21.730> about<00:14:21.910> right<00:14:21.939> and 00:14:22.790 --> 00:14:22.800 align:start position:0% DEFCON Fawcett sounds about right and 00:14:22.800 --> 00:14:27.079 align:start position:0% DEFCON Fawcett sounds about right and just<00:14:23.800> pick<00:14:24.009> a<00:14:24.720> different<00:14:25.720> port<00:14:26.350> for<00:14:26.620> this<00:14:26.769> one 00:14:27.079 --> 00:14:27.089 align:start position:0% just pick a different port for this one 00:14:27.089 --> 00:14:29.670 align:start position:0% just pick a different port for this one what<00:14:28.089> shouldn't<00:14:28.389> possibly<00:14:28.930> code<00:14:29.110> on<00:14:29.290> a<00:14:29.319> static 00:14:29.670 --> 00:14:29.680 align:start position:0% what shouldn't possibly code on a static 00:14:29.680 --> 00:14:35.879 align:start position:0% what shouldn't possibly code on a static page<00:14:33.149> of<00:14:34.149> course<00:14:34.600> if<00:14:34.839> I<00:14:35.019> run<00:14:35.199> a<00:14:35.230> faucet<00:14:35.709> I<00:14:35.829> do 00:14:35.879 --> 00:14:35.889 align:start position:0% page of course if I run a faucet I do 00:14:35.889 --> 00:14:38.309 align:start position:0% page of course if I run a faucet I do need<00:14:36.250> a<00:14:36.610> private<00:14:37.240> key<00:14:37.420> so<00:14:37.660> that<00:14:37.779> the<00:14:37.959> faucet 00:14:38.309 --> 00:14:38.319 align:start position:0% need a private key so that the faucet 00:14:38.319 --> 00:14:40.619 align:start position:0% need a private key so that the faucet can<00:14:38.470> actually<00:14:38.889> fund<00:14:39.160> its<00:14:39.430> stuff<00:14:39.670> out<00:14:39.850> of<00:14:39.879> so<00:14:40.600> we 00:14:40.619 --> 00:14:40.629 align:start position:0% can actually fund its stuff out of so we 00:14:40.629 --> 00:14:42.960 align:start position:0% can actually fund its stuff out of so we have<00:14:40.930> a<00:14:40.959> private<00:14:41.379> key<00:14:41.559> paste<00:14:41.949> it<00:14:42.129> in<00:14:42.279> here<00:14:42.550> we 00:14:42.960 --> 00:14:42.970 align:start position:0% have a private key paste it in here we 00:14:42.970 --> 00:14:45.449 align:start position:0% have a private key paste it in here we have<00:14:43.120> to<00:14:43.240> unlock<00:14:43.509> it<00:14:43.569> for<00:14:43.839> the<00:14:43.959> faucet<00:14:44.430> boom 00:14:45.449 --> 00:14:45.459 align:start position:0% have to unlock it for the faucet boom 00:14:45.459 --> 00:14:47.040 align:start position:0% have to unlock it for the faucet boom it's<00:14:45.639> unlocked<00:14:45.939> and<00:14:46.180> do<00:14:46.750> we<00:14:46.839> allow 00:14:47.040 --> 00:14:47.050 align:start position:0% it's unlocked and do we allow 00:14:47.050 --> 00:14:49.530 align:start position:0% it's unlocked and do we allow unauthorized<00:14:47.949> requests<00:14:48.790> well<00:14:49.000> since<00:14:49.300> it's<00:14:49.480> a 00:14:49.530 --> 00:14:49.540 align:start position:0% unauthorized requests well since it's a 00:14:49.540 --> 00:14:51.269 align:start position:0% unauthorized requests well since it's a Def<00:14:49.720> Con<00:14:49.959> and<00:14:49.990> we<00:14:50.230> don't<00:14:50.410> care<00:14:50.649> about<00:14:50.949> the<00:14:51.129> life 00:14:51.269 --> 00:14:51.279 align:start position:0% Def Con and we don't care about the life 00:14:51.279 --> 00:14:53.429 align:start position:0% Def Con and we don't care about the life time<00:14:51.670> of<00:14:51.699> the<00:14:51.910> this<00:14:52.509> whole<00:14:52.689> network<00:14:53.079> so<00:14:53.290> much 00:14:53.429 --> 00:14:53.439 align:start position:0% time of the this whole network so much 00:14:53.439 --> 00:14:56.689 align:start position:0% time of the this whole network so much yes<00:14:53.740> we<00:14:53.920> authorize<00:14:54.399> anyone<00:14:54.819> to<00:14:55.059> request<00:14:55.839> funds 00:14:56.689 --> 00:14:56.699 align:start position:0% yes we authorize anyone to request funds 00:14:56.699 --> 00:15:06.210 align:start position:0% yes we authorize anyone to request funds and<00:15:02.100> that's<00:15:03.100> nice<00:15:03.839> and<00:15:04.839> now<00:15:05.079> comes<00:15:05.949> the<00:15:06.069> moment 00:15:06.210 --> 00:15:06.220 align:start position:0% and that's nice and now comes the moment 00:15:06.220 --> 00:15:06.749 align:start position:0% and that's nice and now comes the moment of<00:15:06.429> truth 00:15:06.749 --> 00:15:06.759 align:start position:0% of truth 00:15:06.759 --> 00:15:09.360 align:start position:0% of truth can<00:15:07.569> we<00:15:07.750> actually<00:15:08.139> as<00:15:08.290> you<00:15:08.410> say<00:15:08.620> again<00:15:09.100> we<00:15:09.250> have 00:15:09.360 --> 00:15:09.370 align:start position:0% can we actually as you say again we have 00:15:09.370 --> 00:15:11.239 align:start position:0% can we actually as you say again we have a<00:15:09.399> nice<00:15:09.550> dump<00:15:09.850> of<00:15:10.000> all<00:15:10.089> the<00:15:10.269> configurations 00:15:11.239 --> 00:15:11.249 align:start position:0% a nice dump of all the configurations 00:15:11.249 --> 00:15:16.100 align:start position:0% a nice dump of all the configurations now<00:15:12.249> can<00:15:12.550> we<00:15:12.699> actually<00:15:12.910> load<00:15:13.779> up<00:15:14.019> the<00:15:14.230> faucet 00:15:16.100 --> 00:15:16.110 align:start position:0% now can we actually load up the faucet 00:15:16.110 --> 00:15:17.689 align:start position:0% now can we actually load up the faucet yep 00:15:17.689 --> 00:15:17.699 align:start position:0% yep 00:15:17.699 --> 00:15:20.340 align:start position:0% yep is<00:15:18.699> it<00:15:18.879> yep<00:15:19.329> we<00:15:19.689> have<00:15:19.870> a<00:15:19.899> Def<00:15:20.139> Con 00:15:20.340 --> 00:15:20.350 align:start position:0% is it yep we have a Def Con 00:15:20.350 --> 00:15:22.619 align:start position:0% is it yep we have a Def Con authenticated<00:15:21.069> faucet<00:15:21.429> and<00:15:21.639> if<00:15:22.179> we<00:15:22.329> request 00:15:22.619 --> 00:15:22.629 align:start position:0% authenticated faucet and if we request 00:15:22.629 --> 00:15:30.270 align:start position:0% authenticated faucet and if we request funds<00:15:22.990> now 00:15:30.270 --> 00:15:30.280 align:start position:0% 00:15:30.280 --> 00:15:34.180 align:start position:0% into<00:15:31.280> an<00:15:31.430> ether<00:15:31.730> address<00:15:32.420> give<00:15:33.410> me<00:15:33.530> one<00:15:33.740> ether 00:15:34.180 --> 00:15:34.190 align:start position:0% into an ether address give me one ether 00:15:34.190 --> 00:15:36.460 align:start position:0% into an ether address give me one ether yep<00:15:35.000> the<00:15:35.270> faucet<00:15:35.600> accepted<00:15:35.990> our<00:15:36.080> funding 00:15:36.460 --> 00:15:36.470 align:start position:0% yep the faucet accepted our funding 00:15:36.470 --> 00:15:38.950 align:start position:0% yep the faucet accepted our funding request<00:15:36.800> and<00:15:37.100> if<00:15:37.370> the<00:15:37.550> minor<00:15:37.760> manages<00:15:38.330> to<00:15:38.540> mine 00:15:38.950 --> 00:15:38.960 align:start position:0% request and if the minor manages to mine 00:15:38.960 --> 00:15:42.220 align:start position:0% request and if the minor manages to mine us<00:15:39.230> a<00:15:39.260> few<00:15:39.770> blocks<00:15:40.040> yep<00:15:40.820> we<00:15:41.420> just<00:15:41.600> mined<00:15:41.810> it<00:15:41.990> and 00:15:42.220 --> 00:15:42.230 align:start position:0% us a few blocks yep we just mined it and 00:15:42.230 --> 00:15:45.490 align:start position:0% us a few blocks yep we just mined it and we<00:15:42.500> have<00:15:42.710> our<00:15:42.920> account<00:15:43.310> funded<00:15:44.200> and<00:15:45.200> we<00:15:45.380> can 00:15:45.490 --> 00:15:45.500 align:start position:0% we have our account funded and we can 00:15:45.500 --> 00:15:47.200 align:start position:0% we have our account funded and we can also<00:15:45.650> check<00:15:45.920> the<00:15:46.040> stats<00:15:46.280> page<00:15:46.490> that 00:15:47.200 --> 00:15:47.210 align:start position:0% also check the stats page that 00:15:47.210 --> 00:15:48.730 align:start position:0% also check the stats page that everything<00:15:47.600> that<00:15:47.750> we<00:15:47.870> deployed<00:15:48.260> on<00:15:48.380> till<00:15:48.560> now 00:15:48.730 --> 00:15:48.740 align:start position:0% everything that we deployed on till now 00:15:48.740 --> 00:15:50.910 align:start position:0% everything that we deployed on till now have<00:15:49.220> indeed<00:15:49.640> appeared<00:15:50.090> on<00:15:50.300> the<00:15:50.420> Status<00:15:50.720> page 00:15:50.910 --> 00:15:50.920 align:start position:0% have indeed appeared on the Status page 00:15:50.920 --> 00:15:54.700 align:start position:0% have indeed appeared on the Status page now<00:15:51.920> finally<00:15:52.420> you<00:15:53.420> deployed<00:15:53.720> everything<00:15:54.380> but 00:15:54.700 --> 00:15:54.710 align:start position:0% now finally you deployed everything but 00:15:54.710 --> 00:15:56.710 align:start position:0% now finally you deployed everything but you<00:15:55.520> don't<00:15:55.730> even<00:15:55.910> know<00:15:56.060> what<00:15:56.210> your<00:15:56.330> Genesis 00:15:56.710 --> 00:15:56.720 align:start position:0% you don't even know what your Genesis 00:15:56.720 --> 00:15:58.270 align:start position:0% you don't even know what your Genesis block<00:15:56.870> is<00:15:57.170> you<00:15:57.380> don't<00:15:57.560> know<00:15:57.680> how<00:15:57.830> to<00:15:57.890> connect 00:15:58.270 --> 00:15:58.280 align:start position:0% block is you don't know how to connect 00:15:58.280 --> 00:16:00.730 align:start position:0% block is you don't know how to connect to<00:15:58.430> it<00:15:58.550> and<00:15:58.730> it's<00:15:59.570> just<00:15:59.810> a<00:15:59.930> mass<00:16:00.140> of<00:16:00.170> different 00:16:00.730 --> 00:16:00.740 align:start position:0% to it and it's just a mass of different 00:16:00.740 --> 00:16:02.440 align:start position:0% to it and it's just a mass of different websites<00:16:00.920> on<00:16:01.310> different<00:16:01.640> domains<00:16:01.970> so<00:16:02.390> you 00:16:02.440 --> 00:16:02.450 align:start position:0% websites on different domains so you 00:16:02.450 --> 00:16:04.150 align:start position:0% websites on different domains so you really<00:16:02.810> want<00:16:03.050> to<00:16:03.230> deploy<00:16:03.470> everything<00:16:03.860> on<00:16:04.130> a 00:16:04.150 --> 00:16:04.160 align:start position:0% really want to deploy everything on a 00:16:04.160 --> 00:16:06.310 align:start position:0% really want to deploy everything on a single<00:16:04.550> host<00:16:04.760> or<00:16:05.300> at<00:16:05.480> least<00:16:05.690> on<00:16:05.840> a<00:16:05.870> single 00:16:06.310 --> 00:16:06.320 align:start position:0% single host or at least on a single 00:16:06.320 --> 00:16:08.680 align:start position:0% single host or at least on a single place<00:16:06.830> that<00:16:07.100> your<00:16:07.550> users<00:16:07.910> could<00:16:08.120> find<00:16:08.360> it<00:16:08.540> and 00:16:08.680 --> 00:16:08.690 align:start position:0% place that your users could find it and 00:16:08.690 --> 00:16:10.660 align:start position:0% place that your users could find it and the<00:16:09.350> only<00:16:09.440> way<00:16:09.590> to<00:16:09.650> do<00:16:09.860> that<00:16:09.890> is<00:16:10.310> to<00:16:10.490> have<00:16:10.640> a 00:16:10.660 --> 00:16:10.670 align:start position:0% the only way to do that is to have a 00:16:10.670 --> 00:16:13.240 align:start position:0% the only way to do that is to have a nice<00:16:10.940> dashboard<00:16:11.360> and<00:16:11.870> that<00:16:12.380> is<00:16:12.560> actually<00:16:13.160> the 00:16:13.240 --> 00:16:13.250 align:start position:0% nice dashboard and that is actually the 00:16:13.250 --> 00:16:16.000 align:start position:0% nice dashboard and that is actually the last<00:16:13.370> thing<00:16:13.610> that<00:16:14.290> what<00:16:15.290> that<00:16:15.320> can<00:16:15.740> do 00:16:16.000 --> 00:16:16.010 align:start position:0% last thing that what that can do 00:16:16.010 --> 00:16:17.190 align:start position:0% last thing that what that can do currently 00:16:17.190 --> 00:16:17.200 align:start position:0% currently 00:16:17.200 --> 00:16:20.440 align:start position:0% currently let's<00:16:18.200> just<00:16:18.350> try<00:16:18.530> to<00:16:18.590> do<00:16:18.800> that<00:16:19.270> we're<00:16:20.270> just 00:16:20.440 --> 00:16:20.450 align:start position:0% let's just try to do that we're just 00:16:20.450 --> 00:16:21.970 align:start position:0% let's just try to do that we're just having<00:16:20.720> a<00:16:20.780> nice<00:16:20.930> yep 00:16:21.970 --> 00:16:21.980 align:start position:0% having a nice yep 00:16:21.980 --> 00:16:25.210 align:start position:0% having a nice yep deploy<00:16:22.640> a<00:16:22.910> new<00:16:22.940> network<00:16:23.720> component<00:16:24.410> and<00:16:24.590> find 00:16:25.210 --> 00:16:25.220 align:start position:0% deploy a new network component and find 00:16:25.220 --> 00:16:26.830 align:start position:0% deploy a new network component and find a<00:16:25.310> piece<00:16:25.490> of<00:16:25.640> the<00:16:25.730> puzzle<00:16:25.880> is<00:16:26.180> a<00:16:26.210> dashboard 00:16:26.830 --> 00:16:26.840 align:start position:0% a piece of the puzzle is a dashboard 00:16:26.840 --> 00:16:30.310 align:start position:0% a piece of the puzzle is a dashboard let's<00:16:27.620> deploy<00:16:27.890> it<00:16:28.010> to<00:16:28.040> our<00:16:28.220> website<00:16:28.400> and<00:16:29.320> let's 00:16:30.310 --> 00:16:30.320 align:start position:0% let's deploy it to our website and let's 00:16:30.320 --> 00:16:32.830 align:start position:0% let's deploy it to our website and let's use<00:16:30.620> a<00:16:30.650> root<00:16:30.950> domain<00:16:31.280> DEFCON<00:16:31.790> Network<00:16:31.820> for<00:16:32.750> it 00:16:32.830 --> 00:16:32.840 align:start position:0% use a root domain DEFCON Network for it 00:16:32.840 --> 00:16:35.050 align:start position:0% use a root domain DEFCON Network for it and<00:16:33.530> then<00:16:33.710> it<00:16:33.830> will<00:16:33.950> ask<00:16:34.130> which<00:16:34.370> services<00:16:34.880> do<00:16:34.970> I 00:16:35.050 --> 00:16:35.060 align:start position:0% and then it will ask which services do I 00:16:35.060 --> 00:16:36.880 align:start position:0% and then it will ask which services do I want<00:16:35.270> to<00:16:35.390> list<00:16:35.570> yeah<00:16:36.080> I<00:16:36.290> want<00:16:36.530> to<00:16:36.620> list<00:16:36.770> the 00:16:36.880 --> 00:16:36.890 align:start position:0% want to list yeah I want to list the 00:16:36.890 --> 00:16:39.820 align:start position:0% want to list yeah I want to list the stat<00:16:37.100> page<00:16:37.400> I<00:16:38.080> want<00:16:39.080> to<00:16:39.170> list<00:16:39.350> the<00:16:39.620> block 00:16:39.820 --> 00:16:39.830 align:start position:0% stat page I want to list the block 00:16:39.830 --> 00:16:43.060 align:start position:0% stat page I want to list the block Explorer<00:16:40.280> I<00:16:41.170> want<00:16:42.170> to<00:16:42.260> list<00:16:42.440> the<00:16:42.590> web<00:16:42.740> wallet 00:16:43.060 --> 00:16:43.070 align:start position:0% Explorer I want to list the web wallet 00:16:43.070 --> 00:16:48.370 align:start position:0% Explorer I want to list the web wallet and<00:16:43.460> I<00:16:44.450> want<00:16:45.110> to<00:16:45.290> list<00:16:46.090> the<00:16:47.090> faucet<00:16:47.450> and<00:16:47.720> we 00:16:48.370 --> 00:16:48.380 align:start position:0% and I want to list the faucet and we 00:16:48.380 --> 00:16:50.440 align:start position:0% and I want to list the faucet and we want<00:16:48.560> the<00:16:48.620> East<00:16:48.800> a<00:16:48.950> secret<00:16:49.310> to<00:16:49.400> be<00:16:49.490> public<00:16:49.880> yes 00:16:50.440 --> 00:16:50.450 align:start position:0% want the East a secret to be public yes 00:16:50.450 --> 00:16:53.710 align:start position:0% want the East a secret to be public yes let's<00:16:51.140> make<00:16:51.290> it<00:16:51.350> public<00:16:51.800> and<00:16:52.600> pocket<00:16:53.600> again 00:16:53.710 --> 00:16:53.720 align:start position:0% let's make it public and pocket again 00:16:53.720 --> 00:16:55.210 align:start position:0% let's make it public and pocket again crunches<00:16:54.410> everything<00:16:54.800> makes<00:16:54.980> the 00:16:55.210 --> 00:16:55.220 align:start position:0% crunches everything makes the 00:16:55.220 --> 00:16:57.910 align:start position:0% crunches everything makes the configuration<00:16:55.820> files<00:16:56.120> deploys<00:16:56.720> a<00:16:57.170> web<00:16:57.620> server 00:16:57.910 --> 00:16:57.920 align:start position:0% configuration files deploys a web server 00:16:57.920 --> 00:17:02.230 align:start position:0% configuration files deploys a web server for<00:16:58.280> us<00:16:58.430> and<00:16:58.730> if<00:17:00.910> everything<00:17:01.910> worked 00:17:02.230 --> 00:17:02.240 align:start position:0% for us and if everything worked 00:17:02.240 --> 00:17:04.720 align:start position:0% for us and if everything worked correctly<00:17:02.510> I<00:17:03.170> should<00:17:03.590> be<00:17:03.770> able<00:17:03.920> to<00:17:04.130> load<00:17:04.430> up 00:17:04.720 --> 00:17:04.730 align:start position:0% correctly I should be able to load up 00:17:04.730 --> 00:17:08.530 align:start position:0% correctly I should be able to load up nice<00:17:05.090> dashboard<00:17:05.920> yep<00:17:06.920> and<00:17:07.160> we<00:17:07.850> have<00:17:08.030> the<00:17:08.240> first 00:17:08.530 --> 00:17:08.540 align:start position:0% nice dashboard yep and we have the first 00:17:08.540 --> 00:17:11.320 align:start position:0% nice dashboard yep and we have the first page<00:17:08.780> we<00:17:08.959> have<00:17:09.110> the<00:17:09.160> eat<00:17:10.160> stat<00:17:10.490> on<00:17:10.850> the 00:17:11.320 --> 00:17:11.330 align:start position:0% page we have the eat stat on the 00:17:11.330 --> 00:17:13.390 align:start position:0% page we have the eat stat on the left-hand<00:17:11.959> side<00:17:12.050> we<00:17:12.290> have<00:17:12.410> a<00:17:12.440> nice<00:17:12.620> sidebar 00:17:13.390 --> 00:17:13.400 align:start position:0% left-hand side we have a nice sidebar 00:17:13.400 --> 00:17:15.460 align:start position:0% left-hand side we have a nice sidebar many<00:17:13.610> where<00:17:13.760> we<00:17:13.910> can<00:17:14.120> switch<00:17:14.840> between<00:17:15.020> the<00:17:15.350> eat 00:17:15.460 --> 00:17:15.470 align:start position:0% many where we can switch between the eat 00:17:15.470 --> 00:17:17.350 align:start position:0% many where we can switch between the eat stat<00:17:15.890> we<00:17:16.190> have<00:17:16.340> the<00:17:16.550> block<00:17:16.760> as<00:17:16.910> well<00:17:16.940> that<00:17:17.240> we 00:17:17.350 --> 00:17:17.360 align:start position:0% stat we have the block as well that we 00:17:17.360 --> 00:17:20.320 align:start position:0% stat we have the block as well that we just<00:17:17.570> configured<00:17:17.870> we<00:17:18.590> have<00:17:18.800> our<00:17:19.130> web<00:17:19.970> wallet 00:17:20.320 --> 00:17:20.330 align:start position:0% just configured we have our web wallet 00:17:20.330 --> 00:17:22.210 align:start position:0% just configured we have our web wallet that<00:17:20.690> we<00:17:20.840> can<00:17:21.020> play<00:17:21.230> around<00:17:21.350> with<00:17:21.650> we<00:17:21.950> have<00:17:22.070> the 00:17:22.210 --> 00:17:22.220 align:start position:0% that we can play around with we have the 00:17:22.220 --> 00:17:24.070 align:start position:0% that we can play around with we have the faucet<00:17:22.610> to<00:17:22.790> request<00:17:23.360> all<00:17:23.540> the<00:17:23.570> funds<00:17:23.870> that<00:17:24.020> you 00:17:24.070 --> 00:17:24.080 align:start position:0% faucet to request all the funds that you 00:17:24.080 --> 00:17:28.460 align:start position:0% faucet to request all the funds that you owe<00:17:24.350> people<00:17:24.709> are<00:17:24.950> requesting<00:17:25.160> funds<00:17:25.550> amazing 00:17:28.460 --> 00:17:28.470 align:start position:0% 00:17:28.470 --> 00:17:36.390 align:start position:0% and<00:17:32.640> and<00:17:33.640> beside<00:17:34.330> beside<00:17:35.290> all<00:17:36.100> of<00:17:36.280> these 00:17:36.390 --> 00:17:36.400 align:start position:0% and and beside beside all of these 00:17:36.400 --> 00:17:38.990 align:start position:0% and and beside beside all of these services<00:17:36.790> as<00:17:36.940> we<00:17:37.059> configure<00:17:37.480> we<00:17:37.990> also<00:17:38.170> have 00:17:38.990 --> 00:17:39.000 align:start position:0% services as we configure we also have 00:17:39.000 --> 00:17:41.910 align:start position:0% services as we configure we also have detailed<00:17:40.000> guide<00:17:40.270> on<00:17:40.630> how<00:17:41.320> to<00:17:41.380> connect<00:17:41.740> go 00:17:41.910 --> 00:17:41.920 align:start position:0% detailed guide on how to connect go 00:17:41.920 --> 00:17:44.430 align:start position:0% detailed guide on how to connect go etherium<00:17:42.340> in<00:17:42.580> archive<00:17:43.390> node<00:17:43.630> full<00:17:43.900> node<00:17:44.110> live 00:17:44.430 --> 00:17:44.440 align:start position:0% etherium in archive node full node live 00:17:44.440 --> 00:17:46.830 align:start position:0% etherium in archive node full node live client<00:17:45.010> or<00:17:45.250> embedded<00:17:45.910> for<00:17:46.120> embedded<00:17:46.480> machines 00:17:46.830 --> 00:17:46.840 align:start position:0% client or embedded for embedded machines 00:17:46.840 --> 00:17:49.919 align:start position:0% client or embedded for embedded machines we<00:17:47.679> have<00:17:47.710> details<00:17:48.250> on<00:17:48.460> how<00:17:48.610> to<00:17:48.640> connect<00:17:49.120> mist 00:17:49.919 --> 00:17:49.929 align:start position:0% we have details on how to connect mist 00:17:49.929 --> 00:17:52.530 align:start position:0% we have details on how to connect mist and<00:17:50.290> serum<00:17:51.190> wallet<00:17:51.520> we<00:17:51.700> have<00:17:51.850> details<00:17:52.210> on<00:17:52.360> how 00:17:52.530 --> 00:17:52.540 align:start position:0% and serum wallet we have details on how 00:17:52.540 --> 00:17:54.990 align:start position:0% and serum wallet we have details on how to<00:17:52.570> connect<00:17:52.960> Android<00:17:53.470> and<00:17:53.800> iOS<00:17:54.010> devices<00:17:54.280> and 00:17:54.990 --> 00:17:55.000 align:start position:0% to connect Android and iOS devices and 00:17:55.000 --> 00:17:57.240 align:start position:0% to connect Android and iOS devices and finally<00:17:55.929> if<00:17:56.110> you<00:17:56.260> really<00:17:56.559> don't<00:17:56.679> prefer 00:17:57.240 --> 00:17:57.250 align:start position:0% finally if you really don't prefer 00:17:57.250 --> 00:17:59.250 align:start position:0% finally if you really don't prefer goethe<00:17:58.000> reom<00:17:58.179> as<00:17:58.360> your<00:17:58.540> client<00:17:58.900> of<00:17:59.020> choice 00:17:59.250 --> 00:17:59.260 align:start position:0% goethe reom as your client of choice 00:17:59.260 --> 00:18:01.049 align:start position:0% goethe reom as your client of choice then<00:17:59.800> we<00:17:59.920> also<00:18:00.070> have<00:18:00.370> details<00:18:00.730> on<00:18:00.850> how<00:18:01.000> to 00:18:01.049 --> 00:18:01.059 align:start position:0% then we also have details on how to 00:18:01.059 --> 00:18:03.150 align:start position:0% then we also have details on how to connect<00:18:01.390> c++<00:18:01.900> etherium<00:18:02.350> a<00:18:02.440> theorem<00:18:02.710> harmony 00:18:03.150 --> 00:18:03.160 align:start position:0% connect c++ etherium a theorem harmony 00:18:03.160 --> 00:18:07.260 align:start position:0% connect c++ etherium a theorem harmony parity<00:18:03.880> and<00:18:04.090> by<00:18:04.450> if<00:18:04.690> app<00:18:04.929> and<00:18:06.090> ladies<00:18:07.090> and 00:18:07.260 --> 00:18:07.270 align:start position:0% parity and by if app and ladies and 00:18:07.270 --> 00:18:14.370 align:start position:0% parity and by if app and ladies and gentlemen<00:18:07.720> that<00:18:08.200> was<00:18:08.470> the<00:18:08.770> puppet<00:18:09.160> Network 00:18:14.370 --> 00:18:14.380 align:start position:0% 00:18:14.380 --> 00:18:30.130 align:start position:0% [Applause] 00:18:30.130 --> 00:18:30.140 align:start position:0% 00:18:30.140 --> 00:18:37.729 align:start position:0% [Music]