WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:15.070 align:start position:0% [Music] 00:00:15.070 --> 00:00:15.080 align:start position:0% 00:00:15.080 --> 00:00:17.950 align:start position:0% hey<00:00:15.280> everyone<00:00:15.960> um<00:00:16.640> it's<00:00:16.800> going<00:00:16.920> to<00:00:17.039> be<00:00:17.199> a<00:00:17.600> talk 00:00:17.950 --> 00:00:17.960 align:start position:0% hey everyone um it's going to be a talk 00:00:17.960 --> 00:00:21.150 align:start position:0% hey everyone um it's going to be a talk about<00:00:18.880> how<00:00:19.080> we<00:00:19.320> actually<00:00:19.640> can<00:00:19.840> use<00:00:20.160> ethereum 00:00:21.150 --> 00:00:21.160 align:start position:0% about how we actually can use ethereum 00:00:21.160 --> 00:00:23.470 align:start position:0% about how we actually can use ethereum uh<00:00:21.320> to<00:00:21.519> build<00:00:22.240> not<00:00:22.439> just<00:00:22.640> great<00:00:22.960> things<00:00:23.279> but 00:00:23.470 --> 00:00:23.480 align:start position:0% uh to build not just great things but 00:00:23.480 --> 00:00:26.230 align:start position:0% uh to build not just great things but really<00:00:24.320> uh<00:00:24.640> good<00:00:24.840> things<00:00:25.080> for<00:00:25.359> the<00:00:26.080> uh 00:00:26.230 --> 00:00:26.240 align:start position:0% really uh good things for the uh 00:00:26.240 --> 00:00:30.109 align:start position:0% really uh good things for the uh humanity<00:00:27.160> and<00:00:28.160> I<00:00:28.279> have<00:00:28.400> today<00:00:28.800> roughly<00:00:29.359> uh<00:00:29.560> 50 00:00:30.109 --> 00:00:30.119 align:start position:0% humanity and I have today roughly uh 50 00:00:30.119 --> 00:00:32.150 align:start position:0% humanity and I have today roughly uh 50 slides<00:00:30.800> and<00:00:31.080> 20<00:00:31.400> minutes<00:00:31.720> so<00:00:31.840> it's<00:00:31.960> going<00:00:32.040> to 00:00:32.150 --> 00:00:32.160 align:start position:0% slides and 20 minutes so it's going to 00:00:32.160 --> 00:00:35.069 align:start position:0% slides and 20 minutes so it's going to be<00:00:32.320> really<00:00:32.640> fun<00:00:33.640> um<00:00:34.239> so<00:00:34.399> if<00:00:34.520> there's<00:00:34.760> something 00:00:35.069 --> 00:00:35.079 align:start position:0% be really fun um so if there's something 00:00:35.079 --> 00:00:37.950 align:start position:0% be really fun um so if there's something that<00:00:35.200> you<00:00:35.640> like<00:00:36.640> um<00:00:37.120> you<00:00:37.320> have<00:00:37.440> to<00:00:37.559> be<00:00:37.680> very 00:00:37.950 --> 00:00:37.960 align:start position:0% that you like um you have to be very 00:00:37.960 --> 00:00:40.950 align:start position:0% that you like um you have to be very quick<00:00:38.160> to<00:00:38.280> take<00:00:38.399> a<00:00:38.680> picture<00:00:39.680> um<00:00:40.200> and<00:00:40.360> I<00:00:40.480> know 00:00:40.950 --> 00:00:40.960 align:start position:0% quick to take a picture um and I know 00:00:40.960 --> 00:00:44.510 align:start position:0% quick to take a picture um and I know tonight<00:00:41.320> it's<00:00:41.520> going<00:00:41.600> to<00:00:41.719> be<00:00:41.879> raav<00:00:42.879> so<00:00:43.879> um<00:00:44.399> I'm 00:00:44.510 --> 00:00:44.520 align:start position:0% tonight it's going to be raav so um I'm 00:00:44.520 --> 00:00:47.630 align:start position:0% tonight it's going to be raav so um I'm trying<00:00:44.800> to<00:00:45.719> and<00:00:45.960> I'm<00:00:46.199> the<00:00:46.360> last<00:00:47.000> uh<00:00:47.160> speaker 00:00:47.630 --> 00:00:47.640 align:start position:0% trying to and I'm the last uh speaker 00:00:47.640 --> 00:00:50.069 align:start position:0% trying to and I'm the last uh speaker here<00:00:48.079> uh<00:00:48.199> today<00:00:48.520> so<00:00:48.719> I'm<00:00:48.920> trying<00:00:49.160> to<00:00:49.280> be<00:00:49.520> as 00:00:50.069 --> 00:00:50.079 align:start position:0% here uh today so I'm trying to be as 00:00:50.079 --> 00:00:52.910 align:start position:0% here uh today so I'm trying to be as efficient<00:00:50.559> as<00:00:50.840> as<00:00:51.199> possible<00:00:52.199> so<00:00:52.399> you<00:00:52.520> can<00:00:52.640> all 00:00:52.910 --> 00:00:52.920 align:start position:0% efficient as as possible so you can all 00:00:52.920 --> 00:00:56.029 align:start position:0% efficient as as possible so you can all have<00:00:53.399> uh<00:00:53.960> your<00:00:54.120> discone<00:00:54.559> app<00:00:54.840> in<00:00:55.160> later<00:00:55.520> today 00:00:56.029 --> 00:00:56.039 align:start position:0% have uh your discone app in later today 00:00:56.039 --> 00:00:56.869 align:start position:0% have uh your discone app in later today before 00:00:56.869 --> 00:00:56.879 align:start position:0% before 00:00:56.879 --> 00:00:58.509 align:start position:0% before a 00:00:58.509 --> 00:00:58.519 align:start position:0% a 00:00:58.519 --> 00:01:01.270 align:start position:0% a um<00:00:59.519> it's<00:00:59.760> really<00:01:00.120> interesting<00:01:00.480> question<00:01:00.960> is 00:01:01.270 --> 00:01:01.280 align:start position:0% um it's really interesting question is 00:01:01.280 --> 00:01:05.350 align:start position:0% um it's really interesting question is is<00:01:01.840> that<00:01:02.840> what<00:01:03.000> is<00:01:03.120> Force<00:01:03.440> for<00:01:03.680> good<00:01:03.960> so<00:01:04.400> why 00:01:05.350 --> 00:01:05.360 align:start position:0% is that what is Force for good so why 00:01:05.360 --> 00:01:07.590 align:start position:0% is that what is Force for good so why what<00:01:05.519> kind<00:01:05.680> of<00:01:05.920> things<00:01:06.479> create<00:01:07.119> positive 00:01:07.590 --> 00:01:07.600 align:start position:0% what kind of things create positive 00:01:07.600 --> 00:01:10.870 align:start position:0% what kind of things create positive outputs<00:01:08.159> for<00:01:09.159> um<00:01:09.600> for<00:01:09.799> the<00:01:10.000> society<00:01:10.520> for<00:01:10.720> the 00:01:10.870 --> 00:01:10.880 align:start position:0% outputs for um for the society for the 00:01:10.880 --> 00:01:14.350 align:start position:0% outputs for um for the society for the community<00:01:11.400> and<00:01:11.640> and<00:01:11.840> and<00:01:12.040> humanity<00:01:13.159> and<00:01:14.159> I 00:01:14.350 --> 00:01:14.360 align:start position:0% community and and and humanity and I 00:01:14.360 --> 00:01:16.350 align:start position:0% community and and and humanity and I personally<00:01:14.759> been<00:01:14.920> building<00:01:15.479> here<00:01:15.840> uh<00:01:16.080> in<00:01:16.200> the 00:01:16.350 --> 00:01:16.360 align:start position:0% personally been building here uh in the 00:01:16.360 --> 00:01:18.990 align:start position:0% personally been building here uh in the ethereum<00:01:17.240> um<00:01:17.439> Community<00:01:17.880> for<00:01:18.119> the<00:01:18.320> past<00:01:18.799> uh 00:01:18.990 --> 00:01:19.000 align:start position:0% ethereum um Community for the past uh 00:01:19.000 --> 00:01:22.590 align:start position:0% ethereum um Community for the past uh seven<00:01:19.400> years<00:01:20.159> and<00:01:20.320> I<00:01:20.439> started<00:01:21.040> by<00:01:21.439> building<00:01:22.439> uh 00:01:22.590 --> 00:01:22.600 align:start position:0% seven years and I started by building uh 00:01:22.600 --> 00:01:25.270 align:start position:0% seven years and I started by building uh mainly<00:01:23.040> as<00:01:23.159> a<00:01:23.479> hobby<00:01:24.000> and<00:01:24.360> experimentation 00:01:25.270 --> 00:01:25.280 align:start position:0% mainly as a hobby and experimentation 00:01:25.280 --> 00:01:28.990 align:start position:0% mainly as a hobby and experimentation while<00:01:25.640> I<00:01:25.759> was<00:01:25.920> still<00:01:26.280> in<00:01:26.920> in<00:01:27.320> University<00:01:28.320> um<00:01:28.600> in 00:01:28.990 --> 00:01:29.000 align:start position:0% while I was still in in University um in 00:01:29.000 --> 00:01:32.550 align:start position:0% while I was still in in University um in Helsinki<00:01:29.520> Finland<00:01:30.079> when<00:01:30.400> where<00:01:30.680> I'm<00:01:31.000> from<00:01:32.000> um 00:01:32.550 --> 00:01:32.560 align:start position:0% Helsinki Finland when where I'm from um 00:01:32.560 --> 00:01:35.429 align:start position:0% Helsinki Finland when where I'm from um a<00:01:32.759> project<00:01:33.079> that<00:01:33.240> started<00:01:33.640> really<00:01:34.040> just<00:01:34.360> by<00:01:35.240> uh 00:01:35.429 --> 00:01:35.439 align:start position:0% a project that started really just by uh 00:01:35.439 --> 00:01:39.710 align:start position:0% a project that started really just by uh enthusias<00:01:36.399> enthusiasm<00:01:37.399> and<00:01:38.159> became<00:01:39.159> um<00:01:39.560> one 00:01:39.710 --> 00:01:39.720 align:start position:0% enthusias enthusiasm and became um one 00:01:39.720 --> 00:01:43.149 align:start position:0% enthusias enthusiasm and became um one of<00:01:39.840> the<00:01:40.040> biggest<00:01:41.000> um<00:01:41.640> defi<00:01:42.159> protocols<00:01:42.880> uh<00:01:43.000> in 00:01:43.149 --> 00:01:43.159 align:start position:0% of the biggest um defi protocols uh in 00:01:43.159 --> 00:01:45.270 align:start position:0% of the biggest um defi protocols uh in our<00:01:43.399> space<00:01:43.799> and<00:01:44.000> hopefully<00:01:44.560> a<00:01:44.759> technology 00:01:45.270 --> 00:01:45.280 align:start position:0% our space and hopefully a technology 00:01:45.280 --> 00:01:49.030 align:start position:0% our space and hopefully a technology that<00:01:45.439> is<00:01:46.000> going<00:01:46.119> to<00:01:46.240> be<00:01:46.399> used<00:01:46.960> by<00:01:47.960> everyone<00:01:48.840> and 00:01:49.030 --> 00:01:49.040 align:start position:0% that is going to be used by everyone and 00:01:49.040 --> 00:01:50.990 align:start position:0% that is going to be used by everyone and I<00:01:49.320> think<00:01:49.600> the<00:01:49.719> same<00:01:49.960> way<00:01:50.240> across<00:01:50.560> all<00:01:50.759> these 00:01:50.990 --> 00:01:51.000 align:start position:0% I think the same way across all these 00:01:51.000 --> 00:01:52.749 align:start position:0% I think the same way across all these protocols<00:01:51.520> that<00:01:51.640> we're<00:01:52.000> building<00:01:52.399> here 00:01:52.749 --> 00:01:52.759 align:start position:0% protocols that we're building here 00:01:52.759 --> 00:01:56.830 align:start position:0% protocols that we're building here together<00:01:53.640> um<00:01:53.880> now<00:01:54.159> and<00:01:54.280> in<00:01:54.399> the<00:01:54.719> future<00:01:55.719> um<00:01:56.560> and 00:01:56.830 --> 00:01:56.840 align:start position:0% together um now and in the future um and 00:01:56.840 --> 00:01:59.109 align:start position:0% together um now and in the future um and ethereum<00:01:57.439> is<00:01:57.920> fascinating<00:01:58.560> because<00:01:58.799> it's<00:01:58.920> a 00:01:59.109 --> 00:01:59.119 align:start position:0% ethereum is fascinating because it's a 00:01:59.119 --> 00:02:01.310 align:start position:0% ethereum is fascinating because it's a really<00:01:59.360> open<00:01:59.600> design<00:01:59.920> science<00:02:00.200> bace<00:02:00.560> so<00:02:01.200> you 00:02:01.310 --> 00:02:01.320 align:start position:0% really open design science bace so you 00:02:01.320 --> 00:02:05.469 align:start position:0% really open design science bace so you can<00:02:01.600> really<00:02:02.360> build<00:02:02.759> anything<00:02:03.920> um<00:02:04.920> but<00:02:05.079> the<00:02:05.240> key 00:02:05.469 --> 00:02:05.479 align:start position:0% can really build anything um but the key 00:02:05.479 --> 00:02:07.870 align:start position:0% can really build anything um but the key ingredients<00:02:06.039> is<00:02:06.240> that<00:02:06.719> how<00:02:06.960> you<00:02:07.240> put<00:02:07.479> things 00:02:07.870 --> 00:02:07.880 align:start position:0% ingredients is that how you put things 00:02:07.880 --> 00:02:10.109 align:start position:0% ingredients is that how you put things together<00:02:08.239> in<00:02:08.319> a<00:02:08.520> way<00:02:08.800> that<00:02:09.200> it<00:02:09.399> creates<00:02:10.000> the 00:02:10.109 --> 00:02:10.119 align:start position:0% together in a way that it creates the 00:02:10.119 --> 00:02:13.990 align:start position:0% together in a way that it creates the output<00:02:10.560> that<00:02:10.640> is<00:02:11.120> beneficial<00:02:12.120> uh<00:02:12.239> for 00:02:13.990 --> 00:02:14.000 align:start position:0% output that is beneficial uh for 00:02:14.000 --> 00:02:16.750 align:start position:0% output that is beneficial uh for everyone<00:02:15.000> in<00:02:15.160> overall<00:02:15.519> when<00:02:15.599> you<00:02:15.720> think<00:02:16.000> about 00:02:16.750 --> 00:02:16.760 align:start position:0% everyone in overall when you think about 00:02:16.760 --> 00:02:19.630 align:start position:0% everyone in overall when you think about um<00:02:17.360> technology<00:02:18.360> um<00:02:18.720> and<00:02:18.959> and<00:02:19.040> the<00:02:19.160> purpose<00:02:19.480> of 00:02:19.630 --> 00:02:19.640 align:start position:0% um technology um and and the purpose of 00:02:19.640 --> 00:02:22.430 align:start position:0% um technology um and and the purpose of technology<00:02:20.239> and<00:02:20.400> what<00:02:20.519> it<00:02:20.760> really<00:02:21.599> uh<00:02:21.720> helps 00:02:22.430 --> 00:02:22.440 align:start position:0% technology and what it really uh helps 00:02:22.440 --> 00:02:25.270 align:start position:0% technology and what it really uh helps um<00:02:22.680> it's<00:02:22.879> about<00:02:23.280> actually<00:02:24.280> lifting<00:02:24.840> the<00:02:25.120> the 00:02:25.270 --> 00:02:25.280 align:start position:0% um it's about actually lifting the the 00:02:25.280 --> 00:02:28.470 align:start position:0% um it's about actually lifting the the standards<00:02:25.800> of<00:02:26.040> of<00:02:26.200> of<00:02:26.360> living<00:02:27.360> um<00:02:28.120> in<00:02:28.239> our 00:02:28.470 --> 00:02:28.480 align:start position:0% standards of of of living um in our 00:02:28.480 --> 00:02:30.790 align:start position:0% standards of of of living um in our communities<00:02:29.160> and<00:02:29.400> and<00:02:29.599> in<00:02:29.920> in<00:02:30.080> wider<00:02:30.640> uh 00:02:30.790 --> 00:02:30.800 align:start position:0% communities and and in in wider uh 00:02:30.800 --> 00:02:33.509 align:start position:0% communities and and in in wider uh Society<00:02:31.440> so<00:02:32.080> when<00:02:32.239> we<00:02:32.400> go<00:02:32.599> back<00:02:32.760> in<00:02:33.040> history 00:02:33.509 --> 00:02:33.519 align:start position:0% Society so when we go back in history 00:02:33.519 --> 00:02:36.270 align:start position:0% Society so when we go back in history and<00:02:34.200> look<00:02:34.440> at<00:02:35.000> all<00:02:35.239> these<00:02:35.680> technological 00:02:36.270 --> 00:02:36.280 align:start position:0% and look at all these technological 00:02:36.280 --> 00:02:39.750 align:start position:0% and look at all these technological innovations<00:02:36.840> that<00:02:37.040> we've<00:02:37.319> we've<00:02:37.680> seen<00:02:38.680> um<00:02:39.519> and 00:02:39.750 --> 00:02:39.760 align:start position:0% innovations that we've we've seen um and 00:02:39.760 --> 00:02:42.350 align:start position:0% innovations that we've we've seen um and and<00:02:39.959> they<00:02:40.280> typically<00:02:40.760> tend<00:02:41.000> to<00:02:41.400> compound<00:02:41.959> so 00:02:42.350 --> 00:02:42.360 align:start position:0% and they typically tend to compound so 00:02:42.360 --> 00:02:46.630 align:start position:0% and they typically tend to compound so let's<00:02:42.560> say<00:02:43.519> um<00:02:44.120> there's<00:02:44.440> innovation<00:02:45.120> in<00:02:45.760> um 00:02:46.630 --> 00:02:46.640 align:start position:0% let's say um there's innovation in um 00:02:46.640 --> 00:02:49.470 align:start position:0% let's say um there's innovation in um Electronics<00:02:47.640> um<00:02:48.159> that<00:02:48.400> compounds<00:02:49.200> different 00:02:49.470 --> 00:02:49.480 align:start position:0% Electronics um that compounds different 00:02:49.480 --> 00:02:51.430 align:start position:0% Electronics um that compounds different types<00:02:49.680> of<00:02:49.959> uh<00:02:50.159> new<00:02:50.319> innovation<00:02:50.760> if<00:02:50.920> there's 00:02:51.430 --> 00:02:51.440 align:start position:0% types of uh new innovation if there's 00:02:51.440 --> 00:02:54.509 align:start position:0% types of uh new innovation if there's Innovation<00:02:52.440> that<00:02:52.599> enables<00:02:53.080> the<00:02:53.400> internet<00:02:54.400> uh 00:02:54.509 --> 00:02:54.519 align:start position:0% Innovation that enables the internet uh 00:02:54.519 --> 00:02:56.350 align:start position:0% Innovation that enables the internet uh you<00:02:54.680> have<00:02:54.920> applications<00:02:55.840> and<00:02:56.000> you<00:02:56.120> have 00:02:56.350 --> 00:02:56.360 align:start position:0% you have applications and you have 00:02:56.360 --> 00:02:58.670 align:start position:0% you have applications and you have access<00:02:56.879> and<00:02:57.040> and<00:02:57.200> that's<00:02:57.440> a<00:02:57.840> compounding<00:02:58.560> uh 00:02:58.670 --> 00:02:58.680 align:start position:0% access and and that's a compounding uh 00:02:58.680 --> 00:03:01.750 align:start position:0% access and and that's a compounding uh innovation 00:03:01.750 --> 00:03:01.760 align:start position:0% 00:03:01.760 --> 00:03:05.190 align:start position:0% but<00:03:02.000> also<00:03:02.879> in<00:03:03.799> the<00:03:03.920> flip<00:03:04.319> side<00:03:04.480> of<00:03:04.560> the<00:03:04.680> coin<00:03:05.000> is 00:03:05.190 --> 00:03:05.200 align:start position:0% but also in the flip side of the coin is 00:03:05.200 --> 00:03:08.070 align:start position:0% but also in the flip side of the coin is that<00:03:05.680> technology<00:03:06.159> can<00:03:06.400> also<00:03:07.200> uh<00:03:07.440> do<00:03:07.680> a<00:03:07.799> lot<00:03:07.920> of 00:03:08.070 --> 00:03:08.080 align:start position:0% that technology can also uh do a lot of 00:03:08.080 --> 00:03:11.830 align:start position:0% that technology can also uh do a lot of harm<00:03:08.480> if<00:03:08.640> it's<00:03:08.879> designed<00:03:09.319> in<00:03:09.400> a<00:03:10.000> wrong<00:03:10.319> way<00:03:11.319> um 00:03:11.830 --> 00:03:11.840 align:start position:0% harm if it's designed in a wrong way um 00:03:11.840 --> 00:03:15.070 align:start position:0% harm if it's designed in a wrong way um or<00:03:12.360> without<00:03:12.680> the<00:03:12.840> certain<00:03:13.159> values<00:03:13.599> as<00:03:13.760> well<00:03:14.080> so 00:03:15.070 --> 00:03:15.080 align:start position:0% or without the certain values as well so 00:03:15.080 --> 00:03:17.910 align:start position:0% or without the certain values as well so um<00:03:15.360> technology<00:03:15.879> can<00:03:16.080> actually<00:03:16.400> also<00:03:16.920> create 00:03:17.910 --> 00:03:17.920 align:start position:0% um technology can actually also create 00:03:17.920 --> 00:03:21.110 align:start position:0% um technology can actually also create um<00:03:18.080> unequal<00:03:18.640> access<00:03:19.319> information<00:03:20.120> asymmetry 00:03:21.110 --> 00:03:21.120 align:start position:0% um unequal access information asymmetry 00:03:21.120 --> 00:03:24.030 align:start position:0% um unequal access information asymmetry um<00:03:21.799> the<00:03:21.920> more<00:03:22.120> you<00:03:22.319> actually<00:03:22.519> know<00:03:22.840> the<00:03:23.040> better 00:03:24.030 --> 00:03:24.040 align:start position:0% um the more you actually know the better 00:03:24.040 --> 00:03:25.789 align:start position:0% um the more you actually know the better um<00:03:24.560> execution<00:03:25.159> and<00:03:25.319> the<00:03:25.480> better 00:03:25.789 --> 00:03:25.799 align:start position:0% um execution and the better 00:03:25.799 --> 00:03:28.470 align:start position:0% um execution and the better opportunities<00:03:26.360> you<00:03:26.480> can<00:03:27.040> you<00:03:27.159> can<00:03:27.480> have<00:03:28.319> it 00:03:28.470 --> 00:03:28.480 align:start position:0% opportunities you can you can have it 00:03:28.480 --> 00:03:31.630 align:start position:0% opportunities you can you can have it can<00:03:28.640> create<00:03:29.400> uh<00:03:29.840> worker<00:03:30.360> displacements<00:03:31.360> uh 00:03:31.630 --> 00:03:31.640 align:start position:0% can create uh worker displacements uh 00:03:31.640 --> 00:03:35.750 align:start position:0% can create uh worker displacements uh pollution<00:03:32.640> um<00:03:33.400> and<00:03:33.840> increase<00:03:34.360> the<00:03:34.799> climate<00:03:35.599> uh 00:03:35.750 --> 00:03:35.760 align:start position:0% pollution um and increase the climate uh 00:03:35.760 --> 00:03:39.309 align:start position:0% pollution um and increase the climate uh change<00:03:36.720> so<00:03:37.000> technology<00:03:37.480> always<00:03:38.400> um<00:03:38.720> is<00:03:38.959> really 00:03:39.309 --> 00:03:39.319 align:start position:0% change so technology always um is really 00:03:39.319 --> 00:03:41.550 align:start position:0% change so technology always um is really neutral<00:03:39.720> to<00:03:39.879> the<00:03:40.040> outputs<00:03:40.640> and<00:03:40.760> it's<00:03:40.920> up<00:03:41.120> to 00:03:41.550 --> 00:03:41.560 align:start position:0% neutral to the outputs and it's up to 00:03:41.560 --> 00:03:44.750 align:start position:0% neutral to the outputs and it's up to really<00:03:42.280> the<00:03:42.439> people<00:03:42.840> behind<00:03:43.640> uh<00:03:44.480> that<00:03:44.599> are 00:03:44.750 --> 00:03:44.760 align:start position:0% really the people behind uh that are 00:03:44.760 --> 00:03:46.830 align:start position:0% really the people behind uh that are building<00:03:45.080> the<00:03:45.239> technology<00:03:45.640> to<00:03:45.879> decide<00:03:46.560> what's 00:03:46.830 --> 00:03:46.840 align:start position:0% building the technology to decide what's 00:03:46.840 --> 00:03:49.869 align:start position:0% building the technology to decide what's the<00:03:47.000> outputs<00:03:47.560> are<00:03:47.720> going<00:03:47.799> to 00:03:49.869 --> 00:03:49.879 align:start position:0% the outputs are going to 00:03:49.879 --> 00:03:53.390 align:start position:0% the outputs are going to be<00:03:50.879> so<00:03:51.480> these<00:03:51.680> interest<00:03:52.120> Technologies<00:03:52.760> are 00:03:53.390 --> 00:03:53.400 align:start position:0% be so these interest Technologies are 00:03:53.400 --> 00:03:55.589 align:start position:0% be so these interest Technologies are built<00:03:53.959> in<00:03:54.040> a<00:03:54.239> way<00:03:54.439> that<00:03:54.760> they're<00:03:55.079> accessible 00:03:55.589 --> 00:03:55.599 align:start position:0% built in a way that they're accessible 00:03:55.599 --> 00:03:58.990 align:start position:0% built in a way that they're accessible and<00:03:55.840> open<00:03:56.760> and<00:03:57.680> a<00:03:57.840> big<00:03:58.079> question<00:03:58.480> remains<00:03:58.799> is 00:03:58.990 --> 00:03:59.000 align:start position:0% and open and a big question remains is 00:03:59.000 --> 00:04:02.110 align:start position:0% and open and a big question remains is that<00:03:59.560> can<00:03:59.920> these<00:04:00.280> Technologies<00:04:00.920> be<00:04:01.799> uh<00:04:01.959> a 00:04:02.110 --> 00:04:02.120 align:start position:0% that can these Technologies be uh a 00:04:02.120 --> 00:04:04.990 align:start position:0% that can these Technologies be uh a force<00:04:02.400> of<00:04:02.640> good<00:04:03.079> that<00:04:03.319> actually<00:04:03.680> can<00:04:04.560> uh<00:04:04.720> lift 00:04:04.990 --> 00:04:05.000 align:start position:0% force of good that actually can uh lift 00:04:05.000 --> 00:04:07.830 align:start position:0% force of good that actually can uh lift up<00:04:05.280> the<00:04:05.720> the<00:04:05.920> society<00:04:06.400> and<00:04:06.640> and 00:04:07.830 --> 00:04:07.840 align:start position:0% up the the society and and 00:04:07.840 --> 00:04:09.750 align:start position:0% up the the society and and Humanity 00:04:09.750 --> 00:04:09.760 align:start position:0% Humanity 00:04:09.760 --> 00:04:12.750 align:start position:0% Humanity um<00:04:10.760> I<00:04:10.879> believe<00:04:11.159> that<00:04:11.360> ethereum<00:04:11.879> is<00:04:12.120> is<00:04:12.280> is<00:04:12.400> a 00:04:12.750 --> 00:04:12.760 align:start position:0% um I believe that ethereum is is is a 00:04:12.760 --> 00:04:16.590 align:start position:0% um I believe that ethereum is is is a really<00:04:13.840> powerful<00:04:14.840> uh<00:04:15.040> set<00:04:15.280> of 00:04:16.590 --> 00:04:16.600 align:start position:0% really powerful uh set of 00:04:16.600 --> 00:04:20.110 align:start position:0% really powerful uh set of Technology<00:04:17.600> especially<00:04:18.199> because<00:04:19.199> not<00:04:19.560> purely 00:04:20.110 --> 00:04:20.120 align:start position:0% Technology especially because not purely 00:04:20.120 --> 00:04:22.550 align:start position:0% Technology especially because not purely from<00:04:20.400> the<00:04:20.959> technical<00:04:21.479> perspective<00:04:22.000> but<00:04:22.199> also 00:04:22.550 --> 00:04:22.560 align:start position:0% from the technical perspective but also 00:04:22.560 --> 00:04:24.790 align:start position:0% from the technical perspective but also the<00:04:22.759> choices<00:04:23.160> we<00:04:23.320> have<00:04:23.479> made<00:04:24.080> um<00:04:24.280> as<00:04:24.400> a 00:04:24.790 --> 00:04:24.800 align:start position:0% the choices we have made um as a 00:04:24.800 --> 00:04:27.430 align:start position:0% the choices we have made um as a community<00:04:25.800> being<00:04:26.080> able<00:04:26.280> to<00:04:26.479> build<00:04:26.840> on<00:04:27.120> open 00:04:27.430 --> 00:04:27.440 align:start position:0% community being able to build on open 00:04:27.440 --> 00:04:30.270 align:start position:0% community being able to build on open sour<00:04:28.000> Source<00:04:28.360> stock<00:04:29.240> ensures 00:04:30.270 --> 00:04:30.280 align:start position:0% sour Source stock ensures 00:04:30.280 --> 00:04:33.510 align:start position:0% sour Source stock ensures accessibility<00:04:31.280> open<00:04:32.120> contributions<00:04:33.120> um<00:04:33.320> and 00:04:33.510 --> 00:04:33.520 align:start position:0% accessibility open contributions um and 00:04:33.520 --> 00:04:35.430 align:start position:0% accessibility open contributions um and actually<00:04:33.960> access<00:04:34.320> to<00:04:34.639> to<00:04:34.800> building<00:04:35.240> these 00:04:35.430 --> 00:04:35.440 align:start position:0% actually access to to building these 00:04:35.440 --> 00:04:38.230 align:start position:0% actually access to to building these protocols<00:04:35.960> and<00:04:36.120> and<00:04:36.280> networks<00:04:36.720> in<00:04:36.919> in<00:04:37.000> a<00:04:37.240> way 00:04:38.230 --> 00:04:38.240 align:start position:0% protocols and and networks in in a way 00:04:38.240 --> 00:04:41.110 align:start position:0% protocols and and networks in in a way um<00:04:39.080> uh<00:04:39.160> for<00:04:39.360> ourselves<00:04:40.240> uh<00:04:40.360> to<00:04:40.520> live<00:04:40.800> in<00:04:41.000> in 00:04:41.110 --> 00:04:41.120 align:start position:0% um uh for ourselves uh to live in in 00:04:41.120 --> 00:04:43.350 align:start position:0% um uh for ourselves uh to live in in that<00:04:41.320> future<00:04:42.160> um<00:04:42.639> as 00:04:43.350 --> 00:04:43.360 align:start position:0% that future um as 00:04:43.360 --> 00:04:46.270 align:start position:0% that future um as well<00:04:44.360> and<00:04:44.960> the<00:04:45.120> very<00:04:45.320> interesting<00:04:45.800> idea<00:04:46.080> about 00:04:46.270 --> 00:04:46.280 align:start position:0% well and the very interesting idea about 00:04:46.280 --> 00:04:49.270 align:start position:0% well and the very interesting idea about decentralization<00:04:47.280> is<00:04:47.520> that<00:04:48.280> it<00:04:48.520> really 00:04:49.270 --> 00:04:49.280 align:start position:0% decentralization is that it really 00:04:49.280 --> 00:04:52.909 align:start position:0% decentralization is that it really removes<00:04:50.280> the<00:04:50.600> central<00:04:51.039> point<00:04:51.240> of<00:04:51.400> failure<00:04:52.120> or 00:04:52.909 --> 00:04:52.919 align:start position:0% removes the central point of failure or 00:04:52.919 --> 00:04:55.909 align:start position:0% removes the central point of failure or um<00:04:53.160> gatekeeping<00:04:53.919> that<00:04:54.240> we've<00:04:54.440> been<00:04:54.919> trusting 00:04:55.909 --> 00:04:55.919 align:start position:0% um gatekeeping that we've been trusting 00:04:55.919 --> 00:05:01.990 align:start position:0% um gatekeeping that we've been trusting uh<00:04:56.039> in<00:04:56.280> society<00:04:56.759> for<00:04:57.080> for<00:04:57.639> centuries<00:04:58.639> um<00:04:58.960> now 00:05:01.990 --> 00:05:02.000 align:start position:0% 00:05:02.000 --> 00:05:03.150 align:start position:0% so<00:05:02.240> this<00:05:02.360> is<00:05:02.479> something<00:05:02.759> interesting 00:05:03.150 --> 00:05:03.160 align:start position:0% so this is something interesting 00:05:03.160 --> 00:05:05.710 align:start position:0% so this is something interesting obviously<00:05:03.919> the<00:05:04.039> internet<00:05:04.479> itself<00:05:04.840> has<00:05:05.000> been 00:05:05.710 --> 00:05:05.720 align:start position:0% obviously the internet itself has been 00:05:05.720 --> 00:05:09.110 align:start position:0% obviously the internet itself has been built<00:05:06.759> um<00:05:07.759> by<00:05:07.919> relying<00:05:08.280> on<00:05:08.440> decentralized 00:05:09.110 --> 00:05:09.120 align:start position:0% built um by relying on decentralized 00:05:09.120 --> 00:05:12.749 align:start position:0% built um by relying on decentralized Technologies<00:05:09.720> so<00:05:10.120> we<00:05:10.320> have<00:05:11.039> IP<00:05:11.440> protocol 00:05:12.749 --> 00:05:12.759 align:start position:0% Technologies so we have IP protocol 00:05:12.759 --> 00:05:15.830 align:start position:0% Technologies so we have IP protocol HTTP<00:05:13.759> um<00:05:14.320> different<00:05:14.600> email<00:05:15.000> protocols<00:05:15.520> and 00:05:15.830 --> 00:05:15.840 align:start position:0% HTTP um different email protocols and 00:05:15.840 --> 00:05:19.270 align:start position:0% HTTP um different email protocols and and<00:05:16.000> then<00:05:16.320> the<00:05:16.479> ethernet<00:05:17.280> uh<00:05:17.560> protocol<00:05:18.560> um<00:05:19.080> so 00:05:19.270 --> 00:05:19.280 align:start position:0% and then the ethernet uh protocol um so 00:05:19.280 --> 00:05:20.990 align:start position:0% and then the ethernet uh protocol um so the<00:05:19.440> actual<00:05:19.759> internet<00:05:20.199> itself<00:05:20.639> has<00:05:20.759> been 00:05:20.990 --> 00:05:21.000 align:start position:0% the actual internet itself has been 00:05:21.000 --> 00:05:24.510 align:start position:0% the actual internet itself has been built<00:05:21.520> in<00:05:21.960> in<00:05:22.080> a<00:05:22.520> decent<00:05:23.000> just<00:05:23.280> way<00:05:23.960> but<00:05:24.160> over 00:05:24.510 --> 00:05:24.520 align:start position:0% built in in a decent just way but over 00:05:24.520 --> 00:05:28.430 align:start position:0% built in in a decent just way but over time<00:05:25.319> um<00:05:25.960> became<00:05:26.240> more<00:05:26.440> centralized<00:05:27.160> and<00:05:28.160> open 00:05:28.430 --> 00:05:28.440 align:start position:0% time um became more centralized and open 00:05:28.440 --> 00:05:30.189 align:start position:0% time um became more centralized and open internet<00:05:28.880> has<00:05:29.000> fostered<00:05:29.759> a<00:05:29.880> lot<00:05:30.000> of 00:05:30.189 --> 00:05:30.199 align:start position:0% internet has fostered a lot of 00:05:30.199 --> 00:05:32.469 align:start position:0% internet has fostered a lot of Innovations<00:05:31.199> uh<00:05:31.360> over<00:05:31.600> the<00:05:31.759> years<00:05:32.160> and<00:05:32.319> that 00:05:32.469 --> 00:05:32.479 align:start position:0% Innovations uh over the years and that 00:05:32.479 --> 00:05:35.150 align:start position:0% Innovations uh over the years and that Innovation<00:05:32.960> is<00:05:33.160> just<00:05:33.680> accelerating<00:05:34.680> uh<00:05:34.840> over 00:05:35.150 --> 00:05:35.160 align:start position:0% Innovation is just accelerating uh over 00:05:35.160 --> 00:05:38.469 align:start position:0% Innovation is just accelerating uh over time<00:05:35.960> and<00:05:36.120> this<00:05:36.600> centralization<00:05:37.600> um<00:05:38.039> started 00:05:38.469 --> 00:05:38.479 align:start position:0% time and this centralization um started 00:05:38.479 --> 00:05:41.909 align:start position:0% time and this centralization um started more<00:05:39.199> recently<00:05:40.039> and<00:05:40.280> and<00:05:40.440> I<00:05:40.520> would<00:05:40.720> say<00:05:41.400> more 00:05:41.909 --> 00:05:41.919 align:start position:0% more recently and and I would say more 00:05:41.919 --> 00:05:46.110 align:start position:0% more recently and and I would say more two<00:05:42.199> decades<00:05:42.880> uh<00:05:43.000> for<00:05:43.440> now<00:05:44.720> um<00:05:45.720> even<00:05:45.960> though 00:05:46.110 --> 00:05:46.120 align:start position:0% two decades uh for now um even though 00:05:46.120 --> 00:05:48.430 align:start position:0% two decades uh for now um even though the<00:05:46.280> actual<00:05:46.919> original<00:05:47.440> architecture<00:05:48.039> was<00:05:48.280> was 00:05:48.430 --> 00:05:48.440 align:start position:0% the actual original architecture was was 00:05:48.440 --> 00:05:51.150 align:start position:0% the actual original architecture was was more<00:05:48.759> decentralized<00:05:49.600> and<00:05:50.280> and<00:05:50.479> I<00:05:50.560> think<00:05:50.840> what 00:05:51.150 --> 00:05:51.160 align:start position:0% more decentralized and and I think what 00:05:51.160 --> 00:05:55.029 align:start position:0% more decentralized and and I think what happened<00:05:51.560> here<00:05:51.759> is<00:05:52.000> that<00:05:52.840> humans<00:05:53.840> um<00:05:54.479> and<00:05:54.840> and 00:05:55.029 --> 00:05:55.039 align:start position:0% happened here is that humans um and and 00:05:55.039 --> 00:05:58.029 align:start position:0% happened here is that humans um and and people<00:05:55.400> who<00:05:56.240> were<00:05:56.720> using<00:05:57.199> the<00:05:57.360> internet 00:05:58.029 --> 00:05:58.039 align:start position:0% people who were using the internet 00:05:58.039 --> 00:06:01.029 align:start position:0% people who were using the internet wanted<00:05:58.400> more<00:05:58.680> accessibility<00:06:00.080> wanted 00:06:01.029 --> 00:06:01.039 align:start position:0% wanted more accessibility wanted 00:06:01.039 --> 00:06:03.670 align:start position:0% wanted more accessibility wanted everything<00:06:01.520> at<00:06:01.639> the<00:06:01.759> same<00:06:02.080> time<00:06:02.840> it's<00:06:03.000> an<00:06:03.199> open 00:06:03.670 --> 00:06:03.680 align:start position:0% everything at the same time it's an open 00:06:03.680 --> 00:06:05.550 align:start position:0% everything at the same time it's an open environment<00:06:04.160> to<00:06:04.360> build<00:06:04.880> but<00:06:05.039> at<00:06:05.120> the<00:06:05.280> same 00:06:05.550 --> 00:06:05.560 align:start position:0% environment to build but at the same 00:06:05.560 --> 00:06:10.270 align:start position:0% environment to build but at the same time<00:06:06.319> we<00:06:06.599> sacrificed<00:06:07.599> uh<00:06:07.800> ownership<00:06:08.520> over<00:06:09.520> um 00:06:10.270 --> 00:06:10.280 align:start position:0% time we sacrificed uh ownership over um 00:06:10.280 --> 00:06:14.270 align:start position:0% time we sacrificed uh ownership over um or<00:06:10.479> use<00:06:10.800> experience<00:06:11.319> over<00:06:11.680> over 00:06:14.270 --> 00:06:14.280 align:start position:0% 00:06:14.280 --> 00:06:18.189 align:start position:0% ownership<00:06:15.280> and<00:06:15.440> I<00:06:15.639> think<00:06:16.520> truly<00:06:17.080> after<00:06:18.080> a 00:06:18.189 --> 00:06:18.199 align:start position:0% ownership and I think truly after a 00:06:18.199 --> 00:06:20.670 align:start position:0% ownership and I think truly after a couple<00:06:18.440> of<00:06:18.599> decades<00:06:19.560> actually<00:06:19.919> living 00:06:20.670 --> 00:06:20.680 align:start position:0% couple of decades actually living 00:06:20.680 --> 00:06:21.870 align:start position:0% couple of decades actually living building<00:06:21.120> on 00:06:21.870 --> 00:06:21.880 align:start position:0% building on 00:06:21.880 --> 00:06:25.510 align:start position:0% building on online<00:06:22.880> um<00:06:23.720> we<00:06:23.919> started<00:06:24.280> to 00:06:25.510 --> 00:06:25.520 align:start position:0% online um we started to 00:06:25.520 --> 00:06:27.950 align:start position:0% online um we started to effectively<00:06:26.520> gravitate<00:06:27.080> towards<00:06:27.680> these 00:06:27.950 --> 00:06:27.960 align:start position:0% effectively gravitate towards these 00:06:27.960 --> 00:06:29.710 align:start position:0% effectively gravitate towards these interest<00:06:28.360> Technologies<00:06:29.360> like<00:06:29.639> the 00:06:29.710 --> 00:06:29.720 align:start position:0% interest Technologies like the 00:06:29.720 --> 00:06:32.270 align:start position:0% interest Technologies like the blockchain<00:06:30.199> and<00:06:30.400> and<00:06:30.759> ethereum 00:06:32.270 --> 00:06:32.280 align:start position:0% blockchain and and ethereum 00:06:32.280 --> 00:06:34.830 align:start position:0% blockchain and and ethereum specifically<00:06:33.280> because<00:06:33.759> that<00:06:33.960> can<00:06:34.240> actually 00:06:34.830 --> 00:06:34.840 align:start position:0% specifically because that can actually 00:06:34.840 --> 00:06:37.430 align:start position:0% specifically because that can actually be<00:06:35.000> a<00:06:35.160> game<00:06:35.400> changer<00:06:36.039> you<00:06:36.160> can<00:06:36.360> bring<00:06:36.720> a<00:06:36.840> lot<00:06:37.000> of 00:06:37.430 --> 00:06:37.440 align:start position:0% be a game changer you can bring a lot of 00:06:37.440 --> 00:06:40.710 align:start position:0% be a game changer you can bring a lot of those<00:06:38.440> that<00:06:39.160> decentralization<00:06:40.160> uh<00:06:40.319> into<00:06:40.560> your 00:06:40.710 --> 00:06:40.720 align:start position:0% those that decentralization uh into your 00:06:40.720 --> 00:06:43.189 align:start position:0% those that decentralization uh into your application<00:06:41.240> Level<00:06:42.039> and<00:06:42.360> bring<00:06:42.720> open 00:06:43.189 --> 00:06:43.199 align:start position:0% application Level and bring open 00:06:43.199 --> 00:06:45.990 align:start position:0% application Level and bring open protocols<00:06:44.199> uh<00:06:44.319> into<00:06:44.599> the<00:06:44.840> everyday<00:06:45.800> uh 00:06:45.990 --> 00:06:46.000 align:start position:0% protocols uh into the everyday uh 00:06:46.000 --> 00:06:48.909 align:start position:0% protocols uh into the everyday uh application 00:06:48.909 --> 00:06:48.919 align:start position:0% 00:06:48.919 --> 00:06:50.749 align:start position:0% interfaces 00:06:50.749 --> 00:06:50.759 align:start position:0% interfaces 00:06:50.759 --> 00:06:54.749 align:start position:0% interfaces um<00:06:51.759> and<00:06:52.520> really<00:06:52.800> main<00:06:53.039> thing<00:06:53.280> about<00:06:54.199> the 00:06:54.749 --> 00:06:54.759 align:start position:0% um and really main thing about the 00:06:54.759 --> 00:06:58.309 align:start position:0% um and really main thing about the safeguards<00:06:55.520> is<00:06:56.319> is<00:06:56.800> that<00:06:57.800> what<00:06:57.960> we<00:06:58.080> can 00:06:58.309 --> 00:06:58.319 align:start position:0% safeguards is is that what we can 00:06:58.319 --> 00:07:02.390 align:start position:0% safeguards is is that what we can provide<00:06:59.120> is<00:06:59.599> is<00:06:59.840> effectively<00:07:00.800> rules<00:07:01.800> over 00:07:02.390 --> 00:07:02.400 align:start position:0% provide is is effectively rules over 00:07:02.400 --> 00:07:05.830 align:start position:0% provide is is effectively rules over data<00:07:02.759> ownership<00:07:03.759> data<00:07:04.000> sharing<00:07:04.840> neutrality 00:07:05.830 --> 00:07:05.840 align:start position:0% data ownership data sharing neutrality 00:07:05.840 --> 00:07:08.909 align:start position:0% data ownership data sharing neutrality openness<00:07:06.560> and<00:07:06.720> and<00:07:06.960> security<00:07:07.840> and<00:07:08.039> security 00:07:08.909 --> 00:07:08.919 align:start position:0% openness and and security and security 00:07:08.919 --> 00:07:11.790 align:start position:0% openness and and security and security here<00:07:09.919> uh<00:07:10.080> effectively<00:07:10.599> means<00:07:11.080> the<00:07:11.240> security 00:07:11.790 --> 00:07:11.800 align:start position:0% here uh effectively means the security 00:07:11.800 --> 00:07:14.270 align:start position:0% here uh effectively means the security that<00:07:12.319> the<00:07:12.800> the<00:07:12.960> ethereum<00:07:13.599> as<00:07:13.720> a<00:07:13.840> network 00:07:14.270 --> 00:07:14.280 align:start position:0% that the the ethereum as a network 00:07:14.280 --> 00:07:16.350 align:start position:0% that the the ethereum as a network provides<00:07:15.240> for<00:07:15.599> different<00:07:15.919> types<00:07:16.120> of 00:07:16.350 --> 00:07:16.360 align:start position:0% provides for different types of 00:07:16.360 --> 00:07:20.550 align:start position:0% provides for different types of applications<00:07:17.000> that<00:07:17.520> have<00:07:17.840> really<00:07:18.680> core<00:07:19.680> um 00:07:20.550 --> 00:07:20.560 align:start position:0% applications that have really core um 00:07:20.560 --> 00:07:22.670 align:start position:0% applications that have really core um functionality<00:07:21.319> whether<00:07:21.520> it's<00:07:21.840> Finance<00:07:22.360> or 00:07:22.670 --> 00:07:22.680 align:start position:0% functionality whether it's Finance or 00:07:22.680 --> 00:07:26.029 align:start position:0% functionality whether it's Finance or other<00:07:22.960> types<00:07:23.199> of<00:07:23.479> uh<00:07:24.160> use<00:07:24.520> cases<00:07:24.960> and<00:07:25.560> ethereum 00:07:26.029 --> 00:07:26.039 align:start position:0% other types of uh use cases and ethereum 00:07:26.039 --> 00:07:29.909 align:start position:0% other types of uh use cases and ethereum by<00:07:26.199> itself<00:07:27.160> uh<00:07:27.400> by<00:07:27.560> its<00:07:27.759> design<00:07:28.199> is<00:07:28.680> censorship 00:07:29.909 --> 00:07:29.919 align:start position:0% by itself uh by its design is censorship 00:07:29.919 --> 00:07:32.670 align:start position:0% by itself uh by its design is censorship resistance<00:07:30.919> and<00:07:31.120> obviously<00:07:31.720> that's<00:07:31.960> a 00:07:32.670 --> 00:07:32.680 align:start position:0% resistance and obviously that's a 00:07:32.680 --> 00:07:35.029 align:start position:0% resistance and obviously that's a spectrum<00:07:33.199> than<00:07:33.400> anything<00:07:33.720> else<00:07:34.080> because 00:07:35.029 --> 00:07:35.039 align:start position:0% spectrum than anything else because 00:07:35.039 --> 00:07:37.270 align:start position:0% spectrum than anything else because sensorship<00:07:35.680> resistance<00:07:36.440> depends<00:07:37.039> on 00:07:37.270 --> 00:07:37.280 align:start position:0% sensorship resistance depends on 00:07:37.280 --> 00:07:41.550 align:start position:0% sensorship resistance depends on actually<00:07:38.240> the<00:07:39.160> the<00:07:39.520> um<00:07:40.120> rules<00:07:40.440> we're<00:07:40.680> setting 00:07:41.550 --> 00:07:41.560 align:start position:0% actually the the um rules we're setting 00:07:41.560 --> 00:07:44.469 align:start position:0% actually the the um rules we're setting uh<00:07:41.680> around<00:07:42.039> ethereum<00:07:42.720> and<00:07:43.639> how<00:07:43.840> we<00:07:44.080> actually 00:07:44.469 --> 00:07:44.479 align:start position:0% uh around ethereum and how we actually 00:07:44.479 --> 00:07:47.270 align:start position:0% uh around ethereum and how we actually prevent<00:07:45.319> uh<00:07:45.520> centralization<00:07:46.440> within<00:07:46.759> the 00:07:47.270 --> 00:07:47.280 align:start position:0% prevent uh centralization within the 00:07:47.280 --> 00:07:51.070 align:start position:0% prevent uh centralization within the existing<00:07:48.280> rules<00:07:48.879> how<00:07:49.240> ethereum<00:07:49.919> operates<00:07:50.919> but 00:07:51.070 --> 00:07:51.080 align:start position:0% existing rules how ethereum operates but 00:07:51.080 --> 00:07:53.990 align:start position:0% existing rules how ethereum operates but it<00:07:51.240> also<00:07:51.680> ensures<00:07:52.319> individual 00:07:53.990 --> 00:07:54.000 align:start position:0% it also ensures individual 00:07:54.000 --> 00:07:57.029 align:start position:0% it also ensures individual Freedom<00:07:55.000> effectively<00:07:55.599> for<00:07:55.879> developers<00:07:56.759> to 00:07:57.029 --> 00:07:57.039 align:start position:0% Freedom effectively for developers to 00:07:57.039 --> 00:07:59.830 align:start position:0% Freedom effectively for developers to express<00:07:57.759> with<00:07:58.000> code<00:07:58.400> and<00:07:58.520> and<00:07:58.680> build<00:07:59.000> things 00:07:59.830 --> 00:07:59.840 align:start position:0% express with code and and build things 00:07:59.840 --> 00:08:03.189 align:start position:0% express with code and and build things that<00:08:00.039> makes<00:08:00.680> uh<00:08:00.919> a<00:08:01.080> better 00:08:03.189 --> 00:08:03.199 align:start position:0% that makes uh a better 00:08:03.199 --> 00:08:06.469 align:start position:0% that makes uh a better society<00:08:04.199> and<00:08:04.440> it<00:08:04.639> enables<00:08:05.520> uh<00:08:05.680> programmable 00:08:06.469 --> 00:08:06.479 align:start position:0% society and it enables uh programmable 00:08:06.479 --> 00:08:08.550 align:start position:0% society and it enables uh programmable trusters<00:08:07.280> agreements<00:08:07.800> and<00:08:07.960> I<00:08:08.080> think<00:08:08.319> one<00:08:08.440> of 00:08:08.550 --> 00:08:08.560 align:start position:0% trusters agreements and I think one of 00:08:08.560 --> 00:08:11.510 align:start position:0% trusters agreements and I think one of the<00:08:08.720> biggest<00:08:09.560> uh<00:08:09.720> challenges<00:08:10.199> today<00:08:10.639> is<00:08:10.840> that 00:08:11.510 --> 00:08:11.520 align:start position:0% the biggest uh challenges today is that 00:08:11.520 --> 00:08:14.629 align:start position:0% the biggest uh challenges today is that every<00:08:11.800> day<00:08:12.039> we<00:08:12.280> actually<00:08:12.560> are<00:08:13.120> relying<00:08:14.120> um 00:08:14.629 --> 00:08:14.639 align:start position:0% every day we actually are relying um 00:08:14.639 --> 00:08:17.309 align:start position:0% every day we actually are relying um upon<00:08:14.919> agreements<00:08:15.759> so<00:08:16.199> when<00:08:16.360> we<00:08:16.520> walk<00:08:16.879> on<00:08:17.039> the 00:08:17.309 --> 00:08:17.319 align:start position:0% upon agreements so when we walk on the 00:08:17.319 --> 00:08:21.670 align:start position:0% upon agreements so when we walk on the street<00:08:18.319> we<00:08:18.560> have<00:08:18.840> a<00:08:19.639> agreement<00:08:20.639> um<00:08:21.240> social 00:08:21.670 --> 00:08:21.680 align:start position:0% street we have a agreement um social 00:08:21.680 --> 00:08:24.469 align:start position:0% street we have a agreement um social agreement<00:08:22.360> economical<00:08:23.080> agreement<00:08:24.080> legal 00:08:24.469 --> 00:08:24.479 align:start position:0% agreement economical agreement legal 00:08:24.479 --> 00:08:27.029 align:start position:0% agreement economical agreement legal agreement<00:08:24.960> that<00:08:25.120> for<00:08:25.440> example<00:08:26.440> at<00:08:26.639> certain 00:08:27.029 --> 00:08:27.039 align:start position:0% agreement that for example at certain 00:08:27.039 --> 00:08:29.830 align:start position:0% agreement that for example at certain point<00:08:27.479> during<00:08:27.800> the<00:08:28.000> day<00:08:28.400> in<00:08:28.520> the<00:08:28.680> evening<00:08:29.680> um 00:08:29.830 --> 00:08:29.840 align:start position:0% point during the day in the evening um 00:08:29.840 --> 00:08:32.310 align:start position:0% point during the day in the evening um there's<00:08:30.080> going<00:08:30.159> to<00:08:30.280> be<00:08:30.400> lights<00:08:30.720> on<00:08:30.879> the<00:08:31.320> street 00:08:32.310 --> 00:08:32.320 align:start position:0% there's going to be lights on the street 00:08:32.320 --> 00:08:34.630 align:start position:0% there's going to be lights on the street um<00:08:32.519> we're<00:08:32.760> trusting<00:08:33.719> when<00:08:33.880> we<00:08:34.039> open<00:08:34.479> the 00:08:34.630 --> 00:08:34.640 align:start position:0% um we're trusting when we open the 00:08:34.640 --> 00:08:36.990 align:start position:0% um we're trusting when we open the faucets<00:08:35.599> um<00:08:35.760> in<00:08:35.880> our<00:08:36.120> kitchens<00:08:36.680> that<00:08:36.800> there's 00:08:36.990 --> 00:08:37.000 align:start position:0% faucets um in our kitchens that there's 00:08:37.000 --> 00:08:40.310 align:start position:0% faucets um in our kitchens that there's going<00:08:37.080> to<00:08:37.159> be<00:08:37.479> water<00:08:38.479> um<00:08:39.320> we<00:08:39.560> have<00:08:39.800> other<00:08:40.120> types 00:08:40.310 --> 00:08:40.320 align:start position:0% going to be water um we have other types 00:08:40.320 --> 00:08:42.949 align:start position:0% going to be water um we have other types of<00:08:40.719> agreements<00:08:41.240> between<00:08:41.599> people<00:08:42.560> uh<00:08:42.680> that<00:08:42.800> are 00:08:42.949 --> 00:08:42.959 align:start position:0% of agreements between people uh that are 00:08:42.959 --> 00:08:45.350 align:start position:0% of agreements between people uh that are based<00:08:43.279> on<00:08:43.560> on<00:08:43.919> on<00:08:44.159> different<00:08:44.440> kinds<00:08:44.640> of<00:08:44.800> norms 00:08:45.350 --> 00:08:45.360 align:start position:0% based on on on different kinds of norms 00:08:45.360 --> 00:08:49.110 align:start position:0% based on on on different kinds of norms or<00:08:45.560> legal<00:08:45.920> agreements<00:08:46.360> as<00:08:46.519> well<00:08:47.600> and<00:08:48.600> ethereum 00:08:49.110 --> 00:08:49.120 align:start position:0% or legal agreements as well and ethereum 00:08:49.120 --> 00:08:51.150 align:start position:0% or legal agreements as well and ethereum provides<00:08:49.600> this<00:08:49.880> ability<00:08:50.360> to<00:08:50.640> actually 00:08:51.150 --> 00:08:51.160 align:start position:0% provides this ability to actually 00:08:51.160 --> 00:08:53.750 align:start position:0% provides this ability to actually formalize<00:08:52.160> rules<00:08:52.920> that<00:08:53.080> can<00:08:53.240> actually<00:08:53.560> be 00:08:53.750 --> 00:08:53.760 align:start position:0% formalize rules that can actually be 00:08:53.760 --> 00:09:00.550 align:start position:0% formalize rules that can actually be really<00:08:54.040> good<00:08:54.640> for<00:08:55.640> everyone 00:09:00.550 --> 00:09:00.560 align:start position:0% 00:09:00.560 --> 00:09:03.069 align:start position:0% this<00:09:00.680> is<00:09:00.880> interesting<00:09:01.320> to<00:09:01.480> think<00:09:01.720> about<00:09:02.600> um 00:09:03.069 --> 00:09:03.079 align:start position:0% this is interesting to think about um 00:09:03.079 --> 00:09:06.670 align:start position:0% this is interesting to think about um when<00:09:03.279> we<00:09:03.839> compare<00:09:04.399> something<00:09:05.040> like<00:09:06.040> how 00:09:06.670 --> 00:09:06.680 align:start position:0% when we compare something like how 00:09:06.680 --> 00:09:08.550 align:start position:0% when we compare something like how ethereum<00:09:07.680> and<00:09:07.839> the<00:09:07.959> blockchain<00:09:08.399> has 00:09:08.550 --> 00:09:08.560 align:start position:0% ethereum and the blockchain has 00:09:08.560 --> 00:09:11.870 align:start position:0% ethereum and the blockchain has progressed<00:09:09.320> um<00:09:09.519> over<00:09:09.839> the<00:09:10.839> um<00:09:11.120> years<00:09:11.560> and<00:09:11.720> and 00:09:11.870 --> 00:09:11.880 align:start position:0% progressed um over the um years and and 00:09:11.880 --> 00:09:14.150 align:start position:0% progressed um over the um years and and compare<00:09:12.399> it<00:09:12.600> to 00:09:14.150 --> 00:09:14.160 align:start position:0% compare it to 00:09:14.160 --> 00:09:16.030 align:start position:0% compare it to something<00:09:15.160> something<00:09:15.600> like<00:09:15.760> the<00:09:15.920> the 00:09:16.030 --> 00:09:16.040 align:start position:0% something something like the the 00:09:16.040 --> 00:09:18.750 align:start position:0% something something like the the internet<00:09:16.399> progression<00:09:16.880> I<00:09:17.279> think<00:09:18.279> even<00:09:18.519> before 00:09:18.750 --> 00:09:18.760 align:start position:0% internet progression I think even before 00:09:18.760 --> 00:09:21.550 align:start position:0% internet progression I think even before going<00:09:19.040> that<00:09:19.959> we<00:09:20.160> started<00:09:20.640> pretty<00:09:20.880> much<00:09:21.200> with 00:09:21.550 --> 00:09:21.560 align:start position:0% going that we started pretty much with 00:09:21.560 --> 00:09:24.310 align:start position:0% going that we started pretty much with the<00:09:21.720> most<00:09:22.040> basic<00:09:22.800> type<00:09:23.000> of<00:09:23.240> uh<00:09:23.480> functionality 00:09:24.310 --> 00:09:24.320 align:start position:0% the most basic type of uh functionality 00:09:24.320 --> 00:09:27.389 align:start position:0% the most basic type of uh functionality moving<00:09:24.760> value<00:09:25.200> across<00:09:25.760> different<00:09:26.760> users<00:09:27.240> and 00:09:27.389 --> 00:09:27.399 align:start position:0% moving value across different users and 00:09:27.399 --> 00:09:29.389 align:start position:0% moving value across different users and and<00:09:27.519> trying<00:09:27.760> to<00:09:27.959> create<00:09:28.600> trying<00:09:28.839> to<00:09:29.000> tackle 00:09:29.389 --> 00:09:29.399 align:start position:0% and trying to create trying to tackle 00:09:29.399 --> 00:09:31.790 align:start position:0% and trying to create trying to tackle one<00:09:29.519> of<00:09:29.640> the<00:09:30.399> most 00:09:31.790 --> 00:09:31.800 align:start position:0% one of the most 00:09:31.800 --> 00:09:35.630 align:start position:0% one of the most centralized<00:09:32.800> most<00:09:33.399> centralized 00:09:35.630 --> 00:09:35.640 align:start position:0% centralized most centralized 00:09:35.640 --> 00:09:39.069 align:start position:0% centralized most centralized um<00:09:36.640> aspect<00:09:36.959> of<00:09:37.079> it<00:09:37.279> which<00:09:37.480> is<00:09:37.839> which<00:09:37.959> is<00:09:38.200> the<00:09:38.880> uh 00:09:39.069 --> 00:09:39.079 align:start position:0% um aspect of it which is which is the uh 00:09:39.079 --> 00:09:42.269 align:start position:0% um aspect of it which is which is the uh value<00:09:39.360> movements<00:09:40.040> and<00:09:40.360> and<00:09:40.800> finance<00:09:41.800> and<00:09:41.959> over 00:09:42.269 --> 00:09:42.279 align:start position:0% value movements and and finance and over 00:09:42.279 --> 00:09:45.110 align:start position:0% value movements and and finance and over time<00:09:42.760> obviously<00:09:43.240> as<00:09:43.839> we<00:09:44.000> had<00:09:44.200> a<00:09:44.399> programmable 00:09:45.110 --> 00:09:45.120 align:start position:0% time obviously as we had a programmable 00:09:45.120 --> 00:09:47.430 align:start position:0% time obviously as we had a programmable machine<00:09:46.120> the<00:09:46.279> ethereum<00:09:46.680> virtual<00:09:47.000> machine<00:09:47.320> we 00:09:47.430 --> 00:09:47.440 align:start position:0% machine the ethereum virtual machine we 00:09:47.440 --> 00:09:50.030 align:start position:0% machine the ethereum virtual machine we were<00:09:47.640> able<00:09:47.880> to<00:09:48.120> actually<00:09:48.959> program<00:09:49.760> different 00:09:50.030 --> 00:09:50.040 align:start position:0% were able to actually program different 00:09:50.040 --> 00:09:51.590 align:start position:0% were able to actually program different kinds<00:09:50.240> of<00:09:50.399> function<00:09:50.800> functionalities<00:09:51.480> that 00:09:51.590 --> 00:09:51.600 align:start position:0% kinds of function functionalities that 00:09:51.600 --> 00:09:55.389 align:start position:0% kinds of function functionalities that are<00:09:52.279> that<00:09:52.480> go<00:09:52.880> beyond<00:09:53.880> uh<00:09:54.279> moving<00:09:54.680> funds<00:09:55.200> from 00:09:55.389 --> 00:09:55.399 align:start position:0% are that go beyond uh moving funds from 00:09:55.399 --> 00:09:58.949 align:start position:0% are that go beyond uh moving funds from one<00:09:55.640> account<00:09:55.920> to<00:09:56.120> another<00:09:57.160> so<00:09:58.160> some<00:09:58.360> of<00:09:58.560> you 00:09:58.949 --> 00:09:58.959 align:start position:0% one account to another so some of you 00:09:58.959 --> 00:10:02.350 align:start position:0% one account to another so some of you who<00:09:59.480> been<00:10:00.120> uh<00:10:00.240> in<00:10:00.360> the<00:10:00.560> space<00:10:00.839> for<00:10:01.600> uh<00:10:02.079> years 00:10:02.350 --> 00:10:02.360 align:start position:0% who been uh in the space for uh years 00:10:02.360 --> 00:10:05.630 align:start position:0% who been uh in the space for uh years now<00:10:02.640> remember<00:10:03.200> the<00:10:03.880> days<00:10:04.120> of<00:10:04.360> icos 00:10:05.630 --> 00:10:05.640 align:start position:0% now remember the days of icos 00:10:05.640 --> 00:10:09.110 align:start position:0% now remember the days of icos when<00:10:06.640> Capital<00:10:07.160> allocation<00:10:08.160> um<00:10:08.560> and<00:10:08.760> capital 00:10:09.110 --> 00:10:09.120 align:start position:0% when Capital allocation um and capital 00:10:09.120 --> 00:10:13.509 align:start position:0% when Capital allocation um and capital formation<00:10:09.760> was<00:10:10.440> was<00:10:10.600> done<00:10:10.880> in<00:10:11.000> an<00:10:11.200> open<00:10:12.200> uh<00:10:12.600> way 00:10:13.509 --> 00:10:13.519 align:start position:0% formation was was done in an open uh way 00:10:13.519 --> 00:10:16.750 align:start position:0% formation was was done in an open uh way in<00:10:13.720> in<00:10:13.880> based<00:10:14.160> on<00:10:14.399> ideas<00:10:15.040> that<00:10:15.200> could<00:10:15.760> funded 00:10:16.750 --> 00:10:16.760 align:start position:0% in in based on ideas that could funded 00:10:16.760 --> 00:10:18.790 align:start position:0% in in based on ideas that could funded um<00:10:17.040> a<00:10:17.160> lot<00:10:17.320> of<00:10:17.920> interesting<00:10:18.320> Innovation 00:10:18.790 --> 00:10:18.800 align:start position:0% um a lot of interesting Innovation 00:10:18.800 --> 00:10:20.670 align:start position:0% um a lot of interesting Innovation happened<00:10:19.279> there<00:10:19.720> there<00:10:19.959> and<00:10:20.120> a<00:10:20.240> lot<00:10:20.360> of<00:10:20.480> things 00:10:20.670 --> 00:10:20.680 align:start position:0% happened there there and a lot of things 00:10:20.680 --> 00:10:22.990 align:start position:0% happened there there and a lot of things that<00:10:20.839> didn't<00:10:21.120> work<00:10:21.839> and<00:10:22.000> that<00:10:22.160> mimics<00:10:22.760> pretty 00:10:22.990 --> 00:10:23.000 align:start position:0% that didn't work and that mimics pretty 00:10:23.000 --> 00:10:25.069 align:start position:0% that didn't work and that mimics pretty much<00:10:23.200> how<00:10:23.839> internet<00:10:24.240> started<00:10:24.600> there<00:10:24.720> was<00:10:24.920> lot 00:10:25.069 --> 00:10:25.079 align:start position:0% much how internet started there was lot 00:10:25.079 --> 00:10:28.829 align:start position:0% much how internet started there was lot of<00:10:25.279> ideas<00:10:25.800> where<00:10:27.079> um<00:10:28.079> that<00:10:28.240> sounded<00:10:28.600> really 00:10:28.829 --> 00:10:28.839 align:start position:0% of ideas where um that sounded really 00:10:28.839 --> 00:10:30.829 align:start position:0% of ideas where um that sounded really interesting<00:10:29.720> but<00:10:29.920> then<00:10:30.120> eventually<00:10:30.519> didn't 00:10:30.829 --> 00:10:30.839 align:start position:0% interesting but then eventually didn't 00:10:30.839 --> 00:10:33.069 align:start position:0% interesting but then eventually didn't work<00:10:31.680> and<00:10:31.839> at<00:10:31.959> the<00:10:32.079> same<00:10:32.399> time<00:10:32.720> there<00:10:32.839> were 00:10:33.069 --> 00:10:33.079 align:start position:0% work and at the same time there were 00:10:33.079 --> 00:10:35.110 align:start position:0% work and at the same time there were ideas<00:10:33.519> that<00:10:33.720> actually<00:10:34.000> worked<00:10:34.800> and<00:10:34.959> and 00:10:35.110 --> 00:10:35.120 align:start position:0% ideas that actually worked and and 00:10:35.120 --> 00:10:37.590 align:start position:0% ideas that actually worked and and became<00:10:35.720> success<00:10:36.079> stories<00:10:36.720> of<00:10:36.920> the<00:10:37.079> whole 00:10:37.590 --> 00:10:37.600 align:start position:0% became success stories of the whole 00:10:37.600 --> 00:10:40.110 align:start position:0% became success stories of the whole internet<00:10:38.240> era<00:10:39.240> and<00:10:39.440> now<00:10:39.680> I<00:10:39.760> think<00:10:39.920> we're 00:10:40.110 --> 00:10:40.120 align:start position:0% internet era and now I think we're 00:10:40.120 --> 00:10:43.949 align:start position:0% internet era and now I think we're moving<00:10:40.480> towards<00:10:41.120> uh<00:10:41.279> a<00:10:41.519> phase<00:10:42.120> where<00:10:43.120> um<00:10:43.720> we're 00:10:43.949 --> 00:10:43.959 align:start position:0% moving towards uh a phase where um we're 00:10:43.959 --> 00:10:46.350 align:start position:0% moving towards uh a phase where um we're starting<00:10:44.279> to<00:10:44.560> validate<00:10:45.320> uh<00:10:45.519> lot<00:10:45.680> of<00:10:45.800> the<00:10:45.959> ideas 00:10:46.350 --> 00:10:46.360 align:start position:0% starting to validate uh lot of the ideas 00:10:46.360 --> 00:10:49.949 align:start position:0% starting to validate uh lot of the ideas that<00:10:46.600> actually<00:10:47.320> work<00:10:48.120> on<00:10:48.680> chain<00:10:49.680> um 00:10:49.949 --> 00:10:49.959 align:start position:0% that actually work on chain um 00:10:49.959 --> 00:10:52.790 align:start position:0% that actually work on chain um decentralized<00:10:50.639> Finance<00:10:51.200> is<00:10:51.399> is<00:10:51.639> one<00:10:52.519> good 00:10:52.790 --> 00:10:52.800 align:start position:0% decentralized Finance is is one good 00:10:52.800 --> 00:10:56.310 align:start position:0% decentralized Finance is is one good example<00:10:53.279> where<00:10:53.680> we<00:10:53.920> have<00:10:54.360> a<00:10:55.360> decentralized 00:10:56.310 --> 00:10:56.320 align:start position:0% example where we have a decentralized 00:10:56.320 --> 00:10:58.670 align:start position:0% example where we have a decentralized financial<00:10:56.880> protocols<00:10:57.399> that<00:10:57.519> are<00:10:58.160> functioning 00:10:58.670 --> 00:10:58.680 align:start position:0% financial protocols that are functioning 00:10:58.680 --> 00:11:01.269 align:start position:0% financial protocols that are functioning well<00:10:59.279> providing<00:10:59.600> High<00:10:59.880> utility<00:11:00.880> and<00:11:01.040> at<00:11:01.160> the 00:11:01.269 --> 00:11:01.279 align:start position:0% well providing High utility and at the 00:11:01.279 --> 00:11:04.590 align:start position:0% well providing High utility and at the same<00:11:01.560> time<00:11:01.800> are<00:11:02.000> making<00:11:02.839> also<00:11:03.519> revenue<00:11:04.440> and 00:11:04.590 --> 00:11:04.600 align:start position:0% same time are making also revenue and 00:11:04.600 --> 00:11:07.670 align:start position:0% same time are making also revenue and are<00:11:05.000> organized<00:11:06.000> uh<00:11:06.320> in<00:11:06.600> decentralized 00:11:07.670 --> 00:11:07.680 align:start position:0% are organized uh in decentralized 00:11:07.680 --> 00:11:09.670 align:start position:0% are organized uh in decentralized organizations<00:11:08.680> which<00:11:08.800> is<00:11:09.000> really 00:11:09.670 --> 00:11:09.680 align:start position:0% organizations which is really 00:11:09.680 --> 00:11:12.990 align:start position:0% organizations which is really fascinating<00:11:10.680> U<00:11:11.120> concept<00:11:11.639> and<00:11:11.800> I<00:11:11.920> think<00:11:12.760> we're 00:11:12.990 --> 00:11:13.000 align:start position:0% fascinating U concept and I think we're 00:11:13.000 --> 00:11:16.350 align:start position:0% fascinating U concept and I think we're moving<00:11:13.360> towards<00:11:14.160> a<00:11:15.160> path<00:11:15.560> where<00:11:15.839> we<00:11:16.000> have 00:11:16.350 --> 00:11:16.360 align:start position:0% moving towards a path where we have 00:11:16.360 --> 00:11:19.670 align:start position:0% moving towards a path where we have scalability<00:11:17.360> and<00:11:17.519> we<00:11:17.639> can<00:11:18.320> actually<00:11:19.320> move 00:11:19.670 --> 00:11:19.680 align:start position:0% scalability and we can actually move 00:11:19.680 --> 00:11:25.629 align:start position:0% scalability and we can actually move towards<00:11:20.160> more<00:11:20.680> consumer<00:11:21.200> facing 00:11:25.629 --> 00:11:25.639 align:start position:0% 00:11:25.639 --> 00:11:29.470 align:start position:0% level<00:11:26.639> so<00:11:26.880> obviously<00:11:27.600> ethereum<00:11:28.120> isn't<00:11:29.040> uh 00:11:29.470 --> 00:11:29.480 align:start position:0% level so obviously ethereum isn't uh 00:11:29.480 --> 00:11:32.470 align:start position:0% level so obviously ethereum isn't uh perfect<00:11:30.480> um<00:11:30.760> it<00:11:30.880> never<00:11:31.240> will<00:11:31.440> be<00:11:32.000> because<00:11:32.279> we 00:11:32.470 --> 00:11:32.480 align:start position:0% perfect um it never will be because we 00:11:32.480 --> 00:11:34.910 align:start position:0% perfect um it never will be because we have<00:11:32.720> a<00:11:32.839> lot<00:11:33.000> of<00:11:33.600> programmers<00:11:34.240> here<00:11:34.600> we<00:11:34.720> have<00:11:34.839> a 00:11:34.910 --> 00:11:34.920 align:start position:0% have a lot of programmers here we have a 00:11:34.920 --> 00:11:36.949 align:start position:0% have a lot of programmers here we have a lot<00:11:35.079> of<00:11:35.200> contributors<00:11:36.200> that<00:11:36.320> are<00:11:36.519> constantly 00:11:36.949 --> 00:11:36.959 align:start position:0% lot of contributors that are constantly 00:11:36.959 --> 00:11:39.750 align:start position:0% lot of contributors that are constantly innovating<00:11:37.839> and<00:11:38.279> the<00:11:38.399> world<00:11:38.839> is<00:11:39.079> constantly 00:11:39.750 --> 00:11:39.760 align:start position:0% innovating and the world is constantly 00:11:39.760 --> 00:11:42.310 align:start position:0% innovating and the world is constantly changing<00:11:40.760> and<00:11:41.480> that's<00:11:41.680> the<00:11:41.839> challenge<00:11:42.120> of 00:11:42.310 --> 00:11:42.320 align:start position:0% changing and that's the challenge of 00:11:42.320 --> 00:11:44.629 align:start position:0% changing and that's the challenge of ethereum<00:11:42.880> to<00:11:43.079> keeping<00:11:43.399> up<00:11:43.680> with<00:11:44.240> things<00:11:44.480> that 00:11:44.629 --> 00:11:44.639 align:start position:0% ethereum to keeping up with things that 00:11:44.639 --> 00:11:47.670 align:start position:0% ethereum to keeping up with things that we<00:11:44.760> learn<00:11:45.480> on<00:11:45.720> on<00:11:45.880> the<00:11:46.079> way<00:11:46.839> and<00:11:47.000> also<00:11:47.279> figuring 00:11:47.670 --> 00:11:47.680 align:start position:0% we learn on on the way and also figuring 00:11:47.680 --> 00:11:51.389 align:start position:0% we learn on on the way and also figuring out<00:11:48.399> how<00:11:48.639> ethereum<00:11:49.320> actually<00:11:50.320> um<00:11:50.639> progresses 00:11:51.389 --> 00:11:51.399 align:start position:0% out how ethereum actually um progresses 00:11:51.399 --> 00:11:55.470 align:start position:0% out how ethereum actually um progresses and<00:11:51.600> and<00:11:51.760> improves<00:11:52.240> over<00:11:52.560> time<00:11:53.399> as<00:11:53.519> we 00:11:55.470 --> 00:11:55.480 align:start position:0% and and improves over time as we 00:11:55.480 --> 00:11:58.470 align:start position:0% and and improves over time as we learn<00:11:56.480> but<00:11:56.680> one<00:11:56.880> thing<00:11:57.040> is<00:11:57.279> really<00:11:57.959> important 00:11:58.470 --> 00:11:58.480 align:start position:0% learn but one thing is really important 00:11:58.480 --> 00:12:01.829 align:start position:0% learn but one thing is really important to<00:11:58.680> realize<00:11:59.079> is<00:11:59.240> is<00:11:59.440> that<00:12:00.399> with<00:12:00.839> scalability 00:12:01.829 --> 00:12:01.839 align:start position:0% to realize is is that with scalability 00:12:01.839 --> 00:12:04.150 align:start position:0% to realize is is that with scalability and<00:12:02.519> ethereum<00:12:03.120> transaction<00:12:03.600> costs<00:12:03.880> going 00:12:04.150 --> 00:12:04.160 align:start position:0% and ethereum transaction costs going 00:12:04.160 --> 00:12:07.550 align:start position:0% and ethereum transaction costs going down<00:12:05.160> with<00:12:05.480> with<00:12:05.760> scaling<00:12:06.760> uh<00:12:06.920> whether<00:12:07.200> it's 00:12:07.550 --> 00:12:07.560 align:start position:0% down with with scaling uh whether it's 00:12:07.560 --> 00:12:10.629 align:start position:0% down with with scaling uh whether it's L2<00:12:08.560> or<00:12:09.040> the<00:12:09.160> improvements<00:12:09.720> in<00:12:09.880> the<00:12:10.079> actual 00:12:10.629 --> 00:12:10.639 align:start position:0% L2 or the improvements in the actual 00:12:10.639 --> 00:12:14.189 align:start position:0% L2 or the improvements in the actual main<00:12:10.959> architecture<00:12:11.680> on<00:12:11.839> Main<00:12:12.360> net<00:12:13.360> we<00:12:13.519> can 00:12:14.189 --> 00:12:14.199 align:start position:0% main architecture on Main net we can 00:12:14.199 --> 00:12:17.629 align:start position:0% main architecture on Main net we can achieve<00:12:15.079> um<00:12:15.920> scale<00:12:16.279> of<00:12:16.480> economics<00:12:17.360> in<00:12:17.480> the 00:12:17.629 --> 00:12:17.639 align:start position:0% achieve um scale of economics in the 00:12:17.639 --> 00:12:20.230 align:start position:0% achieve um scale of economics in the sense<00:12:18.000> that<00:12:18.760> the<00:12:18.920> more<00:12:19.160> of<00:12:19.360> these<00:12:19.760> transaction 00:12:20.230 --> 00:12:20.240 align:start position:0% sense that the more of these transaction 00:12:20.240 --> 00:12:22.870 align:start position:0% sense that the more of these transaction costs<00:12:20.519> are<00:12:20.639> going<00:12:20.959> down<00:12:21.760> we'll<00:12:22.000> see<00:12:22.279> more 00:12:22.870 --> 00:12:22.880 align:start position:0% costs are going down we'll see more 00:12:22.880 --> 00:12:25.509 align:start position:0% costs are going down we'll see more actually<00:12:23.399> adoption<00:12:24.040> of<00:12:24.199> the<00:12:24.360> technology<00:12:25.360> and 00:12:25.509 --> 00:12:25.519 align:start position:0% actually adoption of the technology and 00:12:25.519 --> 00:12:28.470 align:start position:0% actually adoption of the technology and this<00:12:25.680> happens<00:12:26.320> uh<00:12:26.480> in<00:12:26.639> every<00:12:27.240> uh<00:12:27.399> industry<00:12:28.320> as 00:12:28.470 --> 00:12:28.480 align:start position:0% this happens uh in every uh industry as 00:12:28.480 --> 00:12:30.790 align:start position:0% this happens uh in every uh industry as the<00:12:28.639> technology 00:12:30.790 --> 00:12:30.800 align:start position:0% the technology 00:12:30.800 --> 00:12:33.990 align:start position:0% the technology progresses<00:12:31.800> obviously<00:12:32.120> l2s<00:12:32.560> is<00:12:32.680> a<00:12:33.000> really 00:12:33.990 --> 00:12:34.000 align:start position:0% progresses obviously l2s is a really 00:12:34.000 --> 00:12:37.069 align:start position:0% progresses obviously l2s is a really great<00:12:34.279> example<00:12:34.880> of<00:12:35.519> finding<00:12:35.839> a<00:12:36.040> solution<00:12:36.760> how 00:12:37.069 --> 00:12:37.079 align:start position:0% great example of finding a solution how 00:12:37.079 --> 00:12:38.990 align:start position:0% great example of finding a solution how ethereum<00:12:37.519> could<00:12:37.680> actually 00:12:38.990 --> 00:12:39.000 align:start position:0% ethereum could actually 00:12:39.000 --> 00:12:41.829 align:start position:0% ethereum could actually scale<00:12:40.000> in<00:12:40.079> a<00:12:40.320> way<00:12:40.639> where<00:12:40.959> we're<00:12:41.240> focusing<00:12:41.639> on 00:12:41.829 --> 00:12:41.839 align:start position:0% scale in a way where we're focusing on 00:12:41.839 --> 00:12:44.189 align:start position:0% scale in a way where we're focusing on getting<00:12:42.160> transaction<00:12:42.680> cost<00:12:43.320> to<00:12:43.519> a<00:12:43.639> minimum 00:12:44.189 --> 00:12:44.199 align:start position:0% getting transaction cost to a minimum 00:12:44.199 --> 00:12:46.590 align:start position:0% getting transaction cost to a minimum and<00:12:44.600> opening<00:12:44.920> the<00:12:45.079> doors<00:12:45.360> to<00:12:45.600> a<00:12:45.800> new<00:12:46.040> types<00:12:46.240> of 00:12:46.590 --> 00:12:46.600 align:start position:0% and opening the doors to a new types of 00:12:46.600 --> 00:12:49.269 align:start position:0% and opening the doors to a new types of uh<00:12:47.040> applications<00:12:48.040> and<00:12:48.160> this<00:12:48.279> is<00:12:48.480> just<00:12:48.800> one 00:12:49.269 --> 00:12:49.279 align:start position:0% uh applications and this is just one 00:12:49.279 --> 00:12:52.509 align:start position:0% uh applications and this is just one kind<00:12:49.399> of<00:12:49.519> like<00:12:49.639> a<00:12:49.760> main<00:12:50.160> scaling<00:12:51.079> strategy<00:12:52.079> uh 00:12:52.509 --> 00:12:52.519 align:start position:0% kind of like a main scaling strategy uh 00:12:52.519 --> 00:12:55.389 align:start position:0% kind of like a main scaling strategy uh that<00:12:52.680> we're<00:12:53.160> seeing<00:12:53.440> at<00:12:53.560> the<00:12:53.959> moment<00:12:54.959> we<00:12:55.240> we're 00:12:55.389 --> 00:12:55.399 align:start position:0% that we're seeing at the moment we we're 00:12:55.399 --> 00:12:59.350 align:start position:0% that we're seeing at the moment we we're seeing<00:12:55.760> also<00:12:56.680> alternative<00:12:57.360> blockchains<00:12:58.360> and 00:12:59.350 --> 00:12:59.360 align:start position:0% seeing also alternative blockchains and 00:12:59.360 --> 00:13:01.110 align:start position:0% seeing also alternative blockchains and it's<00:12:59.560> always<00:12:59.880> kind<00:13:00.040> of<00:13:00.199> like<00:13:00.440> uh<00:13:00.680> interesting 00:13:01.110 --> 00:13:01.120 align:start position:0% it's always kind of like uh interesting 00:13:01.120 --> 00:13:03.990 align:start position:0% it's always kind of like uh interesting to<00:13:01.320> put<00:13:01.839> yourself<00:13:02.839> um<00:13:02.959> an<00:13:03.160> ethereum<00:13:03.760> in 00:13:03.990 --> 00:13:04.000 align:start position:0% to put yourself um an ethereum in 00:13:04.000 --> 00:13:06.829 align:start position:0% to put yourself um an ethereum in competition<00:13:04.519> to<00:13:04.839> other<00:13:05.839> um<00:13:06.160> networks<00:13:06.680> and 00:13:06.829 --> 00:13:06.839 align:start position:0% competition to other um networks and 00:13:06.839 --> 00:13:09.310 align:start position:0% competition to other um networks and other<00:13:07.160> opportunities<00:13:07.639> that<00:13:07.760> are<00:13:08.079> there<00:13:08.880> to<00:13:09.160> to 00:13:09.310 --> 00:13:09.320 align:start position:0% other opportunities that are there to to 00:13:09.320 --> 00:13:11.670 align:start position:0% other opportunities that are there to to either<00:13:09.560> to<00:13:09.720> use<00:13:09.920> or<00:13:10.120> build<00:13:11.000> and<00:13:11.199> I<00:13:11.320> think 00:13:11.670 --> 00:13:11.680 align:start position:0% either to use or build and I think 00:13:11.680 --> 00:13:14.790 align:start position:0% either to use or build and I think competition<00:13:12.240> in<00:13:12.360> general<00:13:12.760> is<00:13:13.040> is<00:13:13.240> is<00:13:13.800> healthy 00:13:14.790 --> 00:13:14.800 align:start position:0% competition in general is is is healthy 00:13:14.800 --> 00:13:18.030 align:start position:0% competition in general is is is healthy um<00:13:15.160> it<00:13:15.279> creates<00:13:15.680> inspiration<00:13:16.480> and<00:13:16.880> and<00:13:17.880> and 00:13:18.030 --> 00:13:18.040 align:start position:0% um it creates inspiration and and and 00:13:18.040 --> 00:13:20.509 align:start position:0% um it creates inspiration and and and creates<00:13:18.399> more<00:13:19.040> um 00:13:20.509 --> 00:13:20.519 align:start position:0% creates more um 00:13:20.519 --> 00:13:23.670 align:start position:0% creates more um Innovation<00:13:21.519> but<00:13:22.240> the<00:13:22.360> main<00:13:22.600> thing<00:13:22.920> why<00:13:23.440> also 00:13:23.670 --> 00:13:23.680 align:start position:0% Innovation but the main thing why also 00:13:23.680 --> 00:13:26.470 align:start position:0% Innovation but the main thing why also we<00:13:23.800> are<00:13:24.000> here<00:13:24.519> because<00:13:25.519> we're<00:13:25.839> maybe<00:13:26.160> thinking 00:13:26.470 --> 00:13:26.480 align:start position:0% we are here because we're maybe thinking 00:13:26.480 --> 00:13:29.110 align:start position:0% we are here because we're maybe thinking that<00:13:26.680> ethereum<00:13:27.240> has<00:13:27.720> an<00:13:27.959> advantage<00:13:28.839> some 00:13:29.110 --> 00:13:29.120 align:start position:0% that ethereum has an advantage some 00:13:29.120 --> 00:13:32.230 align:start position:0% that ethereum has an advantage some something<00:13:29.440> that<00:13:29.600> doesn't<00:13:30.040> exist<00:13:30.399> somewhere 00:13:32.230 --> 00:13:32.240 align:start position:0% something that doesn't exist somewhere 00:13:32.240 --> 00:13:35.829 align:start position:0% something that doesn't exist somewhere else<00:13:33.240> and<00:13:33.440> I<00:13:33.760> truly<00:13:34.079> believe<00:13:34.320> in<00:13:34.519> that 00:13:35.829 --> 00:13:35.839 align:start position:0% else and I truly believe in that 00:13:35.839 --> 00:13:38.470 align:start position:0% else and I truly believe in that so<00:13:36.839> first<00:13:37.079> of<00:13:37.199> all<00:13:37.360> I<00:13:37.440> think<00:13:37.600> ethereum<00:13:38.079> has<00:13:38.240> the 00:13:38.470 --> 00:13:38.480 align:start position:0% so first of all I think ethereum has the 00:13:38.480 --> 00:13:43.110 align:start position:0% so first of all I think ethereum has the best<00:13:39.000> developer<00:13:39.920> Community<00:13:41.079> ever<00:13:42.079> and<00:13:42.920> I've 00:13:43.110 --> 00:13:43.120 align:start position:0% best developer Community ever and I've 00:13:43.120 --> 00:13:45.430 align:start position:0% best developer Community ever and I've been<00:13:44.079> part<00:13:44.240> of<00:13:44.399> developer<00:13:44.760> communities 00:13:45.430 --> 00:13:45.440 align:start position:0% been part of developer communities 00:13:45.440 --> 00:13:49.949 align:start position:0% been part of developer communities outside<00:13:45.800> of<00:13:46.040> the<00:13:46.440> web3<00:13:47.440> uh<00:13:47.600> in<00:13:47.800> in<00:13:48.160> web3<00:13:49.160> um<00:13:49.519> and 00:13:49.949 --> 00:13:49.959 align:start position:0% outside of the web3 uh in in web3 um and 00:13:49.959 --> 00:13:53.310 align:start position:0% outside of the web3 uh in in web3 um and there's<00:13:50.440> nowhere<00:13:50.880> else<00:13:51.800> so<00:13:52.399> much<00:13:52.600> of<00:13:52.800> energy 00:13:53.310 --> 00:13:53.320 align:start position:0% there's nowhere else so much of energy 00:13:53.320 --> 00:13:55.790 align:start position:0% there's nowhere else so much of energy that<00:13:53.519> really<00:13:53.759> wants<00:13:54.040> to<00:13:54.920> move<00:13:55.240> the<00:13:55.399> space 00:13:55.790 --> 00:13:55.800 align:start position:0% that really wants to move the space 00:13:55.800 --> 00:13:58.509 align:start position:0% that really wants to move the space forward<00:13:56.800> innovate<00:13:57.639> and<00:13:57.880> actually<00:13:58.240> create 00:13:58.509 --> 00:13:58.519 align:start position:0% forward innovate and actually create 00:13:58.519 --> 00:14:00.949 align:start position:0% forward innovate and actually create something<00:13:58.800> good<00:13:59.320> for<00:14:00.079> for<00:14:00.279> the 00:14:00.949 --> 00:14:00.959 align:start position:0% something good for for the 00:14:00.959 --> 00:14:04.550 align:start position:0% something good for for the people<00:14:01.959> there's<00:14:02.639> obviously<00:14:03.639> aspect<00:14:04.000> of<00:14:04.360> being 00:14:04.550 --> 00:14:04.560 align:start position:0% people there's obviously aspect of being 00:14:04.560 --> 00:14:06.990 align:start position:0% people there's obviously aspect of being a<00:14:04.720> battle<00:14:05.079> tested<00:14:06.000> Network<00:14:06.519> in<00:14:06.639> the<00:14:06.759> sense 00:14:06.990 --> 00:14:07.000 align:start position:0% a battle tested Network in the sense 00:14:07.000 --> 00:14:10.790 align:start position:0% a battle tested Network in the sense that<00:14:07.279> ethereum<00:14:07.839> has<00:14:08.560> gone<00:14:08.880> ups<00:14:09.079> and<00:14:09.320> downs<00:14:10.040> and 00:14:10.790 --> 00:14:10.800 align:start position:0% that ethereum has gone ups and downs and 00:14:10.800 --> 00:14:14.350 align:start position:0% that ethereum has gone ups and downs and has<00:14:11.519> actually<00:14:12.519> um<00:14:12.920> been<00:14:13.199> progressing<00:14:13.839> on<00:14:14.079> on 00:14:14.350 --> 00:14:14.360 align:start position:0% has actually um been progressing on on 00:14:14.360 --> 00:14:18.670 align:start position:0% has actually um been progressing on on scalability<00:14:15.360> but<00:14:15.560> also<00:14:15.880> learn<00:14:16.880> over<00:14:17.199> the<00:14:17.800> time 00:14:18.670 --> 00:14:18.680 align:start position:0% scalability but also learn over the time 00:14:18.680 --> 00:14:20.910 align:start position:0% scalability but also learn over the time what<00:14:18.920> actually<00:14:19.519> what<00:14:19.720> path<00:14:19.959> to<00:14:20.120> take<00:14:20.680> uh<00:14:20.800> in 00:14:20.910 --> 00:14:20.920 align:start position:0% what actually what path to take uh in 00:14:20.920 --> 00:14:22.749 align:start position:0% what actually what path to take uh in the<00:14:21.079> future<00:14:21.720> and<00:14:21.839> there's<00:14:22.079> ongoing 00:14:22.749 --> 00:14:22.759 align:start position:0% the future and there's ongoing 00:14:22.759 --> 00:14:25.430 align:start position:0% the future and there's ongoing improvements<00:14:23.759> these<00:14:23.959> improvements<00:14:24.920> haven't 00:14:25.430 --> 00:14:25.440 align:start position:0% improvements these improvements haven't 00:14:25.440 --> 00:14:26.829 align:start position:0% improvements these improvements haven't are<00:14:25.639> something<00:14:25.959> that<00:14:26.079> we<00:14:26.199> don't<00:14:26.360> see<00:14:26.600> every 00:14:26.829 --> 00:14:26.839 align:start position:0% are something that we don't see every 00:14:26.839 --> 00:14:29.110 align:start position:0% are something that we don't see every day<00:14:27.160> necessarily<00:14:28.079> but<00:14:28.240> there's<00:14:28.480> a<00:14:28.600> lot<00:14:28.759> of 00:14:29.110 --> 00:14:29.120 align:start position:0% day necessarily but there's a lot of 00:14:29.120 --> 00:14:31.069 align:start position:0% day necessarily but there's a lot of work<00:14:29.320> that<00:14:29.480> actually<00:14:29.759> goes<00:14:30.079> into<00:14:30.959> the 00:14:31.069 --> 00:14:31.079 align:start position:0% work that actually goes into the 00:14:31.079 --> 00:14:33.710 align:start position:0% work that actually goes into the ethereum<00:14:31.959> um<00:14:32.240> ecosystem<00:14:32.800> and<00:14:33.040> infrastructure 00:14:33.710 --> 00:14:33.720 align:start position:0% ethereum um ecosystem and infrastructure 00:14:33.720 --> 00:14:36.949 align:start position:0% ethereum um ecosystem and infrastructure improvements<00:14:34.480> over<00:14:34.800> time<00:14:35.639> and<00:14:35.880> I<00:14:36.000> think<00:14:36.680> more 00:14:36.949 --> 00:14:36.959 align:start position:0% improvements over time and I think more 00:14:36.959 --> 00:14:39.230 align:start position:0% improvements over time and I think more more<00:14:37.199> importantly<00:14:38.160> there<00:14:38.279> is<00:14:38.399> a<00:14:38.720> commitment 00:14:39.230 --> 00:14:39.240 align:start position:0% more importantly there is a commitment 00:14:39.240 --> 00:14:44.749 align:start position:0% more importantly there is a commitment to<00:14:40.560> decentralization<00:14:41.560> um<00:14:41.839> as<00:14:42.040> well 00:14:44.749 --> 00:14:44.759 align:start position:0% to decentralization um as well 00:14:44.759 --> 00:14:48.230 align:start position:0% to decentralization um as well and<00:14:45.759> I<00:14:45.839> would<00:14:46.040> say<00:14:46.320> that<00:14:46.800> first<00:14:47.240> applications 00:14:48.230 --> 00:14:48.240 align:start position:0% and I would say that first applications 00:14:48.240 --> 00:14:51.230 align:start position:0% and I would say that first applications were<00:14:48.600> a<00:14:48.800> lot<00:14:49.480> related<00:14:49.839> to<00:14:50.079> finance<00:14:50.600> because 00:14:51.230 --> 00:14:51.240 align:start position:0% were a lot related to finance because 00:14:51.240 --> 00:14:54.870 align:start position:0% were a lot related to finance because that<00:14:51.440> was<00:14:51.759> obviously<00:14:53.240> very<00:14:54.240> straightforward 00:14:54.870 --> 00:14:54.880 align:start position:0% that was obviously very straightforward 00:14:54.880 --> 00:14:57.069 align:start position:0% that was obviously very straightforward use<00:14:55.240> case<00:14:55.480> as<00:14:56.079> blockchains<00:14:56.600> in<00:14:56.720> the<00:14:56.839> first 00:14:57.069 --> 00:14:57.079 align:start position:0% use case as blockchains in the first 00:14:57.079 --> 00:14:59.949 align:start position:0% use case as blockchains in the first place<00:14:57.279> were<00:14:57.800> trying<00:14:58.079> to<00:14:58.240> solve<00:14:58.839> a<00:14:59.079> Financial 00:14:59.949 --> 00:14:59.959 align:start position:0% place were trying to solve a Financial 00:14:59.959 --> 00:15:04.389 align:start position:0% place were trying to solve a Financial uh<00:15:00.199> problem<00:15:01.120> and<00:15:01.600> for<00:15:01.800> me<00:15:02.040> personally<00:15:03.040> um<00:15:03.759> I 00:15:04.389 --> 00:15:04.399 align:start position:0% uh problem and for me personally um I 00:15:04.399 --> 00:15:07.590 align:start position:0% uh problem and for me personally um I basically<00:15:04.800> moved<00:15:05.320> uh<00:15:05.440> into<00:15:05.680> Finland<00:15:06.480> uh<00:15:06.600> in<00:15:06.759> my 00:15:07.590 --> 00:15:07.600 align:start position:0% basically moved uh into Finland uh in my 00:15:07.600 --> 00:15:08.550 align:start position:0% basically moved uh into Finland uh in my '90s 00:15:08.550 --> 00:15:08.560 align:start position:0% '90s 00:15:08.560 --> 00:15:11.470 align:start position:0% '90s um<00:15:09.560> I<00:15:09.680> grew<00:15:09.920> up<00:15:10.199> there<00:15:10.759> uh<00:15:10.880> it<00:15:11.000> was<00:15:11.120> a<00:15:11.240> big 00:15:11.470 --> 00:15:11.480 align:start position:0% um I grew up there uh it was a big 00:15:11.480 --> 00:15:15.509 align:start position:0% um I grew up there uh it was a big recession<00:15:12.240> back<00:15:12.399> in<00:15:12.560> the<00:15:12.720> days<00:15:13.320> and<00:15:14.040> lot<00:15:14.199> of 00:15:15.509 --> 00:15:15.519 align:start position:0% recession back in the days and lot of 00:15:15.519 --> 00:15:18.230 align:start position:0% recession back in the days and lot of unemployment<00:15:16.519> Capital<00:15:16.880> dried<00:15:17.199> up<00:15:17.560> and<00:15:17.920> I<00:15:18.040> grew 00:15:18.230 --> 00:15:18.240 align:start position:0% unemployment Capital dried up and I grew 00:15:18.240 --> 00:15:20.790 align:start position:0% unemployment Capital dried up and I grew up<00:15:18.399> in<00:15:18.519> a<00:15:18.720> society<00:15:19.279> where<00:15:19.759> basically<00:15:20.639> you 00:15:20.790 --> 00:15:20.800 align:start position:0% up in a society where basically you 00:15:20.800 --> 00:15:23.670 align:start position:0% up in a society where basically you could<00:15:21.040> feel<00:15:21.480> in<00:15:21.720> families<00:15:22.360> the<00:15:22.519> pain<00:15:22.759> of<00:15:23.480> lack 00:15:23.670 --> 00:15:23.680 align:start position:0% could feel in families the pain of lack 00:15:23.680 --> 00:15:26.670 align:start position:0% could feel in families the pain of lack of<00:15:23.959> access<00:15:24.240> to<00:15:24.519> finance<00:15:25.399> um<00:15:26.160> and<00:15:26.399> just 00:15:26.670 --> 00:15:26.680 align:start position:0% of access to finance um and just 00:15:26.680 --> 00:15:29.470 align:start position:0% of access to finance um and just economical<00:15:27.600> uh<00:15:27.759> depression<00:15:28.440> and<00:15:28.600> for<00:15:28.720> me 00:15:29.470 --> 00:15:29.480 align:start position:0% economical uh depression and for me 00:15:29.480 --> 00:15:31.870 align:start position:0% economical uh depression and for me building<00:15:30.120> Financial<00:15:30.800> protocols<00:15:31.240> that<00:15:31.360> create 00:15:31.870 --> 00:15:31.880 align:start position:0% building Financial protocols that create 00:15:31.880 --> 00:15:35.550 align:start position:0% building Financial protocols that create accessibility<00:15:33.160> transparency<00:15:34.160> and<00:15:34.560> mitigates 00:15:35.550 --> 00:15:35.560 align:start position:0% accessibility transparency and mitigates 00:15:35.560 --> 00:15:37.509 align:start position:0% accessibility transparency and mitigates what<00:15:35.800> actually<00:15:36.079> Banks<00:15:36.399> can<00:15:36.560> do<00:15:36.720> today<00:15:37.240> as<00:15:37.360> a 00:15:37.509 --> 00:15:37.519 align:start position:0% what actually Banks can do today as a 00:15:37.519 --> 00:15:40.350 align:start position:0% what actually Banks can do today as a centralized<00:15:38.519> Authority<00:15:39.519> has<00:15:39.680> been<00:15:39.959> very 00:15:40.350 --> 00:15:40.360 align:start position:0% centralized Authority has been very 00:15:40.360 --> 00:15:42.309 align:start position:0% centralized Authority has been very important<00:15:40.720> to 00:15:42.309 --> 00:15:42.319 align:start position:0% important to 00:15:42.319 --> 00:15:45.509 align:start position:0% important to me<00:15:43.319> but<00:15:44.160> good<00:15:44.399> question<00:15:44.800> remains<00:15:45.040> on<00:15:45.240> how<00:15:45.360> do 00:15:45.509 --> 00:15:45.519 align:start position:0% me but good question remains on how do 00:15:45.519 --> 00:15:48.949 align:start position:0% me but good question remains on how do we<00:15:45.680> make<00:15:46.279> Financial<00:15:47.279> systems<00:15:47.959> accessible<00:15:48.839> uh 00:15:48.949 --> 00:15:48.959 align:start position:0% we make Financial systems accessible uh 00:15:48.959 --> 00:15:51.790 align:start position:0% we make Financial systems accessible uh to<00:15:49.160> everyone<00:15:49.720> because<00:15:50.600> we<00:15:50.759> know<00:15:51.120> that<00:15:51.639> there 00:15:51.790 --> 00:15:51.800 align:start position:0% to everyone because we know that there 00:15:51.800 --> 00:15:54.189 align:start position:0% to everyone because we know that there might<00:15:52.000> be<00:15:52.160> still<00:15:52.480> access<00:15:52.959> to<00:15:53.160> finance<00:15:53.839> uh<00:15:54.040> in 00:15:54.189 --> 00:15:54.199 align:start position:0% might be still access to finance uh in 00:15:54.199 --> 00:15:56.990 align:start position:0% might be still access to finance uh in Europe<00:15:54.600> and<00:15:54.800> in<00:15:54.920> the<00:15:55.040> Wern<00:15:55.480> world<00:15:56.399> but<00:15:56.600> when<00:15:56.839> we 00:15:56.990 --> 00:15:57.000 align:start position:0% Europe and in the Wern world but when we 00:15:57.000 --> 00:16:00.550 align:start position:0% Europe and in the Wern world but when we look<00:15:57.160> at<00:15:57.360> the<00:15:57.519> whole<00:15:58.079> landscape<00:15:59.240> globally<00:16:00.240> um 00:16:00.550 --> 00:16:00.560 align:start position:0% look at the whole landscape globally um 00:16:00.560 --> 00:16:03.670 align:start position:0% look at the whole landscape globally um we<00:16:00.720> still<00:16:01.120> have<00:16:01.759> quite<00:16:01.959> a<00:16:02.079> big<00:16:02.319> number<00:16:02.720> of 00:16:03.670 --> 00:16:03.680 align:start position:0% we still have quite a big number of 00:16:03.680 --> 00:16:06.110 align:start position:0% we still have quite a big number of unbanked<00:16:04.519> and<00:16:04.639> unbank<00:16:05.120> is<00:16:05.240> a<00:16:05.399> team<00:16:05.720> that 00:16:06.110 --> 00:16:06.120 align:start position:0% unbanked and unbank is a team that 00:16:06.120 --> 00:16:12.110 align:start position:0% unbanked and unbank is a team that always<00:16:07.120> um<00:16:08.000> circulates<00:16:09.000> across<00:16:10.079> the<00:16:11.120> um 00:16:12.110 --> 00:16:12.120 align:start position:0% always um circulates across the um 00:16:12.120 --> 00:16:15.790 align:start position:0% always um circulates across the um onchain<00:16:12.560> Innovation<00:16:13.519> because<00:16:14.399> ethereum<00:16:15.399> um 00:16:15.790 --> 00:16:15.800 align:start position:0% onchain Innovation because ethereum um 00:16:15.800 --> 00:16:17.829 align:start position:0% onchain Innovation because ethereum um has<00:16:15.959> this<00:16:16.160> unique<00:16:16.480> opportunity<00:16:17.120> where<00:16:17.639> you 00:16:17.829 --> 00:16:17.839 align:start position:0% has this unique opportunity where you 00:16:17.839 --> 00:16:19.910 align:start position:0% has this unique opportunity where you basically<00:16:18.160> need<00:16:18.360> an<00:16:18.519> internet<00:16:18.920> connection<00:16:19.720> in 00:16:19.910 --> 00:16:19.920 align:start position:0% basically need an internet connection in 00:16:19.920 --> 00:16:24.309 align:start position:0% basically need an internet connection in a<00:16:20.519> device<00:16:21.360> and<00:16:21.519> you<00:16:22.319> pretty<00:16:22.600> much<00:16:22.839> have<00:16:23.199> a<00:16:24.120> uh 00:16:24.309 --> 00:16:24.319 align:start position:0% a device and you pretty much have a uh 00:16:24.319 --> 00:16:27.110 align:start position:0% a device and you pretty much have a uh distribution<00:16:25.079> of<00:16:25.360> of<00:16:25.759> uh<00:16:26.199> value<00:16:26.759> at<00:16:26.920> that 00:16:27.110 --> 00:16:27.120 align:start position:0% distribution of of uh value at that 00:16:27.120 --> 00:16:29.550 align:start position:0% distribution of of uh value at that point 00:16:29.550 --> 00:16:29.560 align:start position:0% point 00:16:29.560 --> 00:16:31.470 align:start position:0% point and<00:16:30.000> I<00:16:30.120> think<00:16:30.680> there's<00:16:30.959> been<00:16:31.120> a<00:16:31.199> lot<00:16:31.360> of 00:16:31.470 --> 00:16:31.480 align:start position:0% and I think there's been a lot of 00:16:31.480 --> 00:16:32.949 align:start position:0% and I think there's been a lot of progress<00:16:31.839> that<00:16:31.959> we<00:16:32.079> have<00:16:32.160> to<00:16:32.319> celebrate<00:16:32.800> as 00:16:32.949 --> 00:16:32.959 align:start position:0% progress that we have to celebrate as 00:16:32.959 --> 00:16:35.470 align:start position:0% progress that we have to celebrate as well<00:16:33.319> especially<00:16:33.959> in<00:16:34.160> the<00:16:34.639> space<00:16:34.959> of<00:16:35.079> stable 00:16:35.470 --> 00:16:35.480 align:start position:0% well especially in the space of stable 00:16:35.480 --> 00:16:38.550 align:start position:0% well especially in the space of stable coins<00:16:36.240> as<00:16:36.480> they<00:16:36.680> minimize<00:16:37.560> geographical 00:16:38.550 --> 00:16:38.560 align:start position:0% coins as they minimize geographical 00:16:38.560 --> 00:16:40.470 align:start position:0% coins as they minimize geographical disadvantages<00:16:39.560> especially<00:16:39.920> in<00:16:40.079> countries 00:16:40.470 --> 00:16:40.480 align:start position:0% disadvantages especially in countries 00:16:40.480 --> 00:16:42.470 align:start position:0% disadvantages especially in countries where<00:16:40.720> there<00:16:41.360> there's<00:16:41.639> a<00:16:41.759> lot<00:16:41.920> of<00:16:42.319> uh 00:16:42.470 --> 00:16:42.480 align:start position:0% where there there's a lot of uh 00:16:42.480 --> 00:16:45.269 align:start position:0% where there there's a lot of uh inflation<00:16:43.519> Argentina<00:16:44.519> where<00:16:44.880> recently 00:16:45.269 --> 00:16:45.279 align:start position:0% inflation Argentina where recently 00:16:45.279 --> 00:16:49.389 align:start position:0% inflation Argentina where recently visited<00:16:46.079> and<00:16:47.000> turkey<00:16:47.480> and<00:16:47.720> and<00:16:48.279> lot<00:16:48.440> of<00:16:48.800> other 00:16:49.389 --> 00:16:49.399 align:start position:0% visited and turkey and and lot of other 00:16:49.399 --> 00:16:52.870 align:start position:0% visited and turkey and and lot of other countries<00:16:50.399> and<00:16:50.800> remittances<00:16:51.519> are<00:16:51.759> still<00:16:52.279> a 00:16:52.870 --> 00:16:52.880 align:start position:0% countries and remittances are still a 00:16:52.880 --> 00:16:55.189 align:start position:0% countries and remittances are still a big<00:16:53.519> topic<00:16:53.839> to<00:16:54.000> solve<00:16:54.600> when<00:16:54.720> we<00:16:54.839> compare 00:16:55.189 --> 00:16:55.199 align:start position:0% big topic to solve when we compare 00:16:55.199 --> 00:16:57.629 align:start position:0% big topic to solve when we compare traditional<00:16:55.920> banking<00:16:56.920> uh<00:16:57.040> we<00:16:57.199> look<00:16:57.319> at<00:16:57.519> what 00:16:57.629 --> 00:16:57.639 align:start position:0% traditional banking uh we look at what 00:16:57.639 --> 00:16:59.550 align:start position:0% traditional banking uh we look at what stable<00:16:57.959> coins<00:16:58.240> can<00:16:58.399> actually<00:16:58.600> offer 00:16:59.550 --> 00:16:59.560 align:start position:0% stable coins can actually offer 00:16:59.560 --> 00:17:02.430 align:start position:0% stable coins can actually offer that's<00:16:59.759> going<00:16:59.880> to<00:17:00.000> be<00:17:00.199> a<00:17:00.639> big<00:17:01.440> U<00:17:01.680> area<00:17:02.079> that's 00:17:02.430 --> 00:17:02.440 align:start position:0% that's going to be a big U area that's 00:17:02.440 --> 00:17:06.549 align:start position:0% that's going to be a big U area that's going<00:17:02.560> to<00:17:02.680> move<00:17:03.160> forward<00:17:04.480> rwa<00:17:05.480> as<00:17:05.720> is<00:17:05.839> a<00:17:06.079> way<00:17:06.280> to 00:17:06.549 --> 00:17:06.559 align:start position:0% going to move forward rwa as is a way to 00:17:06.559 --> 00:17:08.590 align:start position:0% going to move forward rwa as is a way to actually<00:17:07.079> put<00:17:07.360> value<00:17:07.679> on<00:17:07.839> chain<00:17:08.280> that<00:17:08.439> has 00:17:08.590 --> 00:17:08.600 align:start position:0% actually put value on chain that has 00:17:08.600 --> 00:17:11.870 align:start position:0% actually put value on chain that has been<00:17:09.360> maybe<00:17:09.720> really<00:17:10.240> difficult<00:17:10.959> um<00:17:11.600> to 00:17:11.870 --> 00:17:11.880 align:start position:0% been maybe really difficult um to 00:17:11.880 --> 00:17:14.630 align:start position:0% been maybe really difficult um to achieve<00:17:12.360> and<00:17:12.559> and<00:17:12.760> and<00:17:13.199> maybe<00:17:13.439> borrow<00:17:13.880> against 00:17:14.630 --> 00:17:14.640 align:start position:0% achieve and and and maybe borrow against 00:17:14.640 --> 00:17:16.870 align:start position:0% achieve and and and maybe borrow against uh<00:17:14.760> or<00:17:15.079> monetize<00:17:16.079> and<00:17:16.240> that's<00:17:16.400> going<00:17:16.480> to<00:17:16.600> be<00:17:16.720> a 00:17:16.870 --> 00:17:16.880 align:start position:0% uh or monetize and that's going to be a 00:17:16.880 --> 00:17:20.270 align:start position:0% uh or monetize and that's going to be a big<00:17:17.640> um<00:17:18.079> category 00:17:20.270 --> 00:17:20.280 align:start position:0% big um category 00:17:20.280 --> 00:17:23.590 align:start position:0% big um category um<00:17:21.280> and<00:17:21.600> social<00:17:21.959> media<00:17:22.600> I<00:17:22.720> think<00:17:23.000> there<00:17:23.120> is<00:17:23.439> a 00:17:23.590 --> 00:17:23.600 align:start position:0% um and social media I think there is a 00:17:23.600 --> 00:17:27.309 align:start position:0% um and social media I think there is a lot<00:17:23.760> of<00:17:24.319> people<00:17:25.039> using<00:17:25.839> social<00:17:26.400> and<00:17:26.559> this<00:17:26.679> is<00:17:26.880> a 00:17:27.309 --> 00:17:27.319 align:start position:0% lot of people using social and this is a 00:17:27.319 --> 00:17:29.150 align:start position:0% lot of people using social and this is a very<00:17:27.559> interesting<00:17:28.199> topic<00:17:28.439> and<00:17:28.559> close<00:17:28.919> to<00:17:29.000> me 00:17:29.150 --> 00:17:29.160 align:start position:0% very interesting topic and close to me 00:17:29.160 --> 00:17:32.950 align:start position:0% very interesting topic and close to me as<00:17:29.320> well<00:17:29.720> with<00:17:30.080> lens<00:17:31.080> um<00:17:31.320> especially<00:17:31.919> because 00:17:32.950 --> 00:17:32.960 align:start position:0% as well with lens um especially because 00:17:32.960 --> 00:17:35.510 align:start position:0% as well with lens um especially because centralized<00:17:33.960> uh<00:17:34.120> platforms<00:17:34.840> own<00:17:35.160> all<00:17:35.360> the 00:17:35.510 --> 00:17:35.520 align:start position:0% centralized uh platforms own all the 00:17:35.520 --> 00:17:37.789 align:start position:0% centralized uh platforms own all the data<00:17:36.120> and<00:17:36.320> and<00:17:36.440> the<00:17:36.640> connectivity<00:17:37.640> and 00:17:37.789 --> 00:17:37.799 align:start position:0% data and and the connectivity and 00:17:37.799 --> 00:17:40.190 align:start position:0% data and and the connectivity and there's<00:17:38.039> no<00:17:38.240> ownership<00:17:38.799> at<00:17:38.919> the<00:17:39.039> moment<00:17:39.799> while 00:17:40.190 --> 00:17:40.200 align:start position:0% there's no ownership at the moment while 00:17:40.200 --> 00:17:42.870 align:start position:0% there's no ownership at the moment while all<00:17:40.400> the<00:17:40.520> users<00:17:40.840> are<00:17:41.280> creating<00:17:42.120> actually<00:17:42.600> the 00:17:42.870 --> 00:17:42.880 align:start position:0% all the users are creating actually the 00:17:42.880 --> 00:17:43.590 align:start position:0% all the users are creating actually the the 00:17:43.590 --> 00:17:43.600 align:start position:0% the 00:17:43.600 --> 00:17:48.470 align:start position:0% the value<00:17:44.600> um<00:17:45.600> onchain<00:17:46.120> puts<00:17:46.480> people<00:17:47.000> first<00:17:47.799> so 00:17:48.470 --> 00:17:48.480 align:start position:0% value um onchain puts people first so 00:17:48.480 --> 00:17:50.310 align:start position:0% value um onchain puts people first so everyone<00:17:48.880> has<00:17:49.000> a<00:17:49.160> social<00:17:49.559> capital<00:17:50.240> they 00:17:50.310 --> 00:17:50.320 align:start position:0% everyone has a social capital they 00:17:50.320 --> 00:17:52.350 align:start position:0% everyone has a social capital they should<00:17:50.520> be<00:17:50.640> able<00:17:50.840> to<00:17:50.960> own<00:17:51.200> it<00:17:51.880> you<00:17:52.000> should<00:17:52.200> be 00:17:52.350 --> 00:17:52.360 align:start position:0% should be able to own it you should be 00:17:52.360 --> 00:17:55.510 align:start position:0% should be able to own it you should be able<00:17:52.880> to<00:17:53.280> access<00:17:54.039> protocols<00:17:54.679> without 00:17:55.510 --> 00:17:55.520 align:start position:0% able to access protocols without 00:17:55.520 --> 00:17:58.350 align:start position:0% able to access protocols without middlemen<00:17:56.520> we<00:17:57.240> actually<00:17:57.559> have<00:17:57.760> technology 00:17:58.350 --> 00:17:58.360 align:start position:0% middlemen we actually have technology 00:17:58.360 --> 00:18:01.230 align:start position:0% middlemen we actually have technology that<00:17:58.520> can<00:17:58.919> provide<00:17:59.240> true<00:17:59.600> access<00:18:00.240> and<00:18:00.880> fair 00:18:01.230 --> 00:18:01.240 align:start position:0% that can provide true access and fair 00:18:01.240 --> 00:18:06.070 align:start position:0% that can provide true access and fair access<00:18:01.600> and<00:18:01.840> and<00:18:02.400> transparency<00:18:03.240> as 00:18:06.070 --> 00:18:06.080 align:start position:0% 00:18:06.080 --> 00:18:08.310 align:start position:0% well<00:18:07.080> there's<00:18:07.320> definitely<00:18:07.679> other<00:18:07.919> sectors 00:18:08.310 --> 00:18:08.320 align:start position:0% well there's definitely other sectors 00:18:08.320 --> 00:18:10.630 align:start position:0% well there's definitely other sectors that<00:18:08.440> we<00:18:08.559> haven't<00:18:08.840> touch<00:18:09.120> upon<00:18:10.000> um<00:18:10.200> supply 00:18:10.630 --> 00:18:10.640 align:start position:0% that we haven't touch upon um supply 00:18:10.640 --> 00:18:13.350 align:start position:0% that we haven't touch upon um supply chain<00:18:11.440> is<00:18:11.640> very<00:18:11.840> interesting<00:18:12.679> there's<00:18:12.919> still 00:18:13.350 --> 00:18:13.360 align:start position:0% chain is very interesting there's still 00:18:13.360 --> 00:18:16.630 align:start position:0% chain is very interesting there's still 27<00:18:14.159> million<00:18:14.480> people<00:18:15.200> in<00:18:15.400> slave<00:18:15.760> labor<00:18:16.320> at<00:18:16.440> the 00:18:16.630 --> 00:18:16.640 align:start position:0% 27 million people in slave labor at the 00:18:16.640 --> 00:18:20.630 align:start position:0% 27 million people in slave labor at the moment<00:18:17.640> there's<00:18:17.960> a<00:18:18.120> lot<00:18:18.320> that<00:18:18.440> we<00:18:18.559> can<00:18:18.679> do<00:18:18.960> in 00:18:20.630 --> 00:18:20.640 align:start position:0% moment there's a lot that we can do in 00:18:20.640 --> 00:18:22.750 align:start position:0% moment there's a lot that we can do in agriculture<00:18:21.640> carbon 00:18:22.750 --> 00:18:22.760 align:start position:0% agriculture carbon 00:18:22.760 --> 00:18:25.950 align:start position:0% agriculture carbon credits<00:18:23.760> and<00:18:24.200> of<00:18:24.360> course<00:18:25.240> importantly<00:18:25.799> when 00:18:25.950 --> 00:18:25.960 align:start position:0% credits and of course importantly when 00:18:25.960 --> 00:18:28.310 align:start position:0% credits and of course importantly when you're<00:18:26.360> thinking<00:18:26.760> about<00:18:27.039> building<00:18:27.760> and<00:18:27.960> use 00:18:28.310 --> 00:18:28.320 align:start position:0% you're thinking about building and use 00:18:28.320 --> 00:18:29.669 align:start position:0% you're thinking about building and use cases 00:18:29.669 --> 00:18:29.679 align:start position:0% cases 00:18:29.679 --> 00:18:31.430 align:start position:0% cases there's<00:18:29.919> a<00:18:30.080> lot<00:18:30.240> of<00:18:30.600> values<00:18:30.960> that<00:18:31.080> you<00:18:31.200> can 00:18:31.430 --> 00:18:31.440 align:start position:0% there's a lot of values that you can 00:18:31.440 --> 00:18:34.669 align:start position:0% there's a lot of values that you can actually<00:18:32.159> tackle<00:18:33.120> um<00:18:33.679> there's<00:18:33.919> obviously<00:18:34.240> 16 00:18:34.669 --> 00:18:34.679 align:start position:0% actually tackle um there's obviously 16 00:18:34.679 --> 00:18:36.870 align:start position:0% actually tackle um there's obviously 16 areas<00:18:35.039> that<00:18:35.120> you<00:18:35.240> can<00:18:35.400> focus<00:18:35.840> and<00:18:36.400> these<00:18:36.559> are 00:18:36.870 --> 00:18:36.880 align:start position:0% areas that you can focus and these are 00:18:36.880 --> 00:18:40.230 align:start position:0% areas that you can focus and these are the<00:18:37.080> sustainability<00:18:37.840> goals<00:18:38.159> from<00:18:38.600> un<00:18:39.600> um<00:18:40.039> in 00:18:40.230 --> 00:18:40.240 align:start position:0% the sustainability goals from un um in 00:18:40.240 --> 00:18:42.149 align:start position:0% the sustainability goals from un um in most<00:18:40.480> cases<00:18:40.880> if<00:18:41.000> you're<00:18:41.200> building<00:18:41.640> already<00:18:41.960> on 00:18:42.149 --> 00:18:42.159 align:start position:0% most cases if you're building already on 00:18:42.159 --> 00:18:44.590 align:start position:0% most cases if you're building already on chain<00:18:43.039> you<00:18:43.360> actually<00:18:43.640> tackling<00:18:44.280> some<00:18:44.440> of 00:18:44.590 --> 00:18:44.600 align:start position:0% chain you actually tackling some of 00:18:44.600 --> 00:18:45.710 align:start position:0% chain you actually tackling some of these 00:18:45.710 --> 00:18:45.720 align:start position:0% these 00:18:45.720 --> 00:18:49.590 align:start position:0% these values<00:18:46.720> question<00:18:47.080> if<00:18:47.200> we<00:18:47.280> are<00:18:47.559> moving<00:18:48.559> too 00:18:49.590 --> 00:18:49.600 align:start position:0% values question if we are moving too 00:18:49.600 --> 00:18:52.310 align:start position:0% values question if we are moving too slowly<00:18:50.600> when<00:18:50.720> you<00:18:50.880> compare<00:18:51.240> to<00:18:51.559> the<00:18:51.720> adoption 00:18:52.310 --> 00:18:52.320 align:start position:0% slowly when you compare to the adoption 00:18:52.320 --> 00:18:53.990 align:start position:0% slowly when you compare to the adoption of<00:18:52.600> of<00:18:53.080> the 00:18:53.990 --> 00:18:54.000 align:start position:0% of of the 00:18:54.000 --> 00:18:56.750 align:start position:0% of of the internet<00:18:55.000> you<00:18:55.159> can<00:18:55.360> actually<00:18:55.679> see<00:18:56.039> that<00:18:56.600> the 00:18:56.750 --> 00:18:56.760 align:start position:0% internet you can actually see that the 00:18:56.760 --> 00:18:59.350 align:start position:0% internet you can actually see that the the<00:18:56.919> growth<00:18:57.240> that<00:18:57.360> is<00:18:57.559> happening<00:18:57.960> now<00:18:58.320> on 00:18:59.350 --> 00:18:59.360 align:start position:0% the growth that is happening now on 00:18:59.360 --> 00:19:02.149 align:start position:0% the growth that is happening now on and<00:18:59.520> within<00:18:59.799> the<00:18:59.919> ethereum<00:19:00.720> ecosystem<00:19:01.720> um<00:19:01.960> is 00:19:02.149 --> 00:19:02.159 align:start position:0% and within the ethereum ecosystem um is 00:19:02.159 --> 00:19:05.270 align:start position:0% and within the ethereum ecosystem um is actually<00:19:02.559> in<00:19:02.760> line<00:19:03.520> how<00:19:03.640> we're<00:19:03.880> growing<00:19:04.600> with 00:19:05.270 --> 00:19:05.280 align:start position:0% actually in line how we're growing with 00:19:05.280 --> 00:19:07.590 align:start position:0% actually in line how we're growing with online<00:19:06.280> uh<00:19:06.480> there's<00:19:06.840> little<00:19:07.039> bit<00:19:07.159> of 00:19:07.590 --> 00:19:07.600 align:start position:0% online uh there's little bit of 00:19:07.600 --> 00:19:10.230 align:start position:0% online uh there's little bit of differences<00:19:08.200> there<00:19:09.120> but<00:19:09.919> there<00:19:10.039> is 00:19:10.230 --> 00:19:10.240 align:start position:0% differences there but there is 00:19:10.240 --> 00:19:12.350 align:start position:0% differences there but there is significant<00:19:10.799> growth<00:19:11.360> happening<00:19:11.840> even<00:19:12.080> if<00:19:12.200> you 00:19:12.350 --> 00:19:12.360 align:start position:0% significant growth happening even if you 00:19:12.360 --> 00:19:16.029 align:start position:0% significant growth happening even if you don't<00:19:12.600> feel<00:19:12.880> it<00:19:13.440> every<00:19:14.120> day<00:19:15.120> we 00:19:16.029 --> 00:19:16.039 align:start position:0% don't feel it every day we 00:19:16.039 --> 00:19:18.669 align:start position:0% don't feel it every day we have<00:19:17.039> we<00:19:17.159> are<00:19:17.320> still<00:19:17.600> very<00:19:17.799> small<00:19:18.159> compared<00:19:18.520> to 00:19:18.669 --> 00:19:18.679 align:start position:0% have we are still very small compared to 00:19:18.679 --> 00:19:23.149 align:start position:0% have we are still very small compared to the<00:19:18.880> bigger<00:19:19.760> pie<00:19:20.400> of<00:19:20.600> the<00:19:20.720> internet<00:19:21.159> users<00:19:22.159> as 00:19:23.149 --> 00:19:23.159 align:start position:0% the bigger pie of the internet users as 00:19:23.159 --> 00:19:26.430 align:start position:0% the bigger pie of the internet users as active<00:19:23.720> users<00:19:24.120> on<00:19:24.799> chain<00:19:25.799> in<00:19:25.960> terms<00:19:26.200> of 00:19:26.430 --> 00:19:26.440 align:start position:0% active users on chain in terms of 00:19:26.440 --> 00:19:32.350 align:start position:0% active users on chain in terms of developers<00:19:27.440> compared<00:19:27.840> to<00:19:28.720> the<00:19:29.000> main<00:19:30.000> Web<00:19:30.240> Two 00:19:32.350 --> 00:19:32.360 align:start position:0% developers compared to the main Web Two 00:19:32.360 --> 00:19:35.470 align:start position:0% developers compared to the main Web Two world<00:19:33.360> but<00:19:33.799> to<00:19:34.000> grow<00:19:34.360> actually<00:19:34.679> from<00:19:35.000> here 00:19:35.470 --> 00:19:35.480 align:start position:0% world but to grow actually from here 00:19:35.480 --> 00:19:38.270 align:start position:0% world but to grow actually from here onwards<00:19:36.480> events<00:19:36.919> like<00:19:37.159> these<00:19:37.440> are<00:19:37.840> perfect 00:19:38.270 --> 00:19:38.280 align:start position:0% onwards events like these are perfect 00:19:38.280 --> 00:19:40.350 align:start position:0% onwards events like these are perfect because<00:19:38.559> we're<00:19:38.919> welcoming<00:19:39.400> more<00:19:39.679> developers 00:19:40.350 --> 00:19:40.360 align:start position:0% because we're welcoming more developers 00:19:40.360 --> 00:19:44.750 align:start position:0% because we're welcoming more developers into<00:19:40.640> ethereum<00:19:41.520> and<00:19:41.679> build<00:19:42.000> more<00:19:42.280> and 00:19:44.750 --> 00:19:44.760 align:start position:0% 00:19:44.760 --> 00:19:47.470 align:start position:0% expand<00:19:45.760> and<00:19:46.039> there's<00:19:46.360> challenges<00:19:46.880> when<00:19:47.039> you 00:19:47.470 --> 00:19:47.480 align:start position:0% expand and there's challenges when you 00:19:47.480 --> 00:19:50.590 align:start position:0% expand and there's challenges when you come<00:19:47.799> and<00:19:47.960> build<00:19:48.600> learning<00:19:48.960> a<00:19:49.120> new<00:19:49.600> technology 00:19:50.590 --> 00:19:50.600 align:start position:0% come and build learning a new technology 00:19:50.600 --> 00:19:53.590 align:start position:0% come and build learning a new technology smart<00:19:51.400> contracts<00:19:52.400> um<00:19:52.679> the<00:19:52.799> technology<00:19:53.240> moves 00:19:53.590 --> 00:19:53.600 align:start position:0% smart contracts um the technology moves 00:19:53.600 --> 00:19:57.789 align:start position:0% smart contracts um the technology moves fast<00:19:54.200> tools<00:19:54.520> are<00:19:54.679> moving<00:19:55.200> fast<00:19:56.200> Dows<00:19:56.640> are<00:19:56.919> very 00:19:57.789 --> 00:19:57.799 align:start position:0% fast tools are moving fast Dows are very 00:19:57.799 --> 00:20:00.870 align:start position:0% fast tools are moving fast Dows are very um<00:19:58.320> un<00:19:58.720> you<00:19:58.840> think<00:19:59.000> there's<00:19:59.200> not<00:19:59.400> many<00:19:59.880> models 00:20:00.870 --> 00:20:00.880 align:start position:0% um un you think there's not many models 00:20:00.880 --> 00:20:02.630 align:start position:0% um un you think there's not many models we're<00:20:01.080> still<00:20:01.400> very<00:20:01.600> early<00:20:01.919> in<00:20:02.039> the<00:20:02.240> space<00:20:02.520> and 00:20:02.630 --> 00:20:02.640 align:start position:0% we're still very early in the space and 00:20:02.640 --> 00:20:05.230 align:start position:0% we're still very early in the space and there's<00:20:02.880> so<00:20:03.039> much<00:20:03.240> to<00:20:03.400> do<00:20:03.799> actually<00:20:04.799> there's 00:20:05.230 --> 00:20:05.240 align:start position:0% there's so much to do actually there's 00:20:05.240 --> 00:20:08.470 align:start position:0% there's so much to do actually there's so<00:20:05.440> much<00:20:05.640> to<00:20:05.799> do<00:20:06.240> so<00:20:06.400> much<00:20:06.600> to<00:20:06.760> build<00:20:07.120> and 00:20:08.470 --> 00:20:08.480 align:start position:0% so much to do so much to build and 00:20:08.480 --> 00:20:11.510 align:start position:0% so much to do so much to build and contribute<00:20:09.480> and<00:20:09.679> ux<00:20:10.159> is<00:20:10.240> a<00:20:10.440> big<00:20:10.799> bottleneck<00:20:11.360> so 00:20:11.510 --> 00:20:11.520 align:start position:0% contribute and ux is a big bottleneck so 00:20:11.520 --> 00:20:14.190 align:start position:0% contribute and ux is a big bottleneck so for<00:20:11.679> ux<00:20:12.360> we<00:20:12.520> have<00:20:12.679> to<00:20:12.799> do<00:20:13.039> a<00:20:13.159> lot<00:20:13.720> and<00:20:13.880> I<00:20:14.000> think 00:20:14.190 --> 00:20:14.200 align:start position:0% for ux we have to do a lot and I think 00:20:14.200 --> 00:20:16.750 align:start position:0% for ux we have to do a lot and I think this<00:20:14.320> is<00:20:14.440> the<00:20:14.720> time<00:20:15.320> as<00:20:15.440> we<00:20:15.600> have<00:20:15.760> solved 00:20:16.750 --> 00:20:16.760 align:start position:0% this is the time as we have solved 00:20:16.760 --> 00:20:18.830 align:start position:0% this is the time as we have solved scalability<00:20:17.520> and<00:20:17.679> progressed<00:20:18.400> uh<00:20:18.559> quite<00:20:18.760> a 00:20:18.830 --> 00:20:18.840 align:start position:0% scalability and progressed uh quite a 00:20:18.840 --> 00:20:22.310 align:start position:0% scalability and progressed uh quite a lot<00:20:19.039> on<00:20:19.360> that<00:20:19.600> aspect<00:20:20.400> being<00:20:20.679> able<00:20:20.960> to<00:20:21.799> have 00:20:22.310 --> 00:20:22.320 align:start position:0% lot on that aspect being able to have 00:20:22.320 --> 00:20:24.909 align:start position:0% lot on that aspect being able to have good<00:20:22.520> U<00:20:22.799> act<00:20:23.280> and<00:20:23.400> build<00:20:23.720> good<00:20:23.919> applications 00:20:24.909 --> 00:20:24.919 align:start position:0% good U act and build good applications 00:20:24.919 --> 00:20:27.110 align:start position:0% good U act and build good applications that<00:20:25.039> are<00:20:25.200> on<00:20:25.400> chain<00:20:26.080> is<00:20:26.280> is<00:20:26.440> going<00:20:26.520> to<00:20:26.679> be<00:20:26.960> the 00:20:27.110 --> 00:20:27.120 align:start position:0% that are on chain is is going to be the 00:20:27.120 --> 00:20:29.510 align:start position:0% that are on chain is is going to be the next<00:20:27.360> chapter 00:20:29.510 --> 00:20:29.520 align:start position:0% next chapter 00:20:29.520 --> 00:20:33.270 align:start position:0% next chapter so<00:20:29.760> where<00:20:29.919> we<00:20:30.039> are<00:20:30.600> in<00:20:30.840> the<00:20:31.400> progress<00:20:32.000> of<00:20:32.280> of<00:20:32.720> uh 00:20:33.270 --> 00:20:33.280 align:start position:0% so where we are in the progress of of uh 00:20:33.280 --> 00:20:35.750 align:start position:0% so where we are in the progress of of uh adoption<00:20:33.960> I<00:20:34.120> think<00:20:34.720> we're<00:20:34.960> somewhere<00:20:35.320> in<00:20:35.440> the 00:20:35.750 --> 00:20:35.760 align:start position:0% adoption I think we're somewhere in the 00:20:35.760 --> 00:20:39.470 align:start position:0% adoption I think we're somewhere in the middle<00:20:36.760> in<00:20:36.919> terms<00:20:37.240> of<00:20:37.480> the<00:20:38.159> usage<00:20:39.159> if<00:20:39.280> we 00:20:39.470 --> 00:20:39.480 align:start position:0% middle in terms of the usage if we 00:20:39.480 --> 00:20:42.789 align:start position:0% middle in terms of the usage if we compare<00:20:39.760> it<00:20:39.960> to<00:20:40.880> the<00:20:41.280> time<00:20:42.000> as<00:20:42.240> Internet 00:20:42.789 --> 00:20:42.799 align:start position:0% compare it to the time as Internet 00:20:42.799 --> 00:20:45.870 align:start position:0% compare it to the time as Internet started<00:20:43.159> to<00:20:43.280> grow<00:20:44.080> it<00:20:44.240> doesn't<00:20:44.720> feel<00:20:45.720> that 00:20:45.870 --> 00:20:45.880 align:start position:0% started to grow it doesn't feel that 00:20:45.880 --> 00:20:47.990 align:start position:0% started to grow it doesn't feel that it's<00:20:46.080> moving<00:20:46.600> fast<00:20:47.200> but<00:20:47.360> we're<00:20:47.600> growing 00:20:47.990 --> 00:20:48.000 align:start position:0% it's moving fast but we're growing 00:20:48.000 --> 00:20:51.070 align:start position:0% it's moving fast but we're growing there's<00:20:48.280> more<00:20:48.440> and<00:20:48.600> more<00:20:48.840> users<00:20:49.760> and<00:20:50.159> Builders 00:20:51.070 --> 00:20:51.080 align:start position:0% there's more and more users and Builders 00:20:51.080 --> 00:20:54.789 align:start position:0% there's more and more users and Builders uh<00:20:51.240> in<00:20:51.360> the 00:20:54.789 --> 00:20:54.799 align:start position:0% 00:20:54.799 --> 00:20:57.190 align:start position:0% space<00:20:55.799> poly<00:20:56.200> Market<00:20:56.440> is<00:20:56.559> an<00:20:56.720> interesting 00:20:57.190 --> 00:20:57.200 align:start position:0% space poly Market is an interesting 00:20:57.200 --> 00:20:59.710 align:start position:0% space poly Market is an interesting example<00:20:57.760> as<00:20:57.919> well<00:20:58.360> where<00:20:58.840> you<00:20:58.960> can<00:20:59.159> build 00:20:59.710 --> 00:20:59.720 align:start position:0% example as well where you can build 00:20:59.720 --> 00:21:02.669 align:start position:0% example as well where you can build something<00:21:00.159> that<00:21:00.280> is<00:21:01.320> actually<00:21:02.320> really 00:21:02.669 --> 00:21:02.679 align:start position:0% something that is actually really 00:21:02.679 --> 00:21:06.190 align:start position:0% something that is actually really valuable<00:21:03.240> in<00:21:03.360> terms<00:21:03.720> of<00:21:04.240> uh<00:21:04.799> information<00:21:05.799> and 00:21:06.190 --> 00:21:06.200 align:start position:0% valuable in terms of uh information and 00:21:06.200 --> 00:21:08.549 align:start position:0% valuable in terms of uh information and can<00:21:06.440> predict<00:21:07.400> we're<00:21:07.640> able<00:21:07.840> to<00:21:08.039> predict 00:21:08.549 --> 00:21:08.559 align:start position:0% can predict we're able to predict 00:21:08.559 --> 00:21:12.029 align:start position:0% can predict we're able to predict election<00:21:09.039> results<00:21:09.720> uh<00:21:09.840> on 00:21:12.029 --> 00:21:12.039 align:start position:0% election results uh on 00:21:12.039 --> 00:21:14.710 align:start position:0% election results uh on chain<00:21:13.039> we<00:21:13.200> can<00:21:13.320> build<00:21:13.640> anything<00:21:14.159> it's<00:21:14.360> just 00:21:14.710 --> 00:21:14.720 align:start position:0% chain we can build anything it's just 00:21:14.720 --> 00:21:17.909 align:start position:0% chain we can build anything it's just about<00:21:15.559> how<00:21:15.799> we<00:21:16.039> imagine<00:21:16.440> and<00:21:16.640> think<00:21:16.919> about 00:21:17.909 --> 00:21:17.919 align:start position:0% about how we imagine and think about 00:21:17.919 --> 00:21:20.830 align:start position:0% about how we imagine and think about it<00:21:18.919> and<00:21:19.120> I<00:21:19.240> think<00:21:19.520> we're<00:21:19.720> in<00:21:19.960> this<00:21:20.120> moment 00:21:20.830 --> 00:21:20.840 align:start position:0% it and I think we're in this moment 00:21:20.840 --> 00:21:22.789 align:start position:0% it and I think we're in this moment because<00:21:21.080> we<00:21:21.240> want<00:21:21.400> to<00:21:21.559> shape<00:21:21.919> the<00:21:22.080> future 00:21:22.789 --> 00:21:22.799 align:start position:0% because we want to shape the future 00:21:22.799 --> 00:21:25.310 align:start position:0% because we want to shape the future where<00:21:22.960> we<00:21:23.080> want<00:21:23.240> to<00:21:23.440> live<00:21:23.799> in<00:21:24.799> and<00:21:24.919> we're<00:21:25.120> just 00:21:25.310 --> 00:21:25.320 align:start position:0% where we want to live in and we're just 00:21:25.320 --> 00:21:28.390 align:start position:0% where we want to live in and we're just getting<00:21:25.720> started<00:21:26.720> it's<00:21:27.000> very<00:21:27.240> early<00:21:28.240> I've 00:21:28.390 --> 00:21:28.400 align:start position:0% getting started it's very early I've 00:21:28.400 --> 00:21:30.909 align:start position:0% getting started it's very early I've been<00:21:28.760> here<00:21:28.840> for<00:21:29.039> seven<00:21:29.400> years<00:21:30.279> and<00:21:30.440> I<00:21:30.600> feel 00:21:30.909 --> 00:21:30.919 align:start position:0% been here for seven years and I feel 00:21:30.919 --> 00:21:33.350 align:start position:0% been here for seven years and I feel that<00:21:31.279> there's<00:21:31.640> there's<00:21:31.840> still<00:21:32.159> two<00:21:32.440> decades 00:21:33.350 --> 00:21:33.360 align:start position:0% that there's there's still two decades 00:21:33.360 --> 00:21:36.549 align:start position:0% that there's there's still two decades just<00:21:33.520> to<00:21:33.760> build<00:21:34.360> every<00:21:35.559> fundamental 00:21:36.549 --> 00:21:36.559 align:start position:0% just to build every fundamental 00:21:36.559 --> 00:21:39.350 align:start position:0% just to build every fundamental infrastructure<00:21:37.320> and<00:21:37.679> accessibility<00:21:38.440> for 00:21:39.350 --> 00:21:39.360 align:start position:0% infrastructure and accessibility for 00:21:39.360 --> 00:21:43.430 align:start position:0% infrastructure and accessibility for users<00:21:40.360> thank 00:21:43.430 --> 00:21:43.440 align:start position:0% 00:21:43.440 --> 00:21:47.190 align:start position:0% [Applause] 00:21:47.190 --> 00:21:47.200 align:start position:0% [Applause] 00:21:47.200 --> 00:21:49.909 align:start position:0% [Applause] you<00:21:48.200> thank<00:21:48.360> you<00:21:48.480> stany<00:21:49.039> that<00:21:49.159> was<00:21:49.360> wonderful 00:21:49.909 --> 00:21:49.919 align:start position:0% you thank you stany that was wonderful 00:21:49.919 --> 00:21:52.029 align:start position:0% you thank you stany that was wonderful lots<00:21:50.159> to<00:21:50.279> think<00:21:50.480> about<00:21:51.000> Okay<00:21:51.159> so<00:21:51.360> we've<00:21:51.600> got 00:21:52.029 --> 00:21:52.039 align:start position:0% lots to think about Okay so we've got 00:21:52.039 --> 00:21:54.430 align:start position:0% lots to think about Okay so we've got three<00:21:52.320> minutes<00:21:52.679> for<00:21:52.840> some<00:21:53.039> questions<00:21:54.000> what<00:21:54.240> is 00:21:54.430 --> 00:21:54.440 align:start position:0% three minutes for some questions what is 00:21:54.440 --> 00:21:58.810 align:start position:0% three minutes for some questions what is the<00:21:55.080> code<00:21:56.080> so<00:21:56.279> the<00:21:56.440> code<00:21:56.760> is<00:21:57.080> Force<00:21:57.480> for<00:21:57.760> good 00:21:58.810 --> 00:21:58.820 align:start position:0% the code so the code is Force for good 00:21:58.820 --> 00:22:02.760 align:start position:0% the code so the code is Force for good [Laughter] 00:22:02.760 --> 00:22:02.770 align:start position:0% [Laughter] 00:22:02.770 --> 00:22:06.029 align:start position:0% [Laughter] [Applause] 00:22:06.029 --> 00:22:06.039 align:start position:0% [Applause] 00:22:06.039 --> 00:22:08.630 align:start position:0% [Applause] okay<00:22:06.760> as<00:22:06.840> a<00:22:07.000> developer<00:22:07.760> sometimes<00:22:08.440> is 00:22:08.630 --> 00:22:08.640 align:start position:0% okay as a developer sometimes is 00:22:08.640 --> 00:22:10.149 align:start position:0% okay as a developer sometimes is haunting<00:22:09.080> to<00:22:09.240> tackle<00:22:09.559> the<00:22:09.679> adoption 00:22:10.149 --> 00:22:10.159 align:start position:0% haunting to tackle the adoption 00:22:10.159 --> 00:22:12.310 align:start position:0% haunting to tackle the adoption challenge<00:22:10.799> what<00:22:11.159> are<00:22:11.360> the<00:22:11.520> baby<00:22:11.840> steps<00:22:12.200> we 00:22:12.310 --> 00:22:12.320 align:start position:0% challenge what are the baby steps we 00:22:12.320 --> 00:22:14.149 align:start position:0% challenge what are the baby steps we should<00:22:12.520> take<00:22:12.679> if<00:22:12.840> we<00:22:12.960> make<00:22:13.200> Financial<00:22:13.640> tools 00:22:14.149 --> 00:22:14.159 align:start position:0% should take if we make Financial tools 00:22:14.159 --> 00:22:16.669 align:start position:0% should take if we make Financial tools that<00:22:14.279> Mak<00:22:15.080> use<00:22:15.279> of<00:22:15.480> crypto<00:22:15.919> and<00:22:16.120> apply<00:22:16.400> it<00:22:16.520> to 00:22:16.669 --> 00:22:16.679 align:start position:0% that Mak use of crypto and apply it to 00:22:16.679 --> 00:22:18.269 align:start position:0% that Mak use of crypto and apply it to our 00:22:18.269 --> 00:22:18.279 align:start position:0% our 00:22:18.279 --> 00:22:20.110 align:start position:0% our community<00:22:19.279> I<00:22:19.360> think<00:22:19.520> you<00:22:19.600> should<00:22:19.840> always 00:22:20.110 --> 00:22:20.120 align:start position:0% community I think you should always 00:22:20.120 --> 00:22:23.269 align:start position:0% community I think you should always start<00:22:20.400> from<00:22:20.559> the<00:22:20.679> user<00:22:21.679> and<00:22:21.880> and<00:22:22.080> actually<00:22:22.760> how 00:22:23.269 --> 00:22:23.279 align:start position:0% start from the user and and actually how 00:22:23.279 --> 00:22:26.990 align:start position:0% start from the user and and actually how you<00:22:23.400> can<00:22:24.039> help<00:22:25.039> by<00:22:25.200> building<00:22:25.640> a<00:22:25.880> product<00:22:26.880> I 00:22:26.990 --> 00:22:27.000 align:start position:0% you can help by building a product I 00:22:27.000 --> 00:22:29.110 align:start position:0% you can help by building a product I think<00:22:27.600> when<00:22:27.760> I<00:22:27.919> was<00:22:28.080> building 00:22:29.110 --> 00:22:29.120 align:start position:0% think when I was building 00:22:29.120 --> 00:22:31.950 align:start position:0% think when I was building on<00:22:29.360> on<00:22:29.520> ethereum<00:22:30.080> and<00:22:30.360> and<00:22:31.320> and<00:22:31.480> even<00:22:31.679> a<00:22:31.799> little 00:22:31.950 --> 00:22:31.960 align:start position:0% on on ethereum and and and even a little 00:22:31.960 --> 00:22:34.390 align:start position:0% on on ethereum and and and even a little bit<00:22:32.080> of<00:22:32.279> today<00:22:33.080> it<00:22:33.240> started<00:22:33.600> from<00:22:33.880> a<00:22:34.000> lot<00:22:34.120> of 00:22:34.390 --> 00:22:34.400 align:start position:0% bit of today it started from a lot of 00:22:34.400 --> 00:22:36.669 align:start position:0% bit of today it started from a lot of the<00:22:34.520> technology<00:22:35.120> side<00:22:35.720> the<00:22:35.840> protocol<00:22:36.279> aspect 00:22:36.669 --> 00:22:36.679 align:start position:0% the technology side the protocol aspect 00:22:36.679 --> 00:22:38.669 align:start position:0% the technology side the protocol aspect but<00:22:36.799> I<00:22:36.960> think<00:22:37.600> today<00:22:38.000> if<00:22:38.120> I<00:22:38.200> will<00:22:38.400> build 00:22:38.669 --> 00:22:38.679 align:start position:0% but I think today if I will build 00:22:38.679 --> 00:22:40.230 align:start position:0% but I think today if I will build something<00:22:38.960> new<00:22:39.320> I<00:22:39.400> will<00:22:39.559> start<00:22:39.840> from<00:22:40.039> a 00:22:40.230 --> 00:22:40.240 align:start position:0% something new I will start from a 00:22:40.240 --> 00:22:43.549 align:start position:0% something new I will start from a product<00:22:40.799> and<00:22:41.000> a<00:22:41.440> and<00:22:41.640> actually<00:22:42.640> what<00:22:43.279> how<00:22:43.440> we 00:22:43.549 --> 00:22:43.559 align:start position:0% product and a and actually what how we 00:22:43.559 --> 00:22:51.909 align:start position:0% product and a and actually what how we can<00:22:43.720> solve<00:22:44.200> a<00:22:44.360> users 00:22:51.909 --> 00:22:51.919 align:start position:0% 00:22:51.919 --> 00:22:54.070 align:start position:0% problem 00:22:54.070 --> 00:22:54.080 align:start position:0% problem 00:22:54.080 --> 00:22:57.630 align:start position:0% problem okay<00:22:55.080> yeah<00:22:55.440> what's<00:22:56.120> the<00:22:56.279> avara<00:22:56.760> end<00:22:57.039> game<00:22:57.520> how 00:22:57.630 --> 00:22:57.640 align:start position:0% okay yeah what's the avara end game how 00:22:57.640 --> 00:22:58.460 align:start position:0% okay yeah what's the avara end game how do<00:22:57.760> you<00:22:57.880> want<00:22:58.080> to 00:22:58.460 --> 00:22:58.470 align:start position:0% do you want to 00:22:58.470 --> 00:23:00.110 align:start position:0% do you want to [Music] 00:23:00.110 --> 00:23:00.120 align:start position:0% [Music] 00:23:00.120 --> 00:23:05.750 align:start position:0% [Music] it's<00:23:00.360> gone<00:23:00.600> hang 00:23:05.750 --> 00:23:05.760 align:start position:0% 00:23:05.760 --> 00:23:08.750 align:start position:0% on<00:23:06.760> okay<00:23:06.960> let's<00:23:07.120> go<00:23:07.240> to<00:23:07.279> the<00:23:07.400> top 00:23:08.750 --> 00:23:08.760 align:start position:0% on okay let's go to the top 00:23:08.760 --> 00:23:11.149 align:start position:0% on okay let's go to the top one<00:23:09.760> how<00:23:09.919> can<00:23:10.080> we<00:23:10.240> protect<00:23:10.520> defi<00:23:10.919> from 00:23:11.149 --> 00:23:11.159 align:start position:0% one how can we protect defi from 00:23:11.159 --> 00:23:13.750 align:start position:0% one how can we protect defi from unhealthy<00:23:11.720> incentives<00:23:12.679> schemes<00:23:13.480> uh<00:23:13.600> and 00:23:13.750 --> 00:23:13.760 align:start position:0% unhealthy incentives schemes uh and 00:23:13.760 --> 00:23:14.950 align:start position:0% unhealthy incentives schemes uh and continue<00:23:14.120> growing<00:23:14.400> it<00:23:14.520> as<00:23:14.640> a<00:23:14.760> better 00:23:14.950 --> 00:23:14.960 align:start position:0% continue growing it as a better 00:23:14.960 --> 00:23:17.950 align:start position:0% continue growing it as a better Financial 00:23:17.950 --> 00:23:17.960 align:start position:0% 00:23:17.960 --> 00:23:20.669 align:start position:0% system<00:23:18.960> I<00:23:19.080> think<00:23:19.240> it<00:23:19.440> really<00:23:19.799> depends 00:23:20.669 --> 00:23:20.679 align:start position:0% system I think it really depends 00:23:20.679 --> 00:23:22.590 align:start position:0% system I think it really depends obviously<00:23:21.080> on<00:23:21.559> what<00:23:21.720> we're<00:23:21.880> building<00:23:22.320> in 00:23:22.590 --> 00:23:22.600 align:start position:0% obviously on what we're building in 00:23:22.600 --> 00:23:25.669 align:start position:0% obviously on what we're building in overall<00:23:23.600> incentives<00:23:24.159> are<00:23:24.919> extremely<00:23:25.440> good 00:23:25.669 --> 00:23:25.679 align:start position:0% overall incentives are extremely good 00:23:25.679 --> 00:23:28.070 align:start position:0% overall incentives are extremely good way<00:23:26.000> of<00:23:26.240> Distributing<00:23:26.960> ownership<00:23:27.600> of<00:23:27.760> a 00:23:28.070 --> 00:23:28.080 align:start position:0% way of Distributing ownership of a 00:23:28.080 --> 00:23:29.149 align:start position:0% way of Distributing ownership of a system 00:23:29.149 --> 00:23:29.159 align:start position:0% system 00:23:29.159 --> 00:23:31.549 align:start position:0% system that<00:23:29.279> can<00:23:29.400> be<00:23:29.520> governed<00:23:29.880> by<00:23:29.960> a<00:23:30.360> community<00:23:31.360> uh 00:23:31.549 --> 00:23:31.559 align:start position:0% that can be governed by a community uh 00:23:31.559 --> 00:23:34.029 align:start position:0% that can be governed by a community uh with<00:23:31.720> the<00:23:31.840> said<00:23:32.080> rules<00:23:32.799> in<00:23:32.919> the<00:23:33.080> community 00:23:34.029 --> 00:23:34.039 align:start position:0% with the said rules in the community 00:23:34.039 --> 00:23:35.909 align:start position:0% with the said rules in the community transparently<00:23:35.039> that's<00:23:35.200> a<00:23:35.360> big<00:23:35.600> valid 00:23:35.909 --> 00:23:35.919 align:start position:0% transparently that's a big valid 00:23:35.919 --> 00:23:38.950 align:start position:0% transparently that's a big valid proposition<00:23:36.720> that<00:23:36.840> is<00:23:37.120> why<00:23:37.720> the<00:23:37.880> a<00:23:38.320> DA<00:23:38.760> uh 00:23:38.950 --> 00:23:38.960 align:start position:0% proposition that is why the a DA uh 00:23:38.960 --> 00:23:41.990 align:start position:0% proposition that is why the a DA uh exist<00:23:39.520> or<00:23:40.279> the<00:23:40.440> sky<00:23:40.760> da<00:23:41.000> exist<00:23:41.279> or<00:23:41.400> Lio<00:23:41.799> da 00:23:41.990 --> 00:23:42.000 align:start position:0% exist or the sky da exist or Lio da 00:23:42.000 --> 00:23:43.750 align:start position:0% exist or the sky da exist or Lio da exist<00:23:42.360> because<00:23:42.840> they're<00:23:43.080> able<00:23:43.279> to<00:23:43.440> create 00:23:43.750 --> 00:23:43.760 align:start position:0% exist because they're able to create 00:23:43.760 --> 00:23:45.950 align:start position:0% exist because they're able to create these<00:23:43.919> rules<00:23:44.760> and<00:23:45.039> actually<00:23:45.400> benefit<00:23:45.799> the 00:23:45.950 --> 00:23:45.960 align:start position:0% these rules and actually benefit the 00:23:45.960 --> 00:23:49.230 align:start position:0% these rules and actually benefit the community<00:23:46.799> and<00:23:46.960> build<00:23:47.440> better<00:23:47.840> outcomes<00:23:48.840> uh 00:23:49.230 --> 00:23:49.240 align:start position:0% community and build better outcomes uh 00:23:49.240 --> 00:23:50.909 align:start position:0% community and build better outcomes uh effectively<00:23:50.240> I 00:23:50.909 --> 00:23:50.919 align:start position:0% effectively I 00:23:50.919 --> 00:23:53.909 align:start position:0% effectively I think<00:23:51.919> incentives<00:23:52.640> come<00:23:53.240> when<00:23:53.440> there<00:23:53.559> is 00:23:53.909 --> 00:23:53.919 align:start position:0% think incentives come when there is 00:23:53.919 --> 00:23:57.350 align:start position:0% think incentives come when there is actually<00:23:54.320> a<00:23:54.760> meaningful<00:23:55.760> Traction<00:23:56.320> in<00:23:56.480> a<00:23:56.840> in<00:23:56.960> a 00:23:57.350 --> 00:23:57.360 align:start position:0% actually a meaningful Traction in a in a 00:23:57.360 --> 00:23:59.830 align:start position:0% actually a meaningful Traction in a in a protocol<00:23:57.799> Market<00:23:58.080> fit<00:23:58.640> and<00:23:59.200> that's<00:23:59.440> the<00:23:59.640> place 00:23:59.830 --> 00:23:59.840 align:start position:0% protocol Market fit and that's the place 00:23:59.840 --> 00:24:02.669 align:start position:0% protocol Market fit and that's the place where<00:24:00.080> incentives<00:24:00.640> are<00:24:01.200> more<00:24:01.919> interesting 00:24:02.669 --> 00:24:02.679 align:start position:0% where incentives are more interesting 00:24:02.679 --> 00:24:05.549 align:start position:0% where incentives are more interesting where<00:24:02.840> it's<00:24:03.039> more<00:24:03.320> about<00:24:04.320> decentralizing<00:24:05.320> a 00:24:05.549 --> 00:24:05.559 align:start position:0% where it's more about decentralizing a 00:24:05.559 --> 00:24:07.950 align:start position:0% where it's more about decentralizing a valuable<00:24:06.039> infrastructure<00:24:06.760> that<00:24:07.360> has 00:24:07.950 --> 00:24:07.960 align:start position:0% valuable infrastructure that has 00:24:07.960 --> 00:24:10.990 align:start position:0% valuable infrastructure that has actually<00:24:08.520> High<00:24:08.760> utility<00:24:09.559> on<00:24:09.799> chain<00:24:10.640> and<00:24:10.840> the 00:24:10.990 --> 00:24:11.000 align:start position:0% actually High utility on chain and the 00:24:11.000 --> 00:24:13.230 align:start position:0% actually High utility on chain and the another<00:24:11.400> question<00:24:11.840> about<00:24:12.200> the<00:24:12.720> avaras 00:24:13.230 --> 00:24:13.240 align:start position:0% another question about the avaras 00:24:13.240 --> 00:24:17.390 align:start position:0% another question about the avaras endgame<00:24:14.120> so<00:24:15.120> obviously<00:24:15.520> we<00:24:15.640> started<00:24:16.320> with<00:24:16.960> um 00:24:17.390 --> 00:24:17.400 align:start position:0% endgame so obviously we started with um 00:24:17.400 --> 00:24:21.230 align:start position:0% endgame so obviously we started with um within<00:24:17.720> a<00:24:18.039> Labs<00:24:18.480> building<00:24:19.480> Defi<00:24:20.480> and<00:24:20.640> the<00:24:20.760> a 00:24:21.230 --> 00:24:21.240 align:start position:0% within a Labs building Defi and the a 00:24:21.240 --> 00:24:24.430 align:start position:0% within a Labs building Defi and the a protocol<00:24:22.240> um<00:24:22.760> our<00:24:22.960> ing<00:24:23.200> game<00:24:23.520> with<00:24:23.840> avara<00:24:24.320> is 00:24:24.430 --> 00:24:24.440 align:start position:0% protocol um our ing game with avara is 00:24:24.440 --> 00:24:27.230 align:start position:0% protocol um our ing game with avara is to<00:24:24.600> build<00:24:24.960> a<00:24:25.159> people<00:24:25.600> powered<00:24:26.080> internet<00:24:27.080> we 00:24:27.230 --> 00:24:27.240 align:start position:0% to build a people powered internet we 00:24:27.240 --> 00:24:29.909 align:start position:0% to build a people powered internet we think<00:24:27.559> that<00:24:27.799> blockchain<00:24:28.440> is<00:24:29.080> as<00:24:29.200> a<00:24:29.360> technology 00:24:29.909 --> 00:24:29.919 align:start position:0% think that blockchain is as a technology 00:24:29.919 --> 00:24:32.389 align:start position:0% think that blockchain is as a technology it's<00:24:30.159> use<00:24:30.480> case<00:24:30.640> neutral<00:24:31.320> meaning<00:24:31.799> that<00:24:32.279> we 00:24:32.389 --> 00:24:32.399 align:start position:0% it's use case neutral meaning that we 00:24:32.399 --> 00:24:35.549 align:start position:0% it's use case neutral meaning that we will<00:24:32.520> see<00:24:32.840> Financial<00:24:33.360> use<00:24:33.760> cases<00:24:34.760> um<00:24:35.159> but<00:24:35.320> also 00:24:35.549 --> 00:24:35.559 align:start position:0% will see Financial use cases um but also 00:24:35.559 --> 00:24:37.230 align:start position:0% will see Financial use cases um but also ethereum<00:24:36.000> is<00:24:36.080> going<00:24:36.200> to<00:24:36.360> be<00:24:36.520> used<00:24:36.919> for 00:24:37.230 --> 00:24:37.240 align:start position:0% ethereum is going to be used for 00:24:37.240 --> 00:24:39.830 align:start position:0% ethereum is going to be used for non-financial<00:24:38.240> use<00:24:38.600> cases<00:24:38.919> as<00:24:39.080> well<00:24:39.679> and 00:24:39.830 --> 00:24:39.840 align:start position:0% non-financial use cases as well and 00:24:39.840 --> 00:24:42.630 align:start position:0% non-financial use cases as well and avara<00:24:40.399> is<00:24:40.799> something<00:24:41.159> that<00:24:41.360> provides<00:24:42.320> access 00:24:42.630 --> 00:24:42.640 align:start position:0% avara is something that provides access 00:24:42.640 --> 00:24:44.789 align:start position:0% avara is something that provides access to<00:24:42.880> that<00:24:43.320> infrastructure<00:24:44.120> and<00:24:44.360> these<00:24:44.480> use 00:24:44.789 --> 00:24:44.799 align:start position:0% to that infrastructure and these use 00:24:44.799 --> 00:24:47.269 align:start position:0% to that infrastructure and these use cases<00:24:45.120> with<00:24:45.320> family<00:24:46.120> and<00:24:46.320> extends<00:24:46.919> with<00:24:47.159> with 00:24:47.269 --> 00:24:47.279 align:start position:0% cases with family and extends with with 00:24:47.279 --> 00:24:50.950 align:start position:0% cases with family and extends with with defy<00:24:47.919> with<00:24:48.120> a<00:24:48.880> and<00:24:49.120> go<00:24:49.480> and<00:24:49.679> and<00:24:49.840> in<00:24:50.039> Social<00:24:50.840> uh 00:24:50.950 --> 00:24:50.960 align:start position:0% defy with a and go and and in Social uh 00:24:50.960 --> 00:24:52.549 align:start position:0% defy with a and go and and in Social uh with 00:24:52.549 --> 00:24:52.559 align:start position:0% with 00:24:52.559 --> 00:24:55.950 align:start position:0% with lens<00:24:53.559> cool<00:24:54.000> 25<00:24:54.480> seconds<00:24:55.080> as<00:24:55.200> a<00:24:55.320> developer 00:24:55.950 --> 00:24:55.960 align:start position:0% lens cool 25 seconds as a developer 00:24:55.960 --> 00:24:58.830 align:start position:0% lens cool 25 seconds as a developer sometimes<00:24:56.320> is<00:24:56.480> haunting<00:24:56.880> to<00:24:57.159> tackle<00:24:58.159> uh<00:24:58.640> oh 00:24:58.830 --> 00:24:58.840 align:start position:0% sometimes is haunting to tackle uh oh 00:24:58.840 --> 00:25:01.350 align:start position:0% sometimes is haunting to tackle uh oh we've<00:24:59.000> done<00:24:59.120> that<00:24:59.240> one<00:24:59.360> haven't<00:24:59.559> we<00:25:00.080> yes<00:25:01.080> as<00:25:01.240> a 00:25:01.350 --> 00:25:01.360 align:start position:0% we've done that one haven't we yes as a 00:25:01.360 --> 00:25:02.909 align:start position:0% we've done that one haven't we yes as a builder<00:25:01.640> of<00:25:01.760> both<00:25:01.960> Network<00:25:02.360> consumer<00:25:02.720> apps 00:25:02.909 --> 00:25:02.919 align:start position:0% builder of both Network consumer apps 00:25:02.919 --> 00:25:04.389 align:start position:0% builder of both Network consumer apps and<00:25:03.039> protocols<00:25:03.640> what's<00:25:03.840> your<00:25:04.000> view<00:25:04.240> on 00:25:04.389 --> 00:25:04.399 align:start position:0% and protocols what's your view on 00:25:04.399 --> 00:25:07.350 align:start position:0% and protocols what's your view on scaling<00:25:05.039> improving<00:25:05.799> on 00:25:07.350 --> 00:25:07.360 align:start position:0% scaling improving on 00:25:07.360 --> 00:25:10.070 align:start position:0% scaling improving on L<00:25:08.360> okay<00:25:08.520> I<00:25:08.640> got<00:25:08.760> it<00:25:09.080> yeah<00:25:09.320> so<00:25:09.559> let's<00:25:09.720> call<00:25:09.840> it<00:25:09.919> a 00:25:10.070 --> 00:25:10.080 align:start position:0% L okay I got it yeah so let's call it a 00:25:10.080 --> 00:25:11.669 align:start position:0% L okay I got it yeah so let's call it a day<00:25:10.320> I<00:25:10.520> give<00:25:10.640> up<00:25:10.960> okay<00:25:11.200> we're<00:25:11.360> just<00:25:11.480> about 00:25:11.669 --> 00:25:11.679 align:start position:0% day I give up okay we're just about 00:25:11.679 --> 00:25:14.190 align:start position:0% day I give up okay we're just about finished<00:25:12.000> now<00:25:12.600> I<00:25:12.679> think<00:25:12.840> scaling<00:25:13.279> should<00:25:13.480> be<00:25:14.039> a 00:25:14.190 --> 00:25:14.200 align:start position:0% finished now I think scaling should be a 00:25:14.200 --> 00:25:16.909 align:start position:0% finished now I think scaling should be a really<00:25:14.640> kind<00:25:14.760> of<00:25:14.919> like<00:25:15.080> a<00:25:15.760> open-ended<00:25:16.760> uh 00:25:16.909 --> 00:25:16.919 align:start position:0% really kind of like a open-ended uh 00:25:16.919 --> 00:25:18.549 align:start position:0% really kind of like a open-ended uh space<00:25:17.240> so<00:25:17.399> you<00:25:17.480> should<00:25:17.679> be<00:25:17.840> able<00:25:18.200> we<00:25:18.279> should<00:25:18.440> be 00:25:18.549 --> 00:25:18.559 align:start position:0% space so you should be able we should be 00:25:18.559 --> 00:25:21.909 align:start position:0% space so you should be able we should be able<00:25:18.799> to<00:25:18.919> see<00:25:19.720> scaling<00:25:20.279> happening<00:25:20.799> within<00:25:21.120> the 00:25:21.909 --> 00:25:21.919 align:start position:0% able to see scaling happening within the 00:25:21.919 --> 00:25:24.269 align:start position:0% able to see scaling happening within the main<00:25:22.360> architecture<00:25:22.880> of<00:25:23.039> ethereum<00:25:23.960> in<00:25:24.159> in 00:25:24.269 --> 00:25:24.279 align:start position:0% main architecture of ethereum in in 00:25:24.279 --> 00:25:26.470 align:start position:0% main architecture of ethereum in in mainnet<00:25:25.120> I<00:25:25.200> think<00:25:25.360> there<00:25:25.480> should<00:25:25.679> be<00:25:25.799> a<00:25:25.919> lot<00:25:26.039> of 00:25:26.470 --> 00:25:26.480 align:start position:0% mainnet I think there should be a lot of 00:25:26.480 --> 00:25:28.310 align:start position:0% mainnet I think there should be a lot of innovation<00:25:27.480> happening<00:25:27.880> which<00:25:28.000> is<00:25:28.120> going<00:25:28.200> to 00:25:28.310 --> 00:25:28.320 align:start position:0% innovation happening which is going to 00:25:28.320 --> 00:25:30.549 align:start position:0% innovation happening which is going to going<00:25:28.399> to<00:25:28.520> happen<00:25:29.480> um<00:25:29.760> but<00:25:29.880> scaling<00:25:30.360> also 00:25:30.549 --> 00:25:30.559 align:start position:0% going to happen um but scaling also 00:25:30.559 --> 00:25:33.549 align:start position:0% going to happen um but scaling also should<00:25:30.840> happen<00:25:31.159> on<00:25:31.360> these<00:25:31.600> l2s<00:25:32.600> specifically 00:25:33.549 --> 00:25:33.559 align:start position:0% should happen on these l2s specifically 00:25:33.559 --> 00:25:36.549 align:start position:0% should happen on these l2s specifically and<00:25:33.679> we<00:25:33.799> should<00:25:34.039> keep<00:25:34.440> exploring<00:25:35.240> new<00:25:35.919> ideas 00:25:36.549 --> 00:25:36.559 align:start position:0% and we should keep exploring new ideas 00:25:36.559 --> 00:25:39.750 align:start position:0% and we should keep exploring new ideas and<00:25:36.840> and<00:25:37.320> ways<00:25:37.600> to<00:25:37.799> scale<00:25:38.200> Beyond<00:25:39.200> uh<00:25:39.480> what<00:25:39.600> we 00:25:39.750 --> 00:25:39.760 align:start position:0% and and ways to scale Beyond uh what we 00:25:39.760 --> 00:25:42.669 align:start position:0% and and ways to scale Beyond uh what we know<00:25:39.960> today<00:25:40.600> and<00:25:40.799> this<00:25:40.919> is<00:25:41.039> a<00:25:41.720> ever<00:25:42.120> ending 00:25:42.669 --> 00:25:42.679 align:start position:0% know today and this is a ever ending 00:25:42.679 --> 00:25:45.669 align:start position:0% know today and this is a ever ending research<00:25:43.200> topic<00:25:43.799> where<00:25:44.799> uh<00:25:44.960> developers<00:25:45.440> can 00:25:45.669 --> 00:25:45.679 align:start position:0% research topic where uh developers can 00:25:45.679 --> 00:25:48.110 align:start position:0% research topic where uh developers can actually<00:25:46.360> uh<00:25:46.520> contribute<00:25:47.080> I<00:25:47.159> do<00:25:47.360> think<00:25:47.600> that 00:25:48.110 --> 00:25:48.120 align:start position:0% actually uh contribute I do think that 00:25:48.120 --> 00:25:50.029 align:start position:0% actually uh contribute I do think that we<00:25:48.240> should<00:25:48.520> apply<00:25:49.200> the<00:25:49.360> exact<00:25:49.640> amount<00:25:49.880> of 00:25:50.029 --> 00:25:50.039 align:start position:0% we should apply the exact amount of 00:25:50.039 --> 00:25:52.110 align:start position:0% we should apply the exact amount of security<00:25:50.480> that<00:25:50.640> we<00:25:50.760> need<00:25:51.279> based<00:25:51.520> on<00:25:51.640> the<00:25:51.760> use 00:25:52.110 --> 00:25:52.120 align:start position:0% security that we need based on the use 00:25:52.120 --> 00:25:54.630 align:start position:0% security that we need based on the use case<00:25:52.799> D5<00:25:53.320> for<00:25:53.480> example<00:25:54.000> might<00:25:54.159> need<00:25:54.480> the 00:25:54.630 --> 00:25:54.640 align:start position:0% case D5 for example might need the 00:25:54.640 --> 00:25:57.470 align:start position:0% case D5 for example might need the highest<00:25:54.960> security<00:25:55.760> where<00:25:56.000> social<00:25:56.480> might<00:25:56.679> need 00:25:57.470 --> 00:25:57.480 align:start position:0% highest security where social might need 00:25:57.480 --> 00:25:59.830 align:start position:0% highest security where social might need uh<00:25:57.640> the<00:25:57.760> least<00:25:58.399> amount<00:25:58.679> of<00:25:59.039> uh<00:25:59.200> security<00:25:59.679> but 00:25:59.830 --> 00:25:59.840 align:start position:0% uh the least amount of uh security but 00:25:59.840 --> 00:26:02.310 align:start position:0% uh the least amount of uh security but some<00:26:00.120> security<00:26:00.480> to<00:26:01.000> enable<00:26:01.440> guarantees<00:26:01.960> for 00:26:02.310 --> 00:26:02.320 align:start position:0% some security to enable guarantees for 00:26:02.320 --> 00:26:04.389 align:start position:0% some security to enable guarantees for the<00:26:02.440> users<00:26:03.440> okay<00:26:03.600> we're<00:26:03.720> out<00:26:03.840> of<00:26:04.000> time<00:26:04.279> thank 00:26:04.389 --> 00:26:04.399 align:start position:0% the users okay we're out of time thank 00:26:04.399 --> 00:26:06.430 align:start position:0% the users okay we're out of time thank you<00:26:04.520> very<00:26:04.679> much<00:26:04.880> Danny<00:26:05.559> big<00:26:05.720> round<00:26:05.919> of 00:26:06.430 --> 00:26:06.440 align:start position:0% you very much Danny big round of 00:26:06.440 --> 00:26:09.020 align:start position:0% you very much Danny big round of applause<00:26:07.440> awesome<00:26:07.799> thank<00:26:07.960> you 00:26:09.020 --> 00:26:09.030 align:start position:0% applause awesome thank you 00:26:09.030 --> 00:26:12.630 align:start position:0% applause awesome thank you [Applause]