WEBVTT Kind: captions Language: en 00:00:14.160 --> 00:00:18.630 align:start position:0% morning<00:00:15.160> everyone<00:00:15.519> I<00:00:16.140> am<00:00:17.140> Everton<00:00:17.920> frog<00:00:18.189> I'm 00:00:18.630 --> 00:00:18.640 align:start position:0% morning everyone I am Everton frog I'm 00:00:18.640 --> 00:00:23.519 align:start position:0% morning everyone I am Everton frog I'm here<00:00:18.999> to<00:00:19.179> talk<00:00:19.419> about<00:00:19.480> mists<00:00:20.289> project<00:00:22.529> Alex 00:00:23.519 --> 00:00:23.529 align:start position:0% here to talk about mists project Alex 00:00:23.529 --> 00:00:27.149 align:start position:0% here to talk about mists project Alex when<00:00:23.739> the<00:00:23.890> sendee<00:00:24.369> couldn't<00:00:25.359> be<00:00:25.480> here<00:00:26.099> he<00:00:27.099> is 00:00:27.149 --> 00:00:27.159 align:start position:0% when the sendee couldn't be here he is 00:00:27.159 --> 00:00:36.560 align:start position:0% when the sendee couldn't be here he is about<00:00:27.519> to<00:00:27.579> have<00:00:27.939> baby<00:00:28.319> so<00:00:29.399> maybe<00:00:30.399> next<00:00:30.609> time 00:00:36.560 --> 00:00:36.570 align:start position:0% 00:00:36.570 --> 00:00:39.330 align:start position:0% well<00:00:37.570> we're<00:00:37.930> here<00:00:38.109> to<00:00:38.170> talk<00:00:38.530> about<00:00:38.590> meals 00:00:39.330 --> 00:00:39.340 align:start position:0% well we're here to talk about meals 00:00:39.340 --> 00:00:45.619 align:start position:0% well we're here to talk about meals project<00:00:40.949> first<00:00:41.949> of<00:00:42.160> all<00:00:42.340> let<00:00:43.000> me<00:00:43.179> go<00:00:43.359> back<00:00:43.600> here 00:00:45.619 --> 00:00:45.629 align:start position:0% project first of all let me go back here 00:00:45.629 --> 00:00:48.900 align:start position:0% project first of all let me go back here okay<00:00:46.660> why<00:00:46.929> missed<00:00:47.260> what's<00:00:48.010> the<00:00:48.219> vision<00:00:48.460> of<00:00:48.730> the 00:00:48.900 --> 00:00:48.910 align:start position:0% okay why missed what's the vision of the 00:00:48.910 --> 00:00:52.950 align:start position:0% okay why missed what's the vision of the project<00:00:49.230> it<00:00:50.230> is<00:00:50.410> to<00:00:50.620> host<00:00:50.920> the<00:00:51.730> web<00:00:51.910> three<00:00:52.269> we 00:00:52.950 --> 00:00:52.960 align:start position:0% project it is to host the web three we 00:00:52.960 --> 00:00:56.130 align:start position:0% project it is to host the web three we have<00:00:53.109> three<00:00:53.170> projects<00:00:54.359> the<00:00:55.359> land<00:00:55.629> of<00:00:55.989> the 00:00:56.130 --> 00:00:56.140 align:start position:0% have three projects the land of the 00:00:56.140 --> 00:01:09.660 align:start position:0% have three projects the land of the decentralized<00:00:56.589> applications<00:01:07.290> and<00:01:08.670> having 00:01:09.660 --> 00:01:09.670 align:start position:0% decentralized applications and having 00:01:09.670 --> 00:01:10.770 align:start position:0% decentralized applications and having the<00:01:10.090> blockchain 00:01:10.770 --> 00:01:10.780 align:start position:0% the blockchain 00:01:10.780 --> 00:01:15.390 align:start position:0% the blockchain as<00:01:10.990> the<00:01:11.530> backend<00:01:13.200> let's<00:01:14.200> browse<00:01:14.530> through<00:01:15.040> the 00:01:15.390 --> 00:01:15.400 align:start position:0% as the backend let's browse through the 00:01:15.400 --> 00:01:22.920 align:start position:0% as the backend let's browse through the past<00:01:15.670> versions<00:01:18.480> okay<00:01:21.120> at<00:01:22.120> the<00:01:22.330> first<00:01:22.600> I've 00:01:22.920 --> 00:01:22.930 align:start position:0% past versions okay at the first I've 00:01:22.930 --> 00:01:28.020 align:start position:0% past versions okay at the first I've come<00:01:24.180> there<00:01:25.180> were<00:01:25.360> no<00:01:25.390> missed<00:01:26.340> so<00:01:27.340> that's<00:01:27.790> why 00:01:28.020 --> 00:01:28.030 align:start position:0% come there were no missed so that's why 00:01:28.030 --> 00:01:31.580 align:start position:0% come there were no missed so that's why people<00:01:28.330> would<00:01:28.720> execute<00:01:29.230> transactions<00:01:30.190> that 00:01:31.580 --> 00:01:31.590 align:start position:0% people would execute transactions that 00:01:31.590 --> 00:01:35.880 align:start position:0% people would execute transactions that execute<00:01:32.590> smile<00:01:32.950> contract<00:01:33.520> methods<00:01:34.500> all<00:01:35.500> in 00:01:35.880 --> 00:01:35.890 align:start position:0% execute smile contract methods all in 00:01:35.890 --> 00:01:38.700 align:start position:0% execute smile contract methods all in command<00:01:36.280> line<00:01:36.340> tools<00:01:36.840> so<00:01:37.840> it<00:01:38.140> was<00:01:38.290> really 00:01:38.700 --> 00:01:38.710 align:start position:0% command line tools so it was really 00:01:38.710 --> 00:01:42.900 align:start position:0% command line tools so it was really developer<00:01:39.490> oriented<00:01:40.270> and<00:01:41.100> well<00:01:42.100> no<00:01:42.460> graphic 00:01:42.900 --> 00:01:42.910 align:start position:0% developer oriented and well no graphic 00:01:42.910 --> 00:01:45.210 align:start position:0% developer oriented and well no graphic interface<00:01:43.480> he<00:01:43.900> had<00:01:44.080> to<00:01:44.200> be<00:01:44.380> a<00:01:44.410> command-line 00:01:45.210 --> 00:01:45.220 align:start position:0% interface he had to be a command-line 00:01:45.220 --> 00:01:51.120 align:start position:0% interface he had to be a command-line guru<00:01:46.380> therefore<00:01:47.380> know<00:01:48.250> that<00:01:49.680> by<00:01:50.680> the<00:01:50.710> time<00:01:50.980> of 00:01:51.120 --> 00:01:51.130 align:start position:0% guru therefore know that by the time of 00:01:51.130 --> 00:01:57.950 align:start position:0% guru therefore know that by the time of the<00:01:51.250> of<00:01:51.400> defqon.1<00:01:53.400> we<00:01:54.400> had<00:01:54.640> a<00:01:54.970> few<00:01:55.210> Mollett 00:01:57.950 --> 00:01:57.960 align:start position:0% 00:01:57.960 --> 00:02:01.680 align:start position:0% which<00:01:58.960> was<00:01:59.320> the<00:02:00.040> foundation<00:02:00.460> of<00:02:00.850> the<00:02:01.480> dab 00:02:01.680 --> 00:02:01.690 align:start position:0% which was the foundation of the dab 00:02:01.690 --> 00:02:05.649 align:start position:0% which was the foundation of the dab space<00:02:02.080> it<00:02:02.560> was<00:02:02.710> the<00:02:02.890> first<00:02:03.160> one<00:02:03.480> we<00:02:04.480> built 00:02:05.649 --> 00:02:05.659 align:start position:0% space it was the first one we built 00:02:05.659 --> 00:02:08.260 align:start position:0% space it was the first one we built it<00:02:06.110> was<00:02:06.260> more<00:02:06.530> like<00:02:06.560> an<00:02:07.130> advanced<00:02:07.610> tools<00:02:07.940> for 00:02:08.260 --> 00:02:08.270 align:start position:0% it was more like an advanced tools for 00:02:08.270 --> 00:02:11.590 align:start position:0% it was more like an advanced tools for specialists<00:02:09.140> you<00:02:09.890> had<00:02:10.039> to<00:02:10.280> click<00:02:10.970> around<00:02:11.150> and 00:02:11.590 --> 00:02:11.600 align:start position:0% specialists you had to click around and 00:02:11.600 --> 00:02:16.630 align:start position:0% specialists you had to click around and get<00:02:12.320> to<00:02:12.470> know<00:02:12.500> all<00:02:12.950> the<00:02:13.250> the<00:02:15.400> all<00:02:16.400> the 00:02:16.630 --> 00:02:16.640 align:start position:0% get to know all the the all the 00:02:16.640 --> 00:02:21.250 align:start position:0% get to know all the the all the application<00:02:17.390> and<00:02:18.370> it<00:02:19.370> pose<00:02:19.670> it<00:02:19.910> as<00:02:20.030> a<00:02:20.260> dynamic 00:02:21.250 --> 00:02:21.260 align:start position:0% application and it pose it as a dynamic 00:02:21.260 --> 00:02:25.350 align:start position:0% application and it pose it as a dynamic interface<00:02:21.950> for<00:02:22.550> contracts<00:02:24.070> through<00:02:25.070> a 00:02:25.350 --> 00:02:25.360 align:start position:0% interface for contracts through a 00:02:25.360 --> 00:02:28.930 align:start position:0% interface for contracts through a auto-generated<00:02:26.500> based<00:02:27.500> on<00:02:27.800> the<00:02:28.010> ABI<00:02:28.430> of<00:02:28.730> the 00:02:28.930 --> 00:02:28.940 align:start position:0% auto-generated based on the ABI of the 00:02:28.940 --> 00:02:29.680 align:start position:0% auto-generated based on the ABI of the contracts 00:02:29.680 --> 00:02:29.690 align:start position:0% contracts 00:02:29.690 --> 00:02:33.460 align:start position:0% contracts you<00:02:30.260> could<00:02:30.440> have<00:02:31.660> executing<00:02:32.660> contracts<00:02:33.260> with 00:02:33.460 --> 00:02:33.470 align:start position:0% you could have executing contracts with 00:02:33.470 --> 00:02:36.070 align:start position:0% you could have executing contracts with all<00:02:33.800> the<00:02:34.010> parameters<00:02:34.580> and<00:02:35.000> it's<00:02:35.840> like<00:02:36.050> a 00:02:36.070 --> 00:02:36.080 align:start position:0% all the parameters and it's like a 00:02:36.080 --> 00:02:39.310 align:start position:0% all the parameters and it's like a boolean<00:02:36.680> and<00:02:37.209> you<00:02:38.209> ain't<00:02:38.450> and<00:02:38.840> then<00:02:38.989> you<00:02:39.140> would 00:02:39.310 --> 00:02:39.320 align:start position:0% boolean and you ain't and then you would 00:02:39.320 --> 00:02:44.229 align:start position:0% boolean and you ain't and then you would execute<00:02:39.709> methods<00:02:41.230> well<00:02:42.230> it<00:02:42.440> was<00:02:42.790> it<00:02:43.790> did<00:02:44.000> its 00:02:44.229 --> 00:02:44.239 align:start position:0% execute methods well it was it did its 00:02:44.239 --> 00:02:48.699 align:start position:0% execute methods well it was it did its job<00:02:45.310> but<00:02:46.310> for<00:02:46.730> the<00:02:46.850> general<00:02:47.209> use<00:02:47.560> there<00:02:48.560> were 00:02:48.699 --> 00:02:48.709 align:start position:0% job but for the general use there were 00:02:48.709 --> 00:02:52.380 align:start position:0% job but for the general use there were some<00:02:48.980> features<00:02:49.640> missing<00:02:50.209> of<00:02:50.360> course<00:02:50.830> such<00:02:51.830> as 00:02:52.380 --> 00:02:52.390 align:start position:0% some features missing of course such as 00:02:52.390 --> 00:02:55.270 align:start position:0% some features missing of course such as that<00:02:53.390> would<00:02:53.540> require<00:02:53.989> you<00:02:54.470> to<00:02:54.530> have<00:02:54.739> either 00:02:55.270 --> 00:02:55.280 align:start position:0% that would require you to have either 00:02:55.280 --> 00:03:00.220 align:start position:0% that would require you to have either for<00:02:56.150> instance<00:02:58.330> then<00:02:59.330> by<00:02:59.540> the<00:02:59.600> time<00:02:59.900> of<00:02:59.959> the 00:03:00.220 --> 00:03:00.230 align:start position:0% for instance then by the time of the 00:03:00.230 --> 00:03:04.150 align:start position:0% for instance then by the time of the DEFCON<00:03:00.709> two<00:03:01.570> we<00:03:02.570> had<00:03:02.870> released<00:03:03.590> the<00:03:03.890> mists 00:03:04.150 --> 00:03:04.160 align:start position:0% DEFCON two we had released the mists 00:03:04.160 --> 00:03:09.940 align:start position:0% DEFCON two we had released the mists better<00:03:05.260> which<00:03:06.400> was<00:03:07.400> more<00:03:07.640> like<00:03:07.700> a<00:03:08.620> Firefox<00:03:09.620> or 00:03:09.940 --> 00:03:09.950 align:start position:0% better which was more like a Firefox or 00:03:09.950 --> 00:03:12.130 align:start position:0% better which was more like a Firefox or Netscape<00:03:10.459> Navigator<00:03:10.489> as<00:03:11.390> the<00:03:11.720> beginning<00:03:12.110> of 00:03:12.130 --> 00:03:12.140 align:start position:0% Netscape Navigator as the beginning of 00:03:12.140 --> 00:03:15.580 align:start position:0% Netscape Navigator as the beginning of the<00:03:12.230> Internet<00:03:13.269> so<00:03:14.269> focus<00:03:14.989> on<00:03:15.170> on<00:03:15.530> the 00:03:15.580 --> 00:03:15.590 align:start position:0% the Internet so focus on on the 00:03:15.590 --> 00:03:19.780 align:start position:0% the Internet so focus on on the enthusiast<00:03:16.549> user<00:03:17.410> it<00:03:18.410> presented<00:03:19.100> the<00:03:19.519> full 00:03:19.780 --> 00:03:19.790 align:start position:0% enthusiast user it presented the full 00:03:19.790 --> 00:03:22.900 align:start position:0% enthusiast user it presented the full power<00:03:20.120> of<00:03:20.269> the<00:03:20.630> web<00:03:21.130> for<00:03:22.130> sbond<00:03:22.459> smart 00:03:22.900 --> 00:03:22.910 align:start position:0% power of the web for sbond smart 00:03:22.910 --> 00:03:27.190 align:start position:0% power of the web for sbond smart contracts<00:03:24.730> so<00:03:25.730> you<00:03:25.790> would<00:03:26.090> from<00:03:27.019> your 00:03:27.190 --> 00:03:27.200 align:start position:0% contracts so you would from your 00:03:27.200 --> 00:03:29.819 align:start position:0% contracts so you would from your JavaScript<00:03:27.769> application<00:03:28.579> from<00:03:29.269> your<00:03:29.450> website 00:03:29.819 --> 00:03:29.829 align:start position:0% JavaScript application from your website 00:03:29.829 --> 00:03:33.340 align:start position:0% JavaScript application from your website you<00:03:30.829> would<00:03:30.980> trigger<00:03:31.250> transactions<00:03:32.180> and<00:03:32.600> then 00:03:33.340 --> 00:03:33.350 align:start position:0% you would trigger transactions and then 00:03:33.350 --> 00:03:36.850 align:start position:0% you would trigger transactions and then mist<00:03:33.650> would<00:03:33.980> handle<00:03:34.400> it<00:03:35.290> here<00:03:36.290> you<00:03:36.410> can<00:03:36.440> see<00:03:36.829> a 00:03:36.850 --> 00:03:36.860 align:start position:0% mist would handle it here you can see a 00:03:36.860 --> 00:03:40.030 align:start position:0% mist would handle it here you can see a confirmation<00:03:37.280> window<00:03:37.850> about<00:03:38.510> the<00:03:39.410> execution 00:03:40.030 --> 00:03:40.040 align:start position:0% confirmation window about the execution 00:03:40.040 --> 00:03:43.300 align:start position:0% confirmation window about the execution of<00:03:40.160> a<00:03:40.310> method<00:03:40.670> in<00:03:40.790> a<00:03:40.880> contract<00:03:41.590> we<00:03:42.590> we<00:03:43.100> have 00:03:43.300 --> 00:03:43.310 align:start position:0% of a method in a contract we we have 00:03:43.310 --> 00:03:45.759 align:start position:0% of a method in a contract we we have these<00:03:43.579> the<00:03:44.480> parameters<00:03:45.049> that<00:03:45.410> could<00:03:45.620> be 00:03:45.759 --> 00:03:45.769 align:start position:0% these the parameters that could be 00:03:45.769 --> 00:03:50.319 align:start position:0% these the parameters that could be parsed<00:03:46.209> via<00:03:47.209> an<00:03:47.780> ABI<00:03:48.380> directory<00:03:49.150> built<00:03:50.150> by 00:03:50.319 --> 00:03:50.329 align:start position:0% parsed via an ABI directory built by 00:03:50.329 --> 00:03:54.729 align:start position:0% parsed via an ABI directory built by Piper<00:03:51.579> so<00:03:52.579> yes<00:03:53.239> that<00:03:53.600> led<00:03:53.870> you<00:03:54.140> to<00:03:54.200> many<00:03:54.590> other 00:03:54.729 --> 00:03:54.739 align:start position:0% Piper so yes that led you to many other 00:03:54.739 --> 00:03:58.289 align:start position:0% Piper so yes that led you to many other things<00:03:55.040> so<00:03:55.280> you<00:03:55.850> could<00:03:56.090> create<00:03:56.329> your<00:03:56.480> own 00:03:58.289 --> 00:03:58.299 align:start position:0% things so you could create your own 00:03:58.299 --> 00:04:02.949 align:start position:0% things so you could create your own Congress<00:03:59.299> Dow<00:03:59.840> ad<00:04:00.430> contract<00:04:01.430> and<00:04:01.700> then<00:04:02.329> build 00:04:02.949 --> 00:04:02.959 align:start position:0% Congress Dow ad contract and then build 00:04:02.959 --> 00:04:07.210 align:start position:0% Congress Dow ad contract and then build an<00:04:03.110> interface<00:04:03.380> out<00:04:03.890> of<00:04:04.010> it<00:04:05.500> but<00:04:06.500> you<00:04:06.709> know<00:04:06.860> as 00:04:07.210 --> 00:04:07.220 align:start position:0% an interface out of it but you know as 00:04:07.220 --> 00:04:10.920 align:start position:0% an interface out of it but you know as the<00:04:08.019> block<00:04:09.019> chains<00:04:09.290> started<00:04:10.070> to<00:04:10.160> grow<00:04:10.370> in<00:04:10.579> size 00:04:10.920 --> 00:04:10.930 align:start position:0% the block chains started to grow in size 00:04:10.930 --> 00:04:13.599 align:start position:0% the block chains started to grow in size it<00:04:11.930> was<00:04:12.110> becoming<00:04:12.470> less<00:04:12.980> and<00:04:13.040> less<00:04:13.280> practical 00:04:13.599 --> 00:04:13.609 align:start position:0% it was becoming less and less practical 00:04:13.609 --> 00:04:17.680 align:start position:0% it was becoming less and less practical for<00:04:14.239> the<00:04:14.359> users<00:04:14.720> to<00:04:15.049> have<00:04:16.040> the<00:04:16.310> whole<00:04:16.609> sink<00:04:17.000> the 00:04:17.680 --> 00:04:17.690 align:start position:0% for the users to have the whole sink the 00:04:17.690 --> 00:04:19.350 align:start position:0% for the users to have the whole sink the whole<00:04:17.840> blockchain<00:04:18.560> sink 00:04:19.350 --> 00:04:19.360 align:start position:0% whole blockchain sink 00:04:19.360 --> 00:04:23.080 align:start position:0% whole blockchain sink so<00:04:20.360> yeah<00:04:20.990> this<00:04:21.320> is<00:04:21.380> one<00:04:21.740> thing<00:04:22.580> that<00:04:22.760> we<00:04:22.910> would 00:04:23.080 --> 00:04:23.090 align:start position:0% so yeah this is one thing that we would 00:04:23.090 --> 00:04:29.340 align:start position:0% so yeah this is one thing that we would talk<00:04:23.360> later<00:04:26.020> throughout<00:04:27.020> this<00:04:27.200> time<00:04:27.530> we<00:04:27.980> had 00:04:29.340 --> 00:04:29.350 align:start position:0% talk later throughout this time we had 00:04:29.350 --> 00:04:33.490 align:start position:0% talk later throughout this time we had the<00:04:30.350> the<00:04:31.000> ecosystem<00:04:32.000> has<00:04:32.300> grown<00:04:32.660> like<00:04:32.990> you 00:04:33.490 --> 00:04:33.500 align:start position:0% the the ecosystem has grown like you 00:04:33.500 --> 00:04:36.520 align:start position:0% the the ecosystem has grown like you know<00:04:33.620> like<00:04:33.950> crazy<00:04:35.020> throughout<00:04:36.020> these<00:04:36.170> three 00:04:36.520 --> 00:04:36.530 align:start position:0% know like crazy throughout these three 00:04:36.530 --> 00:04:42.040 align:start position:0% know like crazy throughout these three years<00:04:36.770> we<00:04:37.730> have<00:04:38.590> we<00:04:39.590> have<00:04:39.800> been<00:04:41.050> downloaded 00:04:42.040 --> 00:04:42.050 align:start position:0% years we have we have been downloaded 00:04:42.050 --> 00:04:43.780 align:start position:0% years we have we have been downloaded many<00:04:42.590> many<00:04:42.890> times<00:04:43.160> as<00:04:43.400> well 00:04:43.780 --> 00:04:43.790 align:start position:0% many many times as well 00:04:43.790 --> 00:04:47.110 align:start position:0% many many times as well so<00:04:44.450> here<00:04:45.230> proud<00:04:45.470> to<00:04:45.650> share<00:04:45.890> with<00:04:46.010> you<00:04:46.220> that<00:04:46.490> if 00:04:47.110 --> 00:04:47.120 align:start position:0% so here proud to share with you that if 00:04:47.120 --> 00:04:49.480 align:start position:0% so here proud to share with you that if you<00:04:47.390> mullet<00:04:47.810> and<00:04:47.960> mist<00:04:48.320> combined<00:04:48.860> has<00:04:49.190> been 00:04:49.480 --> 00:04:49.490 align:start position:0% you mullet and mist combined has been 00:04:49.490 --> 00:04:53.430 align:start position:0% you mullet and mist combined has been downloaded<00:04:49.700> more<00:04:49.970> than<00:04:50.980> 2.6<00:04:51.980> million<00:04:52.430> dollars 00:04:53.430 --> 00:04:53.440 align:start position:0% downloaded more than 2.6 million dollars 00:04:53.440 --> 00:05:04.990 align:start position:0% downloaded more than 2.6 million dollars so<00:04:54.440> that's<00:05:00.880> so<00:05:01.880> that<00:05:02.300> shows<00:05:02.660> a<00:05:03.020> bit<00:05:03.260> of<00:05:04.000> the 00:05:04.990 --> 00:05:05.000 align:start position:0% so that's so that shows a bit of the 00:05:05.000 --> 00:05:06.760 align:start position:0% so that's so that shows a bit of the site<00:05:05.300> of<00:05:05.330> the<00:05:05.630> trip<00:05:05.840> we<00:05:06.050> have<00:05:06.260> actually 00:05:06.760 --> 00:05:06.770 align:start position:0% site of the trip we have actually 00:05:06.770 --> 00:05:10.810 align:start position:0% site of the trip we have actually because<00:05:07.730> we<00:05:07.940> are<00:05:08.000> the<00:05:08.180> most<00:05:08.800> user<00:05:09.820> forefront 00:05:10.810 --> 00:05:10.820 align:start position:0% because we are the most user forefront 00:05:10.820 --> 00:05:14.590 align:start position:0% because we are the most user forefront of<00:05:11.000> Afyon<00:05:11.390> projects<00:05:12.020> and<00:05:13.060> then<00:05:14.060> we<00:05:14.210> have<00:05:14.360> to<00:05:14.480> do 00:05:14.590 --> 00:05:14.600 align:start position:0% of Afyon projects and then we have to do 00:05:14.600 --> 00:05:16.750 align:start position:0% of Afyon projects and then we have to do with<00:05:14.780> all<00:05:14.930> those<00:05:15.140> sort<00:05:15.500> of<00:05:15.620> problems<00:05:16.250> that 00:05:16.750 --> 00:05:16.760 align:start position:0% with all those sort of problems that 00:05:16.760 --> 00:05:20.470 align:start position:0% with all those sort of problems that came<00:05:16.940> as<00:05:17.270> well<00:05:18.430> well<00:05:19.430> in<00:05:19.640> order<00:05:19.880> to<00:05:20.060> solve<00:05:20.360> that 00:05:20.470 --> 00:05:20.480 align:start position:0% came as well well in order to solve that 00:05:20.480 --> 00:05:24.010 align:start position:0% came as well well in order to solve that and<00:05:20.870> organize<00:05:21.380> all<00:05:21.770> the<00:05:22.040> the<00:05:22.340> project<00:05:22.940> we<00:05:23.780> did 00:05:24.010 --> 00:05:24.020 align:start position:0% and organize all the the project we did 00:05:24.020 --> 00:05:29.410 align:start position:0% and organize all the the project we did a<00:05:24.050> mist<00:05:24.620> Summit<00:05:25.130> in<00:05:25.880> Rio<00:05:26.470> where<00:05:27.470> we<00:05:27.740> get<00:05:28.420> to 00:05:29.410 --> 00:05:29.420 align:start position:0% a mist Summit in Rio where we get to 00:05:29.420 --> 00:05:35.080 align:start position:0% a mist Summit in Rio where we get to have<00:05:29.660> the<00:05:29.690> whole<00:05:30.140> team<00:05:33.370> and<00:05:34.370> we<00:05:34.640> talked<00:05:34.910> about 00:05:35.080 --> 00:05:35.090 align:start position:0% have the whole team and we talked about 00:05:35.090 --> 00:05:38.590 align:start position:0% have the whole team and we talked about lots<00:05:35.600> and<00:05:35.840> lots<00:05:35.990> of<00:05:36.080> things<00:05:36.880> so<00:05:37.880> it<00:05:38.000> was<00:05:38.180> sort 00:05:38.590 --> 00:05:38.600 align:start position:0% lots and lots of things so it was sort 00:05:38.600 --> 00:05:41.950 align:start position:0% lots and lots of things so it was sort of<00:05:38.690> a<00:05:38.930> whole<00:05:39.140> week<00:05:39.400> thinking<00:05:40.400> and<00:05:40.610> working<00:05:41.180> so 00:05:41.950 --> 00:05:41.960 align:start position:0% of a whole week thinking and working so 00:05:41.960 --> 00:05:47.430 align:start position:0% of a whole week thinking and working so here's<00:05:42.200> some<00:05:42.410> proof<00:05:42.890> of<00:05:43.190> workshops<00:05:43.760> for<00:05:44.030> you 00:05:47.430 --> 00:05:47.440 align:start position:0% 00:05:47.440 --> 00:05:50.020 align:start position:0% notice<00:05:48.440> that<00:05:48.620> all<00:05:48.950> those<00:05:49.190> different<00:05:49.250> clothing 00:05:50.020 --> 00:05:50.030 align:start position:0% notice that all those different clothing 00:05:50.030 --> 00:05:55.720 align:start position:0% notice that all those different clothing so<00:05:50.240> it<00:05:50.360> was<00:05:50.540> really<00:05:50.840> a<00:05:50.930> whole<00:05:51.380> week<00:05:54.580> yeah<00:05:55.580> and 00:05:55.720 --> 00:05:55.730 align:start position:0% so it was really a whole week yeah and 00:05:55.730 --> 00:06:00.820 align:start position:0% so it was really a whole week yeah and that<00:05:55.880> was<00:05:56.450> our<00:05:56.780> team<00:05:57.500> at<00:05:57.680> that<00:05:57.740> time<00:05:59.590> so<00:06:00.590> yeah 00:06:00.820 --> 00:06:00.830 align:start position:0% that was our team at that time so yeah 00:06:00.830 --> 00:06:03.730 align:start position:0% that was our team at that time so yeah we<00:06:01.010> came<00:06:01.190> up<00:06:01.370> with<00:06:01.490> really<00:06:02.260> lots<00:06:03.260> and<00:06:03.440> lots<00:06:03.590> of 00:06:03.730 --> 00:06:03.740 align:start position:0% we came up with really lots and lots of 00:06:03.740 --> 00:06:09.310 align:start position:0% we came up with really lots and lots of experiments<00:06:04.690> you<00:06:06.760> know<00:06:07.760> there's<00:06:08.090> only<00:06:08.720> some 00:06:09.310 --> 00:06:09.320 align:start position:0% experiments you know there's only some 00:06:09.320 --> 00:06:14.530 align:start position:0% experiments you know there's only some interface<00:06:09.860> wise<00:06:10.540> experiments<00:06:13.000> so<00:06:14.000> let's<00:06:14.390> get 00:06:14.530 --> 00:06:14.540 align:start position:0% interface wise experiments so let's get 00:06:14.540 --> 00:06:17.430 align:start position:0% interface wise experiments so let's get to<00:06:14.720> the<00:06:14.750> deliberate<00:06:15.290> features<00:06:15.680> this<00:06:15.920> year 00:06:17.430 --> 00:06:17.440 align:start position:0% to the deliberate features this year 00:06:17.440 --> 00:06:20.950 align:start position:0% to the deliberate features this year first<00:06:18.440> and<00:06:18.680> foremost<00:06:19.220> our<00:06:19.460> main<00:06:20.120> main<00:06:20.450> concern 00:06:20.950 --> 00:06:20.960 align:start position:0% first and foremost our main main concern 00:06:20.960 --> 00:06:24.910 align:start position:0% first and foremost our main main concern is<00:06:21.250> security<00:06:22.540> because<00:06:23.540> well<00:06:24.380> we<00:06:24.650> have<00:06:24.890> a 00:06:24.910 --> 00:06:24.920 align:start position:0% is security because well we have a 00:06:24.920 --> 00:06:29.650 align:start position:0% is security because well we have a browser<00:06:25.250> that<00:06:26.150> handles<00:06:26.919> private<00:06:27.919> keys<00:06:28.120> so<00:06:29.120> it 00:06:29.650 --> 00:06:29.660 align:start position:0% browser that handles private keys so it 00:06:29.660 --> 00:06:31.690 align:start position:0% browser that handles private keys so it gets<00:06:29.900> you<00:06:30.680> know 00:06:31.690 --> 00:06:31.700 align:start position:0% gets you know 00:06:31.700 --> 00:06:34.540 align:start position:0% gets you know it's<00:06:31.850> not<00:06:32.060> so<00:06:32.300> simple<00:06:32.660> as<00:06:33.050> would<00:06:33.530> be<00:06:33.710> a<00:06:34.010> simple 00:06:34.540 --> 00:06:34.550 align:start position:0% it's not so simple as would be a simple 00:06:34.550 --> 00:06:36.460 align:start position:0% it's not so simple as would be a simple website<00:06:34.730> that<00:06:35.240> doesn't<00:06:35.600> handle<00:06:35.900> anything 00:06:36.460 --> 00:06:36.470 align:start position:0% website that doesn't handle anything 00:06:36.470 --> 00:06:39.570 align:start position:0% website that doesn't handle anything related<00:06:37.340> to<00:06:37.370> money<00:06:38.200> Francis 00:06:39.570 --> 00:06:39.580 align:start position:0% related to money Francis 00:06:39.580 --> 00:06:42.220 align:start position:0% related to money Francis well<00:06:40.580> let's<00:06:40.880> put<00:06:41.090> a<00:06:41.120> ribbon<00:06:41.420> this<00:06:41.810> because 00:06:42.220 --> 00:06:42.230 align:start position:0% well let's put a ribbon this because 00:06:42.230 --> 00:06:46.990 align:start position:0% well let's put a ribbon this because it's<00:06:42.680> so<00:06:42.860> important<00:06:44.950> so<00:06:45.950> we've<00:06:46.640> made<00:06:46.790> an 00:06:46.990 --> 00:06:47.000 align:start position:0% it's so important so we've made an 00:06:47.000 --> 00:06:50.410 align:start position:0% it's so important so we've made an extensive<00:06:47.390> audit<00:06:48.170> by<00:06:48.410> crew<00:06:48.770> 53<00:06:49.490> which<00:06:50.180> is<00:06:50.390> a 00:06:50.410 --> 00:06:50.420 align:start position:0% extensive audit by crew 53 which is a 00:06:50.420 --> 00:06:55.480 align:start position:0% extensive audit by crew 53 which is a really<00:06:51.050> really<00:06:51.320> cool<00:06:53.260> German<00:06:54.260> company<00:06:54.740> those 00:06:55.480 --> 00:06:55.490 align:start position:0% really really cool German company those 00:06:55.490 --> 00:06:58.150 align:start position:0% really really cool German company those guys<00:06:55.730> are<00:06:55.910> really<00:06:56.120> skilled<00:06:56.600> and<00:06:57.020> they<00:06:57.860> managed 00:06:58.150 --> 00:06:58.160 align:start position:0% guys are really skilled and they managed 00:06:58.160 --> 00:07:01.990 align:start position:0% guys are really skilled and they managed to<00:06:58.220> found<00:06:58.580> to<00:06:59.030> find<00:06:59.300> 22<00:07:00.050> issues<00:07:00.790> work<00:07:01.790> with 00:07:01.990 --> 00:07:02.000 align:start position:0% to found to find 22 issues work with 00:07:02.000 --> 00:07:05.140 align:start position:0% to found to find 22 issues work with Brian<00:07:02.480> severity<00:07:03.020> levels<00:07:03.440> so<00:07:03.770> it<00:07:04.460> has<00:07:04.670> some 00:07:05.140 --> 00:07:05.150 align:start position:0% Brian severity levels so it has some 00:07:05.150 --> 00:07:09.190 align:start position:0% Brian severity levels so it has some critical<00:07:05.630> ones<00:07:05.840> high<00:07:06.560> medium<00:07:07.100> and<00:07:07.250> low<00:07:08.020> all<00:07:09.020> of 00:07:09.190 --> 00:07:09.200 align:start position:0% critical ones high medium and low all of 00:07:09.200 --> 00:07:12.660 align:start position:0% critical ones high medium and low all of those<00:07:09.320> were<00:07:09.620> fixed<00:07:10.100> by<00:07:10.160> us<00:07:10.990> as<00:07:11.990> soon<00:07:12.290> as<00:07:12.410> they 00:07:12.660 --> 00:07:12.670 align:start position:0% those were fixed by us as soon as they 00:07:12.670 --> 00:07:18.040 align:start position:0% those were fixed by us as soon as they reach<00:07:13.670> this<00:07:13.940> we<00:07:14.240> were<00:07:14.690> ready<00:07:15.050> to<00:07:15.140> fix<00:07:15.500> and<00:07:17.050> we 00:07:18.040 --> 00:07:18.050 align:start position:0% reach this we were ready to fix and we 00:07:18.050 --> 00:07:21.040 align:start position:0% reach this we were ready to fix and we increased<00:07:18.350> our<00:07:18.560> time<00:07:18.860> sweet<00:07:19.220> so<00:07:20.050> no 00:07:21.040 --> 00:07:21.050 align:start position:0% increased our time sweet so no 00:07:21.050 --> 00:07:25.720 align:start position:0% increased our time sweet so no regressions<00:07:21.650> here<00:07:22.600> and<00:07:24.130> also<00:07:25.130> we<00:07:25.220> had<00:07:25.400> some 00:07:25.720 --> 00:07:25.730 align:start position:0% regressions here and also we had some 00:07:25.730 --> 00:07:28.720 align:start position:0% regressions here and also we had some really<00:07:26.270> important<00:07:26.810> if<00:07:26.990> you<00:07:27.230> bow<00:07:28.190> to<00:07:28.220> program 00:07:28.720 --> 00:07:28.730 align:start position:0% really important if you bow to program 00:07:28.730 --> 00:07:31.510 align:start position:0% really important if you bow to program submissions<00:07:29.450> and<00:07:29.860> here<00:07:30.860> I<00:07:30.890> like<00:07:31.070> to<00:07:31.100> thank 00:07:31.510 --> 00:07:31.520 align:start position:0% submissions and here I like to thank 00:07:31.520 --> 00:07:35.970 align:start position:0% submissions and here I like to thank general<00:07:32.420> and<00:07:32.750> new<00:07:33.140> Hawk<00:07:33.380> in<00:07:33.970> really<00:07:34.970> you<00:07:35.540> know 00:07:35.970 --> 00:07:35.980 align:start position:0% general and new Hawk in really you know 00:07:35.980 --> 00:07:44.950 align:start position:0% general and new Hawk in really you know thank<00:07:36.980> you<00:07:40.810> and<00:07:42.370> we<00:07:43.370> have<00:07:43.610> also<00:07:44.390> some<00:07:44.750> other 00:07:44.950 --> 00:07:44.960 align:start position:0% thank you and we have also some other 00:07:44.960 --> 00:07:46.960 align:start position:0% thank you and we have also some other exciting<00:07:45.350> features<00:07:45.830> such<00:07:46.040> as<00:07:46.070> the<00:07:46.520> swarm 00:07:46.960 --> 00:07:46.970 align:start position:0% exciting features such as the swarm 00:07:46.970 --> 00:07:52.270 align:start position:0% exciting features such as the swarm integration<00:07:47.780> in<00:07:48.740> better<00:07:49.010> version<00:07:49.510> so<00:07:50.510> a<00:07:51.280> user 00:07:52.270 --> 00:07:52.280 align:start position:0% integration in better version so a user 00:07:52.280 --> 00:07:56.340 align:start position:0% integration in better version so a user now<00:07:52.670> is<00:07:52.850> is<00:07:53.180> allowed<00:07:53.570> to<00:07:54.760> click<00:07:55.760> on<00:07:55.910> file 00:07:56.340 --> 00:07:56.350 align:start position:0% now is is allowed to click on file 00:07:56.350 --> 00:08:00.030 align:start position:0% now is is allowed to click on file upload<00:07:57.350> to<00:07:57.560> swarm<00:07:57.970> then<00:07:58.970> choose<00:07:59.510> a<00:07:59.540> file 00:08:00.030 --> 00:08:00.040 align:start position:0% upload to swarm then choose a file 00:08:00.040 --> 00:08:03.490 align:start position:0% upload to swarm then choose a file upload<00:08:01.040> it<00:08:01.580> to<00:08:01.700> this<00:08:01.820> swarm<00:08:02.570> instance<00:08:03.230> that's 00:08:03.490 --> 00:08:03.500 align:start position:0% upload it to this swarm instance that's 00:08:03.500 --> 00:08:07.000 align:start position:0% upload it to this swarm instance that's running<00:08:03.800> local<00:08:04.370> in<00:08:04.490> his<00:08:04.700> machine<00:08:05.980> then<00:08:06.980> the 00:08:07.000 --> 00:08:07.010 align:start position:0% running local in his machine then the 00:08:07.010 --> 00:08:10.840 align:start position:0% running local in his machine then the fire<00:08:07.370> is<00:08:07.550> in<00:08:07.760> this<00:08:07.970> warrant<00:08:08.330> space<00:08:09.580> this<00:08:10.580> form 00:08:10.840 --> 00:08:10.850 align:start position:0% fire is in this warrant space this form 00:08:10.850 --> 00:08:13.860 align:start position:0% fire is in this warrant space this form view<00:08:11.030> compute<00:08:11.600> the<00:08:11.780> hash<00:08:11.960> out<00:08:12.410> of<00:08:12.860> it<00:08:13.010> and 00:08:13.860 --> 00:08:13.870 align:start position:0% view compute the hash out of it and 00:08:13.870 --> 00:08:16.920 align:start position:0% view compute the hash out of it and communicate<00:08:14.870> with<00:08:15.380> other<00:08:15.560> storm<00:08:15.920> instances 00:08:16.920 --> 00:08:16.930 align:start position:0% communicate with other storm instances 00:08:16.930 --> 00:08:21.700 align:start position:0% communicate with other storm instances copying<00:08:17.930> the<00:08:18.050> files<00:08:18.350> over<00:08:18.740> them<00:08:20.170> well<00:08:21.170> that's 00:08:21.700 --> 00:08:21.710 align:start position:0% copying the files over them well that's 00:08:21.710 --> 00:08:25.060 align:start position:0% copying the files over them well that's actually<00:08:22.520> the<00:08:22.880> seed<00:08:23.270> of<00:08:23.300> the<00:08:23.600> web<00:08:23.720> 3<00:08:23.960> right<00:08:24.230> you 00:08:25.060 --> 00:08:25.070 align:start position:0% actually the seed of the web 3 right you 00:08:25.070 --> 00:08:28.300 align:start position:0% actually the seed of the web 3 right you could<00:08:25.250> upload<00:08:25.550> a<00:08:25.730> website<00:08:26.470> then<00:08:27.470> access<00:08:28.040> like 00:08:28.300 --> 00:08:28.310 align:start position:0% could upload a website then access like 00:08:28.310 --> 00:08:31.180 align:start position:0% could upload a website then access like this<00:08:29.080> pasting<00:08:30.080> the<00:08:30.170> same<00:08:30.380> hash<00:08:30.710> in<00:08:31.010> your 00:08:31.180 --> 00:08:31.190 align:start position:0% this pasting the same hash in your 00:08:31.190 --> 00:08:36.700 align:start position:0% this pasting the same hash in your browser<00:08:32.590> but<00:08:33.590> well<00:08:34.040> here's<00:08:34.550> one<00:08:34.790> thing<00:08:35.710> swarm 00:08:36.700 --> 00:08:36.710 align:start position:0% browser but well here's one thing swarm 00:08:36.710 --> 00:08:39.010 align:start position:0% browser but well here's one thing swarm comes<00:08:36.890> with<00:08:37.220> DNS<00:08:37.729> integrations<00:08:38.420> so<00:08:38.510> you<00:08:38.720> can 00:08:39.010 --> 00:08:39.020 align:start position:0% comes with DNS integrations so you can 00:08:39.020 --> 00:08:43.290 align:start position:0% comes with DNS integrations so you can have<00:08:39.200> this<00:08:41.260> that's 00:08:43.290 --> 00:08:43.300 align:start position:0% have this that's 00:08:43.300 --> 00:08:47.370 align:start position:0% have this that's one<00:08:44.020> of<00:08:44.110> my<00:08:44.260> favorite<00:08:44.649> features<00:08:45.630> and<00:08:46.630> speaking 00:08:47.370 --> 00:08:47.380 align:start position:0% one of my favorite features and speaking 00:08:47.380 --> 00:08:50.699 align:start position:0% one of my favorite features and speaking of<00:08:47.500> ENS<00:08:48.070> integration<00:08:48.820> we<00:08:49.480> also<00:08:49.720> did<00:08:50.080> some<00:08:50.110> of 00:08:50.699 --> 00:08:50.709 align:start position:0% of ENS integration we also did some of 00:08:50.709 --> 00:08:56.150 align:start position:0% of ENS integration we also did some of them<00:08:50.980> in<00:08:51.310> the<00:08:51.430> wallet<00:08:51.760> so<00:08:53.640> well<00:08:54.640> of<00:08:54.820> course 00:08:56.150 --> 00:08:56.160 align:start position:0% them in the wallet so well of course 00:08:56.160 --> 00:09:00.750 align:start position:0% them in the wallet so well of course you're<00:08:57.160> able<00:08:57.610> to<00:08:58.080> transfer<00:08:59.080> ether<00:08:59.730> to<00:09:00.730> a 00:09:00.750 --> 00:09:00.760 align:start position:0% you're able to transfer ether to a 00:09:00.760 --> 00:09:03.960 align:start position:0% you're able to transfer ether to a certain<00:09:01.300> address<00:09:01.649> in<00:09:02.649> foundation<00:09:03.550> dot<00:09:03.700> eath 00:09:03.960 --> 00:09:03.970 align:start position:0% certain address in foundation dot eath 00:09:03.970 --> 00:09:12.570 align:start position:0% certain address in foundation dot eath for<00:09:04.390> instance<00:09:05.010> or<00:09:06.010> add<00:09:06.790> a<00:09:07.180> custom<00:09:07.660> toking<00:09:11.580> just 00:09:12.570 --> 00:09:12.580 align:start position:0% for instance or add a custom toking just 00:09:12.580 --> 00:09:15.180 align:start position:0% for instance or add a custom toking just putting<00:09:12.970> the<00:09:13.779> symbol<00:09:14.320> of<00:09:14.350> the<00:09:14.529> token<00:09:14.920> then<00:09:15.100> he 00:09:15.180 --> 00:09:15.190 align:start position:0% putting the symbol of the token then he 00:09:15.190 --> 00:09:17.370 align:start position:0% putting the symbol of the token then he was<00:09:15.339> search<00:09:15.580> on<00:09:15.820> our<00:09:15.940> previews<00:09:16.390> previously 00:09:17.370 --> 00:09:17.380 align:start position:0% was search on our previews previously 00:09:17.380 --> 00:09:23.660 align:start position:0% was search on our previews previously made<00:09:17.589> list<00:09:17.950> and<00:09:18.490> get<00:09:18.760> all<00:09:18.970> the<00:09:19.149> details<00:09:22.380> then 00:09:23.660 --> 00:09:23.670 align:start position:0% made list and get all the details then 00:09:23.670 --> 00:09:27.540 align:start position:0% made list and get all the details then after<00:09:24.670> so<00:09:24.970> after<00:09:25.779> these<00:09:25.990> three<00:09:26.589> years<00:09:26.890> as<00:09:27.310> I 00:09:27.540 --> 00:09:27.550 align:start position:0% after so after these three years as I 00:09:27.550 --> 00:09:31.470 align:start position:0% after so after these three years as I told<00:09:27.790> you<00:09:28.440> the<00:09:29.440> sink<00:09:29.830> was<00:09:30.370> sort<00:09:30.820> of<00:09:30.940> a<00:09:31.180> problem 00:09:31.470 --> 00:09:31.480 align:start position:0% told you the sink was sort of a problem 00:09:31.480 --> 00:09:34.350 align:start position:0% told you the sink was sort of a problem for<00:09:31.839> the<00:09:31.990> users<00:09:32.410> we<00:09:33.220> got<00:09:33.399> many<00:09:33.670> many<00:09:33.850> people 00:09:34.350 --> 00:09:34.360 align:start position:0% for the users we got many many people 00:09:34.360 --> 00:09:39.300 align:start position:0% for the users we got many many people saying<00:09:35.430> my<00:09:36.430> balance<00:09:36.850> is<00:09:37.000> to<00:09:37.270> zero<00:09:37.630> I'm<00:09:38.310> seeking 00:09:39.300 --> 00:09:39.310 align:start position:0% saying my balance is to zero I'm seeking 00:09:39.310 --> 00:09:41.910 align:start position:0% saying my balance is to zero I'm seeking here<00:09:39.730> for<00:09:40.029> you<00:09:40.209> know<00:09:40.330> hours<00:09:40.930> and<00:09:41.440> I<00:09:41.620> can't 00:09:41.910 --> 00:09:41.920 align:start position:0% here for you know hours and I can't 00:09:41.920 --> 00:09:47.550 align:start position:0% here for you know hours and I can't still<00:09:42.310> see<00:09:42.820> my<00:09:43.149> stuff<00:09:43.930> so<00:09:45.959> we<00:09:46.959> have<00:09:47.260> now 00:09:47.550 --> 00:09:47.560 align:start position:0% still see my stuff so we have now 00:09:47.560 --> 00:09:50.750 align:start position:0% still see my stuff so we have now integrated<00:09:48.310> missed<00:09:48.700> with<00:09:49.000> the<00:09:49.029> like<00:09:49.480> client 00:09:50.750 --> 00:09:50.760 align:start position:0% integrated missed with the like client 00:09:50.760 --> 00:09:56.190 align:start position:0% integrated missed with the like client still<00:09:51.760> in<00:09:51.910> better<00:09:52.089> version<00:09:53.430> but<00:09:54.430> they<00:09:55.200> there 00:09:56.190 --> 00:09:56.200 align:start position:0% still in better version but they there 00:09:56.200 --> 00:09:58.050 align:start position:0% still in better version but they there we<00:09:56.470> are<00:09:56.560> aiming<00:09:56.800> to<00:09:57.130> reduce<00:09:57.279> the<00:09:57.670> sinking 00:09:58.050 --> 00:09:58.060 align:start position:0% we are aiming to reduce the sinking 00:09:58.060 --> 00:10:01.230 align:start position:0% we are aiming to reduce the sinking times<00:09:58.300> by<00:09:58.600> an<00:09:58.750> order<00:09:59.079> of<00:09:59.110> magnitude<00:09:59.230> and<00:10:00.240> it's 00:10:01.230 --> 00:10:01.240 align:start position:0% times by an order of magnitude and it's 00:10:01.240 --> 00:10:04.430 align:start position:0% times by an order of magnitude and it's to<00:10:01.510> using<00:10:01.870> the<00:10:01.959> version<00:10:02.350> 1<00:10:02.589> of<00:10:02.620> the<00:10:02.890> protocol 00:10:04.430 --> 00:10:04.440 align:start position:0% to using the version 1 of the protocol 00:10:04.440 --> 00:10:08.370 align:start position:0% to using the version 1 of the protocol the<00:10:05.440> version<00:10:05.770> 2<00:10:05.950> is<00:10:06.010> about<00:10:06.370> to<00:10:06.970> come<00:10:07.380> maybe 00:10:08.370 --> 00:10:08.380 align:start position:0% the version 2 is about to come maybe 00:10:08.380 --> 00:10:10.949 align:start position:0% the version 2 is about to come maybe right<00:10:08.709> after<00:10:08.890> the<00:10:09.130> dive<00:10:09.339> calm<00:10:09.670> so<00:10:10.149> keep<00:10:10.480> posted 00:10:10.949 --> 00:10:10.959 align:start position:0% right after the dive calm so keep posted 00:10:10.959 --> 00:10:16.590 align:start position:0% right after the dive calm so keep posted ongoing<00:10:11.529> theme<00:10:11.910> team<00:10:12.910> and<00:10:13.149> miss<00:10:15.120> we<00:10:16.120> have<00:10:16.329> also 00:10:16.590 --> 00:10:16.600 align:start position:0% ongoing theme team and miss we have also 00:10:16.600 --> 00:10:18.810 align:start position:0% ongoing theme team and miss we have also buting<00:10:17.410> remix<00:10:17.800> IDE 00:10:18.810 --> 00:10:18.820 align:start position:0% buting remix IDE 00:10:18.820 --> 00:10:22.440 align:start position:0% buting remix IDE so<00:10:19.300> we're<00:10:19.779> seeing<00:10:20.459> Hudson<00:10:21.459> Jamison<00:10:21.940> will<00:10:22.180> see 00:10:22.440 --> 00:10:22.450 align:start position:0% so we're seeing Hudson Jamison will see 00:10:22.450 --> 00:10:25.850 align:start position:0% so we're seeing Hudson Jamison will see Young's<00:10:22.930> talk<00:10:23.380> right<00:10:24.010> after<00:10:24.040> mine<00:10:24.520> actually 00:10:25.850 --> 00:10:25.860 align:start position:0% Young's talk right after mine actually 00:10:25.860 --> 00:10:29.600 align:start position:0% Young's talk right after mine actually and<00:10:26.860> now<00:10:27.279> we<00:10:27.339> have<00:10:27.700> the<00:10:28.180> the<00:10:28.450> possibility<00:10:29.110> to 00:10:29.600 --> 00:10:29.610 align:start position:0% and now we have the the possibility to 00:10:29.610 --> 00:10:33.990 align:start position:0% and now we have the the possibility to for<00:10:30.610> a<00:10:30.640> developer<00:10:31.270> to<00:10:31.300> write<00:10:31.930> code<00:10:32.230> run<00:10:33.100> on<00:10:33.760> the 00:10:33.990 --> 00:10:34.000 align:start position:0% for a developer to write code run on the 00:10:34.000 --> 00:10:37.050 align:start position:0% for a developer to write code run on the main<00:10:34.180> ad<00:10:34.390> or<00:10:34.600> on<00:10:34.870> the<00:10:34.959> test<00:10:35.230> nets<00:10:35.820> and<00:10:36.820> that's 00:10:37.050 --> 00:10:37.060 align:start position:0% main ad or on the test nets and that's 00:10:37.060 --> 00:10:40.650 align:start position:0% main ad or on the test nets and that's quite<00:10:37.360> powerful<00:10:38.579> the<00:10:39.579> developers<00:10:40.060> also<00:10:40.240> able 00:10:40.650 --> 00:10:40.660 align:start position:0% quite powerful the developers also able 00:10:40.660 --> 00:10:44.790 align:start position:0% quite powerful the developers also able to<00:10:42.120> debug<00:10:43.120> transactions<00:10:43.930> to<00:10:44.350> see<00:10:44.589> what 00:10:44.790 --> 00:10:44.800 align:start position:0% to debug transactions to see what 00:10:44.800 --> 00:10:47.760 align:start position:0% to debug transactions to see what exactly<00:10:44.950> what<00:10:45.520> steps<00:10:45.959> that<00:10:46.959> transaction<00:10:47.589> made 00:10:47.760 --> 00:10:47.770 align:start position:0% exactly what steps that transaction made 00:10:47.770 --> 00:10:50.190 align:start position:0% exactly what steps that transaction made what<00:10:48.130> were<00:10:48.339> the<00:10:48.640> state<00:10:48.970> the<00:10:49.630> states<00:10:49.899> of<00:10:50.079> the 00:10:50.190 --> 00:10:50.200 align:start position:0% what were the state the states of the 00:10:50.200 --> 00:10:55.100 align:start position:0% what were the state the states of the variables<00:10:50.649> so<00:10:52.740> we<00:10:53.740> also<00:10:53.890> did 00:10:55.100 --> 00:10:55.110 align:start position:0% variables so we also did 00:10:55.110 --> 00:10:57.710 align:start position:0% variables so we also did and<00:10:55.200> really<00:10:56.070> easy<00:10:56.310> way<00:10:56.640> for<00:10:56.700> the<00:10:57.180> developer 00:10:57.710 --> 00:10:57.720 align:start position:0% and really easy way for the developer 00:10:57.720 --> 00:11:01.430 align:start position:0% and really easy way for the developer user<00:10:57.990> which<00:10:58.920> is<00:10:58.950> solo<00:10:59.610> Network<00:11:00.140> you<00:11:01.140> will<00:11:01.260> make 00:11:01.430 --> 00:11:01.440 align:start position:0% user which is solo Network you will make 00:11:01.440 --> 00:11:08.210 align:start position:0% user which is solo Network you will make use<00:11:01.740> of<00:11:01.769> the<00:11:03.740> Goethe<00:11:04.740> on<00:11:05.779> dab<00:11:06.779> flag<00:11:07.290> so<00:11:07.920> you<00:11:08.010> can 00:11:08.210 --> 00:11:08.220 align:start position:0% use of the Goethe on dab flag so you can 00:11:08.220 --> 00:11:09.980 align:start position:0% use of the Goethe on dab flag so you can have<00:11:08.490> your<00:11:08.700> own<00:11:08.910> private<00:11:09.209> GUI<00:11:09.600> theorem 00:11:09.980 --> 00:11:09.990 align:start position:0% have your own private GUI theorem 00:11:09.990 --> 00:11:13.220 align:start position:0% have your own private GUI theorem blockchain<00:11:11.180> so<00:11:12.180> this<00:11:12.450> is<00:11:12.570> not<00:11:12.779> actually<00:11:12.959> a 00:11:13.220 --> 00:11:13.230 align:start position:0% blockchain so this is not actually a 00:11:13.230 --> 00:11:16.400 align:start position:0% blockchain so this is not actually a simulation<00:11:13.529> is<00:11:14.040> the<00:11:14.310> real<00:11:14.579> deal<00:11:14.880> you<00:11:15.630> run<00:11:15.870> an 00:11:16.400 --> 00:11:16.410 align:start position:0% simulation is the real deal you run an 00:11:16.410 --> 00:11:18.889 align:start position:0% simulation is the real deal you run an empty<00:11:16.860> block<00:11:17.160> chain<00:11:17.459> from<00:11:17.730> scratch<00:11:18.089> in<00:11:18.660> your 00:11:18.889 --> 00:11:18.899 align:start position:0% empty block chain from scratch in your 00:11:18.899 --> 00:11:22.310 align:start position:0% empty block chain from scratch in your machine<00:11:19.339> and<00:11:20.339> you<00:11:21.000> can<00:11:21.029> manage<00:11:21.450> mining<00:11:22.050> from 00:11:22.310 --> 00:11:22.320 align:start position:0% machine and you can manage mining from 00:11:22.320 --> 00:11:27.759 align:start position:0% machine and you can manage mining from the<00:11:22.440> interface<00:11:23.089> so<00:11:24.089> that<00:11:24.810> is<00:11:25.970> mist<00:11:26.970> aiming<00:11:27.450> to 00:11:27.759 --> 00:11:27.769 align:start position:0% the interface so that is mist aiming to 00:11:27.769 --> 00:11:32.509 align:start position:0% the interface so that is mist aiming to for<00:11:28.769> a<00:11:28.800> larger<00:11:29.459> adoption<00:11:29.940> of<00:11:30.060> developers<00:11:31.519> we 00:11:32.509 --> 00:11:32.519 align:start position:0% for a larger adoption of developers we 00:11:32.519 --> 00:11:35.870 align:start position:0% for a larger adoption of developers we also<00:11:32.640> had<00:11:34.040> by<00:11:35.040> the<00:11:35.100> end<00:11:35.279> of<00:11:35.339> the<00:11:35.519> last<00:11:35.700> year 00:11:35.870 --> 00:11:35.880 align:start position:0% also had by the end of the last year 00:11:35.880 --> 00:11:39.259 align:start position:0% also had by the end of the last year windows<00:11:36.839> installer<00:11:37.320> so<00:11:37.829> people<00:11:38.310> you<00:11:38.850> know<00:11:38.910> got 00:11:39.259 --> 00:11:39.269 align:start position:0% windows installer so people you know got 00:11:39.269 --> 00:11:44.230 align:start position:0% windows installer so people you know got happier<00:11:40.370> and<00:11:41.370> now<00:11:42.089> some<00:11:42.390> planning<00:11:42.930> features 00:11:44.230 --> 00:11:44.240 align:start position:0% happier and now some planning features 00:11:44.240 --> 00:11:46.430 align:start position:0% happier and now some planning features account<00:11:45.240> management<00:11:45.600> is<00:11:45.930> one<00:11:46.140> of<00:11:46.260> those 00:11:46.430 --> 00:11:46.440 align:start position:0% account management is one of those 00:11:46.440 --> 00:11:50.569 align:start position:0% account management is one of those really<00:11:46.920> really<00:11:47.070> important<00:11:47.700> ones<00:11:49.279> which<00:11:50.279> would 00:11:50.569 --> 00:11:50.579 align:start position:0% really really important ones which would 00:11:50.579 --> 00:11:52.579 align:start position:0% really really important ones which would leverage<00:11:50.880> the<00:11:51.180> power<00:11:51.390> of<00:11:51.589> standalone 00:11:52.579 --> 00:11:52.589 align:start position:0% leverage the power of standalone 00:11:52.589 --> 00:11:56.660 align:start position:0% leverage the power of standalone transaction<00:11:53.339> signer<00:11:54.529> enabling<00:11:55.529> remote<00:11:56.190> node 00:11:56.660 --> 00:11:56.670 align:start position:0% transaction signer enabling remote node 00:11:56.670 --> 00:12:00.610 align:start position:0% transaction signer enabling remote node management<00:11:57.329> and<00:11:58.279> easy<00:11:59.279> to<00:11:59.699> switch<00:12:00.029> between 00:12:00.610 --> 00:12:00.620 align:start position:0% management and easy to switch between 00:12:00.620 --> 00:12:05.449 align:start position:0% management and easy to switch between nodes<00:12:02.510> here's<00:12:03.510> the<00:12:03.600> deal<00:12:03.810> if<00:12:04.589> we<00:12:04.649> want<00:12:05.040> to<00:12:05.220> use 00:12:05.449 --> 00:12:05.459 align:start position:0% nodes here's the deal if we want to use 00:12:05.459 --> 00:12:09.949 align:start position:0% nodes here's the deal if we want to use in<00:12:05.850> footer<00:12:06.180> for<00:12:06.540> instance<00:12:06.959> for<00:12:07.500> any<00:12:07.740> reason<00:12:08.959> we 00:12:09.949 --> 00:12:09.959 align:start position:0% in footer for instance for any reason we 00:12:09.959 --> 00:12:12.470 align:start position:0% in footer for instance for any reason we would<00:12:10.199> sign<00:12:10.589> those<00:12:10.949> transactions<00:12:11.910> from 00:12:12.470 --> 00:12:12.480 align:start position:0% would sign those transactions from 00:12:12.480 --> 00:12:16.790 align:start position:0% would sign those transactions from within<00:12:12.779> designer<00:12:14.149> all<00:12:15.149> those<00:12:15.570> account<00:12:16.500> keys 00:12:16.790 --> 00:12:16.800 align:start position:0% within designer all those account keys 00:12:16.800 --> 00:12:18.560 align:start position:0% within designer all those account keys would<00:12:17.220> be<00:12:17.399> held<00:12:17.670> at<00:12:17.880> is<00:12:18.029> at<00:12:18.180> the<00:12:18.329> same 00:12:18.560 --> 00:12:18.570 align:start position:0% would be held at is at the same 00:12:18.570 --> 00:12:21.110 align:start position:0% would be held at is at the same directory<00:12:19.230> and<00:12:19.709> we<00:12:20.190> could<00:12:20.430> even<00:12:20.610> switch 00:12:21.110 --> 00:12:21.120 align:start position:0% directory and we could even switch 00:12:21.120 --> 00:12:24.560 align:start position:0% directory and we could even switch between<00:12:21.449> notes<00:12:22.070> could<00:12:23.070> be<00:12:23.279> going<00:12:23.550> theorem<00:12:24.060> by 00:12:24.560 --> 00:12:24.570 align:start position:0% between notes could be going theorem by 00:12:24.570 --> 00:12:28.480 align:start position:0% between notes could be going theorem by theorem<00:12:25.079> or<00:12:25.260> any<00:12:25.529> other<00:12:26.810> having<00:12:27.810> all<00:12:28.110> those 00:12:28.480 --> 00:12:28.490 align:start position:0% theorem or any other having all those 00:12:28.490 --> 00:12:31.009 align:start position:0% theorem or any other having all those keys<00:12:29.490> managed<00:12:30.000> by<00:12:30.209> best 00:12:31.009 --> 00:12:31.019 align:start position:0% keys managed by best 00:12:31.019 --> 00:12:37.910 align:start position:0% keys managed by best couldn't<00:12:31.709> be<00:12:31.829> even<00:12:32.670> harder<00:12:32.940> wallets<00:12:34.790> so<00:12:36.920> this 00:12:37.910 --> 00:12:37.920 align:start position:0% couldn't be even harder wallets so this 00:12:37.920 --> 00:12:40.069 align:start position:0% couldn't be even harder wallets so this account<00:12:38.430> management<00:12:38.730> would<00:12:39.120> lead<00:12:39.329> to<00:12:39.360> having 00:12:40.069 --> 00:12:40.079 align:start position:0% account management would lead to having 00:12:40.079 --> 00:12:42.650 align:start position:0% account management would lead to having those<00:12:40.199> boots<00:12:40.529> pool<00:12:40.800> with<00:12:41.100> your<00:12:41.339> clients<00:12:41.880> so 00:12:42.650 --> 00:12:42.660 align:start position:0% those boots pool with your clients so 00:12:42.660 --> 00:12:44.980 align:start position:0% those boots pool with your clients so you<00:12:42.690> could<00:12:42.959> use<00:12:43.170> their<00:12:43.350> own<00:12:43.620> favorite<00:12:44.370> node 00:12:44.980 --> 00:12:44.990 align:start position:0% you could use their own favorite node 00:12:44.990 --> 00:12:47.630 align:start position:0% you could use their own favorite node having<00:12:45.990> nearly<00:12:46.350> support<00:12:46.920> to<00:12:47.220> e<00:12:47.250> theorem 00:12:47.630 --> 00:12:47.640 align:start position:0% having nearly support to e theorem 00:12:47.640 --> 00:12:51.199 align:start position:0% having nearly support to e theorem clients<00:12:48.709> it's<00:12:49.709> actually<00:12:50.130> a<00:12:50.160> JSON<00:12:50.699> manifest 00:12:51.199 --> 00:12:51.209 align:start position:0% clients it's actually a JSON manifest 00:12:51.209 --> 00:12:56.240 align:start position:0% clients it's actually a JSON manifest which<00:12:52.079> we<00:12:52.380> already<00:12:52.740> did<00:12:53.160> so<00:12:53.930> it<00:12:54.930> only<00:12:55.079> has<00:12:55.350> gas 00:12:56.240 --> 00:12:56.250 align:start position:0% which we already did so it only has gas 00:12:56.250 --> 00:12:59.540 align:start position:0% which we already did so it only has gas for<00:12:56.760> now<00:12:57.740> all<00:12:58.740> those<00:12:58.949> accounts<00:12:59.220> will<00:12:59.519> be 00:12:59.540 --> 00:12:59.550 align:start position:0% for now all those accounts will be 00:12:59.550 --> 00:13:02.630 align:start position:0% for now all those accounts will be managed<00:12:59.850> by<00:13:00.029> mist<00:13:00.360> so<00:13:00.769> if<00:13:01.769> you<00:13:02.010> switch<00:13:02.220> nodes 00:13:02.630 --> 00:13:02.640 align:start position:0% managed by mist so if you switch nodes 00:13:02.640 --> 00:13:05.150 align:start position:0% managed by mist so if you switch nodes you<00:13:03.390> would<00:13:03.510> cease<00:13:03.750> to<00:13:04.050> still<00:13:04.709> see<00:13:04.949> all<00:13:04.980> the 00:13:05.150 --> 00:13:05.160 align:start position:0% you would cease to still see all the 00:13:05.160 --> 00:13:06.600 align:start position:0% you would cease to still see all the same<00:13:05.490> accounts 00:13:06.600 --> 00:13:06.610 align:start position:0% same accounts 00:13:06.610 --> 00:13:10.330 align:start position:0% same accounts so<00:13:07.610> we're<00:13:07.940> under<00:13:08.210> actually<00:13:09.200> a<00:13:09.590> major<00:13:10.070> if 00:13:10.330 --> 00:13:10.340 align:start position:0% so we're under actually a major if 00:13:10.340 --> 00:13:13.240 align:start position:0% so we're under actually a major if factor<00:13:10.760> being<00:13:11.420> led<00:13:11.630> by<00:13:11.870> mark<00:13:12.260> please<00:13:12.740> yeah 00:13:13.240 --> 00:13:13.250 align:start position:0% factor being led by mark please yeah 00:13:13.250 --> 00:13:17.890 align:start position:0% factor being led by mark please yeah maybe<00:13:13.610> yeah<00:13:14.300> mark<00:13:15.010> show<00:13:16.010> yourself<00:13:16.690> he's<00:13:17.690> not 00:13:17.890 --> 00:13:17.900 align:start position:0% maybe yeah mark show yourself he's not 00:13:17.900 --> 00:13:20.370 align:start position:0% maybe yeah mark show yourself he's not here<00:13:18.110> hi<00:13:18.440> oh<00:13:18.920> here<00:13:19.310> yes 00:13:20.370 --> 00:13:20.380 align:start position:0% here hi oh here yes 00:13:20.380 --> 00:13:23.500 align:start position:0% here hi oh here yes mark<00:13:21.380> is<00:13:21.530> our<00:13:21.710> new<00:13:22.040> addition<00:13:22.610> he's<00:13:22.940> a<00:13:22.970> Redux 00:13:23.500 --> 00:13:23.510 align:start position:0% mark is our new addition he's a Redux 00:13:23.510 --> 00:13:26.970 align:start position:0% mark is our new addition he's a Redux book<00:13:23.810> author<00:13:24.140> a<00:13:24.560> really<00:13:25.070> skilled<00:13:25.430> developer 00:13:26.970 --> 00:13:26.980 align:start position:0% book author a really skilled developer 00:13:26.980 --> 00:13:30.370 align:start position:0% book author a really skilled developer so<00:13:27.980> he<00:13:28.280> is<00:13:28.340> fixing<00:13:29.060> ternal<00:13:29.420> state<00:13:29.660> issues<00:13:30.140> for 00:13:30.370 --> 00:13:30.380 align:start position:0% so he is fixing ternal state issues for 00:13:30.380 --> 00:13:34.150 align:start position:0% so he is fixing ternal state issues for now<00:13:30.730> which<00:13:31.730> is<00:13:32.140> mainly<00:13:33.140> the<00:13:33.410> foundation<00:13:33.950> for 00:13:34.150 --> 00:13:34.160 align:start position:0% now which is mainly the foundation for 00:13:34.160 --> 00:13:37.540 align:start position:0% now which is mainly the foundation for major<00:13:34.460> features<00:13:34.970> to<00:13:35.150> come<00:13:36.400> we're<00:13:37.400> also 00:13:37.540 --> 00:13:37.550 align:start position:0% major features to come we're also 00:13:37.550 --> 00:13:40.170 align:start position:0% major features to come we're also thinking<00:13:37.850> about<00:13:38.060> having<00:13:38.630> a<00:13:38.960> sink<00:13:39.440> jumpstart 00:13:40.170 --> 00:13:40.180 align:start position:0% thinking about having a sink jumpstart 00:13:40.180 --> 00:13:42.550 align:start position:0% thinking about having a sink jumpstart which<00:13:41.180> is<00:13:41.330> something<00:13:41.690> really<00:13:41.990> awesome<00:13:42.170> in 00:13:42.550 --> 00:13:42.560 align:start position:0% which is something really awesome in 00:13:42.560 --> 00:13:46.300 align:start position:0% which is something really awesome in order<00:13:42.740> to<00:13:42.890> fix<00:13:43.130> that<00:13:43.460> zero<00:13:43.820> balance<00:13:44.030> issues<00:13:45.310> so 00:13:46.300 --> 00:13:46.310 align:start position:0% order to fix that zero balance issues so 00:13:46.310 --> 00:13:50.050 align:start position:0% order to fix that zero balance issues so you<00:13:46.550> would<00:13:46.820> start<00:13:48.640> connected<00:13:49.640> to<00:13:49.820> a<00:13:49.850> remote 00:13:50.050 --> 00:13:50.060 align:start position:0% you would start connected to a remote 00:13:50.060 --> 00:13:53.440 align:start position:0% you would start connected to a remote node<00:13:50.590> so<00:13:51.590> you<00:13:51.680> would<00:13:52.040> see<00:13:52.340> all<00:13:52.610> your<00:13:52.880> balances 00:13:53.440 --> 00:13:53.450 align:start position:0% node so you would see all your balances 00:13:53.450 --> 00:13:56.550 align:start position:0% node so you would see all your balances all<00:13:53.690> your<00:13:53.960> all<00:13:54.380> your<00:13:54.770> stuff<00:13:55.070> like<00:13:55.580> real-time 00:13:56.550 --> 00:13:56.560 align:start position:0% all your all your stuff like real-time 00:13:56.560 --> 00:14:00.400 align:start position:0% all your all your stuff like real-time then<00:13:57.560> you'd<00:13:57.770> have<00:13:58.040> a<00:13:58.100> background<00:13:58.670> sync<00:13:59.410> so 00:14:00.400 --> 00:14:00.410 align:start position:0% then you'd have a background sync so 00:14:00.410 --> 00:14:03.060 align:start position:0% then you'd have a background sync so that<00:14:00.800> would<00:14:00.980> progress<00:14:01.190> progress<00:14:01.820> progress 00:14:03.060 --> 00:14:03.070 align:start position:0% that would progress progress progress 00:14:03.070 --> 00:14:06.490 align:start position:0% that would progress progress progress when<00:14:04.070> it<00:14:04.100> comes<00:14:04.430> to<00:14:04.820> the<00:14:05.090> right<00:14:05.300> point<00:14:05.690> you 00:14:06.490 --> 00:14:06.500 align:start position:0% when it comes to the right point you 00:14:06.500 --> 00:14:09.610 align:start position:0% when it comes to the right point you would<00:14:06.680> switch<00:14:06.920> over<00:14:07.630> so<00:14:08.630> you<00:14:08.690> would<00:14:09.080> switch<00:14:09.290> to 00:14:09.610 --> 00:14:09.620 align:start position:0% would switch over so you would switch to 00:14:09.620 --> 00:14:14.080 align:start position:0% would switch over so you would switch to lie<00:14:09.890> client<00:14:10.310> or<00:14:10.460> foo<00:14:11.000> node<00:14:11.210> over<00:14:11.540> choice<00:14:13.090> there 00:14:14.080 --> 00:14:14.090 align:start position:0% lie client or foo node over choice there 00:14:14.090 --> 00:14:16.900 align:start position:0% lie client or foo node over choice there is<00:14:14.180> also<00:14:14.360> this<00:14:14.840> important<00:14:15.410> news<00:14:16.040> for<00:14:16.400> the<00:14:16.640> DAP 00:14:16.900 --> 00:14:16.910 align:start position:0% is also this important news for the DAP 00:14:16.910 --> 00:14:19.710 align:start position:0% is also this important news for the DAP developers<00:14:17.740> that<00:14:18.740> we're<00:14:18.950> planning<00:14:19.220> to 00:14:19.710 --> 00:14:19.720 align:start position:0% developers that we're planning to 00:14:19.720 --> 00:14:24.570 align:start position:0% developers that we're planning to isolate<00:14:20.720> local<00:14:21.680> storage<00:14:22.360> between<00:14:23.360> networks 00:14:24.570 --> 00:14:24.580 align:start position:0% isolate local storage between networks 00:14:24.580 --> 00:14:29.620 align:start position:0% isolate local storage between networks so<00:14:25.580> you<00:14:25.610> would<00:14:26.120> have<00:14:27.130> different<00:14:28.130> scopes<00:14:28.760> to 00:14:29.620 --> 00:14:29.630 align:start position:0% so you would have different scopes to 00:14:29.630 --> 00:14:30.370 align:start position:0% so you would have different scopes to work<00:14:29.810> with 00:14:30.370 --> 00:14:30.380 align:start position:0% work with 00:14:30.380 --> 00:14:34.060 align:start position:0% work with so<00:14:30.620> the<00:14:30.860> DAP<00:14:31.040> developer<00:14:31.580> wouldn't<00:14:31.970> be<00:14:33.070> worried 00:14:34.060 --> 00:14:34.070 align:start position:0% so the DAP developer wouldn't be worried 00:14:34.070 --> 00:14:37.810 align:start position:0% so the DAP developer wouldn't be worried anymore<00:14:34.400> about<00:14:34.910> having<00:14:35.450> main<00:14:36.230> at<00:14:36.490> storage<00:14:37.490> and 00:14:37.810 --> 00:14:37.820 align:start position:0% anymore about having main at storage and 00:14:37.820 --> 00:14:43.420 align:start position:0% anymore about having main at storage and that's<00:14:38.600> net<00:14:38.870> storage<00:14:39.200> and<00:14:40.270> you<00:14:41.270> know<00:14:41.390> I<00:14:42.430> also 00:14:43.420 --> 00:14:43.430 align:start position:0% that's net storage and you know I also 00:14:43.430 --> 00:14:45.280 align:start position:0% that's net storage and you know I also transaction<00:14:44.120> Spectre<00:14:44.630> which<00:14:44.900> is<00:14:45.080> something 00:14:45.280 --> 00:14:45.290 align:start position:0% transaction Spectre which is something 00:14:45.290 --> 00:14:49.240 align:start position:0% transaction Spectre which is something you<00:14:46.040> know<00:14:46.160> it's<00:14:46.400> time<00:14:46.670> it<00:14:46.820> for<00:14:47.030> us<00:14:47.150> to<00:14:47.330> have<00:14:48.250> we 00:14:49.240 --> 00:14:49.250 align:start position:0% you know it's time it for us to have we 00:14:49.250 --> 00:14:50.890 align:start position:0% you know it's time it for us to have we would<00:14:49.400> show<00:14:49.640> pending<00:14:50.060> in<00:14:50.210> past 00:14:50.890 --> 00:14:50.900 align:start position:0% would show pending in past 00:14:50.900 --> 00:14:55.960 align:start position:0% would show pending in past no<00:14:51.740> more<00:14:52.010> per<00:14:52.490> dab<00:14:52.730> setup<00:14:53.240> because<00:14:53.540> as<00:14:54.970> taking 00:14:55.960 --> 00:14:55.970 align:start position:0% no more per dab setup because as taking 00:14:55.970 --> 00:14:58.180 align:start position:0% no more per dab setup because as taking the<00:14:56.060> wallet<00:14:56.390> as<00:14:56.510> an<00:14:56.720> example<00:14:57.080> he<00:14:57.410> handles<00:14:57.770> all 00:14:58.180 --> 00:14:58.190 align:start position:0% the wallet as an example he handles all 00:14:58.190 --> 00:15:01.210 align:start position:0% the wallet as an example he handles all its<00:14:58.670> transactions<00:14:59.390> and<00:14:59.630> pass<00:14:59.870> in<00:15:00.110> history<00:15:00.560> so 00:15:01.210 --> 00:15:01.220 align:start position:0% its transactions and pass in history so 00:15:01.220 --> 00:15:04.170 align:start position:0% its transactions and pass in history so that<00:15:01.490> wouldn't<00:15:01.880> be<00:15:02.030> necessary<00:15:02.450> anymore 00:15:04.170 --> 00:15:04.180 align:start position:0% that wouldn't be necessary anymore 00:15:04.180 --> 00:15:08.080 align:start position:0% that wouldn't be necessary anymore always<00:15:05.180> a<00:15:05.450> bi<00:15:05.660> look<00:15:05.990> up<00:15:06.200> so<00:15:06.500> you'd<00:15:06.680> see<00:15:07.090> once 00:15:08.080 --> 00:15:08.090 align:start position:0% always a bi look up so you'd see once 00:15:08.090 --> 00:15:12.150 align:start position:0% always a bi look up so you'd see once that<00:15:08.510> methods<00:15:09.410> are<00:15:09.710> on<00:15:10.610> the<00:15:10.790> direct<00:15:11.150> research 00:15:12.150 --> 00:15:12.160 align:start position:0% that methods are on the direct research 00:15:12.160 --> 00:15:16.990 align:start position:0% that methods are on the direct research that<00:15:13.160> would<00:15:13.250> be<00:15:13.460> so<00:15:14.390> evident<00:15:15.700> and<00:15:16.700> you<00:15:16.880> would 00:15:16.990 --> 00:15:17.000 align:start position:0% that would be so evident and you would 00:15:17.000 --> 00:15:19.640 align:start position:0% that would be so evident and you would see<00:15:17.240> perfectly<00:15:18.050> the<00:15:18.260> transaction<00:15:18.800> details 00:15:19.640 --> 00:15:19.650 align:start position:0% see perfectly the transaction details 00:15:19.650 --> 00:15:23.269 align:start position:0% see perfectly the transaction details and<00:15:20.330> speaking<00:15:21.330> of<00:15:21.390> the<00:15:21.570> iam<00:15:21.870> wallet<00:15:22.230> it's<00:15:23.040> time 00:15:23.269 --> 00:15:23.279 align:start position:0% and speaking of the iam wallet it's time 00:15:23.279 --> 00:15:24.170 align:start position:0% and speaking of the iam wallet it's time for<00:15:23.550> a<00:15:23.580> change 00:15:24.170 --> 00:15:24.180 align:start position:0% for a change 00:15:24.180 --> 00:15:29.990 align:start position:0% for a change so<00:15:25.130> back<00:15:26.130> then<00:15:27.200> you<00:15:28.200> would<00:15:28.410> it<00:15:29.160> was<00:15:29.370> one<00:15:29.730> of<00:15:29.850> the 00:15:29.990 --> 00:15:30.000 align:start position:0% so back then you would it was one of the 00:15:30.000 --> 00:15:33.079 align:start position:0% so back then you would it was one of the most<00:15:30.930> ideal<00:15:31.290> ways<00:15:31.740> for<00:15:32.070> you<00:15:32.130> to<00:15:32.310> kick<00:15:32.520> start<00:15:32.670> on 00:15:33.079 --> 00:15:33.089 align:start position:0% most ideal ways for you to kick start on 00:15:33.089 --> 00:15:35.660 align:start position:0% most ideal ways for you to kick start on your<00:15:33.210> solidity<00:15:33.750> project<00:15:34.290> but<00:15:35.130> now<00:15:35.339> we<00:15:35.400> have 00:15:35.660 --> 00:15:35.670 align:start position:0% your solidity project but now we have 00:15:35.670 --> 00:15:39.050 align:start position:0% your solidity project but now we have some<00:15:35.940> powerful<00:15:36.240> tools<00:15:36.420> like<00:15:36.990> remix<00:15:37.440> and<00:15:38.060> maybe 00:15:39.050 --> 00:15:39.060 align:start position:0% some powerful tools like remix and maybe 00:15:39.060 --> 00:15:40.610 align:start position:0% some powerful tools like remix and maybe we<00:15:39.240> don't<00:15:39.450> need<00:15:39.630> some<00:15:39.870> features<00:15:40.320> that<00:15:40.470> we<00:15:40.589> have 00:15:40.610 --> 00:15:40.620 align:start position:0% we don't need some features that we have 00:15:40.620 --> 00:15:43.940 align:start position:0% we don't need some features that we have in<00:15:40.890> the<00:15:40.980> past<00:15:41.160> so<00:15:41.810> now<00:15:42.810> we<00:15:42.870> see<00:15:43.200> it<00:15:43.260> as<00:15:43.529> the 00:15:43.940 --> 00:15:43.950 align:start position:0% in the past so now we see it as the 00:15:43.950 --> 00:15:46.640 align:start position:0% in the past so now we see it as the ideal<00:15:44.430> way<00:15:44.610> of<00:15:44.870> starting<00:15:45.870> as<00:15:46.020> a<00:15:46.050> solidity 00:15:46.640 --> 00:15:46.650 align:start position:0% ideal way of starting as a solidity 00:15:46.650 --> 00:15:51.170 align:start position:0% ideal way of starting as a solidity development<00:15:47.279> is<00:15:47.940> having<00:15:48.779> Wow<00:15:49.700> in<00:15:50.700> remix 00:15:51.170 --> 00:15:51.180 align:start position:0% development is having Wow in remix 00:15:51.180 --> 00:15:53.840 align:start position:0% development is having Wow in remix itself<00:15:51.740> so<00:15:52.740> we're<00:15:53.010> planning<00:15:53.190> to<00:15:53.520> deprecate 00:15:53.840 --> 00:15:53.850 align:start position:0% itself so we're planning to deprecate 00:15:53.850 --> 00:15:56.750 align:start position:0% itself so we're planning to deprecate some<00:15:54.480> features<00:15:54.930> in<00:15:55.589> order<00:15:55.770> to<00:15:56.100> have<00:15:56.520> more 00:15:56.750 --> 00:15:56.760 align:start position:0% some features in order to have more 00:15:56.760 --> 00:16:01.310 align:start position:0% some features in order to have more simplicity<00:15:58.910> and<00:15:59.910> we're<00:16:00.210> planning<00:16:00.570> to<00:16:00.690> have<00:16:00.930> a 00:16:01.310 --> 00:16:01.320 align:start position:0% simplicity and we're planning to have a 00:16:01.320 --> 00:16:06.260 align:start position:0% simplicity and we're planning to have a new<00:16:01.500> wallet<00:16:01.740> wallet<00:16:02.190> contract<00:16:05.180> there<00:16:06.180> are 00:16:06.260 --> 00:16:06.270 align:start position:0% new wallet wallet contract there are 00:16:06.270 --> 00:16:09.890 align:start position:0% new wallet wallet contract there are some<00:16:06.480> other<00:16:07.040> audited<00:16:08.040> and<00:16:08.310> solid<00:16:09.000> work<00:16:09.240> around 00:16:09.890 --> 00:16:09.900 align:start position:0% some other audited and solid work around 00:16:09.900 --> 00:16:12.170 align:start position:0% some other audited and solid work around so<00:16:10.230> we're<00:16:10.410> playing<00:16:10.710> to<00:16:11.040> in<00:16:11.400> the<00:16:11.550> near<00:16:11.970> future 00:16:12.170 --> 00:16:12.180 align:start position:0% so we're playing to in the near future 00:16:12.180 --> 00:16:16.900 align:start position:0% so we're playing to in the near future to<00:16:12.600> change<00:16:12.810> that<00:16:13.880> well<00:16:15.380> this<00:16:16.380> is<00:16:16.589> about 00:16:16.900 --> 00:16:16.910 align:start position:0% to change that well this is about 00:16:16.910 --> 00:16:21.530 align:start position:0% to change that well this is about developers<00:16:17.910> yeah<00:16:19.100> so<00:16:20.100> we<00:16:20.520> plan<00:16:20.760> to<00:16:20.910> have<00:16:21.120> very 00:16:21.530 --> 00:16:21.540 align:start position:0% developers yeah so we plan to have very 00:16:21.540 --> 00:16:24.380 align:start position:0% developers yeah so we plan to have very integration<00:16:22.140> with<00:16:22.290> remix<00:16:22.820> improving<00:16:23.820> private 00:16:24.380 --> 00:16:24.390 align:start position:0% integration with remix improving private 00:16:24.390 --> 00:16:27.470 align:start position:0% integration with remix improving private net<00:16:24.570> integrations<00:16:25.940> kick-starts<00:16:26.940> and<00:16:27.120> purpose 00:16:27.470 --> 00:16:27.480 align:start position:0% net integrations kick-starts and purpose 00:16:27.480 --> 00:16:31.070 align:start position:0% net integrations kick-starts and purpose magic<00:16:27.990> and<00:16:28.490> of<00:16:29.490> course<00:16:29.820> we're<00:16:30.180> totally<00:16:30.660> open 00:16:31.070 --> 00:16:31.080 align:start position:0% magic and of course we're totally open 00:16:31.080 --> 00:16:33.650 align:start position:0% magic and of course we're totally open to<00:16:31.110> suggestions<00:16:31.890> so<00:16:32.130> you<00:16:32.610> can<00:16:32.880> guys<00:16:33.060> reach<00:16:33.450> me 00:16:33.650 --> 00:16:33.660 align:start position:0% to suggestions so you can guys reach me 00:16:33.660 --> 00:16:37.699 align:start position:0% to suggestions so you can guys reach me out<00:16:33.779> before<00:16:35.209> before<00:16:36.209> lunch<00:16:36.900> or<00:16:37.290> maybe 00:16:37.699 --> 00:16:37.709 align:start position:0% out before before lunch or maybe 00:16:37.709 --> 00:16:42.079 align:start position:0% out before before lunch or maybe something<00:16:39.560> speaking<00:16:40.560> of<00:16:40.830> the<00:16:41.160> ecosystem 00:16:42.079 --> 00:16:42.089 align:start position:0% something speaking of the ecosystem 00:16:42.089 --> 00:16:45.560 align:start position:0% something speaking of the ecosystem we're<00:16:42.270> trying<00:16:42.600> to<00:16:42.750> build<00:16:42.930> here<00:16:43.080> I<00:16:44.480> think<00:16:45.480> it 00:16:45.560 --> 00:16:45.570 align:start position:0% we're trying to build here I think it 00:16:45.570 --> 00:16:47.810 align:start position:0% we're trying to build here I think it makes<00:16:45.900> a<00:16:46.080> lot<00:16:46.110> of<00:16:46.290> sense<00:16:46.680> if<00:16:46.920> we<00:16:47.100> if<00:16:47.339> we<00:16:47.580> could 00:16:47.810 --> 00:16:47.820 align:start position:0% makes a lot of sense if we if we could 00:16:47.820 --> 00:16:54.199 align:start position:0% makes a lot of sense if we if we could have<00:16:48.089> some<00:16:48.470> depth<00:16:49.470> rest<00:16:49.980> meter<00:16:51.950> because<00:16:53.209> there 00:16:54.199 --> 00:16:54.209 align:start position:0% have some depth rest meter because there 00:16:54.209 --> 00:16:56.510 align:start position:0% have some depth rest meter because there is<00:16:54.300> a<00:16:54.330> fundamental<00:16:54.600> question<00:16:55.529> about<00:16:55.589> about 00:16:56.510 --> 00:16:56.520 align:start position:0% is a fundamental question about about 00:16:56.520 --> 00:17:00.530 align:start position:0% is a fundamental question about about this<00:16:57.410> should<00:16:58.410> apps<00:16:58.790> have<00:16:59.790> access<00:17:00.209> to<00:17:00.420> your 00:17:00.530 --> 00:17:00.540 align:start position:0% this should apps have access to your 00:17:00.540 --> 00:17:05.260 align:start position:0% this should apps have access to your HTTP<00:17:01.520> if<00:17:02.520> the<00:17:02.850> apps<00:17:02.940> could<00:17:03.330> be<00:17:03.480> run<00:17:03.690> from<00:17:04.050> swarm 00:17:05.260 --> 00:17:05.270 align:start position:0% HTTP if the apps could be run from swarm 00:17:05.270 --> 00:17:08.439 align:start position:0% HTTP if the apps could be run from swarm could<00:17:06.270> be<00:17:06.420> loaded<00:17:06.600> from<00:17:06.870> swarm<00:17:07.319> would<00:17:07.980> they 00:17:08.439 --> 00:17:08.449 align:start position:0% could be loaded from swarm would they 00:17:08.449 --> 00:17:11.179 align:start position:0% could be loaded from swarm would they does<00:17:09.449> that<00:17:09.630> make<00:17:09.809> sense<00:17:09.839> even<00:17:10.500> sense<00:17:10.800> to<00:17:11.040> have 00:17:11.179 --> 00:17:11.189 align:start position:0% does that make sense even sense to have 00:17:11.189 --> 00:17:14.720 align:start position:0% does that make sense even sense to have access<00:17:11.610> to<00:17:11.670> HTTP<00:17:12.709> we<00:17:13.709> all<00:17:13.800> know<00:17:13.949> the<00:17:14.160> web<00:17:14.370> now 00:17:14.720 --> 00:17:14.730 align:start position:0% access to HTTP we all know the web now 00:17:14.730 --> 00:17:17.919 align:start position:0% access to HTTP we all know the web now is<00:17:14.970> full<00:17:15.209> of<00:17:15.380> trackers<00:17:16.380> from<00:17:16.709> all<00:17:16.949> kinds<00:17:17.610> and 00:17:17.919 --> 00:17:17.929 align:start position:0% is full of trackers from all kinds and 00:17:17.929 --> 00:17:20.569 align:start position:0% is full of trackers from all kinds and those<00:17:18.929> trackers<00:17:19.230> feeds<00:17:19.679> a<00:17:19.800> multi<00:17:20.280> billion 00:17:20.569 --> 00:17:20.579 align:start position:0% those trackers feeds a multi billion 00:17:20.579 --> 00:17:23.689 align:start position:0% those trackers feeds a multi billion markets<00:17:21.059> taking<00:17:21.900> advantage<00:17:22.350> out<00:17:22.800> of<00:17:22.860> all<00:17:23.520> of 00:17:23.689 --> 00:17:23.699 align:start position:0% markets taking advantage out of all of 00:17:23.699 --> 00:17:27.679 align:start position:0% markets taking advantage out of all of our<00:17:23.880> online<00:17:24.270> habits<00:17:25.220> and<00:17:26.220> once<00:17:27.120> that's<00:17:27.420> our 00:17:27.679 --> 00:17:27.689 align:start position:0% our online habits and once that's our 00:17:27.689 --> 00:17:30.440 align:start position:0% our online habits and once that's our whole<00:17:27.990> setting<00:17:28.380> swarm<00:17:28.820> users<00:17:29.820> will<00:17:30.270> be<00:17:30.300> able 00:17:30.440 --> 00:17:30.450 align:start position:0% whole setting swarm users will be able 00:17:30.450 --> 00:17:32.730 align:start position:0% whole setting swarm users will be able to<00:17:30.810> decide<00:17:31.170> whether<00:17:31.530> or<00:17:31.679> not 00:17:32.730 --> 00:17:32.740 align:start position:0% to decide whether or not 00:17:32.740 --> 00:17:36.770 align:start position:0% to decide whether or not a<00:17:32.830> certain<00:17:33.520> that<00:17:33.730> would<00:17:34.120> have<00:17:34.330> HTTP<00:17:34.990> access 00:17:36.770 --> 00:17:36.780 align:start position:0% a certain that would have HTTP access 00:17:36.780 --> 00:17:39.570 align:start position:0% a certain that would have HTTP access and<00:17:37.780> I'll<00:17:38.290> talk<00:17:38.440> about<00:17:38.470> the<00:17:38.950> blockchain<00:17:39.190> has 00:17:39.570 --> 00:17:39.580 align:start position:0% and I'll talk about the blockchain has 00:17:39.580 --> 00:17:41.850 align:start position:0% and I'll talk about the blockchain has already<00:17:39.820> proven<00:17:40.300> itself<00:17:40.750> secure<00:17:41.230> of<00:17:41.559> course 00:17:41.850 --> 00:17:41.860 align:start position:0% already proven itself secure of course 00:17:41.860 --> 00:17:44.669 align:start position:0% already proven itself secure of course such<00:17:42.730> social<00:17:43.390> engineering<00:17:43.900> and<00:17:44.140> trickery<00:17:44.559> are 00:17:44.669 --> 00:17:44.679 align:start position:0% such social engineering and trickery are 00:17:44.679 --> 00:17:48.060 align:start position:0% such social engineering and trickery are important<00:17:45.460> problems<00:17:45.970> to<00:17:46.210> deal<00:17:46.390> with<00:17:46.540> and<00:17:47.070> we'd 00:17:48.060 --> 00:17:48.070 align:start position:0% important problems to deal with and we'd 00:17:48.070 --> 00:17:49.740 align:start position:0% important problems to deal with and we'd like<00:17:48.250> to<00:17:48.400> invest<00:17:48.730> some<00:17:48.940> time<00:17:48.970> into<00:17:49.420> ant 00:17:49.740 --> 00:17:49.750 align:start position:0% like to invest some time into ant 00:17:49.750 --> 00:17:53.430 align:start position:0% like to invest some time into ant efficient<00:17:50.230> mechanisms<00:17:50.860> and<00:17:51.960> using<00:17:52.960> some<00:17:53.200> sort 00:17:53.430 --> 00:17:53.440 align:start position:0% efficient mechanisms and using some sort 00:17:53.440 --> 00:17:55.620 align:start position:0% efficient mechanisms and using some sort of<00:17:53.620> reputation<00:17:53.890> system<00:17:54.700> or<00:17:54.940> blacklist 00:17:55.620 --> 00:17:55.630 align:start position:0% of reputation system or blacklist 00:17:55.630 --> 00:17:58.200 align:start position:0% of reputation system or blacklist subscriptions<00:17:56.350> that<00:17:56.830> users<00:17:57.280> will<00:17:57.460> be<00:17:57.490> able<00:17:57.640> to 00:17:58.200 --> 00:17:58.210 align:start position:0% subscriptions that users will be able to 00:17:58.210 --> 00:18:04.950 align:start position:0% subscriptions that users will be able to easily<00:17:58.990> manage<00:18:02.190> so<00:18:03.190> yes<00:18:03.580> here<00:18:04.059> at<00:18:04.090> DEFCON<00:18:04.480> 3<00:18:04.720> I 00:18:04.950 --> 00:18:04.960 align:start position:0% easily manage so yes here at DEFCON 3 I 00:18:04.960 --> 00:18:08.400 align:start position:0% easily manage so yes here at DEFCON 3 I present<00:18:05.470> to<00:18:05.620> you<00:18:05.679> some<00:18:05.740> this<00:18:06.640> summary<00:18:07.410> we've 00:18:08.400 --> 00:18:08.410 align:start position:0% present to you some this summary we've 00:18:08.410 --> 00:18:11.100 align:start position:0% present to you some this summary we've got<00:18:08.620> harder<00:18:09.160> than<00:18:09.309> security<00:18:09.910> this<00:18:10.780> is<00:18:10.900> March 00:18:11.100 --> 00:18:11.110 align:start position:0% got harder than security this is March 00:18:11.110 --> 00:18:13.980 align:start position:0% got harder than security this is March or<00:18:11.290> gasps<00:18:11.530> updates<00:18:12.010> we're<00:18:12.910> no<00:18:13.059> longer<00:18:13.480> having 00:18:13.980 --> 00:18:13.990 align:start position:0% or gasps updates we're no longer having 00:18:13.990 --> 00:18:16.770 align:start position:0% or gasps updates we're no longer having to<00:18:14.410> release<00:18:14.740> mists<00:18:15.130> Burson's<00:18:15.730> for<00:18:16.179> each<00:18:16.420> gas 00:18:16.770 --> 00:18:16.780 align:start position:0% to release mists Burson's for each gas 00:18:16.780 --> 00:18:20.750 align:start position:0% to release mists Burson's for each gas update<00:18:17.880> ENS<00:18:18.880> integrations<00:18:19.660> for<00:18:20.110> our<00:18:20.170> better 00:18:20.750 --> 00:18:20.760 align:start position:0% update ENS integrations for our better 00:18:20.760 --> 00:18:25.190 align:start position:0% update ENS integrations for our better delight<00:18:21.760> client<00:18:22.260> remix<00:18:23.260> integration<00:18:24.000> so 00:18:25.190 --> 00:18:25.200 align:start position:0% delight client remix integration so 00:18:25.200 --> 00:18:28.890 align:start position:0% delight client remix integration so there's<00:18:26.200> a<00:18:26.290> key<00:18:26.530> takeaway<00:18:26.710> which<00:18:27.280> is<00:18:27.900> missed 00:18:28.890 --> 00:18:28.900 align:start position:0% there's a key takeaway which is missed 00:18:28.900 --> 00:18:34.740 align:start position:0% there's a key takeaway which is missed is<00:18:29.620> a<00:18:29.679> full<00:18:30.550> browser<00:18:32.610> that<00:18:33.610> makes<00:18:34.059> you<00:18:34.270> run<00:18:34.450> a 00:18:34.740 --> 00:18:34.750 align:start position:0% is a full browser that makes you run a 00:18:34.750 --> 00:18:38.370 align:start position:0% is a full browser that makes you run a full<00:18:35.080> note<00:18:35.580> you<00:18:36.580> can<00:18:37.120> be<00:18:37.270> also<00:18:37.660> a<00:18:37.929> quite<00:18:38.320> a 00:18:38.370 --> 00:18:38.380 align:start position:0% full note you can be also a quite a 00:18:38.380 --> 00:18:42.299 align:start position:0% full note you can be also a quite a light<00:18:38.710> note<00:18:38.950> but<00:18:39.730> the<00:18:39.970> thing<00:18:40.300> is<00:18:41.040> you<00:18:42.040> should 00:18:42.299 --> 00:18:42.309 align:start position:0% light note but the thing is you should 00:18:42.309 --> 00:18:44.730 align:start position:0% light note but the thing is you should for<00:18:42.760> the<00:18:42.790> grid<00:18:43.090> of<00:18:43.210> the<00:18:43.240> ecosystem<00:18:43.929> run<00:18:44.500> euro 00:18:44.730 --> 00:18:44.740 align:start position:0% for the grid of the ecosystem run euro 00:18:44.740 --> 00:18:51.510 align:start position:0% for the grid of the ecosystem run euro note<00:18:47.370> well<00:18:48.370> this<00:18:49.030> is<00:18:49.330> our<00:18:49.750> current<00:18:50.200> team<00:18:50.520> and 00:18:51.510 --> 00:18:51.520 align:start position:0% note well this is our current team and 00:18:51.520 --> 00:18:54.360 align:start position:0% note well this is our current team and we<00:18:51.760> also<00:18:51.910> has<00:18:52.270> some<00:18:52.720> many<00:18:53.620> in<00:18:53.860> doses<00:18:54.220> of 00:18:54.360 --> 00:18:54.370 align:start position:0% we also has some many in doses of 00:18:54.370 --> 00:18:57.600 align:start position:0% we also has some many in doses of contributors<00:18:54.910> so<00:18:55.210> I<00:18:55.450> like<00:18:55.750> to<00:18:56.250> clap<00:18:57.250> a<00:18:57.280> little 00:18:57.600 --> 00:18:57.610 align:start position:0% contributors so I like to clap a little 00:18:57.610 --> 00:19:02.190 align:start position:0% contributors so I like to clap a little bit<00:18:57.730> for<00:18:57.970> them<00:19:00.150> those<00:19:01.150> guys<00:19:01.390> helped<00:19:01.809> us<00:19:01.960> with 00:19:02.190 --> 00:19:02.200 align:start position:0% bit for them those guys helped us with 00:19:02.200 --> 00:19:05.310 align:start position:0% bit for them those guys helped us with translation<00:19:02.980> with<00:19:03.340> many<00:19:03.580> bug<00:19:03.790> fixes<00:19:04.300> and<00:19:04.570> lots 00:19:05.310 --> 00:19:05.320 align:start position:0% translation with many bug fixes and lots 00:19:05.320 --> 00:19:08.310 align:start position:0% translation with many bug fixes and lots of<00:19:05.470> suggestions<00:19:05.890> around<00:19:06.870> and<00:19:07.870> there's<00:19:08.140> one 00:19:08.310 --> 00:19:08.320 align:start position:0% of suggestions around and there's one 00:19:08.320 --> 00:19:10.590 align:start position:0% of suggestions around and there's one more<00:19:08.440> thing<00:19:08.700> remember<00:19:09.700> that<00:19:10.179> I<00:19:10.210> told<00:19:10.390> you 00:19:10.590 --> 00:19:10.600 align:start position:0% more thing remember that I told you 00:19:10.600 --> 00:19:13.049 align:start position:0% more thing remember that I told you about<00:19:10.660> the<00:19:10.960> workshop<00:19:11.380> back<00:19:11.710> in<00:19:11.890> June<00:19:12.130> we 00:19:13.049 --> 00:19:13.059 align:start position:0% about the workshop back in June we 00:19:13.059 --> 00:19:15.000 align:start position:0% about the workshop back in June we working<00:19:13.390> together<00:19:13.510> for<00:19:13.990> that<00:19:14.260> whole<00:19:14.530> week<00:19:14.559> and 00:19:15.000 --> 00:19:15.010 align:start position:0% working together for that whole week and 00:19:15.010 --> 00:19:16.910 align:start position:0% working together for that whole week and discussed<00:19:15.580> about<00:19:15.790> many<00:19:16.120> many<00:19:16.270> things<00:19:16.540> and 00:19:16.910 --> 00:19:16.920 align:start position:0% discussed about many many things and 00:19:16.920 --> 00:19:19.650 align:start position:0% discussed about many many things and Victor<00:19:17.920> Maia<00:19:18.160> kick-started<00:19:19.030> a<00:19:19.150> new<00:19:19.300> track 00:19:19.650 --> 00:19:19.660 align:start position:0% Victor Maia kick-started a new track 00:19:19.660 --> 00:19:22.590 align:start position:0% Victor Maia kick-started a new track within<00:19:20.080> the<00:19:20.290> team<00:19:20.500> so<00:19:21.429> I<00:19:21.460> invite<00:19:21.820> him<00:19:22.059> to<00:19:22.300> stage 00:19:22.590 --> 00:19:22.600 align:start position:0% within the team so I invite him to stage 00:19:22.600 --> 00:19:52.770 align:start position:0% within the team so I invite him to stage to<00:19:22.840> talk<00:19:22.990> about<00:19:23.170> his<00:19:23.980> new<00:19:24.160> project 00:19:52.770 --> 00:19:52.780 align:start position:0% 00:19:52.780 --> 00:19:57.070 align:start position:0% so<00:19:53.780> hello<00:19:54.170> everyone<00:19:55.120> now<00:19:56.120> we<00:19:56.510> are<00:19:56.630> gonna<00:19:56.780> show 00:19:57.070 --> 00:19:57.080 align:start position:0% so hello everyone now we are gonna show 00:19:57.080 --> 00:20:02.430 align:start position:0% so hello everyone now we are gonna show you<00:19:57.140> show<00:19:57.890> you<00:19:57.950> something<00:19:58.580> new<00:19:58.870> so<00:19:59.870> already<00:20:01.420> I 00:20:02.430 --> 00:20:02.440 align:start position:0% you show you something new so already I 00:20:02.440 --> 00:20:05.530 align:start position:0% you show you something new so already I think<00:20:03.440> everyone<00:20:04.160> here<00:20:04.370> dreams<00:20:04.730> about 00:20:05.530 --> 00:20:05.540 align:start position:0% think everyone here dreams about 00:20:05.540 --> 00:20:07.800 align:start position:0% think everyone here dreams about centralized<00:20:06.020> well<00:20:06.320> our<00:20:07.160> world<00:20:07.430> of<00:20:07.520> abundance 00:20:07.800 --> 00:20:07.810 align:start position:0% centralized well our world of abundance 00:20:07.810 --> 00:20:11.140 align:start position:0% centralized well our world of abundance there<00:20:08.810> are<00:20:08.930> no<00:20:09.110> companies<00:20:09.620> where<00:20:10.310> nobody<00:20:10.850> owns 00:20:11.140 --> 00:20:11.150 align:start position:0% there are no companies where nobody owns 00:20:11.150 --> 00:20:13.720 align:start position:0% there are no companies where nobody owns anything<00:20:11.630> there<00:20:12.530> are<00:20:12.680> just<00:20:12.950> public<00:20:13.430> adapts 00:20:13.720 --> 00:20:13.730 align:start position:0% anything there are just public adapts 00:20:13.730 --> 00:20:17.500 align:start position:0% anything there are just public adapts and<00:20:14.060> the<00:20:14.780> house<00:20:14.990> that<00:20:15.410> are<00:20:15.820> easily 00:20:17.500 --> 00:20:17.510 align:start position:0% and the house that are easily 00:20:17.510 --> 00:20:20.920 align:start position:0% and the house that are easily resilient<00:20:18.470> and<00:20:18.860> free<00:20:19.330> can<00:20:20.330> you<00:20:20.450> imagine<00:20:20.690> that 00:20:20.920 --> 00:20:20.930 align:start position:0% resilient and free can you imagine that 00:20:20.930 --> 00:20:24.550 align:start position:0% resilient and free can you imagine that word<00:20:22.090> well<00:20:23.090> of<00:20:23.330> course<00:20:23.360> you<00:20:23.660> can<00:20:23.870> if<00:20:24.080> you<00:20:24.320> is 00:20:24.550 --> 00:20:24.560 align:start position:0% word well of course you can if you is 00:20:24.560 --> 00:20:29.050 align:start position:0% word well of course you can if you is that<00:20:24.770> thing<00:20:25.100> but<00:20:25.990> for<00:20:26.990> backyard<00:20:27.470> services<00:20:28.060> so 00:20:29.050 --> 00:20:29.060 align:start position:0% that thing but for backyard services so 00:20:29.060 --> 00:20:31.420 align:start position:0% that thing but for backyard services so what<00:20:29.570> about<00:20:29.660> the<00:20:29.900> front<00:20:30.140> end<00:20:30.320> what<00:20:31.190> about 00:20:31.420 --> 00:20:31.430 align:start position:0% what about the front end what about 00:20:31.430 --> 00:20:34.690 align:start position:0% what about the front end what about using<00:20:31.760> the<00:20:32.090> face<00:20:32.530> well<00:20:33.530> it<00:20:33.890> has<00:20:34.040> been<00:20:34.250> 2<00:20:34.490> years 00:20:34.690 --> 00:20:34.700 align:start position:0% using the face well it has been 2 years 00:20:34.700 --> 00:20:37.480 align:start position:0% using the face well it has been 2 years since<00:20:34.850> your<00:20:35.150> launch<00:20:35.450> and<00:20:35.750> yet<00:20:36.380> most<00:20:36.830> laps<00:20:37.190> are 00:20:37.480 --> 00:20:37.490 align:start position:0% since your launch and yet most laps are 00:20:37.490 --> 00:20:40.480 align:start position:0% since your launch and yet most laps are Stooges<00:20:38.440> centralized<00:20:39.440> companies<00:20:40.160> with 00:20:40.480 --> 00:20:40.490 align:start position:0% Stooges centralized companies with 00:20:40.490 --> 00:20:43.510 align:start position:0% Stooges centralized companies with tokens<00:20:40.900> they<00:20:41.900> are<00:20:42.080> hosted<00:20:42.860> on<00:20:43.010> central 00:20:43.510 --> 00:20:43.520 align:start position:0% tokens they are hosted on central 00:20:43.520 --> 00:20:47.200 align:start position:0% tokens they are hosted on central computer<00:20:44.060> they<00:20:44.720> use<00:20:44.900> centralized<00:20:45.470> api's<00:20:46.210> so 00:20:47.200 --> 00:20:47.210 align:start position:0% computer they use centralized api's so 00:20:47.210 --> 00:20:50.290 align:start position:0% computer they use centralized api's so where's<00:20:47.780> the<00:20:48.020> decentralized<00:20:48.380> web<00:20:48.910> why<00:20:49.910> it's 00:20:50.290 --> 00:20:50.300 align:start position:0% where's the decentralized web why it's 00:20:50.300 --> 00:20:57.570 align:start position:0% where's the decentralized web why it's not<00:20:50.570> happening<00:20:52.030> let's<00:20:53.030> talk<00:20:53.240> about<00:20:53.390> mist<00:20:55.780> what 00:20:57.570 --> 00:20:57.580 align:start position:0% not happening let's talk about mist what 00:20:57.580 --> 00:21:01.660 align:start position:0% not happening let's talk about mist what this<00:20:58.580> is<00:20:58.940> our<00:20:59.300> code<00:20:59.800> as<00:21:00.800> you<00:21:00.980> know<00:21:01.130> it's<00:21:01.370> not<00:21:01.520> in 00:21:01.660 --> 00:21:01.670 align:start position:0% this is our code as you know it's not in 00:21:01.670 --> 00:21:04.120 align:start position:0% this is our code as you know it's not in a<00:21:01.730> great<00:21:01.940> state<00:21:02.150> now<00:21:02.420> right<00:21:02.780> now<00:21:02.930> miss<00:21:03.770> little 00:21:04.120 --> 00:21:04.130 align:start position:0% a great state now right now miss little 00:21:04.130 --> 00:21:06.490 align:start position:0% a great state now right now miss little a<00:21:04.340> little<00:21:04.460> bit<00:21:04.670> slow<00:21:04.970> it<00:21:05.360> has<00:21:05.630> some<00:21:05.900> bugs 00:21:06.490 --> 00:21:06.500 align:start position:0% a little bit slow it has some bugs 00:21:06.500 --> 00:21:08.920 align:start position:0% a little bit slow it has some bugs of<00:21:07.310> course<00:21:07.610> you're<00:21:07.790> working<00:21:08.030> to<00:21:08.330> prove<00:21:08.570> it<00:21:08.750> and 00:21:08.920 --> 00:21:08.930 align:start position:0% of course you're working to prove it and 00:21:08.930 --> 00:21:10.690 align:start position:0% of course you're working to prove it and we<00:21:09.410> believe<00:21:09.650> you<00:21:09.740> can<00:21:09.890> make<00:21:09.920> it<00:21:10.160> much<00:21:10.430> much 00:21:10.690 --> 00:21:10.700 align:start position:0% we believe you can make it much much 00:21:10.700 --> 00:21:13.360 align:start position:0% we believe you can make it much much better<00:21:10.970> now<00:21:11.360> with<00:21:11.420> Mark<00:21:11.840> on<00:21:12.050> our<00:21:12.200> team<00:21:12.440> but 00:21:13.360 --> 00:21:13.370 align:start position:0% better now with Mark on our team but 00:21:13.370 --> 00:21:15.700 align:start position:0% better now with Mark on our team but even<00:21:14.060> if<00:21:14.180> you<00:21:14.270> miss<00:21:14.480> himself<00:21:14.990> was<00:21:15.230> perfect 00:21:15.700 --> 00:21:15.710 align:start position:0% even if you miss himself was perfect 00:21:15.710 --> 00:21:18.910 align:start position:0% even if you miss himself was perfect even<00:21:16.400> if<00:21:16.520> that<00:21:16.730> thing<00:21:17.180> was<00:21:17.540> flawless<00:21:17.920> would 00:21:18.910 --> 00:21:18.920 align:start position:0% even if that thing was flawless would 00:21:18.920 --> 00:21:23.310 align:start position:0% even if that thing was flawless would that<00:21:19.160> be<00:21:19.400> enough<00:21:20.050> well<00:21:21.050> what<00:21:21.680> about<00:21:21.770> those 00:21:23.310 --> 00:21:23.320 align:start position:0% that be enough well what about those 00:21:23.320 --> 00:21:26.080 align:start position:0% that be enough well what about those browsers<00:21:24.320> like<00:21:24.650> Miss<00:21:24.860> depend<00:21:25.460> on<00:21:25.550> a<00:21:25.640> huge<00:21:25.880> web 00:21:26.080 --> 00:21:26.090 align:start position:0% browsers like Miss depend on a huge web 00:21:26.090 --> 00:21:28.810 align:start position:0% browsers like Miss depend on a huge web stack<00:21:26.390> there<00:21:27.320> are<00:21:27.470> millions<00:21:28.010> of<00:21:28.220> lines<00:21:28.550> of 00:21:28.810 --> 00:21:28.820 align:start position:0% stack there are millions of lines of 00:21:28.820 --> 00:21:32.140 align:start position:0% stack there are millions of lines of code<00:21:29.120> that<00:21:29.780> we<00:21:30.080> do<00:21:30.230> not<00:21:30.410> control<00:21:30.950> and<00:21:31.340> you 00:21:32.140 --> 00:21:32.150 align:start position:0% code that we do not control and you 00:21:32.150 --> 00:21:34.240 align:start position:0% code that we do not control and you already<00:21:32.540> had<00:21:32.660> two<00:21:33.020> major<00:21:33.320> vulnerabilities 00:21:34.240 --> 00:21:34.250 align:start position:0% already had two major vulnerabilities 00:21:34.250 --> 00:21:37.600 align:start position:0% already had two major vulnerabilities because<00:21:35.060> of<00:21:35.270> those<00:21:35.480> things<00:21:35.980> so<00:21:36.980> the<00:21:37.280> point<00:21:37.520> is 00:21:37.600 --> 00:21:37.610 align:start position:0% because of those things so the point is 00:21:37.610 --> 00:21:39.310 align:start position:0% because of those things so the point is how<00:21:38.360> can<00:21:38.750> we 00:21:39.310 --> 00:21:39.320 align:start position:0% how can we 00:21:39.320 --> 00:21:42.910 align:start position:0% how can we those<00:21:39.770> things<00:21:40.190> should<00:21:40.700> be<00:21:40.790> secured<00:21:41.680> well<00:21:42.680> we 00:21:42.910 --> 00:21:42.920 align:start position:0% those things should be secured well we 00:21:42.920 --> 00:21:45.340 align:start position:0% those things should be secured well we can't<00:21:43.160> and<00:21:43.580> that's<00:21:44.210> a<00:21:44.360> serious<00:21:44.690> problem<00:21:44.930> for<00:21:45.080> a 00:21:45.340 --> 00:21:45.350 align:start position:0% can't and that's a serious problem for a 00:21:45.350 --> 00:21:48.190 align:start position:0% can't and that's a serious problem for a browser<00:21:45.650> that<00:21:46.190> deals<00:21:46.610> with<00:21:46.700> real<00:21:47.060> money<00:21:47.300> don't 00:21:48.190 --> 00:21:48.200 align:start position:0% browser that deals with real money don't 00:21:48.200 --> 00:21:51.490 align:start position:0% browser that deals with real money don't you<00:21:48.290> think<00:21:48.700> so<00:21:49.700> and<00:21:50.270> even<00:21:50.570> if<00:21:50.840> that<00:21:51.050> was<00:21:51.290> not 00:21:51.490 --> 00:21:51.500 align:start position:0% you think so and even if that was not 00:21:51.500 --> 00:21:53.680 align:start position:0% you think so and even if that was not the<00:21:51.560> case<00:21:51.890> if<00:21:52.190> those<00:21:52.700> things<00:21:53.060> were<00:21:53.390> perfect 00:21:53.680 --> 00:21:53.690 align:start position:0% the case if those things were perfect 00:21:53.690 --> 00:21:58.630 align:start position:0% the case if those things were perfect what<00:21:54.530> about<00:21:54.800> those<00:21:55.520> things<00:21:55.850> above<00:21:57.040> well<00:21:58.040> let's 00:21:58.630 --> 00:21:58.640 align:start position:0% what about those things above well let's 00:21:58.640 --> 00:22:05.380 align:start position:0% what about those things above well let's talk<00:21:58.880> about<00:21:59.060> JavaScript<00:22:03.910> okay<00:22:04.910> sorry<00:22:05.210> I<00:22:05.270> think 00:22:05.380 --> 00:22:05.390 align:start position:0% talk about JavaScript okay sorry I think 00:22:05.390 --> 00:22:06.970 align:start position:0% talk about JavaScript okay sorry I think I<00:22:05.510> have<00:22:05.540> some<00:22:05.900> problem<00:22:06.260> with<00:22:06.290> this<00:22:06.560> controller 00:22:06.970 --> 00:22:06.980 align:start position:0% I have some problem with this controller 00:22:06.980 --> 00:22:11.650 align:start position:0% I have some problem with this controller so<00:22:07.700> would<00:22:08.150> use<00:22:08.420> that<00:22:08.660> code<00:22:08.960> on<00:22:09.290> your<00:22:09.350> that<00:22:10.660> no 00:22:11.650 --> 00:22:11.660 align:start position:0% so would use that code on your that no 00:22:11.660 --> 00:22:13.540 align:start position:0% so would use that code on your that no really<00:22:11.900> think<00:22:12.050> about<00:22:12.110> it<00:22:12.470> is<00:22:12.800> it<00:22:13.040> safe<00:22:13.280> to<00:22:13.520> use 00:22:13.540 --> 00:22:13.550 align:start position:0% really think about it is it safe to use 00:22:13.550 --> 00:22:16.840 align:start position:0% really think about it is it safe to use that<00:22:13.820> finger<00:22:14.060> and<00:22:14.180> that<00:22:15.250> well<00:22:16.250> of<00:22:16.430> course<00:22:16.490> it 00:22:16.840 --> 00:22:16.850 align:start position:0% that finger and that well of course it 00:22:16.850 --> 00:22:18.550 align:start position:0% that finger and that well of course it is<00:22:16.970> it's<00:22:17.240> just<00:22:17.330> a<00:22:17.540> pure<00:22:17.720> function<00:22:17.930> it's<00:22:18.320> as 00:22:18.550 --> 00:22:18.560 align:start position:0% is it's just a pure function it's as 00:22:18.560 --> 00:22:19.570 align:start position:0% is it's just a pure function it's as simple<00:22:18.740> as<00:22:18.950> it<00:22:19.100> gets 00:22:19.570 --> 00:22:19.580 align:start position:0% simple as it gets 00:22:19.580 --> 00:22:21.840 align:start position:0% simple as it gets there<00:22:19.910> is<00:22:20.000> nothing<00:22:20.150> potential<00:22:20.750> safe<00:22:20.990> about<00:22:21.290> it 00:22:21.840 --> 00:22:21.850 align:start position:0% there is nothing potential safe about it 00:22:21.850 --> 00:22:23.980 align:start position:0% there is nothing potential safe about it so<00:22:22.850> what<00:22:23.150> about<00:22:23.240> this<00:22:23.540> one 00:22:23.980 --> 00:22:23.990 align:start position:0% so what about this one 00:22:23.990 --> 00:22:27.840 align:start position:0% so what about this one would<00:22:24.470> you<00:22:24.590> use<00:22:24.800> that<00:22:25.070> thing<00:22:25.370> on<00:22:25.760> your<00:22:25.940> deck 00:22:27.840 --> 00:22:27.850 align:start position:0% would you use that thing on your deck 00:22:27.850 --> 00:22:31.540 align:start position:0% would you use that thing on your deck well<00:22:28.850> of<00:22:29.120> course<00:22:29.180> you<00:22:29.630> do<00:22:30.080> not<00:22:30.320> I<00:22:30.650> hope<00:22:31.220> you<00:22:31.370> I 00:22:31.540 --> 00:22:31.550 align:start position:0% well of course you do not I hope you I 00:22:31.550 --> 00:22:33.640 align:start position:0% well of course you do not I hope you I hope<00:22:31.580> you<00:22:31.940> not<00:22:32.210> I<00:22:32.480> mean<00:22:32.900> you<00:22:33.050> don't<00:22:33.260> know<00:22:33.470> what 00:22:33.640 --> 00:22:33.650 align:start position:0% hope you not I mean you don't know what 00:22:33.650 --> 00:22:36.220 align:start position:0% hope you not I mean you don't know what square<00:22:33.920> that<00:22:34.070> is<00:22:34.310> does<00:22:34.700> it<00:22:35.300> could<00:22:35.630> do<00:22:35.720> anything 00:22:36.220 --> 00:22:36.230 align:start position:0% square that is does it could do anything 00:22:36.230 --> 00:22:39.850 align:start position:0% square that is does it could do anything for<00:22:36.800> example<00:22:37.510> this<00:22:38.510> is<00:22:38.930> a<00:22:39.170> very<00:22:39.320> implemented 00:22:39.850 --> 00:22:39.860 align:start position:0% for example this is a very implemented 00:22:39.860 --> 00:22:42.670 align:start position:0% for example this is a very implemented it's<00:22:40.580> correct<00:22:41.060> but<00:22:41.870> there<00:22:42.260> is<00:22:42.350> something 00:22:42.670 --> 00:22:42.680 align:start position:0% it's correct but there is something 00:22:42.680 --> 00:22:46.000 align:start position:0% it's correct but there is something extra<00:22:43.130> it<00:22:43.910> also<00:22:44.420> alters<00:22:44.990> the<00:22:45.290> global<00:22:45.650> r3 00:22:46.000 --> 00:22:46.010 align:start position:0% extra it also alters the global r3 00:22:46.010 --> 00:22:50.320 align:start position:0% extra it also alters the global r3 object<00:22:46.490> so<00:22:48.400> this<00:22:49.400> isn't<00:22:49.490> like<00:22:49.730> it<00:22:50.030> it's<00:22:50.180> not 00:22:50.320 --> 00:22:50.330 align:start position:0% object so this isn't like it it's not 00:22:50.330 --> 00:22:52.120 align:start position:0% object so this isn't like it it's not who<00:22:50.600> this<00:22:50.900> is<00:22:51.020> the<00:22:51.230> kind<00:22:51.440> of<00:22:51.860> you<00:22:51.890> can 00:22:52.120 --> 00:22:52.130 align:start position:0% who this is the kind of you can 00:22:52.130 --> 00:22:55.720 align:start position:0% who this is the kind of you can do<00:22:52.250> in<00:22:52.340> JavaScript<00:22:53.200> so<00:22:54.280> by<00:22:55.280> the<00:22:55.340> way<00:22:55.460> it's<00:22:55.670> not 00:22:55.720 --> 00:22:55.730 align:start position:0% do in JavaScript so by the way it's not 00:22:55.730 --> 00:22:58.570 align:start position:0% do in JavaScript so by the way it's not only<00:22:55.850> about<00:22:56.240> practice<00:22:57.190> hacking<00:22:58.190> the<00:22:58.280> global 00:22:58.570 --> 00:22:58.580 align:start position:0% only about practice hacking the global 00:22:58.580 --> 00:23:00.580 align:start position:0% only about practice hacking the global scope<00:22:58.760> of<00:22:58.940> adapt<00:22:59.210> can<00:22:59.510> cause<00:22:59.720> it<00:22:59.990> to<00:23:00.020> for 00:23:00.580 --> 00:23:00.590 align:start position:0% scope of adapt can cause it to for 00:23:00.590 --> 00:23:03.580 align:start position:0% scope of adapt can cause it to for example<00:23:01.100> show<00:23:02.060> me<00:23:02.120> is<00:23:02.240> listening<00:23:02.630> for<00:23:02.930> track 00:23:03.580 --> 00:23:03.590 align:start position:0% example show me is listening for track 00:23:03.590 --> 00:23:06.280 align:start position:0% example show me is listening for track user<00:23:03.920> actions<00:23:04.400> mine<00:23:05.060> cryptocurrencies<00:23:05.750> on 00:23:06.280 --> 00:23:06.290 align:start position:0% user actions mine cryptocurrencies on 00:23:06.290 --> 00:23:09.310 align:start position:0% user actions mine cryptocurrencies on your<00:23:06.530> computer<00:23:07.070> so<00:23:07.940> here's<00:23:08.330> a<00:23:08.450> lesson<00:23:08.840> you 00:23:09.310 --> 00:23:09.320 align:start position:0% your computer so here's a lesson you 00:23:09.320 --> 00:23:11.950 align:start position:0% your computer so here's a lesson you should<00:23:09.560> never<00:23:09.740> import<00:23:10.400> jeaious<00:23:10.910> code<00:23:11.210> you<00:23:11.750> did 00:23:11.950 --> 00:23:11.960 align:start position:0% should never import jeaious code you did 00:23:11.960 --> 00:23:23.970 align:start position:0% should never import jeaious code you did not<00:23:12.170> read<00:23:12.440> it's<00:23:13.070> not<00:23:13.340> safe<00:23:14.710> but<00:23:15.710> oh<00:23:16.810> my<00:23:17.810> god 00:23:23.970 --> 00:23:23.980 align:start position:0% 00:23:23.980 --> 00:23:27.630 align:start position:0% something<00:23:24.980> okay<00:23:25.970> if<00:23:26.330> I<00:23:26.450> just<00:23:26.660> use<00:23:26.870> the<00:23:27.080> arrows 00:23:27.630 --> 00:23:27.640 align:start position:0% something okay if I just use the arrows 00:23:27.640 --> 00:23:30.610 align:start position:0% something okay if I just use the arrows but<00:23:28.640> do<00:23:28.760> we<00:23:28.850> know<00:23:29.000> that<00:23:29.030> that<00:23:29.450> D<00:23:29.840> lives<00:23:30.200> with 00:23:30.610 --> 00:23:30.620 align:start position:0% but do we know that that D lives with 00:23:30.620 --> 00:23:33.100 align:start position:0% but do we know that that D lives with all<00:23:30.830> the<00:23:31.100> reports<00:23:31.550> like<00:23:32.420> this<00:23:32.600> is<00:23:32.690> not<00:23:32.840> a<00:23:32.870> real 00:23:33.100 --> 00:23:33.110 align:start position:0% all the reports like this is not a real 00:23:33.110 --> 00:23:35.530 align:start position:0% all the reports like this is not a real problem<00:23:33.260> because<00:23:33.560> that<00:23:34.400> devs<00:23:34.670> are<00:23:34.910> doing<00:23:35.300> all 00:23:35.530 --> 00:23:35.540 align:start position:0% problem because that devs are doing all 00:23:35.540 --> 00:23:38.860 align:start position:0% problem because that devs are doing all that<00:23:35.750> audit<00:23:36.230> work<00:23:36.440> by<00:23:36.950> themselves<00:23:37.100> right<00:23:37.870> so 00:23:38.860 --> 00:23:38.870 align:start position:0% that audit work by themselves right so 00:23:38.870 --> 00:23:41.280 align:start position:0% that audit work by themselves right so let<00:23:39.170> me<00:23:39.290> show<00:23:39.410> something 00:23:41.280 --> 00:23:41.290 align:start position:0% let me show something 00:23:41.290 --> 00:23:43.660 align:start position:0% let me show something these<00:23:42.290> are<00:23:42.500> least<00:23:42.710> refer<00:23:43.070> to<00:23:43.280> that<00:23:43.400> as 00:23:43.660 --> 00:23:43.670 align:start position:0% these are least refer to that as 00:23:43.670 --> 00:23:48.370 align:start position:0% these are least refer to that as dependencies<00:23:46.180> each<00:23:47.180> one<00:23:47.450> of<00:23:47.600> those<00:23:47.750> lines<00:23:48.020> is 00:23:48.370 --> 00:23:48.380 align:start position:0% dependencies each one of those lines is 00:23:48.380 --> 00:23:50.290 align:start position:0% dependencies each one of those lines is an<00:23:48.560> intern<00:23:49.010> pocket<00:23:49.370> with<00:23:49.670> a<00:23:49.790> lot<00:23:49.940> of<00:23:49.970> files 00:23:50.290 --> 00:23:50.300 align:start position:0% an intern pocket with a lot of files 00:23:50.300 --> 00:23:52.560 align:start position:0% an intern pocket with a lot of files perhaps<00:23:50.810> hundreds<00:23:51.230> of<00:23:51.380> lines<00:23:51.620> of<00:23:51.770> code 00:23:52.560 --> 00:23:52.570 align:start position:0% perhaps hundreds of lines of code 00:23:52.570 --> 00:23:59.959 align:start position:0% perhaps hundreds of lines of code this<00:23:53.049> is<00:23:53.109> the<00:23:53.199> first<00:23:53.469> is<00:23:53.979> the<00:23:54.159> second<00:23:54.609> return 00:23:59.959 --> 00:23:59.969 align:start position:0% 00:23:59.969 --> 00:24:04.789 align:start position:0% all<00:24:00.969> those<00:24:01.299> are<00:24:01.919> but<00:24:02.919> that<00:24:03.279> just<00:24:03.459> depends<00:24:03.879> and 00:24:04.789 --> 00:24:04.799 align:start position:0% all those are but that just depends and 00:24:04.799 --> 00:24:08.399 align:start position:0% all those are but that just depends and my<00:24:05.799> question<00:24:06.190> is<00:24:06.690> have<00:24:07.690> you<00:24:07.719> depth<00:24:08.139> depth 00:24:08.399 --> 00:24:08.409 align:start position:0% my question is have you depth depth 00:24:08.409 --> 00:24:12.569 align:start position:0% my question is have you depth depth around<00:24:08.829> here<00:24:09.070> read<00:24:09.820> all<00:24:10.029> of<00:24:10.089> them<00:24:11.159> and<00:24:12.159> of<00:24:12.339> them 00:24:12.569 --> 00:24:12.579 align:start position:0% around here read all of them and of them 00:24:12.579 --> 00:24:14.069 align:start position:0% around here read all of them and of them hood<00:24:12.879> behind<00:24:13.239> in<00:24:13.359> something<00:24:13.749> like<00:24:13.929> this 00:24:14.069 --> 00:24:14.079 align:start position:0% hood behind in something like this 00:24:14.079 --> 00:24:19.769 align:start position:0% hood behind in something like this anywhere<00:24:17.190> so<00:24:18.190> the<00:24:18.669> point<00:24:18.940> I<00:24:18.999> tried<00:24:19.239> to<00:24:19.269> make<00:24:19.389> is 00:24:19.769 --> 00:24:19.779 align:start position:0% anywhere so the point I tried to make is 00:24:19.779 --> 00:24:22.439 align:start position:0% anywhere so the point I tried to make is for<00:24:20.679> that<00:24:20.889> and<00:24:21.159> many<00:24:21.459> other<00:24:21.639> reasons<00:24:21.789> that<00:24:22.389> I 00:24:22.439 --> 00:24:22.449 align:start position:0% for that and many other reasons that I 00:24:22.449 --> 00:24:24.689 align:start position:0% for that and many other reasons that I don't<00:24:22.690> have<00:24:22.869> the<00:24:23.049> time<00:24:23.259> to<00:24:23.320> explain<00:24:23.799> the<00:24:24.459> web 00:24:24.689 --> 00:24:24.699 align:start position:0% don't have the time to explain the web 00:24:24.699 --> 00:24:27.689 align:start position:0% don't have the time to explain the web as<00:24:25.089> we<00:24:25.509> know<00:24:25.539> it<00:24:25.869> was<00:24:26.289> not<00:24:26.529> made<00:24:26.769> and<00:24:27.069> not<00:24:27.459> very 00:24:27.689 --> 00:24:27.699 align:start position:0% as we know it was not made and not very 00:24:27.699 --> 00:24:30.389 align:start position:0% as we know it was not made and not very for<00:24:27.969> crypto<00:24:28.359> so<00:24:29.229> what<00:24:29.619> he<00:24:29.739> needs<00:24:29.919> not<00:24:30.099> another 00:24:30.389 --> 00:24:30.399 align:start position:0% for crypto so what he needs not another 00:24:30.399 --> 00:24:33.029 align:start position:0% for crypto so what he needs not another web<00:24:30.609> browser<00:24:30.639> but<00:24:31.509> a<00:24:31.569> brand<00:24:31.869> new<00:24:32.019> thing<00:24:32.049> made 00:24:33.029 --> 00:24:33.039 align:start position:0% web browser but a brand new thing made 00:24:33.039 --> 00:24:37.319 align:start position:0% web browser but a brand new thing made from<00:24:33.429> scratch<00:24:33.759> for<00:24:34.329> etc<00:24:34.809> as<00:24:34.899> well<00:24:35.969> we<00:24:36.969> need<00:24:37.089> an 00:24:37.319 --> 00:24:37.329 align:start position:0% from scratch for etc as well we need an 00:24:37.329 --> 00:24:39.749 align:start position:0% from scratch for etc as well we need an answer<00:24:37.599> to<00:24:37.989> the<00:24:38.109> question<00:24:38.559> how<00:24:39.129> would<00:24:39.399> the<00:24:39.549> web 00:24:39.749 --> 00:24:39.759 align:start position:0% answer to the question how would the web 00:24:39.759 --> 00:24:44.009 align:start position:0% answer to the question how would the web look<00:24:39.999> like<00:24:40.269> if<00:24:40.929> it<00:24:41.169> came<00:24:41.469> after<00:24:41.739> a<00:24:42.099> few<00:24:42.399> and<00:24:43.019> to 00:24:44.009 --> 00:24:44.019 align:start position:0% look like if it came after a few and to 00:24:44.019 --> 00:24:49.289 align:start position:0% look like if it came after a few and to answer<00:24:44.289> that<00:24:44.469> question<00:24:45.009> we<00:24:45.489> started<00:24:46.299> the<00:24:48.299> moon 00:24:49.289 --> 00:24:49.299 align:start position:0% answer that question we started the moon 00:24:49.299 --> 00:24:56.860 align:start position:0% answer that question we started the moon project 00:24:56.860 --> 00:24:56.870 align:start position:0% 00:24:56.870 --> 00:25:00.879 align:start position:0% thank<00:24:57.620> you<00:24:57.710> so<00:24:57.860> much<00:24:58.279> so<00:24:58.720> this<00:24:59.720> is<00:25:00.350> not<00:25:00.679> another 00:25:00.879 --> 00:25:00.889 align:start position:0% thank you so much so this is not another 00:25:00.889 --> 00:25:03.970 align:start position:0% thank you so much so this is not another web<00:25:01.129> browser<00:25:01.399> but<00:25:02.269> an<00:25:02.659> actual<00:25:02.990> decentralized 00:25:03.970 --> 00:25:03.980 align:start position:0% web browser but an actual decentralized 00:25:03.980 --> 00:25:06.669 align:start position:0% web browser but an actual decentralized app<00:25:04.309> engine<00:25:04.850> that<00:25:05.570> is<00:25:05.899> lightweight<00:25:06.409> and 00:25:06.669 --> 00:25:06.679 align:start position:0% app engine that is lightweight and 00:25:06.679 --> 00:25:09.879 align:start position:0% app engine that is lightweight and performant<00:25:08.350> uses<00:25:09.350> the<00:25:09.470> scripting<00:25:09.860> language 00:25:09.879 --> 00:25:09.889 align:start position:0% performant uses the scripting language 00:25:09.889 --> 00:25:12.460 align:start position:0% performant uses the scripting language with<00:25:10.429> Safe<00:25:10.639> Mode<00:25:10.669> alert<00:25:11.120> so<00:25:11.749> people<00:25:12.110> can<00:25:12.230> share 00:25:12.460 --> 00:25:12.470 align:start position:0% with Safe Mode alert so people can share 00:25:12.470 --> 00:25:15.220 align:start position:0% with Safe Mode alert so people can share code<00:25:12.830> without<00:25:13.159> needing<00:25:13.909> to<00:25:14.090> audit<00:25:14.659> everything 00:25:15.220 --> 00:25:15.230 align:start position:0% code without needing to audit everything 00:25:15.230 --> 00:25:17.049 align:start position:0% code without needing to audit everything and<00:25:15.830> that<00:25:16.159> language<00:25:16.340> is<00:25:16.490> kind<00:25:16.820> of<00:25:16.879> like 00:25:17.049 --> 00:25:17.059 align:start position:0% and that language is kind of like 00:25:17.059 --> 00:25:20.980 align:start position:0% and that language is kind of like JavaScript<00:25:17.779> but<00:25:18.169> without<00:25:18.649> the<00:25:18.889> bad<00:25:19.249> things<00:25:19.990> is 00:25:20.980 --> 00:25:20.990 align:start position:0% JavaScript but without the bad things is 00:25:20.990 --> 00:25:23.289 align:start position:0% JavaScript but without the bad things is Manoff<00:25:21.710> to<00:25:21.950> be<00:25:22.070> formally<00:25:22.460> prove<00:25:22.610> insecure<00:25:23.059> and 00:25:23.289 --> 00:25:23.299 align:start position:0% Manoff to be formally prove insecure and 00:25:23.299 --> 00:25:25.869 align:start position:0% Manoff to be formally prove insecure and if<00:25:23.929> those<00:25:24.230> words<00:25:24.559> sound<00:25:24.889> a<00:25:25.129> little<00:25:25.370> bit<00:25:25.490> scary 00:25:25.869 --> 00:25:25.879 align:start position:0% if those words sound a little bit scary 00:25:25.879 --> 00:25:28.239 align:start position:0% if those words sound a little bit scary and<00:25:26.389> that<00:25:26.749> just<00:25:27.019> means<00:25:27.200> a<00:25:27.379> computer<00:25:27.799> not<00:25:28.190> a 00:25:28.239 --> 00:25:28.249 align:start position:0% and that just means a computer not a 00:25:28.249 --> 00:25:30.820 align:start position:0% and that just means a computer not a human<00:25:28.730> can<00:25:29.240> verify<00:25:29.690> that<00:25:30.049> the<00:25:30.350> whole<00:25:30.529> thing 00:25:30.820 --> 00:25:30.830 align:start position:0% human can verify that the whole thing 00:25:30.830 --> 00:25:33.100 align:start position:0% human can verify that the whole thing does<00:25:31.190> not<00:25:31.399> have<00:25:31.610> a<00:25:31.639> single<00:25:31.970> vulnerability<00:25:32.840> and 00:25:33.100 --> 00:25:33.110 align:start position:0% does not have a single vulnerability and 00:25:33.110 --> 00:25:35.399 align:start position:0% does not have a single vulnerability and that's<00:25:33.710> kind<00:25:33.950> of<00:25:34.009> big<00:25:34.159> deal 00:25:35.399 --> 00:25:35.409 align:start position:0% that's kind of big deal 00:25:35.409 --> 00:25:42.450 align:start position:0% that's kind of big deal so<00:25:36.409> in<00:25:36.649> short<00:25:36.679> oh<00:25:37.899> sorry 00:25:42.450 --> 00:25:42.460 align:start position:0% 00:25:42.460 --> 00:25:48.129 align:start position:0% so<00:25:43.460> in<00:25:43.549> short<00:25:43.730> this<00:25:44.210> is<00:25:44.509> very<00:25:44.749> heavy<00:25:45.999> and<00:25:47.139> this 00:25:48.129 --> 00:25:48.139 align:start position:0% so in short this is very heavy and this 00:25:48.139 --> 00:25:59.609 align:start position:0% so in short this is very heavy and this is<00:25:48.499> very<00:25:49.100> building<00:25:57.309> by<00:25:58.309> the<00:25:58.369> way<00:25:58.580> I'd<00:25:58.820> love<00:25:59.210> to 00:25:59.609 --> 00:25:59.619 align:start position:0% is very building by the way I'd love to 00:25:59.619 --> 00:26:01.720 align:start position:0% is very building by the way I'd love to elaborate<00:26:00.619> on<00:26:00.679> how<00:26:01.039> those<00:26:01.249> things<00:26:01.549> are 00:26:01.720 --> 00:26:01.730 align:start position:0% elaborate on how those things are 00:26:01.730 --> 00:26:04.149 align:start position:0% elaborate on how those things are possible<00:26:01.970> but<00:26:02.779> sadly<00:26:03.019> I<00:26:03.350> don't<00:26:03.590> have<00:26:03.799> the<00:26:03.980> time 00:26:04.149 --> 00:26:04.159 align:start position:0% possible but sadly I don't have the time 00:26:04.159 --> 00:26:05.230 align:start position:0% possible but sadly I don't have the time for<00:26:04.190> that<00:26:04.399> right<00:26:04.879> now 00:26:05.230 --> 00:26:05.240 align:start position:0% for that right now 00:26:05.240 --> 00:26:07.930 align:start position:0% for that right now so<00:26:06.019> sorry<00:26:06.649> yeah<00:26:07.039> it'll<00:26:07.190> be<00:26:07.309> for<00:26:07.490> another<00:26:07.580> day 00:26:07.930 --> 00:26:07.940 align:start position:0% so sorry yeah it'll be for another day 00:26:07.940 --> 00:26:11.409 align:start position:0% so sorry yeah it'll be for another day and<00:26:08.860> finally<00:26:09.860> some<00:26:10.850> of<00:26:10.879> you<00:26:11.119> may<00:26:11.269> be<00:26:11.299> thinking 00:26:11.409 --> 00:26:11.419 align:start position:0% and finally some of you may be thinking 00:26:11.419 --> 00:26:14.289 align:start position:0% and finally some of you may be thinking but<00:26:12.320> I<00:26:12.590> like<00:26:12.950> the<00:26:13.129> web<00:26:13.279> the<00:26:13.639> web<00:26:13.669> has<00:26:13.999> so<00:26:14.179> many 00:26:14.289 --> 00:26:14.299 align:start position:0% but I like the web the web has so many 00:26:14.299 --> 00:26:15.999 align:start position:0% but I like the web the web has so many things<00:26:14.450> are<00:26:14.960> you<00:26:15.080> just<00:26:15.320> like<00:26:15.499> showing<00:26:15.799> the 00:26:15.999 --> 00:26:16.009 align:start position:0% things are you just like showing the 00:26:16.009 --> 00:26:18.159 align:start position:0% things are you just like showing the whole<00:26:16.159> web<00:26:16.340> away<00:26:16.580> of<00:26:17.240> course<00:26:17.539> not<00:26:17.749> and<00:26:17.990> not 00:26:18.159 --> 00:26:18.169 align:start position:0% whole web away of course not and not 00:26:18.169 --> 00:26:20.289 align:start position:0% whole web away of course not and not that<00:26:18.409> in<00:26:18.649> saying<00:26:19.090> everything<00:26:20.090> is<00:26:20.119> work 00:26:20.289 --> 00:26:20.299 align:start position:0% that in saying everything is work 00:26:20.299 --> 00:26:22.869 align:start position:0% that in saying everything is work compatible<00:26:20.929> and<00:26:21.259> mooned<00:26:21.830> apps<00:26:22.039> also<00:26:22.730> work 00:26:22.869 --> 00:26:22.879 align:start position:0% compatible and mooned apps also work 00:26:22.879 --> 00:26:25.359 align:start position:0% compatible and mooned apps also work inside<00:26:23.240> a<00:26:23.299> browser<00:26:23.769> moon<00:26:24.769> Lang<00:26:24.980> can<00:26:25.279> be 00:26:25.359 --> 00:26:25.369 align:start position:0% inside a browser moon Lang can be 00:26:25.369 --> 00:26:29.139 align:start position:0% inside a browser moon Lang can be compiled<00:26:25.669> to<00:26:25.820> JavaScript<00:26:27.309> in<00:26:28.309> fact<00:26:28.610> you<00:26:28.909> could 00:26:29.139 --> 00:26:29.149 align:start position:0% compiled to JavaScript in fact you could 00:26:29.149 --> 00:26:31.180 align:start position:0% compiled to JavaScript in fact you could even<00:26:29.179> use<00:26:29.600> more<00:26:29.809> languages<00:26:30.499> a<00:26:30.529> safe<00:26:30.799> module 00:26:31.180 --> 00:26:31.190 align:start position:0% even use more languages a safe module 00:26:31.190 --> 00:26:33.549 align:start position:0% even use more languages a safe module system<00:26:31.519> for<00:26:31.639> JavaScript<00:26:32.119> so<00:26:32.899> for<00:26:33.139> example 00:26:33.549 --> 00:26:33.559 align:start position:0% system for JavaScript so for example 00:26:33.559 --> 00:26:36.009 align:start position:0% system for JavaScript so for example here<00:26:34.220> I<00:26:34.399> import<00:26:34.879> morning<00:26:35.330> in<00:26:35.659> normal 00:26:36.009 --> 00:26:36.019 align:start position:0% here I import morning in normal 00:26:36.019 --> 00:26:39.279 align:start position:0% here I import morning in normal JavaScript<00:26:36.259> code<00:26:37.389> then<00:26:38.389> I<00:26:38.570> use<00:26:38.809> moon<00:26:39.110> langage 00:26:39.279 --> 00:26:39.289 align:start position:0% JavaScript code then I use moon langage 00:26:39.289 --> 00:26:43.200 align:start position:0% JavaScript code then I use moon langage imports<00:26:39.950> on<00:26:40.100> library<00:26:40.940> from<00:26:41.629> ipfs<00:26:42.289> or<00:26:42.529> swarm 00:26:43.200 --> 00:26:43.210 align:start position:0% imports on library from ipfs or swarm 00:26:43.210 --> 00:26:47.109 align:start position:0% imports on library from ipfs or swarm and<00:26:44.710> then<00:26:45.710> I<00:26:45.919> use<00:26:46.100> that<00:26:46.340> library<00:26:46.580> inside 00:26:47.109 --> 00:26:47.119 align:start position:0% and then I use that library inside 00:26:47.119 --> 00:26:50.950 align:start position:0% and then I use that library inside normal<00:26:47.690> JavaScript<00:26:48.909> so<00:26:49.909> you<00:26:50.179> don't<00:26:50.480> actually 00:26:50.950 --> 00:26:50.960 align:start position:0% normal JavaScript so you don't actually 00:26:50.960 --> 00:26:53.560 align:start position:0% normal JavaScript so you don't actually need<00:26:51.379> to<00:26:51.649> use<00:26:51.889> my<00:26:52.100> way<00:26:52.279> to<00:26:52.850> benefit<00:26:53.179> from<00:26:53.389> it 00:26:53.560 --> 00:26:53.570 align:start position:0% need to use my way to benefit from it 00:26:53.570 --> 00:26:57.639 align:start position:0% need to use my way to benefit from it and<00:26:55.029> it<00:26:56.029> also<00:26:56.269> works<00:26:56.539> on<00:26:56.749> other<00:26:56.960> languages<00:26:57.379> so 00:26:57.639 --> 00:26:57.649 align:start position:0% and it also works on other languages so 00:26:57.649 --> 00:26:59.710 align:start position:0% and it also works on other languages so you<00:26:57.679> can<00:26:57.889> think<00:26:58.159> of<00:26:58.249> it<00:26:58.490> as<00:26:58.759> kind<00:26:59.360> of<00:26:59.480> like<00:26:59.539> a 00:26:59.710 --> 00:26:59.720 align:start position:0% you can think of it as kind of like a 00:26:59.720 --> 00:27:02.409 align:start position:0% you can think of it as kind of like a safe<00:27:00.320> coding<00:27:00.889> sharing<00:27:01.249> tool<00:27:01.429> not<00:27:01.909> an<00:27:02.090> actual 00:27:02.409 --> 00:27:02.419 align:start position:0% safe coding sharing tool not an actual 00:27:02.419 --> 00:27:06.220 align:start position:0% safe coding sharing tool not an actual language<00:27:02.869> you<00:27:03.619> don't<00:27:03.740> need<00:27:03.950> to<00:27:04.129> use<00:27:04.279> it<00:27:05.230> so 00:27:06.220 --> 00:27:06.230 align:start position:0% language you don't need to use it so 00:27:06.230 --> 00:27:08.590 align:start position:0% language you don't need to use it so demo<00:27:06.559> time 00:27:08.590 --> 00:27:08.600 align:start position:0% demo time 00:27:08.600 --> 00:27:11.869 align:start position:0% demo time this<00:27:09.600> is<00:27:09.779> a<00:27:09.809> video<00:27:10.200> of<00:27:10.379> the<00:27:10.679> moon<00:27:10.830> browser<00:27:11.070> it's 00:27:11.869 --> 00:27:11.879 align:start position:0% this is a video of the moon browser it's 00:27:11.879 --> 00:27:14.960 align:start position:0% this is a video of the moon browser it's the<00:27:12.149> web<00:27:12.360> version<00:27:12.570> of<00:27:12.990> the<00:27:13.049> moon<00:27:13.350> engine<00:27:13.970> this 00:27:14.960 --> 00:27:14.970 align:start position:0% the web version of the moon engine this 00:27:14.970 --> 00:27:18.409 align:start position:0% the web version of the moon engine this is<00:27:15.360> a<00:27:15.389> hundred<00:27:15.720> kilobytes<00:27:16.200> HTML<00:27:17.070> file<00:27:17.370> so<00:27:18.090> yes 00:27:18.409 --> 00:27:18.419 align:start position:0% is a hundred kilobytes HTML file so yes 00:27:18.419 --> 00:27:20.810 align:start position:0% is a hundred kilobytes HTML file so yes it's<00:27:18.690> really<00:27:19.049> small<00:27:19.289> you<00:27:19.500> can<00:27:20.039> use<00:27:20.250> it<00:27:20.460> kind<00:27:20.700> of 00:27:20.810 --> 00:27:20.820 align:start position:0% it's really small you can use it kind of 00:27:20.820 --> 00:27:24.560 align:start position:0% it's really small you can use it kind of like<00:27:20.879> a<00:27:21.059> mighty<00:27:21.360> wallet<00:27:21.899> but<00:27:22.559> if<00:27:22.799> dubs<00:27:23.570> so 00:27:24.560 --> 00:27:24.570 align:start position:0% like a mighty wallet but if dubs so 00:27:24.570 --> 00:27:27.560 align:start position:0% like a mighty wallet but if dubs so let's<00:27:24.960> open<00:27:25.139> up<00:27:25.440> that<00:27:25.559> by<00:27:25.980> placing<00:27:26.340> its<00:27:26.909> ipfs 00:27:27.560 --> 00:27:27.570 align:start position:0% let's open up that by placing its ipfs 00:27:27.570 --> 00:27:34.039 align:start position:0% let's open up that by placing its ipfs hash<00:27:27.809> I<00:27:31.519> think<00:27:32.519> I<00:27:32.610> see<00:27:32.820> this<00:27:33.389> depths<00:27:33.809> pretty 00:27:34.039 --> 00:27:34.049 align:start position:0% hash I think I see this depths pretty 00:27:34.049 --> 00:27:36.230 align:start position:0% hash I think I see this depths pretty simple<00:27:34.409> there<00:27:34.919> is<00:27:34.950> an<00:27:35.129> title<00:27:35.549> there<00:27:36.029> is<00:27:36.059> an 00:27:36.230 --> 00:27:36.240 align:start position:0% simple there is an title there is an 00:27:36.240 --> 00:27:38.149 align:start position:0% simple there is an title there is an image<00:27:36.509> and<00:27:36.720> there's<00:27:37.169> the<00:27:37.350> button<00:27:37.529> number<00:27:37.740> it's 00:27:38.149 --> 00:27:38.159 align:start position:0% image and there's the button number it's 00:27:38.159 --> 00:27:39.320 align:start position:0% image and there's the button number it's connected<00:27:38.700> to<00:27:38.730> it<00:27:39.000> whew 00:27:39.320 --> 00:27:39.330 align:start position:0% connected to it whew 00:27:39.330 --> 00:27:44.899 align:start position:0% connected to it whew so<00:27:40.139> let's<00:27:40.440> see<00:27:40.679> how<00:27:40.830> its<00:27:40.980> holes<00:27:41.309> look<00:27:41.549> like<00:27:43.909> one 00:27:44.899 --> 00:27:44.909 align:start position:0% so let's see how its holes look like one 00:27:44.909 --> 00:27:46.610 align:start position:0% so let's see how its holes look like one of<00:27:45.029> the<00:27:45.179> cool<00:27:45.360> things<00:27:45.389> about<00:27:45.659> me<00:27:46.019> is<00:27:46.259> that<00:27:46.470> you 00:27:46.610 --> 00:27:46.620 align:start position:0% of the cool things about me is that you 00:27:46.620 --> 00:27:49.129 align:start position:0% of the cool things about me is that you can<00:27:46.649> always<00:27:47.039> recover<00:27:47.519> readable<00:27:48.360> cold<00:27:48.659> fronts 00:27:49.129 --> 00:27:49.139 align:start position:0% can always recover readable cold fronts 00:27:49.139 --> 00:27:51.259 align:start position:0% can always recover readable cold fronts byte<00:27:49.350> code<00:27:49.620> so<00:27:50.250> it's<00:27:50.429> not<00:27:50.580> actually<00:27:51.029> playing 00:27:51.259 --> 00:27:51.269 align:start position:0% byte code so it's not actually playing 00:27:51.269 --> 00:27:53.480 align:start position:0% byte code so it's not actually playing tags<00:27:51.629> as<00:27:51.899> we<00:27:52.169> do<00:27:52.320> on<00:27:52.529> the<00:27:52.649> web<00:27:52.799> we<00:27:53.100> recover 00:27:53.480 --> 00:27:53.490 align:start position:0% tags as we do on the web we recover 00:27:53.490 --> 00:27:57.499 align:start position:0% tags as we do on the web we recover readable<00:27:54.179> code<00:27:54.389> from<00:27:54.990> the<00:27:55.110> byte<00:27:55.259> code<00:27:56.509> above 00:27:57.499 --> 00:27:57.509 align:start position:0% readable code from the byte code above 00:27:57.509 --> 00:28:01.519 align:start position:0% readable code from the byte code above the<00:27:57.779> we<00:27:58.620> have<00:27:58.830> imports<00:27:59.700> with<00:28:00.240> address<00:28:00.899> ipfs 00:28:01.519 --> 00:28:01.529 align:start position:0% the we have imports with address ipfs 00:28:01.529 --> 00:28:04.249 align:start position:0% the we have imports with address ipfs hash<00:28:01.769> and<00:28:02.370> that's<00:28:02.850> good<00:28:03.120> because<00:28:03.330> with<00:28:04.019> that 00:28:04.249 --> 00:28:04.259 align:start position:0% hash and that's good because with that 00:28:04.259 --> 00:28:06.049 align:start position:0% hash and that's good because with that you<00:28:04.409> can<00:28:04.559> make<00:28:04.740> sure<00:28:04.769> that<00:28:05.279> those<00:28:05.549> imports 00:28:06.049 --> 00:28:06.059 align:start position:0% you can make sure that those imports 00:28:06.059 --> 00:28:12.169 align:start position:0% you can make sure that those imports will<00:28:06.240> never<00:28:06.480> change<00:28:10.669> we<00:28:11.669> have<00:28:11.820> the<00:28:12.000> main 00:28:12.169 --> 00:28:12.179 align:start position:0% will never change we have the main 00:28:12.179 --> 00:28:14.149 align:start position:0% will never change we have the main components<00:28:12.779> with<00:28:12.960> some<00:28:13.259> things<00:28:13.559> like<00:28:13.860> its 00:28:14.149 --> 00:28:14.159 align:start position:0% components with some things like its 00:28:14.159 --> 00:28:20.060 align:start position:0% components with some things like its name<00:28:14.460> its<00:28:14.909> local<00:28:15.450> state<00:28:15.690> and<00:28:15.990> a<00:28:16.500> title<00:28:19.070> there 00:28:20.060 --> 00:28:20.070 align:start position:0% name its local state and a title there 00:28:20.070 --> 00:28:23.149 align:start position:0% name its local state and a title there is<00:28:20.190> on<00:28:20.340> fetch<00:28:20.639> function<00:28:21.320> it<00:28:22.320> gets<00:28:22.679> data<00:28:22.919> for 00:28:23.149 --> 00:28:23.159 align:start position:0% is on fetch function it gets data for 00:28:23.159 --> 00:28:25.159 align:start position:0% is on fetch function it gets data for children<00:28:23.519> since<00:28:23.970> moons<00:28:24.299> are<00:28:24.509> pure<00:28:24.750> language 00:28:25.159 --> 00:28:25.169 align:start position:0% children since moons are pure language 00:28:25.169 --> 00:28:28.129 align:start position:0% children since moons are pure language we<00:28:25.529> need<00:28:25.830> to<00:28:26.129> use<00:28:26.700> something<00:28:27.000> called<00:28:27.179> mana<00:28:27.750> to 00:28:28.129 --> 00:28:28.139 align:start position:0% we need to use something called mana to 00:28:28.139 --> 00:28:29.810 align:start position:0% we need to use something called mana to do<00:28:28.289> that<00:28:28.500> but<00:28:29.009> you<00:28:29.129> don't<00:28:29.279> need<00:28:29.460> to<00:28:29.519> worry 00:28:29.810 --> 00:28:29.820 align:start position:0% do that but you don't need to worry 00:28:29.820 --> 00:28:33.159 align:start position:0% do that but you don't need to worry about<00:28:30.029> that<00:28:30.240> because<00:28:30.480> that's<00:28:30.840> very<00:28:30.929> hidden 00:28:33.159 --> 00:28:33.169 align:start position:0% about that because that's very hidden 00:28:33.169 --> 00:28:36.590 align:start position:0% about that because that's very hidden and<00:28:34.519> finally<00:28:35.519> we<00:28:35.610> have<00:28:35.759> the<00:28:35.909> handy<00:28:36.179> function 00:28:36.590 --> 00:28:36.600 align:start position:0% and finally we have the handy function 00:28:36.600 --> 00:28:39.740 align:start position:0% and finally we have the handy function it's<00:28:36.779> kind<00:28:37.049> of<00:28:37.110> like<00:28:37.259> react<00:28:37.649> so<00:28:38.580> I<00:28:39.090> guess<00:28:39.480> some 00:28:39.740 --> 00:28:39.750 align:start position:0% it's kind of like react so I guess some 00:28:39.750 --> 00:28:41.539 align:start position:0% it's kind of like react so I guess some of<00:28:39.870> you<00:28:40.019> may<00:28:40.169> be<00:28:40.200> familiar<00:28:40.470> with<00:28:40.799> that<00:28:40.860> already 00:28:41.539 --> 00:28:41.549 align:start position:0% of you may be familiar with that already 00:28:41.549 --> 00:28:48.200 align:start position:0% of you may be familiar with that already so<00:28:42.210> let's<00:28:42.480> change<00:28:42.629> some<00:28:42.899> things<00:28:47.029> here<00:28:48.029> will 00:28:48.200 --> 00:28:48.210 align:start position:0% so let's change some things here will 00:28:48.210 --> 00:28:51.619 align:start position:0% so let's change some things here will replace<00:28:48.509> moon<00:28:48.960> by<00:28:49.139> Def<00:28:49.320> Con<00:28:49.590> on<00:28:49.830> the<00:28:49.980> body<00:28:50.629> we 00:28:51.619 --> 00:28:51.629 align:start position:0% replace moon by Def Con on the body we 00:28:51.629 --> 00:28:55.220 align:start position:0% replace moon by Def Con on the body we also<00:28:51.840> do<00:28:52.230> that<00:28:52.470> on<00:28:52.679> the<00:28:52.769> title<00:28:53.269> and<00:28:54.269> now<00:28:54.509> I<00:28:54.779> want 00:28:55.220 --> 00:28:55.230 align:start position:0% also do that on the title and now I want 00:28:55.230 --> 00:28:57.830 align:start position:0% also do that on the title and now I want you<00:28:55.320> to<00:28:55.470> pay<00:28:55.649> attention<00:28:55.860> to<00:28:56.190> the<00:28:56.610> hash<00:28:57.179> bar<00:28:57.450> the 00:28:57.830 --> 00:28:57.840 align:start position:0% you to pay attention to the hash bar the 00:28:57.840 --> 00:29:02.960 align:start position:0% you to pay attention to the hash bar the title<00:28:58.200> above<00:28:58.470> there<00:29:00.919> as<00:29:01.919> you<00:29:02.100> can<00:29:02.129> see<00:29:02.279> not 00:29:02.960 --> 00:29:02.970 align:start position:0% title above there as you can see not 00:29:02.970 --> 00:29:05.180 align:start position:0% title above there as you can see not only<00:29:03.240> the<00:29:03.419> title<00:29:03.899> but<00:29:04.169> the<00:29:04.320> hash<00:29:04.500> itself<00:29:04.980> has 00:29:05.180 --> 00:29:05.190 align:start position:0% only the title but the hash itself has 00:29:05.190 --> 00:29:08.149 align:start position:0% only the title but the hash itself has changed<00:29:05.549> that<00:29:06.480> means<00:29:06.929> the<00:29:07.320> new<00:29:07.710> tab<00:29:07.919> is 00:29:08.149 --> 00:29:08.159 align:start position:0% changed that means the new tab is 00:29:08.159 --> 00:29:10.879 align:start position:0% changed that means the new tab is already<00:29:08.490> published<00:29:08.820> on<00:29:09.149> my<00:29:09.269> PFS<00:29:09.509> or<00:29:10.200> in<00:29:10.679> other 00:29:10.879 --> 00:29:10.889 align:start position:0% already published on my PFS or in other 00:29:10.889 --> 00:29:13.369 align:start position:0% already published on my PFS or in other words<00:29:11.190> we<00:29:11.610> just<00:29:11.879> hard<00:29:12.210> forked<00:29:12.779> that's<00:29:13.110> that 00:29:13.369 --> 00:29:13.379 align:start position:0% words we just hard forked that's that 00:29:13.379 --> 00:29:17.270 align:start position:0% words we just hard forked that's that that's<00:29:14.250> kind<00:29:14.519> of<00:29:14.580> cool<00:29:14.730> don't<00:29:14.940> you<00:29:15.000> think 00:29:17.270 --> 00:29:17.280 align:start position:0% 00:29:17.280 --> 00:29:19.910 align:start position:0% of<00:29:17.700> course<00:29:18.540> it's<00:29:18.810> a<00:29:18.900> very<00:29:19.080> simple<00:29:19.410> app<00:29:19.560> so 00:29:19.910 --> 00:29:19.920 align:start position:0% of course it's a very simple app so 00:29:19.920 --> 00:29:26.960 align:start position:0% of course it's a very simple app so let's<00:29:20.190> open<00:29:20.340> something<00:29:20.700> more<00:29:21.030> useful<00:29:25.850> this<00:29:26.850> is 00:29:26.960 --> 00:29:26.970 align:start position:0% let's open something more useful this is 00:29:26.970 --> 00:29:30.500 align:start position:0% let's open something more useful this is a<00:29:27.080> talking<00:29:28.080> wallet<00:29:28.790> there<00:29:29.790> is<00:29:29.820> some<00:29:30.060> there's 00:29:30.500 --> 00:29:30.510 align:start position:0% a talking wallet there is some there's 00:29:30.510 --> 00:29:32.600 align:start position:0% a talking wallet there is some there's no<00:29:30.690> written<00:29:30.990> on<00:29:31.080> this<00:29:31.170> account<00:29:31.530> so<00:29:31.950> let's<00:29:31.980> and 00:29:32.600 --> 00:29:32.610 align:start position:0% no written on this account so let's and 00:29:32.610 --> 00:29:51.730 align:start position:0% no written on this account so let's and submit<00:29:33.060> it<00:29:33.090> to<00:29:33.210> it 00:29:51.730 --> 00:29:51.740 align:start position:0% 00:29:51.740 --> 00:29:53.799 align:start position:0% as<00:29:52.640> you<00:29:52.760> can<00:29:52.909> see<00:29:53.029> the<00:29:53.149> confirmation<00:29:53.419> window 00:29:53.799 --> 00:29:53.809 align:start position:0% as you can see the confirmation window 00:29:53.809 --> 00:29:56.889 align:start position:0% as you can see the confirmation window is<00:29:54.110> a<00:29:54.140> little<00:29:54.649> bit<00:29:54.770> ugly<00:29:55.190> but<00:29:55.370> the<00:29:56.270> transaction 00:29:56.889 --> 00:29:56.899 align:start position:0% is a little bit ugly but the transaction 00:29:56.899 --> 00:30:00.100 align:start position:0% is a little bit ugly but the transaction was<00:29:57.110> silent<00:29:57.590> and<00:29:57.679> sent<00:29:58.070> so<00:29:58.940> let's<00:29:59.630> select<00:29:59.899> the 00:30:00.100 --> 00:30:00.110 align:start position:0% was silent and sent so let's select the 00:30:00.110 --> 00:30:11.500 align:start position:0% was silent and sent so let's select the previous<00:30:00.500> account<00:30:00.830> and<00:30:02.590> see<00:30:03.590> the<00:30:03.679> code<00:30:10.149> okay 00:30:11.500 --> 00:30:11.510 align:start position:0% previous account and see the code okay 00:30:11.510 --> 00:30:14.799 align:start position:0% previous account and see the code okay so<00:30:11.929> one<00:30:12.470> of<00:30:12.500> the<00:30:12.740> cool<00:30:12.919> things<00:30:12.950> about<00:30:13.340> me<00:30:14.059> is 00:30:14.799 --> 00:30:14.809 align:start position:0% so one of the cool things about me is 00:30:14.809 --> 00:30:18.610 align:start position:0% so one of the cool things about me is that<00:30:15.230> it<00:30:16.159> has<00:30:17.029> a<00:30:17.059> component<00:30:17.600> based<00:30:17.990> back<00:30:18.350> shot 00:30:18.610 --> 00:30:18.620 align:start position:0% that it has a component based back shot 00:30:18.620 --> 00:30:21.370 align:start position:0% that it has a component based back shot architecture<00:30:19.309> so<00:30:19.940> you<00:30:19.970> can<00:30:20.390> like<00:30:20.690> get<00:30:20.990> inside 00:30:21.370 --> 00:30:21.380 align:start position:0% architecture so you can like get inside 00:30:21.380 --> 00:30:28.690 align:start position:0% architecture so you can like get inside any<00:30:21.679> component<00:30:22.279> that<00:30:22.669> is<00:30:23.059> inside<00:30:23.570> any<00:30:23.840> dad<00:30:27.700> so 00:30:28.690 --> 00:30:28.700 align:start position:0% any component that is inside any dad so 00:30:28.700 --> 00:30:30.730 align:start position:0% any component that is inside any dad so for<00:30:29.000> example<00:30:29.419> here<00:30:29.630> we<00:30:29.899> access<00:30:30.049> a<00:30:30.470> sub 00:30:30.730 --> 00:30:30.740 align:start position:0% for example here we access a sub 00:30:30.740 --> 00:30:35.470 align:start position:0% for example here we access a sub component<00:30:31.250> of<00:30:31.370> the<00:30:31.820> wallets<00:30:32.779> depth<00:30:33.970> and<00:30:34.970> we 00:30:35.470 --> 00:30:35.480 align:start position:0% component of the wallets depth and we 00:30:35.480 --> 00:30:37.539 align:start position:0% component of the wallets depth and we can<00:30:35.630> also<00:30:35.809> go<00:30:36.110> all<00:30:36.350> the<00:30:36.559> way<00:30:36.590> down<00:30:36.919> to<00:30:37.190> the<00:30:37.309> most 00:30:37.539 --> 00:30:37.549 align:start position:0% can also go all the way down to the most 00:30:37.549 --> 00:30:43.000 align:start position:0% can also go all the way down to the most basic<00:30:37.940> functions<00:30:41.289> see<00:30:42.289> how<00:30:42.470> everything's 00:30:43.000 --> 00:30:43.010 align:start position:0% basic functions see how everything's 00:30:43.010 --> 00:30:45.190 align:start position:0% basic functions see how everything's hash<00:30:43.309> addresses<00:30:43.940> so<00:30:44.510> one<00:30:44.720> of<00:30:44.750> the<00:30:44.960> cool<00:30:45.169> things 00:30:45.190 --> 00:30:45.200 align:start position:0% hash addresses so one of the cool things 00:30:45.200 --> 00:30:48.250 align:start position:0% hash addresses so one of the cool things about<00:30:45.559> module<00:30:46.220> is<00:30:46.399> that<00:30:46.700> for<00:30:47.480> example<00:30:47.899> if<00:30:48.110> an 00:30:48.250 --> 00:30:48.260 align:start position:0% about module is that for example if an 00:30:48.260 --> 00:30:51.159 align:start position:0% about module is that for example if an application<00:30:48.740> use<00:30:49.279> that<00:30:49.580> same<00:30:49.880> function<00:30:50.390> an 00:30:51.159 --> 00:30:51.169 align:start position:0% application use that same function an 00:30:51.169 --> 00:30:53.529 align:start position:0% application use that same function an equivalent<00:30:51.710> function<00:30:52.190> it<00:30:52.700> will<00:30:52.970> download<00:30:53.210> the 00:30:53.529 --> 00:30:53.539 align:start position:0% equivalent function it will download the 00:30:53.539 --> 00:30:55.720 align:start position:0% equivalent function it will download the same<00:30:53.750> thing<00:30:54.020> so<00:30:54.440> there<00:30:54.799> is<00:30:54.890> a<00:30:54.919> lot<00:30:55.100> of<00:30:55.130> sharing 00:30:55.720 --> 00:30:55.730 align:start position:0% same thing so there is a lot of sharing 00:30:55.730 --> 00:30:59.680 align:start position:0% same thing so there is a lot of sharing and<00:30:55.909> very<00:30:56.450> good<00:30:56.659> users<00:30:57.169> of<00:30:57.470> ipfs<00:30:58.190> resource<00:30:58.690> so 00:30:59.680 --> 00:30:59.690 align:start position:0% and very good users of ipfs resource so 00:30:59.690 --> 00:31:09.299 align:start position:0% and very good users of ipfs resource so ok<00:30:59.870> let's<00:30:59.899> go<00:31:00.260> back<00:31:00.409> to<00:31:00.559> the<00:31:00.649> wallet 00:31:09.299 --> 00:31:09.309 align:start position:0% 00:31:09.309 --> 00:31:12.570 align:start position:0% as<00:31:09.760> you<00:31:09.880> can<00:31:10.000> see<00:31:10.210> already<00:31:10.720> has<00:31:11.710> arrived<00:31:12.100> so 00:31:12.570 --> 00:31:12.580 align:start position:0% as you can see already has arrived so 00:31:12.580 --> 00:31:13.890 align:start position:0% as you can see already has arrived so that's<00:31:12.940> kind<00:31:13.240> of<00:31:13.270> cool 00:31:13.890 --> 00:31:13.900 align:start position:0% that's kind of cool 00:31:13.900 --> 00:31:16.919 align:start position:0% that's kind of cool and<00:31:14.860> for<00:31:15.250> a<00:31:15.280> last<00:31:15.490> thing<00:31:15.730> let's<00:31:16.150> open<00:31:16.540> again 00:31:16.919 --> 00:31:16.929 align:start position:0% and for a last thing let's open again 00:31:16.929 --> 00:31:27.030 align:start position:0% and for a last thing let's open again the<00:31:16.960> token<00:31:17.350> table<00:31:24.990> no<00:31:25.990> there<00:31:26.230> is<00:31:26.320> a<00:31:26.350> questions 00:31:27.030 --> 00:31:27.040 align:start position:0% the token table no there is a questions 00:31:27.040 --> 00:31:29.280 align:start position:0% the token table no there is a questions these<00:31:27.490> are<00:31:27.730> component<00:31:28.240> from<00:31:28.510> the<00:31:28.660> wallet<00:31:28.900> step 00:31:29.280 --> 00:31:29.290 align:start position:0% these are component from the wallet step 00:31:29.290 --> 00:31:32.220 align:start position:0% these are component from the wallet step how<00:31:30.040> hard<00:31:30.370> would<00:31:31.210> it<00:31:31.270> be<00:31:31.450> to<00:31:31.660> use<00:31:31.960> that 00:31:32.220 --> 00:31:32.230 align:start position:0% how hard would it be to use that 00:31:32.230 --> 00:31:34.200 align:start position:0% how hard would it be to use that component<00:31:32.650> inside<00:31:33.280> the<00:31:33.549> hello<00:31:33.730> Def<00:31:33.940> Con<00:31:34.179> that 00:31:34.200 --> 00:31:34.210 align:start position:0% component inside the hello Def Con that 00:31:34.210 --> 00:31:35.910 align:start position:0% component inside the hello Def Con that that<00:31:35.049> we<00:31:35.170> just<00:31:35.350> made 00:31:35.910 --> 00:31:35.920 align:start position:0% that we just made 00:31:35.920 --> 00:31:41.880 align:start position:0% that we just made well<00:31:36.610> let's<00:31:36.850> see<00:31:39.809> so<00:31:40.809> we<00:31:41.200> copy 00:31:41.880 --> 00:31:41.890 align:start position:0% well let's see so we copy 00:31:41.890 --> 00:31:46.530 align:start position:0% well let's see so we copy that's<00:31:42.250> hash<00:31:44.130> we'll<00:31:45.130> go<00:31:45.250> back<00:31:45.490> to<00:31:45.669> the<00:31:45.910> hello 00:31:46.530 --> 00:31:46.540 align:start position:0% that's hash we'll go back to the hello 00:31:46.540 --> 00:31:55.409 align:start position:0% that's hash we'll go back to the hello Def<00:31:46.750> Con<00:31:46.990> that<00:31:52.350> we<00:31:53.350> purchased<00:31:53.980> by<00:31:54.340> using<00:31:54.880> that 00:31:55.409 --> 00:31:55.419 align:start position:0% Def Con that we purchased by using that 00:31:55.419 --> 00:32:04.830 align:start position:0% Def Con that we purchased by using that hash<00:31:55.750> oh<00:32:01.620> sorry<00:32:02.710> and<00:32:03.120> I'll<00:32:04.120> actually<00:32:04.330> go<00:32:04.630> back 00:32:04.830 --> 00:32:04.840 align:start position:0% hash oh sorry and I'll actually go back 00:32:04.840 --> 00:32:07.020 align:start position:0% hash oh sorry and I'll actually go back so<00:32:05.530> because<00:32:06.040> I<00:32:06.160> want<00:32:06.400> to<00:32:06.429> show<00:32:06.610> something's 00:32:07.020 --> 00:32:07.030 align:start position:0% so because I want to show something's 00:32:07.030 --> 00:32:09.450 align:start position:0% so because I want to show something's and<00:32:07.240> I<00:32:07.390> press<00:32:07.690> the<00:32:07.960> arrow<00:32:08.200> on<00:32:08.890> the<00:32:09.309> wrong 00:32:09.450 --> 00:32:09.460 align:start position:0% and I press the arrow on the wrong 00:32:09.460 --> 00:32:18.570 align:start position:0% and I press the arrow on the wrong timing<00:32:10.650> so<00:32:16.410> again<00:32:17.410> here<00:32:17.710> imports<00:32:18.160> the<00:32:18.309> token 00:32:18.570 --> 00:32:18.580 align:start position:0% timing so again here imports the token 00:32:18.580 --> 00:32:20.760 align:start position:0% timing so again here imports the token table 00:32:20.760 --> 00:32:20.770 align:start position:0% table 00:32:20.770 --> 00:32:22.980 align:start position:0% table I<00:32:20.799> replaced<00:32:21.580> the<00:32:21.760> shoot<00:32:22.090> component<00:32:22.690> by<00:32:22.929> the 00:32:22.980 --> 00:32:22.990 align:start position:0% I replaced the shoot component by the 00:32:22.990 --> 00:32:25.289 align:start position:0% I replaced the shoot component by the token<00:32:23.620> table<00:32:23.950> that<00:32:24.070> I<00:32:24.100> just<00:32:24.490> imported 00:32:25.289 --> 00:32:25.299 align:start position:0% token table that I just imported 00:32:25.299 --> 00:32:28.200 align:start position:0% token table that I just imported I<00:32:25.799> removed<00:32:26.799> the<00:32:26.950> moon<00:32:27.190> image<00:32:27.549> so<00:32:27.910> it's<00:32:28.059> the 00:32:28.200 --> 00:32:28.210 align:start position:0% I removed the moon image so it's the 00:32:28.210 --> 00:32:30.289 align:start position:0% I removed the moon image so it's the same<00:32:28.390> place<00:32:28.600> as<00:32:28.900> the<00:32:29.140> moon<00:32:29.290> image<00:32:29.620> would<00:32:29.860> be 00:32:30.289 --> 00:32:30.299 align:start position:0% same place as the moon image would be 00:32:30.299 --> 00:32:34.500 align:start position:0% same place as the moon image would be and<00:32:31.299> we<00:32:32.200> click<00:32:32.410> above<00:32:33.250> that<00:32:33.460> it's<00:32:33.850> forked<00:32:34.299> and 00:32:34.500 --> 00:32:34.510 align:start position:0% and we click above that it's forked and 00:32:34.510 --> 00:32:37.350 align:start position:0% and we click above that it's forked and as<00:32:35.320> you<00:32:35.500> can<00:32:35.620> see<00:32:35.679> that<00:32:36.460> component<00:32:36.880> is<00:32:37.179> not 00:32:37.350 --> 00:32:37.360 align:start position:0% as you can see that component is not 00:32:37.360 --> 00:32:39.240 align:start position:0% as you can see that component is not working<00:32:37.840> inside<00:32:38.260> the<00:32:38.320> hello<00:32:38.650> Def<00:32:38.830> Con<00:32:39.040> that 00:32:39.240 --> 00:32:39.250 align:start position:0% working inside the hello Def Con that 00:32:39.250 --> 00:32:42.000 align:start position:0% working inside the hello Def Con that and<00:32:39.760> doing<00:32:40.450> that<00:32:40.630> kind<00:32:40.929> of<00:32:41.020> thing<00:32:41.080> is<00:32:41.500> always 00:32:42.000 --> 00:32:42.010 align:start position:0% and doing that kind of thing is always 00:32:42.010 --> 00:32:44.430 align:start position:0% and doing that kind of thing is always safe<00:32:42.250> so<00:32:42.940> we<00:32:43.090> can<00:32:43.299> always<00:32:43.690> take<00:32:43.960> a<00:32:43.990> component 00:32:44.430 --> 00:32:44.440 align:start position:0% safe so we can always take a component 00:32:44.440 --> 00:32:46.799 align:start position:0% safe so we can always take a component from<00:32:44.770> some<00:32:45.160> other<00:32:45.400> that<00:32:45.700> and<00:32:46.000> what<00:32:46.540> eating 00:32:46.799 --> 00:32:46.809 align:start position:0% from some other that and what eating 00:32:46.809 --> 00:32:49.230 align:start position:0% from some other that and what eating your<00:32:47.080> that<00:32:47.320> and<00:32:47.559> because<00:32:48.250> moon<00:32:48.520> is<00:32:48.700> pure<00:32:49.030> and 00:32:49.230 --> 00:32:49.240 align:start position:0% your that and because moon is pure and 00:32:49.240 --> 00:32:51.120 align:start position:0% your that and because moon is pure and may<00:32:49.510> to<00:32:49.570> be<00:32:49.809> secure<00:32:50.110> you<00:32:50.290> can<00:32:50.470> always<00:32:50.710> do<00:32:50.950> that 00:32:51.120 --> 00:32:51.130 align:start position:0% may to be secure you can always do that 00:32:51.130 --> 00:32:55.110 align:start position:0% may to be secure you can always do that without<00:32:51.340> worrying<00:32:51.850> at<00:32:52.179> all<00:32:53.070> so<00:32:54.070> in<00:32:54.340> short<00:32:54.370> add 00:32:55.110 --> 00:32:55.120 align:start position:0% without worrying at all so in short add 00:32:55.120 --> 00:32:56.970 align:start position:0% without worrying at all so in short add app<00:32:55.330> engine<00:32:55.780> that<00:32:56.020> can<00:32:56.230> be<00:32:56.380> formally<00:32:56.710> proven 00:32:56.970 --> 00:32:56.980 align:start position:0% app engine that can be formally proven 00:32:56.980 --> 00:32:59.220 align:start position:0% app engine that can be formally proven secure<00:32:57.280> and<00:32:57.669> a<00:32:58.120> scripting<00:32:58.630> language<00:32:58.660> we're 00:32:59.220 --> 00:32:59.230 align:start position:0% secure and a scripting language we're 00:32:59.230 --> 00:33:01.650 align:start position:0% secure and a scripting language we're sharing<00:32:59.559> code<00:32:59.740> is<00:32:59.950> always<00:33:00.280> safe<00:33:00.580> and<00:33:01.120> actually 00:33:01.650 --> 00:33:01.660 align:start position:0% sharing code is always safe and actually 00:33:01.660 --> 00:33:04.950 align:start position:0% sharing code is always safe and actually word<00:33:02.260> that's<00:33:03.070> the<00:33:03.370> moon<00:33:03.520> project<00:33:03.960> if 00:33:04.950 --> 00:33:04.960 align:start position:0% word that's the moon project if 00:33:04.960 --> 00:33:07.049 align:start position:0% word that's the moon project if you<00:33:05.140> want<00:33:05.260> to<00:33:05.350> try<00:33:05.530> it<00:33:05.590> we<00:33:05.919> have<00:33:06.130> a<00:33:06.160> live<00:33:06.669> demo 00:33:07.049 --> 00:33:07.059 align:start position:0% you want to try it we have a live demo 00:33:07.059 --> 00:33:11.510 align:start position:0% you want to try it we have a live demo at<00:33:07.240> that<00:33:07.720> you<00:33:08.020> are<00:33:08.169> how<00:33:08.290> thank<00:33:09.190> you 00:33:11.510 --> 00:33:11.520 align:start position:0% 00:33:11.520 --> 00:33:19.009 align:start position:0% [Applause] 00:33:19.009 --> 00:33:19.019 align:start position:0% 00:33:19.019 --> 00:33:21.839 align:start position:0% by<00:33:20.019> the<00:33:20.080> way<00:33:20.289> just<00:33:20.590> a<00:33:20.769> smaller<00:33:21.129> point<00:33:21.549> I<00:33:21.729> would 00:33:21.839 --> 00:33:21.849 align:start position:0% by the way just a smaller point I would 00:33:21.849 --> 00:33:23.909 align:start position:0% by the way just a smaller point I would like<00:33:21.940> to<00:33:22.210> make<00:33:22.359> that<00:33:23.200> whole<00:33:23.470> thing<00:33:23.739> is 00:33:23.909 --> 00:33:23.919 align:start position:0% like to make that whole thing is 00:33:23.919 --> 00:33:26.039 align:start position:0% like to make that whole thing is actually<00:33:24.159> decentralized<00:33:24.879> so<00:33:25.509> there<00:33:25.749> is<00:33:25.840> no 00:33:26.039 --> 00:33:26.049 align:start position:0% actually decentralized so there is no 00:33:26.049 --> 00:33:29.669 align:start position:0% actually decentralized so there is no central<00:33:26.470> computer<00:33:27.039> anywhere<00:33:28.200> the<00:33:29.200> back<00:33:29.409> end 00:33:29.669 --> 00:33:29.679 align:start position:0% central computer anywhere the back end 00:33:29.679 --> 00:33:34.009 align:start position:0% central computer anywhere the back end of<00:33:29.799> the<00:33:29.979> Deb's<00:33:30.220> is<00:33:30.489> a<00:33:30.519> film<00:33:31.409> code<00:33:32.409> is 00:33:34.009 --> 00:33:34.019 align:start position:0% of the Deb's is a film code is 00:33:34.019 --> 00:33:38.099 align:start position:0% of the Deb's is a film code is downloaded<00:33:35.019> from<00:33:35.679> ipfs<00:33:36.249> so<00:33:37.119> like<00:33:37.690> you<00:33:37.869> can 00:33:38.099 --> 00:33:38.109 align:start position:0% downloaded from ipfs so like you can 00:33:38.109 --> 00:33:40.409 align:start position:0% downloaded from ipfs so like you can just<00:33:38.349> try<00:33:38.979> it<00:33:39.039> do<00:33:39.519> something<00:33:39.820> I<00:33:40.059> don't<00:33:40.269> like 00:33:40.409 --> 00:33:40.419 align:start position:0% just try it do something I don't like 00:33:40.419 --> 00:33:42.299 align:start position:0% just try it do something I don't like and<00:33:40.659> there's<00:33:40.840> not<00:33:41.080> anything<00:33:41.529> that<00:33:41.679> me<00:33:42.039> or 00:33:42.299 --> 00:33:42.309 align:start position:0% and there's not anything that me or 00:33:42.309 --> 00:33:44.159 align:start position:0% and there's not anything that me or anyone<00:33:42.669> else<00:33:43.090> in<00:33:43.450> the<00:33:43.509> world<00:33:43.690> could<00:33:43.899> do<00:33:44.049> about 00:33:44.159 --> 00:33:44.169 align:start position:0% anyone else in the world could do about 00:33:44.169 --> 00:33:46.409 align:start position:0% anyone else in the world could do about it<00:33:44.320> because<00:33:45.279> mooned<00:33:45.519> apps<00:33:45.700> are<00:33:45.940> actually 00:33:46.409 --> 00:33:46.419 align:start position:0% it because mooned apps are actually 00:33:46.419 --> 00:33:49.169 align:start position:0% it because mooned apps are actually public<00:33:47.710> decentralized<00:33:48.580> resilient 00:33:49.169 --> 00:33:49.179 align:start position:0% public decentralized resilient 00:33:49.179 --> 00:33:51.810 align:start position:0% public decentralized resilient and<00:33:49.419> free<00:33:49.659> is<00:33:49.869> acting<00:33:50.590> like<00:33:50.619> smart<00:33:51.309> contracts 00:33:51.810 --> 00:33:51.820 align:start position:0% and free is acting like smart contracts 00:33:51.820 --> 00:33:56.970 align:start position:0% and free is acting like smart contracts ah<00:33:52.409> as<00:33:53.409> I<00:33:53.710> think<00:33:53.979> that<00:33:54.220> that<00:33:54.489> should<00:33:54.759> be