WEBVTT Kind: captions Language: en 00:00:04.750 --> 00:00:15.709 align:start position:0% [Music] 00:00:15.709 --> 00:00:15.719 align:start position:0% 00:00:15.719 --> 00:00:18.429 align:start position:0% so<00:00:16.400> thank<00:00:16.560> you<00:00:16.760> everyone<00:00:17.119> for<00:00:17.359> coming<00:00:17.800> and<00:00:18.240> as 00:00:18.429 --> 00:00:18.439 align:start position:0% so thank you everyone for coming and as 00:00:18.439 --> 00:00:20.990 align:start position:0% so thank you everyone for coming and as this<00:00:18.600> is<00:00:18.720> a<00:00:18.920> developers<00:00:19.520> conference<00:00:20.160> I<00:00:20.840> had 00:00:20.990 --> 00:00:21.000 align:start position:0% this is a developers conference I had 00:00:21.000 --> 00:00:23.830 align:start position:0% this is a developers conference I had planned<00:00:21.320> to<00:00:21.439> do<00:00:21.680> the<00:00:22.000> developers<00:00:22.560> rant<00:00:23.039> but<00:00:23.439> um 00:00:23.830 --> 00:00:23.840 align:start position:0% planned to do the developers rant but um 00:00:23.840 --> 00:00:26.589 align:start position:0% planned to do the developers rant but um I've<00:00:24.039> been<00:00:24.199> informed<00:00:24.599> I'm<00:00:24.720> not<00:00:24.880> sweaty<00:00:25.359> enough 00:00:26.589 --> 00:00:26.599 align:start position:0% I've been informed I'm not sweaty enough 00:00:26.599 --> 00:00:30.509 align:start position:0% I've been informed I'm not sweaty enough so<00:00:27.599> um<00:00:27.800> my<00:00:27.960> name<00:00:28.119> is<00:00:28.279> Ming<00:00:28.599> Chan<00:00:29.599> I<00:00:29.759> am<00:00:30.160> the<00:00:30.240> new 00:00:30.509 --> 00:00:30.519 align:start position:0% so um my name is Ming Chan I am the new 00:00:30.519 --> 00:00:32.549 align:start position:0% so um my name is Ming Chan I am the new executive<00:00:31.039> director<00:00:31.640> of<00:00:31.960> ethereum 00:00:32.549 --> 00:00:32.559 align:start position:0% executive director of ethereum 00:00:32.559 --> 00:00:36.069 align:start position:0% executive director of ethereum foundation<00:00:33.440> as<00:00:33.640> of<00:00:34.200> August<00:00:34.719> 1st<00:00:35.160> and<00:00:35.360> I'm<00:00:35.719> very 00:00:36.069 --> 00:00:36.079 align:start position:0% foundation as of August 1st and I'm very 00:00:36.079 --> 00:00:38.590 align:start position:0% foundation as of August 1st and I'm very pleased<00:00:36.480> to<00:00:36.640> be<00:00:36.840> able<00:00:37.200> to<00:00:38.000> give<00:00:38.160> an 00:00:38.590 --> 00:00:38.600 align:start position:0% pleased to be able to give an 00:00:38.600 --> 00:00:40.830 align:start position:0% pleased to be able to give an introduction<00:00:39.600> to 00:00:40.830 --> 00:00:40.840 align:start position:0% introduction to 00:00:40.840 --> 00:00:44.950 align:start position:0% introduction to our<00:00:41.840> our<00:00:42.559> lead<00:00:43.559> um<00:00:44.039> Chief<00:00:44.559> our<00:00:44.680> chief 00:00:44.950 --> 00:00:44.960 align:start position:0% our our lead um Chief our chief 00:00:44.960 --> 00:00:47.150 align:start position:0% our our lead um Chief our chief scientist<00:00:45.360> and<00:00:45.520> Creator<00:00:45.960> vitalic<00:00:46.320> butan<00:00:46.920> our 00:00:47.150 --> 00:00:47.160 align:start position:0% scientist and Creator vitalic butan our 00:00:47.160 --> 00:00:49.310 align:start position:0% scientist and Creator vitalic butan our chief<00:00:47.840> our<00:00:48.039> lead<00:00:48.480> go<00:00:48.800> developer<00:00:49.160> and 00:00:49.310 --> 00:00:49.320 align:start position:0% chief our lead go developer and 00:00:49.320 --> 00:00:53.470 align:start position:0% chief our lead go developer and co-founder<00:00:49.920> Jeff<00:00:50.280> wilka<00:00:50.960> vilka<00:00:51.960> and<00:00:52.719> Dr<00:00:53.079> Gavin 00:00:53.470 --> 00:00:53.480 align:start position:0% co-founder Jeff wilka vilka and Dr Gavin 00:00:53.480 --> 00:00:57.310 align:start position:0% co-founder Jeff wilka vilka and Dr Gavin wood<00:00:54.320> our<00:00:54.960> chief<00:00:55.320> web<00:00:55.640> 3<00:00:55.960> architect<00:00:56.879> and<00:00:57.039> Lead 00:00:57.310 --> 00:00:57.320 align:start position:0% wood our chief web 3 architect and Lead 00:00:57.320 --> 00:00:59.590 align:start position:0% wood our chief web 3 architect and Lead C++<00:00:58.079> developer<00:00:58.840> so<00:00:59.000> if<00:00:59.079> you<00:00:59.160> could<00:00:59.320> all<00:00:59.480> give 00:00:59.590 --> 00:00:59.600 align:start position:0% C++ developer so if you could all give 00:00:59.600 --> 00:01:01.880 align:start position:0% C++ developer so if you could all give them<00:00:59.680> a<00:00:59.760> hand<00:01:00.000> and<00:01:00.160> I'm<00:01:00.320> very<00:01:00.519> proud<00:01:00.760> of<00:01:01.039> every 00:01:01.880 --> 00:01:01.890 align:start position:0% them a hand and I'm very proud of every 00:01:01.890 --> 00:01:08.280 align:start position:0% them a hand and I'm very proud of every [Music] 00:01:08.280 --> 00:01:08.290 align:start position:0% [Music] 00:01:08.290 --> 00:01:10.149 align:start position:0% [Music] [Applause] 00:01:10.149 --> 00:01:10.159 align:start position:0% [Applause] 00:01:10.159 --> 00:01:13.230 align:start position:0% [Applause] that<00:01:11.159> so<00:01:11.520> without<00:01:11.880> further<00:01:12.320> Ado<00:01:12.680> we<00:01:12.799> have<00:01:12.960> a 00:01:13.230 --> 00:01:13.240 align:start position:0% that so without further Ado we have a 00:01:13.240 --> 00:01:15.550 align:start position:0% that so without further Ado we have a very<00:01:13.720> full<00:01:14.119> schedule<00:01:14.600> I'll<00:01:14.799> go<00:01:14.960> ahead<00:01:15.200> and<00:01:15.320> let 00:01:15.550 --> 00:01:15.560 align:start position:0% very full schedule I'll go ahead and let 00:01:15.560 --> 00:01:19.109 align:start position:0% very full schedule I'll go ahead and let vitalic<00:01:16.119> start<00:01:17.000> and<00:01:17.600> um<00:01:17.799> in<00:01:17.960> the<00:01:18.240> spirit<00:01:18.759> of 00:01:19.109 --> 00:01:19.119 align:start position:0% vitalic start and um in the spirit of 00:01:19.119 --> 00:01:22.069 align:start position:0% vitalic start and um in the spirit of our<00:01:19.560> kind<00:01:19.720> of<00:01:20.000> autonomous<00:01:21.079> decentralized 00:01:22.069 --> 00:01:22.079 align:start position:0% our kind of autonomous decentralized 00:01:22.079 --> 00:01:24.870 align:start position:0% our kind of autonomous decentralized Tech<00:01:22.520> and<00:01:23.079> decentralized<00:01:23.799> Technologies<00:01:24.799> I 00:01:24.870 --> 00:01:24.880 align:start position:0% Tech and decentralized Technologies I 00:01:24.880 --> 00:01:26.630 align:start position:0% Tech and decentralized Technologies I have<00:01:25.040> not<00:01:25.159> been<00:01:25.360> able<00:01:25.560> to<00:01:25.680> pin<00:01:25.960> down<00:01:26.240> exactly 00:01:26.630 --> 00:01:26.640 align:start position:0% have not been able to pin down exactly 00:01:26.640 --> 00:01:27.910 align:start position:0% have not been able to pin down exactly what<00:01:26.759> they're<00:01:26.920> going<00:01:27.000> to<00:01:27.159> say<00:01:27.400> but<00:01:27.520> I'm<00:01:27.640> sure 00:01:27.910 --> 00:01:27.920 align:start position:0% what they're going to say but I'm sure 00:01:27.920 --> 00:01:29.590 align:start position:0% what they're going to say but I'm sure what<00:01:28.040> they<00:01:28.159> will<00:01:28.360> say<00:01:28.560> will<00:01:28.720> be<00:01:28.880> of<00:01:29.040> great 00:01:29.590 --> 00:01:29.600 align:start position:0% what they will say will be of great 00:01:29.600 --> 00:01:31.429 align:start position:0% what they will say will be of great interest<00:01:29.880> interest<00:01:30.119> and<00:01:30.320> value<00:01:30.720> and<00:01:30.840> it'll<00:01:31.079> be 00:01:31.429 --> 00:01:31.439 align:start position:0% interest interest and value and it'll be 00:01:31.439 --> 00:01:33.469 align:start position:0% interest interest and value and it'll be an<00:01:31.680> open<00:01:31.960> format<00:01:32.439> so<00:01:32.720> you<00:01:32.880> will<00:01:33.040> be<00:01:33.159> able<00:01:33.320> to 00:01:33.469 --> 00:01:33.479 align:start position:0% an open format so you will be able to 00:01:33.479 --> 00:01:38.830 align:start position:0% an open format so you will be able to ask<00:01:33.680> some<00:01:33.920> questions<00:01:34.840> thank 00:01:38.830 --> 00:01:38.840 align:start position:0% 00:01:38.840 --> 00:01:42.350 align:start position:0% you<00:01:39.840> oh<00:01:40.520> I<00:01:40.759> I<00:01:40.840> did<00:01:40.960> want<00:01:41.079> to<00:01:41.240> say<00:01:41.399> at<00:01:41.560> the<00:01:41.720> end<00:01:42.079> of 00:01:42.350 --> 00:01:42.360 align:start position:0% you oh I I did want to say at the end of 00:01:42.360 --> 00:01:45.429 align:start position:0% you oh I I did want to say at the end of the<00:01:42.840> uh<00:01:43.240> presentation<00:01:44.240> Alex 00:01:45.429 --> 00:01:45.439 align:start position:0% the uh presentation Alex 00:01:45.439 --> 00:01:48.709 align:start position:0% the uh presentation Alex vanaand<00:01:46.439> our<00:01:47.000> uh<00:01:47.320> lead<00:01:47.680> designer<00:01:48.320> will<00:01:48.479> be 00:01:48.709 --> 00:01:48.719 align:start position:0% vanaand our uh lead designer will be 00:01:48.719 --> 00:01:51.749 align:start position:0% vanaand our uh lead designer will be talking<00:01:49.119> about<00:01:49.719> mist<00:01:50.119> and<00:01:50.360> wallet<00:01:50.960> on<00:01:51.119> the 00:01:51.749 --> 00:01:51.759 align:start position:0% talking about mist and wallet on the 00:01:51.759 --> 00:02:17.910 align:start position:0% talking about mist and wallet on the blockchain<00:01:52.759> okay<00:01:53.000> thank<00:01:53.159> you 00:02:17.910 --> 00:02:17.920 align:start position:0% 00:02:17.920 --> 00:02:20.350 align:start position:0% so<00:02:18.840> this<00:02:18.959> is<00:02:19.120> a<00:02:19.319> live<00:02:19.599> example<00:02:20.000> of<00:02:20.160> why 00:02:20.350 --> 00:02:20.360 align:start position:0% so this is a live example of why 00:02:20.360 --> 00:02:21.949 align:start position:0% so this is a live example of why decentralized<00:02:21.000> internet<00:02:21.360> technology<00:02:21.800> is 00:02:21.949 --> 00:02:21.959 align:start position:0% decentralized internet technology is 00:02:21.959 --> 00:02:37.990 align:start position:0% decentralized internet technology is useful 00:02:37.990 --> 00:02:38.000 align:start position:0% 00:02:38.000 --> 00:02:40.030 align:start position:0% okay<00:02:38.280> fine 00:02:40.030 --> 00:02:40.040 align:start position:0% okay fine 00:02:40.040 --> 00:02:42.830 align:start position:0% okay fine so<00:02:41.040> I<00:02:41.200> guess<00:02:41.599> I<00:02:41.680> am<00:02:41.920> what<00:02:42.040> I'm<00:02:42.200> going<00:02:42.319> to<00:02:42.519> start 00:02:42.830 --> 00:02:42.840 align:start position:0% so I guess I am what I'm going to start 00:02:42.840 --> 00:02:45.070 align:start position:0% so I guess I am what I'm going to start off<00:02:43.120> with<00:02:43.519> is<00:02:43.959> basically<00:02:44.480> you<00:02:44.599> know<00:02:44.720> start<00:02:44.959> off 00:02:45.070 --> 00:02:45.080 align:start position:0% off with is basically you know start off 00:02:45.080 --> 00:02:46.110 align:start position:0% off with is basically you know start off the<00:02:45.200> conference<00:02:45.599> by<00:02:45.720> talking<00:02:46.000> about 00:02:46.110 --> 00:02:46.120 align:start position:0% the conference by talking about 00:02:46.120 --> 00:02:49.589 align:start position:0% the conference by talking about ethereum's<00:02:46.760> future<00:02:47.760> so<00:02:48.760> project<00:02:49.200> has<00:02:49.360> been 00:02:49.589 --> 00:02:49.599 align:start position:0% ethereum's future so project has been 00:02:49.599 --> 00:02:54.589 align:start position:0% ethereum's future so project has been around<00:02:50.239> now<00:02:50.920> for<00:02:51.920> about<00:02:52.920> 2<00:02:53.360> years<00:02:53.959> minus<00:02:54.400> six 00:02:54.589 --> 00:02:54.599 align:start position:0% around now for about 2 years minus six 00:02:54.599 --> 00:02:56.710 align:start position:0% around now for about 2 years minus six or<00:02:54.800> seven<00:02:55.159> days<00:02:55.560> since<00:02:55.800> I<00:02:55.959> first<00:02:56.360> wrote<00:02:56.599> the 00:02:56.710 --> 00:02:56.720 align:start position:0% or seven days since I first wrote the 00:02:56.720 --> 00:02:59.190 align:start position:0% or seven days since I first wrote the ethereum<00:02:57.159> white<00:02:57.400> paper<00:02:58.319> and<00:02:58.599> since<00:02:58.920> then<00:02:59.080> it 00:02:59.190 --> 00:02:59.200 align:start position:0% ethereum white paper and since then it 00:02:59.200 --> 00:03:00.470 align:start position:0% ethereum white paper and since then it has<00:02:59.360> gone<00:02:59.560> through 00:03:00.470 --> 00:03:00.480 align:start position:0% has gone through 00:03:00.480 --> 00:03:02.830 align:start position:0% has gone through very<00:03:00.720> many<00:03:01.000> iterations<00:03:01.800> going<00:03:02.159> from<00:03:02.360> the<00:03:02.560> very 00:03:02.830 --> 00:03:02.840 align:start position:0% very many iterations going from the very 00:03:02.840 --> 00:03:06.190 align:start position:0% very many iterations going from the very first<00:03:03.239> version<00:03:03.879> which<00:03:04.879> Gavin<00:03:05.360> very<00:03:05.959> very 00:03:06.190 --> 00:03:06.200 align:start position:0% first version which Gavin very very 00:03:06.200 --> 00:03:08.350 align:start position:0% first version which Gavin very very quickly<00:03:06.640> and<00:03:06.920> and<00:03:07.120> effectively<00:03:07.519> coded<00:03:07.920> up<00:03:08.159> way 00:03:08.350 --> 00:03:08.360 align:start position:0% quickly and and effectively coded up way 00:03:08.360 --> 00:03:12.270 align:start position:0% quickly and and effectively coded up way back<00:03:08.480> in<00:03:08.680> the<00:03:08.840> in<00:03:09.000> those<00:03:09.480> days<00:03:09.640> in<00:03:10.159> Miami 00:03:12.270 --> 00:03:12.280 align:start position:0% back in the in those days in Miami 00:03:12.280 --> 00:03:15.550 align:start position:0% back in the in those days in Miami through<00:03:13.280> 10<00:03:13.599> proof<00:03:13.799> of<00:03:14.000> concept<00:03:14.400> iterations<00:03:15.400> A 00:03:15.550 --> 00:03:15.560 align:start position:0% through 10 proof of concept iterations A 00:03:15.560 --> 00:03:18.949 align:start position:0% through 10 proof of concept iterations A Crowd<00:03:16.000> sale<00:03:16.879> a<00:03:17.280> Defcon<00:03:17.840> zero<00:03:18.319> which<00:03:18.480> consisted 00:03:18.949 --> 00:03:18.959 align:start position:0% Crowd sale a Defcon zero which consisted 00:03:18.959 --> 00:03:21.710 align:start position:0% Crowd sale a Defcon zero which consisted of<00:03:19.440> of<00:03:19.560> a<00:03:19.720> rather<00:03:20.040> small<00:03:20.400> event<00:03:20.799> consisting<00:03:21.319> of 00:03:21.710 --> 00:03:21.720 align:start position:0% of of a rather small event consisting of 00:03:21.720 --> 00:03:24.789 align:start position:0% of of a rather small event consisting of e<00:03:22.480> all<00:03:22.720> the<00:03:22.799> ethereum<00:03:23.280> developers<00:03:24.000> in<00:03:24.239> an 00:03:24.789 --> 00:03:24.799 align:start position:0% e all the ethereum developers in an 00:03:24.799 --> 00:03:27.630 align:start position:0% e all the ethereum developers in an huddle<00:03:25.280> together<00:03:25.480> in<00:03:25.599> an<00:03:25.799> office<00:03:26.040> in<00:03:26.640> Berlin 00:03:27.630 --> 00:03:27.640 align:start position:0% huddle together in an office in Berlin 00:03:27.640 --> 00:03:31.990 align:start position:0% huddle together in an office in Berlin finally<00:03:28.439> after<00:03:29.879> 16<00:03:30.640> 16<00:03:31.080> months<00:03:31.400> to<00:03:31.560> launch<00:03:31.799> of 00:03:31.990 --> 00:03:32.000 align:start position:0% finally after 16 16 months to launch of 00:03:32.000 --> 00:03:35.470 align:start position:0% finally after 16 16 months to launch of FR<00:03:32.439> Frontier<00:03:33.120> back<00:03:33.319> in<00:03:33.680> at<00:03:33.760> the<00:03:33.879> end<00:03:34.040> of<00:03:34.480> July 00:03:35.470 --> 00:03:35.480 align:start position:0% FR Frontier back in at the end of July 00:03:35.480 --> 00:03:39.110 align:start position:0% FR Frontier back in at the end of July and<00:03:36.239> here<00:03:36.400> we<00:03:36.519> are<00:03:36.760> now<00:03:37.239> you<00:03:37.599> know<00:03:38.599> 3<00:03:38.840> months 00:03:39.110 --> 00:03:39.120 align:start position:0% and here we are now you know 3 months 00:03:39.120 --> 00:03:40.589 align:start position:0% and here we are now you know 3 months after<00:03:39.280> the<00:03:39.400> frontier<00:03:39.799> launch<00:03:40.120> fairly<00:03:40.400> close 00:03:40.589 --> 00:03:40.599 align:start position:0% after the frontier launch fairly close 00:03:40.599 --> 00:03:44.429 align:start position:0% after the frontier launch fairly close to<00:03:40.760> Homestead<00:03:41.560> so<00:03:42.560> what<00:03:42.680> comes<00:03:43.000> after<00:03:43.319> this<00:03:44.159> so 00:03:44.429 --> 00:03:44.439 align:start position:0% to Homestead so what comes after this so 00:03:44.439 --> 00:03:45.910 align:start position:0% to Homestead so what comes after this so the<00:03:44.599> first<00:03:44.840> thing<00:03:45.120> that<00:03:45.280> I<00:03:45.360> think<00:03:45.519> a<00:03:45.599> lot<00:03:45.760> of 00:03:45.910 --> 00:03:45.920 align:start position:0% the first thing that I think a lot of 00:03:45.920 --> 00:03:48.229 align:start position:0% the first thing that I think a lot of people<00:03:46.120> have<00:03:46.280> been<00:03:46.439> waiting<00:03:46.720> for<00:03:47.120> is<00:03:47.920> when 00:03:48.229 --> 00:03:48.239 align:start position:0% people have been waiting for is when 00:03:48.239 --> 00:03:51.429 align:start position:0% people have been waiting for is when exactly<00:03:48.799> is<00:03:49.080> Homestead<00:03:49.560> going<00:03:49.720> to<00:03:49.920> come 00:03:51.429 --> 00:03:51.439 align:start position:0% exactly is Homestead going to come 00:03:51.439 --> 00:03:54.589 align:start position:0% exactly is Homestead going to come so<00:03:52.439> the<00:03:52.640> simple<00:03:53.599> the<00:03:53.760> sort<00:03:53.879> of<00:03:54.000> simple<00:03:54.319> answer 00:03:54.589 --> 00:03:54.599 align:start position:0% so the simple the sort of simple answer 00:03:54.599 --> 00:03:57.350 align:start position:0% so the simple the sort of simple answer to<00:03:54.799> this<00:03:55.000> is<00:03:55.360> hopefully<00:03:55.760> fairly<00:03:56.159> soon<00:03:57.079> uh<00:03:57.200> the 00:03:57.350 --> 00:03:57.360 align:start position:0% to this is hopefully fairly soon uh the 00:03:57.360 --> 00:03:59.990 align:start position:0% to this is hopefully fairly soon uh the more<00:03:57.599> sort<00:03:57.799> of<00:03:58.360> elaborate<00:03:58.879> answer<00:03:59.200> is<00:03:59.480> that 00:03:59.990 --> 00:04:00.000 align:start position:0% more sort of elaborate answer is that 00:04:00.000 --> 00:04:01.630 align:start position:0% more sort of elaborate answer is that originally<00:04:00.560> when<00:04:00.680> we<00:04:00.879> came<00:04:01.040> up<00:04:01.239> with<00:04:01.480> that 00:04:01.630 --> 00:04:01.640 align:start position:0% originally when we came up with that 00:04:01.640 --> 00:04:04.350 align:start position:0% originally when we came up with that whole<00:04:01.840> schedule<00:04:02.360> with<00:04:02.480> the<00:04:02.640> four<00:04:03.040> stages<00:04:04.040> we 00:04:04.350 --> 00:04:04.360 align:start position:0% whole schedule with the four stages we 00:04:04.360 --> 00:04:07.270 align:start position:0% whole schedule with the four stages we had<00:04:04.599> that<00:04:04.840> idea<00:04:05.360> back<00:04:05.760> around<00:04:06.319> March<00:04:06.640> 1st<00:04:07.079> when 00:04:07.270 --> 00:04:07.280 align:start position:0% had that idea back around March 1st when 00:04:07.280 --> 00:04:09.069 align:start position:0% had that idea back around March 1st when we<00:04:07.560> actually<00:04:07.840> we<00:04:08.040> thought<00:04:08.239> that<00:04:08.400> Frontier<00:04:08.920> was 00:04:09.069 --> 00:04:09.079 align:start position:0% we actually we thought that Frontier was 00:04:09.079 --> 00:04:11.670 align:start position:0% we actually we thought that Frontier was going<00:04:09.200> to<00:04:09.360> launch<00:04:09.720> in<00:04:09.920> a<00:04:10.680> much<00:04:10.959> more<00:04:11.360> kind<00:04:11.480> of 00:04:11.670 --> 00:04:11.680 align:start position:0% going to launch in a much more kind of 00:04:11.680 --> 00:04:15.069 align:start position:0% going to launch in a much more kind of raw<00:04:12.159> form<00:04:13.079> and<00:04:14.079> probably<00:04:14.439> with<00:04:14.840> with<00:04:14.959> a 00:04:15.069 --> 00:04:15.079 align:start position:0% raw form and probably with with a 00:04:15.079 --> 00:04:17.150 align:start position:0% raw form and probably with with a network<00:04:15.400> that<00:04:15.519> doesn't<00:04:15.799> work<00:04:16.120> quite<00:04:16.639> quite<00:04:16.919> as 00:04:17.150 --> 00:04:17.160 align:start position:0% network that doesn't work quite quite as 00:04:17.160 --> 00:04:19.629 align:start position:0% network that doesn't work quite quite as well<00:04:17.680> and<00:04:18.040> and<00:04:18.239> much<00:04:18.400> earlier<00:04:18.840> and<00:04:19.359> and<00:04:19.519> much 00:04:19.629 --> 00:04:19.639 align:start position:0% well and and much earlier and and much 00:04:19.639 --> 00:04:22.430 align:start position:0% well and and much earlier and and much more<00:04:19.840> minimal<00:04:20.759> instead<00:04:21.239> for<00:04:21.919> a<00:04:22.079> bunch<00:04:22.240> of 00:04:22.430 --> 00:04:22.440 align:start position:0% more minimal instead for a bunch of 00:04:22.440 --> 00:04:24.189 align:start position:0% more minimal instead for a bunch of reasons<00:04:22.880> that<00:04:23.000> ended<00:04:23.280> up<00:04:23.440> not<00:04:23.639> happening<00:04:24.080> we 00:04:24.189 --> 00:04:24.199 align:start position:0% reasons that ended up not happening we 00:04:24.199 --> 00:04:25.790 align:start position:0% reasons that ended up not happening we ended<00:04:24.400> up<00:04:24.560> launching<00:04:24.840> for<00:04:25.160> year<00:04:25.400> quite<00:04:25.520> a<00:04:25.639> bit 00:04:25.790 --> 00:04:25.800 align:start position:0% ended up launching for year quite a bit 00:04:25.800 --> 00:04:29.790 align:start position:0% ended up launching for year quite a bit later<00:04:26.639> and<00:04:26.840> so<00:04:27.800> we're<00:04:28.680> at<00:04:28.840> the<00:04:29.080> stage<00:04:29.560> where 00:04:29.790 --> 00:04:29.800 align:start position:0% later and so we're at the stage where 00:04:29.800 --> 00:04:32.550 align:start position:0% later and so we're at the stage where where<00:04:30.520> most<00:04:30.840> of<00:04:31.000> the<00:04:31.199> pieces<00:04:31.880> well<00:04:32.120> almost<00:04:32.440> all 00:04:32.550 --> 00:04:32.560 align:start position:0% where most of the pieces well almost all 00:04:32.560 --> 00:04:35.029 align:start position:0% where most of the pieces well almost all of<00:04:32.680> the<00:04:32.800> pieces<00:04:33.160> that<00:04:33.280> we<00:04:33.400> had<00:04:33.600> expected<00:04:34.080> to<00:04:34.240> be 00:04:35.029 --> 00:04:35.039 align:start position:0% of the pieces that we had expected to be 00:04:35.039 --> 00:04:36.629 align:start position:0% of the pieces that we had expected to be around<00:04:35.560> at<00:04:35.680> the<00:04:35.800> time<00:04:35.919> of<00:04:36.080> Homestead 00:04:36.629 --> 00:04:36.639 align:start position:0% around at the time of Homestead 00:04:36.639 --> 00:04:40.310 align:start position:0% around at the time of Homestead basically<00:04:37.280> are<00:04:37.520> around<00:04:38.520> so<00:04:39.520> the<00:04:39.720> go<00:04:40.039> client 00:04:40.310 --> 00:04:40.320 align:start position:0% basically are around so the go client 00:04:40.320 --> 00:04:42.790 align:start position:0% basically are around so the go client was<00:04:40.479> launched<00:04:41.080> at<00:04:42.000> made<00:04:42.199> available<00:04:42.600> at<00:04:42.720> the 00:04:42.790 --> 00:04:42.800 align:start position:0% was launched at made available at the 00:04:42.800 --> 00:04:45.510 align:start position:0% was launched at made available at the end<00:04:42.960> of<00:04:43.160> July<00:04:43.680> since<00:04:43.960> then<00:04:44.120> the<00:04:44.240> C++<00:04:45.039> client 00:04:45.510 --> 00:04:45.520 align:start position:0% end of July since then the C++ client 00:04:45.520 --> 00:04:48.150 align:start position:0% end of July since then the C++ client and<00:04:45.960> the<00:04:46.600> python<00:04:47.000> client<00:04:47.440> have<00:04:47.680> both<00:04:47.919> gone 00:04:48.150 --> 00:04:48.160 align:start position:0% and the python client have both gone 00:04:48.160 --> 00:04:50.590 align:start position:0% and the python client have both gone through<00:04:48.400> security<00:04:48.800> audits<00:04:49.639> uh<00:04:49.759> C<00:04:50.080> the<00:04:50.280> version 00:04:50.590 --> 00:04:50.600 align:start position:0% through security audits uh C the version 00:04:50.600 --> 00:04:53.230 align:start position:0% through security audits uh C the version 1.0<00:04:51.120> of<00:04:51.240> C++<00:04:51.960> has<00:04:52.080> I<00:04:52.199> Believe<00:04:52.400> been<00:04:52.600> released 00:04:53.230 --> 00:04:53.240 align:start position:0% 1.0 of C++ has I Believe been released 00:04:53.240 --> 00:04:56.749 align:start position:0% 1.0 of C++ has I Believe been released very<00:04:53.479> recently<00:04:53.919> I<00:04:54.039> it<00:04:54.160> was<00:04:54.400> last<00:04:54.919> week<00:04:55.919> and<00:04:56.639> you 00:04:56.749 --> 00:04:56.759 align:start position:0% very recently I it was last week and you 00:04:56.759 --> 00:04:59.270 align:start position:0% very recently I it was last week and you know<00:04:56.960> Asa<00:04:57.320> has<00:04:57.520> done<00:04:57.800> a<00:04:57.960> lot<00:04:58.120> of<00:04:58.720> and<00:04:59.000> others 00:04:59.270 --> 00:04:59.280 align:start position:0% know Asa has done a lot of and others 00:04:59.280 --> 00:05:00.909 align:start position:0% know Asa has done a lot of and others have<00:04:59.440> done<00:04:59.720> a<00:04:59.800> lot<00:04:59.919> of<00:05:00.000> wonderful<00:05:00.400> work<00:05:00.680> on 00:05:00.909 --> 00:05:00.919 align:start position:0% have done a lot of wonderful work on 00:05:00.919 --> 00:05:03.310 align:start position:0% have done a lot of wonderful work on getting<00:05:01.400> the<00:05:02.039> wallet<00:05:02.600> which<00:05:02.720> is<00:05:02.880> kind<00:05:03.000> of<00:05:03.160> like 00:05:03.310 --> 00:05:03.320 align:start position:0% getting the wallet which is kind of like 00:05:03.320 --> 00:05:05.469 align:start position:0% getting the wallet which is kind of like the<00:05:03.520> very<00:05:03.800> first<00:05:04.080> sort<00:05:04.240> of<00:05:04.360> minimal<00:05:05.360> well 00:05:05.469 --> 00:05:05.479 align:start position:0% the very first sort of minimal well 00:05:05.479 --> 00:05:07.029 align:start position:0% the very first sort of minimal well what's<00:05:05.680> going<00:05:05.840> to<00:05:06.000> end<00:05:06.199> up<00:05:06.400> being<00:05:06.680> the<00:05:06.840> very 00:05:07.029 --> 00:05:07.039 align:start position:0% what's going to end up being the very 00:05:07.039 --> 00:05:08.870 align:start position:0% what's going to end up being the very first<00:05:07.280> kind<00:05:07.400> of<00:05:07.520> minimum<00:05:07.960> viable<00:05:08.360> product<00:05:08.600> for 00:05:08.870 --> 00:05:08.880 align:start position:0% first kind of minimum viable product for 00:05:08.880 --> 00:05:11.510 align:start position:0% first kind of minimum viable product for mist<00:05:09.880> out<00:05:10.400> and<00:05:10.639> that's<00:05:10.880> available<00:05:11.199> for<00:05:11.360> people 00:05:11.510 --> 00:05:11.520 align:start position:0% mist out and that's available for people 00:05:11.520 --> 00:05:14.790 align:start position:0% mist out and that's available for people to<00:05:11.680> use<00:05:11.960> already<00:05:12.840> so<00:05:13.759> the<00:05:13.919> sort<00:05:14.080> of<00:05:14.280> Milestone 00:05:14.790 --> 00:05:14.800 align:start position:0% to use already so the sort of Milestone 00:05:14.800 --> 00:05:16.110 align:start position:0% to use already so the sort of Milestone that<00:05:14.880> we're<00:05:15.080> waiting<00:05:15.320> for<00:05:15.639> before<00:05:15.880> we<00:05:16.000> can 00:05:16.110 --> 00:05:16.120 align:start position:0% that we're waiting for before we can 00:05:16.120 --> 00:05:17.749 align:start position:0% that we're waiting for before we can launch<00:05:16.440> Homestead<00:05:16.960> is<00:05:17.199> basically<00:05:17.600> the 00:05:17.749 --> 00:05:17.759 align:start position:0% launch Homestead is basically the 00:05:17.759 --> 00:05:20.749 align:start position:0% launch Homestead is basically the Milestone<00:05:18.319> where<00:05:18.960> the<00:05:19.160> network<00:05:20.039> the<00:05:20.199> entire 00:05:20.749 --> 00:05:20.759 align:start position:0% Milestone where the network the entire 00:05:20.759 --> 00:05:23.070 align:start position:0% Milestone where the network the entire ethereum<00:05:21.240> network<00:05:21.639> you<00:05:21.759> know 00:05:23.070 --> 00:05:23.080 align:start position:0% ethereum network you know 00:05:23.080 --> 00:05:25.749 align:start position:0% ethereum network you know miners<00:05:24.080> all<00:05:24.199> of<00:05:24.319> the<00:05:24.440> sort<00:05:24.600> of<00:05:24.720> critical<00:05:25.199> stuff 00:05:25.749 --> 00:05:25.759 align:start position:0% miners all of the sort of critical stuff 00:05:25.759 --> 00:05:28.230 align:start position:0% miners all of the sort of critical stuff works<00:05:26.479> without<00:05:26.880> serious<00:05:27.319> hiccups<00:05:27.880> without 00:05:28.230 --> 00:05:28.240 align:start position:0% works without serious hiccups without 00:05:28.240 --> 00:05:30.390 align:start position:0% works without serious hiccups without without<00:05:28.479> interruptions<00:05:29.039> for<00:05:29.199> 4<00:05:29.400> weeks 00:05:30.390 --> 00:05:30.400 align:start position:0% without interruptions for 4 weeks 00:05:30.400 --> 00:05:31.909 align:start position:0% without interruptions for 4 weeks so<00:05:30.840> you<00:05:30.960> know<00:05:31.080> it's<00:05:31.240> basically<00:05:31.639> just<00:05:31.759> a 00:05:31.909 --> 00:05:31.919 align:start position:0% so you know it's basically just a 00:05:31.919 --> 00:05:34.629 align:start position:0% so you know it's basically just a counter<00:05:32.680> keeps<00:05:32.880> on<00:05:33.080> incrementing<00:05:34.039> and<00:05:34.520> you 00:05:34.629 --> 00:05:34.639 align:start position:0% counter keeps on incrementing and you 00:05:34.639 --> 00:05:36.710 align:start position:0% counter keeps on incrementing and you know<00:05:34.840> at<00:05:35.000> some<00:05:35.240> point<00:05:36.120> there<00:05:36.360> have<00:05:36.520> been 00:05:36.710 --> 00:05:36.720 align:start position:0% know at some point there have been 00:05:36.720 --> 00:05:38.390 align:start position:0% know at some point there have been issues<00:05:37.000> with<00:05:37.120> the<00:05:37.280> network<00:05:37.680> the<00:05:37.840> most<00:05:38.080> recent 00:05:38.390 --> 00:05:38.400 align:start position:0% issues with the network the most recent 00:05:38.400 --> 00:05:40.070 align:start position:0% issues with the network the most recent one<00:05:38.639> has<00:05:38.759> been<00:05:39.000> that<00:05:39.199> fork<00:05:39.639> because<00:05:39.840> of<00:05:39.960> a 00:05:40.070 --> 00:05:40.080 align:start position:0% one has been that fork because of a 00:05:40.080 --> 00:05:42.469 align:start position:0% one has been that fork because of a block<00:05:40.440> of<00:05:40.560> a<00:05:40.639> block<00:05:40.960> has<00:05:41.199> issue<00:05:41.479> that<00:05:41.600> we<00:05:41.800> had 00:05:42.469 --> 00:05:42.479 align:start position:0% block of a block has issue that we had 00:05:42.479 --> 00:05:44.070 align:start position:0% block of a block has issue that we had around<00:05:42.759> two<00:05:42.919> to<00:05:43.080> three<00:05:43.280> weeks<00:05:43.479> ago<00:05:43.720> at<00:05:43.840> the<00:05:43.919> end 00:05:44.070 --> 00:05:44.080 align:start position:0% around two to three weeks ago at the end 00:05:44.080 --> 00:05:47.070 align:start position:0% around two to three weeks ago at the end of<00:05:44.280> October<00:05:45.280> so<00:05:45.840> you<00:05:45.960> know<00:05:46.160> if<00:05:46.280> all<00:05:46.520> goes<00:05:46.800> well 00:05:47.070 --> 00:05:47.080 align:start position:0% of October so you know if all goes well 00:05:47.080 --> 00:05:48.710 align:start position:0% of October so you know if all goes well Homestead<00:05:47.680> theoretically<00:05:48.199> should<00:05:48.520> come 00:05:48.710 --> 00:05:48.720 align:start position:0% Homestead theoretically should come 00:05:48.720 --> 00:05:51.309 align:start position:0% Homestead theoretically should come fairly<00:05:49.120> soon<00:05:50.000> but<00:05:50.240> of<00:05:50.400> course<00:05:50.720> anything<00:05:51.080> can 00:05:51.309 --> 00:05:51.319 align:start position:0% fairly soon but of course anything can 00:05:51.319 --> 00:05:53.110 align:start position:0% fairly soon but of course anything can happen<00:05:51.960> you<00:05:52.080> know<00:05:52.319> technical<00:05:52.720> issues<00:05:52.960> are 00:05:53.110 --> 00:05:53.120 align:start position:0% happen you know technical issues are 00:05:53.120 --> 00:05:55.710 align:start position:0% happen you know technical issues are with<00:05:53.319> technical<00:05:53.720> issues<00:05:54.039> are<00:05:54.919> and<00:05:55.479> you<00:05:55.600> know 00:05:55.710 --> 00:05:55.720 align:start position:0% with technical issues are and you know 00:05:55.720 --> 00:05:57.350 align:start position:0% with technical issues are and you know we'd<00:05:55.960> rather<00:05:56.240> launch<00:05:56.600> Homestead<00:05:57.039> when<00:05:57.160> we're 00:05:57.350 --> 00:05:57.360 align:start position:0% we'd rather launch Homestead when we're 00:05:57.360 --> 00:05:58.870 align:start position:0% we'd rather launch Homestead when we're actually<00:05:57.680> confident<00:05:58.160> that<00:05:58.319> that<00:05:58.440> the<00:05:58.520> network 00:05:58.870 --> 00:05:58.880 align:start position:0% actually confident that that the network 00:05:58.880 --> 00:06:00.430 align:start position:0% actually confident that that the network is<00:05:59.120> is<00:05:59.240> safe<00:05:59.479> and<00:05:59.639> instead<00:05:59.880> of<00:05:59.960> sticking<00:06:00.280> to 00:06:00.430 --> 00:06:00.440 align:start position:0% is is safe and instead of sticking to 00:06:00.440 --> 00:06:04.590 align:start position:0% is is safe and instead of sticking to any<00:06:00.639> particular<00:06:01.319> deadline<00:06:02.360> so<00:06:03.360> after<00:06:03.720> that 00:06:04.590 --> 00:06:04.600 align:start position:0% any particular deadline so after that 00:06:04.600 --> 00:06:07.790 align:start position:0% any particular deadline so after that Metropolis<00:06:05.400> that's<00:06:05.560> going<00:06:05.680> to<00:06:05.840> focus<00:06:06.120> on<00:06:06.800> Mist 00:06:07.790 --> 00:06:07.800 align:start position:0% Metropolis that's going to focus on Mist 00:06:07.800 --> 00:06:09.230 align:start position:0% Metropolis that's going to focus on Mist beyond<00:06:08.199> that<00:06:08.360> there's<00:06:08.599> four<00:06:08.880> primary 00:06:09.230 --> 00:06:09.240 align:start position:0% beyond that there's four primary 00:06:09.240 --> 00:06:11.390 align:start position:0% beyond that there's four primary research<00:06:09.639> directions<00:06:10.360> that<00:06:10.759> we're<00:06:11.039> taking 00:06:11.390 --> 00:06:11.400 align:start position:0% research directions that we're taking 00:06:11.400 --> 00:06:15.309 align:start position:0% research directions that we're taking for<00:06:12.000> 2.0<00:06:13.000> so<00:06:13.680> the<00:06:13.840> first<00:06:14.120> one<00:06:14.360> is<00:06:14.720> Casper<00:06:15.240> the 00:06:15.309 --> 00:06:15.319 align:start position:0% for 2.0 so the first one is Casper the 00:06:15.319 --> 00:06:16.909 align:start position:0% for 2.0 so the first one is Casper the proof<00:06:15.520> of<00:06:15.639> stake<00:06:15.960> algorithm<00:06:16.560> and<00:06:16.680> that<00:06:16.800> is 00:06:16.909 --> 00:06:16.919 align:start position:0% proof of stake algorithm and that is 00:06:16.919 --> 00:06:18.189 align:start position:0% proof of stake algorithm and that is something<00:06:17.160> that<00:06:17.319> Vlad<00:06:17.639> is<00:06:17.759> going<00:06:17.880> to<00:06:18.000> be 00:06:18.189 --> 00:06:18.199 align:start position:0% something that Vlad is going to be 00:06:18.199 --> 00:06:20.510 align:start position:0% something that Vlad is going to be talking<00:06:18.520> about<00:06:19.319> actually<00:06:19.599> immediately<00:06:20.160> after 00:06:20.510 --> 00:06:20.520 align:start position:0% talking about actually immediately after 00:06:20.520 --> 00:06:22.710 align:start position:0% talking about actually immediately after this<00:06:21.160> so<00:06:21.759> you<00:06:21.880> know<00:06:22.120> from<00:06:22.280> a<00:06:22.440> sort<00:06:22.599> of 00:06:22.710 --> 00:06:22.720 align:start position:0% this so you know from a sort of 00:06:22.720 --> 00:06:24.029 align:start position:0% this so you know from a sort of philosophical<00:06:23.280> standpoint<00:06:23.720> there's<00:06:23.880> no 00:06:24.029 --> 00:06:24.039 align:start position:0% philosophical standpoint there's no 00:06:24.039 --> 00:06:25.710 align:start position:0% philosophical standpoint there's no reason<00:06:24.319> why<00:06:24.440> we<00:06:24.560> can't<00:06:24.840> consider<00:06:25.160> Vlad<00:06:25.560> part 00:06:25.710 --> 00:06:25.720 align:start position:0% reason why we can't consider Vlad part 00:06:25.720 --> 00:06:27.110 align:start position:0% reason why we can't consider Vlad part of<00:06:25.840> this<00:06:26.000> keynote<00:06:26.400> because<00:06:26.560> everyone<00:06:26.800> else<00:06:26.960> is 00:06:27.110 --> 00:06:27.120 align:start position:0% of this keynote because everyone else is 00:06:27.120 --> 00:06:31.790 align:start position:0% of this keynote because everyone else is presenting<00:06:27.520> here<00:06:28.120> anyway<00:06:29.120> um<00:06:29.960> the<00:06:30.160> SEC<00:06:30.599> so<00:06:31.599> the 00:06:31.790 --> 00:06:31.800 align:start position:0% presenting here anyway um the SEC so the 00:06:31.800 --> 00:06:34.629 align:start position:0% presenting here anyway um the SEC so the second<00:06:32.240> part<00:06:32.680> is<00:06:33.199> uh<00:06:33.400> scalability<00:06:34.400> so 00:06:34.629 --> 00:06:34.639 align:start position:0% second part is uh scalability so 00:06:34.639 --> 00:06:37.110 align:start position:0% second part is uh scalability so scalability<00:06:35.440> this<00:06:35.720> idea<00:06:36.319> of<00:06:36.560> coming<00:06:36.800> up<00:06:37.000> with 00:06:37.110 --> 00:06:37.120 align:start position:0% scalability this idea of coming up with 00:06:37.120 --> 00:06:40.150 align:start position:0% scalability this idea of coming up with a<00:06:37.240> blockchain<00:06:37.919> that<00:06:38.080> can<00:06:38.880> scale<00:06:39.440> much<00:06:39.720> larger 00:06:40.150 --> 00:06:40.160 align:start position:0% a blockchain that can scale much larger 00:06:40.160 --> 00:06:42.909 align:start position:0% a blockchain that can scale much larger than<00:06:40.400> existing<00:06:40.800> chains<00:06:41.360> essentially<00:06:42.120> by 00:06:42.909 --> 00:06:42.919 align:start position:0% than existing chains essentially by 00:06:42.919 --> 00:06:45.870 align:start position:0% than existing chains essentially by processing<00:06:43.440> transactions<00:06:44.039> in<00:06:44.400> parallel<00:06:45.400> and 00:06:45.870 --> 00:06:45.880 align:start position:0% processing transactions in parallel and 00:06:45.880 --> 00:06:48.670 align:start position:0% processing transactions in parallel and by<00:06:46.080> moving<00:06:46.680> away<00:06:47.039> from<00:06:47.319> this<00:06:47.520> Paradigm<00:06:48.120> where 00:06:48.670 --> 00:06:48.680 align:start position:0% by moving away from this Paradigm where 00:06:48.680 --> 00:06:50.189 align:start position:0% by moving away from this Paradigm where absolutely<00:06:49.280> every<00:06:49.479> single<00:06:49.759> node<00:06:50.000> in<00:06:50.080> the 00:06:50.189 --> 00:06:50.199 align:start position:0% absolutely every single node in the 00:06:50.199 --> 00:06:52.670 align:start position:0% absolutely every single node in the network<00:06:50.599> has<00:06:50.720> to<00:06:50.919> process<00:06:51.280> every<00:06:51.680> transaction 00:06:52.670 --> 00:06:52.680 align:start position:0% network has to process every transaction 00:06:52.680 --> 00:06:55.390 align:start position:0% network has to process every transaction so<00:06:53.400> there<00:06:53.680> are<00:06:54.319> a<00:06:54.479> number<00:06:54.759> of<00:06:54.919> different<00:06:55.199> ways 00:06:55.390 --> 00:06:55.400 align:start position:0% so there are a number of different ways 00:06:55.400 --> 00:06:57.710 align:start position:0% so there are a number of different ways to<00:06:55.560> do<00:06:55.759> that<00:06:55.919> we'll<00:06:56.120> be<00:06:56.280> hearing<00:06:56.759> about<00:06:57.479> quite 00:06:57.710 --> 00:06:57.720 align:start position:0% to do that we'll be hearing about quite 00:06:57.720 --> 00:06:59.830 align:start position:0% to do that we'll be hearing about quite a<00:06:57.879> lot<00:06:58.039> of<00:06:58.160> the<00:06:58.319> different<00:06:58.639> strategies<00:06:59.120> for 00:06:59.830 --> 00:06:59.840 align:start position:0% a lot of the different strategies for 00:06:59.840 --> 00:07:04.189 align:start position:0% a lot of the different strategies for people<00:07:00.840> uh<00:07:01.199> throughout<00:07:01.599> this<00:07:01.759> week<00:07:02.720> but<00:07:02.960> it 00:07:04.189 --> 00:07:04.199 align:start position:0% people uh throughout this week but it 00:07:04.199 --> 00:07:07.990 align:start position:0% people uh throughout this week but it is<00:07:05.199> I<00:07:05.360> think<00:07:05.720> probably<00:07:06.240> the<00:07:06.560> single<00:07:07.560> single 00:07:07.990 --> 00:07:08.000 align:start position:0% is I think probably the single single 00:07:08.000 --> 00:07:10.589 align:start position:0% is I think probably the single single technical<00:07:08.479> thing<00:07:08.919> that's<00:07:09.919> right<00:07:10.080> now<00:07:10.280> holding 00:07:10.589 --> 00:07:10.599 align:start position:0% technical thing that's right now holding 00:07:10.599 --> 00:07:12.189 align:start position:0% technical thing that's right now holding blockchain<00:07:11.080> technology<00:07:11.560> back<00:07:11.720> for<00:07:11.919> me<00:07:12.080> for 00:07:12.189 --> 00:07:12.199 align:start position:0% blockchain technology back for me for 00:07:12.199 --> 00:07:13.790 align:start position:0% blockchain technology back for me for mainstream<00:07:12.639> adoption<00:07:13.080> even<00:07:13.280> more<00:07:13.400> so<00:07:13.639> than 00:07:13.790 --> 00:07:13.800 align:start position:0% mainstream adoption even more so than 00:07:13.800 --> 00:07:16.830 align:start position:0% mainstream adoption even more so than anything<00:07:14.280> else<00:07:15.280> Z<00:07:15.720> Stark<00:07:16.039> integration<00:07:16.599> so 00:07:16.830 --> 00:07:16.840 align:start position:0% anything else Z Stark integration so 00:07:16.840 --> 00:07:20.150 align:start position:0% anything else Z Stark integration so this<00:07:17.039> covers<00:07:17.440> the<00:07:17.639> other<00:07:18.080> big<00:07:18.560> problem<00:07:19.560> with 00:07:20.150 --> 00:07:20.160 align:start position:0% this covers the other big problem with 00:07:20.160 --> 00:07:22.390 align:start position:0% this covers the other big problem with blockchains<00:07:20.879> that<00:07:21.039> makes<00:07:21.280> it<00:07:21.520> unsatisfactory 00:07:22.390 --> 00:07:22.400 align:start position:0% blockchains that makes it unsatisfactory 00:07:22.400 --> 00:07:24.309 align:start position:0% blockchains that makes it unsatisfactory for<00:07:22.560> at<00:07:22.680> least<00:07:22.840> some<00:07:23.000> use<00:07:23.319> cases<00:07:23.720> which<00:07:23.919> is 00:07:24.309 --> 00:07:24.319 align:start position:0% for at least some use cases which is 00:07:24.319 --> 00:07:27.189 align:start position:0% for at least some use cases which is privacy<00:07:25.319> so<00:07:26.080> you<00:07:26.199> know<00:07:26.520> companies<00:07:26.919> they're 00:07:27.189 --> 00:07:27.199 align:start position:0% privacy so you know companies they're 00:07:27.199 --> 00:07:28.510 align:start position:0% privacy so you know companies they're interested<00:07:27.520> in<00:07:27.639> blockchains<00:07:28.120> they<00:07:28.280> love 00:07:28.510 --> 00:07:28.520 align:start position:0% interested in blockchains they love 00:07:28.520 --> 00:07:30.270 align:start position:0% interested in blockchains they love blockchains<00:07:29.199> yay<00:07:29.520> it's<00:07:29.639> the<00:07:29.720> new<00:07:29.840> buzzword 00:07:30.270 --> 00:07:30.280 align:start position:0% blockchains yay it's the new buzzword 00:07:30.280 --> 00:07:32.990 align:start position:0% blockchains yay it's the new buzzword it's<00:07:30.440> the<00:07:30.759> future<00:07:31.759> wait<00:07:32.199> you're<00:07:32.440> saying<00:07:32.800> we 00:07:32.990 --> 00:07:33.000 align:start position:0% it's the future wait you're saying we 00:07:33.000 --> 00:07:35.150 align:start position:0% it's the future wait you're saying we have<00:07:33.120> to<00:07:33.560> publish<00:07:34.120> each<00:07:34.319> and<00:07:34.520> every<00:07:34.759> one<00:07:35.000> of 00:07:35.150 --> 00:07:35.160 align:start position:0% have to publish each and every one of 00:07:35.160 --> 00:07:37.189 align:start position:0% have to publish each and every one of our<00:07:35.479> transactions<00:07:36.160> to<00:07:36.319> a<00:07:36.479> public<00:07:36.800> database 00:07:37.189 --> 00:07:37.199 align:start position:0% our transactions to a public database 00:07:37.199 --> 00:07:39.390 align:start position:0% our transactions to a public database that<00:07:37.319> could<00:07:37.479> be<00:07:37.599> read<00:07:37.879> by<00:07:38.000> our 00:07:39.390 --> 00:07:39.400 align:start position:0% that could be read by our 00:07:39.400 --> 00:07:42.589 align:start position:0% that could be read by our competitors<00:07:40.400> so<00:07:41.160> you<00:07:41.280> know<00:07:41.479> the<00:07:41.639> question<00:07:42.000> is 00:07:42.589 --> 00:07:42.599 align:start position:0% competitors so you know the question is 00:07:42.599 --> 00:07:44.990 align:start position:0% competitors so you know the question is how<00:07:42.840> can<00:07:42.960> you<00:07:43.280> have<00:07:44.039> the<00:07:44.199> benefits<00:07:44.720> of<00:07:44.879> the 00:07:44.990 --> 00:07:45.000 align:start position:0% how can you have the benefits of the 00:07:45.000 --> 00:07:47.670 align:start position:0% how can you have the benefits of the transparency<00:07:45.840> of<00:07:46.000> the<00:07:46.280> the<00:07:46.400> public<00:07:47.080> nature<00:07:47.520> of 00:07:47.670 --> 00:07:47.680 align:start position:0% transparency of the the public nature of 00:07:47.680 --> 00:07:50.830 align:start position:0% transparency of the the public nature of the<00:07:48.000> blockchain<00:07:49.080> without<00:07:50.080> compromising<00:07:50.639> your 00:07:50.830 --> 00:07:50.840 align:start position:0% the blockchain without compromising your 00:07:50.840 --> 00:07:52.990 align:start position:0% the blockchain without compromising your privacy<00:07:51.840> and<00:07:51.960> there's<00:07:52.199> this<00:07:52.360> wonderful<00:07:52.759> area 00:07:52.990 --> 00:07:53.000 align:start position:0% privacy and there's this wonderful area 00:07:53.000 --> 00:07:54.510 align:start position:0% privacy and there's this wonderful area of<00:07:53.080> cryptography<00:07:53.680> called<00:07:53.879> zero<00:07:54.159> knowledge 00:07:54.510 --> 00:07:54.520 align:start position:0% of cryptography called zero knowledge 00:07:54.520 --> 00:07:58.110 align:start position:0% of cryptography called zero knowledge proofs<00:07:55.520> that<00:07:55.879> basically<00:07:56.599> is<00:07:56.879> able<00:07:57.199> to<00:07:57.599> somehow 00:07:58.110 --> 00:07:58.120 align:start position:0% proofs that basically is able to somehow 00:07:58.120 --> 00:08:00.589 align:start position:0% proofs that basically is able to somehow magically<00:07:59.039> use<00:07:59.560> a<00:07:59.639> bunch<00:07:59.800> of<00:07:59.919> algorithms 00:08:00.589 --> 00:08:00.599 align:start position:0% magically use a bunch of algorithms 00:08:00.599 --> 00:08:02.990 align:start position:0% magically use a bunch of algorithms invol<00:08:01.319> involving<00:08:01.759> mathematical<00:08:02.400> transforms 00:08:02.990 --> 00:08:03.000 align:start position:0% invol involving mathematical transforms 00:08:03.000 --> 00:08:07.110 align:start position:0% invol involving mathematical transforms on<00:08:03.199> binary<00:08:03.599> circuits<00:08:04.039> do<00:08:04.280> exactly<00:08:04.879> that<00:08:06.120> so 00:08:07.110 --> 00:08:07.120 align:start position:0% on binary circuits do exactly that so 00:08:07.120 --> 00:08:08.990 align:start position:0% on binary circuits do exactly that so that's<00:08:07.560> we<00:08:07.680> know<00:08:08.080> we've<00:08:08.240> been<00:08:08.400> talking<00:08:08.680> to 00:08:08.990 --> 00:08:09.000 align:start position:0% that's we know we've been talking to 00:08:09.000 --> 00:08:10.469 align:start position:0% that's we know we've been talking to some<00:08:09.120> of<00:08:09.240> the<00:08:09.400> groups<00:08:09.720> that<00:08:09.800> are<00:08:10.199> that<00:08:10.280> are 00:08:10.469 --> 00:08:10.479 align:start position:0% some of the groups that are that are 00:08:10.479 --> 00:08:14.909 align:start position:0% some of the groups that are that are developing<00:08:11.520> um<00:08:12.599> zase<00:08:13.599> zase<00:08:14.080> Nar<00:08:14.400> technology 00:08:14.909 --> 00:08:14.919 align:start position:0% developing um zase zase Nar technology 00:08:14.919 --> 00:08:17.270 align:start position:0% developing um zase zase Nar technology there's<00:08:15.159> a<00:08:15.400> project<00:08:15.879> called<00:08:16.120> zeroc<00:08:16.599> cach 00:08:17.270 --> 00:08:17.280 align:start position:0% there's a project called zeroc cach 00:08:17.280 --> 00:08:18.550 align:start position:0% there's a project called zeroc cach that's<00:08:17.479> going<00:08:17.599> to<00:08:17.720> be<00:08:17.840> coming<00:08:18.039> out<00:08:18.199> fairly 00:08:18.550 --> 00:08:18.560 align:start position:0% that's going to be coming out fairly 00:08:18.560 --> 00:08:20.390 align:start position:0% that's going to be coming out fairly soon<00:08:18.919> that's<00:08:19.120> basically<00:08:19.479> going<00:08:19.639> to<00:08:19.800> be 00:08:20.390 --> 00:08:20.400 align:start position:0% soon that's basically going to be 00:08:20.400 --> 00:08:23.270 align:start position:0% soon that's basically going to be putting<00:08:20.720> ZK<00:08:21.199> Starks<00:08:22.120> into<00:08:22.440> a<00:08:22.599> Bitcoin<00:08:23.080> like 00:08:23.270 --> 00:08:23.280 align:start position:0% putting ZK Starks into a Bitcoin like 00:08:23.280 --> 00:08:25.629 align:start position:0% putting ZK Starks into a Bitcoin like cryptocurrency<00:08:24.120> in<00:08:24.199> order<00:08:24.479> to<00:08:25.039> provide<00:08:25.440> much 00:08:25.629 --> 00:08:25.639 align:start position:0% cryptocurrency in order to provide much 00:08:25.639 --> 00:08:27.790 align:start position:0% cryptocurrency in order to provide much higher<00:08:25.879> degrees<00:08:26.199> of<00:08:26.520> privacy<00:08:27.520> but<00:08:27.680> then 00:08:27.790 --> 00:08:27.800 align:start position:0% higher degrees of privacy but then 00:08:27.800 --> 00:08:29.790 align:start position:0% higher degrees of privacy but then there's<00:08:28.120> also<00:08:28.479> you<00:08:28.560> know<00:08:28.879> many<00:08:29.159> other<00:08:29.560> many 00:08:29.790 --> 00:08:29.800 align:start position:0% there's also you know many other many 00:08:29.800 --> 00:08:31.909 align:start position:0% there's also you know many other many other<00:08:30.080> applications<00:08:30.639> of<00:08:30.879> privacy<00:08:31.400> ranging 00:08:31.909 --> 00:08:31.919 align:start position:0% other applications of privacy ranging 00:08:31.919 --> 00:08:35.110 align:start position:0% other applications of privacy ranging from<00:08:32.560> you<00:08:32.680> know<00:08:32.959> things<00:08:33.399> like<00:08:34.200> proving 00:08:35.110 --> 00:08:35.120 align:start position:0% from you know things like proving 00:08:35.120 --> 00:08:37.709 align:start position:0% from you know things like proving proving<00:08:35.560> that<00:08:35.760> you<00:08:35.919> are<00:08:36.440> a<00:08:36.919> a<00:08:37.080> reliable<00:08:37.560> and 00:08:37.709 --> 00:08:37.719 align:start position:0% proving that you are a a reliable and 00:08:37.719 --> 00:08:39.790 align:start position:0% proving that you are a a reliable and trustworthy<00:08:38.320> person<00:08:39.000> by<00:08:39.279> some<00:08:39.479> kind<00:08:39.599> of 00:08:39.790 --> 00:08:39.800 align:start position:0% trustworthy person by some kind of 00:08:39.800 --> 00:08:42.070 align:start position:0% trustworthy person by some kind of reputation<00:08:40.360> metric<00:08:40.919> or<00:08:41.479> you<00:08:41.599> know<00:08:41.760> some<00:08:41.959> kind 00:08:42.070 --> 00:08:42.080 align:start position:0% reputation metric or you know some kind 00:08:42.080 --> 00:08:44.350 align:start position:0% reputation metric or you know some kind of<00:08:42.440> identity<00:08:42.880> registry<00:08:43.440> system<00:08:43.959> without 00:08:44.350 --> 00:08:44.360 align:start position:0% of identity registry system without 00:08:44.360 --> 00:08:46.070 align:start position:0% of identity registry system without actually<00:08:44.720> revealing<00:08:45.240> what<00:08:45.360> your<00:08:45.640> specific 00:08:46.070 --> 00:08:46.080 align:start position:0% actually revealing what your specific 00:08:46.080 --> 00:08:50.470 align:start position:0% actually revealing what your specific name<00:08:46.519> is<00:08:47.880> and<00:08:48.880> sort<00:08:49.120> of<00:08:49.320> figuring<00:08:49.800> those 00:08:50.470 --> 00:08:50.480 align:start position:0% name is and sort of figuring those 00:08:50.480 --> 00:08:52.230 align:start position:0% name is and sort of figuring those figuring<00:08:50.839> out<00:08:51.200> applications<00:08:51.760> of<00:08:51.959> that<00:08:52.120> and 00:08:52.230 --> 00:08:52.240 align:start position:0% figuring out applications of that and 00:08:52.240 --> 00:08:54.310 align:start position:0% figuring out applications of that and figuring<00:08:52.600> out<00:08:52.959> how<00:08:53.120> to<00:08:53.519> integrate<00:08:53.959> that<00:08:54.080> into 00:08:54.310 --> 00:08:54.320 align:start position:0% figuring out how to integrate that into 00:08:54.320 --> 00:08:57.550 align:start position:0% figuring out how to integrate that into ethereum<00:08:55.080> is<00:08:55.959> one<00:08:56.160> of<00:08:56.640> uh<00:08:56.880> our<00:08:57.160> primary 00:08:57.550 --> 00:08:57.560 align:start position:0% ethereum is one of uh our primary 00:08:57.560 --> 00:09:00.310 align:start position:0% ethereum is one of uh our primary focuses<00:08:58.440> finally<00:08:58.839> number<00:08:59.079> four<00:08:59.880> upgrading 00:09:00.310 --> 00:09:00.320 align:start position:0% focuses finally number four upgrading 00:09:00.320 --> 00:09:03.990 align:start position:0% focuses finally number four upgrading the<00:09:00.440> ethereum<00:09:00.839> virtual<00:09:01.240> machine<00:09:02.519> so<00:09:03.519> a<00:09:03.680> lot<00:09:03.839> of 00:09:03.990 --> 00:09:04.000 align:start position:0% the ethereum virtual machine so a lot of 00:09:04.000 --> 00:09:07.069 align:start position:0% the ethereum virtual machine so a lot of the<00:09:04.160> design<00:09:04.519> decisions<00:09:05.120> that<00:09:05.320> we<00:09:05.640> had<00:09:06.160> um<00:09:06.399> at 00:09:07.069 --> 00:09:07.079 align:start position:0% the design decisions that we had um at 00:09:07.079 --> 00:09:10.829 align:start position:0% the design decisions that we had um at at<00:09:07.200> the<00:09:07.399> time<00:09:08.279> such<00:09:08.519> as<00:09:08.680> you<00:09:08.839> know<00:09:09.519> 32<00:09:10.120> 32<00:09:10.560> byte 00:09:10.829 --> 00:09:10.839 align:start position:0% at the time such as you know 32 32 byte 00:09:10.839 --> 00:09:13.470 align:start position:0% at the time such as you know 32 32 byte registers<00:09:11.600> memory<00:09:12.079> stack<00:09:12.880> all<00:09:13.079> the<00:09:13.200> sort<00:09:13.360> of 00:09:13.470 --> 00:09:13.480 align:start position:0% registers memory stack all the sort of 00:09:13.480 --> 00:09:16.110 align:start position:0% registers memory stack all the sort of really<00:09:13.680> low<00:09:13.959> Lev<00:09:14.240> details<00:09:15.160> came<00:09:15.440> up<00:09:15.600> with<00:09:15.800> that 00:09:16.110 --> 00:09:16.120 align:start position:0% really low Lev details came up with that 00:09:16.120 --> 00:09:18.870 align:start position:0% really low Lev details came up with that back<00:09:16.320> in<00:09:16.480> the<00:09:16.640> beginning<00:09:16.959> of<00:09:17.160> 2014<00:09:18.120> when<00:09:18.720> the 00:09:18.870 --> 00:09:18.880 align:start position:0% back in the beginning of 2014 when the 00:09:18.880 --> 00:09:21.350 align:start position:0% back in the beginning of 2014 when the design<00:09:19.320> requirements<00:09:20.040> looked<00:09:20.519> much<00:09:20.720> simpler 00:09:21.350 --> 00:09:21.360 align:start position:0% design requirements looked much simpler 00:09:21.360 --> 00:09:24.269 align:start position:0% design requirements looked much simpler than<00:09:21.720> the<00:09:22.480> than<00:09:22.640> they<00:09:22.760> are<00:09:23.000> now<00:09:23.720> so<00:09:23.920> you<00:09:24.000> know 00:09:24.269 --> 00:09:24.279 align:start position:0% than the than they are now so you know 00:09:24.279 --> 00:09:26.150 align:start position:0% than the than they are now so you know back<00:09:24.519> initially<00:09:25.120> I<00:09:25.240> thought<00:09:25.440> that<00:09:25.600> ethereum 00:09:26.150 --> 00:09:26.160 align:start position:0% back initially I thought that ethereum 00:09:26.160 --> 00:09:28.350 align:start position:0% back initially I thought that ethereum was<00:09:26.360> a<00:09:26.560> thing<00:09:26.800> that<00:09:26.920> would<00:09:27.040> be<00:09:27.240> used<00:09:27.600> for 00:09:28.350 --> 00:09:28.360 align:start position:0% was a thing that would be used for 00:09:28.360 --> 00:09:30.829 align:start position:0% was a thing that would be used for people<00:09:28.640> to<00:09:28.880> write<00:09:29.079> simple<00:09:29.519> Financial<00:09:29.959> scripts 00:09:30.829 --> 00:09:30.839 align:start position:0% people to write simple Financial scripts 00:09:30.839 --> 00:09:32.470 align:start position:0% people to write simple Financial scripts as<00:09:30.920> it<00:09:31.079> turns<00:09:31.360> out<00:09:31.680> people<00:09:31.920> are<00:09:32.120> you<00:09:32.240> know 00:09:32.470 --> 00:09:32.480 align:start position:0% as it turns out people are you know 00:09:32.480 --> 00:09:34.990 align:start position:0% as it turns out people are you know writing<00:09:32.959> stuff<00:09:33.320> like<00:09:34.079> stuff<00:09:34.279> like<00:09:34.440> augur<00:09:34.800> on 00:09:34.990 --> 00:09:35.000 align:start position:0% writing stuff like stuff like augur on 00:09:35.000 --> 00:09:37.509 align:start position:0% writing stuff like stuff like augur on top<00:09:35.160> of<00:09:35.320> it<00:09:35.839> and<00:09:36.000> so<00:09:36.760> you<00:09:36.839> know<00:09:37.000> figuring<00:09:37.360> out 00:09:37.509 --> 00:09:37.519 align:start position:0% top of it and so you know figuring out 00:09:37.519 --> 00:09:38.630 align:start position:0% top of it and so you know figuring out how<00:09:37.640> to<00:09:37.839> like 00:09:38.630 --> 00:09:38.640 align:start position:0% how to like 00:09:38.640 --> 00:09:41.269 align:start position:0% how to like really<00:09:39.640> make<00:09:40.360> make<00:09:40.519> the<00:09:40.640> virtual<00:09:40.959> machine 00:09:41.269 --> 00:09:41.279 align:start position:0% really make make the virtual machine 00:09:41.279 --> 00:09:43.630 align:start position:0% really make make the virtual machine more<00:09:41.480> efficient<00:09:41.959> is<00:09:42.360> uh<00:09:42.880> also<00:09:43.160> something<00:09:43.519> that 00:09:43.630 --> 00:09:43.640 align:start position:0% more efficient is uh also something that 00:09:43.640 --> 00:09:46.710 align:start position:0% more efficient is uh also something that we're<00:09:44.079> going<00:09:44.240> to<00:09:44.320> be<00:09:44.519> discussing<00:09:45.519> this<00:09:45.720> week 00:09:46.710 --> 00:09:46.720 align:start position:0% we're going to be discussing this week 00:09:46.720 --> 00:09:49.630 align:start position:0% we're going to be discussing this week so<00:09:47.720> with<00:09:48.040> that<00:09:48.480> I<00:09:48.600> think<00:09:48.880> we're<00:09:49.079> going<00:09:49.240> to<00:09:49.399> move 00:09:49.630 --> 00:09:49.640 align:start position:0% so with that I think we're going to move 00:09:49.640 --> 00:09:52.230 align:start position:0% so with that I think we're going to move on<00:09:49.800> to<00:09:50.200> uh<00:09:50.440> Jeff<00:09:50.959> and<00:09:51.399> Alex<00:09:51.760> we're<00:09:51.920> going<00:09:52.000> to<00:09:52.120> be 00:09:52.230 --> 00:09:52.240 align:start position:0% on to uh Jeff and Alex we're going to be 00:09:52.240 --> 00:09:54.670 align:start position:0% on to uh Jeff and Alex we're going to be giving<00:09:53.000> their<00:09:53.240> updates<00:09:53.920> and<00:09:54.279> uh<00:09:54.399> talking 00:09:54.670 --> 00:09:54.680 align:start position:0% giving their updates and uh talking 00:09:54.680 --> 00:09:58.360 align:start position:0% giving their updates and uh talking about<00:09:54.839> the<00:09:54.920> wallet<00:09:55.200> and<00:09:55.320> mist 00:09:58.360 --> 00:09:58.370 align:start position:0% 00:09:58.370 --> 00:10:04.920 align:start position:0% [Applause] 00:10:04.920 --> 00:10:04.930 align:start position:0% 00:10:04.930 --> 00:10:20.110 align:start position:0% [Applause] 00:10:20.110 --> 00:10:20.120 align:start position:0% 00:10:20.120 --> 00:10:22.670 align:start position:0% all<00:10:20.240> right<00:10:20.440> hi<00:10:20.680> guys<00:10:21.360> um<00:10:21.959> so<00:10:22.120> for<00:10:22.320> those<00:10:22.440> of<00:10:22.560> you 00:10:22.670 --> 00:10:22.680 align:start position:0% all right hi guys um so for those of you 00:10:22.680 --> 00:10:25.710 align:start position:0% all right hi guys um so for those of you who<00:10:22.800> don't<00:10:23.000> know<00:10:23.600> um<00:10:23.800> I'm<00:10:24.000> Jeff<00:10:24.959> I<00:10:25.079> am<00:10:25.560> the 00:10:25.710 --> 00:10:25.720 align:start position:0% who don't know um I'm Jeff I am the 00:10:25.720 --> 00:10:28.230 align:start position:0% who don't know um I'm Jeff I am the original<00:10:26.720> um<00:10:27.000> author<00:10:27.360> of<00:10:27.560> The<00:10:28.000> Go 00:10:28.230 --> 00:10:28.240 align:start position:0% original um author of The Go 00:10:28.240 --> 00:10:30.550 align:start position:0% original um author of The Go implementation<00:10:29.720> and<00:10:29.920> what<00:10:30.079> I<00:10:30.160> would<00:10:30.320> like<00:10:30.440> to 00:10:30.550 --> 00:10:30.560 align:start position:0% implementation and what I would like to 00:10:30.560 --> 00:10:32.710 align:start position:0% implementation and what I would like to talk<00:10:30.720> to<00:10:30.839> you<00:10:30.959> about<00:10:31.160> today<00:10:31.480> is<00:10:31.720> the<00:10:32.160> uh<00:10:32.600> the 00:10:32.710 --> 00:10:32.720 align:start position:0% talk to you about today is the uh the 00:10:32.720 --> 00:10:36.230 align:start position:0% talk to you about today is the uh the road<00:10:33.079> map<00:10:33.880> for<00:10:34.160> go<00:10:34.360> ethereum 00:10:36.230 --> 00:10:36.240 align:start position:0% road map for go ethereum 00:10:36.240 --> 00:10:39.750 align:start position:0% road map for go ethereum itself<00:10:37.240> um<00:10:38.160> because<00:10:39.160> most<00:10:39.360> of<00:10:39.480> you<00:10:39.600> are 00:10:39.750 --> 00:10:39.760 align:start position:0% itself um because most of you are 00:10:39.760 --> 00:10:43.230 align:start position:0% itself um because most of you are running<00:10:40.760> um<00:10:41.279> go<00:10:41.560> ethereum<00:10:41.920> or<00:10:42.040> you<00:10:42.120> know<00:10:42.279> it<00:10:42.399> as 00:10:43.230 --> 00:10:43.240 align:start position:0% running um go ethereum or you know it as 00:10:43.240 --> 00:10:46.069 align:start position:0% running um go ethereum or you know it as G<00:10:44.240> it<00:10:44.399> has<00:10:44.839> most<00:10:45.279> part<00:10:45.399> of<00:10:45.519> the<00:10:45.720> current 00:10:46.069 --> 00:10:46.079 align:start position:0% G it has most part of the current 00:10:46.079 --> 00:10:49.030 align:start position:0% G it has most part of the current Network<00:10:47.079> um<00:10:47.760> which<00:10:47.880> is<00:10:48.079> something<00:10:48.560> that<00:10:48.880> that 00:10:49.030 --> 00:10:49.040 align:start position:0% Network um which is something that that 00:10:49.040 --> 00:10:50.310 align:start position:0% Network um which is something that that the<00:10:49.160> whole<00:10:49.360> team<00:10:49.560> needs<00:10:49.760> to<00:10:49.880> address<00:10:50.200> because 00:10:50.310 --> 00:10:50.320 align:start position:0% the whole team needs to address because 00:10:50.320 --> 00:10:53.670 align:start position:0% the whole team needs to address because we<00:10:50.440> need<00:10:50.560> to<00:10:50.639> get<00:10:50.800> some<00:10:51.000> more<00:10:52.240> diversity<00:10:53.240> um 00:10:53.670 --> 00:10:53.680 align:start position:0% we need to get some more diversity um 00:10:53.680 --> 00:10:55.550 align:start position:0% we need to get some more diversity um hopefully<00:10:54.279> Gavin<00:10:54.600> can<00:10:54.800> speak<00:10:55.079> about<00:10:55.360> that 00:10:55.550 --> 00:10:55.560 align:start position:0% hopefully Gavin can speak about that 00:10:55.560 --> 00:10:59.750 align:start position:0% hopefully Gavin can speak about that perhaps<00:10:55.839> in<00:10:56.079> his<00:10:56.639> uh<00:10:57.639> uh<00:10:58.120> his<00:10:58.320> update<00:10:58.680> on<00:10:58.880> on<00:10:59.000> C 00:10:59.750 --> 00:10:59.760 align:start position:0% perhaps in his uh uh his update on on C 00:10:59.760 --> 00:11:01.590 align:start position:0% perhaps in his uh uh his update on on C p+ 00:11:01.590 --> 00:11:01.600 align:start position:0% p+ 00:11:01.600 --> 00:11:03.710 align:start position:0% p+ um<00:11:02.600> so<00:11:02.800> one<00:11:02.880> of<00:11:03.000> the<00:11:03.120> first<00:11:03.320> thing<00:11:03.519> that<00:11:03.639> we 00:11:03.710 --> 00:11:03.720 align:start position:0% um so one of the first thing that we 00:11:03.720 --> 00:11:06.710 align:start position:0% um so one of the first thing that we need<00:11:03.880> to<00:11:04.079> address<00:11:05.040> is<00:11:05.600> uh<00:11:05.760> the<00:11:06.279> sorry<00:11:06.560> that's 00:11:06.710 --> 00:11:06.720 align:start position:0% need to address is uh the sorry that's 00:11:06.720 --> 00:11:10.670 align:start position:0% need to address is uh the sorry that's the<00:11:06.839> wrong<00:11:07.440> slide<00:11:08.440> is<00:11:08.959> um<00:11:09.120> splitting<00:11:09.519> up<00:11:09.760> gu<00:11:10.480> So 00:11:10.670 --> 00:11:10.680 align:start position:0% the wrong slide is um splitting up gu So 00:11:10.680 --> 00:11:12.790 align:start position:0% the wrong slide is um splitting up gu So currently<00:11:11.040> it<00:11:11.240> has<00:11:11.440> two<00:11:11.680> components<00:11:12.600> uh<00:11:12.680> one 00:11:12.790 --> 00:11:12.800 align:start position:0% currently it has two components uh one 00:11:12.800 --> 00:11:14.629 align:start position:0% currently it has two components uh one of<00:11:12.920> them<00:11:13.079> is<00:11:13.279> the<00:11:13.519> is<00:11:13.639> the<00:11:13.760> node<00:11:14.120> and<00:11:14.279> and<00:11:14.440> one 00:11:14.629 --> 00:11:14.639 align:start position:0% of them is the is the node and and one 00:11:14.639 --> 00:11:17.389 align:start position:0% of them is the is the node and and one part<00:11:14.880> is<00:11:15.079> is<00:11:15.200> the<00:11:15.680> client<00:11:16.680> um<00:11:17.000> and<00:11:17.160> as<00:11:17.279> it 00:11:17.389 --> 00:11:17.399 align:start position:0% part is is the client um and as it 00:11:17.399 --> 00:11:19.710 align:start position:0% part is is the client um and as it stands<00:11:17.839> currently<00:11:18.279> today<00:11:18.720> is<00:11:19.000> it<00:11:19.200> it's<00:11:19.560> it's 00:11:19.710 --> 00:11:19.720 align:start position:0% stands currently today is it it's it's 00:11:19.720 --> 00:11:21.590 align:start position:0% stands currently today is it it's it's more<00:11:19.839> or<00:11:20.000> less<00:11:20.120> one<00:11:20.240> and<00:11:20.399> the<00:11:20.560> same<00:11:21.160> and<00:11:21.480> what 00:11:21.590 --> 00:11:21.600 align:start position:0% more or less one and the same and what 00:11:21.600 --> 00:11:22.829 align:start position:0% more or less one and the same and what we<00:11:21.720> want<00:11:21.800> to<00:11:21.920> do<00:11:22.079> is<00:11:22.200> we<00:11:22.279> want<00:11:22.399> to<00:11:22.639> want<00:11:22.720> to 00:11:22.829 --> 00:11:22.839 align:start position:0% we want to do is we want to want to 00:11:22.839 --> 00:11:25.750 align:start position:0% we want to do is we want to want to split<00:11:23.160> out<00:11:23.360> the<00:11:23.480> two<00:11:23.760> components<00:11:24.720> into<00:11:25.279> into<00:11:25.519> a 00:11:25.750 --> 00:11:25.760 align:start position:0% split out the two components into into a 00:11:25.760 --> 00:11:29.509 align:start position:0% split out the two components into into a node<00:11:26.040> and<00:11:26.160> a<00:11:26.560> client<00:11:27.560> um<00:11:27.959> because 00:11:29.509 --> 00:11:29.519 align:start position:0% node and a client um because 00:11:29.519 --> 00:11:32.910 align:start position:0% node and a client um because a<00:11:29.720> node<00:11:30.200> is<00:11:30.440> nothing<00:11:30.760> more<00:11:31.040> than<00:11:31.279> just<00:11:31.639> a<00:11:32.440> uh<00:11:32.720> a 00:11:32.910 --> 00:11:32.920 align:start position:0% a node is nothing more than just a uh a 00:11:32.920 --> 00:11:36.110 align:start position:0% a node is nothing more than just a uh a system<00:11:33.279> in<00:11:33.480> which<00:11:33.639> you<00:11:33.800> can<00:11:34.240> uh<00:11:34.800> interface<00:11:35.800> um 00:11:36.110 --> 00:11:36.120 align:start position:0% system in which you can uh interface um 00:11:36.120 --> 00:11:40.350 align:start position:0% system in which you can uh interface um and<00:11:36.399> which<00:11:36.560> you<00:11:36.760> can<00:11:37.399> subscribe<00:11:38.240> certain<00:11:39.279> uh 00:11:40.350 --> 00:11:40.360 align:start position:0% and which you can subscribe certain uh 00:11:40.360 --> 00:11:43.470 align:start position:0% and which you can subscribe certain uh um<00:11:41.360> sub<00:11:41.720> protocols<00:11:42.279> like<00:11:42.519> like 00:11:43.470 --> 00:11:43.480 align:start position:0% um sub protocols like like 00:11:43.480 --> 00:11:45.110 align:start position:0% um sub protocols like like ethereum<00:11:44.480> just<00:11:44.639> going<00:11:44.720> to<00:11:44.839> drop<00:11:45.040> the 00:11:45.110 --> 00:11:45.120 align:start position:0% ethereum just going to drop the 00:11:45.120 --> 00:11:46.670 align:start position:0% ethereum just going to drop the microphone<00:11:45.480> on<00:11:45.560> the 00:11:46.670 --> 00:11:46.680 align:start position:0% microphone on the 00:11:46.680 --> 00:11:50.829 align:start position:0% microphone on the floor<00:11:47.680> sorry<00:11:47.920> I<00:11:48.000> was<00:11:48.120> giving<00:11:48.360> some<00:11:48.560> feedback 00:11:50.829 --> 00:11:50.839 align:start position:0% floor sorry I was giving some feedback 00:11:50.839 --> 00:11:53.790 align:start position:0% floor sorry I was giving some feedback um<00:11:51.839> so<00:11:52.200> one<00:11:52.320> of<00:11:52.480> the<00:11:52.680> for<00:11:52.839> example<00:11:53.160> one<00:11:53.320> of<00:11:53.480> the 00:11:53.790 --> 00:11:53.800 align:start position:0% um so one of the for example one of the 00:11:53.800 --> 00:11:55.389 align:start position:0% um so one of the for example one of the uh<00:11:53.920> one<00:11:54.040> of<00:11:54.200> the<00:11:54.480> one<00:11:54.560> of<00:11:54.680> the<00:11:54.800> subsystems 00:11:55.389 --> 00:11:55.399 align:start position:0% uh one of the one of the subsystems 00:11:55.399 --> 00:11:58.230 align:start position:0% uh one of the one of the subsystems could<00:11:55.560> be<00:11:55.959> ethereum<00:11:56.480> itself<00:11:57.160> uh<00:11:57.360> whisper 00:11:58.230 --> 00:11:58.240 align:start position:0% could be ethereum itself uh whisper 00:11:58.240 --> 00:12:01.829 align:start position:0% could be ethereum itself uh whisper swarm<00:11:59.279> uh<00:11:59.440> or<00:11:59.680> the<00:12:00.040> or<00:12:00.160> the<00:12:00.279> light<00:12:00.680> client<00:12:01.680> um 00:12:01.829 --> 00:12:01.839 align:start position:0% swarm uh or the or the light client um 00:12:01.839 --> 00:12:03.870 align:start position:0% swarm uh or the or the light client um something<00:12:02.120> about<00:12:02.360> that<00:12:02.519> later<00:12:03.480> um<00:12:03.639> and<00:12:03.760> the 00:12:03.870 --> 00:12:03.880 align:start position:0% something about that later um and the 00:12:03.880 --> 00:12:05.389 align:start position:0% something about that later um and the other<00:12:04.079> part<00:12:04.200> of<00:12:04.320> the<00:12:04.440> application<00:12:04.959> is<00:12:05.120> is<00:12:05.240> the 00:12:05.389 --> 00:12:05.399 align:start position:0% other part of the application is is the 00:12:05.399 --> 00:12:07.310 align:start position:0% other part of the application is is the client<00:12:05.720> itself<00:12:06.360> something<00:12:06.720> that<00:12:06.959> that's 00:12:07.310 --> 00:12:07.320 align:start position:0% client itself something that that's 00:12:07.320 --> 00:12:10.030 align:start position:0% client itself something that that's would<00:12:07.519> interface<00:12:08.040> with<00:12:08.800> uh<00:12:09.279> something<00:12:09.680> you 00:12:10.030 --> 00:12:10.040 align:start position:0% would interface with uh something you 00:12:10.040 --> 00:12:12.949 align:start position:0% would interface with uh something you can<00:12:11.040> like<00:12:11.240> the<00:12:11.720> the<00:12:11.839> current<00:12:12.079> RPC<00:12:12.639> that<00:12:12.760> we 00:12:12.949 --> 00:12:12.959 align:start position:0% can like the the current RPC that we 00:12:12.959 --> 00:12:16.670 align:start position:0% can like the the current RPC that we have<00:12:13.360> that<00:12:13.480> we<00:12:13.639> have<00:12:14.040> today<00:12:15.440> um<00:12:16.440> another 00:12:16.670 --> 00:12:16.680 align:start position:0% have that we have today um another 00:12:16.680 --> 00:12:18.269 align:start position:0% have that we have today um another something<00:12:17.160> that<00:12:17.360> we<00:12:17.560> that<00:12:17.680> we<00:12:17.800> really<00:12:17.959> want<00:12:18.120> to 00:12:18.269 --> 00:12:18.279 align:start position:0% something that we that we really want to 00:12:18.279 --> 00:12:20.629 align:start position:0% something that we that we really want to split<00:12:18.560> up<00:12:19.160> um<00:12:19.320> because<00:12:19.839> we<00:12:19.959> see<00:12:20.120> it<00:12:20.240> as<00:12:20.399> two 00:12:20.629 --> 00:12:20.639 align:start position:0% split up um because we see it as two 00:12:20.639 --> 00:12:21.509 align:start position:0% split up um because we see it as two different 00:12:21.509 --> 00:12:21.519 align:start position:0% different 00:12:21.519 --> 00:12:24.550 align:start position:0% different domains<00:12:22.519> um<00:12:23.160> and<00:12:23.360> and<00:12:23.560> with<00:12:23.760> that<00:12:23.920> in<00:12:24.079> mind<00:12:24.440> we 00:12:24.550 --> 00:12:24.560 align:start position:0% domains um and and with that in mind we 00:12:24.560 --> 00:12:26.910 align:start position:0% domains um and and with that in mind we want<00:12:24.760> to<00:12:25.560> uh<00:12:25.720> address<00:12:26.079> some<00:12:26.199> of<00:12:26.360> the<00:12:26.560> issues 00:12:26.910 --> 00:12:26.920 align:start position:0% want to uh address some of the issues 00:12:26.920 --> 00:12:29.230 align:start position:0% want to uh address some of the issues that<00:12:27.079> we<00:12:27.240> have<00:12:27.480> with<00:12:27.600> the<00:12:27.839> interfacing<00:12:28.839> um<00:12:29.000> I 00:12:29.230 --> 00:12:29.240 align:start position:0% that we have with the interfacing um I 00:12:29.240 --> 00:12:30.910 align:start position:0% that we have with the interfacing um I know<00:12:29.440> that<00:12:29.600> there<00:12:29.720> is<00:12:30.279> there<00:12:30.480> there<00:12:30.680> there's 00:12:30.910 --> 00:12:30.920 align:start position:0% know that there is there there there's 00:12:30.920 --> 00:12:32.590 align:start position:0% know that there is there there there's more<00:12:31.279> people<00:12:31.600> wanting<00:12:31.880> to<00:12:32.199> directly 00:12:32.590 --> 00:12:32.600 align:start position:0% more people wanting to directly 00:12:32.600 --> 00:12:35.310 align:start position:0% more people wanting to directly interface<00:12:33.040> with<00:12:33.160> the<00:12:33.279> core<00:12:33.639> itself<00:12:34.639> uh<00:12:34.760> and<00:12:35.240> as 00:12:35.310 --> 00:12:35.320 align:start position:0% interface with the core itself uh and as 00:12:35.320 --> 00:12:37.230 align:start position:0% interface with the core itself uh and as it<00:12:35.480> is<00:12:35.639> today<00:12:35.920> it's<00:12:36.160> it's<00:12:36.360> quite<00:12:36.920> well<00:12:37.160> I 00:12:37.230 --> 00:12:37.240 align:start position:0% it is today it's it's quite well I 00:12:37.240 --> 00:12:38.990 align:start position:0% it is today it's it's quite well I wouldn't<00:12:37.440> say<00:12:37.600> it's<00:12:37.760> impossible<00:12:38.399> but<00:12:38.560> it's 00:12:38.990 --> 00:12:39.000 align:start position:0% wouldn't say it's impossible but it's 00:12:39.000 --> 00:12:40.910 align:start position:0% wouldn't say it's impossible but it's difficult<00:12:39.760> and<00:12:39.920> we<00:12:40.040> want<00:12:40.120> to<00:12:40.279> address<00:12:40.600> some<00:12:40.720> of 00:12:40.910 --> 00:12:40.920 align:start position:0% difficult and we want to address some of 00:12:40.920 --> 00:12:43.590 align:start position:0% difficult and we want to address some of the<00:12:41.360> uh<00:12:41.760> uh<00:12:42.399> some<00:12:42.519> of<00:12:42.639> the<00:12:42.839> documentation<00:12:43.519> we 00:12:43.590 --> 00:12:43.600 align:start position:0% the uh uh some of the documentation we 00:12:43.600 --> 00:12:46.509 align:start position:0% the uh uh some of the documentation we want<00:12:43.720> to<00:12:43.839> improve<00:12:44.160> on<00:12:44.360> that<00:12:44.600> we<00:12:44.720> want<00:12:45.279> to<00:12:46.279> uh<00:12:46.399> we 00:12:46.509 --> 00:12:46.519 align:start position:0% want to improve on that we want to uh we 00:12:46.519 --> 00:12:49.910 align:start position:0% want to improve on that we want to uh we want<00:12:46.720> to<00:12:47.880> um<00:12:48.880> make<00:12:49.040> it<00:12:49.160> more<00:12:49.399> clear<00:12:49.680> for 00:12:49.910 --> 00:12:49.920 align:start position:0% want to um make it more clear for 00:12:49.920 --> 00:12:52.629 align:start position:0% want to um make it more clear for developers<00:12:50.519> on<00:12:50.760> on<00:12:51.000> how<00:12:51.199> to<00:12:51.760> how<00:12:51.880> to<00:12:52.120> directly 00:12:52.629 --> 00:12:52.639 align:start position:0% developers on on how to how to directly 00:12:52.639 --> 00:12:55.230 align:start position:0% developers on on how to how to directly interface<00:12:53.360> with<00:12:53.600> the<00:12:54.000> uh<00:12:54.720> with<00:12:54.839> the<00:12:54.959> client 00:12:55.230 --> 00:12:55.240 align:start position:0% interface with the uh with the client 00:12:55.240 --> 00:12:57.790 align:start position:0% interface with the uh with the client itself<00:12:55.560> with<00:12:55.839> with<00:12:55.959> the<00:12:56.120> with<00:12:56.240> the<00:12:56.360> core<00:12:56.800> API 00:12:57.790 --> 00:12:57.800 align:start position:0% itself with with the with the core API 00:12:57.800 --> 00:12:59.750 align:start position:0% itself with with the with the core API uh<00:12:57.880> but<00:12:58.040> on<00:12:58.199> top<00:12:58.320> of<00:12:58.440> that<00:12:58.560> we<00:12:58.680> want<00:12:58.839> to<00:12:59.600> um 00:12:59.750 --> 00:12:59.760 align:start position:0% uh but on top of that we want to um 00:12:59.760 --> 00:13:02.430 align:start position:0% uh but on top of that we want to um Supply<00:13:00.360> people<00:13:00.720> with<00:13:01.000> a<00:13:01.560> uh<00:13:01.880> it's<00:13:02.040> like<00:13:02.199> an 00:13:02.430 --> 00:13:02.440 align:start position:0% Supply people with a uh it's like an 00:13:02.440 --> 00:13:07.310 align:start position:0% Supply people with a uh it's like an abstract<00:13:03.040> layer<00:13:03.959> um<00:13:04.199> s<00:13:04.480> such<00:13:04.680> as<00:13:05.480> uh<00:13:06.480> a<00:13:06.639> new<00:13:07.199> a 00:13:07.310 --> 00:13:07.320 align:start position:0% abstract layer um s such as uh a new a 00:13:07.320 --> 00:13:10.069 align:start position:0% abstract layer um s such as uh a new a new<00:13:07.600> IPC<00:13:08.079> Channel<00:13:09.040> something<00:13:09.639> uh<00:13:09.760> something 00:13:10.069 --> 00:13:10.079 align:start position:0% new IPC Channel something uh something 00:13:10.079 --> 00:13:13.269 align:start position:0% new IPC Channel something uh something that<00:13:10.240> we're<00:13:10.480> hardly<00:13:10.920> working<00:13:11.279> on<00:13:12.199> um<00:13:12.920> working 00:13:13.269 --> 00:13:13.279 align:start position:0% that we're hardly working on um working 00:13:13.279 --> 00:13:17.189 align:start position:0% that we're hardly working on um working hard<00:13:13.480> on<00:13:13.720> sorry<00:13:15.120> um<00:13:16.120> not<00:13:16.320> hardly<00:13:16.639> working<00:13:16.959> on 00:13:17.189 --> 00:13:17.199 align:start position:0% hard on sorry um not hardly working on 00:13:17.199 --> 00:13:18.629 align:start position:0% hard on sorry um not hardly working on working<00:13:17.519> hard 00:13:18.629 --> 00:13:18.639 align:start position:0% working hard 00:13:18.639 --> 00:13:22.230 align:start position:0% working hard on<00:13:19.639> um<00:13:20.320> and<00:13:21.079> and<00:13:21.199> through<00:13:21.760> we<00:13:21.839> want<00:13:21.959> to<00:13:22.079> we<00:13:22.160> want 00:13:22.230 --> 00:13:22.240 align:start position:0% on um and and through we want to we want 00:13:22.240 --> 00:13:24.670 align:start position:0% on um and and through we want to we want to<00:13:22.360> change<00:13:22.600> some<00:13:22.720> of<00:13:22.839> the<00:13:23.000> components<00:13:24.000> um 00:13:24.670 --> 00:13:24.680 align:start position:0% to change some of the components um 00:13:24.680 --> 00:13:27.110 align:start position:0% to change some of the components um because<00:13:25.680> what<00:13:25.839> we<00:13:26.000> have<00:13:26.240> now<00:13:26.399> is<00:13:26.560> more<00:13:26.720> of<00:13:26.839> a 00:13:27.110 --> 00:13:27.120 align:start position:0% because what we have now is more of a 00:13:27.120 --> 00:13:29.590 align:start position:0% because what we have now is more of a like<00:13:27.440> you<00:13:27.639> you<00:13:27.800> pull<00:13:28.240> data<00:13:28.600> out<00:13:28.760> of<00:13:28.920> the<00:13:29.279> out<00:13:29.399> of 00:13:29.590 --> 00:13:29.600 align:start position:0% like you you pull data out of the out of 00:13:29.600 --> 00:13:32.389 align:start position:0% like you you pull data out of the out of the<00:13:29.880> out<00:13:30.000> of<00:13:30.120> the<00:13:30.279> client<00:13:31.120> um<00:13:31.560> and<00:13:31.720> it's<00:13:32.000> it's 00:13:32.389 --> 00:13:32.399 align:start position:0% the out of the client um and it's it's 00:13:32.399 --> 00:13:33.350 align:start position:0% the out of the client um and it's it's difficult<00:13:32.560> for<00:13:32.680> the<00:13:32.800> client<00:13:33.040> to<00:13:33.160> give 00:13:33.350 --> 00:13:33.360 align:start position:0% difficult for the client to give 00:13:33.360 --> 00:13:36.230 align:start position:0% difficult for the client to give feedback<00:13:34.279> um<00:13:34.639> to<00:13:34.880> the<00:13:35.440> um<00:13:35.560> you<00:13:35.680> know<00:13:35.880> adap 00:13:36.230 --> 00:13:36.240 align:start position:0% feedback um to the um you know adap 00:13:36.240 --> 00:13:39.189 align:start position:0% feedback um to the um you know adap itself<00:13:36.800> or<00:13:36.959> or<00:13:37.120> an<00:13:37.600> application 00:13:39.189 --> 00:13:39.199 align:start position:0% itself or or an application 00:13:39.199 --> 00:13:41.990 align:start position:0% itself or or an application and<00:13:40.199> it<00:13:40.360> kind<00:13:40.519> of<00:13:40.720> burdens<00:13:41.199> the<00:13:41.360> node<00:13:41.680> with<00:13:41.800> so 00:13:41.990 --> 00:13:42.000 align:start position:0% and it kind of burdens the node with so 00:13:42.000 --> 00:13:44.430 align:start position:0% and it kind of burdens the node with so many<00:13:42.320> requests<00:13:43.320> um<00:13:43.560> because<00:13:43.880> for<00:13:44.040> example<00:13:44.360> if 00:13:44.430 --> 00:13:44.440 align:start position:0% many requests um because for example if 00:13:44.440 --> 00:13:45.949 align:start position:0% many requests um because for example if you<00:13:44.560> would<00:13:44.680> like<00:13:44.839> to<00:13:45.079> subscribe<00:13:45.440> to<00:13:45.560> a<00:13:45.639> certain 00:13:45.949 --> 00:13:45.959 align:start position:0% you would like to subscribe to a certain 00:13:45.959 --> 00:13:47.430 align:start position:0% you would like to subscribe to a certain event<00:13:46.320> you<00:13:46.680> you<00:13:46.800> tell<00:13:47.079> them<00:13:47.199> want<00:13:47.320> to 00:13:47.430 --> 00:13:47.440 align:start position:0% event you you tell them want to 00:13:47.440 --> 00:13:48.910 align:start position:0% event you you tell them want to subscribe<00:13:47.800> to<00:13:47.880> an<00:13:48.040> event<00:13:48.240> and<00:13:48.320> then<00:13:48.440> you<00:13:48.720> need 00:13:48.910 --> 00:13:48.920 align:start position:0% subscribe to an event and then you need 00:13:48.920 --> 00:13:50.629 align:start position:0% subscribe to an event and then you need to<00:13:49.079> keep<00:13:49.279> pulling<00:13:49.639> for<00:13:49.839> day<00:13:50.120> you<00:13:50.199> have<00:13:50.320> to<00:13:50.480> keep 00:13:50.629 --> 00:13:50.639 align:start position:0% to keep pulling for day you have to keep 00:13:50.639 --> 00:13:52.430 align:start position:0% to keep pulling for day you have to keep asking<00:13:51.000> hey<00:13:51.160> do<00:13:51.240> you<00:13:51.320> have<00:13:51.480> new<00:13:51.680> data<00:13:51.880> for<00:13:52.040> me 00:13:52.430 --> 00:13:52.440 align:start position:0% asking hey do you have new data for me 00:13:52.440 --> 00:13:54.230 align:start position:0% asking hey do you have new data for me so<00:13:52.639> instead<00:13:52.920> of<00:13:53.360> instead<00:13:53.600> of<00:13:53.800> that<00:13:53.959> approach 00:13:54.230 --> 00:13:54.240 align:start position:0% so instead of instead of that approach 00:13:54.240 --> 00:13:55.629 align:start position:0% so instead of instead of that approach we<00:13:54.360> want<00:13:54.440> to<00:13:54.600> we<00:13:54.680> want<00:13:54.800> to<00:13:54.920> change<00:13:55.160> that<00:13:55.320> around 00:13:55.629 --> 00:13:55.639 align:start position:0% we want to we want to change that around 00:13:55.639 --> 00:13:57.509 align:start position:0% we want to we want to change that around you<00:13:55.759> want<00:13:55.839> to<00:13:55.959> say<00:13:56.240> well<00:13:56.560> you<00:13:56.759> subscribe<00:13:57.240> to<00:13:57.360> an 00:13:57.509 --> 00:13:57.519 align:start position:0% you want to say well you subscribe to an 00:13:57.519 --> 00:14:00.350 align:start position:0% you want to say well you subscribe to an event<00:13:57.920> and<00:13:58.079> instead<00:13:58.440> of<00:13:59.240> asking<00:13:59.600> for<00:13:59.959> data<00:14:00.240> all 00:14:00.350 --> 00:14:00.360 align:start position:0% event and instead of asking for data all 00:14:00.360 --> 00:14:01.790 align:start position:0% event and instead of asking for data all the<00:14:00.480> time<00:14:00.639> you're<00:14:00.759> just<00:14:00.880> GNA<00:14:01.160> wait<00:14:01.440> you're<00:14:01.600> GNA 00:14:01.790 --> 00:14:01.800 align:start position:0% the time you're just GNA wait you're GNA 00:14:01.800 --> 00:14:04.030 align:start position:0% the time you're just GNA wait you're GNA just<00:14:01.920> GNA<00:14:02.160> wait<00:14:02.320> and<00:14:02.480> sit<00:14:02.720> there<00:14:02.920> until<00:14:03.720> the 00:14:04.030 --> 00:14:04.040 align:start position:0% just GNA wait and sit there until the 00:14:04.040 --> 00:14:05.230 align:start position:0% just GNA wait and sit there until the the<00:14:04.120> node<00:14:04.360> is<00:14:04.399> are<00:14:04.480> going<00:14:04.560> to<00:14:04.639> tell<00:14:04.759> you<00:14:05.000> well 00:14:05.230 --> 00:14:05.240 align:start position:0% the node is are going to tell you well 00:14:05.240 --> 00:14:06.710 align:start position:0% the node is are going to tell you well here<00:14:05.360> you<00:14:05.480> go<00:14:05.639> here<00:14:05.759> you<00:14:05.880> have<00:14:06.040> the<00:14:06.199> data<00:14:06.440> and 00:14:06.710 --> 00:14:06.720 align:start position:0% here you go here you have the data and 00:14:06.720 --> 00:14:10.949 align:start position:0% here you go here you have the data and do<00:14:06.880> something<00:14:07.279> with<00:14:07.399> it<00:14:07.959> and<00:14:08.440> um<00:14:09.440> off<00:14:09.639> you<00:14:09.959> go 00:14:10.949 --> 00:14:10.959 align:start position:0% do something with it and um off you go 00:14:10.959 --> 00:14:12.389 align:start position:0% do something with it and um off you go so<00:14:11.160> that's<00:14:11.320> one<00:14:11.440> of<00:14:11.519> the<00:14:11.639> things<00:14:11.800> that<00:14:12.160> that<00:14:12.279> we 00:14:12.389 --> 00:14:12.399 align:start position:0% so that's one of the things that that we 00:14:12.399 --> 00:14:14.629 align:start position:0% so that's one of the things that that we would<00:14:12.680> really<00:14:12.920> like<00:14:13.079> to<00:14:13.279> address<00:14:13.680> in<00:14:13.880> the<00:14:14.279> uh 00:14:14.629 --> 00:14:14.639 align:start position:0% would really like to address in the uh 00:14:14.639 --> 00:14:17.350 align:start position:0% would really like to address in the uh in<00:14:14.800> the<00:14:14.920> upcoming<00:14:15.519> in<00:14:15.639> the<00:14:15.759> upcoming 00:14:17.350 --> 00:14:17.360 align:start position:0% in the upcoming in the upcoming 00:14:17.360 --> 00:14:20.150 align:start position:0% in the upcoming in the upcoming months<00:14:18.360> um<00:14:18.759> so<00:14:18.920> that<00:14:19.079> we<00:14:19.199> can<00:14:19.360> make<00:14:19.519> it<00:14:19.800> a<00:14:19.920> bit 00:14:20.150 --> 00:14:20.160 align:start position:0% months um so that we can make it a bit 00:14:20.160 --> 00:14:22.069 align:start position:0% months um so that we can make it a bit more<00:14:20.399> easier<00:14:20.680> for<00:14:20.920> developers<00:14:21.399> to<00:14:21.920> uh 00:14:22.069 --> 00:14:22.079 align:start position:0% more easier for developers to uh 00:14:22.079 --> 00:14:25.269 align:start position:0% more easier for developers to uh directly<00:14:22.519> interface<00:14:22.920> with<00:14:23.120> the<00:14:23.240> node<00:14:23.759> and<00:14:24.279> uh 00:14:25.269 --> 00:14:25.279 align:start position:0% directly interface with the node and uh 00:14:25.279 --> 00:14:27.749 align:start position:0% directly interface with the node and uh uh<00:14:25.680> you<00:14:25.759> know<00:14:26.079> have<00:14:26.519> have<00:14:26.759> native<00:14:27.240> application 00:14:27.749 --> 00:14:27.759 align:start position:0% uh you know have have native application 00:14:27.759 --> 00:14:28.910 align:start position:0% uh you know have have native application because<00:14:27.920> that's<00:14:28.240> really<00:14:28.440> what<00:14:28.560> it<00:14:28.639> is<00:14:28.759> this<00:14:28.839> is 00:14:28.910 --> 00:14:28.920 align:start position:0% because that's really what it is this is 00:14:28.920 --> 00:14:31.509 align:start position:0% because that's really what it is this is not<00:14:29.279> for<00:14:29.839> people<00:14:30.120> doing<00:14:30.480> HTML<00:14:31.040> daps<00:14:31.399> this 00:14:31.509 --> 00:14:31.519 align:start position:0% not for people doing HTML daps this 00:14:31.519 --> 00:14:33.389 align:start position:0% not for people doing HTML daps this would<00:14:31.680> be<00:14:31.839> more<00:14:32.040> for<00:14:32.320> developers<00:14:33.279> uh 00:14:33.389 --> 00:14:33.399 align:start position:0% would be more for developers uh 00:14:33.399 --> 00:14:36.269 align:start position:0% would be more for developers uh developing<00:14:34.240> uh<00:14:34.320> for<00:14:34.560> iot<00:14:35.040> devices<00:14:35.639> or<00:14:36.120> uh 00:14:36.269 --> 00:14:36.279 align:start position:0% developing uh for iot devices or uh 00:14:36.279 --> 00:14:40.350 align:start position:0% developing uh for iot devices or uh phone<00:14:36.759> smartphone<00:14:37.600> smart<00:14:38.600> uh<00:14:38.759> smart<00:14:39.360> watches 00:14:40.350 --> 00:14:40.360 align:start position:0% phone smartphone smart uh smart watches 00:14:40.360 --> 00:14:43.430 align:start position:0% phone smartphone smart uh smart watches um<00:14:40.639> you<00:14:40.759> know<00:14:41.120> like<00:14:41.320> like<00:14:41.560> low<00:14:41.839> lowend<00:14:42.279> devices 00:14:43.430 --> 00:14:43.440 align:start position:0% um you know like like low lowend devices 00:14:43.440 --> 00:14:46.550 align:start position:0% um you know like like low lowend devices and<00:14:44.440> but<00:14:44.600> as<00:14:44.720> it<00:14:44.839> is<00:14:45.079> today<00:14:45.920> um<00:14:46.120> it's<00:14:46.320> going<00:14:46.440> to 00:14:46.550 --> 00:14:46.560 align:start position:0% and but as it is today um it's going to 00:14:46.560 --> 00:14:48.949 align:start position:0% and but as it is today um it's going to be<00:14:46.920> quite<00:14:47.440> difficult<00:14:47.720> putting<00:14:48.000> a<00:14:48.160> full<00:14:48.440> node 00:14:48.949 --> 00:14:48.959 align:start position:0% be quite difficult putting a full node 00:14:48.959 --> 00:14:51.710 align:start position:0% be quite difficult putting a full node on<00:14:49.120> a<00:14:49.480> uh<00:14:49.880> on<00:14:50.000> a<00:14:50.199> watch<00:14:51.040> and<00:14:51.160> that's<00:14:51.360> what<00:14:51.480> a 00:14:51.710 --> 00:14:51.720 align:start position:0% on a uh on a watch and that's what a 00:14:51.720 --> 00:14:53.069 align:start position:0% on a uh on a watch and that's what a what<00:14:51.839> a<00:14:51.920> light<00:14:52.120> client<00:14:52.440> comes<00:14:52.639> in<00:14:52.880> there's 00:14:53.069 --> 00:14:53.079 align:start position:0% what a light client comes in there's 00:14:53.079 --> 00:14:54.269 align:start position:0% what a light client comes in there's there's<00:14:53.279> going<00:14:53.399> to<00:14:53.480> be<00:14:53.600> a<00:14:53.720> presentation<00:14:54.160> in 00:14:54.269 --> 00:14:54.279 align:start position:0% there's going to be a presentation in 00:14:54.279 --> 00:14:55.949 align:start position:0% there's going to be a presentation in the<00:14:54.399> upcoming<00:14:54.720> days<00:14:54.920> about<00:14:55.079> the<00:14:55.199> light<00:14:55.360> cin<00:14:55.680> S 00:14:55.949 --> 00:14:55.959 align:start position:0% the upcoming days about the light cin S 00:14:55.959 --> 00:14:58.150 align:start position:0% the upcoming days about the light cin S I<00:14:56.040> won't<00:14:56.199> go<00:14:56.320> into<00:14:56.519> too<00:14:56.680> many<00:14:56.920> details<00:14:57.920> um<00:14:58.040> but 00:14:58.150 --> 00:14:58.160 align:start position:0% I won't go into too many details um but 00:14:58.160 --> 00:15:00.310 align:start position:0% I won't go into too many details um but I<00:14:58.279> just<00:14:58.360> want<00:14:58.480> to<00:14:58.639> briefly<00:14:59.160> touch<00:14:59.360> on<00:14:59.639> the<00:14:59.959> uh 00:15:00.310 --> 00:15:00.320 align:start position:0% I just want to briefly touch on the uh 00:15:00.320 --> 00:15:02.150 align:start position:0% I just want to briefly touch on the uh on<00:15:00.440> the<00:15:00.600> stuff<00:15:00.839> that<00:15:01.000> we<00:15:01.079> will<00:15:01.279> be<00:15:01.880> how<00:15:02.040> we 00:15:02.150 --> 00:15:02.160 align:start position:0% on the stuff that we will be how we 00:15:02.160 --> 00:15:03.150 align:start position:0% on the stuff that we will be how we going<00:15:02.240> to<00:15:02.360> how<00:15:02.480> we<00:15:02.600> going<00:15:02.680> to<00:15:02.759> handle<00:15:03.040> the 00:15:03.150 --> 00:15:03.160 align:start position:0% going to how we going to handle the 00:15:03.160 --> 00:15:05.430 align:start position:0% going to how we going to handle the development<00:15:03.680> of<00:15:03.880> the<00:15:04.079> of<00:15:04.199> the<00:15:04.320> light<00:15:04.600> client 00:15:05.430 --> 00:15:05.440 align:start position:0% development of the of the light client 00:15:05.440 --> 00:15:07.389 align:start position:0% development of the of the light client um<00:15:05.560> one<00:15:05.680> of<00:15:05.839> them<00:15:06.120> is<00:15:06.880> um<00:15:07.040> so<00:15:07.120> we're<00:15:07.240> going<00:15:07.320> to 00:15:07.389 --> 00:15:07.399 align:start position:0% um one of them is um so we're going to 00:15:07.399 --> 00:15:09.749 align:start position:0% um one of them is um so we're going to do<00:15:07.480> it<00:15:07.560> in<00:15:07.720> two<00:15:07.959> stages<00:15:08.920> uh<00:15:09.079> stage<00:15:09.360> one<00:15:09.600> would 00:15:09.749 --> 00:15:09.759 align:start position:0% do it in two stages uh stage one would 00:15:09.759 --> 00:15:13.710 align:start position:0% do it in two stages uh stage one would be<00:15:09.920> a<00:15:10.120> developer<00:15:10.600> preview<00:15:11.560> um<00:15:12.519> it's<00:15:13.440> it's<00:15:13.600> kind 00:15:13.710 --> 00:15:13.720 align:start position:0% be a developer preview um it's it's kind 00:15:13.720 --> 00:15:16.389 align:start position:0% be a developer preview um it's it's kind of<00:15:13.920> like<00:15:14.279> uh<00:15:15.199> just<00:15:15.360> for<00:15:15.560> us<00:15:15.759> so<00:15:15.920> that<00:15:16.040> we<00:15:16.160> can 00:15:16.389 --> 00:15:16.399 align:start position:0% of like uh just for us so that we can 00:15:16.399 --> 00:15:19.389 align:start position:0% of like uh just for us so that we can check<00:15:17.120> whether<00:15:17.320> it's<00:15:17.560> viable<00:15:18.560> um<00:15:18.959> whether<00:15:19.199> it 00:15:19.389 --> 00:15:19.399 align:start position:0% check whether it's viable um whether it 00:15:19.399 --> 00:15:20.749 align:start position:0% check whether it's viable um whether it you<00:15:19.519> know<00:15:19.720> actually<00:15:20.000> decent<00:15:20.440> whether<00:15:20.600> it 00:15:20.749 --> 00:15:20.759 align:start position:0% you know actually decent whether it 00:15:20.759 --> 00:15:22.629 align:start position:0% you know actually decent whether it works<00:15:21.079> whether<00:15:21.240> it's<00:15:21.399> something<00:15:21.880> that<00:15:22.519> the 00:15:22.629 --> 00:15:22.639 align:start position:0% works whether it's something that the 00:15:22.639 --> 00:15:24.710 align:start position:0% works whether it's something that the community<00:15:23.040> would<00:15:23.199> like<00:15:23.360> to<00:15:23.600> have<00:15:24.440> and<00:15:24.600> this 00:15:24.710 --> 00:15:24.720 align:start position:0% community would like to have and this 00:15:24.720 --> 00:15:26.030 align:start position:0% community would like to have and this will<00:15:24.880> be<00:15:25.079> developed<00:15:25.480> as<00:15:25.560> a<00:15:25.759> separate 00:15:26.030 --> 00:15:26.040 align:start position:0% will be developed as a separate 00:15:26.040 --> 00:15:27.749 align:start position:0% will be developed as a separate subprotocol<00:15:26.720> so<00:15:26.839> it's<00:15:26.959> going<00:15:27.040> to<00:15:27.160> be<00:15:27.360> separate 00:15:27.749 --> 00:15:27.759 align:start position:0% subprotocol so it's going to be separate 00:15:27.759 --> 00:15:29.269 align:start position:0% subprotocol so it's going to be separate from<00:15:28.040> ethereum<00:15:28.560> it's<00:15:28.680> going<00:15:28.759> to<00:15:29.000> function 00:15:29.269 --> 00:15:29.279 align:start position:0% from ethereum it's going to function 00:15:29.279 --> 00:15:31.430 align:start position:0% from ethereum it's going to function obviously<00:15:29.639> on<00:15:29.920> on<00:15:30.120> on<00:15:30.199> the<00:15:30.319> same<00:15:30.519> chain<00:15:30.839> but<00:15:31.279> it 00:15:31.430 --> 00:15:31.440 align:start position:0% obviously on on on the same chain but it 00:15:31.440 --> 00:15:33.189 align:start position:0% obviously on on on the same chain but it it's<00:15:31.560> going<00:15:31.680> to<00:15:31.839> have<00:15:31.959> its<00:15:32.120> own<00:15:32.519> subprotocol 00:15:33.189 --> 00:15:33.199 align:start position:0% it's going to have its own subprotocol 00:15:33.199 --> 00:15:34.710 align:start position:0% it's going to have its own subprotocol registered<00:15:33.639> to<00:15:33.720> the<00:15:33.839> node<00:15:34.079> as<00:15:34.199> I<00:15:34.319> described 00:15:34.710 --> 00:15:34.720 align:start position:0% registered to the node as I described 00:15:34.720 --> 00:15:36.790 align:start position:0% registered to the node as I described earlier<00:15:35.639> and<00:15:35.959> one<00:15:36.079> of<00:15:36.199> the<00:15:36.319> things<00:15:36.519> that<00:15:36.639> it 00:15:36.790 --> 00:15:36.800 align:start position:0% earlier and one of the things that it 00:15:36.800 --> 00:15:39.069 align:start position:0% earlier and one of the things that it can<00:15:37.040> do<00:15:37.279> for<00:15:37.480> now<00:15:37.759> is<00:15:37.920> simply<00:15:38.240> State<00:15:38.600> querying 00:15:39.069 --> 00:15:39.079 align:start position:0% can do for now is simply State querying 00:15:39.079 --> 00:15:41.870 align:start position:0% can do for now is simply State querying which<00:15:39.240> means<00:15:39.680> that<00:15:40.600> um<00:15:40.720> you<00:15:40.839> can<00:15:41.240> you<00:15:41.360> can<00:15:41.600> get 00:15:41.870 --> 00:15:41.880 align:start position:0% which means that um you can you can get 00:15:41.880 --> 00:15:44.030 align:start position:0% which means that um you can you can get balance<00:15:42.800> uh<00:15:42.959> you<00:15:43.079> can<00:15:43.360> you<00:15:43.480> can<00:15:43.639> you<00:15:43.720> can<00:15:43.880> get 00:15:44.030 --> 00:15:44.040 align:start position:0% balance uh you can you can you can get 00:15:44.040 --> 00:15:46.430 align:start position:0% balance uh you can you can you can get the<00:15:44.240> code<00:15:44.680> you<00:15:44.800> can<00:15:45.360> uh<00:15:45.480> you<00:15:45.560> can<00:15:45.759> get<00:15:46.000> certain 00:15:46.430 --> 00:15:46.440 align:start position:0% the code you can uh you can get certain 00:15:46.440 --> 00:15:48.749 align:start position:0% the code you can uh you can get certain State<00:15:46.880> information<00:15:47.319> about<00:15:47.519> a<00:15:47.720> contract<00:15:48.600> um 00:15:48.749 --> 00:15:48.759 align:start position:0% State information about a contract um 00:15:48.759 --> 00:15:51.269 align:start position:0% State information about a contract um but<00:15:48.880> that's<00:15:49.040> about<00:15:49.240> it<00:15:49.399> so<00:15:49.880> there's<00:15:50.880> uh<00:15:51.160> there 00:15:51.269 --> 00:15:51.279 align:start position:0% but that's about it so there's uh there 00:15:51.279 --> 00:15:52.710 align:start position:0% but that's about it so there's uh there isn't<00:15:51.519> there<00:15:51.600> isn't<00:15:51.839> much<00:15:52.000> else<00:15:52.199> than<00:15:52.440> just 00:15:52.710 --> 00:15:52.720 align:start position:0% isn't there isn't much else than just 00:15:52.720 --> 00:15:54.749 align:start position:0% isn't there isn't much else than just quering<00:15:53.199> for<00:15:53.440> data<00:15:53.720> and<00:15:53.959> validating<00:15:54.440> that<00:15:54.600> the 00:15:54.749 --> 00:15:54.759 align:start position:0% quering for data and validating that the 00:15:54.759 --> 00:15:57.990 align:start position:0% quering for data and validating that the data<00:15:55.000> that<00:15:55.160> you<00:15:55.839> um<00:15:56.680> that<00:15:56.800> you<00:15:57.000> got<00:15:57.279> from<00:15:57.639> from 00:15:57.990 --> 00:15:58.000 align:start position:0% data that you um that you got from from 00:15:58.000 --> 00:16:00.030 align:start position:0% data that you um that you got from from from<00:15:58.120> the<00:15:58.279> remote<00:15:58.560> node<00:15:58.800> is<00:15:59.079> actually 00:16:00.030 --> 00:16:00.040 align:start position:0% from the remote node is actually 00:16:00.040 --> 00:16:02.910 align:start position:0% from the remote node is actually valid<00:16:01.040> now<00:16:01.199> in<00:16:01.360> stage<00:16:01.639> two<00:16:02.360> it's<00:16:02.600> actually 00:16:02.910 --> 00:16:02.920 align:start position:0% valid now in stage two it's actually 00:16:02.920 --> 00:16:04.870 align:start position:0% valid now in stage two it's actually going<00:16:03.120> to<00:16:03.240> be<00:16:03.399> a<00:16:03.519> lot<00:16:03.680> more<00:16:03.880> interesting<00:16:04.720> um 00:16:04.870 --> 00:16:04.880 align:start position:0% going to be a lot more interesting um 00:16:04.880 --> 00:16:06.389 align:start position:0% going to be a lot more interesting um because<00:16:05.040> that<00:16:05.160> would<00:16:05.319> be<00:16:05.560> the<00:16:06.000> there<00:16:06.120> would<00:16:06.240> be 00:16:06.389 --> 00:16:06.399 align:start position:0% because that would be the there would be 00:16:06.399 --> 00:16:08.910 align:start position:0% because that would be the there would be more<00:16:06.519> of<00:16:06.639> the<00:16:07.079> full-blown<00:16:08.079> full-blown<00:16:08.680> light 00:16:08.910 --> 00:16:08.920 align:start position:0% more of the full-blown full-blown light 00:16:08.920 --> 00:16:11.590 align:start position:0% more of the full-blown full-blown light client<00:16:09.240> you<00:16:09.319> would<00:16:09.560> expect<00:16:10.399> in<00:16:10.560> which<00:16:10.800> you<00:16:11.399> can 00:16:11.590 --> 00:16:11.600 align:start position:0% client you would expect in which you can 00:16:11.600 --> 00:16:14.150 align:start position:0% client you would expect in which you can do<00:16:12.120> uh<00:16:12.319> transaction<00:16:12.800> sending<00:16:13.639> so<00:16:13.800> it<00:16:13.920> actually 00:16:14.150 --> 00:16:14.160 align:start position:0% do uh transaction sending so it actually 00:16:14.160 --> 00:16:16.910 align:start position:0% do uh transaction sending so it actually becomes<00:16:14.759> useful<00:16:15.759> um<00:16:16.199> and<00:16:16.319> one<00:16:16.440> of<00:16:16.560> the<00:16:16.680> other 00:16:16.910 --> 00:16:16.920 align:start position:0% becomes useful um and one of the other 00:16:16.920 --> 00:16:18.949 align:start position:0% becomes useful um and one of the other things<00:16:17.120> would<00:16:17.319> be<00:16:17.680> uh<00:16:17.800> log<00:16:18.120> filtering<00:16:18.759> and 00:16:18.949 --> 00:16:18.959 align:start position:0% things would be uh log filtering and 00:16:18.959 --> 00:16:19.910 align:start position:0% things would be uh log filtering and Bloom 00:16:19.910 --> 00:16:19.920 align:start position:0% Bloom 00:16:19.920 --> 00:16:21.829 align:start position:0% Bloom lookups<00:16:20.920> um<00:16:21.079> because<00:16:21.279> you<00:16:21.399> know<00:16:21.560> without 00:16:21.829 --> 00:16:21.839 align:start position:0% lookups um because you know without 00:16:21.839 --> 00:16:23.590 align:start position:0% lookups um because you know without there<00:16:22.079> going<00:16:22.160> to<00:16:22.240> be<00:16:22.399> pretty<00:16:22.800> impossible<00:16:23.440> to 00:16:23.590 --> 00:16:23.600 align:start position:0% there going to be pretty impossible to 00:16:23.600 --> 00:16:26.189 align:start position:0% there going to be pretty impossible to do<00:16:23.880> a<00:16:24.160> uh<00:16:24.319> to<00:16:24.480> do<00:16:24.600> a<00:16:24.759> dep<00:16:25.000> on<00:16:25.120> a<00:16:25.199> light<00:16:25.480> client 00:16:26.189 --> 00:16:26.199 align:start position:0% do a uh to do a dep on a light client 00:16:26.199 --> 00:16:27.990 align:start position:0% do a uh to do a dep on a light client now<00:16:26.399> jel<00:16:26.720> is<00:16:26.839> going<00:16:26.920> to<00:16:27.120> give<00:16:27.240> you<00:16:27.560> a<00:16:27.680> whole<00:16:27.839> lot 00:16:27.990 --> 00:16:28.000 align:start position:0% now jel is going to give you a whole lot 00:16:28.000 --> 00:16:30.069 align:start position:0% now jel is going to give you a whole lot more<00:16:28.160> in-depth<00:16:28.560> information<00:16:29.160> about 00:16:30.069 --> 00:16:30.079 align:start position:0% more in-depth information about 00:16:30.079 --> 00:16:32.189 align:start position:0% more in-depth information about that<00:16:31.079> and 00:16:32.189 --> 00:16:32.199 align:start position:0% that and 00:16:32.199 --> 00:16:34.470 align:start position:0% that and um<00:16:33.199> so<00:16:33.680> it's<00:16:33.800> going<00:16:33.880> to<00:16:33.959> be<00:16:34.040> somewhere<00:16:34.360> this 00:16:34.470 --> 00:16:34.480 align:start position:0% um so it's going to be somewhere this 00:16:34.480 --> 00:16:36.790 align:start position:0% um so it's going to be somewhere this week<00:16:34.639> I<00:16:34.720> don't<00:16:34.839> think<00:16:34.959> it's<00:16:35.079> today<00:16:35.360> is<00:16:35.800> it 00:16:36.790 --> 00:16:36.800 align:start position:0% week I don't think it's today is it 00:16:36.800 --> 00:16:39.550 align:start position:0% week I don't think it's today is it Wednesday<00:16:37.399> there<00:16:37.480> you<00:16:37.639> go<00:16:38.519> um<00:16:39.079> so<00:16:39.279> he's<00:16:39.440> going 00:16:39.550 --> 00:16:39.560 align:start position:0% Wednesday there you go um so he's going 00:16:39.560 --> 00:16:41.030 align:start position:0% Wednesday there you go um so he's going to<00:16:39.639> give<00:16:39.759> you<00:16:39.880> a<00:16:40.000> more<00:16:40.160> in-depth<00:16:40.600> explanation 00:16:41.030 --> 00:16:41.040 align:start position:0% to give you a more in-depth explanation 00:16:41.040 --> 00:16:42.590 align:start position:0% to give you a more in-depth explanation about<00:16:41.199> the<00:16:41.319> light<00:16:41.600> client<00:16:42.000> and<00:16:42.240> the<00:16:42.399> and<00:16:42.519> the 00:16:42.590 --> 00:16:42.600 align:start position:0% about the light client and the and the 00:16:42.600 --> 00:16:45.189 align:start position:0% about the light client and the and the setup<00:16:42.959> of<00:16:43.440> it<00:16:44.440> uh<00:16:44.560> one<00:16:44.680> of<00:16:44.759> the<00:16:44.880> other<00:16:45.040> things 00:16:45.189 --> 00:16:45.199 align:start position:0% setup of it uh one of the other things 00:16:45.199 --> 00:16:46.550 align:start position:0% setup of it uh one of the other things that<00:16:45.319> we're<00:16:45.480> going<00:16:45.800> going<00:16:45.959> to<00:16:46.079> be<00:16:46.199> addressing 00:16:46.550 --> 00:16:46.560 align:start position:0% that we're going going to be addressing 00:16:46.560 --> 00:16:48.309 align:start position:0% that we're going going to be addressing is<00:16:46.680> the<00:16:46.839> core<00:16:47.120> refactoring<00:16:47.959> that<00:16:48.120> this<00:16:48.240> is 00:16:48.309 --> 00:16:48.319 align:start position:0% is the core refactoring that this is 00:16:48.319 --> 00:16:50.309 align:start position:0% is the core refactoring that this is something<00:16:48.639> has<00:16:48.839> already<00:16:49.120> started<00:16:50.000> um<00:16:50.199> and 00:16:50.309 --> 00:16:50.319 align:start position:0% something has already started um and 00:16:50.319 --> 00:16:51.990 align:start position:0% something has already started um and there's<00:16:50.720> an<00:16:50.839> ongoing<00:16:51.319> process<00:16:51.680> that<00:16:51.759> will 00:16:51.990 --> 00:16:52.000 align:start position:0% there's an ongoing process that will 00:16:52.000 --> 00:16:55.829 align:start position:0% there's an ongoing process that will happen<00:16:52.279> for<00:16:52.519> at<00:16:52.639> least<00:16:53.360> well<00:16:54.160> probably<00:16:55.160> uh 00:16:55.829 --> 00:16:55.839 align:start position:0% happen for at least well probably uh 00:16:55.839 --> 00:16:58.550 align:start position:0% happen for at least well probably uh probably<00:16:56.240> 6<00:16:56.519> months<00:16:57.319> um<00:16:57.680> 6<00:16:57.920> months<00:16:58.199> time<00:16:58.399> it's 00:16:58.550 --> 00:16:58.560 align:start position:0% probably 6 months um 6 months time it's 00:16:58.560 --> 00:17:00.870 align:start position:0% probably 6 months um 6 months time it's going<00:16:58.680> to<00:16:58.920> go<00:16:59.160> slowly<00:16:59.639> and<00:17:00.040> it's<00:17:00.199> an<00:17:00.360> iterative 00:17:00.870 --> 00:17:00.880 align:start position:0% going to go slowly and it's an iterative 00:17:00.880 --> 00:17:03.509 align:start position:0% going to go slowly and it's an iterative process<00:17:01.199> that<00:17:01.360> we<00:17:01.639> that<00:17:01.720> we<00:17:01.800> will<00:17:02.040> have<00:17:02.880> um<00:17:03.399> now 00:17:03.509 --> 00:17:03.519 align:start position:0% process that we that we will have um now 00:17:03.519 --> 00:17:04.710 align:start position:0% process that we that we will have um now one<00:17:03.639> of<00:17:03.720> the<00:17:03.839> first<00:17:04.079> things<00:17:04.240> that<00:17:04.360> we<00:17:04.480> want<00:17:04.559> to 00:17:04.710 --> 00:17:04.720 align:start position:0% one of the first things that we want to 00:17:04.720 --> 00:17:07.110 align:start position:0% one of the first things that we want to do<00:17:05.079> is<00:17:05.439> we<00:17:05.559> want<00:17:05.679> to<00:17:05.880> address<00:17:06.199> the<00:17:06.360> validation 00:17:07.110 --> 00:17:07.120 align:start position:0% do is we want to address the validation 00:17:07.120 --> 00:17:10.309 align:start position:0% do is we want to address the validation process<00:17:08.079> um<00:17:08.679> so<00:17:09.400> what<00:17:09.520> it<00:17:09.640> current<00:17:10.039> what<00:17:10.160> we 00:17:10.309 --> 00:17:10.319 align:start position:0% process um so what it current what we 00:17:10.319 --> 00:17:12.309 align:start position:0% process um so what it current what we have<00:17:10.559> now<00:17:10.839> is<00:17:11.280> the<00:17:11.439> validation<00:17:12.000> and<00:17:12.160> the 00:17:12.309 --> 00:17:12.319 align:start position:0% have now is the validation and the 00:17:12.319 --> 00:17:14.470 align:start position:0% have now is the validation and the processing<00:17:12.760> of<00:17:12.919> blocks<00:17:13.280> are<00:17:13.839> you<00:17:14.000> know<00:17:14.160> like 00:17:14.470 --> 00:17:14.480 align:start position:0% processing of blocks are you know like 00:17:14.480 --> 00:17:16.110 align:start position:0% processing of blocks are you know like interwin<00:17:15.360> they're<00:17:15.520> they're<00:17:15.679> one<00:17:15.799> and<00:17:15.959> the 00:17:16.110 --> 00:17:16.120 align:start position:0% interwin they're they're one and the 00:17:16.120 --> 00:17:18.390 align:start position:0% interwin they're they're one and the same<00:17:16.480> and<00:17:16.959> if<00:17:17.079> we<00:17:17.240> want<00:17:17.360> to<00:17:17.679> if<00:17:17.839> want<00:17:17.959> to<00:17:18.079> tweak 00:17:18.390 --> 00:17:18.400 align:start position:0% same and if we want to if want to tweak 00:17:18.400 --> 00:17:20.029 align:start position:0% same and if we want to if want to tweak something<00:17:18.679> or<00:17:18.880> we<00:17:19.000> want<00:17:19.079> to<00:17:19.199> change<00:17:19.520> something 00:17:20.029 --> 00:17:20.039 align:start position:0% something or we want to change something 00:17:20.039 --> 00:17:21.829 align:start position:0% something or we want to change something it's<00:17:20.240> quite<00:17:20.720> you<00:17:20.839> know<00:17:21.199> you<00:17:21.319> need<00:17:21.520> you<00:17:21.600> need<00:17:21.720> to 00:17:21.829 --> 00:17:21.839 align:start position:0% it's quite you know you need you need to 00:17:21.839 --> 00:17:23.429 align:start position:0% it's quite you know you need you need to address<00:17:22.120> a<00:17:22.280> whole<00:17:22.640> whole<00:17:22.880> bunch<00:17:23.079> of<00:17:23.199> other 00:17:23.429 --> 00:17:23.439 align:start position:0% address a whole whole bunch of other 00:17:23.439 --> 00:17:25.309 align:start position:0% address a whole whole bunch of other code<00:17:23.679> and<00:17:23.799> we<00:17:23.919> want<00:17:24.039> to<00:17:24.439> we<00:17:24.520> want<00:17:24.679> to<00:17:24.880> clearly 00:17:25.309 --> 00:17:25.319 align:start position:0% code and we want to we want to clearly 00:17:25.319 --> 00:17:27.390 align:start position:0% code and we want to we want to clearly separate<00:17:25.720> the<00:17:25.839> two<00:17:26.079> from<00:17:26.240> each<00:17:26.360> other<00:17:27.039> so<00:17:27.319> this 00:17:27.390 --> 00:17:27.400 align:start position:0% separate the two from each other so this 00:17:27.400 --> 00:17:30.190 align:start position:0% separate the two from each other so this is<00:17:27.480> going<00:17:27.559> to<00:17:27.640> be<00:17:27.799> especially<00:17:29.160> um<00:17:29.480> develop<00:17:29.919> for 00:17:30.190 --> 00:17:30.200 align:start position:0% is going to be especially um develop for 00:17:30.200 --> 00:17:32.470 align:start position:0% is going to be especially um develop for Casper<00:17:31.200> um<00:17:31.559> because<00:17:31.840> Casper<00:17:32.160> is<00:17:32.240> going<00:17:32.360> to 00:17:32.470 --> 00:17:32.480 align:start position:0% Casper um because Casper is going to 00:17:32.480 --> 00:17:33.870 align:start position:0% Casper um because Casper is going to require<00:17:32.960> several<00:17:33.280> other<00:17:33.559> different 00:17:33.870 --> 00:17:33.880 align:start position:0% require several other different 00:17:33.880 --> 00:17:35.750 align:start position:0% require several other different components<00:17:34.600> or<00:17:34.760> you<00:17:34.840> want<00:17:34.960> to<00:17:35.120> Simply<00:17:35.440> switch 00:17:35.750 --> 00:17:35.760 align:start position:0% components or you want to Simply switch 00:17:35.760 --> 00:17:37.470 align:start position:0% components or you want to Simply switch out<00:17:35.919> the<00:17:36.000> validation<00:17:36.480> or<00:17:36.600> the<00:17:36.760> processing<00:17:37.280> and 00:17:37.470 --> 00:17:37.480 align:start position:0% out the validation or the processing and 00:17:37.480 --> 00:17:40.870 align:start position:0% out the validation or the processing and and<00:17:37.679> put<00:17:37.880> something<00:17:38.120> else<00:17:38.360> back<00:17:38.520> in<00:17:38.760> place<00:17:39.880> and 00:17:40.870 --> 00:17:40.880 align:start position:0% and put something else back in place and 00:17:40.880 --> 00:17:42.950 align:start position:0% and put something else back in place and as<00:17:41.039> a<00:17:41.240> side<00:17:41.520> effect<00:17:41.880> it<00:17:42.000> actually<00:17:42.280> becomes 00:17:42.950 --> 00:17:42.960 align:start position:0% as a side effect it actually becomes 00:17:42.960 --> 00:17:47.190 align:start position:0% as a side effect it actually becomes quite<00:17:43.960> uh<00:17:44.240> easy<00:17:44.919> to<00:17:45.320> develop<00:17:45.679> your<00:17:46.000> own<00:17:47.000> uh 00:17:47.190 --> 00:17:47.200 align:start position:0% quite uh easy to develop your own uh 00:17:47.200 --> 00:17:48.590 align:start position:0% quite uh easy to develop your own uh your<00:17:47.320> own<00:17:47.600> private<00:17:47.880> chain<00:17:48.160> with<00:17:48.320> your<00:17:48.400> own 00:17:48.590 --> 00:17:48.600 align:start position:0% your own private chain with your own 00:17:48.600 --> 00:17:50.950 align:start position:0% your own private chain with your own custom<00:17:49.000> rules<00:17:49.880> um<00:17:50.000> so<00:17:50.240> for<00:17:50.400> perhaps<00:17:50.720> if<00:17:50.799> you 00:17:50.950 --> 00:17:50.960 align:start position:0% custom rules um so for perhaps if you 00:17:50.960 --> 00:17:52.909 align:start position:0% custom rules um so for perhaps if you you<00:17:51.039> know<00:17:51.160> for<00:17:51.280> example<00:17:51.559> if<00:17:51.640> you<00:17:51.760> have<00:17:51.880> a<00:17:52.679> uh<00:17:52.799> if 00:17:52.909 --> 00:17:52.919 align:start position:0% you know for example if you have a uh if 00:17:52.919 --> 00:17:54.310 align:start position:0% you know for example if you have a uh if you<00:17:53.000> want<00:17:53.120> to<00:17:53.200> lay<00:17:53.440> down<00:17:53.559> a<00:17:53.760> network<00:17:54.080> in<00:17:54.200> your 00:17:54.310 --> 00:17:54.320 align:start position:0% you want to lay down a network in your 00:17:54.320 --> 00:17:56.870 align:start position:0% you want to lay down a network in your own<00:17:54.919> uh<00:17:55.080> company<00:17:55.440> or<00:17:55.600> an<00:17:55.760> organization<00:17:56.679> uh<00:17:56.760> you 00:17:56.870 --> 00:17:56.880 align:start position:0% own uh company or an organization uh you 00:17:56.880 --> 00:17:58.549 align:start position:0% own uh company or an organization uh you can<00:17:57.000> take<00:17:57.200> the<00:17:57.320> code<00:17:57.679> you<00:17:57.760> can<00:17:57.960> switch<00:17:58.280> out<00:17:58.440> the 00:17:58.549 --> 00:17:58.559 align:start position:0% can take the code you can switch out the 00:17:58.559 --> 00:18:00.590 align:start position:0% can take the code you can switch out the fellow<00:17:58.799> valtion<00:17:59.600> and<00:17:59.720> the<00:17:59.919> processing<00:18:00.360> I<00:18:00.440> mean 00:18:00.590 --> 00:18:00.600 align:start position:0% fellow valtion and the processing I mean 00:18:00.600 --> 00:18:01.950 align:start position:0% fellow valtion and the processing I mean obviously<00:18:00.919> you<00:18:01.000> need<00:18:01.120> to<00:18:01.200> be<00:18:01.320> a<00:18:01.400> developer<00:18:01.799> to 00:18:01.950 --> 00:18:01.960 align:start position:0% obviously you need to be a developer to 00:18:01.960 --> 00:18:03.950 align:start position:0% obviously you need to be a developer to do<00:18:02.120> that<00:18:02.559> uh<00:18:02.679> you<00:18:02.799> need<00:18:02.960> to<00:18:03.360> develop<00:18:03.679> your<00:18:03.799> own 00:18:03.950 --> 00:18:03.960 align:start position:0% do that uh you need to develop your own 00:18:03.960 --> 00:18:05.470 align:start position:0% do that uh you need to develop your own rules<00:18:04.240> but<00:18:04.360> if<00:18:04.440> you<00:18:04.559> want<00:18:04.640> to<00:18:05.039> if<00:18:05.120> you<00:18:05.240> want<00:18:05.320> to 00:18:05.470 --> 00:18:05.480 align:start position:0% rules but if you want to if you want to 00:18:05.480 --> 00:18:07.110 align:start position:0% rules but if you want to if you want to take<00:18:05.640> that<00:18:05.840> apart<00:18:06.159> and<00:18:06.320> and<00:18:06.440> Implement<00:18:06.880> some 00:18:07.110 --> 00:18:07.120 align:start position:0% take that apart and and Implement some 00:18:07.120 --> 00:18:08.669 align:start position:0% take that apart and and Implement some some<00:18:07.240> other<00:18:07.440> rules<00:18:07.760> then<00:18:07.960> you<00:18:08.080> can<00:18:08.200> do<00:18:08.400> that 00:18:08.669 --> 00:18:08.679 align:start position:0% some other rules then you can do that 00:18:08.679 --> 00:18:10.669 align:start position:0% some other rules then you can do that quite<00:18:08.919> easily<00:18:09.919> uh<00:18:10.039> but<00:18:10.200> that<00:18:10.320> that<00:18:10.400> would<00:18:10.520> be 00:18:10.669 --> 00:18:10.679 align:start position:0% quite easily uh but that that would be 00:18:10.679 --> 00:18:13.310 align:start position:0% quite easily uh but that that would be that's<00:18:10.840> a<00:18:10.960> nice<00:18:11.200> side<00:18:11.799> effect<00:18:12.799> and<00:18:13.120> uh<00:18:13.240> the 00:18:13.310 --> 00:18:13.320 align:start position:0% that's a nice side effect and uh the 00:18:13.320 --> 00:18:14.510 align:start position:0% that's a nice side effect and uh the other<00:18:13.520> thing<00:18:13.679> that<00:18:13.840> we<00:18:14.080> that<00:18:14.200> we've<00:18:14.400> been 00:18:14.510 --> 00:18:14.520 align:start position:0% other thing that we that we've been 00:18:14.520 --> 00:18:16.870 align:start position:0% other thing that we that we've been working<00:18:14.919> on<00:18:15.440> and<00:18:15.559> this<00:18:15.799> functions<00:18:16.240> more<00:18:16.440> as<00:18:16.600> a 00:18:16.870 --> 00:18:16.880 align:start position:0% working on and this functions more as a 00:18:16.880 --> 00:18:19.630 align:start position:0% working on and this functions more as a foundation<00:18:17.480> for<00:18:17.720> the<00:18:18.080> uh<00:18:18.200> for<00:18:18.360> the<00:18:18.480> future<00:18:19.400> of 00:18:19.630 --> 00:18:19.640 align:start position:0% foundation for the uh for the future of 00:18:19.640 --> 00:18:22.190 align:start position:0% foundation for the uh for the future of the<00:18:19.919> uh<00:18:20.039> of<00:18:20.159> the 00:18:22.190 --> 00:18:22.200 align:start position:0% the uh of the 00:18:22.200 --> 00:18:24.710 align:start position:0% the uh of the evm<00:18:23.200> um<00:18:23.400> which<00:18:23.520> is<00:18:23.640> the<00:18:23.799> jet<00:18:24.000> evm<00:18:24.400> so<00:18:24.520> there<00:18:24.600> is 00:18:24.710 --> 00:18:24.720 align:start position:0% evm um which is the jet evm so there is 00:18:24.720 --> 00:18:26.430 align:start position:0% evm um which is the jet evm so there is not<00:18:24.840> to<00:18:24.919> be<00:18:25.080> confused<00:18:25.480> with<00:18:25.600> the<00:18:25.720> jet<00:18:25.919> VM<00:18:26.280> that 00:18:26.430 --> 00:18:26.440 align:start position:0% not to be confused with the jet VM that 00:18:26.440 --> 00:18:31.430 align:start position:0% not to be confused with the jet VM that was<00:18:26.640> done<00:18:27.120> in<00:18:27.480> C++<00:18:28.360> by<00:18:28.960> uh<00:18:29.120> by<00:18:29.480> Paul<00:18:30.480> um<00:18:30.880> this<00:18:31.039> is 00:18:31.430 --> 00:18:31.440 align:start position:0% was done in C++ by uh by Paul um this is 00:18:31.440 --> 00:18:33.350 align:start position:0% was done in C++ by uh by Paul um this is something<00:18:31.799> that<00:18:31.960> was<00:18:32.120> developed<00:18:32.600> in<00:18:32.840> in<00:18:33.000> go 00:18:33.350 --> 00:18:33.360 align:start position:0% something that was developed in in go 00:18:33.360 --> 00:18:36.390 align:start position:0% something that was developed in in go itself<00:18:34.360> um<00:18:35.039> it<00:18:35.159> kind<00:18:35.280> of<00:18:35.360> what<00:18:35.480> it<00:18:35.559> does<00:18:35.760> it<00:18:36.280> it 00:18:36.390 --> 00:18:36.400 align:start position:0% itself um it kind of what it does it it 00:18:36.400 --> 00:18:38.710 align:start position:0% itself um it kind of what it does it it analyzes<00:18:37.200> the<00:18:37.600> uh<00:18:37.720> the<00:18:37.840> code<00:18:38.080> in<00:18:38.200> the<00:18:38.360> contract 00:18:38.710 --> 00:18:38.720 align:start position:0% analyzes the uh the code in the contract 00:18:38.720 --> 00:18:40.590 align:start position:0% analyzes the uh the code in the contract it<00:18:38.880> takes<00:18:39.039> it<00:18:39.159> out<00:18:39.400> and<00:18:39.600> and<00:18:40.159> kind<00:18:40.280> of<00:18:40.440> like 00:18:40.590 --> 00:18:40.600 align:start position:0% it takes it out and and kind of like 00:18:40.600 --> 00:18:42.750 align:start position:0% it takes it out and and kind of like looks<00:18:41.080> looks<00:18:41.320> it<00:18:41.480> looks<00:18:41.679> at<00:18:41.799> it<00:18:42.000> analyz<00:18:42.440> it<00:18:42.600> and 00:18:42.750 --> 00:18:42.760 align:start position:0% looks looks it looks at it analyz it and 00:18:42.760 --> 00:18:44.870 align:start position:0% looks looks it looks at it analyz it and and<00:18:42.919> tries<00:18:43.200> to<00:18:43.640> uh<00:18:43.760> put<00:18:43.919> it<00:18:44.039> in<00:18:44.200> a<00:18:44.559> in<00:18:44.679> a 00:18:44.870 --> 00:18:44.880 align:start position:0% and tries to uh put it in a in a 00:18:44.880 --> 00:18:46.350 align:start position:0% and tries to uh put it in a in a different<00:18:45.200> language<00:18:45.600> so<00:18:45.760> that<00:18:45.919> it<00:18:46.039> can<00:18:46.200> be 00:18:46.350 --> 00:18:46.360 align:start position:0% different language so that it can be 00:18:46.360 --> 00:18:48.390 align:start position:0% different language so that it can be more<00:18:46.600> easily<00:18:46.960> understood<00:18:47.600> by<00:18:48.000> uh<00:18:48.159> by<00:18:48.280> a 00:18:48.390 --> 00:18:48.400 align:start position:0% more easily understood by uh by a 00:18:48.400 --> 00:18:50.870 align:start position:0% more easily understood by uh by a machine<00:18:49.400> uh<00:18:49.520> and<00:18:49.720> by<00:18:50.320> because<00:18:50.520> of<00:18:50.640> that 00:18:50.870 --> 00:18:50.880 align:start position:0% machine uh and by because of that 00:18:50.880 --> 00:18:53.070 align:start position:0% machine uh and by because of that process<00:18:51.200> it<00:18:51.400> can<00:18:51.840> it<00:18:51.960> can<00:18:52.159> analyze<00:18:52.600> certain 00:18:53.070 --> 00:18:53.080 align:start position:0% process it can it can analyze certain 00:18:53.080 --> 00:18:55.070 align:start position:0% process it can it can analyze certain segments<00:18:53.559> of<00:18:53.679> the<00:18:53.840> code<00:18:54.159> and<00:18:54.520> and<00:18:54.640> look<00:18:54.840> at<00:18:54.960> it 00:18:55.070 --> 00:18:55.080 align:start position:0% segments of the code and and look at it 00:18:55.080 --> 00:18:56.789 align:start position:0% segments of the code and and look at it and<00:18:55.159> say<00:18:55.440> well<00:18:55.840> here<00:18:55.960> we<00:18:56.080> go<00:18:56.280> we've<00:18:56.440> we've<00:18:56.600> seen 00:18:56.789 --> 00:18:56.799 align:start position:0% and say well here we go we've we've seen 00:18:56.799 --> 00:18:58.909 align:start position:0% and say well here we go we've we've seen it<00:18:56.960> before<00:18:57.320> we<00:18:57.440> we<00:18:57.559> can<00:18:57.720> optimize<00:18:58.159> it<00:18:58.520> we<00:18:58.799> can 00:18:58.909 --> 00:18:58.919 align:start position:0% it before we we can optimize it we can 00:18:58.919 --> 00:19:00.950 align:start position:0% it before we we can optimize it we can run<00:18:59.080> it<00:18:59.240> quicker<00:18:59.840> and<00:19:00.000> this<00:19:00.080> is<00:19:00.200> going<00:19:00.320> to<00:19:00.520> help 00:19:00.950 --> 00:19:00.960 align:start position:0% run it quicker and this is going to help 00:19:00.960 --> 00:19:04.549 align:start position:0% run it quicker and this is going to help with<00:19:01.720> uh<00:19:02.360> uh<00:19:02.480> the<00:19:02.799> scalability<00:19:03.799> um<00:19:04.080> for<00:19:04.440> for 00:19:04.549 --> 00:19:04.559 align:start position:0% with uh uh the scalability um for for 00:19:04.559 --> 00:19:06.590 align:start position:0% with uh uh the scalability um for for the<00:19:04.799> processing<00:19:05.280> for<00:19:05.440> the<00:19:05.600> processing<00:19:06.080> part 00:19:06.590 --> 00:19:06.600 align:start position:0% the processing for the processing part 00:19:06.600 --> 00:19:09.110 align:start position:0% the processing for the processing part now<00:19:07.120> all<00:19:07.240> of<00:19:07.360> the<00:19:07.720> optimizations<00:19:08.720> um<00:19:08.880> haven't 00:19:09.110 --> 00:19:09.120 align:start position:0% now all of the optimizations um haven't 00:19:09.120 --> 00:19:10.669 align:start position:0% now all of the optimizations um haven't been<00:19:09.320> done<00:19:09.559> so<00:19:09.720> it's<00:19:09.880> only<00:19:10.280> the<00:19:10.480> the 00:19:10.669 --> 00:19:10.679 align:start position:0% been done so it's only the the 00:19:10.679 --> 00:19:13.270 align:start position:0% been done so it's only the the foundation<00:19:11.240> on<00:19:11.480> which<00:19:11.600> we<00:19:11.720> can<00:19:11.960> build<00:19:12.760> and<00:19:13.120> uh 00:19:13.270 --> 00:19:13.280 align:start position:0% foundation on which we can build and uh 00:19:13.280 --> 00:19:15.190 align:start position:0% foundation on which we can build and uh optimize<00:19:13.679> further<00:19:14.080> so<00:19:14.520> uh<00:19:14.760> we<00:19:14.880> want<00:19:15.080> don't 00:19:15.190 --> 00:19:15.200 align:start position:0% optimize further so uh we want don't 00:19:15.200 --> 00:19:16.430 align:start position:0% optimize further so uh we want don't want<00:19:15.320> to<00:19:15.400> do<00:19:15.559> this<00:19:15.720> now<00:19:15.960> because<00:19:16.159> that<00:19:16.280> would 00:19:16.430 --> 00:19:16.440 align:start position:0% want to do this now because that would 00:19:16.440 --> 00:19:19.070 align:start position:0% want to do this now because that would be<00:19:16.640> premature<00:19:17.080> optimization<00:19:17.720> is<00:19:18.080> something 00:19:19.070 --> 00:19:19.080 align:start position:0% be premature optimization is something 00:19:19.080 --> 00:19:24.590 align:start position:0% be premature optimization is something um<00:19:19.600> we<00:19:19.720> don't<00:19:19.919> like<00:19:20.080> to<00:19:20.200> do<00:19:21.200> um<00:19:21.760> so<00:19:22.200> oh<00:19:22.960> sorry<00:19:23.960> um 00:19:24.590 --> 00:19:24.600 align:start position:0% um we don't like to do um so oh sorry um 00:19:24.600 --> 00:19:25.950 align:start position:0% um we don't like to do um so oh sorry um the<00:19:24.720> other<00:19:24.880> thing<00:19:25.039> that<00:19:25.159> we<00:19:25.280> want<00:19:25.360> to<00:19:25.520> touch<00:19:25.720> on 00:19:25.950 --> 00:19:25.960 align:start position:0% the other thing that we want to touch on 00:19:25.960 --> 00:19:29.710 align:start position:0% the other thing that we want to touch on is<00:19:26.159> the<00:19:26.679> um<00:19:26.960> Improvement<00:19:27.679> on<00:19:28.520> uh<00:19:28.880> a<00:19:29.039> code 00:19:29.710 --> 00:19:29.720 align:start position:0% is the um Improvement on uh a code 00:19:29.720 --> 00:19:32.110 align:start position:0% is the um Improvement on uh a code coverage<00:19:30.720> um<00:19:31.240> have<00:19:31.360> to<00:19:31.600> give<00:19:31.720> a<00:19:31.799> bit<00:19:31.919> of<00:19:32.000> an 00:19:32.110 --> 00:19:32.120 align:start position:0% coverage um have to give a bit of an 00:19:32.120 --> 00:19:33.590 align:start position:0% coverage um have to give a bit of an explanation<00:19:32.559> on<00:19:32.720> how<00:19:32.880> we<00:19:33.080> how<00:19:33.200> we<00:19:33.320> started 00:19:33.590 --> 00:19:33.600 align:start position:0% explanation on how we how we started 00:19:33.600 --> 00:19:36.870 align:start position:0% explanation on how we how we started this<00:19:33.760> whole<00:19:34.000> process<00:19:34.720> from<00:19:35.000> pc1<00:19:35.919> we<00:19:36.720> there 00:19:36.870 --> 00:19:36.880 align:start position:0% this whole process from pc1 we there 00:19:36.880 --> 00:19:39.230 align:start position:0% this whole process from pc1 we there like<00:19:37.080> has<00:19:37.200> been<00:19:37.320> an<00:19:37.520> iterative<00:19:38.080> process<00:19:38.600> on<00:19:39.080> uh 00:19:39.230 --> 00:19:39.240 align:start position:0% like has been an iterative process on uh 00:19:39.240 --> 00:19:40.870 align:start position:0% like has been an iterative process on uh improving<00:19:39.640> the<00:19:39.799> code<00:19:40.000> and<00:19:40.120> changing<00:19:40.480> the<00:19:40.640> code 00:19:40.870 --> 00:19:40.880 align:start position:0% improving the code and changing the code 00:19:40.880 --> 00:19:42.750 align:start position:0% improving the code and changing the code and<00:19:41.000> and<00:19:41.159> trying<00:19:41.440> out<00:19:41.640> new<00:19:41.919> things<00:19:42.559> and 00:19:42.750 --> 00:19:42.760 align:start position:0% and and trying out new things and 00:19:42.760 --> 00:19:45.070 align:start position:0% and and trying out new things and because<00:19:42.960> of<00:19:43.200> that<00:19:43.360> we<00:19:43.559> kind<00:19:43.679> of<00:19:43.799> been<00:19:44.360> sloppy 00:19:45.070 --> 00:19:45.080 align:start position:0% because of that we kind of been sloppy 00:19:45.080 --> 00:19:46.750 align:start position:0% because of that we kind of been sloppy on<00:19:45.720> uh<00:19:45.880> on 00:19:46.750 --> 00:19:46.760 align:start position:0% on uh on 00:19:46.760 --> 00:19:48.789 align:start position:0% on uh on testing<00:19:47.760> that<00:19:47.880> means<00:19:48.080> that<00:19:48.240> some<00:19:48.440> part<00:19:48.600> of<00:19:48.679> the 00:19:48.789 --> 00:19:48.799 align:start position:0% testing that means that some part of the 00:19:48.799 --> 00:19:52.390 align:start position:0% testing that means that some part of the code<00:19:49.080> are<00:19:49.280> are<00:19:49.440> simply<00:19:49.840> left<00:19:50.840> uh<00:19:51.240> untested<00:19:52.240> and 00:19:52.390 --> 00:19:52.400 align:start position:0% code are are simply left uh untested and 00:19:52.400 --> 00:19:55.070 align:start position:0% code are are simply left uh untested and thankfully<00:19:53.280> um<00:19:53.600> kristofh<00:19:54.080> came<00:19:54.240> along<00:19:54.480> and<00:19:54.720> he 00:19:55.070 --> 00:19:55.080 align:start position:0% thankfully um kristofh came along and he 00:19:55.080 --> 00:19:57.630 align:start position:0% thankfully um kristofh came along and he was<00:19:55.360> he<00:19:55.480> has<00:19:55.640> been<00:19:55.799> developing<00:19:56.320> a<00:19:56.640> generic 00:19:57.630 --> 00:19:57.640 align:start position:0% was he has been developing a generic 00:19:57.640 --> 00:20:00.630 align:start position:0% was he has been developing a generic Json<00:19:58.159> testing<00:19:59.039> which<00:19:59.520> you<00:19:59.679> know<00:20:00.039> just<00:20:00.559> it 00:20:00.630 --> 00:20:00.640 align:start position:0% Json testing which you know just it 00:20:00.640 --> 00:20:02.310 align:start position:0% Json testing which you know just it works<00:20:00.880> like<00:20:01.000> an<00:20:01.120> end<00:20:01.280> to<00:20:01.400> end<00:20:01.600> test<00:20:01.799> so<00:20:02.200> you 00:20:02.310 --> 00:20:02.320 align:start position:0% works like an end to end test so you 00:20:02.320 --> 00:20:03.870 align:start position:0% works like an end to end test so you shove<00:20:02.600> some<00:20:02.799> data<00:20:03.039> in<00:20:03.200> and<00:20:03.400> and<00:20:03.520> you<00:20:03.679> get<00:20:03.760> you 00:20:03.870 --> 00:20:03.880 align:start position:0% shove some data in and and you get you 00:20:03.880 --> 00:20:06.470 align:start position:0% shove some data in and and you get you get<00:20:03.960> a<00:20:04.120> result<00:20:04.440> out<00:20:05.320> um<00:20:05.880> and<00:20:06.159> all<00:20:06.280> of<00:20:06.400> the 00:20:06.470 --> 00:20:06.480 align:start position:0% get a result out um and all of the 00:20:06.480 --> 00:20:09.029 align:start position:0% get a result out um and all of the clients<00:20:06.840> need<00:20:07.000> to<00:20:07.159> pass<00:20:07.520> those<00:20:07.840> tests<00:20:08.679> um<00:20:08.880> if 00:20:09.029 --> 00:20:09.039 align:start position:0% clients need to pass those tests um if 00:20:09.039 --> 00:20:10.230 align:start position:0% clients need to pass those tests um if they<00:20:09.159> don't<00:20:09.400> then<00:20:09.520> it<00:20:09.640> means<00:20:09.880> there<00:20:10.000> is<00:20:10.120> a 00:20:10.230 --> 00:20:10.240 align:start position:0% they don't then it means there is a 00:20:10.240 --> 00:20:12.470 align:start position:0% they don't then it means there is a consensus<00:20:10.760> issue<00:20:11.440> um<00:20:11.520> but<00:20:11.640> it<00:20:11.760> doesn't<00:20:12.360> it 00:20:12.470 --> 00:20:12.480 align:start position:0% consensus issue um but it doesn't it 00:20:12.480 --> 00:20:14.789 align:start position:0% consensus issue um but it doesn't it doesn't<00:20:12.919> it<00:20:13.039> doesn't<00:20:13.480> doesn't<00:20:13.799> test<00:20:14.200> the 00:20:14.789 --> 00:20:14.799 align:start position:0% doesn't it doesn't doesn't test the 00:20:14.799 --> 00:20:18.110 align:start position:0% doesn't it doesn't doesn't test the specific<00:20:15.400> parts<00:20:16.280> of<00:20:16.559> the<00:20:17.159> uh<00:20:17.679> the<00:20:17.840> of<00:20:17.960> the 00:20:18.110 --> 00:20:18.120 align:start position:0% specific parts of the uh the of the 00:20:18.120 --> 00:20:20.909 align:start position:0% specific parts of the uh the of the entire<00:20:18.559> chain<00:20:19.000> so<00:20:19.240> some<00:20:19.480> parts<00:20:19.799> are<00:20:20.600> while 00:20:20.909 --> 00:20:20.919 align:start position:0% entire chain so some parts are while 00:20:20.919 --> 00:20:22.510 align:start position:0% entire chain so some parts are while while<00:20:21.080> being<00:20:21.360> tested<00:20:21.760> by<00:20:21.919> the<00:20:22.000> end<00:20:22.200> to<00:20:22.280> endend 00:20:22.510 --> 00:20:22.520 align:start position:0% while being tested by the end to endend 00:20:22.520 --> 00:20:24.590 align:start position:0% while being tested by the end to endend test<00:20:23.159> we<00:20:23.360> we<00:20:23.520> we<00:20:23.640> can't<00:20:23.880> really<00:20:24.080> test<00:20:24.360> those 00:20:24.590 --> 00:20:24.600 align:start position:0% test we we we can't really test those 00:20:24.600 --> 00:20:26.470 align:start position:0% test we we we can't really test those specific<00:20:25.000> little<00:20:25.600> Parts<00:20:25.840> in<00:20:25.960> the<00:20:26.120> chain<00:20:26.360> and 00:20:26.470 --> 00:20:26.480 align:start position:0% specific little Parts in the chain and 00:20:26.480 --> 00:20:27.750 align:start position:0% specific little Parts in the chain and that's<00:20:26.640> something<00:20:26.880> that<00:20:27.000> we<00:20:27.120> do<00:20:27.280> want<00:20:27.440> to<00:20:27.559> test 00:20:27.750 --> 00:20:27.760 align:start position:0% that's something that we do want to test 00:20:27.760 --> 00:20:30.549 align:start position:0% that's something that we do want to test so<00:20:27.960> we<00:20:28.240> want<00:20:28.360> to<00:20:28.880> some<00:20:29.480> uh<00:20:29.760> you<00:20:29.880> know 00:20:30.549 --> 00:20:30.559 align:start position:0% so we want to some uh you know 00:20:30.559 --> 00:20:33.710 align:start position:0% so we want to some uh you know implementation<00:20:31.480> specific<00:20:32.080> tests<00:20:33.080> uh<00:20:33.200> for<00:20:33.480> the 00:20:33.710 --> 00:20:33.720 align:start position:0% implementation specific tests uh for the 00:20:33.720 --> 00:20:35.990 align:start position:0% implementation specific tests uh for the go<00:20:33.960> etherum<00:20:34.520> implementation<00:20:35.520> so<00:20:35.720> what<00:20:35.840> we 00:20:35.990 --> 00:20:36.000 align:start position:0% go etherum implementation so what we 00:20:36.000 --> 00:20:38.149 align:start position:0% go etherum implementation so what we have<00:20:36.200> currently<00:20:37.000> using<00:20:37.240> the<00:20:37.440> state<00:20:37.679> t<00:20:37.919> is<00:20:38.000> a 00:20:38.149 --> 00:20:38.159 align:start position:0% have currently using the state t is a 00:20:38.159 --> 00:20:41.190 align:start position:0% have currently using the state t is a 51%<00:20:38.960> coverage<00:20:39.960> um<00:20:40.080> so<00:20:40.280> this<00:20:40.400> is<00:20:40.559> only<00:20:40.919> using 00:20:41.190 --> 00:20:41.200 align:start position:0% 51% coverage um so this is only using 00:20:41.200 --> 00:20:43.669 align:start position:0% 51% coverage um so this is only using the<00:20:41.360> Json<00:20:41.799> tests<00:20:42.799> um<00:20:43.080> and<00:20:43.240> we<00:20:43.360> have<00:20:43.520> been 00:20:43.669 --> 00:20:43.679 align:start position:0% the Json tests um and we have been 00:20:43.679 --> 00:20:47.470 align:start position:0% the Json tests um and we have been writing<00:20:44.679> um<00:20:45.039> the<00:20:45.440> the<00:20:45.600> go<00:20:45.880> test<00:20:46.320> itself<00:20:47.320> um 00:20:47.470 --> 00:20:47.480 align:start position:0% writing um the the go test itself um 00:20:47.480 --> 00:20:50.070 align:start position:0% writing um the the go test itself um which<00:20:47.679> covers<00:20:48.240> about<00:20:48.600> 65%<00:20:49.440> but<00:20:49.640> we<00:20:49.760> need<00:20:49.919> to 00:20:50.070 --> 00:20:50.080 align:start position:0% which covers about 65% but we need to 00:20:50.080 --> 00:20:52.669 align:start position:0% which covers about 65% but we need to get<00:20:50.200> that<00:20:50.400> up<00:20:50.520> to<00:20:50.960> uh<00:20:51.080> to<00:20:51.280> at<00:20:51.440> least<00:20:52.240> uh<00:20:52.320> to<00:20:52.520> at 00:20:52.669 --> 00:20:52.679 align:start position:0% get that up to uh to at least uh to at 00:20:52.679 --> 00:20:55.549 align:start position:0% get that up to uh to at least uh to at least 00:20:55.549 --> 00:20:55.559 align:start position:0% 00:20:55.559 --> 00:20:57.990 align:start position:0% 80%<00:20:56.559> now<00:20:56.840> the<00:20:57.080> uh<00:20:57.200> the<00:20:57.320> task<00:20:57.559> that<00:20:57.679> we<00:20:57.760> wrote 00:20:57.990 --> 00:20:58.000 align:start position:0% 80% now the uh the task that we wrote 00:20:58.000 --> 00:21:00.390 align:start position:0% 80% now the uh the task that we wrote for<00:20:58.120> the<00:20:58.240> VM<00:20:58.640> itself<00:20:59.000> so<00:20:59.159> this<00:20:59.320> is<00:20:59.760> just<00:20:59.960> the 00:21:00.390 --> 00:21:00.400 align:start position:0% for the VM itself so this is just the 00:21:00.400 --> 00:21:03.909 align:start position:0% for the VM itself so this is just the the<00:21:00.520> execution<00:21:01.039> part<00:21:01.280> it's<00:21:01.520> about<00:21:02.120> 60%<00:21:03.120> um<00:21:03.280> 80% 00:21:03.909 --> 00:21:03.919 align:start position:0% the execution part it's about 60% um 80% 00:21:03.919 --> 00:21:06.230 align:start position:0% the execution part it's about 60% um 80% because<00:21:04.320> the<00:21:04.559> the<00:21:04.720> jit<00:21:04.960> VM<00:21:05.640> so<00:21:05.880> when<00:21:06.000> when<00:21:06.120> you 00:21:06.230 --> 00:21:06.240 align:start position:0% because the the jit VM so when when you 00:21:06.240 --> 00:21:09.310 align:start position:0% because the the jit VM so when when you run<00:21:06.440> the<00:21:06.640> tests<00:21:07.200> the<00:21:08.120> um<00:21:08.640> you<00:21:08.760> only<00:21:08.960> test<00:21:09.200> one 00:21:09.310 --> 00:21:09.320 align:start position:0% run the tests the um you only test one 00:21:09.320 --> 00:21:10.870 align:start position:0% run the tests the um you only test one of<00:21:09.440> the<00:21:09.520> two<00:21:09.720> implementation<00:21:10.360> so<00:21:10.480> you<00:21:10.559> either 00:21:10.870 --> 00:21:10.880 align:start position:0% of the two implementation so you either 00:21:10.880 --> 00:21:12.710 align:start position:0% of the two implementation so you either test<00:21:11.039> The<00:21:11.120> Bu<00:21:11.360> code<00:21:11.520> VM<00:21:11.799> or<00:21:12.080> you<00:21:12.200> test<00:21:12.400> the<00:21:12.520> jit 00:21:12.710 --> 00:21:12.720 align:start position:0% test The Bu code VM or you test the jit 00:21:12.720 --> 00:21:14.990 align:start position:0% test The Bu code VM or you test the jit VM<00:21:13.440> and<00:21:13.600> therefore<00:21:13.840> it's<00:21:14.039> 60%<00:21:14.640> because<00:21:14.840> some 00:21:14.990 --> 00:21:15.000 align:start position:0% VM and therefore it's 60% because some 00:21:15.000 --> 00:21:16.230 align:start position:0% VM and therefore it's 60% because some part<00:21:15.159> of<00:21:15.240> the<00:21:15.320> code<00:21:15.480> is<00:21:15.600> not<00:21:15.720> being<00:21:15.919> touched 00:21:16.230 --> 00:21:16.240 align:start position:0% part of the code is not being touched 00:21:16.240 --> 00:21:17.710 align:start position:0% part of the code is not being touched when<00:21:16.360> you<00:21:16.520> use<00:21:16.679> the<00:21:16.840> bite<00:21:17.080> code<00:21:17.320> or<00:21:17.480> or<00:21:17.600> your 00:21:17.710 --> 00:21:17.720 align:start position:0% when you use the bite code or or your 00:21:17.720 --> 00:21:20.390 align:start position:0% when you use the bite code or or your way<00:21:18.320> around<00:21:19.320> um<00:21:19.559> and<00:21:19.679> the<00:21:19.840> last<00:21:20.039> thing<00:21:20.200> that<00:21:20.279> I 00:21:20.390 --> 00:21:20.400 align:start position:0% way around um and the last thing that I 00:21:20.400 --> 00:21:22.789 align:start position:0% way around um and the last thing that I want<00:21:20.559> to<00:21:21.080> I<00:21:21.159> want<00:21:21.279> to<00:21:21.400> touch<00:21:21.640> on<00:21:22.159> um<00:21:22.559> this<00:21:22.679> is 00:21:22.789 --> 00:21:22.799 align:start position:0% want to I want to touch on um this is 00:21:22.799 --> 00:21:24.190 align:start position:0% want to I want to touch on um this is something<00:21:23.039> that<00:21:23.159> is<00:21:23.320> already<00:21:23.640> implemented 00:21:24.190 --> 00:21:24.200 align:start position:0% something that is already implemented 00:21:24.200 --> 00:21:27.230 align:start position:0% something that is already implemented something<00:21:24.480> that<00:21:24.600> was<00:21:24.760> done<00:21:25.080> by<00:21:25.520> uh<00:21:25.679> by<00:21:26.240> Peter 00:21:27.230 --> 00:21:27.240 align:start position:0% something that was done by uh by Peter 00:21:27.240 --> 00:21:29.230 align:start position:0% something that was done by uh by Peter is<00:21:27.440> the<00:21:27.720> uh<00:21:27.840> fast<00:21:28.080> synchronous<00:21:28.720> ation<00:21:28.880> process 00:21:29.230 --> 00:21:29.240 align:start position:0% is the uh fast synchronous ation process 00:21:29.240 --> 00:21:31.430 align:start position:0% is the uh fast synchronous ation process this<00:21:29.360> is<00:21:29.600> I<00:21:29.720> have<00:21:29.840> to<00:21:29.960> say<00:21:30.200> quite<00:21:30.440> impressive 00:21:31.430 --> 00:21:31.440 align:start position:0% this is I have to say quite impressive 00:21:31.440 --> 00:21:33.470 align:start position:0% this is I have to say quite impressive and<00:21:31.559> I<00:21:31.679> do<00:21:31.919> have<00:21:32.120> some<00:21:32.760> I<00:21:32.840> won't<00:21:33.039> go<00:21:33.159> into<00:21:33.360> too 00:21:33.470 --> 00:21:33.480 align:start position:0% and I do have some I won't go into too 00:21:33.480 --> 00:21:35.310 align:start position:0% and I do have some I won't go into too many<00:21:33.679> details<00:21:33.960> on<00:21:34.080> how<00:21:34.200> the<00:21:34.320> fasing<00:21:34.720> rization 00:21:35.310 --> 00:21:35.320 align:start position:0% many details on how the fasing rization 00:21:35.320 --> 00:21:39.350 align:start position:0% many details on how the fasing rization works<00:21:36.159> uh<00:21:36.279> but<00:21:36.400> I<00:21:36.559> do<00:21:36.760> want<00:21:36.840> to<00:21:37.440> show<00:21:37.760> off<00:21:38.360> some 00:21:39.350 --> 00:21:39.360 align:start position:0% works uh but I do want to show off some 00:21:39.360 --> 00:21:42.190 align:start position:0% works uh but I do want to show off some um<00:21:39.640> statistics<00:21:40.240> about<00:21:40.480> it<00:21:41.480> um<00:21:41.720> so<00:21:41.919> on<00:21:42.080> the 00:21:42.190 --> 00:21:42.200 align:start position:0% um statistics about it um so on the 00:21:42.200 --> 00:21:44.590 align:start position:0% um statistics about it um so on the freret<00:21:42.840> on<00:21:42.960> the<00:21:43.120> time<00:21:43.279> of<00:21:43.600> when<00:21:43.720> we<00:21:44.039> uh<00:21:44.200> when<00:21:44.320> we 00:21:44.590 --> 00:21:44.600 align:start position:0% freret on the time of when we uh when we 00:21:44.600 --> 00:21:46.669 align:start position:0% freret on the time of when we uh when we when<00:21:44.679> we<00:21:44.799> conducted<00:21:45.200> the<00:21:45.320> testing<00:21:46.320> it<00:21:46.440> had 00:21:46.669 --> 00:21:46.679 align:start position:0% when we conducted the testing it had 00:21:46.679 --> 00:21:48.950 align:start position:0% when we conducted the testing it had about<00:21:46.960> 360,000<00:21:47.960> blocks<00:21:48.440> in<00:21:48.480> the<00:21:48.600> chain<00:21:48.880> I 00:21:48.950 --> 00:21:48.960 align:start position:0% about 360,000 blocks in the chain I 00:21:48.960 --> 00:21:52.029 align:start position:0% about 360,000 blocks in the chain I think<00:21:49.080> it's<00:21:49.279> about<00:21:49.799> half<00:21:49.960> a<00:21:50.120> million<00:21:50.480> now<00:21:51.480> um 00:21:52.029 --> 00:21:52.039 align:start position:0% think it's about half a million now um 00:21:52.039 --> 00:21:54.390 align:start position:0% think it's about half a million now um so<00:21:52.200> using<00:21:52.760> using<00:21:53.120> normal<00:21:53.559> State<00:21:54.039> State 00:21:54.390 --> 00:21:54.400 align:start position:0% so using using normal State State 00:21:54.400 --> 00:21:55.830 align:start position:0% so using using normal State State Processing<00:21:54.840> where<00:21:54.960> you<00:21:55.080> start<00:21:55.360> at<00:21:55.520> zero<00:21:55.760> and 00:21:55.830 --> 00:21:55.840 align:start position:0% Processing where you start at zero and 00:21:55.840 --> 00:21:58.669 align:start position:0% Processing where you start at zero and you<00:21:55.960> go<00:21:56.120> all<00:21:56.240> the<00:21:56.320> way<00:21:56.480> to<00:21:56.840> uh<00:21:57.200> 360<00:21:58.200> uh<00:21:58.360> took 00:21:58.669 --> 00:21:58.679 align:start position:0% you go all the way to uh 360 uh took 00:21:58.679 --> 00:22:02.310 align:start position:0% you go all the way to uh 360 uh took about<00:21:58.880> 12<00:21:59.159> minutes<00:21:59.720> which<00:21:59.840> is<00:22:00.039> 1.6<00:22:00.960> GB<00:22:01.400> of<00:22:01.559> data 00:22:02.310 --> 00:22:02.320 align:start position:0% about 12 minutes which is 1.6 GB of data 00:22:02.320 --> 00:22:06.269 align:start position:0% about 12 minutes which is 1.6 GB of data um<00:22:02.480> using<00:22:03.120> the<00:22:04.120> um<00:22:04.760> using<00:22:05.080> the<00:22:05.279> fast<00:22:05.600> Sync<00:22:06.080> It's 00:22:06.269 --> 00:22:06.279 align:start position:0% um using the um using the fast Sync It's 00:22:06.279 --> 00:22:09.909 align:start position:0% um using the um using the fast Sync It's 2<00:22:06.559> minute<00:22:06.919> and<00:22:07.279> 235<00:22:08.320> megabytes<00:22:09.320> but<00:22:09.600> it's<00:22:09.799> it's 00:22:09.909 --> 00:22:09.919 align:start position:0% 2 minute and 235 megabytes but it's it's 00:22:09.919 --> 00:22:12.390 align:start position:0% 2 minute and 235 megabytes but it's it's not<00:22:10.120> really<00:22:10.520> a<00:22:11.360> it's<00:22:11.480> still<00:22:11.760> the<00:22:12.120> still<00:22:12.320> the 00:22:12.390 --> 00:22:12.400 align:start position:0% not really a it's still the still the 00:22:12.400 --> 00:22:13.630 align:start position:0% not really a it's still the still the Frontier<00:22:12.799> Net<00:22:13.000> there<00:22:13.080> are<00:22:13.200> not<00:22:13.360> many 00:22:13.630 --> 00:22:13.640 align:start position:0% Frontier Net there are not many 00:22:13.640 --> 00:22:16.390 align:start position:0% Frontier Net there are not many transactions<00:22:14.600> so<00:22:14.799> it's<00:22:15.039> quite<00:22:15.799> difficult<00:22:16.000> to 00:22:16.390 --> 00:22:16.400 align:start position:0% transactions so it's quite difficult to 00:22:16.400 --> 00:22:18.750 align:start position:0% transactions so it's quite difficult to really<00:22:17.200> fully<00:22:17.799> understand<00:22:18.080> how<00:22:18.360> fast<00:22:18.559> it 00:22:18.750 --> 00:22:18.760 align:start position:0% really fully understand how fast it 00:22:18.760 --> 00:22:21.269 align:start position:0% really fully understand how fast it really<00:22:19.000> is<00:22:19.760> um<00:22:19.919> so<00:22:20.080> we<00:22:20.200> took<00:22:20.520> the<00:22:20.880> uh<00:22:21.000> we<00:22:21.120> took 00:22:21.269 --> 00:22:21.279 align:start position:0% really is um so we took the uh we took 00:22:21.279 --> 00:22:25.149 align:start position:0% really is um so we took the uh we took the<00:22:21.440> Olympic<00:22:22.039> Network<00:22:23.039> and<00:22:23.520> um<00:22:24.440> unfortunately 00:22:25.149 --> 00:22:25.159 align:start position:0% the Olympic Network and um unfortunately 00:22:25.159 --> 00:22:26.789 align:start position:0% the Olympic Network and um unfortunately we<00:22:25.240> didn't<00:22:25.520> have<00:22:25.640> the<00:22:25.760> full<00:22:26.000> chain<00:22:26.279> so<00:22:26.440> we<00:22:26.559> only 00:22:26.789 --> 00:22:26.799 align:start position:0% we didn't have the full chain so we only 00:22:26.799 --> 00:22:28.990 align:start position:0% we didn't have the full chain so we only had<00:22:26.919> a<00:22:27.159> had<00:22:27.240> a<00:22:27.400> file<00:22:27.720> that<00:22:27.960> somebody<00:22:28.559> exported 00:22:28.990 --> 00:22:29.000 align:start position:0% had a had a file that somebody exported 00:22:29.000 --> 00:22:31.470 align:start position:0% had a had a file that somebody exported and<00:22:29.400> uploaded<00:22:29.840> in<00:22:29.919> a<00:22:30.039> bit<00:22:30.240> torrent<00:22:30.600> file<00:22:31.240> was 00:22:31.470 --> 00:22:31.480 align:start position:0% and uploaded in a bit torrent file was 00:22:31.480 --> 00:22:34.350 align:start position:0% and uploaded in a bit torrent file was about<00:22:31.720> 840,000<00:22:32.840> blocks<00:22:33.840> um<00:22:34.039> when<00:22:34.200> we 00:22:34.350 --> 00:22:34.360 align:start position:0% about 840,000 blocks um when we 00:22:34.360 --> 00:22:36.590 align:start position:0% about 840,000 blocks um when we processed<00:22:34.720> it<00:22:34.880> took<00:22:35.080> about<00:22:35.279> 4<00:22:35.520> hours<00:22:35.960> now 00:22:36.590 --> 00:22:36.600 align:start position:0% processed it took about 4 hours now 00:22:36.600 --> 00:22:38.470 align:start position:0% processed it took about 4 hours now maybe<00:22:36.840> some<00:22:37.000> of<00:22:37.120> you<00:22:37.320> remember<00:22:38.240> how 00:22:38.470 --> 00:22:38.480 align:start position:0% maybe some of you remember how 00:22:38.480 --> 00:22:41.909 align:start position:0% maybe some of you remember how incredibly<00:22:39.360> tedious<00:22:40.000> it<00:22:40.200> was<00:22:40.400> to<00:22:40.760> catch<00:22:41.039> up<00:22:41.679> on 00:22:41.909 --> 00:22:41.919 align:start position:0% incredibly tedious it was to catch up on 00:22:41.919 --> 00:22:43.909 align:start position:0% incredibly tedious it was to catch up on the<00:22:42.039> Olympic<00:22:42.440> Network<00:22:43.120> especially<00:22:43.640> with<00:22:43.799> an 00:22:43.909 --> 00:22:43.919 align:start position:0% the Olympic Network especially with an 00:22:43.919 --> 00:22:46.549 align:start position:0% the Olympic Network especially with an ARM<00:22:44.200> device<00:22:44.480> like<00:22:44.600> a<00:22:44.720> Rasberry<00:22:45.240> pie<00:22:45.880> it<00:22:46.039> was 00:22:46.549 --> 00:22:46.559 align:start position:0% ARM device like a Rasberry pie it was 00:22:46.559 --> 00:22:51.070 align:start position:0% ARM device like a Rasberry pie it was it<00:22:47.679> was<00:22:48.360> awful<00:22:49.360> um<00:22:49.640> so<00:22:49.919> but<00:22:50.080> on<00:22:50.279> on<00:22:50.400> an<00:22:50.480> i7 00:22:51.070 --> 00:22:51.080 align:start position:0% it was awful um so but on on an i7 00:22:51.080 --> 00:22:53.990 align:start position:0% it was awful um so but on on an i7 it<00:22:51.200> took<00:22:51.440> 4<00:22:51.640> hours<00:22:51.880> and<00:22:52.039> 7<00:22:52.279> Minutes<00:22:53.000> uh<00:22:53.200> 28<00:22:53.600> GB 00:22:53.990 --> 00:22:54.000 align:start position:0% it took 4 hours and 7 Minutes uh 28 GB 00:22:54.000 --> 00:22:57.029 align:start position:0% it took 4 hours and 7 Minutes uh 28 GB of<00:22:54.159> data<00:22:54.760> and<00:22:54.960> using<00:22:55.440> the<00:22:56.039> uh<00:22:56.360> using<00:22:56.640> the<00:22:56.760> fast 00:22:57.029 --> 00:22:57.039 align:start position:0% of data and using the uh using the fast 00:22:57.039 --> 00:22:59.110 align:start position:0% of data and using the uh using the fast synchronization<00:22:57.840> process<00:22:58.480> it<00:22:58.600> went<00:22:58.760> down<00:22:58.919> to 00:22:59.110 --> 00:22:59.120 align:start position:0% synchronization process it went down to 00:22:59.120 --> 00:23:01.630 align:start position:0% synchronization process it went down to 31<00:22:59.600> minutes<00:22:59.880> and<00:23:00.039> only<00:23:00.279> 3.8<00:23:00.840> GB<00:23:01.200> of<00:23:01.320> data<00:23:01.520> so 00:23:01.630 --> 00:23:01.640 align:start position:0% 31 minutes and only 3.8 GB of data so 00:23:01.640 --> 00:23:04.149 align:start position:0% 31 minutes and only 3.8 GB of data so it's<00:23:01.919> quite<00:23:02.200> a<00:23:02.880> quite<00:23:03.039> a<00:23:03.200> significant 00:23:04.149 --> 00:23:04.159 align:start position:0% it's quite a quite a significant 00:23:04.159 --> 00:23:07.269 align:start position:0% it's quite a quite a significant Improvement<00:23:05.159> um<00:23:05.679> so<00:23:05.960> that's<00:23:06.159> like<00:23:06.480> 4<00:23:06.720> minutes 00:23:07.269 --> 00:23:07.279 align:start position:0% Improvement um so that's like 4 minutes 00:23:07.279 --> 00:23:09.470 align:start position:0% Improvement um so that's like 4 minutes uh<00:23:07.400> 4<00:23:07.600> hours<00:23:07.880> for<00:23:08.200> at<00:23:08.320> 31<00:23:08.880> and<00:23:09.000> that's<00:23:09.360> uh 00:23:09.470 --> 00:23:09.480 align:start position:0% uh 4 hours for at 31 and that's uh 00:23:09.480 --> 00:23:10.669 align:start position:0% uh 4 hours for at 31 and that's uh that's<00:23:09.679> pretty 00:23:10.669 --> 00:23:10.679 align:start position:0% that's pretty 00:23:10.679 --> 00:23:13.430 align:start position:0% that's pretty awesome<00:23:11.679> um<00:23:11.799> so<00:23:11.960> that<00:23:12.080> was<00:23:12.200> it<00:23:12.320> for<00:23:12.440> the<00:23:12.559> update 00:23:13.430 --> 00:23:13.440 align:start position:0% awesome um so that was it for the update 00:23:13.440 --> 00:23:16.710 align:start position:0% awesome um so that was it for the update um<00:23:14.320> I<00:23:14.480> think<00:23:14.600> we're<00:23:14.720> going<00:23:14.799> to<00:23:14.960> go<00:23:15.159> into 00:23:16.710 --> 00:23:16.720 align:start position:0% um I think we're going to go into 00:23:16.720 --> 00:23:21.390 align:start position:0% um I think we're going to go into um<00:23:17.720> into<00:23:18.000> a<00:23:18.200> presentation<00:23:18.919> by<00:23:19.520> uh<00:23:19.880> by<00:23:20.400> Alex 00:23:21.390 --> 00:23:21.400 align:start position:0% um into a presentation by uh by Alex 00:23:21.400 --> 00:23:29.850 align:start position:0% um into a presentation by uh by Alex thank<00:23:21.559> you<00:23:21.720> very<00:23:21.919> much 00:23:29.850 --> 00:23:29.860 align:start position:0% 00:23:29.860 --> 00:23:34.029 align:start position:0% [Applause] 00:23:34.029 --> 00:23:34.039 align:start position:0% 00:23:34.039 --> 00:23:37.549 align:start position:0% okay<00:23:35.039> you<00:23:35.159> can<00:23:35.400> put<00:23:35.760> the<00:23:36.640> back<00:23:36.799> on<00:23:36.919> the<00:23:37.039> screen 00:23:37.549 --> 00:23:37.559 align:start position:0% okay you can put the back on the screen 00:23:37.559 --> 00:23:43.029 align:start position:0% okay you can put the back on the screen thank<00:23:37.720> you<00:23:38.440> so<00:23:38.679> thank<00:23:38.840> you<00:23:39.360> everyone 00:23:43.029 --> 00:23:43.039 align:start position:0% 00:23:43.039 --> 00:23:45.549 align:start position:0% so<00:23:44.039> is<00:23:44.200> not 00:23:45.549 --> 00:23:45.559 align:start position:0% so is not 00:23:45.559 --> 00:23:48.110 align:start position:0% so is not working<00:23:46.559> okay 00:23:48.110 --> 00:23:48.120 align:start position:0% working okay 00:23:48.120 --> 00:23:50.549 align:start position:0% working okay so<00:23:49.120> I'm<00:23:49.240> going<00:23:49.360> to<00:23:49.520> talk<00:23:49.760> about<00:23:50.000> this<00:23:50.240> epic 00:23:50.549 --> 00:23:50.559 align:start position:0% so I'm going to talk about this epic 00:23:50.559 --> 00:23:52.710 align:start position:0% so I'm going to talk about this epic battle<00:23:50.960> between<00:23:51.360> the<00:23:51.840> the<00:23:52.120> blockchain<00:23:52.600> and 00:23:52.710 --> 00:23:52.720 align:start position:0% battle between the the blockchain and 00:23:52.720 --> 00:23:55.549 align:start position:0% battle between the the blockchain and the<00:23:53.080> user<00:23:54.080> so<00:23:54.360> we've<00:23:54.559> been<00:23:54.760> talking<00:23:55.159> about 00:23:55.549 --> 00:23:55.559 align:start position:0% the user so we've been talking about 00:23:55.559 --> 00:23:58.029 align:start position:0% the user so we've been talking about blockchain<00:23:56.120> so<00:23:56.360> far<00:23:56.799> we<00:23:56.919> will<00:23:57.200> talk<00:23:57.480> it<00:23:57.880> the 00:23:58.029 --> 00:23:58.039 align:start position:0% blockchain so far we will talk it the 00:23:58.039 --> 00:23:59.950 align:start position:0% blockchain so far we will talk it the whole<00:23:58.480> afternoon<00:23:59.039> and<00:23:59.200> we<00:23:59.279> will<00:23:59.520> talk<00:23:59.799> the 00:23:59.950 --> 00:23:59.960 align:start position:0% whole afternoon and we will talk the 00:23:59.960 --> 00:24:02.149 align:start position:0% whole afternoon and we will talk the whole<00:24:00.200> week<00:24:01.080> and<00:24:01.240> we<00:24:01.320> will<00:24:01.520> keep<00:24:01.760> talking 00:24:02.149 --> 00:24:02.159 align:start position:0% whole week and we will keep talking 00:24:02.159 --> 00:24:04.870 align:start position:0% whole week and we will keep talking about<00:24:02.440> it<00:24:02.760> after<00:24:03.159> that<00:24:03.880> because<00:24:04.120> it's<00:24:04.279> a<00:24:04.520> very 00:24:04.870 --> 00:24:04.880 align:start position:0% about it after that because it's a very 00:24:04.880 --> 00:24:08.390 align:start position:0% about it after that because it's a very powerful<00:24:05.480> idea<00:24:06.480> build<00:24:06.960> Unstoppable 00:24:08.390 --> 00:24:08.400 align:start position:0% powerful idea build Unstoppable 00:24:08.400 --> 00:24:11.230 align:start position:0% powerful idea build Unstoppable applications<00:24:09.400> software<00:24:10.320> that<00:24:10.480> cannot<00:24:10.760> be 00:24:11.230 --> 00:24:11.240 align:start position:0% applications software that cannot be 00:24:11.240 --> 00:24:13.990 align:start position:0% applications software that cannot be censored<00:24:12.240> contracts<00:24:12.880> that<00:24:13.080> can't<00:24:13.279> be<00:24:13.440> medled 00:24:13.990 --> 00:24:14.000 align:start position:0% censored contracts that can't be medled 00:24:14.000 --> 00:24:17.990 align:start position:0% censored contracts that can't be medled with<00:24:14.760> it's<00:24:14.919> a<00:24:15.120> very<00:24:15.520> powerful<00:24:16.400> idea<00:24:17.400> but<00:24:17.760> like 00:24:17.990 --> 00:24:18.000 align:start position:0% with it's a very powerful idea but like 00:24:18.000 --> 00:24:20.310 align:start position:0% with it's a very powerful idea but like our<00:24:18.400> ideas<00:24:19.240> if<00:24:19.360> you<00:24:19.440> want<00:24:19.720> them<00:24:19.880> to<00:24:20.080> be 00:24:20.310 --> 00:24:20.320 align:start position:0% our ideas if you want them to be 00:24:20.320 --> 00:24:22.870 align:start position:0% our ideas if you want them to be successful<00:24:21.000> they<00:24:21.120> need<00:24:21.320> math<00:24:21.720> adoption<00:24:22.720> and 00:24:22.870 --> 00:24:22.880 align:start position:0% successful they need math adoption and 00:24:22.880 --> 00:24:26.070 align:start position:0% successful they need math adoption and to<00:24:23.120> get<00:24:23.400> math<00:24:23.799> adoption<00:24:24.799> you<00:24:24.960> need<00:24:25.200> to<00:24:25.440> aim<00:24:25.840> and 00:24:26.070 --> 00:24:26.080 align:start position:0% to get math adoption you need to aim and 00:24:26.080 --> 00:24:30.630 align:start position:0% to get math adoption you need to aim and to<00:24:26.880> for<00:24:27.120> a<00:24:27.520> very<00:24:28.399> is<00:24:28.600> even<00:24:28.880> mythical<00:24:29.640> creature 00:24:30.630 --> 00:24:30.640 align:start position:0% to for a very is even mythical creature 00:24:30.640 --> 00:24:33.750 align:start position:0% to for a very is even mythical creature that<00:24:30.799> we<00:24:30.960> call<00:24:31.279> them<00:24:31.880> the<00:24:32.080> average<00:24:32.760> user 00:24:33.750 --> 00:24:33.760 align:start position:0% that we call them the average user 00:24:33.760 --> 00:24:36.389 align:start position:0% that we call them the average user probably<00:24:34.159> the<00:24:34.320> most<00:24:34.559> boring<00:24:34.960> superhero<00:24:35.520> ever 00:24:36.389 --> 00:24:36.399 align:start position:0% probably the most boring superhero ever 00:24:36.399 --> 00:24:38.669 align:start position:0% probably the most boring superhero ever invented<00:24:37.399> the<00:24:37.600> problem<00:24:37.960> with<00:24:38.120> the<00:24:38.320> average 00:24:38.669 --> 00:24:38.679 align:start position:0% invented the problem with the average 00:24:38.679 --> 00:24:41.510 align:start position:0% invented the problem with the average user<00:24:39.159> is<00:24:39.360> that<00:24:39.760> everyone<00:24:40.159> has<00:24:40.360> heard<00:24:40.679> about<00:24:40.960> it 00:24:41.510 --> 00:24:41.520 align:start position:0% user is that everyone has heard about it 00:24:41.520 --> 00:24:44.470 align:start position:0% user is that everyone has heard about it everyone<00:24:41.960> talks<00:24:42.399> about<00:24:42.720> him<00:24:43.360> but<00:24:43.559> no<00:24:43.679> one<00:24:43.919> ever 00:24:44.470 --> 00:24:44.480 align:start position:0% everyone talks about him but no one ever 00:24:44.480 --> 00:24:46.190 align:start position:0% everyone talks about him but no one ever knows<00:24:44.840> who<00:24:45.000> he<00:24:45.200> is<00:24:45.600> I<00:24:45.679> mean<00:24:45.799> who<00:24:45.960> is<00:24:46.080> the 00:24:46.190 --> 00:24:46.200 align:start position:0% knows who he is I mean who is the 00:24:46.200 --> 00:24:49.269 align:start position:0% knows who he is I mean who is the average<00:24:46.520> user<00:24:47.200> is<00:24:47.320> it<00:24:47.640> my<00:24:47.840> mother<00:24:48.360> is<00:24:48.480> it<00:24:48.640> your 00:24:49.269 --> 00:24:49.279 align:start position:0% average user is it my mother is it your 00:24:49.279 --> 00:24:51.669 align:start position:0% average user is it my mother is it your grandfather<00:24:50.279> it's<00:24:50.480> certainly<00:24:50.880> not<00:24:51.120> my<00:24:51.279> mother 00:24:51.669 --> 00:24:51.679 align:start position:0% grandfather it's certainly not my mother 00:24:51.679 --> 00:24:53.789 align:start position:0% grandfather it's certainly not my mother my<00:24:51.840> mother<00:24:52.159> she<00:24:52.480> worked<00:24:52.799> with<00:24:53.000> AdSense<00:24:53.520> code 00:24:53.789 --> 00:24:53.799 align:start position:0% my mother she worked with AdSense code 00:24:53.799 --> 00:24:55.710 align:start position:0% my mother she worked with AdSense code all<00:24:54.039> day<00:24:54.200> she's<00:24:54.360> a<00:24:54.520> smart<00:24:54.840> cookie<00:24:55.200> so<00:24:55.440> she's 00:24:55.710 --> 00:24:55.720 align:start position:0% all day she's a smart cookie so she's 00:24:55.720 --> 00:24:58.789 align:start position:0% all day she's a smart cookie so she's not<00:24:56.000> it<00:24:56.600> maybe<00:24:56.799> it's<00:24:56.960> your<00:24:57.279> father<00:24:58.440> that's<00:24:58.600> the 00:24:58.789 --> 00:24:58.799 align:start position:0% not it maybe it's your father that's the 00:24:58.799 --> 00:25:01.350 align:start position:0% not it maybe it's your father that's the problem<00:24:59.159> really<00:24:59.399> if<00:24:59.559> the<00:24:59.720> average<00:25:00.000> user<00:25:00.880> he's 00:25:01.350 --> 00:25:01.360 align:start position:0% problem really if the average user he's 00:25:01.360 --> 00:25:05.470 align:start position:0% problem really if the average user he's never<00:25:01.960> really<00:25:02.440> a<00:25:02.679> single<00:25:03.360> person<00:25:04.360> he's<00:25:04.799> only 00:25:05.470 --> 00:25:05.480 align:start position:0% never really a single person he's only 00:25:05.480 --> 00:25:09.430 align:start position:0% never really a single person he's only not<00:25:06.039> a<00:25:06.240> lot<00:25:06.440> of<00:25:06.640> people<00:25:07.559> for<00:25:07.919> example<00:25:08.919> I<00:25:09.200> know 00:25:09.430 --> 00:25:09.440 align:start position:0% not a lot of people for example I know 00:25:09.440 --> 00:25:12.630 align:start position:0% not a lot of people for example I know for<00:25:09.679> a<00:25:09.960> fact<00:25:10.640> that<00:25:10.919> the<00:25:11.080> average<00:25:11.440> user<00:25:11.880> is<00:25:12.159> not 00:25:12.630 --> 00:25:12.640 align:start position:0% for a fact that the average user is not 00:25:12.640 --> 00:25:15.950 align:start position:0% for a fact that the average user is not a<00:25:13.159> developer<00:25:14.159> and<00:25:14.440> that's<00:25:14.960> what<00:25:15.279> etheron<00:25:15.840> has 00:25:15.950 --> 00:25:15.960 align:start position:0% a developer and that's what etheron has 00:25:15.960 --> 00:25:19.710 align:start position:0% a developer and that's what etheron has been<00:25:16.240> so<00:25:16.480> far<00:25:17.200> tools<00:25:17.720> for<00:25:18.240> developers<00:25:19.240> common 00:25:19.710 --> 00:25:19.720 align:start position:0% been so far tools for developers common 00:25:19.720 --> 00:25:23.070 align:start position:0% been so far tools for developers common line<00:25:20.000> tools<00:25:20.520> libraries<00:25:21.440> very<00:25:22.120> very<00:25:22.600> complex 00:25:23.070 --> 00:25:23.080 align:start position:0% line tools libraries very very complex 00:25:23.080 --> 00:25:25.389 align:start position:0% line tools libraries very very complex tools<00:25:23.440> for<00:25:23.640> building 00:25:25.389 --> 00:25:25.399 align:start position:0% tools for building 00:25:25.399 --> 00:25:28.110 align:start position:0% tools for building apps<00:25:26.399> and<00:25:26.559> we<00:25:26.679> want<00:25:26.840> to<00:25:27.039> change<00:25:27.520> that<00:25:27.840> so<00:25:28.000> we 00:25:28.110 --> 00:25:28.120 align:start position:0% apps and we want to change that so we 00:25:28.120 --> 00:25:30.830 align:start position:0% apps and we want to change that so we want<00:25:28.320> want<00:25:28.480> to<00:25:28.640> get<00:25:28.880> to<00:25:29.039> the<00:25:29.200> next<00:25:30.000> to<00:25:30.159> the<00:25:30.320> next 00:25:30.830 --> 00:25:30.840 align:start position:0% want want to get to the next to the next 00:25:30.840 --> 00:25:35.230 align:start position:0% want want to get to the next to the next average<00:25:31.679> user<00:25:32.679> but<00:25:33.480> again<00:25:33.919> who<00:25:34.200> who<00:25:34.520> is<00:25:34.799> he 00:25:35.230 --> 00:25:35.240 align:start position:0% average user but again who who is he 00:25:35.240 --> 00:25:37.830 align:start position:0% average user but again who who is he really<00:25:36.000> so<00:25:36.360> when<00:25:36.640> the<00:25:36.799> in<00:25:36.919> the<00:25:37.000> 80s<00:25:37.520> when<00:25:37.679> the 00:25:37.830 --> 00:25:37.840 align:start position:0% really so when the in the 80s when the 00:25:37.840 --> 00:25:39.950 align:start position:0% really so when the in the 80s when the Computing<00:25:38.320> Revolution<00:25:38.960> was<00:25:39.399> let's<00:25:39.640> build 00:25:39.950 --> 00:25:39.960 align:start position:0% Computing Revolution was let's build 00:25:39.960 --> 00:25:41.389 align:start position:0% Computing Revolution was let's build computer<00:25:40.399> for<00:25:40.600> the 00:25:41.389 --> 00:25:41.399 align:start position:0% computer for the 00:25:41.399 --> 00:25:44.789 align:start position:0% computer for the Mathes<00:25:42.399> what<00:25:42.600> the<00:25:42.799> maths<00:25:43.480> turned<00:25:43.840> out<00:25:44.080> to<00:25:44.279> be 00:25:44.789 --> 00:25:44.799 align:start position:0% Mathes what the maths turned out to be 00:25:44.799 --> 00:25:47.110 align:start position:0% Mathes what the maths turned out to be were<00:25:45.159> very<00:25:45.440> geeky<00:25:45.919> people<00:25:46.320> who<00:25:46.480> were<00:25:46.720> working 00:25:47.110 --> 00:25:47.120 align:start position:0% were very geeky people who were working 00:25:47.120 --> 00:25:50.470 align:start position:0% were very geeky people who were working on<00:25:47.600> word<00:25:47.960> Word<00:25:48.320> documents<00:25:48.960> spreadsheets<00:25:49.880> and 00:25:50.470 --> 00:25:50.480 align:start position:0% on word Word documents spreadsheets and 00:25:50.480 --> 00:25:53.470 align:start position:0% on word Word documents spreadsheets and desktop<00:25:51.399> publishing<00:25:52.399> that's<00:25:52.880> hardly<00:25:53.279> an 00:25:53.470 --> 00:25:53.480 align:start position:0% desktop publishing that's hardly an 00:25:53.480 --> 00:25:56.029 align:start position:0% desktop publishing that's hardly an average<00:25:53.799> user<00:25:54.200> today<00:25:55.200> but<00:25:55.360> that's<00:25:55.520> a<00:25:55.679> user 00:25:56.029 --> 00:25:56.039 align:start position:0% average user today but that's a user 00:25:56.039 --> 00:25:59.230 align:start position:0% average user today but that's a user that<00:25:56.240> still<00:25:56.760> exists<00:25:57.760> probably<00:25:58.559> it's<00:25:58.760> the<00:25:58.919> one 00:25:59.230 --> 00:25:59.240 align:start position:0% that still exists probably it's the one 00:25:59.240 --> 00:26:01.389 align:start position:0% that still exists probably it's the one that<00:25:59.520> is<00:25:59.880> everyone<00:26:00.320> here<00:26:00.520> in<00:26:00.679> this<00:26:00.880> room<00:26:01.200> is 00:26:01.389 --> 00:26:01.399 align:start position:0% that is everyone here in this room is 00:26:01.399 --> 00:26:04.510 align:start position:0% that is everyone here in this room is one<00:26:02.039> it's<00:26:02.559> one<00:26:03.000> some<00:26:03.320> someone<00:26:03.760> that<00:26:03.919> can<00:26:04.240> open 00:26:04.510 --> 00:26:04.520 align:start position:0% one it's one some someone that can open 00:26:04.520 --> 00:26:07.269 align:start position:0% one it's one some someone that can open up<00:26:04.720> an<00:26:04.880> application<00:26:05.559> and<00:26:05.760> run<00:26:06.399> uh<00:26:06.640> spreadsheet 00:26:07.269 --> 00:26:07.279 align:start position:0% up an application and run uh spreadsheet 00:26:07.279 --> 00:26:11.510 align:start position:0% up an application and run uh spreadsheet or<00:26:07.520> run<00:26:08.440> Excel<00:26:09.000> or<00:26:09.480> maybe<00:26:09.679> we<00:26:09.799> can<00:26:10.360> call<00:26:10.559> it<00:26:10.799> the 00:26:11.510 --> 00:26:11.520 align:start position:0% or run Excel or maybe we can call it the 00:26:11.520 --> 00:26:14.510 align:start position:0% or run Excel or maybe we can call it the the<00:26:11.679> modern<00:26:12.240> work<00:26:12.840> modern<00:26:13.360> office<00:26:13.720> worker<00:26:14.279> or 00:26:14.510 --> 00:26:14.520 align:start position:0% the modern work modern office worker or 00:26:14.520 --> 00:26:16.630 align:start position:0% the modern work modern office worker or just<00:26:14.679> a<00:26:14.880> power<00:26:15.159> user<00:26:15.919> I<00:26:16.000> don't<00:26:16.159> know<00:26:16.360> but<00:26:16.520> I 00:26:16.630 --> 00:26:16.640 align:start position:0% just a power user I don't know but I 00:26:16.640 --> 00:26:20.830 align:start position:0% just a power user I don't know but I think<00:26:17.480> that's<00:26:18.360> that's<00:26:18.640> one<00:26:19.039> one<00:26:19.320> go<00:26:19.880> to<00:26:20.120> have 00:26:20.830 --> 00:26:20.840 align:start position:0% think that's that's one one go to have 00:26:20.840 --> 00:26:23.310 align:start position:0% think that's that's one one go to have that's<00:26:21.080> the<00:26:21.320> person<00:26:21.760> that<00:26:21.880> is<00:26:22.039> next<00:26:22.799> after<00:26:23.120> the 00:26:23.310 --> 00:26:23.320 align:start position:0% that's the person that is next after the 00:26:23.320 --> 00:26:25.630 align:start position:0% that's the person that is next after the developer<00:26:23.960> as<00:26:24.200> a<00:26:24.360> powerful<00:26:24.760> thing<00:26:25.000> so<00:26:25.440> we<00:26:25.520> are 00:26:25.630 --> 00:26:25.640 align:start position:0% developer as a powerful thing so we are 00:26:25.640 --> 00:26:27.909 align:start position:0% developer as a powerful thing so we are not<00:26:25.840> going<00:26:26.000> to<00:26:26.159> make<00:26:26.320> Aon<00:26:27.080> usable<00:26:27.600> by<00:26:27.720> your 00:26:27.909 --> 00:26:27.919 align:start position:0% not going to make Aon usable by your 00:26:27.919 --> 00:26:29.870 align:start position:0% not going to make Aon usable by your grand<00:26:28.320> mother<00:26:28.600> who<00:26:28.799> plays<00:26:29.120> candy<00:26:29.440> crush<00:26:29.720> on 00:26:29.870 --> 00:26:29.880 align:start position:0% grand mother who plays candy crush on 00:26:29.880 --> 00:26:31.990 align:start position:0% grand mother who plays candy crush on her<00:26:30.159> iPad<00:26:30.919> at<00:26:31.080> least<00:26:31.200> we're<00:26:31.399> not<00:26:31.559> going<00:26:31.720> to<00:26:31.840> do 00:26:31.990 --> 00:26:32.000 align:start position:0% her iPad at least we're not going to do 00:26:32.000 --> 00:26:34.029 align:start position:0% her iPad at least we're not going to do that<00:26:32.159> today<00:26:32.919> today<00:26:33.200> we're<00:26:33.440> going<00:26:33.600> to<00:26:33.799> that 00:26:34.029 --> 00:26:34.039 align:start position:0% that today today we're going to that 00:26:34.039 --> 00:26:34.950 align:start position:0% that today today we're going to that office 00:26:34.950 --> 00:26:34.960 align:start position:0% office 00:26:34.960 --> 00:26:38.350 align:start position:0% office worker<00:26:35.960> and<00:26:36.960> that<00:26:37.120> is<00:26:37.240> the<00:26:37.399> current<00:26:37.760> wallet 00:26:38.350 --> 00:26:38.360 align:start position:0% worker and that is the current wallet 00:26:38.360 --> 00:26:41.149 align:start position:0% worker and that is the current wallet that<00:26:38.480> we've<00:26:38.799> built<00:26:39.799> I<00:26:40.240> Fabian<00:26:40.720> there<00:26:40.880> and<00:26:41.039> the 00:26:41.149 --> 00:26:41.159 align:start position:0% that we've built I Fabian there and the 00:26:41.159 --> 00:26:45.870 align:start position:0% that we've built I Fabian there and the whole<00:26:41.799> go<00:26:42.320> go<00:26:43.080> team<00:26:44.080> and<00:26:44.760> so<00:26:45.039> far<00:26:45.440> I<00:26:45.520> mean<00:26:45.760> it's 00:26:45.870 --> 00:26:45.880 align:start position:0% whole go go team and so far I mean it's 00:26:45.880 --> 00:26:49.190 align:start position:0% whole go go team and so far I mean it's a<00:26:46.039> nice<00:26:46.320> wallet<00:26:47.279> you<00:26:47.399> can<00:26:47.640> see<00:26:48.039> that<00:26:48.559> we<00:26:49.080> you 00:26:49.190 --> 00:26:49.200 align:start position:0% a nice wallet you can see that we you 00:26:49.200 --> 00:26:51.470 align:start position:0% a nice wallet you can see that we you can<00:26:49.480> keep<00:26:49.840> your<00:26:50.080> eater<00:26:50.559> inside<00:26:51.000> it<00:26:51.320> you 00:26:51.470 --> 00:26:51.480 align:start position:0% can keep your eater inside it you 00:26:51.480 --> 00:26:52.909 align:start position:0% can keep your eater inside it you shouldn't<00:26:51.799> be<00:26:51.919> keeping<00:26:52.279> eater<00:26:52.559> in<00:26:52.720> other 00:26:52.909 --> 00:26:52.919 align:start position:0% shouldn't be keeping eater in other 00:26:52.919 --> 00:26:55.590 align:start position:0% shouldn't be keeping eater in other people's<00:26:53.360> sites<00:26:54.120> we<00:26:54.279> added<00:26:54.640> even<00:26:54.880> a<00:26:55.080> little 00:26:55.590 --> 00:26:55.600 align:start position:0% people's sites we added even a little 00:26:55.600 --> 00:26:58.549 align:start position:0% people's sites we added even a little converter<00:26:56.200> so<00:26:56.360> you<00:26:56.919> can<00:26:57.919> check<00:26:58.240> check<00:26:58.440> the 00:26:58.549 --> 00:26:58.559 align:start position:0% converter so you can check check the 00:26:58.559 --> 00:27:01.029 align:start position:0% converter so you can check check the current<00:26:59.360> current<00:27:00.159> conversion<00:27:00.600> rate<00:27:00.799> so<00:27:00.960> if 00:27:01.029 --> 00:27:01.039 align:start position:0% current current conversion rate so if 00:27:01.039 --> 00:27:03.990 align:start position:0% current current conversion rate so if you<00:27:01.120> want<00:27:01.279> to<00:27:01.440> send<00:27:01.840> exactly<00:27:02.200> $1<00:27:02.840> to<00:27:03.039> someone 00:27:03.990 --> 00:27:04.000 align:start position:0% you want to send exactly $1 to someone 00:27:04.000 --> 00:27:06.990 align:start position:0% you want to send exactly $1 to someone you<00:27:04.440> you<00:27:04.559> don't<00:27:04.760> need<00:27:04.919> to<00:27:05.880> to<00:27:06.240> calculate<00:27:06.640> it 00:27:06.990 --> 00:27:07.000 align:start position:0% you you don't need to to calculate it 00:27:07.000 --> 00:27:08.950 align:start position:0% you you don't need to to calculate it and<00:27:07.120> I<00:27:07.240> think<00:27:07.440> that's<00:27:07.760> cool<00:27:08.120> know<00:27:08.360> but<00:27:08.559> we<00:27:08.679> are 00:27:08.950 --> 00:27:08.960 align:start position:0% and I think that's cool know but we are 00:27:08.960 --> 00:27:11.669 align:start position:0% and I think that's cool know but we are a<00:27:09.120> smart<00:27:09.480> contract<00:27:09.960> platform<00:27:10.559> after<00:27:10.799> all<00:27:11.440> so 00:27:11.669 --> 00:27:11.679 align:start position:0% a smart contract platform after all so 00:27:11.679 --> 00:27:14.389 align:start position:0% a smart contract platform after all so we<00:27:11.799> need<00:27:12.159> smart<00:27:12.559> contracts<00:27:13.080> of<00:27:13.279> course<00:27:14.000> so<00:27:14.320> we 00:27:14.389 --> 00:27:14.399 align:start position:0% we need smart contracts of course so we 00:27:14.399 --> 00:27:16.430 align:start position:0% we need smart contracts of course so we are<00:27:14.520> going<00:27:14.679> to<00:27:14.880> have<00:27:15.080> one<00:27:15.760> so<00:27:16.000> the<00:27:16.159> smart 00:27:16.430 --> 00:27:16.440 align:start position:0% are going to have one so the smart 00:27:16.440 --> 00:27:20.029 align:start position:0% are going to have one so the smart contract<00:27:16.799> that<00:27:16.960> we<00:27:17.159> come<00:27:17.440> with<00:27:18.360> is<00:27:18.840> a<00:27:19.279> mul<00:27:19.799> Sig 00:27:20.029 --> 00:27:20.039 align:start position:0% contract that we come with is a mul Sig 00:27:20.039 --> 00:27:22.789 align:start position:0% contract that we come with is a mul Sig wallet<00:27:20.480> it's<00:27:20.600> a<00:27:20.840> multi-<00:27:21.240> shared<00:27:21.640> wallet<00:27:22.559> where 00:27:22.789 --> 00:27:22.799 align:start position:0% wallet it's a multi- shared wallet where 00:27:22.799 --> 00:27:25.750 align:start position:0% wallet it's a multi- shared wallet where multiple<00:27:23.399> people<00:27:23.760> can<00:27:24.080> have<00:27:24.559> can<00:27:25.159> own<00:27:25.640> a 00:27:25.750 --> 00:27:25.760 align:start position:0% multiple people can have can own a 00:27:25.760 --> 00:27:27.430 align:start position:0% multiple people can have can own a single<00:27:26.080> money<00:27:26.399> so<00:27:26.559> you<00:27:26.720> have<00:27:26.880> three<00:27:27.159> people 00:27:27.430 --> 00:27:27.440 align:start position:0% single money so you have three people 00:27:27.440 --> 00:27:29.510 align:start position:0% single money so you have three people and<00:27:27.559> you<00:27:27.640> need<00:27:27.799> two<00:27:28.200> signatures<00:27:28.960> in<00:27:29.080> order<00:27:29.360> to 00:27:29.510 --> 00:27:29.520 align:start position:0% and you need two signatures in order to 00:27:29.520 --> 00:27:31.669 align:start position:0% and you need two signatures in order to move<00:27:29.799> money<00:27:30.120> around<00:27:30.520> so<00:27:30.720> let's<00:27:30.960> call<00:27:31.159> it<00:27:31.440> our 00:27:31.669 --> 00:27:31.679 align:start position:0% move money around so let's call it our 00:27:31.679 --> 00:27:34.510 align:start position:0% move money around so let's call it our shared<00:27:32.120> wallet<00:27:32.799> we<00:27:32.880> are<00:27:33.039> going<00:27:33.200> to<00:27:33.480> add<00:27:33.919> three 00:27:34.510 --> 00:27:34.520 align:start position:0% shared wallet we are going to add three 00:27:34.520 --> 00:27:37.110 align:start position:0% shared wallet we are going to add three two<00:27:34.799> other<00:27:35.080> people<00:27:36.000> but<00:27:36.159> I<00:27:36.279> think<00:27:36.520> that's<00:27:36.799> fine 00:27:37.110 --> 00:27:37.120 align:start position:0% two other people but I think that's fine 00:27:37.120 --> 00:27:40.110 align:start position:0% two other people but I think that's fine but<00:27:37.360> every<00:27:38.000> Bitcoin<00:27:39.000> every<00:27:39.320> Advanced<00:27:39.720> Bitcoin 00:27:40.110 --> 00:27:40.120 align:start position:0% but every Bitcoin every Advanced Bitcoin 00:27:40.120 --> 00:27:41.990 align:start position:0% but every Bitcoin every Advanced Bitcoin app<00:27:40.360> has<00:27:40.559> that<00:27:40.720> so<00:27:40.840> we<00:27:40.919> wanted<00:27:41.159> to<00:27:41.320> add<00:27:41.480> a<00:27:41.640> Twist 00:27:41.990 --> 00:27:42.000 align:start position:0% app has that so we wanted to add a Twist 00:27:42.000 --> 00:27:45.029 align:start position:0% app has that so we wanted to add a Twist and<00:27:42.159> we<00:27:42.279> added<00:27:42.600> this<00:27:42.760> one<00:27:43.039> which<00:27:43.240> is<00:27:44.240> under<00:27:44.840> a 00:27:45.029 --> 00:27:45.039 align:start position:0% and we added this one which is under a 00:27:45.039 --> 00:27:47.830 align:start position:0% and we added this one which is under a lower<00:27:45.399> daily<00:27:45.760> limit<00:27:46.279> let's<00:27:46.480> say<00:27:46.840> 20<00:27:47.240> eer<00:27:47.720> you 00:27:47.830 --> 00:27:47.840 align:start position:0% lower daily limit let's say 20 eer you 00:27:47.840 --> 00:27:51.669 align:start position:0% lower daily limit let's say 20 eer you don't<00:27:48.080> need<00:27:48.720> actual<00:27:49.399> the<00:27:49.720> whole<00:27:50.720> all<00:27:51.039> the<00:27:51.519> all 00:27:51.669 --> 00:27:51.679 align:start position:0% don't need actual the whole all the all 00:27:51.679 --> 00:27:54.549 align:start position:0% don't need actual the whole all the all the<00:27:51.880> signatures<00:27:52.880> so<00:27:53.000> we<00:27:53.159> just<00:27:53.360> click<00:27:53.720> create 00:27:54.549 --> 00:27:54.559 align:start position:0% the signatures so we just click create 00:27:54.559 --> 00:27:57.389 align:start position:0% the signatures so we just click create type<00:27:54.799> your<00:27:55.080> password<00:27:56.080> and<00:27:56.279> boom<00:27:56.880> we<00:27:57.120> just 00:27:57.389 --> 00:27:57.399 align:start position:0% type your password and boom we just 00:27:57.399 --> 00:27:59.950 align:start position:0% type your password and boom we just created<00:27:57.799> your<00:27:58.200> first<00:27:58.559> smart<00:27:58.919> contract<00:27:59.799> that 00:27:59.950 --> 00:27:59.960 align:start position:0% created your first smart contract that 00:27:59.960 --> 00:28:02.310 align:start position:0% created your first smart contract that didn't<00:28:00.320> hurt<00:28:00.679> at<00:28:00.880> all<00:28:01.559> and<00:28:01.679> you<00:28:01.799> can<00:28:02.000> keep<00:28:02.159> your 00:28:02.310 --> 00:28:02.320 align:start position:0% didn't hurt at all and you can keep your 00:28:02.320 --> 00:28:04.630 align:start position:0% didn't hurt at all and you can keep your eer<00:28:02.760> there<00:28:03.039> there<00:28:03.159> are<00:28:03.360> the<00:28:03.519> owners<00:28:04.399> and<00:28:04.519> you 00:28:04.630 --> 00:28:04.640 align:start position:0% eer there there are the owners and you 00:28:04.640 --> 00:28:07.269 align:start position:0% eer there there are the owners and you can<00:28:04.840> let's<00:28:05.120> deposit<00:28:05.720> eer<00:28:06.159> inside<00:28:06.480> it<00:28:07.039> but<00:28:07.200> I 00:28:07.269 --> 00:28:07.279 align:start position:0% can let's deposit eer inside it but I 00:28:07.279 --> 00:28:08.830 align:start position:0% can let's deposit eer inside it but I think<00:28:07.519> that's<00:28:07.720> cool<00:28:08.000> but<00:28:08.120> we<00:28:08.240> can<00:28:08.399> do<00:28:08.559> more 00:28:08.830 --> 00:28:08.840 align:start position:0% think that's cool but we can do more 00:28:08.840 --> 00:28:12.430 align:start position:0% think that's cool but we can do more than<00:28:09.120> that<00:28:09.679> so<00:28:10.200> we<00:28:10.320> can<00:28:10.840> also<00:28:11.320> hold<00:28:11.880> any<00:28:12.240> kind 00:28:12.430 --> 00:28:12.440 align:start position:0% than that so we can also hold any kind 00:28:12.440 --> 00:28:15.269 align:start position:0% than that so we can also hold any kind of<00:28:13.159> cryptocurrency<00:28:14.159> based<00:28:14.440> on<00:28:14.640> ethereum<00:28:15.159> that 00:28:15.269 --> 00:28:15.279 align:start position:0% of cryptocurrency based on ethereum that 00:28:15.279 --> 00:28:17.909 align:start position:0% of cryptocurrency based on ethereum that you<00:28:15.399> build<00:28:15.760> today<00:28:16.360> you<00:28:16.480> can<00:28:16.679> hold<00:28:17.000> it<00:28:17.279> both<00:28:17.799> on 00:28:17.909 --> 00:28:17.919 align:start position:0% you build today you can hold it both on 00:28:17.919 --> 00:28:19.789 align:start position:0% you build today you can hold it both on your<00:28:18.120> wallet<00:28:18.480> and<00:28:18.760> any<00:28:19.120> of<00:28:19.279> the<00:28:19.480> smart 00:28:19.789 --> 00:28:19.799 align:start position:0% your wallet and any of the smart 00:28:19.799 --> 00:28:22.830 align:start position:0% your wallet and any of the smart contracts<00:28:20.640> so<00:28:20.880> loyalty<00:28:21.519> points<00:28:22.519> gold 00:28:22.830 --> 00:28:22.840 align:start position:0% contracts so loyalty points gold 00:28:22.840 --> 00:28:25.630 align:start position:0% contracts so loyalty points gold certificate<00:28:23.640> anything<00:28:23.960> that<00:28:24.080> you<00:28:24.240> can<00:28:24.640> create 00:28:25.630 --> 00:28:25.640 align:start position:0% certificate anything that you can create 00:28:25.640 --> 00:28:28.549 align:start position:0% certificate anything that you can create you<00:28:25.840> could<00:28:26.159> the<00:28:26.600> theor<00:28:27.159> theoretically<00:28:28.200> also 00:28:28.549 --> 00:28:28.559 align:start position:0% you could the theor theoretically also 00:28:28.559 --> 00:28:31.230 align:start position:0% you could the theor theoretically also keep<00:28:29.080> with<00:28:29.360> all<00:28:29.559> the<00:28:29.799> security<00:28:30.320> of<00:28:30.480> the 00:28:31.230 --> 00:28:31.240 align:start position:0% keep with all the security of the 00:28:31.240 --> 00:28:34.789 align:start position:0% keep with all the security of the blockchain<00:28:32.240> I<00:28:32.320> think<00:28:32.600> that's<00:28:32.960> very<00:28:33.200> cool<00:28:34.120> but 00:28:34.789 --> 00:28:34.799 align:start position:0% blockchain I think that's very cool but 00:28:34.799 --> 00:28:37.149 align:start position:0% blockchain I think that's very cool but what's<00:28:35.039> the<00:28:35.240> point<00:28:35.559> of<00:28:35.799> having<00:28:36.320> other<00:28:36.679> people 00:28:37.149 --> 00:28:37.159 align:start position:0% what's the point of having other people 00:28:37.159 --> 00:28:39.590 align:start position:0% what's the point of having other people coins<00:28:37.559> or<00:28:37.760> other<00:28:38.039> people<00:28:38.440> tokens<00:28:39.080> that's<00:28:39.279> so 00:28:39.590 --> 00:28:39.600 align:start position:0% coins or other people tokens that's so 00:28:39.600 --> 00:28:43.070 align:start position:0% coins or other people tokens that's so far<00:28:39.960> what<00:28:40.120> we've<00:28:40.360> known<00:28:41.360> so<00:28:42.080> I<00:28:42.399> I<00:28:42.519> figure<00:28:42.840> out 00:28:43.070 --> 00:28:43.080 align:start position:0% far what we've known so I I figure out 00:28:43.080 --> 00:28:45.350 align:start position:0% far what we've known so I I figure out that<00:28:43.279> maybe<00:28:43.559> you<00:28:43.679> should<00:28:44.120> create<00:28:44.679> be<00:28:44.880> able<00:28:45.120> to 00:28:45.350 --> 00:28:45.360 align:start position:0% that maybe you should create be able to 00:28:45.360 --> 00:28:47.909 align:start position:0% that maybe you should create be able to create<00:28:45.880> your<00:28:46.039> own<00:28:46.440> token<00:28:47.200> so<00:28:47.360> you<00:28:47.480> can<00:28:47.640> go<00:28:47.760> to 00:28:47.909 --> 00:28:47.919 align:start position:0% create your own token so you can go to 00:28:47.919 --> 00:28:50.430 align:start position:0% create your own token so you can go to the<00:28:48.080> contracts<00:28:48.640> Tab<00:28:48.880> and<00:28:49.000> we<00:28:49.200> keep<00:28:49.880> an<00:28:50.080> eye<00:28:50.240> on 00:28:50.430 --> 00:28:50.440 align:start position:0% the contracts Tab and we keep an eye on 00:28:50.440 --> 00:28:52.430 align:start position:0% the contracts Tab and we keep an eye on all<00:28:50.640> the<00:28:50.760> contracts<00:28:51.159> and<00:28:51.320> you<00:28:51.480> can<00:28:51.679> click 00:28:52.430 --> 00:28:52.440 align:start position:0% all the contracts and you can click 00:28:52.440 --> 00:28:54.509 align:start position:0% all the contracts and you can click create<00:28:53.000> and<00:28:53.159> you'll<00:28:53.360> be<00:28:53.519> able<00:28:53.760> to<00:28:53.919> create<00:28:54.240> your 00:28:54.509 --> 00:28:54.519 align:start position:0% create and you'll be able to create your 00:28:54.519 --> 00:28:56.830 align:start position:0% create and you'll be able to create your own<00:28:54.840> contract<00:28:55.559> you<00:28:55.720> just<00:28:55.880> need<00:28:56.039> to<00:28:56.279> paste<00:28:56.519> some 00:28:56.830 --> 00:28:56.840 align:start position:0% own contract you just need to paste some 00:28:56.840 --> 00:28:59.789 align:start position:0% own contract you just need to paste some code<00:28:57.159> there<00:28:57.720> oh<00:28:57.919> wa<00:28:58.200> wait<00:28:58.760> I<00:28:58.919> thought<00:28:59.360> you<00:28:59.559> told 00:28:59.789 --> 00:28:59.799 align:start position:0% code there oh wa wait I thought you told 00:28:59.799 --> 00:29:01.470 align:start position:0% code there oh wa wait I thought you told me<00:29:00.039> that<00:29:00.200> this<00:29:00.360> was<00:29:00.559> not<00:29:00.720> an<00:29:00.919> app<00:29:01.120> for 00:29:01.470 --> 00:29:01.480 align:start position:0% me that this was not an app for 00:29:01.480 --> 00:29:04.269 align:start position:0% me that this was not an app for developers<00:29:02.480> so<00:29:02.799> why<00:29:02.960> are<00:29:03.159> we<00:29:03.320> showing<00:29:03.799> code 00:29:04.269 --> 00:29:04.279 align:start position:0% developers so why are we showing code 00:29:04.279 --> 00:29:07.070 align:start position:0% developers so why are we showing code there<00:29:05.279> that's<00:29:05.440> a<00:29:05.640> good<00:29:05.880> question<00:29:06.720> and<00:29:06.880> my 00:29:07.070 --> 00:29:07.080 align:start position:0% there that's a good question and my 00:29:07.080 --> 00:29:09.830 align:start position:0% there that's a good question and my point<00:29:07.440> is<00:29:08.200> I<00:29:08.320> am<00:29:08.440> not<00:29:08.640> in<00:29:08.760> the<00:29:09.000> business<00:29:09.480> of 00:29:09.830 --> 00:29:09.840 align:start position:0% point is I am not in the business of 00:29:09.840 --> 00:29:11.950 align:start position:0% point is I am not in the business of creating<00:29:10.440> artificial<00:29:11.039> walls<00:29:11.600> between 00:29:11.950 --> 00:29:11.960 align:start position:0% creating artificial walls between 00:29:11.960 --> 00:29:13.710 align:start position:0% creating artificial walls between developers<00:29:12.440> and<00:29:12.600> the<00:29:12.720> power<00:29:13.000> users<00:29:13.440> and<00:29:13.559> I'm 00:29:13.710 --> 00:29:13.720 align:start position:0% developers and the power users and I'm 00:29:13.720 --> 00:29:15.830 align:start position:0% developers and the power users and I'm not<00:29:13.840> in<00:29:14.000> the<00:29:14.519> I<00:29:14.640> have<00:29:14.799> no<00:29:15.039> interest<00:29:15.720> in 00:29:15.830 --> 00:29:15.840 align:start position:0% not in the I have no interest in 00:29:15.840 --> 00:29:17.669 align:start position:0% not in the I have no interest in building<00:29:16.240> artificial<00:29:16.799> ceilings<00:29:17.399> because 00:29:17.669 --> 00:29:17.679 align:start position:0% building artificial ceilings because 00:29:17.679 --> 00:29:21.750 align:start position:0% building artificial ceilings because there<00:29:17.840> is<00:29:18.039> no<00:29:18.519> ceiling<00:29:19.720> and<00:29:20.720> and<00:29:21.200> I<00:29:21.360> I'm<00:29:21.519> in<00:29:21.640> the 00:29:21.750 --> 00:29:21.760 align:start position:0% there is no ceiling and and I I'm in the 00:29:21.760 --> 00:29:23.990 align:start position:0% there is no ceiling and and I I'm in the business<00:29:22.080> of<00:29:22.240> building<00:29:22.760> easy<00:29:23.159> escalators 00:29:23.990 --> 00:29:24.000 align:start position:0% business of building easy escalators 00:29:24.000 --> 00:29:27.310 align:start position:0% business of building easy escalators that<00:29:24.320> help<00:29:24.679> you<00:29:25.000> go<00:29:25.360> up<00:29:25.720> if<00:29:25.840> you<00:29:26.000> want<00:29:26.240> it<00:29:27.000> so 00:29:27.310 --> 00:29:27.320 align:start position:0% that help you go up if you want it so 00:29:27.320 --> 00:29:29.310 align:start position:0% that help you go up if you want it so the<00:29:27.720> purpose<00:29:28.080> purpose<00:29:28.320> of<00:29:28.440> the<00:29:28.600> wallet<00:29:29.080> is 00:29:29.310 --> 00:29:29.320 align:start position:0% the purpose purpose of the wallet is 00:29:29.320 --> 00:29:31.830 align:start position:0% the purpose purpose of the wallet is actually<00:29:29.640> to<00:29:29.799> bridge<00:29:30.240> the<00:29:30.480> gap<00:29:31.120> between<00:29:31.480> the 00:29:31.830 --> 00:29:31.840 align:start position:0% actually to bridge the gap between the 00:29:31.840 --> 00:29:34.389 align:start position:0% actually to bridge the gap between the developer<00:29:32.360> and<00:29:32.559> the<00:29:32.720> power<00:29:33.039> user<00:29:33.760> so<00:29:34.039> that<00:29:34.279> if 00:29:34.389 --> 00:29:34.399 align:start position:0% developer and the power user so that if 00:29:34.399 --> 00:29:36.789 align:start position:0% developer and the power user so that if you<00:29:34.600> want<00:29:34.960> to<00:29:35.159> learn<00:29:35.519> more<00:29:35.880> you<00:29:36.240> can<00:29:36.559> if<00:29:36.679> you 00:29:36.789 --> 00:29:36.799 align:start position:0% you want to learn more you can if you 00:29:36.799 --> 00:29:39.710 align:start position:0% you want to learn more you can if you want<00:29:37.039> to<00:29:37.320> develop<00:29:37.840> you<00:29:38.000> can<00:29:38.760> but<00:29:39.120> actually<00:29:39.600> you 00:29:39.710 --> 00:29:39.720 align:start position:0% want to develop you can but actually you 00:29:39.720 --> 00:29:41.870 align:start position:0% want to develop you can but actually you don't<00:29:39.960> need<00:29:40.200> it<00:29:40.480> and<00:29:40.679> I<00:29:40.840> hope<00:29:41.159> that<00:29:41.320> you<00:29:41.600> grow 00:29:41.870 --> 00:29:41.880 align:start position:0% don't need it and I hope that you grow 00:29:41.880 --> 00:29:44.950 align:start position:0% don't need it and I hope that you grow outgrow<00:29:42.679> our<00:29:43.240> our<00:29:43.519> wallet<00:29:43.919> and<00:29:44.360> and<00:29:44.559> that<00:29:44.760> at 00:29:44.950 --> 00:29:44.960 align:start position:0% outgrow our our wallet and and that at 00:29:44.960 --> 00:29:46.710 align:start position:0% outgrow our our wallet and and that at that<00:29:45.120> point<00:29:45.320> you<00:29:45.440> will<00:29:45.640> be<00:29:46.039> able<00:29:46.240> to<00:29:46.360> download 00:29:46.710 --> 00:29:46.720 align:start position:0% that point you will be able to download 00:29:46.720 --> 00:29:49.669 align:start position:0% that point you will be able to download mix<00:29:47.000> or<00:29:47.200> something<00:29:47.519> else<00:29:48.320> but<00:29:48.640> the<00:29:48.799> point<00:29:49.120> is 00:29:49.669 --> 00:29:49.679 align:start position:0% mix or something else but the point is 00:29:49.679 --> 00:29:52.509 align:start position:0% mix or something else but the point is you<00:29:49.919> actually<00:29:50.200> don't<00:29:50.480> need<00:29:51.200> you<00:29:51.360> could<00:29:51.640> just 00:29:52.509 --> 00:29:52.519 align:start position:0% you actually don't need you could just 00:29:52.519 --> 00:29:55.230 align:start position:0% you actually don't need you could just see<00:29:52.960> the<00:29:53.440> you<00:29:53.919> there<00:29:54.039> are<00:29:54.320> you<00:29:54.399> can<00:29:54.640> just<00:29:54.880> feel 00:29:55.230 --> 00:29:55.240 align:start position:0% see the you there are you can just feel 00:29:55.240 --> 00:29:57.110 align:start position:0% see the you there are you can just feel the<00:29:55.399> parameters<00:29:55.840> on<00:29:56.000> the<00:29:56.200> right<00:29:56.559> ignore<00:29:56.960> the 00:29:57.110 --> 00:29:57.120 align:start position:0% the parameters on the right ignore the 00:29:57.120 --> 00:29:59.430 align:start position:0% the parameters on the right ignore the code<00:29:57.519> there<00:29:58.120> and<00:29:58.279> you'll<00:29:58.480> be<00:29:58.679> creating<00:29:59.039> your 00:29:59.430 --> 00:29:59.440 align:start position:0% code there and you'll be creating your 00:29:59.440 --> 00:30:01.509 align:start position:0% code there and you'll be creating your your<00:29:59.720> your<00:29:59.880> little<00:30:00.200> token<00:30:00.600> so<00:30:00.799> let's<00:30:01.320> just 00:30:01.509 --> 00:30:01.519 align:start position:0% your your little token so let's just 00:30:01.519 --> 00:30:03.870 align:start position:0% your your little token so let's just tell<00:30:01.720> me<00:30:02.000> what<00:30:02.159> the<00:30:02.320> supply<00:30:02.840> is<00:30:03.120> what<00:30:03.240> the<00:30:03.440> name 00:30:03.870 --> 00:30:03.880 align:start position:0% tell me what the supply is what the name 00:30:03.880 --> 00:30:06.190 align:start position:0% tell me what the supply is what the name is<00:30:04.240> what<00:30:04.399> the<00:30:04.880> symbol<00:30:05.440> is<00:30:05.559> and<00:30:05.760> how<00:30:05.880> many 00:30:06.190 --> 00:30:06.200 align:start position:0% is what the symbol is and how many 00:30:06.200 --> 00:30:09.389 align:start position:0% is what the symbol is and how many decimal<00:30:06.720> places<00:30:07.080> you<00:30:07.360> want<00:30:08.360> and<00:30:08.840> you<00:30:09.039> click 00:30:09.389 --> 00:30:09.399 align:start position:0% decimal places you want and you click 00:30:09.399 --> 00:30:11.789 align:start position:0% decimal places you want and you click okay<00:30:09.640> and<00:30:09.799> you'll<00:30:10.039> be<00:30:10.279> creating<00:30:11.000> your<00:30:11.320> token 00:30:11.789 --> 00:30:11.799 align:start position:0% okay and you'll be creating your token 00:30:11.799 --> 00:30:13.590 align:start position:0% okay and you'll be creating your token you<00:30:11.919> don't<00:30:12.080> need<00:30:12.399> actually<00:30:12.720> to<00:30:12.880> read<00:30:13.159> the<00:30:13.360> code 00:30:13.590 --> 00:30:13.600 align:start position:0% you don't need actually to read the code 00:30:13.600 --> 00:30:15.430 align:start position:0% you don't need actually to read the code just<00:30:13.919> copy<00:30:14.200> it<00:30:14.360> from<00:30:14.559> our<00:30:14.840> website<00:30:15.240> or 00:30:15.430 --> 00:30:15.440 align:start position:0% just copy it from our website or 00:30:15.440 --> 00:30:18.190 align:start position:0% just copy it from our website or anywhere<00:30:15.840> else<00:30:16.679> type<00:30:16.919> your<00:30:17.159> password<00:30:18.000> and 00:30:18.190 --> 00:30:18.200 align:start position:0% anywhere else type your password and 00:30:18.200 --> 00:30:20.789 align:start position:0% anywhere else type your password and boom<00:30:18.640> we<00:30:18.840> just<00:30:19.080> create<00:30:19.519> the<00:30:19.720> token<00:30:20.159> and<00:30:20.399> Bob 00:30:20.789 --> 00:30:20.799 align:start position:0% boom we just create the token and Bob 00:30:20.799 --> 00:30:22.990 align:start position:0% boom we just create the token and Bob owns<00:30:21.480> 100%<00:30:22.320> of 00:30:22.990 --> 00:30:23.000 align:start position:0% owns 100% of 00:30:23.000 --> 00:30:27.509 align:start position:0% owns 100% of it<00:30:24.000> and<00:30:24.159> I<00:30:24.320> think<00:30:25.000> that's<00:30:25.360> very<00:30:26.120> cool<00:30:27.120> but 00:30:27.509 --> 00:30:27.519 align:start position:0% it and I think that's very cool but 00:30:27.519 --> 00:30:29.630 align:start position:0% it and I think that's very cool but again<00:30:28.240> I<00:30:28.320> think<00:30:28.559> we<00:30:28.679> can<00:30:28.840> do<00:30:29.000> more<00:30:29.200> with<00:30:29.399> that 00:30:29.630 --> 00:30:29.640 align:start position:0% again I think we can do more with that 00:30:29.640 --> 00:30:31.669 align:start position:0% again I think we can do more with that because<00:30:29.919> what's<00:30:30.159> the<00:30:30.360> point<00:30:30.799> of<00:30:31.039> having<00:30:31.440> yet 00:30:31.669 --> 00:30:31.679 align:start position:0% because what's the point of having yet 00:30:31.679 --> 00:30:34.070 align:start position:0% because what's the point of having yet another<00:30:32.080> new<00:30:32.399> token<00:30:32.840> what's<00:30:33.080> the<00:30:33.360> value 00:30:34.070 --> 00:30:34.080 align:start position:0% another new token what's the value 00:30:34.080 --> 00:30:36.350 align:start position:0% another new token what's the value what's<00:30:34.279> the<00:30:34.480> utility<00:30:35.120> or<00:30:35.399> usefulness<00:30:36.159> of 00:30:36.350 --> 00:30:36.360 align:start position:0% what's the utility or usefulness of 00:30:36.360 --> 00:30:38.389 align:start position:0% what's the utility or usefulness of having<00:30:36.600> another<00:30:37.000> token<00:30:37.799> so<00:30:37.960> we're<00:30:38.120> going<00:30:38.279> to 00:30:38.389 --> 00:30:38.399 align:start position:0% having another token so we're going to 00:30:38.399 --> 00:30:40.350 align:start position:0% having another token so we're going to do<00:30:38.600> something<00:30:38.919> useful<00:30:39.440> with<00:30:39.600> it<00:30:40.120> and<00:30:40.279> what 00:30:40.350 --> 00:30:40.360 align:start position:0% do something useful with it and what 00:30:40.360 --> 00:30:41.909 align:start position:0% do something useful with it and what we're<00:30:40.559> going<00:30:40.720> to<00:30:40.840> do<00:30:41.080> first<00:30:41.480> I'm<00:30:41.600> going<00:30:41.760> to 00:30:41.909 --> 00:30:41.919 align:start position:0% we're going to do first I'm going to 00:30:41.919 --> 00:30:44.230 align:start position:0% we're going to do first I'm going to distribute<00:30:42.360> it<00:30:42.519> around<00:30:42.960> I<00:30:43.080> created<00:30:43.519> Bob<00:30:43.960> Alice 00:30:44.230 --> 00:30:44.240 align:start position:0% distribute it around I created Bob Alice 00:30:44.240 --> 00:30:47.789 align:start position:0% distribute it around I created Bob Alice and<00:30:44.519> Eve<00:30:45.320> now<00:30:46.000> Bob<00:30:46.279> is<00:30:46.360> going<00:30:46.559> to<00:30:46.640> send<00:30:46.960> 30%<00:30:47.600> to 00:30:47.789 --> 00:30:47.799 align:start position:0% and Eve now Bob is going to send 30% to 00:30:47.799 --> 00:30:51.149 align:start position:0% and Eve now Bob is going to send 30% to Eve<00:30:48.039> and<00:30:48.159> 30%<00:30:48.679> to<00:30:48.840> Alice<00:30:49.159> so<00:30:49.320> it's<00:30:49.440> a<00:30:49.559> 40<00:30:49.880> 30<00:30:50.240> 30% 00:30:51.149 --> 00:30:51.159 align:start position:0% Eve and 30% to Alice so it's a 40 30 30% 00:30:51.159 --> 00:30:53.430 align:start position:0% Eve and 30% to Alice so it's a 40 30 30% split<00:30:52.120> and<00:30:52.279> what<00:30:52.360> you're<00:30:52.559> going<00:30:52.760> to<00:30:52.880> do<00:30:53.120> is<00:30:53.240> we 00:30:53.430 --> 00:30:53.440 align:start position:0% split and what you're going to do is we 00:30:53.440 --> 00:30:56.110 align:start position:0% split and what you're going to do is we going<00:30:53.600> to<00:30:53.799> create<00:30:54.159> a<00:30:54.320> virtual<00:30:55.120> organization 00:30:56.110 --> 00:30:56.120 align:start position:0% going to create a virtual organization 00:30:56.120 --> 00:30:58.149 align:start position:0% going to create a virtual organization that<00:30:56.240> is<00:30:56.360> a<00:30:56.519> democratic<00:30:57.240> organization<00:30:58.039> that 00:30:58.149 --> 00:30:58.159 align:start position:0% that is a democratic organization that 00:30:58.159 --> 00:31:00.430 align:start position:0% that is a democratic organization that lives<00:30:58.519> only<00:30:58.799> on<00:30:58.960> the<00:30:59.120> blockchain<00:31:00.039> that<00:31:00.200> can 00:31:00.430 --> 00:31:00.440 align:start position:0% lives only on the blockchain that can 00:31:00.440 --> 00:31:03.870 align:start position:0% lives only on the blockchain that can hold<00:31:00.880> funds<00:31:01.760> and<00:31:01.919> use<00:31:02.240> those<00:31:02.679> tokens<00:31:03.519> as<00:31:03.639> a 00:31:03.870 --> 00:31:03.880 align:start position:0% hold funds and use those tokens as a 00:31:03.880 --> 00:31:08.590 align:start position:0% hold funds and use those tokens as a voting<00:31:04.519> shares<00:31:05.519> so<00:31:05.720> let's<00:31:06.000> do<00:31:06.200> that<00:31:06.399> now 00:31:08.590 --> 00:31:08.600 align:start position:0% voting shares so let's do that now 00:31:08.600 --> 00:31:11.870 align:start position:0% voting shares so let's do that now okay<00:31:09.600> so<00:31:10.360> you<00:31:10.480> can<00:31:10.639> see<00:31:10.880> that<00:31:11.080> Alis<00:31:11.519> already 00:31:11.870 --> 00:31:11.880 align:start position:0% okay so you can see that Alis already 00:31:11.880 --> 00:31:14.149 align:start position:0% okay so you can see that Alis already has<00:31:12.080> 30%<00:31:12.639> of<00:31:12.799> the<00:31:12.919> coins<00:31:13.240> now<00:31:13.399> we<00:31:13.519> go<00:31:13.720> back<00:31:14.000> the 00:31:14.149 --> 00:31:14.159 align:start position:0% has 30% of the coins now we go back the 00:31:14.159 --> 00:31:16.430 align:start position:0% has 30% of the coins now we go back the contract<00:31:14.600> you<00:31:14.760> just<00:31:14.919> click<00:31:15.200> deploy<00:31:15.679> contract 00:31:16.430 --> 00:31:16.440 align:start position:0% contract you just click deploy contract 00:31:16.440 --> 00:31:18.310 align:start position:0% contract you just click deploy contract get<00:31:16.639> the<00:31:16.760> code<00:31:17.039> that<00:31:17.159> you<00:31:17.320> got<00:31:17.760> somewhere<00:31:18.240> we 00:31:18.310 --> 00:31:18.320 align:start position:0% get the code that you got somewhere we 00:31:18.320 --> 00:31:20.990 align:start position:0% get the code that you got somewhere we are<00:31:18.399> going<00:31:18.559> to<00:31:18.679> put<00:31:18.919> 500<00:31:19.440> eers<00:31:20.080> on<00:31:20.440> inside<00:31:20.799> that 00:31:20.990 --> 00:31:21.000 align:start position:0% are going to put 500 eers on inside that 00:31:21.000 --> 00:31:24.110 align:start position:0% are going to put 500 eers on inside that contract<00:31:21.480> which<00:31:21.720> is<00:31:22.480> already<00:31:22.960> real<00:31:23.240> some<00:31:23.399> real 00:31:24.110 --> 00:31:24.120 align:start position:0% contract which is already real some real 00:31:24.120 --> 00:31:26.950 align:start position:0% contract which is already real some real money<00:31:25.120> so<00:31:25.320> you<00:31:25.480> just<00:31:25.720> paste<00:31:25.960> it<00:31:26.240> there<00:31:26.600> and<00:31:26.799> you 00:31:26.950 --> 00:31:26.960 align:start position:0% money so you just paste it there and you 00:31:26.960 --> 00:31:28.669 align:start position:0% money so you just paste it there and you fill<00:31:27.279> in<00:31:27.399> the<00:31:27.519> blank<00:31:27.760> you<00:31:27.919> you<00:31:28.000> don't<00:31:28.120> need<00:31:28.240> to 00:31:28.669 --> 00:31:28.679 align:start position:0% fill in the blank you you don't need to 00:31:28.679 --> 00:31:30.830 align:start position:0% fill in the blank you you don't need to understand<00:31:28.840> the<00:31:29.000> code<00:31:29.480> just<00:31:29.760> go<00:31:30.080> there<00:31:30.600> we<00:31:30.720> are 00:31:30.830 --> 00:31:30.840 align:start position:0% understand the code just go there we are 00:31:30.840 --> 00:31:33.070 align:start position:0% understand the code just go there we are going<00:31:31.000> to<00:31:31.120> deploy<00:31:31.440> the<00:31:31.519> Democracy<00:31:32.080> contract 00:31:33.070 --> 00:31:33.080 align:start position:0% going to deploy the Democracy contract 00:31:33.080 --> 00:31:36.430 align:start position:0% going to deploy the Democracy contract now<00:31:34.080> and<00:31:34.720> now<00:31:34.960> we<00:31:35.120> add<00:31:35.440> there<00:31:35.679> on<00:31:35.919> the<00:31:36.039> share 00:31:36.430 --> 00:31:36.440 align:start position:0% now and now we add there on the share 00:31:36.440 --> 00:31:38.750 align:start position:0% now and now we add there on the share addresses<00:31:37.159> the<00:31:37.519> address<00:31:37.919> of<00:31:38.039> the<00:31:38.240> token<00:31:38.600> that 00:31:38.750 --> 00:31:38.760 align:start position:0% addresses the address of the token that 00:31:38.760 --> 00:31:41.149 align:start position:0% addresses the address of the token that we<00:31:39.000> just<00:31:39.240> created<00:31:39.720> a<00:31:39.880> minute<00:31:40.200> ago<00:31:40.720> and<00:31:41.000> those 00:31:41.149 --> 00:31:41.159 align:start position:0% we just created a minute ago and those 00:31:41.159 --> 00:31:42.870 align:start position:0% we just created a minute ago and those are<00:31:41.399> some<00:31:41.600> other<00:31:41.880> things<00:31:42.240> like<00:31:42.440> how<00:31:42.559> many 00:31:42.870 --> 00:31:42.880 align:start position:0% are some other things like how many 00:31:42.880 --> 00:31:45.230 align:start position:0% are some other things like how many shares<00:31:43.279> you<00:31:43.440> need<00:31:43.600> to<00:31:43.919> in<00:31:44.039> order<00:31:44.240> to<00:31:44.399> vote<00:31:45.080> how 00:31:45.230 --> 00:31:45.240 align:start position:0% shares you need to in order to vote how 00:31:45.240 --> 00:31:47.590 align:start position:0% shares you need to in order to vote how many<00:31:45.519> minutes<00:31:46.039> you<00:31:46.200> have<00:31:46.320> to<00:31:46.519> debate<00:31:47.120> until 00:31:47.590 --> 00:31:47.600 align:start position:0% many minutes you have to debate until 00:31:47.600 --> 00:31:50.070 align:start position:0% many minutes you have to debate until the<00:31:47.919> until<00:31:48.159> you<00:31:48.279> can<00:31:48.480> execute<00:31:48.880> something<00:31:49.760> you 00:31:50.070 --> 00:31:50.080 align:start position:0% the until you can execute something you 00:31:50.080 --> 00:31:54.470 align:start position:0% the until you can execute something you type<00:31:50.360> your<00:31:51.279> we<00:31:51.480> type<00:31:51.679> your<00:31:52.240> password<00:31:53.240> and<00:31:54.120> we 00:31:54.470 --> 00:31:54.480 align:start position:0% type your we type your password and we 00:31:54.480 --> 00:31:59.310 align:start position:0% type your we type your password and we just<00:31:55.480> created<00:31:56.120> or<00:31:56.679> let<00:31:56.840> me<00:31:56.960> see<00:31:57.120> if<00:31:57.279> it's<00:31:57.559> ready 00:31:59.310 --> 00:31:59.320 align:start position:0% just created or let me see if it's ready 00:31:59.320 --> 00:32:03.350 align:start position:0% just created or let me see if it's ready and<00:32:00.320> and<00:32:00.799> there<00:32:00.919> we<00:32:01.159> go<00:32:01.679> we<00:32:02.000> just<00:32:02.320> created<00:32:03.120> a 00:32:03.350 --> 00:32:03.360 align:start position:0% and and there we go we just created a 00:32:03.360 --> 00:32:06.350 align:start position:0% and and there we go we just created a new<00:32:04.320> Democratic<00:32:04.960> organization<00:32:05.639> that<00:32:05.960> only 00:32:06.350 --> 00:32:06.360 align:start position:0% new Democratic organization that only 00:32:06.360 --> 00:32:08.870 align:start position:0% new Democratic organization that only exists<00:32:06.760> on<00:32:06.919> the<00:32:07.080> blockchain<00:32:07.960> let's<00:32:08.159> rename<00:32:08.559> it 00:32:08.870 --> 00:32:08.880 align:start position:0% exists on the blockchain let's rename it 00:32:08.880 --> 00:32:11.509 align:start position:0% exists on the blockchain let's rename it blockchain<00:32:09.840> unlimited<00:32:10.840> and<00:32:10.960> you<00:32:11.080> can<00:32:11.240> click 00:32:11.509 --> 00:32:11.519 align:start position:0% blockchain unlimited and you can click 00:32:11.519 --> 00:32:13.549 align:start position:0% blockchain unlimited and you can click there<00:32:11.720> it<00:32:11.840> will<00:32:12.039> show<00:32:12.440> all<00:32:12.720> the<00:32:13.240> public 00:32:13.549 --> 00:32:13.559 align:start position:0% there it will show all the public 00:32:13.559 --> 00:32:16.190 align:start position:0% there it will show all the public information<00:32:14.279> about<00:32:14.559> that<00:32:14.799> company<00:32:15.799> and<00:32:16.039> which 00:32:16.190 --> 00:32:16.200 align:start position:0% information about that company and which 00:32:16.200 --> 00:32:18.430 align:start position:0% information about that company and which is<00:32:16.519> the<00:32:16.799> address<00:32:17.200> of<00:32:17.320> the<00:32:17.519> token<00:32:18.120> and<00:32:18.279> the 00:32:18.430 --> 00:32:18.440 align:start position:0% is the address of the token and the 00:32:18.440 --> 00:32:20.509 align:start position:0% is the address of the token and the other<00:32:18.760> things<00:32:19.039> that<00:32:19.200> we<00:32:19.519> how<00:32:19.639> many<00:32:19.919> proposals 00:32:20.509 --> 00:32:20.519 align:start position:0% other things that we how many proposals 00:32:20.519 --> 00:32:22.350 align:start position:0% other things that we how many proposals there<00:32:20.639> are<00:32:21.039> how<00:32:21.159> many<00:32:21.480> minutes<00:32:21.919> you<00:32:22.039> have<00:32:22.200> to 00:32:22.350 --> 00:32:22.360 align:start position:0% there are how many minutes you have to 00:32:22.360 --> 00:32:24.590 align:start position:0% there are how many minutes you have to debate<00:32:22.679> it<00:32:23.279> how<00:32:23.600> how<00:32:23.720> many<00:32:23.880> shares<00:32:24.240> you<00:32:24.399> need 00:32:24.590 --> 00:32:24.600 align:start position:0% debate it how how many shares you need 00:32:24.600 --> 00:32:26.190 align:start position:0% debate it how how many shares you need it<00:32:24.799> it's<00:32:25.000> very<00:32:25.240> simple<00:32:25.639> actually<00:32:25.919> you<00:32:26.039> just 00:32:26.190 --> 00:32:26.200 align:start position:0% it it's very simple actually you just 00:32:26.200 --> 00:32:28.310 align:start position:0% it it's very simple actually you just need<00:32:26.320> to<00:32:26.519> read<00:32:26.760> it<00:32:27.279> and<00:32:27.480> on<00:32:27.600> the<00:32:28.080> there<00:32:28.200> you 00:32:28.310 --> 00:32:28.320 align:start position:0% need to read it and on the there you 00:32:28.320 --> 00:32:29.590 align:start position:0% need to read it and on the there you have<00:32:28.480> all<00:32:28.639> the<00:32:28.799> functions<00:32:29.200> that<00:32:29.320> you<00:32:29.399> can 00:32:29.590 --> 00:32:29.600 align:start position:0% have all the functions that you can 00:32:29.600 --> 00:32:31.830 align:start position:0% have all the functions that you can execute<00:32:29.960> it<00:32:30.120> if<00:32:30.360> now<00:32:30.840> so<00:32:31.000> let's<00:32:31.200> create<00:32:31.440> a<00:32:31.600> new 00:32:31.830 --> 00:32:31.840 align:start position:0% execute it if now so let's create a new 00:32:31.840 --> 00:32:34.230 align:start position:0% execute it if now so let's create a new proposal<00:32:32.360> we<00:32:32.480> have<00:32:32.639> 500<00:32:33.120> eers<00:32:33.559> how<00:32:33.760> are<00:32:34.080> we 00:32:34.230 --> 00:32:34.240 align:start position:0% proposal we have 500 eers how are we 00:32:34.240 --> 00:32:36.830 align:start position:0% proposal we have 500 eers how are we going<00:32:34.360> to<00:32:34.480> spend<00:32:34.799> it<00:32:35.360> so<00:32:35.600> first<00:32:36.080> I'm<00:32:36.200> going<00:32:36.320> to 00:32:36.830 --> 00:32:36.840 align:start position:0% going to spend it so first I'm going to 00:32:36.840 --> 00:32:39.789 align:start position:0% going to spend it so first I'm going to propose<00:32:37.240> that<00:32:37.399> we<00:32:37.559> send<00:32:37.880> money<00:32:38.240> for<00:32:38.559> Eve<00:32:39.519> 200 00:32:39.789 --> 00:32:39.799 align:start position:0% propose that we send money for Eve 200 00:32:39.799 --> 00:32:42.310 align:start position:0% propose that we send money for Eve 200 eers<00:32:40.320> for<00:32:40.519> the<00:32:40.840> planning<00:32:41.200> of<00:32:41.360> a 00:32:42.310 --> 00:32:42.320 align:start position:0% eers for the planning of a 00:32:42.320 --> 00:32:45.110 align:start position:0% eers for the planning of a conference<00:32:43.320> just<00:32:43.519> click<00:32:43.919> execute<00:32:44.639> type<00:32:44.880> your 00:32:45.110 --> 00:32:45.120 align:start position:0% conference just click execute type your 00:32:45.120 --> 00:32:47.269 align:start position:0% conference just click execute type your password<00:32:45.880> and<00:32:46.080> it's<00:32:46.279> done<00:32:46.679> it's<00:32:46.880> going<00:32:47.039> to<00:32:47.159> be 00:32:47.269 --> 00:32:47.279 align:start position:0% password and it's done it's going to be 00:32:47.279 --> 00:32:50.590 align:start position:0% password and it's done it's going to be loaded<00:32:48.000> there<00:32:49.000> so<00:32:49.320> why<00:32:49.519> we<00:32:49.799> wait<00:32:50.159> for<00:32:50.399> the 00:32:50.590 --> 00:32:50.600 align:start position:0% loaded there so why we wait for the 00:32:50.600 --> 00:32:52.310 align:start position:0% loaded there so why we wait for the transaction<00:32:51.080> to<00:32:51.200> be<00:32:51.360> confirmed<00:32:51.799> let's<00:32:52.080> just 00:32:52.310 --> 00:32:52.320 align:start position:0% transaction to be confirmed let's just 00:32:52.320 --> 00:32:54.430 align:start position:0% transaction to be confirmed let's just create<00:32:52.720> another<00:32:53.200> another<00:32:53.600> another<00:32:54.080> few 00:32:54.430 --> 00:32:54.440 align:start position:0% create another another another few 00:32:54.440 --> 00:32:59.029 align:start position:0% create another another another few proposals<00:32:54.960> so<00:32:55.200> let's<00:32:55.679> say<00:32:56.679> 50<00:32:57.120> eers<00:32:58.080> for<00:32:58.559> Bob 00:32:59.029 --> 00:32:59.039 align:start position:0% proposals so let's say 50 eers for Bob 00:32:59.039 --> 00:33:01.710 align:start position:0% proposals so let's say 50 eers for Bob now<00:32:59.679> for<00:33:00.200> for<00:33:00.480> Alis<00:33:00.880> or<00:33:01.000> for<00:33:01.240> Eve<00:33:01.519> for 00:33:01.710 --> 00:33:01.720 align:start position:0% now for for Alis or for Eve for 00:33:01.720 --> 00:33:04.110 align:start position:0% now for for Alis or for Eve for something<00:33:02.000> else<00:33:02.360> let's<00:33:02.559> say<00:33:02.919> thck 00:33:04.110 --> 00:33:04.120 align:start position:0% something else let's say thck 00:33:04.120 --> 00:33:07.149 align:start position:0% something else let's say thck reimbursement<00:33:05.120> you<00:33:05.279> click<00:33:05.559> as<00:33:05.679> aute<00:33:06.519> and<00:33:06.840> you 00:33:07.149 --> 00:33:07.159 align:start position:0% reimbursement you click as aute and you 00:33:07.159 --> 00:33:10.710 align:start position:0% reimbursement you click as aute and you load<00:33:07.440> it<00:33:07.559> on<00:33:07.679> the 00:33:10.710 --> 00:33:10.720 align:start position:0% 00:33:10.720 --> 00:33:13.710 align:start position:0% blockchain<00:33:11.720> so<00:33:11.919> it's<00:33:12.240> it's<00:33:12.600> quite<00:33:12.960> fast<00:33:13.559> of 00:33:13.710 --> 00:33:13.720 align:start position:0% blockchain so it's it's quite fast of 00:33:13.720 --> 00:33:15.870 align:start position:0% blockchain so it's it's quite fast of course<00:33:14.039> this<00:33:14.279> I'm<00:33:14.399> not<00:33:14.559> doing<00:33:14.799> it<00:33:15.200> live<00:33:15.679> but 00:33:15.870 --> 00:33:15.880 align:start position:0% course this I'm not doing it live but 00:33:15.880 --> 00:33:18.909 align:start position:0% course this I'm not doing it live but it's<00:33:16.440> it's<00:33:16.880> it's<00:33:17.120> about<00:33:18.000> how<00:33:18.200> we<00:33:18.320> would<00:33:18.559> see<00:33:18.799> it 00:33:18.909 --> 00:33:18.919 align:start position:0% it's it's it's about how we would see it 00:33:18.919 --> 00:33:21.789 align:start position:0% it's it's it's about how we would see it in<00:33:19.080> real<00:33:19.519> life<00:33:20.519> so<00:33:20.720> the<00:33:20.880> transaction<00:33:21.320> has<00:33:21.519> been 00:33:21.789 --> 00:33:21.799 align:start position:0% in real life so the transaction has been 00:33:21.799 --> 00:33:23.430 align:start position:0% in real life so the transaction has been executed<00:33:22.240> you<00:33:22.320> can<00:33:22.440> see<00:33:22.679> that<00:33:22.919> one<00:33:23.080> of<00:33:23.240> them 00:33:23.430 --> 00:33:23.440 align:start position:0% executed you can see that one of them 00:33:23.440 --> 00:33:25.549 align:start position:0% executed you can see that one of them has<00:33:23.600> already<00:33:23.880> loaded<00:33:24.399> there<00:33:24.720> on<00:33:24.919> the<00:33:25.159> on<00:33:25.320> the 00:33:25.549 --> 00:33:25.559 align:start position:0% has already loaded there on the on the 00:33:25.559 --> 00:33:28.430 align:start position:0% has already loaded there on the on the side<00:33:25.880> here<00:33:26.799> let's<00:33:27.039> create<00:33:27.360> one<00:33:27.559> last<00:33:27.919> proposal 00:33:28.430 --> 00:33:28.440 align:start position:0% side here let's create one last proposal 00:33:28.440 --> 00:33:30.149 align:start position:0% side here let's create one last proposal which<00:33:28.600> will<00:33:28.760> be<00:33:28.880> for<00:33:29.159> Bob<00:33:29.399> send<00:33:29.760> monitor 00:33:30.149 --> 00:33:30.159 align:start position:0% which will be for Bob send monitor 00:33:30.159 --> 00:33:32.669 align:start position:0% which will be for Bob send monitor himself<00:33:30.919> for<00:33:31.360> badge<00:33:31.760> design<00:33:32.200> probably<00:33:32.559> the 00:33:32.669 --> 00:33:32.679 align:start position:0% himself for badge design probably the 00:33:32.679 --> 00:33:36.389 align:start position:0% himself for badge design probably the most<00:33:32.960> expensive<00:33:33.559> badge<00:33:34.519> we<00:33:34.720> ever<00:33:35.399> designed 00:33:36.389 --> 00:33:36.399 align:start position:0% most expensive badge we ever designed 00:33:36.399 --> 00:33:39.149 align:start position:0% most expensive badge we ever designed just<00:33:36.639> type<00:33:36.880> a<00:33:37.080> password<00:33:37.519> there<00:33:38.120> and<00:33:38.279> if<00:33:38.399> you<00:33:38.679> f 00:33:39.149 --> 00:33:39.159 align:start position:0% just type a password there and if you f 00:33:39.159 --> 00:33:41.190 align:start position:0% just type a password there and if you f if<00:33:39.480> if<00:33:39.559> you<00:33:39.720> wait<00:33:39.960> a<00:33:40.080> few<00:33:40.279> minutes<00:33:40.679> you<00:33:40.880> see 00:33:41.190 --> 00:33:41.200 align:start position:0% if if you wait a few minutes you see 00:33:41.200 --> 00:33:43.509 align:start position:0% if if you wait a few minutes you see that<00:33:41.919> now<00:33:42.080> we<00:33:42.240> just<00:33:42.480> wait<00:33:42.679> a<00:33:42.799> little<00:33:43.039> bit<00:33:43.240> until 00:33:43.509 --> 00:33:43.519 align:start position:0% that now we just wait a little bit until 00:33:43.519 --> 00:33:46.190 align:start position:0% that now we just wait a little bit until all<00:33:43.760> proposal<00:33:44.480> are<00:33:44.639> loaded 00:33:46.190 --> 00:33:46.200 align:start position:0% all proposal are loaded 00:33:46.200 --> 00:33:49.230 align:start position:0% all proposal are loaded and<00:33:47.200> you<00:33:47.360> can<00:33:47.760> click<00:33:47.960> on<00:33:48.080> the<00:33:48.240> proposes<00:33:48.799> number 00:33:49.230 --> 00:33:49.240 align:start position:0% and you can click on the proposes number 00:33:49.240 --> 00:33:51.350 align:start position:0% and you can click on the proposes number zero<00:33:49.679> zero<00:33:50.120> there<00:33:50.320> and<00:33:50.440> if<00:33:50.559> you<00:33:50.679> switch<00:33:51.039> it<00:33:51.279> you 00:33:51.350 --> 00:33:51.360 align:start position:0% zero zero there and if you switch it you 00:33:51.360 --> 00:33:53.750 align:start position:0% zero zero there and if you switch it you can<00:33:51.880> anyone<00:33:52.240> who's<00:33:52.519> following<00:33:53.120> this<00:33:53.320> contract 00:33:53.750 --> 00:33:53.760 align:start position:0% can anyone who's following this contract 00:33:53.760 --> 00:33:55.990 align:start position:0% can anyone who's following this contract on<00:33:53.880> the<00:33:54.000> blockchain<00:33:54.760> will<00:33:54.960> be<00:33:55.159> able<00:33:55.440> to<00:33:55.600> see 00:33:55.990 --> 00:33:56.000 align:start position:0% on the blockchain will be able to see 00:33:56.000 --> 00:33:58.149 align:start position:0% on the blockchain will be able to see all<00:33:56.240> the<00:33:56.519> proposals<00:33:57.399> so<00:33:57.559> it's<00:33:57.919> very 00:33:58.149 --> 00:33:58.159 align:start position:0% all the proposals so it's very 00:33:58.159 --> 00:34:00.950 align:start position:0% all the proposals so it's very transparent<00:33:58.880> anyone<00:33:59.320> watching<00:33:59.760> can<00:33:59.919> see<00:34:00.279> that 00:34:00.950 --> 00:34:00.960 align:start position:0% transparent anyone watching can see that 00:34:00.960 --> 00:34:03.190 align:start position:0% transparent anyone watching can see that and<00:34:01.159> now<00:34:01.600> that<00:34:01.760> they<00:34:01.880> are<00:34:02.120> there<00:34:02.360> we<00:34:02.480> can<00:34:02.720> vote 00:34:03.190 --> 00:34:03.200 align:start position:0% and now that they are there we can vote 00:34:03.200 --> 00:34:05.110 align:start position:0% and now that they are there we can vote voting<00:34:03.600> is<00:34:03.880> very<00:34:04.159> simple<00:34:04.600> again<00:34:04.799> you<00:34:04.919> just 00:34:05.110 --> 00:34:05.120 align:start position:0% voting is very simple again you just 00:34:05.120 --> 00:34:07.190 align:start position:0% voting is very simple again you just type<00:34:05.360> the<00:34:05.519> proposal<00:34:06.000> number<00:34:06.279> you<00:34:06.399> want<00:34:06.960> and<00:34:07.080> if 00:34:07.190 --> 00:34:07.200 align:start position:0% type the proposal number you want and if 00:34:07.200 --> 00:34:09.190 align:start position:0% type the proposal number you want and if you<00:34:07.360> support<00:34:07.760> it<00:34:08.000> you<00:34:08.159> click 00:34:09.190 --> 00:34:09.200 align:start position:0% you support it you click 00:34:09.200 --> 00:34:12.510 align:start position:0% you support it you click yes<00:34:10.200> and<00:34:10.440> that's<00:34:10.760> all<00:34:11.000> you<00:34:11.119> need<00:34:11.320> to<00:34:11.520> do<00:34:12.200> so<00:34:12.359> you 00:34:12.510 --> 00:34:12.520 align:start position:0% yes and that's all you need to do so you 00:34:12.520 --> 00:34:15.349 align:start position:0% yes and that's all you need to do so you click<00:34:12.879> execute<00:34:13.399> you<00:34:13.679> type<00:34:13.919> your 00:34:15.349 --> 00:34:15.359 align:start position:0% click execute you type your 00:34:15.359 --> 00:34:18.030 align:start position:0% click execute you type your password<00:34:16.359> and<00:34:16.520> you<00:34:16.639> click<00:34:16.879> Send<00:34:17.679> and<00:34:17.800> now<00:34:17.919> we 00:34:18.030 --> 00:34:18.040 align:start position:0% password and you click Send and now we 00:34:18.040 --> 00:34:20.230 align:start position:0% password and you click Send and now we are<00:34:18.159> going<00:34:18.320> to<00:34:18.440> do<00:34:18.720> a<00:34:18.960> secondary<00:34:19.560> vote<00:34:20.040> let's 00:34:20.230 --> 00:34:20.240 align:start position:0% are going to do a secondary vote let's 00:34:20.240 --> 00:34:24.589 align:start position:0% are going to do a secondary vote let's say<00:34:20.440> that<00:34:20.639> Alis<00:34:21.040> is<00:34:21.399> also<00:34:21.679> going<00:34:21.879> to<00:34:22.040> vote 00:34:24.589 --> 00:34:24.599 align:start position:0% say that Alis is also going to vote 00:34:24.599 --> 00:34:28.109 align:start position:0% say that Alis is also going to vote Yes<00:34:25.599> and<00:34:25.919> that<00:34:26.040> means<00:34:26.440> that<00:34:27.320> those<00:34:27.760> votes<00:34:28.000> are 00:34:28.109 --> 00:34:28.119 align:start position:0% Yes and that means that those votes are 00:34:28.119 --> 00:34:29.829 align:start position:0% Yes and that means that those votes are being<00:34:28.320> loaded<00:34:28.800> on<00:34:28.960> the<00:34:29.079> blockchain<00:34:29.679> that 00:34:29.829 --> 00:34:29.839 align:start position:0% being loaded on the blockchain that 00:34:29.839 --> 00:34:32.310 align:start position:0% being loaded on the blockchain that company<00:34:30.200> only<00:34:30.560> exists<00:34:31.200> there<00:34:31.760> which<00:34:31.879> is<00:34:32.159> kind 00:34:32.310 --> 00:34:32.320 align:start position:0% company only exists there which is kind 00:34:32.320 --> 00:34:33.349 align:start position:0% company only exists there which is kind of 00:34:33.349 --> 00:34:33.359 align:start position:0% of 00:34:33.359 --> 00:34:35.470 align:start position:0% of fascinating<00:34:34.359> and<00:34:34.639> you<00:34:34.720> can<00:34:34.879> see<00:34:35.159> the<00:34:35.280> number 00:34:35.470 --> 00:34:35.480 align:start position:0% fascinating and you can see the number 00:34:35.480 --> 00:34:37.669 align:start position:0% fascinating and you can see the number of<00:34:35.679> votes<00:34:36.000> has<00:34:36.280> just<00:34:36.440> been<00:34:36.639> increased<00:34:37.119> by<00:34:37.240> two 00:34:37.669 --> 00:34:37.679 align:start position:0% of votes has just been increased by two 00:34:37.679 --> 00:34:39.430 align:start position:0% of votes has just been increased by two they<00:34:37.760> are<00:34:38.079> they<00:34:38.200> have<00:34:38.320> been<00:34:38.480> loaded<00:34:39.159> and<00:34:39.280> now 00:34:39.430 --> 00:34:39.440 align:start position:0% they are they have been loaded and now 00:34:39.440 --> 00:34:40.950 align:start position:0% they are they have been loaded and now we<00:34:39.520> are<00:34:39.639> going<00:34:39.760> to<00:34:39.960> execute<00:34:40.320> the<00:34:40.520> proposal 00:34:40.950 --> 00:34:40.960 align:start position:0% we are going to execute the proposal 00:34:40.960 --> 00:34:43.109 align:start position:0% we are going to execute the proposal meaning<00:34:41.280> that<00:34:41.960> the<00:34:42.159> blockchain<00:34:42.560> is<00:34:42.679> going<00:34:42.879> to 00:34:43.109 --> 00:34:43.119 align:start position:0% meaning that the blockchain is going to 00:34:43.119 --> 00:34:45.550 align:start position:0% meaning that the blockchain is going to count<00:34:43.480> up<00:34:43.800> our<00:34:44.079> votes<00:34:44.560> and<00:34:44.720> if<00:34:44.839> the<00:34:45.000> proposal 00:34:45.550 --> 00:34:45.560 align:start position:0% count up our votes and if the proposal 00:34:45.560 --> 00:34:47.310 align:start position:0% count up our votes and if the proposal passes<00:34:45.960> it's<00:34:46.119> going<00:34:46.280> to<00:34:46.399> send<00:34:46.679> the<00:34:46.800> money<00:34:47.200> if 00:34:47.310 --> 00:34:47.320 align:start position:0% passes it's going to send the money if 00:34:47.320 --> 00:34:48.990 align:start position:0% passes it's going to send the money if it<00:34:47.480> doesn't<00:34:47.839> passes<00:34:48.200> it's<00:34:48.359> going<00:34:48.520> to<00:34:48.679> keep<00:34:48.879> the 00:34:48.990 --> 00:34:49.000 align:start position:0% it doesn't passes it's going to keep the 00:34:49.000 --> 00:34:51.510 align:start position:0% it doesn't passes it's going to keep the money<00:34:49.560> it's<00:34:49.800> as<00:34:50.000> simple<00:34:50.320> as<00:34:50.480> that<00:34:50.760> really<00:34:51.359> so 00:34:51.510 --> 00:34:51.520 align:start position:0% money it's as simple as that really so 00:34:51.520 --> 00:34:52.869 align:start position:0% money it's as simple as that really so you're<00:34:51.679> going<00:34:51.919> just<00:34:52.040> to<00:34:52.159> execute<00:34:52.520> it<00:34:52.639> and<00:34:52.760> I 00:34:52.869 --> 00:34:52.879 align:start position:0% you're going just to execute it and I 00:34:52.879 --> 00:34:58.069 align:start position:0% you're going just to execute it and I I'll<00:34:53.200> watch<00:34:53.520> there<00:34:54.040> just<00:34:54.200> for<00:34:54.359> a<00:34:54.520> second 00:34:58.069 --> 00:34:58.079 align:start position:0% 00:34:58.079 --> 00:35:00.069 align:start position:0% and<00:34:58.280> the<00:34:58.440> proposal<00:34:58.839> has<00:34:59.079> passed<00:34:59.560> the<00:34:59.720> money 00:35:00.069 --> 00:35:00.079 align:start position:0% and the proposal has passed the money 00:35:00.079 --> 00:35:02.430 align:start position:0% and the proposal has passed the money has<00:35:00.240> moved<00:35:00.640> away<00:35:01.320> from<00:35:01.680> there<00:35:01.920> to<00:35:02.160> here<00:35:02.320> you 00:35:02.430 --> 00:35:02.440 align:start position:0% has moved away from there to here you 00:35:02.440 --> 00:35:04.510 align:start position:0% has moved away from there to here you can<00:35:02.599> see<00:35:02.800> that<00:35:02.920> the<00:35:03.079> proposal<00:35:03.599> has<00:35:03.839> passed<00:35:04.359> he 00:35:04.510 --> 00:35:04.520 align:start position:0% can see that the proposal has passed he 00:35:04.520 --> 00:35:06.870 align:start position:0% can see that the proposal has passed he not<00:35:04.720> open<00:35:05.040> to<00:35:05.200> vote<00:35:05.480> anymore<00:35:06.320> and<00:35:06.480> if<00:35:06.599> you 00:35:06.870 --> 00:35:06.880 align:start position:0% not open to vote anymore and if you 00:35:06.880 --> 00:35:09.990 align:start position:0% not open to vote anymore and if you remember<00:35:07.880> Eve<00:35:08.440> had<00:35:08.640> only<00:35:09.000> like<00:35:09.160> two<00:35:09.440> eers<00:35:09.880> in 00:35:09.990 --> 00:35:10.000 align:start position:0% remember Eve had only like two eers in 00:35:10.000 --> 00:35:12.230 align:start position:0% remember Eve had only like two eers in the<00:35:10.119> beginning<00:35:10.400> of<00:35:10.520> the<00:35:11.040> presentation<00:35:11.520> Alice 00:35:12.230 --> 00:35:12.240 align:start position:0% the beginning of the presentation Alice 00:35:12.240 --> 00:35:15.190 align:start position:0% the beginning of the presentation Alice and<00:35:12.359> now<00:35:12.520> she<00:35:12.760> has<00:35:13.320> 200<00:35:13.760> eers<00:35:14.760> and<00:35:14.920> I<00:35:15.000> think 00:35:15.190 --> 00:35:15.200 align:start position:0% and now she has 200 eers and I think 00:35:15.200 --> 00:35:17.069 align:start position:0% and now she has 200 eers and I think that's<00:35:15.400> kind<00:35:15.560> of<00:35:15.760> fascinating<00:35:16.640> we<00:35:16.839> just 00:35:17.069 --> 00:35:17.079 align:start position:0% that's kind of fascinating we just 00:35:17.079 --> 00:35:19.829 align:start position:0% that's kind of fascinating we just created<00:35:17.560> a<00:35:17.800> company<00:35:18.320> that<00:35:18.520> only<00:35:19.040> exists<00:35:19.640> on 00:35:19.829 --> 00:35:19.839 align:start position:0% created a company that only exists on 00:35:19.839 --> 00:35:23.870 align:start position:0% created a company that only exists on the<00:35:20.320> internet<00:35:21.320> yet<00:35:21.800> it<00:35:21.960> can<00:35:22.200> hold<00:35:22.599> real<00:35:23.000> money 00:35:23.870 --> 00:35:23.880 align:start position:0% the internet yet it can hold real money 00:35:23.880 --> 00:35:27.510 align:start position:0% the internet yet it can hold real money and<00:35:24.079> do<00:35:24.520> real<00:35:25.000> world<00:35:25.640> things<00:35:26.320> with<00:35:26.560> that<00:35:26.800> money 00:35:27.510 --> 00:35:27.520 align:start position:0% and do real world things with that money 00:35:27.520 --> 00:35:29.790 align:start position:0% and do real world things with that money and<00:35:27.760> it<00:35:27.839> can<00:35:28.000> hold<00:35:28.320> shares<00:35:28.839> it<00:35:28.960> can<00:35:29.160> hold<00:35:29.480> gold 00:35:29.790 --> 00:35:29.800 align:start position:0% and it can hold shares it can hold gold 00:35:29.800 --> 00:35:32.310 align:start position:0% and it can hold shares it can hold gold it<00:35:29.920> can<00:35:30.280> hold<00:35:30.640> anything<00:35:31.040> you<00:35:31.160> want<00:35:31.960> and<00:35:32.200> I 00:35:32.310 --> 00:35:32.320 align:start position:0% it can hold anything you want and I 00:35:32.320 --> 00:35:35.270 align:start position:0% it can hold anything you want and I think<00:35:32.560> it's<00:35:33.200> fascinating<00:35:34.200> maybe<00:35:34.839> the<00:35:34.960> average 00:35:35.270 --> 00:35:35.280 align:start position:0% think it's fascinating maybe the average 00:35:35.280 --> 00:35:38.069 align:start position:0% think it's fascinating maybe the average user<00:35:35.560> doesn't<00:35:35.880> think<00:35:36.119> so<00:35:37.079> maybe<00:35:37.560> he<00:35:37.720> doesn't 00:35:38.069 --> 00:35:38.079 align:start position:0% user doesn't think so maybe he doesn't 00:35:38.079 --> 00:35:40.910 align:start position:0% user doesn't think so maybe he doesn't care<00:35:38.400> about<00:35:38.720> all<00:35:39.040> that<00:35:39.800> again<00:35:40.119> like<00:35:40.320> I<00:35:40.480> say<00:35:40.760> to 00:35:40.910 --> 00:35:40.920 align:start position:0% care about all that again like I say to 00:35:40.920 --> 00:35:43.630 align:start position:0% care about all that again like I say to you<00:35:41.160> before<00:35:41.640> you<00:35:41.880> never<00:35:42.160> know<00:35:42.440> who<00:35:42.680> he<00:35:42.880> is<00:35:43.440> but 00:35:43.630 --> 00:35:43.640 align:start position:0% you before you never know who he is but 00:35:43.640 --> 00:35:46.390 align:start position:0% you before you never know who he is but he<00:35:43.880> can<00:35:44.079> only<00:35:44.400> tell<00:35:44.640> you<00:35:44.839> who<00:35:45.040> he's<00:35:45.359> not<00:35:46.200> and 00:35:46.390 --> 00:35:46.400 align:start position:0% he can only tell you who he's not and 00:35:46.400 --> 00:35:48.270 align:start position:0% he can only tell you who he's not and apparently<00:35:46.839> he's<00:35:47.079> not<00:35:47.320> someone<00:35:47.640> who<00:35:47.839> cares 00:35:48.270 --> 00:35:48.280 align:start position:0% apparently he's not someone who cares 00:35:48.280 --> 00:35:50.069 align:start position:0% apparently he's not someone who cares about<00:35:48.560> smart<00:35:48.960> contracts<00:35:49.440> or<00:35:49.640> peer-to-peer 00:35:50.069 --> 00:35:50.079 align:start position:0% about smart contracts or peer-to-peer 00:35:50.079 --> 00:35:52.870 align:start position:0% about smart contracts or peer-to-peer networking<00:35:50.839> or<00:35:51.040> anything<00:35:51.400> like<00:35:51.560> that<00:35:52.359> what<00:35:52.720> he 00:35:52.870 --> 00:35:52.880 align:start position:0% networking or anything like that what he 00:35:52.880 --> 00:35:55.030 align:start position:0% networking or anything like that what he wants<00:35:53.440> is<00:35:53.599> he<00:35:53.720> wants<00:35:53.920> to<00:35:54.119> save<00:35:54.400> money<00:35:54.720> he<00:35:54.839> wants 00:35:55.030 --> 00:35:55.040 align:start position:0% wants is he wants to save money he wants 00:35:55.040 --> 00:35:58.069 align:start position:0% wants is he wants to save money he wants to<00:35:55.200> work<00:35:55.520> better<00:35:55.839> he<00:35:55.960> wants<00:35:56.160> to<00:35:56.280> be<00:35:56.440> insured 00:35:58.069 --> 00:35:58.079 align:start position:0% to work better he wants to be insured 00:35:58.079 --> 00:36:00.589 align:start position:0% to work better he wants to be insured against<00:35:58.520> disasters<00:35:59.160> he<00:35:59.319> wants<00:35:59.599> that<00:35:59.839> his<00:36:00.480> the 00:36:00.589 --> 00:36:00.599 align:start position:0% against disasters he wants that his the 00:36:00.599 --> 00:36:03.950 align:start position:0% against disasters he wants that his the money<00:36:00.880> for<00:36:01.079> his<00:36:01.240> children<00:36:01.680> will<00:36:01.839> be<00:36:02.040> kept<00:36:02.960> safe 00:36:03.950 --> 00:36:03.960 align:start position:0% money for his children will be kept safe 00:36:03.960 --> 00:36:05.710 align:start position:0% money for his children will be kept safe and<00:36:04.119> we<00:36:04.280> can<00:36:04.480> do<00:36:04.800> that<00:36:05.040> and<00:36:05.160> I'm<00:36:05.280> going<00:36:05.400> to<00:36:05.520> tell 00:36:05.710 --> 00:36:05.720 align:start position:0% and we can do that and I'm going to tell 00:36:05.720 --> 00:36:07.510 align:start position:0% and we can do that and I'm going to tell you<00:36:05.800> a<00:36:05.920> little<00:36:06.160> secret<00:36:06.599> about<00:36:06.880> this<00:36:07.079> Wallet 00:36:07.510 --> 00:36:07.520 align:start position:0% you a little secret about this Wallet 00:36:07.520 --> 00:36:11.910 align:start position:0% you a little secret about this Wallet app<00:36:08.280> it's<00:36:08.560> not<00:36:09.040> a<00:36:09.480> single<00:36:10.480> app<00:36:11.480> those<00:36:11.640> are 00:36:11.910 --> 00:36:11.920 align:start position:0% app it's not a single app those are 00:36:11.920 --> 00:36:14.790 align:start position:0% app it's not a single app those are actually<00:36:12.359> two<00:36:12.839> apps<00:36:13.720> on<00:36:13.880> the<00:36:14.000> left<00:36:14.400> here<00:36:14.680> we 00:36:14.790 --> 00:36:14.800 align:start position:0% actually two apps on the left here we 00:36:14.800 --> 00:36:17.750 align:start position:0% actually two apps on the left here we have<00:36:15.040> M<00:36:15.839> it<00:36:16.000> keeps<00:36:16.359> all<00:36:16.599> the<00:36:16.839> complexity<00:36:17.599> of 00:36:17.750 --> 00:36:17.760 align:start position:0% have M it keeps all the complexity of 00:36:17.760 --> 00:36:20.589 align:start position:0% have M it keeps all the complexity of connecting<00:36:18.280> to<00:36:18.560> the<00:36:19.400> of<00:36:19.560> connecting<00:36:20.040> to<00:36:20.280> the 00:36:20.589 --> 00:36:20.599 align:start position:0% connecting to the of connecting to the 00:36:20.599 --> 00:36:23.230 align:start position:0% connecting to the of connecting to the to<00:36:20.800> to<00:36:20.920> the<00:36:21.040> network<00:36:21.720> and<00:36:22.000> signing<00:36:22.720> signing 00:36:23.230 --> 00:36:23.240 align:start position:0% to to the network and signing signing 00:36:23.240 --> 00:36:25.750 align:start position:0% to to the network and signing signing everything<00:36:24.040> on<00:36:24.200> the<00:36:24.400> right<00:36:24.680> there<00:36:25.000> you<00:36:25.200> have 00:36:25.750 --> 00:36:25.760 align:start position:0% everything on the right there you have 00:36:25.760 --> 00:36:30.069 align:start position:0% everything on the right there you have just<00:36:26.240> a<00:36:26.720> a<00:36:27.040> website<00:36:27.960> that<00:36:28.160> connects<00:36:28.640> to<00:36:28.920> to<00:36:29.119> M 00:36:30.069 --> 00:36:30.079 align:start position:0% just a a website that connects to to M 00:36:30.079 --> 00:36:31.990 align:start position:0% just a a website that connects to to M that<00:36:30.240> means<00:36:30.599> that<00:36:30.800> if<00:36:30.960> your<00:36:31.280> your<00:36:31.480> team<00:36:31.800> can 00:36:31.990 --> 00:36:32.000 align:start position:0% that means that if your your team can 00:36:32.000 --> 00:36:34.670 align:start position:0% that means that if your your team can develop<00:36:32.359> a<00:36:32.560> website<00:36:33.160> then<00:36:33.400> you<00:36:33.599> can<00:36:34.240> make<00:36:34.440> a 00:36:34.670 --> 00:36:34.680 align:start position:0% develop a website then you can make a 00:36:34.680 --> 00:36:36.670 align:start position:0% develop a website then you can make a web<00:36:35.119> web<00:36:35.319> application<00:36:36.240> that<00:36:36.400> you<00:36:36.480> can 00:36:36.670 --> 00:36:36.680 align:start position:0% web web application that you can 00:36:36.680 --> 00:36:38.950 align:start position:0% web web application that you can distribute<00:36:37.200> it<00:36:37.720> and<00:36:37.920> since<00:36:38.119> it's<00:36:38.319> all<00:36:38.640> open 00:36:38.950 --> 00:36:38.960 align:start position:0% distribute it and since it's all open 00:36:38.960 --> 00:36:40.829 align:start position:0% distribute it and since it's all open source<00:36:39.280> you<00:36:39.400> can<00:36:39.560> just<00:36:39.839> put<00:36:40.000> your<00:36:40.280> app<00:36:40.599> here 00:36:40.829 --> 00:36:40.839 align:start position:0% source you can just put your app here 00:36:40.839 --> 00:36:43.750 align:start position:0% source you can just put your app here and<00:36:41.000> distribute<00:36:41.480> it<00:36:41.640> to<00:36:42.359> to<00:36:42.720> to<00:36:42.920> various 00:36:43.750 --> 00:36:43.760 align:start position:0% and distribute it to to to various 00:36:43.760 --> 00:36:47.430 align:start position:0% and distribute it to to to various places<00:36:44.760> and<00:36:45.240> actually<00:36:46.240> okay<00:36:46.440> maybe<00:36:47.200> he<00:36:47.319> he 00:36:47.430 --> 00:36:47.440 align:start position:0% places and actually okay maybe he he 00:36:47.440 --> 00:36:49.030 align:start position:0% places and actually okay maybe he he doesn't<00:36:47.720> even<00:36:47.960> want<00:36:48.319> that<00:36:48.520> maybe<00:36:48.720> he<00:36:48.800> doesn't 00:36:49.030 --> 00:36:49.040 align:start position:0% doesn't even want that maybe he doesn't 00:36:49.040 --> 00:36:51.349 align:start position:0% doesn't even want that maybe he doesn't want<00:36:49.200> to<00:36:49.359> download<00:36:49.760> a<00:36:49.880> bunch<00:36:50.160> of<00:36:50.440> apps<00:36:50.960> so<00:36:51.200> what 00:36:51.349 --> 00:36:51.359 align:start position:0% want to download a bunch of apps so what 00:36:51.359 --> 00:36:53.829 align:start position:0% want to download a bunch of apps so what if<00:36:51.720> instead<00:36:52.160> you<00:36:52.359> just<00:36:52.520> put<00:36:52.680> a<00:36:52.880> browser<00:36:53.359> inside 00:36:53.829 --> 00:36:53.839 align:start position:0% if instead you just put a browser inside 00:36:53.839 --> 00:36:55.829 align:start position:0% if instead you just put a browser inside here<00:36:54.079> and<00:36:54.200> you<00:36:54.280> can<00:36:54.520> distribute<00:36:55.319> those<00:36:55.560> apps 00:36:55.829 --> 00:36:55.839 align:start position:0% here and you can distribute those apps 00:36:55.839 --> 00:36:59.309 align:start position:0% here and you can distribute those apps via<00:36:56.079> the<00:36:56.240> Internet<00:36:57.040> and<00:36:57.200> that's<00:36:57.680> what<00:36:57.880> my<00:36:58.480> is 00:36:59.309 --> 00:36:59.319 align:start position:0% via the Internet and that's what my is 00:36:59.319 --> 00:37:01.990 align:start position:0% via the Internet and that's what my is my<00:36:59.839> this<00:36:59.960> is<00:37:00.079> a<00:37:00.280> real<00:37:00.680> working<00:37:01.280> product<00:37:01.839> a 00:37:01.990 --> 00:37:02.000 align:start position:0% my this is a real working product a 00:37:02.000 --> 00:37:03.750 align:start position:0% my this is a real working product a screenshot<00:37:02.520> of<00:37:02.680> the<00:37:02.839> working<00:37:03.160> product<00:37:03.560> if<00:37:03.640> you 00:37:03.750 --> 00:37:03.760 align:start position:0% screenshot of the working product if you 00:37:03.760 --> 00:37:05.390 align:start position:0% screenshot of the working product if you want<00:37:03.920> to<00:37:04.040> see<00:37:04.200> a<00:37:04.319> demo<00:37:04.599> you<00:37:04.680> can<00:37:04.839> just<00:37:05.000> ask<00:37:05.240> us 00:37:05.390 --> 00:37:05.400 align:start position:0% want to see a demo you can just ask us 00:37:05.400 --> 00:37:07.870 align:start position:0% want to see a demo you can just ask us in<00:37:05.599> private<00:37:05.960> we<00:37:06.079> can<00:37:06.240> do<00:37:06.760> but<00:37:06.920> it's<00:37:07.200> a<00:37:07.640> it's 00:37:07.870 --> 00:37:07.880 align:start position:0% in private we can do but it's a it's 00:37:07.880 --> 00:37:10.829 align:start position:0% in private we can do but it's a it's just<00:37:08.480> everything<00:37:08.880> that<00:37:09.040> I've<00:37:09.240> shown<00:37:09.599> you<00:37:10.400> but 00:37:10.829 --> 00:37:10.839 align:start position:0% just everything that I've shown you but 00:37:10.839 --> 00:37:13.910 align:start position:0% just everything that I've shown you but with<00:37:11.079> a<00:37:11.520> with<00:37:11.640> a<00:37:11.839> browser<00:37:12.280> bar<00:37:12.599> that<00:37:12.720> you<00:37:12.800> can 00:37:13.910 --> 00:37:13.920 align:start position:0% with a with a browser bar that you can 00:37:13.920 --> 00:37:17.270 align:start position:0% with a with a browser bar that you can download<00:37:14.920> and<00:37:15.720> I<00:37:15.800> think<00:37:16.079> that's<00:37:16.440> awesome<00:37:17.000> but 00:37:17.270 --> 00:37:17.280 align:start position:0% download and I think that's awesome but 00:37:17.280 --> 00:37:20.589 align:start position:0% download and I think that's awesome but is<00:37:17.480> that<00:37:17.800> enough<00:37:18.680> is<00:37:18.880> that<00:37:19.200> having<00:37:19.599> all<00:37:19.920> those 00:37:20.589 --> 00:37:20.599 align:start position:0% is that enough is that having all those 00:37:20.599 --> 00:37:22.790 align:start position:0% is that enough is that having all those those<00:37:21.160> those<00:37:21.880> those<00:37:22.160> applications 00:37:22.790 --> 00:37:22.800 align:start position:0% those those those applications 00:37:22.800 --> 00:37:25.589 align:start position:0% those those those applications accessible<00:37:23.480> via<00:37:23.680> the<00:37:23.839> Internet<00:37:24.520> enough<00:37:25.520> I 00:37:25.589 --> 00:37:25.599 align:start position:0% accessible via the Internet enough I 00:37:25.599 --> 00:37:27.670 align:start position:0% accessible via the Internet enough I think<00:37:25.960> don't<00:37:26.359> I<00:37:26.520> I<00:37:26.599> don't<00:37:26.800> think<00:37:27.000> so<00:37:27.280> I<00:37:27.480> I<00:37:27.560> think 00:37:27.670 --> 00:37:27.680 align:start position:0% think don't I I don't think so I I think 00:37:27.680 --> 00:37:29.510 align:start position:0% think don't I I don't think so I I think we<00:37:27.760> can<00:37:27.920> do<00:37:28.040> more<00:37:28.280> than<00:37:28.480> that<00:37:29.079> because 00:37:29.510 --> 00:37:29.520 align:start position:0% we can do more than that because 00:37:29.520 --> 00:37:31.589 align:start position:0% we can do more than that because actually<00:37:30.119> the<00:37:30.280> internet<00:37:30.720> system<00:37:31.160> kind<00:37:31.319> of 00:37:31.589 --> 00:37:31.599 align:start position:0% actually the internet system kind of 00:37:31.599 --> 00:37:34.470 align:start position:0% actually the internet system kind of sucks<00:37:32.000> today<00:37:32.359> because<00:37:32.599> it's<00:37:32.880> centralized<00:37:33.880> DNS 00:37:34.470 --> 00:37:34.480 align:start position:0% sucks today because it's centralized DNS 00:37:34.480 --> 00:37:36.230 align:start position:0% sucks today because it's centralized DNS can<00:37:34.680> be<00:37:34.880> censored<00:37:35.480> and<00:37:35.599> there<00:37:35.680> are<00:37:35.880> countries 00:37:36.230 --> 00:37:36.240 align:start position:0% can be censored and there are countries 00:37:36.240 --> 00:37:37.710 align:start position:0% can be censored and there are countries that<00:37:36.359> don't<00:37:36.560> have<00:37:36.800> access<00:37:37.040> to<00:37:37.200> the<00:37:37.319> internet 00:37:37.710 --> 00:37:37.720 align:start position:0% that don't have access to the internet 00:37:37.720 --> 00:37:39.750 align:start position:0% that don't have access to the internet because<00:37:37.920> of<00:37:38.119> that<00:37:38.640> IP<00:37:39.000> system<00:37:39.359> can<00:37:39.560> make 00:37:39.750 --> 00:37:39.760 align:start position:0% because of that IP system can make 00:37:39.760 --> 00:37:41.750 align:start position:0% because of that IP system can make things<00:37:40.040> go<00:37:40.319> down<00:37:40.560> when<00:37:40.680> they<00:37:40.880> heard<00:37:41.200> too<00:37:41.480> many 00:37:41.750 --> 00:37:41.760 align:start position:0% things go down when they heard too many 00:37:41.760 --> 00:37:44.390 align:start position:0% things go down when they heard too many requests<00:37:42.760> all<00:37:42.960> of<00:37:43.200> those<00:37:43.520> are<00:37:43.760> centralized 00:37:44.390 --> 00:37:44.400 align:start position:0% requests all of those are centralized 00:37:44.400 --> 00:37:46.710 align:start position:0% requests all of those are centralized and<00:37:44.560> the<00:37:44.680> internet<00:37:45.079> is<00:37:45.319> kind<00:37:45.480> of<00:37:45.720> broken 00:37:46.710 --> 00:37:46.720 align:start position:0% and the internet is kind of broken 00:37:46.720 --> 00:37:48.430 align:start position:0% and the internet is kind of broken luckily<00:37:47.200> if<00:37:47.280> you<00:37:47.480> care<00:37:47.760> about<00:37:48.040> those<00:37:48.240> things 00:37:48.430 --> 00:37:48.440 align:start position:0% luckily if you care about those things 00:37:48.440 --> 00:37:50.950 align:start position:0% luckily if you care about those things you<00:37:48.599> came<00:37:48.800> to<00:37:48.920> the<00:37:49.160> right<00:37:49.440> place<00:37:50.240> if<00:37:50.359> you<00:37:50.560> stay 00:37:50.950 --> 00:37:50.960 align:start position:0% you came to the right place if you stay 00:37:50.960 --> 00:37:53.510 align:start position:0% you came to the right place if you stay here<00:37:51.640> until<00:37:51.960> the<00:37:52.160> until<00:37:52.440> the<00:37:52.640> talk<00:37:52.920> later<00:37:53.400> you 00:37:53.510 --> 00:37:53.520 align:start position:0% here until the until the talk later you 00:37:53.520 --> 00:37:55.829 align:start position:0% here until the until the talk later you can<00:37:53.800> talk<00:37:54.079> you<00:37:54.160> can<00:37:54.280> see<00:37:54.480> the<00:37:54.599> apfs<00:37:55.200> and<00:37:55.359> swarm 00:37:55.829 --> 00:37:55.839 align:start position:0% can talk you can see the apfs and swarm 00:37:55.839 --> 00:37:57.510 align:start position:0% can talk you can see the apfs and swarm talk<00:37:56.079> where<00:37:56.200> you<00:37:56.440> talk<00:37:56.680> about<00:37:56.880> how<00:37:56.960> to<00:37:57.079> make 00:37:57.510 --> 00:37:57.520 align:start position:0% talk where you talk about how to make 00:37:57.520 --> 00:37:59.910 align:start position:0% talk where you talk about how to make web<00:37:57.680> into<00:37:57.839> a<00:37:57.960> permanent<00:37:58.400> web<00:37:59.000> stay<00:37:59.440> stay<00:37:59.720> on 00:37:59.910 --> 00:37:59.920 align:start position:0% web into a permanent web stay stay on 00:37:59.920 --> 00:38:01.230 align:start position:0% web into a permanent web stay stay on the<00:38:00.079> on<00:38:00.200> the<00:38:00.319> rest<00:38:00.480> of<00:38:00.599> the<00:38:00.720> week<00:38:00.920> you'll<00:38:01.119> be 00:38:01.230 --> 00:38:01.240 align:start position:0% the on the rest of the week you'll be 00:38:01.240 --> 00:38:03.710 align:start position:0% the on the rest of the week you'll be able<00:38:01.560> how<00:38:01.880> you'll<00:38:02.079> see<00:38:02.319> how<00:38:02.440> we<00:38:02.560> can<00:38:03.280> replace 00:38:03.710 --> 00:38:03.720 align:start position:0% able how you'll see how we can replace 00:38:03.720 --> 00:38:06.069 align:start position:0% able how you'll see how we can replace the<00:38:03.839> DNS<00:38:04.359> system<00:38:04.640> for<00:38:04.800> a<00:38:04.920> register<00:38:05.640> contracts 00:38:06.069 --> 00:38:06.079 align:start position:0% the DNS system for a register contracts 00:38:06.079 --> 00:38:08.910 align:start position:0% the DNS system for a register contracts and<00:38:06.280> DEP<00:38:06.560> stores<00:38:07.240> and<00:38:07.440> now<00:38:07.680> of<00:38:07.880> that<00:38:08.680> and<00:38:08.839> I 00:38:08.910 --> 00:38:08.920 align:start position:0% and DEP stores and now of that and I 00:38:08.920 --> 00:38:11.150 align:start position:0% and DEP stores and now of that and I think<00:38:09.160> the<00:38:09.359> point<00:38:09.680> is<00:38:09.960> that<00:38:10.200> we<00:38:10.319> can<00:38:10.520> do<00:38:10.760> more 00:38:11.150 --> 00:38:11.160 align:start position:0% think the point is that we can do more 00:38:11.160 --> 00:38:13.270 align:start position:0% think the point is that we can do more with<00:38:11.400> itan<00:38:12.000> but<00:38:12.119> in<00:38:12.240> order<00:38:12.520> to<00:38:12.720> do<00:38:12.960> that<00:38:13.160> we 00:38:13.270 --> 00:38:13.280 align:start position:0% with itan but in order to do that we 00:38:13.280 --> 00:38:15.309 align:start position:0% with itan but in order to do that we need<00:38:13.599> everyone<00:38:14.040> here<00:38:14.520> together<00:38:14.839> the<00:38:15.000> Ki 00:38:15.309 --> 00:38:15.319 align:start position:0% need everyone here together the Ki 00:38:15.319 --> 00:38:17.030 align:start position:0% need everyone here together the Ki people<00:38:15.599> the<00:38:15.720> finance<00:38:16.240> people<00:38:16.560> the<00:38:16.720> power 00:38:17.030 --> 00:38:17.040 align:start position:0% people the finance people the power 00:38:17.040 --> 00:38:20.230 align:start position:0% people the finance people the power users<00:38:18.040> and<00:38:18.200> we<00:38:18.359> can<00:38:18.640> build<00:38:19.079> a<00:38:19.240> better<00:38:19.640> internet 00:38:20.230 --> 00:38:20.240 align:start position:0% users and we can build a better internet 00:38:20.240 --> 00:38:23.270 align:start position:0% users and we can build a better internet together<00:38:20.520> and<00:38:20.880> we<00:38:21.000> can<00:38:21.200> fix<00:38:21.640> the<00:38:22.119> internet<00:38:23.119> and 00:38:23.270 --> 00:38:23.280 align:start position:0% together and we can fix the internet and 00:38:23.280 --> 00:38:26.270 align:start position:0% together and we can fix the internet and we<00:38:23.440> can<00:38:23.640> do<00:38:23.839> it<00:38:24.440> this<00:38:24.680> week<00:38:25.240> so<00:38:25.760> thank<00:38:25.920> you<00:38:26.040> for 00:38:26.270 --> 00:38:26.280 align:start position:0% we can do it this week so thank you for 00:38:26.280 --> 00:38:34.100 align:start position:0% we can do it this week so thank you for coming 00:38:34.100 --> 00:38:34.110 align:start position:0% 00:38:34.110 --> 00:38:40.190 align:start position:0% [Applause] 00:38:40.190 --> 00:38:40.200 align:start position:0% 00:38:40.200 --> 00:38:43.470 align:start position:0% thank<00:38:40.400> you<00:38:40.599> Alex<00:38:41.160> also<00:38:41.520> known<00:38:41.800> as<00:38:42.119> Absa<00:38:43.119> it's 00:38:43.470 --> 00:38:43.480 align:start position:0% thank you Alex also known as Absa it's 00:38:43.480 --> 00:38:45.150 align:start position:0% thank you Alex also known as Absa it's very<00:38:43.760> special<00:38:44.040> to<00:38:44.280> have<00:38:44.400> him<00:38:44.599> here<00:38:44.760> today 00:38:45.150 --> 00:38:45.160 align:start position:0% very special to have him here today 00:38:45.160 --> 00:38:46.390 align:start position:0% very special to have him here today because<00:38:45.400> he's<00:38:45.599> come<00:38:45.800> all<00:38:45.960> the<00:38:46.040> way<00:38:46.200> from 00:38:46.390 --> 00:38:46.400 align:start position:0% because he's come all the way from 00:38:46.400 --> 00:38:50.150 align:start position:0% because he's come all the way from Brazil<00:38:47.240> to<00:38:47.480> speak<00:38:48.480> but<00:38:48.800> I<00:38:48.880> would<00:38:49.119> like<00:38:49.319> to<00:38:49.920> um 00:38:50.150 --> 00:38:50.160 align:start position:0% Brazil to speak but I would like to um 00:38:50.160 --> 00:38:51.910 align:start position:0% Brazil to speak but I would like to um since<00:38:50.400> we<00:38:50.520> only<00:38:50.760> have<00:38:51.000> five<00:38:51.200> more<00:38:51.480> minutes 00:38:51.910 --> 00:38:51.920 align:start position:0% since we only have five more minutes 00:38:51.920 --> 00:38:54.630 align:start position:0% since we only have five more minutes before<00:38:52.720> our<00:38:52.960> next<00:38:53.280> talk<00:38:53.640> I<00:38:53.720> would<00:38:53.960> like<00:38:54.480> uh 00:38:54.630 --> 00:38:54.640 align:start position:0% before our next talk I would like uh 00:38:54.640 --> 00:38:57.670 align:start position:0% before our next talk I would like uh Gavin<00:38:55.240> has<00:38:55.800> uh<00:38:56.520> will<00:38:56.960> answer<00:38:57.240> some<00:38:57.440> some 00:38:57.670 --> 00:38:57.680 align:start position:0% Gavin has uh will answer some some 00:38:57.680 --> 00:39:00.430 align:start position:0% Gavin has uh will answer some some questions<00:38:58.160> for<00:38:58.359> the<00:38:58.520> next<00:38:58.800> 5<00:38:59.200> minutes<00:39:00.200> uh 00:39:00.430 --> 00:39:00.440 align:start position:0% questions for the next 5 minutes uh 00:39:00.440 --> 00:39:02.589 align:start position:0% questions for the next 5 minutes uh because<00:39:01.079> actually<00:39:01.599> he<00:39:01.720> will<00:39:01.920> be<00:39:02.079> speaking 00:39:02.589 --> 00:39:02.599 align:start position:0% because actually he will be speaking 00:39:02.599 --> 00:39:04.710 align:start position:0% because actually he will be speaking quite<00:39:02.760> a<00:39:02.880> lot<00:39:03.160> the<00:39:03.280> rest<00:39:03.440> of<00:39:03.560> the<00:39:03.720> week<00:39:04.359> later 00:39:04.710 --> 00:39:04.720 align:start position:0% quite a lot the rest of the week later 00:39:04.720 --> 00:39:07.470 align:start position:0% quite a lot the rest of the week later today<00:39:05.200> he<00:39:05.400> will<00:39:05.599> be<00:39:06.160> uh<00:39:06.400> on<00:39:06.560> the<00:39:06.680> scalability 00:39:07.470 --> 00:39:07.480 align:start position:0% today he will be uh on the scalability 00:39:07.480 --> 00:39:11.030 align:start position:0% today he will be uh on the scalability panel<00:39:08.160> at<00:39:08.760> 11:15<00:39:09.760> on<00:39:10.040> Wednesday<00:39:10.560> he<00:39:10.680> will<00:39:10.839> be 00:39:11.030 --> 00:39:11.040 align:start position:0% panel at 11:15 on Wednesday he will be 00:39:11.040 --> 00:39:15.950 align:start position:0% panel at 11:15 on Wednesday he will be speaking<00:39:11.480> about<00:39:11.960> whisper<00:39:12.960> at<00:39:13.599> 1:25<00:39:14.760> p.m.<00:39:15.760> uh 00:39:15.950 --> 00:39:15.960 align:start position:0% speaking about whisper at 1:25 p.m. uh 00:39:15.960 --> 00:39:18.950 align:start position:0% speaking about whisper at 1:25 p.m. uh Thursday<00:39:16.839> Gavin<00:39:17.200> will<00:39:17.359> be<00:39:17.480> on<00:39:17.680> the<00:39:18.400> ethereum 00:39:18.950 --> 00:39:18.960 align:start position:0% Thursday Gavin will be on the ethereum 00:39:18.960 --> 00:39:23.270 align:start position:0% Thursday Gavin will be on the ethereum clients<00:39:19.480> panel<00:39:20.480> at<00:39:20.920> 1:50<00:39:21.920> and<00:39:22.119> then<00:39:22.800> Friday 00:39:23.270 --> 00:39:23.280 align:start position:0% clients panel at 1:50 and then Friday 00:39:23.280 --> 00:39:26.990 align:start position:0% clients panel at 1:50 and then Friday ethereum<00:39:23.760> for<00:39:23.960> dummies<00:39:24.800> and<00:39:25.760> also<00:39:26.400> Pathway<00:39:26.839> to 00:39:26.990 --> 00:39:27.000 align:start position:0% ethereum for dummies and also Pathway to 00:39:27.000 --> 00:39:29.790 align:start position:0% ethereum for dummies and also Pathway to ethereum<00:39:27.560> adoption<00:39:28.520> so<00:39:28.960> Gavin<00:39:29.240> if<00:39:29.359> you<00:39:29.480> would 00:39:29.790 --> 00:39:29.800 align:start position:0% ethereum adoption so Gavin if you would 00:39:29.800 --> 00:39:33.890 align:start position:0% ethereum adoption so Gavin if you would come<00:39:30.000> up<00:39:30.440> you<00:39:31.440> thank 00:39:33.890 --> 00:39:33.900 align:start position:0% 00:39:33.900 --> 00:39:36.589 align:start position:0% [Applause] 00:39:36.589 --> 00:39:36.599 align:start position:0% [Applause] 00:39:36.599 --> 00:39:41.589 align:start position:0% [Applause] you<00:39:37.599> yeah<00:39:38.160> thanks<00:39:38.800> um<00:39:39.680> yeah<00:39:39.960> this<00:39:40.040> is<00:39:40.599> amazing 00:39:41.589 --> 00:39:41.599 align:start position:0% you yeah thanks um yeah this is amazing 00:39:41.599 --> 00:39:43.390 align:start position:0% you yeah thanks um yeah this is amazing uh<00:39:41.760> this<00:39:41.839> is<00:39:42.040> somewhat<00:39:42.440> more<00:39:42.800> marbl<00:39:43.200> and 00:39:43.390 --> 00:39:43.400 align:start position:0% uh this is somewhat more marbl and 00:39:43.400 --> 00:39:45.150 align:start position:0% uh this is somewhat more marbl and wooden<00:39:43.839> crystal<00:39:44.160> chandeliers<00:39:44.839> than<00:39:45.000> the 00:39:45.150 --> 00:39:45.160 align:start position:0% wooden crystal chandeliers than the 00:39:45.160 --> 00:39:48.390 align:start position:0% wooden crystal chandeliers than the Berlin<00:39:45.680> office<00:39:46.680> where<00:39:46.800> we<00:39:46.920> have<00:39:47.119> Dev<00:39:47.400> con<00:39:47.599> zero 00:39:48.390 --> 00:39:48.400 align:start position:0% Berlin office where we have Dev con zero 00:39:48.400 --> 00:39:52.069 align:start position:0% Berlin office where we have Dev con zero no<00:39:48.560> this<00:39:48.680> is<00:39:48.880> this<00:39:49.000> is<00:39:49.400> quality<00:39:50.880> um<00:39:51.880> it's 00:39:52.069 --> 00:39:52.079 align:start position:0% no this is this is quality um it's 00:39:52.079 --> 00:39:56.150 align:start position:0% no this is this is quality um it's brilliant<00:39:52.440> to<00:39:52.640> hear<00:39:53.599> um<00:39:54.280> about<00:39:54.720> the<00:39:55.160> browser 00:39:56.150 --> 00:39:56.160 align:start position:0% brilliant to hear um about the browser 00:39:56.160 --> 00:39:58.390 align:start position:0% brilliant to hear um about the browser um<00:39:56.560> it's 00:39:58.390 --> 00:39:58.400 align:start position:0% um it's 00:39:58.400 --> 00:40:01.910 align:start position:0% um it's really<00:39:59.400> uh<00:39:59.800> thinking<00:40:00.240> back<00:40:00.440> to<00:40:01.240> uh<00:40:01.440> January 00:40:01.910 --> 00:40:01.920 align:start position:0% really uh thinking back to uh January 00:40:01.920 --> 00:40:04.510 align:start position:0% really uh thinking back to uh January 2014<00:40:02.720> when<00:40:03.079> we<00:40:03.240> got<00:40:03.520> together<00:40:03.760> in<00:40:03.920> Miami<00:40:04.359> and 00:40:04.510 --> 00:40:04.520 align:start position:0% 2014 when we got together in Miami and 00:40:04.520 --> 00:40:06.630 align:start position:0% 2014 when we got together in Miami and kind<00:40:04.640> of<00:40:04.760> sketched<00:40:05.160> out<00:40:05.960> what<00:40:06.119> we<00:40:06.240> all<00:40:06.400> thought 00:40:06.630 --> 00:40:06.640 align:start position:0% kind of sketched out what we all thought 00:40:06.640 --> 00:40:09.470 align:start position:0% kind of sketched out what we all thought ethereum<00:40:07.079> was<00:40:07.200> going<00:40:07.359> to<00:40:07.520> be<00:40:07.800> and<00:40:08.079> then<00:40:09.079> um 00:40:09.470 --> 00:40:09.480 align:start position:0% ethereum was going to be and then um 00:40:09.480 --> 00:40:13.150 align:start position:0% ethereum was going to be and then um later<00:40:10.319> 3<00:40:10.680> months<00:40:11.680> um<00:40:12.119> figuring<00:40:12.560> out<00:40:12.800> with<00:40:13.000> with 00:40:13.150 --> 00:40:13.160 align:start position:0% later 3 months um figuring out with with 00:40:13.160 --> 00:40:16.470 align:start position:0% later 3 months um figuring out with with people<00:40:13.520> like<00:40:13.680> this<00:40:13.839> notion<00:40:14.119> of<00:40:14.280> web<00:40:14.520> 3<00:40:15.319> and<00:40:16.319> how 00:40:16.470 --> 00:40:16.480 align:start position:0% people like this notion of web 3 and how 00:40:16.480 --> 00:40:19.589 align:start position:0% people like this notion of web 3 and how we<00:40:16.640> can<00:40:17.280> how<00:40:17.440> we<00:40:17.560> can<00:40:17.839> rethink<00:40:18.839> um<00:40:19.079> how 00:40:19.589 --> 00:40:19.599 align:start position:0% we can how we can rethink um how 00:40:19.599 --> 00:40:21.470 align:start position:0% we can how we can rethink um how massively<00:40:20.040> multi-user<00:40:20.760> applications<00:40:21.240> are 00:40:21.470 --> 00:40:21.480 align:start position:0% massively multi-user applications are 00:40:21.480 --> 00:40:23.910 align:start position:0% massively multi-user applications are done<00:40:22.200> and<00:40:22.359> seeing<00:40:22.720> it<00:40:23.040> you<00:40:23.160> know<00:40:23.560> come 00:40:23.910 --> 00:40:23.920 align:start position:0% done and seeing it you know come 00:40:23.920 --> 00:40:27.069 align:start position:0% done and seeing it you know come together<00:40:24.680> um<00:40:25.079> in<00:40:25.280> such<00:40:25.520> an<00:40:26.040> amazing<00:40:26.680> amazingly 00:40:27.069 --> 00:40:27.079 align:start position:0% together um in such an amazing amazingly 00:40:27.079 --> 00:40:29.950 align:start position:0% together um in such an amazing amazingly Prof<00:40:27.359> professional<00:40:27.800> way<00:40:28.079> I<00:40:28.160> mean<00:40:28.760> um<00:40:29.280> Absa<00:40:29.800> and 00:40:29.950 --> 00:40:29.960 align:start position:0% Prof professional way I mean um Absa and 00:40:29.960 --> 00:40:33.069 align:start position:0% Prof professional way I mean um Absa and Fabian<00:40:30.720> and<00:40:30.839> the<00:40:30.960> team<00:40:31.720> are<00:40:31.920> really<00:40:32.920> they've 00:40:33.069 --> 00:40:33.079 align:start position:0% Fabian and the team are really they've 00:40:33.079 --> 00:40:38.030 align:start position:0% Fabian and the team are really they've done<00:40:33.319> amazing<00:40:34.079> work<00:40:35.079> um<00:40:36.079> from<00:40:36.440> my<00:40:37.440> uh<00:40:37.560> from<00:40:37.800> my 00:40:38.030 --> 00:40:38.040 align:start position:0% done amazing work um from my uh from my 00:40:38.040 --> 00:40:39.309 align:start position:0% done amazing work um from my uh from my side 00:40:39.309 --> 00:40:39.319 align:start position:0% side 00:40:39.319 --> 00:40:43.470 align:start position:0% side um<00:40:40.319> uh<00:40:40.760> solidity<00:40:41.760> uh<00:40:41.880> seeing<00:40:42.319> that<00:40:42.760> come<00:40:43.280> uh 00:40:43.470 --> 00:40:43.480 align:start position:0% um uh solidity uh seeing that come uh 00:40:43.480 --> 00:40:44.510 align:start position:0% um uh solidity uh seeing that come uh developed 00:40:44.510 --> 00:40:44.520 align:start position:0% developed 00:40:44.520 --> 00:40:46.829 align:start position:0% developed from<00:40:45.520> what<00:40:45.680> was<00:40:45.880> essentially<00:40:46.319> a<00:40:46.480> sort<00:40:46.640> of 00:40:46.829 --> 00:40:46.839 align:start position:0% from what was essentially a sort of 00:40:46.839 --> 00:40:49.069 align:start position:0% from what was essentially a sort of dream<00:40:47.319> programming<00:40:47.839> language<00:40:48.680> uh<00:40:48.800> all<00:40:48.960> the 00:40:49.069 --> 00:40:49.079 align:start position:0% dream programming language uh all the 00:40:49.079 --> 00:40:51.390 align:start position:0% dream programming language uh all the way<00:40:49.319> to<00:40:50.000> uh<00:40:50.280> to<00:40:50.400> where<00:40:50.560> it<00:40:50.640> is<00:40:50.839> now<00:40:51.040> you<00:40:51.119> know 00:40:51.390 --> 00:40:51.400 align:start position:0% way to uh to where it is now you know 00:40:51.400 --> 00:40:54.190 align:start position:0% way to uh to where it is now you know thanks<00:40:51.640> to<00:40:52.000> to<00:40:52.200> Christian<00:40:52.640> and<00:40:52.800> the<00:40:53.079> team<00:40:54.079> uh 00:40:54.190 --> 00:40:54.200 align:start position:0% thanks to to Christian and the team uh 00:40:54.200 --> 00:40:58.470 align:start position:0% thanks to to Christian and the team uh for<00:40:54.359> bringing<00:40:54.760> that<00:40:55.480> together<00:40:56.480> and 00:40:58.470 --> 00:40:58.480 align:start position:0% for bringing that together and 00:40:58.480 --> 00:41:03.069 align:start position:0% for bringing that together and um<00:40:59.480> yeah<00:41:00.240> in<00:41:00.480> general<00:41:01.040> the<00:41:01.400> the<00:41:01.520> CPP<00:41:02.119> client<00:41:02.560> is 00:41:03.069 --> 00:41:03.079 align:start position:0% um yeah in general the the CPP client is 00:41:03.079 --> 00:41:06.910 align:start position:0% um yeah in general the the CPP client is is<00:41:03.560> um<00:41:04.560> is<00:41:04.720> coming<00:41:05.000> on<00:41:05.319> thanks<00:41:05.599> to<00:41:06.160> U<00:41:06.440> pavl<00:41:06.800> and 00:41:06.910 --> 00:41:06.920 align:start position:0% is um is coming on thanks to U pavl and 00:41:06.920 --> 00:41:10.710 align:start position:0% is um is coming on thanks to U pavl and arade<00:41:07.760> uh<00:41:07.880> doing<00:41:08.440> amazing<00:41:08.880> work<00:41:09.079> on 00:41:10.710 --> 00:41:10.720 align:start position:0% arade uh doing amazing work on 00:41:10.720 --> 00:41:14.309 align:start position:0% arade uh doing amazing work on that<00:41:11.720> in<00:41:11.880> terms<00:41:12.160> of<00:41:12.319> where<00:41:12.440> we're<00:41:12.640> going<00:41:13.319> next 00:41:14.309 --> 00:41:14.319 align:start position:0% that in terms of where we're going next 00:41:14.319 --> 00:41:17.270 align:start position:0% that in terms of where we're going next um<00:41:15.200> I<00:41:15.319> think<00:41:15.839> I<00:41:16.000> probably<00:41:16.280> refer<00:41:16.680> to<00:41:17.000> some<00:41:17.119> of 00:41:17.270 --> 00:41:17.280 align:start position:0% um I think I probably refer to some of 00:41:17.280 --> 00:41:19.030 align:start position:0% um I think I probably refer to some of what<00:41:17.440> Jeff<00:41:17.680> is<00:41:17.880> saying<00:41:18.400> um<00:41:18.560> certainly<00:41:18.920> the 00:41:19.030 --> 00:41:19.040 align:start position:0% what Jeff is saying um certainly the 00:41:19.040 --> 00:41:21.670 align:start position:0% what Jeff is saying um certainly the turbo<00:41:19.400> syncing<00:41:19.880> stuff<00:41:20.680> but<00:41:21.040> uh<00:41:21.200> the<00:41:21.359> thing<00:41:21.520> I'm 00:41:21.670 --> 00:41:21.680 align:start position:0% turbo syncing stuff but uh the thing I'm 00:41:21.680 --> 00:41:23.589 align:start position:0% turbo syncing stuff but uh the thing I'm most<00:41:21.920> excited<00:41:22.319> about<00:41:22.560> at<00:41:22.760> this<00:41:22.960> point<00:41:23.319> is<00:41:23.480> some 00:41:23.589 --> 00:41:23.599 align:start position:0% most excited about at this point is some 00:41:23.599 --> 00:41:25.630 align:start position:0% most excited about at this point is some of<00:41:23.800> the<00:41:24.119> uh<00:41:24.560> the<00:41:24.680> refactoring<00:41:25.280> I've<00:41:25.440> been 00:41:25.630 --> 00:41:25.640 align:start position:0% of the uh the refactoring I've been 00:41:25.640 --> 00:41:28.109 align:start position:0% of the uh the refactoring I've been doing<00:41:26.319> um<00:41:26.760> I've<00:41:26.920> recently<00:41:27.440> ly<00:41:27.560> given<00:41:27.880> the 00:41:28.109 --> 00:41:28.119 align:start position:0% doing um I've recently ly given the 00:41:28.119 --> 00:41:30.790 align:start position:0% doing um I've recently ly given the client<00:41:28.920> what<00:41:29.160> might<00:41:29.359> be<00:41:29.520> sort<00:41:29.720> of<00:41:30.319> considered 00:41:30.790 --> 00:41:30.800 align:start position:0% client what might be sort of considered 00:41:30.800 --> 00:41:33.230 align:start position:0% client what might be sort of considered a<00:41:30.960> heart<00:41:31.240> transplant<00:41:31.960> in<00:41:32.119> terms<00:41:32.440> of<00:41:32.920> uh<00:41:33.119> in 00:41:33.230 --> 00:41:33.240 align:start position:0% a heart transplant in terms of uh in 00:41:33.240 --> 00:41:35.589 align:start position:0% a heart transplant in terms of uh in terms<00:41:33.440> of<00:41:33.560> what<00:41:33.680> needed<00:41:33.920> to<00:41:34.040> be<00:41:34.200> done<00:41:34.560> but<00:41:35.160> um 00:41:35.589 --> 00:41:35.599 align:start position:0% terms of what needed to be done but um 00:41:35.599 --> 00:41:37.910 align:start position:0% terms of what needed to be done but um it's<00:41:35.800> now<00:41:36.040> complete<00:41:36.960> uh<00:41:37.079> the<00:41:37.200> client<00:41:37.720> is 00:41:37.910 --> 00:41:37.920 align:start position:0% it's now complete uh the client is 00:41:37.920 --> 00:41:40.710 align:start position:0% it's now complete uh the client is largely<00:41:38.319> a<00:41:38.480> plug-in<00:41:38.880> based<00:41:39.440> system<00:41:39.880> now<00:41:40.560> what 00:41:40.710 --> 00:41:40.720 align:start position:0% largely a plug-in based system now what 00:41:40.720 --> 00:41:44.550 align:start position:0% largely a plug-in based system now what this<00:41:40.839> means<00:41:41.160> is<00:41:41.440> that<00:41:42.040> much<00:41:42.640> of<00:41:43.079> the<00:41:43.720> uh<00:41:44.119> core 00:41:44.550 --> 00:41:44.560 align:start position:0% this means is that much of the uh core 00:41:44.560 --> 00:41:47.870 align:start position:0% this means is that much of the uh core logic<00:41:45.560> um<00:41:46.160> is<00:41:46.720> uh<00:41:46.800> stored<00:41:47.160> in<00:41:47.480> Dynamic 00:41:47.870 --> 00:41:47.880 align:start position:0% logic um is uh stored in Dynamic 00:41:47.880 --> 00:41:49.270 align:start position:0% logic um is uh stored in Dynamic libraries<00:41:48.319> that<00:41:48.400> can<00:41:48.520> be<00:41:48.599> placed<00:41:49.000> together 00:41:49.270 --> 00:41:49.280 align:start position:0% libraries that can be placed together 00:41:49.280 --> 00:41:51.270 align:start position:0% libraries that can be placed together through<00:41:49.560> a<00:41:50.119> uh<00:41:50.240> very<00:41:50.480> simple<00:41:50.800> Json 00:41:51.270 --> 00:41:51.280 align:start position:0% through a uh very simple Json 00:41:51.280 --> 00:41:54.550 align:start position:0% through a uh very simple Json configuration<00:41:52.119> file<00:41:53.119> um<00:41:53.560> what<00:41:53.800> this<00:41:53.920> means<00:41:54.280> is 00:41:54.550 --> 00:41:54.560 align:start position:0% configuration file um what this means is 00:41:54.560 --> 00:41:57.349 align:start position:0% configuration file um what this means is that<00:41:54.880> the<00:41:55.359> uh<00:41:55.560> consensus<00:41:56.160> protocol<00:41:56.880> is 00:41:57.349 --> 00:41:57.359 align:start position:0% that the uh consensus protocol is 00:41:57.359 --> 00:41:59.870 align:start position:0% that the uh consensus protocol is largely<00:41:57.880> able<00:41:58.160> to<00:41:58.319> be<00:41:58.880> uh<00:41:59.040> constituted<00:41:59.760> and 00:41:59.870 --> 00:41:59.880 align:start position:0% largely able to be uh constituted and 00:41:59.880 --> 00:42:01.190 align:start position:0% largely able to be uh constituted and swapped<00:42:00.280> in<00:42:00.400> and 00:42:01.190 --> 00:42:01.200 align:start position:0% swapped in and 00:42:01.200 --> 00:42:04.829 align:start position:0% swapped in and out<00:42:02.400> um<00:42:03.400> I<00:42:03.560> foresee<00:42:04.040> this<00:42:04.200> as<00:42:04.359> being<00:42:04.560> a<00:42:04.680> very 00:42:04.829 --> 00:42:04.839 align:start position:0% out um I foresee this as being a very 00:42:04.839 --> 00:42:09.069 align:start position:0% out um I foresee this as being a very useful<00:42:05.359> thing<00:42:05.680> for<00:42:06.280> when<00:42:06.440> we<00:42:06.599> move<00:42:06.960> to<00:42:07.640> uh 00:42:09.069 --> 00:42:09.079 align:start position:0% useful thing for when we move to uh 00:42:09.079 --> 00:42:13.470 align:start position:0% useful thing for when we move to uh Casper<00:42:10.079> um<00:42:10.960> ideally<00:42:11.960> um<00:42:12.319> it's<00:42:12.599> designed<00:42:13.160> such 00:42:13.470 --> 00:42:13.480 align:start position:0% Casper um ideally um it's designed such 00:42:13.480 --> 00:42:16.510 align:start position:0% Casper um ideally um it's designed such that<00:42:14.359> um<00:42:15.000> the<00:42:15.160> move<00:42:15.359> to<00:42:15.560> Casper<00:42:15.920> is<00:42:16.040> as<00:42:16.160> simple 00:42:16.510 --> 00:42:16.520 align:start position:0% that um the move to Casper is as simple 00:42:16.520 --> 00:42:22.230 align:start position:0% that um the move to Casper is as simple as<00:42:17.280> uh<00:42:17.440> deleting<00:42:18.800> eash<00:42:19.800> and<00:42:20.200> uh<00:42:20.440> and<00:42:20.800> typing<00:42:21.800> uh 00:42:22.230 --> 00:42:22.240 align:start position:0% as uh deleting eash and uh and typing uh 00:42:22.240 --> 00:42:24.150 align:start position:0% as uh deleting eash and uh and typing uh Casper<00:42:23.240> uh<00:42:23.400> that's<00:42:23.559> certainly<00:42:23.880> what<00:42:23.960> we're 00:42:24.150 --> 00:42:24.160 align:start position:0% Casper uh that's certainly what we're 00:42:24.160 --> 00:42:27.829 align:start position:0% Casper uh that's certainly what we're aiming<00:42:24.440> to<00:42:25.160> the<00:42:25.359> alth<00:42:26.160> family<00:42:26.680> of 00:42:27.829 --> 00:42:27.839 align:start position:0% aiming to the alth family of 00:42:27.839 --> 00:42:30.589 align:start position:0% aiming to the alth family of applications<00:42:28.839> have<00:42:29.040> also<00:42:29.280> been<00:42:29.720> revamped 00:42:30.589 --> 00:42:30.599 align:start position:0% applications have also been revamped 00:42:30.599 --> 00:42:33.109 align:start position:0% applications have also been revamped there's<00:42:30.920> a<00:42:31.119> new<00:42:31.800> um<00:42:32.160> abstraction<00:42:32.640> layer<00:42:32.920> for 00:42:33.109 --> 00:42:33.119 align:start position:0% there's a new um abstraction layer for 00:42:33.119 --> 00:42:34.910 align:start position:0% there's a new um abstraction layer for each<00:42:33.319> of<00:42:33.480> them<00:42:34.119> uh<00:42:34.200> some<00:42:34.359> of<00:42:34.480> you<00:42:34.640> might<00:42:34.760> have 00:42:34.910 --> 00:42:34.920 align:start position:0% each of them uh some of you might have 00:42:34.920 --> 00:42:37.990 align:start position:0% each of them uh some of you might have already<00:42:35.200> seen<00:42:35.440> lf1<00:42:36.240> the<00:42:36.640> uh<00:42:36.839> the<00:42:36.920> mining<00:42:37.599> front 00:42:37.990 --> 00:42:38.000 align:start position:0% already seen lf1 the uh the mining front 00:42:38.000 --> 00:42:42.630 align:start position:0% already seen lf1 the uh the mining front end<00:42:39.079> um<00:42:40.079> there's<00:42:40.480> also<00:42:41.319> lf5<00:42:42.079> coming<00:42:42.440> which<00:42:42.559> is 00:42:42.630 --> 00:42:42.640 align:start position:0% end um there's also lf5 coming which is 00:42:42.640 --> 00:42:45.910 align:start position:0% end um there's also lf5 coming which is a<00:42:42.800> very<00:42:43.079> simplified<00:42:44.079> um<00:42:44.800> um<00:42:45.040> holster<00:42:45.599> for 00:42:45.910 --> 00:42:45.920 align:start position:0% a very simplified um um holster for 00:42:45.920 --> 00:42:49.069 align:start position:0% a very simplified um um holster for applications<00:42:46.839> much<00:42:47.079> the<00:42:47.240> same<00:42:47.839> uh<00:42:48.359> ultimately 00:42:49.069 --> 00:42:49.079 align:start position:0% applications much the same uh ultimately 00:42:49.079 --> 00:42:50.589 align:start position:0% applications much the same uh ultimately the<00:42:49.200> idea<00:42:49.480> being<00:42:49.680> that<00:42:49.800> it<00:42:49.880> will<00:42:49.960> be<00:42:50.079> able<00:42:50.200> to 00:42:50.589 --> 00:42:50.599 align:start position:0% the idea being that it will be able to 00:42:50.599 --> 00:42:54.150 align:start position:0% the idea being that it will be able to host<00:42:51.040> mist<00:42:52.040> and<00:42:52.280> alth<00:42:52.760> Zer<00:42:53.079> has<00:42:53.240> been<00:42:53.720> um 00:42:54.150 --> 00:42:54.160 align:start position:0% host mist and alth Zer has been um 00:42:54.160 --> 00:42:57.309 align:start position:0% host mist and alth Zer has been um rearchitecturing 00:42:57.309 --> 00:42:57.319 align:start position:0% 00:42:57.319 --> 00:43:00.309 align:start position:0% um<00:42:58.040> blockchain<00:42:58.520> exploration 00:43:00.309 --> 00:43:00.319 align:start position:0% um blockchain exploration 00:43:00.319 --> 00:43:04.190 align:start position:0% um blockchain exploration environment<00:43:01.319> um<00:43:02.440> which<00:43:03.440> should<00:43:03.760> go<00:43:04.000> hand 00:43:04.190 --> 00:43:04.200 align:start position:0% environment um which should go hand 00:43:04.200 --> 00:43:07.230 align:start position:0% environment um which should go hand inand<00:43:04.920> with<00:43:05.240> the<00:43:05.920> uh<00:43:06.119> the<00:43:06.440> core<00:43:06.720> refactoring 00:43:07.230 --> 00:43:07.240 align:start position:0% inand with the uh the core refactoring 00:43:07.240 --> 00:43:09.349 align:start position:0% inand with the uh the core refactoring to<00:43:07.400> make<00:43:07.640> something<00:43:08.040> that's<00:43:08.520> um<00:43:08.720> incredibly 00:43:09.349 --> 00:43:09.359 align:start position:0% to make something that's um incredibly 00:43:09.359 --> 00:43:12.030 align:start position:0% to make something that's um incredibly flexible<00:43:10.200> for<00:43:10.599> doing<00:43:11.040> all<00:43:11.240> sorts<00:43:11.559> of<00:43:11.920> uh 00:43:12.030 --> 00:43:12.040 align:start position:0% flexible for doing all sorts of uh 00:43:12.040 --> 00:43:14.870 align:start position:0% flexible for doing all sorts of uh blockchainbased<00:43:12.839> um<00:43:13.839> development<00:43:14.559> trying 00:43:14.870 --> 00:43:14.880 align:start position:0% blockchainbased um development trying 00:43:14.880 --> 00:43:18.470 align:start position:0% blockchainbased um development trying out<00:43:15.079> new<00:43:15.319> ideas<00:43:16.319> and<00:43:16.680> getting<00:43:17.040> something<00:43:17.520> from 00:43:18.470 --> 00:43:18.480 align:start position:0% out new ideas and getting something from 00:43:18.480 --> 00:43:23.990 align:start position:0% out new ideas and getting something from um<00:43:19.440> a<00:43:20.040> uh<00:43:20.520> a<00:43:20.640> simple<00:43:20.920> sort<00:43:21.160> of<00:43:21.960> um<00:43:22.960> base<00:43:23.280> set<00:43:23.559> of 00:43:23.990 --> 00:43:24.000 align:start position:0% um a uh a simple sort of um base set of 00:43:24.000 --> 00:43:26.390 align:start position:0% um a uh a simple sort of um base set of of<00:43:24.160> assumptions<00:43:24.800> right<00:43:25.119> the<00:43:25.200> way<00:43:25.359> through<00:43:25.559> to 00:43:26.390 --> 00:43:26.400 align:start position:0% of assumptions right the way through to 00:43:26.400 --> 00:43:30.190 align:start position:0% of assumptions right the way through to um<00:43:26.559> something<00:43:26.800> that's<00:43:26.920> wor<00:43:27.200> workable<00:43:28.200> um<00:43:28.480> in 00:43:30.190 --> 00:43:30.200 align:start position:0% um something that's wor workable um in 00:43:30.200 --> 00:43:33.710 align:start position:0% um something that's wor workable um in Industry<00:43:31.200> um<00:43:31.440> yeah<00:43:31.599> for<00:43:31.880> my<00:43:32.680> um<00:43:33.079> for<00:43:33.240> my<00:43:33.440> talk 00:43:33.710 --> 00:43:33.720 align:start position:0% Industry um yeah for my um for my talk 00:43:33.720 --> 00:43:37.630 align:start position:0% Industry um yeah for my um for my talk I'd<00:43:34.000> kind<00:43:34.160> of<00:43:34.359> like<00:43:34.599> to<00:43:35.400> uh<00:43:35.559> open<00:43:36.559> open<00:43:36.800> up<00:43:36.960> to 00:43:37.630 --> 00:43:37.640 align:start position:0% I'd kind of like to uh open open up to 00:43:37.640 --> 00:43:40.710 align:start position:0% I'd kind of like to uh open open up to questions<00:43:38.640> um<00:43:39.040> so<00:43:39.440> if<00:43:39.599> there<00:43:39.760> are<00:43:40.119> I<00:43:40.400> probably 00:43:40.710 --> 00:43:40.720 align:start position:0% questions um so if there are I probably 00:43:40.720 --> 00:43:42.150 align:start position:0% questions um so if there are I probably only<00:43:40.880> got<00:43:41.000> a<00:43:41.119> minute<00:43:41.319> or<00:43:41.440> two<00:43:41.640> left<00:43:41.960> but<00:43:42.040> if 00:43:42.150 --> 00:43:42.160 align:start position:0% only got a minute or two left but if 00:43:42.160 --> 00:43:43.750 align:start position:0% only got a minute or two left but if there<00:43:42.280> are<00:43:42.400> one<00:43:42.520> or<00:43:42.599> two<00:43:42.760> questions<00:43:43.319> then<00:43:43.640> I'm 00:43:43.750 --> 00:43:43.760 align:start position:0% there are one or two questions then I'm 00:43:43.760 --> 00:43:47.309 align:start position:0% there are one or two questions then I'm happy<00:43:43.960> to<00:43:44.079> answer 00:43:47.309 --> 00:43:47.319 align:start position:0% 00:43:47.319 --> 00:43:50.870 align:start position:0% them<00:43:48.319> yeah<00:43:49.040> what's<00:43:49.200> your<00:43:49.440> favorite<00:43:50.119> uh<00:43:50.400> D 00:43:50.870 --> 00:43:50.880 align:start position:0% them yeah what's your favorite uh D 00:43:50.880 --> 00:43:52.549 align:start position:0% them yeah what's your favorite uh D either 00:43:52.549 --> 00:43:52.559 align:start position:0% either 00:43:52.559 --> 00:43:56.069 align:start position:0% either devel<00:43:53.559> exced<00:43:54.400> well<00:43:54.599> gcoin<00:43:55.079> was<00:43:55.280> pretty<00:43:55.520> good 00:43:56.069 --> 00:43:56.079 align:start position:0% devel exced well gcoin was pretty good 00:43:56.079 --> 00:43:59.470 align:start position:0% devel exced well gcoin was pretty good but<00:43:56.520> um 00:43:59.470 --> 00:43:59.480 align:start position:0% 00:43:59.480 --> 00:44:03.109 align:start position:0% um<00:43:59.920> to<00:44:00.079> be<00:44:00.240> honest<00:44:00.680> I<00:44:00.800> think 00:44:03.109 --> 00:44:03.119 align:start position:0% um to be honest I think 00:44:03.119 --> 00:44:06.549 align:start position:0% um to be honest I think um<00:44:04.119> having<00:44:04.400> heard<00:44:04.760> Christoff<00:44:05.319> Yen<00:44:05.680> talk<00:44:05.920> about 00:44:06.549 --> 00:44:06.559 align:start position:0% um having heard Christoff Yen talk about 00:44:06.559 --> 00:44:09.750 align:start position:0% um having heard Christoff Yen talk about um<00:44:07.160> slockett<00:44:08.160> um<00:44:08.480> I'm<00:44:08.680> I'm<00:44:08.880> kind<00:44:09.000> of<00:44:09.520> it's<00:44:09.640> one 00:44:09.750 --> 00:44:09.760 align:start position:0% um slockett um I'm I'm kind of it's one 00:44:09.760 --> 00:44:11.109 align:start position:0% um slockett um I'm I'm kind of it's one of<00:44:09.839> the<00:44:09.960> things<00:44:10.119> that<00:44:10.280> really<00:44:10.480> got<00:44:10.599> me<00:44:10.800> geared 00:44:11.109 --> 00:44:11.119 align:start position:0% of the things that really got me geared 00:44:11.119 --> 00:44:13.950 align:start position:0% of the things that really got me geared up<00:44:11.640> to<00:44:11.839> seeing<00:44:12.280> wow<00:44:12.480> you<00:44:12.599> know<00:44:12.800> this<00:44:12.920> is<00:44:13.480> uh 00:44:13.950 --> 00:44:13.960 align:start position:0% up to seeing wow you know this is uh 00:44:13.960 --> 00:44:15.430 align:start position:0% up to seeing wow you know this is uh this<00:44:14.040> is<00:44:14.240> something<00:44:14.520> that<00:44:14.680> really<00:44:15.240> really 00:44:15.430 --> 00:44:15.440 align:start position:0% this is something that really really 00:44:15.440 --> 00:44:18.990 align:start position:0% this is something that really really could<00:44:15.599> change<00:44:15.880> the<00:44:16.000> world<00:44:16.800> it's<00:44:17.800> um<00:44:18.640> for<00:44:18.839> those 00:44:18.990 --> 00:44:19.000 align:start position:0% could change the world it's um for those 00:44:19.000 --> 00:44:22.750 align:start position:0% could change the world it's um for those that<00:44:19.119> don't<00:44:19.319> know<00:44:19.520> slockit<00:44:20.119> is<00:44:20.319> a<00:44:21.480> um<00:44:22.480> is<00:44:22.599> a 00:44:22.750 --> 00:44:22.760 align:start position:0% that don't know slockit is a um is a 00:44:22.760 --> 00:44:25.910 align:start position:0% that don't know slockit is a um is a system<00:44:23.119> for<00:44:24.079> in<00:44:24.280> principle<00:44:24.760> opening<00:44:25.200> blocks 00:44:25.910 --> 00:44:25.920 align:start position:0% system for in principle opening blocks 00:44:25.920 --> 00:44:28.710 align:start position:0% system for in principle opening blocks via<00:44:26.160> the<00:44:26.280> blockchain<00:44:27.240> um<00:44:27.760> but<00:44:28.040> the<00:44:28.200> vision<00:44:28.520> is 00:44:28.710 --> 00:44:28.720 align:start position:0% via the blockchain um but the vision is 00:44:28.720 --> 00:44:31.670 align:start position:0% via the blockchain um but the vision is somewhat<00:44:29.079> more<00:44:29.880> um<00:44:30.640> uh<00:44:30.800> comprehensive<00:44:31.480> than 00:44:31.670 --> 00:44:31.680 align:start position:0% somewhat more um uh comprehensive than 00:44:31.680 --> 00:44:36.910 align:start position:0% somewhat more um uh comprehensive than that<00:44:32.440> it's<00:44:33.680> um<00:44:34.680> in<00:44:34.839> reality<00:44:35.760> I<00:44:35.880> think<00:44:36.160> we<00:44:36.319> can 00:44:36.910 --> 00:44:36.920 align:start position:0% that it's um in reality I think we can 00:44:36.920 --> 00:44:40.109 align:start position:0% that it's um in reality I think we can understand<00:44:37.119> it<00:44:37.319> as<00:44:37.480> being<00:44:38.400> um<00:44:39.240> a<00:44:39.440> a<00:44:39.680> project 00:44:40.109 --> 00:44:40.119 align:start position:0% understand it as being um a a project 00:44:40.119 --> 00:44:42.150 align:start position:0% understand it as being um a a project that<00:44:40.280> seeks<00:44:40.680> to<00:44:40.960> connect<00:44:41.400> the<00:44:41.559> blockchain<00:44:42.000> to 00:44:42.150 --> 00:44:42.160 align:start position:0% that seeks to connect the blockchain to 00:44:42.160 --> 00:44:43.870 align:start position:0% that seeks to connect the blockchain to the<00:44:42.319> physical<00:44:42.640> world<00:44:42.880> in<00:44:43.040> a<00:44:43.160> very<00:44:43.359> general 00:44:43.870 --> 00:44:43.880 align:start position:0% the physical world in a very general 00:44:43.880 --> 00:44:46.950 align:start position:0% the physical world in a very general sense<00:44:44.880> and<00:44:45.640> this<00:44:45.760> is<00:44:45.960> something<00:44:46.359> that's<00:44:46.839> kind 00:44:46.950 --> 00:44:46.960 align:start position:0% sense and this is something that's kind 00:44:46.960 --> 00:44:48.670 align:start position:0% sense and this is something that's kind of<00:44:47.079> sorely<00:44:47.440> missing<00:44:47.760> at<00:44:47.880> the<00:44:48.000> moment<00:44:48.359> from<00:44:48.559> the 00:44:48.670 --> 00:44:48.680 align:start position:0% of sorely missing at the moment from the 00:44:48.680 --> 00:44:50.470 align:start position:0% of sorely missing at the moment from the frontier<00:44:49.160> chain<00:44:49.440> you<00:44:49.559> know<00:44:49.960> we<00:44:50.119> have<00:44:50.319> the 00:44:50.470 --> 00:44:50.480 align:start position:0% frontier chain you know we have the 00:44:50.480 --> 00:44:52.190 align:start position:0% frontier chain you know we have the technology<00:44:51.079> here<00:44:51.280> we've<00:44:51.480> developed<00:44:51.920> it<00:44:52.040> it's 00:44:52.190 --> 00:44:52.200 align:start position:0% technology here we've developed it it's 00:44:52.200 --> 00:44:53.829 align:start position:0% technology here we've developed it it's out<00:44:52.400> there<00:44:52.559> it's<00:44:52.640> in<00:44:52.760> the<00:44:52.880> wild<00:44:53.119> it's<00:44:53.240> running 00:44:53.829 --> 00:44:53.839 align:start position:0% out there it's in the wild it's running 00:44:53.839 --> 00:44:55.990 align:start position:0% out there it's in the wild it's running but<00:44:54.040> so<00:44:54.280> far<00:44:54.520> there<00:44:54.640> isn't<00:44:55.040> really<00:44:55.400> that<00:44:55.760> that 00:44:55.990 --> 00:44:56.000 align:start position:0% but so far there isn't really that that 00:44:56.000 --> 00:44:58.790 align:start position:0% but so far there isn't really that that physical<00:44:56.440> connection<00:44:57.160> as<00:44:57.319> we<00:44:57.480> see<00:44:58.240> um<00:44:58.440> people 00:44:58.790 --> 00:44:58.800 align:start position:0% physical connection as we see um people 00:44:58.800 --> 00:45:01.870 align:start position:0% physical connection as we see um people bring<00:44:59.680> um<00:45:00.200> real<00:45:00.480> world<00:45:00.800> assets<00:45:01.400> onto<00:45:01.640> the 00:45:01.870 --> 00:45:01.880 align:start position:0% bring um real world assets onto the 00:45:01.880 --> 00:45:04.670 align:start position:0% bring um real world assets onto the blockchain<00:45:02.880> gold<00:45:03.200> storage<00:45:03.599> and<00:45:03.720> so<00:45:03.880> on<00:45:04.440> um 00:45:04.670 --> 00:45:04.680 align:start position:0% blockchain gold storage and so on um 00:45:04.680 --> 00:45:07.109 align:start position:0% blockchain gold storage and so on um this<00:45:05.319> uh<00:45:05.800> this<00:45:05.920> will<00:45:06.040> change<00:45:06.359> things<00:45:06.520> a<00:45:06.680> little 00:45:07.109 --> 00:45:07.119 align:start position:0% this uh this will change things a little 00:45:07.119 --> 00:45:10.549 align:start position:0% this uh this will change things a little but<00:45:07.319> when<00:45:07.480> we<00:45:07.599> see<00:45:08.280> actual<00:45:09.280> real<00:45:09.880> physical 00:45:10.549 --> 00:45:10.559 align:start position:0% but when we see actual real physical 00:45:10.559 --> 00:45:14.430 align:start position:0% but when we see actual real physical areas<00:45:11.160> become<00:45:11.480> unlocked<00:45:12.400> by<00:45:13.200> um<00:45:13.920> you<00:45:14.040> know<00:45:14.240> by 00:45:14.430 --> 00:45:14.440 align:start position:0% areas become unlocked by um you know by 00:45:14.440 --> 00:45:16.470 align:start position:0% areas become unlocked by um you know by sign<00:45:14.720> transactions<00:45:15.640> this<00:45:15.760> is<00:45:15.960> something<00:45:16.359> I 00:45:16.470 --> 00:45:16.480 align:start position:0% sign transactions this is something I 00:45:16.480 --> 00:45:19.150 align:start position:0% sign transactions this is something I think<00:45:16.760> that<00:45:16.920> will<00:45:17.559> really<00:45:18.440> um<00:45:18.760> really<00:45:19.000> get 00:45:19.150 --> 00:45:19.160 align:start position:0% think that will really um really get 00:45:19.160 --> 00:45:21.630 align:start position:0% think that will really um really get Minds<00:45:19.480> racing<00:45:20.400> I<00:45:20.480> mean<00:45:20.760> one<00:45:21.000> can<00:45:21.160> never<00:45:21.440> really 00:45:21.630 --> 00:45:21.640 align:start position:0% Minds racing I mean one can never really 00:45:21.640 --> 00:45:23.109 align:start position:0% Minds racing I mean one can never really say<00:45:21.920> where<00:45:22.079> this<00:45:22.240> stuff's<00:45:22.520> going<00:45:22.640> to<00:45:22.839> go 00:45:23.109 --> 00:45:23.119 align:start position:0% say where this stuff's going to go 00:45:23.119 --> 00:45:25.109 align:start position:0% say where this stuff's going to go because<00:45:23.359> inevitably<00:45:24.280> when<00:45:24.480> new<00:45:24.680> technology 00:45:25.109 --> 00:45:25.119 align:start position:0% because inevitably when new technology 00:45:25.119 --> 00:45:27.030 align:start position:0% because inevitably when new technology comes<00:45:25.319> along<00:45:25.640> we<00:45:25.800> just<00:45:25.920> try<00:45:26.079> and<00:45:26.280> liken<00:45:26.599> it<00:45:26.720> as 00:45:27.030 --> 00:45:27.040 align:start position:0% comes along we just try and liken it as 00:45:27.040 --> 00:45:28.990 align:start position:0% comes along we just try and liken it as much<00:45:27.200> as<00:45:27.359> possible<00:45:27.680> to<00:45:28.000> previous 00:45:28.990 --> 00:45:29.000 align:start position:0% much as possible to previous 00:45:29.000 --> 00:45:31.390 align:start position:0% much as possible to previous technology<00:45:30.000> um<00:45:30.280> we<00:45:30.440> we<00:45:30.559> tend<00:45:30.760> to<00:45:30.960> develop 00:45:31.390 --> 00:45:31.400 align:start position:0% technology um we we tend to develop 00:45:31.400 --> 00:45:32.990 align:start position:0% technology um we we tend to develop things<00:45:31.680> that<00:45:31.839> we<00:45:32.000> we<00:45:32.160> already<00:45:32.440> kind<00:45:32.559> of<00:45:32.680> knew 00:45:32.990 --> 00:45:33.000 align:start position:0% things that we we already kind of knew 00:45:33.000 --> 00:45:34.990 align:start position:0% things that we we already kind of knew could<00:45:33.160> be<00:45:33.319> developed<00:45:33.960> and<00:45:34.040> it<00:45:34.160> takes<00:45:34.359> us<00:45:34.559> a<00:45:34.800> a 00:45:34.990 --> 00:45:35.000 align:start position:0% could be developed and it takes us a a 00:45:35.000 --> 00:45:36.630 align:start position:0% could be developed and it takes us a a good<00:45:35.160> long<00:45:35.400> while<00:45:35.680> before<00:45:35.920> we<00:45:36.319> understand<00:45:36.520> the 00:45:36.630 --> 00:45:36.640 align:start position:0% good long while before we understand the 00:45:36.640 --> 00:45:38.390 align:start position:0% good long while before we understand the true<00:45:36.880> repercussions<00:45:37.520> and<00:45:37.680> the<00:45:38.000> what<00:45:38.160> what 00:45:38.390 --> 00:45:38.400 align:start position:0% true repercussions and the what what 00:45:38.400 --> 00:45:41.430 align:start position:0% true repercussions and the what what real<00:45:39.079> sort<00:45:39.280> of<00:45:39.440> Vistas<00:45:39.839> are<00:45:40.040> opened<00:45:41.040> um<00:45:41.240> so 00:45:41.430 --> 00:45:41.440 align:start position:0% real sort of Vistas are opened um so 00:45:41.440 --> 00:45:42.670 align:start position:0% real sort of Vistas are opened um so that's<00:45:41.599> something<00:45:41.880> I'm<00:45:42.000> looking<00:45:42.240> forward<00:45:42.520> to 00:45:42.670 --> 00:45:42.680 align:start position:0% that's something I'm looking forward to 00:45:42.680 --> 00:45:43.710 align:start position:0% that's something I'm looking forward to but<00:45:42.760> I<00:45:42.839> think<00:45:43.040> it's<00:45:43.160> something<00:45:43.400> that's<00:45:43.559> going 00:45:43.710 --> 00:45:43.720 align:start position:0% but I think it's something that's going 00:45:43.720 --> 00:45:46.430 align:start position:0% but I think it's something that's going to<00:45:43.920> evolve<00:45:44.240> over<00:45:44.400> the<00:45:44.520> next<00:45:44.680> two<00:45:44.839> to<00:45:44.960> three 00:45:46.430 --> 00:45:46.440 align:start position:0% to evolve over the next two to three 00:45:46.440 --> 00:45:50.430 align:start position:0% to evolve over the next two to three years<00:45:47.440> any 00:45:50.430 --> 00:45:50.440 align:start position:0% 00:45:50.440 --> 00:45:52.670 align:start position:0% others<00:45:51.440> no<00:45:51.800> okay<00:45:51.960> well<00:45:52.119> my<00:45:52.240> time's<00:45:52.520> pretty 00:45:52.670 --> 00:45:52.680 align:start position:0% others no okay well my time's pretty 00:45:52.680 --> 00:45:57.080 align:start position:0% others no okay well my time's pretty much<00:45:52.839> up<00:45:53.040> anyway<00:45:53.400> so<00:45:53.720> thank<00:45:53.920> you 00:45:57.080 --> 00:45:57.090 align:start position:0% 00:45:57.090 --> 00:46:00.420 align:start position:0% [Applause] 00:46:00.420 --> 00:46:00.430 align:start position:0% [Applause] 00:46:00.430 --> 00:46:04.310 align:start position:0% [Applause] [Music]